Index: openacs-4/packages/dotlrndoc/www/doc/detailed-todo.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrndoc/www/doc/Attic/detailed-todo.adp,v
diff -u -N -r1.7 -r1.8
--- openacs-4/packages/dotlrndoc/www/doc/detailed-todo.adp	11 Nov 2001 20:57:14 -0000	1.7
+++ openacs-4/packages/dotlrndoc/www/doc/detailed-todo.adp	29 Nov 2001 02:17:34 -0000	1.8
@@ -6,7 +6,7 @@
 This document details the precise steps in moving forward with dotLRN development.
 
 <p>
-<small>Last update: $Id$</small>
+<font size=-2>Last update: $Date$</font>
 <p>
 
 <h3>Things to Do</h3>
@@ -15,29 +15,19 @@
 <P>
 Now:
 <ul>
-<strike>
-<li> impliment dotlrn-news and news-portlet
-<li> impliment theme change in portal::config
-<li> add buttons to "red box" theme
-<li> impliment "unshade" icons in both themes
-</strike>
+Check left-to-finish core
 </ul>
 
 Later:
 <ul>
-<li> add optional theme_id args to portal::render
-<li> edit calendar_portlet::show for different views - ugly!
-<li> acs-service-contract
-<li> impliment dotlrn-survey and survey-portlet
-<li> overview of file-storage - think about UI improvements
 </ul>
 
 <p>
 
 <b>Ben</b>:
 <ul>
-<li> data model for dotLRN workspace
-<li> updates to applet interface as a result
+<li> <strike>data model for dotLRN workspace</strike>
+<li> <strike>updates to applet interface as a result</strike>
 <li> managing classes, profs, etc...
 </ul>
 
@@ -140,6 +130,14 @@
 <strike><li> "available" portlets: data-model, Tcl API, and web pages</strike>
 <strike><li> implement shade, remove, edit, link from title</strike>
 
+<strike>
+<li> impliment dotlrn-news and news-portlet
+<li> impliment theme change in portal::config
+<li> add buttons to "red box" theme
+<li> impliment "unshade" icons in both themes
+<li> add optional theme_id args to portal::render
+<li> edit calendar_portlet::show for different views - ugly!
+</strike>
 </ul>
 
 
Index: openacs-4/packages/dotlrndoc/www/doc/index.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrndoc/www/doc/index.adp,v
diff -u -N -r1.4 -r1.5
--- openacs-4/packages/dotlrndoc/www/doc/index.adp	25 Oct 2001 19:51:51 -0000	1.4
+++ openacs-4/packages/dotlrndoc/www/doc/index.adp	29 Nov 2001 02:17:34 -0000	1.5
@@ -6,6 +6,7 @@
 <ul>
 <li> <a href=schedule.adp>Schedule</a>
 <li> <strong><a href=detailed-todo.adp>Detailed TODO</a></strong>
+<li> <strong><a href=left-to-finish-core.adp>TODO to finish core</a></strong>
 <p>
 <li> <a href=nomenclature.adp>Nomenclature</a>
 <li> <a href=permission-overview.adp>Roles, Sections, and Permissions</a> | <a href=permission-api.adp>Permission API</a>
Index: openacs-4/packages/dotlrndoc/www/doc/left-to-finish-core.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrndoc/www/doc/Attic/left-to-finish-core.adp,v
diff -u -N -r1.2 -r1.3
--- openacs-4/packages/dotlrndoc/www/doc/left-to-finish-core.adp	14 Nov 2001 19:40:25 -0000	1.2
+++ openacs-4/packages/dotlrndoc/www/doc/left-to-finish-core.adp	29 Nov 2001 02:17:34 -0000	1.3
@@ -10,39 +10,64 @@
 
 <h3>Portal</h3>
 <ul>
-<li> Adjust buttons on portlets as a function of capabilities
 <li> Implement portlet locking capability.
 <li> Implement cloning stuff.
+<li> <strike>Clean up UI on configuration page (change backlink)</strike>
+<li> add roles and permissions (admin create|delete)(from dotlrn_community API)<li> code review (Wednesday, 11/21, 2pm).
+<strike>
+<li> change theme data model to map to pages.
 <li> Refactor some functionality as part of base portal package.
-<li> Clean up UI on configuration page (change backlink)
 <li> add acs-service-contract support.
-<li> change theme data model to map to pages.
-<li> add roles and permissions (admin create|delete)
-     (from dotlrn_community API).
+<li> update all portlets for datasource.new, user_editable_p, shadeable_p, hideable_p, sc, new procs
+<li> Adjust buttons on portlets as a function of capabilities
 <li> Remove render-element.tcl ::get_pretty_name other render cleanup
