On Tuesday, March 5, 2013 12:45:36 PM UTC+2, Hans-Peter Locher wrote: > > over making trac a django based application. > > As moving trac to become a django based app would have a large effect on > > - addon compatibilty > - migration of exisitng trac instances > - addon development in general >
Absolutely. But when you look at current trac-hacks catalog, there's only a few really serious must-haves there. I think they can be ported with reasonable effort, perhaps even simply replaced with existing Django ecosystem apps. All the other minor hacks it doesn't really make sense to worry about. If it'd somehow be possible to achieve a new platform codebase that could just rebase and merge Trac's core modules (Tickets, Wiki) improvements, that'd be awesome. There's also Apache BloodHound. I should dig through their mailing lists because I'm fairly certain they also discussed these options. -- 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.
