Greetings and Salutations.
I was wandering around the Internet the other day and came across this interesting little project called Perl 6. A closer look revealed an equally promising (if a little strangely named) virtual machine. I've been looking for a replacement for python and ruby (which are both excellent, but have a few 'features' (or lack thereof) that are a little less than desireable. The communities also seem to lack direction, but I digress). So in order to learn more about Perl 6, I'd like to get involved. My question is which is the best way to go about doing this?
A few sub-questions as well:
- Should I read all the exegesis and apocalypses first? Just the exegesis? Also, where are they? I can't find exegesis 1 (are there any past 5?) and a search on perl.com only turns up one apocalypse.
- I take it Perl 6 and Parrot are completely separate projects. Which one requires more assistance? There's obviously some very talented people involved already, how much more help is needed? In what areas? Which brings me to the next point...
- Documentation - where's it at? What needs to be written? If this is similar to other open source projects I've looked at closely, this seems to sadly be the last thing that gets done. Also, testing - how can I help in that area?
- Level of skill required? Do I have to be a C god? or can someone with a moderately in-depth understanding of the language still contribute substantially code-wise? Is Perl 5 (or any other language) knowledge also of use?
I know I've missed a few points, I'll post them in the follow-ups if I remember them. As for posting this here instead of on the mailing lists - this does seem to be The Perl site and I noticed several of the Perl 6 developers frequent here, so no harm in discussing it here and increasing awareness, right?
Thanks :-)
-
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.
|