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! 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. 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. I'll echo Ethan's question: Have you already looked into my suggestion to extend the existing permission system? I think that would be a pretty simple solution to your problem (I'd estimate one week if you can read and write Python) and I imagine that your code would inspire other cool new ideas for how Trac permissions can be used. //Peter -- 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.
