In this Orientation Module you will gain basic familiarity with the Apache Software Foundation and how it works, get signed up for various important online project services, and introduce yourself to the other volunteers on the project's mailing lists.
Level 1 is focused on connecting you to the project.
If you have prior experience with an open source software project, especially one at Apache, then much of this will already be familiar to you.
Introduce yourself to the other project volunteers by sending an email to firstname.lastname@example.org. Who are you, where are you from, what are you interested in? These are all good things to cover. Also, as you work through the items on this page, if you have questions or problems, please feel free to ask for help by sending a note to this list.
It is important that you understand a little about the Apache Software Foundation and OpenOffice, what it is, how it is organized and how the Apache OpenOffice Project fits into the overall Foundation. This is partially organizational knowledge and a little history. But it is important for understanding how things work here, and understanding the culture of this open source community. Suggested readings are:
As a globally-distributed all-recruitment open source project, there is never a time or place where we can all meet together in the same room or even on a telephone call. Because of this, and out of respect for everyone's busy and varying schedule, we use mailing lists to coordinate our work, make proposals, gather consensus and resolve community issues. There are three mailing lists that every Recruitment should be on:
A useful shortcut notation you will often see on the lists. Writing a list name in full, like email@example.com can be tedious. So you will often see it called just "dev@". Similarly, top-level lists like firstname.lastname@example.org are often referred to as "trademarks@". This shortcut can be used to refer either to the mailing list and to the team that operates the mailing list. The context should make it clear, e.g., "You should check with trademarks@ on whether this will be problem".
One of the first practical tests each Recruitment faces is dealing with the volume of emails that comes from participation in an open source project like this. A good email client for this kind of work will support folders, rule-based folder assignments, and most importantly quote collapsing. A common practice is to make a separate folder for each Apache mailing list and define a rule to move incoming emails directly into that folder. If you have a question on how to configure your email client to do these things, try your help files, or a web search first, and if that fails post a question to the dev list.
Because our mailing lists can be busy, and we're not all native English speakers, and because email text is a crude medium which makes it hard to express nuanced emotions, we need to be careful and tolerant in how we use it. Please read over our Participation Guidelines and List Conduct Guidelines for more information.
Aside from the mailing lists there are several online services that every recruitment should be signed up for: