Apache Community Development

Wednesday November 23, 2016

The Apache Community Development Team Prepares to Send Out its First Diversity Survey

Over the next few weeks the Apache Community Development team will be sending out and running its first ever Apache Software Foundation Committer Diversity Survey. The committer group was selected because they are a significant number of people that are linked to every Apache project.  (NOTE: The ASF currently has 5861 committers across 295 projects.)

Although there are many aspects to diversity including socio-economic, disability and education etc which may be addressed in future surveys, this initial survey will focus on the three broad areas of age, gender and ethnicity. It will also try to capture information about why people contribute to Apache projects. To ensure the confidentiality and privacy of the respondents, the survey will be anonymous and completely voluntary.

Why capture this information?
Many organisations are wanting to find out how effective they are at attracting a diverse range of people. The Apache Software Foundation promotes open, community focussed projects that are welcoming to all, yet have not collected any information to support this. This survey will be an opportunity to capture this information.

The survey results will be used to generate consolidated and aggregated statistics for the Apache Community Development team and the Apache Software Foundation. These details may be published and made publicly available.

When will the survey results be published?
The survey will be run over a two week period and once complete an additional week will be required to consolidate the responses into statistics. Survey results will be announced on the committers and community development mailing lists.

Wednesday March 21, 2012

The Apache Software Foundation Participating in Google Summer of Code 2012 as a Mentoring Organization

The Apache Software Foundation will be participating in the Google Summer of Code again this year as a mentoring organization.

Google Summer of Code is a program where students work on open source projects backed by a stipend granted by Google. The Apache Software Foundation has been participating in the program since its inception in 2005.

Each year, 30-40 students are guided by volunteer mentors from various Apache communities. During the summer they learn what it means to participate in a diverse open source community and develop open source software "The Apache Way". Many of past students are now active contributors to our projects.

This year we hope to build on our previous successes and again build student interest and enthusiasm in The Apache Software Foundation. Our list of project ideas (at http://s.apache.org/gsoc2012tasks) already contains over 100 ideas spanning more than 25 Apache projects. But that's only what we have come up with. A lot of students have their very own itch to scratch and approach our projects with their own ideas.

If you are enrolled as a university student and always wanted to get involved with Apache, here's is your chance. Browse our ideas list, approach the projects you are most interested in, discuss your ideas, get involved, code the summer away, and at the end, get a nice paycheck from Google!

Monday December 20, 2010

Who should use Apache Extras?

Who should host their projects on Apache Extras



Apache Extras is aimed primarily those who are unable or unwilling to licence their code under the Apache License V2, but want to signal their relationship to one or more Apache project community.



One example of this is my own Drupal connector for Apache Wookie (Incubating). This needs to be GPL licensed due to the Drupal dependency, but it contains Apache Licensed code as well. Consequently it cannot be hosted at Drupal, nor can it be hosted at the ASF. Now, with Apache Extras, it has a home that is associated with at least one of those organisations.


A second group of projects that may choose to host on Apache Extras are those who wish to manage their projects in a way that is not aligned with our own collaborative consensus based processes.

Wednesday December 15, 2010

Why Apache Extras?


[Read More]

Tuesday September 21, 2010

How Apache Projects Use Consensus

What are those 'veto' votes about, anyway? What does Apache mean by 'consensus', and how does it foster 'community over code'?

[Read More]

Thursday June 03, 2010

What makes Apache projects different?

Sharing a code repository with some other programmers might seem enough to create an open source project; the Apache Software Foundation goes further and focuses on making projects sustainable in the long term, and ensuring that our code is legally clean.

This means that our projects have to follow a (small) number of rules, and a number of best practices have been established over the years.

Here's a quick description of how Apache projects are born and live on - some of the items below are derived from the ASF's bylaws (http://www.apache.org/foundation/bylaws.html), while others are best practices that evolved over time.

Projects enter the ASF via the Incubator, anyone can suggest a new project as described on the Incubator website (http://incubator.apache.org).

A Project Management Committee (PMC) oversees each project on behalf of its users, contributors, committers and the foundation itself.

New committers and PMC members are elected by the PMC based on merit.

Committers and PMC members are not necessarily ASF members, to be members they have to be elected separately (see "roles" in http://www.apache.org/foundation/how-it-works.html).

Each project has at least one private and one public (development,"dev") mailing list which are the only official communication channels for the PMC members and committers.

Discussions and decisions about people (such as the elections mentioned above) usually happen on the project's private list, but that's not a hard rule, each PMC can decide.

All other decisions happen on the dev list, discussions on the private list are kept to a minimum.

"If it didn't happen on the dev list, it didn't happen" - which leads to:

a) Elections of committers and PMC members are published on the dev list once finalized.

b) Out-of-band discussions (IRC etc.) are summarized on the dev list as soon as they have impact on the project, code or community.

Where possible, decisions are made by consensus. The ASF has voting procedures to help reach this consensus (http://www.apache.org/foundation/voting.html).

Releases are created according to the ASF's release rules (http://www.apache.org/dev/release.html), and all released software uses the Apache License (http://www.apache.org/licenses/).

A formal PMC vote is required to publish a release. By voting to accept the release, the PMC makes the release an act of the foundation, as opposed to a personal action of the the release manager. This is a very important distinction should any legal issues arise.

Each PMC reports to the ASF's board of directors, usually quarterly. The PMC's report mentions progress made and any problems encountered. Items of particular relevance to the board include community activities,
software releases, development work and compliance with the ASF's rules and best practices.

Trademarks and logos used by ASF projects belong to the ASF.

Don't hesitate to ask on the community development mailing list (http://community.apache.org/) if you have questions about this - and in the meantime, have fun at the ASF, commit early and communicate often!

Calendar

Search

Hot Blogs (today's hits)

Tag Cloud

Categories

Feeds

Links

Navigation