Infrastructure/infra-docs-fpo
1
0
Fork 0
Code Issues 100 Pull requests 6 Projects Releases Packages Wiki Activity Actions

Drop IRC and replace with matrix is all our docs.

Browse source 
Since we are moving to matrix, lets drop reference to irc.
I may have missed a few of these and I left the Zodbot SOP alone for now
until we replace it with the new matrix one.

Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This commit is contained in:
Kevin Fenzi 2023-12-20 11:15:46 -08:00
parent 7398ec55c8
commit cc6d4b0750
19 changed files with 54 additions and 86 deletions
Download patch file Download diff file Expand all files Collapse all files

2
modules/sysadmin_guide/pages/ansible.adoc
View file

@ -78,7 +78,7 @@ via git hooks:
*** A mail about the changes is sent to _sysadmin-members_.
*** The changes are announced on the message bus, which in turn triggers
announcements on IRC.
announcements on matrix.
You can check out the repo locally on _batcave01_ with:

4
modules/sysadmin_guide/pages/bugzilla2fedmsg.adoc
View file

@ -68,6 +68,4 @@ $ systemctl restart moksha-hub
== Internal Contacts
If we need to contact someone from the RH internal "unified messagebus"
team, search for "unified messagebus" in mojo. It is operated as a joint
project between RHIT and PnT Devops. See also the `#devops-message` IRC
channel, internally.
team, search for "unified messagebus" in source.

2
modules/sysadmin_guide/pages/fedmsg-new-message-type.adoc
View file

@ -50,7 +50,7 @@ the next playbook run.
At this point, you can push the change out to production and be
publishing messages "okay". Everything should be fine.
However, your message will show up blank in _datagrepper_, in IRC, and in
However, your message will show up blank in _datagrepper_, in matrix, and in
_FMN_, and everywhere else we try to render it. You _must_ then follow up
and write a new _Processor_ for it in the _fedmsg_meta_
library we maintain:

1
modules/sysadmin_guide/pages/fmn.adoc
View file

@ -14,7 +14,6 @@ irc.
____
* #fedora-apps for FMN development
* #fedora-fedmsg for an IRC feed of all fedmsgs
* #fedora-admin for problems with the deployment of FMN
* #fedora-noc for outage/crisis alerts
____

2
modules/sysadmin_guide/pages/gdpr_delete.adoc
View file

@ -48,7 +48,7 @@ FAS account to delete the required data. Update the `fedora-pdr` issue
saying the request has been received. There is a 'quick response' in the
pagure issue tracker to note this.
. Login to FAS and clear the `Telephone number` entry, set Country to
`Other`, clear `Lattitude` and `Longitude` and `IRC Nick` and
`Other`, clear `Lattitude` and `Longitude` and `Matrix` and
`GPG Key ID` and set `Time Zone` to UTC and `Locale` to `en` and set the
user status to `disabled`. If the user is not in cla_done plus one
group, you are done. Update the ticket and close it. This step will be

17
modules/sysadmin_guide/pages/github.adoc
View file

@ -33,23 +33,6 @@ $ git clone GIT_URL
$ git checkout -b develop
$ git push --all
....
** Set up an IRC hook for notifications. From the `Settings` tab click
on `Webhooks & Services`. Under the `Add Service` dropdown, find `IRC`
and click it. You might need to enter your password. In the form, you
probably want the following values:
*** Server, irc.freenode.net
*** Port, 6697
*** Room, #fedora-apps
*** Nick, <nothing>
*** Branch Regexes, <nothing>
*** Password, <nothing>
*** Ssl, <on>
*** Message Without Join, <on>
*** No Colors, <off>
*** Long Url, <off>
*** Notice, <on>
*** Active, <on>
== Add an EasyFix label

2
modules/sysadmin_guide/pages/github2fedmsg.adoc
View file

@ -21,7 +21,7 @@ Purpose::
github2fedmsg is a small Python Pyramid app that bridges github events
onto our fedmsg bus by way of github's "webhooks" feature. It is what
allows us to have IRC notifications of github activity via fedmsg. It
allows us to have notifications of github activity via fedmsg. It
has two phases of operation:
* Infrequently, a user will log in to github2fedmsg via Fedora OpenID.

6
modules/sysadmin_guide/pages/mote.adoc
View file

@ -1,7 +1,7 @@
= mote SOP
mote is a MeetBot log wrangler, providing an user-friendly interface for
viewing logs produced by Fedora's IRC meetings.
viewing logs produced by Fedora's matrix meetings.
Production instance: http://meetbot.fedoraproject.org/ Staging instance:
http://meetbot.stg.fedoraproject.org
@ -26,7 +26,7 @@ Contact::
Location::
Fedora Infrastructure
Purpose::
IRC meeting coordination
matrix meeting coordination
== Deployment
@ -57,7 +57,7 @@ sudo rbac-playbook manual/upgrade/mote.yml
mote is a Python webapp running on Flask with mod_wsgi. It can be used
to view past logs, browse meeting minutes, or glean other information
relevant to Fedora's IRC meetings. It employs a JSON file store cache,
relevant to Fedora's matrix meetings. It employs a JSON file store cache,
in addition to a memcached store which is currently not in use with
Fedora infrastructure.

2
modules/sysadmin_guide/pages/orientation.adoc
View file

@ -54,7 +54,7 @@ The team itself is generally friendly and honest. Don't be afraid to
disagree with someone, even if you're new and they're an old timer. Just
make sure you ask yourself what is important to you and make sure to
provide data, we like that. We generally communicate on libera.chat
in #fedora-admin. We have our weekly meetings on IRC and its the
in #fedora-admin. We have our weekly meetings on matrix and its the
quickest way to get in touch with everyone. Secondary to that we use the
mailing list. After that it's our ticketing system and
talk.fedoraproject.org.

2
modules/sysadmin_guide/pages/outage.adoc
View file

@ -149,7 +149,7 @@ http://status.fedoraproject.org please push an update to reflect the
outage (see xref:status-fedora.adoc[status-fedora SOP]).
Report all information in #fedora-admin. Coordination is extremely
important, it's rare for our group to meet in person and IRC is our only
important, it's rare for our group to meet in person and matrix is our only
real-time communication device. If a web site is out please put up some
sort of outage page in its place.

2
modules/sysadmin_guide/pages/requestforresources.adoc
View file

@ -58,7 +58,7 @@ infrastructure sysadmin-main group.
Once a sponsor is aquired and all needed packages have been packaged and
are available in EPEL, we move on to the planning phase. In this phase
discussion should take place about the application/resource on the
infrastructure list and IRC. Questions about how the resource could be
infrastructure list and matrix. Questions about how the resource could be
deployed should be considered:
* Should the resource be load balanced?