Closed pchainho closed 8 years ago
I suppose this question is about the content of the deliverable. Note that the deliverable will be delivered as PDF file, so a zip file will not help here. We could make it available separately in the folder that contains all material under review. https://bscw.rethink-project.eu/bscw/bscw.cgi/25236 Of course then it needs to be properly referenced. The problem might be that this is a public document and that the mentioned folder is password protected. So for later deliverable publication we need to put such a file into a public space.
Tasos
From: pchainho [mailto:notifications@github.com] Sent: Wednesday, September 23, 2015 7:17 PM To: reTHINK-project/core-framework Subject: [core-framework] Runtime APIs (#105)
Move into annex
Add a zip containing jsdoc web documentationhttps://github.com/reTHINK-project/dev-runtime-core/tree/master/Docs, instead?
— Reply to this email directly or view it on GitHubhttps://github.com/reTHINK-project/core-framework/issues/105.
In that case the API Web Documentation can just be published in a web site and references could be just the links to it. We should consider Github Pages to publish APIs documentation. GitHub pages are nicely integrated with github repos. We've also used it in Wonder and published there the Wonder API.
I do not think we should make any API Web Documentation publicly available until the API is final; and we all see that the API might change during the project.
So having a Zip on BSCW where only reviewers have access to should be fine.
Keep in the main body but have after the main procedures section
@emmelmann-fokus we can also put in the bscw a copy
Move into annex
Add a zip containing jsdoc web documentation, instead?