1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
============================
So You Want to Contribute...
============================
For general information on contributing to OpenStack, please check out the
`contributor guide <https://docs.openstack.org/contributors/>`_ to get started.
It covers all the basics that are common to all OpenStack projects: the accounts
you need, the basics of interacting with our Gerrit review system, how we
communicate as a community, etc.
Below will cover the more project specific information you need to get started
with Reno.
Communication
~~~~~~~~~~~~~
* IRC channel #openstack-release at OFTC
* Mailing list (prefix subjects with ``[release]`` for faster responses)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss
Contacting the Core Team
~~~~~~~~~~~~~~~~~~~~~~~~
Please refer the `reno Core Team
<https://review.opendev.org/admin/groups/82d77855547a7c8c68f67a527d94bcf276effa65,members>`_ contacts.
New Feature Planning
~~~~~~~~~~~~~~~~~~~~
reno features are tracked on `Storyboard <https://storyboard.openstack.org/#!/project/933>`_.
Task Tracking
~~~~~~~~~~~~~
We track our tasks in `Storyboard <https://storyboard.openstack.org/#!/project/933>`_.
If you're looking for some smaller, easier work item to pick up and get started
on, search for the 'low-hanging-fruit' tag.
Reporting a Bug
~~~~~~~~~~~~~~~
You found an issue and want to make sure we are aware of it? You can do so on
`Storyboard <https://storyboard.openstack.org/#!/project/933>`_.
Getting Your Patch Merged
~~~~~~~~~~~~~~~~~~~~~~~~~
All changes proposed to the reno project require one or two +2 votes
from reno core reviewers before one of the core reviewers can approve
patch by giving ``Workflow +1`` vote.
|
