Hi Devs, As we've previously agreed, here's a draft of the board report that we agreed to publish on the dev list. I've taken the liberty to draft this one, as per Ed's recent absence from community activity. I will attempt to ensure that this is submitted on time (tomorrow) as I have drafted here, unless there are any proposed changes before then.
***************************** ## Description: The mission of Apache Accumulo is the creation and maintenance of software related to a robust, scalable, distributed key/value store with cell-based access control and customizable server-side processing. ## Project Status: Current project status: Ongoing with moderate activity Issues for the board: The current PMC chair has not recently been active in the project, and the last few board reports have been prepared by an alternate volunteer. The PMC is currently in process of discussing nominations for a new PMC Chair to nominate to the board. ## Membership Data: Apache Accumulo was founded 2012-03-20 (14 years ago) There are currently 43 committers and 39 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 Kevin Rathbun on 2024-07-24. - No new committers. Last addition was John Kucera on 2025-06-04. ## Project Activity: Project activity varied between several different efforts. - Work on a separate access control library was updated to support Java 11 for use with Accumulo 2.1 versions (1.0.0-beta3). - Work on bug fixes and stability fixes for the Accumulo 2.1 release series has been ongoing, with a release candidate staged for 2.1.5 and undergoing a release vote as of the time of this writing. - Work on improvements to the future 4.0 version to support more dynamic scaling (elastic deployments) continues, with recent focus on updating Java, Hadoop, and Thrift dependencies, producing and displaying metrics, and command-line tool improvements. Some progress on new features has stalled due to temporary inactivity of the main contributor for those features, but this probably will not block any future release, and the work may be deferred to a later version. ## Community Health: Overall community health is good, and GitHub activity remains regular. The low email traffic on the dev list reflects the community preference of using GitHub projects and issues for planning and PRs for code discussions, but this activity is also reflected in the notifications list, for anybody who prefers not to engage on GitHub (this is rare for our community). We have observed some new "drive-by" contributions for easy-to-fix typos and things that are probably the result of contributors using AI to create PRs, but these haven't resulted in any new active contributors, though we have seen at least one new active contributor in the last quarter, and several existing community members have provided some tips and mentoring on ASF's Slack and in PR comments. The only serious concern is finding a replacement PMC Chair. We have a few nominations on the private list, which we will discuss and vote on, and present to the board for approval.
