Gre7g Luterman <[EMAIL PROTECTED]> writes: > [1] Would you want me to get tmda-cgi its own sourceforge space so I > can update it without bugging you, or do you want to set up a way > that I can make releases somehow within your project space?
I can create an additional 'tmda-cgi' module along side 'tmda' within the CVS repository if you want. Then you wouldn't have to register a new project. > what do we do when I need to make changes to Defaults.py between > your releases? You can still make changes to Defaults.py as you've been doing. Since our efforts are tightly coupled, I can speed up a release if you're waiting on something you added to Defaults.py. Historically though, your changes to Defaults.py aren't that frequent, so I don't think it'll be a problem. >> Then I'll remove contrib/cgi from TMDA's CVS repository. > > So I guess that means its own SF project? No, it just means it'll no longer be housed within tmda/contrib/cgi, but rather as it's own module within CVS. For example, you'd checkout the tmda-cgi module using the following (once I create it) $ cvs -d:ext:[EMAIL PROTECTED]:/cvsroot/tmda co tmda-cgi _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
