gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/storm article.rst


From: Toni Alatalo
Subject: [Gzz-commits] manuscripts/storm article.rst
Date: Sat, 15 Feb 2003 12:19:59 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo <address@hidden>   03/02/15 12:19:59

Modified files:
        storm          : article.rst 

Log message:
        the to-which-zone-new-blocks issue

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/article.rst.diff?tr1=1.180&tr2=1.181&r1=text&r2=text

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.180 manuscripts/storm/article.rst:1.181
--- manuscripts/storm/article.rst:1.180 Sat Feb 15 12:17:15 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 12:19:59 2003
@@ -1110,7 +1110,10 @@
 
 Besides these issues with the backend, we are facing user interface issues
 as well -- for example the conventions for listing, moving and deleting
-blocks.
+blocks. Also conventions for which zones e.g. new blocks should be stored in
+must be resolved. Often they will be private, but when making changes to
+documents that are shared with a project group, the changes should be
+visible to others.
 
 We have provided a case study in
 what's possible in a system that does not use




reply via email to

[Prev in Thread] Current Thread [Next in Thread]