[pypy-svn] r8818 - pypy/funding
hpk at codespeak.net
hpk at codespeak.net
Thu Feb 3 13:19:05 CET 2005
Date: Thu Feb 3 13:19:05 2005
New Revision: 8818
dramatic shortening of the model. Use more definite phrases
and no "maybe"s. PLEASE read and counter-check if you
like this all!
--- pypy/funding/physical-person-model.txt (original)
+++ pypy/funding/physical-person-model.txt Thu Feb 3 13:19:05 2005
@@ -78,91 +78,54 @@
We want to implement an effective process for integrating physical
-persons into the EU project. The technical board is to
-actively invite people and partners to join our sprints and
-other developments. The board will select people according to
-criterias like usefulness for the project, past contributions
-and specific fields of knowledge.
-However, on the formal side there are still some details to
-resolve and we ask everyone, including our EU project officer
-and the national EU offices we have contacts to, to help us in
-setting up a model that can then be reused by other open
-and transparent projects as well.
-Here are some of the issues and our proposed solutions:
-- physical persons enter the EU contract by means of
- an Accession form. They are to get reimbursement for their
- travel and accomodation costs but not for their work
- costs. (See 2.4.7 of the Financial Guidelines from 04/2004).
- We do not think that we will have physical persons with
- full accounting systems and thus expect them to use
- the AC model (in a very simple way).
-- We would like to reimburse costs to the external
- sprint participants (as physical persons) while they
- are on the sprint venue. They should usually
- receive the money after we received copies of their
- receipts for travel/accomodation costs. Although the
- EU commission prepays only 80% of the full funding amount,
- we may want to reimburse 100% of their costs at once to
- simplify administration.
-- Physical persons are to sign an amendment to our Consortium
- contract. Here we need to specialize their membership
- internally in order to allow the consortium of full partners
- to continue to act efficiently. We cannot make sprint
- participants (physical persons) full members of the consortium
- because it would make meetings and decisions ever more difficult.
- Therefore, physical persons are to enter as "associated
- partners" which waive their voting rights and are not
- required to attend consortium meetings. We consider this
- mostly an internal detail of the consortium than something
- the EU commission has to care about.
- Also we want physical persons to _not_ participate in the
- general common liability of the full consortium partners
- towards the EU commission. We feel that it is unwarranted
- to receive work and contribution "for free" from sprint
- participants and then make them liable if the full partners
- cannot deliver as promised to the EU.
-- sprint participants (formally physical persons) should
- not be required to deliver audit certificates.
- If this is not feasible then we need to find an auditor who
- is willing to audit the very simple cost statements of the physical
- persons in a way that does not affect the management budget.
- (The costs for audit certificates are accounted to the
- management budget as far as we know). If audit certificates
- are neccessary even for one or two-time attenders of sprints
- then we kindly ask the EU commission for special allowance to
- not count the according costs to the "7% management Cap" rule.
+persons into the EU project according to Annex B.4.2. We aim
+to have this model reusable by other open and agile projects.
+Our experiences will be documented under WP14 (documentation
+The technical board is to actively invite people and partners
+to join our sprints and other developments. The board will
+select people according to criterias like project requirements,
+past contributions and specific fields of knowledge.
+Here are formal details about the implementation of B.4.2:
+- physical persons enter the EU contract by means of Form B.
+ They get reimbursement for their travel and accomodation costs
+ but not for their work costs. (See 2.4.7 of the Financial
+ Guidelines from 04/2004). We do not envision that we will
+ have physical persons with full accounting systems and
+ thus expect them to use the AC model in a simple way
+ and with small budgets.
+- Physical persons are to get 80% of their costs after they
+ show travel and accomodation receipts. Those receipts
+ will be audited by one auditor (payed for on an hourly basis).
+- Physical persons are to sign our Consortium contract. We will
+ specialcase their membership internally in order to allow the
+ consortium of full partners to continue to act efficiently
+ as they continue to bear the responsibility and liability for
+ the full implementation of the project.
Please note that the costs for sprint participants (physical
-persons) will only affect a very small portion of the overall
-budget. Also we are - as explicitely stated in the proposal -
-pioneering agile development/sprinting methods within
-an EU project we hope that the commission will help us
-to design the process in the proposed lightweight manner.
-We would like to setup the full model and process for
-getting physical persons into the EU project by mid
-February 2005. We have a number of people already interested
-and many of them are already explicitely mentioned in
-the proposal (B.220.127.116.11 and B.18.104.22.168 in the last amended
-version of December 2004).
-Please direct any feedback to pypy-funding at codespeak.net or to
-Laura Creighton <lac at strakt.com> and Holger Krekel
-<krekel at merlinux.de> who have been tasked by the partners
-to find a workable and efficient model for sprint participants
-to enter the project as physical persons.
+persons) will only affect a small portion of the overall
+budget which fully fits our accepted budget planning.
+Also we are - as explicitely stated in the proposal -
+pioneering agile development/sprinting methods within our EU
+project and we hope that the commission will later help us to
+think about designing open-source/agile development processes
+Time frame / Request for confirmation
+We want to perform the implementation of B.4.2 as soon as posssible,
+but no later than March 2005. We respectfully request a confirmation
+in writing that we can proceed as outlined.
+We have a number of people already interested and most of them
+are even explicitely mentioned in the proposal (B.22.214.171.124
+and B.126.96.36.199 in the December 2004 version).
More information about the Pypy-commit