NGI0-REUSE SPDX license and copyright commentheaders #1

Open
opened 2023-08-08 09:40:57 +00:00 by jithendra · 1 comment

Hello!

By way of introduction, I am jithendra with the Free Software Foundation Europe, a consortium member of the NGI0 Initiative, of which you have signed liminix up for participation and funding. Part of what is offered with your involvement with NGI0 is help from us with your project on your copyright and license management.

After a quick check on the repositories of your project, we saw that the project needs a standardized way for displaying copyright and licensing information. In case you are interested in automating the process in a standardized way, our REUSE specifications (https://reuse.software) intends to make licensing easier with best practices to display legal information through comment headers on source files that can be easily human and machine readable. The REUSE specification makes the process of applying licenses to files and compliance checking much easier.

Please let me know if you are interested, then I can add the comment headers using REUSE and send a Pull Request so you get an idea on how it looks like! Please also do not hesitate to contact me in case you have any questions.

Thank you

Best
Jithendra (Free Software Foundation Europe)
jithendra@fsfe.org

Hello! By way of introduction, I am jithendra with the Free Software Foundation Europe, a consortium member of the NGI0 Initiative, of which you have signed liminix up for participation and funding. Part of what is offered with your involvement with NGI0 is help from us with your project on your copyright and license management. After a quick check on the repositories of your project, we saw that the project needs a standardized way for displaying copyright and licensing information. In case you are interested in automating the process in a standardized way, our REUSE specifications (https://reuse.software) intends to make licensing easier with best practices to display legal information through comment headers on source files that can be easily human and machine readable. The REUSE specification makes the process of applying licenses to files and compliance checking much easier. Please let me know if you are interested, then I can add the comment headers using REUSE and send a Pull Request so you get an idea on how it looks like! Please also do not hesitate to contact me in case you have any questions. Thank you Best Jithendra (Free Software Foundation Europe) jithendra@fsfe.org

Hello!

Sorry for the delay in responding to you: I hadn't realised this repository had issues enabled so have not been checking them regularly.

Yes, this sounds very useful, and thanks for offering to take it on.

Some guidelines:

  • all the original code in Liminix is MIT-licensed.
  • some patches that are potentially upstreamable need to be license-compatible with the upstream projects: though I know of not case where MIT is incompatible with any other common license, I'd be happy to CC0 those files
pkgs/kernel-backport/gentree-writable-outputs.patch
pkgs/kernel/cmdline-cookie.patch
pkgs/kexec-map-file.patch
pkgs/mtdutils/0001-mkfs.jffs2-add-graft-option.patch
  • pkgs/tufted/tftp.lua is, per the top-of-file comment, a fork of another project that is MIT licenced.

I can't remember any other licensing weirdness, but please do let me know if you find anything unclear.

Thanks!

Hello! Sorry for the delay in responding to you: I hadn't realised this repository had issues enabled so have not been checking them regularly. Yes, this sounds very useful, and thanks for offering to take it on. Some guidelines: * all the original code in Liminix is MIT-licensed. * some patches that are potentially upstreamable need to be license-compatible with the upstream projects: though I know of not case where MIT is incompatible with any other common license, I'd be happy to CC0 those files ```` pkgs/kernel-backport/gentree-writable-outputs.patch pkgs/kernel/cmdline-cookie.patch pkgs/kexec-map-file.patch pkgs/mtdutils/0001-mkfs.jffs2-add-graft-option.patch ```` * pkgs/tufted/tftp.lua is, per the top-of-file comment, a fork of another project that is MIT licenced. I can't remember any other licensing weirdness, but please do let me know if you find anything unclear. Thanks!
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: dan/liminix#1
There is no content yet.