Re: Some initial thoughts on IPv6

Thanks for starting the discussion about this Evers! Supporting IPv6 has been a long awaited feature for Mesos, so glad to see that you are interested in working on this. I would also vote for #1 because it seems to get us far with minimal code changes. There is already a #networking working

Re: Shephard Reqeust: patch for MESOS-4370

Thanks for the explanation, Greg!! Travis, Thanks for contributing to Mesos. Please go through the contributor guidelines as suggested by Greg. I can then shepherd the patch for you. Best, Kapil On Tue, Feb 2, 2016 at 2:56 PM, Greg Mann wrote: > Hi Travis, > Thanks for

RE: Shephard Reqeust: patch for MESOS-4370

OK then, Thanks. Consider this message a formal request for contributor permissions so that I can assign the JIRA to myelf. Travis -Original Message- From: Kapil Arya [mailto:ka...@mesosphere.io] Sent: Tuesday, February 2, 2016 3:04 PM To: dev Subject: Re:

Re: Cron <apsite@minotaur> /x1/home/apsite/wrkdir/bin/build.sh

We moved the 'site' directory from svn into our git repo to make it easy for contributors to submit patches for the website. Is it possible for whatever is looking at the doap file to look at git/mesos/site instead?

Re: Version numbers in docs

I agree we should remove this text after some period of time has passed since that version of Mesos was released; it is quite distracting. The proper long-term fix is probably to have version-specific docs. So all the documentation at /documentation/v0.27/... would implicitly discuss the

Version numbers in docs

Hi all! In our docs, you find such sentences as: "Mesos 0.15.0 added support for framework authentication, and 0.19.0 added slave authentication." It's a minor point, but I wonder how long we should maintain such version numbers in the docs? In the example above, my feeling is that we are far

Re: Shephard Reqeust: patch for MESOS-4370

How about rename submitting-a-patch to CONTRIBUTING.md or create CONTRIBUTING.md which would show when user create pull request in github? Furthermore, because I saw we also submit doc through Review board, how about disable pull request in Github which let user confuse? On Wed, Feb 3, 2016 at

Design Doc: Initial Support for GPGPU Resources

Hi folks, On behalf of the GPU working group [1] I'd like to share a design doc for adding some initial support for GPU resources in Mesos: JIRA Epic: https://issues.apache.org/jira/browse/MESOS-4424 Design Doc:

Re: MESOS-4581 Docker containers getting stuck in staging.

Hi Travis Thanks for narrowing down the issue. I had a brief look at your patch and it looks like it relies on adding delay before inspect is called. Although that might work mostly, I am wondering if that is the right solution. It would be better if we can have a timeout (using ‘after’ on the

Re: Install some 3rdparty packages needed for building Mesos modules

I just wanted to note that there are some existing packages doing this already. For example the thunderbird-dev package on ubuntu (>= trusty) has several private library headers in e.g. /usr/include/thunderbird/gmock or /usr/include/thunderbird/google/protobuf On 27.01.2016 16:28, Kapil Arya