Difference between revisions of "Project Governance/Modules"
| Line 1: | Line 1: | ||
{{ApprovedChangesOnly}} | {{ApprovedChangesOnly}} | ||
| − | |||
| − | |||
{{Module | {{Module | ||
Revision as of 22:42, 3 September 2013
| 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:
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 |
Governance Sub Modules
| Name | Module Ownership System (#) |
| Description | Healthy operation of the module ownership system, including topics such as:
|
| Technical }}Owner | Dan Mills |
| Name | New Contributor and Access Policy (#) |
| Description | Procedures for new contributors and for requesting and determining commit access. |
| Technical }}Owner | Dan Mills |
| 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 |