taskSavannah Administration - Tasks: task #16104, Submission of Kissinger 2

 
 

task #16104: Submission of Kissinger 2

Submitted by:  -*- <_289157>
Submitted on:  Sun 02 Jan 2022 12:27:45 PM UTC
Votes:  100  
 
Should Start On:  Sun 02 Jan 2022 12:00:00 AM UTC Should be Finished on:  Wed 12 Jan 2022 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Cancelled Privacy:  Public
Percent Complete:  0% Assigned to:  ineiev
Open/Closed:  Closed Effort:  0.00
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       

 

( Jump to the original submission )

Mon 07 Feb 2022 02:44:15 PM UTC, comment #18: 

The ISC license — https://directory.fsf.org/wiki/License:ISC — which is permissive,

and the 0BSD license — https://landley.net/toybox/license.html — which is public domain,

That's the difference.

-*- <_289157>
Mon 07 Feb 2022 02:21:22 PM UTC, comment #17: 

comment #16:

> You keep missing the difference between works in public domain and  works under a (permissive) license, and this is crucial in order to maintain proper legal notices in your case.
>
> I have to cancel this submission.


The difference is in attribution, which public domain does not require. Therrefore, my license is public domain.

-*- <_289157>
Mon 07 Feb 2022 11:06:23 AM UTC, comment #16: 

You keep missing the difference between works in public domain and  works under a (permissive) license, and this is crucial in order to maintain proper legal notices in your case.

I have to cancel this submission.

Ineiev <ineiev>
Site Administrator
Fri 04 Feb 2022 07:48:19 AM UTC, comment #15: 

comment #14:

> I mean I don't understand your wordings.


This entire license is a wording for public domain (including trademark, patent, and no warranty). What else is supposed to be there that isn't already covered by kissinger2-.tar.gz ?

I am also contacting the owner of stb in attempt to get copyright notice write support in the png engine.

Also, the readme mentions the license applies to * . The use of asterisk for the wildcard could be interpreted to mean it is unusable on Unix systems (which is especially problematic given the Unix text format being used). Is there a better way of expressing this than an asterisk?

-*- <_289157>
Fri 04 Feb 2022 07:39:16 AM UTC, comment #14: 

I mean I don't understand your wordings.

Ineiev <ineiev>
Site Administrator
Fri 04 Feb 2022 07:20:09 AM UTC, comment #13: 

comment #12:

> I don't think this makes sense for me; as I've just said, I don't understand your terms.


You mean you don't understand the license terms?

"The name of <software name> and the names of its contributors may be used to endorse and/or promote products derived from this software. The contributor names include <contributors>." refers to the ability to give credit to the original software while promoting its derivative works (as opposed to the 3-clause BSD license, which does not allow for this), and lists the contributor names.

"All trademark and patent rights held by <software> are waived, abandoned, surrendered, licensed and affected by this document." refers to the grant of trademark and patent rights in addition to copyright.

"This copyright notice and this permission notice do not have to appear in any copies or derivative works." refers to attribution being optional.

"Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted." is what grants the public domain rights.

"THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE." is the warranty disclaimer.

-*- <_289157>
Fri 04 Feb 2022 06:45:08 AM UTC, comment #12: 

I don't think this makes sense for me; as I've just said, I don't understand your terms.

Ineiev <ineiev>
Site Administrator
Fri 04 Feb 2022 06:31:29 AM UTC, comment #11: 

comment #10:

> I'm afraid we fundamentally differ in terminology.  I think I essentially don't understand what you wrote in comment #9.


The public domain rights resemble permissive rights but do not have the attribution requirements. I've heard that in extremely many jurisdictions a raw public domain dedication does not work as expected, so the rights have to be explicitly granted.

-*- <_289157>
Fri 04 Feb 2022 06:09:17 AM UTC, comment #10: 

I'm afraid we fundamentally differ in terminology.  I think I essentially don't understand what you wrote in comment #9.

Ineiev <ineiev>
Site Administrator
Wed 26 Jan 2022 03:25:30 PM UTC, comment #9: 

comment #8:

> Thank you!
>
> It looks like codepagedatabase.cpp doesn't mention it's public domain; it does contain something that looks like a (custom?) permissive license, but then it needs a copyright notice.  Please check other files as well.
>
> Then, what about the PNG files?


The license used in codepagedatabase.cpp is the same as the one in the other cpp files, the difference being it's not called 'public domain license'. The purpose of this license is to grant public domain rights, in fact being an extended version of the 0BSD license.

As for the PNG files, the stb_image_write library does not appear to provide an interface to write copyright notices. Do I have to ask the authors of the library to provide a version with copyright notice write support?

-*- <_289157>
Wed 26 Jan 2022 02:45:31 PM UTC, comment #8: 

Thank you!

It looks like codepagedatabase.cpp doesn't mention it's public domain; it does contain something that looks like a (custom?) permissive license, but then it needs a copyright notice.  Please check other files as well.

Then, what about the PNG files?

Ineiev <ineiev>
Site Administrator
Tue 25 Jan 2022 10:37:56 AM UTC, comment #7: 

