We have a number of milestones due by the end of the summer (flock for some,
end of august for the others), I thought it would be nice to try to list and
There are four apps that are mainly concerned: Pagure, FAS, python-fedora and
There are three main goals for pagure for this summer:
- Support for private git repos (Farhaan Bukhsh)
- Pagure/Jenkins integration (Farhaan Bukhsh)
- Adjust pagure and crons to have pagure run at pkgs.fp.o (Vivek Anand)
The deadline for these is the end of august (the end of GSoC)
The main goal for FAS is: getting FAS3 running in stg, before flock.
This is going to be a team effort from: Xavier, Patrick, Szymon and I.
As above, the main idea here is to get it adjusted for FAS3 before flock so that
eventually at flock we can do a small hackfest on porting apps to FAS3.
Regarding FAS3 and python-fedora, the idea is to get FAS3 running in stg asap,
next to FAS2, finish/polish things around python-fedora and when that is done,
break stg by removing FAS2 and then work on every apps using FAS2 to port them
The day we push FAS3 and the day we drop FAS2 will of course be announced so
we can start testing FAS3 and then fixing the apps.
The basic idea for hubs is to get a demo running in time for flock.
This will also be a team effort together with: devyani7 (GSoC), Szymon (RH
Intern), Eric (RH Intern), Radhika (RH Intern), Máirín, Ryan and I.
Of course the names listed there do not mean that only those people can work on
these projects, as usual everyone is welcome to join one or all of these
the more the merrier :)
Thanks for your attention,
Another quick update: as of right now, Basset will also block users
This is indicated by an internal error saying "Denied service to $username."
This will make sure that spambots are even more limited with regards
to the amount of
spam they can place.
If a user complains about this, see the Basset SOP on how to undo this block.
Just a quick update that at this moment Basset also handles trac attachments.
Next up will be to deploy the trac block plugin and integrate that with Basset.
I'll finish that tomorrow, so more FBRs will come in by then.
The infrastructure team will be having it's weekly meeting tomorrow,
2016-06-02 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.
= 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 (2016-06-02)
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson
#topic New folks introductions / Apprentice feedback
= 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 We are now in Fedora 24 Final freeze - everyone
#info fix_arm_soc.yml playbook ready for use, see it for docs - 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 supybot-gribble fork: https://github.com/ProgVal/Limnoria plans - kevin
#topic split notifications from scm-commits to new list? - kevin
= Apprentice 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.
#topic Apprentice office hours
= 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: modularity from a high level - threebean
= Meeting end stuff =
#topic Open Floor