fedora-docs-l10n/council/master/pages/index — Chinese (Simplified) (zh_CN) @ Fedora Weblate: Fedora Operations Architect

Translation

Source change

English type: Title ====

Chinese (Simplified) (zh_CN)

Needs editing

Skip

	English	Chinese (Simplified) (zh_CN)	Actions
	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.
	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
	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
	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.
	Elections are held twice a year, in concert with the joint Fedora election cycle. One seat is selected at each election, and each position has a two-election (approximately one year) term. No person who currently holds another {team_name} seat can be elected. If a seat becomes vacant, the {team_name} will arrange for a temporary replacement.
	Appointed Leadership Positions
	Fedora Project Leader (FPL)
	The xref:fpl.adoc[Fedora Project Leader] (FPL) serves as the chair of the {team_name}, organizing discussion agendas, bringing issues to the table, and facilitating the consensus process. He or she is accountable for success in all areas of the project, but is not a dictator, benevolent or otherwise. The FPL often serves as the public face and collective voice of the project, and has a corresponding duty to listen to, understand, and fairly represent the collective views and needs of project contributors and stakeholders.
	The Fedora Project Leader is hired by Red Hat with the advice and consent of the {team_name}.
	Fedora Community Architect (FCA)	Fedora 社区架构师 (FCA)
	The xref:fca.adoc[Fedora Community Architect] (FCA) works to grow the Fedora user and developer communities, and to make Red Hat / Fedora interactions even more transparent and positive. The Fedora community budget comes to us through the Red Hat Open Source Program Office, and this position facilitates decision-making on how to best focus that to meet our collective objectives.
	Fedora Operations Architect	Fedora 社区架构师 (FCA)
	The xref:foa.adoc[Fedora Operations Architect] (FOA) is employed full-time by Red Hat to assist the community in managing technical changes. This includes oversight of the Change process, schedule management, communications, and ownership of key strategic efforts. They also assist with the creation, improvement, maintenance, and execution of formal, repeatable Fedora processes. Additionally, the Fedora Operations Architect serves as record-keeper and secretary for Fedora Council Meetings.
	Coda
	Meetings
	The {team_name} is not driven by meetings or by tickets, but does hold link:{FWIKI}/Council_Meetings[regular public meetings] (via a chat system or video call). The {team_name} discusses current issues, clear through anything outstanding which can be quickly resolved, and to ensure that nothing urgent is left pending. All members are expected to regularly communicate what is going on in their area, through blog posts or other public updates.
	The {team_name} holds a multi-day, face-to-face meeting annually. All members should strive to attend in person (travel funding is available). We also often meet for a day before or after other significant Fedora-related conferences (Flock, DevConf.cz). These meetings are not public, but minutes and summary documents will be provided.
	Additionally, the xref:fpl.adoc[Fedora Project Leader] will set aside regular times to meet with the community. Attendance is not mandatory for all {team_name} members but is encouraged.
	Transparency
	The general policy of the {team_name} is to default to open. Most meetings are held in public channels, and open to all Fedora users and contributors. Discussion is held in a link:{team_asynch_communication}[public forum] open to all, and formal decisions will be recorded in a public ticket tracking system.
	Occasionally, when personal, private, or sensitive issues need to be discussed, a video call might be used. A private mailing list and ticket tracking instance also exist for these situations, but will also only be used when dealing with these uncommon issues.
	Time Commitment
	Serving on the {team_name} is a significant commitment of time and energy. Workload for the various roles will vary, but each will require a number of hours every week, and in most cases, the more, the better a {team_name} member is able to do the job fully.
	We recognize that most Fedora community members do not have the luxury of working on Fedora full-time or as part of a paid position. The time commitment required for these roles comes simply from what is required to lead a large project like Fedora, and is not intended to be an artificial limit on who can participate. We know that that it can be a _pragmatic_ limit, and for that reason, the {team_name} is responsible for extra effort to receive, recognize, be responsive to, and meaningfully reward the input of contributors offering their individual time.
	Governance Philosophy
	To advance free software, we need to provide a sustainable integration of free software without cutting corners. By providing a positive first impression before and during installation and real use, we support Fedora's reputation as a leading and reliable product that attracts future users and contributors. To provide that integration and experience we must have a clear set of priorities to help all contributors decide how to allocate resources and resolve conflicts. These priorities are not meant to be exclusive, or to keep contributors from working on the parts of Fedora that matter to them.
	These priorities will sometimes expose gaps where contributors need additional assistance, and allow them to seek it both within the community and by bringing in additional contributors to help, exclusively on their particular interest area if desired. While narrowing our focus in some areas, though, we must provide opportunities for exploration to all contributors within the framework of our core values and without impeding progress.

Loading…

None

String updated in the repository

English

Chinese (Simplified) (zh_CN) 18 characters edited Current translation Needs editing

4 months ago

None

Source string changed

English 15 characters edited

4 months ago

Browse all string changes

Things to check

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Chinese (Simplified) (zh_CN)
No related strings found in the glossary.

String information

Source string description

type: Title ====

Flags

no-wrap

Source string location

pages/index.adoc:159

String age

4 months ago

Last updated

4 months ago

Source string age

6 months ago

Translation file

po/zh_CN/master/pages/index.po, string 49