Difference between revisions of "Project Governance/Modules"

From Creative Commons
Jump to: navigation, search
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
<noinclude>
 
−
'''Do not edit this page''' unless either:
 
−
 
−
# 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
 
−
# you have agreed a change of owner or module addition/deletion with the Module Ownership Module group.
 
−
</noinclude>
 
−
 
 
{{Module
 
{{Module
 
|name=Governance
 
|name=Governance
Line 18: Line 8:
  
 
[http://www.mozilla.org/about/roles.html#ultimate-decision-makers Ultimate authority] within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.
 
[http://www.mozilla.org/about/roles.html#ultimate-decision-makers Ultimate authority] within the project rests with the owner and peer(s) of this module, and project decisions can be escalated to here.
−
|owner=[mailto:dan@creativecommons.org Dan Mills]
+
|owner=[mailto:ceo@creativecommons.org Management Committee]
 
|peers=
 
|peers=
−
|list=(to be created)
+
|glist=governance
 
|url=[[Governance]]
 
|url=[[Governance]]
 
}}
 
}}
Line 34: Line 24:
 
* Figuring out what to do if a module isn't getting enough attention
 
* Figuring out what to do if a module isn't getting enough attention
 
* Resolving conflicts among module owners  
 
* Resolving conflicts among module owners  
−
|owner=[mailto:dan@creativecommons.org Dan Mills]
+
|owner=[mailto:ceo@creativecommons.org Management Committee]
 
|peers=
 
|peers=
 
|url=[[Governance/Module_System]]
 
|url=[[Governance/Module_System]]
Line 40: Line 30:
  
 
{{Module
 
{{Module
−
|name=Contributor Agreement and Access Policy
+
|name=New Contributor and Access Policy
 
|description=Procedures for new contributors and for requesting and determining commit access.
 
|description=Procedures for new contributors and for requesting and determining commit access.
−
|owner=[mailto:dan@creativecommons.org Dan Mills]
+
|owner=[mailto:ceo@creativecommons.org Management Committee]
 
|peers=
 
|peers=
−
|url=[[Governance/New_Contributor]]
+
|url=[[Governance/New_Contributor_and_Access_Policy]]
 
}}
 
}}
  
Line 50: Line 40:
 
|name=Licensing 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.
 
|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.
−
|owner=[mailto:dan@creativecommons.org Dan Mills]
+
|owner=[mailto:ceo@creativecommons.org Management Committee]
 
|peers=
 
|peers=
 
|url=[[Governance/License_Policy]]
 
|url=[[Governance/License_Policy]]
 
}}
 
}}
 +
 +
{{ApprovedChangesOnly}}
 +
{{IncludesContentWithLicense|page=Modules/All}}

Latest revision as of 00:12, 28 February 2014

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 Management Committee
Content Owner {{{contentowner}}}
Peers
Mailing List {{{list}}}
Mailing List governance
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 Management Committee
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 Management Committee
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 Management Committee
Content Owner {{{contentowner}}}
Peers
Mailing List {{{list}}}
Mailing List {{{glist}}}
URL Governance/License_Policy
Do not edit this page unless you are confident you are allowed to do so. See this page for details.
{{{site}}}|wiki.mozilla.org}}{{#if:Modules/All|/Modules/All|}} {{#if:|{{{site}}}|wiki.mozilla.org}}{{#if:Modules/All|/Modules/All|}}], and is licensed under CC BY-SA 3.0.
Retrieved from "https://wiki.creativecommons.org/index.php?title=Project_Governance/Modules&oldid=97317"