Google Summer of Code 2020: A Mentor's Perspective
Tags: googlesummerofcode, opensource, mentorship
Published: 2020-09-25 08:14:53

![Google Summer of Code logo](https://dev-to-uploads.s3.amazonaws.com/i/cbgrxop2j5xsycfczd6x.png)

<a href="https://summerofcode.withgoogle.com/">Google Summer of Code</a> (GSoC) is a summer initiative that allows students to obtain a first deep dive into Open Source projects.

It has several benefits:
<ul>
 	<li>GSoC creates bonds between students and Open Source communities. Some, but not all, students continue to contribute to the Open Source project they worked on after GSoC</li>
 	<li>This initiative is a two-way street. Working on an Open Source project goes way beyond writing code (or tests, or documentation, etc.). It’s being part of a group, which can support the individual on the task at hand, but also provide a supporting and nurturing environment.</li>
 	<li>Last but not least, it gives students hands-on experience working in companies beyond academics. In some places, getting one’s first job is hard, as companies want to hire developers with experience. GSoC is a good opportunity to get this first experience.</li>
</ul>
For the first time in 2020, Hazelcast submitted to be a hosting organization for GSoC… and we were ecstatic when we received our notification of acceptance. As it was our first year, we only received 2 slots but the experience was so beneficial to both us and (I hope!) the interns that we intend to renew it next year.

The gist of GSoC is to pair a student with a mentor and let the magic happen. This year, <a href="https://twitter.com/mtopolnik">Marko Topolnik</a> and <a href="https://twitter.com/erosb88">Bence <span class="css-901oao css-16my406 r-1qd0xha r-ad9z0x r-bcqeeo r-qvutc0">Erős</span></a> were our mentors. In this post, we asked them a few questions about their experience.

<strong>Hello, Marko and Bence. Could you first introduce yourself?</strong>
<ul>
 	<li><em>Marko</em>: I've been with Hazelcast since 2015, doing Hot Restart persistence as my first task. Today, I'm the tech lead of the Hazelcast Jet team. I also like hanging out on Stack Overflow, mostly on the Kotlin Coroutines tag. It's a language feature the Jet team would really like to see in Java!</li>
 	<li><em>Bence</em>: I joined Hazelcast in 2019 October and I’m a member of the Management Center team as a senior developer. Previously, I worked in various industries (logistics-related R&amp;D, language processing, healthcare IT). My most significant open source contribution was a JSON schema validator, implemented in java.</li>
</ul>
<strong>What motivated you to be a mentor in Google Summer of Code? Did you already have any teaching experience? What were your expectations?</strong>
<ul>
 	<li><em>M</em>: I used to work at the Zagreb University teaching Java. I enjoy working with motivated students, helping them learn not just programming, but also the ropes of being a software professional.</li>
 	<li><em>B</em>: I used to be an associate lecturer at the University of Debrecen (Hungary), and later I mentored a couple of interns at my workplace. I always enjoyed it a lot and considered it as a valuable activity, so when the opportunity came across in Hazelcast to be a GSoC mentor, I thought why not.</li>
</ul>
<strong>Could you tell me a little about how you approached your mentoring? What was your relationship with the student? How did you work day-to-day?</strong>
<ul>
 	<li><em>M</em>: I used my experience from the university, where I noticed that mentors generally tend toward too much ceremony, dragging the student's attention away from the essence of the work. I emphasize close interaction and iterating over the design ideas quickly, in the informal setting of a chat. Purely verbal communication has many drawbacks and there's plenty of opportunity for misunderstanding. You have to practice it with each individual to get better and more efficient at communicating the ideas in both directions.</li>
 	<li><em>B</em>: we started working on the project during the community bonding period because there were a couple of refactoring tasks to be done before getting to the actual feature implementation and this imposed some risk on the completion of the project on schedule. We stayed in close connection with the student all over the summer, we talked on gitter 3-5 days per week, and also I gave him detailed feedback in PR reviews (fortunately that was doable since the whole project got broken up into a dozen of small-ish PRs). Luckily, the student accomplished everything he listed in his proposal by the end of July (a month before the final deadline) so we could also implement some stretch goals. Overall, we were in a friendly working relationship and the student will probably continue as a member of the Hazelcast contributor community in the future, so we will keep working together.</li>
</ul>
<strong>What’s the takeaway from this experience? Would you do it again? What would you do differently?</strong>
<ul>
 	<li><em>M</em>: I highly enjoyed my interaction this year, it was smooth at the beginning and got even better over time. The student did an excellent job and was also very happy with the way things worked out in the project.</li>
 	<li><em>B</em>: I would definitely love participating in GSoC as a mentor again next year. Maybe I would try to get my mentee a bit more engaged in the community, and try to answer user questions on the various community channels we have (StackOverflow, Slack, Google Groups).</li>
</ul>
<strong>Would you have any advice for students who want to take part in GSoC 2021?</strong>
<ul>
 	<li><em>M</em>: To be honest, I don't know what advice I could give to the participants at large, but I'm happy to share some advice with students who consider applying to my projects: make sure you bring a lot of enthusiasm and the desire to do some honest, serious work. Don't expect a typical professor-student relationship, I'll want you to become my colleague for the summer. Keep asking questions, keep the ideas coming, and you can achieve something you'll be proud of.</li>
 	<li><em>B</em>: My single advice would be: don't rush. It is much more valuable from a mentor’s perspective to provide good work at moderate speed than submitting mediocre quality code in haste.</li>
</ul>
<strong>Any parting words?</strong>
<ul>
 	<li><em>M</em>: If you're interested in the inner workings of distributed systems, especially stream processing, if you feel you're ready for a serious challenge, I'll be happy to take that journey with you and let you experience what it's like to be a part of the Hazelcast Jet Core Team!</li>
 	<li><em>B</em>: GSoC is a great opportunity for students because not every university can offer such great options to participate in significantly large-scale and quality software projects, so I encourage everyone to apply and give it a go.</li>
</ul>
Thanks a lot Marko &amp; Bence!

At [Hazelcast](https://hazelcast.org), we know first hand Open Source is not only about people contributing to our codebase. It’s a whole process that benefits everybody involved.

If you don’t want to wait until GSoC 2021, we intend to be part of <a href="https://hacktoberfest.digitalocean.com/">Hacktober</a>. If you want to start (or continue!) your journey into Open Source, Marko, Bence and our whole engineering team would be happy to help you along the way.

In all cases, come in and say hi, it’s just a <a href="https://slack.hazelcast.com/">Slack</a> away.