## Preamble
The infrastructure team will be having its weekly meeting tomorrow,
2020-02-13 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a document at https://board.net/p/fedora-infra
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
## Introduction
We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs.
### Meeting start stuff
```
#startmeeting Infrastructure (2020-02-13)
#meetingname infrastructure
#chair nirik pingou relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs
#info Agenda is at: https://board.net/p/fedora-infra
#topic aloha
```
### Determine who the next chair is
#topic Next chair
#info magic eight ball says:
#info 2020-02-13 - smooge
#info 2020-02-20 - bowlofeggs
#info 2020-02-27 - ???
### Let new people say hello
```
#topic New folks introductions
#info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
#info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
```
### Status / Information / Trivia / Announcements
(We put things here we want others on the team to know, but don't need to discuss)
(Please use ```#info (the thing - your name)```
```
#topic announcements and information
#info ops folks are trying a 30min ticket triage every day at 19UTC in #fedora-admin
#info Fedora Infrastructure will be moving in 2020-06 from its Phoenix Az datacenter to one near Herndon Va. A lot of planning will be involved on this. Please watch out for announcements on changes.
#info Fedora 32 has been branched from rawhide.
#info
```
### Things we should discuss
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus /suor decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use ```#topic your discussion topic - your username)```
```
#topic Oncall
#info smooge is oncall 2020-02-06 -> 2020-02-13
#info nirik is oncall 2020-02-13 -> 2020-02-20
#info cverna is oncall 2020-02-20 -> 2020-02-27
#info ??? is oncall 2020-02-27 -> 2020-03-05
## .oncalltakeeu .oncalltakeus
#info Summary of last week: (from current oncall )
#info DNS broke on 2020-02-11 due to signing problems.
#topic Monitoring discussion [nirik]
#info Go over existing out items and fix
#topic Tickets discussion [nirik]
#topic backlog discussion
#info go over our backlog and discuss and determine priority
```
Go thru each ticket one by one
### Put all topics for discussion under here
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
### Learn about some application or setup in infrastructure
(This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.)
```
#info
```
### Meeting end stuff
```
#topic Open Floor
#endmeeting
```
Stephen J Smoogen.
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
