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