Improving the description of tutorials so we get the kinds of articles we think are most useful #203
Description
There's some question about whether we need to make the requirements for tutorials more restrictive to make people self-select not to submit if the software is not actually going to be useful. We don't necessarily want tutorials for code that is just barely leaving development, because most of those are not actually that useful to people; maybe there's some good ones there, but they are hard to find. Also, those papers are less likely to be good and require more time and energy from reviewers (reviewers like to review good papers).
- One thought is to make it explicit there should already exist some community of users, but not restricting the size of the community (i.e. a project with a community of 5 external users might end up just needing to be advertised more)
Other thoughts?