Bug 103 - Ensure that all source code actually has a copyright license
Summary: Ensure that all source code actually has a copyright license
Status: CONFIRMED
Alias: None
Product: Libre-SOC's first SoC
Classification: Unclassified
Component: Source Code (show other bugs)
Version: unspecified
Hardware: All All
: --- critical
Assignee: Luke Kenneth Casson Leighton
URL:
Depends on:
Blocks:
 
Reported: 2019-06-28 08:58 BST by Jacob Lifshay
Modified: 2023-11-10 09:29 GMT (History)
1 user (show)

See Also:
NLnet milestone: ---
total budget (EUR) for completion of task and all subtasks: 0
budget (EUR) for this task, excluding subtasks' budget: 0
parent task for budget allocation:
child tasks for budget allocation:
The table of payments (in EUR) for this task; TOML format:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jacob Lifshay 2019-06-28 08:58:43 BST 
I noticed that ieee754fpu doesn't have any licenses, we need to ensure that all our source ends up with a license or at least a comment directing to the file with the license.

We should try to include SPDX license headers for machine readability.

Example:
https://salsa.debian.org/Kazan-team/kazan/blob/master/Cargo.toml
https://salsa.debian.org/Kazan-team/kazan/blob/master/Notices.txt

License status key:
? -- unknown
Y -- properly licensed
N -- not properly licensed

Repository check list (edit to keep updated):

git.libre-riscv.org:

? crowdsupply.git
? freedom-sifive.git
N ieee754fpu.git
? libreriscv.git
? pinmux.git
Y riscv-isa-sim.git
? riscv-tests.git
Y rv32.git
? shakti-core.git
? shakti-iclass.git
? shakti-peripherals.git
? sifive-blocks.git
? soc.git
? sv2nmigen.git

Kazan-team on Debian Salsa:

Y algebraics
Y nmigen-type-annotations
Y simple-barrel-processor
Y softfloat-verify
Y softfloat-sys
Y kazan
Comment 1 Luke Kenneth Casson Leighton 2019-06-28 09:51:15 BST 
yehyeh, it's basically (implicitly) the license that jon dawson wrote,
for some stuff, and i just haven't been focussing on it.  the bugreport's
a good idea.