[pypy-svn] rev 1181 - in pypy/trunk/doc: . sprintinfo

[hpk at codespeak.net]

Author: hpk
Date: Fri Jul 18 04:05:52 2003
New Revision: 1181

Added:
   pypy/trunk/doc/sprintinfo/hildesheim.txt
Removed:
   pypy/trunk/doc/pe.txt
   pypy/trunk/doc/socialpy.txt
Log:
some cleanup of the doc-directoy

- moved most of "socialpy" into a hildesheim.txt report

- removed pe.txt which is just a fragment and at least
  has no reason to be at top-level. If anybody understands
  this fragment then please make it into a document and
  put it to some appropriate place.  Now that we have the
  OSCON-Paper as a base i don't think that we need  all 
  these small fragments anymore. 



Deleted: pypy/trunk/doc/pe.txt
==============================================================================
--- pypy/trunk/doc/pe.txt	Fri Jul 18 04:05:52 2003
+++ (empty file)
@@ -1,22 +0,0 @@
-the core idea is: you have the SOS or maybe a subclass of it that
-keeps lightweight instrumentation and detects when a function is
-heavily used for some definition, when that happens it will
-(say for a thread or process on a diff CPU) run the annotating
-os for that function, so the SOS might collect info about the
-types of arguments for the function already, "it's popular and
-often called with 2 int args" so (AI at work) "it's a good idea
-to see if we can implement it in C" so the annotating OS is
-asked to do symbolic exec and later generate C (how you do the
-latter is a different story -. we now build a huge data struct
-about what we know about the code at each point during exec,
-from that it should be possible to generate C code, currently
-we don't record which variable are still alive and which ones
-aren't so we'll need to add that).
-
-So there's a 3rd OS that lets you run functions that have bee
-translated to machine code via C, still needs to interact with
-the first OS so here having multiple OSs that interact makes
-sense, e.g. for calls from C-speed-OS stuff back to occasional
-calls to Standard OS (translate the C ints back to Python ints
-before you can call the Python code, etc etc)
-

Deleted: pypy/trunk/doc/socialpy.txt
==============================================================================
--- pypy/trunk/doc/socialpy.txt	Fri Jul 18 04:05:52 2003
+++ (empty file)
@@ -1,12 +0,0 @@
-PyPy:
-
-Social aspects of PyPy
-
-PyPy was created in a cooperative process among pythonistas across the world. The first PyPy concepts were developed by who/where?
-
-The Hildesheim Sprint provided a chance to meet and decide several crucial design considerations. A #pypy irc channel provided communication among participants between sprints. The sourcecode was loaded into subversion and participants given commit rights.
-
-At the Sprint:
-Some folks did lots of handwaving and created really kewl concepts. Other pairs concentrated on coding, testing, builtin functions etc etc. We gathered for goalsetting meetings several times during the sprint, then split up to work on tasks. Much of the work was done by pair programming. Pairs were informal, developing and changing as tasks were discovered and completed. Sprints varied in amount of "discuss as a group" and "just do it" time. We spent lots of intense time together, not just coding but also social time, (meals, spending a day playing tourist, etc), which enhanced the building of relationships and understanding among sprinters.
-
-Some discoveries: Plan on the first morning for hardware setup and fixing system issues, (wireless is great!) Built-in private time is necessary for the sprint. Whiteboards and projectors are both necessary, as is coffee and tea. Bringing in/providing food is fine but getting people away for lunch is good to clear their minds. Leadership varied throughout the sprints and throughout the day.

Added: pypy/trunk/doc/sprintinfo/hildesheim.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/sprintinfo/hildesheim.txt	Fri Jul 18 04:05:52 2003
@@ -0,0 +1,11 @@
+Hildesheim Sprint Report
+========================
+
+The Hildesheim Sprint provided a chance to meet and decide several crucial design considerations. 
+A #pypy irc channel provided communication among participants between sprints. The sourcecode 
+was loaded into subversion and participants given commit rights.
+
+At the Sprint:
+Some folks did lots of handwaving and created really kewl concepts. Other pairs concentrated on coding, testing, builtin functions etc etc. We gathered for goalsetting meetings several times during the sprint, then split up to work on tasks. Half of the work was done by pair programming. Pairs were informal, developing and changing as tasks were discovered and completed. Sprints varied in amount of "discuss as a group" and "just do it" time. We spent lots of intense time together, not just coding but also social time, (meals, spending a day playing tourist, etc), which enhanced the building of relationships and understanding among sprinters.
+
+Some discoveries: Plan on the first morning for hardware setup and fixing system issues, (wireless is great!) Built-in private time is necessary for the sprint. Whiteboards and projectors are both necessary, as is coffee and tea. Bringing in/providing food is fine but getting people away for lunch is good to clear their minds. Leadership varied throughout the sprints and throughout the day.