Unfortunately the hackmd.io document could be only edited by owner.
On IRC I saw that we should send e-mail regarding changes to
sysadmin-main group,
but I don't know what e-mail we should use.
Michal
On 9/4/19 8:00 PM, Stephen John Smoogen wrote:
## Preamble
The infrastructure team will be having its weekly meeting tomorrow,
2019-09-05 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a hackmd.io document at https://hackmd.io/@ssmoogen/HyqIIdlmS
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 (2019-09-05)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink cverna mizdebsk
mkonecny abompard bowlofeggs
```
### 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 smooge will be on PTO 2019-09-07 -> 2019-09-15
#info we are in F31 beta freeze
#info pagure updates to 5.7.?
#info
#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 https://fedoraproject.org/wiki/Infrastructure/Oncall
#info relrod is on call from 2019-08-29 -> 2019-09-05
#info ?????? is on call from 2019-08-05 -> 2019-09-12
#info Summary of last week: (from cverna )
#topic Monitoring discussion
#info https://nagios.fedoraproject.org/nagios
#info Go over existing out items and fix
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
```
Go thru each ticket one by one
### Put all topics for discussion under here
```
#topic Where to put these docs in the future?
#info infinote is going away and this is my 'private hackmd'
#info a new central doc place would be good. can someone set this up?
```
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
```
_______________________________________________
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
