taskSavannah Administration - Tasks: task #16238, Submission of Fidei - Take back...

 
 

task #16238: Submission of Fidei - Take back your faith

Submitter:  Florian sp1rit <sp1rit>
Submitted:  Fri 29 Jul 2022 06:23:44 PM UTC
 
Should Start On:  Fri 29 Jul 2022 12:00:00 AM UTC Should be Finished on:  Mon 08 Aug 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 )

Thu 06 Oct 2022 08:46:41 AM UTC, comment #8: 

If there is no further interest, I'll cancel this submission.

Ineiev <ineiev>
Site Administrator
Thu 15 Sep 2022 07:05:57 PM UTC, comment #7: 

comment #6:

> Yes, that isn't the issue for myself, but for inclusion in distribution repositories.


Then I would suggest that it's distribution's problem rather than yours, it's pointless to solve it on your side.

> The GNU License List does list the CC BY-SA 4.0 as one way compatible with the GPLv3. But that isn't really what I need. I'd like some kind of resource that tells me how to proceed (license header wise)


Please check the pages https://savannah.gnu.org/maintenance/ValidNotices/ links to, if you are really curious.

> Would something like what Qt5 is doing be fine?..


If you were contributing to Qt5 code, you would be expected to follow their conventions; if you want to host your package on Savannah, you should comply with our requirements.

> yes, but these aren't really source files, but rather resource files.


Still you care of their size, you should strip all parts that don't affect the features when building the .data section of the binary.

Ineiev <ineiev>
Site Administrator
Tue 06 Sep 2022 08:03:28 PM UTC, comment #6: 

comment #5:

> I'm out of context.  AppStream is a free software, isn't it?  Then one can modify that function to include any strings needed.
>


