Difference between revisions of "To-Do List"
m (Moved out Tools to-dos into Tools/To-Dos ...) |
(Moved out QA To-Dos into QA/To-Dos) |
||
| Line 6: | Line 6: | ||
=QA= | =QA= | ||
| − | + | {{:QA/To-Dos}} | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
=Stats= | =Stats= | ||
Revision as of 15:33, 19 January 2007
Contents
Porting/To-Dos
Helping push a particular port forward (sparc, arm, netbsd, etc, etc)
Areas to port
* Documentation/DevGuide/AdvUNO/Advanced_UNO * Documentation/DevGuide/GUI/Graphical_User_Interfaces
Contact
* dev@porting.openoffice.org * Martin Hollmichel (mh at openoffice.org)
Tools/To-Dos
Maintaining tinderbox builds for all available platforms
* tinderbox@tools.openoffice.org * Michael Meeks (mmeeks at openoffice.org)
OpenOffice.org Platform Technology: Faster Startup
Probably the most discussed problem since StarOffice 4.0. One first shot would be to optimize library exports. Contact
* dev@tools.openoffice.org * Martin Hollmichel (martin.hollmichel at sun.com)
Code Analysis
Keeping the code flexible, maintainable, extensible, is highly desired. However the current state of the code is quite opaque. Providing tools to detect areas that became or become prone to be examined would be highly desirable. Contact
* dev@tools.openoffice.org * Martin Hollmichel (martin.hollmichel at sun.com)
QA
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)
Official QA'ing of contributed builds
From other locales or lesser known ports
Contact
* dev@porting.openoffice.org or dev@qa.openoffice.org * Kevin Hendricks (khendricks at openoffice.org)
More formal regression testing
Contact
* dev@porting.openoffice.org * Kevin Hendricks (khendricks at openoffice.org)
Bug Tracking System statistics
Provide statistics issues submitted per time, number of active contributors, etc
* dev@tools.openoffice.org * Martin Hollmichel (mh at openoffice.org)
Stats
Source Code Repository Activity
Provide statistics for CVS repository activity. The first step would be a quick analyse what type of statistics other projects are providing. Together with our requirement to better understand how the code base and groups of committers are evolving this should give input to start work on the preparation of some nice stats and graphs about repository activity. Results should be generated with open-source tools, automatically and on a regular basis for the http://stats.openoffice.org website. Additionally an interface to [1] cia would be helpful.
* dev@stats.openoffice.org * Stefan Taxhet (stefan.taxhet at sun.com)
