The StarlingX project decided to move the gerritbot notifications into
a dedicated IRC channel. This change applies that change to the config
files.
Change-Id: I74b82bfdd4497d4f61126c07e1045e316bbc798a
Signed-off-by: Ildiko Vancsa <ildiko.vancsa@gmail.com>
Adds a few more tripleo-ci team members as channel ops. Removes
weshay and sshnaidm as they moved on from the team.
Change-Id: I737bb193494b57a93e07ff64ae1e4dd2d62202d8
In order to help drive the ptgbot during the PTG event, give
ttx OP rights on #openinfra-events channel.
Change-Id: I6afb3c1ea67fce8c9f9d58295e3a393d1b35c6ea
I might be able to help with few things on IRC,
especially ono OpenStack channels for project
additions/retirements work on IRC, topic change etc.
Change-Id: I72fc732771f6c4dc6c35a76afba760c3c553c07e
We are retiring the #openstack-state-management channel in favor
of consolidating the discussion to the #openstack-oslo channel[1].
This patch removes openstack-state-management from gerritbot and
accessbot.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/022929.html
Change-Id: Ic7aee1df77510e1421d9b42fcd3f950da987a1c4
This reverts commit 68c091e744, except
for #rdo and #puppet-openstack (fixed in parent changes) and
channel is no longer needed so removed statusbot configuration for
it with change I47613e4d88f358db5c51f9cb21c1eb1c2ebd32ed).
Merge once passing project-config-irc-access job indicates access is
sufficient for these channels.
Change-Id: Icced679f6a3f2882e61c6c558357c1f0b3332dce
The individual who registered #puppet-openstack on OFTC has added
master access for our opendevaccess accessbot account, so we can add
that channel back to our configuration now.
This partially reverts commit 68c091e744.
Change-Id: Ia63ef1a8e79c587115c49d5199b9085691f4db11
The folks who registered #rdo on OFTC have added master access for
our opendevaccess accessbot account, so we can add that channel back
to our configuration now.
This partially reverts commit 68c091e744.
Change-Id: Iafdfe7d8e8e81efc4e6f1377d15ee2c3e1d7668d
According to OFTC docs [1]:
s - secret, channel will not show up in /whois unless clients
share the channel
It seems to be used by the Debian community and may prevent some
spam and increase users' privacy.
[1] https://www.oftc.net/ChannelModes/
Change-Id: I2314ec884409c0db0d6ef2590bdf8426f1033c4a
I'm so seldom nowadays on IRC that I don't need those rights anymore,
remove myself and add to alumni list.
Another change removed me, so just add to alumni list.
Change-Id: Ia96bac1019b7f5524a8ca858a80f0feec80c0b07
Show how to go about adding admins or ops to a channel, as well as
doing channel-specific mode overrides.
Change-Id: I591c5467c94598c220292693bcb674e4f9d23c28
Make some adjustments to the IRC access check script so that it
works in the OFTC network now. Also update the channel config to
reflect the new ACL paradigms there. Remove our volunteer operators
temporarily until we can confirm their nicks there. Also rip out the
channel forwarding for unregistered nicks, we can work on readding
it there later if we determine it's necessary after all, but it will
need implementing differently anyway if so.
Change-Id: Ib3c43ef5ba22191d869629cd01d3800f3e235ea4
In preparation to switch to setting additional channel permissions
on OFTC, drop any from our config where we don't currently provide
bot services on Freenode. In basically all cases these are retired
or otherwise abandoned channels which we continued to maintain
registrations on to prevent confusion from someone re-registering
one after deletion. We're not maintaining registrations on OFTC for
channels we know nobody is going to use, so clean them up prior to a
mass migration.
Change-Id: I6f277148641e88a974187ed48e0c04a9e1258851
Depends-On: https://review.opendev.org/792302
The four channels removed in this change are registered on OFTC but
have no permissions for our opendevaccess service account. We can
readd them as soon as their current owners grant access to us.
Change-Id: I744b15b469f1b3b31d45d03cb84de68f5446ba64
The #ara channel no longer grants founder access to the
openstackinfra bot account, so we should not continue to operate our
bots in it.
Change-Id: Ic323a436bfc057a919ece48f578f6626f87ae03c
Depends-on: https://review.opendev.org/787891
Several foundation channels have moved to new names and the old ones
have been set private to ensure new joins get correctly forwarded.
Unfortunately this means that our check access script is unable to
correctly determine permissions as it does not use a privileged
account and instead receives an access denied error from ChanServ
when trying to perform an access list call on each of them. Remove
these channels so we'll stop blocking merge of unrelated changes in
this repository.
Also take gerritbot out of #openstack-ptg so accessbot won't insist
on it being listed.
Change-Id: I1730dc7c0cd02c5a4cf02486ab1e3d61f879e384
openstack-forum, openstack-ptg, openstack-summit and openinfra-summit
will now be openinfra-events.
openstack-diversity will now be openinfra-diversity.
openstack-foundation will now be openinfra.
openstack-board will come later after we can get op rights and
register the channel.
Change-Id: I4d09979e0c9dac75c7f3d878cde99cdc56b8dbe3
The Open Infrastructure Foundation is going to work on consolidating
its IRC channel names under a common namespace, #openinfra on
Freenode. Access has been granted to our bot account by the original
channel operators.
Change-Id: If407e4c4fa9d81c13577bac6240e02472a7fb6b2
This switches the Airship project's gerritbot config to use the
new #airshipit-gerritbot channel, instead of the #airshipit channel.
This will help make sure conversation doesn't get missed in #airshipit.
Change-Id: I105b2e34b89fd2b3f13277731e90413d00baf78b
As I am no longer infra-root, I no longer need access to accessbot.
Thanks all!
Change-Id: Ie724999ac914e965eec33368ad73f78570c6223b
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The openstack-infra-incident channel has traditionally (though
infrequently) been used as a venue for focusing on specific tasks
during emergency incidents, so that conversation doesn't get muddied
by other discussions occurring in the general channel. The OpenDev
collaborators are also in need of a brand-neutral channel where we
can conduct recurring IRC meetings, instead of continuing to rely on
the openstack-meeting channel. The two needs are actually similar,
and also incidents and meeting conversation will tend to not occur
at the same exact time (because if there's an incident underway
we'll be postponing the meeting, or actually meeting around the
incident, depending on how you look at it).
Change-Id: I56663ad0de2db297956c8a9ad36b005b52d20065