on Mon Jan 12 2009, Jeff Hammel <jhammel-AT-openplans.org> wrote:

> Two points:
>
>  * releases for trac are triaged well ahead of time.  For instance, the 0.12 
> release
> focuses on i18n (IIRC).  So even if this additional feature was trivial 
> (which it
> almost is), it might not be slated until several releases in the future.  
> Read:
> several years (maybe).  I'm all for faster development of trac.  That being 
> said, I
> haven't thrown my hat in the ring to this end, so I can't complain.  But 
> plugins can
> be developed and version completely independently and can provide a solution 
> for
> everyone (that follows trac-hacks, anyway) now.
>
> ...relatedly...
>
>  * developing components as plugins allows for independent efforts of 
> implementation,
> testing, and release from core.  You can work out a solution without having 
> to tramp
> all over a shared code base.  Once a plugin has been proven, it is much 
> easier to
> propose an enhancement to core and really start to answer the question: "do 
> people
> want this?"  You can actually see what the plugin does and meaningfully judge 
> it.

These are both wonderful features of a modular system.  However, they
don't really address why you think this particular improvement "belongs"
in a plug-in.

> That's my opinion anyway, as a plugin and non-core developer.  One of
> my patches is now in core (from the AutoQueryPlugin) and another is
> triaged for 0.13 IIRC (from the AutocompleteUsersPlugin).
>
> On the other hand, if you wanted to provide a patch, I'm sure that
> would be considered too.

Yeah, perhaps I will.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com


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