On Tue, 25 Mar 2003 19:02:54 -0700, "Jason R. Mastaler" <[EMAIL PROTECTED]> wrote:
> Probably start by figuring out how installation would change once > tmda-cgi is a standalone tarball. Then update the code and > documentation accordingly. Obviously, the tmda-cgi HOWTO would be a > good place to start for your own tmda-cgi page. Here's the complications that jump to my mind: [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? [2] tmda-cgi overlaps TMDA in Defaults.py. I like being able to keep my settings in the same configuration files and it's nice having ALL of the configuration variables documented in one place. I could split off my own documentation for CGI variables in Defaults, but what do we do when I need to make changes to Defaults.py between your releases? Do I release my own copy of Defaults and then have to go update it when you make changes to it (bleah!)? Do I release a patchfile to it instead of the actual file? Do we change Defaults so it includes my own defaults if CGI_ACTIVE == 1? > Once all this is done, we can modify the tmda-cgi references within > the TMDA docs to point to your site instead. > > Then I'll remove contrib/cgi from TMDA's CVS repository. So I guess that means its own SF project? > Discussion of tmda-cgi can take place as it does currently, on > tmda-users and tmda-workers. You can make release announcements on > tmda-announce if you'd like. That would be great. Gre7g. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
