W3C home > Mailing lists > Public > public-council@w3.org > March 2015

Template for Community Group Affiliated with a Working Group - potentially large number of specs and easy to add specs

From: Wayne Carr <wayne.carr@linux.intel.com>
Date: Sat, 28 Mar 2015 16:40:17 -0700
Message-ID: <55173BE1.2070106@linux.intel.com>
To: "public-council@w3.org" <public-council@w3.org>

Community Groups choose their own Charter. The template attached to this 
provides one approach.

Template forCommunity Group Affiliated with a Working Group - 
potentially large number of specs and easy to add specs

Goal: provide a place for a large Working Group like Web Apps or CSS to 
explore new areas of work, possibly outside their current scope.  This 
could be for incubation work, not yet ready for the WG, but in an area 
the WG is interested in for possible future work.

1a. Working Groups can pick up specifications from any Community Group. 
Affiliated Community Groups are different only in that a Working Group 
controls its charter and requests that it work on particular 
specifications, reports or code.  Working Group can ask the Affiliated 
Community Group to work on areas outside the Working Group scope to 
explore new areas, including incubator, exploratory specs.  Community 
Group volunteers decide whether to work on each spec.
1b. CG Charter written/modified by Working Group.
1c. To provide protection against unintended contribution in a group 
with potentially many specs and a scope that can expand, Community Group 
participants must opt-in to work on a particular spec (makes it easier 
to join CG)
1d. Community Group uses GitHub
1e. Fairness rules in Charter



Received on Saturday, 28 March 2015 23:40:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:16:38 UTC