Index
Links: 2017 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
August 16, 2017
1. Call to order
The meeting was scheduled for 10:30am Pacific and began at 10:36
when a sufficient attendance to constitute a quorum was
recognized by the chairman.
Other Time Zones:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=2017-08-16T10:30:00&msg=ASF+Board+Meeting&p1=137
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
Ted Dunning
Jim Jagielski
Chris Mattmann
Brett Porter
Directors Absent:
Phil Steitz
Mark Thomas
Executive Officers Present:
Ross Gardler
Kevin A. McGrail
Sam Ruby
Craig L Russell
Executive Officers Absent:
Ulrich Stärk
Guests:
Daniel Gruno
Greg Stein
Myrle Krantz
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 July 19, 2017
See: board_minutes_2017_07_19.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Brett]
I spent some time this month writing up some details about scripts and
running meetings that the Chairman needs, and spoke with Phil about
transitioning over to him. I'll be working with him over the next
couple of weeks to ensure everything is handed over, as I'll be
travelling for two weeks at the beginning of September.
I still need to send some follow up material from our face to face in
that time as well.
I'll be speaking at DataWorks Summit in Sydney on the Apache Way in
September.
Thanks for having me as chair for the last 4 years, it's been great!
B. President [Sam]
My current priorities: EA/TAC/Conferences
Items requiring board attention:
Fundraising is planning to revisit the idea of Directed Sponsorships.
Perhaps we can have a brief discussion on the topic at the board
meeting, take the discussion to the fundraising mailing list, and
return back to the board at a later date with a complete proposal?
- - -
Financially, we continue to be on track. FY18 looks great, but again I
remind everybody that the amount we are projecting to be over almost
exactly matches the amount that we missed in FY17 due to timing issues.
It has taken a lot of work to get us here (and both Sally and Virtual
have been instrumental). We continue to find low hanging fruit in terms
of unbilled sponsors; but at some point further growth in revenue is
going to depend on the harder (and longer lead time) problem of
attracting new sponsors.
Quiet (in terms of questions) but busy (in terms of renewals, etc.)
month for Brand Management. Lack of volunteers is an ongoing issue.
Seeing if we can utilize our EA better remains on my todo list.
Additionally, please see Attachments 1 through 7.
C. Treasurer [Ulrich]
Virtual Report:
Here is a brief summary of the Foundation’s performance for the first
three months of FY18.
Cash on July 31th 2017 was $1,789K, which is down $53K from last
month’s ending balance (Jun 17) of $1,842K, due to the timing of
Sponsor pmts vs payables. The July 2017 cash balance is up $35K from
the July 2016 month end balance of $1,754K. The June 2017 ending cash
balance of $1,789K represents a cash reserve of 15.4 months based on
the FY18 Cash forecast average monthly spending of $116.5K/month. The
ASF reserve continues to be very healthy for an organization of ASF’s
size, with an FY18 YE estimate of 13.3 month’s cash reserve.
Regarding the YTD Cash P&L, we continue to have a very strong showing
against our FY18 Budget. Revenue YTD is $604.4K vs a budget of
$240.2K. This was due to the Platinum Sponsor payments for Google,
Comcast (upgraded to Platinum from Gold) and Microsoft which had been
forecasted to arrive later in the year. This has us for revenue,
$364.3K ahead of bud through July 2017. So with the $604.4K of
Sponsor revenue received so far in the first three months of FY18 we
are more than 55% to our budgeted Sponsor revenue goal of $1,084K for
FY18. We are also now forecasting with the remaining sponsorships,
and the Coinbase base revenue to be about $176.8K ahead of the $1,084K
FY18 budget, if the sponsors that were budgeted for the last 9 months
of FY18 all renew and pay.
YTD expenses are under by $23.9K. Infra is over by $4K and the other
depts. combined are under by $27.9K. I would caution that we are only
three months into the current fiscal year so it is still early yet.
In our forecast we have pushed some expenses that have not been spent
yet, “ahead” in the year and we will follow up with dept heads
accordingly.
With regard to Net Income (NI), YTD for FY18 the ASF finished with a
positive $273.4K NI vs a budgeted negative $114.7K NI or $388.1K ahead
of Budget for the first three months of FY18. With the forecasted
revenue ahead of budget due to the Pivotal and Microsoft FY 17
payments as well as the Coinbase funds coming in FY18 and expenses at
$23.9K under Budget at this point we are estimating a $31.7K positive
NI for FY18 vs a budgeted NI loss of $167.8K. While it is a fantastic
start and we should very pleased with all the hard work that everyone
has put into the FY so far, it is still a bit early in the FY at this
point and this forecast could change if we take our eye off the ball.
KAM NOTE: Discussed with Tom and this report and the financials
reflects accrual for payments authorized in July but paid Aug 2
because of the approval process.
Current Balances:
Citizens Money Market 1,469,636.70
Citizens Checking 316,730.00
Paypal - ASF 2,308.82
Total Checking/Savings 1,788,675.52
Jul-17 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 2,458.67 2,657.88 -199.21
Sponsorship Program 45,000.00 70,000.00 -25,000.00
Programs Income 0.00 0.00 0.00
Other Income 482.31 0.00 482.31
Interest Income 623.83 292.92 330.91
Total Income 48,564.81 72,950.80 -24,385.99
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 74,937.67 74,451.17 486.50
Sponsorship Program 2,000.00 5,000.00 -3,000.00
Programs Expense 0.00 0.00 0.00
Publicity 10,318.00 28,625.00 -18,307.00
Brand Management 0.00 7,416.67 -7,416.67
Conferences 240.55 0.00 240.55
Travel Assistance Committee 0.00 0.00 0.00
Tax and Audit 0.00 0.00 0.00
Treasury Services 3,350.00 3,500.00 -150.00
General & Administrative 11,290.22 12,672.74 -1,382.52
Total Expense 102,136.44 131,665.58 -29,529.14
Net Income -53,571.63 -58,714.78 5,143.15
Cash Proof 1,842,247.15
1,788,675.52
YTD 2018 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 28,330.76 8,025.24 20,305.52
Sponsorship Program 569,612.08 231,250.00 338,362.08
Programs Income 0.00 0.00 0.00
Other Income 4,634.17 0.00 4,634.17
Interest Income 1,849.93 878.76 971.17
Total Income 604,426.94 240,154.00 364,272.94
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 222,210.15 218,150.78 4,059.37
Sponsorship Program 6,747.23 10,250.00 -3,502.77
Programs Expense 0.00 0.00 0.00
Publicity 49,835.61 54,625.00 -4,789.39
Brand Management 7,479.05 22,250.01 -14,770.96
Conferences 4,987.62 4,000.00 987.62
Travel Assistance Committee 2,191.81 5,000.00 -2,808.19
Tax and Audit 0.00 0.00 0.00
Treasury Services 9,800.00 9,950.00 -150.00
General & Administrative 27,758.10 30,656.12 -2,898.02
Total Expense 331,009.57 354,881.91 -23,872.34
Net Income 273,417.37 -114,727.91 388,145.28
Asst Treasurer Report:
- A few more bitcoin monies donated. Was able to easily convert to
cash. $1005 confirmed received yesterday.
- DMCA Filing for ASF Agent is Done.
- Requested an Engagement Letter to Move forward with the Audit. This
will be for FY17 because I forgot we are already in FY18 as discussed
at the last board meeting. Thanks to Tom for reminding me.
- Payoneer Signup was completed by Uli for GSOC
- Benevity continues to pay dividends and we got an $800 donation
unsolicited
- CDARS - Virtual has gotten the information and it is perfect. See
https://www.youtube.com/watch?v=PEiVU1Kyl14 for more info about CDARS.
Uli, Tom & I will confirm an appropriate amount to leave in
operational checking and the amounts to tie up in CDARS but they can
be done at very short, revolving intervals so liquidity can be
maintained.
- Greg Stein identified some oddities with Spare Hardware cost center.
Virtual is working with him to fix how it’s recorded.
- We are renewing the NPO Management Liability policy currently in
force. This covers Directors and Officers Insurance and Employment
Practices.
- Credit Card with a lower foreign transaction fee - Lynsey got
Citizens to lower the Foreign fees on the current card, and is working
on changing the current cards to Small Business cards in the next
month or so. UPDATE: Citizens is now waiving all the foreign fees
and that they will be crediting April-July on the Sept statement.
Kudos to Lynsey.
Previously Reported Items Still Tracking:
- Contribution Language for Car Donations - No update
- Payment Privacy changes to move away from Dropbox, etc. Virtual will
be documenting what they do now which is working - No update since
last meeting.
- Network for Good - Missing a $125 check - Will ask for a reissue. No
Update
D. Secretary [Craig]
I am looking to improve the IP Clearance process documentation which
has raised a few questions recently.
In July, 84 iclas and one grant were received and filed.
E. Executive Vice President [Ross]
Infrastructure
In process of renewing our binary signing service with Symantec,
requires a new "authentication" of the business. This has highlighted
that while our D&B records reflect our new Wakefield postal address,
but many other third-party records are out of date. If anyone sees an
incorrect listing please notify our EA to have them corrected.
Gitbox usage is being expanded to more users. Edge cases still being
discovered so mass migration is still a long term, rather than short
term, goal.
Marketing and Publicity
Starting to see immediate results from having VP Marketing tasked with
assisting in sponsorship activities.
Business as usual with respect to press and analyst engagements.
Conferences
We have a booth at All Things Open. Conversations are ongoing with
respect to involvement in other events / meetups. Conversations also
ongoing with respect to alternative conference producer arrangements.
TAC
Nothing to report
F. Vice Chairman [Phil]
Nothing to report qua Vice Chair this month.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Mark]
See Attachment 8
B. Apache Legal Affairs Committee [Chris Mattmann]
See Attachment 9
C. Apache Security Team Project [Mark J. Cox / Bertrand]
See Attachment 10
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# ACE [bp]
# Airavata [bp]
# Ambari [bp]
# Axis [bp]
# Community Development [bp]
# Giraph [bp]
# Hama [bp]
# Helix [bp]
# Ignite [mt]
# Incubator [bp]
# Libcloud [mt]
# MADlib [bd]
# MINA [bp]
# Marmotta [bp]
# Oltu [bp]
# REEF [mt]
# Serf [bp]
# Usergrid [bp]
# Xalan [bp]
# Xerces [bp]
A. Apache ACE Project [Marcel Offermans / Chris]
No report was submitted.
B. Apache Airavata Project [Suresh Marru / Ted]
No report was submitted.
C. Apache Ambari Project [Yusaku Sako / Brett]
No report was submitted.
D. Apache Ant Project [Jan Matèrne / Phil]
See Attachment D
E. Apache Atlas Project [Madhan Neethiraj / Jim]
See Attachment E
F. Apache Axis Project [Deepal Jayasinghe / Rich]
No report was submitted.
@Shane: work with the Axis community to help with governance
issues
G. Apache Bloodhound Project [Gary Martin / Shane]
See Attachment G
H. Apache BookKeeper Project [Sijie Guo / Shane]
See Attachment H
I. Apache Brooklyn Project [Richard Downer / Mark]
See Attachment I
J. Apache Buildr Project [Antoine Toulme / Brett]
See Attachment J
K. Apache Camel Project [Christian Mueller / Jim]
See Attachment K
L. Apache Cassandra Project [Nate McCall / Phil]
See Attachment L
M. Apache Clerezza Project [Hasan Hasan / Rich]
See Attachment M
N. Apache Cocoon Project [Cédric Damioli / Bertrand]
See Attachment N
O. Apache Community Development Project [Ulrich Stärk / Ted]
No report was submitted.
@Ted: pursue a report for Community Development; look at
previous examples of good reports; look at the blog post for
ideas
P. Apache CouchDB Project [Jan Lehnardt / Chris]
See Attachment P
Q. Apache Creadur Project [Brian E Fox / Brett]
See Attachment Q
R. Apache DeltaSpike Project [Thomas Andraschko / Jim]
See Attachment R
S. Apache Directory Project [Stefan Seelmann / Ted]
See Attachment S
T. Apache Drill Project [Aman Sinha / Bertrand]
See Attachment T
U. Apache Empire-db Project [Rainer Döbele / Shane]
See Attachment U
V. Apache Fineract Project [Myrle Krantz / Chris]
See Attachment V
W. Apache Flume Project [Hari Shreedharan / Phil]
See Attachment W
X. Apache Fluo Project [Keith Turner / Rich]
See Attachment X
Y. Apache Forrest Project [David Crossley / Mark]
See Attachment Y
Z. Apache Geode Project [Mark Bretl / Ted]
See Attachment Z
AA. Apache Giraph Project [Avery Ching / Chris]
See Attachment AA
@Chris: follow up with PMC: critical bugs fixes need release
AB. Apache Gora Project [Lewis John McGibbney / Bertrand]
See Attachment AB
AC. Apache Groovy Project [Guillaume Laforge / Phil]
See Attachment AC
AD. Apache Hama Project [Edward J. Yoon / Rich]
No report was submitted.
@Rich: follow up to see if the project is still viable
AE. Apache Helix Project [Kishore Gopalakrishna / Brett]
See Attachment AE
@Brett: pursue a better report for next time
AF. Apache HTTP Server Project [Daniel Gruno / Mark]
See Attachment AF
AG. Apache HttpComponents Project [Asankha Perera / Shane]
See Attachment AG
AH. Apache Ignite Project [Denis Magda / Jim]
See Attachment AH
@Jim: follow up to document the resolution of ignite.run issue
next board report
AI. Apache Incubator Project [John D. Ament / Mark]
See Attachment AI
@Brett: discuss board comments with incubator pmc
AJ. Apache jUDDI Project [Alex O'Ree / Bertrand]
See Attachment AJ
AK. Apache Kafka Project [Jun Rao / Ted]
See Attachment AK
AL. Apache Knox Project [Larry McCay / Rich]
See Attachment AL
AM. Apache Kylin Project [Luke Han / Shane]
See Attachment AM
AN. Apache Lens Project [Amareshwari Sriramadasu / Phil]
See Attachment AN
AO. Apache Libcloud Project [Tomaž Muraus / Brett]
See Attachment AO
@Brett: follow up on board comments for next report
AP. Apache Logging Services Project [Ralph Goers / Chris]
See Attachment AP
AQ. Apache MADlib Project [Aaron Feng / Jim]
See Attachment AQ
@Jim: follow up with trademark assignment issue
AR. Apache ManifoldCF Project [Karl Wright / Shane]
See Attachment AR
AS. Apache Marmotta Project [Jakob Frank / Rich]
No report was submitted.
AT. Apache MetaModel Project [Kasper Sørensen / Phil]
See Attachment AT
AU. Apache MINA Project [Jean-François Maury / Brett]
No report was submitted.
@Brett: pursue a report for MINA
AV. Apache Mynewt Project [Justin Mclean / Bertrand]
See Attachment AV
AW. Apache Oltu Project [Antonio Sanso / Mark]
No report was submitted.
@Mark: pursue a report for Oltu
AX. Apache Oozie Project [Robert Kanter / Chris]
See Attachment AX
AY. Apache Open Climate Workbench Project [Michael James Joyce / Ted]
See Attachment AY
AZ. Apache Perl Project [Philippe M. Chiasson / Jim]
No report was submitted.
BA. Apache Phoenix Project [James R. Taylor / Ted]
See Attachment BA
BB. Apache POI Project [Dominik Stadler / Phil]
See Attachment BB
BC. Apache Qpid Project [Robbie Gemmell / Brett]
See Attachment BC
BD. Apache REEF Project [Byung-Gon Chun / Shane]
See Attachment BD
@Shane: follow up with PMC: why no new PMC members
BE. Apache River Project [Patricia Shanahan / Jim]
See Attachment BE
BF. Apache Roller Project [Dave Johnson / Chris]
See Attachment BF
BG. Apache Santuario Project [Colm O hEigeartaigh / Bertrand]
See Attachment BG
BH. Apache Serf Project [Bert Huijben / Rich]
No report was submitted.
@Rich: pursue a better report for Serf
BI. Apache SIS Project [Martin Desruisseaux / Mark]
See Attachment BI
BJ. Apache Spark Project [Matei Zaharia / Rich]
See Attachment BJ
BK. Apache Streams Project [Stephen D Blackmon / Brett]
See Attachment BK
BL. Apache Subversion Project [Evgeny Kotkov / Jim]
See Attachment BL
BM. Apache Syncope Project [Francesco Chicchiriccò / Mark]
See Attachment BM
BN. Apache SystemML Project [Deron Eriksson / Ted]
See Attachment BN
BO. Apache Thrift Project [Jake Farrell / Bertrand]
See Attachment BO
BP. Apache Turbine Project [Georg Kallidis / Phil]
See Attachment BP
BQ. Apache Usergrid Project [Todd Nine / Chris]
No report was submitted.
BR. Apache Velocity Project [Nathan Bubna / Shane]
See Attachment BR
BS. Apache Whimsy Project [Sam Ruby / Jim]
See Attachment BS
BT. Apache Xalan Project [Steven J. Hathaway / Ted]
No report was submitted.
@Ted: pursue a report for Xalan
BU. Apache Xerces Project [Michael Glavassevich / Bertrand]
No report was submitted.
BV. Apache XML Graphics Project [Glenn Adams / Phil]
See Attachment BV
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache DeltaSpike Project Chair
WHEREAS, the Board of Directors heretofore appointed Thomas Andraschko
(tandraschko) to the office of Vice President, Apache DeltaSpike, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Thomas Andraschko from the office of Vice President, Apache
DeltaSpike, and
WHEREAS, the Project Management Committee of the Apache DeltaSpike
project has chosen by vote to recommend Mark Struberg (struberg) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Thomas Andraschko is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache DeltaSpike, and
BE IT FURTHER RESOLVED, that Mark Struberg be and hereby is appointed
to the office of Vice President, Apache DeltaSpike, 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 DeltaSpike Project Chair,
was approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Appointment of Chairman
At the face-to-face meeting in June, succession of the chair was
discussed and Phil Steitz agreed to accept the position.
By general consent, Phil Steitz is appointed Chairman.
B. Appointment of Vice Chairman
By general consent, Jim Jagielski is appointed Vice Chairman.
C. Article about Apache OpenOffice https://lwn.net/Articles/729460/
Bertrand: do we want AOO to make public statements about the level
of activity on the project?
Rich: it would be good for them to make a public statement
Chris: no strong opinions about this, but this is not the normal way
the board interacts with PMCs
Ted: the issue is the difference between user activity level (downloads)
and code activity level
Shane: most of our projects have technical users but AOO users won't
necessarily know e.g. that security questions may an issue in
the future
Bertrand: maybe we should ask them to publish a blog post about the
status of the project
Brett: what is our objective? discourage downloads?
Ted: is either a blog or a disclaimer going to accomplish the
objective?
Bertrand: we should have a public statement to make people aware
Jim: no matter what we do, some people will want more. we should go
public; ask the PMC to make a statement of direction so end users
understand what is happening with the project
@Jim: follow up with the PMC to get a public statement out
9. Review Outstanding Action Items
* Mark: Take suggestions for improving communication back to the project
[ Flex 2017-06-21 ]
Status: Ongoing.
* Ted: Discuss state of development with PMC; encourage on-list development
[ Tajo 2017-06-21 ]
Status:
* Shane: contact the project and strongly encourage them to propose a new
chair and report next month
[ Axis 2017-07-19 ]
Status: In progress, will need active encouragement on axis lists to
secure a new chair. Development happening, but PMC not really
very active.
* Brett: pursue a report for Bloodhound
[ Bloodhound 2017-07-19 ]
Status: present
* Mark: ask for an improved report next month
[ Camel 2017-07-19 ]
Status: Done.
* Rich: pursue a report for Directory
[ Directory 2017-07-19 ]
Status: Resolved
* Brett: pursue a report for Fineract
[ Fineract 2017-07-19 ]
Status: Myrle will report again next month, it was prepared for July
but did not submit properly.
* Phil: follow up to see if a new chair is needed and file a report next
month
[ Giraph 2017-07-19 ]
Status: Report was submitted.
* Chris: pursue a report for Hama; is a new chair needed?
[ Hama 2017-07-19 ]
Status: My opinion is that it's time to rotate the chair.
* Mark: pursue a report for Helix
[ Helix 2017-07-19 ]
Status: Done.
* Rich: help resolve billing issue with AWS
[ Mahout 2017-07-19 ]
Status: Resolved
* Mark: remove company names from the report and give the PMC guidance for
future reports
[ Mesos 2017-07-19 ]
Status: Complete
* Rich: ask for a report for next month
[ Thrift 2017-07-19 ]
Status: Report was submitted.
* Phil: follow up to ensure that PMC knows that IP clearance is required
[ Arrow 2017-07-19 ]
Status: Complete
10. Unfinished Business
11. New Business
12. Announcements
Shane will be starting a consulting gig, which will is not expected
to affect his commitment to Apache.
13. Adjournment
Adjourned at 12:03 p.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the Executive Assistant [Melissa Warnkin]
* Working with Regina (Frenkel & Co.), Tom, and Kevin regarding D&O insurance
renewal.
* Working with JimJag re shipping of swag to All Things Open
* No issues at this time
-----------------------------------------
Attachment 2: Report from the VP of Brand Management [Shane Curcuru]
* ISSUES FOR THE BOARD
None.
* OPERATIONS
A quiet month in terms of specific trademarks@ questions, although there are
still some open questions to address. We still have not succeeded in
attracting sufficient (or much at all, really) new volunteer energy or
assistance in answering questions.
Website Analytics show an average of about 120 users per day, the vast
majority from direct URLs, not from links or referrals.
* REGISTRATIONS & CONTRACTS
A *very* busy month in terms of registration renewals and other legal
paperwork related to registrations (more than a dozen issues), including
several questions involving counsel about specific agreements around
individual project marks.
One bit of good news is our opposition to a conflicting FLEX mark in the EU
was successful, with the other party deleting conflicting claims.
-----------------------------------------
Attachment 3: Report from the VP of Fundraising [Kevin A. McGrail]
-Meetings with Virtual continue semi-monthly while we sort out foundational
issues and continue the transition to KAM as the VP. As reported previously,
we have identified large sponsors that have not been billed. If those
sponsors had renewed and paid, we are easily in excess of ½ million missed
potential revenue. It should be easily defendable that the expense of having
Virtual onboard solely based on these missed sponsorships.
- Launching a fundraising website similar to treasurer to help things be more
transparent
- Launched a fundraising-private committee mailing list so sensitive
information can be discussed with appropriately accessible archives.
- Have gone through the data in SVN foundation/Fundraising and archived old
stuff and created a plan for other items
- Have audited with Virtual the list of sponsors that they have vs what we
have on the sponsors page. As noted anecdotally, we’ve missed a LOT of
sponsorship over the years by simply failing to invoice. But we’ve been doing
a good job of recapturing sponsors and in some case even getting some back
monies.
- Using Google Apps NPO edition for Apache for Fundraising work but will
implement so any project or initiative can use it. Planning for
gsuite.cloud.apache.org for flexibility for things like aws.cloud.apache.org
or huawei.cloud.apache.org to be added down the road.
- Working on identifying inkind sponsors
- Revised Slide deck is coming along. Sally has been instrumental as always.
Targeting 8/21 for Ready to Send.
- Support inclusion in tech in concert with Media -
https://blogs.apache.org/foundation/entry/success-at-apache-meritocracy
- Monitoring the spam messages for fundraising continues to identify potential
sponsors being blocked.
- I'll be attending All Things Open on ASF behalf
- I’ll be merging Infra Sponsors into a Directed Sponsors tier as the start of
the directed sponsorship idea and to more fairly and equitably recognize
different in-kind sponsors. Infra is looped in.
- Requested ASF Credit Card with 5K limit in process.
- For directed sponsorship, Sam, please ask the board to individually give
ideas to me of:
Things that shouldn't/should be done and a sentence of why/why not
&
Things that shouldn't/should be done and a sentence of why/why not
Examples: case studies, coding, bug bounties, speeches, sysadmin work, legal,
trademarks, infra NOTE: Please do not assume historical knowledge such as "the
ASF doesn't pay for programming". It'll be codified in this policy so mention
it.
With this feedback, I'll prepare a proposal for the board for directed
sponsorship to then discuss from there.
- I'm gelling that the sponsor thank you event will be good in new york. I
was thinking about asking Google to host because I know them and they might
cater as well. And I can use the opp to leverage Justin's offer to help meet
/ invite with some wall street sponsor candidates. As discussed on
fundraising, I think the thank you will be for sustaining benefactors who have
given more than 500K to the foundation over the years.
-----------------------------------------
Attachment 4: Report from the VP of Marketing and Publicity [Sally Khudairi]
I. Budget: we are on budget and on schedule with no vendor payments
due at this time.
II. Cross-committee Liaison: work with ASF Fundraising continues, with
Sally Khudairi reworking the pitch deck and leading Sponsor
engagement. She has helped bring one Gold Sponsor up to term, and has
had budgeting/renewal meetings with four Sponsors. One Platinum
Sponsor’s billing and payments have been made current with
invoicing/accounting support from Virtual. Rich Bowen and Mark Thomas
have been supporting Sally with the “Sponsor Ambassador” program; a
total of 22 Sponsors have been engaged thus far. Work continues on
individual giving and donor outreach. Sally has also been working with
some Sponsors that are actively involved with some projects in the
Apache Incubator, much of which has involved project promotions and
marketing.
III. Press Releases: the following formal announcements were issued
via the newswire service, ASF Foundation Blog, and announce@apache.org
during this timeframe:
- 1 August 2017 - The Apache Software Foundation announces Apache®
Polygene™ v3.0
- 26 July 2017 - The Apache Software Foundation Announces Apache®
Fluo™ as a Top-Level Project
IV. Informal Announcements: 6 items were published on the ASF
"Foundation" Blog. 4 Apache News Round-ups were issued, with a total
of 160 weekly summaries published to date. We tweeted 30 items, and
have 43K followers. 6 items were posted on LinkedIn, which garnered
more than 28K organic impressions in total.
V. Future Announcements: two announcements are 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 7 media queries. The holidays
have been challenging in coordinating a few press interviews, some of
which were still not scheduled despite being requested weeks or months
before. The ASF received 1,599 press clips vs. last month's clip count
of 765. Media coverage of Apache projects yielded 1,302 press hits vs.
last month's 2,870.
VII. Analyst Relations: we received 3 analyst queries during this
timeframe, including an ongoing Cloud briefing that we have been
involved with over the past 3 years. We also had an inadvertent
timezone glitch with a podling briefing a top-tier analyst firm; this
proved problematic as 26 other analysts and researchers were invited
to participate in the call. Sally has taken on a more active role in
coordinating briefings and interviews to minimize such occurrences.
Apache was mentioned in 58 reports by Gartner (including 4 Magic
Quadrant and 50 Hype Cycle reports); 3 reports by Forrester; 17
reports by 451 Research; and 8 reports by IDC.
VIII. Graphics: Sally finalized the design templates for ASF business
cards, which were printed for VP Fundraising. The templates will be
added to ASF Committer-accessible resources.
IX. ApacheCon liaison: we will continue to support VP Conferences as
ApacheCon evolves.
X. (Non-ASF) Industry Events and Outreach liaison: we are exploring
participating at various events as exhibitors and/or community
partners.
XI. Newswire accounts: we have 10 pre-paid press releases remaining
with NASDAQ GlobeNewswire through December 2017; any unused
announcements will be applied towards our new contract that ends in
December 2019.
# # #
-----------------------------------------
Attachment 5: Report from the VP of Infrastructure [David Nalley]
General
=======
No Board-level issues at this time.
Finances
========
The InfraAdmin has been working with our Accounting team to clear up a
workflow and invoice issue with one of our vendors. Our vendor will
now sending invoices directly to Infra for review and approval.
Operations Action Items
=======================
We have a service contract with Symantec for signing binary releases.
That contract expired in June, and we are working to re-up signings
for the next year. This has been hampered because we need to
"authenticate" our business according to new rules from the CA/Browser
Forum. We are also switching the primary contact point to the
InfraAdmin and our VP Infra email address, to provide backstop points
on contract/renewal issues. The authentication process is involved,
but is progressing. With some hope, it will be solved by end of
August. This service is primarily used by our Apache OpenMeetings and
Apache Tomcat PMCs.
Per above, our D&B records reflect our new Wakefield postal address,
but many other third-party records are out of date. These need to be
updated to ease verification of our business.
Short Term Priorities
=====================
- Complete our LDAP schema changes, and server layout.
- The schema changes have been performed in conjunction with the
Apache Whimsy development team to provide tooling, and design
thoughts on our updated schema. The goal is to provide a unified
view of Incubator podlings and TLPs.
- Our LDAP servers are configured as a multiple-master system with
multiple slave replicas. We will be winding this to a simpler
single-master and a few replicas layout.
- Expanding gitbox usage to more projects.
- Improved/automated monitoring via DataDog.
Long Range Priorities
=====================
- Moving all projects over to gitbox. We are still discovering some
edge cases in our tooling, so the mass-migration is not "now".
- Upgrades to our Confluence and Jira installations, along with moving
them to use Atlassian's Crowd product for single-sign-on.
- Revamp of our DNS management; see below.
General Activity
================
Over the past few weeks, we've done a lot of work with the domains
that we manage. As domains are coming up for renewal, we've been
moving them to Namecheap. However, this process will likely accelerate
as Namecheap provides API-based facilities that can help our DNS
management. After some testing, it appears that we can defer/diminish
our DNS work by shifting those functions over to Namecheap.
Lots of work has been done to ensure that our historical/archival
mailing list content is correct. Thanks to Sebb and Gavin for the
grunt work to make this happen. In addition, the team is now reviewing
what remains to declare lists.apache.org as the only service for
archive access (and turning off mail-search.a.o and mail-archive.a.o).
-----------------------------------------
Attachment 6: Report from the VP of Conferences [Rich Bowen]
We will have a table/booth at All Things Open, and have had a good response
from people willing to staff that presence.
-----------------------------------------
Attachment 7: Report from the Apache Travel Assistance Committee [Melissa Warnkin]
No issues to report at this time.
-----------------------------------------
Attachment 8: Report from the VP of W3C Relations [Andy Seaborne]
There was a request from EFF to appeal the directors decision to have
EME (Encrypted Media Extensions) in HTML proceed to REC status. In W3C
process, an appeal is heard if it passes an initial vote where 5% of
the member organisations vote in favour of hearing the appeal.
The Foundation voted to hear the appeal (discussion on members@).
The request for appeal passed comfortably. The appeal is being held
over 16 August - 13 September and is a vote on the original directors
decision. ASF support for hearing the appeal is not expressing a view in
W3C on the appeal itself.
-----------------------------------------
Attachment 9: Report from the Apache Legal Affairs Committee [Chris Mattmann]
A handful of issues highlight the report this month.
First, Facebook changed the license on RocksDB to dual-licensed
ALv2 and GPLv2 [1]. As such Legal has updated the Legal/resolved
page [2] to reflect this. Despite this specific reclassification
for RocksDB, many Facebook developed projects are still licensed
under the BSD+patents license, and as such several ASF projects
using Facebook dependencies such as BigTop have questions related
to the Facebook BSD+patents license Category-X classification. For
example, BigTop was concerned about packaging code that was licensed
under BSD+patents. Legal's recommendation is not to include such
code in Apache products as described in LEGAL-322 [3].
The discussion on RocksDB evolved into a discussion of another
popular webapp framework developed by Facebook, ReactJS [4]. Several
ASF projects use React including (but not limited to), CouchDB,
Superset (in the Incubator [5]), and other projects. If ReactJS
continues under the BSD+patents license, Legal's opinion has not
changed, and the license itself is now disallowed in ASF projects.
There is an open GitHub issue and ongoing discussion at Facebook
considering changing the license [4] initially driven by a question
from one of the Apache CouchDB PMC members.
In other news, VP Legal has agreed to take on a role as DCMA agent
for the ASF as described in LEGAL-164 [6].
Other major discussion was surrounding if binary artifacts are
officially part of a release, as asked in LEGAL-323 [7]. Clarification
from Legal is that source code is the only artifact that is actually
released by a PMC, and that existing requirements as specified on
[1] are sufficient, so documentation will not be updated.
A question asking for confirmation that 4-clause BSD being is in
category-X was confirmed.
[1] https://s.apache.org/XWzg
[2] https://www.apache.org/legal/resolved.html
[3] https://issues.apache.org/jira/browse/LEGAL-322
[4] https://s.apache.org/yFHp
[5] https://issues.apache.org/jira/browse/LEGAL-320
[6] https://issues.apache.org/jira/browse/LEGAL-164
[7] https://issues.apache.org/jira/browse/LEGAL-323
-----------------------------------------
Attachment 10: Report from the Apache Security Team Project [Mark J. Cox]
Stats for July 2017:
We contacted Mitre to start working on the CVE backlog (where a CVE
was assigned but the information is not yet available on the Mitre
site). Part of the backlog (where issues were public before Oct 2016)
relies on Mitre writing up the description. The rest depends on our
projects filling in the missing information, and we started contacting
projects to get them to do that. We'll give metrics on how that is
going in future reports.
11 CVEs issued to projects (some may not be public yet).
e-mails to security@
7 Phishing/spam/proxy/attacks point to site "powered by Apache" or
Confused user due to "Apache" mentioned in OSS licenses
6 Support Questions
6 Direct Vulnerability report to security@apache.org
1 [site] rejected
1 [ambari]
1 [httpd]
1 [solr]
1 [tomcat]
1 [camel]
14 Vulnerabilities reported to projects
1 [cloudstack]
1 [spark]
4 [geode]
1 [httpd]
2 [struts]
1 [couchdb]
1 [kafka]
1 [nifi]
1 [zookeeper]
1 [hadoop]
-----------------------------------------
Attachment A: Report from the Apache ACE Project [Marcel Offermans]
-----------------------------------------
Attachment B: Report from the Apache Airavata Project [Suresh Marru]
-----------------------------------------
Attachment C: Report from the Apache Ambari Project [Yusaku Sako]
-----------------------------------------
Attachment D: Report from the Apache Ant Project [Jan Matèrne]
## Description:
Apache Ant is a Java based build tool along with associated tools. It consists
of 3 main projects:
- Ant - core and libraries (AntLibs)
- Ivy - Ant based dependency manager
- IvyDE - Eclipse plugin to integrate Ivy into Eclipse Additionally Ant
provides several extensions to Ant (antlibs).
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
Set up Github integration (Jenkins-GithubPullRequests) according to infra's
blog post (use of Cloudbees Enterprise plugin). Fixed some Ivy issues.
Introduced Jaikiran Pai as new committer. Start introducing Gintas Grigelionis
as new committer. Change documentation for Ivy from Xooki to Asciidoc. Plans
started for cutting a release of Ivy. But we haven't any release date yet.
## Health report:
For Ant we feel healthy enough to apply patches, and get a release done. But
basically we are in "maintenance mode". There isn't much development.
The Ivy-call-for-help brought two developers in our focus. They helped
bringing Ivy back to life and are willing to help further.
The first one we invited in June 2017 and he accepted the second on end of
July 2017 and he accepted too.
## PMC changes:
- Currently 21 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jean-Louis Boudart on Thu Dec 12 2013
## Committer base changes:
- Currently 29 committers.
- Jaikiran Pai was added as a committer on Wed Jun 14 2017
- Gintas Grigelionis will be added as a committer in these days.
## Releases:
- Compress Antlib 1.5 was released on Tue Jun 13 2017
-----------------------------------------
Attachment E: Report from the Apache Atlas Project [Madhan Neethiraj]
## Description:
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
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Migration from incubator infra to TLP infra (INFRA-14486) is now complete
- Planning to release 0.8.1, the first release after graduation, in August
- Continuing work on core enhancements like relationships as first class type
- Working on new features like business catalog, tag-propagation,
Virtual Data Connector, Automated Discovery
## Health report:
- Added 2 new committers in last month
- Invited 1 more for committer role in last month. Yet to receive acceptance
as the member is on vacation
- Added 6 new contributors in last month
- A lot of interest in adding new features to Atlas from the community,
like: Virtual Data Connector, Automated Discovery, Business User UIs
## PMC changes:
- Currently 33 PMC members
- No new PMC members added in last month
- Last PMC member addition was on 6/21/2017
## Committer base changes:
- Currently 35 committers
- 2 new committers added in last month, on 7/29/2017
- Last additions to committer role were Ashutosh Mestry and David Radley
## Releases:
0.8.1 release work is in progress
0.8-incubating was released on 03/16/2017
0.7.1-incubating was released on 01/26/2017
0.7-incubating was released on 07/09/2016
0.6-incubating was released on 12/31/2015
0.5-incubating was released on 07/11/2015
-----------------------------------------
Attachment F: Report from the Apache Axis Project [Deepal Jayasinghe]
-----------------------------------------
Attachment G: 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. Further concerns
have been expressed about the long term viability and a further suggestion
from a current PMC member that the project moves to the attic.
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 14 PMC members on the project. The last changes were
in April 2017.
The last new committers were added in May 2014.
The last addition to the PMC was in January 2017 (dammina)
Ryan Ollos resigned from the PMC in April 2017.
Community & Development
=======================
Work on the project has once again stagnated and the positive effect of
the last addition to the PMC has worn off. Since the last report we have
had one further resignation from the PMC with Ryan Ollos noting his lack
of time to contribute towards the project. There has also been a further
suggestion from a current PMC member that the project should move to the
attic due to the lack of community interest. This has not provoked any
further discussion.
Some limited activity has been attempted with Gary Martin's attempt to
restore the salt provisioning for the development environment which had
hampered previous efforts. Additionally with INFRA's requirement for the
migration of bloodhound vms, including the main issue tracker from old
hardware, a new vm was requested and migration to this is in progress,
albeit rather slower than desired. The initial plan of migrating to a
puppet based setup has been postponed with the intention of getting the
tracker up faster but an unexpected issue with upgrading the database
to use the latest version of Bloodhound has further delayed this work.
Activity on the user list remains negligible. The dev list is similarly
quiet with a few messages from Gary Martin discussing ideas of making
greater use of git mirrors to reduce barriers to contribution to the
project and of puppet configuration.
-----------------------------------------
Attachment H: Report from the Apache BookKeeper Project [Sijie Guo]
## Description:
BookKeeper is a scalable, fault-tolerant, and low-latency storage service optimized for append-only workloads.
It has been used as a fundamental service to build high available and replicated services in companies like Twitter,
Yahoo and Salesforce. It is also the log segment store for Apache DistributedLog and message store for Apache Pulsar.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Apache DistributedLog graduates as a subproject of BookKeeper. We are consolidating the development efforts around
log stream library over bookkeeper.
- BookKeeper moves the development including issue reporting and tracking to Github. It reduces the barrier for people
to make contributions to bookkeeper.
- The 4.5.0 release which aims at merging 3 main branches is ready to release. The first release candidate is out on August 07.
- BookKeeper moves the website from CMS to Git. A new bookkeeper website along with tons of documentation improvements are made from contributors.
## Health report:
- After a year of development among develops from multiple different organizations, release 4.5 is almost complete. The first release candidate is out for vote on August 07. It includes exciting features like security support, netty 4 upgrade, weight-based placement policy.
- We moved the git repo to gitbox and are using Github for both issue management and pull request management. It reduced the gap for new contributors to engage with the community.
- DistributedLog graduates as a subproject.
- There are a few promising candidates based on the growth of the community and contributions from joining developers.
## PMC changes:
- Currently 9 PMC members.
- JV Jujjuri was added to the PMC on Tue Jun 27 2017
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Enrico Olivelli and Charan Reddy G at Fri Mar 31 2017
## Releases:
- Last release was 4.4.0 on Sun May 15 2016
## Mailing list activity:
A good number of merged contributions is introducing the mailing list activity.
Consolidate efforts coming from DistributedLog graduation as subproject. More contributor/committer
engagement cause the increased of mailing list activities.
- dev@bookkeeper.apache.org:
- 90 subscribers (up 7 in the last 3 months):
- 3114 emails sent to list (1009 in previous quarter)
- issues@bookkeeper.apache.org:
- 6 subscribers (up 0 in the last 3 months)
- user@bookkeeper.apache.org:
- 100 subscribers (down -1 in the last 3 months):
- 27 emails sent to list (23 in previous quarter)
## JIRA activity:
- 55 JIRA tickets created in the last 3 months
- 90 JIRA tickets closed/resolved in the last 3 months
- 120 Github issues created in the last 3 months
- 70 Github issues closed/resolved in the last 3 months
- 118 Github Pull Requests created in the last 3 months
- 109 Github Pull Requests closed/resolved in the last 3 months
-----------------------------------------
Attachment I: Report from the Apache Brooklyn Project [Richard Downer]
## Description:
- Apache Brooklyn Project is a software framework for modeling, monitoring and
managing cloud applications through autonomic blueprints.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Development continues with a regular turnover of pull requests submitted and
merged.
- We made a new release (0.11.0)
- No new committers or PMC members in this reporting cycle.
## Health report:
- The project continues with a similar level of activity that we have seen
recently. There is a regular turnover of pull requests and commits, and JIRA
tickets, showing that development is at a healthy pace and that users are
feeding back their problems and feature suggestions.
- The mailing list has been slightly quieter in the last month or two; this
is probably due to the holiday season and I assume will only be temporary.
- We continue to monitor our community for potential new committers and PMC
members with the aim of regularly adding individuals.
## PMC changes:
- Currently 14 PMC members.
- Mark McKenna was added to the PMC on Fri May 05 2017
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Mark McKenna at Thu Mar 30 2017
## Releases:
- 0.11.0 was released on Thu May 18 2017
## JIRA activity:
- 28 JIRA tickets created in the last 3 months
- 34 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment J: Report from the Apache Buildr Project [Antoine Toulme]
## Description:
Apache Buildr is a build system for Java-based applications, including
support for Scala, Groovy and a growing number of JVM languages and
tools. We wanted something that’s simple and intuitive to use, so
we only need to tell it what to do, and it takes care of the rest.
But also something we can easily extend for those one-off tasks, with
a language that’s a joy to use. And of course, we wanted it to be
fast, reliable and have outstanding dependency management.
## Issues:
In progress: we are discussing the board feedback from the last board
meeting in which the board underlined the lack of activity and the
small PMC.
https://lists.apache.org/thread.html/6b7216eaf9ed5287461cc6355b71d2cb7141b4414c80477fd96f24ab@%3Cprivate.buildr.apache.org%3E
We're still discussing this and welcome any feedback.
## Activity:
We have made some inroads towards a 1.5.4 release, adding Kotlin support,
better packaging capabilities and sorting through our addons.
## Health report:
The activity is slow, with 2 active committers.
Little activity on the user or dev list.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Peter Donald on Tue Oct 15 2013
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Tammo van Lessen at Fri Aug 08 2014
## Releases:
- Last release was 1.5.3 on May 17 2017
-----------------------------------------
Attachment K: Report from the Apache Camel Project [Christian Mueller]
Status report for the Apache Camel project - August 2017
## 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:
- The spam mails we are receiving on Nabble and also on the moderate mail
accounts are painful.
- The Camel team created a Gitter chat at
https://gitter.im/apache/apache-camel to provide more possibilities to our our
community to get in touch with us. https://s.apache.org/9kwJ
- 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.
- We are focusing the development of the next minor release Apache Camel
2.20.0 expected to be released in Q4 2017.
- 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 run a new logo proposal and our community has vote:
https://s.apache.org/qWPW
Now, the PMC decides how 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 30 PMC members.
- Zoran Regvart was added to the PMC on Sun Jul 02 2017
## Committer base changes:
- Currently 58 committers.
- Tomohisa Igarashi was added as a committer on Wed Jun 07 2017
- Onder Sezgin was added as a committer on Thu Jun 08 2017
- Quinn Stevenson was added as a committer on Wed Jun 07 2017
## Releases:
- 2.17.5 was released on Jan 22 2017
- 2.17.6 was released on March 8 2017
- 2.17.7 was released on May 18 2017
- 2.18.2 was released on Jan 30 2017
- 2.18.3 was released on Mar 12 2017
- 2.18.4 was released on May 25 2017
- 2.19.1 was released on Jun 15 2017
- 2.19.2 was released on Aug 1 2017
## Mailing list activity:
- Mailing list activity stays at a high level.
-----------------------------------------
Attachment L: Report from the Apache Cassandra Project [Nate McCall]
## Description:
The Apache Cassandra database is the right choice when you need scalability
and high availability without compromising performance. Linear scalability and
proven fault-tolerance on commodity hardware or cloud infrastructure make it
the perfect platform for mission-critical data.Cassandra's support for
replicating across multiple datacenters is best-in-class, providing lower
latency for your users and the peace of mind of knowing that you can survive
regional outages.
## Issues:
There are no issues requiring board attention at this time.
## Activity and Health:
Overall the project is healthy. It's been about a year since the inquiry from
the board and we've continued to make progress expanding the committer base
and PMC membership while moving forward with development.
We very much appreciate the involvement of the management, membership and
community with the resolution of LEGAL-303. The paves the way for a first
implementation of new functionality around pluggable storage engines.
The cassandra-dtest project made it through the ASF code donation process.
This has removed a small bottleneck and source of occasional test errors by
allowing committers to commit distributed test suites at the same as code
commits to the core project.
## PMC changes:
There are currently 21 PMC members. No new PMC members added in the last 3
months. The last PMC addition was Sankalp Kohli on Mon Oct 24 2016. Note that
there are currently open votes for four additional PMC members. They should be
resolved by the time the board meets.
## Committer base changes:
There are currently 46 committers. Philip Thompson was added as a committer on
Fri Jun 23 2017.
## Releases:
The final release of the 2.1.x series was done this quarter. Maintenance
releases were done on the 2.2.x, 3.0.x, 3.11.x branches. We anticipate a
release of 4.0 in the next quarter.
- 2.1.18 was released on Mon Jun 26 2017
- 2.2.10 was released on Mon Jun 26 2017
- 3.0.14 was released on Fri Jun 23 2017
- 3.11.0 was released on Fri Jun 23 2017
## Mailing list activity: The participation on the dev list was down this
quarter, perhaps attributed to summer holidays and the lack of anything
contentious. However, user list participation was up slightly which is a good
sign of positive community engagement.
dev@cassandra.apache.org:
- 1625 subscribers (down -2 in the last 3 months):
- 320 emails sent to list (474 in previous quarter)
user@cassandra.apache.org:
- 3112 subscribers (down -18 in the last 3 months):
- 1112 emails sent to list (1107 in previous quarter)
## JIRA activity:
- 230 JIRA tickets created in the last 3 months
- 156 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment M: Report from the Apache Clerezza Project [Hasan Hasan]
DESCRIPTION
Apache Clerezza models the RDF abstract syntax in Java and provides supports
for serializing, parsing, and managing triple collections, as well as a tool
to generate the source code of a Java class with constants for an ontology
described in RDF. Apache Clerezza components are OSGi-based and have the
purpose to ease building of Semantic Web applications and services.
ISSUES FOR THE BOARD
There are no issues requiring board attention at this time.
RELEASE
Latest release was partial-release-201604 created on May 13, 2016.
ACTIVITY
- Fixed a bug in SparqlClient related to media type comparison.
- As an Apache Clerezza demo application, a simple Linked Data Server exposing
data from a SPARQL server as Linked Data has been implemented.
COMMUNITY
Latest change was addition of a new committer and PMC member on 16.08.2013.
INFRASTRUCTURE
Latest update of the Apache Clerezza Website was in May 2017.
-----------------------------------------
Attachment N: Report from the Apache Cocoon Project [Cédric Damioli]
## Description:
Web development framework: separation of concerns, component-based.
## Issues:
there are no issues requiring board attention at this time
## Activity:
The most recent release is 2.1.12 on 2013-03-14
A few JIRA issues opened since last report
There's only a little activity on both users and dev mailing-lists.
There was a final point given to an old security report (rejected as a security issue by the PMC).
There have been some quite interesting changes since last release, at least for 2.1 branch, which would deserve a release.
The last board feedback recommanded us to plan a release. This is definitely something we should think about, for each of our 3 branches, 2.1.x, 2.2.x and 3.x
## PMC changes:
None.
Most recent addition: 2012-07-06
## Committer base changes:
None.
Most recent addition: 2012-07-06
-----------------------------------------
Attachment O: Report from the Apache Community Development Project [Ulrich Stärk]
-----------------------------------------
Attachment P: Report from the Apache CouchDB Project [Jan Lehnardt]
## Description:
- Seamless multi-master sync, that scales from Big Data to Mobile,
with an Intuitive HTTP/JSON API and designed for Reliability.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- Released version 2.1.0, details on the blog:
https://blog.couchdb.org/2017/08/07/2-1/ (tl;dr: a major new feature
for users at scale, tons of post 2.0.0 bugfixes, and:
- Massively overhauled test suites, jenkins setup, worked with Infra around
lots of little and gnarly issues; all this resulting in being able to
make more reliable release in quicker succession from now on. We haven’t
settled on anything yet, but are discussing a release per quarter plus
security ad bugfix releases as needed. Special shout out for PMC member
Joan “wohali” Touzet, for primarily driving this effort to success.
- Currently awaiting Facebook’s decision on licensing their React & adjunct
JavaScript frameworks, which are in use in our admin UI Fauxton:
https://github.com/facebook/react/issues/10191 — We have discussed
alternatives, but made no contingency plans just yet.
## Health report:
- The project is doing fine overall. We’ll be doing a dedicated drive for
JavaScript contributors for our admin UI after the licensing discussion
is over, and we have more certainty about future direction. Current
contributors are moving towards other areas of the projects, and it’s
a great place for people to get into the project without having to
learn Erlang.
## PMC changes:
- Currently 14 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Garren Smith on Mon Oct 19 2015
## Committer base changes:
- Currently 58 committers.
- Glynn Bird was added as a committer on Mon May 29 2017
## Releases:
- 2.1.0 was released on Mon Aug 07 2017
-----------------------------------------
Attachment Q: Report from the Apache Creadur Project [Brian E Fox]
Apache Creadur creates and maintains a suite of open source software related
to the auditing and comprehension of software distributions. Any language and
build system are welcomed.
Status
------
No changes since the last report.
Creadur is primarily used by other Apache projects to help check for
conformity to ASF standards. This is why the project team is primarily
comprised of members and committers from other ASF projects. The risk of the
project foundering is therefore very low despite the ongoing lack of progress.
If someone has an itch to scratch, it will no doubt get fixed.
Community
---------
In September 2016 Karl Heinz Marbaise was elected to join the PMC / Commit.
Releases
--------
Apache Rat 0.12 was released in June, 2016
Apache Rat 0.11 was released in August, 2014
Apache Rat 0.10 was released in September, 2013.
-----------------------------------------
Attachment R: Report from the Apache DeltaSpike Project [Thomas Andraschko]
## Description:
Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency
Injection) extensions intended to make application development easier when
working with CDI and Java EE. Some of its key features include:
- A core runtime that supports component configuration, type safe messaging
and internationalization, and exception handling.
- A suite of utilities to make programmatic bean lookup easier.
- A plugin for Java SE to bootstrap both JBoss Weld and Apache OpenWebBeans
outside of a container.
- JSF integration, including backporting of JSF 2.2 features for Java EE 6.
- JPA integration and transaction support.
- A Data module, to create an easy to use repository pattern on top of JPA.
- Quartz integration
Testing support is also provided, to allow you to do low level unit testing of
your CDI enabled projects.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
1.8.0 got released. We also streamlined our CI setup.
## Health report:
Community involvement is ok but could be a tad higher.
## PMC changes:
- Currently 19 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Harald Wellmann on Thu May 19 2016
## Committer base changes:
- Currently 33 committers.
- No new committers added in the last 3 months
- Last committer addition was Matej Novotny at Fri Jun 03 2016
## Releases:
- 1.8.0 was released on Thu Jun 01 2017
## Mailing list activity:
- users@deltaspike.apache.org:
- 181 subscribers (up 2 in the last 3 months):
- 46 emails sent to list (76 in previous quarter)
- dev@deltaspike.apache.org:
- 105 subscribers (up 1 in the last 3 months):
- 219 emails sent to list (159 in previous quarter)
## JIRA activity:
- 27 JIRA tickets created in the last 3 months
- 19 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment S: Report from the Apache Directory Project [Stefan Seelmann]
## Description:
The Apache Directory TLP consists of the following sub-projects:
- ApacheDS: An extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3
compatible by the Open Group. Besides LDAP it supports
Kerberos 5 and the Change Password Protocol.
- LDAP API: An ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap
and Mozilla LDAP API). This is a "schema aware" API
with some convenient ways to access all types of LDAP
servers.
- Studio: A complete directory tooling platform intended to be
used with any LDAP server however it is particularly
designed for use with ApacheDS. It is an Eclipse RCP
application, composed of several Eclipse (OSGi) plugins.
- Fortress: A standards-based access management system that provides
role-based access control, delegated administration and
password policy services with an LDAP backend.
- Kerby: An implementation of Kerberos v5 protocol and contains
various tools to access and manage kerberos principals
and keytabs. It provides a rich, intuitive and
interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2)
as desired in modern environments such as cloud, Hadoop
and mobile.
- Mavibot: An embeddable key-value database library with MVCC
(Multi Version Concurrency Control) support.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
General:
- We decided to move all projects to Java 8
Per sub-project activity:
- ApacheDS: Good activity
- LDAP API: High activity: Version 1.0.0 release, discussion about
2.0.0 roadmap, repository will be migrated to Git
- Studio: Low activity: Bugfix release planned
- Fortress: Good activity: Release of version 2.0.0
- Kerby: High activity: Relase of version 1.0.0, work on GSSAPI,
improvements in kinit and kadmin tools
- Mavibot: Low activity, but a talk at LDAPCon was accepted
## Health report:
Overall develomment activity (commits, development related mails,
resolved issues, releases) was higher than last quater. Two new
committers were added. 4 release were published. The project is
healthy.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Chris Pike on Wed Nov 23 2016
## Committer base changes:
- Currently 55 committers.
- Yudhi Karunia Surtan was added as a committer on Mon May 29 2017
- Brian Burch was added as a commiter end of April 2017
## Releases:
- Apache Directory Fortress 2.0.0 was released on Fri Jul 07 2017
- Apache Kerby 1.0.0 was released on Sat May 13 2017
- Apache LDAP API 1.0.0 was released on Wed Jun 07 2017
- ApacheDS 2.0.0-M24 was released on Wed Jun 07 2017
- Studio: Last release 2.0.0.v20161101-M12 on 2016-11-01
- Mavibot: Last release 1.0.0-M8 on 2015-08-15
## Mailing list activity:
- Higher activiy then previous quater
- Peak on kerby@d.a.o due to release activity
## JIRA activity:
- 52 JIRA tickets created in the last 3 months
- 43 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment T: Report from the Apache Drill Project [Aman Sinha]
## Description:
- Drill is a Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Since the last board report, Drill has released version 1.11.0. The
following new features/enhancements
were added in addition to many other bug fixes:
- Cryptography-related functions.
- Spill to disk for the hash aggregate operator.
- Format plugin support for PCAP files.
- Ability to change the HDFS block Size for Parquet files.
- Ability to store query profiles in memory.
- Configurable CTAS directory and file permissions option.
- Support for network encryption.
- Relative paths stored in the metadata file.
- Support for ANSI_QUOTES.
## Health report:
- The project is healthy. Development activity as reflected in the pull
requests and JIRAs
is good. Activity on the dev and user mailing lists has shown a slight
increase compared
to previous period. Three new committers and one new PMC member were added
in the last period.
## PMC changes:
- Currently 18 PMC members.
- Arina Ielchiieva was added to the PMC on Tue Aug 01 2017
## Committer base changes:
- Currently 36 committers.
- New commmitters:
- Charles Givre was added as a committer on Mon Jun 12 2017
- Laurent Goujon was added as a committer on Thu Jun 08 2017
- Paul Rogers was added as a committer on Fri May 19 2017
## Releases:
- 1.11.0 was released on Thu Jul 27 2017
## Mailing list activity:
- dev@drill.apache.org:
- 444 subscribers (up 8 in the last 3 months):
- 1928 emails sent to list (1918 in previous quarter)
- issues@drill.apache.org:
- 18 subscribers (down -2 in the last 3 months):
- 2748 emails sent to list (2964 in previous quarter)
- user@drill.apache.org:
- 609 subscribers (up 23 in the last 3 months):
- 454 emails sent to list (362 in previous quarter)
## JIRA activity:
- 234 JIRA tickets created in the last 3 months
- 101 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment U: Report from the Apache Empire-db Project [Rainer Döbele]
## Description:
- Apache Empire-db is a relational database access engine that takes an
SQL-centric approach in comparison to traditional OR-Mappers
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- This quarter we have created new tickets for improvements in order
to make our the code more robust and to support new features in the
latest version of the SQL-Server DBMS and have already partially
resolved some of those issues.
- Additionally some bugs reported by users or committers have been
resolved and user questions have been answered.
## Health report:
- The project remains healthy. Activity levels on mailing lists, git and
JIRA are low but constant among the existing community.
- However it is acknowledged that in order to attract new user and
committers an overhaul of the website and the documentation is necessary.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jan Glaubitz on Sun Jul 10 2016
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Jan Glaubitz at Mon Oct 05 2015
## Releases:
- Last release was 2.4.6 on Tue Jan 17 2017
## Mailing list activity:
- dev@empire-db.apache.org:
- 37 subscribers (up 0 in the last 3 months):
- 7 emails sent to list (1 in previous quarter)
- user@empire-db.apache.org:
- 55 subscribers (up 1 in the last 3 months):
- 9 emails sent to list (2 in previous quarter)
## JIRA activity:
- 9 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment V: Report from the Apache Fineract Project [Myrle Krantz]
## Description:
- Apache Fineract (\’fīn-,ә-,rakt\) is an open source system for core
banking as a platform. Fineract provides a reliable, robust, and affordable
solution for entrepreneurs, financial institutions, and service providers to
offer financial services to the world’s 2 billion underbanked and unbanked.
## Issues:
## Activity:
- Feature work includes additional reports, blocks and holds for savings
accounts, rescheduling bulk loans, pre-defining customer sms and e-mails
notification, improvements in credit bureau integration, support for
surveys, and support for two factor authentication.
- GSOC interns on Apache Fineract and the Mifos Initiative are making good
progress on their projects related to the platform.
Alex Ivanov is ahead of schedule on the Two Factor Authentication project
under mentorship of Avik Ganguly
Thisura Philips has been making multiple pull requests to fix issues found
during his static analysis of the code base under mentorship of Mark
Reynolds
Sanyam Goel is continuing to integrate the APIs with Swagger for live API
documentation under the mentorship of Aleksandar Vidakovic
Nikhil Pawar is finalizing integration with the Equifax Credit Bureau as
part of his project under the mentorship of Nazeer Sheik.
Courage Angeh is adding in additional back-end support for our
notifications framework to deliver staff notifications across various apps
powered by Apache Fineract with the guidance of Pranjal Goswami.
Vladimir Fomene is implementing a brand new database design for a mobile
money bridge integrating with Apache Fineract with support from Ayuk Etta
and Antony Omeri
Developers from R116 with support from Mentors International have built and
added in enhancements to building reports directly via SQL queries in the
platform.
- The community has begun discussing taking over the Mifos I/O code base
(https://github.com/mifosio). This code has, from its inception, been
intended for Apache Fineract. Still, there are a few issues that need to be
resolved before we're ready for this.
- Adoptions and deployments of Apache Fineract in Guatemala, Germany, and
Nigeria are proceeding along smoothly and beginning to scale on the
platform. Members of those terms are working with the community on their
implementations.
## Health report:
- The project remains healthy. Activity levels on mailing lists, git and
JIRA remain mostly constant, or have very slight upticks.
- Many community functions are filled by only one person. The mailing
list has only one moderator; all merges are being performed by one
committer; only one committer is serving as a release manager.
- We have 38 open pull requests stretching back over a year. We need to do
a better job of reacting to pull requests.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jim Jagielski on November 3rd, 2016.
## Committer base changes:
- Currently 15 committers.
- One addition still getting setup: Santosh Math was voted in and
announced this week.
- Last committer additions before that were Zayyad Said and Robert Ippez
on March 13th, 2017.
## Releases:
- Released version 1.0.0
https://dist.apache.org/repos/dist/release/fineract/1.0.0/ on June 1 2017.
- The Mifos Initiative has issued a Mifos release based on the current
Apache Fineract code.
## Mailing list activity:
Requests for help on the user list continue to be answered in a prompt and
friendly manner.
- dev@fineract.apache.org:
- 148 subscribers (up 9 in the last 3 months):
- 1046 emails sent to list (783 in previous quarter)
- issues@fineract.apache.org:
- 8 subscribers (up 0 in the last 3 months):
- 262 emails sent to list (167 in previous quarter)
- user@fineract.apache.org:
- 124 subscribers (up 9 in the last 3 months):
- 66 emails sent to list (65 in previous quarter)
## JIRA activity:
- 50 JIRA tickets created in the last 3 months
- 44 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment W: Report from the Apache Flume Project [Hari Shreedharan]
DESCRIPTION
Apache Flume is a distributed, reliable, and available system for
efficiently collecting, aggregating, and moving large amounts of log
data to scalable data storage systems such as Apache Hadoop's HDFS.
RELEASES
* The last release of Flume was version 1.7.0, released on October
16, 2016.
* No other releases are planned at this time.
CURRENT ACTIVITY:
* A total of 52 issues have been filed, and 14 issues have been
resolved in the last three months.
* Approximately 459 messages were exchanged on the dev list in the
past three months, while a total of 24 were exchanged on the user
list in this period.
COMMUNITY
* The last time a committer was added to the project
was on May 19, 2017. Denes Arvay was added a committer.
* Currently there are:
- Total of 292 subscribers to the developer list
- Total of 688 subscribers to the user list
- Total of 29 committers
- Total of 22 PMC members
* The last time a new PMC member was elected for the project was
on March 8, 2017.
PMC CHANGES
* Bessenyei Balázs Donát was added to the PMC on March 08, 2017.
ISSUES
* There are no issues requiring board attention at this time.
-----------------------------------------
Attachment X: Report from the Apache Fluo Project [Keith Turner]
## Description:
- Apache Fluo is a distributed processing system built on Apache Accumulo. Fluo
users can easily setup workflows that execute cross node transactions when data
changes. These workflows enable users to continuously join new data into large
existing data sets with low latency while avoiding reprocessing all data.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Released versions of Fluo are tightly coupled with YARN+Twill for launching
services on a cluster. Work is currently under way to break this tight
coupling inorder to support YARN+Twill, Mesos, and Kubernetes.
- Fluo implements an immutable byte array wrapper in its API. Work on moving
this to its own sub-project is underway. The goal of this is to create
something analogous to String for bytes that is suitable for use in other APIs.
This goal was discussed on an OpenJDK list and there was agreement Java needs a
library like this until Java defines a bigger story for immutability.
- Still working through a few gradutation task with INFRA, this is mostly done.
## Health report:
- Within the past three months
- 46 GitHub issues were opened and 23 closed
- 64 GitHub pull request were opened and 56 were closed
- 69 commits were made by 6 authors, 2 authors were not committers
## PMC changes:
- Currently 8 PMC members.
- Chris McTague was added to the PMC on Wed May 31 2017, after our last report to IPMC.
- PMC and Committers are the same.
## Releases:
- fluo-1.1.0-incubating was released on Mon Jun 12 2017
- fluo-recipes-1.1.0-incubating was released on Thu Jun 22 2017
-----------------------------------------
Attachment Y: Report from the Apache Forrest Project [David Crossley]
Apache Forrest mission is software for generation of aggregated multi-channel
documentation maintaining a separation of content and presentation.
Issues needing board attention:
None.
Changes in the PMC membership:
None.
Last modified: 2013-04-08
Most recent addition: 2009-06-09
New committers:
None.
Most recent addition: 2009-06-09
None on the horizon.
General status:
The most recent release is 0.9 on 2011-02-07.
No activity on the user mail list. However it never gets used much anyway.
No activity on the dev mail list.
Two PMC members were present during the quarter.
At this report, three other PMC members responded to my draft report.
This confirms that there are sufficient people hanging around for us to
potentially be able to make a decision or encourage new contributors.
Project status:
Activity: Idle
3+ people have indicated presence, so has sufficient oversight.
Security issues published:
None.
Progress of the project:
Minor tweaks to docs to follow move of Gump's report URLs.
-----------------------------------------
Attachment Z: Report from the Apache Geode Project [Mark Bretl]
## Description:
- Apache Geode provides a database-like consistency model, reliable
transaction processing and a shared-nothing architecture to maintain very low
latency performance with high concurrency processing.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Geode 1.2 was released with over 300 tickets resolved, including
- Integration with Apache Lucene is no longer experimental
- A built in partition resolver
- Examples bundled with the distribution
- ApacheCon presentation - Building an IoT platform with Apache Apollo and
Apache Geode by Swapnil Bawaskar
## Health report:
- We’re continuing to work on attracting new contributors and making it easier
to participate in the community.
- Mailing list activity is healthy.
- Work has started towards the next Geode release, 1.3.0 including development
of a new client/server protocol.
## PMC changes:
- Currently 36 PMC members (+1 since last report)
- Joey McAllister was added to the PMC on Mon Jul 24 2017
## Committer base changes:
- Currently 81 committers (+2 since last report)
- Joey McAllister was added as a committer on Tue Jul 25 2017
- Deepak Dixit was added as a committer on Thu Jul 13 2017
## Releases:
- 1.2.0 was released on Wed July 17th 2017
## Mailing list activity:
- Mailing lists remain active and we’re seeing continued growth in subscriber
counts. Mailing list traffic on dev went down because we redirected jira
traffic to issues@geode.apache.org, but the combined activity increased.
- dev@geode.apache.org:
- 174 subscribers (up 10 in the last 3 months)
- 4264 emails sent in the past 3 months, 7166 in the previous cycle
- issues@geode.apache.org:
- 56 subscribers (up 1 in the last 3 months)
- 3183 emails sent in the past 3 months, 0 in the previous cycle
- user@geode.apache.org:
- 232 subscribers (up 12 in the last 3 months)
- 286 emails sent in the past 3 months, 202 in the previous cycle
## JIRA activity:
- 513 JIRA tickets created in the last 3 months
- 351 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AA: Report from the Apache Giraph Project [Avery Ching]
Giraph is a Bulk Synchronous Parallel framework for writing programs
that analyze large graphs on a Hadoop cluster. Giraph is similar to
Google's Pregel system.
Project releases
* No immediate plans for an upcoming new release - last major release 10/21/2016
Overall project activity since the last report
* No major updates since the last report
* Several critical bug fixes
When were the last committers or PMC members elected?
** Hassan Eslami (Committer) on 7/15/2016
** Sergey Edunov (PMC) on 8/15/2016
Mailing list members
* Our mailing list is stable (not much change from the last report)
** user@ 457 -> 460
** dev@ 281 -> 281
-----------------------------------------
Attachment AB: Report from the Apache Gora Project [Lewis John McGibbney]
## Description:
The Apache Gora open source framework provides an in-memory data model
and persistence for big data. Gora supports persisting to column stores,
key value stores, document stores and RDBMSs, and analyzing the data
with extensive Apache Hadoop MapReduce support.
## Issues:
There are no issues requiring board attention at this time
## Activity:
Community activity has revolved around GSoC (2 projects; additio module)
and review of these projects. A significant degree of high quality code has
resulted from these efforts and we will be VOTE'ing on a 0.8 RC shortly.
## Health report:
The Gora community remains healthy. We will be looking to add to our PMC
roster shortly. This is reflected through GSoC efforts.
## PMC changes:
- Currently 23 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Kevin Ratnasekera on Thu Jan 12 2017
## Committer base changes:
- Currently 23 committers.
- No new committers added in the last 3 months
- Last committer addition was Kevin Ratnasekera at Wed Dec 07 2016
## Releases:
- Last release was 0.7 on Mon Mar 20 2017
## Mailing list activity:
user@ is up, which is great. New users have been aided with thier queries
in good time.
- dev@gora.apache.org:
- 75 subscribers (up 0 in the last 3 months):
- 594 emails sent to list (234 in previous quarter)
- user@gora.apache.org:
- 81 subscribers (up 2 in the last 3 months):
- 9 emails sent to list (6 in previous quarter)
## JIRA activity:
- 11 JIRA tickets created in the last 3 months
- 13 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AC: Report from the Apache Groovy Project [Guillaume Laforge]
## Description:
Apache Groovy is a multi-faceted programming language for the Java platform.
Groovy is a powerful, optionally typed and dynamic language, with static-
typing and static compilation capabilities, aimed at multiplying developers’
productivity thanks to a concise, familiar and easy to learn syntax. It
integrates smoothly with any Java program, and immediately delivers to your
application powerful features, including scripting capabilities, Domain-
Specific Language authoring, first class functional programming support
and runtime and compile-time meta-programming.
## Issues:
There are no new issues arising requiring board attention at this time.
On the website front, we are tracking this topic along with those 3 tickets:
- GROOVY-8181: Website move - step 1:
create new repositories for user and dev sites
- GROOVY-8182: Website move - step 2:
populate user and dev sites splitting current content
- GROOVY-8183: Website move - step 3:
generate user and dev sites from repo content
Of these, step 1 (previously reported) and 2 are complete.
Step 2 involved splitting the site in two:
The developer focused site, on the typical Apache domain:
http://groovy.apache.org/ The community site (domain also owned by ASF):
http://www.groovy-lang.org/
Some early work has begun on step 3. We are exploring how to adapt our
current site generation scripts to work with existing Apache tools in this
area (e.g. Buildbot). As well as automating some manual steps taken to
complete step 2, part of step 3 completes the move of the website fully
onto Apache infrastructure.
## Activity:
This quarter, 147 commits were contributed from 19 contributors including 14
non-committer contributors (12 new).
## Health report:
With the progress on the build and release aspects of the project,
our release train has increased velocity, and the community seems
happy to see us being back on track with regular releases.
This quarter also took place two Groovy focused conferences:
GR8Conf Europe, in Copenhagen, and GR8Conf US, in Minneapolis,
gathering developers of the Apache Groovy Ecosystem from everywhere
around the world.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was John Wagenleitner on Sun Apr 02 2017
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Sergei Egorov at Thu Dec 08 2016
## Releases:
- 2.5.0-beta-1 was released on Tue Jun 06 2017
- 2.4.12 was released on Sat Jun 24 2017
## Mailing list activity:
- users@groovy.apache.org:
- 412 subscribers (up 7 in the last 3 months):
- 174 emails sent to list (216 in previous quarter)
- dev@groovy.apache.org:
- 235 subscribers (up 0 in the last 3 months):
- 144 emails sent to list (353 in previous quarter)
- notifications@groovy.apache.org:
- 32 subscribers (up 0 in the last 3 months):
- 874 emails sent to list (1258 in previous quarter)
## JIRA activity:
- 99 JIRA tickets created in the last 3 months
- 56 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AD: Report from the Apache Hama Project [Edward J. Yoon]
-----------------------------------------
Attachment AE: Report from the Apache Helix Project [Kishore Gopalakrishna]
## Description:
A cluster management framework for partitioned and replicated distributed resources
## Issues:
- Need merge selective changes from 0.7 branch into current master branch.
## Activity:
- 19 pull requests merged in last 3 months.
- 22 commits in last 3 months.
- New master branch created.
## Health report:
## PMC changes:
- Currently 18 PMC members.
- One new PMC (Junkai Xue) added in July 4. 2017.
## Committer base changes:
- Currently 19 committers.
- No new committer added in last 3 months.
## Releases:
- Last release was 0.6.8 on June 19, 2017.
## Mailing list activity:
- dev@helix.apache.org:
- 69 subscribers (up 2 in the last 3 months): -- need update.
- 188 emails sent to list (108 in previous quarter)
- user@helix.apache.org:
- 98 subscribers (up 3 in the last 3 months): -- need update.
- 18 emails sent to list (21 in previous quarter)
## JIRA activity:
- 10 JIRA tickets created in the last 3 months
- 4 JIRA tickets resolved in the last 3 months
-----------------------------------------
Attachment AF: Report from the Apache HTTP Server Project [Daniel Gruno]
## Description:
- The Apache HTTP Server is an open-source HTTP server for modern
operating systems including UNIX, Microsoft Windows, Mac OS/X and
Netware.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
Three releases (two for 2.4 and one for 2.2) were cut. A lot of great
improvements in the codebase were made alongside some herculean tasks in
cleaning up old code/designs and keeping HTTPd at cutting edge. The 2.2
release also marks the last release of the 2.2 branch, save whatever
security patches may be released from now and through December 2017[1].
Among the plethora of activities in this cycle, I wish to point out a few:
At ApacheCon North America 2017 in Miami, a total of four talks were
held about HTTPd. Thanks go out to the speakers for the time and effort
put into this.
The HTTP/2 support in HTTPd 2.4 has been changed from "experimental" to
stable in future releases[2], in part to avoid confusion over the
projects use of the term "experimental" to denote modules and/or
features whose API may change but are otherwise considered stable, as is
the case with the mod_h2 and mod_lua modules.
Work has also begun[3] on a new module, mod_md, that enables on-the-fly
acquisitions and integrations of web site certificates via Automatic
Certificate Management Environment (ACME) providers such as ISRG's
LetsEncrypt.
[1] https://s.apache.org/obH5
[2] https://s.apache.org/yqNQ
[3] https://s.apache.org/Tnra
## Health report:
The project remains in superb health. Mailing lists are full of active and
engaged people, with many simultaneous discussions going on. The number of
committers actively contributing to the code/documentation has been steady
throughout the past two years and remains at a level of 15-20 active
committers each month. HTTPd is also seeing increased interest on GitHub even
though the project is only mirrored there. Looking at user/support activity,
HTTPd can boast a very vibrant and alive user sphere in terms of interactions
on mailing lists and IRC, as well as other fora. While we have not invited new
committers or PMC members in the past 3 months (summertime being a bit of a
lull), we are always on the lookout for new people to bolster our ranks and
help make HTTPd one of the best pieces of open source software out there.
## PMC changes:
- Currently 49 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Steffen Land on Mon Feb 27 2017
## Committer base changes:
- Currently 119 committers.
- No new committers added in the last 3 months
- Last committer addition was Daniel Ferradal at Wed Apr 26 2017
## Releases:
- 2.2.34 was released on Tue Jul 11 2017, and marks the last release of 2.2.
- 2.4.26 was released on Mon Jun 19 2017
- 2.4.27 was released on Tue Jul 11 2017
## Mailing list activity:
Mailing activity remains steady, albeit a bit lower than the previous
reporting cycle (likely due to it being summer), and have been omitted for the
sake of brevity.
## Bugzilla Statistics:
- 64 Bugzilla tickets created in the last 3 months
- 50 Bugzilla tickets resolved in the last 3 months
-----------------------------------------
Attachment AG: Report from the Apache HttpComponents Project [Asankha Perera]
## Description:
- The Apache HttpComponents project is responsible for creating and
maintaining a toolset of low-level Java components focused on HTTP and
associated protocols
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- The HttpClient 5.0 alpha 2 release introduces HTTP/2 support
- We are about to update the minimum JRE level for the HttpClient to 1.8 for
all version 5.x artifacts, and have asked for feedback from users
## Health report:
- Overall the project remains active. Although established in late 2007
the project remains stable and active as seen by JIRA and Emails.
- The number of emails could be seen as low, but it is stable like the state
of the project, and we still have interested people joining into the
dev list hoping to contribute.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Osipov on Mon Aug 24 2015
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Julian Sedding at Fri Sep 30 2016
## Releases:
- HttpComponents Core 5.0 alpha3 was released on May 2 2017
- HttpClient 5.0-alpha2 was released on Thu May 11 2017
## JIRA activity:
- 33 JIRA tickets created in the last 3 months
- 27 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AH: Report from the Apache Ignite Project [Denis Magda]
## Description:
Apache Ignite is a memory-centric data platform that is strongly consistent and highly available with powerful SQL, key-value and processing APIs.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Apache Ignite community incubated and accepted the donation of Ignite Native
Persistence from GridGain.
- Apache Ignite 2.1 was released on Thu Jul 27 2017 The release integrated the Durable
Memory architecture with Ignite Native Persistence allowing to store and process data
and indexes both in memory and on disk cluster-wide. Such a memory architecture helps
to achieve in-memory performance with durability of disk using all the available
resources of the cluster.
- Apache Ignite site’s front page has been reworked and improved to meet the recent
changes happened to the project: https://ignite.apache.org/index.html
- The community members organized, participated and conducted around 17 webinars, meetups,
conference talks since the last report. There are two more scheduled till the end of
August: https://ignite.apache.org/events.html
## Health report:
The mailing statistics, project evolvement, releases delivery and overall community
engagement shows that the state of the project is in a good shape. However, the
community has not elected new committers and PMC members since the last report.
There are several candidates the PMC keep an eye on and it will initiate discussion
on their promotion in the nearest time.
## PMC changes:
- Currently 23 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Denis Magda on Sun Sep 27 2015
## Committer base changes:
- Currently 33 committers.
- No new committers added in the last 3 months
- Last committer addition was Igor Sapego at Thu Mar 02 2017
## Releases:
- 2.0.0 was released on Wed May 03 2017
- 2.1.1 was released on Thu Jul 27 2017
## Mailing list activity:
- TODO Please explain what the following statistics mean
for the project. If there is nothing significant in the figures, omit this
section.
- dev@ignite.apache.org:
- 290 subscribers (up 24 in the last 3 months):
- 2982 emails sent to list (3100 in previous quarter)
- ci@ignite.apache.org:
- 4 subscribers (up 4 in the last 3 months)
- issues@ignite.apache.org:
- 26 subscribers (up 1 in the last 3 months):
- 6276 emails sent to list (4899 in previous quarter)
- services@ignite.apache.org:
- 7 subscribers (up 0 in the last 3 months)
- user@ignite.apache.org:
- 526 subscribers (up 67 in the last 3 months):
- 2225 emails sent to list (1787 in previous quarter)
## JIRA activity:
- 760 JIRA tickets created in the last 3 months
- 539 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AI: Report from the Apache Incubator Project [John D. Ament]
Incubator PMC report for August 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 53 podlings incubating. July was a quieter month for the incubator, summer holidays and what not. We executed seven podling releases this month, one podling retired but otherwise no other changes.
* Community
New IPMC members:
- None
People who left the IPMC:
- None
* New Podlings
- None
* Podlings that failed to report, expected next month
- MRQL
- Ratis
* Graduations
The board has motions for the following:
- None
* Retirements
The following podlings retired this month:
- HORN
* Releases
The following releases entered distribution during the month of
July:
- 2017-07-06 Apache Gearpump 0.8.4
- 2017-07-06 Apaceh Traffic Control 2.0.0
- 2017-07-08 Apache Aria Tosca 0.1.0
- 2017-07-11 Apahce HAWQ 2.2.0.0
- 2017-07-18 Apache Griffin 0.1.5
- 2017-07-18 Apache Aria Tosca 0.1.1
- 2017-07-31 Apache Guacamole 0.9.13
* IP Clearance
- We have begun work to clean up IP Clearance policies. First is to make it clear that the preference is ICLAs and CCLAs over SGAs. We have also seen better responsiveness after reasserting that the IPMC owns responsibility for all incoming code donations.
* Legal / Trademarks
* Infrastructure
* Miscellaneous
- A general issue of VPs within other cross functional areas of the ASF reaching out to podlings has started to surface. Specifically, I would like to request that the board supports a request that those areas should be reaching out to podlings directly with issues, escalating to the IPMC due to lack of follow through, rather than approaching the IPMC first. The Security team's model is a perfect example of what to do.
----------------------------------------------------------------------
Table of Contents
BatchEE
DataFu
Edgent
Fluo
Gobblin
Guacamole
Heron
Impala
iota
Joshua
Livy
MRQL
NetBeans
PredictionIO
Pulsar
S2Graph
Slider
Superset
Tamaya
Toree
Unomi
----------------------------------------------------------------------
--------------------
BatchEE
BatchEE projects aims to provide a JBatch implementation (aka JSR352) and a
set of useful extensions for this specification.
BatchEE has been incubating since 2013-10-03.
Three most important issues to address in the move towards graduation:
1. Increase the community probably?
2. -
3. -
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?
Not much as expected being in between "spec" releases.
How has the project developed since the last report?
BatchEE is quite stable and therefore should probably head to graduation soon.
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-09-22
When were the last committers or PPMC members elected?
2016-12-18
Signed-off-by:
[ ](batchee) Jean-Baptiste Onofré
Comments:
[X](batchee) Olivier Lamy
Comments:
[X](batchee) Mark Struberg
Comments: I think we should graduate indeed.
It seems we had some confusion with the LDAP when we added rsandtner as committer.
We need to scan our mailing lists and check what is missing on the official status page.
IPMC/Shepherd notes:
team-list.html - this page shows no members or committers.
I checked private and it looks like the last committer/ppmc add was in Dec 2015.
User ML had questions from only one person at two different times in 2015.
There is activity and it looks like a new release may happen soon.
Dave Fisher
--------------------
DataFu
DataFu provides a collection of Hadoop MapReduce jobs and functions in higher
level languages based on it to perform data analysis. It provides functions
for common statistics tasks (e.g. quantiles, sampling), PageRank, stream
sessionization, and set and bag operations. DataFu also provides Hadoop jobs
for incremental data processing in MapReduce.
DataFu has been incubating since 2014-01-05.
Three most important issues to address in the move towards graduation:
1. Positive IPMC recommendation vote for graduation
2. Address any IPMC feedback regarding graduation
3. Continue 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?
* Community voted positively for graduation from Incubator.
* New contributor opened and fixed DATAFU-124
How has the project developed since the last report?
* Completed maturity evaluation checklist
(https://cwiki.apache.org/confluence/display/DATAFU/Maturity+Evaluation)
* Drafted a graduation resolution
(https://cwiki.apache.org/confluence/display/DATAFU/Graduation+Resolution)
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-03-10
When were the last committers or PPMC members elected?
July 2016 (Eyal Allweil)
Signed-off-by:
[ ](datafu) Ashutosh Chauhan
Comments:
[x](datafu) Roman Shaposhnik
Comments:
best of luck to this podling's graduation. They are a small, but a viable community
[x](datafu) Ted Dunning
Comments: Good luck to the community
IPMC/Shepherd notes:
Project is ready to graduate. I noticed a problem with their answer to QU30 on the Maturity model.
It was in part a documentation issue. Raised it with the project and they are addressing the way that
they are asking for security issues. Raised the documentation issue with ComDev and we fixed it.
Dave Fisher
--------------------
Edgent
Apache Edgent is a programming SDK and micro-kernel style runtime
that can be embedded in gateways and small footprint edge devices enabling
local, real-time, analytics on the continuous streams of data coming
from equipment, vehicles, systems, appliances, devices and sensors of
all kinds (for example, Raspberry Pis or smart phones). Working in
conjunction with centralized analytic systems, Apache Edgent provides
efficient and timely analytics across the whole IoT ecosystem: from the
center to the edge.
Edgent has been incubating since 2016-02-29.
Three most important issues to address in the move towards graduation:
1. Create and expand a diverse community of contributors and committers
around the Edgent project.
2. Attracting at least another independent committer/ppmc member.
3. Finding further real world users of Edgent
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?
* Total, we have 70 subscribers to our mailing list, an improvement
of 5 since the last report.
* We have had a noticeable increase in the number of information-seeking
emails on the mailing list from new Edgent developers.
* A San Francisco meetup has been scheduled for the 20th of September
to demonstrate an Edgent video analytics application which was
initially presented at ApacheCon 2017 (Video Analytics at the Edge:
Fun with Apache Edgent, OpenCV and a Raspberry Pi).
* In addition to Chris Dutz, we have had one non-committer PR merged.
How has the project developed since the last report?
* With the contributions of Christoper Dutz and Dale LaBossiere, the
Edgent build system is undergoing an overhaul to Maven from Gradle.
Maven provides benefits over Gradle, including a more rigid build
structure, and the Maven package system.
* According to JIRA, 13 new issues were added to the project and 6
issues have been resolved or closed between May 2017 and August 2017.
How would you assess the podling's maturity?
Edgent is making slow but consistent progress towards graduation. While we
don't yet meet the diversity requirements, we put emphasis on community
growth through outreach which will ultimately pave the way for additional
committers and contributors.
Additionally, before we graduate it is important that we find users
outside of IBM. As most Edgent committers are employed by IBM, external
stakeholders help ensure long term contribution to the project.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-05-17
When were the last committers or PPMC members elected?
In May 2016, we added two new committers and PPMC members,
Kathy Saunders and Queenie Ma.
Signed-off-by:
[ ](edgent) Daniel Debrunner
Comments:
[x](edgent) Luciano Resende
Comments:
[x](edgent) John Ament
Comments:
[X](edgent) Justin Mclean
Comments:
--------------------
Gobblin
Gobblin is a distributed data integration framework that simplifies common
aspects of big data integration such as data ingestion, replication,
organization and lifecycle management for both streaming and batch data
ecosystems.
Gobblin has been incubating since 2017-02-23.
Three most important issues to address in the move towards graduation:
1. Cut our first release
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?
We are very first steps of the project
How has the project developed since the last report?
* The code has been migrated now to the Apache Git Infra
* Issues has been migrated to Apache Jira Infra
* Site infrastructure has been created (now working on imported the content)
* Discussion on setup Jenkins build
How would you assess the podling's maturity?
The podling is still on early stage. But a lot of progress and activities has been made recently.
[ ] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
N/A
Signed-off-by:
[X](gobblin) Olivier Lamy
Comments:
[](gobblin) Jean-Baptiste Onofre
Comments:
[X](gobblin) Jim Jagielski
Comments:
--------------------
Guacamole
Guacamole is an enterprise-grade, protocol-agnostic, remote desktop gateway.
Combined with cloud hosting, Guacamole provides an excellent alternative to
traditional desktops. Guacamole aims to make cloud-hosted desktop access
preferable to traditional, local access.
Guacamole has been incubating since 2016-02-10.
Three most important issues to address in the move towards graduation:
1. Call community graduation VOTE
2.
3.
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?
Community activity on the mailing lists is still strong and increasing, with
the user@ list now receiving an average of 171 posts per month.
Overall:
Report | Period | Avg. posts (per month)
--------------+--------------------+------------------------
May 2016 (1) | (START) .. 2016-04 | 0 (Not yet migrated)
Aug 2016 (2) | 2016-05 .. 2016-07 | 90
Nov 2016 (3) | 2016-08 .. 2016-10 | 108
Feb 2017 (4) | 2016-11 .. 2017-01 | 129
May 2017 (5) | 2017-02 .. 2017-04 | 164
Aug 2017 (6) | 2017-05 .. 2017-07 | 171
The community is supportive and actively participates in high-level and
development-related discussions on the mailing lists, and in assisting
others.
How has the project developed since the last report?
All items on the podling status page have been completed, the podling name
search has been resolved (name approved), and another release has gone out
smoothly. We will be moving forward with the community graduation VOTE.
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-07-30 (0.9.13-incubating)
When were the last committers or PPMC members elected?
The following committers have been elected since Guacamole began incubation:
* Nick Couchman - 2017-02-09
* Frode Langelo - 2016-04-03
As of the VOTE on 2016-12-09, all committers are implicitly members of the
PPMC.
Signed-off-by:
[ ](guacamole) Jean-Baptiste Onofre
Comments:
[ ](guacamole) Daniel Gruno
Comments:
[X](guacamole) Jim Jagielski
Comments:
[X](guacamole) Greg Trasuk
Comments: The Guacamole podling continues to run their affairs in accordance with ASF policy and practice. Graduation should be imminent.
IPMC/Shepherd notes:
Nearing graduation. The web site needs to address links back to the ASF.
See https://www.apache.org/foundation/marks/pmcs#navigation
I started a thread on the dev list.
Dave Fisher
--------------------
Heron
Heron is a real-time, distributed, fault-tolerant stream processing engine
Heron has been incubating since 2017-06-23.
Three most important issues
- Finish bootstrapping project, IP clearance, initial website
- Expanding the community and adding new committers
- 1st ASF release
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?
- The mailing lists have been setup and we have started using them for
communication. Some issue have been encountered with new mailing list signups
and we are working through this with Infra [2].
- All initial committers have started the process of submitting ICLAs and
getting their ASF accounts setup.
- A Podling name search has been started [1]
How has the project developed since the last report?
- We have setup the incubator status page and are working to get the code
base ready for import to the ASF. An Infra ticket will be created to track
this once we are ready.
Date of last release
- No releases as of yet. Working on code import.
When were the last committers or PPMC members elected?
- N/A, still bootstrapping the project.
[1]: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-128
[2]: https://issues.apache.org/jira/browse/INFRA-14636
Signed-off-by:
[X](heron) Jake Farrell
Comments:
[ ](heron) Jacques Nadeau
Comments:
[ ](heron) Julien Le Dem
Comments:
[X](heron) P. Taylor Goetz
Comments: Podling still getting bootstrapped.
--------------------
Impala
Impala is a high-performance C++ and Java SQL query engine for data stored in
Apache Hadoop-based clusters.
Impala has been incubating since 2015-12-03.
Three most important issues to address in the move towards graduation:
1. Growth of the developer community
2.
3.
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 have been 268 Commits:
git log --format='%ci' | grep -cE '2017-0(5|6|7)'
51 of those commits were by non-committers:
git log --format='%ae %ci' | grep -E '2017-0(5|6|7)' | cut -d ' ' -f 1 | sort | uniq -c | sort -n
There are two new PPMC members:
https://lists.apache.org/list.html?dev@impala.apache.org:dfr=2017-2-1|dto=2017-4-30:%22has%20invited%22
Impala has done a third release with a second release manager. Two CVEs were issued, our first ones under the Apache security guidelines.
How has the project developed since the last report?
There have been big changes to the buffer pool, as outlined in https://lists.apache.org/thread.html/f573698455bf2ff9ac2073c778802d0d5c9f3c8be43ede80614259cb@%3Cdev.impala.apache.org%3E . There have also been big changes landing to the RPC layer to improve scalability. Impala now has TABLESAMPLE to allow running queries on only a small percentage of the table for experimenting with queries quickly, and it now works on ADLS.
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
[X] Nearing graduation
[ ] Other:
Once the developer community has grown a bit, Impala will be ready
to contemplate graduation.
Date of last release:
2017-06-16
When were the last committers or PPMC members elected?
2017-07-17
Signed-off-by:
[ ](impala) Tom White
Comments:
[x](impala) Todd Lipcon
Comments:
[x](impala) Carl Steinbach
Comments:
[ ](impala) Brock Noland
Comments:
--------------------
iota
Open source system that enables the orchestration of IoT devices.
iota has been incubating since 2016-01-20.
Three most important issues to address in the move towards graduation:
1. An initial release of iota
2. Building a more active community
3. Consistency in the discussions on mailing lists/ steady flow of source code
contributions
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?
@crostofolini and @rafaelweingartner are working on integrating the
Spring framework into iota (pull request 35)
We are waiting on a jar file to be removed from the test suit so that
an initial release of the software can be produced. (The jar file is related to
iota tests - need committer to publish the source code - enabling us to remove the
jar artifact enabling the initial release of the software).
The initial release will proceed without the Spring Framework
Integration. We will add this in a future release.
Ticket's are in place for the initial release.
How has the project developed since the last report?
Interest in using iota (including the Spring Framework) outside the committer group
The email reflectors for dev and users have become more active.
New functionality was added to iota - global performers.
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:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Yes - Barbara Gomes was added as a committer on 12/02/2016
Signed-off-by:
[ ](iota) Daniel Gruno
Comments:
[ ](iota) Sterling Hughes
Comments:
[X](iota) Justin Mclean
Comments: Still having issues making a release.
[ ](iota) Hadrian Zbarcea
Comments:
--------------------
Joshua
Joshua is a statistical machine translation toolkit
Joshua has been incubating since 2016-02-13.
Three most important issues to address in the move towards graduation:
1. Make another Apache Joshua incubating release.
2. Identifying specific use cases that we might excel at.
3. Attracting active developers and users.
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?
The community mailing lists have seen a few new users.
Questions have been answered in reasonable time. Community
building is probably the biggest challenge for Joshua right
now.
Tommaso Teofili and Suneel Marthi, presented 'Embracing Diversity:
Searching Over multiple languages' on June 12, 2017 at Berlin Buzzwords,
Berlin - demonstrating machine translation using Apache Joshua.
How has the project developed since the last report?
Apache Joshua 6.1 (Incubating) was released, which is the first
Apache release for Joshua. The community is actively discussing
the roadmap and where Joshua should be in the near future.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[X] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2017-06-22
When were the last committers or PPMC members elected?
- 2016-11-16 Michael A. Hedderich (mhedderich) joins the Joshua PPMC +
Committership.
- 2016-11-16 Tobias Domhan (tdomhan) joins the Joshua PPMC + Committership.
- 2016-11-02 Max Thomas (mthomas) joins the Joshua PPMC + Committership.
Signed-off-by:
[ ](joshua) Paul Ramirez
Comments:
[X](joshua) Lewis John McGibbney
Comments:
[X](joshua) Chris Mattmann
Comments:
I updated status to nearing graduation. The community has grown and we have made a release. Not sure what else we need to do in the Incubator, but willing to wait a few months to sort it out.
[X](joshua) Tom Barber
Comments:
The release was well organized and delivered thanks to Lewis and Tommaso, it feels to me like the Joshua developers need to be a little more proactive. As the report points out, community building is the biggest issue, I'm going to spend some time in the near future working with the PPMC to see what integrations, tutorials and demos we can do to drive developers and adoption which will hopefully expand the community.
--------------------
Livy
Livy is web service that exposes a REST interface for managing long running
Apache Spark contexts in your cluster. With Livy, new applications can be
built on top of Apache Spark that require fine grained interaction with many
Spark contexts.
Livy has been incubating since 2017-06-05.
Three most important issues to address in the move towards graduation:
N/A
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?
The community is working on moving the project to Apache.
How has the project developed since the last report?
The community made a big progress moving the project to Apache (https://issues.cloudera.org/projects/LIVY/issues/LIVY-373).
Two new features (Livy Web UI and improve ACL) has merged.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
N/A
Signed-off-by:
[ ](livy) Bikas Saha
Comments:
[ ](livy) Brock Noland
Comments:
[x](livy) Luciano Resende
Comments:
[ ](livy) Jean-Baptiste Onofre
Comments:
--------------------
MRQL
IPMC/Shepherd notes:
johndament: Podling is expecting to retire soon.
--------------------
NetBeans
NetBeans is a development environment, tooling platform and application
framework.
NetBeans has been incubating since 2016-10-01.
Three most important issues to address in the move towards graduation:
1. Legal process to hand over code. Still pending and frustrating to all concerned.
2. Possibility that NetBeans 1st donation will not be done in time to release together with JDK 9.
3. Slowness/thoroughness of the process of handing over code from Oracle.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The process will take time.
How has the community developed since the last report?
Various discussions about specific plugins, etc, and about the logo and website.
How has the project developed since the last report?
Progress is being made on the Oracle side, the progress is continual, but slow.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
No releases as of yet.
When were the last committers or PPMC members elected?
Signed-off-by:
[X](netbeans) Ate Douma
Comments: Latest news is that Oracle is now at the final stage,
reviewing the AL2.0 and CCLA itself, needed for the 1st code donation.
So hopefully we finally can import and validate the 1st donation soon.
[ ](netbeans) Bertrand Delacretaz
Comments:
[ ](netbeans) Emmanuel Lecharny
Comments:
[ ](netbeans) Daniel Gruno
Comments:
[X](netbeans) Mark Struberg
Comments: NetCAT (Community Acceptance Testing) got set up. Could be a good chance to broaden the community.
--------------------
PredictionIO
PredictionIO is an open source Machine Learning Server built on top of state-
of-the-art open source stack, that enables developers to manage and deploy
production-ready predictive services for various kinds of machine learning
tasks.
PredictionIO has been incubating since 2016-05-26.
Three most important issues to address in the move towards graduation:
1. Establish a formal release schedule and process, allowing for
dependable release cycles in a manner consistent with the Apache way.
2. Grow the community to establish diversity of background.
3. Transition remaining former PredictionIO users from google-groups to
ASF mailing lists.
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?
1. Our new committers have been actively contributing new features and
bug fixes to the core codebase.
2. There are new local meetups about PredictionIO in Japan.
3. There has been growing integration effort of PredictionIO on the
Heroku platform.
4. Increased traffic on the user mailing list.
How has the project developed since the last report?
1. Around 40 pull requests have been accepted and merged since 0.11's
release, from both committers and contributors.
2. On track to stick with a bi-monthly release schedule. Proposing a new
release for the beginning of August.
3. Many cleanup effort into TLP 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:
2017-04-25
When were the last committers or PPMC members elected?
Mars Hall was elected as committer and PMC member on July 8, 2017.
Signed-off-by:
[X](predictionio) Andrew Purtell
Comments:
[ ](predictionio) James Taylor
Comments:
[ ](predictionio) Lars Hofhansl
Comments:
[x](predictionio) Luciano Resende
Comments:
[ ](predictionio) Xiangrui Meng
Comments:
[ ](predictionio) Suneel Marthi
Comments:
--------------------
Pulsar
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management for
subscribers, and cross-datacenter replication.
Pulsar has been incubating since 2017-06-01.
Three most important issues to address in the move towards graduation:
1.Make an Apache Release
2.Set up a test cluster to be able to run system tests
3.Grow the community with new Committers/PPMC members.
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?
The community added one contributor. There is a healthy discuss on issues related to development, tools and processes among the community members.
How has the project developed since the last report?
6 authors have pushed 21 commits to master and 31 commits to all branches.
The first release from the incubator is in process. A Release Candidate is up for vote, scheduled to close on Aug 3. The project has completed setting up its website and project documentation. The community has added a slack
channel.
How would you assess the podling's maturity?
The podling is progressing well on its way to it's first Apache release (1.19.0-incubating). There is good participation in governance and in contributions.
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:
2017-06-17, v 1.18
When were the last committers or PPMC members elected?
Signed-off-by:
[X](pulsar) Dave Fisher
Comments: Note v1.18 was a Github release of pre-incubation code. A release vote was just sent to general@incubator.
[X](pulsar) Jim Jagielski
Comments:
[X](pulsar) P. Taylor Goetz
Comments: Also note that the download page has a note to the effect that the 1.18 release isn't an
Apache release. The message could be worded better, but at least it is there.
[ ](pulsar) Francis Liu
Comments:
--------------------
S2Graph
S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.
S2Graph has been incubating since 2015-11-29.
Three most important issues to address in the move towards graduation:
1. Make a second release.
2. Attract more users and contributors.
3. Build the developer community in both size and diversity.
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?
* There have been 45 Commits
- All of 45 commits were by single active committers
* Mailing list has been quite.
- Discuss next release schedule and scope.
How has the project developed since the last report?
* Focused on Tinkerpop3 integration.
- Added Global Index layer.
- Full text predicate support.
- Provide Gremlin plugin to integrate gremlin-console, gremlin-server.
- S2Graph is now TinkerPop compliant.
* Discuss next release schedule and scope.
- Agrees to release with Tinkerpop3 integration.
- Release manager is working on building release candidate.
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-01
When were the last committers or PPMC members elected?
None
Signed-off-by:
[X](s2graph) Andrew Purtell
Comments: We need to find more mentors for this podling. In the past
Sergio was helpful but he hasn't been around much recently. I would
resign but am lurking as mentor of last resort.
[ ](s2graph) Seetharam Venkatesh
Comments:
[ ](s2graph) Sergio Fernández
Comments:
--------------------
Slider
Slider is a collection of tools and technologies to package, deploy, and
manage long running applications on Apache Hadoop YARN clusters.
Slider has been incubating since 2014-04-29.
Three most important issues to address in the move towards graduation:
1. Apache Slider community/PPMC has voted to move portions of Slider into
Apache Hadoop YARN as modules. It is possible that the remaining pieces
will be moved at a later point in time or become obsolete or evolve to
work closely with YARN. Slider PPMC will decide what makes the most
sense as we progress through this exciting time.
2. Getting more external users
3. Growth of a diverse set of developers/committers/PMC members is also
crucial towards the final state of Slider
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?
Mailing list activity has been lower due to the bulk of the development
moving to an Apache Hadoop branch. Questions on usage and issues
encountered by end users keep coming at regular intervals, keeping the DL
fairly active.
How has the project developed since the last report?
Work continues in parallel on the Apache Hadoop yarn-native-services
branch and on the Slider podling. The bulk of the work has been in
yarn-native-services, while a few Slider patches (related to critical
issues or agent-only issues) have been committed as well.
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-03-23 slider-0.92.0-incubating
When were the last committers or PPMC members elected?
2015-07-07: Yu (Thomas) Liu
Signed-off-by:
[ ](slider) Arun C Murthy
Comments:
[ ](slider) Devaraj Das
Comments:
[ ](slider) Jean-Baptiste Onofré
Comments:
[ ](slider) Mahadev Konar
Comments:
[X](slider) Vinod Kumar Vavilapalli
Comments: More work happening in Apache Hadoop YARN project to finish the module move of Slider but it is opaque. Will prod the community to send periodic dev-list updates demonstrating the current progress in this process.
IPMC/Shepherd notes:
johndament: Based on the description, as well as the little bit of information I've been able to get out of the Slider community, it seems that while there is a Slider community they're not actively working on Slider's codebase. My recommendation is probably to retire the Slider community if they cannot be absorbed into the Hadoop TLP.
--------------------
Superset
Superset is an enterprise-ready web application for data exploration, data
visualization and dashboarding.
Superset has been incubating since 2017-05-21.
Three most important issues to address in the move towards graduation:
1. Grow the community and enroll new committers.
2. Plan and execute our first Apache release
3. Address the challenge that React is no longer allowed in Apache projects
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* Superset is heavily reliant upon React, however React has the same patent clause as RocksDB, which ASF had condoned use of until RocksDB backtracked and removed that clause. Our team is concerned about the implications and we are looking for guidance (https://issues.apache.org/jira/browse/LEGAL-320)
* The team is working on finishing up all the items on the Incubation Checklist.
How has the community developed since the last report?
* Organic growth of our Github contributors (148), forks (2,153), watchers
(770) and stars (15,075)
How has the project developed since the last report?
* The code repository now lives at https://github.com/apache/incubator-superset on Apache’s infrastructure
* We have migrated the project website to the Apache website: http://superset.apache.org/
* A healthy, constant flow of bug fixes, quality improvements and new features, take a look at the project’s Pulse on Github for more details
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 official release yet since being voted into Apache
Incubation. (Planning for the first Apache release in Q3, 2017)
When were the last committers or PPMC members elected?
* Project is still functioning with the initial set of committers
Signed-off-by:
[X](superset) Ashutosh Chauhan
Comments:
[ ](superset) Luke Han
Comments:
[X](superset) Jim Jagielski
Comments:
--------------------
Tamaya
Tamaya is a highly flexible configuration solution based on an modular,
extensible and injectable key/value based design, which should provide a
minimal but extendible modern and functional API leveraging SE, ME and EE
environments.
Tamaya has been incubating since 2014-11-14.
Three most important issues to address in the move towards graduation:
1. Release version 0.3 of Tamaya Core and Extensions
2. Start a new Howto/blog series about Tamaya and its new features
3. Use attention of these releases to gather new committers
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
We'd like to graduate soon.
How has the community developed since the last report?
No changes, due to holiday season a slightly lower activity.
How has the project developed since the last report?
Release of Core 0.3 is out, extensions just passed the IPMC approval.
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
[X] Nearing graduation
[ ] Other:
Date of last release:
2017-08-01
When were the last committers or PPMC members elected?
P. Ottlinger at 2016-04-24.
Signed-off-by:
[X](tamaya) John D. Ament
Comments:
[ ](tamaya) David Blevins
Comments:
--------------------
Toree
Toree provides applications with a mechanism to interactively and remotely
access Apache Spark.
Toree has been incubating since 2015-12-02.
Three most important issues to address in the move towards graduation:
1. More discussion and engagement on the mailing list
2. Community growth
3. Continue to make releases
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* No issues require attention at this time.
How has the community developed since the last report?
* The community is discussing and starting activities to
produce a Toree 0.2.0-incubating release.
How has the project developed since the last report?
* Identifying issues and working on PR reviews for
0.2.0-incubating 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:
2017-02-21
When were the last committers or PPMC members elected?
* Ryan Blue was added to the PMC on 2017-04-03
Signed-off-by:
[x](toree) Luciano Resende
Comments:
[ ](toree) Reynold Xin
Comments:
[x](toree) Hitesh Shah
Comments:
[ ](toree) Julien Le Dem
Comments:
[x](toree) Ryan Blue
Comments:
--------------------
Unomi
Unomi is a reference implementation of the OASIS Context Server specification
currently being worked on by the OASIS Context Server Technical Committee. It
provides a high-performance user profile and event tracking server.
Unomi has been incubating since 2015-10-05.
Three most important issues to address in the move towards graduation:
1. During the three last months, we did bunch of bug fixes and we are preparing new maintenance release. We also working on a feature branch with major dependencies update (Apache Karaf 4, ...) and refactoring on some Unomi internals (like the tags).
2. If we did good improvements on the user community front, we would like to increase the developer community and see more contributions.
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?
The user community grew up (according messages and feedback we go). We think that we are getting close to graduation and we will define an action plan with the topics to address for this.
How has the project developed since the last report?
We are still preparing 1.2.0-incubating
release including more bug fixes.
We also started a 2.0.0-incubating branch with major dependencies update (Apache Karaf 4.x, Elasticsearch 5.x, ...) and refactoring of some internals.
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-10-03
When were the last committers or PPMC members elected?
2017-01-23
Signed-off-by:
[ ](unomi) Bertrand Delacretaz
Comments:
[X](unomi) Jean-Baptiste Onofre
Comments:
IPMC/Shepherd notes:
johndament: Just for clarification, Unomi has PPMC members, not a PMC. In addition, their website continues to use the old incubator logo. On the flip side, activity is high on the mailing lists so I'm a bit surprised it took extra effort to get a report submitted. Keep up the activity levels.
-----------------------------------------
Attachment AJ: Report from the Apache jUDDI Project [Alex O'Ree]
jUDDI (pronounced "Judy") is an open source Java implementation of the
Universal Description, Discovery, and Integration (UDDI v3)
specification for (Web) Services. The jUDDI project includes Scout.
Scout is an implementation of the JSR 93 - Java API for XML Registries
1.0 (JAXR).
jUDDI
- All mailing lists have had low traffic this quarter with some additional out of band email traffic from one user.
- 3.3.4 Released Feb 11, 2017, maintenance and bug fixes.
Scout
- No release this period, no development took place.
- No JAXR related questions on the mailing list.
Last PMC addition and new committer April 3, 2013 (Alex O'Ree)
Last Release jUDDI-3.3.4, Feb 11, 2017
Next Release jUDDI-3.3.5, Planned for Dec 2017
There are no issues that require the boards attention at this time.
Low development activity is a factor for low mailing list volume, but in all
likelihood, it's from a general lack of interest in the protocol.
There are enough active PMC members to approve releases and respond to potential
security issues. There were no issue raised since the last report.
-----------------------------------------
Attachment AK: Report from the Apache Kafka Project [Jun Rao]
Apache Kafka is a distributed streaming platform for efficiently storing and
processing a large number of records in real time.
Development
===========
We released 0.11.0.0 on Jun. 28, 2017, which includes 32 KIPs, over 400 bug fixes and improvements,
and more than 700 pull requests. The main features in this release include exactly-once semantic,
new admin apis, request quotas, etc.
We are actively working on new features such as JBOD, delegation tokens and improvements of
the controller. The next release will be 1.0.0, a big milestone in Kafka.
Community
===========
Lots of activities in the mailing list. We have 2474 subscribers in the user mailing
list, up 44 in the last 3 months. We have 1705 emails in the user mailing list in
the last 3 months, about the same as 1736 in the previous cycle. We have 1003 subscribers
in the dev mailing list, up 24 in the last 3 months. We have 6526 emails in the dev mailing
list in the last 3 months, up from 6248 in the previous cycle.
We elected one new committer, Damian Guy on Jun. 9, 2017. We elected two new PMC members, Ismael Juma
on Jul. 5, 2017 and Jason Gustafson on Jul. 11, 2017.
We plan to have a 1-day Kafka Summit in SF on Aug 28.
Releases
===========
0.11.0.0 was released on Jun. 28, 2017.
-----------------------------------------
Attachment AL: Report from the Apache Knox Project [Larry McCay]
## Description
The Apache Knox Gateway is a REST API Gateway for interacting with Apache
Hadoop clusters. The Knox Gateway provides a single access point for all
REST/HTTP interactions with Apache Hadoop clusters.
## Issues
There are no issues requiring board attention at this time
## Activity
The Apache Knox team is in the process of an active VOTE for our 0.13.0 release.
While we were going to also try and make this our 1.0.0 release there were a
couple reasons to delay this milestone. We discovered a couple issues
that required a good bit of investigation and will require rigorous testing from
the community before they can be considered properly complete and ready. We also
took a good bit of time to try and pull in contributions from the community that
many users have been looking for. Most notably in the service definitions for proxying UIs.
## Health report:
We have continued to use the KIP-# pages to drive the primary focus of each
release and feel it is working well. The 0.13.0 release was primarily
focused on the addition of the port-mapping feature and extending UI proxying
capabilities. It also fixes a number of bugs.
The current level of collaboration is healthy and encouraging within the
community on both mailing lists and JIRAs.
## Releases
- Last release was 0.12.0: 2017-03-20 Added support for new APIs and UIs, KnoxToken API,
release module for KnoxShell, and fixed a number of bugs - through
~35 commits.
- 0.13.0: Currently pending VOTE of the first RC
## PMC changes:
- Currently 14 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Sandeep More on Wed Feb 08 2017
- Have an active VOTE in progress to add one committer/PMC member
## Committer base changes:
- Currently 17 committers.
- No new committers added in the last 3 months
- Last committer addition was Sandeep More at Thu Jan 19 2017
- Active VOTE in progress for one committer (non-PMC)
## Mailing List Activity
- dev@knox.apache.org:
- 80 subscribers (up 3 in the last 3 months):
- 864 emails sent to list (897 in previous quarter)
- user@knox.apache.org:
- 103 subscribers (up 10 in the last 3 months):
- 42 emails sent to list (63 in previous quarter)
## JIRA activity:
- Jira: 991 total, +14 -16 (last 30 days)
- 57 JIRA tickets created in the last 3 months
- 57 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AM: Report from the Apache Kylin Project [Luke Han]
## Description:
Apache Kylin is an open source Distributed Analytics Engine designed
to provide SQL interface and multi-dimensional analysis (OLAP) on
Hadoop supporting extremely large datasets.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- Hadoop & Kylin Meetup hosted in Beijing on 2017-07-14
- Alberto Ramón presented Kylin topic
at Docker Meetup on 2017-06-15
- Yang Li presented Keynote about Apache Kylin
at Tableau User Conf Shenzhen on 2017-07-12
- Luke Han presented Keynote about Apache Kylin
at Strata Hadoop World Beijing on 2017-07-15
- Dong Li presented Apache Kylin 2.x
at Strata Hadoop World Beijing on 2017-07-15
- Luke Han presented Keynote about Apache Kylin
at Strata Hadoop World Beijing on 2017-07-15
- Kaige Liu presented Kylin on AWS
at AWS Summit China in Beijing on 2017-07-26
- Dayue Gao presented Kylin topic
at Druid Meetup Beijing on 2017-08-05
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
## Committer base changes:
- Currently 28 committers
- No new committers in the last 3 months.
- Last committer addition: Fri Apr 28 2017 (Alberto Ramón)
## Releases:
- Last release was 2.0.0, released on Sun Apr 30 2017
## Mailing list activity:
- dev@kylin.apache.org:
- 370 subscribers (up 33 in the last 3 months)
- 778 emails sent in the past 3 months, 794 in the previous cycle
- issues@kylin.apache.org:
- 71 subscribers (up 9 in the last 3 months)
- 1258 emails sent in the past 3 months, 921 in the previous cycle
- user@kylin.apache.org:
- 286 subscribers (up 10 in the last 3 months)
- 327 emails sent in the past 3 months, 232 in the previous cycle
## JIRA activity:
- 180 JIRA tickets created in the last 3 months
- 124 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AN: Report from the Apache Lens Project [Amareshwari Sriramadasu]
## Description:
Lens provides an Unified Analytics interface. Lens aims to cut the Data
Analytics silos by providing a single view of data across multiple tiered
data stores and optimal execution environment for the analytical query. It
seamlessly integrates Hadoop with traditional data warehouses to appear like
one.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Fact to fact union and cube segmentation features are stabilized
Virtual fact feature is added
Release verification for 2.7 is going on.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Puneet Gupta on Tue Sep 20 2016
## Committer base changes:
- Currently 22 committers.
- No new committers added in the last 3 months
- Last committer addition was Archana H at Sat May 21 2016
## Releases:
- Last release was 2.6 on Tue Oct 25 2016
-----------------------------------------
Attachment AO: Report from the Apache Libcloud Project [Tomaž Muraus]
## Description:
Libcloud is a Python library that abstracts away the differences among
multiple cloud provider APIs.
## Issues:
There are no issues which require board attention at this time.
## Activity:
Libcloud v2.1.0 has been released in July. This release included various
changes from the committers and also many contributions from the community.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Jeff Dunham on Sat May 21 2016
## Committer base changes:
- Currently 19 committers.
- No new committers added in the last 3 months
- Last committer addition was Jeff Dunham at Sat May 21 2016
## Releases:
- 2.1.0 was released on Mon Jul 17 2017
- 2.0.0 was released on Tue Apr 25 2017
- 2.0.0-rc2 was released on Fri Apr 07 2017
## JIRA activity:
- 19 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
(This information is not really a good reflection of the activity,
because majority of our contributions primarily come via Github which offers
lower barrier to entry)
-----------------------------------------
Attachment AP: Report from the Apache Logging Services Project [Ralph Goers]
The Apache Logging Services Project creates and maintains open-
source software related to application logging.
Currently there are no issues which require the board's attention.
- Community
Logging Services remains an active project. The overall community is healthy
and friendly.
After combining the dev mailing lists the number of subscribers has
continued to decline, however the amount of email traffic appears to
have increased although it is hard to tell how much since GitHub and
Jira generate a lot of noise.
In general, all subprojects are still healthy.
- Project Branding Requirements
All components except Chainsaw meet the branding requirements. As noted
below, work has begun to address these issues.
- Last three community changes
* Curt Arnold resigned from the PMC and as a committer on May 4, 2017
* Thorsten Schöning was added as a committer on Mar 6, 2017
* Jonathon Davies was added as a committer on Jan 8, 2017
- Releases
* Log4j-Scala 11.0 (Jul 23, 2017)
* Log4j 2.8.2 (Apr 4, 2017)
* Log4net 2.0.8 (Mar 10, 2017)
- Subproject summaries
Log4j 2: Active. Work to support Java 9 has continued. A new release
should be available prior to Java 9 being released. A few individuals
have recently started contributing and the PMC continues to monitor
their progress towards becoming committers.
Log4J-Scala: The Scala support was moved out of Log4j into its own
sub-project so that its needs could be better supported. While a release
has been created the web site for the project still needs to be integrated
into the Log4j and/or Logging sites.
Log4net: Moderately active with 1 recent release. Effort is being put into
automating the build process aiming for a pipeline to automate as much as
possible.
Log4cxx: Log4cxx still has not had a new release but discussion continue
on the dev list.
Log4php: No activity this quarter.
Chainsaw: The PMC has begun to address the branding issues. A new version
of the site was generated that addresses the missing copyrights. However,
the latest artifacts (from 2006) are embedded in the web site and must
be moved to the proper distribution location. A new release will be
created to address that. Discussions have also taken place with regard to
providing better integration with Log4j 2.
-----------------------------------------
Attachment AQ: Report from the Apache MADlib Project [Aaron Feng]
## Description:
- The Apache MADlib is a scalable, Big Data, SQL-driven machine learning framework for Data Scientists.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The bulk of the community activity is now focused on post-graduation tasks of promoting MADlib to the ASF's TLP status. This includes working on code base, website, wiki, and ASF infrastructure.
- We expect to finalize the trademark transfer from Pivotal to ASF within the
month of August, 2017.
- Ed Espino volunteered to drive the first TLP release of MADlib 1.12 which is expected to happen within the next couple of months.
## Health report:
The project has just graduated to the status of a TLP at ASF. The community is small but very engaged with robust mailing list traffic, interest in doing frequent releases and a bunch of new functionality being developed by contributors. The number of committers actively contributing to the code/documentation has been steady and remains at a level of half a dozen active committers each month. Since the project has just graduated we haven't had a chance to actively grow our PMC roster, but it must be noted that at this point all of our active committers are also PMC members. Of course, we will constantly be on a lookout for new community members to be invited either as committers or PMC.
## PMC changes:
- PMC has been just formalized as part of the graduation resolution
- Currently 13 PMC members.
## Committer base changes:
- Currently 13 committers.
- No new committers added in the last 3 months
- Last committer addition was Nandish Jayaram on 2016-09-08
## Releases:
- v1.11.0-incubating released on 2017-05-17
- v1.10.0-incubating released on 2017-03-10
- v1.9.1-incubating released on 2016-09-19
## Mailing list activity:
Mailing activity remains steady with 203 posts to dev@ and 23 posts to user@
## JIRA Statistics:
- 10 JIRA tickets created in the last month
- 3 JIRA tickets resolved in the last month
-----------------------------------------
Attachment AR: Report from the Apache ManifoldCF Project [Karl Wright]
Project description
==============
ManifoldCF is an effort to provide an open source framework for connecting
source content repositories like Microsoft Sharepoint and EMC Documentum, to
target repositories or indexes, such as Apache Solr, OpenSearchServer or
ElasticSearch. ManifoldCF also defines a security model for target
repositories that permits them to enforce source repository security
policies.
Releases
========
ManifoldCF graduated from the Apache Incubator on May 16, 2012. Since then,
there have been numerous major releases, including a 2.7 release on
April 20, 2017. The next major release is scheduled for August 30, 2017,
and is on track.
Committers and PMC membership
=============================
The last committer we signed up was Markus Schuch on December 2, 2016. The last
PMC member was Rafa Haro, voted in on August 31, 2015. In response to the
Board's inquiry in February, we've been looking for PMC members and there are
some potential ones among our newer committers, but it's too soon to know yet.
Summer has impacted both the contribution rate to the project and the rate
of engagement. Generally we like to see long-term interest in the project before
we offer PMC memberships.
Mailing list activity
=====================
Mailing list activity has been moderate this quarter. Major development has been
taking place around a set of new output connectors. Issues reported have been
centered on the Documentum connector, which surprisingly remains active without
significant modifications for most of a decade now. I am unaware of any mailing list
question that has gone unanswered.
Outstanding issues
==================
No outstanding infrastructure issues are known at this time.
Branding
========
We continue to believe we are now compliant with Apache branding guidelines,
with the possible exception of (TM) signs in logos from other Apache products
that don't have any such marks. We received word that the ManifoldCF
trademark application (US TM App No. 86583085 for "MANIFOLDCF" in Cl. 9 | DLA
Ref: 393457-900118) has been accepted.
-----------------------------------------
Attachment AS: Report from the Apache Marmotta Project [Jakob Frank]
-----------------------------------------
Attachment AT: Report from the Apache MetaModel Project [Kasper Sørensen]
## Description:
Providing a common interface for discovery, exploration of metadata and
querying of different types of data sources.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Two milestone/RC versions of MetaModel 5.0 has been released.
- A new subproject "Membrane" was founded, first release pending.
## Health report:
The MetaModel project is generally doing much better now than
previous two quarters. The two activity points above seem to have
ignited a lot of new enthusiasm and traffic on the mailing lists.
Also, new contributors are showing up with PRs on GitHub and good
issue reports on JIRA.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dennis Du Krøger on Mon Sep 05 2016
## Committer base changes:
- Currently 11 committers.
- No new committers added in the last 3 months
- Last committer addition was Dennis Du Krøger at Thu Oct 15 2015
## Releases:
- 5.0-RC1 was released on Sat May 20 2017
- 5.0-RC2 was released on Thu Jun 15 2017
## Mailing list activity:
- The activity on the dev@ and user@ mailing lists have increased significantly.
- dev@metamodel.apache.org:
- 77 subscribers (down -1 in the last 3 months):
- 228 emails sent to list (9 in previous quarter)
- issues@metamodel.apache.org:
- 8 subscribers (up 1 in the last 3 months)
- user@metamodel.apache.org:
- 20 subscribers (up 4 in the last 3 months):
- 10 emails sent to list (0 in previous quarter)
## JIRA activity:
- 13 JIRA tickets created in the last 3 months
- 10 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AU: Report from the Apache MINA Project [Jean-François Maury]
-----------------------------------------
Attachment AV: Report from the Apache Mynewt Project [Justin Mclean]
Mynewt is a real-time operating system for constrained embedded systems like
wearables, lightbulbs, locks and doorbells. It works on a variety of 32-bit
MCUs (microcontrollers), including ARM Cortex-M and MIPS architectures.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- Move to TLP complete
- Made first release as a TLP
- Community work in several areas including new PWM driver and support for
other boards
## Health report:
- PMC and committers are active
- Users questions and contributor's pull requests are dealt with in a timely
manner
## PMC changes:
- Currently 19 PMC members
- No new PMC members added since last report
- Last PMC addition was everyone on 21st June
## Committer base changes:
- Currently 23 committers
- No new committers added since last report
- Last committer addition was Jacob Rosenthal on 13th June 2017
## Releases:
- 1.1 was released on Aug 01 2017
## Mailing list activity:
- Activity a little down on last month.
## JIRA activity:
- Activity less than last month with more JIRAs closed than raised.
-----------------------------------------
Attachment AW: Report from the Apache Oltu Project [Antonio Sanso]
-----------------------------------------
Attachment AX: Report from the Apache Oozie Project [Robert Kanter]
## Description:
- Oozie is a workflow scheduler system to manage Apache Hadoop jobs.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The OOZIE-1770 Oozie on Yarn project has been finally
merged into the trunk branch! OOZIE-2889 is tracking some
followups.
- Other misc bug/usability fixes and improvements are still
ongoing.
- An Oozie 5.0.0 release is still planned for sometime before
the end of this year, with Oozie on Yarn as the flagship feature.
## PMC changes:
- Currently 16 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ryota Egashira on Mon Aug 10 2015
## Committer base changes:
- Currently 23 committers.
- New commmitters:
- Attila Sasvári was added as a (full) committer on Mon Jul 17 2017
- Last committer addition was Satish Saley at Mon Jan 02 2017
## Releases:
- Last release was 4.3.0 on Thu Dec 01 2016
## JIRA activity:
- 144 JIRA tickets created in the last 3 months
- 87 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AY: Report from the Apache Open Climate Workbench Project [Michael James Joyce]
Apache Open Climate Workbench is a tool for scalable comparisons of remote
sensing observations to climate model outputs.
OCW successfully pushed out v1.2 at the end of April and is working towards our
next release. Discussion started towards the end of July on which features we
would like to see integrated, so I expect we'll see a release upcoming in the
next month or two.
Activity on the lists "bathtubbed" a good bit during this last quarter. We saw
a good amount of development in May and into June which went to near nothing in
July. Activity has started picking up a bit more in August so far, but it's
something we should keep an eye on.
We have had a few new faces over the last quarter show up. Most have gone as
quickly as they showed up, but we are keeping an eye out for people who are
sticking around so we can reach out and ask them to join the PMC/Contributors.
Issues for the Board:
None
When was the last committer or PMC member elected:
- Ibrahim Jarif - 26 April 2016
- Omkar Reddy - 20 January 2016
When was the last release:
- 1.2.0 - 24 April 2017
- 1.1.0 - 27 July 2016
-----------------------------------------
Attachment AZ: Report from the Apache Perl Project [Philippe M. Chiasson]
--- mod_perl --
No new mod_perl 2.x releases since 2016-10.
-- Activity --
mod_perl continues to be a healthy development community, though
as a mature and stable product development moves at a naturally
slower pace than in years past. Bugs are found and discussed and
fixes are applied with due consideration for our production userbase.
-- Users --
The mod_perl users list is seeing little activity, as usual.
Patches and bug reports are few, but keep on coming.
-- Commiters --
Currently 22 committers.
No new changes to the committer base since last report.
Last Commiter addition was Jan Kaluza in April 2013
-- PMC --
Currently 11 PMC members.
No new PMC members added in the last 3 months
Last PMC addition was Steve Hay on Wed Feb 29 2012
-----------------------------------------
Attachment BA: Report from the Apache Phoenix Project [James R. Taylor]
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics
for Hadoop using Apache HBase as its backing store.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- PhoenixCon 2017 was hosted by Salesforce on June 13th. Attendance was
good (~75 people) and we had some good community discussions.
- Phoenix 4.11 was released in late June and work.
- Work toward Phoenix 4.12 is well underway with lots of stabilization
around mutable secondary indexes and some solid contributions from
potential new committers in the area of table sampling and approximate
count.
## Health report:
- The project is healthy and continues to grow as users look for easy
ways to gain insight over and manage their ever-increasing Hadoop
data through standard SQL and JDBC APIs.
## PMC changes:
- Currently 24 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Josh Elser on Tue Aug 09 2016
## Committer base changes:
- Currently 31 committers.
- No new committers added in the last 3 months
- Last committer addition was Geoffrey Jacoby at Sun Feb 26 2017
## Releases:
- Last release was 4.11.0 on Tue Jun 20 2017
## Mailing list activity:
- Mailing list activity is steady.
- dev@phoenix.apache.org:
- 226 subscribers (down -1 in the last 3 months):
- 3048 emails sent to list (2033 in previous quarter)
- user@phoenix.apache.org:
- 546 subscribers (down -1 in the last 3 months):
- 280 emails sent to list (345 in previous quarter)
## JIRA activity:
- 233 JIRA tickets created in the last 3 months
- 160 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BB: Report from the Apache POI Project [Dominik Stadler]
Report from the Apache POI committee [Dominik Stadler]
## Description:
- Apache POI is a Java library for reading and writing Microsoft Office file
formats
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- There is constant activity in commits, bugfixes, feature-work and also
user questions.
Work happened for handling broken files better, found via fuzzing-efforts
done by Tim Allison, HPSF improvements, bugfixes, removing deprecated code,
and general improvements.
Discussions about depending on commons-math for some functionality are
ongoing.
We released 3.17-beta1 in June and are planning a 3.17 at the end of summer.
We are planning to target a 4.0 release after that which will require JDK 7
(compared to JDK 6 now) and might remove some more deprecated APIs.
## Health report:
- The last few months we saw a constant stream of new bug reports/feature
requests which indicates that the popularity of Apache POI is still very
good. Questions via email or on Stackoverflow usually get answers quickly,
regularly even from people not actively involved in Apache POI development.
## PMC changes:
- Currently 29 PMC members.
- PJ Fanning was added to the PMC on Fri Jun 23 2017
## Committer base changes:
- Currently 36 committers.
- PJ Fanning was added as a committer on Fri Jun 23 2017
## Releases:
- 3.17-beta1 was released on Wed Jun 28 2017
## Mailing list activity:
- Mostly constant membership numbers, a few un-subscribers for this
period, not apparent reason for that. POI is a mature project with
a stable user/developer-base.
- dev@poi.apache.org:
- 240 subscribers (down -3 in the last 3 months):
- 863 emails sent to list (898 in previous quarter)
- general@poi.apache.org:
- 131 subscribers (up 0 in the last 3 months):
- 6 emails sent to list (2 in previous quarter)
- user@poi.apache.org:
- 627 subscribers (down -8 in the last 3 months):
- 128 emails sent to list (138 in previous quarter)
## Bugzilla Statistics:
- 62 Bugzilla tickets created in the last 3 months
- 65 Bugzilla tickets resolved in the last 3 months
- 495 bugs are open overall
- Having 135 enhancements, thus having 360 actual bugs
- 101 of these are waiting for feedback
- Thus having 259 actual workable bugs
- 6 of the workable bugs have patches available
- Distribution of workable bugs across components: {HSSF=75, XSSF=67, HWPF=38,
SS Common=28, XWPF=16, SXSSF=9, XSLF=8, POI Overall=5, POIFS=4, HPSF=3,
HSLF=2, HPBF=1, HSMF=1, OPC=1, SL Common=1}
-----------------------------------------
Attachment BC: Report from the Apache Qpid Project [Robbie Gemmell]
Apache Qpid is a project focused on creating software based on the
Advanced Message Queuing Protocol (AMQP), currently providing a
protocol engine library, message brokers written in C++ and Java, a
message router, and client libraries for C++, Java / JMS, .Net,
Python, Perl and Ruby.
# Releases:
- Qpid JMS 0.23.0 was released on 15th May 2017.
- Qpid for Java 6.0.7 was released on 1st June 2017.
- Qpid for Java 6.1.3 was released on 1st June 2017.
- Qpid for Java 6.0.8 was released on 29th June 2017.
- Qpid for Java 6.1.4 was released on 29th June 2017.
- Qpid Proton-J 0.20.0 was released on 4th August 2017.
- Qpid JMS 0.24.0 was released on 8th August 2017.
# Community:
- The main user and developer mailing lists continue to be active and JIRAs
are being raised and addressed, in line with prior activity levels.
- Adel Boutros was added as a committer on 8th August 2017.
- There were no new PMC additions in this quarter.
The most recent new PMC member is Ganesh Murthy, added on 30th Jan 2017.
# Development:
- Work on the Dispatch router continues apace to add new functionality,
resolve various defects, and overhaul its IO handling around the work
being done for Proton-C 0.18.0, all building towards Dispatch 1.0.0.
- Work continues towards a 7.0.0 java broker release and a 6.3.0 AMQP 0-x
JMS client release since their migration from Subversion to individual
Git repositories, as well as bug fixes in the existing 6.x lines.
- Proton-C and its language bindings continue to see significant work
implementing improvements around IO level integrations, including porting
the C++ binding to this new model, all working toward a 0.18.0 release in
the weeks ahead. Proton-J just had its 0.20.0 release, incorporating some
changes needed to facilitate some bug fix and feature additions in
dependent client/broker components.
- The AMQP 1.0 JMS client had its 0.23.0 and 0.24.0 releases, incorporating
various bug fixes and improvements since the 0.2X.0 releases added support
for JMS 2.0. Additional fixes and improvements continue, with some work
just done to allow building and testing on JDK9 going forward.
# Issues:
There are no Board-level issues at this time.
-----------------------------------------
Attachment BD: Report from the Apache REEF Project [Byung-Gon Chun]
## Description:
Apache REEF (Retainable Evaluator Execution Framework) is a library for
developing portable applications for cluster resource managers such as
Apache Hadoop YARN or Apache Mesos.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Lots of activities around running REEF .Net on .NET Core/Standard 2.0
- Great progress on running REEF on Spark
- Good progress on exposing advanced resource manager features through REEF
## Health report:
Overall, the community is healthy: the community has been achieving
important milestones and there is a constant flow of bug reports, fixes,
and discussions.
## PMC changes:
- Currently 21 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andrew Chung on Wed Nov 18 2015
## Committer base changes:
- Currently 34 committers.
- No new committers added in the last 3 months
- Last committer addition was Doug Service at Tue Apr 11 2017
## Releases:
- 0.16 was released on Thu Aug 10 2017
## Mailing list activity:
- dev@reef.apache.org:
- 82 subscribers (up 2 in the last 3 months):
- 772 emails sent to list (776 in previous quarter)
- user@reef.apache.org:
- 14 subscribers (up 2 in the last 3 months):
- 2 emails sent to list (2 in previous quarter)
## JIRA activity:
- 65 JIRA tickets created in the last 3 months
- 45 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BE: Report from the Apache River Project [Patricia Shanahan]
## Description:
- Apache River software provides a standards-compliant JINI service.
## Issues:
The River PMC seeks advice and guidance from the board on the following issue:
River has had difficulty transitioning from a solid platform inherited from
Jini into a more modular and active development. Parallel development has
occurred outside the project in JGDMS, while trying to find a resolution.
At this point, there is an opportunity to bring in that code from parallel
development and, hopefully, move forward with a modular build architecture
that supports broader participation and better velocity.
1. JGDMS is a fork of River on github.
2. JGDMS has security features, improved IPv6 support and a Maven
modular build.
3. There are a couple of developers actively working on JGDMS, one is
also an active River PMC member, the second has participated for a
long time in River, but isn't a PMC Member or committer at this
time, and recently received enough votes to be invited to the PMC.
4. It was a goal of JGDMS to influence River's roadmap and donate the
work to River.
5. No code from JGDMS is included in River at this time.
6. The JGDMS fork has features that are aligned with River's roadmap.
## Activity:
- We are in the process of voting on a possible PMC member
- The main activity has been discussion of the JGDMS issue.
- We currently have a River 3.0.1 release candidate under review.
## Health report:
- It is difficult to make progress without resolving the JGDMS import issue.
- The PMC chair intends to resign effective the September board meeting. This
is a routine change - I have been chair for over 3 years, and strongly believe
the role should circulate among the PMC members. There is a volunteer for
successor.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Bryan Thompson on Sun Aug 30 2015
## Committer base changes:
- Currently 15 committers.
- No new committers added in the last 3 months
- Last committer addition was Bharath Kumar at Mon Mar 13 2017
## Releases:
- Last release was River-3.0.0 on Wed Oct 05 2016
-----------------------------------------
Attachment BF: Report from the Apache Roller Project [Dave Johnson]
## Description:
Apache Roller is a full-featured, Java-based blog server that works
well on Tomcat and MySQL, and is known to run on other Java servers
and relational databases. The ASF blog site at blogs.apache.org runs on
Roller 5.1.2 Tomcat and MySQL.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- The core Roller community is small and with low activity levels.
- There is ongoing work to create a modernized UI using Bootstrap with Struts.
- A new Roller 5.2.0 release is being prepared to fix I18N and other issues on blogs.apache.org
## Health report:
- Community is made-up of part-time volunteers with very limited time to devote to Roller.
## PMC changes:
- Currently 5 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Kohei Nozaki on Sun Dec 06 2015
## Committer base changes:
- Currently 9 committers.
- No new committers added in the last 3 months
- Last committer addition was Kohei Nozaki at Mon Mar 09 2015
## Releases:
- Last release was 5.1.2 on Tue Mar 24 2015
## Mailing list activity:
Subscriber counts could be taken to mean there is still some interest in
Apache Roller. The low email counts reflec the low level of development
and user-support activity.
- dev@roller.apache.org:
- 158 subscribers (up 1 in the last 3 months):
- 4 emails sent to list (4 in previous quarter)
- user@roller.apache.org:
- 281 subscribers (down -3 in the last 3 months):
- 1 emails sent to list (6 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BG: Report from the Apache Santuario Project [Colm O hEigeartaigh]
## Description:
- Library implementing XML Digital Signature Specification & XML Encryption
Specification
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- It was a quiet quarter for the project with no new releases. A couple of
user bugs were reported and fixed. More work was done to get the Java
library working with Java 9. A discussion was initiated on the mailing
list to release a new major release (2.1.0) supporting Java 9 - work on
getting this release out will start shortly.
Over the next quarter it is planned to release V1.8 of the C++ library to
add OpenSSL 1.1 support.
## Health report:
- Apache Santuario is a mature and stable project that has reached a point
where not too many fixes are required, as it is a set of implementations
of some specifications that are quite old now. It is actively managed by
the PMC. Right now there are no obvious potential new committers for the
project.
## PMC changes:
- Currently 6 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Marc Giger on Wed Apr 03 2013
## Committer base changes:
- Currently 16 committers.
- No new changes to the committer base since last report.
- Last committer addition was Marc Giger in July 2012
## Releases:
- Last release was Apache Santuario XML Security for Java 2.0.8 on Mon Dec
05 2016
## JIRA activity:
- 3 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BH: Report from the Apache Serf Project [Bert Huijben]
-----------------------------------------
Attachment BI: Report from the Apache SIS Project [Martin Desruisseaux]
## Description:
Apache Spatial Information System (SIS) is a Java library for developing
geospatial applications. SIS enables better representation of spatial
objects for searching, archiving, or other relevant spatial needs. The
base of the SIS library is modelled according international standards
published jointly by the Open Geospatial Consortium (OGC) and the
International Organization for Standardization (ISO).
## Issues:
There are no issues requiring board attention at this time.
## Activity:
A 20 minutes talk about geospatial international standards and their
implementation in Apache SIS was done in the Free and Open Source
Software for Geospatial (FOSS4G) European conference in Paris, July 19th
[1]. About 20~30 attendees were in the room. A similar conference will
be done in the international FOSS4G conference in Boston, August 14-19 [2].
The two Google Summer of Code (GSoC) projects are progressing. Branches
have been prepared for integration, but the codes themselves have not
been merged yet. Those merges may require a significant amount of work
because of code review needed. We will try to use the last students days
for refactoring their code in order to ease merge.
One contributor signed ICLA and donated an upgrade of XML metadata
format to latest revisions of ISO standards. This contributor does not
wish to have commit right for now. We will merge his work (currently on
a GitHub clone) as soon as time allow. A related but smaller work was
done on JIRA [3] and is also pending time for integration in Apache SIS.
In this case too, the contributor did not wished commit right.
Apache SIS 0.8 release is blocked by GeoAPI 3.0.1 release by the Open
Geospatial Consortium (OGC). We are working with OGC for helping them to
make this release. We hope to have it by the end of August.
## Health report:
The project is reported mostly okay according the Apache Committee
Report Helper, but got no new PMC in two years. However activity on the
developers mailing list has increased significantly, from 46 emails in
previous cycle to 147 emails in this cycle. This activity is due not
only to Google Summer of Code, but also to discussions and contributions
from peoples of other horizons.
## PMC changes:
* Currently 19 PMC members.
* No new PMC members added in the last 3 months.
* Last PMC addition was Marc Le Bihan on Wed Dec 10 2014.
## Committer base changes:
* Currently 21 committers.
* No new committers added in the last 3 months.
* Last committer addition was Johann Sorel at Thu Mar 31 2016.
We do not have new committer candidate yet. We do not know what will be
the GSoC students intend after their project, and the other contributors
declined (for now) the proposal.
## Releases:
Last release was 0.7 on May 27 2016. The 0.8 release will start as soon
as GeoAPI 3.0.1 release is available (hopefully this month).
## Mailing list activity:
* dev@sis.apache.org:
o 65 subscribers (up 2 in the last 3 months):
o 147 emails sent to list (46 in previous quarter)
## JIRA activity:
* 7 JIRA tickets created in the last 3 months.
* 1 JIRA tickets closed/resolved in the last 3 months.
[1] https://europe.foss4g.org/2017/assets/pdf/FOSS4G-Europe-2017-Program.pdf
[2] http://2017.foss4g.org/accepted-presentations/
[3] https://issues.apache.org/jira/browse/SIS-171
-----------------------------------------
Attachment BJ: Report from the Apache Spark Project [Matei Zaharia]
Apache Spark is a fast and general engine for large-scale data processing. It
offers high-level APIs in Java, Scala, Python and R as well as a rich set of
libraries including stream processing, machine learning, and graph analytics.
Project status:
- We released Spark 2.2.0 on July 11th, with 1100 patches since the last
version. Some of the major features released included a cost-based
optimizer for Spark SQL / DataFrames, PyPI publishing, and the first
production version of the new high-level Structured Streaming API (losing
the experimental tag because the API has been stabilized). More details
are available at spark.apache.org/releases/spark-release-2-2-0.html.
- The Spark Summit conference ran in June with around 3000 attendees.
- Work is under way for Spark 2.3.0, with the current target to close the
new feature window and cut a release branch in November 2017.
Trademarks:
- We are continuing engagement with various organizations.
Latest releases:
- July 11, 2017: Spark 2.2.0
- May 02, 2017: Spark 2.1.1
- Dec 28, 2016: Spark 2.1.0
- Nov 14, 2016: Spark 2.0.2
- Nov 07, 2016: Spark 1.6.3
Committers and PMC:
- The last committers were added on July 27th, 2017
(Hyukjin Kwon and Sameer Agarwal).
- The last PMC members were added on June 16th, 2017
(six new PMC members from the existing committers).
-----------------------------------------
Attachment BK: Report from the Apache Streams Project [Stephen D Blackmon]
## Description:
- Apache Streams unifies a diverse world of digital profiles and online
activities into common formats and vocabularies, and makes these datasets
accessible across a variety of databases, devices, and platforms for
streaming, browsing, search, sharing, and analytics use-cases.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Most recent activity has been focused on graduation and TLP
post-graduation tasks.
- We have completed most PMC setup and infra tasks; some code and website
refactoring work remains.
## Health report:
Streams graduated to TLP on July 19 2017. Eight PPMC members have joined
the new PMC. Enthusiasm is strong and there is a lot of important work
ahead.
## PMC changes:
- PMC has been just formalized as part of the graduation resolution.
- Currently 8 PMC members.
## Committer base changes:
- PMC has been just formalized as part of the graduation resolution.
- Currently 8 committers.
## Releases:
- Prior release was 0.5-incubating on March 20, 2017
- Next release will be 0.6.0 - discussion on list has started.
## Mailing list activity: (3 month)
81 Emails sent during these 92 days, up 32 (65%) compared to previous 92
days.
25 topics started during these 92 days, up 10 (66%) compared to previous 92
days.
17 Participants during these 92 days, up 6 (54%) compared to previous 92
days.
https://s.apache.org/yYqm
## JIRA Statistics: (3 month)
13 new, 7 resolved
https://s.apache.org/72GL
## Upcoming Project Initiatives:
- Work to reduce disparities between normalized activities and objects of
like type collected from various data sources.
- Work to reduce disparities between the configuration objects that
initialize similar providers from various data sources.
- Drop remaining maven dependencies on java SDKs for accessing third-party
HTTP APIs in favor of interfaces powered by Apache Juneau (incubating)
Remoteable Annotations.
- Add official support for Schema.org <http://schema.org/> and Activity
Streams 2.0 data types.
- More tweets and blog posts of zeppelin notebooks demonstrating data
pipelines and analyses based on Apache Streams.
- More official examples in source tree demonstrating integration of Apache
Streams with complementary technologies.
-----------------------------------------
Attachment BL: Report from the Apache Subversion Project [Evgeny Kotkov]
Apache Subversion exists to be universally recognized and adopted as
an open-source, centralized version control system characterized by
its reliability as a safe haven for valuable data; the simplicity of
its model and usage; and its ability to support the needs of a wide
variety of users and projects, from individuals to large-scale
enterprise operations.
* Board Issues
There are no Board-level issues of concern.
* Community
The community has finished the work on resolving the prior-reported
SHA1 hash collision issues. This resulted in preparing two new patch
releases, Subversion 1.8.18 and 1.9.6, with the corresponding fixes.
These releases were simultaneously made available to our users on July 6th.
Apart from this, we also finished the work on the first alpha release of
the upcoming Subversion 1.10 series, 1.10-alpha3 ("alpha1" and "alpha2"
were not released for various technical reasons). While we continue
moving towards the first GA release of Subversion 1.10, such pre-
releases should allow for more widespread testing by the community.
There hasn't been any visible benefits from the previously reported
experimental integration with the Transifex (https://www.transifex.com)
translation platform at this time. We will, however, continue to monitor
how this experiment works out.
During this quarter, there is a major increase in commit activity and
in both dev@ and users@ mailing lists traffic. For instance, our dev@
mailing list has received around 547 messages, opposed to 318 in the
previous quarter. We have seen new people actively participating in
the discussions of some of the upcoming and developed features in
Subversion 1.10, and this may partly explain the increased amount
of traffic.
Last PMC addition was in February 2017 (Stefan Hett).
Last committer addition happened in November 2015 (James McCoy).
* Releases
Subversion 1.8.18 and 1.9.6 were released on July 6th, 2017.
Subversion 1.10-alpha3 was released on July 26th, 2017.
-----------------------------------------
Attachment BM: Report from the Apache Syncope Project [Francesco Chicchiriccò]
## Description:
Apache Syncope is an Open Source system for managing digital identities in
enterprise environments.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
The last months were again busy with fixes, new features and enhancements for
the stable branch, which led to the release of 2.0.4. Such activity keeps
steady and will likely bring 2.0.5 soon.
## Health report:
Discussions about new features and improvements keep appearing and being
followed up in dev@.
Newcomers approach user@ and are getting supported by various members of the
community.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition: Thu Oct 13 2016 (Andrea Patricelli)
## Committer base changes:
- Currently 21 committers.
- Matteo Alessandroni was added as a committer on Fri Jul 28 2017
- Last committer addition: Fri Jul 28 2017 (Matteo Alessandroni)
## Releases:
- 2.0.4 was released on Mon Jul 03 2017
-----------------------------------------
Attachment BN: Report from the Apache SystemML Project [Deron Eriksson]
## Description:
SystemML provides declarative large-scale machine learning (ML) that aims at
flexible specification of ML algorithms and automatic generation of hybrid
runtime plans ranging from single node, in-memory computations, to distributed
computations such as Apache Hadoop MapReduce and Apache Spark.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- We graduated as an Apache top-level project on May 18, 2017.
- We are working towards our first top-level project release.
- Second phase of GSoC project completed to automate performance testing.
## Health report:
- Code activity is healthy with 299 commits in the last 3 months.
- Community growth is healthy with 4 new contributors in the last 2 months.
- Communication at a healthy level on mailing list, JIRAs, and pull requests.
## PMC changes:
- Currently 23 PMC members.
- Felix Schüler was elected as PMC member on April 19, 2017.
## Committer base changes:
- Currently 23 committers.
- Felix Schüler was elected as committer on April 19, 2017.
## Releases:
- Version 0.14.0-incubating was released on May 8, 2017.
-----------------------------------------
Attachment BO: Report from the Apache Thrift Project [Jake Farrell]
Apache Thrift is a framework for providing cross-platform RPC and serialization.
Project Status
---------
The Apache Thrift community is currently working on our 0.11.0 release
candidate which will include a number of stability and performance
enhancements to our Go, Node and Python client libraries [1]. We
have also started auditing our codebase to ensure that recent
category-x licensing changes [2] that occurred due to the Facebook
BSD+patents license changes do not impact Apache Thrift.
Community
---
Latest Additions:
* PMC addition: Nobuaki Sukegawa, 1.25.2016
* Committer addition: James King, 10.18.2016
Issue backlog status since last report:
* Created: 87
* Resolved: 57
Mailing list activity since last report:
* @dev 1145 messages
* @user 36 messages
Releases
---
Last release: 0.10.0, Release Date: 1.3.2017
Cut 0.11.0 branch, release candidate creation and testing in progress
[1]: https://git-wip-us.apache.org/repos/asf?p=thrift.git;a=tree;h=refs/heads/0.11.0;hb=refs/heads/0.11.0
[2]: https://www.apache.org/legal/resolved.html#category-x
-----------------------------------------
Attachment BP: Report from the Apache Turbine Project [Georg Kallidis]
## Description:
Apache Turbine is a servlet based framework that allows experienced Java
developers to quickly build web applications. Turbine allows you to
personalize the web sites and to use user logins to restrict access to
parts of your application.
Turbine is a matured and well established framework that is used as the
base of many other projects.
## PMC changes:
- Currently 8 PMC members.
- No new PMC members added in the last 3 months
- Georg Kallidis has been elected as the new PMC chair.
## Committer base changes:
- Currently 11 committers.
- No new changes to the committer base since last report.
- The last change to the committer base was the addition of Georg Kallidis
(2012/09/19).
## Releases:
Fulcrum component project:
- The latest released component was Fulcrum Security 1.1.1
(May 23 2017)
- A new version of the Fulcrum JSON component 1.1.1 is being prepared.
Turbine core project:
- No releases have been done this quarter.
- The latest released component was the Turbine4 Webapp Archetype
1.0.1 (January 25 2017)
## Issues:
- No issues requiring board attention are known at this time.
## Health report:
- The Turbine project has had low levels of activity this quarter.
- Code activity was mainly in Turbine4 Webapp Archetype and Fulcrum JSON/Security.
- Release of final Turbine4 + site update is targeted next along with
release of Webapp Archetype.
-----------------------------------------
Attachment BQ: Report from the Apache Usergrid Project [Todd Nine]
-----------------------------------------
Attachment BR: Report from the Apache Velocity Project [Nathan Bubna]
## Description:
- Java-based template engine
## Issues:
- No issues requiring board attention at this time.
## Activity:
- Light activity, mostly centered around new PMC member, new Engine 2.0
release, and a few minor bugs.
## Health report:
- Project is healthy. New major version of core product, latest committer has
moved up to PMC.
## PMC changes:
- Currently 9 PMC members.
- Michael Osipov was added to the PMC on Thu Jul 27 2017
## Committer base changes:
- Currently 14 committers.
- No new committers added in the last 3 months
- Last committer addition was Michael Osipov at Mon Jan 30 2017
## Releases:
- Engine 2.0 was released as GA on Aug 6 2017
## Mailing list activity:
- Light traffic regarding PMC membership, Engine 2.0 release, and minor bugs.
- dev@velocity.apache.org:
- 125 subscribers (up 0 in the last 3 months):
- 67 emails sent to list (47 in previous quarter)
- general@velocity.apache.org:
- 85 subscribers (up 1 in the last 3 months):
- 0 emails sent to list (1 in previous quarter)
- user@velocity.apache.org:
- 306 subscribers (up 4 in the last 3 months):
- 0 emails sent to list (9 in previous quarter)
## JIRA activity:
- 3 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BS: Report from the Apache Whimsy Project [Sam Ruby]
## Description:
Tools that help automate various administrative tasks or information lookup
activities
## Issues:
Four tools (board/agenda, secretary/workbench, roster, and test/icla) make
use of React.js, which has recently been reclassified as Category X by
Legal Affairs. It would be helpful if VP Legal Affairs and/or the ASF Board
reach out to Facebook to help convince them to relicense React.JS, just like
they did with RocksDB.
## Health report:
- John D Ament was added as a committer this month.
The current status is that we continue to have more than adequate oversight,
we now have two to three active committers, and two to four occasional
committers.
## Development:
- Worked closely with the infrastructure team to update and modernize a
a number of tools including: new account requests, roster, and mailing list
requests. These tools are now all hosted on whimsy's VM.
- Progress continues towards enabling all PMC members (as well as all
ASF members) to maintain PMC rosters (something that already is supported
for PPMC rosters).
- Significant improvement was made to the podling roster pages.
- Stylistic improvments continue.
- Deployment is now triggered by gitpubsub; speeding development.
- The final three applications were migrated to the new machine, and the
process of decomissioning whimsy-vm3 has begun.
## PMC and committer base:
- Currently 10 committers, all on the PMC.
- Last addition: Thu Jun 2017 (John D. Ament)
-----------------------------------------
Attachment BT: Report from the Apache Xalan Project [Steven J. Hathaway]
-----------------------------------------
Attachment BU: Report from the Apache Xerces Project [Michael Glavassevich]
-----------------------------------------
Attachment BV: Report from the Apache XML Graphics Project [Glenn Adams]
## Description:
- The Apache XML Graphics Project is responsible for software
intended for the creation & maintenance of the conversion of XML
formats to graphical output & related software components.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- During this reporting period, activity on the three sub-projects
has remained low, with 38 issues resolved or closed during this
reporting period.
## Health:
- The level of community and developer activity remains at a
low level for a relatively mature product, albeit one
with a fair number of outstanding unresolved issues.
## PMC:
- No new PMC members added in the last 3 months
- Last PMC addition was Simon Steiner on Tue Jan 19 2016
- Currently 11 PMC members.
## Committers:
- No new committers added in the last 3 months
- Last committer added was Matthias Reischenbacher at Wed May 13 2015
- Currently 21 committers.
## Releases:
- XMLGraphics Batik 1.9.1 was released on Tue Aug 01 2017
## Mailing Lists:
- Slight decrease in subscribers of 1%, down from 1095 to 1083.
- Mail lists show a decrease in traffic of 38%, down from 589 to 367,
reflecting a post-major release drop in activity.
------------------------------------------------------
End of minutes for the August 16, 2017 board meeting.
Index