The infrastructure team will be having it's weekly meeting tomorrow,
2015-07-30 at 18:00 UTC in #fedora-meeting on the freenode network.
We have a gobby document
fedora-infrastructure-meeting-next is the document.
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 =
This shared document is for the next fedora infrastructure meeting.
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 (2015-07-30)
#chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou
#topic New folks introductions / Apprentice feedback
#topic GSoC student update - kushal
= 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 old cloud to new cloud migration moving along, hopefully done by friday -
#info ibiblio05 installed and ready for service - kevin
#info virthost19/20/21/22 installed and ready for service - smooge
#info smooge onsite at phx2
#info bapp02/app01.stg now gone. Down to just 9 hosts in puppet - kevin
#info We are now in Fedora 23 Alpha freeze! - kevin
= 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 or 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 TRAC tickets review - p_klos
There are many tickets left alone for months with comments that let thin there are
Maybe we should review all open tickets one by one and decide whether we should do
something or just close the ticket?
#topic Idea: We could create official Fedoraproject Docker repo - p_klos
I found some Fedora cloud repo on Docker Hub but we don't have any official
FedoraProject repo with Docker images. Maybe we could create one and put there
Docker-ready images? I.E. Latest, alpha, server minimal, server freeipa, other options
available to "click" in anaconda during installation?
= 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 info 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.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor