Jeremy White wrote:
I'm willing to move every simple textual (static content) page from the website to the Wiki and link from the website to the corresponding pages.
I think this is a bad idea.
The current system ensures that changes to the core parts of WineHQ are reviewed before being made, whereas a Wiki can allow things to change willy-nilly, often reflecting the views of the last person to touch a page, rather than a consensus.
OTOH, the current system seems to ensure that many parts of WineHQ are very outdated.
Isn't there a compromise where Wiki's upfront editing capabilities can be used to ensure up-to-date, dynamic content while you also make sure that nobody wrecks the pages?
I'm no wiki expert, but it seems like an obvious solution to have the pages editable only by a certain class of users. People wanting to edit something could then just ask for edit access for certain pages for correcting this or that on wine-devel and be granted those privileges on a case-by-case basis.
Or is that simply impossible..