I think you should take a look at what people are doing with Bloodhound https://incubator.apache.org/projects/bloodhound.html
Obviously whatever patches you can come up with for Trac *or* Bloodhound are always welcome. Just keep in mind all new stuff is a process that affects a lot of people, so nothing is guaranteed to get it and takes a lot of perseverence to polish and finish. I just don't see how rolling your from scratch, by yourself (if that is the case), could get close to what Trac's codebase is today. It takes years and years and power of many men to work all the quirks out and achieve real feature completeness and stability. So I would definitely encourage you to patch existing work to the max, customize it to your specifics, push applicable stuff upstream. Everybody wins and you get your tool while youre still young. :> On Friday, April 6, 2012 5:43:45 AM UTC+3, Devin Jacobs wrote: > > I've been thinking about writing a issue tracking system myself, > because I feel the existing options are all too complicated for my > needs. I'm a Python fan, so Trac was first on my list. I figure Trac > will either support the workflow I want in my issue tracking system or > I can find ways to contribute and customize Trac. > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/trac-users/-/HcaEzzDaXMoJ. 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-users?hl=en.
