Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-5383

Update developer docs with Copyright instructions

    XMLWordPrintable

    Details

    • Team:
      Architecture

      Description

      The adoption of RFC-45 requires the documentation is updated to reflect this new approach to copyright tracking.

        Attachments

          Issue Links

            Activity

            Hide
            ktl Kian-Tat Lim added a comment -

            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.

            Show
            ktl Kian-Tat Lim added a comment - 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.
            Hide
            tjenness Tim Jenness added a comment -

            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.

            Show
            tjenness Tim Jenness added a comment - 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.
            Hide
            jsick Jonathan Sick added a comment -

            I'll try to get this done before the DM All Hands.

            Show
            jsick Jonathan Sick added a comment - I'll try to get this done before the DM All Hands.
            Hide
            tjenness Tim Jenness added a comment -

            I was pondering having a crack at it today whilst I'm waiting for some butler code to be reviewed.

            Show
            tjenness Tim Jenness added a comment - I was pondering having a crack at it today whilst I'm waiting for some butler code to be reviewed.
            Hide
            jsick Jonathan Sick added a comment -

            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.

            Show
            jsick Jonathan Sick added a comment - 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.
            Hide
            tjenness Tim Jenness added a comment -

            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.

            Show
            tjenness Tim Jenness added a comment - 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.
            Hide
            tjenness Tim Jenness added a comment -

            Reviewed on GitHub and approved there by Wil O'Mullane.

            Show
            tjenness Tim Jenness added a comment - Reviewed on GitHub and approved there by Wil O'Mullane .

              People

              Assignee:
              tjenness Tim Jenness
              Reporter:
              tjenness Tim Jenness
              Reviewers:
              John Swinbank, Wil O'Mullane
              Watchers:
              John Parejko, John Swinbank, Jonathan Sick, Kian-Tat Lim, Tim Jenness, Wil O'Mullane
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.