Versions Compared

Old Version 22

changes.mady.by.user Unknown User (sscout)

Saved on

compared with

New Version 23

changes.mady.by.user Kay Schenk

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Submit feedback about the product or website(s). Subscribe to the users mailing list or the developer mailing list. Skills needed: e-mail.
  2. Submit problem reports about the product or website(s). Register for a an Apache OpenOffice Bugzilla account and submit an "issue". Skills needed: ability to learn Bugzilla.
  3. Help existing users. Skills needed: a working knowledge of OpenOffice, and a desire to help other users. Subscribe to the users mailing list, or join the support forum.
  4. Test Developer Builds. See the source code page for more information on testing developer builds. The easiest way to test is to use "Full Installation Sets" for your OS environment. Install to a separate area (directory) so as not to overwrite your existing OOo installation.
  5. Improve the look of our website(s), especially the default landing page.  Skills needed: graphic design, web design, good taste, possible svn.  Skills gained: Markdown syntax, Apache CMS. (Also see the Website information page and Developer FAQ ).
  6. Create a more friendly "Develop" landing page for the website (related to the previous item).   Skills needed: web page authoring including graphic design, svn for committers, or the Apache CMS to submit a page for others. See discussion and proposed mockup from the dev mailing list.
  7. Help market Apache OpenOffice by developing artwork or other marketing materials. See the marketing web site or review the marketing mailing list for more information. Get creative!
  8. Help plan the future of Apache OpenOffice. Subscribe to the developer mailing list and apply for a Apache OpenOffice Planning Wiki account. Skills needed: e-mail, Confluence wiki desirable (but easy to learn). Skills gained: Confluence wiki, cooperation.

...