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

Clarify license #197

Closed
Totktonada opened this issue Dec 7, 2021 · 1 comment · Fixed by #210
Closed

Clarify license #197

Totktonada opened this issue Dec 7, 2021 · 1 comment · Fixed by #210
Assignees
Labels
code health Improve code readability, simplify maintenance and so on

Comments

@Totktonada
Copy link
Member

I would like to resolve several problems here.

The first one is that README.rst states that Tarantool is 'BSD licensed' (which is ambiguous, but correct) and links to the Modified BSD license (which is incorrect). The Modified BSD license is BSD-3-Clause, while Tarantool is licensed under BSD-2-Clause. Check it out: https://github.com/tarantool/tarantool/commits/master/LICENSE. It would be nice to correctly refer BSD-2-Clause and, preferably, without GNU Project comments on it.

Next, tarantool-python license is not defined neither in README.rst, nor in the LICENSE file. I really doubt that anyone meant a license that is different from tarantool's one, so I hope I can assume that this project is licensed under BSD-2-Clause. I propose to add the LICENSE file with BSD-2-Clause license with shared copyright attributed to tarantool-python authors, add the AUTHORS file with the list of all contributors (why not?) and refer to the license file from README.rst explicitly calling the license using the well known SPDX identifier (BSD-2-Clause).

The project refers 'BSD' in setup.py:

license="BSD",

"License :: OSI Approved :: BSD License",

It is ambiguous: which one of the BSD family? However, it seems, there is no recommended way to resolve this ambiguity within setup.py: pypa/trove-classifiers#17. I propose to leave it as is until the problem will be resolved on the python packaging infrastructure/tooling side.

@Totktonada Totktonada added the code health Improve code readability, simplify maintenance and so on label Dec 7, 2021
@Totktonada
Copy link
Member Author

@coxx I would like to know your opinion on it and, if it would not be too sticky, formal agreement with the statement that the project was always licensed under BSD-2-Clause and had no clear statement about this just by mistake.

Totktonada added a commit that referenced this issue Feb 17, 2022
The readme file wrongly refers to the BSD-3-Clause license. Tarantool
was always licensed under BSD-2-Clause, it is just a mistake.

See details in the linked issue.

Part of #197
Totktonada added a commit that referenced this issue Feb 17, 2022
The readme file (updated) refers to the license file (added), which
refers to the authors file (added).

Fixes #197
Totktonada added a commit that referenced this issue Feb 18, 2022
The readme file wrongly refers to the BSD-3-Clause license. Tarantool
was always licensed under BSD-2-Clause, it is just a mistake.

See details in the linked issue.

Part of #197
Totktonada added a commit that referenced this issue Feb 18, 2022
The readme file (updated) refers to the license file (added), which
refers to the authors file (added).

Fixes #197
Totktonada added a commit that referenced this issue Feb 18, 2022
The readme file wrongly refers to the BSD-3-Clause license. Tarantool
was always licensed under BSD-2-Clause, it is just a mistake.

See details in the linked issue.

Part of #197
Totktonada added a commit that referenced this issue Feb 18, 2022
The readme file (updated) refers to the license file (added), which
refers to the authors file (added).

Fixes #197
@Totktonada Totktonada self-assigned this Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code health Improve code readability, simplify maintenance and so on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant