4cff2ab6d5
With pbr 2.0 and Sphinx 1.5, the setting for treat sphinx warnings as errors is setting warning-is-error in build_sphinx section. Migrate the setting from the old warnerrors one. Fix problems found: * Duplicate labels (rename wrong faq entries, rename unused drivers entries) * Add api/autoindex.rst as hidden to the index so that we do not get a warning. The modindex includes the same content, so no need to show this. * Add releasenotes/index.rst, webapi/v1.rst, user-guide, and install-guide.rst to hidden index since they're not listed in index on purpose, so sphinx will not warn that they do not appear in a toc * Add deploy/radosgw to index * ignore app.add_directiv warning * Fix reference to user-guide to use proper markup so that Sphinx knows the user-guide is referenced. Change-Id: I00d249229d4d31ba36d4393d60847fdb1513a744
1.4 KiB
1.4 KiB
Ironic Governance Structure
The ironic project manages a number of repositories that contribute to our mission. The full list of repositories that ironic manages is available in the governance site.
What belongs in ironic governance?
For a repository to be part of the Ironic project:
- It must comply with the TC's rules for a new project.
- It must not be intended for use with only a single vendor's hardware. A library that implements a standard to manage hardware from multiple vendors (such as IPMI or redfish) is okay.
- It must align with Ironic's mission statement.
Lack of contributor diversity is a chicken-egg problem, and as such a repository where only a single company is contributing is okay, with the hope that other companies will contribute after joining the ironic project.
Repositories that are no longer maintained should be pruned from governance regularly.
Proposing a new project to ironic governance
Bring the proposal to the ironic weekly meeting to discuss with the team.