Changes between Version 4 and Version 5 of GSoCersStartHere

Show
Ignore:
Timestamp:
05/04/10 23:58:34 (12 years ago)
Author:
darbelo
Comment:

Make "CLA" into links to the CLA.

Legend:

Unmodified
Added
Removed
Modified

  • GSoCersStartHere

    v4 v5  
    33The first thing you'll need to do is register an account on trac.parrot.org. This is a prerequisite to getting commit access to svn, which is managed via trac credentials. 
    44 
    5 The following step is to send in a signed copy of the Parrot CLA.  The instructions for sending it in are included in the document.  There can be some delay in the process of activating a commit bit after the CLA is recieved, so try to get this done as soon as possible.  In the meantime, you don't need a CLA to submit patches so feel free to do so.  Your GSoC mentor should be able to guide you on the patch submission process if you need any help, but the usual way is to open a Trac ticket with the patch attached and then bug people on IRC until it's committed or you get some feedback. 
     5The following step is to send in a signed copy of the Parrot [http://www.parrot.org/files/parrot_cla.pdf CLA].  The instructions for sending it in are included in the document.  There can be some delay in the process of activating a commit bit after the [http://www.parrot.org/files/parrot_cla.pdf CLA] is recieved, so try to get this done as soon as possible.  In the meantime, you don't need a [http://www.parrot.org/files/parrot_cla.pdf CLA] to submit patches so feel free to do so.  Your GSoC mentor should be able to guide you on the patch submission process if you need any help, but the usual way is to open a Trac ticket with the patch attached and then bug people on IRC until it's committed or you get some feedback. 
    66 
    77Subscribing to parrot-commits and parrot-dev is highly recommended. parrot-commits sends you a message with a diff every time there's a svn commit and parrot-dev is the place for general development discussion.  Most of the commit messages you can safely ignore, but they can provide some insight into how other developers work, and can help you gauge the community's general 'standard' for commit quality.  If you want a good example to follow, chromatic is a good choice, he's a good coder and usually does a very good job of explaining code changes in the commit messages.