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

Kathryn Andersen kat_lists at katspace.homelinux.org
Mon Oct 2 08:12:31 CDT 2006


On Mon, Oct 02, 2006 at 01:38:28PM +0100, Am?rico Albuquerque wrote:
> Patrick R. Michaud wrote:
> > 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? 
> > 
> I might be mixing things a little but it seams to me that a comment is 
> something you do outside of a page.

What has been said before, and now needs to be said again, PM is writing
the comment facility so that comments can *either* be in a separate page
(which might have some naming convention like MyPage-Comments, but
doesn't have to) OR comments can be added to the content of the page,
and not only that, but they can be *inserted* into a page, rather than
being limited to being appended to the end of a page.

This is because PM is generous and wants us to have maximum flexibility.

> The comments normally doesn't appear 
> on the main text but on a separated page.

It *may*.  It doesn't have to.

> > 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.)
> Actually is does exactly that. How can you comment something you haven't 
> red before?

The point being made here is that the configuration is so flexible that
the wiki administrator can set permissions completely arbitrarily --
even when those permissions would seem to be illogical.
 
> > 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
> > 
> Again I say that comment is not the same as insert. When I'm commenting 
> a page, my comments become read-only. Insert means the person with edit 
> permissions can change what was inserted. This means that an author can 
> later change a comment that he/she doesn't like

Which can be done now, with any of the comment recipes.  Edit permission
is edit permission, I don't think we want to start trying to tangle with
the kind of mess that this sort of "frozen" permissions would give.
 
That isn't to say that one couldn't do what you desire above for
commenting -- the proposed system is flexible enough that you *could*
set it up like that(*), but it doesn't have to be the only way that it's
done.

(*) So far as I can see, from what PM has said about the new commenting
facility which he's going to put into 2.2, in order to have this
"comments can never be deleted or edited" setup, you would do the
following:
- put a commentbox in the page which appends comments to
  {*$FullName}-Comments (the comments page for this page)
- set the permissions on the -Comments page so that it can only be
  appended to, and not edited by anybody.

Thus the original author of MyPage can still edit MyPage, but nobody can
edit MyPage-Comments.

If you wanted to set it up so that every page in a group had a
corresponding comments page, and you didn't want to have to set the
permissions by hand for each page -- can one set permissions with
wildcards?  Otherwise, one could make a "comments" group matching that
group, and take advantage of group-wide configuration, like so:
- put a commentbox in MyGroup.GroupFooter (or MyGroup.GroupHeader,
  depending on which you prefer) where the comments are directed to
  MyGroup-Comments.{*$Name}
- set the permissions in local/MyGroup-Coments.php so that nobody has
  edit permission, only insert permission, for all pages in that group.

PmWiki is wonderfully flexible.

Kathryn Andersen
-- 
 _--_|\     | Kathryn Andersen	<http://www.katspace.com>
/      \    | 
\_.--.*/    | GenFicCrit mailing list <http://www.katspace.com/gen_fic_crit/>
      v     | 
------------| Melbourne -> Victoria -> Australia -> Southern Hemisphere
Maranatha!  |	-> Earth -> Sol -> Milky Way Galaxy -> Universe




More information about the pmwiki-users mailing list