Add permissions for suggesting/accepting edits

[danny.piccirillo@…]

Wikis are great tools for collaborative content of all types, but the choice for website creators who want a level of collaboration seem to have to choose between a static website, a wiki that anyone (or all members) can edit, or an overkill customized web app.

A simple innovation that needs to propagate through wiki software is adding the ability to suggest edits and accept those edits. Perhaps you want a wiki that anyone can suggest and edit, but only registered users can edit freely or accept edits. Or you want anyone, including members, to only be able to suggest edits, and only have moderators able to approve edits and edit freely. Etc, etc.

[Christian Boos]

Interesting idea, though it could quickly lead to inconsistencies if you don't review quickly the edits one by one (multiple pending edits that lead to conflicts once you start applying them).

Unfortunately, that seems to be clearly out of scope of core Trac. In core Trac, you already have the possibility to flag some pages as "read-only", and then people can just create tickets for suggesting edits (that's what happening here, even sometimes for pages which are not read-only ;-) ). With custom policies, you can even handle fine grained permissions (see for example PublicWikiPolicy​).

(please don't set arbitrary milestones - see NewTicketGuidelines#HowtoProceed on the matter)

[Remy Blank]

Not to mention that once we have the wiki in a DVCS, all the corresponding workflows will become possible (pull requests, etc).