Space: Apache OpenOffice Community (https://cwiki.apache.org/confluence/display/OOOUSERS) Page: Help Wanted (https://cwiki.apache.org/confluence/display/OOOUSERS/Help+Wanted)
Edited by Kay Schenk: --------------------------------------------------------------------- We are looking for volunteers to do the following tasks. But please do not feel limited to these items. For inspiration on other ideas we recommend reading "[14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star|http://www.softwarequalityconnection.com/2012/03/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/]."; If you are interested in working on any of these items, please send a note to the ooo-...@incubator.apache.org list and we can give you hints on how to accomplish the task. h2. Easy # *Submit feedback about the product or website(s).* Subscribe to the [users mailing list|mailto:ooo-users-subscr...@incubator.apache.org] or the [developer mailing list|mailto:ooo-dev-subscr...@incubator.apache.org]. Skills needed: e-mail. # *Submit problem reports about the product or website(s)*. Register for a an [Apache OpenOffice Bugzilla|http://incubator.apache.org/openofficeorg/bug-tracking.html] account and submit an "issue". Skills needed: ability to learn Bugzilla. # *Help existing users*. Skills needed: a working knowledge of OpenOffice, and a desire to help other users. Subscribe to the [users mailing list|mailto:ooo-users-subscr...@incubator.apache.org], or join the [support forum|http://user.services.openoffice.org/]. # *Test Developer Builds*. See [the source code page|http://incubator.apache.org/openofficeorg/source.html] 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. # *Improve the look of the our website(s)*, especially the default [landing page|http://incubator.apache.org/openofficeorg/index.html]. Skills needed: graphic design, web design, good taste, possible svn. Skills gained: Markdown syntax, Apache CMS. (Also see the [Website information page|http://incubator.apache.org/openofficeorg/website-local.html] and [Developer FAQ|http://incubator.apache.org/openofficeorg/developer-faqs.html] ). # *Help market Apache OpenOffice* by developing artwork or other marketing materials. See the [marketing web site|http://www.openoffice.org/marketing] or review the [marketing mailing list|http://incubator.apache.org/openofficeorg/mailing-lists.html] for more information. Get creative\! # *Help plan the future of Apache OpenOffice.* Subscribe to the [developer mailing list|mailto:ooo-dev-subscr...@incubator.apache.org] and apply for a [Apache OpenOffice Planning Wiki account|https://cwiki.apache.org/confluence/display/OOOUSERS/Wiki+Home]. Skills needed: e-mail, Confluence wiki desirable (but easy to learn). Skills gained: Confluence wiki, cooperation. h2. Medium # *Write Documentation.* This includes user guides, install guides and developer documentation. Documentation is found in the documentation area of the OpenOffice wiki. To participate through the [OpenOffice Documentation wiki|http://wiki.services.openoffice.org/wiki/Documentation], register for an [Apache OpenOffice Community wiki account|http://wiki.services.openoffice.org/wiki/Documentation]. Skills needed: familiarity with, or willing to learn [Media Wiki|http://www.mediawiki.org/wiki/MediaWiki]. Skills gained: more wiki experience, group collaboration. # Update the [OpenOffice Administration Guide|http://wiki.services.openoffice.org/wiki/Documentation/Administration_Guide]. # *Develop a trademark approval process.* This would be used by the PPMC for external entities that want to use our trademarks. Write up the process, review with Apache Branding, and get consensus on the ooo-dev list. Add the process definition to the Community FAQ's on the website. Things to consider include criteria for approval and record keeping. A good starting point might be [this |http://markmail.org/message/r6ud3wtajm5ryvwi] email. Skills gained: greater understanding of Apache branding requirements. # *Write up a tutorial (or link to a good existing one) that explains how new project volunteers should create and submit patches* (for publication on the Project website). Skills needed: an understanding of Markdown and probably committer rights to the project website. (Already somewhat done on the [Developer FAQs page|http://incubator.apache.org/openofficeorg/developer-faqs.html] ). # *Write up a tutorial on how committers should review and apply patches.* Add a link to this tutorial from the [Developer FAQs|http://incubator.apache.org/openofficeorg/developer-faqs.html] page. Skills needed: SVN, technical writing. Skills gained: Apache CMS. # *Document the procedures used by the PPMC.* This would include the processes: how to elect new committers and PPMC members, including form letters, userid generation, tracking, etc. Link it from the [PPMC FAQs|http://incubator.apache.org/openofficeorg/ppmc-faqs.html] page on the website. Consider the steps that the PPMC needs to do, as well as the new committer, so this can be a reference for both. Skills needed: writing. Skills gained: Apache CMS. Note: this task is suitable for existing PPMC members only. h2. *Challenging* # *Document or find tools*. Specifically, external diff and merge tools for Subversion that can process ODF documents. # *Fix bugs, create and update OpenOffice.* Skills needed: an [Apache OpenOffice Bugzilla account|http://incubator.apache.org/openofficeorg/bug-tracking.html], subversion (svn) knowledge, C+\+ (Apache OpenOffice is mainly written in C++, though there is some code in Java and Python). See [the Developer FAQ|http://incubator.apache.org/openofficeorg/developer-faqs.html] to get started. # *Build ApacheOffice from source*. We can use feedback on the build process. Skills needed include familiarity with C++, and your system's batch or shell processing capabilities. See the [Source Control|http://incubator.apache.org/openofficeorg/source.html] page for more information on obtaining and building Apache OpenOffice. Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action
