We currently have messages posted on the #fedora-apps and
#fedora-infrastructure IRC channels when there's a ticket change or a
pull-request change. I don't know about the infrastructure channel, but it
makes it difficult to have a development conversation in #fedora-apps, the
signal/noise ratio is just too low.
Are you all happy with this setup? I would like to propose we move those
notifications to a different channel, such as #fedora-apps-activity (and
#fedora-infrastructure-activity). Otherwise I can go have my development
discussions in another channel, it's fine too.
What do you think?
Hi, I'm Beatriz and I'm a student at the Santa Catarina State University.
Currently, I'm studying the Fedora Release Life Cycle, and would like to
know if anyone could help me with some questions about this subject:
1. I understand that the services used to build composes (e.g., Koji,
Bodhi, Pungi) use TLS. But it was unclear whether these certificates are
generated internally or whether they are generated by a public CA (e.g.,
2. Do clients use the trust anchors from the ca-certificates package or
do they have a list of their own?
Santa Catarina State University - UDESC
You are kindly invited to the meeting:
Fedora Infrastructure on 2021-07-22 from 16:00:00 to 17:00:00 UTC
The meeting will be about:
Weekly Fedora Infrastructure meeting. See infrastructure list for agenda.
On Mon, Jul 19, 2021 at 5:30 PM Onur Özkan <onurozkan.dev(a)outlook.com>
> Hey folks,
> I am someone new for fedora-infra. I have introduced myself a couple of
> months ago. But I haven't received any reply about where and how to start
> so today I wanted to start by picking issues from repositories and solving
> them. But, I need some answers before I go for that. (I already asked the
> questions on #fedora-admin but sadly didn't get the answer there. So that's
> why I ask them from here.)
> Questions are:
> - We have 2 infra organizations 1 on Github 1 on Pagure. What are the
> It is mostly a matter of preference for the developer but you will find
most upstream apps on github and most direct infrastructure repos on pagure
> - We have fedora-infrastructure repository on Pagure without any
> organization which contains so many issues. But we also have issues on
> organization repositories. So which issue goes where?
> This tracker https://pagure.io/fedora-infrastructure/issues is for
general infrastructure bugs where as bug related directly to an app will be
filed on the upstream repository
> - As a volunteer contributor, where should I pick the issues from for
> the start? For example, can I start working on this
> <https://github.com/fedora-infra/the-new-hotness/issues/323> issue?
> Yes! please do :) We generally use the flow of create a fork and raise a
Please let me know if this is not the right place to ask such questions.
This is a good place to ask these questions and I hope my answers were
> Best regards,
New release of Greenwave is now available and has been deployed to
* RHEL product versions in Brew/Koji build tasks are now recognized
* Internal subject type configuration can use regular expression to extract
short product version from artifact name.
* Satisfied requirements with type "fetched-gating-yaml" now contain
field so as not to break existing clients.
* Unexpected or unsupported Koji task types are now ignored when guessing
product version for new test results allowing decision updates to be
Get in touch: exd-guild-gating(a)redhat.com
EXD SP Gating guild
today on Fedora infra weekly meeting I proposed to start doing a backlog
refinement on https://pagure.io/fedora-infrastructure/issues
This should be done in the similar way how the backlog refinement is
done in weekly RelEng meeting.
So how do you want to approach this? Separate new meeting or use
existing weekly meeting and just dedicate a part of it to going through
If we want a new meeting, I would go with weekly and we need to decide
when this meeting will take place.