Apache software foundation members

Members have a number of rights and responsibilities documented in our Governance guide. This is separate from membership in our many Apache Project Management Committees, who are only responsible for development and community management in their individual project. The membership of the ASF elects the nine-member board to run the foundation, to set policy, and to ensure it is carried out. The directors of the board are:. The Foundation is a collaborative project of the ASF.

Our goal is to build and sustain the literal foundation upon which our open-source software projects are based. We do this by providing services and support for many software project communities consisting of individuals who choose to participate in ASF activities. Since the appointed PMCs have the power to create their own self-governing rules, there is no single vision on how PMCs should run their projects and nurture the communities they lead.

At the same time, while there are some differences, there are a number of similarities all ASF projects share:. Communication is via mailing lists. These are "virtual meeting rooms" where conversations happen asynchronously, which is a general requirement for groups that are distributed across many time zones as is normally the case for Apache communities. Some projects additionally use more synchronous messaging for example, IRC or instant messaging.

Voice communication is extremely rare, normally because of costs and the language barrier speech is harder to understand than written text. In general, asynchronous communication is important because it allows archives to be created and it's more tolerant on the volunteer nature of the various communities.

Each project is responsible for its own project website. Projects are normally auto governing and driven by the people who volunteer for the job. This is sometimes referred to as "do-ocracy" -- power of those who do.

This functions well in most cases. When coordination is required, projects make decisions with a lazy consensus approach: a few positive votes with no negative vote is enough to get going. The rules require that a PMC member registering a negative vote must include an alternative proposal or a detailed explanation of the reasons for the negative vote.

The community then tries to gather consensus on an alternative proposal that can resolve the issue. In the great majority of cases, the concerns leading to the negative vote can be addressed. This process is called "consensus gathering" and we consider it a very important indication of a healthy community. While there is not an official list, people often cite these six principles, often referred to as "The Apache Way", as the core beliefs behind the foundation:.

All ASF projects share these principles. Similarly, Apache projects must govern themselves independently of undue commercial influence.

All participants in ASF projects are volunteers and nobody not even members or officers is paid directly by the foundation to do their job. There are many examples of committers who are paid to work on projects, but never by the foundation itself. Rather, companies or institutions that use the software and want to enhance it or maintain it provide the salary. The ASF does contract out various services, including accounting, Press and Media relations, and infrastructure system administration.

All of the ASF including the board, the officers, the committers, and the members, are participating as individuals. That is one strength of the ASF: personal affiliations do not cloud the person's contributions. Unless they specifically state otherwise, whatever an ASF participant posts on any mailing list is done as themselves.

It is the individual point-of-view, wearing their personal hat and not as a mouthpiece for whatever company happens to be signing their paychecks right now, and not even as a director of the ASF. They sometimes need to talk about a matter of policy, so to avoid appearing to be expressing a personal opinion, they will state that they are talking in their special capacity. However, most of the time this is not necessary: personal opinions work well.

Some people declare their hats by using a special footer to their email, others enclose their statements in special quotation marks, others use their apache. This last method is not reliable, as many people use their apache. We endeavour to conduct as much discussion in public as possible.

This encourages openness, provides a public record, and stimulates the broader community. However sometimes internal private mail lists are necessary. You must never divulge information from such a list in public without the express permission of the list. Also never copy an email between private and public lists no Cc.

Nasdaq 14, Russell 2, Crude Oil Gold 1, Silver CMC Crypto 1, FTSE 7, Nikkei 28, Read full article. Story continues. Whirr , Bigtop , jclouds. Hadoop , Falcon , Hive , Lens. Cocoon , Forrest , Lenya.

Portals , Cocoon , Jackrabbit , Wicket. Sqoop ; Flume. Storm , Hadoop , Spark , Tez. Ant , Gump , Jakarta. Subversion ; httpd. Maven ; Archiva ; Continuum ; Incubator ; board. Maven ; Archiva ; Continuum. Axis2 , Axiom , Neethi. Hadoop , ZooKeeper. Cocoon , Forrest , xml-commons. Sling , Felix , Portals. Subversion , Infrastructure. James , Jakarta , Labs. Lucene , Mahout , Solr. Directory ; Mina. Accumulo , Calcite , Incubator , Phoenix.

HttpComponents , httpd , httpd-docs , incubator , infrastructure. Cxf ; Servicemix ; Karaf ; Camel ; Felix. APR , commons , incubator. Airflow ; Avro ; Parquet ; Druid. ZooKeeper ; BookKeeper ; Incubator. Cocoon ; Xindice.