Re: Welcome Greg Mann as a new committer and PMC member!

[Judith Malnick]

Congrats!! That's awesome!

On Thu, Jun 15, 2017 at 10:28 AM, Greg Mann  wrote:

> Thanks everyone! It's an honor to be part of such a group :)
>
> Looking forward to more contributions and collaborations!!
>
> Cheers,
> Greg
>
> On Wed, Jun 14, 2017 at 9:39 AM, Artem Harutyunyan 
> wrote:
>
>> Awesome!!! Congrats Greg, very well deserved.
>>
>> Artem.
>>
>> On Tue, Jun 13, 2017 at 2:42 PM Vinod Kone  wrote:
>>
>> > Hi folks,
>> >
>> > Please welcome Greg Mann as the newest committer and PMC member of the
>> > Apache Mesos project.
>> >
>> > Greg has been an active contributor to the Mesos project for close to 2
>> > years now and has made many solid contributions. His biggest source code
>> > contribution to the project has been around adding authentication
>> support
>> > for default executor. This was a major new feature that involved quite a
>> > few moving parts. Additionally, he also worked on improving the
>> scheduler
>> > and executor APIs.
>> >
>> > Here is his more formal checklist for your perusal.
>> >
>> >
>> > https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_R
>> 8JYRRc5spV0yKrpsGBw/edit
>> >
>> > Thanks,
>> > Vinod
>> >
>> >
>>
>
>


-- 
Judith Malnick
DC/OS Community Manager
310-709-1517

Re: Welcome Greg Mann as a new committer and PMC member!

[Benjamin Mahler]

Thanks for all that you've done for the project so far Greg, it's been a
pleasure working with you.

Congrats and welcome!

On Tue, Jun 13, 2017 at 2:42 PM, Vinod Kone  wrote:

> Hi folks,
>
> Please welcome Greg Mann as the newest committer and PMC member of the
> Apache Mesos project.
>
> Greg has been an active contributor to the Mesos project for close to 2
> years now and has made many solid contributions. His biggest source code
> contribution to the project has been around adding authentication support
> for default executor. This was a major new feature that involved quite a
> few moving parts. Additionally, he also worked on improving the scheduler
> and executor APIs.
>
> Here is his more formal checklist for your perusal.
>
> https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_
> R8JYRRc5spV0yKrpsGBw/edit
>
> Thanks,
> Vinod
>
>

Re: Work group on Community

[Benjamin Mahler]

Thanks for kicking this off Vinod! (lists to bcc)

I'm happy to join, I would add the following under this umbrella for now:

--> Project PR (e.g. blog posts, twitter, etc)
--> Events
--> Website / documentation
--> New contributor UX

On Thu, Jun 15, 2017 at 10:57 AM, Vinod Kone  wrote:

> Hi folks,
>
> Seeing that our first official containerizer WG is off to a good start, we
> want to use that momentum to start new WGs.
>
> I'm proposing that we start a new work group on community. The mission of
> this work group would be to figure out ways to grow the size of our
> community and improve the experience of community members (users, devs,
> contributors, committers etc).
>
> In the first meeting, we can nail down what the charter of this work group
> should be etc. My initial ideas for the topics/components this work group
> could cover
>
> --> Releases
> --> Roadmap
> --> Reviews
> --> JIRA
> --> CI
>
> Over time, I'm hoping that new specific work groups will sprung up that can
> own some of these topics.
>
> If you are interested in joining this work group, please reply to this
> thread and I'll add you to the invite.
>
> Thanks,
> Vinod
>

Re: [Proposal] Multiple Containers in Single Mesos Task

[Benjamin Mahler]

>From reading this, the motivation is that TaskGroup having 1 task per
container "could create a scalability issue for a large scale Mesos cluster
since many endpoints/operations scale with the total number of Tasks in the
cluster."

Is that the only motivation here?

On Thu, Jun 15, 2017 at 11:45 AM, Charles Raimbert 
wrote:

> Hello All,
>
> As we are interested in PODs to run colocated containers under the same
> grouping, we have been looking at TaskGroup but we have also been working
> on a design to allow multiple containers in the same Task.
>
> Please feel free to write your comments and suggestions on the proposal
> draft:
> https://docs.google.com/document/d/1Os5tXUJfJ8Op_
> YBZR7L8hSHqIeO1f9LY2yzKxsOdrwg
>
> Thanks,
> Charles Raimbert & Zhitao Li
>

[Containerization WG] Notes 06/15/2017

[Jie Yu]

Hi folks,

Today, we discussed the volume ownership problem, lead by Ilya.
https://docs.google.com/document/d/1eMaSTS3-DTsWJYyeXUnotIquSpf3nsukrHEt9GS2ONE/edit#

Please find today's notes in the following doc.
https://docs.google.com/document/d/1z55a7tLZFoRWVuUxz1FZwgxkHeugtc2nHR89skFXSpU/edit?usp=sharing

The recording can be found here:
https://drive.google.com/file/d/0B78XyMjTpvTmWWdFZGRUazkwRkU/view?usp=sharing

- Jie

Work group on Community

[Vinod Kone]

Hi folks,

Seeing that our first official containerizer WG is off to a good start, we
want to use that momentum to start new WGs.

I'm proposing that we start a new work group on community. The mission of
this work group would be to figure out ways to grow the size of our
community and improve the experience of community members (users, devs,
contributors, committers etc).

In the first meeting, we can nail down what the charter of this work group
should be etc. My initial ideas for the topics/components this work group
could cover

--> Releases
--> Roadmap
--> Reviews
--> JIRA
--> CI

Over time, I'm hoping that new specific work groups will sprung up that can
own some of these topics.

If you are interested in joining this work group, please reply to this
thread and I'll add you to the invite.

Thanks,
Vinod

Re: Welcome Greg Mann as a new committer and PMC member!

[Greg Mann]

Thanks everyone! It's an honor to be part of such a group :)

Looking forward to more contributions and collaborations!!

Cheers,
Greg

On Wed, Jun 14, 2017 at 9:39 AM, Artem Harutyunyan 
wrote:

> Awesome!!! Congrats Greg, very well deserved.
>
> Artem.
>
> On Tue, Jun 13, 2017 at 2:42 PM Vinod Kone  wrote:
>
> > Hi folks,
> >
> > Please welcome Greg Mann as the newest committer and PMC member of the
> > Apache Mesos project.
> >
> > Greg has been an active contributor to the Mesos project for close to 2
> > years now and has made many solid contributions. His biggest source code
> > contribution to the project has been around adding authentication support
> > for default executor. This was a major new feature that involved quite a
> > few moving parts. Additionally, he also worked on improving the scheduler
> > and executor APIs.
> >
> > Here is his more formal checklist for your perusal.
> >
> >
> > https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_
> R8JYRRc5spV0yKrpsGBw/edit
> >
> > Thanks,
> > Vinod
> >
> >
>

Re: Easing the Pain of Code Formatting in Mesos

[Greg Mann]

+1!!!

On Thu, Jun 15, 2017 at 8:43 AM, Jie Yu  wrote:

> +1
>
> Also, agreed with AlexR. Some of our style rules are very subjective.
> Tooling and enforceable rules are much more important.
>
> - Jie
>
> On Thu, Jun 15, 2017 at 8:13 AM, Zhitao Li  wrote:
>
> > strongly +1 to this.
> >
> > On Thu, Jun 15, 2017 at 7:20 AM, Alex Rukletsov 
> > wrote:
> >
> > > +1. Having an enforceable rule is sometimes more important than the
> rule
> > > itself (e.g., 4 vs. 2 spaces indent).
> > >
> > > On Thu, Jun 15, 2017 at 9:59 AM, Alexander Rojas <
> > alexan...@mesosphere.io>
> > > wrote:
> > >
> > > > +1 It is always frustrating to rely in clang format to realize it
> > > generate
> > > > the wrong style, even for old Mesos contributors
> > > >
> > > > Alexander Rojas
> > > > alexan...@mesosphere.io
> > > >
> > > >
> > > >
> > > >
> > > > > On 15. Jun 2017, at 04:32, Michael Park  wrote:
> > > > >
> > > > > I'm increasingly hearing that many contributors who want to
> > contribute
> > > to
> > > > > Mesos find that
> > > > > it's often difficult to do so. One of the big issues is due to our
> > > > > formatting rules which is not
> > > > > automated. As a result, we've had many reviews that are
> overwhelming
> > in
> > > > > style comments
> > > > > with only a couple of comments on functionality.
> > > > >
> > > > > This is very frustrating for contributors, and is also a large
> burden
> > > on
> > > > > the committers to
> > > > > remember, review and explain the formatting sections of the style
> > > guide.
> > > > >
> > > > > I introduced *ClangFormat* a long time ago as our formatting tool,
> > but
> > > it
> > > > > was only
> > > > > a supplementary tool since it didn't yet conform fully to the style
> > > > guide.
> > > > > We've done a lot of
> > > > > work to narrow this gap and the gap is actually quite small at this
> > > > point.
> > > > > However, the existence
> > > > > of such a gap is enough to stir discussions and render the tool
> > useless
> > > > for
> > > > > some people.
> > > > >
> > > > > I think we should close this gap by adopting ClangFormat as our
> > > > formatting
> > > > > guideline.
> > > > >
> > > > > I don't have a fully fleshed out plan just yet. I'd like to push
> for
> > > this
> > > > > effort again,
> > > > > as I find it to be very important.
> > > > >
> > > > > I'm just seeking for +1s if you'd like to see a fleshed out plan
> for
> > > > this.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > MPark
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Cheers,
> >
> > Zhitao Li
> >
>

Re: Easing the Pain of Code Formatting in Mesos

[Jie Yu]

+1

Also, agreed with AlexR. Some of our style rules are very subjective.
Tooling and enforceable rules are much more important.

- Jie

On Thu, Jun 15, 2017 at 8:13 AM, Zhitao Li  wrote:

> strongly +1 to this.
>
> On Thu, Jun 15, 2017 at 7:20 AM, Alex Rukletsov 
> wrote:
>
> > +1. Having an enforceable rule is sometimes more important than the rule
> > itself (e.g., 4 vs. 2 spaces indent).
> >
> > On Thu, Jun 15, 2017 at 9:59 AM, Alexander Rojas <
> alexan...@mesosphere.io>
> > wrote:
> >
> > > +1 It is always frustrating to rely in clang format to realize it
> > generate
> > > the wrong style, even for old Mesos contributors
> > >
> > > Alexander Rojas
> > > alexan...@mesosphere.io
> > >
> > >
> > >
> > >
> > > > On 15. Jun 2017, at 04:32, Michael Park  wrote:
> > > >
> > > > I'm increasingly hearing that many contributors who want to
> contribute
> > to
> > > > Mesos find that
> > > > it's often difficult to do so. One of the big issues is due to our
> > > > formatting rules which is not
> > > > automated. As a result, we've had many reviews that are overwhelming
> in
> > > > style comments
> > > > with only a couple of comments on functionality.
> > > >
> > > > This is very frustrating for contributors, and is also a large burden
> > on
> > > > the committers to
> > > > remember, review and explain the formatting sections of the style
> > guide.
> > > >
> > > > I introduced *ClangFormat* a long time ago as our formatting tool,
> but
> > it
> > > > was only
> > > > a supplementary tool since it didn't yet conform fully to the style
> > > guide.
> > > > We've done a lot of
> > > > work to narrow this gap and the gap is actually quite small at this
> > > point.
> > > > However, the existence
> > > > of such a gap is enough to stir discussions and render the tool
> useless
> > > for
> > > > some people.
> > > >
> > > > I think we should close this gap by adopting ClangFormat as our
> > > formatting
> > > > guideline.
> > > >
> > > > I don't have a fully fleshed out plan just yet. I'd like to push for
> > this
> > > > effort again,
> > > > as I find it to be very important.
> > > >
> > > > I'm just seeking for +1s if you'd like to see a fleshed out plan for
> > > this.
> > > >
> > > > Thanks,
> > > >
> > > > MPark
> > >
> > >
> >
>
>
>
> --
> Cheers,
>
> Zhitao Li
>

Re: Easing the Pain of Code Formatting in Mesos

[Zhitao Li]

strongly +1 to this.

On Thu, Jun 15, 2017 at 7:20 AM, Alex Rukletsov  wrote:

