Last 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 readingThe Fedora Council has been working with the Fedora Community Action and Impact Coordinator to update and improve Fedora’s Code of Conduct. This work began with Brian Exelbierd during his tenure as FCAIC and was then picked up by Marie Nordin at the start of 2020. The new draft of the Code of Conduct is more comprehensive than our current Code of Conduct and will be accompanied by a set of Clarifying Statements. The Clarifying Statements are a work in progress.
Continue readingEarlier this month, Matthew Miller suggested the Fedora Council update the default content license from the Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license to the Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0) license. This license applies to content (not code) submitted to Fedora that does not have an explicit license attached. It does not override the explicit license choices of contributors or upstream projects.
Continue readingThe 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 readingWith 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.
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:
Continue readingThe 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.
Inspired 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 © 2024 Fedora Community Blog
This work is licensed under a Creative Commons Attribution 4.0 International License.
Theme by Anders Noren — Up ↑
Recent Comments