Contents

• 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

Links

• How to start a new project
• Templates (for setting up a project)
• Mail lists & archives (all)
• Obligatory Lists
• Document & Files
• Membership (how to change roles)
• Release Checkist

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.

1. 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.
2. Content. The Protocols give guidelines on content for all projects. But for Level II projects, and for those projects focused on support and documentation only, there are templates you are encouraged to use (and enhance). These are located in the Files and Documents section of the NLC homepage, http://native-lang.openoffice.org/servlets/ProjectDocumentList.
   • 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 .

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 dev@native-lang.openoffice.org.

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 releases@openoffice.org list. For marketing, we also use com@native-lang.openoffice.org.

Note: All Level II project leads (and co-leads) must be subscribed to dev@native-lang.openoffice.org. We hold general discussions on this list.

For any sort of problem encountered in setting up or managing the project, please contact the leads of NLC and the discussion list, dev@native-lang.openoffice.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.