Browse Source

Update mailinglist from dev to discuss

openstack-dev was decomissioned this night in https://review.openstack.org/621258
Update openstack-dev to openstack-discuss

Change-Id: I739ec6a4984df396b11b29f2d55f0d24fecab6eb
changes/21/621821/5
ZhongShengping 3 years ago
parent
commit
7d44666e8d
  1. 2
      README.rst
  2. 2
      doc/source/contributor/contribute.rst
  3. 2
      doc/source/contributor/policies/blueprints.rst
  4. 4
      doc/source/contributor/policies/bugs.rst
  5. 2
      doc/source/contributor/policies/contributor-onboarding.rst
  6. 2
      doc/source/contributor/policies/neutron-teams.rst
  7. 4
      doc/source/contributor/policies/thirdparty-ci.rst
  8. 2
      setup.cfg

2
README.rst

@ -17,7 +17,7 @@ To learn more about neutron:
* Defects: https://launchpad.net/neutron
* Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
Get in touch via `email <mailto:openstack-dev@lists.openstack.org>`_. Use
Get in touch via `email <mailto:openstack-discuss@lists.openstack.org>`_. Use
[Neutron] in your subject.
To learn how to contribute:

2
doc/source/contributor/contribute.rst

@ -174,7 +174,7 @@ Security Issues
~~~~~~~~~~~~~~~
Here are some answers to how to handle security issues in your repo, taken
from `this openstack-dev mailing list message
from `this mailing list message
<http://lists.openstack.org/pipermail/openstack-dev/2015-July/068617.html>`_:
- How should security your issues be managed?

2
doc/source/contributor/policies/blueprints.rst

@ -212,7 +212,7 @@ that depending on your level of engagement with the Neutron project and your rol
(user, developer, deployer, operator, etc.), you are more than welcome to have
a preliminary discussion of a potential RFE by reaching out to other people involved
in the project. This usually happens by posting mails on the relevant mailing
lists (e.g. `openstack-dev <http://lists.openstack.org>`_ - include [neutron] in
lists (e.g. `openstack-discuss <http://lists.openstack.org>`_ - include [neutron] in
the subject) or on #openstack-neutron IRC channel on Freenode. If current ongoing
code reviews are related to your feature, posting comments/questions on gerrit
may also be a way to engage. Some amount of interaction with Neutron developers

4
doc/source/contributor/policies/bugs.rst

@ -80,7 +80,7 @@ Finally, the PTL will work with the deputy to produce a brief summary of the
issues of the week to be shared with the larger team during the weekly IRC
meeting and tracked in the meeting notes. If for some reason the deputy is not
going to attend the team meeting to report, the deputy should consider sending
a brief report to the openstack-dev@ mailing list in advance of the meeting.
a brief report to the openstack-discuss@ mailing list in advance of the meeting.
Getting Ready to Serve as the Neutron Bug Deputy
@ -138,7 +138,7 @@ Bug Deputy routines in your week
If you can, do the same for older bugs.
* Take a note of bugs you processed.
At the end of your week, post a report on openstack-dev mailing list.
At the end of your week, post a report on openstack-discuss mailing list.
Plugin and Driver Repositories

2
doc/source/contributor/policies/contributor-onboarding.rst

@ -6,7 +6,7 @@ For new contributors, the following are useful onboarding information.
Contributing to Neutron
-----------------------
Work within Neutron is discussed on the openstack-dev mailing list, as well as in the
Work within Neutron is discussed on the openstack-discuss mailing list, as well as in the
#openstack-neutron IRC channel. While these are great channels for engaging Neutron,
the bulk of discussion of patches and code happens in gerrit itself.

2
doc/source/contributor/policies/neutron-teams.rst

@ -259,7 +259,7 @@ have.
Adding or Removing Core Reviewers
---------------------------------
A new Neutron core reviewer may be proposed at anytime on the openstack-dev
A new Neutron core reviewer may be proposed at anytime on the openstack-discuss
mailing list. Typically, the Lieutenant for a given area will propose a new
core reviewer for their specific area of coverage, though the Neutron PTL may
propose new core reviewers as well. The proposal is typically made after

4
doc/source/contributor/policies/thirdparty-ci.rst

@ -11,7 +11,7 @@ external plugins and drivers at any time.
Neutron expects any Third Party CI system that interacts with gerrit to
follow the requirements set by the Infrastructure team [1]_ as well as the
Neutron Third Party CI guidelines below. Please ping the PTL in
#openstack-neutron or send an email to the openstack-dev ML (with subject
#openstack-neutron or send an email to the openstack-discuss ML (with subject
[neutron]) with any questions. Be aware that the Infrastructure documentation
as well as this document are living documents and undergo changes. Track
changes to the infrastructure documentation using this url [2]_ (and please
@ -85,7 +85,7 @@ systems.
A third party system can have it's voting rights removed as well. If the
system becomes unstable (stops running, voting, or start providing inaccurate
results), the Neutron PTL or any core reviewer will make an attempt to contact
the owner and copy the openstack-dev mailing list. If no response is received
the owner and copy the openstack-discuss mailing list. If no response is received
within 2 days, the Neutron PTL will remove voting rights for the third party
CI system. If a response is received, the owner will work to correct the
issue. If the issue cannot be addressed in a reasonable amount of time, the

2
setup.cfg

@ -4,7 +4,7 @@ summary = OpenStack Networking
description-file =
README.rst
author = OpenStack
author-email = openstack-dev@lists.openstack.org
author-email = openstack-discuss@lists.openstack.org
home-page = https://docs.openstack.org/neutron/latest/
classifier =
Environment :: OpenStack

Loading…
Cancel
Save