Merge "Use openstack-discuss"

This commit is contained in:
Zuul 2018-11-19 15:12:03 +00:00 committed by Gerrit Code Review
commit 5756f60dca
7 changed files with 17 additions and 16 deletions

View File

@ -2,7 +2,7 @@
name = openstackdocumentationcontributorguide
summary = OpenStack Documentation Contributor Guide
author = OpenStack
author-email = openstack-dev@lists.openstack.org
author-email = openstack-discuss@lists.openstack.org
home-page = https://docs.openstack.org/
classifier =
Environment :: OpenStack

View File

@ -144,8 +144,8 @@ steps you will need to follow in order to be prepared.
volunteers to be bug deputy are requested.
Alternatively, use the #openstack-doc IRC channel or the
openstack-dev@lists.openstack.org mailing list to contact the documentation
core team members.
openstack-discuss@lists.openstack.org mailing list to contact the
documentation core team members.
#. Sign up as a volunteer by adding your name to the bug triaging schedule on the
`Bug Triage Team

View File

@ -194,7 +194,7 @@ The proposal job will update the patch with the next run.
If you cannot fix the problem, ask for help on the mailing lists:
* openstack-i18n@lists.openstack.org: translation failures
* openstack-dev@lists.openstack.org: requirements failures, glossary sync
* openstack-discuss@lists.openstack.org: requirements failures, glossary sync
failures, and common content sync failures.
Considerations for documentation aligned with release cycles

View File

@ -114,16 +114,17 @@ The process is:
* `openstack-manuals Stackalytics
<http://stackalytics.com/?module=openstack-manuals&metric=commits>`_
* The PTL then consults the existing core team and the OpenStack community
with a list of names to be removed from and added to the core list. This is
done in public by using the openstack-dev@lists.openstack.org mailing list
as the primary communication channel. Cores who are being removed will be
contacted personally before changes are made.
* The PTL then consults the existing core team and the OpenStack
community with a list of names to be removed from and added to the
core list. This is done in public by using the
openstack-discuss@lists.openstack.org mailing list as the primary
communication channel. Cores who are being removed will be contacted
personally before changes are made.
* Existing core team members can nominate a new core member at any time,
with a justification sent to the openstack-dev@lists.openstack.org mailing
list. Three +1 votes from other existing core team members must be achieved
for approval.
* Existing core team members can nominate a new core member at any
time, with a justification sent to the
openstack-discuss@lists.openstack.org mailing list. Three +1 votes
from other existing core team members must be achieved for approval.
Core reviewer responsibilities
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

View File

@ -2,7 +2,7 @@
name = openstackdocumentationglossary
summary = OpenStack Documentation Glossary
author = OpenStack
author-email = openstack-dev@lists.openstack.org
author-email = openstack-discuss@lists.openstack.org
home-page = https://docs.openstack.org/
classifier =
Environment :: OpenStack

View File

@ -2,7 +2,7 @@
name = openstackhaguide
summary = OpenStack High Availability Guide
author = OpenStack
author-email = openstack-dev@lists.openstack.org
author-email = openstack-discuss@lists.openstack.org
home-page = https://docs.openstack.org/
classifier =
Environment :: OpenStack

View File

@ -2,7 +2,7 @@
name = openstackinstallguide
summary = OpenStack Installation Guides
author = OpenStack
author-email = openstack-dev@lists.openstack.org
author-email = openstack-discuss@lists.openstack.org
home-page = http://docs.openstack.org/
classifier =
Environment :: OpenStack