[Savannah-register-public] [task #15019] Submission of uLisp-TFT

[Ineiev]

Update of task #15019 (project administration):

  Status: In Progress => Done   
 Open/Closed:Open => Closed 

___

Follow-up Comment #4:

Oh, I'm sorry, I misread your submission in the way that you were going to
release your changes under a permissive license.

If the intention is to release the new thing under the GPLv3+, I think you can
leave the original copyright and license notice in that file with a
clarification that they are the notices for the original package and that this
version is under the GPL.

Approving.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15019] Submission of uLisp-TFT

[Christopher Howard]

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

I've attached a new tarball. I've separated my code from the original project
code, so they could have separate license headers.

(file #44784)
___

Additional Item Attachment:

File name: ulisp-tft.tar.gz   Size:140 KB


___

Reply to this item at:

  

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

[Savannah-register-public] [task #15019] Submission of uLisp-TFT

[Christopher Howard]

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

This is a little complicated because I really want my changes copylefted under
the GPL, but the project is only a single source code file, and the MIT
license requires the license text to appear in all "significant portions" of
the original work. Let me see if I can use "includes" to separate out my code
from the original project file. 

I'll take another look at the README.md file.

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15019] Submission of uLisp-TFT

[Ineiev]

Update of task #15019 (project administration):

  Status:None => In Progress
 Assigned to:None => ineiev 

___

Follow-up Comment #1:

In your tarball, the licensing terms are specified in a little bit confusing
way: the source is essentially a single file, but there is nothing that would
let the user know which parts could be used under the permissive license.

Then, the README.md file also needs copyright and license notices, and it
would be better if you used canonical forms for copyright and license notices
of the package there (not "GPLv3+", it would do as a tech speak, but not for
general public, and not just "copyright", but cite the years and use a
separate line for it).

At last, there is no need for having a short license like MIT in a file, such
licenses should be written directly in the relevant files.

Could you fix that?

___

Reply to this item at:

  

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

[Savannah-register-public] [task #15019] Submission of uLisp-TFT

[Christopher Howard]

URL:
  

 Summary: Submission of uLisp-TFT
 Project: Savannah Administration
Submitted by: creationist
Submitted on: Fri 10 Aug 2018 01:39:01 AM UTC
 Should Start On: Fri 10 Aug 2018 12:00:00 AM UTC
   Should be Finished on: Mon 20 Aug 2018 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: *uLisp-TFT*
* System Name:  *ulisp-tft*
* Type: non-GNU software and documentation
* License: GNU General Public License v3 or later (The primary source code
file is a modification of the uLisp source code, which is copyright David
Johnson-Davies and licensed under the MIT license.)



 Description: 
uLisp-TFT integrate native functions into uLisp for using a TFT LCD Shield.
Development is currently being done using the Kuman (TM) 3.5" TFT LCD Shield.


 Other Software Required: 
- Adafruit GFX library, BSD (2-Clause?)
https://github.com/prenticedavid/MCUFRIEND_kbv/blob/master/license.txt
- MCUFRIEND_kbv library , BSD (2-Clause?)
https://github.com/prenticedavid/MCUFRIEND_kbv/blob/master/license.txt


 Other Comments: 
Changes are currently small but I am intending to add more native functions.


 Tarball URL: 
https://savannah.nongnu.org/submissions_uploads/ulisp-tft.tar.gz






___

Reply to this item at:

  

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