Re: Contribution Request

[Artem Harutyunyan]

Done! Welcome to Mesos!

On Wed, Feb 17, 2016 at 9:48 AM, Kevin Devroede 
wrote:

> Hello,
>
> Can you please add me to the list of Mesos contributors?
>
> I would like to submit a code review for the following JIRA:
> https://issues.apache.org/jira/browse/MESOS-4693 <
> https://issues.apache.org/jira/browse/MESOS-4693>
>
> Thanks,
> Kevin
>
>

Contribution Request

[Kevin Devroede]

Hello,

Can you please add me to the list of Mesos contributors?

I would like to submit a code review for the following JIRA: 
https://issues.apache.org/jira/browse/MESOS-4693 


Thanks,
Kevin

Re: Contribution Request

[Artem Harutyunyan]

Done. Welcome to Mesos and sorry this fell through the cracks.

Artem.

On Wed, Jan 20, 2016 at 7:09 PM, Jayamohan.K  wrote:
> Pl add me as a Mesos Contributor.
>
> My Apache Review Board and Jira username is jayamohank
>
> Thanks
> JayK

Contribution Request

[Jayamohan.K]

Pl add me as a Mesos Contributor.

My Apache Review Board and Jira username is jayamohank

Thanks
JayK

Contribution request

[Abhishek Dasgupta]

Hi,
  
   I want to contribute to mesos project. So, please add me as a mesos contributor.

   I created Apache Review Board account as "a10gupta" and JIRA account as 
"a10gupta".

--
  Regards,

  
---
  Abhishek Dasgupta
  Linux Software Developer - Linux Technology Centre
  IBM Systems Lab,
  IBM India Pvt. Ltd.
  Embassy Golf Link, D Block
  Koramongala - Off Indiranagar Ring Road
  Bangalore - 560 071
  Mobile: +91-8884107981
  
---

Re: Contribution request

[Vinod Kone]

Added. Welcome!

On Wed, Jan 20, 2016 at 10:51 AM, Abhishek Dasgupta <
a10gu...@linux.vnet.ibm.com> wrote:

> Hi,
>  I want to contribute to mesos project. So, please add me as a mesos
> contributor.
>I created Apache Review Board account as "a10gupta" and JIRA account as
> "a10gupta".
>
> --
>   Regards,
>
>
> ---
>   Abhishek Dasgupta
>   Linux Software Developer - Linux Technology Centre
>   IBM Systems Lab,
>   IBM India Pvt. Ltd.
>   Embassy Golf Link, D Block
>   Koramongala - Off Indiranagar Ring Road
>   Bangalore - 560 071
>   Mobile: +91-8884107981
>
> ---
>
>

Re: Contribution Request

[Vinod Kone]

I think you might be confused. The external facing flag is still
`authenticate`. The internal representation of the flag has been changed to
`authenticate_frameworks` a while back, as you alluded to. I added the JIRA
link to the existing TODO last week :)

On Mon, Jan 18, 2016 at 1:23 AM, Alexander Rojas 
wrote:

> Hey guys,
>
> There is already a flag called `authenticate_frameworks` which was added
> as early as April 2015, it also includes a TODO pointing to the mentioned
> JIRA (MESOS-4386). So I think enough time has passed to simply remove the
> flag.
>
> Best,
>
> Alexander
>
> > On 15 Jan 2016, at 19:15, Vinod Kone  wrote:
> >
> > Hi Disha,
> >
> > Thanks for asking.
> >
> > We cannot just rename the `authenticate` flag to
> `authenticate_frameworks`
> > because that will break users who are already setting that flag, when
> they
> > upgrade to the new version (that has this change). We always strive to do
> > backwards compatible changes.
> >
> > The first step is to add a new flag called `authenticate_frameworks` flag
> > and make sure the master does the same thing as when `authenticate` flag
> is
> > set. As part of this we need to 1) send an email to dev/user mailing
> lists
> > that this deprecation is coming and 2) update the CHANGELOG. Lets say
> this
> > all happens in the 0.28 release. After a few releases (to give
> > users/operators enough time), we can remove the `authenticate` flag.
> >
> > Does that make sense?
> >
> >
> > On Fri, Jan 15, 2016 at 9:55 AM, Disha Singh 
> > wrote:
> >
> >> MESOS-4386 says :
> >>
> >> << `authenticate_http`
> >> flags, we should rename `authenticate` to `authenticate_frameworks`
> flag.
> >>
> >> This should be done via deprecation cycle.
> >>
> >> 1) Release X supports both `authenticate` and `authenticate_frameworks`
> >> flags
> >>
> >> 2) Release X + n supports only `authenticate_frameworks` flag.
> >>
> >> How should I move ahead with resolving it ? Does it simply mean changing
> >> the word "authenticate" to authenticate frameworks ? I am a newbie
> .Please
> >> help. :)
> >>
> >>
> >> On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan <
> ar...@mesosphere.io>
> >> wrote:
> >>
> >>> Done. Welcome to Mesos community!
> >>>
> >>> On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh <
> directionsta...@gmail.com>
> >>> wrote:
>  Please add me to the list of Mesos contributors. I would like to
> >> submit a
>  code review for the following JIRA:
>  
> >>>
> >>
>
>

Re: Contribution Request

[Alexander Rojas]

Hey guys,

There is already a flag called `authenticate_frameworks` which was added as 
early as April 2015, it also includes a TODO pointing to the mentioned JIRA 
(MESOS-4386). So I think enough time has passed to simply remove the flag.

Best,

Alexander

> On 15 Jan 2016, at 19:15, Vinod Kone  wrote:
> 
> Hi Disha,
> 
> Thanks for asking.
> 
> We cannot just rename the `authenticate` flag to `authenticate_frameworks`
> because that will break users who are already setting that flag, when they
> upgrade to the new version (that has this change). We always strive to do
> backwards compatible changes.
> 
> The first step is to add a new flag called `authenticate_frameworks` flag
> and make sure the master does the same thing as when `authenticate` flag is
> set. As part of this we need to 1) send an email to dev/user mailing lists
> that this deprecation is coming and 2) update the CHANGELOG. Lets say this
> all happens in the 0.28 release. After a few releases (to give
> users/operators enough time), we can remove the `authenticate` flag.
> 
> Does that make sense?
> 
> 
> On Fri, Jan 15, 2016 at 9:55 AM, Disha Singh 
> wrote:
> 
>> MESOS-4386 says :
>> 
>> <<> flags, we should rename `authenticate` to `authenticate_frameworks` flag.
>> 
>> This should be done via deprecation cycle.
>> 
>> 1) Release X supports both `authenticate` and `authenticate_frameworks`
>> flags
>> 
>> 2) Release X + n supports only `authenticate_frameworks` flag.
>> 
>> How should I move ahead with resolving it ? Does it simply mean changing
>> the word "authenticate" to authenticate frameworks ? I am a newbie .Please
>> help. :)
>> 
>> 
>> On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan 
>> wrote:
>> 
>>> Done. Welcome to Mesos community!
>>> 
>>> On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh 
>>> wrote:
 Please add me to the list of Mesos contributors. I would like to
>> submit a
 code review for the following JIRA:
 
>>> 
>> 

Re: Contribution Request

[Artem Harutyunyan]

Done. Welcome to Mesos community!

On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh  wrote:
> Please add me to the list of Mesos contributors. I would like to submit a
> code review for the following JIRA:
> 

Re: Contribution Request

[Disha Singh]

MESOS-4386 says :

<<>>>

 How should I move ahead with resolving it ? Does it simply mean changing
the word "authenticate" to authenticate frameworks ? I am a newbie .Please
help. :)


On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan 
wrote:

> Done. Welcome to Mesos community!
>
> On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh 
> wrote:
> > Please add me to the list of Mesos contributors. I would like to submit a
> > code review for the following JIRA:
> > 
>

Re: Contribution Request

[Vinod Kone]

done

On Fri, Jan 15, 2016 at 8:35 AM, Jiří Šimša  wrote:

> Please add me to the list of Mesos contributors. I would like to submit a
> code review for the following JIRA
> .
>
> Best,
>
> --
> Jiří Šimša
>

Contribution Request

[Disha Singh]

Please add me to the list of Mesos contributors. I would like to submit a
code review for the following JIRA:

Contribution Request

[Jiří Šimša]

Please add me to the list of Mesos contributors. I would like to submit a
code review for the following JIRA
.

Best,

--
Jiří Šimša

Re: Contribution Request

[Disha Singh]

Yes,It does. If you could tell me where these flags are and where I should
add them . I tried to figure it out in the git repository :
https://github.com/apache/mesos

But unfortunately could not.


On Fri, Jan 15, 2016 at 11:45 PM, Vinod Kone  wrote:

> Hi Disha,
>
> Thanks for asking.
>
> We cannot just rename the `authenticate` flag to `authenticate_frameworks`
> because that will break users who are already setting that flag, when they
> upgrade to the new version (that has this change). We always strive to do
> backwards compatible changes.
>
> The first step is to add a new flag called `authenticate_frameworks` flag
> and make sure the master does the same thing as when `authenticate` flag is
> set. As part of this we need to 1) send an email to dev/user mailing lists
> that this deprecation is coming and 2) update the CHANGELOG. Lets say this
> all happens in the 0.28 release. After a few releases (to give
> users/operators enough time), we can remove the `authenticate` flag.
>
> Does that make sense?
>
>
> On Fri, Jan 15, 2016 at 9:55 AM, Disha Singh 
> wrote:
>
> > MESOS-4386 says :
> >
> > << `authenticate_http`
> > flags, we should rename `authenticate` to `authenticate_frameworks` flag.
> >
> > This should be done via deprecation cycle.
> >
> > 1) Release X supports both `authenticate` and `authenticate_frameworks`
> > flags
> >
> > 2) Release X + n supports only `authenticate_frameworks` flag.
> >
> >  How should I move ahead with resolving it ? Does it simply mean changing
> > the word "authenticate" to authenticate frameworks ? I am a newbie
> .Please
> > help. :)
> >
> >
> > On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan  >
> > wrote:
> >
> > > Done. Welcome to Mesos community!
> > >
> > > On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh <
> directionsta...@gmail.com>
> > > wrote:
> > > > Please add me to the list of Mesos contributors. I would like to
> > submit a
> > > > code review for the following JIRA:
> > > > 
> > >
> >
>

Re: Contribution Request

[Artem Harutyunyan]

Hi Disha,

Did you get a chance to take a look at
http://mesos.apache.org/documentation/latest/submitting-a-patch/?

Cheers,
Artem.

On Fri, Jan 15, 2016 at 10:35 AM, Disha Singh  wrote:
> Yes,It does. If you could tell me where these flags are and where I should
> add them . I tried to figure it out in the git repository :
> https://github.com/apache/mesos
>
> But unfortunately could not.
>
>
> On Fri, Jan 15, 2016 at 11:45 PM, Vinod Kone  wrote:
>
>> Hi Disha,
>>
>> Thanks for asking.
>>
>> We cannot just rename the `authenticate` flag to `authenticate_frameworks`
>> because that will break users who are already setting that flag, when they
>> upgrade to the new version (that has this change). We always strive to do
>> backwards compatible changes.
>>
>> The first step is to add a new flag called `authenticate_frameworks` flag
>> and make sure the master does the same thing as when `authenticate` flag is
>> set. As part of this we need to 1) send an email to dev/user mailing lists
>> that this deprecation is coming and 2) update the CHANGELOG. Lets say this
>> all happens in the 0.28 release. After a few releases (to give
>> users/operators enough time), we can remove the `authenticate` flag.
>>
>> Does that make sense?
>>
>>
>> On Fri, Jan 15, 2016 at 9:55 AM, Disha Singh 
>> wrote:
>>
>> > MESOS-4386 says :
>> >
>> > <<> `authenticate_http`
>> > flags, we should rename `authenticate` to `authenticate_frameworks` flag.
>> >
>> > This should be done via deprecation cycle.
>> >
>> > 1) Release X supports both `authenticate` and `authenticate_frameworks`
>> > flags
>> >
>> > 2) Release X + n supports only `authenticate_frameworks` flag.
>> >
>> >  How should I move ahead with resolving it ? Does it simply mean changing
>> > the word "authenticate" to authenticate frameworks ? I am a newbie
>> .Please
>> > help. :)
>> >
>> >
>> > On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan > >
>> > wrote:
>> >
>> > > Done. Welcome to Mesos community!
>> > >
>> > > On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh <
>> directionsta...@gmail.com>
>> > > wrote:
>> > > > Please add me to the list of Mesos contributors. I would like to
>> > submit a
>> > > > code review for the following JIRA:
>> > > > 
>> > >
>> >
>>

Re: Contribution Request

[Abhishek Dasgupta]

