Thanks for responses. Between movie night and kids I didn't submit. I'll submit tomorrow afternoon so if there is any other feedback or corrections let me know.
Thanks, Marc On Mon, Oct 5, 2026, 1:58 PM Daniel Roberts <[email protected]> wrote: > Report looks good! > > On Sun, Oct 4, 2026 at 6:03 PM dlmarion.comcast.net via dev < > [email protected]> wrote: > > > Looks good, no issues here. > > ________________________________ > > From: Marc P. <[email protected]> > > Sent: Sunday, October 4, 2026 4:10 PM > > To: dev <[email protected]> > > Subject: [DRAFT] Board report due October 14 2026 > > > > Hi Devs, > > > > Here's a draft of the board report that we agreed to publish on the dev > > list. I'll leave this open for several days and submit it by COB October > > 9th to give time for feedback, suggestions, and changes. > > > > I drafted it by hand, then checked the facts with the following prompt: > > https://gist.github.com/phrocker/7b925795be97e298d59b10a4bd42dce2 > > > > I look forward to your feedback. > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > ## 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 32 PMC members in this project. > > The Committer-to-PMC ratio is roughly 11:8. > > > > Community changes, past quarter: > > - Arbaaz Khan was added to the PMC and as a committer on 2026-08-24. > > - Eight PMC members moved to emeritus status on 2026-09-30, following a > > roll > > call for inactive PMC members. > > > > ## Project Activity: > > - 2.1.5 [1] contained bug fixes and stability improvements. > > - 2.1.6 [2] fixed CVE-2026-62764 [3], which let an authenticated user > > without system permissions shut down Accumulo services in 2.1.4 and > > 2.1.5. > > - 4.0.0-alpha-1 [4] is the first preview of 4.0, which supports elastic > > deployments and multiple active Managers. Work continues toward a final > > 4.0.0 [5]. > > - We added a SECURITY.md [6] describing our threat model and how to > report > > vulnerabilities. > > - With help from INFRA [7], we renamed several side repositories to > remove > > Fluo from their names and archived those no longer maintained. > > > > ### Releases: > > - accumulo-4.0.0-alpha-1 was released on 2026-09-24. > > - accumulo-2.1.6 was released on 2026-07-17. > > - accumulo-2.1.5 was released on 2026-07-08. > > > > ## Community Health: > > Overall community health is good and GitHub activity remains consistent, > > with > > about 80 commits this quarter. The board approved a new PMC Chair, > > resolving > > the concern from our last report. The dev list (44 emails this quarter) > > carried release votes and design discussions, including Java 21 virtual > > threads, a standard key format for command-line tools, and whether to > > create > > a separate security mailing list. > > > > ## Links > > [1] https://accumulo.apache.org/release/accumulo-2.1.5/ > > [2] https://accumulo.apache.org/release/accumulo-2.1.6/ > > [3] https://www.cve.org/CVERecord?id=CVE-2026-62764 > > [4] https://accumulo.apache.org/release/accumulo-4.0.0-alpha-1/ > > [5] https://github.com/apache/accumulo/milestone/25 > > [6] https://github.com/apache/accumulo/blob/main/SECURITY.md > > [7] https://issues.apache.org/jira/browse/INFRA-28238 > > >
