In preparing for the end of the project, the Project Office would like to make sure that code developed within the project or code improved via the project has proper copyright notices/acknowledgements attached. Please see the guidelines from Steven on what software should be marked. Please identify what software should be subject to the copyright/acknowledgement policy.
"Test" for identifying software packages from Steven Newhouse
If there is a package that originated from outside EGEE, but that we have subsequently contributed to, there should (minimally) be a clear acknowledgement that the EGEE-III project has contributed to the work - by paying individuals or their institutions - and that this work was funded by the EC and by including the grant number. I could see this as being a 2 line acknowledgement in each source code file.
Again for a package that we have contributed to as a (minor) partner, ideally the license that the code is realised under should be as aligned with the EGEE Apache 2 license. This will make it easier for us to manage distributions of code - but this is not something we could demand... but ask nicely!
In these cases we are not trying to grab ownership - just recognition.
Where EGEE has been the clear driver behind the development of the package then standard boilerplate text of license and copyright should appear.
For something like Taverna where our focus has been on a plugin then those source code files should be clearly identified.
Acknowledgement Text
This work has been partially funded by the EU Commission (contract INFSO-RI-222667) under the EGEE-III collaboration (See http://www.eu-egee.org/partners/).