openstack/neutron
Code Issues Proposed changes

Fixed Typo in contribute.rst

Browse Source 
Replaced '.' with ':'

Change-Id: I1c0b9233b4c06989e3fea9c4462c7f417d9ebfc1
This commit is contained in:
Anindita Das 2016-07-06 04:14:57 +00:00
parent 77cdddb055
commit 88bd2be57a
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/source/devref/contribute.rst
View File

@ -118,7 +118,7 @@ Design documents can still be supplied in form of Restructured Text (RST)
documents, within the same third-party library repo. If changes to the common documents, within the same third-party library repo. If changes to the common
Neutron code are required, an `RFE Neutron code are required, an `RFE
<http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements>`_ <http://docs.openstack.org/developer/neutron/policies/blueprints.html#neutron-request-for-feature-enhancements>`_
may need to be filed. However every case is different and you are invited to may need to be filed. However, every case is different and you are invited to
seek guidance from Neutron core reviewers about what steps to follow. seek guidance from Neutron core reviewers about what steps to follow.
@ -126,7 +126,7 @@ Testing and Continuous Integration
---------------------------------- ----------------------------------
The following strategies are recommendations only, since third-party CI testing The following strategies are recommendations only, since third-party CI testing
is not a enforced requirement. However, these strategies are employed by the is not an enforced requirement. However, these strategies are employed by the
majority of the plugin/driver contributors that actively participate in the majority of the plugin/driver contributors that actively participate in the
Neutron development community, since they have learned from experience how Neutron development community, since they have learned from experience how
quickly their code can fall out of sync with the rapidly changing Neutron core quickly their code can fall out of sync with the rapidly changing Neutron core
@ -188,7 +188,7 @@ reused by any project-team when needed.
The OpenStack VMT directly oversees vulnerability reporting and disclosure for The OpenStack VMT directly oversees vulnerability reporting and disclosure for
a `subset of OpenStack source code repositories a `subset of OpenStack source code repositories
<https://wiki.openstack.org/wiki/Security_supported_projects>`_. However they <https://wiki.openstack.org/wiki/Security_supported_projects>`_. However, they
are still quite happy to answer any questions you might have about are still quite happy to answer any questions you might have about
vulnerability management for your own projects even if they're not part of that vulnerability management for your own projects even if they're not part of that
set. Feel free to reach out to the VMT in public or in private. set. Feel free to reach out to the VMT in public or in private.
@ -202,7 +202,7 @@ help with security-related issues (vulnerabilities or otherwise).
- Does a CVE need to be filed? - Does a CVE need to be filed?
It can vary widely. If a commercial distribution such as Red Hat is It can vary widely. If a commercial distribution such as Red Hat is
redistributing a vulnerable version of your software then they may assign one redistributing a vulnerable version of your software, then they may assign one
anyway even if you don't request one yourself. Or the reporter may request one; anyway even if you don't request one yourself. Or the reporter may request one;
the reporter may even be affiliated with an organization who has already the reporter may even be affiliated with an organization who has already
assigned/obtained a CVE before they initiate contact with you. assigned/obtained a CVE before they initiate contact with you.
@ -329,7 +329,7 @@ Internationalization (I18n) is one of important areas to make OpenStack ubiquito
Each project is recommended to support i18n. Each project is recommended to support i18n.
This section describes how to set up translation support. This section describes how to set up translation support.
The description in this section uses the following variables. The description in this section uses the following variables:
* repository : ``openstack/${REPOSITORY}`` (e.g., ``openstack/networking-foo``) * repository : ``openstack/${REPOSITORY}`` (e.g., ``openstack/networking-foo``)
* top level python path : ``${MODULE_NAME}`` (e.g., ``networking_foo``) * top level python path : ``${MODULE_NAME}`` (e.g., ``networking_foo``)