Charters are formally developed by the Team, with community input. + 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 Strategy Team's Incubation Pipeline (Funnel), + and moves them through the pipeline (left to right) as they progress.
+ +In particular, Community Groups and Interest Groups may develop draft charters (or draft the "scope" and "deliverables" section of a charter) + when they identify work items that they believe are ready for the Recommendation track.
+ +The Strategy Team identifies a charter shephered, through the process documented in the "chartering" column 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.
-First, W3M chooses a Team Contact to manage the group creation -process.
- -The Process Document includes a section on The Process Document includes a section on Working Group and Interest Group Charter Development, which includes a requirement to alert the Advisory Committee when work begins on a @@ -109,7 +117,7 @@
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 @@ -121,15 +129,12 @@
Note: 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 list -of charter requirements to ensure that your charter is complete -(e.g., it includes a duration for the group).
- -Timeline: For existing groups, this takes no time. For new groups, it may take one month or more for W3M - to start dedicating resources.
+Team Contacts and others proposing charters should start from the Charter Template, rather than copying + an existing Group charter, as the template reflects the latest guidance from Membership and the Director/W3M on common matters of structure.
+ + +The Team Contact works with the Strategy Lead to +
The Team Contact or shepherd works with the Strategy Team and interested community participants to draft a provisional charter. See the Charter template and W3C Process Document for the list of charter requirements. 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.
Timeline: due to the discussion needing to happen with the community and the need @@ -329,15 +333,10 @@
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 +
When the Charter is brought to W3M, the Team Contact should note the horizontal review status in the Pipeline. +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.
+report this to W3M.