Skip to content
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.

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

Describe community opportunities in charter development #146

Merged
merged 2 commits into from
Oct 12, 2021

Conversation

wseltzer
Copy link
Member

Describe community opportunities in charter development.

Address w3c/process#560

Wendy Seltzer added 2 commits August 16, 2021 16:41
Describe community opportunities in charter development
Additional updates to describe community input
@wseltzer wseltzer requested a review from plehegar October 1, 2021 15:02
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


<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

@@ -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)

@@ -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)

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)

@svgeesus svgeesus merged commit 03e9817 into main Oct 12, 2021
@plehegar plehegar deleted the wseltzer-patch-2 branch October 26, 2023 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants