The Free and Open Productivity Suite
Released: Apache OpenOffice 4.1.14

Native Language Confederation


This page is obsolete. Please visit

About this document

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!

Mission statement

The Native-Language Confederation (NLC) is composed of those projects working on all aspects related to the localization and support of, 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 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 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

How do the NLC projects differ from the l10n project?

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,, 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.

Joining the NLC

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 Guidelines

  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.
    • We ask that you use CSS when possible. For guidelines and information on how the web infrastructure (SourceCast) works, please read the general Style Guide, As well, don't hesitate to use the site help in on the left navbar after you log .

Moving from Level I to Level II

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 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 homepage,, and its new status will be reflected on the other relevant pages.

Responsibilities of Level II projects

Level II projects are centers of community and activity.  They offer support to users of, 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 is explained in the QA Project localization pages.

Marketing 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 list. For marketing, we also use

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

General Guidelines for NLC projects

Project terminus

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.

Problems? Disputes?

For any sort of problem encountered in setting up or managing the project, please contact the leads of NLC and the discussion list,

Disputes sometimes arise. The 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, 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.

Obligatory Mail List



Apache Software Foundation

Copyright & License | Privacy | Contact Us | Donate | Thanks

Apache, OpenOffice, and the seagull logo are registered trademarks of The Apache Software Foundation. The Apache feather logo is a trademark of The Apache Software Foundation. Other names appearing on the site may be trademarks of their respective owners.