> On Mar 14, 2016, at 3:48 AM, Shubham Chauhan <shubham13...@iiitd.ac.in> wrote:
>
>
>>
>> Something to add to the list is looking for existing bugs and patching them.
>
> There are many other tasks like deployment and debugging in the list (but is
> not in the list I shared), had kept that once gsoc coding period starts :P
It's worth noting that while deployment is certainly important and should be a
part of most development plans, it cannot be a substantial portion of your
proposal work during the gsoc coding timeframe.
Same goes for any gsoc project proposal. Non coding tasks like research, docs,
profiling, testing, etc., should be done during bonding or after and/or spread
throughout your coding timeline as a minor percentage of the work.
That doesn't mean you won't or shouldn't do those things -- they are a normal
part of development and important -- it means they cannot be a substantial
aspect during the coding window as GSoC's focus and all you may be evaluated on
is the code that gets written.
Cheers!
Sean
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
