You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Sanjiva Weerawarana <sa...@wso2.com> on 2013/10/07 09:00:26 UTC
Fwd: Too many late reports
Someone needs to send this .. not good to get on the bad list right away
:-).
---------- Forwarded message ----------
From: Marvin Humphrey <ma...@rectangular.com>
Date: Mon, Oct 7, 2013 at 9:49 AM
Subject: Too many late reports
To: "general@incubator.apache.org" <ge...@incubator.apache.org>
On Sun, Oct 6, 2013 at 11:29 AM, Dave Fisher <da...@comcast.net> wrote:
> > Dave Fisher DeviceMap
> > Dave Fisher Spark
>
> Although there are no reports yet.
On Sun, Oct 6, 2013 at 11:45 AM, Matt Franklin <m....@gmail.com>
wrote:
> Missing the ODF Toolkit report for this month.
Lots of late or missing reports this month!
As of the due date last Wednesday, 8 podlings out of 16 had not reported:
* Chukwa
* DeviceMap
* Helix
* ODF Toolkit
* Ripple
* Samza
* Spark
* Stratos
Since then, Chukwa and Helix filed their reports late Saturday; Spark filed
a
report today -- *after* Dave Fisher had filed his shepherding commentary,
which concludes with the sentence "I'm not sure why they have not reported
yet."
It's inconvenient to receive podling reports late. Mentors have less time
to
sign off and possibly comment; shepherds don't get to take the podling's own
self-examination into account when conducting their reviews.
Perhaps it would be better if we ask late podlings to file next month
instead.
That's what the Board asks TLPs to do when their reports show up too late.
In the past, the Incubator PMC has not done a good job of following up when
reports are missed entirely, arguably contributing to our losing track of
low-activity podlings and delaying intervention. I've started doing it a
bit,
though I've missed at least one (NPanday did not file in August but there
was
no followup AFAIK). It might be nice to build a remedy into the reporting
run
book -- something like this:
After filing the report, perform the following steps for each podling
which did not report:
* Edit podlings.xml to set the "monthly" reporting attribute for the
podling.
* Send a message to the podling's dev list requesting that they
file an out-of-cycle report next month as a makeup.
One possible contributing factor is that podlings are still not getting a
full week's notice to file their reports. Sure, reporting isn't a huge
task,
but when you're new to creating reports it takes much longer.
The argument that podlings ought to just know these dates and file on time
rather than relying on reminders[1] simply isn't getting the job done. I
think we'd get better results if we expect punctuality from podlings, set a
good example by demonstrating punctuality ourselves, and express lenience by
requesting that a podling report next month rather than by accepting a
report too
late to give it the attention it deserves.
The problem is that at present the reminders have to be sent out
manually[2],
and despite the best of intentions, humans are not ideal replacements for
cron
jobs. It's time to ask again: what would it take to get those reminders
firing with unerring reliability three weeks before the Board meeting? Is
it
realistic to attempt a patch eliminating the need for an svn password?
Marvin Humphrey
[1] http://s.apache.org/PIj
[2] http://s.apache.org/dwM
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: sanjiva@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/
Lean . Enterprise . Middleware
Re: Fwd: Too many late reports
Posted by Chip Childers <ch...@sungard.com>.
On Mon, Oct 07, 2013 at 02:06:38PM +0530, Lakmal Warusawithana wrote:
> Hi Sanjiva,
>
> Azeez already submitted.
Ignore my last email then... ;-)
Thanks for jumping on this Lakmal.
Re: Fwd: Too many late reports
Posted by Lakmal Warusawithana <la...@wso2.com>.
Hi Sanjiva,
Azeez already submitted.
Thanks
sent from phone
On Oct 7, 2013 12:31 PM, "Sanjiva Weerawarana" <sa...@wso2.com> wrote:
> Someone needs to send this .. not good to get on the bad list right away
> :-).
>
> ---------- Forwarded message ----------
> From: Marvin Humphrey <ma...@rectangular.com>
> Date: Mon, Oct 7, 2013 at 9:49 AM
> Subject: Too many late reports
> To: "general@incubator.apache.org" <ge...@incubator.apache.org>
>
>
> On Sun, Oct 6, 2013 at 11:29 AM, Dave Fisher <da...@comcast.net>
> wrote:
>
> > > Dave Fisher DeviceMap
> > > Dave Fisher Spark
> >
> > Although there are no reports yet.
>
> On Sun, Oct 6, 2013 at 11:45 AM, Matt Franklin <m....@gmail.com>
> wrote:
>
> > Missing the ODF Toolkit report for this month.
>
> Lots of late or missing reports this month!
>
> As of the due date last Wednesday, 8 podlings out of 16 had not reported:
>
> * Chukwa
> * DeviceMap
> * Helix
> * ODF Toolkit
> * Ripple
> * Samza
> * Spark
> * Stratos
>
> Since then, Chukwa and Helix filed their reports late Saturday; Spark
> filed a
> report today -- *after* Dave Fisher had filed his shepherding commentary,
> which concludes with the sentence "I'm not sure why they have not reported
> yet."
>
> It's inconvenient to receive podling reports late. Mentors have less time
> to
> sign off and possibly comment; shepherds don't get to take the podling's
> own
> self-examination into account when conducting their reviews.
>
> Perhaps it would be better if we ask late podlings to file next month
> instead.
> That's what the Board asks TLPs to do when their reports show up too late.
>
> In the past, the Incubator PMC has not done a good job of following up when
> reports are missed entirely, arguably contributing to our losing track of
> low-activity podlings and delaying intervention. I've started doing it a
> bit,
> though I've missed at least one (NPanday did not file in August but there
> was
> no followup AFAIK). It might be nice to build a remedy into the reporting
> run
> book -- something like this:
>
> After filing the report, perform the following steps for each podling
> which did not report:
>
> * Edit podlings.xml to set the "monthly" reporting attribute for the
> podling.
> * Send a message to the podling's dev list requesting that they
> file an out-of-cycle report next month as a makeup.
>
> One possible contributing factor is that podlings are still not getting a
> full week's notice to file their reports. Sure, reporting isn't a huge
> task,
> but when you're new to creating reports it takes much longer.
>
> The argument that podlings ought to just know these dates and file on time
> rather than relying on reminders[1] simply isn't getting the job done. I
> think we'd get better results if we expect punctuality from podlings, set a
> good example by demonstrating punctuality ourselves, and express lenience
> by
> requesting that a podling report next month rather than by accepting a
> report too
> late to give it the attention it deserves.
>
> The problem is that at present the reminders have to be sent out
> manually[2],
> and despite the best of intentions, humans are not ideal replacements for
> cron
> jobs. It's time to ask again: what would it take to get those reminders
> firing with unerring reliability three weeks before the Board meeting? Is
> it
> realistic to attempt a patch eliminating the need for an svn password?
>
> Marvin Humphrey
>
> [1] http://s.apache.org/PIj
> [2] http://s.apache.org/dwM
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
> email: sanjiva@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
> 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware
>