Re: DistributedLog Podling Report Draft - Feb 2017

2017-02-01 Thread Jia Zhai
+1 thanks for this.

On Thu, Feb 2, 2017 at 5:10 AM, Sijie Guo  wrote:

> If there is no objection here, I would like to update the incubator board
> report.
>
> Can any mentors take a look too?
>
> - Sijie
>
> On Wed, Feb 1, 2017 at 9:17 AM, Khurrum Nasim 
> wrote:
>
> > +1 thank you for putting this up, Sijie.
> >
> > - KN
> >
> > On Tue, Jan 31, 2017 at 11:17 PM, Xi Liu  wrote:
> >
> > > lgtm. +1
> > >
> > > it might be good to mention the slack channel for community
> development.
> > >
> > > - Xi
> > >
> > > On Tue, Jan 31, 2017 at 2:01 PM, Sijie Guo  wrote:
> > >
> > > > Hi, all,
> > > >
> > > > Here is the draft of podling report for Feb 2017. Please help review
> > it.
> > > >
> > > > =
> > > >
> > > > 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.
> > > >- 127 created and 103 resolved issues in community JIRA between
> Nov
> > > 2016
> > > > and Feb 2017.
> > > > 2. Lots of engagements on feature proposals - 7 improvement
> proposals.
> > > > 3. Increased traffic on the mailing list, in particular, due to
> > > committers
> > > > engaging more actively with contributors.
> > > >- we have 43 people subscribed mail list.
> > > >
> > > > How has the project developed since the last report?
> > > >
> > > > The community is voting for release 0.4.0-incubating.
> > > >
> > > > - Sijie
> > > >
> > >
> >
>


Re: Podling Report Reminder - November 2016

2016-10-27 Thread Jia Zhai
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,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 16 November 2016, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, November 02).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/November2016
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>


Distributedlog Podling Report Draft - November 2016

2016-10-30 Thread Jia Zhai
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]
2.   Improve documentation.
3.   First Apache release


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.

2. Lots of engagement on documentation.

3. Improved responsiveness of committers to community members


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.

2. Involved more discussion of new ideas and bring in new features. Include
major discussions like 'transaction support', 'batch commit' .etc.

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

- Expect to cut a release on Nov.




On Fri, Oct 28, 2016 at 11:10 PM, Flavio Junqueira <f...@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 <zhaiji...@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, <johndam...@apache.org> wrote:
> >
>


Re: Distributedlog Podling Report Draft - November 2016

2016-10-31 Thread Jia Zhai
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 <
fpjunque...@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 <zhaiji...@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 

Re: Distributedlog Podling Report Draft - November 2016

2016-11-03 Thread Jia Zhai
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 <sij...@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 <johndam...@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 <f...@apache.org> wrote:
> > > +1
> > >
> > > > On 02 Nov 2016, at 09:22, Khurrum Nasim <khurrumnas...@gmail.com>
> > wrote:
> > > >
> > > > +1 from me (non-binding).
> > > >
> > > > - KN
> > > >
> > > > On Tue, Nov 1, 2016 at 7:18 PM, Jia Zhai <zhaiji...@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 <zhaiji...@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.
> > > >>>>

Re: Distributedlog Podling Report Draft - November 2016

2016-11-01 Thread Jia Zhai
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 <zhaiji...@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 <zhaiji...@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 <
> > > fpjunque...@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 <zhaiji...@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 contribut

Re: Is there a page like "who is using BK/DL"?

2016-12-09 Thread Jia Zhai
Thanks for the suggestions. would like to collect some suggestions and
feedbacks here, then update the tickets. And will update the ticket at next
Wensday, Is this OK?

On Fri, Dec 9, 2016 at 1:01 PM, Sijie Guo <si...@apache.org> wrote:

> Good suggestions, Xi.
>
> Jia, do you want to update draft and then update the tickets?
>
> - Sijie
>
> On Thu, Dec 8, 2016 at 9:25 AM, Xi Liu <xi.liu@gmail.com> wrote:
>
> > Jia,
> >
> > It might be good to add
> >
> > - why do you use bookkeeper/distributedlog?
> >
> > - what areas are you working on or interested in
> bookkeeper/distributedlog?
> >
> > - Xi
> >
> > On Wed, Dec 7, 2016 at 3:49 AM, Jia Zhai <zhaiji...@gmail.com> wrote:
> >
> > > Here is a draft content(referenced other project) for BookKeeper, Would
> > you
> > > please kindly help comment and refine it?
> > > ```
> > >
> > > Thanks for enjoys Apache BookKeeper sincerely. We will try our best to
> > keep
> > > Apache BookKeeper open source community constantly growing and healthy.
> > > The purpose of this issue:
> > >
> > >- We want to attract more people to participate in the contribution;
> > >
> > >
> > >- We will be friends when you begin to use Apache Bookkeeper. we
> will
> > >together going, together gossip, let Apache Bookkeeper better
> > > development;
> > >
> > >
> > >- We will push you our recently documents, release report,
> activities
> > >etc.
> > >
> > > What is expected:
> > > submit a comment, the comment including:
> > >
> > >- your company, school or organization.
> > >
> > >
> > >- your location(city).
> > >
> > >
> > >- your contact: email, blog, twitter.
> > >
> > >
> > >- what scenarios do you use Apache BookKeeper.
> > >
> > > Thank you again for your participation !
> > >
> > > ```
> > >
> > > Regards.
> > > -Jia
> > >
> > >
> > > On Wed, Dec 7, 2016 at 7:13 PM, Jia Zhai <zhaiji...@gmail.com> wrote:
> > >
> > > > Got it. I will open a ticket on Jira first.
> > > >
> > > > On Wed, Dec 7, 2016 at 11:05 AM, Khurrum Nasim <
> > khurrumnas...@gmail.com>
> > > > wrote:
> > > >
> > > >> +1 for this idea.
> > > >>
> > > >> - KN
> > > >>
> > > >> On Mon, Dec 5, 2016 at 9:59 PM, Sijie Guo <si...@apache.org> wrote:
> > > >>
> > > >> > Sounds a good idea! Let's create one for that purpose.
> > > >> >
> > > >> > Sijie
> > > >> >
> > > >> > On Dec 5, 2016 6:00 PM, "Jia Zhai" <zhaiji...@gmail.com> wrote:
> > > >> >
> > > >> > > Yes. That is what I mean. By it, we  may get more direct info
> > about
> > > >> who
> > > >> > is
> > > >> > > intresting and want to try on it, not only who has used it for
> big
> > > >> case.
> > > >> > >
> > > >> > > On Tue, Dec 6, 2016 at 4:21 AM, Sijie Guo <si...@apache.org>
> > wrote:
> > > >> > >
> > > >> > > > I think both BK and DL have the poweredby cwiki page. Do you
> > mean
> > > we
> > > >> > > open a
> > > >> > > > dummy github issue for people to comment to register
> themselves?
> > > >> > > >
> > > >> > > > - Sijie
> > > >> > > >
> > > >> > > > On Sun, Dec 4, 2016 at 6:50 PM, Jia Zhai <zhaiji...@gmail.com
> >
> > > >> wrote:
> > > >> > > >
> > > >> > > > > Hi guys,
> > > >> > > > > I found that in project RocketMQ, there is an open issue:
> > > >> > > > > https://github.com/alibaba/RocketMQ/issues/1 , in which a
> lot
> > > of
> > > >> > user
> > > >> > > /
> > > >> > > > > developer registered themself.  This may bring benifit of
> > > >> connecting
> > > >> > > > > between usr, developor and community.
> > > >> > > > >
> > > >> > > > > Is there a need for us to have such a similar issue or page
> > > >> related
> > > >> > to
> > > >> > > > > BK/DL?
> > > >> > > > >
> > > >> > > > > Regards.
> > > >> > > > > -Jia
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>


Re: [discuss] Official Slack or Gitter channel for Distributedlog

2016-12-14 Thread Jia Zhai
+1 for slack

On Wed, Dec 14, 2016 at 10:00 PM, Flavio Junqueira  wrote:

> I'm +1 for Slack.
>
> -Flavio
>
> > On 14 Dec 2016, at 08:32, Stevo Slavić  wrote:
> >
> > Either works for me, as long as it's documented in project website and
> readme file.
> >
> > On Wed, Dec 14, 2016 at 9:16 AM, Xi Liu > wrote:
> > I would prefer using slack channel.
> >
> > - Xi
> >
> > On Wed, Dec 14, 2016 at 12:04 AM, Sijie Guo > wrote:
> >
> > > Hi all,
> > >
> > > As some forks are asking the slack or Gitter for DL, and the ASF
> provides
> > > the official support for both of them, I'd like to start a discussion
> > > thread about this :
> > >
> > > - do you want an official slack or Gitter channel?
> > > -  which channel do you prefer? Slack or Gitter?
> > >
> > > Please comment with your opinion. Appreciate your participation.
> > >
> > > Thanks,
> > > Sijie
> > >
> >
>
>


Re: DistributedLog Podling Report Draft - December 2016

2016-12-06 Thread Jia Zhai
+1 LGTM.
looking foward for the first release.

On Wed, Dec 7, 2016 at 12:19 AM, Sijie Guo  wrote:

> Hi, all,
>
> Here is the draft of podling report. Please help review it.
>
> =
>
> 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.
>- 20 created and 9 resolved issues in community JIRA in November.
> 2. Lots of engagements on feature proposals.
> 3. Increased traffic on the mailing list, in particular, due to committers
> engaging more actively with contributors.
>- we have 36 people subscribed mail list.
>- 192 messages to distributedlog mail list in November.
>
> How has the project developed since the last report?
>
> The community is working on the first release. The first release will be in
> mid December.
>
> - Sijie
>


Re: Is there a page like "who is using BK/DL"?

2016-12-07 Thread Jia Zhai
Got it. I will open a ticket on Jira first.

On Wed, Dec 7, 2016 at 11:05 AM, Khurrum Nasim <khurrumnas...@gmail.com>
wrote:

> +1 for this idea.
>
> - KN
>
> On Mon, Dec 5, 2016 at 9:59 PM, Sijie Guo <si...@apache.org> wrote:
>
> > Sounds a good idea! Let's create one for that purpose.
> >
> > Sijie
> >
> > On Dec 5, 2016 6:00 PM, "Jia Zhai" <zhaiji...@gmail.com> wrote:
> >
> > > Yes. That is what I mean. By it, we  may get more direct info about who
> > is
> > > intresting and want to try on it, not only who has used it for big
> case.
> > >
> > > On Tue, Dec 6, 2016 at 4:21 AM, Sijie Guo <si...@apache.org> wrote:
> > >
> > > > I think both BK and DL have the poweredby cwiki page. Do you mean we
> > > open a
> > > > dummy github issue for people to comment to register themselves?
> > > >
> > > > - Sijie
> > > >
> > > > On Sun, Dec 4, 2016 at 6:50 PM, Jia Zhai <zhaiji...@gmail.com>
> wrote:
> > > >
> > > > > Hi guys,
> > > > > I found that in project RocketMQ, there is an open issue:
> > > > > https://github.com/alibaba/RocketMQ/issues/1 , in which a lot of
> > user
> > > /
> > > > > developer registered themself.  This may bring benifit of
> connecting
> > > > > between usr, developor and community.
> > > > >
> > > > > Is there a need for us to have such a similar issue or page related
> > to
> > > > > BK/DL?
> > > > >
> > > > > Regards.
> > > > > -Jia
> > > > >
> > > >
> > >
> >
>


Re: Is there a page like "who is using BK/DL"?

2016-12-07 Thread Jia Zhai
Here is a draft content(referenced other project) for BookKeeper, Would you
please kindly help comment and refine it?
```

Thanks for enjoys Apache BookKeeper sincerely. We will try our best to keep
Apache BookKeeper open source community constantly growing and healthy.
The purpose of this issue:

   - We want to attract more people to participate in the contribution;


   - We will be friends when you begin to use Apache Bookkeeper. we will
   together going, together gossip, let Apache Bookkeeper better development;


   - We will push you our recently documents, release report, activities
   etc.

What is expected:
submit a comment, the comment including:

   - your company, school or organization.


   - your location(city).


   - your contact: email, blog, twitter.


   - what scenarios do you use Apache BookKeeper.

Thank you again for your participation !

```

Regards.
-Jia


On Wed, Dec 7, 2016 at 7:13 PM, Jia Zhai <zhaiji...@gmail.com> wrote:

> Got it. I will open a ticket on Jira first.
>
> On Wed, Dec 7, 2016 at 11:05 AM, Khurrum Nasim <khurrumnas...@gmail.com>
> wrote:
>
>> +1 for this idea.
>>
>> - KN
>>
>> On Mon, Dec 5, 2016 at 9:59 PM, Sijie Guo <si...@apache.org> wrote:
>>
>> > Sounds a good idea! Let's create one for that purpose.
>> >
>> > Sijie
>> >
>> > On Dec 5, 2016 6:00 PM, "Jia Zhai" <zhaiji...@gmail.com> wrote:
>> >
>> > > Yes. That is what I mean. By it, we  may get more direct info about
>> who
>> > is
>> > > intresting and want to try on it, not only who has used it for big
>> case.
>> > >
>> > > On Tue, Dec 6, 2016 at 4:21 AM, Sijie Guo <si...@apache.org> wrote:
>> > >
>> > > > I think both BK and DL have the poweredby cwiki page. Do you mean we
>> > > open a
>> > > > dummy github issue for people to comment to register themselves?
>> > > >
>> > > > - Sijie
>> > > >
>> > > > On Sun, Dec 4, 2016 at 6:50 PM, Jia Zhai <zhaiji...@gmail.com>
>> wrote:
>> > > >
>> > > > > Hi guys,
>> > > > > I found that in project RocketMQ, there is an open issue:
>> > > > > https://github.com/alibaba/RocketMQ/issues/1 , in which a lot of
>> > user
>> > > /
>> > > > > developer registered themself.  This may bring benifit of
>> connecting
>> > > > > between usr, developor and community.
>> > > > >
>> > > > > Is there a need for us to have such a similar issue or page
>> related
>> > to
>> > > > > BK/DL?
>> > > > >
>> > > > > Regards.
>> > > > > -Jia
>> > > > >
>> > > >
>> > >
>> >
>>
>
>


Re: Is there a page like "who is using BK/DL"?

2016-12-05 Thread Jia Zhai
Yes. That is what I mean. By it, we  may get more direct info about who is
intresting and want to try on it, not only who has used it for big case.

On Tue, Dec 6, 2016 at 4:21 AM, Sijie Guo <si...@apache.org> wrote:

> I think both BK and DL have the poweredby cwiki page. Do you mean we open a
> dummy github issue for people to comment to register themselves?
>
> - Sijie
>
> On Sun, Dec 4, 2016 at 6:50 PM, Jia Zhai <zhaiji...@gmail.com> wrote:
>
> > Hi guys,
> > I found that in project RocketMQ, there is an open issue:
> > https://github.com/alibaba/RocketMQ/issues/1 , in which a lot of user /
> > developer registered themself.  This may bring benifit of connecting
> > between usr, developor and community.
> >
> > Is there a need for us to have such a similar issue or page related to
> > BK/DL?
> >
> > Regards.
> > -Jia
> >
>


Re: [VOTE] Release 0.4.0, release candidate #1

2017-01-08 Thread Jia Zhai
+1 binding.

Build and smoke-test both passed on my local machine.

Thanks a lot for the work.

On Mon, Jan 9, 2017 at 12:04 PM, Sijie Guo  wrote:

> Hi all,
>
> Please review and vote on the release candidate #1 for the version 0.4.0,
> as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your review, which includes:
>
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
> [2],
> * all artifacts to be deployed to the Maven Central Repository [3],
> * source code tag "v0.4.0-RC1" [4],
> * website pull request listing the release [5] and publishing the API
> reference manual.
>
> A simple instruction for validation the source and binary packages.
>
> - source package: run "*./scripts/integration/smoketest.sh*" after
> building
> the package with "*mvn clean apache-rat:check package findbugs:check
> -DskipTests*"
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PPMC affirmative votes.
>
> Thanks,
> Sijie
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12320620=12337980
> [2]
> https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> incubating/
> [3]
> https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1001/
> [4]
> https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC1
> [5] https://github.com/apache/incubator-distributedlog/pull/109
>


Re: [VOTE] Release 0.4.0, release candidate #3

2017-03-30 Thread Jia Zhai
+1 binding.

"mvn apache-rat:check package findbugs:check -DskipTests" execute
successfully, after exclude 1 file for rat check, by adding this line at
line232 of pom.xml
```
src/main/resources/DISCLAIMER.bin.txt
```

On Thu, Mar 30, 2017 at 12:46 AM, Sijie Guo  wrote:

> I think apache-rat:check will fail because of
> https://issues.apache.org/jira/browse/DL-195. But I don't think it is a
> blocker for the release.
>
> - Sijie
>
> On Tue, Mar 28, 2017 at 3:29 PM, Sijie Guo  wrote:
>
> > Hi all,
> >
> > Please review and vote on the release candidate #3 for the version 0.4.0,
> > as follows:
> >
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > The complete staging area is available for your review, which includes:
> >
> > * JIRA release notes [1],
> > * the official Apache source release to be deployed to
> dist.apache.org
> >  [2],
> > * all artifacts to be deployed to the Maven Central Repository [3],
> > * source code tag "v0.4.0-incubating-RC1_2.11" (for scala 2.11) and
> > "v0.4.0-incubating-RC1_2.10" (for scala 2.10) [4][5],
> > * website pull request listing the release [6] and publishing the API
> > reference manual.
> >
> > A simple instruction for validation the source and binary packages.
> >
> > - source package: building the package with "*mvn clean apache-rat:check
> > package findbugs:check -DskipTests*"
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PPMC affirmative votes.
> >
> > Thanks,
> > Sijie
> >
> > [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > version=12337980==12320620
> > [2] https://dist.apache.org/repos/dist/dev/incubator/
> distributedlog/0.4.0-
> > incubating-RC3/
> > [3] https://repository.apache.org/content/repositories/
> > orgapachedistributedlog-1006/
> > [4] https://github.com/apache/incubator-distributedlog/tree/
> > v0.4.0-incubating-RC3_2.11
> > [5] https://github.com/apache/incubator-distributedlog/tree/
> > v0.4.0-incubating-RC3_2.10
> > [6] https://github.com/apache/incubator-distributedlog/pull/109
> >
>


Re: [VOTE] Release 0.4.0, release candidate #4

2017-04-13 Thread Jia Zhai
+1 (non-binding)

for both distributedlog_2.10 and distributedlog_2.11:
- verified packages (md5, asc and sha1 all look good)
- the source package build and test all run successfully.
- NOTICE, DISCLAIME, License headers look good.


On Thu, Apr 13, 2017 at 3:36 PM, Sijie Guo  wrote:

> Hi all,
>
> Please review and vote on the release candidate #4 for the version 0.4.0,
> as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> The complete staging area is available for your review, which includes:
>
> * JIRA release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
>  [2],
> * all artifacts to be deployed to the Maven Central Repository [3][4],
> * source code tag "v0.4.0-incubating-RC4_2.11" (for scala 2.11) and
> "v0.4.0-incubating-RC4_2.10" (for scala 2.10) [5][6],
> * website pull request listing the release [7] and publishing the API
> reference manual.
>
> A simple instruction for validation the source and binary packages.
>
> - source package: building the package with "*mvn clean apache-rat:check
> package findbugs:check -DskipTests*"
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PPMC affirmative votes.
>
> Thanks,
> Sijie
>
> [1] https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12337980==12320620
> [2]
> https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
> incubating-RC4/
> [3]
> https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1007/
> [4]
> https://repository.apache.org/content/repositories/
> orgapachedistributedlog-1008/
> [5]
> https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC4_2.11
> [6]
> https://github.com/apache/incubator-distributedlog/tree/
> v0.4.0-incubating-RC4_2.10
> [7] https://github.com/apache/incubator-distributedlog/pull/109
>


Re: [DISCUSS] Slack Channel for BookKeeper

2017-07-24 Thread Jia Zhai
 It is great to have a slack channel. It make things more effective and
smooth.

On Tue, Jul 25, 2017 at 8:11 AM, Sijie Guo  wrote:

> Hi all,
>
> What do you guys all think about having a dedicated slack channel for
> informal discussion for the community? There are a handful of Apache
> projects are doing that already, there are also ways to have a bot that
> sends daily digest of the conversation to the mailing lists (to keep the
> records in ASF infrastructure).
>
> As the followup steps for merging DL into BookKeeper, we are transferring
> the DL slack channel to BookKeeper PMC. We can just make it a BK slack
> channel, and have different channels under it for different discussions.
>
> Thoughts?
>
> - Sijie
>


Re: [Discuss] Release DL 0.5.0

2017-07-26 Thread Jia Zhai
Hi sijie,
I am inserested to be the release manager for 0.5.0, but there will be some
instruction and help needed from you guys. :)

Thanks.
-Jia

On Thu, Jul 27, 2017 at 1:35 AM, Sijie Guo <guosi...@gmail.com> wrote:

> +1. Jia, thank you for raising this up.
>
> I have a few questions:
>
> - Release Manager:
>   Any volunteers on driving this release?
>
> - Pending changes:
>   What are the pending changes that are blocking DL upgrade BK to 4.5.0
> (both BK and DL side)?
>
> Any thoughts?
>
> - Sijie
>
>
>
> On Tue, Jul 25, 2017 at 6:17 PM, Jia Zhai <zhaiji...@gmail.com> wrote:
>
> > Hi All,
> > Because DL is merged to BK, if BK is going to release 4.5.0, it would be
> > good that DL can release 0.5.0 as well.  What do you think of this? :)
> >
> > Thanks a lot.
> > -Jia
> >
>


Re: Slack Channel

2017-08-01 Thread Jia Zhai
The links works well.
I am updating the documentation for slack channel.
https://github.com/apache/bookkeeper/pull/341

On Tue, Aug 1, 2017 at 10:46 AM, Sijie Guo  wrote:

> Hi all,
>
> The slack channel https://apachebookkeeper.slack.com is live now. If you
> have emails (@apache.org), you can signup with
> https://apachebookkeeper.slack.com/signup.
>
> If you don't have apache emails, you can auto-invite yourself in
> https://apachebookkeeper.herokuapp.com/
>
> If you were already in apache distributedlog slack before, you don't need
> to sign up this time.
>
> Let me know if you have any questions.
>
> - Sijie
>


Re: [VOTE] Slack Channel for BookKeeper

2017-07-27 Thread Jia Zhai
+1

On Fri, Jul 28, 2017 at 4:02 AM, atracymartin 
wrote:

> +1
>
>
> Sent from my T-Mobile 4G LTE Device
>  Original message From: Sijie Guo 
> Date: 7/27/17  2:02 PM  (GMT-05:00) To: dev@distributedlog.incubator.
> apache.org, d...@bookkeeper.apache.org Subject: [VOTE] Slack Channel for
> BookKeeper
> Start a vote thread for transferring the DL slack channel to BK.
>
> The propose is:
>
> - transfer the dl slack channel apachedistributedlog.slack.com to
> apachebookkeeper.slack.com
> - the owner will be BookKeeper PMC (priv...@bookkeeper.apache.org)
>
> One note:
>
> - the slack channel is for informal/immediate discussion. no decisions are
> made in slack channel. decision related discussions should be recorded in
> ASF (either mailing list, JIR or wiki)
>
> Please vote +1, 0, -1. The vote will be open for 72 hours.
>
> - Sijie
>


[Discuss] Release DL 0.5.0

2017-07-25 Thread Jia Zhai
Hi All,
Because DL is merged to BK, if BK is going to release 4.5.0, it would be
good that DL can release 0.5.0 as well.  What do you think of this? :)

Thanks a lot.
-Jia


Re: [VOTE] Merge DistributedLog as the subproject of Apache BookKeeper

2017-06-09 Thread Jia Zhai
+1 (non-binding)

On Fri, Jun 9, 2017 at 3:02 PM, Stevo Slavić  wrote:

> +1 (non-binding)
>
> On Fri, Jun 9, 2017 at 8:47 AM, Sijie Guo  wrote:
>
> > (dropping general@)
> >
> > - Sijie
> >
> > On Thu, Jun 8, 2017 at 5:21 PM, Sijie Guo  wrote:
> >
> > > ( /cc bookkeeper dev@ and incubator general@ for awareness )
> > >
> > > Hi all,
> > >
> > > There was a joint discussion between BookKeeper PMC and DistributedLog
> > > PPMC about moving the development of DistributedLog as part of Apache
> > > BookKeeper. The reasons behind it are:
> > >
> > > First, DistributedLog is born as an extension to BookKeeper, to offer
> > > continuous log streams as the service. The ledger API in bookkeeper is
> a
> > > lower level API and has learning curves, while the log stream API in
> > > distributedlog is a higher level API that simplifies the usage. The
> > > combination of ledger API and stream API would offer a better
> > > developer/user experience for applications.
> > >
> > > Secondly, using ledgers to build continuous (re-openable) log stream
> is a
> > > very common pattern for BookKeeper use cases. We did this for HDFS
> > namenode
> > > journal, for Hedwig, for DistributedLog, and for Pulsar. The same
> pattern
> > > has been implemented again and again. Merge DistributedLog (also
> > > ManagedLedger in Pulsar) with BookKeeper will consolidate all the
> > > development efforts around this common 'log stream' pattern.
> > >
> > > Thirdly, the 'log' stream abstraction is a good abstraction for both
> > > messaging and streaming. Internally at BookKeeper, there are a few
> places
> > > that can use such 'messaging' facility to improve bookkeeper itself.
> the
> > > log stream in DistributedLog can be used internally at bookkeeper for
> > > streaming changes as well.
> > >
> > > We choose merging DistributedLog as subproject rather than modules. It
> is
> > > a softer starting point to avoid disrupting the folks who are depending
> > on
> > > the ledger api alone. The BookKeeper PMC and DistributedLog PPMC has
> > > achieved initial consensus on this merge. There is an official VOTE
> > ongoing
> > > in bookkeeper PMC. We'd like to bring this to the distributedlog
> > community
> > > for a community vote following the guidelines here
> > > .
> > >
> > > Please vote +1 if in favor of merging DistributedLog to BookKeeper, and
> > -1
> > > if not. The vote will be open until Tuesday 13rd June, 18:00 PST.
> > >
> > > - Sijie
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>


