Difference between revisions of "OpenOffice.org Internship"
m (fix link) |
|||
| Line 1: | Line 1: | ||
| − | In addition to the [[Summer of Code | + | In addition to the [[Summer of Code 2009|Google Summer of Code]] program, we are glad to be able to support some additional efforts. |
__TOC__ | __TOC__ | ||
| + | |||
| + | = 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. | ||
| + | |||
| + | == How to apply == | ||
| + | |||
| + | * mail to ?? | ||
| + | * write on ?? | ||
| + | * find you a mentor and ask a go for your proposal | ||
| + | |||
| + | == Terms & Conditions == | ||
| + | * | ||
| + | |||
| + | == Possible tasks == | ||
| + | |||
| + | Below are listed tasks that can be completed during this OpenOffice.org Internship program. | ||
| + | But you may propose one yourself, or ask developers at you favorite project's list. | ||
=== Quality Assurance: [[Release_QA_Tracking_Tool |Release QA Tracking Tool]] === | === Quality Assurance: [[Release_QA_Tracking_Tool |Release QA Tracking Tool]] === | ||
Revision as of 22:31, 13 May 2009
In addition to the Google Summer of Code program, we are glad to be able to support some additional efforts.
Contents
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.
How to apply
- mail to ??
- write on ??
- find you a mentor and ask a go for your proposal
Terms & Conditions
Possible tasks
Below are listed tasks that can be completed during this OpenOffice.org Internship program. But you may propose one yourself, or ask developers at you favorite project's list.
Quality Assurance: 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 workflow in place should be supported. The tool should provide an overview, the means to maintain a release including easy status manipulations.
- Contact
- dev@qa.openoffice.org
- Andre Schnabel (Andre.Schnabel at gmx.net)
