End of a Project

As this kind of documentation is only valuable if engineers can freely share their opinions and experiences (also negative ones!), this document itself is not meant for external distribution.

• high-level description of actual escience requirements in the project
• what went great, what could have gone better
• pointers (URL) to project documentation
• motivation for chosen approach,
• high-level description of used or developed tools and references to them (github, website, )

• escience engineer(s) working on the project

• escience engineers
• escience coordinators

• should be written during the last weeks of the project
• Stored on the internal sharepoint site

Support

After a project has finished the eScience Center will in principle not further support the software. Reported bugs in our own software will of course have a high chance of being looked at, but this also has its limits. We cannot in any way contribute to the administration of infrastructure needed after a project has ended.

For in-house developed eStep software we do provide some support, though even here only limited time is available for this. See the technology page on the website () for the list of supported software.