2013Q2 Call for Grant Proposals

Category: (none)

Comments (5)

IMHO it would be good if people with ideas for project, but without the time to do that would post them here. Then others who might lack the ideas, but have time and could do with some money, could pick up those ideas.

Let me start with one:

Act the toolkit that runs most of the Perl events have several installations. I think it would be nice to unite them - if the people who run these agree. This might involved merging the changes they made privately and merging the user data.

Proposal idea for the grabs: A web frontend to perlbug. Being able to fill up a form rather than mailing would make things easier for a lot of people. Or well, at least me : D

Brian: perlbug is a command line interface to send a mail to http://rt.perl.org/ -- however the perlbug tool is recommended (required?) because it helps gather the pertinent information about your Perl installation.

Ask: I know. And it makes it surprisingly onerous for anyone not using sendmail to actually report bugs (read: me. Go gmail).

Ruby, PHP and Python all have web forms. If I find a bug in them, at most I need to log in -- a minor annoyance if they have multiple ways of doing that[0] -- and then I'm set. For Perl, I need to use perlbug[1], follow the instructions, Save to File, put a filename, Quit, copypaste the file into a mail, remove the headers, yadda yadda.
That's ridiculous. Half of the time I simply give up and send a message on #p5p, then cross my fingers and hope that it catches someone's attention.

[0] Python, for example, has launchpad, openID, and google
[1] Which won't even get the right information if I'm trying to report a bug on blead

Brian: I see what you are saying, you don't mind perlbug but that perlbug only can submit via email.

Teaching perlbug to submit via HTTP and setup rt.perl.org to receive such submissions doesn't seem like it'd be a dumb idea to me (though I'm not volunteering).

Sign in to add comment