comment on

Reading perlguts, PerlGuts Illustrated, perlxstut and perlxs might help. The Porting directory in the perl source also contains a lot useful info.

However, there's a lot of source code with much magic hidden within. I'd suggest a more focussed approach, such as picking a TODO from perltodo and work towards DOing it.

The p5p mailing list (subscribe or archive) and #p5p on irc.perl.org could be sources of assistance, as well as here.

At some point, you will have to learn how to use git. There's a free book, or a more perl oriented cheat sheet in perlgit.

Update:

Another avenue you might like to try, is looking at perl5's bug-tracker (it's much easier to use if you log in first) and see if there are any bugs you can try to fix.

Update^2: Corrected address of #p5p (thanks moritz!)

Perl: perlintro    perlretut    perldoc    Basic debugging checklist    Yes, even you can use CPAN
PerlMonks: How do I post a question effectively?    Markup in the Monastery    How do I post a question effectively?    I know what I mean. Why don't you?
General: How To Ask Questions The Smart Way    What every computer scientist should know about floating-point arithmetic
To Be Continued...

In reply to Re: Hacking Perl (I think) by FunkyMonk
in thread Hacking Perl (I think) by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Keep It Simple, Stupid
	PerlMonks