Changes between Version 30 and Version 31 of NewParrotDeveloperGuide
- Timestamp:
- 04/10/11 04:36:22 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NewParrotDeveloperGuide
v30 v31 6 6 Hopefully this will evolve into a road map for those who wish to contribute but are having trouble getting started. 7 7 8 == Before you start ==8 == Before You Start == 9 9 10 10 Before you download and compile Parrot, you may want to check you system to make sure you have the following packages installed. 11 11 12 * [http://perl.org Perl] (5.8.4 or later is required; run perl --versionto find out what you have)12 * [http://perl.org Perl] (5.8.4 or later is required; run {{{perl --version}}} to find out what you have) 13 13 * [http://perldoc.perl.org/perldoc.html perldoc] (provided by package {{{perl-doc}}} on Debian/Ubuntu). 14 14 * [http://git-scm.com/ git] … … 99 99 More information about the subject can be found on our `docs/` folder. More precisely, here: [https://github.com/parrot/parrot/blob/master/docs/tests.pod docs/tests.pod] 100 100 101 == Submitting your work ==101 == Submitting Your Work == 102 102 103 103 In general you'll need to create a patch and then create a ticket on Parrot's [http://trac.parrot.org/parrot/report/1 ticket tracking system]. Give as much details as you can. A good idea is to provide a list of all files affected with summary of the changes made in each file and the reasons that made you change them. And don't forget to attach your patch directly to the ticket. … … 111 111 Once again there is a POD covering this topic. Read [https://github.com/parrot/parrot/blob/master/docs/submissions.pod docs/submissions.pod] for specific details on how to submit your work. 112 112 113 == Getting feedback ==113 == Getting Feedback == 114 114 115 115 If the Parrot's ticket tracking system is not enough to discuss about patches you wrote or features that you would like to develop, you can subscribe to the `parrot-dev` mailing list using this [http://lists.parrot.org/mailman/listinfo/parrot-dev subscription form]. There is also an official mailing list called `parrot-users`. The subscription form is available [http://lists.parrot.org/mailman/listinfo/parrot-users here]. 116 116 117 117 For real-time feedback you can go to the `#parrot` channel, available on the `irc.perl.org` network. Parrot developers can be found there in almost any time of the day. 118 119 == Additional Resources == 120 121 * [http://docs.parrot.org/parrot/latest/html/ Parrot Official Documentation] 122 * [http://coolnamehere.com/geekery/parrot/learn/ Parrot Babysteps] 123 * [http://en.wikibooks.org/wiki/Parrot_Virtual_Machine Parrot Virtual Machine @ Wikibooks] 124 * [http://planet.parrotcode.org/ Planet Parrot] 125 * [http://www.tutorialspoint.com/parrot/ Parrot Tutorial @ Tutorials Point]