[GCompris-devel] Proposal for GSoC 2016

[JAZEIX Johnny]

Hi,

you should work 40 hours a week, not more ;).

What is the actual status of railroad? As I understood, it was well 
advanced?

In your timeline, there should be time for reviews (and fixing the 
issues/code found during the reviews) just after each activity. You 
should only work activity by activity and change only when one is 
finished (or close to be).

What do you mean by optimizing code? Is it cleaning?

For playpiano, what do you mean by algorithm?
There is already a base code for piano activity (branch *playpiano* 
<http://quickgit.kde.org/?p=gcompris.git&a=shortlog&h=7658e56653fd369873d3625bdc5aece5d948763c>) 
but it does not handle everything, do you plan to start from zero or use it?

For wordsearch, have you looked at existing algorithms to create levels?

Globally, for me 5 activities seems a lot to do.

Johnny

On 03/21/16 21:49, Irshaad Ali wrote:
> Hi,
> This is Irshaad Ali (GCEt, Bikaner). I am applying gor GSoC 2016.
> I attached My proposal.
>
> Kindly review the following ideas and give suggestions.
> Proposal : 
> https://docs.google.com/document/d/1LYZc9wG8GLFmjJNw2twviQbx3v_v0pKBEnlE6ezjkP0/edit?usp=sharing
>
>
> _______________________________________________
> GCompris-devel mailing list
> GCompris-devel at kde.org
> https://mail.kde.org/mailman/listinfo/gcompris-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/gcompris-devel/attachments/20160321/5ca46c23/attachment.html>