> My assumption was that since there is an Emmanuel Blot on the development team > you are he and that being part of the development team you would consider it > "your" project. (Whether or not you started it)
Indeed, "we" are the same person, I try to participate, but I do not consider the project as "mine" ;-) There are much more serious contributors to this project. > Perhaps it would be better to have asked what Trac brings you that an > intergration of existing tools does not. For example, there is already an > integration of Bugzilla, MediaWiki and various CVS packages. Well, from my perspective although these projects are great projects these are heavy projects and I was looking for a light tool, which integrate seamlessly the various features I needed (wiki+ticket+svn). To draw a comparison, *Office suites offer a very large panel of possibilities, with hundreds of features. However when I want to write a short document I don't need an Office suite, I do prefer a lightweight tool, which offers less features but fulfill my needs and is simple enough and nice to use. I don't need a spork that support hundreds or thousands of fancy features. In other words: keep it simple. Bugzilla, MediaWiki etc. use different technologies, different languages, and I don't think they could offer the same level of integration as Trac does. Trac does less things, but it is simple and nice to use. That's all I'm looking for. > Why not invest the time to make either of the other packages or the > integration of the two > better? There are a lot of ways to answer this question. From _my_ perspective, some answers might be: * I don't need the level of features they provide and the more features, the more complexity. This is a very important point for users that are likely to avoid using a bug tracker because of an overly complex interface. * They are really different beasts, and an integration could end up as a massive spork * From a technical point of view, I think Python fits nicely for this kind of application. I really dislike PHP (reasons for this are really off-topic), and I think MediaWiki is written in PHP. * Before using Trac, I used to work with Mantis (which is a very nice PHP tool btw), and the "user experience" IMHO is better w/ Mantis than it is w/ Bugzilla. * The plugin architecture, that rely on a clean architecture (*), allows me to easily customize Trac for my needs, without having to deal with a lot of features I do not need, and the dependencies they could bring. *: it's quite difficult to maintain a clear architecture when it comes to merge or bridge to very different products... * ... Cheers, Manu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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-users -~----------~----~----~----~------~----~------~--~---
