> -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Robert C Corsaro > Sent: Friday, June 20, 2008 12:29 PM > To: [email protected] > Subject: [Trac-dev] Re: Packaged Trac > > > Jeff Hammel wrote: > > There has been much discussion on this list and elsewhere concerning > installing trac + plugins out of the box, and probably doing > configuration. Several projects, such as oforge, already do this sort > of thing, but there is a perceived need for either other methodologies > or perhaps more of a community effort towards this solution. I'll > going to share my methodology that I use for installs and suggest a > short-term methodology for trac-hacks dealing with this issue. Nothing > here is meant to obviate the need for longer-term methodologies, such > as (just naming random ideas I heard) making plugins > installable/browsable via the webadmin interface, setting up a PyPi for > trac-hacks, better orphaning and adoption of plugins, and other ideas > that can't (or at least won't) be done in a day. > > > [snip] > > We would like OForge to be a community driven project, and not just an > Optaros project. I'd like to make it clear that having outside > contributers is one of the main goals of a doing public release. We > don't want to fork anything, but to be active members of the community. > The work we put into each component of OForge should be usable by > projects outside of OForge's scope. > > As far as one blessed trac distribution, I don't like the idea. As has > been mentioned many times, users have different needs. OForge, as it > currently stands, serves our needs. That of a consulting company with > many clients. We would expect that our users/contributers would have > similar needs. It could be that OForge fulfills the needs of other > types of users, that we haven't even considered. That would be great, > but we don't expect OForge to be the end all, be all of Trac > distributions. I think that there is room in our community for > multiple > trac distributions that suit different needs.
Really I don't think there is. Not in a bad way, but it seems like the insane flexibility we have created can sometimes be overwhelming to people. The idea of having the One True Turnkey Trac would be that it offers far fewer choices, but gives a new team the kind of structure and guidance many people seem to want. This also extends to things like the Trac install process. Many people don't know which of the dozen deployment options to choose so they decide "Trac is hard to install", when really getting Trac on tracd running takes no more than ~10 commands. I think giving people some kind of package that has all the best practices they have been hearing about setup and ready to go will lower the barrier to entry for a lot of people. And if they decide they want the flexibility back, Trac Classic will be waiting on the sidelines for them. --Noah --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
