[jira] [Created] (ZOOKEEPER-3584) "NoAuth" error message is ambiguous

[Lars Francke (Jira)]

Lars Francke created ZOOKEEPER-3584:
---

 Summary: "NoAuth" error message is ambiguous
 Key: ZOOKEEPER-3584
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3584
 Project: ZooKeeper
  Issue Type: Improvement
Affects Versions: 3.5.6
Reporter: Lars Francke
Assignee: Lars Francke


Currently we get a NoAuthException printed as "NoAuth"

 

Unfortunately "Auth" could mean "Authentication" or "Authorization" so I 
propose to change the error message to "Not authenticated"

I won't change the NoAuthException class name.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Apache Zookeeper - Export Commodity Control Classification (ECCN) Needed

[Lars Francke]

Owen O'Malley just did this for ORC and is proposing to do the same for
Hive. I'll reach out to him and will see if he can help out as he should be
familiar with the process.

On Mon, Jun 17, 2019 at 3:49 PM Flavio Junqueira  wrote:

> As we are not developing any cryptography code, we are only consumers, I
> understand that we should be classified as ECCN 5D002 as most of the
> software on the page Pat shared. Is there a document somewhere listing the
> dependencies we use for security?
>
> -Flavio
>
> > On 16 Jun 2019, at 07:19, Enrico Olivelli  wrote:
> >
> > Il sab 15 giu 2019, 18:40 Patrick Hunt  ha scritto:
> >
> >> I don't believe we've updated it to include ZK, seems we need to go
> through
> >> this process:
> >> http://www.apache.org/dev/crypto.html
> >>
> >> I haven't been involved with this before - anyone have experience with
> >> this, perhaps on another ASF project?
> >>
> >
> >
> > I don't. Sorry
> >
> > Enrico
> >
> >
> >> Patrick
> >>
> >>
> >> On Wed, Jun 12, 2019 at 7:01 AM DANOS, Bertrand <
> bertrand.da...@airbus.com
> >>>
> >> wrote:
> >>
> >>> Dear team,
> >>>
> >>> I've check the page http://www.apache.org/licenses/exports/ however
> the
> >>> "Apache Zookeeper" project is not referenced on it.
> >>> Can you report me which is the ECCN number associated to Zookeeper
> >> project?
> >>>
> >>> Thanks in advance
> >>>
> >>> Regards
> >>>
> >>> Bertrand Danos
> >>>
> >>>
> >>>
> >>> This document, technology or software does not contain French national
> >>> dual-use or military controlled data nor US national dual-use or
> military
> >>> controlled data.
> >>>
> >>> The information in this e-mail is confidential. The contents may not be
> >>> disclosed or used by anyone other than the addressee. Access to this
> >> e-mail
> >>> by anyone else is unauthorised.
> >>> If you are not the intended recipient, please notify Airbus immediately
> >>> and delete this e-mail.
> >>> Airbus cannot accept any responsibility for the accuracy or
> completeness
> >>> of this e-mail as it has been sent over public networks. If you have
> any
> >>> concerns over the content of this message or its Accuracy or Integrity,
> >>> please contact Airbus immediately.
> >>> All outgoing e-mails from Airbus are checked using regularly updated
> >> virus
> >>> scanning software but you should take whatever measures you deem to be
> >>> appropriate to ensure that this message and any attachments are virus
> >> free.
> >>>
> >>
>
>

Re: [NOTICE] Change of mailing list behavior (soon)

[Lars Francke]

The issues@ mailing list has now also been activated.

On Thu, May 30, 2019 at 6:28 PM Andor Molnar 
wrote:

> Great stuff!
> Thanks Lars.
>
> Andor
>
>
>
> On Thu, May 30, 2019 at 6:05 PM Lars Francke 
> wrote:
>
> > GitHub notifications are now being sent to notifications@
> >
> > I've asked that the commits@ mailing list is left untouched.
> >
> > On Wed, May 29, 2019, 23:50 Lars Francke  wrote:
> >
> > > In the next few days Jira & Git notifications will stop being sent to
> > > dev@zookeeper.apache.org.
> > >
> > > Only the creation of new issues will still be announced on dev@.
> > >
> > > For everything else notifications will be sent to issues@ (for Jira
> > > related things) and notifications@ (for Git related things).
> > >
> > > If you're interested in these notiifcations please subscribe to these
> > > mailing lists by sending a mail to:
> > > issues-subscr...@zookeeper.apache.org
> > > notifications-subscr...@zookeeper.apache.org
> > >
> > > I'll update this thread when INFRA has made the necessary changes.
> > >
> > > Thank you!
> > >
> >
>

Re: Github & Jira notifications

[Lars Francke]

I already submitted a pull request yesterday. Only on mobile, don't have
the link right now.

On Thu, May 30, 2019, 18:32 Andor Molnar  wrote:

> Would somebody please update the Mailing Lists page on the website:
>
> https://zookeeper.apache.org/lists.html <
> https://zookeeper.apache.org/lists.html>
>
> Thanks,
> Andor
>
>
>
> > On 2019. May 23., at 16:24, Patrick Hunt  wrote:
> >
> > Nope.
> >
> > Regards,
> >
> > Patrick
> >
> > On Thu, May 23, 2019 at 1:35 AM Lars Francke 
> wrote:
> >
> >> Me neither. I'm happy to keep the vote open a bit longer, we're in no
> rush.
> >>
> >> Patrick, do you have anything to add?
> >>
> >> On Mon, May 20, 2019 at 1:15 PM Andor Molnar  wrote:
> >>
> >>> I’m not sure whether we have convinced Patrick entirely.
> >>> Before casting my vote, I’d be happy if we could reach consensus in the
> >>> community with this change, not just majority.
> >>>
> >>> Reason is that I rather feel it a nice-to-have improvement, not
> critical.
> >>>
> >>> Andor
> >>>
> >>>
> >>>
> >>>> On 2019. May 17., at 17:05, Flavio Junqueira  wrote:
> >>>>
> >>>> To add to this conversation, we have 5 mailing lists as of today:
> >>>>
> >>>> dev@z.a.o
> >>>> commits@z.a.o
> >>>> private@z.a.o
> >>>> security@z.a.o
> >>>> user@z.a.o
> >>>>
> >>>> The commits@ one was historically supposed to be for notifications.
> >>>>
> >>>> -Flavio
> >>>>
> >>>>
> >>>>> On 17 May 2019, at 16:50, Lars Francke 
> >> wrote:
> >>>>>
> >>>>> Alright, I will do so, thank you
> >>>>>
> >>>>> On Fri, May 17, 2019 at 11:46 AM Norbert Kalmar
> >>>>>  wrote:
> >>>>>
> >>>>>> I think we should start a vote.
> >>>>>>
> >>>>>> Lars, feel free to start it, as it is your initiative, you can place
> >>> your
> >>>>>> argument in the initial email.
> >>>>>> Thanks for bringing this up!
> >>>>>>
> >>>>>> Regards,
> >>>>>> Norbert
> >>>>>>
> >>>>>>
> >>>>>> On Fri, May 17, 2019 at 11:38 AM Lars Francke <
> >> lars.fran...@gmail.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> I don't really have anything else to add to this conversation. I
> >> agree
> >>>>>> with
> >>>>>>> Norbert & Andor.
> >>>>>>> Separating the lists is (slowly) becoming the standard at the ASF
> in
> >>> the
> >>>>>>> projects I participate in and it makes it easier for newcomers.
> >>>>>>>
> >>>>>>> Do we want to put this to a vote or abandon this?
> >>>>>>>
> >>>>>>> On Mon, May 13, 2019 at 5:33 PM Andor Molnar 
> >>> wrote:
> >>>>>>>
> >>>>>>>> Without responding to this, let’s clarify what emails are we
> >> talking
> >>>>>>> about:
> >>>>>>>>
> >>>>>>>> - Jenkins build notifications: failures / successes,
> >>>>>>>> - Jira notifications: Created, Updated, Status change, Commented,
> >>> etc.
> >>>>>>>> - Github notifications: opened/closed pull request, commented on
> >> pull
> >>>>>>>> request, etc.
> >>>>>>>>
> >>>>>>>> Researching a bit around it seems like that issues@ mailing list
> >> is
> >>> a
> >>>>>>>> common pattern across some Hadoop projects:
> >>>>>>>> https://hbase.apache.org/mailing-lists.html <
> >>>>>>>> https://hbase.apache.org/mailing-lists.html>
> >>>>>>>> https://hadoop.apache.org/mailing_lists.html <
> >>>>>>>> https://hadoop.apache.org/mailing_lists.html>
> >>>>>>>> https://kafka.apache.org/contact <
> https://kafka.apache.org/contact
> >>>
> >>>>>>>

Re: [NOTICE] Change of mailing list behavior (soon)

[Lars Francke]

GitHub notifications are now being sent to notifications@

I've asked that the commits@ mailing list is left untouched.

On Wed, May 29, 2019, 23:50 Lars Francke  wrote:

> In the next few days Jira & Git notifications will stop being sent to
> dev@zookeeper.apache.org.
>
> Only the creation of new issues will still be announced on dev@.
>
> For everything else notifications will be sent to issues@ (for Jira
> related things) and notifications@ (for Git related things).
>
> If you're interested in these notiifcations please subscribe to these
> mailing lists by sending a mail to:
> issues-subscr...@zookeeper.apache.org
> notifications-subscr...@zookeeper.apache.org
>
> I'll update this thread when INFRA has made the necessary changes.
>
> Thank you!
>

[jira] [Updated] (ZOOKEEPER-3407) Update POM file with new information

[Lars Francke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Francke updated ZOOKEEPER-3407:

Summary: Update POM file with new information  (was: Update POM with new 
mailing lists)

> Update POM file with new information
> 
>
> Key: ZOOKEEPER-3407
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3407
> Project: ZooKeeper
>  Issue Type: Task
>        Reporter: Lars Francke
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ZOOKEEPER-3407) Update POM file with new information

[Lars Francke (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Francke updated ZOOKEEPER-3407:

Description: New mailing lists & Jenkins update

> Update POM file with new information
> 
>
> Key: ZOOKEEPER-3407
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3407
> Project: ZooKeeper
>  Issue Type: Task
>    Reporter: Lars Francke
>Priority: Trivial
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> New mailing lists & Jenkins update



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ZOOKEEPER-3407) Update POM with new mailing lists

[Lars Francke (JIRA)]

Lars Francke created ZOOKEEPER-3407:
---

 Summary: Update POM with new mailing lists
 Key: ZOOKEEPER-3407
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3407
 Project: ZooKeeper
  Issue Type: Task
Reporter: Lars Francke






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ZOOKEEPER-3406) Update website for new mailing lists

[Lars Francke (JIRA)]

Lars Francke created ZOOKEEPER-3406:
---

 Summary: Update website for new mailing lists
 Key: ZOOKEEPER-3406
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3406
 Project: ZooKeeper
  Issue Type: Task
Reporter: Lars Francke


This updates the website to include information about issues@ and notifications@



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[NOTICE] Change of mailing list behavior (soon)

[Lars Francke]

In the next few days Jira & Git notifications will stop being sent to
dev@zookeeper.apache.org.

Only the creation of new issues will still be announced on dev@.

For everything else notifications will be sent to issues@ (for Jira related
things) and notifications@ (for Git related things).

If you're interested in these notiifcations please subscribe to these
mailing lists by sending a mail to:
issues-subscr...@zookeeper.apache.org
notifications-subscr...@zookeeper.apache.org

I'll update this thread when INFRA has made the necessary changes.

Thank you!

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Lars Francke]

The two mailing lists have been created.

I opened <https://issues.apache.org/jira/browse/INFRA-18524> & <
https://issues.apache.org/jira/browse/INFRA-1852
<https://issues.apache.org/jira/browse/INFRA-18524>5>

On Wed, May 29, 2019 at 11:34 PM Lars Francke 
wrote:

> Thank you Norbert, I'll submit
>
> You are right. I don't know either. But there's not really any written
> rules for this kind of change just a community consensus I believe.
>
> On Wed, May 29, 2019 at 12:02 PM Norbert Kalmar
>  wrote:
>
>> There is a source for the website [1], and the generated live site [2].
>> Also, there is a guide [3] available.
>>
>> I'm not sure a committer vote is binding here? :)
>>
>> [1]
>>
>> https://gitbox.apache.org/repos/asf?p=zookeeper.git;a=shortlog;h=refs/heads/website
>> [2]
>>
>> https://gitbox.apache.org/repos/asf?p=zookeeper.git;a=shortlog;h=refs/heads/asf-site
>> [3] https://cwiki.apache.org/confluence/display/ZOOKEEPER/WebSiteSetup
>>
>> On Wed, May 29, 2019 at 8:36 AM Lars Francke 
>> wrote:
>>
>> > Can anyone tell me where the site source lives?
>> >
>> > I assumed <https://svn.apache.org/viewvc/zookeeper/site/trunk/> but
>> that
>> > was updated 18 months ago but the site has information on release 3.5.5
>> so
>> > there must be something else somewhere.
>> >
>> > On Wed, May 29, 2019 at 8:30 AM Lars Francke 
>> > wrote:
>> >
>> > > Alright, I'm closing this.
>> > >
>> > > I've requested both issues@ and notifications@ and will file the
>> > > necessary tickets once that's done.
>> > > You should get a mail to private@ but I'll also check the status.
>> > >
>> > > On Mon, May 27, 2019 at 11:54 PM Lars Francke > >
>> > > wrote:
>> > >
>> > >> I'd like to close the vote but forgot to state the "rules" in the
>> > initial
>> > >> mail. I would think that this change requires lazy consensus which we
>> > have
>> > >> achieved already. But because I forgot I'll wait another day before I
>> > close
>> > >> this.
>> > >>
>> > >> 2 binding (both Enrico & Norbert are now committers,
>> congratulations!)
>> > >> 1 non-binding
>> > >>
>> > >> If there are no more objections until tomorrow I'll file the
>> necessary
>> > >> Jira tasks for INFRA (referring to this thread) and will request the
>> > >> mailing lists (using the same moderators as dev@).
>> > >>
>> > >> Cheers,
>> > >> Lars
>> > >>
>> > >> On Fri, May 17, 2019 at 7:06 PM Enrico Olivelli > >
>> > >> wrote:
>> > >>
>> > >>> +1
>> > >>>
>> > >>> Enrico
>> > >>>
>> > >>> Il ven 17 mag 2019, 17:11 Norbert Kalmar
>> > > >
>> > >>> ha
>> > >>> scritto:
>> > >>>
>> > >>> > +1 (non-binding)
>> > >>> >
>> > >>> > Whoever will do the change (if voted), needs to make sure stuff
>> like
>> > >>> > markmail are updated/checked.
>> > >>> > I see Apache projects going for separate mailing lists for
>> automated
>> > >>> > notifications (I subscribed to HBase and Thrift for example, they
>> > have
>> > >>> this
>> > >>> > separation).
>> > >>> >
>> > >>> > My +1 is to separate the automated messages from the dev list, we
>> can
>> > >>> > discuss the details. For example, we already have a commit list
>> [1].
>> > >>> Also,
>> > >>> > some automated messages might stay on this list, like creating a
>> new
>> > >>> jira
>> > >>> > (as mentioned on the DISCUSS thread).
>> > >>> >
>> > >>> > Regards,
>> > >>> > Norbert
>> > >>> >
>> > >>> > [1] https://zookeeper.apache.org/lists.html
>> > >>> >
>> > >>> > On Fri, May 17, 2019 at 5:00 PM Lars Francke <
>> lars.fran...@gmail.com
>> > >
>> > >>> > wrote:
>> > >>> >
>> > >>> > > And here is my +1 (non-binding)

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Lars Francke]

Thank you Norbert, I'll submit

You are right. I don't know either. But there's not really any written
rules for this kind of change just a community consensus I believe.

On Wed, May 29, 2019 at 12:02 PM Norbert Kalmar
 wrote:

> There is a source for the website [1], and the generated live site [2].
> Also, there is a guide [3] available.
>
> I'm not sure a committer vote is binding here? :)
>
> [1]
>
> https://gitbox.apache.org/repos/asf?p=zookeeper.git;a=shortlog;h=refs/heads/website
> [2]
>
> https://gitbox.apache.org/repos/asf?p=zookeeper.git;a=shortlog;h=refs/heads/asf-site
> [3] https://cwiki.apache.org/confluence/display/ZOOKEEPER/WebSiteSetup
>
> On Wed, May 29, 2019 at 8:36 AM Lars Francke 
> wrote:
>
> > Can anyone tell me where the site source lives?
> >
> > I assumed <https://svn.apache.org/viewvc/zookeeper/site/trunk/> but that
> > was updated 18 months ago but the site has information on release 3.5.5
> so
> > there must be something else somewhere.
> >
> > On Wed, May 29, 2019 at 8:30 AM Lars Francke 
> > wrote:
> >
> > > Alright, I'm closing this.
> > >
> > > I've requested both issues@ and notifications@ and will file the
> > > necessary tickets once that's done.
> > > You should get a mail to private@ but I'll also check the status.
> > >
> > > On Mon, May 27, 2019 at 11:54 PM Lars Francke 
> > > wrote:
> > >
> > >> I'd like to close the vote but forgot to state the "rules" in the
> > initial
> > >> mail. I would think that this change requires lazy consensus which we
> > have
> > >> achieved already. But because I forgot I'll wait another day before I
> > close
> > >> this.
> > >>
> > >> 2 binding (both Enrico & Norbert are now committers, congratulations!)
> > >> 1 non-binding
> > >>
> > >> If there are no more objections until tomorrow I'll file the necessary
> > >> Jira tasks for INFRA (referring to this thread) and will request the
> > >> mailing lists (using the same moderators as dev@).
> > >>
> > >> Cheers,
> > >> Lars
> > >>
> > >> On Fri, May 17, 2019 at 7:06 PM Enrico Olivelli 
> > >> wrote:
> > >>
> > >>> +1
> > >>>
> > >>> Enrico
> > >>>
> > >>> Il ven 17 mag 2019, 17:11 Norbert Kalmar
>  > >
> > >>> ha
> > >>> scritto:
> > >>>
> > >>> > +1 (non-binding)
> > >>> >
> > >>> > Whoever will do the change (if voted), needs to make sure stuff
> like
> > >>> > markmail are updated/checked.
> > >>> > I see Apache projects going for separate mailing lists for
> automated
> > >>> > notifications (I subscribed to HBase and Thrift for example, they
> > have
> > >>> this
> > >>> > separation).
> > >>> >
> > >>> > My +1 is to separate the automated messages from the dev list, we
> can
> > >>> > discuss the details. For example, we already have a commit list
> [1].
> > >>> Also,
> > >>> > some automated messages might stay on this list, like creating a
> new
> > >>> jira
> > >>> > (as mentioned on the DISCUSS thread).
> > >>> >
> > >>> > Regards,
> > >>> > Norbert
> > >>> >
> > >>> > [1] https://zookeeper.apache.org/lists.html
> > >>> >
> > >>> > On Fri, May 17, 2019 at 5:00 PM Lars Francke <
> lars.fran...@gmail.com
> > >
> > >>> > wrote:
> > >>> >
> > >>> > > And here is my +1 (non-binding)
> > >>> > >
> > >>> > > On Fri, May 17, 2019 at 4:55 PM Lars Francke <
> > lars.fran...@gmail.com
> > >>> >
> > >>> > > wrote:
> > >>> > >
> > >>> > > > Hi ZooKeeper devs,
> > >>> > > >
> > >>> > > > I'd like to call a vote on whether we want to have separate
> > mailing
> > >>> > lists
> > >>> > > > for dev chatter (mostly humans) and automated notifications
> > >>> > > >
> > >>> > > > Andor summarized this in another thread:
> > >>> > > > - Jenkins build notifications: 

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Lars Francke]

Can anyone tell me where the site source lives?

I assumed <https://svn.apache.org/viewvc/zookeeper/site/trunk/> but that
was updated 18 months ago but the site has information on release 3.5.5 so
there must be something else somewhere.

On Wed, May 29, 2019 at 8:30 AM Lars Francke  wrote:

> Alright, I'm closing this.
>
> I've requested both issues@ and notifications@ and will file the
> necessary tickets once that's done.
> You should get a mail to private@ but I'll also check the status.
>
> On Mon, May 27, 2019 at 11:54 PM Lars Francke 
> wrote:
>
>> I'd like to close the vote but forgot to state the "rules" in the initial
>> mail. I would think that this change requires lazy consensus which we have
>> achieved already. But because I forgot I'll wait another day before I close
>> this.
>>
>> 2 binding (both Enrico & Norbert are now committers, congratulations!)
>> 1 non-binding
>>
>> If there are no more objections until tomorrow I'll file the necessary
>> Jira tasks for INFRA (referring to this thread) and will request the
>> mailing lists (using the same moderators as dev@).
>>
>> Cheers,
>> Lars
>>
>> On Fri, May 17, 2019 at 7:06 PM Enrico Olivelli 
>> wrote:
>>
>>> +1
>>>
>>> Enrico
>>>
>>> Il ven 17 mag 2019, 17:11 Norbert Kalmar 
>>> ha
>>> scritto:
>>>
>>> > +1 (non-binding)
>>> >
>>> > Whoever will do the change (if voted), needs to make sure stuff like
>>> > markmail are updated/checked.
>>> > I see Apache projects going for separate mailing lists for automated
>>> > notifications (I subscribed to HBase and Thrift for example, they have
>>> this
>>> > separation).
>>> >
>>> > My +1 is to separate the automated messages from the dev list, we can
>>> > discuss the details. For example, we already have a commit list [1].
>>> Also,
>>> > some automated messages might stay on this list, like creating a new
>>> jira
>>> > (as mentioned on the DISCUSS thread).
>>> >
>>> > Regards,
>>> > Norbert
>>> >
>>> > [1] https://zookeeper.apache.org/lists.html
>>> >
>>> > On Fri, May 17, 2019 at 5:00 PM Lars Francke 
>>> > wrote:
>>> >
>>> > > And here is my +1 (non-binding)
>>> > >
>>> > > On Fri, May 17, 2019 at 4:55 PM Lars Francke >> >
>>> > > wrote:
>>> > >
>>> > > > Hi ZooKeeper devs,
>>> > > >
>>> > > > I'd like to call a vote on whether we want to have separate mailing
>>> > lists
>>> > > > for dev chatter (mostly humans) and automated notifications
>>> > > >
>>> > > > Andor summarized this in another thread:
>>> > > > - Jenkins build notifications: failures / successes,
>>> > > > - Jira notifications: Created, Updated, Status change, Commented,
>>> etc.
>>> > > > - Github notifications: opened/closed pull request, commented on
>>> pull
>>> > > > request, etc.
>>> > > >
>>> > > > This was previously discussed in two threads[1][2]
>>> > > >
>>> > > > This is the suggestion:
>>> > > > Jira
>>> > > > 
>>> > > > Issue created -> dev@zookeeper.apache.org + issues@
>>> > > > Everything else -> iss...@zookeeper.apache.org
>>> > > >
>>> > > > Github/Gitbox
>>> > > > --
>>> > > > All notifications sent to notificati...@zookeeper.apache.org
>>> > > >
>>> > > > issues@ and notifications@ mailing lists have to be created first.
>>> > > >
>>> > > >
>>> > > > Please vote on the issue. I'll leave the vote running for at least
>>> 72
>>> > > > hours considering we have a weekend ahead of us probably a bit
>>> longer.
>>> > > >
>>> > > > Cheers,
>>> > > > Lars
>>> > > >
>>> > > > [1] <
>>> > > >
>>> > >
>>> >
>>> https://lists.apache.org/thread.html/ae530b1c7dae8b83740d83243f18b76d6e0e6572ff1bfb6189e6e0d6@%3Cdev.zookeeper.apache.org%3E
>>> > > > >
>>> > > > [2] <
>>> > > >
>>> > >
>>> >
>>> https://lists.apache.org/thread.html/bd7bdae9da67145dcde636219c6d3bd8429565cd864abc55358eb67f@
>>> > > 
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Lars Francke]

Alright, I'm closing this.

I've requested both issues@ and notifications@ and will file the necessary
tickets once that's done.
You should get a mail to private@ but I'll also check the status.

On Mon, May 27, 2019 at 11:54 PM Lars Francke 
wrote:

> I'd like to close the vote but forgot to state the "rules" in the initial
> mail. I would think that this change requires lazy consensus which we have
> achieved already. But because I forgot I'll wait another day before I close
> this.
>
> 2 binding (both Enrico & Norbert are now committers, congratulations!)
> 1 non-binding
>
> If there are no more objections until tomorrow I'll file the necessary
> Jira tasks for INFRA (referring to this thread) and will request the
> mailing lists (using the same moderators as dev@).
>
> Cheers,
> Lars
>
> On Fri, May 17, 2019 at 7:06 PM Enrico Olivelli 
> wrote:
>
>> +1
>>
>> Enrico
>>
>> Il ven 17 mag 2019, 17:11 Norbert Kalmar 
>> ha
>> scritto:
>>
>> > +1 (non-binding)
>> >
>> > Whoever will do the change (if voted), needs to make sure stuff like
>> > markmail are updated/checked.
>> > I see Apache projects going for separate mailing lists for automated
>> > notifications (I subscribed to HBase and Thrift for example, they have
>> this
>> > separation).
>> >
>> > My +1 is to separate the automated messages from the dev list, we can
>> > discuss the details. For example, we already have a commit list [1].
>> Also,
>> > some automated messages might stay on this list, like creating a new
>> jira
>> > (as mentioned on the DISCUSS thread).
>> >
>> > Regards,
>> > Norbert
>> >
>> > [1] https://zookeeper.apache.org/lists.html
>> >
>> > On Fri, May 17, 2019 at 5:00 PM Lars Francke 
>> > wrote:
>> >
>> > > And here is my +1 (non-binding)
>> > >
>> > > On Fri, May 17, 2019 at 4:55 PM Lars Francke 
>> > > wrote:
>> > >
>> > > > Hi ZooKeeper devs,
>> > > >
>> > > > I'd like to call a vote on whether we want to have separate mailing
>> > lists
>> > > > for dev chatter (mostly humans) and automated notifications
>> > > >
>> > > > Andor summarized this in another thread:
>> > > > - Jenkins build notifications: failures / successes,
>> > > > - Jira notifications: Created, Updated, Status change, Commented,
>> etc.
>> > > > - Github notifications: opened/closed pull request, commented on
>> pull
>> > > > request, etc.
>> > > >
>> > > > This was previously discussed in two threads[1][2]
>> > > >
>> > > > This is the suggestion:
>> > > > Jira
>> > > > 
>> > > > Issue created -> dev@zookeeper.apache.org + issues@
>> > > > Everything else -> iss...@zookeeper.apache.org
>> > > >
>> > > > Github/Gitbox
>> > > > --
>> > > > All notifications sent to notificati...@zookeeper.apache.org
>> > > >
>> > > > issues@ and notifications@ mailing lists have to be created first.
>> > > >
>> > > >
>> > > > Please vote on the issue. I'll leave the vote running for at least
>> 72
>> > > > hours considering we have a weekend ahead of us probably a bit
>> longer.
>> > > >
>> > > > Cheers,
>> > > > Lars
>> > > >
>> > > > [1] <
>> > > >
>> > >
>> >
>> https://lists.apache.org/thread.html/ae530b1c7dae8b83740d83243f18b76d6e0e6572ff1bfb6189e6e0d6@%3Cdev.zookeeper.apache.org%3E
>> > > > >
>> > > > [2] <
>> > > >
>> > >
>> >
>> https://lists.apache.org/thread.html/bd7bdae9da67145dcde636219c6d3bd8429565cd864abc55358eb67f@
>> > > 
>> > > > >
>> > > >
>> > >
>> >
>>
>

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Lars Francke]

I'd like to close the vote but forgot to state the "rules" in the initial
mail. I would think that this change requires lazy consensus which we have
achieved already. But because I forgot I'll wait another day before I close
this.

2 binding (both Enrico & Norbert are now committers, congratulations!)
1 non-binding

If there are no more objections until tomorrow I'll file the necessary Jira
tasks for INFRA (referring to this thread) and will request the mailing
lists (using the same moderators as dev@).

Cheers,
Lars

On Fri, May 17, 2019 at 7:06 PM Enrico Olivelli  wrote:

> +1
>
> Enrico
>
> Il ven 17 mag 2019, 17:11 Norbert Kalmar  ha
> scritto:
>
> > +1 (non-binding)
> >
> > Whoever will do the change (if voted), needs to make sure stuff like
> > markmail are updated/checked.
> > I see Apache projects going for separate mailing lists for automated
> > notifications (I subscribed to HBase and Thrift for example, they have
> this
> > separation).
> >
> > My +1 is to separate the automated messages from the dev list, we can
> > discuss the details. For example, we already have a commit list [1].
> Also,
> > some automated messages might stay on this list, like creating a new jira
> > (as mentioned on the DISCUSS thread).
> >
> > Regards,
> > Norbert
> >
> > [1] https://zookeeper.apache.org/lists.html
> >
> > On Fri, May 17, 2019 at 5:00 PM Lars Francke 
> > wrote:
> >
> > > And here is my +1 (non-binding)
> > >
> > > On Fri, May 17, 2019 at 4:55 PM Lars Francke 
> > > wrote:
> > >
> > > > Hi ZooKeeper devs,
> > > >
> > > > I'd like to call a vote on whether we want to have separate mailing
> > lists
> > > > for dev chatter (mostly humans) and automated notifications
> > > >
> > > > Andor summarized this in another thread:
> > > > - Jenkins build notifications: failures / successes,
> > > > - Jira notifications: Created, Updated, Status change, Commented,
> etc.
> > > > - Github notifications: opened/closed pull request, commented on pull
> > > > request, etc.
> > > >
> > > > This was previously discussed in two threads[1][2]
> > > >
> > > > This is the suggestion:
> > > > Jira
> > > > 
> > > > Issue created -> dev@zookeeper.apache.org + issues@
> > > > Everything else -> iss...@zookeeper.apache.org
> > > >
> > > > Github/Gitbox
> > > > --
> > > > All notifications sent to notificati...@zookeeper.apache.org
> > > >
> > > > issues@ and notifications@ mailing lists have to be created first.
> > > >
> > > >
> > > > Please vote on the issue. I'll leave the vote running for at least 72
> > > > hours considering we have a weekend ahead of us probably a bit
> longer.
> > > >
> > > > Cheers,
> > > > Lars
> > > >
> > > > [1] <
> > > >
> > >
> >
> https://lists.apache.org/thread.html/ae530b1c7dae8b83740d83243f18b76d6e0e6572ff1bfb6189e6e0d6@%3Cdev.zookeeper.apache.org%3E
> > > > >
> > > > [2] <
> > > >
> > >
> >
> https://lists.apache.org/thread.html/bd7bdae9da67145dcde636219c6d3bd8429565cd864abc55358eb67f@
> > > 
> > > > >
> > > >
> > >
> >
>

Re: Re: Request for review & contribution of Apache Training

[Lars Francke]

Hi everyone!

This is now a proper pull request with 3.5 content added and converted to
Asciidoc: <https://github.com/apache/incubator-training/pull/14>

Cheers,
Lars

On Sun, Apr 28, 2019 at 5:20 AM Justin Ling Mao 
wrote:

> @Lars.Thanks for this:
> https://drive.google.com/file/d/1STmz-nTBjGeFuu8ycjrFDSL-KdahAQiG/view
> - Original Message -
> From: Flavio Junqueira 
> To: dev@zookeeper.apache.org
> Cc: Patrick Hunt 
> Subject: Re: Request for review & contribution of Apache Training
> Date: 2019-04-28 03:10
>
>
> This is great, Lars. Thanks for putting this together. I have some
> additional comments:
> - I'd rather not characterize zookeeper as a key-value store, one reason
> being that to access a znode we give a "path" and not a "key". I don't want
> to open this up to a discussion on what a key-value store actually is, but
> I typically say that it is a hierarchy of znodes and explain what a znode
> is (Slide 2). If it is early to talk about znodes, then say hierarchy of
> simple data files.
> - It would be nice to have a slide illustrating how to get going with
> zookeeper, like starting a server with `bin/zkServer.sh start` and using
> the `bin/zkCli.sh` to issue some commands.
> - In Slide 8, the statement saying that "in an ensemble we always have a
> single leader" isn't accurate. I think you want to say something along the
> lines of "in an ensemble there is at most on leader server supported by a
> majority of followers".
> Thanks again for the initiative.
> -Flavio
> > On 27 Apr 2019, at 00:55, Lars Francke  wrote:
> >
> > Thank you Patrick, that's great!
> >
> > I've incorporated the feedback (and a bit more) and have uploaded a new
> > version.
> >
> > This is just a first start and I hope that over time the community will
> > expand on it (e.g. slides on use cases/patterns/recipes, API usage, the
> Zab
> > protocol, etc.). This is also an invitation to the ZooKeeper community to
> > add anything at any point if you feel it's worthwhile to teach to
> potential
> > learners. If you don't want to fiddle around with slides that's fine as
> > well, just filing an issue in Jira in the TRAINING project will already
> > help.
> >
> > Cheers,
> > Lars
> >
> > On Fri, Apr 26, 2019 at 10:49 PM Patrick Hunt  wrote:
> >
> >> Wow, this is great, thanks Lars. I reviewed, here are my comments:
> >>
> >> 3: you might highlight that it's used outside hadoop (e.g. solr and many
> >> others inside and outside apache). Also heavily using in the tech
> industry;
> >> facebook, twitter, linkedin, etc...
> >>
> >> You might also reference Curator as it's a good way to get started from
> a
> >> client perspective.
> >>
> >> Regards,
> >>
> >> Patrick
> >>
> >> On Fri, Apr 26, 2019 at 7:20 AM Lars Francke 
> >> wrote:
> >>
> >>> Hi ZooKeeper devs,
> >>>
> >>> we started the Apache Training (incubating) project back in February.
> >>> Our aim is to develop training material (slides, labs, tests etc.) for
> all
> >>> kinds of projects (mostly focusing on Apache projects but not
> >>> exclusively).
> >>>
> >>> We're still getting off the ground with homepage and so. We're also
> >>> working
> >>> on the very first content donation which is a super simple four slide
> >>> ZooKeeper introduction.
> >>>
> >>> I chose this because it's small and we can test our processes.
> >>>
> >>> I still wanted to reach out and see if anyone here is interested in
> >>> contributing anything and/or reviewing the existing material. It can be
> >>> found in Jira: <https://issues.apache.org/jira/browse/TRAINING-13>
> >>>
> >>> Thank you very much!
> >>>
> >>> Cheers,
> >>> Lars
> >>>
> >>
>

Re: Github & Jira notifications

[Lars Francke]

Me neither. I'm happy to keep the vote open a bit longer, we're in no rush.

Patrick, do you have anything to add?

On Mon, May 20, 2019 at 1:15 PM Andor Molnar  wrote:

> I’m not sure whether we have convinced Patrick entirely.
> Before casting my vote, I’d be happy if we could reach consensus in the
> community with this change, not just majority.
>
> Reason is that I rather feel it a nice-to-have improvement, not critical.
>
> Andor
>
>
>
> > On 2019. May 17., at 17:05, Flavio Junqueira  wrote:
> >
> > To add to this conversation, we have 5 mailing lists as of today:
> >
> > dev@z.a.o
> > commits@z.a.o
> > private@z.a.o
> > security@z.a.o
> > user@z.a.o
> >
> > The commits@ one was historically supposed to be for notifications.
> >
> > -Flavio
> >
> >
> >> On 17 May 2019, at 16:50, Lars Francke  wrote:
> >>
> >> Alright, I will do so, thank you
> >>
> >> On Fri, May 17, 2019 at 11:46 AM Norbert Kalmar
> >>  wrote:
> >>
> >>> I think we should start a vote.
> >>>
> >>> Lars, feel free to start it, as it is your initiative, you can place
> your
> >>> argument in the initial email.
> >>> Thanks for bringing this up!
> >>>
> >>> Regards,
> >>> Norbert
> >>>
> >>>
> >>> On Fri, May 17, 2019 at 11:38 AM Lars Francke 
> >>> wrote:
> >>>
> >>>> I don't really have anything else to add to this conversation. I agree
> >>> with
> >>>> Norbert & Andor.
> >>>> Separating the lists is (slowly) becoming the standard at the ASF in
> the
> >>>> projects I participate in and it makes it easier for newcomers.
> >>>>
> >>>> Do we want to put this to a vote or abandon this?
> >>>>
> >>>> On Mon, May 13, 2019 at 5:33 PM Andor Molnar 
> wrote:
> >>>>
> >>>>> Without responding to this, let’s clarify what emails are we talking
> >>>> about:
> >>>>>
> >>>>> - Jenkins build notifications: failures / successes,
> >>>>> - Jira notifications: Created, Updated, Status change, Commented,
> etc.
> >>>>> - Github notifications: opened/closed pull request, commented on pull
> >>>>> request, etc.
> >>>>>
> >>>>> Researching a bit around it seems like that issues@ mailing list is
> a
> >>>>> common pattern across some Hadoop projects:
> >>>>> https://hbase.apache.org/mailing-lists.html <
> >>>>> https://hbase.apache.org/mailing-lists.html>
> >>>>> https://hadoop.apache.org/mailing_lists.html <
> >>>>> https://hadoop.apache.org/mailing_lists.html>
> >>>>> https://kafka.apache.org/contact <https://kafka.apache.org/contact>
> >>>>>
> >>>>> But not on:
> >>>>> https://hive.apache.org/mailing_lists.html <
> >>>>> https://hive.apache.org/mailing_lists.html>
> >>>>> https://oozie.apache.org/mail-lists.html <
> >>>>> https://oozie.apache.org/mail-lists.html>
> >>>>>
> >>>>> Regards,
> >>>>> Andor
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On 2019. May 13., at 16:43, Patrick Hunt  wrote:
> >>>>>>
> >>>>>> I seem to remember that in the early days of apache the intent was
> >>> for
> >>>>> all
> >>>>>> developers to participate in development of the project. MLs were
> >>> used
> >>>>> for
> >>>>>> this initially and there has been concern in the past about the move
> >>> to
> >>>>>> JIRA as it removes critical discussions from the general dev flow.
> >>> JIRA
> >>>>>> discussions are cc'd to an ML for just this reason. Granted another
> >>>>> aspect
> >>>>>> of this mirroring is for archival purposes.
> >>>>>>
> >>>>>> As such the intent is for developers to participate in development
> >>>>>> discussion. It sounds like you're turning this on it's head.
> >>>>>>
> >>>>>> Isn't this why we have a user list? For folks that are only casually
> >>>>>> interested in proje

[jira] [Commented] (ZOOKEEPER-1147) Add support for local sessions

[Lars Francke (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16844602#comment-16844602
 ] 

Lars Francke commented on ZOOKEEPER-1147:
-

Thanks for checking. Did you already create a follow-up ticket? If not I can do 
so.

> Add support for local sessions
> --
>
> Key: ZOOKEEPER-1147
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1147
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.3
>Reporter: Vishal Kathuria
>Assignee: Thawan Kooburat
>Priority: Major
>  Labels: api-change, scaling
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1147.patch, ZOOKEEPER-1147.patch, 
> ZOOKEEPER-1147.patch, ZOOKEEPER-1147.patch, ZOOKEEPER-1147.patch, 
> ZOOKEEPER-1147.patch, ZOOKEEPER-1147.patch, ZOOKEEPER-1147.patch, 
> ZOOKEEPER-1147.patch
>
>   Original Estimate: 840h
>  Remaining Estimate: 840h
>
> This improvement is in the bucket of making ZooKeeper work at a large scale. 
> We are planning on having about a 1 million clients connect to a ZooKeeper 
> ensemble through a set of 50-100 observers. Majority of these clients are 
> read only - ie they do not do any updates or create ephemeral nodes.
> In ZooKeeper today, the client creates a session and the session creation is 
> handled like any other update. In the above use case, the session create/drop 
> workload can easily overwhelm an ensemble. The following is a proposal for a 
> "local session", to support a larger number of connections.
> 1.   The idea is to introduce a new type of session - "local" session. A 
> "local" session doesn't have a full functionality of a normal session.
> 2.   Local sessions cannot create ephemeral nodes.
> 3.   Once a local session is lost, you cannot re-establish it using the 
> session-id/password. The session and its watches are gone for good.
> 4.   When a local session connects, the session info is only maintained 
> on the zookeeper server (in this case, an observer) that it is connected to. 
> The leader is not aware of the creation of such a session and there is no 
> state written to disk.
> 5.   The pings and expiration is handled by the server that the session 
> is connected to.
> With the above changes, we can make ZooKeeper scale to a much larger number 
> of clients without making the core ensemble a bottleneck.
> In terms of API, there are two options that are being considered
> 1. Let the client specify at the connect time which kind of session do they 
> want.
> 2. All sessions connect as local sessions and automatically get promoted to 
> global sessions when they do an operation that requires a global session 
> (e.g. creating an ephemeral node)
> Chubby took the approach of lazily promoting all sessions to global, but I 
> don't think that would work in our case, where we want to keep sessions which 
> never create ephemeral nodes as always local. Option 2 would make it more 
> broadly usable but option 1 would be easier to implement.
> We are thinking of implementing option 1 as the first cut. There would be a 
> client flag, IsLocalSession (much like the current readOnly flag) that would 
> be used to determine whether to create a local session or a global session.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [ANNOUNCE] Apache ZooKeeper 3.5.5

[Lars Francke]

Congratulations on this release! It looks great and I'm looking forward to
using all those new features.

Thank you, everyone, for your work on this.

On Mon, May 20, 2019 at 7:06 PM Andor Molnar  wrote:

> The Apache ZooKeeper team is proud to announce Apache ZooKeeper version
> 3.5.5
>
> ZooKeeper is a high-performance coordination service for distributed
> applications. It exposes common services - such as naming,
> configuration management, synchronization, and group services - in a
> simple interface so you don't have to write them from scratch. You can
> use it off-the-shelf to implement consensus, group management, leader
> election, and presence protocols. And you can build on it for your
> own, specific needs.
>
> For ZooKeeper release details and downloads, visit:
> https://zookeeper.apache.org/releases.html
>
> ZooKeeper 3.5.5 Release Notes are at:
> https://zookeeper.apache.org/doc/r3.5.5/releasenotes.html
>
> We would like to thank the contributors that made the release possible.
>
> Regards,
>
> The ZooKeeper Team
>
>
>

[jira] [Commented] (ZOOKEEPER-1147) Add support for local sessions

[Lars Francke (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16844139#comment-16844139
 ] 

Lars Francke commented on ZOOKEEPER-1147:
-

I just saw this in the release announcement for 3.5: Is there any documentation 
on this available?

> Add support for local sessions
> --
>
> Key: ZOOKEEPER-1147
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1147
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: server
>Affects Versions: 3.3.3
>Reporter: Vishal Kathuria
>Assignee: Thawan Kooburat
>Priority: Major
>  Labels: api-change, scaling
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1147.patch, ZOOKEEPER-1147.patch, 
> ZOOKEEPER-1147.patch, ZOOKEEPER-1147.patch, ZOOKEEPER-1147.patch, 
> ZOOKEEPER-1147.patch, ZOOKEEPER-1147.patch, ZOOKEEPER-1147.patch, 
> ZOOKEEPER-1147.patch
>
>   Original Estimate: 840h
>  Remaining Estimate: 840h
>
> This improvement is in the bucket of making ZooKeeper work at a large scale. 
> We are planning on having about a 1 million clients connect to a ZooKeeper 
> ensemble through a set of 50-100 observers. Majority of these clients are 
> read only - ie they do not do any updates or create ephemeral nodes.
> In ZooKeeper today, the client creates a session and the session creation is 
> handled like any other update. In the above use case, the session create/drop 
> workload can easily overwhelm an ensemble. The following is a proposal for a 
> "local session", to support a larger number of connections.
> 1.   The idea is to introduce a new type of session - "local" session. A 
> "local" session doesn't have a full functionality of a normal session.
> 2.   Local sessions cannot create ephemeral nodes.
> 3.   Once a local session is lost, you cannot re-establish it using the 
> session-id/password. The session and its watches are gone for good.
> 4.   When a local session connects, the session info is only maintained 
> on the zookeeper server (in this case, an observer) that it is connected to. 
> The leader is not aware of the creation of such a session and there is no 
> state written to disk.
> 5.   The pings and expiration is handled by the server that the session 
> is connected to.
> With the above changes, we can make ZooKeeper scale to a much larger number 
> of clients without making the core ensemble a bottleneck.
> In terms of API, there are two options that are being considered
> 1. Let the client specify at the connect time which kind of session do they 
> want.
> 2. All sessions connect as local sessions and automatically get promoted to 
> global sessions when they do an operation that requires a global session 
> (e.g. creating an ephemeral node)
> Chubby took the approach of lazily promoting all sessions to global, but I 
> don't think that would work in our case, where we want to keep sessions which 
> never create ephemeral nodes as always local. Option 2 would make it more 
> broadly usable but option 1 would be easier to implement.
> We are thinking of implementing option 1 as the first cut. There would be a 
> client flag, IsLocalSession (much like the current readOnly flag) that would 
> be used to determine whether to create a local session or a global session.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Lars Francke]

Hi ZooKeeper devs,

I'd like to call a vote on whether we want to have separate mailing lists
for dev chatter (mostly humans) and automated notifications

Andor summarized this in another thread:
- Jenkins build notifications: failures / successes,
- Jira notifications: Created, Updated, Status change, Commented, etc.
- Github notifications: opened/closed pull request, commented on pull
request, etc.

This was previously discussed in two threads[1][2]

This is the suggestion:
Jira

Issue created -> dev@zookeeper.apache.org + issues@
Everything else -> iss...@zookeeper.apache.org

Github/Gitbox
--
All notifications sent to notificati...@zookeeper.apache.org

issues@ and notifications@ mailing lists have to be created first.


Please vote on the issue. I'll leave the vote running for at least 72 hours
considering we have a weekend ahead of us probably a bit longer.

Cheers,
Lars

[1] <
https://lists.apache.org/thread.html/ae530b1c7dae8b83740d83243f18b76d6e0e6572ff1bfb6189e6e0d6@%3Cdev.zookeeper.apache.org%3E
>
[2] <
https://lists.apache.org/thread.html/bd7bdae9da67145dcde636219c6d3bd8429565cd864abc55358eb67f@
>

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications - Take 2

[Lars Francke]

And here is my +1 (non-binding)

On Fri, May 17, 2019 at 4:55 PM Lars Francke  wrote:

> Hi ZooKeeper devs,
>
> I'd like to call a vote on whether we want to have separate mailing lists
> for dev chatter (mostly humans) and automated notifications
>
> Andor summarized this in another thread:
> - Jenkins build notifications: failures / successes,
> - Jira notifications: Created, Updated, Status change, Commented, etc.
> - Github notifications: opened/closed pull request, commented on pull
> request, etc.
>
> This was previously discussed in two threads[1][2]
>
> This is the suggestion:
> Jira
> 
> Issue created -> dev@zookeeper.apache.org + issues@
> Everything else -> iss...@zookeeper.apache.org
>
> Github/Gitbox
> --
> All notifications sent to notificati...@zookeeper.apache.org
>
> issues@ and notifications@ mailing lists have to be created first.
>
>
> Please vote on the issue. I'll leave the vote running for at least 72
> hours considering we have a weekend ahead of us probably a bit longer.
>
> Cheers,
> Lars
>
> [1] <
> https://lists.apache.org/thread.html/ae530b1c7dae8b83740d83243f18b76d6e0e6572ff1bfb6189e6e0d6@%3Cdev.zookeeper.apache.org%3E
> >
> [2] <
> https://lists.apache.org/thread.html/bd7bdae9da67145dcde636219c6d3bd8429565cd864abc55358eb67f@
> >
>

Re: Github & Jira notifications

[Lars Francke]

Alright, I will do so, thank you

On Fri, May 17, 2019 at 11:46 AM Norbert Kalmar
 wrote:

> I think we should start a vote.
>
> Lars, feel free to start it, as it is your initiative, you can place your
> argument in the initial email.
> Thanks for bringing this up!
>
> Regards,
> Norbert
>
>
> On Fri, May 17, 2019 at 11:38 AM Lars Francke 
> wrote:
>
> > I don't really have anything else to add to this conversation. I agree
> with
> > Norbert & Andor.
> > Separating the lists is (slowly) becoming the standard at the ASF in the
> > projects I participate in and it makes it easier for newcomers.
> >
> > Do we want to put this to a vote or abandon this?
> >
> > On Mon, May 13, 2019 at 5:33 PM Andor Molnar  wrote:
> >
> > > Without responding to this, let’s clarify what emails are we talking
> > about:
> > >
> > > - Jenkins build notifications: failures / successes,
> > > - Jira notifications: Created, Updated, Status change, Commented, etc.
> > > - Github notifications: opened/closed pull request, commented on pull
> > > request, etc.
> > >
> > > Researching a bit around it seems like that issues@ mailing list is a
> > > common pattern across some Hadoop projects:
> > > https://hbase.apache.org/mailing-lists.html <
> > > https://hbase.apache.org/mailing-lists.html>
> > > https://hadoop.apache.org/mailing_lists.html <
> > > https://hadoop.apache.org/mailing_lists.html>
> > > https://kafka.apache.org/contact <https://kafka.apache.org/contact>
> > >
> > > But not on:
> > > https://hive.apache.org/mailing_lists.html <
> > > https://hive.apache.org/mailing_lists.html>
> > > https://oozie.apache.org/mail-lists.html <
> > > https://oozie.apache.org/mail-lists.html>
> > >
> > > Regards,
> > > Andor
> > >
> > >
> > >
> > > > On 2019. May 13., at 16:43, Patrick Hunt  wrote:
> > > >
> > > > I seem to remember that in the early days of apache the intent was
> for
> > > all
> > > > developers to participate in development of the project. MLs were
> used
> > > for
> > > > this initially and there has been concern in the past about the move
> to
> > > > JIRA as it removes critical discussions from the general dev flow.
> JIRA
> > > > discussions are cc'd to an ML for just this reason. Granted another
> > > aspect
> > > > of this mirroring is for archival purposes.
> > > >
> > > > As such the intent is for developers to participate in development
> > > > discussion. It sounds like you're turning this on it's head.
> > > >
> > > > Isn't this why we have a user list? For folks that are only casually
> > > > interested in project activity?
> > > >
> > > > Patrick
> > > >
> > > > On Mon, May 13, 2019 at 3:31 AM Andor Molnar 
> wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> Sorry for starting the vote too early, for some reason I thought
> it’s
> > a
> > > >> straightforward thing, but the concerns are valid.
> > > >>
> > > >> I believe this is a good thing to do now, because the activity in
> > > >> ZooKeeper community has reached a level which the dev list with all
> > > >> notifications included hasn’t been prepared for. I see emails every
> > now
> > > and
> > > >> then from people who fed up with the flood of notification emails
> and
> > > >> decide to unsubscribe instead of taking the hassle of dealing with
> > email
> > > >> filters.
> > > >>
> > > >> *Filters*
> > > >> Pretty much everything which can be done with separate mailing
> lists,
> > > can
> > > >> be achieved by some clever email filters too. Though I think having
> > > >> multiple mailing lists is technologically a better distinction for
> > > emails:
> > > >> separate archives, different retention policies, less email to be
> > > delivered
> > > >> (filters working on client side) and more convenient for new
> > > subscribers.
> > > >>
> > > >> *Markmail*
> > > >> I’m a power user of markmail too, but I’m not sure how it works.
> Tbh I
> > > >> cannot see the benefits of searching for automated emails from
> Gitbox,
> > 

Re: Github & Jira notifications

[Lars Francke]

I don't really have anything else to add to this conversation. I agree with
Norbert & Andor.
Separating the lists is (slowly) becoming the standard at the ASF in the
projects I participate in and it makes it easier for newcomers.

Do we want to put this to a vote or abandon this?

On Mon, May 13, 2019 at 5:33 PM Andor Molnar  wrote:

> Without responding to this, let’s clarify what emails are we talking about:
>
> - Jenkins build notifications: failures / successes,
> - Jira notifications: Created, Updated, Status change, Commented, etc.
> - Github notifications: opened/closed pull request, commented on pull
> request, etc.
>
> Researching a bit around it seems like that issues@ mailing list is a
> common pattern across some Hadoop projects:
> https://hbase.apache.org/mailing-lists.html <
> https://hbase.apache.org/mailing-lists.html>
> https://hadoop.apache.org/mailing_lists.html <
> https://hadoop.apache.org/mailing_lists.html>
> https://kafka.apache.org/contact <https://kafka.apache.org/contact>
>
> But not on:
> https://hive.apache.org/mailing_lists.html <
> https://hive.apache.org/mailing_lists.html>
> https://oozie.apache.org/mail-lists.html <
> https://oozie.apache.org/mail-lists.html>
>
> Regards,
> Andor
>
>
>
> > On 2019. May 13., at 16:43, Patrick Hunt  wrote:
> >
> > I seem to remember that in the early days of apache the intent was for
> all
> > developers to participate in development of the project. MLs were used
> for
> > this initially and there has been concern in the past about the move to
> > JIRA as it removes critical discussions from the general dev flow. JIRA
> > discussions are cc'd to an ML for just this reason. Granted another
> aspect
> > of this mirroring is for archival purposes.
> >
> > As such the intent is for developers to participate in development
> > discussion. It sounds like you're turning this on it's head.
> >
> > Isn't this why we have a user list? For folks that are only casually
> > interested in project activity?
> >
> > Patrick
> >
> > On Mon, May 13, 2019 at 3:31 AM Andor Molnar  wrote:
> >
> >> Hi,
> >>
> >> Sorry for starting the vote too early, for some reason I thought it’s a
> >> straightforward thing, but the concerns are valid.
> >>
> >> I believe this is a good thing to do now, because the activity in
> >> ZooKeeper community has reached a level which the dev list with all
> >> notifications included hasn’t been prepared for. I see emails every now
> and
> >> then from people who fed up with the flood of notification emails and
> >> decide to unsubscribe instead of taking the hassle of dealing with email
> >> filters.
> >>
> >> *Filters*
> >> Pretty much everything which can be done with separate mailing lists,
> can
> >> be achieved by some clever email filters too. Though I think having
> >> multiple mailing lists is technologically a better distinction for
> emails:
> >> separate archives, different retention policies, less email to be
> delivered
> >> (filters working on client side) and more convenient for new
> subscribers.
> >>
> >> *Markmail*
> >> I’m a power user of markmail too, but I’m not sure how it works. Tbh I
> >> cannot see the benefits of searching for automated emails from Gitbox,
> but
> >> I’m sure we can set it up properly, if needed.
> >>
> >> *Existing users*
> >> It’s completely valid that on the flip side we’ll mess up the config of
> >> existing users. I don’t we can avoid that or do this in a backward
> >> compatible way, but I think it’s worth to pay this price. What will
> happen
> >> to them?
> >> - Stop receiving emails from Jira and Github,
> >> - Get the announcement on the dev list: hey, from now on you need to
> >> subscribe from a...@zk.org if you want to be notified about A and 
> >> b...@zk.org
> >> if you want to be notified about B, etc.
> >> I don’t think we can automatically subscribe them for the new lists, it
> >> sounds like against the law (GDPR?), but I’m not a lawyer.
> >>
> >> My 2 cents.
> >>
> >> Regards,
> >> Andor
> >>
> >>
> >>
> >>> On 2019. May 13., at 9:25, Norbert Kalmar  >
> >> wrote:
> >>>
> >>> Well, +1 (non-binding) from my side (if it wasn't clear from my email
> ).
> >>> I agree that anyone following the dev list will have a chance to
> sign-up
> >>> for the new lis

Re: Github & Jira notifications

[Lars Francke]

re: existing users
I'd expect they read this mailing list, and if they do they should see the
announcement that things change and need to re-subscribe, if they don't
follow the list anyway then...well nothing really lost.
I understand the concern but I'm afraid there's nothing we can do there. I
don't think it's trivial to automatically subscribe people to a new list,
we'd need to ask INFRA if it's even possible.

re: new users: Yes, as a new subscriber it's definitely VERY overwhelming
(especially the gitbox mails) and it's also nowadays almost unexpected
because most other projects (at least the ones I follow) have the
separation of mailing lists already

On Sun, May 12, 2019 at 6:28 PM Norbert Kalmar 
wrote:

> I agree we have a lot of "noise", as others, I have created the filters and
> since forgot about them.
> But it is overwhelming for a new subscriber, and filters always carry the
> dangers of false positive filtering. i.e. filter out someone's email.
> I think someone joining the dev-zookeeper mailing list is always a good
> thing, and we shouldn't scare them away :)
> For the existing users, I guess they would have to sign up for the new
> list.
>
> It would be nice, but I'm not even sure of all the dependent stuff (Patrick
> just mentioned marmail for example).
>
> Regards,
> Norbert
>
> On Sun, May 12, 2019 at 10:06 AM Lars Francke 
> wrote:
>
> > Sorry, I didn't mean to comment on the tracking sites in the VOTE thread.
> > That belongs here.
> >
> > Either way: Markmail etc. shouldn't be broken. Yes, they may take a while
> > before they index stuff but the "canonical" tracking site is
> > https://lists.apache.org and that indexes new stuff automatically
> anwyay.
> >
> > On Sun, May 12, 2019 at 9:55 AM Lars Francke 
> > wrote:
> >
> > > I'm subscribed to around 40-60 Apache Mailing lists. If the
> notifications
> > > were in a separate list I could just subscribe to what I want instead
> of
> > > creating 80 or so filters.
> > >
> > > I think I disagree, I don't have to create filters if the dev list only
> > > contains "discussions".
> > >
> > > Cheers,
> > > Lars
> > >
> > > On Sun, May 12, 2019 at 12:38 AM Patrick Hunt 
> wrote:
> > >
> > >> You're going to have to have a filter regardless. Why change now?
> Also,
> > if
> > >> you do change it, be sure to update all of the tracking sites such as
> > >> markmail (etc...), I find this invaluable.
> > >>
> > >> Regards,
> > >>
> > >> Patrick
> > >>
> > >> On Fri, May 10, 2019 at 1:18 AM Lars Francke 
> > >> wrote:
> > >>
> > >> > INFRA can do it all :)
> > >> >
> > >> > See for example this:
> > >> > <https://issues.apache.org/jira/browse/INFRA-17915> for Jira
> > >> > <https://issues.apache.org/jira/browse/INFRA-18296> for Github
> > >> >
> > >> > The necessary mailing lists can be created here <
> > >> > https://selfserve.apache.org/>
> > >> >
> > >> > I'd be happy to file the issues myself but it's better if it comes
> > from
> > >> a
> > >> > PMC member.
> > >> >
> > >> > Cheers,
> > >> > Lars
> > >> >
> > >> > On Fri, May 10, 2019 at 10:00 AM Andor Molnar
> > >> 
> > >> > wrote:
> > >> >
> > >> > > Hi Lars,
> > >> > >
> > >> > > Thank you for the hands, yes, indeed we are interested!
> > >> > > Currently I'm using all kind of magic filters to separate signal
> > from
> > >> > > noise.
> > >> > >
> > >> > > What do we need to do?
> > >> > >
> > >> > > Regards,
> > >> > > Andor
> > >> > >
> > >> > >
> > >> > >
> > >> > > On Fri, May 10, 2019 at 9:51 AM Lars Francke <
> > lars.fran...@gmail.com>
> > >> > > wrote:
> > >> > >
> > >> > > > Hi,
> > >> > > >
> > >> > > > I've recently subscribed to the dev mailinglist but am
> overwhelmed
> > >> by
> > >> > the
> > >> > > > number of github notifications and about to unsubscribe again.
> > >> > > >
> > >> > > > But maybe you're interested in moving the github & jira
> > >> notifications
> > >> > to
> > >> > > a
> > >> > > > different mailing list? I did a quick search for on the mailing
> > list
> > >> > > > archives but couldn't find another thread about it.
> > >> > > >
> > >> > > > The way we've done it at the Apache Training project now for
> > >> example is
> > >> > > to
> > >> > > > send all Github notifications to notifications@ and all Jira
> > >> messages
> > >> > to
> > >> > > > issues@ we only send Jira open and close mails to dev@
> > >> > > >
> > >> > > > This lowers the volume significantly and works just fine.
> > >> > > >
> > >> > > > Is this something you'd be interested in?
> > >> > > >
> > >> > > > Cheers,
> > >> > > > Lars
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >
> >
>

Re: Github & Jira notifications

[Lars Francke]

Sorry, I didn't mean to comment on the tracking sites in the VOTE thread.
That belongs here.

Either way: Markmail etc. shouldn't be broken. Yes, they may take a while
before they index stuff but the "canonical" tracking site is
https://lists.apache.org and that indexes new stuff automatically anwyay.

On Sun, May 12, 2019 at 9:55 AM Lars Francke  wrote:

> I'm subscribed to around 40-60 Apache Mailing lists. If the notifications
> were in a separate list I could just subscribe to what I want instead of
> creating 80 or so filters.
>
> I think I disagree, I don't have to create filters if the dev list only
> contains "discussions".
>
> Cheers,
> Lars
>
> On Sun, May 12, 2019 at 12:38 AM Patrick Hunt  wrote:
>
>> You're going to have to have a filter regardless. Why change now? Also, if
>> you do change it, be sure to update all of the tracking sites such as
>> markmail (etc...), I find this invaluable.
>>
>> Regards,
>>
>> Patrick
>>
>> On Fri, May 10, 2019 at 1:18 AM Lars Francke 
>> wrote:
>>
>> > INFRA can do it all :)
>> >
>> > See for example this:
>> > <https://issues.apache.org/jira/browse/INFRA-17915> for Jira
>> > <https://issues.apache.org/jira/browse/INFRA-18296> for Github
>> >
>> > The necessary mailing lists can be created here <
>> > https://selfserve.apache.org/>
>> >
>> > I'd be happy to file the issues myself but it's better if it comes from
>> a
>> > PMC member.
>> >
>> > Cheers,
>> > Lars
>> >
>> > On Fri, May 10, 2019 at 10:00 AM Andor Molnar
>> 
>> > wrote:
>> >
>> > > Hi Lars,
>> > >
>> > > Thank you for the hands, yes, indeed we are interested!
>> > > Currently I'm using all kind of magic filters to separate signal from
>> > > noise.
>> > >
>> > > What do we need to do?
>> > >
>> > > Regards,
>> > > Andor
>> > >
>> > >
>> > >
>> > > On Fri, May 10, 2019 at 9:51 AM Lars Francke 
>> > > wrote:
>> > >
>> > > > Hi,
>> > > >
>> > > > I've recently subscribed to the dev mailinglist but am overwhelmed
>> by
>> > the
>> > > > number of github notifications and about to unsubscribe again.
>> > > >
>> > > > But maybe you're interested in moving the github & jira
>> notifications
>> > to
>> > > a
>> > > > different mailing list? I did a quick search for on the mailing list
>> > > > archives but couldn't find another thread about it.
>> > > >
>> > > > The way we've done it at the Apache Training project now for
>> example is
>> > > to
>> > > > send all Github notifications to notifications@ and all Jira
>> messages
>> > to
>> > > > issues@ we only send Jira open and close mails to dev@
>> > > >
>> > > > This lowers the volume significantly and works just fine.
>> > > >
>> > > > Is this something you'd be interested in?
>> > > >
>> > > > Cheers,
>> > > > Lars
>> > > >
>> > >
>> >
>>
>

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications

[Lars Francke]

Why does it break tracking sites? They index the ASF stuff automatically as
far as I know.

On Sun, May 12, 2019 at 12:40 AM Patrick Hunt  wrote:

> -1 - I don't see the benefit. EOD it's a filter. Why change now?
>
> Also it will break all the tracking sites such as markmail, which I find
> invaluable when providing feedback to people or trying to look something
> up.
>
> Patrick
>
>
> On Fri, May 10, 2019 at 7:38 AM Lars Francke 
> wrote:
>
> > +1 non-binding.
> >
> > Thank you!
> >
> > On Fri, May 10, 2019, 12:48 Enrico Olivelli  wrote:
> >
> > > +1 (non binding)
> > >
> > > Enrico
> > >
> > > Il giorno ven 10 mag 2019 alle ore 12:41 Andor Molnar <
> an...@apache.org>
> > > ha
> > > scritto:
> > >
> > > > Hi dev team,
> > > >
> > > > Based on Lars' suggestions I propose the following email notification
> > > > scheme for ZooKeeper:
> > > > (same as HBase setup)
> > > >
> > > > Jira
> > > > 
> > > > Issue created -> dev@zookeeper.apache.org + issues@
> > > > Everything else -> iss...@zookeeper.apache.org
> > > >
> > > > Github/Gitbox
> > > > --
> > > > All notifications sent to notificati...@zookeeper.apache.org
> > > >
> > > > issues@ and notifications@ mailing lists have to be created first.
> > > >
> > > > Please vote on the suggestion.
> > > >
> > > > Andor
> > > >
> > >
> >
>

Re: Github & Jira notifications

[Lars Francke]

I'm subscribed to around 40-60 Apache Mailing lists. If the notifications
were in a separate list I could just subscribe to what I want instead of
creating 80 or so filters.

I think I disagree, I don't have to create filters if the dev list only
contains "discussions".

Cheers,
Lars

On Sun, May 12, 2019 at 12:38 AM Patrick Hunt  wrote:

> You're going to have to have a filter regardless. Why change now? Also, if
> you do change it, be sure to update all of the tracking sites such as
> markmail (etc...), I find this invaluable.
>
> Regards,
>
> Patrick
>
> On Fri, May 10, 2019 at 1:18 AM Lars Francke 
> wrote:
>
> > INFRA can do it all :)
> >
> > See for example this:
> > <https://issues.apache.org/jira/browse/INFRA-17915> for Jira
> > <https://issues.apache.org/jira/browse/INFRA-18296> for Github
> >
> > The necessary mailing lists can be created here <
> > https://selfserve.apache.org/>
> >
> > I'd be happy to file the issues myself but it's better if it comes from a
> > PMC member.
> >
> > Cheers,
> > Lars
> >
> > On Fri, May 10, 2019 at 10:00 AM Andor Molnar  >
> > wrote:
> >
> > > Hi Lars,
> > >
> > > Thank you for the hands, yes, indeed we are interested!
> > > Currently I'm using all kind of magic filters to separate signal from
> > > noise.
> > >
> > > What do we need to do?
> > >
> > > Regards,
> > > Andor
> > >
> > >
> > >
> > > On Fri, May 10, 2019 at 9:51 AM Lars Francke 
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I've recently subscribed to the dev mailinglist but am overwhelmed by
> > the
> > > > number of github notifications and about to unsubscribe again.
> > > >
> > > > But maybe you're interested in moving the github & jira notifications
> > to
> > > a
> > > > different mailing list? I did a quick search for on the mailing list
> > > > archives but couldn't find another thread about it.
> > > >
> > > > The way we've done it at the Apache Training project now for example
> is
> > > to
> > > > send all Github notifications to notifications@ and all Jira
> messages
> > to
> > > > issues@ we only send Jira open and close mails to dev@
> > > >
> > > > This lowers the volume significantly and works just fine.
> > > >
> > > > Is this something you'd be interested in?
> > > >
> > > > Cheers,
> > > > Lars
> > > >
> > >
> >
>

Re: [VOTE] Separate mailing lists for Jira and Github/Gitbox notifications

[Lars Francke]

+1 non-binding.

Thank you!

On Fri, May 10, 2019, 12:48 Enrico Olivelli  wrote:

> +1 (non binding)
>
> Enrico
>
> Il giorno ven 10 mag 2019 alle ore 12:41 Andor Molnar 
> ha
> scritto:
>
> > Hi dev team,
> >
> > Based on Lars' suggestions I propose the following email notification
> > scheme for ZooKeeper:
> > (same as HBase setup)
> >
> > Jira
> > 
> > Issue created -> dev@zookeeper.apache.org + issues@
> > Everything else -> iss...@zookeeper.apache.org
> >
> > Github/Gitbox
> > --
> > All notifications sent to notificati...@zookeeper.apache.org
> >
> > issues@ and notifications@ mailing lists have to be created first.
> >
> > Please vote on the suggestion.
> >
> > Andor
> >
>

Re: Github & Jira notifications

[Lars Francke]

INFRA can do it all :)

See for example this:
<https://issues.apache.org/jira/browse/INFRA-17915> for Jira
<https://issues.apache.org/jira/browse/INFRA-18296> for Github

The necessary mailing lists can be created here <
https://selfserve.apache.org/>

I'd be happy to file the issues myself but it's better if it comes from a
PMC member.

Cheers,
Lars

On Fri, May 10, 2019 at 10:00 AM Andor Molnar 
wrote:

> Hi Lars,
>
> Thank you for the hands, yes, indeed we are interested!
> Currently I'm using all kind of magic filters to separate signal from
> noise.
>
> What do we need to do?
>
> Regards,
> Andor
>
>
>
> On Fri, May 10, 2019 at 9:51 AM Lars Francke 
> wrote:
>
> > Hi,
> >
> > I've recently subscribed to the dev mailinglist but am overwhelmed by the
> > number of github notifications and about to unsubscribe again.
> >
> > But maybe you're interested in moving the github & jira notifications to
> a
> > different mailing list? I did a quick search for on the mailing list
> > archives but couldn't find another thread about it.
> >
> > The way we've done it at the Apache Training project now for example is
> to
> > send all Github notifications to notifications@ and all Jira messages to
> > issues@ we only send Jira open and close mails to dev@
> >
> > This lowers the volume significantly and works just fine.
> >
> > Is this something you'd be interested in?
> >
> > Cheers,
> > Lars
> >
>

Github & Jira notifications

[Lars Francke]

Hi,

I've recently subscribed to the dev mailinglist but am overwhelmed by the
number of github notifications and about to unsubscribe again.

But maybe you're interested in moving the github & jira notifications to a
different mailing list? I did a quick search for on the mailing list
archives but couldn't find another thread about it.

The way we've done it at the Apache Training project now for example is to
send all Github notifications to notifications@ and all Jira messages to
issues@ we only send Jira open and close mails to dev@

This lowers the volume significantly and works just fine.

Is this something you'd be interested in?

Cheers,
Lars

Re: Request for review & contribution of Apache Training

[Lars Francke]

Thank you!

On Sat, Apr 27, 2019 at 5:10 PM Flavio Junqueira  wrote:

> This is great, Lars. Thanks for putting this together. I have some
> additional comments:
>
> - I'd rather not characterize zookeeper as a key-value store, one reason
> being that to access a znode we give a "path" and not a "key". I don't want
> to open this up to a discussion on what a key-value store actually is, but
> I typically say that it is a hierarchy of znodes and explain what a znode
> is (Slide 2). If it is early to talk about znodes, then say hierarchy of
> simple data files.
>

I've changed it to "data store"


> - It would be nice to have a slide illustrating how to get going with
> zookeeper, like starting a server with `bin/zkServer.sh start` and using
> the `bin/zkCli.sh` to issue some commands.
>

Good idea, I've put it in the todo list for now though


> - In Slide 8, the statement saying that "in an ensemble we always have a
> single leader" isn't accurate. I think you want to say something along the
> lines of "in an ensemble there is at most on leader server supported by a
> majority of followers".
>

I've changed this to your suggestion


>
> Thanks again for the initiative.
>

Thanks for the review! I've uploaded a new version at the same URL

Let me know if you can think of anything else.

Lars


>
> -Flavio
>
> > On 27 Apr 2019, at 00:55, Lars Francke  wrote:
> >
> > Thank you Patrick, that's great!
> >
> > I've incorporated the feedback (and a bit more) and have uploaded a new
> > version.
> >
> > This is just a first start and I hope that over time the community will
> > expand on it (e.g. slides on use cases/patterns/recipes, API usage, the
> Zab
> > protocol, etc.). This is also an invitation to the ZooKeeper community to
> > add anything at any point if you feel it's worthwhile to teach to
> potential
> > learners. If you don't want to fiddle around with slides that's fine as
> > well, just filing an issue in Jira in the TRAINING project will already
> > help.
> >
> > Cheers,
> > Lars
> >
> > On Fri, Apr 26, 2019 at 10:49 PM Patrick Hunt  wrote:
> >
> >> Wow, this is great, thanks Lars. I reviewed, here are my comments:
> >>
> >> 3: you might highlight that it's used outside hadoop (e.g. solr and many
> >> others inside and outside apache). Also heavily using in the tech
> industry;
> >> facebook, twitter, linkedin, etc...
> >>
> >> You might also reference Curator as it's a good way to get started from
> a
> >> client perspective.
> >>
> >> Regards,
> >>
> >> Patrick
> >>
> >> On Fri, Apr 26, 2019 at 7:20 AM Lars Francke 
> >> wrote:
> >>
> >>> Hi ZooKeeper devs,
> >>>
> >>> we started the Apache Training (incubating) project back in February.
> >>> Our aim is to develop training material (slides, labs, tests etc.) for
> all
> >>> kinds of projects (mostly focusing on Apache projects but not
> >>> exclusively).
> >>>
> >>> We're still getting off the ground with homepage and so. We're also
> >>> working
> >>> on the very first content donation which is a super simple four slide
> >>> ZooKeeper introduction.
> >>>
> >>> I chose this because it's small and we can test our processes.
> >>>
> >>> I still wanted to reach out and see if anyone here is interested in
> >>> contributing anything and/or reviewing the existing material. It can be
> >>> found in Jira: <https://issues.apache.org/jira/browse/TRAINING-13>
> >>>
> >>> Thank you very much!
> >>>
> >>> Cheers,
> >>> Lars
> >>>
> >>
>
>

Re: Request for review & contribution of Apache Training

[Lars Francke]

Thank you Patrick, that's great!

I've incorporated the feedback (and a bit more) and have uploaded a new
version.

This is just a first start and I hope that over time the community will
expand on it (e.g. slides on use cases/patterns/recipes, API usage, the Zab
protocol, etc.). This is also an invitation to the ZooKeeper community to
add anything at any point if you feel it's worthwhile to teach to potential
learners. If you don't want to fiddle around with slides that's fine as
well, just filing an issue in Jira in the TRAINING project will already
help.

Cheers,
Lars

On Fri, Apr 26, 2019 at 10:49 PM Patrick Hunt  wrote:

> Wow, this is great, thanks Lars. I reviewed, here are my comments:
>
> 3: you might highlight that it's used outside hadoop (e.g. solr and many
> others inside and outside apache). Also heavily using in the tech industry;
> facebook, twitter, linkedin, etc...
>
> You might also reference Curator as it's a good way to get started from a
> client perspective.
>
> Regards,
>
> Patrick
>
> On Fri, Apr 26, 2019 at 7:20 AM Lars Francke 
> wrote:
>
>> Hi ZooKeeper devs,
>>
>> we started the Apache Training (incubating) project back in February.
>> Our aim is to develop training material (slides, labs, tests etc.) for all
>> kinds of projects (mostly focusing on Apache projects but not
>> exclusively).
>>
>> We're still getting off the ground with homepage and so. We're also
>> working
>> on the very first content donation which is a super simple four slide
>> ZooKeeper introduction.
>>
>> I chose this because it's small and we can test our processes.
>>
>> I still wanted to reach out and see if anyone here is interested in
>> contributing anything and/or reviewing the existing material. It can be
>> found in Jira: <https://issues.apache.org/jira/browse/TRAINING-13>
>>
>> Thank you very much!
>>
>> Cheers,
>> Lars
>>
>

Request for review & contribution of Apache Training

[Lars Francke]

Hi ZooKeeper devs,

we started the Apache Training (incubating) project back in February.
Our aim is to develop training material (slides, labs, tests etc.) for all
kinds of projects (mostly focusing on Apache projects but not exclusively).

We're still getting off the ground with homepage and so. We're also working
on the very first content donation which is a super simple four slide
ZooKeeper introduction.

I chose this because it's small and we can test our processes.

I still wanted to reach out and see if anyone here is interested in
contributing anything and/or reviewing the existing material. It can be
found in Jira: 

Thank you very much!

Cheers,
Lars