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
D2.6: Community building: Impact of development workshops, dissemination and training activities, year 2 #46
Labels
Comments
@VivianePons This deliverable is officially due for 31/08/2017. Can you please report on the progress you have achieved? |
In the revised plan, this deliverable was removed. It was merged with D2.11
2017-08-16 15:54 GMT+02:00 bpilorget <notifications@github.com>:
… @VivianePons <https://github.com/vivianepons> This deliverable is
officially due for 31/08/2017. Can you please report on the progress you
have achieved?
Thanks in advance
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#46 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADcG4Ozckp6FXc2LMvk06nKs4B7MOBjkks5sYvSJgaJpZM4F5ynX>
.
|
Thanks :) |
I will start preparing the document next week, it will eventually contain
all the data about events that happened in 2016-2017 and also 2017-2018 (D
2.11). But considering it is the end of august, I'm not going to rush
people next week to have everything by the D2.6 deadline (this document
depends on many different persons). I would rather leave more time to get
more comprehensive information on each event.
2017-08-17 13:27 GMT+02:00 bpilorget <notifications@github.com>:
… Thanks :)
Yes but the revised plan will not be officially accepted before the
deadline, hence the need for your answer
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#46 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADcG4DldDYsJnQGCmU-D3FVuBLZ2EEEYks5sZCO6gaJpZM4F5ynX>
.
|
I know all this :) Just reminding the deadline that's all |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See page 39 of the proposal for the full description.
The text was updated successfully, but these errors were encountered: