Re: Accumulo Board Report - due by Wed Jan 10th

2024-01-05 Thread Christopher
Looks good to me.

On Fri, Jan 5, 2024 at 10:43 AM Dave Marion  wrote:
>
> Looks good Ed. Thanks!
>
> On Fri, Jan 5, 2024 at 10:20 AM dev1  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 Jan 10th.
> >
> > 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: Ongoing with high activity.
> > - Issues for the board: None.
> >
> > Accumulo is currently working 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 committer 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 has 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. It is expected that we will release 2.1.3 in this quarter. Currently
> > 106 PRs have been merged, and there are 18 open issues with 2 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 187 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.
> >
> > ## Community Health:
> >
> > Overall community health is good and GitHub activity remains consistent.
> >
> > The low 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
> >
> > --- end report tool text
> >


Re: Accumulo Board Report - due by Wed Jan 10th

2024-01-05 Thread Dave Marion
Looks good Ed. Thanks!

On Fri, Jan 5, 2024 at 10:20 AM dev1  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 Jan 10th.
>
> 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: Ongoing with high activity.
> - Issues for the board: None.
>
> Accumulo is currently working 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 committer 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 has 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. It is expected that we will release 2.1.3 in this quarter. Currently
> 106 PRs have been merged, and there are 18 open issues with 2 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 187 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.
>
> ## Community Health:
>
> Overall community health is good and GitHub activity remains consistent.
>
> The low 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
>
> --- end report tool text
>


Accumulo Board Report - due by Wed Jan 10th

2024-01-05 Thread dev1


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 Jan 10th.

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: Ongoing with high activity.
- Issues for the board: None.

Accumulo is currently working 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 committer 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 has 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. It is expected that we will release 2.1.3 in this quarter. Currently
106 PRs have been merged, and there are 18 open issues with 2 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 187 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.

## Community Health:

Overall community health is good and GitHub activity remains consistent.

The low 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

--- end report tool text