Sorry for not running this past everyone prior to submission (I dropped
the ball on getting a draft together before it was due).
Please take a look at the report below, and let me know if there are any
concerns :)
## 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 for the board at this time.
## Membership Data:
Apache Phoenix was founded 2014-05-20 (5 years ago)
There are currently 44 committers and 31 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Chinmay Kulkarni was added to the PMC on 2019-09-09
- No new committers. Last addition was Kadir Ozdemir on 2019-05-30.
## Project Activity:
Business as usual for the community overall.
We continue to have active development on the 4.x and 5.x release lines.
There
was an rc0 for a 4.15.0 release which is the next-up release to be had. The
5.x line still needs an owner to step up and drive a release cadence.
There was a suggestion that the Omid and Tephra podlings graduate into
sub-projects of the Apache Phoenix PMC. This suggestion was made as both
Omid
and Tephra have integration into Phoenix and provide some direct, end-user
value. Both podlings were struggling to retain active podling memberships.
The Phoenix community voted in favor of this graduation for both
podlings, and
all podling members who request it will be made Apache Phoenix committers.
At this point, the 72hr lazy-consensus/notice on general@incubator to
perform
this double-podling subproject graduation has passed. VP-Phoenix and podling
mentors need to sync and make a plana to start combining these resources.
## Community Health:
Developer (dev/issues) mailing list traffic is down slightly, but user
mailing
list traffic is actually up over the past quarter. We continue to see an
up-tick
and the use of Github pull requests over patches on Jira (which may be
related
to the change in dev/issues traffic volume). As a project, continuing to
ensure
that Github-based code contributions are being integrated is ever more
important.
In general, we continue to see the same developers participating, with a
reasonable number of new contributors to keep the committer pipeline active.
