User: louis Date: 2007-06-27 21:03:13+0000 Modified: native-lang/www/index.html
Log: changed status to qatrack File Changes: Directory: /native-lang/www/ ============================ File [changed]: index.html Url: http://native-lang.openoffice.org/source/browse/native-lang/www/index.html?r1=1.36&r2=1.37 Delta lines: +2 -2 ------------------- --- index.html 2007-04-03 15:35:56+0000 1.36 +++ index.html 2007-06-27 21:03:11+0000 1.37 @@ -74,7 +74,7 @@ <p class="indent">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> <p class="Header"><a name="responsibilities"></a>Responsibilities of Level II projects</p> <div class="indent"> - <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 in the <a href="http://qa.openoffice.org/localized/status.html";>Status</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>. 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>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> @@ -109,7 +109,7 @@ </ul> <p> </p> <hr> -$Date: 2007/04/03 15:35:56 $ $Revision: 1.36 $ +$Date: 2007/06/27 21:03:11 $ $Revision: 1.37 $ <p> </p> <hr> <p> </p> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
