Summer of Code Instructions for Students

[Boudewijn Rempt]

Hi Sharaf, Albert, Kuntal, Tusooa,

Congrats on getting a slot for this year's Google Summer of Code. Life is going to be earnest and strenuous for y'all from now on! Here are some ground rules for students:

* You have to participate in the weekly meetings. These are almost always on Monday, 14:00 CEST. You will need to maintain your doing/done/todo section in that meeting document. This week's meeting is today, though!

* You have to have a blog, make sure the blog is registered with planetkde.org and you need to blog at least ever other Friday, whether or not you feel you've made progress.

* You have to make a task on Phabricator where you keep note of commits and things you're working on. This task + your commits will be your deliverable to Google

* You should work in a branch; the naming conventions are commiter_name/T#####-title-of-the-task, where #### is your task number.

* You should commit early and often. Don't collect huge changes that you commit only once a month. Commit when you've done something and push the commits. Your mentor cannot see what you're doing if you don't show what you're doing.

* Communication between you and your mentor happens on #krita (maybe through the matrix bridge) and the kimageshop at kde.org mailing list. Private conversations and queries on IRC, or through other chat applications are not allowed under KDE's rules for summer of code students (except for really personal stuff: if you've fallen sick or got an accident, you can approach both your mentores privately).


-- 
https://www.krita.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kimageshop/attachments/20190507/ba2f1abf/attachment.sig>