July 2021 - infrastructure - Fedora Mailing-Lists

by Pierre-Yves Chibon

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, Pierre

7 months, 3 weeks

10
12
3 / 0

Infrastructure and release engineering Documentation

by Mark O'Brien

Hi All, As some of you may be aware there has been chatter around having the documentation for infrastructure and release engineering centralised in one place. 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: https://fedora-infra-docs.readthedocs.io/en/latest/ https://docs.pagure.org/releng/ https://fedoraproject.org/wiki/Infrastructure 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. Thanks, Mark

1 year, 7 months

4
8
0 / 0

Update hyperkitty to latest?

by Reon Beon

https://release-monitoring.org/project/53453/

1 year, 7 months

2
2
0 / 0

Noggin 1.3.0 deployed to production

by Aurelien Bompard

Hey folks! I forgot to announce it here, but I deployed Noggin 1.3.0 to prod last week. Here are the highlights. Features - Add a page to manage registering users (PR#672 <https://github.com/fedora-infra/noggin/pull/672>). - Allow template override with a custom directory, see the TEMPLATES_CUSTOM_DIRECTORIES configuration value (PR#701 <https://github.com/fedora-infra/noggin/pull/701>). - Allow users to declare their Matrix IDs in addition to the IRC nicknames (#248 <https://github.com/fedora-infra/noggin/issues/248>). - Display on users’ profiles the agreements they have signed (#576 <https://github.com/fedora-infra/noggin/issues/576>). - Validate email addresses when changed in the mail or rhbz_mail attributes (#610 <https://github.com/fedora-infra/noggin/issues/610>). - Allow users to select multiple pronouns (#646 <https://github.com/fedora-infra/noggin/issues/646>). Bug Fixes - Don’t tell users signing up that their username is already taken when it can be the email address (PR#665 <https://github.com/fedora-infra/noggin/pull/665>). - Add the for attribute to checkbox labels (#658 <https://github.com/fedora-infra/noggin/issues/658>). Development Improvements - Start using pre-commit <https://pre-commit.com/> to run the simple checkers (linters, formatters, security checks). Run poetry install to install the new dependencies, and then run pre-commit install to setup the git hook. Also add the safety <https://pyup.io/safety/> tool (PR#659 <https://github.com/fedora-infra/noggin/pull/659>). As always, please report the issues you may encounter. Cheers! Aurélien

1 year, 10 months

1
0
0 / 0

Ticket notifications in IRC

by Aurelien Bompard

Hey folks! 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? Aurélien

1 year, 10 months

6
13
0 / 0

[Fedocal] Reminder meeting : Websites & Apps Team Meeting

by jflory7＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Websites & Apps Team Meeting on 2021-07-27 from 15:00:00 to 16:00:00 UTC At https://meet.jit.si/fedora-websites-apps-meeting The meeting will be about: Weekly team meeting for the Websites & Apps Team. This is part of the [Websites & Apps Community Revamp Objective](https://fedoraproject.org/wiki/Objectives/Websites_%26_Apps_Co.... See [past discussion]( https://discussion.fedoraproject.org/t/planning-meeting-for-websites-apps...) to learn more about the Websites & Apps Team and how it came together. More information available at: [hackmd.io/Mxm2We3yTqKybLsdohadOA](https://hackmd.io/Mxm2We3yTqKybLsdohadOA?view) Source: https://calendar.fedoraproject.org//meeting/9990/

1 year, 10 months

1
0
0 / 0

Questions about the Fedora Release Life Cycle

by Beatriz Michelson Reichert

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., letsencrypt). 2. Do clients use the trust anchors from the ca-certificates package or do they have a list of their own? -- Best regards, Beatriz Santa Catarina State University - UDESC

1 year, 10 months

2
2
0 / 0

[Fedocal] Reminder meeting : Fedora Infrastructure

by Damian Tometzki

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2021-07-22 from 16:00:00 to 17:00:00 UTC At fedora-meeting-3(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda. Source: https://apps.fedoraproject.org/calendar/meeting/9675/

1 year, 10 months

1
0
0 / 0

DNS patch request to enable ocp staging worker01-03

by David Kirwan

https://gist.github.com/davidkirwan/ae4038fa101dea3e8e1318ce3330970b Hi infra, can I please get a review on the patch above, we are configuring the ocpstaging worker machines to boot via dhcp. cheers -- David Kirwan Software Engineer Community Platform Engineering @ Red Hat T: +(353) 86-8624108 IM: @dkirwan

1 year, 10 months

3
2
0 / 0

Re: A couple of questions before contributing to projects

by Mark O'Brien

On Mon, Jul 19, 2021 at 5:30 PM Onur Özkan <onurozkan.dev(a)outlook.com> wrote: > 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 > differences? > > 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 PR 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 helpful. > > Best regards, > Onur > Mark

1 year, 10 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure July 2021