Chad Emahizer wrote: > I think I might be restating a bit here from what others have already said, > but Trac does (or can do) what you want it to do. It is flexible and > doesn't force its own "business logic" on its users. It basically has to be > like that, or it will be targeting only a small portion of the population > regardless of whichever specific implementation it would choose to > implement. > > A problem with that approach is that not only do you have to learn a new > tool, but you also have to understand the processes your company has in > place and then determine ways to configure/utilize Trac to fit in with those > processes. ... > So, maybe the question shouldn't be "How is Trac supposed to be used?". > Maybe it should be "What are the processes for my company, and how can I > tailor Trac to enforce those processes and make them easier to do?"
There are 2 kinds of users: those who want to tweak software to do what they want, and those who're happy to click on a button and let the software take them to wherever Bill Jobs (aka Steve Gates) thinks they want to go. Those in the second category should probably not use trac, linux, or any "programming languages" other than flash. Dima --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
