Context Navigation

Changes between Version 2 and Version 3 of GSoCersStartHere

Timestamp:: 05/04/10 20:23:20 (12 years ago)
Author:: darbelo
Comment:: Mention that students should swarm Coke and demand he do stuff for them.

v2	v3
7	7	Subscribing 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.
8	8
	9	You will also be required to blog on a weekly basis, as a form of status report, on the parrot.org site. This is a drupal instance for which you will need another set for credentials, separate from trac. The best way to get set up for blogging is to create the account on your own and then ask Coke on IRC to give you the right set of privileges. Or, in case you can't get a hold of him, create a Trac ticket for that task and assign it to him.
	10
9	11	Attending the parrot developers weekly #parrotsketch planning meetings are mandatory for all GSoC students, as that is the place where developers post 'status reports' letting everyone else know how their tasks are progressing and the weekly development priorities are set. You should also explore the wiki a bit, but I guess you must already be doing it if you are here ;).