Hi Simon, on 2007-05-03 09:51 Simon Josefsson said the following: > Frank Ellermann <nobody@xxxxxxxxxxxxxxxxx> writes: > >> Simon Josefsson wrote: >> >>> I'm not sure it automatically imply that there are any indexes, >>> a log of who made what changes when, or a search function, etc. >> >> Some wikis offer a revision history and a search function, e.g. >> most openspf.org pages are based on a Wiki, which is a fork of >> "Usemod". That offers a news feed (RSS) for "recent changes". >> >> The IAOC wiki is broken at the moment (at least from my POV), >> but the IESG wiki using the same software has similar features, >> check out <http://tools.ietf.org/group/iesg/trac/timeline> > > Will the IAOC use the same wiki software? Since it's up and running, why don't you go and have a look? The links are here (and in the left-hand menu-bar of any tools.ietf.org WG or wiki page): http://www3.tools.ietf.org/group/iesg/trac/ http://www3.tools.ietf.org/group/iaoc/ There's also, to complete the set, these: http://www3.tools.ietf.org/group/trust/ http://www3.tools.ietf.org/group/bof/ http://www3.tools.ietf.org/group/wgchairs/ http://www3.tools.ietf.org/group/irtf/trac/ > I seems sub-optimal to > require the IAOC to use a particular wiki implementation. It seems > better to list the requirements one should have on such an > implementation instead. That gives the IAOC/tools team more freedom to > chose and/or develop its own software. Well, since it's all in place and running, we've had the needed freedom already ,;-) >>> Setting up a mailing list that receives notification of >>> every change to the wiki is another idea. >> >> IMO redundant if there's a news feed. You could watch it >> with a "google alert", and let the "alert" post to blogger >> readable as pure HTML (i.e. without feed reader or ugly >> Javascript approximations of a feed reader). It's more >> straight forward if you simply bookmark "recent changes". > > I believe a mailing list archive would give more confidence. For > example, since mailing list archives are mirrored externally (and even > on people's own local machine in their MUAs), they aren't affected by > power outages on a single web server, or remote alteration of history by > everyone who has access to that particular web server. If you'll write an email notification plugin for Trac, I'll deploy it. Otherwise Frank might know of a RSS-to-email gateway. As for the backup part, all the tools.ietf.org wikis are replicated to all the 3 tools servers every hour, so we don't have a single-point-of failure, exactly. Re-pointing the DNS in case of a crash will take a little time to propagate, of course (If someone wants to run a mirror of the content on the tools servers, or donate a machine to set up as an additional tools server, send me an email.) Henrik _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf