Today in the DM Developer Guide you’ll find a few new pages that describe how to manage licenses and copyrights in DM’s open source projects. This content isn’t entirely new—we’ve lifted it out of another page that we’re about to replace—but we’ve also expanded its scope. If you have any questions about how to set copyrights or licenses, please take a moment to review these docs.
For Stack developers
Most of us work on some part of the DM Stack, which is a GPL-3.0-licensed project. We’ve created a one-page overview of how licensing and copyrights work in packages:
This documentation follows the practices adopted in RFC-45, which is different from how we’ve traditionally asserted copyright and licensing in packages. I’m not aware of how individual DM teams are managing this transition, but in general, developers can transition their packages to this new, more efficient style immediately.
We’ve also created a new section in the Developer Guide called “Legal” to document policy on open source licensing and copyright and how to apply these concepts:
Bonus: directory-based Git configuration
We’ve also updated the Git settings page to mention directory-based conditional Git configuration. This is a great way to have Git use your institutional email address for commits whenever you’re working on LSST projects.