You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Marvin Humphrey <ma...@rectangular.com> on 2015/03/27 16:56:10 UTC

Podling report reminders didn't go out

Greets,

With the chaos of the Members meeting this week it went unremarked,
but Marvin failed to send out report reminders again.  Reports are due
next Wednesday.

(Other Marvin.  The robot.)

Marvin Humphrey

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


Re: Podling report reminders didn't go out

Posted by Ted Dunning <te...@gmail.com>.
On Fri, Mar 27, 2015 at 7:47 PM, Marvin Humphrey <ma...@rectangular.com>
wrote:

> I've contemplated writing a quickie Incubator-specific Python version which
> fetches report_due_*.txt over http:
>
>
> http://svn.apache.org/repos/asf/incubator/public/trunk/content/report_due_1.txt
>
> I think those report_due_*.txt files are all the script needs.
>
> A more ambitious project would be a modularized version with unit tests
> which
> handles all uses cases of the original.  Dunno if other users would be down
> with that, though.
>

Incubator specific version sounds great.  Using only web-accessible zero
security files is an awesome idea.

Unit tests are awesome things to have and would be much easier if you fetch
the schedule from a URL (just need a few static URL's for testing!).

Re: Podling report reminders didn't go out

Posted by Marvin Humphrey <ma...@rectangular.com>.
On Fri, Mar 27, 2015 at 6:51 PM, Matt Franklin <m....@gmail.com> wrote:

>> The script is fiddly and hard to test.  It's expanded beyond its
>> original scope and probably could stand to be refactored or rewritten.

>
> Where does it live?

https://git-wip-us.apache.org/repos/asf?p=infrastructure-puppet.git;a=blob;f=modules/subversion_server/files/board_reminders/reminders.pl

*   900+ lines of Perl.
*   Handles both TLP and podling reminders, plus [other stuff].
*   Has a test mode, but no unit tests.
*   Used to be run manually by Infra until I asked for it to be run on a cron
    while I was IPMC Chair.
*   Needs a local checkout of the Incubator svn using `file://` and has to run
    on subversion master (a security sensitive machine) because `svn up` would
    ordinarily need credentials.  Apparently this was necessary in order to
    get it to run as a cron, though I'm not clear on the details.

The script broke when Subversion master moved machines a few months ago, and
has had various problems since.

I've contemplated writing a quickie Incubator-specific Python version which
fetches report_due_*.txt over http:

  http://svn.apache.org/repos/asf/incubator/public/trunk/content/report_due_1.txt

I think those report_due_*.txt files are all the script needs.

A more ambitious project would be a modularized version with unit tests which
handles all uses cases of the original.  Dunno if other users would be down
with that, though.

Marvin Humphrey

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


Re: Podling report reminders didn't go out

Posted by "John D. Ament" <jo...@apache.org>.
On Fri, Mar 27, 2015 at 9:52 PM Matt Franklin <m....@gmail.com>
wrote:

> On Fri, Mar 27, 2015 at 9:31 PM Marvin Humphrey <ma...@rectangular.com>
> wrote:
>
> > On Fri, Mar 27, 2015 at 9:14 AM, Matt Franklin <m.ben.franklin@gmail.com
> >
> > wrote:
> >
> > > Do we have a cause for the continued failure to send reminders?
> >
> > The script is fiddly and hard to test.  It's expanded beyond its
> > original scope and probably could stand to be refactored or rewritten.
> >
>
> Where does it live?
>
>
This is the semi-automatic Marvin:
https://github.com/apache/infrastructure-puppet/blob/master/modules/subversion_server/files/board_reminders/reminders.pl




>
> >
> > > Every podling SHOULD know their reporting schedule, but it is easy to
> > forget.
> >
> > That's true, but there's also a matter of our *own* credibility. If we
> > expect podlings to adhere to the schedule we set, we ought to adhere
> > to it ourselves.
> >
> > Marvin Humphrey
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>

Re: Podling report reminders didn't go out

Posted by Matt Franklin <m....@gmail.com>.
On Fri, Mar 27, 2015 at 9:31 PM Marvin Humphrey <ma...@rectangular.com>
wrote:

> On Fri, Mar 27, 2015 at 9:14 AM, Matt Franklin <m....@gmail.com>
> wrote:
>
> > Do we have a cause for the continued failure to send reminders?
>
> The script is fiddly and hard to test.  It's expanded beyond its
> original scope and probably could stand to be refactored or rewritten.
>

Where does it live?


>
> > Every podling SHOULD know their reporting schedule, but it is easy to
> forget.
>
> That's true, but there's also a matter of our *own* credibility. If we
> expect podlings to adhere to the schedule we set, we ought to adhere
> to it ourselves.
>
> Marvin Humphrey
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: Podling report reminders didn't go out

Posted by Marvin Humphrey <ma...@rectangular.com>.
On Fri, Mar 27, 2015 at 9:14 AM, Matt Franklin <m....@gmail.com> wrote:

> Do we have a cause for the continued failure to send reminders?

The script is fiddly and hard to test.  It's expanded beyond its
original scope and probably could stand to be refactored or rewritten.

> Every podling SHOULD know their reporting schedule, but it is easy to forget.

That's true, but there's also a matter of our *own* credibility. If we
expect podlings to adhere to the schedule we set, we ought to adhere
to it ourselves.

Marvin Humphrey

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


Re: Podling report reminders didn't go out

Posted by Matt Franklin <m....@gmail.com>.
On Fri, Mar 27, 2015 at 11:58 AM Marvin Humphrey <ma...@rectangular.com>
wrote:

> Greets,
>
> With the chaos of the Members meeting this week it went unremarked,
> but Marvin failed to send out report reminders again.  Reports are due
> next Wednesday.
>
> (Other Marvin.  The robot.)
>

Do we have a cause for the continued failure to send reminders?  Every
podling SHOULD know their reporting schedule, but it is easy to forget.


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