We are getting close to filling up people02:/projects and RISC-V is
taking up the largest section of disk space
There are a lot of duplicate packages in ./RPMS and ./SRPMS also. What
do we need to do long term for this?
Stephen J Smoogen.
I am Dakota Eurell, a Computer Science student in the United States
(UTC-04:00, or EDT). On IRC, you will find me by my handle of 'akrylo'.
I am a very security and privacy oriented individual, which I believe
to be a large influence in the decision making involved in my work. My
skills are largely System Administrator based; meaning I have a strong
basis in the command-line and scripting.
As far as development skills go, I am definitely still green in a lot
of areas. Despite this, I have skills in Bash scripting, Python, and
C/C++. I also have minor skills with SQL, although I definitely have a
lot to learn.
I don't have any certifications, although very soon I plan on pursuing
the RHCSA. In the coming months, I will be interning at a large company
where I will be implementing an incidence response system. In addition
to this, I expect that I will gain a lot of networking fundamentals. I
hope the skills I obtain from this work will help me with any tasks I
have with Fedora's development.
I have been using Linux for around three years, beginning with Arch
before transitioning to Debian about half a year later. About a year
ago I began heavily using Fedora. Fedora's commitment to blazing a path
for Linux and working heavily with upstream have inspired me to help
the world of Linux be fully realized. In addition to these points, I
have seen almost nothing but good things coming from those within the
Fedora community. I strongly believe that Fedora would be a good home
for myself and my future.
Since my schedule changes so rapidly, I cannot give a concrete amount
of time I will be capable of contributing to Fedora, but I would say my
range is 10-40 hours per week, averaging around 20 hours. I do not
expect there to be any weeks in which I will be fully unable to
contribute (barring emergencies and vacations).
I am interested helping with all of the tasks that the Infrastructure
Team tackles, although I would certainly say that implementing 'fault-
tolerant systems' and the creation and maintaining of tools to automate
maintenence are my strongest passion. My overall goal is to make Fedora
easier to maintain and expand. To this end, all of my work would have
security, modularity, and expansion in mind. This of course assumes
that the tasks I am involved with have these goals in mind. While I
like to attempt to innovate, I definitely understand the necessity to
not add unnecessary complications to the process.
As far as specific issues I have in mind to tackle: the 'easyfix'
issues on pagure are all tasks I would like to help with, although I
would certainly need direction in order to help.
Thank you to all who have read this introduction; I hope to be a
valuable asset to the Infrastructure Team in the near future.
we are now in the infrastructure freeze leading up to the Fedora 27 Beta
release. This is a pre-release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 27 Beta when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2017-09-19 (or later if Beta
slips). Frozen hosts should have no changes made to them without a
sign-off on the change from at least 2 sysadmin-main or rel-eng members,
along with (in most cases) a patch of the exact change to be made to
I tagged v2.1.0 of FMN and it's currently building for Rawhide. It'll be
in staging soon and, assuming there are no problems, in production next
The full changelog is at
Note: Maintaining FMN isn't *really* my job anymore, and while
serverless applications are all the rage at the moment, maintainerless
applications aren't yet possible, so it'd be great if someone could take
over. I'm happy to walk whoever the lucky volunteer is through the
current state of things :)
I'm Elorm. On IRC, I'm elormes. I'm a CSE undergrad student in Ghana. I
code much in python and do web development with django. I am familiar
with other langs like C# and Java. I have a fascination with DevOps and
I saw a blog post requesting for maintainers for the fedora-tagger
application. I would like to volunteer for the migration and also as a
long time maintainer.
This is a FBR for a patch to add a FAS group to Fedora Badge mapping for
the 'mindshare' FAS group.
It is a straightforward patch. The patch file is attached.
Let me know if anything else is needed. Thanks!
Justin W. Flory
A patch is attached to update and better organize the Fedora
Council-related aliases and update the Flock email addresses.
The patch changes the following:
* Organizes and comments Fedora Council aliases together
* Changes board alias to council-private(a)lists.fp.o
* Links to new doc pages for FPL and FCAIC in comments
* Drop diversity alias (this was never used in Diversity Team)
* Use fcaic alias for Flock emails instead of hard-coding bex
Let me know if anything else is needed. Thank you!
Justin W. Flory
In a futile effort to get slightly less email to worry about, I'd like
to nuke the scholarship alias, since we no longer do the scholarship
and the address gets nothing but spam at this point.
I'd like to push this and run bastion.yml with -t fas_client
Author: Ricky Elrod <relrod(a)redhat.com>
Date: Wed Mar 28 21:39:07 2018 +0000
Remove myself from scholarship alias, it is all spam at this point anyway
Signed-off-by: Ricky Elrod <relrod(a)redhat.com>
diff --git a/roles/fas_client/files/aliases.template
index 41682da..a655be7 100644
@@ -243,7 +243,7 @@ nick.bebout: nb
# Fedora Scholarship
# Fudcon regional aliases - point to point person before that fudcon