[ZDP] BackTalk to Document Zope Developer's Guide (2.4 edition)/Appendix A - Zope Core Permissions

[webmaster at zope.org]

A comment to the paragraph below was recently added via http://zope.org/Documentation/Books/ZDG/current/AppendixA.stx#1-0

---------------

  This is a list of standard permissions included with Zope. It is a
  good idea to use these permissions when applicable with your Zope
  products, rather than creating new ones.

    % mcdonc - June 11, 2002 6:46 pm:
     The Copy or Move permission was added as of 2.6. If you revoke the Copy and Move permission from a role
     respective to an object, even if a user has "View management screen" permissions, he or she will not be able
     to copy or move the object.

    % Anonymous User - Dec. 20, 2002 1:15 pm:
     I don't mean to bitch, but the following list is absolutely unnecessary. Every permission seems to be defined
     by quoting the permission and adding 'object' or the like. To me, this list contains no information.
     Couldn't you put longer descriptions and examples for each right?

    % Anonymous User - Dec. 20, 2002 1:20 pm:
     I'd rather just remove the chapter if it becomes more than this. Right now I can't maintain it. If someone
     else wanted to do this and keep it up to date, I'd be fine with it. -- chrism

    % proton - May 9, 2003 7:14 am:
     Sorry, Anon, "the following list" is absolutely NECESSARY. Yes, the descriptions are a little skimpy, but the
     whole reason I found this page was that I needed to see the ENTIRE list of permissions without being filtered
     by type. (i.e. if I go to the Zope management interface, I see only the permissions that apply to the type of
     object that I've selected.)
     Perhaps the page could be automatically generated from the Python source? I'd like to see a table-oriented
     display: name of permission, object types it applies to, 1-sentence description, and "warnings / gotchas /
     special notes."

    % Anonymous User - June 21, 2004 12:22 pm:
     This page needs expansion. I'm not a believer in "self-documentation", so administrators need to be able to
     know for sure what security settings they're putting on a page. Yes, we could check the source. . .or we
     could use a product that tells us what we're dealing with. I like the security model, the permission layering
     is great, but we need a bit more info.

    % Anonymous User - June 21, 2004 12:27 pm:
     This page needs expansion. I'm not a believer in "self-documentation", so administrators need to be able to
     know for sure what security settings they're putting on a page. Yes, we could check the source. . .or we
     could use a product that tells us what we're dealing with. I like the security model, the permission layering
     is great, but we need a bit more info.