- From: Wayne Carr <wayne.carr@linux.intel.com>
- Date: Sat, 28 Mar 2015 16:42:16 -0700
- To: "public-council@w3.org" <public-council@w3.org>
Received on Saturday, 28 March 2015 23:42:44 UTC
Community Groups choose their own Charter. The template attached to this provides one approach. Template for Community Group - potentially large number of specs and easy to add specs Intended for Community Groups that have vague scope or don't know yet what the scope and deliverables are. Makes it easier to join a loosely specified Community Group like this because patent licensing happens only for specifications that a participant opts-in to work on. Those decisions don't have to be made before joining. 1a. Deliverables can be added to easily and scope can be broadly defined. 1b. CG Charter written/modified by Working Group. 1c. To provide protection against unintended contribution in a group with potentially many specs, 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:42:44 UTC