-<li> Params issues
-<li> code review (Monday, 11/19, 10am-12pm).
+</strike>
+
 </ul>
 
 <h3>dotLRN Core</h3>
 <ul>
 <li> Review exactly what the roles are
 <li> Write up permissions procs!
-<li> Move administration to community-specific pages! Duh!
+<li> <strike>Move administration to community-specific pages! Duh!</strike>
 <li> Allow for addition of users who haven't registered yet? Check that.
 <li> Automatically redirect single-community guests to the right location.
-<li> Fix registration/deregistration bugs!
+<li> <strike>Fix registration/deregistration bugs!</strike>
 <li> Get clubs working
 <li> !! Figure out Relational Segments !!
 </ul>
 
+<h3>Operations</h3>
+<ul>
+<li> prepare staging server:
+<ul>
+<li> <strike>AOLserver 3.3ad13</strike>
+<li> <strike>Oracle 8.1.7</strike>
+<li> <strike>drivers</strike>
+<li> 
+</ul>
+<li> review existing SloanSpace site
+</ul>
+
+<p>
+
 <h3>calendar</h3>
 <ul>
 <li> make group calendar work!
 <li> each user has *ONE* personal calendar, and has access to each community calendar.
 <li> calendar works as multi-package view in portlet.
 </ul>
 
+<b>how this works</b>
+
+<ul>
+<li> part of this involves figuring out multiple values for single parameters (instance_id in particular).
+<li>every user has only ONE personal calendar
+<li>every community has only ONE community calendar
+<li>when a user views a community-specific page, he/she only sees that community's event.
+<li>on personal calendar, they see everything
+</ul>
+
 <h3>bboard</h3>
 <ul>
 <li> test a bit more
@@ -60,7 +85,7 @@
 
 <h3>FAQ</h3>
 <ul>
-<li> Clean up portlet UI (display list of FAQs)1
+<li> Clean up portlet UI (display list of FAQs)
 </ul>
 
 <h3>News</h3>
Index: openacs-4/packages/dotlrndoc/www/doc/permission-api.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrndoc/www/doc/permission-api.adp,v
diff -u -N -r1.1 -r1.2
--- openacs-4/packages/dotlrndoc/www/doc/permission-api.adp	24 Oct 2001 23:30:53 -0000	1.1
+++ openacs-4/packages/dotlrndoc/www/doc/permission-api.adp	29 Nov 2001 02:17:34 -0000	1.2
@@ -9,6 +9,45 @@
 
 <p>
 
+<h3>Relational Segments & Context IDs</h3>
+
+In order to make things much cleaner with respect to permissions, we
+use relational segments and context IDs. The goal of relational
+segments will be to determine groups of users to whom permissions
+are granted. The goal of context IDs will be to create a hierarchy of
+objects so that as new components are added to subcommunities,
+permissions are naturally extended in appropriate ways.
+
+<p>
+
+For this to work, the actual privileges used throughout dotLRN and all
+of its modules must be <b>consistent</b>. Since permissions follow an
+inheritance path, we must make sure everything bootstraps off the
+basic read, write, create, delete, admin privileges.
+
+<p>
+
+To better explain the situation, we want the following to happen:
+<ul>
+<li> Hal is a member of "Intro to Computer Science Spring 2002" group, with relationship
+type <tt>dotlrn_instructor_rel</tt> to that group.
+<li> An FAQ about the Computer Science Program is created for "Intro
+to Computer Science Spring 2002", with <tt>context_id</tt> pointing to
+the course.
+<li> A relational segment "Intro to CS Spring 2002 Instructors" is
+created on the "Intro to CS Spring 2002" group and
+<tt>dotlrn_instructor_rel</tt> relationship type.
+<li> The privilege <tt>faq_admin</tt> exists, inheriting from
+the core OpenACS <tt>admin</tt> privilege.
+<li> A permission is granted: "Intro to CS Spring 2002 Instructors"
+are given the <tt>admin</tt> privilege on the course "Intro to
+CS Spring 2002".
+<li> <b>Thus</b>, automatically, Hal has the right to admin the FAQ,
+because the admin privilege translates to the faq_admin privilege by
+inheritance, Hal is part of the relational segment in question, and
+the FAQ in question has a context_id pointing to the course. It's BEAUTIFUL!
+</ul>
+
 <h3>General Roles API</h3>
 
 These are fairly straight-forward: