-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
License changed from BSD to MIT without permission #15
Comments
@sparrowt - Yes, tracking this issue here is recommended. Thanks |
I noticed that LICENSE.txt has now been reverted to BSD 3-Clause by 4dfb39c, thank you! For some reason GitHub isn't displaying the license 'infobox' at the top of https://github.com/microsoft/mssql-django/blob/dev/LICENSE.txt (whereas for example the parent of this fork does) - see here re auto-detection - possibly due to this extra line at the top:
|
The other thing mentioned in the description of this issue is the copyright notice - unfortunately this still says simply:
which doesn't acknowledge the years of work by the following (from previous license files linked above):
though I realise this may be more of a grey area, but I thought I'd point it out. |
@sparrowt - Thanks for your patience - I've now updated the License.txt file in the dev branch to account for the historical copyright notices. This will be merged this week and be part of the subsequent releases. |
Filing this as a separate issue so it doesn't get lost in a comment thread on the repo from which this was forked:
ESSolutions/django-mssql-backend#91 (comment)
Thank you @vwarchu for the response:
I trust this ticket can serve to track resolving this issue.
As well as re-instating the license it would be appropriate (if not required - I'll let you talk to the lawyers!) to retain the Copyright lines from each fork in the chain, especially the original "django-pyodbc developers" one, to acknowledge their contributions over many years - rather than just replacing them all with "Copyright (c) Microsoft Corporation" on its own which I believe is incorrect.
The text was updated successfully, but these errors were encountered: