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

An update is attached.  We're using a related template for a Community 
Group and there have been significant improvements in it related to use 
of GitHub.

Here is where the latest versions are:
http://wcarr.github.io/cg-charter/

and I'll attach the updated version here as well and here is the URL
https://wcarr.github.io/cg-charter/W3CWGAffiliatedCGCharterl20150331.html



On 2015-03-28 16:40, Wayne Carr wrote:
>
> 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
>
>