Update GOVERNANCE.md - #18
Conversation
clevinson
left a comment
clevinson
left a comment
There was a problem hiding this comment.
Thanks for pushing this forward @MathewBiddle. Excited to see ACDD work getting reboot and moving along.
I have a few small suggestions but happy to see this merged and the suggestions taken as follow ups if preferred.
| Identified a problem | ||
| Make an issue | ||
| Issue will be available for open discussion for any interested participants |
There was a problem hiding this comment.
This renders a bit funky. I think these lines should either have further spacing so that they render as separate paragraphs, or have periods between them to designate different sentences.
There was a problem hiding this comment.
This was supposed to be a numeric list. I made the change. Have a look-see.
|
|
||
| ### Dormant issues | ||
|
|
||
| If an issue falls silent for more than six months without conclusion, any member of the ACDD steering committee may post on the issue to encourage any interested person to resume it within three weeks, if they wish it to remain open. |
There was a problem hiding this comment.
Just noting that we're referencing steering committee here, but we've dropped all mention of the steering committee & who is on it.
Should be fine if this PR is followed up shortly with one that's specific to outlining more info on steering committee.
There was a problem hiding this comment.
I added a section with a table for Steering Committee membership. We can define who is on it later. Have a look-see.
fixing syntax and making a space for steering committee
|
This looks great, and looks ready to merge! |
| 1. Issues can be closed under the following conditions: | ||
| 1. Once consensus is reached, the issue can be closed and move to summary and Pull Request | ||
| 1. After no activity in the issue for 3 months, an automated message will prompt administrators to take some action on the issue (close, raise for more discussion, merge, leave open, etc.). After three additional months it will become a [dormant issue](#dormant-issues). | ||
| 1. After no discussion for one week the issue will be closed or implemented according to the consensus reached. |
There was a problem hiding this comment.
One week is pretty quick for a distributed discussion where the individuals involved may be working on multiple other projects as well.
| 1. Make an issue | ||
| 1. Issue will be available for open discussion for any interested participants | ||
| 1. Issues can be closed under the following conditions: | ||
| 1. Once consensus is reached, the issue can be closed and move to summary and Pull Request |
There was a problem hiding this comment.
It might be good to more explicitly define what is meant by consensus. Perhaps including
- a conclusion/summary should be clearly stated
- any objections should be discussed and either addressed or withdrawn
- no objections for one (or three, see comment below) week(s) after conclusion stated or last objection closed
There was a problem hiding this comment.
I use the term objection rather than discussion to allow for questions, clarification, etc. without restarting the waiting period.
4 participants
closes #3 #15 #16