Skip to content

Describe community opportunities in charter development #146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 12, 2021
Merged

Describe community opportunities in charter development #146

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
46fd9f9
Describe community opportunities in charter development
Aug 16, 2021
dd395e2
Update charter.html
Aug 16, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
49 changes: 24 additions & 25 deletions process/charter.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,19 +97,27 @@ <h4>Nearby</h4>
href="https://www.w3.org/groups/">Groups</a></li>
</ul>
</div>
<p>Charters are <a href="https://www.w3.org/2020/Process-20200915/#WGCharterDevelopment">formally</a> developed by the Team, with community input.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good (and reflects current reality)

In practice, ideas for new charter development come from a range of sources: Community Groups, Interest Groups, Workshops, input to the Strategy Incubation Pipeline.
Team documents proposals in the <a href="https://github.com/w3c/strategy/projects/2">Strategy Team's Incubation Pipeline (Funnel)</a>,
and moves them through the pipeline (left to right) as they progress.</p>

<p>In particular, Community Groups and Interest Groups may develop draft charters (or draft the <a href="https://w3c.github.io/charter-drafts/charter-template.html#scope">"scope"</a> and <a href="https://w3c.github.io/charter-drafts/charter-template.html#deliverables">"deliverables"</a> section of a charter)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having done so, do they add it to the funnel themselves or wait for "the Team to document the proposal" as the previous paragraph suggests?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addresses w3c/process#560 well

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which do you think works better for people, @svgeesus ? I'd be happy to invite people to input directly

when they identify work items that they believe are ready for the Recommendation track.</p>

<p>The Strategy Team identifies a charter shephered, through the <a href="https://github.com/w3c/strategy/blob/main/4.Chartering.md">process documented in the "chartering" column</a> of the public Pipeline.
Each area of exploration or possible new work is shown as a GitHub issue.
Interested community members are invited to add comments to the issue thread with information or expressions of support or concern, and to share pull requests on draft charters.</p>

<p>First, W3M chooses a Team Contact to manage the group creation
process.</p>

<p>The Process Document includes a section on <a
<!-- <p>The Process Document includes a section on <a
href="https://www.w3.org/Consortium/Process/#WGCharterDevelopment">Working Group
and Interest Group Charter Development</a>, which includes a
requirement to alert the Advisory Committee when work begins on a
charter for a new group. See also <a href="/2002/05/rec-tips">tips for
getting to Recommendation faster</a> and <a
href="/TR/qa-handbook/">The QA Handbook</a>, which discusses process
and operational aspects of certain quality assurance practices of
W3C's Working Groups,</p>
W3C's Working Groups,</p> -->

<p>For existing groups, the Chair and Team Contact should work with
the WG to create a new charter and develop rationale as to why the
Expand All @@ -121,15 +129,12 @@ <h4>Nearby</h4>
should send them to the Team Contact, who should see that the
request is reviewed by the Project and Strategy Leads in a timely manner.</p>

<p><strong>Note:</strong> Team Contacts should take caution when
creating a new charter by copying an old one, especially in light of
adoption of the W3C Patent Policy. Please review the <a
href="https://www.w3.org/Consortium/Process/#WGCharter">list
of charter requirements</a> to ensure that your charter is complete
(e.g., it includes a duration for the group).</p>

<p class=timeline><em>Timeline:</em> For existing groups, this takes no time. For new groups, it may take one month or more for W3M
to start dedicating resources.</p>
<p>Team Contacts and others proposing charters should start from the <a href="https://w3c.github.io/charter-drafts/">Charter Template</a>, rather than copying
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strongly in favor of this change

an existing Group charter, as the template reflects the latest guidance from Membership and the Director/W3M on common matters of structure.</p>


<!--<p class=timeline><em>Timeline:</em> For existing groups, this takes no time. For new groups, it may take one month or more for W3M
to start dedicating resources.</p> -->

<h2 id="advance">2. Advance Notice</h2>

Expand All @@ -152,15 +157,14 @@ <h2 id="advance">2. Advance Notice</h2>

<h2>3. <a id="creation" name="creation">Charter Creation</a></h2>

<p>The Team Contact works with the Strategy Lead to
<p>The Team Contact or shepherd works with the Strategy Team and interested community participants to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good (and reflects current reality)

draft a provisional charter. See the
<a href="https://w3c.github.io/charter-drafts/charter-template.html">Charter template</a>
and
W3C Process Document for the
<a href="https://www.w3.org/Consortium/Process/#WGCharter">list of charter requirements</a>.
The Team Contact may wish to share drafts of the provisional
charter with a candidate Chair (if one exists), a relevant interest
group or interested community of W3C members prior to Member
charter with relevant interest groups and interested community of W3C members prior to Advisory Committee
review.</p>

<p class=timeline><em>Timeline:</em> due to the discussion needing to happen with the community and the need
Expand Down Expand Up @@ -329,15 +333,10 @@ <h3 id="horizontal-review">3.4 Horizontal Review</h3>
principles)</li>
</ul>

<p>When the Charter is brought to W3M, the Team Contact should state
which horizontal experts approved that the dependencies were
appropriately documented based on the current understanding of the
work. If when the Team Contact engaged experts there were
insufficient experts available for timely review, then the Team
<p>When the Charter is brought to W3M, the Team Contact should note the horizontal review status in the Pipeline.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Much better than the previous text (and again, reflects current practice)

If team was unable to obtain timely review, then the Team
Contact can move ahead with the charter nevertheless, and should
report this to W3M. W3M will monitor whether particular horizontal
activities are insufficiently resourced, leading to regular delays on
charter reviews.</p>
report this to W3M. </p>

<h2>4. <a id="approval" name="approval">Charter Approval by
W3M</a></h2>
Expand Down