> While people would certainly use it, I can't help but think that a BK
> clone would damage other open source SCM efforts. I call this the
> "SourceForge Syndrome":
Where do I get pills for that one? :-)
> Q. I found a problem/bug/annoyance, how do I solve it?
> A. Clearly, a brand new sourceforge project is called for.
>
> My counter-question is, why not improve an _existing_ open source SCM
> to read and write BitKeeper files?
I of course thought about that (I'm not yet
hit *that* hard by sf syndrome :-), but:
a) I might extend cssc, but bitbucket is
naturally layer *over* cssc, and cssc
is GNU program (copyright assignment
needed) and is C++. I do not feel like
writing new code in C++, and I do not
like their codingstyle.
b) take something else, *merge cssc to
it*, then add my stuff. Ouch. svn is out
because of licensing, cvs is not powerfull
enough, and I do not like arch. (I did
not know abojt opencm, sorry). Ouch
and this would mean fork, anyway,
because developers of that project
would probably not be happy about
those copyrights (FSF!).
c) so new sf project is indeed way to go :-(.
I hope you understand now,
Pavel
-- Pavel Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/