Looks fine to me, but I'm wondering if we should omit the Fluo portions from this, in order to avoid spreading the conversation across too many forums. Maybe just a simple statement like "see Fluo report" and I can include the details from your summary of the matter on the Fluo report instead.
On Fri, Apr 4, 2025 at 5:11 PM Ed Coleman <edcole...@apache.org> 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 report is due by Wednesday, April 9th. > > The following is cut-n-paste directly from the tool - formatting > differences should not be reflected in the tool submission. > > Ed Coleman > > --- report text from reporter tool --- > > ## 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: Discussion on folding Fluo under the Accumulo PMC. > > The question has been raised by an ASF Director about the status of Fluo > [1]. > > Fluo is a distinct and separate project that builds on Accumulo. The > Accumulo > and Fluo PMCs need to start a public discussion on how the Accumulo PMC can > take ownership of the Fluo code base and if Fluo is maintained as a > separate > repo, keeping the current Fluo branding or somehow made a sub-project of > Accumulo. Keeping the Fluo branding and repo may be the preferred approach, > but may require additional guidance and coordination with the Board. > > ## Membership Data: > Apache Accumulo was founded 2012-03-20 (13 years ago) > There are currently 43 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 Kevin Rathbun on 2024-07-24. > - No new committers. Last addition was Kevin Rathbun on 2024-07-24. > > ## Project Activity: > > ### Releases: > - accumulo-1.10.4 (legacy) was released on 2023-11-16. > - accumulo-2.1.3 (LTM) was released on 2024-08-12. > - accumulo-3.0.0 was released on 2023-08-21. > - accumulo-access-1.0.0-beta was released on 2024-02-17. > > ### Planned Release Activity: > > Release planning for 2.1.4, 3.1 and 4.0 has been started on the dev list > [2]. > The release work for 2.1.4 is under way. The 3.1 branch has being prepared > for > release with the deprecations required by semver to mark removals that are > planned to occur in the 4.0 release. > > The upcoming 4.0 release will be a significant change to Accumulo and is an > evolution of the processing model to support dynamic scaling and provide > elasticity for improved cost and performance management. > > ## 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 PRs discussions. We also use our slack channel for day-to-day > communications. We continue to use the mailing list for official Apache > business and it remains a channel for users to contact us. > > ## Links > <private> > [1] https://lists.apache.org/thread/dcf5b1ypb6ynlklkrfs7r6dbmg9wqsoh > </private> > [2] https://lists.apache.org/thread/ktpj3165v99gsw8s8lr5qh35r230mkym >
