From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 9fans content
Date: Fri, 10 Aug 2007 15:16:05 -0700 [thread overview]
Message-ID: <70A20023-DFBF-4F10-B13A-81B2E05C6727@telus.net> (raw)
In-Reply-To: <5d375e920708101228u4b86f15dv715bf50f57ee6e82@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm one of the "guilty" parties regarding plan9-tech. GSOC requires
public communications, but I'm entirely unhappy passing "did you
check bit 11 of the VPN register" level of crap to 9fans - it's
clearly not where it belongs (I believe it belongs in private email,
but that's another matter). Plan9-tech was a (possibly ill-named)
place to drop those messages.
Frankly, my post-mortem on gsoc won't be very nice. I should never
have accepted to work with a student 9 timezones away, even if the
project is really interesting. And I certainly could have poured
arbitrary amounts of time into it, but I'm really unsure where the
line is between the student's project and my own (essentially
recreational) coding.
Paul
On 10-Aug-07, at 12:28 PM, Uriel wrote:
> The plan9-tech list was created (not by me) after various gsoc
> students *and* mentors plain refused to use 9fans, and really, who can
> blame them when even jmk refuses to use 9fans anymore.
>
> Anyway, keep jumping to assumptions, bashing people who tries to help,
> and doing what you have doing so far, it seems to have worked really
> well.
>
> uriel
>
> P.S.: Oh, I know, you would rather have everyone use private email,
> that has worked so wonderfully so far.
>
> On 8/10/07, ron minnich <rminnich@gmail.com> wrote:
>> On 8/10/07, Steve Simon <steve@quintile.net> wrote:
>>
>>> good one uriel, good one.
>>
>> so, set me straight on this: somone is leading the tribe of True
>> 3lite
>> Hackers across the desert, gonna part the waters etc., take 'em to
>> the
>> promised land, and so on.
>>
>> So, uh, who are these tech contributors who are going? I can only
>> gaze
>> in awe. And, once they get there, I assume they'll take a blanket off
>> the blanket tree and take a nap (ref. to CM Kornbluth is entirely
>> intentional; I'll let you find story and title).
>>
>> ron
>> p.s. met the coraid guys at linux world yesterday. Very, very fine
>> stuff. I love the fact that they are 'the linux storage company'.
>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGvOOlpJeHo/Fbu1wRAhwVAKCHRJquefKgAFfSnZugJgWuLWbRzgCffgBy
y4b5mvW20Q7QpgdsoQqfIN4=
=mYF7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-08-10 22:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 19:52 [9fans] [9fans-bounces@cse.psu.edu: Auto-discard notification] Scott Schwartz
2007-08-10 9:34 ` Uriel
2007-08-10 11:08 ` [9fans] 9fans content Charles Forsyth
2007-08-10 11:28 ` Steve Simon
2007-08-10 16:22 ` ron minnich
2007-08-10 16:27 ` erik quanstrom
2007-08-10 17:13 ` David Leimbach
2007-08-10 17:24 ` David Leimbach
2007-08-10 18:09 ` ron minnich
2007-08-10 18:11 ` erik quanstrom
2007-08-10 18:36 ` Paweł Lasek
2007-08-11 9:17 ` matt
2007-08-10 22:43 ` Roman Shaposhnick
2007-08-10 19:28 ` Uriel
2007-08-10 22:16 ` Paul Lalonde [this message]
2007-08-10 22:34 ` Charles Forsyth
2007-08-10 22:34 ` David Leimbach
2007-08-10 22:39 ` Bruce Ellis
2007-08-10 22:41 ` Paul Lalonde
2007-08-10 22:58 ` ron minnich
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=70A20023-DFBF-4F10-B13A-81B2E05C6727@telus.net \
--to=plalonde@telus.net \
--cc=9fans@cse.psu.edu \
/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).