On 3/5/2013 6:13 PM, Peter Stuge wrote: > Javier Domingo wrote: >> I think that going django would mean a complete remake of trac, but >> would simplify a lot trac deployment (in for example appengine) > > Stop the madness. > > Trac has existed for 10+ years. You're a student who doesn't really > know Python (you said). > > It makes no sense whatsoever for you to rewrite Trac using hipster > frameworks!
Well, something like that has been attempted already, also by people wanting to use Trac for supporting university projects. Greg Wilson and his student teams fro U. of Toronto started DrProject, a fork of Trac, in 2006 (IIRC) aiming at a simplified interface and multi-project support. At some point they decided to rewrite this on top of Django: the Basie project was born. Then apparently they decided to move from that to Pinax (1). That might be already closer to what you want to achieve... > > You would be completely alone working on that, it would take an > enormous amount of time because you have to learn so many things, > and in the end it's not likely going to be any better than what is > already there. Switching to a new cool "technology" can feel attractive and there might be some advantages in the long run... or not, it's always hard to tell beforehand. Witness our Genshi migration, which was a very long trip, with lots of ups and downs. It's true that Peewee looks nice (thanks for the pointer, Hans-Peter!), but using it or something similar is not a light decision to take (a switch to SqlAlchemy was suggested or tried several times since 2006, it didn't happen, maybe for good reasons). And I tend to agree with Peter, even if such a switch would be successful, would Trac really be significantly better after? I think that this amount of effort and time would be better spend on rethinking the *model* itself, rather than focusing on the cosmetics of using the model we have. > > Please just learn to develop the existing Trac instead, and work > together with existing community. You will be able to accomplish > much more with much less effort. Trac, or anything closer to what you're aiming at (check the Pinax thing mentioned above, someone suggested you have a look at BloodHound, and if you're not too deep already in Python, you also have Redmine/ChiliProject to look at). My point is that if you realize that the Trac fundamentals don't suit you or your purpose, maybe you would be better off to start with something that fits better, as there's no lack of alternative models. This is not to say that everything is perfect in Trac, of course... -- Christian (1) http://third-bit.com/blog/archives/4079.html -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
