[pypy-svn] r41156 - pypy/extradoc/planning/1.0

hpk at codespeak.net hpk at codespeak.net
Fri Mar 23 12:14:14 CET 2007

Author: hpk
Date: Fri Mar 23 12:14:11 2007
New Revision: 41156

after considering (and drafting a bit) 
i think we need to seriously consider architecture.txt
refinements if we want to be clearer about 
our communication regarding what PyPy is. 

Modified: pypy/extradoc/planning/1.0/TODO.txt
--- pypy/extradoc/planning/1.0/TODO.txt	(original)
+++ pypy/extradoc/planning/1.0/TODO.txt	Fri Mar 23 12:14:11 2007
@@ -58,6 +58,26 @@
     - review entry points from the play1 demos. 
+    - review/refactor architecture.txt:
+      - mission statement should emphasize VM
+        framework/translation and not mention project results 
+      - always clearly separate the talk about the VM translation 
+        framework and the Python implementation (and its features) 
+        for example "PyPy - implementation of python in python" 
+        as the first title is misleading.  maybe something like: 
+        a) PyPy is a VM/VHLL translation framework (or whatever we settle on)
+        b) already contains a full Python implementation
+           part of which is re-used from the translation framework 
+           to analyse RPython programs (abstract interpretation ...)
+      - make the descriptions more "future" proof, i.e. 
+        not reflecting the current state, possibly shortening
+      rationale for looking in more depth at architecture.txt: 
+      this document and getting-started.txt document are
+      the most viewed (arch: 1500 times in march, getting-started: 
+      around 2200 times) ones and people expect archictecture.txt
+      to reflect our view on the project. 
   - describe particularly Javascript-related demos, refine them. 
     (mostly done, apart from 404/500 pages and possible JIT demo) 
     It's all more or less done. What needs to be done (play1):

More information about the Pypy-commit mailing list