fedora-docs-l10n/council/master/pages/index — English @ Fedora Weblate: Responsibilities

Zen

	English	Actions
	{team_name} Charter
	council-logo-500px.png
	{team_summary}
	The {team_name} is composed of a mix of representatives from different areas of the project, named roles appointed by Red Hat, and a variable number of seats connected to medium-term project goals. Decisions are made by a consensus process, in which we work together as a common team to find shared solutions and address concerns, with a focus on giving voice rather than on balance of power.
	The {team_name} is ultimately accountable for the Fedora Project as a whole, and is responsible for providing advice to and oversight of other Fedora governance bodies and teams as needed.
	Responsibilities
	The {team_name} is responsible for issues of strategic importance for Fedora that require leadership and coordination across the various teams and sub-projects to achieve. Its primary role is to identify the short, medium, and long term goals of the Fedora community and to organize and enable the project to best achieve them. This is done in consultation with the entire Fedora community through transparent, public discussion.
	{team_name} members engage with people across the community to make sure Fedora is functioning smoothly and that teams are empowered to do interesting and meaningful things. They decide on issues regarding use of the Fedora trademarks, are responsible for final arbitration of complaints related to project policies and for settling disputes escalated from other committees or subgroups. They may handle sensitive legal or personnel issues which require research and discussion to protect the interests of the Fedora Project or its sponsors.
	To support project efforts with more ambitious scope, the {team_name} sponsors xref:project::initiatives.adoc[Community Initiatives] proposed by the community. {team_name} members serve as xref:project::initiatives.adoc#proposing-sponsors[Executive Sponsors] for these Initiatives, working personally to ensure that the <<composition\--initiative-leads,Leads>> have everything they need to succeed.
	The {team_name} governs Fedora’s financial resources, working with our sponsor to establish an annual budget allocated to support these Initiatives, various Fedora teams and programs, Fedora-managed events, and other activities which advance the Fedora Strategy.
	The {team_name} is also responsible for developing, tracking, and updating the Fedora Strategy.
	Making Decisions
	Consensus decision-making aims to be:
	Agreement Seeking: A consensus decision-making process attempts to help everyone get what they need.
	Collaborative: Participants contribute to a shared proposal and shape it into a decision that meets the concerns of all group members as much as possible.
	Cooperative: Participants in an effective consensus process should strive to reach the best possible decision for the group and all of its members, rather than competing for personal preferences.
	Egalitarian: All members of a consensus decision-making body should be afforded, as much as possible, equal input into the process. All members have the opportunity to present, and amend proposals.
	Inclusive: As many stakeholders as possible should be involved in the consensus decision-making process.
	Participatory: The consensus process should actively solicit the input and participation of all decision-makers.
	— from https://en.wikipedia.org/wiki/Consensus_decision-making#Objectives[Wikipedia on Consensus decision-making]
	Many basic decisions are made through a process known as “lazy approval”, in which general consent is assumed unless valid objections are raised within a period of time — generally three to seven days, although the timeframe should be stated each time and should be proportionate to the impact of the action. This process is used for decisions with short-term consequences and which can be easily reversed. Any project member can ask for the deadline to be extended or the decision escalated to require full consensus.

Loading…

No matching activity found.

Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Inconsistent: Catalan, Czech, Finnish, French, Odia, Portuguese (Portugal), Swedish, Turkish, Ukrainian

Reset

Glossary

English	English
No related strings found in the glossary.

String information

Source string description

type: Title ==

Flags

no-wrap, read-only

Source string location

./pages/index.adoc:16

String age

4 years ago

Last updated

11 months ago

Source string age