erp5.zope: Disable ownership checking.

stack/erp5/buildout.cfg

@@ -203,7 +203,7 @@ md5sum = 1cb9160482a6be615c34dbc55b017dce
 [template-zope-conf]
 < = download-base
 filename = zope.conf.in
-md5sum = b54344ee94519f7e95e270664ba3dc99
+md5sum = 5ad1664a39fbab5f8450c7fb36c81945
 
 [template-my-cnf]
 < = download-base

stack/erp5/zope.conf.in

@@ -3,6 +3,14 @@
 %define INSTANCE {{ instance }}
 instancehome $INSTANCE
 zserver-threads {{ parameter_dict['thread-amount'] }}
+# When ownership checking is enabled, the roles a script runs as are the
+# intersection between user's roles and script owner's roles. This means
+# that revoking a code author's access to the system prevent all scripts
+# owned by that user from being of much use.
+# This is not how ERP5 approaches development: Managers write code,
+# Managers must be trustable and trusted, and their past work should not be
+# revoked when their account is terminated.
+skip-ownership-checking true
 
 lock-filename {{ parameter_dict['lock-file'] }}
 pid-filename {{ parameter_dict['pid-file'] }}