Native Language Confederation
Louis Suárez-Potts, Lead
- Our Planet
- About this document
- Mission statement
- How do the NLC projects differ from the l10n project?
- Joining the NLC
- Project Guidelines
- Moving from Level I to Level II
- Responsibilities of Level II projects
- General guidelines
- Problems? Disputes?
- Project Terminus
This document looks complicated but it is not. Forming a language project and joining the Native Language Confederation is a simple, three-step process. If you get lost or confused at any point, we are happy to guide you. Enjoy!
The Native-Language Confederation (NLC) is composed of those projects working on all aspects related to the localization and support of OpenOffice.org, including localization, QA, support, documentation, and marketing. Initially conceptualized and led by Guy Capra, its current mandate is to provide a community wherein those involved in furthering OpenOffice.org in all the world's languages can share resources and information. It is important to note that NLC projects are language not region based. It's equally important to note that we really enjoy what we are doing and think it really important.
The NLC represents one of the key political elements of the OpenOffice.org Project. Its voice is heard in the Community Council, via the elected members representing the NLC. All developers and other contributors who are members of the NLC are invited to participate in the development projects, and to help create OpenOffice.org.
The NLC projects complement the l10n project; all actual localization development takes place within the l10n project. The l10n project is a coding project and discussions on the primary list, L10N@openoffice.apache.org, are in English, as they are for all development projects. The NLC projects provide a "home" for developers and other contributors. Mature NLC projects (Level II) work closely not only with the l10n project but also with Marketing and QA, as well as other development projects.
Every new localization initiative is invited to form a specific localization project and join the NLC. There are two levels of NLC projects, I, and II. All NLC projects working on localizations (some may only be providing support), regardless of their level, are listed both on the l10n project languages page and on the NLC projects page. The project's level is marked on this page.
- Level I: Localization only. Responsible for issuing and QA'ing, if possible, localized builds.
- Level II: Support, documentation, marketing, localization. Responsible for localized builds, QA, as well as related information and marketing.
To learn how to start a new NLC project, see the Protocols for Project Proposal.
- Project creation. We have to create the project for you. There are some considerations, such as the name.
- Projects should be named by the two letters composing the ISO code for the language (not country). If there is no ISO code available, then a combination of two other letters should be made, provided that no conflict with an existing project name nor any other ISO code for language should exist.
- In some cases the ISO code for a language is not known or familiar to the people speaking the language, to the point where such a code would hinder the ability of the new project to attract volunteers (i.e., lack of identification, knowledge and advertising of the project). Provided that no conflict with an existing project name nor any ISO code for language should exist, the new project can choose its own code. However this project cannot choose its code on a geographical basis only; that is the project cannot name itself only according to the country criteria. In case of dispute the NLC leads will name the project themselves.
- We ask that you use CSS when possible. For guidelines and information on how the OpenOffice.org web infrastructure (SourceCast) works, please read the general Style Guide, http://www.openoffice.org/styles/. As well, don't hesitate to use the site help in on the left navbar after you log .
Moving from Level I to II is a significant undertaking but it is worth it. Once a NLC project has deemed itself to be mature, the lead should send a note to firstname.lastname@example.org indicating the desire and ability. The NLC lead and co-lead must approve of the move prior to its being formally included as a Level II project. Upon approval, the NLC project will be listed as offering a supported localization on the OpenOffice.org homepage, http://www.openoffice.org/, and its new status will be reflected on the other relevant pages.
Level II projects are centers of community and activity. They offer support to users of OpenOffice.org, coordinate development, marketing, and help in the QA (testing and quality assurance) of the file. In this way, they ensure their community that the product fully meets their needs. The process for QA'ing OpenOffice.org is explained in the QA Project localization pages. Ideally, all localized files should be QA'd and the status of the QA'ing should be indicated on the QA Track page. If you need information or assistance in setting up a QA effort for localized builds, send a note to email@example.com.
Marketing OpenOffice.org is a complex affair. Much of it is done locally. However, it is important to coordinate both with other members of the NLC as well as with the overall Marketing Project, which hosts the MarCon list for global marketing notices. It is especially important to synchronize work around the time of new releases. To find out when a release is due, check with the firstname.lastname@example.org list. For marketing, we also use email@example.com.
Note: All Level II project leads (and co-leads) must be subscribed to firstname.lastname@example.org. We hold general discussions on this list.
- Level I project engaged in localization only are obligated to use the l10n development list, L10N@openoffice.apache.org. They are also urged to use the l10n Issue Tracker. As needed, more components are made available. The point is to locate, as much as possible, all OpenOffice.org material on the OpenOffice.org website.
- On occasion, we understand that it is impossible for a NLC project to use the provided mail lists and other tools. In these cases, we ask that the project provide monthly (once a month) updates of activity and accomplishments, as well as links to the active project on the OpenOffice.org website.
- For those projects engaged in QA, they should follow the guidelines stipulated on the QA project related to localizations. These are listed here: http://qa.openoffice.org/localized/index.html
- All Level II NLC projects should, at least once a month, post a brief status report on ongoing activities to email@example.com.
Sometimes interest dies in a project. If a NLC project has been inactive—no localization, no significant mail list activity, no visible work—for six (6) months, the NLC lead, Louis Suarez-Potts, will begin the process of closing the project. We begin this process only after having endeavored to contact the lead(s) and try otherwise to revive the project. If nothing works, due warnings will be issued, and the project will be closed; but we will make every effort to preserve valuable material.
For any sort of problem encountered in setting up or managing the project, please contact the leads of NLC and the discussion list, firstname.lastname@example.org.
Disputes sometimes arise. The OpenOffice.org Guidelines suggest how disputes related to management and leadership are to be resolved. Disputes should be settled first within the particular project.
Most changes in leadership are peaceable. In cases of disputes, the project members should set up a vote (the +1 /-1 process is recommended but not required). If a qualified majority of the registered members of the native-lang project agree on their lead's dismissal, the project's lead will have lost his or her position.
Note: As with any project on OpenOffice.org, all NLC project members are entitled to bring grievances before the Community Council. To do so, they should submit the grievance as an agenda item to the wiki.
- We use L10N@openoffice.apache.org for all discussions.
$Date: 2010/11/04 19:36:00 $ $Revision: 1.46 $