More GSOC instructions...

[Boudewijn Rempt]

In addition to what Tiar posted:

* You have to participate in the weekly meetings. These are almost always on Monday, 16:00 CEST. We have a new format compared to last year, where we end the meeting with a round table where everyone tells the rest what they've been up to.

* 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 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. Try to make that daily. Your mentor cannot see what you're doing if you don't show what you're doing. If you feel you're getting stuck, tell your mentor on #krita.

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

* There is also the requirement to keep up a wiki page: https://community.kde.org/GSoC/2020/StatusReports (check https://community.kde.org/GSoC/2019/StatusReports to see what that entails).


-- 
https://www.krita.org