Category: Council (page 1 of 3)

Sticky post

Council policy proposal: Community Publishing Platforms

The Fedora Council is considering a new policy to define Community Publishing Platforms. It provides a loose framework of how moderation is handled in cases that involve the Fedora Trademark. The policy as proposed by Justin W. Flory, with edits from the Fedora Council, is found in Fedora-Council/council-docs#67.

Continue reading

Ambassadors Revamp Volunteer Kick-Off

Fedora Mindshare has been actively trying to help Taskforce leads put together volunteers who will be helping revamp the Fedora Ambassador
Program. As a part of this effort, the FCIAC and Taskforce lead put out a survey to folks who expressed interest.

Continue reading

Fedora Council August 2020 meeting

Every year in the days before Flock, the Fedora Council holds a face-to-face meeting. We had expected to do this in Detroit this year, but… you know… COVID. Instead, we held a virtual face-to-face over two half-days. Unlike in past meetings, there was little Big New Idea discussion to have. Instead, this meeting focused on catching up on work in progress. Minutes are available in the Zodbot archives.

Continue reading

Council policy proposal: Process for promoting Fedora deliverable to Edition

With several Fedora deliverables ready (or nearly ready) to be promoted to Edition status, we need a policy for how this will work. After consulting with representatives from QA, Release Engineering, and Fedora IoT, I drafted a proposed process. The Council will begin voting on Tuesday 28 July in accordance with the policy change policy.

If you have feedback, please comment on the council-discuss thread.

Council policy proposal: withdrawing support from events

The Fedora Council is considering a change in policy that better defines how the Council will handle withdrawing from sponsored events. The policy as proposed by Ben Cotton, with edits from the Mindshare Committee is:

The Fedora Council may choose to withdraw Fedora’s support from events or other activities that involve fiscal sponsorship or use of Fedora trademarks when it determines that participation is not in the interests of the Fedora Project. Decisions to withdraw support will be published in venues normally used for Council decisions. Deliberation and reasoning for the decision should be public to the extent possible. The Council will engage with the committee/group/team that is involved with the event in question to ensure their input is considered.

Continue reading

Fedora Council and the git forge

I love the passion the Fedora Project inspires in our community. That passion has been on display in the past week as the community has discussed the decision to move forward with GitLab as our git forge. I want to be very clear: we, the Fedora Council, dropped the ball on communication here. No one intended to be secretive or hide from the community, but we should have done better.

Continue reading

Fedora Council January 2020 in-person meeting

The Fedora Council stuck around Brno the day after DevConf.CZ to have a day-long working session. This is part of our newly-adopted regular cadence of in-person meetings. We mostly used this day to follow up on some items from the November meeting, including the vision statement.

Continue reading

Fedora Council video meeting: Aoife Moloney talks about Red Hat’s CPE team, and we discuss COVID-19 plans

Every month, the Fedora Council holds a recorded video meeting where, in addition to normal business, we have a discussion with someone from the community about the area they work on. This month, we’re joined by Aiofe Moloney from Red Hat’s Community Platform Engineering (CPE) team. She walks us through that team’s workflow and plan for interaction with the community, while Matthew reveals secrets of Red Hat’s internal business organization. We also talk briefly about Fedora’s response to COVID-19 and our upcoming event sponsorships and attendance.

If you have suggestions for a future video meeting guest, please add them to the wish list.

Fedora Council and the future of Modularity

This is part four of a four-part series recapping the Fedora Council’s face-to-face meeting in November 2019.

Since the “should we switch to systemd” discussion has finally settled down, few things have inspired passionate conversations on the devel mailing list like Fedora Modularity. Developing Modularity has been a long process and we finally shipped “Modularity for Everyone” in Fedora 29. But we know there are a lot of rough edges, and it’s not surprising that the response hasn’t been completely enthusiastic. Let’s be honest: we’ve ended up in a situation where a lot of Fedora developers hate Modularity.

The Council agrees that Modularity serves a purpose that we really want to see Fedora, but we also understand the community frustrations. The packager experience is difficult, and handling upgrades needs additional work. We don’t want to throw away the work that’s been done, we want to take what’s there and make it work better.

Continue reading

Let’s keep writing a new vision statement for Fedora

Last month, I shared a draft vision statement that the Fedora Council worked on during our face-to-face meeting in November. We got a lot of great feedback on the council-discuss list. When the Fedora Council met after DevConf.CZ, we went over the feedback and came up with a new draft:

The Fedora Project envisions a world where everyone benefits from free and open source software built by inclusive, welcoming, and open-minded communities.

Continue reading
Olderposts

Copyright © 2020 Fedora Community Blog

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Theme by Anders NorenUp ↑