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

nico at codespeak.net nico at codespeak.net
Fri Oct 3 12:34:10 CEST 2003


Author: nico
Date: Fri Oct  3 12:34:09 2003
New Revision: 1537

Added:
   pypy/trunk/doc/funding/B6.7.wp100_aspect_oriented_prog.txt
   pypy/trunk/doc/funding/B6.7.wp90_constraint_prog.txt
   pypy/trunk/doc/funding/project_gantt.png   (contents, props changed)
Modified:
   pypy/trunk/doc/funding/project_planning.xml
   pypy/trunk/doc/funding/project_resources.xml
Log:
two new workpackages.

the png gantt diagram to make things.


Added: pypy/trunk/doc/funding/B6.7.wp100_aspect_oriented_prog.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B6.7.wp100_aspect_oriented_prog.txt	Fri Oct  3 12:34:09 2003
@@ -0,0 +1,72 @@
+.. include:: crossreferences.asc
+
+:DELETE:BEGIN:
+
+participants are Logilab and PBF
+
+possible: Alex Martelli with Strakt or PBF ?
+          
+
+:DELETE:END:
+
+.. |title| replace:: Aspect Oriented Programming and static checking
+.. |wp|    replace:: WP100
+.. |start| replace:: M2
+.. |p1|    replace:: X
+.. |m1|    replace:: 0
+.. |p2|    replace:: Y
+.. |m2|    replace:: 0
+.. |p3|    replace:: Z
+.. |m3|    replace:: 0
+.. |p4|    replace:: |e|
+.. |m4|    replace:: |e|
+.. |p5|    replace:: |e|
+.. |m5|    replace:: |e|
+.. |p6|    replace:: |e|
+.. |m6|    replace:: |e|
+
+.. include:: wp-toptable.asc
+
+.. include:: wp-tablebegin.asc
+
+**Objectives**
+
+Implement aspect oriented programming features to
+allow for more flexible ways to design software
+applications by better separating design concerns.
+
+.. include:: wp-tableend.asc
+.. include:: wp-tablebegin.asc
+
+**Description of work**
+
+Using the flexible architecture provided by the PyPy interpreter,
+we will first reimplement the current aspect-oriented libraries
+available from Logilab, to better integrate with the language
+and greatly simplify the design and enhance the performance.
+
+This aspect enabled interpreter will be used to offer
+design-by-contract facilities as seen in the Eiffel programming
+language and the current aspect-oriented library. It will also
+allow us to implement advanced static checking and code
+correctness capabilities, thus furthering the work done with
+the pychecker and pylint tools.
+
+.. include:: wp-tableend.asc
+.. include:: wp-tablebegin.asc
+
+**Deliverables**
+
+- DL??? Implementation of aspect-oriented programming
+  capabilities in PyPy
+
+- DL??? Implementation of design-by-contract and advanced
+  static checking capabilities.
+
+.. include:: wp-tableend.asc
+.. include:: wp-tablebegin.asc
+
+**Milestones and Expected Result**
+
+
+.. include:: wp-tableend.asc

Added: pypy/trunk/doc/funding/B6.7.wp90_constraint_prog.txt
==============================================================================
--- (empty file)
+++ pypy/trunk/doc/funding/B6.7.wp90_constraint_prog.txt	Fri Oct  3 12:34:09 2003
@@ -0,0 +1,70 @@
+.. include:: crossreferences.asc
+
+:DELETE:BEGIN:
+
+participants are Logilab and DFKI
+
+roughly 1,5 person each
+
+--> 3 person total for 1 year (?)
+
+:DELETE:END:
+
+.. |title| replace:: Constraint programming for the Semantic Web
+.. |wp|    replace:: WP90
+.. |start| replace:: 
+.. |p1|    replace:: X
+.. |m1|    replace:: 0
+.. |p2|    replace:: Y
+.. |m2|    replace:: 0
+.. |p3|    replace:: Z
+.. |m3|    replace:: 0
+.. |p4|    replace:: |e|
+.. |m4|    replace:: |e|
+.. |p5|    replace:: |e|
+.. |m5|    replace:: |e|
+.. |p6|    replace:: |e|
+.. |m6|    replace:: |e|
+
+.. include:: wp-toptable.asc
+
+.. include:: wp-tablebegin.asc
+
+**Objectives**
+
+Implement constraint satisfaction algorithms and
+inference engine to allow logic programming for
+Semantic Web applications.
+
+.. include:: wp-tableend.asc
+.. include:: wp-tablebegin.asc
+
+**Description of work**
+
+Using the flexible architecture provided by the PyPy interpreter,
+we will first reimplement the current python-logic libraries 
+available from Logilab to better integrate with the language
+and gain important execution speed-ups.
+
+This logic programming enabled python interpreter will then be
+used to further develop the projects related to Semantic Web
+applications that are on-going at Logilab and DFKI.
+
+.. include:: wp-tableend.asc
+.. include:: wp-tablebegin.asc
+
+**Deliverables**
+
+- DL??? Implementation of constraint satisfaction engine and 
+  inference engine in PyPy
+
+- DL??? Assessment of benefits obtained from using PyPy over
+  current tools to further develop Semantic Web projects
+  at Logilab and DFKI.
+
+.. include:: wp-tableend.asc
+.. include:: wp-tablebegin.asc
+
+**Milestones and Expected Result**
+
+.. include:: wp-tableend.asc

Added: pypy/trunk/doc/funding/project_gantt.png
==============================================================================
Binary file. No diff available.

Modified: pypy/trunk/doc/funding/project_planning.xml
==============================================================================
--- pypy/trunk/doc/funding/project_planning.xml	(original)
+++ pypy/trunk/doc/funding/project_planning.xml	Fri Oct  3 12:34:09 2003
@@ -1,5 +1,7 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-
+<!--  use with http://www.logilab.org/projects/pygantt
+      to generate gantt diagrams in image (png?) format
+-->
 <project id="PyPy EU Project">
 
 <import-resources file="project_resources.xml"/>

Modified: pypy/trunk/doc/funding/project_resources.xml
==============================================================================
--- pypy/trunk/doc/funding/project_resources.xml	(original)
+++ pypy/trunk/doc/funding/project_resources.xml	Fri Oct  3 12:34:09 2003
@@ -1,9 +1,25 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
+<!--  use with http://www.logilab.org/projects/pygantt
+      to generate gantt diagrams in image (png?) format
+-->
 
 <resource-list>
 
-<resource id="proj-manager" type="worker" unitcost="1"/>
+<resource id="proj-manager" type="person" unitcost="1"><skill>project management</skill></resource>
 
-<resource id="hacker1" type="worker" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker1" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker2" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker3" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker4" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker5" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker6" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker7" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker8" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker9" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker10" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker11" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker12" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker13" type="person" unitcost="1"><skill>hacker</skill></resource>
+<resource id="hacker14" type="person" unitcost="1"><skill>hacker</skill></resource>
 
 </resource-list>
\ No newline at end of file


More information about the Pypy-commit mailing list