Difference between revisions of "To-Do List"

Revision as of 20:56, 30 November 2006 (view source) St (Talk | contribs) (add to category todo) ← Older edit		Revision as of 13:55, 8 December 2006 (view source) St (Talk | contribs) m (spelling) Newer edit →
Line 87:		Line 87:
−	[[Category:Development]] [[Category:Todo]]	+	[[Category:Development]] [[Category:To-Do]]

---

Revision as of 13:55, 8 December 2006

Porting

OpenOffice.org Platform Technology: Mac OS X -- Carbon Port with Aqua NWF

Currently the Mac OS X port OpenOffice.org requires an X11 server at runtime. This adds an additional burden to installation, and adds a huge footprint on startup performance. Further on it disables a native look and feel. Providing a port based on Carbon, using an Aqua Native Widget Framework will add tremendously to the acceptance of the Macintosh version and will be a highly visible and well received feature. The project is in need of developers, testers, qa, etc. Contact

   * mac@porting.openoffice.org
   * Eric Bachard (ericb at openoffice.org)

Links for Mac OS X Carbon port

http://wiki.services.openoffice.org/wiki/User:Ericb

http://wiki.services.openoffice.org/wiki/Mac_OS_X_Porting_-_Work_Areas/Todo%27s

Helping push a particular port forward (sparc, arm, netbsd, etc, etc)

Contact

   * dev@porting.openoffice.org
   * Martin Hollmichel (mh at openoffice.org)

Working with affiliated patch trees to speed integration of patches

From the Ximian build system and other third party developers into OOo Contact

   * dev@porting.openoffice.org
   * Martin Hollmichel (mh at openoffice.org), Michael Meeks(mmeeks 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)