Andrew C. Oliver wrote:
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?
eheh, sure. But XML is just a syntax and RSS is just a semantic. If I have no tool that reads RSS and does something good with it for me, it's useless data. Well-formed and valid, but still useless.
I emphasize *to me* because I don't run RSS feeds, nor have *any* intention of doing it since newsfeeds don't go along very well with my off-line habits (mine and those of million others throughout the world which aren't as lucky as many here).
Unlike good old asynchronous email.
But I'm not saying that it's a bad idea to have it, gosh no, just that it is not a general-enough technology for people to use it instead of email notification.
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.
Oh, great, that removes one of my concerns. Cool.
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.
Don't count on me :(
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.
Ah, good to know.
I am not convinced this is a good idea.... Might be a great tool for spamming or exploiting sendmail.....
Hmmm, pretty damn good point, didn't think of this one.
Could be wrong... I'm kinda a paranoid administrator...
Yeah, well, I'm no system administrator and definately not paranoid these days but I think I know enough about email to question if this is a real security concern or just paranoia.
I don't think it's possible to write something in a wiki, get it picked up, sent to a mail list, infect a sendmail of some sort simply by receiving the message (we use qmail, so no problem from our side, I'm concerned on the mail list subscriber receiver end) and do something nasty.
If that was possible, then a normal spam flood would do as much damage.
The only thing I see is people abusing the wiki to place shameless plugs of themselves that get submitted to the mail list.
But email doesn't really change the picture there.
So, call me liberal but I think we have more to loose than to gain in not allowing diffs forwarding to the mail lists.
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";
}
I don't think I get your point, Andy. What is this different from direct diff emailing?
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
As I said, I'm not advocating against it, I'm just saying that we need email nofication also.
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.
I'll let the more sys-adm-savy people take a shot there.
-- Stefano Mazzocchi <[EMAIL PROTECTED]> --------------------------------------------------------------------
