44efc50ac5
* In response to openstack-dev ML thread at http://lists.openstack.org/pipermail/openstack-dev/2016-December/109294.html * Proof-of-concept that we would get both a GitHub UI addition of a linked CONTRIBUTING file as well as a Sphinx include directive in the more detailed contributor guide. Change-Id: Ibe4c46faa25697eac4819d8ff1b2722fe58f23bf
38 lines
1.4 KiB
ReStructuredText
38 lines
1.4 KiB
ReStructuredText
=================
|
|
How to contribute
|
|
=================
|
|
|
|
Our community welcomes all people interested in open source cloud
|
|
computing, and encourages you to join the `OpenStack Foundation
|
|
<https://www.openstack.org/join>`_.
|
|
|
|
The best way to get involved with the community is to talk with others
|
|
online or at a meet up and offer contributions through our processes,
|
|
the `OpenStack wiki <https://wiki.openstack.org>`_, blogs, or on IRC at
|
|
``#openstack`` on ``irc.freenode.net``.
|
|
|
|
We welcome all types of contributions, from blueprint designs to
|
|
documentation to testing to deployment scripts.
|
|
|
|
If you would like to contribute to the documents, please see the
|
|
`OpenStack Documentation Contributor Guide
|
|
<http://docs.openstack.org/contributor-guide/>`_.
|
|
|
|
If you would like to contribute to the development of OpenStack, you must
|
|
follow the steps in this page:
|
|
|
|
http://docs.openstack.org/infra/manual/developers.html
|
|
|
|
If you already have a good understanding of how the system works and your
|
|
OpenStack accounts are set up, you can skip to the development workflow
|
|
section of this documentation to learn how changes to OpenStack should be
|
|
submitted for review via the Gerrit tool:
|
|
|
|
http://docs.openstack.org/infra/manual/developers.html#development-workflow
|
|
|
|
Pull requests submitted through GitHub will be ignored.
|
|
|
|
Bugs should be filed on Launchpad, not GitHub:
|
|
|
|
https://bugs.launchpad.net/openstack-manuals
|