Tool licensing for Beman.transcode

Beman Project Development
1

I am considering, being ridiculously over cautious, shifting the license of some python tools in transcode from the default Apache to zero clause BSD, and an extra readme, to clarify that the tools and the headers and tables they produce are unencumbered and can be used directly by any implementor without incurring obligations. WhatWG specifically contemplates this sort of use of their data, and I’m not reusing their code, just read their docs.

Not that it’s actually more than a couple hours of work and there are tons of upstream test cases.

Thoughts? Problems I’m not thinking of?

(Actual code to come over soonish)

2

Along the way we removed MIT as an option and never really supported BSD – but then this is still in your private repo and not Beman – is the intent to bring it over? You might recall that at least STL at MSFT basically said they can’t use MIT licensed stuff – not sure if BSD is similar or not, but my guess is yes bc if I recall it has to do with the attribution clauses.