Noah Kantrowitz wrote:
>> -----Original Message-----
>> From: [email protected] [mailto:[EMAIL PROTECTED] On
>> Behalf Of Jani Tiainen
>> Sent: Thursday, June 19, 2008 1:11 AM
>> To: [email protected]
>> Subject: [Trac-dev] Re: Is Redmine a better Trac? What's gone wrong
>> with Trac?
> 
> [snip]
> 
>> But still it feels that there is not much of real discussion how to
>> implement and possible solutions. Most of requests are bypassed by "use
>> a plugin" or "do a plugin" statements. It's a bit annoying specially
>> since it makes you feel that you need to trust some hacked "3rd party"
>> tool.
> 
> This is true. We do avoid discussion of some things when we know there won't
> ever be a clear way forward without action. In the example of multi-project
> support, I have been quite vocal that people should build examples of lots
> of different models, and see which ones people like. This is why I have
> spent so much time trying to build TracForge.
> 
> Unrelated to this is the idea that doing things in plugins is bad. I really
> don't understand where people get this idea. Trac is already just a plugin
> framework, and some bundled plugins (wiki, tickets, timeline, etc). There is
> no fundamental difference between 3rd party stuff from trac-hacks, and Trac
> itself (other than decoupled release dates, smaller codebase, etc). I wrote
> a long rant on this on my blog
>  (http://coderanger.livejournal.com/23087.html) so I don't feel I need to
> repeat it all here, but the short of it is that people need to stop thinking
> "plugin" == "bad".
> 
[snip]

It would be good to get feedback about why ppl feel this way.  Noah has 
talked about trac-hacks++ and a nice plugin installer.  That would go a 
long way to dispel the notion that "trac-hacks" are bad.  I also think 
some marketing could go a long way, like drop the name for something 
more "stable" sounding. ;)  A rating system would be nice, so you could 
see right away what plugins are solid and widely used and which ones to 
be wary of.  Also, a simple way for ppl to contribute to plugins.  I 
think github does an excellent job in this regard and would like to see 
something like that for trac-hacks.  We wouldn't have such a problem 
with orphaned plugins either.

What are ppl's feelings about this?


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to