Diff for /wikisrc/wiki/todo/let_non-developers_contribute_content.mdwn between versions 1.8 and 1.9

version 1.8, 2009/12/23 15:36:02 version 1.9, 2009/12/26 15:57:22
Line 1 Line 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.  [[tron]] suggests that non-developers should be able to post content
   to a staging area, to be approved (possibly after editing) by
 > 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]]  developers. [[schmonz]] likes this idea a lot.
   
 _For non-developers using [[anonymous CVS|wiki/todo/push_wikisrc_to_anoncvs]]_: submit a diff to `netbsd-docs@`.  > what about to make a sub-page called e.g. User contributed
   > documentation an give non-developers rw access there while editing
 _For non-developers using a web browser_: the ikiwiki discussion subpage and/or [[!iki plugins/comments desc="comments plugin"]] may point toward the solution.  > 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]]  One of the reasons we [[chose ikiwiki|wiki/todo/choose_wiki_software]]
 is the ability to edit via CVS  is the ability to edit via CVS directly, as well as via the web.
 directly, as well as via the web. As long as every wiki editor is a  As long as every wiki editor is a developer, controlling access
 developer, controlling access consistently is simple. In order to open  consistently is simple. In order to open up wiki editing to
 up wiki editing to non-developers, we have to think carefully about  non-developers, we have to think carefully about both the CVS case
 both the CVS case and the web case.  and the web case.
   
 In the short term, to start getting non-developers involved, I intend  In the short term, to start getting non-developers involved, I intend
 to [[push wikisrc to anoncvs]] and  to [[push wikisrc to anoncvs]] and
Line 39  anonymous editing of Discussion subpages Line 47  anonymous editing of Discussion subpages
 The resulting workflow:  The resulting workflow:
   
 7. Non-developer finds a page to which to suggest changes.  7. Non-developer finds a page to which to suggest changes.
 7. Non-developer edits its Discussion subpage and writes the suggested changes.  7. Non-developer edits its Discussion subpage and writes the suggested
 7. Developer who follows [[RecentChanges]] (or the commit mails) notices the changes.  changes.
 7. If the changes aren't acceptable, developer edits the Discussion subpage and explains why not.  7. Developer who follows [[RecentChanges]] (or the commit mails)
 7. If the changes are acceptable, developer applies them to the page and removes them from the Discussion subpage.  notices the changes.
   7. If the changes aren't acceptable, developer edits the Discussion
 > 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]]  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]]

Removed from v.1.8  
changed lines
  Added in v.1.9


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb