Grokbase
x

Richard Foley (richard...@rfi.net)

Profile | Posts (21)

User Information

Display Name:Richard Foley
Partial Email Address:richard...@rfi.net
Posts:
21 total
21 in Perl 5 Porters

5 Most Recent

All Posts
1) Richard Foley Re: spending other people's money
| +1 vote
Taken off-list, as suggested.
Perl 5 Porters
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
Taken off-list, as suggested.

--
Richard Foley
Ciao - shorter than aufwiedersehen

http://www.rfi.net/

On Thursday 05 November 2009 12:00:44 James Laver wrote:
> On Thu, Nov 5, 2009 at 10:46 AM, Nicholas Clark <nick@ccl4.org> wrote:
> >
> > You don't need my permission to do this.
> >
> > Also, I'm afraid that I don't have much time to give advice. I know *why*
> > the details of the suggestion are they way that they are, so if you think
> > they should be different, I can say what that "breaks" from the original
> > intent, but I can't be sure to have a good idea of what the implications
of
> > an alternative going to be.
> >
> > The one thing I can say confidently is that a grants programme, certainly
> > the existing grants programme, is demonstrating that it is *not* a viable
> > system to convert money into people working on Perl 5 core bug fixing.
> >
> > Nicholas Clark
>
> Matt Trout and I put together the outline for how such a system would
> work, but both of us lost the time to actually work on creating it.
>
> If anyone is interested in taking up where we left off, please contact
> me offlist and I'll fill you in.
>
> --James
>
2) Richard Foley Re: spending other people's money
| +1 vote
If that's what's needed, I'd be happy to help put a proposal together.
Perl 5 Porters
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
If that's what's needed, I'd be happy to help put a proposal together.

--
Richard Foley
Ciao - shorter than aufwiedersehen

http://www.rfi.net/

On Thursday 05 November 2009 11:20:56 Nicholas Clark wrote:
> On Thu, Nov 05, 2009 at 11:03:57AM +0100, Richard Foley wrote:
> > This was a damned good idea, to do something concrete for Perl. Nearly 6
> > months later has anything happened with it? Has TPF:
> >
> > 1. approved the idea?
> >
> > 2. allocated (freely donated) funds?
> >
> > 3. created a procedure/team to handle the administration of this effort?
>
> I don't know the answers to any of these.
>
> I do know that I (no longer) have the time to get it started, nor to
> organise it. I had spoken to some people privately about 6 months ago, and
> I know that subsequently at least one I'd spoken with was aware that I no
> longer had time and so wasn't able to carry it forward. A couple of others
> have asked since, and I have said that I wasn't able to carry it forward.
>
> I made no application to TPF for funds to run this, because I hadn't got
> very far before I ran out of time, certainly not enough to need money.
>
> I would be very happy for anyone else to take the idea and run with it
> (I had hoped that that was obvious from the start). Perl shouldn't stall
> just because I run out of time.
>
> Nicholas Clark
>
3) Richard Foley Re: spending other people's money
| +1 vote
This was a damned good idea, to do something concrete for Perl. Nearly 6 months later has anything...
Perl 5 Porters
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
This was a damned good idea, to do something concrete for Perl.  Nearly 6 
months later has anything happened with it?  Has TPF:

1. approved the idea?

2. allocated (freely donated) funds?

3. created a procedure/team to handle the administration of this effort?

...yet?

--
Richard Foley
Ciao - shorter than aufwiedersehen

http://www.rfi.net/

