summaryrefslogtreecommitdiffstats
path: root/fedora-infrastructure-meeting-next
blob: f1e2ab4afadbdb409fab981264f5ad47f2b381ed (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
This shared document is for the next fedora infrastructure meeting.

Send on IRC a day before meeting (#fedora-noc #fedora-admin #fedora-releng #fedora-apps)

REMINDER: There will be a Fedora Infrastructure meeting tomorrow (2019-06-06) at 15:00 UTC in #fedora-meeting-1. Please update the gobby-0.5 document at infinote.fedoraproject.org with any agenda items https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure-meeting-next

On the day of the meeting send the following

REMINDER: There will be a Fedora Infrastructure meeting today (2019-06-06) at 15:00 UTC in #fedora-meeting-1. Please update the gobby-0.05 document at infinote.fedoraproject.org with any agenda items https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure-meeting-next

= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2019-06-06 at 15:00 UTC in #fedora-meeting-1 on the freenode network.

We have a gobby document at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure-meeting-next
which can be edited for the agenda (see: https://fedoraproject.org/wiki/Gobby )

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-06-06)
#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 bowlofeggs will be going on extended leave in 2019-06
#info cverna will be going on extended leave in 2019-06
#info Flock2Fedora 2019-08-08 -> 2019-08-11
#info Site trip to PHX2 will be 2019-07
wh
= 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 smooge is on call from 2019-05-30 -> 2019-06-06
#info no one is on call from 2019-06-06 -> 2019-06-20
#info pingou is on call from 2019-06-20 -> 2019-06-27
#info ?????? is on call from 2019-06-27 -> 2019-07-04
#info ?????? is on call from 2019-07-04 -> 2019-07-11
#info Summary of last week: (from smooge )

#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
#topic options for release artifact signing for Fedora CoreOS - dustymabe

#info We are exploring options for signing our release artifacts for Fedora CoreOS.
#info We have an open ticket where we have defined various options and narrowed down
#info the options to ones we'd like to explore with Fedora Infrastructure. The ticket
#info and all context can be found here: https://github.com/coreos/fedora-coreos-tracker/issues/187
#info The TL;DR is that we'd like to deliver an artifact and a detached signature:
#info i.e. `fcos.iso` and `fcos.iso.sig`. We'd like to discuss with infra to see what
#info the limitations are in the infra for achieving this goal and if we can make it happen.


=====
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