Patch to get email notification (with diff) of wiki changes

[pierre.palatin+trac@…]

This is a little patch to get notification, with diff included, of wiki changes.
That's implemented against trunk/, revision 1777, as a component.
I did'nt know where to put plugins, so I put it in Notify.py (I use NotifyEmail? class), but I don't like that too much ...
(patch follows ...)

[pierre.palatin+trac@…]

initial version of wiki changes email notification patch

[ytse@…]

This feature is useful, but get_recipients() looks too simple. It would be a great deal if a user could control the notification by oneself. It may by a watch-list of wiki pages in user's settings or something else...

Let us see how other wikies do it.

[cmlenz]

See also #576.

[cboos]

See also #1459, which discusses a redesign of the ticket CC field.
Transposed here, the idea of a nosy list for a Wiki page is also interesting,
as anyone who contributes to a Wiki page is potentially interested in what
follows-up...

[husted@…]

Let us see how other wikies do it.

Typically, the email address comes from the user profile, rather than being input with the change. The user profile will have settings that determine whether and/or what kind of notifications are issued. For example, sometimes you can opt-out of alerts for your own changes.

Confluence lets you watch a space, so that you can get email alerts for any change to any page in the space. You can also opt-in for a daily change summary.

Moin-Moin also lets you subscribe to pages using a regex. You can use ".*" to subscribe to all changes, or another expression to subscribe to a smaller set. The UI will also add an individual page to the list for you.

Both have a "trivial change" setting you can check. Subscribers can then "opt-out" of trivial changes.

Adding wiki email notification seems like a "must-have" feature for a 1.0 release, since it is now a standard feature of similar products, that many people (including myself) consider essential.

HTH, Ted.

[cboos]

More general notifications certainly need to make it for 1.0,
if not sooner.

Alect an me have already discussed a bit about this and the need
to make notifications react on change listeners.

[cboos]

Generic change listener interface coupled with notification should be defined.
This is somehow related to the propagation of "contexts" of changes that will be introduced at the wiki level.

Adapters to the 0.10 compatible APIs could be written on top of that.

[Noah Kantrowitz (coderanger) <coderanger@…>]

The ​WikiNotification plugin will do this for 0.10.

[jason@…]

Updated patch which applies to trac 0.10

[jason@…]

I have updated the patch to apply cleanly to (and function correctly) with trac 0.10.

[mgood]

Replying to jason@peaceworks.ca:

I have updated the patch to apply cleanly to (and function correctly) with trac 0.10.

It looks like you forgot part of the patch, since it only includes the template and not the associated code changes.

[stelian.iancu@…]

So is this going to svn commit anytime soon?

[cboos]

• the patch attached here will most likely not be integrated in the 0.10 branch, as 0.10.x releases are mostly bug fix releases; they only get minor enhancements that can be easily backported from trunk
• the real fix for this feature (eventually for 0.11) is getting nearer, as I recently made some progresses on the architecture changes needed for this to happen (see TracDev/Proposals /Journaling if you're interested in the details). I'd certainly make use of the contributed patches in some way or another.

[cboos]

#379, #4679 are also duplicates of this ticket.

The new notification architecture is currently being discussed in ​Trac-Dev.

[cboos]

Most probably not for 0.11.

[stoile@…]

I'm very interested in this Feature, too.

[cboos]

Keeping on the long term plan, however this is a very important feature to have, as it makes it possible to have well maintained pages through a micro community of editors interested in that page only.

[itamaro]

I'm confused - what's the difference between this enhancement and #2293?

[cboos]

The mechanism of notification is quite different (push vs. pull to make it short).

#2293 is about RSS readers regularly querying for changes (pull) that happened to a given page (or hierarchy subset), the same way as the timeline RSS feed restricted to the wiki changes would get you the changes for all pages.

Here, we're talking about sending a mail after each change (push), in a similar way we do for ticket changes. However, we probably don't want to reimplement the Cc: system for the wiki, with all its quirks and limitations. We rather need something like nosy list of RoundUp (#8637).

[DMcLean <dmclean@…>]

I would like to see this change as well.