Difference between revisions of "Summer of Code/Checklist"
From BRL-CAD
(retitle) |
(regroup for clarity) |
||
| Line 3: | Line 3: | ||
Before the summer coding 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 GSoC coding 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. | Before the summer coding 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 GSoC coding 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 [[Google_Summer_of_Code/Project_Ideas|Project Ideas]] | # Review our [[Google_Summer_of_Code/Project_Ideas|Project Ideas]] | ||
| Line 37: | Line 37: | ||
* Discuss your plan via irc and/or on the mailing list | * Discuss your plan via irc and/or on the mailing list | ||
* Set up an interaction schedule with your mentor | * Set up an interaction schedule with your mentor | ||
| − | + | * Become a productive developer | |
| − | + | ** '''''[http://sourceforge.net/tracker/?group_id=105292&atid=640804 Post patches] until you get commit access''''' | |
| − | * '''''[http://sourceforge.net/tracker/?group_id=105292&atid=640804 Post patches] until you get commit access''''' | + | ** Write maintainable, portable, complete code |
| − | * Write maintainable, portable, complete code | + | ** Keep a '''daily''' log of your activities online somewhere (wiki user page is great for this) |
| − | * Keep a '''daily''' log of your activities online somewhere (wiki user page is great for this) | + | ** Report your progress periodically to the mailing list |
| − | * Report your progress periodically to the mailing list | ||
| − | |||
| − | |||
* Provide a final report on your project progress to the mailing list | * Provide a final report on your project progress to the mailing list | ||
* '''Continue working on BRL-CAD :-)''' | * '''Continue working on BRL-CAD :-)''' | ||
| + | |||
[[category:Google Summer of Code]] | [[category:Google Summer of Code]] | ||
Revision as of 00:16, 10 March 2011
GSoC Checklist
Before the summer coding 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 GSoC coding 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 Project Ideas
- Follow the Application Guidelines
- Understand your Acceptance Requirements
- Join the #brlcad IRC channel and introduce yourself
- Join the brlcad-devel mailing list and introduce yourself
- Discuss your application with the mentors
- Prepare your application
- Discuss your application with the mentors some more :)
- (optional) Post your application to your wiki user page (/wiki/User:username)
- (optional) Share and discuss your application on the mailing list
- Submit a patch if you don't have commit access
- Submit your application
IF YOU ARE ACCEPTED
- Agree to the acceptance requirements
- Read our participation expectations
- Read the development guidelines
- Familiarize yourself with Subversion
- Compile and run BRL-CAD from source
- Familiarize yourself with BRL-CAD's on-line resources
- Create a Sourceforge and brlcad.org wiki account
- Publish a development plan to the wiki
- Document a list of 3 to 10 development milestones
- Document your plan on the Wiki as a design document
- Discuss your plan 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 project progress to the mailing list
- Continue working on BRL-CAD :-)
