[pypy-svn] rev 1952 - pypy/trunk/doc/funding

[lac at codespeak.net]

Author: lac
Date: Wed Oct 15 12:00:24 2003
New Revision: 1952

Modified:
   pypy/trunk/doc/funding/B4.resources.txt
Log:
talk about life-in-a-fishbowl, and how transparency effects how we can deliver


Modified: pypy/trunk/doc/funding/B4.resources.txt
==============================================================================
--- pypy/trunk/doc/funding/B4.resources.txt	(original)
+++ pypy/trunk/doc/funding/B4.resources.txt	Wed Oct 15 12:00:24 2003
@@ -524,6 +524,27 @@
 results has already been tested under circumstances that are very
 similar to what they will be during the project.
 
+Moreover, this project will be run in as transparent a fashion as
+possible.  Our code will be avaliable every night from our repository.
+Our mailing list discussions will be available on a publically
+readable archive, and any person is free to join our mailing lists.
+Our Internet-Relay-Chat conversations, when important, will be
+logged and archived.  You can watch us create our documents, our
+code, and our deliverables, day to day, as it happens.  Meetings
+in person will be summarised, and they will be posted.  This is 
+'life in a fish bowl', as transparent a process as you can see.
+
+This is important because the reason most projects fail to deliver
+is because somebody was having a problem, and was too embarassed or
+afraid to look bad in front of others to admit the problem until it
+was too late to do anything about it.  It is secrecy, and not lack of
+competance that causes most of the problem.  We will avoid this.
+Our EU project leader will be able to monitor our progress on a daily
+basis and will always be able to know what we are up to, and how
+we think it is going.  He or she will be free to participate in our
+Sprints, and join our mailing lists, talk to us via IRC - whatever 
+level of involvement is desired.
+
 Resources to be mobilised
 -------------------------
 In any project there are three crucial resources to be mobilised.