openstack/ironic
Code Issues Proposed changes

Merge "Add 'How to get a decision on something' to FAQ"

Browse Source
This commit is contained in:
Jenkins 2016-06-08 11:52:20 +00:00 committed by Gerrit Code Review
commit 1678c9f0e8
1 changed files with 44 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
doc/source/dev/faq.rst
View File

@ -63,3 +63,47 @@ Then edit the result file.
For more information see the `reno documentation`_. For more information see the `reno documentation`_.
.. _`reno documentation`: http://docs.openstack.org/developer/reno/usage.html .. _`reno documentation`: http://docs.openstack.org/developer/reno/usage.html
...get a decision on something?
-------------------------------
You have an issue and would like a decision to be made. First, make sure
that the issue hasn't already been addressed, by looking at documentation,
bugs, specifications, or asking. Information and links can be found on the
`Ironic wiki`_ page.
There are several ways to solicit comments and opinions:
* bringing it up at the `weekly Ironic meeting`_
* bringing it up on IRC_
* bringing it up on the `mailing list`_ (add "[Ironic]" to the Subject of the
email)
If there are enough core folks at the weekly meeting, after discussing an
issue, voting could happen and a decision could be made.
The problem with IRC or the weekly meeting is that feedback will only
come from the people that are actually present.
To inform (and solicit feedback from) more people about an issue,
the preferred process is:
#. bring it up on the mailing list
#. after some period of time has elapsed (and depending on the
thread activity), someone should propose a solution via gerrit.
(E.g. the person that started the thread if no one else steps up.)
The proposal should be made in the the git repository that is associated
with the issue. (For instance, this decision process was proposed as a
documentation patch to the ironic repository.)
#. In the email thread, don't forget to provide a link to the proposed patch!
#. The discussion then moves to the proposed patch. If this is a big
decision, we could declare that some percentage of the cores should
vote on it before landing it.
(This process was suggested in an email thread about
`process for making decisions`_.)
.. _Ironic wiki: https://wiki.openstack.org/wiki/Ironic
.. _weekly Ironic meeting: https://wiki.openstack.org/wiki/Meetings/Ironic
.. _IRC: https://wiki.openstack.org/wiki/Ironic#IRC
.. _mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.. _process for making decisions: http://lists.openstack.org/pipermail/openstack-dev/2016-May/095460.html