You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Ross Gardler <rg...@opendirective.com> on 2012/02/04 02:06:51 UTC

Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

My biggest problem is that the proposal moves undefined responsibilities to
ComDev while none of the candidates have actually spoken to ComDev about
this.

Doesn't that strike the candidates as a little odd?

l want to know what ComDev is being asked to do. The proposal in the wiki
is not clear in this regard and a number of discussion questions remain
unanswered.

I realise I've made it clear that I don't object, in principle, but I'm
only one member of ComDev. Furthermore I've made it clear I'm having
difficulty keeping up at the moment due to other commitments. As a result
of these two facts I'm not willing to sign ComDev up to an, as yet,
undefined role. I request that someone, shows ComDev, and in particular
myself as VP ComDev, tasks to us rather than about us.

Do any of the candidates want to take a little time to define the role they
see for ComDev?

Ross

Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

Posted by Luciano Resende <lu...@gmail.com>.
On Sun, Feb 5, 2012 at 10:29 PM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> On Sat, Feb 4, 2012 at 2:06 AM, Ross Gardler <rg...@opendirective.com> wrote:
>> My biggest problem is that the proposal moves undefined responsibilities to
>> ComDev while none of the candidates have actually spoken to ComDev about
>> this....
>
> As a comdev PMC member, I am opposed to making that PMC responsible
> for the incubator.apache.org docs. I don't think comdev has any spare
> capacity at the moment, so I don't see the docs improving there.
>
> -Bertrand
>
> [1] http://wiki.apache.org/incubator/IncubatorDeconstructionProposal
>

+1, with my comdev PMC hat.


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

Posted by Ross Gardler <rg...@opendirective.com>.
Thanks Bertrand.

I hope that ComDev can help with the future incubation. However, it is a
small PMC and thus any transition of responsibilities must be done in a
controlled and managed way.

Ross

Sent from my mobile device, please forgive errors and brevity.
On Feb 6, 2012 6:30 AM, "Bertrand Delacretaz" <bd...@apache.org>
wrote:

> On Sat, Feb 4, 2012 at 2:06 AM, Ross Gardler <rg...@opendirective.com>
> wrote:
> > My biggest problem is that the proposal moves undefined responsibilities
> to
> > ComDev while none of the candidates have actually spoken to ComDev about
> > this....
>
> As a comdev PMC member, I am opposed to making that PMC responsible
> for the incubator.apache.org docs. I don't think comdev has any spare
> capacity at the moment, so I don't see the docs improving there.
>
> -Bertrand
>
> [1] http://wiki.apache.org/incubator/IncubatorDeconstructionProposal
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 2/6/2012 12:29 AM, Bertrand Delacretaz wrote:
> On Sat, Feb 4, 2012 at 2:06 AM, Ross Gardler <rg...@opendirective.com> wrote:
>> My biggest problem is that the proposal moves undefined responsibilities to
>> ComDev while none of the candidates have actually spoken to ComDev about
>> this....
> 
> As a comdev PMC member, I am opposed to making that PMC responsible
> for the incubator.apache.org docs. I don't think comdev has any spare
> capacity at the moment, so I don't see the docs improving there.
> 
> -Bertrand
> 
> [1] http://wiki.apache.org/incubator/IncubatorDeconstructionProposal

Note that I had proposed something slightly different, where ComDev would
own all process docs which apply to the smooth functioning of all projects,
incubating or TLP.  Its guidelines wouldn't be focused on IP for example
(that's on the VP, Legal) but on the health and well being of project
communities.  Most of these documents are already written, and simply need
to be updated to state "Here are recommendations to all projects; these
are mandatory requirements for incubating projects".

Incubation docs, which are rules by-reference-to the general process docs,
plus the incubation wiki would all still be on VP, Project Incubation, and
their small officer committee to edit and maintain them.

I'd gather that you and Luciano don't believe that the committee has even
that bandwidth.  But I'd suggest there are individuals at incubator whose
primary interest is documenting the process.  If the ComDev adopted these
general documents, I trust you would gather new participants at ComDev.

By filtering "incubation rules" as part of VP, Project Incubation role
along with the board's decisions, those debates don't have to fall onto
ComDev.  If ComDev wants to switch a general suggestion into a requirement
or a requirement into a suggestion for all TLP's, that would be for them
to discuss and increase the traffic on the ComDev list.

Again, the very guts of the Chris proposed deconstruction is that there
are rules, and there are recommendations for every ASF project to follow,
and this artificial incubating v.s. tlp distinction is a bit absurd.  The
only delta should those few suggestions to all projects which are actually
so important that they are requirements on the incubating projects, until
graduation.

Note that transitioning "best practices" documentations into asf-wide,
www.apache.org/dev/* resources under ComDev could happen at any point,
independent of all the proposals on the table.  If it's what both ComDev
and Incubator want to do.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Sat, Feb 4, 2012 at 2:06 AM, Ross Gardler <rg...@opendirective.com> wrote:
> My biggest problem is that the proposal moves undefined responsibilities to
> ComDev while none of the candidates have actually spoken to ComDev about
> this....

As a comdev PMC member, I am opposed to making that PMC responsible
for the incubator.apache.org docs. I don't think comdev has any spare
capacity at the moment, so I don't see the docs improving there.

-Bertrand

[1] http://wiki.apache.org/incubator/IncubatorDeconstructionProposal

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: too much traffic here

Posted by Christian Grobmeier <gr...@gmail.com>.
On Sat, Feb 4, 2012 at 7:47 PM, Doug Cutting <cu...@apache.org> wrote:
> On 02/04/2012 09:15 AM, Mattmann, Chris A (388J) wrote:
>> We both care about this stuff, which is why we keep replying. I'm happy
>> to continue to reply, so long as you are when I feel it's warranted. I've
>> ignored a few of them that I didn't have the energy to, but that's the point
>> of a mailing list. At the end of the day, I hope with the diligence and effort
>> I've provided to reply to folks concerns (whether they think I've replied
>> or addressed them or not), I am basically brain dumping and trying to
>> not leave any question as to what my opinions are.
>
> Chris & others,
>
> Please do not feel obliged to answer every response to your messages
> here.  That does not scale well.  There are a lot of people who read
> this list.  Each message sent is equivalent to taking the floor in a
> meeting with all of these people in the room.  Please pause to consider
> that before responding or folks will start to leave this room.
>
> A best practice on a list with this many members is to respond
> thoughtfully on each thread just once per day.  Try to keep your
> responses short, sticking to the points which are most important to you.
>  Then wait, giving folks who might only read the list once a day a
> chance to respond to each of your messages.  Use this time to gauge the
> general response of the community.  Then try to respond to the list as a
> whole rather than individually to each member of the list.

Chris is one with a radical suggestion, the others are many. It is
very likely, that the one with a radical suggestion needs to respond
to many questions/concerns/etc and needs more emails than the other
people. Acting like you said is a unbalanced discussion. If you have
problems with the content of this list subscribe to:
general-digest-subscribe
read the mail archive or try to get your email filter to work. Gmail
offers "mute"

Cheers
Christian
(one of the guys who can't follow all emails here)

> Thanks,
>
> Doug
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>



-- 
http://www.grobmeier.de
https://www.timeandbill.de

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


too much traffic here

Posted by Doug Cutting <cu...@apache.org>.
On 02/04/2012 09:15 AM, Mattmann, Chris A (388J) wrote:
> We both care about this stuff, which is why we keep replying. I'm happy
> to continue to reply, so long as you are when I feel it's warranted. I've
> ignored a few of them that I didn't have the energy to, but that's the point
> of a mailing list. At the end of the day, I hope with the diligence and effort
> I've provided to reply to folks concerns (whether they think I've replied
> or addressed them or not), I am basically brain dumping and trying to 
> not leave any question as to what my opinions are. 

Chris & others,

Please do not feel obliged to answer every response to your messages
here.  That does not scale well.  There are a lot of people who read
this list.  Each message sent is equivalent to taking the floor in a
meeting with all of these people in the room.  Please pause to consider
that before responding or folks will start to leave this room.

A best practice on a list with this many members is to respond
thoughtfully on each thread just once per day.  Try to keep your
responses short, sticking to the points which are most important to you.
 Then wait, giving folks who might only read the list once a day a
chance to respond to each of your messages.  Use this time to gauge the
general response of the community.  Then try to respond to the list as a
whole rather than individually to each member of the list.

Thanks,

Doug

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

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

On Feb 4, 2012, at 9:03 AM, Ross Gardler wrote:

> Chris, seriously, take a break. You are not hearing what I'm trying to  say
> and therefore not answering my concerns, directly at least.

I could say the same thing to you. :) 

We both care about this stuff, which is why we keep replying. I'm happy
to continue to reply, so long as you are when I feel it's warranted. I've
ignored a few of them that I didn't have the energy to, but that's the point
of a mailing list. At the end of the day, I hope with the diligence and effort
I've provided to reply to folks concerns (whether they think I've replied
or addressed them or not), I am basically brain dumping and trying to 
not leave any question as to what my opinions are. 

> 
> For an example see where you use the word failure in this reply - that word
> has no bearing on anything I have said, yet you directly attribute it to
> me.

Ross, read your email. You said:

>> 
>> 
>> Arguably, legal and the Legal Committee have a hand in this, no?
>> I'm not sure it was entirely managed by the IPMC before.
> 
> Again, I agree the IPMC has not always worked, but it has not always failed
> either.

You said "failed", suggesting I had implied the Incubator was a failure, or 
suggesting I don't know what to be honest. But you used the word, not me, buddy.

> 
> I've made up my mind about how I feel about this proposal. In general I
> like it. I have some concerns that I will express in a summary document
> that I'll share with ComDev. At this point b I'm not sure if my concerns
> are misplaced our not.

Your concerns are valid. I hope you can agree that at least when you've tried
to raise one, I've tried to reply to it; whether it's to your satisfaction or not
that's up to you, but at least I've tried.

> 
> Thanks for taking the time to try and understand my issues. Enjoy the rest
> of your weekend.

You too, dude. I'm sure at some point, we'll all sit down have a beer 
about this stuff. In the interim, I'll set up the bastille (ooops, I mean, sorry
Benson, I didn't mean that.... tee hee)

Cheers,
Chris

> 
> Sent from my mobile device, please forgive errors and brevity.
> On Feb 4, 2012 3:57 PM, "Mattmann, Chris A (388J)" <
> chris.a.mattmann@jpl.nasa.gov> wrote:
> 
>> Hi Ross,
>> 
>> On Feb 4, 2012, at 2:36 AM, Ross Gardler wrote:
>> 
>>> Sent from my mobile device, please forgive errors and brevity.
>>> On Feb 4, 2012 3:41 AM, "Mattmann, Chris A (388J)" <
>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>>> [...snip...]
>>>>> Who fixes it?
>>>> 
>>>> The project's PMC. And if not, the project's VP. And if not that, the
>>> board,
>>>> or the membership. Just like the current way it works for existing TLPs.
>>> 
>>> if l the "membership" what is the channel used and who is responsible for
>>> ensuring that channel works?
>> 
>> The same channel that exists today for normal projects. The board is
>> elected by the membership. If the board doesn't fix the problem for the
>> project, and the membership is unpleased, the members elect a new
>> board that will fix it. Or they won't.
>> 
>>> 
>>>> 
>>>>> Who is maintaining the standards with respect to IP
>>>>> management?
>>>> 
>>>> How much work is there maintaing them? What's left to do?
>>> 
>>> I mean in individual projects, not in defining policy. Even in the
>> poddling
>>> that I've felt would benefit from this proposal the RM has learned by his
>>> mistakes. Some of which were caught by IPMC review when an additional
>> vote
>>> was needed.
>> 
>> Sure, and in my proposal it'll be caught by review of having 3 ASF members
>> on the project; by actually signing up strong ASF members (or "mentors")
>> to the project (as Benson said) who care about that stuff (release review,
>> etc.), and by having
>> a VP for the project. Or by the board. Or by the legal committee.
>> 
>> If you think about it, I'm simply proposing to use what's there, and to
>> move more towards the existing foundation resources, than to pretend
>> that the IPMC was the only place that we could get this information from.
>> A lot of the passionate legal folks or release review folks in the IPMC
>> (ant, Sam, etc.) are also members of the legal committee, and/or lurk
>> there. A lot of the release passionate folks (Joe S., myself etc.) also
>> lurk in other
>> places that will see releases happening (infra@, etc.). It's not putting
>> extra
>> burden on them to ask them to flag what they see, or provide advice.
>> They're
>> doing that already.
>> 
>>> Who provides these cross-checks?
>> 
>> See above.
>> 
>>> 
>>> You asked if a project couldn't muster the binding votes on a release,
>>> what's it doing on the incubator. This project couldn't, but it is still
>>> graduating. Ironically when I suggested bringing the RM into the IPMC to
>>> help other podlings trying to find votes Bill, who supports this proposal
>>> said yes, but required that the RM must refrain from voting on his own
>>> releases. That position seems to conflict with this proposal and I'm
>>> unclear what the difference is.
>> 
>> I can't speak for Bill, but I can say that Bill "gets" what I am saying
>> (and so do quite a few others).  Bill is just keeping up with the threads
>> right now, and doing a great job.
>> 
>> You'll note I supported giving your RM his VOTE, and in my proposal
>> you wouldn't have had problems mustering any binding VOTEs. You'd
>> have had them already like any other project management committee.
>> 
>>> 
>>>> 
>>>> Arguably, legal and the Legal Committee have a hand in this, no?
>>>> I'm not sure it was entirely managed by the IPMC before.
>>> 
>>> Again, I agree the IPMC has not always worked, but it has not always
>> failed
>>> either.
>> 
>> Stop calling it a failure. I *never* called it a failure. I called it a
>> success.
>> Even things that are a "success" end.
>> 
>>> 
>>> Are legal@ going to do reviews when necessary? If not who is?
>> 
>> Of course they are. They do it now for existing projects, that come
>> to them and ask (Sam's famous phrase). And even before that, the ASF
>> members who
>> are on the project committee (and even the non members) need
>> to do a bit of reading, and try and help out there as much as possible.
>> Signing up to be a PMC member on an incoming project means
>> investing the time to help out in some way. The member doesn't have to be
>> all
>> knowing or be the super star champion. That's why the trust is
>> distributed amongst the members of the PMC just like any PMC,
>> is funneled through the chair of the committee, and is acted or
>> reacted upon by the board, and why the board is elected by
>> the membership.
>> 
>> Cheers,
>> Chris
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW:   http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>> 
>> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

Posted by Ross Gardler <rg...@opendirective.com>.
Chris, seriously, take a break. You are not hearing what I'm trying to  say
and therefore not answering my concerns, directly at least.

For an example see where you use the word failure in this reply - that word
has no bearing on anything I have said, yet you directly attribute it to
me.

I've made up my mind about how I feel about this proposal. In general I
like it. I have some concerns that I will express in a summary document
that I'll share with ComDev. At this point b I'm not sure if my concerns
are misplaced our not.

Thanks for taking the time to try and understand my issues. Enjoy the rest
of your weekend.

Sent from my mobile device, please forgive errors and brevity.
On Feb 4, 2012 3:57 PM, "Mattmann, Chris A (388J)" <
chris.a.mattmann@jpl.nasa.gov> wrote:

> Hi Ross,
>
> On Feb 4, 2012, at 2:36 AM, Ross Gardler wrote:
>
> > Sent from my mobile device, please forgive errors and brevity.
> > On Feb 4, 2012 3:41 AM, "Mattmann, Chris A (388J)" <
> > chris.a.mattmann@jpl.nasa.gov> wrote:
> >> [...snip...]
> >>> Who fixes it?
> >>
> >> The project's PMC. And if not, the project's VP. And if not that, the
> > board,
> >> or the membership. Just like the current way it works for existing TLPs.
> >
> > if l the "membership" what is the channel used and who is responsible for
> > ensuring that channel works?
>
> The same channel that exists today for normal projects. The board is
> elected by the membership. If the board doesn't fix the problem for the
> project, and the membership is unpleased, the members elect a new
> board that will fix it. Or they won't.
>
> >
> >>
> >>> Who is maintaining the standards with respect to IP
> >>> management?
> >>
> >> How much work is there maintaing them? What's left to do?
> >
> > I mean in individual projects, not in defining policy. Even in the
> poddling
> > that I've felt would benefit from this proposal the RM has learned by his
> > mistakes. Some of which were caught by IPMC review when an additional
> vote
> > was needed.
>
> Sure, and in my proposal it'll be caught by review of having 3 ASF members
> on the project; by actually signing up strong ASF members (or "mentors")
> to the project (as Benson said) who care about that stuff (release review,
> etc.), and by having
> a VP for the project. Or by the board. Or by the legal committee.
>
> If you think about it, I'm simply proposing to use what's there, and to
> move more towards the existing foundation resources, than to pretend
> that the IPMC was the only place that we could get this information from.
> A lot of the passionate legal folks or release review folks in the IPMC
> (ant, Sam, etc.) are also members of the legal committee, and/or lurk
> there. A lot of the release passionate folks (Joe S., myself etc.) also
> lurk in other
> places that will see releases happening (infra@, etc.). It's not putting
> extra
> burden on them to ask them to flag what they see, or provide advice.
> They're
> doing that already.
>
> > Who provides these cross-checks?
>
> See above.
>
> >
> > You asked if a project couldn't muster the binding votes on a release,
> > what's it doing on the incubator. This project couldn't, but it is still
> > graduating. Ironically when I suggested bringing the RM into the IPMC to
> > help other podlings trying to find votes Bill, who supports this proposal
> > said yes, but required that the RM must refrain from voting on his own
> > releases. That position seems to conflict with this proposal and I'm
> > unclear what the difference is.
>
> I can't speak for Bill, but I can say that Bill "gets" what I am saying
>  (and so do quite a few others).  Bill is just keeping up with the threads
> right now, and doing a great job.
>
> You'll note I supported giving your RM his VOTE, and in my proposal
> you wouldn't have had problems mustering any binding VOTEs. You'd
> have had them already like any other project management committee.
>
> >
> >>
> >> Arguably, legal and the Legal Committee have a hand in this, no?
> >> I'm not sure it was entirely managed by the IPMC before.
> >
> > Again, I agree the IPMC has not always worked, but it has not always
> failed
> > either.
>
> Stop calling it a failure. I *never* called it a failure. I called it a
> success.
> Even things that are a "success" end.
>
> >
> > Are legal@ going to do reviews when necessary? If not who is?
>
> Of course they are. They do it now for existing projects, that come
> to them and ask (Sam's famous phrase). And even before that, the ASF
> members who
> are on the project committee (and even the non members) need
> to do a bit of reading, and try and help out there as much as possible.
> Signing up to be a PMC member on an incoming project means
> investing the time to help out in some way. The member doesn't have to be
> all
> knowing or be the super star champion. That's why the trust is
> distributed amongst the members of the PMC just like any PMC,
> is funneled through the chair of the committee, and is acted or
> reacted upon by the board, and why the board is elected by
> the membership.
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: Earned autonomy

Posted by Ross Gardler <rg...@opendirective.com>.
On 6 February 2012 01:33, Ate Douma <at...@douma.nu> wrote:
> On 02/06/2012 01:41 AM, Marvin Humphrey wrote:
>>
>> On Sun, Feb 05, 2012 at 01:26:47PM -0600, William A. Rowe Jr. wrote:
>>>
>>> It might be worthwhile to require 3 ASF members on the initial release,
>>> 2 on the next, 1 on the following and then trust the committee to follow
>>> the established precedent.
>>
>>
>> +1
>>
>> Instead of automatically decreasing the count, the device I'd suggest is
>> for
>> the ASF Members on the committee to vote to grant binding votes to
>> individual
>> contributors who they believe have demonstrated a thorough understanding
>> of
>> the Apache Way.
>>
>> Release Managers would be prime candidates; given the challenge of getting
>> an
>> incubating release out the door, an RM will likely have acquired greater
>> expertise than many ASF PMC members who have been voted directly into TLP
>> PMCs.  Just being an RM might not be enough, but it would be left to the
>> judgment of the ASF Members / Mentors to vet and vote on candidates.
>>
>> The canonical path towards project autonomy would thus be to make three
>> incubating releases with three different contributors serving as RM.
>
>
> What worries me a lot about the recent proposals, not only the text above,
> is that project autonomy seems to be measured foremost by just doing proper
> releases.
>
> To me, Apache == Community over code.

+1000

(I fully support everything Ate says here and I will further observe
that I have learned much about mentoring from Ate).

Ross

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Earned autonomy

Posted by Ralph Goers <ra...@dslextreme.com>.
On Feb 5, 2012, at 8:00 PM, Luciano Resende wrote:

> On Sun, Feb 5, 2012 at 5:33 PM, Ate Douma <at...@douma.nu> wrote:
>> 
>> 
>> I fully agree the current Incubator has its issues, but radically killing it
>> off IMO will also kill off more than just those issues: it will also kill
>> the Incubator community itself. Maybe ComDev can or actually then will have
>> to take over, but we should be really careful before breaking something down
>> without having a replacement 'safety net' in place.
>> 
>> Ate
>> 
>> 
> 
> Yes, moving from one "Incubator" to "ComDev" will not really fix all
> the issues... but it seems that consensus is being built on this
> direction.

I don't agree that consensus is being built on that direction or any other.  At this point I only see consensus on giving podlings more autonomy and authority.  The disagreement seems to be that some want podlings to essentially be a TLP from the beginning while others prefer transitioning them from podling to TLP but faster than happens today.

FWIW, I'm in complete agreement with Jim's message from early this morning which i read as effectively saying, the IPMC should not be worrying so much about how podlings are doing but about how mentors are doing.  

Ralph


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Earned autonomy

Posted by Luciano Resende <lu...@gmail.com>.
On Sun, Feb 5, 2012 at 5:33 PM, Ate Douma <at...@douma.nu> wrote:
> On 02/06/2012 01:41 AM, Marvin Humphrey wrote:
>>
>> On Sun, Feb 05, 2012 at 01:26:47PM -0600, William A. Rowe Jr. wrote:
>>>
>>> It might be worthwhile to require 3 ASF members on the initial release,
>>> 2 on the next, 1 on the following and then trust the committee to follow
>>> the established precedent.
>>
>>
>> +1
>>
>> Instead of automatically decreasing the count, the device I'd suggest is
>> for
>> the ASF Members on the committee to vote to grant binding votes to
>> individual
>> contributors who they believe have demonstrated a thorough understanding
>> of
>> the Apache Way.
>>
>> Release Managers would be prime candidates; given the challenge of getting
>> an
>> incubating release out the door, an RM will likely have acquired greater
>> expertise than many ASF PMC members who have been voted directly into TLP
>> PMCs.  Just being an RM might not be enough, but it would be left to the
>> judgment of the ASF Members / Mentors to vet and vote on candidates.
>>
>> The canonical path towards project autonomy would thus be to make three
>> incubating releases with three different contributors serving as RM.
>
>

Agreed that we need to have supervision on the initial phase, and that
some type of gradual phasing is required before they can handle the
releases by themselves.

> What worries me a lot about the recent proposals, not only the text above,
> is that project autonomy seems to be measured foremost by just doing proper
> releases.
>
> To me, Apache == Community over code.
>
> Code is important, it is what we are all here for (too), but the 'Apache
> Way' and especially community development and a healthy diversity IMO are
> even more critical. And especially for reaching project autonomy: *that* IMO
> is what the Incubator is (or should be) about.
>

Code and Releases are things that the Foundation might have legal
liability, that's why I have some concerns about leaving it without
any supervision.

I also agreed with your point about community, and I think this is the
place where ComDev would get pluged in.

> Learning the 'tricks' and reasons of doing proper releases isn't easy, and
> for sure required. But a 'perfect' RM doesn't automatically make a 'perfect'
> Apache TLP PMC member in my book. Which has been discussed quite a lot as
> well last week.
>
> The thing I'm worried about with the 'radical/revolutionary proposals of
> creating Incubator projects as TLPs from the start, is that they they also
> start 'on their own', even with 3 Mentors on board.
> Meaning: there is no 'glue' or common community between individual
> 'incubator' TLPs anymore which can help them, with the help of (many more)
> experienced IPMC members, as well as fellow Incubator PPMC members, to learn
> the ropes.
> Beyond merely doing proper releases.
>
> I fully agree the current Incubator has its issues, but radically killing it
> off IMO will also kill off more than just those issues: it will also kill
> the Incubator community itself. Maybe ComDev can or actually then will have
> to take over, but we should be really careful before breaking something down
> without having a replacement 'safety net' in place.
>
> Ate
>
>

Yes, moving from one "Incubator" to "ComDev" will not really fix all
the issues... but it seems that consensus is being built on this
direction.

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Earned autonomy

Posted by Craig L Russell <cr...@oracle.com>.
On Feb 6, 2012, at 8:23 AM, Marvin Humphrey wrote:

> Hi, Ate,
>
> On Mon, Feb 06, 2012 at 02:33:11AM +0100, Ate Douma wrote:
>> What worries me a lot about the recent proposals, not only the text
>> above, is that project autonomy seems to be measured foremost by just
>> doing proper releases.
>>
>> To me, Apache == Community over code.
>
> The case I have been trying to make is that there are community  
> benefits when
> a podling is allowed to earn progressively increasing autonomy over  
> its
> releases.

To me, this increasing autonomy can be handled today if the Mentors  
step up.

The first release should be vetted by each of the three Mentors,  
before it even gets to the full IPMC membership. If the Mentors do the  
minimum of checking signatures, looking over the RAT report, they can  
then rely on the PPMC members to technically vet the release.

And the second time around, reviewing a release should take even less  
time. And once the Mentors have confidence in the ability of the PPMC  
members to properly review, they can choose to vote +1 on a release  
with confidence that the release satisfies the requirements. Thus, a  
Mentor can give more autonomy simply by voting.

>
> For what it's worth, the poor state of the Incubator release system  
> has had
> negative impact on our podling's ability to recruit and retain new
> contributors.  When you're accustomed to the instantaneous  
> gratification of
> releasing to Github, CPAN, or RubyGems.org, coming into the  
> Incubator and
> seeing that it is routine for release candidates to be delayed for  
> *weeks*
> awaiting three IPMC votes is shocking.

The delay is shocking. Why can't the Mentors check signatures and  
review RAT?

There is no requirement by the incubator that a release actually do  
anything useful. So to sign off on a release should be a 30 minute  
task. We know that Mentors need to pay attention to the community  
interactions, which is where I expect most of their time to be spent.  
Reviewing a release for proper licensing and signatures should be a  
tiny part of the job.

Craig
>
> If you were trying to pick which open source project to spend your  
> time on,
> why would you want to stick around an organization that has so much  
> trouble
> getting its act together?
>
> Marvin Humphrey
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Earned autonomy

Posted by Marvin Humphrey <ma...@rectangular.com>.
Hi, Ate,

On Mon, Feb 06, 2012 at 02:33:11AM +0100, Ate Douma wrote:
> What worries me a lot about the recent proposals, not only the text 
> above, is that project autonomy seems to be measured foremost by just 
> doing proper releases.
>
> To me, Apache == Community over code.

The case I have been trying to make is that there are community benefits when
a podling is allowed to earn progressively increasing autonomy over its
releases.

For what it's worth, the poor state of the Incubator release system has had
negative impact on our podling's ability to recruit and retain new
contributors.  When you're accustomed to the instantaneous gratification of
releasing to Github, CPAN, or RubyGems.org, coming into the Incubator and
seeing that it is routine for release candidates to be delayed for *weeks*
awaiting three IPMC votes is shocking.

If you were trying to pick which open source project to spend your time on,
why would you want to stick around an organization that has so much trouble
getting its act together?

Marvin Humphrey


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Earned autonomy

Posted by Ate Douma <at...@douma.nu>.
On 02/06/2012 01:41 AM, Marvin Humphrey wrote:
> On Sun, Feb 05, 2012 at 01:26:47PM -0600, William A. Rowe Jr. wrote:
>> It might be worthwhile to require 3 ASF members on the initial release,
>> 2 on the next, 1 on the following and then trust the committee to follow
>> the established precedent.
>
> +1
>
> Instead of automatically decreasing the count, the device I'd suggest is for
> the ASF Members on the committee to vote to grant binding votes to individual
> contributors who they believe have demonstrated a thorough understanding of
> the Apache Way.
>
> Release Managers would be prime candidates; given the challenge of getting an
> incubating release out the door, an RM will likely have acquired greater
> expertise than many ASF PMC members who have been voted directly into TLP
> PMCs.  Just being an RM might not be enough, but it would be left to the
> judgment of the ASF Members / Mentors to vet and vote on candidates.
>
> The canonical path towards project autonomy would thus be to make three
> incubating releases with three different contributors serving as RM.

What worries me a lot about the recent proposals, not only the text above, is 
that project autonomy seems to be measured foremost by just doing proper releases.

To me, Apache == Community over code.

Code is important, it is what we are all here for (too), but the 'Apache Way' 
and especially community development and a healthy diversity IMO are even more 
critical. And especially for reaching project autonomy: *that* IMO is what the 
Incubator is (or should be) about.

Learning the 'tricks' and reasons of doing proper releases isn't easy, and for 
sure required. But a 'perfect' RM doesn't automatically make a 'perfect' Apache 
TLP PMC member in my book. Which has been discussed quite a lot as well last week.

The thing I'm worried about with the 'radical/revolutionary proposals of 
creating Incubator projects as TLPs from the start, is that they they also start 
'on their own', even with 3 Mentors on board.
Meaning: there is no 'glue' or common community between individual 'incubator' 
TLPs anymore which can help them, with the help of (many more) experienced IPMC 
members, as well as fellow Incubator PPMC members, to learn the ropes.
Beyond merely doing proper releases.

I fully agree the current Incubator has its issues, but radically killing it off 
IMO will also kill off more than just those issues: it will also kill the 
Incubator community itself. Maybe ComDev can or actually then will have to take 
over, but we should be really careful before breaking something down without 
having a replacement 'safety net' in place.

Ate

>
> This mechanism incentivizes the following healthy habits:
>
>    * Release early, release often.
>    * Share crucial responsibilities and disperse knowledge amongst multiple
>      contributors.
>    * Learn ASF documentation and relevant legal issues (thoroughly enough to
>      pass muster in the eyes of the ASF Members / Mentors).
>
> I don't worry too much that promoting individuals one-at-a-time will create a
> class of pseudo-BDFL contributors who are "more equal" than others.  Every
> project is going to have people who contribute disproportionally; what we
> want is for those people to do less coding and more community building and
> small-m mentoring.
>
>> projects should earn incremental trust and authority.
>
> +1 for incremental increases in autonomy.
>
> +1 for making it clear that the increased autonomy is *earned*.
>
> We want newcomers to internalize ASF values.  We want them to understand both
> how much we care about doing things the way we do and why.
>
> We also have oversight responsibilities that it would be best if we
> relinquished progressively.
>
> Marvin Humphrey
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Earned autonomy

Posted by Marvin Humphrey <ma...@rectangular.com>.
On Sun, Feb 05, 2012 at 01:26:47PM -0600, William A. Rowe Jr. wrote:
> It might be worthwhile to require 3 ASF members on the initial release,
> 2 on the next, 1 on the following and then trust the committee to follow
> the established precedent.

+1

Instead of automatically decreasing the count, the device I'd suggest is for
the ASF Members on the committee to vote to grant binding votes to individual
contributors who they believe have demonstrated a thorough understanding of
the Apache Way.

Release Managers would be prime candidates; given the challenge of getting an
incubating release out the door, an RM will likely have acquired greater
expertise than many ASF PMC members who have been voted directly into TLP
PMCs.  Just being an RM might not be enough, but it would be left to the
judgment of the ASF Members / Mentors to vet and vote on candidates.

The canonical path towards project autonomy would thus be to make three
incubating releases with three different contributors serving as RM.

This mechanism incentivizes the following healthy habits:

  * Release early, release often.
  * Share crucial responsibilities and disperse knowledge amongst multiple
    contributors.
  * Learn ASF documentation and relevant legal issues (thoroughly enough to
    pass muster in the eyes of the ASF Members / Mentors).

I don't worry too much that promoting individuals one-at-a-time will create a
class of pseudo-BDFL contributors who are "more equal" than others.  Every
project is going to have people who contribute disproportionally; what we
want is for those people to do less coding and more community building and
small-m mentoring.

> projects should earn incremental trust and authority.

+1 for incremental increases in autonomy.

+1 for making it clear that the increased autonomy is *earned*.

We want newcomers to internalize ASF values.  We want them to understand both
how much we care about doing things the way we do and why.

We also have oversight responsibilities that it would be best if we
relinquished progressively.

Marvin Humphrey


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 2/5/2012 12:37 AM, Luciano Resende wrote:
> 
> One thing that is not clear on the proposal is that it says that
> releases will be responsibility of the TLPs, but it doest not suggest
> or require that the actual existing ASF members that are part of the
> TLP have to vote on the release. This might become an issue with
> podlings that are not so experienced with the IP issues, etc and
> official ASF releases from these podlings might have issues.
> 
> I'd recommend that, during the incubation period of the TLP,  releases
> are required to have at least 3 votes from existing ASF members. This
> might still be a little overhead, but at least it's members of the
> PMC, and the TLP would not have to go chase IPMC on the general list
> to get release approval.

Here again, this suggests excessive paranoia.  We've had broken releases
from plenty of TLP's... they do get sorted out over time.

It might be worthwhile to require 3 ASF members on the initial release,
2 on the next, 1 on the following and then trust the committee to follow
the established precedent.  I believe that in the "Incubating Project
Requirements and Guidelines" (a different document than the proposal, one
that will be created and refined over time, largely the existing incubator
docs today to start with) ... projects should earn incremental trust and
authority.  You've raised one good example.


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

Posted by Luciano Resende <lu...@gmail.com>.
On Sat, Feb 4, 2012 at 8:01 AM, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
> Hi Ross,
>
> On Feb 4, 2012, at 2:36 AM, Ross Gardler wrote:
>
>> Sent from my mobile device, please forgive errors and brevity.
>> On Feb 4, 2012 3:41 AM, "Mattmann, Chris A (388J)" <
>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>> [...snip...]
>>>> Who fixes it?
>>>
>>> The project's PMC. And if not, the project's VP. And if not that, the
>> board,
>>> or the membership. Just like the current way it works for existing TLPs.
>>
>> if l the "membership" what is the channel used and who is responsible for
>> ensuring that channel works?
>
> The same channel that exists today for normal projects. The board is
> elected by the membership. If the board doesn't fix the problem for the
> project, and the membership is unpleased, the members elect a new
> board that will fix it. Or they won't.
>
>>
>>>
>>>> Who is maintaining the standards with respect to IP
>>>> management?
>>>
>>> How much work is there maintaing them? What's left to do?
>>
>> I mean in individual projects, not in defining policy. Even in the poddling
>> that I've felt would benefit from this proposal the RM has learned by his
>> mistakes. Some of which were caught by IPMC review when an additional vote
>> was needed.
>
> Sure, and in my proposal it'll be caught by review of having 3 ASF members
> on the project; by actually signing up strong ASF members (or "mentors")
> to the project (as Benson said) who care about that stuff (release review, etc.), and by having
> a VP for the project. Or by the board. Or by the legal committee.
>
> If you think about it, I'm simply proposing to use what's there, and to
> move more towards the existing foundation resources, than to pretend
> that the IPMC was the only place that we could get this information from.
> A lot of the passionate legal folks or release review folks in the IPMC
> (ant, Sam, etc.) are also members of the legal committee, and/or lurk
> there. A lot of the release passionate folks (Joe S., myself etc.) also lurk in other
> places that will see releases happening (infra@, etc.). It's not putting extra
> burden on them to ask them to flag what they see, or provide advice. They're
> doing that already.
>

One thing that is not clear on the proposal is that it says that
releases will be responsibility of the TLPs, but it doest not suggest
or require that the actual existing ASF members that are part of the
TLP have to vote on the release. This might become an issue with
podlings that are not so experienced with the IP issues, etc and
official ASF releases from these podlings might have issues.

I'd recommend that, during the incubation period of the TLP,  releases
are required to have at least 3 votes from existing ASF members. This
might still be a little overhead, but at least it's members of the
PMC, and the TLP would not have to go chase IPMC on the general list
to get release approval.


>> Who provides these cross-checks?
>
> See above.
>
>>
>> You asked if a project couldn't muster the binding votes on a release,
>> what's it doing on the incubator. This project couldn't, but it is still
>> graduating. Ironically when I suggested bringing the RM into the IPMC to
>> help other podlings trying to find votes Bill, who supports this proposal
>> said yes, but required that the RM must refrain from voting on his own
>> releases. That position seems to conflict with this proposal and I'm
>> unclear what the difference is.
>
> I can't speak for Bill, but I can say that Bill "gets" what I am saying
>  (and so do quite a few others).  Bill is just keeping up with the threads
> right now, and doing a great job.
>
> You'll note I supported giving your RM his VOTE, and in my proposal
> you wouldn't have had problems mustering any binding VOTEs. You'd
> have had them already like any other project management committee.
>
>>
>>>
>>> Arguably, legal and the Legal Committee have a hand in this, no?
>>> I'm not sure it was entirely managed by the IPMC before.
>>
>> Again, I agree the IPMC has not always worked, but it has not always failed
>> either.
>
> Stop calling it a failure. I *never* called it a failure. I called it a success.
> Even things that are a "success" end.
>
>>
>> Are legal@ going to do reviews when necessary? If not who is?
>
> Of course they are. They do it now for existing projects, that come
> to them and ask (Sam's famous phrase). And even before that, the ASF members who
> are on the project committee (and even the non members) need
> to do a bit of reading, and try and help out there as much as possible.
> Signing up to be a PMC member on an incoming project means
> investing the time to help out in some way. The member doesn't have to be all
> knowing or be the super star champion. That's why the trust is
> distributed amongst the members of the PMC just like any PMC,
> is funneled through the chair of the committee, and is acted or
> reacted upon by the board, and why the board is elected by
> the membership.
>
> Cheers,
> Chris
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>



-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

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

On Feb 4, 2012, at 2:36 AM, Ross Gardler wrote:

> Sent from my mobile device, please forgive errors and brevity.
> On Feb 4, 2012 3:41 AM, "Mattmann, Chris A (388J)" <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>> [...snip...]
>>> Who fixes it?
>> 
>> The project's PMC. And if not, the project's VP. And if not that, the
> board,
>> or the membership. Just like the current way it works for existing TLPs.
> 
> if l the "membership" what is the channel used and who is responsible for
> ensuring that channel works?

The same channel that exists today for normal projects. The board is
elected by the membership. If the board doesn't fix the problem for the
project, and the membership is unpleased, the members elect a new
board that will fix it. Or they won't.

> 
>> 
>>> Who is maintaining the standards with respect to IP
>>> management?
>> 
>> How much work is there maintaing them? What's left to do?
> 
> I mean in individual projects, not in defining policy. Even in the poddling
> that I've felt would benefit from this proposal the RM has learned by his
> mistakes. Some of which were caught by IPMC review when an additional vote
> was needed.

Sure, and in my proposal it'll be caught by review of having 3 ASF members
on the project; by actually signing up strong ASF members (or "mentors")
to the project (as Benson said) who care about that stuff (release review, etc.), and by having
a VP for the project. Or by the board. Or by the legal committee. 

If you think about it, I'm simply proposing to use what's there, and to 
move more towards the existing foundation resources, than to pretend 
that the IPMC was the only place that we could get this information from.
A lot of the passionate legal folks or release review folks in the IPMC 
(ant, Sam, etc.) are also members of the legal committee, and/or lurk
there. A lot of the release passionate folks (Joe S., myself etc.) also lurk in other
places that will see releases happening (infra@, etc.). It's not putting extra
burden on them to ask them to flag what they see, or provide advice. They're
doing that already. 

> Who provides these cross-checks?

See above.

> 
> You asked if a project couldn't muster the binding votes on a release,
> what's it doing on the incubator. This project couldn't, but it is still
> graduating. Ironically when I suggested bringing the RM into the IPMC to
> help other podlings trying to find votes Bill, who supports this proposal
> said yes, but required that the RM must refrain from voting on his own
> releases. That position seems to conflict with this proposal and I'm
> unclear what the difference is.

I can't speak for Bill, but I can say that Bill "gets" what I am saying
 (and so do quite a few others).  Bill is just keeping up with the threads 
right now, and doing a great job.

You'll note I supported giving your RM his VOTE, and in my proposal
you wouldn't have had problems mustering any binding VOTEs. You'd
have had them already like any other project management committee.

> 
>> 
>> Arguably, legal and the Legal Committee have a hand in this, no?
>> I'm not sure it was entirely managed by the IPMC before.
> 
> Again, I agree the IPMC has not always worked, but it has not always failed
> either.

Stop calling it a failure. I *never* called it a failure. I called it a success.
Even things that are a "success" end. 

> 
> Are legal@ going to do reviews when necessary? If not who is?

Of course they are. They do it now for existing projects, that come 
to them and ask (Sam's famous phrase). And even before that, the ASF members who 
are on the project committee (and even the non members) need 
to do a bit of reading, and try and help out there as much as possible.
Signing up to be a PMC member on an incoming project means 
investing the time to help out in some way. The member doesn't have to be all
knowing or be the super star champion. That's why the trust is
distributed amongst the members of the PMC just like any PMC, 
is funneled through the chair of the committee, and is acted or 
reacted upon by the board, and why the board is elected by
the membership.

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

Posted by Ross Gardler <rg...@opendirective.com>.
Sent from my mobile device, please forgive errors and brevity.
On Feb 4, 2012 3:41 AM, "Mattmann, Chris A (388J)" <
chris.a.mattmann@jpl.nasa.gov> wrote:
>
> Hi Ross,
>
> On Feb 3, 2012, at 7:27 PM, Ross Gardler wrote:
>
> > On 4 February 2012 02:01, Mattmann, Chris A (388J)
> > <ch...@jpl.nasa.gov> wrote:
> > ...
> >
> >>> Sounds like additional documentation for the proposal
> >>>
> >>> Committee:  Previous responsibility   <--->   Revised responsibility
> >>> _________   _______________________           ______________________
> >>>
> >>> ---------------------------------------------------------------------
> >>
> >> Great idea!
> >>
> >> I've added this to the proposal:
> >>
> >> http://wiki.apache.org/incubator/IncubatorDeconstructionProposal
> >>
> >> Ross: I think the table shows what I think ComDev should take over.
> >
> > Thanks, that covers the procedural issues.
> >
> > And when things go wrong with the mentoring process who spots this?
>
> The project's PMC. And if not, the project's VP. And if not that, the
board
> during the board report. Just like the current way it works for existing
TLPs.
>
> > Who fixes it?
>
> The project's PMC. And if not, the project's VP. And if not that, the
board,
> or the membership. Just like the current way it works for existing TLPs.

if l the "membership" what is the channel used and who is responsible for
ensuring that channel works?

>
> > Who is maintaining the standards with respect to IP
> > management?
>
> How much work is there maintaing them? What's left to do?

I mean in individual projects, not in defining policy. Even in the poddling
that I've felt would benefit from this proposal the RM has learned by his
mistakes. Some of which were caught by IPMC review when an additional vote
was needed.

Who provides these cross-checks?

You asked if a project couldn't muster the binding votes on a release,
what's it doing on the incubator. This project couldn't, but it is still
graduating. Ironically when I suggested bringing the RM into the IPMC to
help other podlings trying to find votes Bill, who supports this proposal
said yes, but required that the RM must refrain from voting on his own
releases. That position seems to conflict with this proposal and I'm
unclear what the difference is.

>
> Arguably, legal and the Legal Committee have a hand in this, no?
> I'm not sure it was entirely managed by the IPMC before.

Again, I agree the IPMC has not always worked, but it has not always failed
either.

Are legal@ going to do reviews when necessary? If not who is?

>
> Cheers,
> Chris
>
> P.S. Good questions above, I added them (and my suggestions for them)
> to the proposal
http://wiki.apache.org/incubator/IncubatorDeconstructionProposal
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

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

On Feb 3, 2012, at 7:27 PM, Ross Gardler wrote:

> On 4 February 2012 02:01, Mattmann, Chris A (388J)
> <ch...@jpl.nasa.gov> wrote:
> ...
> 
>>> Sounds like additional documentation for the proposal
>>> 
>>> Committee:  Previous responsibility   <--->   Revised responsibility
>>> _________   _______________________           ______________________
>>> 
>>> ---------------------------------------------------------------------
>> 
>> Great idea!
>> 
>> I've added this to the proposal:
>> 
>> http://wiki.apache.org/incubator/IncubatorDeconstructionProposal
>> 
>> Ross: I think the table shows what I think ComDev should take over.
> 
> Thanks, that covers the procedural issues.
> 
> And when things go wrong with the mentoring process who spots this?

The project's PMC. And if not, the project's VP. And if not that, the board
during the board report. Just like the current way it works for existing TLPs.

> Who fixes it?

The project's PMC. And if not, the project's VP. And if not that, the board,
or the membership. Just like the current way it works for existing TLPs.

> Who is maintaining the standards with respect to IP
> management?

How much work is there maintaing them? What's left to do?

Arguably, legal and the Legal Committee have a hand in this, no?
I'm not sure it was entirely managed by the IPMC before.

Cheers,
Chris

P.S. Good questions above, I added them (and my suggestions for them)
to the proposal http://wiki.apache.org/incubator/IncubatorDeconstructionProposal

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

Posted by Ross Gardler <rg...@opendirective.com>.
On 4 February 2012 02:01, Mattmann, Chris A (388J)
<ch...@jpl.nasa.gov> wrote:
...

>> Sounds like additional documentation for the proposal
>>
>> Committee:  Previous responsibility   <--->   Revised responsibility
>> _________   _______________________           ______________________
>>
>> ---------------------------------------------------------------------
>
> Great idea!
>
> I've added this to the proposal:
>
> http://wiki.apache.org/incubator/IncubatorDeconstructionProposal
>
> Ross: I think the table shows what I think ComDev should take over.

Thanks, that covers the procedural issues.

And when things go wrong with the mentoring process who spots this?
Who fixes it? Who is maintaining the standards with respect to IP
management?


Ross

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

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

On Feb 3, 2012, at 5:18 PM, William A. Rowe Jr. wrote:

> On 2/3/2012 7:06 PM, Ross Gardler wrote:
>> 
>> Do any of the candidates want to take a little time to define the role they
>> see for ComDev?
> 
> Sounds like additional documentation for the proposal
> 
> Committee:  Previous responsibility   <--->   Revised responsibility
> _________   _______________________           ______________________
> 
> ---------------------------------------------------------------------

Great idea!

I've added this to the proposal:

http://wiki.apache.org/incubator/IncubatorDeconstructionProposal

Ross: I think the table shows what I think ComDev should take over. 

Let me know what you think.

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Anyone care to talk to ComDev? (was Re: Time to vote the chair?)

Posted by "William A. Rowe Jr." <wr...@rowe-clan.net>.
On 2/3/2012 7:06 PM, Ross Gardler wrote:
> 
> Do any of the candidates want to take a little time to define the role they
> see for ComDev?

Sounds like additional documentation for the proposal

Committee:  Previous responsibility   <--->   Revised responsibility
_________   _______________________           ______________________

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org