The Accumulo community decided to draft the Apache community reports on the
Accumulo dev list – and this is a draft of the October report for review /
comments. The report is due by Wednesday, October 10th. Sorry for the short
noticeThe following is cut-n-paste directly from the tool - formatting
differences should not be reflected in the tool submission.
Ed Coleman

--- begin report ---
## 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 high activity.
- Issues for the board: None.

## Membership Data:
Apache Accumulo was founded 2012-03-20 (14 years ago) There are currently 44
committers and 39 PMC members in this project. The Committer-to-PMC ratio is
roughly 6:5. It is our practice to invite committers to be PMC members at
the
same time. The difference between committers and PMC members is because some
PMC members have elected to go emeritus.

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:
Accumulo is currently working on some significant development efforts.
- Improving the performance and stability of the with the patch release of
2.1.4
- Adding new features and performance improvements to 3.1 line
- The evolution of the processing model to support dynamic scaling and
provide
  elasticity.

### Releses:
- accumulo-1.10.4 (EOL) was released on 2023-11-16.
- accumulo-2.1.4 (LTM) was released on 2025-08-20.
- accumulo-3.0.0 (non-LTM) was released on 2023-08-21.
- accumulo-access-1.0.0-beta was released on 2024-02-17.

## Community Health:
Overall community health is good and GitHub activity remains consistent. The
email traffic reflects the community preference of using GitHub projects and
issues for planning and PRs for code discussions. We also use our slack
channel for day-to-day communications. We continue to use the mailing list
for
official Apache business and remains a channel for users to contact us.

Reply via email to