Difference between revisions of "OpenOffice.org Internship"

From Apache OpenOffice Wiki
Jump to: navigation, search
(initial set up - QA tracking added)
 
m (fix link)
Line 1: Line 1:
In addition to the [[SummerOfCode2006 | Google Summer of Code]] program, we are glad to be able to support some additional efforts.  
+
In addition to the [[Summer of Code 2007|Google Summer of Code]] program, we are glad to be able to support some additional efforts.  
  
 
__TOC__
 
__TOC__
Line 7: Line 7:
 
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.
 
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/index.html 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.
+
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
 
; Contact
 
: dev@qa.openoffice.org
 
: dev@qa.openoffice.org
 
: Andre Schnabel (Andre.Schnabel at gmx.net)
 
: Andre Schnabel (Andre.Schnabel at gmx.net)

Revision as of 20:40, 1 September 2007

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

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)
Personal tools