[[tron]] suggests that non-developers should be able to post content to a staging area, to be approved (possibly after editing) by developers. [[schmonz]] likes this idea a lot.
> what about to make a sub-page called e.g. User contributed documentation an give non-developers rw access there while editing other parts(TNF contributed) of wiki will require developers account or possible some sort of bless from a developer. --[[haad]]
_For non-developers using [[anonymous CVS|wiki/todo/push_wikisrc_to_anoncvs]]_: submit a diff to `netbsd-docs@`.
_For non-developers using a web browser_: the ikiwiki discussion subpage and/or [[!iki plugins/comments desc="comments plugin"]] may point toward the solution.
One of the reasons we [[chose ikiwiki|wiki/todo/choose_wiki_software]]
is the ability to edit via CVS
directly, as well as via the web. As long as every wiki editor is a
developer, controlling access consistently is simple. In order to open
up wiki editing to non-developers, we have to think carefully about
both the CVS case and the web case.
In the short term, to start getting non-developers involved, I intend
to [[push wikisrc to anoncvs]] and
[[hook up wiki commits to www-changes@]].
In the long term, ikiwiki has a few ready-made web authentication
options (a locally managed user database, OpenID, and HTTP auth), and
if they don't suffice for some reason, it's easy enough to write an
auth plugin. The hard part is deciding the workflow: where is a
sensible place for non-developers to make their edits, and what is a
sensible way for developers to review and "bless" the changes? Two
ikiwiki-native possibilities are listed above.
Ideas welcome! Edit this page and add your comments. --[[schmonz]]
One idea (which needs to be considered by board@):
7. Enable Discussion subpages.
7. Mark very clearly on the Discussion page template that content may
have been written by anyone at all and has not been vetted by any
member of TNF.
7. Enable the `anonok` plugin and set the `anonok_pagespec` to allow
anonymous editing of Discussion subpages (and of no other pages).
The resulting workflow:
7. Non-developer finds a page to which to suggest changes.
7. Non-developer edits its Discussion subpage and writes the suggested changes.
7. Developer who follows [[RecentChanges]] (or the commit mails) notices the changes.
7. If the changes aren't acceptable, developer edits the Discussion subpage and explains why not.
7. If the changes are acceptable, developer applies them to the page and removes them from the Discussion subpage.
> This can be work flow for a TNF contributed pages but as I said above this is not acceptable for as normal wiki workflow. We had almost similar discussion about comments on a blog software for NetBSD. There were developers who thought that there will be too many comments and we do not have man power to read/approve them all. After setting blog we have found that we have barely 1-2 comments in every third article. I don;t thing that there will be too many real editors on our wiki from non-developers and therefore we need to make it easy not hard to do. --[[haad]]
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb