New license request: Autonomous Commons Dedication 1.0, 1.1 and 1.2 (ACD-1.0 / ACD-1.1 / ACD-1.2)

Aperta
  • Qualcosa non va?
#5,368 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
68/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
tooling

Direzione di ricerca

Start with the three frozen license texts and pin references supplied in the issue, then locate the existing license-rule format and tests used by scancode.api.get_licenses. Run the current API against each text to reproduce the fragmented expressions, including the proprietary-license match in versions 1.0 and 1.1. Done means each complete version is detected under its own acd-1.0, acd-1.1, or acd-1.2 key, with regression coverage for all three.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

License Name
Autonomous Commons Dedication, versions 1.0, 1.1 and 1.2 (ACD-1.0, ACD-1.1, ACD-1.2). Each version is a separate, frozen text: its bytes are pinned by SHA-256 in the repository and will not change. One rule per version is requested. Suggested keys: acd-1.0, acd-1.1, acd-1.2.

License Homepage URL

Reference URLs

License Notes

  • What it is: a public-domain dedication (Section 3) plus a separate, unconditional permissive licence (Section 4). The licence does not depend on the dedication being valid. It also has an explicit patent licence (Section 8). It places no conditions on recipients: no attribution, no notice, no share-alike. The closest existing keys are probably cc0-1.0 and unlicense. 1.1 and 1.2 are revisions of 1.0 with the same structure; 1.1 and 1.2 renumber some clauses relative to 1.0.
  • Why this is requested: without a rule, ScanCode 32.5.0 matches these texts in fragments. In ACD-1.0 and ACD-1.1, one fragment is reported as proprietary-license, via proprietary-license_544.RULE, on a phrase in Section 6.1 that grants permission ("for any purpose, commercial or non-commercial"). With scancode.api.get_licenses, the detected_license_expression for ACD-1.0 is public-domain AND proprietary-license AND unknown AND warranty-disclaimer AND unknown-license-reference AND unknown-spdx. ACD-1.2 rewords that phrase, so its detection no longer includes proprietary-license, but it is still matched in fragments (public-domain AND unknown AND warranty-disclaimer AND unknown-license-reference AND unknown-spdx). A full-text rule per version would let each text be identified as one licence.
  • Status, stated plainly: none of these versions is on the SPDX License List or OSI-approved. ACD-1.0 was posted for discussion on OSI license-discuss, which is not an approval submission. Its only use today is the steward's own repository. If that is below your bar for adding a licence, that is understood.
  • Disclosure: this account belongs to the licence steward. The licence texts were drafted by an AI model (Claude) on the steward's direction. This request was written and filed by the same AI assistant, at the steward's request.
Lingua principale
Python
Stelle
2.7k
Fork
831
Merge medio
3g 4h
PR unite (30g)
7

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di aboutcode-org/scancode-toolkit

Tutte le issue di aboutcode-org/scancode-toolkit

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.