Hi all, here's the report I submitted to the board for this quarter.
Please let me know of any issues or omissions.
thanks,
bryan
==============================================================
## Description:
The mission of the Apache DB project is to create and maintain
commercial-quality, open-source, database solutions based on software licensed
to the Foundation, for distribution at no charge to the public.
The Apache DB TLP consists of the following subprojects:
o JDO : focused on building the API and the TCK for compatibility
testing of Java Data Object implementations providing data
persistence.
o Torque : an object-relational mapper for Java.
## Project Status:
Current project status: ongoing
Issues for the board: none
Please see the Project Activity section of our report for some
significant updates.
## Membership Data:
Apache DB was founded 2002-07-16 (23 years ago)
There are currently 48 committers and 46 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 Max Philipp Wriedt on 2024-07-03.
- No new committers. Last addition was Max Philipp Wriedt on 2023-04-14.
## Project Activity:
The JDO project is working on cleaning up the TCK to make multithreaded
queries more efficient and has encountered some underlying issues
that are taking a while to resolve. Once these are resolved,
we will start looking at making a release.
Two significant changes are underway in the DB project:
- Apache DB have voted to select a new PMC chair, Jeffery Painter, and
approved the proposal with 10 positive votes. The Special Order to
ratify the new chair is in this month's agenda.
- The Derby codebase has been moved to read-only state. This
includes the website (https://db.apache.org/derby/), mailing lists, wiki
(https://cwiki.apache.org/confluence/display/DERBY/FrontPage),
Subversion repository, and JIRA bug tracker. Official distributions
remain available on an as-is basis at
https://db.apache.org/derby/derby_downloads.html.
## Community Health:
Although the action to move the Derby codebase to read-only state
reflects a general decline in community interest in the Derby
software, overall the DB project remains in good health. Both the
JDO and Torque communities experience steady activity, with
ongoing development and periodic releases in both codebases.
PMC participation in the recent decisions described above was
strong, with a dozen PMC members participating in the discussions
and broad consensus to make the changes described, including from
3 PMC members in the Derby community.