Jump to content

GSoC/2017/StatusReports: Difference between revisions

From KDE Community Wiki
Valoriez (talk | contribs)
Created page with "== Status reports for GSoC 2017 == '''''Remember to submit this link to Google Summer of Code; creating your report here is not enough.''''' A good status report will includ..."
 
Valoriez (talk | contribs)
No edit summary
Line 5: Line 5:
A good status report will include:
A good status report will include:


#. Design documents the student created
# Design documents the student created
#. Short video of the work, or screenshots as appropriate
# Short video of the work, or screenshots as appropriate
#. Link to a list of commits ( [https://developers.google.com/open-source/gsoc/help/work-product example] )
# Link to a list of commits ( [https://developers.google.com/open-source/gsoc/help/work-product example] )
#. Link to blog posts (on kdeplanet, at least monthly)
# Link to blog posts (on kdeplanet, at least monthly)


This is the summary of the GSoC project.
This is the summary of the GSoC project.

Revision as of 04:24, 9 February 2017

Status reports for GSoC 2017

Remember to submit this link to Google Summer of Code; creating your report here is not enough.

A good status report will include:

  1. Design documents the student created
  2. Short video of the work, or screenshots as appropriate
  3. Link to a list of commits ( example )
  4. Link to blog posts (on kdeplanet, at least monthly)

This is the summary of the GSoC project.

Students list

Please keep list sorted.

John Doe (Template )