Re: Range-based for loops

[Benjamin Mahler]

No worries, thanks for the follow-up!

On Wed, Aug 5, 2015 at 6:20 PM, Michael Park  wrote:

> Looks like I introduced it initially, sorry about that.
>
> Michael, is there a plan to replace 'foreach' with range-based for loops?
>
>
> I've thought about this and I don't know exactly how we would want to do
> it as a community.
> I've filed MESOS-3214  with
> listing 2 possible approaches.
>
> Please share your thoughts and preferences there!
>
> Thanks,
>
> MPark.
>
> On 4 August 2015 at 20:19, Artem Harutyunyan  wrote:
>
>> We should also come up with the recommended way of dealing with
>> foreachpair and foreachvalue occurrences. I did a quick grep and there
>> seem to be over 900 places where foreach(value/pair) are used. It's
>> going to be quite a change (albeit a straightforward one), but we
>> should still be all for it :-).
>>
>> Cheers,
>> Artem.
>>
>>
>> On Tue, Aug 4, 2015 at 5:18 PM, Benjamin Mahler
>>  wrote:
>> > I noticed there was a single ranged-based for loop introduced in the
>> source
>> > tree:
>> >
>> >
>> https://github.com/apache/mesos/blob/master/src/tests/resources_tests.cpp#L1004
>> >
>> > Since this is the only one in the codebase AFAICT, I've removed it to
>> keep
>> > our use of 'foreach' consistent. Michael, is there a plan to replace
>> > 'foreach' with range-based for loops? Would just like there to be a
>> > consistent way to loop over containers. :)
>>
>
>

Re: Range-based for loops

[Michael Park]

Looks like I introduced it initially, sorry about that.

Michael, is there a plan to replace 'foreach' with range-based for loops?


I've thought about this and I don't know exactly how we would want to do it
as a community.
I've filed MESOS-3214  with
listing 2 possible approaches.

Please share your thoughts and preferences there!

Thanks,

MPark.

On 4 August 2015 at 20:19, Artem Harutyunyan  wrote:

> We should also come up with the recommended way of dealing with
> foreachpair and foreachvalue occurrences. I did a quick grep and there
> seem to be over 900 places where foreach(value/pair) are used. It's
> going to be quite a change (albeit a straightforward one), but we
> should still be all for it :-).
>
> Cheers,
> Artem.
>
>
> On Tue, Aug 4, 2015 at 5:18 PM, Benjamin Mahler
>  wrote:
> > I noticed there was a single ranged-based for loop introduced in the
> source
> > tree:
> >
> >
> https://github.com/apache/mesos/blob/master/src/tests/resources_tests.cpp#L1004
> >
> > Since this is the only one in the codebase AFAICT, I've removed it to
> keep
> > our use of 'foreach' consistent. Michael, is there a plan to replace
> > 'foreach' with range-based for loops? Would just like there to be a
> > consistent way to loop over containers. :)
>

Re: [Mesos][Patch] How to make the patches under review board link to a mesos bug

[Guangya Liu]

Got it. Thanks Kapil!

On Wed, Aug 5, 2015 at 6:07 PM, Kapil Arya  wrote:

> You need to click on the pencil icon near "Bugs:" and type in the Jira
> ticket number, e.g. "MESOS-1234". You can do this only if you are logged in
> into Reviewboard and have created the review request yourself.
>
> Kapil
>
> PS: The dev list doesn't allow images, so if you had attached any, they
> were discarded :-).
>
> On Wed, Aug 5, 2015 at 5:52 PM, Guangya Liu  wrote:
>
> > Hi Mesos,
> >
> > I see that there are some patches can be easily be directed to a mesos
> bug
> > by a link on the right side of the review board, how can I have this for
> my
> > patch?
> > ​
> >
> > Thanks,
> >
> > Guangya
> >
>

Re: mesos git commit: Revert "Add subscribe-> subscribed workflow for http frameworks"

[Benjamin Mahler]

My bad, I accidentally pushed out a patch that I had applied earlier. Build
should be back to normal now!

On Wed, Aug 5, 2015 at 4:47 PM,  wrote:

> Repository: mesos
> Updated Branches:
>   refs/heads/master dbf35da46 -> 586307e54
>
>
> Revert "Add subscribe-> subscribed workflow for http frameworks"
>
> This reverts commit 1709e8a82fdae6a10893f0cfb9d2fae144d6a7a8.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
> Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/586307e5
> Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/586307e5
> Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/586307e5
>
> Branch: refs/heads/master
> Commit: 586307e546955c23aadf0ed5bfae9e00c0228f86
> Parents: dbf35da
> Author: Benjamin Mahler 
> Authored: Wed Aug 5 16:47:36 2015 -0700
> Committer: Benjamin Mahler 
> Committed: Wed Aug 5 16:47:36 2015 -0700
>
> --
>  src/master/http.cpp   |  21 +--
>  src/master/master.cpp | 343 ++---
>  src/master/master.hpp |  36 -
>  3 files changed, 42 insertions(+), 358 deletions(-)
> --
>
>
>
> http://git-wip-us.apache.org/repos/asf/mesos/blob/586307e5/src/master/http.cpp
> --
> diff --git a/src/master/http.cpp b/src/master/http.cpp
> index 181db46..76e7080 100644
> --- a/src/master/http.cpp
> +++ b/src/master/http.cpp
> @@ -70,7 +70,6 @@ using process::http::InternalServerError;
>  using process::http::NotFound;
>  using process::http::NotImplemented;
>  using process::http::OK;
> -using process::http::Pipe;
>  using process::http::TemporaryRedirect;
>  using process::http::Unauthorized;
>  using process::http::UnsupportedMediaType;
> @@ -376,24 +375,10 @@ Future Master::Http::call(const Request&
> request) const
>  responseContentType = ContentType::PROTOBUF;
>}
>
> -  switch (call.type()) {
> -case scheduler::Call::SUBSCRIBE: {
> -  Pipe pipe;
> -  OK ok;
> +  // Silence unused warning for now.
> +  (void)responseContentType;
>
> -  ok.type = Response::PIPE;
> -  ok.reader = pipe.reader();
> -
> -  master->subscribe(
> -  call.subscribe(),
> -  responseContentType,
> -  pipe.writer());
> -
> -  return ok;
> -}
> -default:
> -  break;
> -  }
> +  // TODO(anand): Handle the call.
>
>return NotImplemented();
>  }
>
>
> http://git-wip-us.apache.org/repos/asf/mesos/blob/586307e5/src/master/master.cpp
> --
> diff --git a/src/master/master.cpp b/src/master/master.cpp
> index e738607..50b9824 100644
> --- a/src/master/master.cpp
> +++ b/src/master/master.cpp
> @@ -1771,227 +1771,6 @@ void Master::reregisterFramework(
>
>
>  void Master::subscribe(
> -const scheduler::Call::Subscribe& subscribe,
> -ContentType contentType,
> -Pipe::Writer writer)
> -{
> -  // TODO(anand): We need to ensure that framework is authenticated
> -  // before calling into this function. If not, we need to build the
> -  // authentication logic here before invoking subscribe(...)
> -
> -  const FrameworkInfo& frameworkInfo = subscribe.framework_info();
> -
> -  LOG(INFO) << "Received registration request for"
> -<< " http framework '" << frameworkInfo.name() << "'";
> -
> -  // Assign a new FrameworkID.
> -  FrameworkInfo frameworkInfo_ = frameworkInfo;
> -  frameworkInfo_.mutable_id()->CopyFrom(newFrameworkId());
> -
> -  Framework* framework = new Framework(
> -  this,
> -  frameworkInfo_,
> -  writer,
> -  contentType);
> -
> -  // TODO(anand): Add validation/authorization logic before we invoke
> -  // the continuation function.
> -  this->_subscribe(framework, subscribe);
> -}
> -
> -
> -void Master::_subscribe(
> -Framework* framework,
> -const scheduler::Call::Subscribe& subscribe)
> -{
> -  const FrameworkInfo& frameworkInfo = subscribe.framework_info();
> -
> -  if (!frameworkInfo.has_id() || frameworkInfo.id() == "") {
> -// TODO(anand): Make '(re-)registerFramework()' also call into
> -// this method (MESOS-3182).
> -LOG(INFO) << "Registering framework " << *framework
> -  << " with checkpointing "
> -  << (framework->info.checkpoint() ? "enabled" : "disabled")
> -  << " and capabilities " << framework->info.capabilities();
> -
> -// TODO(vinod): Deprecate this in favor of authorization.
> -bool rootSubmissions = flags.root_submissions;
> -
> -if (framework->info.user() == "root" && rootSubmissions == false) {
> -  LOG(INFO) << "Framework " << *framework << " registering as root,
> but "
> -<< "root submissions are disabled on this cluster";
> -  FrameworkErrorMessage message;
> -  message.set_message("User 'root' is not allowed to run frameworks");
> -

Re: Apache Mesos Community Sync

[Vinod Kone]

We'll have the next community sync tomorrow at 3 PM PST.

Please add items to agenda

.

Thanks,

On Thu, Jul 2, 2015 at 11:24 AM, Joris Van Remoortere 
wrote:

> Reminder: The Mesos Community Developer Sync will be happening today at
> 3pm Pacific.
>
> To participate remotely, join the Google hangout:
> https://plus.google.com/hangouts/_/twitter.com/mesos-sync
>
> On Thu, Jun 18, 2015 at 7:22 AM, Adam Bordelon  wrote:
>
>> Reminder: We're hosting a developer community sync at Mesosphere HQ this
>> morning from 9-11am Pacific.
>>
>> The agenda is pretty bare, so please add more topics you would like to
>> discuss:
>>
>> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit
>>
>> If you want to join in person, just show up to 88 Stevenson St, ring the
>> buzzer, take the elevator up to 2nd floor, and then you can take the stairs
>> up to the 3rd floor dining room, or ask somebody to let you up the elevator
>> to the 3rd floor.
>>
>> To participate remotely, join the Google hangout:
>> https://plus.google.com/hangouts/_/mesosphere.io/mesos-developer
>>
>> On Mon, Jun 15, 2015 at 10:46 AM, Adam Bordelon 
>> wrote:
>>
>>> As previously mentioned, we would like to host additional Mesos
>>> developer syncs at our new Mesosphere HQ at 88 Stevenson St (tucked behind
>>> Market & 2nd), starting this Thursday from 9-11am Pacific. We opted for an
>>> earlier slot so that the European developer community can participate.
>>>
>>> Now that we are having these more frequently, it would be great to dive
>>> deeper into designs for upcoming features as well as discuss longstanding
>>> issues. While high-level status updates are useful, they should be a small
>>> part of these meetings so that we can address issues currently facing our
>>> developers.
>>>
>>> Please add agenda items to the same doc we've been using for previous
>>> meetings' Agenda/Notes:
>>>
>>> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit
>>>
>>> Join in person if you can, or join remotely via hangout:
>>> https://plus.google.com/hangouts/_/mesosphere.io/mesos-developer
>>>
>>> Thanks,
>>> -Adam-
>>>
>>>
>>> On Thu, May 28, 2015 at 10:08 AM, Vinod Kone 
>>> wrote:
>>>
 Cool.

 Here's the agenda doc
 <
 https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#
 >
 for next week that folks can fill in.

 On Thu, May 28, 2015 at 9:52 AM, Adam Bordelon 
 wrote:

 > Looks like next week, Thursday June 4th on my calendar.
 > I thought it was always the first Thursday of the month.
 >
 > On Thu, May 28, 2015 at 9:33 AM, Vinod Kone 
 wrote:
 >
 > > Do we have community sync today or next week? I'm a bit confused.
 > >
 > > @vinodkone
 > >
 > > > On Apr 1, 2015, at 3:18 AM, Adam Bordelon 
 wrote:
 > > >
 > > > Reminder: We're having another Mesos Developer Community Sync this
 > > > Thursday, April 2nd from 3-5pm Pacific.
 > > >
 > > > Agenda:
 > > >
 > >
 >
 https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit?usp=sharing
 > > > To Join: follow the BlueJeans instructions from the recurring
 meeting
 > > > invite at the start of this thread.
 > > >
 > > >> On Fri, Mar 6, 2015 at 11:11 AM, Vinod Kone <
 vinodk...@apache.org>
 > > wrote:
 > > >>
 > > >> Hi folks,
 > > >>
 > > >> We are planning to do monthly Mesos community meetings.
 Tentatively
 > > these
 > > >> are scheduled to occur on 1st Thursday of every month at 3 PM
 PST. See
 > > >> below for details to join the meeting remotely.
 > > >>
 > > >> This is a forum to ask questions/discuss about upcoming features,
 > > process
 > > >> etc. Everyone is welcome to join. Feel free to add items to the
 agenda
 > > for
 > > >> the next meeting here
 > > >> <
 > > >>
 > >
 >
 https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit?usp=sharing
 > > >> .
 > > >>
 > > >> Cheers,
 > > >>
 > > >> On Thu, Mar 5, 2015 at 11:23 AM, Vinod Kone via Blue Jeans
 Network <
 > > >> inv...@bluejeans.com> wrote:
 > > >>
 > > >>>[image: Blue Jeans]    Vinod Kone
 > > >>>  has invited you to a video meeting.
  Meeting
 > > >> Title: Apache Mesos Community Sync
 > > >>>  Meeting Time: Every 4th week on Thursday • from March 5, 2015
 • 3
 > p.m.
 > > >>> PST / 2 hrs  Join Meeting
 > > >>> <
 > > >>
 > >
 https://bluejeans.com/272369669?ll=en&g=mrsxmqdnmvzw64zomfygcy3imuxg64th
 > >
 > > >>> --
 > > >>>  Connecting directly from a room system?
 > > >>>
 > > >>> 1) Dial: 199.48.152.1

Re: [Mesos][Patch] How to make the patches under review board link to a mesos bug

[Kapil Arya]

You need to click on the pencil icon near "Bugs:" and type in the Jira
ticket number, e.g. "MESOS-1234". You can do this only if you are logged in
into Reviewboard and have created the review request yourself.

Kapil

PS: The dev list doesn't allow images, so if you had attached any, they
were discarded :-).

On Wed, Aug 5, 2015 at 5:52 PM, Guangya Liu  wrote:

> Hi Mesos,
>
> I see that there are some patches can be easily be directed to a mesos bug
> by a link on the right side of the review board, how can I have this for my
> patch?
> ​
>
> Thanks,
>
> Guangya
>

[Mesos][Patch] How to make the patches under review board link to a mesos bug

[Guangya Liu]

Hi Mesos,

I see that there are some patches can be easily be directed to a mesos bug
by a link on the right side of the review board, how can I have this for my
patch?
​

Thanks,

Guangya

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  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 
> > 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: Re-opening an issue (aka - Un-Resolving it)

[Vinod Kone]

Ah. That's confusing. Is there no way we can fix the schema to not do this?
I'm assuming you already asked INFRA?

On a side note, is it possible to make the "Shepherd" field mandatory when
a task transitions from Accepted --> Assigned? I think this will force
users to find shepherds before they start working on an issue. Will also
help shepherds guide what issues we want new contributors to focus on.

On Wed, Aug 5, 2015 at 11:34 AM, Marco Massenzio 
wrote:

> Dear all:
>
> When re-opening an issue (for whatever reason) moving it from its Resolved
> state (to either Open or In progress) Jira will *not* update the
> "Resolution" field back to "Unresolved".
>
> This means that (a) you now have a confusing "Open but Resolution: Fixed"
> issue and (b) the issue link/display (eg, MESOS-1234) will appear with a
> misleading strike-through in Sprint and Kanban Boards.
>
> The solution is rather simple, albeit fiendishly unintuitive:
>
> 1) Resolve (again) the issue;
> 2) in the resolve dialog that pops up, choose "Unresolved" for its
> Resolution field;
> 3) move it back to whatever state makes sense (Open, In Progress, etc.)
>
> Hope this helps!
>
> *Marco Massenzio*
> *Distributed Systems Engineer*
>

