Legal statement

[pavel-kirienko]

Currently, the legal statement says this, which is not exactly correct:

UAVCAN is an interface standard open to everyone. No copyrights are reserved and no licensing is necessary for its implementation, distribution, or use. In no event shall the authors of the standard be liable for any damage arising, directly or indirectly, from its use.

A better wording should be found. The objectives are the following:

• We want the spec and related docs to be free and open in the spirit of CC-BY-4.0 except that the "No additional restrictions" limitation should be lifted.
• The liability disclaimer should be there.

[pavel-kirienko]

@thirtytwobits Can your OSS guru be of any help here?

[thirtytwobits]

Unfortunately not. Sorry. I reached out but nobody had advice on this beyond pointing out that AWS uses CC-BY-SA-4.0 on their github documentation. Not sure if that's helpful here.

Perhaps we should sniff around other open standards and see what they have. Here's my quick search:

https://xmpp.org/extensions/xep-0009.html#appendix-legal
https://www.xiph.org/ogg/doc/rfc3533.txt
https://www.w3.org/Consortium/Legal/2015/doc-license

[LorenzMeier]

I would advise for CC-BY as there is no point in limiting the use of documentation and those terms are pretty clear. CC-BY-SA makes it impossible to include any documentation in e.g. a vendor manual and that's probably not intended here.