Skip to content
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

Software licensing #26

Closed
JBodera opened this issue Feb 1, 2019 · 2 comments
Closed

Software licensing #26

JBodera opened this issue Feb 1, 2019 · 2 comments
Assignees

Comments

@JBodera
Copy link
Contributor

JBodera commented Feb 1, 2019

During the PMC 29/01/2019 and within WP4 @jamhall discussed what licensing to use for all the different software that will be produced.

Ideally the software licenses must be harmonised, so we do not have problems with incompatible licenses
@fangohr asked what the proposal said about licenses

It was also said that Jupyter uses MIT-BSD license

@JBodera
Copy link
Contributor Author

JBodera commented Feb 1, 2019

Just for reference, the proposal says in section 2.2.a.3 Open Source Software the following:
All software developed in the course of the project will be under version control in an open source repository (such as GitHub) and licensed under a license compliant with the Open Source Initiative (OSI, www.opensource.org). The software will thus be Findable and Accessible and because it also will be developed with Inter-operability and Reuability in mind, the software will be FAIR in its own right.
All public deliverables will be made available and accessible from the project’s website.

@JBodera
Copy link
Contributor Author

JBodera commented Feb 28, 2019

During the PMC 27/02/2019 it was agreed that:

  • Existing software will continue with its license
  • New software will use an open source license (e.g. MIT)

It is encouraged that WP leaders inform the Project Management Committee of the software license chosen for new developments.

@JBodera JBodera closed this as completed Feb 28, 2019
perrin1024 added a commit that referenced this issue Jul 27, 2020
perrin1024 added a commit that referenced this issue Aug 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants