Re: [ZooLib-dev] Is ZooLib ready for real-world use?

[Joshua J. <ju...@nc...>]

At 6:01 PM -0700 2001-05-22, Andrew Green wrote:
>Hi Joshua,
>
>Using this mailing list would be most valuable, rather than sending
>directly to my email. I get the feeling that although there must be at
>least 1000 people who've downloaded the source, most of them have not
>been able to get into it because of the paucity of documentation and
>sample code. A richer mailing list archive might be helpful, and could

And the latest source archive on SourceForge doesn't compile out of 
the box with the current version of the dominant Mac compiler.  I 
suspect many people quit at this point.

>seed a documentation effort (I can dream).

If you build it, they will come. :-)  Eventually.

>wrt cvs, my copy of ZooLib is managed out of a private cvs server that
>supports the product development work of Learning in Motion and OISE.
>Every month or so I post a package of source at
><http://www.zoolib.org/bleedingedge/>,
>which I intended as an interim measure until I figured out how to handle
>keeping the source in two cvs servers simultaneously. Unfortunately I
>don't have any experience with that kind of setup -- in fact if I'm
>doing anything other than a checkin or update I have to hit the cvs
>manual to refresh my memory. If you (or anyone else reading this) has
>any suggestions about how to handle this I'd love to hear from you.

Well, you may find it rewarding to use a more intuitive CVS client. 
I have nothing against the command-line (and I rely on it on 
occasion) but for general use I use MacCVS Pro, the development 
version of which supports SSH.  My only objection is that binary 
distribution of MacCVS Pro violates the GPL.  There's also a Mac port 
of GNU cvs, but it's basically a front-end to the command-line 
program -- not as cool as MacCVS Pro.

As for the repositories, I haven't tried maintaining a project in 
more than one at the same time, and until the software supports it I 
don't recommend trying.  I specifically recommend keeping ZooLib in a 
repository that offers anonymous read access, and write access to the 
appripriate ZooLib developers (whom you may not wish to grant access 
to your private server).  I suggest you either run a separate ZooLib 
repository on your own server and open it to the public as outlined 
above, or just move it to SourceForge.  You can download the nightly 
tarball if you're paranoid.

Generally speaking, people want to contribute, and if you make it 
easy and rewarding, they will.  For me, contributing will be easier 
if I have (even read-only) access to a CVS server.  My vote is on 
SourceForge.  And I'll even set it up if you like -- make those tax 
dollars work for you! :-)

>Looking forward to hearing from you,
>Andrew Green

Looking forward to CVS.  I don't think I can be more clear than that. :-)

Josh