[GCompris-devel] GCompris

JAZEIX Johnny jazeix at gmail.com
Wed Feb 24 16:19:08 UTC 2016


Hi,

welcome.

As said, do what you want, the [1] gives you ideas on what is actually 
missing. Some activities are more easy than others to do.

There are two ways to work, either use github and send pull requests to 
https://github.com/bdoin/GCompris-qt or if you use kde git, you can use 
https://git.reviewboard.kde.org to send the diff.

In both cases, for the beginning we'll merge the code for you.

The wiki has some information that may help you: 
http://gcompris.net/wiki/Developer's_corner, 
http://gcompris.net/wiki/An_exercise_for_new_contributors and 
http://gcompris.net/wiki/Contribution_process for example.

There are no stupid questions, feel free to ask if you have more :).

Johnny

On 02/24/16 17:04, Nilesh Kokane wrote:
> Thanks for your reply.
>
> On Wed, Feb 24, 2016 at 3:34 AM, Bruno Coudoin
> <bruno.coudoin at gcompris.net> wrote:
>> Hi,
>>
>> Thanks for your interest in GCompris.
>>
>> Now that you have a good idea of what GCompris is about, you probably
>> saw our bug tracker [1] and our idea list [2].
>>
>> It is up to you to tell us what you want to do for GCompris, we will do
>> our best to guide you to make a nice contribution.
>>
>> Bruno.
>>
>> [1] https://phabricator.kde.org/project/view/1/
>> [2] http://gcompris.net/wiki/Ideas_for_activities
> I'll go for [1] . Which branch should I work on?
>
> As of now I've cloned master and it builds without complains with
> Qt-Creator. Should I be following [3] to send patches?
>
> Please spare me if these questions seems silly.
>
> 3. https://techbase.kde.org/Contribute/Send_Patches.
>



More information about the GCompris-devel mailing list