From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200104211308.OAA05285@localhost.localdomain> To: 9fans@cse.psu.edu Subject: Re: [9fans] Publish and be damned. In-Reply-To: Your message of "Sat, 21 Apr 2001 13:06:43 +0200." <002b01c0ca53$27545b30$e0b6c6d4@SOMA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Steve Kilbane Date: Sat, 21 Apr 2001 14:08:42 +0100 Topicbox-Message-UUID: 89019554-eac9-11e9-9e20-41e7f4b1d025 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