[Discuss] Try Github issues for Issue tracking

2017-06-19 Thread Jia Zhai
Hi all,

Recently, Apache BookKeeper community discussed and decided to have a try
on "github issues" for issue tracking,  What do you think of DistributedLog
also have a try on “github issues”? :)


At here, you could find the related discussion of BookKeeper here:
http://mail-archives.apache.org/mod_mbox/bookkeeper-dev/201706.mbox/thread?2


And here is a proposal for BookKeeper github issues:

https://cwiki.apache.org/confluence/display/BOOKKEEPER/BP-9+-+Github+issues+for+Issue+Tracking


Thanks a lot.

-Jia


Re: DistributedLog Podling Report Draft - May 2017

2017-05-01 Thread Jia Zhai
+1

On Tue, May 2, 2017 at 8:54 AM, Franck Cuny  wrote:

> +1
>
> On Mon, May 1, 2017 at 10:02 AM Leigh Stewart  >
> wrote:
>
> > +1
> >
> > On Mon, May 1, 2017 at 9:43 AM, Sijie Guo  wrote:
> >
> > > Hi, all,
> > >
> > > Here is the draft of podling report for May 2017. Please help review
> it.
> > >
> > > =
> > >
> > > 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. community
> > >
> > > - Sijie gave a talk about DistributedLog at Strata+Hadoop San Jose.
> > > - The DistributedLog paper is accepted at ICDE 2017.
> > > - Leigh Stewart gave a presentation about DistributedLog at ICDE.
> > >
> > > 2. 44 people subscribed to dev mail list,
> > > 8 improvement proposal in progress,
> > > and 72 open issues.
> > >
> > > How has the project developed since the last report?
> > >
> > > - We have released the first Apache version : 0.4.0-incubating on April
> > 25.
> > > - We start the work on release 0.5.0-incubating.
> > >
> > > - Sijie
> > >
> >
> --
> -franck
>


[jira] [Commented] (DL-120) Open a long live Ticket for "Who is using DistriburtedLog"

2016-12-09 Thread Jia Zhai (JIRA)

[ 
https://issues.apache.org/jira/browse/DL-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15734879#comment-15734879
 ] 

Jia Zhai commented on DL-120:
-

There is a discussion in the dev mail thread. will update here once collect 
feedbacks. Thanks.

> Open a long live Ticket for "Who is using DistriburtedLog"
> --
>
> Key: DL-120
> URL: https://issues.apache.org/jira/browse/DL-120
> Project: DistributedLog
>  Issue Type: Bug
>Reporter: Jia Zhai
>
> As discussed, would like to create an always open issue "who is using 
> DistributedLog" on github.
> Here is some example of other project:
> [https://github.com/alibaba/RocketMQ/issues/1]
> [https://github.com/mgechev/angular-seed/issues/855]
> [https://github.com/labstack/echo/issues/295]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (DL-120) Open a long live Ticket for "Who is using DistriburtedLog"

2016-12-07 Thread Jia Zhai (JIRA)
Jia Zhai created DL-120:
---

 Summary: Open a long live Ticket for "Who is using DistriburtedLog"
 Key: DL-120
 URL: https://issues.apache.org/jira/browse/DL-120
 Project: DistributedLog
  Issue Type: Bug
Reporter: Jia Zhai


As discussed, would like to create an always open issue "who is using 
DistributedLog" on github.

Here is some example of other project:
[https://github.com/alibaba/RocketMQ/issues/1]
[https://github.com/mgechev/angular-seed/issues/855]
[https://github.com/labstack/echo/issues/295]




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)