From: Bryce Harrington <bryce@osdl.org>
To: nfsv4@linux-nfs.org
Cc: nfs@lists.sourceforge.net
Subject: Re: Google Summer of Code and NFSv4
Date: Fri, 5 May 2006 11:25:49 -0700 [thread overview]
Message-ID: <20060505182549.GA20459@osdl.org> (raw)
In-Reply-To: <20060427214838.GR24981@osdl.org>
Just as a reminder, student applications are due May 8th (Monday). I've
updated the descriptions of the NFSv4 projects here:
http://developer.osdl.org/dev/soc/
We've had several good proposals submitted, although none yet for the
NFSv4 ones, so if you know a student that would be interested in
getting paid to learn NFSv4 this summer, and develop some tests, please
encourage them to sign up with Google and post an application!
Bryce
On Thu, Apr 27, 2006 at 02:48:38PM -0700, Bryce Harrington wrote:
> Hi all,
>
> Google runs a "Summer of Code" project to employ college students to
> work on open source projects for the summer. OSDL has signed up as a
> mentoring organization this year for a few different things, including
> Linux NFSv4.
>
> If you are a student and interested in working on NFSv4 for the summer,
> you can find more information at http://developer.osdl.org/dev/soc/ and
> http://code.google.com/summerofcode.html . Proposals can be sent in
> between May 1st and May 8th.
>
> I've volunteered to be a mentor for any testing projects around NFSv4;
> there's a couple ideas I listed on the above link, but if you have
> a better idea for a testing project, please feel free to propose that.
> In either case, please feel free to contact me off-list to work out
> details.
>
> Bryce
>
> P.S., if anyone else would also like to be a mentor through OSDL, we
> might be able to arrange this; contact me offlist.
next parent reply other threads:[~2006-05-05 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060427214838.GR24981@osdl.org>
2006-05-05 18:25 ` Bryce Harrington [this message]
2006-06-16 18:21 ` Google Summer of Code and NFSv4 Bryce Harrington
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=20060505182549.GA20459@osdl.org \
--to=bryce@osdl.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.