Updated some of the internal tech docs

diff --git a/citadel/techdoc/netconfigs.txt b/citadel/techdoc/netconfigs.txt
index 55434fb050bb0f208e8245793c1ab53ad667d722..8440f5db975ff288f3175407fc7f92b4f1a1ef13 100644 (file)
--- a/citadel/techdoc/netconfigs.txt
+++ b/citadel/techdoc/netconfigs.txt
@@ -66,8 +66,24 @@ timestamp, so that we may purge old records which were never confirmed.
  
  The sixth field is the URL of the web page used to enter the subscription
 request, minus any parameters.
  
  The sixth field is the URL of the web page used to enter the subscription
 request, minus any parameters.

+

  
  INSTRUCTION:  unsubpending
  SYNTAX:       unsubpending|friko@mumjiboolean.com|A234Z|1234567890|http://foo.com/lists
     Similar to the 'subpending' command, except this one is for unsubscribe
 requests.  The same rules apply with regard to the token and the web page.
  
  INSTRUCTION:  unsubpending
  SYNTAX:       unsubpending|friko@mumjiboolean.com|A234Z|1234567890|http://foo.com/lists
     Similar to the 'subpending' command, except this one is for unsubscribe
 requests.  The same rules apply with regard to the token and the web page.

+
+
+ INSTRUCTION:  participate
+ SYNTAX:       participate|list-addr@example.com
+   This allows a room to be a  *subscriber* to an external mailing list
+somewhere.  The room's email address should be subscribed to the list, and the
+external listserv should be told "do not send me my own messages."  Any
+messages which originated on Citadel (as opposed to messages which arrived via
+email, such as those from the list) will be sent to the list, with the display
+name of the author kept intact, but the email address changed to the address of
+the room.
+ 
+   This is somewhat finicky, which is why it is not officially supported, and
+why there are no facilities in the user interface to configure it.  If you want
+to use this option you are on your own.

diff --git a/citadel/techdoc/package-setup.txt b/citadel/techdoc/package-setup.txt
index 88362ac76677c074d1f55bb7c7bebda574a21829..ff60a6fec8be4ad82cfdd29ba14861f9d2c86b89 100644 (file)
--- a/citadel/techdoc/package-setup.txt
+++ b/citadel/techdoc/package-setup.txt
@@ -30,3 +30,6 @@ CREATE_XINETD_ENTRY   Set to "yes" to automatically configure xinetd to route
                        telnet connections into a Citadel client, if needed.
 
 SYSADMIN_NAME          Name of system administrator.
                        telnet connections into a Citadel client, if needed.
 
 SYSADMIN_NAME          Name of system administrator.

+
+NO_INIT_SCRIPTS                Set to non-null to suppress the creation of init
+                       scripts when running on a SysV-init based host.

diff --git a/citadel/techdoc/roadmap.txt b/citadel/techdoc/roadmap.txt
index f1827c6766d949b27066531d2b188d898eba1a1d..4a02d68db05ccc96f01a9e97cbd36eb09d57f5b1 100644 (file)
--- a/citadel/techdoc/roadmap.txt
+++ b/citadel/techdoc/roadmap.txt
@@ -8,29 +8,24 @@ some code and deciding what to work on.
 
 * GroupDAV and "webcal" (icalendar over dav) support
 * Updated schema for publishing Citadel address book data into an
 
 * GroupDAV and "webcal" (icalendar over dav) support
 * Updated schema for publishing Citadel address book data into an

-  external LDAP directory (still awaiting enterprise number from IANA)
+  external LDAP directory

 * Internationalization (WebCit is now available in several languages.)
 * Internationalization (WebCit is now available in several languages.)

+* Per-user auto-handling of inbound mail.  (Sieve + rules editor)
+

 
  Goals to achieve during the 7.xx cycle
  --------------------------------------
 
 
  Goals to achieve during the 7.xx cycle
  --------------------------------------
 

-* Aliases, virtual addresses, and distribution lists
-  (We ought to be able to handle all three of these using the same facility.)
-
-* CalDAV support (eventually -- since the protocol is so ugly and needlessly
-  complex, the draft authors are still arguing over small details -- once the
-  draft is finalized, we will implement enough of CalDAV to support the two
-  major client packages currently using it)
+* CalDAV support (Eventually.  Since both the protocol itself and the people
+  designing it are incredibly ugly, it keeps changing, and implementations
+  keep breaking.  When the spec is finalized, we will implement enough of
+  CalDAV to provide compatibility with any major client packages which use
+  it.)

 
 * Integration of CMS and social software features (more on this later).
 
 * Further internationalization (for example, in the citserver).
 
 
 * Integration of CMS and social software features (more on this later).
 
 * Further internationalization (for example, in the citserver).
 

-* Per-user auto-handling of inbound mail.  Simple handlers such as an "out
-  of office reply" should be easy for users to set up.  More complex handlers
-  such as the automatic sorting of inbound mail into various folders based
-  on sender, subject, etc. should also be possible.
-

 * Address books: build dialogs to integrate personal address books into
   mail recipient boxes, auto-completion, etc.  Use AJAX for this.
 
 * Address books: build dialogs to integrate personal address books into
   mail recipient boxes, auto-completion, etc.  Use AJAX for this.
 


@@ -90,4 +85,4 @@ some code and deciding what to work on.
   to other users, if they share it to others. it should do something like username/room
   where username should be a floor.
 
   to other users, if they share it to others. it should do something like username/room
   where username should be a floor.
 

-* webcit should be made more resistant to html injections, especialy the chat window.
\ No newline at end of file
+* webcit should be made more resistant to html injections, especialy the chat window.

diff --git a/citadel/techdoc/views.txt b/citadel/techdoc/views.txt
index 167e163e34459d7cfccb8c10a616151acf348f8b..2e127b28c67fdfede15b25cd60042e1eb8c5c1ab 100644 (file)
--- a/citadel/techdoc/views.txt
+++ b/citadel/techdoc/views.txt
@@ -1,5 +1,5 @@
-How "views" work in Citadel (beginning with v6.00)
---------------------------------------------------
+How "views" work in Citadel
+---------------------------

  
  There's no need to be rigid and stupid about how different rooms are presented
 in a Citadel client.  And we don't enforce things either.  But there's a need
  
  There's no need to be rigid and stupid about how different rooms are presented
 in a Citadel client.  And we don't enforce things either.  But there's a need