Voting in the Fedora 30 elections is now open. Go to the Elections app to cast your vote. Voting closes at 23:59 UTC on Thursday 20 June. Don’t forget to claim your “I Voted” badge when you cast your ballot. Links to candidate interviews are below.
If you cannot vote because you only have the “CLA done” group in FAS, please file an issue ASAP and I will take care of that for you
Continue readingIt’s hard for me to believe, but it’s been more than five years since we launched the “Fedora.next” initiative. At the end of Fedora’s first decade, we knew it would be important to think, plan, and adjust so the project could continue successfully in the decades to come. Now we’re halfway into the next one, and this Flock conference will be an important time for reflecting on our progress and charting our path for the next five years and beyond.
Because Flock is focused specifically at our contributors and developers, this is a unique conference and we’re looking for talks and sessions that reflect that.
It’s been around 20 days that I have been working on an Outreachy internship project with The Fedora Project. I have been working on some of the pending issues, miscellaneous bugs and cleaning up code in Fedora Happiness Packets. This month has been quite fun, which includes great learning through the entire process
Continue readingHere’s your report of what has happened in Fedora Program Management this week. Elections voting is open through 23:59 UTC on Thursday 20 June.
I have weekly office hours in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else.
Fire! Libgit can’t be installed, module changes are being temporarily reverted, and one of our great contributors are thinking about moving their packages out of Fedora.
This blog post has been written to summarize the problem, explain how we got here, offer potential solutions that would work right now, and to set a common ground for a discussion on the devel list about how to address this and similar problems properly.
Continue readingOn May 23, 2019, the Fedora Community in Mexico City ran an awesome Fedora 30 Release Party. This activity took place in the local Red Hat office. We really appreciate the space for our activities and particularly thanks to Alex Callejas (darkaxl017) for doing all the necessary paperwork.
We had three main activities: An amazing talk from Rolando Cedillo (@rolman) about KVM in Fedora, a Q&A session and our networking time with pizza and Fedora cup cakes.
Continue readingThis blog post summaries what I’ve completed in Phase 1 in my Outreachy internship with Fedora Happiness Packets, things I learned and the challenges I faced 🙂
Continue readingThis is part of a recurring series between May – August 2019 on the Community Blog about Fedora Happiness Packets. These posts are published as part of a series of prompts from the Outreachy program.
I recently got selected for Outreachy with Fedora and thought I should document the entire process for other curious souls looking to participate! 🙂
Note: This article by no means provides a ‘hack’ or definite steps to get into Outreachy. These are just my thoughts on what worked for me.
Continue readingAbout two years ago the Fedora Engineering team merged with the CentOS Engineering team to form what is now called the Community Platform Engineering (CPE) team. For the team members, the day to day work did not change much.
The members working on Fedora are still fully dedicated to work on the Fedora Project, and those working on CentOS are still fully dedicated to CentOS. On both projects its members are involved in infrastructure, release engineering, and design. However, it brought the two infrastructures and teams closer to each other, allowing for more collaboration between them.
Continue readingHere’s your report of what has happened in Fedora Program Management this week. Elections voting is underway!
I have weekly office hours in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else.
Continue readingInspired by the request that we provide written guidance on time commitment expectations and some conversations from our meeting in December, I have submitted a pull request to implement a policy that anyone running for an elected Fedora Council seat not run for other elected boards at the same time:
The reasoning is that we have an unspoken (for now) expectation that being on the Council, particularly as an elected representative, will not be a trivial commitment. This is an easier check than trying to determine post-election which body a candidate would rather serve on (and thus having to deal with alternates, etc).
Please discuss this on the council-discuss mailing list. Per the Council policy change policy, this will be submitted for a Council vote in two weeks.
Copyright © 2019 Fedora Community Blog
This work is licensed under a Creative Commons Attribution 4.0 International License.
Theme by Anders Noren — Up ↑
Recent Comments