Hi Disha,
Welcome to mesos community. First of all, if you want to work on 
MESOS-4386, you need to assign yourself the ticket. So go through all 
the necessary steps of


http://mesos.apache.org/documentation/latest/submitting-a-patch/  for that.

I think, if you check this source file (src/master/flags.cpp) and look 
for authenticate_frameworks, you might get a hint on resolving the issue.


Thank you,
Abhishek Dasgupta


On Saturday 16 January 2016 12:05 AM, Disha Singh wrote:

Yes,It does. If you could tell me where these flags are and where I should
add them . I tried to figure it out in the git repository :
https://github.com/apache/mesos

But unfortunately could not.


On Fri, Jan 15, 2016 at 11:45 PM, Vinod Kone  wrote:


Hi Disha,

Thanks for asking.

We cannot just rename the `authenticate` flag to `authenticate_frameworks`
because that will break users who are already setting that flag, when they
upgrade to the new version (that has this change). We always strive to do
backwards compatible changes.

The first step is to add a new flag called `authenticate_frameworks` flag
and make sure the master does the same thing as when `authenticate` flag is
set. As part of this we need to 1) send an email to dev/user mailing lists
that this deprecation is coming and 2) update the CHANGELOG. Lets say this
all happens in the 0.28 release. After a few releases (to give
users/operators enough time), we can remove the `authenticate` flag.

Does that make sense?


On Fri, Jan 15, 2016 at 9:55 AM, Disha Singh 
wrote:


MESOS-4386 says :

<<
`authenticate_http`

flags, we should rename `authenticate` to `authenticate_frameworks` flag.

This should be done via deprecation cycle.

1) Release X supports both `authenticate` and `authenticate_frameworks`
flags

2) Release X + n supports only `authenticate_frameworks` flag.

  How should I move ahead with resolving it ? Does it simply mean changing
the word "authenticate" to authenticate frameworks ? I am a newbie

.Please

help. :)


On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan 

wrote:

Please add me to the list of Mesos contributors. I would like to

submit a

code review for the following JIRA:



--
  Regards,

  
---
  Abhishek Dasgupta
  Linux Software Developer - Linux Technology Centre
  IBM Systems Lab,
  IBM India Pvt. Ltd.
  Embassy Golf Link, D Block
  Koramongala - Off Indiranagar Ring Road
  Bangalore - 560 071
  Mobile: +91-8884107981
  
---

Re: Contribution Request

[Disha Singh]

Yes Artem, I did look at the link .I'm only looking for an issue which I
can resolve so that I can start working with the patch. I also read about
"shepherd". I wonder when I can be assigned one.
Also , I think it's easy to resolve : <
https://issues.apache.org/jira/browse/MESOS-4336> but I can't find the code
on git so i can carry out the necessary work . :(

On Sat, Jan 16, 2016 at 12:21 AM, Artem Harutyunyan 
wrote:

> Hi Disha,
>
> Did you get a chance to take a look at
> http://mesos.apache.org/documentation/latest/submitting-a-patch/?
>
> Cheers,
> Artem.
>
> On Fri, Jan 15, 2016 at 10:35 AM, Disha Singh 
> wrote:
> > Yes,It does. If you could tell me where these flags are and where I
> should
> > add them . I tried to figure it out in the git repository :
> > https://github.com/apache/mesos
> >
> > But unfortunately could not.
> >
> >
> > On Fri, Jan 15, 2016 at 11:45 PM, Vinod Kone 
> wrote:
> >
> >> Hi Disha,
> >>
> >> Thanks for asking.
> >>
> >> We cannot just rename the `authenticate` flag to
> `authenticate_frameworks`
> >> because that will break users who are already setting that flag, when
> they
> >> upgrade to the new version (that has this change). We always strive to
> do
> >> backwards compatible changes.
> >>
> >> The first step is to add a new flag called `authenticate_frameworks`
> flag
> >> and make sure the master does the same thing as when `authenticate`
> flag is
> >> set. As part of this we need to 1) send an email to dev/user mailing
> lists
> >> that this deprecation is coming and 2) update the CHANGELOG. Lets say
> this
> >> all happens in the 0.28 release. After a few releases (to give
> >> users/operators enough time), we can remove the `authenticate` flag.
> >>
> >> Does that make sense?
> >>
> >>
> >> On Fri, Jan 15, 2016 at 9:55 AM, Disha Singh  >
> >> wrote:
> >>
> >> > MESOS-4386 says :
> >> >
> >> > << >> `authenticate_http`
> >> > flags, we should rename `authenticate` to `authenticate_frameworks`
> flag.
> >> >
> >> > This should be done via deprecation cycle.
> >> >
> >> > 1) Release X supports both `authenticate` and
> `authenticate_frameworks`
> >> > flags
> >> >
> >> > 2) Release X + n supports only `authenticate_frameworks` flag.
> >> >
> >> >  How should I move ahead with resolving it ? Does it simply mean
> changing
> >> > the word "authenticate" to authenticate frameworks ? I am a newbie
> >> .Please
> >> > help. :)
> >> >
> >> >
> >> > On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan <
> ar...@mesosphere.io
> >> >
> >> > wrote:
> >> >
> >> > > Done. Welcome to Mesos community!
> >> > >
> >> > > On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh <
> >> directionsta...@gmail.com>
> >> > > wrote:
> >> > > > Please add me to the list of Mesos contributors. I would like to
> >> > submit a
> >> > > > code review for the following JIRA:
> >> > > > 
> >> > >
> >> >
> >>
>

Re: Contribution Request

[Vinod Kone]

Hi Disha,

Thanks for asking.

We cannot just rename the `authenticate` flag to `authenticate_frameworks`
because that will break users who are already setting that flag, when they
upgrade to the new version (that has this change). We always strive to do
backwards compatible changes.

The first step is to add a new flag called `authenticate_frameworks` flag
and make sure the master does the same thing as when `authenticate` flag is
set. As part of this we need to 1) send an email to dev/user mailing lists
that this deprecation is coming and 2) update the CHANGELOG. Lets say this
all happens in the 0.28 release. After a few releases (to give
users/operators enough time), we can remove the `authenticate` flag.

Does that make sense?


On Fri, Jan 15, 2016 at 9:55 AM, Disha Singh 
wrote:

> MESOS-4386 says :
>
> << flags, we should rename `authenticate` to `authenticate_frameworks` flag.
>
> This should be done via deprecation cycle.
>
> 1) Release X supports both `authenticate` and `authenticate_frameworks`
> flags
>
> 2) Release X + n supports only `authenticate_frameworks` flag.
>
>  How should I move ahead with resolving it ? Does it simply mean changing
> the word "authenticate" to authenticate frameworks ? I am a newbie .Please
> help. :)
>
>
> On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan 
> wrote:
>
> > Done. Welcome to Mesos community!
> >
> > On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh 
> > wrote:
> > > Please add me to the list of Mesos contributors. I would like to
> submit a
> > > code review for the following JIRA:
> > > 
> >
>

Re: Contribution Request

[Vinod Kone]

We really need to swap steps 4 (well the assigning part) and 6 in the
"submitting
a patch "
link. I would love for new users to first find a shepherd, discuss the
problem/solution *before* assigning the ticket to themselves.

On Fri, Jan 15, 2016 at 11:08 AM, Abhishek Dasgupta <
a10gu...@linux.vnet.ibm.com> wrote:

> Hi Disha,
> Welcome to mesos community. First of all, if you want to work on
> MESOS-4386, you need to assign yourself the ticket. So go through all the
> necessary steps of
>
> http://mesos.apache.org/documentation/latest/submitting-a-patch/  for
> that.
>
> I think, if you check this source file (src/master/flags.cpp) and look for
> authenticate_frameworks, you might get a hint on resolving the issue.
>
> Thank you,
> Abhishek Dasgupta
>
>
>
> On Saturday 16 January 2016 12:05 AM, Disha Singh wrote:
>
>> Yes,It does. If you could tell me where these flags are and where I should
>> add them . I tried to figure it out in the git repository :
>> https://github.com/apache/mesos
>>
>> But unfortunately could not.
>>
>>
>> On Fri, Jan 15, 2016 at 11:45 PM, Vinod Kone 
>> wrote:
>>
>> Hi Disha,
>>>
>>> Thanks for asking.
>>>
>>> We cannot just rename the `authenticate` flag to
>>> `authenticate_frameworks`
>>> because that will break users who are already setting that flag, when
>>> they
>>> upgrade to the new version (that has this change). We always strive to do
>>> backwards compatible changes.
>>>
>>> The first step is to add a new flag called `authenticate_frameworks` flag
>>> and make sure the master does the same thing as when `authenticate` flag
>>> is
>>> set. As part of this we need to 1) send an email to dev/user mailing
>>> lists
>>> that this deprecation is coming and 2) update the CHANGELOG. Lets say
>>> this
>>> all happens in the 0.28 release. After a few releases (to give
>>> users/operators enough time), we can remove the `authenticate` flag.
>>>
>>> Does that make sense?
>>>
>>>
>>> On Fri, Jan 15, 2016 at 9:55 AM, Disha Singh 
>>> wrote:
>>>
>>> MESOS-4386 says :

 <<>>>
>>> `authenticate_http`
>>>
 flags, we should rename `authenticate` to `authenticate_frameworks`
 flag.

 This should be done via deprecation cycle.

 1) Release X supports both `authenticate` and `authenticate_frameworks`
 flags

 2) Release X + n supports only `authenticate_frameworks` flag.

   How should I move ahead with resolving it ? Does it simply mean
 changing
 the word "authenticate" to authenticate frameworks ? I am a newbie

>>> .Please
>>>
 help. :)


 On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan <
 ar...@mesosphere.io

 wrote:

 Done. Welcome to Mesos community!
>
> On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh <
>
 directionsta...@gmail.com>
>>>
 wrote:
>
>> Please add me to the list of Mesos contributors. I would like to
>>
> submit a

> code review for the following JIRA:
>> 
>>
>
> --
>   Regards,
>
>
> ---
>   Abhishek Dasgupta
>   Linux Software Developer - Linux Technology Centre
>   IBM Systems Lab,
>   IBM India Pvt. Ltd.
>   Embassy Golf Link, D Block
>   Koramongala - Off Indiranagar Ring Road
>   Bangalore - 560 071
>   Mobile: +91-8884107981
>
> ---
>
>

Re: Contribution Request

[Vaibhav Khanduja]

Current process makes sure bad code does not get in … though not sure of
this swap ...

On Fri, Jan 15, 2016 at 11:12 AM, Vinod Kone  wrote:

> We really need to swap steps 4 (well the assigning part) and 6 in the
> "submitting
> a patch  >"
> link. I would love for new users to first find a shepherd, discuss the
> problem/solution *before* assigning the ticket to themselves.
>
> On Fri, Jan 15, 2016 at 11:08 AM, Abhishek Dasgupta <
> a10gu...@linux.vnet.ibm.com> wrote:
>
> > Hi Disha,
> > Welcome to mesos community. First of all, if you want to work on
> > MESOS-4386, you need to assign yourself the ticket. So go through all the
> > necessary steps of
> >
> > http://mesos.apache.org/documentation/latest/submitting-a-patch/  for
> > that.
> >
> > I think, if you check this source file (src/master/flags.cpp) and look
> for
> > authenticate_frameworks, you might get a hint on resolving the issue.
> >
> > Thank you,
> > Abhishek Dasgupta
> >
> >
> >
> > On Saturday 16 January 2016 12:05 AM, Disha Singh wrote:
> >
> >> Yes,It does. If you could tell me where these flags are and where I
> should
> >> add them . I tried to figure it out in the git repository :
> >> https://github.com/apache/mesos
> >>
> >> But unfortunately could not.
> >>
> >>
> >> On Fri, Jan 15, 2016 at 11:45 PM, Vinod Kone 
> >> wrote:
> >>
> >> Hi Disha,
> >>>
> >>> Thanks for asking.
> >>>
> >>> We cannot just rename the `authenticate` flag to
> >>> `authenticate_frameworks`
> >>> because that will break users who are already setting that flag, when
> >>> they
> >>> upgrade to the new version (that has this change). We always strive to
> do
> >>> backwards compatible changes.
> >>>
> >>> The first step is to add a new flag called `authenticate_frameworks`
> flag
> >>> and make sure the master does the same thing as when `authenticate`
> flag
> >>> is
> >>> set. As part of this we need to 1) send an email to dev/user mailing
> >>> lists
> >>> that this deprecation is coming and 2) update the CHANGELOG. Lets say
> >>> this
> >>> all happens in the 0.28 release. After a few releases (to give
> >>> users/operators enough time), we can remove the `authenticate` flag.
> >>>
> >>> Does that make sense?
> >>>
> >>>
> >>> On Fri, Jan 15, 2016 at 9:55 AM, Disha Singh <
> directionsta...@gmail.com>
> >>> wrote:
> >>>
> >>> MESOS-4386 says :
> 
>  << 
> >>> `authenticate_http`
> >>>
>  flags, we should rename `authenticate` to `authenticate_frameworks`
>  flag.
> 
>  This should be done via deprecation cycle.
> 
>  1) Release X supports both `authenticate` and
> `authenticate_frameworks`
>  flags
> 
>  2) Release X + n supports only `authenticate_frameworks` flag.
> 
>    How should I move ahead with resolving it ? Does it simply mean
>  changing
>  the word "authenticate" to authenticate frameworks ? I am a newbie
> 
> >>> .Please
> >>>
>  help. :)
> 
> 
>  On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan <
>  ar...@mesosphere.io
> 
>  wrote:
> 
>  Done. Welcome to Mesos community!
> >
> > On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh <
> >
>  directionsta...@gmail.com>
> >>>
>  wrote:
> >
> >> Please add me to the list of Mesos contributors. I would like to
> >>
> > submit a
> 
> > code review for the following JIRA:
> >> 
> >>
> >
> > --
> >   Regards,
> >
> >
> >
> ---
> >   Abhishek Dasgupta
> >   Linux Software Developer - Linux Technology Centre
> >   IBM Systems Lab,
> >   IBM India Pvt. Ltd.
> >   Embassy Golf Link, D Block
> >   Koramongala - Off Indiranagar Ring Road
> >   Bangalore - 560 071
> >   Mobile: +91-8884107981
> >
> >
> ---
> >
> >
>

