You are viewing a plain text version of this content. The canonical link for it is here.
Posted to distributedlog-dev@bookkeeper.apache.org by Jia Zhai <zh...@gmail.com> on 2016/11/01 02:42:23 UTC
Re: Distributedlog Podling Report Draft - November 2016
Thanks a lot for your comments, will address them and post a new draft.
On Mon, Oct 31, 2016 at 6:02 PM, Flavio Junqueira <
fpjunqueira@yahoo.com.invalid> wrote:
> Thanks, Jia. It would be good to have concrete metrics where possible. See
> my comments below:
>
> > On 30 Oct 2016, at 10:53, Jia Zhai <zh...@gmail.com> wrote:
> >
> > Thanks a lot for your suggestions Flavio.
> > And Guys, Here is a draft. Please help comments on it.
> > Regards.
> > -Jia
> >
> > =====================================
> >
> > DistributedLog
> >
> > DistributedLog is a high-performance replicated log service. It offers
> >
> > durability, replication and strong consistency, which provides a
> fundamental
> >
> > building block for building reliable distributed systems.
> >
> > DistributedLog has been incubating since 2016-06-24.
> >
> > Three most important issues to address in the move towards graduation:
> > 1. Continue to grow the community, especially people from outside
> > Twitter.
> > [Ask the PMC for helping check the number of people subscribed to dev@
> mail
> > list]
>
> I think you're referring to the project PMC checking the subscription
> list. I checked and we have 35 people subscribed. A lot of people have
> gmail and apache.org <http://apache.org/> addresses so it is hard to tell
> affiliation. One typical sign of community diversity is to have active
> committers from multiple organizations, which is just a natural extension
> of a diverse community. As folks contribute to the project, I'd expect the
> PPMC to offer committership to the contributors.
>
> Please do not refer to Twitter specifically, just say that we want to
> increase diversity.
>
> > 2. Improve documentation.
>
> Project documentation is important, but from a community perspective, it
> is more important to have all processes documented well: how to contribute,
> how to merge, notes for first time committers, how to cut a release, check
> licenses. We need to make sure all this is in place once we suggest
> graduation.
>
>
> > 3. First Apache release
>
> When is the first release due? it would be good for this community to
> release sooner rather later. I'd expect multiple releases upon graduation.
> I think I'd just say "Release successfully".
>
> >
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware
> >
> > of?
> >
> > None
> >
> > How has the community developed since the last report?
> >
> > 1. Increase in contributions from community.
> >
>
> How do we measure this? Here are a few suggestions:
>
> - Number of messages to the list
> - Number of jiras created/resolved
> - Number of individual contributors
>
> > 2. Lots of engagement on documentation.
> >
>
> What are you using to determine this? Mailing list discussion or jira?
>
> There are other interesting threads going on too, like transactions and
> event sourcing.
>
> > 3. Improved responsiveness of committers to community members
> >
>
> I'd phrase this differently. I'd say something like:
>
> Increased traffic on the mailing list, in particular, due to committers
> engaging more actively with contributors.
>
> >
> > How has the project developed since the last report?
> >
> > 1. Documentation has improved for project build and project deployment.
> > Added more information on community page.
> >
>
> Please try to be a bit more specific.
>
> > 2. Involved more discussion of new ideas and bring in new features.
> Include
> > major discussions like 'transaction support', 'batch commit' .etc.
>
> Ok, I see you talked about other threads here.
>
> >
> > 3. First release and repackaging of the project under apache namespace
> are
> >
> > being discussed, such as:
> >
> > - Pull requests for repackaging.
> >
> > - Twitter folks are working on porting twitter's bk version back to
> > community
>
> It is a bit unclear why this is important, and I'd again avoid referring
> to a specific company if possible.
>
> If there is a major change happening and the community is all involved,
> then I'd mention it, but as stated it sounds like this is relevant to the
> BookKeeper community, although it affects this community because of the
> dependency.
>
> >
> > - Expect to cut a release on Nov.
>
> We should mention this above when we refer to the first release. I'd also
> be interested in knowing why the delay, what is holding it, and who is the
> release manager. We don't necessarily need to add it to the report,
> although more detail isn't bad.
>
> -Flavio
>
> >
> >
> >
> >
> > On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <fp...@apache.org>
> wrote:
> >
> >> Hi Jia,
> >>
> >> I'd suggest that you put a draft together and share on the list so that
> we
> >> can comment before posting on the wiki.
> >>
> >> -Flavio
> >>
> >>> On 27 Oct 2016, at 16:44, Jia Zhai <zh...@gmail.com> wrote:
> >>>
> >>> Hi Guys,
> >>> If there is an opportunity, I would like to have a try for this month.
> :)
> >>>
> >>> Thanks a lot.
> >>> -Jia
> >>>
> >>> On Thu, Oct 27, 2016 at 7:01 AM, <jo...@apache.org> wrote:
> >>>
> >>
>
>
Re: Distributedlog Podling Report Draft - November 2016
Posted by Jia Zhai <zh...@gmail.com>.
The lost report for DistributedLog has been added back.
Thanks for taking care of it. :)
On Thu, Nov 3, 2016 at 7:04 AM, Sijie Guo <si...@twitter.com.invalid>
wrote:
> Thanks John.
>
> Jia, can you help readd the report?
>
> - Sijie
>
> On Wed, Nov 2, 2016 at 3:14 PM, John D. Ament <jo...@apache.org>
> wrote:
>
> > All,
> >
> > Apologies. Infra had to migrate moin-moin and in doing so, some of the
> > recent data was lost. Please readd your report.
> >
> > John
> >
> > On 2016-11-02 09:22 (-0400), Flavio Junqueira <fp...@apache.org> wrote:
> > > +1
> > >
> > > > On 02 Nov 2016, at 09:22, Khurrum Nasim <kh...@gmail.com>
> > wrote:
> > > >
> > > > +1 from me (non-binding).
> > > >
> > > > - KN
> > > >
> > > > On Tue, Nov 1, 2016 at 7:18 PM, Jia Zhai <zh...@gmail.com>
> wrote:
> > > >
> > > >> Thanks so much for your suggestions. Here is a new draft:
> > > >>
> > > >> ===========
> > > >> DistributedLog
> > > >>
> > > >> DistributedLog is a high-performance replicated log service. It
> offers
> > > >> durability, replication and strong consistency, which provides a
> > > >> fundamental building block for building reliable distributed
> systems.
> > > >> DistributedLog has been incubating since 2016-06-24.
> > > >>
> > > >> Three most important issues to address in the move towards
> graduation:
> > > >> 1.Continue to grow the community, and increase diversity of
> community.
> > > >> 2.Improve documentation, including documentation of project and
> > processes.
> > > >> 3.Successful releases.
> > > >>
> > > >> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
> be
> > aware
> > > >> of?
> > > >> None
> > > >>
> > > >> How has the community developed since the last report?
> > > >> 1. Increase in contributions from community.
> > > >> - 8 created and 4 resolved issues in community JIRA in October.
> > > >> 2. Lots of engagement on documentation.
> > > >> - Enhance existing documents,
> > > >> - Setup guides for developers and committers.
> > > >> 3. Increased traffic on the mailing list, in particular, due to
> > committers
> > > >> engaging more actively with contributors.
> > > >> - we have 35 people subscribed mail list.
> > > >> - 125 messages to distributedlog mail list in October.
> > > >>
> > > >> How has the project developed since the last report?
> > > >> 1. Documentation has improved for project build and project
> > deployment.
> > > >> Added more information on community page.
> > > >> New added pages:
> > > >> https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> > > >> https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> > > >> 2. Involved more discussion of new ideas and bring in new features.
> > Include
> > > >> major discussions like 'transaction support', 'batch commit',
> > "EventStore"
> > > >> . etc.
> > > >> 3. First release expected on November, and repackaging of the
> project
> > under
> > > >> apache namespace are being discussed.
> > > >> - Pull requests for repackaging.
> > > >> - The major blocker is https://issues.apache.org/jira/browse/DL-2.
> > We were
> > > >> expecting to let DL depends on an official bk version.
> > > >>
> > > >> ================
> > > >>
> > > >> On Tue, Nov 1, 2016 at 5:54 PM, Sijie Guo <si...@apache.org> wrote:
> > > >>
> > > >>> Thank you Jia and Flavio. Comments inline.
> > > >>>
> > > >>> On Tue, Nov 1, 2016 at 1:54 AM, Jia Zhai <zh...@gmail.com>
> > wrote:
> > > >>>
> > > >>>> Hi Sijie,
> > > >>>> Would you please help address some of Flavio's comments first, You
> > may
> > > >>> have
> > > >>>> more information for story behind the result. I would like to
> handle
> > > >> this
> > > >>>> after your comments.
> > > >>>>
> > > >>>> Thanks a lot.
> > > >>>> -Jia
> > > >>>>
> > > >>>> On Tue, Nov 1, 2016 at 10:42 AM, Jia Zhai <zh...@gmail.com>
> > wrote:
> > > >>>>
> > > >>>>> Thanks a lot for your comments, will address them and post a new
> > > >> draft.
> > > >>>>>
> > > >>>>> On Mon, Oct 31, 2016 at 6:02 PM, Flavio Junqueira <
> > > >>>>> fpjunqueira@yahoo.com.invalid> wrote:
> > > >>>>>
> > > >>>>>> Thanks, Jia. It would be good to have concrete metrics where
> > > >> possible.
> > > >>>>>> See my comments below:
> > > >>>>>>
> > > >>>>>>> On 30 Oct 2016, at 10:53, Jia Zhai <zh...@gmail.com>
> wrote:
> > > >>>>>>>
> > > >>>>>>> Thanks a lot for your suggestions Flavio.
> > > >>>>>>> And Guys, Here is a draft. Please help comments on it.
> > > >>>>>>> Regards.
> > > >>>>>>> -Jia
> > > >>>>>>>
> > > >>>>>>> =====================================
> > > >>>>>>>
> > > >>>>>>> DistributedLog
> > > >>>>>>>
> > > >>>>>>> DistributedLog is a high-performance replicated log service. It
> > > >>> offers
> > > >>>>>>>
> > > >>>>>>> durability, replication and strong consistency, which provides
> a
> > > >>>>>> fundamental
> > > >>>>>>>
> > > >>>>>>> building block for building reliable distributed systems.
> > > >>>>>>>
> > > >>>>>>> DistributedLog has been incubating since 2016-06-24.
> > > >>>>>>>
> > > >>>>>>> Three most important issues to address in the move towards
> > > >>> graduation:
> > > >>>>>>> 1. Continue to grow the community, especially people from
> > > >>>> outside
> > > >>>>>>> Twitter.
> > > >>>>>>> [Ask the PMC for helping check the number of people subscribed
> to
> > > >>> dev@
> > > >>>>>> mail
> > > >>>>>>> list]
> > > >>>>>>
> > > >>>>>> I think you're referring to the project PMC checking the
> > > >> subscription
> > > >>>>>> list. I checked and we have 35 people subscribed. A lot of
> people
> > > >> have
> > > >>>>>> gmail and apache.org <http://apache.org/> addresses so it is
> hard
> > > >> to
> > > >>>>>> tell affiliation. One typical sign of community diversity is to
> > have
> > > >>>> active
> > > >>>>>> committers from multiple organizations, which is just a natural
> > > >>>> extension
> > > >>>>>> of a diverse community. As folks contribute to the project, I'd
> > > >> expect
> > > >>>> the
> > > >>>>>> PPMC to offer committership to the contributors.
> > > >>>>>>
> > > >>>>>> Please do not refer to Twitter specifically, just say that we
> want
> > > >> to
> > > >>>>>> increase diversity.
> > > >>>>
> > > >>>
> > > >>> Agreed. We should just say that we want to increase diversity.
> > > >>>
> > > >>>
> > > >>>>>>
> > > >>>>>>> 2. Improve documentation.
> > > >>>>>>
> > > >>>>>> Project documentation is important, but from a community
> > > >> perspective,
> > > >>> it
> > > >>>>>> is more important to have all processes documented well: how to
> > > >>>> contribute,
> > > >>>>>> how to merge, notes for first time committers, how to cut a
> > release,
> > > >>>> check
> > > >>>>>> licenses.
> > > >>>>
> > > >>>
> > > >>> Yup. We have setup a guide for developers and committers:
> > > >>>
> > > >>> https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> > > >>> https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> > > >>>
> > > >>> They are linked under the community tab in
> > > >>> http://distributedlog.incubator.apache.org/
> > > >>>
> > > >>>
> > > >>>> We need to make sure all this is in place once we suggest
> > > >>>>>> graduation.
> > > >>>>>>
> > > >>>>>>
> > > >>>>>>> 3. First Apache release
> > > >>>>>>
> > > >>>>>> When is the first release due? it would be good for this
> community
> > > >> to
> > > >>>>>> release sooner rather later. I'd expect multiple releases upon
> > > >>>> graduation.
> > > >>>>>> I think I'd just say "Release successfully".
> > > >>>>
> > > >>>
> > > >>> Or "Multiple successful releases"
> > > >>>
> > > >>>
> > > >>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need
> > to
> > > >>> be
> > > >>>>>> aware
> > > >>>>>>>
> > > >>>>>>> of?
> > > >>>>>>>
> > > >>>>>>> None
> > > >>>>>>>
> > > >>>>>>> How has the community developed since the last report?
> > > >>>>>>>
> > > >>>>>>> 1. Increase in contributions from community.
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>> How do we measure this? Here are a few suggestions:
> > > >>>>>>
> > > >>>>>> - Number of messages to the list
> > > >>>>>> - Number of jiras created/resolved
> > > >>>>>> - Number of individual contributors
> > > >>>>
> > > >>>
> > > >>> Jia,
> > > >>>
> > > >>> I think you can collect
> > > >>>
> > > >>> - number of messages by checking
> > > >>> http://mail-archives.apache.org/mod_mbox/incubator-
> > distributedlog-dev/
> > > >>> - number of jiras by filtering jira queue
> > > >>> - number of individual contributors : probably by looking at the
> > number
> > > >> of
> > > >>> contributors at github?
> > > >>>
> > > >>>
> > > >>>>>>
> > > >>>>>>> 2. Lots of engagement on documentation.
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>> What are you using to determine this? Mailing list discussion or
> > > >> jira?
> > > >>>>>>
> > > >>>>>> There are other interesting threads going on too, like
> > transactions
> > > >>> and
> > > >>>>>> event sourcing.
> > > >>>>
> > > >>>
> > > >>> I think pull requests can be used for counting this.
> > > >>>
> > > >>>
> > > >>>>>>
> > > >>>>>>> 3. Improved responsiveness of committers to community members
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>> I'd phrase this differently. I'd say something like:
> > > >>>>>>
> > > >>>>>> Increased traffic on the mailing list, in particular, due to
> > > >>> committers
> > > >>>>>> engaging more actively with contributors.
> > > >>>>>>
> > > >>>>>>>
> > > >>>>>>> How has the project developed since the last report?
> > > >>>>>>>
> > > >>>>>>> 1. Documentation has improved for project build and project
> > > >>>> deployment.
> > > >>>>>>> Added more information on community page.
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>> Please try to be a bit more specific.
> > > >>>>>>
> > > >>>>>>> 2. Involved more discussion of new ideas and bring in new
> > > >> features.
> > > >>>>>> Include
> > > >>>>>>> major discussions like 'transaction support', 'batch commit'
> > .etc.
> > > >>>>>>
> > > >>>>>> Ok, I see you talked about other threads here.
> > > >>>>>>
> > > >>>>>>>
> > > >>>>>>> 3. First release and repackaging of the project under apache
> > > >>> namespace
> > > >>>>>> are
> > > >>>>>>>
> > > >>>>>>> being discussed, such as:
> > > >>>>>>>
> > > >>>>>>> - Pull requests for repackaging.
> > > >>>>>>>
> > > >>>>>>> - Twitter folks are working on porting twitter's bk version
> back
> > > >> to
> > > >>>>>>> community
> > > >>>>>>
> > > >>>>>> It is a bit unclear why this is important, and I'd again avoid
> > > >>> referring
> > > >>>>>> to a specific company if possible.
> > > >>>>>>
> > > >>>>>> If there is a major change happening and the community is all
> > > >>> involved,
> > > >>>>>> then I'd mention it, but as stated it sounds like this is
> relevant
> > > >> to
> > > >>>> the
> > > >>>>>> BookKeeper community, although it affects this community because
> > of
> > > >>> the
> > > >>>>>> dependency.
> > > >>>>
> > > >>>
> > > >>> Currently distributedlog relies on some major changes made in
> > twitter's
> > > >>> bookkeeper branch, such as long poll read support, parallel
> recovery,
> > > >> delay
> > > >>> ensemble change and such. we are working on merging those changes
> > back.
> > > >>>
> > > >>>
> > > >>>>>>
> > > >>>>>>>
> > > >>>>>>> - Expect to cut a release on Nov.
> > > >>>>>>
> > > >>>>>> We should mention this above when we refer to the first release.
> > I'd
> > > >>>> also
> > > >>>>>> be interested in knowing why the delay, what is holding it, and
> > who
> > > >> is
> > > >>>> the
> > > >>>>>> release manager. We don't necessarily need to add it to the
> > report,
> > > >>>>>> although more detail isn't bad.
> > > >>>>
> > > >>>
> > > >>> The major blocker is https://issues.apache.org/jira/browse/DL-2.
> We
> > were
> > > >>> expecting to let DL depends on an official bk version rather than a
> > > >> version
> > > >>> from twitter's branch.
> > > >>>
> > > >>>
> > > >>>>>>
> > > >>>>>> -Flavio
> > > >>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <
> > > >> fpj@apache.org>
> > > >>>>>> wrote:
> > > >>>>>>>
> > > >>>>>>>> Hi Jia,
> > > >>>>>>>>
> > > >>>>>>>> I'd suggest that you put a draft together and share on the
> list
> > > >> so
> > > >>>>>> that we
> > > >>>>>>>> can comment before posting on the wiki.
> > > >>>>>>>>
> > > >>>>>>>> -Flavio
> > > >>>>>>>>
> > > >>>>>>>>> On 27 Oct 2016, at 16:44, Jia Zhai <zh...@gmail.com>
> > wrote:
> > > >>>>>>>>>
> > > >>>>>>>>> Hi Guys,
> > > >>>>>>>>> If there is an opportunity, I would like to have a try for
> this
> > > >>>>>> month. :)
> > > >>>>>>>>>
> > > >>>>>>>>> Thanks a lot.
> > > >>>>>>>>> -Jia
> > > >>>>>>>>>
> > > >>>>>>>>> On Thu, Oct 27, 2016 at 7:01 AM, <jo...@apache.org>
> > wrote:
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>
> > > >>>
> > > >>
> > >
> > >
> >
>
Re: Distributedlog Podling Report Draft - November 2016
Posted by Sijie Guo <si...@twitter.com.INVALID>.
Thanks John.
Jia, can you help readd the report?
- Sijie
On Wed, Nov 2, 2016 at 3:14 PM, John D. Ament <jo...@apache.org> wrote:
> All,
>
> Apologies. Infra had to migrate moin-moin and in doing so, some of the
> recent data was lost. Please readd your report.
>
> John
>
> On 2016-11-02 09:22 (-0400), Flavio Junqueira <fp...@apache.org> wrote:
> > +1
> >
> > > On 02 Nov 2016, at 09:22, Khurrum Nasim <kh...@gmail.com>
> wrote:
> > >
> > > +1 from me (non-binding).
> > >
> > > - KN
> > >
> > > On Tue, Nov 1, 2016 at 7:18 PM, Jia Zhai <zh...@gmail.com> wrote:
> > >
> > >> Thanks so much for your suggestions. Here is a new draft:
> > >>
> > >> ===========
> > >> DistributedLog
> > >>
> > >> DistributedLog is a high-performance replicated log service. It offers
> > >> durability, replication and strong consistency, which provides a
> > >> fundamental building block for building reliable distributed systems.
> > >> DistributedLog has been incubating since 2016-06-24.
> > >>
> > >> Three most important issues to address in the move towards graduation:
> > >> 1.Continue to grow the community, and increase diversity of community.
> > >> 2.Improve documentation, including documentation of project and
> processes.
> > >> 3.Successful releases.
> > >>
> > >> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware
> > >> of?
> > >> None
> > >>
> > >> How has the community developed since the last report?
> > >> 1. Increase in contributions from community.
> > >> - 8 created and 4 resolved issues in community JIRA in October.
> > >> 2. Lots of engagement on documentation.
> > >> - Enhance existing documents,
> > >> - Setup guides for developers and committers.
> > >> 3. Increased traffic on the mailing list, in particular, due to
> committers
> > >> engaging more actively with contributors.
> > >> - we have 35 people subscribed mail list.
> > >> - 125 messages to distributedlog mail list in October.
> > >>
> > >> How has the project developed since the last report?
> > >> 1. Documentation has improved for project build and project
> deployment.
> > >> Added more information on community page.
> > >> New added pages:
> > >> https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> > >> https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> > >> 2. Involved more discussion of new ideas and bring in new features.
> Include
> > >> major discussions like 'transaction support', 'batch commit',
> "EventStore"
> > >> . etc.
> > >> 3. First release expected on November, and repackaging of the project
> under
> > >> apache namespace are being discussed.
> > >> - Pull requests for repackaging.
> > >> - The major blocker is https://issues.apache.org/jira/browse/DL-2.
> We were
> > >> expecting to let DL depends on an official bk version.
> > >>
> > >> ================
> > >>
> > >> On Tue, Nov 1, 2016 at 5:54 PM, Sijie Guo <si...@apache.org> wrote:
> > >>
> > >>> Thank you Jia and Flavio. Comments inline.
> > >>>
> > >>> On Tue, Nov 1, 2016 at 1:54 AM, Jia Zhai <zh...@gmail.com>
> wrote:
> > >>>
> > >>>> Hi Sijie,
> > >>>> Would you please help address some of Flavio's comments first, You
> may
> > >>> have
> > >>>> more information for story behind the result. I would like to handle
> > >> this
> > >>>> after your comments.
> > >>>>
> > >>>> Thanks a lot.
> > >>>> -Jia
> > >>>>
> > >>>> On Tue, Nov 1, 2016 at 10:42 AM, Jia Zhai <zh...@gmail.com>
> wrote:
> > >>>>
> > >>>>> Thanks a lot for your comments, will address them and post a new
> > >> draft.
> > >>>>>
> > >>>>> On Mon, Oct 31, 2016 at 6:02 PM, Flavio Junqueira <
> > >>>>> fpjunqueira@yahoo.com.invalid> wrote:
> > >>>>>
> > >>>>>> Thanks, Jia. It would be good to have concrete metrics where
> > >> possible.
> > >>>>>> See my comments below:
> > >>>>>>
> > >>>>>>> On 30 Oct 2016, at 10:53, Jia Zhai <zh...@gmail.com> wrote:
> > >>>>>>>
> > >>>>>>> Thanks a lot for your suggestions Flavio.
> > >>>>>>> And Guys, Here is a draft. Please help comments on it.
> > >>>>>>> Regards.
> > >>>>>>> -Jia
> > >>>>>>>
> > >>>>>>> =====================================
> > >>>>>>>
> > >>>>>>> DistributedLog
> > >>>>>>>
> > >>>>>>> DistributedLog is a high-performance replicated log service. It
> > >>> offers
> > >>>>>>>
> > >>>>>>> durability, replication and strong consistency, which provides a
> > >>>>>> fundamental
> > >>>>>>>
> > >>>>>>> building block for building reliable distributed systems.
> > >>>>>>>
> > >>>>>>> DistributedLog has been incubating since 2016-06-24.
> > >>>>>>>
> > >>>>>>> Three most important issues to address in the move towards
> > >>> graduation:
> > >>>>>>> 1. Continue to grow the community, especially people from
> > >>>> outside
> > >>>>>>> Twitter.
> > >>>>>>> [Ask the PMC for helping check the number of people subscribed to
> > >>> dev@
> > >>>>>> mail
> > >>>>>>> list]
> > >>>>>>
> > >>>>>> I think you're referring to the project PMC checking the
> > >> subscription
> > >>>>>> list. I checked and we have 35 people subscribed. A lot of people
> > >> have
> > >>>>>> gmail and apache.org <http://apache.org/> addresses so it is hard
> > >> to
> > >>>>>> tell affiliation. One typical sign of community diversity is to
> have
> > >>>> active
> > >>>>>> committers from multiple organizations, which is just a natural
> > >>>> extension
> > >>>>>> of a diverse community. As folks contribute to the project, I'd
> > >> expect
> > >>>> the
> > >>>>>> PPMC to offer committership to the contributors.
> > >>>>>>
> > >>>>>> Please do not refer to Twitter specifically, just say that we want
> > >> to
> > >>>>>> increase diversity.
> > >>>>
> > >>>
> > >>> Agreed. We should just say that we want to increase diversity.
> > >>>
> > >>>
> > >>>>>>
> > >>>>>>> 2. Improve documentation.
> > >>>>>>
> > >>>>>> Project documentation is important, but from a community
> > >> perspective,
> > >>> it
> > >>>>>> is more important to have all processes documented well: how to
> > >>>> contribute,
> > >>>>>> how to merge, notes for first time committers, how to cut a
> release,
> > >>>> check
> > >>>>>> licenses.
> > >>>>
> > >>>
> > >>> Yup. We have setup a guide for developers and committers:
> > >>>
> > >>> https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> > >>> https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> > >>>
> > >>> They are linked under the community tab in
> > >>> http://distributedlog.incubator.apache.org/
> > >>>
> > >>>
> > >>>> We need to make sure all this is in place once we suggest
> > >>>>>> graduation.
> > >>>>>>
> > >>>>>>
> > >>>>>>> 3. First Apache release
> > >>>>>>
> > >>>>>> When is the first release due? it would be good for this community
> > >> to
> > >>>>>> release sooner rather later. I'd expect multiple releases upon
> > >>>> graduation.
> > >>>>>> I think I'd just say "Release successfully".
> > >>>>
> > >>>
> > >>> Or "Multiple successful releases"
> > >>>
> > >>>
> > >>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need
> to
> > >>> be
> > >>>>>> aware
> > >>>>>>>
> > >>>>>>> of?
> > >>>>>>>
> > >>>>>>> None
> > >>>>>>>
> > >>>>>>> How has the community developed since the last report?
> > >>>>>>>
> > >>>>>>> 1. Increase in contributions from community.
> > >>>>>>>
> > >>>>>>
> > >>>>>> How do we measure this? Here are a few suggestions:
> > >>>>>>
> > >>>>>> - Number of messages to the list
> > >>>>>> - Number of jiras created/resolved
> > >>>>>> - Number of individual contributors
> > >>>>
> > >>>
> > >>> Jia,
> > >>>
> > >>> I think you can collect
> > >>>
> > >>> - number of messages by checking
> > >>> http://mail-archives.apache.org/mod_mbox/incubator-
> distributedlog-dev/
> > >>> - number of jiras by filtering jira queue
> > >>> - number of individual contributors : probably by looking at the
> number
> > >> of
> > >>> contributors at github?
> > >>>
> > >>>
> > >>>>>>
> > >>>>>>> 2. Lots of engagement on documentation.
> > >>>>>>>
> > >>>>>>
> > >>>>>> What are you using to determine this? Mailing list discussion or
> > >> jira?
> > >>>>>>
> > >>>>>> There are other interesting threads going on too, like
> transactions
> > >>> and
> > >>>>>> event sourcing.
> > >>>>
> > >>>
> > >>> I think pull requests can be used for counting this.
> > >>>
> > >>>
> > >>>>>>
> > >>>>>>> 3. Improved responsiveness of committers to community members
> > >>>>>>>
> > >>>>>>
> > >>>>>> I'd phrase this differently. I'd say something like:
> > >>>>>>
> > >>>>>> Increased traffic on the mailing list, in particular, due to
> > >>> committers
> > >>>>>> engaging more actively with contributors.
> > >>>>>>
> > >>>>>>>
> > >>>>>>> How has the project developed since the last report?
> > >>>>>>>
> > >>>>>>> 1. Documentation has improved for project build and project
> > >>>> deployment.
> > >>>>>>> Added more information on community page.
> > >>>>>>>
> > >>>>>>
> > >>>>>> Please try to be a bit more specific.
> > >>>>>>
> > >>>>>>> 2. Involved more discussion of new ideas and bring in new
> > >> features.
> > >>>>>> Include
> > >>>>>>> major discussions like 'transaction support', 'batch commit'
> .etc.
> > >>>>>>
> > >>>>>> Ok, I see you talked about other threads here.
> > >>>>>>
> > >>>>>>>
> > >>>>>>> 3. First release and repackaging of the project under apache
> > >>> namespace
> > >>>>>> are
> > >>>>>>>
> > >>>>>>> being discussed, such as:
> > >>>>>>>
> > >>>>>>> - Pull requests for repackaging.
> > >>>>>>>
> > >>>>>>> - Twitter folks are working on porting twitter's bk version back
> > >> to
> > >>>>>>> community
> > >>>>>>
> > >>>>>> It is a bit unclear why this is important, and I'd again avoid
> > >>> referring
> > >>>>>> to a specific company if possible.
> > >>>>>>
> > >>>>>> If there is a major change happening and the community is all
> > >>> involved,
> > >>>>>> then I'd mention it, but as stated it sounds like this is relevant
> > >> to
> > >>>> the
> > >>>>>> BookKeeper community, although it affects this community because
> of
> > >>> the
> > >>>>>> dependency.
> > >>>>
> > >>>
> > >>> Currently distributedlog relies on some major changes made in
> twitter's
> > >>> bookkeeper branch, such as long poll read support, parallel recovery,
> > >> delay
> > >>> ensemble change and such. we are working on merging those changes
> back.
> > >>>
> > >>>
> > >>>>>>
> > >>>>>>>
> > >>>>>>> - Expect to cut a release on Nov.
> > >>>>>>
> > >>>>>> We should mention this above when we refer to the first release.
> I'd
> > >>>> also
> > >>>>>> be interested in knowing why the delay, what is holding it, and
> who
> > >> is
> > >>>> the
> > >>>>>> release manager. We don't necessarily need to add it to the
> report,
> > >>>>>> although more detail isn't bad.
> > >>>>
> > >>>
> > >>> The major blocker is https://issues.apache.org/jira/browse/DL-2. We
> were
> > >>> expecting to let DL depends on an official bk version rather than a
> > >> version
> > >>> from twitter's branch.
> > >>>
> > >>>
> > >>>>>>
> > >>>>>> -Flavio
> > >>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <
> > >> fpj@apache.org>
> > >>>>>> wrote:
> > >>>>>>>
> > >>>>>>>> Hi Jia,
> > >>>>>>>>
> > >>>>>>>> I'd suggest that you put a draft together and share on the list
> > >> so
> > >>>>>> that we
> > >>>>>>>> can comment before posting on the wiki.
> > >>>>>>>>
> > >>>>>>>> -Flavio
> > >>>>>>>>
> > >>>>>>>>> On 27 Oct 2016, at 16:44, Jia Zhai <zh...@gmail.com>
> wrote:
> > >>>>>>>>>
> > >>>>>>>>> Hi Guys,
> > >>>>>>>>> If there is an opportunity, I would like to have a try for this
> > >>>>>> month. :)
> > >>>>>>>>>
> > >>>>>>>>> Thanks a lot.
> > >>>>>>>>> -Jia
> > >>>>>>>>>
> > >>>>>>>>> On Thu, Oct 27, 2016 at 7:01 AM, <jo...@apache.org>
> wrote:
> > >>>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> >
>
Re: Distributedlog Podling Report Draft - November 2016
Posted by "John D. Ament" <jo...@apache.org>.
All,
Apologies. Infra had to migrate moin-moin and in doing so, some of the recent data was lost. Please readd your report.
John
On 2016-11-02 09:22 (-0400), Flavio Junqueira <fp...@apache.org> wrote:
> +1
>
> > On 02 Nov 2016, at 09:22, Khurrum Nasim <kh...@gmail.com> wrote:
> >
> > +1 from me (non-binding).
> >
> > - KN
> >
> > On Tue, Nov 1, 2016 at 7:18 PM, Jia Zhai <zh...@gmail.com> wrote:
> >
> >> Thanks so much for your suggestions. Here is a new draft:
> >>
> >> ===========
> >> DistributedLog
> >>
> >> DistributedLog is a high-performance replicated log service. It offers
> >> durability, replication and strong consistency, which provides a
> >> fundamental building block for building reliable distributed systems.
> >> DistributedLog has been incubating since 2016-06-24.
> >>
> >> Three most important issues to address in the move towards graduation:
> >> 1.Continue to grow the community, and increase diversity of community.
> >> 2.Improve documentation, including documentation of project and processes.
> >> 3.Successful releases.
> >>
> >> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
> >> of?
> >> None
> >>
> >> How has the community developed since the last report?
> >> 1. Increase in contributions from community.
> >> - 8 created and 4 resolved issues in community JIRA in October.
> >> 2. Lots of engagement on documentation.
> >> - Enhance existing documents,
> >> - Setup guides for developers and committers.
> >> 3. Increased traffic on the mailing list, in particular, due to committers
> >> engaging more actively with contributors.
> >> - we have 35 people subscribed mail list.
> >> - 125 messages to distributedlog mail list in October.
> >>
> >> How has the project developed since the last report?
> >> 1. Documentation has improved for project build and project deployment.
> >> Added more information on community page.
> >> New added pages:
> >> https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> >> https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> >> 2. Involved more discussion of new ideas and bring in new features. Include
> >> major discussions like 'transaction support', 'batch commit', "EventStore"
> >> . etc.
> >> 3. First release expected on November, and repackaging of the project under
> >> apache namespace are being discussed.
> >> - Pull requests for repackaging.
> >> - The major blocker is https://issues.apache.org/jira/browse/DL-2. We were
> >> expecting to let DL depends on an official bk version.
> >>
> >> ================
> >>
> >> On Tue, Nov 1, 2016 at 5:54 PM, Sijie Guo <si...@apache.org> wrote:
> >>
> >>> Thank you Jia and Flavio. Comments inline.
> >>>
> >>> On Tue, Nov 1, 2016 at 1:54 AM, Jia Zhai <zh...@gmail.com> wrote:
> >>>
> >>>> Hi Sijie,
> >>>> Would you please help address some of Flavio's comments first, You may
> >>> have
> >>>> more information for story behind the result. I would like to handle
> >> this
> >>>> after your comments.
> >>>>
> >>>> Thanks a lot.
> >>>> -Jia
> >>>>
> >>>> On Tue, Nov 1, 2016 at 10:42 AM, Jia Zhai <zh...@gmail.com> wrote:
> >>>>
> >>>>> Thanks a lot for your comments, will address them and post a new
> >> draft.
> >>>>>
> >>>>> On Mon, Oct 31, 2016 at 6:02 PM, Flavio Junqueira <
> >>>>> fpjunqueira@yahoo.com.invalid> wrote:
> >>>>>
> >>>>>> Thanks, Jia. It would be good to have concrete metrics where
> >> possible.
> >>>>>> See my comments below:
> >>>>>>
> >>>>>>> On 30 Oct 2016, at 10:53, Jia Zhai <zh...@gmail.com> wrote:
> >>>>>>>
> >>>>>>> Thanks a lot for your suggestions Flavio.
> >>>>>>> And Guys, Here is a draft. Please help comments on it.
> >>>>>>> Regards.
> >>>>>>> -Jia
> >>>>>>>
> >>>>>>> =====================================
> >>>>>>>
> >>>>>>> DistributedLog
> >>>>>>>
> >>>>>>> DistributedLog is a high-performance replicated log service. It
> >>> offers
> >>>>>>>
> >>>>>>> durability, replication and strong consistency, which provides a
> >>>>>> fundamental
> >>>>>>>
> >>>>>>> building block for building reliable distributed systems.
> >>>>>>>
> >>>>>>> DistributedLog has been incubating since 2016-06-24.
> >>>>>>>
> >>>>>>> Three most important issues to address in the move towards
> >>> graduation:
> >>>>>>> 1. Continue to grow the community, especially people from
> >>>> outside
> >>>>>>> Twitter.
> >>>>>>> [Ask the PMC for helping check the number of people subscribed to
> >>> dev@
> >>>>>> mail
> >>>>>>> list]
> >>>>>>
> >>>>>> I think you're referring to the project PMC checking the
> >> subscription
> >>>>>> list. I checked and we have 35 people subscribed. A lot of people
> >> have
> >>>>>> gmail and apache.org <http://apache.org/> addresses so it is hard
> >> to
> >>>>>> tell affiliation. One typical sign of community diversity is to have
> >>>> active
> >>>>>> committers from multiple organizations, which is just a natural
> >>>> extension
> >>>>>> of a diverse community. As folks contribute to the project, I'd
> >> expect
> >>>> the
> >>>>>> PPMC to offer committership to the contributors.
> >>>>>>
> >>>>>> Please do not refer to Twitter specifically, just say that we want
> >> to
> >>>>>> increase diversity.
> >>>>
> >>>
> >>> Agreed. We should just say that we want to increase diversity.
> >>>
> >>>
> >>>>>>
> >>>>>>> 2. Improve documentation.
> >>>>>>
> >>>>>> Project documentation is important, but from a community
> >> perspective,
> >>> it
> >>>>>> is more important to have all processes documented well: how to
> >>>> contribute,
> >>>>>> how to merge, notes for first time committers, how to cut a release,
> >>>> check
> >>>>>> licenses.
> >>>>
> >>>
> >>> Yup. We have setup a guide for developers and committers:
> >>>
> >>> https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> >>> https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> >>>
> >>> They are linked under the community tab in
> >>> http://distributedlog.incubator.apache.org/
> >>>
> >>>
> >>>> We need to make sure all this is in place once we suggest
> >>>>>> graduation.
> >>>>>>
> >>>>>>
> >>>>>>> 3. First Apache release
> >>>>>>
> >>>>>> When is the first release due? it would be good for this community
> >> to
> >>>>>> release sooner rather later. I'd expect multiple releases upon
> >>>> graduation.
> >>>>>> I think I'd just say "Release successfully".
> >>>>
> >>>
> >>> Or "Multiple successful releases"
> >>>
> >>>
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
> >>> be
> >>>>>> aware
> >>>>>>>
> >>>>>>> of?
> >>>>>>>
> >>>>>>> None
> >>>>>>>
> >>>>>>> How has the community developed since the last report?
> >>>>>>>
> >>>>>>> 1. Increase in contributions from community.
> >>>>>>>
> >>>>>>
> >>>>>> How do we measure this? Here are a few suggestions:
> >>>>>>
> >>>>>> - Number of messages to the list
> >>>>>> - Number of jiras created/resolved
> >>>>>> - Number of individual contributors
> >>>>
> >>>
> >>> Jia,
> >>>
> >>> I think you can collect
> >>>
> >>> - number of messages by checking
> >>> http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/
> >>> - number of jiras by filtering jira queue
> >>> - number of individual contributors : probably by looking at the number
> >> of
> >>> contributors at github?
> >>>
> >>>
> >>>>>>
> >>>>>>> 2. Lots of engagement on documentation.
> >>>>>>>
> >>>>>>
> >>>>>> What are you using to determine this? Mailing list discussion or
> >> jira?
> >>>>>>
> >>>>>> There are other interesting threads going on too, like transactions
> >>> and
> >>>>>> event sourcing.
> >>>>
> >>>
> >>> I think pull requests can be used for counting this.
> >>>
> >>>
> >>>>>>
> >>>>>>> 3. Improved responsiveness of committers to community members
> >>>>>>>
> >>>>>>
> >>>>>> I'd phrase this differently. I'd say something like:
> >>>>>>
> >>>>>> Increased traffic on the mailing list, in particular, due to
> >>> committers
> >>>>>> engaging more actively with contributors.
> >>>>>>
> >>>>>>>
> >>>>>>> How has the project developed since the last report?
> >>>>>>>
> >>>>>>> 1. Documentation has improved for project build and project
> >>>> deployment.
> >>>>>>> Added more information on community page.
> >>>>>>>
> >>>>>>
> >>>>>> Please try to be a bit more specific.
> >>>>>>
> >>>>>>> 2. Involved more discussion of new ideas and bring in new
> >> features.
> >>>>>> Include
> >>>>>>> major discussions like 'transaction support', 'batch commit' .etc.
> >>>>>>
> >>>>>> Ok, I see you talked about other threads here.
> >>>>>>
> >>>>>>>
> >>>>>>> 3. First release and repackaging of the project under apache
> >>> namespace
> >>>>>> are
> >>>>>>>
> >>>>>>> being discussed, such as:
> >>>>>>>
> >>>>>>> - Pull requests for repackaging.
> >>>>>>>
> >>>>>>> - Twitter folks are working on porting twitter's bk version back
> >> to
> >>>>>>> community
> >>>>>>
> >>>>>> It is a bit unclear why this is important, and I'd again avoid
> >>> referring
> >>>>>> to a specific company if possible.
> >>>>>>
> >>>>>> If there is a major change happening and the community is all
> >>> involved,
> >>>>>> then I'd mention it, but as stated it sounds like this is relevant
> >> to
> >>>> the
> >>>>>> BookKeeper community, although it affects this community because of
> >>> the
> >>>>>> dependency.
> >>>>
> >>>
> >>> Currently distributedlog relies on some major changes made in twitter's
> >>> bookkeeper branch, such as long poll read support, parallel recovery,
> >> delay
> >>> ensemble change and such. we are working on merging those changes back.
> >>>
> >>>
> >>>>>>
> >>>>>>>
> >>>>>>> - Expect to cut a release on Nov.
> >>>>>>
> >>>>>> We should mention this above when we refer to the first release. I'd
> >>>> also
> >>>>>> be interested in knowing why the delay, what is holding it, and who
> >> is
> >>>> the
> >>>>>> release manager. We don't necessarily need to add it to the report,
> >>>>>> although more detail isn't bad.
> >>>>
> >>>
> >>> The major blocker is https://issues.apache.org/jira/browse/DL-2. We were
> >>> expecting to let DL depends on an official bk version rather than a
> >> version
> >>> from twitter's branch.
> >>>
> >>>
> >>>>>>
> >>>>>> -Flavio
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <
> >> fpj@apache.org>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>>> Hi Jia,
> >>>>>>>>
> >>>>>>>> I'd suggest that you put a draft together and share on the list
> >> so
> >>>>>> that we
> >>>>>>>> can comment before posting on the wiki.
> >>>>>>>>
> >>>>>>>> -Flavio
> >>>>>>>>
> >>>>>>>>> On 27 Oct 2016, at 16:44, Jia Zhai <zh...@gmail.com> wrote:
> >>>>>>>>>
> >>>>>>>>> Hi Guys,
> >>>>>>>>> If there is an opportunity, I would like to have a try for this
> >>>>>> month. :)
> >>>>>>>>>
> >>>>>>>>> Thanks a lot.
> >>>>>>>>> -Jia
> >>>>>>>>>
> >>>>>>>>> On Thu, Oct 27, 2016 at 7:01 AM, <jo...@apache.org> wrote:
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>
Re: Distributedlog Podling Report Draft - November 2016
Posted by Flavio Junqueira <fp...@apache.org>.
+1
> On 02 Nov 2016, at 09:22, Khurrum Nasim <kh...@gmail.com> wrote:
>
> +1 from me (non-binding).
>
> - KN
>
> On Tue, Nov 1, 2016 at 7:18 PM, Jia Zhai <zh...@gmail.com> wrote:
>
>> Thanks so much for your suggestions. Here is a new draft:
>>
>> ===========
>> DistributedLog
>>
>> DistributedLog is a high-performance replicated log service. It offers
>> durability, replication and strong consistency, which provides a
>> fundamental building block for building reliable distributed systems.
>> DistributedLog has been incubating since 2016-06-24.
>>
>> Three most important issues to address in the move towards graduation:
>> 1.Continue to grow the community, and increase diversity of community.
>> 2.Improve documentation, including documentation of project and processes.
>> 3.Successful releases.
>>
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
>> of?
>> None
>>
>> How has the community developed since the last report?
>> 1. Increase in contributions from community.
>> - 8 created and 4 resolved issues in community JIRA in October.
>> 2. Lots of engagement on documentation.
>> - Enhance existing documents,
>> - Setup guides for developers and committers.
>> 3. Increased traffic on the mailing list, in particular, due to committers
>> engaging more actively with contributors.
>> - we have 35 people subscribed mail list.
>> - 125 messages to distributedlog mail list in October.
>>
>> How has the project developed since the last report?
>> 1. Documentation has improved for project build and project deployment.
>> Added more information on community page.
>> New added pages:
>> https://cwiki.apache.org/confluence/display/DL/Developer+Guide
>> https://cwiki.apache.org/confluence/display/DL/Committer+Guide
>> 2. Involved more discussion of new ideas and bring in new features. Include
>> major discussions like 'transaction support', 'batch commit', "EventStore"
>> . etc.
>> 3. First release expected on November, and repackaging of the project under
>> apache namespace are being discussed.
>> - Pull requests for repackaging.
>> - The major blocker is https://issues.apache.org/jira/browse/DL-2. We were
>> expecting to let DL depends on an official bk version.
>>
>> ================
>>
>> On Tue, Nov 1, 2016 at 5:54 PM, Sijie Guo <si...@apache.org> wrote:
>>
>>> Thank you Jia and Flavio. Comments inline.
>>>
>>> On Tue, Nov 1, 2016 at 1:54 AM, Jia Zhai <zh...@gmail.com> wrote:
>>>
>>>> Hi Sijie,
>>>> Would you please help address some of Flavio's comments first, You may
>>> have
>>>> more information for story behind the result. I would like to handle
>> this
>>>> after your comments.
>>>>
>>>> Thanks a lot.
>>>> -Jia
>>>>
>>>> On Tue, Nov 1, 2016 at 10:42 AM, Jia Zhai <zh...@gmail.com> wrote:
>>>>
>>>>> Thanks a lot for your comments, will address them and post a new
>> draft.
>>>>>
>>>>> On Mon, Oct 31, 2016 at 6:02 PM, Flavio Junqueira <
>>>>> fpjunqueira@yahoo.com.invalid> wrote:
>>>>>
>>>>>> Thanks, Jia. It would be good to have concrete metrics where
>> possible.
>>>>>> See my comments below:
>>>>>>
>>>>>>> On 30 Oct 2016, at 10:53, Jia Zhai <zh...@gmail.com> wrote:
>>>>>>>
>>>>>>> Thanks a lot for your suggestions Flavio.
>>>>>>> And Guys, Here is a draft. Please help comments on it.
>>>>>>> Regards.
>>>>>>> -Jia
>>>>>>>
>>>>>>> =====================================
>>>>>>>
>>>>>>> DistributedLog
>>>>>>>
>>>>>>> DistributedLog is a high-performance replicated log service. It
>>> offers
>>>>>>>
>>>>>>> durability, replication and strong consistency, which provides a
>>>>>> fundamental
>>>>>>>
>>>>>>> building block for building reliable distributed systems.
>>>>>>>
>>>>>>> DistributedLog has been incubating since 2016-06-24.
>>>>>>>
>>>>>>> Three most important issues to address in the move towards
>>> graduation:
>>>>>>> 1. Continue to grow the community, especially people from
>>>> outside
>>>>>>> Twitter.
>>>>>>> [Ask the PMC for helping check the number of people subscribed to
>>> dev@
>>>>>> mail
>>>>>>> list]
>>>>>>
>>>>>> I think you're referring to the project PMC checking the
>> subscription
>>>>>> list. I checked and we have 35 people subscribed. A lot of people
>> have
>>>>>> gmail and apache.org <http://apache.org/> addresses so it is hard
>> to
>>>>>> tell affiliation. One typical sign of community diversity is to have
>>>> active
>>>>>> committers from multiple organizations, which is just a natural
>>>> extension
>>>>>> of a diverse community. As folks contribute to the project, I'd
>> expect
>>>> the
>>>>>> PPMC to offer committership to the contributors.
>>>>>>
>>>>>> Please do not refer to Twitter specifically, just say that we want
>> to
>>>>>> increase diversity.
>>>>
>>>
>>> Agreed. We should just say that we want to increase diversity.
>>>
>>>
>>>>>>
>>>>>>> 2. Improve documentation.
>>>>>>
>>>>>> Project documentation is important, but from a community
>> perspective,
>>> it
>>>>>> is more important to have all processes documented well: how to
>>>> contribute,
>>>>>> how to merge, notes for first time committers, how to cut a release,
>>>> check
>>>>>> licenses.
>>>>
>>>
>>> Yup. We have setup a guide for developers and committers:
>>>
>>> https://cwiki.apache.org/confluence/display/DL/Developer+Guide
>>> https://cwiki.apache.org/confluence/display/DL/Committer+Guide
>>>
>>> They are linked under the community tab in
>>> http://distributedlog.incubator.apache.org/
>>>
>>>
>>>> We need to make sure all this is in place once we suggest
>>>>>> graduation.
>>>>>>
>>>>>>
>>>>>>> 3. First Apache release
>>>>>>
>>>>>> When is the first release due? it would be good for this community
>> to
>>>>>> release sooner rather later. I'd expect multiple releases upon
>>>> graduation.
>>>>>> I think I'd just say "Release successfully".
>>>>
>>>
>>> Or "Multiple successful releases"
>>>
>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
>>> be
>>>>>> aware
>>>>>>>
>>>>>>> of?
>>>>>>>
>>>>>>> None
>>>>>>>
>>>>>>> How has the community developed since the last report?
>>>>>>>
>>>>>>> 1. Increase in contributions from community.
>>>>>>>
>>>>>>
>>>>>> How do we measure this? Here are a few suggestions:
>>>>>>
>>>>>> - Number of messages to the list
>>>>>> - Number of jiras created/resolved
>>>>>> - Number of individual contributors
>>>>
>>>
>>> Jia,
>>>
>>> I think you can collect
>>>
>>> - number of messages by checking
>>> http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/
>>> - number of jiras by filtering jira queue
>>> - number of individual contributors : probably by looking at the number
>> of
>>> contributors at github?
>>>
>>>
>>>>>>
>>>>>>> 2. Lots of engagement on documentation.
>>>>>>>
>>>>>>
>>>>>> What are you using to determine this? Mailing list discussion or
>> jira?
>>>>>>
>>>>>> There are other interesting threads going on too, like transactions
>>> and
>>>>>> event sourcing.
>>>>
>>>
>>> I think pull requests can be used for counting this.
>>>
>>>
>>>>>>
>>>>>>> 3. Improved responsiveness of committers to community members
>>>>>>>
>>>>>>
>>>>>> I'd phrase this differently. I'd say something like:
>>>>>>
>>>>>> Increased traffic on the mailing list, in particular, due to
>>> committers
>>>>>> engaging more actively with contributors.
>>>>>>
>>>>>>>
>>>>>>> How has the project developed since the last report?
>>>>>>>
>>>>>>> 1. Documentation has improved for project build and project
>>>> deployment.
>>>>>>> Added more information on community page.
>>>>>>>
>>>>>>
>>>>>> Please try to be a bit more specific.
>>>>>>
>>>>>>> 2. Involved more discussion of new ideas and bring in new
>> features.
>>>>>> Include
>>>>>>> major discussions like 'transaction support', 'batch commit' .etc.
>>>>>>
>>>>>> Ok, I see you talked about other threads here.
>>>>>>
>>>>>>>
>>>>>>> 3. First release and repackaging of the project under apache
>>> namespace
>>>>>> are
>>>>>>>
>>>>>>> being discussed, such as:
>>>>>>>
>>>>>>> - Pull requests for repackaging.
>>>>>>>
>>>>>>> - Twitter folks are working on porting twitter's bk version back
>> to
>>>>>>> community
>>>>>>
>>>>>> It is a bit unclear why this is important, and I'd again avoid
>>> referring
>>>>>> to a specific company if possible.
>>>>>>
>>>>>> If there is a major change happening and the community is all
>>> involved,
>>>>>> then I'd mention it, but as stated it sounds like this is relevant
>> to
>>>> the
>>>>>> BookKeeper community, although it affects this community because of
>>> the
>>>>>> dependency.
>>>>
>>>
>>> Currently distributedlog relies on some major changes made in twitter's
>>> bookkeeper branch, such as long poll read support, parallel recovery,
>> delay
>>> ensemble change and such. we are working on merging those changes back.
>>>
>>>
>>>>>>
>>>>>>>
>>>>>>> - Expect to cut a release on Nov.
>>>>>>
>>>>>> We should mention this above when we refer to the first release. I'd
>>>> also
>>>>>> be interested in knowing why the delay, what is holding it, and who
>> is
>>>> the
>>>>>> release manager. We don't necessarily need to add it to the report,
>>>>>> although more detail isn't bad.
>>>>
>>>
>>> The major blocker is https://issues.apache.org/jira/browse/DL-2. We were
>>> expecting to let DL depends on an official bk version rather than a
>> version
>>> from twitter's branch.
>>>
>>>
>>>>>>
>>>>>> -Flavio
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <
>> fpj@apache.org>
>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Jia,
>>>>>>>>
>>>>>>>> I'd suggest that you put a draft together and share on the list
>> so
>>>>>> that we
>>>>>>>> can comment before posting on the wiki.
>>>>>>>>
>>>>>>>> -Flavio
>>>>>>>>
>>>>>>>>> On 27 Oct 2016, at 16:44, Jia Zhai <zh...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>> Hi Guys,
>>>>>>>>> If there is an opportunity, I would like to have a try for this
>>>>>> month. :)
>>>>>>>>>
>>>>>>>>> Thanks a lot.
>>>>>>>>> -Jia
>>>>>>>>>
>>>>>>>>> On Thu, Oct 27, 2016 at 7:01 AM, <jo...@apache.org> wrote:
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
Re: Distributedlog Podling Report Draft - November 2016
Posted by Khurrum Nasim <kh...@gmail.com>.
+1 from me (non-binding).
- KN
On Tue, Nov 1, 2016 at 7:18 PM, Jia Zhai <zh...@gmail.com> wrote:
> Thanks so much for your suggestions. Here is a new draft:
>
> ===========
> DistributedLog
>
> DistributedLog is a high-performance replicated log service. It offers
> durability, replication and strong consistency, which provides a
> fundamental building block for building reliable distributed systems.
> DistributedLog has been incubating since 2016-06-24.
>
> Three most important issues to address in the move towards graduation:
> 1.Continue to grow the community, and increase diversity of community.
> 2.Improve documentation, including documentation of project and processes.
> 3.Successful releases.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
> of?
> None
>
> How has the community developed since the last report?
> 1. Increase in contributions from community.
> - 8 created and 4 resolved issues in community JIRA in October.
> 2. Lots of engagement on documentation.
> - Enhance existing documents,
> - Setup guides for developers and committers.
> 3. Increased traffic on the mailing list, in particular, due to committers
> engaging more actively with contributors.
> - we have 35 people subscribed mail list.
> - 125 messages to distributedlog mail list in October.
>
> How has the project developed since the last report?
> 1. Documentation has improved for project build and project deployment.
> Added more information on community page.
> New added pages:
> https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> 2. Involved more discussion of new ideas and bring in new features. Include
> major discussions like 'transaction support', 'batch commit', "EventStore"
> . etc.
> 3. First release expected on November, and repackaging of the project under
> apache namespace are being discussed.
> - Pull requests for repackaging.
> - The major blocker is https://issues.apache.org/jira/browse/DL-2. We were
> expecting to let DL depends on an official bk version.
>
> ================
>
> On Tue, Nov 1, 2016 at 5:54 PM, Sijie Guo <si...@apache.org> wrote:
>
> > Thank you Jia and Flavio. Comments inline.
> >
> > On Tue, Nov 1, 2016 at 1:54 AM, Jia Zhai <zh...@gmail.com> wrote:
> >
> > > Hi Sijie,
> > > Would you please help address some of Flavio's comments first, You may
> > have
> > > more information for story behind the result. I would like to handle
> this
> > > after your comments.
> > >
> > > Thanks a lot.
> > > -Jia
> > >
> > > On Tue, Nov 1, 2016 at 10:42 AM, Jia Zhai <zh...@gmail.com> wrote:
> > >
> > > > Thanks a lot for your comments, will address them and post a new
> draft.
> > > >
> > > > On Mon, Oct 31, 2016 at 6:02 PM, Flavio Junqueira <
> > > > fpjunqueira@yahoo.com.invalid> wrote:
> > > >
> > > >> Thanks, Jia. It would be good to have concrete metrics where
> possible.
> > > >> See my comments below:
> > > >>
> > > >> > On 30 Oct 2016, at 10:53, Jia Zhai <zh...@gmail.com> wrote:
> > > >> >
> > > >> > Thanks a lot for your suggestions Flavio.
> > > >> > And Guys, Here is a draft. Please help comments on it.
> > > >> > Regards.
> > > >> > -Jia
> > > >> >
> > > >> > =====================================
> > > >> >
> > > >> > DistributedLog
> > > >> >
> > > >> > DistributedLog is a high-performance replicated log service. It
> > offers
> > > >> >
> > > >> > durability, replication and strong consistency, which provides a
> > > >> fundamental
> > > >> >
> > > >> > building block for building reliable distributed systems.
> > > >> >
> > > >> > DistributedLog has been incubating since 2016-06-24.
> > > >> >
> > > >> > Three most important issues to address in the move towards
> > graduation:
> > > >> > 1. Continue to grow the community, especially people from
> > > outside
> > > >> > Twitter.
> > > >> > [Ask the PMC for helping check the number of people subscribed to
> > dev@
> > > >> mail
> > > >> > list]
> > > >>
> > > >> I think you're referring to the project PMC checking the
> subscription
> > > >> list. I checked and we have 35 people subscribed. A lot of people
> have
> > > >> gmail and apache.org <http://apache.org/> addresses so it is hard
> to
> > > >> tell affiliation. One typical sign of community diversity is to have
> > > active
> > > >> committers from multiple organizations, which is just a natural
> > > extension
> > > >> of a diverse community. As folks contribute to the project, I'd
> expect
> > > the
> > > >> PPMC to offer committership to the contributors.
> > > >>
> > > >> Please do not refer to Twitter specifically, just say that we want
> to
> > > >> increase diversity.
> > >
> >
> > Agreed. We should just say that we want to increase diversity.
> >
> >
> > > >>
> > > >> > 2. Improve documentation.
> > > >>
> > > >> Project documentation is important, but from a community
> perspective,
> > it
> > > >> is more important to have all processes documented well: how to
> > > contribute,
> > > >> how to merge, notes for first time committers, how to cut a release,
> > > check
> > > >> licenses.
> > >
> >
> > Yup. We have setup a guide for developers and committers:
> >
> > https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> > https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> >
> > They are linked under the community tab in
> > http://distributedlog.incubator.apache.org/
> >
> >
> > > We need to make sure all this is in place once we suggest
> > > >> graduation.
> > > >>
> > > >>
> > > >> > 3. First Apache release
> > > >>
> > > >> When is the first release due? it would be good for this community
> to
> > > >> release sooner rather later. I'd expect multiple releases upon
> > > graduation.
> > > >> I think I'd just say "Release successfully".
> > >
> >
> > Or "Multiple successful releases"
> >
> >
> > > >>
> > > >> >
> > > >> >
> > > >> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
> > be
> > > >> aware
> > > >> >
> > > >> > of?
> > > >> >
> > > >> > None
> > > >> >
> > > >> > How has the community developed since the last report?
> > > >> >
> > > >> > 1. Increase in contributions from community.
> > > >> >
> > > >>
> > > >> How do we measure this? Here are a few suggestions:
> > > >>
> > > >> - Number of messages to the list
> > > >> - Number of jiras created/resolved
> > > >> - Number of individual contributors
> > >
> >
> > Jia,
> >
> > I think you can collect
> >
> > - number of messages by checking
> > http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/
> > - number of jiras by filtering jira queue
> > - number of individual contributors : probably by looking at the number
> of
> > contributors at github?
> >
> >
> > > >>
> > > >> > 2. Lots of engagement on documentation.
> > > >> >
> > > >>
> > > >> What are you using to determine this? Mailing list discussion or
> jira?
> > > >>
> > > >> There are other interesting threads going on too, like transactions
> > and
> > > >> event sourcing.
> > >
> >
> > I think pull requests can be used for counting this.
> >
> >
> > > >>
> > > >> > 3. Improved responsiveness of committers to community members
> > > >> >
> > > >>
> > > >> I'd phrase this differently. I'd say something like:
> > > >>
> > > >> Increased traffic on the mailing list, in particular, due to
> > committers
> > > >> engaging more actively with contributors.
> > > >>
> > > >> >
> > > >> > How has the project developed since the last report?
> > > >> >
> > > >> > 1. Documentation has improved for project build and project
> > > deployment.
> > > >> > Added more information on community page.
> > > >> >
> > > >>
> > > >> Please try to be a bit more specific.
> > > >>
> > > >> > 2. Involved more discussion of new ideas and bring in new
> features.
> > > >> Include
> > > >> > major discussions like 'transaction support', 'batch commit' .etc.
> > > >>
> > > >> Ok, I see you talked about other threads here.
> > > >>
> > > >> >
> > > >> > 3. First release and repackaging of the project under apache
> > namespace
> > > >> are
> > > >> >
> > > >> > being discussed, such as:
> > > >> >
> > > >> > - Pull requests for repackaging.
> > > >> >
> > > >> > - Twitter folks are working on porting twitter's bk version back
> to
> > > >> > community
> > > >>
> > > >> It is a bit unclear why this is important, and I'd again avoid
> > referring
> > > >> to a specific company if possible.
> > > >>
> > > >> If there is a major change happening and the community is all
> > involved,
> > > >> then I'd mention it, but as stated it sounds like this is relevant
> to
> > > the
> > > >> BookKeeper community, although it affects this community because of
> > the
> > > >> dependency.
> > >
> >
> > Currently distributedlog relies on some major changes made in twitter's
> > bookkeeper branch, such as long poll read support, parallel recovery,
> delay
> > ensemble change and such. we are working on merging those changes back.
> >
> >
> > > >>
> > > >> >
> > > >> > - Expect to cut a release on Nov.
> > > >>
> > > >> We should mention this above when we refer to the first release. I'd
> > > also
> > > >> be interested in knowing why the delay, what is holding it, and who
> is
> > > the
> > > >> release manager. We don't necessarily need to add it to the report,
> > > >> although more detail isn't bad.
> > >
> >
> > The major blocker is https://issues.apache.org/jira/browse/DL-2. We were
> > expecting to let DL depends on an official bk version rather than a
> version
> > from twitter's branch.
> >
> >
> > > >>
> > > >> -Flavio
> > > >>
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <
> fpj@apache.org>
> > > >> wrote:
> > > >> >
> > > >> >> Hi Jia,
> > > >> >>
> > > >> >> I'd suggest that you put a draft together and share on the list
> so
> > > >> that we
> > > >> >> can comment before posting on the wiki.
> > > >> >>
> > > >> >> -Flavio
> > > >> >>
> > > >> >>> On 27 Oct 2016, at 16:44, Jia Zhai <zh...@gmail.com> wrote:
> > > >> >>>
> > > >> >>> Hi Guys,
> > > >> >>> If there is an opportunity, I would like to have a try for this
> > > >> month. :)
> > > >> >>>
> > > >> >>> Thanks a lot.
> > > >> >>> -Jia
> > > >> >>>
> > > >> >>> On Thu, Oct 27, 2016 at 7:01 AM, <jo...@apache.org> wrote:
> > > >> >>>
> > > >> >>
> > > >>
> > > >>
> > > >
> > >
> >
>
Re: Distributedlog Podling Report Draft - November 2016
Posted by Leigh Stewart <ls...@twitter.com.INVALID>.
LGTM
On Tue, Nov 1, 2016 at 9:31 PM, Sijie Guo <si...@apache.org> wrote:
> +1 LGTM.
>
> - Sijie
>
> On Tue, Nov 1, 2016 at 7:18 PM, Jia Zhai <zh...@gmail.com> wrote:
>
> > Thanks so much for your suggestions. Here is a new draft:
> >
> > ===========
> > DistributedLog
> >
> > DistributedLog is a high-performance replicated log service. It offers
> > durability, replication and strong consistency, which provides a
> > fundamental building block for building reliable distributed systems.
> > DistributedLog has been incubating since 2016-06-24.
> >
> > Three most important issues to address in the move towards graduation:
> > 1.Continue to grow the community, and increase diversity of community.
> > 2.Improve documentation, including documentation of project and
> processes.
> > 3.Successful releases.
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware
> > of?
> > None
> >
> > How has the community developed since the last report?
> > 1. Increase in contributions from community.
> > - 8 created and 4 resolved issues in community JIRA in October.
> > 2. Lots of engagement on documentation.
> > - Enhance existing documents,
> > - Setup guides for developers and committers.
> > 3. Increased traffic on the mailing list, in particular, due to
> committers
> > engaging more actively with contributors.
> > - we have 35 people subscribed mail list.
> > - 125 messages to distributedlog mail list in October.
> >
> > How has the project developed since the last report?
> > 1. Documentation has improved for project build and project deployment.
> > Added more information on community page.
> > New added pages:
> > https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> > https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> > 2. Involved more discussion of new ideas and bring in new features.
> Include
> > major discussions like 'transaction support', 'batch commit',
> "EventStore"
> > . etc.
> > 3. First release expected on November, and repackaging of the project
> under
> > apache namespace are being discussed.
> > - Pull requests for repackaging.
> > - The major blocker is https://issues.apache.org/jira/browse/DL-2. We
> were
> > expecting to let DL depends on an official bk version.
> >
> > ================
> >
> > On Tue, Nov 1, 2016 at 5:54 PM, Sijie Guo <si...@apache.org> wrote:
> >
> > > Thank you Jia and Flavio. Comments inline.
> > >
> > > On Tue, Nov 1, 2016 at 1:54 AM, Jia Zhai <zh...@gmail.com> wrote:
> > >
> > > > Hi Sijie,
> > > > Would you please help address some of Flavio's comments first, You
> may
> > > have
> > > > more information for story behind the result. I would like to handle
> > this
> > > > after your comments.
> > > >
> > > > Thanks a lot.
> > > > -Jia
> > > >
> > > > On Tue, Nov 1, 2016 at 10:42 AM, Jia Zhai <zh...@gmail.com>
> wrote:
> > > >
> > > > > Thanks a lot for your comments, will address them and post a new
> > draft.
> > > > >
> > > > > On Mon, Oct 31, 2016 at 6:02 PM, Flavio Junqueira <
> > > > > fpjunqueira@yahoo.com.invalid> wrote:
> > > > >
> > > > >> Thanks, Jia. It would be good to have concrete metrics where
> > possible.
> > > > >> See my comments below:
> > > > >>
> > > > >> > On 30 Oct 2016, at 10:53, Jia Zhai <zh...@gmail.com> wrote:
> > > > >> >
> > > > >> > Thanks a lot for your suggestions Flavio.
> > > > >> > And Guys, Here is a draft. Please help comments on it.
> > > > >> > Regards.
> > > > >> > -Jia
> > > > >> >
> > > > >> > =====================================
> > > > >> >
> > > > >> > DistributedLog
> > > > >> >
> > > > >> > DistributedLog is a high-performance replicated log service. It
> > > offers
> > > > >> >
> > > > >> > durability, replication and strong consistency, which provides a
> > > > >> fundamental
> > > > >> >
> > > > >> > building block for building reliable distributed systems.
> > > > >> >
> > > > >> > DistributedLog has been incubating since 2016-06-24.
> > > > >> >
> > > > >> > Three most important issues to address in the move towards
> > > graduation:
> > > > >> > 1. Continue to grow the community, especially people from
> > > > outside
> > > > >> > Twitter.
> > > > >> > [Ask the PMC for helping check the number of people subscribed
> to
> > > dev@
> > > > >> mail
> > > > >> > list]
> > > > >>
> > > > >> I think you're referring to the project PMC checking the
> > subscription
> > > > >> list. I checked and we have 35 people subscribed. A lot of people
> > have
> > > > >> gmail and apache.org <http://apache.org/> addresses so it is hard
> > to
> > > > >> tell affiliation. One typical sign of community diversity is to
> have
> > > > active
> > > > >> committers from multiple organizations, which is just a natural
> > > > extension
> > > > >> of a diverse community. As folks contribute to the project, I'd
> > expect
> > > > the
> > > > >> PPMC to offer committership to the contributors.
> > > > >>
> > > > >> Please do not refer to Twitter specifically, just say that we want
> > to
> > > > >> increase diversity.
> > > >
> > >
> > > Agreed. We should just say that we want to increase diversity.
> > >
> > >
> > > > >>
> > > > >> > 2. Improve documentation.
> > > > >>
> > > > >> Project documentation is important, but from a community
> > perspective,
> > > it
> > > > >> is more important to have all processes documented well: how to
> > > > contribute,
> > > > >> how to merge, notes for first time committers, how to cut a
> release,
> > > > check
> > > > >> licenses.
> > > >
> > >
> > > Yup. We have setup a guide for developers and committers:
> > >
> > > https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> > > https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> > >
> > > They are linked under the community tab in
> > > http://distributedlog.incubator.apache.org/
> > >
> > >
> > > > We need to make sure all this is in place once we suggest
> > > > >> graduation.
> > > > >>
> > > > >>
> > > > >> > 3. First Apache release
> > > > >>
> > > > >> When is the first release due? it would be good for this community
> > to
> > > > >> release sooner rather later. I'd expect multiple releases upon
> > > > graduation.
> > > > >> I think I'd just say "Release successfully".
> > > >
> > >
> > > Or "Multiple successful releases"
> > >
> > >
> > > > >>
> > > > >> >
> > > > >> >
> > > > >> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need
> to
> > > be
> > > > >> aware
> > > > >> >
> > > > >> > of?
> > > > >> >
> > > > >> > None
> > > > >> >
> > > > >> > How has the community developed since the last report?
> > > > >> >
> > > > >> > 1. Increase in contributions from community.
> > > > >> >
> > > > >>
> > > > >> How do we measure this? Here are a few suggestions:
> > > > >>
> > > > >> - Number of messages to the list
> > > > >> - Number of jiras created/resolved
> > > > >> - Number of individual contributors
> > > >
> > >
> > > Jia,
> > >
> > > I think you can collect
> > >
> > > - number of messages by checking
> > > http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/
> > > - number of jiras by filtering jira queue
> > > - number of individual contributors : probably by looking at the number
> > of
> > > contributors at github?
> > >
> > >
> > > > >>
> > > > >> > 2. Lots of engagement on documentation.
> > > > >> >
> > > > >>
> > > > >> What are you using to determine this? Mailing list discussion or
> > jira?
> > > > >>
> > > > >> There are other interesting threads going on too, like
> transactions
> > > and
> > > > >> event sourcing.
> > > >
> > >
> > > I think pull requests can be used for counting this.
> > >
> > >
> > > > >>
> > > > >> > 3. Improved responsiveness of committers to community members
> > > > >> >
> > > > >>
> > > > >> I'd phrase this differently. I'd say something like:
> > > > >>
> > > > >> Increased traffic on the mailing list, in particular, due to
> > > committers
> > > > >> engaging more actively with contributors.
> > > > >>
> > > > >> >
> > > > >> > How has the project developed since the last report?
> > > > >> >
> > > > >> > 1. Documentation has improved for project build and project
> > > > deployment.
> > > > >> > Added more information on community page.
> > > > >> >
> > > > >>
> > > > >> Please try to be a bit more specific.
> > > > >>
> > > > >> > 2. Involved more discussion of new ideas and bring in new
> > features.
> > > > >> Include
> > > > >> > major discussions like 'transaction support', 'batch commit'
> .etc.
> > > > >>
> > > > >> Ok, I see you talked about other threads here.
> > > > >>
> > > > >> >
> > > > >> > 3. First release and repackaging of the project under apache
> > > namespace
> > > > >> are
> > > > >> >
> > > > >> > being discussed, such as:
> > > > >> >
> > > > >> > - Pull requests for repackaging.
> > > > >> >
> > > > >> > - Twitter folks are working on porting twitter's bk version back
> > to
> > > > >> > community
> > > > >>
> > > > >> It is a bit unclear why this is important, and I'd again avoid
> > > referring
> > > > >> to a specific company if possible.
> > > > >>
> > > > >> If there is a major change happening and the community is all
> > > involved,
> > > > >> then I'd mention it, but as stated it sounds like this is relevant
> > to
> > > > the
> > > > >> BookKeeper community, although it affects this community because
> of
> > > the
> > > > >> dependency.
> > > >
> > >
> > > Currently distributedlog relies on some major changes made in twitter's
> > > bookkeeper branch, such as long poll read support, parallel recovery,
> > delay
> > > ensemble change and such. we are working on merging those changes back.
> > >
> > >
> > > > >>
> > > > >> >
> > > > >> > - Expect to cut a release on Nov.
> > > > >>
> > > > >> We should mention this above when we refer to the first release.
> I'd
> > > > also
> > > > >> be interested in knowing why the delay, what is holding it, and
> who
> > is
> > > > the
> > > > >> release manager. We don't necessarily need to add it to the
> report,
> > > > >> although more detail isn't bad.
> > > >
> > >
> > > The major blocker is https://issues.apache.org/jira/browse/DL-2. We
> were
> > > expecting to let DL depends on an official bk version rather than a
> > version
> > > from twitter's branch.
> > >
> > >
> > > > >>
> > > > >> -Flavio
> > > > >>
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <
> > fpj@apache.org>
> > > > >> wrote:
> > > > >> >
> > > > >> >> Hi Jia,
> > > > >> >>
> > > > >> >> I'd suggest that you put a draft together and share on the list
> > so
> > > > >> that we
> > > > >> >> can comment before posting on the wiki.
> > > > >> >>
> > > > >> >> -Flavio
> > > > >> >>
> > > > >> >>> On 27 Oct 2016, at 16:44, Jia Zhai <zh...@gmail.com>
> wrote:
> > > > >> >>>
> > > > >> >>> Hi Guys,
> > > > >> >>> If there is an opportunity, I would like to have a try for
> this
> > > > >> month. :)
> > > > >> >>>
> > > > >> >>> Thanks a lot.
> > > > >> >>> -Jia
> > > > >> >>>
> > > > >> >>> On Thu, Oct 27, 2016 at 7:01 AM, <jo...@apache.org>
> wrote:
> > > > >> >>>
> > > > >> >>
> > > > >>
> > > > >>
> > > > >
> > > >
> > >
> >
>
Re: Distributedlog Podling Report Draft - November 2016
Posted by Sijie Guo <si...@apache.org>.
+1 LGTM.
- Sijie
On Tue, Nov 1, 2016 at 7:18 PM, Jia Zhai <zh...@gmail.com> wrote:
> Thanks so much for your suggestions. Here is a new draft:
>
> ===========
> DistributedLog
>
> DistributedLog is a high-performance replicated log service. It offers
> durability, replication and strong consistency, which provides a
> fundamental building block for building reliable distributed systems.
> DistributedLog has been incubating since 2016-06-24.
>
> Three most important issues to address in the move towards graduation:
> 1.Continue to grow the community, and increase diversity of community.
> 2.Improve documentation, including documentation of project and processes.
> 3.Successful releases.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
> of?
> None
>
> How has the community developed since the last report?
> 1. Increase in contributions from community.
> - 8 created and 4 resolved issues in community JIRA in October.
> 2. Lots of engagement on documentation.
> - Enhance existing documents,
> - Setup guides for developers and committers.
> 3. Increased traffic on the mailing list, in particular, due to committers
> engaging more actively with contributors.
> - we have 35 people subscribed mail list.
> - 125 messages to distributedlog mail list in October.
>
> How has the project developed since the last report?
> 1. Documentation has improved for project build and project deployment.
> Added more information on community page.
> New added pages:
> https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> 2. Involved more discussion of new ideas and bring in new features. Include
> major discussions like 'transaction support', 'batch commit', "EventStore"
> . etc.
> 3. First release expected on November, and repackaging of the project under
> apache namespace are being discussed.
> - Pull requests for repackaging.
> - The major blocker is https://issues.apache.org/jira/browse/DL-2. We were
> expecting to let DL depends on an official bk version.
>
> ================
>
> On Tue, Nov 1, 2016 at 5:54 PM, Sijie Guo <si...@apache.org> wrote:
>
> > Thank you Jia and Flavio. Comments inline.
> >
> > On Tue, Nov 1, 2016 at 1:54 AM, Jia Zhai <zh...@gmail.com> wrote:
> >
> > > Hi Sijie,
> > > Would you please help address some of Flavio's comments first, You may
> > have
> > > more information for story behind the result. I would like to handle
> this
> > > after your comments.
> > >
> > > Thanks a lot.
> > > -Jia
> > >
> > > On Tue, Nov 1, 2016 at 10:42 AM, Jia Zhai <zh...@gmail.com> wrote:
> > >
> > > > Thanks a lot for your comments, will address them and post a new
> draft.
> > > >
> > > > On Mon, Oct 31, 2016 at 6:02 PM, Flavio Junqueira <
> > > > fpjunqueira@yahoo.com.invalid> wrote:
> > > >
> > > >> Thanks, Jia. It would be good to have concrete metrics where
> possible.
> > > >> See my comments below:
> > > >>
> > > >> > On 30 Oct 2016, at 10:53, Jia Zhai <zh...@gmail.com> wrote:
> > > >> >
> > > >> > Thanks a lot for your suggestions Flavio.
> > > >> > And Guys, Here is a draft. Please help comments on it.
> > > >> > Regards.
> > > >> > -Jia
> > > >> >
> > > >> > =====================================
> > > >> >
> > > >> > DistributedLog
> > > >> >
> > > >> > DistributedLog is a high-performance replicated log service. It
> > offers
> > > >> >
> > > >> > durability, replication and strong consistency, which provides a
> > > >> fundamental
> > > >> >
> > > >> > building block for building reliable distributed systems.
> > > >> >
> > > >> > DistributedLog has been incubating since 2016-06-24.
> > > >> >
> > > >> > Three most important issues to address in the move towards
> > graduation:
> > > >> > 1. Continue to grow the community, especially people from
> > > outside
> > > >> > Twitter.
> > > >> > [Ask the PMC for helping check the number of people subscribed to
> > dev@
> > > >> mail
> > > >> > list]
> > > >>
> > > >> I think you're referring to the project PMC checking the
> subscription
> > > >> list. I checked and we have 35 people subscribed. A lot of people
> have
> > > >> gmail and apache.org <http://apache.org/> addresses so it is hard
> to
> > > >> tell affiliation. One typical sign of community diversity is to have
> > > active
> > > >> committers from multiple organizations, which is just a natural
> > > extension
> > > >> of a diverse community. As folks contribute to the project, I'd
> expect
> > > the
> > > >> PPMC to offer committership to the contributors.
> > > >>
> > > >> Please do not refer to Twitter specifically, just say that we want
> to
> > > >> increase diversity.
> > >
> >
> > Agreed. We should just say that we want to increase diversity.
> >
> >
> > > >>
> > > >> > 2. Improve documentation.
> > > >>
> > > >> Project documentation is important, but from a community
> perspective,
> > it
> > > >> is more important to have all processes documented well: how to
> > > contribute,
> > > >> how to merge, notes for first time committers, how to cut a release,
> > > check
> > > >> licenses.
> > >
> >
> > Yup. We have setup a guide for developers and committers:
> >
> > https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> > https://cwiki.apache.org/confluence/display/DL/Committer+Guide
> >
> > They are linked under the community tab in
> > http://distributedlog.incubator.apache.org/
> >
> >
> > > We need to make sure all this is in place once we suggest
> > > >> graduation.
> > > >>
> > > >>
> > > >> > 3. First Apache release
> > > >>
> > > >> When is the first release due? it would be good for this community
> to
> > > >> release sooner rather later. I'd expect multiple releases upon
> > > graduation.
> > > >> I think I'd just say "Release successfully".
> > >
> >
> > Or "Multiple successful releases"
> >
> >
> > > >>
> > > >> >
> > > >> >
> > > >> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
> > be
> > > >> aware
> > > >> >
> > > >> > of?
> > > >> >
> > > >> > None
> > > >> >
> > > >> > How has the community developed since the last report?
> > > >> >
> > > >> > 1. Increase in contributions from community.
> > > >> >
> > > >>
> > > >> How do we measure this? Here are a few suggestions:
> > > >>
> > > >> - Number of messages to the list
> > > >> - Number of jiras created/resolved
> > > >> - Number of individual contributors
> > >
> >
> > Jia,
> >
> > I think you can collect
> >
> > - number of messages by checking
> > http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/
> > - number of jiras by filtering jira queue
> > - number of individual contributors : probably by looking at the number
> of
> > contributors at github?
> >
> >
> > > >>
> > > >> > 2. Lots of engagement on documentation.
> > > >> >
> > > >>
> > > >> What are you using to determine this? Mailing list discussion or
> jira?
> > > >>
> > > >> There are other interesting threads going on too, like transactions
> > and
> > > >> event sourcing.
> > >
> >
> > I think pull requests can be used for counting this.
> >
> >
> > > >>
> > > >> > 3. Improved responsiveness of committers to community members
> > > >> >
> > > >>
> > > >> I'd phrase this differently. I'd say something like:
> > > >>
> > > >> Increased traffic on the mailing list, in particular, due to
> > committers
> > > >> engaging more actively with contributors.
> > > >>
> > > >> >
> > > >> > How has the project developed since the last report?
> > > >> >
> > > >> > 1. Documentation has improved for project build and project
> > > deployment.
> > > >> > Added more information on community page.
> > > >> >
> > > >>
> > > >> Please try to be a bit more specific.
> > > >>
> > > >> > 2. Involved more discussion of new ideas and bring in new
> features.
> > > >> Include
> > > >> > major discussions like 'transaction support', 'batch commit' .etc.
> > > >>
> > > >> Ok, I see you talked about other threads here.
> > > >>
> > > >> >
> > > >> > 3. First release and repackaging of the project under apache
> > namespace
> > > >> are
> > > >> >
> > > >> > being discussed, such as:
> > > >> >
> > > >> > - Pull requests for repackaging.
> > > >> >
> > > >> > - Twitter folks are working on porting twitter's bk version back
> to
> > > >> > community
> > > >>
> > > >> It is a bit unclear why this is important, and I'd again avoid
> > referring
> > > >> to a specific company if possible.
> > > >>
> > > >> If there is a major change happening and the community is all
> > involved,
> > > >> then I'd mention it, but as stated it sounds like this is relevant
> to
> > > the
> > > >> BookKeeper community, although it affects this community because of
> > the
> > > >> dependency.
> > >
> >
> > Currently distributedlog relies on some major changes made in twitter's
> > bookkeeper branch, such as long poll read support, parallel recovery,
> delay
> > ensemble change and such. we are working on merging those changes back.
> >
> >
> > > >>
> > > >> >
> > > >> > - Expect to cut a release on Nov.
> > > >>
> > > >> We should mention this above when we refer to the first release. I'd
> > > also
> > > >> be interested in knowing why the delay, what is holding it, and who
> is
> > > the
> > > >> release manager. We don't necessarily need to add it to the report,
> > > >> although more detail isn't bad.
> > >
> >
> > The major blocker is https://issues.apache.org/jira/browse/DL-2. We were
> > expecting to let DL depends on an official bk version rather than a
> version
> > from twitter's branch.
> >
> >
> > > >>
> > > >> -Flavio
> > > >>
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <
> fpj@apache.org>
> > > >> wrote:
> > > >> >
> > > >> >> Hi Jia,
> > > >> >>
> > > >> >> I'd suggest that you put a draft together and share on the list
> so
> > > >> that we
> > > >> >> can comment before posting on the wiki.
> > > >> >>
> > > >> >> -Flavio
> > > >> >>
> > > >> >>> On 27 Oct 2016, at 16:44, Jia Zhai <zh...@gmail.com> wrote:
> > > >> >>>
> > > >> >>> Hi Guys,
> > > >> >>> If there is an opportunity, I would like to have a try for this
> > > >> month. :)
> > > >> >>>
> > > >> >>> Thanks a lot.
> > > >> >>> -Jia
> > > >> >>>
> > > >> >>> On Thu, Oct 27, 2016 at 7:01 AM, <jo...@apache.org> wrote:
> > > >> >>>
> > > >> >>
> > > >>
> > > >>
> > > >
> > >
> >
>
Re: Distributedlog Podling Report Draft - November 2016
Posted by Jia Zhai <zh...@gmail.com>.
Thanks so much for your suggestions. Here is a new draft:
===========
DistributedLog
DistributedLog is a high-performance replicated log service. It offers
durability, replication and strong consistency, which provides a
fundamental building block for building reliable distributed systems.
DistributedLog has been incubating since 2016-06-24.
Three most important issues to address in the move towards graduation:
1.Continue to grow the community, and increase diversity of community.
2.Improve documentation, including documentation of project and processes.
3.Successful releases.
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?
None
How has the community developed since the last report?
1. Increase in contributions from community.
- 8 created and 4 resolved issues in community JIRA in October.
2. Lots of engagement on documentation.
- Enhance existing documents,
- Setup guides for developers and committers.
3. Increased traffic on the mailing list, in particular, due to committers
engaging more actively with contributors.
- we have 35 people subscribed mail list.
- 125 messages to distributedlog mail list in October.
How has the project developed since the last report?
1. Documentation has improved for project build and project deployment.
Added more information on community page.
New added pages:
https://cwiki.apache.org/confluence/display/DL/Developer+Guide
https://cwiki.apache.org/confluence/display/DL/Committer+Guide
2. Involved more discussion of new ideas and bring in new features. Include
major discussions like 'transaction support', 'batch commit', "EventStore"
. etc.
3. First release expected on November, and repackaging of the project under
apache namespace are being discussed.
- Pull requests for repackaging.
- The major blocker is https://issues.apache.org/jira/browse/DL-2. We were
expecting to let DL depends on an official bk version.
================
On Tue, Nov 1, 2016 at 5:54 PM, Sijie Guo <si...@apache.org> wrote:
> Thank you Jia and Flavio. Comments inline.
>
> On Tue, Nov 1, 2016 at 1:54 AM, Jia Zhai <zh...@gmail.com> wrote:
>
> > Hi Sijie,
> > Would you please help address some of Flavio's comments first, You may
> have
> > more information for story behind the result. I would like to handle this
> > after your comments.
> >
> > Thanks a lot.
> > -Jia
> >
> > On Tue, Nov 1, 2016 at 10:42 AM, Jia Zhai <zh...@gmail.com> wrote:
> >
> > > Thanks a lot for your comments, will address them and post a new draft.
> > >
> > > On Mon, Oct 31, 2016 at 6:02 PM, Flavio Junqueira <
> > > fpjunqueira@yahoo.com.invalid> wrote:
> > >
> > >> Thanks, Jia. It would be good to have concrete metrics where possible.
> > >> See my comments below:
> > >>
> > >> > On 30 Oct 2016, at 10:53, Jia Zhai <zh...@gmail.com> wrote:
> > >> >
> > >> > Thanks a lot for your suggestions Flavio.
> > >> > And Guys, Here is a draft. Please help comments on it.
> > >> > Regards.
> > >> > -Jia
> > >> >
> > >> > =====================================
> > >> >
> > >> > DistributedLog
> > >> >
> > >> > DistributedLog is a high-performance replicated log service. It
> offers
> > >> >
> > >> > durability, replication and strong consistency, which provides a
> > >> fundamental
> > >> >
> > >> > building block for building reliable distributed systems.
> > >> >
> > >> > DistributedLog has been incubating since 2016-06-24.
> > >> >
> > >> > Three most important issues to address in the move towards
> graduation:
> > >> > 1. Continue to grow the community, especially people from
> > outside
> > >> > Twitter.
> > >> > [Ask the PMC for helping check the number of people subscribed to
> dev@
> > >> mail
> > >> > list]
> > >>
> > >> I think you're referring to the project PMC checking the subscription
> > >> list. I checked and we have 35 people subscribed. A lot of people have
> > >> gmail and apache.org <http://apache.org/> addresses so it is hard to
> > >> tell affiliation. One typical sign of community diversity is to have
> > active
> > >> committers from multiple organizations, which is just a natural
> > extension
> > >> of a diverse community. As folks contribute to the project, I'd expect
> > the
> > >> PPMC to offer committership to the contributors.
> > >>
> > >> Please do not refer to Twitter specifically, just say that we want to
> > >> increase diversity.
> >
>
> Agreed. We should just say that we want to increase diversity.
>
>
> > >>
> > >> > 2. Improve documentation.
> > >>
> > >> Project documentation is important, but from a community perspective,
> it
> > >> is more important to have all processes documented well: how to
> > contribute,
> > >> how to merge, notes for first time committers, how to cut a release,
> > check
> > >> licenses.
> >
>
> Yup. We have setup a guide for developers and committers:
>
> https://cwiki.apache.org/confluence/display/DL/Developer+Guide
> https://cwiki.apache.org/confluence/display/DL/Committer+Guide
>
> They are linked under the community tab in
> http://distributedlog.incubator.apache.org/
>
>
> > We need to make sure all this is in place once we suggest
> > >> graduation.
> > >>
> > >>
> > >> > 3. First Apache release
> > >>
> > >> When is the first release due? it would be good for this community to
> > >> release sooner rather later. I'd expect multiple releases upon
> > graduation.
> > >> I think I'd just say "Release successfully".
> >
>
> Or "Multiple successful releases"
>
>
> > >>
> > >> >
> > >> >
> > >> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
> be
> > >> aware
> > >> >
> > >> > of?
> > >> >
> > >> > None
> > >> >
> > >> > How has the community developed since the last report?
> > >> >
> > >> > 1. Increase in contributions from community.
> > >> >
> > >>
> > >> How do we measure this? Here are a few suggestions:
> > >>
> > >> - Number of messages to the list
> > >> - Number of jiras created/resolved
> > >> - Number of individual contributors
> >
>
> Jia,
>
> I think you can collect
>
> - number of messages by checking
> http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/
> - number of jiras by filtering jira queue
> - number of individual contributors : probably by looking at the number of
> contributors at github?
>
>
> > >>
> > >> > 2. Lots of engagement on documentation.
> > >> >
> > >>
> > >> What are you using to determine this? Mailing list discussion or jira?
> > >>
> > >> There are other interesting threads going on too, like transactions
> and
> > >> event sourcing.
> >
>
> I think pull requests can be used for counting this.
>
>
> > >>
> > >> > 3. Improved responsiveness of committers to community members
> > >> >
> > >>
> > >> I'd phrase this differently. I'd say something like:
> > >>
> > >> Increased traffic on the mailing list, in particular, due to
> committers
> > >> engaging more actively with contributors.
> > >>
> > >> >
> > >> > How has the project developed since the last report?
> > >> >
> > >> > 1. Documentation has improved for project build and project
> > deployment.
> > >> > Added more information on community page.
> > >> >
> > >>
> > >> Please try to be a bit more specific.
> > >>
> > >> > 2. Involved more discussion of new ideas and bring in new features.
> > >> Include
> > >> > major discussions like 'transaction support', 'batch commit' .etc.
> > >>
> > >> Ok, I see you talked about other threads here.
> > >>
> > >> >
> > >> > 3. First release and repackaging of the project under apache
> namespace
> > >> are
> > >> >
> > >> > being discussed, such as:
> > >> >
> > >> > - Pull requests for repackaging.
> > >> >
> > >> > - Twitter folks are working on porting twitter's bk version back to
> > >> > community
> > >>
> > >> It is a bit unclear why this is important, and I'd again avoid
> referring
> > >> to a specific company if possible.
> > >>
> > >> If there is a major change happening and the community is all
> involved,
> > >> then I'd mention it, but as stated it sounds like this is relevant to
> > the
> > >> BookKeeper community, although it affects this community because of
> the
> > >> dependency.
> >
>
> Currently distributedlog relies on some major changes made in twitter's
> bookkeeper branch, such as long poll read support, parallel recovery, delay
> ensemble change and such. we are working on merging those changes back.
>
>
> > >>
> > >> >
> > >> > - Expect to cut a release on Nov.
> > >>
> > >> We should mention this above when we refer to the first release. I'd
> > also
> > >> be interested in knowing why the delay, what is holding it, and who is
> > the
> > >> release manager. We don't necessarily need to add it to the report,
> > >> although more detail isn't bad.
> >
>
> The major blocker is https://issues.apache.org/jira/browse/DL-2. We were
> expecting to let DL depends on an official bk version rather than a version
> from twitter's branch.
>
>
> > >>
> > >> -Flavio
> > >>
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <fp...@apache.org>
> > >> wrote:
> > >> >
> > >> >> Hi Jia,
> > >> >>
> > >> >> I'd suggest that you put a draft together and share on the list so
> > >> that we
> > >> >> can comment before posting on the wiki.
> > >> >>
> > >> >> -Flavio
> > >> >>
> > >> >>> On 27 Oct 2016, at 16:44, Jia Zhai <zh...@gmail.com> wrote:
> > >> >>>
> > >> >>> Hi Guys,
> > >> >>> If there is an opportunity, I would like to have a try for this
> > >> month. :)
> > >> >>>
> > >> >>> Thanks a lot.
> > >> >>> -Jia
> > >> >>>
> > >> >>> On Thu, Oct 27, 2016 at 7:01 AM, <jo...@apache.org> wrote:
> > >> >>>
> > >> >>
> > >>
> > >>
> > >
> >
>
Re: Distributedlog Podling Report Draft - November 2016
Posted by Sijie Guo <si...@apache.org>.
Thank you Jia and Flavio. Comments inline.
On Tue, Nov 1, 2016 at 1:54 AM, Jia Zhai <zh...@gmail.com> wrote:
> Hi Sijie,
> Would you please help address some of Flavio's comments first, You may have
> more information for story behind the result. I would like to handle this
> after your comments.
>
> Thanks a lot.
> -Jia
>
> On Tue, Nov 1, 2016 at 10:42 AM, Jia Zhai <zh...@gmail.com> wrote:
>
> > Thanks a lot for your comments, will address them and post a new draft.
> >
> > On Mon, Oct 31, 2016 at 6:02 PM, Flavio Junqueira <
> > fpjunqueira@yahoo.com.invalid> wrote:
> >
> >> Thanks, Jia. It would be good to have concrete metrics where possible.
> >> See my comments below:
> >>
> >> > On 30 Oct 2016, at 10:53, Jia Zhai <zh...@gmail.com> wrote:
> >> >
> >> > Thanks a lot for your suggestions Flavio.
> >> > And Guys, Here is a draft. Please help comments on it.
> >> > Regards.
> >> > -Jia
> >> >
> >> > =====================================
> >> >
> >> > DistributedLog
> >> >
> >> > DistributedLog is a high-performance replicated log service. It offers
> >> >
> >> > durability, replication and strong consistency, which provides a
> >> fundamental
> >> >
> >> > building block for building reliable distributed systems.
> >> >
> >> > DistributedLog has been incubating since 2016-06-24.
> >> >
> >> > Three most important issues to address in the move towards graduation:
> >> > 1. Continue to grow the community, especially people from
> outside
> >> > Twitter.
> >> > [Ask the PMC for helping check the number of people subscribed to dev@
> >> mail
> >> > list]
> >>
> >> I think you're referring to the project PMC checking the subscription
> >> list. I checked and we have 35 people subscribed. A lot of people have
> >> gmail and apache.org <http://apache.org/> addresses so it is hard to
> >> tell affiliation. One typical sign of community diversity is to have
> active
> >> committers from multiple organizations, which is just a natural
> extension
> >> of a diverse community. As folks contribute to the project, I'd expect
> the
> >> PPMC to offer committership to the contributors.
> >>
> >> Please do not refer to Twitter specifically, just say that we want to
> >> increase diversity.
>
Agreed. We should just say that we want to increase diversity.
> >>
> >> > 2. Improve documentation.
> >>
> >> Project documentation is important, but from a community perspective, it
> >> is more important to have all processes documented well: how to
> contribute,
> >> how to merge, notes for first time committers, how to cut a release,
> check
> >> licenses.
>
Yup. We have setup a guide for developers and committers:
https://cwiki.apache.org/confluence/display/DL/Developer+Guide
https://cwiki.apache.org/confluence/display/DL/Committer+Guide
They are linked under the community tab in
http://distributedlog.incubator.apache.org/
> We need to make sure all this is in place once we suggest
> >> graduation.
> >>
> >>
> >> > 3. First Apache release
> >>
> >> When is the first release due? it would be good for this community to
> >> release sooner rather later. I'd expect multiple releases upon
> graduation.
> >> I think I'd just say "Release successfully".
>
Or "Multiple successful releases"
> >>
> >> >
> >> >
> >> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> >> aware
> >> >
> >> > of?
> >> >
> >> > None
> >> >
> >> > How has the community developed since the last report?
> >> >
> >> > 1. Increase in contributions from community.
> >> >
> >>
> >> How do we measure this? Here are a few suggestions:
> >>
> >> - Number of messages to the list
> >> - Number of jiras created/resolved
> >> - Number of individual contributors
>
Jia,
I think you can collect
- number of messages by checking
http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/
- number of jiras by filtering jira queue
- number of individual contributors : probably by looking at the number of
contributors at github?
> >>
> >> > 2. Lots of engagement on documentation.
> >> >
> >>
> >> What are you using to determine this? Mailing list discussion or jira?
> >>
> >> There are other interesting threads going on too, like transactions and
> >> event sourcing.
>
I think pull requests can be used for counting this.
> >>
> >> > 3. Improved responsiveness of committers to community members
> >> >
> >>
> >> I'd phrase this differently. I'd say something like:
> >>
> >> Increased traffic on the mailing list, in particular, due to committers
> >> engaging more actively with contributors.
> >>
> >> >
> >> > How has the project developed since the last report?
> >> >
> >> > 1. Documentation has improved for project build and project
> deployment.
> >> > Added more information on community page.
> >> >
> >>
> >> Please try to be a bit more specific.
> >>
> >> > 2. Involved more discussion of new ideas and bring in new features.
> >> Include
> >> > major discussions like 'transaction support', 'batch commit' .etc.
> >>
> >> Ok, I see you talked about other threads here.
> >>
> >> >
> >> > 3. First release and repackaging of the project under apache namespace
> >> are
> >> >
> >> > being discussed, such as:
> >> >
> >> > - Pull requests for repackaging.
> >> >
> >> > - Twitter folks are working on porting twitter's bk version back to
> >> > community
> >>
> >> It is a bit unclear why this is important, and I'd again avoid referring
> >> to a specific company if possible.
> >>
> >> If there is a major change happening and the community is all involved,
> >> then I'd mention it, but as stated it sounds like this is relevant to
> the
> >> BookKeeper community, although it affects this community because of the
> >> dependency.
>
Currently distributedlog relies on some major changes made in twitter's
bookkeeper branch, such as long poll read support, parallel recovery, delay
ensemble change and such. we are working on merging those changes back.
> >>
> >> >
> >> > - Expect to cut a release on Nov.
> >>
> >> We should mention this above when we refer to the first release. I'd
> also
> >> be interested in knowing why the delay, what is holding it, and who is
> the
> >> release manager. We don't necessarily need to add it to the report,
> >> although more detail isn't bad.
>
The major blocker is https://issues.apache.org/jira/browse/DL-2. We were
expecting to let DL depends on an official bk version rather than a version
from twitter's branch.
> >>
> >> -Flavio
> >>
> >> >
> >> >
> >> >
> >> >
> >> > On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <fp...@apache.org>
> >> wrote:
> >> >
> >> >> Hi Jia,
> >> >>
> >> >> I'd suggest that you put a draft together and share on the list so
> >> that we
> >> >> can comment before posting on the wiki.
> >> >>
> >> >> -Flavio
> >> >>
> >> >>> On 27 Oct 2016, at 16:44, Jia Zhai <zh...@gmail.com> wrote:
> >> >>>
> >> >>> Hi Guys,
> >> >>> If there is an opportunity, I would like to have a try for this
> >> month. :)
> >> >>>
> >> >>> Thanks a lot.
> >> >>> -Jia
> >> >>>
> >> >>> On Thu, Oct 27, 2016 at 7:01 AM, <jo...@apache.org> wrote:
> >> >>>
> >> >>
> >>
> >>
> >
>
Re: Distributedlog Podling Report Draft - November 2016
Posted by Jia Zhai <zh...@gmail.com>.
Hi Sijie,
Would you please help address some of Flavio's comments first, You may have
more information for story behind the result. I would like to handle this
after your comments.
Thanks a lot.
-Jia
On Tue, Nov 1, 2016 at 10:42 AM, Jia Zhai <zh...@gmail.com> wrote:
> Thanks a lot for your comments, will address them and post a new draft.
>
> On Mon, Oct 31, 2016 at 6:02 PM, Flavio Junqueira <
> fpjunqueira@yahoo.com.invalid> wrote:
>
>> Thanks, Jia. It would be good to have concrete metrics where possible.
>> See my comments below:
>>
>> > On 30 Oct 2016, at 10:53, Jia Zhai <zh...@gmail.com> wrote:
>> >
>> > Thanks a lot for your suggestions Flavio.
>> > And Guys, Here is a draft. Please help comments on it.
>> > Regards.
>> > -Jia
>> >
>> > =====================================
>> >
>> > DistributedLog
>> >
>> > DistributedLog is a high-performance replicated log service. It offers
>> >
>> > durability, replication and strong consistency, which provides a
>> fundamental
>> >
>> > building block for building reliable distributed systems.
>> >
>> > DistributedLog has been incubating since 2016-06-24.
>> >
>> > Three most important issues to address in the move towards graduation:
>> > 1. Continue to grow the community, especially people from outside
>> > Twitter.
>> > [Ask the PMC for helping check the number of people subscribed to dev@
>> mail
>> > list]
>>
>> I think you're referring to the project PMC checking the subscription
>> list. I checked and we have 35 people subscribed. A lot of people have
>> gmail and apache.org <http://apache.org/> addresses so it is hard to
>> tell affiliation. One typical sign of community diversity is to have active
>> committers from multiple organizations, which is just a natural extension
>> of a diverse community. As folks contribute to the project, I'd expect the
>> PPMC to offer committership to the contributors.
>>
>> Please do not refer to Twitter specifically, just say that we want to
>> increase diversity.
>>
>> > 2. Improve documentation.
>>
>> Project documentation is important, but from a community perspective, it
>> is more important to have all processes documented well: how to contribute,
>> how to merge, notes for first time committers, how to cut a release, check
>> licenses. We need to make sure all this is in place once we suggest
>> graduation.
>>
>>
>> > 3. First Apache release
>>
>> When is the first release due? it would be good for this community to
>> release sooner rather later. I'd expect multiple releases upon graduation.
>> I think I'd just say "Release successfully".
>>
>> >
>> >
>> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware
>> >
>> > of?
>> >
>> > None
>> >
>> > How has the community developed since the last report?
>> >
>> > 1. Increase in contributions from community.
>> >
>>
>> How do we measure this? Here are a few suggestions:
>>
>> - Number of messages to the list
>> - Number of jiras created/resolved
>> - Number of individual contributors
>>
>> > 2. Lots of engagement on documentation.
>> >
>>
>> What are you using to determine this? Mailing list discussion or jira?
>>
>> There are other interesting threads going on too, like transactions and
>> event sourcing.
>>
>> > 3. Improved responsiveness of committers to community members
>> >
>>
>> I'd phrase this differently. I'd say something like:
>>
>> Increased traffic on the mailing list, in particular, due to committers
>> engaging more actively with contributors.
>>
>> >
>> > How has the project developed since the last report?
>> >
>> > 1. Documentation has improved for project build and project deployment.
>> > Added more information on community page.
>> >
>>
>> Please try to be a bit more specific.
>>
>> > 2. Involved more discussion of new ideas and bring in new features.
>> Include
>> > major discussions like 'transaction support', 'batch commit' .etc.
>>
>> Ok, I see you talked about other threads here.
>>
>> >
>> > 3. First release and repackaging of the project under apache namespace
>> are
>> >
>> > being discussed, such as:
>> >
>> > - Pull requests for repackaging.
>> >
>> > - Twitter folks are working on porting twitter's bk version back to
>> > community
>>
>> It is a bit unclear why this is important, and I'd again avoid referring
>> to a specific company if possible.
>>
>> If there is a major change happening and the community is all involved,
>> then I'd mention it, but as stated it sounds like this is relevant to the
>> BookKeeper community, although it affects this community because of the
>> dependency.
>>
>> >
>> > - Expect to cut a release on Nov.
>>
>> We should mention this above when we refer to the first release. I'd also
>> be interested in knowing why the delay, what is holding it, and who is the
>> release manager. We don't necessarily need to add it to the report,
>> although more detail isn't bad.
>>
>> -Flavio
>>
>> >
>> >
>> >
>> >
>> > On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <fp...@apache.org>
>> wrote:
>> >
>> >> Hi Jia,
>> >>
>> >> I'd suggest that you put a draft together and share on the list so
>> that we
>> >> can comment before posting on the wiki.
>> >>
>> >> -Flavio
>> >>
>> >>> On 27 Oct 2016, at 16:44, Jia Zhai <zh...@gmail.com> wrote:
>> >>>
>> >>> Hi Guys,
>> >>> If there is an opportunity, I would like to have a try for this
>> month. :)
>> >>>
>> >>> Thanks a lot.
>> >>> -Jia
>> >>>
>> >>> On Thu, Oct 27, 2016 at 7:01 AM, <jo...@apache.org> wrote:
>> >>>
>> >>
>>
>>
>