Index
Links: 2017 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
March 15, 2017
1. Call to order
The meeting was scheduled for 10:30am Pacific and began at 10:32
when a sufficient attendance to constitute a quorum was
recognized by the chairman.
Other Time Zones: http://timeanddate.com/s/3773
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:
Rich Bowen
Shane Curcuru
Bertrand Delacretaz
Isabel Drost-Fromm - joined at 11:09
Marvin Humphrey
Brett Porter
Mark Thomas
Directors Absent:
Jim Jagielski
Chris Mattmann
Executive Officers Present:
Sam Ruby
Craig L Russell
Executive Officers Absent:
Ross Gardler
Ulrich Stärk
Guests:
Bob Paulin
Daniel Gruno
David Nalley
Greg Stein - joined at 10:48
Hadrian Zbarcea
Kevin A. McGrail
Par Niclas Hedhman
Sean Kelly
Sharan Foga
Tom Pappas
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of February 27, 2017
See: board_minutes_2017_02_27.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Brett]
A verbal report was given:
Significant discussion occurred around fundraising in the lead up to
the face to face referenced in the President's report.
Discussion also occurred around the implementation of brand policy
as covered in earlier months. This was distilled down to 5 points to
clarify the board's position.
Concerns were raised over whether the board held a singular vision
for the foundation, and that this at times posed difficulty in
working together. Several directors voiced a need for the board to
meet face to face early in the new term to ensure these concerns
were addressed.
I have observed times when individual directors are interpreted as
speaking for the board whenever they give feedback or raise an
issue. I've reiterated that board actions occur in the context of a
meeting.
Aside from these discussions, the focus has been on the upcoming
annual meeting. I'd like to take a moment to thank the board for
their service to the Foundation over the past year!
B. President [Sam]
Overall
=======
My current priorities remain: budget, fundraising, EA/TAC, then Brand
Management.
Budget
======
Thanks for the input last month on the FY22 budget projections. Based
on that input, I am going to presume that the board is OK with
expenditures as they are, specifically that infrastructure staffing
levels remaining where they are, for TAC to continue for the next few
years, that the choice of trademark attorney are all OK.
Please let me know ASAP if any of these assumptions are incorrect.
Otherwise, I look forward to presenting a FY18 budget in the next
board meeting that should hopefully be uncontroversial.
Fundraising
===========
We continue to be under forecast for revenues; this is now a growing
concern.
There also doesn't seem to be a common understanding of what an
appropriate "SLA" would be for responding for sponsor requests. As an
example, one sponsor provided early input into what information they
would like to see the next time their sponsorship was up for renewal,
that input was ACKed, and the plans were to comply with that request
when it was time for renewal - which is not for several months.
Apparently, this was not well communicated as a number of people were
unhappy that a response was not sent out promptly.
I'll work with Hadrian and others involved with fundraising to make
this process more transparent and predictable. The target is to make
progress on this by the meeting in Miami in May.
We have a F2F planned for the 23rd of March in Virginia; graciously
hosted by Capital One. Agenda will be to build a plan to get us to
the fundraising targets provided by the board last month, and any
remaining time left in that meeting will be devoted to process.
EA/TAC
======
EA continues to work on TAC and dealing with things that might
otherwise fall through the cracks like CSC renewal.
Last call for ApacheCon NA 2017 closed on March 8th.
Brand Management
================
Per my direction, Brand Management is continuing to defer working
with PMCs that either don't recognize or aren't following the
documented policy.
I could understand if the board felt they needed to step in and
ratify and/or give a stamp of approval if there was a history of
Brand Management destroying communities or not accepting feedback,
and if the President wasn't resolving this situation; but to preemptively
require prior approval without that history doesn't make any sense to me;
particularly coming literally one day after the board came to consensus
that the Brand Management policy is indeed ASF wide policy.
Now an additional two months have gone by. There has only been cosmetic
feedback on the policy; and a good faith effort has been made to address
this feedback. What does it take to get this to closure?
In addition to being a significant impact on morale, having policy
that only applies to some but not all PMCs is not a sane strategy.
My recommendation remains that the board reaffirm the position made two
board meetings ago, and go further: namely to clearly delegate the
setting of Brand Management policy with the understanding that (a) all
members are welcome to contribute to the development of the policy, (b)
early warning is provided to the board on all significant changes
and/or potential issues, and (c) the board reserves the right to step
in should Brand Management and the President prove to be unwilling or
unable to successfully resolve issues with PMCs on their own.
Unless the board comes to consensus on how to proceed in the next few
months, I believe that it would be better for all concerned if we were
to begin the process of shuttering Brand Management and archiving the
current policy. What would remain is the interface to counsel to handle
such matters as trademark registrations; perhaps this could be folded
into Legal Affairs?
The consequences of such an approach would be an increase in PMCs
inadequately enforcing their trademarks, the potential for third
parties to be presented with different requirements from different
PMCs, and PMCs following the lead of PMCs that chose to unfairly apply
different policies to different third parties.
What the board needs to balance is the demoralizing consequences of the
delegation of responsibility without the associated authority; the
theoretical but to date unrealized potential for an entire Brand
Management committee composed of trusted ASF members destroying a
community; and the consequences of letting each PMC decide how to
approach Brand Management.
Overall
=======
Adding in Bertrand's comment, Rich's ping this morning on fundraising,
and a recent board-private thread that I won't share specifics on; and
Chris's comment last month, there is a common theme. But first, a
story.
When Geir was treasurer, he would generally make payments within a
month of the approval. This caused much anxiety as people would often
worry about when a payment would go out. When I became treasurer,
payments would generally go out within 72 hours of approval. To my
surprise, the anxiety didn't go away. On my way out, I stated to bring
Virtual into this, and this was completed when Chris was treasurer. One
of the first changes made was that payments only went out at the end of
the month unless prior arrangements were made. For two months, there
was confusion and anxiety... and then... calm.
From time to time we have had individual Directors wade into
infrastructure, TAC, fundraising, brand management, or where-ever and
make demands. Often times they were intended as requests, but were
perceived as demands; and the next result was the same: context switches
thrashes, confusion, and reduced productivity.
Earlier this month, a single Director made a request to me, copying
board private. I indicated that I would evaluate the request and
report back in May. A number of Directors supported the original
request, and the original individual reminded me that when the board
asked me to do something, I had a duty to comply. At this point, Brett
weighed in, and stated that the board as a whole had not asked me to do
something, and while the board could operate in that way, it should not.
A number of Directors agreed with Brett on this, as do I.
And I'd like to extend that response to include Bertrand's comment; yes
the board's input was non-binding and the board can (but shouldn't!)
change its mind at any moment. My problem with emphasizing the CAN
without balancing that with SHOULDN'T is that doing so has the effect
of rendering the whole five year planning exercise as useless. Let's
not do that.
I understand based on Chris's comment that he hopes that the next board
radically changes Infrastructure's budget targets next month. Let's not
do that either.
Next week, I'm bringing together some of the best talent within the ASF
to focus on fundraising. I will insist that the plans that they come up
with will be published and that the board and membership in general will
have an opportunity to comment on those plans. I will also request
(hopefully not futilely) that the board give this fundraising team
something that it has to date denied of Brand Management - the
assumption that they can operate via lazy consensus - i.e. unless their
is a specific objection they are free to take action.
As to how I would like to see board members operate:
1) with respect to budget, I would prefer to only see major changes of
direction be proposed when we discuss five year plans, and not
out of cycle or when we review individual years budgets.
2) we have a number of Directors productively contributing as members
of various committees - this is welcome and encouraged.
3) for everything else, I would prefer that the board provide its
input during board meetings and assign and track actions to
completion.
Of course, if there is a true emergency or significant new information
that comes in between board meetings or the times that we revisit the
five year plans, I will work with the board and the relevant officers to
address the issue. But just like with Virtual and out of cycle payments;
this should be the exception rather than the norm.
Additionally, please see Attachments 1 through 7.
C. Treasurer [Ulrich]
* Not much changed due to short time between board meetings
* Worked with Virtual on preparing and filing our annual 990 for FY15 and
updated our public records
* A first look at a long-term solution to invoice filing meeting privacy
requirements showed that the preferred Bill.com cannot meet our requirements
due to missing international wiring capabilities. Further discussions are
ongoing
Virtual Update:
Here is a brief summary of the Foundation’s performance through
February 2017.
Cash at February 28th 2017 was $1,476.4K, which is down $28.8K from
last month’s ending balance (Jan 17) of $1,505.2K, due to monthly AP
and lower than expected sponsorship pmts received for Feb 2017. The
Feb 17 cash balance is down $194.1K from the Feb 2016 month end
balance of $1,67.5K. The Feb 17 ending cash of $1,476.4K represents a
cash reserve of 15 months based on the FY17 Cash forecast average
monthly spending of $99.7K/month. The "Estimated" year-end cash reserve
for the ASF, based on the Cash Forecast is 16.5 months which continues
to be very healthy for an organization of ASF's size.
Regarding the Cash P&L, the Foundation's total revenue YTD through Feb
17 was $613.2K and is behind the “UPDATED” budget by $335.1K. VP of
Fundraising is working on the $441.8K that remains in the forecast, for
the rest of FY17, which will leave us about $34K under for the year.
The good news is that we have enough open AR and the donation of $75K
arrived in Mar 2017. Currently we have $332K in open AR. Sponsorship
payment was received from ARM in Feb 17 for $40K. With regard to
sponsorship we have the 7 sponsors we anticipate remitting payment in
Mar and the 4 sponsors estimated to remit in April and we will be
following up with them.
In Feb expenses were under budget by $49.4K This was driven by under
spending in Infra ($10K in under-spending in Staffing alone), as well
as under-spending in Programs was under by $10K, Publicity was under
budget by $8.4K due primarily to underspending in Press Releases
(which we have moved forward assuming timing as the issue). Brand was
under by $6K which we have moved forward as well and Conferences was
under by $5K due to Hackathons which we have moved forward. With
regard to YTD, Infra was under bud by $3K. Prog is under by $20K as
is Publicity by $16.8K which may be timing of spending. Tac &
Conference is under by $10.7K. Brand and Treasury are right on budget
with G&A slightly under budget by $1.3K. Sponsorship is under by
$1.5K and Brand is under bud by 6.3K. This leaves us YTD $59.6K under
budget in expenses.
With regard to Net Income, for Feb 17 we were under by $204.2K, due
to $253.6K under in Revenue offset by $49.4K underspent in expenses.
From a YTD perspective we are $335K under in revenue and $59.6K under
in Expenses so net we are under budget, for Net income by $275.4K,
YTD. At this point we are estimating being $16K under bud in Net
income, due to revenue being under bud by $34 and Expenses being under
bud by $18K.
The FY 16 990 was signed and filed on 2017-03-09.
Board Summary Financials:
Current Balances:
Citizens Checking 163,053.00
Citizens Money Market 1,312,588.00
Paypal - ASF 742.00
Total Checking/Savings 1,476,383.00
Feb-17 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 1,590.43 75,000.00 -73,409.57
Sponsorship Program 40,000.00 220,667.00 -180,667.00
Programs Income 0.00 0.00 0.00
Other Income 0.00 0.00 0.00
Interest Income 473.62 0.00 473.62
Total Income 42,064.05 295,667.00 -253,602.95
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 48,709.75 67,307.00 -18,597.25
Sponsorship Program 1,250.00 2,000.00 -750.00
Programs Expense 0.00 10,000.00 -10,000.00
Publicity 6,759.04 15,137.54 -8,378.50
Brand Management 2,195.25 8,500.00 -6,304.75
Conferences 0.00 5,000.00 -5,000.00
Travel Assistance Committee 0.00 0.00 0.00
Tax and Audit 0.00 0.00 0.00
Treasury Services 3,100.00 3,100.00 0.00
General & Administrative 8,832.14 9,189.00 -356.86
Total Expense 70,846.18 120,233.54 -49,387.36
Net Income -28,782.13 175,433.46 -204,215.59
YTD 2017 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 24,322.42 88,873.67 -64,551.25
Sponsorship Program 555,795.00 827,796.00 -272,001.00
Programs Income 27,200.00 27,200.00 0.00
Other Income 825.00 825.00
Interest Income 5,010.76 3,515.00 1,495.76
Total Income 613,153.18 948,209.67 -335,056.49
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 578,183.02 581,168.00 -2,984.98
Sponsorship Program 2,250.00 3,750.00 -1,500.00
Programs Expense 0.00 20,000.00 -20,000.00
Publicity 112,813.06 129,635.64 -16,822.58
Brand Management 60,976.32 67,291.00 -6,314.68
Conferences 4,822.32 10,409.00 -5,586.68
Travel Assistance Committee 28,734.51 33,864.00 -5,129.49
Tax and Audit 6,000.00 6,000.00 0.00
Treasury Services 31,000.00 31,000.00 0.00
General & Administrative 94,746.77 96,027.00 -1,280.23
Total Expense 919,526.00 979,144.64 -59,618.64
Net Income -306,372.82 -30,934.97 -275,437.85
(Continued) Asst Treasurer [KAM]
* Short time window since last report so not too much
* Treasurer / Individual Giving Contribution Work (Hadrian, Sally & KAM) on
Hopsie Continues - Thanks to Sally for her work on the beta.
We've set Hopsie up for SPF and DKIM thanks to Infra.
* Still no word from PayPal re: charity status
* More work on Hopsie and cleaning up the individual contribution page
* PayPal re: FDIC, you can see on the summary that monies have been removed
from PayPal. This will continue monthly so as to protect these funds.
* Will be Attending F2F for Fundraising
* At F2F will be attempting to convert our existing Bitcoins to cash using
Bitstamp so another person can be physically present in case there are
hiccups or complete disasters.
* Will then sign up for Coinbase and replace any donation pages for Bitcoin
with that.
Mark: how confident are we in the receivables actually coming
in?
Kevin: don't know but will report later
Tom: one sponsor dropped out as reported; but others look good
Sam: will discuss this in detail in fundraising meeting
D. Secretary [Craig]
Secretary continues to run smoothly thanks to excellent Whimsy tooling.
In February, 94 ICLAs, one CCLA, and two grants were received and filed.
E. Executive Vice President [Ross]
No report was submitted.
F. Vice Chairman [Chris]
Nothing to report.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Mark]
No report was submitted.
B. Apache Legal Affairs Committee [Marvin Humphrey]
See Attachment 9
C. Apache Security Team Project [Mark J. Cox / Shane]
See Attachment 10
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Archiva [bp]
# Chemistry [rb]
# Commons [bp]
# Giraph [bp]
# Helix [bp]
# Lucene.Net [bp]
# Sentry [bp]
# Stanbol [bp]
# Tajo [bp]
# Wink [bp]
# Xerces [bp]
A. Apache Allura Project [Dave Brondsema / Marvin]
See Attachment A
B. Apache Any23 Project [Lewis John McGibbney / Isabel]
See Attachment B
C. Apache Archiva Project [Olivier Lamy / Bertrand]
No report was submitted.
D. Apache Aurora Project [Jake Farrell / Brett]
See Attachment D
E. Apache Axis Project [Deepal Jayasinghe / Chris]
See Attachment E
F. Apache Bahir Project [Luciano Resende / Jim]
See Attachment F
G. Apache Beam Project [Davor Bonaci / Rich]
See Attachment G
H. Apache Bigtop Project [Evans Ye / Brett]
See Attachment H
I. Apache Bloodhound Project [Gary Martin / Mark]
See Attachment I
J. Apache BVal Project [Matt Benson / Isabel]
See Attachment J
K. Apache Camel Project [Christian Mueller / Chris]
See Attachment K
L. Apache Cayenne Project [Michael Gentry / Shane]
See Attachment L
M. Apache Chemistry Project [Florian Müller / Rich]
See Attachment M
N. Apache CloudStack Project [Wido den Hollander / Bertrand]
See Attachment N
O. Apache Commons Project [Gary D. Gregory / Jim]
No report was submitted.
P. Apache Cordova Project [Shazron Abdullah / Marvin]
See Attachment P
Q. Apache cTAKES Project [Pei J Chen / Marvin]
See Attachment Q
R. Apache Curator Project [Jordan Zimmerman / Mark]
See Attachment R
S. Apache Eagle Project [Edward Zhang / Rich]
See Attachment S
T. Apache Falcon Project [Srikanth Sundarrajan / Chris]
See Attachment T
U. Apache Felix Project [Carsten Ziegeler / Jim]
See Attachment U
V. Apache Flex Project [Alex Harui / Bertrand]
See Attachment V
W. Apache Flink Project [Stephan Ewen / Isabel]
See Attachment W
X. Apache Geronimo Project [Alan Cabrera / Shane]
See Attachment X
Y. Apache Giraph Project [Avery Ching / Brett]
No report was submitted.
Z. Apache Gump Project [Stefan Bodewig / Brett]
See Attachment Z
AA. Apache Hama Project [Edward J. Yoon / Jim]
See Attachment AA
AB. Apache Helix Project [Kishore Gopalakrishna / Mark]
No report was submitted.
@Mark: pursue a report for Helix
AC. Apache Hive Project [Ashutosh Chauhan / Bertrand]
See Attachment AC
AD. Apache Incubator Project [Ted Dunning / Chris]
See Attachment AD
AE. Apache Jackrabbit Project [Michael Dürig / Isabel]
See Attachment AE
AF. Apache Karaf Project [Jean-Baptiste Onofré / Rich]
See Attachment AF
AG. Apache Labs Project [Danny Angus / Marvin]
See Attachment AG
AH. Apache Lucene Project [Tommaso Teofili / Shane]
See Attachment AH
AI. Apache Lucene.Net Project [Prescott Nasser / Jim]
No report was submitted.
@Jim: pursue a report for Lucene.Net
AJ. Apache OFBiz Project [Jacopo Cappellato / Bertrand]
See Attachment AJ
AK. Apache Olingo Project [Christian Amend / Isabel]
See Attachment AK
AL. Apache OODT Project [Tom Barber / Chris]
See Attachment AL
AM. Apache OpenNLP Project [Jörn Kottmann / Brett]
See Attachment AM
AN. Apache OpenWebBeans Project [Mark Struberg / Marvin]
See Attachment AN
AO. Apache Pig Project [Daniel Dai / Shane]
See Attachment AO
AP. Apache Pivot Project [Roger Whitcomb / Rich]
See Attachment AP
AQ. Apache Polygene Project [Niclas Hedhman / Mark]
See Attachment AQ
AR. Apache Portable Runtime (APR) Project [Nick Kew / Bertrand]
See Attachment AR
AS. Apache Portals Project [David Sean Taylor / Isabel]
See Attachment AS
AT. Apache Ranger Project [Selvamohan Neethiraj / Chris]
See Attachment AT
AU. Apache Sentry Project [Sravya Tirukkovalur / Shane]
No report was submitted.
@Shane: pursue a report for Sentry
AV. Apache ServiceMix Project [Krzysztof Sobkowiak / Mark]
See Attachment AV
AW. Apache Shiro Project [Les Hazlewood / Brett]
See Attachment AW
AX. Apache Sling Project [Carsten Ziegeler / Marvin]
See Attachment AX
AY. Apache SpamAssassin Project [Sidney Markowitz / Rich]
See Attachment AY
AZ. Apache Stanbol Project [Fabian Christ / Jim]
No report was submitted.
BA. Apache Storm Project [P. Taylor Goetz / Chris]
See Attachment BA
BB. Apache Synapse Project [Isuru Udana / Rich]
See Attachment BB
BC. Apache Tajo Project [Hyunsik Choi / Bertrand]
No report was submitted.
@Bertrand: pursue a report for Tajo
BD. Apache Tiles Project [Mick Semb Wever / Jim]
See Attachment BD
BE. Apache Tomcat Project [Mladen Turk / Isabel]
See Attachment BE
BF. Apache Twill Project [Terence Yim / Shane]
See Attachment BF
BG. Apache UIMA Project [Marshall Schor / Mark]
See Attachment BG
BH. Apache VCL Project [Andy Kurth / Marvin]
See Attachment BH
BI. Apache Wicket Project [Martijn Dashorst / Brett]
See Attachment BI
BJ. Apache Wink Project [Luciano Resende / Marvin]
No report was submitted.
@Marvin: pursue a report for Wink
BK. Apache Xerces Project [Michael Glavassevich / Mark]
No report was submitted.
@Mark: pursue a report for Xerces; looks like they are heading
for retirement
BL. Apache Yetus Project [Sean Busbey / Chris]
See Attachment BL
BM. Apache ZooKeeper Project [Flavio Junqueira / Jim]
See Attachment BM
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Accumulo Project Chair
WHEREAS, the Board of Directors heretofore appointed Billie
Rinaldi (billie) to the office of Vice President, Apache
Accumulo, and
WHEREAS, the Board of Directors is in receipt of the resignation
of Billie Rinaldi from the office of Vice President, Apache
Accumulo, and
WHEREAS, the Project Management Committee of the Apache Accumulo
project has chosen by vote to recommend Michael Wall (mjwall) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Billie Rinaldi is relieved
and discharged from the duties and responsibilities of the
office of Vice President, Apache Accumulo, and
BE IT FURTHER RESOLVED, that Michael Wall be and hereby is
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.
Special Order 7A, Change the Apache Accumulo Project Chair,
was approved by Unanimous Vote of the directors present.
B. Clarify Brand Management policy
WHEREAS recent discussions show a need to clarify how our Brand
Management policy is set.
NOW, THEREFORE, BE IT RESOLVED that the following five rules apply to
our Brand Management policy from now on and until changed by a new
Board Resolution:
1. Setting of brand policy is delegated to V.P. Brand.
2. All PMCs are required to follow brand policy.
3. Exceptions to brand policy are permitted and should be agreed
between the PMC and V.P. Brand.
4. All exceptions, including those already agreed, must be documented
in a single central location.
5. The escalation path for any issues (changes to policy, agreement of
exceptions etc.) is first the President, then the board.
Special Order 7B, Clarify Brand Management policy, was tabled.
@Brett: resolve this on the board mail list prior to the Members'
meeting
8. Discussion Items
9. Review Outstanding Action Items
* Bertrand: Work with PMC to get a more complete report
[ Felix 2016-12-21 ]
Status: done, relayed the board's comments to the Felix PMC
* Jim: Mentor comments are extremely important; please try to include them.
[ Incubator 2016-12-21 ]
Status:
* Jim: Many projects have been incubating for years. Please address this.
[ Incubator 2016-12-21 ]
Status:
* Isabel: Work with PMC to see if they plan to change their remit
[ Labs 2016-12-21 ]
Status: PMC chair has limited time, but sees potential in the project.
Work for more outreach within the ASF has started.
* Alan: will report next month
[ Geronimo 2017-01-18 ]
Status: closed
* Jim: consolidate and take board's concerns to IPMC.
[ Incubator 2017-01-18 ]
Status:
* Jim: pursue a report for Mesos
[ Mesos 2017-01-18 ]
Status:
* Marvin: try to get a better report that reflects activity
[ Tajo 2017-01-18 ]
Status:
* Brett: pursue resolution of Brand Management Policy issue
[ President 2017-02-27 ]
Status:
* Rich: bring comments regarding transparency to PMC and ask them to resubmit
[ BookKeeper 2017-02-27 ]
Status: BookKeeper PMC confirms that meeting notes are being posted to
https://cwiki.apache.org/confluence/display/BOOKKEEPER/Community+Meetings
and that this link is also sent to the dev mailing list after
meetings. So we're all good here. Status: RESOLVED to my
satisfaction
* Shane: please explain the comment regarding external org
[ Cassandra 2017-02-27 ]
Status:
* Chris: follow up on reported meeting between external parties not brought
back
[ Eagle 2017-02-27 ]
Status: have not explicitly followed this up. Will look to hand off to
next Board member, or pick up as Board member next month.
* Mark: pursue a report for Giraph
[ Giraph 2017-02-27 ]
Status: Ongoing. Report chased 2017-03-11
* Bertrand: pursue a report for Hama
[ Hama 2017-02-27 ]
Status: reminder sent
* Shane: follow up on brand action item
[ Spark 2017-02-27 ]
Status:
* Jim: follow up with PMC to ensure that there are three active PMC members to
[ Buildr 2017-02-27 ]
Status:
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 11:33 a.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the Executive Assistant [Melissa Warnkin]
Monitoring of all email and following up with appropriate personnel when
needed.
Gearing up for ACNA’17. Collaborating with Sally and Sharan Foga on swag and
booth logistics, etc.
-----------------------------------------
Attachment 2: Report from the VP of Brand Management [Shane Curcuru]
* ISSUES FOR THE BOARD
Please see last month's Brand report and this month's President report.
* OPERATIONS
Short and fairly quiet month.
Lacking any significant actionable feedback, I plan to clarify and ratify the
following two policies:
- Services naming policy: https://www.apache.org/foundation/marks/services
- Merchandise use policy: https://www.apache.org/foundation/marks/merchandise
(public) https://svn.apache.org/repos/private/committers/brand/merchandise.txt
(committer-only additional permissions)
A proposal to encourage (rather than prohibit) "Apache" in third party event
branding has been brought up. As with the draft proposals above,
disappointingly little (none, so far on events) feedback has appeared.
Similarly, a call to members@ soliciting questions about Apache brands met
with resounding silence. Will try one more time - hoping the activity around
the member's meeting helps.
* REGISTRATIONS & CONTRACTS
Still working through some complex feedback from counsel on potential issues
with registration applications. Balancing the needs and requests of various
PMCs with limited in-house expertise and budget for counsel continues to take
effort.
A proposal for a new method of tax-deductible fundraising by licensing brands
was forwarded to fundraising@; the process is likely to take a while to come
to fruition (or to be decided against, perhaps).
-----------------------------------------
Attachment 3: Report from the VP of Fundraising [Hadrian Zbarcea]
Fundraising activities continue normally.
Renewal invoices are sent by Lynsey on time. Besides the issue with the SLA
mentioned in the President report we have an issue with our two contact people
leaving a sponsoring company. I got a call with somebody else in the
organization and hope to be put in contact with the new person in charge.
A small group of members is currently testing a new donation channel. Thanks
Sally for taking the lead on that.
I am looking forward to the F2F meeting regarding fundraising. Thanks to
Capital One for providing the venue.
-----------------------------------------
Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi]
I. Budget: Sally Khudairi is preparing the FY2018 budget. No vendor
payments are due at this time.
II. Cross-committee Liaison: Sally continues work with Fundraising,
Brand Management, Apache Incubator, Conferences/ApacheCon, and ComDev.
She published the fourth "Success at Apache" post
https://s.apache.org/yFgQ , and has secured authors for the next five
editions. The ASF’s Q3 Operations Summary for FY2017 is in its final
edit and will be published soon. She has been actively working on the
new individual giving fundraising system and is hoping to launch in
time for the ASF’s 18th Anniversary at the end of the month. The
Apache Incubator call for a new logo is at the finishing stages, and
the winner will be announced the week of 13 March.
III. Press Releases: the following formal announcement was issued via
the newswire service, ASF Foundation Blog, and announce@apache.org
during this timeframe:
- 14 February 2017 --The Apache Software Foundation Announces Apache®
MyFaces™ Tobago 3
IV. Informal Announcements: 6 items were published on the ASF
"Foundation" Blog. 4 Apache News Round-ups were issued, with a total
of 138 weekly summaries published to date. 85 items were Tweeted on
@TheASF, which has now grown to more than 40.6K followers. Nearly four
months have passed since ApacheCon Europe, and Rich Bowen and the team
of ComDev volunteers are nearing completion of uploading audio the
conference recordings onto Feathercast. Sally is closing in on
securing professional editing services to reduce production time for
future events. No new videos have been added to the ASF YouTube
channel. Sally continues to tweet for the Apache Incubator, and has
posted 18 items on LinkedIn, which have garnered more than 130.2K
collective organic impressions.
V. Future Announcements: one announcement is in development. Projects
planning to graduate from the Apache Incubator as well as PMCs wishing
to announce major project milestones and "Did You Know?" success
stories are requested to contact Sally at <press@apache.org> with at
least 2-weeks' notice for proper planning and execution.
VI. Media Relations: we responded to 11 media queries, including two
conference speaker requests and press release reviews/signoffs by a
few companies invested in Apache projects. Additionally, Sally has
been requested to review/copyedit some articles from a couple of
projects and committers. The ASF received 1,404 press clips vs. last
month's clip count of 1,214. Media coverage of Apache projects yielded
4,687 press hits vs. last month's 3,949. ApacheCon received 21 press
hits, which we anticipate will increase with two press releases
announcing the conference program.
VII. Analyst Relations: we received 3 analyst queries during this
timeframe. Apache was mentioned in 23 reports by Gartner, 8 reports by
Forrester, 9 reports by 451 Research, and 8 reports by IDC.
VIII. Graphics: work on the ASF Identity Style Guide
(graphics/visual/branding) continues with Fran Lukesh (one of the
designers who created the new ASF logo).
IX. ApacheCon liaison: Sally is exploring possible underwriters for a
future event in Europe. She has also been working alongside Rich Bowen
and the Linux Foundation on marketing the upcoming ApacheCon in Miami,
and has developed a new sponsorship opportunity, namely the Apache
Community Sponsor
http://events.linuxfoundation.org/events/apachecon-north-america/sponsors/community-sponsor.
In addition, she is working with Melissa Warnkin, Sharan Foga, and Daniel Gruno
on promotional materials for ApacheCon, as well as creating new banners and a
3D version of the new Apache feather to replace the original, heritage feather
https://www.cloudsigma.com/wp-content/uploads/apache_feather.jpg
X. (Non-ASF) Industry Events and Outreach liaison: Sally has been
reviewing several conference opportunities and is discussing with Rich
Bowen the best ways to address them.
XI. Newswire accounts: we have 22 pre-paid press releases remaining
with NASDAQ GlobeNewswire through December 2017.
# # #
-----------------------------------------
Attachment 5: Report from the VP of Infrastructure [David Nalley]
Highlights
==========
No Board or Executive action is requested at this time. Infrasturcture
is operating normally, without issue.
Finances
========
The Infrastructure team is working within the FY17 budget set by the
Board in December 2016. Planning for Fiscal Year 2018 has begun, based
on the five-year budget outlook prepared earlier.
General Activity
================
The Infra team has begun booking travel and hotel for ApacheCon in
Miami, in May. We will be using the conference for team education, for
interaction with the community and volunteers, and for team building
and face-to-face meetings.
GitHub as Master ("Gitbox")
===========================
Our work on enabling GitHub as the primary focal point for development
continues. As we add new projects, we've found/added several improvements
to our recording of provenance.
Cost-per-Project Reduction
==========================
Our work on reducing our per-project costs continues to be a second
priority, relative to our primary work of VM/machine migrations and
ramping-up of gitbox.
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Rich Bowen]
The schedule for ApacheCon North America has been published. We have
two primary events - ApacheCon and Apache Big Data - with schedules
published at
http://events.linuxfoundation.org/events/apachecon-north-america/program/schedule
and
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/schedule
respectively.
ApacheCon is further divided into mini-conferences, for the purpose of
being able to do very targeted promotion of these events to specific
audiences. To that end, we have:
Apache Traffic Server and Apache Traffic Control Summit -
http://events.linuxfoundation.org/events/apachecon-north-america/extend-the-experience/ats-summit
BarCampApache - http://events.linuxfoundation.org/events/apachecon-north-america/extend-the-experience/barcamp
ApacheIoT - http://us.apacheiot.org/
CloudStack Collaboration Conference - http://us.cloudstackcollab.org/
FlexJS Summit - http://us.apacheflexjs.org/
TomCatCon - https://tomcat.apache.org/conference.html
We are depending on each of these communities to help us in promoting
these events, and driving attendance.
We announced a new type of sponsorship, where a community can band
together to put several smaller sponsorships together to create one
combined Community Sponsor. The details of this program are published
on the conference website at
http://events.linuxfoundation.org/events/apachecon-north-america/sponsors/community-sponsor
and we already have a few communities looking at how they might
participate in this program. We consider this critical to building
ownership of the event in our communities, even if it doesn't bring in
an enormous amount of money.
ApacheCon and Apache Big Data will be held in Miami, Tuesday May 16th
through Thursday May 18th. BarCampApache will be held on Monday, May
15th. The Apache Traffic Server Summit will be held on Sunday May 14th
and Monday May 15th. These events will, all be held at the Miami
InterContinental Hotel.
-----------------------------------------
Attachment 7: Report from the Apache Travel Assistance Committee [Melissa Warnkin]
Applications closed on schedule with 22 applications and the judges
call was held Sunday, March 12th.
Our statistics tracking spreadsheet shows that included 6 speakers, 4
students, 13 committers, and 1 woman.
After scoring all applications, and discussing them, there are 12
applicants we'd like to bring along to Miami. That'd be 11 people
above the typical 30 score cut-off, plus 1 person only just under it.
If we brought all 12, then including OTG costs, we estimate the bill
would be around 28k. (25k plus likely contingency). This would put us
under budget, which Tom has confirmed is $32k for the rest of FY17.
12 people would a tiny bit lower than Vancouver or Seville, but about
at our long-term average. The judges didn't feel lower scoring
applicants should be brought, and there was no desire amongst judges
to lower the cut-off bar this time beyond the one "just under" score
applicant.
-----------------------------------------
Attachment 8: Report from the VP of W3C Relations [Andy Seaborne]
-----------------------------------------
Attachment 9: Report from the Apache Legal Affairs Committee [Marvin Humphrey]
After considerable debate, the ACE license has been added to "Category
A". It is a BSD-style license with extra verbiage describing the ACE
project's history; no concerns have been voiced that the extra verbiage
materially changes the meaning of the license.
An earlier recommendation resolving a complex licensing issue with the
Incubator podling MADlib was reaffirmed.
-----------------------------------------
Attachment 10: Report from the Apache Security Team Project [Mark J. Cox]
Stats for Feb 2017:
8 CVEs issued to projects (some may not be public yet).
e-mails to security@
2 Phishing/spam/proxy/attacks point to site "powered by Apache" or
Confused user due to "Apache" mentioned in OSS licenses
2 Support question
10 Direct Vulnerability report to security@apache.org
3 [site] (3 rejected)
1 [httpd]
1 [hbase] (rejected)
1 [ranger]
1 [flex]
1 [struts]
1 [camel]
1 [karaf]
9 Vulnerabilities reported to projects
1 [ambari]
1 [httpd] (rejected, was PHP)
1 [zookeeper]
2 [tomcat]
1 [brooklyn]
1 [apex]
1 [struts]
1 [ofbiz]
-----------------------------------------
Attachment A: Report from the Apache Allura Project [Dave Brondsema]
## Description:
Apache Allura is an open source implementation of a software forge, a web site
that manages source code repositories, bug reports, discussions, wiki pages,
blogs, and more for any number of individual projects.
## Issues:
- No issues needing board attention.
## Activity:
- Development has been quieter this past quarter, but still moving along
(security fix, small features added, some fixes, etc)
- Kenton Taylor added to PMC
- A few users with questions, and some potential GSOC students starting to get
involved already
## Health report:
As mentioned, development is a bit slower, main contributors have been working
on other projects, but that's not expected to be permanent. Still good health
in terms of adding a PMC member and seeing GSOC activity already.
## PMC changes:
- Currently 14 PMC members.
- Kenton Taylor was added to the PMC on Sun Jan 22 2017
## Committer base changes:
- Currently 14 committers.
- Kenton Taylor was added as a committer on Thu Jan 19 2017
## Releases:
- 1.6.0 was released on Tue Dec 13 2016
-----------------------------------------
Attachment B: Report from the Apache Any23 Project [Lewis John McGibbney]
## Description:
Anything To Triples (Any23) is a library, a web service and a
command line tool that extracts structured data in RDF format from a variety
of Web documents.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity has been good. Any23 has seen quite a bit of activity recently with
new community members VOTE'ing on the very recent 2.0 release.
## Health report:
Existing commitership and PMC is pretty quiet however there is certainly a
healthy interested in the Any23 project. The 2.0 release was announced
extensively through relevant project communication channels e.g. W3C,
DBPedia, WebDataCommons, etc.
## PMC changes:
- Currently 14 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was William L. Anderson on Sun Aug 28 2016
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Bill Anderson at Tue Aug 30 2016
## Releases:
- 2.0 was released on Thu Feb 16 2017
## Mailing list activity:
Due to a slight increase in development prior to the 2.0 release, dev@ has
been busy. user@ remains pretty quiet with mostly announcements threads.
- dev@any23.apache.org:
- 35 subscribers (up 0 in the last 3 months):
- 178 emails sent to list (47 in previous quarter)
- user@any23.apache.org:
- 51 subscribers (up 0 in the last 3 months):
- 14 emails sent to list (2 in previous quarter)
## JIRA activity:
- 6 JIRA tickets created in the last 3 months
- 17 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment C: Report from the Apache Archiva Project [Olivier Lamy]
-----------------------------------------
Attachment D: Report from the Apache Aurora Project [Jake Farrell]
Apache Aurora is a stateless and fault tolerant service scheduler used to
schedule jobs onto Apache Mesos such as long-running services, cron jobs,
and one off tasks.
Project Status
---------
The Apache Aurora community has continued to see growth from new
contributors over the last quarter while working on our latest 0.17.0 release,
which was successfully released on February 6th. There has been a great
deal of open discussions on the mailing lists surrounding dynamic
reservations, rolling restarts and recently the idea of leveraging Apache
Aurora to start Apache Mesos Maintenance. The Apache
Aurora PMC also added a new committer, Santhosh Shanmugham, as
well as added a new PMC member Mehrdad Nurolahzade.
Community
---
Latest Additions:
* Committer addition: Santhosh Kumar Shanmugham, 2.9.2017
* PMC addition: Mehrdad Nurolahzade, 2.24.2017
Issue backlog status since last report:
* Created: 50
* Resolved: 51
Mailing list activity since last report:
* @dev 124 messages
* @user 24 messages
* @reviews 1292 messages
Releases
---
Last release: Apache Aurora 0.17.0 released 02.06.2017
-----------------------------------------
Attachment E: Report from the Apache Axis Project [Deepal Jayasinghe]
## Description
The Apache Axis project is responsible for the creation and maintenance of
software related to the Axis Web Services frameworks and subsidiary
components (both Java and C).
## Issues:
- Axis2/C and its sub-projects are inactive and we need to consider moving
that to Attic as well. We will move them to Attic before next board
meeting.
- We need to find a volunteer for PMC chair (with current workload I have
limited time to work on the project).
## PMC/Committer changes:
- Currently 62 PMC/Commiters members.
- No new committers were added in last three month (last addition was in
June 2016.).
## Releases:
- No new releases in last three months. Last Axis2 release was on October,
21 2016 (Axis2 Java 1.7.4).
-----------------------------------------
Attachment F: Report from the Apache Bahir Project [Luciano Resende]
Apache Bahir provides extensions to distributed analytic platforms such as
Apache Spark and Apache Flink. Currently Bahir provides extensions to
multiple distributed analytic platforms, extending their reach with a
diversity of streaming connectors and SQL data sources.
Community Activity:
Apache Bahir community has been actively working on supporting and enhancing
previously available Apache Spark extensions and also creating new ones such
as the new structured streaming extension for MQTT. The community is also
actively keeping up with the Apache Spark release cadence, aiming to provide
compatible releases with the minimum time interval.
Apache Bahir has also integrated various extensions for Apache Flink
analytical platform. Currently, the following extensions are available in
Apache Bahir : ActiveMQ, Akka, Flume, Netty, and Redis connectors.
Also, based on some internal discussions/feedback, the Apache Bahir PMC has
sent an e-mail to all the Spark Committers that were listed in the original
Apache Bahir proposal given them the Ability to reply with any concerns that
they might have. The PMC will report if it hears anything but after a few
days, we have not received any feedback.
Last, but not least, there were couple feedbacks around the project mission,
and we will be discussing the matter and providing a more community driven
feedback on the next report.
Issues:
* No known issues
Releases:
03/05/2017 - Bahir 2.1.0
01/28/2017 - Bahir 2.0.2
10/28/2016 - Bahir 2.0.1
Committers or PMC changes:
03/13/2017 - Christian Kadner becomes Apache Bahir PMC
11/30/2016 - Christian Kadner voted as Apache Bahir committer
10/18/2016 - Robert Metzger voted as Apache Bahir committer
Trademark/Branding:
* No known issues.
Legal Issues:
* None
-----------------------------------------
Attachment G: Report from the Apache Beam Project [Davor Bonaci]
## Description:
Apache Beam is a unified programming model for both batch and streaming data
processing, enabling efficient execution across diverse distributed execution
engines and providing extensibility points for connecting to different
technologies and user communities.
## Issues:
There are no issues that require the Board's attention at this time.
## Activity:
Apache Beam was established as a top-level project at December’s Board
meeting. This is the third in the series of three consecutive monthly reports
for new projects.
Since last month's report, we have started work on the next release, version
0.6.0. This will be the first release with the new Python SDK, a highly
anticipated component that opens up a new user community. Pipelines built with
Python SDK currently run on a limited number of runners, but work is ongoing
to extend runner support.
Beam continues to interconnect additional execution engines and data
storage/messaging systems. Since the last report, IO connector for Apache
HBase has been contributed, and additional connectors for Redis, Apache
Cassandra, Apache DistributedLog, Apache Parquet, Apache Solr, RabbitMQ, and
Advanced Message Queuing Protocol (AMQP) are in progress. The work has resumed
on the Apache Gearpump (incubating) runner.
Going forward, the main focus continues to be on the community growth,
particularly users. Beam will be covered at 6 major conferences over the next
2 months, including 2 talks and a tutorial at the upcoming Apache: Big Data
North America 2017 conference.
On the technical side, the next major milestone is the availability of the
first stable release, which will include backward-compatibility guarantees.
This stabilization effort has started recently.
## Health report:
The community continues to grow steadily, as follows:
- The number of contributors continues to increase.
- Releases continue at a regular pace of 1-1.5 months per release.
- Mailing list activity continues to increase significantly.
## PMC changes:
Currently 14 PMC members. No new PMC members have been added since graduation
three months ago.
## Committer base changes:
Currently 20 committers. Three new committers have been added since
graduation:
- Ahmet Altay was added as a committer on Tue Jan 31 2017.
- Pei He was added as a committer on Tue Jan 31 2017.
- Stas Levin was added as a committer on Tue Jan 31 2017.
## Releases:
In the two months following graduation, Apache Beam has published two
releases:
- 0.4.0 was released on Sun Jan 01 2017.
- 0.5.0 was released on Mon Feb 06 2017.
In addition, the 0.6.0 release is in progress.
## Mailing list activity:
Mailing list activity continues to increase across all metrics.
- dev@beam.apache.org
- 351 subscribers (up 60 in the last 3 months)
- 1161 emails sent to list (866 in previous quarter)
- user@beam.apache.org
- 298 subscribers (up 58 in the last 3 months)
- 282 emails sent to list (241 in previous quarter)
## JIRA activity:
- 542 JIRA tickets created in the last 3 months
- 347 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment H: Report from the Apache Bigtop Project [Evans Ye]
## Description:
Apache Bigtop is a software related to a system for integration, packaging,
deployment and validation of a big data management software distribution based
on Apache Hadoop.
## Issues:
None
## Activity:
The community is still working on 1.2 release with visible progress. There has
been no schedule for the release yet. [1]
A task to merge ODPi contributions back to Bigtop is in progress. [2]
There have been a couple of talks around Apache Bigtop at FOSDEM 2017: Roman
Shaposhnik:
- Postgres MPP Data Warehousing joins Hadoop ecosystem Making two elephants
dance Olaf Flebbe
- Quickstart Big Data Roman also co-moderated a devroom "HPC, Big Data and
Data Science".
## PMC changes:
Last PMC addition was Nate D'Amico on Fri Jan 22 2016
## Committer base changes:
Last committer addition was Jonathan Kelly on Thu Dec 08 2016
## Releases:
Last release was 1.1.0 on Sat Jan 30 2016
## Links
1. https://issues.apache.org/jira/browse/BIGTOP-2282
2. https://issues.apache.org/jira/browse/BIGTOP-2666
-----------------------------------------
Attachment I: Report from the Apache Bloodhound Project [Gary Martin]
Project Description
===================
Apache Bloodhound is a software development collaboration tool, including
issue tracking, wiki and repository browsing
Issues
======
The threat of moving the project to the attic is ongoing with further
concerns expressed on the long term viability of the project.
Releases
========
There have been no releases over the last three months. The last release
was towards the end of 2014:
* apache-bloodhound-0.8 (11th December 2014)
PMC/Committer Changes
=====================
There are currently 15 PMC members on the project. The last changes were
in December 2016.
The last new committers were added in May 2014.
Community & Development
=======================
The addition of Dammina Sahabandu to the PMC has had a positive effect on
the development activity and, together with Ryan Ollos, there is evidence
of work going into the project.
In particular, over the last few months there has been an ongoing effort
to clean up work from previous GSoC projects for merging into the main
project. One of these, a wiki macro to manage multiple tickets creations
within the wiki view, has been completed and merged.
There is currently an expectation for further new feature branches to be
examined and brought into the project over the next few months.
The project is also looking into the possibility of involvement with GSoC
for 2017 with projects being proposed. This has led to interest from some
prospective students to get involved with the project. If this comes to
fruition it could have further benefits for the Bloodhound project if it
is possible to translate such interest to new PMC members.
Activity on the user list remains negligible.
-----------------------------------------
Attachment J: Report from the Apache BVal Project [Matt Benson]
## Apache BVal Report March 2017 ##
- The Apache BVal project implements the Java EE Bean Validation
specification(s) and related extensions, and became a top-level project
of the foundation on February 15, 2012.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- None to speak of this quarter, which is normal for BVal: occasionally
there is a frenzy of activity to effect a release, but these are
punctuated by relative silence. As mentioned in previous reports, the
specification process for Java Bean Validation 2.0 proceeds and seems to
be nearing completion. There will be a resumption of activity in this
project in response to that.
## Health report:
- The project staff remains busy elsewhere, for the most part. BVal is
curated on a obligation basis more than anything else at this point. It
is perhaps not the ideal scenario for project health, but it remains
tenable.
## PMC changes:
- Currently 14 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Romain Manni-Bucau on Mon Nov 18 2013
## Committer base changes:
- Currently 14 committers.
- No new changes to the committer base since last report.
- Last committer addition was Romain Manni-Bucau on Sun Jun 23 2013
## Releases:
- Last release was 1.1.2 on Wed Nov 02 2016
## Mailing list activity:
- The following statistics reflect the ebb in activity subsequent to the
previous release.
- dev@bval.apache.org:
- 44 subscribers (up 1 in the last 3 months):
- 7 emails sent to list (75 in previous quarter)
- user@bval.apache.org:
- 53 subscribers (up 2 in the last 3 months):
- 4 emails sent to list (3 in previous quarter)
## JIRA activity:
- N/A
-----------------------------------------
Attachment K: Report from the Apache Camel Project [Christian Mueller]
## Description:
- Apache Camel is a powerful open source integration framework based on known
Enterprise Integration Patterns.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- We are receiving many contributions from our contributors (via GitHub pull
requests). We have more than 1500 closed pull requests where 98% is from
community contributors.
- A new releases is coming out soon: Camel 2.18.3
- We are focusing the development of the next minor release Apache Camel
2.19.0 expected to be released in April.
- Some people started to work on some bigger changes for the next major
release Apache Camel 3.0.0.
- We have started to deprecate APIs and components that will be dropped for
Camel 3.0
- We are running a new logo proposal that has a deadline at the end of March.
We have receive about 6 different logo proposals. After the deadline we will
have a vote about the logo which the PMC then ultimate decides whether to
carry on with the logo change
## Health report:
- The project is super healthy, active and stays at a high level
- At ApacheCon Europe 2016, we had 5 presentations about Apache Camel from
PMC's, committers and contributers/users.
## PMC changes:
- Currently 29 PMC members.
- Luca Burgazzoli was added to the PMC on Thu Oct 06 2016
## Committer base changes:
- Currently 54 committers.
- Last committer addition was Zoran Regvart at Feb 18 2017
## Releases:
- 2.17.5 was released on Jan 22 2017
- 2.17.6 was released on March 8 2017
- 2.18.2 was released on Jan 30 2017
## Mailing list activity:
- Mailing list activity stays at a high level.
-----------------------------------------
Attachment L: Report from the Apache Cayenne Project [Michael Gentry]
## Description:
Apache Cayenne is a Java database persistence framework. It takes a
distinct approach to object persistence and provides an ORM runtime,
remote persistence services, and a GUI mapping/modeling tool.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Cayenne 3.1 (stable)
- Maintenance only.
- Cayenne 4.0 (development)
- This is where all current development effort is taking place.
We just released a new milestone, which we hope to be our final
milestone release before going into beta.
## Health report:
Cayenne is still under active development and has a stable user and
developer community.
## PMC changes:
- Currently 8 PMC members.
- No new PMC members added in the last 3 months.
- Last PMC addition was Savva Kolbachev on Tue Apr 12 2016.
## Committer base changes:
- Currently 21 committers.
- Nikita Timofeev was added as a committer on Fri Dec 23 2016
## Releases:
- Cayenne 4.0.M5 was announced on Mon Mar 6 2017.
## Mailing list activity:
- dev@cayenne.apache.org:
- 128 subscribers (up 0 in the last 3 months)
- 168 emails sent to list (81 in previous quarter)
- user@cayenne.apache.org:
- 250 subscribers (up 1 in the last 3 months)
- 208 emails sent to list (96 in previous quarter)
The increase in mailing list traffic is due to an increase in developer
activity on the Cayenne milestones and from answering questions to those
trying out the new milestone features or trying to perform more advanced
operations using Cayenne.
## JIRA activity:
- 96 JIRA tickets created in the last 3 months
- 82 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment M: Report from the Apache Chemistry Project [Florian Müller]
## Description:
Apache Chemistry is an effort to provide an implementation of the CMIS
(Content Management Interoperability Services) specification in Java,
Python, PHP, .NET, Objective-C, and JavaScript (and possibly other
languages).
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- OpenCMIS (Java), PortCMIS (C#), and cmislib (Python) received bug fixes
and smaller enhancements.
- There is no schedule for new releases yet, but we have to target them
for the next few months.
## Health report:
- The CMIS standard hasn't changed and the libraries are mature now.
There is no major code development expected.
## PMC changes:
- Currently 35 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ben Chevallereau on Thu Dec 11 2014
- There is only a small core of active PMC members left.
## Committer base changes:
- Currently 37 committers.
- No new committers added in the last 3 months
- Last committer addition was Sanija Shabani at Wed Nov 26 2014
- Because of the low activity, we don't except a growth of the community.
## Releases:
- Last release was OpenCMIS 1.0.0 on Thu Sep 08 2016
## Mailing list activity:
- dev@chemistry.apache.org:
- 178 subscribers (up 2 in the last 3 months):
- 114 emails sent to list (145 in previous quarter)
## JIRA activity:
- 12 JIRA tickets created in the last 3 months
- 9 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment N: Report from the Apache CloudStack Project [Wido den Hollander]
## Description:
Apache CloudStack (ACS) is an IaaS (Infrastructure as a Service) cloud
orchestration platform. ACS manages many types of hypervisors, storage
and networking devices.
## Issues:
- Project is still waiting to participate in the 'Github as Master' Beta
to provide the project access to Github features (CI, labels) without
being an anomaly in what Apache is supporting.
## Activity:
- Project is preparing for a good presence at ApacheCon USA in Miami
- Working hard on getting stable releases out
- Still figuring out how to further automate testing of CloudStack
- In both the 4.8 and 4.9 series releases were made in the last few months
and the first VOTE round for 4.10 failed, but RC2 will be voted on next
week
## Health report:
- Project is healthy. Lots of commits coming in and releases being prepared
- Discussions inside the PMC about new potential committers
- Main focus is still stability. Quality over quantity
## PMC changes:
- Wido den Hollander (widodh) is the new VP for the project
- Currently 44 PMC members.
- New PMC members:
- Paul Angus was added to the PMC on Fri Jan 13 2017
- Simon Weller was added to the PMC on Fri Jan 13 2017
## Committer base changes:
- Currently 112 committers.
- No new committers added in the last 3 months
- Last committer addition was Nicolás Vázquez at Fri Nov 25 2016
## Releases:
- Last release was 4.9.2.0 on Thu Jan 05 2017
## Mailing list activity:
- users@cloudstack.apache.org:
- 1115 subscribers (up 2 in the last 3 months):
- 554 emails sent to list (726 in previous quarter)
- dev@cloudstack.apache.org:
- 740 subscribers (up 1 in the last 3 months):
- 4696 emails sent to list (3985 in previous quarter)
- announce@cloudstack.apache.org:
- 487 subscribers (up 11 in the last 3 months):
- 0 emails sent to list (2 in previous quarter)
- issues@cloudstack.apache.org:
- 234 subscribers (up 2 in the last 3 months):
- 4565 emails sent to list (3248 in previous quarter)
- marketing@cloudstack.apache.org:
- 233 subscribers (down -2 in the last 3 months):
- 54 emails sent to list (38 in previous quarter)
- press@cloudstack.apache.org:
- 13 subscribers (down -2 in the last 3 months)
## JIRA activity:
- 168 JIRA tickets created in the last 3 months
- 342 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment O: Report from the Apache Commons Project [Gary D. Gregory]
-----------------------------------------
Attachment P: Report from the Apache Cordova Project [Shazron Abdullah]
## Description:
A platform for building native mobile applications using HTML, CSS and
JavaScript.
## Issues:
There are no issues requiring Board attention at this time.
## Activity:
There were two overall plugin releases this quarter. An overall plugin
release usually consists of all, if not most, of our 22 plugins. This
number was the same as last quarter.
We had three platform releases - two patch releases for Android (6.1.1 and
6.1.2) and one major release for Windows (5.0.0). Android patch releases
were to fix a CI issue, and a security issue, respectively. The major
Windows release introduces a major change in resource-file behavior and adds
WinMD + C++ based DLL combination support for plugins. There was no iOS
platform release this quarter, with ongoing work to release version 4.4.0 in
the coming weeks.
We had a minor tools release of the CLI version 6.5.0 which updated Android
platform pinning, as well as including minor fixes. We are planning a major
release of the tools (version 7.0) in the coming months.
## Health report:
Our status dashboard at http://status.cordova.io is mostly all green. The
badges that are red are general flakiness and unreliability of the CI
environments that we use, which we are trying to track down. We are running
into roadblocks with using Apache's account on Travis CI, where pull
requests usually don't start until more than 24 hours later:
https://issues.apache.org/jira/browse/INFRA-13634 which slows down
evaluating contributions and iterative development.
We still have a huge backlog of Github Pull Request activity, same as last
quarter -- but it has improved. We would have liked to have direct access to
Github to manage these issues better, instead of the workaround we have now.
Our JIRA issue resolve rate has vastly improved as well.
Our goal for plugins release is to have one per week as a cadence, and we
have failed to do so again this quarter. We have done work on streamlining
this so it will improve in the future.
## PMC changes:
- Currently 85 PMC members.
- Audrey So was added to the PMC on Sun Jan 22 2017
## Committer base changes:
- Currently 88 committers.
- Audrey So was added as a committer on Mon Jan 23 2017
## Releases:
- cordova-android@6.1.1 was released on Wed Jan 04 2017
- cordova-android@6.1.2 was released on Thu Jan 26 2017
- cordova-common@2.0.0 was released on Mon Jan 23 2017
- cordova-common@2.0.1 was released on Sun Mar 12 2017
- cordova-create@1.0.2 was released on Mon Jan 23 2017
- cordova-fetch@1.0.2 was released on Mon Jan 23 2017
- cordova-js@4.2.1 was released on Mon Jan 23 2017
- cordova-lib@6.5.0 was released on Mon Jan 23 2017
- cordova-plugin-battery-status@1.2.2 was released on Thu Dec 15 2016
- cordova-plugin-battery-status@1.2.3 was released on Mon Mar 06 2017
- cordova-plugin-camera@2.4.0 was released on Mon Mar 06 2017
- cordova-plugin-console@1.0.6 was released on Tue Mar 07 2017
- cordova-plugin-contacts@2.3.0 was released on Tue Mar 07 2017
- cordova-plugin-device-motion@1.2.4 was released on Tue Mar 07 2017
- cordova-plugin-device-orientation@1.0.6 was released on Tue Mar 07 2017
- cordova-plugin-device@1.1.5 was released on Tue Mar 07 2017
- cordova-plugin-dialogs@1.3.2 was released on Tue Mar 07 2017
- cordova-plugin-file-transfer@1.6.2 was released on Tue Mar 07 2017
- cordova-plugin-file@4.3.2 was released on Tue Mar 07 2017
- cordova-plugin-geolocation@2.4.2 was released on Tue Mar 07 2017
- cordova-plugin-globalization@1.0.6 was released on Tue Mar 07 2017
- cordova-plugin-inappbrowser@1.6.1 was released on Thu Dec 15 2016
- cordova-plugin-inappbrowser@1.7.0 was released on Tue Mar 07 2017
- cordova-plugin-media-capture@1.4.2 was released on Tue Mar 07 2017
- cordova-plugin-media@3.0.0 was released on Tue Mar 07 2017
- cordova-plugin-network-information@1.3.2 was released on Tue Mar 07 2017
- cordova-plugin-splashscreen@4.0.2 was released on Tue Mar 07 2017
- cordova-plugin-statusbar@2.2.2 was released on Tue Mar 07 2017
- cordova-plugin-test-framework@1.1.5 was released on Tue Mar 07 2017
- cordova-plugin-vibration@2.1.4 was released on Tue Mar 07 2017
- cordova-plugin-whitelist@1.3.2 was released on Tue Mar 07 2017
- cordova-plugin-wkwebview-engine@1.1.2 was released on Tue Mar 07 2017
- cordova-windows@5.0.0 was released on Thu Feb 09 2017
- cordova@6.5.0 was released on Mon Jan 23 2017
- plugman@1.4.1 was released on Mon Jan 23 2017
## JIRA activity:
- 320 JIRA tickets created in the last 3 months
- 321 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Q: Report from the Apache cTAKES Project [Pei J Chen]
## Description:
Apache clinical Text Analysis and Knowledge Extraction System (cTAKES) is
an open-source natural language processing system for information extraction
from electronic medical record clinical free-text.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Committee continues to work on the next release (4.0) and anticipate an
upcoming release soon with new features and improvements.
- Committee is actively working on updating the cTAKES Confluence website for
improved documentation
- James Masanz, an original cTAKES committer, also volunteered to help with
the upcoming release.
- Committee continues to make improvements to the system. e.g human-tagged
gold annotations of 18 mockup clinical notes done. Notes were generated by a
cTAKES committer-physician John Green. Format is Anafora
(https://github.com/weitechen/anafora), annotations are for signs/symptoms,
diseases/disorders, procedures, anatomical sites and medications with
relevant attributes and mappings to ontology concept codes. Human tagged
annotations done by Dave Harris at Boston Children's Hospital.
## PMC changes:
- Currently 30 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michelle Chen on Mon Feb 02 2015
## Committer base changes:
- Currently 35 committers.
- New commmitters:
- Azad Dehghan was added as a committer on Fri Jun 03 2016
- Lewis John McGibbney was added as a committer on Fri May 27 2016
- Peter Klügl was added as a committer on Fri May 27 2016
- Richard Eckart de Castilho was added as a committer on Fri May 27 2016
## Releases:
- Last release was 3.2.2 on Sat May 30 2015
- 3.2.1 was released on Dec 10 2014
- 3.2.0 was released on Jul 23 2014
## Mailing list activity:
There is a significant increase in the dev mailing list(s) over the
last quarter. This is partly due to the planned upcoming release.
- dev@ctakes.apache.org:
- 218 subscribers (up 8 in the last 3 months):
- 286 emails sent to list (77 in previous quarter)
- user@ctakes.apache.org:
- 203 subscribers (up 14 in the last 3 months):
- 26 emails sent to list (71 in previous quarter)
## JIRA activity:
- 11 JIRA tickets created in the last 3 months
- 6 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment R: Report from the Apache Curator Project [Jordan Zimmerman]
## Description:
- The Apache Curator Java libraries make using Apache ZooKeeper much easier
and more reliable.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- Curator activity is normal for this period - we are in the middle of a
release vote right now
- We continue to produce releases, field questions, etc.
- We continue to track releases of Apache ZooKeeper and try to stay current
with it
## Health report:
- The project is healthy and popular as ever
- We still need 1 or 2 more active committers
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Mike Drob on Wed Jul 22 2015
## Committer base changes:
- Currently 11 committers.
- No new committers added in the last 3 months
- Last committer addition was Mike Drob at Thu Jul 23 2015
## Releases:
- Last release was Apache Curator 2.11.1 on Sun Nov 13 2016
## Mailing list activity:
- dev@curator.apache.org:
- 56 subscribers (up 2 in the last 3 months):
- 511 emails sent to list (334 in previous quarter)
- user@curator.apache.org:
- 156 subscribers (down -1 in the last 3 months):
- 26 emails sent to list (94 in previous quarter)
## JIRA activity:
- 29 JIRA tickets created in the last 3 months
- 21 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment S: Report from the Apache Eagle Project [Edward Zhang]
Apache Eagle is an open source analytics solution for identifying security and
performance issues instantly on big data platforms.
## Issues:
There are no issues requiring board attention at this time
## Activity:
1. Nominated 2 committers in dev list and vote is on-going
2. 0.5 Release is not yet started which was scheduled end of Feb, but we are
approaching to start release this major version.
## Health report:
0.5 branch still has a lot of activities and people like this version's
simplicity and extensibility.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
## Committer base changes:
- Currently 16 committers.
- Ji Jun Tang was added as a committer on Mon Jan 23 2017
## Releases:
- No release in last month
## Mailing list activity:
- dev@eagle.apache.org:
- 71 subscribers (up 0 in the last 3 months):
- 249 emails sent to list (2840 in previous quarter)
- issues@eagle.apache.org:
- 16 subscribers (down -1 in the last 3 months):
- 1417 emails sent to list (305 in previous quarter)
- user@eagle.apache.org:
- 47 subscribers (up 3 in the last 3 months):
- 16 emails sent to list (3 in previous quarter)
## JIRA activity:
- 115 JIRA tickets created in the last 3 months
- 81 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment T: Report from the Apache Falcon Project [Srikanth Sundarrajan]
ABOUT
Falcon is a data processing and management solution for Hadoop
designed for data motion, coordination of data pipelines,
lifecycle management, and data discovery. Falcon enables end
consumers to quickly onboard their data and its associated
processing and management tasks on Hadoop clusters.
ISSUES
There are no issues that require board's attention at this time.
STATUS
After months of effort, user space extensions or recipe feature is complete
and is planned in the upcoming release 0.11. Falcon 0.11 should be released
in early Apr.
Backlog metrics Feature has been pushed, which enables users to view the
backlogs on dashboards. Falcon Shell has been added giving shell utilities
to Falcon CLI. The upcoming 0.11 release also includes some resource
optimization fixes. Entity updates with effective time feature and feed
retention based on instance production time are being considered for the
release following 0.11.
As project activity had declined in the recent past (there has been a
uptick since the last report), the PMC is looking at ways to grow the
developer and user community. PMC discussed and agreed to adopt a uniform
and simple committer invitation criteria (as recommended by CO50), as
there were challenges and subjectivity in our earlier approach. Also
we as a project are focusing to improve documentation and promote the
project in events to invite more developers and contributors further.
PMC CHANGES
- Currently 17 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sowmya Ramesh on Mon Jun 06 2016
COMMITTER CHANGES
- Currently 25 committers.
- Sandeep Samudrala was added as a committer on Thu Mar 09 2017
RELEASES
- Last release was 0.10 on Mon Aug 08 2016
MAILING LIST ACTIVITY
- dev@falcon.apache.org:
- 114 subscribers (up 4 in the last 3 months):
- 583 emails sent to list (430 in previous quarter)
-----------------------------------------
Attachment U: Report from the Apache Felix Project [Carsten Ziegeler]
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
The project is in good health. Questions on the user list are frequently
answered, development concerns are either discussed in the mailing list
or directly in the JIRA issues. Existing implementations are
improved/enhanced based on community feedback. Other activities are
covering implementing the new OSGi R7 specifications.
PMC: The last new PMC member was added in Jul. 2016.
Committers: Three new committers have been added (Stefan Seifert,
David Leangen and Neil Bartlett) The last new committer was
added in February 2017.
There are no issues requiring board attention at this time.
Software
Apache Felix Framework 5.6.2 and Resolver 1.12.0 released (February
20th, 2017)
Apache Felix Web Console Event Plugin 1.1.6 and
Apache Felix Web Console PackageAdmin Plugin 1.0.4 (February 20, 2017)
Apache Felix Web Console 4.3.0 (February 17, 2017)
Apache Felix Dependency Manager r9 (February 14, 2017)
Apache Felix Utils 1.9.0 (February 13, 2017)
Apache Felix Config Admin 1.8.14 (February 2, 2017)
Apache Felix JAAS 1.0.0 (January 30, 2017)
Apache Felix DS Webconsole Plugin 2.0.6 (January 24, 2017)
Apache Felix SCR 2.0.8, Apache Felix DS Webconsole Plugin 2.0.4,
Apache Felix Utils 1.8.6 (January 16, 2017)
Apache Felix Web Console 4.2.18 (January 13, 2017)
Apache Felix Http Jetty 3.4.2, Apache Felix Http Bridge 3.0.18, and
Apache Felix Http Base 3.0.18 (January 06, 2017)
Apache Felix SCR bnd Plugin 1.7.2 (January 02, 2017)
Apache Felix Maven SCR Plugin 1.24.0, Apache Felix SCR Ant Task 1.17.0,
Apache Felix SCR bnd Plugin 1.7.0 and
Apache Felix SCR Generator 1.16.0 (December 24, 2016)
-----------------------------------------
Attachment V: Report from the Apache Flex Project [Alex Harui]
Apache Flex is an application framework for easily building Flash-based
applications for mobile devices, the browser and desktop.
RELEASES
- Apache Flex FalconJX 0.7.0 was released on 9/7/16.
- Voting still underway for Apache Flex SDK 4.16.0.
- Preparing to vote on Apache Flex BlazeDS 4.7.3.
- Apache Flex SDK 4.15.0 was released on 1/9/16.
- Apache Flex BlazeDS 4.7.2 was released on 11/16/15.
- Apache Flex Tour De Flex Component Explorer 1.2 was released on 11/28/14.
- Apache Flex Tool API 1.0.0 was released on 11/20/14
- Apache Flex Squiggly 1.1 was released on 10/26/14
- Apache Flex Installer 3.2.0 was released on 6/23/15.
ACTIVITY
The past three months saw further increase in committer activity
around FlexJS. FlexJS is the next generation of Flex that provides
application developers with a highly productive framework and tool chain for
developing web apps, mobile apps and desktop apps. Traditional Flex
applications require Adobe Flash/AIR runtimes (or tools to pre-compile them to
Android/IOS). FlexJS applications output HTML/JS/CSS and can even be used to
create Apache Cordova applications.
Christofer Dutz has taken the lead on the first ever FlexJS Summit at
ApacheCon NA in Miami. About 6 other PMC members have helped to get the word
out, and proposed talks. One new company announced on the dev list that they
are planning to attend. So far, no other new names have stated that they will
attend.
A few new names have appeared on the mailing list, indicating that interest is
up. There is at least one person we are watching as a potential committer
candidate.
COMMUNITY
- Last committer as added on 9/5/16.
- Yishay Weiss was added to the PMC on 1/20/17.
- Latest analytics include a little less than 1000 hits per day on the website
during the work week (less on weekends).
- There were more than 16000 installs of Apache Flex 4.15.0 since its release
in January 2016.
- More than 115,000 people have run the Tour De Flex application. Tour De
Flex is a set of examples folks use to learn how to develop Flex
applications.
TRADEMARKS
- A company is promoting a software product called Flex that appears to be
related to themes/styles for website visuals. Despite several attempts to
contact them, they have not responded. The ASF VP Trademarks sent them an
email on 11/3/16. I did not see a response and their website is still up.
What is the next step?
-----------------------------------------
Attachment W: Report from the Apache Flink Project [Stephan Ewen]
DESCRIPTION
Apache Flink is a distributed data streaming system for batch and streaming
data analysis on top of a streaming dataflow engine. Flink's stack contains
functional batch and streaming analysis APIs in Java and Scala and libraries
for various use cases.
Flink interacts and integrates with several Apache projects in the broader
ecosystem of data storage and computing, such as Apache Beam (incubating),
Hadoop, Kafka, HBase, Cassandra, and others.
ISSUES
- There are no issues that require board attention.
STATUS AND ACTIVITY
- The project continues to have quite a high activity, with many
contributions both for complex long-term features, and small usability-
and bug fixes. We are growing the committer base in order to keep up
with the contributions.
- While additional committers are helping in many of the user-facing
components, there are still some more low-level components where
expertise naturally takes a bit longer to spread. The committers keep
working with more contributors on those parts to help with that.
- The PMC is currently in progress of adding another member. The vote has
passed, currently waiting for the board notice period before extending
the invitation.
- After the previous release, the community discussed and decided to
switch to a strictly time-based release policy. That makes it
more predictable for both users and contributors. The initial
interval was decided to be 4 months, which would mark the next
release at mid May.
- The community has started to gather issues for the bugfix releases
1.2.1 and probably 1.1.5
- There has been a long discussion (not fully concluded) how to make it
easier to working on Flink libraries (Graph Processing, Complex Event
Processing, Machine Learning). Some issues are teh large code base and
the increasingly long build times. Other discussions are how to foster
activity in those specific components.
- The Program for the upcoming Flink Forward conference in San Francisco
has been announced. There will be talks by users and committers about
use cases, technology, community participation, and ecosystem
integration.
- Aside from the talks at Flink Forward, there will be presentations about
Flink at Strata, Dataworks Summit, Kafka Summit, and other conferences.
- The results from a Flink survey by data Artisans have been shared in a
two part blog post. The link to the results was was shared over the
user/dev mailing lists.
COMMUNITY
We are in the process of adding a new PMC member.
The latest PMC addition was July 2nd, 2015 (Maximilian Michels)
Committers added since the last board report:
- Kostas Kloudas was added as a committer on February, 5th, 2017
- Jark Wu was added as a committer on February, 9th, 2017
- Stefan Richter was added as a committer on February 9th 2017
- Kurt Young was added as a committer on February 21st, 2017
Flink currently has 28 committers and 16 PMC members.
RELEASES
The following releases were made since the last board report:
- 1.1.4 was released on December, 21st, 2016
- 1.2.0 was released on February 2nd, 2017
ACTIVITY ON JIRA / MAILING LISTS
Both user@f.a.o and dev@f.a.o lists are very active, with mails getting
answered by a mix of committers and non-committers.
JIRA continues to be very active
(713 JIRA tickets created, 630 JIRA tickets over last 3 months)
-----------------------------------------
Attachment X: Report from the Apache Geronimo Project [Alan Cabrera]
## Description:
Apache Geronimo is a JEE6 certified 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.
## Issues:
- We are concerned with the lack of community activity
- The inability to obtain a AL2.0 compatible JEE TCK pins Geronimo to JEE6
- CI/TCK setup has fallen into disrepair
## Activity:
- Released geronimo-validation 1.0 spec API
- Released geronimo transaction manager 3.1.4
- A large number of patches from the IBM’s WAS Liberty application server
product was incorporated into Geronimo's Yoko CORBA sub-project.
Many thanks to David Jenks, Joe Chacko, and Neil Richards.
- The community is actively discussing possible pivots for the project.
## Health report:
- Traffic is relatively low, until the community began pivot discussions.
- There seem to be a number of very realistic viable options for Geronimo
that don't include a JEE7+ TCK.
## PMC changes:
- Currently 42 PMC members.
- No new PMC members added since 2014
## Committer base changes:
- Currently 70 committers.
- Reinhard Sandtner was added as a committer on Mon Feb 13 2017
## Releases:
- Released geronimo-validation 1.0 spec API
- Released geronimo transaction manager 3.1.4
## Mailing list activity:
- messages are up a bit due to the community's current pivot discussions
- dev@geronimo.apache.org:
- 351 subscribers (down -4 in the last 3 months):
- 197 emails sent to list (76 in previous quarter)
- user@geronimo.apache.org:
- 442 subscribers (down -3 in the last 3 months):
- 6 emails sent to list (2 in previous quarter)
## JIRA activity:
- much of this activity is due to the patches from the IBM’s WAS
Liberty application server product was incorporated into Geronimo's
Yoko CORBA sub-project.
- 21 JIRA tickets created in the last 3 months
- 62 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Y: Report from the Apache Giraph Project [Avery Ching]
-----------------------------------------
Attachment Z: Report from the Apache Gump Project [Stefan Bodewig]
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 ASF as well
as non-ASF projects and their dependencies. It started in the Java
part of the foundation but also builds projects like APR, HTTPd and
XMLUnit.NET.
== Summary ==
No changes compared to the last quarter, the service is humming along.
== Releases ==
Gump has never done any releases. One reason for this is that the ASF
installations of Gump work on the latest code base almost all of the
time following its "integrate everything continuously" philosophy.
== Activity ==
This has been a very quiet quarter for Gump. Gump seems to remain
useful for the projects using it.
== Changes to the Roster ==
All ASF committers have write access to the metadata that configure
the ASF installations.
The last changes to the PMC have seen Konstantin Kolinko and Mark
Thomas join in November 2014.
-----------------------------------------
Attachment AA: Report from the Apache Hama Project [Edward J. Yoon]
Apache Hama(TM) is a framework for Big Data analytics which uses the
Bulk Synchronous Parallel (BSP) computing model, which was established
in 2012 as a Top-Level Project of The Apache Software Foundation.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Hama community is going inactive. We discussed about this issue, 3 PMC
members said that they still have a interest in contribute this project.
We'll discuss more about how to manage the community in the future.
## Health report:
- Received few user-list emails and one subproject proposal. There's no
active improvement progress.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Behroz Sikander on Mon Feb 01 2016
## Committer base changes:
- Currently 17 committers.
- No new committers added in the last 3 months
- Last committer addition was JongYoon Lim at Tue Sep 13 2016
## Releases:
- Last release was hama-0.7.1 on Mon Mar 14 2016
## Mailing list activity:
- The framework has been stabilized in term of functionality. We need to let
more users find more bugs and find more use cases.
- dev@hama.apache.org:
- 115 subscribers (up 2 in the last 3 months):
- 11 emails sent to list (15 in previous quarter)
- user@hama.apache.org:
- 184 subscribers (down -2 in the last 3 months):
- 9 emails sent to list (2 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AB: Report from the Apache Helix Project [Kishore Gopalakrishna]
-----------------------------------------
Attachment AC: Report from the Apache Hive Project [Ashutosh Chauhan]
## Description:
- The Apache Hive (TM) data warehouse software facilitates querying and
managing large datasets residing in distributed storage.
## Issues:
- A concern is raised that some activities of Apache Spark project are not
in accordance to Apache way and is detrimental to our project. In
particular, Spark copy pasting Hive code and then subsequently releasing
jars with same names. Further, this forking of code may result in forking
of communities. What course of action (if any) Hive project should take
is still under discussion.
## Activity:
- Community is brainstorming on branching and releasing strategy to
accelerate development while still serving user community in predictable
manner. Discussion is still underway.
## Health report:
- Project continues to have strong user community which is active on users@.
- Project continues to receive strong contributions from various contributors.
## PMC changes:
- Currently 31 PMC members.
- Eugene Koifman was added to the PMC on Sun Mar 12 2017
- Last PMC addition was Eugene Koifman on Sun Mar 12 2017
## Committer base changes:
- Currently 63 committers.
- New commmitters:
- Zoltan Haindrich was added as a committer on Sat Feb 18 2017
- Naveen Gangam was added as a committer on Fri Dec 23 2016
- Rajesh Balamohan was added as a committer on Tue Dec 13 2016
## Releases:
- hive-storage-2.2.0 was released on Thu Jan 12 2017
- hive-storage-2.2.1 was released on Mon Feb 20 2017
## Mailing list activity:
- dev@hive.apache.org:
- 860 subscribers (up 11 in the last 3 months):
- 1535 emails sent to list (1263 in previous quarter)
- issues@hive.apache.org:
- 14 subscribers (up 0 in the last 3 months):
- 10117 emails sent to list (8076 in previous quarter)
- user@hive.apache.org:
- 2210 subscribers (up 31 in the last 3 months):
- 386 emails sent to list (403 in previous quarter)
## JIRA activity:
- 764 JIRA tickets created in the last 3 months
- 524 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AD: Report from the Apache Incubator Project [Ted Dunning]
Incubator PMC report for March 2017
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
There are currently 64 podlings incubating. In the month of February we had 7
releases and no changes in IPMC roster.
* Community
New IPMC members:
- None
People who left the IPMC:
- None
* New Podlings
- Gobblin
* Podlings that failed to report, expected next month
- Griffin
- Pony Mail
- Sirona
* Graduations
The board has motions for the following:
- None
* Releases
The following releases entered distribution during the month of
February:
- 2017-02-02 Apache Guacamole 0.9.11
- 2017-02-08 Apache SystemML 0.12.0
- 2017-02-12 Apache Singa 1.1.0
- 2017-02-15 Apache mynewt 1.0.0-b2
- 2017-02-20 Apache RocketMQ 4.0.0
- 2017-02-25 Apache Juneau 6.1.0
- 2017-02-27 Apache HAWQ 2.1.0.0
* Legal / Trademarks
- A great discussion happened regarding the IP clearance and missing SGA
around MADLib. It demonstrates the needs to ensure that proper provenance
is in place.
* Credits
- Report Manager: John D. Ament, Marvin Humphrey
----------------------------------------------------------------------
Table of Contents
AriaTosca
Atlas
Gearpump
Hivemall
HTrace
log4cxx2
Mnemonic
MRQL
MXNet
Myriad
ODF Toolkit
Omid
OpenWhisk
Pirk
Pony Mail
Quickstep
Ratis
RocketMQ
SAMOA
Singa
Sirona
Spot
Streams
Taverna
Tephra
Trafodion
Wave
Weex
----------------------------------------------------------------------
--------------------
AriaTosca
ARIA TOSCA project offers an easily consumable Software Development Kit(SDK)
and a Command Line Interface(CLI) to implement TOSCA(Topology and
Orchestration Specification of Cloud Applications) based solutions.
AriaTosca has been incubating since 2016-08-27.
Three most important issues to address in the move towards graduation:
1. Grow the community and enroll new committers.
2. Have frequent Release cycles to be compliant with the Apache Way.
3. Update ARIA website according to ASF guideline(Include release process
for ARIA-TOSCA Project).
4. Publish "How To Contribute" guide at ARIA-TOSCA Website.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Most of the project discussions are now happening on mailing lists.
How has the project developed since the last report?
TOSCA parser migrated into ASF
CI on Appveyor, Jenkins
Sphinx documentation added to the project
CLIs of workflow engine and parser coalesced
TOSCA CSAR packager added
APIs for workflows, operations
Workflow engine task retry support
Workflow engine execution cancel support
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
No release yet
When were the last committers or PPMC members elected?
Project is still operating with the initial set of committers.
Signed-off-by:
[X](ariatosca) Suneel Marthi
Comments:
Podling activity has been consistent and discussions are now happening
on the mailing lists.
[X](ariatosca) John D. Ament
Comments:
Podling activity peaks and dives. Would like to see more on-list
chatter.
[ ](ariatosca) Jakob Homan
Comments:
IPMC/Shepherd notes:
Drew Farris (shepherd): 2 mentors active on mailing lists, evidence of healthy
development activity. Consider a separate jira/commits list to encourage
discussion among humans on the dev list.
--------------------
Atlas
Apache Atlas is a scalable and extensible set of core foundational
governance services that enables enterprises to effectively and
efficiently meet their compliance requirements within Hadoop and
allows integration with the complete enterprise data ecosystem.
Atlas has been incubating since 2015-05-05.
Three most important issues to address in the move towards graduation:
1. Podling name search is pending. PODLINGNAMESEARCH-118 [1] was
opened to track this.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No specific issues at this time to report.
How has the community developed since the last report?
1. No new committers or PPMC additions since last time. About 4 new
contributors have been added since the last report. The current number
of contributors is around 74.
2. The activity on the atlas-dev mailing list stands at an average of
around 800 messages per month between December and February [2]
How has the project developed since the last report?
1. 0.7.1 (incubating) release of Apache Atlas was made on 30th January
2017 [3]. In addition, a 0.8 release is being planned and community is
focussed on this.
2. New features such as an improved API layer, more performance
improvements, UI enhancements to create new entities etc are being
planned in the 0.8 release. In addition, there are proposals to bring a
new Business Glossary feature.
3. A total of 238 issues were reported between Dec 1st 2016 and Feb
28th 2017. 160 issues have been resolved in the same time [4][5]
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2017-01-30: 0.7.1-incubating [3]
When were the last committers or PMC members elected?
The PPMC voted and elected 3 new members as committers to the project on
2016-10-20: Madhan Neethiraj, Jeffrey Hagelberg and Vimal Sharma.
Links:
[1] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-118
[2] http://markmail.org/search/?q=atlas#query:atlas%20list%3Aorg.apache.atlas.dev+page:1+state:facets
[3] https://lists.apache.org/thread.html/a63701573703d464c963e1cad9b93c0038c1826f841982b50d08c515@%3Cdev.atlas.apache.org%3E
[4] https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20created%20%3E%3D%202016-12-01%20AND%20created%20%3C%3D%202017-02-28
[5] https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolved%20%3E%3D%202016-12-01%20AND%20resolved%20%3C%3D%202017-02-28
Signed-off-by:
[ ](atlas) Arun Murthy
Comments:
[X](atlas) Chris Douglas
Comments:
[ ](atlas) Jakob Homan
Comments:
[ ](atlas) Vinod Kumar Vavilapalli
Comments:
--------------------
Gearpump
Gearpump is a reactive real-time streaming engine based on the micro-service
Actor model.
Gearpump has been incubating since 2016-03-08.
Three most important issues to address in the move towards graduation:
1. Release on a regular schedule.
2. Continue to evolve community interest and support.
3. Integrate within Apache Beam and Akka-stream frameworks.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None.
How has the community developed since the last report?
- Increased community contribution on Docker integration improvement.
- Applied for Google Summer of Code 2017 and we already have students
interested in our project.
How has the project developed since the last report?
- 34 issues created and 34 issues resolved.
- Added finite stream and session windows support.
- Akka-stream feature branch has been merged into master.
- Continued integration within Apache Beam (Gearpump Runner).
14 issues resolved.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-11-30 *and we plan to make next release in early March*.
When were the last committers or PPMC members elected?
- No new committers or PMC members elected yet.
Signed-off-by:
[X](gearpump) Andrew Purtell
Comments:
[ ](gearpump) Jarek Jarcec Cecho
Comments:
[ ](gearpump) Reynold Xin
Comments:
[ ](gearpump) Todd Lipcon
Comments:
[ ](gearpump) Xuefu Zhang
Comments:
--------------------
Griffin
IPMC/Shepherd notes:
Justin McLean:
No report and seems slow to get started / no web site or code imported
yet / low email traffic.
Uma Maheswara Rao G:
Seems slow in getting in to Apache Way process and mentors guiding on
that. There were confusions on report timings and mentors dropped
heads-up mail on that. Hope to see next report on time.
--------------------
Hivemall
Hivemall is a library for machine learning implemented as Hive
UDFs/UDAFs/UDTFs.
Hivemall has been incubating since 2016-09-13.
Three most important issues to address in the move towards graduation:
1. Create the first Apache release
2. Community growth (committers and users)
3. Documentation improvements
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Help would be required for IP clearance (being ready)
How has the community developed since the last report?
* Merged contributions from two external contributors.
* Mailing list activity (Jan-Feb): @dev: 78 messages
https://lists.apache.org/trends.html?dev@hivemall.apache.org:2017-01
https://lists.apache.org/trends.html?dev@hivemall.apache.org:2017-02
- The number of messages decreased in Feb because we changed
JIRA/github notification addresses to issues@hivemall.apache.org
* Github watchers/stars are gradually increasing:
52 stars as of Feb 28 (was 38 on Dec 26)
https://github.com/apache/incubator-hivemall
* Twitter account @ApacheHivemall followers are gradually increasing:
52 followers as of Feb 28 (was 33 on Dec 26)
* Submitted a talk to Apache BigData, Miami.
How has the project developed since the last report?
Worked hard towards the first Apache release.
* Documentation enrichment (e.g., Hivemall on Apache Spark)
http://hivemall.incubator.apache.org/userguide/
Since the last report (January 2017), we have
* Opened 40 JIRA issues
* Closed 13 JIRA issues
as seen in bit.ly/hivemall-jira-may
* Created 36 Pull Requests
https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20created%3A2017-01-01..2017-02-28
* Merged 33 Pull Requests
https://github.com/apache/incubator-hivemall/pulls?q=is%3Apr%20closed%3A2017-01-01..2017-02-28
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[x] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
No release yet
(planning the first Apache release in Q1 ~ Early Q2, 2017)
When were the last committers or PPMC members elected?
None
Signed-off-by:
[ ](hivemall) Reynold Xin
Comments:
[X](hivemall) Markus Weimer
Comments:
[ ](hivemall) Xiangrui Meng
Comments:
[X](hivemall) Daniel Dai
Comments:
--------------------
HTrace
HTrace is a tracing framework intended for use with distributed systems
written in java.
HTrace has been incubating since 2014-11-11.
Three most important issues to address in the move towards graduation:
1. Continue to grow the Apache HTrace community
2. Continue to explore projects integrating Apache HTrace
3. Continue to develop and release stable Apache HTrace incubating artifacts
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
There are no issues requiring board attention at this time.
How has the community developed since the last report?
Mailing lists have been quiet.
How has the project developed since the last report?
Development has been quiet.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-10-06
When were the last committers or PPMC members elected?
2016-10-03
Signed-off-by:
[ ](htrace) Jake Farrell
Comments:
[ ](htrace) Todd Lipcon
Comments:
[ ](htrace) Lewis John Mcgibbney
Comments:
[ ](htrace) Andrew Purtell
Comments:
[x](htrace) Billie Rinaldi
Comments:
[x](htrace) Michael Stack
Comments:
--------------------
log4cxx2
Logging for C++. N.B. This is a reboot of the Log4cxx podling which previously
graduated.
log4cxx2 has been incubating since 2013-12-09.
Three most important issues to address in the move towards graduation:
1. Create a release
2. Activate some community
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
There is an ongoing discussion since first quarter 2016 about how to deal
with this project, because no release happened yet and there's only little
activity regarding development and support. Especially no release is a
problem for incubating projects.
How has the community developed since the last report?
One support question, no new project members.
How has the project developed since the last report?
Robert Middleton finished his attempt to move the project to use C++
smart pointers instead of the former used custom implementation. That
work needs to be tested and integrated upstream, but there's no time plan
currently on when this will be done.
How would you assess the podling's maturity?
It seems this project has run its course in the incubator. The Logging PMC
needs to decide what to do with the project.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[X] Other: pretty much dormant
Date of last release:
2008-04-03 was the last official, pre-incubation 0.10.0
When were the last committers or PPMC members elected?
Signed-off-by:
[X](log4cxx2) Ralph Goers
Comments:
--------------------
Mnemonic
Apache Mnemonic is an advanced hybrid memory storage oriented library,
we've proposed a non-volatile/durable Java object model and durable
computing service that bring many advantages to significantly improve
the performance of massive real-time data
processing/analytics. developers are able to use this library to design
their cache-less, SerDe-less and native-direct computing high
performance applications.
Three most important issues to address in the move towards graduation:
1. Apache releases: we have release version 0.4.0-incubating
2. Integrated with Hadoop as Mapreduce Input/Output formatters.
3. Introduced Mnemonic to potential developers and users.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No.
How has the community developed since the last report?
Our last report was in Dec. Since then
* Two more developers are going to contribute code.
* We need to encourage more discussion on the dev list in the coming months
How has the project developed since the last report?
* Upgraded MemChunkHolder/MemBufferHolder to DurableChunk/DurableHolder
* Provided mnemonic-hadoop-mapreduce module with testcases
* and other bugfixes, features, improvements
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[*] Nearing graduation
[ ] Other:
Date of last release:
2017-01-24
When were the last committers or PMC members elected?
None
Signed-off-by:
[X](mnemonic) Patrick Hunt
Comments:
One year milestone as podling this month. Community growth has been
slow and activity dominated by one to two committers. Not clear how
active the mentors are in helping the podling - only two mentors
signed off on the report last quarter.
[X](mnemonic) Andrew Purtell
Comments:
Mentors have not been active, including myself. We may want to
solicit new or additional mentors for this podling.
[ ](mnemonic) James Taylor
Comments:
[ ](mnemonic) Henry Saputra
Comments:
--------------------
MRQL
MRQL is a query processing and optimization system for large-scale,
distributed data analysis, built on top of Apache Hadoop, Hama, Spark,
Flink, and Storm.
MRQL has been incubating since 2013-03-13.
Three most important issues to address in the move towards graduation:
1. Increase the number of active committers
2. Increase adoption, expand user community, and increase user list activity
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
One new MRQL committer was accepted since our last report. He developed
the new evaluation mode for MRQL that runs on top of Apache Storm.
How has the project developed since the last report?
There was very little activity on JIRA since our last report. The
resolved issues on JIRA included various bug fixes and performance
improvements.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-03-02
When were the last committers or PPMC members elected?
2016-12-22
Signed-off-by:
[X](mrql) Alan Cabrera
Comments:
[ ](mrql) Edward J. Yoon
Comments:
[ ](mrql) Mohammad Nour El-Din
Comments:
--------------------
MXNet
A Flexible and Efficient Library for Deep Learning
MXNet has been incubating since 2017-01-23.
Three most important issues to address in the move towards graduation:
1. Move the code and website to Apache Infrastructure.
2. Establish a formal release process and schedule, allowing for dependable
release cycles in line with Apache development process.
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
PPMC to discuss adding in some community members who asked to join while
the Incubator vote was in progress.
How has the community developed since the last report?
Project is still getting set up in Incubator.
How has the project developed since the last report?
Project is still getting set up, all proposed committers have submitted
their ICLAs.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
No Release yet
When were the last committers or PPMC members elected?
Project is being set up with the initial set of committers.
Signed-off-by:
[X](mxnet) Sebastian Schelter
Comments:
[X](mxnet) Suneel Marthi
Comments:
[X](mxnet) Markus Weimer
Comments:
[X](mxnet) Henri Yandell
Comments:
As project already exists in the public, this incubation is about
moving the development over without stopping the momentum of the
project, and then learning about the Apache development processes.
Previous conversations were Slack/GitHub-issue based, so making
decisions on the email list will be the first likely adaptation. A
dependency on ZeroMQ will be the primary discussion point for a first
release at Apache. PPMC list is still low on subscriptions, with
less than half of the PPMC members subscribed.
--------------------
Myriad
Myriad enables co-existence of Apache Hadoop YARN and Apache Mesos together on
the same cluster and allows dynamic resource allocations across both Hadoop
and other applications running on the same physical data center
infrastructure.
Myriad has been incubating since 2015-03-01.
Three most important issues to address in the move towards graduation:
1. Nurture dwindling developer community
2. Expand Myriad user base, get feedback from production deployments
3. Release new versions (0.3 in progress) with new features
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Participation is dropping, as developers are busy with other projects. When
should we consider retiring from the incubator?
How has the community developed since the last report?
* dev@ mailing list had 41 messages since the last report. 1 new user, 4
continuing users, 3 committers
* Bi-weekly dev syncs with 0-2 participants. Most cancelled due to lack of
attendance. Minutes at http://s.apache.org/8kF
How has the project developed since the last report?
* 1 PR and 1 JIRA closed.
* PRs #95, #96 and #100 are iterating. We can do a 0.3 release after they
merge.
* DC/OS Universe PR is in review, needs a walkthrough doc:
https://github.com/mesosphere/universe/pull/841
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-06-20 myriad-0.2.0-incubating
When were the last committers or PPMC members elected?
2016-06-16 Yuliya Feldman
Signed-off-by:
[ ](myriad) Benjamin Hindman
Comments:
[ ](myriad) Danese Cooper
Comments:
[ ](myriad) Ted Dunning
Comments:
[x](myriad) Luciano Resende
Comments:
--------------------
ODF Toolkit
Java modules that allow programmatic creation, scanning and manipulation of
OpenDocument Format (ISO/IEC 26300 == ODF) documents
ODF Toolkit has been incubating since 2011-08-01.
Three most important issues to address in the move towards graduation:
1. Get companies backing up the project as part of a commercial story, to
get a long-term momentum
2. Do recurrent releases - some semi-automation would be helpful - for the
3rd party users
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We have a lack of active mentors. Sam Ruby resigned due to switch of
personal focus. Mentors have not signed the past two reports, not answering
on direct mail. Overworked?
A general issue of the project is that it 'just' a toolkit of an office
file format, which in addition is far from leading on the business market,
so likely never being used by the mass market - a very niche product.
Still the toolkit seems to be working well for most common use cases, but
is repeatedly updated by developers on changes of the ODF, like Red Hat
developers enhancing the ODF validator as part of LibreOffice regression
tests (e.g. out-of-the-box running on http://odf-validator.rhcloud.com/)
most often quite ahead of one of the international ODF Plugfests -
http://odfplugfest.org/2016-paris/programme/.
Since there are still some game changing features in the pipeline (e.g.
collaboration) which are expected to strengthen the acceptance and develop
the community but on the other hand the mentorship / infrastructure of the
project could be better, a decision needs to be made on the future.
How has the community developed since the last report?
A company stated their commitment to the ODF toolkit and works on
contribution to the project.
We are working on the next release including the fixes and planning a
follow-up release adding new features.
How has the project developed since the last report?
Problem with Windows build bots were solved.
Build tested with JDK 6 to 8 under Windows and Linux with JDK 8.
Preparing a release after a long time to allow newcomers to rely on
state-of-the-art features.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2013-06-22, just started one
When were the last committers or PPMC members elected?
2015-10-05 - Damjan Jovanovic for Commiter/PPMC
Signed-off-by:
[ ](odftoolkit) Rob Weir
Comments:
[ ](odftoolkit) Nick Burch
Comments:
[ ](odftoolkit) Yegor Kozlov
Comments:
[X](odftoolkit) Tom Barber
Comments:
Clearly the project has some operational issues, both in active PMC
members and mentors. I'll work with Svante on trying to setup regular
releases and some marketing to try and attract new members and we'll
see where we go from there.
IPMC/Shepherd notes
--------------------
Omid
Omid is a flexible, reliable, high performant and scalable ACID transactional
framework that allows client applications to execute transactions on top of
MVCC key/value-based NoSQL datastores (currently Apache HBase) providing
Snapshot Isolation guarantees on the accessed data.
Omid has been incubating since 2016-03-28.
Three most important issues to address in the move towards graduation:
1. Boost project dissemination in the Apache community.
2. Collaborate/integrate Omid with other Apache projects.
3. Get positive feedback from other projects currently
integrating/using Omid.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
N/A
How has the community developed since the last report?
Started integration with Apache Phoenix community.
Omid presented in the SF HBase community event in Dec.
Omid paper accepted in FAST 2017
How has the project developed since the last report?
Started working in the next release.
Quarter Stats (from: 2016-12-01 to: 2017-02-28):
+---------------------------------------------+
| Metric | counts |
+---------------------------------------------+
| # of msgs in dev list | 36 |
| Active Contributors (incl mentors)| 6 |
| Jira New Issues | 4 |
| Resolved Issues | 2 |
| Pull Requests merged | 0 |
| Pull Requests proposed | 0 |
+---------------------------------------------+
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-06-24
When were the last committers or PPMC members elected?
At incubation acceptance (2016-03-28)
Signed-off-by:
[X](omid) Alan Gates
Comments:
Activity on this podling remains low but it is good to see a few
issues files and resolved and the report filed on time and without
prodding by the mentors.
[ ](omid) Lars Hofhansl
Comments:
[ ](omid) Flavio P. Junqueira
Comments:
[ ](omid) Thejas Nair
Comments:
[ ](omid) James Taylor
Comments:
--------------------
OpenWhisk
OpenWhisk is an open source, distributed Serverless computing platform able
to execute application logic (Actions) in response to events (Triggers) from
external sources (Feeds) or HTTP requests governed by conditional logic
(Rules). It provides a programming environment supported by a REST API-based
Command Line Interface (CLI) along with tooling to support packaging and
catalog services.
OpenWhisk has been incubating since 2016-11-23.
Three most important issues to address in the move towards graduation:
1. Moving github repos under the Apache Github Org (organization move,
repository renames), first 2 repos. moved; issues identified and being
worked.
2. Working to redirect openwhisk.incubator.apache.org to openwhisk.org,
update openwhisk.org to be Apache compliant (pre-req is repo. move
completion so that we can generate site via Jenkins/Apache tooling)
3. Working through project incubation checklists on CWIKI
Compliance Checklist for OpenWhisk.org website
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- Travis CI takes hours to process a PR on Apache Org; whereas it takes
minutes under current OpenWhisk org.
- The root cause is that Apache has 185 repos enable with Travis[1], but
only an allocation of 30 concurrent builds. OpenWhisk typically needs 5
concurrent build slots by itself continually.
- Many of the OpenWhisk’s repos. have cross-build dependencies (primarily
for Travis CI tests) this may will cause issues as repos. are brought
over 1 at a time if forwarding links are not preserved by GitHub.
- There may be issues with Committers in China being able
to enable 2FA since it does not work with their cell phones and the
alternative encryption tool seems to be blocked. Investigating with
infra.
How has the community developed since the last report?
- Committers have begun enable 2FA for GitHub and enable cross-
authentication to their Apache accounts using GitBox.
- “dev", “private” email list traffic continues to be healthy; positive
discussion of a few new code feature/change topics
- GitHub project “Stars” = 1144 (up from 1024 last month).
- a few new contributors in package deployment tool repo.
- more active discussions occurring on “dev” list.
- Created new public Slack Team (openwhisk-team.slack.com). includes
channels:
- “general” for general project questions and help
- “dev” channel where notifications of all OpenWhisk GitHub Issues are
posted.
- “dev-pr” channel where notifications of all OpenWhisk GitHub Pull
Requests are posted.
- Note: all development related discussions are directed to our “dev”
mailing list.
How has the project developed since the last report?
- Updating existing project code scan tools used in Travis CI to check for
ASF license header in files.
- Confluence WIKI
(https://cwiki.apache.org/confluence/display/OPENWHISK/OpenWhisk+Project+Wiki)
added pages for:
- Accessing Apache GitHub as a Committer
- GitHub How to Submit Pull Requests
- Developer Best Practices
- Active discussion on:
- Configuration through environment vs. Consul KV
- vanity urls for web actions
- Exposing garbage collector for nodejs runtime
- New features: webactions, official support for annotations
- New repo.: https://github.com/openwhisk/openwhisk-GitHubSlackBot
- This bot is designed to post updates to Slack when a GitHub pull
request is ready to merge or a list of pull requests are under review
for certain days and haven't merged.
- Submissions to “dev” list for new articles, use cases (new contribs.)
- New features: webactions, official support for annotations
- Multiple sessions submitted for ApacheCon NA. In addition, submitted for
panel talk and lightning talks.
Date of last release:
- No release yet
When were the last committers or PPMC members elected?
- Ioana Baldini, new committer 2017-02-09
- Justin Berstler, new committer 2017-02-20
Signed-off-by:
[X](openwhisk) Felix Meschberger
Comments:
[ ](openwhisk) Isabel Drost-Fromm
Comments:
[X](openwhisk) Sergio Fernández
Comments:
Podling still struggling with landing on ASF infrastructure, although
slowly making progress.
--------------------
Pirk
Pirk is a framework for scalable Private Information Retrieval (PIR).
Pirk has been incubating since 2016-06-17.
Three most important issues to address in the move towards graduation:
1. Grow the community to establish diversity of background and expertise.
2. Establish a formal release process and schedule, allowing for dependable
release cycles in a manner consistent with the Apache development
process.
3. Add to and improve the Pirk user documentation and examples both on the
website and in the codebase
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Yes. The Pirk community participation and growth has stalled over the last
few months. Recently, there's been discussion on the mailing lists about
retiring Pirk for now.
How has the community developed since the last report?
The Pirk community has not developed since the last report - no new
contributors or committers have been added
How has the project developed since the last report?
The project has stalled - the existing community has not been active nor
has the community grown.
How would you assess the podling's maturity?
The podling will not be seeing any activity in the near future, and the
consensus has been to retire the podling for now.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[X] Other:
Date of last release:
October 9, 2016
When were the last committers or PPMC members elected?
Pirk elected two new committers (Tim Ellison and Suneel Marthi, both
mentors) on August 18, 2016.
Signed-off-by:
[x](pirk) Billie Rinaldi
Comments:
[x](pirk) Joe Witt
Comments:
As noted in the report and observed in the community contributions
and discussion have stalled. Discussions to prompt engagement have
revealed that availability to contribute for much of the original
team is no longer available. It is my opinion that retirement should
be pursued given the range of community growth for the past few
months and stated lack of intent to turn that around soon.
[x](pirk) Josh Elser
Comments:
It's sad to see the discussion about the low recent activity quickly
change into a a discussion about retirement. I was hoping that the
previously active podling members would have taken some steps to
grow, but it seems like their priorities have shifted elsewhere. Pirk
had been doing quite well and is very interesting software; it's a
shame to see it moving to retirement. Sounds like retirement will be
pursued in the coming month.
[X](pirk) Suneel Marthi
Comments:
Based on recent discussions on Mailing lists the consensus has been
to retire Pirk for now, in large part due to unavailability of the
full set of initial committers that can steer this project forward.
[X](pirk) Tim Ellison
Comments:
Pirk had a very promising start, with the community exhibiting all
the right behaviors, including being able to gain consensus on an
early initial release. The initial committers are critical to the
future of Pirk due to their specialist knowledge, and there has not
been sufficient time to fully grow new members who can cover their
role. With their withdrawl it is unfortunate but inevitable that
Pirk be retired. The discussion is taking place on the dev list as
expected.
--------------------
Quickstep
Quickstep is a high-performance database engine that is designed to exploit
the full potential of hardware that is packed in modern servers. The initial
effort targets single-node in-memory environments.
Quickstep has been incubating since 2016-03-29.
Three most important issues to address in the move towards graduation:
1. Building a Quickstep community.
2. More adoption of the Quickstep technology.
3. No releases so far.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None.
How has the community developed since the last report?
Members of the community have become more aware about the release process.
The details about the release process that we plan to use are well
documented so that future releases will be smooth and more frequent.
How has the project developed since the last report?
We are working on our first release. Since the last report, we have done
the following:
* We have made several changes to the code base. Some highlights are:
Cleaning up the third party library code as per the Apache hygiene,
improve the code performance by adding several novel features.
* Preparation for release: Created scripts and step by step procedural
documentation for how to make a Quickstep release.
* Scripts have been added to the main repo while documentation is on
confluence.
* We went through several release candidates.
* During this period, we identified some usability issues on our supported
platforms and fixed them.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
November 2016.
Signed-off-by:
[ ](quickstep) Konstantin Boudnik
Comments:
[x](quickstep) Julian Hyde
Comments:
Lots of effort going into the first release - it's taken a while, but
it's very welcome! The community is getting better at having
discussions on the list (and not just about code). Have not seen many
potential new committers so far, but the release should change that,
and the project is starting to become more outward looking.
[x](quickstep) Roman Shaposhnik
Comments:
good progress
--------------------
Ratis
Ratis is a java implementation for RAFT consensus protocol.
Ratis has been incubating since 2017-01-03.
Three most important issues to address in the move towards graduation:
1. Setup wiki, jenkins
2. Make the first release.
3. Grow the community.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None
How has the community developed since the last report?
- One new contributor
How has the project developed since the last report?
- IP Clearance is completed
(https://incubator.apache.org/ip-clearance/ratis.html)
- Active development started in the community. 16 commits in last month.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup - Ip clearance, Git setup completed and development
started. Next step is to get jenkins going.
[ ] Working towards first release - Working towards first snapshot release.
Need INFRA help for access.
[ ] Community building - One new contributor
[ ] Nearing graduation
[ ] Other:
Date of last release:
- None
When were the last committers or PPMC members elected?
- Initial set of committers / PPMC.
Signed-off-by:
[ ](ratis) Chris Nauroth
Comments:
[ ](ratis) Devaraj Das
Comments:
[ ](ratis) Jakob Homan
Comments:
[X](ratis) Uma Maheswara Rao G
Comments:
--------------------
RocketMQ
RocketMQ is a fast, low latency, reliable, scalable, distributed, easy to use
message-oriented middleware, especially for processing large amounts of
streaming data.
RocketMQ has been incubating since 2016-11-21.
Three most important issues to address in the move towards graduation:
1. Make our first Apache release and vote in our first committer / PMC
members – COMPLETE
2. Moving sub-projects from GitHub into the ASF
3. Grow the community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
* Increased mailing list activity: solutions and milestone plan are
discussed and decided in mailing list.
* More than 15+ new contributors from different organizations since
podling.
* Organized 1 hackathon in community, the attendees was more than 50+. The
mainly contributors have subscribe our dev mailing list and begin to be
familiar to Apache way.
* Star has increased to 516 from 0 since move repository from alibaba to
apache.
* Voted upon and invited 2 new committers in PPMC since entering podling.
How has the project developed since the last report?
* The first release of RocketMQ as part of the Apache incubator on
2017-2-22.
* Since November 111 issues+ have been reported on JIRA site and 50 have
been resolved or closed. The plus are all association with the future
release version. Since November 70+ pull requests have been created and
44+ pull requests have been closed. The 3 guys review mechanism was to
be applied, we highly value the quality of the Apache project.
* Created Travis CI, Sonar and Coveralls, project infrastructure for
RocketMQ. Apply JIRA agile and kanban for RocketMQ committers.
* Created the website: http://rocketmq.incubator.apache.org and some
necessary document have been created such as user guide, developer
guide, faq, etc.
* There are more than 5+ Apache project integration are decided to be done
in the future release, such as ignite, storm etc.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup - The initial setup went pretty well with assistance
from John Ament and his Incubator documentation improvement efforts.
[ ] Working towards first release - The podling has performed its first
release as noted below
[ ] Community building - Some contributors are beginning to participate.
So far users have been slow to show up, so more effort on this front
will be encouraged.
[ ] Nearing graduation - Making progress, not there yet.
[ ] Other:
Date of last release:
2017-02-21
When were the last committers or PPMC members elected?
27 Feb 2017 - Roman Shtykh
27 Feb 2017 - Zhen Dong Liu
Signed-off-by:
[X](rocketmq) Bruce Snyder
Comments:
[ ](rocketmq) Brian McCallister
Comments:
[ ](rocketmq) Willem Ning Jiang
Comments:
[ ](rocketmq) Luke Han
Comments:
[X](rocketmq) Justin McLean
Comments:
Missing from issues above is moving [1] to inside the project.
1. https://github.com/rocketmq
IPMC/Shepherd notes:
Drew Farris (shepherd): 4 mentors active on the mailing lists. Congratulations
on the first incubator release. Healthy progress.
--------------------
SAMOA
SAMOA provides a collection of distributed streaming algorithms for the
most common data mining and machine learning tasks such as
classification, clustering, and regression, as well as programming
abstractions to develop new algorithms that run on top of distributed
stream processing engines (DSPEs). It features a pluggable architecture
that allows it to run on several DSPEs such as Apache Flink, Apache
Storm, Apache Apex and Apache Samza.
SAMOA has been incubating since 2014-12-15.
Three most important issues to address in the move towards graduation:
1. Grow the developer base
2. Grow the user base
3. Add some more ML techniques
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Mailing list activity (December 2016 - February 2017):
* @dev: 24 messages
Jira issues backlog (December 2016 - February 2017):
* Created: 2
* Resolved: 0
- We are organizing an internal workshop on SAMOA at Telefonica
I+D with researchers of Orange Labs
- We had a presentation of Apache Samoa at Paris Machine Learning
Meetup and Hamburg Machine Learning Meetup
- Bhupesh Chawda has presented Apache SAMOA in different venues
with his presentation "Machine Learning Support in Apache Apex
(Next Gen Hadoop) with Apache SAMOA"
- We invited edi_bice who made several contributions last
spring to become a committer.
- We published a scientific paper using Apache Samoa and one of
its machine learning techniques (Vertical Hoeffding Tree)
presented in IEEE BigData Conference last December 2016.
- We submitted a paper on SAMOA to a post-proceedings book of the
workshops MUSE/MSM 2015/2016 in the Springer LNCS/LNAI series.
How has the project developed since the last report?
- We are looking into new ML techniques for development.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-09-30
When were the last committers or PMC members elected?
None
Signed-off-by:
[X](samoa) Alan Gates
Comments:
Activity on this podling remains low. It is good to see a new
committer being elected. Shouldn't that be noted in the final section
on when new committers and PMC members were elected?
[ ](samoa) Ashutosh Chauhan
Comments:
[ ](samoa) Enis Soztutar
Comments:
[ ](samoa) Ted Dunning
Comments:
--------------------
Singa
Singa is a distributed deep learning platform.
Singa has been incubating since 2015-03-17.
Three most important issues to address in the move towards graduation:
1. Improve distributed training in SINGA V1.2
2. Improve the documentation and add more examples
3. Attract more contributors
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
No
How has the community developed since the last report?
There were 66, 60, and 43 emails from dev@ list in December 2016, January
2017 and February 2017 respectively.
There are 67 new commits since the last report.
One new committer (Li Boon Tan) was added.
How has the project developed since the last report?
We released the V1.1 version after the last report. The following features
were added after last report
+ Ease the installation process via Docker images, debian packages, conda
packages and Amazon AMI (CPU version)
+ Integrate with Jenkins for automatically generating convenient packages
and updating the website.
+ Improve the model classes: adding debug mode, adding the Concat and Slice
layers, and supporting model loading and saving via the Snapshot API
+ Add image_tool.py for image augmentation and rafiki sub-package for
providing RESTFul APIs.
+ Enable Java binding (basic) for SINGA
+ Add examples pre-trained from Caffe, e.g., GoogleNet, and examples
pre-trained from torch, e.g. ResNet
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-02-12
When were the last committers or PMC members elected?
2017-02-26
Signed-off-by:
[ ](singa) Daniel Dai
Comments:
[X](singa) Alan Gates
Comments:
On the maturity assessment I would say the community is in the
"Community building" phase but not far from the "Nearing graduation"
phase.
[ ](singa) Ted Dunning
Comments:
[ ](singa) Thejas Nair
Comments:
--------------------
Spot
Apache Spot is a solution stack that provides the capability to ingest IT
related telemetry (network flows, domain name service information and proxy
server logs) and provide unsupervised machine learning capabilities to
identify suspicious activity. The information is organized and presented
using operational analytics so that a security analyst can investigate the
most suspicious connections. Apache Spot is built on an open data model using
Apache Spark and Apache Hadoop.
Spot has been incubating since 2016-09-23.
Three most important issues to address in the move towards graduation:
1. Move infrastructure and development to ASF (code, issues, mailing
list, ...)
2. Build diverse community
3. Demonstrate ability to create releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?
None
How has the community developed since the last report?
Based on initial feedback, process for issues was updated on the project
website, with primary objective to facilitate the workflow and interaction
with Community, and having diverse ownership of them until resolution.
Slack channel has become very popular, however in order to adhere to ASF
official communications channels, those conversations that involve quick
question will be kept there, any extended discussion on code, pipeline, and
architecture, are being ported to Dev mail list.
There has been a concern to get continuous improvement of the UI on Apache
Spot, committers have been working on process to get UX interviews that
help to understand and address community and compliance needs.
How has the project developed since the last report?
The project got a major architecture change in order to remove CSV’s,
offload storage from the OS file system and instead leverage HDFS (for
distributed architecture).
Per community request through JIRA issue, and in order to facilitate the
installation/adoption of the project for scale deployments, an installation
script consolidating the ones that were built per pipeline component has
been pulled to repository, it will reduce the complexity of porting files
and configuration variables, by having a central point of deployment.
Open Data Models, which serves as a framework for data sources
normalization, initially for ingestion, was ported through its
Specification to the project repository, this will bring more contributions
to facilitate the design of the NoSQL table, and then determine technology
selection through discussion and voting through mailing list.
February Metrics:
+---------------------------------------------+
| Metric | counts |
+---------------------------------------------+
| Active Contributors (incl mentors)| 14 |
| Jira New Issues | 6 |
| Resolved Issues | 1 |
| Pull Requests merged | 3 |
| Pull Requests proposed | 3 |
+---------------------------------------------+
Date of last release:
N/A
When were the last committers or PMC members elected?
Last committer was elected on 2/24
How does the podling rate their own maturity?
There was a strong focus on code delivery over the last quarter, towards
Apache release, community adoption keeps growing, now by adding a layer of
process for opening issues and commits, plus interaction over channels
we're bringing contributions from others, towards Apache release.
Signed-off-by:
[x](spot) Jarek Jarcec Cecho
Comments:
[ ](spot) Brock Noland
Comments:
[ ](spot) Andrei Savu
Comments:
[x](spot) Uma Maheswara Rao G
Comments:
--------------------
Streams
Apache Streams is a lightweight server for ActivityStreams.
Streams has been incubating since 2012-11-20.
Three most important issues to address in the move towards graduation:
1. Community growth and PMC maturity.
2. Demonstrate a consistent release schedule.
3. Participation of project community within related standards-bodies
and Apache projects.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The podling has satisfied all of the requirements as laid down in the Apache
Maturity Model and is ready to graduate to TLP.
The Apache Maturity Model Assessment for Streams can be found at:
https://cwiki.apache.org/confluence/display/STREAMS/Apache+Maturity+Model+Assessment+for+Streams
How has the community developed since the last report?
Dev List
60 emails sent by 14 people, divided into 27 topics.
Web Page
844 Sessions, 631 Users, 2183 Pageviews.
How has the project developed since the last report?
Source Control
https://github.com/apache/incubator-streams
Excluding merges, 5 authors have pushed 46 commits to master. On master,
446 files have changed and there have been 22,388 additions and 13,129
deletions.
https://github.com/apache/incubator-streams-examples
Excluding merges, 2 authors have pushed 29 commits to master and 2
commits to all branches. On master, 79 files have changed and there
have been 2655 additions and 2458 deletions.
Team presently has a 0.5-incubating release candidate out for PPMC voting
and will be pushing the same for IPMC vote the week of March 5, 2017.
Since September 2016, the project has had 4 releases and has been having
consistent activity.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2016-12-26
When were the last committers or PPMC members elected?
2016-10-27: Joey Frazee elected as committer / PPMC member
2016-09-28: Suneel Marthi elected as mentor / PPMC member
Signed-off-by:
[X](streams) Matt Franklin
Comments:
The podling has a small, but invested community from multiple
different companies. I agree with Suneel that we should consider
graduation.
[X](streams) Ate Douma
Comments:
Getting close to termination a little over 6 months ago because of
lack of activity, the podling has remarkably revived and revitalized
itself, and IMO now is in good shape, ready to graduate.
[X](streams) Suneel Marthi
Comments:
This podling is ready to graduate and has fulfilled all the criteria
as laid down in the Apache Maturity Model Assessment. The discussion
to graduate the podling can start off once the in progress Streams
0.5-incubating release is through.
--------------------
Taverna
Taverna is a domain-independent suite of tools used to design and execute
data-driven workflows.
Taverna has been incubating since 2014-10-20.
Three most important issues to address in the move towards graduation:
1. Project maturity evaluation
2. IP/Licence Review
3. Graduate!
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Reviewing licences and IP with a view to graduation.
https://cwiki.apache.org/confluence/display/TAVERNADEV/2016-09+License+review
How has the community developed since the last report?
List has gone a bit more quiet, while activity on the
Gitter chat https://gitter.im/apache/taverna
has remained at same level. Need to re-focus use of
mailing list and community development.
How has the project developed since the last report?
Preparing maturity report, almost ready for graduation vote.
Taverna has a lot of different code bases and we are reviewing
what code we should remove from the repo while leaving a core set
of modules for graduation.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[x] Nearing graduation
[ ] Other:
Date of last release:
2016-07-01 taverna-engine-3.1.0-incubating
2016-07-01 taverna-common-activities-2.1.0-incubating
2016-07-01 taverna-commandline-3.1.0-incubating
When were the last committers or PPMC members elected?
2016-10-20 Committer
2015-12-09 PPMC member
Signed-off-by:
[x](taverna) Andy Seaborne
Comments:
Taverna dev@ has been quiet for this reporting period. The podling
is trying to establish which parts of the total software grant to
take through the incubator process into a TLP. There are still parts
that have not been released or at a minimum checked for IP.
The active PPMC membership is low and it would be better to work on
community growth to provide a stable PMC as a TLP.
[ ](taverna) Daniel J Debrunner
Comments:
[ ](taverna) Marlon Pierce
Comments:
[x](taverna) Stian Soiland-Reyes
Comments:
Activity has stalled a bit in the drive towards graduation, as some
(perhaps tedious) IP review remains. Ambition levels might need
adjustment, e.g. don't include all repositories in graduation to
TLP.
[ ](taverna) Suresh Marru
Comments:
[ ](taverna) Suresh Srinivas
Comments:
IPMC/Shepherd notes:
John D. Ament:
The concerns about IP review may be valid, but there seems to be a disconnect
on community graduation vs code graduation.
--------------------
Tephra
Tephra is a system for providing globally consistent transactions on top of
Apache HBase and other storage engines.
Tephra has been incubating since 2016-03-07.
Three most important issues to address in the move towards graduation:
1. Regular releases
2. Improve community engagement
3. Increase adoption
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
- None at this time.
How has the community developed since the last report?
- 1 new subscriber in dev mailing list since the last report
- 25 new JIRAs filed since the last report
- 0 external contributors submitted patches since the last report
- 1 external contributor created a ticket in JIRA since the last report
How has the project developed since the last report?
- Working on 0.11.0-incubating release
- Released 0.10.0-incubating
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of the last release:
2016-12-16
When were the last committers or PMC members elected?
- None since coming to incubation
Signed-off-by:
[X](tephra) Alan Gates
Comments:
[X](tephra) Andrew Purtell
Comments:
[ ](tephra) James Taylor
Comments:
[ ](tephra) Lars Hofhansl
Comments:
--------------------
Trafodion
Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or
operational workloads on Hadoop.
Trafodion has been incubating since 2015-05-24.
Three most important issues to address in the move towards graduation:
1. Develop community and bring in more diverse contributors.
2. Continue the momentum and become more integrated with the
rest of the Apache community.
3. Continue to create software releases.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* None
How has the community developed since the last report?
* Participation in public lists has declined slightly:
503 messages in the codereview forum, 560@commits,
246@dev, 871@issues and 26@user.
* 217 people are following @trafodion on Twitter.
* We are working towards our next release, 2.1.
* Gunnar Tapper stepped down as the Release Manager on Feb. 5th
and Sandhya Sundaresan volunteered on Feb. 9th to take over
that role.
* The community continues to be active in China, with
some communications happening outside the Apache dev lists.
* We had discussions about our readiness to graduate. Many
people feel that we are ready, others felt that we should
get more diverse contributors first.
How has the project developed since the last report?
* 173 commits from 21 contributors.
* 127 JIRAs filed and 112 resolved Dec 1 - Feb 27.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2016-07-07 2.0.1
When were the last committers or PPMC members elected?
in August 2016
Signed-off-by:
[ ](trafodion) Devaraj Das
Comments:
[ ](trafodion) Enis Söztutar
Comments:
[x](trafodion) Michael Stack
Comments:
--------------------
Wave
A wave is a hosted, live, concurrent data structure for rich communication. It
can be used like email, chat, or a document.
Wave has been incubating since 2010-12-04.
Three most important issues to address in the move towards graduation:
1. Growing community
2. Improving code base
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Pablo Ojanguren has accepted invitation to become committer.
Community is discussing whether it have reached
a sufficient level of stability to consider graduation.
How has the project developed since the last report?
IP clearance got from SwellRT former copyright owners.
In process to plan a release.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
March 2016
When were the last committers or PPMC members elected?
December 2016
Signed-off-by:
[x](wave) Upayavira
Comments:
--------------------
Weex
Weex is a framework for building Mobile cross-platform high performance UI.
Weex has been incubating since 2016-11-30.
Three most important issues to address in the move towards graduation:
1. Weex codebase has been migrated to Apache git repo.
2. Weex website has been deployed to https://weex.incubator.apache.org/ in gitpubsub way.
3. Made some guide for users and developers to Apache.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
No
How has the community developed since the last report?
* Just a beginning in Apache.
* 71 stars and 14 forks in our new Apache repo in GitHub.
* Notice: We have stopped committing code to the old repo since Feb 24 2017
but there are still a lot of activities which need to be migrated here.
How has the project developed since the last report?
* Weex codebase has been migrated to Apache git repo.
* Travis-ci enabled for our new repo above.
* Weex website has been deployed to https://weex.incubator.apache.org/ in
gitpubsub way.
* JIRA & Confluence space ready.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[x] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
No
When were the last committers or PPMC members elected?
No
Signed-off-by:
[ ](weex) Luke Han
Comments:
[ ](weex) Willem Jiang
Comments:
[ ](weex) Stephan Ewen
Comments:
[x](weex) Niclas Hedhman
Comments:
The project from a technical point of view is doing well. I am trying
to get the participants really grok TheApacheWay, as there is still too
much "corporate think" in the project, and things are done seemingly
randomly. The GitHub workflow is also something that I worry about,
since it makes the mailing list look like a commit log and not really a
community discussion forum. There is some who listens and trying to get
their colleagues to understand. This doesn't seem to be a language
(Chinese) issue as much as a GitHub culture issue. These guys love
GitHub issues and pull requests. But I am hopeful we will get there.
-----------------------------------------
Attachment AE: Report from the Apache Jackrabbit Project [Michael Dürig]
## Description:
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 Jackrabbit content
repository is stable, largely feature complete and actively being
maintained.
Jackrabbit Oak is an effort to implement a scalable and performant
hierarchical content repository as a modern successor to the Apache
Jackrabbit content repository. It is targeted for use as the
foundation of modern world-class web sites and other demanding
content applications. In contrast to its predecessor, Oak does not
implement all optional features from the JSR specifications and it
is not a reference implementation.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the unstable development branch are
continuously seeing moderate to high activity.
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling. New features are mainly
driven by dependencies from Oak.
This quarter saw the 4th major release of Jackrabbit Oak (1.6).
There is an ongoing effort to stabilise our continuous integration
(Jenkins) infrastructure. The deployment of the Jira plug-in resulted
in further insight and improvements. It also revealed that over 25%
of the issues are caused by infrastructure problems rather than
our project.
The PMC is currently evaluating the impact of the recently published
SHA-1 collisions on our products.
## Health report:
The project is healthy with a continuous stream of traffic on all
mailing lists reflecting the activity of the respective component.
There is a wide range of topics being discussed on the dev and user
lists as well as on the various JIRA issues.
Commit activity was moderate to high this quarter with a plunge around
the Christmas break.
## PMC changes:
- Currently 50 PMC members.
- Andrei Dulceanu was added to the PMC on Mon Dec 19 2016
## Committer base changes:
- Currently 50 committers.
- Andrei Dulceanu was added as a committer on Fri Dec 16 2016
## Releases:
- Jackrabbit-2.12.6 was released on Tue Dec 06 2016
- Jackrabbit-2.13.5 was released on Wed Dec 07 2016
- Jackrabbit-2.10.5 was released on Mon Jan 16 2017
- Jackrabbit-2.12.6 was released on Tue Dec 06 2016
- Jackrabbit-2.13.5 was released on Wed Dec 07 2016
- Jackrabbit-2.13.6 was released on Wed Dec 14 2016
- Jackrabbit-2.13.7 was released on Mon Dec 19 2016
- Jackrabbit-2.14.0 was released on Tue Jan 03 2017
- Jackrabbit-2.15.0 was released on Mon Jan 09 2017
- Jackrabbit-2.4.7 was released on Mon Jan 30 2017
- Jackrabbit-2.6.8 was released on Mon Feb 06 2017
- Jackrabbit-2.8.4 was released on Mon Jan 23 2017
- Jackrabbit-2.8.5 was released on Mon Feb 20 2017
- Jackrabbit Oak-1.0.36 was released on Tue Jan 03 2017
- Jackrabbit Oak-1.0.37 was released on Mon Feb 13 2017
- Jackrabbit Oak-1.2.22 was released on Mon Dec 12 2016
- Jackrabbit Oak-1.2.23 was released on Tue Jan 10 2017
- Jackrabbit Oak-1.4.11 was released on Mon Dec 12 2016
- Jackrabbit Oak-1.4.12 was released on Tue Jan 10 2017
- Jackrabbit Oak-1.4.13 was released on Tue Feb 07 2017
- Jackrabbit Oak-1.5.15 was released on Thu Dec 08 2016
- Jackrabbit Oak-1.5.16 was released on Mon Dec 19 2016
- Jackrabbit Oak-1.5.17 was released on Wed Jan 04 2017
- Jackrabbit Oak-1.5.18 was released on Wed Jan 18 2017
- Jackrabbit Oak-1.6.0 was released on Mon Jan 23 2017
## JIRA activity:
- 715 JIRA tickets created in the last 3 months
- 632 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AF: Report from the Apache Karaf Project [Jean-Baptiste Onofré]
## Description:
- Apache Karaf provides a very modern and polymorphic container,
multi-purpose (microservices, OSGi, etc) powered by OSGi.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- We released first version in our new main serie: 4.1.0. It's a new major
version. A 4.1.1 fix release is in preparation.
- New release of Karaf Cellar and Decanter are in preparation.
- We are beginning the work for a full JDK9 support, we expect to achieve the
result in release 4.2.0
## Health report:
We can note an increase in user community recently, probably due to new Karaf
adoption in products or other projects.
We are watching new potential PMC members, a format discussion and vote will
stand on the private mailing list pretty soon.
Talks have been proposed at ApacheCon NA. As several committers will be at
ACNA, we plan to organize an informal event (like a dinner).
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Christian Schneider on Mon Aug 22 2016
## Committer base changes:
- Currently 29 committers.
- No new committers added in the last 3 months
- Last committer addition was Grzegorz Grzybek at Mon Oct 31 2016
## Releases:
- 4.0.8 was released on Sun Dec 18 2016
- 4.1.0 was released on Sat Feb 04 2017
## Mailing list activity:
- dev@karaf.apache.org:
- 186 subscribers (up 3 in the last 3 months):
- 296 emails sent to list (341 in previous quarter)
- issues@karaf.apache.org:
- 41 subscribers (up 2 in the last 3 months):
- 1148 emails sent to list (1414 in previous quarter)
- user@karaf.apache.org:
- 372 subscribers (up 2 in the last 3 months):
- 618 emails sent to list (700 in previous quarter)
## JIRA activity:
- 135 JIRA tickets created in the last 3 months
- 153 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AG: Report from the Apache Labs Project [Danny Angus]
## Description
Apache Labs exists to incubate small and emerging projects from ASF
committers.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
In the past few weeks I have started a series of actions intended
to determine whether there is any interest from committers or a section of the
committers in reforming Labs to make it relevant. If this activity comes to
nothing the project will be closed down.
## Health report:
Lack of activity does not imply a lack of health, the PMC and
committers include experienced and active members and committers, however
prolonged inactivity coupled with limited visibility and an offering that is
not fit for purpose do raise questions about the viability of the project.
I have recently started some activity to identify volunteers and
gauge whether or not there might be any value in revising the service.
If there is not enough volunteer activity generated by this to
sustain the project it will be retired.
My own opinion is that a vibrant Labs community could be an asset
to the ASF, and to our committers, but as with all things ASF this
will require volunteer energy.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Iversen on Tue Feb 04 2014
## Committer base changes:
- Currently 31 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Iversen at Thu Feb 27 2014
## Releases:
- Labs does not make releases
## Mailing list activity:
labs@labs.apache.org:
208 subscribers (up 31 in the last 3 months):
40 emails sent to list (0 in previous quarter)
-----------------------------------------
Attachment AH: Report from the Apache Lucene Project [Tommaso Teofili]
## Description:
- Lucene Core is a search-engine toolkit
- Solr is a search server built on top of Lucene Core
## Issues:
- There are no new issues requiring board attention at this time
## Activity:
- The community is actively working on both Lucene and Solr, with daily
commits, towards 6.5.0 (and 7) releases
- We pushed out 4 releases since last report
- We solved one a reported security vulnerability
- We are discussing how to more easily monitor private Jira issues (to handle
security problems)
- Discussions are generally flowing in a good shape
- Meetups / conferences around Lucene / Solr:
- Elasticon 2017, March 7-9th, 2017
## PMC changes:
- Currently 41 PMC members.
- Christine Poerschke was added to the PMC on Jan 2nd, 2017
- Mikhail Khludnev was added to the PMC on Jan 2nd, 2017
## Committer base changes:
- Currently 64 committers.
- Cao Mạnh Đạt was added as a committer on Jan 9th, 2017
- Jim Ferenczi was added as a committer on Dec 31st, 2016
- Toke Eskildsen was added as a committer on Feb 14th, 2017
## Releases:
- Lucene 6.4.0 released on Jan 23rd, 2017
- Solr 6.4.0 released on Jan 23rd, 2017
- Lucene 6.4.1 released on Feb 6th, 2017
- Solr 6.4.1 released on Feb 6th, 2017
- PyLucene 6.4.1 release on Feb 14th, 2017.
- Lucene 5.5.4 released on Feb 17th, 2017
- Solr 5.5.4 released on Feb 17th, 2017
- Lucene 6.4.2 released on Mar 7th, 2017
- Solr 6.4.2 released on Mar 7th, 2017
-----------------------------------------
Attachment AI: Report from the Apache Lucene.Net Project [Prescott Nasser]
-----------------------------------------
Attachment AJ: Report from the Apache OFBiz Project [Jacopo Cappellato]
## Description:
Apache OFBiz is an open source enterprise automation software project
## Issues:
there are no issues requiring board attention at this time
## Activity:
- the project made a major design change by splitting OFBiz into two
products: OFBiz framework and plugins. The two products are placed in two
repositories with the intention of having different releases and support
cycles for each. The purpose of this change is to reduce the complexity of
the core product by providing a uniform extension mechanism through
plugins. This allows for more functionality without the need for a
monolithic code-base. More details can be found in this thread [1]
- new features, improvements and bug fixes have been contributed and
integrated into the official code base
- refactoring and stabilization of source code repository is ongoing
- the activity in the mailing list, official blog [2] and Twitter account [3]
is steady with a monthly blog post and frequent tweets
- the PMC has defined and published a policy to govern and limit marketing
messages operated by third parties on the OFBiz lists [4]
- the PMC is addressing specific trademark violations with good results;
## Health report:
the project is stable and active: users questions are answered in the
users list and proposals and design are discussed in the dev list; the PMC
is monitoring the community to identify potential committers and PMC members
## PMC changes:
- Currently 19 PMC members.
- Deepak Dixit was added to the PMC on Fri Feb 24 2017
## Committer base changes:
- Currently 42 committers.
- New committers:
- Swapnil Shah was added as a committer on Mon Feb 13 2017
- James Yong was added as a committer on Fri Mar 03 2017
## Releases:
- Last release was 16.11.01 on Sun Nov 27 2016
## Mailing list activity:
mailing list traffic is relevant as usual
- user@ofbiz.apache.org:
- 933 subscribers (down -7 in the last 3 months):
- 401 emails sent to list (188 in previous quarter)
- dev@ofbiz.apache.org:
- 566 subscribers (down -5 in the last 3 months):
- 775 emails sent to list (1048 in previous quarter)
- notifications@ofbiz.apache.org:
- 80 subscribers (down -2 in the last 3 months):
- 1562 emails sent to list (5718 in previous quarter)
## JIRA activity:
- 109 JIRA tickets created in the last 3 months
- 97 JIRA tickets closed/resolved in the last 3 months
## References
[1] https://s.apache.org/vp5e
[2] https://blogs.apache.org/ofbiz/
[3] https://twitter.com/ApacheOfbiz
[4] http://ofbiz.apache.org/mailing-lists.html#3rd-party-marketing
-----------------------------------------
Attachment AK: Report from the Apache Olingo Project [Christian Amend]
## Description:
Apache Olingo is a Java and JavaScript library that implements the Open
Data Protocol (OData). Apache Olingo serves client and server aspects of
OData. It currently supports OData 2.0 and OData 4.0. The latter is
the OASIS version of the protocol: OASIS Open Data Protocol (OData) TC.
## Olingo Status
Currently Olingo has no issues that would require board attention.
As stated within the last board report a release for the 4.4.0 code line
was scheduled for the end of December. Since there have been no major
feature updates the release was not produced.
This is mainly due to the library being mostly feature complete and the
fact that the new OData 4.01 specification is not yet released. Once the
new specification is out there should be an increase in commits again.
The V2 code line had a 2.0.8 patch release in January. There the work is
in an ongoing maintenance mode. No new features have been introduced. The
changes where mostly bug fixes or convenience methods.
We have seen more JIRA issues with patches lately that follow the guidelines
the PMC specified on the hompage. Those patch contributors could be potential
new committers. I will include an update on this in the next board report.
Overall the Olingo project can still be considered healthy. The number of
users on the mailing list is steadily growing and questions get answered
by other community members.
Questions/Remarks from last report:
mt: It has been a while since the last new PMC member or committer
was added. Does the PMC have any thoughts on growing the
community?
New contributers, committers or PMC members are always welcome. Yet they
should also show a certain knowledge of the specification before they
are given commit rights. I personally could not point out someone like
this for now. Once a person like this appears the PMC will certainly
invite him. In the last board report I gave my personal opinion on
why I think that we see such few people.
idf: Thanks for addressing the previous board report comments.
rb: Thanks so much for explicitly responding to questions from your
last report. This is hugely appreciated.
Thanks from my side as well. This feedback mechanism is very valuable
for me to see what kind of information the board needs.
=== Statistics ===
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ramesh Reddy on Thu Oct 08 2015
## Committer base changes:
- Currently 23 committers.
- No new committers added in the last 3 months
- Last committer addition was Christian Holzer at Thu Feb 26 2015
## Releases:
- Last release was (Java) V4 4.3.0 on Mon Sep 19 2016
## Mailing list activity:
- dev@olingo.apache.org:
- 86 subscribers (up 3 in the last 3 months):
- 217 emails sent to list (304 in previous quarter)
- user@olingo.apache.org:
- 171 subscribers (up 6 in the last 3 months):
- 50 emails sent to list (59 in previous quarter)
## JIRA activity:
- 36 JIRA tickets created in the last 3 months
- 27 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AL: Report from the Apache OODT Project [Tom Barber]
DESCRIPTION
Apache OODT is a software framework as well as 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
- Last release was 1.0 on Wed Jun 29 2016
We resolved 0 issues for this release.
Development on Apache OODT has been pretty quiet over the last 9 months, but
we have recently accepted a large new feature into our code base and are
currently working at incorporating that into the mainline branch so that we
can run a release with the new features in place.
On top of that there has been renewed discussion over the last week or so
over the state of Apache OODT development and what we need to do to move
forward with the 2.0 roadmap. This has been organised and we should be
seeing increased development activity over the coming quarter.
COMMUNITY
Latest committers and PMC members
Radu Maonle(radumanole) on 11th Oct 2015 as committer and PMC member
Last committer and PMC member added on 11th October 2015.
No new users have spoken up on the mailing list recently, but there
has been some interest and patches committed by a volunteer via Jira
so we will be working at bringing them into the project.
ISSUES
There are no issues requiring board attention at this time.
HEALTH REPORT
The project activity is pretty quiet, but there are still on going efforts
in place to help drive wider adoption.
-----------------------------------------
Attachment AM: Report from the Apache OpenNLP Project [Jörn Kottmann]
Apache OpenNLP library is a machine learning based toolkit for the
processing of natural language text.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- There’s been a big surge in project activity since Dec 2016
- Project had a major 1.7.0 release on Dec 30 2016
- There have been 2 minor releases - 1.7.1 and 1.7.2 on
Jan 23, 2017 and Feb 4, 2017 respectively.
- All of the legacy code has been ported over to Java 8
- Team’s presently working towards the next major 1.8.0
release targeted for late March 2017
- The project added 2 new committers and 2 new PMC
members since Dec 2016
- An Apache OpenNLP talk titled - ‘Large Scale Processing of
Unstructured Text’ accepted for Apache Big Data North
America 2017, Miami
- A few abstracts about the project have been submitted for
Berlin Buzzwords 2017.
- Project is presently working on a new project logo,
see https://issues.apache.org/jira/browse/OPENNLP-6
## Health report:
The overall project state significantly improved with a strong increase
in activity and a series of releases in the last three month.
Two new committers joined and existing committers became much more active.
## PMC changes:
- Currently 10 PMC members.
- New PMC members:
- Suneel Marthi was added to the PMC on Thu Jan 19 2017
- Tommaso Teofili was added to the PMC on Thu Jan 19 2017
## Committer base changes:
- Currently 17 committers.
- New committers:
- Daniel Russ was added as a committer on Wed Jan 11 2017
- Suneel Marthi was added as a committer on Sun Dec 25 2016
## Releases:
- 1.7.0 was released on Fri Dec 30 2016
- 1.7.1 was released on Mon Jan 23 2017
- 1.7.2 was released on Sat Feb 04 2017
## Mailing list activity:
The volume of mails on the dev list mainly increased because Github
Pull Request status updates are sent there, otherwise the volume stayed
on a similar level as before.
- users@opennlp.apache.org:
- 421 subscribers (down -7 in the last 3 months):
- 123 emails sent to list (18 in previous quarter)
- dev@opennlp.apache.org:
- 222 subscribers (down -9 in the last 3 months):
- 506 emails sent to list (114 in previous quarter)
- issues@opennlp.apache.org:
- 44 subscribers (down -3 in the last 3 months):
- 859 emails sent to list (155 in previous quarter)
## JIRA activity:
- 110 JIRA tickets created in the last 3 months
- 196 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AN: Report from the Apache OpenWebBeans Project [Mark Struberg]
## Description:
Apache OpenWebBeans is an ALv2-licensed implementations of the
"Contexts and Dependency Injection for the Java EE platform"
specification which is defined as JSR-299 (CDI-1.0) and CDI-1.1
and CDI-1.2 (MR) specifications (JSR-346).
## Issues:
There are no issues requiring board attention at this time.
## Activity:
We released a few maintenance versions plus a small OpenWebBeans
+ Tomcat + CXF + Johnzon based Micro server called Apache Meecrowave.
Aside from that it was a rather unhasty month.
We expect high activity again when finally kicking off the work on
CDI-2.0.
We also supported the HotswapAgent community with creating ha-OWB support.
This happened mostly on IRC. I would have preferred to channel this via
the mailing list, but there was a lot of Questions back%&forth which
was easier to do on IRC. I'll ask the involved guys to also create
a bit of documentation on the mailing list and probably on our web
page.
## Health report:
All fine I think.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jean-Louis Monteiro on Wed May 28 2014
## Committer base changes:
- Currently 19 committers.
- No new committers added in the last 3 months
- Last committer addition was Reinhard Sandtner at Fri Sep 26 2014
## Releases:
- 0.2.0 was released on Mon Jan 09 2017
- 1.7.1 was released on Mon Jan 09 2017
- 1.7.2 was released on Sun Feb 19 2017
- meecrowave-0.3.0 was released on Sun Mar 05 2017
## Mailing list activity:
- dev@openwebbeans.apache.org:
- 71 subscribers (up 1 in the last 3 months):
- 177 emails sent to list (66 in previous quarter)
- user@openwebbeans.apache.org:
- 97 subscribers (up 3 in the last 3 months):
- 18 emails sent to list (9 in previous quarter)
## JIRA activity:
- 28 JIRA tickets created in the last 3 months
- 29 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AO: Report from the Apache Pig Project [Daniel Dai]
Apache Pig is a platform for analyzing large data sets on Hadoop. It provides
a high-level language for expressing data analysis programs, coupled with
infrastructure for evaluating these programs.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- We are weeks away from merging Pig on Spark to trunk
- Preparing Pig 0.16.1 release
## Health report:
- Project activity in the community - mails, commits, jiras, etc is good and
is at the same levels as previous few quarters.
## PMC changes:
- Currently 17 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Koji Noguchi on Thu Aug 04 2016
## Committer base changes:
- Currently 29 committers.
- Liyun Zhang was added as a committer on Thu Dec 15 2016
- Jeff Zhang is reinstated from emeritus to active committer
## Releases:
- Last release was 0.16.0 on Tue Jun 07 2016
## Mailing list activity:
- dev@pig.apache.org:
- 402 subscribers (down -1 in the last 3 months):
- 1252 emails sent to list (1118 in previous quarter)
- user@pig.apache.org:
- 1151 subscribers (down -6 in the last 3 months):
- 37 emails sent to list (36 in previous quarter)
## JIRA activity:
- 104 JIRA tickets created in the last 3 months
- 72 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AP: Report from the Apache Pivot Project [Roger Whitcomb]
Description:
Apache Pivot is an open-source 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.
Issues:
There are no board-level issues at this time.
Activity:
Activity remains low, but there was a bit of an uptick this quarter from
last. A familiar user returned asking about a new release, which has still
not happened, but definitely could happen this quarter.
Health report:
Definitely a "stable" product looking for new blood. I think there are
several directions we could go, but I have no significant time to devote.
I will start some discussions soon on the "dev" list about these ideas.
PMC changes:
- Currently 4 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Niclas Hedhman on Wed Jan 13 2016
Committer base changes:
- Currently 5 active (that is, not emeritus) committers.
- No new changes to the committer base since last report.
- No new committers added in the last 3 months.
- Last committer addition was more than 2 years ago.
Releases:
- Last release was 2.0.4 on Mon May 19 2014
Mailing list activity:
Some development / bug fixing was done this quarter, so a slight uptick
in activity. As noted above, one long-time user returned asking for a
new release; that discussion is ongoing.
- dev@pivot.apache.org:
- 62 subscribers (up 0 in the last 3 months):
- 21 emails sent to list (7 in previous quarter)
- user@pivot.apache.org:
- 174 subscribers (down -1 in the last 3 months):
- 6 emails sent to list (2 in previous quarter)
JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AQ: Report from the Apache Polygene Project [Niclas Hedhman]
## Description:
Apache Polygene is a community based effort exploring Composite Oriented
Programming for domain centric application development.
## Issues:
Apache Zest has successfully transitioned its name to Apache Polygene, and all
interactions with infra team was smooth and went much better than expected. All
tasks related to the name change were captured in
https://issues.apache.org/jira/browse/POLYGENE-195 for future reference.
## Activity:
The name change spurred a lot of code activity, intersected with remaining
issues for the 3.0 release, which has been a bigger chunk of changes than we
were prepared for, hence the delays. But we will get there eventually. With one
of the most capable build systems at ASF now in place, we expect that future
releases will be frequent (by our standards).
We have also been participating in the JDK 9 Outreach program from Oracle,
where we have been asked to test against Early Releases. Our 2000 tests run
well in "legacy mode", but in "jigsaw mode" we are not compatible and have
not enabled the CI build.
## Health report:
The http://reporter.apache.org tool went a little bit bananas after the name
change, and we had some fairly high negative number of health in it. Quite
amusing in itself. Development activity was normal for our project, with a
small, typical slowdown over the holidays.
We are aware that we need to be better at capture the few interested parties
that shows up on occasions and convert them to contributors.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Kent Sølvsten on Tue Sep 22 2015
## Committer base changes:
- Currently 18 committers.
- No new changes to the committer base since last report.
## Releases:
- Last release was apache-zest-java-2.1 on Fri Jul 31 2015
## Mailing list activity:
The two emails on users@ is still our good old friend Rich making
announcements. We don't list that mailing list anymore, as infra suggested
to keep it for symmetry reasons.
Many mails on dev@ lists are Jira tickets related to the name change.
- users@polygene.apache.org:
- 19 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (0 in previous quarter)
- dev@polygene.apache.org:
- 39 subscribers (up 0 in the last 3 months):
- 188 emails sent to list (0 in previous quarter)
## JIRA activity:
- 37 JIRA tickets created in the last 3 months
- 38 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AR: Report from the Apache Portable Runtime (APR) Project [Nick Kew]
The Apache Portable Runtime (APR) project creates and maintains
software libraries that provide a predictable and consistent interface
to underlying platform-specific implementations. The sub-projects
which are released somewhat regularly are APR and APR-util. In
addition, the APR-iconv sub-project is commonly used but has not had
a release since 2007.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- There has been above-average activity (for this project), as reflected
in higher-than-usual traffic on the dev list. This has comprised
several substantive technical discussions, and a brief discussion
on the (legacy) problems of bundling a third-party library (expat).
## Health report:
- Nothing to report, except as above. Health is unchanged.
A new release of APR-1.x is needed to bring a backlog of activity
into a released version, including unbundling expat.
## PMC changes:
- Currently 40 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Christophe Jaillet on Sun Oct 30 2016
## Committer base changes:
- Currently 66 committers.
- No new committers added in the last 3 months
- Last committer addition was Ivan Zhakov at Fri Oct 28 2016
## Releases:
- Last release was 1.5.2 on Wed Apr 29 2015
## Mailing list activity:
- The increased traffic to dev@ is a modest spike in regular activity:
several extended technical discussions. There is no reason
to suppose it predicts future activity levels.
- dev@apr.apache.org:
- 339 subscribers (down -9 in the last 3 months):
- 219 emails sent to list (41 in previous quarter)
- bugs@apr.apache.org:
- 22 subscribers (up 1 in the last 3 months):
- 31 emails sent to list (37 in previous quarter)
## Bugzilla Statistics:
- 3 Bugzilla tickets created in the last 3 months
- 2 Bugzilla tickets resolved in the last 3 months
-----------------------------------------
Attachment AS: Report from the Apache Portals Project [David Sean Taylor]
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.
## Activity:
Apache Portals released 1 release since the last report.
18 January 2017 - Apache Portals Pluto team released Pluto 3.0 to support to
the Portlet Spec 3.0
## Mailing list activity:
Not much activity since the Pluto release. The Pluto team worked on the spec
and release for several years to achieve this major milestone.
## Issues:
We have no board-level issues at this time.
## PMC/Committership changes:
none
Last Added PMC Members:
4 May 2015 - Randy Watler
Last Added Committers:
05 August 2016 Mohd Ahmed Kahn
11 Dec 2014 Martin Scott Nicklous
11 Dec 2014 Neil Griffin
## Releases:
Pluto 3.0.0 - 18 January 2017
Jetspeed 2.3.1- 09 May 2016
-----------------------------------------
Attachment AT: Report from the Apache Ranger Project [Selvamohan Neethiraj]
# Description:
The Ranger project is a framework to enable, monitor and manage comprehensive
data security across the Hadoop platform.
# Issues:
* There are no issues requiring board attention at this time.
# Activity:
* Ranger 0.7.0 release is done and Community is working on 1.0.0 release
activities
* Jira: 105 total, +72(added) -58(resolved) over last 28 days (Feb-2017)
* Git (Source): 83 commits over last 28 days (Feb-2017)
* SVN (Site & Docs): 2 commits over last 28 days (Feb-2017)
# Health report:
* Added five more committers and Expecting more adaption to Apache Ranger
* Scoping for next release is in progress, which may include integration with
other Apache projects
## PMC changes:
- Currently 17 PMC members.
- Last PMC members were added as part of Ranger Graduation on Jan 18, 2017.
- No new PMC members added in the last 1 months
# Committer base changes:
* Currently 22 committers.
* New commmitters:
- Abhay Kulkarni was added as a committer on Mon Feb 13 2017
- Ankita Sinha was added as a committer on Thu Feb 09 2017
- Mehul Parikh was added as a committer on Sun Feb 26 2017
- Pradeep Agrawal was added as a committer on Thu Feb 09 2017
- Sailaja Polavarapu was added as a committer on Mon Feb 13 2017
# Releases:
* 0.7.0 was released on Sun Feb 26 2017
# Mailing list activity:
* dev@ranger.apache.org:
- 856 emails sent to list (in the month of Feb 2017)
* user@ranger.apache.org:
- 48 emails sent to list (in the month of Feb 2017)
* commits@ranger.apache.org:
- 125 emails sent to list (in the month of Feb 2017)
# JIRA activity:
* 72 JIRA tickets created in the month of Feb 2017
* 58 JIRA tickets closed/resolved in the month of Feb 2017
-----------------------------------------
Attachment AU: Report from the Apache Sentry Project [Sravya Tirukkovalur]
-----------------------------------------
Attachment AV: Report from the Apache ServiceMix Project [Krzysztof Sobkowiak]
Apache ServiceMix is a flexible, open-source integration container that
unifies the features and functionality of Apache ActiveMQ, Camel, CXF and
Karaf to provide a complete, enterprise-ready ESB powered by OSGi.
### Issues
There are no outstanding issues requiring board attention.
### Activity
The project focus of Apache ServiceMix is the assembly of the integration
container, the actual functionality is being maintained in related projects
like Apache Karaf, Apache CXF, Apache Camel and Apache ActiveMQ.
During the last period we have released the final release 7.0.0 of ServiceMix
7, which is based on Karaf 4.0.x and includes numerous new features. In the
new period we are going to focus on the further development, stability and
maintenance of ServiceMix 7.
We have also released the version 5.6.3, which was the last scheduled version
of ServiceMix 5, which has been transited to EOL.
We're not expecting too much dependency updates to become available for the
6.1.x, which is currently the only active branch of ServiceMix 6, but we do
plan to keep our release schedule going with the 6.1.x releases.
During the past period we have also released 4 sets of OSGi bundles and a new
release of Depends Maven Plugin.
We plan to keep a steady release schedule and keep up with new fix releases of
our dependency projects.
Our goal for the next months is also to improve the documentation and
examples, which is our still outstanding theme.
### Health report
Activity on the mailing lists and in JIRA is picking up. We had some new
contributions.
### PMC changes
- Currently 22 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Krzysztof Sobkowiak on Sat Jul 05 2014
### Committer base changes
- Currently 50 committers.
- No new committers added in the last 3 months
- Last committer addition was Andrea Cosentino at Sun Mar 13 2016
### Releases
- Apache ServiceMix Bundles 2016.11 on December 09 2016
- Apache ServiceMix Bundles 2016.12 on January 05 2017
- Apache ServiceMix Bundles 2017.01 on January 21 2017
- Apache ServiceMix 7.0.0 on January 21 2017
- Apache ServiceMix Bundles 2017.02 on February 28 2017
- Apache ServiceMix 5.6.3 on March 01 2017
- Apache ServiceMix Depends Maven Plugin 1.4.0 on March 01 2017
### JIRA activity
- 96 JIRA tickets created in the last 3 months
- 95 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AW: Report from the Apache Shiro Project [Les Hazlewood]
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:
- None since last report
Community & Project:
- Mailing list traffic has remained the same.
- Community pull requests to the Shiro doc site have increased, now that
pages includes an 'Edit in Github' link.
- Feature development is planned to continue against master.
- The 1.4.0 Release has been a step toward modernizing Shiro as well as
retain backwards compatibility
Last committer voted in: Andreas Kohn on 15 Jul 2016
Last PMC Member voted in: Andreas Kohn on 26 Jul 2016
-----------------------------------------
Attachment AX: Report from the Apache Sling Project [Carsten Ziegeler]
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
Good activity level overall, contributions from different people continue,
frequent questions on the user list get answered, technical discussions on
developer list/issues. Many improvements and enhancements in various areas.
No new committer (last committers change was in September 2016 with one new
committer elected), no new PMC member (last PMC change was in October 2016
with one new PMC members elected).
Releases
Apache Sling i18n 2.5.8, Apache Sling JCR Installer 3.1.24,
Apache Sling XSS 1.0.18,
Apache Sling HTL JavaScript Use Provider 1.0.20,
Apache Sling Scripting Core 2.0.46,
Apache Sling Health Check Core 1.2.6,
Apache Sling Event 4.2.2,
Apache Sling Distributed Event Admin 1.1.2 (March 8th, 2017)
Apache Sling Content Distribution Core 0.2.6,
Apache Sling Installer Health Checks 1.0.0,
Apache Sling Parent 30 (Mar 6th, 2017)
Apache Sling Scripting HTL Compiler 1.0.8,
Apache Sling Scripting HTL Engine 1.0.32 (March 2nd, 2017)
Apache Sling Commons Classloader 1.4.0,
Apache Sling Commons File System Classloader 1.0.6 (Mar 1st, 2017)
Apache Sling Resource Resolver 1.5.14 (Feb 28th, 2017)
Apache Sling JUnit Tests Teleporter 1.0.12 (Feb 28th, 2017)
Apache Slingstart Maven Plugin 1.7.2 (Feb 28th, 2017)
Apache Sling Installer Core 3.8.6 (Feb 20th, 2017)
Apache Sling Content Distribution Core 0.2.4 (Feb 20th, 2017)
Apache Sling Content Distribution Core 0.2.0 (Feb 14th, 2017)
Apache Sling Servlets GET 2.1.22 (Feb 12th, 2017)
Apache Sling Resource Merger 1.3.2 (Feb 8th, 2017)
Apache Sling DavEx Access to repositories 1.3.8,
Apache Sling Simple WebDAV Access to repositories 2.3.8 (Feb 8th, 2017)
Apache Sling Launchpad Base 2.6.16 (Feb 5th, 2017)
Apache Sling Servlets GET 2.1.20 (Feb 3rd, 2017)
Apache Sling Commons ClassLoader 1.3.8 (Feb 3rd, 2017)
Apache Sling Resource Inventory 1.0.6,
Apache Sling Installer Core 3.8.2 (Jan 31st, 2017)
Apache Sling JSP 2.2.6, Apache Sling Auth Core 1.3.24 (Jan 30th, 2017)
Apache Sling File System Resource Provider 1.2.2,
Maven Sling Plugin 2.1.10, and
Apache Sling Resource Resolver 1.5.12 (Jan 23th, 2017)
Apache Sling Tenant 1.1.0, Apache Sling Scripting HTL Compiler 1.0.6,
Apache Sling Scripting HTL Java Compiler 1.0.8,
Apache Sling Scripting HTL Engine 1.0.30,
Apache Sling HTL Maven Plugin 1.0.6 (Jan 17th, 2017)
Apache Sling JSP 2.2.4 (Jan 16th, 2017)
Apache Sling Resource Resolver 1.5.10 (Jan 13th, 2017)
Apache Sling JUnit Core 1.0.23, Apache Sling JUnit Tests Teleporter 1.0.10,
Apache Sling Testing Clients 1.0.1,
Apache Sling Server Setup Tools 1.0.1,
Apache Sling Testing Rules 1.0.1 (Jan 11th, 2017)
Apache Sling Scripting HTL Compiler 1.0.4,
Apache Sling Scripting HTL Java Compiler 1.0.6,
Apache Sling Scripting HTL Engine 1.0.28,
Apache Sling Scripting HTL Models Use Provider 1.0.6,
Apache Sling Scripting HTL JS Use Provider 1.0.18,
Apache Sling HTL Maven Plugin 1.0.4 (January 9th, 2017)
Apache Sling Testing Hamcrest 1.0.2 (January 7th, 2017)
Apache Sling Testing ResourceResolver Mock 1.1.16 (December 27th, 2016)
Apache Sling Servlets Resolver 2.4.10,
Apache Sling File System Classloader 1.0.4 and
Apache Sling Installer Console 1.0.2 (December 24th, 2016)
Apache Sling Resource Resolver 1.5.8, Apache Sling JCR Resource 2.9.2 and
Apache Sling Slingshot Sample 0.8.0 (December 23rd, 2016)
Apache Sling Mock 2.2.4, Apache Sling Mock 1.9.4, Apache Sling JUnit Core 1.0.22,
Apache Sling Models API 1.3.2,
Apache Sling Models Impl 1.3.8 and
Apache Sling Service User Mapper 1.2.4 (December 22th, 2016)
Apache Sling JCR Base 3.0.0 (December 20th, 2016)
Apache Sling Dynamic Include 3.0.0 (December 20th, 2016)
Apache Sling i18n 2.5.6, Apache Sling JCR RepoInit module 1.1.2 (December 19th, 2016)
Apache Sling API 2.16.2 and Slingstart Maven Plugin 1.7.0 (December 18th, 2016)
Apache Sling JCR Resource 2.9.0, Apache Sling Scripting JSP 2.2.2,
Apache Sling Scripting Java 2.1.2,
Apache Sling Provisioning Model 1.8.0,
Apache Sling Testing JCR Mock 1.2.0,
Apache Sling OSGi Mock 2.2.2, Apache Sling OSGi Mock 1.9.2,
Apache Sling Sling Mock 2.2.2, Apache Sling Sling Mock 1.9.2,
Apache Sling JUnit Core 1.0.20, Apache Sling Context-Aware Configuration API 1.1.0,
Apache Sling Context-Aware Configuration SPI 1.2.0,
Apache Sling Context-Aware Configuration Impl 1.2.0,
Apache Sling Context-Aware Configuration bnd Plugin 1.0.2,
Apache Sling Context-Aware Configuration Mock Plugin 1.0.0 (December 16th, 2016)
Apache Sling Scripting API 2.1.12,
Apache Sling Scripting Core 2.0.44 (December 15th, 2016)
Apache Sling JCR Installer 3.1.22 (December 13th, 2016)
Apache Sling Commons Metrics 1.2.0 (December 13th, 2016)
Documentation and infrastructure
Nothing to report
Project Branding is tracked in SLING-2696.
-----------------------------------------
Attachment AY: Report from the Apache SpamAssassin Project [Sidney Markowitz]
Apache SpamAssassin report to board for March 2017
SpamAssassin is a mail filter to identify spam. The project provides a
framework/engine and regular rule updates that reflect the changing nature of
spam email seen in the wild. Updated rules are generated through a combination
of hand crafted contributions and automated processing of spam and anonymized
processed non-spam that are contributed by volunteers.
Health report:
The status of the project is basically unchanged from the last report, a
mature project that is not in rapid development. The users mailing list is
active with user level questions and responses from people with expertise in
SpamAssassin. There is moderate activity on the developer mailing list and
Bugzilla. Questions are answered in a timely fashion and bug reports are being
addressed.
We have had a modest increase in the number of volunteers who submit sample
mail to our mass-check rule generation system.
Issues:
Two computers that the project has been using to support our mass-check rule
generation and updates are scheduled to be shut down soon (mid-March). Kevin
McGrail (KAM) has been working on getting the replacement VM ready and moving
data and processes to it. We expect a report from him soon on the
de-provisioning of the old machines.
Releases:
KAM has volunteered to be release manager for SpamAssassin 3.4.2. We will
start the formal release process after he has completed the machine migration
and de-provisioning that we mentioned in the previous section.
Committer/PMC changes:
There were no changes in membership in committers or PMC in the last quarter.
However we are very pleased to welcome Kevin McGrail back to active
participation in the project.
-----------------------------------------
Attachment AZ: Report from the Apache Stanbol Project [Fabian Christ]
-----------------------------------------
Attachment BA: Report from the Apache Storm Project [P. Taylor Goetz]
## Description:
- Apache Storm is a distributed real-time computation system.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The community continues to advance toward a 1.1.0 release. That release
has been delayed due to a number of necessary bug fixes and packaging
changes aimed at reducing the file size of the distribution. We expect
the packaging changes to be completed soon and followed by a release.
- Discussions regarding a roadmap for the 2.0 release are beginning and are
expected to pick up once the 1.1.0 release is out.
- Developer interest in the Apache Beam runner for Storm seems to have
waned a bit. There is interest in a Storm runner from the Beam community,
so we may persue moving that effort to the Beam community similar to how
the Flink and Apex runners were developed.
- There are a number of presentations covering Storm at the upcoming
Hadoop/DataWorks Summit Munich in April.
## Health report:
- Overall the project continues to be healthy and we are seeing new
faces show up and contribute.
- Activity on the dev@ list has picked up as the community works toward the
1.1.0 release.
## PMC changes:
- Currently 33 PMC members.
- Hugo da Cruz Louro was added to the PMC on Thu Mar 9 2016
## Committer base changes:
- Currently 34 committers.
- Hugo da Cruz Louro was added as a committer on Fri Feb 24 2017
## Releases:
- 1.0.3 was released on Tue Feb 14 2017
-----------------------------------------
Attachment BB: Report from the Apache Synapse Project [Isuru Udana]
[REPORT] Synapse - March 2017
Apache Synapse is a high performance, flexible, lightweight
Enterprise Service Bus (ESB) and a mediation framework.
Community
=========
The last committer was added in Feb 2017:
Prabath Ariyarathna (prabathar)
As indicated in the last report, we managed the get the long awaited Synapse
3.0.0 release out in December 2016.
It was after nearly five years (previous release was done in Jan 2012).
Several new contributors helped us a lot for this release. Two of them
(Vanjikumaran Shivajothy and Prabath Ariyarathna) were onboarded as
committers.
Releases
========
1 release since the last report - Synapse 3.0.0 released on December 2016 .
Board Issues
============
None identified.
-----------------------------------------
Attachment BC: Report from the Apache Tajo Project [Hyunsik Choi]
-----------------------------------------
Attachment BD: Report from the Apache Tiles Project [Mick Semb Wever]
## Description:
Apache Tiles is a free open-sourced templating framework for Java
applications. Based upon the Composite pattern it is built to simplify the
development of user interfaces.
## Activity:
Apache Tiles remains a stable but low traffic project.
This quarter there has been a little more public activity. A couple of
small fixes. A couple of improvements and upgrades. And more community
involvement. No releases were cut, but one is now warranted.
Responsiveness on the ML dropped this quarter.
## Health report:
There are currently two responsive PMC, other PMC help out with votes when
needed. Everyone is aware of the how little momentum the project has, but
it does not feel abandoned by members, nor not in use by the public. There
is room to add another committer to the project.
## Issues
Further effort is required to increase health to the project. Previous
board report received feedback on what such effort might be. This remains
unaddressed by the community, although a new individual is contributing
patches.
Past ideas remain: from including the StackExchange traffic, following up
on some of the development ideas, to publicity and engagement with other
communities that have more momentum in the UI space.
-----------------------------------------
Attachment BE: Report from the Apache Tomcat Project [Mladen Turk]
## Description:
- A Java Servlet, JavaServer Pages, Java WebSocket and Java
Unified Expression language specifications implementation.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Continued healthy activity across multiple components and
responsiveness on both dev and user lists.
- TomcatCon has been organised to run along side ApacheCon
with 3 days of content in a single track dedicated to Apache Tomcat.
The content has just been agreed. Next step marketing.
## PMC changes:
- Currently 24 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Felix Schumacher on Mon Oct 26 2015
## Committer base changes:
- Currently 43 committers.
- Emmanuel Bourg was added as a committer on Fri Jan 20 2017
## Releases:
- Apache Tomcat 7.0.75 was released on Tue Jan 24 2017
- Apache Tomcat 8.0.41 was released on Tue Jan 24 2017
- Apache Tomcat 8.5.11 was released on Mon Jan 16 2017
- Apache Tomcat 9.0.0.M17 was released on Mon Jan 16 2017
## Trademark:
- No new trademark issues in the last 3 months
and there are currently no outstanding trademark issues that the
Apache Tomcat PMC is working on.
- Detailed history is available at:
https://svn.apache.org/repos/private/pmc/tomcat/trademark-status.txt
## Security:
- Detailed status:
http://tomcat.apache.org/security.html
- Important: Information Disclosure CVE-2016-8745
A bug in the error handling of the send file code for the NIO HTTP
connector resulted in the current Processor object being added to
the Processor cache multiple times.
Affects: Apache Tomcat 7.0.0 to 7.0.73 and 8.0.0.RC1 to 8.0.39
-----------------------------------------
Attachment BF: Report from the Apache Twill Project [Terence Yim]
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Add a new committer, Martin Serrano (serrano@)
## Health report:
- Addition of new committer
- Made one release since Dec 2016
## PMC changes:
- Currently 6 PMC members
- Last PMC addition was Henry Saputra on August 4, 2015
## Committer base changes:
- Currently 8 committers and 22 contributors
- One new committer added in the last 3 months
- No new contributor added in the last 3 months
- Last committer addition was Martin Serrano on Feb 24, 2017
- Last contributor addition was Chengfeng Mao on November 18, 2016
## Releases:
- Last release was release 0.10.0 on February 23, 2017
## Mailing list activity:
- dev@twill.apache.org:
- 67 subscribers
- 601 emails sent to the list in past three months (424 in last report)
- commits@twill.apache.org:
- 18 subscribers
- 134 emails sent to the list in past three months (99 in last report)
## JIRA activity:
- 4 new JIRA tickets created in the last month
- 2 JIRA tickets resolved in the last month
-----------------------------------------
Attachment BG: Report from the Apache UIMA Project [Marshall Schor]
Board report for Apache UIMA, for March 2017.
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.
Dates:
23 Feb 2017 (new) last release - Apache UIMA DUCC 2.2.0
03 May 2016 (no change) last PMC addition
24 Jul 2015 (no change) last Committer addition
Releases:
23 Feb 2017 Apache UIMA DUCC 2.2.0
30 Jan 2017 Apache UIMA Java SDK 3.0.0-alpha
Alpha release of significant new internal
implementation of core UIMA Java framework
15 Dec 2016 Apache UIMA Asynchronous Scaleout (UIMA-AS) 2.9.0
many upgrades, improvements, fixes
Other Activity:
Two release candidate votes are pending.
Community:
Response to board question for previous report:
idf: No new committer for over a year - any candidates?
We did reach out in one project to see if a contributor
might be interested, but got a not-at-this-time response.
We are watching some other people who have started with
some initial contributions.
The community continues to be moderately active.
Actively working on boosting prioritization for work on
UIMA CPP; this (sub)project has had pending fixes that haven't been
applied and needs a new release.
Issues:
No Board level issues at this time.
-----------------------------------------
Attachment BH: Report from the Apache VCL Project [Andy Kurth]
## Description:
VCL is a modular cloud computing platform which dynamically provisions and
brokers remote access to compute resources including virtual machines,
bare-metal computers, and resources in other cloud platforms. A self-service
web portal is used to request resources and for administration. VCL became a
TLP on June 20, 2012.
## Issues:
There are no issues requiring board attention at this time
## Activity:
- Code for the upcoming release is just about complete.
- The most significant new feature is support for automatically joining an
Active Directory domain when a Windows image is loaded. This is complete
but needs a bit of testing.
- Work continues on documentation. We are starting fresh using a VCLDOCS
Confluence space created long ago but never really used. This is making it
easier to keep track of what has been reworked rather than trying to
update and sort out all of the old, disorganized pages. Pages will be
moved en masse once enough content has been updated and organized to
surpass the old docs.
## Health report:
Overall, the health of the project is fair but could be improved. I think
there are a few factors that have limited the appeal of potential
contributors:
- Poor documentation. Hopefully our updated documentation will increase
interest. This alone, however, won't likely make a huge difference. There
are other projects with poor documentation that draw a respectable amount
of development contributions.
- Staleness. The codebase does not use any of the modern frameworks of the
month. It's basicly old fashioned PHP and Perl. There are some JavaScript
components, but these mainly use the Dojo Toolkit which seems to be losing
popularity. We could think about a significant rewrite and use things such
as Angular, Laravel, etc.
- Marketing. The project began at NC State University and still has a strong
NCSU relation. Years ago, leaders at NCSU along with colleagues at IBM did
a great job spreading the word about VCL to other universities and
contacts. Many of these people have either retired or moved on to other
roles. Regardless, NCSU's past marketing is appreciated but this is the
PMC's responsibility. We need to work to think of ways to make the project
more attractive to contributors and to communicate it. Someone recently
mentioned VCL in a thread on a higher education list hosted by Stanford. I
have alerts set up for such occurances and responded with additional
information. We should do a better job monitoring other lists and venues
including other ASF projects for opportunities. VCL also integrates with a
number of other technologies. There may be opportunites to have the
project included on other website's such as the "Applications using
libvirt" page. [1] This will be discussed by the PMC members.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Aaron Coburn on Tue Jun 19 2012
## Committer base changes:
- Currently 8 committers.
- No new committers added in the last 3 months
- Last committer addition was Young Hyun Oh at Sun Dec 08 2013
## Releases:
- Last release was 2.4.2 on Wed Apr 15 2015
## Mailing list activity:
- Mailing list traffic is essentially flat. Dev list traffic increase is
due to the final tasks to prepare the release. User list traffic is down.
This could partially be due to the holidays.
- dev@vcl.apache.org:
- 128 subscribers (down -2 in the last 3 months):
- 109 emails sent to list (77 in previous quarter)
- user@vcl.apache.org:
- 169 subscribers (up 1 in the last 3 months):
- 12 emails sent to list (20 in previous quarter)
## JIRA activity:
- 18 JIRA tickets created in the last 3 months
- 8 JIRA tickets closed/resolved in the last 3 months
[1] https://libvirt.org/apps.html
-----------------------------------------
Attachment BI: Report from the Apache Wicket Project [Martijn Dashorst]
Report from the Apache Wicket project [Martijn Dashorst]
Apache Wicket is an open source Java component oriented web application
framework.
## Noteworthy items:
- Andrea del Bene is now a release manager
- 8.0 inches closer to a final release
- CVE-2016-6793 Apache Wicket deserialization vulnerability solved
## Releases this quarter
We have issued the following releases: 1.5.17, 7.6.0, 6.26.0, 8.0.0-M3 and
8.0.0-M4.
## State of the project
The project has gained a new release manager: Andrea del Bene who has
performed the last couple of releases since ApacheCon EU.
Discussions regarding our 8.0 release are ongoing, respectfully and based on
technical exchanges on the dev list. While no date has been set for a final
8.0 release, it seems we are getting closer to do so.
We keep an eye on our community for new committers, but as the project is
quite stable not many new developers are joining the ranks.
## PMC changes:
- Currently 29 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was François Meillet on Mon Jun 29 2015
## Committer base changes:
- Currently 30 committers.
- No new committers added in the last 3 months
- Last committer addition was Francois Meillet at Fri Jun 26 2015
-----------------------------------------
Attachment BJ: Report from the Apache Wink Project [Luciano Resende]
-----------------------------------------
Attachment BK: Report from the Apache Xerces Project [Michael Glavassevich]
-----------------------------------------
Attachment BL: Report from the Apache Yetus Project [Sean Busbey]
Apache Yetus provides libraries and tools that enable contribution and
release processes for software projects.
ISSUES FOR THE BOARD'S ATTENTION
Last report we were asked if we had identified candidates for
committers and PMC additions, and specifically if we were being too
conservative. The PMC has slowly been discussing candidates; we are
probably still being too conservative. As chair I'll be pinging on
this issue again this month.
RELEASES
The community released version 0.4.0 on January 9th, 2017.
ACTIVITY
No new PMC additions in this period; our last PMC addition was Ajay
Yadava on Dec 1st, 2016.
No new committer additions in this period; our last committer
additions were Andrew Wang and Ajay Yadava on Sep 20th, 2016.
The community has had roughly the same low level of activity during
this period as last. Working through the 0.4.0 release revealed some
gaps in our process documentation that caused us to lose some energy
that could have been put towards being responsive to our contributors.
As previously mentioned, I'm looking to rotate the PMC chair some time
in the next reporting period.
STATS
- Currently 8 PMC members
- Currently 10 committers
- dev list has 41 subscribers (flat from previous period)
- 22 JIRA tickets created in the last 3 months
- 9 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BM: Report from the Apache ZooKeeper Project [Flavio Junqueira]
## Description: Apache ZooKeeper is a system for distributed coordination. It
enables distributed systems to implement a variety of primitives and
mechanisms that are critical for them to function, e.g., distributed locks,
master election, group membership, and configuration.
## Issues: There are no issues requiring board attention at this time.
## Activity:
The community has been very active on the discussion of issues as we can
observe by the number of messages sent to the dev list. This number is
actually larger compared to the previous period.
We have also been receiving a few security reports over time (one in the last
period) and have needed to act upon them. Our community is still a bit
immature with respect to dealing with security, which mainly stems from the
fact that Apache ZooKeeper has traditionally assumed that it runs behind
secure boundaries, and only recently security has become of greater interest
to our users. We are making progress on learning how to deal with such
security issues and reports, though.
As for releases, we have been discussing two releases for a while, 3.4.10 and
3.5.3, but unfortunately, they didn’t happen in this period. The PMC expects
at least one release to happen in the upcoming period.
## Health report:
We have added two new committers and one new PMC member. The dev activity is
high, while the user activity is steady. We have not had high activity on the
user list in the recent past, mainly because of the nature of the project.
Users of Apache ZooKeeper tend to be interested in its internals and questions
are often sent directly to dev.
## PMC changes:
- Currently 12 PMC members.
- Rakesh Radhakrishnan was added to the PMC on Fri Mar 03 2017
## Committer base changes:
- Currently 21 committers.
- New commmitters:
- Mohammad Arshad was added as a committer on Mon Jan 23 2017
- Michael Han was added as a committer on Tue Dec 20 2016
## Releases:
- Last release was 3.4.9 on Sat Sep 03 2016
## Mailing list activity:
The dev list activity has increased compared to the last period. There is no
special reason for it to happen other than interest of contributors and
committers being more available to interact with the community. As we
mentioned above, the traffic of the user list has been steady for quite a
while. Members of the Apache ZooKeeper community tend to ask questions
directly on the dev list as they are often interested in the internals and
contributing as well.
- dev@zookeeper.apache.org:
- 504 subscribers (up 4 in the last 3 months):
- 3842 emails sent to list (3322 in previous quarter)
- user@zookeeper.apache.org:
- 1189 subscribers (up 6 in the last 3 months):
- 187 emails sent to list (185 in previous quarter)
## JIRA activity:
- 68 JIRA tickets created in the last 3 months
- 52 JIRA tickets closed/resolved in the last 3 months
------------------------------------------------------
End of minutes for the March 15, 2017 board meeting.
Index