Welcome Kapil as Mesos committer and PMC member!

I'm happy to announce that Kapil Arya has been voted a Mesos committer and PMC member! Welcome Kapil, and thanks for all of your great contributions to the project so far! Looking forward to lots more of your contributions! Thanks Till

Re: Welcome Kapil as Mesos committer and PMC member!

Congratulations! On Thu, Nov 5, 2015 at 6:02 PM, Till Toenshoff wrote: > I'm happy to announce that Kapil Arya has been voted a Mesos committer and > PMC member! > > Welcome Kapil, and thanks for all of your great contributions to the > project so far! > > Looking forward to

Re: Proposal: move towards #pragma and away from #include guards

+1 On Thu, Nov 5, 2015 at 7:58 PM, Bernd Mathiske wrote: > +1 > > This site has a list of compilers that support #pragma once. > > https://en.wikipedia.org/wiki/Pragma_once#Portability > > Clang, MS V C++, GCC as of 3.4. from 2006. OK! > > (Too bad for Sun/Oracle Studio

Re: Proposal: move towards #pragma and away from #include guards

+1 for #pragma and +1 for Bernd's suggestion. I normally don't like mass updates because they make it harder to read the commit history. However in this case all the changes will be located at the top of the file and shouldn't influence readability of the history. However, I would limit the

Re: Welcome Kapil as Mesos committer and PMC member!

Welcome, Kapil! Well-deserved. On Thu, Nov 5, 2015 at 2:07 AM, haosdent wrote: > Congratulations! > > On Thu, Nov 5, 2015 at 6:02 PM, Till Toenshoff wrote: > >> I'm happy to announce that Kapil Arya has been voted a Mesos committer >> and PMC member! >> >>

Re: Proposal: move towards #pragma and away from #include guards

