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

New license request: Inner-Net-2.0 [SPDX-Online-Tools] #1987

Closed
jlovejoy opened this issue Jun 1, 2023 · 3 comments · Fixed by #2007
Closed

New license request: Inner-Net-2.0 [SPDX-Online-Tools] #1987

jlovejoy opened this issue Jun 1, 2023 · 3 comments · Fixed by #2007

Comments

@jlovejoy
Copy link
Member

jlovejoy commented Jun 1, 2023

1. License Name: Inner Net License v2.0
2. Short identifier: Inner-Net-2.0
3. License Author or steward: Unknown
4. Comments: This is an older license that is approved and used in Fedora. I think it meets the inclusion principles.

See https://gitlab.com/fedora/legal/fedora-license-data/-/issues/16
5. License Request Url: http://tools.spdx.org/app/license_requests/236
6. URL(s): https://fedoraproject.org/wiki/Licensing/Inner_Net_License
7. OSI Status: Unknown
8. Example Projects: https://www.gnu.org/software/libc/sources.html

@swinslow
Copy link
Member

swinslow commented Jun 8, 2023

Copy of license text for easier viewing:

The Inner Net License, Version 2.00

  The author(s) grant permission for redistribution and use in source and
binary forms, with or without modification, of the software and documentation
provided that the following conditions are met:

0. If you receive a version of the software that is specifically labelled
   as not being for redistribution (check the version message and/or README),
   you are not permitted to redistribute that version of the software in any
   way or form.
1. All terms of the all other applicable copyrights and licenses must be
   followed.
2. Redistributions of source code must retain the authors' copyright
   notice(s), this list of conditions, and the following disclaimer.
3. Redistributions in binary form must reproduce the authors' copyright
   notice(s), this list of conditions, and the following disclaimer in the
   documentation and/or other materials provided with the distribution.
4. [The copyright holder has authorized the removal of this clause.]
5. Neither the name(s) of the author(s) nor the names of its contributors
   may be used to endorse or promote products derived from this software
   without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY ITS AUTHORS AND CONTRIBUTORS ``AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

  If these license terms cause you a real problem, contact the author.

@swinslow
Copy link
Member

swinslow commented Jun 8, 2023

The preamble, clauses 2-5 and the disclaimer appear to be equivalent to BSD-3-Clause (haven't compared whether identical, but roughly the same).

Clause 1 seems kind of meaningless, but fine.

Clause 0 is the only one that gives me pause. It appears to suggest that something could be licensed under this license but also separately marked as "not for redistribution", and then prohibited for redistribution. Is that the intent here?

Given that it's approved for use in Fedora, I'm assuming that whatever software is used in Fedora doesn't have this "not for redistribution" tag.

Clause 0 is a bit odd, but given its use in Fedora I'm cautiously a +1 to add this to the license list.

@jlovejoy
Copy link
Member Author

jlovejoy commented Jun 8, 2023

used in glibc - discussed on 6/8 call - accepted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants