-
Notifications
You must be signed in to change notification settings - Fork 12
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
Sphinxify licensing #20
Comments
Thanks for the very detailed breakdown, @jasongrout ! @ccordoba12 Might be a good idea to add a brief note to the License section of the Readme summarizing this as it directly relates to docrepr and linking here for more information, if @jasongrout wants to submit a PR...but I leave that up to you. |
Should we close this then? |
I was going to add a mention and a link to this in the Readme in #37 |
Sorry for chiming in so late here, but I'd like to thank @jasongrout for clarifying the licensing situation of this project. I'd also like to add a bit more context to this part
Actually, I found about This is also why the first version of https://github.com/spyder-ide/spyder/blob/master/spyder/plugins/help/utils/sphinxify.py One day we hope to integrate this project with Spyder as well. |
I was tracking down the history of the sphinxify licensing to clarify how this sphinxify module is BSD while the core Sage sphinxify is currently GPLv2+. Here is what I found:
I don't think there is anything to do and this ticket can be closed immediately, but I just wanted to document the history to prevent confusion.
Personal side note: If I recall correctly, I remember having a conversation about the BSD license on the original sphinxify module at SageDays 19 with Tim and a few others, where we decided it would be fine to have a BSD-licensed file in the Sage Notebook codebase, but that we'd just make sure that file explicitly stated it had the BSD license
The text was updated successfully, but these errors were encountered: