9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: steve_kilbane@cegelecproj.co.uk steve_kilbane@cegelecproj.co.uk
Subject: [9fans] Oil on the water
Date: Wed, 23 Sep 1998 09:37:59 +0100	[thread overview]
Message-ID: <19980923083759.OgrNk23XngsSQlSdlObD8t3cs1kApGCrmF6LGGX6_sI@z> (raw)

On 22/09/98 22:28:53 rob wrote:

> The main obstacle to a release is pragmatic: the work of putting
> together a coherent package of hundreds of programs and the better
> part of a million lines of code is not something to be undertaken
> lightly.  There were several man-years of documentation work alone in
> the last distribution.  We don't relish going through all that again.
[shudder]

I wonder, would it be possible to have multiple levels of release?

Lucent would provide the first level of distribution, which would be for a
single, agreed-upon platform spec, with minimal documentation. This would
be somewhat similar to the ealy UNIX tapes.

The second level would be provided by Plan 9 users, rather than Lucent,
allowing the userbase to extend the basic distribution to something more
acceptable to today's persistence-challenged net: more docs, more drivers,
additional hardware platforms, better installation code, etc.

I'm taking a lot for granted from the readers of this list, of course. Just
thinking of ways in which the initial release process can be made less
demanding on the original developers.

steve






             reply	other threads:[~1998-09-23  8:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-23  8:37 steve_kilbane [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-09-24  9:08 forsyth
1998-09-24  8:54 Digby
1998-09-24  8:27 steve_kilbane
1998-09-24  7:49 Nigel
1998-09-24  7:34 Elliott
1998-09-24  7:28 okamoto
1998-09-24  3:04 jmk
1998-09-23 17:09 Frank
1998-09-23  6:32 James
1998-09-23  5:40 G.David
1998-09-23  4:48 Lucio
1998-09-23  2:27 Digby
1998-09-22 21:28 rob

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=19980923083759.OgrNk23XngsSQlSdlObD8t3cs1kApGCrmF6LGGX6_sI@z \
    --to=steve_kilbane@cegelecproj.co.uk \
    /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).