[Savannah-register-public] [task #13173] Chromium vs. Savannah mens

2014-03-30 Thread INVALID.NOREPLY
Follow-up Comment #6, task #13173 (project administration):

OK I can reproduce it on my jidanni2 machine but not my jidanni3 machine. I
still have to test my jidanni3 and jidanni6 machines...

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/




[Savannah-register-public] [task #13173] Chromium vs. Savannah mens

2014-03-31 Thread INVALID.NOREPLY
Follow-up Comment #7, task #13173 (project administration):

OK I submitted https://code.google.com/p/chromium/issues/detail?id=358499

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/




[task #15687] Submission of ChingKong Technology CO.,Ltd.

2020-06-11 Thread INVALID.NOREPLY
URL:
  

 Summary: Submission of ChingKong Technology CO.,Ltd.
 Project: Savannah Administration
Submitted by: chingkong
Submitted on: Fri 12 Jun 2020 02:22:53 AM UTC
 Should Start On: Fri 12 Jun 2020 12:00:00 AM UTC
   Should be Finished on: Mon 22 Jun 2020 12:00:00 AM UTC
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

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):

* Group Administration



= Registration Details =

* Name: *ChingKong Technology CO.,Ltd.*
* System Name:  *jammer*
* Type: non-GNU software and documentation
* License: GNU General Public License v3 or later



== Description: ==
Which is a professional manufacturer of indoor wireless signal jammer?

Ching Kong Technology Co., Limited. is original manufacturer of indoor
wireless signal jammer, GPS Jammers, WiFi/Bluetooth signal Jammers,Prison
Jamming system, Handheld Jammers Solutions,Drone Signal Jammer,UAV
Detector&Defend System and so on


== Other Software Required: ==
https://www.szckt.com/


== Tarball URL: ==
https://www.szckt.com/






___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15735] Submission of Open project and Mattermost integration

2020-07-23 Thread INVALID.NOREPLY
URL:
  

 Summary: Submission of Open project and Mattermost
integration
 Project: Savannah Administration
Submitted by: girishm
Submitted on: Thu 23 Jul 2020 07:03:44 AM UTC
 Should Start On: Thu 23 Jul 2020 12:00:00 AM UTC
   Should be Finished on: Sun 02 Aug 2020 12:00:00 AM UTC
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

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):

* Group Administration



= Registration Details =

* Name: *Open project and Mattermost integration*
* System Name:  *op-mattermost*
* Type: non-GNU software and documentation
* License: Other license (This is free and unencumbered software released into
the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or
distribute this software, either in source code form or as a compiled
binary, for any purpose, commercial or non-commercial, and by any
means.

In jurisdictions that recognize copyright laws, the author or authors
of this software dedicate any and all copyright interest in the
software to the public domain. We make this dedication for the benefit
of the public at large and to the detriment of our heirs and
successors. We intend this dedication to be an overt act of
relinquishment in perpetuity of all present and future rights to this
software under copyright law.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

For more information, please refer to )



== Description: ==
An integration between OpenProject (www.openproject.org) and Mattermost
(www.mattermost.org). This project aims at enabling RESTful APIs of
OpenProject in Mattermost through interactive slash commands.
Currently, supports logging time for a work-package in OpenProject using a
slash command (/logtime) created in Mattermost.

op-mattermost is a Node Express application written in JavaScript ES6.


== Other Software Required: ==
"axios": "^0.19.2", https://www.npmjs.com/package/axios, Expat/MIT license,
www.github.com/axios/axios

"dotenv": "^8.2.0", BSD-2-Clause license,
www.github.com/motdotla/dotenv#readme

"express": "^4.17.1", Expat/MIT license, www.expressjs.com

"moment": "^2.24.0", Expat/MIT license, www.momentjs.com

"nodemon": "^2.0.2", Expat/MIT license, www.nodemon.io

"chai": "^4.2.0", Expat/MIT license, www.chaijs.com

"mocha": "^7.1.1", Expat/MIT license, www.mochajs.org

"should": "^13.2.3", Expat/MIT license, www.github.com/shouldjs

"sinon": "^9.0.1", BSD-3-Clause license, www.sinonjs.org

"supertest": "^4.0.2", Expat/MIT license,
www.github.com/visionmedia/supertest

"ngrok": Apache 2.0 license, www.ngrok.com

"docker": Apache License, Version 2.0, www.docker.com



== Other Comments: ==
This project is already hosted at https://github.com/girish17/op-mattermost .
A mirror of the project at savannah non gnu is sought for, as it runs on
completely free software.


== Tarball URL: ==
https://github.com/girish17/op-mattermost/archive/master.zip






___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15735] Submission of Open project and Mattermost integration

2020-07-23 Thread INVALID.NOREPLY
Follow-up Comment #2, task #15735 (project administration):

I
 would be using savannah non gnu for development purposes from here on 
with this project. It is not just a back up. Currently, only one feature
 is available in this project and the rest would be developed and hosted
 through savannah non gnu.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15735] Submission of Open project and Mattermost integration

2020-07-29 Thread INVALID.NOREPLY
Follow-up Comment #4, task #15735 (project administration):

I would like to withdraw my submission. It seems to me that the project is
better equipped to be hosted at its current location than at Savannah non GNU.
It was not intended to be a free software in the first place (when it started)
and now trying to make it one through licenses (I barely understand), is
something I wouldn't want to try. Thank you for the insights and your valuable
time.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15828] Submission of Mirror Port

2020-12-02 Thread INVALID.NOREPLY
URL:
  

 Summary: Submission of Mirror Port
 Project: Savannah Administration
Submitted by: salahuddin
Submitted on: Wed 02 Dec 2020 10:01:36 PM UTC
 Should Start On: Wed 02 Dec 2020 12:00:00 AM UTC
   Should be Finished on: Sat 12 Dec 2020 12:00:00 AM UTC
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

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):

* Group Administration



= Registration Details =

* Name: *Mirror Port*
* System Name:  *mirror-port*
* Type: non-GNU software and documentation
* License: GNU General Public License v3 or later



== Description: ==
Purpose: This program allows users to mirror a local port to a remote server.

Topic: TCP networking, socket, client-server

Example use case (there are many): You are behind a firewall and want to show
your local HTTP server for demo. You can mirror your local port 80 to a remote
server with public IP without administrative privileges.

Programming language: C

Special about it: You connect to a remove server using a client application,
but your system will act as a server for the users.



== Other Software Required: ==
port-mirror-0.1a/src/common/base64.(c|h) MIT License
https://github.com/joedf/base64.c

GnuTLS  LGPLv2.1+ https://gnutls.org/


== Other Comments: ==
I implemented it for my personal use.

Use case: Instead of installing Nominatim (openstreetmap) in cloud, we
installed it in a local machine and was able to show a demo.


== Tarball URL: ==
https://demo.minmaxopt.com/port-mirror-0.1a.tar.gz






___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15828] Submission of Mirror Port

2020-12-03 Thread INVALID.NOREPLY
Follow-up Comment #2, task #15828 (project administration):

[comment #1 comment #1:]
> All copyrightable files in your tarball should have valid copyright and
license notices ,
including files like INSTALL and src/common/base64.[ch].
I will add notice in INSTALL.
There is a copyright notice from original author in src/common/base64.[ch]. I
did not modify it.

Did you mean I should reformat copyright text add full "MIT License" in
base64.[ch] ?


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15828] Submission of Mirror Port

2020-12-03 Thread INVALID.NOREPLY
Follow-up Comment #3, task #15828 (project administration):


[comment #1 comment #1:]
> All copyrightable files in your tarball should have valid copyright and
license notices ,
including files like INSTALL and src/common/base64.[ch].

update:
https://demo.minmaxopt.com/port-mirror-0.1.1a.tar.gz

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15828] Submission of Mirror Port

2020-12-10 Thread INVALID.NOREPLY
Additional Item Attachment, task #15828 (project administration):

File name: port-mirror-0.1.1a.tar.gz  Size:25 KB
   




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15828] Submission of Mirror Port

2020-12-10 Thread INVALID.NOREPLY
Follow-up Comment #5, task #15828 (project administration):


[comment #4 comment #4:]
> The first file I've checked lacked them; have you attached the right
tarball?

Yes. Please let me know if you have any issue accessing it.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15828] Submission of Mirror Port

2020-12-11 Thread INVALID.NOREPLY
Follow-up Comment #7, task #15828 (project administration):


[comment #6 comment #6:]
> The issue is not with file access, it's with missing copyright and license
notices.
>Thu 03 Dec 2020 08:26:46 AM UTC, comment #1: 

>All copyrightable files in your tarball should have valid >copyright and
license notices, including files like INSTALL and >src/common/base64.[ch].


port-mirror-0.1.1a.tar.gz

I already added copyright and license as you suggested in INSTALL and
base64.[ch].

Please let me know if I missed anything else.
Thank you.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15828] Submission of Mirror Port

2020-12-13 Thread INVALID.NOREPLY
Follow-up Comment #8, task #15828 (project administration):

https://savannah.nongnu.org/task/download.php?file_id=50431

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15828] Submission of Mirror Port

2020-12-14 Thread INVALID.NOREPLY
Additional Item Attachment, task #15828 (project administration):

File name: port-mirror-0.1.2a.tar.gz  Size:25 KB
   




___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #15828] Submission of Mirror Port

2020-12-14 Thread INVALID.NOREPLY
Follow-up Comment #10, task #15828 (project administration):


[comment #9 comment #9:]
> You should be able to identify files with missing copyright and license
notices yourself.  Please check all files, your tarball is quite small.

Update:
https://savannah.nongnu.org/task/download.php?file_id=50459

Thank you.

___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.nongnu.org/




[task #16037] Submission of Agena-board

2021-08-24 Thread INVALID.NOREPLY
URL:
  

 Summary: Submission of Agena-board
 Project: Savannah Administration
Submitted by: comatoast
Submitted on: Tue 24 Aug 2021 04:32:43 PM UTC
 Should Start On: Tue 24 Aug 2021 12:00:00 AM UTC
   Should be Finished on: Fri 03 Sep 2021 12:00:00 AM UTC
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

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):

* Group Administration



= Registration Details =

* Name: *Agena-board*
* System Name:  *agenaboard*
* Type: non-GNU software and documentation
* License: GNU General Public License v3 or later



== Description: ==
AegnaBoard is a Free and Open Source Text board for the gemini protocol.


== Other Comments: ==
AegnaBoard is a Free and Open source text board for the Gemini protocol based
on Haskell that is hosted on a GPLv3 license and is dedicated to Free and Open
source software.


== Tarball URL: ==
AegnaBoard






___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[task #16184] Submission of Audio Broadcast

2022-05-07 Thread INVALID.NOREPLY
URL:
  

 Summary: Submission of Audio Broadcast
 Project: Savannah Administration
Submitted by: xsbee
Submitted on: Sat 07 May 2022 06:01:09 PM UTC
 Should Start On: Sat 07 May 2022 12:00:00 AM UTC
   Should be Finished on: Tue 17 May 2022 12:00:00 AM UTC
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

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):

* Group Administration



= Registration Details =

* Name: *Audio Broadcast*
* System Name:  *audcast*
* Type: non-GNU software and documentation
* License: GNU General Public License v3 or later



== Description: ==
A minimal UNIX program written in C for streaming of MP2 audio over
UDP(-Lite), with optionally broadcast. It transmits one MP2 frame per
datagram.


== Other Software Required: ==
TwoLAME (GPLv2.1, https://www.twolame.org/)


== Other Comments: ==
This project is primarily developed on FreeBSD.


== Tarball URL: ==
https://savannah.gnu.org/submissions_uploads/audcast.tar.gz







___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/




[task #16254] Submission of PAM OAuth 2.0 Device Auth Grant

2022-09-09 Thread INVALID.NOREPLY
URL:
  

 Summary: Submission of PAM OAuth 2.0 Device Auth Grant
 Project: Savannah Administration
   Submitter: ll4il
   Submitted: Fri 09 Sep 2022 09:13:55 AM UTC
 Should Start On: Fri 09 Sep 2022 12:00:00 AM UTC
   Should be Finished on: Mon 19 Sep 2022 12:00:00 AM UTC
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00


___

Follow-up Comments:


---
Date: Fri 09 Sep 2022 09:13:55 AM UTC By: Anonymous
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):

* Group Administration



= Registration Details =

* Name: *PAM OAuth 2.0 Device Auth Grant*
* System Name:  *pamdevauthgrant*
* Type: non-GNU software and documentation
* License: GNU General Public License v3 or later



== Description: ==
A minimal C implementation of a 
PAM module performing device authentication
as prescribed in 

RFC 8628: OAuth 2.0 Device Authorization Grant
https://oauth.net/2/device-flow/


== Other Software Required: ==
jsmn.h, MIT License, https://github.com/zserge/jsmn
qr.c, CC0-1.0 Universal License, https://github.com/Y2Z/qr


== Tarball URL: ==
https://savannah.nongnu.org/submissions_uploads/pam_deviceauthgrant-0.2.tar.gz









___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16455] Submission of Glitchapp productions

2023-10-28 Thread INVALID.NOREPLY
URL:
  

 Summary: Submission of Glitchapp productions
   Group: Savannah Administration
   Submitter: glitchapp
   Submitted: Sat 28 Oct 2023 08:08:15 AM UTC
 Should Start On: Sat 28 Oct 2023 12:00:00 AM UTC
   Should be Finished on: Tue 07 Nov 2023 12:00:00 AM UTC
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any


___

Follow-up Comments:


---
Date: Sat 28 Oct 2023 08:08:15 AM UTC By: Anonymous
A new group has been registered at Savannah.
This group will remain inactive until a site admin approves
or discards the registration.


= Registration Administration =

Approving or discarding the registration must be done using the specific
[https://savannah.gnu.org/siteadmin/groupedit.php?group_id=12325 Group
administration] page, accessible only to site
administrators logged in as superusers.

= Registration Details =

* Name: *Glitchapp productions*
* System Name:  *glitchapp*
* Type: non-GNU software and documentation
* License: GNU General Public License v2 or later (License Gpl v2.0

Credits for all the assets can be found here:
https://codeberg.org/glitchapp/fish-fillets-remake-assets/src/branch/master/Credits.md

Love-webp (Mit license)

Other libraries included:
https://codeberg.org/glitchapp/fish-fillets-remake/src/branch/main/lib/README)



== Description: ==
Remake from scratch of "Fish fillets" by altar interactive (GNU/GPL since
2004) written in lua /love2d with the following new features:

Dialogs dubbed in several languages.
Higher resolutions supported: from 1080p till 8k.
3d mode.
Classic graphics upscaled.
New graphic set
Gamepad support
Level editor
Runs on windows, Os-x, linux and android. 


== Other Software Required: ==
love libwebp-dev
Love-webp (windows) Repository:
https://github.com/ImagicTheCat/love-webp/tree/master/dist



== Other Comments: ==
Some assets were created with stable diffusion (less than 10%, see credits)

Some issues with alignments remain unresolved, by selecting the right
resolution for your screen the game should align  properly, see issues here:
https://codeberg.org/glitchapp/fish-fillets-remake/issues


== Tarball URL: ==
https://ufile.io/ofl2vukd









___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/




[task #16455] Submission of Glitchapp productions

2023-10-30 Thread INVALID.NOREPLY
Follow-up Comment #2, task #16455 (project administration):

Hi, thanks for the reply. I did my best to improve the readability of the
licenses for the external dependencies and libraries and uploaded it here: 

https://codeberg.org/glitchapp/fish-fillets-remake/src/branch
/main/lib/license.md

The rest of the software which is written by me have the GNU General Public
License v2 or later (License Gpl v2.0).

Apologize for the confusion, this project has grown way too much and I'm doing
my best to keep everything credited properly.

The tar I provided is an AppImage with extra license files which I though
would be the best way to distribute the game, but since the game is written in
lua there's no compilation process and it can directly be run from source:
https://codeberg.org/glitchapp/fish-fillets-remake

Anything else I can do to fullfill requirements please let me know 


[comment #0 original submission:]
> A new group has been registered at Savannah.
> This group will remain inactive until a site admin approves
> or discards the registration.
> 
> 
> = Registration Administration =
> 
> Approving or discarding the registration must be done using the specific
> [https://savannah.gnu.org/siteadmin/groupedit.php?group_id=12325 Group
administration] page, accessible only to site
> administrators logged in as superusers.
> 
> = Registration Details =
> 
> * Name: *Glitchapp productions*
> * System Name:  *glitchapp*
> * Type: non-GNU software and documentation
> * License: GNU General Public License v2 or later (License Gpl v2.0
> 
> Credits for all the assets can be found here:
https://codeberg.org/glitchapp/fish-fillets-remake-assets/src/branch/master/Credits.md
> 
> Love-webp (Mit license)
> 
> Other libraries included:
https://codeberg.org/glitchapp/fish-fillets-remake/src/branch/main/lib/README)
> 
> 
> 
> == Description: ==
> Remake from scratch of "Fish fillets" by altar interactive (GNU/GPL since
2004) written in lua /love2d with the following new features:
> 
> Dialogs dubbed in several languages.
> Higher resolutions supported: from 1080p till 8k.
> 3d mode.
> Classic graphics upscaled.
> New graphic set
> Gamepad support
> Level editor
> Runs on windows, Os-x, linux and android. 
> 
> 
> == Other Software Required: ==
> love libwebp-dev
> Love-webp (windows) Repository:
https://github.com/ImagicTheCat/love-webp/tree/master/dist
> 
> 
> 
> == Other Comments: ==
> Some assets were created with stable diffusion (less than 10%, see credits)
> 
> Some issues with alignments remain unresolved, by selecting the right
resolution for your screen the game should align  properly, see issues here:
https://codeberg.org/glitchapp/fish-fillets-remake/issues
> 
> 
> == Tarball URL: ==
> https://ufile.io/ofl2vukd
> 
> 


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16455] Submission of Glitchapp productions

2023-11-01 Thread INVALID.NOREPLY
Follow-up Comment #5, task #16455 (project administration):

Hi Corwin, I'm glad to read that the submission can still be approved and
regarding the incompatible library, I have to guess it is "block.lua" from the
external libraries (in the lib folder) which was stated in the license list as
only gpl2.

The good news is that there was an error and the original code was not even
licensed and can be found here:
https://simplegametutorials.github.io/love/blocks/

That library is only in charge of a tetris mini game inside the game, and
since the author did not write any license to it I think it can perfectly
licensed as gpl 2 or later.

I committed the necessary changes to the repository on my last commit and the
license has been corrected: please check the commit here:
https://codeberg.org/glitchapp/fish-fillets-remake/commit/e30e8f77317d9d6c833c789f609692205583a211

Let me know if there's anything else I can do to make the project compatible.

Thanks!

Martin


[comment #4 comment #4:]
> Hello again.
> 
> Thank you for looking at Savannah to host your Free Software project.  As
Ineiev has said: we do require GPLv3 combability of the projects we host.   
> 
> That said, I'm hoping we might be able to think of a path forward, to
"remedy" your application.  In that hope, I have reopened the ticket and
assigned myself.
> 
> Please reply back with your thoughts, especially let me know if you'd prefer
to cancel the submission as Ineiev assumes.  I'll reclose it in that case, or
if there's no progress in something like 90 days.
> 
> Thank you for your work developing Free Software!
> 
> Corwin Brust
[comment #4 comment #4:]
> Hello again.
> 
> Thank you for looking at Savannah to host your Free Software project.  As
Ineiev has said: we do require GPLv3 combability of the projects we host.   
> 
> That said, I'm hoping we might be able to think of a path forward, to
"remedy" your application.  In that hope, I have reopened the ticket and
assigned myself.
> 
> Please reply back with your thoughts, especially let me know if you'd prefer
to cancel the submission as Ineiev assumes.  I'll reclose it in that case, or
if there's no progress in something like 90 days.
> 
> Thank you for your work developing Free Software!
> 
> Corwin Brust


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16461] Submission of sinaps is not a password safe

2023-11-10 Thread INVALID.NOREPLY
URL:
  

 Summary: Submission of sinaps is not a password safe
   Group: Savannah Administration
   Submitter: xwst
   Submitted: Fri 10 Nov 2023 10:14:06 PM CET
 Should Start On: Fri 10 Nov 2023 12:00:00 AM CET
   Should be Finished on: Mon 20 Nov 2023 12:00:00 AM CET
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any


___

Follow-up Comments:


---
Date: Fri 10 Nov 2023 10:14:06 PM CET By: Anonymous
A new group has been registered at Savannah.
This group will remain inactive until a site admin approves
or discards the registration.


= Registration Administration =

Approving or discarding the registration must be done using the specific
[https://savannah.nongnu.org/siteadmin/groupedit.php?group_id=12329 Group
administration] page, accessible only to site
administrators logged in as superusers.

= Registration Details =

* Name: *sinaps is not a password safe*
* System Name:  *sinaps*
* Type: non-GNU software and documentation
* License: GNU General Public License v3 or later



== Description: ==
sinaps is a stateless password manager that derives passwords using a single
master pin and different contexts (site names, user names, ...).
In that sense, it is very much like lesspass (https://www.lesspass.com/) but
it
also supports configuration files with tab completion, a history and will
support encrypted secrets, as well as special commands to set default values.

sinaps aims to bridge the gap between classical and stateless password
managers.
On the one hand, passwords should be deterministically generated on the fly
to
avoid copying/syncing password databases all the time; on the other hand, it
should still be possible to also store small secrets that can not be chosen
at
will (e.g. credit card numbers).


== Other Software Required: ==
libsodium
gtkmm
libsigc++
GNU readline library
CxxTest

Tools: CMake and doxygen

The dependencies are also mentioned in the README including the corresponding
licenses and links to the webpages.

There are two additional dependencies on python packages for a short script
that serves as a reference implementation (argon2-cffi: MIT, PyCryptodome:
public domain & BSD 2-Clause). These dependencies are not mentioned in the
README.


== Tarball URL: ==
https://savannah.nongnu.org/submissions_uploads/sinaps.tgz









___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16461] Submission of sinaps is not a password safe

2023-11-14 Thread INVALID.NOREPLY
Follow-up Comment #2, task #16461 (project administration):

Thank you for your feedback. I added the missing license versions and
copyright and license notices in doxygen.conf.
I attached a new version including the generated documentation.

Please let me know if anything else is missing.

(file #55330)

___

Additional Item Attachment:

File name: sinaps.tgz Size:1827 KB




___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16461] Submission of sinaps is not a password safe

2023-11-16 Thread INVALID.NOREPLY
Follow-up Comment #4, task #16461 (project administration):

Yes, I forgot to also license the generated html files. I just added the
notices.

The section containing the GNU Free Documentation License can be found in the
tree view on the left-hand side or from "Related Pages" in the top menu.

Regarding doxygen.conf: Are you concerned that the file should inherit the
license of doxygen because of all the boilerplate code? I dropped all default
lines and kept only the ones I changed; then, it shouldn't be an issue. Or did
you refer to something else?

I uploaded a new version with said changes so you can check.



(file #55334)

___

Additional Item Attachment:

File name: sinaps_2.tgz   Size:526 KB




___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16461] Submission of sinaps is not a password safe

2023-11-17 Thread INVALID.NOREPLY
Follow-up Comment #6, task #16461 (project administration):


[comment #5 comment #5:]
> [comment #4 comment #4:]
> > Yes, I forgot to also license the generated html files. I just added the
notices.
> 
> Did I say, "HTML"?  Do you mean HTML?  And a question with an asterisk: are
all added notices valid?
The HTML documentation is the only one that I generated, so I assumed that's
what you were talking about.
The doxygen webpage states the following: "Documents produced by doxygen are
derivative works derived from the input used in their production; they are not
affected by this license."
My understanding is that I can choose any license for the produced documents.
If that was not the case, using doxygen would force me to also use GPLv2.

> 
> > The section containing the GNU Free Documentation License can be found in
the tree view on the left-hand side or from "Related Pages" in the top menu.
> 
> I see neither the tree view nor the top menu with my browser.

Hmm... just to be on the same page: Are we talking about the generated
HTML-documentation? Out of curiosity and to trouble shoot: Which browser do
you use?

> 
> > Regarding doxygen.conf: Are you concerned that the file should inherit the
license of doxygen because of all the boilerplate code?
> 
> You are right.
> 
> > I dropped all default lines and kept only the ones I changed; then, it
shouldn't be an issue.
> 
> Why not?  The file is still derived, isn't it?

Well, ... technically it is. But taking pieces from the doxygen manual to
construct a doxygen.conf is also derived, isn't it? So am I forced into GPLv2
when using doxygen? I assumed the license requirements are less prohibitive.
Thoughts?

I suppose the easy way out is to strip off the doxygen.conf and generated
documentation and leave it to interested people to run doxygen themselves.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16461] Submission of sinaps is not a password safe

2023-11-20 Thread INVALID.NOREPLY
Follow-up Comment #8, task #16461 (project administration):

Ok, so the documentation part is much tougher than I expected. Thank you for
all the input and guidance. Let me try to organize it a bit, please comment on
my thoughts.

1. I currently use doxygen to generate "HTML output". This is the term that is
used by doxygen itself, but it includes HTML, css, javascript, png and *.md5
and *.map files.

  a) The latter two are intermediate files and not part of the documentation
so I do not see the necessity to put in notices.
  b) The css and javascript files are boilerplate so I don't think I can or
should put a copyright in there. I am not sure about a license notice though.
If you think I should include one, I can do it.
  c) The HTML files already contain copyright and license notices.
  d) The png files are also generated from the source code so I put a note in
the README to declare their license.

2. Just to clairfy: I think all the files mentioned above make up one
particular type of a "produced document" to which the GPLv2 of doxygen does
not apply.

3. I see that lynx does not render the menus; I added a direct link so the
license will be accessible.

4. Regarding doxygen.conf: Now that I have dropped all boilerplate, there is
no copied expression in there because all of the remaining settings were
handwritten after reading the documentation.

(file #55343)

___

Additional Item Attachment:

File name: sinaps_3.tgz   Size:527 KB




___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16485] Submission of NetUseMod

2024-01-12 Thread INVALID.NOREPLY
URL:
  

 Summary: Submission of NetUseMod
   Group: Savannah Administration
   Submitter: salahuddin
   Submitted: Fri 12 Jan 2024 10:53:12 PM UTC
 Should Start On: Fri 12 Jan 2024 12:00:00 AM UTC
   Should be Finished on: Mon 22 Jan 2024 12:00:00 AM UTC
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any


___

Follow-up Comments:


---
Date: Fri 12 Jan 2024 10:53:12 PM UTC By: Anonymous
A new group has been registered at Savannah.
This group will remain inactive until a site admin approves
or discards the registration.


= Registration Administration =

Approving or discarding the registration must be done using the specific
[https://savannah.gnu.org/siteadmin/groupedit.php?group_id=12340 Group
administration] page, accessible only to site
administrators logged in as superusers.

= Registration Details =

* Name: *NetUseMod*
* System Name:  *netusemod*
* Type: non-GNU software and documentation
* License: GNU General Public License v3 or later



== Description: ==
NetUseMod is a program to moderate Usenet posts via web interface.


== Other Software Required: ==
procmail, Perl, Perl Dancer2 module (for web interface)


== Tarball URL: ==
https://savannah.gnu.org/submissions_uploads/YIzG2K-NetUseMod-0.1.tar.gz









___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/




[task #16485] Submission of NetUseMod

2024-01-13 Thread INVALID.NOREPLY
Follow-up Comment #2, task#16485 (group administration):

done

(file #55561)

___

Additional Item Attachment:

File name: NetUseMod-0.1.tag.gz   Size:23 KB



AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://git.savannah.nongnu.org/cgit/administration/savane.git/snapshot/savane-2bbd2982b8cb5f7080f85acd17caf4358bc6047a.tar.gz


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16485] Submission of NetUseMod

2024-01-13 Thread INVALID.NOREPLY
Follow-up Comment #3, task#16485 (group administration):

Other Software Required:

procmail - https://github.com/BuGlessRB/procmail -
https://en.wikipedia.org/wiki/Procmail

perl - https://www.perl.org/
perl Dancer2 - https://metacpan.org/dist/Dancer2



___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16485] Submission of NetUseMod

2024-01-13 Thread INVALID.NOREPLY
Follow-up Comment #5, task#16485 (group administration):


>Thank you, please check for missing copyright and license notices again. 

Could you please be specific which copyright and notices are missing ?
I added copyright notice all the places possible in the project.


I am not including anything from procmail, perl dancer2 in my project.

Just it requires procmail and perl dancer2 to be installed OS to run.

procmail - GPL-2.0 license
perl - Dancer2  -  GPL-1 license

Thank you.



___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16485] Submission of NetUseMod

2024-01-15 Thread INVALID.NOREPLY
Follow-up Comment #6, task#16485 (group administration):

removed Image.

(file #55573)

___

Additional Item Attachment:

File name: NetUseMod-0.1.tag.gz   Size:22 KB



AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://git.savannah.nongnu.org/cgit/administration/savane.git/snapshot/savane-3f5b69a3b837951a0e5c0b7730ee347c798a8844.tar.gz


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16485] Submission of NetUseMod

2024-01-15 Thread INVALID.NOREPLY
Additional Item Attachment, task#16485 (group administration):

File name: NetUseMod-0.2.tar.gz   Size:22 KB



AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://git.savannah.nongnu.org/cgit/administration/savane.git/snapshot/savane-3f5b69a3b837951a0e5c0b7730ee347c798a8844.tar.gz


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16485] Submission of NetUseMod

2024-01-15 Thread INVALID.NOREPLY
Follow-up Comment #7, task#16485 (group administration):

update version.
https://savannah.nongnu.org/task/download.php?file_id=55574


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16485] Submission of NetUseMod

2024-01-16 Thread INVALID.NOREPLY
Follow-up Comment #9, task#16485 (group administration):

Thank you for your patience.

Some packaging rules changed in recent year which I was not aware of.

I added other tool licenses and a README in the image directory for copyright
notice.
(the image is not important - just to show small logo in browser tab.)


Just one small feedback.
It would be great to have a sample package showing example how to add
copyright notices of external packages and binary images README.

https://www.gnu.org/prep/maintain/maintain.html#External-Libraries
Seems like - it was written by lawyers, and therefore not developer friendly.

Thank you.


(file #55579)

___

Additional Item Attachment:

File name: NetUseMod-0.3.tar.gz   Size:35 KB



AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://git.savannah.nongnu.org/cgit/administration/savane.git/snapshot/savane-dc9b9bbc95a92dc81e8bc82138016fbea1bb3a8d.tar.gz


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[task #16485] Submission of NetUseMod

2024-01-19 Thread INVALID.NOREPLY
Follow-up Comment #11, task#16485 (group administration):

Hi Ineiev,

You are always writing in vague language.

> Could you use a complete license notice as recommended in the GPL? 

I have complete LICENSE added from https://www.gnu.org/licenses/gpl-3.0.txt

What is complete gpl license in your view ?


> There should be no ambiguities left about what copyright and > license
notices applies to the image files and to README itself. 

I added README for image license. (Just, like other approved project in
savannah.)

Should I add another 2nd LICENSE file in my project to make things more
confusing now ?


> Then, I could point to the files that still lack the copyright and >license
notices, but the tarball is so small that it shouldn't be >hard for you to
find them.

I already told you I checked and added license to all the files possible.
Why can't you check now let me know, if there is anything missing.
So, I can submit fix at once.

I feel you are just wasting my time here.

If you feel the project is not ready for savannah, you can reject it, and I
will host it elsewhere.

Thank you.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/




[Savannah-register-public] [task #7327] Submission of logsyscrash

2007-09-23 Thread INVALID.NOREPLY

URL:
  

 Summary: Submission of logsyscrash
 Project: Savannah Administration
Submitted by: tobb
Submitted on: Sonntag 23.09.2007 um 12:43
 Should Start On: Sonntag 23.09.2007 um 00:00
   Should be Finished on: Mittwoch 03.10.2007 um 00:00
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

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):

* Group Administration



= Registration Details =

* Name: *logsyscrash*
* System Name:  *logsyscrash*
* Type: non-GNU software & documentation
* License: GNU General Public License v3 or later



 Description: 
This program logs if your system was not shut down correctly (in the most
cases this means that a crash has happend).


 Other Software Required: 
Only standard C++! (libstdc++)






___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #7327] Submission of logsyscrash

2007-09-23 Thread INVALID.NOREPLY

Follow-up Comment #2, task #7327 (project administration):

Source Code:
http://cpp.sourceforge.net/?show=40630



Description:
Program for Linux / Unix.
This program logs if your system was not shut down correctly (in the most
cases this means that a crash has happend).

For example: power fail restart
You may get problems with your file system or with pid files. But you don't
know why because you miss the power cut and you do not dissect your syslog
every day.

A short look in /var/log/logsyscrash will clear you up!

___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #7327] Submission of logsyscrash

2007-09-23 Thread INVALID.NOREPLY

Follow-up Comment #4, task #7327 (project administration):

http://pastebin.com/f73f23332

Sorry, I don't know how to upload a tarball here...?

___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #8097] Submission of jmbdos

2008-04-30 Thread INVALID.NOREPLY

URL:
  

 Summary: Submission of jmbdos
 Project: Savannah Administration
Submitted by: jmbdos
Submitted on: Wednesday 04/30/2008 at 10:43
 Should Start On: Wednesday 04/30/2008 at 00:00
   Should be Finished on: Saturday 05/10/2008 at 00:00
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

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):

* Group Administration



= Registration Details =

* Name: *jmbdos*
* System Name:  *jmbdos*
* Type: non-GNU software & documentation
* License: WebSite Only



 Description: 
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla bla
bla blabla bla



 Tarball URL: 
www.123.com\a.tar.gz






___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #8357] Submission of AudioERP

2008-06-25 Thread INVALID.NOREPLY

URL:
  

 Summary: Submission of AudioERP
 Project: Savannah Administration
Submitted by: xtester00
Submitted on: mercoledì 25/06/2008 alle 21:12
 Should Start On: mercoledì 25/06/2008 alle 00:00
   Should be Finished on: sabato 05/07/2008 alle 00:00
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

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):

* Group Administration



= Registration Details =

* Name: *AudioERP*
* System Name:  *audioerp*
* Type: non-GNU software & documentation
* License: GNU General Public License v2 or later



 Description: 
Python-based medical ERP solution.


 Tarball URL: 
http://savannah.gnu.org/submissions_uploads/audioerp.tar.gz






___

Reply to this item at:

  

___
  Messaggio inviato con/da Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #8424] Submission of Larus Board

2008-07-23 Thread INVALID.NOREPLY

URL:
  

 Summary: Submission of Larus Board
 Project: Savannah Administration
Submitted by: saturas
Submitted on: Mittwoch 23.07.2008 um 21:34
 Should Start On: Mittwoch 23.07.2008 um 00:00
   Should be Finished on: Samstag 02.08.2008 um 00:00
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

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):

* Group Administration



= Registration Details =

* Name: *Larus Board*
* System Name:  *larusboard*
* Type: non-GNU software & documentation
* License: Modified BSD License



 Description: 
LB is a light-weight discussion board written in PHP. At least 5.2.0 is
required as OOP became pretty stable here. Storage Backend uses PDO for
abstraction and supports MySQL and Postgres (preferred) at the moment. The UI
uses Unicode, AJAX, XHTML/CSS and is rendered by Smarty (PHP Template Engine).
Instead of being bloated it has a minimal featureset and uses tags set by
users on any posting instead of fixed categories. Any topic can be fetched by
RSS. Edited postings have a history to view the differences. It is designed to
have a public part accessible from the web and a private part which can be
anywhere.


 Other Software Required: 
overlib (Artistic)
http://www.bosrup.com/web/overlib/?License

SHA1 in JS (BSD)
http://pajhome.org.uk/crypt/md5/sha1src.html

Smarty Template Engine (LGPL)
http://www.smarty.net/

Text_Diff from PEAR (LGPL)
http://pear.php.net/package/Text_Diff

xajax (BSD)
http://www.xajaxproject.org/


 Other Comments: 
All dependent libs are included in tarball. Currently it is in alpha phase,
but beta is near. At least on my platform it runs quite well. The copyright
headers have not a correct url at the moment. This will be fixed before the
first release. In /docs is an index.html which contents will be incorporated
to project site (Description, ToDo-List, History, License and so on). A
separated license file will also be included. I just put alltogether in the
index file first.


 Tarball URL: 
http://savannah.gnu.org/submissions_uploads/larus_board.tar.bz2






___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/





[Savannah-register-public] [task #8357] Submission of AudioERP

2008-10-07 Thread INVALID.NOREPLY

Follow-up Comment #2, task #8357 (project administration):

I am not interested anymore to use Savannah to host my project. I understand
your amount of work to do but too time is elapsed. Thanks, anyway.

Regards,
xtester00

___

Reply to this item at:

  

___
  Messaggio inviato con/da Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #8357] Submission of AudioERP

2008-10-07 Thread INVALID.NOREPLY

Follow-up Comment #3, task #8357 (project administration):

I ask to you guys to cancel my AudioERP registration in order to erase my
account.

Thanks a lot.

___

Reply to this item at:

  

___
  Messaggio inviato con/da Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #8424] Submission of Larus Board

2008-10-12 Thread INVALID.NOREPLY

Follow-up Comment #1, task #8424 (project administration):

This package has become pretty nice during the last three months (yes, LB is
alive) and I just wonder why the submission has not been touched for three
months? Having a look on the task list tells me, I am not alone... :)

Is there any hard work going on not mentioned in the news delaying the
submission queue?

___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #8424] Submission of Larus Board

2008-10-18 Thread INVALID.NOREPLY

Follow-up Comment #3, task #8424 (project administration):

Hello,

I know what you mean. Sometimes the day should have 48 hours :)

Well, I replaced the old copyright notices by a modified version of the gpl
template from gnu.org. Hope it´s okay now.

Images, language files, templates and documentation are now licensed under
cc-by-sa. Basically any "non-sources" like PHP or JS. All neccessary folders
now include a license.txt with information. 

(file #16695)
___

Additional Item Attachment:

File name: larus_board-0.8.36.tbz Size:394 KB


___

Reply to this item at:

  

___
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #9944] Submission of Argile programming language compiler

2009-12-03 Thread INVALID.NOREPLY

URL:
  

 Summary: Submission of Argile programming language compiler
 Project: Savannah Administration
Submitted by: jc86
Submitted on: jeu 03 déc 2009 22:23:49 GMT
 Should Start On: jeu 03 déc 2009 00:00:00 GMT
   Should be Finished on: dim 13 déc 2009 00:00:00 GMT
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
Percent Complete: 0%
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
  Effort: 0.00

___

Details:

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):

* Group Administration



= Registration Details =

* Name: *Argile programming language compiler*
* System Name:  *argile*
* Type: non-GNU software & documentation
* License: GNU General Public License v2 or later (most of the code is
distributed under GNU General Public License v3;

some other code (the runtime library) is distributed under a zlib-like
license.)



 Description: 
Argile is an experimental, C-based, compiled programming language, that
produces C code. It is not intended for beginners, but for experimented
programmers with a good knowledge of C. It is polymorphism-oriented and has
variable syntax.


 Other Software Required: 
GCC (GPL) http://gcc.gnu.org/
GNU make (GPL) http://www.gnu.org/software/make/
GNU bash (GPL) http://www.gnu.org/software/bash/

OPTIONALLY:

automake (GPL) http://www.gnu.org/software/automake/
autoconf (GPL) http://www.gnu.org/software/autoconf/
GNU bison(or yacc) (GPL) http://www.gnu.org/software/bison/
flex(or lex) (BSD license) http://flex.sourceforge.net/



 Tarball URL: 
http://savannah.gnu.org/submissions_uploads/argile-1.0.0.tar.gz






___

Reply to this item at:

  

___
  Message posté via/par Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #9944] Submission of Argile programming language compiler

2009-12-06 Thread INVALID.NOREPLY

Follow-up Comment #2, task #9944 (project administration):

I re-uploaded
http://savannah.gnu.org/submissions_uploads/argile-1.0.0.tar.gz

I added copyright information in all files,
except for some documentations, but they are listed in README.
If there are still files lacking copyright information, please
specify explicitely which ones, as I have doubts on what needs
to be copyrighted (I cannot copyright aclocal.m4 for example).

Besides, I do not know what license I should specify for these
documentations files (FDL ?) ...
(note that one of them contains an english short
description of some algorithms used in the software)

Also, I wonder if it is important to copyright
build files (Makefile.am , configure.ac) they are not really
part of the software itself. What wrong would that do if they
were copied without restrictions ?


___

Reply to this item at:

  

___
  Message posté via/par Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #9944] Submission of Argile programming language compiler

2009-12-06 Thread INVALID.NOREPLY

Follow-up Comment #4, task #9944 (project administration):

I updated again
http://savannah.gnu.org/submissions_uploads/argile-1.0.0.tar.gz

I added copyright and GNU FDL notices at the end of long
documentation files, but not for small documentation files
(they are listed in README anyway)

I added doc/COPYING from http://www.gnu.org/licenses/fdl.txt

I updated AUTHORS and README files

Do I need to specify "(see the AUTHORS file distributed along with this
software)" everywhere ?
or is "the Argile authors" sufficient ?
(some files do not have this precision in their copyright notices
as it seemed pedantic)

I also changed the license of the runtime library
from zlib to LGPL rather than GPL because I think that
forcing GPLization of programs written in this language
could scare a lot of programmers away
(it is a new programming language, and no other compiler
for it exist yet).

However, I am open to suggestions.


___

Reply to this item at:

  

___
  Message posté via/par Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #9944] Submission of Argile programming language compiler

2009-12-07 Thread INVALID.NOREPLY

Follow-up Comment #6, task #9944 (project administration):

I finally decided to license the runtime library under
the GNU GPL as well (it is not a mandatory library anyway)

updated:
http://savannah.gnu.org/submissions_uploads/argile-1.0.0.tar.gz

Also, the item status doesn't seem to have changed:
in my browser it prints "In Progress" instead of "Need admin"
and "0%" instead of "90%".


___

Reply to this item at:

  

___
  Message posté via/par Savannah
  http://savannah.gnu.org/





[Savannah-register-public] [task #9944] Submission of Argile programming language compiler

2009-12-08 Thread INVALID.NOREPLY

Follow-up Comment #8, task #9944 (project administration):

Also, the licensing information should be changed,
now that there is no more code under zlib license.

But, I don't know how to do that myself.


___

Reply to this item at:

  

___
  Message posté via/par Savannah
  http://savannah.gnu.org/





[task #16658] Submission of serde-catholicmatch

2025-06-25 Thread INVALID.NOREPLY
URL:
  

 Summary: Submission of serde-catholicmatch
   Group: Savannah Administration
   Submitter: dullbananas
   Submitted: Thu 26 Jun 2025 03:41:35 AM GMT
 Should Start On: Thu 26 Jun 2025 12:00:00 AM GMT
   Should be Finished on: Sun 06 Jul 2025 12:00:00 AM GMT
Category: Project Approval
Priority: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any


___

Follow-up Comments:


---
Date: Thu 26 Jun 2025 03:41:35 AM GMT By: Anonymous
A new group has been registered at Savannah.
This group will remain inactive until a site admin approves
or discards the registration.


= Registration Administration =

Approving or discarding the registration must be done using the specific
[https://savannah.nongnu.org/siteadmin/groupedit.php?group_id=12404 Group
administration] page, accessible only to site
administrators logged in as superusers.

= Registration Details =

* Name: *serde-catholicmatch*
* System Name:  *serdecm*
* Type: non-GNU software and documentation
* License: GNU Affero General Public License v3 or later



== Description: ==
(Rust library) Parser for user data exports that are provided by CatholicMatch


== Other Software Required: ==
[
  {
"name": "itoa",
"version": "1.0.15",
"authors": "David Tolnay ",
"repository": "https://github.com/dtolnay/itoa";,
"license": "Apache-2.0 OR MIT",
"license_file": null,
"description": "Fast integer primitive to string conversion"
  },
  {
"name": "memchr",
"version": "2.7.5",
"authors": "Andrew Gallant |bluss",
"repository": "https://github.com/BurntSushi/memchr";,
"license": "MIT OR Unlicense",
"license_file": null,
"description": "Provides extremely fast (uses SIMD on x86_64, aarch64 and
wasm32) routines for 1, 2 or 3 byte search and single substring search."
  },
  {
"name": "proc-macro2",
"version": "1.0.95",
"authors": "David Tolnay |Alex Crichton
",
"repository": "https://github.com/dtolnay/proc-macro2";,
"license": "Apache-2.0 OR MIT",
"license_file": null,
"description": "A substitute implementation of the compiler's `proc_macro`
API to decouple token-based libraries from the procedural macro use case."
  },
  {
"name": "quote",
"version": "1.0.40",
"authors": "David Tolnay ",
"repository": "https://github.com/dtolnay/quote";,
"license": "Apache-2.0 OR MIT",
"license_file": null,
"description": "Quasi-quoting macro quote!(...)"
  },
  {
"name": "ryu",
"version": "1.0.20",
"authors": "David Tolnay ",
"repository": "https://github.com/dtolnay/ryu";,
"license": "Apache-2.0 OR BSL-1.0",
"license_file": null,
"description": "Fast floating point to string conversion"
  },
  {
"name": "serde",
"version": "1.0.219",
"authors": "Erick Tryzelaar |David Tolnay
",
"repository": "https://github.com/serde-rs/serde";,
"license": "Apache-2.0 OR MIT",
"license_file": null,
"description": "A generic serialization/deserialization framework"
  },
  {
"name": "serde-catholicmatch",
"version": "0.1.0",
"authors": null,
"repository": null,
"license": "AGPL-3.0-or-later",
"license_file": null,
"description": "Unofficial deserializer for user data exports that are
provided by CatholicMatch"
  },
  {
"name": "serde_derive",
"version": "1.0.219",
"authors": "Erick Tryzelaar |David Tolnay
",
"repository": "https://github.com/serde-rs/serde";,
"license": "Apache-2.0 OR MIT",
"license_file": null,
"description": "Macros 1.1 implementation of #[derive(Serialize,
Deserialize)]"
  },
  {
"name": "serde_json",
"version": "1.0.140",
"authors": "Erick Tryzelaar |David Tolnay
",
"repository": "https://github.com/serde-rs/json";,
"license": "Apache-2.0 OR MIT",
"license_file": null,
"description": "A JSON serialization file format"
  },
  {
"name": "syn",
"version": "2.0.104",
"authors": "David Tolnay ",
"repository": "https://github.com/dtolnay/syn";,
"license": "Apache-2.0 OR MIT",
"license_file": null,
"description": "Parser for Rust source code"
  },
  {
"name": "unicode-ident",
"version": "1.0.18",
"authors": "David Tolnay ",
"repository": "https://github.com/dtolnay/unicode-ident";,
"license": "(MIT OR Apache-2.0) AND Unicode-3.0",
"license_file": null,
"description": "Determine whether characters have the XID_Start or
XID_Continue properties according to Unicode Standard Annex #31"
  }
]


== Tarball URL: ==
https://savannah.nongnu.org/submissions_uploads/serde-catholicmatch.tar.gz









___

[task #16658] Submission of serde-catholicmatch

2025-07-08 Thread INVALID.NOREPLY
Follow-up Comment #10, task #16658 (group administration):

For consistency and clarity, I have now decided to use AGPL for the Cargo.lock
and rust_fmt_version.txt files, regardless of whether or not they can be
restricted by copyright. To work around the fact that these files are
automatically overwritten, I put the notices in the Cargo.lock.license and
rust_fmt_version.txt.license files. They are the same notices that other files
have, except I made the phrase "This file" more specific.

[comment #9 comment #9:]
>> rust_fmt_version.txt is generated by `cargo +nightly fmt --version >
>> rust_fmt_version.txt` in the lint.sh script. Currently the file just
>> contains
>> `rustfmt 1.8.0-nightly (c68340350c 2025-06-18)`. It's not derived from my
>> work
>> at all. The included work of Rust developers (e.g. a version number) don't
>> seem copyrightable.
> 
> Why doesn't it seem copyrightable?

It's way too simple.

These are all the things that the string "rustfmt 1.8.0-nightly (c68340350c
2025-06-18)" comes from (not that I think this matters):
- Format strings "rustfmt {version_number}-{commit_info}" and "{} ({} {})" in
rustfmt source code.
- The version number "1.8.0".
- The string literal "nightly".
- The outputs of the commands `git rev-parse HEAD` and `git log -1
--date=short --pretty=format:%cd` when run in the rustfmt repository.

>> - libgit2's GPLv2 license, with a linking exception (granting "unlimited
>> permission to link the compiled version of this library into combinations
>> with
>> other programs, and to distribute those combinations without any
>> restriction
>> coming from the use of this file")
> 
> Is this compatible with GPLv3?  What do you think?

Yes, assuming you are using the definition of "compatible" that the GNU
licenses FAQ gives. Libgit2 can be a dependency of GPLv3 software via either
static or dynamic linking. GPLv2 restricts things such as "modification of the
file, and distribution when not linked into a combined executable" according
to the linking exception.

> We have just seen that e.g. 'MIT OR Apache-2.0' in fact may mean a much
> richer set of licenses, haven't we?  (And sincerely speaking, I can't get the
> point of licensing anything like (in Rust 'materials') Apache-2.0 OR
> Apache-2.0 WITH LLVM-exception OR CC0-1.0.)

"Apache-2.0 OR Apache-2.0 WITH LLVM-exception OR CC0-1.0" can be treated the
same as "CC0-1.0" (public domain) and does not prevent Rust from being
released under "MIT or Apache-2.0".

The purpose of combining Apache-2.0 with a more permissive license using `OR`
is to protect against patent aggression (probably from contributors) using
Apache-2.0's patent grant, without removing compatibility with GPLv2.


My best guess for the purpose of using "Apache-2.0 OR Apache-2.0 WITH
LLVM-exception" instead of just "Apache-2.0" is to make it clearly optional to
read the LLVM exception, which is convenient for someone who doesn't know what
"WITH LLVM-exception" means.

My best guess for the purpose of using "Apache-2.0 OR Apache-2.0 WITH
LLVM-exception OR CC0-1.0" instead of "Apache-2.0 OR CC0-1.0" (basically
CC0-1.0 plus patent grant) is to use "Apache-2.0 OR Apache-2.0 WITH
LLVM-exception" (equivalent to "Apache-2.0 WITH LLVM-exception") as a backup
for when CC0-1.0 doesn't work in some jurisdictions (may or may not be a
rational fear).

 - rust, , MIT OR Apache-2.0
> ...
>> The items listed in that same file under "We track licenses for third-party
>> materials in two ways" are sufficient for the "otherwise noted" cases. The
>> REUSE.toml file precisely lists licenses for files in both the Rust
>> repository
>> and the included git submodules. Here's the external dependencies'
>> licenses,
>> summarized by the `cargo-license` tool:
>> 
>> ```
>> (MIT OR Apache-2.0) AND Unicode-3.0 (1): unicode-ident
> ...
>> MPL-2.0 (2): colored, option-ext
>> N/A (106): build-manifest, build_helper, bump-stage0, cargotest2,
> ...
>> Zlib (1): foldhash
>> ```
> 
> What conclusion can you make based on this?

- All libraries listed under "N/A" in the output of cargo-license are
non-external libraries in the Rust repository. Their licenses are only
specified in REUSE.toml, not in the per-library Cargo.toml files.
- The Rust repository includes fonts licensed under OFL-1.1. I don't know if
that's a problem.
- Some entries in REUSE.toml are for things in the `src/gcc` directory, which
is a Git submodule that is typically not initialized or used. It's for Rust's
fork of GCC. Official Rust builds don't use it. Some non-default Rust builds
may have to be GPL 3 or later because of opting into the feature that uses the
GCC fork. GCC has a GPL-2.0-only test suite that is not touched by Rust's
fork, so that license is listed in Rust's REUSE.toml, but it can be ignored
because GCC's test suite has nothing to do with Rust. For details, see


[task #16658] Submission of serde-catholicmatch

2025-07-03 Thread INVALID.NOREPLY
Follow-up Comment #8, task #16658 (group administration):

Here's a corrected explanation of the files that have no notice.

rust_fmt_version.txt is generated by `cargo +nightly fmt --version >
rust_fmt_version.txt` in the lint.sh script. Currently the file just contains
`rustfmt 1.8.0-nightly (c68340350c 2025-06-18)`. It's not derived from my work
at all. The included work of Rust developers (e.g. a version number) don't
seem copyrightable. The purpose of rust_fmt_version.txt is to make the current
code formatting style reproducible, just in case there's problems caused by
all the formatting suddenly changing when updating rustfmt.

Cargo.lock is a package manager state. It lists each direct or indirect
dependency's name, version, source location, checksum, and dependency names.
Before compiling a package (not including dependencies), Cargo always rewrites
its Cargo.lock file. A change to the next contents of Cargo.lock can be
triggered by editing the list of direct dependencies in Cargo.toml (not to be
confused with Cargo.lock) or by running `cargo update`. The purpose of
including Cargo.lock in version control (which is controversial) is to allow
investigation when a new version of a dependency causes my library to break.

Not sure it it matters, but there's "rust_fmt_version.txt.license" and
"Cargo.lock.license" files with the following contents so that the `reuse
lint` command doesn't complain about the lack of embedded license data:

```
SPDX-FileCopyrightText: NONE

SPDX-License-Identifier: CC0-1.0
```

>> - cargo, , MIT OR Apache-2.0
> 
> Its README.md says it contains some software under more licenses 
> (LICENSE-THIRD-PARTY).  Could you analyze it?

LICENSE-THIRD-PARTY contains copies of these licenses used by dependencies:
- old license that OpenSSL used to use, outdated because Cargo uses version
300.5.0+3.5.0 of openssl-src, and OpenSSL switched to Apache-2.0 license in
version 3 (see  and
)
- libgit2's GPLv2 license, with a linking exception (granting "unlimited
permission to link the compiled version of this library into combinations with
other programs, and to distribute those combinations without any restriction
coming from the use of this file")
- zlib license
- expat licenses
- LGPL v2.1 license
- BSD 3-clause license
- a variant of the X11 license, with "the X Consortium" replaced with generic
references to authors and copyright holders
- the unlicense

> While at it, there is no single
> [//www.gnu.org/licenses/license-list.html#Expat "MIT" license]: people use it
> to refer to a number of various licenses.

Should I look in the repository of each "MIT"-licensed dependency to check
what the authors meant by "MIT"?

>> - rust, , MIT OR Apache-2.0
> 
> The COPYRIGHT file says (the emphasis is mine),
> 
>> *Except as otherwise noted*, Rust is licensed... 
> 
> What do you think about it?

The items listed in that same file under "We track licenses for third-party
materials in two ways" are sufficient for the "otherwise noted" cases. The
REUSE.toml file precisely lists licenses for files in both the Rust repository
and the included git submodules. Here's the external dependencies' licenses,
summarized by the `cargo-license` tool:

```
(MIT OR Apache-2.0) AND Unicode-3.0 (1): unicode-ident
0BSD OR Apache-2.0 OR MIT (1): adler2
Apache-2.0 (4): dissimilar, fluent-langneg, self_cell, similar
Apache-2.0 OR Apache-2.0 WITH LLVM-exception OR CC0-1.0 (1): blake3
Apache-2.0 OR Apache-2.0 WITH LLVM-exception OR MIT (17): linux-raw-sys,
rustix, wasi, wasi, wasm-component-ld, wasm-encoder, wasm-encoder,
wasm-encoder, wasm-metadata, wasmparser, wasmparser, wasmparser, wast, wat,
wit-bindgen-rt, wit-component, wit-parser
Apache-2.0 OR BSD-2-Clause OR MIT (2): zerocopy, zerocopy-derive
Apache-2.0 OR BSL-1.0 (1): ryu
Apache-2.0 OR CC0-1.0 OR MIT-0 (1): constant_time_eq
Apache-2.0 OR LGPL-2.1-or-later OR MIT (1): r-efi
Apache-2.0 OR MIT (362): addr2line, aes, allocator-api2, android-tzdata,
android_system_properties, annotate-snippets, annotate-snippets, anstream,
anstyle, anstyle-lossy, anstyle-parse, anstyle-query, anstyle-svg,
anstyle-wincon, anyhow, arrayvec, askama, askama_derive, askama_parser,
autocfg, backtrace, base64, basic-toml, bitflags, block-buffer, bstr, bumpalo,
bytecount, camino, cargo-miri, cargo-platform, cc, cfg-if, chrono, chrono-tz,
chrono-tz-build, cipher, clap, clap-cargo, clap_builder, clap_derive,
clap_lex, clippy, clippy_lints, clippy_utils, collect-license-metadata,
color-eyre, color-print, color-print-proc-macro, color-spantrace, colorchoice,
core-foundation-sys, cpufeatures, crc32fast, crossbeam-channel,
crossbeam-deque, crossbeam-epoch, crossbeam-utils, crypto-common, ctrlc,
datafrog, dbus, declare_clippy_lint, derive-where, derive_builder,
derive_builder_core, derive_builder_macro, derive_setters, diff, digest

[task #16658] Submission of serde-catholicmatch

2025-07-01 Thread INVALID.NOREPLY
Follow-up Comment #6, task #16658 (group administration):

[comment #5 comment #5:]
> If a file is generated automatically, it doesn't mean it isn't copyrightable,
> does it?

Correct, it isn't copyrightable.

>> - reuse, , Apache-2.0 AND CC0-1.0 AND
>> CC-BY-SA-4.0 AND GPL-3.0-or-later
> 
> Could you explain what this means?

The "AND" operator means that compliance with multiple licenses is needed. I
got this license expression with `dnf info` which seems to show overly verbose
license expressions, possibly generated from per-file license data. I'm more
awake now, so I now know that "Apache-2.0" (permissive) and "CC0-1.0" (public
domain) are redundant because they are compatible with GPL.

Also I now noticed that there's a non-GPL-compatible license "CC-BY-SA-4.0". I
looked at the project's README, and it says that this license is for the
documentation. My project does not require installing the documentation.

In conclusion, this dependency is GPL-3.0-or-later.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/


signature.asc
Description: PGP signature


[task #16658] Submission of serde-catholicmatch

2025-06-27 Thread INVALID.NOREPLY
Follow-up Comment #2, task #16658 (group administration):

I guess I submitted it prematurely. Attached here is a newer version that's a
lot more finished.

Also, this project is more tricky/demanding than it seems at first glance.
Especially since it parses an undocumented unstable format, and there will be
heavy demand for reliability and clarity when other libre software uses it for
an import feature. It doesn't make sense to host this project without bug
tracking, mailing list, patch submissions, etc.

(file #57336)

___

Additional Item Attachment:

File name: serde-catholicmatch-2025-06-27.tar.gz Size: 22KiB




AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://savannah.nongnu.org/source/savane-ef91de49e2976f6d280ab934c829bfe625128396.tar.gz


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/


signature.asc
Description: PGP signature


[task #16658] Submission of serde-catholicmatch

2025-07-01 Thread INVALID.NOREPLY
Follow-up Comment #4, task #16658 (group administration):

New tarball is attached.

Cargo.lock and rust_fmt_version.txt intentionally don't contain notices
because they are automatically generated.

Additional dependencies needed for use:
- cargo, , MIT OR Apache-2.0
- rust, , MIT OR Apache-2.0

Additional dependencies for development:
- rustup, , MIT OR Apache-2.0
- clippy, , MIT OR Apache-2.0
- rustfmt, , Apache-2.0 OR MIT
- reuse, , Apache-2.0 AND CC0-1.0 AND
CC-BY-SA-4.0 AND GPL-3.0-or-later
- any implementations of the POSIX commands `env` and `sh`

(file #57347)

___

Additional Item Attachment:

File name: serde-catholicmatch-2025-06-30.tar.gz Size: 24KiB




AGPL NOTICE

These attachments are served by Savane. You can download the corresponding
source code of Savane at
https://savannah.nongnu.org/source/savane-ef91de49e2976f6d280ab934c829bfe625128396.tar.gz


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/


signature.asc
Description: PGP signature


[task #16658] Submission of serde-catholicmatch

2025-07-23 Thread INVALID.NOREPLY
Follow-up Comment #12, task #16658 (group administration):

[comment #11 comment #11:]
> [comment #10 comment #10:]
>> For consistency and clarity, I have now decided to use AGPL for the
>> Cargo.lock and rust_fmt_version.txt files, regardless of whether or not they
>> can be restricted by copyright. To work around the fact that these files are
>> automatically overwritten, I put the notices in the Cargo.lock.license and
>> rust_fmt_version.txt.license files. They are the same notices that other
>> files have, except I made the phrase "This file" more specific.
> 
> Copyrightable text files should include copyright and license notices
> themselves.

Custom additions to the top of these files are not preserved.

To be clear, the generation of these files is not a one-time initialization
thing.

> In other words, the exception of libgit2 allows linking with software under
> GPLv3; however, when a GPLv3-covered program is linked to other software,
> that other software should be distributable under the terms of GPLv3, and
> libgit2 doesn't allow that,
> www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs.

Does that just mean that any GPLv3 code that links to libgit2 needs to include
an exception to allow that linking?

If that is the correct understanding, then it's nothing to worry about, since
my library does not link to Cargo or anything that's only used by Cargo. The
only connection between libgit2 and my library is that Cargo would use libgit2
to download my library, if a dependency on my library is added in a special
way.

>> - All libraries listed under "N/A" in the output of cargo-license are
>> non-external libraries in the Rust repository. Their licenses are only
>> specified in REUSE.toml, not in the per-library Cargo.toml files.
> 
> Is there a reason why the licenses of those libraries may be ignored?

No, their licenses may not be ignored. They are specified in REUSE.toml. Those
libraries are not external dependencies, but rather inside of the Rust
repository. "N/A" is how the cargo-license tool indicates that the "license"
field is not listed in a library's Cargo.toml file.

>> - The Rust repository includes fonts licensed under OFL-1.1. I don't know if
>> that's a problem.
> 
> At least you should understand how it interacts with other licenses.

The only thing that gave me uncertainty is that gnu.org lists this license
under "Free licenses, incompatible with the GNU GPL and FDL". I'm still
confused about that.

I at least should know whether or not an HTML file may both use the OFL fonts
and include portions of my GPLed files, because the fonts are for Rust's
documentation generator.

> To be on the same page: all cargo-license lists are libraries, aren't they?

Mostly. It also includes packages that are inside of the current repository,
which aren't always libraries.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/


signature.asc
Description: PGP signature