> +1. Having an enforceable rule is sometimes more important than the rule
> itself (e.g., 4 vs. 2 spaces indent).
>
> On Thu, Jun 15, 2017 at 9:59 AM, Alexander Rojas 
> wrote:
>
> > +1 It is always frustrating to rely in clang format to realize it
> generate
> > the wrong style, even for old Mesos contributors
> >
> > Alexander Rojas
> > alexan...@mesosphere.io
> >
> >
> >
> >
> > > On 15. Jun 2017, at 04:32, Michael Park  wrote:
> > >
> > > I'm increasingly hearing that many contributors who want to contribute
> to
> > > Mesos find that
> > > it's often difficult to do so. One of the big issues is due to our
> > > formatting rules which is not
> > > automated. As a result, we've had many reviews that are overwhelming in
> > > style comments
> > > with only a couple of comments on functionality.
> > >
> > > This is very frustrating for contributors, and is also a large burden
> on
> > > the committers to
> > > remember, review and explain the formatting sections of the style
> guide.
> > >
> > > I introduced *ClangFormat* a long time ago as our formatting tool, but
> it
> > > was only
> > > a supplementary tool since it didn't yet conform fully to the style
> > guide.
> > > We've done a lot of
> > > work to narrow this gap and the gap is actually quite small at this
> > point.
> > > However, the existence
> > > of such a gap is enough to stir discussions and render the tool useless
> > for
> > > some people.
> > >
> > > I think we should close this gap by adopting ClangFormat as our
> > formatting
> > > guideline.
> > >
> > > I don't have a fully fleshed out plan just yet. I'd like to push for
> this
> > > effort again,
> > > as I find it to be very important.
> > >
> > > I'm just seeking for +1s if you'd like to see a fleshed out plan for
> > this.
> > >
> > > Thanks,
> > >
> > > MPark
> >
> >
>



-- 
Cheers,

Zhitao Li

Re: Easing the Pain of Code Formatting in Mesos

[Alex Rukletsov]

+1. Having an enforceable rule is sometimes more important than the rule
itself (e.g., 4 vs. 2 spaces indent).

On Thu, Jun 15, 2017 at 9:59 AM, Alexander Rojas 
wrote:

> +1 It is always frustrating to rely in clang format to realize it generate
> the wrong style, even for old Mesos contributors
>
> Alexander Rojas
> alexan...@mesosphere.io
>
>
>
>
> > On 15. Jun 2017, at 04:32, Michael Park  wrote:
> >
> > I'm increasingly hearing that many contributors who want to contribute to
> > Mesos find that
> > it's often difficult to do so. One of the big issues is due to our
> > formatting rules which is not
> > automated. As a result, we've had many reviews that are overwhelming in
> > style comments
> > with only a couple of comments on functionality.
> >
> > This is very frustrating for contributors, and is also a large burden on
> > the committers to
> > remember, review and explain the formatting sections of the style guide.
> >
> > I introduced *ClangFormat* a long time ago as our formatting tool, but it
> > was only
> > a supplementary tool since it didn't yet conform fully to the style
> guide.
> > We've done a lot of
> > work to narrow this gap and the gap is actually quite small at this
> point.
> > However, the existence
> > of such a gap is enough to stir discussions and render the tool useless
> for
> > some people.
> >
> > I think we should close this gap by adopting ClangFormat as our
> formatting
> > guideline.
> >
> > I don't have a fully fleshed out plan just yet. I'd like to push for this
> > effort again,
> > as I find it to be very important.
> >
> > I'm just seeking for +1s if you'd like to see a fleshed out plan for
> this.
> >
> > Thanks,
> >
> > MPark
>
>

Re: Easing the Pain of Code Formatting in Mesos

[Alexander Rojas]

+1 It is always frustrating to rely in clang format to realize it generate the 
wrong style, even for old Mesos contributors

Alexander Rojas
alexan...@mesosphere.io




> On 15. Jun 2017, at 04:32, Michael Park  wrote:
> 
> I'm increasingly hearing that many contributors who want to contribute to
> Mesos find that
> it's often difficult to do so. One of the big issues is due to our
> formatting rules which is not
> automated. As a result, we've had many reviews that are overwhelming in
> style comments
> with only a couple of comments on functionality.
> 
> This is very frustrating for contributors, and is also a large burden on
> the committers to
> remember, review and explain the formatting sections of the style guide.
> 
> I introduced *ClangFormat* a long time ago as our formatting tool, but it
> was only
> a supplementary tool since it didn't yet conform fully to the style guide.
> We've done a lot of
> work to narrow this gap and the gap is actually quite small at this point.
> However, the existence
> of such a gap is enough to stir discussions and render the tool useless for
> some people.
> 
> I think we should close this gap by adopting ClangFormat as our formatting
> guideline.
> 
> I don't have a fully fleshed out plan just yet. I'd like to push for this
> effort again,
> as I find it to be very important.
> 
> I'm just seeking for +1s if you'd like to see a fleshed out plan for this.
> 
> Thanks,
> 
> MPark