The Accumulo community decided to draft the Apache community reports on the 
Accumulo dev list – and this is a draft of the July report  for review / 
comments.

The text below is copied from the reporting tool and may not reflect the final 
formatting of the final report when submitted.

Ed Coleman

--- report tool 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 moderate activity.
Issues for the board: none.

Accumulo is currently working two significant development efforts.  Improving
the performance and stability of the 2.1.x line and the evolution of the
processing model to support dynamic scaling and provide elasticity.

## Membership Data:
Apache Accumulo was founded 2012-03-21 (11 years ago)
There are currently 41 committers and 38 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 Christopher L. Shannon on 2022-09-27.
- No new committers. Last addition was Christopher L. Shannon on 2022-09-27.

## Project Activity:

Releases:
- accumulo-2.1.1 was released on 2023-06-19.
- accumulo-1.10.3 was released on 2023-04-13.  1.x is planned to be end of
  life on or around 2023-11-01, with an expected final release of any
  ready-to-ship bug fixes.

The 2.1.1 release closes CVE-2023-34340. Accumulo 2.1.0 contains a defect in
the user authentication process that may succeed when invalid credentials are
provided. The CVE was reported on 2023-06-01 and was closed with the release
on 2023-06-19.

Activity on 2.1 has been very active with bug-fixes and performance
improvements that are being driven by increased community adoption of 2.1.x as
1.10.x approaches end of life. Accumulo is planning on a 2.1.2 release this
quarter that includes items that were slated for 2.1.1, but were bumped
because of the need for a quick release to resolve the CVE.

A release of 3.0 is also expected this quarter. It is planned to be a removal
of deprecated items as permitted by semver, but with minimal other changes.
The 3.0 release will also complete the removal of potentially offensive terms.

Work on the evolution of the Accumulo processing model to support dynamic
scaling and provide elasticity.  The goal for Accumulo is to move from a model
where active table metatdata and table data management is hosted in active
processes to a model that can dynamically scale server components on-demand to
provide configurable latency and higher scalability. the community has not
decided if the redesign will be a 3.1 or a 4.0 release.

## Community Health:
Overall community health is good and GitHub activity remains consistent.

- The current decline in GitHub activity is due to quiet post-release activity
  and work concentrating on a redesign efforts, including activity
  occurring on Confluence

- Accumulo has transitioned from Jira to GitHub issues. The remaining Jira
  activity reflects closing obsolete issues.

## Links
[1] https://www.cve.org/CVERecord?id=CVE-2023-34340

Reply via email to