[pypy-svn] rev 1778 - in pypy/trunk/doc/funding: . makedoc

[tismer at codespeak.net]

Author: tismer
Date: Sun Oct 12 17:07:14 2003
New Revision: 1778

Modified:
   pypy/trunk/doc/funding/B4.resources.txt
   pypy/trunk/doc/funding/makedoc/makedoc.py
   pypy/trunk/doc/funding/makedoc/part_b.pdf
   pypy/trunk/doc/funding/makedoc/part_b.sxw
Log:
small format corrections. Built a new PDF

Modified: pypy/trunk/doc/funding/B4.resources.txt
==============================================================================
--- pypy/trunk/doc/funding/B4.resources.txt	(original)
+++ pypy/trunk/doc/funding/B4.resources.txt	Sun Oct 12 17:07:14 2003
@@ -363,12 +363,12 @@
 
 We are pioneers of a software development method, Sprint Driven 
 Development,  which promises to mobilise people in a unique and
-special way.  We outline _what_ we do in Section 5 -- Project
-Management.  Here we would only like to speak briefly of _one 
-reason why we do this_.
+special way.  We outline *what* we do in Section 5 -- Project
+Management.  Here we would only like to speak briefly of *one 
+reason why we do this*.
 
 One of the classics of  software management is Fred Brooks
-_The Mythical Man Month_.  FIXME how do we do references?
+*The Mythical Man Month*.  FIXME how do we do references?
 
 In it he asserts:
 'Adding people to a late software project makes it later'.  This is
@@ -380,13 +380,13 @@
 
 Sprint Driven Development is an attempt to make a development
 model which refutes this claim.  What would you get if you didn't
-have to 'bring people up to speed' because _they were already
-aware of the project_?  If you published everything you were doing
+have to 'bring people up to speed' because *they were already
+aware of the project*?  If you published everything you were doing
 and made constant efforts to communicate where you were, and why
 you were doing things to the base of programmers you might
-_someday_ like to have on your project, then when time came to
+*someday* like to have on your project, then when time came to
 add people to the late project (or just because the project
-reached a point where there _was_ comparatively more work that
+reached a point where there *was* comparatively more work that
 could be shared among programmers) they would already be mostly
 ready to go.
 
@@ -449,6 +449,7 @@
 
 Project acronym -
 
+::
 
             Short Names                       
 	    Partner 1         

Modified: pypy/trunk/doc/funding/makedoc/makedoc.py
==============================================================================
--- pypy/trunk/doc/funding/makedoc/makedoc.py	(original)
+++ pypy/trunk/doc/funding/makedoc/makedoc.py	Sun Oct 12 17:07:14 2003
@@ -80,7 +80,7 @@
     "empty",
     "",
     "fake sublevel3",
-    "+++++++++++++++",
+    "::::::::::::::::",
     "empty",
     "",
     ":DELETE:END",

Modified: pypy/trunk/doc/funding/makedoc/part_b.pdf
==============================================================================
Binary files. No diff available.

Modified: pypy/trunk/doc/funding/makedoc/part_b.sxw
==============================================================================
Binary files. No diff available.