You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Roman Shaposhnik <rv...@apache.org> on 2014/05/31 17:27:55 UTC
Re: Reports needing shepherd attention
Looks like I've never sent this one out.
Moving this to general@incubator from board@
On Wed, May 21, 2014 at 10:45 PM, Brett Porter <br...@apache.org> wrote:
> On 22 May 2014, at 3:26 am, Roman Shaposhnik <rv...@apache.org> wrote:
>
>> On Wed, May 21, 2014 at 6:31 AM, Brett Porter <br...@apache.org> wrote:
>>> AB. Apache Incubator (Roy)
>>
>> FWIW: I can not parse the feedback from danielsh. Would appreciate
>> more details.
>
> Following up post-meeting, the board didn't have any concerns with
> the Incubator report when discussed.
Thanks Brett! This makes sense.
Still I'd like to take a moment and discuss what you've articulated bellow
to get IPMC feedback:
> Daniel made an observation as an interested member, and picked up on a couple of
> instances of podlings that potentially misunderstood graduation or reporting requirements,
> based on the text of the report. The first example listed a piece of software functionality
> as a graduation goal, which may misunderstand that graduation is about the completeness
> of the community, IP transfer, and understanding of Apache policies; not the completeness
> of the software. The second example was that the answer to a question about how a
> community has developed doesn't depend on mail statistics (though might be aided by it),
> so the podling might have misunderstood what the template suggested.
Interestingly enough this wasn't how I read those same reports. To me
the listed concerns signified podlings desire to make software 'more
compelling' before graduation point.
Regardless, I guess my real question is this: if a podling feels that they
need to achieve a certain milestone in software completeness before
they can confidently graduate, are we really in a position to push
them out of the incubator somewhat against their will?
> However, I'll leave it to Daniel to further clarify if he wishes (perhaps on the incubator lists for
> the benefit of those shepherding the podling reports).
That would be useful as well.
Thanks,
Roman.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Reports needing shepherd attention
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Roman Shaposhnik wrote on Sat, May 31, 2014 at 23:39:06 -0700:
> On Sat, May 31, 2014 at 10:18 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> >> Regardless, I guess my real question is this: if a podling feels that they
> >> need to achieve a certain milestone in software completeness before
> >> they can confidently graduate, are we really in a position to push
> >> them out of the incubator somewhat against their will?
> >
> > I can imagine situations in which you'd graduate a podling that has a
> > diverse and self-managing PPMC and advise the PMC to work with Press, or
> > Infra, or Brand, or Comdev post-graduation to improve some aspect or
> > another.
>
> I can't. If the community doesn't think it is ready the best you can do is
> try to persuade them that they are ready, but not graduate by force.
>
We aren't talking about the same thing.
I don't think it would make sense to graduate somebody by force.
I'm just saying that I see scenarios in which a project graduates that
still has some problems, which the PMC-to-be can address by itself
(i.e., doesn't need IPMC's hand-holding with addressing).
> > Back to the instance at hand: the project reported that adding a feature
> > is a graduation blocker. That is unusual. The likely explanation is
> > that they misunderstood what graduation is about. The situation should
> > therefore be checked.
> > If the project has a misunderstanding then it
> > should be corrected, and if it doesn't then it'd be better if they
> > clarified in future reports why they, unusually, consider adding a
> > feature to be a graduation blocker.
>
> That's a good point, but see below.
>
> > A podling was asked "Has your community grown" and replied that the
> > statistics server was down. To me, that's not a satisfactory answer,
> > for the same reason that (with car drivers) a broken speedometer is not
> > a carte blanche to speeding.
>
> [...] only hope is to have good mentors.
+1
> > Time for reductio ad absurdum.
>
> Never a good move on an email thread ;-)
Because...?
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Reports needing shepherd attention
Posted by Roman Shaposhnik <rv...@apache.org>.
On Sat, May 31, 2014 at 10:18 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>> Regardless, I guess my real question is this: if a podling feels that they
>> need to achieve a certain milestone in software completeness before
>> they can confidently graduate, are we really in a position to push
>> them out of the incubator somewhat against their will?
>
> I can imagine situations in which you'd graduate a podling that has a
> diverse and self-managing PPMC and advise the PMC to work with Press, or
> Infra, or Brand, or Comdev post-graduation to improve some aspect or
> another.
I can't. If the community doesn't think it is ready the best you can do is
try to persuade them that they are ready, but not graduate by force.
> Back to the instance at hand: the project reported that adding a feature
> is a graduation blocker. That is unusual. The likely explanation is
> that they misunderstood what graduation is about. The situation should
> therefore be checked.
> If the project has a misunderstanding then it
> should be corrected, and if it doesn't then it'd be better if they
> clarified in future reports why they, unusually, consider adding a
> feature to be a graduation blocker.
That's a good point, but see below.
> A podling was asked "Has your community grown" and replied that the
> statistics server was down. To me, that's not a satisfactory answer,
> for the same reason that (with car drivers) a broken speedometer is not
> a carte blanche to speeding.
I'd agree with you in theory. In practice, the only way for this kind of
checks-n-balances to happen is for mentors to stay super engaged
and take it onto themselves to address these kind of issues during
report review within the community (before the report is every submitted
to the wiki).
Perhaps this email thread will be a reminder to all the mentors out there
to make sure they follow up ASAP.
The next best thing (just as Marvin proposed) would be for the entire
report to be submitted for a short review window (instead of just
shepherding notes). That would also engage the entire IPMC community,
but only as a measure of last resort where we ourselves would
flag this issues to both mentors and the board.
At the end of the day -- just like the board is a hammer, not a scalpel,
IPMC (as a collective) is not a proper tool for the kind of intricate job
you've meant in your replies. Our only hope is to have good mentors.
> Time for reductio ad absurdum.
Never a good move on an email thread ;-)
Thanks,
Roman.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Reports needing shepherd attention
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
[ Brett: thanks for communicating my feedback to Roman; I missed his
question to me in his previous mail. ]
Roman Shaposhnik wrote on Sat, May 31, 2014 at 08:27:55 -0700:
> On Wed, May 21, 2014 at 10:45 PM, Brett Porter <br...@apache.org> wrote:
> > The first example listed a piece of software functionality
> > as a graduation goal, which may misunderstand that graduation is about the completeness
> > of the community, IP transfer, and understanding of Apache policies; not the completeness
> > of the software.
Yes, that is precisely the point I was trying to make.
> Regardless, I guess my real question is this: if a podling feels that they
> need to achieve a certain milestone in software completeness before
> they can confidently graduate, are we really in a position to push
> them out of the incubator somewhat against their will?
I can imagine situations in which you'd graduate a podling that has a
diverse and self-managing PPMC and advise the PMC to work with Press, or
Infra, or Brand, or Comdev post-graduation to improve some aspect or
another.
Back to the instance at hand: the project reported that adding a feature
is a graduation blocker. That is unusual. The likely explanation is
that they misunderstood what graduation is about. The situation should
therefore be checked. If the project has a misunderstanding then it
should be corrected, and if it doesn't then it'd be better if they
clarified in future reports why they, unusually, consider adding a
feature to be a graduation blocker.
> > The second example was that the answer to a question about how a
> > community has developed doesn't depend on mail statistics (though might be aided by it),
> > so the podling might have misunderstood what the template suggested.
> > However, I'll leave it to Daniel to further clarify if he wishes (perhaps on the incubator lists for
> > the benefit of those shepherding the podling reports).
A podling was asked "Has your community grown" and replied that the
statistics server was down. To me, that's not a satisfactory answer,
for the same reason that (with car drivers) a broken speedometer is not
a carte blanche to speeding.
Time for reductio ad absurdum. Suppose Infra switched to a mailing
lists software that did not allow (P)PMCs to obtain subscriber counts.
Would you consider it reasonable, in that scenario, for (P)PMCs to report
to the Board that they have no idea how their community is doing? What
would you expect them to do instead? That is what the PPMC in question
should have done.
Cheers,
Daniel
P.S. Please CC me on replies.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Reports needing shepherd attention
Posted by Marvin Humphrey <ma...@rectangular.com>.
On Sat, May 31, 2014 at 8:27 AM, Roman Shaposhnik <rv...@apache.org> wrote:
> Still I'd like to take a moment and discuss what you've articulated bellow
> to get IPMC feedback:
>
>> Daniel made an observation as an interested member, and picked up on a
>> couple of instances of podlings that potentially misunderstood graduation
>> or reporting requirements, based on the text of the report.
In addition to the specific points raised, I understood Daniel's general
concern to be that some reports contained bugs and that those should have been
caught by IPMC review prior to submitting. I'm not sure that the IPMC can
consistently muster the focus necessary to catch everything that the Board
might flag as a bug, but there's an easy step we can take to improve matters.
Right now, on the Monday before the report is filed, the Report Manager sends
a summary of shepherding comments extracted from the report to
general@incubator, giving podlings a chance to react to the reviews. I
suggest that that the Report Manager just send out the complete report
instead.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org