Author: buildbot
Date: Wed Jul 4 19:41:19 2018
New Revision: 1032105
Log:
Staging update by buildbot for ooo-site
Modified:
websites/staging/ooo-site/trunk/cgi-bin/ (props changed)
websites/staging/ooo-site/trunk/content/ (props changed)
websites/staging/ooo-site/trunk/content/native-lang/index.html
Propchange: websites/staging/ooo-site/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 4 19:41:19 2018
@@ -1 +1 @@
-1835027
+1835083
Propchange: websites/staging/ooo-site/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jul 4 19:41:19 2018
@@ -1 +1 @@
-1835027
+1835083
Modified: websites/staging/ooo-site/trunk/content/native-lang/index.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/native-lang/index.html (original)
+++ websites/staging/ooo-site/trunk/content/native-lang/index.html Wed Jul 4
19:41:19 2018
@@ -55,7 +55,7 @@
<p>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!</p>
<h2>Mission statement </h2>
<p>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.</p>
-<p>The NLC represents one of the key political elements of the OpenOffice.org
Project. Its voice is heard in the <a
href="http://council.openoffice.org/";>Community Council</a>, via the <a
href="http://council.openoffice.org/#nlc";>elected members</a> 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. </p>
+<p>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. </p>
<h2><a name="notl10n"></a>How do the NLC projects differ from the l10n
project? </h2>
<p>The NLC projects complement the <a href="http://l10n.openoffice.org/";> l10n
project</a>; all actual localization development takes place within the l10n
project. The l10n project is a coding project and discussions on the primary
list, <a
HREF="mailto:[email protected]";>[email protected]</a>, 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.</p>
<h2><a name="joining"></a>Joining the NLC </h2>
@@ -91,7 +91,7 @@
<p>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 <a
HREF="mailto:[email protected]";>[email protected]</a>
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, <a
href="http://www.openoffice.org/";>http://www.openoffice.org/</a>, and its new
status will be reflected on the other relevant pages. </p>
<h2><a name="responsibilities"></a>Responsibilities of Level II projects</h2>
<div>
- <p>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 <a
href="http://qa.openoffice.org/localized/";>QA Project localization
pages</a>. Ideally, all localized files should be QA'd and the status of
the QA'ing should be indicated on the <a
href="http://qatrack.services.openoffice.org/view.php";>QA Track</a> page.
If you need information or assistance in setting up a QA effort for localized
builds, send a note to <a
href="mailto:[email protected]";>[email protected]</a>.
</p>
+ <p>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 <a
href="http://qa.openoffice.org/localized/";>QA Project localization
pages</a>.</p>
<p>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 <a
href="http://marketing.openoffice.org/";>Marketing Project</a>, 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 <em>when</em> a
release is due, check with the <a
href="mailto:[email protected]";>[email protected]</a> list. For
marketing, we also use <a
href="mailto:[email protected]";>[email protected]</a>.</p>
<p><strong>Note</strong>: All Level II project leads (and co-leads) must be
subscribed to <a
href="mailto:[email protected]";>[email protected]</a>.
We hold general discussions on this list.</p>
</div>
