On Wed, Jul 26, 2017 at 3:50 AM, atracymartin <atracymar...@gmail.com>
wrote:

> I am interested in learning more about the decision to merge DL into BK.
> What will that look like, and when will it be available?  What can I do to
> help?
>

Thank you Martin.

In short, DL (especially the core library) is more an extension to BK to
provide continuous log stream abstraction over bookkeeper.
Merge DL into BK is to bring a high level API on bookkeeper to simplify the
usage of BookKeeper and consolidate the efforts on building log stream
abstraction over BookKeeper. The vote
<http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3CCAO2yDya-%3D0cBfUM0SsL5kuf9HJ1G%3DpL7Z_%3D7Ps%2BTQgqwJs%3DCaA%40mail.gmail.com%3E>
link provides more insights about the considerations behind this.

>> What will that look like, and when will it be available?

DL has become a sub-project of BookKeeper already. But there are a few
INFRA tasks that BK PMC is working with INFRA team on it.
The git repo, mailing lists will remain same in the following few months.

At the same time, there are a couple of things happening (or will happen):

- the documentation, release procedure, ci builds will be aligned between
projects.
- we are working with Pulsar community for combining its managedledger
library (built over bookkeeper) with DL to provide a more robust log stream
library over bookkeeper.


>> What can I do to help?

Both BK and DL have some good projects for contributions.

Specially on the topic of merging DL into BK, there is one big outstanding
topic is to work with Pulsar community for combining its managedledger
library with DL to provide a unified log stream library on bookkeeper.
We started a gist a while ago -
https://gist.github.com/sijie/d7a242eb7d185e182b9a72c63534830b If you are
interested in this topic, feel free to participant.

Besides features/projects,

- Documentation is an area that need more contributions. Both BK and DL
don't have good documentation - the internal details of bookkeeper (for
developers), how to use it (for users), how to deploy and operate a cluster
(for administrators).
  It can be a good start to help us writing documentation around how to use
it and examples.
- Automate builds and release procedure can be another good area to
contribute as well.

Hope this helps.

- Sijie









>
>
> Sent from my T-Mobile 4G LTE Device
> -------- Original message --------From: Sijie Guo <guosi...@gmail.com>
> Date: 7/25/17  8:22 PM  (GMT-05:00) To: dev@bookkeeper.apache.org Cc:
> d...@distributedlog.incubator.apache.org Subject: Re: [DISCUSS] Slack
> Channel for BookKeeper
> Currently BK doesn't has one yet.
>
> On Tue, Jul 25, 2017 at 9:29 AM, Henry Saputra <henry.sapu...@gmail.com>
> wrote:
>
> > Is Apache BookKeeper has its own Slack team? If it has then we could just
> > add a channel for DistLog.
> >
> > - Henry
> >
> > On Mon, Jul 24, 2017 at 11:42 PM, Enrico Olivelli <eolive...@gmail.com>
> > wrote:
> >
> > > Awesome +1
> > >
> > > Il mar 25 lug 2017, 05:39 Dustin Castor <dustincas...@yahoo.com.invali
> d>
> > > ha
> > > scritto:
> > >
> > > > Agreed! Or an IRC.
> > > >
> > > > On Monday, July 24, 2017, 6:50:22 PM PDT, Jia Zhai <
> > zhaiji...@gmail.com>
> > > > wrote:
> > > >
> > > > 👍 It is great to have a slack channel. It make things more effective
> > and
> > > > smooth.
> > > >
> > > > On Tue, Jul 25, 2017 at 8:11 AM, Sijie Guo <guosi...@gmail.com>
> wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > What do you guys all think about having a dedicated slack channel
> for
> > > > > informal discussion for the community? There are a handful of
> Apache
> > > > > projects are doing that already, there are also ways to have a bot
> > that
> > > > > sends daily digest of the conversation to the mailing lists (to
> keep
> > > the
> > > > > records in ASF infrastructure).
> > > > >
> > > > > As the followup steps for merging DL into BookKeeper, we are
> > > transferring
> > > > > the DL slack channel to BookKeeper PMC. We can just make it a BK
> > slack
> > > > > channel, and have different channels under it for different
> > > discussions.
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > - Sijie
> > > > >
> > >
> > > --
> > >
> > >
> > > -- Enrico Olivelli
> > >
> >
>

Reply via email to