View source for EN/nlc

{{NLC}}
----
== [[Image:Nlcsmall.png]] Welcome to the Native-Language Confederation Wiki == 



There is a [[List_of_N-L_Projects_Wiki_Pages|long list]] of the Native-Lang projects with wiki pages full of information !

[[NLC:whatshot|What's hot in the NLC?]]

[[NLC:ReleaseChecklist|How to get OpenOffice.org released in my language]]

[[NLC:LanguageList|World Language List for Content Negotiation]]

[[NLC/mission|Roles of Native-Language Project leads]]

[[Languages#Language_localization_status|Languages Localisation status]]
 
-------------------------------------------------------------------------------------------------------------------------------------------------------------

Here you will find some useful information concerning the Native-Language Confederation (NLC) and Projects.

''How to propose a new Native-Language project''
* Visit [http://native-lang.openoffice.org] for administrative information

* Learn how to differentiate between level 1 and 2 native-language projects
Level 2 projects are "regular" native-language projects, while level 1 projects are mostly localization projects (See [http://l10n.openoffice.org] for more info on localization projects] for whose it makes sense to have some web space on OpenOffice.org . These projects are not supposed to design their web site, manage mailing lists, write documentation, but they are encouraged to work on QA.

* Once you have decided what level your project should choose, you have to:
** Assess your resources (human, material, time to devout to the project)
** Check if your language is not already being localized or considered for localization. See [http://l10n.openoffice.org/languages.html] for a comprehensive list of the OpenOffice.org localizations
** Draft and post a proposal on the dev@native-lang.openoffice.org and discuss@openoffice.org lists. Your proposal should describe your goals, your resources and introduce yourself and your team. Please mention what level you wish to give to your project

* Once your project has been accepted by the NLC leads and by the consensus of the native-lang projects' leads, please follow these instructions:
** Indicate the desired domain name for your project: it should be the two or three letters corresponding to the ISO code of your language. BEWARE: Native-Lang projects are based on languages, not on countries!
** Indicate your OpenOffice.org username and if necessary your co-lead's username
** Register yourself to the NLC 
** Indicate if you signed and sent/faxed the SCA See: [http://www.openoffice.org/FAQs/faq-licensing.html]
** The NLC leads will open an issue that may take some time to be approved (not more than 10 days) then your project will be set up. 

''Now you need to submit your ssh keys and work with CVS''

Whether it is for editing your website or contribute code, OpenOffice.org uses CVS. It is actually the same CVS platform that is being used for both the website and the development platform. In order to be able to use OpenOffice.org's CVS and access your new native-lang project's website you need to:
* Open an issue (separate from the issue opening your new native-language project) and file it as follows: component "www" and subcomponent "openoffice.org website general issues" with your key in attachment. Assign it to "ssh2key". Also make sure to specify what part of the website you want to work with. In the NLC case, that would be your new native-lang project, so specify the two letters forming the domain name of your new project. For example, if your project is http://xy.openoffice.org, specify "xy". If your project is http://xyz.openoffice.org, specify "xyz"
* Read [http://www.openoffice.org/scdocs/ddCVS.html.en] to learn how to use the CVS.

You are ready to go!

'' Initiatives of the Native-Lang Confederation ''


''' Wiki Pages of Native-Lang Projects'''

Some of Native-Lang Confederation Projects started to use this wiki for organizing parts of their work. You can access these wiki pages from the
[[List of N-L Projects Wiki Pages]]
[[Category:Project]]