Thanks everyone. I rearranged the access library to be formally part of the releases section.
The report as submitted (note, this is a cut-n-paste from the report wizard, so formatting may be off) --- begin submitted 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 high activity. - Issues for the board: None. Accumulo is currently working on some significant development efforts. Improving the performance and stability of the 2.1.x line, adding new features and performance improvements to 3.1 line, and the evolution of the processing model to support dynamic scaling and provide elasticity. ## 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. It is our practice to invite committers to be PMC members at the same time. The difference between committers and PMC members is due to some PMC members electing to go emeritus. Community changes, past quarter: - No new PMC members. Last addition was Daniel Roberts on 2023-08-09. - No new committers. Last addition was Daniel Roberts on 2023-08-10. ## Project Activity: ### Releases: - accumulo-access-1.0.0-beta was released on 2024-02-17 - accumulo-1.10.4 was released on 2023-11-16. - accumulo-2.1.2 was released on 2023-08-21. - accumulo-3.0.0 was released on 2023-08-21. The Accumulo 1-10.x line reached end-of-life and Accumulo-1.10.4 is the final release. The vote thread can be found at [1] Activity on the next release of 2.1.3, has been very active with bug-fixes and performance improvements that are being driven by community adoption of 2.1.x. Currently 174 PRs have been merged, and there are 21 open issues with 1 labeled as a blocker for the release. Work is actively proceeding on 3.1.0 that will contain new features and performance improvements. Currently, 3.1.0 has 266 merged PRs. In parallel to 3.1, work continues on the evolution of the Accumulo processing model to support dynamic scaling and provide elasticity [2]. The goal for Accumulo is to move from a model where active table metadata 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 Accumulo Access library provides a stand-alone java library with an AccessExpression syntax and an ANTLRv4 grammar to enable reuse separate from Accumulo. Within Accumulo, the AccessExpression is used in the ColumnVisibility and VisibilityEvaluator to provide column-level authorization for data access. The vote thread is available at [3] ## 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 planning and PRs for code 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 [1] https://lists.apache.org/thread/6jy0v0qk14163xx19ocz4l3xxc1rzr3z [2] https://github.com/orgs/apache/projects/164/views/1 [3] https://lists.apache.org/thread/q96v767png90mfm4t330kfbjvml0rc37 --- end of submitted text --- On 2024/04/05 21:19:56 Christopher wrote: > I agree with Dave that it could be moved out of Other and into the > Project activity and Releases sections. But I don't know that it > matters much. > > On Fri, Apr 5, 2024 at 4:21 PM Daniel Roberts <ddani...@apache.org> wrote: > > > > Report looks good! > > > > On Fri, Apr 5, 2024 at 3:41 PM Dave Marion <dmario...@gmail.com> wrote: > > > > > I'm fine with leaving it as-is, like I said, was just curious. > > > > > > On Fri, Apr 5, 2024 at 3:33 PM Ed Coleman <edcole...@apache.org> wrote: > > > > > > > I don't recall mentioning them at all. But the access library seems > > > > significant because it is designed for re-use outside of Accumulo. The > > > > others seem to be "here are some things you may find helpful" - maybe > > > > the > > > > proxy is more than that? But I don't recall ever mention the proxy > > > > specifically in a project report. > > > > > > > > Would if help if the sub-heading (it's at the same level as releases) > > > read > > > > "Other Releases:" ? > > > > > > > > On 2024/04/05 19:22:22 Dave Marion wrote: > > > > > And I have no issue if that's what we do for other sub-projects (I was > > > > > asking because I don't know / remember). > > > > > > > > > > On Fri, Apr 5, 2024 at 3:20 PM Ed Coleman <edcole...@apache.org> > > > wrote: > > > > > > > > > > > "Just curious why the Accumulo Access library mentions is in > > > > > > "Other". > > > > > > > > > > > > It was an arbitrary decision on my part. I wanted to make sure that > > > it > > > > > > was noted as an achievement / project activity. But, it did not seem > > > > (to > > > > > > me) to be an Accumulo release - reserving those for 2.x, 3,x .... > > > > > > > > > > > > I used other to actually highlight it - I could place it under > > > project > > > > > > activity if that is the consensus. Same as considering it as a > > > > release - > > > > > > but as you mentioned we don't seem to treat other sub-projects that > > > > way. > > > > > > > > > > > > > > > > > > On 2024/04/05 17:59:22 Dave Marion wrote: > > > > > > > Just curious why the Accumulo Access library mentions is in > > > "Other". > > > > I > > > > > > > think an alternate version of this could describe Accumulo Access > > > in > > > > the > > > > > > > "Project Status" or "Project Activity" section and then add the > > > > release > > > > > > to > > > > > > > the "Releases" section. Does it get relegated to "Other" because > > > > it's a > > > > > > > sub-project (is that what would happen to testing, docker, etc.)? > > > > > > > > > > > > > > On Tue, Apr 2, 2024 at 10:34 AM 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 April report for > > > > review > > > > > > / > > > > > > > > comments. The report is due by Wednesday, April 10th. I'd like > > > > > > > > to > > > > > > submit > > > > > > > > the report on Friday, April 5th. > > > > > > > > > > > > > > > > The text below is copied from the reporting tool and may not > > > > reflect > > > > > > the > > > > > > > > final formatting of the final report when submitted. > > > > > > > > > > > > > > > > Ed Coleman > > > > > > > > > > > > > > > > --- begin report text from report 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: None. > > > > > > > > > > > > > > > > Accumulo is currently working on some significant development > > > > efforts. > > > > > > > > Improving > > > > > > > > the performance and stability of the 2.1.x line, adding new > > > > features > > > > > > and > > > > > > > > performance improvements to 3.1 line, and the evolution of the > > > > > > processing > > > > > > > > model to support dynamic scaling and provide elasticity. > > > > > > > > > > > > > > > > ## 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. It is our practice to invite committers to be PMC > > > > members > > > > > > at > > > > > > > > the > > > > > > > > same time. The difference between committers and PMC members is > > > > because > > > > > > > > some > > > > > > > > PMC members have elected to go emeritus. > > > > > > > > > > > > > > > > Community changes, past quarter: > > > > > > > > - No new PMC members. Last addition was Daniel Roberts on > > > > 2023-08-09. > > > > > > > > - No new committers. Last addition was Daniel Roberts on > > > > 2023-08-10. > > > > > > > > > > > > > > > > ## Project Activity: > > > > > > > > > > > > > > > > ### Releases: > > > > > > > > - accumulo-1.10.4 was released on 2023-11-16. > > > > > > > > - accumulo-2.1.2 was released on 2023-08-21. > > > > > > > > - accumulo-3.0.0 was released on 2023-08-21. > > > > > > > > > > > > > > > > The Accumulo 1-10.x line reached end-of-life and Accumulo-1.10.4 > > > > is the > > > > > > > > final release. The vote thread can be found at [1] > > > > > > > > > > > > > > > > Activity on the next release of 2.1.3, has been very active with > > > > > > bug-fixes > > > > > > > > and > > > > > > > > performance improvements that are being driven by community > > > > adoption of > > > > > > > > 2.1.x. Currently 174 PRs have been merged, and there are 21 open > > > > issues > > > > > > > > with 1 > > > > > > > > labeled as a blocker for the release. > > > > > > > > > > > > > > > > Work is actively proceeding on 3.1.0 that will contain new > > > > features and > > > > > > > > performance improvements. Currently, 3.1.0 has 266 merged PRs. > > > > > > > > > > > > > > > > In parallel to 3.1, work continues on the evolution of the > > > Accumulo > > > > > > > > processing > > > > > > > > model to support dynamic scaling and provide elasticity [2]. The > > > > goal > > > > > > for > > > > > > > > Accumulo is to move from a model where active table metadata 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. > > > > > > > > > > > > > > > > ### Other: > > > > > > > > 2024-02-17 Released Accumulo Access Library. The library > > > provides > > > > a > > > > > > > > stand-alone java library with an AccessExpression syntax and an > > > > ANTLRv4 > > > > > > > > grammar that enables reuse separate from Accumulo. Within > > > > Accumulo, > > > > > > the > > > > > > > > AccessExpression is used in the ColumnVisibility and > > > > > > VisibilityEvaluator to > > > > > > > > provide column-level authorization for data access. The vote > > > > thread is > > > > > > > > available at [3] > > > > > > > > > > > > > > > > > > > > > > > > ## 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 planning and PRs for code discussions. We also > > > > > > > > use > > > > our > > > > > > slack > > > > > > > > channel for day-to-day communications. We continue to use the > > > > mailing > > > > > > list > > > > > > > > for > > > > > > > > official Apache business and remains a channel for users to > > > > contact us. > > > > > > > > > > > > > > > > ## Links > > > > > > > > [1] > > > > https://lists.apache.org/thread/6jy0v0qk14163xx19ocz4l3xxc1rzr3z > > > > > > > > [2] https://github.com/orgs/apache/projects/164/views/1 > > > > > > > > [3] > > > > https://lists.apache.org/thread/q96v767png90mfm4t330kfbjvml0rc37 > > > > > > > > > > > > > > > > --- end text --- > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
