[pypy-svn] r43489 - pypy/extradoc/talk/ep2007

[antocuni at codespeak.net]

Author: antocuni
Date: Fri May 18 16:49:35 2007
New Revision: 43489

Modified:
   pypy/extradoc/talk/ep2007/   (props changed)
   pypy/extradoc/talk/ep2007/abstract_interpreter.txt   (props changed)
   pypy/extradoc/talk/ep2007/development.txt   (contents, props changed)
   pypy/extradoc/talk/ep2007/planning.txt   (contents, props changed)
   pypy/extradoc/talk/ep2007/pypy_10_and_jit.txt   (props changed)
Log:
typo and fixeol



Modified: pypy/extradoc/talk/ep2007/development.txt
==============================================================================
--- pypy/extradoc/talk/ep2007/development.txt	(original)
+++ pypy/extradoc/talk/ep2007/development.txt	Fri May 18 16:49:35 2007
@@ -1,18 +1,18 @@
-PyPy: Why and how did it (not) work? 
--------------------------------------------------
-
-Some people have said that they have hardly seen a large
-project succeed with delivering to the original goals as much
-as the PyPy project did.  Others consider it a failure because
-it did not take over the world yet or is not usable for
-mainstream purposes.  Anyway, we'll talk about the mix of
-development processes, methods and infrastructure of the PyPy
-project.  We will summarize our experiences regarding the
-evolving development environment (version control, automated
-test-driven development, sprints, synchronization, "conceptual
-integrity", communication channels). We will also try to share
-our "learning by burnings" so that other projects can explore
-other creative problems and mistakes than maybe repeating the
-ones we explored in depth already during the last 4 years of
-PyPy development. 
-
+PyPy: Why and how did it (not) work? 
+-------------------------------------------------
+
+Some people have said that they have hardly seen a large
+project succeed with delivering to the original goals as much
+as the PyPy project did.  Others consider it a failure because
+it did not take over the world yet or is not usable for
+mainstream purposes.  Anyway, we'll talk about the mix of
+development processes, methods and infrastructure of the PyPy
+project.  We will summarize our experiences regarding the
+evolving development environment (version control, automated
+test-driven development, sprints, synchronization, "conceptual
+integrity", communication channels). We will also try to share
+our "learning by burnings" so that other projects can explore
+other creative problems and mistakes than maybe repeating the
+ones we explored in depth already during the last 4 years of
+PyPy development. 
+

Modified: pypy/extradoc/talk/ep2007/planning.txt
==============================================================================
--- pypy/extradoc/talk/ep2007/planning.txt	(original)
+++ pypy/extradoc/talk/ep2007/planning.txt	Fri May 18 16:49:35 2007
@@ -2,13 +2,13 @@
 
 1. "A usual pypy talk" - architecture, motivation etc. (samuele,armin)
 2. An RPython talk: .NET, JVM, JS, extcompiler, possible uses, caveats,
-   probably some architecture (anot,fijal)
+   probably some architecture (anto,fijal)
 3. Interpreters talk: taint, thunk, persistance, distribution, probably
    some stackless (?), interpreter for .NET (hpk, fijal)
-4. recommendations on "how to" OSS/EU-funding/research project (hpk,lene)
-5. development process "how to" (bea, hpk maybe)
-
-These last two talks (4-5) should be scheduled together - let´s ask for it
-when submitting. They are "final" recommendations and reflections from PyPy
-regarding formal structures and informal structures (contract and development process).
+4. recommendations on "how to" OSS/EU-funding/research project (hpk,lene)
+5. development process "how to" (bea, hpk maybe)
+
+These last two talks (4-5) should be scheduled together - let´s ask for it
+when submitting. They are "final" recommendations and reflections from PyPy
+regarding formal structures and informal structures (contract and development process).
 (Phone discussion between hpk and bea 18/5)