It's quite some times that we are thinking about a lot of new features we could introduce in Agilo, but most of the time we just incur in some Trac "limitations" and we just get frustrated... Do no...
I am an Agile Coach and Trainer and I am helping customers all around the world to become more Agile. I am more and more keen on adopting adaptive emergent approaches to improve people's quality of life. Through an holistic and pragmatic approach - I consider Lean and Agile very powerful frameworks - it is possible to improve results, performance and also personal satisfaction.
It's quite some times that we are thinking about a lot of new features we could introduce in Agilo, but most of the time we just incur in some Trac "limitations" and we just get frustrated...
Do not misunderstand me, fact is Trac has been build to do some generic and very easy to use Ticket tracking and management, what we are doing with Agilo is to try to support a specific Process, that needs a bit more of infrastructure, rules, support. We are now porting Agilo to Trac 0.11 and thanks to Edgewall guys, they really made some great improvement there... but still some things are just not fitting in :-(
First thought we had is to build a completely new User interface on and use Trac as a backend to store and retrive information, fact is that Agilo alters quite a bit also the "normal" Business Logic of Trac, and this is making the development of the product not so easy, but gives you as user the advantage to use additional plugins, or hacks :-)
On the other side, if we would have full control and the possibility of build our own Model we would surely be able to improve usability, without giving up on limitations, and probably achieve more attractive performance, optimizing the data management in the way Agilo needs without having to withstand the existing Models.
So, you are the users... what do you think? How much is it important that Agilo is based on Trac?
Thanks for Contributing, your opinion matters!