This is not a new project, by any means, rather one of my long-running favorite projects – the Google Summer of Code. INCF has partcipated each year since 2011, and I have been the main org admin on ONCF’s behalf for all but the two first years.
I described GSoC in some detail in Swedish back in 2014 when I guest-blogged at Tidningen Curie (“En snart passerad sommar av kod”). Many of the things I named as positive then are still true today; it is in many ways a fantastically fun project to work with. The students are smart, motivated and enthusiastic over having the possibility to contribute to projects and tools that are needed and useful. The mentors get a lot of development done for the price of regular mentoring, and the projects get new contributors – many continue to involve their students one way or another after the paid period, and some of them come back as mentors for the same project they started on. One former student, from 2018, is even my co-org-admin! (Hi, Arnab!) As mentoring organization, we get the joyous task of helping our community members help each other; many of the participating software tool projects are developed an maintained on small or no funds by the researchers themselves. We know how many small gaps there are that need to be bridged to make community tools better, faster, and smarter. And all the developed and inproved resources are openly accessible for everyone to pick up and continue working on or extend.
January, now, is the run up period – we have a call out for project suggestions and mentors, and responses have just started trickling in. Usually the mentors/project owners come to us with specific, well-thought-out and well described ideas, and sitting at the other end reading them all is a great experience – it is a veritable fountain of scientific and technical creativity, and one of the high points of my year. Projects that are well scoped and described – nearly all the submissions – end up on our official Project Ideas List and form the most important part of our application (I think, nobody knows exactly what Google looks for). As soon as that list goes public, around the end of January/start of February, mentors start interacting with potential students, working out the students’ project proposals. But slowly. The real explosion in activity comes when Google announces the year’s accepted organizations, this year that announcement goes out on March 9 (usually pretty late in the day, since it is on US-compatible time). It is always a very nervous day.
This year, Google has reshaped the program a bit, shortening the time spent coding and lowering the (high) threshold for participation. Which means we will get more students who are not hard core coders (yet) and need some support – which we as mentoring organization will be partly responsible for providing – and also the mentors and their community – all student projects start with an official community bonding period (genius idea). I distinctly remember being new to coding as a student, and hope that experience will help me be helpful.