Noah Kantrowitz wrote: <snip> > -1. You are trying to solve a PR problem with a technical solution. There > will always be that one plugin that someone wants, that we don't include. > Unless you propose to basically merge t.e.o and trac-hacks (possibly not a > bad idea eventually, but not a discussion for today), this won't do much > IMO. You know and I know what plugins on trac-hacks are up to snuff, and we > are quite clear about it in many places (see how many guides recommend > installing AccountManager). I would propose an alternate solution, the > creation of a "new" project that is officially recognized by t.e.o in some > way as being the turnkey solution so many people want. Perhaps something > like bitnami+oforge+some common options and config settings. "Trac" remains > the minimalist system we all know and love, and anyone installing it will > continue to get the same experience. People wanting the turnkey version can > get $NEWPROJECT, and not care about what particular components it pulls in.
Actually, I think Alec was trying to solve a PR problem with a completely PR solution. Moving "popular" plugins to t.e.o doesn't change the quality or function of the code, it simply gives it a more "positive" spin (isn't that what PR's all about?). Including some plugins in the tarball of the trac distribution saves all of 4 or 5 commands, and in no way changes the effectiveness of the code, but it does make people feel like they are getting "more". Now, I am actually -1 for moving "popular" plugins onto t.e.o because I don't think it's worth it. Same with bundling popular plugins in the tarball. However, I do think that we need to make it much clearer on both t.e.o and t-h.o that t-h.o IS the OFFICIAL place for trac plugins. If we don't like the "hacks" part of t-h.o, then let's look into getting another name to make the official plugin repos.[2] The other things we can do on t-h.o are: 1) Don't show all plugins by default, only show those that have been "vetted" (migrating to 0.11 and the VotePlugin would help here) 2) Create a section for plugins maintained by the core devs 3) (Optional) Create a "recommended by" section for the core devs to put the plugins that they use and recommend I'm also all for community projects like oforge, but more on that in the following thread: http://groups.google.com/group/trac-dev/browse_thread/thread/23f12595cff16914 -John --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
