Good Morning Everyone,
I just cut and pushed a new version of anitya: 0.9.1
Here is the corresponding changelog:
* Tue Apr 19 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.9.1-1
- Update to 0.9.1
- Fix the stackage backend
It should cut the list of failed update of ~200 projects :)
Skills: Current Linux SysAd
Tech: RHEL, Centos, Apache, Docker, Ansible, etc
Employer: Rackspace - We love FOSS!
Wanna learn: Python, bash, packaging, expanding on current linux
knowledge, more ansible and Docker
I am all setup in FAS (jshua), so feel free to reach out at anytime in
IRC or email.
Good Morning Everyone,
I just cut and pushed a new version of anitya: 0.9.0
Here is the corresponding changelog
* Fri Apr 15 2016 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.9.0-1
- Update to 0.9.0
- Do not trigger the keyboard shortcut when in the search box (Prashant-Surya)
- Improved UI for flash messages being shown (sudheesh001)
- Add a maven-central backend (Michael Simacek)
- Indicate that anitya is py2 only (sudheesh001)
- Appended UTC as timezone (Jinank Jain)
- Update the drupal backends to use updates.drupal.org as source of info (Dave
The infrastructure team will be having it's weekly meeting tomorrow,
2016-04-14 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-04-14)
#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 mass update/reboot cycle mostly done, just a few groups left - kevin/patrick/smooge
#info bodhi02.stg reinstalled as bodhi01.stg - kevin
#info buildvm-02/03/04/05.stg added in staging - kevin
#info bvirthost01 and autosign02 added in build network - kevin
#info spammers still trying to get in, mostly being blocked by basset - everyone
#info noc01/02 upgraded to nagios 4.0.8 - kevin/patrick
= 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)
= 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.)
unknown. Sign up now?
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
so as people know, the ansible repository is quite old. Fedora was one
of the first big public ansible user, and as such, has a rather huge repo.
And going where no one has gone before has the downside of not being
able to build on others people experience with the new tools, resulting in
sometime less optimal solutions, or using older patterns, or just regular
bitrot. And as people have seen on the list, I did sent a few patches
for refactoring and cleaning things around as I did explore the repo,
but I think it would be more efficient to work on that as a team.
Therefor, I would like to know who would be interested by a hackfest during
flock this year. The idea would be to focus on improving existing playbooks.
And among the tasks, we could have:
- convert tasks who are not to be roles (example, 2fa)
- start using dependencies among roles (example, collectd, fedmsg)
- move from yum modules to packages (to handle the yum to dnf change)
- remove things < F21 (or EL 6 when applicable)
- move handlers, vars, files to role (or role arguments)
- move cronjob declaration to cron module (since currently, cron is not reloaded,
so changes are not picked)
and I think that alone would keep us busy.
That's most of the time small tasks, so that would scale well to any number of participants,
and with a low complexity, so open to everybody.
I already did the proposal before the end of the Cfp, but I kinda
forgot to send a email about it.
Any people besides me interested ?