Changes between Version 6 and Version 7 of GSoCersStartHere

Timestamp:

04/10/11 03:57:56 (11 years ago)

Author:

soh_cah_toa

Comment:

Fixed mailto links. Also added link to GSoC page which I forgot before. It's overkill, I know.

GSoCersStartHere

@@ -1 @@
-This is a page aimed at helping students working on Parrot as part of Google Summer of Code to get acclimated into the community.  It doesn't deal with any coding matters but rather the administrative matters you'll need to get out of the way first.
+This is a page aimed at helping students working on Parrot as part of [http://www.google-melange.com Google Summer of Code] to get acclimated into the community.  It doesn't deal with any coding matters but rather the administrative matters you'll need to get out of the way first.
 
 The first thing you'll need to do is register an account on [http://trac.parrot.org Trac]. This is a prerequisite to getting commit access to our [https://github.com/parrot/parrot GitHub] repository, which is managed via [http://trac.parrot.org Trac] credentials.
@@ -5 +5 @@
 The following step is to send in a signed copy of the Parrot [http://www.parrot.org/files/parrot_cla.pdf Contributor License Agreement].  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 received, 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 [http://trac.parrot.org Trac] ticket with the patch attached and then bug people on IRC until it's committed or you get some feedback.
 
-Subscribing to [mailto:parrot-commits@lists.parrot.org parrot-commits] and [mailto:parrot-dev@lists.parrot.org parrot-dev] is highly recommended. [mailto:parrot-commits@lists.parrot.org parrot-commits] sends you a message with a diff every time there's a git commit and [mailto:parrot-dev@lists.parrot.org parrot-dev] is the place for general development discussion.  Most of the commit messages can be safely ignored, 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.
+Subscribing to [http://lists.parrot.org/mailman/listinfo/parrot-commits parrot-commits] and [http://lists.parrot.org/mailman/listinfo/parrot-dev parrot-dev] is highly recommended. [http://lists.parrot.org/mailman/listinfo/parrot-commits parrot-commits] sends you a message with a diff every time there's a git commit and [http://lists.parrot.org/mailman/listinfo/parrot-dev parrot-dev] is the place for general development discussion.  Most of the commit messages can be safely ignored, 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.
 
 You will also be required to blog on a weekly basis, as a form of status report, on the [http://www.parrot.org Parrot] site.  This is a Drupal instance for which you will need another set of credentials, separate from [http://trac.parrot.org Trac].  The best way to get set up for blogging is to create an account on your own and then ask Coke on IRC to give you the right set of privileges. In case you can't get a hold of him, create a [http://trac.parrot.org Trac] ticket for that task and assign it to him.