[Kde-scm-interest] GSoC coding workflow

[Anne-Marie Mahfouf]

Hi,

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.

Code
- 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.

Licencing
- all coded files should have a licence header as explained in 
http://techbase.kde.org/Policies/Licensing_Policy

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

Anything else? Is that OK?

Best regards,

Anne-Marie