Shall we also report that the 'bookkeeper proposals flow' is growing and
leads to healthy and organized discussions?

Enrico

Il dom 6 ago 2017, 10:27 Flavio Junqueira <f...@apache.org> ha scritto:

> Thanks for putting this together, a few comments:
>
> - Yahoo! Pulsar is now an Apache Incubator project, it is better to refer
> to it as Apache Pulsar instead.
> - "the 4.5 release is also there. It is due in this August" -> "release
> 4.5 is almost complete and it is due in August".
> - "at Mar 2017" -> "in Mar 2017"
> - The board typically looks for signs indicating that there are potential
> committers being considered or that are promising. For example, I'm not
> seeing the number of new contributors, which is a loose indicator of the
> potential for new committers. I suggest we say that there are a few
> promising candidates based on the growth of the community and contributions
> from joining developers. We don't have to list names.
> - It might also be useful to expand on the mailing list activity. For
> example, we could refer to the number of merges to indicate that all the
> mailing list activity is inducing a very good number of merged
> contributions.
>
> -Flavio
>
>
> > On 01 Aug 2017, at 09:59, Jia Zhai <zhaiji...@gmail.com> wrote:
> >
> > Hi all,
> > Here is a draft for our August report,  Please help review and comments
> on
> > it.
> >
> > Thanks a lot.
> > -Jia
> >
> > ==============
> > ## Description:
> >
> > BookKeeper is a distributed, reliable, and high performance
> > logging service. It has been used as a fundamental service to build
> > high available and replicated services in companies like Twitter,
> > Yahoo and Salesforce. It is also the log segment store for Apache
> > DistributedLog (incubating) and message store for Yahoo Pulsar.
> >
> > ## Issues:
> >
> > There are no issues requiring board attention at this time.
> >
> > ## Activity:
> >
> > - DistributedLog graduates as a sub-project of BookKeeper. Consolidate
> the
> > development with log stream library over bookkeeper.
> > - BookKeeper moves the development to github - use github for tracking
> > issues, moved to gitbox.
> > - New contributions for a new bookkeeper website.
> >
> > ## Health report:
> >
> > - After a year of development among developers from multiple different
> > companies, the 4.5 release is also there. It is due in this August, it
> > includes exciting features like security support, netty 4 upgrade,
> > weight-based placement policy, long poll reads.
> > - We moved to gitbox to reduce the gap for new contributors to engage
> with
> > the community.
> > - DL graduates as a sub-project to consolidate the development efforts
> > around log stream library.
> >
> > ## PMC changes:
> >
> > - Currently 9 PMC members.
> > - JV Jujjuri was added to the PMC on Tue Jun 27 2017
> >
> > ## Committer base changes:
> >
> > - Currently 14 committers.
> > - No new committers added in the last 3 months
> > - Last committers addition was Enrico Olivelli and Charan Reddy G at Mar
> > 2017
> >
> > ## Releases:
> >
> > - Last release was 4.4.0 on Sun May 15 2016
> >
> > ## Mailing list activity:
> >
> > Consolidate efforts coming from DL graduation as sub-project. More
> > contributor/committer engagement cause the increased of mailing list
> > activities.
> >
> > - dev@bookkeeper.apache.org:
> >    - 90 subscribers (up 7 in the last 3 months):
> >    - 2706 emails sent to list (875 in previous quarter)
> >
> > - iss...@bookkeeper.apache.org:
> >    - 6 subscribers (up 0 in the last 3 months)
> >
> > - u...@bookkeeper.apache.org:
> >    - 100 subscribers (down -1 in the last 3 months):
> >    - 27 emails sent to list (23 in previous quarter)
> >
> >
> > ## JIRA activity:
> > - 60 JIRA tickets created in the last 3 months
> > - 88 JIRA tickets closed/resolved in the last 3 months
> >
> > - 85 Github issues created in the last 3 months
> > - 42 Github issues closed/resolved in the last 3 months
> > - 83 Github Pull Requests created in the last 3 months
> > - 75 Github Pull Requests closed/resolved in the last 3 months
>
> --


-- Enrico Olivelli

Reply via email to