Fix Version/s: None
Component/s: Stack Documentation and UX
The adoption of
RFC-45 requires the documentation is updated to reflect this new approach to copyright tracking.
DM-13565 Put correct copyright/license headers in all jointcal files
- is triggered by
DM-5382 Update template repository with new copyright rules
RFC-45 Process for maintaining Copyright information in DM source code
- relates to
DM-13599 Update copyright info following RFC-45
The confusion on this topic continues so it would be great if we could finally write the plan into the developer guide. Our files are a mess at the moment.
I was pondering having a crack at it today whilst I'm waiting for some butler code to be reviewed.
Tim Jenness go for it. One thing I'd like to see is a list of the legal names for each DM institution that can claim copyright. And a comment on whether very old code was in fact legally copyrighted by the LSST Corporation.
Wil O'Mullane or John Swinbank can you please take a look at these changes to copyright? Since they have an impact on who owns and licenses code I need approval from DM management.
Reviewed on GitHub and approved there by Wil O'Mullane.
I think the remaining major question is what the COPYRIGHT file looks like. There's some text about this in the RFC description, but a sample would be good to look at. I think we did decide that something generic like "LSST DM Participating Institutions" is insufficient, unfortunately.