fedora-docs-l10n/council/master/pages/index — Odia @ Fedora Weblate: *Agreement Seeking:* A consensus decision-making process attempts to help everyone …

Translation

Source change

English type: delimited block *

Odia

Needs editing

Skip

	English	Odia	Actions
	{team_name} Charter
	council-logo-500px.png	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]	— ରୁ https://en.wikipedia.org/wiki/Consensus_decision-making#Objectives[ମତୈକ ନିଷ୍ପତି-ନେବା ଉପରେ ଉଇକିପିଡ଼ିଆ ]
	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.
	More significant decisions are made through a process of full consensus. In order to pass, these decisions need three positive votes (+3) and _no_ negative votes (-1). A negative vote immediately halts the process and requires discussion. Therefore, in order to remain valid, negative votes must be supported with a specific concerns about the proposal, and suggestions for what could be changed in order to make the proposal acceptable. A vote of “0” is sometimes used to indicate a disagreement but willingness to stand aside; this should also be accompanied with an explanation.
	This model matches Fedora's “Friends” foundation, which calls for finding acceptable consensus to serve the interests of advancing free software. It works because we work together in a community of mutual respect even when we disagree.
	In general, the {team_name} conducts business in public discussion, and any Fedora project member can make negative or positive votes. It is the duty of the {team_name} to take concerns raised in this way into serious consideration, but only {team_name} members' votes are binding in the final tally.
	When consensus cannot be reached, the {team_name} may ask the xref:fpl.adoc[Fedora Project Leader] to decide on a resolution. Such a request can be made when issues leading to negative votes are outstanding and all {team_name} members agree that the {team_name} is deadlocked, or if the dispute is unresolved after fourteen days and a simple majority of {team_name} members are in favor of the request.
	Composition	ରଚନା
	Community Initiative Leads
	On an ongoing basis, including sessions at Flock and in public online meetings, the {team_name} will identify two to four key xref:project::initiatives.adoc[Community Initiatives] with a timeframe of approximately eighteen months, and appoint Community Initiative Leads for each goal. Each xref:project::initiatives.adoc[Community Initiative] is represented by one {team_name} seat. Typically, this seat is filled by the Lead of the Initiative, although it is possible for two people (at most) to share a single {team_name} seat as Co-Leads. While naturally the people in these roles will focus primarily on their own Initiative, this is a full {team_name} position and Community Initiative Leads are invited to participate in all {team_name} activities and decisions.
	This policy may be surprising, but we have found that this wider engagement connects the specific work to everything going on in Fedora, leading to greater success for the Initiative. Community Initiative Leads may even serve as Executive Sponsors for other Initiatives.

Loading…

None

String updated in the repository

English

Odia 112 characters edited Current translation Needs editing

11 months ago

None

Source string changed

English 1 character edited

11 months ago

Browse all string changes

Things to check

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English	Odia
No related strings found in the glossary.

String information

Source string description

type: delimited block *

Flags

no-wrap

Source string location

pages/index.adoc:43

String age

11 months ago

Last updated

11 months ago

Source string age

11 months ago

Translation file

po/or/master/pages/index.po, string 14