Revision as of 18:33, 23 August 2009

In addition to the Google Summer of Code program, we are glad to be able to support some additional efforts.

Join the OpenOffice.org Internship

The OpenOffice.org Internship will start on May XX and will stop on September 21.
It is organised to help students with their first or second step in OpenOffice.org code
Also we expect some code and bug fixes contributed.

In te category ToDo, on the OpenOffice.org wiki, you can find many possible tasks for completion during this OpenOffice.org Internship program. http://wiki.services.openoffice.org/wiki/Category:To-Do

But you may propose one yourself, or ask developers at you favorite project's list.

@@ Line 20: / Line 20: @@
 == Possible tasks ==
-Below are listed tasks that can be completed during this OpenOffice.org Internship program.
+In te category ToDo, on the OpenOffice.org wiki, you can find many possible tasks for completion during this OpenOffice.org Internship program.
+http://wiki.services.openoffice.org/wiki/Category:To-Do
 But you may propose one yourself, or ask developers at you favorite project's list.
-=== Writer ===
-Nice tasks to be found at the [[Writer_ToDo | to do list]].
-=== Quality Assurance: [[Release_QA_Tracking_Tool |Release QA Tracking Tool]] ===
-Tracking a release with dozens of languages and several platforms can be tedious. This is especially the case if the only used tool is a manually maintained table with colors indicating the status.
-A web based tool should help us to keep track of the location and status of the builds as well as the responsible contact. The [http://qa.openoffice.org/localized/ workflow] in place should be supported. The tool should provide an [http://qa.openoffice.org/localized/status.html overview], the means to maintain a release including easy status manipulations.
-; Contact
-: dev@qa.openoffice.org
-: Andre Schnabel (Andre.Schnabel at gmx.net)