This is just a heads up that there is a dependency chain of orphaned packages
that would lead to problems in bodhi when retired. They will be retired in less
than a month if nobody takes them.
(I wonder who takes care of bodhi when Randy is not available, ccing Aurelien
who made some commits recently.)
I suspect this request might fall short, but I figure I'll start a dialog.
With Fedora CoreOS needing some different services set up and more and more
requests getting opened every day on the infra issue tracker, it would be nice
if I could gain some more access within Fedora Infra to be able to help support
the Fedora CoreOS efforts as well as possibly help lighten the load (i.e. perform
simple privileged tasks for unprivileged people when appropriate) of Fedora's
I've had a few services that I recently got all the way through the RFR process.
I was admittedly out for a month during that time on leave, but if you subtract
that month it still took a rather long time to make it to completion. The long times
aren't necessarily anyone's fault, just happens to be how the requests landed and
also my projects not necessarily being on anyone's priority list.
That being said, I have learned a lot by getting these apps into prod and I feel
like I can help our future apps along if I had more access to debug things myself
(i.e. inconsistencies in stage) rather than waiting on someone from infra.
I am not requesting this access to abuse it. I am typically conservative and don't
do things that I'm not comfortable doing or that I know would be frowned upon. As
an example I was granted access to the releng group a while back and I think that
has worked out well.
I'd like to help if possible, but I understand if my request isn't granted.
I'd like to start contributing to Fedora Infrastructure. I have a operations engineer background and I am familiar with Bash, Python, AWS, Kubernetes, Ansible, Terraform. I'm in the PST time zone (California).
I've created a Fedora account (slee), signed the FPCA, and subscribed to the Fedora Infrastructure Mailing List. I'm squishedlunch on IRC and I've been lurking a bit on #fedora-admin. Unfortunately I missed the weekly meeting this morning but I'll be sure to catch future sessions.
Can someone invite me to the 'fi-apprentice' group? Also I've seen references to various tools like release-monitoring.org and https://jenkins-fedora-infra.apps.ci.centos.org, is there a central place where all these tools/endpoints are listed?
Looking forward to working with everyone!
After the Flock talk from the Facebook folks, they approached QA about
the idea of submitting karma and/or test results from their internal
testing as a bot account.
Is this something that is possible? I know that we have done bot
accounts at various points in time but I don't remember if automated
karma is allowed or what the other restrictions on that were.
I wrote  to devel some time ago regarding the deprecation of the apps.fp.o
index and plan to move its content to the main docs. Kevin mentionned that it
could end up in the infrastructure docs and that the whole should be moved to
docs.fp.o at some point. I will take a look at both since I have wanted to play
with the new documentation pipeline for a while. I am not the best guy to
meddle with the infrastructure doc but I might as well do something useful
while playing with antora. Tell me if it's not or if I missed something.
I might have something to show you at Flock if I have troubles sleeping in the
See you in Budapest,
The Fedora Infrastructure is planning to retire the infinote 
service. This service allows text collaboration using the Gobby
client and was mainly used by the Infrastructure team to coordinate
our weekly meeting and the mass update & reboot of the machines.
The service will be taken offline on August 30th 2019. If you wish to
backup some of the document currently hosted, you should make sure
that you have downloaded them locally before that date.
The Infrastructure team will most likely use the service provided by
hackmd.io  for their needs. Other alternatives like public etherpad
can also be used to replace this service.
 - https://infinote.fedoraproject.org/infinote/
 - https://fedoraproject.org/wiki/Gobby
 - https://opensource.com/article/19/7/enable-collaboration-hackmd
So we do a reposync of RHEL-7 trees every night. For the x86_64 we have
been keeping track of a lot of repositories which may not make sense to
keep. I have broken it into 3 types: We need to Keep, no idea, and nope.
Please look over these and let me know where the others go as I am fixing
the rhel7-sync script to be a bit more maintainable.
Need to Keep
Which of these make sense to keep syncing?
To Be Deleted
Stephen J Smoogen.
Good Morning Everyone,
As you may remember from  the CPE team has started categorizing its
applications into the following categories:
1. We maintain it, we run it
2. We don’t maintain it, we run it
3. We don’t maintain it, we don’t run it
4. We turn it off
In this process we picked the following four applications that we want
to move from the first category to the third:
* elections 
However, we do not want to throw code over the wall to anyone, so we’re
setting up something we called “A Friday with Infra”. The goal is to
help on-boarding anyone interested in picking up the maintenance of any
of these apps by taking time on Friday to work on these apps with them.
We have prepared a wiki page describing this proposal, how to get
involved in it as well as all the work we believe should be done to have
a smooth hand-over of the applications:
Let us know if you have any questions or (even better) want to be
involved with any of them :)
– On behalf of the CPE team
 elections has actually already found a new maintainer