On Mon, Feb 24, 2003 at 04:03:45AM +0100, Tony L. Svanstrom wrote:
On Sun, 23 Feb 2003 the voices made Peter H. Coffin write:
PHC> On Sat, Feb 22, 2003 at 04:43:13PM -0800, Tyler F. Creelan wrote:
PHC> > On Feb 22 at 2:50pm -0800, Professional Software Engineering wrote:
PHC> > |I'd be interested in knowing _where_ said CVS is, since I'm a regular
PHC> > |enough contributor here that I'd just as soon be the one doing my own
PHC> > |updates.
PHC> > Actually I'm just airing the idea, I don't have a computer suitable
PHC> > for hosting, unless it can be on 14.4 dialup.
PHC> I can host. Are enough of our audience comfortable with a CVS setup or
PHC> would a hierarchical http space do?
1. Using a CVS there should be someone actively taking recipes from the list
and adding them; which will result in a lot of good quality recipes.
2. Using the a non-CVS solution the quality of the recipes might be somewhat
lower, and the number of recipes higher; not to mention that more people will
easier keep on working with their scripts.
The problem with #1 is that it would have to focus on complete solutions; the
problem with #2 is that the user would have to do a lil bit of thinking before
he starts using a recipe.
Personally I think people will lose interest pretty quickly, and that only #1
would have a real chance to survive (or even get going at all).
I was thinking along the lines of convenience of retreiving... perhaps a
combination of methods? CVS for recipe maintainers or section
maintainers, with a way for others to access the results by other means.
82. I will not shoot at any of my enemies if they are standing in front of
the crucial support beam to a heavy, dangerous, unbalanced structure.
--Peter Anspach's list of things to do as an Evil Overlord
procmail mailing list