/cc (distributedlog-dev@)

Thank you Enrico and Jia. I created a master issue for BP-12 :
https://github.com/apache/bookkeeper/issues/439 for tracking all the
efforts on improving documentation.

I'd also like to call for volunteers to improve the documentation. You can
check #439 <https://github.com/apache/bookkeeper/issues/439> for more
details.

- Sijie

On Wed, Aug 9, 2017 at 7:21 AM, Jia Zhai <zhaiji...@gmail.com> wrote:

> I would like to help on the docker deployment part.
> Thanks.
>
> On Wed, Aug 9, 2017 at 7:39 PM, Enrico Olivelli <eolive...@gmail.com>
> wrote:
>
> > Il mer 9 ago 2017, 07:47 Sijie Guo <guosi...@gmail.com> ha scritto:
> >
> > > (/cc dev@distributedlog for calling for contributions)
> > >
> > > Hi all,
> > >
> > > Prior to 4.5.0, bookkeeper doesn't have good documentation. In 4.5.0
> > > release, the community did a lot of work on improving the current
> > > documentation along with new bookkeeper website. However, the
> > documentation
> > > itself is stilling lagging behind of production usages and
> > implementations.
> > > A while ago, the community was trying to improve documentation but it
> > > didn't actually happen due to lack of efforts.
> > >
> > > I am starting a BP for calling for contributions to improve the
> > > documentation. Here is the BP:
> > >
> > >
> > > https://cwiki.apache.org/confluence/display/BOOKKEEPER/
> > BP-12+-+Improve+documentation
> > >
> > > Any thoughts? If you are interested in participating in this, please
> > > comment here as well.
> > >
> >
> > +1
> >
> > >
> > I did start to write about the client API some months ago. I wuold like
> to
> > continue on this topic.
> > It is very important and interesting.while writing docs I found several
> > problems and so this activity will make us grow in a good direction and
> > become more 'owners' of own project.
> >
> > Apart from writing docs in the next months I would like to help in
> cleaning
> > up the client API anf the various plugin APIs
> >
> > Enrico
> >
> >
> > > - Sijie
> > >
> > --
> >
> >
> > -- Enrico Olivelli
> >
>

Reply via email to