2013Q2 Call for Grant Proposals
Sun, 31-Mar-2013 by
As you might have noticed, TPF has been grating money for some big tasks, like funding Nicholas Clark or Dave Mitchel work on Perl 5. Nevertheless, TPF has a Grants Committee with its own budget (although not a big one), to give grants for smaller projects, ranging from $500 to $3000.
With this amount we do not expect to fund full-time work, but instead, use it as an incentive to complete some specific task. Therefore, you don't have to have a large, complex, or lengthy project. You don't even have to be a Perl master or guru. If you have a good idea and the means and ability to accomplish it, we want to hear from you!
If you have something that could benefit the Perl community but just need that little extra help, submit a grant proposal until the end of April. You would like to have the money, you have the knowledge, but do not know what do propose? Ask around and you will probably get some ideas. Some Perl pumpkins might post some ideas as comments on this post.
As a general rule, a properly formatted grant proposal is more likely to be approved if it meets the following criteria
* It has widespread benefit to the Perl community or a large segment of it.
* We have reasons to believe that you can accomplish your goals.
* We can afford it (please, respect the limits or your proposal should be rejected immediately).
To submit a proposal see the guidelines at "http://www.perlfoundation.org/how_to_write_a_proposal":http://www.perlfoundation.org/how_to_write_a_proposal and TPF GC current rules of operation at "http://www.perlfoundation.org/rules_of_operation":http://www.perlfoundation.org/rules_of_operation. Then send your proposal to email@example.com. Your submission should be properly formatted accordingly with our POD template.
Proposals will be made available publicly (on this blog) for public discussion, as was done in the previous rounds. If your proposal should not be made public,
please make this clear in your proposal and provide a reason.
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 -- and then I'm set. For Perl, I need to use perlbug, 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.
 Python, for example, has launchpad, openID, and google
 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).