James E Keenan wrote:
1. I will encourage all of you who wrote me to get Bitcard accounts
(http://tinyurl.com/5eqcw8) so that you're eligible to post patches
through our RT interface (http://rt.perl.org/rt3/Public). One of the 6
already has an RT account; the others of you should get one.
I know that at least one of the five has acquired a Bitcard account.
2. I will file an RT for some cleanup work on the configuration steps
tests and direct one person who specifically volunteered for that to
that RT. (Of course, once an RT is filed, anyone can take a crack at it.)
http://rt.perl.org/rt3/Ticket/Display.html?id=58740
3. I will file a separate RT for another project. This second RT will
actually be a way to track progress on more than a dozen RTs focusing on
smartlinks. I will encourage the other people who wrote me over the
past night and day to work on those.
http://rt.perl.org/rt3/Ticket/Display.html?id=58742 is the marker
ticket, and thanks to szbalint we have resolved one of the 12 remaining
underlying tickets.
4. Any other Perl 5 projects connected to Parrot we can have people
work on? Please let me know.
Here is a search query for our RT that will yield plenty of open tickets
-- though they're not limited to Perl 5. They cover C and PIR as well.
http://tinyurl.com/4kd4g8
Paul T Cochrane was the cage cleaner par excellence but hasn't been as
active recently. So here are tickets that he opened that have not been
resolved or rejected.
Paul had a program to go through our source code searching for inline
comments marked with TODO or XXX. The program would then open an RT
with the substance of the code and, in the code itself, replace TODO or
XXX with RT #nnnnn.
This was cage cleaning with a top-of-the-line Electrolux! But what it
meant was that many tickets were opened saying that something *ought* to
be implemented but not necessarily explaining why. After all, the
inline comment could have been written years previously. So when we're
looking at this type of RT, we have to study the context carefully first
to determine whether the TODO item should actually be done or not. If
the former, we have to do it.
Ladies and gentlemen, start your engines!
kid51
