Annotation of wikisrc/wiki/todo/let_non-developers_contribute_content.mdwn, revision 1.7
1.3 wiki 1: [[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.
1.1 wiki 2:
1.7 ! wiki 3: [[haad]] 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.
1.3 wiki 5: _For non-developers using [[anonymous CVS|wiki/todo/push_wikisrc_to_anoncvs]]_: submit a diff to `netbsd-docs@`.
1.1 wiki 6:
1.3 wiki 7: _For non-developers using a web browser_: the ikiwiki discussion subpage and/or [[!iki plugins/comments desc="comments plugin"]] may point toward the solution.
9: One of the reasons we [[chose ikiwiki|wiki/todo/choose_wiki_software]]
10: is the ability to edit via CVS
11: directly, as well as via the web. As long as every wiki editor is a
12: developer, controlling access consistently is simple. In order to open
13: up wiki editing to non-developers, we have to think carefully about
14: both the CVS case and the web case.
16: In the short term, to start getting non-developers involved, I intend
17: to [[push wikisrc to anoncvs]] and
18: [[hook up wiki commits to www-changes@]].
20: In the long term, ikiwiki has a few ready-made web authentication
21: options (a locally managed user database, OpenID, and HTTP auth), and
22: if they don't suffice for some reason, it's easy enough to write an
23: auth plugin. The hard part is deciding the workflow: where is a
24: sensible place for non-developers to make their edits, and what is a
25: sensible way for developers to review and "bless" the changes? Two
26: ikiwiki-native possibilities are listed above.
28: Ideas welcome! Edit this page and add your comments. --[[schmonz]]
1.4 wiki 29:
1.5 wiki 30: One idea (which needs to be considered by board@):
1.4 wiki 31:
32: 7. Enable Discussion subpages.
33: 7. Mark very clearly on the Discussion page template that content may
34: have been written by anyone at all and has not been vetted by any
35: member of TNF.
1.6 wiki 36: 7. Enable the `anonok` plugin and set the `anonok_pagespec` to allow
37: anonymous editing of Discussion subpages (and of no other pages).
1.4 wiki 38:
39: The resulting workflow:
41: 7. Non-developer finds a page to which to suggest changes.
42: 7. Non-developer edits its Discussion subpage and writes the suggested changes.
43: 7. Developer who follows [[RecentChanges]] (or the commit mails) notices the changes.
44: 7. If the changes aren't acceptable, developer edits the Discussion subpage and explains why not.
45: 7. If the changes are acceptable, developer applies them to the page and removes them from the Discussion subpage.
1.7 ! wiki 46:
! 47: [[haad]] 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.
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb