[Zope3-checkins] CVS: Zope3/doc - TODO.txt:1.7

[Fred L. Drake, Jr.]

Update of /cvs-repository/Zope3/doc
In directory cvs.zope.org:/tmp/cvs-serv12400

Modified Files:
	TODO.txt 
Log Message:
- remove completed item
- added additional notes, fixed typos


=== Zope3/doc/TODO.txt 1.6 => 1.7 ===
--- Zope3/doc/TODO.txt:1.6	Thu Jun 26 11:31:35 2003
+++ Zope3/doc/TODO.txt	Thu Jun 26 13:27:42 2003
@@ -10,10 +10,6 @@
 - Write documentation on how to develop principal sources for the
   pluggable auth service.
 
-- Fill out an authentication service based on the architecture
-  that Itamar came up with in Rotterdam. See
-  src/zope/app/services/auth.txt. 
-
 - Redo local Role service to use configurations
 
 - Implement a local permission service (using configurations)
@@ -22,6 +18,9 @@
   the fact that people will likley plug in different grant and
   owndership systems for different security policies.
 
+  o Document the relationship between the security policy and the
+    grants
+
 - Untrusted modules.  Also implement a way of
   specifying policies for trusted and untrusted modules.
   At a minimum:
@@ -70,17 +69,21 @@
 
 - Software bundles.
 
-- zcml directives for module security
+- ZCML directives for module security
+
+  o Fix the ++module++ namespace to honor security assertions
 
-- zcml directive for layers and corresponding checks that a resource is 
+- ZCML directive for layers and corresponding checks that a resource is 
   registered in a registered layer
 
-- local module service. This provides support for local imports
-  as well as a place to manage security configuration for
-  persistent modules.
+  o Typos can cause new layers to be defined unintentionally
 
-  Provide support for within package access to persistent
-  modules without the need to register them.
+- Local module service. This provides support for local imports as
+  well as a place to manage security configuration for persistent
+  modules.
+
+  Provide support for within package access to persistent modules
+  without the need to register them.
 
 - Rework undo
 
@@ -98,6 +101,8 @@
 
 - Implement interface types, and thus content types.
 
+  o Categories?  (Not inheritable.)
+
 - Local Interface service
 
   This service should support:
@@ -145,7 +150,7 @@
 
 - Broken-object support
 
-  When an object cannot beunpickled because it's class can't be found, 
+  When an object cannot be unpickled because it's class can't be found, 
   it should be converted to a special kind of immutable object.  
 
   See http://collector.zope.org/Zope3-dev/109
@@ -155,7 +160,6 @@
 
   What form should these take? Should they be like Zope 2 Python
   scipts? or should they by like Python modules.
-
 
 - Supply a generic property mechanism?