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

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

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,

Canonical contributors list

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

Re: Slack as the canonical chat channel

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

Re: Slack as the canonical chat channel

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

Re: Slack as the canonical chat channel

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

Re: Slack as the canonical chat channel

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

Re: Mesos CLI

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

Re: Slack as the canonical chat channel

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

Re: mesos/kafka issues (reviving old thread)

+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