Date: Tue, 19 Mar 2024 03:24:22 +0000 (UTC)
Message-ID: <1945981457.54054.1710818662103@cwiki-he-fi.apache.org>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_54053_903947157.1710818662103"
------=_Part_54053_903947157.1710818662103
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Help Wanted
Help Wanted
We are looking for volunteers to do the following tasks. But ple=
ase do not feel limited to these items. For inspiration on other ideas we r=
ecommend reading "=
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 no=
te to the dev@openoffice.apache.org mailing list and we can give you hints =
on how to accomplish the task.
Easy
- Submit feedback about the product or website(s). Subsc=
ribe to the users mailing list or the developer mailing list. Skills needed: e-mail.
- 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.=
li>
- Help existing users. Skills needed: a working knowledg=
e of OpenOffice, and a desire to help other users. Subscribe to the users mailing list, or join the support forum=
a>, or help users that write to the Facebook page.
- Test Developer Builds. See the sour=
ce code webpage for more information on testing developer builds. The e=
asiest way to test is to use "Full Installation Sets" for your OS environme=
nt. Install to a separate area (directory) so as not to overwrite your exis=
ting AOO installation.
- Improve the look of our website(s), especially the def=
ault landing page. Skills needed: graphic design, web=
design, good taste, possible svn. Skills gained: Markdown syntax, Apache C=
MS. (Also see the Website information page an=
d Developer FAQ ).
- Create a more friendly "Develop" landing page for the website (=
related to the previous item). Skills needed: webpage authoring in=
cluding graphic design, svn for committers, or the Apach=
e CMS to submit a webpage for others. See discussion and proposed mocku=
p from the developer mailing list.
- Help market Apache OpenOffice by developing artwork or=
other marketing materials. See the marketing webpage or=
review the marketing mailing list for more informatio=
n. Get creative!
- Help plan the future of Apache OpenOffice. Subscribe t=
o 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: Conflu=
ence wiki, cooperation.
Medium
- Write Documentation. This includes user guides, instal=
l guides and developer documentation. Documentation is found in the documen=
tation area of the OpenOffice wiki. To participate through the OpenOffice Documentation Wiki, register for an Apache OpenOffice Community Wiki account. Skil=
ls needed: familiarity with, or willing to learn Media Wi=
ki. Skills gained: more wiki experience, group collaboration.
- Update the OpenOffice Adm=
inistration Guide.
- Develop a trademark approval process. This would be us=
ed by the PMC for external entities that want to use our trademarks. Write =
up the process, review with Apache Branding, and get consensus on the ooo-d=
ev 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 email. Skills gai=
ned: greater understanding of Apache branding requirements.
- Write up a tutorial (or link to a good existing one) that expla=
ins how new project volunteers should create and submit patches (f=
or publication on the Project website). Skills needed: an understanding of =
Markdown and probably committer rights to the project website. (Already som=
ewhat done on the Developer FAQs webpage).=
li>
- Write up a tutorial on how committers should review and apply p=
atches. Add a link to this tutorial from the Developer FAQs webpage. Skills needed: SVN, technical writi=
ng. Skills gained: Apache CMS.
- Document the procedures used by the PMC. This would in=
clude the processes: how to elect new committers and PMC members, including=
form letters, userid generation, tracking, etc. Link it from the PMC FAQs webpage on the website. Consider the steps t=
hat the PMC needs to do, as well as the new committer, so this can be a ref=
erence for both. Skills needed: writing. Skills gained: Apache =
CMS. Note: this task is suitable for existing PMC members only.
Challenging
- Document or find tools. Specifically, external diff an=
d merge tools for Subversion that can process ODF documents.
- Fix bugs, create and update OpenOffice. Skills needed:=
an Apache OpenOffice Bugzilla account, git or=
github knowledge, C++ (Apache OpenOffice is mainly written in C++, though =
there is some code in Java and Python). See the =
Developer FAQ to get started.
- Build ApacheOffice from source. We can use feedback on=
the build process. Skills needed include familiarity with C++, and your sy=
stem's batch or shell processing capabilities. See the Source Control webpage for more information on obtaining and build=
ing Apache OpenOffice.
------=_Part_54053_903947157.1710818662103--