I found Odd Simons (and other people ;)'s comments very interesting so here you have my own $0.02 version . Firstly I say that I enjoy when people say to me things like <<you're so damn wrong that it hurts>> , so please don't hesitate to do so if you feel it's necessary . I write this by assuming I'm terribly wrong and consult my personal psycho because I have butterflies inside my head ;) .
Secondly , there are a few facts involved in this story : - Wandisco has decided to launch some services and products. As a consequence a decision has been made that Trac should/will be the starting point to achieve product/service goals . * This means that continued and stable product support, defect resolution, ... are needed so as to ensure quality, reliability, ... and (I'm guessing) commitment so as to obtain some return-on-investment considering resources planned to be dedicated to this effort . * For some reason the current state of Trac community does not satisfy these requirements (... and honestly I understand this position ; e.g. the fact that Trac-Hacks is still running 0.10 , XML-RPC is disabled , etc, and nothing can be done even if some people want to, that's a bit frustrating for me - and this is not to blame anybody in particular, that's a fact and just an example - ) - The initial offer sent by the company to trac-dev & trac-users MLs was not received as they expected (for further details please consult previous comments). - For some reasons (previous experience, ... whatever) ASF alignment seems to be a very important (non-technical?) decision The fact that Wandisco still wants to consider Trac as the starting point to achieve some goals (disregarding the other details involved) is positive AFAICT . The fork of the project is, in part, a consequence of aforementioned conflict of interests . The duplicate effort and overhead will follow, but there are some technical and non-technical decisions that might mitigate the impact on both projects ; as long as they both will be able «coexist peacefully» (<= I hope you understand what I mean ) so that maybe maintaining plugins for Bloodhound & Trac will be similar to maintaining Trac plugins for 0.10 , 0.11 , 0.12 & 0.13 . I do believe that it would be very important if both projects are in synch and consider compatibilty as a goal to survive in this cruel world . Maybe a clear workflow (policy , ... or whatever name you want to use ;) to exchange code back and forth might help. I don't know what will happen in a near future but there's still a chance to make this happen just like many other software hosted by social coding sites (e.g. Bitbucket, Github ...) where many users (in this case Wandisco , Trac-dev community , maybe others later ... who knows?) commit changes to their (personal) repositories or patch queue repository and notify each other (e.g. by sending push/pull requests, patches under version control, ... whatever) of changes for review, approval, etc . Apache vs BSD should not be a problem . Another fact is that some plugin developers (please add my name to the list) have no chance to dedicate time to develop Trac plugins . Myself , I have a very long TODO list of enhancements , and I have not developed anything related to Trac since long time ago, even if I'd liked to, because I really cannot dedicate time to this (ok ... shame on me). The offer to support full-time Trac/Bloodhound developers IMO is positive as well AFAICS . I hope you agree if I mention that there's still a lot of place for enhancement in Trac core and plugins , e.g. testing and related QA, OS-specific packaging and more. AFAICS (and I may be wrong) this is happening nowadays in many open-source projects, even if **circumstances are not always the same** . I'll mention some of them : - Mercurial is a well established FLOSS project ... there you have Google maintaining a custom branch of development to make it run on top of their Big Table & Co. infraestructure. - Subversion is another paradigmatic FLOSS project . Once again there you have many companies building cutomized Subversion distributions (including Google & Wandisco) and paying developers (including Google & Wandisco) to make the project move forward . - Trac itself has been customized , patched , packaged & distributed in many forms ... e.g. Bitnami , OForge , Sourceforge as a hosted app , Assembla ... and project is still alive (although this is a completely different story). - Ubuntu & Debian ... a love story ;) - The Linux kernel vs patched kernels (e.g. Red Hat's ? , SuSE's ?) - OTOH other projects e.g. Hudson have been forked (e.g. Jenkins) and both of them survive and were able (as far as I could see in the ML ...) to <<move the wheel together>> while still keeping their own identity. Well I really cannot dedicate more time to write . I look forward to your comments as well , hoping this initiative will be positive for both Trac & Bloodhound -- Regards, Olemis Facebook => http://www.facebook.com/olemis Twitter => http://www.twitter.com/olemislc (@olemislc) Blog ES => http://simelo-es.blogspot.com Blog EN => http://simelo-en.blogspot.com Quora => http://www.quora.com/olemis Youtube => http://youtube.com/user/greatsoftw Featured article : Personalizando imagenes mostradas al compartir páginas en sitios sociales http://feedproxy.google.com/~r/simelo-news/~3/nSdht_RqLKk/personalizando-imagenes-mostradas-al.html Tweet: +1 RT @holdenweb This is insane. Everyone should be fighting this: Stop American Censorship http://t.co/S9EIkYdk #fb Follow @olemislc Reply Retweet 23:08 Dec-14 Get this email app! Get a signature like this. CLICK HERE. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
