>
> I don't have the time to comment on everything in this mail, but overall
> I think it's a good approach. From your description, this could be
> entirely written as a plugin using the various I*ChangeListener
> interfaces already in Trac. The question of whether it goes into core
> Trac (replacing the existing system) can be deferred until it's complete
> as it shouldn't (at first blush) require any patching of Trac core.
>

Yea, I tried to make it as plug-iny as possible. Hm. If I just totally
disable
all the notification options in the trac.ini and use my own, then I'd
probably
need no core changes at all. Hadn't thought of that-- figured I'd have to
replace
the NotifyEmail calls. Cool, cool.

I figured the decision's be deferred anyways until I produced a patch and
someone decided it didn't suck ;-) But I was seeking thoughts early, so if I
can satisfy my needs and larger interests of The Greater Good at the same
time, might as well.


> You'd also probably have to implement a backwards compatibility layer on
> top of this system. eg. if "always_notify_owner" is set, an
> ITicketChangeListener implementation adds a subscription for that user.
>

Point; a LegacySubscription component can just always return
('email', 'username', '[EMAIL PROTECTED]') if that option is on as if they had
such
a subscription. And the other always_notify_* options. And a
CarbonCopySubscription component which tosses out everyone CC'd on a
ticket as if they had a subscription.

You should also definitely talk to Emmanuel Blot (eblot). He wrote the
> original notification system and I believe he has been considering
> extending it.


 Noted, thanks :)

--Stephen

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