Difference between revisions of "To-Do List"
From Apache OpenOffice Wiki
(→Porting: Extracted into Porting/To-Dos) |
m (Relativated ...) |
||
| Line 1: | Line 1: | ||
| − | + | =Porting/To-Dos= | |
{{:Porting/To-Dos}} | {{:Porting/To-Dos}} | ||
| − | + | =Tools= | |
| − | + | ==Maintaining tinderbox builds for all available platforms== | |
* tinderbox@tools.openoffice.org | * tinderbox@tools.openoffice.org | ||
* Michael Meeks (mmeeks at 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. | Probably the most discussed problem since StarOffice 4.0. One first shot would be to optimize library exports. | ||
| Line 17: | Line 17: | ||
* Martin Hollmichel (martin.hollmichel at sun.com) | * 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. | 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. | ||
| Line 25: | Line 25: | ||
* Martin Hollmichel (martin.hollmichel at sun.com) | * Martin Hollmichel (martin.hollmichel at sun.com) | ||
| − | + | =QA= | |
| − | + | ==Official QA'ing of contributed builds== | |
From other locales or lesser known ports | From other locales or lesser known ports | ||
| Line 35: | Line 35: | ||
* Kevin Hendricks (khendricks at openoffice.org) | * Kevin Hendricks (khendricks at openoffice.org) | ||
| − | + | ==More formal regression testing== | |
Contact | Contact | ||
| Line 42: | Line 42: | ||
* Kevin Hendricks (khendricks at openoffice.org) | * Kevin Hendricks (khendricks at openoffice.org) | ||
| − | + | ==Bug Tracking System statistics== | |
Provide statistics issues submitted per time, number of active contributors, etc | Provide statistics issues submitted per time, number of active contributors, etc | ||
| Line 49: | Line 49: | ||
* Martin Hollmichel (mh at 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 [http://cia.navi.cx] cia would be helpful. | 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 [http://cia.navi.cx] cia would be helpful. | ||
| Line 59: | Line 59: | ||
| − | + | [[Category:Development]] [[Category:To-Do]] | |
Revision as of 15:18, 19 January 2007
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
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
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)
