Pull request [apache/mesos] Added jvanz as contributor.

[mesosprbot]

Added jvanz as contributor.
By jvanz 
The contributors.yaml has been updated adding myself as contributor
June 24, 2016 at 07:59PM
via GitHub https://github.com/apache/mesos/pull/114

Re: Slack as the canonical chat channel

[Vinod Kone]

Anyone can self-invite now by going here:
https://mesos-slackin.herokuapp.com/

Happy Friday!

P.S: Right now the invites come from my apache.org email address. Need to
figure out how to make them come from a generic (e.g., dev@mesos.apache.org)
email address.

On Fri, Jun 24, 2016 at 11:42 AM, Vinod Kone  wrote:

> Yup. It is linked in the channel description.
> http://mesos.slackarchive.io/
>
> On Fri, Jun 24, 2016 at 11:36 AM, James Peach  wrote:
>
>> Are there public archives of the slack channel
>>
>> > On Jun 24, 2016, at 10:31 AM, Vinod Kone  wrote:
>> >
>> > The plan is to open them up to all. Currently, slack has a limitation
>> that
>> > either users have to be invited individually (which doesn't scale) or
>> they
>> > need to belong to manually created white-list of corporate domains
>> (which
>> > doesn't scale either).
>> >
>> > I'm looking into using 3rd party tools like
>> > https://github.com/rauchg/slackin to let anyone signup.
>> >
>> > On Fri, Jun 24, 2016 at 9:28 AM, Vaibhav Khanduja <
>> vaibhavkhand...@gmail.com
>> >> wrote:
>> >
>> >> We should atleast  open this to contributors or who has access to
>> assign
>> >> issue to them ...
>> >>
>> >>
>> >>
>> >>> On 6/23/16, 10:50 PM, "Vinod Kone"  wrote:
>> >>>
>> >>> Opened it up for few more domain names (ibm, apple etc). If your
>> domain is
>> >>> listed at https://mesos.slack.com/signup please feel free to join.
>> >>>
>>  On Thu, Jun 23, 2016 at 7:07 PM, tommy xiao 
>> wrote:
>> 
>>  because the mesos repo is not hosted on github.  gitter.im is not
>> best
>>  option on team. slack is popular than gitter.im. so i suggest based
>> on
>>  slack.
>> 
>>  2016-06-24 8:11 GMT+08:00 Jay JN Guo :
>> 
>> > Great, thanks for your effort! We'd love to see it's opening up
>> soon!
>> >
>> > /J
>> >
>> > Vinod Kone  wrote on 06/24/2016 00:36:44:
>> >
>> >> From: Vinod Kone 
>> >> To: dev 
>> >> Cc: Benjamin Hindman , Jake Farrell
>> > 
>> >> Date: 06/24/2016 00:37
>> >> Subject: Re: Slack as the canonical chat channel
>> >>
>> >> Looks like there is an overwhelming majority for *slack*! So, I
>> went
>> > ahead
>> >> and created a slack team https://mesos.slack.com.
>> >>
>> >> For now, you can signup if you have a "*apache.org <
>> >> http://apache.org
>> > *"
>> >> email address (https://mesos.slack.com/signup). I'll start slowly
>> > opening
>> >> it up for more people as we get our feet wet and iron out any
>> >> kinks. So
>> >> everyone should still keep using #mesos IRC channel.
>> >>
>> >> Thanks,
>> >> Vinod
>> >>
>> >> On Tue, Jun 21, 2016 at 9:42 AM, José Guilherme Vanz <
>> >> guilherme@gmail.com> wrote:
>> >>
>> >>> Yeah, sound as a good option.
>> >>>
>> >>> On Mon, 20 Jun 2016 at 20:04 Cosmin Lehene 
>>  wrote:
>> >>>
>>  Looks like there's a majority of +1 for Slack, so this this may
>> >> be
>>  pointless, however :), have you considered gitter.im (
>>  https://gitter.im/home/explore/)?
>> 
>> 
>>  It has similar capabilities to Slack, but it's (unlimited) free
>> >> for
>> > open
>>  source projects and seamlessly works over Github organizations
>> >> and
>> > repos
>>  with several major open source projects using it.
>> 
>> 
>>  Cheers,
>> 
>>  Cosmin
>> 
>>  
>>  From: haosdent 
>>  Sent: Friday, June 17, 2016 6:48:02 PM
>>  To: dev
>>  Cc: Benjamin Hindman; Jake Farrell
>>  Subject: Re: Slack as the canonical chat channel
>> 
>>  +1 For Slack
>>  On Jun 18, 2016 4:04 AM, "Vinod Kone" 
>>  wrote:
>> 
>> > Looks like people have jumped the gun here before I sent the
>> > email :)
>> >
>> > Here is the context. During the community sync we discussed
>> >> about
>> > using
>> > *Slack* or *HipChat* as our official chat channel instead of
>> >> our
>> >>> current
>> > #mesos IRC channel on freenode.
>> >
>> > The main reasons for using Slack/Hipchat are
>> >
>> >   - In-client chat history
>> >   - Discoverability of work group specific channels
>> >   - Email notifications when offline
>> >   - Modern UX and clients
>> >
>> > During the sync most people preferred the move to *Slack*. I
>>  wanted
>> > to
>>  get
>> > a sense from other community members as well through this
>> >> email.
>> > Please
>>  let
>> > us know what you think.
>> >
>> > Note that even if we move to Slack, we will make sure people
>> >> can
>> > still
>> > connect using IRC clients and that the chat history is
>> >> publicly
>> >>> available
>> >

Canonical contributors list

[Vinod Kone]

Hi,

As discussed in the previous community sync, we would like to start storing
a canonical list of contributors to the project.

The main goal is to constantly measure how we are growing and improving as
a community. For example, we want to track what % of reviews getting
committed are from a given organization, so that we can become better
diversified.

As such, we committed a new
https://github.com/apache/mesos/blob/master/docs/contributors.yaml (thanks
artem!) and seeded it with some contributors that we know about.

I*f you are contributor, please send a PR or review to add yourself to this
file*. Feel free to omit any fields that you are not comfortable publicly
sharing (e.g., affiliation, start/end dates etc).

Thanks,
Vinod

Re: Slack as the canonical chat channel

[James Peach]

Are there public archives of the slack channel 

> On Jun 24, 2016, at 10:31 AM, Vinod Kone  wrote:
> 
> The plan is to open them up to all. Currently, slack has a limitation that
> either users have to be invited individually (which doesn't scale) or they
> need to belong to manually created white-list of corporate domains (which
> doesn't scale either).
> 
> I'm looking into using 3rd party tools like
> https://github.com/rauchg/slackin to let anyone signup.
> 
> On Fri, Jun 24, 2016 at 9:28 AM, Vaibhav Khanduja > wrote:
> 
>> We should atleast  open this to contributors or who has access to assign
>> issue to them ...
>> 
>> 
>> 
>>> On 6/23/16, 10:50 PM, "Vinod Kone"  wrote:
>>> 
>>> Opened it up for few more domain names (ibm, apple etc). If your domain is
>>> listed at https://mesos.slack.com/signup please feel free to join.
>>> 
 On Thu, Jun 23, 2016 at 7:07 PM, tommy xiao  wrote:
 
 because the mesos repo is not hosted on github.  gitter.im is not best
 option on team. slack is popular than gitter.im. so i suggest based on
 slack.
 
 2016-06-24 8:11 GMT+08:00 Jay JN Guo :
 
> Great, thanks for your effort! We'd love to see it's opening up soon!
> 
> /J
> 
> Vinod Kone  wrote on 06/24/2016 00:36:44:
> 
>> From: Vinod Kone 
>> To: dev 
>> Cc: Benjamin Hindman , Jake Farrell
> 
>> Date: 06/24/2016 00:37
>> Subject: Re: Slack as the canonical chat channel
>> 
>> Looks like there is an overwhelming majority for *slack*! So, I went
> ahead
>> and created a slack team https://mesos.slack.com.
>> 
>> For now, you can signup if you have a "*apache.org <
>> http://apache.org
> *"
>> email address (https://mesos.slack.com/signup). I'll start slowly
> opening
>> it up for more people as we get our feet wet and iron out any
>> kinks. So
>> everyone should still keep using #mesos IRC channel.
>> 
>> Thanks,
>> Vinod
>> 
>> On Tue, Jun 21, 2016 at 9:42 AM, José Guilherme Vanz <
>> guilherme@gmail.com> wrote:
>> 
>>> Yeah, sound as a good option.
>>> 
>>> On Mon, 20 Jun 2016 at 20:04 Cosmin Lehene 
 wrote:
>>> 
 Looks like there's a majority of +1 for Slack, so this this may
>> be
 pointless, however :), have you considered gitter.im (
 https://gitter.im/home/explore/)?
 
 
 It has similar capabilities to Slack, but it's (unlimited) free
>> for
> open
 source projects and seamlessly works over Github organizations
>> and
> repos
 with several major open source projects using it.
 
 
 Cheers,
 
 Cosmin
 
 
 From: haosdent 
 Sent: Friday, June 17, 2016 6:48:02 PM
 To: dev
 Cc: Benjamin Hindman; Jake Farrell
 Subject: Re: Slack as the canonical chat channel
 
 +1 For Slack
 On Jun 18, 2016 4:04 AM, "Vinod Kone" 
 wrote:
 
> Looks like people have jumped the gun here before I sent the
> email :)
> 
> Here is the context. During the community sync we discussed
>> about
> using
> *Slack* or *HipChat* as our official chat channel instead of
>> our
>>> current
> #mesos IRC channel on freenode.
> 
> The main reasons for using Slack/Hipchat are
> 
>   - In-client chat history
>   - Discoverability of work group specific channels
>   - Email notifications when offline
>   - Modern UX and clients
> 
> During the sync most people preferred the move to *Slack*. I
 wanted
> to
 get
> a sense from other community members as well through this
>> email.
> Please
 let
> us know what you think.
> 
> Note that even if we move to Slack, we will make sure people
>> can
> still
> connect using IRC clients and that the chat history is
>> publicly
>>> available
> (per ASF guidelines). During the transition period, we might
 mirror
> messages from Slack channel to IRC and vice-versa.
> 
> Thoughts?
> 
> On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia
> >>> 
> wrote:
> 
>> +1 Slack.
>> 
>> On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo
> 
>> wrote:
>> 
>>> +1 Slack!
>>> 
>>> /J
>>> 
>>> Vaibhav Khanduja  wrote on
> 06/16/2016
>> 22:26:27:
>>> 
 From: Vaibhav Khanduja 
 To: dev@mesos.apache.org
 Date: 06/16/2016 22:26
 Subject: Re: Notification: Community Meeting @ Thu Jun
>> 16,
> 2016
>>> 3pm
 - 4pm (Apache Mesos)
 
 + 1 slack
 
 Sent from my iPhone. Pl

Re: Slack as the canonical chat channel

[Vinod Kone]

Yup. It is linked in the channel description. http://mesos.slackarchive.io/

On Fri, Jun 24, 2016 at 11:36 AM, James Peach  wrote:

> Are there public archives of the slack channel
>
> > On Jun 24, 2016, at 10:31 AM, Vinod Kone  wrote:
> >
> > The plan is to open them up to all. Currently, slack has a limitation
> that
> > either users have to be invited individually (which doesn't scale) or
> they
> > need to belong to manually created white-list of corporate domains (which
> > doesn't scale either).
> >
> > I'm looking into using 3rd party tools like
> > https://github.com/rauchg/slackin to let anyone signup.
> >
> > On Fri, Jun 24, 2016 at 9:28 AM, Vaibhav Khanduja <
> vaibhavkhand...@gmail.com
> >> wrote:
> >
> >> We should atleast  open this to contributors or who has access to assign
> >> issue to them ...
> >>
> >>
> >>
> >>> On 6/23/16, 10:50 PM, "Vinod Kone"  wrote:
> >>>
> >>> Opened it up for few more domain names (ibm, apple etc). If your
> domain is
> >>> listed at https://mesos.slack.com/signup please feel free to join.
> >>>
>  On Thu, Jun 23, 2016 at 7:07 PM, tommy xiao  wrote:
> 
>  because the mesos repo is not hosted on github.  gitter.im is not
> best
>  option on team. slack is popular than gitter.im. so i suggest based
> on
>  slack.
> 
>  2016-06-24 8:11 GMT+08:00 Jay JN Guo :
> 
> > Great, thanks for your effort! We'd love to see it's opening up soon!
> >
> > /J
> >
> > Vinod Kone  wrote on 06/24/2016 00:36:44:
> >
> >> From: Vinod Kone 
> >> To: dev 
> >> Cc: Benjamin Hindman , Jake Farrell
> > 
> >> Date: 06/24/2016 00:37
> >> Subject: Re: Slack as the canonical chat channel
> >>
> >> Looks like there is an overwhelming majority for *slack*! So, I went
> > ahead
> >> and created a slack team https://mesos.slack.com.
> >>
> >> For now, you can signup if you have a "*apache.org <
> >> http://apache.org
> > *"
> >> email address (https://mesos.slack.com/signup). I'll start slowly
> > opening
> >> it up for more people as we get our feet wet and iron out any
> >> kinks. So
> >> everyone should still keep using #mesos IRC channel.
> >>
> >> Thanks,
> >> Vinod
> >>
> >> On Tue, Jun 21, 2016 at 9:42 AM, José Guilherme Vanz <
> >> guilherme@gmail.com> wrote:
> >>
> >>> Yeah, sound as a good option.
> >>>
> >>> On Mon, 20 Jun 2016 at 20:04 Cosmin Lehene 
>  wrote:
> >>>
>  Looks like there's a majority of +1 for Slack, so this this may
> >> be
>  pointless, however :), have you considered gitter.im (
>  https://gitter.im/home/explore/)?
> 
> 
>  It has similar capabilities to Slack, but it's (unlimited) free
> >> for
> > open
>  source projects and seamlessly works over Github organizations
> >> and
> > repos
>  with several major open source projects using it.
> 
> 
>  Cheers,
> 
>  Cosmin
> 
>  
>  From: haosdent 
>  Sent: Friday, June 17, 2016 6:48:02 PM
>  To: dev
>  Cc: Benjamin Hindman; Jake Farrell
>  Subject: Re: Slack as the canonical chat channel
> 
>  +1 For Slack
>  On Jun 18, 2016 4:04 AM, "Vinod Kone" 
>  wrote:
> 
> > Looks like people have jumped the gun here before I sent the
> > email :)
> >
> > Here is the context. During the community sync we discussed
> >> about
> > using
> > *Slack* or *HipChat* as our official chat channel instead of
> >> our
> >>> current
> > #mesos IRC channel on freenode.
> >
> > The main reasons for using Slack/Hipchat are
> >
> >   - In-client chat history
> >   - Discoverability of work group specific channels
> >   - Email notifications when offline
> >   - Modern UX and clients
> >
> > During the sync most people preferred the move to *Slack*. I
>  wanted
> > to
>  get
> > a sense from other community members as well through this
> >> email.
> > Please
>  let
> > us know what you think.
> >
> > Note that even if we move to Slack, we will make sure people
> >> can
> > still
> > connect using IRC clients and that the chat history is
> >> publicly
> >>> available
> > (per ASF guidelines). During the transition period, we might
>  mirror
> > messages from Slack channel to IRC and vice-versa.
> >
> > Thoughts?
> >
> > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia
> >  
> > wrote:
> >
> >> +1 Slack.
> >>
> >> On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo
> > 
> >> wrote:
> >>
> >>> +1 Slack!
> >>>
> >>>

Re: Slack as the canonical chat channel

[Vaibhav Khanduja]

Thank Vinod for taking this up. 

Sent from my iPhone. Please excuse for typos and brevity of this message.

> On Jun 24, 2016, at 10:31 AM, Vinod Kone  wrote:
> 
> The plan is to open them up to all. Currently, slack has a limitation that
> either users have to be invited individually (which doesn't scale) or they
> need to belong to manually created white-list of corporate domains (which
> doesn't scale either).
> 
> I'm looking into using 3rd party tools like
> https://github.com/rauchg/slackin to let anyone signup.
> 
> On Fri, Jun 24, 2016 at 9:28 AM, Vaibhav Khanduja > wrote:
> 
>> We should atleast  open this to contributors or who has access to assign
>> issue to them ...
>> 
>> 
>> 
>>> On 6/23/16, 10:50 PM, "Vinod Kone"  wrote:
>>> 
>>> Opened it up for few more domain names (ibm, apple etc). If your domain is
>>> listed at https://mesos.slack.com/signup please feel free to join.
>>> 
 On Thu, Jun 23, 2016 at 7:07 PM, tommy xiao  wrote:
 
 because the mesos repo is not hosted on github.  gitter.im is not best
 option on team. slack is popular than gitter.im. so i suggest based on
 slack.
 
 2016-06-24 8:11 GMT+08:00 Jay JN Guo :
 
> Great, thanks for your effort! We'd love to see it's opening up soon!
> 
> /J
> 
> Vinod Kone  wrote on 06/24/2016 00:36:44:
> 
>> From: Vinod Kone 
>> To: dev 
>> Cc: Benjamin Hindman , Jake Farrell
> 
>> Date: 06/24/2016 00:37
>> Subject: Re: Slack as the canonical chat channel
>> 
>> Looks like there is an overwhelming majority for *slack*! So, I went
> ahead
>> and created a slack team https://mesos.slack.com.
>> 
>> For now, you can signup if you have a "*apache.org <
>> http://apache.org
> *"
>> email address (https://mesos.slack.com/signup). I'll start slowly
> opening
>> it up for more people as we get our feet wet and iron out any
>> kinks. So
>> everyone should still keep using #mesos IRC channel.
>> 
>> Thanks,
>> Vinod
>> 
>> On Tue, Jun 21, 2016 at 9:42 AM, José Guilherme Vanz <
>> guilherme@gmail.com> wrote:
>> 
>>> Yeah, sound as a good option.
>>> 
>>> On Mon, 20 Jun 2016 at 20:04 Cosmin Lehene 
 wrote:
>>> 
 Looks like there's a majority of +1 for Slack, so this this may
>> be
 pointless, however :), have you considered gitter.im (
 https://gitter.im/home/explore/)?
 
 
 It has similar capabilities to Slack, but it's (unlimited) free
>> for
> open
 source projects and seamlessly works over Github organizations
>> and
> repos
 with several major open source projects using it.
 
 
 Cheers,
 
 Cosmin
 
 
 From: haosdent 
 Sent: Friday, June 17, 2016 6:48:02 PM
 To: dev
 Cc: Benjamin Hindman; Jake Farrell
 Subject: Re: Slack as the canonical chat channel
 
 +1 For Slack
 On Jun 18, 2016 4:04 AM, "Vinod Kone" 
 wrote:
 
> Looks like people have jumped the gun here before I sent the
> email :)
> 
> Here is the context. During the community sync we discussed
>> about
> using
> *Slack* or *HipChat* as our official chat channel instead of
>> our
>>> current
> #mesos IRC channel on freenode.
> 
> The main reasons for using Slack/Hipchat are
> 
>   - In-client chat history
>   - Discoverability of work group specific channels
>   - Email notifications when offline
>   - Modern UX and clients
> 
> During the sync most people preferred the move to *Slack*. I
 wanted
> to
 get
> a sense from other community members as well through this
>> email.
> Please
 let
> us know what you think.
> 
> Note that even if we move to Slack, we will make sure people
>> can
> still
> connect using IRC clients and that the chat history is
>> publicly
>>> available
> (per ASF guidelines). During the transition period, we might
 mirror
> messages from Slack channel to IRC and vice-versa.
> 
> Thoughts?
> 
> On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia
> >>> 
> wrote:
> 
>> +1 Slack.
>> 
>> On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo
> 
>> wrote:
>> 
>>> +1 Slack!
>>> 
>>> /J
>>> 
>>> Vaibhav Khanduja  wrote on
> 06/16/2016
>> 22:26:27:
>>> 
 From: Vaibhav Khanduja 
 To: dev@mesos.apache.org
 Date: 06/16/2016 22:26
 Subject: Re: Notification: Community Meeting @ Thu Jun
>> 16,
> 2016
>>> 3pm
 - 4pm (Apache Mesos)
 
 

Re: Slack as the canonical chat channel

[Vinod Kone]

The plan is to open them up to all. Currently, slack has a limitation that
either users have to be invited individually (which doesn't scale) or they
need to belong to manually created white-list of corporate domains (which
doesn't scale either).

I'm looking into using 3rd party tools like
https://github.com/rauchg/slackin to let anyone signup.

On Fri, Jun 24, 2016 at 9:28 AM, Vaibhav Khanduja  wrote:

> We should atleast  open this to contributors or who has access to assign
> issue to them ...
>
>
>
> On 6/23/16, 10:50 PM, "Vinod Kone"  wrote:
>
> >Opened it up for few more domain names (ibm, apple etc). If your domain is
> >listed at https://mesos.slack.com/signup please feel free to join.
> >
> >On Thu, Jun 23, 2016 at 7:07 PM, tommy xiao  wrote:
> >
> >> because the mesos repo is not hosted on github.  gitter.im is not best
> >> option on team. slack is popular than gitter.im. so i suggest based on
> >> slack.
> >>
> >> 2016-06-24 8:11 GMT+08:00 Jay JN Guo :
> >>
> >> > Great, thanks for your effort! We'd love to see it's opening up soon!
> >> >
> >> > /J
> >> >
> >> > Vinod Kone  wrote on 06/24/2016 00:36:44:
> >> >
> >> > > From: Vinod Kone 
> >> > > To: dev 
> >> > > Cc: Benjamin Hindman , Jake Farrell
> >> > 
> >> > > Date: 06/24/2016 00:37
> >> > > Subject: Re: Slack as the canonical chat channel
> >> > >
> >> > > Looks like there is an overwhelming majority for *slack*! So, I went
> >> > ahead
> >> > > and created a slack team https://mesos.slack.com.
> >> > >
> >> > > For now, you can signup if you have a "*apache.org <
> http://apache.org
> >> >*"
> >> > > email address (https://mesos.slack.com/signup). I'll start slowly
> >> > opening
> >> > > it up for more people as we get our feet wet and iron out any
> kinks. So
> >> > > everyone should still keep using #mesos IRC channel.
> >> > >
> >> > > Thanks,
> >> > > Vinod
> >> > >
> >> > > On Tue, Jun 21, 2016 at 9:42 AM, José Guilherme Vanz <
> >> > > guilherme@gmail.com> wrote:
> >> > >
> >> > > > Yeah, sound as a good option.
> >> > > >
> >> > > > On Mon, 20 Jun 2016 at 20:04 Cosmin Lehene 
> >> wrote:
> >> > > >
> >> > > > > Looks like there's a majority of +1 for Slack, so this this may
> be
> >> > > > > pointless, however :), have you considered gitter.im (
> >> > > > > https://gitter.im/home/explore/)?
> >> > > > >
> >> > > > >
> >> > > > > It has similar capabilities to Slack, but it's (unlimited) free
> for
> >> > open
> >> > > > > source projects and seamlessly works over Github organizations
> and
> >> > repos
> >> > > > > with several major open source projects using it.
> >> > > > >
> >> > > > >
> >> > > > > Cheers,
> >> > > > >
> >> > > > > Cosmin
> >> > > > >
> >> > > > > 
> >> > > > > From: haosdent 
> >> > > > > Sent: Friday, June 17, 2016 6:48:02 PM
> >> > > > > To: dev
> >> > > > > Cc: Benjamin Hindman; Jake Farrell
> >> > > > > Subject: Re: Slack as the canonical chat channel
> >> > > > >
> >> > > > > +1 For Slack
> >> > > > > On Jun 18, 2016 4:04 AM, "Vinod Kone" 
> >> wrote:
> >> > > > >
> >> > > > > > Looks like people have jumped the gun here before I sent the
> >> > email :)
> >> > > > > >
> >> > > > > > Here is the context. During the community sync we discussed
> about
> >> > using
> >> > > > > > *Slack* or *HipChat* as our official chat channel instead of
> our
> >> > > > current
> >> > > > > > #mesos IRC channel on freenode.
> >> > > > > >
> >> > > > > > The main reasons for using Slack/Hipchat are
> >> > > > > >
> >> > > > > >- In-client chat history
> >> > > > > >- Discoverability of work group specific channels
> >> > > > > >- Email notifications when offline
> >> > > > > >- Modern UX and clients
> >> > > > > >
> >> > > > > > During the sync most people preferred the move to *Slack*. I
> >> wanted
> >> > to
> >> > > > > get
> >> > > > > > a sense from other community members as well through this
> email.
> >> > Please
> >> > > > > let
> >> > > > > > us know what you think.
> >> > > > > >
> >> > > > > > Note that even if we move to Slack, we will make sure people
> can
> >> > still
> >> > > > > > connect using IRC clients and that the chat history is
> publicly
> >> > > > available
> >> > > > > > (per ASF guidelines). During the transition period, we might
> >> mirror
> >> > > > > > messages from Slack channel to IRC and vice-versa.
> >> > > > > >
> >> > > > > > Thoughts?
> >> > > > > >
> >> > > > > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia
> >> >  >> > > > >
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > +1 Slack.
> >> > > > > > >
> >> > > > > > > On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo
> >> > 
> >> > > > > > > wrote:
> >> > > > > > >
> >> > > > > > > > +1 Slack!
> >> > > > > > > >
> >> > > > > > > > /J
> >> > > > > > > >
> >> > > > > > > > Vaibhav Khanduja  wrote on
> >> > 06/16/2016
> >> > > > > > > 22:26:27:
> >> > > > > > > >
> >> > > > > > > > > From: Vaibhav Khanduja 
> >> > > > > > > > > To: dev@mesos.apache.org
> >> > > > > > > > > Date

Re: Mesos CLI

[Artem Harutyunyan]

Having the CLI package outside the Mesos repo will make it very hard for
Mesos developers to verify whether the change that they're introducing
breaks the CLI or not. In practise no one is going to actually do that and
so the CLI will just sit there and slowly degrade. It will also make it
virtually impossible to package it together with Mesos, and someone will
need to maintain a compatibility table between CLI and Mesos versions.

I am also a +1 for python. Users shouldn't care as long as we can package
it as a binary. As for developers, it's naive to expect that there will be
a consensus, both sides have very strong advantages and drawbacks. So we
need to come to a compromise.

I would suggest that Kevin and Haris make a live demo of the functionality
that's already in place during our next community sync. This way everyone
we'll be able to see what they already have, and we collectively will be
able to estimate how long will it actually take us to re-implement all of
that in C++. It would be great to see everyone who has an opinion about
this join the community sync and express it.

Artem.

On Thu, Jun 23, 2016 at 7:40 PM, haosdent  wrote:

> IMO, I perfer to C++ if we decide to put CLI in Mesos repo.
> Because we have a lot of utils in stout and libprocess, I think we could
> reuse most of them when implementing CLI.
> So it would be effective in development as well. If not utils classes and
> functions in stout/libprocess meet our requirements. We could add
> them and the whole Mesos code would get benefits after adding these C++
> utils classes and functions. Comparing to implement CLI by
> Python/Golang or other languages, seems they could not bring too much
> benefits.
>
> But If we decide to put CLI outside Mesos repo. I perfer to use Python or
> Golang as the reasons @Guangya and @tommy mentioned above.
>
>
> On Fri, Jun 24, 2016 at 10:06 AM, tommy xiao  wrote:
>
> > Because the golang's popular, the golang is preferred as a cli build
> > toolbox. anyone interesting it.
> >
> > 2016-06-24 10:01 GMT+08:00 Guangya Liu :
> >
> > > Another advantage for using python is that we can use stevedore
> > > 
> to
> > > manage all of the CLI plugins for container, agent,cluster etc.
> > > The stevedore was been widely used in OpenStack.
> > >
> > > Thanks,
> > >
> > > Guangya
> > >
> > > On Fri, Jun 24, 2016 at 9:56 AM, Jie Yu  wrote:
> > >
> > > > I am actually fine with Python as long as we can figure out a way to
> > > > install python executable without any dependency during make install
> > (and
> > > > subsequently bundle it into rpm/deb packages). According to Kevin,
> > looks
> > > > like pyinstall can achieve that.
> > > >
> > > > If we go for the Python route, I'd like to have a style guide for our
> > > > python code. Looks like we can directly use the google python style
> > guide
> > > > . Looks like
> pylint
> > > can
> > > > also check the style automatically.
> > > >
> > > > - Jie
> > > >
> > > >
> > > > On Thu, Jun 23, 2016 at 1:21 AM, Guangya Liu 
> > wrote:
> > > >
> > > > > +1 to use python. By using python, we can debug the CLI without
> > > > re-compile
> > > > > but just update the CLI file and debug it with pdb, this is very
> > > helpful
> > > > to
> > > > > trouble shooting.
> > > > >
> > > > > On Thu, Jun 23, 2016 at 9:34 AM, Kevin Klues 
> > > wrote:
> > > > >
> > > > > > >
> > > > > > > The best option may still be for it
> > > > > > > to be in Python, this is why I'm asking if there are particular
> > > > things
> > > > > > that
> > > > > > > our helper libraries don't provide which you are leveraging in
> > > > python.
> > > > > > >
> > > > > >
> > > > > > One thing we rely heavily on that is missing is `docopt`. We use
> > > docopt
> > > > > for
> > > > > > convenient / standardized command line parsing and help
> formatting.
> > > > This
> > > > > > makes it really easy to enforce a standard help format across
> > plugins
> > > > so
> > > > > > the CLI has a consistent feel throughout all of its subcommands.
> > > > > Supposedly
> > > > > > there is a C++ implementation of this now, but it requires gcc
> 4.9+
> > > > (for
> > > > > > regex).
> > > > > > https://github.com/docopt/docopt.cpp
> > > > > >
> > > > > > In addition to this, the plugin architecture we built was very
> easy
> > > to
> > > > > > implement in python, and I'm worried it would be much more
> > > complicated
> > > > > (and
> > > > > > less readable) to get the same functionality out of C++. The
> > existing
> > > > CLI
> > > > > > has some support for "plugins" (by looking for executables in the
> > > path
> > > > > with
> > > > > > a "mesos-" prefix and assuming they are an extension to the CLI
> > that
> > > > can
> > > > > > exist as a subcommand). However, the implementation of this is
> > pretty
> > > > > > ad-hoc and error prone (though it could conceivably be redone to
> > work
> > 

Re: Slack as the canonical chat channel

[Vaibhav Khanduja]

We should atleast  open this to contributors or who has access to assign issue 
to them ...



On 6/23/16, 10:50 PM, "Vinod Kone"  wrote:

>Opened it up for few more domain names (ibm, apple etc). If your domain is
>listed at https://mesos.slack.com/signup please feel free to join.
>
>On Thu, Jun 23, 2016 at 7:07 PM, tommy xiao  wrote:
>
>> because the mesos repo is not hosted on github.  gitter.im is not best
>> option on team. slack is popular than gitter.im. so i suggest based on
>> slack.
>>
>> 2016-06-24 8:11 GMT+08:00 Jay JN Guo :
>>
>> > Great, thanks for your effort! We'd love to see it's opening up soon!
>> >
>> > /J
>> >
>> > Vinod Kone  wrote on 06/24/2016 00:36:44:
>> >
>> > > From: Vinod Kone 
>> > > To: dev 
>> > > Cc: Benjamin Hindman , Jake Farrell
>> > 
>> > > Date: 06/24/2016 00:37
>> > > Subject: Re: Slack as the canonical chat channel
>> > >
>> > > Looks like there is an overwhelming majority for *slack*! So, I went
>> > ahead
>> > > and created a slack team https://mesos.slack.com.
>> > >
>> > > For now, you can signup if you have a "*apache.org > >*"
>> > > email address (https://mesos.slack.com/signup). I'll start slowly
>> > opening
>> > > it up for more people as we get our feet wet and iron out any kinks. So
>> > > everyone should still keep using #mesos IRC channel.
>> > >
>> > > Thanks,
>> > > Vinod
>> > >
>> > > On Tue, Jun 21, 2016 at 9:42 AM, José Guilherme Vanz <
>> > > guilherme@gmail.com> wrote:
>> > >
>> > > > Yeah, sound as a good option.
>> > > >
>> > > > On Mon, 20 Jun 2016 at 20:04 Cosmin Lehene 
>> wrote:
>> > > >
>> > > > > Looks like there's a majority of +1 for Slack, so this this may be
>> > > > > pointless, however :), have you considered gitter.im (
>> > > > > https://gitter.im/home/explore/)?
>> > > > >
>> > > > >
>> > > > > It has similar capabilities to Slack, but it's (unlimited) free for
>> > open
>> > > > > source projects and seamlessly works over Github organizations and
>> > repos
>> > > > > with several major open source projects using it.
>> > > > >
>> > > > >
>> > > > > Cheers,
>> > > > >
>> > > > > Cosmin
>> > > > >
>> > > > > 
>> > > > > From: haosdent 
>> > > > > Sent: Friday, June 17, 2016 6:48:02 PM
>> > > > > To: dev
>> > > > > Cc: Benjamin Hindman; Jake Farrell
>> > > > > Subject: Re: Slack as the canonical chat channel
>> > > > >
>> > > > > +1 For Slack
>> > > > > On Jun 18, 2016 4:04 AM, "Vinod Kone" 
>> wrote:
>> > > > >
>> > > > > > Looks like people have jumped the gun here before I sent the
>> > email :)
>> > > > > >
>> > > > > > Here is the context. During the community sync we discussed about
>> > using
>> > > > > > *Slack* or *HipChat* as our official chat channel instead of our
>> > > > current
>> > > > > > #mesos IRC channel on freenode.
>> > > > > >
>> > > > > > The main reasons for using Slack/Hipchat are
>> > > > > >
>> > > > > >- In-client chat history
>> > > > > >- Discoverability of work group specific channels
>> > > > > >- Email notifications when offline
>> > > > > >- Modern UX and clients
>> > > > > >
>> > > > > > During the sync most people preferred the move to *Slack*. I
>> wanted
>> > to
>> > > > > get
>> > > > > > a sense from other community members as well through this email.
>> > Please
>> > > > > let
>> > > > > > us know what you think.
>> > > > > >
>> > > > > > Note that even if we move to Slack, we will make sure people can
>> > still
>> > > > > > connect using IRC clients and that the chat history is publicly
>> > > > available
>> > > > > > (per ASF guidelines). During the transition period, we might
>> mirror
>> > > > > > messages from Slack channel to IRC and vice-versa.
>> > > > > >
>> > > > > > Thoughts?
>> > > > > >
>> > > > > > On Fri, Jun 17, 2016 at 8:52 AM, Vinit Mahedia
>> > > > > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > +1 Slack.
>> > > > > > >
>> > > > > > > On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo
>> > 
>> > > > > > > wrote:
>> > > > > > >
>> > > > > > > > +1 Slack!
>> > > > > > > >
>> > > > > > > > /J
>> > > > > > > >
>> > > > > > > > Vaibhav Khanduja  wrote on
>> > 06/16/2016
>> > > > > > > 22:26:27:
>> > > > > > > >
>> > > > > > > > > From: Vaibhav Khanduja 
>> > > > > > > > > To: dev@mesos.apache.org
>> > > > > > > > > Date: 06/16/2016 22:26
>> > > > > > > > > Subject: Re: Notification: Community Meeting @ Thu Jun 16,
>> > 2016
>> > > > 3pm
>> > > > > > > > > - 4pm (Apache Mesos)
>> > > > > > > > >
>> > > > > > > > > + 1 slack
>> > > > > > > > >
>> > > > > > > > > Sent from my iPhone. Please excuse for typos and brevity of
>> > this
>> > > > > > > message.
>> > > > > > > > >
>> > > > > > > > > > On Jun 16, 2016, at 6:46 PM, haosdent <
>> haosd...@gmail.com>
>> > > > > wrote:
>> > > > > > > > > >
>> > > > > > > > > > +1 For Slack.
>> > > > > > > > > >
>> > > > > > > > > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann <
>> > > > g...@mesosphere.io>
>> > > > > > > > wrote:
>> > > > > > > > > >>
>> > > > > > > > >

Re: mesos/kafka issues (reviving old thread)

[Joe Stein]

+1 to setting --debug

also make sure you set the --api via CLI or properties file correctly
suspectfully sounds like the issue that keeps going back and forth (or
since it isn't set right not going back and forth ... )  its also why
it works on master because your property file may have api as localhost  or
such...

thinking out loud quick here but overall definitely a first thing to check

regards,


~ Joe Stein

On Fri, Jun 24, 2016 at 12:05 AM, Steve Niemitz  wrote:

> Have you tried running the Kafka scheduler in debug? (Pass --debug to
> iirc). That gives you a good amount of output in stdout/stderr.
>
> Also make sure your mesos lib that the scheduler is running matches your
> master version.
>
> Finally, make sure the master can communicate BACK to the scheduler on
> whatever port you set as the LIBPROCESS_PORT on the scheduler. (Firewall
> rules and such)
>
> If you want to post the stderr/stdout logs from the scheduler (with debug
> on) I can take a look.
> On Jun 23, 2016 4:41 PM, "Vinit Mahedia"  wrote:
>
> > I am running into an issue where kafka framework can't register with
> > Mesos. In packet capture I see the POST request to subscribe on mesos
> > master box but mesos master does not respond, neither it logs that it
> > received the request which it usually does on any attempt by a framework.
> > Kafka-framework keeps re-sending the request and eventually gives up.
> >
> > running locally, Mesos in VM1 and kafka-framework on VM2 works fine, also
> > some people here reported that putting kafka-framework on mesos master
> > works as well, but that is not actually working deployment.
> >
> > I can provide more information. Thanks for offering help, I really
> > appreciate your time.
> >
> > On Fri, Jun 17, 2016 at 1:36 PM, Steve Niemitz 
> > wrote:
> >
> >> No issues here, we've been running two 8 broker clusters for ~a month
> >> without incident, and I plan on rolling it out to one of our larger (~40
> >> broker) clusters next week.
> >>
> >> My experience with it has been really positive so far, it just pretty
> >> much worked out of the box.   I'm curious what issues you ran into,
> happy
> >> to try to help if you want!
> >>
> >> On Fri, Jun 17, 2016 at 3:31 PM, Vinit Mahedia 
> >> wrote:
> >>
> >>> ​Hi Steve, ​
> >>>
> >>> How long has it been running without problems? I have read on mailing
> >>> list
> >>> some people complaining that brokers sometimes disappear etc. Have you
> >>> come
> >>> across any such problems? Any other issues that you had to take care
> of?
> >>>
> >>> I tried to use the version you specified and also took the latest
> release
> >>> of kafka without luck although I am happy to have found someone for
> whom
> >>> it's working.
> >>>
> >>>
> >>> On Fri, Jun 10, 2016 at 3:57 PM, Steve Niemitz 
> >>> wrote:
> >>>
> >>> > Just to chime in, I've been running the 0.9.5.1 scheduler as a task
> on
> >>> > another slave without issues. (Aurora runs the kafka-mesos scheduler
> >>> in my
> >>> > case).
> >>> >
> >>> > On Thu, Jun 9, 2016 at 2:50 PM, Vinit Mahedia <
> vinitmahe...@gmail.com>
> >>> > wrote:
> >>> >
> >>> > > Justin,
> >>> > >
> >>> > > When you say "working" - does it mean kafka-scheduler still has to
> >>> be on
> >>> > > the same box as mesos-master? or you
> >>> > > have it working without that constraint?
> >>> > >
> >>> > > On Wed, Jun 8, 2016 at 6:07 PM, Justin Ryan 
> >>> > wrote:
> >>> > >
> >>> > > > inline
> >>> > > >
> >>> > > > On 6/8/16, 4:06 PM, "Justin Ryan"  wrote:
> >>> > > >
> >>> > > > >FYI, when I updated to the latest kafka-mesos (0.5.1.0) this
> >>> problem
> >>> > > went
> >>> > > > away.  FWIW, I’m actually using a branch which updates kafka to
> >>> > 0.10.0.0
> >>> > > as
> >>> > > > well:
> >>> > > > >
> >>> > > >
> >>> > > > Correction: 0.9.5.1 (current git master)
> >>> > > >
> >>> > > > > PR for kafka 0.10.0.0 (tests still fail, someone else did the
> >>> bulk of
> >>> > > > porting but didn’t PR it) :
> >>> https://github.com/mesos/kafka/pull/220
> >>> > > > >   ( ./gradlew jar –x test gets a successful build )
> >>> > > > >
> >>> > > > > Issue for the problem discussed in this thread:
> >>> > > > https://github.com/mesos/kafka/issues/199
> >>> > > > >
> >>> > > > >Cheers!
> >>> > > > >
> >>> > > >
> >>> > > >
> >>> > > > 
> >>> > > >
> >>> > > > P Please consider the environment before printing this e-mail
> >>> > > >
> >>> > > > The information in this electronic mail message is the sender's
> >>> > > > confidential business and may be legally privileged. It is
> intended
> >>> > > solely
> >>> > > > for the addressee(s). Access to this internet electronic mail
> >>> message
> >>> > by
> >>> > > > anyone else is unauthorized. If you are not the intended
> >>> recipient, any
> >>> > > > disclosure, copying, distribution or any action taken or omitted
> >>> to be
> >>> > > > taken in reliance on it is prohibited and may be unlawful. The
> >>> sender
> >>> > > > believes that this E-mail a