Difference between revisions of "Google Code In/Checklist"
From BRL-CAD
Mandeepkaur (talk | contribs) |
Mandeepkaur (talk | contribs) |
||
| Line 11: | Line 11: | ||
= IF YOU HAVE ASSIGNED TASK = | = IF YOU HAVE ASSIGNED TASK = | ||
| − | |||
| − | |||
| − | |||
| − | |||
* Read our [http://brlcad.svn.sourceforge.net/svnroot/brlcad/brlcad/trunk/HACKING development guidelines] | * Read our [http://brlcad.svn.sourceforge.net/svnroot/brlcad/brlcad/trunk/HACKING development guidelines] | ||
* Familiarize yourself with Subversion | * Familiarize yourself with Subversion | ||
Revision as of 14:36, 23 October 2013
Before the google code in begins, there are several things that students should do to become familiarized with BRL-CAD development. Below is a checklist of things each student should complete before the official start date. Some items on the checklist should occur during the application submission process while others need to occur before it's time to start coding.
IN ORDER TO APPLY
- Review our GCI Tasks
- Join our #brlcad IRC channel and introduce yourself (web interface here)
- Join our brlcad-devel mailing list and introduce yourself
- Claim task from tasks list.
- Discuss your task with our mentors (don't wait!)
IF YOU HAVE ASSIGNED TASK
- Read our development guidelines
- Familiarize yourself with Subversion
- Compile and run BRL-CAD from source
- Familiarize yourself with BRL-CAD's on-line resources
- Discuss your task/problems via irc and/or on the mailing list
- Set up an interaction schedule with your mentor
- Become a productive developer
- Post patches until you get commit access
- Write maintainable, portable, complete code
- Keep a daily log of your activities online somewhere (wiki user page is great for this)
- Report your progress periodically to the mailing list
- Provide a final report on your task progress to the mailing list
- Continue working on BRL-CAD :-)
