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

Add missing license, add list of third-party requirements and licenses in case they differ #54

Open
benjamir opened this issue Jun 30, 2017 · 1 comment
Assignees
Milestone

Comments

@benjamir
Copy link
Member

As of Mar 24, 2017 our licensing policy for

  • Software: permissive licenses (MIT or BSD) if possible
  • Resources: CC-BY if possible.

"
There is an ongoing group-intern debate on whether source code (e.g., the JCoRe code we distribute via GitHub) must comply with the licenses of the employed libraries if those are not included in the distribution and instead only referenced as a maven dependency (that would mean that using the API in the source makes the the source a derivative) or the source code rather constitutes a work of its own and only building the project merges source and libraries (thus constituting a derivative).
"

Anyways, I would recommend setting the BSD-2 clause license now and a prominent note at the top of the REAMDE that third party libraries might have different licenses -- better: make a list of all the third-party dependencies and their licenses respectively.

@egrygorova egrygorova added this to the 2.3 milestone Aug 2, 2017
@egrygorova
Copy link
Contributor

what are third-party-dependencies for example?

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