I think it's a great idea, check out CPAN for a great model of how this sort of thing works. No CVS necessary because it should be a repository of "releases" not a repository for development, that's what places like sourceforge are for...
-Peter --- Peter A. Vogel Manager, Configuration Management Arsin Corporation, Professional Services http://www.arsin.com > -----Original Message----- > From: Diane Holt [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 02, 2001 1:58 PM > To: [EMAIL PROTECTED] > Subject: RE: [ANNOUNCE] Coming Soon: taskdefs.org website... > > > --- Tim Vernum <[EMAIL PROTECTED]> wrote: > > All I really need is somewhere to put a task with > > * Task code > > * Documentation > > * Sample build file > > > > And then have a url I can point people to when they say > > "I wanna foreach task" > > > > Obviously searching is useful too. > > I don't think you need any sort of CVS though. > > Your original <foreach> has already had changes submitted to > the list(s). > How do you see that being handled, if there's no > source-control available? > > Diane > > ===== > ([EMAIL PROTECTED]) > > > > __________________________________________________ > Do You Yahoo!? > Get personalized email addresses from Yahoo! Mail - only $35 > a year! http://personal.mail.yahoo.com/ >
