9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] GSOC 2008
Date: Wed, 27 Feb 2008 08:39:02 -0600	[thread overview]
Message-ID: <a4e6962a0802270639g50313fc3k80e7935be27b97e1@mail.gmail.com> (raw)

(reposting as my initial post bounced because it had too many recipients)
(Cross-posted into inferno-list, v9fs-developer, plan9-gsoc, and
plan9-gsoc-mentors)

Okay, from the deafening silence outside of students and project
nominations, it sound like we better get cracking.  At the very least
folks should start thinking up project ideas and people should decide
whether or not they will be available to mentor.  For folks unaware of
GSoC (aka Google Summer of Code), here's the link:
http://code.google.com/soc and also a link to last year's Plan 9 GSoC:
http://gsoc.cat-v.org/

I started a toplevel wiki page:
http://plan9.bell-labs.com/wiki/plan9/GSoC2008/index.html for people
to post interest and ideas -- although I think it would be a good idea
to post project ideas in the gsoc mailing list (one message per idea)
to make discussion easier -- vetted ideas can then be transfered to
the wiki.

Its probably also appropriate to start discussing guidelines for
project ideas and rules of engagement for how we are going to manage
project selection, mentor assignment, and student selections this year
as well as discuss volunteers and nominations for project
administrators.

All of this should probably happen in the plan9-gsoc mailing list
(http://groups.google.com/group/plan9-gsoc) to allow folks to opt-in
to the noise, so this will be my last cross-post.  I'm cc:'ing the
inferno list and v9fs-developer list as those projects participated in
the Plan 9 GSoC last year (and will likely do so again this year).

         -eric


             reply	other threads:[~2008-02-27 14:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 14:39 Eric Van Hensbergen [this message]
2008-02-27 19:28 ` hiro
2008-02-27 19:40   ` ron minnich
2008-02-27 20:30     ` don bailey
2008-02-27 20:17       ` [9fans] GSOC 2008 project maht
2008-02-27 21:43       ` [9fans] GSOC 2008 hiro
2008-02-27 21:59         ` ron minnich
2008-02-27 22:07           ` andrey mirtchovski
2008-02-27 22:09           ` Sape Mullender
2008-02-27 22:10             ` Eric Van Hensbergen
2008-02-27 22:24               ` ron minnich
2008-02-27 22:34                 ` Eric Van Hensbergen
2008-02-27 22:36                   ` erik quanstrom
2008-02-27 23:03                     ` ron minnich
2008-02-28 11:47                   ` Gorka Guardiola
2008-02-27 21:58       ` ron minnich
2008-02-27 22:09         ` john
  -- strict thread matches above, loose matches on Subject: below --
2008-02-26 14:18 [9fans] GSoC 2008 Eric Van Hensbergen
2008-02-26 14:25 ` Iruata Souza
2008-02-27 13:18 ` Sergey Zhilkin

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=a4e6962a0802270639g50313fc3k80e7935be27b97e1@mail.gmail.com \
    --to=ericvh@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).