Dear All, As announced already at one of our previous Security Chapter conf call there would be now measures imposed by TID with approval of FI-WARE PCC to ensure timely delivery (starting first with M14 deliverables). Those measures are detailed below and translate into rejection of costs by those partners that do not deliver by July 23rd. * Partners involved in development of a given FI-WARE GE that is not delivered by July 23rd will not be allowed to justify any PM in WP3-WP8 until they deliver. Once they deliver, it will be assumed that the PMs consumed had been those that were reported until month 12, so that no additional PMs will be accepted. Planning of PMs for the remaining of the project will be adjusted accordingly. * Delivery of software that doesn't work or proves to be rather unstable in the FI-WARE Testbed will not be considered as actually delivered. This intends to prevent that some partner delivers software which doesn't meet enough quality by July 23rd ust to avoid costs rejections. * Partners that deliver by July 23rd will be allowed to justify the PMs planned until July 23rd (provided that the software they have delivered is not rejected as stated in the previous point). This means they would not suffer any impact. * PMs of any partner within a given WP (WP3-8) are distributed from month 10 on across deliverables as follows (note: we propose to include whatever distribution gets approved in the next amendment of the DoW): * Contributions to WP2 deliverables: 10% * FI-WARE Open Specifications: 20% * SW Release: 40% * Installation and Admin Guides: 7,5% * Users' and Programmers' Guides: 7,5% * Unit Testing Plan and Report: 15% * Deliverables of a given WP rejected by the WPL will be rejected. TID and the WPL agree on any amendment of the above rules that may apply (e.g., failing in delivery of a given GE may not be the fault of all partners involved in development of that GE so that they agree not to apply penalization to some partners). TID may reject some additional deliverables if it considers that they do not meet the defined guidelines or expected quality, after discussion with the WPL. * Similar rules would apply to WP9 (development tools) In view of those measures I'm now counting on those who still have actions to perform to perform them asap not to be penalized nor penalize the Security Chapter as a whole. Best Regards, Pascal -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20120717/7092ef97/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy