9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] GSoC 2012
Date: Fri, 24 Feb 2012 11:23:43 -0500	[thread overview]
Message-ID: <CAFgOgC8+AZbciFSGnXeWUGcy7HQMHFsqKf2fKWPWxuL1CjEy1Q@mail.gmail.com> (raw)
In-Reply-To: <CAJFUHyU-wROi8B6dr6B6A8jThFoRL3mdMZgAbOb57JKEtcRjYg@mail.gmail.com>

Op 24 februari 2012 11:19 heeft Calvin Morrison
<mutantturkey@gmail.com> het volgende geschreven:
>
>
> On 24 February 2012 11:13, Anthony Sorace <a@9srv.net> wrote:
>>
>> Folks:
>>        The fine folks over at Google's Open Source Programs
>> Office have announced the 2012 edition of Summer of
>> Code. I intend to submit an application for Plan 9 to again
>> participate. I'd like your help in making this year a success.
>>
>>        We had one major problem last year. Between Google's
>> decision to focus on bringing in a larger number of smaller
>> organizations and our own group's tendency to be pretty
>> hands-off on marketing, we got an abysmal showing in the
>> student application process. We got very few applications
>> (7, from memory), and only 3 of those (at best) were viable.
>> We were given two slots for student projects.
>>
>>        This is bad for a few reasons. Obviously it means we
>> don't get as many people exposed to our code and our
>> community, we don't get as much work done, and we don't
>> have the opportunity to create new contributors, which is
>> the fundamental point of GSoC. It also makes our numbers
>> pretty vulnerable when, as happened last year, one
>> student goes silent at midterms and never resurfaces.
>>
>>        This year, I'd like to make an explicit call for help from
>> our community in getting the word out. I know we have
>> several members who're attached to higher education
>> institutions; that's really the best route here. It's likely that
>> your school provides several ways of getting this program
>> in front of students; It'd be wonderful if you could look into
>> those. I've spoken to a few of you individually, but I'm sure
>> there are several more I'm not aware of.
>>
>>        If you'd like help in terms of written text, presentation
>> outlines, whatever, just let me know. There's a good
>> collection of such things that folks have done for GSoC in
>> the past, and I'm happy to point you at relevant ones of
>> those or help you create more specific things. Just let me
>> know what you need. A good place to start is the FAQ[0].
>>
>>        In the mean time, I'll be going through the wiki and
>> giving it a good scrubbing, moving the 2011 pages out of
>> the way and preparing for 2012. I'd encourage anyone
>> who's got some free time to take a look at that, as well.
>> And, of course, we'll need projects! Think about what
>> would make a good summer-sized project for a student.
>> And if you're at all interested in Plan 9's participation in
>> GSoC, I'd suggest joining the Google group for the
>> topic[1], where most of the discussion in the summer
>> goes on.
>>
>>        Aside from that one major issue, last year went well. I
>> was able to get good feedback from a few people during
>> the application process, mentors signed up without
>> hassle, reviews of student applications were done well
>> and promptly. I'd like to thank everyone who's participated
>> so far, and I hope you'll sign up again once that's open.
>>
>> Anthony
>>
>> [0]
>> http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/faqs
>> [1]     http://groups.google.com/group/plan9-gsoc
>
>
> How can I apply for GSoC as a student? is it to late?

This year's program has not yet started; application submissions will
begin soon for organizations. After that, it will be a bit before
student applications begin being accepted. So it's definitely not too
late. Just check out the timeline at
http://www.google-melange.com/gsoc/events/google/gsoc2012. Hopefully
we are accepted again this year, and you can apply.

--dho

> Calvin Morrison



  reply	other threads:[~2012-02-24 16:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 16:13 Anthony Sorace
2012-02-24 16:19 ` Calvin Morrison
2012-02-24 16:23   ` Devon H. O'Dell [this message]
2012-02-24 16:30     ` Calvin Morrison
2012-02-27  8:40       ` JIghtuse
2012-02-28 17:36         ` Anthony Sorace
2012-03-14 19:03           ` tlaronde
2012-03-14 19:38             ` John Floren
2012-03-14 22:15               ` Charles Forsyth
2012-03-14 22:57                 ` Anthony Sorace
2012-03-15  0:35                   ` Devon H. O'Dell
2012-03-15 22:01                   ` Jeremy Jackins
     [not found]                   ` <CAOr72mhZkyOd_0BmUMn3dYjF64dtvcO3yL7beAK8n+cwPr2oBg@mail.gmail.c>
2012-03-16  0:38                     ` erik quanstrom
2012-03-16  1:55                       ` Jeremy Jackins
2012-03-16  2:06                         ` andrew zerger
2012-03-16  2:43                           ` Stanley Lieber
     [not found]                   ` <CAEDadry=HSYbzrScF+J7AT2qUxzNr7TNy=tL8fXyt3qdH035cA@mail.gmail.c>
2012-03-16  2:34                     ` erik quanstrom
2012-02-24 16:23   ` Anthony Sorace
2012-03-15 22:27 Paschke Christoph
     [not found] ` <CAB+41mHTO=anpHyxSrPrv-8tGW19_-cA9=21HEjQPcemXdCVOA@mail.gmail.com>
2012-03-16  6:58   ` Paschke Christoph

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFgOgC8+AZbciFSGnXeWUGcy7HQMHFsqKf2fKWPWxuL1CjEy1Q@mail.gmail.com \
    --to=devon.odell@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).