If you’re interested in sponsoring the ASF at a higher level, we’d love that too, and I might have a bunch of buttons for you!

You may also see a number of people at ApacheCon featuring giant “Ask Me!” buttons with the Apache feather on them. Please – follow directions, and ask us your questions! A number of knowledgeable members are wearing these buttons, and will be happy to answer your questions about what the larger ASF is all about, and why the organization behind all of our great projects is also important to support.

For those who can’t make it to ApacheCon, please feel free to contact me offline or on the mailing list for your button.

Reminder: Apache and the feather logo are trademarks of The Apache Software Foundation, along with the names of our many projects – and should be used with respect both for the ASF as a whole and for the many committers in our project communities.

In this particular case, much of the growth comes from within existing projects, wherein subprojects communities within Hadoop and Lucene have matured sufficiently to deserve to manage their own fates, and to create their own Project Mangement Committees (PMCs) to take charge. To put this in another perspective, this is also reflective of the ASF’s growth; before this meeting we had over 70 TLPs and over 30 Incubator podlings, so an addition of 6 new TLPs is less than 10% growth for the month.

We should congratulate the Apache Traffic Server community first, since they went through the Incubation process and successfully graduated from an Incubator Podling into their own TLP. Soon to be served (once the website migration is complete) from http://trafficserver.apache.org/, Apache Traffic Server is fast, scalable and extensible HTTP/1.1 compliant caching proxy server. Congratulations to the whole team in showing a strong and diverse community around this new product.

Next up come three subprojects within the well-known Apache Lucene project which have grown organically from modules within Lucene to be diverse and active projects within their own right. You may recognize some of these product names from the Lucene world.

• Apache Mahout, which is building a system for creating scalable and effective machine learning libraries which can perform recommendation mining, clustering, classification, and grouping into itemsets.
• Apache Tika is a toolkit for detecting and extracting metadata and structured text content from various documents using existing parser libraries.
• Apache Nutch, integratable with both Lucene and Hadoop, adds web-specific crawling, fetching, and organization features.

The Apache Hadoop project – another wildly distributed computing technology – has also grown two of it’s subprojects to the point where they deserve their own fame.

• Apache Avro is a fast data serialization system that includes rich and dynamic schemas in all it’s processing.
• Apache HBase is the Hadoop database – designed to provide random, realtime read/write access to Big Data – billions of records – using commodity hardware.

Why did these subprojects spin out to become their own TLPs? The driving factor is not the technology, but rather the community and oversight aspects of how the ASF organizes it’s mostly self-running projects.

From the oversight perspective, the ASF Board relies on every project’s PMC to manage their project’s operations within the broad guidelines of the Apache Way, and to report their project’s progress and issues to the board. This means that there must be enough PMC members who can actively monitor and participate in their project’s activities, and can especially show due diligence and responsibility in voting on any official product releases the project makes. With the rapid growth in both community and technology areas in the Hadoop and Lucene projects, it’s a difficult job for the PMCs to truly understand and help manage all the subprojects they’ve created or added over the past two years.

While the scope of oversight may have hinted that some subprojects should be promoted to TLP status, the gating factor is community. Does a subproject have a strong and diverse enough community to provide their own, independent PMC that can manage their own affairs? Becoming a TLP is both a benefit and a responsibility: the community through it’s new, more focused PMC can better run itself; however the new PMC is also expected to provide accurate reports and responsible oversight of their community and product releases.

Congratulations to all six new projects! Please note that as the websites are updated, each project will be moving it’s home page to http://projectname.apache.org in the near future.

All attendees – heck, even if you’re not attending, but know some of our projects or committers – are welcome to create a profile on the ApacheCon EU 2009 CrowdVine site. Just Create an Account or Login there.

Note that if you have an existing profile on a CrowdVine site and use the same email address to login, it will pull in your existing bio, url, and personal profile.

On the CrowdVine site for ApacheCon, you can sign up for a personalized schedule of the conference, picking which sessions you’d like to attend, and get your own personal iCal. The great thing about clicking the green plus for sessions there is that you’ll be able to see who else at the conference is planning to attend each particular talk.

CrowdVine also offers several different ways to network and communicate, including making friend/fan/want to meet connections with other attendees as well as having an overall and per-session discussion boards for asking speakers questions or giving feedback. It also provides a nice way to see what other projects or communities other people are interested in.