we decided it's time to rethink our needs and redesign Fedora main website from scratch.
I would like to encourage your team to take a part in this initiative and work on this together as we need to make sure that we have everybody on board and all needs are taken into consideration.
Based on initial input I gather from Fedora forum and meeting with Matthew I prepared one page with summary of what we are going to do and it's available here https://fedoraproject.org/wiki/Websites/Fedora_Website_Revamp
It's possible I'll move it to other place in the future but for now it will be our workspace.
As a short term strategy I would like you to choose one representative from your team for upcoming kick-off meeting with other stakeholders and send me directly details like name, Feroda ID and e-mail address. It will be much easier for me to contact chosen person having this. Please try to do this by 30th June. I'm aware holiday period started and probably not everyone will be available but let's try to do our best and push forward this exciting initiative :)
When I have all participants gathered I'll try to find common slot to organize session for us. Agenda will be included in invitation.
Main goal of this kick-off will be to discuss known facts, go through goals, assumptions and requirements and also plan next steps for next couple of weeks.
I'll propose long term strategy, approach and wider plan after meeting with all of you.
Please read in advance https://fedoraproject.org/wiki/Websites/Fedora_Website_Revamp and if you already have some requests, suggestion please send it to your representative and then each person can send it to me before kick-off. Taking into consideration we will have huge amount of stakeholders I don't see other way to work on this than having one person from each team, I hope you understand.
Looking forward to work with all of you.
* Your IRC handle
* What skills you have to offer and which you would like to learn. This can include...
* Python but not professionally by any means. can generally understand what others have written though not good at writing my own thing from scratch
* Systems administration skills I have a homelab of 1 server and 2 laptops, I have a couple dedicated servers in datacenters to play with as well mostly using linux though some bsd such as free and opnsense as a router., Have an associates degree in networking, no certifications but a goal for the next 10 years or so would be to get rhca (ambitious but hey that's a long time), and technologies I'd like to learn would be the containers stuff like openshift, kubernetes, and get better at automation which I have tried a little but don't really have a large enough use case to actually do much with such as ansible.
* No real relevent associations at the moment locally as I live in a rather rural area.
* What you want to learn
* What I would like to work on would be things that improve my abilities in areas that I am weak such as the automation and podman/containers areas. Even outside the eventual goal mentioned above I genuinely like learning new things and improving myself and helping others.
* https://pagure.io/fedora-infrastructure/issue/9695 looks like a task I should be able to learn and accomplish to start with? T (https://pagure.io/fedora-infrastructure/issue/9695)here are a few others I could look at too but that ones near the top and seems reasonable to start with.
* Any initial questions you have for the team
* Look at the Fedora Infrastructure Best Practices (https://fedora-infra-docs.readthedocs.io/en/latest/) document < - have done so
* I have joined #fedora admin
* I attended the meeting this morning as a guest.
* Watch some videos (http://fedoramagazine.org/?p=642) intended to introduce new contributors to the team. <- Playing now.
* Interested in the apprenticeship program if there are spots open please.
In https://pagure.io/fedora-infrastructure/issue/10053 Ryan notes that
we have a ton of groups that mention irc.freenode.net in their group
infromation in the account system.
In https://pagure.io/fedora-infrastructure/issue/10035 bookware notes
that we have irc nick's set in the account system when they may no
longer be valid with the irc network move. Also, our notifications
service is sending to the new network, but using the old
nicks/previously setup, which may or may not be the same.
Also, I'd like to note that libera.net is amending their nick policies
this friday: https://github.com/Libera-Chat/libera-chat.github.io/commit/cf5211538ed65...
basically if someone registers a nick, but only uses it 2 for less than
2 hours after registering, it can be freed up after 2 weeks.
This new policy may allow some contributors that couldn't get their old
nick on the new network back.
Addiitonally, we hope to sometime real soon now(tm) have our fedora
matrix server up and running with 'spaces' so all the rooms and mappings
will change around again then anyhow.
Abompard has a PR to noggin to allow it to specify irc network and
matrix ids: https://github.com/fedora-infra/noggin/pull/668
So, what do we want to do here?
* Set a date, like June 30th (1 week from today) to clear things.
* Get things lined up before that date and on that date:
* clear all irc info from groups, we can re-add info after matrix is
setup pointing to matrix channels.
* Clear all irc nicks from account system
* Clear all irc nicks from FMN
* Send announcement that we did that and ask everyone to re-enter irc
nicks in account system and re-validate irc nicks with FMN.
* Do we want to get that noggin PR rolled out first?
* Do we want to get noggin to be able to verify nicks first?
* Do we want to just hold off on all this until matrix is setup?
* Clearning verified irc from FMN, does that also require users to
re-enter all their rules?
As a reminder, if you need to reach package maintainers for a specific
package in private, you can email:
You can also now mail:
packagename-maintainers-fedora(a)fedoraproject.org to just reach the
fedora branch(es) maintainer(s).
packagename-maintainers-epel(a)fedoraproject.org to just reach the epel
Note that these aliases are for coordination or other items that cannot
be a bugzilla bugs. In general all bug or enhancement requests should be
During the development of Fedora Accounts (freeIPA, freeipa-fas,
noggin, etc), the AAA development team started work on a collection of
Vagrant controlled virtual machines to make it simple to create a dev
environment for working on applications that use Fedora Accounts for
authentication. It was named tiny-stage:
By default, it creates machines that set up FreeIPA, Ipsilon, and
FasJSON (the fedora accounts API), and populates the accounts with a
bunch of users and groups, so you can test everything out. For
example, if you currently have a local dev version of an application
that pointed to iddev.fedorainfracloud.org, you create the tinystage
VMs locally, and use ipsilon.tinystage.test/idp
There are also a collection of other VMs that set up some of our
applications (like elections), and are configured to run in the dev
environment out of the box. There is also another VM that implements a
simple OpenID Connect client for devs to use as a sample
Long story short, check out and try tiny-stage and see if it is useful to you!