"C. Michael Pilato" <cmpilato@collab.net> writes:
> While gaps remain between JavaSVN and Subversion's C core, I see no
> reason why you couldn't maintain your own versioning scheme and such
> and still live in the Subversion repository. Subversion wouldn't
> distribute JavaSVN in its tarballs and such -- you could release your
> own.
>
> When you have "caught up", though, I think it would make sense to
> unify the versioning schemes (though perhaps still keep distribution
> separate). And having your code in the Subversion repository should
> help to expedite this "catching up".
>
> Not to be a Fitzish wet blanket or anything, but you'd likely also
> need to change your copyright and license to match what is used by the
> rest of Subversion. I hope this isn't too great an obstacle though --
> I *really* think the combination of these two efforts would be a
> monumental step towards world domination. :-)
Also, if you can't work out a comfortable way to live in the same
repository as Subversion, we'd be happy to host a separate repository
for it on svn.collab.net, and have a 'javasvn.tigris.org' project, so
that you're part of the same "family" anyway.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 28 21:15:54 2005