On Mon, Jun 27, 2005 at 03:00:07PM +0200, Tom Schindl wrote:
> Well I'm not sure we should go on discussing here the issues with TomKit
> which is until now not the offical successor of AxKit or moreover AxKit2
> and maybe will never be. Maybe I should get up a mailling list
> discussing TomKit or what ever name it will get. What's the opinion of
> the other guys hanging around here?

Hm - it' time to create a *master* repository for TomKit.

But why not using the NameSpace "AxKit2" to merge all the usefull
things of (will be) derived *Kit's. 

"TomKit" sounds really close to "Tomcat",- another Apache XML Project.
The "AxKit"-label is also wellknown, and the community get together 
at "axkit.org".

The existing infrastructure "axkit.org" should be used, - if this 
doesn't collide with the interests of Matt Sergant or his company
AxKit.com Ltd ... but I see: The domain AxKit.com is gone ...

And remember: "AxKit.org" already belongs to xml.apache.org ...

We should start a _distributed_ versioning (like the GIT stuff
        http://www.kernel.org/git/
). So everyone can do his versioning offline from a central 
repository in his own copy of the repository ... maybe later 
to merged/patched into the mastercopy. The mastercopy's home 
can be everywhere ... reachable/linked by axkit.org ! 
And your copy, Tom, is the mastercopy ;)

My Apache2-TomKit GIT repository is placed (temporarily) here

        http://www.RichardLeopold.com/git/Apache2-TomKit.git

On Debian (etch) do this to make your _own_ copy/clone of it:
        # apt-get install cogito
        $ cg-clone http://www.RichardLeopold.com/git/Apache2-TomKit.git
        $ cd Apache2-TomKit
        $ ls -la

Also the current bug- and issue-tracker can be linked by AxKit.org
Tom - I've bookmarked yours at:
        http://phpot.bestsolution.at/mantis/main_page.php

I've waited a long time to see axkit.org starts with Apache2 ...
... it's time to start, anyway ! And the TomKit-Source will be 
the initial ignition ...

Regards - Richard

--
http://www.RichardLeopold.com

Reply via email to