DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
Foundation organization and governance structure (https://www.apache.org/foundation/governance/)
The ASF is an operating a US 501(c)3 organization that supports 3 non-profit charity that acts as a steward for several hundred open source projects. The operating part ASF is one of the ASF is managed by the President, supported by the Treasurer, Vice Presidents, committees and third parties. The ASF board provides oversight for operating functions as well as ASF project communities. The Legal Affairs, Security, and Treasurer departments report directly to the board, which means, for example that the Security team acts with the authority of the board.largest open source organizations in the world, and is home to prolific projects just as Hadoop, Tomcat, Cassandra, and scores of others. The ASF provides a known and vetted set of governance, intellectual property, and release processes as well as providing a vendor-neutral place for contributors to collaborate. However, within those processes there is a high degree of autonomy for each project. Projects decisions are driven by the people doing the work. The ASF Board of Directors is responsible for project oversight, ensuring the health and vitality of each project.
In brief numbers the ASF has:
- 227 Million lines of code
- 630,000+ contributors
- 8,370+ committers (individuals who have earned the status of being able to directly change source code.
- 200+ projects
How project oversight works (https://www.apache.org/foundation/how-it-works.html)
ASF projects are run by Project Management Committees (PMCs). PMC members nominate and vote on new PMC members and collectively manage community, security, trademarks, or other problems. The PMC plays a key role in technical project oversight, but not the only role. The full project community contributes by working creating and reviewing patches and contributing to discussion.All ASF community members, including PMC members, officers and the board, participate in our communities as individuals, not as representatives of companies or other organizations. Some community members
The ASF regards all contributors as individuals and volunteers as part of its vendor neutrality. We do this despite the fact that many, if not most, of our contributors are paid by their employers to contribute to ASF projects but in their ASF work they are expected to projects at the ASF. As part of that neutrality, we expect that all ASF contributors act in the best interest of the community, exercising their own best judgement. Impact on project decisions is based on publicly earned merit which accrues to individuals, based only on their contributions at the ASF.project. Additionally, who a contributor works for has no bearing on their standing in any particular project community. Contributors earn different levels of project standing based on their contributions to the project.
...
ASF projects differ in how they do things, but most have documented process for working bug reports, introducing new features and planning and executing releases. As new features are developed and bugs are addressed, code changes are made that will go into releases. Typically, proposed changes are submitted as “pull requests” (PRs) that explicitly describe how the source code will change if they are applied. The original source, the PR and any changes that result from applying it are all publicly visible. Any interested party can comment on proposed changes and it frequently happens that performance, security or other issues are discovered in the open development process that creates and modifies ASF software.
...