On Mon, 2 Jan 2012, Christian Boos wrote:
Please, let's drop this "vote". We initially suggested the fork as a way for them to be able to show us more "meat" so we're not in a position now to say "no, don't fork", even if there's still no meat and they even moved one step ahead by starting the Apache incubation directly. Realize they have their own constraints, habits, and right to do what they want with the code.
You still have the right. I doubt you have been aware (or even are now, or ever :-) of all the implications and it is not forbidden to change the own opinion.
The main argument about fork or not seems to be the argument whether Trac core is capable to be the base of an improved project. WANdisco claimed no. I would say: Better try and only if it really does not work do the fork later. It is VERY complicated to undo it.
They have the right to do so and they don't need to ask, but this does not mean they really need to go that way. The question here is if TRAC DEVELOPERS want that fork or not.
Forking a project always consumes a lot of additional manpower which better could be spend on improving a living project (like Trac is).
Ciao -- http://www.dstoecker.eu/ (PGP key available) -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
