Pratik Chandra Roy <[EMAIL PROTECTED]> wrote: > I was wondering, whether I would just remain a mere > spectator, or will I get an opportunity to do anything > as well.
Hello Patrik, Parrot isn't really an environment where people are *assigned* work; they just do something that's necessary. If you're not sure what to do... * Documentation is always nice, and usually sorely lacking. * Likewise with tests. * The Parrot todo list is at <http://www.parrotcode.org/todo.html>. Some of the items are more estoric than others. * Dan Sugalski (the internals designer) will occasionally post a "small task for the interested" to the list, which you could do. You can search the archives for old ones and see if they've been done. If you're using Windows, there are several todo items specifically for that OS; fixing those would be helpful, since there aren't too many Windows hackers here. If you're familiar with assembly language on a processor other than the i386, the JIT people could use a hand. If you know Python, there's a half-finished Python implementation you can work on...just poke around and you'll find things. HTH, -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker There is no cabal. [I currently have a couple Gmail invites--contact me if you're interested.]
