[VOTE] Graduate Apache DistributedLog as a subproject of Apache BookKeeper

[Flavio Junqueira]

The Apache DistributedLog community has voted to graduate the project and make 
it a subproject of Apache BookKeeper. The Apache BookKeeper PMC has also voted 
to accept DistributedLog as a subproject. The links to the vote threads are the 
following:

DistributedLog PPMC vote:
https://mail-search.apache.org/members/private-arch/distributedlog-private/201706.mbox/%3ccao2ydyy3nzjtb934g-aryujswzjetktpupf_la0jkhf263f...@mail.gmail.com%3e
 

https://mail-search.apache.org/members/private-arch/distributedlog-private/201706.mbox/%3cCAO2yDybfqt72xGtrvR-9eUYycHJvpCo5=ts87rzhpsm096r...@mail.gmail.com%3e
 


DistributedLog Community vote:
http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3ccao2ydyzzinfghjxqmvehxdaulkwdt9v2nkqeyuzxe0i4tzg...@mail.gmail.com%3e
 

http://mail-archives.apache.org/mod_mbox/incubator-distributedlog-dev/201706.mbox/%3cCAO2yDya-=0cBfUM0SsL5kuf9HJ1G=pL7Z_=7Ps+TQgqwJs=c...@mail.gmail.com%3e
 


BookKeeper PMC vote:
https://mail-search.apache.org/members/private-arch/bookkeeper-private/201706.mbox/%3cCAO2yDyacdXuXh==iw1oqrriugoxhprp_htnofojot5rxmv6...@mail.gmail.com%3e
 

https://mail-search.apache.org/members/private-arch/bookkeeper-private/201706.mbox/%3cCAO2yDyYzV_7vVNg6Efyp3TPjddoYRyQx4rXvqP=W=c09qk2...@mail.gmail.com%3e
 


This message is to start an IPMC vote. Please vote on the following:

[ ] +1 Graduate Apache DistributedLog from the Incubator.
[ ] +0 No opinion
[ ] -1 Don't graduate Apache DistributedLog from the Incubator (please provide
the reason)

This VOTE will be opened for the next 72 hours.

-Flavio

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

[Flavio Junqueira]

Given that there has been no further feedback on the LICENSE/NOTICE point 
below, perhaps we should create a couple of issues to track them so that we can 
revisit before graduation? They should not block this release, but we need to 
do some due diligence there.

-Flavio

> On 24 Jan 2017, at 02:52, Sijie Guo  wrote:
> 
> Ping?
> 
> If there is no other strong objections here, I'd like to conclude the votes
> and proceed the remaining steps for the release.
> 
> - Sijie
> 
> On Fri, Jan 20, 2017 at 10:15 AM, Sijie Guo  wrote:
> 
>> 
>> 
>> On Fri, Jan 20, 2017 at 6:28 AM, Flavio Junqueira  wrote:
>> 
>>> 
>>>> On 19 Jan 2017, at 18:42, Sijie Guo  wrote:
>>>> 
>>>> Flavio,
>>>> 
>>>> 
>>>> 
>>>> On Wed, Jan 18, 2017 at 10:38 AM, Sijie Guo >> si...@apache.org>> wrote:
>>>> 
>>>> 
>>>> On Jan 18, 2017 10:37 AM, "Sijie Guo" >> si...@apache.org>> wrote:
>>>> 
>>>> 
>>>> On Jan 17, 2017 2:58 PM, "Flavio Junqueira" >> f...@apache.org>> wrote:
>>>> +1, I have checked the following:
>>>> 
>>>> - Built both 2.10 and 2.11 from source (skipped tests)
>>>> - Checksums and signatures
>>>> - NOTICE and LICENSE
>>>> - Rat
>>>> 
>>>> Questions:
>>>> 1- I'm wondering if the text about Hadoop in NOTICE is necessary. How
>>> did you guys end up including it?
>>>> 
>>>> Ah, I need to check that. Can't remember why it was brought in right
>>> now.
>>>> 
>>>> I think this because we ported one class from Hadoop
>>> "TestTimedOutTestsListener" - we used it for dump information when the
>>> tests timed out. do you see any concerns here? what is your suggestion?
>>> 
>>> I'm not particularly concerned, but I'm wondering if this is really
>>> needed in NOTICE, simply because the guidance we have from ASF is that we
>>> should change the NOTICE file only when strictly necessary. In particular,
>>> this part:
>>> 
>>> NOTICE is reserved for a certain subset of legally required notifications
>>> which are not satisfied by either the text of LICENSE or the presence of
>>> licensing information embedded within the bundled dependency. Aside from
>>> Apache-licensed dependencies which supply NOTICE files of their own, it is
>>> uncommon for a dependency to require additions to NOTICE.
>>> 
>>> says that such changes aren't necessary for Apache-licensed dependencies,
>>> but in this case, it is not really a dependency, you copied a file into
>>> your code, so I'm not sure. Perhaps one of the other mentors have some
>>> insight here.
>>> 
>> 
>> Henry, Chris,
>> 
>> Any thoughts about the NOTICE file here?
>> 
>> Liang,
>> 
>> Since you added the hadoop part in the NOTICE file, can you comment what
>> was your experiences about the NOTICE file here?
>> 
>> - Sijie
>> 
>> 
>>> 
>>>> 
>>>> commit ea3c1143f9e2718d0d86e8b1c8f3a7e51ac19c4d
>>>> Author: xieliang mailto:xieliang...@gmail.com>>
>>>> Date:   Wed Jan 4 16:09:01 2017 -0800
>>>> 
>>>>DL-165: Add TestTimedOutTestsListener to dump timed out cases
>>> thread dump
>>>> 
>>>>Author: xieliang >> xieliang...@gmail.com>>
>>>> 
>>>>Reviewers: Leigh Stewart >> lstew...@apache.org>>
>>>> 
>>>>Closes #91 from xieliang/DL-165-TimedOutTestsListene
>>>> 
>>>> 
>>>> 2- The tgz bundles do not include any jar directly, so there is no real
>>> concern about bundling the bits from other projects that could require more
>>> sections in the NOTICE file, is it right?
>>>> 
>>>> I am clear about this part. Any principles to follow in Apache?
>>>> 
>>>> Sorry typo => not clear about
>>>> 
>>>> Can you comment more on this part?
>>>> 
>>> 
>>> This comment is based on this:
>>> 
>>> LICENSE and NOTICE must always be tailored to the content of the specific
>>> distribution they reside within. Dependencies which are not included in the
>>> distribution MUST NOT be added to LICENSE and NOTICE. As far as LICENSE and
>>> NOTICE are concerned, only bundled bits matter.
>&g

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

[Flavio Junqueira]

> On 19 Jan 2017, at 18:42, Sijie Guo  wrote:
> 
> Flavio,
> 
> 
> 
> On Wed, Jan 18, 2017 at 10:38 AM, Sijie Guo  <mailto:si...@apache.org>> wrote:
> 
> 
> On Jan 18, 2017 10:37 AM, "Sijie Guo"  <mailto:si...@apache.org>> wrote:
> 
> 
> On Jan 17, 2017 2:58 PM, "Flavio Junqueira"  <mailto:f...@apache.org>> wrote:
> +1, I have checked the following:
> 
> - Built both 2.10 and 2.11 from source (skipped tests)
> - Checksums and signatures
> - NOTICE and LICENSE
> - Rat
> 
> Questions:
> 1- I'm wondering if the text about Hadoop in NOTICE is necessary. How did you 
> guys end up including it?
> 
> Ah, I need to check that. Can't remember why it was brought in right now.
> 
> I think this because we ported one class from Hadoop 
> "TestTimedOutTestsListener" - we used it for dump information when the tests 
> timed out. do you see any concerns here? what is your suggestion?

I'm not particularly concerned, but I'm wondering if this is really needed in 
NOTICE, simply because the guidance we have from ASF is that we should change 
the NOTICE file only when strictly necessary. In particular, this part:

NOTICE is reserved for a certain subset of legally required notifications which 
are not satisfied by either the text of LICENSE or the presence of licensing 
information embedded within the bundled dependency. Aside from Apache-licensed 
dependencies which supply NOTICE files of their own, it is uncommon for a 
dependency to require additions to NOTICE.

says that such changes aren't necessary for Apache-licensed dependencies, but 
in this case, it is not really a dependency, you copied a file into your code, 
so I'm not sure. Perhaps one of the other mentors have some insight here.
 
> 
> commit ea3c1143f9e2718d0d86e8b1c8f3a7e51ac19c4d
> Author: xieliang mailto:xieliang...@gmail.com>>
> Date:   Wed Jan 4 16:09:01 2017 -0800
> 
> DL-165: Add TestTimedOutTestsListener to dump timed out cases thread dump
> 
> Author: xieliang mailto:xieliang...@gmail.com>>
> 
> Reviewers: Leigh Stewart  <mailto:lstew...@apache.org>>
> 
> Closes #91 from xieliang/DL-165-TimedOutTestsListene 
> 
> 
> 2- The tgz bundles do not include any jar directly, so there is no real 
> concern about bundling the bits from other projects that could require more 
> sections in the NOTICE file, is it right?
> 
> I am clear about this part. Any principles to follow in Apache?
> 
> Sorry typo => not clear about 
> 
> Can you comment more on this part?
>  

This comment is based on this:

LICENSE and NOTICE must always be tailored to the content of the specific 
distribution they reside within. Dependencies which are not included in the 
distribution MUST NOT be added to LICENSE and NOTICE. As far as LICENSE and 
NOTICE are concerned, only bundled bits matter.

I didn't see anything specific that called my attention, and I'm doing due 
diligence and asking.

Both paragraphs I copied are from this page:

http://www.apache.org/dev/licensing-howto.html

-Flavio

> 
> 
> -Flavio
> 
> > On 17 Jan 2017, at 17:12, Leigh Stewart  
> > wrote:
> >
> > +1
> >
> > On Mon, Jan 16, 2017 at 8:13 AM, Jon Derrick  > <mailto:jonathan.derri...@gmail.com>>
> > wrote:
> >
> >> +1
> >>
> >> LGTM. compiled the source packages and ran dbench. the license files look
> >> good.
> >>
> >> - jd
> >>
> >> On Tue, Jan 10, 2017 at 11:56 PM, Sijie Guo  >> <mailto:si...@apache.org>> wrote:
> >>
> >>> Hi all,
> >>>
> >>> Please review and vote on the release candidate #2 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 <http://dist.apache.org/>
> >>> [2],
> >>>* all artifacts to be deployed to the Maven Central Repository
> >> [3][4],
> >>>* 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) [5][6],
> >>>* website pull request listing the release [7] and publishing the API
> >>> reference manual.
> >>>
> >>> A simple instruction for validation the source 

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

[Flavio Junqueira]

+1, I have checked the following:

- Built both 2.10 and 2.11 from source (skipped tests)
- Checksums and signatures
- NOTICE and LICENSE
- Rat

Questions:
1- I'm wondering if the text about Hadoop in NOTICE is necessary. How did you 
guys end up including it?
2- The tgz bundles do not include any jar directly, so there is no real concern 
about bundling the bits from other projects that could require more sections in 
the NOTICE file, is it right?

-Flavio

> On 17 Jan 2017, at 17:12, Leigh Stewart  wrote:
> 
> +1
> 
> On Mon, Jan 16, 2017 at 8:13 AM, Jon Derrick 
> wrote:
> 
>> +1
>> 
>> LGTM. compiled the source packages and ran dbench. the license files look
>> good.
>> 
>> - jd
>> 
>> On Tue, Jan 10, 2017 at 11:56 PM, Sijie Guo  wrote:
>> 
>>> Hi all,
>>> 
>>> Please review and vote on the release candidate #2 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-RC1_2.11" (for scala 2.11) and
>>> "v0.4.0-incubating-RC1_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?
>>> projectId=12320620&version=12337980
>>> [2]
>>> https://dist.apache.org/repos/dist/dev/incubator/distributedlog/0.4.0-
>>> incubating-RC2/
>>> [3]
>>> https://repository.apache.org/content/repositories/
>>> orgapachedistributedlog-1003/
>>> [4]
>>> https://repository.apache.org/content/repositories/
>>> orgapachedistributedlog-1004/
>>> [5]
>>> https://github.com/apache/incubator-distributedlog/tree/
>>> v0.4.0-incubating-RC1_2.11
>>> [6]
>>> https://github.com/apache/incubator-distributedlog/tree/
>>> v0.4.0-incubating-RC1_2.10
>>> [7] https://github.com/apache/incubator-distributedlog/pull/109
>>> 
>> 
>> 
>> 
>> --
>> - jderrick
>> 

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

[Flavio Junqueira]

You're saying my machine is slow... ;-)

-Flavio

> On 12 Jan 2017, at 16:38, Sijie Guo  wrote:
> 
> Yeah, currently some of the tests are time dependent. So they failed
> sometimes when the machine is slow. There were efforts on improving this
> and will also do this in next release.
> 
> Sijie
> 
> On Jan 12, 2017 3:32 AM, "Flavio Junqueira"  <mailto:f...@apache.org>> wrote:
> 
>> Ok, so I've seen the following test cases showing errors:
>> 
>> TestBKDistributedLogManager.testNumberOfTransactionsWithIn
>> progressAtEnd:325
>> TestAsyncReaderLock.testReaderLockDlmClosed » Cancellation
>> 
>> They don't seem to fail consistently for me, though.
>> 
>> -Flavio
>> 
>>> On 10 Jan 2017, at 18:10, Sijie Guo  wrote:
>>> 
>>> Liang had a pull request for the assembly issue. Going to cancel this
>> vote
>>> and produce a new RC.
>>> 
>>> Flavio, what are the tests failed in your case?
>>> 
>>> Sijie
>>> 
>>> On Jan 10, 2017 9:10 AM, "Flavio Junqueira" >> <mailto:f...@apache.org> > f...@apache.org <mailto:f...@apache.org>>> wrote:
>>> 
>>> Yeah, I can't build because of the same issue:
>>> 
>>>   [ERROR] Failed to execute goal org.apache.maven.plugins:
>>> maven-assembly-plugin:2.2.1:single (default) on project
>>> distributedlog-service: Failed to create assembly: Error adding file to
>>>   archive: distributedlog-0.4.0-incubating/distributedlog-
>> service/../README.md
>>> isn't a file. -> [Help 1]
>>> 
>>> The command I ran is:
>>> 
>>>  mvn clean apache-rat:check package findbugs:check -DskipTests
>>> 
>>> I also tried other commands, and they all seem to fail on tests.
>>> 
>>> -Flavio
>>> 
>>>> On 10 Jan 2017, at 07:24, Xi Liu >>> <mailto:xi.liu@gmail.com>> wrote:
>>>> 
>>>> On Mon, Jan 9, 2017 at 8:00 PM, liang xie >>> <mailto:xieliang...@gmail.com>
>> <mailto:xieliang...@gmail.com <mailto:xieliang...@gmail.com>> >> xieliang...@gmail.com>> wrote:
>>>> 
>>>>> Glad to see 0.4 will be release soon :)
>>>>> I could not find tutorials package from link[2], it should be released
>>>>> as well, please correct me if i am wrong.
>>>>> I can pass this command with current git master code: "mvn clean
>>>>> apache-rat:check package findbugs:check -DskipTests", but failed with
>>>>> from distributedlog-0.4.0-incubating-src.tar.gz which downloaded from
>>>>> dist.apache.org, the error msg:
>>>>> 
>>>>> [ERROR] Failed to execute goal
>>>>> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
>>>>> on project distributedlog-service: Failed to create assembly: Error
>>>>> adding file to archive:
>>>>> /tmp/distributedlog-0.4.0-incubating/distributedlog-
>> service/../README.md
>>>>> isn't a file. -> [Help 1]
>>>>> 
>>>> 
>>>> I also saw this issue.
>>>> 
>>>> 
>>>>> 
>>>>> And none of you saw this : DL-181, it can be reproduced on my local
>>>>> box always w/o patched,  weird...
>>>>> 
>>>>> 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&version=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 #1

[Flavio Junqueira]

Ok, so I've seen the following test cases showing errors:

TestBKDistributedLogManager.testNumberOfTransactionsWithInprogressAtEnd:325
TestAsyncReaderLock.testReaderLockDlmClosed » Cancellation

They don't seem to fail consistently for me, though.

-Flavio

> On 10 Jan 2017, at 18:10, Sijie Guo  wrote:
> 
> Liang had a pull request for the assembly issue. Going to cancel this vote
> and produce a new RC.
> 
> Flavio, what are the tests failed in your case?
> 
> Sijie
> 
> On Jan 10, 2017 9:10 AM, "Flavio Junqueira"  <mailto:f...@apache.org>> wrote:
> 
> Yeah, I can't build because of the same issue:
> 
>[ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-assembly-plugin:2.2.1:single (default) on project
> distributedlog-service: Failed to create assembly: Error adding file to
>archive: 
> distributedlog-0.4.0-incubating/distributedlog-service/../README.md
> isn't a file. -> [Help 1]
> 
> The command I ran is:
> 
>   mvn clean apache-rat:check package findbugs:check -DskipTests
> 
> I also tried other commands, and they all seem to fail on tests.
> 
> -Flavio
> 
>> On 10 Jan 2017, at 07:24, Xi Liu  wrote:
>> 
>> On Mon, Jan 9, 2017 at 8:00 PM, liang xie > <mailto:xieliang...@gmail.com>  xieliang...@gmail.com>> wrote:
>> 
>>> Glad to see 0.4 will be release soon :)
>>> I could not find tutorials package from link[2], it should be released
>>> as well, please correct me if i am wrong.
>>> I can pass this command with current git master code: "mvn clean
>>> apache-rat:check package findbugs:check -DskipTests", but failed with
>>> from distributedlog-0.4.0-incubating-src.tar.gz which downloaded from
>>> dist.apache.org, the error msg:
>>> 
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
>>> on project distributedlog-service: Failed to create assembly: Error
>>> adding file to archive:
>>> /tmp/distributedlog-0.4.0-incubating/distributedlog-service/../README.md
>>> isn't a file. -> [Help 1]
>>> 
>> 
>> I also saw this issue.
>> 
>> 
>>> 
>>> And none of you saw this : DL-181, it can be reproduced on my local
>>> box always w/o patched,  weird...
>>> 
>>> 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&version=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 #1

[Flavio Junqueira]

Yeah, I can't build because of the same issue:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default) on 
project distributedlog-service: Failed to create assembly: Error adding file to 
 
archive: 
distributedlog-0.4.0-incubating/distributedlog-service/../README.md isn't a 
file. -> [Help 1]

The command I ran is:

   mvn clean apache-rat:check package findbugs:check -DskipTests

I also tried other commands, and they all seem to fail on tests.

-Flavio

> On 10 Jan 2017, at 07:24, Xi Liu  wrote:
> 
> On Mon, Jan 9, 2017 at 8:00 PM, liang xie  > wrote:
> 
>> Glad to see 0.4 will be release soon :)
>> I could not find tutorials package from link[2], it should be released
>> as well, please correct me if i am wrong.
>> I can pass this command with current git master code: "mvn clean
>> apache-rat:check package findbugs:check -DskipTests", but failed with
>> from distributedlog-0.4.0-incubating-src.tar.gz which downloaded from
>> dist.apache.org, the error msg:
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
>> on project distributedlog-service: Failed to create assembly: Error
>> adding file to archive:
>> /tmp/distributedlog-0.4.0-incubating/distributedlog-service/../README.md
>> isn't a file. -> [Help 1]
>> 
> 
> I also saw this issue.
> 
> 
>> 
>> And none of you saw this : DL-181, it can be reproduced on my local
>> box always w/o patched,  weird...
>> 
>> 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&version=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: [discuss] Official Slack or Gitter channel for Distributedlog

[Flavio Junqueira]

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: [DISCUSSION] First Release

[Flavio Junqueira]

It does make sense, Sijie, thanks for the update.

-Flavio

> On 17 Nov 2016, at 05:12, Sijie Guo  wrote:
> 
> Flavio,
> 
> I totally agreed that not using an official Apache  version is not great
> for the community. We had a bookkeeper meetup last night. We've discussed
> the current situation with the community. We came to a commitment to merge
> Twitter's branch back into bookkeeper 4.5. After that we won't maintain our
> own branch and switch to 4.5.
> 
> Hope this make sense.
> 
> Sijie
> 
> On Nov 16, 2016 8:04 PM, "Flavio Junqueira"  wrote:
> 
> It isn't great that DistributedLog is not using the Apache BookKeeper
> release. Essentially anyone using DistributedLog today needs to use the
> Twitter branch of BookKeeper, which has diverged from Apache BookKeeper.
> I'm sure the changes in the Twitter branch are all great, but I'd be more
> comfortable being able to rely on the Apache BookKeeper releases, which are
> community driven.
> 
> I'm not going to block the release on this alone because it is important
> for this project to get a first release out soon, but we need to fix DL-2.
> 
> -Flavio
> 
>> On 15 Nov 2016, at 19:02, Leigh Stewart 
> wrote:
>> 
>> +1
>> 
>> On Tue, Nov 15, 2016 at 7:01 PM, Franck Cuny 
> wrote:
>> 
>>> +1 and I agree to not make DL-2 a blocker.
>>> 
>>> On Tue, Nov 15, 2016 at 2:02 AM, Xi Liu  wrote:
>>> 
>>>> +1 especially on DL-23.
>>>> 
>>>> - Xi
>>>> 
>>>> On Sat, Nov 12, 2016 at 2:22 AM, Khurrum Nasim 
>>>> wrote:
>>>> 
>>>>> +1 (non-binding)
>>>>> 
>>>>> I am also interested in participating.
>>>>> 
>>>>> - kn
>>>>> 
>>>>> On Tue, Nov 8, 2016 at 11:08 PM, Sijie Guo  wrote:
>>>>> 
>>>>>> I'd like to start the discussion about the first release. There are
>>>>> still a
>>>>>> few discussions and pull requests outstanding. I think we need to
>>> pick
>>>>> up a
>>>>>> few items and cut the first release and then iterate from there. Here
>>>> is
>>>>> a
>>>>>> list of items that I think we should include:
>>>>>> 
>>>>>> - DL-4 <https://issues.apache.org/jira/browse/DL-4>: Repackaging
>>>>> namespace
>>>>>> to org.apache (the pull request is out and under reviewing)
>>>>>> - DL-49 <https://issues.apache.org/jira/browse/DL-49>: support scala
>>>>> 2.10
>>>>>> and 2.11 (the review is done, need to be merged)
>>>>>> - DL-23 <https://issues.apache.org/jira/browse/DL-23>: Move DL to
>>>> depend
>>>>>> on
>>>>>> central maven repo. The main blocker is about the libthrift version,
>>>>> which
>>>>>> is only hosted at twtter's maven repo. There is a pull request out.
>>>>>> 
>>>>>> I am kind of thinking to not make DL-2
>>>>>> <https://issues.apache.org/jira/browse/DL-2> (using the official
>>>>>> bookkeeper
>>>>>> version) the blocker for the first release. We can cut a new release
>>>> once
>>>>>> that change is ready. So to decouple the release procedure between DL
>>>> and
>>>>>> BK.
>>>>>> 
>>>>>> Please feel free to add any jiras that you believe it should be
>>>> included
>>>>> in
>>>>>> the first release.
>>>>>> 
>>>>>> Also, is there anyone interested in being the release manager for
>>> first
>>>>>> release?
>>>>>> 
>>>>>> - Sijie
>>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> -franck
>>> 

Re: [DISCUSSION] First Release

[Flavio Junqueira]

It isn't great that DistributedLog is not using the Apache BookKeeper release. 
Essentially anyone using DistributedLog today needs to use the Twitter branch 
of BookKeeper, which has diverged from Apache BookKeeper. I'm sure the changes 
in the Twitter branch are all great, but I'd be more comfortable being able to 
rely on the Apache BookKeeper releases, which are community driven.

I'm not going to block the release on this alone because it is important for 
this project to get a first release out soon, but we need to fix DL-2.

-Flavio

> On 15 Nov 2016, at 19:02, Leigh Stewart  wrote:
> 
> +1
> 
> On Tue, Nov 15, 2016 at 7:01 PM, Franck Cuny  wrote:
> 
>> +1 and I agree to not make DL-2 a blocker.
>> 
>> On Tue, Nov 15, 2016 at 2:02 AM, Xi Liu  wrote:
>> 
>>> +1 especially on DL-23.
>>> 
>>> - Xi
>>> 
>>> On Sat, Nov 12, 2016 at 2:22 AM, Khurrum Nasim 
>>> wrote:
>>> 
 +1 (non-binding)
 
 I am also interested in participating.
 
 - kn
 
 On Tue, Nov 8, 2016 at 11:08 PM, Sijie Guo  wrote:
 
> I'd like to start the discussion about the first release. There are
 still a
> few discussions and pull requests outstanding. I think we need to
>> pick
 up a
> few items and cut the first release and then iterate from there. Here
>>> is
 a
> list of items that I think we should include:
> 
> - DL-4 : Repackaging
 namespace
> to org.apache (the pull request is out and under reviewing)
> - DL-49 : support scala
 2.10
> and 2.11 (the review is done, need to be merged)
> - DL-23 : Move DL to
>>> depend
> on
> central maven repo. The main blocker is about the libthrift version,
 which
> is only hosted at twtter's maven repo. There is a pull request out.
> 
> I am kind of thinking to not make DL-2
>  (using the official
> bookkeeper
> version) the blocker for the first release. We can cut a new release
>>> once
> that change is ready. So to decouple the release procedure between DL
>>> and
> BK.
> 
> Please feel free to add any jiras that you believe it should be
>>> included
 in
> the first release.
> 
> Also, is there anyone interested in being the release manager for
>> first
> release?
> 
> - Sijie
> 
 
>>> 
>> 
>> 
>> 
>> --
>> -franck
>> 

Re: Distributedlog Podling Report Draft - November 2016

[Flavio Junqueira]

+1

> On 02 Nov 2016, at 09:22, Khurrum Nasim  wrote:
> 
> +1 from me (non-binding).
> 
> - KN
> 
> On Tue, Nov 1, 2016 at 7:18 PM, Jia Zhai  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  wrote:
>> 
>>> Thank you Jia and Flavio. Comments inline.
>>> 
>>> On Tue, Nov 1, 2016 at 1:54 AM, Jia Zhai  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  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  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
>>>> outsid

Re: Distributedlog Podling Report Draft - November 2016

[Flavio Junqueira]

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  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  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  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,  wrote:
>>> 
>> 

Re: hundreds of millions of streams?

[Flavio Junqueira]

Perhaps this is an obvious observation, but can't you deploy multiple instances 
to scale to whatever size you like?

-Flavio

> On 28 Oct 2016, at 20:27, Poule Dodue  wrote:
> 
> I think it would cause more concurrency problems in write operations as
> described at page 12 point #2 of this thesis:
> 
> http://www.diva-portal.se/smash/get/diva2:877307/FULLTEXT01.pdf
> 
> 
> 
>> Le 28 oct. 2016 à 11:48, Leigh Stewart  a 
>> écrit :
>> 
>> Got it. We probably can't support that scale at this time.
>> Curious: do you resort to sharing streams among objects with systems that
>> don't support 100s millions of streams? (i.e. partitioning objects across
>> streams?)
>> 
>> On Fri, Oct 28, 2016 at 8:24 AM, Poule Dodue  wrote:
>> 
>>> yes aka ES/CQRS
>>> 
>>> some links:
>>> 
>>> https://msdn.microsoft.com/en-us/library/jj554200.aspx
>>> http://williamverdolini.github.io/2014/08/11/cqrses-architecture/
>>> http://docs.geteventstore.com/introduction/3.9.0/event-sourcing-basics/
>>> 
>>> it needs lot of streams to basically replay events for any entity on a
>>> system.
>>> 
>>> example: i could replay events for all changes that happened in 1 Cart of
>>> 1 User:
>>> 
>>> 
>>> (read events from stream "cart-of-user-233293111" ):
>>> 
>>> 1- added item X
>>> 2- deleted item X
>>> 3- added item Y
>>> 
>>> 
>>> by replaying that stream, I can rebuild a user's cart state
>>> 
>>> 
 Le 28 oct. 2016 à 10:13, Leigh Stewart  a
>>> écrit :
 
 Poule- would you mind sharing some information on Event Sourcing? Are you
 referring to something like
 http://martinfowler.com/eaaDev/EventSourcing.html ?
 
 On Fri, Oct 28, 2016 at 7:11 AM, Leigh Stewart 
>>> wrote:
 
> DL is not able to handle 100s of millions of streams. 10^5-106 is
>>> probably
> ok.
> ZK is probably the biggest challenge (we are looking at ways to
>>> eliminate
> this as we would like to scale to 10^6-10^7 in the not too distant
>>> future),
> but 100s of millions is so far beyond what we've worked with there would
> likely be other scaling challenges on the way to that point.
> 
> On Fri, Oct 28, 2016 at 5:56 AM, Poule Dodue 
> wrote:
> 
>> In Event Sourcing, we need to have 1 stream per entity/aggregate so for
>> a typical prod system it means we need hundreds of millions of streams.
>> 
>> Is DL able to handle that or it is limited to, say, few hundreds
>> thousands of streams?
>> 
>> 
>> 
> 
>>> 
>>> 
> 

Re: Podling Report Reminder - November 2016

[Flavio Junqueira]

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  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,  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
>> 

Re: [DRAFT] Podling report for September 2016

[Flavio Junqueira]

I have signed off even though it hasn't been updated. Let's leave the 
improvements to the next report.

-Flavio

> On 13 Sep 2016, at 02:29, Sijie Guo  wrote:
> 
> Gotcha. I will improve the report tonight.
> 
> - Sijie
> 
> On Mon, Sep 12, 2016 at 2:35 AM, Flavio Junqueira  wrote:
> 
>> I'd actually prefer to add this information for the current one, we still
>> have time. Even if we don't add it all, some clarification with respect to
>> the contributions would be great.
>> 
>> -Flavio
>> 
>>> On 10 Sep 2016, at 20:20, Sijie Guo  wrote:
>>> 
>>> Yup. +1 on Flavio's suggestion. We should start report these things on
>> next
>>> report.
>>> 
>>> - Sijie
>>> 
>>> On Fri, Sep 9, 2016 at 2:21 PM, Flavio Junqueira  wrote:
>>> 
>>>> It looks good. It'd be nice to add some more detail, though. For
>> example:
>>>> 
>>>> - Number of jiras created
>>>> - Number of jiras resolved
>>>> - Jenkins has been set up
>>>> - Number of contributors reporting jira issues
>>>> - Can we quantify a "a few people contributing"? Is that 2-3 or more
>> like
>>>> 10?
>>>> - Can we quantify the ideas being proposed, like was it one or more?
>>>> 
>>>> It is not a big issue to not report these things early on, but I find it
>>>> good practice to do it even if the numbers aren't impressive at this
>> point
>>>> (it's a starting project after all). Having these figures will help
>> later
>>>> on to determine how the community has been growing.
>>>> 
>>>> -Flavio
>>>> 
>>>>> On 09 Sep 2016, at 16:20, Chris Nauroth 
>>>> wrote:
>>>>> 
>>>>> I entered my sign-off.  Nice job, Khurrum!
>>>>> 
>>>>> --Chris Nauroth
>>>>> 
>>>>> On 9/7/16, 11:59 PM, "Sijie Guo"  wrote:
>>>>> 
>>>>>  I submitted the podling report.
>>>>> 
>>>>>  Can any mentor take a look and sign off?
>>>>> 
>>>>>  - Sijie
>>>>> 
>>>>>  On Wed, Sep 7, 2016 at 10:17 PM, Khurrum Nasim <
>>>> khurrumnas...@gmail.com>
>>>>>  wrote:
>>>>> 
>>>>>> It seems that I have troubles with my account. Can anyone submit the
>>>>>> report?
>>>>>> 
>>>>>> KN
>>>>>> 
>>>>>> On Wed, Sep 7, 2016 at 9:26 PM, Khurrum Nasim <
>> khurrumnas...@gmail.com>
>>>>>> wrote:
>>>>>> 
>>>>>>> If no objection, I will update the wiki to submit the report.
>>>>>>> 
>>>>>>> KN
>>>>>>> 
>>>>>>> On Tue, Sep 6, 2016 at 11:43 PM, Khurrum Nasim <
>>>> khurrumnas...@gmail.com>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> Thank you Sijie. I've requested the wiki permission at the incubator
>>>>>> list.
>>>>>>>> 
>>>>>>>> - KN
>>>>>>>> 
>>>>>>>> On Tue, Sep 6, 2016 at 6:48 PM, Sijie Guo  wrote:
>>>>>>>> 
>>>>>>>>> LGTM +1
>>>>>>>>> 
>>>>>>>>> Btw you might need to request the permission to edit the incubator
>>>>>> wiki.
>>>>>>>>> You can send an email to general@i.a.o to ask for the permission.
>>>>>>>>> 
>>>>>>>>> Sijie
>>>>>>>>> 
>>>>>>>>> On Tuesday, September 6, 2016, Khurrum Nasim <
>>>> khurrumnas...@gmail.com>
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> DistributedLog
>>>>>>>>>> 
>>>>>>>>>> DistributedLog (DL) is a high-performance, replicated log service,
>>>>>>>>> offering
>>>>>>>>>> durability, replication and strong consistency as essentials for
>>>>>>>>> building
>>>>>>>>>> reliable distributed systems.
>>>>>>>>>> 
>>>>>>>>>> Three most important issues to address in the move towards
>>>>>> graduation:
>>>>>>>>>> * Getting an Apache release out
>>>>>>>>>> * Improve general documentation
>>>>>>>>>> * Grow user base
>>>>>>>>>> 
>>>>>>>>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
>>>> be
>>>>>>>>> aware
>>>>>>>>>> of?
>>>>>>>>>> There is currently no issue.
>>>>>>>>>> 
>>>>>>>>>> How has the community developed since the last report?
>>>>>>>>>> * A few people began actively to involve in the project discussion
>>>>>>>>>> * Some project ideas have been initiated and discussed on the
>>>> mailing
>>>>>>>>> list
>>>>>>>>>> 
>>>>>>>>>> How has the project developed since the last report?
>>>>>>>>>> * The wiki has been filled up with development and contribution
>>>>>>>>>> information.
>>>>>>>>>> * The existing website content has been pushed to asf-site branch
>>>> and
>>>>>>>>> live
>>>>>>>>>> under http://distributedlog.incubator.apache.org. The new website
>>>>>> has
>>>>>>>>> been
>>>>>>>>>> discussed.
>>>>>>>>>> * The pom file was updated to follow Apache's principle and the
>>>>>> status
>>>>>>>>> page
>>>>>>>>>> is updated.
>>>>>>>>>> * Various project ideas are under developing.
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> - KN
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>> 
>> 

Re: Repackaging the package namespace

[Flavio Junqueira]

It isn't strictly necessary, here is what the documentation says:

On Repackaging

It is recommended - but not mandated - that source is repackaged under the 
Apache namespace. There is no need to use the incubator namespace. For example, 
Java source might be repackaged to org.apache.foo.Bar or a DTD to 
http://dtd.apache.org/foo/bar.

Existing open source projects moving to Apache may well need to consider 
carefully how they will approach this transition.



My suggestion is to repackage before the first release, though. This way 
applications written against the early release will have the right namespace 
already. 

-Flavio

> On 10 Sep 2016, at 20:32, Sijie Guo  wrote:
> 
> Any suggestions from mentors for the first release?
> 
> - Sijie
> 
> On Tue, Aug 30, 2016 at 11:18 PM, Sijie Guo  wrote:
> 
>> Does anyone know if it is required to repackage the namespace to under
>> org.apache for the first release? Any suggestions from mentors?
>> 
>> - Sijie
>> 

Re: [DRAFT] Podling report for September 2016

[Flavio Junqueira]

I'd actually prefer to add this information for the current one, we still have 
time. Even if we don't add it all, some clarification with respect to the 
contributions would be great.

-Flavio

> On 10 Sep 2016, at 20:20, Sijie Guo  wrote:
> 
> Yup. +1 on Flavio's suggestion. We should start report these things on next
> report.
> 
> - Sijie
> 
> On Fri, Sep 9, 2016 at 2:21 PM, Flavio Junqueira  wrote:
> 
>> It looks good. It'd be nice to add some more detail, though. For example:
>> 
>> - Number of jiras created
>> - Number of jiras resolved
>> - Jenkins has been set up
>> - Number of contributors reporting jira issues
>> - Can we quantify a "a few people contributing"? Is that 2-3 or more like
>> 10?
>> - Can we quantify the ideas being proposed, like was it one or more?
>> 
>> It is not a big issue to not report these things early on, but I find it
>> good practice to do it even if the numbers aren't impressive at this point
>> (it's a starting project after all). Having these figures will help later
>> on to determine how the community has been growing.
>> 
>> -Flavio
>> 
>>> On 09 Sep 2016, at 16:20, Chris Nauroth 
>> wrote:
>>> 
>>> I entered my sign-off.  Nice job, Khurrum!
>>> 
>>> --Chris Nauroth
>>> 
>>> On 9/7/16, 11:59 PM, "Sijie Guo"  wrote:
>>> 
>>>   I submitted the podling report.
>>> 
>>>   Can any mentor take a look and sign off?
>>> 
>>>   - Sijie
>>> 
>>>   On Wed, Sep 7, 2016 at 10:17 PM, Khurrum Nasim <
>> khurrumnas...@gmail.com>
>>>   wrote:
>>> 
>>>> It seems that I have troubles with my account. Can anyone submit the
>>>> report?
>>>> 
>>>> KN
>>>> 
>>>> On Wed, Sep 7, 2016 at 9:26 PM, Khurrum Nasim 
>>>> wrote:
>>>> 
>>>>> If no objection, I will update the wiki to submit the report.
>>>>> 
>>>>> KN
>>>>> 
>>>>> On Tue, Sep 6, 2016 at 11:43 PM, Khurrum Nasim <
>> khurrumnas...@gmail.com>
>>>>> wrote:
>>>>> 
>>>>>> Thank you Sijie. I've requested the wiki permission at the incubator
>>>> list.
>>>>>> 
>>>>>> - KN
>>>>>> 
>>>>>> On Tue, Sep 6, 2016 at 6:48 PM, Sijie Guo  wrote:
>>>>>> 
>>>>>>> LGTM +1
>>>>>>> 
>>>>>>> Btw you might need to request the permission to edit the incubator
>>>> wiki.
>>>>>>> You can send an email to general@i.a.o to ask for the permission.
>>>>>>> 
>>>>>>> Sijie
>>>>>>> 
>>>>>>> On Tuesday, September 6, 2016, Khurrum Nasim <
>> khurrumnas...@gmail.com>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> DistributedLog
>>>>>>>> 
>>>>>>>> DistributedLog (DL) is a high-performance, replicated log service,
>>>>>>> offering
>>>>>>>> durability, replication and strong consistency as essentials for
>>>>>>> building
>>>>>>>> reliable distributed systems.
>>>>>>>> 
>>>>>>>> Three most important issues to address in the move towards
>>>> graduation:
>>>>>>>> * Getting an Apache release out
>>>>>>>> * Improve general documentation
>>>>>>>> * Grow user base
>>>>>>>> 
>>>>>>>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
>> be
>>>>>>> aware
>>>>>>>> of?
>>>>>>>> There is currently no issue.
>>>>>>>> 
>>>>>>>> How has the community developed since the last report?
>>>>>>>> * A few people began actively to involve in the project discussion
>>>>>>>> * Some project ideas have been initiated and discussed on the
>> mailing
>>>>>>> list
>>>>>>>> 
>>>>>>>> How has the project developed since the last report?
>>>>>>>> * The wiki has been filled up with development and contribution
>>>>>>>> information.
>>>>>>>> * The existing website content has been pushed to asf-site branch
>> and
>>>>>>> live
>>>>>>>> under http://distributedlog.incubator.apache.org. The new website
>>>> has
>>>>>>> been
>>>>>>>> discussed.
>>>>>>>> * The pom file was updated to follow Apache's principle and the
>>>> status
>>>>>>> page
>>>>>>>> is updated.
>>>>>>>> * Various project ideas are under developing.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> - KN
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>> 
>> 

Re: [DRAFT] Podling report for September 2016

[Flavio Junqueira]

It looks good. It'd be nice to add some more detail, though. For example:

- Number of jiras created
- Number of jiras resolved
- Jenkins has been set up
- Number of contributors reporting jira issues
- Can we quantify a "a few people contributing"? Is that 2-3 or more like 10?
- Can we quantify the ideas being proposed, like was it one or more?

It is not a big issue to not report these things early on, but I find it good 
practice to do it even if the numbers aren't impressive at this point (it's a 
starting project after all). Having these figures will help later on to 
determine how the community has been growing.

-Flavio

> On 09 Sep 2016, at 16:20, Chris Nauroth  wrote:
> 
> I entered my sign-off.  Nice job, Khurrum!
> 
> --Chris Nauroth
> 
> On 9/7/16, 11:59 PM, "Sijie Guo"  wrote:
> 
>I submitted the podling report.
> 
>Can any mentor take a look and sign off?
> 
>- Sijie
> 
>On Wed, Sep 7, 2016 at 10:17 PM, Khurrum Nasim 
>wrote:
> 
>> It seems that I have troubles with my account. Can anyone submit the
>> report?
>> 
>> KN
>> 
>> On Wed, Sep 7, 2016 at 9:26 PM, Khurrum Nasim 
>> wrote:
>> 
>>> If no objection, I will update the wiki to submit the report.
>>> 
>>> KN
>>> 
>>> On Tue, Sep 6, 2016 at 11:43 PM, Khurrum Nasim 
>>> wrote:
>>> 
 Thank you Sijie. I've requested the wiki permission at the incubator
>> list.
 
 - KN
 
 On Tue, Sep 6, 2016 at 6:48 PM, Sijie Guo  wrote:
 
> LGTM +1
> 
> Btw you might need to request the permission to edit the incubator
>> wiki.
> You can send an email to general@i.a.o to ask for the permission.
> 
> Sijie
> 
> On Tuesday, September 6, 2016, Khurrum Nasim 
> wrote:
> 
>> DistributedLog
>> 
>> DistributedLog (DL) is a high-performance, replicated log service,
> offering
>> durability, replication and strong consistency as essentials for
> building
>> reliable distributed systems.
>> 
>> Three most important issues to address in the move towards
>> graduation:
>> * Getting an Apache release out
>> * Improve general documentation
>> * Grow user base
>> 
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware
>> of?
>> There is currently no issue.
>> 
>> How has the community developed since the last report?
>> * A few people began actively to involve in the project discussion
>> * Some project ideas have been initiated and discussed on the mailing
> list
>> 
>> How has the project developed since the last report?
>> * The wiki has been filled up with development and contribution
>> information.
>> * The existing website content has been pushed to asf-site branch and
> live
>> under http://distributedlog.incubator.apache.org. The new website
>> has
> been
>> discussed.
>> * The pom file was updated to follow Apache's principle and the
>> status
> page
>> is updated.
>> * Various project ideas are under developing.
>> 
>> 
>> - KN
>> 
> 
 
 
>>> 
>> 
> 
> 

Re: [DRAFT] Podling report for September 2016

[Flavio Junqueira]

Will do.

-Flavio

> On 08 Sep 2016, at 07:59, Sijie Guo  wrote:
> 
> I submitted the podling report.
> 
> Can any mentor take a look and sign off?
> 
> - Sijie
> 
> On Wed, Sep 7, 2016 at 10:17 PM, Khurrum Nasim 
> wrote:
> 
>> It seems that I have troubles with my account. Can anyone submit the
>> report?
>> 
>> KN
>> 
>> On Wed, Sep 7, 2016 at 9:26 PM, Khurrum Nasim 
>> wrote:
>> 
>>> If no objection, I will update the wiki to submit the report.
>>> 
>>> KN
>>> 
>>> On Tue, Sep 6, 2016 at 11:43 PM, Khurrum Nasim 
>>> wrote:
>>> 
 Thank you Sijie. I've requested the wiki permission at the incubator
>> list.
 
 - KN
 
 On Tue, Sep 6, 2016 at 6:48 PM, Sijie Guo  wrote:
 
> LGTM +1
> 
> Btw you might need to request the permission to edit the incubator
>> wiki.
> You can send an email to general@i.a.o to ask for the permission.
> 
> Sijie
> 
> On Tuesday, September 6, 2016, Khurrum Nasim 
> wrote:
> 
>> DistributedLog
>> 
>> DistributedLog (DL) is a high-performance, replicated log service,
> offering
>> durability, replication and strong consistency as essentials for
> building
>> reliable distributed systems.
>> 
>> Three most important issues to address in the move towards
>> graduation:
>> * Getting an Apache release out
>> * Improve general documentation
>> * Grow user base
>> 
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware
>> of?
>> There is currently no issue.
>> 
>> How has the community developed since the last report?
>> * A few people began actively to involve in the project discussion
>> * Some project ideas have been initiated and discussed on the mailing
> list
>> 
>> How has the project developed since the last report?
>> * The wiki has been filled up with development and contribution
>> information.
>> * The existing website content has been pushed to asf-site branch and
> live
>> under http://distributedlog.incubator.apache.org. The new website
>> has
> been
>> discussed.
>> * The pom file was updated to follow Apache's principle and the
>> status
> page
>> is updated.
>> * Various project ideas are under developing.
>> 
>> 
>> - KN
>> 
> 
 
 
>>> 
>> 

First release?

[Flavio Junqueira]

No pressure, really, but I was wondering what the plan for the first release 
is. Better to do a first release sooner than later. You already have a working 
system so it is mostly about sorting out any issues related to releasing in 
Apache.

-Flavio

Re: [draft] Podling report for August 2016

[Flavio Junqueira]

I've also signed off on the wiki. Thanks, Franck!

-Flavio

> On 04 Aug 2016, at 01:01, Franck Cuny  wrote:
> 
> Good point, thanks Chris. I've moved it to the correct location in the wiki.
> 
> On Wed, Aug 3, 2016 at 4:47 PM, Chris Nauroth 
> wrote:
> 
>> +1.  I have entered my mentor sign-off.
>> 
>> It looks like the report wiki page now has 2 sections for DistributedLog:
>> one in alphabetical order, which is still the uncompleted template, and
>> another at the bottom of the page.  Could you please move the full report
>> into place alphabetically?  I’m not sure if the alphabetical sorting is
>> significant, but I’d prefer to avoid any potential confusion.
>> 
>> --Chris Nauroth
>> 
>> On 8/3/16, 4:10 PM, "Franck Cuny"  wrote:
>> 
>>The wiki page [1] has been updated for our report.
>> 
>>[1] https://wiki.apache.org/incubator/August2016
>> 
>>On Wed, Aug 3, 2016 at 9:02 AM, Chris Nauroth <
>> cnaur...@hortonworks.com>
>>wrote:
>> 
>>> Hello Franck,
>>> 
>>> Yes, please send an email to gene...@incubator.apache.org.  Mention
>> your
>>> username and ask for permissions to edit the wiki for a podling
>> report.
>>> 
>>> --Chris Nauroth
>>> 
>>> On 8/3/16, 8:58 AM, "Franck Cuny"  wrote:
>>> 
>>>Sijie, Chris,
>>> 
>>>I do not believe I have the authorization to edit that page. My
>>> username is
>>>'Franck Cuny'. Should I request access somewhere ?
>>> 
>>>Thanks
>>> 
>>>On Tue, Aug 2, 2016 at 10:35 PM, Chris Nauroth <
>>> cnaur...@hortonworks.com>
>>>wrote:
>>> 
>>>> +1.  Thank you, Franck.
>>>> 
>>>> Please let us know when wiki is updated, and I’ll apply my
>> mentor
>>> sign-off.
>>>> 
>>>> --Chris Nauroth
>>>> 
>>>> On 8/2/16, 10:22 PM, "Sijie Guo"  wrote:
>>>> 
>>>>LGTM +1
>>>> 
>>>>- Sijie
>>>> 
>>>>On Tue, Aug 2, 2016 at 5:17 PM, Franck Cuny <
>>> franck.c...@gmail.com>
>>>> wrote:
>>>> 
>>>>> Here's an updated version, if it's OK with every one,
>> I'll
>>> update
>>>> the wiki.
>>>>> 
>>>>> Thanks
>>>>> 
>>>>> ---
>>>>> 
>>>>> DistributedLog
>>>>> 
>>>>> DistributedLog (DL) is a high-performance, replicated log
>>> service,
>>>> offering
>>>>> durability, replication and strong consistency as
>> essentials
>>> for
>>>> building
>>>>> reliable distributed systems.
>>>>> 
>>>>> Three most important issues to address in the move
>> towards
>>>> graduation:
>>>>> * Getting an Apache release out
>>>>> * Improve general documentation
>>>>> * Grow user base
>>>>> 
>>>>> Any issues that the Incubator PMC (IPMC) or ASF Board
>>> wish/need to
>>>> be aware
>>>>> of?
>>>>> There is currently no issue.
>>>>> 
>>>>> How has the community developed since the last report?
>>>>> * A few people have started to report issues
>>>>> * Some conversations have been initiated on the mailing
>> list
>>>>> * Sijie will be present at Strata in China to present the
>>> project
>>>>> 
>>>>> How has the project developed since the last report?
>>>>> * The wiki has been set up (
>>> cwiki.apache.org/confluence/display/DL/)
>>>>> * A few contributions were made to the repository on
>> GitHub
>>> and are
>>>> in the
>>>>> process of being merged
>>>>> * Various mailing lists have been set up
>>>>> * SGA from Twitter has been completed
>>>>> * Status page is up and we have started filling it out
>>>>> * Most accounts of initial committers have been created
>>>>> * Jira queue has been created (
>>>> https://issues.apache.org/jira/browse/DL)
>>>>> * Repository has been created (and mirrored on GitHub)
>>>>> * Existing issues have been migrated from the old GitHub
>>> repository
>>>> to JIRA
>>>>> 
>>

Re: [draft] Podling report for August 2016

[Flavio Junqueira]

Thanks for putting this together, Franck. A few things that might be worth 
adding:

- Status page is up and we have started filling it out
- Most accounts of initial committers have been created
- Jira queue has been created
- Repository has been created

-Flavio

> On 28 Jul 2016, at 19:19, Chris Nauroth  wrote:
> 
> Hello Franck,
> 
> Thank you for writing the draft.  This looks good to me.  My only 
> recommendation is to add one more bullet point under project development to 
> state that the SGA from Twitter has been completed.
> 
> --Chris Nauroth
> 
> On 7/28/16, 11:12 AM, "Franck Cuny"  wrote:
> 
>Here's a draft of the report. Please review and comment, and I'll update
>the incubator wiki page in the next couple of days.
> 
>Thanks
> 
>---
> 
>DistributedLog
> 
>DistributedLog (DL) is a high-performance, replicated log service, offering
>durability, replication and strong consistency as essentials for building
>reliable distributed systems.
> 
>Three most important issues to address in the move towards graduation:
>* Getting an Apache release out
>* Improve general documentation
>* Grow user base
> 
>Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
>of?
>There is currently no issue.
> 
>How has the community developed since the last report?
>* A few people have started to report issues
> 
>How has the project developed since the last report?
>* The wiki has been set up
>* Existing issues have been migrated from the old GitHub repository to JIRA
>* A few contributions were made to the repository on GitHub and are in the
>process of being merged
>* Various mailing lists have been set up
> 
> 

Committers

[Flavio Junqueira]

Have all committers submitted an ICLA and subscribed to this list?

-Flavio

DL Jira

[Flavio Junqueira]

Jira is set up and I have added Sijie, Henry, and Chris as administrators.

-Flavio

Re: Board Report?

[Flavio Junqueira]

Sounds good, thank you, John.

-Flavio

> On 11 Jul 2016, at 07:16, Sijie Guo  wrote:
> 
> Thank you John!
> 
> Sijie
> 
> On Monday, July 11, 2016, John D. Ament  <mailto:johndam...@apache.org>> wrote:
> Hi Flavio,
> 
> At this point I'd recommend that you guys wait.  Reports were due last 
> Wednesday, we usually give a little bit of buffer.  At this point, all sign 
> offs should have happened so you'll be really late.  Its no big deal, don't 
> look at it as a bad mark.
> 
> I'll move the podling over this evening.
> 
> John
> 
> On Mon, Jul 11, 2016 at 5:14 AM Flavio Junqueira  > wrote:
> Hi John,
> 
> It looks like folks want to submit the report this month, Sijie copied here 
> is working on one and will update it.
> 
> -Flavio
> 
> > On 10 Jul 2016, at 16:46, Flavio Junqueira  > > wrote:
> >
> > Twitter is still working on the SGA, so moving to group 2 sounds like a 
> > good option.
> >
> > -Flavio
> >
> >> On 09 Jul 2016, at 16:23, John D. Ament  >> > wrote:
> >>
> >> DistributedLog,
> >>
> >> Do you plan to submit a board report this month?  If not, I will move you
> >> to reporting group 2 and monthly August -> October instead of July.
> >>
> >> John
> >
> 

Re: Board Report?

[Flavio Junqueira]

Hi John,

It looks like folks want to submit the report this month, Sijie copied here is 
working on one and will update it.

-Flavio

> On 10 Jul 2016, at 16:46, Flavio Junqueira  wrote:
> 
> Twitter is still working on the SGA, so moving to group 2 sounds like a good 
> option.
> 
> -Flavio
> 
>> On 09 Jul 2016, at 16:23, John D. Ament  wrote:
>> 
>> DistributedLog,
>> 
>> Do you plan to submit a board report this month?  If not, I will move you
>> to reporting group 2 and monthly August -> October instead of July.
>> 
>> John
> 

Re: [DRAFT] DistributedLog Report

[Flavio Junqueira]

That's fine for me, the formatting is a bit broken, though.

-Flavio

> On 11 Jul 2016, at 07:21, Sijie Guo  wrote:
> 
> Hello all,
> 
> Below is the draft of incubator report for DistributedLog. Let me know
> if it looks good.
> 
> 
> ---
> 
> DistributedLogDistributedLog is a high-performance replicated log
> service. It offersdurability, replication and strong consistency,
> which provides a fundamentalbuilding 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. Establish the project at the ASF, including moving
> code, wiki, website and such.
>  2. Make initial Apache branded release and release on a regular schedule.
>  3. Attract more contributions. Reach a bigger community.  Any issues
> that the Incubator PMC (IPMC) or ASF Board wish/need to beaware of?
> 
> None How has the community developed since the last report?
> We just setup the dev mail list. We will start development discussions
> in the mail list.How has the project developed since the last report?
> 
> We setup the mail lists, and are moving the repo from GitHub to apache
> but waiting for Twitter's SGA. Date of last release:
> N/AWhen were the last committers or PMC members elected?
> N/ASigned-off-by:  [ ](distributedlog) Flavio Junqueira  [
> ](distributedlog) Chris Nauroth  [ ](distributedlog) Henry
> SaputraShepherd/Mentor notes:
> 
> - Sijie

Re: Incubator report for July

[Flavio Junqueira]

I hadn't seen this message before I responded to John about moving to group 2. 
I'm fine either way, we can report that we have the mailing lists created and 
we are waiting on the SGA. I don't think we can say anything else, but if you 
feel that's enough, Henry, let's respond to John to say that we will stick to 
the current group.

Btw, I'll be traveling tomorrow, so I won't be very responsive for the next 
couple of days. If you guys can sort out the report issue, I'd appreciate. I 
think Chris is also not available.

-Flavio


> On 09 Jul 2016, at 22:45, Henry Saputra  wrote:
> 
> Hi All,
> 
> Any volunteer to write report for July [1]?
> 
> It is overdue but I think we could still make it.
> 
> - Henry
> 
> [1] https://wiki.apache.org/incubator/July2016

Re: Board Report?

[Flavio Junqueira]

Twitter is still working on the SGA, so moving to group 2 sounds like a good 
option.

-Flavio

> On 09 Jul 2016, at 16:23, John D. Ament  wrote:
> 
> DistributedLog,
> 
> Do you plan to submit a board report this month?  If not, I will move you
> to reporting group 2 and monthly August -> October instead of July.
> 
> John