w3c / w3c/process

State the purpose of AC meetings

Open
#1,096 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
262
Forks
194
PR merge metrics
No merged PRs in 30d

Description

§ 3.2.4. Advisory Committee Meetings requires that AC meetings happen, but it doesn't concisely state why AC meetings are even a thing. Why do we require the Team to organize two AC meetings each year? @cwilso's comment on #1094 suggests a rationale:

One of the most important parts of this in-person interaction is the ability to have two-way conversations: having advisory committee meetings that are one way presentation focused is not a great use of time. […] Having the ability to meet and have interactive discussions across membership stakeholders on various topics is very important however.

I'm inclined to agree. I suspect something along these lines is a widely shared belief among the membership: the AC meeting is important because it provides an opportunity for the AC to have frank discussions on matters of import to it and to the consortium.

Perhaps the Process section on AC meetings would benefit from the addition of a one-sentence statement of purpose, along these lines.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with § 3.2.4, Advisory Committee Meetings, in the Process Document and review the linked discussion in issue #1094. Add a concise statement explaining the purpose of AC meetings, reflecting their role in frank, interactive discussions. Done means the section clearly states why the meetings are required.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.