We updated the “How is Fedora Organized?” page on Fedora docs with the org chart below. This chart shows governing bodies, teams, editions, spins/labs, and initiatives. Is your Fedora thing missing? Feel free to comment on this Discussion post to ask for an update.
The Fedora Council wants to hear what you have to say! Take the anonymous survey now.
As before we are interested in the usage of tools and communication channels, your roles, your favorite apps and programming languages. This year we also specifically ask about the development mailing list.
Continue readingThis is the second post in a series covering details about the journey of the Fedora Websites and Apps community Initiative, those who were involved in making it a grand success, and what lies ahead down the road for the team. If you have not already, read the previous post before delving into this one.
We started off with having recorded meetings on video conferencing platforms like Jitsi Meet. Around August 2021 we decided against to accommodate more fruitful and open discussions. Eventually, we developed rules and regulations for in-call discipline to ensure that everyone in the meeting got equal representation.
Months passed by with us slowly moving into rewriting our first application, Meetbot Logs, and our first website, Fedora Easyfix. That is when one of our founding members, Nasir Hussain, had to leave for a while. For a fast-moving and quickly evolving team that takes on multiple projects at once, this also was unfortunately the time when many disagreements among the ambitious members plagued the team’s progress. Development stalled for some weeks before we were again helped by Justin W. Flory (J.W.F.) and Marie Nordin.
Back on track now — around October 2021 — we started looking for interns to mentor under our wings for the Outreachy 2021 winter cohort. We looked at the existing projects that we maintain and the new projects we wanted to prototype and develop. Vipul Siddharth helped me and Onuralp Sezer to create a mentored projects proposal. Soon after, Francois Andrieu joined me and Michael Scherer joined Onuralp Sezer to mentor the Outreachy applicants.
To ensure that we are well equipped to lead the Council objective, Ramya Parimi, Justin W. Flory, Matthew Miller, Marie Nordin, and I started having a Fedora Websites and Apps Objective Leads meeting every couple of weeks. We made a lot of progress with a two-track approach to development and planning with the help of one of the Fedora Websites veterans, Rick Elrod. Gregory Lee Bartholomew and Graham White joined us then from the (now, defunct) Fedora Program Management team.
The time of December 2021 was yet again a time for setbacks. Life became increasingly busy and our council objective co-lead Ramya Parimi announced she was stepping down. This dealt a great impact on me as with Ramya Parimi and Sayak Sarkar looking into the planning and documentation side of things. Before that, I could spend most of my time doing what I liked to do — developing and maintaining the codebase of our projects with the team. To this date, I like to think that we have not yet recovered from that loss and I do look forward to her return to the community as well as the team. Also, the development of Fedora Easyfix, which I was doing for a long time under Pierre-Yves Chibon’s guidance and Masha Leonova’s assistance, had to be abandoned due to the lack of interest within the community in using the project. Thankfully, we had some things going well at around the same time – which included Graham White stepping up as the new Council objective co-lead and the project led by Onuralp Sezer for making the Fedora Project organization chart as an interactive website.
With the vast amount of knowledge around program management that Graham White brought to the table, he also became a part of the Fedora Websites and Apps Objective Co-Leads team and joined the efforts for revamping our Fedora Websites and Apps Team. By around February 2022, we had Pawel Zelawski bringing in a wave of positive change by helping lead the efforts of revamping our main websites. With him, a variety of stakeholders like Ankur Sinha, Timothee Ravier, Peter Boy, Allan Day, Luna Jernberg, Kevin Fenzi, and many more joined us in the Fedora Websites and Apps Stakeholders Team – helping us understand what our renewed websites offering Fedora Linux really need. This is also right around the time when the community efforts around building our Fedora Linux websites slowly started off and the team got two Outreachy interns, Subhangi Choudhary, and Ojong Enow, getting mentored and working on extending my rewrite of Mote called Fragment and Onuralp Sezer’s project about interactive Fedora Project organization chart called Fedora Graphs 1.
With the Fedora Websites 3.0 out alongside the release of Fedora Linux 38 and the redevelopment of Fedora Badges in full swing, it could not have been a better time than now to close the community initiative as a success. Let’s look back at how far we came from where we started. This is the first in a series of five posts detailing the journey of Fedora Websites and Apps Community Initiative, those who were involved in making it a grand success, and what lies ahead for the team.
Continue readingAt our hackfest earlier this year, the Council agreed that we want to drop the distinction between full and auxiliary positions on the Council. Instead, we should have all members on an equal footing. The concerns expressed by some on the former Fedora Board (the predecessor to the Council) haven’t come to pass. But we have seen a negative impact: people in these roles feel less empowered to act, and unsure about their standing as a “real” member of the Council.
I propose to remove this distinction. Please discuss this in the Fedora Discussion topic. The Council will begin voting on this proposal on 21 April.
Last month, the Fedora Council gathered in Frankfurt, Germany for our first in-person meeting since January 2020. It felt great to see folks again, but it wasn’t all fun and games (actually, we didn’t even play games until after we’d wrapped up on the last night). With three years of work to catch up on and a five year strategy to develop, there was a lot to do. If you want the Zodbot form, we logged the minutes. For more detail, read on.
Continue readingLast week, I submitted a proposal to the Fedora Council establishing a structure for the Fedora Code of Conduct Committee. You can read the full proposal in the Discussion topic, but in short, the goal is to establish a structured committee to handle Code of Conduct reports.
Continue readingIn January 2023, the Fedora Council approved a title change for the Fedora community role. The Fedora Community Action & Impact Coordinator (FCAIC) is now renamed to Fedora Community Architect (FCA).
Continue readingThe Fedora.Next strategy was a key part of the success we’ve enjoyed over the last few years. But we can’t stop there. It’s time to develop a strategy to meet our goal for the next five years: doubling the number of active contributors. To do this, there are a number of technical and community objectives we need to drive. It looks like that number is 18. The Fedora Council developed a list of 18 objectives to support the impacts we’re looking for. Now it’s your turn. Let us know what you think in the Discussion thread.
This is just the first step. We’re looking for discussion at a high level. Over the next few months, we’ll have a thread dedicated to each objective. Once we’ve had a chance to discuss it together, the Council will vote on the final strategy. From there, we’ll start working on the details to make these objectives a reality. I’m super excited to work on this with you.
Our websites are our face to the Fedora Linux users and the community members. We started with a successful Council objective proposal to revamp the websites and applications. As part of that, we want to revitalize and organize the community that maintains them. Allow me to share with you the things that we have been up to so far.
Continue readingCopyright © 2023 Fedora Community Blog
This work is licensed under a Creative Commons Attribution 4.0 International License.
Theme by Anders Noren — Up ↑
Recent Comments