At the end of the day, I see this really boiling down to two things. If either a) do not trust the development team (see earlier thread about editing tickets), or b) disagree with their priorities then simply do not use the piece of software. This is not specific to either Trac or Ilias. A fork has been suggested as an option, and there are other tools that could used. I am personally a big fan of forks in FOSS, I think they allow more people to bring their ideas to the table. For those that don't know, DrProject is a fork of Trac from a while ago, and I think it has some interesting features that would be nice in Trac. This is the way projects feed each other. Can we turn this into a constructive debate? Clearly you, Ilias, dislike a large number of Trac's policies or lack thereof, so take the source and go work on it yourself. If you come up with good ideas, I am sure someone will notice. If you make something better than Trac, I am sure people will start using it. As I said at the beginning, if either of those two statements apply to you, you need to do something differently, not the Trac team.
--Noah Kantrowitz Plugin Guru --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