Just because I apparently was not very clear: in the "history" and "summarized objections" sections of my original mail, I did attempt to capture all of the objections from this thread and previous discussions I found (and, just for the sake of thoroughness, I do actually explicitly cite this

Re: Proposal: move towards #pragma and away from #include guards

While I’m all in on the proposal, we did have this discussion almost a year ago [1] at the end I think, the decision was not to use them, though I don’t remember the exact reason. In any case, I vote +1 non-binding. [1]

Re: Welcome Kapil as Mesos committer and PMC member!

Congrats, Kapil! Gilbert > On Nov 5, 2015, at 2:02 AM, Till Toenshoff wrote: > > I'm happy to announce that Kapil Arya has been voted a Mesos committer and > PMC member! > > Welcome Kapil, and thanks for all of your great contributions to the project > so far! > >

Re: Towards Mesos release 0.26.0

As announced, we will be cutting the next release tomorrow, 6th of November. We currently have 130 blockers (as shown at https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12327111 ). If you have any

Re: Towards Mesos release 0.26.0

Just for closure, it looks like a stunning 78% of these are due to me (they are Windows integration-related). Since probably all of these are not actually blocking 0.26, I will un/re-tag as appropriate today. Also, I do apologize for making the issue graph a hockey stick. On Thu, Nov 5, 2015 at

Re: Proposal: move towards #pragma and away from #include guards

Hi Alex, While I agree with the idea in general, I strongly believe that we should either leave it as it is or fix everything in one go (i.e. three consecutive commits). Having both #include guards and #pragmas in the codebase will be confusing and untidy. We have done code sweeps like this in

Re: Proposal: move towards #pragma and away from #include guards

my fault, I started reading at the office and when I came home I thought I had already read your whole email. Still, I have always been in favor or the `#pragma once` solution. So as I said: +1 (non-binding). > On 05 Nov 2015, at 18:21, Alex Clemmer wrote: > >

Re: Proposal: move towards #pragma and away from #include guards

+1. I think we should do it all at once as Artem mentioned. This doesn't really affect the history (git-blame, etc.) because we are not touching code per se. On Thu, Nov 5, 2015 at 12:29 PM, Artem Harutyunyan wrote: > Hi Alex, > > While I agree with the idea in general, I

Fwd: [jira] [Created] (MESOS-2353) Improve performance of the master's state.json endpoint for large clusters.

The benchmark can be written independently and should exist before the fix so we can measure the improvement. Vinod sounds like you might be interested in writing one while waiting for michael? -- Forwarded message -- From: *Vinod Kone (JIRA)* Date: Thursday,

Re: [jira] [Created] (MESOS-2353) Improve performance of the master's state.json endpoint for large clusters.

Definitely! I wasn't sure if Michael already added a benchmark as part of this reviews/prototyping. On Thu, Nov 5, 2015 at 8:40 AM, Benjamin Mahler wrote: > The benchmark can be written independently and should exist before the fix > so we can measure the improvement.

Finish Oversubscription before 0.26.0?

All who worked on MESOS-354, What’s the status of the Oversubscription epic? Can we already call it a feature in 0.26? Shall we wait a few days to finish it? Will it slip into 0.27? I see only 6 unresolved tickets and lots of resolved ones here: https://issues.apache.org/jira/browse/MESOS-354

New Cloud Foundry Framework - Mesos & CloudFoundry Integration

Hi folks, I just joined the Apache Mesos mailing list. I wanted to reach out to the community regarding the new CloudFoundry/Mesos framework we have developed in our Santa Clara Lab. We would like to contribute this work to the Mesos open source community. I am pretty sure that this

Re: Welcome Kapil as Mesos committer and PMC member!

Congrats Kapil! On Thu, Nov 5, 2015 at 2:02 AM, Till Toenshoff wrote: > I'm happy to announce that Kapil Arya has been voted a Mesos committer and > PMC member! > > Welcome Kapil, and thanks for all of your great contributions to the > project so far! > > Looking forward to

Re: Finish Oversubscription before 0.26.0?

Nope - go ahead and close On Thu, Nov 5, 2015 at 10:24 AM, Jie Yu wrote: > I would say the MVP is done. Of course, there'll be some followup > improvement to the feature, and all the remaining issues are within that > category. I am fine resolving this epic. Any one has any

Re: New Cloud Foundry Framework - Mesos & CloudFoundry Integration

I think that the Mesos org. on github (https://github.com/mesos) hosts similar projects, so perhaps that would be a suitable location? On Thu, Nov 5, 2015 at 2:09 PM, Marco Massenzio wrote: > Hey Deepak, > > that's really exciting, great stuff! > > As Alex correctly pointed

Re: Apache Mesos Community Sync

Sorry for the late link, but you can see the youtube stream (and after-the-fact video) at: http://youtu.be/rJyT8xDzhcA We also have a hangout link for those with agenda items, or those who have lengthy things to discuss (ask if you need the link). For brief questions, you can add them to the

Re: Welcome Kapil as Mesos committer and PMC member!

Thanks everyone! :-). On Thu, Nov 5, 2015 at 3:50 PM, Elizabeth Lingg wrote: > Congrats Professor! You definitely deserve it. > > -Elizabeth > > On Thu, Nov 5, 2015 at 10:53 AM, Jie Yu wrote: > > > Congrats Kapil! > > > > On Thu, Nov 5, 2015 at

Re: Welcome Kapil as Mesos committer and PMC member!

Congrats Professor! You definitely deserve it. -Elizabeth On Thu, Nov 5, 2015 at 10:53 AM, Jie Yu wrote: > Congrats Kapil! > > On Thu, Nov 5, 2015 at 2:02 AM, Till Toenshoff wrote: > > > I'm happy to announce that Kapil Arya has been voted a Mesos

Re: Mesos Style Guideline Adjustments

This has come up in a couple of reviews, seems like we should add some soft guidelines around how to format comments for readability. In particular, the reason that we wrapped at 70 in the past was for readability, so it would be great to continue doing so as a soft stylistic rule. The other

Re: New Cloud Foundry Framework - Mesos & CloudFoundry Integration

Hey Deepak, that's really exciting, great stuff! As Alex correctly pointed out, though, if we understand this correctly, your work is around a Mesos Framework, is that right? (what does the framework does?) If that's the case, it would not be part of the Mesos codebase proper, but should

Re: New Cloud Foundry Framework - Mesos & CloudFoundry Integration

The contribution documentation for the Mesos codebase is here: http://mesos.apache.org/documentation/latest/submitting-a-patch/ That said, it is not clear (to me at least) what you mean. It sounds like you've written a framework. Is that right? If so, the it seems like it might not fit in the

Re: Welcome Kapil as Mesos committer and PMC member!

Awesome! Welcome Kapil! On Thu, Nov 5, 2015 at 5:20 PM, Benjamin Mahler wrote: > Congrats and welcome! > > On Thu, Nov 5, 2015 at 4:04 PM, Kapil Arya wrote: > >> Thanks everyone! :-). >> >> >> >> On Thu, Nov 5, 2015 at 3:50 PM, Elizabeth Lingg

Re: Welcome Kapil as Mesos committer and PMC member!

Congrats and welcome! On Thu, Nov 5, 2015 at 4:04 PM, Kapil Arya wrote: > Thanks everyone! :-). > > > > On Thu, Nov 5, 2015 at 3:50 PM, Elizabeth Lingg > wrote: > >> Congrats Professor! You definitely deserve it. >> >> -Elizabeth >> >> On Thu, Nov

Re: Proposal: move towards #pragma and away from #include guards

+1 with all-at-once — *Joris Van Remoortere* Mesosphere On Thu, Nov 5, 2015 at 9:37 AM, Kapil Arya wrote: > +1. > > I think we should do it all at once as Artem mentioned. This doesn't really > affect the history (git-blame, etc.) because we are not touching code per > se.

Re: [jira] [Comment Edited] (MESOS-2079) IO.Write test is flaky on OS X 10.10.

Just want to surface this up to the dev@ thread to raise some awareness. Recently with the SIGPIPE bug from libev [1], we've revisited whether it makes sense to continue down the path of leaving SIGPIPE unblocked and trying to handle it case by case. We originally wanted users of libprocess to

Re: Welcome Kapil as Mesos committer and PMC member!

Congrats Kapil. This is really worth to be celebrated. > On 05 Nov 2015, at 11:02, Till Toenshoff wrote: > > I'm happy to announce that Kapil Arya has been voted a Mesos committer and > PMC member! > > Welcome Kapil, and thanks for all of your great contributions to the