[Gardeners] CL Gardeners: good news, bad news, how to win big

[Brandon Edens]

I'd like it if it were possible for other developers to not necessarily take
over the project on CL directory but instead have a means of submitting patches
and usage notes/examples/howtos relating to a project. The CL directory could
act as the meeting ground for the projects that it houses, or at least a journal
of information relating to projects.

I know this requires additional work in the framework. Its just that if I were
using CL-NCURSES and someone else was adding additional features/bug fixes to
that project then I'd like a standard way/place of/to learning about those
modifications (not every project has a mailing list). I know there was some
mention that the directory would eventually help house/mirror projects. Can we
start by having it be place to store this sort of data? I see this as slightly
more than just notes/comments.

Brandon

On Fri, Feb 24, 2006 at 11:13:08PM -0800, Peter Seibel wrote:

> My understanding was folks were proposing a one-month time limit for  
> the project maintainer of record to *respond* to the email, not  
> necessarily that folks have to check in something every month. The  
> point is, as I understand it, that if I see a project that I'd like  
> to submit patches to and it doesn't have any obvious activity going  
> on, I drop a note to the c-l.net guys and ask them to ping the  
> current maintainer. If the maintainer replies with, "Yes, I'm alive  
> and still care about the project" then they get to keep it. It's only  
> if there's *no* response for a month that the keys to their project  
> might be given away to someone who's showing more interest in it. And  
> the original maintainer can always show up later and say, "Hey, I was  
> out of the country for a year and away from email, what happened?!"  
> and get their project back in the state it was in when they left. Of  
> course if in that year the new owner has made a bunch of changes they  
> may want to fork. Which could happen now; the new policy seems aimed  
> at preventing needless forks, mostly in the interest of not confusing  
> would-be users of these libs.
> 
> -Peter
> 
> -- 
> Peter Seibel           * peter at gigamonkeys.com
> Gigamonkeys Consulting * http://www.gigamonkeys.com/
> Practical Common Lisp  * http://www.gigamonkeys.com/book/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://www.lispniks.com/pipermail/gardeners/attachments/20060225/4c0083fe/attachment.bin