Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2017-11-15 21:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

BookKeeper

15 Nov 2017 [Sijie Guo / Rich]

A report was expected, but not received

16 Aug 2017 [Sijie Guo / Shane]

## Description:

BookKeeper is a scalable, fault-tolerant, and low-latency storage service optimized for append-only workloads.
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 and message store for Apache Pulsar.

## Issues:

There are no issues requiring board attention at this time.

## Activity:

- Apache DistributedLog graduates as a subproject of BookKeeper. We are consolidating the development efforts around
    log stream library over bookkeeper.
- BookKeeper moves the development including issue reporting and tracking to Github. It reduces the barrier for people
    to make contributions to bookkeeper.
- The 4.5.0 release which aims at merging 3 main branches is ready to release. The first release candidate is out on August 07.
- BookKeeper moves the website from CMS to Git. A new bookkeeper website along with tons of documentation improvements are made from contributors.

## Health report:

- After a year of development among develops from multiple different organizations, release 4.5 is almost complete. The first release candidate is out for vote on August 07. It includes exciting features like security support, netty 4 upgrade, weight-based placement policy.
- We moved the git repo to gitbox and are using Github for both issue management and pull request management. It reduced the gap for new contributors to engage with the community.
- DistributedLog graduates as a subproject.
- There are a few promising candidates based on the growth of the community and contributions from joining developers.

## 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 committer addition was Enrico Olivelli and Charan Reddy G at Fri Mar 31 2017

## Releases:

- Last release was 4.4.0 on Sun May 15 2016

## Mailing list activity:

A good number of merged contributions is introducing the mailing list activity.

Consolidate efforts coming from DistributedLog graduation as subproject. More contributor/committer
engagement cause the increased of mailing list activities.

 - dev@bookkeeper.apache.org:
    - 90 subscribers (up 7 in the last 3 months):
    - 3114 emails sent to list (1009 in previous quarter)

 - issues@bookkeeper.apache.org:
    - 6 subscribers (up 0 in the last 3 months)

 - user@bookkeeper.apache.org:
    - 100 subscribers (down -1 in the last 3 months):
    - 27 emails sent to list (23 in previous quarter)


## JIRA activity:

 - 55 JIRA tickets created in the last 3 months
 - 90 JIRA tickets closed/resolved in the last 3 months
 - 120 Github issues created in the last 3 months
 - 70 Github issues closed/resolved in the last 3 months
 - 118 Github Pull Requests created in the last 3 months
 - 109 Github Pull Requests closed/resolved in the last 3 months

17 May 2017 [Sijie Guo / Shane]

## 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:

- Sijie gave a bookkeeper talk at linux #vault in March.
- A followup #vault interview about bookkeeper on linux.com by Sijie and JV.
- BookKeeper Proposals are continuing accepting new proposals.

## Health report:

Release 4.5.0 is inprogress. We have been having healthy discussions around
the issues and features that need to be included in 4.5.0, including security
support, netty 4 upgrade, weight-based placement policy and such.

## PMC changes:

- Currently 8 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Matteo Merli on Wed May 25 2016

## Committer base changes:

- Currently 14 committers.
- New commmitters:
- Enrico Olivelli was added as a committer on Tue Mar 28 2017
- Charan Reddy G was added as a committer on Fri Mar 31 2017

## Releases:

- Last release was 4.4.0 on Sun May 15 2016

## Mailing list activity:

- TODO Please explain what the following statistics mean for the project. If
there is nothing significant in the figures, omit this section.

- dev@bookkeeper.apache.org:
- 83 subscribers (up 3 in the last 3 months):
- 953 emails sent to list (595 in previous quarter)

- issues@bookkeeper.apache.org:
- 6 subscribers (up 0 in the last 3 months)

- user@bookkeeper.apache.org:
- 101 subscribers (up 2 in the last 3 months):
- 23 emails sent to list (36 in previous quarter)


## JIRA activity:

- 49 JIRA tickets created in the last 3 months
- 35 JIRA tickets closed/resolved in the last 3 months

27 Feb 2017 [Sijie Guo / Rich]

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).

## Issues:

There are no issues requiring board attention at this time

## Activity:

We have a bookkeeper meetup organized by Yahoo on November, 2016.

The community continued with bi-weekly calls for review BPs (bookkeeper
proposals) and discussing issues. The progress is going very well. We have
accepted and reviewed several important BPs, like security, weigh-based
data placement policy, lifecycle management and such.

## Health report:

The community is making good progress on release 4.5.0 . We have been
having discussions around issues and features and there are a few contributors
on track to become.

## PMC changes:

- Currently 8 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Matteo Merli on Wed May 25 2016

## Committer base changes:

- Currently 12 committers.
- No new committers added in the last 3 months
- Last committer addition was Siddharth Boobna at Fri Nov 11 2016

## Releases: - Last release was 4.4.0 on Sun May 15 2016

## Mailing list activity:

The number of subscribers has been going up slightly.

- dev@bookkeeper.apache.org:
 - 80 subscribers (up 2 in the last 3 months):
 - 618 emails sent to list (322 in previous quarter)
- issues@bookkeeper.apache.org:
 - 6 subscribers (up 0 in the last 3 months)
- user@bookkeeper.apache.org:
 - 99 subscribers (up 2 in the last 3 months):
 - 35 emails sent to list (10 in previous quarter)

## JIRA activity:

- 34 JIRA tickets created in the last 3 months
- 26 JIRA tickets closed/resolved in the last 3 months

@Rich: bring comments regarding transparency to PMC and ask them to resubmit report next month

16 Nov 2016 [Sijie Guo / Chris]

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).

## Issues:
There are no issues requiring board attention at this time

## Activity:
The mailing list activity has dropped and we attribute it to the split
attention between Apache BookKeeper and the incubating project Apache
DistributedLog. They are closely related given that DistributedLog uses
BookKeeper as a building block for storing logs. Despite the drop of mailing
list activity, there has been good discussion around upcoming features and
improvements to the project.

The community started organizing bi-weekly calls where everyone is invited to
join. The goal is not to make decisions outside the mailing list and jira, but
instead to have a better understanding of current proposals and problems that
users of the project are facing. The community is also organizing a meetup
that will happen in November.

## Health report:
The community is making good progress. We have been having healthy discussions
around issues and features and there are a few contributors on track to
become.

We haven't had a release in a while and we are targeting one for December
2016.

## PMC changes:

- Currently 8 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Matteo Merli on Thu May 26 2016

## Committer base changes:

- Currently 11 committers.
- No new committers added in the last 3 months
- Last committer addition was JV Jujjuri at Thu Jun 09 2016

## Releases:

- Last release was 4.4.0 on Mon, 16 May 2016

## Mailing list activity:

The number of subscribers has been going up slightly. The drop in the traffic
of the dev list we attribute to the split attention between the two related
projects we mention above.

- dev@bookkeeper.apache.org:
 - 77 subscribers (up 4 in the last 3 months):
 - 276 emails sent to list (512 in previous quarter)

- issues@bookkeeper.apache.org:
 - 6 subscribers (up 0 in the last 3 months)

- user@bookkeeper.apache.org:
 - 96 subscribers (up 4 in the last 3 months):
 - 12 emails sent to list (19 in previous quarter)


## JIRA activity:

- 23 JIRA tickets created in the last 3 months
- 6 JIRA tickets closed/resolved in the last 3 months

17 Aug 2016 [Sijie Guo / Chris]

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 large companies like Twitter,
Yahoo and Salesforce. It is also the log segment store for Apache
DistributedLog (incubating).

## Issues:
 - there are no issues requiring board attention at this time

## Activity:
 - The 4.4.0 has been release on May 16th 2016.
 - The community is working on releasing 4.5.0. The 4.5.0 release is targeted on
   merging major changes from different companies, including Twitter, Yahoo and
   Salesforce.
 - Salesforce hosted the last bookkeeper meetup on the 28th Jun 2016


## Health report:
 - The community has been stable.

## PMC changes:

 - Currently 8 PMC members.
 - Matteo Merli was added to the PMC on Wed May 25 2016

## Committer base changes:

 - Currently 11 committers.
 - New commmitters:
    - JV Jujjuri was added as a committer on Wed Jun 08 2016
    - Jia Zhai was added as a committer on Sat Jun 04 2016

## Releases:

 - Last release was 4.4.0 on May 16th 2016

## Mailing list activity:

 - dev@bookkeeper.apache.org:
    - 73 subscribers (up 2 in the last 3 months):
    - 526 emails sent to list (765 in previous quarter)

 - issues@bookkeeper.apache.org:
    - 6 subscribers (up 0 in the last 3 months)

 - user@bookkeeper.apache.org:
    - 93 subscribers (up 6 in the last 3 months):
    - 17 emails sent to list (5 in previous quarter)


## JIRA activity:

 - 15 JIRA tickets created in the last 3 months
 - 14 JIRA tickets closed/resolved in the last 3 months

18 May 2016 [Sijie Guo / Jim]

BookKeeper is a distributed, reliable, and high performance logging service.

= Project Status =

Development on 4.4.0 release is completed. The first release candidate has
been sent out for voting. We expect to announce 4.4.0 release by end of this
week. We will start on release 4.5.0 after 4.4.0 is release.

There are various improvements on storage and client in 4.4.0. An advanced
ledger handle is introduced in 4.4.0, to provide API to add entries with user
supplied entry ids. Details will be noted in 4.4.0 release note.

= Releases =

Our last release was 4.3.2, released on 2015-11-30. The first release
candidate of 4.4.0 was out for voting last week.

= Community Status =

The last committer added was Matteo Merli (mmerli) on the 6th Jul 2015.

No infrastructure issues.

Two BookKeeper Talks at ApacheCon this year: "Apache BookKeeper at Twitter"
from Leigh Stewart, "Low latency storage service using BookKeeper" from JV.

New projects using BookKeeper were open sourced:

- Majordodo: A distributed resource manager : http://majordodo.org/
- DistributedLog: A replicated log service:
https://github.com/twitter/distributedlog


71 subscribers in dev@bookkeeper.apache.org 88 subscribers in
user@bookkeeper.apache.org

916 issues opened to date, 26 since 2016-03-03 641 issues resolved to date, 28
since 2016-03-03 59 people have reported issues, 7 since 2016-03-03 33 people
have contributed patches, 7 since 2016-03-03

16 Mar 2016 [Sijie Guo / Brett]

BookKeeper is a distributed, reliable, and high performance logging service.
The project also includes Hedwig which is a highly scalable Pub/Sub service
built on top of ZooKeeper and BookKeeper with strong durability guarantees.

= Project Status =

Development has continued towards the 4.4.0 release, which is a feature
release. It will be including improvements on bookie storage, compaction and
ledger recovery, and new features about last-add-confirmed long poll. We will
cut 4.4.0 at this month and plan 4.5.0.

= Releases =

Our last release was 4.3.2, released on 2015-11-30. The next release will be
4.4.0.

= Community Status =

The last committer added was Matteo Merli (mmerli) on the 6th Jul 2015.

No infrastructure issues.

70 subscribers in dev@bookkeeper.apache.org
83 subscribers in user@bookkeeper.apache.org

890 issues opened to date, 20 since 2015-11-12
613 issues resolved to date, 15 since 2015-11-12
57 people have reported issues, 6 since 2015-11-12
31 people have contributed patches, 5 since 2015-11-12

17 Feb 2016 [Sijie Guo / Jim]

No report was submitted.

18 Nov 2015 [Sijie Guo / Rich]

BookKeeper is a distributed, reliable, and high performance
logging service. The project also includes Hedwig which is
a highly scalable Pub/Sub service built on top of ZooKeeper
and BookKeeper with strong durability guarantees.

= Project Status =

Development has continued towards the 4.4.0 release, which
is a feature release. It will be including improvements on bookie storage,
compaction and ledger recovery, and new features about last-add-confirmed
long poll. A new api about ledger handle is on proposal and under
discussing.

4.3.2 is under releasing include ledger storage bug fixes that are ported
back from master.

= Releases =

Our last release was 4.3.1, released on 2015-05-27. The next release will
be 4.4.0 and 4.3.2.

= Community Status =

The last committer added was Matteo Merli (mmerli) on
the 6th Jul 2015.

BookKeeper community organized a messaging meetup on 9/21.

Infrastructure issues on committer permission on updating KEYS and staging
repository.

https://issues.apache.org/jira/browse/INFRA-10727
https://issues.apache.org/jira/browse/INFRA-10646

65 subscribers in dev@bookkeeper.apache.org
79 subscribers in user@bookkeeper.apache.org

871 issues opened to date, 18 since 2015-08-11
598 issues resolved to date, 10 since 2015-08-11
55 people have reported issues, 6 since 2015-08-11
29 people have contributed patches, 7 since 2015-08-11

19 Aug 2015 [Sijie Guo / Sam]

BookKeeper is a distributed, reliable, and high performance
logging service. The project also includes Hedwig which is
a highly scalable Pub/Sub service built on top of ZooKeeper
and BookKeeper with strong durability guarantees.

= Project Status =

Development has continued towards the 4.4.0 release, which
is a feature release. It will be including improvements on
bookie storage, compaction and ledger recovery, and new
features about last-add-confirmed long poll. A new api about
 ledger handle is on proposal and under discussing.

= Releases =

Our last release was 4.3.1, released on 2015-05-27.
The next release will be 4.4.0.

= Community Status =

The last committer added was Matteo Merli (mmerli) on
the 6th Jul 2015.

We are going to schedule the first user meetup in September.

No infrastructure issues.

61 subscribers in dev@bookkeeper.apache.org
77 subscribers in user@bookkeeper.apache.org

853 issues opened to date, 10 since 2015-05-15
589 issues resolved to date, 8 since 2015-05-15
54 people have reported issues, 7 since 2015-05-15
26 people have contributed patches, 4 since 2015-05-15

20 May 2015

Change the Apache BookKeeper Project Chair

 WHEREAS, the Board of Directors heretofore appointed Ivan Kelly to the
 office of Vice President, Apache BookKeeper, and

 WHEREAS, the Board of Directors is in receipt of the resignation of
 Ivan Kelly from the office of Vice President, Apache BookKeeper, and

 WHEREAS, the Project Management Committee of the Apache BookKeeper
 project has chosen by vote to recommend Sijie Guo as the successor to
 the post;

 NOW, THEREFORE, BE IT RESOLVED, that Ivan Kelly is relieved and
 discharged from the duties and responsibilities of the office of Vice
 President, Apache BookKeeper, and

 BE IT FURTHER RESOLVED, that Sijie Guo be and hereby is appointed to
 the office of Vice President, Apache BookKeeper, to serve in
 accordance with and subject to the direction of the Board of Directors
 and the Bylaws of the Foundation until death, resignation, retirement,
 removal or disqualification, or until a successor is appointed.

 Special Order 7D, Change the Apache BookKeeper Project Chair,
 was approved by Unanimous Vote of the directors present.

20 May 2015 [Ivan Kelly / Brett]

BookKeeper is a distributed, reliable, and high performance
logging service. The project also includes Hedwig which is
a highly scalable Pub/Sub service built on top of ZooKeeper
and BookKeeper with strong durability guarantees.

= Project Status =

Development has continued towards the 4.3.1 release, which
is a bugfix release. Work has mostly been on bugfixing and test
flakiness, and has been progressing at a steady rhythm.

= Releases =
Our last release was 4.2.4, released on 2015-01-22.

We are currently working on release 4.3.1, which has had one
release candidate which did not pass due to test flakiness.

= Community Status =

The last committer added was Robin Dhamankar (robindh) on
the 9th April 2015.

We also plan to appoint Sijie Guo as PMC chair this month (resolution
submitted).

No infrastructure issues.

55 subscribers in dev@bookkeeper.apache.org
70 subscribers in user@bookkeeper.apache.org

843 issues opened to date, 9 since 2015-03-15
581 issues resolved to date, 12 since 2015-03-15
51 people have reported issues, 4 since 2015-03-15
25 people have contributed patches, 6 since 2015-03-15

18 Mar 2015 [Ivan Kelly / Doug]

BookKeeper is a distributed, reliable, and high performance
logging service. The project also includes Hedwig which is
a highly scalable Pub/Sub service built on top of ZooKeeper
and BookKeeper with strong durability guarantees.

= Project Status =

We made a press release, announcing our move to TLP, through the
foundation on 2015-01-27. This triggered Yahoo to publish a blog post
about their internal usage of BookKeeper in their cloud messaging
service.

Development activity finally picked up at the end of February after a
couple of months of being slow, due to the Christmas period and some
committers changing jobs.

= Releases =
Our last release was 4.2.4, released on 2015-01-22.

A release candidate for 4.3.1 was released on 2015-02-13, but it did
not pass due to some flakiness in tests. We are currently addressing
the flakiness and should cut a new candidate soon.

= Community Status =
There have been no committers added since we became TLP (2014-11-19),
though we are currently in the process of adding one committer.

The last committer added, when we were a subproject, was Rakesh
Radhakrishnan on 24th July 2014.

No infrastructure issues.

51 subscribers in dev@bookkeeper.apache.org
67 subscribers in user@bookkeeper.apache.org

833 issues opened to date, 9 since 2015-01-16
566 issues resolved to date, 3 since 2015-01-16
50 people have reported issues, 5 since 2015-01-16
24 people have contributed patches, 2 since 2015-01-16

18 Feb 2015 [Ivan Kelly / Greg]

Report was submitted but rejected and requested the following month.

21 Jan 2015 [Ivan Kelly / Brett]

BookKeeper is a distributed, reliable, and high performance
logging service. The project also includes Hedwig which is
a highly scalable Pub/Sub service built on top of ZooKeeper
and BookKeeper with strong durability guarantees.

= Project Status =
Development activity has been low over the last month due to the holiday
season. We have been having discussions on how to improve the project
visibility and attract new contributors. One angle we will take is to improve
our documentation to flatten the learning curve for new comers to the
project. We also intend to do more public talks and blog posts, publicizing
the production usecases that already exist.

We plan to submit one talk to ApacheCon NA. We have also been working with
press@a.o to create a press release announcing the BookKeeper TLP. All that
is required now for this, is approval from the relevant press offices in the
companies mentioned, and it's ready to go.

= Releases =
Our last release was 4.3.0, released on 2014-10-14.

Release 4.2.4 is currently being voted on, so we expect it to be released in
the next week.
We are currently working on the 4.3.1 release also, which should follow soon
after 4.2.4.

= Community Status =
There have been no committers added since we became TLP (2014-11-19).

The last committer added, when we were a subproject, was Rakesh
Radhakrishnan on 24th July 2014.

49 subscribers in dev@bookkeeper.apache.org
66 subscribers in user@bookkeeper.apache.org

824 issues opened to date, 10 since 2014-12-12
563 issues resolved to date, 4 since 2014-12-12
50 people have reported issues, 4 since 2014-12-12
24 people have contributed patches, 3 since 2014-12-12

17 Dec 2014 [Ivan Kelly / Greg]

Bookkeeper is a distributed, reliable, and high performance
logging service. The project also includes Hedwig which is
a highly scalable Pub/Sub service built on top of ZooKeeper
and Bookkeeper with strong durability guarantees.

= Project Status =
Since becoming TLP (2014-11-19), focus has been on getting our
new infrastructure set up. There were some delays in getting the
mailing list up and running, but it's all resolved now. Subsequently,
everything that depended on the mailing lists was delayed. We are
current voting on a set of bylaws.

Development work has been low over the last month, but a lot of work
has been done to improve the documentation and accessibility of the
project (new website, new client tutorial, etc).

= Releases =
Our last release was 4.3.0, released on 2014-10-14. We are
currently in the process of voting for a release plan for 4.3.1 and
4.2.4.

= Community Status =
There have been no committers added since we became TLP (2014-11-19).
The last committer added, when we were a subproject, was Rakesh
Radhakrishnan on 24th July 2014.

50 subscribers in dev@bookkeeper.apache.org
66 subscribers in user@bookkeeper.apache.org

811 issues opened to date, 34 since 2014-10-01
556 issues resolved to date, 14 since 2014-10-01
50 people have reported issues, 9 since 2014-10-01
24 people have contributed patches, 6 since 2014-10-01

19 Nov 2014

Establish the Apache BookKeeper Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to
 the public, related to distributed, fault-tolerant,
 and high-performance logging.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the "Apache BookKeeper Project",
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache BookKeeper Project be and hereby is
 responsible for the creation and maintenance of software
 related to distributed, fault-tolerant, and high-performance logging;
 and be it further

 RESOLVED, that the office of "Vice President, Apache BookKeeper” be
 and hereby is created, the person holding such office to serve at the
 direction of the Board of Directors as the chair of the Apache BookKeeper
 Project, and to have primary responsibility for management of the projects
 within the scope of responsibility of the Apache BookKeeper Project; and
 be it further

 RESOLVED, that the persons listed immediately below be and
 hereby are appointed to serve as the initial members of the
 Apache BookKeeper Project:

  * Sijie Guo (sijie@apache.org)
  * Flavio Junqueira (fpj@apache.org)
  * Ivan Kelly (ivank@apache.org)
  * Rakesh Radhakrishnan (rakeshr@apache.org)
  * Ben Reed (breed@apache.org)
  * Uma Maheswara Rao G (umamahesh@apache.org)
  * Jiannan Wang (jiannan@apache.org)

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ivan Kelly
 be appointed to the office of Vice President, Apache BookKeeper, to
 serve in accordance with and subject to the direction of the
 Board of Directors and the Bylaws of the Foundation until
 death, resignation, retirement, removal or disqualification,
 or until a successor is appointed; and be it further

 RESOLVED, that the initial Apache BookKeeper PMC be and hereby
 is tasked with the creation of a set of bylaws intended to encourage
 open development and increased participation in the Apache
 BookKeeper Project; and be it further

 RESOLVED, that the Apache BookKeeper Project be and hereby
 is tasked with the migration and rationalization of the Apache
 BookKeeper subproject; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 BookKeeper subproject encumbered upon the Apache ZooKeeper
 Project are hereafter discharged.

 Special Order 7G, Establish the Apache BookKeeper Project, was
 approved by Unanimous Vote of the directors present.