[pypy-svn] r18631 - pypy/extradoc/planning
hpk at codespeak.net
hpk at codespeak.net
Sat Oct 15 16:40:32 CEST 2005
Date: Sat Oct 15 16:40:30 2005
New Revision: 18631
results of the saturday afternoon planning meeting
at the Paris sprint covering phase 2 and some phase 3
sprint + conferences + workshop + ... plans.
--- pypy/extradoc/planning/phase2_projectactivities.txt (original)
+++ pypy/extradoc/planning/phase2_projectactivities.txt Sat Oct 15 16:40:30 2005
@@ -2,44 +2,108 @@
Rough preparation draft for saturday-afternoon 20051015 meeting Paris
+work group/pairing status
+- ootypes / rtyper refactoring:
+ Boris reports: continued to refactor rypting into
+ non-ll specific and ll-specific parts. still a lot
+ of work to be done (currently you can specialize
+ an empty class with the oo-type system).
+ bert: squeak backend uses the oo-type system and
+ creates squeak class definitions. (oo-types are
+ built manually there at the moment).
+- socket module:
+ all the interface is wrapped/implemented at interpreter-level
+ and is reusing the underlying (cpython) socket module. There is
+ not translation/external function calls yet (which will introduce
+ platform issues).
+- numeric module:
+ started the basic Array type, you can construct such types that
+ contain floats or integers, and you can have efficient slices
+ (reusing the same underlying array). The base Array class
+ is not connected to storage, subclasses are (specific to floats/ints).
+ have a refined very-low-level flow graph model, and we can
+ pass in integers and do addition. also the l3intepreter
+ is translateable and passes tests.
+- compiler issues
+ ran the core compliancy tests (failing ones are mostly
+ due to missing weakref support). problem is that we
+ are having a mix of all slightly incorrect compiler
+ (or at least don't know if they/which are correct)
+ variations. It seems to make more sense to contribute the
+ whole astcompiler rather than trying to come up with patches
+ to the CPython version.
+- translation issues:
+ compliance tests start to run on pypy-c (test_builtin.py)
+ but there are likely more bugs/issues lurking.
+ christian is working on locality of references by
+ analysing flowgraphs.
+pypy technical task planning
+Identify tasks to be done in between sprints, start with
+- full compiler/parser integration
+- pypy-sync meetings should constantly track/amend/modify those
+ technical tasks and in general focus on technical issues
+ NOTE though: pypy-sync cannot focus too much on EU requirements
+ because it's a more open/community forum.
+- idea is to collect all larger tasks and bring plannings
+ to the pypy-sync meetings. Carl is going to do the next
+ pypy-sync meeting. Send plans/larger task plannings to
+ the moderators and don't wait until the moderator generates
+ the idea himself.
sprints & conferences
- *5-11th December (?):
- Meeting in Sweden? Change Maker?/Götabergsgatan?
- A sprint around bruxelles might make sense,
- holger is checking with bruxelles and Louvain-la-neuve
- (near bruxelles) people for a sprint beginning of
- december. Bea is checking with Mallorca/Barcelona
- regarding the same time frame. Nothing definitive
- yet, alas!
+ next sprint: 5-11th December in Sweden (Change Maker?/Götabergsgatan?)
+ *(10 th January eu review workshop)
*23-29th January: CS Dep. of the Palma de Mallorca University/CS Dep. of the Barcelona University
Bea check dates, Bruxelles/Louvain-la-neuve, Holger check dates),
- *27-29th February: PyCon (24-26 Feb, 2006 Dallas, Texas, Presperint?, Holger)
+ *27-29th February: PyCon (24-26 Feb, 2006 Dallas, Texas, postsprint,
+ Michael/Holger, Armin, Christian, Bea), DEADLINE 30th October
*April Japan: (1) April 23 to April 29, (2) April 30 to May 5, contact: Yutaka Niibe,
- National Institute of AIST, Japan (FSIJ) Akihabara, Tokyo (Bea)
- *6-9th (?) July: Europython Cern (3-5th July (?) Swizerland, Michael/Holger?)
+ National Institute of AIST, Japan (FSIJ) Akihabara, Tokyo (Bea), venue for 32 people.
+ (However, check with the EU).
+ * (IBM workshop possibly end June, holger)
+ *6-9th (?) July: Europython Cern (3-5th July maybe in Leysin (Armin) Swizerland,
+ and the post-sprint at CERN, Michael/Holger)
- *21-27th August: University of Limerick/Ireland (Bea)
+ *21-27th August: University of Limerick/Ireland (Bea), maybe good possibility
+ to present pypy results to researchers.
- *2-8th October: ?
+ * 2-8th October: ?
+ * November: closure sprint
- Other possibilities: Romania, Switzerland (Leysin,Bern), Uganda (Nkozi)
+ Other possibilities: Romania, Switzerland (Leysin,Bern), Bristol, Uganda (Nkozi), bruxelles
- Conference/y´talks planning:
- HALF-FIXED:8th December 2005 Calibre/agile development workshop in
+ FIXED:27th October2005 PMI Chapter Sweden, methodology/PyPy talk in Linköping (Bea)
+ HALF-FIXED: 8th December 2005 Calibre/agile development workshop in
Bruxelles, Bea, Holger, Alastair attending (or maybe
just two persons). Bea coordinates (Alastair?).
- FIXED:27th October2005 PMI Chapter Sweden, methodology/PyPy talk in Linköping (Bea)
HALF-FIXED: CCC 27th-30th December Berlin (pypy technical talk accepted,
non-technical talk pending, may be unlikely, holger is keeping
@@ -49,9 +113,9 @@
Holger/Bea do talks about PyPy - methodology and tehnical aspects
FIXED: Solution Linux 2006 (31st Januray-2nd Feb):
- Logilab will present PyPy in the "free software models" track.
+ Logilab will present PyPy in the "free software models" track in Paris.
- OPEN: PyCon, 24th-26th Feburary: Holger wants to submit one or two proposals
+ OPEN: PyCon, 24th-26th Feburary: michael/holger/christian/armin want to submit one or two proposals
and go there, also doing a py lib and/or pypy-sprint. Bea wants to submit methodology talk.
Note that sprints are scheduled after the conf.
DEADLINE: 30th October (in two weeks!)
@@ -59,35 +123,23 @@
OPEN: 3 of March 2006 Skövde Sweden, CALIBRE Workshop on Distributed Development,
Open Source & Industry- Opportunities, Suspicions, & Strategies (Bea)
+ OPEN: ACCU 19th-22nd April 2005 (michael, jacob)
+ Submission date:?
OPEN: XP 2006, 17-22th June 2006 Oulu Finland
Submission date: 1 march 2006 (methodology talk/workshop?/Bea)
OPEN: 3-5th July 2006 Europython Cern Switzerland
Submission date: ?
- OPEN: OOPSLA 2006 (no date?)
- Submission date: ?
+ OPEN: OOPSLA 2006 (Samuele, Armin)
+ Submission date: probably 20th March 2006
OPEN: Calibre conferences
OPEN: Agile Alliance conferences?
Submission date: ?
- OPEN: ACCU?
- Submission date:?
-pypy technical task planning
-Identify tasks to be done in between sprints, start with
-- full compiler/parser integration
-- pypy-sync meetings should constantly track/amend/modify those
- technical tasks and in general focus on technical issues
- NOTE though: pypy-sync cannot focus too much on EU requirements
- because it's a more open/community forum.
EU-related Workpackage planning planning phase 2
@@ -127,39 +179,39 @@
Completion date: 16th Oct 2005
D04.1 Partial Python Impl:
+Primary/Secondary: Jacob / Christian
D04.2 Complete Python Impl:
+Primary/Secondary: Jacob / Christian
D04.3 Parser report:
+Primary/Secondary: ludovic,adrien / Arre
D04.4 Release PyPy-research-tool:
+Primary/Secondary: Samuele / Ludovic
D05.1 Publish on translating a very-high-level description:
+Primary/Secondary: Armin / Michael
D05.2 A compiled, self-contained version of PyPy:
+Primary/Secondary: dfki/Anders L. / Jacob
D05.3 Publish on implementation with translation aspects:
+Primary/Secondary: Carl / Armin, Christian
D05.4 Publish on encapsulating low level language aspects:
+Primary/Secondary: Armin / holger
D14.1 Report about Milestone/Phase 1:
Completion date:21th October 2005
@@ -175,7 +227,7 @@
*9th December 2005: Periodic management/activity reports updated with all data but costs
-*15th December 205: submit reports to EC/reviewers
+*15th December 2005: submit reports to EC/reviewers
*16th December 2005: all partners submit FORM C:s to DFKI (or communicate a new
@@ -187,4 +239,4 @@
*15th of January 2006: submit FORM C:s to EC/PO and possible updated periodic management/
\ No newline at end of file
More information about the Pypy-commit