9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] GSoC '14
Date: Sun, 26 Jan 2014 09:43:33 -0500	[thread overview]
Message-ID: <674c3805c6d41fb1a937ebd031745f19@mikro.quanstro.net> (raw)
In-Reply-To: <CAL6pNZ89vS3GUfs5SDAXcWVNvZXu8cohew_prew=XyKw0ytRsQ@mail.gmail.com>

> ·        A device driver for Plan 9 for an unsupported device
> 
> ·        A GUI builder for the Plan 9 control graphics library
> 
> ·        Porting of the Tcl tool-kit Tk and the Tk GUI builder Xf
> 
> ·        VRML support for the Httpd
> 
> ·        Writing of an editor similar to Vi for Plan 9
> 
> ·        An Html front end to the PQ database system. This would involve
> adding PQ support to the Httpd
> 
> ·        Java support for Plan 9
> 
> ·        A lockable screen saver for Plan 9
> 
> ·        Mpeg support for Plan 9
> 
> ·        Addition of load balancing support into Plan 9

without addressing these particular ideas, these are the things that i've found
helpful as a mentor spotting projects likely to be finished in a summer.  

1.  the project should be of personal interest to the student.  it helps guide
decisions, it helps motivation, etc.  build something for yourself that happens
to be of interest to the community.

2.  the project needs to be fully scoped out.  some projects are conceptually
straightforward, but require mountains of code to implement.  some projects
are conceptually interesting and take less code.  projects that require lots of
code often run into trouble.

3.  planning that allow time for a false start.

4.  a stepwise plan.

- erik



  parent reply	other threads:[~2014-01-26 14:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-25 10:03 Jessica Yu
2014-01-25 15:42 ` Steven Stallion
2014-01-25 22:59   ` Conor Williams
2014-01-26  0:09     ` Anthony Sorace
2014-01-26  1:42       ` Conor Williams
2014-01-26  2:14         ` Steven Stallion
2014-01-26  2:37           ` Conor Williams
2014-01-26  3:37             ` Shane Morris
2014-01-26  4:00               ` Calvin Morrison
2014-01-26  4:04                 ` Shane Morris
2014-01-26  4:15                   ` erik quanstrom
2014-01-26  4:18                     ` Shane Morris
2014-01-26  4:33             ` Steven Stallion
2014-01-26  4:37               ` Shane Morris
2014-01-26  6:25                 ` Steven Stallion
2014-01-26  4:38               ` Salman Javaid
2014-01-26  6:22                 ` Steven Stallion
2014-01-26  6:24                   ` Shane Morris
2014-01-26  6:28                     ` Steven Stallion
2014-01-26  6:30                       ` Shane Morris
2014-01-26 14:43             ` erik quanstrom [this message]
2014-01-26 16:15               ` Tristan
2014-01-26 19:17                 ` Muhammad Junaid Muzammil
2014-01-30 12:16             ` Steve Simon
2014-04-25 11:54               ` Conor Williams
2014-01-26  7:58   ` Jessica Yu
2014-01-26 22:02     ` Steven Stallion
2014-01-27  4:35     ` blstuart
2014-01-27 15:17       ` Jeff Sickel
2014-01-27 16:24         ` Steven Stallion
2014-01-27 17:31           ` Jeff Sickel

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=674c3805c6d41fb1a937ebd031745f19@mikro.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).