Dear all,

I maintain the `rust-difftastic` package, a structural diff tool; in a
recent update it has started unbundling the tree-sitter parsers it
used, and as part of the review process for the new crates, this came
up:

https://bugzilla.redhat.com/show_bug.cgi?id=2421761

- difftastic previously used tree-sitter-clojure
- this is CC0-1.0 licensed which is no longer allowed for code in
Fedora (but this usage might be considered grandfathered in -- though
we'd need to file for a retroactive exemption I guess) -
https://lwn.net/Articles/902410/
- tree-sitter-clojure is then forked to tree-sitter-clojure-orchard -
conversation: https://github.com/Wilfred/difftastic/pull/915 - citing
upstream not uploading to crates.io. Apparently there's yet another
fork as well (which requires a newer Rust version)
- the fork difftastic ended up using claims it is MIT licensed:
https://codeberg.org/grammar-orchard/tree-sitter-clojure-orchard/blame/branch/main/Cargo.toml
- but the LICENSE file it bundled is still CC0-1.0 which is how this
issue was surfaced

Any suggestion how to proceed here? I'm temporarily yanking the Clojure
support out of difftastic until this is resolved. Of question:

- is such a relicensing away from CC0-1.0 by a fork allowed? In which
case I will put up a PR to the fork so it carries both license texts
and explain the relicensing
- if not, does the grandfathering of existing CC0-1.0 software cover
forks too?

The difftastic upstream (cc:ed), after I brought this to his attention,
has requested that the original tree-sitter-clojure be dual-licensed
CC0/MIT, which will resolve this too:

https://github.com/sogaiu/tree-sitter-clojure/issues/71

Best regards,

-- 
 _o) Michel Lind
_( ) identities:
https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2
     README:     https://fedoraproject.org/wiki/User:Salimma#README

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
_______________________________________________
legal mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to