L10N Steering Committee
Fedora Localization Steering Committee (FLSCo)
The Fedora Localization Steering Committee (FLSCo)[[FootNote("FLSCo" is pronounced "flisco" or "full-sco" to avoid confusion with FESCo.)] leads the Fedora Localization Project (FLP).
- Bart Couvreur (vice chair)
- Diego Búrigo Zacarão
- Dimitris Glezos (chair)
- Fabian Affolter
- Marek Mahut
- Noriko Mizumoto
- Piotr Drąg
FLSCo meets often to discuss business at hand. Refer to the L10n Meetings page for more information.
At its core, the purpose of the FLSCo is to make the Fedora Localization Project successful. Its mission is to provide the Fedora translators with necessary guidance, and support their efforts to localize the Fedora Project to multiple languages and cultures.
Some of the goals of the FLSCo:
- To support FLP members who localize Fedora in every possible language
- To provide translators with the necessary infrastructure to contribute translations
- To suggest, motivate, and practice creative ways of bringing Fedora, the Fedora Project, and its sub-projects to people worldwide
To accomplish this, the FLSCo has several key functions, listed below.
Making operational decisions
The committee meets often on IRC (#fedora-l10n on irc.freenode.net at a specific time). The purpose of this meeting is to assign tasks, check on the status of work, help unblock activities or resolve issues, and anything else necessary to keep the project on track.
Committee discussions occur on the email@example.com mailing list (f-trans-l). Meeting notes include summaries and full IRC logs mailed to f-trans-l. A list of links to the archives of the mailed notes may be posted on the wiki.
Maintain a list of active tasks on the project Wiki
The task list can be found at http://fedoraproject.org/wiki/L10N/Tasks.
Practice open and accountable leadership
Because of the danger of self-censorship in a closed or partially open format, it is safer to work entirely in the open.
This is a best practice. If something needs to be discussed on the side to keep the on list flow going, so be it. Consensus reaching is always done on list, and that requires completely open information. Any content (ideas) and work generated off-list should be brought into the sunshine as soon as feasible.
Consensus for FLSCo is defined as agreement by more than 50% of its members. Consensus for the whole FLP always surfaces from the mailing list. No hard percentages have been decided yet.
Consider the long-term strategy of the project.
It is an important part of the leadership of the steering committee to study and act upon long-term strategic objectives to the FLP.
Act within the goals and beliefs of the overall Fedora Project
To be a Fedora project, act like one. Here is the canonical document for Fedora's goals and beliefs: http://fedoraproject.org/wiki/Objectives.
Committee Requirements and Terms of Service
The committee represents the community as a whole. The actions of each of its members form a part of the recognition required to do committee service.
Each member commits to a minimum of one or two full release cycles of active duty on the committee. Active members need to attend meetings to remain active.
The committee chair is the de facto project leader, and serves that role within the Fedora Project.
The committee chair agrees to a two release cycle of duty. The new chair arises from the committee, and has the consensus of the entire committee for the position. Refer to 'Committee Consensus Process' for more on how to do this. A chair may extend the duty another release cycle or two, subject to the vote of the full committee and his acceptance.
As part of their service, the committee should attempt to meet face-to-face at least once per year. This can be at a convention such as FUDCon, FOSDEM, or similar. Such meetings are essential to keeping the human factor intact in what is essentially a human endeavor - free and open information. Whereas this is an official request of FLSCo, use this as leverage wherever you can to get permission and funds to get together with the committee. This is a strong request, rather than a requirement. This is an ongoing effort to make happen.
From time to time, at least once every 3 Fedora releases, the entire membership of FLSCo will stand for re-election. The elections should ensure continuous involvement of the community in the decision-making process, as well as rotation of membership to have inflow of new ideas and views.
Refer to the Elections page for more information on election rules.