In another topic on setting goals for 2020, @docwilmot raised the issue of finding better ways of setting priorities for core development. It has been suggested by some members of our community that this is a conversation that deserves its own topic. So here it is. To start the conversation, here are a few excerpts from the @docwilmot's original post.
For example, Drupal has methods of setting priorities for core development: there are 4 possible (mandatory!) tags on issues (critical, major, normal, minor).
There are also the "favorite of ..." tags which may give an idea of the perceived priorities of the main leaders of the organization.
We don't currently have an effective prioritization system. Devs pick their favorite issues and contribute PRs, then hope that someone else will review it, but due to our small group size, that someone else very likely has some other issue(s) which is his/her favorite. We can also advocate for an issue, that simply tells others which issues we prefer. We have milestones; if an issue is not concluded by a milestone, we simply bump it to a new milestone, or remove the milestone(!) regardless of how significant it may be.
None of this allows any group consensus or discussion on which of these may be critical to Backdrop's development and future.
What are your comments or suggestions regarding setting development priorities?