
The upstream docs structure is changing, so this change updates our existing docs into contributor and install guide sections. Change-Id: I37fabd25fdda6bc56fcfb331b74e3294e31e68bb
2.0 KiB
How to Contribute
source code is publicly available. You can contribute code to individual projects, documentation, report bugs and vulnerabilities, request features.
Contributing Code
As long as is a set of integrated OpenStack projects, all development is happening in OpenStack upstream.
Learn how to contribute into OpenStack's upstream <https://wiki.openstack.org/ wiki/How_To_Contribute>.
See ../install/introduction/components
to find out how to
contribute into individual projects.
Contributing to this Documentation
User Documentation lives on git.openstack.org and is mirrored on GitHub under the OpenStack organization.
Learn how to contribute into TripleO Docs.
Reporting Bugs
OpenStack Upstream: If you find bugs or vulnerabilities which affect upstream projects, please follow OpenStack's process of filing bugs.
- Learn how to report bugs in OpenStack.
- If you want to file a bug against upstream project, you can find
useful links in our list of
../install/introduction/components
.
TripleO If the bug impacts the project as a whole, you can file a bug in :
- Go to
- Fill in needed information (If you filed also upstream bug, please provide its URL in advanced fields)
- Submit bug
Requesting Features
OpenStack Upstream: Since we are developing projects in OpenStack community, all the features are being requested upstream via Blueprints.
- Learn how to create Blueprints in OpenStack.
- If you want to file a bug against upstream project, you can find
useful links in our list of
../install/introduction/components
.