[Trac] Pluggable Modules

Christopher Lenz cmlenz at gmx.de
Tue Jan 11 06:50:32 EST 2005


Am 11.01.2005 um 01:32 schrieb Christopher Lenz:
> Am 11.01.2005 um 00:07 schrieb Brad Anderson:
>> I took a look at Christopher Lenz's patch here:
>>
>> http://projects.edgewall.com/trac/wiki/TracPluggableModules
>>
>> and it looks promising.  My question is, what is the timeframe for a 
>> change
>> like this?  Is this post-1.0 or pre-1.0.  I'm working on a couple of 
>> modules
>> and would like to fit into this framework if it will be ready soon.
>>
>> The code looked like prototyping only, and I'll dive deeper into it 
>> this week.
>> But how big of a breadbox is it to retrofit current modules to this 
>> new
>> framework?  I would definitely be able to help, although I see time 
>> getting
>> little bit scarce in the coming weeks.
>>
>> Just curious as to the perceived timeframe on this.
>
> The timeframe pretty much depends on:
>
> a) feedback from the edgewall folks <ping/> and anyone else interested
> b) whether we can drop support for python 2.1 (the new architecture 
> requires >= 2.2)
>
> If those two points get checked, I would say that the refactoring 
> could happen even before 1.0. Yes, there's a lot of code that would 
> need retrofitting, but it's doable. And probably in an almost 
> evolutionary fashion (i.e. having working code in trunk throughout the 
> process).

To put my response into some context, the original plan is to continue 
building on the current code-base until 1.0. At that point we want to 
branch out and do some much-needed refactorings, not only to support 
pluggable modules, but also for:
  - Multi-project support
  - Better integrated user management (whatever that means)
  - Database independence
  - Support for other version control systems
  - SOAP/XML-RPC interface

I think it's a good idea to defer any big changes until we've put a 
stable 1.0 release out with a solid feature-set. But it's starting to 
look like we might get database independence and an abstraction layer 
for different version control systems into Trac without any really 
major changes (thanks to your and Justus' work), so the magic 1.0 line 
has already started to blur...

> There's also the issue of momentum. I'm currently the only committer 
> actively and regularly working on Trac (i.e. checking stuff in, 
> applying patches, etc), so trunk might starve when my interest in the 
> current code-base fades. If we want to keep up the plan of refactoring 
> after 1.0, we need more folks with write-access to the repository 
> <ping target="edgewall"/>.

Cheers,
Chris
--
Christopher Lenz
/=/ cmlenz at gmx.de



More information about the Trac mailing list