Consider dropping the entire section on AC meetings
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 262
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Description
As (perhaps obliquely) suggested by @reidmore-online in a comment on #1084, maybe the Process document doesn't need to define what an AC meeting is, or require that or how they happen.
One argument for this that comes to mind: the Process document does not say anything at all about an annual technical plenary, and yet we can see that the Team has diligently organized one every year for twenty four years and counting. (A different conclusion that you could come to from this same argument is #1095.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source file or test; start by reading the AC-meetings section of the Process document and the linked discussion in #1084. Done means deciding whether that section and its requirements should be removed, then updating the document accordingly; #1095 is noted as an alternative direction.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100