You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the infrastructure
I am doing something different this time with this email:
If you would like to stay in the apprentice group, please login at least
once to batcave01.phx2.fedoraproject.org. I'll check at the end of the
month and remove folks who haven't logged in at all in January.
Note that you can always be re-added down the road when you have more time.
If you need assistance logging into batcave01, please do look at:
and ask on irc or email list if you have any problems.
The infrastructure team will be having it's weekly meeting tomorrow,
2018-01-18 at 18: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.
> This shared document is for the next fedora infrastructure meeting.
> = Preamble =
> The infrastructure team will be having its weekly meeting tomorrow,
> HERE, 2018-01-11 at 18:00 UTC in #fedora-meeting on the freenode network.
> = 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-01-18)
> #meetingname infrastructure
> #topic aloha
> #chair smooge relrod nirik dgilmore threebean pingou puiterwijk pbrobinson maxamillion
> = 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 to discuss)
> (Please use #info <the thing> - your name)
> #topic announcements and information
> #info Lots of reboot been and upcoming for various CVEs - puiterwijk/kevin/smooge/relrod
> #info Many old f25 instances moved to f27, a few more to go - kevin
> #info Many folks traveling to devconf/fosdem/configmgmt-camp next week>
> = 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 Ticket cleanup
> #info none this week.
> = Apprentice office hours =
> #topic Apprentice Open office hours
> 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.)
> #topic Learn about:
> #info none this week
> = Meeting end stuff =
> #topic Open Floor
Good Morning Everyone,
After more than 2 years (!) without releases, I just cut a new release of
Here is its changelog:
* Wed Jan 10 2018 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.11.0-1
- Update to 0.11.0
- Change the label of the fiels from `Motif` to `Cause for rejection / Comment`
- Encode the image title to UTF-8 when sending notifications
- Make the CSRF token timeout configurable (Jeremy Cline)
- Add a Vagrant dev environment (Jeremy Cline)
- Adjust import for newer recommended flask version
- Port nuancier to python3 while remaining compatible with python2
- Add an submission_date_end field to the Election
It's currently happily running in stg. I would like to push it to prod but there
is an election in progress and the update will likely require something like a 5
minutes outage or so.
The addition of the submission_date_end field allowing some time between the end
of the submissions and the start of the voting period is quite interesting as it
lead to some issues during the last election.
What do you think?
-----BEGIN PGP SIGNED MESSAGE-----
I go to a dist-git repo and find a bug when browsing the source code. I can
open a PR to fix it, but what if I don't know how to fix it? I open an issue, right?
Except, there's no issue tracker for dist-git pagure repos. That's what bugzilla
is for. Now I need to go to bugzilla, find the component, fill out a bug, yada yada.
I understand the need for bugzilla and that it's not going away anytime soon, but could
we possibly integrate dist-git pagure issue tracking and bugzilla in a way that makes
the whole process more seamless for this workflow. We could even use the bugzilla API
and display things differently in pagure if we wanted.
These are just suggestions. I feel like this can be improved.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
The infrastructure team will be having its weekly meeting tomorrow,
HERE, 2018-01-11 at 18:00 UTC in #fedora-meeting on the freenode
Our agenda is stored in the gobby-0.5 server on infinote.fedoraproject.org
= 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-01-11)
#chair smooge relrod nirik dgilmore threebean pingou puiterwijk
= 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
= 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 Ticket cleanup
#info none this week.
#topic Upgrading/Migrating Jenkins
#info: Working with Pagure-CI triggers
#info A Pagure SCM Plugin for Jenkins
#topic enabling default Pagure fedmsg hooks on Fedora DistGit - clime, pingou
#topic Apprentice program feedback and changes - kevin
= Apprentice office hours =
#topic Apprentice Open office hours
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.)
#topic Learn about:
#info none this week
= Meeting end stuff =
#topic Open Floor
Stephen J Smoogen.
Here’s my introduction, or more accurately reintroduction email to the infrastructure team. I dropped back into the feadora-admin channel after the weekly meeting last week.
My IRC handle is willo and I was involved a couple of years ago as an apprentice for not quite a year. Since then I’ve moved to the beach not far from Sydney. Presently, I’m working remote for a cyber security company. Day to day, I’m cutting python some code, building things in AWS, working towards getting some CI into our pipeline and performing some integration testing.
Since I was contributing last time, I've continued working with ansible, python, KVM, virtualisation, integrating HA into various services and more recently exploring containerisation with Docker. I’ve also been doing datacenter migrations, configuring more Cisco network kit that I can to remember, both in the datacenter DC and also CPE. This time around, I’d like to maybe focus a bit more on the app development side, but also would like to keep my feet wet with some sysadmin activities.
Catch you all on IRC.
Good Morning Everyone,
I just cut a new release of mdapi: 2.10.3
Here is its changelog:
* Wed Jan 10 2018 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.10.3-1
- Update to 2.10.3
- Always initialize the output variable
- Fix getting package by their source name
It's currently running fine in stg and tests there are passing.
If no more issues are reported with it, I will push to it prod :)
Good Morning Everyone,
There has been work on fedora-hubs for a while now and there is an objective to
make it live in staging early this year.
However, there is a question about how we want to deploy such application.
So far we have asked that all our application be packaged in RPMs. The main
application may not be in the official Fedora repositories but (for most) we
asked that all of its dependencies are.
For example, pkgdb or pagure aren't in Fedora's repositories themselves, but we
still build them in koji pulling the dependencies from the official repos.
Hubs is the second of our app where this model is almost not workable because it
is written in nodejs where every file is/can be a separate package and semantic
versioning sometime not very well respected.
The other application we have that is in nodejs is the flock registration
application that, iirc, we run in our cloud.
However, hubs is not meant to be run in our cloud.
So how do we want to deploy hub?
Do we allow npm install? Do we want to use container? Should it target
How do we want to handle updates? (especially considering the semantic
versioning aspect mentioned above)
What do people think?