Here is the revised version: kissinger2-.tar.gz

Replaced the lodepng dependency with public domain stb_image and stb_image_write which are bundled. Also added contributors in the bdf copyright notice (kissinger2test.bdf and kissinger2ftest.bdf at line 24, generated by makekissinger2.cpp with the copyright strings at line 35 and 36 in the cpp).

(file #52728)

-*- <_289157>
Tue 25 Jan 2022 10:23:05 AM UTC, comment #6: 

comment #5:

>
> It is at line 24 of the bdf.


You are right; still it misses the info about the authors.

Ineiev <ineiev>
Site Administrator
Tue 25 Jan 2022 08:09:49 AM UTC, comment #5: 

comment #4:

> comment #3:
> > BDF is based on a text-like format, and the copyright notice in there is simply "public domain".
>
> I see no such text there.
>


It is at line 24 of the bdf. Note that it is in the Unix text format, not the Microsoft text format. (There should actually be two bdf files, which I will fix in the next build)

-*- <_289157>
Tue 25 Jan 2022 07:01:46 AM UTC, comment #4: 

comment #3:

> There is no 'kissinger2ftest.pdf' in there, there's BDF.


Sorry, I meant bdf.

> BDF is based on a text-like format, and the copyright notice in there is simply "public domain".


I see no such text there.

Please distinguish copyright and license notices, those are two separate things. GNU documentation on legal matters may be useful for you.

> The bdf file is generated with makekissinger2.cpp . What copyright notice would I use for public domain?


There should be just a notice recording its public domain status,  authors and anything else that is relevant,
https://www.gnu.org/prep/maintain/html_node/Non_002dFSF_002dCopyrighted-Package.html#Non_002dFSF_002dCopyrighted-Package
https://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html#Copyright-Notices

> Also, some other public domain licenses like the Unlicense and CC0 also have a warranty disclaimer. So why wouldn't that be compatible in this case?


The Unlicense and CC0 aren't licenses at all, they are public domain dedications, https://www.gnu.org/licenses/license-list.html#Unlicense

However, you are right, the Unlicense does contain such disclaimers (CC0 doesn't); probably this is acceptable.

Ineiev <ineiev>
Site Administrator
Mon 24 Jan 2022 07:22:34 PM UTC, comment #3: 

There is no 'kissinger2ftest.pdf' in there, there's BDF. BDF is based on a text-like format, and the copyright notice in there is simply "public domain". The bdf file is generated with makekissinger2.cpp . What copyright notice would I use for public domain?

Also, some other public domain licenses like the Unlicense and CC0 also have a warranty disclaimer. So why wouldn't that be compatible in this case?

As for the lodepng library, I can replace that with public domain libraries like stb_image.h and stb_image_write.h . But how would I generate copyright notices for the png files?

-*- <_289157>
Mon 24 Jan 2022 04:34:58 PM UTC, comment #2: 

Please add valid legal notices to all files in your package, including files like kissinger2ftest.pdf and PNG files.

In your *.cpp files, you correctly mentioned the contributors, however, public domain isn't a license, it's a state when (in this case) the authors disclaimed their copyright interest. I'm not sure whether it's compatible with statements like

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
THIS SOFTWARE.

Ineiev <ineiev>
Site Administrator
Wed 05 Jan 2022 09:13:20 AM UTC, comment #1: 

Also note that Kissinger 2 is not to be confused with the original Kissinger. Kissinger is a glitchy outdated Unifont clone with bugfixes, whereas Kissinger 2 is an entirely new design.

-*- <_289157>
Sun 02 Jan 2022 12:27:45 PM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves
or discards the registration.

Registration Administration

While this item will be useful to track the registration process,
approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators,
effectively logged as site administrators (superuser):

Registration Details

  • Name: Kissinger 2
  • System Name:  kissinger2
  • Type: non-GNU software and documentation
  • License: Public domain

Description:

Kissinger 2 is a public domain duospaced glyph project (8×16, 16×16) aimed at Unicode/CSUR/UCSUR/… coverage.

Other Software Required:

lodepng+https://github.com/lvandeve/lodepng/blob/master/LICENSE+https://lodev.org/lodepng/

Other Comments:

Kissinger 2 is a Unifont competitor, so it competes with a GNU project. Competition is extremely essential for the free software community.

Tarball URL:

https://savannah.nongnu.org/submissions_uploads/kissinger2.tar.gz

-*- <_289157>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #52728:  kissinger2-.tar.gz added by _289157 (2MiB - application/gzip)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by ineiev (Posted a comment)
  • -email is unavailable- added by _289157 (Voted in favor of this item)
  • -email is unavailable- added by _289157 (Submitted the item)
  •  

    There are 100 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

     

     

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-02-07 ineiev StatusIn Progress => Cancelled
        Open/ClosedOpen => Closed
    2022-01-25 _289157 Attached File- => Added kissinger2-.tar.gz, #52728
    2022-01-24 ineiev StatusNone => In Progress
        Assigned toNone => ineiev
    2022-01-05 _289157 Carbon-Copy- => Added fontdevelopment

    Back to the top


    Powered by Savane 3.9