Index
Links: 2012 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
March 21, 2012
1. Call to order
The meeting was scheduled for 10:00am (Pacific) and began at
10:04 when a sufficient attendance to constitute a quorum was
recognized by the chairman. The meeting was held via
teleconference, hosted by Doug Cutting and Cloudera.
IRC #asfboard on irc.freenode.net was used for backup purposes.
2. Roll Call
Directors Present:
Shane Curcuru
Doug Cutting
Bertrand Delacretaz
Roy T. Fielding
Jim Jagielski
Dan Kulp
Brett Porter
Sam Ruby
Greg Stein
Directors Absent:
none
Executive Officers Present:
Craig L Russell
Executive Officers Absent:
Noirin Plunkett
Guests:
Hadrian Zbarcea
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of February 15, 2012
See: board_minutes_2012_02_15.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Doug]
The board recently accepted the resignation of director Larry
Rosen. In resigning Larry cited differences in the appropriate
strategy and tactics for the foundation with the majority of
the board. We thank Larry for his service to the foundation
serving on the board and wish him well.
B. President [Jim]
There are has been quite a bit of active and tense communication on
many of the public ASF mailing lists. Kudos to those who have
tried to defuse these threads before they become too damaging.
I am very pleased to see that we appear to be on an even keel again
regarding our books and treasury duties. I am also happy to report
that our EA continues to be utilized and valued.
I will send a "final" reminder to PMCs and cmmt's today regarding
the budget calls. All budget updates are due by the end of this
month in expectation of a submittal to, and approval of, the board
next month.
I have somewhat of a concern over the response of the fundraising
team. Some emails and queries sent to fundraising (both internal
as well as external) have been ignored or un-seen, and the fact that,
as of this writing, we still have not rec'd a report does not give me
a warm and fuzzy feeling.
On a similar note, I am quite interested in seeing Concom's
report since I know there has been quite a bit of activity within
the last few weeks.
In general, foundation-wise, we are operating well.
C. Treasurer [Sam]
All bills are paid. All contractors are paid. A 1099 was sent to
Melissa. No taxes are due at this time.
I'm documenting the process as I go. Once the situation is under
control I plan to identify an Assistant Treasurer and make use of the
existing EA.
My next priority is producing reports. I have a copy of QuickBooks.
D. Secretary [Craig]
February was a busy month in secretary land. 60 ICLAs, three CCLAs,
and three grants were received and recorded. If there is enough
information regarding a new committer, in either the ICLA form
itself, or in the email to which the ICLA is attached, then the
new account request will be created upon filing of the ICLA.
In February, six accounts were requested to be created as part of
the ICLA filing process.
E. Executive Vice President [Noirin]
No report was submitted.
F. Vice Chairman [Greg]
I've done a bit of fundraising work, but otherwise a quiet month.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of Brand Management [Shane Curcuru]
See Attachment 1
B. VP of Fundraising [Serge Knystautas / Brett]
See Attachment 2
C. VP of Marketing and Publicity [Sally Khudairi / Roy]
See Attachment 3
D. VP of W3C Relations [Sam Ruby]
See Attachment 4
E. Apache Legal Affairs Committee [Sam Ruby]
See Attachment 5
F. Apache Security Team Project [Mark Cox / Sam]
See Attachment 6
G. Apache Conference Planning Project [Nick Burch / Bertrand]
See Attachment 7
AI Sam follow up with specific advice on how to get legal help
H. Apache Infrastructure Team [Sam Ruby]
See Attachment 8
I. Apache Travel Assistance Committee [Gavin McDonald / Shane]
See Attachment 9
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
A. Apache ACE Project [Marcel Offermans / Doug]
See Attachment A
B. Apache APR Project [Jeff Trawick / Jim]
See Attachment B
C. Apache Archiva Project [Maria Odea Ching / Greg]
See Attachment C
D. Apache Axis Project [Andreas Veithen / Sam]
See Attachment D
E. Apache BVal Project [Matt Benson / Brett]
See Attachment E
F. Apache C++ Standard Library Project [Martin Sebor / Doug]
See Attachment F
approved, and expect a report next month.
G. Apache Camel Project [Christian Mueller / Shane]
See Attachment G
H. Apache Cayenne Project [Andrus Adamchik / Greg]
See Attachment H
I. Apache Chemistry Project [Florian Müller / Jim]
See Attachment I
J. Apache Click Project [Malcolm Edgar / Roy]
See Attachment J
K. Apache Commons Project [Luc Maisonobe / Bertrand]
See Attachment K
AI: Daniel Kulp draft an ASF policy for projects which need to
re-bundle other Apache projects
L. Apache Continuum Project [Emmanuel Venisse / Roy]
No report was submitted.
AI: Brett follow up with PMC
M. Apache CouchDB Project [Jan Lehnardt / Bertrand]
See Attachment M
N. Apache Empire-db Project [Francis De Brabandere / Doug]
See Attachment N
O. Apache Felix Project [Richard Hall / Jim]
See Attachment O
AI: Jim ask for details on new committers and PMC members
P. Apache Gora Project [Lewis John McGibbney / Greg]
See Attachment P
Q. Apache Gump Project [Stefan Bodewig / Brett]
See Attachment Q
R. Apache Hive Project [John Sichi / Shane]
See Attachment R
S. Apache Incubator Project [Jukka Zitting / Sam]
See Attachment S
T. Apache Jackrabbit Project [Jukka Zitting / Shane]
See Attachment T
U. Apache Karaf Project [Jean-Baptiste Onofré / Greg]
See Attachment U
V. Apache Labs Project [Tim Williams / Bertrand]
See Attachment V
W. Apache Logging Project [Curt Arnold / Brett]
See Attachment W
X. Apache Lucene Project [Simon Willnauer / Doug]
See Attachment X
Y. Apache OFBiz Project [Jacopo Cappellato / Sam]
See Attachment Y
Z. Apache OODT Project [Chris A. Mattmann / Roy]
See Attachment Z
AA. Apache OpenNLP Project [Joern Kottmann / Jim]
See Attachment AA
AB. Apache OpenWebBeans Project [Gurkan Erdogdu / Sam]
See Attachment AB
AC. Apache Pig Project [Daniel Dai / Brett]
See Attachment AC
AD. Apache Pivot Project [Sandro Martini / Doug]
See Attachment AD
AE. Apache Portals Project [David Sean Taylor / Shane]
See Attachment AE
AF. Apache ServiceMix Project [Guillaume Nodet / Jim]
See Attachment AF
AG. Apache Shiro Project [Les Hazlewood / Bertrand]
See Attachment AG
AH. Apache Sling Project [Carsten Ziegeler / Roy]
See Attachment AH
AI. Apache SpamAssassin Project [Daryl C. W. O'Shea / Greg]
No report was submitted.
AI: Greg to pursue a report for SpamAssassin
AJ. Apache Synapse Project [Paul Fremantle / Jim]
See Attachment AJ
AK. Apache Tiles Project [Greg Reddin / Sam]
See Attachment AK
AL. Apache Tomcat Project [Mladen Turk / Greg]
See Attachment AL
AM. Apache UIMA Project [Marshall Schor / Bertrand]
See Attachment AM
AN. Apache Whirr Project [Tom White / Brett]
See Attachment AN
AO. Apache Wicket Project [Martijn Dashorst / Doug]
See Attachment AO
AP. Apache XML Project [Gianugo Rabellino / Roy]
No report was submitted.
AI: Shane prepare a resolution to move XML to the Attic
AQ. Apache XMLBeans Project [Cezar Andrei / Shane]
No report was submitted.
AR. Apache ZooKeeper Project [Mahadev Konar / Roy]
See Attachment AR
AS. Apache Thrift Project [Bryan Duxbury / Bertrand]
See Attachment AS
AI: Bertrand ask the PMC to update the web site "now"
AT. Apache OpenJPA Project [Pinaki Poddar / Brett]
See Attachment AT
AU. Apache Mahout Project [Jeff Eastman / Greg]
See Attachment AU
AI: Shane ask PMC to update agenda
AV. Apache JAMES Project [Norman Maurer / Sam]
See Attachment AV
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Establish the Apache Lucy Project
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of open
source software, for distribution at no charge to the public,
related to providing full-text search for dynamic programming
languages.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Lucy Project", be
and hereby is established pursuant to Bylaws of the Foundation;
and be it further
RESOLVED, that the Apache Lucy Project be and hereby is
responsible for the creation and maintenance of software
related to providing full-text search for dynamic programming
languages; and be it further
RESOLVED, that the office of "Vice President, Apache Lucy" be
and hereby is created, the person holding such office to serve
at the direction of the Board of Directors as the chair of the
Apache Lucy Project, and to have primary responsibility for
management of the projects within the scope of responsibility
of the Apache Lucy Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Lucy Project:
* Logan Bell <logie@apache.org>
* Brad C. Harder <bch@apache.org>
* Marvin Humphrey <marvin@apache.org>
* Peter Karman <karpet@apache.org>
* Nathan Kurz <nate@apache.org>
* Dan Markham <dmarkham@apache.org>
* Mike McCandless <mikemccand@apache.org>
* Joe Schaefer <joes@apache.org>
* Upayavira <upayavira@apache.org>
* David E. Wheeler <theory@apache.org>
* Nick Wellnhofer <nwellnhof@apache.org>
* Simon Willnauer <simonw@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Peter Karman be
appointed to the office of Vice President, Apache Lucy, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification, or
until a successor is appointed; and be it further
RESOLVED, that the initial Apache Lucy PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Lucy Project; and be it further
RESOLVED, that the Apache Lucy Project be and hereby is tasked
with the migration and rationalization of the Apache Incubator
Lucy podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Lucy podling encumbered upon the Apache Incubator
Project are hereafter discharged.
Special Order 7A, Establish the Apache Lucy Project, was
approved by Unanimous Vote of the directors present.
B. Establish the Apache Rave Project
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to the public,
related to a widgets-based, web-and-social mashup platform.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Rave Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Rave Project be and hereby is
responsible for the creation and maintenance of software
related to a widgets-based, web-and-social mashup platform;
and be it further
RESOLVED, that the office of "Vice President, Apache Rave" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Rave Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Rave Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Rave Project:
* Ard Schrijvers <ard@apache.org>
* Ate Douma <ate@apache.org>
* Bas Zoetekouw <bas@apache.org>
* Gerald Guo <zhguo@apache.org>
* Hadrian Zbarcea <hadrian@apache.org>
* Jasha Joachimsthal <jasha@apache.org>
* Jesse Ciancetta <jcian@apache.org>
* Joost van Dijk <joostvandijk@apache.org>
* Maarten Kremers <mkremers@apache.org>
* Marlon Pierce <mpierce@apache.org>
* Matt Franklin <mfranklin@apache.org>
* Niels van Dijk <cthings@apache.org>
* Okke Harsta <oharsta@apache.org>
* Raminder Singh <raminder@apache.org>
* Ross Gardler <rgardler@apache.org>
* Sander van der Waal <svanderwaal@apache.org>
* Scott Wilson <scottbw@apache.org>
* Sean Cooper <secooper@apache.org>
* Suresh Marru <smarru@apache.org>
* Tony Carlucci <carlucci@apache.org>
* Unico Hommes <unico@apache.org>
* Venkat Mahadevan <venkatm@apache.org>
* Woonsan Ko <woonsan@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matt Franklin
be appointed to the office of Vice President, Apache Rave, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the initial Apache Rave PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Rave Project; and be it further
RESOLVED, that the Apache Rave Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Rave podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Rave podling encumbered upon the Apache Incubator
Project are hereafter discharged.
Special Order 7B, Establish the Apache Rave Project, was
approved by Unanimous Vote of the directors present.
C. Establish the Apache Sqoop Project
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to the public,
related to efficiently transferring bulk data between Apache Hadoop
and structured datastores.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Sqoop Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Sqoop Project be and hereby is
responsible for the creation and maintenance of software
related to efficiently transferring bulk data between Apache
Hadoop and structured datastores; and be it further
RESOLVED, that the office of "Vice President, Apache Sqoop" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Sqoop Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Sqoop Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Sqoop Project:
* Aaron Kimball <kimballa@apache.org>
* Andrew Bayer <abayer@apache.org>
* Ahmed Radwan <ahmed@apache.org>
* Arvind Prabhakar <arvind@apache.org>
* Bilung Lee <blee@apache.org>
* Greg Cottman <gcottman@apache.org>
* Guy le Mar <guylemar@apache.org>
* Jaroslav Cecho <jarcec@apache.org>
* Jonathan Hsieh <jmhsieh@apache.org>
* Olivier Lamy <olamy@apache.org>
* Paul Zimdars <pzimdars@apache.org>
* Roman Shaposhnik <rvs@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Arvind Prabhakar
be appointed to the office of Vice President, Apache Sqoop, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the initial Apache Sqoop PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Sqoop Project; and be it further
RESOLVED, that the Apache Sqoop Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Sqoop podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Sqoop podling encumbered upon the Apache Incubator
Project are hereafter discharged.
Special Order 7C, Establish the Apache Sqoop Project, was
approved by Unanimous Vote of the directors present.
D. Establish the Apache Accumulo Project
WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to the public,
related to a robust, scalable, distributed key/value store with
cell-based access control and customizable server-side processing.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Accumulo Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Accumulo Project be and hereby is
responsible for the creation and maintenance of software
related to a robust, scalable, distributed key/value store with
cell-based access control and customizable server-side processing
and be it further
RESOLVED, that the office of "Vice President, Apache Accumulo" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Accumulo Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Accumulo Project; and be it further
RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Accumulo Project:
* Aaron Cordova <acordova@apache.org>
* Adam Fuchs <afuchs@apache.org>
* Billie Rinaldi <billie@apache.org>
* Chris Waring <cawaring@apache.org>
* Eric Newton <ecn@apache.org>
* Keith Turner <kturner@apache.org>
* David Medinets <medined@apache.org>
* John Vines <vines@apache.org>
* Benson Margulies <bimargulies@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Billie Rinaldi
be appointed to the office of Vice President, Apache Accumulo, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further
RESOLVED, that the initial Apache Accumulo PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Accumulo Project; and be it further
RESOLVED, that the Apache Accumulo Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Accumulo podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Accumulo podling encumbered upon the Apache Incubator
Project are hereafter discharged.
Special Order 7D, Establish the Apache Accumulo Project, was
approved by Unanimous Vote of the directors present.
E. Change the Apache ServiceMix Project Chair
WHEREAS, the Board of Directors heretofore appointed Guillaume Nodet
to the office of Vice President, Apache ServiceMix, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Guillaume Nodet from the office of Vice President,
Apache ServiceMix, and
WHEREAS, the Project Management Committee of the Apache ServiceMix
project has chosen by vote to recommend Gert Vanthienen as the
successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Guillaume Nodet is relieved and
discharged from the duties and responsibilities of the office
of Vice President, Apache ServiceMix, and
BE IT FURTHER RESOLVED, that Gert Vanthienen be and hereby is
appointed to the office of Vice President, Apache ServiceMix, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification, or
until a successor is appointed.
Special Order 7E, Change the Apache ServiceMix Project Chair,
was approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Appoint a new Director to fill the empty board seat
Daniel Kulp was appointed to fill the empty board seat.
B. Naming Noirin Plunkett as Assistant Treasurer.
Sam would like to offload some of the workload.
Tabled.
C. Audit plans? Or plan for a plan?
There is no legal requirement for annual audits based on ASF annual revenues.
Usually the audit committee is chaired by the Treasurer.
Audit done by a smaller accounting firm would be $10K; larger firms would charge $20k - $30K.
Hadrian volunteered to start by looking at the books.
9. Review Outstanding Action Items
* Craig: see that Olio provenance is complete and start retirement process.
Status: Provenance is complete; retirement in process
* Doug: pursue a report for Continuum.
Status: Sent a message to chair & PMC. No response or
report in evidence.
* Greg: discuss security handling with DB PMC.
Status: Personal concern; now timed out; can be closed.
* Greg: pursue a report for Fundraising.
Status: Done.
* Greg: pursue a report for Click.
Status: Report has been submitted.
* Jim: prepare a resolution to create a VP of OSI.
Status: Awaiting agreement from OSI
* Sam: follow up on /dist with Perl PMC
Status: I'm not pursuing it, can be closed
* Sam: follow up with Zookeeper PMC re: adoption of Curator project
Status: can be closed, Curator decided to pursue other alternatives
* Shane: discuss legal trademark issues with ActiveMQ PMC.
Status: In progress this week; can be closed.
* Shane: pursue a report for CouchDB.
Status: Done, see attached
10. Unfinished Business
11. New Business
12. Announcements
Jim was elected to be a director of OSI.
13. Adjournment
Adjourned at 11:06 a.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management
Apologies for a late report.
Operations And Community
========================
Calling for volunteers to work in an organized fashion to review
branding status for all TLPs. It's clear that a more active approach
with specific PMCs that have not reported completion is needed.
Meeting with counsel from DLAPiper to work on reviewing basic policies,
get cost figures (for next year's budget request which will be higher),
and to organize which tasks that need counsel support versus can
be done by volunteers with training.
Worked with CouchDB PMC to make suggestions for the PMC to deal with
specific Couch-* named product by third party.
The recently detailed Incubator podling name search guidelines have
been very helpful for several new podlings to review the suitability
of their names in a organized fashion; many thanks to the IPMC members
who put that guide together!
External Requests
=================
Signed release for use of Apache OpenOffice as set dressing in a
major US company motion picture. Thanks to AOO
PPMC for the approval and DLAPiper counsel for legal review.
Trademark Registrations
=======================
Waiting for meeting with DLAPiper, expect more news next month.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising
The fundraising@ group has received a resignation request from Serge,
who has found his available time is insufficient for continuing with
the VP Fundraising role. The mailing list is discussing potential
replacements and hope to provide the Board with a candidate for its
April meeting.
Inquiries from sponsors continue to get handling by the volunteers on
fundraising@, and we have signed up two new (bronze-level) sponsors.
The group is working to establish some better management of our set of
sponsors and their renewal date. We expect the new VP to help plan
and execute on that, with a comprehensive report to the Board in the
May or June timeframe.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity
I. Budget: All outstanding payments have been made with kind
assistance from Sam Ruby and Jim Jagielski.
II. Fundraising/Branding/Marketing liaison: no official meetings
or discussions have taken place or are currently being planned.
III. Press Releases: the following formal announcements were issued
during this timeframe --
- The Apache Software Foundation Announces Apache ACE as a Top-Level
Project
- The Apache Software Foundation Celebrates the 17th Anniversary of
the Apache HTTP Server with the release of v2.4
- The Apache Software Foundation Announces Apache Deltacloud as a
Top-Level Project
IV. Informal Announcements: the following items were announced on
@TheASF Twitter feed --
-11 Mar: The #Apache #HTTP #Server now powers 420+M Websites globally
--23 million sites more over last month per @Netcraft survey!
#TheApacheWay
-01 Mar: LAST CALL: Request for Proposals for #ApacheCon
North America (submit through 8 March) http://s.apache.org/oh
#OpenSource #conference #RFP
-28 Feb: New! Apache HTTP Server Usage
Survey results are in! How do you use the #Apache #Server?
s.apache.org/jy #httpd #TheApacheWay
-27 Feb: The Apache Software
Foundation Announces #Apache #ACE as a Top-Level Project s.apache.org/u5
#OSGi #Cloud #TheApacheWay
-23 Feb: Learn about #Apache #Rave in
"Code Well & Prosper with OSS Foundations: How Apache + Eclipse
Help Developers Succeed!" s.apache.org/MhZ
-21 Feb: The Apache
Software Foundation Celebrates the 17th Anniversary of the #Apache
#HTTP #Server with the release of v2.4 s.apache.org/je
-16 Feb: The
ASF Announces #Apache #Deltacloud as a Top-Level Project s.apache.org/my
#CloudComputing #OpenSource #TheApacheWay #Cloud
V. Future Announcements: those PMCs wishing to announce major project
milestones please contact Sally Khudairi at press@apache.org for
more information. Kindly provide at least 2-week's notice for proper
planning and execution.
VI. Media Relations: overall in maintenance mode; reactive press
interaction and coordinating some longer-lead requests.
VII. Analyst Relations: we've received requests from a handful of
analysts outside our usual briefing pool to be added to our media
outreach lists.
VIII. ApacheCon liaison: no active initiatives currently undertaken
aside from reminders for the RFP closing date.
IX. (Non-ASF) Industry Events and Outreach liaison: all quiet over
the past month.
X. Newswire accounts: we have decided to extend our relationship
with PRNewswire as they agreed to carry our pre-paid press release
balance through 2013. Project press releases will be primarily
disseminated over the NASDAQ GlobeNewswire service using our new
pre-paid package (via the HALO Worldwide account), with Foundation-level
announcements and statements requiring specialty distribution (e.g.
country/region-specific) sent over PR Newswire.
-----------------------------------------
Attachment 4: Report from the VP of W3C Relations
Jeremias Märki joined the Print and Page Layout Community Group.
Larry Rosen left the HTML5 working group (he still participates in the PSIG).
-----------------------------------------
Attachment 5: Status report for the Apache Legal Affairs Committee
DLA Piper LLP's engagement letter has been signed and filed. It looks like we
are settling quickly to a split where DLA Piper handles Trademarks affairs,
which means that I likely will treat the SFLC as primary for all other legal
matters. Of course, this is just the 'default', individual circumstances can
influence this on a case by case basis.
Discussions that the board should be aware of:
Adobe's RTMP specification license (LEGAL-120). Not clear yet whether it is
something we need to worry about, whether or not it amounts to a Field of
Use restriction. If the latter, it appears that our intended use is not one
that would be permitted.
Aggregation of GPL dictionaries with Apache Open Office was approved
(LEGAL-117)
The Army initially determined the Apache License, version 2.0 was
incompatible with the Antideficiency Act. They later determined that this
was not something they needed to worry about.
Multiple separate conversations about contributions that were previously
made available elsewhere. Two easy cases: smallish and self contained
single author code bases need nothing more than an ICLA from that
contributor; established projects with multiple contributors need either a
Software Grant or documentation that identifies how the accepting [P]PMC
came to the conclusion that all of the contributors have been identified and
that they have given their approval. Additionally, larger code bases or
code bases with multiple contributors will also have to be verified as free
of unacceptable dependencies. Ultimately, this may lead to a major update
to the so-called "Short Form" for Intellectual Property Clearance at the
Incubator.
All in all, this was an active month in that there were quite a number of
other threads. Overall these were largely without controversy, and no board
action is required at this time.
-----------------------------------------
Attachment 6: Status report for the Apache Security Team Project
For February 2012: There continues to be a steady stream of reports of
various kinds arriving at security@. These continue to be dealt with
by the security team.
5 Support question
2 Security vulnerability question, but not a vulnerability report
6 Vulnerability reports, of which:
1 [xerces, via security@apache.org]
1 [httpd, via security@apache.org]
2 [stuts, via security@struts.apache.org]
1 [tomcat, via security@tomcat.apache.org]
1 [poi, via security@apache.org]
Reminder: vulnerability handling process explained at
http://apache.org/security/committers.html
-----------------------------------------
Attachment 7: Status report for the Apache Conference Planning Project
Small Events
------------
A "BarCamp" was held over two days in Colombo, Sri Lanka, at the end of
February. There was a lot more interest than expected, with numbers limited to
200 on the first day, 100 on the 2nd. The large numbers meant the format of the
event was changed last minute, to more Roadshow style one. This had a mixed
effect, which was discussed with the organisers by Nick and Ross. Everyone who
attended seemed to find it interesting and useful, and there was a lot of
energy, especially on the 1st day (lots of students / recent graduates). We
hope to see more events, big and small from these organisers in the future.
Work on the DC BarCamp for May is continuing nicely. Lots of good questions are
being asked on the organisers list, some of which have been re-posted in a
general form to the small events discuss list. After the event, it may make
sense to collect up some more of these to share. Signup and the website will go
live shortly.
There was some discussion on a http related hackathon, with two proposals
floated. This has gone back to the relevant PMCs for more discussion.
No other possible small events are known about, but we may well try to tag
another call-to-action for local events on with one of the bigger
announcements, to see if that helps.
Logos for small events are now on the new site (see below), which should
hopefully make it easier for people to find and create their small event logos.
We've also helped with the foundation site logos section.
We need to make a push on the events at OSCON this coming month.
Third Party Events
------------------
We reached out to Lucid about Lucene Revolution, and worked with them to tweak
things to match the TPEBP, and they're now approved.
CamelOne was approved recently under the TPEBP, after lots of hard work by a
number of people, from ConCom and the PMC.
Based on the CamelOne experience, it seems like a few small changes to
the Third Party Event Branding Policy (TPEBP) are warranted, we'll
look at these this month.
ApacheCon
---------
The RFP for ApacheCon NA has closed, and one response was received.
We're in the process of drawing up a list of questions and concerns,
which we'll put to the proposer, and we'll vote once we have their
responses.
If we do accept, we'll need some legal help with the contract. We would
appreciate advice on the correct procedure to go about getting this?
(A decision on the first phase of ACEU12 approval is in progress, we'll aim to
update this before the board report with the outcome)
Budget
------
The committee has discussed the budget requirements for the upcoming
year. We're awaiting feedback on one point before submitting.
Committee
---------
No new committee members this month.
After only 13 years, we have finally decided to have our own website!
http://events.apache.org/ has been setup to provide a single location for our
policies and information, as well as a canonical URL (+site if needed) for
events. Some things have been moved over already, others still need to follow
(and our information is widely spread...). We aim to tackle most of the
migrations in the next week or so.
The ApacheCon and events.apache.org related tasks have used all available admin
energy this month, so no progress was made on committee structure.
-----------------------------------------
Attachment 8: Status report for the Apache Infrastructure Team
All outstanding bills have been paid.
Spoke with the myfaces PMC about their public-facing
maven repo on their zone. The zone has been taken down.
Discussed replacement purchase for harmonia (svn.eu)
and and additional VMware server for linux vm's.
Upgraded the majority of our FreeBSD servers to 9.0.
Will complete the remaining ones in the near future.
Next time round we will likely enable dtrace throughout.
Discussed infra's authority to pull improperly-signed
releases from the mirrors. VP Infra concurs we can/should
do this if appropriate justification is available.
Mark Thomas upgraded our Bugzilla installs to 4.0.4.
Dealt with our monitoring host being redeployed to a new
VM server.
Discussed hosting a yum repository for project releases.
No decision was made at this time, pending further input
from volunteers.
Discussed deploying an Australian svn mirror to Gav's
local server. No decision was made at this point.
Greg Stein has taken svnpubsub over to Subversion's trunk
and has done a lot of work on improving the svnwcsub service.
We look forward to seeing svnpubsub distributed in a subversion
release!
Established the precedent of not resetting accounts for
returning committers that are no longer a part of any active
project.
Experiencing chronic problems with isis, one of our build hosts
in Y!'s datacenter. Y! has offered us a pair of new servers
to supplant it.
Began discussion of a budget for FY2012-2013.
Posted a few CMS-related blog entries to http://blogs.apache.org/infra
describing recent activity.
-----------------------------------------
Attachment 9: Status report for the Apache Travel Assistance Committee
General
=======
List is still quiet with not much going on currently.
Budget
======
Nick provided a list of _possible_ events that TAC could look forward
to supporting over the next Financial Year.
We have submitted our 2012-2013 budget requirements based on that list
and also taking into account actual spending figures from previous
events to come up with a budget request on time.
With thanks to our EA, the final actuals we spent for Vancouver
(from the TAC budget portion) have been entered into our current
2011-2012 budget file.
No change to the committee membership.
Other Events
==========
No news about any other events happening at this time. (Other than the
list of possible events coming up later in the year)
-----------------------------------------
Attachment A: Status report for the Apache ACE Project
Apache ACE is a software distribution framework that allows you to
centrally manage and distribute modular software components,
configuration data and other artifacts to OSGi based and related target
systems.
This board report is the third one since ACE graduated as a TLP.
Releases:
* December 11th, 2011: ACE 0.8.1-incubator
Activity:
* We migrated the website and documentation to the Apache CMS.
Actions are still in progress around this topic.
* A press release announcing the graduation as TLP has been sent
on Monday, February 27th.
* A launch party was organized in Apeldoorn, The Netherlands on
March, 1st. All people involved in ACE were invited.
* Jan Willem Janssen donated a multi-process launcher, which we
are reviewing.
* We are now working towards the first TLP release.
Changes in committers/PMC members:
* None so far.
Committer/PMC diversity:
* No concerns, our PMC of 8 has 6 different unique organizations.
Branding/naming issues:
* No issues.
Legal issues:
* None.
-----------------------------------------
Attachment B: Status report for the Apache APR Project
The Apache Portable Runtime (APR) project creates and maintains
software libraries that provide a predictable and consistent interface
to underlying platform-specific implementations.
Releases
--------
apr-util 1.4.1 was in progress at the time of the previous board
report and was released December 15, 2011. This was the first
release from this branch and introduced several new features,
the most important of which is access to certain crypto capabilities
in other libraries. The branch had been in development for several
years without a release. (Subsequent httpd releases switched
from apr-util 1.3.latest to apr-util 1.4.1 for those httpd release
tarballs.)
apr 1.4.6 was released February 14, 2012. It included various
bug fixes from committers and users. Notably, it included a change
to the hashing algorithm to randomize hashes. This was initially
assigned a CVE id, but it is not considered a security fix in APR.
(The change may or may not help resolve a vulnerability in an
application which uses APR. We are not aware of any such
vulnerabilities at this time.)
The most recent release of the legacy APR 0.9.x branch was in
September 2011.
Community
---------
New PMC members or committers: none
Only 2 bugs have been closed during the reporting period, with
about 12 new ones opened.
Mailing list activity has increased dramatically during the quarter
but has been concentrated on three topics:
* finalization of the apr-util 1.4.1 release
* the apr 1.4.6 release
* hash collision vectors
Development
-----------
Activity has been minimal aside from the three topics listed
previously.
Issues
------
There are no board-level issues at this time.
-----------------------------------------
Attachment C: Status report for the Apache Archiva Project
Apache Archiva is an extensible repository management software that helps
taking care of your own personal or enterprise-wide build artifact
repository. It is the perfect companion for build tools such as Maven,
Continuum, and ANT.
Releases
--------
* 1.4-M2 release 2011-12-20
Community
---------
* Jean-Baptiste Onofré was added as a new committer on 2012-01-20.
* The December release vote and the January committer vote had very few
participants from the PMC, which prompted Brett to ask around the Archiva
PMC list if certain members who had little or no activity in the last
year still wish to be active in the project. The following members
noted they were unable to continue their participation and decided to
move to emeritus status:
- Arnaud Héritier
- James William Dumay
- John Tolentino
- Jesse McConnell
- Fabrice Bellingard
- Emmanuel Venisse
Reference thread for the discussion can be viewed at:
http://s.apache.org/xZu
Development
-----------
* As reported in the previous board reports, there were a number of planned
refactorings of Archiva trunk. Below are the status of each of them:
- moving the UI to another framework (in-progress)
- removal of all plexus components (completed)
- replace or overhaul the security system used (UI overhaul of current
security system used has been done to integrate with the UI refactorings
in Archiva)
* For Archiva's UI refactoring, the aim is to make it fast and simple, and
to de-couple it with the core. The UI overhaul is almost half-way through
the webapp, with mostly the administration pages done.
* The OSGi integration with Apache Karaf is still in progress. All the
modules in Archiva have already been converted to OSGi bundles. Next step
is to add the OBR (OSGi Bundle Repository) support.
Project Branding Requirements
-----------------------------
* Project Website Basics - done
* Project Naming and Descriptions - done
* Website Navigation Links - done
* Trademark Attributions - not yet done
* Logos and Graphics - not yet done
* Project Metadata - not yet done
* Read PMC Branding Responsibilities - not yet done
Issues
------
No board level issues at this time.
-----------------------------------------
Attachment D: Status report for the Apache Axis Project
The Apache Axis project is responsible for the creation and maintenance
of software related to the Axis Web Services frameworks and subsidiary
components.
Releases this quarter:
* Sandesha2/Java 1.6.1 (RM: Andreas Veithen)
Last releases for other subprojects:
* Axis2/Java: August 2011
* Rampart/Java: October 2011
* Axis2 Transports/Java: December 2009
* Axis/Java: April 2006
* Axis2/C: Apr 2009
* Rampart/C: May 2009
* Sandesha/C: Oct 2007
* Savan/C: May 2007
* Axis/C++ 1.x: March 2006
Inactive/abandoned subprojects: Savan/Java, Kandula
Branding checklist for subprojects with releases in the last quarters
(Axis2/Java, Rampart/Java, Sandesha2/Java):
* Project Naming And Descriptions: OK
* Website Navigation Links: OK
* Trademark Attributions: OK
* Logos and Graphics: TM not yet included in product logos
* Project Metadata: OK
Not yet compliant:
* Axis2/Java Transports
* Axis/Java
* C/C++ subprojects
* Project homepage (needs review anyway)
Community:
* No issues requiring board attention.
* We voted in a new committer/PMC member: Amila Jayasekara
-----------------------------------------
Attachment E: Status report for the Apache BVal Project
The Apache BVal project implements the Java EE Bean Validation 1.0 (JSR-303)
specification and related extensions, and became a top-level project of the
foundation on February 15, 2012.
### Releases ###
BVal version 0.3-incubating was released April 28, 2011. The PMC is actively
discussing making its first non-incubating release in the *immediate* future.
We are highly motivated because as members of the Java EE ecosystem @ Apache
we like to cooperate and coordinate with the release schedules of related
projects (e.g. OpenJPA, Geronimo) whenever possible.
### Activity ###
Since graduating to TLP status, activity has focused on post-graduation tasks,
primarily the migration of the BVal website from Confluence to the Apache CMS.
We continue to follow the progress of the Bean Validation specification; its
1.1.0 version is being developed under Red Hat's (open) leadership as JSR-349.
Apache BVal will implement Bean Validation v1.1.0 as soon as is practical.
Finally, we have established a #bval channel on Freenode IRC. We continue to
make decisions on-list, but we hope that our availability on IRC will help
build a sense of team camaraderie, and allow us to resolve simple questions
in a more synchronous manner.
### Community ###
The composition of the team has not changed since graduation, at which time
all committers became members of the inaugural PMC. The PMC is quite diverse
and we are satisfied that no entity has undue influence in our decision-making
process.
### Branding ###
Most of the team (and everyone else who has been asked) harbor some level of
dislike for BVal's existing logo, the "check mark made of coffee beans." One
of our ongoing tasks is the direction/selection/creation of a new project logo.
### Legal ###
No concerns at present.
### Infrastructure ###
We have some outstanding features we'd like to implement on our project
website (specifically a news or blog feed), and may seek advice and/or support
from infrastructure to accomplish this.
-----------------------------------------
Attachment F: Status report for the Apache C++ Standard Library Project
Last month, stdcxx added three committers/PMC members. One sent in his
CLA and and an account for him was created. The other two are in the
process of getting their CLAs signed by their employers. Beyond that,
we have nothing to report. All stdcxx committers are busy with our
day jobs and have only limited time to spend on the project. Requiring
reports on a monthly basis won't help increase the activity of the
project. On the contrary, since it takes away from the little time we
have to contribute it is likely to decrease it.
-----------------------------------------
Attachment G: Status report for the Apache Camel Project
Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
Project Status
--------------
* There are no issues that require the board attention.
* The project is healthy and continues to grow.
* Progress has been made toward using the CXF developed export utility to
migrate the website from rsync to svnpubsub as per guidelines from the
Infrastructure team.
Community
---------
* The community grows:
* 503 subscribers to the users mailing list (+3 %)
* 183 subscribers to the dev mailing list (+2 %)
* The community is active
* Avg. 688 mails per month on the users mailing list in Dec 2011 - Feb 2012
* Avg. 196 mails per month on the dev mailing list in Dec 2011 - Feb 2012
* Avg. 507 commits per month in Dec 2011 - Feb 2012
* Babak Vahdat (bvahdat) joined the community as a new committer.
* Bilgin Ibryam (bibryam) joined the community as a new committer.
* No new PMC members since the last board report (December 2011)
* We are on track to increasing diversity.
* Our PMC of 19 is affiliated with 6 different unique organizations (11 of
them are affiliated with a single company).
* Our additional 16 committers belongs to 14 different unique organizations
(3 of them are affiliated with the same single company mentioned above).
* Fusesource planned and announced a CamelOne conference at May 15th - 16th
(http://fusesource.com/apache-camel-conference-2012/). ConCom approved to use
the name CamelOne for this event. The Camel PMC, especially Jeff Genender,
Rob Davies, Claus Ibsen and myself will make sure this event will meet the
ASF trademark and ConCom guidelines.
Community Objectives
--------------------
* Our first objective is to continue with the development for Camel 2.10.0.
* Beside this, we continues development with new features and fixes for the
camel-2.8.x and 2.9.x maintenance branches.
* In the next weeks we have to concrete our schedule for Camel 3.0.0 which
will be a bigger release.
Branding Status
---------------
* Project Naming And Descriptions : Compliant
* Website Navigation Links : Compliant
* Trademark Attributions : Compliant
* Logos and Graphics : Compliant
* Project Metadata : Compliant
Releases
--------
* 2.7.5 (the 2.7.x series continues to be maintained under a "security and
important fixes only" profile)
* 2.8.4
* 2.9.0
* 2.9.1
-----------------------------------------
Attachment H: Status report for the Apache Cayenne Project
Apache Cayenne(TM) is an open source persistence framework licensed under
the Apache License, providing object-relational mapping (ORM) and remoting
services.
Development
* Active work on Cayenne 3.1 release continues.
* We are discussing the first Beta release of Cayenne 3.1.
* DocBook migration of Confluence documentation continues.
Community
* Mailing list activity is average on developer and user lists. The user
list and developer list are both seeing new names appear as more people
seem interested in Cayenne and are exploring it. Also a number of bug
reports and patches have filtered into JIRA from these newcomers.
* We started running an official PMC Twitter at
https://twitter.com/#!/ApacheCayenne
* No new committers or PMC members this quarter.
-----------------------------------------
Attachment I: Status report for the Apache Chemistry Project
== Status report for Apache Chemistry ==
Apache Chemistry is an effort to provide an implementation of the CMIS
(Content Management Interoperability Services) specification in
Java, Python, PHP, and .NET (and possibly other languages).
The project has graduated in February 2011.
== Project status ==
OpenCMIS (Java) still is the most active subproject. The next release will
provide the first complete implementation of the CMIS 1.1 browser binding.
We have received a contribution that adapts OpenCMIS for Android devices.
It is currently on a branch and will be merged it into trunk after a
code review.
We have seen a bit more interest in DotCMIS (.NET) lately.
We got questions, bug reports and patches in the past few weeks.
== Community ==
No significant changes. Steady traffic on the mailing list.
== Releases ==
OpenCMIS 0.7.0 will be released soon.
-----------------------------------------
Attachment J: Status report for the Apache Click Project
Apache Click is an easy-to-use page and component oriented Java web framework.
There are no board level issues at this time.
However the low community participation rate is becoming an issue the project
will need to address, through recruiting new committers and more effort by the
existing project committers.
Infrastructure
-------------------
There are no infrastructure issues at this time.
Development
------------------
Development activity has focused on a 2.4/2.3.1 release scheduled this year..
Community
----------------
There have been no new committer or PMC members added during this period.
Mailing list traffic has picked up quite a bit for the period. There have been
a number of requests about the project's road and the release schedule, with
little response from the project team.
-----------------------------------------
Attachment K: Status report for the Apache Commons Project
Apache Commons provides a large set of reusable Java components. Commons
components are widely used in many projects, both at Apache and outside.
There is one particular problem that may be of interest to board. It
was noted recently that Apache Solr did release on public maven
repository a snapshot version of an Apache Commons sandbox component:
CSV, without changing the top level package name. See
<http://mail-archives.apache.org/mod_mbox/commons-dev/201203.mbox/%3C4F55647C.6050802%40apache.org%3E>. As mentioned here:
<http://mail-archives.apache.org/mod_mbox/commons-dev/201203.mbox/%3Cjj4fnc%24k6u%241%40dough.gmane.org%3E>,
the problem is not the fork (which is welcome, be it from an Apache
project or from anyone else), the problem is that the classpath is
spoiled. A Jira issue has been opened
<https://issues.apache.org/jira/browse/SOLR-3204> and the Commons team
is working together with the Solr team to get the issue solved. It
appears the same problem appears with other components Solr uses (at
least Carrot2 and Jsonic which are not Apache projects, but also
Noggit from Apache Lab and Uima which is a TLP and maybe others).
The Apache Commons PMC would like to ask board whether package names
should remain in the control of the project team or if other project
can publish artifacts using the same packages names freely.
Several components have been released since last report:
Commons Jexl 2.1 (2011-12-13)
Commons Digester 3.2 (2011-12-14)
Commons Pool 1.5.7 (2011-12-21)
Commons Jexl 2.1.1 (2011-12-24)
Commons Pool 1.6 (2012-01-12)
Commons Parent 23 (2012-01-12)
Commons Validator 1.4 (2012-02-03)
Commons Configuration 1.8 (2012-02-05)
Commons Daemon 1.0.9 (2012-02-13)
Commons Net 3.1 (2012-02-21)
Commons Daemon 1.0.10 (2012-02-28)
After several years spent with us and providing countless hours of help,
advices and code, Phil Steitz has decided to go emeritus. The Apache
Commons community is very grateful to him.
Three new committers have been elected to commons:
Thomas Neidhart
Claudio Squarcella
Marco Speranza
As a way to prevent misuses by other people, the G+ brand page "Apache
Commons" has been reserved by Christian Grobmeier. Christian exchanged
with Shane (VP Brand Management) who mentioned the key point is the PMC
needs get access to that G+ account when the original owner has
vanished.
-----------------------------------------
Attachment L: Status report for the Apache Continuum Project
-----------------------------------------
Attachment M: Status report for the Apache CouchDB Project
We added two new Committers to the project: Jason Smith and Dave
Cottlehuber. Both have been contributing to the CouchDB ecosystem and
Apache CouchDB in particular for quite some time.
The PMC chair finally got around to announce Paul Davis as a new member
of the PMC, the vote for which occurred last year.
A new major release 1.2.0 is around the corner. For 1.2.0, for the first
time, we will be voting on official Windows release binaries (courtesy
of Dave Cottlehuber's work).
Noticeable pick-up of activity around pressing issues, including
community members publicly applauding the efforts.
Git integration is going well. Developers are getting into the habit of
regular branching and merging of features and bugfixes. Sharing of
changes for testing and review is becoming easier as well. As cases in
point, a large refactoring of an internal component[1] went very smooth
as did the collaboration on a new security related feature. Regular,
smaller work and bugfixes have been going on at the same time and was in
no way hindered. We started documenting committer and contributor
workflows on the wiki.
PMC member Noah Slater started an inquiry with trademarks@ about a
potential confusion with the Couchbase brand. While the thread is
ongoing, Couchbase have already signalled eagerness to help resolve any
issues. In the past, a similar inquiry about Couchbase's line CouchConf
conferences was resolved to mutual satisfaction as well.
Project founder Damien Katz resigned from the PMC after posting
controversial blog posts challenging the future of the project.
[1]: https://issues.apache.org/jira/browse/COUCHDB-1270
-----------------------------------------
Attachment N: Status report for the Apache Empire-db Project
Apache Empire-db
Apache Empire-db is a relational database abstraction layer that
allows developers to take a more SQL-centric approach in application
development than traditional ORM frameworks. Its focus is to allow
highly efficient database operations in combination with a maximum of
compile-time-safety and DBMS independence.
Progress of the project
Apache Empire-db became a TLP in January 2012. The migration from the
incubator has been completed, our website was updated to reflect the
changes.
We are now working towards a first TLP release, this will probably
take a bit longer than usual as we have to update our release process
guide. The release should be out before next board report.
Changes in committers or PMC members
There have been no changes in Committers since our TLP graduation in
February 2012
Issues
There are no issues that require the board's attention at this time.
Releases
No releases as TLP yet
-----------------------------------------
Attachment O: Status report for the Apache Felix Project
Apache Felix is a project aimed at implementing specifications from the
OSGi Alliance as well as implementing other supporting tools and
technologies aligned with OSGi technology.
Community
* Normal mailing list and bug reporting activity.
* Reuben Garrett has volunteered to work on the iPOJO documentation.
* Benedikt Ritter has volunteered to work on improving documentation on our
wiki.
Software
* Recent subproject releases:
* iPOJO Manipulator (1.8.2)
* Lightweight OSGi HTTP Service (0.1.4)
* Maven Bundle Plugin (2.3.7)
* Service Diagnostics Web Console Plugin (0.1.1) - First release of
contributed project by Arjun Panday.
* Utils (1.1.2)
Project Branding
* Project Website Basics: done
* Website Navigation Links: done
* Trademark Attributions: done
* Logos and Graphics: open
* TM missing from all Logos
* Project Metadata: done
Licensing and other issues
* None.
-----------------------------------------
Attachment P: Status report for the Apache Gora Project
Apache Gora
The Apache Gora open source framework provides an in-memory data model and
persistence for big data. Gora supports persisting to column stores, key
value stores, document stores and RDBMSs, and analyzing the data with
extensive Apache Hadoop MapReduce support.
Project Releases
The last official project release was made on 24/09/2011 which was the
0.1.1-incubating release (2nd whilst in the Incubator). Although since last
reporting there have been some commits to three Gora modules, some remaining
issues still need to be addressed before we are ready to roll out a 0.2
release. This is rather frustrating, as the main issue which blocks a 0.2
release is a licensing issue on the gora-sql store. It is widely
acknowledged that although gora-sql is the least used module, it is the one
which requires attention to rectify this licensing issue.
Overall Project Activity since last report
Since graduation all documentation, and infrastructure has been successfully
migrated over to TLP status. We've witnessed development and commits to
three datastores and a number of issues addressed as a result. It is safe to
say that the gora-hbase store seems to be attracting the most development,
however there are also a number of issues which have recently been opened
for the gora-cassandra module. In the last report we stated that there were
two new modules in the process of being integrated into the project (namely
gora-accumulo and gora-solr), however due to ongoing issues with releases
for Solr and Accumulo, we are not able to release the gora modules.
How has the community developed since the last report?
The Gora mailing lists have seen some activity with regards to
gora-accumulo, however generally speaking traffic was quite low for the
month until this report. We do however have some excellent news that we are
submitting an application to Google Summer of Code. The project comprises a
gora-dynamodb (Amazon Dynamo DB) module, again making best efforts to open
up Gora to a wider audience.
Changes to PMC & Committers
Since VOTE'ing Keith Turner on to the team no new members have been accepted
into the Gora development team. Additionally, no new VOTE'ing has taken place.
PMC and Committer diversity
We currently have committers from a wide variety of projects including,
Nutch, Tika, OODT, Camel, Solr, Accumulo & Hadoop (this is not an exhaustive
list). There is work to be done with the Avro implementations, so once we
are 100% ready to work on these issues, we will be looking to interest
members of the Avro community in Gora.
Project Branding or Naming issues
We recently sorted out all branding and trademark issues through trademarks@.
As this has been addressed there is no more to add at this stage.
Legal issues
We currently have an issue with one particular library being used within the
gora-sql store. It is the communities intention to remove this LGPL licensed
library from the codebase replacing it with implementations from JOOQ an ASL
2.0 licensed library. A re-write of the gora-sql module building from the
JOOQ library has been delayed until after our 0.2 release, an interim
solution comprises simply replacing the offending code with TODO's. Although
technically this makes the gora-sql module unfit for production use, it does
allow us to progress with releasing Gora 0.2. The community can then move
towards a rewrite of the gora-sql module for a 0.3 release.
-----------------------------------------
Attachment Q: Status report for the Apache Gump Project
Apache Gump is a cross-project continuous integration server. Gump's
intention isn't so much to be a CI server but rather a vehicle that
makes people look beyond their project's boundaries and helps the
projects to collaborate.
Gump is written in Python and supports several build tools and version
control systems. The Apache installation of Gump builds many ASF
projects and their dependencies. It started in the Java part of the
foundation but also builds projects like APR, HTTPd and log4net.
== Summary ==
No Board level issues.
== Releases ==
The ASF installations of Gump work on the latest code base almost all
of the time. The project is in a state of a perpetual beta. There
have been no releases.
== Infrastructure ==
The site now uses svnpubsub. If we ever want to create a release,
we'll use svnpubsub right from the start.
We encountered only a few minor hick-ups after the upgrade to FreeBSD
9.0, mostly due to upgrading svn and having to upgrade all working
copies. Many thanks to the infra team.
== Activity ==
The Gump project really consists of two parts, the code base for the
project and the ASF installations[1] running this code base to build
many ASF projects as well as some related projects.
The code base mostly does what its current users need so there isn't
much development going on at all. During this quarter we've tweaked
git support to allow pulling from branches other than "master".
There are only a few people contributing across all projects and a few
additional people maintaining the metadata of the projects they are
interested in the most.
We've finally given up waiting for expat to build on libtool2 systems
and now provide a system installed expat, this means we've started to
successfully build APR and projects depending on APR for the first time
since at least a year, probably longer.
== Changes to the Roster ==
All ASF committers have write access to the metadata that configure
the ASF installations.
No new committers to the code base, no changes to the PMC.
== Branding and Naming ==
We believe to meet all branding requirements.
== Statistics ==
As of Tue, 13 Mar 2012 the ASF installations check out a bit less than
180 source trees (115 from the ASF repository) and try to build a bit
more than 850 "projects". A complete Gump run takes about nine and a
half hours on vmgump and about nine on the FreeBSD jail and ten on
Adam where more projects fail to build.
[1] the main instance at http://vmgump.apache.org/gump/public/ , a
FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS
X Server at http://adam.apache.org/gump/
-----------------------------------------
Attachment R: Status report for the Apache Hive Project
Apache Hive is a data warehouse written on top of Apache Hadoop. It
provides SQL to query and manage data (in the form of tables and
partitions stored in HDFS or external systems) and provides a
metastore containing metadata information about the stored data.
Releases:
0.8.0 released on December 16, 2011.
0.8.1 released on February 6, 2012.
Community:
* Kevin Wilfong was added as a committer.
* 467 contributors (commented, filed bugs or contributed to
Hive). This was 424 at the last report time (September 2011)
Branding Checklist:
We've created HIVE-2432 to track this, with sub-tasks corresponding to
each item.
* Project Website Basics: [DONE]
* Project Naming And Descriptions: [IN PROGRESS]
* Website Navigation Links: [IN PROGRESS]
* Trademark Attributions: [IN PROGRESS]
* Logos and Graphics: [DONE]
* Project Metadata: [DONE]
-----------------------------------------
Attachment S: Status report for the Apache Incubator Project
Many thanks to Noel Bergman for his service as the chairman of the
Incubator PMC over the past eight years!
The discussions about the role and structure of the Incubator over
the past few months have receded as we've recently been focusing more
on the status and concrete issues of individual podlings. This has
resulted in a notable improvement in the overall atmosphere in the
Incubator, though some of the deeper issues that were identified
earlier may come back to haunt us unless we revisit them at some point.
Based on the discussion during the last board meeting and related
thoughts on general@incubator.apache.org we have decided to keep
including individual podling reports as a part of the main Incubator
report. The main rationale for this is that we want to teach podlings
the habit of reporting all the way to the ASF board (with help from
and extra review by the IPMC) instead of positioning the Incubator PMC
as a "mini-board" that filters out and just summarizes podling reports.
That said, we did put extra effort in reviewing podling reports and
highlighting issues that might be of special interest to the board.
Comments and feedback on this approach would be welcome.
o Community
Matt Franklin and Colm O hEigeartaigh joined the Incubator PMC since
our last report.
The following podlings are requesting graduation to Apache TLPs:
- Apache Accumulo
- Apache Lucy
- Apache Rave
- Apache Sqoop
The Incubator PMC recommends the board to accept the respective resolutions.
Other podlings like RAT (Creadur) are currently preparing for graduation.
No new project proposals have been received since our last report.
The initial response to our recent increased emphasis on report review
has been positive, and it looks like the effort is starting to bear fruit
in terms of timely reports and a gradually improving focus on graduation
plans across the Incubator.
Community activity and diversity remain the most common graduation blockers
for incubating projects. We are seeking ways to better track such things
and help podlings grow their communities. There's been talk about
cooperation with ComDev on this front, but so far nothing concrete
has come out of this.
Of particular note community-wise is the Kato podling that no longer
considers itself blocked by Oracle's position on JSR 326. See the Kato
report for more details and thoughts on the project's future.
o Releases
The following incubating releases were made since our last report:
- February 17th, 2012: Apache Sqoop 1.4.1-incubating
- February 21st, 2012: Apache Isis 0.2.0-incubating
- February 21st, 2012: Apache Wookie 0.9.2-incubating
- March 1st, 2012: Apache Oozie 3.1.3-incubating
- March 4th, 2012: Apache Rave 0.8-incubating
- March 4th, 2012: Apache Tashi 201202-incubating
- March 6th, 2012: Apache Hama 0.4-incubating
- March 10th, 2012: Apache Jena TDB 0.9.0-incubating
- March 11th, 2012: Apache MRUnit 0.8.1-incubating
The release process continues to be a source of trouble for many
podlings and also to the Incubator in general. The typical symptoms
of this trouble are major delays in releases of some podlings.
We've had discussions about ways to fix this, but so far there
unfortunately hasn't been much concrete progress.
o Legal / Trademarks
The issue of using Java package names other than org.apache.*
came up in relation to the Sqoop project. The resulting discussion
and the rough consensus that was reached is summarized in the
Sqoop report.
The Flex podling is working on a custom trademark licensing deal
with Adobe. See the Flex report for mode details.
The PODLINGNAMESEARCH process prepared especially by Robert is
now being used by many podlings, and the initial results in terms
of increased confidence in the uniqueness and suitability of
podling names seem pretty good.
o Infrastructure
Thanks especially to Joe and Sebb, the Incubator web site is now
managed using the Apache CMS.
Three podlings - Cordova, DeltaSpike and S4 - are using the Git
repositories provided by the infra team. The early experiences
seem to have been generally positive with no major issues raised,
though no detailed review of potential community impacts has yet
been done.
The infrastructure migrations of large or complex projects like
OpenOffice and Flex have been (and continue being) fairly long
processes that seem to have generated at least some frustration.
We're hoping to collect experience of key problems so that future
podlings with similar needs could at least better anticipate and
plan for such issues.
The OpenMeetings podling is looking to set up a meeting server
as a service for other projects and groups (possibly the board)
within the ASF. Interested groups should contact OpenMeetings
and/or infra for more details.
The idea came up of reviving the old INCUBATOR issue tracker for
tracking Incubator-related tasks. Time will tell how useful this
will be to us.
-------------------- Summary of podling reports --------------------
We reviewed all podlings reporting in this quarter and categorized them
according to their progress through the Incubator and the most pressing
issues that are currently blocking progress.
Still getting started at the Incubator (3 podlings)
DeviceMap, Flex, Syncope
These projects are still getting started, so no immediate progress
towards graduation is yet expected.
Not yet ready to graduate (14 podlings)
IP clearance: Openmeetings
No release: Bloodhound, Cordova, OpenOffice
Low activity: Kalumet, Kato
Low diversity: Bigtop, Etch, Isis, Hama, HCatalog, MRUnit, S4, Wave
We expect the next quarterly report of projects in this category to
include a summary of their actions and progress in solving these issues.
Ready to graduate (6 podlings)
Accumulo, Flume, ManifoldCF, RAT, Rave, Sqoop
We expect these projects to graduate within the next quarter.
-------------------- Detailed Reports --------------------
Accumulo
Accumulo is robust, scalable distributed key/value store with cell-based
access control and customizable server-side processing. Accumulo entered
incubation in September 2011.
Progress since the last report:
- released 1.3.5-incubating
- began final stages of pre-release testing for 1.4.0-incubating
- fostered active discussion on mailing lists and on JIRA tickets
- voted in one new committer
- received patches from 5 new contributors
- agreed on suitability of Accumulo name
- discussed graduation and drafted mission statement for resolution
- called PPMC vote on graduation
Top priorities prior to graduation:
- none
Issues for Incubator PMC or ASF Board:
- none
Signed off by mentor: adc - Alan Cabrera
--------------------
Bigtop
Bigtop is a project for the development of native packaging and stack
tests of the Hadoop ecosystem.
Bigtop entered incubation on June 20, 2011.
Primary issues blocking graduation:
- Need for increased diversity and additional committers.
Issues which Incubator PMC and/or ASF Board might need/wish to be aware of:
- None
Community development since last report:
- Invited talk at Softwarelivre http://softwarelivre.org/fisl12
- Our regular Bay Area Bigtop meetup/class is going strong with ~10 members
http://www.meetup.com/HandsOnProgrammingEvents/
- Bigtop talk @Bay Are Hadoop User group:
http://www.meetup.com/hadoop/events/36789782/
- Gave talks on Bigtop @ApacheCON 2011
- Submitted talk proposals to Hadoop summit (http://hadoopsummit.org/)
and HBase conf.
Project development since last report:
- 0.3.0-incubating is in a process of being released
- Significantly improved our deployment code (puppet) with the help of
an external contributor (Patrick Ramsey)
- Added code for producing virtual machine images with Bigtop Hadoop
stack baked in
- Added code for producing LiveCD/LiveUSB distros of Hadoop stack
- Bigtop branch based on Hadoop 0.23 has stabilized to a point where
we can start thinking of making 0.4.0 release based on it
- Used Bigtop to validate Zookeeper 3.4.* releases
- Used Bigtop to validate Hadoop 1.0.* RC and Hadoop 0.23.*RC release
- Additional component project Bigtop-jsvc added.
- Additional component project Bigtop-tomcat added.
- Increased the # and scope of integration tests
Signed off by mentor: phunt, tomwhite
--------------------
Bloodhound
Bloodhound is an issue tracker derivative of Trac, with the goal of making
deployment easy, and usage intuitive.
Bloodhound has been incubating since December 2011.
The current three most important issues toward graduation remain unchanged
from last month, and are:
1. Improving community diversity
2. Lowering the barrier to entry and development
3. Creating shippable releases and getting user feedback
The last month saw the addition of one committer, Joachim Dreimann, as well
as increased technical discussion on the mailing lists, particularly around
the areas of user interface, multi-project support and rudimentary
installation capabilities. In addition, the first commits of code that
should form part of the distribution have been achieved, providing the
basis for multi-project support and a very basic installer script.
The primary goals of the community remain getting something potential
developers can play with into the repository, and creating a release to
get some widespread exposure to the project.
Signed off by mentor: hwright, gstein
--------------------
Cordova
Apache Cordova is a platform for building native mobile applications
using HTML, CSS and JavaScript. The project entered incubation as Apache
Callback in October, 2011, before changing its name to Cordova.
Our aim for Feb was to ship an official Apache release, but a few issues
remain. We're confident 1.6 will mark our first release.
- completed code migration to Cordova name
- weinre nowing running on nodejs
- cordova-js migration complete for android, underway for other platforms
- aim to new code release cutting tool called `coho`
- launched http://incubator.apache.org/cordova (nice work yohei)
- excellent update to the wiki on contribution (fil, michael)
- Denis Kormalev (dkormalev) voted as committer
- Longwei Su (longwei) voted as committer
- Jeff Tranter (tranter) voted as committer
Graduation concerns:
- updated all license headers to asl
- official apache release
Signed off by mentor: gianugo, jukka
--------------------
DeviceMap
Apache DeviceMap is a data repository containing device information, images
and other relevant information for all sorts of mobile devices, e.g.
smartphones and tablets.
Entered incubation on January 3rd, 2012.
There are no issues that require the Incubator PMC's or the board's attention.
The project is starting slowly, initial technical goals are being discussed
and we hope to have our first mobile device data collection prototypes soon.
Analyzing apache.org requests coming from mobile devices might help us
gather the data that we need, we'll get in touch with infrastructure about
this once we have precise requirements.
Signed off by mentor: bdelacretaz, kevan
--------------------
Etch
Etch was accepted into Incubator on 2 September 2008.
Etch is a cross-platform, language- and transport-independent framework
for building and consuming network services. The Etch toolset includes
a network service description language, a compiler, and binding libraries
for a variety of programming languages.
Status:
- We published our next release Apache Etch 1.2.0-incubating
- The Apache Etch website was switched to the new Apache CMS system.
The website is available at http://incubator.apache.org/etch/
- The binding-cpp implementation makes some progress. I think a fist
version of the whole stack could be finished while the next weeks
- We work on our graduation to become an Apache TLP. Nearly all issues
are solved http://incubator.apache.org/projects/etch.html
The PODLINGNAMESEARCH is in progress and should be concluded soon.
The preparations for the graduation steps are under way.
- We could acquire a new committer Thomas Marsh to our team
Future Tasks:
- Development binding-cpp
- Bug fixing
- Graduation
- Community development
Signed off by mentor: cutting
--------------------
Flex
Apache Flex is an application framework for easily building Flash-based
applications for mobile devices, the browser and desktop.
Summary: A highly energetic community waits for Adobe to complete the
source code transition and infrastructure.
Date of entry to the Incubator: December 31, 2011
Top three items to resolve before graduation:
1. Resolve trademark donation or licensing
2. Complete code and bug database donation
3. Make at least one release
Is there anything that the Incubator PMC or ASF Board specifically needs
to address?
The ASF legal team may have to agree to a custom Trademark licensing.
Adobe is currently evaluating the parameters of a custom Trademark license
proposed by an ASF Board member. If approved, a custom agreement will be
drafted and signed by both parties.
Are there any legal, infrastructure, cross-project or personal issues that
need to be addressed? (Are there any stumbling blocks that impede the podling?)
Besides the trademark issue mentioned previously, the import of existing
JIRA bugs is blocked by an issue with Apache JIRA's import utility. It has
failed to import the data file supplied by Adobe. Infra is supposed to
open a support ticket with Atlassian.
Check that the project's Incubation Status file up to date.
http://incubator.apache.org/projects/flex
What has been done (releases, milestones, etc.) since the last report?
- An initial set of Flex source (base framework code), including history,
was checked into the trunk area of the podling’s Subversion repository.
- Other initial committers have donated code to the whiteboard.
- Updates to the podling's wiki including a getting started area for
reference to new project members.
- Justin Mclean was accepted as committer to the podling.
What are the plans and expectations for the next period?
Adobe expects to complete the transfer of the bug database. Adobe also
hopes to contribute the compiler and test suite as well. And there is hope
for an initial release.
Are there any recommendations for how incubation could run more smoothly
for you?
Incubation has been working well. Our mentors are great.
Signed off by mentor: wave, bdelacretaz, greddin
--------------------
Flume
Apache Flume is a distributed, reliable, and available system for efficiently
collecting, aggregating, and moving large amounts of log data to scalable
data storage systems such as Apache Hadoop's HDFS.
Flume entered incubation on June 12th, 2011.
Progress since last report
- Flume made it's first release from Incubator - version 1.0.0-incubating
on January 4th, 2012.
- Flume PPMC voted in three new committers from diverse organizations:
Jarek Jarcec Cecho, Brock Noland, and Juhani Connolly.
- Development work is going strong on flume-728 branch with over 50 issues
fixed since the last submitted report.
- The flume-dev list is vibrant with discussions around design and policy,
with active participation from contributors and committers alike.
Issues before graduation
- Move the active development branch - flume-728 to trunk.
- Release a version from the trunk.
Signed off by mentor: Ralph Goers (rgoers), phunt, tomwhite
--------------------
Hama
Hama was accepted into Incubator on 20 May 2008. Hama is a distributed
computing framework based on BSP (Bulk Synchronous Parallel) computing
techniques for massive scientific computations.
Top 2 or 3 things to resolve prior to graduation
- Grow the community size.
- Making a ready-to-use release.
Issues for the Incubator PMC or ASF Board
- None.
Community development
- Increased contributions from new people interested in Hama.
Apurv Verma and Suraj Menon did contributed great efforts to our project.
- Looking forward to participate in GSOC 2012 and invite new committers.
Project development
- Prepared Hama 0.4.0-incubating and benchmarked its performance
(The concept is proofed).
- This release includes a lot of new features and improvements and
is currently being voted.
- Stabilized barrier synchronization.
- Support Muli-tasks.
- Input/Output Formatter like MapReduce.
Signed off by mentor: tommaso
--------------------
HCatalog
HCatalog is a table and storage management service for data created using
Apache Hadoop. HCatalog entered Apache incubator on March 2011.
The most important issues in moving the project to graduation are expanding
the community of users and developers. There has been progress on this over
last few months as we are seeing some significant contributions coming from
the community adding in new features. e.g., see HCATALOG-2 We are adding
new features (see 3rd point below) which will help us to reach out to
non-java users which we believe will help us significantly expand our
user base.
Since the last report we:
- Are preparing for our second release HCatalog 0.4
- Continued feature development, making Hive and HCatalog
interoperability better (HCATALOG-237).
- Work in progress for adding rest apis for HCatalog (HCATALOG-182)
which could help us in significantly expand our user base.
Currently there are 85 subscribers to the user list and 77 on the dev list.
There were 75 and 70 respectively last report (December 2011).
Signed off by mentor: Alan Gates (gates)
--------------------
Isis
Isis is an ALv2 licensed implementation of the Naked Objects pattern. It is
based on contributions of the original Naked Objects Framework along with
a number of sister projects that were developed for the book "Domain Driven
Design using Naked Objects " (pragprog 2009).
Isis was accepted into the Incubator in 2010, September 7th.
Project Development
- Released 0.2.0-incubating, with improved website and archetype
- Added demo of jQuery mobile to demonstrate REST API
- Added support for MongoDB in the nosql object store
Community Development
- Mailing list remains reasonably active
- New site gone live which improves the "message" for would-be users
- Hoping to pick up a new committer; awaiting their contribution for review
- New JIRA tickets raised/tagged existing tickets for potential newbie
contributors to pick up and contribute back
- Continuing to work on restful objects spec, implemented by Isis and
by (non-Apache) Naked Objects MVC open source project
- hope is that this will raise some synergies and build community
across both
Top 3 Issues to address in move towards graduation
- only really one issue: need to demonstrate can bring in at least one
new committer. At that point, we feel that we have done enough to
warrant graduation (as a small but viable community)
- in mean time, need to continue to remove impediments for building the
community, by improving the messaging on the website, by making the
archetypes easy to use, by blogging
We don't believe that any of these issues requires Board attention.
New Releases
- 0.2.0-incubating was released in Feb 2011
- intention is to release 0.3.0 in Apr or May (prior to next report)
Signed off by mentor: struberg
--------------------
Kalumet
Apache Kalumet is a complete platform to administrate data center. It covers
the operating system tasks, middleware provisioning, etc. Kalumet entered
incubation in September 2011.
Community Development:
Some new users gave interest to Kalumet. Some contributions should arrive soon.
Lot of users are still "linked" to the old area on sourceforge.
We are going to deprecate the sourceforge area to highly promote Kalumet.
Our effort will be on the project activity.
Project Development:
From a codebase perspective, we added the support of JBoss 6/7 and made some
important enhancements on the VFS file manipulation.
Now, we are working on the documentation, to be able to publish on the website
asap.
Roadmap Before Graduation:
- The first target is the documentation. We plan to provide an online
installation guide (for both agent and console), user guide (for the
console), tutorial/use case. The work started and should be committed soon.
- Kalumet scripts. It's the extension of the "software" concept globally
to all Kalumet resources. It will allow users to create custom
deployment/update plan, with a set of fine-grained steps.
- Refactoring of the UI. Currently Kalumet Console uses Echo2 framework.
It's a category B license framework. We plan to refactor the console
to use a new framework.
Web Site/Communication Development:
The website has been created: http://incubator.apache.org/kalumet/
It introduces Kalumet and provide first content. The website will be updated
with the documentation soon.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of:
None so far.
Signed off by mentor: jbonofre, olamy
--------------------
Kato
Kato was accepted into the Incubator on 6 November 2008.
Kato is a project to develop the Specification, Reference Implementation,
and TCK for JSR 326: the JVM Post-mortem Diagnostics API.
Recent Activity:
- Oracle finally stated its position on JSR 326 and the Kato project.
In short, other technologies are a higher priority, and there is a
limited audience for the API.
- There was a lot of discussion on the status of this project and the
reporting of that status.
- Robert Burrell Donkin announced his resignation from the IPMC and as
mentor for this project.
- There was some discussion about the future of the project, but
nothing concrete.
The following is planned for next reporting period:
- Decide in what form the podling should continue, if at all.
Before this project can graduate we need to encourage more participation
in the project and grow the community.
Signed off by mentor: ant
--------------------
ManifoldCF
ManifoldCF is an incremental crawler framework and set of connectors designed
to pull documents from various kinds of repositories into search engine
indexes or other targets. The current bevy of repository connectors includes
Documentum (EMC), FileNet (IBM), LiveLink (OpenText), Meridio (Autonomy),
SharePoint (Microsoft), JDBC, CIFS file systems, CMIS repositories, Alfresco,
RSS feeds, Wiki content, and web content. Output support includes Solr,
MetaCarta GTS, and OpenSearchServer.
ManifoldCF also provides components for individual document security within
a target search engine, so that repository security access conventions can
be enforced in search results.
ManifoldCF has been in incubation since January, 2010. It was originally
a planned subproject of Lucene but is now a likely top-level project.
A list of the three most important issues to address in the move
towards graduation:
1. We believe we've reached graduation threshold. More committers and
greater breadth in the committer base is always welcome, of course.
2. We need the current committer base to continue to broaden their
commits to new areas of the project
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
be aware of?
We have an outstanding request to Apache Legal to determine whether we can
distribute PDF files containing Japanese characters rendered with the IPA
family of fonts. It would be great to know the answer prior to the release
of ManifoldCF 0.5-incubating. A ticket is open (LEGAL-123) but no activity
has taken place on it.
How has the community developed since the last report?
We've received sustained contributions from multiple individuals, and signed
up one new committer. Deployments of the project software are also now
clearly reaching a much broader audience than they were a year ago, and
this trend seems likely to continue. A second revision of ManifoldCF in
Action is also planned to keep up with developments on the project.
How has the project developed since the last report?
An 0.1 release was made on January 31, 2011, and a 0.2 release occurred
on May 17, 2011. The 0.3 release occurred on September 20, 2011. The 0.4
release took place on February 2, 2012. The fifth incubator release is
planned for March 30, 2012, and will include an ElasticSearch connector,
full internationalization support and a Japanese localization, MySQL
support, automated UI testing, and more.
Signed off by mentor: tommaso, jukka
--------------------
MRUnit
MRUnit is a unit testing framework specifically designed to make it easy
to test and evaluate Map Reduce algorithms and applications that run on
top of Hadoop.
MRUnit entered the Incubator on Mar 8, 2011.
Community
- Added a new committer, Jim Donofrio.
- Release 0.8.0-incubating has been announced.
- Release 0.8.1-incubating will be announced shortly.
Issues before graduation
- Grow the community size and diversity
- Make another incubating release
- Construct an MRUnit website to replace the existing stub
Licensing and other issues
- none - MRUnit was originally a subproject of Hadoop
Signed off by mentor: mattmann, phunt
--------------------
Openmeetings
Openmeetings provides video conferencing, instant messaging, white
board, collaborative document editing and other groupware tools using
API functions of the Red5 Streaming Server for Remoting and Streaming.
OpenMeetings entered the incubation on November 12, 2011.
- A question for PMC: Should we start a demo server on Apache, so people
can benefit from communication?
Project status:
- We have prepared our build environment for integration with Apache's
build server and discussing with Infra team
https://issues.apache.org/jira/browse/OPENMEETINGS-2
https://issues.apache.org/jira/browse/INFRA-4438
- Integration of new Audio/Video components, progress is documentated at:
https://cwiki.apache.org/confluence/display/OPENMEETINGS/NewAudioVideoComponents
- A first version of the JIRA Plugin for Openmeetings is ready
https://svn.apache.org/repos/asf/incubator/openmeetings/branches/jira-plugin/
http://vimeo.com/37419990
- Code review is ongoing to prepare files for IP clearance
Community status:
- Wiki starting to get in shape
https://cwiki.apache.org/confluence/display/OPENMEETINGS
- Tutorials english/spanish and VMWare Image created by Alavaro
https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+related+to+OpenMeetings
https://cwiki.apache.org/confluence/display/OPENMEETINGS/ISO+Live+OpenMeetings+1.9.1+in+Ubuntu+11.04+to+download
Problems:
- currently the legal status of our plugins is not 100% clear if we are
able to maintain and publish them under ASL, see
http://mail-archives.apache.org/mod_mbox/incubator-openmeetings-dev/201202.mbox/%3CCACeMiA-HLOFjCj%3DHopsHz-FP884JyQ5mwHnGPVSrD5TVC_D%2BTw%40mail.gmail.com%3E
we need to discuss that further and get an official statement.
Signed off by mentor: rgardler, jim
--------------------
OpenOffice (was OpenOffice.org)
* OpenOffice entered incubation 2011-06-13
OpenOffice is an open-source, office-document productivity suite providing
six productivity applications based around the OpenDocument Format (ODF).
OpenOffice is released on multiple platforms. Its localizations support
110 languages worldwide.
Most Important To Address:
1. Completion of the IP-review portions of the incubation checklist
2. A Successful Podling Release
3. Increase size and diversity of the active development community
Issues for IPMC or ASF Board Awareness
- None
Community Development Progress
- Since our last report we have voted in 3 new Committers.
- We have improved to act more as a self organized project to address
and solve project related topics (e.g., budget transfer from SPI, forum
moderation).
- We accepted an offer from SourceForge to host our extension repository
(host, upgrade, improve) as interim solution.
- With the start of QA and translation effort, additional volunteers have
now started becoming active in the project.
- We continue to get trademark usage permission requests, including an
interesting one to use Apache OpenOffice as "stage dressing" in a
Hollywood motion picture.
Project Development Progress
- We believe that all category-x copyleft code has been removed.
Development focus has shifted to preparing our initial Podling Release
(release 3.4)
- Buildbot now doing nightly Linux 64bit and Windows builds.
Linux 32bit and MacOS is in-progress.
- Work on a working translation process has started. We restore and backup
the old Pootle data, analyzed the data and the translation process.
Work ongoing (very complex to understand the roundtrip)
- Started organized QA work (manual testing + automated testing)
- Provide weekly developer snapshots for Linux (32, 64 bit), Windows,
MacOS and partly Solaris (x86)
- Added script to build source packages for releases
- Working on final pieces of infrastructure migration, including shut
down of legacy openoffice.org email forwarder.
- Community support forums remain popular with users, hitting a new
concurrency record (296), but also seeing more spammers:
http://user.services.openoffice.org/en/forum/viewtopic.php?p=222874#p222874
Signed off by mentor: rgardler, joes
--------------------
RAT
RAT started incubation as a Java library that scans files for known licenses
and reports files that lack any of them. By now more tools that help
collecting, aggregating and validating licenses have been added.
After some soul-searching the RAT community is preparing to vote on
graduating as a TLP under the name Creadur. The voting process is not
likely to complete in time for the next board meeting, though.
Signed off by mentor:
--------------------
Rave
Apache Rave is a a widgets-based, web-and-social mashup platform. It will
provide an out-of-the-box as well as an extendible lightweight Java platform
to host, serve and aggregate (Open)Social Gadgets, W3C Widgets and services
through a highly customizable and Web 2.0 friendly front-end.
Rave entered incubation on 2011-03-01.
Project Development:
- Venkat Mahadevan was voted in as new committer and PPMC member in January
- Three additional releases (0.6-incubating, 0.7-incubating, 0.8-incubating)
since the last report
- A next 0.9-incubating release candidate is being voted on on the dev list
- Apache Wookie is now integrated and bundled with the 0.9-incubation
release candidate
- A patch for easier and more modular integration of Apache Shindig in
Rave has been accepted and applied by Shindig
Community Development
- Rave received honorable mention in the 2011 Open Source Rookies of the
Year selection from Black Duck Software
- Ate Douma represented the ASF and Rave in a public webinar from
Black Duck Software "Code well and Prosper with OSS: How Apache and
Eclipse Help Developers Succeed"
- Matt Franklin did a live demo and presentation on Rave at the
OpenSocial 3.0 Kickoff
- Community interaction on mailing list remains high and rising
- Discussions on architecture and roadmap plans towards a 1.0 release
are heating up
Tasks done and remaining to graduate:
- A suitable name search has been executed on usage of "Apache Rave"
- IP Clearance of all code donations have been performed and resolved
- All other relevant Incubating work items have been resolved
- The Rave PPMC has voted on and accepted to graduate and collaborated
on the proposed board resolution
- The Rave PPMC decided with general consensus to propose Matt Franklin
as new Chair for Apache Rave
- The IPMC has voted on and accepted the graduation proposal on March 1st
(exactly 1 year after entering the incubator)
- The Apache Rave graduation proposal has been added to the next board
meeting agenda
Signed off by mentor: ate, rgardler
--------------------
S4
S4 (Simple Scalable Streaming System) is a general-purpose, distributed,
scalable, partially fault-tolerant, pluggable platform that allows
programmers to easily develop applications for processing continuous,
unbounded streams of data.
S4 entered incubation on September 26th 2011.
Infrastructure issues
- Migration to the experimental git program completed. No problems reported.
Other issues before graduation
1. Still working towards an initial release on Apache with the current
code (version 0.4 = version 0.3 + checkpointing + bugfixes)
2. Complete the current work on the new version (S4-piper, 0.5), which
is a major refactoring that simplifies concepts, API, and introduce
new features such as dynamic deployment and reliable channels.
Designed reliable channels; implemented guaranteed message-delivery even
in the presence of network glitches and partitions using Netty's TCP.
Pending one bug, this code is up for inclusion.
Added an Embedded Domain Specific Language (EDSL) to create applications.
Designed and started implementation of command-line deployment tool to
make it easy to manage the cluster.
Design adaptor and inter-application communication.
3. Grow the community
Project activity:
- 45 Jira issues created to date
- 8 issue reporters
- 5 contributors
- Mailing lists: 55 on dev, 72 on user
Signed off by mentor: phunt
--------------------
Sqoop
A tool for efficiently transferring bulk data between Apache Hadoop and
structured datastores such as relational databases.
Sqoop was accepted into Apache Incubator on June 11, 2011. Status information
is available at http://incubator.apache.org/projects/sqoop.html.
Progress since last report:
- Sqoop PPMC voted in Kathleen Ting as a new committer.
- Sqoop PPMC voted in Jarek Jarcec Checho (Jarsolav Cecho) as PPMC member.
- Released Sqoop version 1.4.1-incubating, with support for Apache Hadoop
versions 0.20, 0.23 and 1.0.
- Sqoop started its graduation process on February 19th, 2012.
Progress on graduation:
- Community Vote: PASSED. Vote (1), Result (2)
- Incubator PMC Vote: PASSED. Vote (3), Result (4)
- During IPMC vote a concern was raised that Sqoop contains deprecated
Java source in com.cloudera.sqoop namespace which need be removed
before graduation.
- Sqoop dev expressed that this code was:
- Marked deprecated and retained solely for backward compatibility.
- That there was a concrete plan to completely remove it by next major
revision, work for which had already started.
- That it was not motivated by Cloudera's corporate interests.
- The Incubator PMC and Sqoop community reached consensus that:
- Sqoop was within its right to retain Java source code in
com.cloudera.sqoop namespace to provide backwards compatibility.
- And, that it was for the benefit of Sqoop community.
- And, that there is no such policy in ASF that Incubator can enforce
on any Incubating projects.
- And, that if anyone feels that this should be a policy, they must
establish it via the proper channel of providing the problem statement,
impact of the problem, and solution to the board for consideration.
- The draft board resolution that was voted on by IPMC has been submitted
to the board for consideration in its next meeting scheduled for
March 21, 2012.
(1) http://s.apache.org/scvt
(2) http://s.apache.org/sqoop
(3) http://s.apache.org/sivt
(4) http://s.apache.org/sivr
Signed off by mentor: phunt, olamy, tomwhite
--------------------
Syncope
Apache Syncope is an Open Source system for managing digital identities in
enterprise environments, implemented in JEE technology. Syncope joined the
incubator on February 10th 2012.
Community Development:
Project is still too young to have attracted users already.
Project Development:
New committers accounts have been created,
SVN+MLs+JIRA+Confluence+Jenkins+Sonar+Nexus have been enabled,
codebase has been imported, development started healthy.
Now, we are working towards the first release.
Web Site/Communication Development:
The website has been created and kept up-to-date according to
development: http://incubator.apache.org/syncope/
It introduces Syncope and provide first content.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of:
None so far.
Signed off by mentors: elecharny, coheigea, simonetripodi
--------------------
Wave
Incubating since: Dec-2010
Description: Wave is a real-time communication and collaboration tool.
Wave in a Box (WIAB) is a server that hosts and federates waves, supports
extensive APIs, and provides a rich web client. This project also includes
an implementation of the Wave Federation protocol, to enable federated
collaboration systems (such as multiple interoperable Wave In a Box instances).
Most important issues are:
- Building up community.
- Bug fixes.
Community:
The Wave project attracted significant interest recently - probably caused
by Google Wave becoming read only. The activity levels on the mailing list
are increasing constantly, as well as number of contributors.
Project development:
- Added waves import from Google Wave.
- Added SSL server capabilities.
- Bug fixes + improved stability.
- Some improvements to UI.
There are more features soon to be added to Wave in the review process.
Signed off by mentor:
-----------------------------------------
Attachment T: Status report for the Apache Jackrabbit Project
The Apache Jackrabbit™ content repository is a fully conforming
implementation of the Content Repository for Java™ Technology API
(JCR, specified in JSR 170 and 283).
The Apache Jackrabbit project is in good shape. We have no board-level
issues at this time.
o Releases
The biggest news this quarter was the first stable Jackrabbit 2.4 release,
about a year after Jackrabbit 2.2 was branched.
* Apache Jackrabbit 2.4.0 on February 9th
In the run-up to 2.4, we cut the following unstable 2.3.x releases:
* Apache Jackrabbit 2.3.7 on January 24th
* Apache Jackrabbit 2.3.6 on January 2nd
* Apache Jackrabbit 2.3.5 on December 16th
We made one patch release from the earlier 2.2 maintenance branch:
* Apache Jackrabbit 2.2.11 on February 11th
We also completed the end-of-life period of the last Jackrabbit 1.x
maintenance branch, making the stable 2.x branches the only actively
maintained versions of Jackrabbit.
o Community / Development
No new committers or PMC members were added in this quarter.
The work towards Jackrabbit 3 entered a major new phase as we decided
to promote the effort from prototypes in the Jackrabbit sandbox to
a new Jackrabbit subproject codenamed "Oak". This is a major rewrite
of Jackrabbit, which is why we wanted to clearly separate the effort
from work on the main Jackrabbit codebase. It is yet undecided whether
the Oak codebase will eventually replace Jackrabbit trunk to become
Jackrabbit 3.0 or if we want to rebrand the effort and branch it off
to a separate TLP, possibly through the Incubator. Meanwhile we plan
to start publishing early access versions of the Oak codebase as a
series of monthly "Apache Jackrabbit Oak 0.x" releases (as the codename
"Oak" is not unique enough for use as a standalone "Apache Oak" brand).
Jukka Zitting wishes to resign as chairman of the Jackrabbit PMC due
to his new role at the Incubator, so we have started the process of
electing a new chairman.
o Infrastructure
We are still in progress of migrating from Confluence to the new CMS.
-----------------------------------------
Attachment U: Status report for the Apache Karaf Project
Apache Karaf provides higher level features and services
specifically designed for creating OSGi-based servers.
Community
=========
The Karaf community continues to provide help to others Apache
projects (Whirr, Archiva, etc) in order to increase the Karaf
adoption.
We welcome a new committer: Stephen Evanchik. Stephen already signed
the ICLA. His account should be setup soon.
Stephan made the donation to EIK (see below).
We are discussing about mentoring a GSoC project.
Some indicators during the last 3 months:
- Download: around 14,000 distribution downloads
- User mailing list: 718 messages
- Dev mailing list: 706 messages
- Commits: 742
Development
===========
The following new releases have been voted:
* Apache Karaf 2.2.5
* Apache Karaf Cellar 2.2.3
We made progresses on the stabilization of the Karaf 3.0 next release.
A karaf-3.0.x branch will be cut off soon in order to prepare a first RC.
A new Karaf sub-project has been created: EIK (Eclipse Integration for
Karaf), which allows to run Karaf directly into the Eclipse IDE.
Web Site
=======
A new version of the website has been deployed to give more visibility to
the Karaf sub-projects.
Branding
========
* project website basics: ok
* website nav links: ok
* trademarks: ok
* logo: ok
* metadata: ok
Issues for board consideration
==============================
None so far.
-----------------------------------------
Attachment V: Status report for the Apache Labs Project
Apache Labs hosts small and emerging projects from ASF committers.
[STATUS]
A typically slow quarter for Labs. The PMC remains healthy.
[DETAILS]
== Community ==
As reported last quarter, the community was supportive of a proposal to the
Apache CMS. We migrated over this quarter and are now using the CMS.
We had one lab, Oak, get started using Git. It is currently in the midst of a
vote to complete.
Some housekeeping was done on our unix group membership to make it more
accurate.
== New Labs ==
None.
== Labs Statistics ==
- new: 0
- status changes (last 3 months): 0
- total number: 38
- active: 16
- idle: 15
- promoted: 3
- completed: 4
- labs with commits: magnet, yay, oak
-----------------------------------------
Attachment W: Status report for the Apache Logging Project
This is an off-cycle report due to a missed report last
month.
- Community
Florian Semm has been added as a log4php member.
- Project Branding Requirements
No activity this quarter.
- Development
log4j 1.2:
Christian Grobmeier is intending to manage the release of
log4j 1.2.17 and push the release forward in the middle of
March to address a nasty memory leak. Ralph Goers has
volunteered to assist with Windows specific tests.
Two unreleased log4j companions (component and receivers) which
which primarily support Chainsaw are planned to be rolled into
the "extras" companion to minimize the number of products
supported by the project.
log4j 2.0:
Log4j 2 was moved out of the experimental branch and now has its own trunk
under log4j where further development can continue. The Logging team posted
a blog entry announcing this in February. It has remained a struggle to gain
new participants in this effort. Work is continuing towards an initial
release.
log4cxx:
log4cxx has had an extended period of no activity. In recent thread
"Is log4cxx still alive", there was a legitimate frustration at the
lack of a review or action on a bug report and a newcomer
announced that he was forking the project on github, unfortunately
with the name log4cpp which is yet another logging framework for C++.
Ideally, those frustrated with the lack of activity could be converted
to contributors as had happened to varying degrees with log4php and log4net.
However, that requires at least one committer to serve as mentor.
log4net:
Unfortunately the 1.2.11 release of log4net hasn't attracted new
contributors so far. Development activity is very low, there are a few
questions on the user list that get answered timely and we see almost no
JIRA activity.
We have conducted a user survey last quarter and only very few users
requested support for .NET 1.x, so we may be able to clean up the code
base for upcoming releases.
log4php:
The log4php team has released version 2.2.1.
Florian Semm has joined then ranks of the log4php committers.
The log4php project is still small, but it seems it gets more and more
attraction. Since the last report we have found a few positive reviews
of log4php in the blogosphere.
Chainsaw:
Progress on release still blocked by lack of activity to push log4j companions
on which it depends to release.
-----------------------------------------
Attachment X: Status report for the Apache Lucene Project
TLP
We have added several new PMC members:
* Martijn van Groningen
* Dawid Weiss
* Jan Jøydahl
Trademarks:
We have not made progress on trademarks since the last board report, but
do intend to finish the necessary pieces.
* Project Naming And Descriptions :
We believe this is complete, but are still reviewing.
* Website Navigation Links : navbar links included, link to
www.apache.org included.
Likely complete, but under review.
* Trademark Attributions : attribution for all ASF marks included in
footers, etc.
The main TLP site is converted, subproject sites have not.
* Logos and Graphics : include TM, use consistent product logo on your
site In progress. Some have been converted to have TM, some not.
We don't seem to have ready volunteers on the graphical front,
so it is slower than we'd like
* Project Metadata : DOAP file checkedin and up to date
Done
LUCENE JAVA/Solr
Lucene Java is a search-engine toolkit and Solr is a search server
built on top of Lucene. The community is very active. The community
has recently switched to the Apache CMS including several improvement
that increased the number of package downloads significantly.
The community is working towards a Lucene & Solr 3.6 release and plans
to branch trunk in preparation for a Lucene 4.0 Alpha release.
Additionally, we have added several new committers:
* David Smiley
* Christian Moen
* Sami Siren
* James Dyer
* Stefan Matheis
* Tommaso Teofili
Open Relevance Project
The Open Relevance Project is a project aimed at providing Lucene
and others tools for judging the quality of search and machine
learning approaches. The community is not very active, but
we don't expect it to be very high volume either as it is a niche
area.
PyLucene
PyLucene is a Python integration of Lucene Java. Development is
almost entirely an automated port, so this project will never
require a lot of developers. The user community is active.
-----------------------------------------
Attachment Y: Status report for the Apache OFBiz Project
Apache OFBiz (The Apache Open For Business Project) is an open source
enterprise automation software project. By enterprise automation we mean:
ERP, CRM, E-Business / E-Commerce, MRP, SCM, CMMS/EAM, and so on.
We have no issues that require Board assistance at this time.
*Releases*
- new releases; "Apache OFBiz 09.04.02" has been released in 2012-02-25;
- the community has discussed a plan for a time-based release roadmap:
the release branch 09.04 is now closed; the active release branches are
now 10.04 and 11.04 (and the upcoming 12.04); from each active release
branch we will release about 2 releases every year (approx every 6 months);
every year in April we will create a new release branch (that will determine
the major release number YY-MM); no more than 3 active release branches
will be maintained and then we will close (every year sometimes before April)
the oldest one; the OFBiz site download page has been updated with the
above information; even if the plan is not set in stone the community will
try to implement it and it will be reviewed over time if needed.
*Community and Project*
- new PMC member: Erwan De Ferrieres
- Community interaction remains strong, user and dev mailing lists traffic
is high
- Significant new development continues
*Infrastructure/Legal*
- INFRA-4485: migration to svnpubsub in progress
- no issues
*Project Branding Checklist*
Project Website Basics: mostly complete [*]
Project Naming And Descriptions: complete
Website Navigation Links: complete
Trademark Attributions: complete
Logos and Graphics: complete
Project Metadata: complete
[*] The text in the main pages (index, download) of the project's website is
now compliant with the project branding guidelines;
however there are several Confluence based pages (linked from the home
page) that still need to be reviewed; we are currently discussing a plan to
finalize this effort
-----------------------------------------
Attachment Z: Status report for the Apache OODT Project
Apache OODT is a software framework, and an architectural style for
the rapid construction of scientific data systems. It provides
components for data capture, curation, metadata extraction, workflow
management, resource management and data processing.
Releases/Development:
Paul Ramirez volunteered to roll an 0.4 release candidate, and
hopefully that will be done in the next week or so.
There are over 100+ issues that have been fixed since 0.3. The major
innovations in this release are the PCS Operator Interface [1], the
complete refactoring and re-architecture of the Workflow Engine
(aka "Workflow2") [2], OODT RADIX [3] for easy deployment of OODT
systems, and improvements to our command line interfaces for all
components [4].
Community:
The Apache OODT PMC has had a busy 3 months of adding new contributors.
We added Shakeh Khudikyan, Paul Zimdars, Luca Cinquini, and Bruce
Barkstrom to our ranks, and are in the process of wrapping up another
PMC member VOTE currently.
In addition, Apache OODT was recently used by a Master's student,
Billy Webb, who also works at Northrup Grumman corporation, to study
software architecture, and data systems. He cited Apache OODT as a
great example of an open source community, and active software
project, that he could use to study in his class.
Branding:
No updates beyond last report. Looks good.
Press:
Apache OODT was mentioned in several recent articles, including a
link from NASA's new code.nasa.gov website [5], in NASA Spinoff
magazine [6] (includes quotes from Chris Mattmann, Dan Crichton and
Jim Jagielski) and also in a link from MSNBC to the NASA Spinoff
site [7] which links to OODT.
[1] https://issues.apache.org/jira/browse/OODT-157
[2] https://issues.apache.org/jira/browse/OODT-215
[3] https://issues.apache.org/jira/browse/OODT-120
[4] http://s.apache.org/flV
[5] http://code.nasa.gov
[6] http://s.apache.org/ne
[7] http://s.apache.org/jQD
-----------------------------------------
Attachment AA: Status report for the Apache OpenNLP Project
The Apache OpenNLP library is a machine learning based toolkit for the
processing of natural language text. It supports the most common NLP tasks,
such as tokenization, sentence segmentation, part-of-speech tagging,
named entity extraction, chunking, parsing, and coreference resolution.
These tasks are usually required to build more advanced text processing
services.
Development
------------------
The project graduated last month from the incubator which distracted everyone
a bit from the normal development activity. The team is active and works on
bug fixes and features for our next release.
Community
---------------
The community is active and we have good traffic on the developer
and user mailing list. Users frequently report issues which usually get fixed
quickly.
No new committers have been voted in.
Releases
------------
No releases since we graduated from the incubator.
Issues
--------
There are no board-level issues at this time.
-----------------------------------------
Attachment AB: Status report for the Apache OpenWebBeans Project
Apache OpenWebBeans is an ALv2-licensed implementation of the "Contexts and
Dependency Injection for the Java EE platform" specification which is defined
as JSR-299 (CDI-1.0). OpenWebBeans will also implement the CDI-1.1
specification which is currently being created as JSR-346.
Board Issues
* There are no issues that require Board attention.
Development
* Continue to fix bugs and implement code improvement.
New Releases
* None
Discussions
* Implementing a Hierarchical BeanManager
* Next release date and content
Community
* New committer, Martin Koci, 7 January 2012
-----------------------------------------
Attachment AC: Status report for the Apache Pig Project
Pig is a platform for analyzing large data sets that consists of a
high-level language for expressing data analysis programs, coupled
with infrastructure for evaluating these programs. The salient
property of Pig programs is that their structure is amenable to
substantial parallelization, which in turns enables them to handle
very large data sets.
Releases:
* Pig 0.9.2 released on 01/22/12.
Community:
* No new committers or PMC members
* 264 subscribers to the dev mailing list (247 in the last report)
* 741 subscribers to the user mailing list (681 in the last report)
Status of branding checklist:
Project Naming and Description: DONE
Website Navigation Links: DONE
Trademark Attributions: DONE
Logos and Graphics: NOT STARTED
Project Metadata: NOT STARTED
-----------------------------------------
Attachment AD: Status report for the Apache Pivot Project
Apache Pivot is a platform for building installable Internet
applications (IIAs). It combines the enhanced productivity and
usability features of a modern user interface toolkit with the
robustness of the Java platform.
Status
As usual we had a low levels of traffic in our users mailing lists,
but usually we are able to give an answer on fast time.
Little activity on dev mail list and issue tracker, but sometimes we
receive some patches from our users via JIRA.
I tried many times to get more committers, but nothing new at the moment.
On the progress of the project, we are still working on bug fixing,
and we proceed slowly because all of us can work on it only at spare time.
After we'll start to develop our next release with many new features.
Issues
There are no issues that require the board's attention at this time.
Releases
No new Release, but we are working on a maintenance one: 2.0.2,
to be releases in a few months.
Branding/naming issues:
During the last quarter I re-read the revised branding docs, identify
all things that has to be done, and fix some of them.
Remaining issues are:
* main site navigation needs some additional links
* create a DOAP file
Legal issues:
None.
Infrastructure issues/needs:
INFRA-4355: Enable svnpubsub for Pivot web site - resolved
INFRA-4356: Enable svnpubsub for Pivot distrib - resolved
Community changes
No new committers were voted in since the last board report.
A PMC Member, Christopher Brind (brindy) has indicated (after a long
inactivity period) that he wants to leave the Pivot PMC.
There are no diversity issues regarding the PMC.
Note:
To try to get more interest from people, during last month I committed
and published some Pivot-related things under Apache-Extras (pivot-stuff).
-----------------------------------------
Attachment AE: Status report for the Apache Portals Project
Apache Portals exists to promote the use of open source portal technology.
We intend to build freely available and interoperable portal software in
order to promote the use of this technology. With the Pluto project, we
provide a reference implementation for the Java portlet standard. The
Jetspeed project is a full feature enterprise open source portal. The
Portals Applications project is dedicated to providing robust,
full-featured, commercial-quality, and freely available portlet
applications.
Status
No new releases since October, 2011 (last report)
There have been no changes to the PMC or committers group this
quarter. User list traffic is minimal.
-----------------------------------------
Attachment AF: Status report for the Apache ServiceMix Project
Project Status
While we continue to have an active community with good participation from
users on mailing lists, IRC, and issue reporting in Jira, we also have lost
some of our momentum now that major parts of the functionality are being
maintained in related projects like Apache Karaf and Apache Camel.
With the community objectives mentioned below, we want to ensure a new and
better focus for the Apache ServiceMix project.
Community
No changes since last report.
Community Objectives
Our current objective is to work on a ServiceMix 4.5.0 release.
We keep on working on the documentation and website to ensure both new and
existing users are finding their way around the project more easily.
Branding Status
* Project Naming And Descriptions : Compliant
* Website Navigation Links : Compliant
* Trademark Attributions : Non-compliant, will be compliant in new web site.
* Logos and Graphics : Current logo is not compliant, new logo will be
compliant
* Project Metadata : Compliant
Releases
* ServiceMix 4.4.1 in February
* A set of 23 OSGi bundles in February
* A set of 154 OSGi bundles in January to provide associated sources in the
maven repository for ease of debugging
-----------------------------------------
Attachment AG: Status report for the Apache Shiro Project
Apache Shiro is a powerful and flexible open-source application security
framework that cleanly handles authentication, authorization, enterprise
session management and cryptography.
We have no issues that require Board assistance at this time.
Releases:
- We are very happy to announce that we have released Apache Shiro 1.2 on
Tuesday, January 24 2012, after our last report. While 'just' a point
release, this effort constituted over a year's worth of work. We are
very excited for the community to have this release.
Community & Project:
- We are happy to report that Jared Bunting has become our newest PMC member.
He has been a valuable member of the team overall, and especially helpful
with Shiro's Guice integration.
- More articles, blog posts, tweets and tutorials are being written about
Apache Shiro every day. Google Analytics shows almost 100,000 page views
and 10,000 unique visitors per month, showing significant continued
project interest and community growth after leaving the Incubator a little
over a year ago.
-----------------------------------------
Attachment AH: Status report for the Apache Sling Project
Apache Sling is an OSGI-based scriptable web framework that uses a Java
Content Repository, such as Apache Jackrabbit, to store and manage content.
There are no issues which require board attention at the moment.
Community
No new committers or PMC members, the project is relatively quiet but mailing
lists are responsive.
Releases
* Apache Sling Commons Testing 2.0.10
Apache Sling Commons Scheduler 2.3.4
Apache Sling Commons Log 3.0.0
Apache Sling Commons Log Service 1.0.0
Apache Sling Adapter 2.0.12
Apache Sling Installer Core 3.3.4
Apache Sling Launchpad API 1.1.0
Apache Sling Launchpad Installer 1.1.0
Apache Sling Maven JSPC Plugin 2.0.6 (February 7th, 2012)
* Apache Sling API 2.2.4
Apache Sling Adapter 2.0.10
Apache Sling Scripting JSP Taglib 2.1.6
Apache Sling Rewriter 1.0.2
Apache Sling JCR ContentLoader 2.1.4
Apache Sling JCR Base 2.1.2
Apache Sling Servlet Resolver 2.1.2
Apache Sling Security 1.0.0 (January 30th, 2012)
* Apache Sling Scripting API 2.1.4
Apache Sling Scripting Core 2.0.20
Apache Sling i18n 2.2.0
Apache Sling Installer Core 3.3.2
Apache Sling Scripting Java 2.0.2
Apache Sling Scripting JSP 2.0.20 (January 16th, 2012)
* Apache Adapter Annotations 1.0.0
Apache Sling Maven Sling Plugin 2.1.0 (January 14th, 2012)
* Apache Sling Settings 1.1.0
Apache Sling Commons ClassLoader 1.2.4
Apache Sling Commons Scheduler 2.3.2
Apache Sling Event 3.1.2
Apache Sling Installer Core 3.3.0
Apache Sling Installer Configuration Factory 1.0.4
Apache Sling Launchpad Installer 1.0.6
Apache Sling JCR Installer 3.1.2
Apache Sling Thread Dumper 0.2.2 (January 6th, 2012)
Documentation
* Website documentation is steadily improving
Project Branding
* Project Website Basics: done
* Project Naming And Descriptions: done
* Website Navigation Links: partial
** Open Question regarding "License" link
* Trademark Attributions: done
** Attribution on footer of each page
* Logos and Graphics: open
** TM missing from all Logos
* Project Metadata: done
Licensing and other issues
* none
-----------------------------------------
Attachment AI: Status report for the Apache SpamAssassin Project
-----------------------------------------
Attachment AJ: Status report for the Apache Synapse Project
Apache Synapse is a highly performant, flexible, lightweight
Enterprise Service Bus and mediation framework.
Community
We have nominated 2 new committers - Sadeep and Miyuru.
In addition we implemented a new policy that all committers are PMC members.
This has resulted in a larger PMC.
Two PMC members took this opportunity to become emeritus and we would like to
thank Oleg and Rajith for their efforts.
The level of participation on mailing lists is consistent and active, and
neither growing nor shrinking. However, a number of new users have started
asking questions this quarter.
During the reporting period there have been 73 commits from 5 committers.
Releases
We did a Synapse 2.1 release including the following features:
- Support for creating and managing REST APIs with URL patterns and URI
templates
- Define sequences and endpoints as templates and reuse seamlessly across the
whole configuration
- Payload factory mediator for constructing custom XML payloads
- Recipient list endpoint
- HTTPD like access logging capability in the NHTTP transport
- Message stores and message processors for implementing complex integration
patterns and advanced messaging scenarios
- Receiving sequence support in the send mediator to make service chaining
easier
- Conditional router mediator for implementing complex routing scenarios with
many conditions and rules
Board issues
None identified.
-----------------------------------------
Attachment AK: Status report for the Apache Tiles Project
Apache Tiles is a templating framework built to simplify the development of
web application user interfaces.
The Tiles PMC is in the middle of a slow, but steady reconstitution. This
quarter, like most quarters, has been characterized by slow progress. The
development team is aware that it has been a while since our last release and
discussion is underway to bring things together for a 3.0.0 release, which will
probably be Beta quality. We have not added any new PMC members this quarter,
but there have been a couple of outside contributions that may someday lead to
new committers if they continue.
As I've stated before, we believe that, at some point the original PMC will be
mostly replaced by new members and a new chair will be named. We don't have a
timeline for that right now, but it does feel like the new effort still has
legs.
-----------------------------------------
Attachment AL: Status report for the Apache Tomcat Project
General:
Continued healthy activity across multiple components and
responsiveness on both dev and user lists.
Issues:
There are no issues requiring Board attention at this time.
Releases:
* Apache Tomcat 7.0.26
* Apache Tomcat 7.0.25
* Apache Tomcat 5.5.35
* Apache Tomcat Connectors 1.2.33
* Apache Tomcat Native 1.1.23
* Apache Taglibs Parent POM 1
* Apache Tomcat Maven Plugin 2.0-beta-1
Community:
Olivier Lamy has been elected as new Apache Tomcat PMC member.
Security:
* CVE-2012-0022 Denial of service
* CVE-2011-3375 Information disclosure
* CVE-2011-1184 Multiple weaknesses in HTTP DIGEST authentication
Note: Mitre elected to break this issue down into multiple issues
and have allocated the following additional references to parts of
this issue: CVE-2011-5062, CVE-2011-5063 and CVE-2011-5064.
The Apache Tomcat security team will continue to treat this as a
single issue using the reference CVE-2011-1184.
Trademark:
Detailed status:
https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt
Tomcat PMC initiated licensing discussion with Oracle regarding a
couple of issues with Oracle's JSTL release. Waiting for the response
from their legal team.
-----------------------------------------
Attachment AM: Status report for the Apache UIMA Project
Board report for Apache UIMA, for March 2012.
Apache UIMA's mission: the creation and maintenance of open-source
software related to the analysis of unstructured data, guided by the
UIMA Oasis Standard.
Releases:
No releases since last report, but had 4 release candidates for the
C++ version of the UIMA framework, and it's pretty close to a release.
UIMA-AS (Asynchronous Scaleout) is being worked on for release.
Activity:
Typical mailing list activities for this quarter. We did notice that
the approximate downloads (as reported here:
http://people.apache.org/~vgritsenko/stats/projects/uima.html#Downloads-N1008F)
seems to have doubled in the last 2 quarters.
The Lucene project has a new adapter that enables using UIMA annotators for
tokenizing the stream, in their trunk (not yet released).
Community:
Peter Klügl joined the PMC.
Issues: No Board level issues at this time
Trademarks/Branding:
This is now complete:
Branding checklist:
Project Website Basics - done
Website Navigation Links - done
Trademark Attributions - done
Logos and Graphics - done
Project Metadata - done
Read PMC Branding Responsibilities - done,
all PMC members have confirmed
-----------------------------------------
Attachment AN: Status report for the Apache Whirr Project
Status report for the Apache Whirr project - March 2012
Whirr is a library for running services in the cloud. Whirr graduated from the
incubator in August 2011.
Community
---------
We have a healthy, growing community as shown by the growing number of
messages on the dev and user lists. Last month we voted in two new committers:
Frank Scholten and Ioannis Canellos. Paul Baclace gave a lightning talk about
Whirr at BigDataCamp before O'Reilly's Strata conference in February.
No new PMC members have been added since the last board report (December 2011).
There are no issues that require the board attention.
Community Objectives
--------
Over the coming quarter we plan to make improve the reliability of launching
Whirr clusters, as well as make clusters resizable and reconfigurable. We
would also like to support more services on more cloud providers.
Releases
--------
Version 0.7.0 was released in December, and a bugfix release 0.7.1 was made
last month. We are close to a 0.7.2 release later this month.
-----------------------------------------
Attachment AO: Status report for the Apache Wicket Project
Status report for the Apache Wicket Project March 2012
Apache Wicket is a Java framework for creating highly dynamic, component
oriented web applications.
Things worthy of note:
- Working with Git is great, the team thanks infra@ for their support
- Voted in a new committer and PMC member: Emond Papegaaij
- One release has been completed: 1.5.4
- Work on Wicket 6 is in its final stages and we'll be releasing a first
beta soon, and hope to have 6.0.0 complete with our next report.
On using Git
I asked our PMC for their view whether Git has changed any community dynamics
and here are their reactions (I've summarized a bit).
- Applying a patch over several branches (e.g. using 'git cherry-pick') is
a lot easier
- With the exception of much easier patch and branch management, which is a
huge win), I don't think anything has really changed community-wise. We
still communicate with the community via jira and patches.
- Git is just a source control tool, it's not a community tool.
One committer notes that his old SVN workflow-merging between branches-is
still engrained in his brain, but he's slowly adopting Git.
Compliance with branding/trademark guidelines
Only our logo on the webpage does not comply in missing a TM. We're still
working on a new web design and will incorporate the TM in that design. All
other items on the checklist are fulfilled.
-----------------------------------------
Attachment AP: Status report for the Apache XML Project
-----------------------------------------
Attachment AQ: Status report for the Apache XMLBeans Project
-----------------------------------------
Attachment AR: Status report for the Apache ZooKeeper Project
ZooKeeper is a reliable coordination service for distributed
applications.
There were three new releases in the last quarter; 3.4.1, 3.4.2,
3.4.3. All of them are bug fix releases. 3.3.5 is expected soon as a
bug fix release on the 3.3 branch.
Trunk is also under development for an eventual 3.5.0 release. So far
primarily code cleanup and refactoring has been applied to trunk.
We intend to do a 3.5.0 release in June. Our focus is on scalability,
jdk7 and openjdk support, maven build/rel, testing and audit logging.
Community:
Apache ZooKeeper had its first official meetup in Feb.
http://www.meetup.com/zookeeperusergroup/events/49372662/
It was very well attended and received good feedback. This was an
effort to collect feedback from users and to create a more vibrant
developer community for ZooKeeper. We intend to do it every 3
months and get more participation from our users.
Mailing list activity continues to be high and we are seeing more
contributor activity than we've seen in past quarters.
* 8 active committers representing 5 unique organizations
* 7 active PMC members representing 4 unique organizations
* 298 subscribers on dev (up from 276 last quarter)
* 597 subscribers on user (up from 551 last quarter)
BOOKKEEPER
Bookkeeper is a distributed, reliable, and high performance logging
service. The project also includes Hedwig which is a highly scalable
Pub/Sub service built on top of ZooKeeper and Bookkeeper with strong
durability guarantees.
We are working towards our next release, 4.1.0, and we are planning
on having it out late March. We are also getting ready for our first
large-scale deployment at Yahoo!. We will report on our experience as
soon as we have concrete information.
Community:
* 33 subscribers to bookkeeper-dev
* 35 subscribers to bookkeeper-user
* 16 reporters of Jira issues
* 6 patch contributors
-----------------------------------------
Attachment AS: Status report for the Apache Thrift Project
Thrift is a framework for providing cross-platform RPC and serialization.
Project Status
--------------
This is a status report on the Apache Thrift website as requested by
Greg Stein on Sunday, March 4, 2012. The Apache Thrift website has
been minimally maintained since the projects initial incubation and is
currently in the process of a new reworking. We are investigating
different build mechanisms which will allow for us to use markdown as
the primary site language to facilitate easier community contributions
as well as a new site structure. We are also looking at possibly
moving our tutorials and how-to guides from the Apache provided wiki
and integrate them directly into the Apache Thrift site.
The following is our progress in updating the content on the new
Apache Thrift website to meet the requirements in the Branding Report
Checklist:
Project Website Basics
- Complete
Project Naming And Descriptions
- In progress: updating all references throughout the site to
comply with the ASF standard, "Apache Thrift"
Website Navigation Links
- In progress: adding appropriate links
Trademark Attributions
- Complete. added to new footer
Logos And Graphics
- Complete. currently no logo or graphics.
Project Metadata
- complete.
Community
---------
Roger Meier was voted into the Apache Thrift PMC.
Community activity is very strong. We are seeing a growth around new
client libraries and new users submitting tickets along with patches
for issues.
Releases
--------
11.29.2011 release version 0.8.0. Starting organization for our next
major release, 0.9.0.
-----------------------------------------
Attachment AT: Status report for the Apache OpenJPA Project
There are no items requiring board attention at this time.
* Highlights
Apache OpenJPA provides POJO persistence for stand-alone JSE, JEE
container and many other lightweight frameworks, such as Tomcat,
Spring or OSGi.
* Community
Mailing lists continue to be very active and many instances of developers
migrating from other vendors to OpenJPA can be cited.
The developer community had maintained steady rate of defect resolution
and support for previous releases.
* Governance
We continue to monitor contributors for possible committers and
PMC members.
* Releases
OpenJPA 2.2.0 version has been released on February 12, 2012.
Albert Lee was the Release Manager.
-----------------------------------------
Attachment AU: Status report for the Apache Mahout Project
Apache Mahout provides implementations of machine learning algorithms
(collaborative filtering, clustering, classification, and more) for
large-scale data, mostly via Hadoop-based implementations.
ISSUES
There are no issues requiring board attention at this time.
CURRENT ACTIVITY
Activity has remained high during the past 3 months. We completed our
0.6 release on Feb. 6th that closed 182 JIRA issues.
Now we are embarked upon a new 0.7 release. The goal of 0.7
is to clean up and refactor existing functionality to improve
consistency and improve user experience.
Code freeze for 0.7 is targeted for May 15.
A 1.0 release is not yet on the horizon.
COMMUNITY
We have two new committers since our last report:
- Paritosh Ranjan
- Tom Pierce
MAHOUT DISTRIBUTIONS
Mahout now has multiple commercial distributions.
MAHOUT IN PRINT
"Mahout in Action", Owen, Anil, Dunning & Friedman is being well
received.
(http://manning.com/owen/)
-----------------------------------------
Attachment AV: Status report for the Apache JAMES Project
The Apache JAMES Project delivers a rich set of open source modules
and libraries, written in Java, related to internet mail which build
into an advanced enterprise mail server.
ISSUES
There are no issues requiring board attention at this time.
CURRENT ACTIVITY
Eric Charles tries to get Apache James Server 3.0-beta4 released
COMMUNITY
We added one new committer this quarter.
RELEASES
We did the following releases during this period:
* Apache James jSieve 0.5
* Apache James Mailbox 0.5
* Apache James Imap 0.3
TRADEMARKS / BRANDING
* Project Naming And Descriptions : use proper Apache forms, describe
product, etc -> Done
* Website Navigation Links : navbar links included, link to
www.apache.org included -> Done
* Trademark Attributions : attribution for all ASF marks included in
footers, etc. -> Done
* Logos and Graphics : include TM, use consistent product logo on your
site -> We lack someone which can do that atm. We will look at it
* Project Metadata : DOAP file checked-in and up to date -> Not yet
------------------------------------------------------
End of minutes for the March 21, 2012 board meeting.
Index