Skip to content
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

Closed
minrk opened this issue Sep 8, 2015 · 14 comments

Comments

@minrk
Copy link
Contributor

@minrk minrk commented Sep 8, 2015

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.

@minrk minrk added this to the D1.5 milestone Sep 8, 2015
@nthiery nthiery modified the milestones: Month 36: 2018-08-31, D1.5 Mar 22, 2016
@kohlhase kohlhase mentioned this issue Mar 2, 2017
19 of 19 tasks complete
@nthiery nthiery changed the title D1.5: Internal Progress Reports year 2, including risk management and quality assurance plan D1.5: Internal Progress Reports year 3, including risk management and quality assurance plan Mar 2, 2017
@nthiery
Copy link
Contributor

@nthiery nthiery commented Mar 2, 2017

I left a comment in #193 about fixing the title as well in the grant agreement.

@bpilorget bpilorget mentioned this issue Apr 12, 2017
7 of 7 tasks complete
@bpilorget bpilorget changed the title D1.5: Internal Progress Reports year 3, including risk management and quality assurance plan D1.5: Internal Progress Reports years 2 and 3, including risk management and quality assurance plan Jan 11, 2018
@kohlhase
Copy link
Member

@kohlhase kohlhase commented Sep 5, 2018

@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.

@kohlhase
Copy link
Member

@kohlhase kohlhase commented Sep 5, 2018

@nthiery
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 -
  • Florian Rabe: December 2017 -

and I will hire

  • Katja Bercic: November 2018 -
@nthiery
Copy link
Contributor

@nthiery nthiery commented Sep 5, 2018

@nthiery
Copy link
Contributor

@nthiery nthiery commented Sep 5, 2018

@kohlhase
Copy link
Member

@kohlhase kohlhase commented Sep 5, 2018

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 will not have time to do that unfortunately.

@nthiery
Copy link
Contributor

@nthiery nthiery commented Sep 5, 2018

@kohlhase
Copy link
Member

@kohlhase kohlhase commented Oct 5, 2018

I have started carefully going over this report again, and I have pushed the first results of this. I have

  • reorganized the sectioning of the report to save on nesting depth and make reading easier (especially in the WPs)
  • I have moved the sections into their own (included) files.
  • I am leaving lots of ednotes and oldparts, where I have the feeling, the text is not updated yet.
    All in all, there is still considerable work to do on this deliverable (boring as it is).
@kohlhase
Copy link
Member

@kohlhase kohlhase commented Oct 5, 2018

I will continue doing this all of today.

@nthiery
Copy link
Contributor

@nthiery nthiery commented Oct 5, 2018

Thank you Michael; I really really appreciate this. With Benoit away
and all the rest, I am in submarine mode and this plugs a serious
breach: this deliverable was meant as a draft for our periodic technical report
(due October 10th!) and I never got to finalize it. So let's just work on it
as our final technical report, and submit both on October 10th.

@VivianePons, @defeo, @minrk, @ClementPernet, please check on Michael's ednotes and fill them in!

@nthiery
Copy link
Contributor

@nthiery nthiery commented Oct 5, 2018

About the overall structure: you may want to double check on the template
and our previous report

@kohlhase
Copy link
Member

@kohlhase kohlhase commented Oct 5, 2018

Wow, that is quite different to the current structure (which I only changed marginally).
I will have a look how to best adapt that.

@kohlhase
Copy link
Member

@kohlhase kohlhase commented Oct 6, 2018

I have adapted the structure of the report (the ToC is now correct) and will continue later.

@IzabelaFaguet
Copy link
Contributor

@IzabelaFaguet IzabelaFaguet commented Dec 7, 2018

Accepted by the EU on December 5th.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants