Re: API working group

[Gastón Kleiman]

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

[bmahler]

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

[pleia2]

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

[bmahler]

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
2018-01-30 14:41:09 
URL:https://patch-diff.githubusercontent.com/raw/apache/mesos/pull/256.patch 
[96588] -> "256.patch" [1]
error: patch failed: site/source/community/user-groups.html.md:10
error: site/source/community/user-groups.html.md: patch does not apply
error: patch failed: docs/advanced-contribution.md:23
error: docs/advanced-contribution.md: patch does not apply
error: patch failed: docs/app-framework-development-guide.md:91
error: docs/app-framework-development-guide.md: patch does not apply
error: patch failed: docs/building.md:90
error: docs/building.md: patch does not apply
error: patch failed: docs/cmake.md:106
error: docs/cmake.md: patch does not apply
error: patch failed: docs/cni.md:202
error: docs/cni.md: patch does not apply
error: patch failed: docs/committing.md:24
error: docs/committing.md: patch does not apply
error: patch failed: docs/configuration/cmake.md:146
error: docs/configuration/cmake.md: patch does not apply
error: patch failed: docs/containerizers.md:38
error: docs/containerizers.md: patch does not apply
error: patch failed: docs/csi.md:177
error: docs/csi.md: patch does not apply
error: patch failed: docs/doxygen-style-guide.md:67
error: docs/doxygen-style-guide.md: patch does not apply
error: patch failed: docs/endpoints/files/browse.json.md:20
error: docs/endpoints/files/browse.json.md: patch does not apply
error: patch failed: docs/endpoints/files/browse.md:20
error: docs/endpoints/files/browse.md: patch does not apply
error: patch failed: docs/endpoints/files/debug.json.md:16
error: docs/endpoints/files/debug.json.md: patch does not apply
error: patch failed: docs/endpoints/files/debug.md:16
error: docs/endpoints/files/debug.md: patch does not apply
error: patch failed: docs/endpoints/files/download.json.md:20
error: docs/endpoints/files/download.json.md: patch does not apply
error: patch failed: docs/endpoints/files/download.md:20
error: docs/endpoints/files/download.md: patch does not apply
error: patch failed: docs/endpoints/files/read.json.md:21
error: docs/endpoints/files/read.json.md: patch does not apply
error: patch failed: docs/endpoints/files/read.md:21
error: docs/endpoints/files/read.md: patch does not apply
error: patch failed: docs/endpoints/master/create-volumes.md:31
error: docs/endpoints/master/create-volumes.md: patch does not apply
error: patch failed: docs/endpoints/master/destroy-volumes.md:31
error: docs/endpoints/master/destroy-volumes.md: patch does not apply
error: patch failed: docs/endpoints/master/flags.md:12
error: docs/endpoints/master/flags.md: patch does not apply
error: patch failed: docs/endpoints/master/frameworks.md:25
error: docs/endpoints/master/frameworks.md: patch does not apply
error: patch failed: docs/endpoints/master/health.md:12
error: docs/endpoints/master/health.md: patch does not apply
error: patch failed: docs/endpoints/master/quota.md:30
error: docs/endpoints/master/quota.md: patch does not apply
error: patch failed: docs/endpoints/master/reserve.md:31
error: docs/endpoints/master/reserve.md: patch does not apply
error: patch failed: docs/endpoints/master/roles.json.md:28
error: docs/endpoints/master/roles.json.md: patch does not apply
error: patch failed: docs/endpoints/master/roles.md:28
error: docs/endpoints/master/roles.md: patch does not apply
error: patch failed: docs/endpoints/master/slaves.md:29
error: docs/endpoints/master/slaves.md: patch does not apply
error: patch failed: docs/endpoints/master/state-summary.md:28
error: docs/endpoints/master/state-summary.md: patch does not apply
error: patch failed: docs/endpoints/master/state.md:97
error: docs/endpoints/master/state.md: patch does not apply
error: patch failed: docs/endpoints/master/tasks.json.md:34
error: docs/endpoints/master/tasks.json.md: patch does not apply
error: patch failed: docs/endpoints/master/tasks.md:34
error: docs/endpoints/master/tasks.md: patch does not apply
error: patch failed: docs/endpoints/master/teardown.md:25
error: docs/endpoints/master/teardown.md: patch does not apply
error: patch failed: docs/endpoints/master/unreserve.md:31
error: docs/endpoints/master/unreserve.md: patch does not apply
error: patch failed: docs/endpoints/master/weights.md:25
error: docs/endpoints/master/weights.md: patch does not apply
error: patch failed: docs/endpoints/metrics/snapshot.md:22
error: docs/endpoints/metrics/snapshot.md: patch does not apply
error: patch failed: do

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

[pleia2]

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

[bmahler]

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 at the diff correctly?


---

Re: API working group

[Benjamin Mahler]

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
> new WGs as necessary.
>
> One of the recent proposals is to spin up a API working group to discuss
> about API changes and infrastructure.
>
> I'm sending this email to gauge interest from the broader community
> regarding this working group. Particularly I would like to know
> 1) Would you be interested in participating in the API WG?
> 2) Would you be interested in leading or co-leading the API WG?
>
> Please reply to this thread if interested.
>
> Thanks,
> Vinod
>

Re: This Month in Mesos - January 2018

[Gilbert Song]

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
>> share.
>> Check out the new Apache Mesos publication > os> on
>> Medium for the latest content!
>>
>
>
> I'm really looking forward to this. As a reminder, if any one in the
> community wants to blog (cross post) about their use of Apache Mesos please
> reach out to us. We are always looking for great content!
>

Re: API working group

[Kapil Arya]

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 necessary.
>
> One of the recent proposals is to spin up a API working group to discuss
> about API changes and infrastructure.
>
> I'm sending this email to gauge interest from the broader community
> regarding this working group. Particularly I would like to know
> 1) Would you be interested in participating in the API WG?
> 2) Would you be interested in leading or co-leading the API WG?
>
> Please reply to this thread if interested.
>
> Thanks,
> Vinod
>

Re: API working group

[Zhitao Li]

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 necessary.
> 
> One of the recent proposals is to spin up a API working group to discuss
> about API changes and infrastructure.
> 
> I'm sending this email to gauge interest from the broader community
> regarding this working group. Particularly I would like to know
> 1) Would you be interested in participating in the API WG?
> 2) Would you be interested in leading or co-leading the API WG?
> 
> Please reply to this thread if interested.
> 
> Thanks,
> Vinod

API working group

[Vinod Kone]

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.

I'm sending this email to gauge interest from the broader community
regarding this working group. Particularly I would like to know
1) Would you be interested in participating in the API WG?
2) Would you be interested in leading or co-leading the API WG?

Please reply to this thread if interested.

Thanks,
Vinod

Re: This Month in Mesos - January 2018

[Vinod Kone]

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 the latest content!
>


I'm really looking forward to this. As a reminder, if any one in the
community wants to blog (cross post) about their use of Apache Mesos please
reach out to us. We are always looking for great content!

This Month in Mesos - January 2018

[Greg Mann]

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 interests you, please attend in the future! Working group meetings can
be found on the Mesos community calendar
, and you can feel free
to add agenda items beforehand.


*Containerization Working Group*

[Agenda Doc

]

Next meeting: Feb. 8 @ 9am PST


   - Resource constraints on Windows! (MESOS-6690
   )
   - Container Storage Interface MVP has landed! (docs
   )
   - Standalone container support MVP has landed! (MESOS-7302
   )
   - Image layer garbage collection MVP has landed! (docs
   

   )
   - Network ports isolator has landed! (docs
   )
   - Planning for 1.6 is underway (planning doc
   

   )


*Performance Working Group*

[Agenda Doc

]

Next meeting: Feb. 21 @ 10am PST


   - Benchmarking of "v0" vs. v1 API; results in agenda doc
  - Big improvements in v1 performance in 1.5.0!
  - Room for further optimization


*Community Working Group*

[Agenda Doc

]

Next Meeting: Feb. 12 @ 10:30am PST


   - Suggestions for new working groups:
  - API
  - Operator
  - Storage
   - Starting to cross-post future blog posts on Medium
   - Have long list of blog post ideas, need to organize/motivate authors


*1.5.0 Release Update*
The first release candidate for Mesos 1.5.0 went out on the mailing lists,
and subsequently a regression was identified. The fix for MESOS-8481
 just landed, so a new RC
will be sent out for a vote soon. Watch your inbox!


*Doc-A-Thon*
Thanks to everyone who attended on Jan. 11th for our first doc-a-thon of
2018! Some notable results:

   - Standalone container documentation
   
   - Mesos developer's guide
   

   - Operator API curl commands 
   - WIP: beginner's guide for framework development

We plan to continue with quarterly gatherings to improve our documentation.
Long-term goals include versioned documentation on the website and
automatic generation of API docs from our protobuf definitions. If you have
any desire to help with these initiatives, join the #docs channel on Mesos
Slack  or reach out to the
community working group!


*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  on
Medium for the latest content!


That's it for this month; until next time,
-Greg

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

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/mesos/pull/261


---

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

[EMumau]

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 changes as the patch at:

https://github.com/apache/mesos/pull/261.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #261


commit 76ef72854e2849a9850d4e97f15340ddd749443e
Author: EMumau 
Date:   2018-01-30T16:50:27Z

Update contributors.yaml




---

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

[EMumau]

Github user EMumau closed the pull request at:

https://github.com/apache/mesos/pull/260


---

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

[jieyu]

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
+  affiliations:
+- {organization: Microsoft}
+  emails:
+- ermu...@microsoft.com
+  jira_user: ermumau
+  reviewboard_user: ermumau
+  
--- End diff --

Can you remove the tailing space? It failed our style checker.


---

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

[EMumau]

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 changes as the patch at:

https://github.com/apache/mesos/pull/260.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #260


commit 3cfe74dde143d2cb5abf0b3770322ebd2f3f779b
Author: EMumau 
Date:   2018-01-30T16:41:56Z

Update contributors.yaml




---