I know you mentioned that this draft may not be the submitted version, but "current project status" is duplicated in the same line. ``` ## Project Status: Current project status: Current project status: Ongoing with moderate activity. Issues for the board: None. ```
Overall it looks good! I did have a clarifying question about the Community Health section. You mentioned that Github activity remains consistent, but the next line refers to a current decline in activity. What previous activity level is the decline referring to? Thanks, - Daniel R. On Wed, Sep 27, 2023 at 10:39 AM 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 October report for > review / comments. I’d like to submit the report by Sept 30th (it is > formally by Oct 11th) > > 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: 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. > > The issue concerning accumulodata.com domain was raised at the last board > meeting. We have not been reporting on the issue because there has been > no progress and we stopped actively pursuing the issue (see past reports > for > details.) The domain was registered and is owned by an Accumulo PMC member, > but the domain was registered using an account that is not longer > accessible. > Without access to that account, the registrar will not take any action. > For > some reason, the domain continues to be auto-renewed. The domain clearly > provides historical information and points to the official Accumulo ASF > site > for downloads. There seems little incentive to use volunteer's time to > pursue > the issue at this time. Unless things change, we will not continue to > report > on this issue in future reports. > > ## Membership Data: > Apache Accumulo was founded 2012-03-21 (12 years ago) > There are currently 42 committers and 39 PMC members in this project. > The Committer-to-PMC ratio is roughly 1:1. > > Community changes, past quarter: > - Daniel Roberts was added to the PMC on 2023-08-09 > - Daniel Roberts was added as committer on 2023-08-10 > > ## Project Activity: > > ### Releases: > > - accumulo-2.1.2 was released on 2023-08-21. > - accumulo-3.0.0 was released on 2023-08-21. > - accumulo-1.10.3 was released on 2023-04-13. > > Activity on 2.1.3 has been very active with bug-fixes and performance > improvements that are being driven by community adoption of 2.1.x as > 1.10.x approaches end of life. > > Accumulo is planning on a 2.1.3 release [1] this quarter with additional > bug > fixes and performance improvements. As of 2023-09-27, there have been 40 > issues / PR closed since 2.1.2 was released. There are just a few items > that > have been marked as blockers for 2.1.3, and they are actively being worked. > > Accumulo is planning on a 1.10.4 release [2] this quarter as the last > release > of the 1.10 line that reaches declared end-of-life 2023-11-01. > > Accumulo 3.0.0 release was a removal of deprecated items as permitted by > semver. And work is actively proceeding on 3.1 that will contain new > features > and performance improvements. > > In parallel to 3.1, work on the evolution of the Accumulo processing model > to > support dynamic scaling and provide elasticity [3]. 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.x 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://github.com/apache/accumulo/projects/30 > [2] https://github.com/apache/accumulo/projects/27 > [3] https://github.com/orgs/apache/projects/164/views/1 > > > --- end report tool text --- >
