My name is Nabil Rasool and I work in Information Security. Hoping to offer 5-10 hours a week, potentially more. I was a CS major in college so have coded in C++ in the past.
I’d like to learn more about Fedora and help out in any way I can. I don’t have any particular outstanding issues that I’d like to work on off the bat but will hopefully have something after a couple of meetings. I’m also interested in the fi-apprentice group and learn the infrastructure. Lastly, I think this is a great project and would love to contribute.
I’m looking forward to being at the meeting tomorrow.
IRC handle: piston
The infrastructure team will be having its weekly meeting tomorrow,
2018-05-03 at 14:00 UTC in #fedora-meeting on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
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 =
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 (2018-05-03)
#chair smooge relrod nirik pingou puiterwijk tflink
= 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
= Status / Information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need
(Please use #info <the thing> - your name)
#topic announcements and information
#info Fedora 28 released! Kudos to everyone!
#info Freeze is over
#info Pagure 4.0 being deployed
#info New openshift being deployed
#info Bodhi updates are happening
= 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 Tickets discussion
Go thru each ticket one by one
= Apprentice office hours =
#topic Apprentice Open office minutes
#info A time where apprentices may ask for help or look at problems.
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
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 none this week
= Meeting end stuff =
#topic Open Floor
Stephen J Smoogen.
we are now in the infrastructure freeze leading up to the Fedora 28
release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 28 when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2018-05-01 (or later if
release slips). Frozen hosts should have no changes made to them without
a sign-off on the change from at least 2 sysadmin-main or rel-eng
members, along with (in most cases) a patch of the exact change to be
made to this list.
I have had to update libmodulemd on bodhi-backend01, because it requires the "modulemd_objects_from_file" function in libmodulemd, which was added in version 1.2, but it is lacking a (versioned) requirement on libmodulemd, and due to the freeze we still had modulemd v1.1.
This should not have any impact, other than that we can actually send out module updates again.
Any +1s or complaints?