9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Kilbane <steve@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Publish and be damned.
Date: Sat, 21 Apr 2001 14:08:42 +0100	[thread overview]
Message-ID: <200104211308.OAA05285@localhost.localdomain> (raw)
In-Reply-To: Your message of "Sat, 21 Apr 2001 13:06:43 +0200." <002b01c0ca53$27545b30$e0b6c6d4@SOMA>

Lucio and Boyd are talking about different things. Furthermore, Boyd
knows this, but doesn't want to listen to it. :-)

Boyd's talking about each original author maintaining a package. Lucio's
talking about an amorphous mass of people hacking on several packages,
at whim. Boyd's starting point is simpler, because it's present-day.
Lucio's reason for changing things is so that a package doesn't stagnate
because the original author lacks time or inclination.

/n/dump is okay if you've got a reasonable level of self-discipline, and
your group is small. As the (project size)/(amount of discipline) figure
rises, a more comprehensive control system becomes more important.

Boyd suggests reading the code. That's fine if the code's good. If Lucio's
suggestion takes off, the code will be less predictable, and having a
change comment is more important, because the reason for the change may not
be deducible from the change itself.

But either way, I don't see any conflicts here. Russ's comments on avoiding
conflicts with BL's interests aside, I don't see a problem with Lucio setting
up the server. Those who like the idea will join in; those who don't, won't.
Whether it'll produce anything better than what would happen otherwise,
I don't know.

steve




  parent reply	other threads:[~2001-04-21 13:08 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20  5:54 Lucio De Re
2001-04-20 12:22 ` Boyd Roberts
2001-04-20 14:13   ` Eric Lee Green
2001-04-20 19:15     ` Boyd Roberts
2001-04-20 14:39   ` Lucio De Re
2001-04-20 20:35     ` Christopher Nielsen
2001-04-20 21:02     ` Boyd Roberts
2001-04-21  7:34       ` Lucio De Re
2001-04-21 11:06         ` Boyd Roberts
2001-04-21 12:59           ` Lucio De Re
2001-04-21 13:43             ` Boyd Roberts
2001-04-21 14:20               ` Lucio De Re
2001-04-21 13:08           ` Steve Kilbane [this message]
2001-04-22  1:37             ` Boyd Roberts
2001-04-22  9:37               ` Steve Kilbane
2001-04-22 14:51                 ` Boyd Roberts
2001-04-22 15:21                   ` Lucio De Re
2001-04-22 15:42                     ` Boyd Roberts
2001-04-22 15:55                       ` Software Repository
2001-04-22 13:26             ` Lucio De Re
2001-04-22 16:00               ` Dan Cross
2001-04-22 16:13                 ` Lucio De Re
2001-04-22 22:25                   ` Dan Cross
2001-04-22 16:18                 ` Boyd Roberts
2001-04-22 16:33                   ` Lucio De Re
2001-04-22 16:46                     ` Boyd Roberts
2001-04-22 22:14                   ` Dan Cross
2001-04-22 22:16                     ` Boyd Roberts
2001-04-22 22:25                     ` Boyd Roberts
2001-04-22 22:32                     ` Boyd Roberts
2001-04-23 19:31                       ` Dan Cross
2001-04-20 14:52 nemo
2001-04-20 15:11 ` Lucio De Re
2001-04-21 14:34 jmk
2001-04-21 19:03 ` Boyd Roberts
2001-04-22 16:12 rsc
2001-04-22 16:17 ` Lucio De Re
2001-04-22 23:52 rsc
2001-04-23  4:26 ` Lucio De Re
2001-04-23 19:33   ` Dan Cross
2001-04-23 19:32 ` Dan Cross

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=200104211308.OAA05285@localhost.localdomain \
    --to=steve@whitecrow.demon.co.uk \
    --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).