Re-opening an issue (aka - Un-Resolving it)

[Marco Massenzio]

Dear all:

When re-opening an issue (for whatever reason) moving it from its Resolved
state (to either Open or In progress) Jira will *not* update the
"Resolution" field back to "Unresolved".

This means that (a) you now have a confusing "Open but Resolution: Fixed"
issue and (b) the issue link/display (eg, MESOS-1234) will appear with a
misleading strike-through in Sprint and Kanban Boards.

The solution is rather simple, albeit fiendishly unintuitive:

1) Resolve (again) the issue;
2) in the resolve dialog that pops up, choose "Unresolved" for its
Resolution field;
3) move it back to whatever state makes sense (Open, In Progress, etc.)

Hope this helps!

*Marco Massenzio*
*Distributed Systems Engineer*

Re: Prepping for next release

[Vinod Kone]

Hi,

The tracking ticket for the 0.24.0 release is
https://issues.apache.org/jira/browse/MESOS-2562

The main feature of this release is going to be v1 (beta) release of the
HTTP scheduler API.

Hoping to cut an RC early next week, so if there's anything you absolutely
need to be in 0.24.0 please land them by EOW.

Thanks,

On Tue, Jul 21, 2015 at 4:10 PM, Adam Bordelon  wrote:

> Thanks, Vinod.
>
> I've got a handful of JIRAs I'd really like to see land in 0.24.0.
> https://issues.apache.org/jira/browse/MESOS-2559 Do not use
> RunTaskMessage.framework_id.
> https://issues.apache.org/jira/browse/MESOS-2600 Add /reserve and
> /unreserve endpoints on the master for dynamic reservation
> https://issues.apache.org/jira/browse/MESOS-2998 Disable Persistent
> Volumes, Dynamic Reservations via master flags
> https://issues.apache.org/jira/browse/MESOS-3050 Failing ROOT_ tests in
> 0.23.0-rc3 on CentOS 7.1
> https://issues.apache.org/jira/browse/MESOS-3079 `sudo make distcheck`
> fails on Ubuntu 14.04 (and possibly other OSes too)
>
> I understand your desire to untarget the majority of the tickets, since
> it's a time-based release, but we might want to keep some of these targeted
> so we can track the priority issues. When the actual rc1 cut date
> approaches, it's pretty easy to aggressively push things out of the release
> that haven't made it. Let me know what you think.
>
> Cheers,
> -A-
>
>
> On Tue, Jul 21, 2015 at 11:02 AM, Vinod Kone  wrote:
>
> > Hi folks,
> >
> > I will be the release manager for the upcoming release (ETA early
> August).
> >
> > To prep for the release (and make my life easy) I'm planning to remove
> the
> > target versions for all *unresolved* tickets that have a target version
> > 0.24.0.
> >
> > I would like folks to explicitly set the target version to 0.24.0* for
> > tickets they want to absolutely land in the next release (keeping in mind
> > the time frame). If you are unsure, please reach out to me or reply to
> this
> > thread.
> >
> > The main blocking feature for this release is going to the new HTTP API.
> >
> > Thanks,
> > Vinod
> >
> > P.S. If things go according to plan we might make this 1.0 release!
> >
>

Re: Mesos Contribution Request

[Vinod Kone]

Welcome Tim.

This doc

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  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 
> 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 
> > > 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 
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 
> > 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

[Marco Massenzio]

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  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 
> 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]

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 
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

[Marco Massenzio]

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  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
>

Mesos Contribution Request

[Timothy Anderegg]

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

Announcing MesosCon Europe. CFP and Early-Bird Registration Now Open

[Dave Lester]

We just went live with a blog post[1] drafted by Michael Hausenblas
announcing MesosCon Europe[2], a European conference for the Apache
Mesos community. The inaugural MesosCon EU will take place in
Dublin October 8-9, 2015 and both the CFP and early-bird
registration are now open.

Help us get the word out and join us at MesosCon Europe!
http://events.linuxfoundation.org/events/mesoscon-europe

Here's Michael's post pasted below:
> The Mesos community has been growing steadily over the past years and
> on behalf of the #MesosCon Program Committee I’m excited and proud to
> be able to share the great news with you: MesosCon is now a world-wide
> event and this fall it comes to Europe. Organized by the Apache Mesos
> community, #MesosCon Europe brings together users and developers to
> share and learn about the project and its growing ecosystem.
>
> MesosCon Europe 2015 will take place in Dublin, Ireland and feature a
> full day of sessions to learn more about the Mesos core, an ecosystem
> developed around the project, and related technologies. The program
> will include workshops to get started with Mesos, keynote speakers
> from industry leaders, and sessions led by adopters and contributors.
> Day two will feature a hackathon held at the conference.
>
> Now is a good time to start preparing yourself for #MesosCon Europe:
> no matter if you want to contribute through a talk submission (see the
> CfP for details) or want to support us through a sponsorship. Stay
> tuned via @MesosCon and mark these dates in your calendar:
>
> * Early bird registration closes: 24 August 2015
> * CfP deadline: 25 August 2015
> * Schedule announced: 15 September 2015
> * Conference dates: 8 and 9 October 2015
>
> More info: http://events.linuxfoundation.org/events/mesoscon-europe
>
> Help us make this first European #MesosCon event a big success by
> spreading the word and register today!


Links:

  1. http://mesos.apache.org/blog/mesoscon-goes-europe/
  2. http://events.linuxfoundation.org/events/mesoscon-europe