Index
Links: 2022 - All years
- Original The Apache Software Foundation
Board of Directors Meeting Minutes
May 18, 2022
1. Call to order
The meeting was scheduled for 15:00 UTC and began at 15:02 when
a sufficient attendance to constitute a quorum was recognized by
the chair.
Other Time Zones: https://timeanddate.com/s/42hh
The meeting was held via teleconference, hosted by the Secretary
via Zoom.
The #asfboard channel on the-asf.slack.com was used for backup.
2. Roll Call
Directors Present:
Rich Bowen
Bertrand Delacretaz
Christofer Dutz
Roy T. Fielding
Sharan Foga
Willem Ning Jiang
Sam Ruby
Roman Shaposhnik
Sander Striker
Directors Absent:
none
Executive Officers Present:
Craig R. McClanahan
Craig L Russell
Matt Sicker
Ruth Suehle
Executive Officers Absent:
David Nalley
Guests:
Daniel Gruno
Dave Fisher
Greg Stein
Joe Brockmeier - :02
Karl Heinz Marbaise
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 April 20, 2022
See: board_minutes_2022_04_20.txt
Tabled.
4. Executive Officer Reports
A. Board Chair [Sander Striker]
May has taken me slightly by surprise. I've had some unexpected
travel last week; a first for me since the start of COVID-19. Having
had a reminder of what face-to-face contact is like again, I can only
imagine that ApacheCon NA 2022 is going to be a great experience
again. It is also worth exploring having the board gather face to
face.
Regarding the board meeting, I'd like to express my thanks to the
directors for their diligence. The vast majority of reports is in,
and has seen enough pre-approvals for swift coverage during the
meeting.
In March we agreed to have a special members meeting in June. I'm in
the process of preparing the notice. My intent is to keep the meeting
agenda simple and focused. If this process works well, there is no
reason to not have another meeting in say September, if so desired.
B. President [David Nalley]
It's been a relatively quiet month.
We received an invite to participate in the followup meeting with the
White House regarding open source supply chain security. We ultimately
declined, due to scheduling and time constraints.
Additionally, I received an invite to testify before the US House of
Representatives Committee on Science, Space, & Technology about open
source supply chain. Again, timing, schedule constraints, and the fact
that Brian Behlendorf was already planning to testify, I ultimately
declined the invitation.
Additionally, please see Attachments 1 through 8.
C. Treasurer [Craig R. McClanahan]
As we have completed our 2021-2022 fiscal year (ending on April 30,
2022), we primarily focused on cleaning up some outstanding issues on
the way Targeted Donations have been handled - in some cases the funds
were not actually separated from unrestricting giving, and in some
cases expenditures were not being charged against the Targeted
Donations for each particular project. Several of these have been
resolved, but a few remain to be addressed - including some targeted
donations that have been on the books for a long time. We will be
working with Fundraising to resolve the current status of each of
these donations, as well as implement a standard strategy (worked out
with Fundraising) on how to deal with future targeted donations.
On the Statement of Financial Position (formerly called the Balance
Sheet, but this term is more accurate when it relates to non-profits
like us), you will see two numbers listed under the Operating Reserve
category:
Operating Reserve-Basis: This balance is made up of (1) Our
initial contribution to the reserve ($100 test transaction to confirm
that the wire transfer process works correctly, $2,000,000 for the
initial contribution; (2) Increased by interest payments we receive
monthly; (3) Decreased by management fees with TD Wealth on a
quarterly basis.
Unrealized Gains/Losses: What we would make or lose
if we sold the entire portfolio, at end-of-month market prices. Why
is it negative right now? We are invested in a broad list of high
quality corporate bonds - and when interest rates are rising (as they
are at the moment), the sales price of bonds goes down in order to
maintain competitive yields. Should we be concerned? No - unlike
with purchasing stocks, we are guaranteed the original bond amount
when it matures, unless (a) a bond seller defaults on paying the bonds
off – extremely unlikely with the investments recommended by our
advisor, or (b) we have to sell prior to maturity – which is also
extremely unlikely unless our fundraising falls off a cliff.
Because this was the end of our fiscal year, a YTD
this-year-versus-last-year report was provided, so we can review the
entire year’s activity in addition to just the current month.
D. Secretary [Matt Sicker]
No report was submitted.
E. Executive Vice President [Ruth Suehle]
- ApacheCon CFP remains open
- Hotel reservations link has arrived! Watch the website for that and registration soon.
- Currently $167,500 in expected sponsorship funds
F. Vice Chair [Shane Curcuru]
Nothing to report for the month.
Executive officer reports approved as submitted by General Consent.
5. Additional Officer Reports
A. VP of W3C Relations [Andy Seaborne / Rich]
See Attachment 9
B. Apache Legal Affairs Committee [Roman Shaposhnik]
See Attachment 10
C. Apache Security Team Project [Mark J. Cox / Sander]
See Attachment 11
D. VP of Jakarta EE Relations [Rob Tompkins / Sam]
No report was submitted.
Additional officer reports approved as submitted by General Consent.
6. Committee Reports
Summary of Reports
The following reports required further discussion:
# Data Privacy [striker]
# Ignite [sharan]
# Xalan [striker]
A. Apache Ant Project [Jan Materne / Roman]
No report was submitted.
B. Apache BookKeeper Project [Sijie Guo / Sharan]
See Attachment B
C. Apache Brooklyn Project [Geoff Macartney / Roy]
See Attachment C
D. Apache Buildr Project [Antoine Toulme / Willem]
See Attachment D
E. Apache Cassandra Project [Michael Semb Wever / Christofer]
See Attachment E
F. Apache Clerezza Project [Hasan Hasan / Sander]
No report was submitted.
G. Apache Cocoon Project [Cédric Damioli / Bertrand]
See Attachment G
H. Apache Community Development Project [Swapnil Mane / Sander]
See Attachment H
I. Apache CouchDB Project [Jan Lehnardt / Rich]
No report was submitted.
J. Apache Creadur Project [Philipp Ottlinger / Sharan]
See Attachment J
K. Apache DataSketches Project [Lee Rhodes / Roman]
See Attachment K
L. Apache DeltaSpike Project [Mark Struberg / Willem]
No report was submitted.
M. Apache Drill Project [Charles Givre / Christofer]
See Attachment M
N. Apache Druid Project [Gian Merlino / Roy]
See Attachment N
O. Apache Empire-db Project [Rainer Döbele / Willem]
See Attachment O
P. Apache Flume Project [Balázs Donát Bessenyei / Sam]
See Attachment P
Q. Apache FreeMarker Project [Dániel Dékány / Bertrand]
See Attachment Q
R. Apache Geode Project [Dan Smith / Willem]
See Attachment R
S. Apache Giraph Project [Dionysios Logothetis / Bertrand]
See Attachment S
T. Apache Gora Project [Kevin Ratnasekera / Sam]
No report was submitted.
U. Apache Griffin Project [William Guo / Roy]
No report was submitted.
V. Apache Groovy Project [Paul King / Rich]
See Attachment V
W. Apache Hop Project [Hans Van Akelyen / Sander]
See Attachment W
X. Apache HTTP Server Project [Joe Orton / Roman]
See Attachment X
Y. Apache HttpComponents Project [Michael Osipov / Christofer]
See Attachment Y
Z. Apache Ignite Project [Dmitry Pavlov / Sharan]
See Attachment Z
@Sharan: follow up on recognition service details
AA. Apache Impala Project [Jim Apple / Roman]
See Attachment AA
AB. Apache Incubator Project [Justin Mclean / Christofer]
See Attachment AB
AC. Apache jUDDI Project [Alex O'Ree / Bertrand]
See Attachment AC
AD. Apache Juneau Project [James Bognar / Sam]
See Attachment AD
AE. Apache Kafka Project [Jun Rao / Sander]
See Attachment AE
AF. Apache Kibble Project [Sharan Foga]
No report was submitted.
AG. Apache Knox Project [Larry McCay / Roy]
See Attachment AG
AH. Apache Kudu Project [Andrew Wong / Rich]
See Attachment AH
AI. Apache Kylin Project [Shao Feng Shi / Christofer]
See Attachment AI
AJ. Apache Libcloud Project [Tomaž Muraus / Sharan]
See Attachment AJ
AK. Apache Logging Services Project [Ron Grabowski / Willem]
See Attachment AK
AL. Apache Mahout Project [Trevor Grant / Willem]
See Attachment AL
AM. Apache ManifoldCF Project [Karl Wright / Roy]
No report was submitted.
AN. Apache Oozie Project [Dénes Bodó / Christofer]
See Attachment AN
AO. Apache OpenWhisk Project [Dave Grove / Sander]
See Attachment AO
AP. Apache Ozone Project [Sammi Chen / Sharan]
See Attachment AP
AQ. Apache Perl Project [Steve Hay / Sam]
See Attachment AQ
AR. Apache Petri Project [Dave Fisher / Rich]
See Attachment AR
AS. Apache Phoenix Project [Ankit Singhal / Bertrand]
See Attachment AS
AT. Apache Pinot Project [Kishore G / Roman]
See Attachment AT
AU. Apache POI Project [Dominik Stadler / Bertrand]
See Attachment AU
AV. Apache Qpid Project [Robbie Gemmell / Christofer]
See Attachment AV
AW. Apache Ranger Project [Selvamohan Neethiraj / Roman]
See Attachment AW
AX. Apache REEF Project [Sergiy Matusevych / Sam]
No report was submitted.
AY. Apache RocketMQ Project [Xiaorui Wang / Rich]
See Attachment AY
AZ. Apache Roller Project [David M. Johnson / Roy]
See Attachment AZ
BA. Apache Santuario Project [Colm O hEigeartaigh / Sharan]
No report was submitted.
BB. Apache Serf Project [Justin Erenkrantz / Rich]
No report was submitted.
BC. Apache ServiceComb Project [Willem Ning Jiang]
See Attachment BC
BD. Apache ShardingSphere Project [Liang Zhang / Willem]
See Attachment BD
BE. Apache SIS Project [Martin Desruisseaux / Sander]
See Attachment BE
BF. Apache Solr Project [Houston Putman / Bertrand]
See Attachment BF
BG. Apache Spark Project [Matei Alexandru Zaharia / Sander]
See Attachment BG
BH. Apache Streams Project [Steve Blackmon / Christofer]
See Attachment BH
BI. Apache Subversion Project [Nathan Hartman / Sam]
See Attachment BI
BJ. Apache Superset Project [Maxime Beauchemin / Rich]
See Attachment BJ
BK. Apache Syncope Project [Francesco Chicchiriccò / Sharan]
See Attachment BK
BL. Apache SystemDS Project [Matthias Boehm / Roman]
See Attachment BL
BM. Apache TomEE Project [David Blevins / Roy]
No report was submitted.
BN. Apache Traffic Control Project [Eric Friedrich / Willem]
See Attachment BN
BO. Apache Turbine Project [Georg Kallidis / Willem]
See Attachment BO
BP. Apache Velocity Project [Nathan Bubna / Rich]
No report was submitted.
BQ. Apache Whimsy Project [Shane Curcuru / Christofer]
See Attachment BQ
BR. Apache Xalan Project [Gary D. Gregory / Bertrand]
See Attachment BR
BS. Apache Xerces Project [Michael Glavassevich / Sharan]
No report was submitted.
BT. Apache XML Graphics Project [Clay Leeds / Sam]
See Attachment BT
BU. Apache YuniKorn Project [Weiwei Yang / Roman]
See Attachment BU
Committee reports approved as submitted by General Consent.
7. Special Orders
A. Create members-announce
WHEREAS, ASF members have requested that we provide a mailing list for
member announcements that is separate from the members list which is
used for discussions as well as being separate from the members list
which is used for notifications;
NOW, THEREFORE, BE IT RESOLVED, that a members-announce mailing list be
created, to which members are automatically subscribed, for the
limited purpose of sending annoucements, summaries, and pointers to
other discussions to the membership as a whole
Special Order 7A, Create members-announce, 6 yes, 3 no; no is
due to list being opt-out rather than opt-in
B. Change the Apache Bigtop Project Chair
WHEREAS, the Board of Directors heretofore appointed Kengo Seki
(sekikn) to the office of Vice President, Apache Bigtop, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Kengo Seki 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 Yuqi Gu (guyuqi) as the successor to
the post;
NOW, THEREFORE, BE IT RESOLVED, that Kengo Seki is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Bigtop, and
BE IT FURTHER RESOLVED, that Yuqi Gu 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 Phoenix Project Chair
WHEREAS, the Board of Directors heretofore appointed Ankit Singhal
(ankit) to the office of Vice President, Apache Phoenix, and
WHEREAS, the Board of Directors is in receipt of the resignation of
Ankit Singhal from the office of Vice President, Apache Phoenix, and
WHEREAS, the Project Management Committee of the Apache Phoenix project
has chosen by vote to recommend Rajeshbabu Chintaguntla (rajeshbabu) as
the successor to the post;
NOW, THEREFORE, BE IT RESOLVED, that Ankit Singhal is relieved and
discharged from the duties and responsibilities of the office of Vice
President, Apache Phoenix, and
BE IT FURTHER RESOLVED, that Rajeshbabu Chintaguntla be and hereby is
appointed to the office of Vice President, Apache Phoenix, 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 Phoenix Project Chair, was
approved by Unanimous Vote of the directors present.
D. Establish the Apache Doris 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 MPP-based interactive SQL data warehousing for
reporting and analysis.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache Doris Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache Doris be and hereby is responsible for the
creation and maintenance of software related to a MPP-based interactive
SQL data warehousing for reporting and analysis; and be it further
RESOLVED, that the office of "Vice President, Apache Doris " 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 Doris
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Doris
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 Doris Project:
* Conghui Cai <caiconghui@apache.org>
* Hao Chen <chenhao@apache.org>
* Mingyu Chen <morningman@apache.org>
* Dayue Gao <gaodayue@apache.org>
* Sijie Guo <sijie@apache.org>
* Willem Ning Jiang <ningjiang@apache.org>
* Kaisen Kang <kangkaisen@apache.org>
* Chaoyong Li <lichaoyong@apache.org>
* De Li <lide@apache.org>
* HaoPeng Li <lihaopeng@apache.org>
* Bin Ling <lingbin@apache.org>
* Hangyuan Liu <liuhangyuan@apache.org>
* Ruyue Ma <maruyue@apache.org>
* Ling Miao <lingmiao@apache.org>
* Zheng Shao <zshao@apache.org>
* Shao Feng Shi <shaofengshi@apache.org>
* Bo Wang <wangbo@apache.org>
* Zuo Wei <weizuo@apache.org>
* Ming Wen <wenming@apache.org>
* Zhengguo Yang <yangzhg@apache.org>
* Jiafeng Zhang <jiafengzheng@apache.org>
* Chun Zhao <zhaoc@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mingyu Chen be appointed
to the office of Vice President, Apache Doris , 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, Establish the Apache Doris Project, was
tabled.
E. Establish the Apache AGE 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 multi-model database that enables graph and relational
models built on PostgreSQL.
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache AGE Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache AGE Project be and hereby is responsible for
the creation and maintenance of software related to a multi-model
database that enables graph and relational models built on PostgreSQL;
and be it further
RESOLVED, that the office of "Vice President, Apache AGE" 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 AGE Project, and to
have primary responsibility for management of the projects within the
scope of responsibility of the Apache AGE 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 AGE Project:
* Alex Kwak <emotionbug@apache.org>
* Dehowe Feng <dehowef@apache.org>
* Eya Badal <eya@apache.org>
* Felix Cheung <felixcheung@apache.org>
* Jasper Blues <jasper@apache.org>
* John Gemignani <jgemignani@apache.org>
* Josh Innis <joshinnis@apache.org>
* Juan Pan <panjuan@apache.org>
* Kevin Ratnasekera <djkevincr@apache.org>
* Nick Sorrell <sorrell@apache.org>
* Pieterjan De Potter <pdpotter@apache.org>
* Von Gosling <vongosling@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Eya Badal be appointed to
the office of Vice President, Apache AGE, 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 Apache AGE Project be and hereby is tasked with the
migration and rationalization of the Apache Incubator AGE podling; and
be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
AGE podling encumbered upon the Apache Incubator PMC are hereafter
Discharged.
Special Order 7E, Establish the Apache AGE Project, was
approved by Unanimous Vote of the directors present.
8. Discussion Items
9. Review Outstanding Action Items
* Christofer: follow up on BT SIG
[ Mynewt 2021-09-15 ]
Status: Thanks to Justin helping them, the project managed to finish
the application for a BlueTooth ID and the project is now
unblocked.
* David: what do we do when SHTF?
[ Project Support 2022-01-19 ]
Status:
* David: follow up on this question re: brand management
[ President 2022-03-16 ]
Status: Done, as per https://s.apache.org/tcfbd
* Willem: pursue a report for DeltaSpike
[ DeltaSpike 2022-03-16 ]
Status: There is no response from DeltaSpike so far.
* Rich: pursue a report for Serf
[ Serf 2022-03-16 ]
Status: Still no report from Serf this month.
* Christofer: pursue a report for Incubator
[ Incubator 2022-04-20 ]
Status: Together with the other IPMCs we re-started the efforts to
remind and re-motivate the podlings to file their reports. As
far as I can see them, they are coming in nicely. Also started
discussion on how to keep things this way in the near future.
* Christofer: find out about minimum vote count
[ Storm 2022-04-20 ]
Status: So it seems that the project lost a great number of PMC
members, when Twitter moved away and Alibaba seemed to have
created a fork (However this seems to have been stale for some
time). After not being to release for some time, the RM
decided to call it a release. I have communicated with the
project, that this is generally not acceptable and that not
being able to release, usually is a reason for moving into the
attic. However I was told that from the 3 remaining
committers, that are not yet part of the PMC and are still
active, there will be votes to invite into the PMC soon.
However while chatting with the RM, he wasn't aware that he is
allowed to vote. So I asked him to do the formal release
candidate validation and cast a vote. He said that he did that
after my comment. So now we should be on the safe side.
10. Unfinished Business
11. New Business
12. Announcements
13. Adjournment
Adjourned at 15:27 UTC
============
ATTACHMENTS:
============
-----------------------------------------
Attachment 1: Report from the VP of Brand Management [Mark Thomas]
Covering the period April 2022
* ISSUES FOR THE BOARD
None.
* OPERATIONS
It was a quiet month.
I will be updating the formal TLP website requirements [1] to additionally
require a link to the ASF privacy policy.
Responded to the following queries, liaising with projects as required:
- one query from a PMC regarding naming of an event they are running
- one query regarding using project logos to refer to projects
- provided advice to a project regarding a potential community edition of a
book about the project
* REGISTRATIONS
Worked with counsel to progress the transfer of the DOLPHINSCHEDULER marks to
the ASF.
* INFRINGEMENTS
Two more potential infringements have been identified by the OpenOffice PMC.
[1] https://www.apache.org/foundation/marks/pmcs#navigation
-----------------------------------------
Attachment 2: Report from the VP of Fundraising [Bob Paulin]
1) ASF Sponsors: we have signed on a new Platinum, Gold and Bronze Sponsor. We
await new sponsorship and renewal payments for 4 Platinum, 2 Gold, and 5
Bronze Sponsors. We received payment from two Gold and one Bronze Sponsor.
2) Targeted Sponsors: ongoing process refinement regarding donations that
benefit individual PMCs.
3) Sponsor Relations: we met with two existing ASF Platinum Sponsors and
helped orient a Silver Sponsor’s new OSPO team.
4) Event Sponsorship: sponsorships for ApacheCon North America are in flight
and ahead of projections. We collected payment for an outstanding sponsorship
from 2021.
5) Individual Donations and Corporate Giving: we received $4.92K in individual
donations in April.
6) Administrivia: we continue to fine-tune ways to improve workflow with the
Accounting team, which enabled us to close out issues with a long-outstanding
Sponsor payment. We are also beginning to use a new CRM solution for Sponsor
lifecycle management.
-----------------------------------------
Attachment 3: Report from the VP of Marketing and Publicity [Joe Brockmeier]
== Overview
Quiet month, little to report since last month.
== Published
Combining March + April here as promised last month.
Published Weekly news round-up weekly March + April, see blogs.apache.org for
installments.
=== Blog in March
- Success at Apache: "My experience with the Apache Way —a perfect society?"
https://s.apache.org/r1j4c
- Announcing New ASF Board of Directors https://s.apache.org/5nmrr
- The Apache Software Foundation Welcomes VMware as its Newest Platinum
Sponsor https://s.apache.org/j91mb
=== Blog in April
- The Apache Software Foundation Welcomes 52 New Members
https://s.apache.org/b4wfu
- Your call is important to us: The Apache Software Foundation’s
Infrastructure team unveils new support line https://s.apache.org/dka8e
== Press releases
No press releases issued in April. One press release issued in March.
- The Apache Software Foundation Welcomes VMware as its Newest Platinum
Sponsor https://s.apache.org/nq2wh
== Analyst relations
Responded to 2 analyst queries in April and are coordinating 2 briefings with
an analyst team handling multiple sections of a larger report. Apache was
mentioned in 22 reports by Gartner, Forrester, and IDC combined.
In March responded to 3 analyst queries. Apache was mentioned in 14 reports by
Gartner, Forrester, and IDC combined. Liaised with PMCs regarding
participating in new Cloud performance testing research and NoSQL reports with
GigaOM, and pre-briefed an analyst firm on a report on data integration.
-----------------------------------------
Attachment 4: Report from the VP of Infrastructure [David Nalley]
General
=======
Infrastructure is operating as expected, and has no current issues
requiring escalation to the President or the Board.
Short Term Priorities
=====================
- Complete mail migration, then LDAP migration.
- Support Ubuntu 22.04 on our boxes.
Long Range Priorities
=====================
- Complete the Board Agenda Tool
- New artifact distribution system
General Activity
================
- Initial work on per-path commit emails for git
- AOO has completed VM migrations. Overall, we are nearly complete
with the migration away from Puppet v3.
- The new mail gateway is coming up to speed, and is handling some
projects' mailing lists now. We're fixing problems as we perform
some moves from the old machine (hermes) to the new system.
- More machines for HBase' Jenkins cluster (via donation).
- Investigations on blogging alternatives for M&P and projects.
- Pelican website improvements in docco and code.
- PoC deployment of Hashicorp Vault for secrets management, primarily
for GitHub self-Runners (but possibly broader usage).
- Bolt (a puppet tool) work, in relation to some of our machine
inventory scripting.
- Jira upgrade to fix a security issue.
- Cleanup/fixes for the upgraded GitBox service.
- Designing a new platform for artifact distribution, rolling up
dist.a.o, nightlies, archive, etc.
- Lots of disk space issues across our Jenkins clusters.
- Resolve backup issues for one of our larger boxes.
- Prepare Apache STeVe for upcoming Members Meeting.
- New Guy gets thrown into pager rotation. Heh.
-----------------------------------------
Attachment 5: Report from the VP of Conferences [Rich Bowen]
The Call for Presentations for both ApacheCon North America and
ApacheCon Asia are currently open, and will close by the end of the
month. We anticipate that the schedules will be published shortly
after that.
Sponsorship for both events is still currently available. See
https://apachecon.com/ for details.
-----------------------------------------
Attachment 6: Report from the Apache Travel Assistance Committee [Gavin McDonald]
Current Events
==============
ApacheCon NA 2022 New Orleans.
TAC Applications opened on April 4th to support both committers and
non-committers to attend. Applications are coming in steadily.
Reminder to other Operations Committees: TAC has a calendar that was created
as cross-committee information and is shared with some people from those
committees - if anyone wants access but does not yet have it, please ask.
When we opened applications, we sent out our announce email direct to PMCs and
as usual asked them to forward this on to their community user/dev lists.
Having checked on this after a few weeks I was disappointed to see that not
many PMCs did this. Therefore a large number of our user/dev base did not get
to see the announce mail that TAC applications were open. We then decided that
the follow up reminder mails and all future announce mails we would just send
direct to all project user/dev lists instead.
TAC app closes on July 1st 2022 so still a few weeks to receive new
applications.
Future Events
=============
None currently
Short/Medium Term Priorities
=====================
Still keeping an eye out for other smaller events to support.
Budget
======
Budget was approved!
TAC Chair has gotten up to speed on Ramp cards. A discussion with treasurers
Committee has come up with a workflow/plan for handling cards/purchases for
ApacheCon
Mailing List Activity
=====================
A few emails over the last couple of weeks. We have 20+ subscribers.
Membership
==========
No changes to the membership this month.
-----------------------------------------
Attachment 7: Report from the VP of Diversity and Inclusion [Katia Rojas]
## Description:
- The Diversity and Inclusion VP works in collaboration with a team that contributes towards generating a current description of the D&I landscape in the industry and for the foundation. The team also focuses on developing resources the projects can leverage to increase diversity and inclusion in their communities.
## Issues:
## Activity:
*** Project: Internships for underrepresented groups (Outreachy) ***
We got 2 interns approved, one inter per project. The announcement of the selected interns will be done on May 20th. [1]
The projects are: Improve Camel K API and Examples and Improve Camel K operator scalability.
The "May to August 2022" round will start with on May 30th.
*** Project: User Experience Research on new contributors ***
The community has provided feedback on the content of the survey [2]. We have closed the feedback period and included/addressed all the recommendations done.
The VP. of privacy, Christian Grobmeier, has assessed the survey tool from data privacy perspective and gave the GTG (good to go) to the tool. We are currently reviewing the GDPR checks completion and will start porting the survey content to the tool during the next days.
Bitergia is going to provided a new mockup of the dashboard that will be used as improvement method, we will review it in the next round.
*** Operations
Addressed emails related to our name "Apache".
Received new follow up emails about concerns caused by a potential misconduct or misbehaviour of an Apache member/contributor involving the topic of Russia and Ukraine. I will review them in the next days.
## Committee members' changes:
no news.
## References
[1] https://www.outreachy.org/communities/cfp/apache/
[2] https://docs.google.com/document/d/1s0TVBFf-KvOTl3IejI2FFOOTdkugZlX_ptnN6YWMFN0/edit?usp=sharing
-----------------------------------------
Attachment 8: Report from the VP of Data Privacy [Christian Grobmeier]
Privacy has received several "data removal requests", but apart from that, no
bigger issues.
We have published our privacy policy for public services (for all visitors on
websites): https://privacy.apache.org/policies/privacy-policy-public.html
With the announcement we have received generally good feedback. At this point,
already 22 projects have migrated to Matomo, the new ASF service we provide:
https://analytics.apache.org/
VP Data Privacy is grateful for the help of some volunteers, specifically
Martijn Visser, who was recently elected as committer, but also helps a lot
with creating new accounts on Matomo.
One interesting question was raised on the mailing list regarding the
"enforcement" of those policies. If interested in the context:
https://lists.apache.org/thread/vf4drk82so4k4tcw188h9370grzy8wz1
As it was explained, the privacy office can only give recommendations to apply
privacy practices, but cannot enforce it. As per GDPR, the board is
responsible for ultimately enforcing the privacy policy. This is a duty which
cannot be outsourced.
If the privacy policy is not enforced to all projects, we cannot consider our
organisation GDPR compliant. I ask the board to give a recommendation how the
privacy policies worked on in the privacy office (as part of the president
office) should be enforced (or if).
At the moment privacy list is not yet cleared of all open requests, but once
the number of requests goes down, a proposal for the new "mailing list policy"
and also "committer policies" will follow.
Policy-wise, end of summer might be a good time think of the ASF as GDPR
compliant. Implementation wise, it will be difficult to convince all projects
to support the new privacy policy or have the work done. An answer to the
above question about enforcement of the GDPR will definitely help.
-----------------------------------------
Attachment 9: Report from the VP of W3C Relations [Andy Seaborne]
Niklas Merz (niklasmerz@) and Bryan Ellis (erisu@) joined
the WebView Community Group.
These are the first people join the community group and ASF
has now signed the W3C Community Contributor License Agreement
-----------------------------------------
Attachment 10: Report from the Apache Legal Affairs Committee [Roman Shaposhnik]
Past month has been pretty calm. Committee members took good care of resolving
most issues on time. After resolving a handful of LEGAL issues, we are flat at
22 outstanding issues compared to last month.
There hasn't been much else happening aside from us engaging with DLAPiper
around reviewing our by-laws.
Thanks to sebb we've been closing issues around our ECCN and release policies
and processes with a number of INFRA JIRAs and direct patches resulting from
that.
-----------------------------------------
Attachment 11: 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.
Opened a position for a Security Response Program Manager
https://blogs.apache.org/security/entry/position-available-security-response-program
Stats for Apr 2022:
18 [license confusion]
42 [support request/question not security notification]
Security reports: 41 (last months: 47, 67, 71)
9 [site]
6 [airflow]
3 [druid], [httpd]
2 [apisix]
1 [bookkeeper], [camel], [commons], [dolphinscheduler],
[hc], [ignite] [jena], [logging], [nifi], [ofbiz],
[openoffice], [shardingsphere], [shenyu], [spark],
[tapestry], [tika], [tomcat], [xalan]
In total, as of 1st May 2022, we're tracking 91 (last month:
93) open issues across 42 projects, median age 78 (last month:
61) days. 64 of those issues have CVE names assigned.
10 (last month: 11) of these issues, across 7 projects, are older
than 365 days.
-----------------------------------------
Attachment 12: Report from the VP of Jakarta EE Relations [Rob Tompkins]
-----------------------------------------
Attachment A: Report from the Apache Ant Project [Jan Materne]
-----------------------------------------
Attachment B: Report from the Apache BookKeeper Project [Sijie Guo]
## Description:
The mission of BookKeeper is the creation and maintenance of software related
to Replicated log service which can be used to build replicated state machines
## Issues:
There is no particular issue relevant for the board. The project is cutting
releases, bug fixes and new features are being contributed.
## Membership Data:
Apache BookKeeper was founded 2014-11-18 (7 years ago)
There are currently 28 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:5.
Community changes, past quarter:
- Andrey Yegorov was added to the PMC on 2022-03-17
- Nicolò Boschi was added as committer on 2022-03-29
- ZhangJian He was added as committer on 2022-05-04
## Project Activity:
We cut a new feature release: Apache BookKeeper 4.15.0
## Community Health:
There is activity on GitHub, with new issues, users that ask for questions and
new patches. Slack is also quite active. The activity in the ML is quite low.
-----------------------------------------
Attachment C: Report from the Apache Brooklyn Project [Geoff Macartney]
## Description:
The mission of Apache Brooklyn is the creation and maintenance of software
related to a software framework for modeling, monitoring and managing cloud
applications through autonomic blueprints.
## Issues:
- There are no issues requiring board attention at this time.
## Membership Data:
Apache Brooklyn was founded 2015-11-18 (6 years ago) There are currently 20
committers and 19 PMC members in this project. The Committer-to-PMC ratio is
roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Iuliana Cosmina on 2021-06-04.
- Mykola Mandra was added as committer on 2022-03-08. We are happy to welcome
Mykoka as a Brooklyn committer.
## Project Activity:
- The last major Brooklyn release was 1.0.0, released on 3rd March 2020.
- There has been a steady turnover of commits to the project over this quarter.
## Community Health:
Discussions about issues and directions for the project continue
on the mailing lists.
-----------------------------------------
Attachment D: 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:
- We have released 1.5.8 in July 2019. We haven't had any activity since.
This report is essentially the same as what we filed for a while now.
I am starting a retirement discussion on the private list.
## Health report:
- We still have a small PMC presence of 3 active members still able
to vote releases.
## 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 10 committers.
- Olle Jonsson was added as a committer on Wed Dec 12 2018
## Releases:
- Last release was 1.5.8 on July 14th 2019
-----------------------------------------
Attachment E: Report from the Apache Cassandra Project [Michael Semb Wever]
## Description:
Apache Cassandra software is a highly scalable second-generation distributed
database.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Cassandra was founded 2010-02-16 (12 years ago) There are currently 70
committers and 36 PMC members in this project. The Committer-to-PMC ratio is
roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Dinesh Joshi on 2021-05-19.
- Anthony Grasso was added as committer on 2022-02-17
- Alex Sorokoumov was added as committer on 2022-03-21
- Erick Ramirez was added as committer on 2022-02-11
- Lorina Poland was added as committer on 2022-02-17
Anthony, Erick, and Lorina were contributors to the website and docs. Their
inclusion as committers came as a result of the PMC agreeing to broaden the
scope and trust to who could be committers.
## Project Activity:
The cassandra-4.1 release branch was created on the 1st May. The community has
held its agreement to a yearly major release cadence.
Some statistics on the last years worth of work are:
- 89 unique contributors
- 498 jira issues (43% bugs)
- over 3k files touched
- over 65k added LOC, >310k deleted LOC
The community will now maintain four release branches: 3.0, 3.11, 4.0, 4.1;
over the next year and then (next May) will drop maintenance of both the 3.0
and 3.11 branches.
Recent releases:
4.0.3 was released on 2022-02-17.
3.0.26 was released on 2022-02-11.
3.11.12 was released on 2022-02-11.
New release 4.0.4, 3.11.13, 3.0.27 are currently being voted on.
An interview with GigaOm was recently done, it has not yet been published.
## Community Health:
Keeping a stable trunk remains a challenge. Test failures on 4.0 remain low
(single-digit) and serve as a control test that the CI infrastructure is
working (ci-cassandra.a.o still suffers high saturation and on occasion full
disks). While in trunk (4.1) over the past year the failures have increased
and are typically collateral damage from poorly written past tests and/or
unforeseen setup/teardown requirements. These failures need to be address
before any releases are cut off the 4.1 branch. The number of tests in trunk
has increased significantly, with a 30% increase in test LOC. The community
has introduced a build lead role that rotates every week, to keep track of
failures and CI infra, ensuring test failures are associated to a jira
ticket. This work is facilitated with the use of the Butler tool/website.
Community blog posts and changelog articles continue to come out on a regular
basis, thanks to Chris Thornett, Diogenese Topper and Erick Ramirez. Efforts
are also underway around coordinating and pushing marketing efforts. And a
number of folk are organising the Cassandra track at the ACNA, the number of
submissions remain low and more effort will be required to get the word out.
Cassandra project status updates are emailed regularly to dev@, these are
worth reading for a more detailed view on current state of affairs in the
project.
https://lists.apache.org/list?dev@cassandra.apache.org:lte=2y:%22Cassandra%20project%22%20%22status%20update%22
-----------------------------------------
Attachment F: Report from the Apache Clerezza Project [Hasan Hasan]
-----------------------------------------
Attachment G: Report from the Apache Cocoon Project [Cédric Damioli]
## Description:
The mission of Cocoon is the creation and maintenance of software related to
Web development framework: separation of concerns, component-based
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Cocoon was founded 2003-01-22 (19 years ago)
There are currently 79 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- No new PMC members. Last addition was Javier Puerto on 2012-07-06.
- No new committers were added.
## Project Activity:
2.1.13 was released on 2020-07-29
2.1.12 was released on 2013-03-14
## Community Health:
The project is in maintenance mode.
As usual, low but not null activity on both user and dev lists.
-----------------------------------------
Attachment H: Report from the Apache Community Development Project [Swapnil Mane]
## Description:
The mission of Community Development is the creation and maintenance of
software related to Resources to help people become involved with Apache
projects
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Community Development was founded 2009-11-01 (13 years ago)
There are currently 41 committers and 36 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- Willem Ning Jiang was added to the PMC on 2022-02-22
- No new committers. Last addition was Ted Liu on 2021-10-18.
## Project Activity:
ALC
We had various good activities from the ALC Chapters.
ALC Indore organized the first in-person event for the year
(almost after 1.5 years) on the topic 'Open Source and ASF Awareness' and had
~50 participants in the event.
ALC Beijing worked on ApacheCon Asia with ALC Shenzhen
and worked on setting up track chairs, website, and calling for presentations.
ALC Shenzhen helped and guided Apache projects (RocketMQ, EventMesh, Inlong,
Linkis, Shenyu, and KVRocks) to prepare meetups, on GSoC front, and
also guided some incubating projects regarding board report.
GSoC
Our application as mentoring organization is accepted this year also.
We have 74 mentors and received 112 proposals from people who are interested
in contributing to Apache projects.
Currently, our mentors are reviewing these proposals and ranking them.
ApacheCon NA
Announcements have been made for ApacheCon NA in New Orleans.
Community development will provide support for the event
and promote it and coordinate in the booth to help attendees.
FOSS Backstage
Various members from our Apache Community were the part of
FOSS Backstage [1] Program Committee and we had a good presence in the event
and some members also delivered the talk at the conference.
Other
We fixed some typos and improved the statements on the website,
thanks to Andrew Wetmore, who submitted various pull requests related to this.
We also had various discussions (some are still in conversation) on topics like
alternative communication channels for our communities [2].
And Effective ways of getting individuals funded to work on ASF projects [3].
[1] https://foss-backstage.de/home/program/#
[2] https://s.apache.org/gekgl
[3] https://s.apache.org/axlp7
## Community Health:
Our dev mailing list had seen increased traffic as compared
to the past quarter (621 emails compared to 194 in the past quarter).
The majority of traffic rise is because of GSoC discussions and
activities related to it in Jira. Various mentors and students
contacted us on the mailing list for their queries.
-----------------------------------------
Attachment I: Report from the Apache CouchDB Project [Jan Lehnardt]
-----------------------------------------
Attachment J: Report from the Apache Creadur Project [Philipp Ottlinger]
## Description:
The mission of Creadur is the creation and maintenance of software related to
Comprehension and auditing of software distributions
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Creadur was founded 2012-04-18 (10 years ago)
There are currently 11 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Karl Heinz Marbaise on 2016-08-30.
- No new committers. Last addition was Karl Heinz Marbaise on 2016-08-30.
## Project Activity:
Work continues to release 0.14 (planned for end of May 2022).
Recent releases:
- Apache Rat 0.13 was released on 2018-10-13.
- Apache Rat 0.12 was released on 2016-06-09.
- 0.11 was released on 2014-08-21.
## Community Health:
Activity remains steady but slow.
Currently work is going on to release 0.14.
I started to sort out the Jira issues to prepare the release.
There's some interest to get a new release of RAT due to some Maven changes.
-dev@creadur.apache.org had a 115% increase in traffic in the past quarter
(196 emails compared to 91)
-6 issues opened in JIRA, past quarter (-14% change)
-9 issues closed in JIRA, past quarter (50% increase)
-66 commits in the past quarter (-42% change)
-4 code contributors in the past quarter (33% increase)
-41 PRs opened on GitHub, past quarter (-16% change)
-42 PRs closed on GitHub, past quarter (-33% change)
-----------------------------------------
Attachment K: Report from the Apache DataSketches Project [Lee Rhodes]
## Description:
The mission of Apache DataSketches is the creation and maintenance of software
related to an open source, high-performance library of streaming algorithms
commonly called "sketches" in the data sciences. Sketches are small, stateful
programs that process massive data as a stream and can provide approximate
answers, with mathematical guarantees, to computationally difficult queries
orders-of-magnitude faster than traditional, exact methods
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache DataSketches was founded 2020-12-15 (a year ago)
There are currently 16 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
Community changes, past quarter:
- No new PMC members. Last addition was David Cromberge on 2021-09-22.
- Will Lauer was added as committer on 2022-03-07
## Project Activity:
Releases since last Report (Feb, 2022):
Apr 27, 2022: Released Java Core 3.2.0
Mar 3, 2022: Released Java Hive Adaptor 1.2.0
Feb 17, 2022: Released Java Pig Adaptor 1.1.0
Our recent research work is now published on arXiv.org:
[(Nearly) All Cardinality Estimators Are Differentially
Private](https://arxiv.org/pdf/2203.15400.pdf).
It is also being submitted to some major journals for publication.
## Community Health:
The DataSketches project is healthy. Most of our interactions with users are
through GitHub or through Slack, both of which are easier to use and more
interactive than the dev@ list. So the decrease in dev@ usage is
understandable. But on the whole, the activity on the DataSketches project is
growing.
-----------------------------------------
Attachment L: Report from the Apache DeltaSpike Project [Mark Struberg]
-----------------------------------------
Attachment M: Report from the Apache Drill Project [Charles Givre]
## Description:
The mission of Drill is the creation and maintenance of software related to
Schema-free SQL Query Engine for Apache Hadoop, NoSQL and Cloud Storage
## Issues:
No significant issues to report.
## Membership Data:
Apache Drill was founded 2014-11-18 (7 years ago)
There are currently 61 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was James Turton on 2022-01-23.
- Tengfei Wang was added as committer on 2022-02-22
## Project Activity:
The Drill project released a bug fix release on May 16, 2022. The bug fix
release deals with a number of critical CVEs. Release notes will be published
shortly.
* 1.20.1 was released on 2022-05-16.
* 1.20.0 was released on 2022-02-25.
* 1.19.0 was released on 2021-06-10.
Conversations continue about Drill 2.0. We have merged a very significant
improvement which we are calling user translation. Currently, Drill can
impersonate a user for file systems, however for connections to data sources
which do not have the concept of user impersonation. For instance, relational
databases generally require usernames and passwords. Prior to these mods
Drill would only allow one set of shared credentials for these plugins.
With user translation, users must supply their own individual credentials
for all plugins. This option is configurable for each plugin, so users
can still use a shared user or user translation.
Another area of ongoing work for Drill 2.0 is to eliminate the need for
Drill to maintain our own fork of Calcite. The unfortunate result of this
has been that Drill is stuck on a version of Calcite that is several years old
and not benefiting from all the work that is going on in the Calcite community.
This is ongoing work.
## Community Health:
The Drill community health is strong. What isn't reflected in the metrics
below are the complexity of some of the pull requests which were merged,
particularly those around access controls.
* dev@drill.apache.org had a 80% increase in traffic in the past quarter
(1147 emails compared to 635)
* issues@drill.apache.org had a 79% increase in traffic in the past quarter
(1033 emails compared to 576)
* 82 issues opened in JIRA, past quarter (-14% change)
* 37 issues closed in JIRA, past quarter (-59% change)
* 113 commits in the past quarter (-16% change)
* 20 code contributors in the past quarter (-4% change)
* 83 PRs opened on GitHub, past quarter (-3% change)
* 81 PRs closed on GitHub, past quarter (-8% change)
* 3 issues opened on GitHub, past quarter (-80% change)
* 4 issues closed on GitHub, past quarter (-60% change)
* 375 users on the Apache Drill slack channel.
-----------------------------------------
Attachment N: Report from the Apache Druid Project [Gian Merlino]
## Description
Apache Druid is a high performance real-time analytics database. It is
designed for workflows where low-latency query and ingest are the main
requirements. It implements ingestion, storage, and querying subsystems. Users
interface with Druid through built-in SQL and JSON APIs, as well as
third-party applications.
Druid has an extensive web of connections with other Apache projects: Calcite
for SQL planning, Curator and ZooKeeper for coordination, Kafka and Hadoop as
data sources, Avro, ORC, or Parquet as supported data input formats, and
DataSketches for scalable approximate algorithms. Druid can also be used as a
data source by Superset.
## Issues
There are no issues requiring board attention at this time.
## Activity
Our last major release was Druid 0.22.0, which contained 400 new features,
bug fixes, performance enhancements, documentation improvements, and
additional test coverage from 73 contributors.
A Helm chart for Druid was contributed after the helm/charts repository on
GitHub was deprecated. However, we did not include this in 0.22.0 due to
uncertainty about whether or not we need to perform formal IP clearance for
this contribution. We also intend to exclude the Helm chart from the upcoming
0.23.0 release. We hope to be able to sort this out subsequent to the 0.23.0
release.
Since our last report, there have been 29 community meetups via groups based
in San Francisco, Boston, Houston, Tampa, Denver, Dallas, St. Louis,
Melbourne, Sydney, London, Peterborough (UK), Tel Aviv, Berlin, São Paulo,
Pune, Hong Kong, and Singapore.
The Druid PMC recently granted permission to Imply to organize a sequence of
local, in-person events in 2022 under the brand "Druid Summit On The Road".
More information is available at https://druidsummit.org/.
On January 27 we set up a community Slack workspace at
https://apachedruidworkspace.slack.com/. We decided to create this new
workspace, instead of our existing #druid channel on ASF Slack, because the
official ASF Slack workspace requires an invitation from an existing member in
order to join, which was hampering the ability of members of the public to
join up. The new workspace currently has 350 members, an increase of 200
members since our last report.
## Recent PMC changes
- Currently 32 PMC members.
- No new PMC members since the last report.
- Most recently added PMC member:
- Atul Mohan (2021-10-26)
## Recent committer changes
- Currently 51 committers.
- 1 new committer since the last report:
- Kashif Faraz (2022-01-12)
## Recent releases
- 0.22.1, a security patch release, on 2021-12-11.
- 0.22.0, a major release, on 2021-09-22.
- 0.21.0, a major release, on 2021-04-26.
## Development activity by the numbers
In the last quarter:
- 446 commits from 62 contributors
- 446 pull requests opened
- 444 pull requests merged/closed
- 110 issues opened
- 42 issues closed
-----------------------------------------
Attachment O: Report from the Apache Empire-db Project [Rainer Döbele]
## Description:
Empire-db is a library for dealing with all aspects of storing,
manipulating, retrieving and modelling data in relational database
management systems. As an alternative to traditional OR-Mapping
solutions it provides an SQL centric, no-compromise approach that
uses a Java-Object-Model rather than Mapping Files or Annotations.
## Issues:
There are no issues requiring the boards attention at this time.
## Membership Data:
Apache Empire-db was founded 2012-01-24 (10 years ago)
There are currently 10 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is roughly 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Jan Glaubitz on 2016-07-10.
- Ralf Eichinger was added as committer on 2022-03-15
## Project Activity:
The previous quarter has been one of the most active in recent years
as we have not only completed and released a new major version featuring
a full API rework but also published an all new project website.
## Community Health:
The community has been particularly active during the final approval
of the new version with a lot of activity on all mailing lists and
in Jira. The project has also invited and successfully added a new
committer for his contribution to the project.
-----------------------------------------
Attachment P: Report from the Apache Flume Project [Balázs Donát Bessenyei]
## Description:
The mission of Flume is the creation and maintenance of software related to A
reliable service for efficiently collecting, aggregating, and moving large
amounts of log data
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Flume was founded 2012-06-20 (10 years ago)
There are currently 32 committers and 25 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:7.
Community changes, past quarter:
- Tristan Stevens was added to the PMC on 2022-04-10
- No new committers. Last addition was Tristan Stevens on 2020-01-07.
## Project Activity:
The last release was on January 8, 2019, more than three years ago. A
new one is being actively worked on. We have good hopes we can get it
out this month.
## Community Health:
The community shows low activity, but we still seem to have the
necessary number of people around. We have invited a new committer who
is waiting for approval from his employer.
-----------------------------------------
Attachment Q: 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 recent months.
## Health report:
Activity was lower than usual in recent months. User questions (mostly on
StackOverflow) and new Jira issues are still being answered promptly. The
short term goal is to develop the next micro version. 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.
## PMC changes:
- Currently 7 PMC members.
- No changes since the graduation on 2018-03-21
## Committer base changes:
- Currently 8 committers.
- Last added: Siegfried Goeschl on 2020-01-07
## Releases:
- 2.3.31 was released on 2021-02-16
-----------------------------------------
Attachment R: Report from the Apache Geode Project [Dan Smith]
## Description:
The mission of Apache Geode is the creation and maintenance of software related
to a data management platform that provides real-time, consistent access to
data-intensive applications throughout widely distributed cloud architectures.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Geode was founded 2016-11-15 (7 years ago)
There are currently 115 committers and 54 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Donal Evans on 2021-03-22.
- No new committers. Last addition was Alberto Bustamante on 2021-05-13.
## Project Activity:
The project has issued several patch releases since the last report to fix
stability issues such as a socket leak:
- 1.14.4: 2022-03-18
- 1.13.8: 2022-03-15
- 1.12.9: 2022-03-10
The project has started the stabilization phase of the next minor release,
1.15.0. We previously cut a release branch, reverted to develop, and are back
to stabilizing the release branch again. Some notable features include JDK 17
support, removing ACE from the C++ client, and expiring and re-authenticating
clients with new credentials.
## Community Health:
The project membership hasn't changed much in a last year.
The community is fairly active with several new RFCs, a number of mailing list
discussions, and a couple more live video discussions with community members
in this last quarter.
-----------------------------------------
Attachment S: Report from the Apache Giraph Project [Dionysios Logothetis]
## Description:
The mission of Giraph is the creation and maintenance of software related to
Iterative graph processing system built for high scalability
## Issues:
There are no issues requiring board attention
## Membership Data:
Apache Giraph was founded 2012-05-15 (10 years ago)
There are currently 20 committers and 13 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:4.
Community changes, past quarter:
- No new PMC members. Last addition was Dionysios Logothetis on 2018-04-22.
- No new committers. Last addition was Dionysios Logothetis on 2018-04-23.
## Project Activity:
- Minor changes to make one of the graph algorithms more generic. No other
development otherwise.
## Community Health:
- New activity/interest from people who want to develop algorithms on top of
Giraph.
-----------------------------------------
Attachment T: Report from the Apache Gora Project [Kevin Ratnasekera]
-----------------------------------------
Attachment U: Report from the Apache Griffin Project [William Guo]
-----------------------------------------
Attachment V: Report from the Apache Groovy Project [Paul King]
## Description:
Apache Groovy is responsible for the evolution and maintenance of the
Groovy programming language
## Issues:
No issues requiring board attention at this time.
## Membership Data:
Apache Groovy was founded 2015-11-18 (6 years ago)
There are currently 20 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
- No new PMC members. Last addition was Eric Milles on 2020-11-20.
- No new committers. Last addition was Mikko Värri on 2020-06-03.
## Project Activity:
Our main goal for this quarter was community support related
to our release of Groovy 4.0 from last quarter.
Groovy 4 includes a range of new features including switch expressions,
sealed types, records, language integrated query and much more!
All up there were about 800 new features, improvements and bug fixes
since Groovy 3 which was released just over a year ago.
Typically, moving to a major new Groovy version takes some time. As more
projects have started moving to Groovy 4, we have had more feedback
on some performance and compatibility regressions.
We will continue to work with the community on such issues with Groovy 4
as well as needed bug fixes for earlier Groovy versions.
We have yet to give much attention to our roadmap for Groovy 5 but some
small steps have been taken. We will give that topic additional attention
once activity around the recent Groovy 4 release has settled down.
Recent releases:
4.0.2 was released on 2022-04-22.
4.0.1 was released on 2022-03-08.
3.0.10 was released on 2022-03-06.
2.5.16 was released on 2022-03-05.
## Community Health:
Activity on Github, Jira and the mailing lists has been a little
stronger than last quarter. We anticipate early work for the Groovy
track at ApacheCon to begin this coming quarter.
This quarter on our main branch (which now corresponds to Groovy 5)
of our core repo, 196 commits were contributed from 6 contributors
including 3 non-committer contributors (1 new).
(641 commits by 12 contributors across all branches/repos.)
-----------------------------------------
Attachment W: Report from the Apache Hop Project [Hans Van Akelyen]
## Description:
The mission of Apache Hop is the creation and maintenance of software related
to a platform for data orchestration
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Hop was founded 2021-12-15 (5 months ago)
There are currently 22 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Bart Maertens on 2021-12-15.
- Gabriel Dutra was added as committer on 2022-02-19
- Ricardo Gouvea was added as committer on 2022-02-22
## Project Activity:
latest release: 1.2.0 was released on 2022-03-07
Working towards a next major release. Including a Java 11 upgrade.
It has been a bit more quiet period after busy months.
## Community Health:
In the previous period there has been a bit less activity in number of commits
and PR's. But the complexity and size has grown. Our global reach is slowly
growing and partnerships with other Apache projects is growing
(Beam,Doris,Kafka). By reviving our meetups and spending a bit more time on
our socials we expect to grow further.
-----------------------------------------
Attachment X: Report from the Apache HTTP Server Project [Joe Orton]
## Description:
The mission of HTTP Server is the creation and maintenance of software related
to Apache Web Server (httpd)
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache HTTP Server was founded 1995-02-27 (27 years ago)
There are currently 127 committers and 55 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Giovanni Bechis on 2021-06-11.
## Project Activity:
As in the previous report, this quarter appears to be "business as usual". The
project made a single new release in the quarter, version 2.4.53 being
announced in March from the 2.4 branch. This release again addresses a number
of pending security issues, plus bug fixes and some enhancements backported
from the trunk branch.
A mailing list discussion around moving httpd development to GitHub (with a
PR-based workflow) from Subversion appeared to gain rough consensus but has
not been taken forward (yet).
## Community Health:
Both commit volumes and mailing list were down a little this quarter. The dev@
activity was made up mainly of a technical discussions between committers
around changes landing in trunk, plus the usual debate around the release
candidate tarballs. There was significantly higher activity in Github PRs than
in the previous quarter.
-----------------------------------------
Attachment Y: Report from the Apache HttpComponents Project [Michael Osipov]
## 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.
## Project Activity:
- Active feature developments happens on master (5.2.x) with Java 8
## Community Health:
- Overall the project remains active. Issues and dicussions are
resolved in time.
## Membership Data:
- No new PMC members. Last addition was Ryan Schmitt on 2019-08-28.
- No new committers. Last addition was Carter Kozak on 2020-08-13.
## Releases:
- HttpComponents Client 5.1.2 was released on 2021-12-08
- HttpComponents HttpAsyncClient 5.1.2 was released on 2021-12-13
- HttpComponents Core 4.4.15 was released on 2021-10-20
- HttpComponents Core 5.1.3 GA was released on 2021-12-23
- HttpComponents Core 5.2-beta1 was released on 2022-03-17
-----------------------------------------
Attachment Z: Report from the Apache Ignite Project [Dmitry Pavlov]
## Description:
The mission of Ignite project is the creation and maintenance of software
related to high-performance distributed database engine providing in-memory
and persistent data caching, partitioning, processing, and
querying components.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Ignite was founded 2015-08-19 (7 years ago)
There are currently 70 committers and 36 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
- No new PMC members. Last addition was Kseniya Romanova on 2021-09-08.
- Alexander Lapin was added as committer on 2022-02-09
## Project Activity:
Releases:
- 2.13.0 (latest stable) was released on 2022-04-26
- The latest release includes Apache Calcite-based SQL beta version support
Events:
- Community hosted a virtual Meetup on April 17
- Ignite Summit CFP was closed and schedule is to be published in May on
https://ignite-summit.org/2022-june/
Docs:
- Updating releases documentation was automated using GitHub Actions
## Community Health:
Activity:
- dev list had a 33% decrease in traffic in the past quarter
- All code contributions (commits, PRs, and JIRA tickets) had approx 30%
decrease the past quarter
- The only metrics grown is user list activity 43% increase in traffic
Recognition service:
- Recognition service to track and celebrate non coding contributions is being
hosted on an external site because of technologies this hosting provides
- PMC, PMC Chair and Joe Brockmeier from the ASF branding team - didn't find
any vendor's preferential treatment
- PMC is dicussing more options on how this service could be deployed
-----------------------------------------
Attachment AA: Report from the Apache Impala Project [Jim Apple]
## Description:
The mission of Apache Impala is the creation and maintenance of software
related to a high-performance distributed SQL engine.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Impala was founded 2017-11-14 (4 years ago).
There are currently 61 committers and 35 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Laszlo Gaal on 2022-01-20.
- No new committers. Last addition was Daniel Becker on 2021-12-07.
## Project Activity:
- Improved support for compatibility with Apache projects Iceberg,
ORC, Hive, Ranger, Parquet, Thrift, and Kudu
- Many fixes for flaky tests
- Improved support for materialized views
- Upgraded Spring past three CVEs
- Upgraded other packages past other CVEs
- Numerous performance improvements, including some queries improved
by 50% or more
## Community Health:
reviews@ is the best gauge of Impala community activity. There were
2532 emails to reviews@ in the last three months; Impala remains a
busy community.
The most recent release was Impala 3.4.1, on 2022-04-07.
-----------------------------------------
Attachment AB: Report from the Apache Incubator Project [Justin Mclean]
# Incubator PMC report for May 2022
The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.
There are currently 38 podlings undergoing incubation. We have had 6 new
IPMC members, 2 members who have stepped down, and 3 new podlings since the
last report. Since the Incubator PMC missed the last few reports, it was
decided to request all podlings to report and summarize the state of all
podlings in a single report. Apologies for the longer report.
## Community
### New IPMC members:
- Wenil Zheng
- Zili Chen
- Liang Zhang
- Calvin Kirs
- Xiaoqiao He
- Xiaorui Wang
### People who left the IPMC:
- Kevin A. McGrail
- Jukka Zitting
## New Podlings
- DevLake
- Kvrocks
- Hugegraph was accepted in January, this is the first report since then
that we have reported.
## Podlings that failed to report, expected next month
- Hivemall
- Livy - pending a retirement discussion
- Pegasus
- PonyMail
- SDAP
## Graduations
- Discussion has started to graduate AGE, MXNet
The board has motions for the following:
- Doris
## Releases
The following releases entered distribution as of
April:
- Apache Tuweni 2.1.0 - 2022-01-22
- Apache ShenYu 2.4.2 - 2022-01-25
- Apache DataLab 2.5.1 - 2022-01-27
- Apache Linkis 1.0.3 - 2022-01-29
- Apache Kyuubi 1.4.1 - 2022-01-31
- Apache YuniKorn 0.12.2 - 2022-02-03
- Apache AGE 0.7.0 - 2022-02-03
- Apache InLong 1.0.0 - 2022-02-19
- Apache Liminal 0.0.4 - 2022-03-06
- Apache SeaTunnel 2.1.0 - 2022-03-20
- Apache Tuweni 2.2.0 - 2022-03-18
- Apache Doris Flink Connector 1.0.3 - 2022-03-19
- Apache Doris Spark Connector 1.0.1 - 2022-03-20
- Apache StreamPipes 0.69.0 - 2022-03-18
- Apache MXNet 2.0.0.beta1.rc1 - 2022-03-21
- Apache Kyuubi 1.5.0 - 2022-03-25
- Apache EventMesh 1.4.0 - 2022-03-31
- Apache AGEViewer 1.0.0 - 2022-04-04
- Apache brpc 1.1.0 - 2022-04-11
- Apache Linkis 1.1.0 - 2022-04-19
- Apache ShenYu 2.4.3 - 2022-04-17
- Apache Sedona 1.2.0 - 2022-04-17
- Apache Doris 1.0.0 - 2022-04-17
- Apaceh Teaclave trustzone-sdk-0.2.0 - 2022-04-18
- Apache Teaclave 0.4.0 - 2022-04-17
- Apache AGE 1.0.0 - 2022-04-20
- Apache Kyuubi 1.5.1 - 2022-04-21
- Apache Toree 0.5.0 - 2022-04-11
- Apache InLong 1.1.0 - 2022-04-24
- Apache Seatunnel 2.1.1 - 2022-04-25
## IP Clearance
- Apache ShardingSphere imported something called Charts
- Apache IoTDB imported a UDF Library
## Legal / Trademarks
## Infrastructure
- A patch was received during this reporting period to upgrade our report
reminders script to Python 3. It will be tested with the next round of
Podling reports.
## Miscellaneous
- A discussion is currently going on about revamping our shepherd
process/responsibilities.
- A discussion is on going about rotating the chair.
## Credits
- John Ament served as Report Manager for this report.
## Table of Contents
[AGE](#age)
[Annotator](#annotator)
[brpc](#brpc)
[Crail](#crail)
[DataLab](#datalab)
[Doris](#doris)
[EventMesh](#eventmesh)
[Flagon](#flagon)
[Heron](#heron)
[HugeGraph](#hugegraph)
[InLong](#inlong)
[Kvrocks](#kvrocks)
[Kyuubi](#kyuubi)
[Liminal](#liminal)
[Linkis](#linkis)
[Marvin-AI](#marvin-ai)
[Milagro](#milagro)
[MXNet](#mxnet)
[Nemo](#nemo)
[NLPCraft](#nlpcraft)
[NuttX](#nuttx)
[PageSpeed](#pagespeed)
[SeaTunnel](#seatunnel)
[Sedona](#sedona)
[ShenYu](#shenyu)
[Spot](#spot)
[StreamPipes](#streampipes)
[Teaclave](#teaclave)
[Toree](#toree)
[Training](#training)
[Tuweni](#tuweni)
[Wayang](#wayang)
--------------------
## AGE
AGE is a multi-model database that enables graph and relational models built
on PostgreSQL.
AGE has been incubating since 2020-04-29.
### Three most important unfinished issues to address before graduating:
There are no issues. The Apache AGE(incubating) project is currently in
incubation graduation process.
### Are there any issues that the IPMC or ASF Board need to be aware of?
There are no issues.
### How has the community developed since the last report?
We added six new committers and two PPMCs.
The two committers(Joe Fagan and Pierre Alexander Voye) submitted ICLA form
and are in process to be registered in the system.
### How has the project developed since the last report?
We released AGE 0.7.0(2022-02-03) and 1.0.0(2022-04-21), AGE Viewer
1.0.0(2022-04-04).
Apache AGE Docker container was made available on Apache Docker Hub.
### 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:
2022-04-21
### When were the last committers or PPMC members elected?
2022-04-21
Joe Fagan as a committer
### Have your mentors been helpful and responsive?
Yes, very much.
### Is the PPMC managing the podling's brand / trademarks?
Yes, PPMC is managing the podling's brand / trademarks.
### Signed-off-by:
- [ ] (age) Kevin Ratnasekera
Comments:
- [ ] (age) Von Gosling
Comments:
- [X] (age) Felix Cheung
Comments:
- [X] (age) Juan Pan
Comments: The data of community looks nice.
### IPMC/Shepherd notes:
--------------------
## Annotator
Annotator provides annotation enabling code for browsers, servers, and
humans.
Annotator has been incubating since 2016-08-30.
### Three most important unfinished issues to address before graduating:
1. Grow the community
2. Add PPMC members and committers
3. Continue making releases
### Are there any issues that the IPMC or ASF Board need to be aware of?
None at this time.
### How has the community developed since the last report?
At the suggestion of community members, the
project kicked off monthly conference calls
for contributors to share progress and users
to share implementation experience. Several
folks attended the first such call.
### How has the project developed since the last report?
Voting has just begun for the next release,
incorporating changes intended to make it
easier to consume the project in browsers.
### 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:
After a period of slow progress and missed
reports, the project is making progress once
again. It will be crucial to convert this
new activity into sustained involvement from
new users and contributors.
### Date of last release:
2021-09-03
### When were the last committers or PPMC members elected?
2018-09-04
### Have your mentors been helpful and responsive?
No issues so far. But it is worth checking
in again to see who is still interested.
### Is the PPMC managing the podling's brand / trademarks?
No known issues at this time.
### Signed-off-by:
- [X] (annotator) Nick Kew
Comments: Easy to miss when the report is buried in the template!
- [ ] (annotator) Tommaso Teofili
Comments:
- [ ] (annotator) Benjamin Young
Comments:
### IPMC/Shepherd notes:
--------------------
## brpc
brpc is an industrial-grade RPC framework for building reliable and high-
performance services.
brpc has been incubating since 2018-11-13.
### Three most important unfinished issues to address before graduating:
1.Regular Apache Release by more release manager
2.Attract more committer and PPMC member
3.Fix Branding issue
### Are there any issues that the IPMC or ASF Board need to be aware of?
No
### How has the community developed since the last report?
we add one PPMC member Wang Weibing from Baidu, and one Committer Liu
Shuai from Baidu also.Also we launched the new website of our project,
using new style, looking much better than old one.
### How has the project developed since the last report?
1.1.0 release has been finished by new release manager Wang Weibing.
### 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:
2022-04-11
### When were the last committers or PPMC members elected?
2022-04-01 Liu Shuai
### Have your mentors been helpful and responsive?
Kevin just decided to end his mentorship in this project due to limited
time. We miss him.
### Is the PPMC managing the podling's brand / trademarks?
I will check it out before next pod report.
### Signed-off-by:
- [ ] (brpc) Kevin A. McGrail
Comments:
- [X] (brpc) Jean-Baptiste Onofré
Comments:
- [ ] (brpc) Von Gosling
Comments:
- [X] (brpc) Juan Pan
Comments: BTW, could we delete the original notice words, e.g., "Are
things falling through the cracks?..."? It's confusing at my first glance,
Thanks. Sorry to hear that Kevin will leave us, but I respect his thoughts.
If it's decided, resignation is supposed to be on our schedule, Thanks.
### IPMC/Shepherd notes:
--------------------
## Crail
Crail is a storage platform for sharing performance critical data in
distributed data processing jobs at very high speed.
Crail has been incubating since 2017-11-01.
### Three most important unfinished issues to address before graduating:
1. More frequent code contributions
2. A steady release process
3. Growing the ecosystem: more committers, more use cases
### Are there any issues that the IPMC or ASF Board need to be aware of?
Visible project activities are very low. No new release since
one year.
### How has the community developed since the last report?
No new committer or known new use cases. We are aware of a proprietary
elasticity extension of Crail, but that code was not (yet?)
officially contributed or reviewed.
### How has the project developed since the last report?
Not much development visible. We started discussion on dev-list
regarding project future, including considering retiring the Crail Podling.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
The project stagnates since mid last year.
### Date of last release:
2021-05-03
### When were the last committers or PPMC members elected?
2021-05-16
### Have your mentors been helpful and responsive?
Our mentors are helpful and always responsive.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [X] (crail) Julian Hyde
Comments: Glad to see a discussion about Crail's future,
even though it's a tough conversation to have. I'll try
to keep up the momentum so that we get to consensus in the
next few weeks.
- [X] (crail) Luciano Resende
Comments:
- [X] (crail) Felix Cheung
Comments:
### IPMC/Shepherd notes:
--------------------
## DataLab
DataLab is a platform for creating self-service, exploratory data science
environments in the cloud using best-of-breed data science tools.
DataLab has been incubating since 2018-08-20.
### Three most important unfinished issues to address before graduating:
1. Finish graduation as a TLP.
2.
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No issues.
### How has the community developed since the last report?
We have a new committer Denys Yankiv and PPMC members
Alina Ignatiuk and Ruslan Kulynych.
### How has the project developed since the last report?
We’ve released DataLab version 2.5.1.
### 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
- [X] Other: working towards next release
### Date of last release:
2022-27-01
### When were the last committers or PPMC members elected?
The last PPMC member was added on March 15, 2022.
### Have your mentors been helpful and responsive?
Yes, our mentors are very helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
There are no known brand and naming issues.
### Signed-off-by:
- [ ] (datalab) P. Taylor Goetz
Comments:
- [ ] (datalab) Henry Saputra
Comments:
- [ ] (datalab) Konstantin I Boudnik
Comments:
- [X] (datalab) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
johndament: This report is very sparse. It appears to be written by a
single member and not discussed on list at all. I can't find any on list
discussion of this report, nor recent on list discussion of the graduation
proposal. I doubt the podling is actually ready to graduate.
--------------------
## 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 unfinished issues to address before graduating:
None
### Are there any issues that the IPMC or ASF Board need to be aware of?
We initiated and passed the graduation vote at IPMC:
https://lists.apache.org/thread/qpbhpwoyclx6vxy3j2wcms4t5v79pgs9
And the Resolution has been send to the ASF Board.
### How has the community developed since the last report?
The contributors has grown up to 300+.
We start using wiki to save some significant proposal for Doris and some
other community issue.
https://cwiki.apache.org/confluence/display/DORIS/Home
### How has the project developed since the last report?
We have released 1.0.0.
### 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:
2022-04-18
### When were the last committers or PPMC members elected?
2022/03/21 New PPMC, Invite committer Zuo Wei to PPMC
2022/03/23 New Committer, Jianliang Qi
2022/03/24 New Committer, Di Wu
2022/03/24 New Committer, Huajian Lan
### Have your mentors been helpful and responsive?
All mentors are very helpful!
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [X] (doris) Willem Ning Jiang
Comments: It's good to see Doris is ready to graduation.
- [ ] (doris) Shao Feng Shi
Comments:
- [ ] (doris) Ming Wen
Comments:
### IPMC/Shepherd notes:
--------------------
## EventMesh
EventMesh is a dynamic cloud-native basic service runtime used to decouple
the application and middleware layer.
EventMesh has been incubating since 2021-02-18.
### Three most important unfinished issues to address before graduating:
1. More frequent code contributions
2. A steady release process
3. Growing the community: more committers, more use cases
### Are there any issues that the IPMC or ASF Board need to be aware of?
N/A
### How has the community developed since the last report?
we have two more use cases in production
we have 20 more contributors,2 new committers and 1 new ppmc member
### How has the project developed since the last report?
we have 2 version released(cloudevents and grpc support)
we have several new features under developing such as
gosdk/workflow/webhook/dashboard/kafka/dledger
### 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:
2022-3-31
### When were the last committers or PPMC members elected?
2022-4-15
### Have your mentors been helpful and responsive?
Mentors were all very nice and helpful.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (eventmesh) Francois Papon
Comments:
- [ ] (eventmesh) Junping Du
Comments:
- [X] (eventmesh) Jean-Baptiste Onofré
Comments:
- [ ] (eventmesh) Justin Mclean
Comments:
- [ ] (eventmesh) Von Gosling
Comments:
### IPMC/Shepherd notes:
--------------------
## Flagon
Flagon is a software tool usability testing platform
Flagon has been incubating since 2016-07-13.
### Three most important unfinished issues to address before graduating:
1. Continue VOTE thread for Graduation on general@incubator
2. Retire STOUT, TAP products via INFRA
3. Move unsubscribed PPMC members to Emeritus
### Are there any issues that the IPMC or ASF Board need to be aware of?
None at this time.
### How has the community developed since the last report?
1. We are coordinating software gift from UMD for Flagon analytics
package (Distill), via CCLA (still under review by UMD for IP release)
2. CCLA will include at least 6 new committers and at least 1 PPMC member
3. Substantive PRs from User Base
### How has the project developed since the last report?
1. UserALE.js 2.3.0 release currently under VOTE on general@incubator
2. Developments on analytical package (Distill) are currently being
tested on fork (awaiting CCLA execution)
### 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:
2021-06-03 Apache UserALE.js 2.2.0
### When were the last committers or PPMC members elected?
2021-03-26 (Gedd Johnson)
### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.
Mentors remain supportive, although some procedural questions RE
graduation actions (see above) have been unanswered
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (flagon) Lewis John McGibbney
Comments:
- [ ] (flagon) David Meikle
Comments:
- [ ] (flagon) Tim Allison
Comments:
- [X] (flagon) Furkan Kamaci
Comments:
### IPMC/Shepherd notes:
--------------------
## Heron
A real-time, distributed, fault-tolerant stream processing engine.
Heron has been incubating since 2017-06-23.
### Three most important unfinished issues to address before graduating:
1. Growing the community, make Heron easier to use
2. Python compatibility issues
3. Improving our release process
### Are there any issues that the IPMC or ASF Board need to be aware of?
n/a
### How has the community developed since the last report?
The current community has stayed consistent and stable.
### How has the project developed since the last report?
There has been lots of work in addressing issues of running Heron in k8s
(move “cloud native”).
### 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:
2021-05-26
### When were the last committers or PPMC members elected?
Saad Ur Rahman, 2021/11/29
### Have your mentors been helpful and responsive?
Yes.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (heron) Jake Farrell
Comments:
- [X] (heron) Julien Le Dem
Comments:
- [ ] (heron) P. Taylor Goetz
Comments:
- [X] (heron) Dave Fisher
Comments:
- [ ] (heron) Ming Wen
Comments:
- [ ] (heron) Kevin Ratnasekera
Comments:
### IPMC/Shepherd notes:
--------------------
## HugeGraph
A large-scale and easy-to-use graph database
HugeGraph has been incubating since 2022-01-23.
### Three most important unfinished issues to address before graduating:
1. Increase diversity contributors.
2. Publish spec-compliant release version.
3. Enhance core product functionality as mentioned in the initial goals.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No issues so far.
### How has the community developed since the last report?
This is the first report.
All HugeGraph sub-projects have more than 50 contributors, and we are
attracting more contributors to the development.
### How has the project developed since the last report?
This is the first report.
We have completed the SGA signing, now we are discussing the trademark
donation, and are going through the approval process.
The donated 5 repositories have been migrated from hugegraph org to apache
org, 7 committers have completed the github account association, they are
granted codebase write permissions, 5 of them have been initialized as PPMC
members.
We solved a series of ci workflow problems for repositories migration. The
official website is currently under construction.
The next step is to make an official announcement, and prepare for the
release version.
### 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:
None (This is the first report)
### When were the last committers or PPMC members elected?
We have just initialized committers or PPMC members on April 28th.
### Have your mentors been helpful and responsive?
Yes, the hugegraph mentors are very helpful.
They guided us through the incubation process, helped solve problems we
encountered, and taught us the apache way.
### Is the PPMC managing the podling's brand / trademarks?
Yes, 3rd parties are respecting and correctly using the podlings name and
brand.
### Signed-off-by:
- [X] (hugegraph) Lidong Dai
Comments:
- [X] (hugegraph) Trista Pan
Comments: Good start for the community!
- [ ] (hugegraph) Xiangdong Huang
Comments:
- [ ] (hugegraph) Yu Li
Comments:
- [X] (hugegraph) Willem Ning Jiang
Comments: bootstrap the project.
### IPMC/Shepherd notes:
--------------------
## InLong
InLong is a one-stop data integration framework that provides automatic,
secure, and reliable data transmission capabilities. InLong supports both
batch and stream data processing at the same time, which offers great power
to build data analysis, modeling, and other real-time applications based on
streaming data.
InLong has been incubating since 2019-11-03.
### Three most important unfinished issues to address before graduating:
1. Gain more active contributors/committers to build a diverse community.
2. Prepare to discuss in the community.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No issues.
### How has the community developed since the last report?
1. 2 new committers and 1 PPMC have voted from different organizations.
2. About 26 new contributors have joined the community (currently: 95).
3. 36+ authors have pushed 720+ commits to master.
4. Add GitHub Discussions Board to communicate with contributors and users.
5. Attend the Pulsar Summit and share a topic about InLong.
6. Attend the DataFun Summit and share a topic about InLong.
7. Prepare a joint meetup with the SeaTunnel community.
### How has the project developed since the last report?
1. Release 1.0.0 on Feb 17, 2022
2. Release 1.1.0 on Apr 24, 2022
### 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:
2022-04-24
### When were the last committers or PPMC members elected?
1. committer, bluewang was elected as committer on 2022-04-22
2. PPMC, healchow was elected as PPMC on 2022-03-30
### Have your mentors been helpful and responsive?
Yes, our mentors are very helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
Yes, all good here.
### Signed-off-by:
- [ ] (inlong) Junping Du
Comments:
- [ ] (inlong) Justin Mclean
Comments:
- [ ] (inlong) Sijie Guo
Comments:
- [ ] (inlong) Zhijie Shen
Comments:
- [X] (inlong) Jean-Baptiste Onofré
Comments: I think InLong is not so far from graduation. Worth to
start the maturity assesment as see if we can move forward on the
graduation.
### IPMC/Shepherd notes:
--------------------
## Kvrocks
Kvrocks is a distributed key-value NoSQL database, supporting the rich data
structure, Redis like protocol, disk storage, stored procedures
using Lua script, etc.
Kvrocks has been incubating since 2022-04-23.
### Three most important unfinished issues to address before graduating:
1. Bootstrap project, prepare first Kvrocks release at Apache
2. Prepare Apache Kvrocks website
3. Promote the project and grow user and dev community
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
This is our first report. We are preparing the Kvrocks website,
blog posts and talks to promote Kvrocks and grow the user and dev
communities.
### How has the project developed since the last report?
This is our first report. We are preparing all resources: git/github,
mailing list, etc.
We are working on code cleanup before code donation and also SGA.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [ ] Working towards first release
- [ ] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
No release yet
### When were the last committers or PPMC members elected?
2022-04-23
### Have your mentors been helpful and responsive?
Mentors are helping to bootstrap.
### Is the PPMC managing the podling's brand / trademarks?
We are starting ;)
### Signed-off-by:
- [X] (kvrocks) Jean-Baptiste Onofre
Comments: podling is just bootstrapping, but good start !
- [ ] (kvrocks) Xiaoqiao He
Comments:
- [X] (kvrocks) tison
Comments:
- [ ] (kvrocks) Von Gosling
Comments:
- [X] (kvrocks) Liang Chen
Comments: Podling just started, already finished some infra creation.
### IPMC/Shepherd notes:
--------------------
## Kyuubi
Kyuubi is a distributed multi-tenant Thrift JDBC/ODBC server for
large-scale data management, processing, and analytics, built on top of
Apache Spark and designed to support more engines.
Kyuubi has been incubating since 2021-06-21.
### Three most important unfinished issues to address before graduating:
1. Gain more active contributors/committers to build a diverse community
2. Make Apache releases regularly and keep the quality for all releases
3. Improve project structure and documentation
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
- New committers: Nicholas Jiang & Fu Chen
- Hosted a section on DataFun Sumit 2022 on April 23, gave three talks by
Cheng Pan, Xiduo You and Yaodong Zhang
- Organized one online meetup with Apache SeaTunnel community, gave two
talks by Vino Yang, Xinkai Lin and Fei Wang
- 9 new contributors join code contribution. There are currently 74
contributors and 13 committers.
### How has the project developed since the last report?
- Apache Kyuubi(Incubating) 1.5.0-incubating released
- Apache Kyuubi(Incubating) 1.5.1-incubating released
### 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:
- 2022-04-21
### When were the last committers or PPMC members elected?
- 2021-12-15 Yang Hua
- 2021-12-15 Dongdong Hong
- 2022-03-29 Nicholas Jiang
- 2022-03-29 Fu Cheng
### Have your mentors been helpful and responsive?
- Mentors are helpful and always responsive.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [X] (kyuubi) Willem Ning Jiang
Comments: Good to see we are keeping adding PPMC members.
- [ ] (kyuubi) Jeff Zhang
Comments:
- [ ] (kyuubi) Duo Zhang
Comments:
- [X] (kyuubi) Akira Ajisaka
Comments: Looking https://s.apache.org/dqgcn, the pace of contributions is
increasing. Great.
### IPMC/Shepherd notes:
--------------------
## Liminal
Apache Liminal is an end-to-end platform for data engineers and scientists,
allowing them to build, train and deploy machine learning models in a robust
and agile way.
Liminal has been incubating since 2020-05-23.
### Three most important unfinished issues to address before graduating:
1. Grow developers community.
2. Adoption of the project by a few companies.
3. More features and integrations with eco-system projects.
### Are there any issues that the IPMC or ASF Board need to be aware of?
NA
### How has the community developed since the last report?
We have presented Liminal to few companies and received important feedback.
We have 2 new official committers. We are also starting a PoC with one
company.
### How has the project developed since the last report?
We have released version 0.0.4, introducing Airflow 2.0 support +
extensibility API.
### 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:
2022-03-10
### When were the last committers or PPMC members elected?
2022-04-06
### Have your mentors been helpful and responsive?
They have been very responsive and helpful.
### Is the PPMC managing the podling's brand / trademarks?
NA
### Signed-off-by:
- [X] (liminal) Jean-Baptiste Onofré
Comments:
- [ ] (liminal) Henry Saputra
Comments:
- [ ] (liminal) Uma Maheswara Rao G
Comments:
- [X] (liminal) Davor Bonaci
Comments: The podling is moving forward; community building is the key
next step.
- [ ] (liminal) Liang Chen
Comments:
### IPMC/Shepherd notes:
--------------------
## Linkis
Apache Linkis is a computation middleware project, which decouples the upper
applications and the underlying data engines, provides standardized
interfaces (REST, JDBC, WebSocket etc.) to easily connect to various
underlying engines (Spark, Presto, Flink, etc.).
Linkis has been incubating since 2021-08-02.
### Three most important unfinished issues to address before graduating:
1. Improve project infrastructure(CI, CD, test automation, etc.) and
structure to facilitate community collaboration
2. Make Apache releases regularly and keep the quality for all releases
3. Gain more active contributors and committers to build a diverse
community
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
* 7 contributors increased.There are currently 90 contributors and 16
committers.
* 115 issues and 116 pull requests since last report(2022/03/29).(
issues:total/closed/open 1111/803/308, pr: total/closed/open 923/893/30)
### How has the project developed since the last report?
* We’ve released Linkis version 1.1.0(supports datasource and metadata
source query services to supports new features of query functions for
different types of metadata)
* Version 1.1.1 under development(provides multiple versions of UDF and
UDF material storage to BML, tasks support the collection of Yarn queue
resource usage statistics), progress 60%.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2022-04-15
### When were the last committers or PPMC members elected?
2022-02-24 New Committer: Chen Xia
### Have your mentors been helpful and responsive?
Our mentors have been helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
The PPMC manages the podling's brand / trademarks.
### Signed-off-by:
- [ ] (linkis) Duo Zhang
Comments:
- [X] (linkis) Lidong Dai
Comments:
- [ ] (linkis) Shaofeng Shi
Comments:
- [ ] (linkis) Saisai Shao
Comments:
- [ ] (linkis) Junping Du
Comments:
### 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 unfinished issues to address before graduating:
1. Increase activity from current contributors and community.
2. Release a new architecture.
3. Documentation and new community roadmap.
### Are there any issues that the IPMC or ASF Board need to be aware of?
No.
### How has the community developed since the last report?
We now have 3 new interns that are actively contributing with the new
design document, and will continue to contribute in coding tasks.
### How has the project developed since the last report?
We are preparing for a new release of the features added before the
architecture change. The main work was in the design document that has
ideas to modernize Apache Marvin-AI's architecture.
### How would you assess the podling's maturity?
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2019-07-18
### When were the last committers or PPMC members elected?
2021-09-17 - Lucas Cardoso Silva was approved as a committer.
### Have your mentors been helpful and responsive?
Yes.
### Is the PPMC managing the podling's brand / trademarks?
Yes.
### Signed-off-by:
- [ ] (marvin-ai) Luciano Resende
Comments:
- [ ] (marvin-ai) William Colen
Comments:
### IPMC/Shepherd notes:
--------------------
## Milagro
Milagro is core security infrastructure and crypto libraries for
decentralized networks and distributed systems.
Milagro has been incubating since 2015-12-21.
### Three most important unfinished issues to address before graduating:
1. Continue to build relevant and useful crypto libraries and applications
for decentralized networks in order to grow the ecosystem of users and
contributors to the project.
2. Continue to improve compliance with the Apache Way. In particular to
update the Milagro website and other project sites (e.g. Whimsy)
in accordance with Apache policies.
3. Further releases to increase the scope of the Milagro project, extend
the capability of existing releases and to demonstrate improved
compliance with the Apache Way.
### Are there any issues that the IPMC or ASF Board need to be aware of?
Administrative tasks are still outstanding due to members' other
commitments and the pandemic. These include in particular, a PPMC
meeting to discuss the project roadmap needs to be arranged,
confirmation that the project's Whimsy, Clutch, SVN, Confluence
& Committers pages are all current, and the code signing keys needs
countersigning. Investigations into a redirect on Milagro's home
page and an XSS vulnerability on the Decentralized Trust Authority's
Swagger page are ongoing.
### How has the community developed since the last report?
Qredo, one of the main contributors to the projects have just hired an
Open Source Manager one of whose roles will be to reinvigorate and
support the Milagro project and in particular to assist with the first
Apache release of a Multi-Party Computation library.
Discussions around how to incorporate them into the PPMC to follow shortly.
### How has the project developed since the last report?
No change.
### 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:
2020-02-10
### When were the last committers or PPMC members elected?
February 2020
### Have your mentors been helpful and responsive?
No issues.
### Is the PPMC managing the podling's brand / trademarks?
No known issues, but further investigation is still required by the
Milagro community.
### Signed-off-by:
- [X] (milagro) Nick Kew
Comments: Qredo hiring a new Open Source Manager may very well be
good for the
project, but could risk blurring lines between apache and
the company.
- [X] (milagro) Jean-Frederic Clere
Comments:
### IPMC/Shepherd notes:
--------------------
## MXNet
A Flexible and Efficient Library for Deep Learning
MXNet has been incubating since 2017-01-23.
### Three most important unfinished issues to address before graduating:
1. Complete general@incubator discussion
### Are there any issues that the IPMC or ASF Board need to be aware of?
We are currently
[discussing](https://lists.apache.org/thread/3rxzjcmo2y457y6r8ohz1j4qv49joyo
6) graduation in the general@incubator list after the community discussed
and voted.
### How has the community developed since the last report?
* The number of GitHub contributors is the same, currently 870
* Active blogs and social media presence
* Medium (https://medium.com/apache-mxnet) w/ 2.1k followers (+0%)
* Active video channels
* YouTube channel (https://www.youtube.com/apachemxnet) w/ 1.57k
subscribers (+0.6% since last report)
* Chinese YouTube channel
(https://www.youtube.com/channel/UCjeLwTKPMlDt2segkZzw2ZQ) w/ 7.23k
subscribers (+0.3%)
### How has the project developed since the last report?
1. Community
[discussed](https://lists.apache.org/thread/l9h2qgb2vqs2y0cm46wh83sgomr9w190
) and
[voted](https://lists.apache.org/thread/py1nw6whov78sch5kkm1gcg7cv3zb2sv)
on graduating to a Apache Top Level Project
2. Apache MXNet (incubating) 1.9.1 RC0 created, currently undergoing dev
community vote to release.
### 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:
2022-03-21
### When were the last committers or PPMC members elected?
2022-04-25
### Have your mentors been helpful and responsive?
Yes.
### Is the PPMC managing the podling's brand / trademarks?
Yes. From past brand usage review for MXNet third-party distributions, we
found several listings on AWS marketplace that needed update. The PPMC
reached out to the publishers of these listings for correction and fixed
them.
### Signed-off-by:
- [ ] (mxnet) Markus Weimer
Comments:
- [ ] (mxnet) Bob Paulin
Comments:
- [ ] (mxnet) Jason Dai
Comments:
- [X] (mxnet) Furkan Kamaci
Comments:
- [X] (mxnet) Zhenxu Ke
Comments:
### IPMC/Shepherd notes:
--------------------
## Nemo
Nemo is a data processing system to flexibly control the runtime behaviors
of a job to adapt to varying deployment characteristics.
Nemo has been incubating since 2018-02-04.
### Three most important unfinished issues to address before graduating:
1. Address a few remaining items in the Apache Project Maturity model
2. Grow the community
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
* Accepting GSoC students to contribute to Nemo
### How has the project developed since the last report?
* Updated library versions
* Added fault tolerance for stream operators
* Added latency measurement improvement for stream
* Added automatic stream input rate throttling
* Added new stream workload examples
### 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:
2020-12-07
### When were the last committers or PPMC members elected?
September 28, 2021
### Have your mentors been helpful and responsive?
Our mentors have been helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
The PPMC manages the podling's brand / trademarks.
### Signed-off-by:
- [ ] (nemo) Hyunsik Choi
Comments:
- [X] (nemo) Byung-Gon Chun
Comments:
- [X] (nemo) Jean-Baptiste Onofré
Comments:
- [X] (nemo) Markus Weimer
Comments:
### IPMC/Shepherd notes:
--------------------
## NLPCraft
A Java API for NLU applications
NLPCraft has been incubating since 2020-02-13.
### Three most important unfinished issues to address before graduating:
1. Comunity growth.
2. Releasing a stable 1.0 version.
3.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
Community development has seemingly stalled in the last 4-5 months. The
main reason is probably due to core committers engaged in a deep
refactoring of the project.
### How has the project developed since the last report?
The project is undergoing a significant re-architecture based on the
initial user feedback. This work is focused primarily on simplification and
narrowing the scope of the project.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2021-7-30
### When were the last committers or PPMC members elected?
August of 2021.
### Have your mentors been helpful and responsive?
No issues with mentors to report.
### Is the PPMC managing the podling's brand / trademarks?
No issues to report.
### Signed-off-by:
- [ ] (nlpcraft) Roman Shaposhnik
Comments:
- [X] (nlpcraft) Furkan Kamaci
Comments:
- [ ] (nlpcraft) Evans Ye
Comments:
- [X] (nlpcraft) Paul King
Comments:
- [ ] (nlpcraft) Konstantin I Boudnik
Comments:
- [X] (nlpcraft) Dave Fisher
Comments:
### IPMC/Shepherd notes:
johndament: Releasing a 1.0 should not be a requirement to graduate. If
the podling understands the release process, that is enough.
--------------------
## NuttX
NuttX is a mature, real-time embedded operating system (RTOS).
NuttX has been incubating since 2019-12-09.
### Three most important unfinished issues to address before graduating:
1. Clear any potential infringing use of the NuttX trademark
2. Achieve a non-WIP Disclaimer release under Apache
3. Continue to grow the community with people from different background
### Are there any issues that the IPMC or ASF Board need to be aware of?
During our previous month report (April 2022), we submitted our first
non-WIP-DISCLAIMER release candidate to the IPMC for a vote. One of our
mentors identified several additional items that should be listed in
LICENSE. This is currently being addressed and we hope to submit a new
release candidate for IPMC vote soon. If the vote passes, we will make
our first non-WIP-DISCLAIMER release since joining the ASF Incubator
and the project hopes to apply for graduation to TLP status shortly
after that. Throughout this process, we would appreciate any and all
helpful feedback that will assist us in reaching this important
milestone and would like to express our sincere gratitude for all the
help we've received so far.
### How has the community developed since the last report?
* Virtually all communications have moved from old venues to
dev@nuttx.apache.org. The dev list contains 253 subscribers
and is the home of most development discussions and user
questions.
* GitHub's PRs and Issues also have their own discussions.
* We are seeing new contributors to the project through GitHub.
* We have 5 mentors, 17 PPMC members, and 26 non-PPMC committers.
### How has the project developed since the last report?
* The WIP-DISCLAIMER has been removed from the nuttx and apps
repositories pending NuttX-10.3, which we expect will be our
first non-disclaimer release.
* NuttX-10.2 was released on November 23, 2021.
* Many technical improvements, bug fixes, and new architectures
have been collaborated and work continues with several pull
requests merged per day.
* We have listened to the valuable feedback received during our
previous releases and continue to improve our documentation. This
can be found at https://nuttx.apache.org/docs/latest/.
### 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:
NuttX-10.2.0 was released on 2022-11-23.
NuttX-10.3.0 is currently pending IPMC voting.
### When were the last committers or PPMC members elected?
Last elected PPMC: 2021-05-08
Last committer added: 2021-12-27
### Have your mentors been helpful and responsive?
Mentors are helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
Podling name was approved on May 17th 2020: https://s.apache.org/4hfzx
### Signed-off-by:
- [ ] (nuttx) Duo Zhang
Comments:
- [ ] (nuttx) Junping Du
Comments:
- [X] (nuttx) Justin Mclean
Comments:
- [ ] (nuttx) Mohammad Asif Siddiqui
Comments:
- [ ] (nuttx) Flavio Paiva Junqueira
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 unfinished issues to address before graduating:
1. Grow the number of active developers
### Are there any issues that the IPMC or ASF Board need to be aware of?
While there is a healthy user base, the number of active developers remains
persistently low.
This seems to be a hard to address challenge.
### How has the community developed since the last report?
Mailing lists and git issues are active. The number of active developers is
unchanged.
### How has the project developed since the last report?
Minor activity.
### 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:
The week of May 11th, 2020
### When were the last committers or PPMC members elected?
May 27 2019 (Longinos Ferrando, elected as both committer and PMC member)
### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.
### Is the PPMC managing the podling's brand / trademarks?
As far as we know the brand is respected by third parties.
### Signed-off-by:
- [ ] (pagespeed) Leif Hedstrom
Comments:
- [X] (pagespeed) Nick Kew
Comments: One mentor having just stepped down, it's encouraging
that a new mentor has stepped up!
### IPMC/Shepherd notes:
--------------------
## SeaTunnel
SeaTunnel is a very easy-to-use ultra-high-performance distributed data
integration platform that supports real-time synchronization of massive
data.
SeaTunnel has been incubating since 2021-12-09.
### Three most important unfinished issues to address before graduating:
1.Keep Apache versions released regularly and ensure the quality of
all releases.
2.Attract more active contributors and committers to build a diverse
community.
3.Improve features and documentation.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
The community ushers in 10 new contributors, bringing the total number to
70
now.
60+ pull requests have been merged since SeaTunnel entered the last report.
We will be hosting a meetup with InLong (Incubating) on 5.14 2022, in which
the community contributors and users will share their stories about
application practices or open-source contributions.
### How has the project developed since the last report?
The community contributors are continuously working on 2.0 features,
devoting themselves to new architecture design.
### 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:
27th Apr 2022
### When were the last committers or PPMC members elected?
Shiming Zhang as a committer on Mar 21, 2022.
### Have your mentors been helpful and responsive?
Yes, always responsive and helpful.
They gave a lot of advice on building the first version.
### Is the PPMC managing the podling's brand / trademarks?
No known issues, but further investigation is still required by the
SeaTunnel community.
### Signed-off-by:
- [X] (seatunnel) Zhenxu Ke
Comments:
- [X] (seatunnel) William-GuoWei
Comments:
- [X] (seatunnel) Lidong Dai
Comments:
- [X] (seatunnel) Ted Liu
Comments:
- [ ] (seatunnel) Kevin Ratnasekera
Comments:
- [X] (seatunnel) JB Onofré
Comments:
- [ ] (seatunnel) Willem Jiang
Comments:
### IPMC/Shepherd notes:
--------------------
## Sedona
Sedona is a big geospatial data processing engine. It provides an easy to
use APIs for spatial data scientists to manage, wrangle, and process
geospatial data.
Sedona has been incubating since 2020-07-19.
### Three most important unfinished issues to address before graduating:
1. Self-assessment for graduation
2. More contributors
3. More release managers
### Are there any issues that the IPMC or ASF Board need to be aware of?
All good
### How has the community developed since the last report?
The monthly downloads have reached record high, around 500K downloads per
month
### How has the project developed since the last report?
All good here. We received lots of PRs from new contributors.
### 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:
2022-04-16
### When were the last committers or PPMC members elected?
2022-03-04
### Have your mentors been helpful and responsive?
All good here
### Is the PPMC managing the podling's brand / trademarks?
All good here
### Signed-off-by:
- [X] (sedona) Felix Cheung
Comments:
- [ ] (sedona) Jean-Baptiste Onofré
Comments:
- [ ] (sedona) George Percivall
Comments:
- [ ] (sedona) Von Gosling
Comments:
### IPMC/Shepherd notes:
--------------------
## ShenYu
ShenYu is a high performance Microservices API gateway in the Java
ecosystem,
compatible with a variety of mainstream framework systems, it supports hot
plugin loading.
ShenYu has been incubating since 2021-05-03.
### Three most important unfinished issues to address before graduating:
1. Releasing more and more versions.
2. There are more contributors, committers, users.
3. Building a diverse community with open governance.
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
* 8+ new contributors and 1+ new committers have participated in the
community
since the last report. There are currently 267 contributors and 34
committers.
* 50+ pull requests since entering the last report.
* Number of GitHub stars increased (last report: 6022, currently: 6163).
* Held 2 community meetings to discuss development tasks and how to build
an open governance community.
* 3 topics in participating in Gsoc activities.
* 2 topics in participating in OSPP
activities（https://summer-ospp.ac.cn/）.
### How has the project developed since the last report?
* [Released] Released 2.4.3.
* [New Feature] Support register instance to consul.
* [New Feature] Support configurable timeout for Motan Plugin.
* [New Feature] Sync plugin control from admin.
* [New Feature] Add MemorySafeTaskQueue.
* [New Feature] Add alert module.
* [New Feature] Admin Support oracle database.
* [New Feature] Record operation logs in admin.
* [Refactor] Refactor result wrap.
* [Refactor] Refactor divide plugin.
* [Refactor] Refactor the performance of MemoryLimitCalculator.
* [Refactor] Refactor logging plugin to loggingConsole plugin.
* [Refactor] Refactor register-server module to register-client-server
* [Refactor] Refactor response cors headers.
* [Refactor] Refactor metadata match.
* [Refactor] Refactor request query codec.
* [Refactor] Refactor new pagination scheme.
* [Refactor] Refactor valid data for admin.
* [Refactor] Refactor web filter.
* [Bug] Fix PostgreSQL script error.
* [Bug] Fix keep waiting for acquiring memory unexpectedly.
* [Bug] Fix encode queryParam's key to avoid 400 error.
* [Bug] Fix plugin metadata valid error.
### 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:
14 April 2022.
### When were the last committers or PPMC members elected?
19 April 2022
### Have your mentors been helpful and responsive?
Our mentors have been helpful and responsive.
### Is the PPMC managing the podling's brand / trademarks?
The PPMC manages the podling's brand / trademarks.
### Signed-off-by:
- [X] (shenyu) Willem Ning Jiang
Comments: community building in progress
- [ ] (shenyu) Jincheng Sun
Comments:
- [ ] (shenyu) Duo Zhang
Comments:
- [ ] (shenyu) Kevin Ratnasekera
Comments:
- [ ] (shenyu) Atri Sharma
Comments:
- [X] (shenyu) Justin Mclean
Comments:
### IPMC/Shepherd notes:
--------------------
## Spot
Apache Spot is a platform for network telemetry built on an open data model
and Apache Hadoop.
Spot has been incubating since 2016-09-23.
### Three most important unfinished issues to address before graduating:
1. Revive community activity (Discussion in mailing lists, increase
frequency of commits)
2. Create a new roadmap and release plan that will improve adoption
3. Make it easier to contribute to the project (eg, documentation,
framework)
### Are there any issues that the IPMC or ASF Board need to be aware of?
No notification was sent about our upcoming March 2022 report and as result
we missed submitting our report.
### How has the community developed since the last report?
We're continuing to solidify a short term and long term on a roadmap with
the community that will allow more contributors to focus and work on
different levels of the project (i.e. data modeling and schema design,
use-cases, ingestion, ml, ui, dev ops, docs, etc). We're working to
prioritize these discussions, onboarding new committers, and getting
schedules aligned relative to everyone's other workloads.
### How has the project developed since the last report?
The master branch of Apache Spot was largely developed for commercial but
freely available Hadoop software (i.e. Cloudera, Hortonworks) are now in an
end of life (eol) state. In the next several quarters there should be some
priority to shift and add more native implementations on cloud providers
(i.e. AWS, Azure, GCP).
In the short-term it may be feasible to get things working in AWS EMR, and
specifically focus on fixing any issues related to getting the existing
Spot software installed and working. We anticipate lots of compatibility
issues such as working with newer versions of Spark with the existing code
base, as well as updating python code to be compatible with Python 3.9 or
later. Once we get this working we can also release a Cloudformation
template to the public community so that getting Spot setup is much less
labor intesnive than in the past.
In the long term we will want to support several cloud providers and
on-premise options depending on the interest of the community.
Investigate and exploring a replacement for the Spot UI is also still a
high priority. In the short-term, exploring Apache Supersets might be the
best approach. Apache Supersets would give us a basic authentication and
visualization layer into the data landed and processed by Spot.
In the long-term we will need to develop a more comprehensive security and
use-case roadmap for the UI and determine if it makes sense to develop
something from scratch. This will require more involvement and feedback in
the community before we can start designing and planning.
### How would you assess the podling's maturity?
Please feel free to add your own commentary.
- [X] Initial setup
- [X] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2017-09-08
### When were the last committers or PPMC members elected?
2019-09-02
### Have your mentors been helpful and responsive?
Our mentor has been helpful. However, the board and our mentor have
suggested we request an additional mentor to help us keep on top of things.
We would like make this a high priority during the next quarter.
### Is the PPMC managing the podling's brand / trademarks?
Yes
### Signed-off-by:
- [ ] (spot) Uma Maheswara Rao G
Comments:
### IPMC/Shepherd notes:
--------------------
## StreamPipes
StreamPipes is a self-service (Industrial) IoT toolbox to enable non-
technical users to connect, analyze and explore (Industrial) IoT data
streams.
StreamPipes has been incubating since 2019-11-11.
### Three most important unfinished issues to address before graduating:
1. Complete maturity assessment
2. Prepare graduation process
### Are there any issues that the IPMC or ASF Board need to be aware of?
There are no issues right now.
### How has the community developed since the last report?
* The community focused on the new release
* Several active discussions on the mailing list
* Several users have asked for help on the user mailing list
* Number of Twitter followers has increased (last report: 208, current:
219)
* Number of Github stars increased (last report: 274, current: 307)
### How has the project developed since the last report?
* This reporting period was focused on finishing the next release 0.69.0
* Release 0.69.0 was successfully published
* We plan to have a first stable release 1.0 within the next months
### 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:
2022-03-21 (next release is under vote)
### When were the last committers or PPMC members elected?
2022-03-16 (Stefan Obermeier)
### Have your mentors been helpful and responsive?
Yes, our mentors are helpful.
### Is the PPMC managing the podling's brand / trademarks?
Yes, project name is approved and the brand is actively managed.
### Signed-off-by:
- [X] (streampipes) Christofer Dutz
Comments: This podling is doing great. Looking forwards to the
graduation party.
- [X] (streampipes) Jean-Baptiste Onofré
Comments: Great podling, I think they are quite ready to graduate.
- [ ] (streampipes) Julian Feinauer
Comments:
- [X] (streampipes) Justin Mclean
Comments:
- [ ] (streampipes) Kenneth Knowles
Comments:
### IPMC/Shepherd notes:
--------------------
## Teaclave
Teaclave is a universal secure computing platform.
Teaclave has been incubating since 2019-08-20.
### Three most important unfinished issues to address before graduating:
- Improve project structure and documentation
- Grow the community (attracting more committers, contributors, users)
- Publish Apache releases (resolving logistics on Apache release)
### Are there any issues that the IPMC or ASF Board need to be aware of?
None.
### How has the community developed since the last report?
Since the last report, we have organized three monthly virtual meetups. For
each meetup, we have write-ups published on the Teaclave blog.
- Teaclave Meetup #10:
<https://teaclave.apache.org/blog/2022-02-24-teaclave-meetup-10/>
- Teaclave Meetup #11:
<https://teaclave.apache.org/blog/2022-03-31-teaclave-meetup-11/>
- Teaclave Meetup #12:
<https://teaclave.apache.org/blog/2022-04-28-teaclave-meetup-12/>
We also released two versions of the Teaclave platform and Teaclave
TrustZone separately:
- Teaclave 0.4.0:
<https://teaclave.apache.org/blog/2022-04-18-announcing-teaclave-0-4-0/>
- Teaclave TrustZone SDK 0.2.0:
<https://teaclave.apache.org/blog/2022-04-18-announcing-teaclave-trustzone-s
dk-0-2-0/>
### How has the project developed since the last report?
Here are the summaries of recent progress:
Teaclave Faas Platform:
- Merged PRs:
<https://github.com/apache/incubator-teaclave/pulls?q=is%3Apr+is%3Aclosed+me
rged%3A2022-01-01..2022-05-01+base%3Amaster>
Teaclave TrustZone SDK
- Merged PRs:
<https://github.com/apache/incubator-teaclave-trustzone-sdk/pulls?q=is%3Apr+
is%3Aclosed+merged%3A2022-01-01..2022-05-01+base%3Amaster+>
Teaclave SGX SDK
- Merged PRs:
<https://github.com/apache/incubator-teaclave-sgx-sdk/pulls?q=is%3Apr+is%3Ac
losed+merged%3A2022-01-01..2022-05-01+base%3Amaster+>
Website
- [blog] Teaclave Meetup #10:
<https://teaclave.apache.org/blog/2022-02-24-teaclave-meetup-10/>
- [blog] Teaclave Meetup #11:
<https://teaclave.apache.org/blog/2022-03-31-teaclave-meetup-11/>
- [blog] Teaclave Meetup #12:
<https://teaclave.apache.org/blog/2022-04-28-teaclave-meetup-12/>
- [blog] Announcing Apache Teaclave (incubating) 0.4.0:
<https://teaclave.apache.org/blog/2022-04-18-announcing-teaclave-0-4-0/>
- [blog] Announcing Apache Teaclave TrustZone SDK (incubating) 0.2.0:
<https://teaclave.apache.org/blog/2022-04-18-announcing-teaclave-trustzone-s
dk-0-2-0/>
### How would you assess the podling's maturity?
- [ ] Initial setup
- [ ] Working towards first release
- [X] Community building
- [ ] Nearing graduation
- [ ] Other:
### Date of last release:
2021-04-18: Apache Teaclave (incubating) TrustZone SDK 0.2.0
### When were the last committers or PPMC members elected?
- 2022-04-26: Qinkun Bao (Apache ID: qinkun), Committer
### Have your mentors been helpful and responsive?
Yes, our mentors work responsively to help us with electing new mentors,
developing new features, fixing bugs, and expanding the community.
### Is the PPMC managing the podling's brand / trademarks?
We don't find any 3rd parties incorrectly using the podling's name and
brand. The VP, Brand has approved the project name. (PODLINGNAMESEARCH-175)
### Signed-off-by:
- [X] (teaclave) Felix Cheung
Comments:
- [X] (teaclave) Furkan Kamaci
Comments:
- [ ] (teaclave) Jianyong Dai
Comments:
- [ ] (teaclave) Matt Sicker
Comments:
- [ ] (teaclave) Zhijie Shen
Comments:
- [ ] (teaclave) Gordon King
Comments:
### IPMC/Shepherd notes:
--------------------
## 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 unfinished issues to address before graduating:
1.Increase active contributors
### Are there any issues that the IPMC or ASF Board need to be aware of?
None
### How has the community developed since the last report?
We added a new Mentor (@Weiwei Yang) which gave Toree an injection
of new blood and ability to move votes quicker.
We have a few new enhancement patches and questions on the project, and
overall
Toree, which is sort of in a mature state, continued in a regular flow.
### How has the project developed since the last report?
Release 0.5.0-incubating has finally been approved and released.
### 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:
2022-04-11
### When were the last committers or PPMC members elected?
Kevin Bates was added to the PPMC on 2019-08-14
### Have your mentors been helpful and responsive?
After adding new mentor we are now able to move votes quicker.
### Is the PPMC managing the podling's brand / trademarks?
No Trademark issues
### Signed-off-by:
- [X] (toree) Luciano Resende
Comments:
- [ ] (toree) Julien Le Dem
Comments:
- [ ] (toree) Ryan Blue
Comments:
- [ ] (toree) Weiwei Yang
Comments:
### IPMC/Shepherd notes:
-------------------- --------------------
## Training
The Training project aims to develop resources which can be used for
training purposes in various media formats, languages and for various Apache
and non-Apache target projects.
Training has been incubating since 2019-02-21.
### Three most important unfinished issues to address before graduating:
1. Restart the Community
2. Start doing releases
3. Make Apache Training more well known
### Are there any issues that the IPMC or ASF Board need to be aware of?
As mentioned in the previous reports, activity in the Training project has
been very low. There was nearly no mailing list activity in the first
quarter, and virtually no commits.
### How has the community developed since the last report?
In April, one of the mentors (cdutz) launched a discussion on the mailing
list to see what the community wanted to do with the project. Together, we
brought up some ideas why the initial enthusiasm for Training materials
has sputtered out.
Some of the ideas to make the project more relevant and build community
include:
- maintaining presence and visiblity as in-person conferences return,
- encourage conversation and brainstorming about effective presentation
resources on the dev website,
- changing our focus to include self-learning resources for Apache
projects, and
- building and publishing Training web artifacts on the project website.
Even if it seems that we haven't yet found a clear and compelling niche,
the existing community is willing to continue work to see where we can
improve.
### How has the project developed since the last report?
Specific work on showcasing web artifacts on the Training project website
has started, as a quick win to demonstrate the project value.
### 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:
2020-07-03 Presentation on NavigatingASFIncubation
### When were the last committers or PPMC members elected?
2020-11-23 Gautam Gupta (Comitter)
### Have your mentors been helpful and responsive?
It was a project mentor that relaunched the discussion after our long
period of inactivity.
### Is the PPMC managing the podling's brand / trademarks?
No issues.
### Signed-off-by:
- [X] (training) Craig Russell
Comments:
- [X] (training) Christofer Dutz
Comments: We really need to get some more activity here.
- [X] (training) Justin Mclean
Comments:
- [ ] (training) Lars Francke
Comments:
### IPMC/Shepherd notes:
--------------------
## Tuweni
Tuweni is a set of libraries and other tools to aid development of
blockchain and other decentralized software in Java and other JVM languages.
Tuweni has been incubating since 2019-03-25.
### Three most important unfinished issues to address before graduating:
1. We need a functional PMC. It's not working right now.
2. We need to educate devs and make sure we generate interest for them.
3. We need to run some outreach to let the world know of this awesome
project ;)
### Are there any issues that the IPMC or ASF Board need to be aware of?
No big problem. We started a vote for new committers and it completely
stalled though, mostly
because our PMC is not in order yet.
### How has the community developed since the last report?
We have had a few folks asking for releases and participating in our dev
list.
### How has the project developed since the last report?
We have continued making some code changes and new features, and made a
maintenance release.
### 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:
2022-03-18
### When were the last committers or PPMC members elected?
ajsutton, 2021-12-21
### Have your mentors been helpful and responsive?
As above, we need to continue our committer votes.
### Is the PPMC managing the podling's brand / trademarks?
No answer
### Signed-off-by:
- [X] (tuweni) Jean-Baptiste Onofré
Comments:
- [X] (tuweni) Furkan Kamaci
Comments:
- [X] (tuweni) Antoine Toulme
Comments: I filed the draft report.
- [X] (tuweni) Dave Fisher
Comments: Perhaps new committers should be voted onto the PPMC too.
### IPMC/Shepherd notes:
--------------------
## Wayang
Wayang is a cross-platform data processing system that aims at decoupling
the business logic of data analytics applications from concrete data
processing platforms, such as Apache Flink or Apache Spark. Hence, it tames
the complexity that arises from the "Cambrian explosion" of novel data
processing platforms that we currently witness.
Wayang has been incubating since 2020-12-16.
### Three most important unfinished issues to address before graduating:
1. Simplifying and documenting the release process
2. Had a significant growth (stars/forks at GitHub), but we want to gain
popularity further and grow the community.
### Are there any issues that the IPMC or ASF Board need to be aware of?
When establishing whether "Apache Wayang" was a proper name, it was
rejected because the 'wayang' word was wrong translated by Google
Translator as 'puppet' but instead of that means 'Imagination' or 'shadow'.
Because of the confusion and to avoid future problems, the process is under
"ASF's trademark counsel". The process started in January, and until these
days, the community did not get any status updates.
### How has the community developed since the last report?
When establishing whether "Apache Wayang" was a proper name, it was
rejected because the 'wayang' word was wrong translated by Google
Translator as 'puppet' but instead of that means 'Imagination' or 'shadow'.
Because of the confusion and to avoid future problems, the process is under
"ASF's trademark counsel". The process started in January, and until these
days, the community did not get any status updates.
In addition to that the community is presenting some project for GSOC and
OSPP.
### How has the project developed since the last report?
The community growth is significant (according to Github); during the last
month, two persons outside of the committer registered had been
contributing to the code.
### 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:
December 13, 2021
### When were the last committers or PPMC members elected?
2022-01-18 : Calvin Kirs
### Have your mentors been helpful and responsive?
Yes, the mentors are very responsive and helpful, nevertheless, two of them
have prolonged inactivity
### Is the PPMC managing the podling's brand / trademarks?
The name is under the process of "ASF's trademark counsel."
### Signed-off-by:
- [X] (wayang) Christofer Dutz
Comments:
- [ ] (wayang) Lars George
Comments:
- [ ] (wayang) Bernd Fondermann
Comments:
- [X] (wayang) Jean-Baptiste Onofré
Comments: great podling, we are still working on growing the
community. However, we are pretty close to graduation imho.
### IPMC/Shepherd notes:
-----------------------------------------
Attachment AC: 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.
## Membership Data:
Apache jUDDI was founded 2010-08-21 (11 years ago) There are currently 7
committers and 7 PMC members in this project. The Committer-to-PMC ratio is
1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Alex O'Ree on 2013-03-17.
- No new committers were added.
## Activity:
- jUDDI - last release was July 1, 2021 to address a reported security issue.
Some recent development activities have been logged, primarily maintenance
and dependency updates. CI capabilities have been renewed using the new
Github features. A new release is planned shortly.
- SCOUT - last release 10 DEC 2018. Resolved several bugs and 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.
- Minimal JIRA activity or mailing list activity (aside from spam) is also a
factor for low development.
- There are enough active PMC members to approve releases and respond to
potential security issues.
## Releases:
- 3.3.10 was released on 2021-07-01.
- SCOUT-1.2.8 was released on Mon Dec 10 2018
-----------------------------------------
Attachment AD: Report from the Apache Juneau Project [James Bognar]
## Description:
The mission of Apache Juneau is the creation and maintenance of software
related to a toolkit for marshalling POJOs to a wide variety of content types
using a common framework, and for creating sophisticated self-documenting REST
interfaces and microservices using VERY little code
## Issues:
No issues to report.
## Membership Data:
Apache Juneau was founded 2017-10-17 (5 years ago)
There are currently 12 committers and 12 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Ayeshmantha Perera on 2019-01-02.
- No new committers. Last addition was Ayeshmantha Perera on 2019-01-02.
## Project Activity:
Last release was 8.2.0 on 2020-10-14.
Still working on next major release v9.0. Mostly done but documentation
and testing is still not complete.
## Community Health:
Project has been inactive in the past quarter due to other commitments.
Hopefully we can get back to working on this project next quarter and
finally complete v9.0.
-----------------------------------------
Attachment AE: Report from the Apache Kafka Project [Jun Rao]
## Description:
Apache Kafka is a distributed event streaming platform for efficiently storing
and processing a large number of records in real time.
## Project Activity:
3.2.0 passed the vote and will be released shortly. It includes
* log4j 1.x is replaced with reload4j (KAFKA-9366)
* StandardAuthorizer for KRaft (KIP-801)
* Send a hint to the partition leader to recover the partition (KIP-704)
* Top-level error code field in DescribeLogDirsResponse (KIP-784)
* kafka-console-producer writes headers and null values (KIP-798 and KIP-810)
* JoinGroupRequest and LeaveGroupRequest have a reason attached (KIP-800)
* Static membership protocol lets the leader skip assignment (KIP-814)
* Rack-aware standby task assignment in Kafka Streams (KIP-708)
* Interactive Query v2 (KIP-796, KIP-805, and KIP-806)
* Connect APIs list all connector plugins and retrieve their configuration
(KIP-769)
* TimestampConverter SMT supports different unix time precisions (KIP-808)
* Connect source tasks handle producer exceptions (KIP-779)
3.1.1 is being voted now.
## Community
Dev mailing list had an 18% decrease in traffic in the past quarter (1336
emails compared to 1621).
User mailing list had an 11% increase in traffic in the past quarter (397
emails compared to 355).
Kafka Summit London was held on Apr 25-26 with more than 1,200 attendees.
Kafka PMC approved Current 2022: The Next Generation of Kafka Summit, a hybrid
event for Kafka and Event Streaming technologies. The new event will extend
Apache Kafka’s reach into the broader community. The event will be held in
Austin in October, 2022.
We didn't add any new PMC members this quarter. We last added a new PMC member
David Jacot on Dec. 16, 2021.
We added one new committer Luke Chen on Feb. 9, 2022.
## Releases
3.1.0 was released on 2022-01-24.
2.7.2 was released on 2021-11-22.
2.6.3 was released on 2021-11-22.
## Issues:
There are no issues requiring board attention.
-----------------------------------------
Attachment AF: Report from the Apache Kibble Project [Sharan Foga]
-----------------------------------------
Attachment AG: Report from the Apache Knox Project [Larry McCay]
## Description:
The mission of Knox is the creation and maintenance of software related to
Simplify and normalize the deployment and implementation of secure Hadoop
clusters
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Knox was founded 2014-02-18 (8 years ago)
There are currently 23 committers and 19 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Attila Magyar on 2021-12-12.
- No new committers. Last addition was Attila Magyar on 2021-12-13.
## Project Activity:
1.6.1 was released on 2022/01/12
This was a security patch release with fixes related to log4j and
a minor url parsing error. We have plans to move to log4j 2.x line
and an Apache Knox 2.0.0 release due to the incompatibility that
refactoring presents. We will continue to maintain the 1.6.x line
with security and bug fixes as appropriate.
## Community Health:
The community interactions continue to reflect a mature project
and fewer features rather than small improvements and fixes. We
will be pursuing interesting new SSO services and cloud native
usecases in coming releases which should increase traffic and
community involvement. We also have a feature that still requires
additional security review and scrutiny in a feature branch.
dev@knox.apache.org had a 29% decrease in traffic in the past
quarter (544 emails compared to 759)
user@knox.apache.org had a 56% increase in traffic in the past
quarter (25 emails compared to 16)
40 issues opened in JIRA, past quarter (166% increase)
40 issues closed in JIRA, past quarter (135% increase)
35 commits in the past quarter (-53% change)
10 code contributors in the past quarter (66% increase)
40 PRs opened on GitHub, past quarter (122% increase)
31 PRs closed on GitHub, past quarter (6% increase)
-----------------------------------------
Attachment AH: Report from the Apache Kudu Project [Andrew Wong]
## Description:
The mission of Apache Kudu is the creation and maintenance of software related
to a distributed columnar storage engine built for the Apache Hadoop ecosystem.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Kudu was founded 2016-07-20 (6 years ago)
There are currently 27 committers and 27 PMC members in this project.
The Committer-to-PMC ratio is 1:1.
Community changes, past quarter:
- No new PMC members. Last addition was Bankim Bhavsar on 2020-04-18.
- No new committers. Last addition was Bankim Bhavsar on 2020-04-17.
## Project Activity:
Recent releases:
- 1.16.0 was released on 2022-04-11.
- 1.15.0 was released on 2021-06-22.
- 1.14.0 was released on 2021-01-27.
## Community Health:
- Traffic to dev@kudu.apache.org had a 66% increase in traffic in the past
quarter (5 emails compared to 3) due to the 1.16.0 release and vote threads.
- Public IM activity over the community Slack channel remained steady,
measured by daily active users (+4%) and weekly active users (+0%).
- Development activity measured in the number of commits is steady at 79
commits (-4% change from previous quarter).
- Development activity measured in the number of closed JIRA issues is down to
13 issues (-31% change from previous quarter).
- Number of code contributors increased by 54% compared to the past quarter to
17.
- Website traffic is steady, +0.44% users and -1.78% in sessions.
-----------------------------------------
Attachment AI: Report from the Apache Kylin Project [Shao Feng Shi]
## Description:
The mission of Apache Kylin is the creation and maintenance of
software-related to a distributed and scalable OLAP engine
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Kylin was founded 2015-11-18 (6 years ago)
There are currently 47 committers and 24 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. The last addition was Xiaoxiang Yu on 2020-10-08.
- No new committers. The last addition was Shengjun Zheng on 2021-07-07.
## Project Activity:
4.0.1 and 3.1.3 were released on 2022-01-05. The next release should be
coming in June.
## Community Health:
Overall community health is good but development activity is decreasing.
The good news is that more Kylin users are willing to upgrade from Kylin 2/3 to
the latest 4.0 version, we are collecting feedback from users and doing our
best to fix bugs and provide enhancement to make Kylin 4 ready for production.
23 issues opened in JIRA, past quarter (-41% change) 7 issues closed in JIRA,
past quarter (-22% change) 50 commits in the past quarter (-43% change) 9 code
contributors in the past quarter (28% increase) 51 PRs opened on GitHub, past
quarter (no change) 42 PRs closed on GitHub, past quarter (-4% change)
-----------------------------------------
Attachment AJ: Report from the Apache Libcloud Project [Tomaž Muraus]
## Description:
The mission of Libcloud is the creation and maintenance of software related to
Unified interface to the cloud
## Issues:
There are no issues which require board attention at this time.
## Membership Data:
Apache Libcloud was founded 2011-05-19 (10 years ago)
There are currently 24 committers and 16 PMC members in this project.
The Committer-to-PMC ratio is 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Dimitris Moraitis on 2021-05-07.
- No new committers. Last addition was Dimitris Moraitis on 2021-05-02.
## Project Activity:
Activity on Github continues to be OK.
Libcloud v3.5.0 and v3.5.1 has been released in March 2022. v3.5.0
release dropped support for Python 3.5 and reformatted the code
with black code formatting tool to ensure a more consistent
development experience.
- https://libcloud.apache.org/blog/2022/03/12/libcloud-3-5-0-released.html
- https://libcloud.apache.org/blog/2022/03/30/libcloud-3-5-1-released.html
We plan to do v3.5.1 / v3.6.0 release in the next month or so.
In addition to v3.5.0 we have also made various improvements to the website
(dark theme support, various upgrades and improvements in the backend,
switch from svn to git, Docker image for easier website contributions,
removal of Google Analytics code and switch to Apache Matomo instance -
thanks to the Martijn Visser for help with that).
- https://libcloud.apache.org/blog/2022/03/30/website-updates.html
## Community Health:
Community health continues to be OK. Most of the activity happens
on Github via issues and PRs.
-----------------------------------------
Attachment AK: Report from the Apache Logging Services Project [Ron Grabowski]
## Description:
The mission of the Apache Logging Services project is to create and maintain
software for managing the logging of application behavior and related
software components.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Logging Services was founded 2003-12-16 (18 years ago) There are
currently 40 committers and 16 PMC members in this project. The
Committer-to-PMC ratio is roughly 5:2.
Community changes, past quarter:
- Davyd McColl was added to the PMC on 2021-11-09
- Piotr P. Karwasz added a committer on 2022-03-03
## Project Activity:
- LOG4J-2.17.2 was released on 2022-02-23
- log4cxx-0.13.0 was released on 2022-04-15
## Community Health:
- log4cxx and Log4j have had the most active communities the past quarter
- Work is progressing on Log4j 3.x
- Log4j project continues to work on optimizing Maven build process,
GitHub integrations, and is exploring website redesign
-----------------------------------------
Attachment AL: Report from the Apache Mahout Project [Trevor Grant]
## Description:
The mission of Mahout is the creation and maintenance of software related to
Scalable machine learning library
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Mahout was founded 2010-04-20 (12 years ago)
There are currently 28 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- No new PMC members. Last addition was Trevor Grant on 2017-02-03.
- No new committers. Last addition was Christofer Dutz on 2020-06-08.
## Project Activity:
14.1 Was released 2020-10-07.
We've cleaned up the releases area thanks to a note from Sebb.
## Community Health:
dev@ and user@ have both once again seen dramatic upticks in email traffic.
But the code base has had little to no activity, which is mainly a reflection
of there really isn't that much changing in the world of distributed linear
algebra.
Comitters/PMC are over extended on other projects at the moment, but next steps
should be updating to run with more modern versions of Apache Spark, and also
easing the learning curve for new members.
-----------------------------------------
Attachment AM: Report from the Apache ManifoldCF Project [Karl Wright]
-----------------------------------------
Attachment AN: Report from the Apache Oozie Project [Dénes Bodó]
## Description:
The mission of Oozie is the creation and maintenance of software related to A
workflow scheduler system to manage Apache Hadoop jobs.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Oozie was founded 2012-08-28 (9 years ago)
There are currently 27 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:6.
Community changes, past quarter:
- No new PMC members. Last addition was Dénes Bodó on 2021-04-08.
- No new committers. Last addition was Mate Juhasz on 2020-03-28.
## Project Activity:
There is slow, but steady development going on after our release of 5.2.1
back in February. There is push to support Hadoop 3 and we might have to
drop Pig from the supported actions due to that.
## Community Health:
Community activity is low,
but there are enough active people on the project to provide oversight.
Some metrics:
dev@oozie.apache.org had a 2% increase in traffic in the past quarter
(231 emails compared to 225)
5 issues opened in JIRA, past quarter
3 issues closed in JIRA, past quarter
4 commits in the past quarter
3 code contributors in the past quarter (no change)
-----------------------------------------
Attachment AO: Report from the Apache OpenWhisk Project [Dave Grove]
## Description:
The mission of Apache OpenWhisk is the creation and maintenance of software
related to a platform for building serverless applications with functions
## Issues:
There are no issues requiring board attention
## Membership Data:
Apache OpenWhisk was founded 2019-07-16 (3 years ago)
There are currently 53 committers and 22 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
- Brendan Doyle was added to the PMC on 2022-02-16
- Cosmin Stanciu was added to the PMC on 2022-02-22
- No new committers. Last addition was Ning You Gang on 2021-01-19.
## Project Activity:
The main focus of development has been the merging of a new scheduler
implementation to the core openwhisk repository. This has generated a fair
amount of discussion and an uptick in pull requests, code commits and
discussion.
There should be a wave of releases in the next quarter as we refresh the
programming language-specific openwhisk-runtime components to incorporate new
versions of the underlying upstream runtimes (php, python, go, java, etc).
Recent releases:
+ openwhisk-wskdebug-1.4.0 was released on 2022-05-06.
## Community Health:
Interest in the new scheduler implementation has resulted in increased
activity in comparison to the previous couple of quarters. Hopefully this can
be sustained and we can leverage that interest to complete the long overdue next
release of the core openwhisk system.
-----------------------------------------
Attachment AP: Report from the Apache Ozone Project [Sammi Chen]
## Description
Apache Ozone is a scalable, redundant, and distributed object and file store,
designed to scale to billions of objects/files and run on clusters of
thousands of nodes. Ozone supports S3 compatible object APIs as well as a
Hadoop Compatible File System implementation.
## Issues
None.
## Membership Data
- Apache Ozone was founded 2020-10-21.
- There are currently 56 comitters and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
- In the last quarter, Ethan Rose was added to the PMC on 2022-03-07,
Jyotinder Singh was added as a committer on 2022-04-23, and
Siddhant Sangwan was added as a committer on 2022-05-03
## Project Activity
- S3 performance improvement, "Change S3G to OM RPC framework to keep
persistent connection across multiple users" feature development is
finished.
- Datanode side container rocksdb merge feature is under development. The
major improvement will be the stability and performance on data read/write
path.
- Stream writing is under development. Community is now working on performance
tests and tuning.
- Erasure coding Phase I development was finished. The feature branch was
merged back to master after community vote.
- Many issues are fixed to improve the whole stability and performance. Phase
II development is ongoing, including offline data recovery, usability and
performance improvement.
- Multi-Tenant support feature development is ongoing.
- Introduce hashed key path locks for bucket, to replace the current bucket
wise lock, improving the bucket access performance. Feature is under
development.
- Efforts made to identify and fix the flaky tests, to improve the new PR CI
efficiency.
- A lot of bugs are fixed to improve the stability, performance and integrity.
- Community started the discussion of the 1.3.0 release. There are several
pending blocking issues to address. After that, we will start the release
process.
## Releases Data
- 1.0.0 was released on 2020-09-02.
- 1.1.0 was released on 2021-04-20.
- 1.2.0 was released on 2021-11-17.
- 1.2.1 was released on 2021-12-22.
## Community Health
Last board report was sent on May 11th. In the past quarter,
- dev@ozone.apache.org had 42 emails (-7% change).
- 310 PRs opened on GitHub (+15% change).
- 306 PRs closed on GitHub (+15% change).
- 401 commits (+5% change).
- 43 code contributors in the past quarter (-12% change).
-----------------------------------------
Attachment AQ: Report from the Apache Perl Project [Steve Hay]
## Description:
The mission of Perl is the creation and maintenance of software related to
Dynamic websites using Perl
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Perl was founded 2000-03-10 (22 years ago)
There are currently 21 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Steve Hay on 2012-03-01.
- No new committers were added.
## Project Activity:
The last release was mod_perl-2.0.12 on 2022-01-30.
A few items raised during the last release process still need to be tidied up,
which I should have time for soon if nobody else gets there first.
## Community Health:
Mailing lists have been quiet, which seems to be normal in this project in the
period shortly after a release.
Hopefully a new release later in the year will cause another flurry of activity.
-----------------------------------------
Attachment AR: Report from the Apache Petri Project [Dave Fisher]
## Description:
The mission of Apache Petri is the creation and maintenance of software related
to assessment of, education in, and adoption of the Foundation's policies and
procedures for collaborative development and the pros and cons of joining the
Foundation
## Issues:
No issues for the Board.
## Membership Data:
Apache Petri was founded 2019-11-19 (2 years ago)
There are currently 8 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Daniel Shahaf on 2019-11-19.
- No new committers. Last addition was Justin Erenkrantz on 2020-04-23.
## Project Activity:
The Buildstream culture is nearly ready to cut a 2.0 Beta release following the
Apache release policy. They recently added a new plugin repository. We discussed
some of the licensing and notice requirements last month.
## Community Health:
Not much happens in Petri. We have our one initial culture - Buildstream. As
it becomes a new TLP we should discuss how to promote Petri as an alternative
to the Incubator for certain types of existing communities.
-----------------------------------------
Attachment AS: Report from the Apache Phoenix Project [Ankit Singhal]
## Description:
The mission of Phoenix is the creation and maintenance of software related to
High performance relational database layer over Apache HBase for low latency
applications
## Issues:
No issues to report to the board at this time.
## Membership Data:
Apache Phoenix was founded 2014-05-20 (8 years ago) There are currently 56
committers and 35 PMC members in this project. The Committer-to-PMC ratio is
8:5.
Community changes, past quarter:
- No new PMC members. Last addition was Viraj Jasani on 2021-06-16.
- No new committers. Last addition was Tanuj Khurana on 2021-12-07.
## Project Activity:
Apache Phoenix had its last main release
5.1.2 on 2021-06-07, And we recently discussed cutting out another major
release 5.2.0 soon.
We dropped the support of HBase versions 2.1 and 2.2 from Apache Phoenix as
they were already EOL'ed a long time back and also did not support our new
implementation of global indexes, which are fully consistent.
We also released phoenix-thirdparty 2.0.0 on 2022-04-19 to update the Guava
and common-cli versions.
We discussed removing HBase 1.x support from Apache Phoenix and Omid in
subsequent releases. It will avoid backporting the fixes in multiple branches
and maintaining shim layers.
We recently discussed switching Phoenix on log4j2 from EOL'ed log4j1 and also
to get compatible with Hbase 2.5, which supports log4j2 only.
## Community Health:
Phoenix community continues to remain active, though sometimes most of the
contributions and discussions come from a few individuals.
There is a decline in traffic on user@ by 12%. Some of the discussions on the
user@ list could get offset by the new users who are not aware of the mailing
list and approaching other community sites supported by Vendors or other
question/answer websites.
We had a -24% decline in dev@ and -42% in issues@phoenix.apache.org due to
less discussion/reviews on the JIRAs/PRs owing to more minor fixes than
significant feature development in the last quarter.
We did more commits(+53%) and closed more PRs(+5%) with 8% increase in code
contributors.
-----------------------------------------
Attachment AT: Report from the Apache Pinot Project [Kishore G]
## Description:
The mission of Apache Pinot is the creation and maintenance of software related
to distributed OLAP data store to provide Real-time Analytics to power wide
variety of analytical use case
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Pinot was founded 2021-07-20 (10 months ago)
There are currently 30 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:3.
Community changes, past quarter:
- No new PMC members. Last addition was Felix Cheung on 2021-07-20.
- Rong Rong was added as committer on 2022-05-05
## Project Activity:
Last major release in April was 0.10.0. Since then,
Software development activity:
1. completed work on uploading segments to realtime tables in master branch
2. CSV decoder for realtime added
3. Realtime Native Text Index added
4. Several scalar functions added
5. Continued work on PQL deprecation
Early release branch:
1. Multi stage query execution and JOINS
## Community Health:
The community continue to see a healthy growth. The number of members on slack
is up to 2461. Contributors have been healthy at 34 this month, with 3 of them
first time contributors. Number of issues filed is up, as PMCs are keeping a
more active track on slack conversations and ensuring those get converted to
issues on github.
-----------------------------------------
Attachment AU: 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.
## Issues:
- There are no issues requiring board attention at this time
## Membership Data:
Apache POI was founded 2007-05-16 (15 years ago)
There are currently 41 committers and 34 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Marius Volkhart on 2020-12-27.
- No new committers. Last addition was Marius Volkhart on 2020-12-19.
## Project Activity:
5.2.2 was released on 2022-03-19.
5.2.1 was released on 2022-03-03.
- Release 5.2.1 and 5.2.2 were published in March. These mostly provided
bugfixes, third-party-library updates to avoid security
vulnerabilities and more memory allocation limits to further harden
against malicious documents.
- The library was improved in various areas, a number of additional Excel
functions were added, other than that a continuous stream of
bug-fixes and improvements in various parts of the code.
## Community Health:
- There are questions about features/behaviour which indicates that Apache
POI is in wide-spread use. Questions via email or on Stackoverflow usually
get answers quickly.
- We have a fairly small number of active committers. So we are always looking
at ways to broaden the developer base as the code-base
is large and so some areas are currently not maintained much at all.
- Bug-numbers stayed fairly constant, some bugs were resolved, but a similar
number of bugs was reported, however some of them rather questions or having
root-causes in the user-environment.
Urgent issues and security reports are usually handled quickly.
### XMLBeans
- A few issues were reported for XMLBeans along some discussions with
people still using it for other projects, it seems there are is a small but
active set of users of it besides Apache POI itself.
- Bug influx for XMLBeans is low in general because it is a stable
project in maintenance-mode.
## Bug Statistics:
### Apache POI
- 566 bugs are open overall (+-0)
- Having 138 enhancements (+-0)
- Thus having 428 actual bugs (+-0)
- 110 of these are waiting for feedback (+3)
- Thus having 318 actual workable bugs (-3)
- 3 of the workable bugs have patches available (+-0)
- Distribution of workable bugs across components: {XSSF=87, HSSF=83,
SS Common=39, HWPF=35, XSLF=19, XWPF=19, POI Overall=10, SXSSF=8,
HPSF=4, HSMF=4, POIFS=4, OPC=3, HPBF=1, HSLF=1, SL Common=1}
### Apache XMLBeans
- 160 open issues (+-0)
- Bug 111 (-2)
- Improvement 28 (+1)
- New Feature 17 (+1)
- Wish 2 (+-0)
- Task 2 (+-0)
-----------------------------------------
Attachment AV: Report from the Apache Qpid Project [Robbie Gemmell]
Apache Qpid is a project focused on creating software based on the
Advanced Message Queuing Protocol (AMQP), currently providing a protocol
engine library, message brokers written in C++ and Java, a message router,
and client libraries for C, C++, Go, Java/JMS, Python, and Ruby.
# Releases:
- Qpid Proton 0.37.0 was released on 21st March 2022.
- Qpid Dispatch 1.19.0 was released on 22nd March 2022.
- Qpid JMS 1.6.0 was released on 31st March 2022.
- Qpid ProtonJ2 1.0.0-M5 was released on 7th April 2022.
- Qpid JMS 2.0.0 was released on 27th April 2022.
# 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.
- Roddie Kieley was added to the PMC on 17th February 2022.
- There were no new committer additions in this quarter.
The most recent new committer is Tomas Vavricka, added 14th July 2021.
# Development:
- Development for Proton 0.38.0 is under way, including rework of the
Python binding packaging and installation handling, various bug fixes,
and a rework of the C core event and object handling to simplify it
and improve performance.
- A ProtonJ2 1.0.0-M5 milestone release was made to fix some issues
identified in the earlier releases, with more improvements and fixes
having been made since towards a future M6 release.
- The AMQP 1.0 JMS client had 1.6.0 and 2.0.0 releases with some bug
fixes and improvements, work continues on more as they arise.
- A proposal was made to make Broker-J require a Java 11 minimum for
its next major release, and some work has begun towards that as well
as better supporting Java 17.
# Issues:
There are no Board-level issues at this time.
-----------------------------------------
Attachment AW: Report from the Apache Ranger Project [Selvamohan Neethiraj]
## Description:
Apache Ranger is a framework to enable, monitor and manage comprehensive data
security - consistently across various data processing services.
## Issues:
There are no issues requiring board attention at this time
## Membership Data:
Apache Ranger was founded 2017-01-17 (5 years ago) There are currently 30
committers and 20 PMC members in this project. The Committer-to-PMC ratio is
3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Sailaja Polavarapu on 2019-09-18.
- No new committers. Last addition was Dhaval Shah on 2021-01-20.
## Project Activity:
- Community has initiated the release process for Apache Ranger 2.3.0
- Includes lot of bug fixes since 2.2.0 release
- 527 commits (45 bug fixes + 55 improvements)
- Expected to be released by end of May 2022.
- Apache Ranger 3.0.0 has been progressing well within the community
- Includes 257 bug fixes, 205 Improvements, 6 new features
- Support for reading audit logs from Amazon Cloudwatch
- Support macros to support user/group attribute based row filterings
- Ranger KMS integration with Google Cloud HSM / TencentKMS
- Updated to handle log4j2 issues
## Community Health:
- as the stats below show, the community is active and continue to improve
Apache Ranger is adding more features to support enterprise data security
needs
- Community is working to release 2.3.0 (next minor release) in May 2022.
- Community is scoping for next major release - 3.0.0
- Stats
- dev@ranger.apache.org had a 0% increase in traffic in the past quarter
(1089 vs 1083)
- user@ranger.apache.org had a 84% decrease in traffic in the past quarter
(5 vs 31)
- 135 issues opened in JIRA, past quarter (+ 25% change)
- 112 issues closed in JIRA, past quarter (- 2% change)
- 262 commits in the past quarter (+ 96% change)
- 40 code contributors in the past quarter (+ 73% change)
- 14 PRs opened on GitHub, past quarter (+ 55% change)
- 7 PRs closed on GitHub, past quarter (+ 40% change)
-----------------------------------------
Attachment AX: Report from the Apache REEF Project [Sergiy Matusevych]
-----------------------------------------
Attachment AY: Report from the Apache RocketMQ Project [Xiaorui Wang]
## Description:
The mission of Apache RocketMQ is the creation and maintenance of software
related to a fast, low latency, reliable, scalable, distributed, easy to use
message-oriented middleware, especially for processing large amounts of
streaming data
## Issues:
There is no issues requiring board attention.
## Membership Data:
Apache RocketMQ was founded 2017-09-20 (5 years ago)
There are currently 53 committers and 14 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:2.
Community changes, past quarter:
- No new PMC members. Last addition was Rongtong Jin on 2020-03-30.
- Hongjian Fei was added as committer on 2022-03-16
- Zhi Pan was added as committer on 2022-03-16
- Ping Wang was added as committer on 2022-04-26
- Liuhe Tian was added as committer on 2022-04-26
- Arthur Liang was added as committer on 2022-04-26
## Project Activity:
ROCKETMQ-SPRING-2.2.2 was released on 2022-04-14.
ROCKETMQ-4.9.3 was released on 2022-02-26.
RocketMQ Streams 1.0.1-preview was released on 2022-04-16
## Community Health:
- dev@rocketmq.apache.org had a 21% decrease in traffic in the past quarter
(3011 emails compared to 3777)
- users@rocketmq.apache.org had a 86% increase in traffic in the past quarter
(43 emails compared to 23)
- 378 commits in the past quarter (19% increase)
- 84 code contributors in the past quarter (2% increase)
- 348 PRs opened on GitHub, past quarter (56% increase)
- 296 PRs closed on GitHub, past quarter (21% increase)
- 322 issues opened on GitHub, past quarter (19% increase)
- 185 issues closed on GitHub, past quarter (-17% change)
-----------------------------------------
Attachment AZ: 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, Postgres and MySQL, and is known to run on other Java servers
and relational databases. Latest release is 6.1.1.
## Issues:
We have no issues that require board attention at this time.
## Membership Data:
Apache Roller was founded 2007-02-20 (15 years ago)
There are currently 12 committers and 7 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Michael Bien on 2021-05-24.
- No new committers. Last addition was Yash Maheshwari on 2021-09-01.
## Project Activity:
Roller 6.1.1 was released on April 3, 2022. The Roller community is active
but mostly involved in bug fixes and dependency updates these days.
## Community Health:
The Roller community is healthy enough to maintain Roller and make bug
fix and security releases. We're on the lookout for new contributors.
-----------------------------------------
Attachment BA: Report from the Apache Santuario Project [Colm O hEigeartaigh]
-----------------------------------------
Attachment BB: Report from the Apache Serf Project [Justin Erenkrantz]
-----------------------------------------
Attachment BC: Report from the Apache ServiceComb Project [Willem Ning Jiang]
## Description:
The mission of Apache ServiceComb is the creation and maintenance of software
related to a microservice framework that provides a set of tools and components
to make development and deployment of cloud applications easier.
## Issues:
There is no issues requiring board attention.
## Membership Data:
Apache ServiceComb was founded 2018-10-17 (4 years ago)
There are currently 29 committers and 20 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:5.
Community changes, past quarter:
- No new PMC members. Last addition was MabinGo on 2019-10-09.
- Yasheng Tang was added as committer on 2022-02-12
## Project Activity:
ServiceComb Java Chassis 2.7.1 was released on 2022-04-17.
ServiceComb Java Chassis 2.7.0 was released on 2022-04-07.
ServiceComb Java Chassis 2.6.0 was released on 2021-12-02.
## Community Health:
Overall community health is good. ServiceComb Pack is preparing
the new release this week. We just voted two new committers this week.
There are about 50% increase on the code commits and code contributors.
-----------------------------------------
Attachment BD: Report from the Apache ShardingSphere Project [Liang Zhang]
## Description:
The mission of Apache ShardingSphere is the creation and maintenance of
software related to a database clustering system providing data sharding,
distributed transactions, and distributed database management
## Issues:
None. There are no Apache ShardingSphere related issues.
## Membership Data:
Apache ShardingSphere was founded 2020-04-15 (2 years ago)
There are currently 43 committers and 17 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- Weijie Wu was added to the PMC on 2022-04-06
- Liangda Wang was added as committer on 2022-02-19
- Guoping Li was added as committer on 2022-02-19
- Chuxin Chen was added as committer on 2022-02-19
- Weihong Yin was added as committer on 2022-05-10
- Jinchao Zhao was added as committer on 2022-02-23
## Project Activity:
Software development activity:
- Released Apache ShardingSphere 5.1.0 and 5.1.1.
- Preparing for Apache ShardingSphere 5.1.2.
Attended the following activities to give talks
on Apache ShardingSphere:
Meetups:
- Apache ShardingSphere Meetups on Apr 11 2022,
May 07 2022 and May 12 2022.
Conferences:
- Devcon 2022
- Big Data Days 2022
- FOSDEM 2022
- Conf42: Cloud Native 2022
- FOSS Backstage 2022
- Subsurface LIVE Winter 2022
- FOSSASIA Summit 2022
Other Activities:
- OpenForce 2022
- Published academic paper <Apache ShardingSphere:
A Holistic and Pluggable Platform for Data Sharding> in ICDE 2022
- Stack Overflow Podcast
## Community Health:
The overall community health is good.
We started to hold meetups by ourself every 2 weeks.
More contributors have been included in the community.
-----------------------------------------
Attachment BE: Report from the Apache SIS Project [Martin Desruisseaux]
## Description:
The mission of Apache SIS is the creation and maintenance of software providing
data structures for developing geospatial applications compliant with the model
of OGC/ISO international standards.
## Issues:
There are no issues requiring board attention
## Membership Data:
Apache SIS was founded 2012-09-19 (10 years ago)
There are currently 23 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is roughly 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Alexís Manin on 2021-05-27.
- No new committers. Last addition was Bruno P. Kinoshita on 2021-06-23.
## Project Activity:
A joint Open Geospatial Consortium (OGC)/OSGeo/ASF code sprint happened
in March. Results have been published in an OGC engineering report.
Section 5.10 of that report [1] cites the use of Apache SIS for testing
the Geospatial Integrity of Geoscience Software (GIGS) test suite.
A SIS 1.2 release is under progress. New features include the support of
more data formats and various bug fixes.
[1] https://portal.ogc.org/files/?artifact_id=100630#toc27
## Community Health:
The community health is stable, with the same situation than the one described
in previous reports (i.e. majority of developments done by a single individual).
Two merge requests from other developers of the same company have been submitted
and are pending review (to be done after the release).
However the amount of tests and bug reports that we receive from the rest of the
community is increasing. Not all of them are reported on the public mailing list
since the developers are sometime contacted directly.
-----------------------------------------
Attachment BF: Report from the Apache Solr Project [Houston Putman]
## Description:
The mission of Apache Solr is the creation and maintenance of software related
to highly scalable distributed document search and analytics
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Solr was founded 2021-02-17 (a year ago)
There are currently 89 committers and 61 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Ilan Ginzburg on 2021-09-21.
- No new committers. Last addition was Michael Gibney on 2021-10-07.
## Project Activity:
Software development activity:
- The Solr Operator v0.5.1 was released on 2022-03-21.
- Apache Solr 9.0 was released on 2022-05-12.
- There has been a strong effort to make the tests more stable over the last
quarter, and we have seen notable improvements.
Apache Solr 9.0:
- This is Solr's first solo-release as a TLP.
- This release vastly increases the modularization of the system to enable
new features for users that want to enable them.
- The build system has been completely overhauled to use Gradle instead of
Ant.
- The Official Docker image is now managed within the project and tested as a
part of the release.
- The new minimum Java version is Java 11.
- Many new and exciting features, including neural search are available in
this new release.
Community:
- We had the latest iteration of our Committer Meeting series on 2022-05-10.
During this meeting, we discussed:
- The migration to Apache Curator
- Further modularization of our codebase
- How we can continue to build our community and enable new contributors
- Many members of the community will meet in June 2022, during Berlin
Buzzwords, a popular conference that encompasses search as well as other
big data topics.
## Community Health:
We have seen a flurry of activity over the last quarter, anticipating and
contributing to the release of Solr 9.0. However, development on new features
has taken a back seat to the large amount of work to bring the build and
release up to where it needs to be for 9.0. With 9.0 released, we
expect more feature work to begin.
The development mailing list saw a large increase, 87%, in traffic over the
last quarter. The user list has stayed consistent, with a mere 4% decrease.
Pony Factor is holding steady at 6.
-----------------------------------------
Attachment BG: Report from the Apache Spark Project [Matei Alexandru Zaharia]
Description:
Apache Spark is a fast and general purpose engine for large-scale data
processing. It offers high-level APIs in Java, Scala, Python, R and SQL as
well as a rich set of libraries including stream processing, machine learning,
and graph analytics.
Issues for the board:
- None
Project status:
- We are working on the release of Spark 3.3.0, with Release Candidate 1
currently being tested and voted on.
- We released Apache Spark 3.1.3, a bug fix release for the 3.1 line, on
February 18th.
- We started publishing official Docker images of Apache Spark in Docker Hub,
at https://hub.docker.com/r/apache/spark/tags
- A new Spark Project Improvement Proposal (SPIP) is being discussed by the
community to offer a simplified API for deep learning inference, including
built-in integration with popular libraries such as Tensorflow, PyTorch and
HuggingFace (https://issues.apache.org/jira/browse/SPARK-38648).
Trademarks:
- No changes since the last report.
Latest releases:
- Spark 3.1.3 was released on February 18, 2022.
- Spark 3.2.1 was released on January 26, 2022.
- Spark 3.2.0 was released on October 13, 2021.
Committers and PMC:
- The latest committer was added on Dec 20th, 2021 (Yuanjian Li).
- The latest PMC member was added on Jan 19th, 2022 (Maciej Szymkiewicz).
-----------------------------------------
Attachment BH: Report from the Apache Streams Project [Steve Blackmon]
## Description:
Apache Streams unifies a diverse world of digital profiles and online
activities into common formats and vocabularies, and makes these datasets
accessible across a variety of databases, devices, and platforms for
streaming, browsing, search, sharing, and analytics use-cases.
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Streams was founded 2017-07-18 (4 3/4 years ago). There are currently 9
committers and 9 PMC members in this project. The Committer-to-PMC ratio is
1:1.
## Community changes:
- Brian Hodge joined PMC on 2020-04-26
- Brian Hodge became a committer on 2020-04-26
## Project Activity:
- Apache Streams 0.6.1 was released in March 2020.
- Next Apache Streams release will be the first compatible with JDK11.
- There was discussion last year about path and priorities to 1.0 release and
roadmap beyond, but not many discussions or commits in 2021 or 2022 thus
far.
## Community Health:
- We need to get the upgrades on our main branch released asap.
- We need to conduct more regular roadmap planning, create and deliver based
on a planned release schedule.
- We need to identify and execute strategies to reach out to likely interested
users and developers to reinvigorate the project.
- We need to be willing to evolve the project toward new use cases if
necessary to expand the community.
-----------------------------------------
Attachment BI: Report from the Apache Subversion Project [Nathan Hartman]
## Description:
The Apache Subversion® version control system exists to be universally
recognized and adopted as an open-source, centralized version control
solution 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.
## Issues:
There are no Board-level issues at this time.
## Membership Data:
Our developer and user community is all-volunteer and we'd like to
begin by thanking everyone for their support.
Subversion was founded in February 2000 (22 years ago) and joined the
ASF to become Apache Subversion on 2010-02-16 (12 years ago). There
are currently 88 committers and 50 PMC members in this project. The
Committer-to-PMC ratio is roughly 3:2.
No new committers or PMC members have been added since the last
report. Our most recently added PMC member, Daniel Sahlberg
(dsahlberg@) joined the PMC in August 2021.
## Project Activity:
This has been an eventful and rewarding quarter for Subversion with
ongoing new features development, improved and expanded regression
tests, bug fixes, website improvements, an emerging consensus on
future release planning policies, and, perhaps most notably, two
releases including security fixes.
On 4 April 2022, we released Subversion 1.10.8 and 1.14.2. These
releases fix two server-side security issues known as CVE-2021-28544
and CVE-2022-24070, in addition to a number of other bug fixes and
improvements on both the client and server.
Development of new features is ongoing and has progressed nicely
during this quarter. Two major features currently in development are
described below:
Previously, Subversion clients could operate only on the latest
available working copy format. A new feature known as Multi-WC-Format,
which has already been merged to trunk, will allow newer clients to
operate on multiple working copy formats. This will alleviate the need
for users to upgrade their working copies unless they wish to use
features that require a new format. It will also allow users who have
multiple installed versions of Subversion clients (e.g., the latest
command line client installed in parallel to an IDE with an older
built-in Subversion client library) to experience less hassle if they
access a working copy with more than one of these clients. Multi-WC-
Format is expected to be released with Subversion 1.15.0 and will
support working copies from Subversion 1.8 and up. This feature is
motivated by a desire to balance the maturity and stability enjoyed by
Subversion's users with the needs of the upcoming Pristines On Demand
feature, described below.
Our last few reports have mentioned Pristines On Demand, a new feature
which, at the user's option, cuts in half the storage space consumed
by a Subversion working copy at the expense of potential additional
network communication with the repository server. This tradeoff makes
sense in a number of situations, such as when version controlling very
large files that change infrequently (e.g., release artifacts, binary
formats, etc.), or where network bandwidth is more abundant than
storage space (e.g., Subversion working copies on FLASH-limited
embedded systems). This quarter, development of the initial
production-ready version of the feature continued, with excellent
results. Though it is currently a little rough around the edges, the
feature appears to work as advertised. (I have used a recent
development build and have not encountered any problems with it.)
Altogether, over 300 commits were made to the Subversion subtree this
quarter, roughly categorized as follows: 30% in new features
development, 7% in improved regression tests, 7% in bug fixes, 41% in
release engineering, and 15% in website improvements. To everyone who
has helped move this project forward, thank you.
## Community Health:
It is this chair's opinion that community health is good, despite the
ups and downs and various challenges we experience as a community-
driven project.
For several years, the Subversion website described a time-based
release policy under which new minor release lines would be released
every six months, with a combination of LTS releases supported for
four years and Regular releases having short six month lifespans. This
replaced an earlier policy of making releases whenever we were ready
with no predefined time-based lifespan. Motivation for the time-based
policy was to encourage new feature development, release new features
to users more quickly, and help system administrators plan server
upgrades.
The time-based policy worked well when corporate sponsorship made it
possible, but turned out to be unrealistic without corporate backing.
As a community, we've discussed this issue on and off for some time
with some developers encouraging a return to the original "when we're
ready" policy and others suggesting a variety of alternatives.
Finally, there is an emerging consensus to go with a hybrid of the
newer and older policies which should be more in tune with the
realities of a community-driven project while still providing the most
important benefits that motivated the time-based policy:
New minor release lines will be made "when we're ready" but we'll keep
the LTS and Regular designations to help system administrators plan
server upgrades.
To ensure that there is always at least one supported LTS release
line, these will be supported for at least four years, or three months
after the next LTS release, whichever is later.
There is no longer a requirement to make releases on any fixed
schedule, but to facilitate development and timely release of new
features, the option to make Regular (six month lifespan) releases
exists. Also, if and when we make new minor release lines frequently
enough to justify it, we'll designate some of them as Regular to avoid
creating too many LTS lines that need to be supported in parallel.
Interested readers can find the new policy text on the "roadmap" part
of our website: https://subversion.apache.org/roadmap.html.
We hope this new release policy strikes a balance that is both
advantageous and realistic. As always, we encourage and welcome
participation, both in development and project management, on our
mailing lists.
-----------------------------------------
Attachment BJ: Report from the Apache Superset Project [Maxime Beauchemin]
## Description:
The mission of Apache Superset is the creation and maintenance of software
related to data exploration, analysis, visualization, and dashboarding
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Superset was founded 2020-11-17 (a year ago)
There are currently 54 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
- Diego Pucci was added to the PMC on 2022-03-06
- Hugh Miles was added to the PMC on 2022-03-07
- Michael S Molina was added to the PMC on 2022-02-18
- Stephen Liu was added as committer on 2022-05-06
## Project Activity:
Recent releases that occurred:
1.5.0 was released on 2022-04-28.
1.4.2 was released on 2022-03-29.
1.4.1 was released on 2022-02-10.
## Community Health:
3 new PMC members and 1 new committer
Email list: We've started to encourage even more discussions in dev@ wherever
possible.
Healthy growth in PR activity: PR's opened (749) and closed (761).
Still seeing a large volume of Github issues, and we've started to brainstorm
ways to reduce dependence on Issues (e.g. encourage questions and feature
requests to happen in Github Discussions instead!).
-----------------------------------------
Attachment BK: Report from the Apache Syncope Project [Francesco Chicchiriccò]
## Description:
The mission of Syncope is the creation and maintenance of software related to
Managing digital identities in enterprise environments
## Issues:
There are no issues requiring board attention at this time.
## Membership Data:
Apache Syncope was founded 2012-11-21 (9 years ago)
There are currently 24 committers and 11 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
- No new PMC members. Last addition was Matteo Alessandroni on 2017-12-22.
- No new committers. Last addition was Misagh Moayyed on 2019-10-04.
## Project Activity:
The final steps to release the first 3.0.0 milestone release are being
completed, possibly not as fast as desirable. Anyway, cooperation with Open
Source projects external to the ASF as Apereo CAS and Pac4j is still live and
consistent.
Maintenance for current stable branch 2_1_X keeps going and would possibly
bring at least 2.1.12.
Recent releases:
* 2.1.11 was released on 2022-03-18.
## Community Health:
Discussions about new features and improvements keep appearing and being
followed up in dev@.
Newcomers approach user@ and are getting supported by the community.
GitHub's Pull Requests are confirmed to be the main contribution path, from both
first-time contributors and committers.
-----------------------------------------
Attachment BL: Report from the Apache SystemDS Project [Matthias Boehm]
## Description:
Apache SystemDS is a machine learning (ML) system for the end-to-end
data science lifecycle from data preparation and cleaning, over
efficient ML model training, to scoring and debugging. ML algorithms
or pipelines are specified in a high-level language with R-like syntax,
or related Python and Java APIs, and the system automatically generates
hybrid runtime plans of local, in-memory operations and distributed
operations on Apache Spark.
## Issues for the Board:
- None
## Project Status:
- We are currently working on releasing Apache SystemDS 3.0,
which is the first release on Java 11, Spark 3, and Hadoop 3.
- SystemDS 3.0 also comprises important new features including
federated learning and federated data cleaning/preparation,
data cleaning pipelines, task-parallel feature transformations,
generalized dynamic function loading and execution, as well as
lossless compression, reuse, and memory management
## Membership Data:
- Apache SystemDS was founded 2017-05-16 (incubator process entered
2015-11-02)
- Last PMC members added 2022-05-03 (Shafaq Siddiqi)
- Last committer added 2021-09-23 (David Weissteiner)
- There are currently 34 committers and 26 PMC members in the project.
## Activity and Health:
- Code activity is healthy with 115 commits (-21%) in the last 3 months.
- Community growth is healthy with 16 active contributors (-20%)
in the last 3 months
- Communication is healthy, mailing list activity is improving,
additional work on better documentation.
## Releases:
- Apache SystemDS 2.2.0 was released on 2021-10-30.
- Apache SystemDS 2.1.0 was released on 2021-06-28.
- Apache SystemDS 2.0.0 was released on 2020-10-14.
- Apache SystemML 1.2.0 was released on 2018-08-24.
-----------------------------------------
Attachment BM: Report from the Apache TomEE Project [David Blevins]
-----------------------------------------
Attachment BN: Report from the Apache Traffic Control Project [Eric Friedrich]
## Description:
The mission of Apache Traffic Control is the creation and maintenance of
software related to building, monitoring, configuring, and provisioning a
large scale content delivery network (CDN)
## Issues:
There are no issues requiring the board's attention.
## Membership Data:
Apache Traffic Control was founded 2018-05-15 (3 years ago) There are
currently 28 committers and 18 PMC members in this project. The
Committer-to-PMC ratio is roughly 1.6:1.
Community changes, past quarter:
- Zero new PMC members. Last addition was Zach Hoffman on 2021-11-19.
- Zero new committer. Last addition was Srijeet Chatterjee on 2022-01-03.
## Project Activity:
The community is making progress towards our next major release ATC 7.0.
- Traffic Ops API and authentication improvements
- Add ability for Traffic Ops to reverse proxy for other services
- Move Traffic Ops from APIv2 to APIv3
- Scaling Improvements for Traffic Monitor (sharding of polling large numbers
of caches)
- Traffic Router local fetch of geolocation database
- Traffic Monitor access log enabled
- 25 bug fixes
- Removed Centos8 support in favor of Rocky
ATC7 will be released once last few milestones are completed in the TO API.
## Community Health:
Community health is currently good. The mailing lists are fairly quiet, but
healthy discussion - mainly support, is happening in Slack channels and Github
Issues.
-----------------------------------------
Attachment BO: Report from the Apache Turbine Project [Georg Kallidis]
## Description:
The mission of Turbine is the creation and maintenance of software related to A
Java Servlet Web Application Framework and associated component library
## Issues:
The Turbine project has no board-level issues at this time.
## Membership Data:
Apache Turbine was founded 2007-05-16 (15 years ago)
There are currently 12 committers and 9 PMC members in this project.
The Committer-to-PMC ratio is 4:3.
Community changes, past quarter:
- No new PMC members. Last addition was Jeffery Painter on 2017-11-12.
- No new committers. Last addition was Youngho Cho on 2021-12-06.
## Project Activity:
Last main release was Turbine Core 5.1 on 2021-12-13. No Fulcrum components
are released this quarter.
Current code consolidation work includes:
- release of Turbine archetype (overdue),
- prepare support for upcoming java versions (beginning) and
- still more updating the build processes (using e.g. dependabot, that is
cross cutting for all components).
## Community Health:
This quarter Turbine activity has been below average level. Some feedback was
given from the community, what to do next including feature ideas. Next (not
yet resolved) steps should also include preparing "easy to fix" issues,
which could be adopted and updating more advanced targets, e.g. replace Torque
as default ORM or add support for JDO ORM.
-----------------------------------------
Attachment BP: Report from the Apache Velocity Project [Nathan Bubna]
-----------------------------------------
Attachment BQ: Report from the Apache Whimsy Project [Shane Curcuru]
## Description:
The mission of Apache Whimsy is the creation and maintenance of software
related to tools that help automate various administrative tasks or information
lookup activities
## Issues:
No issues for the board.
## Membership Data:
Apache Whimsy was founded 2015-05-19 (7 years ago)
There are currently 12 committers and 10 PMC members in this project.
The Committer-to-PMC ratio is 6:5.
Community changes, past quarter:
- No new PMC members. Last addition was Matt Sicker on 2020-04-11.
- No new committers. Last addition was Matt Sicker on 2020-04-09.
## Project Activity:
A few PMC members continue to fix any server or page issues.
We attracted a new documentation contributor fixing up webpages, thanks!
## Community Health:
No changes - still very few active committers, but still have oversight
and serious issues get reviewed.
-----------------------------------------
Attachment BR: Report from the Apache Xalan Project [Gary D. Gregory]
## Description:
Apache Xalan exists to promote the use of XSLT. We view XSLT (Extensible
Stylesheet Language Transformations) as a compelling paradigm that transforms
XML documents, thereby facilitating the exchange, transformation, and
presentation of knowledge. The ability to transform XML documents into usable
information has great potential to improve the functionality and use of
information systems. We intend to build freely available XSLT processing
components in order to engender such improvements.
## Issues:
There are no issues requiring board attention.
## Membership Data:
Apache Xalan was founded 2004-09-30 (18 years ago)
There are currently 57 committers and 5 PMC members in this project.
The Committer-to-PMC ratio is roughly 8:1.
Community changes, past quarter:
- No new PMC members. The last addition was Bill Blough on 2019-02-19.
- No new committers. The last addition was Bill Blough on 2019-03-20.
## Project Activity:
As in the previous report, we have not released new software and have not
added new features. While there had been a flare-up of interest in reviving
Xalan-J development to bring it in line with newer versions of W3C
specifications, this has not happened. The last Xalan-J release was July 24
2014. The last Xalan-C++ release was October 22, 2005.
## Community Health:
I would still describe the health of the Xalan project as poor with little
activity while there is still a chance of improvement due to recent but brief
interest in Xalan-J. It should be interesting to note that Xalan's XML
"sibling" project, Apache Xerces, is also experiencing some health issues,
which is not great for the future of XML at Apache.
-----------------------------------------
Attachment BS: Report from the Apache Xerces Project [Michael Glavassevich]
-----------------------------------------
Attachment BT: Report from the Apache XML Graphics Project [Clay Leeds]
Apache XML Graphics Project Board Report for May 2022
==========================================================
The Apache XML Graphics Project is responsible for software intended for the
creation & maintenance of the conversion of XML formats to graphical output &
related software components.
Issues for the Board
====================
Apache FOP 2.7 and Apache XML Graphics Commons 2.7 were both released with bug
fixes earlier this year.
Activity
========
* Apache Batik 1.14 released 2021-01-21
* Apache FOP 2.7 released 2022-01-20
* Apache XML Graphics Commons 2.7 released 2022-01-20
Project Health Report
=====================
The level of community and developer activity remains at a consistent, level
with respect to the previous reporting period.
Recent PMC Changes
==================
Currently 11 PMC members.
* Simon Steiner was added to the PMC on Tue Jan 19 2016
* Clay Leeds was approved for XML Graphics PMC Chair position on March 26,
2018.
Community
=========
Currently 21 committers.
* No new committers added in the last 3 months
* Last committer added was Matthias Reischenbacher at Wed May 13 2015
Most Recent Releases
====================
* Apache Batik 1.14 was released January 21, 2021
* Apache FOP 2.7 was released January 20, 2022
* Apache XML Graphics Commons 2.7 was released January 20, 2022
= SUB PROJECTS =
================
APACHE BATIK
============
Batik is a Java-based toolkit for applications or applets that want to use
images in the Scalable Vector Graphics (SVG) format for various purposes, such
as display, generation or manipulation.
Latest Release
------------
Apache XML Graphics Apache Batik 1.14 was released on January 21, 2021
* BATIK-1292: Useless console message "About to transcoder source of type:
..."
* BATIK-1297: Dependency Convergence issue with xml-apis
APACHE FOP
==========
Apache FOP (Formatting Objects Processor) is a print formatter driven by XSL
formatting objects (XSL-FO) and an output independent formatter. It is a Java
application that reads a formatting object (FO) tree and renders the resulting
pages to a specified output. Output formats currently supported include PDF,
PS, PCL, AFP, XML (area tree representation), Print, AWT and PNG, and to a
lesser extent, RTF and TXT. The primary output target is PDF.
Latest Release
--------------
Apache XML Graphics Apache FOP 2.7 was released on January 20, 2022
* Bug fixes
XML GRAPHICS COMMONS
====================
Apache XML Graphics Commons is a library that consists of several reusable
components used by Apache Batik and Apache FOP. Many of these components can
easily be used separately outside the domains of SVG and XSL-FO. You will find
components such as a PDF library, an RTF library, Graphics2D implementations
that let you generate PDF & PostScript files, and much more.
Latest Release
------------
Apache XML Graphics Commons 2.7 was released January 20, 2022
* Bug fixes
-----------------------------------------
Attachment BU: Report from the Apache YuniKorn Project [Weiwei Yang]
## Description:
The mission of Apache YuniKorn is the creation and maintenance of software
related to a standalone resource scheduler responsible for scheduling batch
jobs and long-running services on large scale distributed systems running in
on-premises environments as well as different public clouds
## Issues:
There is no issues requiring board attention.
## Membership Data:
Apache YuniKorn was founded 2022-03-15 (2 months ago)
There are currently 29 committers and 23 PMC members in this project.
The Committer-to-PMC ratio is roughly 4:3.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- No new committers were added.
## Project Activity:
Development activity:
- The community just published 1.0.0 release (05/04/2022).
This is a huge milestone with a tone of improvements, and
a new deployment model now is supported.
- The community had a meeting to discuss the roadmap
for 1.1 and 1.2. And the target release time frame
for 1.1 is Aug, 2022. Also the community might want
to release a 1.0.1 version for bug fixes if we see
major production issues.
## Community Health:
There were 15+ active committers and contributors who
contributed to the 1.0.0 release. And we see more users
are starting to trying yunikorn, and trying to get help
from our slack channel or mailing list. Overall the
community health is good.
This month, 2 PPMC member will present a session on
KubeConf, and next month 2 other PPMC member will
present a session on Spark AI Summit. PPMC members
are also preparing to submit talks for the comming
ApacheConf.
------------------------------------------------------
End of minutes for the May 18, 2022 board meeting.
Index