LGTM. Thanks for putting this together Ed. On Tue, Apr 4, 2023 at 4:27 PM dev1 <d...@etcoleman.com> wrote:
> The Accumulo community decided to draft the Apache community reports on > the Accumulo dev list – and this is a draft of the January 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. > > ## Issues: > There are no issues requiring board attention. > > ## Membership Data: > Apache Accumulo was founded 2012-03-21 (11 years ago) > There are currently 41 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 Christopher L. Shannon on > 2022-09-27. > - No new committers. Last addition was Christopher L. Shannon on > 2022-09-27. > > Members transitioned to emeritus: > - Arvind Shyamsundar (arvindsh) > - David Medinets (medined) > > ## Project Activity: > Accumulo has started discussions and work to change the processing model to > support dynamic scaling and provide elasticity. The Accumulo Confluence > space[1] was activated to host the design documents and provide a > collaboration platform for developers and users. The goal 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. > > Upcoming planned releases expected in the next quarter. > - Maintenance releases of 1.10.3 and 2.1.1, (The legacy 1.x line will reach > end-of-life on 2022-11-01) > - The 3.0 release is planned to be a removal of deprecated items as > permitted > by semver, but with minimal other changes. The 3.0 release will be a > baseline for redesign work but the community has not decided if the > redesign > would be a 3.1 or a 4.0 release. Those discussions will occur as the > design > continues to evolve > > ## 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://cwiki.apache.org/confluence/display/ACCUMULO/Apache+Accumulo+Home >
