1. GNOME Accepted in GSoC, mentors needs to register and call to more ideas

Hello all, 

GNOME was again accepted for GSoC! \\o//

Thanks to the mentors who've already listed GSoC project ideas! We currently have only around 16 GSoC ideas, it would be excellent to have at least four more mentors with new ideas for this round, as we are used to be one of the biggest organisations and would be awesome to keep it this way :)
If you are interested please add your idea in the wiki [0]. If you are interested but don't have any ideas, please contact us at soc-admins@gnome.org or one of the admins [1] on IRC and we will help you find some.

For mentors whose ideas are triaged, it's time to register with us!
Please fill the form [2] and we will invite you to the GSoC program in Google's website.
Also, please subscribe to the mentors list [3] if you haven't done so yet. We will send required information for mentors in that list.

If you have any question, please don't hesitate to contact us at soc-admins@gnome.org or any of us on IRC [1].

[0] https://wiki.gnome.org/Outreach/SummerOfCode/2017/Ideas 
[1] https://wiki.gnome.org/Outreach/SummerOfCode/admins
[2] https://docs.google.com/forms/d/e/1FAIpQLSeCuIH2mY7D6aMvQs0jFymTc_7AwEC5lX54NYa24a6bI1pvOw/viewform?usp=sf_link
[3] https://mail.gnome.org/mailman/listinfo/soc-mentors-list

Have a nice day, 
GSOC admins

2. Students submitted their final proposals

Hello GSoC Mentors,

Students already have their final proposals in the Google's website and we cleaned up everything so you can search for the ones you are interested in.

In order to get the students you want in the accepted slots, go to https://summerofcode.withgoogle.com/ and search for the proposals you want to mentor. Then 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 soc-admins@gnome.org 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! In any case, do this before 14/04/2016

*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 and GNOME will get penalized if the evaluation is not filled on time.
- Spend around 10h per week with the student; reviewing code, helping him/her, chatting, etc.
- Weekly goals and review of the goals in weekly meetings.
- Review code submissions of the student thoroughly and in a timely manner.
- Communicate regularly with the student.
- The student is on planet.gnome.org before the end of the community bonding phase.

If you have any questions, please don't hesitate to send us an email to soc-admins@gnome.org (preferred) or contact one of us on IRC.

Have a nice day,
GSoC Admins

3. After students are accepted. To the mailman entry for mass subscribing

Dear GNOME 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
on GNOME!

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 communicate that to the GNOME
administrators (listed on
https://wiki.gnome.org/Outreach/SummerOfCode/2017/ ):
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:

http://mail.gnome.org/mailman/listinfo/gnome-soc-list

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.

https://wiki.gnome.org/Outreach/SummerOfCode/2017/Projects

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:

https://wiki.gnome.org/Outreach/SummerOfCode/2016/Projects

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.

https://wiki.gnome.org/RecentChanges

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.

http://planet.gnome.org

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:

http://wiki.gnome.org/PlanetGnome

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
about.

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 ('planet.gnome.org') for
your bug.

https://bugzilla.gnome.org/enter_bug.cgi?product=website&component=planet.gnome.org

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:

https://mail.gnome.org/mailman/listinfo/desktop-devel-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.
You should also subscribe to the mailing list relevant to your project.

You should join #gnome-hackers, #newcomers, and #soc IRC channels
on GIMPNet (irc.gnome.org), 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:

https://wiki.gnome.org/Community/GettingInTouch/IRC

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

All students are invited to attend GUADEC, taking place in
Manchester, United Kingdom from 28th July to 2nd August 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 29 or you have vacation
time between now and May 30, 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
mentor.

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: July 28th August 2nd at least
+ start early if you will be busy with school towards the end

Welcome and Congratulations!

Cheers,
GNOME GSoC Administrators

4. Final evaluations approaching

To: soc-mentors-list@gnome.org, soc-admins@gnome.org

Hello fellow mentors,

GSoC program is approaching its end. Please file your evaluations by Sunday 27-08-2017 17:00 UTC.

Thank you for being a mentor this summer! Please be sure to encourage your student to stay involved with specific recommendations for what they can work on and continue mentoring them in their involvement in GNOME!

Please let us know if you have any concerns about your student, and approach us at any time for any question at soc-admins@gnome.org.

GNOME GSoC Admins

To: gnome-soc-list@gnome.org, soc-admins@gnome.org

Hello fellow students,

Thank you for all your contributions to GNOME this summer!

If you have not done so already, please be sure to do the following this week:
1) Update your page at https://wiki.gnome.org/Outreach/SummerOfCode/2017/Projects , including links to your merged or work-in-progress contributions
2) Write a wrap-up blog post
3) Fill out the final evaluation from Google

If your code or other contributions have not been merged yet, please do your best to follow through the review process to merge what you worked on this summer as soon as possible.

We would love to see you continue contributing to GNOME. Please feel free to continue asking your mentor and other members of the GNOME community for guidance and advice in your participation in GNOME.

Your blogs will continue being aggregated on Planet GNOME for another half year. After that, you would need to be the GNOME Foundation member to keep your blog on Planet GNOME. If you contributed to GNOME before the GSoC application process and are not yet a member, you should consider applying for the membership soon. If you only started contributing to GNOME after February 2017, we ask that you continue contributing for another half a year before applying. http://www.gnome.org/foundation/membership/apply/

If you have any question, concern or feedback for us, write us any time to soc-admins@gnome.org.

GNOME GSoC Admins