Fleet rule (culturebotai-claw#394): data CC0-1.0, code BSD-3-Clause. What this repository ships on origin/main:
LICENSE is a custom scope document (GitHub reads it as NOASSERTION): CC0 for authored material, third-party material keeps its own terms. Of 17 adopted sources, 7 are CC0_OK, 6 ATTRIBUTION, 1 RESTRICTED, 1 NONCOMMERCIAL, 2 UNVERIFIED.
|
shipped |
rule |
| code |
CC0-1.0 (custom text) |
BSD-3-Clause |
| data |
CC0-1.0 authored; third-party mixed |
CC0-1.0 |
To change
- Add
LICENSE = BSD-3-Clause for the code and set pyproject.toml license to match.
- Add
LICENSE-DATA = CC0-1.0 for the records, with the boundary below, and say in the README which files each covers.
- Whatever lands here is what the public fleet page must render (
CultureBotAI.github.io/_fleet/fleet_fragment.html carries the strings by hand today).
The data half needs a boundary, not a blanket
A row derived from an ATTRIBUTION-class source cannot be re-released CC0 without discarding the attribution its source requires, and a NONCOMMERCIAL or RESTRICTED source cannot be redistributed as data at all. So "data CC0" here means: authored and CC0_OK-derived records CC0-1.0, with every other record carrying its source's licence in the record -- this schema already has licence slots for that. The repository-level file then states the default and the exception, and the source queue's redistribution column is the evidence.
Filed alongside the same issue in every Mech; the policy and its check live in claw.
Fleet rule (culturebotai-claw#394): data CC0-1.0, code BSD-3-Clause. What this repository ships on
origin/main:LICENSEis a custom scope document (GitHub reads it as NOASSERTION): CC0 for authored material, third-party material keeps its own terms. Of 17 adopted sources, 7 are CC0_OK, 6 ATTRIBUTION, 1 RESTRICTED, 1 NONCOMMERCIAL, 2 UNVERIFIED.To change
LICENSE= BSD-3-Clause for the code and setpyproject.tomllicenseto match.LICENSE-DATA= CC0-1.0 for the records, with the boundary below, and say in the README which files each covers.CultureBotAI.github.io/_fleet/fleet_fragment.htmlcarries the strings by hand today).The data half needs a boundary, not a blanket
A row derived from an ATTRIBUTION-class source cannot be re-released CC0 without discarding the attribution its source requires, and a NONCOMMERCIAL or RESTRICTED source cannot be redistributed as data at all. So "data CC0" here means: authored and CC0_OK-derived records CC0-1.0, with every other record carrying its source's licence in the record -- this schema already has licence slots for that. The repository-level file then states the default and the exception, and the source queue's
redistributioncolumn is the evidence.Filed alongside the same issue in every Mech; the policy and its check live in claw.