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

D2.1: Starting press release #34

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

D2.1: Starting press release #34

minrk opened this issue Sep 8, 2015 · 2 comments
Assignees
Labels

Comments

@minrk
Copy link
Contributor

@minrk minrk commented Sep 8, 2015

We have announced the start of this project through diverse media linked to the institutions and thematic of the different partners. A regularly updated list is available from our web page: http://opendreamkit.org/follow/#press-releases. Copies of the annoucements published at the time of delivery are included as appendices of the report.

We intend to keep releasing relevant information to these media throughout the project.

@minrk minrk added this to the D2.1 milestone Sep 8, 2015
@nthiery nthiery mentioned this issue Sep 11, 2015
3 of 3 tasks complete
VivianePons added a commit that referenced this issue Feb 25, 2016
@nthiery nthiery modified the milestones: Month 6: 2016-02-29, D2.1 Mar 22, 2016
@nthiery
Copy link
Contributor

@nthiery nthiery commented Apr 28, 2016

I just got an answer from the SMF: ``La Gazette serait heureuse de publier comme vous le proposez un texte d'une ou deux pages dans la rubrique information''.
Once we have submitted this text, we can close this issue.

@bpilorget
Copy link
Contributor

@bpilorget bpilorget commented Oct 24, 2016

Deliverable updates

@VivianePons As you know , during the interim review in Bremen, reviewers gave advice to improve deliverables. UPSud tried to follow their advice by updating D5.1 #107
The main critic is that deliverables should be static document. Therefore we went through the #107 report to check if all links were still working and also if the information contained on the links was necessary for the understanding of the report.
As a result when it was necessary annexes were added to the #107 report.

Can you please do the same for this deliverable and add annexes when need be?

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
3 participants
You can’t perform that action at this time.