Re: Contribution Request

[Disha Singh]

The documentation says "find a shepherd" but in the "create an issue"
option on JIRA one can click on any user he feels like. I am not
understanding the process actually. Please help. I created an issue taking
an idea from the suggestion above:



 What should I do next to resolve the issue?


On Sat, Jan 16, 2016 at 12:42 AM, Vinod Kone  wrote:

> We really need to swap steps 4 (well the assigning part) and 6 in the
> "submitting
> a patch  >"
> link. I would love for new users to first find a shepherd, discuss the
> problem/solution *before* assigning the ticket to themselves.
>
> On Fri, Jan 15, 2016 at 11:08 AM, Abhishek Dasgupta <
> a10gu...@linux.vnet.ibm.com> wrote:
>
> > Hi Disha,
> > Welcome to mesos community. First of all, if you want to work on
> > MESOS-4386, you need to assign yourself the ticket. So go through all the
> > necessary steps of
> >
> > http://mesos.apache.org/documentation/latest/submitting-a-patch/  for
> > that.
> >
> > I think, if you check this source file (src/master/flags.cpp) and look
> for
> > authenticate_frameworks, you might get a hint on resolving the issue.
> >
> > Thank you,
> > Abhishek Dasgupta
> >
> >
> >
> > On Saturday 16 January 2016 12:05 AM, Disha Singh wrote:
> >
> >> Yes,It does. If you could tell me where these flags are and where I
> should
> >> add them . I tried to figure it out in the git repository :
> >> https://github.com/apache/mesos
> >>
> >> But unfortunately could not.
> >>
> >>
> >> On Fri, Jan 15, 2016 at 11:45 PM, Vinod Kone 
> >> wrote:
> >>
> >> Hi Disha,
> >>>
> >>> Thanks for asking.
> >>>
> >>> We cannot just rename the `authenticate` flag to
> >>> `authenticate_frameworks`
> >>> because that will break users who are already setting that flag, when
> >>> they
> >>> upgrade to the new version (that has this change). We always strive to
> do
> >>> backwards compatible changes.
> >>>
> >>> The first step is to add a new flag called `authenticate_frameworks`
> flag
> >>> and make sure the master does the same thing as when `authenticate`
> flag
> >>> is
> >>> set. As part of this we need to 1) send an email to dev/user mailing
> >>> lists
> >>> that this deprecation is coming and 2) update the CHANGELOG. Lets say
> >>> this
> >>> all happens in the 0.28 release. After a few releases (to give
> >>> users/operators enough time), we can remove the `authenticate` flag.
> >>>
> >>> Does that make sense?
> >>>
> >>>
> >>> On Fri, Jan 15, 2016 at 9:55 AM, Disha Singh <
> directionsta...@gmail.com>
> >>> wrote:
> >>>
> >>> MESOS-4386 says :
> 
>  << 
> >>> `authenticate_http`
> >>>
>  flags, we should rename `authenticate` to `authenticate_frameworks`
>  flag.
> 
>  This should be done via deprecation cycle.
> 
>  1) Release X supports both `authenticate` and
> `authenticate_frameworks`
>  flags
> 
>  2) Release X + n supports only `authenticate_frameworks` flag.
> 
>    How should I move ahead with resolving it ? Does it simply mean
>  changing
>  the word "authenticate" to authenticate frameworks ? I am a newbie
> 
> >>> .Please
> >>>
>  help. :)
> 
> 
>  On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan <
>  ar...@mesosphere.io
> 
>  wrote:
> 
>  Done. Welcome to Mesos community!
> >
> > On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh <
> >
>  directionsta...@gmail.com>
> >>>
>  wrote:
> >
> >> Please add me to the list of Mesos contributors. I would like to
> >>
> > submit a
> 
> > code review for the following JIRA:
> >> 
> >>
> >
> > --
> >   Regards,
> >
> >
> >
> ---
> >   Abhishek Dasgupta
> >   Linux Software Developer - Linux Technology Centre
> >   IBM Systems Lab,
> >   IBM India Pvt. Ltd.
> >   Embassy Golf Link, D Block
> >   Koramongala - Off Indiranagar Ring Road
> >   Bangalore - 560 071
> >   Mobile: +91-8884107981
> >
> >
> ---
> >
> >
>

Re: Contribution Request

[Vaibhav Khanduja]

As per process, you need to get a shepherd. Easiest way to send an email to
dev community requesting commiters ..

On Fri, Jan 15, 2016 at 12:36 PM, Disha Singh 
wrote:

> The documentation says "find a shepherd" but in the "create an issue"
> option on JIRA one can click on any user he feels like. I am not
> understanding the process actually. Please help. I created an issue taking
> an idea from the suggestion above:
>
> 
>
>  What should I do next to resolve the issue?
>
>
> On Sat, Jan 16, 2016 at 12:42 AM, Vinod Kone  wrote:
>
> > We really need to swap steps 4 (well the assigning part) and 6 in the
> > "submitting
> > a patch <
> http://mesos.apache.org/documentation/latest/submitting-a-patch/
> > >"
> > link. I would love for new users to first find a shepherd, discuss the
> > problem/solution *before* assigning the ticket to themselves.
> >
> > On Fri, Jan 15, 2016 at 11:08 AM, Abhishek Dasgupta <
> > a10gu...@linux.vnet.ibm.com> wrote:
> >
> > > Hi Disha,
> > > Welcome to mesos community. First of all, if you want to work on
> > > MESOS-4386, you need to assign yourself the ticket. So go through all
> the
> > > necessary steps of
> > >
> > > http://mesos.apache.org/documentation/latest/submitting-a-patch/  for
> > > that.
> > >
> > > I think, if you check this source file (src/master/flags.cpp) and look
> > for
> > > authenticate_frameworks, you might get a hint on resolving the issue.
> > >
> > > Thank you,
> > > Abhishek Dasgupta
> > >
> > >
> > >
> > > On Saturday 16 January 2016 12:05 AM, Disha Singh wrote:
> > >
> > >> Yes,It does. If you could tell me where these flags are and where I
> > should
> > >> add them . I tried to figure it out in the git repository :
> > >> https://github.com/apache/mesos
> > >>
> > >> But unfortunately could not.
> > >>
> > >>
> > >> On Fri, Jan 15, 2016 at 11:45 PM, Vinod Kone 
> > >> wrote:
> > >>
> > >> Hi Disha,
> > >>>
> > >>> Thanks for asking.
> > >>>
> > >>> We cannot just rename the `authenticate` flag to
> > >>> `authenticate_frameworks`
> > >>> because that will break users who are already setting that flag, when
> > >>> they
> > >>> upgrade to the new version (that has this change). We always strive
> to
> > do
> > >>> backwards compatible changes.
> > >>>
> > >>> The first step is to add a new flag called `authenticate_frameworks`
> > flag
> > >>> and make sure the master does the same thing as when `authenticate`
> > flag
> > >>> is
> > >>> set. As part of this we need to 1) send an email to dev/user mailing
> > >>> lists
> > >>> that this deprecation is coming and 2) update the CHANGELOG. Lets say
> > >>> this
> > >>> all happens in the 0.28 release. After a few releases (to give
> > >>> users/operators enough time), we can remove the `authenticate` flag.
> > >>>
> > >>> Does that make sense?
> > >>>
> > >>>
> > >>> On Fri, Jan 15, 2016 at 9:55 AM, Disha Singh <
> > directionsta...@gmail.com>
> > >>> wrote:
> > >>>
> > >>> MESOS-4386 says :
> > 
> >  << > 
> > >>> `authenticate_http`
> > >>>
> >  flags, we should rename `authenticate` to `authenticate_frameworks`
> >  flag.
> > 
> >  This should be done via deprecation cycle.
> > 
> >  1) Release X supports both `authenticate` and
> > `authenticate_frameworks`
> >  flags
> > 
> >  2) Release X + n supports only `authenticate_frameworks`
> flag.
> > 
> >    How should I move ahead with resolving it ? Does it simply mean
> >  changing
> >  the word "authenticate" to authenticate frameworks ? I am a newbie
> > 
> > >>> .Please
> > >>>
> >  help. :)
> > 
> > 
> >  On Fri, Jan 15, 2016 at 11:07 PM, Artem Harutyunyan <
> >  ar...@mesosphere.io
> > 
> >  wrote:
> > 
> >  Done. Welcome to Mesos community!
> > >
> > > On Fri, Jan 15, 2016 at 9:26 AM, Disha Singh <
> > >
> >  directionsta...@gmail.com>
> > >>>
> >  wrote:
> > >
> > >> Please add me to the list of Mesos contributors. I would like to
> > >>
> > > submit a
> > 
> > > code review for the following JIRA:
> > >> 
> > >>
> > >
> > > --
> > >   Regards,
> > >
> > >
> > >
> >
> ---
> > >   Abhishek Dasgupta
> > >   Linux Software Developer - Linux Technology Centre
> > >   IBM Systems Lab,
> > >   IBM India Pvt. Ltd.
> > >   Embassy Golf Link, D Block
> > >   Koramongala - Off Indiranagar Ring Road
> > >   Bangalore - 560 071
> > >   Mobile: +91-8884107981
> > >
> > >
> >
> ---
> > >
> > >
> >
>

Re: Contribution Request

[Jiří Šimša]

Thanks Vinod. Would you mind being a shepherd for this code review? Thank
you.

Best,

--
Jiří Šimša

On Fri, Jan 15, 2016 at 8:52 AM, Vinod Kone  wrote:

> done
>
> On Fri, Jan 15, 2016 at 8:35 AM, Jiří Šimša  wrote:
>
> > Please add me to the list of Mesos contributors. I would like to submit a
> > code review for the following JIRA
> > .
> >
> > Best,
> >
> > --
> > Jiří Šimša
> >
>

Re: Contribution Request

[Vinod Kone]

Seems simple enough. Sure.

On Fri, Jan 15, 2016 at 2:33 PM, Jiří Šimša  wrote:

> Thanks Vinod. Would you mind being a shepherd for this code review? Thank
> you.
>
> Best,
>
> --
> Jiří Šimša
>
> On Fri, Jan 15, 2016 at 8:52 AM, Vinod Kone  wrote:
>
> > done
> >
> > On Fri, Jan 15, 2016 at 8:35 AM, Jiří Šimša 
> wrote:
> >
> > > Please add me to the list of Mesos contributors. I would like to
> submit a
> > > code review for the following JIRA
> > > .
> > >
> > > Best,
> > >
> > > --
> > > Jiří Šimša
> > >
> >
>

Re: Contribution Request

[Jiří Šimša]

Thank you. Here is the code review 
.

--
Jiří Šimša

On Fri, Jan 15, 2016 at 3:27 PM, Vinod Kone  wrote:

> Seems simple enough. Sure.
>
> On Fri, Jan 15, 2016 at 2:33 PM, Jiří Šimša  wrote:
>
> > Thanks Vinod. Would you mind being a shepherd for this code review? Thank
> > you.
> >
> > Best,
> >
> > --
> > Jiří Šimša
> >
> > On Fri, Jan 15, 2016 at 8:52 AM, Vinod Kone 
> wrote:
> >
> > > done
> > >
> > > On Fri, Jan 15, 2016 at 8:35 AM, Jiří Šimša 
> > wrote:
> > >
> > > > Please add me to the list of Mesos contributors. I would like to
> > submit a
> > > > code review for the following JIRA
> > > > .
> > > >
> > > > Best,
> > > >
> > > > --
> > > > Jiří Šimša
> > > >
> > >
> >
>

