Drop IRC and replace with matrix is all our docs.
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:
parent
7398ec55c8
commit
cc6d4b0750
19 changed files with 54 additions and 86 deletions
|
@ -69,14 +69,14 @@ there and close it or rework it as needed. You can add to the next meeting agend
|
||||||
Most any task will require changes to ansible. You can check this out on batcave01.iad2.fedoraproject.org
|
Most any task will require changes to ansible. You can check this out on batcave01.iad2.fedoraproject.org
|
||||||
(just "git clone /git/ansible" there) and make edits to your local copy. Then you can create a PR with your changes into link:https://pagure.io/fedora-infra/ansible[]
|
(just "git clone /git/ansible" there) and make edits to your local copy. Then you can create a PR with your changes into link:https://pagure.io/fedora-infra/ansible[]
|
||||||
|
|
||||||
== IRC/Matrix Tips
|
== Matrix Tips
|
||||||
|
|
||||||
The primary ways the infrastructure team communicates are IRC and Matrix. Here's a few tips to best communicate with the rest of the team:
|
The primary way the infrastructure team communicates is Matrix. Here's a few tips to best communicate with the rest of the team:
|
||||||
|
|
||||||
* Feel free to ask questions when you think of them/run into them, but don't expect everyone to drop what they are doing and answer right then.
|
* Feel free to ask questions when you think of them/run into them, but don't expect everyone to drop what they are doing and answer right then.
|
||||||
Please be patient.
|
Please be patient.
|
||||||
|
|
||||||
* Try to avoid private messages to specific team members. Instead ask your questions in #fedora-admin or #fedora-noc on IRC and
|
* Try to avoid private messages to specific team members. Instead ask your questions in
|
||||||
link:https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org[Fedora Infrastructure Team"] and link:https://chat.fedoraproject.org/#/room/#noc:fedoraproject.org["Fedora Network Operation Center"]
|
link:https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org[Fedora Infrastructure Team"] and link:https://chat.fedoraproject.org/#/room/#noc:fedoraproject.org["Fedora Network Operation Center"]
|
||||||
on Matrix if at all possible. This allows anyone to help you out and also other folks to see the answer and peer review the answers you get.
|
on Matrix if at all possible. This allows anyone to help you out and also other folks to see the answer and peer review the answers you get.
|
||||||
|
|
||||||
|
@ -85,23 +85,18 @@ behind it. "Have we considered switching from foo to bar?" is great, "Why are yo
|
||||||
is not.
|
is not.
|
||||||
|
|
||||||
* Keep in mind many of the infrastructure folks are busy, so do try and avoid 'pinging' them unless there's a specific need or you know they are
|
* Keep in mind many of the infrastructure folks are busy, so do try and avoid 'pinging' them unless there's a specific need or you know they are
|
||||||
active in channel. Many people have a IRC 'trigger' that notifies them when someone mentions their nick.
|
active in channel. Many people have a matrix 'trigger' that notifies them when someone mentions their nick.
|
||||||
|
|
||||||
* Being active in IRC/Matrix and asking questions is a great way to find out how things are setup and gain more trust.
|
* Being active in Matrix and asking questions is a great way to find out how things are setup and gain more trust.
|
||||||
|
|
||||||
* Watching discussion in IRC/Matrix can often lead to some topic or area you might be interested in helping out with.
|
* Watching discussion in Matrix can often lead to some topic or area you might be interested in helping out with.
|
||||||
If so, please feel free to chime in in channel that you would be interested in helping out and ask how you could
|
If so, please feel free to chime in in channel that you would be interested in helping out and ask how you could
|
||||||
do so.
|
do so.
|
||||||
|
|
||||||
* IRC channel #fedora-admin is bridged to link:https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org[Fedora Infrastructure Matrix room],
|
|
||||||
#fedora-apps is bridged to link:https://chat.fedoraproject.org/#/room/#apps:fedoraproject.org[Fedora Apps Matrix room]
|
|
||||||
and #fedora-nox is bridged to link:https://chat.fedoraproject.org/#/room/#noc:fedoraproject.org["Fedora Network Operation Center"].
|
|
||||||
These rooms belongs to the link:https://chat.fedoraproject.org[Fedora Matrix servers].
|
|
||||||
|
|
||||||
== Further information
|
== Further information
|
||||||
|
|
||||||
For further information on this group, please ask in #fedora-admin on irc.libera.chat, the
|
For further information on this group, please ask in #fedora-admin on irc.libera.chat, the
|
||||||
link:https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org[Fedora Infrastructure Matrix room] and/or
|
link:https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org[Fedora Infrastructure Matrix room] and/or
|
||||||
the fedora infrastructure xref:index.adoc#_mailing_list[mailing list].
|
the fedora infrastructure xref:index.adoc#_mailing_list[mailing list].
|
||||||
|
|
||||||
Ansible documentation is available at link:http://docs.ansible.com/[].
|
Ansible documentation is available at link:http://docs.ansible.com/[].
|
||||||
|
|
|
@ -1,7 +1,6 @@
|
||||||
= Working with Fedora Infrastructure
|
= Working with Fedora Infrastructure
|
||||||
|
|
||||||
This document explains how to efficiently work with the
|
This document explains how to efficiently work with the Fedora Infrastructure team.
|
||||||
Fedora Infrastructure team.
|
|
||||||
Your close attention to this document will help both you and us
|
Your close attention to this document will help both you and us
|
||||||
do the work you are asking us to do.
|
do the work you are asking us to do.
|
||||||
|
|
||||||
|
@ -18,10 +17,10 @@ Is your issue/problem urgent? (An important service is down, you need
|
||||||
a change asap) or is your issue/problem such that you cannot file a ticket
|
a change asap) or is your issue/problem such that you cannot file a ticket
|
||||||
(authentication, no account, ticketing system down)
|
(authentication, no account, ticketing system down)
|
||||||
|
|
||||||
* On IRC (irc.libera.chat) join the `#fedora-admin` channel, say _.oncall_,
|
* Login to a matrix account. join the #admin:fedoraproject.org channel.
|
||||||
and explain the issue to the oncall person.
|
say '!oncall' and explain the issue or problem to the oncall person.
|
||||||
|
|
||||||
* If no answer:
|
* If no one is available there:
|
||||||
** If you cannot authenticate to link:https://pagure.io/[], send an email
|
** If you cannot authenticate to link:https://pagure.io/[], send an email
|
||||||
to admin@fedoraproject.org
|
to admin@fedoraproject.org
|
||||||
** Otherwise: go to next step.
|
** Otherwise: go to next step.
|
||||||
|
@ -44,7 +43,7 @@ image::daily_process.png[750,750, link="../_images/daily_process.png"]
|
||||||
A few notes:
|
A few notes:
|
||||||
|
|
||||||
* Make sure to note if there is a deadline or if this issue blocks you.
|
* Make sure to note if there is a deadline or if this issue blocks you.
|
||||||
* We review tickets during the two stand ups we hold Monday through Friday
|
* We review tickets during the two stand ups we hold Monday through Thursday
|
||||||
(one more Europe timezone friendly and one more US timezone friendly).
|
(one more Europe timezone friendly and one more US timezone friendly).
|
||||||
* There is no need to ping team members or notify us about the newly filed
|
* There is no need to ping team members or notify us about the newly filed
|
||||||
ticket.
|
ticket.
|
||||||
|
@ -78,10 +77,9 @@ worked on:
|
||||||
|
|
||||||
== The "Oncall" Role in Our Team
|
== The "Oncall" Role in Our Team
|
||||||
|
|
||||||
One CPE team member is always designated “oncall”. The assigned person changes
|
One team member is always designated “oncall”. The assigned person changes
|
||||||
every week. You can find who the currently assigned person is on IRC by using
|
every week. You can find who the currently assigned person is on matrix by using
|
||||||
`.oncall` in any of our various IRC channels, such as `#fedora-admin` on
|
`!oncall` in any of our various matrix channels, such as `#admin:fedoraproject.org`
|
||||||
Libera Chat.
|
|
||||||
|
|
||||||
When available, this person:
|
When available, this person:
|
||||||
|
|
||||||
|
@ -107,7 +105,7 @@ It will then be scoped and prioritized from there.
|
||||||
|
|
||||||
Please provide as much information as you can in your ticket to avoid
|
Please provide as much information as you can in your ticket to avoid
|
||||||
back and forth for information. If you know your issue is going to
|
back and forth for information. If you know your issue is going to
|
||||||
cause a lot of discussion, start a mailing list thread for that.
|
cause a lot of discussion, start a mailing list or discussion thread for that.
|
||||||
|
|
||||||
Make sure your ticket:
|
Make sure your ticket:
|
||||||
|
|
||||||
|
@ -133,12 +131,12 @@ our question/ping within two weeks, otherwise we reserve the right to close the
|
||||||
ticket (knowing that you can always re-open it or open a new one if the issue
|
ticket (knowing that you can always re-open it or open a new one if the issue
|
||||||
persists or re-appeared).
|
persists or re-appeared).
|
||||||
|
|
||||||
== IRC
|
== Matrix
|
||||||
|
|
||||||
IRC is a great way to communicate, but please do not ping team members
|
Matrix is a great way to communicate, but please do not ping team members
|
||||||
directly. Instead, update your ticket with any new information you have and
|
directly. Instead, update your ticket with any new information you have and
|
||||||
when the team member(s) working on that issue have time/availability, they
|
when the team member(s) working on that issue have time/availability, they
|
||||||
may contact you on IRC for more interactive debugging/testing.
|
may contact you on matrix for more interactive debugging/testing.
|
||||||
|
|
||||||
== Direct emails
|
== Direct emails
|
||||||
|
|
||||||
|
@ -154,7 +152,7 @@ link:https://tools.ietf.org/html/rfc1149[Pigeons are too slow] for most work
|
||||||
items, and require facilities (e.g. dovecots) that most team members do not
|
items, and require facilities (e.g. dovecots) that most team members do not
|
||||||
have. Even if the oncall member does have a free dovecot, feed, and is trained
|
have. Even if the oncall member does have a free dovecot, feed, and is trained
|
||||||
in handling carrier pigeons, sending a pigeon to a single team member has the
|
in handling carrier pigeons, sending a pigeon to a single team member has the
|
||||||
same problems as using IRC or email for the same purpose, which means tickets
|
same problems as using matrix or email for the same purpose, which means tickets
|
||||||
are still the correct way to report problems.
|
are still the correct way to report problems.
|
||||||
|
|
||||||
In other words, please don't send us any birds.
|
In other words, please don't send us any birds.
|
||||||
|
|
|
@ -58,9 +58,7 @@ Infrastructure Team as well as communicate with other team members on a regular
|
||||||
** When you are ready to send a [introduction to the group](mailto:infrastructure@lists.fedoraproject.org),
|
** When you are ready to send a [introduction to the group](mailto:infrastructure@lists.fedoraproject.org),
|
||||||
** your subject should be 'Meeting Agenda Item: Introduction _Your Name_'.
|
** your subject should be 'Meeting Agenda Item: Introduction _Your Name_'.
|
||||||
The message body should include:
|
The message body should include:
|
||||||
*** Your IRC/Matrix handle
|
*** Your Matrix handle
|
||||||
**** link:https://fedoraproject.org/wiki/How_to_use_IRC[_What's this?_]
|
|
||||||
**** link:https://fedoramagazine.org/beginners-guide-irc[Beginner's Guide to IRC]
|
|
||||||
**** link:https://fedoramagazine.org/join-the-conversation/[Fedora's Matrix instance at chat.fedoraproject.org]
|
**** link:https://fedoramagazine.org/join-the-conversation/[Fedora's Matrix instance at chat.fedoraproject.org]
|
||||||
*** What skills you have to offer and which you would like to learn. This can include...
|
*** What skills you have to offer and which you would like to learn. This can include...
|
||||||
**** Programming languages you are familiar with or have used
|
**** Programming languages you are familiar with or have used
|
||||||
|
@ -72,8 +70,8 @@ The message body should include:
|
||||||
issues for one that is of interest.
|
issues for one that is of interest.
|
||||||
** Any initial questions you have for the team
|
** Any initial questions you have for the team
|
||||||
*** Look at the link:https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/[Fedora Infrastructure Best Practices] document
|
*** Look at the link:https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/[Fedora Infrastructure Best Practices] document
|
||||||
*** Be patient, as sometimes folks are busy and might not reply to your email quickly. You may get a faster response on IRC.
|
*** Be patient, as sometimes folks are busy and might not reply to your email quickly. You may get a faster response on Matrix.
|
||||||
*** join the #fedora-admin channel on IRC and attend the next IRC meeting.
|
*** join the #admin:fedoraproject.org channel on matrix and attend the next matrix meeting.
|
||||||
*** Watch link:http://fedoramagazine.org/?p=642[some videos] intended to introduce new contributors to
|
*** Watch link:http://fedoramagazine.org/?p=642[some videos] intended to introduce new contributors to
|
||||||
the team.
|
the team.
|
||||||
|
|
||||||
|
@ -83,7 +81,7 @@ After you've completed the steps outlined in the xref:gettingstarted.adoc#_first
|
||||||
section] you should:
|
section] you should:
|
||||||
|
|
||||||
* Regularly attend the link:https://fedoraproject.org/wiki/Infrastructure/Meetings[Weekly Meetings]
|
* Regularly attend the link:https://fedoraproject.org/wiki/Infrastructure/Meetings[Weekly Meetings]
|
||||||
on IRC/Matrix and be sure to introduce yourself the first time you attend. There is a section at the
|
on Matrix and be sure to introduce yourself the first time you attend. There is a section at the
|
||||||
start of the meeting where you can give a short introduction of yourself to the rest of the team.
|
start of the meeting where you can give a short introduction of yourself to the rest of the team.
|
||||||
* Take some time to learn about the link:[services]https://docs.fedoraproject.org/en-US/infra/map_critical_services/
|
* Take some time to learn about the link:[services]https://docs.fedoraproject.org/en-US/infra/map_critical_services/
|
||||||
the Fedora Infrastructure Group develops, deploys and maintains.
|
the Fedora Infrastructure Group develops, deploys and maintains.
|
||||||
|
@ -91,7 +89,7 @@ the Fedora Infrastructure Group develops, deploys and maintains.
|
||||||
* Read up on link:https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/#_standard_operating_procedures[SOPs]
|
* Read up on link:https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/#_standard_operating_procedures[SOPs]
|
||||||
you find interesting. These are a good point of reference for hosts related to an app. They give an overview
|
you find interesting. These are a good point of reference for hosts related to an app. They give an overview
|
||||||
of how things work for that app.
|
of how things work for that app.
|
||||||
* Idle in IRC and chime in with questions or offers to help when you see an interesting problem being discussed.
|
* Idle in matrix and chime in with questions or offers to help when you see an interesting problem being discussed.
|
||||||
|
|
||||||
If you don't have the time to be involved on a regular basis at this point, please feel free to watch over
|
If you don't have the time to be involved on a regular basis at this point, please feel free to watch over
|
||||||
things and report bugs and RFEs as you see fit. Showing interest now is a great way to make it easier to
|
things and report bugs and RFEs as you see fit. Showing interest now is a great way to make it easier to
|
||||||
|
@ -108,13 +106,13 @@ contributions.
|
||||||
== How the team works
|
== How the team works
|
||||||
|
|
||||||
The Fedora Infrastructure Group consists of volunteers and Red Hat employees. Our preferred
|
The Fedora Infrastructure Group consists of volunteers and Red Hat employees. Our preferred
|
||||||
method of communication is IRC on Libera.Chat in channel though we also heavily use the Fedora Mailing
|
method of communication is matrix though we also heavily use the Fedora Mailing
|
||||||
List. We also have a Matrix room dedicated to us link:https://chat.fedoraproject.org/#/room/#admin:fedoraproject.org[#admin].
|
List.
|
||||||
We try to be as transparent as possible and default to open.
|
We try to be as transparent as possible and default to open.
|
||||||
|
|
||||||
New members are encouraged to join the list, use the discourse, IRC, Matrix and attend meetings.
|
New members are encouraged to join the list, use the discourse, Matrix and attend meetings.
|
||||||
|
|
||||||
Asking questions (in any of our public areas: IRC, Matrix, lists, meetings) is encouraged. Unless there's an outage
|
Asking questions (in any of our public areas: Matrix, lists, meetings) is encouraged. Unless there's an outage
|
||||||
or people are busy we are happy to try and explain how something is setup or works.
|
or people are busy we are happy to try and explain how something is setup or works.
|
||||||
|
|
||||||
The team is a meritocracy, which means those people who solve issues and do work are given more privileges over time. In
|
The team is a meritocracy, which means those people who solve issues and do work are given more privileges over time. In
|
||||||
|
|
|
@ -15,6 +15,7 @@ matters under their area:
|
||||||
* Infrastructure Lead - Kevin Fenzi
|
* Infrastructure Lead - Kevin Fenzi
|
||||||
* Development Manager - Aurelien Bompard
|
* Development Manager - Aurelien Bompard
|
||||||
* Quality Engineering - Adam Williamson
|
* Quality Engineering - Adam Williamson
|
||||||
|
* Release Engineering - Samyak Jain
|
||||||
|
|
||||||
The officers generally decide what needs to be done in the day to day operations
|
The officers generally decide what needs to be done in the day to day operations
|
||||||
of the various Fedora infrastructure facilities. The officers themselves work
|
of the various Fedora infrastructure facilities. The officers themselves work
|
||||||
|
@ -23,13 +24,10 @@ Council. This basically means that we'll try to do whatever we can to fill needs
|
||||||
and fix things but if we refuse for whatever reason, the final decision can be
|
and fix things but if we refuse for whatever reason, the final decision can be
|
||||||
made by the Fedora Project Council. Such decisions, however, are rare.
|
made by the Fedora Project Council. Such decisions, however, are rare.
|
||||||
|
|
||||||
For more information on our officers and governance method see our Officers
|
|
||||||
page.
|
|
||||||
|
|
||||||
== Communicating
|
== Communicating
|
||||||
|
|
||||||
The Infrastructure Team coordinates their activities using a variety of tools.
|
The Infrastructure Team coordinates their activities using a variety of tools.
|
||||||
Our primary methods of communication are weekly IRC meetings, the Matrix room
|
Our primary methods of communication are weekly matrix meetings, the Matrix room
|
||||||
#admin:fedoraproject.org and the discussion.fedoraproject.org with the #infra-team tag.
|
#admin:fedoraproject.org and the discussion.fedoraproject.org with the #infra-team tag.
|
||||||
|
|
||||||
Application development efforts take place in the #apps:fedoraproject.org Matrix room,
|
Application development efforts take place in the #apps:fedoraproject.org Matrix room,
|
||||||
|
@ -38,7 +36,7 @@ Matrix channel.
|
||||||
|
|
||||||
=== Meetings
|
=== Meetings
|
||||||
|
|
||||||
We also hold weekly meetings in #fedora-meeting[?] each Thursday at 14:00 UTC.
|
We also hold weekly meetings in #meeting-3:fedoraproject.org each Thursday at 16:00 UTC.
|
||||||
See the UTC Howto for instructions to convert UTC to your local time.
|
See the UTC Howto for instructions to convert UTC to your local time.
|
||||||
|
|
||||||
See the meetings page for details and historical archives.
|
See the meetings page for details and historical archives.
|
||||||
|
|
|
@ -20,8 +20,7 @@ repositories or host static web pages. The top-level domain is an index of the
|
||||||
existing pages.
|
existing pages.
|
||||||
|
|
||||||
Notifications https://apps.fedoraproject.org/notifications[apps.fp.o/notifications]::
|
Notifications https://apps.fedoraproject.org/notifications[apps.fp.o/notifications]::
|
||||||
Centrally managed preferences for Fedora notifications via email or
|
Centrally managed preferences for Fedora notifications via email or matrix
|
||||||
https://fedoramagazine.org/beginners-guide-irc/[IRC].
|
|
||||||
+
|
+
|
||||||
* https://github.com/fedora-infra/fmn[Sources]
|
* https://github.com/fedora-infra/fmn[Sources]
|
||||||
* https://fmn.readthedocs.io/en/stable/[Documentation]
|
* https://fmn.readthedocs.io/en/stable/[Documentation]
|
||||||
|
@ -113,9 +112,9 @@ sure one for you.
|
||||||
* https://docs.mailman3.org/projects/hyperkitty/en/latest/[Documentation]
|
* https://docs.mailman3.org/projects/hyperkitty/en/latest/[Documentation]
|
||||||
|
|
||||||
Meetbot https://meetbot.fedoraproject.org/[meetbot.fp.o]::
|
Meetbot https://meetbot.fedoraproject.org/[meetbot.fp.o]::
|
||||||
Fedora Infrastructure runs a friendly IRC bot that you may know named
|
Fedora Infrastructure runs a friendly matrix bot that you may know named
|
||||||
https://fedoraproject.org/wiki/Zodbot[zodbot]. Among its many and varied
|
https://fedoraproject.org/wiki/Zodbot[zodbot]. Among its many and varied
|
||||||
functions is logging IRC meetings, the archives of which you can find here.
|
functions is logging matrix meetings, the archives of which you can find here.
|
||||||
+
|
+
|
||||||
* https://github.com/fedora-infra/mote[Sources]
|
* https://github.com/fedora-infra/mote[Sources]
|
||||||
|
|
||||||
|
|
|
@ -45,7 +45,7 @@ the availability of staff.
|
||||||
|
|
||||||
* Have a clear schedule of reachable hours.
|
* Have a clear schedule of reachable hours.
|
||||||
* Set and take regular vacation time to be rested.
|
* Set and take regular vacation time to be rested.
|
||||||
* Rotate through days on-call in IRC and tickets.
|
* Rotate through days on-call in matrix and tickets.
|
||||||
* If adding a new service, be available outside of normal business hours to
|
* If adding a new service, be available outside of normal business hours to
|
||||||
help debug problems.
|
help debug problems.
|
||||||
* Follow procedures and checklists when adding or updating services.
|
* Follow procedures and checklists when adding or updating services.
|
||||||
|
|
|
@ -38,7 +38,7 @@ Provide a brief description of the SOP here.
|
||||||
Owner::
|
Owner::
|
||||||
<usually, Fedora Infrastructure Team>
|
<usually, Fedora Infrastructure Team>
|
||||||
Contact::
|
Contact::
|
||||||
<stakeholder fas groups, individuals, IRC channels to find the action>
|
<stakeholder fas groups, individuals, matrix channels to find the action>
|
||||||
Location::
|
Location::
|
||||||
<Relevant URIs, etc>
|
<Relevant URIs, etc>
|
||||||
Servers::
|
Servers::
|
||||||
|
|
|
@ -10,7 +10,7 @@ team.
|
||||||
[[releng-contact-info]]
|
[[releng-contact-info]]
|
||||||
=== Contact Information
|
=== Contact Information
|
||||||
|
|
||||||
* IRC: `#fedora-releng` on irc.libera.chat
|
* matrix: `#releng:fedoraproject.org`
|
||||||
* Mailing List: https://admin.fedoraproject.org/mailman/listinfo/rel-eng[rel-eng@lists.fedoraproject.org]
|
* Mailing List: https://admin.fedoraproject.org/mailman/listinfo/rel-eng[rel-eng@lists.fedoraproject.org]
|
||||||
* Issue tracker: https://pagure.io/releng/new_issue[Fedora Releng Pagure Tickets]
|
* Issue tracker: https://pagure.io/releng/new_issue[Fedora Releng Pagure Tickets]
|
||||||
|
|
||||||
|
@ -43,7 +43,7 @@ For information on the Fedora Release Engineering Philosophy, see
|
||||||
|
|
||||||
=== Fedora Release Engineering Leadership
|
=== Fedora Release Engineering Leadership
|
||||||
|
|
||||||
Mohan Boddu (mboddu on IRC, FAS username mohanboddu)
|
(@jnsamyak:matrix.org on matrix, FAS username jnsamyak)
|
||||||
|
|
||||||
Leadership is currently appointed by FESCo with input from the current
|
Leadership is currently appointed by FESCo with input from the current
|
||||||
release team.
|
release team.
|
||||||
|
@ -75,11 +75,11 @@ reporting.
|
||||||
[[join-releng]]
|
[[join-releng]]
|
||||||
=== Joining Release Engineering
|
=== Joining Release Engineering
|
||||||
|
|
||||||
Much of rel-eng's communication is via IRC. One of the best ways to
|
Much of rel-eng's communication is via matrx. One of the best ways to
|
||||||
initially get involved is to attend one of the meetings and say that
|
initially get involved is to attend one of the meetings and say that
|
||||||
you're interested in doing some work during the open floor at the end of
|
you're interested in doing some work during the open floor at the end of
|
||||||
the meeting. If you can't make the meeting times, you can also ping one
|
the meeting. If you can't make the meeting times, you can also ping one
|
||||||
of us on IRC or sign up for the
|
of us on matrix or sign up for the
|
||||||
https://admin.fedoraproject.org/mailman/listinfo/rel-eng[mailing list].
|
https://admin.fedoraproject.org/mailman/listinfo/rel-eng[mailing list].
|
||||||
|
|
||||||
Since release engineering needs special access to systems essential to
|
Since release engineering needs special access to systems essential to
|
||||||
|
@ -106,8 +106,8 @@ requests, please consult the `releng-contact-info`
|
||||||
|
|
||||||
=== Meetings
|
=== Meetings
|
||||||
|
|
||||||
rel-eng holds regular meetings every Monday at 14:30 UTC in
|
rel-eng holds regular meetings every Tuesday at 17:00 UTC in
|
||||||
[.title-ref]##fedora-meeting-3# on the Libera IRC network.
|
[.title-ref]##meeting-3:fedoraproject.org on matrix.
|
||||||
|
|
||||||
* https://pagure.io/releng/issues?status=Open&tags=meeting[Meeting
|
* https://pagure.io/releng/issues?status=Open&tags=meeting[Meeting
|
||||||
agendas] are created from open tickets in pagure that contain the
|
agendas] are created from open tickets in pagure that contain the
|
||||||
|
|
|
@ -78,7 +78,7 @@ via git hooks:
|
||||||
*** A mail about the changes is sent to _sysadmin-members_.
|
*** A mail about the changes is sent to _sysadmin-members_.
|
||||||
|
|
||||||
*** The changes are announced on the message bus, which in turn triggers
|
*** 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:
|
You can check out the repo locally on _batcave01_ with:
|
||||||
|
|
||||||
|
|
|
@ -68,6 +68,4 @@ $ systemctl restart moksha-hub
|
||||||
== Internal Contacts
|
== Internal Contacts
|
||||||
|
|
||||||
If we need to contact someone from the RH internal "unified messagebus"
|
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
|
team, search for "unified messagebus" in source.
|
||||||
project between RHIT and PnT Devops. See also the `#devops-message` IRC
|
|
||||||
channel, internally.
|
|
||||||
|
|
|
@ -50,7 +50,7 @@ the next playbook run.
|
||||||
At this point, you can push the change out to production and be
|
At this point, you can push the change out to production and be
|
||||||
publishing messages "okay". Everything should be fine.
|
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
|
_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_
|
and write a new _Processor_ for it in the _fedmsg_meta_
|
||||||
library we maintain:
|
library we maintain:
|
||||||
|
|
|
@ -14,7 +14,6 @@ irc.
|
||||||
|
|
||||||
____
|
____
|
||||||
* #fedora-apps for FMN development
|
* #fedora-apps for FMN development
|
||||||
* #fedora-fedmsg for an IRC feed of all fedmsgs
|
|
||||||
* #fedora-admin for problems with the deployment of FMN
|
* #fedora-admin for problems with the deployment of FMN
|
||||||
* #fedora-noc for outage/crisis alerts
|
* #fedora-noc for outage/crisis alerts
|
||||||
____
|
____
|
||||||
|
|
|
@ -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
|
saying the request has been received. There is a 'quick response' in the
|
||||||
pagure issue tracker to note this.
|
pagure issue tracker to note this.
|
||||||
. Login to FAS and clear the `Telephone number` entry, set Country to
|
. 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
|
`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
|
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
|
group, you are done. Update the ticket and close it. This step will be
|
||||||
|
|
|
@ -33,23 +33,6 @@ $ git clone GIT_URL
|
||||||
$ git checkout -b develop
|
$ git checkout -b develop
|
||||||
$ git push --all
|
$ 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
|
== Add an EasyFix label
|
||||||
|
|
||||||
|
|
|
@ -21,7 +21,7 @@ Purpose::
|
||||||
|
|
||||||
github2fedmsg is a small Python Pyramid app that bridges github events
|
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
|
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:
|
has two phases of operation:
|
||||||
|
|
||||||
* Infrequently, a user will log in to github2fedmsg via Fedora OpenID.
|
* Infrequently, a user will log in to github2fedmsg via Fedora OpenID.
|
||||||
|
|
|
@ -1,7 +1,7 @@
|
||||||
= mote SOP
|
= mote SOP
|
||||||
|
|
||||||
mote is a MeetBot log wrangler, providing an user-friendly interface for
|
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:
|
Production instance: http://meetbot.fedoraproject.org/ Staging instance:
|
||||||
http://meetbot.stg.fedoraproject.org
|
http://meetbot.stg.fedoraproject.org
|
||||||
|
@ -26,7 +26,7 @@ Contact::
|
||||||
Location::
|
Location::
|
||||||
Fedora Infrastructure
|
Fedora Infrastructure
|
||||||
Purpose::
|
Purpose::
|
||||||
IRC meeting coordination
|
matrix meeting coordination
|
||||||
|
|
||||||
== Deployment
|
== 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
|
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
|
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
|
in addition to a memcached store which is currently not in use with
|
||||||
Fedora infrastructure.
|
Fedora infrastructure.
|
||||||
|
|
||||||
|
|
|
@ -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
|
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
|
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
|
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
|
quickest way to get in touch with everyone. Secondary to that we use the
|
||||||
mailing list. After that it's our ticketing system and
|
mailing list. After that it's our ticketing system and
|
||||||
talk.fedoraproject.org.
|
talk.fedoraproject.org.
|
||||||
|
|
|
@ -149,7 +149,7 @@ http://status.fedoraproject.org please push an update to reflect the
|
||||||
outage (see xref:status-fedora.adoc[status-fedora SOP]).
|
outage (see xref:status-fedora.adoc[status-fedora SOP]).
|
||||||
|
|
||||||
Report all information in #fedora-admin. Coordination is extremely
|
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
|
real-time communication device. If a web site is out please put up some
|
||||||
sort of outage page in its place.
|
sort of outage page in its place.
|
||||||
|
|
||||||
|
|
|
@ -58,7 +58,7 @@ infrastructure sysadmin-main group.
|
||||||
Once a sponsor is aquired and all needed packages have been packaged and
|
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
|
are available in EPEL, we move on to the planning phase. In this phase
|
||||||
discussion should take place about the application/resource on the
|
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:
|
deployed should be considered:
|
||||||
|
|
||||||
* Should the resource be load balanced?
|
* Should the resource be load balanced?
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue