Browse Source

Update irc server references in docs to new network

Change-Id: I8f166a8de280bff82230af28bff5d487b5ce76ce
changes/24/793824/1
Marios Andreou 2 months ago
parent
commit
5572f587b6
  1. 2
      doc/source/ci/ci_primer.rst
  2. 8
      doc/source/ci/ruck_rover_primer.rst
  3. 2
      doc/source/contributor/new_developers.rst

2
doc/source/ci/ci_primer.rst

@ -153,7 +153,7 @@ Contacting CI team
------------------
When in need you can contact the TripleO CI team members on one of the two
irc channels on freenode #tripleo by mentioning ``@oooq`` keyword in your
irc channels on OFTC #tripleo by mentioning ``@oooq`` keyword in your
message as team members get notified about such messages. It is good to
remember that those nicknames with ``|ruck`` and ``|rover`` suffix are on duty
to look for CI status.

8
doc/source/ci/ruck_rover_primer.rst

@ -3,7 +3,7 @@ TripleO CI ruck|rover primer
The tripleo-squad divides their work across 3 week sprints. During sprint
planning 2 members of the team are nominated as the 'ruck' and 'rover'.
You can easily identify these unfortunate souls in freenode #oooq with "ruck" or
You can easily identify these unfortunate souls in OFTC #oooq with "ruck" or
"rover" in their irc nick.
In short the "ruck" and "rover" are tasked with keeping the lights on for a
@ -45,7 +45,7 @@ appropriate tag(s):
* ci: a general tag for all ci related bugs - any bug about a failing CI job
should have this.
* alert: critical bugs e.g. something that affects a great number of jobs. This
tag causes the bug to be advertised in irc freenode #tripleo.
tag causes the bug to be advertised in irc OFTC #tripleo.
* tempest: bug is tempest related - failing tests or other tempest related error.
* ci-reproducer: related to the `zuul based job reproducer`_
* promotion-blocker: this is used when the failing job(s) is in the promotion
@ -90,7 +90,7 @@ through to simply harrassing the 'right folks' ;) in the relevant `TripleO Squad
In other cases bugs may be deprioritized - for example if the job is non voting
or is not in the promotion criteria then any related bugs are less likely to
be getting the rover's attention. If you are interested in such jobs or bugs
then you should go to #freenode oooq channel and find the folks with "ruck" or
then you should go to #OFTC oooq channel and find the folks with "ruck" or
"rover" in their nick and harrass them about it!
Of course for other cases there are bona fide bugs with the `TripleO CI code`_
@ -120,7 +120,7 @@ any ongoing issues actively being worked on. Besides allowing coordination
between ruck and rover themselves (the TripleO CI team is distributed across
a number of time zones) one other use case is to allow tripleo-devs to check
if the reason a particular job is failing on their code review is 'known' or if
they need to go harrass the ruck|rover about it in freenode #oooq. The location
they need to go harrass the ruck|rover about it in OFTC #oooq. The location
of the current ruck|rover etherpad is given in grafana (see below).
Sova

2
doc/source/contributor/new_developers.rst

@ -99,7 +99,7 @@ implementing a new feature.
- Documentation should be updated if necessary. New features need a
tripleo-docs patch.
- If any new dependencies are used for your feature, be sure they are properly
packaged and available in RDO. You can ask on #rdo (on freenode server) for
packaged and available in RDO. You can ask on #rdo (on OFTC server) for
help with this.

Loading…
Cancel
Save