Move channel reg requirement to top of IRC docs

We require channels to be registered and have the openstackinfra
account added to the access list before we'll add infra-managed
bots.

Moving this documentation to the beginning of the document and
giving them their own section in case we wish to have other
requirements in the future.

Also add link on stackforge.rst back to the IRC page.

Change-Id: Ic92f3935de19c4afef23f51257a189f2860796c2
This commit is contained in:
Elizabeth Krumbach Joseph 2014-03-18 08:02:25 -07:00
parent 56fa804c10
commit 49f3ba50e0
2 changed files with 23 additions and 4 deletions

View File

@ -32,6 +32,26 @@ At a Glance
:Bugs:
* http://bugs.launchpad.net/openstack-ci
Channel Requirements
====================
In general, discussion for OpenStack projects is preferred in #openstack-dev,
but there are many reasons why a team would like to have their own channel.
Access
------
Register the channel with ChanServ and give the infrastructure team account
founder access to the channel with::
/msg chanserv access #channel add openstackinfra +AFRfiorstv
This is good practice project-wide to make sure we keep channels under
control and is a requirement if you want any of the project bots in
your channel.
Join #openstack-infra if you have any trouble with any of these commands.
Meetbot
=======
@ -163,7 +183,3 @@ Gerritbot's configuration is in
Teams can add their channel and go through the standard code review process to
get the bot added to their channel. The configuration is organized by channel,
with each project that a channel is interested in listed under the channel.
Please also add the openstackinfra account as a channel founder:
/msg chanserv access #channel add openstackinfra +AFRfiorstv

View File

@ -226,6 +226,9 @@ end of this file that looks like::
branches:
- master
For more information about channel requirements and IRC services provided by
the infrasructure team, visit :ref:`irc`
And thats it. At this point you will want to submit these edits as a
change to review.openstack.org. When you do so, please use the
``new-project`` topic. You can do that using the ``-t`` option to