Consider normalizing the advance notice requirements between the AC meeting and all other kinds of meetings
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 262
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Description
(Split off from https://github.com/w3c/AB-public/issues/283)
How much advance notice is required for all but one meeting type is defined in §3.1.2.1. Meeting Scheduling and Announcements. The one exception is the AC meeting; the advance notice requirements for it are defined in §3.2.4. Advisory Committee Meetings.
We should consider aligning the advance notice requirements. If we're able to fully align them, we could have one set of requirements that apply to all meeting types.
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
Start by comparing §3.1.2.1, Meeting Scheduling and Announcements, with §3.2.4, Advisory Committee Meetings, in the linked Process document. Determine whether their advance-notice requirements can be fully aligned, then update the relevant requirements once the desired policy has been agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100