-
Notifications
You must be signed in to change notification settings - Fork 41
Description
@danielballan and I noticed that GitHub doesn't recognize or label most Bluesky projects as having a BSD 3-Clause license, even though they ship with what we consider a BSD 3-Clause license.
This means they don't get a prominent license tag that identifies the license at the top of the project landing page:
And they also don't get a header providing a quick overview of license features when you view the license file:
Note that this project is correctly recognized. Ophyd, for example, is not.
The reason for this are differences in the LICENSE file, deviating from what GitHub recognizes as a standard BSD 3-Clause license. We think this is worth fixing, as there is both legal and social value in using an established and recognizable license with minimal deviations.
Reference for what GitHub recognizes as standard: BSD 3-Clause
The current LICENSE in this repo matches this exactly, changing only the [year] and replacing [fullname] with "Brookhaven National Laboratory".
The current LICENSE in many other NSLS-II and Bluesky repos has the following differences:
- Missing explicit
BSD 3-Clause Licensedeclaration on line 1 - Names
Brookhaven Science Associatesas copyright holder in addition toBrookhaven National Laboratory - Has
All rights reserved.on same line as copyright, instead of its own line below it - Uses bullet points instead of numbered list of clauses
- Modified Clause 3 to again explicitly name
Brookhaven Science Associates, Brookhaven National Laboratoryas copyright holder, replacing the default reference:the copyright holder
Points 1, 3 and 4 should be straightforward fixes.
Points 2 and 5 require attention.
Once we have answers to the above, the next steps would be:
- Update LICENSE in this repo to comply with requirements
- Ensure updated LICENSE is still recognized by GitHub, fix if not
- Update LICENSEs in other repos to match this one


