taskSavannah Administration - Tasks: task #16351, Submission of Emilua

 
 

task #16351: Submission of Emilua

Submitter:  Vinícius dos Santos Oliveira <vinipsmaker>
Submitted:  Sat 18 Mar 2023 10:16:11 AM UTC
   
 
Should Start On:  Sat 18 Mar 2023 12:00:00 AM UTC Should be Finished on:  Tue 28 Mar 2023 12:00:00 AM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Cancelled Privacy:  Public
Assigned to:  ineiev Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 18 Mar 2023 03:25:28 PM UTC, comment #5: 


> I used the ArchLinux package database to check the license for some of the dependencies. For OpenSSL 1.1 (which is the version I use), they list it as "BSD": https://archlinux.org/packages/core/x86_64/openssl-1.1/


This is my point: you don't bother to check if your dependencies are GPL-compatible, and in this case you actually end up with your package being GPL-incompatible---your users can't combine it with software under the GPL.

Savannah has no resources to continually verify if every hosted package follows our requirements.  We have to rely on the developers to maintain the compliance, and I believe a more responsible attitude is needed to that end.

Ineiev <ineiev>
Site Administrator
Sat 18 Mar 2023 02:31:47 PM UTC, comment #4: 

Thank you for the follow-up.

> Savannah hosting requirements say that the documentation should be released under FDL-compatible terms.  The GPL isn't compatible with the FDL.


But is CC-BY incompatible with FDL? If it is, I can change the license for the documentation. As far as I know, it should be compatible with FDL as well.

I wouldn't choose a documentation license to be intentionally incompatible with FDL, and CC-BY seemed permissive enough that shouldn't cause any troubles.

> I'm sorry.  Your submission suggested that you didn't really care of the licensing terms of your dependencies (e.g. OpenSSL is licensed under anything but "BSD", whatever it could mean),


I'm sorry. I used the ArchLinux package database to check the license for some of the dependencies. For OpenSSL 1.1 (which is the version I use), they list it as "BSD": https://archlinux.org/packages/core/x86_64/openssl-1.1/

I'm sorry for the trouble.

> and of our requirements generally ("runs on FreeBSD, Linux, or other systems").


Linux is my main system, so it is were things get tested. The code is portable and should run on other systems as well (which I test from time to time, but breaks once I develop new features and stay that way until I test and fix incompatibilities again).

Vinícius dos Santos Oliveira <vinipsmaker>
Sat 18 Mar 2023 02:09:36 PM UTC, comment #3: 


> How so? Boost Software License is a FSF-approved (and GPL-compatible) software license: https://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses


It's nice that you read GNU license list; it would be great if you followed its recommendations for naming licenses.

> Creative Commons Attribution 4.0 International License is also FSF-approved and GPL-compatible: <https://www.gnu.org/licenses/license-list.html#OtherLicenses>. I'm not using it for software, but for the documentation, so it doesn't deviate from FSF guidelines.


Savannah hosting requirements say that the documentation should be released under FDL-compatible terms.  The GPL isn't compatible with the FDL.

> I've read the hosting requirements before sending this submission. Could you help me to find my mistakes (if any) so we can work together on how I can adequate my project to the requirements?


I'm sorry.  Your submission suggested that you didn't really care of the licensing terms of your dependencies (e.g. OpenSSL is licensed under anything but "BSD", whatever it could mean), and of our requirements generally ("runs on FreeBSD, Linux, or other systems").

Ineiev <ineiev>
Site Administrator
Sat 18 Mar 2023 12:50:21 PM UTC, comment #2: 


> The licensing terms of your package are incompatible with Savannah hosting requirements.


How so? Boost Software License is a FSF-approved (and GPL-compatible) software license: https://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses

Creative Commons Attribution 4.0 International License is also FSF-approved and GPL-compatible: <https://www.gnu.org/licenses/license-list.html#OtherLicenses>. I'm not using it for software, but for the documentation, so it doesn't deviate from FSF guidelines.

I've read the hosting requirements before sending this submission. Could you help me to find my mistakes (if any) so we can work together on how I can adequate my project to the requirements?

Vinícius dos Santos Oliveira <vinipsmaker>
Sat 18 Mar 2023 11:13:20 AM UTC, comment #1: 

The licensing terms of your package are incompatible with Savannah hosting requirements.

Cancelling.

Ineiev <ineiev>
Site Administrator
Sat 18 Mar 2023 10:16:11 AM UTC, 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
Group administration page, accessible only to site
administrators logged in as superusers.

Registration Details


  • Name: Emilua
  • System Name:  emilua
  • Type: non-GNU software and documentation
  • License: Other license (The project uses the Boost Software License 1.0 which is pretty similar in effect to MIT and BSD licenses. Documentation is licensed under Creative Commons Attribution 4.0 International License. The license Boost Software License 1.0 makes it easier to contribute code back to the projects I make use of as dependencies in Emilua (e.g. the Boost libraries).)





Description:

Emilua is an execution engine for the Lua programming language. It offers to users of the Lua programming language, a runtime similar to what NodeJS offers for JavaScript. That is, it offers a concurrency runtime that abstracts IO operations offered by the underlying OS. Whether your Lua program runs on FreeBSD, Linux, or others systems, the same IO interfaces will be available. The project has been in development for over a few years, and it finally reached a point where it may be of use for more people, so I'll finally announce it soonish. Therefore, I need a mailing list, and I think Savannah is the right place to host the mailing list to have discussions with its users and potential contributors.

You may use Emilua in a range of projects, from building sites to building torrent clients.

As a consequence of developing Emilua, I found bugs in several free software projects, for which I either reported the bugs or even sent bugfix patches myself. Here are a few bugs that were solved as a consequence of this:


You can find the source code for the project at <https://gitlab.com/emilua/emilua>. The first commit dates back from 2020. However, the code for an earlier experiment that I did would date back even further (2018).

You may find detailed info on the project in the documentation hosted online at <https://docs.emilua.org/>. The same documentation is installed in the system (as manpages) when you build the project. There's a guix package for the previous version of the project. I'll update it to the next version as soon as I release the new version (I'm planning April 15).


Other Software Required:

LuaJIT - MIT - https://luajit.org/
Boost - Boost Software License 1.0 - https://www.boost.org/
Asciidoctor - MIT - https://asciidoctor.org/
fmt - MIT - https://fmt.dev/
sord - ISC license (also known as Zero Clause BSD) - https://drobilla.net/software/sord.html
Trial.Protocol - Boost Software License 1.0 - https://github.com/breese/trial.protocol
OpenSSL - BSD - https://www.openssl.org/
re2c - public domain - https://re2c.org/


Tarball URL:

https://gitlab.com/emilua/emilua/-/archive/master/emilua-master.tar.gz


Vinícius dos Santos Oliveira <vinipsmaker>

 

(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 vinipsmaker (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 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2023-03-18 ineiev StatusNone Cancelled
        Assigned toNone ineiev
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code