Index
Links: 2012 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
January 24, 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 joined at 10:14
Jim Jagielski
Brett Porter
Sam Ruby
Directors Absent:
Greg Stein
Lawrence Rosen
Officers Present:
Craig L Russell
Ross Gardler
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of December 21, 2011
See: board_minutes_2011_12_21.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Doug]
No report was submitted.
B. President [Jim]
Thanks to our EA, the foundation calendar is a reality. If you need
access, just contact myself or Melissa.
Thanks also to Joe and Sam for cleaning up the main ASF page; when
pulling in content from the blog and/or mailing lists, some invalid
characters would leak out causing the site to look really, really bad.
Filtering was added to the CMS system to address this.
I will be starting the formal budgeting process this month.
The mailing lists have been relatively quiet; the foundation is
running on greased grooves.
C. Treasurer [Geir]
No report was submitted.
D. Secretary [Craig]
The office of secretary@ continues to run smoothly with help from official
and unofficial volunteers.
In December, 60 ICLAs and five CCLAs were received and filed.
E. Executive Vice President [Noirin]
No report was submitted.
F. Vice Chairman [Greg]
Nothing to report. There was an intent for me to run the
January meeting, but the date was moved to allow Doug to Chair
the meeting.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of JCP [Geir Magnusson Jr]
No report was submitted.
B. VP of Brand Management [Shane Curcuru]
See Attachment 2
C. VP of Fundraising [Serge Knystautas / Sam]
See Attachment 3
D. VP of Marketing and Publicity [Sally Khudairi / Roy]
See Attachment 4
E. VP of W3C Relations [Sam Ruby]
See Attachment 5
F. Apache Legal Affairs Committee [Sam Ruby]
See Attachment 6
G. Apache Security Team Project [Mark Cox / Jim]
See Attachment 7
H. Apache Conference Planning Project [Nick Burch / Brett]
See Attachment 8
I. Apache Infrastructure Team [Sam Ruby / Jim]
See Attachment 9
J. Apache Travel Assistance Committee [Gavin McDonald / Larry]
No report was submitted.
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
A. Apache ACE Project [Marcel Offermans / Greg]
See Attachment A
B. Apache ActiveMQ Project [Hiram Chirino / Bertrand]
See Attachment B
C. Apache Aries Project [Jeremy Hughes / Shane]
See Attachment C
D. Apache Attic Project [Gianugo Rabellino / Brett]
See Attachment D
E. Apache Avro Project [Scott Carey / Shane]
See Attachment E
F. Apache C++ Standard Library Project [Martin Sebor / Sam]
No report was submitted. Attic resolution expected next month.
G. Apache Continuum Project [Emmanuel Venisse / Roy]
See Attachment G
H. Apache CXF Project [J. Daniel Kulp / Jim]
See Attachment H
I. Apache DB Project [Kristian Waagan / Larry]
See Attachment I
J. Apache Deltacloud Project [David Lutterkort / Bertrand]
See Attachment J
K. Apache Directory Project [Pierre-Arnaud Marcelot / Greg]
See Attachment K
L. Apache ESME Project [Richard Hirsch / Brett]
See Attachment L
There have been no new committers in the past year.
Might be a red flag.
M. Apache Geronimo Project [Kevan Miller / Roy]
See Attachment M
N. Apache Hadoop Project [Arun Murthy / Bertrand]
See Attachment N
O. Apache HBase Project [Michael Stack / Jim]
See Attachment O
There appears to be a discrepancy in the url for the hackathon.
AI Brett: follow up with PMC and update minutes.
P. Apache Incubator Project [Noel J. Bergman / Greg]
See Attachment P
Action Item: Doug to convey list of items that should have been
caught by the Incubator prior to forwarding, and to request that
the Incubator PMC more carefully review the reports before they
are sent.
Q. Apache James Project [Norman Maurer / Sam]
See Attachment Q
R. Apache JMeter Project [Sebastian Bazley / Larry]
See Attachment R
S. Apache Mahout Project [Jeff Eastman / Shane]
See Attachment S
T. Apache Maven Project [John Casey / Roy]
See Attachment T
U. Apache MINA Project [Niklas Gustavsson / Brett]
See Attachment U
V. Apache MyFaces Project [Gerhard Petracek / Jim]
See Attachment V
W. Apache Nutch Project [Julien Nioche / Shane]
See Attachment W
X. Apache ODE Project [Tammo van Lessen / Bertrand]
See Attachment X
Y. Apache OpenEJB Project [David Blevins / Larry]
See Attachment Y
Z. Apache OpenJPA Project [Pinaki Poddar / Greg]
See Attachment Z
AA. Apache PDFBox Project [Andreas Lehmkühler / Sam]
See Attachment AA
AB. Apache Shindig Project [Paul Lindner / Jim]
See Attachment AB
AC. Apache SpamAssassin Project [Daryl C. W. O'Shea / Shane]
No report was submitted. The project is expected to
submit a resolution requesting to change the chair.
AD. Apache Struts Project [Rene Gielen / Sam]
See Attachment AD
AE. Apache Tapestry Project [Howard M. Lewis Ship / Greg]
See Attachment AE
AF. Apache Tcl Project [David N. Welton / Bertrand]
No report was submitted.
AG. Apache Thrift Project [Bryan Duxbury / Larry]
See Attachment AG
AH. Apache Tika Project [Chris A. Mattmann / Roy]
See Attachment AH
AI. Apache Traffic Server Project [Leif Hedstrom / Brett]
See Attachment AI
AJ. Apache Web Services Project [Glen Daniels / Jim]
See Attachment AJ
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Establish the Apache Gora 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 mapping objects to NoSQL databases
for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Gora Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Gora Project be and hereby is
responsible for the creation and maintenance of software
related to open-source software for mapping objects to NoSQL
databases; and be it further
RESOLVED, that the office of "Vice President, Apache Gora" 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 Gora Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Gora 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 Gora Project:
* Sertan Alkan <sertan@apache.org>
* Andrzej Bialecki <ab@apache.org>
* Ioannis Canellos <iocanel@apache.org>
* Ferdy Galema <ferdy@apache.org>
* Dogacan Guney <dogacan@apache.org>
* Andrew Hart <ahart@apache.org>
* Chris Mattmann <mattmann@apache.org>
* Lewis John McGibbney <lewismc@apache.org>
* Julien Nioche <jnioche@apache.org>
* Henry Saputra <hsaputra@apache.org>
* Enis Soztutar <enis@apache.org>
* David Woollard <woollard@apache.org>
RESOLVED, that the Apache Gora Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Gora sub-project; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Gora sub-project encumbered upon the
Apache Incubator Project are hereafter discharged.
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Lewis John McGibbney
be appointed to the office of Vice President, Apache Gora, 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 7A, Establish the Apache Gora Project, was
approved by Unanimous Vote of the directors present.
B. Change Chair for Apache Pivot
WHEREAS, the Board of Directors heretofore appointed Todd
Volkert to the office of Vice President, Apache Pivot, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Todd Volkert from the office of Vice President, Apache
Pivot, and
WHEREAS, the Project Management Committee of the Apache Pivot
project has chosen by vote to recommend Sandro Martini as
the Successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Todd Volkert is
relieved and discharged from the duties and responsibilities of
the office of Vice President, Apache Pivot, and
BE IT FURTHER RESOLVED, that Sandro Martini be and hereby
is appointed to the office of Vice President, Apache Pivot, 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 7B, Change Chair for Apache Pivot, was approved
by Unanimous Vote of the directors present.
C. Establish the Apache Empire-db 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 related to api-based SQL generation and utilization
of RDBMS features, for distribution at no charge to the public.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Empire-db Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further
RESOLVED, that the Apache Empire-db Project be and hereby is
responsible for the creation and maintenance of software
related to api-based SQL generation and utilization
of RDBMS features; and be it further
RESOLVED, that the office of "Vice President, Apache Empire-db" 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 Empire-db Project, and to have primary
responsibility for management of the projects within the scope of
responsibility of the Apache Empire-db 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 Empire-db Project:
* Martijn Dashorst <dashorst@apache.org>
* Francis De Brabandere <francisdb@apache.org>
* Rainer Döbele <doebele@apache.org>
* Eike Kettner <ek@apache.org>
* Jörg Reiher <reiher@apache.org>
* Benjamin Venditti <benniven@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Francis De Brabandere
be appointed to the office of Vice President, Apache Empire-db, 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 Empire-db 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 Empire-db Project; and be it further
RESOLVED, that the Apache Empire-db Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Empire-db podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache
Incubator Empire-db podling encumbered upon the Apache Incubator
Project are hereafter discharged.
Special Order 7C, Establish the Apache Empire-db Project, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Apache Open Office Extensions site and SourceForge offer
Discuss this (from Ross Gardler on board@) unless already done.
The aoo pmc wants to arrange for hosting of ooo extensions now on
the oo.o site.
Extensions include templates and dictionaries, which are not
necessarily licensed to Apache.
Infra is willing to host a metadata site but not a download site,
due to bandwidth issues.
Sourceforge has volunteered to host a site, giving root access to
authorized ppmc folks.
Downloads from sourceforge have advertising, which pays for running
the service.
Apache.org domains should not have advertising on them.
Advice from board: proceed with sourceforge; can host extensions on
sourceforge.org domain; ok for non-apache download site to have
advertising; continue to work on a long term solution.
B. Termination of VP, JCP
AI Jim: discuss with Geir, prepare a resolution for termination for
February 2012.
C. How is the calendar supposed to work? There is a Feb 9th item in
the calendar. Is the EA tasked with sending out reminders?
Jim and Melissa are working to add items to the calendar. The plan
was for Melissa to manage the items on the calendar, not to remind
folks. But Melissa can set up reminders on request.
Should the calendar be publicly available? Not now, as there are
private items included. If we want the calendar to be public, we
will need to have a separate calendar. But the calendar is intended
for the use of the board so it's not clear why the calendar should
be public, except that's what Apache usually does.
Access to the calendar is by secret url, that can be changed at
will. Security by obscurity. Any member should be able to get the
secret url on request to Melissa.
9. Review Outstanding Action Items
* Philip: follow up on /dist with Perl PMC
Status: Action Item transferred to Sam
* Larry: discuss legal trademark issues with ActiveMQ PMC.
Status: Shane to follow up with the ActiveMQ PMC.
* Greg: discuss security handling with DB PMC.
Status: no update.
* Craig: see that Olio provenance is complete and start retirement process.
Status: Provenance is complete; repository is read-only.
Mail lists still need to be removed.
* Jim: Assist C++ Standard Library in move to the attic
Status: They agree attic makes sense. Reso will be provided
for next month.
* Jim: prepare a resolution to create a VP of OSI.
Status: Awaiting formal affiliate agreement from OSI.
* Geir Magnusson Jr: prepare to discuss termination of VP, JCP at next
board meeting
Status: Jim now has an action item to get with Geir
* Jim: discuss calendar improvements suggested by Shane with Melissa
Status: covered in the Discussion Items
* Sam and Shane: discuss invoicing of sponsors with Serge.
Status: no more follow up needed
* Sam: follow up with Zookeeper PMC re: adoption of Curator project
Status: no update
* Bertrand: discuss with Sally how to get her invoices submitted in
the appropriate place in svn.
Status: Done - Sally will send future invoices to board@ and
ask for someone to commit them to svn.
If there's a regular schedule for paying invoices,
she'd like to be informed so that she can get them in
at the appropriate time.
10. Unfinished Business
11. New Business
12. Announcements
Props to Sam on whimsy tools.
13. Adjournment
Adjourned at 10:59 a.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of JCP
-----------------------------------------
Attachment 2: Report from the VP of Brand Management
Operations And Community
========================
Formally contacted Team OpenOffice.org e.V. again to insist that they
correct their misuse of our OpenOffice.org brand.
Approve request for Apache Rat's potential project name.
Approved clarifications of Apache Extras project guidelines and package
naming suggestions brought up in conjunction with ComDev; thanks to Chris
Mattman, Benson, and others for their helpful work on the thread.
External Requests
=================
As usual, answered a handful of regular brand usage requests on trademarks@,
typically by referring to our published policies and FAQs. FAQ drafts
to provide answers for more common publishing requests are in the works.
Trademark Registrations
=======================
The CEO of Sonatype has agreed to assign the "Maven Central" mark
registration to the ASF once their US application is completed, as
part of the MOU the Maven PMC is working on with Sonatype.
-----------------------------------------
Attachment 3: Report from the VP of Fundraising
-----------------------------------------
Attachment 4: Report from the VP of Marketing and Publicity
I. Budget: all outstanding invoices had been paid before the end
of the calendar year. Special thanks to Sam Ruby and Jim Jagielski
for processing and expediting payments.
II. Fundraising/Branding/Marketing liaison: no official meetings
or discussions have taken place since ApacheCon.
III. Press Releases: the following announcements were issued
- via PRNewsWire service - 20 December: Open Letter to the Open
Document Format Ecosystem from The Apache Software Foundation - via
NASDAQ GlobeNewswire service - 4 January: The Apache Software
Foundation Announces Apache Hadoop(tm) v1.0
IV. Informal Announcements: in addition to the above announcements
also posted on the ASF blog, the following items were announced on
@TheASF Twitter feed:
- 24 November: #Apache returns to Oz! Join the next @BarCampApache 10 December
in #Sydney! barcamp.org/BarCampApacheS… #BarCamp #OpenSource #TheApacheWay
- 25 November: The goodness continues: the #Apache #HTTP Server powers nearly
342M Websites globally, according to @Netcraft November Web server survey.
- 8 December: Join us at @BarCampApache 10 December in #Sydney!
barcamp.org/w/page/3212102… #BarCamp #OpenSource #TheApacheWay
- 20 December: Open Letter to the Open Document Format Ecosystem from The
Apache Software Foundation s.apache.org/P7e #Apache #OpenOffice #ODF
- 20 December: The #Apache #HTTP Server powers more than 362M Websites
globally --a 20M increase from November-- according to @Netcraft Web server
survey.
- 4 January: The Apache Software Foundation Announces #Apache #Hadoop™ v1.0
s.apache.org/hX #Cloud #BigData #OpenSource
- 9 January:#Apache #Callback (Incubating; nee #Phonegap) also received an
InfoWorld Technology of the Year Award. Well done! s.apache.org/oM
- 9 January: Congratulations to #Apache #Hadoop for winning an InfoWorld 2012
Technology of the Year Award! s.apache.org/l3 #OpenSource #Cloud
V. Future Announcements: upcoming releases include Deltacloud
graduating as a TLP and the "Have You Contributed?" campaign. Those
PMCs wishing to announce major project milestones should 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: in spite of the holidays, we've had a very
busy month with extensive press coverage on high-profile projects
including Apache OpenOffice.org and Apache Hadoop.
VII. Analyst Relations: quotes from Forrester, Gartner, and RedMonk
were secured for the Apache Hadoop announcement. We have been
actively briefing various analysts on "Apache: the foundation of
the Cloud" as well (theme created in 2009, still having great
traction).
VIII. ApacheCon liaison: no further contact from the producer
regarding planner expenses and related reimbursements.
IX. (Non-ASF) Industry Events and Outreach liaison: Sally is working
with VP ConCom Nick Burch regarding our participation, partnership,
and promotion at OSCON.
X. Newswire accounts: we have 5 pre-paid press releases with
PRNewswire remaining through 3 March 2012. Sally has purchased a
25 pre-paid pack to disseminate press releases over the NASDAQ
GlobeNewswire service using the HALO Worldwide account (these
distributions are at a lower cost than PRNewswire, and will be used
as our primary distribution channel for project-based announcements,
as well as overflow for any Foundation-level statements). # # #
-----------------------------------------
Attachment 5: Report from the VP of W3C Relations
No changes this month.
-----------------------------------------
Attachment 6: Status report for the Apache Legal Affairs Committee
Mailing list has returned back to quieter times, with the focus being
on JIRA entries. One such JIRA issue merits calling out:
Legal-177: Aggregation of GPL dictionaries with Apache Open Office is likely
to be approved by the time of this board meeting.
-----------------------------------------
Attachment 7: Status report for the Apache Security Team Project
For December 2011: 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.
3 Support question
2 Phishing/spam/attacks point to site "powered by Apache"
6 Vulnerability reports, of which:
3 [httpd, via security@apache.org]
1 [httpd, via security@httpd.apache.org]
1 [oo, via securityteam@openoffice.org and officesecurity@lists.freedesktop.org]
1 [struts, via security@struts.apache.org]
Reminder: vulnerability handling process explained at
http://apache.org/security/committers.html
-----------------------------------------
Attachment 8: Status report for the Apache Conference Planning Project
General
-------
Our announcement about the OSCON CFP was thwarted by the message not being
moderated through in time. (Everyone on concom@ got the cc'd copy, which is
one of the reasons why we didn't notice the problem in time...) This is a
shame, but we think at least some Apache talks were submitted anyway.
We have received a few third party event requests, all of which have seemed
fine in theory, but all of which are awaiting a few more bits of information
before approval can be granted.
Small Events
------------
The planned Knocktree Retreat won't be going ahead, as there weren't enough
people interested in attending on any of the weekends the venue is
available.
There was a feeling that a Retreat style event should be tried during the
week, but the venue used in the past isn't able to support this. No suitable
alternate venues have been found, and there doesn't seem that much volunteer
energy to drive it (largely due to the failure to attract people for the
planned weekend one)
On a more positive note, a DC event is in the planning.
ApacheCon
---------
We're still waiting to hear back from SAP on which week in late 2012 we can
have, and linked to that which exact conference centre + space we've got.
(This is the process of turning our outline approval into a specific space
on a specific date). Christmas seems to have got in the way of the approval
process.
A few areas of the RFP have generated lots of discussion, but we think we've
now finished. We're hoping to open the RFP this week, once the new list to
capture submissions is open and people are subscribed
*Update 23rd Jan* The RFP has now opened
Committee
---------
No new committee members have been added this month, and there are not
currently any in the pipeline.
Planning for the future of the committee has taken a backseat to the RFP,
but with any luck should be tackled this coming month
-----------------------------------------
Attachment 9: Status report for the Apache Infrastructure Team
Still attempting to pursue a github FI instance for ASF use.
Intervision LOC has still not been filled out and sent off.
We've determined there is adequate space (9U free) for us
to install our new gear in SARA. However we are in need
of an additional switch, which is tasked to Uli Stärk for
purchase.
Awaiting a final decision from the OpenOffice podling regarding
hosting of extensions and templates. They are considering
either hosting those services locally at the ASF or with
SourceForge.
Joe spent a few hours training Melissa (EA) on svn use.
A google calendar is now available for everyone's use
thanks to Melissa.
Secured and rolled out a wildcard cert from Thawte.
Dealt with a minor security issue in the Nexus installation,
reported by Sebastian Bazley.
Partitioned our SSL termination for our linux hosts to separate
VM's for additional security.
Began deploying puppet for eventual management of our linux hosts.
Dealt with a benign security incident on modules.apache.org.
Further enhanced CMS performance with the introduction of parallel
builds.
-----------------------------------------
Attachment 10: Status report for the Apache Travel Assistance Committee
-----------------------------------------
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 first one since ACE graduated as a TLP.
Releases:
* December 11th, 2011: ACE 0.8.1-incubator
Activity:
* Several ACE committers were present at ApacheCon NA 2011 and we had
multiple talks/training sessions.
* We are structuring the community after the graduation (PMCs, PMC
Chair definition).
* Some informal discussions started during the ApacheCon in order to
identify relationship between ACE and others projects (Karaf (already
started), Archiva, Whirr, etc).
* We are now focusing on the first TLP release.
* Work on the resources (website, documentation, etc) will start soon
to promote ACE as a TLP and give more information to the users.
Changes in committers/PMC members:
* None so far after establishing the project as a TLP.
Committer/PMC diversity:
* No concerns, our PMC of 8 has 6 different unique organizations.
Branding/naming issues:
* No issues.
* As part of the website migration, we will double check
logos/trademarks.
* Discussing the design of a "Powered by Apache ACE" logo.
Legal issues:
* None.
Infrastructure issues/needs:
* Working with infra to migrate everything, going well:
https://issues.apache.org/jira/browse/INFRA-4265
-----------------------------------------
Attachment B: Status report for the Apache ActiveMQ Project
Apache ActiveMQ is a popular and powerful open source messaging
server. Apache ActiveMQ is fast, supports many Cross Language Clients
and Protocols, comes with easy to use Enterprise Integration Patterns
and many advanced features while fully supporting JMS 1.1 and J2EE
1.4.
Community:
* The development and user lists continue to stay active.
* Torsten Mielke we voted in as a new committer.
* PMC members Aaron Mulder and Alan D. Cabrera changed status to emeritus
Development:
* ActiveMQ 5.6 is still being worked on.
* Apollo 1.0 is approaching completion. Several betas have been
released and it has shown to be stable and easy to manage. The Apollo
messaging engine will likely be the path used to implement ActiveMQ
6.0.
Trademark / Branding Status:
* The activemq.org and activemq.com TLD's are owned by other entities
* Need to investigate if we should be using (R) instead of (TM) for
the ActiveMQ mark
* Sub-projects need to be reviewed to make sure they are also compliant
* Documentation and readme files will also be reviewed for compliance
Releases:
* Apache ActiveMQ-CPP v3.4.1
* Apache Apollo 1.0 beta 6
* Apache.NMS.Stomp v1.5.2
* Apache.NMS.ActiveMQ 1.5.2
-----------------------------------------
Attachment C: Status report for the Apache Aries Project
Apache Aries delivers a set of pluggable Java components enabling an
enterprise OSGi application programming model.
We have successfully executed on our 'release by bundle' approach. This
will help our users who would like to take updates of individual bundles:
"Small releases". Distribution releases containing sets of bundles that
combine well together will come later: "Big releases".
Releases
* Apache Aries Unit Test Support 0.4
* Apache Aries Util 0.4
* Apache Aries Proxy:
* Apache Aries Proxy API 0.4
* Apache Aries Proxy Service 0.4
* Apache Aries Proxy iTests 0.4
* Apache Aries Proxy Bundle 0.4
* Apache Aries Quiesce
* Apache Aries Quiesce Manager 0.3.1
* Apache Aries Quiesce Manager iTests 0.3.1
* Apache Aries Blueprint
* Apache Aries Blueprint Annotation API 0.3.2
* Apache Aries Blueprint Annotation Impl 0.3.2
* Apache Aries Blueprint Annotation iTests 0.3.2
* Apache Aries Blueprint CM 0.3.2
* Apache Aries Blueprint Core 0.4
* Apache Aries Blueprint iTests 0.4
* Apache Aries Blueprint JEXL evaluator 0.1.0
* Apache Aries Blueprint Sample 0.4
* Apache Aries Blueprint Sample for Testing Annotation 0.3.2
* Apache Aries Blueprint Sample Fragment for Testing Annotation 0.3.2
* Apache Aries Blueprint Test Bundle A 0.3.2
* Apache Aries Blueprint Test Bundle B 0.3.2
* Apache Aries Blueprint Test Quiesce Bundle 0.3.2
* Apache Aries Blueprint Bundle 0.4
* Apache Aries Blueprint Parser 0.4
* Apache Aries JNDI
* Apache Aries JNDI Core 0.3.1
* Apache Aries JNDI URL Handler 0.3.1
* Apache Aries JNDI RMI Handler 0.3.1
* Apache Aries JNDI Bundle 0.3.1
* Apache Aries JNDI Support for Legacy Runtimes 0.3.1
* Apache Aries JNDI "business logic" test bundle for Aries jndi-url
iTests 0.3.1
* Apache Aries JNDI Test Bundle for Aries jndi-url iTests 0.3.1
* Apache Aries JNDI iTests for jndi-url 0.3.1
Project Branding Board Report Checklist
Unfortunately no progress here.
* Project Website Basics : homepage is aries.apache.org (done)
* Project Naming And Descriptions : use proper Apache forms, describe
product, etc. (pending)
* Website Navigation Links : navbar links included, link to www.apache.org
included (pending - feather link done)
* Trademark Attributions : attribution for all ASF marks included in
footers, etc. (pending)
* Logos and Graphics : include TM, use consistent product logo on your
site (pending)
* Project Metadata : DOAP file checked-in and up to date (done)
Community update
There continues to be some good discussion on the user and dev lists. No
new committers since the last report.
There are no board level issues.
-----------------------------------------
Attachment D: Status report for the Apache Attic Project
No issues requiring board attention at this time. Since the
past board report, Harmony moved to the attic and process is
ongoing.
-----------------------------------------
Attachment E: Status report for the Apache Avro Project
Apache Avro is a cross-language data serialization system.
== Issues ==
There are no issues that require the board's attention at this time.
== Community ==
We added 4 Committers: Miki Tebeka, James Baldassari, Donna Alvarez, and
Thomas White.
October 2011 set a new record for messages on the dev mailing list (353).
We had strong activity in most language implementations.
== Releases ==
Avro 1.6.0 was released on November 1st, 2011.
Avro 1.6.1 was released on November 14th, 2011.
-----------------------------------------
Attachment F: Status report for the Apache C++ Standard Library Project
-----------------------------------------
Attachment G: Status report for the Apache Continuum Project
Apache Continuum is an enterprise-ready continuous integration server with
features such as automated builds, release management, role-based security,
and integration with popular build tools and source control management
systems.
Releases
--------
* None
Community
---------
* No activity.
* One committer at ApacheCon in November expressed interest in helping to
pick up work on a release and reignite activity.
* The PMC needs to review who is still active and whether the project can
move forward.
Development
-----------
* Zero development activity since the last report in September.
* Lots of fixes still on trunk but with no real strategy to release 1.4.1.
Project Branding Requirements
-----------------------------
* Project Website Basics - done
* Project Naming and Descriptions - not yet done
* Website Navigation Links - not yet 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 other board level issues at this time.
-----------------------------------------
Attachment H: Status report for the Apache CXF Project
Apache CXF is an open source services framework. CXF helps you build and
develop services using frontend programming APIs, like JAX-WS and
JAX-RS. These services can speak a variety of protocols such as SOAP,
XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports
such as HTTP, JMS or JBI.
Releases:
2.3.8 released
2.4.4 released
2.4.5 released
2.5.0 released
2.5.1 released
Committer added:
Oliver Wulff
Community updates:
The 2.5.0 release was done in late October (and subsequent 2.5.1 patch release
in December) which was a big milestone for CXF as it provided a bunch of new
features and enhancements. The response has been very good with several
requests on the lists and JIRA's filed and such. Some work has been started
to update the DOSGi subproject to the latest 2.5.1 release as well as
introduce some new features and enhancements there. A release of that should
be done soon.
Some work has been started on trunk to cleanup the code a bit (compile
warnings removed), enhance the OSGi support, etc... Early discussions on
ideas for 2.6.0 have started with the work targeting that.
13 committers committed changes during the period. A total of 987 commits
were done, with 519 of them on trunk. (the rest were back porting fixes to
branches as well as some work in the sandbox). From a diversity standpoint,
6 committers from one company were responsible for roughly 80% of the commits,
4 committers from a second at 7% and the remaining 13% among the other 3
independents. Those numbers are slightly concerning but not unexpected.
It should be noted, however, that the release manager for one of the releases
(2.4.4) was an employee from the second and was the first release in a long
time not managed by me (dkulp) which is a very welcome change.
-----------------------------------------
Attachment I: Status report for the Apache DB Project
The Apache DB TLP consists of the following subprojects:
o DdlUtils : a small, easy-to-use component for working with Database
Definition (DDL) files.
o Derby : an open source relational database implemented entirely in Java
o JDO : focused on building the JDO API and the TCK for
compatibility testing of JDO implementations.
o Torque : an object-relational mapper for Java.
== Status ==
There are no issues requiring board attention at this time.
Activities over the last quarter:
1) Apache DB is still not fully compliant with the branding
requirements. No progress this quarter (same as last quarter).
2) Ongoing efforts in the subprojects:
o DdlUtils: low activity maintenance
o Derby: focus on bugfixing, some feature work
o JDO: continued work on 3.1 maintenance release
o Torque: continued work on Torque 4
== Community ==
No PMC changes since August 2011.
No new committers since August 2010.
List subscriber counts stable (see July 2011 report for numbers).
== Releases ==
Derby: maintenance release 10.8.2.2 (October 24, 2011)
JDO: maintenance release 3.0.1 (November 13, 2011)
-----------------------------------------
Attachment J: Status report for the Apache Deltacloud Project
Deltacloud defines a web service API for interacting with cloud service
providers and resources in those clouds in a unified manner. In
addition, it consists of a number of implementations of this API for the
most popular clouds.
Their are no issues for board consideration
Community
---------
No new committers
Two Deltacloud talks planned for FOSDEM
Working on ASF press release announcing graduation to TLP
Releases/Development
--------------------
Posted release candidate for 0.5.0; need to post another rc because of a
couple minor issues that were found.
Work on DMTF CIMI frontend continues to progress.
Project setup
-------------
Migration to TLP is complete. There is one minor issue in that the old
incubator mailing list archives haven't been moved to the TLP yet.
-----------------------------------------
Attachment K: Status report for the Apache Directory Project
The Apache Directory Project provides directory solutions entirely written in
Java. These include a directory server, which has been certified as LDAP v3
compliant by the Open Group (ApacheDS), Eclipse-based directory tools (Apache
Directory Studio) and a client API that can be used to communicate with any
directory server (Apache LDAP API).
-- Community --
* No new committers
* No new PMC members.
-- Development --
* Apache LDAP API:
* Bug fixes and small additions.
* A new release is expected very shortly (to be included inside Apache
Directory Studio 2.0.0-M1).
* ApacheDS 2.0:
* Work continued on two main focus points:
* Make ApacheDS run in an OSGI container (using Apache Felix or Karaf).
* Include a transaction mechanism on top of our backend implementations.
* Apache Directory Studio 2.0:
* A lot of bug fixes and improvements have been made in order to be able
to release a first milestone version (2.0.0-M1) in early 2012.
-- Releases --
* One minor bugfix release for Apache Directory Studio Maven Plugin:
* 1.0.5 (January 2nd 2011)
-----------------------------------------
Attachment L: Status report for the Apache ESME Project
Apache ESME's mission: Enterprise Social Messaging Environment (ESME) is a
secure and highly scalable microsharing and micromessaging platform that
allows people to discover and meet one another and get controlled access
to other sources of information, all in a business process context.
Releases:
2011-08-29 1.3
Development:
We are continuing work on our 1.4 release. We hope to focus on Akka
and Apache Camel integration.
The level of development activity has decreased dramatically the last
1.5 months. We hope to increase the level of activity this quarter.
Community:
* No new committers
* No new PMC members.
Issues:
No Board level issues at this time
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 -> In progress
* Project Metadata : DOAP file checked-in and up to date -> Done
-----------------------------------------
Attachment M: Status report for the Apache Geronimo Project
Apache Geronimo is an open source server runtime that integrates
the best open source projects to create Java/OSGi server runtimes
that meet the needs of enterprise developers and system
administrators.
The community released our first Java EE 6 compliant
server (Geronimo 3.0-beta-1). 3.0-beta-1 is both web profile and
full profile compliant. There were additional releases of additional
components and server versions.
RELEASES
The community released 3.0-beta-1 versions of our
server, samples, and eclipse plugin. Geronimo 2.1.8 was also
released.
CONFERENCES
Two Geronimo presentations were given at ApacheCon in Vancouver.
COMMUNITY
The PMC accepted a code donation to the project from Hypobytes LTD.
NEW COMMITTERS
Trygve Hardersen was voted as a new committer on the project.
SECURITY
The Java HashTable collision Denial of Service vulnerability
reported in late December affected Geronimo releases. In response,
community has created several new releases and patches.
-----------------------------------------
Attachment N: Status report for the Apache Hadoop Project
Hadoop is a set of related tools and frameworks for creating and
managing distributed applications running on clusters of commodity
computers.
On the people side, we have new person join our ranks.
* We've added one new committer - Siddharth Seth.
On the project side, we have made some very exciting progress. We have
had a total of 3 releases:
- hadoop-0.23.0 released from trunk, first one off trunk in nearly 2 years.
- hadoop-0.22.0 released, branched in early 2011.
- hadoop-1.0.0 released of branch-0.20.2xx baseline (now branch-1)
- https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces21
- Work on further Hadoop 0.23.1 release is continuing, and is
scheduled for release at the end of the month
- Developer community is working well together. The public dialogue
among vendors who employ many in the developer community seems to
have died down since the last board report. No action from the
board is required at this stage.
- Some vendors are continuing to use the lists to promote their own
products. A few PMC members have responded to discourage this
practice, but not directly as the PMC. No action from the board is
required at this stage.
COMMON
Common is the shared libraries for HDFS and MapReduce.
Releases:
* 0.23.0 was released on 11th Nov, 2011.
* 0.22.0 was released on 10th Dec, 2011.
* 1.0.0 was released on 29th Dec, 2011.
Community:
* 42 committers
* 1433 subscribers on common-dev
* 2761 subscribers on common-user
* 1468 subscribers on general
New committers:
* 1 new committer has been added to this project.
HDFS
HDFS is a distributed file system that supports reliable replicated
storage across the cluster using a single name space.
Community:
* 41 committers
* 567 subscribers on hdfs-dev
* 985 subscribers on hdfs-user
MAPREDUCE
MapReduce is a distributed computation framework for easily writing
applications that process large volumes of data.
Releases:
* None this period.
New committers:
* 1 new committer has been added to this project.
Community:
* 42 committers
* 587 subscribers to mapreduce-dev
* 1118 subscribers to mapreduce-user
-----------------------------------------
Attachment O: Status report for the Apache HBase Project
HBase is a distributed column-oriented database built on top of Hadoop
Common and Hadoop HDFS
ISSUES FOR THE BOARD’s ATTENTION
None
RELEASES
0.90.5, a point release with 80 plus fixes over 0.90.4
Four 0.92.0 release candidates, our next major release.
COMMITTERS
We added three committers:
Kannan Muthukkaruppan (Facebook)
Karthik Ranganathan (Facebook)
Jonathan Hsieh (Cloudera)
COMMUNITY
We had a well attended developer pow-wow at salesforce in SF
on November 29th, 2011 [1]. Here is thread summarizing
discussion posted dev list [2].
We're having a meetup on the 19th of January at EBay [3].
16 committers
674 subscribers to the dev list
1521 subscribers to the user list
1. http://www.meetup.com/hackathon/events/41025972/
2. http://s.apache.org/zA
3. http://www.meetup.com/hbaseusergroup/events/46702842/
-----------------------------------------
Attachment P: Status report for the Apache Incubator Project
A number of substantive issues came up during the past month.
First, and although it was raised on the private list and therefore details
won't be part of the public report, we advise the Board that there is
substantial discussion regarding changing the Incubator VP, which has been
held for almost 8 years by the current VP.
Second, there is a dispute, both in the abstract and concretely, regarding
whether or not the ASF, via the Incubator, may play host to a community that
has forked a compatibly licensed codebase. Roy suggested that, in the
specific case:
> The VOTE was based on misleading information. The Incubator PMC should declare it
> void and request a new proposal. The existing Bloodhound podling should be
> placed on hold until this is sorted out.
Greg has said, more recently, that "the Bloodhound and Trac communities
already have a new non-fork plan and are executing on that now, on the
bloodhound-dev mailing list." If that comes to pass, perhaps no further
attention from the PMC and Board will be required on this issue. If not,
we'll have to revisit the specific case.
However, Bill Rowe has requested that the Incubator PMC formally put the
general matter to the Board: what policy do or should we have regarding a
community that wishes to fork a suitably licensed codebase and come to the
ASF? If so, what is that policy? Or is that decision still a matter to be
determined situationally by the Incubator PMC? For whatever it is worth,
the latter is the opinion of the Incubator VP, who recalls that more than
one successful ASF project started elsewhere and came to the ASF as a fork,
and not without some complaint from members of the outside community (e.g.,
Apache Felix).
Third, there was a lot of discussion surrounding a couple of Incubator
issues: 1) podlings being comfortably settled in the Incubator, and not
being focused enough on graduation; 2) Mentors being insufficiently active,
and thus not providing either proper guidance or oversight. We definitely
need to address these issues, promoting both Mentor involvement and
graduation from the Incubator. And, finally, Jukka spent time reviewing the
status of many of the older podlings, and recommending an action.
Perhaps not coincidentally, ACE, Gora and Bean Validation Framework are all
in graduation mode. But, meanwhile, Bloodhound (the podling previously
mentioned), DeviceMap and Flex have joined.
Below are podling reports. Sam Ruby has already reviewed the original list
prior to posting, and requested that specific posts not be provided to the
Board, as he was unhappy with their status:
Kato: has been in limbo for years due to Oracle. The podling needs
to decide what to do, or terminate
Bloodhound, HISE, JSPWiki and Openmeetings: missing
VXQuery: not signed off by a Mentor
Although initially requested to be excluded, the Celix and Tashi reports
were revised to provide at least some graduation guidance, and so their
reports are included, below.
---------------------------------------------------------
Any23
Any23 is defined as a Java library, a Web service and a set of command line
tools to extract and validate structured data in RDF format from a variety
of Web documents and markup formats. Any23 is what it is informally named an
RDF Distiller.
A list of the three most important issues to address in the move towards
graduation
1. Port Any23 code to ASF infrastructure and update license headers
2. Develop a strong community with organizational diversity and with
strong connections to other relevant ASF communities.
3. At least one Any23 incubating release
Any issues that the Incubator PMC (IPMC), Tika PMC, or ASF Board wish/need
to be aware of?
Yes, all of the code has been ported from Google Code to the ASF. Thanks to
Daniel Shahaf and Michele Mostarda for leading the charge here.
How has the community developed since the last report?
All ASF karma has been granted on the repository, and we've received a few
JIRA issues, but not from outside the core set of PPMC members as of yet. The
team needs to respond to Paolo Castagna's points regarding RDF frameworks and
collaboration, and will hopefully do so this month.
How has the project developed since the last report?
Any23 was voted into the Incubator by the IPMC on October 1, 2011.
We have Jenkins CI builds going thanks to Lewis John McGibbney, code up and
running at the ASF thanks to Michele and to Daniel, so we're all set to really
get kicking!
--------------------
Celix
Celix is an implementation of the OSGi Specification in C.
Celix entered incubation on November 2, 2010.
Over the last few months lots of work has been put into integrating APR and
updating the Celix code base to the proposed code style. This code style has
partially been documented on [1]. Also some effort has been put into
updating the source for Visual Studio, even though not yet finished some
interesting and helpful patches were submitted and applied.
In October an event was held to create more awareness for services, OSGi and
Celix in the Dutch embedded community. The attendance was great, and a
follow-up will be planned. Also, in November a talk was given at the
ApacheCon.
As listed below, one of the most important issues is the slow growth of the
Celix community. With the current discussion about podlings and how long a
podling is in the incubator, we are discussing a plan how we can move to a
more diverse community and be able to graduate. This plan will be included
in the next board report.
Most important issues are:
* Improve robustness (APR, error handling etc), resulting in a first release
* Generate awareness and grow a community!
--------------------
Chukwa
Chukwa is an open source data collection system for monitoring large
distributed systems. Chukwa is built on top of the Hadoop Distributed File
System (HDFS), HBase and Map/Reduce framework and inherits Hadoop's
scalability and robustness. Chukwa also includes a flexible and powerful
toolkit for displaying, monitoring and analyzing results to make the best
use of the collected data.
* Updated LICENSE and NOTICE files to comply with IPMC requests
* Updated Hadoop dependency to Hadoop 1.0.0
* Vote in progress for Chukwa 0.5.0 Release Candidate 3
When Chukwa 0.5.0 is officially released, Chukwa will complete all required
goals to graduate incubation.
--------------------
Cordova
December was a busy month. Lots of updates to the code base and our working
toolchain.
We would particularly like to thank infra for all the work getting us setup
with git. We really appreciate the effort and valuable discussion
surrounding it. It is this sort of attention to community that makes us
grateful to be members of the Apache community.
* shipped 1.3 with full windows phone support (NOTE: this was not an ASF
release; this is next for us)
* BlackBerry Playbook support
* started migration to Cordova name
* git migration complete
* battery events api
(http://docs.phonegap.com/en/1.3.0/phonegap_events_events.md.html#Events)
* first version of the project web site up
Graduation concerns:
* Complete the migration to Apache infrastructure
* Make an official Apache release
* Grant committership to new contributors
--------------------
Deft
Deft is a non-blocking, asynchronous, event driven high performance web
framework running on the JVM. The project entered incubation on 2011-07-08.
The most important issues to address in moving to graduation:
1. Prepare an initial incubation release.
2. Attract more committers, and other community members.
3. Secure the previously used URL, "deftserver.org".
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
- Not at this time.
How has the community developed since the last report?
- There have been no significant developments.
How has the project developed since the last report?
- Outstanding tasks are still being worked on.
--------------------
DeltaSpike
(incubating since December 2011)
DeltaSpike will consist of a number of portable CDI extensions that provide
useful features for Java application developers. The goal of DeltaSpike is
to create a de-facto standard of CDI-Extensions that is developed and
maintained by the community.
There are currently no issues requiring IPMC or Board attention.
Since our last report on December 12, 2011, we have accomplished the
following:
- Finished the discussion about coding conventions and added the
corresponding checkstyle rules
- Finished the discussion on the first features
- Finished infrastructure topics together with the infrastructure team (GIT
repository, nightly builds with Jenkins, Sonar setup)
(Only the JIRA plug-in for GIT is missing because there are issues with
using it side by side with the plug-in for SVN)
- Most initial committers signed their ICLA and got their account
- Started discussions on the next features
- Started with the build structure
- Started with the test-infrastructure
- Started to migrate core feature contributions from Seam3 and CODI
- Started to add information to the Wiki to help new folks getting involved
- Started discussions about tools for our documentation and website
- Started with the status page (based on
http://incubator.apache.org/guides/website.html)
Upcoming major goals:
- Finish test-infrastructure to allow in-container tests
- Finish the setup for the documentation and the website
- Finish the discussions for all features which will be part of the first
release
Top 2 or 3 things to resolve before graduation:
1. Build community
2. Create at least one release
3. Create Documentation
--------------------
DirectMemory
(incubating since October 2011)
Apache DirectMemory is a multi layered cache implementation featuring
off-heap memory management (a-la BigMemory) to enable efficient handling of
a large number of java objects without affecting jvm garbage collection
performance.
A list of the three most important issues to address in the move towards
graduation.
1) closed - Branding requirements have been met and modified logos and
artwork have been published
2) Understanding process/decision making guidelines (new committer process
is undergoing testing, release process still yet to be worked out)
Any issues that the Incubator PMC or ASF Board might wish/need to be aware
of
- None - we are going well even having lost one mentor (but always hope
he'll keep in touch ;)
How has the community developed since the last report
- Tasks and proposals contributed by non-committers
- The team is voting a new committer
How has the project developed since the last report.
- Some examples are being added to the code base including another
interesting integration with Apache Solr
--------------------
EasyAnt
Easyant is a build system based on Apache Ant and Apache Ivy. Incubating
since 2011-01-31.
Towards graduation, we need to:
* Create a release
* Build a community
Since the last report:
* no particular progress on the diversity of the community
* very little activity on the developer mailing list
--------------------
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. Empire-db has entered Incubation in August 2008.
Activity since last report:
* Last month we voted for graduation, submitted our resolution which was
revoked because of a copy-paste issue
* A fixed resolution will be submitted for this month's board meeting
--------------------
Flex
Flex is an application framework for building Flash-based applications.
Entered incubation December 30th, 2011.
The podling is just getting started, accounts and infrastructure are being
created.
--------------------
Giraph
Giraph is a large-scale, fault-tolerant, Bulk Synchronous Parallel
(BSP)-based graph processing framework that runs on Hadoop. Giraph
entered the incubator in August 2011.
Project developments:
* Sebastian Schelter, and Claudio Martella were added to the PPMC
* Review Board in frequent use and high traffic on dev and commit lists
* ICLA on file from all committers
Next steps:
* Adding new committers.
* Making a release.
--------------------
Kafka
(introduced to Apache incubator on Jul 4, 2011)
Kafka provides an extremely high throughput distributed publish/subscribe
messaging system. Additionally, it supports relatively long term persistence
of messages to support a wide variety of consumers, partitioning of the
message stream across servers and consumers, and functionality for loading
data into Apache Hadoop for offline, batch processing.
A list of the most important issues to address in the move towards
graduation
1. Invite diverse new active committers
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
We incurred significant overhead during our first release; see
http://apache.markmail.org/message/rsxjgrrufc6khlqy?q=list:org%2Eapache%2Eincubator%2Egeneral+from:%22junrao%22
for reference. Firstly, there is no good example to follow for a new podling.
Secondly, the licensing rules are complex and the documentation is not enough
for a new podling to understand. This gets more complicated since different
IPMC members have different views and apply those rules slightly differently.
This delays releases and causes overhead to the team. We hope that some of
these things can be addressed to make the process easier to other projects.
How has the community developed since the last report?
Activities in the mailing list increased 4x since the last report. Several
patches from non-committers have been submitted, reviewed and committed.
How has the project developed since the last report?
We have successfully completed the first release of Kafka after joining the
incubator. This releases adds the end-to-end compression feature and
mirroring support in Kafka. In addition to this, it also fixes more than 40
issues.
--------------------
Kitty
Incubating since 2010-10-03
Description
Kitty is a command line JMX Client written in Groovy.
It is a lightweight, production focused, application server performance
diagnostic and management utility.
The three most important issues to address in the move towards graduation:
1) The community around this project is absent, looking at the amount of
mails sent to the mailing list in the past months
2) The lack of a "Product Owner" who can prioritise stories/tasks, leaving
the developers without a clue about the functionalities to implement
3) The code is a port from another language (Jython), and the history of
the past project seems lost, so there isn't any reference about how the
actual code should work. Also, there is no test (acceptance criteria) in
support of that nor for the new features to implement.
Any issues that the Incubator PMC or ASF Board might wish/need to be aware of?
What seems relevant to me at the moment is the lack of communication between
the committers; it would be fine if there was a clear statement about who is
still interested and who is not in participating in the project, and how to
reorganise the now shrunken team, if still there is one.
How has the community developed since the last report?
Sadly, the community hasn't develop at all; even worse, we faced the loss of
some members who were actively involved in the project
development/management.
How has the project developed since the last report?
Jira is not updated, leaving a shade of uncertainty about what has been fixed
and what is still in progress since the last report. It seems that the last
update was done in October, the 4th, with a fix regarding the correct
navigation through the server tree in a file-system fashion.
--------------------
Lucy
Lucy is a loose port of the Apache Lucene search engine library, written in C
and targeted at dynamic language users.
Lucy was voted into the Incubator on July 22, 2010.
Progress since the last report:
* Added new Committers/PPMC-members Nick Wellnhofer and Logan Bell.
* Made substantial improvements in committer diversity.
* Released version 0.2.2
* Technical developments:
* Added several new classes relating to Unicode text processing.
* Improved clustering support.
* Finished eliminating Perl-licensed dependencies, resolving LEGAL-86.
* Set up per-commit build-and-test buildbot.
* Finished porting Clownfish compiler to C.
Top priorities prior to graduation:
* None. We will likely be discussing graduation as soon as version 0.3.0
is released.
Issues for Incubator PMC or ASF Board:
* None at this time.
--------------------
Mesos
Mesos is a scalable cluster manager that can dynamically share resources
between multiple computing frameworks, including Hadoop, Spark and MPI.
Mesos entered incubation on December 23, 2010.
Progress since the last report:
* Shooting for an end of January release. Hope to call a release vote by
early next week.
* Internal Twitter repo almost eliminated (all code being developed through
Apache).
* Documentation added (in anticipation of end of month release).
* Support for Mac OS X Lion almost complete (expected to be included in end
of month release).
* New autotools support almost complete (expected to be included in of end
of month release).
* Mesos provided replicated log deployed in production (and optimized).
* New web UI, including task history viewing, committed.
* Features and bug fixes contributed by 3+ new contributors.
Top priorities prior to graduation:
* Making our first release (we want to do that this month).
* Adding more committers to the project from the various developers that
have contributed to Mesos.
Issues for Incubator PMC or ASF Board:
* None at this time.
--------------------
ODFToolkit
The ODF Toolkit is a set of Java modules that allow programmatic creation,
scanning and manipulation of OpenDocument Format (ISO/IEC 26300 == ODF)
documents. Unlike other approaches which rely on runtime manipulation of
heavy-weight editors via an automation interface, the ODF Toolkit is
lightweight and ideal for server use.
* ODF Toolkit entered incubation on Aug 1st, 2011.
* Most important issues to address.
1) Successful podling release.
2) Growing the community, increasing diversity of committers
* Any issues that the Incubator PMC or ASF Board might wish/need to be aware of
None at this time.
* How has the community developed since the last report
We have a new committer: Oliver Rau.
* How has the project developed since the last report.
1) With the help of mentor, Jenkins support for the build is ready.
2) We are voting for the candidate (RC7) of the first release.
--------------------
Oozie
Oozie is a workflow management and scheduler primarily for Hadoop based
jobs.
Oozie entered the incubation on July 11, 2011.
* A list of the three most important issues to address in the move towards
graduation:
* Make the first Oozie release from Apache incubation.
* Further improve the documentations: user, development for quicker adoption
* Establish the formal release process.
* Any issues that the Incubator PMC or ASF Board might wish/need to be aware of:
* No issues.
* How has the community developed since the last report:
* Oozie dev/users are active in the email lists (1152 Email in oozie-dev
and in oozie-user 212).
* Around 7 new developers are contributing to the process and coding.
* 84 JIRAs were created since last report.
* How has the project developed since the last report.
* A lot of new features are added. Fixed a lot of bugs too. Nearly 85
JIRAs were closed/resolved in last three months.
* Oozie product web page is improved and more usable. Further
improvement is ongoing on.
* The process has started for cutting the first release from Apache.
--------------------
Tashi
Tashi has been incubating since September 2008.
The Tashi project aims to build a software infrastructure for cloud computing
on massive internet-scale datasets (what we call Big Data). The idea is to
build a cluster management system that enables the Big Data that are stored in
a cluster/data center to be accessed, shared, manipulated, and computed on by
remote users in a convenient, efficient, and safe manner.
Tashi originally encompassed just the tools to manage virtual machines
using Xen and QEMU, but has been merged with Zoni, which manages the
physical aspects of a cluster like power control, network settings and
handing out physical machines.
Development activities have included:-
* Accounting server has been added to the codebase
* Primitive scheduler changes
* bug fixes
* Add support for user choice of dense packing or not
* Guard against starting more than one VM with
persistent disk
* Client changes
* Check syntax of user commands
* Add support for querying available images
* Add support for querying image size
* Add support for copying of images
* QEMU VMM changes
* bug fixes
* Reserve some memory for the host itself
* Make scratch location configurable
* Live migrations take a long time, eliminate
some timeout values
* Cluster manager changes
* bug fixes
* Reduce network traffic
* Move accounting functions to new accounting server
* Branched off new stable version and release candidate
* Audit compliance with Incubator policies
The project is still working toward building a larger user and development
community. User groups have been identified in Ireland, Slovenia and Korea,
Malaysia, as well as the United States.
Items to be resolved before graduation:
* A stable branch exists which could be a release candidate, but
the codebase is large and test hardware is currently in
short supply. We are confident that the code in the stablefix
branch will work if running QEMU emulation, Pickle or sqlite
data storage, primitive scheduler. Xen, other data stores and
schedulers have not been tested recently.
* Develop community diversity (Committers currently at Telefonica,
Google and CMU)
-----------------------------------------
Attachment Q: 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
We are currently trying to get Apache James Protocols 1.6.0 released. After
that we will start to focus on Apache James Server 3.0. Beside this Steve
Brewin started to work on our SIEVE implementation.
COMMUNITY
There are no new Committers or PMC members. Anyway some contributor just popped
up and try to implement ACL support in IMAP.
RELEASES
We did the following releases during this period:
* Apache James Mime4J 0.7.1
* Apache James Mime4J 0.7.2
* Apache James Protocols 1.6-beta2
* Apache James Protocols 1.6-beta3
* Apache James Protocols 1.6.0-RC1
* Apache James jSPF 1.0
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 checkedin and up to date -> Not yet
-----------------------------------------
Attachment R: Status report for the Apache JMeter Project
The Apache JMeter desktop application is a Java application designed to load
test functional behavior and measure performance.
This is the third monthly board report for the JMeter TLP.
Work continues on fixing bugs and implementing new features and
generally tidying up the code.
There have been no changes to the PMC or committers since the last report.
The JMeter user list is active and user requests are generally dealt
with promptly, either by other members of the community or the JMeter
developers.
Likewise the developer list, though of course that is mainly used by
the committers.
As previously reported, it is believed that all the branding
requirements have been completed.
There are no board level issues at this time.
-----------------------------------------
Attachment S: 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 been high during the past 3 months as we have begun
the release process for 0.6. Of 181 issues targeted for this release,
there are only 4 remaining.
Code freeze, originally targeted for Jan 1, is currently being delayed
by these outstanding issues. We still expect to release 0.6 in the
near future.
A 1.0 release is not yet on the horizon.
COMMUNITY
There are no new committers since last report.
Dmitriy Lyubimov has been elected a member of the Mahout PMC.
MAHOUT DISTRIBUTIONS
Mahout has been included in the Cloudera CDH3u2 release.
(http://www.cloudera.com/blog/2011/11/cdh3u2-apache-mahout-integration)
As with other commercial distributions we will keep an eye out to
make sure it is distributed in accordance with Apache trademark
guidelines.
MAHOUT IN PRINT
"Mahout in Action", Owen, Anil, Dunning & Friedman has been published
and is being well received.
(http://manning.com/owen/)
-----------------------------------------
Attachment T: Status report for the Apache Maven Project
Maven Board Report - Jan 2012
---------------------------
* General Information
* Vote to use aether 1.13 and sisu 2.3.0 as dependencies of Apache Maven
* Progress on the Memorandum of Understanding with Sonatype continues, though
it has been slowed by the availability of John Casey and others to continue
hammering out the language. It seems that we're down to the point where
we're fine-tuning legal definitions and such in the MOU as it's written.
John hopes this effort will be completed in the next month, though it
depends on the extent to which we need to renegotiate the terms with
Sonatype after we're done pinning down the legal ramifications.
* New PMC Members
* Benson Margulies (2011-12-12)
* New Committers
* Simone Tripodi (2011-11-10)
* Releases
* Maven App Engine 1.0-alpha-1 (2011-11-01)
* Maven Script Interpreter 1.0 (2011-11-18)
* Maven Jar Signer 1.0 (2011-11-21)
* Maven Archetype 2.2 (2011-11-23)
* Maven Wagon 2.1 (2011-11-24)
* Maven Fluido Skin 1.0 (2011-11-26)
* Maven SCM 1.6 (2011-12-02)
* Maven Common Filters 1.4 (2011-12-02)
* Maven Wagon 2.2 (2011-12-20)
* Plugins
* Maven Antrun Plugin 1.7 (2011-11-01)
* Maven Shade Plugin 1.5 (2011-11-01)
* Maven Checkstyle Plugin 2.8 (2011-11-01)
* Maven Pmd Plugin 2.6 (2011-11-11)
* Maven Assembly Plugin 2.2.2 (2011-12-02)
* Maven Surefire Plugin 2.11 (2011-12-04)
* Maven Dependency Plugin 2.4 (2011-12-05)
* Maven Release Plugin 2.2.2 (2011-12-16)
-----------------------------------------
Attachment U: Status report for the Apache MINA Project
Apache MINA is a network application framework which helps users
develop high performance and high scalability network applications
easily.
Releases
--------
* No releases has been made since the last report
Community
---------
* Activity on the mailing list are at normal levels, with questions
being timely answered by both committers and community members.
* A new committer, Mike Mahoney was voted in.
* No PMC changes
Development
-----------
* Continued development on MINA 3.0.
* The SSHD, FtpServer and Vysper subprojects had another low activity quarter.
Issues
------
No board level issues at this time.
-----------------------------------------
Attachment V: Status report for the Apache MyFaces Project
Apache MyFaces is a project of the Apache Software Foundation, and hosts
several sub-projects relating to the JavaServer Faces (JSF) technology.
Community
---------
* No new Committers
* No new PMC Members
* No new Contributors
Releases
--------
MyFaces (sub) projects with new releases since the last report:
* MyFaces Core 1.2.11
* MyFaces Core 2.0.10
* MyFaces Core 2.0.11
* MyFaces Core 2.1.4
* MyFaces Core 2.1.5
* MyFaces Extensions CDI (CODI) 1.0.2
* MyFaces Extensions Validator (ExtVal) 1.2.5
* MyFaces Extensions Validator (ExtVal) 2.0.5
* MyFaces Tobago 1.0.38
* MyFaces Tobago 1.5.0-beta-2
* MyFaces Tobago 1.5.0
* MyFaces Tobago 1.5.1
* MyFaces Commons 1.0.2
* MyFaces Master POM 11
* MyFaces Builder plugin 1.0.10
* MyFaces Trinidad Maven Plugins 2.0.7
Discussions
-----------
* Changing contributor status of inactive (3+ years) community members.
(We contacted those community members on November 7, 2011. Some answered
that they are going to be active again soon, some confirmed that they
aren't active any longer and the majority didn't even answer.
We will mark them as inactive and send the result to the dev list.)
* MyFaces CODI goes TLP
(Result: Apache DeltaSpike incubation project. Furthermore,
we sent an announcement about the future of MyFaces CODI.)
Project Branding
----------------
* Started (ongoing)
-----------------------------------------
Attachment W: Status report for the Apache Nutch Project
DESCRIPTION
Apache Nutch is an open source web-search software project. Stemming from
Apache Lucene, it now builds on Apache Solr adding web-specifics, such as a
crawler, a link-graph database and parsing support handled by Apache Tika for
HTML and an array of other document formats.
ISSUES
There are no issues requiring board attention at this time.
CURRENT ACTIVITY
Nutch 1.4 has been released on 26th November 2011. A number of issues has been
filled in JIRA for 1.5. The GORA-based branch (2.0) is benefiting from the
progress made in GORA but a release is not yet planned. Recent patches have
upgraded some of our dependencies on other Apache projects such as Tika,
Hadoop or Gora.
COMMUNITY
The traffic on the user and dev mailing lists has kept a relatively high level
in the last quarter. Some of the committers met at ApacheCon NA 2011 in
November and discussed Nutch and its interaction with GORA. Finally the book
Tika in Action (one of the co-authors Chris Mattmann is a Nutch committer and
PMC member) contains quite a few references to Nutch, which should contribute
to exposing the project to a wider audience.
-----------------------------------------
Attachment X: Status report for the Apache ODE Project
Apache ODE (Orchestration Director Engine) executes business processes
written following the WS-BPEL standard. It talks to web services,
sending and receiving messages, handling data manipulation and error
recovery as described by your process definition. It supports both long
and short living process executions to orchestrate all the services that
are part of your application.
Status
======
This was again a quiet development period. We are still in the situation
that the development speed has decreased and the project lacks of dev
resources. We still have some development items on our agenda, e.g.
OModel refactoring, and are thinking of adding a BPMN 2.0
implementation, which may bring ODE back to life since all available
open source BPMN 2.0 implementations lack the Web services messaging
support that is needed for serious SOA scenarios and that is in the core
of ODE already.
Release
=======
No release to report in this quarter.
Development
===========
No significant progress to report.
Community
=========
Nothing to report.
Project Branding Board Report Checklist
=======================================
It turned out to be difficult for us to change the template of our web
site. We use the autoexport plugin for Confluence and we have been told
that Confluence admin permissions are needed in order to edit the
templates. These permissions, however, are not granted anymore. As a
"workaround" we plan to migrate to the new CMS and will address the
branding issues then as well.
- Project Website Basics : homepage is project.apache.org ✔
- Project Naming And Descriptions : use proper Apache forms, describe
product, etc. ✔
- Website Navigation Links : navbar links included, link to
www.apache.org included ✘
- Trademark Attributions : attribution for all ASF marks included in
footers, etc. ✘
- Logos and Graphics : include TM, use consistent product logo on your
site ✘
- Project Metadata : DOAP file checkedin and up to date ✔
-----------------------------------------
Attachment Y: Status report for the Apache OpenEJB Project
Apache OpenEJB is an enterprise application containers and object distribution
services based on, the Enterprise JavaBeans Specification and Java Enterprise
Edition Web Profile.
Primary activity over the last quarter has been on keeping up with bug fixes
and generally supporting the OpenEJB 4.0.0-beta-1 and TomEE 1.0.0-beta-1
release shipped in early.
The project switched to the Apache CMS just prior to ApacheCon and developed a
new website heavily featuring TomEE. The site itself is still under
development and work is still in progress on how to best communicate TomEE and
OpenEJB together. The change to the CMS has been incredibly positive and very
productive and confluence is no longer in use.
Heavy development has been done in the area of OSGi support and integration
with Apache Karaf. The effort has been an overlapping with contributions
coming from both communities.
Contributor, Vishwanath Krishnamurthi, was voted in as a committer and is also
a new face at Apache. He's contributed some great things to the
infrastructure (twitter bot), documentation and examples. We're very excited
to have him in the community and to welcome him into Apache.
Work on the OpenEJB 4.0.0-beta-2 and TomEE 1.0.0-beta-2 release has been
ongoing for the last two weeks. A second set of binaries are up for a vote
currently. Releasing frequently has been a challenge for the project and in
efforts to improve that a considerable amount of work has been done to create
tooling for automating the release tasks. Hopefully this will bring us closer
to the goal of releasing frequently which has been discussed and agreed upon
several times, but the weight of the code has thus far kept it from being a
reality.
-----------------------------------------
Attachment Z: 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
Discussion started for OpenJPA 2.2.0 release.
-----------------------------------------
Attachment AA: Status report for the Apache PDFBox Project
The Apache PDFBox library is an open source Java tool for working with PDF
documents.
General Comments
----------------
There are no issues that require Board attention.
Community
---------
There is a steady stream of contributions and bug reports from the
community.
Releases
--------
No release this quarter.
Development:
------------
The development on the next release is still in progress. We are currently
working on
- a new conforming parser
- improved font handling
- improved rendering
- refactoring + improved integration of preflight
Maybe our next release will be a major release, but it's still to early
to go for it as the discussion about it just started some time ago.
-----------------------------------------
Attachment AB: Status report for the Apache Shindig Project
Apache Shindig is an Opensocial Reference implementation in wide use by
both social networks and enterprise software. Shindig graduated from the
Incubator in January 2010.
The Shindig PMC has no issues that require board attention.
COMMUNITY
The project continues to enjoy broad contributions with an active
community and mailing list. The Apache Rave project is using
Apache Shindig and has provided patches and assistance.
We voted in four new committers and PMC members this quarter. Six
members requested emeritus status after the chair asked inactive
members about their status.
RELEASES
* 3.0.0-beta3 released October, 2011
* 3.0.0-beta4 released November, 2011
-----------------------------------------
Attachment AC: Status report for the Apache SpamAssassin Project
-----------------------------------------
Attachment AD: Status report for the Apache Struts Project
Apache Struts is an action-based Java web application framework.
The Struts team made two releases in the last quarter:
* Struts 2.3.1 - various bug fixes and improvements such as plugin support for
Contexts And Dependency Injection (CDI) and Portlet 2.0
* Struts 2.3.1.1 - security fix release
In December we announced the end of life for the Struts 2.0.x branch, which
for some time was supported in parallel to the Struts 2 trunk releases, due to
breaking API changes introduced with Struts 2.1. However, important security
fixes did not make it into the Struts 2.0.x branch lately. For that reason we
recommended our users to switch all their existing applications to the latest
Struts 2 versions.
With the latest releases we closed two important security issues reported by
JPCERT [1] and Sec Consult [2]. Dealing with both issues and their reporters
went very well both in terms of communication and disclosure as well as time
to fix.
In the last quarter we added Maurizio Cucchiara (mcucchiara) and John Lindal
(jafl) to the PMC. Christian Grobmeier (grobmeier) was added as a new
committer in this period.
We have no issues that require Board assistance at this time.
Trademarks and Project Branding (ongoing)
----------------------------------------
Trademark Attributions: ongoing
(all other topics were marked as fixed already previous reports)
[1] http://jvndb.jvn.jp/en/contents/2011/JVNDB-2011-000106.html
[2] https://www.sec-consult.com/files/20120104-0_Apache_Struts2_Multiple_Critical_Vulnerabilities.txt
-----------------------------------------
Attachment AE: Status report for the Apache Tapestry Project
Tapestry is a component-based Java web framework that combines high
performance, extensibility, conciseness, and excellent developer productivity.
It has been a busy quarter for Tapestry; we've released Tapestry 5.3, a
significant upgrade to Tapestry functionality and performance, just under a
year after the 5.2 release. We have followed up with a 5.3.1 bug fix release,
with at least one more bug fix release planned.
The Tapestry 5.3.1 vote and release was executed by Massimo Lusetti which is
notable as nearly all other recent releases where executed by Howard Lewis
Ship.
Some initial work on Tapestry 5.4 is already underway.
Mailing list activity remains steady, with approximately 1400-1500
messages/month on the mailing lists.
Widely used third party libraries (developed outside of Apache) such as
chenille-kit and Tynamo have released new versions compatible with 5.3.1.
Igor Drobiasko is continuing to work on his self-published book on Tapestry.
Ulrich Stark is investigating a conversion of the Tapestry project site from
Confluence to Apache CMS.
-----------------------------------------
Attachment AF: Status report for the Apache Tcl Project
-----------------------------------------
Attachment AG: Status report for the Apache Thrift Project
Thrift is a framework for providing cross-platform RPC and serialization.
Community
No new committers since the last report, but we've seen a steady flow of new
contributors sending in patches. The software seems to be improving at a fair
clip.
Releases
We released Thrift 0.8 and are accumulating issues into Thrift 0.9.
-----------------------------------------
Attachment AH: Status report for the Apache Tika Project
What is Tika?
=========================
Apache Tika is a dynamic
toolkit for content detection, analysis, and extraction. It allows
a user to understand, and leverage information from, a growing a
list over 1200 different file types including most of the major
types in existence (MS Office, Adobe, Text, Images, Video, Code,
and science data) as recognized by IANA and other standards bodies.
Releases
=========================
We released Tika 1.0 on 11/7/11
[1] to coincide with Apache Con NA 2011. Since then we've been
working on the 1.1 release, with 42 issues already resolved in JIRA
[2] and 1.1 likely to be shipped in the next quarter.
Community
=========================
We added Jerome Charron and
Antoni Mylkato the Tika PMC in November 2011.
At ApacheCon NA, and since, there have been some discussions regarding
Tika and the ODF Toolkit [3], as well as the Tika PMC's sponsorship
of the Any23 incubator project [4], which is progressing along.
Mailing list activity on dev@ remained steady in November and
December 2011 (259, 287 messages) but slowed in January 2012 (21
messages, respectively), while the user activity remained consistent
in November and December 2011 (47 and 65 messages), but has been
quiet in January 2012 (12 messages).
Chris Mattmann gave a talk at ApacheCon NA 2011 on "Apache Tika:
One Point Oh!" [5] commemorating the upcoming 1.0 Tika release.
Chris also had some discussions about Any23 and Tika with Lewis
John McGibbney at ApacheCon NA 2012. Lewis is a Nutch PMC member,
the candidate for the Gora VP with the current board resolution and
an Any23 Incubator committer.
Press
=========================
Chris and Jukka and Sally have
published a press release [6] about Tika's use at NASA, as well as
its use at Day Software and other companies. The press release went
out during ApacheCon NA 2011 and was perfect timing with the event.
Tika In Action
==========================
Chris Mattmann and Jukka
Zitting completed the Manning book called "Tika in Action" [7] in
time for ApacheCon NA 2011. The book is now available in print,
ebook and mobi editions. Yay!
[1] http://s.apache.org/AE6
[2] http://s.apache.org/HLX
[3] https://issues.apache.org/jira/browse/TIKA-737
[4] http://s.apache.org/gJ
[5] http://na11.apachecon.com/talks/19391
[6] http://s.apache.org/N0I
[7] http://manning.com/mattmann/
-----------------------------------------
Attachment AI: Status report for the Apache Traffic Server Project
Apache Traffic Server is an HTTP proxy server and cache, similar to Squid
and Varnish in functionality and features.
Issues
======
There are no issues that needs the boards attention.
Community
=========
No new committers were added since the last report, but several new
contributors have appeared, submitting excellent bug reports and
patches. The hope is that some of these contributors will become
committers in the future. The mailing lists are seeing our normal growth,
the current tallies are:
users@ - 243 subscribers (up 15% since last report)
dev@ - 175 subscribers (up 11% since last report)
Three presentations related to Apache Traffic Server were given in the
last quarter: two at ApacheCon 2011 (Vancouver), and one at Usenix LISA
(Boston). We're planning a Feathercast session in the near future.
Releases
========
Two releases have been made since the last status report:
3.0.2 - The second stable release update on the 3.0 branch
3.1.1 - Additional trunk development towards v3.2.
Primary focus right now includes
* Stability and bug fixes, without performance regressions
* Full IPv6
* Improvements related to SSL and addition of features such as SNI and
NPN, and public APIs related to such features.
* Continued improvements and additions to the plugin APIs.
The v3.2 release is delayed, probably close to 3 months later than we had
initially expected (and hoped for). v3.1.2 is almost ready for release,
and will be followed by at least a v3.1.3 and most likely a v3.1.4
release. The new goal is for a v3.2 release sometime in Q1 of 2012.
-----------------------------------------
Attachment AJ: Status report for the Apache Web Services Project
Web Services Report for January 2012
Releases
--------
* WSS4J 1.6.4
General
-------
* A light quarter for WS activity. JIRAs still getting filed and
fixed, not a lot of new development.
* Although much of our branding + restructuring work has been
completed, there is still more to do and it's been challenging to
get cycles from the PMC for this kind of work. Benson Margulies
kicked off a thread on the PMC list about this, and it seems to be
having the desired effect of turning up the heat under the team.
There is a concrete proposal on the table to rework and modernize
the website.
Subprojects
-----------
Current subproject descriptions follow, along with anything
specifically requiring the board's attention this quarter.
* Apache Woden
Woden is an open source Java implementation of the W3C WSDL 2.0
specification.
* Apache Axiom
Apache Axiom is a StAX-based, XML Infoset compliant object model which
supports on-demand building of the object tree.
- Project branding guidelines fully implemented.
- No release during last quarter. 1.2.13 planned for next quarter.
- Community activity: slightly increased JIRA activity over the last
quarter.
* Apache XmlSchema
Apache XmlSchema is a Java object model for manipulating and utilizing
XML Schema.
- no developer activity this quarter, although a user did raise a JIRA
that needs to be looked at.
* Apache Neethi
Apache Neethi is a Java implementation of the WS-Policy specifications.
- Two minor bugs fixed on trunk, but not yet released
* Apache TCPMon
Apache TCPMon is a Java-based network trace tool, useful for debugging
Web Service interactions.
* Apache XML-RPC
Apache XML-RPC is a Java implementation of XML-RPC, a popular protocol
that uses XML over HTTP to implement remote procedure calls.
* Apache WSS4J
Apache WSS4J is a Java implementation of the OASIS Web Services Security
(WS-Security) from OASIS Web Services Security TC.
------------------------------------------------------
End of minutes for the January 24, 2012 board meeting.
Index