You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.
At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.
0. Whats your fedora account system login?
1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?
No. Still having a hard time setting up
2. Has it helped you decide any area you wish to focus on or contribute
3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets? No
4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?
5. Is there any help or communication or ideas you have that would help
you do any of the above?
Not at this moment.
6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?
Finding tickets to work on.
7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?
8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby
Not recently, but I have in the past.
9. Whats your favorite Halloween food?
Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.
Nothing yet, sir.
Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).
Thanks, and looking forward to your feedback!
infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org<mailto:email@example.com>
To unsubscribe send an email to infrastructure-leave(a)lists.fedoraproject.org<mailto:firstname.lastname@example.org>
Hi as I am a newbie into open source and programming in general, would
anyone like to be my mentor and help through this process.
Someone who is proficient in Python would be highly appreciated.
On Nov 6, 2016 1:47 PM, "Subham Sharma" <sam271994(a)gmail.com> wrote:
IRC Handle: s27
Programming languages familiar with : Python, Java
Hi, I am a newbie to programming and to open source and would love to work
on "real world" issues and help out as much as I can. I am open to learning
new things but would love to start out working in python.
Looking forward to an awesome time working with you guys.
I was going through this,
Had some questions around the same. The questions may sound a bit
noobish, but anyhow am throwing it up.
1. HAProxy load balances the requests among the various app servers,
but the configuration on which HAProxy runs, are those dynamically
changing, or they are manually updated through some bash scripts,
whenever there is a need to ?
2. Also before making the choices of HAProxy, Apache and Varnish were
there any discussions related to why the choice is being made. Are
those discussion docs public ?
Good Morning Everyone,
The design folks have asked if we could bump the maximum size allowed when
uploading content to pagure.
It is currently of 4MB and they are asking if we could bump it to 50MB.
It is a simple configuration change that looks like this:
diff --git a/ roles/pagure/frontend/templates/pagure.cfg b/ roles/pagure/frontend/templates/pagure.cfg
index 227813d..eb3ed92 100644
--- a/ roles/pagure/frontend/templates/pagure.cfg
+++ b/ roles/pagure/frontend/templates/pagure.cfg
@@ -143,7 +143,7 @@ ITEM_PER_PAGE = 50
### Maximum size of the uploaded content
# Used to limit the size of file attached to a ticket for example
-MAX_CONTENT_LENGTH = 4 * 1024 * 1024 # 4 megabytes
+MAX_CONTENT_LENGTH = 50 * 1024 * 1024 # 4 megabytes
### Lenght for short commits ids or file hex
SHORT_LENGTH = 7
I would like to ask if I can apply this change, deploy it and restart apache on
Good Morning Everyone,
This morning I started looking at migration our license agreements from FAS2 to
We currently have 8 CLAs in FAS2:
For the moment, in the migration script I created a dummy license agreement:
`cla_fpca` and migrated all the people member of the `cla_fpca` group in FAS2 as
having signed that new license agreement.
The question I have is basically: do we want to migrate all 8 CLAs by creating
their respective LAs in FAS3 and migrating their members or are we only
interested in the FPCA group these days?
I'm sending this out on a few different mailing lists, but it's
something that will require participation and effort from a few
I filed a ticket in the Fedora Infrastructure Pagure about migrating
from Trac for Fedora Badges. This is picking up from an earlier
discussion that Zach Villers (aikidouke) started on the mailing lists a
couple months ago. In the ticket, I've tried to summarize the major pain
points for migrating this Trac. A comprehensive overview can be found there.
I would like to ask anyone who is involved with Fedora Badges, past or
present, to please review this ticket and offer feedback to the issues
raised in the ticket. I think of all the Tracs on FedoraHosted, this
will be the most complex one to migrate because we have a lot of other
components dependent on Trac or the FedoraHosted domain. It's important
to start this discussion early than late. Even if you're not involved
with Fedora Badges but might have ideas or advice on some of the
problems raised here, your feedback would also be welcome!
Justin W. Flory
The infrastructure team will be having it's weekly meeting tomorrow,
2016-11-03 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-11-03)
#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 Fedora 25 Final FREEZE now in effect - everyone
#info infra-docs git hooks fixed up - patrick
#info ansible updated to 18.104.22.168 on batcave01 - kevin
#info November apprentice nag out, all apprentices please answer - 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 more outreach / improving onboarding - stickster / 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 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
Rel-eng has been wanting a got hook that would notify the people involved with
secondary arches about changes made to packages involving ExclusiveArch or
I took a stab at this hook today and I would like to offer the result for
So with this email is an ansible patch adding the hook and installing it in our
Things that needs to be tweaked:
- Where to send the email?
- Turn off debug after we confirmed it works
- Currently I install the script as a file not a template, so the URL to point
to commits in CGIT will be the same in prod and in stg.
Comments and thoughts more than welcome :)