[SoC] GSoC 2022 – Congratulations to the Accepted Students! What's next: Community Bonding Period (May 20 - June 12, 2022)

Thu May 26 23:16:39 PDT 2022

Dear Students,

Heartiest congratulations to those who have been accepted for GSoC 2022!

*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 20 - June 12, 2022) 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, and 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:
https://googlesummerofcode.blogspot.com/2007/04/so-what-is-this-community-bonding-all.html

In short, after the Community Bonding Period you should be ready to start
achieving your coding objectives post June 12, 2022 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 **(May 20 -
June 12, 2022)?*

   - Request writing access to the OSGeo wiki [1], you need it to edit all
   info related to your project
   - Get to know your mentors, and establish with them a way of
   communication, that can be a video call, chat, email, etc. You are supposed
   to communicate regularly and often with your mentors.
   - Familiarize yourself 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 the 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 to your project.
   - Install the developer environment and get ready to start coding.
   - Participate in Mailing Lists / IRC / etc, try and help users.Important
   point related to your
   - Start coding for bug fixes NOT necessarily related to your project: it
   is a good exercise to become familiar with the codebase. Include these bug
   fixes into your report due at the end of the 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 this 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 enough to be included in the main repo. Discuss the
   details with your mentors.

What is required immediately from you?

   1.

   Create your OSGeo User Profile (you can refer [2] for reference) by
   going to the Request account option on the OSGeo wiki page [3].
   2.

   Create your OSGeo GSoC project wiki page and add the links to your wiki
   page and public repository in the Accepted Proposals wiki page [4] (you can
   refer [5] for reference). Also, link your OSGeo User Profile (created
   above) in the Accepted Proposals wiki page, as a hyperlink in the
   "Student" column. The wiki page would be required to be edited with
   weekly reports without delay. Your project wiki page would act as a mirror
   of your work throughout the GSoC and community members would be able to
   access it, provide feedback, and interact with the work.
   3.

   Write an introductory email to our SOC mailing list [6] 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.
   4.

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

*Changes to GSoC 2022 program, related to the coding period timeline*:

   - The GSoC 2022 program has allowed flexibility with the actual coding
   period - a project can be anywhere from 10 weeks to 22 weeks, with the
   standard being 12 weeks. *A GSoC contributor with the agreement of the
   mentor can reach out to the Org Admins to adjust the coding period duration
   at any point in the program, as long as the coding period is not longer
   than 22 weeks*. The standard 12 weeks coding period will be convenient
   for all of us in adhering to the deadlines, but we understand that you
   might want to take a planned break, or to adjust the schedule around
   exams, previous commitments, or to finish earlier. So, on request of the
   GSoC contributors, the lengths can be adjusted throughout the program as
   needed to reflect a 10, 14, 16, 18, 20, or 22-week project [10].

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. Depending on your location, you might be still working
from home or in a constrained environment, so, 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/User:Krashish8
[3] https://wiki.osgeo.org/wiki/Special:RequestAccount
[4] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2022_Accepted
[5] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2021_Accepted
[6] https://lists.osgeo.org/mailman/listinfo/soc
[7] https://google.github.io/gsocguides/student/
[8]
https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#What_to_expect_after_application
[9]
https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#What_to_expect_during_the_summer
[10] https://developers.google.com/open-source/gsoc/help/2022-project-dates
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/soc/attachments/20220527/032d3655/attachment.htm>