[Kde-scm-interest] GSoC coding workflow

Anne-Marie Mahfouf annemarie.mahfouf at free.fr
Sun Mar 27 18:39:55 CEST 2011


I feel some guidelines need to be established in order to have a nice workflow 
from GSoC students. Below are some points I think should help, I propose to 
put them on a Community wiki page if you all agree about them.

- for additional features to Foo project still in svn, develop the GSoC in a 
svn branch  (naming convention?)
- for additional features to Foo project in Git, develop the GSoC in a Git 
branch of foo (naming convention?)
- for new code, use a Git personal repository as described here 
http://community.kde.org/Sysadmin/GitFAQ#Personal_scratch_repositories and 
when the code is mature and stable enough, move it to git playground.

- all coded files should have a licence header as explained in 

(I saw student code without proper licencing so I think this needs to be 

Anything else? Is that OK?

Best regards,


More information about the Kde-scm-interest mailing list