9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Caleb Malchik <cmalchik@gmail.com>
To: 9fans@9fans.net
Subject: [9fans]  inquiry about project sponsorship outside GSoC
Date: Wed, 17 Sep 2014 17:33:36 -0400	[thread overview]
Message-ID: <20140917173336.6f4ae762af1f0e7be4109d4c@gmail.com> (raw)

Greetings 9fans,

I am a senior studying computer science at Tufts University. I'm
interested in Plan 9 and frequently read this list. As seniors at Tufts
we are required to do a year long capstone project; it's fairly open
ended but must be motivated by some external sponsor. If sponsoring a
group of 3 university students to do a year-long project around Plan 9
sounds cool, read on!

What project we choose to do (Plan 9 or otherwise) is still up in the
air, and depends on our sponsor. In the Plan 9 vein, the GSoC wiki page
has a nice selection of projects that are of comparable size:

http://www.plan9.bell-labs.com/wiki/plan9/gsoc-2014-ideas/index.html

Some projects from that page that seem particularly intersting and
in-scope:

* alternative window system
* create additional modules for pq
* Kernel lock analyzer for amd64 kernel
* Kernel lock timing analyzer for amd64 kernel
* a per-processor scheduler
* Implement TLS 1.2 in libsec
* Add support for OAuth2 Login authentication to factotum
* 9p on Arduino Yun
* Teach Plan 9 to speak mDNS

We're also very open to other project ideas.

Your role as a sponsor would look something like this: fall semester
(between now and mid-December) you would help define requirements and a
deliverables timeline, and approve design documents. In the spring you
would monitor progress and optionally provide support to the
implementation. There are resources for in-house support at Tufts, but
nobody here knows Plan 9 well enough to provide Plan 9-specific
support, or clarify requirements such that the project will be useful
to the community. If you are worried about the time commitment, a
couple emails per month would be sufficient once we get the ball
rolling (more frequent communication could be necessary at first to get
us to a place where we can write and test code).

If this seems at all interesting, feel free to contace me off-list.

Best,
Caleb Malchik



             reply	other threads:[~2014-09-17 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17 21:33 Caleb Malchik [this message]
2014-09-17 23:22 ` Aleksandar Kuktin

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=20140917173336.6f4ae762af1f0e7be4109d4c@gmail.com \
    --to=cmalchik@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).