Index
Links: 2018 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
November 21, 2018
1. Call to order
The meeting was scheduled for 10:30am Pacific and began at 10:33
when a sufficient attendance to constitute a quorum was
recognized by the chairman.
Other Time Zones: https://timeanddate.com/s/3pdg
The meeting was held via teleconference, hosted by Doug Cutting
and Cloudera.
IRC #asfboard on irc.freenode.net was used for backup purposes.
2. Roll Call
Directors Present:
Rich Bowen
Shane Curcuru
Bertrand Delacretaz
Isabel Drost-Fromm
Brett Porter
Roman Shaposhnik
Phil Steitz
Mark Thomas
Directors Absent:
Ted Dunning
Executive Officers Present:
Ross Gardler
Tom Pappas - joined at 11:00
Sam Ruby
Craig L Russell
Matt Sicker
Executive Officers Absent:
Daniel Ruggeri
Ulrich Stärk
Guests:
Daniel Gruno
Geoff Macartney
Greg Stein - joined at 10:59
Jim Jagielski
Kevin A. McGrail
Sally Khudairi
3. Minutes from previous meetings
Published minutes can be found at:
http://www.apache.org/foundation/board/calendar.html
A. The meeting of October 17, 2018
See: board_minutes_2018_10_17.txt
Approved by General Consent.
B. The meeting of September 19, 2018
See: board_minutes_2018_09_19.txt
Approved by General Consent.
4. Executive Officer Reports
A. Chairman [Phil]
We continued to make slow but steady progress last month on strategic
topics. Research into endowment options is nearing completion with an
initial recommendation to be posted for discussion on the finance
list. I incorporated feedback from the kickoff meeting on the 5-year
plan into a revised set of objectives and set up the wiki site [1].
Some good discussions around ASF vision, assuring that contributors
understand their obligations under the ICLA and the status of binary
releases began this month. I am happy to report that the tone of
these discussions has been positive. Thanks in advance to all who
participate to keep it that way as we work through these and other
important issues in the coming months.
Three reports were complemented for their thoughtfulness and / or
comprehension this month: Flume, Ant and Incubator. In a few cases,
issues like those handled thoughtfully in those reports were observed
by Directors reviewing list activity in other projects and they were
encouraged to cover them in their reports. Constructive feedback
related to ensuring oversight, moving toward release and keeping
discussion public whenever possible.
[1] https://cwiki.apache.org/confluence/display/ASFP/5-Year+Strategic+Plan+for+the+Apache+Software+Foundation
B. President [Sam]
Financially, we continue to significantly exceed income (by more
than we did last year), and significantly under-run expense (by less
than we did last year). I neglected to kick off a bottoms up effort
to collect input for a five year plan, which I will do by the end
of the week.
Other areas:
Brand Management has a private matter seeking feedback from the board.
Fundraising is operating smoothly and is exceeding targets.
Low to average month in terms of activity for Marketing and Publicity,
which generally is a good thing :-).
Infrastructure is operating as expected, one notable item: the team
will be moving from HipChat to Slack.
Conferences has chosen a date for ApacheCon NA in Las Vegas, September
9th through 12th, 2019. DC road show has been postponed. Other
events are still in the planning stages.
No Travel Assistance activity this month as we are between conferences.
Finance continues to work on an Endowment proposal.
Additionally, please see Attachments 1 through 7.
C. Treasurer [Ulrich]
Operating Cash on Oct 31st, 2018 was $2,169.5K, which is up $73.2K
from last month's ending balance (Sep 18) of $2,096.3K. Total Cash as
of Oct 31st, 2018 is $3,563.4K (includes the Pineapple and restricted
Donation) as compared to $1,690.5K on Oct 31st 2017. The Oct 2018
ending Operating cash balance of $2,169.5K represents an Operating
cash reserve of 13.8 months based on the FY19 conservative Cash
forecast average monthly spending of $157.1K/month. The ASF actual
Operating reserve of 13.8 months at the end of Oct 2018 is ahead of
the budgeted 11.1 month reserve for YTD through Oct 2018. The ASF
Operating reserve continues to be very healthy for an organization of
the ASF's size and Operating activity.
Reviewing the YTD Cash P&L, total Income was ahead of FY 18 at this
point in the Fiscal year by $151.9K. As compared to the FY 19
Budgeted Income, YTD we are ahead by $241.4K as compared to being
ahead of budget at the end of Sept 2018 by $34.3K, a significant
increase.
YTD expenses through Oct 31st, 2018 are under budget by $228.7K, as
compared to being under budget in expense by $329.1K at the end of Sep
2018. All depts. are under budget at the end of Oct 2018. The timing
variance has narrowed a bit as can be seen by the reduction in
the amount under budget from Sept 2018 to Oct 2018. There are
still a couple worth mentioning, one being Infra, as noted in
the Board summary is $112.1K under budget due to Timing of
hiring of staff and timing of Lease web invoices. The other
being TAC at $45K under budget YTD for FY19. We have moved
most of the dept underspending forward in the Cash forecast and
will be reviewing the underspending with the departments as we
move forward in FY19 Q3.
Regarding Net Income (NI), YTD FY 19 the ASF finished with a positive
$99.5K NI vs a budgeted negative <$370.6K> NI or $470.1K ahead of
Budget, NI, for FY19 at this point in the Fiscal year. This was
attributable to timing of some Sponsor payments offset by more
Donations than were budgeted as well as underspending in all depts
YTD, vs the FY19 Budget. At this point in the FY we are doing very
well, ahead in Revenue and well under budget in Expenses, even taking
timing variances into account. We will continue to monitor this as
we move further into FY19. With regard to FY18, we are outpacing
revenue but are also out pacing expenses, and therefore training in
NI year over year, but again significantly ahead of FY19 budget in
all categories.
Current Balances:
Boston Private CDARS Account 2,250,000.00
Citizens Money Aprket 1,066,312.47
Citizens Checking 246,891.28
Paypal - ASF 184.27
Total Checking/Savings 3,563,388.02
Oct-18 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 2,276.96 7,033.96 -4,757.00
Sponsorship Program 170,000.00 70,000.00 100,000.00
Programs Income 0.00 0.00 0.00
Conference/Event Income 112,427.95 0.00 112,427.95
Other Income 0.00 1.00 -1.00
Interest Income 609.19 1,172.93 -563.74
Total Income 285,314.10 78,207.89 207,106.21
Expense Summary:
In Kind Expense 0.00 0.00 0.00
Infrastructure 60,186.32 81,128.32 -20,942.00
Programs Expense 0.00 0.00 0.00
Publicity 14,760.97 13,312.88 1,448.09
Brand Management 15,117.30 8,166.67 6,950.63
Conferences 103,313.09 0.00 103,313.09
Travel Assistance Committee 0.00 0.00 0.00
Fundraising 12,082.60 17,333.34 -5,250.74
Treasury Services 3,350.00 3,475.00 -125.00
General & Administrative 2,293.27 2,366.94 -73.67
Total Expense 211,103.55 125,783.15 85,320.40
Net Income 74,210.55 -47,575.26 121,785.81
YTD FY19 Budget Variance
Income Summary:
Inkind Revenue 0.00 0.00 0.00
Public Donations 134,528.05 31,630.37 102,897.68
Sponsorship Program 575,371.47 480,000.00 95,371.47
Programs Income 17,200.00 14,400.00 2,800.00
Conference/Event Income 228,227.95 184,000.00 44,227.95
Other Income 0.00 0.00 0.00
Interest Income 3,002.62 6,942.77 -3,940.15
Total Income 958,330.09 716,973.14 241,356.95
Expense SumApry:
In Kind Expense 0.00 0.00 0.00
Infrastructure 384,662.50 496,769.92 -112,107.42
Programs Expense 0.00 4,400.00 -4,400.00
Publicity 135,762.33 151,422.77 -15,660.44
Brand Management 31,875.50 49,000.02 -17,124.52
Conferences 194,805.48 200,000.00 -5,194.52
Travel Assistance Committee 0.00 45,000.00 -45,000.00
Fundraising 81,820.56 104,000.04 -22,179.48
Treasury Services 22,735.00 23,000.00 -265.00
General & Administrative 7,206.21 14,005.93 -6,799.72
Total Expense 858,867.58 1,087,598.68 -228,731.10
Net Income 99,462.51 -370,625.54 470,088.05
D. Secretary [Craig]
The office of Secretary is operating well with plenty of support from
whimsy and the Assistant Secretary.
In October, 62 ICLAs, two CCLAs, and four grants were received and
filed.
E. Executive Vice President [Ross]
Infrastructure
=============
Infrastructure is operating as expected, and has no current issues to
bring to the attention of the President or the Board.
Possible financial impact from level of Slack usage. Team are
monitoring.
Reviewing resumes to fill two open headcount.
Cloud credits from one provide have been renewed, with a commitment to
three years. This allows for an expansion of GitBox. It's good to see
cloud providers willing to provide stability to the foundation through
three year commitments.
There was a security issue with our Sonarcube analysis server, this
has been resolved without any known impact.
Marketing and Publicity
=======================
Marketing and Publicity is operating as expected, and has no current
issues to bring to the attention of the President or the Board.
Some Q1 FY2019 reports are now overdue, please submit at your earliest
convenience.
Conferences
===========
Signed contracts for Virtual to produce ApacheCon North America 2019
at the Flamingo hotel in Las Vegas, September 9th through 12th, 2019.
DC road show has been postponed, due to difficulties with sponsors,
and \the venue.
Chicago Road Show, 2019 proposal submitted by, and championed by,
Trevor Grant.
Discussion around ApacheCon EU 2019 has stalled. Assistance is both
forthcoming and requested (more needed).
Travel Assistance Committee
===========================
No report submitted. I'm unaware of any issues requiring attention and
no event requires attention at present.
F. Vice Chairman [Shane]
Nothing to report this month, unfortunately!
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Roman]
See Attachment 8
B. Apache Legal Affairs Committee [Roman Shaposhnik]
See Attachment 9
@Board review CCLA discussion on legal-internal and provide
input as appropriate
C. Apache Security Team Project [Mark J. Cox / Isabel]
See Attachment 10
@Phil: draft strongly worded message on board list to PMCs
that have outstanding security issues
D. VP of Data Privacy [Chris Mattmann / Shane]
See Attachment 11
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Brand Management [rs]
# Cocoon [ps]
# Community Development [rs]
# Hama [mt]
# Juneau [mt]
# Legal Affairs [rs]
# Polygene [bd]
# Security Team [rs, rb]
# Stanbol [rs]
# Xalan [rs]
A. Apache Ambari Project [Jayush Luniya / Phil]
See Attachment A
B. Apache Ant Project [Jan Materne / Rich]
See Attachment B
C. Apache Bloodhound Project [Gary Martin / Ted]
See Attachment C
D. Apache BookKeeper Project [Sijie Guo / Mark]
See Attachment D
E. Apache Brooklyn Project [Geoff Macartney / Brett]
See Attachment E
F. Apache Buildr Project [Antoine Toulme / Bertrand]
See Attachment F
G. Apache Cassandra Project [Nate McCall / Rich]
See Attachment G
H. Apache Clerezza Project [Hasan Hasan / Roman]
See Attachment H
I. Apache Cocoon Project [Cédric Damioli / Brett]
See Attachment I
@Brett: follow up with Cocoon to encourage a release
J. Apache Community Development Project [Sharan Foga / Shane]
See Attachment J
@Sally: work with Sam and Tom to request more budget for
stickers for events
K. Apache CouchDB Project [Jan Lehnardt / Isabel]
See Attachment K
L. Apache Creadur Project [Brian E Fox / Ted]
See Attachment L
M. Apache DeltaSpike Project [Mark Struberg / Phil]
See Attachment M
N. Apache DRAT Project [Chris Mattmann / Mark]
See Attachment N
O. Apache Drill Project [Arina Ielchiieva / Bertrand]
See Attachment O
P. Apache Empire-db Project [Rainer Döbele / Ted]
See Attachment P
Q. Apache Flume Project [Mike Percy / Shane]
See Attachment Q
R. Apache Forrest Project [David Crossley / Bertrand]
See Attachment R
S. Apache FreeMarker Project [Dániel Dékány / Phil]
See Attachment S
T. Apache Geode Project [Mark Bretl / Brett]
See Attachment T
U. Apache Giraph Project [Dionysios Logothetis / Isabel]
See Attachment U
V. Apache Gora Project [Lewis John McGibbney / Mark]
See Attachment V
W. Apache Groovy Project [Guillaume Laforge / Roman]
See Attachment W
X. Apache Hama Project [Chia-Hung Lin / Rich]
See Attachment X
@Rich: follow up with the PMC and get a report next month
Y. Apache HAWQ Project [Lei Chang / Shane]
No report was submitted.
@Shane: pursue a report for HAWQ
Z. Apache Helix Project [Kishore G / Bertrand]
See Attachment Z
AA. Apache HTTP Server Project [Daniel Gruno / Mark]
See Attachment AA
AB. Apache HttpComponents Project [Asankha Chamath Perera / Isabel]
See Attachment AB
AC. Apache Ignite Project [Denis A. Magda / Roman]
See Attachment AC
AD. Apache Impala Project [Jim Apple / Ted]
See Attachment AD
AE. Apache Incubator Project [Justin Mclean / Phil]
See Attachment AE
AF. Apache jUDDI Project [Alex O'Ree / Rich]
See Attachment AF
AG. Apache Juneau Project [James Bognar / Brett]
See Attachment AG
@Mark: work to verify adequate oversight by PMC
AH. Apache Kafka Project [Jun Rao / Roman]
See Attachment AH
AI. Apache Kibble Project [Rich Bowen]
See Attachment AI
AJ. Apache Knox Project [Larry McCay / Shane]
See Attachment AJ
AK. Apache Kylin Project [Luke Han / Ted]
See Attachment AK
AL. Apache Lens Project [Amareshwari Sriramadasu / Bertrand]
See Attachment AL
AM. Apache Libcloud Project [Tomaž Muraus / Rich]
See Attachment AM
AN. Apache Logging Services Project [Matt Sicker / Phil]
See Attachment AN
AO. Apache Lucene.Net Project [Shad Storhaug / Mark]
No report was submitted.
AP. Apache ManifoldCF Project [Karl Wright / Brett]
See Attachment AP
AQ. Apache Marmotta Project [Jakob Frank / Isabel]
See Attachment AQ
AR. Apache MetaModel Project [Kasper Sørensen / Shane]
See Attachment AR
AS. Apache Olingo Project [Christian Amend / Isabel]
See Attachment AS
AT. Apache Oozie Project [Gézapeti / Ted]
See Attachment AT
AU. Apache Open Climate Workbench Project [Michael James Joyce / Rich]
No report was submitted.
@Rich: pursue a report for Open Climate Workbench
AV. Apache Perl Project [Philippe Chiasson / Mark]
No report was submitted.
AW. Apache Phoenix Project [Josh Elser / Brett]
See Attachment AW
AX. Apache POI Project [Dominik Stadler / Phil]
See Attachment AX
AY. Apache Polygene Project [Jiri Jetmar / Bertrand]
No report was submitted.
@Bertrand: pursue a report for Polygene
AZ. Apache Pulsar Project [Matteo Merli / Roman]
See Attachment AZ
BA. Apache Qpid Project [Robert Gemmell / Brett]
See Attachment BA
BB. Apache REEF Project [Byung-Gon Chun / Mark]
See Attachment BB
BC. Apache River Project [Peter Firmstone / Roman]
See Attachment BC
BD. Apache RocketMQ Project [Xiaorui Wang / Rich]
See Attachment BD
BE. Apache Roller Project [David M. Johnson / Isabel]
See Attachment BE
BF. Apache Santuario Project [Colm O hEigeartaigh / Bertrand]
See Attachment BF
BG. Apache Serf Project [Branko Čibej / Shane]
See Attachment BG
BH. Apache SIS Project [Martin Desruisseaux / Phil]
See Attachment BH
BI. Apache Spark Project [Matei Alexandru Zaharia / Ted]
See Attachment BI
BJ. Apache Stanbol Project [Fabian Christ / Ted]
No report was submitted.
BK. Apache Subversion Project [Stefan Sperling / Phil]
See Attachment BK
BL. Apache Synapse Project [Isuru Udana / Shane]
See Attachment BL
BM. Apache Syncope Project [Francesco Chicchiriccò / Brett]
See Attachment BM
BN. Apache SystemML Project [Jon Deron Eriksson / Isabel]
See Attachment BN
BO. Apache TomEE Project [David Blevins / Bertrand]
See Attachment BO
BP. Apache Traffic Control Project [David Neuman / Rich]
See Attachment BP
BQ. Apache Turbine Project [Georg Kallidis / Mark]
See Attachment BQ
BR. Apache Usergrid Project [Michael Russo / Roman]
See Attachment BR
BS. Apache Velocity Project [Nathan Bubna / Phil]
See Attachment BS
BT. Apache Whimsy Project [Sam Ruby / Bertrand]
No report was submitted.
BU. Apache Xalan Project [Steven J. Hathaway / Isabel]
No report was submitted.
@Roman: work with the community on retiring Xalan
BV. Apache Xerces Project [Michael Glavassevich / Rich]
No report was submitted.
@Rich: pursue a report for Xerces
BW. Apache XML Graphics Project [Clay Leeds / Mark]
No report was submitted.
@Mark: pursue a report for XML Graphics
BX. Apache Servicecomb Project [Willem Ning Jiang / Shane]
See Attachment BX
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Change the Apache Olingo Project Chair
WHEREAS, the Board of Directors heretofore appointed Christian Amend
(chrisam) to the office of Vice President, Apache Olingo, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Christian Amend from the office of Vice President, Apache Olingo, and
WHEREAS, the Project Management Committee of the Apache Olingo project
has chosen by vote to recommend Michael Bolz (mibo) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Christian Amend is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Olingo, and
BE IT FURTHER RESOLVED, that Michael Bolz be and hereby is appointed to
the office of Vice President, Apache Olingo, 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 Olingo Project Chair, was
approved by Unanimous Vote of the directors present.
B. Change the Apache Bigtop Project Chair
WHEREAS, the Board of Directors heretofore appointed Peter Linnell
(plinnell) to the office of Vice President, Apache Bigtop, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Peter Linnell from the office of Vice President, Apache Bigtop, and
WHEREAS, the Project Management Committee of the Apache Bigtop project
has chosen by vote to recommend Youngwoo Kim (ywkim) as the successor
to the post;
NOW, THEREFORE, BE IT RESOLVED, that Peter Linnell is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Bigtop, and
BE IT FURTHER RESOLVED, that Youngwoo Kim be and hereby is appointed to
the office of Vice President, Apache Bigtop, to serve in accordance
with and subject to the direction of the Board of Directors and the
Bylaws of the Foundation until death, resignation, retirement, removal
or disqualification, or until a successor is appointed.
Special Order 7B, Change the Apache Bigtop Project Chair, was
approved by Unanimous Vote of the directors present.
C. Change the Apache Groovy Project Chair
WHEREAS, the Board of Directors heretofore appointed Guillaume Laforge
(glaforge) to the office of Vice President, Apache Groovy, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Guillaume Laforge from the office of Vice President, Apache Groovy, and
WHEREAS, the Project Management Committee of the Apache Groovy project
has chosen by vote to recommend Paul King (paulk) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Guillaume Laforge is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Groovy, and
BE IT FURTHER RESOLVED, that Paul King be and hereby is appointed to
the office of Vice President, Apache Groovy, 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 7C, Change the Apache Groovy Project Chair, was
approved by Unanimous Vote of the directors present.
D. Change the Apache Geode Project Chair
WHEREAS, the Board of Directors heretofore appointed Mark Bretl
(mbretl) to the office of Vice President, Apache Geode, and
WHEREAS, the Board of Directors is in receipt of the resignation of Mark Bretl
from the office of Vice President, Apache Geode, and
WHEREAS, the Project Management Committee of the Apache Geode project has
chosen by vote to recommend Karen Miller (kmiller) as the successor to the
post;
NOW, THEREFORE, BE IT RESOLVED, that Mark Bretl is relieved and discharged
from the duties and responsibilities of the office of Vice President, Apache
Geode, and
BE IT FURTHER RESOLVED, that Karen Miller be and hereby is appointed to the
office of Vice President, Apache Geode, 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 7D, Change the Apache Geode Project Chair, was
approved by Unanimous Vote of the directors present.
E. Establish the Apache Griffin Project
WHEREAS, the Board of Directors deems it to be in the best interests
of the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to a data quality solution for big data, including
both streaming and batch mode. It offers an unified process to measure
data quality from different perspectives.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Griffin Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Griffin Project be and hereby is responsible
for the creation and maintenance of software related to a data quality
solution for big data, including both streaming and batch mode. It
offers an unified process to measure data quality from different
perspectives; and be it further
RESOLVED, that the office of "Vice President, Apache Griffin" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache Griffin
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Griffin
Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Griffin
Project:
* Alex Lv <alexlv@apache.org>
* Kevin Yao <dyyao@apache.org>
* Eugene Liu <liujin@apache.org>
* Grant Guo <xuexu@apache.org>
* He Wang <wanghe@apache.org>
* Henry Saputra <hsaputra@apache.org>
* Jason Liao <jasonliao@apache.org>
* John Liu <johnliu@apache.org>
* Juan Li <icesmartjuan@apache.org>
* Liang Shao <liangshao@apache.org>
* Lionel Liu <lionelliu@apache.org>
* Luciano Resende <lresende@apache.org>
* Nick Sokolov <nsokolov@apache.org>
* Shawn Sha <yosha@apache.org>
* Vincent Zhao <wenzhao@apache.org>
* William Guo <guoyp@apache.org>
* Yuqin Xuan <xuanyq@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that William Guo be appointed
to the office of Vice President, Apache Griffin, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed; and be
it further
RESOLVED, that the initial Apache Griffin PMC be and hereby is tasked
with the creation of a set of bylaws intended to encourage open
development and increased participation in the Apache Griffin Project;
and be it further
RESOLVED, that the Apache Griffin Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator Griffin
podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
Griffin podling encumbered upon the Apache Incubator PMC are hereafter
discharged.
Special Order 7E, Establish the Apache Griffin Project, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
A. Appoint Myrle Krantz (myrle) to the position of Assistant Treasurer
Myrle has volunteered to serve as Assistant Treasurer, filling the role
vacated by Phil Steitz.
The board appoints Myrle Krantz to the position of Assistant Treasurer
by general consent.
9. Review Outstanding Action Items
* Phil: work with infrastructure (Greg) on plans for projects with
extraordinary requirements
[ Action Items 2018-05-16 ]
Status:
* Mark: Follow up with project as to current status
[ Creadur 2018-08-15 ]
Status: 2018-11-09 Chased again. 2018-11-20 Resolved. Project
confirmed it was a copy/paste error from previous report.
* Jim: perhaps the httpd project would be willing to adopt mod_perl as a
[ Perl 2018-08-15 ]
Status: As reported last month, the httpd project would be willing to
take over some parts of the project, but not the entire
project. This was relayed to the Perl PMC. No response as of
this date.
* Rich: pursue a report for Lucene.Net
[ Lucene.Net 2018-09-19 ]
Status: Still no report.
* Roman: is this project still viable?
[ Stanbol 2018-09-19 ]
Status:
* Roman: help the project with their request to add new pmc/committers
[ Xalan 2018-09-19 ]
Status:
* Phil: document process of reinstatement of emeritus members
[ Bylaws 4.5: Reinstatement of Membership of Emeritus Members 2018-09-19 ]
Status: Here is what I remember proposing: Emeritus members wishing to
rejoin the ASF should post a message expressing that into to
members@apache.org. Their names will then be added to the next
membership vote. Assuming the vote is successful they will be
reinstated. Do we agree with this? If so, where should it be
posted?
* Roman: Make one last attempt at assessing liability and Attic move
viability,
[ Attic 2018-10-17 ]
Status:
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 12:13 p.m. (Pacific)
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
* ISSUES FOR THE BOARD
* OPERATIONS
Responded to a query on the trademark transfer process for podlings.
Dave Fisher (wave) has been progressing podling name searches with 6 resolved
this month.
Approved two requests to use project logos in books/presentations and one
request to create an Apache users group.
Provided advice to the Spark PMC.
* REGISTRATIONS
CLOUDSTACK is now registered in the UK.
* INFRINGEMENTS
Work continues to address a number of potential infringements.
The Spark PMC resolved an issue with a GitHub project.
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Daniel Ruggeri]
Fundraising continues well with no issues to report. Our monthly committee
meetings continue and our next meeting is on the 28th and guests are welcome.
Financially, we continue to add more sponsors and fundraising goals are being
met or exceeded. The foundation is currently running in the black and
is significantly ahead of budget.
The endowment is now being driven by VP Finance.
A draft prospectus and fundraising input were given for ApacheCon 2019 and a
Roadshow Event in Chicago. The DC Event is postponed and a new date will be
forthcoming.
A new statement of work has been implemented for KAM through the FY.
We have stopped taking car donations.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Sally Khudairi]
I. Budget: we are on budget and on schedule, with no vendor payments outstanding.
II. Cross-committee Liaison: Sally Khudairi continues Sponsor outreach and renewal activities. The latest "Success at Apache" post, "Wearing Small Hats", is live at https://s.apache.org/TGuO . Preparations are underway for the next FY2019 quarterly report.
III. Press Releases: the following formal announcement was issued via the newswire service, ASF Foundation Blog, or announce@apache.org during this timeframe:
- 31 October: The Apache Software Foundation Announces Apache® Subversion® v1.11.0
- 24 October: The Apache Software Foundation Announces Apache® ServiceComb™ as a Top-Level Project
- 23 October: The Apache Software Foundation Announces Apache® HTTP Server v2.4.37
IV. Informal Announcements: 6 items were published on the ASF "Foundation" Blog. 5 Apache News Round-ups were issued, with a total of 226 weekly summaries published to date. We tweeted 13 items, and have 51.6K followers on Twitter. We posted 10 items on LinkedIn, which garnered more than 34K organic impressions.
V. Future Announcements: no 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 4 media queries. The ASF received 1,236 press clips vs. last month's clip count of 1,551. Media coverage of Apache projects yielded 3,024 press hits vs. last month's 4,193. ApacheCon received 5 press hits.
VII. Analyst Relations: we received no analyst queries during this time. Apache was mentioned in 3 reports by Gartner; 3 reports by Forrester; 4 reports by 451 Research; and 2 reports by IDC.
VIII. Graphics: planning for promotional assets for the ASF's 20th Anniversary is underway.
IX. Events liaison: none are planned at this time, however, we are exploring tactics for ApacheCon 2019.
X. Newswire accounts: we have 4 pre-paid press releases remaining in our contract with GlobeNewswire, which will auto-renew through December 2019.
# # #
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [David Nalley]
General
=======
Infrastructure is operating as expected, and has no current issues to
bring to the attention of the President or the Board. This report
covers two months, as we missed our report in October.
The Infrastructure Team has "taken over" management of the-asf.slack.com,
and will be using that for our needs going forward (as Atlassian's
HipChat has been end-of-life'd). As a side-effect, we will officially
support this Slack workspace for existing channels/projects, and for
those who may join going forward. We signed up for Slack's NGO
benefits for the workspace, though it is possible that heavy usage may
move us into a range where we will be billed for some usage. We will
continue to monitor the usage, billing, and determine if any
strategies are needed to keep the Foundation's chat expenditure down.
Finances
========
We are operating within/ahead of budget. We are actively processing
submitted candidate resumes to fill two open headcount, which our
budget will cover once we fill the positions.
Our renewed sponsorship of cloud credits has arrived, with the
requested three year duration and a generous credit. We will be using
these credits to expand our GitBox service to all of our projects.
Short Term Priorities
=====================
- Complete our hiring process.
- Finish deprecation/replacement of the Zmanda backup service with
rsync-based backup. (this will save on licensing costs)
Long Range Priorities
=====================
- Turn off all of our old hardware. Some projects are still on this
hardware, along with some core Infrastructure services. This creates
both stability and security issues for us.
General Activity
================
- ACNA in Montreal was a success for the team. We spent a lot more
time together this year, than our time in Miami (May 2017). We
accomplished a long list of tasks that took advantage of the higher
bandwidth of face-to-face communications.
- Continued work on GitBox, in preparation for moving all projects
over from git-wip.
- Work on replacing our email infrastructure (from an old FreeBSD
system creaking along, to an Ubuntu-based server) continues. The old
server lives under a decade of patches and custom work, so our
largest hurdle is archeology. The new server is reaching a state for
testing, and then slow migration in a month or three.
- Various work on making our monitoring, logging, and alerting
processes more regular across our multitude of VMs.
- A number of our donated Jenkins nodes had small drives, which had
been causing problems. The sponsor has upgraded those VMs to larger
drives, and we've re-imaged and re-integrated them into Jenkins.
- We had a security issue with our Sonarcube analysis server that has
been resolved, along with assisting some projects to use the new setup.
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Rich Bowen]
We have signed a contract to produce ApacheCon North America 2019 at
the Flamingo hotel in Las Vegas, September 9th through 12th, 2019.
We have also entered an agreement with Virtual for the production of
that event.
You will see announcements over the coming days, to every mailing list
you're on, about this event, and we ask that you help amplify that
message.
The DC road show has been postponed, due to a variety of difficulties
with sponsors, and with the venue. We hope to have an updated date for
that event within the next few weeks.
Discussion continues around the Chicago Road Show, 2019, with a
proposal for the event being submitted by, and championed by, Trevor
Grant.
Discussion around ApacheCon EU 2019 has stalled, and we need to get
that going again. Two people have stepped up to assist with that
effort so that I, Rich, don't have to carry that event myself, and
this is hugely appreciated.
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
-----------------------------------------
Attachment 7: Report from the VP of Finance [Tom Pappas]
VP of Finance 2018 Report,
The major activity that occurred this month was my meeting with a
partner from one of the largest CPA firms in Massachusetts mainly to
discuss his experience with his clients Endowments and some other
topics. A note will be coming out on the Finance@ list, in the near
future.
I was also able to attend the monthly Fundraising call in October and
have been working on assisting and adding Guidance where I can.
-----------------------------------------
Attachment 8: Report from the VP of W3C Relations [Andy Seaborne]
Nothing to report this month.
-----------------------------------------
Attachment 9: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
I would like to request board's attention on the CCLA discussion that's been
simmering for a month or so now. There are no other issues that require board
attention at the moment.
Legal Affairs committee for the past month has been mostly business as usual
with an average number of LEGAL jiras coming in and requiring our attention.
Once again, Assistant V.P., Legal Affairs has been doing excellent job at
triaging legal JIRAs and making sure we make progress on addressing our
backlog. We are currently at 22 open JIRAs with the oldest dating back to Jan
2017.
Mark Radcliffe arranged for a meeting with the Intellectual Property Counsel of
a major US corporation that was focused on educating them on the evolution
of Apache License and general ASF's policies around patent trolling.
I've been approached by members of the Silicon Valley VC community involved in
Common Clause discussions seeking to build more of a relationship with ASF.
The initial conversation went well and I expect them to follow up on a
legal-discuss mailing list.
-----------------------------------------
Attachment 10: Report from the Apache Security Team Project [Mark J. Cox]
Continued work on incoming security issues, keeping projects reminded
of outstanding issues, and general oversight and advice.
Stats for October 2018:
11 [license confusion]
21 [support request/question not security notification]
Security reports: 28 (last months: 32, 37, 32)
3 [hadoop], [ofbiz], [syncope]
2 [httpd], [lucene], [openoffice], [spark]
1 [hc], [nifi], [nutch], [oozie], [shindig], [shiro],
[spamassassin], [subversion], [tapestry], [tomcat], [site]
In total, as of 1st November, we're tracking 90 (last month: 87)
open issues across 42 projects, median age 73 (last month: 86)
days. 57 of those issues have CVE names assigned.
5 (last month: 4) of these issues, across 4 projects, are older
than 365 days.
-----------------------------------------
Attachment 11: Report from the VP of Data Privacy [Chris Mattmann]
The RFC period is underway for our draft privacy policy. Several members and
VP infrastructure have weighed in. I will continue to collect feedback through
the CY, and publish the draft in Jan 2019 with whatever feedback and comments
received by then. Keep them coming.
-----------------------------------------
Attachment A: Report from the Apache Ambari Project [Jayush Luniya]
## Description:
- Apache Ambari simplifies provisioning, managing, and monitoring of Apache
Hadoop clusters.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Since the last report, the community released Ambari 2.7.1. This
maintenance release resolved 159 issues.
- The community is continuing to make steady progress on the revamped
architecture chalked out for future Ambari major release.
## Health report:
- The development community and engagement remains strong; we have 102
committers on the project, with 2 new PMC members added since the last
report.
## PMC changes:
- Currently 48 PMC members.
- New PMC members:
- Ishan Bhatt was added to the PMC on Thu Oct 25 2018
- Oliver Szabo was added to the PMC on Wed Oct 17 2018
## Committer base changes:
- Currently 102 committers.
- No new committers added in the last 3 months
- Last committer addition was Krisztian Kasa at Thu Jun 21 2018
## Releases:
- 2.7.1 was released on Sun Aug 26 2018
## Mailing list activity:
- Apache Ambari has moved from ReviewBoard to GitBox for code reviews and
hence there is no activity on
reviews@ambari.ap ache.org<mailto:reviews@ambari.apache.org><mailto:reviews@ambari.apache.org>
- dev@ambari.apache.org<mailto:dev@ambari.apache.org>:
- 299 subscribers (up 0 in the last 3 months):
- 54 emails sent to list (46 in previous quarter)
- issues@ambari.apache.org<mailto:issues@ambari.apache.org>:
- 47 subscribers (up 0 in the last 3 months):
- 2953 emails sent to list (3549 in previous quarter)
- reviews@ambari.apache.org<mailto:reviews@ambari.apache.org>:
- 60 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (0 in previous quarter)
- user@ambari.apache.org<mailto:user@ambari.apache.org>:
- 479 subscribers (down -5 in the last 3 months):
- 28 emails sent to list (60 in previous quarter)
## JIRA activity:
- 413 JIRA tickets created in the last 3 months
- 370 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment B: Report from the Apache Ant Project [Jan Materne]
## 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:
- In progress of fixing some issues with Java 11.
## 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.
## PMC changes:
- Currently 23 PMC members.
- No new PMC members added in the last 3 months
- Magesh Umasankar was (re)added to the PMC on Fri Jul 06 2018
## Committer base changes:
- Currently 30 committers.
- No new committers added in the last 3 months
- Last committer addition was Gintas Grigelionis at Sat Aug 05 2017
## Releases:
- Last release was Ant 1.10.5 on Fri Jul 13 2018
-----------------------------------------
Attachment C: 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
======
Note that this report will be limited as it only covers one month. This
is primarily being used as an opportunity to respond to the query raised
following the report submitted in October. See below.
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
=======================
Since the last report, the sprint mentioned in the report from October has
happened. As a first sprint the main thrust of this was to iron out some
details and agree on some limited goals to progress work on the bloodhound
core experiment. The chair is expected to arrange further sprints to help
define a definite period over which they can look to try to work on the
project with some immediate advice being available from others.
Further discussion on this may be expected in the December report.
Responses to Board Queries
==========================
> idf: Can you please check/ confirm that there are at least three PMC
> members providing oversight?
We can confirm that this is the case at the moment. We are cutting it fine
at three PMC members who are active enough to qualify for the moment. These
are John Chambers, Gary Martin and Dammina Sahabandu. There have been the
occasional interjections from others but we stop short of suggesting any
more than three are active for the moment.
We are obviously concerned with this but consider the best way to deal with
this is to make progress, look more appealing (by the move to frameworks
that are either already more familiar or would benefit new committers to
learn and apply beyond this project) and generally easier to contribute
(looking at the use of git as a more familiar tool and looking at how other
Apache projects make use of pull requests.)
-----------------------------------------
Attachment D: 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.
Apache DistributedLog is a high-level API and service layer for
Apache BookKeeper, providing easier access to the BookKeeper
primitives. It is a subproject of Apache BookKeeper.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- 4.8.0 was released on Wed Sep 26 2018
- 4.8.1 is going to be released
- The growth of Apache Pulsar community also help grow the adoption
of BookKeeper.
This helps building the ecosystem around BookKeeper.
## Health report:
- Development continues at a steady pace. We are merging multiple PRs per
week on average.
- Mailing list and slack discussions are brisk, in particularly around the
active projects.
- The community holds a bi-weekly meeting on Hangout.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Enrico Olivelli on Thu Feb 22 2018
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Andrey Yegorov at Fri Feb 09 2018
## Releases:
- 4.7.1 was released on Tue Jun 19 2018
- 4.8.0 was released on Wed Sep 26 2018
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Enrico Olivelli on Fri Feb 23 2018
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Andrey Yegorov at Fri Feb 09 2018
## Releases:
- 4.8.0 was released on Wed Sep 26 2018
## Mailing list activity:
- Discussions mostly run on dev@ mailing list, distributedlog lists
are mostly unused, now that the project as been merged completely with
BookKeeper and users started to use the version bundled with
BookKeeper releases.
- dev@bookkeeper.apache.org:
- 103 subscribers (down -1 in the last 3 months):
- 125 emails sent to list (132 in previous quarter)
- distributedlog-commits@bookkeeper.apache.org:
- 12 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (2 in previous quarter)
- distributedlog-dev@bookkeeper.apache.org:
- 41 subscribers (down -1 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- distributedlog-issues@bookkeeper.apache.org:
- 9 subscribers (up 0 in the last 3 months):
- 4 emails sent to list (2 in previous quarter)
- distributedlog-user@bookkeeper.apache.org:
- 26 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- issues@bookkeeper.apache.org:
- 8 subscribers (down -1 in the last 3 months):
- 2686 emails sent to list (1952 in previous quarter)
- user@bookkeeper.apache.org:
- 115 subscribers (down -2 in the last 3 months):
- 20 emails sent to list (39 in previous quarter)
-----------------------------------------
Attachment E: Report from the Apache Brooklyn Project [Geoff Macartney]
## Description:
- Apache Brooklyn is a software framework for modelling, 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 are pleased that the new UI has drawn some initial commits
from new contributors.
- Rather than making a 1.0.0 release of Brooklyn in the summer, we decided we
would benefit from an interim release first, given that the new UI is so
recent. Accordingly we have released Apache Brooklyn 1.0.0-M1 as a first
milestone on our way to an official 1.0.0 release.
## Health report:
- The project continues with a regular turnover of pull requests and commits,
especially around the new UI that was contributed in May.
- We continue to monitor our community for potential new committers and PMC
members with the aim of regularly adding individuals (see "PMC Changes").
## PMC changes:
- Currently 16 PMC members.
- Duncan Grant was added to the PMC on Thu Aug 30 2018
## Committer base changes:
- Currently 16 committers.
- No new committers added in the last 3 months
- Last committer addition was Duncan Grant at Wed Jun 13 2018
## Releases:
- 1.0.0-M1 was released on Mon Sep 17 2018
## JIRA activity:
- 9 JIRA tickets created in the last 3 months
- 3 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment F: 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:
There are no issues requiring board attention at this time.
## Activity:
The project is moving at a slow pace with a few commits in the last months.
Recently there was more activity directly on the github repository with
multiple contributions from one person.
We have contacted that person and just confirmed that they'd be willing
to engage in becoming a committer.
## Health report:
The project has been stable for a long while and the space of build
tools for Java projects has been overall stagnant for a number of years.
## 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.6 on May 12th 2018
## Mailing list activity:
- users@buildr.apache.org:
- 125 subscribers (down -1 in the last 3 months):
- 4 emails sent to list (4 in previous quarter)
- dev@buildr.apache.org:
- 49 subscribers (up 0 in the last 3 months):
- 11 emails sent to list (8 in previous quarter)
- ci@buildr.apache.org:
- 12 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment G: 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:
Several months ago, DataStax had made a change around an assignment of IP
clause in the ICLA for their Java Driver (which serves as a reference
implementation for the native protocol) that had prevented some users from
contributing. We were able to work with them to get that change rolled back.
This was a pretty serious issue given that some features in-tree rely on the
driver as a dependency. We have asked to have the driver donated to the
project and they have declined.
We have recently voted to begin the process of importing the GoCQL driver, but
that project's policy of making every contributor an author may make this
impossible given we would have to get signoff from each person:
https://github.com/gocql/gocql/blob/master/AUTHORS
This quarter, we started a series of blog posts and have had a steady stream
of community contributions for content: http://cassandra.apache.org/blog/
The blog has been well received and is serving as a method for distributing
information about the changes we have been making for 4.0.
## Health report:
Project activity is up substantially in the context of development
discussions. We have moved into a freeze in anticipation of testing 4.0 and
have worked with the community to put together a testing plan for which many
members of the community have already signed up:
https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+Quality%3A+Components+and+Test+Plans
In parallel we have begun performance testing 4.0 and have already seen order
of magnitude improvements of cluster startup times, streaming data to new
nodes and internode messaging. This has been the direct result of a re-write
of the internode communication layer to rely on NIO via the Netty API. These
improvements have been tracked on the following parent issue:
https://issues.apache.org/jira/browse/CASSANDRA-14746
## PMC changes:
We have added four new PMC members during this period. There are currently 31
PMC members.
- New PMC members:
- Ariel Weisberg was added to the PMC on Tue Sep 25 2018
- Benedict Elliott Smith was added to the PMC on Tue Sep 25 2018
- Benjamin Lerer was added to the PMC on Wed Aug 15 2018
- Stefania Alborghetti was added to the PMC on Thu Sep 27 2018
## Committer base changes:
There are currently 50 committers. No new committers added in the last 3
months.
## Releases:
The last release was 2.2.13 on Wed Aug 01 2018.
## Mailing list activity:
We have had a substantial uptick in traffic on the development mailing list as
a result of robust discussions around a feature freeze for 4.0, calls for
participation for testing 4.0, and inclusion of a side-car management process
for repair.
- dev@cassandra.apache.org:
- 1624 subscribers (down -1 in the last 3 months):
- 482 emails sent to list (303 in previous quarter)
- pr@cassandra.apache.org:
- 13 subscribers (up 1 in the last 3 months):
- 595 emails sent to list (514 in previous quarter)
- user@cassandra.apache.org:
- 3020 subscribers (down -43 in the last 3 months):
- 815 emails sent to list (874 in previous quarter)
## JIRA activity:
JIRA activity is lower this quarter as we have been primarily focused around
fixing bugs for 4.0.
- 245 JIRA tickets created in the last 3 months
- 133 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment H: 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
Question of the board to the previous report:
rb: 5 years is a really long time with no change to your committer
list. Are there any community members who you are actively
mentoring towards committership?
Answer: No, there are not any.
Hasan sent a request to the dev list to vote whether to move Apache
Clerezza to the Attic. Votes are expected within this week.
RELEASE
Latest release was partial-release-201604 created on May 13, 2016.
ACTIVITY
Refactoring of the 'reunited' branch of Apache Clerezza is still ongoing.
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 February 2018.
-----------------------------------------
Attachment I: 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 or
resolved since last report. A little more activity on both users and dev
mailing-lists, even if still at a low level. The project is mainly in
maintenance mode.
## PMC changes:
None. Most recent addition: 2012-07-06
## Committer base changes:
None. Most recent addition: 2012-07-06
-----------------------------------------
Attachment J: Report from the Apache Community Development Project [Sharan Foga]
## Description:
- The Community Development PMC is responsible for helping people become
involved with Apache Projects
## Issues:
- No issues require board attention at the moment
## Activity:
Apache Project Logos: A key activity this quarter was the co-ordination and
set up a central logo page and repository [1] for high resolution logos for
all ASF projects. Feedback and participation from projects was extremely
positive and we have up to date versions of all ASF project logos available in
several formats.
New PMC Members and Committer: Two new PMC members have been added, Trevor
Grant and Ruth Suehle. Both have been very active in community development
efforts. We have also added a new committer, Kristopher Traquair in
recognition of the photographic work done during Apachecon NA in Montreal.
This is in line with our commitment to highlight that noncoding contributions
as well a coding contributions earn merit.
Events: We are continuing to be active in external events. During September we
participated at Solutions Hamburg and have several events coming up including
Codemotion in Madrid, Berlin and the Paris Open Source Summit.
Diversity Survey: It has been nearly two years since we ran the Committer
Diversity survey and have had discussions around re-running it. The community
has been very positive and many offers of help have been received to help with
review and support.
## Health report:
- In our previous report there was some concern regarding not having enough
volunteers to participate in the increased number of events we have been
invited to. Fortunately we have found that new people are coming forward to
volunteer to take on these co-ordination roles
- Our monthly blog update has slipped and we are actively looking for people
from the community to help provide content or help with putting it
together.
## PMC changes:
- Currently 28 PMC members.
- New PMC members:
- Trevor Grant was added to the PMC on Wed Sep 26 2018
- Ruth Suehle was added to the PMC on Wed Sep 26 2018
## Committer base changes:
- Currently 29 committers.
- New commmitters:
- Kristopher Traquair was added as a committer on Tue Oct 16 2018
## Mailing list activity:
- Mailing list traffic has increased over the quarter with a lot of active
and interesting discussions. The increase could also be linked to the
number of events we are participating in (e.g CFP notifications and event
reminders)
- dev@community.apache.org:
- 869 subscribers (up 22 in the last 3 months):
- 498 emails sent to list (344 in previous quarter)
## JIRA activity:
- 8 JIRA tickets created in the last 3 months
- 4 JIRA tickets closed/resolved in the last 3 months
[1] https://s.apache.org/32Cc
-----------------------------------------
Attachment K: 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:
- Gear-up for the 2.3.0 release continuing our pattern of one
big feature for every feature release. This time, clustered
purge that even replication clients can make use of.
- Near completion of getting CouchDB to build an run on arm64.
- Continued activity on infrastructure like build tooling, CI,
test suites (including a completely new test suite written in
Elixir) to streamline our release processes, and simplify
consumption of CouchDB in various shapes and forms.
- Presence at ApacheCon NA in Montreal with two talks.
## Health report:
- Project activity is steady and as expected.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Nick Vatamaniuc on Tue Nov 07 2017
## Committer base changes:
- Currently 63 committers.
- No new committers added in the last 3 months
- Last committer addition was Peng Hui Jiang at Sat Mar 03 2018
## Releases:
- Last release was 2.2.0 on Tue Aug 07 2018
-----------------------------------------
Attachment L: 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
Since the last report, 0.13 has been released. (Announcements and final
paperwork pending). Activity has been low on the project, but we still managed
6 votes (3 binding) over a 5 day period on the release.
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.13 was released Nov 5th, 2018 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 M: Report from the Apache DeltaSpike Project [Mark Struberg]
## 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:
We switched to Java8 as minimum requirement in DeltaSpike-1.9.0.
There have been discussions about JavaEE 8 support, but nothing got
decided yet.
## Health report:
Health is basically fine but activity could of course be 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 34 committers.
- No new committers added in the last 3 months
- Last committer addition was Alexander Falb at Wed Aug 01 2018
## Releases:
- 1.9.0 was released on Mon Sep 10 2018
## 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.
- users@deltaspike.apache.org:
- 177 subscribers (down -1 in the last 3 months):
- 29 emails sent to list (19 in previous quarter)
- dev@deltaspike.apache.org:
- 101 subscribers (up 2 in the last 3 months):
- 102 emails sent to list (121 in previous quarter)
## JIRA activity:
- 8 JIRA tickets created in the last 3 months
- 10 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment N: Report from the Apache DRAT Project [Chris Mattmann]
## Description:
- Apache DRAT is a distributed, parallelized (Map Reduce) wrapper around
Apache RAT™ and other code auditing tools to allow it to complete on large
code repositories of multiple file types.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The next steps are to make an RC1. Chris Mattmann will send a thread to the
dev list and spend some time in the next few months putting this up.
- Though activity has slowed a bit we have a functional Apache DRAT prototype
working for the ASF (similar to a "Gump" style service) and are ready to
roll an RC1.
## Health report:
- We are ready for a 1.0 RC1. Chris Mattmann will volunteer to be the RM.
- We expect some activity to pick up with 1.0 RC1.
- In addition we also expect integration of the Avro integration work from
Apache OODT (not a blocker to 1.0RC1 for DRAT) will also spurn some
interest.
- We did take feedback from Ted Dunning after standing up the Apache DRAT
prototype on our VM and update the UI based on his feedback (you can now
search by projects in the DRAT UI).
- Ahmed our awesome GSOC 2018 student was added as a PMC member and
committer.
## PMC changes:
- Currently 14 PMC members.
- Ahmed Ifhaam was added to the PMC on Thu Aug 30 2018
## Committer base changes:
- Currently 14 committers.
- Ahmed Ifhaam was added as a committer on Tue Aug 28 2018
## Releases:
- Chris Mattmann will volunteer to be the RM for Apache DRAT 1.0. We slipped
a little but are on target for a CY2018/1st Q 2019 release.
## Mailing list activity:
- Mailing list activity took a slight dip. Main reason I believe is that we
are waiting to test and integrate Apache OODT 1.9-dev with the AvroRPC
module in our code base. It's not a blocker to releasing 1.0 for Apache
DRAT but I think Imesha is waiting for that to be tested. Mailing list
activity will probably spike for a bit in the next quarter as we roll RC1
for 1.0 Apache DRAT.
- dev@drat.apache.org:
- 16 subscribers (up 0 in the last 3 months):
- 56 emails sent to list (221 in previous quarter)
- issues@drat.apache.org:
- 10 subscribers (up 0 in the last 3 months)
-----------------------------------------
Attachment O: Report from the Apache Drill Project [Arina Ielchiieva]
## 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.14.0, including
the following enhancements:
- Drill in a Docker container
- Image metadata format plugin
- Upgrade to Calcite 1.16.0
- Kafka plugin push down support
- Phonetic and String functions
- Enhanced decimal data support
- Spill to disk for the Hash Join support
- CGROUPs resource management support
- Lateral / Unnest support (disabled by default)
- Support Transitive Closure during Filter Push Down and Partition Pruning
- Batch processing improvements to limit the amount of memory for Hash Join,
Union All, Project, Hash Aggregate and Nested Loop Join.
- There were active discussions about schema provision in Drill. Based on
these discussions two projects are currently evolving: Drill metastore and
schema provision in the file and in a query.
- Apache Drill book has been written by two PMC members (Charles and Paul).
- Drill developer meet up will be held on November 14, 2018.
The following areas are going to be discussed:
- Storage plugins
- Schema discovery & Evolution
- Metadata Management
- Resource management
- Integration with Apache Arrow
## 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 are stable.
- Three committers and three new PMC member were added in the last period.
## PMC changes:
- Currently 23 PMC members.
- New PMC members:
- Boaz Ben-Zvi was added to the PMC on Fri Aug 17 2018
- Charles Givre was added to the PMC on Mon Sep 03 2018
- Vova Vysotskyi was added to the PMC on Fri Aug 24 2018
## Committer base changes:
- Currently 49 committers.
- New commmitters:
- Chunhui Shi was added as a committer on Thu Sep 27 2018
- Gautam Parai was added as a committer on Mon Oct 22 2018
- Hanumath Rao Maduri was added as a committer on Thu Nov 01 2018
- Weijie Tong was added as a committer on Fri Aug 31 2018
## Releases:
- 1.14.0 was released on Sat Aug 04 2018
## Mailing list activity:
- dev@drill.apache.org:
- 427 subscribers (down -6 in the last 3 months):
- 2827 emails sent to list (2126 in previous quarter)
- issues@drill.apache.org:
- 18 subscribers (down -1 in the last 3 months):
- 3487 emails sent to list (4769 in previous quarter)
- user@drill.apache.org:
- 597 subscribers (down -6 in the last 3 months):
- 332 emails sent to list (346 in previous quarter)
## JIRA activity:
- 164 JIRA tickets created in the last 3 months
- 128 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment P: 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 contrast to object-relational-mapping like with JPA
It encapsulates the functionality of a RDBMS in a powerful, vendor
independent, intuitive and maintenance friendly API providing a maximum of
compile-time-safety.
## Issues:
- there are no issues requiring board attention at this time.
## Activity:
- This quarter we have completed our work on release 2.4.7 which we have
finally published on Oct 31. The release contains 9 bugfixes and 18
improvements. The main new feature is a template that can be used
to build clients using the JavaScript framework vue and a REST server
backend utilizing database metadata.
## Health report:
- The project remains healthy. There are about 5 committers who
contribute to the project and who have approved the release.
## 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:
- empire-db-2.4.7 was released on Wed Oct 31 2018
## Mailing list activity:
- dev@empire-db.apache.org:
- 36 subscribers (up 0 in the last 3 months):
- 45 emails sent to list (6 in previous quarter)
- user@empire-db.apache.org:
- 54 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (3 in previous quarter)
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 27 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment Q: Report from the Apache Flume Project [Mike Percy]
## 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.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
This quarter:
- Several improvements were made, including bug fixes and minor feature and
configuration enhancements to existing subcomponents.
- There has been recent work on enhancing the build, including adding support
for SpotBugs.
- Discussions have started regarding a 1.9 release.
## Health report:
- Ferenc Szabo is doing basically all of the commits these days.
- There have been several commits this quarter from some newer promising
contributors.
- There is a slow but steady heartbeat of activity on the project recently
(~1 commit / week).
## PMC changes:
- Currently 23 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Denes Arvay on Sun Nov 05 2017
## Committer base changes:
- Currently 31 committers.
- No new committers added in the last 3 months
- Last committer addition was Attila Simon at Sat Nov 04 2017
## Releases:
- Last release was 1.8.0 on Tue Oct 03 2017
## Mailing list activity:
The majority of our mailing list traffic is code review interactions. There
was a small uptick in code review activity this quarter compared to the
previous one as well as discussion about an upcoming release.
- dev@flume.apache.org:
- 280 subscribers (up 1 in the last 3 months):
- 42 emails sent to list (34 in previous quarter)
- issues@flume.apache.org:
- 9 subscribers (up 0 in the last 3 months):
- 167 emails sent to list (124 in previous quarter)
- user@flume.apache.org:
- 667 subscribers (down -3 in the last 3 months):
- 7 emails sent to list (14 in previous quarter)
## JIRA activity:
- 16 JIRA tickets created in the last 3 months
- 16 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment R: 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.
This quarter there has been no activity on any Forrest mail list.
At this report, two 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 indicated presence: barely potential for sufficient oversight.
Please see the detailed status notes for the June 2018 report.
At that report a non-PMC member indicated that they intended to produce a
release. During this past quarter (August-November) there has been no
visible activity. The last action was my note to the dev list around
7 August, explaining a wrinkle in the documented release process, and
summarising some history about the last release. There was no follow-up.
It seems that we should tread-water for a while longer, to give the best
chance for this to happen.
Security issues published:
None.
Progress of the project:
None.
-----------------------------------------
Attachment S: Report from the Apache FreeMarker Project [Dániel Dékány]
## Description:
Apache FreeMarker is a template engine, i.e. a generic tool to generate text
output based on templates. Apache FreeMarker is implemented in Java as a class
library for programmers.
FreeMarker 2 (the current stable line) produces releases since 2002. The
FreeMarker project has joined the ASF in 2015, and graduated from the
Incubator in early 2018.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
Activity was low in the last months. The most notable event was the donation
of a Maven plugin to the project from Oath Inc., which we plan to generalize
further and release in the future. (The code base was given to the ASF
according to https://issues.apache.org/jira/browse/LEGAL-418. Required CCLA
and ICLA-s were received.)
## Health report:
Activity is relatively low but steady, as it's usual for this project. User
question (mostly on StackOverflow) and new Jira issues are being answered
promptly. The short term goal is to release the next micro version (2.3.29) in
December. The long term goal is continuing the ongoing development on the 3.0
branch, so that the project can innovate and the code base can become much
cleaner (and more attractive for new committers), instead of being blocked by
15 years of historical baggage.
## PMC changes:
- Currently 7 PMC members.
- No changes since the graduation on 2018-03-21
## Committer base changes:
- Currently 7 committers.
- No changes since the graduation on 2018-03-21
## Releases:
- 2.3.28 was released on Wed Apr 04 2018
-----------------------------------------
Attachment T: 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:
- We released v1.7.0, containing 859 commits resolving 196 bugs, 98
improvements and features, and a total of 357 JIRA tickets
- We've made a number of build improvements, including upgrading to Gradle
v4.10.1
- We've begun testing with Java 11 and have added automated Windows testing to
our CI jobs.
- We have reviewed and acted on a number of code issues reported by
lgtm.com <http://lgtm.com/>.
- We discussed use of Lombok and decided that adoption would prove to be a
barrier to users and contributors.
- We added a notifications@ mailing list to track GitHub PR activity.
- We agreed to adopt a quarterly release schedule to improve predictability of
releases.
- We reorganized the top-level wiki for better navigation and
discoverability. We also added a page to track conference presentations,
blog postings, and other media.
- The Geode Summit at SpringOnePlatform 2018 was very well-attended with over
400 people filling the conference room. Both users and committers alike
presented 15 talks during the conference. The sessions were recorded and
available on youtube.
## Health report:
- Overall project momentum is picking back up. We are seeing good results from
the efforts to improve test reliability
## PMC changes:
- Currently 46 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dick Cavender on Tue Feb 20 2018
## Committer base changes:
- Currently 98 committers.
- New commmitters:
- Addison Huddy was added as a committer on Sat Sep 01 2018
- Alexander Murmann was added as a committer on Sat Sep 08 2018
- Blake Bender was added as a committer on Sat Sep 01 2018
- Helena Bales was added as a committer on Sat Sep 01 2018
- Ivan Godwin was added as a committer on Sat Sep 01 2018
- Juan Ramos was added as a committer on Sat Sep 08 2018
- Ryan McMahon was added as a committer on Sat Sep 01 2018
- Michael Martell was added as a committer on Sat Sep 08 2018
- Michael Oleske was added as a committer on Sat Sep 08 2018
- Robert Houghton was added as a committer on Mon Oct 01 2018
- Sean Goller was added as a committer on Sat Sep 01 2018
## Releases:
- 1.7.0 was released on Thu Oct 04 2018
- We have begun work on the 1.8.0 release. We expect the release to include
geode-native (a C++/C# client for Geode) for the first time.
- We're continuing to rotate release manager duties among committers toensure
the release process is well documented and repeatable.
## Mailing list activity:
- Mailing lists have remained active and have been seen a marked increase in
use for both development and issues
- The increase in the user@ mailing list is very encouraging and seems to
correlate with the Geode Summit.
- dev@geode.apache.org:
- 190 subscribers (up 8 in the last 3 months):
- 889 emails sent to list (624 in previous quarter)
- issues@geode.apache.org:
- 55 subscribers (up 1 in the last 3 months):
- 4283 emails sent to list (2707 in previous quarter)
- notifications@geode.apache.org:
- 7 subscribers (up 7 in the last 3 months):
- 1998 emails sent to list (0 in previous quarter)
- user@geode.apache.org:
- 249 subscribers (up 7 in the last 3 months):
- 201 emails sent to list (138 in previous quarter)
## JIRA activity:
- 456 JIRA tickets created in the last 3 months
- 485 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment U: Report from the Apache Giraph Project [Dionysios Logothetis]
## Description:
- 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.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Upgrade to Java 8 as the minimum requirement.
- Cleaning up old Hadoop profiles.
- Small fixes and improvements.
- More cleaning-up of old JIRA issues.
## Health report:
- Committee Health score: 1.43 (Mostly Okay)
- In this last quarter, we've seen small contributions from external users.
- I have also solicited a bit larger contributions from members of the
academic community: (i) one of them is the implementation of a new
technique for storing the graph in a compressed form. This currently under
review and has not been committed yet, (ii) a team of external
collaborators have submitted the implementation of a new algorithm for
review, (iii) I've asked another user to contribute a new algorithm
implementation. This is still under discussion as to what algorithm to
implement.
- New release was delayed as I'd like to do some more cleanup, mostly get rid
of old hadoop profiles, before this.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dionysios Logothetis on Sun Apr 22 2018
## Committer base changes:
- Currently 20 committers.
- No new committers added in the last 3 months
- Last committer addition was Dionysios Logothetis at Mon Apr 23 2018
## Releases:
- Last release was 1.2.0 on Thu Oct 20 2016
## Mailing list activity:
- Even though there's been a decrease in mailing list members, we have
actually seen more activity in this last quarter.
- dev@giraph.apache.org:
- 268 subscribers (down -7 in the last 3 months):
- 93 emails sent to list (74 in previous quarter)
- user@giraph.apache.org:
- 442 subscribers (down -3 in the last 3 months):
- 19 emails sent to list (16 in previous quarter)
## JIRA activity:
- After a long time, this quarter there was a big pull request from a member
outside the Giraph committee (details in health report section).
- 12 JIRA tickets created in the last 3 months
- 14 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment V: 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, distributed in-memory key/value stores, in-memory
data grids, in-memory caches, distributed multi-model stores, and hybrid
in-memory architectures. Gora also enables analysis of data with extensive
Apache Hadoop MapReduce and Apache Spark support.
## Issues:
As of 2018-11-15 the PMC is currrently VOTE'ing on a change of Project Chair
for the Apache Gora project. The VOTE will be closed and a RESOLUTION will be
passed to the board for consideration by the time the November 2018 board
meeting takes place.
## Activity:
Activity has been reasonably post summer, the Gora project did recently
however welcome a new Committer and PMC member Carlos Muñoz was added as a
committer on Mon Nov 12 2018.
## Health report:
The Gora project is in good health. Mailing lists are responsive with VOTE'ing
initiatives seeing good response from the community. The project will most
likely look towards a new release once the PMC Chair position has been
transferred.
## PMC changes:
- Currently 26 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Cihad Guzel on Tue Mar 13 2018
## Committer base changes:
- Currently 27 committers.
- Carlos Muñoz was added as a committer on Mon Nov 12 2018
## Releases:
- Last release was 0.8 on Mon Sep 18 2017
## Mailing list activity:
Mailing lists number remain allmost flatlined with a very slight decrease on
dev@, our primary communication medium. Hopefully with the transition of PMC
duties we can inject some renewed energy into the project and see incresed
initiatives.
- dev@gora.apache.org:
- 72 subscribers (down -1 in the last 3 months):
- 145 emails sent to list (138 in previous quarter)
- user@gora.apache.org:
- 75 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (5 in previous quarter)
## JIRA activity:
- 6 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment W: 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 requiring board attention at this time.
- Outstanding issues: completion of the website migration is underway again
## Activity:
- This quarter, 213 commits were contributed from 14 contributors
including 8 non-committer contributors (5 new).
- Apache Groovy was downloaded 27M+ times the past three months.
Stats are from July, August, &September) across Maven Central and
Bintray JCenter for a total of 75.7M+ since the beginning of the year.
Generally, 2/3 of the downloads are from Maven Central, vs 1/3 from
Bintray JCenter. We don't have stats from ASF mirrors.
About 3/4 of the downloads are for Groovy 2.5.3 or the previous 2.5.x/2.4.x
versions. There is still a lot of users downloading the latest 2.4.x releases,
almost as much as the 2.5.x ones. And close to 1/4 are trying our 3.0
alphas releases.
## Health report:
- Committee Health score: 9.60 (Super Healthy)
- Release train velocity and discussions within mailing list seem healthy
## PMC changes:
Current status:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andres Almiray on Thu May 31 2018
Proposed change:
- Appoint Paul King as the new VP for the Apache Groovy PMC
## Committer base changes:
- Currently 19 committers.
- No new committers added in the last 3 months
- Last committer addition was Remko Popma at Sat Jul 07 2018
## Releases:
- 2.5.2 was released on Tue Aug 14 2018
- 2.5.3 was released on Sun Oct 14 2018
## Mailing list activity:
- Activity relatively stable
## JIRA activity:
- 136 JIRA tickets created in the last 3 months
- 113 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment X: Report from the Apache Hama Project [Chia-Hung Lin]
## Description:
- Apache Hama is a framework for Big Data analytics based on the Bulk
Synchronous Parallel paradigm
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- A branching for further componentization core module is underway, preparing
for 0.8.0 release.
## Health report:
- One new committer joined the community.
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Behroz Sikander on Mon Feb 01 2016
## Committer base changes:
- Currently 18 committers.
- Last committer addition was YoungWoo Kim at Sun May 20 2018
## Releases:
- Last release was hama-0.7.1 on Sun Mar 13 2016
-----------------------------------------
Attachment Y: Report from the Apache HAWQ Project [Lei Chang]
-----------------------------------------
Attachment Z: Report from the Apache Helix Project [Kishore G]
## Description:
- A cluster management framework for partitioned and replicated distributed resources
## Issues:
- NO
## Activity:
-
## Health report:
- 0.8.3 release is in prepare, will be released in early December.
- There is regular level of activities on commits, pull requests and releases.
- The dev@ list traffic is healthy, user@ list traffic is increasing.
## PMC changes:
- Currently 18 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Junkai Xue on Mon Jul 03 2017
## Committer base changes:
- Currently 19 committers.
- Jiajun Wang was added as a committer on Fri Jul 13 2018
## Releases:
- Last release was 0.8.2 on July 30 2017
## Mailing list activity:
- Mailing list activity is in normal level.
- dev@helix.apache.org:
- 70 subscribers (up 1 in the last 3 months):
- 245 emails sent to list (336 in previous quarter)
- user@helix.apache.org:
- 104 subscribers (up 0 in the last 3 months):
- 55 emails sent to list (24 in previous quarter)
## JIRA activity:
- 38 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AA: Report from the Apache HTTP Server Project [Daniel Gruno]
## Description:
- The Apache HTTP Server Project is an effort to develop and maintain an
open-source HTTP server for modern operating systems including UNIX and
Windows. The goal of this project is to provide a secure, efficient and
extensible server that provides HTTP services in sync with the current HTTP
standards.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The main focus this quarter has been put on releasing HTTPd with support
for the latest OpenSSL (1.1.1) and thus TLS/1.3, as well as fixing up the
test framework and miscellaneous supporting applications.
- The project worked with Sally to promote the 2.4.37 release, highlighting
the features mentioned in the previous bullet point. Save for a few snafus,
the workflow with the new release automation we've been working on lately
seems to be...flowing quite well :)
## Health report:
While the commit activity remains on par with the previous quarter, the
email activity, both in terms of senders and emails sent, have seen quite
an uptick
(22% each overall, 40%+ on dev@), while the number of topics went down
(-17%) to roughly 200 topics discussed in this quarter. This is primarily
explained by the focus on OpenSSL 1.1.1 and TLS 1.3 upgrades to the
httpd software, as well as extensive focus on the test framework and
related tools.
Looking at the slightly softer figures at our disposal, we see a steady
continuation of the previous quarter (and indeed previous years), with a
mostly fixed number of contributors and experience levels - a sort of
neutral trend that could be interpreted either way. On one hand, we are
doing well and retaining people that join the project. On the other hand,
the level and speed of attracting new contributors have slowed down a bit.
One can argue that this is a good thing (that we retain those that join),
as well as argue that we could do more to attract new people to the
project. My personal take is that the project is in good hands, but could
start exploring how other projects have attracted people, should we feel
this is needed in the near future. HTTPd has typically been a highly
esteemed 'flagship project', and as such, one could argue that we have been
complacent in our recruiting efforts...and while we do not appear to have
suffered from this (that we know of), I believe it prudent to become more
proactive in community outreach.
## PMC changes:
- Currently 53 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Hank Ibell on Mon Jul 09 2018
## Committer base changes:
- Currently 122 committers.
- No new committers added in the last 3 months
- Last committer addition was Sebastian Bazley at Fri Jul 13 2018
## Releases:
- 2.4.35 was released on Thu Sep 20 2018
- 2.4.37 was released on Sun Oct 21 2018
## Mailing list activity:
I've only included the lists where we have seen a noticeable change in
figures:
- users@httpd.apache.org:
- 2513 subscribers (down -4 in the last 3 months):
- 512 emails sent to list (338 in previous quarter)
- dev@httpd.apache.org:
- 824 subscribers (down -7 in the last 3 months):
- 677 emails sent to list (390 in previous quarter)
## Bugzilla Statistics:
- 51 Bugzilla tickets created in the last 3 months
- 51 Bugzilla tickets resolved in the last 3 months
-----------------------------------------
Attachment AB: Report from the Apache HttpComponents Project [Asankha Chamath 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.
- There are several casual contributors to the project. We are in the
process of evaluating one contributor for committership. A formal vote
is expected soon
## Activity:
- The team is currently working toward completing HttpCore 5.0 and
HttpClient 5.0 BETA development phase and reaching GA milestone.
## 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 contributing.
## 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:
- HttpClient 5.0-beta2 was released on Mon Oct 29 2018
- HttpCore 5.0-beta3 was released on Wed Aug 29 2018
- HttpCore 5.0-beta5 was released on Mon Oct 22 2018
-----------------------------------------
Attachment AC: Report from the Apache Ignite Project [Denis A. Magda]
## Description:
- Ignite is a memory-centric distributed database, caching, and processing
platform for transactional, analytical, and streaming workloads delivering
in-memory speeds at petabyte scale.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Ignite community is preparing to release Ignite 2.7 that adds MVCC and
Transactional SQL support, Transparent data encryption, TensorFlow
integration.
## Health report:
- Ignite PMC simplified and lowed the bar for new committers and about to
accept many valuable candidates.
## PMC changes:
- Currently 26 PMC members.
- Dmitry Pavlov was added to the PMC on Tue Aug 28 2018
## Committer base changes:
- Currently 38 committers.
- Dmitriy Govorukhin was added as a committer on Tue Aug 28 2018
## Releases:
- Last release was 2.6.0 on Mon Jul 16 2018
- dev@ignite.apache.org:
- 405 subscribers (up 20 in the last 3 months):
- 4119 emails sent to list (3298 in previous quarter)
- ci@ignite.apache.org:
- 5 subscribers (up 0 in the last 3 months)
- issues@ignite.apache.org:
- 33 subscribers (down -2 in the last 3 months):
- 10043 emails sent to list (7175 in previous quarter)
- services@ignite.apache.org:
- 7 subscribers (up 0 in the last 3 months)
- user@ignite.apache.org:
- 729 subscribers (up 20 in the last 3 months):
- 1875 emails sent to list (1830 in previous quarter)
## JIRA activity:
- 964 JIRA tickets created in the last 3 months
- 703 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AD: Report from the Apache Impala Project [Jim Apple]
## Description:
Impala is a high-performance distributed SQL engine.
## Activity:
The previous three months had 350 patches to the master branch, while this
three-month period had 330.
Prominent work in the last three months includes:
- Support for multiple DISTINCT
- The first Apache two-dot release (3.0.1) was made; normally we only do
x.y.0 releases. This was done to fix two security issues.
- Official CentOS support for developers.
- A number of changes to make the C++ code have a reduced number of undefined
behaviors.
- Support for Hadoop's connector for Azure's new storage system,
"Azure Data Lake Storage Gen2".
- Multiple improvements in resource estimation and resource management.
- Continued improvements in "local catalog" mode.
- The addition of builtin JSON parsing functions.
- Graceful node shutdown (with drain/quiesce).
## Health report:
The project remains healthy and metrics (number of commits, bugs filed, and
mailing list activity) remain healthy.
Four new contributors had patches committed.
## PMC changes:
- Currently 27 PMC members.
- Joe McDonnell was added to the PMC on Mon Aug 20 2018
## Committer base changes:
- Currently 44 committers.
- Quanlong Huang was added as a committer on Thu Aug 23 2018
## Releases:
- 3.0.1 was released on Tue Oct 23 2018
## Mailing list activity:
Mailing lists metrics that held steady:
- user@: 83 emails sent in the past 3 months, 87 in the previous cycle.
Mailing list metrics that changed more:
- dev@: 205 emails sent in the past 3 months, 299 in the previous cycle.
There is no obvious immediate cause and this is likely just statistical
fluctuation.
- reviews@: 7312 emails sent in the past 3 months, 5638 in the previous
cycle.
## JIRA activity:
- 409 JIRA tickets created in the last 3 months
- 386 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AE: Report from the Apache Incubator Project [Justin Mclean]
= Incubator PMC report for November 2018 =
=== Timeline ===
||Wed November 07 ||Podling reports due by end of day ||
||Sun November 11 ||Shepherd reviews due by end of day ||
||Sun November 11 ||Summary due by end of day ||
||Tue November 13 ||Mentor signoff due by end of day ||
||Wed November 14 ||Report submitted to Board ||
||Wed November 21 ||Board meeting ||
=== Shepherd Assignments ===
||Dave Fisher ||Edgent ||
||Dave Fisher ||Tamaya ||
||Drew Farris ||Ratis ||
||Drew Farris ||Toree ||
||John Ament ||Heron ||
||John Ament ||Joshua ||
||Justin Mclean ||Doris ||
||P. Taylor Goetz ||Marvin-AI ||
||P. Taylor Goetz ||Unomi ||
||P. Taylor Goetz ||Warble ||
||Timothy Chen ||ECharts ||
||Timothy Chen ||SDAP ||
||Timothy Chen ||Zipkin ||
||[none] ||DLab ||
||[none] ||Livy ||
||[none] ||PageSpeed ||
||[none] ||Pinot ||
||[none] ||S2Graph ||
||[none] ||Weex ||
=== Report content ===
{{{
Incubator PMC report for November 2018
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 presently 52 podlings incubating. During the month of October,
podlings executed 4 distinct releases (a low number) and there are a couple
of outstanding votes on releases for November. We added 3 new IPMC members.
Several podlings are heading towards graduation and several look like they
may retire. ServiceComb and Joshua graduated last month and we will welcome
several new podlings with votes or discussion underway for IotDB, Pinot,
Sharding-Sphere, Brpc and Iceburg. Annotator had a discussion where they
decided not to retire. BatchEE still seems stuck in performing the last
graduation steps.
Doris is taking steps to address its lack of discussion on the mailing list
and working on its first release.
MXNet had an excellent discussion around diversity and what it means to be
a committer.
Superset is slowly addressing its issues, but has not yet made an Apache
release and has continued to make unofficial releases. Its (new) mentor is
helping out with this and it has pointed out if they don't try a little
harder they may be removed from the incubator.
Unomi started graduation discussions, but run into some issues with PPMC
members missing ICLAs and its roster. It may be that IP clearance still
needs to be done.
Weex has improved with more discussion on the mailing list and discussion
and action about how to improve community growth.
Skywalking put up a discussion to graduation, but it may of been too soon,
given some irregularities with its roster and that they have only added one
committer/PPMC member during incubation but have had a large number of
contributions from many people.
Thanks to Edgenet for an honest and open assessment of where it is at.
Senssoft got a bit carried away and submitted a report when it didn't
need to. :-)
There were 6 IP clearances.
No podlings failed to report which is great to see.
The remaining missing mentors were contacted and those who didn't reply
were removed from the podlings roster. We currently have about half of the
podlings (23) with less than 3 mentors and 5 podlings only having one
mentor. To get all podlings back to 3 mentors (which seems the ideal
number) we would need 29 mentors volunteer. We're in the process of
drafting an email to the members list, to see if we can get more members to
step forward and become mentors. Several podlings have requested new
mentors but so far we've only had a few IPMC members step forward and take
on the role. (Podlings include Annotator, Dubbo, Hivemall, Superset and
Warble).
In September several incubator PMC members visited China to speak at the
Huawei Connect and COSCon'18 (where 3 different ASF incubator/Apache Ways
talks were given). Many of the talks had moderate attendance but were
streamed live to large numbers of people; one was live streamed to more than
1,000 people. Both conferences had ASF booths and we spoke to 100's of
people and gave away countless ASF stickers, pamphlets and other swag.
IPMC and board members also visited several companies; Alibaba, Huawei and
Tencent, to give talks, meet with developers contributing to ASF projects
and meet with executives to find out how these companies and the ASF can
work together. I was impressed to see Alibaba reached out to other people
contributing to the Apache Dubbo project and invited them along to the
meetings as well.
As a result of this a number of projects have a far better idea of how to
operate as an Apache project and the steps towards graduation. We are
likely to see several new (8-10) incubating projects arrive over the next
few months.
Thanks to Huawei, Alibaba and Kaiyuanshe for making this possible. Thanks
to Craig, Dave, Justin, Roman and Ross and others who gave up their time to
do this and also many thanks to the many local people who helped out at the
ASF booths, with translation of our talks and acting as guides to sometimes
bewildered and slightly confused ASF people.
Several podlings have not kept their rosters up-to-date, and this has
caused some graduation and access issues. Several of these podlings have
been contacted and asked to correct their rosters and a couple have done
so. The IPMC will keep an eye on podling reports and check that new
committers/PPMC have been added to the roster, but it would be best if the
podlings (and their mentors) take a more active role in doing this.
Some podlings are still having issues with creating initial accounts and
signing ICLAs. A proof of concept system for easy ICLA signing was made by
Daniel here https://icla.live/ .
What to do about podlings tasked with writing bylaws/guidelines is still
outstanding.
* Community
New IPMC members:
- Ioannis Canellos
- Koji Sekiguchi
- Jason Dai
People who left the IPMC:
- None
* New Podlings
- Pinot
* Podlings that failed to report, expected next month
- None
* Graduations
- Apache Griffin
* Releases
The following releases entered distribution during the month of
October:
- Apache Plc4x 0.1.0
- Apache Dubbo 2.6.4
- Apache Skywalking 5.0.0 GA
- Apache Weex 0.19.0
* IP Clearance
- Apache Arrow Parquet Ruby Library
- Apache Arrow C# Library
- Apache Beam Euphoria API
- Apache Beam Dataflow Java Worker
- Arrow Parquet GLib Library
- Mojohaus Maven Utilities, for the NetBeans podling
* Legal / Trademarks
Discussion of what needed re ICLAs, CCLA and software grants
(LEGAL-420).
* Infrastructure
No issues.
* Miscellaneous
- Discussion with UNICEF’s about bringing a project to the ASF.
- Discussion on reviewing binary releases.
- Question on mirror sites (redirection preferred).
- Update to web site with guidelines for publicity for incubating projects.
----------------------------------------------------------------------
Table of Contents
DLab
Doris
ECharts
Edgent
Heron
Livy
Marvin-AI
PageSpeed
Pinot
Ratis
S2Graph
SDAP
Tamaya
Toree
Unomi
Warble
Weex
Zipkin
Senssoft
----------------------------------------------------------------------
--------------------
DLab
DLab is a platform for creating self-service, exploratory data science
environments in the cloud using best-of-breed data science tools.
DLab has been incubating since 2018-08-20.
Three most important issues to address in the move towards graduation:
1. Execute the SGA between EPAM and the ASF so code can be imported.
2. Move bug tracking system including project backlog to Apache issue
tracking system.
3. Work toward an initial Apache release.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Nothing at this point of time.
How has the community developed since the last report?
We are not at the stage of building community so far.
How has the project developed since the last report?
Initial committers have submitted their Apache ICLA, subscribed to all
mailing lists and created Jira accounts. Functionality added:
- Administrative Web UI for roles management
- Fixed libraries installation for RStudio
- Restrict usage of EC2 instances of certain shapes to different groups
of users
- Fixed a bug on MS Azure when instance creation failed because of same
IP allocation to different instances
- Added support of Dex authentication
- Work in progress towards deployment into two VPC’s (SSN and Edge Node
into one VPC, notebooks and computational resources into separate VPC)
- Work in progress implementing Java libraries support from WebUI
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:
This is going to be our first release.
When were the last committers or PPMC members elected?
We are still operating with the set of initial committers.
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Mentors were very responsive and provided a good overview of incubation
process in general. Helped a lot providing detailed instructions on how
to get subscribed, submit ICLA application and certainly provided a
vector for next steps. The team has immediate support and can ask for
any questions.
Signed-off-by:
[X](dlab) P. Taylor Goetz
Comments: To give some context regarding the mentor question above,
I'm employed by the same company as the initial committers
and have working with them since before the proposal to
prep them for Apache.
Currently we're waiting on the SGA (I'm working on pushing it
through) which is blocking code import. Meanwhile the podling
is starting to use the mailing list and populating JIRA.
[X](dlab) Henry Saputra
Comments:
[ ](dlab) Konstantin I Boudnik
Comments:
IPMC/Shepherd notes:
--------------------
Doris
Doris is a MPP-based interactive SQL data warehousing for reporting and
analysis.
Doris has been incubating since 2018-07-18.
Three most important issues to address in the move towards graduation:
1. Move discussion to the mailing list;
2. Make our first ASF release;
3. Work on the web site.
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?
New added a contributor who contribute a feature.
How has the project developed since the last report?
Start to test the feature of streaming import and prepare to commit;
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[x] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A.
When were the last committers or PPMC members elected?
N/A.
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Yes.
Signed-off-by:
[X](doris) Dave Fisher
Comments: Still in the getting started stage ...
I did meet with Reed in person in Shenzhen.
[ ](doris) Luke Han
Comments:
[X](doris) Willem Jiang
Comments: Project team is getting used to have discussion in the
mailing list.
IPMC/Shepherd notes:
--------------------
ECharts
ECharts is a charting and data visualization library written in JavaScript.
ECharts has been incubating since 2018-01-18.
Three most important issues to address in the move towards graduation:
1. Have merged several pull request from community.
2. Received ICLA files from new contributors.
3. Preparing version 4.2.0 release.
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?
Several new contributors joined community, sending PR and helping answer
questions.
How has the project developed since the last report?
Preparing the 4.2.0 release and add some new features and fixed bugs.
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:
2018-08-04
When were the last committers or PPMC members elected?
N/A
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Yes. They helped a lot and solved many of our problems.
Signed-off-by:
[X](echarts) John D. Ament
Comments:
[ ](echarts) Kevin A. McGrail
Comments:
[X](echarts) Dave Fisher
Comments: I met with Wenli in Shenzhen.
None of the PPMC had subscribed to the private email list.
We discussed and this was corrected.
More work is coming to the dev@ list and a new release is
being Voted on.
Looking forward to more discussion on dev@.
Next report should have a better discussion about steps to
graduation.
IPMC/Shepherd notes:
--------------------
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. Re-creating a working community
2. Re-populating the PPMC
3. Replenishing the group of mentors
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
For the past months, there has been absolutely no activity in the project
Even if there has been an occasional Email from an external entity in the
last 3 months, the activity in the project has been solely me (Christofer)
writing emails without getting any form of response from the rest of the
committers, PPMCs or mentors
The main problem here is, that when being voted into the project, I had
been working on the build, but before I was able to start digging in the
code the rest of the team disappeared without me having had the chance to
do a reasonably significant amount of know-how transfer. Currently, we
have a codebase for which we have a detailed understanding of the build,
but almost none of the code itself.
How has the community developed since the last report?
* Total, we have 82 subscribers to our mailing list, an increase of 5
since the last report.
* There have been two questions asked by users and two little
discussions about these issues on the list
* Discussions started on the private list have been left unresponded
* On 19th September 2018 Christofer had a talk about Apache Edgent on
the Solutions.Hamburg TechCamp
How has the project developed since the last report?
* According to JIRA, 0 new issue were added and none were resolved in
the last 90 days
* 0 commits were made in the last 90 days.
How would you assess the podling's maturity?
After the withdrawal of most of the active committers and PPCM members
currently a new committer, PPMC and mentor-base has to be built. Being
working hard on the PLC4X podling, I am currently evaluating if I am
going to be willing and able to achieve this goal.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-12-14 Apache Edgent 1.2.0
When were the last committers or PPMC members elected?
In August 2017, we added Christofer Dutz as a new committer
and PPMC member.
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
I just double checked, but it seems our mentors are not existent
there had been one or two issues where feedback was explicitly
asked for, but both the PPMC as well as all mentors remained silent.
Except Justin mentioning the absence of mentors.
Signed-off-by:
[x](edgent) Luciano Resende
Comments:
[X](edgent) Justin Mclean
Comments:
IPMC/Shepherd notes:
Dave Fisher: If the project is to be rebooted then the PPMC needs to
be grown.
I think you might find at least one candidate from dev@ activity.
Also I noticed a JIRA - EDGENT-450 about creating an Edge
Connector for Apache Pulsar.
I've sent a note to dev@pulsar suggesting they join at dev@edgent
to help.
--------------------
Heron
A real-time, distributed, fault-tolerant stream processing engine.
Heron has been incubating since 2017-06-23.
Three most important issues to address in the move towards graduation:
1. Making the fist Apache Release. Vote for RC5 is currently on
general@incubator
2. Making several Releases
3. Continuing to grow the community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Not at this time
How has the community developed since the last report?
The community has been growing. Two more monthly meetups have been
successfully organized so far after the initial one in April 2018. We
have also seen more interests in the Heron from different channels and
getting more ideas from the community. In October 2018 there was a
presentation given at BazelCon in New York city on building Apache Heron.
How has the project developed since the last report?
There have been mainly bug fixes and improvements to existing features.
Some to note are
* Works towards Apache release and five release candidates have been
created.
* Updates for the licenses
* Updates to the documentation
* New integration tests
* New designs/works for the Streamlet API(Heron’s high level DSL)
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
No Apache releases as of yet. Latest RC was done on Oct 15th. [this might
change if our Apache release succeeds]
When were the last committers or PPMC members elected?
Ning Wang was elected a committer on accepted on 11/1/2018.
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Mentors have been very responsive and helpful.
Signed-off-by:
[ ](heron) Jake Farrell
Comments:
[ ](heron) Julien Le Dem
Comments:
[X](heron) P. Taylor Goetz
Comments:
[X](heron) David Fisher
Comments: Heron has switched its 2x monthly offline hangout for a
twice weekly "what am I up to" on dev@heron.
IPMC/Shepherd notes:
--------------------
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:
1. Grow the community to have more activities.
2. Grow more contributors and committers.
3. Regular 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?
Activity on the dev and user mailing lists as well as the rate of reported
JIRA issues has stayed steady. There has been an uptick of development
activity around adding a new feature to the project (a Hive-compatible
Thrift server implementation).
How has the project developed since the last report?
A new feature (Hive-compatible Thrift server) is being implemented and
support is being added for Apache Spark 2.4 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:
2018-02-06
When were the last committers or PPMC members elected?
2017-09-18
Signed-off-by:
[x](livy) Bikas Saha
Comments:
[ ](livy) Brock Noland
Comments:
[x](livy) Luciano Resende
Comments:
[x](livy) Jean-Baptiste Onofre
IPMC/Shepherd notes:
--------------------
Marvin-AI
Marvin-AI is an open-source artificial intelligence (AI) platform that helps
data scientists, prototype and productionalize complex solutions with a
scalable, low-latency, language-agnostic, and standardized architecture
while simplifies the process of exploration and modeling.
Marvin-AI has been incubating since 2018-08-21.
Three most important issues to address in the move towards graduation:
1.Move development infrastructure to Apache
2.Build Community
3.Build Releases
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?
* The community has already migrated most of the infrastructure to
Apache. After weeks of discussion, the community has finally come to a
consensus on the backlog for the first Apache release.
How has the project developed since the last report?
* Code infrastructure is mostly migrated, new features are being
discussed.
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:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
* At least two of the mentors are sometimes active.
Signed-off-by:
[x](marvin-ai) Jim Jagielski
Comments: Request to submit report was sent by Luciano
[x](marvin-ai) Luciano Resende
Comments:
[ ](marvin-ai) William Colen
Comments:
IPMC/Shepherd notes:
--------------------
PageSpeed
PageSpeed represents a series of open source technologies to help
make the web faster by rewriting web pages to reduce latency and
bandwidth.
PageSpeed has been incubating since 2017-09-30.
Three most important issues to address in the move towards graduation:
1. The project needs more active developers.
2. Create a first release
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The number of active developers is low.
It looks like we cannot leave this up to organic growth and would like to
brainstorm on ways to engage more developers.
How has the community developed since the last report?
One new developer was proposed to be added as a committer, but nobody
voted, so the vote failed. This vote may have been initiated too early.
In terms of users the project seems to be growing slightly still, but in
terms of developers we seem to be stalled.
How has the project developed since the last report?
A docker image for Alpine support was merged, which constitutes a non-
trivial contribution.
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?
Feb 2 2018 (Huibao Lin, elected as both committer and PMC member)
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Mentors have been helpful.
Signed-off-by:
[ ](pagespeed) Jukka Zitting
Comments:
[ ](pagespeed) Leif Hedstrom
Comments:
[X](pagespeed) Nick Kew
Comments: Iterating my comment from the last report: this looks like
a healthy github project but the Apache part is less clear.
[ ](pagespeed) Phil Sorber
Comments:
IPMC/Shepherd notes:
--------------------
Pinot
Pinot is a distributed columnar storage engine that can ingest data in real-
time and serve analytical queries at low latency.
Pinot has been incubating since 2018-10-17.
Three most important issues to address in the move towards graduation:
We are just starting the incubation and don't have much to report. Few
things we are working on:
1. Migrate the code base from LinkedIn GitHub to Apache GitHub
2. Finish the initial tasks to set up the podling - website, mailing
lists, developer icla's etc
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
How has the project developed since the last report?
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:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Signed-off-by:
[x](pinot) Kishore Gopalakrishna
Comments:
[ ](pinot) Jim Jagielski
Comments: Very, very early in process.
[ ](pinot) Roman Shaposhnik
Comments:
[x](pinot) Olivier Lamy
Comments:
IPMC/Shepherd notes:
--------------------
Ratis
Ratis is a java implementation for RAFT consensus protocol
Ratis has been incubating since 2017-01-03.
Three most important issues to address in the move towards graduation:
1. Work towards a GA release.
2. Start working on graduation template.
3. Complete name search process.
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?
2 New PPMC members have been added.
3 new contributors have been added. Total 53 contributors currently.
How has the project developed since the last report?
Rapid progress being made towards stabilization for a GA release.
53 new patches committed.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first GA release
[X] Community building
[X] Nearing graduation
When were the last committers or PPMC members elected?
2018-11-03
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Mentors are helpful.
Signed-off-by:
[X](ratis) Jakob Homan
Comments:
[X](ratis) Uma Maheswara Rao G
Comments: IMO, this project is doing well and going towards graduation.
[ ](ratis) Devaraj Das
Comments:
IPMC/Shepherd notes:
--------------------
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 third 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 beaware
of?
None
How has the community developed since the last report?
* In ACNA 2018, we announced S2Graph as the title of the Apache
S2Graph(incubating) with the build data management platform and audience
targeting online application system using Graph Database.
https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/835a6adcab1ce83a0
* There were some questions from the community about the introduction of
S2Graph.
How has the project developed since the last report?
* We have received some inquiries from the community and created an issue
that does not solve it yet.
- 5 issues are created and 0 of them are resolved since the last
report (Sep 2018).
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-08-26
When were the last committers or PPMC members elected?
None
Signed-off-by:
[ ](s2graph) Andrew Purtell
Comments:
[ ](s2graph) Seetharam Venkatesh
Comments:
[X](s2graph) Sergio Fernández
Comments: Incubating for three years;
we may need to discuss the
podling future sooner than
later.
IPMC/Shepherd notes:
--------------------
SDAP
SDAP is an integrated data analytic center for Big Science problems.
SDAP has been incubating since 2017-10-22.
Three most important issues to address in the move towards graduation:
1. Make formal SDAP (Incubating) Release
2. Improve/create user guide documentation
3. Grow Community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Added 2 new developers that are becoming familiar with the project and
will soon become committers.
SDAP has been heavily advertised at/in many Earth Science technology
forums.
SDAP was featured at the CUAHSI Biennial Colloquium with an aim towards
growing the community.
How has the project developed since the last report?
Development is still underway to push towards the first incubating
release of SDAP and each of its subcomponents.
How would you assess the podling's maturity?
Podling's still getting established.
[] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Kevin M Gill was elected on 2018-03-05
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
As mentors, we have not been very actively involved - but there's nothing ye
t that required the mentor's attention (the project is in good hands under L
ewis :-)).
Mentors are available nevertheless to help with releases and guiding the pod
ling.
Signed-off-by:
[X](sdap) Jörn Kottmann
Comments:
[X](sdap) Suneel Marthi
Comments:
IPMC/Shepherd notes:
--------------------
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. Grow the PPMC from the existing community.
2. Make another Release
3. Blog about Tamaya
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* We'd like to graduate soon and plan some reworks to access a broader
audience and collect new contributors/people interested in the project.
How has the community developed since the last report?
* frequent bugreports and discussions via Jira/mailing list
* new external contributions
How has the community developed since the last report?
* frequent bugreports and discussions via Jira/mailing list
* new external contributions
How has the project developed since the last report?
* Bugfixes, changes, discussions going on
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
Date of last release:
2017-05-28 0.3-incubating
When were the last committers or PPMC members elected?
* P. Ottlinger at 2016-04-24.
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
* John is and was the onliest active mentor and answers questions or gives
hints for quite a while.
* As the project needs a wider audience, maybe mentors with interest in Ta
maya would be welcome.
Signed-off-by:
[X](tamaya) John D. Ament
Comments: The podling hasn't executed a release in over a year, has
limited on list discussions. I would be cautious about graduating,
considering how small the community is.
[ ](tamaya) David Blevins
Comments:
IPMC/Shepherd notes:
Dave Fisher: They are currently looking to add committers.
Assuming that they show more community and make one or two
releases then they are close to graduation.
--------------------
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 as opposed to
"gitter"
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 released the 0.2.0-incubating release and
is currently voting the release 0.3.0-incubating.
How has the project developed since the last report?
* Regular cadence of community activity, with some increase on
mailing list activity.
* Several issues have been reported/addressed and a new
release is being voted.
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:
2018-08-15
When were the last committers or PPMC members elected?
* Ryan Blue was added to the PMC on 2017-04-03
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Signed-off-by:
[x](toree) Luciano Resende
Comments:
[ ](toree) Julien Le Dem
Comments:
[ ](toree) Ryan Blue
Comments:
IPMC/Shepherd notes:
--------------------
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. Clarify IP clearance (on-going)
2. Finalized graduation proposal draft
3. Podling graduation vote once step 1 and 2 are complete
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?
We have added a new committer and PPMC member : François Papon and we
have prepared a list of PMC members for post-graduation.
How has the project developed since the last report?
After the release of Apache Unomi 1.3.0, we are now focused on
graduation. The maturity model report has been completed, the website
has been greatly expanded to clarify community joining and
communication, and a draft of the graduation proposal is being
discussed right now.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2018-09-10
When were the last committers or PPMC members elected?
2018-09-19
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Our mentors are very helpful and responsive and are doing their best
to assist the project when asked.
Signed-off-by:
[x](unomi) Bertrand Delacretaz
Comments: I agree that Unomi is mostly ready to graduate
[X](unomi) Jean-Baptiste Onofre
Comments: I'm helping to finalize the pending actions for the
graduation.
IPMC/Shepherd notes:
--------------------
Warble
A distributed endpoint monitoring solution where the agent is hosted on your
own hardware.
Warble has been incubating since 2018-06-11.
Three most important issues to address in the move towards graduation:
1. Engage initial committers.
2. Set core design and feature set, avoid creep of new features before
the core is complete.
3. Expand committers and community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Chris Lambertus has moved from the PMC to a mentor role. This was done to
give us some redundancy in mentorship and Chris said his time would be
better spent in that role.
How has the community developed since the last report?
We've had some interest from outside people that are asking about
contributing and what they can do for the project.
How has the project developed since the last report?
With Chris' move to mentor, we've been working on solidifying the change.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
NA
When were the last committers or PPMC members elected?
NA
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
NA
Signed-off-by:
[X](warble) Chris Lambertus
Comments: Community building and documentation of the framework
continue to be the core focus of Warble.
IPMC/Shepherd notes:
--------------------
Weex
Weex is a framework for building high-performance mobile apps with modern
web development experience.
Weex has been incubating since 2016-11-30.
Three most important issues to address in the move towards graduation:
1. Propose more open discussions in the mailing list, improve the
activity.
2. Establish a regular release schedule and a clear roadmap.
3. Develop more committers and PPMCs, stay focused on the community.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
Apologize for missing the last podling report.
The main reason for it is the PPMC and committers does not pay enough
attention in the mailing list. We have realized this mistake and decide
to take more efforts on building the community.
Here are some actions:
1. Hold meetings regularly among core contributors of Weex and publish
the summary to the mailing list.
2. Take turns on duty for each release and podling reports.
How has the community developed since the last report?
* Released a new version (v0.19.0) of Weex.
https://lists.apache.org/thread.html/3e7bfe9e3f79a8d4b46dbe668bfb559e4e539
bd7c5f4143107e6af00@%3Cgeneral.incubator.apache.org%3E
* Hold a meetup in Shanghai at 2018-09-15, discussed technologies about
the new render pipeline and interactive experience of Weex.
* Migrate the source code from (git-wip-us.apache.org) to
(gitbox.apache.org) and enabled the issue panel on the GitHub.
How has the project developed since the last report?
* In average, more than 10 PRs or commits were merged to the main branch
each week. The Github repository now has 162 contributors (8 new since
the last report) and 1451 forks (130 new).
* Weex has developed a new render pipeline and used it in production, but
it still needs more improvement.
* A more CSS-friendly Weex Renderer is under discussing, it can fix many
cross-platform inconsistency problems.
How would you assess the podling's maturity? Please feel free to add your
own commentary.
[ ] Initial setup
[ ] Working towards the first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of the last release:
2018-10-08 (v0.19.0)
When were the last committers or PPMC members elected?
New PPMC member: jondong (Jonathan Dong)
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Yes, they are helpful, but we still need more active mentors.
Signed-off-by:
[X](Weex) Willem Ning Jiang
Comments: The dev mailing list has 211 subscriptions and there is a
roadmap discussion in the mailing list. We need more mentors for this
project.
IPMC/Shepherd notes:
--------------------
Zipkin
Zipkin is a distributed tracing system. It helps gather timing data needed
to troubleshoot latency problems in microservice architectures.
Zipkin has been incubating since 2018-08-29.
Three most important issues to address in the move towards graduation:
1. Finalize the migration of the GitHub repositories
2. Finalize the migration of website
3. Assess the migration to Apache CI infrastructure (Jenkins)
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The podling is presently blocked on INFRA-16989.
How has the community developed since the last report?
The workshop has been held on 29th of October, 2018.
How has the project developed since the last report?
The team started to look at Apache CI infrastructure (Jenkins) and assess
the fit to the project needs (comparing to Travis CI). The Zipkin web
site has been already migrated to Jenkins job and automatically rebuilds
in case of changes.
How would you assess the podling's maturity?
The IP rights/SGA and Git repository migration are still ongoing.
Please feel free to add your own commentary.
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
2018-09-24
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Mick was instrumental in getting us "in the nick of time" progressed on
the otherwise block on SGA. He encouraged me towards sending a message
to the secretary and escalated later which allowed a last minute progress.
Andriy helped with keeping spirit alive on dev list, review of wiki
content and also progressed our new committer Raja towards steps needed
for committership.
Signed-off-by:
[X](zipkin) Michael Semb Wever
Comments: I would have listed the blockage on migrating the code
(INFRA-16989) under "issues that the Incubator PMC (IPMC) or ASF
Board wish/need to be aware of" as even though it's moving again,
this podling has barely moved for months because of it.
[X](zipkin) John D. Ament
Comments: I agree with the issues around the code import and don't
understand how we can help them move past it. It seems that infra has
suddenly put a burden on secretary that isn't typical.
[X](zipkin) Willem Ning Jiang
Comments: As we already get iCLAs and SGA, can we move the code in to
Apache?
[X](zipkin) Andriy Redko
Comments: The project struggles for a few months now to get the SGA
approved or/and accepted
(https://issues.apache.org/jira/browse/INFRA-16989)
by Apache. This is a significant source of frustration among the PPMCs
and community in general as the any further efforts are blocked.
IPMC/Shepherd notes:
-----------------------
SensSoft
Apache SensSoft is a generalized user behavioral logging platform for web
pages and
thin-client applications
Apache SensSoft has been incubating since 2016-07-13.
Three most important issues to address in the move towards graduation:
1. Extending release process to other parts of the SensSoft software
stack.
2. Grow the Apache SensSoft (Incubating) Committer/Community Base.
3. Complete the issues highlighted at the SensSoft Roadmap
https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmaps
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
The community submitted 12 nominations for new Podling names. The names
are collected for easy reference on our confluence space [1].
JIRA tickets have been written to track progress on research on
PODLINGNAMESEARCH board [2].
How has the community developed since the last report?
The community has been:
-discussing reaching out to other open source projects to identify other
potential communities (analytical technologies) to drive developments,
as well as increase interest in the Podling.
-discussing research applications with university research labs in
machine learning and social computing.
How has the project developed since the last report?
Project maturity roadmaps (Wiki) and version release plans (JIRA)
continue to be maintained. JIRA boards continue to be maintained
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:
2018-03-14
When were the last committers or PPMC members elected?
Arthi Vezhavendan was added to PPMC and Committer base on 2017-01-24
Have your mentors been helpful and responsive or are things falling
through the cracks?
Chris Mattmann and Paul Ramirez have been removed as mentors in the last
month.
Lewis McGibbney has been extremely helpful and has actively participated
in our NAMESEARCH.
Signed-off-by:
[X](senssoft) Lewis John McGibbney
Comments:
[1]
https://cwiki.apache.org/confluence/display/SENSSOFT/PODLINGNAMESEARCH
[2]
https://issues.apache.org/jira/projects/SENSSOFT/issues/SENSSOFT-308?filter=
allopenissues
}}}
----------------------------------------------------------------------
Table of Contents
DLab
Doris
ECharts
Edgent
Heron
Livy
Marvin-AI
PageSpeed
Pinot
Ratis
S2Graph
SDAP
Tamaya
Toree
Unomi
Warble
Weex
Zipkin
Senssoft
----------------------------------------------------------------------
--------------------
DLab
DLab is a platform for creating self-service, exploratory data science
environments in the cloud using best-of-breed data science tools.
DLab has been incubating since 2018-08-20.
Three most important issues to address in the move towards graduation:
1. Execute the SGA between EPAM and the ASF so code can be imported.
2. Move bug tracking system including project backlog to Apache issue
tracking system.
3. Work toward an initial Apache release.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Nothing at this point of time.
How has the community developed since the last report?
We are not at the stage of building community so far.
How has the project developed since the last report?
Initial committers have submitted their Apache ICLA, subscribed to all
mailing lists and created Jira accounts. Functionality added:
- Administrative Web UI for roles management
- Fixed libraries installation for RStudio
- Restrict usage of EC2 instances of certain shapes to different groups
of users
- Fixed a bug on MS Azure when instance creation failed because of same
IP allocation to different instances
- Added support of Dex authentication
- Work in progress towards deployment into two VPC’s (SSN and Edge Node
into one VPC, notebooks and computational resources into separate VPC)
- Work in progress implementing Java libraries support from WebUI
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:
This is going to be our first release.
When were the last committers or PPMC members elected?
We are still operating with the set of initial committers.
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Mentors were very responsive and provided a good overview of incubation
process in general. Helped a lot providing detailed instructions on how
to get subscribed, submit ICLA application and certainly provided a
vector for next steps. The team has immediate support and can ask for
any questions.
Signed-off-by:
[X](dlab) P. Taylor Goetz
Comments: To give some context regarding the mentor question above,
I'm employed by the same company as the initial committers
and have working with them since before the proposal to
prep them for Apache.
Currently we're waiting on the SGA (I'm working on pushing it
through) which is blocking code import. Meanwhile the podling
is starting to use the mailing list and populating JIRA.
[X](dlab) Henry Saputra
Comments:
[ ](dlab) Konstantin I Boudnik
Comments:
IPMC/Shepherd notes:
--------------------
Doris
Doris is a MPP-based interactive SQL data warehousing for reporting and
analysis.
Doris has been incubating since 2018-07-18.
Three most important issues to address in the move towards graduation:
1. Move discussion to the mailing list;
2. Make our first ASF release;
3. Work on the web site.
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?
New added a contributor who contribute a feature.
How has the project developed since the last report?
Start to test the feature of streaming import and prepare to commit;
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[x] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A.
When were the last committers or PPMC members elected?
N/A.
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Yes.
Signed-off-by:
[X](doris) Dave Fisher
Comments: Still in the getting started stage ...
I did meet with Reed in person in Shenzhen.
[ ](doris) Luke Han
Comments:
[X](doris) Willem Jiang
Comments: Project team is getting used to have discussion in the
mailing list.
IPMC/Shepherd notes:
--------------------
ECharts
ECharts is a charting and data visualization library written in JavaScript.
ECharts has been incubating since 2018-01-18.
Three most important issues to address in the move towards graduation:
1. Have merged several pull request from community.
2. Received ICLA files from new contributors.
3. Preparing version 4.2.0 release.
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?
Several new contributors joined community, sending PR and helping answer
questions.
How has the project developed since the last report?
Preparing the 4.2.0 release and add some new features and fixed bugs.
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:
2018-08-04
When were the last committers or PPMC members elected?
N/A
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Yes. They helped a lot and solved many of our problems.
Signed-off-by:
[X](echarts) John D. Ament
Comments:
[ ](echarts) Kevin A. McGrail
Comments:
[X](echarts) Dave Fisher
Comments: I met with Wenli in Shenzhen.
None of the PPMC had subscribed to the private email list.
We discussed and this was corrected.
More work is coming to the dev@ list and a new release is
being Voted on.
Looking forward to more discussion on dev@.
Next report should have a better discussion about steps to
graduation.
IPMC/Shepherd notes:
--------------------
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. Re-creating a working community
2. Re-populating the PPMC
3. Replenishing the group of mentors
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
For the past months, there has been absolutely no activity in the project
Even if there has been an occasional Email from an external entity in the
last 3 months, the activity in the project has been solely me (Christofer)
writing emails without getting any form of response from the rest of the
committers, PPMCs or mentors
The main problem here is, that when being voted into the project, I had
been working on the build, but before I was able to start digging in the
code the rest of the team disappeared without me having had the chance to
do a reasonably significant amount of know-how transfer. Currently, we
have a codebase for which we have a detailed understanding of the build,
but almost none of the code itself.
How has the community developed since the last report?
* Total, we have 82 subscribers to our mailing list, an increase of 5
since the last report.
* There have been two questions asked by users and two little
discussions about these issues on the list
* Discussions started on the private list have been left unresponded
* On 19th September 2018 Christofer had a talk about Apache Edgent on
the Solutions.Hamburg TechCamp
How has the project developed since the last report?
* According to JIRA, 0 new issue were added and none were resolved in
the last 90 days
* 0 commits were made in the last 90 days.
How would you assess the podling's maturity?
After the withdrawal of most of the active committers and PPCM members
currently a new committer, PPMC and mentor-base has to be built. Being
working hard on the PLC4X podling, I am currently evaluating if I am
going to be willing and able to achieve this goal.
[ ] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
2017-12-14 Apache Edgent 1.2.0
When were the last committers or PPMC members elected?
In August 2017, we added Christofer Dutz as a new committer
and PPMC member.
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
I just double checked, but it seems our mentors are not existent
there had been one or two issues where feedback was explicitly
asked for, but both the PPMC as well as all mentors remained silent.
Except Justin mentioning the absence of mentors.
Signed-off-by:
[x](edgent) Luciano Resende
Comments:
[X](edgent) Justin Mclean
Comments:
IPMC/Shepherd notes:
Dave Fisher: If the project is to be rebooted then the PPMC needs to
be grown.
I think you might find at least one candidate from dev@ activity.
Also I noticed a JIRA - EDGENT-450 about creating an Edge
Connector for Apache Pulsar.
I've sent a note to dev@pulsar suggesting they join at dev@edgent
to help.
--------------------
Heron
A real-time, distributed, fault-tolerant stream processing engine.
Heron has been incubating since 2017-06-23.
Three most important issues to address in the move towards graduation:
1. Making the fist Apache Release. Vote for RC5 is currently on
general@incubator
2. Making several Releases
3. Continuing to grow the community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Not at this time
How has the community developed since the last report?
The community has been growing. Two more monthly meetups have been
successfully organized so far after the initial one in April 2018. We
have also seen more interests in the Heron from different channels and
getting more ideas from the community. In October 2018 there was a
presentation given at BazelCon in New York city on building Apache Heron.
How has the project developed since the last report?
There have been mainly bug fixes and improvements to existing features.
Some to note are
* Works towards Apache release and five release candidates have been
created.
* Updates for the licenses
* Updates to the documentation
* New integration tests
* New designs/works for the Streamlet API(Heron’s high level DSL)
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[X] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
No Apache releases as of yet. Latest RC was done on Oct 15th. [this might
change if our Apache release succeeds]
When were the last committers or PPMC members elected?
Ning Wang was elected a committer on accepted on 11/1/2018.
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Mentors have been very responsive and helpful.
Signed-off-by:
[ ](heron) Jake Farrell
Comments:
[ ](heron) Julien Le Dem
Comments:
[ ](heron) P. Taylor Goetz
Comments:
[X](heron) David Fisher
Comments: Heron has switched its 2x monthly offline hangout for a
twice weekly "what am I up to" on dev@heron.
IPMC/Shepherd notes:
--------------------
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:
1. Grow the community to have more activities.
2. Grow more contributors and committers.
3. Regular 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?
Activity on the dev and user mailing lists as well as the rate of reported
JIRA issues has stayed steady. There has been an uptick of development
activity around adding a new feature to the project (a Hive-compatible
Thrift server implementation).
How has the project developed since the last report?
A new feature (Hive-compatible Thrift server) is being implemented and
support is being added for Apache Spark 2.4 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:
2018-02-06
When were the last committers or PPMC members elected?
2017-09-18
Signed-off-by:
[x](livy) Bikas Saha
Comments:
[ ](livy) Brock Noland
Comments:
[x](livy) Luciano Resende
Comments:
[x](livy) Jean-Baptiste Onofre
IPMC/Shepherd notes:
--------------------
Marvin-AI
Marvin-AI is an open-source artificial intelligence (AI) platform that helps
data scientists, prototype and productionalize complex solutions with a
scalable, low-latency, language-agnostic, and standardized architecture
while simplifies the process of exploration and modeling.
Marvin-AI has been incubating since 2018-08-21.
Three most important issues to address in the move towards graduation:
1.Move development infrastructure to Apache
2.Build Community
3.Build Releases
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?
* The community has already migrated most of the infrastructure to
Apache. After weeks of discussion, the community has finally come to a
consensus on the backlog for the first Apache release.
How has the project developed since the last report?
* Code infrastructure is mostly migrated, new features are being
discussed.
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:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
* At least two of the mentors are sometimes active.
Signed-off-by:
[x](marvin-ai) Jim Jagielski
Comments: Request to submit report was sent by Luciano
[x](marvin-ai) Luciano Resende
Comments:
[ ](marvin-ai) William Colen
Comments:
IPMC/Shepherd notes:
--------------------
PageSpeed
PageSpeed represents a series of open source technologies to help
make the web faster by rewriting web pages to reduce latency and
bandwidth.
PageSpeed has been incubating since 2017-09-30.
Three most important issues to address in the move towards graduation:
1. The project needs more active developers.
2. Create a first release
3.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The number of active developers is low.
It looks like we cannot leave this up to organic growth and would like to
brainstorm on ways to engage more developers.
How has the community developed since the last report?
One new developer was proposed to be added as a committer, but nobody
voted, so the vote failed. This vote may have been initiated too early.
In terms of users the project seems to be growing slightly still, but in
terms of developers we seem to be stalled.
How has the project developed since the last report?
A docker image for Alpine support was merged, which constitutes a non-
trivial contribution.
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?
Feb 2 2018 (Huibao Lin, elected as both committer and PMC member)
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Mentors have been helpful.
Signed-off-by:
[ ](pagespeed) Jukka Zitting
Comments:
[ ](pagespeed) Leif Hedstrom
Comments:
[X](pagespeed) Nick Kew
Comments: Iterating my comment from the last report: this looks like
a healthy github project but the Apache part is less clear.
[ ](pagespeed) Phil Sorber
Comments:
IPMC/Shepherd notes:
--------------------
Pinot
Pinot is a distributed columnar storage engine that can ingest data in real-
time and serve analytical queries at low latency.
Pinot has been incubating since 2018-10-17.
Three most important issues to address in the move towards graduation:
We are just starting the incubation and don't have much to report. Few
things we are working on:
1. Migrate the code base from LinkedIn GitHub to Apache GitHub
2. Finish the initial tasks to set up the podling - website, mailing
lists, developer icla's etc
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
How has the community developed since the last report?
How has the project developed since the last report?
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:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Signed-off-by:
[x](pinot) Kishore Gopalakrishna
Comments:
[ ](pinot) Jim Jagielski
Comments: Very, very early in process.
[ ](pinot) Roman Shaposhnik
Comments:
[x](pinot) Olivier Lamy
Comments:
IPMC/Shepherd notes:
--------------------
Ratis
Ratis is a java implementation for RAFT consensus protocol
Ratis has been incubating since 2017-01-03.
Three most important issues to address in the move towards graduation:
1. Work towards a GA release.
2. Start working on graduation template.
3. Complete name search process.
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?
2 New PPMC members have been added.
3 new contributors have been added. Total 53 contributors currently.
How has the project developed since the last report?
Rapid progress being made towards stabilization for a GA release.
53 new patches committed.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[X] Working towards first GA release
[X] Community building
[X] Nearing graduation
When were the last committers or PPMC members elected?
2018-11-03
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Mentors are helpful.
Signed-off-by:
[X](ratis) Jakob Homan
Comments:
[X](ratis) Uma Maheswara Rao G
Comments: IMO, this project is doing well and going towards graduation.
[ ](ratis) Devaraj Das
Comments:
IPMC/Shepherd notes:
--------------------
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 third 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 beaware
of?
None
How has the community developed since the last report?
* In ACNA 2018, we announced S2Graph as the title of the Apache
S2Graph(incubating) with the build data management platform and audience
targeting online application system using Graph Database.
https://apachecon.dukecon.org/acna/2018/#/scheduledEvent/835a6adcab1ce83a0
* There were some questions from the community about the introduction of
S2Graph.
How has the project developed since the last report?
* We have received some inquiries from the community and created an issue
that does not solve it yet.
- 5 issues are created and 0 of them are resolved since the last
report (Sep 2018).
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-08-26
When were the last committers or PPMC members elected?
None
Signed-off-by:
[ ](s2graph) Andrew Purtell
Comments:
[ ](s2graph) Seetharam Venkatesh
Comments:
[X](s2graph) Sergio Fernández
Comments: Incubating for three years;
we may need to discuss the
podling future sooner than
later.
IPMC/Shepherd notes:
--------------------
SDAP
SDAP is an integrated data analytic center for Big Science problems.
SDAP has been incubating since 2017-10-22.
Three most important issues to address in the move towards graduation:
1. Make formal SDAP (Incubating) Release
2. Improve/create user guide documentation
3. Grow Community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
None
How has the community developed since the last report?
Added 2 new developers that are becoming familiar with the project and
will soon become committers.
SDAP has been heavily advertised at/in many Earth Science technology
forums.
SDAP was featured at the CUAHSI Biennial Colloquium with an aim towards
growing the community.
How has the project developed since the last report?
Development is still underway to push towards the first incubating
release of SDAP and each of its subcomponents.
How would you assess the podling's maturity?
Podling's still getting established.
[] Initial setup
[X] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Kevin M Gill was elected on 2018-03-05
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
As mentors, we have not been very actively involved - but there's nothing ye
t that required the mentor's attention (the project is in good hands under L
ewis :-)).
Mentors are available nevertheless to help with releases and guiding the pod
ling.
Signed-off-by:
[X](sdap) Jörn Kottmann
Comments:
[X](sdap) Suneel Marthi
Comments:
IPMC/Shepherd notes:
--------------------
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. Grow the PPMC from the existing community.
2. Make another Release
3. Blog about Tamaya
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
* We'd like to graduate soon and plan some reworks to access a broader
audience and collect new contributors/people interested in the project.
How has the community developed since the last report?
* frequent bugreports and discussions via Jira/mailing list
* new external contributions
How has the community developed since the last report?
* frequent bugreports and discussions via Jira/mailing list
* new external contributions
How has the project developed since the last report?
* Bugfixes, changes, discussions going on
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
Date of last release:
2017-05-28 0.3-incubating
When were the last committers or PPMC members elected?
* P. Ottlinger at 2016-04-24.
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
* John is and was the onliest active mentor and answers questions or gives
hints for quite a while.
* As the project needs a wider audience, maybe mentors with interest in Ta
maya would be welcome.
Signed-off-by:
[X](tamaya) John D. Ament
Comments: The podling hasn't executed a release in over a year, has
limited on list discussions. I would be cautious about graduating,
considering how small the community is.
[ ](tamaya) David Blevins
Comments:
IPMC/Shepherd notes:
Dave Fisher: They are currently looking to add committers.
Assuming that they show more community and make one or two
releases then they are close to graduation.
--------------------
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 as opposed to
"gitter"
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 released the 0.2.0-incubating release and
is currently voting the release 0.3.0-incubating.
How has the project developed since the last report?
* Regular cadence of community activity, with some increase on
mailing list activity.
* Several issues have been reported/addressed and a new
release is being voted.
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:
2018-08-15
When were the last committers or PPMC members elected?
* Ryan Blue was added to the PMC on 2017-04-03
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Signed-off-by:
[x](toree) Luciano Resende
Comments:
[ ](toree) Julien Le Dem
Comments:
[ ](toree) Ryan Blue
Comments:
IPMC/Shepherd notes:
--------------------
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. Clarify IP clearance (on-going)
2. Finalized graduation proposal draft
3. Podling graduation vote once step 1 and 2 are complete
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?
We have added a new committer and PPMC member : François Papon and we
have prepared a list of PMC members for post-graduation.
How has the project developed since the last report?
After the release of Apache Unomi 1.3.0, we are now focused on
graduation. The maturity model report has been completed, the website
has been greatly expanded to clarify community joining and
communication, and a draft of the graduation proposal is being
discussed right now.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[ ] Initial setup
[ ] Working towards first release
[ ] Community building
[X] Nearing graduation
[ ] Other:
Date of last release:
2018-09-10
When were the last committers or PPMC members elected?
2018-09-19
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Our mentors are very helpful and responsive and are doing their best
to assist the project when asked.
Signed-off-by:
[x](unomi) Bertrand Delacretaz
Comments: I agree that Unomi is mostly ready to graduate
[X](unomi) Jean-Baptiste Onofre
Comments: I'm helping to finalize the pending actions for the
graduation.
IPMC/Shepherd notes:
--------------------
Warble
A distributed endpoint monitoring solution where the agent is hosted on your
own hardware.
Warble has been incubating since 2018-06-11.
Three most important issues to address in the move towards graduation:
1. Engage initial committers.
2. Set core design and feature set, avoid creep of new features before
the core is complete.
3. Expand committers and community
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
Chris Lambertus has moved from the PMC to a mentor role. This was done to
give us some redundancy in mentorship and Chris said his time would be
better spent in that role.
How has the community developed since the last report?
We've had some interest from outside people that are asking about
contributing and what they can do for the project.
How has the project developed since the last report?
With Chris' move to mentor, we've been working on solidifying the change.
How would you assess the podling's maturity?
Please feel free to add your own commentary.
[X] Initial setup
[ ] Working towards first release
[X] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
NA
When were the last committers or PPMC members elected?
NA
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
NA
Signed-off-by:
[X](warble) Chris Lambertus
Comments: Community building and documentation of the framework
continue to be the core focus of Warble.
IPMC/Shepherd notes:
--------------------
Weex
Weex is a framework for building high-performance mobile apps with modern
web development experience.
Weex has been incubating since 2016-11-30.
Three most important issues to address in the move towards graduation:
1. Propose more open discussions in the mailing list, improve the
activity.
2. Establish a regular release schedule and a clear roadmap.
3. Develop more committers and PPMCs, stay focused on the community.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
Apologize for missing the last podling report.
The main reason for it is the PPMC and committers does not pay enough
attention in the mailing list. We have realized this mistake and decide
to take more efforts on building the community.
Here are some actions:
1. Hold meetings regularly among core contributors of Weex and publish
the summary to the mailing list.
2. Take turns on duty for each release and podling reports.
How has the community developed since the last report?
* Released a new version (v0.19.0) of Weex.
https://lists.apache.org/thread.html/3e7bfe9e3f79a8d4b46dbe668bfb559e4e539
bd7c5f4143107e6af00@%3Cgeneral.incubator.apache.org%3E
* Hold a meetup in Shanghai at 2018-09-15, discussed technologies about
the new render pipeline and interactive experience of Weex.
* Migrate the source code from (git-wip-us.apache.org) to
(gitbox.apache.org) and enabled the issue panel on the GitHub.
How has the project developed since the last report?
* In average, more than 10 PRs or commits were merged to the main branch
each week. The Github repository now has 162 contributors (8 new since
the last report) and 1451 forks (130 new).
* Weex has developed a new render pipeline and used it in production, but
it still needs more improvement.
* A more CSS-friendly Weex Renderer is under discussing, it can fix many
cross-platform inconsistency problems.
How would you assess the podling's maturity? Please feel free to add your
own commentary.
[ ] Initial setup
[ ] Working towards the first release
[x] Community building
[ ] Nearing graduation
[ ] Other:
Date of the last release:
2018-10-08 (v0.19.0)
When were the last committers or PPMC members elected?
New PPMC member: jondong (Jonathan Dong)
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Yes, they are helpful, but we still need more active mentors.
Signed-off-by:
[X](Weex) Willem Ning Jiang
Comments: The dev mailing list has 211 subscriptions and there is a
roadmap discussion in the mailing list. We need more mentors for this
project.
IPMC/Shepherd notes:
--------------------
Zipkin
Zipkin is a distributed tracing system. It helps gather timing data needed
to troubleshoot latency problems in microservice architectures.
Zipkin has been incubating since 2018-08-29.
Three most important issues to address in the move towards graduation:
1. Finalize the migration of the GitHub repositories
2. Finalize the migration of website
3. Assess the migration to Apache CI infrastructure (Jenkins)
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
The podling is presently blocked on INFRA-16989.
How has the community developed since the last report?
The workshop has been held on 29th of October, 2018.
How has the project developed since the last report?
The team started to look at Apache CI infrastructure (Jenkins) and assess
the fit to the project needs (comparing to Travis CI). The Zipkin web
site has been already migrated to Jenkins job and automatically rebuilds
in case of changes.
How would you assess the podling's maturity?
The IP rights/SGA and Git repository migration are still ongoing.
Please feel free to add your own commentary.
[X] Initial setup
[ ] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
N/A
When were the last committers or PPMC members elected?
2018-09-24
Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.
Mick was instrumental in getting us "in the nick of time" progressed on
the otherwise block on SGA. He encouraged me towards sending a message
to the secretary and escalated later which allowed a last minute progress.
Andriy helped with keeping spirit alive on dev list, review of wiki
content and also progressed our new committer Raja towards steps needed
for committership.
Signed-off-by:
[X](zipkin) Michael Semb Wever
Comments: I would have listed the blockage on migrating the code
(INFRA-16989) under "issues that the Incubator PMC (IPMC) or ASF
Board wish/need to be aware of" as even though it's moving again,
this podling has barely moved for months because of it.
[X](zipkin) John D. Ament
Comments: I agree with the issues around the code import and don't
understand how we can help them move past it. It seems that infra has
suddenly put a burden on secretary that isn't typical.
[X](zipkin) Willem Ning Jiang
Comments: As we already get iCLAs and SGA, can we move the code in to
Apache?
[X](zipkin) Andriy Redko
Comments: The project struggles for a few months now to get the SGA
approved or/and accepted
(https://issues.apache.org/jira/browse/INFRA-16989)
by Apache. This is a significant source of frustration among the PPMCs
and community in general as the any further efforts are blocked.
IPMC/Shepherd notes:
-----------------------
SensSoft
Apache SensSoft is a generalized user behavioral logging platform for web
pages and
thin-client applications
Apache SensSoft has been incubating since 2016-07-13.
Three most important issues to address in the move towards graduation:
1. Extending release process to other parts of the SensSoft software
stack.
2. Grow the Apache SensSoft (Incubating) Committer/Community Base.
3. Complete the issues highlighted at the SensSoft Roadmap
https://cwiki.apache.org/confluence/display/SENSSOFT/Roadmaps
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
The community submitted 12 nominations for new Podling names. The names
are collected for easy reference on our confluence space [1].
JIRA tickets have been written to track progress on research on
PODLINGNAMESEARCH board [2].
How has the community developed since the last report?
The community has been:
-discussing reaching out to other open source projects to identify other
potential communities (analytical technologies) to drive developments,
as well as increase interest in the Podling.
-discussing research applications with university research labs in
machine learning and social computing.
How has the project developed since the last report?
Project maturity roadmaps (Wiki) and version release plans (JIRA)
continue to be maintained. JIRA boards continue to be maintained
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:
2018-03-14
When were the last committers or PPMC members elected?
Arthi Vezhavendan was added to PPMC and Committer base on 2017-01-24
Have your mentors been helpful and responsive or are things falling
through the cracks?
Chris Mattmann and Paul Ramirez have been removed as mentors in the last
month.
Lewis McGibbney has been extremely helpful and has actively participated
in our NAMESEARCH.
Signed-off-by:
[X](senssoft) Lewis John McGibbney
Comments:
[1]
https://cwiki.apache.org/confluence/display/SENSSOFT/PODLINGNAMESEARCH
[2]
https://issues.apache.org/jira/projects/SENSSOFT/issues/SENSSOFT-308?filter=
allopenissues
}}}
-----------------------------------------
Attachment AF: Report from the Apache jUDDI Project [Alex O'Ree]
## Description:
- 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).
## Issues:
- There are no issues that require the board's attention at this time.
## Activity:
- jUDDI - last release was 22 NOV 2017. Some development has taken place
since then related maintenance and updating dependencies.
## Health report:
- 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 issues raised since the last
report.
## PMC changes:
- Currently 7 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Alex O'Ree on Sun Mar 17 2013
## Committer base changes:
- Currently 7 committers.
- No new changes to the committer base since last report.
## Releases:
- Last release was 3.3.5 on Wed Nov 22 2017
## /dist/ errors: 14
- These errors are for older versions of jUDDI in which a former PMC's gpg
key expired. The key has been refreshed however the previous releases will
probably not be resigned.
## Mailing list activity:
- dev@juddi.apache.org:
- 69 subscribers (down -1 in the last 3 months):
- 28 emails sent to list (5 in previous quarter)
- user@juddi.apache.org:
- 110 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (4 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AG: Report from the Apache Juneau Project [James Bognar]
## Description:
- Juneau is a cohesive Java ecosystem consisting of POJO serializers and REST
client and server APIs.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Two releases in the past 2 months.
- Currently working towards another minor release (7.2.2) and major release
(8.0.0).
## Health report:
- Project usage has been steady and consistent, but interest in committers
joining the project has been low. Non-PMC code contributions have recently
picked up though.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Craig L Russell on Tue Oct 17 2017
- Last Committer addition was Craig L Russell on Tue Oct 17 2017
## Committer base changes:
- Currently 9 committers.
- No new changes to the committer base since last report.
## Releases:
- 7.2.0 was released on Sun Sep 16 2018
- 7.2.1 was released on Mon Oct 22 2018
## Mailing list activity:
- Activity has picked up since the last quarter.
- dev@juneau.apache.org:
- 23 subscribers (up 0 in the last 3 months):
- 192 emails sent to list (30 in previous quarter)
-----------------------------------------
Attachment AH: 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 are voting on the next major release 2.1.0. This release includes 28 new KIPs
and features such as Java 11 support, Zstandard support, more intuitive user
timeouts in the producer, better fencing for replication, various Streams API
improvements and the admin client improvements.
We released 2.0.1, which fixes 49 issues.
Community
===========
Lots of activities in the mailing list. We have 2767 subscribers in the user
mailing list, up 28 in the last 3 months. We have 864 emails in the user
mailing list in the last 3 months, a bit less than the 953 in the previous
cycle. We have 1259 subscribers in the dev mailing list, up 45 in the last 3
months. We have 2972 emails in the dev mailing list in the last 3 months, a bit
more than the 2878 in the previous cycle.
We elected two new committers, Colin McCabe on Sep 29, 2018 and Manikumar Reddy
on Oct 11, 2018. We elected one new PMC member Dong Lin on Aug. 4, 2018.
Kafka Summit in San Francisco completed with more than 1200 attendees.
We published the very first Kafka blog in Apache
(https://blogs.apache.org/kafka/entry/apache-kafka-supports-more-partitions).
Releases
===========
2.0.1 was released on Nov. 9, 2018.
1.1.1 was released on Jul. 20, 2018.
-----------------------------------------
Attachment AI: Report from the Apache Kibble Project [Rich Bowen]
Apache Kibble is a suite of tools for collecting, aggregating and visualizing
activity in software projects. http://kibble.apache.org/
## Issues:
There are no issues requiring board attention at this time.
## Activity and health
We had another quiet quarter. There was some discussion of participating in
the upcoming CHAOSS summit at FOSDEM, and a handful of commits.
Some off-list conversations were had at various events, including Open Source
Summit in Edinburgh, with individuals who expressed interest in the project.
These have not translated into actual project engagement.
It is concerning that *ALL* commits in this quarter (indeed, much longer than
that) have been from one person. This is, obviously, not the hallmark of a
sustainable project.
## PMC/Committer changes:
Currently 12 committers and 12 PMC members.
No new PMC members in the last 3 months.
Last PMC addition: Sat Dec 09 2017 (Rafael Weingärtner)
No new committers in the last 3 months.
Last committer addition: Sat Dec 09 2017 (Rafael Weingärtner)
## Releases:
We have not yet made a release.
## Mailing list activity:
Another quiet month on all of our mailing lists. We hope that discussions at
FOSDEM will once again spark some interest, and new contributors.
-----------------------------------------
Attachment AJ: 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 pending 1.2.0 release has evolved from a shorter interval release and
cloud oriented scope to be a longer cycle more focused on bugs and dependency
upgrades.
- 1.2.0 release is in the process of close down and we will have an RC in a day
or two with the release following shortly.
- Cloud usecases have been postponed to the next release with a number of the
issues to be addressed in 1.2.0 being required.
## Health report:
- activity on the email lists, JIRAs and commits appear to continue to grow
and seem rather healthy. Community Health Score 6.33
## PMC changes:
- Currently 17 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Kevin Risden on Mon Apr 02 2018
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Kevin Risden at Tue Apr 03 2018
## Releases:
- Last release was 1.1.0 on Sun Jul 29 2018
## Mailing list activity:
- The pending 1.2.0 release has closed over 198 issues with many
dependency upgrades and minor bug fixes this and general discussion
traffic accounts for the increase. There may also be an artificial inflation due
to jenkins job failures.
- dev@knox.apache.org:
- 95 subscribers (up 0 in the last 3 months):
- 2344 emails sent to list (985 in previous quarter)
- user@knox.apache.org:
- 131 subscribers (up 2 in the last 3 months):
- 169 emails sent to list (212 in previous quarter)
## JIRA activity:
- 179 JIRA tickets created in the last 3 months
- 198 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AK: 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:
- 2018/11/23 Dong Li will present Apache Kylin latest updates
on GITC 2018 at Beijing
- 2018/11/15 Luke Han presented Apache Kylin and Use Cases
on Big Data Spian at Madrid
- 2018/11/14 Shaofeng Shi presented Apache Kylin on The 17th
North East Asia OSS Promotion Forum at Yokohama
- 2018/11/04 Shaofeng Shi presented Kylin on Datafun BigData
Meetup at Shanghai
- 2018/10/26 Billy Liu presented Apache Kylin on Cloud at
Microsoft Tech Summit at Shanghai
- 2018/10/26 Apache Kylin Meetup @Hangzhou
- 2018/10/20 Dong Li presented Apache Kylin on COSCon 2018
at Shenzhen
- 2018/09/12 Zhi Zhu and Luke Han presented Kylin use cases
on Strata Data Conference at New York
- 2018/8/29 CDAP in Cloud, Extreme OLAP w Apache Kylin, Twitter
Reviews & DataStax @ Google Cloud at Bay Area
- 2018/08/17 Shaofeng Shi presented Apache Kylin on HBaseCon Asia 2018
at
- 2018/8/11 Apache Kylin Meetup @Beijing
## PMC changes:
- Currently 20 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Zhong Yanghong on Thu Aug 02 2018
## Committer base changes:
- Currently 33 committers.
- Gang Ma was added as a committer on Fri Oct 12 2018
## Releases:
- 2.4.1 was released on Sun Sep 09 2018
- 2.5.0 was released on Tue Sep 18 2018
- 2.5.1 was released on Tue Nov 06 2018
## Mailing list activity:
- The dev and user mailing lists are showing more active
in last 3 months, almost double emails to dev list and 3 times
in user list
- dev@kylin.apache.org:
- 447 subscribers (up 25 in the last 3 months):
- 1087 emails sent to list (633 in previous quarter)
- issues@kylin.apache.org:
- 92 subscribers (down -2 in the last 3 months):
- 2606 emails sent to list (1561 in previous quarter)
- user@kylin.apache.org:
- 395 subscribers (up 41 in the last 3 months):
- 443 emails sent to list (141 in previous quarter)
## JIRA activity:
- 190 JIRA tickets created in the last 3 months
- 188 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AL: 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:
Some improvements done to code base for showing total session counts per
user, start and end times to cubes, support for querying partition columns.
Bug fixes on authorization code flow to make authorizer singleton and
to pick session config.
## 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 23 committers.
- No new committers added in the last 3 months
- Last committer addition was Rajitha R at Fri Feb 09 2018
## Releases:
- Last release was 2.7 on Tue Feb 06 2018
## JIRA activity:
- 13 JIRA tickets created in the last 3 months
- 6 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AM: 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:
Committer activity has dropped over the last couple of months, but we are
still receiving a good amount of activity and contributions from various
users.
Most of those are "drive by one time" contributions, but we will still
look and see if we can recruit any of those contributors as team members.
## PMC changes:
- Currently 14 PMC members.
- Quentin Pradet was added to the PMC on Mon May 14 2018
## Committer base changes:
- Currently 21 committers.
- Rick van de Loo was added as a committer on Tue Jun 26 2018
## Releases:
- 2.4.0 was released on Thu Nov 08 2018
- 2.3.0 was released on March 03, 2018
- 2.2.1 was released on September 21, 2017
-----------------------------------------
Attachment AN: Report from the Apache Logging Services Project [Matt Sicker]
## Description:
- The Apache Logging Services Project creates and maintains open-source
software related to the logging of application behavior and released at no
charge to the public.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Log4j Audit has gained interest in the community, attracting some new
contributors.
- There is an ongoing release candidate for Log4j Kotlin API 1.0.0.
- Log4j 3 has started being discussed in more detail on the dev list, while
general bugfixing has been going on.
- Log4cxx has been gaining activity lately with outside contributions.
- Small activity in Log4net.
- /dist/ cleanups to update expired signatures and add stronger checksums.
## Health report:
- The Log4j-related components remain active and healthy. Mailing list
activity remains about the same as last quarter. However, log4net, log4cxx,
and log4php are all seeing rather limited activity nowadays. We'll be
continuing to discuss the future of these components.
## PMC changes:
- Currently 14 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Carter Kozak on Sun Jul 29 2018
## Committer base changes:
- Currently 33 committers.
- No new committers added in the last 3 months
- Last committer addition was Carter Kozak at Wed Mar 28 2018
## Releases:
- Last release was LOGJ-2.11.1 on Sun Jul 22 2018
-----------------------------------------
Attachment AO: Report from the Apache Lucene.Net Project [Shad Storhaug]
-----------------------------------------
Attachment AP: 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.11.0 release on
September 30, 2018. The next major release is scheduled for December 31,
2018.
Committers and PMC membership
=============================
We nominated and approved Markus Schuch as a PMC member on 12/29/2017. We did
not sign up any new committers this quarter. We continue to be on the lookout
for new PMC members and committers. There are several candidates at this time
but we have not yet held a vote for committership.
Mailing list activity
=====================
Mailing list activity has been very active this quarter. Much of the
communication has been related to support and installation debugging.
Development has involved numerous enhancement requests, and work integrating
updates to Tika and SolrJ. Our release had to be delayed to synch with
Tika's, and SolrJ was particularly challenging this time because changes there
broke long-standing capabilities we had relied upon. The SolrJ team has now
begun a healthy discussion about how to officially support the ManifoldCF use
case going forward.
Issues reported have been centered mainly on bugs and on GSOC students this
quarter. I am unaware of any mailing list question that has gone unanswered.
Outstanding issues
==================
No outstanding infrastructure issues are known at this time.
-----------------------------------------
Attachment AQ: Report from the Apache Marmotta Project [Jakob Frank]
## Description:
Apache Marmotta, an Open Platform for Linked Data. Apache Marmotta was founded
in December 2012, and has graduated from the Incubator in November 2013.
## Issues:
There are no major issues requiring board attention at this time.
## Activity:
Two very quiet months since the last report, development- and mailing-list-
activities are close to off.
## Health report:
The project was considered feature-complete since 3.3.0 and has recently
published version 3.4.0. Currently there are no active development activities.
## PMC changes:
- Currently 11 PMC members.
- Last PMC addition was Mark A. Matienzo on Thu Aug 18 2016
## Committer base changes:
- Currently 13 committers.
- Xavier Sumba was added as a committer on Mon Mar 27 2017
## Releases:
- Last release was 3.4.0 on Tue Jun 12 2018
## Mailing list activity:
- users@marmotta.apache.org:
- 116 subscribers (up 0 since last report):
- 1 emails sent to list (1 in previous report)
- dev@marmotta.apache.org:
- 96 subscribers (down 1 since last report):
- 14 emails sent to list (98 in previous report)
## JIRA activity:
- 0 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AR: 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:
- A minor bugfix release (5.1.1) has been made since last time.
- There has been a small increase in reported issues and activity in JIRA
## Health report:
- As reported last time, the project is not very busy, but also not in
a particular bad state. Going slow but steady.
## 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 13 committers.
- No new committers added in the last 3 months
- Last committer addition was Jörg Unbehauen at Thu May 03 2018
## Releases:
- 5.1.1 was released on Wed Oct 03 2018
## JIRA activity:
- 14 JIRA tickets created in the last 3 months
- 6 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AS: Report from the Apache Olingo Project [Christian Amend]
## Description:
- Apache Olingo is a Java and JavaScript library that implements the Open
Data Protocol (OData). Apache Olingo serves client and server aspects of
OData. It currently supports OData 2.0 and OData 4.0. The latter is
the OASIS version of the protocol: OASIS Open Data Protocol (OData) TC.
## Activity:
- After announcement of resignment of Christian Amend as VP of Olingo
Michael Bolz has volunteered as VP. As there were on objections
the correspondig vote was done on the private Olingo mailing list
with the result of five +1 votings and no -1 voting. Based on this
vote the resolution to change the chair of a project
was sent to Apache Board
## Health report:
- The Olingo project is still healthy and has no issues that require board
involvement (beside already mentioned activity ).
- The V4 code line is on steady development also reflected in related
discussions on mailing list and new created JIRA items
- The V2 code line has no new contributions but open and new
created JIRA items
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Ramesh Reddy on Thu Oct 08 2015
## Committer base changes:
- Currently 25 committers.
- No new committers added in the last 3 months
- Last committer addition was Archana Rai at Fri May 26 2017
## Releases:
- 4.5.0 was released on Mon Aug 13 2018
## Mailing list activity:
- dev@olingo.apache.org:
- 88 subscribers (up 0 in the last 3 months):
- 173 emails sent to list (91 in previous quarter)
- user@olingo.apache.org:
- 202 subscribers (up 3 in the last 3 months):
- 12 emails sent to list (13 in previous quarter)
## JIRA activity:
- 32 JIRA tickets created in the last 3 months
- 13 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AT: Report from the Apache Oozie Project [Gézapeti]
## Description:
- Oozie is a workflow scheduler system to manage Apache Hadoop jobs.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- New action type (Git action was committed)
- We've converted our documentation to Markdown to make it easier to
contribute to it
- 5.1.0 release rc0 is on vote
- ongoing effort to keep junit tests stable, the pre-commit hook and upgrading
dependencies
## Health report:
- The project is healthy with development in multiple areas ( Python CLI, new
Spark action)
- Activity is slightly down on mailing lists and on the Jira as well.
## PMC changes:
- Currently 21 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andras Piros on Thu Jun 21 2018
## Committer base changes:
- Currently 25 committers.
- Kinga Marton was added as a committer on Sat Nov 10 2018
## Releases:
- Last release was 5.0.0 on Thu Apr 05 2018
## JIRA activity:
- 57 JIRA tickets created in the last 3 months
- 50 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment AU: Report from the Apache Open Climate Workbench Project [Michael James Joyce]
-----------------------------------------
Attachment AV: Report from the Apache Perl Project [Philippe Chiasson]
--- mod_perl --
No new mod_perl 2.x releases since 2016-10.
-- Activity --
Another report similar to the last few, and late as well. I'd like to provide
a great explanation as to the reason for this, but I have a somewhat difficult
time to find one. It's honestly somewhat difficult for me to keep up with a
project that is quiet like we've been for a while now.
I believe the board has rasons to be concerned about the health of this
project, but I am not sure what a good plan going forward could be.
It's not that the project is dead, in my opinion, more like dormant. It works,
it's being used by a large number of users, and is extremely stable.
The current development resources towards new features is pretty low, however,
that's for certain. I, for one, don't really do much more than keep an eye on
the mailing-lists for troubling bug reports, but otherwise, that's about it.
Regarding the active PMC members, I don't want to talk for anybody, but I
suspect the situation is similar all around. The product/project just works
and there are opportunities for new feature development, but there doesn't
seem to much push for that either.
I am not sure what could be done at the moment to change that state of
affairs, really, short of having a sudden infusion of interest and development
cycles.
-- 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 AW: Report from the Apache Phoenix Project [Josh Elser]
## Description:
- Apache Phoenix enables SQL-based OLTP and operational analytics for Apache
Hadoop
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- One release since last report: 4.14.1. The release was approved by the PMC
and is in the process of being released today (2018/11/14)
- Lars H. (PMC) organized a Phoenix Meetup for 2018/11/14 in San Francisco,
CA to be a general community-driven discussion. Notes will be taken and
posted to the dev-list for those unable to join physically and remotely.
- We've not added any new committers or PMC, but do have on-going discussions
as to who we want to invite for each. These threads need to be bump'ed.
## Health report:
- Activity remains relatively flat. Contributions and user-interactions
remain relatively consistent.
## PMC changes:
- Currently 27 PMC members.
- New PMC members:
- Pedro Boado was added to the PMC on Thu Jun 07 2018
- Vincent Poon was added to the PMC on Thu Jun 07 2018
## Committer base changes:
- Currently 36 committers.
- Ohad Shaham was added as a committer on Fri Jun 08 2018
## Releases:
- 4.14.1 was released on 2018/11/14
- 5.0.0 was released on Sat Jul 14 2018
## Mailing list activity:
- Activity is largely in-line with history. No significant changes to trends
to be identified.
-----------------------------------------
Attachment AX: 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
The Apache POI PMC also handles bugfixes for the XMLBeans project: XMLBeans
is a tool that allows you to map XML files to generated Java classes via
XML Schema definitions.
## XMLBeans update plans
- As the main reason for bringing XMLBeans back from the attic was to get rid
of some hurdles when using it in Apache POI, our focus for XMLBeans will be
on bugfixes and updating technology support, e.g. security fixes, newer
version of Java and other dependencies.
Apache POI will remain our main focus for new development work, while
XMLBeans is for us mostly in "bugfix-mode" as a large amount of Apache POI
code depends on XMLBeans..
We will continue to refine how we present this on xmlbeans.apache.org so
that other users of XMLBeans know what to expect.
For mailing lists we redirect questions to the Apache POI users/dev lists.
For issues we continue to use the issues.apache.org project for XMLBEANS
and Bugzilla for Apache POI.
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- We finally released Apache POI 4.0.0, which was received quite well
considering the amount of changes and refactorings that went into that
release.
A few smaller regressions were found, a follow-up fix-release 4.0.1 should
be available soon.
Also XMLBeans 3.0.1 and 3.0.2 were released, both with a small amount of
changes, mostly XML parsing/security related fixes.
We continue to update the XMLBeans homepage to reflect the new
maintainership via the Apache POI PMC.
Java 11 is supported in latest trunk, the changes will be released in the
upcoming version 4.0.1.
One new Committer/PMC member was voted in, but did not follow up on the
invitation yet.
## Health report:
- There was some discussion of bug reports/features via bugzilla and a number
of requests which indicate that the popularity of Apache POI is still very
good. Questions via email or on Stackoverflow usually get answers quickly.
Bug influx was moderate this quarter, however also bug-fix rate is not very
high, probably most "easy wins" are already resolved now and thus mostly
hard to fix bug-repports remain.
Bug influx for XMLBeans is very low because it is a stable project in
maintenance-mode and was re-activated only a short while ago.
## PMC changes:
- Currently 30 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Alain Béarez on Tue Nov 21 2017
## Committer base changes:
- Currently 37 committers.
- No new committers added in the last 3 months
- Last committer addition was Alain Béarez at Mon Nov 20 2017
## Releases:
- 4.0.0 was released on Wed Sep 05 2018
- XMLBeans-3.0.1 was released on Fri Aug 24 2018
- XMLBeans-3.0.2 was released on Sun Oct 28 2018
## Mailing list activity:
- Some subscribers left, probably because Apache POI is a stable project with
a more or less constant user-base
- dev@poi.apache.org:
- 223 subscribers (down -8 in the last 3 months):
- 698 emails sent to list (445 in previous quarter)
- general@poi.apache.org:
- 123 subscribers (down -1 in the last 3 months):
- 3 emails sent to list (6 in previous quarter)
- user@poi.apache.org:
- 583 subscribers (down -8 in the last 3 months):
- 159 emails sent to list (93 in previous quarter)
## Bugzilla Statistics:
### Apache POI
- 62 Bugzilla tickets created in the last 3 months
- 47 Bugzilla tickets resolved in the last 3 months
- 535 bugs are open overall (+23)
- Having 139 enhancements (+2)
- Thus having 396 actual bugs (+21)
- 94 of these are waiting for feedback (-4)
- Thus having 302 actual workable bugs (+25)
- 5 of the workable bugs have patches available (+-0)
- Distribution of workable bugs across components: {HSSF=80, XSSF=75, SS
Common=45, HWPF=38, XWPF=20, SXSSF=15, POI Overall=7, XSLF=6, HPSF=4,
POIFS=4, OPC=3, HSLF=2, HPBF=1, HSMF=1, SL Common=1}
### Apache XMLBeans
- 176 open issues (-6)
- Bug 130
- Improvement 22
- New Feature 19
- Wish 5
-----------------------------------------
Attachment AY: Report from the Apache Polygene Project [Jiri Jetmar]
-----------------------------------------
Attachment AZ: Report from the Apache Pulsar Project [Matteo Merli]
## Description:
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.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- The project has graduated as TLP on Sep. 19th.
- 1st Pulsar meetup in Beijing on Oct 20th was very well attended
- Community has released Apache Pulsar 2.2.0. This has been the first
release after graduation. Biggest features for this release are :
* Pulsar Java Client Interceptors
* Integration of functions and io with schema registry
* Dead Letter Topic
* Apache Flink Source connector
* JDBC Sink Connector
* HDFS Sink Connector
* Google Cloud Storage Offloader
- Work is ongoing for next release (2.3.0) for which we plan to include:
* Apache BookKeeper 4.9.0
* Schema support for C++ and Python
* Token based authentication
## Health report:
- There is healthy grow in the community
- Activity on the Slack channel is still high, many first time users come to
ask questions while getting started. There are 92 weekly active users on
the channel.
- Several new developers have joined the community providing new feature
proposals that were discussed with the community and finally contributed
to the project. We plan to start discussion on committer/PMC pipeline
soon.
## PMC changes:
- Currently 23 PMC members
- No new PMC added in the last month -- All existing PPMC member have joined
the PMC
## Committer base changes:
- Currently 23 committers
- No new committers added in the last month
## Releases:
- 2.2.0 was released on Oct. 24th
## Mailing list activity:
- Activity on the mailing lists remains high with a mixture of new users,
contributors, and deeper more experienced users and contributors sparking
discussion and questions and filing bugs or new features.
- users@pulsar.apache.org:
- 79 subscribers (+16 from Oct 2018) - 35 emails sent to list in Oct (30
in Sep)
- dev@pulsar.apache.org:
- 75 subscribers (+6 from Oct 2018) - 99 emails sent to list in Sep (193
in Sep)
## GitHub activity:
- 131 PR from 26 contributors were merged in the last 1 month
- 60 Issues were created and 45 closed in the last 1 month
-----------------------------------------
Attachment BA: Report from the Apache Qpid Project [Robert 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, C++, Go, Java/JMS, Python, and Ruby.
# Releases:
- Qpid Dispatch 1.3.0 was released on 10th August 2018.
- Qpid Proton-J 0.29.0 was released on 14th August 2018.
- Qpid JMS AMQP 0-x 6.3.3 was released on 17th August 2018.
- Qpid JMS 0.36.0 was released on 20th August 2018.
- Qpid Interop Test 0.2.0 was released on 24th August 2018.
- Qpid for Java 6.1.7 was released on 31st August 2018.
- Qpid Proton 0.25.0 was released on 6th September 2018.
- Qpid JMS 0.37.0 was released on 2nd October 2018.
- Qpid Proton 0.26.0 was released on 8th October 2018.
- Qpid Dispatch 1.4.0 was released on 15th October 2018.
- Qpid CPP 1.39.0 was released on 26th October 2018.
- Qpid Dispatch 1.4.1 was released on 30th October 2018.
- Qpid Proton-J 0.30.0 was released on 9th November 2018 [1].
[1] Proton-J 0.30.0 addressed CVE-2018-17187.
# 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.
- There were no new committer additions in this quarter, though a vote was
taken/passed to offer Roddie Kieley commit rights, with the invite process
under way as of November 13th 2018.
The most recent new committer is Chris Richardson, added on 15th Nov 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:
- The AMQP 1.0 JMS client had its 0.36.0+0.37.0 releases with various bug
fixes and performance improvements. A 0.38.0 candidate with more is
currently under vote, and work continues on more of the same.
- Work on Qpid Dispatch continues toward 1.5.0, including various bug fixes,
improvements, and new features such as work on an 'edge' router mode.
- Proton-C and its language bindings had their 0.25.0 and 0.26.0 releases,
incorporating various bug fixes and improvements. More have been made
since and the 0.27.0 release is expected later this month.
- Proton-J saw 0.29.0 and 0.30.0 releases to incorporate various bug fixes
and improvements, and work continues on more as appropriate to support
dependent client/broker/other components.
- Work continues on Qpid Broker-J 7.1.0, adding various improvements to the
7.0.x base and refining the test suite following the AMQP 0-x JMS client
being made independent. Bug fixes continue to be backported to the 7.0.x
and 6.x lines for intermediate releases as needed.
# Issues:
There are no Board-level issues at this time.
-----------------------------------------
Attachment BB: 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:
- A new .Net bridge for Drivers implemented in C#
- YARN allocation ID in Hadoop 2.9.1 to keep to track of allocated containers
## 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.
- It’s been long time since we made the last release.
We plan to make a release right after a new C# API implementation is merged.
## PMC changes:
- Currently 22 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Doug Service on Fri Sep 29 2017
## Committer base changes:
- Currently 35 committers.
- Scott Inglis was added as a committer on Fri Sep 28 2018
## Releases:
- Last release was 0.16 on Thu Aug 10 2017
## Mailing list activity:
- dev@reef.apache.org:
- 85 subscribers (up 0 in the last 3 months):
- 37 emails sent to list (592 in previous quarter)
- user@reef.apache.org:
- 18 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
## JIRA activity:
- 11 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BC: Report from the Apache River Project [Peter Firmstone]
## Description:
- Apache River provides a platform for dynamic discovery and lookup search of
network services. Services may be implemented in a number of languages,
while clients are required to be jvm based (presently at least), to allow
proxy jvm byte code to be provisioned dynamically.
## Issues:
- No significant issues requiring board attention at this time.
## Activity:
- Minimal activity at present, initial work modular build structure has
commenced, awaiting to be populated with River 3.0 code.
Release roadmap:
River 3.1 - Modular build restructure (& binary release) River 3.2 - Input
validation 4 Serialization, delayed unmarshalling& safe ServiceRegistrar
lookup service.River 3.3 - OSGi support
## Health report:
- River is a mature codebase with existing deployments, it was primarily
designed for dynamic discovery of services on private networks. IPv4 NAT
limitations historically prevented the use of River on public networks,
however the use of IPv6 on public networks removes these limitations. Web
services evolved with the publish subscribe model of todays internet, River
has the potential to dynamically discover services on IPv6 networks, peer
to peer, blurring current destinctions between client and server, it has
the potential to address many of the security issues currently experienced
with IoT and avoid any dependency on the proprietary cloud for "things".
- Future Direction:
* Target IOT space with support for OSGi and IPv6 (security fixes required
prior to announcement)
* Input validation for java deserialization - prevents DOS and Gadget
attacks.
* IPv6 Multicast Service Discovery (River currently only supports IPv4
multicast discovery).
* Delayed unmarshalling for Service Lookup and Discovery (includes
SafeServiceRegistrar mentioned in release roadmap), so authentication can
occur prior to downloading service proxy's, this addresses a long
standing security issue with service lookup while significantly improving
performance under some use cases.
* Security fixes for SSL endpoints, updated to TLS v1.2 with removal of
support for insecure cyphers.
* Secure TLS SocketFactory's for RMI Registry, uses the currently logged in
Subject for authentication. The RMI Registry still plays a minor role in
service activation, this allows those who still use the Registry to
secure it.
* Maven build to replace existing ant built that uses classdepandjar, a
bytecode dependency analysis build tool.
* Updating the Jini specifications.
## PMC changes:
- Currently 12 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dan Rollo on Fri Dec 01 2017
## Committer base changes:
- Currently 16 committers.
- No new committers added in the last 3 months
- Last committer addition was Dan Rollo at Thu Nov 02 2017
## Releases:
- Last release was River-3.0.0 on Thu Oct 06 2016
## Mailing list activity:
- Relatively quiet.
- dev@river.apache.org:
- 91 subscribers (down -3 in the last 3 months):
- 7 emails sent to list (6 in previous quarter)
- user@river.apache.org:
- 92 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (3 in previous quarter)
## JIRA activity:
- 1 JIRA tickets created in the last 3 months
- 0 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BD: Report from the Apache RocketMQ Project [Xiaorui Wang]
## Description:
- Apache RocketMQ is a distributed messaging and streaming platform with low
latency, high performance and reliability, trillion-level capacity and
flexible scalability.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Formal introduction to the RocketMQ Improvement Proposal. Nowadays, The
community has provided the 6 RIPs. We request infra team to open wiki in
Github to archive the data.
- Apache RocketMQ meetup Beijing, China ended in Sep. 300+ spectators
attended
- Call for proposal for Apache RocketMQ meetup Hangzhou, China.
- Du Heng presented Apache Way and RocketMQ at COSCon 2018 Shenzhen, China.
- Xin Wang presented Stream Processing with Apache RocketMQ at Flink China
Meetup 2018 Shanghai, China.
- Von Gosling presented Apache RocketMQ in practice at Linux Foundation’s Open
Source Networking Day. Beijing, China.
## Health report:
Within the past three months (since 2018-08-01 ):
- 94 GitHub issues were opened and 71 were closed
- 53 GitHub pull requests were opened and 41 were closed
## PMC changes:
- Currently 10 PMC members.
- No new PMC members added in the last 3 months, followup the 1 active
committer, have a chance of becoming PMC member.
- Last PMC addition was Bruce Snyder on Wed Sep 20 2017
## Committer base changes:
- Currently 17 committers.
- Xin Wang was added as a committer on Mon Sep 03 2018
- Du Heng was added as a committer on Wed Aug 29 2018
- Last committer addition: Mon Sep 03 2018 (Xin Wang)
- At least 5 active contributors have a chance to be committers, followup
## Releases:
- ROCKETMQ-4.3.0 was released on Jul 31, 2018
- ROCKETMQ-4.3.1 was released on Aug 29, 2018
- ROCKETMQ-4.3.2 was voted on Nov 7, 2018
## Mailing list activity:
We have disabled the JIRA system so the issues mailing list has no activity.
- users@rocketmq.apache.org:
- 158 subscribers (up 14 in the last 3 months):
- 59 emails sent to list (112 in previous quarter)
- dev@rocketmq.apache.org:
- 130 subscribers (up 9 in the last 3 months):
- 766 emails sent to list (643 in previous quarter)
- commits@rocketmq.apache.org:
- 57 subscribers (up 5 in the last 3 months):
- 125 emails sent to list (121 in previous quarter)
-----------------------------------------
Attachment BE: Report from the Apache Roller Project [David M. 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. Latest release is 5.2.1 and the ASF blog site at blogs.apache.org
runs on Roller 5.1.2 Tomcat and MySQL.
## Issues:
- Response to board questions from last report:
- rb: I improved the Health report to better reflect reality of project.
- idf: unfortunately, no new prospects for a while now. I'll nominate just
about anybody who shows interest at this point.
- There are no other issues requiring board attention at this time
## Activity:
- More progress made on new Struts-Bootstrap implementation of UI, about 75%
done with rewrite of web UI.
- New release made in October to upgrade Struts 2.
## Health report:
Community is made-up of part-time volunteers with limited time to devote to
Roller. Currently only one committer is actively working on developing Roller
and making release. For the most part other committers only have time to
review and test release.
## 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 8 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.2.1 on Oct 14 2018
## /dist/ errors: 12
I don't know what this means but I will follow up on it by the next report.
## 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:
- 150 subscribers (down -3 in the last 3 months):
- 23 emails sent to list (4 in previous quarter)
- user@roller.apache.org:
- 273 subscribers (down -2 in the last 3 months):
- 5 emails sent to list (4 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 1 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BF: 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:
- There was one new release over the last quarter. Version 2.0.2 of the
XML Security for C++ project was released. This patch corrects a bug that
can cause crashes in upstream applications.
Some ongoing work has also taken place on a new major release of the Java
library, which is expected in a few weeks.
## 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.
We added the first new committer and PMC member in many years over the
last quarter (Dan Kulp).
## PMC changes:
- Currently 7 PMC members.
- Daniel Kulp was added to the PMC on Mon Oct 01 2018
## Committer base changes:
- Currently 17 committers.
- Daniel Kulp was added as a committer on Mon Oct 01 2018
## Releases:
- Apache Santuario XML-Security C++ 2.0.2 was released on Fri Nov 02 2018
## JIRA activity:
- 6 JIRA tickets created in the last 3 months
- 5 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BG: Report from the Apache Serf Project [Branko Čibej]
Report from the Apache Serf Project [Branko Čibej]
## Description:
The serf library is a high performance C-based HTTP client library
built upon the Apache Portable Runtime (APR) library. Serf is the
default client library of Apache Subversion, Apache OpenOffice and
mod_pagespeed.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
There is some ongoing work to get Serf 1.4.0 released. The release
branch was created and a release candidate package is being tested.
## Health report:
Activity is at a normal, fairly quiet level.
## PMC & Committer changes:
Currently 13 PMC members and 13 committers.
Branko Čibej was installed as PMC Chair at the Board meeting in September.
## Releases:
Apache Serf 1.3.9 was released on Thu Sep 01 2016
## Mailing list and Jira activity:
Normal slow activity.
-----------------------------------------
Attachment BH: 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 and Health report:
SIS 0.8 release was one year ago. We have about 15 tasks scheduled for
1.0 release [1], most of them being regressions not yet fixed,
compatibility with Java 11 not yet verified, conformance with some
international standards not yet verified. Currently, Apache SIS is
getting new features during work days - those features were not
requirements for 1.0 releases - but work on the tasks scheduled for 1.0
release can be done only during weekends. This make difficult to predict
when those tasks will be completed. At this time, we wish to fix at
least the regressions before a release.
The Google Summer of Code has been completed successfully, but
integration of this work is planed only after SIS 1.0 release. Small
contributions from a San-Fransisco student also occurred during summer
and stopped after university resumed.
A talk on SIS and geospatial API for the cloud has been done during the
geospatial track in Montréal ApacheCon with about 30 attendees in the
room. Interesting discussions happened after the presentation (how to
balance standardization and the habits of various user communities,
applications to aeronautic, connection with Apache Calcite, addition of
"geospatial", "machine learning" and "internet of things" categories for
Apache projects) [2]. A similar talk will be presented on December 6th
at Paris Open Source Summit 2018 [3]. Geospatial API were also discussed
in September at the Open Geospatial Consortium meetings [4].
## PMC changes:
Currently 20 PMC members. No new PMC members added in the last 3 months.
Last PMC addition was Johann Sorel on September 7, 2017.
## 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.
## Releases:
0.8 was released on November 24, 2017. Next release will be 1.0.
## Mailing list activity:
dev@sis.apache.org:
* 72 subscribers (up 2 in the last 3 months):
* 28 emails sent to list (80 in previous quarter)
user@sis.apache.org:
* 48 subscribers (up 1 in the last 3 months):
* 1 emails sent to list (3 in previous quarter)
## JIRA activity:
* 10 JIRA tickets created in the last 3 months
* 8 JIRA tickets closed/resolved in the last 3 months
[1] https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20new%20AND%20project%20%3D%2012311072%20AND%20fixVersion%20%3D%2012341704%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
[2] https://lists.apache.org/thread.html/a64ae6bb1962eb052b65da8680eab10068879f88d7e1794000d9eb47@%3Cgeospatial.apache.org%3E
[3] https://www.opensourcesummit.paris/
[4] https://lists.apache.org/thread.html/bfeb6938fff3db4dff69c395e3d6eff83748abc9f6e0c54041767c23@%3Cgeospatial.apache.org%3E
-----------------------------------------
Attachment BI: Report from the Apache Spark Project [Matei Alexandru 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 Apache Spark 2.4.0 on Nov 2nd, 2018 as our newest feature
release. Spark 2.4's features include a barrier execution mode for machine
learning computations, higher-order functions in Spark SQL, pivot syntax in
SQL, a built-in Apache Avro data source, Kubernetes improvements, and
experimental support for Scala 2.12, as well as multiple smaller features
and fixes. The release notes are available at
http://spark.apache.org/releases/spark-release-2-4-0.html.
- We released Apache Spark 2.3.2 on Sept 24th, 2018 as a bug fix release for
the 2.3 branch.
- Multiple dev discussions are under way about the next feature release, which
is likely to be Spark 3.0, on our dev and user mailing lists. Some of the
key questions are which JDK, Scala, Python, R, Hadoop and Hive versions to
support, as well as whether to remove certain deprecated APIs. We encourage
everyone in the community to give feedback on these discussions through the
mailing lists and JIRA.
Trademarks:
- We are continuing engagement with various organizations.
Latest releases:
- Nov 2nd, 2018: Spark 2.4.0
- Sept 24th, 2018: Spark 2.3.2
- July 2nd, 2018: Spark 2.2.2
Committers and PMC:
- We added six new committers since the last report: Shane Knapp, Dongjoon
Hyun, Kazuaki Ishizaki, Xingbo Jiang, Yinan Li, and Takeshi Yamamuro.
- The latest committer was added on Sept 18th, 2018 (Kazuaki Ishizaki).
- The latest PMC member was added on Jan 12th, 2018 (Xiao Li).
-----------------------------------------
Attachment BJ: Report from the Apache Stanbol Project [Fabian Christ]
-----------------------------------------
Attachment BK: Report from the Apache Subversion Project [Stefan Sperling]
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 is healthy and active. New features are being designed
and developed, and bug reports are being handled. Our user support
forums (Email and IRC) receive questions and answers regularly.
Our last committer additions happened in October 2017:
Pavel Lyalyakin who has been contributing to the project's website.
Troy Curtis Jr who has been contributing to SVN's Python 3 bindings.
* Releases
We have released Subversion 1.10.3 on October 10 2018, and
Subversion 1.11.0 on October 30 2018.
The current supported releases are 1.9.9, 1.10.3, and 1.11.0.
* The PMC was formally enquired by the European Commission regarding
the merger of Microsoft and GitHub. The RFI was responded to by the
Chairman.
* Delayed patching of known security issues
The developer base keeps prioritizing other work over known security
problems. The Apache Security team keeps sending us occasional
reminders about problems which got CVE numbers assigned to them
but have no public fix yet after months of being reported.
Part of the problem is that our active developer base is shrinking.
Some outstanding work on security issues was begun by developers
who appear to have since become inactive.
The status of outstanding known security issues is documented below.
^/pmc/subversion/security/CVE-2018-1293
Per recommendation by the Apache Security team, this problem is now
being treated as a non-security issue.
The impact is a DoS which can only be triggered by an authenticated
attacker, and is easily resolved with 'svn rm'. Also, the work
required for a fix is not trivial so development on a public branch
will be easier than mailing patch files around. A fix is now being
developed in public: https://svn.apache.org/r1846391
-----------------------------------------
Attachment BL: Report from the Apache Synapse Project [Isuru Udana]
## Description:
Apache Synapse is a high performance, flexible, lightweight
Enterprise Service Bus (ESB) and a mediation framework.
## Issues:
None identified.
## Activity:
There was a slight increase of the activity in the project compared to last quarter.
## Health report:
All PMC members and committers active on the project in the recent past got busy with their other work, so they couldn’t contribute to the project.
We hope to bring back the project to life at towards the end of the year.
## PMC changes:
- Currently 27 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Prabath Ariyarathna on Thu May 04 2017
## Committer base changes:
- Currently 34 committers.
- No new committers added in the last 3 months
- Last committer addition was Prabath Ariyarathna at Fri Feb 10 2017
## Releases:
- Last release was 3.0.1 on Sat Dec 09 2017
## Mailing list activity:
- dev@synapse.apache.org:
- 185 subscribers (down -1 in the last 3 months):
- 17 emails sent to list (5 in previous quarter)
- user@synapse.apache.org:
- 177 subscribers (up 0 in the last 3 months):
- 1 emails sent to list (3 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 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:
We are keeping ourselves busy with maintenance work (including feature
addition) onto the 2_0_X and 2_1_X branches, which led to the recent 2.1.2 and
2.0.11 releases.
Two security issues were raised and managed (CVE-2018-17184 and
CVE-2018-17186)
We have been able to finalize and merge the work done in GSoC 2018.
Discussion around the features to work on next 3.0.0 needs to start on the
dev@.
## Health report:
Discussions about new features and improvements keep appearing and being
followed up in dev@.
Users keep asking for basic and advanced features and customizations in user@
and are eventually getting supported by the community.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Matteo Alessandroni on Fri Dec 22 2017
## Committer base changes:
- Currently 23 committers.
- No new committers added in the last 3 months
- Last committer addition was Dima Ayash at Mon Jul 09 2018
## Releases:
- 2.0.10 was released on Fri Aug 17 2018
- 2.1.1 was released on Fri Aug 17 2018
- 2.0.11 was released on Fri Nov 02 2018
- 2.1.2 was released on Fri Nov 02 2018
-----------------------------------------
Attachment BN: Report from the Apache SystemML Project [Jon 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:
- The latest release, 1.2.0, was approved on August 24th, 2018.
- One new committer was added this quarter.
## Health report:
- Code activity is healthy with 69 commits in the last 3 months.
- Community growth is healthy with our last new committer approved in August.
- Communication on the dev mailing list is down. 30 emails were sent to the
dev list this quarter but no emails in the last 2 months.
## PMC changes:
- Currently 23 PMC members.
- No new PMC members were added in the last 3 months.
## Committer base changes:
- Currently 26 committers.
- Guobao Li was added as a committer on August 28, 2018.
## Releases:
- Version 1.2.0 was released on August 24, 2018.
-----------------------------------------
Attachment BO: Report from the Apache TomEE Project [David Blevins]
## Description:
Apache TomEE delivers enterprise application containers and services based
on, but not limited to the Enterprise JavaBeans Specification and Java
Enterprise Edition Specifications.
## Activity
Activity has started to climb on the project with work on adding more
MicroProfile compliance into TomEE. MicroProfile JWT was added as discussed
in the last two board reports and was the only support for those periods. On
Sep 7th the project released a new branch of TomEE, called 7.1, which is
TomEE 7 + MicroProfile 1.x on Java 8. This release adds MicroProfile Config
and MicroProfile FaultTolerance, both using the Geronimo implementations.
The master branch switched from TomEE 7 to the future TomEE 8 and a milestone
release of TomEE 8 was completed Oct 19th. The release contains Java EE 8
work which had been ongoing for a long period of time, plus MicroProfile
Health Check, MicroProfile Metrics, MicroProfile Rest Client and MicroProfile
Open API bringing the total number of MicroProfile specifications supported
to 7. The Geronimo implementations were used for all these integrations.
A maintenance release of TomEE 7.0.5 was completed July 24th and consists of
bug fixes, minor dependency upgrades and patched security vulnerabilities.
Nominated by Mark Struberg, the project voted in new committer Roberto Cortez
on Sep 6th for his contributions to the project's MicroProfile efforts and
releases. Discussions on other new potential committers are in progress, also
started by Mark.
Committer Jonathan Fisher who had been voted in last year, but never
completed his CLA and account has now gone through the process and officially
made his first commit this September. He's remained active since which has
been very good for the project.
## PMC changes:
- Currently 11 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Andy Gumbrecht on Tue Aug 11 2015
- Romain Manni-Bucau stepped down from PMC Aug 13 2018
## Committer base changes:
- Currently 31 committers.
- Last two committers added
- Jonathan S Fisher on Wed Nov 1 2017
- Roberto Cortez on Thu Sep 6 2018
## Releases:
- Apache TomEE 7.0.5 on Jul 24, 2018
- Apache TomEE 7.1.0 on Sep 7, 2018
- Apache TomEE 8.0.0-M1 on Oct 19, 2018
-----------------------------------------
Attachment BP: Report from the Apache Traffic Control Project [David Neuman]
## Description:
- Apache Traffic Control can be used to build, monitor, configure, and
provision a large-scale content delivery network (CDN).
## Issues:
- There are no issues requiring board attention at this time
## Activity:
- Held our annual fall summit in Denver in October, which had over 30
registered attendees. These summits are always great for getting the
community together and injecting some enthusiasm. Summits also usually
lead to an increase in activity on the mailing lists because that is where
decisions are made.
- Announced a Release Candidate for Traffic Control 3.0
- A few PMC members attended and spoke at ApacheCon NA!
## Health report:
- The Project is healthy. The project seems to have gained some interest
over the past few months which is encouraging!
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Eric Covener on Tue May 15 2018
## Committer base changes:
- Currently 20 committers.
- No new committers added in the last 3 months
- Last committer addition was Dylan Volz at Mon Jul 23 2018
## Releases:
- Last release was apache-trafficcontrol-2.2.0 on Mon Jun 25 2018
## Mailing list activity:
- users@trafficcontrol.apache.org:
- 106 subscribers (up 4 in the last 3 months):
- 43 emails sent to list (27 in previous quarter)
- dev@trafficcontrol.apache.org:
- 97 subscribers (up 1 in the last 3 months):
- 187 emails sent to list (173 in previous quarter)
## GitHub activity:
- 238 Pull requests submitted in the last quarter
- 239 Pull Requests merged/closed in the last quarter
- 149 issues created in quarter
- 152 issues closed in the last 30 days
-----------------------------------------
Attachment BQ: 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.
## Issues:
- No board-level issues at this time.
## Activity:
- Component upgrades and release preparing in progress (Turbine 5, Fulcrum,
archetype).
- Housekeeping in progress (defining dormant components, ..)
- Lightning Talk by Jeffery Painter at ApacheCon NA 2018
- Apache Db Torque ORM support efforts to allow for release v 4.1 (related to
Fulcrum Security Torque).
- Discussion about migration/JSON issues on mailing list
## Health report:
- The Turbine project has had a well above noise quarter activity with
community collaboration in dev/user mailing list and ongoing code changes
across all components.
## PMC changes:
- Currently 9 PMC members.
- Last PMC addition was Jeffery Painter on Sun Nov 12 2017.
## Committer base changes:
- Currently 11 committers.
- No new changes to the committer base since last report.
- Last committer addition was more than 2 years ago.
## Releases:
- Last release was Turbine 4.0.1 on Mon Mar 05 2018.
- Turbine Parent 5 and Turbine Parent Assembly 1.0.1 (build tools), both on
Mon Oct 29 2018.
-----------------------------------------
Attachment BR: Report from the Apache Usergrid Project [Todd Nine]
## Description:
- Usergrid is Backend-as-a-Service (BaaS) composed of an integrated database
(Cassandra), a query engine (ElasticSearch), and application layer and
client tier with SDKs for developers.
## Issues:
- There are no issues requiring board attention at this time.
## Activity:
- Various Bugfixes around index querying and maintenance.
- Improved test stability.
- Experimentation with using newer versions(5.x) of Elasticsearch vs.
supported older version (1.7).
## Health report:
- Growth has been flat over the past year or so. Some of historical core
contributors have not been active with the project recently. However, there
are contributions from a potential new committer. In addition, the
project's chair just changed. Getting the project to a healthier state will
be a focus over the next few months. This includes more discussion on the
mailing lists, better use of JIRA, and planning of a new release -- master
branch is currently stable.
## PMC changes:
- Currently 25 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Mike Dunker on Mon Jan 18 2016
## Committer base changes:
- Currently 15 committers.
- No new committers added in the last 3 months
- Last committer addition was Robert Walsh at Sun Feb 26 2017
## Releases:
- Last release was 2.1.0 on Wed Feb 17 2016
## /dist/ errors: 1
- This will be looked at and resolved asap.
## Mailing list activity:
- As mentioned in the Health section, growth and activity is flat and the
mailing list shows the same.
- dev@usergrid.apache.org:
- 107 subscribers (up 0 in the last 3 months):
- 89 emails sent to list (8 in previous quarter)
- user@usergrid.apache.org:
- 143 subscribers (down -2 in the last 3 months):
- 9 emails sent to list (3 in previous quarter)
## JIRA activity:
- 4 JIRA tickets created in the last 3 months
- 2 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BS: Report from the Apache Velocity Project [Nathan Bubna]
## Description:
- Java-based template engine
## Issues:
- No issues requiring board attention at this time.
## Activity:
- Moderate. Activity mostly centering on the Tools 3.0 release.
## Health report:
- Project has pulled together several major releases in last 4 months. Active
team is small, could be more responsive to contributors, but things are
getting done.
## PMC changes:
- Currently 9 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Michael Osipov 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:
- Velocity Master POM 3 was released on 2018-10-25
- Velocity Tools 3.0 was released on 2018-10-01
- Velocity Engine 2.0 was released on 2018-08-06
## Mailing list activity:
- Lots of work on the Tools 3 release, some discussion on backward
compatibility for Engine 2.0 regardless of major version bump. Not much
else.
- dev@velocity.apache.org:
- 120 subscribers (up 0 in the last 3 months):
- 204 emails sent to list (116 in previous quarter)
- general@velocity.apache.org:
- 72 subscribers (down -1 in the last 3 months):
- 2 emails sent to list (4 in previous quarter)
- user@velocity.apache.org:
- 284 subscribers (down -3 in the last 3 months):
- 3 emails sent to list (5 in previous quarter)
## JIRA activity:
- 12 JIRA tickets created in the last 3 months
- 38 JIRA tickets closed/resolved in the last 3 months
-----------------------------------------
Attachment BT: Report from the Apache Whimsy Project [Sam Ruby]
-----------------------------------------
Attachment BU: Report from the Apache Xalan Project [Steven J. Hathaway]
-----------------------------------------
Attachment BV: Report from the Apache Xerces Project [Michael Glavassevich]
-----------------------------------------
Attachment BW: Report from the Apache XML Graphics Project [Clay Leeds]
-----------------------------------------
Attachment BX: Report from the Apache Servicecomb Project [Willem Ning Jiang]
## Description:
- ServiceComb is a microservice framework that provides a set of tools and
components to make development and deployment of cloud applications easier.
## Issues:
- there are no issues requiring board attention at this time
## Activity:
- ServiceComb just graduated from incubator, we are in the middle of
transferring. Now the PMC is working on our first TLP release.
## Health report:
- Overall, the community is healthy.
- Activity on the Gitter channel is still high, many first time users come to
ask questions while getting started. There are 130 users on the channel.
## PMC changes:
- Currently 16 PMC members.
- No new PMC members added in the last 3 months
## Committer base changes:
- Currently 18 committers.
- New commmitters:
- Haishi Yao was added as a committer on Tue Nov 13 2018
- Jun Zhao was added as a committer on Tue Nov 13 2018
## Releases:
- Last release was ServiceComb java-chassis 1.0.0 and service-center 1.0.0
on 2018-08-02
## Mailing list activity:
- As we move the github notification to another mailing list , the dev mail
dropped a little bit.
- dev@servicecomb.apache.org:
- 126 subscribers (up 19 in the last 3 months):
- 467 emails sent to list (621 in previous quarter)
- issues@servicecomb.apache.org:
- 8 subscribers (up 0 in the last 3 months):
- 2234 emails sent to list (3180 in previous quarter)
## JIRA activity:
- 182 JIRA tickets created in the last 3 months
- 161 JIRA tickets closed/resolved in the last 3 months
------------------------------------------------------
End of minutes for the November 21, 2018 board meeting.
Index