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 9th.

Currently, the ASF reporting wizard tool is not working, so this was
created by hand and the formatting will certainly change when this is
submitted.

Ed Coleman

---- begin report text ----

## 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 (12 years ago) There are currently
43 committers and 39 PMC members in this project. The Committer-to-PMC
ratio is roughly 1:1. 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:
 - Kevin Rathbun was added as PMC member on 2024-07-25 [1]
 - Kevin Rathbun was added as a committer on 2024-07-25 [1]

 - John Vines elected to move to PMC emeritus status on 2024-07-22

## Project Activity:

### Releases:
  - accumulo-1.10.4 (legacy) was released on 2023-11-16.
  - accumulo-2.1.3 (LTM)  was released on 2024-08-04.
  - accumulo-3.0.0 was released on 2023-08-21.
  - accumulo-access-1.0.0-beta was released on 2024-02-17.

The Accumulo 1-10.x line reached end-of-life and Accumulo-1.10.4 was the
final release. The vote thread can be found at [2]
The vote thread for 2.1.3 can be found at [3]
Work on 3.1.0 and future 4.0.0 branches remain very active.

### Planned Release Activity:
Accumulo is currently working on some significant development efforts.
With the release of
2.1.3, we have begun formalizing future release plans:
  - Continue with critical bug fixes of the 2.1.x line.
  - Created 3.1 branch to prepare for a feature-freeze and a release
preparation.
  - Changes from the elasticity branch have been merged to the main GitHub
branch and we are preparing a 4.0.0-alpha release.  These changes are the
evolution of the processing model to support dynamic scaling and provide
elasticity for improved cost and performance management.

### Other:
  - Migration from GitHub Classic Projects.  The community discussed the
sun-setting of GitHub Classic projects that we used to track release
changes. The community consensus was to switch to using release milestones
and using new project boards for collaboration on specific topics.
 - Updated bylaws to align with the PMC membership change from the ASF
board. The changes included simplifying the bylaw text by replacing text
with links to the relevant ASF documentation and clarifying our community
practices.  The discussion was held on the dev mailing list at [4] and in
the PR [5]. The changes passed with 11 +1 and no other votes [6]

## 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.

## Links
[1] <private>
https://lists.apache.org/thread/2dt1y8grkmw6hxk1dwl5b2rtn76lroxb</private>
[2] https://lists.apache.org/thread/6jy0v0qk14163xx19ocz4l3xxc1rzr3z
[3] https://lists.apache.org/thread/qwghptxc1ws2brcpsb9fd2nlftsr3rhk
[4] https://lists.apache.org/thread/mlkq52wj7bmffnq5cv49xgnzfxz0rkyb
[5] https://github.com/apache/accumulo-website/pull/431
[6] <private>
https://lists.apache.org/thread/yyb1brx0oksxdqb0o3p0ol9235j3xfwm/private>

Reply via email to