I'd much prefer mailing list notifications over RSS feeds. These types of notifications shouldn't be pull. Push-based notifications suit this problem domain far better than pull-based approaches. It also allows archiving of the changes. (We can recreate our entire CVS archive in the event of a castrophic failure just from the complete CVS commit archives.)
I agree with Justin, expecially because while email is a generally used tool around the ASF, weblog and related technologies are not as common.
You know...One could have said that a couple years ago regarding XML technologies... Besides.. RSS is just XML.. .. We like XML right?
Also, I think that 'page-based' RSS it way too granular.
Look at this: http://superlinksoftware.com/cgi-bin/jugwikitest.pl?action=rss
It looks like I was wrong. . Its not per page.. Its the recent changes syndicated as rss... I thought it was per page... ooops.
To be honest there's a fat chance you're getting udiffs. <funny requestedaction="laugh">Thats like asking a kangaroo to shit turtles.. . </funny>
Let's just create a wiki@ mailing list and send everything there. Have it send unified diff's in the style of our CVS mailer. -- justin
If I had to choose I'd rather prefer to send the udiffs to the various mail lists that control their areas.
You most likely will get diffs which will match what is written to the wiki file that will make sense.
To enable this someone needs but to submit the appropriate patches and I'll be pleased to install them.
Think about having [EMAIL PROTECTED] with *all* CVS commits going thru, I don't think that anybody would stand such a low signal/noise ratio and I fear this might be happening here if the wiki takes off.
Yes... I think the wiki is set up to allow you to specify mail lists for those. I am not convinced this is a good idea.... Might be a great tool for spamming or exploiting sendmail.....Could be wrong...
I'm kinda a paranoid administrator... If it were just up to me, I'd ask someone to write a script that goes and does this in a batch based on some rules in a cvs module (so that access was restricted)...
roles:
crontab {
bootstrap running daily/hourly/whatever
}bootstrap.sh {
checks out latest version of myscript and its settings
runs it
}myScriptThingy.pl/py/whatever {
reads the wiki database, sends mail notificaiton of changes to various lists based on rules (perhaps just simple regex or something) specified in myDataFile
}
myDataFile {
"Cocoon*, *Cocoon, *cocoon, *cocoon*, *Cocoon*", [email protected], "message from your loving ApacheWiki....daily diffs";
"POI*, POI*, *poi, *poi*, *POI*, Poi*,*Poi,*Poi*", [email protected], "come and get it, fresh POI served from the ApacheWiki";
}
In short, while a single-page RSS is too specific, a wiki-wide diff mail list is way to general.
I think the RSS is useful. check it out:
http://superlinksoftware.com/cgi-bin/jugwikitest.pl?action=rss
My personal suggestion would be to find a way to partition the wiki pages per project and send those diffs to the various project mail lists.
But I have no idea on how difficult/feasible that is with the current software.
Its highly feasible, I just don't know how "wise" the facilities provided are (letting someone say "sure mail this out to here" seems dangerous...) The above suggestion is probably more secure, easy to implement, etc.
