2009/1/21 Petko Yotov <[email protected]>: >> Eemeli Aro wrote: >> > Ummm, why not Cookbook.RecipeName? Then the names and contents could >> > be kept identical with what's on pmwiki.org. You could then add a >> > default Cookbook.Cookbook page much like the one on pmwiki.org to >> > provide an index for any included documentation. > > What about sites that are about food and cooking, they need a wiki > group "Cookbook"? > > Or even sites about other software that provide configuration examples like we > do in our, so called "Cookbook"?
Good point, but still: are there actually any? A bit of googling didn't give me any conflcts except for <http://www.thewomenscollege.com.au/pmwiki/pmwiki.php/Main/Cookbook>, and even that one's a bit of a stretch, as even there having a Cookbook group wouldn't actually disturb anything. In other words, I'll accept the argument if you (or someone else?) can give me at least a couple of examples. Going outside PmWiki, <http://en.wikibooks.org/wiki/Cookbook> could be seen as a conflict, except that they of course use MediaWiki. As for your second argument, I'm similarly sceptical that there exist actual real-life conflicts with this. To summarise my thoughts, I'd argue that the meaning of "cookbook" in the context of a PmWiki environment is sufficiently unambiguous for it to be used as the parent group for cookbook recipes. And to be honest, I'm taking a rather academic point of view to the whole issue as I agree that it makes very little sense to maintain local copies of the documentation as they're so easily available via pmwiki.org or if that fails (which it never has for me), an archive.org search for the appropriate page. eemeli _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
