j3-fortran / fortran_proposals

Proposals for the Fortran Standard Committee
178 stars 15 forks source link

Issue lifetime #93

Open aradi opened 4 years ago

aradi commented 4 years ago

Question about the general workflow: Should issues be closed at some point? Or should they stay opened, unless they result in a PR? What if the discussion/conversation stopped for a while? Or if it arrived at a dead end? Or in case the discussion raised severe concerns killing its chances of becoming a strong proposal and being discussed by the committee?

I think, closing issues could help to concentrate efforts on the more promising candidates.

certik commented 4 years ago

Right now let's keep all issues open. Only close the ones for which there is a new issue the supersedes them.

I will be discussing with the committee at the February 2020 meeting how to improve our workflow, and once the committee settles on some plan how to handle new proposals, my idea is to close an issue that was essentially rejected by the committee in the current form. One can then open a new issue that fixes some of the objections with a new proposal.

I expect that there will be thousands of issues eventually, so the way I expect us to prioritize them is to use GitHub features like "sort by number of comments", or "number of reactions". We will also create meta issues for things like "issues to create proposals for February 2020 meeting", etc.