Difference between revisions of "Project Governance/Modules"

From Creative Commons
Jump to: navigation, search
Line 21: Line 21:
 
|peers=
 
|peers=
 
|list=(to be created)
 
|list=(to be created)
|url=https://wiki.creativecommons.org/Governance
+
|url=[[Governance]]
 
}}
 
}}
  
Line 36: Line 36:
 
|owner=[mailto:dan@creativecommons.org Dan Mills]
 
|owner=[mailto:dan@creativecommons.org Dan Mills]
 
|peers=
 
|peers=
 +
|url=[[Governance/Module_System]]
 
}}
 
}}
  
Line 43: Line 44:
 
|owner=[mailto:dan@creativecommons.org Dan Mills]
 
|owner=[mailto:dan@creativecommons.org Dan Mills]
 
|peers=
 
|peers=
 +
|url=[[Governance/New_Contributor]]
 
}}
 
}}
  
Line 50: Line 52:
 
|owner=[mailto:dan@creativecommons.org Dan Mills]
 
|owner=[mailto:dan@creativecommons.org Dan Mills]
 
|peers=
 
|peers=
 +
|url=[[Governance/License_Policy]]
 
}}
 
}}

Revision as of 00:57, 2 September 2013

Do not edit this page unless either:

  1. you are a module owner who is:
    • altering the list of peers in your module
    • adding or removing a sub-module
    • changing the owner of one of your sub-modules; or
  2. you have agreed a change of owner or module addition/deletion with the Module Ownership Module group.


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 (to be created)
Mailing List {{{glist}}}
URL Governance

Governance Sub Modules

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 Contributor Agreement 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
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