[GRASS-dev] Fwd: [OSGeo-Discuss] OSGeo accepted to GSoC 2015 - overview of slot assignments

Markus Neteler neteler at osgeo.org
Tue Mar 3 01:59:05 PST 2015


FYI

---------- Forwarded message ----------
From: Margherita Di Leo <diregola at gmail.com>
Date: Tue, Mar 3, 2015 at 10:41 AM
Subject: [OSGeo-Discuss] OSGeo accepted to GSoC 2015 - overview of slot
assignments
To: OSGeo Discussions <discuss at lists.osgeo.org>, OSGeo-SoC <
soc at lists.osgeo.org>


Dear All,

it is our pleasure to announce that *OSGeo has been accepted as mentoring
organization* also this year! [1]
The OSGeo GSoC Team has been reshaped with respect to former
communications, and it's now composed by myself (Madi) in the role of
primary admin and the experienced Anne Ghisla in the role of co-admin.

Now it's time for prospecting students to carefully browse the list of
ideas and contact developers team of their interest. Mentor registration is
not yet open and will be announced in due time. Students can officially
apply on Melange from 16th to 27th of March.

All, do keep an eye (and a calendar client reminder) on all *GSoC 2015
dates* [2]!

This year, we will be using slightly different *procedure for assigning
slots* to selected projects. The experience from previous years made it
possible to define the criteria that will be applied this year, and
hopefully will be improved in the future:

1. Each project requires at least *two mentors*. The soundness of the
project, the selection of reliable mentors and student is responsibility of
its community. However, this year we strongly encourage the community to
assign to the wannabe-GSoC-student some small programming tasks or bug
fixes, in order to be sure that (s)he is familiar with the selected
software, the programming environment, version control system, mailing
list, etc and can code. Particular attention should be paid in the
selection of mentors that *won't disappear* in the course of the GSoC.

2. Each OSGeo software will have *one* slot assigned, provided that the
conditions at point 1 are met.

3. Like previous years, OSGeo will host some like-minded projects that
requested it, and will assign *1* slot to each guest, provided that the
conditions at point 1 are met.

4. This year we want to encourage projects that entail the* integration
between two or more OSGeo software*. For this reason, one extra slot will
be assigned to (sound) projects that aim at integrating two or more
software, provided that mentors of respective communities are involved.

5. If the number of slots will allow it, extra slots can be assigned to
projects that have gained a good *rate of success* in the course of past
years (reliable -not disappearing- mentors, student success, etc).

Further discussion on specific slot assignments will take place among
mentors in due time. This is the admins outline of this year's criteria.

Please send answers to this announcement* to soc [3] list*, and forward
this mail to all relevant mailing lists of your knowledge.

*And now, let s do this thing!*
*http://tinyurl.com/l32yzgp <http://tinyurl.com/l32yzgp>*

Yours enthusiastically,

Madi and Anne
OSGeo GSoC Admins 2015

[1]
http://google-opensource.blogspot.it/2015/03/mentoring-organizations-for-google.html
[2] https://www.google-melange.com/gsoc/events/google/gsoc2015
[3] http://lists.osgeo.org/mailman/listinfo/soc




-- 
Best regards,

Dr. Margherita DI LEO
Scientific / technical project officer

European Commission - DG JRC
Institute for Environment and Sustainability (IES)
Via Fermi, 2749
I-21027 Ispra (VA) - Italy - TP 261

Tel. +39 0332 78 3600
margherita.di-leo at jrc.ec.europa.eu

Disclaimer: The views expressed are purely those of the writer and may not
in any circumstance be regarded as stating an official position of the
European Commission.

_______________________________________________
Discuss mailing list
Discuss at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20150303/20aa301a/attachment-0001.html>


More information about the grass-dev mailing list