[pypy-svn] r3377 - pypy/trunk/doc/funding/negotiations
alastair at codespeak.net
alastair at codespeak.net
Wed Mar 24 18:48:58 CET 2004
Author: alastair
Date: Wed Mar 24 18:48:56 2004
New Revision: 3377
Modified:
pypy/trunk/doc/funding/negotiations/email-eu-1.txt
Log:
Fixed typos.
Modified: pypy/trunk/doc/funding/negotiations/email-eu-1.txt
==============================================================================
--- pypy/trunk/doc/funding/negotiations/email-eu-1.txt (original)
+++ pypy/trunk/doc/funding/negotiations/email-eu-1.txt Wed Mar 24 18:48:56 2004
@@ -7,7 +7,7 @@
During the meeting on 16th of March 2004 the PyPy consortium was told
that the cost model and budget of the PBF is not acceptable according
-to the guidelines of the sixth framework programm.
+to the guidelines of the sixth framework program.
This doesn't impose a big problem to the project because it is - also
contrary to our previous belief - possible that individuals enter the
@@ -21,7 +21,7 @@
As a result, we now intend to bring the consortium into its final
shape like follows:
-1. MPI shall employ Samuele Pedronis, taking part in core work
+1. MPI shall employ Samuele Pedroni, taking part in core work
and will also bring in the end user view into the project.
Discussion: We don't think there is any problem as MPI is
@@ -29,11 +29,11 @@
-------------- or ----------------------
-1. The financers of AB Strakt have promised to provide matching funding
+1. The financiers of AB Strakt have promised to provide matching funding
for Samuele Pedroni. Samuele joins AB Strakt as an employee. Previously
he was planned to work through the MPI at core parts of the PyPy
project. Thankfully, through AB Strakt he can still work at the
- work packages previously assigned to MPI and PBF respecitvely.
+ work packages previously assigned to MPI and PBF respectively.
Discussion: Samuele Pedroni is an important member of the project. We
can't see that this change should pose any problems.
@@ -52,7 +52,7 @@
distribute an average of 4 travel grants to each sprint. Half of
these grants will go to people who are deemed to further the
project technically, while half of the grants will be directed
- towards diseminating knowledge about the project in the Python
+ towards disseminating knowledge about the project in the Python
community. While the former grants may go to a single individual
on multiple occasions, the latter shall be restricted to once per
individual. A grant will cover economy travel, modest lodgings and
@@ -62,14 +62,14 @@
expenses for the actual working time of the sponsored participants.
This will contribute a total of 14 man months to the project, some
of which will contribute to the technical goals and some which will
- contribute to the disemination goals. For this, we want to make the
+ contribute to the dissemination goals. For this, we want to make the
PBF a partner in appropriate working packages.
b) The PBF is allowed to pay individual organisations for up to a
total of 5 man months of time for infrastructure and dissemination
tasks. Each man month will be paid for at a fixed rate of 7000
Euro. Each such contractor shall be selected from the membership of
- the PBF and the wider european python community by the project
+ the PBF and the wider European python community by the project
management board in collaboration with the PyPy-SIG of the PBF.
No single contractor may receive more than 10.000 Euro. The time
contributed in the item a) above shall be considered to be matching
@@ -101,15 +101,15 @@
This limits flat grants to a maximum of 7% of the total project
budget.
-Under 6.1 Annex 1, 6.1.1 - Personell, First item, third sub-item, it
+Under 6.1 Annex 1, 6.1.1 - Personnel, First item, third sub-item, it
appears that the contract can specify a provision that allows
subcontracting as specified in 3 b) above.
-We believe that the procedure for selecting subcontractors as outlined
-above fulfills the requirements in 2.2.1.1 for transparency and equal
+We believe that the procedure for selecting sub-contractors as outlined
+above fulfils the requirements in 2.2.1.1 for transparency and equal
treatment.
-As we understand it, by expicitly spelling out the provisions under item
+As we understand it, by explicitly spelling out the provisions under item
3 above, we are in full compliance with the Guide to Financial Issues.
If you agree to the proposed consortium and cost model scheme above we will
More information about the Pypy-commit
mailing list