960
edits
Difference between revisions of "Summer of Code/Students Guidelines"
Summer of Code/Students Guidelines (view source)
Revision as of 02:16, 24 April 2008
, 02:16, 24 April 2008Added some notes from emails
(Mention CFC) |
(Added some notes from emails) |
||
| Line 4: | Line 4: | ||
* [http://freenode.net/faq.shtml#userregistration Register your nick on FreeNode.net] (it's a good idea for your IRC and SF.net nicks to be similar/identical). | * [http://freenode.net/faq.shtml#userregistration Register your nick on FreeNode.net] (it's a good idea for your IRC and SF.net nicks to be similar/identical). | ||
* Ideally stay connected to IRC and in [irc://irc.freenode.net/scummvm #ScummVM], it is often the quickest way to resolve issues with your mentor or get feedback from the larger team. If you can't stay connected to IRC please review the [http://logs.scummvm.org logs] frequently. | * Ideally stay connected to IRC and in [irc://irc.freenode.net/scummvm #ScummVM], it is often the quickest way to resolve issues with your mentor or get feedback from the larger team. If you can't stay connected to IRC please review the [http://logs.scummvm.org logs] frequently. | ||
* [https://lists.sourceforge.net/lists/listinfo/scummvm-devel Subscribe to the scummvm-devel mailing list. | * [https://lists.sourceforge.net/lists/listinfo/scummvm-devel Subscribe to the scummvm-devel mailing list] and briefly introduce yourself to the team. Tell them who you are, what you are going to work on, where your blog is, what your IRC nick is. | ||
* Read and follow our [[Code Formatting Conventions]]. | * Read and follow our [[Code Formatting Conventions]]. | ||
* Commit your code as soon as possible, preferably on a daily basis or more often. Our preferred approach to code commits is 'commit early, commit often'. Remember that your code is one of the key project deliverables so the more code we can see the easier it is to judge progress and help ensure that everything goes smoothly. | * Commit your code as soon as possible, preferably on a daily basis or more often. Our preferred approach to code commits is 'commit early, commit often'. Remember that your code is one of the key project deliverables so the more code we can see the easier it is to judge progress and help ensure that everything goes smoothly. | ||
* We use [http://subversion.tigris.org/ Subversion (SVN)] as our version management system. Please refer to the online book [http://svnbook.red-bean.com/ Version Control with Subversion] for instructions on how to use SVN. Please also note that all students will be working of individual [http://svnbook.red-bean.com/en/1.4/svn.branchmerge.whatis.html branches] of ScummVM not our main development code. | * We use [http://subversion.tigris.org/ Subversion (SVN)] as our version management system. Please refer to the online book [http://svnbook.red-bean.com/ Version Control with Subversion] for instructions on how to use SVN. Please also note that all students will be working of individual [http://svnbook.red-bean.com/en/1.4/svn.branchmerge.whatis.html branches] of ScummVM not our main development code. It's suggested that you use [http://www.orcaware.com/svn/wiki/Svnmerge.py svnmerge.py] for your branch. It might make it so much easier to do merging later on. | ||
* Reflect your progress in a weblog. If you don't have one already, try [http://www.blogger.com/ Blogger], [http://wordpress.com Wordpress] (see also http://wordpress.org), [http://www.movabletype.com/ Movable Type], ... | * Reflect your progress in a weblog. It's fine to reuse your existing weblog, if you have one, with a "ScummVM GSoC" category or so. If you don't have one already, try [http://www.blogger.com/ Blogger], [http://wordpress.com Wordpress] (see also http://wordpress.org), [http://www.movabletype.com/ Movable Type], ... Start blogging very soon, even if it's just a "First post" so we can have a definite URL and we can subscribe to it. (BTW, you might want to add it to http://planet-soc.com/, too). | ||
* Create your user page on our Wiki and give a brief overview on what you are working on. However, your weblog is the main place to write about your progress. | * Create your user page on our Wiki and give a brief overview on what you are working on. However, your weblog is the main place to write about your progress. | ||