On Saturday 30 May 2009 14:55:08 Nicholas Clark wrote:
> It's almost 6 months since booking.com kindly donated $50,000 to TPF
>
> to aid in the further development and maintenance of the Perl
programming
> language in general, and Perl 5.10 in particular.
>
> http://www.hsyndicate.org/news/4039070.html
> http://news.perlfoundation.org/2008/12/bookingcom_makes_a_major_contr.html
>
>
> So far there is no published plan to spend it, as best I can tell from out
> here the entire amount remains safely in the bank, and at it stands there
> will be no change in the next 6 months either. This aids neither development
> nor maintenance.
>
> Also, vienna.pm still has around $35,000 surplus from YAPC::EU 2007 to spend
> on "advancements of Perl": http://use.perl.org/~domm/journal/39013
>
>
> So, without consulting either group, or anyone with commit rights, here's an
> impertinent suggestion on how to try to spend other people's money. It has 3
> virtues:
>
> Laziness: It requires nearly no up front effort to organise
> Impatience: It tries to spend as much money as rapidly as possible
> Hubris: It ties to both get bugs fixed, and draw new people in.
>
>
> And the crazy scheme is: Offer bug bounties on every open Perl 5 bug*
>
>
http://rt.perl.org/rt3/Search/Results.html?Query=Queue%3D%27perl5%27AND(Status%3D%27open%27ORStatus%3D%27new%27)
>
>
> Anyone can claim:
>
> $25 for correctly identifying* the change that introduced a bug
> or demonstrating that the bug has been present since 5.000
> or explaining why it is not a bug, and should be closed
>
>    $25 for a committed TODO test*
> or for identifying the existing TODO test
> [may well be cheaper to write a new test.
>               I don't have a problem with this]
> or for identifying which bug this is a duplicate of, and merging
it
>
> [bugs in dual life modules can't earn any more, at this point*]
>
> $50 for Perl code that is committed to blead that fixes the bug
> $100 for Bourn shell, Makefile or other code that is committed to blead
that
>              fixes the bug
> $150 for XS or C code that is committed to blead that fixes the bug
>
> $200 bonus for fixing bugs present in perl 5.000
> $400 bonus for fixing bugs present in perl 1.000
>
>
> Hence $100 for completely resolving a Pure perl bug, or $200 for completely
> resolving a bug in C code.
>
> However, the minimum payout is $500, equivalent to
>
>   20 git bisect runs
>   or 10 bisect + TODO test
>   or 10 bisect and de-duplicate
>   or 5 bisect + fix pure perl bugs
>   or 2.5 bisect + fix C bugs
>
>
> Right, now the small print, and hence all the *s
>
> Currently there are 1390 new or open bugs. There isn't enough money (yet) to
> pay for them all. So there needs to be an initial budget, of some size, and
> first-come first-served on claiming it. Once it runs out, more fundraising
> needed.
>
> To stop anyone gaming the system by injecting bugs that they know can be
> closed, or are duplicates of current bugs, "every open Perl 5 bug"
> unconditionally means every bug currently open. All new bugs will be
considered
> by the judges, and may be deemed ineligible, if they suspect that there's a
> fraud involved. This seems unlikely, but people need to be aware of this
> before investing time and expecting money.
>
> For the sake of defining what's new and what's not, I'll pick bug 66092, the
> meta-bug for the 5.10.1 bugs, as the cutoff for "currently open".
>
> http://rt.perl.org/rt3/Public/Bug/Display.html?id=66092
>
> Dual life modules aren't (yet) eligible, unless the maintainer wants to join
> the scheme. For the rest of the document, "dual life modules" refers to
> modules whose maintainers are not involved.
>
> Bugs reported to core but found to be in dual life modules are only eligible
> for the first $25, and the second $25 if they are duplicates, or already
have
> a TODO test in place.
>
> ie NO MONEY CAN BE PAID OUT for code to be committed against dual life
> modules, because we don't control the codebase.
>
> "committed" means code is committed to one of the release branches in
> http://perl5.git.perl.org/perl.git and is not reverted within 14 days.
> (or a release, whichever comes sooner)
>
> "marked as duplicate" or "closed" should be done in rt.cpan.org by the
person
> claiming - ie you will need to have requested and got bug admin rights.
> [See, part of the plan is to suck you in. This isn't quite money for
nothing]
>
> "judges" are some group of people, not including me (I'm busy), probably
> people with commit rights (or people we've asked but they refused)
>
> any single judge is sufficient to validate a claim, unless
>
> 1: he or she committed the test or code in question
> 2: another judge disputes it within 7 days
> 3: he or she is also the claimant
>
> in which case all (other) judges should vote.
>
> [Yes, I want the judges to be able to claim too, because I suspect that some
> of the people with a track record of volunteering to find and fix bugs
would
> be good for this role,and I don't want them to be barred from getting
paid.]
>
>
> Validated claims will be accumulated until they reach $500, at which point
> they can be cashed in. I assume that accumulating claims will be tabulated
> by the judges collectively in public.
>
> "Correctly identified" is marked, because it needs to be awarded with some
> caution. The output from a git bisect run is not necessarily the change that
> caused the bug, particularly for bugs involving memory corruption. The
judges
> can and should seek advice or reject claims where the change implicated does
> not affect code related to the symptoms of the bug.
>
>
> The judges should make clear their scale of bribes, and publish all bribes
> offered, whether accepted, declined or outbid.
>
> Nicholas Clark
>
> PS SuperCollider Programming will not benefit from this scheme. :-)
>
4) Richard Foley Re: Bug in Debugger or DateTime?
| +1 vote
Seeing as it happens with (eg.) CGI (etc.), this suggests a debugger bug. richard@thpad:~> perl...
Perl 5 Porters
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
Seeing as it happens with (eg.) CGI (etc.), this suggests a debugger bug.

richard@thpad:~> perl -MCGI -de 0

Loading DB routines from perl5db.pl version 1.3
Editor support available.

Enter h or `h h' for help, or `man perldebug' for more help.

main::(-e:1):   0
  DB<1> m CGI->new
Not a subroutine reference at /usr/lib/perl5/5.10.0/perl5db.pl line 7934.
at /usr/lib/perl5/5.10.0/perl5db.pl line 7934
        DB::methods_via('CGI', '', 1) called 
at /usr/lib/perl5/5.10.0/perl5db.pl line 7904
        DB::methods('CGI=HASH(0xd73f00)') called 
at /usr/lib/perl5/5.10.0/perl5db.pl line 670
        DB::eval called at /usr/lib/perl5/5.10.0/perl5db.pl line 3436
        DB::DB called at -e line 1
Debugged program terminated.  Use q to quit or R to restart,
  use o inhibit_exit to avoid stopping after program termination,
  h q, h R or h o to get additional info.
  DB<2>                   

The relevant bit is here (xxx):

7920 sub methods_via {
7921
7922     # If we've processed this class already, just quit.
7923     my $class = shift;
7924     return if $seen{$class}++;
7925
7926     # This is a package that is contributing the methods we're about to 
print.
7927     my $prefix  = shift;
7928     my $prepend = $prefix ? "via $prefix: " : '';
7929
7930     my $name;
7931     for $name (
7932
7933         # Keep if this is a defined subroutine in this class.
7934         grep { defined &{ ${"${class}::"}{$_} } }   # <- here (xxx)!
7935
7936         # Extract from all the symbols in this class.
7937         sort keys %{"${class}::"}
7938       )
7939     {
7940
7941         # If we printed this already, skip it.
7942         next if $seen{$name}++;
7943
7944         # Print the new method name.
7945         local $\ = '';
7946         local $, = '';
7947         print $DB::OUT "$prepend$name\n";
7948     } ## end for $name (grep { defined...

--
Richard Foley
Ciao - shorter than aufwiedersehen

http://www.rfi.net/

On Tuesday 14 July 2009 12:40:50 Ovid wrote:
>
> I honestly have no idea if this is a bug in DateTime or the debugger. If
it's a bug in the debugger, it would be nice to fix and I don't have time to
look at it right now.
>
> Basically, when in the debugger, you can type "m" following by an object and
it will list the methods available on that object.  Here's an example of it 
failing when trying with a DateTime object.
>
>     $ perl -MDateTime -de 1
>
> Loading DB routines from perl5db.pl version 1.3
>     Editor support available.
>
> Enter h or `h h' for help, or `man perldebug' for more help.
>
>     main::(-e:1):    1
>       DB<1> m DateTime->now
> Not a subroutine reference at /usr/share/perl/5.10/perl5db.pl line 7930.
>     at /usr/share/perl/5.10/perl5db.pl line 7930
>       DB::methods_via('DateTime', '', 1) called 
at /usr/share/perl/5.10/perl5db.pl line 7900
> DB::methods('DateTime=HASH(0x94fb878)') called
at /usr/share/perl/5.10/perl5db.pl line 670
> DB::eval called at /usr/share/perl/5.10/perl5db.pl line 3434
>       DB::DB called at -e line 1
> Debugged program terminated. Use q to quit or R to restart,
> use o inhibit_exit to avoid stopping after program termination,
>       h q, h R or h o to get additional info.  
>
> Cheers,
>
> Ovid
> --
> Buy the book - http://www.oreilly.com/catalog/perlhks/
> Tech blog - http://use.perl.org/~Ovid/journal/
> Twitter - http://twitter.com/OvidPerl
> Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
>
>
5) Richard Foley Re: 5.12 release/roadmap? - unicode
| +1 vote
With the corollary of "forgive me in advance for speaking", and in the interests of getting...
Perl 5 Porters
[ Profile | Reply to group ] [ Flat  Thread  Threaded ]
With the corollary of "forgive me in advance for speaking", and in the
interests of getting something kicked out the door, how about:

0. Stop pussy-footing around and focus on *one* single task.

1. Take Rafael's suggestion as his "going out" present (last request).

2. Do: "the sanitization of Unicode semantics".

3. Release 5.12 - and it's (like the man said) done.

--
Richard Foley
Ciao - shorter than aufwiedersehen

http://www.rfi.net/

ps. 5.14 (etc.) is always there to take over the one or two otherwise
outstanding tasks ;-)

On Friday 29 May 2009 15:36:44 Rafael Garcia-Suarez wrote:
> 2009/5/28 Richard Foley <Richard.Foley@rfi.net>:
> > Is there a 5.12 release plan?
> >
> > If so, what is it, please ?-)
>
> What I would really have liked to have in 5.12, is a sanitization of
> Unicode semantics : something that we didn't include on 5.10, and that
> will break backwards compatibility for the greater good.
>
> (See "Unicode and lc/uc operators" and "UTF-8 revamp" in perltodo, and
> also "Properly Unicode safe tokeniser and pads", which is not
> completely unrelated.)
>
> This also includes the Unicode standard sanity checking that Karl started.
>
> However, this is a difficult problem. Rounding up tuits and talents
> will be needed. Where are Juerd and Yves gone lately?
>
> I don't see another important goal for 5.12 at the moment. Which
> means: once it's done, release.
>

spacer
Profile | Posts (21)
Home > People > Richard Foley