If we had required an assessment step for https://github.com/ClassicPress-research/custom-fields or https://github.com/ClassicPress-research/object-relationships or https://github.com/ClassicPress-research/db-backup then they would not exist today. These are not fully polished, production-ready projects, but they serve as a base for future development and a way to attract contributors. Low barriers to entry for a research plugin are very important for both of these reasons.
I think so, especially if there is an associated petition. At least, this is what I have been doing until now. This shouldn’t imply any commitment on the part of ClassicPress until we are ready for it.
No, we have a responsibility to do what we can to move CP forward with limited resources. So far, with research plugins, that has meant giving people a sandbox to play in, and more recently providing a way for these sandbox/research projects to advance into something more official if and when they are ready. Some really good things have come out of this process and I think there will be more in the future. Not all research projects will advance into something more official and this is totally fine.
This is exactly the point of the research plugin process, and the reason why we shouldn’t make any changes to that arrangement.
Where the Ecosystem team should come in is when we are ready to decide “hey, this is pretty good, and lots of people are interested in it, it just needs a bit of polish/maintenance to be production ready”.
I don’t think any of the 3 research projects I mentioned above are in this situation right now, but they might be one day (I’d like to work on custom fields after v2 is out for example). We also don’t know ahead of time which research projects are going to end up having value.