From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] GSoC 2012
Date: Wed, 14 Mar 2012 20:35:42 -0400 [thread overview]
Message-ID: <CAFgOgC9qZuvy3aJm2VAKA_9r6E8k+jJX2GvEBA5_59Sp-caduA@mail.gmail.com> (raw)
In-Reply-To: <6BB4497A-1B6D-4924-84B0-7386F6B83589@9srv.net>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
Sending from phone, please pardon errors.
There are projects that use gsoc for docs and the like. I would see nothing
wrong with someone contributing code to the installer -- especially someone
with less familiarity with p9 than most 9fans -- they will likely taake
longer than 1-2 weeks. Additionally it might be a good opportunity to get
someone interested who doesn't have C skills, which is something we have
been historically awful at in GSoC.
--dho
On Mar 14, 2012 6:58 PM, "Anthony Sorace" <a@9srv.net> wrote:
> On Mar 14, 2012, at 18:15 , Charles Forsyth wrote:
>
> > At least in the past, I'm sure I followed a discussion that the summer of
> > code was intended (ie, required) to produce code, not documentation
> > or packaging, although that might have changed.
>
> This is true. All projects in GSoC are required to be (at least
> principally)
> about producing code. No prohibition on including work on relevant
> documentation, of course, but code must be the focus.
>
> Which isn't to say that installation is out of scope. I could imagine a
> proposal looking at creating installation CDs from trees or installing
> under different circumstances being code-focused.
>
> Anthony
>
>
[-- Attachment #2: Type: text/html, Size: 1515 bytes --]
next prev parent reply other threads:[~2012-03-15 0:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 16:13 Anthony Sorace
2012-02-24 16:19 ` Calvin Morrison
2012-02-24 16:23 ` Devon H. O'Dell
2012-02-24 16:30 ` Calvin Morrison
2012-02-27 8:40 ` JIghtuse
2012-02-28 17:36 ` Anthony Sorace
2012-03-14 19:03 ` tlaronde
2012-03-14 19:38 ` John Floren
2012-03-14 22:15 ` Charles Forsyth
2012-03-14 22:57 ` Anthony Sorace
2012-03-15 0:35 ` Devon H. O'Dell [this message]
2012-03-15 22:01 ` Jeremy Jackins
[not found] ` <CAOr72mhZkyOd_0BmUMn3dYjF64dtvcO3yL7beAK8n+cwPr2oBg@mail.gmail.c>
2012-03-16 0:38 ` erik quanstrom
2012-03-16 1:55 ` Jeremy Jackins
2012-03-16 2:06 ` andrew zerger
2012-03-16 2:43 ` Stanley Lieber
[not found] ` <CAEDadry=HSYbzrScF+J7AT2qUxzNr7TNy=tL8fXyt3qdH035cA@mail.gmail.c>
2012-03-16 2:34 ` erik quanstrom
2012-02-24 16:23 ` Anthony Sorace
2012-03-15 22:27 Paschke Christoph
[not found] ` <CAB+41mHTO=anpHyxSrPrv-8tGW19_-cA9=21HEjQPcemXdCVOA@mail.gmail.com>
2012-03-16 6:58 ` Paschke Christoph
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=CAFgOgC9qZuvy3aJm2VAKA_9r6E8k+jJX2GvEBA5_59Sp-caduA@mail.gmail.com \
--to=devon.odell@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).