Zen

Translation

English type: Title ==
Composition
11/110 · 11

Sign in to save the translation.

English French Actions
The {team_name} is also responsible for developing, tracking, and updating the Fedora Strategy.
 
Making Decisions
Prise de décisions
Consensus decision-making aims to be:
La prise de décision par consensus a pour but d’être :
*Agreement Seeking:*
A consensus decision-making process attempts to help everyone get what they need.
*Une recherche d’accord :* un processus de décision par consensus tente d’aider chacun à obtenir ce dont il a besoin.
*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.
*Collaboratif :* les participants contribuent à une proposition commune et la façonnent en une décision qui répond autant que possible aux préoccupations de tous les membres du groupe.
*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.
*Coopératif :* les participants à un processus de consensus efficace doivent s’efforcer de parvenir à la meilleure décision possible pour le groupe et tous ses membres, plutôt que de se faire concurrence pour des préférences personnelles.
*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.
*Égalitaire :* tous les membres d’un organe décisionnel de consensus devraient, dans la mesure du possible, avoir une participation égale au processus. Tous les membres ont la possibilité de présenter et d’amender des propositions.
*Inclusive:*
As many stakeholders as possible should be involved in the consensus decision-making process.
*Inclusif :* le plus grand nombre possible de parties prenantes doit être impliqué dans le processus de décision par consensus.
*Participatory:*
The consensus process should actively solicit the input and participation of all decision-makers.
*Participatif :* le processus de consensus devrait activement solliciter la contribution et la participation de tous les décideurs
— from https://en.wikipedia.org/wiki/Consensus_decision-making#Objectives[Wikipedia on Consensus decision-making]
— de la page https://en.wikipedia.org/wiki/Consensus_decision-making#Objectives[Wikipédia sur la Prise de décision par consensus]
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.
De nombreuses décisions de base sont prises par le biais d’un processus appelé « *approbation paresseuse* », dans lequel le consentement général est présumé sauf si des objections valables sont soulevées dans un certain délai — généralement de trois à sept jours, bien que le délai doive être indiqué à chaque fois et soit proportionnel à l’impact de l’action. Ce processus est utilisé pour les décisions ayant des conséquences à court terme et qui peuvent être facilement annulées. Tout membre du projet peut demander que le délai soit prolongé ou que la décision soit portée à un niveau supérieur pour exiger un consensus complet.
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.
Les décisions les plus importantes sont prises par un processus de *plein consensus*. Pour être adoptées, ces décisions doivent recueillir trois votes positifs (+3) et _aucun_ vote négatif (-1). Un vote négatif interrompt immédiatement le processus et nécessite une discussion. Par conséquent, pour rester valables, les votes négatifs doivent être accompagnés de préoccupations spécifiques concernant la proposition et de suggestions sur ce qui pourrait être modifié pour rendre la proposition acceptable. Un vote de « 0 » est parfois utilisé pour indiquer un désaccord avec une volonté de s’écarter de la discussion ; il doit être accompagné d’une explication.
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.
Ce modèle correspond à la fondation « Friends » de Fedora, qui appelle à trouver un consensus acceptable pour servir les intérêts de la promotion du logiciel libre. Il fonctionne parce que nous travaillons ensemble dans une communauté de respect mutuel, même lorsque nous ne sommes pas d’accord.
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.
En général, le Conseil mène ses activités dans le cadre de débats publics, et tout membre du projet Fedora peut émettre un vote négatif ou positif. Il est du devoir du Conseil de prendre sérieusement en considération les préoccupations soulevées de cette manière, mais seuls les votes des membres du Conseil sont contraignants dans le décompte final.
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.
Lorsqu’un consensus ne peut être atteint, le Conseil peut demander au chef du projet Fedora de décider d’une résolution. Une telle demande peut être faite lorsque des questions conduisant à des votes négatifs sont en suspens et que tous les membres du Conseil conviennent que le Conseil est dans l’impasse, ou si le litige n’est pas résolu après quatorze jours et qu’une majorité simple des membres du Conseil est en faveur de la demande.
Composition
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.
 
Community Initiative Leads typically serve on the {team_name} for the duration of their Initiative. When the Initiative concludes, the {team_name} term also expires.
 
Each Community Initiative Lead is paired with an xref:project::initiatives.adoc#proposing-sponsors[Executive Sponsor], who is another member of the {team_name}.
 
Community Initiatives must be documented with measurable goals. The Community Initiative Leads are responsible for coordinating efforts to reach those goals, evaluating and reporting on progress, and working regularly with all relevant groups in Fedora to ensure that progress is made. xref:project::initiatives.adoc#proposing-sponsors[Executive Sponsors] are responsible for making sure the Initiative is on track and for removing blockers.
Chaque objectif sera documenté avec des cibles atteignables et le responsable d'objectif a la responsabilité de coordonner les efforts pour atteindre ces cibles, évaluant et rapportant l'avancement et travaillant régulièrement avec tous les groupes concernés dans Fedora pour assurer l'avancement.
Representatives
Représentants
The {team_name} also includes five representative seats: an *Engineering Representative*, a *Mindshare Representative*, a xref:dei:roles:council-advisor.adoc[*DEI Advisor*], and two *Elected Representatives*.
Le Conseil inclut également quatre sièges de représentants, un « représentant ingénieurie », un « représentant Mindshare » et deux « représentants élus ».
Engineering & Mindshare Representatives
 
“Engineering” and “Mindshare” are broad areas roughly encompassing two of the major areas of activity in Fedora. _Engineering_ is the technical work related to building and releasing the Fedora operating system and the infrastructure related to that. _Mindshare_ includes marketing, design, and Fedora Ambassadors — largely activities that happen between Fedora and the world at large, with the distribution release cycle serving as a fuel source, not the thing that's being worked on.
 
The engineering and mindshare representatives' responsibility is to represent their areas collectively, _not_ to be just an individual voice that happens to be voted-in by some subset of Fedora. They are selected by contributors working in those areas, under the rules of the xref:fesco::Fedora_Council_Engineering_Rep.adoc[Fedora Engineering Steering Committee (FESCo)] and the xref:mindshare-committee::procedures/council_rep.adoc[Mindshare Committee], respectively.
 
Diversity, Equity, & Inclusion (DEI) Advisor
Conseiller Diversité, équité et inclusion (DEI)
The xref:dei:roles:council-advisor.adoc[*Fedora Diversity, Equity, & Inclusion (DEI) Advisor*] is a liaison between the {team_name} and the Fedora community on topics and issues related to diversity, equity, and inclusion in Fedora. The DEI Advisor works with {team_name} leadership to represent perspectives and voices of the Fedora community in decision-making and project discussions. This position is appointed by members of the xref:dei::index.adoc[Fedora DEI Team], with the approval of the {team_name}.
 
Elected Representatives
Représentants élus
The elected positions cover all Fedora subprojects that are not under the engineering or mindshare banners, and the community at large. One specific responsibility is to represent the voice of individual contributors to the Fedora Project. Each representative will also work on specific goals which they bring to the {team_name} as highlighted during the election process.
 

Loading…

User avatar julroy67

Translation added
Composition
Composition
4 years ago
User avatar None

Source string added
Composition
5 years ago
Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English French
No related strings found in the glossary.

314 String information

Source string description
type: Title ==
Flags
no-wrap
Source string location
pages/index.adoc:79
String age
5 years ago
Last updated
a year ago
Source string age
5 years ago
Translation file
po/fr/master/pages/index.po, string 26