Differences

This shows you the differences between two versions of the page.

--- clean_permissions [2018/11/14 21:14] – external edit 127.0.0.1
+++ clean_permissions [2018/11/28 13:51] (current) – Struct data changed splitbrain
@@ Line 1: / Line 1: @@
-===== Clean Permissions =====
+====== Clean Permissions ======
 The Clean Permissions pattern is to set up an authorization system that is easy for wanted users to use and understand, while minimizing the amount of trashing and other forms of revertable grief from the unwanted.
-==== Usage ====
+===== Usage =====
 Post a clear explanation of the permission model prominently on the wiki. For each action requiring authorization, make sure a clear explanation of the authorization criteria is easily accessible.
-==== Example ====
+===== Example =====
-The original c2.com wiki has a clear and detailed discussion of its [[Permission+Granted|Permission Granted]] scheme and why it works for them.
+The original c2.com wiki has a clear and detailed discussion of its [[Permission Granted]] scheme and why it works for them.
-==== Related Patterns ====
+===== Related Patterns =====
-  * At the current state of the wiki art, probably the two most common clean permission schemes are [[Permission+Granted|Permission Granted]] and [[Community+Write+Permission|Community Write Permission]] .
+  * At the current state of the wiki art, probably the two most common clean permission schemes are [[Permission Granted]] and [[Community Write]] .
-  * [[Registration+Required|Registration Required]] is an anti-pattern, subject to abuse by the bad guys yet a hassle for the good guys.
+  * [[Registration Required]] is an anti-pattern, subject to abuse by the bad guys yet a hassle for the good guys.
-==== Further Reading ====
+===== Further Reading =====
   *  [[http://www.amazon.com/dp/020171499X/|The Wiki Way: Quick Collaboration on the Web]]  Bo Leuf and Ward Cunningham
@@ Line 23: / Line 23: @@
 ---- struct data ----
+classification.type  : Pattern
+classification.focus : Adoption
 ----