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: TrustedQSL [SPDX-Online-Tools] #2518

Closed
davide125 opened this issue Jul 23, 2024 · 8 comments · Fixed by #2552
Closed

New license request: TrustedQSL [SPDX-Online-Tools] #2518

davide125 opened this issue Jul 23, 2024 · 8 comments · Fixed by #2552

Comments

@davide125
Copy link
Contributor

1. License Name: TrustedQSL
2. Short identifier: TrustedQSL
3. License Author or steward: American Radio Relay League, Inc and TrustedQSL Developers
4. Comments: This license is used in Fedora and was found during license review in https://gitlab.com/fedora/legal/fedora-license-data/-/issues/544
5. License Request Url: http://tools.spdx.org/app/license_requests/379
6. URL(s): https://sourceforge.net/p/trustedqsl/tqsl/ci/master/tree/LICENSE.txt
7. OSI Status: Unknown
8. Example Projects: https://www.arrl.org/tqsl

@xsuchy
Copy link
Collaborator

xsuchy commented Jul 23, 2024

License text:

Copyright (C) 2001-2015 American Radio Relay League, Inc. All rights
reserved.

Portions (C) 2003-2023 The TrustedQSL Developers. Please see the AUTHORS.txt
file for contributors.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:

1. Any redistribution of source code must retain the above copyright
notice, this list of conditions and the disclaimer shown in
Paragraph 5 (below).

2. Redistribution in binary form must reproduce the above copyright
notice, this list of conditions and the disclaimer shown in
Paragraph 5 (below) in the documentation and/or other materials
provided with the distribution.

3. Products derived from or including this software may not use
"Logbook of the World" or "LoTW" or any other American Radio Relay
League, Incorporated trademarks or servicemarks in their names
without prior written permission of the ARRL. See Paragraph 6
(below) for contact information.

4. Use of this software does not imply endorsement by ARRL of
products derived from or including this software and vendors may not
claim such endorsement. 

5. Disclaimer: This software is provided "as-is" without
representation, guarantee or warranty of any kind, either express or
implied, including but not limited to the implied warranties of
merchantability or of fitness for a particular purpose. The entire
risk as to the quality and performance of the software is solely
with you. Should the software prove defective, you (and not the
American Radio Relay League, its officers, directors, employees or
agents) assume the entire cost of all necessary servicing, repair or
correction. In no event will ARRL be liable to you or to any third
party for any damages, whether direct or indirect, including lost
profits, lost savings, or other incidental or consequential damages
arising out of the use or inability to use such software, regardless
of whether ARRL has been advised of the possibility of such damages.

6. Contact information:

American Radio Relay League, Inc.
Attn: Logbook of the World Manager
225 Main St
Newington, CT 06111
voice: 860-594-0200
fax: 860-594-0259
email: logbook@arrl.org
Worldwide Web: www.arrl.org

This software consists of voluntary contributions made by many
individuals on behalf of the ARRL. More information on the "Logbook
of The World" project and the ARRL is available from the ARRL Web
site at www.arrl.org.

@jlovejoy
Copy link
Member

jlovejoy commented Aug 8, 2024

This has some BSD-like text, but definitely it's own variant (and looks to be quite old)

+1 to add

Given that the American Radio Relay League copyright is older and "ARRL" is used in various places in the license, I'm wondering if `ARRL' would be a better id?
and maybe American Radio Relay League License for the full name?

@swinslow
Copy link
Member

swinslow commented Aug 8, 2024

+1 to add

Looks like there have been several variations over time for this one. A bit of history from some digging:

So, regarding the name:

Given the above, I'm sort of inclined to go with LOTW for the identifier and "LOTW License" as the longer name, mostly to crib from the decision that Gentoo already made?

But if folks feel more strongly about using TrustedQSL, I'm fine with that, as these all appear to be related.

I might not go with ARRL, mostly out of not knowing whether ARRL as an organization may have released other software under different licenses.

@richardfontana
Copy link
Contributor

Apparently Logbook of the World refers to an associated dataset of some sort maintained by ARRL, so for that reason I'd be inclined to go with TrustedSQL.

@swinslow swinslow modified the milestones: 3.25.0, 3.26.0 Aug 19, 2024
@karsten-klein
Copy link

{metæffekt} Universe
canonical name: TrustedQSL License
short name: TrustedQSL-License
markers: General Terms Matches Marker
category: TrustedQSL
OSI status: none

Comment
+1 to add.

@jlovejoy
Copy link
Member

jlovejoy commented Aug 22, 2024

License Inclusion Decision

Decision:

  • approved
  • not approved

Name

TrustedQSL License

License ID

TrustedQSL

XML markup

none at this time

Notes:

none at this time

Next steps

If the license has been accepted, please follow the accepted-license process to create the PR.

@davide125
Copy link
Contributor Author

Used the online tool to make #2552 for this

Copy link

This new license/exception request has been accepted and the information for the license/exception has been merged to the repository. Thank you to everyone who has participated!
The license/exception will be published at https://spdx.org/licenses/ as part of the next SPDX License List release, which is expected to be in three months' time or sooner. In the interim, the new license will appear on the license list preview site at https://spdx.github.io/license-list-data/.
This is an automated message.

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.

6 participants