On Fri, Oct 21, 2011 at 11:18:02AM +0200, Stefano Zacchiroli wrote:
> TL;DR: I'm looking for volunteers that will act as Debian Project
> liaisons (or "admins") for the Google Code In initiative [1]. Deadline
> for project applications is November 1st; we'll miss it unless we have
> the volunteers before that date. Feel free to volunteer either on
> -project or by mailing me at [email protected].

We've got four volunteers for the task (all Cc:-ed):

- Gergely Nagy
- Sukhbir Singh
- Bastian Blank
- Laszlo Boszorme

I'm just doing the introductions here, as I don't have much of
experience myself with GCI. I suggest using this list for coordination
of Debian participation in GCI, as we did in the past.

It'd be great if you people could get in touch with Debian's admin of
GCI past year, to learn from past experience. IIRC, the admins back then
were Ana and Arthur (both Cc:-ed), while Sylvestre kicked-in later on
for GSOC.

As a complete outsider, I think we should ensure that we get a Debian
press release / news item out of this to call for student applications
when the student application period will start.

Also, as I mentioned in the call for volunteers, I think Debian needs a
general list of "easy hacks" to advertise permanently, even outside GCI:
it is a great way to attract new people in a Free Software project. It'd
be great if, as a side-effect of GCI participation this year, we will
manage to establish social and technical mechanisms to maintain and
advertise such a list.

Good luck!
Cheers.
-- 
Stefano Zacchiroli     zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences   ......   http://upsilon.cc/zack   ......   . . o
Debian Project Leader    .......   @zack on identi.ca   .......    o o o
« the first rule of tautology club is the first rule of tautology club »

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Soc-coordination mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/soc-coordination

Reply via email to