First of all I would like to apologize for the long post.

No need to apologize, thanks for the introduction!  It's exactly the sort of detail we like to see from students.  We don't get a lot of time to get to know you otherwise.

         I consider this project important because a smaller number of lines of code means an easier to understand source as well as an easier to debug one.

Maybe. :)  It's actually quite easy to reduce line counts and make code much harder to understand.  The intent and hope, however, is that lines aren't just reduced, but that they've been carefully refactored so that the main benefit becomes reduced maintenance overhead.

All code has a cost.  If long-term maintenance costs are reduced, the project sustains or improves productivity.  If you can also get code that's also easier to understand or debug, that's an added bonus (but just not a given).

     My exam session starts 19th of May and it ends on 8th of June and I don't know if I would be able to work more than 3-4 hours a week during that period. Aside of that I can work 40 hours a week, but I could also work more and I am willing to do so in order to compensate for the exam session period, as I have no other commitments during summer. The next academic year starts on 1st of October so I could say I have some extra time.
 
Just note scheduling issues like that in your proposal.  You have to list a few milestones anyways, so make sure your development timeline accounts for any vacations or exam periods you know about already.  Others can be worked out with mentors once accepted.
 
     I also plan not to get employed during my undergraduate studies so I could and I am willing to continue working with this organization after GsoC ends at least one year, if not more.

Excellent! 

      Which one of these projects should I choose?

Which sounds more interesting to you?  That one.

      Regarding the second project, I would like to try to fix one or more bugs before I apply for it, what would you recommend me to start with?

Any of the issues listed in our BUGS file would be good to start with.  Here's a recent one, for example:  "rtxray crashes if you specify a -o *.bw output file due to assumptions in the rt front-end that all output files are .pix"

Cheers!
Sean

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to