Meeting Agenda Item: Introduction Jeremy Cline
by Jeremy Cline
Hello everyone!
IRC handle: jcline
Skills: Python, C, Prolog, a bit of Ansible, and a bit of system
administration experience from running personal (mail, XMPP,
HTTP) services.
Associations: I'm a new member of the Fedora engineering team at Red Hat
I'm looking forward to learning all about the Fedora infrastructure and
helping out!
--
Jeremy Cline
XMPP: jeremy(a)jcline.org
IRC: jcline
7 years, 6 months
Freeze break request: add fedmsg bot in #fedora-admin
by Kevin Fenzi
Greetings
Since we switched over to pagure for fedora-infrastructure issues we
don't have in irc channel notifications of new tickets/tickets being
closed, etc.
Here's a stab at adding a fedmsg irc notification for #fedora-admin.
It would be nice to also have our notifications _NOT_ go to
#fedora-apps, but I am not sure how best to exclude them.
Additional patches for that welcome.
In the mean time, +1s?
kevin
--
From 204718ff3ed6bd60f7b4297d3145ce06a5af55ed Mon Sep 17 00:00:00 2001
From: Kevin Fenzi <kevin(a)scrye.com>
Date: Wed, 28 Sep 2016 20:44:02 +0000
Subject: [PATCH] add fedmsg bot for #fedora-admin for pagure issues changes
---
roles/fedmsg/irc/templates/ircbot.py | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/roles/fedmsg/irc/templates/ircbot.py
b/roles/fedmsg/irc/templates/ircbot.py index 2bb4c03..3d66e91 100644
--- a/roles/fedmsg/irc/templates/ircbot.py
+++ b/roles/fedmsg/irc/templates/ircbot.py
@@ -28,6 +28,29 @@ config = dict(
),
),
+ # For fedora-admin
+ dict(
+ network='chat.freenode.net',
+ port=6667,
+ make_pretty=True,
+ make_terse=True,
+
+ {% if env == 'staging' %}
+ nickname='fedmsg-admin-s',
+ {% else %}
+ nickname='fedmsg-admin',
+ {% endif %}
+ channel='fedora-admin',
+ filters=dict(
+ topic=[
+ '^((?!(pagure)).)*$',
+ ],
+ body=[
+ "^((?!(fedora-infrastructure|u'name': u'pagure')).)*$",
+ ],
+ ),
+ ),
+
# For fedora-apps
dict(
network='chat.freenode.net',
--
1.8.3.1
7 years, 6 months
Plan for tomorrow's Fedora Infrastructure meeting - 2016-09-29
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2016-09-08 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.
kevin
--
= 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-09-29)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean pingou puiterwijk pbrobinson
#topic New folks introductions
= 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 25 Beta freeze! - everyone
#info FMN digests flowing again now thanks to patrick! - patrick
#info some more projects migrated to pagure - everyone
#info ansible check/diff report down to just 6k! - kevin
#info infrastructure tickets down to just 97 - everyone
#info budget plans for next year need to be discussed, let us know if you need anything - smooge,patrick,kevin
#info
= 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 fedora infrastructure issues in pagure - kevin
* What kind of tags, milestones, priorities do we want?
* who should be added as users to the project?
#topic
= 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 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
#endmeeting
7 years, 6 months
Freeze break request: allow .htaccess fileinfo override in
getfedora.org
by Kevin Fenzi
Greetings.
To fix issue https://pagure.io/fedora-infrastructure/issue/5502
we need to allow .htaccess files "FileInfo" privs in
the /srv/web/getfedora.org dir on the proxies so the redirects work.
+1s?
From 5625ce807a7ffd294b145b0288846a7f75a42821 Mon Sep 17 00:00:00 2001
From: Kevin Fenzi <kevin(a)scrye.com>
Date: Wed, 28 Sep 2016 17:09:04 +0000
Subject: [PATCH] allow fileinfo on getfedora.org directory to
allow .htaccess to work for issue 5502
---
roles/fedora-web/getfedora/files/getfedora.org.conf | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/roles/fedora-web/getfedora/files/getfedora.org.conf
b/roles/fedora-web/getfedora/files/getfedora.org.conf index
7fc238f..14c5fed 100644 ---
a/roles/fedora-web/getfedora/files/getfedora.org.conf +++
b/roles/fedora-web/getfedora/files/getfedora.org.conf @@ -7,3 +7,7 @@
FileETag MTime Size
ExpiresActive On
ExpiresDefault "access plus 5 days"
+
+<Directory /srv/web/getfedora.org>
+ AllowOverride FileInfo
+</Directory>
--
1.8.3.1
7 years, 6 months
FBR: Update createrepo_c on bodhi-backend03
by Patrick Uiterwijk
Hi all,
I have just found the root cause of another update push issue
regarding the repocache.
This was caused by createrepo_c not closing updateinfo.xml.bz2 after
it's done with it, which
caused NFS to make a silly rename because it is deleted while the file
is still open.
I have a patch for this at
https://github.com/rpm-software-management/createrepo_c/pull/66.
Could I get +1s to update createrepo_c on bodhi-backend03 to a build
that includes this patch?
Thanks,
Patrick
7 years, 6 months
[patch] Badges: Oldschool mapping for 3D Printing SIG
by Justin W. Flory
Hey all,
One more quick patch... this one just adds the mapping for the 3D
Printing SIG FAS group to their badge as well. Should be a fairly quick
and simple one.
Patch file is attached.
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 6 months
Mapping FAS groups to Pagure groups
by Ankur Sinha
Hiya,
So, since trac is about to well.. kick the bucket.. in a few months and
we're all looking to migrate to Pagure, I was wondering if there's a
possibility of mapping FAS groups to Pagure groups - just to make group
management easier? I'm administrating the free-media and join groups
wit relatively fewer members, but groups like packagers are much larger
I'd think and would benefit from this?
pingou said there was a config that could enable this already, but he
suggested this be discussed here on the list to see if it should be
turned on.
I do think there's an alternative, btw. Although, I haven't looked into
it's implementation yet: a script that uses the FAS and Pagure APIs to
sync group memberships - group admins can do this from time to time?
--
Thanks,
Regards,
Ankur Sinha "FranciscoD"
http://fedoraproject.org/wiki/User:Ankursinha
7 years, 6 months
[FREEZE BREAK REQUEST] Badges: Oldschool mapping for Modularity WG
by Justin W. Flory
Hi all,
I have a simple patch that adds the new Modularity WG Member badge as a
mapping for the modularity-wg FAS group. I also alphabetized the list of
badge-to-group mappings for improved readability.
The patch file is attached - if approved, someone else will have to
merge the patch into the ansible.git repository (I don't have
privileges). Please let me know if anything else is needed! Thanks.
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
7 years, 6 months