Archive for 2015 emails

This page is WIP. If everything's going right I (LasseSchuirmann) am reworking the email templates from last year until october or so.

Sent Emails


Early Call For Ideas

When: Directly after the announcement of the GSoC 2016
Why: It is better to give the mentors a bigger timeframe to come up and collect their ideas. Ideas just happen and one can expect to get better/more ideas when collecting them over a wider timeframe.
Subject: GSoC 2016 Call For Ideas
To: desktop-devel-list, soc-mentors-list
CC: soc-admins

Dear GNOME hackers,

Google has just announced the Google Summer of Code 2016. TODO

Late Call For Ideas

After requesting slots

When: After requesting slots
Why: Make sure mentors have marked the right proposals as wanted to mentor and that they score the student.
Subject: To GSoC mentors: Steps to follow to get the proposals in the accepted slots
To: desktop-devel-list, soc-mentors-list
CC: soc-admins

Dear GSoC Mentors,

We have requested slots for GNOME and in a few days we will be able to finally accept or decline proposals.

In order to get the students you want in the accepted slots, you need to do the following:
- Make sure you have marked all proposals you'd like to accept as "want to mentor". If you have two proposals for the same project, you need to decide which one to take.
- Include a score (explanation of score below*) and any comments about your experience mentoring the applicant and how strongly you feel that they should be accepted for the program. Do this in the comments section of the proposal on the Google's website.
- In case you selected to mentor more than one student, send us an email at confirming it. Please make sure you will have enough time for two students. It's expected to spend around 10 hours per week per student. Google started to strongly recommend to just accept a single student per mentor, so we need to be careful when accepting these exceptions.

It is important to do these steps soon - the sooner this is done, the more likely you get the students you want!

*Score scale, half point rankings (i.e. 4.5, 3.5) are ok:
5 = amazing applicant, could become a module maintainer on completing the program, made extensive contributions to GNOME of high quality
4 = strong applicant, will certainly do a good job, made substantial contributions to GNOME of high quality (> ~50 lines of code or equivalent)
3 = good applicant, but is somewhat inexperienced
2 = is unlikely to do a good job
1 = not a good candidate

Also remember that when mentoring in GSoC, we expect:
- Fill evaluations at least 3 days before the official Google deadline. We need some time to tie up loose ends. Your student will fail if the evaluation is not filled on time.
- Spend around 10h per week with the student; reviewing code, helping him/her, chatting, etc.
- Review code submissions of the student thoroughly and in a timely manner.
- Communicate regularly with the student. Weekly meetings are recommended on top of regular communication.
- The student is on before the end of the community bonding phase.

If you have any questions, please don't hesitate to send us an email to or contact one of us on IRC.

Best regards,
GSoC Admins

Welcoming accepted students

Dear GNOME-loving student,

Congratulations: you did it! The GNOME community is glad to welcome
you, and to have you participate in Google Summer of Code and work

Some of you already know the GNOME community quite well, but it might
not be the case for every one of you. That's not a problem: GSoC has a
community bonding time, where you will have a few weeks to get to know
the community before starting the real work. That's a really good
thing, and we hope you'll be able to see how great, friendly and
helpful the GNOME community is!

The first thing we want you to do is to contact your mentor. Write her
or him a nice mail or buy her/him a beer (or some juice) if you happen
to live in the same city :-).

If during the GSoC, you have a problem with your mentor (lack of
communication, or misunderstandings, or deep disagreements, or
anything else), don't hesitate to report that to the GNOME
administrators (listed on ):
they'll be there to help with this kind of things and their goal is
to make sure that you feel good, so they will work hard to fix any
issue with your mentor. But hopefully, this won't be needed: all
mentors and administrators are nice people (or at least, they're
supposed to be ;-)).

We have subscribed you to our mailing list for the Summer of Code:

This is the list where mails will be sent when we need to reach all of
you. Feel free to use this list for discussion between all mentored
students, or to ask questions about GNOME, or about the community or
about anything you need.

To begin things, it would be great if you send to this list an
introduction mail so that the whole community knows about you, your
project, your plans, etc.

You can then use your introduction mail to fill the wiki page for your
GSoC project. First, add a link to it from a page that lists all
projects, then create a wiki page for your individual project.

This is a good place to introduce your project, link to the blog posts
you'll write, link to your code, etc. See the wiki pages from
last year if you need some examples:

Feel free to edit other pages of the GNOME wiki too. This is where we
post the information relevant to the GNOME projects. From time to time,
you might like to look through the recent changes page to see what's
going on in GNOME.

Planet GNOME is an aggregator of blogs of GNOME contributors. From now
on, it will serve as your morning newspaper :-). We ask that you add
your blog to Planet GNOME, creating a new blog if necessary, and write
updates about your work during the internship period every two weeks.
Of course, you are welcome to blog more often too! It is exciting that
you will have a voice on Planet GNOME right from the start and it is a
very important way to let the GNOME community know about the work you
are doing! This will also allow us to keep track of your progress.
Once your blog is added, please write an introductory post and start
blogging about your work on GNOME and other things that you see
relevant for Planet GNOME.

Here is what you need to do to get yourself added to Planet GNOME.
You need to have a link to your blog or to a category of posts in your
blog AND a hackergotchi ready for that. This page has all the details:

In particular, see "Do I have to only blog about GNOME things?"
section which explains that it's great to have posts about other
things that interest you aggregated on Planet GNOME, as long as they
can be of interest to other people in the community. So you should
decide whether you want to add your full blog or just a category
based on how frequently you blog and the range of topics you blog

Once you have the hackergotchi and the blog feed ready, file a bug
with them. Include your IRC nick as well. Be sure to use the right
Bugzilla product ('website') and component ('') for
your bug.

Mention that you are a GSoC student in the bug. That will get your
blog added fast even if it is completely new and will waive the
requirement of being the GNOME Foundation member. You will get a
special GSoC logo next to your posts on Planet GNOME.

Other mailing lists that might be of interest to you are the
desktop-devel-list and the gnome-love list:

You can participate in the general discussion on the
desktop-devel-list, and ask questions if you have problems with
building GNOME, or if you're not sure how to do something on
gnome-love list. You should also subscribe to the mailing
list relevant to your project.

You should join #gnome-hackers, #gnome-love, and #soc IRC channels
on GIMPNet (, as well as the channels relevant to
your project and other channels that might be of interest to you.
It's fine to just lurk on IRC. IRC is where people talk in GNOME,
and it is a great way to learn and discuss things. See this page
for more information:

If you prefer to use an address different from your gmail (or
google account) address to communicate, please tell the

All students are invited to attend GUADEC, taking place in
Karlsruhe, Germany on August 12-14 as core conference days. In
addition to attending a conference and meeting GNOME hackers
from around the world, you will have an opportunity to present
your work during interns' lightning talks and possibly spend a
few additional days working with your mentor and project team.
Please talk to your mentor about setting up a hackfest, a BoF
(Birds of a Feather discussion), or a time to co-work on your
project in the days adjacent to the core conference days. If
needed, students can receive partial financial assistance for
attending GUADEC. We will let you know when GNOME's travel
committee is ready to receive applications for financial
assistance for GUADEC travel.

If your school starts before August 30, and you have vacation
time between now and May 23, we would like to encourage you to
start on your projects early.

That's all for now. If you have any questions, feel free to send
a mail to the administrators or the mailing lists, or ask your

Small summary:
 + make sure you're in contact with your mentor(s)
 + create the wiki page for your project
 + get your blog added to Planet GNOME
 + subscribe to relevant mailing lists
 + hang out on IRC
 + introduce yourself on gnome-soc-list and on Planet GNOME
 + save the date: August 12-14 at least
 + start early if you will be busy with school towards the end

Welcome and Congratulations!

GNOME GSoC Administrators

Midterm evaluations approaching

Subject: GSoC Midterm Evaluations due by June 24th

Dear mentors,

GSoC midterm evaluations are due soon. Please fill them out by end-of-day (UTC) on June 24th, so that we don't need to be tracking down you and/or your student. You can start filling them since 20th of June.
This year evaluations can not be edited, so please revise the evaluation before.

Please let us know:

- if you have any concerns about your student.
- if you need any assistance filling the evaluations.

You can reach us through


The GNOME GSoC Admin Team

Outreach/SummerOfCode/2016/Mails (last edited 2016-06-13 09:51:48 by CarlosSoriano)