Contribution Request for Mesos

[Yong Tang]

Hi
After using Mesos and following Mesos project for quite some time, I would like 
to participate and contribute to the Mesos project. Could I be added to the 
list of Contributors?
My JIRA username is: yongtang
Thanks!Yong   

Re: Contribution Request for Mesos

[Niklas Nielsen]

Hi Yong,

You should be on the list now.

Looking forward to your contributions!

Niklas

On 14 October 2015 at 12:29, Yong Tang  wrote:

> Hi
> After using Mesos and following Mesos project for quite some time, I would
> like to participate and contribute to the Mesos project. Could I be added
> to the list of Contributors?
> My JIRA username is: yongtang
> Thanks!Yong

Contribution Request for Mesos

[tommy xiao]

Hi
After using Mesos and following Mesos project for quite some time, I would
like to participate and contribute to the Mesos project. Could I be added
to the list of Contributors?
My JIRA username is: xds2000

-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Re: Contribution Request for Mesos

[Adam Bordelon]

Added. Now you can assign JIRAs to yourself.
Thanks for contributing!

On Wed, Oct 14, 2015 at 5:29 PM, tommy xiao  wrote:

> Hi
> After using Mesos and following Mesos project for quite some time, I would
> like to participate and contribute to the Mesos project. Could I be added
> to the list of Contributors?
> My JIRA username is: xds2000
>
> --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
>

Contribution Request for Mesos

[Jincheng Li]

Hi all,

I've been following the Mesos project for a bit and would like to
contribute. Could I be added to the list of contributors? My JIRA username
is jcli. Thanks!

Jincheng

Re: Contribution Request for Mesos

[Adam Bordelon]

Hi Jincheng,
You have been added as a contributor, and may now assign issues to yourself.
Welcome to the community!
-Adam-

On Sun, Aug 23, 2015 at 9:28 AM, Jincheng Li jcli@gmail.com wrote:

 Hi all,

 I've been following the Mesos project for a bit and would like to
 contribute. Could I be added to the list of contributors? My JIRA username
 is jcli. Thanks!

 Jincheng

Re: Mesos Contribution Request

[Alexander Rojas]

Hey Timothy,

Great to hear you are jumping into the ship. As Vinod pointed out, we are 
working already in an new HTTP based authentication design for Mesos. You can 
help us out be reading it and point out anything we had miss.


 On 05 Aug 2015, at 20:56, Timothy Anderegg timothy.ander...@gmail.com wrote:
 
 Thanks Vinod, I did see that, looks like a solid approach.  I'll continue
 to dig in and see where I can help.
 
 Tim
 
 On Wed, Aug 5, 2015 at 2:08 PM, Vinod Kone vinodk...@gmail.com wrote:
 
 Welcome Tim.
 
 This doc
 
 https://docs.google.com/document/d/1kM3_f7DSqXcE2MuERrLTGp_XMC6ss2wmpkNYDCY5rOM/edit#heading=h.bbxx6wwg3tpe
 
 might
 help you get a sense of the current state of authN and where it is going.
 
 On Wed, Aug 5, 2015 at 9:53 AM, Timothy Anderegg 
 timothy.ander...@gmail.com
 wrote:
 
 Yeah, I thought it was a good place to start :)  Thanks again!
 
 Tim
 
 On Wed, Aug 5, 2015 at 12:47 PM, Marco Massenzio ma...@mesosphere.io
 wrote:
 
 eh, contributing to documentation is the surest way of being loved by
 *any*
 OSS community :)
 
 There's a lot of activity currently around
 authentication/authorization,
 so
 I'm sure you'll have no trouble in finding stuff to contribute to.
 Thanks, Tim!
 
 *Marco Massenzio*
 *Distributed Systems Engineer*
 
 On Wed, Aug 5, 2015 at 9:35 AM, Timothy Anderegg 
 timothy.ander...@gmail.com
 wrote:
 
 Great, thanks Marco!  Ultimately I'm interested in helping with
 Kerberos
 authentication (would help with adoption of Mesos for us), but I'm
 planning
 to tackle some simpler things first as you suggest.  Right now I'm
 writing
 some of the authentication documentation, since that's missing
 currently
 (MESOS-1838), and will help prep me for more substantial work.
 
 -Tim
 
 On Wed, Aug 5, 2015 at 12:25 PM, Marco Massenzio 
 ma...@mesosphere.io
 wrote:
 
 Hi Tim,
 
 I've added you to the Contributors list, welcome to Apache Mesos
 and
 looking forward to your contributions!
 I assume you've obviously already looked up the Contributing page
 on
 mesos.apache.org and joined our Review Board (reviews.apache.org);
 the
 other one thing to look out for are tickets marked as 'newbie';
 they
 are
 usually a gentler introduction to our code base.
 
 Any other questions, please feel free to ask!
 Thanks for joining.
 
 *Marco Massenzio*
 *Distributed Systems Engineer*
 
 On Wed, Aug 5, 2015 at 7:57 AM, Timothy Anderegg 
 timothy.ander...@gmail.com
 wrote:
 
 Hello, I would like to get involved with the development of
 Mesos,
 my
 JIRA
 username is tanderegg, could I be added to the contributors list?
 Thanks,
 and let me know if you need any more info.
 
 Tim
 
 
 
 
 
 

Re: Mesos Contribution Request

[Timothy Anderegg]

Yeah, I thought it was a good place to start :)  Thanks again!

Tim

On Wed, Aug 5, 2015 at 12:47 PM, Marco Massenzio ma...@mesosphere.io
wrote:

 eh, contributing to documentation is the surest way of being loved by *any*
 OSS community :)

 There's a lot of activity currently around authentication/authorization, so
 I'm sure you'll have no trouble in finding stuff to contribute to.
 Thanks, Tim!

 *Marco Massenzio*
 *Distributed Systems Engineer*

 On Wed, Aug 5, 2015 at 9:35 AM, Timothy Anderegg 
 timothy.ander...@gmail.com
  wrote:

  Great, thanks Marco!  Ultimately I'm interested in helping with Kerberos
  authentication (would help with adoption of Mesos for us), but I'm
 planning
  to tackle some simpler things first as you suggest.  Right now I'm
 writing
  some of the authentication documentation, since that's missing currently
  (MESOS-1838), and will help prep me for more substantial work.
 
  -Tim
 
  On Wed, Aug 5, 2015 at 12:25 PM, Marco Massenzio ma...@mesosphere.io
  wrote:
 
   Hi Tim,
  
   I've added you to the Contributors list, welcome to Apache Mesos and
   looking forward to your contributions!
   I assume you've obviously already looked up the Contributing page on
   mesos.apache.org and joined our Review Board (reviews.apache.org); the
   other one thing to look out for are tickets marked as 'newbie'; they
 are
   usually a gentler introduction to our code base.
  
   Any other questions, please feel free to ask!
   Thanks for joining.
  
   *Marco Massenzio*
   *Distributed Systems Engineer*
  
   On Wed, Aug 5, 2015 at 7:57 AM, Timothy Anderegg 
   timothy.ander...@gmail.com
wrote:
  
Hello, I would like to get involved with the development of Mesos, my
   JIRA
username is tanderegg, could I be added to the contributors list?
   Thanks,
and let me know if you need any more info.
   
Tim
   
  
 

Re: Mesos Contribution Request

[Vinod Kone]

Welcome Tim.

This doc
https://docs.google.com/document/d/1kM3_f7DSqXcE2MuERrLTGp_XMC6ss2wmpkNYDCY5rOM/edit#heading=h.bbxx6wwg3tpe
might
help you get a sense of the current state of authN and where it is going.

On Wed, Aug 5, 2015 at 9:53 AM, Timothy Anderegg timothy.ander...@gmail.com
 wrote:

 Yeah, I thought it was a good place to start :)  Thanks again!

 Tim

 On Wed, Aug 5, 2015 at 12:47 PM, Marco Massenzio ma...@mesosphere.io
 wrote:

  eh, contributing to documentation is the surest way of being loved by
 *any*
  OSS community :)
 
  There's a lot of activity currently around authentication/authorization,
 so
  I'm sure you'll have no trouble in finding stuff to contribute to.
  Thanks, Tim!
 
  *Marco Massenzio*
  *Distributed Systems Engineer*
 
  On Wed, Aug 5, 2015 at 9:35 AM, Timothy Anderegg 
  timothy.ander...@gmail.com
   wrote:
 
   Great, thanks Marco!  Ultimately I'm interested in helping with
 Kerberos
   authentication (would help with adoption of Mesos for us), but I'm
  planning
   to tackle some simpler things first as you suggest.  Right now I'm
  writing
   some of the authentication documentation, since that's missing
 currently
   (MESOS-1838), and will help prep me for more substantial work.
  
   -Tim
  
   On Wed, Aug 5, 2015 at 12:25 PM, Marco Massenzio ma...@mesosphere.io
   wrote:
  
Hi Tim,
   
I've added you to the Contributors list, welcome to Apache Mesos and
looking forward to your contributions!
I assume you've obviously already looked up the Contributing page
 on
mesos.apache.org and joined our Review Board (reviews.apache.org);
 the
other one thing to look out for are tickets marked as 'newbie'; they
  are
usually a gentler introduction to our code base.
   
Any other questions, please feel free to ask!
Thanks for joining.
   
*Marco Massenzio*
*Distributed Systems Engineer*
   
On Wed, Aug 5, 2015 at 7:57 AM, Timothy Anderegg 
timothy.ander...@gmail.com
 wrote:
   
 Hello, I would like to get involved with the development of Mesos,
 my
JIRA
 username is tanderegg, could I be added to the contributors list?
Thanks,
 and let me know if you need any more info.

 Tim

   
  
 

Re: Mesos Contribution Request

[Timothy Anderegg]

Thanks Vinod, I did see that, looks like a solid approach.  I'll continue
to dig in and see where I can help.

Tim

On Wed, Aug 5, 2015 at 2:08 PM, Vinod Kone vinodk...@gmail.com wrote:

 Welcome Tim.

 This doc
 
 https://docs.google.com/document/d/1kM3_f7DSqXcE2MuERrLTGp_XMC6ss2wmpkNYDCY5rOM/edit#heading=h.bbxx6wwg3tpe
 
 might
 help you get a sense of the current state of authN and where it is going.

 On Wed, Aug 5, 2015 at 9:53 AM, Timothy Anderegg 
 timothy.ander...@gmail.com
  wrote:

  Yeah, I thought it was a good place to start :)  Thanks again!
 
  Tim
 
  On Wed, Aug 5, 2015 at 12:47 PM, Marco Massenzio ma...@mesosphere.io
  wrote:
 
   eh, contributing to documentation is the surest way of being loved by
  *any*
   OSS community :)
  
   There's a lot of activity currently around
 authentication/authorization,
  so
   I'm sure you'll have no trouble in finding stuff to contribute to.
   Thanks, Tim!
  
   *Marco Massenzio*
   *Distributed Systems Engineer*
  
   On Wed, Aug 5, 2015 at 9:35 AM, Timothy Anderegg 
   timothy.ander...@gmail.com
wrote:
  
Great, thanks Marco!  Ultimately I'm interested in helping with
  Kerberos
authentication (would help with adoption of Mesos for us), but I'm
   planning
to tackle some simpler things first as you suggest.  Right now I'm
   writing
some of the authentication documentation, since that's missing
  currently
(MESOS-1838), and will help prep me for more substantial work.
   
-Tim
   
On Wed, Aug 5, 2015 at 12:25 PM, Marco Massenzio 
 ma...@mesosphere.io
wrote:
   
 Hi Tim,

 I've added you to the Contributors list, welcome to Apache Mesos
 and
 looking forward to your contributions!
 I assume you've obviously already looked up the Contributing page
  on
 mesos.apache.org and joined our Review Board (reviews.apache.org);
  the
 other one thing to look out for are tickets marked as 'newbie';
 they
   are
 usually a gentler introduction to our code base.

 Any other questions, please feel free to ask!
 Thanks for joining.

 *Marco Massenzio*
 *Distributed Systems Engineer*

 On Wed, Aug 5, 2015 at 7:57 AM, Timothy Anderegg 
 timothy.ander...@gmail.com
  wrote:

  Hello, I would like to get involved with the development of
 Mesos,
  my
 JIRA
  username is tanderegg, could I be added to the contributors list?
 Thanks,
  and let me know if you need any more info.
 
  Tim