[SoC] GSoC 2020 – Congratulations to the Accepted Students! What's next: Community Bonding Period (May 4 - May 31, 2020)

Rajat Shinde rajatshinde2303 at gmail.com
Thu May 7 07:19:59 PDT 2020


Dear Students,

Heartiest congratulations to those who have been accepted for GSoC 2020.

* Please watch this 5 minutes video for an introduction about the
expectations in the coming days: *

https://youtu.be/Pb5N6mD5cbg

The Community Bonding Period (May 4 - May 31, 2020) has started and you all
are required to actively participate in it. You should make full use of
this period by introducing yourself to your project community,
understanding the code structure, understanding the documentation. Read the
following blog post to understand what the Community Bonding period is all
about, it is an old post but explains very well:
http://googlesummerofcode.blogspot.com/2007/04/so-what-is-this-community-bonding-all.html

In short, after Community Bonding Period you should be ready to start
achieving your coding objectives post June 1, 2020 when the official coding
period starts. Students that haven’t participated actively in the community
bonding period could be removed from the program. You can even start coding
during the community bonding period after discussing it with your Mentors.

What are you going to do during the Community Bonding period?

*****************
* Request writing access to the OSGeo wiki [1], you need it to edit all
info related to your project
* Get to know your mentors, establish with them a way of communication,
that can be video call, chat, email, etc. You are supposed to communicate
regularly and often with your mentors.
* Familiarize with the community practices and processes: how does the
community communicate? Where is the source code published? How does the bug
tracker work?
* Introduce yourself and your project in SOC mailing list as well as the
mailing list used by your software community, and start a public dialogue
to gather feedback and refine your project accordingly.
* Redefine your project with more detailed weekly milestones, with the help
of your mentors and the feedback of the community, embedding the evaluation
periods in your timetable, adding more details, figuring out potential
issues, etc.
* Become familiar with the developer manuals
* Study material relevant for your project
* Install the developer environment and get ready to start coding
* Participate in Mailing Lists / IRC / etc, try and help users
* Start coding for bug fixes NOT necessarily related to your project: it is
a good exercise to become familiar with the code base. Include these bug
fixes into your report due at the end of bonding period.
* Set up your repository and wiki page for your project. You are free to
blog/tweet about it too, if you wish. Don’t forget to include these info in
the report due at the end of the bonding period.
* Ask your mentors for guidance on how to commit to the project repository.
Bear in mind that you should commit often, not just at evaluation periods.
However, depending on the policy given by your mentors, you might be
requested to commit in your own repository and make a PR only when the code
is mature to be included in the main repo. Discuss the details with your
mentors.
*****************

What is required immediately from you?

1. Create your OSGeo GSoC project wiki page and add the links to your wiki
page and public repository in the accepted students wiki page [2] (You can
refer [3] for reference). The wiki page would be required to be edited with
weekly reports without delay. Your project wiki page would act as mirror of
your work throughout the GSoC and community members would be able to access
it and provide feedback, interact about the work.

2. Write an introductory email to our SOC mailing list [4] and to your
community dev mailing list, detailing your project and asking for feedback.
Also, include information about your wiki page, public repository and any
other way the community can follow updates for your project, like a blog, a
Twitter account etc.

3. Now it's a good time to study again Google's GSoC students guide [5] and
OSGeo's specific instructions [6] [7], they contain useful advice from past
years.

Public interaction is important -- it is a key principle of open source --
work happens where everyone can see it.

In case of any doubts, remember that we all are one email away. Please feel
free to reach out to the Mentors, Admins and Community Members for any
queries and updates. Having mentioned that, you all might be working from
home or under constrained environment due to COVID-19 pandemic. If
required, please communicate your status to the Mentors asap, instead of
waiting till the last moment thinking that you will solve it on your own.

Wishing you all a very productive geospatial summer!

kind regards,
Your OSGeo GSoC Admins

[1] https://wiki.osgeo.org/
[2] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2020_Accepted
[3] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019_Accepted
[4] http://lists.osgeo.org/mailman/listinfo/soc
[5] https://google.github.io/gsocguides/student/
[6]
https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#What_to_expect_after_application
[7]
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#What_to_expect_during_the_summer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/soc/attachments/20200507/cba4110d/attachment.html>


More information about the SoC mailing list