From: "Federico G. Benavento" <benavento@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] request for more GSoC project suggestions
Date: Wed, 25 Mar 2009 21:09:27 -0300 [thread overview]
Message-ID: <32d987d50903251709o5c7d4785m6d2702f2cecbcf3@mail.gmail.com> (raw)
In-Reply-To: <361d2c0d16ae44890a1a2515f261c800@terzarima.net>
hola,
I think we usually ask for drivers because that's what keeps some
of us away of using Plan 9 natively or in new hardware, but I
also get Charles point, soo..
I'd really like to see p9p for windows and/or 9vx for windows as well.
for the first, I heard somewhere that a german fellow even got acme
going, but I don't know where that work is, for the latter there is also
a port stalled.
As for applications for Plan 9, the ones we need (read to cope with
the rest of the world) are too big for a soc project, so even if I don't
like gcc, a port would help on this matter.
right now, one can get by running old linux binaries and linuxemu+
equis, so improving linuxemu is also a project I'm interested.
just my opinion
On Wed, Mar 25, 2009 at 12:16 PM, Charles Forsyth <forsyth@terzarima.net> wrote:
> There are GSoC project suggestions at http://gsoc.cat-v.org/ideas/
> but I think more are needed, and that it would be especially good
> to have a further set of useful but simpler and smaller projects.
>
> Projects need to be non-trivial for GSoC, but shouldn't
> be hard enough that many of us would shun them (or indeed, have shunned them).
> Based on my experience several years ago,
> I'd also look for projects that are modular, so that the set of deliverables can be extended
> or reduced depending how things go. That worked well for the
> projects I was involved with.
>
> The problem with ports of the system or device driver writing, in my experience,
> is that satisfying though they are, and as necessary
> as they might be, they are typically quite hard to
> supervise, and will usually be fairly difficult for relative novices.
> There is quite a bit to learn for most students just to
> get started and be productive in the programming environment,
> although 9vx does make that much easier.
> Application-level projects are typically easier to
> supervise because they don't need specialised equipment,
> and many more people on this list and elsewhere can help
> with plausible advice, and also help debug when students are stuck. (Advice will
> sometimes be contradictory, but that's not a bad lesson to learn, too.)
> It's quite hard to help when special hardware or kernel-level debugging is involved.
> Because quite a bit in Plan 9 (or Inferno/9vx/p9p etc) is done at
> user-level that is done at kernel-level in other systems, that shouldn't
> narrow the scope much. I wrote "application-level" not just "user-level"
> earlier because I thought it would be good to have some
> interesting applications of the system. Of course, I don't mean
> to preclude system-level things when students are especially keen
> on that (as indeed I was during my school and university years).
>
> I don't know where the best place to suggest or discuss them would be,
> but I thought this list would reach nearly everyone interested.
>
>
--
Federico G. Benavento
next prev parent reply other threads:[~2009-03-26 0:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 15:16 Charles Forsyth
2009-03-25 15:06 ` Devon H. O'Dell
2009-03-26 5:19 ` lucio
2009-03-26 13:18 ` Devon H. O'Dell
2009-03-26 15:03 ` lucio
2009-03-26 15:17 ` lucio
2009-03-25 19:57 ` Paul Lalonde
2009-03-25 20:12 ` Devon H. O'Dell
2009-03-25 20:19 ` erik quanstrom
2009-03-25 20:28 ` Devon H. O'Dell
2009-03-25 20:38 ` Chris Brannon
2009-03-26 0:47 ` erik quanstrom
2009-03-26 1:10 ` Chris Brannon
2009-03-26 2:02 ` Roman Shaposhnik
2009-03-25 20:39 ` Paul Lalonde
2009-03-25 21:12 ` Charles Forsyth
2009-03-26 1:11 ` Roman V. Shaposhnik
2009-03-26 1:51 ` Paul Lalonde
2009-03-26 2:01 ` Roman Shaposhnik
2009-03-26 2:01 ` Devon H. O'Dell
2009-03-25 20:40 ` James Tomaschke
2009-03-25 22:48 ` Paul Lalonde
2009-03-25 23:20 ` Devon H. O'Dell
2009-03-25 23:26 ` erik quanstrom
2009-03-26 2:03 ` Devon H. O'Dell
2009-03-26 4:43 ` erik quanstrom
2009-03-26 2:05 ` Roman Shaposhnik
2009-03-26 14:21 ` Joel C. Salomon
2009-03-26 15:09 ` Juan M. Mendez
2009-03-26 15:18 ` Devon H. O'Dell
2009-03-26 16:23 ` [9fans] LLVM & Exceptions (Was re. request for more GSoC project suggestions) Joel C. Salomon
2009-03-26 0:09 ` Federico G. Benavento [this message]
2009-03-26 1:54 ` [9fans] request for more GSoC project suggestions Devon H. O'Dell
2009-03-26 10:41 ` Charles Forsyth
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=32d987d50903251709o5c7d4785m6d2702f2cecbcf3@mail.gmail.com \
--to=benavento@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).