You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov> on 2013/02/08 07:08:25 UTC

Add myself as a mentor?

Hey Apache Mesos Community,

Wondering if you could use some mentorship help? I'd be happy to be around
to VOTE on releases, and help guide you guys in the Apache way. If you are
OK with this, I will add myself as a mentor to the project.

A couple of questions:

1. When was the last release for the project? Or, has their been a release
yet?
2. How many new committers have you guys added since you joined the
Incubator?
3. Is the code license/IP clear?
4. Any blockers that you guys see to graduation?

Cheers,
Chris


Where's the VOTE thread? (was Re: Add myself as a mentor?)

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Ben,

Sorry just caught the part about you sending up a VOTE thread but it not
going through RE: the release?

I checked: 
http://mail-archives.apache.org/mod_mbox/incubator-mesos-dev/201302.mbox/br
owser

And don't see any [VOTE] thread. Can you try again to send it? What
account are you sending it from? I can double check and make sure you are
subscribed to the list (speaking of which, which one did you send it to?)

Cheers,
Chris

On 2/8/13 8:27 PM, "Mattmann, Chris A (388J)"
<ch...@jpl.nasa.gov> wrote:

>Hi Ben,
>
>Sounds like you guys are in great shape!
>
>On 2/7/13 11:15 PM, "Benjamin Hindman" <be...@eecs.berkeley.edu> wrote:
>
>>Chris,
>>
>>We would be honored to have you as a mentor! I actually just sent out a
>>vote email tonight for 0.10.0 RC4 (not sure when the email will surface,
>>I've had some trouble posting to general@ in the past). I can't imagine
>>anyone that would not be okay with your support, so please by all means
>>add
>>yourself as a mentor.
>
>Awesome, I've done so in r1444326 of the incubator repo.
>
>[chipotle:~/tmp/incubator] mattmann% svn commit -m "Add Chris Mattmann as
>Mesos mentor, and updated all dates in podling.xml"
>Sending        mesos.xml
>Transmitting file data .
>Committed revision 1444326.
>[chipotle:~/tmp/incubator] mattmann%
>
>
>
>>
>>1. When was the last release for the project? Or, has their been a
>>release
>>> yet?
>>>
>>
>>There has been one, and hopefully the next will be in 72 hours! We have
>>more queued up as well (that we've already tagged public SVN branches for
>>but haven't finalized through the release process).
>
>Great, that's awesome news. Looks like you guys released on 05-08-2012. I
>used this to update your podling.xml questions regarding:
>
>            <tr>
>              <td>2012-05-08</td>
>              <td>Check and make sure that for all code included with the
>distribution
>                  that is not under the Apache license, we have the right
>to combine
>                  with Apache-licensed code and redistribute.
>               </td>
>            </tr>
>            <tr>
>              <td>2012-05-08</td>
>              <td>Check and make sure that all source code distributed by
>the project
>                  is covered by one or more of the following approved
>licenses: Apache,
>                  BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something
>with essentially
>                  the same terms.</td>
>            </tr>
>
>Assuming that going through the Incubator release process validated this.
>
>
>>
>>
>>> 2. How many new committers have you guys added since you joined the
>>> Incubator?
>>>
>>
>>Only 1 so far unfortunately. I think we'll easily be able to add another
>>in
>>the next few months.
>
>That's fine. It would be nice to identify one or two more but not a strict
>requirement. Looks like in the few days I've been here that there is
>activity from >1 person, which is great.
>
>>
>>
>>> 3. Is the code license/IP clear?
>>>
>>
>>Yes.
>
>Excellent.
>
>>
>>
>>> 4. Any blockers that you guys see to graduation?
>>>
>>
>>Mostly diversity of community. We'll be at ApacheCon this year and we
>>hope
>>to possibly help rectify that soon.
>
>Awesome. Diversity is important, but not a strict requirement. You guys
>are doing great and on the right path. Let's set a target in the next few
>months to start preparing for graduation, and a release now will
>definitely be great evidence that the community is ready to graduate.
>
>Thanks Ben!
>
>Cheers,
>Chris
>
>>
>


Re: Add myself as a mentor?

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hi Ben,

Sounds like you guys are in great shape!

On 2/7/13 11:15 PM, "Benjamin Hindman" <be...@eecs.berkeley.edu> wrote:

>Chris,
>
>We would be honored to have you as a mentor! I actually just sent out a
>vote email tonight for 0.10.0 RC4 (not sure when the email will surface,
>I've had some trouble posting to general@ in the past). I can't imagine
>anyone that would not be okay with your support, so please by all means
>add
>yourself as a mentor.

Awesome, I've done so in r1444326 of the incubator repo.

[chipotle:~/tmp/incubator] mattmann% svn commit -m "Add Chris Mattmann as
Mesos mentor, and updated all dates in podling.xml"
Sending        mesos.xml
Transmitting file data .
Committed revision 1444326.
[chipotle:~/tmp/incubator] mattmann%



>
>1. When was the last release for the project? Or, has their been a release
>> yet?
>>
>
>There has been one, and hopefully the next will be in 72 hours! We have
>more queued up as well (that we've already tagged public SVN branches for
>but haven't finalized through the release process).

Great, that's awesome news. Looks like you guys released on 05-08-2012. I
used this to update your podling.xml questions regarding:

            <tr>
              <td>2012-05-08</td>
              <td>Check and make sure that for all code included with the
distribution
                  that is not under the Apache license, we have the right
to combine
                  with Apache-licensed code and redistribute.
               </td>
            </tr>
            <tr>
              <td>2012-05-08</td>
              <td>Check and make sure that all source code distributed by
the project
                  is covered by one or more of the following approved
licenses: Apache,
                  BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something
with essentially
                  the same terms.</td>
            </tr>

Assuming that going through the Incubator release process validated this.


>
>
>> 2. How many new committers have you guys added since you joined the
>> Incubator?
>>
>
>Only 1 so far unfortunately. I think we'll easily be able to add another
>in
>the next few months.

That's fine. It would be nice to identify one or two more but not a strict
requirement. Looks like in the few days I've been here that there is
activity from >1 person, which is great.

>
>
>> 3. Is the code license/IP clear?
>>
>
>Yes.

Excellent.

>
>
>> 4. Any blockers that you guys see to graduation?
>>
>
>Mostly diversity of community. We'll be at ApacheCon this year and we hope
>to possibly help rectify that soon.

Awesome. Diversity is important, but not a strict requirement. You guys
are doing great and on the right path. Let's set a target in the next few
months to start preparing for graduation, and a release now will
definitely be great evidence that the community is ready to graduate.

Thanks Ben!

Cheers,
Chris

>


Re: Add myself as a mentor?

Posted by Benjamin Hindman <be...@eecs.berkeley.edu>.
Chris,

We would be honored to have you as a mentor! I actually just sent out a
vote email tonight for 0.10.0 RC4 (not sure when the email will surface,
I've had some trouble posting to general@ in the past). I can't imagine
anyone that would not be okay with your support, so please by all means add
yourself as a mentor.

1. When was the last release for the project? Or, has their been a release
> yet?
>

There has been one, and hopefully the next will be in 72 hours! We have
more queued up as well (that we've already tagged public SVN branches for
but haven't finalized through the release process).


> 2. How many new committers have you guys added since you joined the
> Incubator?
>

Only 1 so far unfortunately. I think we'll easily be able to add another in
the next few months.


> 3. Is the code license/IP clear?
>

Yes.


> 4. Any blockers that you guys see to graduation?
>

Mostly diversity of community. We'll be at ApacheCon this year and we hope
to possibly help rectify that soon.