This document is descriptive, not normative. It aims to help those who are new to the Incubator learn its ways and netiquette.

The usual advice applies. If you are not familiar with the way mailing lists work at Apache, read this.

Please ensure that your mail client is correctly configured. In particular, post only plain text emails to these lists. Apache spam filters may reject HTML emails.

The incubator is a public meeting place with a diverse and ever-changing community. Creating social bonds and establishing a reputation is important. Please be polite, courteous and diplomatic.

When in doubt - ask on general.AT.incubator.apache.org.

The general.AT.incubator.apache.org is an public list with open subscription. All are encouraged to subscribe, read and post their opinions in the usual way.

Anyone can by their words influence the decision-making process and may vote on VOTE threads. However (as is usual) only the votes of those on the Incubator PMC are binding.

A user is anyone who uses our software. Most Apache projects have active user communities who are willing to provide help. This is not always the case with incubator podlings.

To gain the maximum benefit from any immature project (as many podlings are), adopt an active attitude. Read On Contributing and Understanding Open Source. Become a developer (in the Apache meaning of the term).

At Apache, a developer (aka contributor) is anyone who actively helps to develop our software. This includes more than just coders and documenters. For example, anyone who joins in discussions on the mailing lists or answers questions from users is also a developer.

Apache is a DO-ocracy. The first step along the road leading to committership is to become a developer. For more information start with How Apache Works and the developer documentation.

A committer is anyone with write access to the source repository. Election to committership in the Incubator works a little differently from the process that is usual elsewhere at Apache.

Once a podling has been bootstrapped, developers are nominated and election to committer happens in the usual way.

When a proposal is just a candidate, there are two possible approaches (for those interested in committership).

The proposal typically contains a list of initial committers. When a podling is bootstrapped, this list is used by the mentors to set up initial accounts. So, one way to become a committer for a podling is to be listed on the proposal as an initial committer.

The right way to express interest is by a post to the list with a brief introduction. Piling onto a proposal (by adding your own name as an initial committer) is impolite. Read this thread.

A podling needs to learn how to recruit new committers from its developers. So, another way is to show up on the list and start helping with the development. This path will help the podling more than adding your name to the list of initial committers.

Anyone with knowledge of open source or Apache can participate as a informal mentor for a podling. Development is open and anyone with an interest is encouraged to subscribe.

Eligibility to act as a formal Mentor is limited. The best way for an eligible individual to become a Mentor is to post a note introducing him- or herself and volunteering their services to general.AT.incubator.apache.org during the development of the proposal.

Apache Members are encouraged to join the Incubator PMC. Post a note to the Incubator PMC private list.

Those who aren't members may be elected in the usual Apache way (though this is rare). Typically these elections are held on private lists.