gzz-commits
[Top][All Lists]
Advanced

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

[Gzz-commits] gzz/doc/pegboard/projectsplit--tjl peg.rst


From: Tuomas J. Lukka
Subject: [Gzz-commits] gzz/doc/pegboard/projectsplit--tjl peg.rst
Date: Wed, 19 Feb 2003 13:39:13 -0500

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Tuomas J. Lukka <address@hidden>        03/02/19 13:39:13

Modified files:
        doc/pegboard/projectsplit--tjl: peg.rst 

Log message:
        More about splitting

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/projectsplit--tjl/peg.rst.diff?tr1=1.3&tr2=1.4&r1=text&r2=text

Patches:
Index: gzz/doc/pegboard/projectsplit--tjl/peg.rst
diff -u gzz/doc/pegboard/projectsplit--tjl/peg.rst:1.3 
gzz/doc/pegboard/projectsplit--tjl/peg.rst:1.4
--- gzz/doc/pegboard/projectsplit--tjl/peg.rst:1.3      Wed Feb 19 13:30:22 2003
+++ gzz/doc/pegboard/projectsplit--tjl/peg.rst  Wed Feb 19 13:39:13 2003
@@ -4,8 +4,8 @@
 =============================================================
 
 :Author:   Tuomas J. Lukka
-:Last-Modified: $Date: 2003/02/19 18:30:22 $
-:Revision: $Revision: 1.3 $
+:Last-Modified: $Date: 2003/02/19 18:39:13 $
+:Revision: $Revision: 1.4 $
 :Status:   Incomplete
 
 Issues
@@ -53,6 +53,18 @@
 
 - What should be the names of the new projects?
 
+- Who will have what powers in the new packages?
+
+    RESOLVED: Each package will have its own maintainer
+    who will act as the "enlightened tyrant" of the package,
+    having final say on PEGs for that package etc.
+    This is a great responsibility and needs to be distributed;
+    currently too much is in the hands of one person.
+    
+    The different packages and their goals and maintainers
+    will hopefully clarify the goals and have the decisionmakers
+    close to the actual work..
+
 Changes
 =======
 
@@ -73,7 +85,12 @@
 
 All projects shall continue using the PEG style process for
 frozen APIs; this is especially important since now others may
-begin to rely on those APIs.
+begin to rely on those APIs. However, PEG 201 shall be changed
+so that 
+
+The initial dependency structure is shown in the diagram below.
+There *may* be at least one more package needed, for example if
+the same classes in ``gzz.util`` are used by more than one package.
 
 ..  UML:: projectsplitting
 
@@ -109,6 +126,7 @@
     .5[Storm.c, LibPaper.c] = .5[UMLLinker.c, 
TheCoreProjectThatHasNoNameYetButIsTheRealOverallGoal.c];
     Storm.c = LibVob.c + (0, 300);
 
+The packages are briefly detailed below, with their maintainers.
 
 ---------
 UMLLinker
@@ -195,6 +213,7 @@
 - Figure out the new structure
 
 - Write the code to make use of the new structure
+
 
 
 




reply via email to

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