Re: API working group

On Tue, Jan 30, 2018 at 10:42 AM, Vinod Kone wrote: > [...] > 1) Would you be interested in participating in the API WG? > I'd be interested! -Gastón

[GitHub] mesos issue #256: Correct spelling errors in the docs

Github user bmahler commented on the issue: https://github.com/apache/mesos/pull/256 Sorry about that, and thank you for your patience! ---

[GitHub] mesos issue #256: Correct spelling errors in the docs

Github user pleia2 commented on the issue: https://github.com/apache/mesos/pull/256 What a mess. I'll fiddle with my patch and see about submitting it over on the Review Board side. ---

[GitHub] mesos issue #256: Correct spelling errors in the docs

Github user bmahler commented on the issue: https://github.com/apache/mesos/pull/256 Hm.. I'm unable to pull the patch down: ``` $ ./support/apply-reviews.py -g 256 Cookie coming from patch-diff.githubusercontent.com attempted to set domain to github.com

[GitHub] mesos issue #256: Correct spelling errors in the docs

Github user pleia2 commented on the issue: https://github.com/apache/mesos/pull/256 It seems the diff is unhelpfully showing the difference between the two commits, rather than from the source. Pulling it down to do a local squash and diff should show things properly. ---

[GitHub] mesos issue #256: Correct spelling errors in the docs

Github user bmahler commented on the issue: https://github.com/apache/mesos/pull/256 Hm.. I don't know if I'm looking at this right, but when I click 'Files Changed' I still see the "iff" and "acknowledgements" adjustments, so I wonder if your update took effect or if I'm not looking

Re: API working group

I'd be interested in participating. Lots to discuss! On Tue, Jan 30, 2018 at 10:42 AM, Vinod Kone wrote: > Hi folks, > > We've had good success with our containerization, performance and community > working groups and so we would like to keep the momentum going and spin up

Re: This Month in Mesos - January 2018

Awesome, Greg! On Tue, Jan 30, 2018 at 10:34 AM, Vinod Kone wrote: > Thanks Greg for the update! > > > *Medium Posts* >> Going forward, we'll be cross-posting Apache Mesos blog posts on Medium to >> increase exposure, get feedback on engagement, and make it easier to >>

Re: API working group

I'm interested in participating. On Tue, Jan 30, 2018 at 1:42 PM, Vinod Kone wrote: > Hi folks, > > We've had good success with our containerization, performance and community > working groups and so we would like to keep the momentum going and spin up > new WGs as

Re: API working group

Yes I’m interested in attending. > On Jan 30, 2018, at 10:42 AM, Vinod Kone wrote: > > Hi folks, > > We've had good success with our containerization, performance and community > working groups and so we would like to keep the momentum going and spin up > new WGs as

API working group

Hi folks, We've had good success with our containerization, performance and community working groups and so we would like to keep the momentum going and spin up new WGs as necessary. One of the recent proposals is to spin up a API working group to discuss about API changes and infrastructure.

Re: This Month in Mesos - January 2018

Thanks Greg for the update! *Medium Posts* > Going forward, we'll be cross-posting Apache Mesos blog posts on Medium to > increase exposure, get feedback on engagement, and make it easier to share. > Check out the new Apache Mesos publication mesos> on > Medium for

This Month in Mesos - January 2018

Dear Apache Mesos Community, Happy new year! Here's your latest update on happenings in Mesosworld over the past month. *Working Groups* The working groups have been active; here's a brief summary of recent developments, along with links to the agenda documents. If you see anything that

[GitHub] mesos pull request #261: Update contributors.yaml

Github user asfgit closed the pull request at: https://github.com/apache/mesos/pull/261 ---

[GitHub] mesos pull request #261: Update contributors.yaml

GitHub user EMumau opened a pull request: https://github.com/apache/mesos/pull/261 Update contributors.yaml You can merge this pull request into a Git repository by running: $ git pull https://github.com/EMumau/mesos patch-2 Alternatively you can review and apply these

[GitHub] mesos pull request #260: Update contributors.yaml

Github user EMumau closed the pull request at: https://github.com/apache/mesos/pull/260 ---

[GitHub] mesos pull request #260: Update contributors.yaml

Github user jieyu commented on a diff in the pull request: https://github.com/apache/mesos/pull/260#discussion_r164804742 --- Diff: docs/contributors.yaml --- @@ -253,6 +253,14 @@ jira_user: cinchurge reviewboard_user: cinchurge +- name: Eric Mumau +

[GitHub] mesos pull request #260: Update contributors.yaml

GitHub user EMumau opened a pull request: https://github.com/apache/mesos/pull/260 Update contributors.yaml You can merge this pull request into a Git repository by running: $ git pull https://github.com/EMumau/mesos patch-1 Alternatively you can review and apply these