New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
D1.5: Internal Progress Reports years 2 and 3, including risk management and quality assurance plan #21
Comments
I left a comment in #193 about fixing the title as well in the grant agreement. |
@nthiery I have updated WP6 to this report period. My understanding is that the report is to be read cummulatively, and that I do not have to delete past achievements. I am now looking over the other parts of the document. |
@nthiery
and I will hire
|
@ntheiry I have updated WP6 to this report period.
My understanding is that the report is to be read cummulatively, and
that I do not have to delete past achievements.
As long as there is a clear distinction between past achievements and
achievements for this reporting period, and if that contributes to the
overall understanding, that's all good!
I am now looking over the other parts of the document.
Thanks!
|
In 2.1. I see The following people were hired in the past year: and
then the table shows hiring from 2015 and so on.
I am not sure that to do. I have hired
Theresa Pollinger: October 2017 - May 2018
Tom Wiesing: September 2017 -
Hmm, good catch. We definitely should separate hiring from RP1 and
RP2. And possibly remove the former. If you could start a first draft
of this (especially for the information you have) that would be great,
and I'll finalize.
|
I have done that; highlighting Florian's joint appointment. But someone will have to read the general text carefully and update all the little things. |
I have done that; highlighting Florian's joint appointment.
Great, thanks Michael,
But someone will have to read the general text carefully and
update all the little things. I will not have time to do that
unfortunately.
Yeah ... that's on me ...
Luckily, that's the internal report; we will be able to do further
polishing for the full technical report due one month from now.
|
I have started carefully going over this report again, and I have pushed the first results of this. I have
|
I will continue doing this all of today. |
Thank you Michael; I really really appreciate this. With Benoit away @VivianePons, @defeo, @minrk, @ClementPernet, please check on Michael's ednotes and fill them in! |
About the overall structure: you may want to double check on the template |
Wow, that is quite different to the current structure (which I only changed marginally). |
I have adapted the structure of the report (the ToC is now correct) and will continue later. |
Accepted by the EU on December 5th. |
This document is meant as an internal draft for the project's Technical Report for Reporting Period 2. As such, it provides an overview of the project achievements, by objectives, work packages, and tasks from March 2017 to August 2018, and their impact. It also explains how reviewer's recommendations were tackled and discusses risk and quality management and deviations from the original plan.
We recommend to read directly the technical report itself.
The text was updated successfully, but these errors were encountered: