Good Morning Everyone,
Our infrastructure is mostly a python store, meaning almost all our apps are
written in python and most using wsgi.
However in python we are using a number of framework:
* flask for most
* pyramid for some of the biggest (bodhi, FAS3)
* Django (askbot, Hyperkitty)
* TurboGears2 (fedora-packages)
* aiohttp (python3, async app: mdapi)
While this makes sometime things difficult, these are fairly standard framework
and most of our developers are able to help on all.
However, as I see us starting to look at JS for some of our apps (fedora-hubs,
wartaa...), I wonder if we could start the discussion early about the different
framework and eventually see if we can unify around one.
This would also allow those of us not familiar with any JS framework to look at
the recommended one instead of picking one up semi-randomly.
So has anyone experience with one or more JS framework? Do you have one that
would you recommend? Why?
Thanks for your inputs,
As some of you may be aware there has been chatter around having the
documentation for infrastructure and release engineering centralised in one
A possible solution to this is to move all of these under a new section on
docs.fedoraproject.org called something like Infrastructure and Release
Engineering (very original I know).
We could then go about moving docs which are suitable from currrent
locations to the new central point. Each doc should be updated before
moving and the old document should be updated to only contain a link to the
new doc to avoid a case of multiple versions of a doc (https://xkcd.com/927/
The following links contain the bulk of the documentation:
These would be the suggested first steps with other docs to follow if/when
these are completed.
As I say this is just a possible solution so as always all feedback and
suggestions are encouraged and welcomed.
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,