| |
@@ -1,11 +1,11 @@
|
| |
:experimental:
|
| |
- = The Fedora Infrastructure
|
| |
+ = Fedora Infrastructure and Release Engineering
|
| |
|
| |
- The Fedora infrastructure is the team of dedicated volunteers and
|
| |
+ Fedora infrastructure and Release Engineering are the teams of dedicated volunteers and
|
| |
professionals maintaining the servers and some of the services used to build
|
| |
Fedora as well as enable its community.
|
| |
|
| |
- We're located all over the globe and communicate primarily by IRC and e-mail.
|
| |
+ We're located all over the globe and communicate primarily by Matrix and e-mail.
|
| |
|
| |
== Officers
|
| |
|
| |
@@ -13,9 +13,8 @@
|
| |
matters under their area:
|
| |
|
| |
* Infrastructure Lead - Kevin Fenzi
|
| |
- * Security Officer - Patrick Uiterwijk
|
| |
- * Development Manager - Pierre-Yves Chibon
|
| |
- * Quality Engineering - Tim Flink
|
| |
+ * Development Manager - Aurelien Bompard
|
| |
+ * Quality Engineering - Adam Williamson
|
| |
|
| |
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
|
| |
@@ -30,11 +29,12 @@
|
| |
== Communicating
|
| |
|
| |
The Infrastructure Team coordinates their activities using a variety of tools.
|
| |
- Our primary methods of communication are weekly IRC meetings, the IRC channel
|
| |
- #fedora-admin[?] located on libera.chat, and the mailing list.
|
| |
+ Our primary methods of communication are weekly IRC meetings, the Matrix room
|
| |
+ #admin:fedoraproject.org and the discussion.fedoraproject.org with the #infra-team tag.
|
| |
|
| |
- Application development efforts take place in the #fedora-apps[?] IRC channel,
|
| |
- and system administration related efforts take place in the #fedora-noc IRC channel.
|
| |
+ Application development efforts take place in the #apps:fedoraproject.org Matrix room,
|
| |
+ and system administration related efforts take place in the #noc:fedoraproject.org
|
| |
+ Matrix channel.
|
| |
|
| |
=== Meetings
|
| |
|
| |
@@ -43,16 +43,6 @@
|
| |
|
| |
See the meetings page for details and historical archives.
|
| |
|
| |
- === IRC
|
| |
-
|
| |
- You can find core members and contributors in the #fedora-admin[?] channel.
|
| |
-
|
| |
- Additionally, for things specific to application development and testing we
|
| |
- have the #fedora-apps[?] channel, and for things related to alerts/outages
|
| |
- and general sysadmin tasks the #fedora-noc[?] channel.
|
| |
-
|
| |
- New to IRC? Have a read of our [Beginner's Guide to IRC](https://fedoramagazine.org/beginners-guide-irc/) -- Fedora Magazine
|
| |
-
|
| |
=== Mailing list
|
| |
|
| |
The mailing list of the Fedora Infrastructure Project is:
|
| |
@@ -60,3 +50,6 @@
|
| |
|
| |
The archives are available at:
|
| |
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/
|
| |
+
|
| |
+ We are in the process of moving much of the discussion that used to take place
|
| |
+ there over to discussion.fedoraproject.org with the #infra-team tag.
|
| |
kevin
commented 7 months ago
Replace IRC with matrix and lists (mostly) with discussion. Also update officers.
Signed-off-by: Kevin Fenzi kevin@scrye.com