"Fossies" - the Fresh Open Source Software Archive 
Source code changes of the file "doc/source/contributor/contributing.rst" between
openstack-cyborg-6.0.0.tar.gz and openstack-cyborg-7.0.0.tar.gz
About: OpenStack Cyborg provides a general purpose management framework for acceleration resources. The "Xena" series (latest release).
| contributing.rst (openstack-cyborg-6.0.0) | : | contributing.rst (openstack-cyborg-7.0.0) | ||
|---|---|---|---|---|
| skipping to change at line 17 | skipping to change at line 17 | |||
| It covers all the basics that are common to all OpenStack projects: the | 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, | accounts you need, the basics of interacting with our Gerrit review system, | |||
| how we communicate as a community, etc. | how we communicate as a community, etc. | |||
| Below will cover the more project specific information you need to get started | Below will cover the more project specific information you need to get started | |||
| with {{cookiecutter.service}}. | with {{cookiecutter.service}}. | |||
| Communication | Communication | |||
| ~~~~~~~~~~~~~ | ~~~~~~~~~~~~~ | |||
| We use the #openstack-cyborg IRC channel. | We use the #openstack-cyborg channel on the OFTC IRC network. | |||
| The weekly meetings happen in this channel. You can find the meeting times, | The weekly meetings happen in this channel. You can find the meeting times, | |||
| previous meeting logs and proposed meeting agendas at | previous meeting logs and proposed meeting agendas at | |||
| `Cyborg Team Meeting Page | `Cyborg Team Meeting Page | |||
| <https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting>`_. | <https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting>`_. | |||
| Contacting the Core Team | Contacting the Core Team | |||
| ~~~~~~~~~~~~~~~~~~~~~~~~ | ~~~~~~~~~~~~~~~~~~~~~~~~ | |||
| The core reviewers of Cyborg and their emails are listed in | The core reviewers of Cyborg and their emails are listed in | |||
| `Cyborg core team <https://review.opendev.org/#/admin/groups/1243,members>`_. | `Cyborg core team <https://review.opendev.org/#/admin/groups/1243,members>`_. | |||
| New Feature Planning | New Feature Planning | |||
| ~~~~~~~~~~~~~~~~~~~~ | ~~~~~~~~~~~~~~~~~~~~ | |||
| To propose or plan new features, we add a new story in the | To propose or plan new features, we add a new story in the | |||
| `Cyborg Storyboard | `Cyborg Launchpad | |||
| <https://storyboard.openstack.org/#!/project/openstack/cyborg>`_ | <https://blueprints.launchpad.net/openstack-cyborg>`_ | |||
| and/or propose a specification in the | and/or propose a specification in the | |||
| `cyborg-specs <https://opendev.org/openstack/cyborg-specs>`_ repository. | `cyborg-specs <https://opendev.org/openstack/cyborg-specs>`_ repository. | |||
| Task Tracking | Task Tracking | |||
| ~~~~~~~~~~~~~ | ~~~~~~~~~~~~~ | |||
| We track our tasks in the `Cyborg Storyboard | We track our tasks in the `Launchpad <https://bugs.launchpad.net/openstack-cybor | |||
| <https://storyboard.openstack.org/#!/project/openstack/cyborg>`_. | g>`_. | |||
| If you're looking for some smaller, easier work item to pick up and get started | If you're looking for some smaller, easier work item to pick up and get started | |||
| on, ask in the IRC meeting. | on, ask in the IRC meeting. | |||
| Reporting a Bug | Reporting a Bug | |||
| ~~~~~~~~~~~~~~~ | ~~~~~~~~~~~~~~~ | |||
| You found an issue and want to make sure we are aware of it? You can do so | You found an issue and want to make sure we are aware of it? You can do so on | |||
| by adding an entry in the `Cyborg Storyboard | `Launchpad <https://bugs.launchpad.net/openstack-cyborg/+filebug>`__. | |||
| <https://storyboard.openstack.org/#!/project/openstack/cyborg>`_ or raising | More info about Launchpad usage can be found on `OpenStack docs page | |||
| it in the IRC meeting. | <https://docs.openstack.org/contributors/common/task-tracking.html#launchpad>`_. | |||
| Getting Your Patch Merged | Getting Your Patch Merged | |||
| ~~~~~~~~~~~~~~~~~~~~~~~~~ | ~~~~~~~~~~~~~~~~~~~~~~~~~ | |||
| To merge a patch, it must pass all voting Zuul checks and get two +2s from | To merge a patch, it must pass all voting Zuul checks and get two +2s from | |||
| core reviewers. We strive to avoid scenarios where one person from a company | core reviewers. We strive to avoid scenarios where one person from a company | |||
| or organization proposes a patch, and two other core reviewers from the | or organization proposes a patch, and two other core reviewers from the | |||
| same organization approve it to get it merged. In other words, at least | same organization approve it to get it merged. In other words, at least | |||
| one among the patch author and the two approving reviwers must be from | one among the patch author and the two approving reviwers must be from | |||
| another organization. | another organization. | |||
| End of changes. 4 change blocks. | ||||
| 9 lines changed or deleted | 9 lines changed or added | |||