Disagree with something
The point of keeping the count in the open is that you can correct a piece of it
Three kinds of disagreement move the project: an upgrade that is missing, a stage that is wrong, and a test that would not settle the question. Each is welcome, and each leaves a trace.
How to send it
Disagreements go through issues in the public repository, because an issue is durable and quotable, and folding one into the record is a change that can cite it. Every upgrade's page has a link that opens an issue about it with its name already filled in. Or start from one of these:
The most useful thing you can give is a record: a link to the trial report, the approval notice or the confirmed news story that shows the stage you are claiming. A stage without a record cannot be set.
What happens to it
- John rules on it. Some disagreements change the record; some are answered and left as they are. Either way the issue records the ruling.
- A change to the record lands as a commit that cites the issue, with a dated line in the story so far.
- A changed stage gets a revision on the entry, with the old stage, the new one, the date and the reason, so the entry's own page shows how it has moved.
A plain issue with the upgrade's name and your reasoning is exactly enough. The repository is at github.com/jfredson/upgrade-tree.