Re: [Debian-sf-devel] Plugin infrastructure -- Request for comments

[Tim Uckun]

> - Your Own Idea here.

All good ideas. A plug in system would indeed be very useful and in fact 
what you are proposing here is very close to what phpgroupware does. Here 
are some other ideas you may want to think about.

Sourceforge base class (or api) should have a register_plugin function for 
installing and registering plug ins.
There should be a way to "publish" plug in information and interfaces so 
that different plug ins can communicate with each other. For example when a 
task is added and has a start and an end date those dates should be 
communicated to the calendar plug in along with the user who is assigned 
the task. When that person logs in the calender shows the due date for 
his/her tasks. Same with gantt charts and tasks.

If you go to the phpgroupware site and use the demo you'll notice that the 
bug tracking system does not know anything about the project tracking 
system which makes it practically useless!.

Without some sort of an inter process system you will end up in the same place.

Maybe a better way would be to take a zope like approach as done by this 
guy  http://dev.4arrow.com/

I don't know what the answer is but a calender is a good idea.

:wq
Tim Uckun
US Investigations Services/Due Diligence
 http://www.diligence.com/