Yes, that isn't the issue for myself, but for inclusion in distribution repositories. The argument is, that because distros will merge various metainfo files together, "it is not feasible to test every copyleft license for mutual compatibility and compliance when combining metainfo metadata with other data into one larger assembly fully automatically" [0] and I guess it just doesn't work legally with the GPL family of licenses. (the CC-BY-SA seems to me like a decent copyleft option available; as this isn't source code anyways)

> > The page you linked doesn't really specify how to handle such a "dual licensing" case.
>
> You have to understand what the licenses you use imply and how they combine.  For more info, you can check the GPL FAQ and the GNU License List.
>


The GNU License List does list the CC BY-SA 4.0 as one way compatible with the GPLv3. But that isn't really what I need. I'd like some kind of resource that tells me how to proceed (license header wise) in cases where I explicitly licensed files under both the AGPL-3.0 and CC-BY-SA-4.0.

Would something like what Qt5 is doing be fine? (but obviously with exclusively free licenses)
```
// Copyright (C) 2020 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR LGPL-3.0-only OR GPL-2.0-only OR GPL-3.0-only

(--- BEGIN SOURCE ---)
```
as that would also solve the other issue.

> Comments in source code shouldn't affect the size of the executable; if they do and the size is important, then you should reconsider your building process.  The developer shouldn't compromise between source code readability and the efficiency of the translated binary.


yes, but these aren't really source files, but rather resource files. Think of it like a tar file with a bunch of necessary resources contained within. But instead of it being a file on the systems filesystem, the contents of the file are part of the .data section of the binary.

[0]: https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-metadata_license

Florian sp1rit <sp1rit>
Tue 06 Sep 2022 07:01:29 PM UTC, comment #5: 

comment #4:

>
> The thing with the CC-BY-SA-4.0 is, that AppStream requires the metadata to be licensed under a few specific licenses[0], AGPL-3.0 not being one of them.


I'm out of context.  AppStream is a free software, isn't it?  Then one can modify that function to include any strings needed.

> The page you linked doesn't really specify how to handle such a "dual licensing" case.


You have to understand what the licenses you use imply and how they combine.  For more info, you can check the GPL FAQ and the GNU License List.

> All files that carry "This file is distributed under the same license as Fidei" end up inside the binary (via GResource), so I'd like to avoid having the same half a kilobyte of license header a bunch of times in the compiled binary. Is there an alternative shorter form of the AGPL-3.0 license header I could use instead?


Comments in source code shouldn't affect the size of the executable; if they do and the size is important, then you should reconsider your building process.  The developer shouldn't compromise between source code readability and the efficiency of the translated binary.

Ineiev <ineiev>
Site Administrator
Sun 04 Sep 2022 06:35:00 PM UTC, comment #4: 

comment #3:

> Thanks, but I'm afraid, no, it wasn't fixed.
>
> Please use a canonical form of the license notices, "This file is distributed under the same license as Fidei" won't do, and the addition "and CC-BY-SA-4.0" makes it really confusing; whenever you use a license that isn't included in the license notice (like many permissive licenses), you should add a copy of that license to your tarball; I can't find licenses for files in screenshots/, and so on.  Please check the link from comment #1  again.


The thing with the CC-BY-SA-4.0 is, that AppStream requires the metadata to be licensed under a few specific licenses[0], AGPL-3.0 not being one of them. The page you linked doesn't really specify how to handle such a "dual licensing" case.

All files that carry "This file is distributed under the same license as Fidei" end up inside the binary (via GResource), so I'd like to avoid having the same half a kilobyte of license header a bunch of times in the compiled binary. Is there an alternative shorter form of the AGPL-3.0 license header I could use instead?

[0]: https://github.com/ximion/appstream/blob/eb6891e7447be28ee123bfd4a1a6db9aa8085dc8/src/as-spdx.c#L539

Florian sp1rit <sp1rit>
Sun 14 Aug 2022 05:19:44 PM UTC, comment #3: 

Thanks, but I'm afraid, no, it wasn't fixed.

Please use a canonical form of the license notices, "This file is distributed under the same license as Fidei" won't do, and the addition "and CC-BY-SA-4.0" makes it really confusing; whenever you use a license that isn't included in the license notice (like many permissive licenses), you should add a copy of that license to your tarball; I can't find licenses for files in screenshots/, and so on.  Please check the link from comment #1  again.

Ineiev <ineiev>
Site Administrator
Fri 12 Aug 2022 07:57:46 PM UTC, comment #2: 

comment #1:

> Please make sure that all copyrightable files in your tarball
> have valid copyright and license notices; also, please include a plain text version of your license in your tarball.


should be fixed now

Florian sp1rit <sp1rit>
Fri 12 Aug 2022 06:37:55 AM UTC, comment #1: 

Please make sure that all copyrightable files in your tarball
have valid copyright and license notices; also, please include a plain text version of your license in your tarball.

Ineiev <ineiev>
Site Administrator
Fri 29 Jul 2022 06:23:44 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: Fidei - Take back your faith
  • System Name:  fidei
  • Type: non-GNU software and documentation
  • License: GNU Affero General Public License v3 or later

Description:

Fidei is a graphical software utility for reading the bible (to be more precise, any bible) in Zefania XML (https://www.bgfdb.de/zefaniaxml/bml/) format on GNU based operating systems running the GNOME platform (altho it should work on X11/XFree64 or any Wayland based compositor).

Being written in C, it also offers a small binary size (the current nightly package has a filesize of 55.1kB) and a low-ish memory footprint.

It was designed from the ground up to offer a simple, pleasant and intuitive reading experience with the actual content resembling the look of modern printed bibles.

Due to Fidei making use of libadwaita, it will also work on touch and small screens of mobile devices running the GNU operating system with X or Wayland, should any such devices work properly in the future.

---

There aren't any other free applications out there that aim to achieve a similar goal to Fidei. The closest one might be BibleTime (https://bibletime.info/), which is less for just reading and more intended for study and comparison between different versions. It is also visually less appealing and unlikely to work on mobile devices.

Other Software Required:

glib, LGPL-2.1, https://gitlab.gnome.org/GNOME/glib
pango, LGPL-2.1, https://gitlab.gnome.org/GNOME/pango
gtk4, LGPL-2.1, https://gitlab.gnome.org/GNOME/gtk
libadwaita, LGPL-2.1, https://gitlab.gnome.org/GNOME/libadwaita
libxml2, MIT, https://gitlab.gnome.org:GNOME/libxml2
libicu (optional), Unicode/ICU, https://github.com/unicode-org/icu

meson, Apache-2.0, https://mesonbuild.com
ninja, Apache-2.0, https://ninja-build.org

Tarball URL:

https://github.com/sp1ritCS/fidei/archive/refs/heads/master.tar.gz

Florian sp1rit <sp1rit>

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

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 sp1rit (Submitted the item)
  •  

    There are 0 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 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-12-02 ineiev StatusIn Progress Cancelled
        Open/ClosedOpen Closed
    2022-08-12 ineiev StatusNone In Progress
        Assigned toNone ineiev

    Back to the top


    Powered by Savane 3.9