[SoC] Kind Reminder | GSoC 2022 - Instructions for Packaging your Work and Final Submission Guidelines | Deadline - September 12, 18:00 UTC

[Rahul Chauhan]

Dear GSoC Candidates,

This is a kind reminder to our previous email regarding instructions for
packaging your work and final submission. Please remember that the
deadline to *submit your final project* and *fill the mentor
evaluation* is *September
12**, 18:00 UTC *and this is a hard deadline.

We congratulate you all for the great work over the GSoC 2022 and we are
looking forward to your final reports. Thanks to the candidates who have
already shared their final reports.

All the best!
Kind regards,
OSGeo GSoC Administration Team

---------- Forwarded message ---------
From: Ashish Kumar <ashishkr23438 at gmail.com>
Date: Tue, Sep 6, 2022 at 11:18 PM
Subject: Instructions for Packaging your Work and Final Submission
Guidelines: Final Evaluation open Sep 5 - Sep 12, 18:00 UTC
To: OSGeo Google Summer of Code list <soc at lists.osgeo.org>
Cc: gsoc-adminosgeo.org <gsoc-admin at osgeo.org>, Rahul Chauhan <
rahulnitsxr at gmail.com>, Rajat Shinde <rajatshinde2303 at gmail.com>


Dear GSoC students,

The final evaluation and code submission deadline is approaching. The
dashboard is active now for submitting the evaluation and would be active
till Sep 12 18:00 UTC. You might have already received an email from the
GSoC Admins team in this regard. As official GSoC 2022 timeline mentions
[1]:

*Final week: GSoC contributors submit their final work product and their
> final mentor evaluation (standard coding period): September 5 - September
> 12, 18:00 UTC**.*
>

Since all the projects were of standard length (12 weeks), we are supplying
those dates above. Hats off to all the contributors for making sure to
complete their projects within the standard length duration.

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. We
appreciate your efforts for standing strong and reaching this far, as they
say - *"when the going gets tough, the tough get going". *We are sure that
you all must be having your great stories associated with GSoC 2022. The
final step is wrapping up and packaging your project for final submission.

According to Google [2], the basic requirements for code submissions are:

   - It must be easy to identify the work you have done. (i.e. the changes
   you made or new code.) When someone goes to the provided URL it should be
   clear what work you did without requiring them to do significant
   additional digging.

   - It should be in a stable location. The URL cannot be changed after
   submission.

   - Someone else should be able to use the content at (or referenced from)
   the target of the link to extend your work. If your work is 100%
   complete, they should be able to use it. If your work is not 100%
   complete, it should be clear what's left to do.

You are also required to submit your final report to the SOC mailing list.
Your final report must include:

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

*Note:* If your title has changed over the due course of project, then do
not forget to update it to the Dashboard and put the final updated title in
the report;

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

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 edit the file yyy manually";

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, add a graphical image that should serve to show the main
elements of your project. It could be a flow chart, 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 uploaded 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 warmly encourage it. It feels highly elated to see your work or
read a blog post in future.)

The report must be included as text inside your email (not as a separate
attached document, not as a link to an external document). Also, remember
to add the link to your project wiki page and add the final report in your
 wiki.

In order to comply with Google’s requirement of *a report in a stable
location (the URL cannot be changed after submission)*, you can either
check with your mentors for a suitable URL (e.g. a permanent wiki page that
you maintained throughout the program) or submit the URL of your final report
mail. You can find the URL of your final report mail in the SoC Archives
[3] and then use this permanent link to your final report mail in your GSoC
final submission in your dashboard.

To summarize, you must submit your:

   1. Final report mail to the SOC mailing list (based on the above
   template), and
   2. The final mentor evaluations (with the submission URL) on the GSoC
   dashboard.

before *September 12, 18:00 UTC*. Do not wait until the last minute on
September 12, because this is a *hard deadline*, and *f**ailure to submit
evaluations properly may result in failing the program*. Once you make the
final work submission on the dashboard, you can edit it until the
deadline, so do it as soon as possible, because any improvements can be
made later on. That URL is what will be public on the GSoC public archive
site [4], so you should want it to be representative of the work you did
this summer.

If this seems overwhelming, there is no need to worry. You can look at the
following submission made last year for your reference: Final report mail
[5], and GSoC dashboard submission with URL [6].

Please reach out proactively to your mentors and this mailing list in case
of any further queries.

We want to see you as a lifetime contributor and a supporter of the project
you worked on!

All the best!

Kind regards,
Your OSGeo GSoC Admins.

[1] https://developers.google.com/open-source/gsoc/timeline
[2] https://developers.google.com/open-source/gsoc/help/work-product
[3] https://lists.osgeo.org/pipermail/soc/
[4] https://summerofcode.withgoogle.com/archive
[5] https://lists.osgeo.org/pipermail/soc/2021-August/004813.html
[6]
https://summerofcode.withgoogle.com/archive/2021/projects/5684733287071744


-- 


Regards:
*Rahul Chauhan*
LinkedIn <https://www.linkedin.com/in/rahulworld> | Github
<https://github.com/rahulworld> | Web <https://rahulworld.github.io/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/soc/attachments/20220912/fad3ee38/attachment-0001.htm>