[pmwiki-users] PmWiki Magazine proposed Submission/Approval Process

[Patrick R. Michaud]

On Sat, Sep 30, 2006 at 09:01:37PM -0500, Ben Wilson wrote:
> It sounds like we're almost to the point of having a "Draft"
> permission level, which is somewhere between "Read" and "Edit." In
> addition to the "Comment," which sounds like it's a permission in the
> same ballpark. Should we expect permissions to be (in decending order)
> Admin, Edit, Draft, Comment, Read? 

Just to avoid potential future confusion...

I don't think of permission levels as having an intrinsic "order"
to them as implied here, nor does PmWiki implement them that way.
For example, just because someone has permission to add comments
to a page doesn't automatically imply they can read it.  (Consider
the case where comments are stored separately from the page being
commented upon.)

Also, "draft" doesn't sound to me like a separate permission level,
if we need something like this, then it likely will be handled 
in terms of edit permissions on the "-Draft" pages.  But I'm
still mulling this over (and PmWikiPhilosophy #3 applies here).

Essentially, PmWiki's core permission levels will be read, edit, 
insert (comment), upload, attr, and admin.  
  - anyone with admin permission can do anything
  - if a page doesn't have an edit password, it uses the read password
  - if a page doesn't have an insert password, it uses the edit password
  - if a page doesn't have an attr password, it uses the edit password

It might look to many that this has "insert" and "edit" backwards --
i.e., that "edit should be a higher level than insert".  But I think
this is contrary to what authors will expect.  If as a page author
I put an edit password on a page, I don't expect people to be able
to later sneak content into the page by using ?action=insert or 
?action=comment.

Pm