This was extracted (@ 2024-04-17 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.
WARNING: these pages may omit some original contents of the minutes.
Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache BookKeeper was founded 2014-11-19 (9 years ago) There are currently 31 committers and 18 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Hang Chen on 2023-03-14. - No new committers. Last addition was Wenbing Shen on 2023-07-04. ## Project Activity: The project is going well, we are going to cut a new major release 4.17.0. Most of the feature requests and improvements come from Apache Pulsar users. 4.16.4 was released on 2024-01-29 4.15.5 was released on 2023-12-19 4.16.3 was released on 2023-09-19 4.14.8 was released on 2023-09-11 ## Community Health: The community is in good shape, we also have some contributor that is becoming more and more active. Hopefully we will be able to invite some new committers in the next quarter. Mailing list data: - dev@bookkeeper.apache.org had a 81% increase in traffic in the past quarter (40 emails compared to 22) - 100 commits in the past quarter (3% increase) 29 code contributors in the past quarter (81% increase)
No report was submitted.
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache BookKeeper was founded 2014-11-19 (9 years ago) There are currently 31 committers and 18 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Hang Chen on 2023-03-14. - No new committers. Last addition was Wenbing Shen on 2023-07-04. ## Project Activity: In the past quarter the activity slowed down a little bit. 4.16.1 was released on 2023-05-02. 4.16.0 was released on 2023-04-09. 4.15.4 was released on 2023-03-13. ## Community Health: Traffic on GitHub and on the mailing lists slowed down a little bit in the past quarter. The community is still adopting the versions we released in the firs half of the year. Nothing to worry about. Some interesting stats: - dev@bookkeeper.apache.org had a 25% decrease in traffic in the past quarter (43 emails compared to 57) - 69 commits in the past quarter (-44% change) - 63 PRs opened on GitHub, past quarter (-22% change) - 18 code contributors in the past quarter (12% increase)
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache BookKeeper was founded 2014-11-19 (9 years ago) There are currently 31 committers and 18 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Hang Chen on 2023-03-14. - Wenbing Shen was added as committer on 2023-07-04 ## Project Activity: The project isis moving forward well, we are cutting releases both for bugfixes and new features. Recent releases: 4.16.1 was released on 2023-05-02. 4.16.0 was released on 2023-04-09. 4.15.4 was released on 2023-03-13. ## Community Health: The project is healthy. There is a little slowdown in the activity but we see users asking questions, especially on the Slack workspace. Developers use also the mailig list to collaborate and to discuss. We added a committer last month.
WHEREAS, the Board of Directors heretofore appointed Sijie Guo (sijie) to the office of Vice President, Apache BookKeeper, and WHEREAS, the Board of Directors is in receipt of the resignation of Sijie Guo 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 Enrico Olivelli (eolivelli) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Sijie Guo is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache BookKeeper, and BE IT FURTHER RESOLVED, that Enrico Olivelli 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 7C, Change the Apache BookKeeper Project Chair, was approved by Unanimous Vote of the directors present.
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Issues: - There are no issues requiring board attention at this time. ## Membership Data: Apache BookKeeper was founded 2014-11-19 (8 years ago) There are currently 30 committers and 18 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - Hang Chen was added to the PMC on 2023-03-14 - No new committers. Last addition was Shiji Lu on 2022-10-06. ## Project Activity: Recent releases: - 4.16.1 was released on 2023-05 - 4.16.0 was released on 2023-04 - 4.15.4 was released on 2023-03 - 4.14.7 was released on 2023-02 - 4.14.6 was released on 2023-01 - The BookKeeper 4.16.0 is a milestone to support DirectIO and have a lot of performance improvements. - We continue to have many "BookKeeper Proposal" getting submitted, discussed and voted by the community: BP-59:Refactor ByteBuf release method BP-60:Change PCBC limitStatsLogging default value to true BP-61: Revert BP-59 to release ByteBuf using ReferenceCountUtil.release() instead of ReferenceCountUtil.safeRelease() BP-62: Streamline batch add requests BP-63: Make all PacketProcessorBaseV3 recyclable - We also started a project to tune the performance for handling many small entries and got significantly performance improvement. - BookKeeper has reached 172 contributors on the main Github repo (It was 168 contributors in December 2022) - BookKeeper community is discussing rotating the PMC Chair. ## Health report: The community is pretty healthy currently, new features and bugfixes are coming both from committers and new contributors and we recently added one PMC member. New issues and PR review time is a bit long, maybe we need to invite more Committers. ## Community Health: - Activity on the mail lists and PRs increased a lot with more committers and contributors participate in discussions and PR reviews. - dev@bookkeeper.apache.org had a 40% increase in traffic in the past quarter (117 emails compared to 83) - There is low traffic on the user@ mailing list probably because BookKeeper is very low level and most of the times people who reach out to the community start directly from the dev@ mailing list. ### Github activity - 202 commits in the past quarter (42% increase) - 32 code contributors in the past quarter (6% increase) - 150 PRs opened on GitHub, past quarter (31% increase) - 148 PRs closed on GitHub, past quarter (46% increase) - 26 issues opened on GitHub, past quarter (-13% change) - 18 issues closed on GitHub, past quarter (5% increase)
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Issues: Overall the community is doing well. On the PMC side we can note that we had a CVE and it took much time in order to handle it properly. This is something that we are still not tackling on the PMC. There are a few contributors who are doing very well and it is probably worth considering inviting them as committers. ## Membership Data: Apache BookKeeper was founded 2014-11-19 (8 years ago) There are currently 30 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Andrey Yegorov on 2022-03-18. - No new committers. Last addition was Shiji Lu on 2022-10-05. ## Project Activity: Recent releases: 4.15.3 was released on 2022-11-14. 4.14.6 was released on 2022-01-09. All the release lines before 4.14.x have been declared EOL. We are going to cut a new major release (4.16.0) ## Community Health: The community is active, in mailing list discussion, on our slack workspace, on GH pull requests and BPs (BookKeeper proposals, that is our way of discussing public API changes and big features)
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Issues: The community is pretty healthy currently, new features and bugfixes are coming both from committers and new contributors and we recently added some committers. One issue is that we missed to send the report to the Board a couple of times, and also sometimes it takes much time to have 3 binding VOTEs on release candidetes. Maybe it is time to add new members to the PMC or to revive the PMC. A CVE has been found (https://www.cve.org/CVERecord?id=CVE-2022-32531) and it took much time before we could address it, ## Membership Data: Apache BookKeeper was founded 2014-11-19 (8 years ago) There are currently 30 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Andrey Yegorov on 2022-03-18. - Shiji Lu was added as committer on 2022-10-05 ## Project Activity: Recent releases: 4.15.3 was released on 2022-11. 4.14.5 was released on 2022-05. ## Community Health: Discussions happen on the dev@ mailing list and on GH issues. There is low traffic on the user@ mailing list probably because BookKeeper is very low level and most of the times people who reach out to the community start directly from the dev@ mailing list. - dev@bookkeeper.apache.org had a 38% increase in traffic in the past quarter (104 emails compared to 75) - issues@bookkeeper.apache.org had a 130% increase in traffic in the past quarter (1286 emails compared to 558) - 259 commits in the past quarter (33% increase) - 47 code contributors in the past quarter (30% increase) - 159 PRs opened on GitHub, past quarter (23% increase)
No report was submitted.
@Sander: pursue a report for BookKeeper
No report was submitted.
No report was submitted.
No report was submitted.
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Issues: There is no particular issue relevant for the board. The project is cutting releases, bug fixes and new features are being contributed. ## Membership Data: Apache BookKeeper was founded 2014-11-18 (7 years ago) There are currently 28 committers and 17 PMC members in this project. The Committer-to-PMC ratio is roughly 7:5. Community changes, past quarter: - Andrey Yegorov was added to the PMC on 2022-03-17 - Nicolò Boschi was added as committer on 2022-03-29 - ZhangJian He was added as committer on 2022-05-04 ## Project Activity: We cut a new feature release: Apache BookKeeper 4.15.0 ## Community Health: There is activity on GitHub, with new issues, users that ask for questions and new patches. Slack is also quite active. The activity in the ML is quite low.
## Description: The mission of the BookKeeper community is to advance and develop software for append-only, replicated logs in distributed systems. Such logs can be used as the foundation in a number of scenarios, including messaging, streaming and even building replicated state machines generally. ## Issues: There is no particular issue relevant for the board. The project is cutting releases, bug fixes and new features are being contributed. ## Membership Data: Apache BookKeeper was founded 2014-11-18 (7 years ago) There are currently 26 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Charan Reddy G on 2019-07-23. - Prashant Kumar was added as committer on 2021-12-31 ## Project Activity: We cut a few releases in the past two quaters. Apache BookKeeper 4.14.2, 4.14.3, and 4.14.4. New contributions and discussions are around: - Etcd metdata management - Website issues - JDK 11 isssues - Ledger allocation - etc ## Community Health: There is activity on GitHub, with new issues, users that ask for questions and new patches. Slack is also quite active. The activity in the ML is quite low.
No report was submitted.
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Issues: Currently there is no issue for the board. ## Membership Data: Apache BookKeeper was founded 2014-11-19 (7 years ago) There are currently 24 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Charan Reddy G on 2019-07-24. - No new committers. Last addition was Yong Zhang on 2021-07-08. We are onboarding Jack Vanlightly as new committer, he has already accepted the invitation. ## Project Activity: Recent releases: - 4.14.2 was released on 2021-08-24 - 4.14.1 was released on 2021-06-01 - 4.14.0 was released on 2021-05-25 - 4.13.0 was released on 2021-02-25 ## Community Health: The community is in good shape. There are a few ongoing works. We have recently invited a new committer and there are other folks in the community that will be probably be invited soon. Discussions happen mostly on GitHub issues and in the mailing list. We have a slack channel but it is recently less active, it is used mostly by users who reach out to get support. We are trying to encourage the usage of the user@ mailing list but slack is somehow more easy for new comers. - dev@bookkeeper.apache.org had a 89% increase in traffic in the past quarter (110 emails compared to 58) - issues@bookkeeper.apache.org had a 193% increase in traffic in the past quarter (949 emails compared to 323) - user@bookkeeper.apache.org had a 85% decrease in traffic in the past quarter (2 emails compared to 13) - 90 commits in the past quarter (181% increase) - 24 code contributors in the past quarter (71% increase) - 97 PRs opened on GitHub,past quarter (259% increase) - 64 PRs closed on GitHub, past quarter (156% increase) - 24 issues opened on GitHub, past quarter (9% increase) - 18 issues closed on GitHub, past quarter (63% increase)
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Issues: There is no particular issue relevant for the board. The project is cutting releases, bug fixes and new features are being contributed. Unfortunately we do not have many new contributors, most of the folks that contribute to the project come from the Apache Pulsar project. ## Membership Data: Apache BookKeeper was founded 2014-11-18 (7 years ago) There are currently 24 committers and 16 PMC members in this project. The Committer-to-PMC ratio is 3:2. Community changes, past quarter: - No new PMC members. Last addition was Charan Reddy G on 2019-07-23. - Yong Zhang was added as committer on 2021-07-08 ## Project Activity: We cut two releases in June 2021. Apache BookKeeper 4.14.0 and 4.14.1. ## Community Health: There is activity on GitHub, with new issues, users that ask for questions and new patches. Slack is also quite active. The activity in the ML is quite low. We had a talk at the recent PulsarSummit about Apache BookKeeper.
No report was submitted.
No report was submitted.
@Sander: pursue a roll call for BookKeeper
No report was submitted.
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated Log Services which can be used to build replicated state machines. During the past years, it became a more general basic building block for Distributed Storage Systems, as Apache Pulsar and other OpenSource projects like Pravega.io and HerdDB.org. ## Issues: No relevant issues for the board at the moment. ## Membership Data: Apache BookKeeper was founded 2014-11-18 (6 years ago) There are currently 23 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Charan Reddy G on 2019-07-23. - No new committers. Last addition was Anup Ghatage on 2020-10-19. ## Project Activity: The project is quite active even if we are not cutting releases very often. - 4.12.1 was released on 2021-01-12 - 4.12.0 was released on 2020-11-17 The project is moving forward with new features and bugfixes. e.g. - Enhance the Stream Store and TableService; ## Community Health: Since some of the issues are discussed in Slack or Pulsar’s channels, the email threads get a small decrease. GitHub activity： - 108 commits in the past quarter (38% increase) - 24 code contributors in the past quarter (9% increase) - 62 PRs opened on GitHub, past quarter (3% increase0 - 64 PRs closed on GitHub, past quarter (6% increase) - 49 issues opened on GitHub, past quarter (75% increase) - 21 issues closed on GitHub, past quarter (-22% decrease) Mailing List activity: - dev@bookkeeper.apache.org had a 12% decrease in traffic in the past quarter (88 emails compared to 100) - issues@bookkeeper.apache.org had a 8% decrease in traffic in the past quarter (563 emails compared to 607):
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated Log Services which can be used to build replicated state machines. During the past years, it became a more general basic building block for Distributed Storage Systems, as Apache Pulsar and other OpenSource projects like Pravega.io and HerdDB.org. ## Issues: No relevant issues for the board at the moment. ## Membership Data: Apache BookKeeper was founded 2014-11-19 (6 years ago). There are currently 23 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. The last addition was Charan Reddy G on 2019-07-24. - Anup Ghatage was added as a committer on 2020-10-20 ## Project Activity: The project is quite active even if we are not cutting releases very often. - 4.11.1 was released on 2020-10-22 - 4.11.0 was released on 2020-07-09 The project is moving forward with new features and bugfixes. e.g. - Moving BooKeeper to JDK11; - BP-41: Separated BookieID from BookieSocketAddress. ## Community Health: As the Pulsar community grows, The feature requirements and enhancements for BookKeeper get growing. and this causes the contributions and mail list discussions for BookKeeper both get increased. GitHub activity： - 24 code contributors in the past quarter (71% increase) - 71 commits in the past quarter (9% increase) - 59 PRs opened on GitHub, past quarter (31% increase) - 60 PRs closed on GitHub, past quarter (-1% decrease) - 26 issues closed on GitHub, past quarter (136% increase) - 24 issues opened on GitHub, past quarter (-4% decrease) Mailing List activity: - dev@bookkeeper.apache.org had a 37% increase in traffic in the past quarter (111 emails compared to 81) - issues@bookkeeper.apache.org had a 45% decrease in traffic in the past quarter (635 emails compared to 1144) - user@bookkeeper.apache.org had a 33% increase in traffic in the past quarter (12 emails compared to 9) Meetups and Conferences: - We had delivered a few talks about BookKeeper at ApacheCon@Home. - Also there will be some BookKeeper talks at PulsarSummit Asia, a conference devoted to Apache Pulsar.
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated Log Services which can be used to build replicated state machines. During the past years it became a more general basic building block for Distributed Storage Systems, as Apache Pulsar and other OpenSource projects like Pravega.io and HerdDB.org. ## Issues: No relevant issues for the board at the moment. ## Membership Data: Apache BookKeeper was founded 2014-11-19 (6 years ago) There are currently 22 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Charan Reddy G on 2019-07-24. - No new committers. Last addition was Rajan Dhabalia on 2020-03-23. ## Project Activity: The project is quite active even if we are not cutting releases very often. 4.11.0 was release on 2020-07-09 4.10.0 was released on 2019-11-06. The project is moving forward with new features and bugfixes. ## Community Health: New users are often using the Slack channel instead of the ML in order to get in touch with the project, this has the effect to a reduced activity on the user@ mailing list. The activity on the ML is stable on dev@, and we are also following a formal process to get major changes in (BookKeeper Proposals design documents). We had a BookKeeper dedicated track at PulsarSummit.com, a conference devoted to Apache Pulsar. We also have a few talks about BookKeeper at ApacheCon@Home. We recently moved to GitHub Actions the CI jobs relevant to testing Pull Requests.
## 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. It is also the log segment store for Apache DistributedLog and message store for Apache Pulsar. Apache DistributedLog is a high-level API and service layer for Apache BookKeeper, providing easier access to the BookKeeper primitives. It is a subproject of Apache BookKeeper. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache BookKeeper was founded 2014-11-19 (5 years ago) There are currently 23 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. - Rajan Dhabalia was added as committer on 2020-03-23 ## Project Activity: Recently, we've seen lots of activity from upstream consumers such as Apache Pulsar. Companies such as Salesforce and Diennea contributing back to the community. We are also seeing new interest from users at Dell EMC contributing back and starting conversations. Several bugs (issues) were opened and fixed from these upstream consumers which will be going into our next release. Some of the important features being worked on/recently merged are: - Bookkeeper Proposal - 38: Publish Bookie Service Info on Metadata Service - Bookkeeper Proposal - 40: Audit Logging for Apache Bookkeeper - Migrated Project CI from Jenkins to Github Actions on 2020-01-22. Releases - 4.10.0 was released on 2019-11-06. - 4.9.2 was released on 2019-05-16. - Supporting project Bookkeeper Visual Manager released v1.0.0 on 2020-04-12. ## Community Health: The community has been active in making infrastructural changes to Apache Bookkeeper this past quarter. We have had initiatives that moved us to Github Actions from Jenkins and also cut down the build and test time by more than 50%. Another development activity has seemed to go from mailing lists to our slack channel (apachebookkeeper.slack.com) where we had around 38 new users of Apache Bookkeeper. In the past quarter, the above activity has resulted in the following GitHub activity: - 38 PRs opened (8% increase) - 40 PRs closed (48% increase) - 50 commits (51% increase) - 20 code contributors (66% increase) Mailing List activity: - 1272 emails in issues@bookkeeper.apache.org (4% increase) - 30 emails in user@bookkeeper.apache.org - 59 emails in the dev@bookkeeper.apache.org - We'll be pushing to bring the discussions back to the mailing lists. Meetups and Conferences: - Several talks are scheduled for the Bookkeeper Track in the Apache Pulsar Summit 2020 to be held in 17 and 18th June 2020.
## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Issues: There are no blocker issues requiring board attention at this time. ## Membership Data: Apache BookKeeper was founded 2014-11-18 (5 years ago) There are currently 21 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Charan Reddy G on 2019-07-23. - No new committers. Last addition was Andrey Yegorov on 2018-02-09. ## Project Activity: Recent releases: 4.10.0 was released on 2019-11-06. 4.9.2 was released on 2019-05-16. 4.9.1 was released on 2019-04-06. ## Community Health: ### Community We are leveraging Pulsar for growing BookKeeper community. Pulsar Summit has a dedicated `bookkeeper` track for the community to present bookkeeper related talks. This will drive more participation from both communities. ### Committers We did not add any new committer within last year. We have a good amount of small contributions but no one is yet ready to be invited as committer. We are trying to engage more with current contributors. Most of current contributions come from other downstream Open Source projects that are using BookKeeper as building block. We got recent feedback of usage of BookKeeper and DistributeLog by new non open source projects. ### Activities dev@bookkeeper.apache.org had a 80% increase in traffic in the past quarter (123 emails compared to 68) user@bookkeeper.apache.org had a 271% increase in traffic in the past quarter (52 emails compared to 14) 32 commits in the past quarter (-40% decrease) 12 code contributors in the past quarter (-29% decrease) 32 PRs opened on GitHub, past quarter (-31% decrease) 25 PRs closed on GitHub, past quarter (-13% decrease) 25 issues opened on GitHub, past quarter (66% increase) 8 issues closed on GitHub, past quarter (100% increase)
## 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. Apache DistributedLog is a high-level API and service layer for Apache BookKeeper, providing easier access to the BookKeeper primitives. It is a subproject of Apache BookKeeper. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache BookKeeper was founded 2014-11-19 (5 years ago) There are currently 21 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Charan Reddy G on 2019-07-24. - No new committers. Last addition was Andrey Yegorov on 2018-02-09. ## Project Activity: - 4.9.1 was released on April 7 2019 - 4.9.2 was released on May 16 2019 - 4.10.0: was released on November 6 2019 - The growth of Apache Pulsar community also help grow the adoption of BookKeeper. This helps building the ecosystem around BookKeeper. - The project is also extending its scope to cover long term distributed storage and now bundles a new KV distributed database (StreamStorage). - We released a new Python client for the StreamStorage service. - We are working on a brand new CLI interface GitHub issues: 19 issues opened on GitHub, past quarter (35% increase) 35 issues closed on GitHub, past quarter (191% increase) GitHub PR activity: 37 PRs opened on GitHub, past quarter (2% increase) 26 PRs closed on GitHub, past quarter (-33% decrease) ## Community Health: - During the last quarter there development slowed down a little and we missed one scheduled release (we started a Time based release plan this year). - During the last months new users and contributors appeared especially from Apache Pulsar community and from other OSS projects that were born recently and are based on Apache BookKeeper. - Mailing list discussions are brisk, in particularly around the active projects.
## 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. Apache DistributedLog is a high-level API and service layer for Apache BookKeeper, providing easier access to the BookKeeper primitives. It is a subproject of Apache BookKeeper. ## Issues: There are no issues requiring board attention at this time. ## Membership Data: Apache BookKeeper was founded 2014-11-19 (5 years ago) There are currently 21 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Charan Reddy G was added to the PMC on 2019-07-24 - No new committers. Last addition was Andrey Yegorov on 2018-02-10. ## Project Activity: Recent releases: 4.9.2 was released on 2019-05-17. 4.9.1 was released on 2019-04-06. 4.8.2 was released on 2019-03-18. 4.8.0 was released on 2018-09-25. Currently the community is working on releasing 4.10.0. The two releases will be going out soon. ## Community Health: The community is a bit slow. Because the committers and PMC members have a bit overlapped between Pulsar and BookKeeper. So a lot of them have been focused on growing the adoptions of Pulsar and hence BookKeeper. The adoptions of Pulsar has been increased a lot and so does BookKeeper. The members are able to put more focuses on BookKeeper in the next month.
## 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.
Apache DistributedLog is a high-level API and service layer for
Apache BookKeeper, providing easier access to the BookKeeper
primitives. It is a subproject of Apache BookKeeper.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- 4.9.0 was released on January 31 2019
- 4.8.2 was released on March 19 2019
- 4.9.1 was released on April 7 2019
- 4.9.2 is under release voting
- The growth of Apache Pulsar community also help grow the adoption
of BookKeeper.
This helps building the ecosystem around BookKeeper.
## Health report:
- Development continues at a steady pace. We are merging multiple PRs per
week on average.
- Mailing list and slack discussions are brisk, in particularly around the
active projects.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Enrico Olivelli on Fri Feb 23 2018
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Andrey Yegorov at Sat Feb 10 2018
## Releases:
- 4.9.0 was released on January 31 2019
- 4.8.2 was released on March 19 2019
- 4.9.1 was released on April 7 2019
## Mailing list activity:
- dev@bookkeeper.apache.org:
- 104 subscribers (down -1 in the last 3 months):
- 67 emails sent to list (112 in previous quarter)
- distributedlog-commits@bookkeeper.apache.org:
- 12 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- distributedlog-dev@bookkeeper.apache.org:
- 41 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- distributedlog-issues@bookkeeper.apache.org:
- 9 subscribers (up 0 in the last 3 months):
- 6 emails sent to list (2 in previous quarter)
- distributedlog-user@bookkeeper.apache.org:
- 26 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- issues@bookkeeper.apache.org:
- 8 subscribers (up 0 in the last 3 months):
- 1825 emails sent to list (1867 in previous quarter)
- user@bookkeeper.apache.org:
- 117 subscribers (up 0 in the last 3 months):
- 8 emails sent to list (11 in previous quarter)
## 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.
Apache DistributedLog is a high-level API and service layer for
Apache BookKeeper, providing easier access to the BookKeeper
primitives. It is a subproject of Apache BookKeeper.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- 4.9.0 was released on Sat, Feb 6, 2019
- The growth of Apache Pulsar community also help grow the adoption
of BookKeeper. This helps building the ecosystem around BookKeeper.
## Health report:
- Development continues at a steady pace. We are merging multiple PRs per
week on average.
- Mailing list and slack discussions are brisk, in particularly around the
active projects.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Enrico Olivelli on Fri Feb 23 2018
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Andrey Yegorov at Fri Feb 09 2018
## Releases:
- 4.9.0 was released on Sat, Feb 6, 2019
- 4.7.3 was released on Fri, Dec 7, 2018
- 4.8.1 was released on Fri, Nov 30, 2018
## Mailing list activity:
- Discussions mostly run on dev@ mailing list, distributedlog lists
are mostly unused, now that the project as been merged completely with
BookKeeper and users started to use the version bundled with
BookKeeper releases.
- dev@bookkeeper.apache.org:
- 105 subscribers (up 2 in the last 3 months):
- 119 emails sent to list (121 in previous quarter)
- distributedlog-commits@bookkeeper.apache.org:
- 12 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- distributedlog-dev@bookkeeper.apache.org:
- 41 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- distributedlog-issues@bookkeeper.apache.org:
- 9 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (4 in previous quarter)
- distributedlog-user@bookkeeper.apache.org:
- 26 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- issues@bookkeeper.apache.org:
- 8 subscribers (up 0 in the last 3 months):
- 1994 emails sent to list (2433 in previous quarter)
- user@bookkeeper.apache.org:
- 118 subscribers (up 3 in the last 3 months):
- 14 emails sent to list (17 in previous quarter)
## 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.
Apache DistributedLog is a high-level API and service layer for
Apache BookKeeper, providing easier access to the BookKeeper
primitives. It is a subproject of Apache BookKeeper.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- 4.8.0 was released on Wed Sep 26 2018
- 4.8.1 is going to be released
- The growth of Apache Pulsar community also help grow the adoption
of BookKeeper.
This helps building the ecosystem around BookKeeper.
## Health report:
- Development continues at a steady pace. We are merging multiple PRs per
week on average.
- Mailing list and slack discussions are brisk, in particularly around the
active projects.
- The community holds a bi-weekly meeting on Hangout.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Enrico Olivelli on Thu Feb 22 2018
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Andrey Yegorov at Fri Feb 09 2018
## Releases:
- 4.7.1 was released on Tue Jun 19 2018
- 4.8.0 was released on Wed Sep 26 2018
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Enrico Olivelli on Fri Feb 23 2018
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Andrey Yegorov at Fri Feb 09 2018
## Releases:
- 4.8.0 was released on Wed Sep 26 2018
## Mailing list activity:
- Discussions mostly run on dev@ mailing list, distributedlog lists
are mostly unused, now that the project as been merged completely with
BookKeeper and users started to use the version bundled with
BookKeeper releases.
- dev@bookkeeper.apache.org:
- 103 subscribers (down -1 in the last 3 months):
- 125 emails sent to list (132 in previous quarter)
- distributedlog-commits@bookkeeper.apache.org:
- 12 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (2 in previous quarter)
- distributedlog-dev@bookkeeper.apache.org:
- 41 subscribers (down -1 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- distributedlog-issues@bookkeeper.apache.org:
- 9 subscribers (up 0 in the last 3 months):
- 4 emails sent to list (2 in previous quarter)
- distributedlog-user@bookkeeper.apache.org:
- 26 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- issues@bookkeeper.apache.org:
- 8 subscribers (down -1 in the last 3 months):
- 2686 emails sent to list (1952 in previous quarter)
- user@bookkeeper.apache.org:
- 115 subscribers (down -2 in the last 3 months):
- 20 emails sent to list (39 in previous quarter)
## 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.
Apache DistributedLog is a high-level API and service layer for Apache
BookKeeper, providing easier access to the BookKeeper primitives. It is a
subproject of Apache BookKeeper.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- 4.7.1 was released on Tue Jun 19 2018
- 4.8.0 was scheduled to be release in August. It is delayed due to some
discussions around metadata upgrade.
- Apache Pulsar (incubating) has fully integrated with the official
BookKeeper release 4.7.0. The growth of Pulsar community also help grow the
adoption of BookKeeper.
- Deep integration between Pulsar and BookKeeper, for example Pulsar
Functions integration with bookkeeper table service. This helps building
the ecosystem around BookKeeper.
## Health report:
- Development continues at a steady pace. We are merging multiple PRs per day
on average.
- Mailing list and slack discussions are brisk, in particularly around the
active projects.
## PMC changes:
- Currently 15 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Enrico Olivelli on Thu Feb 22 2018
## Committer base changes:
- Currently 21 committers.
- No new committers added in the last 3 months
- Last committer addition was Andrey Yegorov at Fri Feb 09 2018
## Releases:
- 4.7.1 was released on Tue Jun 19 2018
## Mailing list activity:
- dev@bookkeeper.apache.org:
- 105 subscribers (up 1 in the last 3 months):
- 132 emails sent to list (327 in previous quarter)
- distributedlog-commits@bookkeeper.apache.org:
- 12 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (2 in previous quarter)
- distributedlog-dev@bookkeeper.apache.org:
- 42 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- distributedlog-issues@bookkeeper.apache.org:
- 9 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (67 in previous quarter)
- distributedlog-user@bookkeeper.apache.org:
- 26 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (0 in previous quarter)
- issues@bookkeeper.apache.org:
- 9 subscribers (up 0 in the last 3 months):
- 2088 emails sent to list (3044 in previous quarter)
- user@bookkeeper.apache.org:
- 117 subscribers (up 2 in the last 3 months):
- 39 emails sent to list (41 in previous quarter)
## 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.
Apache DistributedLog is a high-level API and service layer for Apache
BookKeeper, providing easier access to the BookKeeper primitives. It is a
subproject of Apache BookKeeper.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- 4.6.2 was released on 09th April 2018.
- 4.7.0 was released on 17th April 2018. It is also the first release of
Apache DistributedLog after it is merged as sub modules of Apache
BookKeeper. This release adopted 7 BPs and 446 issues fix.
- Yahoo branch is fully merged back to upstream, and Apache Pulsar
(incubating) starts using official BookKeeper release 4.7.0 for its
upcoming 2.0 release
- The number of BookKeeper proposals are increasing, due to increased
contributions.
- use etcd as metadata store
- Metadata API module
- BookKeeper Table Service
- BookKeeper Durability Anchor
## Health report:
- Development continues at a steady pace. We are merging multiple PRs per
day on average.
- Mailing list and slack discussions are brisk, in particularly around the
active projects.
## PMC changes:
- Currently 15 PMC members.
- New PMC members:
- Enrico Olivelli was added to the PMC on Fri Feb 23 2018
- Jia Zhai was added to the PMC on Fri Feb 23 2018
## Committer base changes:
- Currently 21 committers.
- New commmitters:
- Andrey Yegorov was added as a committer on Sat Feb 10 2018
- Sam Just was added as a committer on Fri Feb 09 2018
## Releases:
- 4.6.2 was released on Mon Apr 09 2018
- 4.7.0 was released on Tue Apr 17 2018
## Mailing list activity:
- dev@bookkeeper.apache.org:
- 104 subscribers (up 6 in the last 3 months):
- 348 emails sent to list (226 in previous quarter)
- distributedlog-commits@bookkeeper.apache.org:
- 12 subscribers (up 0 in the last 3 months):
- 2 emails sent to list (9 in previous quarter)
- distributedlog-dev@bookkeeper.apache.org:
- 42 subscribers (up 0 in the last 3 months):
- 11 emails sent to list (11 in previous quarter)
- distributedlog-issues@bookkeeper.apache.org:
- 9 subscribers (up 0 in the last 3 months):
- 79 emails sent to list (173 in previous quarter)
- distributedlog-user@bookkeeper.apache.org:
- 26 subscribers (up 0 in the last 3 months):
- 0 emails sent to list (12 in previous quarter)
- issues@bookkeeper.apache.org:
- 9 subscribers (up 2 in the last 3 months):
- 3302 emails sent to list (3647 in previous quarter)
- user@bookkeeper.apache.org:
- 115 subscribers (up 8 in the last 3 months):
- 46 emails sent to list (33 in previous quarter)
## Github activity
- 67 Github issues created in the last 3 months
- 34 Github issues closed/resolved in the last 3 months
- 216 Github Pull Requests created in the last 3 months
- 206 Github Pull Requests closed/resolved in the last 3 month
## 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.
Apache DistributedLog is a high-level API and service layer for
Apache BookKeeper, providing easier access to the BookKeeper
primitives. It is a subproject of Apache BookKeeper.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- 4.6.0 was released on 27th December 2017.
- 4.6.1 was released on 30th January 2018
- Continued work on merging changes from yahoo and salesforce changes
into apache master. The development work is converging into apache master.
- DistributedLog is merging as modules in BookKeeper. This will improve user
experiences and simpilify release procedure.
- The number of BookKeeper proposals are increasing, due to increased
contributions.
- LedgerType, Flags and StorageHints
- Bookie Scanner to improve data integrity
- Ledger Balancer
## Health report:
- Development continues at a steady pace. We are merging multiple PRs per day
on average.
- Mailing list and slack discussions are brisk, in particularly around the
active projects.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dave Rusek on Mon Aug 07 2017
## Committer base changes:
- Currently 19 committers.
- Yiming Zang was added as a committer on Sat Dec 09 2017
## Releases:
- Last release was 4.6.1 on 30th January 2018
- Last release of DistributedLog was 0.5.0 on September 17 2017
## 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 that
increased of mailing list activities.
- dev@bookkeeper.apache.org:
- 98 subscribers (up 7 in the last 3 months):
- 241 emails sent to list (1345 in previous quarter)
- distributedlog-commits@bookkeeper.apache.org:
- 12 subscribers (up 0 in the last 3 months):
- 11 emails sent to list (106 in previous quarter)
- distributedlog-dev@bookkeeper.apache.org:
- 41 subscribers (down -3 in the last 3 months):
- 12 emails sent to list (216 in previous quarter)
- distributedlog-issues@bookkeeper.apache.org:
- 9 subscribers (up 0 in the last 3 months):
- 204 emails sent to list (344 in previous quarter)
- distributedlog-user@bookkeeper.apache.org:
- 25 subscribers (up 2 in the last 3 months):
- 12 emails sent to list (30 in previous quarter)
- issues@bookkeeper.apache.org:
- 7 subscribers (down -1 in the last 3 months):
- 3996 emails sent to list (1846 in previous quarter)
- user@bookkeeper.apache.org:
- 107 subscribers (up 5 in the last 3 months):
- 33 emails sent to list (21 in previous quarter)
## Github activity
- 276 Github issues created in the last 3 months
- 258 Github issues closed/resolved in the last 3 months
- 195 Github Pull Requests created in the last 3 months
- 192 Github Pull Requests closed/resolved in the last 3 month
## 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.
Apache DistributedLog is a high-level API and service layer for
Apache BookKeeper, providing easier access to the BookKeeper
primitives. It is a subproject of Apache BookKeeper.
## Issues:
There are no issues requiring board attention at this time.
## Activity:
- We have moved to a time based schedule, releasing quarterly to
ensure new features ship at a regular interval. 4.6.0 will be the
first release of this kind.
- DistributedLog is aligning its release schedule with that of BookKeeper.
- 4.5.0 was released on 14th August 2017
- 4.5.1 was released on 22nd November 2017
- We are progressing towards a 4.6.0 release. The branch has been
frozen and we expect a release in the next two weeks.
- BookKeeper development now entirely in github. Jira has been made
read only. All jira issues have been migrated to github issues.
- Continued work on merging changes from yahoo's branch changes into
apache master.
- Active discussion on a number of projects:
- Relaxed durability
- New client API
- Improved documentation
## Health report:
- Development continues at a steady pace. We are merging one PR per
day on average.
- Mailing list and slack discussions are brisk, in particularly
around the active projects.
## PMC changes:
- Currently 13 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Dave Rusek on Mon Aug 07 2017
## Committer base changes:
- Currently 18 committers.
- No new committers added in the last 3 months
- Last committer addition was Dave Rusek at Tue Aug 08 2017
## Releases:
- Last release was 4.5.1 on November 22 2017
- Last release of DistributedLog was 0.5.0 on September 17 2017
## 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 that
increased of mailing list activities.
We switch to use "issues" mailing lists for notifications from github
discussion and make "dev" mailing lists purely for discussion. so
there is a drop at "dev" mailing list and increase at "issues"
mailing list.
- dev@bookkeeper.apache.org:
- 93 subscribers (up 2 in the last 3 months):
- 369 emails sent to list (2982 in previous quarter)
- distributedlog-commits@bookkeeper.apache.org:
- 12 subscribers (up 1 in the last 3 months):
- 81 emails sent to list (33 in previous quarter)
- distributedlog-dev@bookkeeper.apache.org:
- 44 subscribers (up 0 in the last 3 months):
- 89 emails sent to list (132 in previous quarter)
- distributedlog-issues@bookkeeper.apache.org:
- 9 subscribers (up 1 in the last 3 months):
- 432 emails sent to list (0 in previous quarter)
- distributedlog-user@bookkeeper.apache.org:
- 23 subscribers (up 3 in the last 3 months):
- 24 emails sent to list (11 in previous quarter)
- issues@bookkeeper.apache.org:
- 8 subscribers (up 0 in the last 3 months):
- 3134 emails sent to list (118 in previous quarter)
- user@bookkeeper.apache.org:
- 105 subscribers (up 3 in the last 3 months):
- 33 emails sent to list (38 in previous quarter)
## JIRA activity:
- 2 JIRA tickets created in the last 3 months
- 70 JIRA tickets closed/resolved in the last 3 months
## Github activity
- 171 Github issues created in the last 3 months (68 of these
migrated from JIRA)
- 76 Github issues closed/resolved in the last 3 months
- 104 Github Pull Requests created in the last 3 months
- 97 Github Pull Requests closed/resolved in the last 3 month
No report was submitted.
## 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
## 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
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
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
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
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
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
No report was submitted.
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
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
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.
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
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
Report was submitted but rejected and requested the following month.
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
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
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.