9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: orc@pell.portland.or.us (david parsons)
To: 9fans@cse.psu.edu
Subject: Re: [9fans] porting from vs. porting to Plan 9
Date: Mon, 20 Oct 2003 18:14:18 -0700	[thread overview]
Message-ID: <bn219a$lc5@pell.portland.or.us> (raw)
In-Reply-To: <slrnbp6q8f.b5f.pat_e@garcia.efn.org>

In article <slrnbp6q8f.b5f.pat_e@garcia.efn.org>,
Patrick R. Wade <pat_e@efn.org> wrote:
>In article <43bc6b835731c3c823fdd658cb28775e@plan9.ucalgary.ca>,
>mirtchov@cpsc.ucalgary.ca wrote:
>>
>>i think Geoff is right -- without somebody being able to work
>>full-time on those things nothing will get done.  the bubble burst and
>>the code that depended on developers' spare time is moving ahead
>>slower and slower -- see how long it took for FBSD 5.0 to come out.
>>
>
>Which seems kind of backwards; one would expect the bubble bursting to
>leave lots of developers with *more* spare time than before...


   Not necessarily.  Being unemployed takes you away from your nice
   remote office where you can work on your open source(r)(tm)(c)
   project after hours and during lunch and puts you at home, where,
   aside from the exciting job of writing PLEASE HIRE ME letters,
   sending resumes, and looking for more victims to send resumes to, you
   become available to the rest of your family.

   I'm guessing that in the two years of recovery that I've enjoyed I've
   done less open source(r)(tm)(c) coding than I've ever done since
   before I was a college student, and the largest chunk of that coding
   has been sneaking off to do 5-6 hour keep-my-fingers-dirty exercises.


                 ____
   david parsons \bi/ Grrr.
                  \/




  reply	other threads:[~2003-10-21  1:14 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 15:20 mirtchov
2003-10-17 16:34 ` Skip Tavakkolian
2003-10-17 17:08   ` Joel Salomon
2003-10-17 18:55     ` Brantley Coile
2003-10-17 19:05       ` matt
2003-10-17 20:17       ` ron minnich
2003-10-17 20:20         ` Christopher Nielsen
2003-10-17 20:26         ` Brantley Coile
2003-10-17 20:41           ` Charles Forsyth
2003-10-17 20:54             ` Brantley Coile
2003-10-20 10:33             ` Douglas A. Gwyn
2003-10-20 16:03               ` Skip Tavakkolian
2003-10-21  6:07                 ` Adrian Tritschler
2003-10-17 22:18           ` ron minnich
2003-10-20  1:38             ` okamoto
2003-10-17 21:36         ` Roman Shaposhnick
2003-10-20 10:33           ` Douglas A. Gwyn
2003-10-21  0:10             ` [9fans] Re: your mail Roman Shaposhnick
2003-10-17 23:38       ` [9fans] porting from vs. porting to Plan 9 Geoff Collyer
2003-10-18  1:21         ` bs
2003-10-21 10:14           ` Martin C.Atkins
2003-10-18  8:27         ` Charles Forsyth
2003-10-18  8:48           ` Richard Miller
2003-10-18 11:09           ` Geoff Collyer
2003-10-18 13:09             ` Tristan Seligmann
2003-10-19  8:25               ` C H Forsyth
2003-10-20  3:28                 ` mirtchov
2003-10-20  7:04                   ` Tristan Seligmann
2003-10-20 17:17                     ` mirtchov
2003-10-20 10:35                   ` Patrick R. Wade
2003-10-21  1:14                     ` david parsons [this message]
2003-10-19 16:27             ` Charles Forsyth
2003-10-20 10:35             ` bs
2003-10-18 19:19           ` Richard Miller
2003-10-19 15:10             ` I RATTAN
2003-10-19 15:54               ` Richard Miller
2003-10-20 14:03             ` ron minnich
2003-10-20 17:03               ` jmk
2003-10-20 21:40         ` splite
2003-10-17 16:43 ` Ronald G. Minnich
2003-10-17 17:01   ` Fco.J.Ballesteros
2003-10-17 20:17     ` Christopher Nielsen
2003-10-20 10:33       ` Douglas A. Gwyn
2003-10-17 15:36 steve-simon
2003-10-17 16:05 Richard C Bilson

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='bn219a$lc5@pell.portland.or.us' \
    --to=orc@pell.portland.or.us \
    --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).