Project Governance/Modules

Do not edit this page unless you are confident you are allowed to do so. See this page for details.

Name	Governance ^(#)
Description	Policies and process for how we distribute authority and govern ourselves; including: Development and Implementation of new policies as appropriate for delegation of authority and responsibility Management of the source tree Balancing different constituencies of the project Maintaining the CC identity as we take on new activities Ultimate authority within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.
Technical }}Owner	Dan Mills
Content Owner	{{{contentowner}}}
Peers
Mailing List	{{{list}}}
Mailing List	governance
URL	Governance

Name	Module Ownership System ^(#)
Description	Healthy operation of the module ownership system, including topics such as: Filling vacant roles where appropriate Ensuring module owners are fulfilling their responsibilities, and replacing those who are not Creating and staffing new modules where new parts of the project evolve. Figuring out what to do if a module isn't getting enough attention Resolving conflicts among module owners
Technical }}Owner	Dan Mills
Content Owner	{{{contentowner}}}
Peers
Mailing List	{{{list}}}
Mailing List	{{{glist}}}
URL	Governance/Module_System

Name	New Contributor and Access Policy ^(#)
Description	Procedures for new contributors and for requesting and determining commit access.
Technical }}Owner	Dan Mills
Content Owner	{{{contentowner}}}
Peers
Mailing List	{{{list}}}
Mailing List	{{{glist}}}
URL	Governance/New_Contributor_and_Access_Policy

Name	Licensing Policy ^(#)
Description	Policies for deciding how contributors should license code and content created for the project, as well as for determining whether 3rd-party code or content may be imported or used.
Technical }}Owner	Dan Mills
Content Owner	{{{contentowner}}}
Peers
Mailing List	{{{list}}}
Mailing List	{{{glist}}}
URL	Governance/License_Policy

Navigation menu