6 June, 2005 at 10:45 Leave a comment

 

How to Write a Proposal

Send proposals to tpf-proposals@perl-foundation.org. Plain-text is best, following this format:

Name

Email
Where can we contact you?

Project Title

Synopsis
A short description.

Benefits to the Perl Community

Deliverables
Quantifiable results e.g. "Improve X modules in ways Y and Z",
"Write 3 articles for X website".

Project Details
A more detailed description.

Project Schedule
How long will the project take? When can you begin work?

Bio
Who are you? What makes you the best person to work on this project?

Amount Requested

If you aren’t the primary maintainer of the project you want funding for, show that you have approval from the primary maintainer.

We’ll be marking proposal status on each submission, so if you have several proposals, or several semi-independent segments of a proposal it’s generally best to split them into different messages.

To make sure we don’t keep reviewing the same proposals long after the proposer has gone on to other projects, we’ll automatically mark a proposal as expired after it’s been reviewed in two quarterly grant cycles (so, about 6 months). You can always resubmit an updated proposal.

All applicants will be notified of the success or otherwise of their proposal. For queries, more information or assistance with preparing proposals, please contact tpf-grants-secretary@perl-foundation.org


The following ideas were added for Google’s Summer of Code 2005. (Some are more appropriate for graduate CS students). If any of these interest you, contact the grants secretary above and we’ll connect you with an appropriate mentor.

  • Automated smoke testing for CPAN.
  • Smoke testing architecture for binary compatibility between versions of Perl.
  • Benchmarks for PGE (Parrot Grammar Engine).
  • Anything in the Perl 5 TODO list.
  • Polish up and finish off P5NCI.
  • LLVM <-> Parrot interop
    • Parrot as LLVM backend (LLVM -> PASM)
    • PIR -> LLVM (not really, but evaluate optimizations)
    • Implement well-known optimizations in PIR compiler (SSA -> register allocation)
    • Runtime & offline bytecode optimization
  • Parrot GC: generational, multi-threaded GC
  • Parrot JIT: improve & complete JIT for some set of subsystems from alpha to Z8000 i.e. several pieces, one per platform
  • Parrot threads: STM (software transactional memory as in GHC, et al.) for Parrot

the camel
Advertisements

Entry filed under: Uncategorized.

Powered by Maven

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed


Calendar

June 2005
M T W T F S S
« May   Jul »
 12345
6789101112
13141516171819
20212223242526
27282930  

Tweets


%d bloggers like this: