At the last few infrastructure meetings (as well as in the past some)
the idea was floated of doing a informal video meeting where
contributors could put faces and voices to names and introduce
What would folks think of doing this after the infrastructure meeting
this thursday? So, 17-17:30UTC? We could fire up a jitsi meeting, with
link to be given out at the end of the infrastructure meeting. :)
What if we record this an we put it in the Fedora Project Channel on
El mié., 5 de mayo de 2021 5:08, Jan K <copper_fin(a)hotmail.com> escribió:
> Sounds good.
> *From:* Kevin Fenzi <kevin(a)scrye.com>
> *Sent:* Wednesday, May 5, 2021 12:07 AM
> *To:* infrastructure(a)lists.fedoraproject.org <
> *Subject:* informal video meeting for infrastructure contributors
> At the last few infrastructure meetings (as well as in the past some)
> the idea was floated of doing a informal video meeting where
> contributors could put faces and voices to names and introduce
> What would folks think of doing this after the infrastructure meeting
> this thursday? So, 17-17:30UTC? We could fire up a jitsi meeting, with
> link to be given out at the end of the infrastructure meeting. :)
> infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
> To unsubscribe send an email to
> Fedora Code of Conduct:
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> Do not reply to spam on the list, report it:
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.
Hope you all are doing well. Myself Bishal and are new to the Fedora
community. Currently I am living in India and working as a Spring Boot
My primary skills include C, PHP, Spring Boot, Git, basic Linux. Last
year I cleared the AWS Cloud Practitioner exam but unfortunately that field
has stopped as my current job role does not permit me to interact with AWS.
I am here to learn Linux and System Administration skills and to
contribute which adds value to current infrastructure. I want to get
familiar with the things that are the backbone of the infrastructure.
My IRC handle : #BISHAL
Linkedin : https://www.linkedin.com/in/bishalnandi1996
Mail : bishalnandi1996(a)gmail.com
Anybody gets any opportunity to interact with me please feel free to
contact me and let me know if I can be of any help for the great
community based team.
Hello everyone, I would like to introduce myself to you precious contributors.
My name is Onur Ozkan (irc: onurozkan), and currently, I am working as a Back End Team Lead in Istanbul. Here is my portfolio https://onurozkan.dev if you want to see some details about me.
I am experienced with languages such as C, Go, C#, and Python.
On Linux, I am good with scripting, containerization, log tracking, file permissions, and network management.
What I want to learn is, I want to see how things work behind the wall. I want to learn more about Operating System Engineering. I want to dive deeper and get more experienced in Linux so one day I can be a full-time Linux contributor without having a need to work for something else. For now, I can contribute 8-12 hours a week as a volunteer.
Please let me know if I can be useful for this team and if yes please guide me to what should I do next.
I have released and deployed Noggin 1.1.0 to production a few minutes
ago. Here are the release notes:
- Add a verification step when enrolling a new OTP token (#422).
- The GPG key ID fields now refuse key IDs shorter than 16 characters,
and allow up to 40 characters (the full fingerprint) (#556).
- Paginate the group members list (#580).
- Handle separately OTP from password in UI (#572).
- Start messages with capital letter (PR#521).
- Show more than 100 users on /group/<groupname> (PR#550).
- Fixed mailto href adding mailto in the template of the group (PR#581).
- Indirect groups are now included in the user’s group list (#560).
- Redirect back to the original page after login (#574).
- Fix the OTP QR code being displayed by default (#577).
- Add rstcheck to check our rst files (1c2205f).
- Update the release docs (96b08ea).
- Fix code-block format in contributing docs (PR#595).
Many thanks to the contributors of bug reports, pull requests, and
pull request reviews for this release:
- Chenxiong Qi
- Josseline Perdomo
- Rafael Fontenelle
- Ryan Lerch
- Vipul Siddhartha
The token verification feature should cut down on admin email from
people who got locked out of their account because the browser crashed
at the wrong moment or because their app did not like the token.