[SoC] GSoC 2018 - get ready to submit your final reports and evaluations

Helmut Kudrnovsky hellik at web.de
Fri Aug 3 02:41:33 PDT 2018

Dear students,

According [1], it’s almost time to wrap up your GSoC project! We hope that you enjoyed coding with OSGeo, and we are sure that you learned a lot from your mentors and the vibrant OSGeo community.

Next week you will begin submitting your *Final Evaluations for GSoC 2018* (starting Monday, August 6).

Please study *Google’s Work Product Submission Guidelines* [2] and *OSGeo’s requirements* for your final report [3]:

1- The title of the project and the software community it belongs to (for
hybrid projects indicate all the software involved);

2- Abstract: a description of the general idea, motivation, challenges,

3- The state of the art BEFORE your GSoC. For example, if you made a GUI,
you can say: "In the software XYZ, when I wanted to use the tool xxx, I had
to manually edit the file yyy";

4- The addition (added value) that your project brought to the software. In
the same example: "With the GUI that I created, now it is possible to use
the tool xxx via graphical user interface";

5- If there is still work to be done on the project, include that too. You
can also share highlights or challenging pieces.

6- Add all the permanent links to access the code and documentation for the
user to get started with testing your application. "Please test my code
following instructions here". (Don’t forget to test that the links are
working and do not require special access permissions!) Ensure that the pull request
description is detailed. If the pull request is going to have more work
done after GSoC is over, make sure the last GSoC commit is noted.

7- At least an image that should serve to show the main elements of your
project. It could be a flowchart, a screenshot, both, or whatever you
think could serve for the scope. Remember: the aim is to showcase your
project to people that are not necessarily familiar with the software. The
image must  be loaded on a public repository or in the web page / wiki of
your project and the link shall be included in your report.

8- Optional: You can add links to videos, blog posts etc. that you have
created. (We really encourage it.)

In order to comply with the requirement of *a report in a stable location (the URL cannot be changed after submission)*, send your final report structured in the above mentioned way to this SOC mailing list. The report must be written as text inside your email (not as a separate attached document, not as a link to an external document).

You can find your final report mail in the SoC Archives (https://lists.osgeo.org/pipermail/soc/) and then use this permanent link to your final report mail in your GSoC final submission in your dashboard.

You must submit your final evaluations (with the submission URL) before *Tuesday, August 14 at 16:00 UTC*. Do not wait until the last minute on August 14. Once you submit your final evaluation, you cannot change it or the final report URL. That URL is what will be public on the GSoC archive site so you should want it to be representative of the work you did this summer.

If there are any open questions about your final submission, reach out proactively to your mentors and to this mailing list.

Kind regards,
OSGeo GSoC admin team

[1] https://summerofcode.withgoogle.com/how-it-works/#timeline
[2] https://developers.google.com/open-source/gsoc/help/work-product
[3] https://lists.osgeo.org/pipermail/soc/2018-July/004136.html

More information about the SoC mailing list