Clarify API license

[lealanko-rt]

The tomu-bootloader repo is licensed (presumably in its entirety) under GPL3. It's not immediately clear what this means for DFU applications that are made compatible with Toboot with the aid of toboot-api.h. It seems exceedingly unlikely that using a single header with some constant and struct definitions would turn an application into a "modified version" of Toboot in the sense of GPL.

Still, it would be clearer if the API header were licensed more permissively, e.g. with an explicit permission that allowed it to be used for making non-GPL applications compatible with toboot.

[xobs]

I am willing to license toboot-api.h under any sort of permissive license, such as Apache or MIT.

What would be the best way to do that? Just adding it to the header of toboot-api.h, or also adding it to LICENSE?

[mithro]

@xobs Add the license header to the toboot-api.h and mention it in the README. Don't update LICENSE file (otherwise you'll break GitHub license detection).

[mithro]

https://opensource.google.com/docs/releasing/preparing/#Apache-header

[xobs]

I've added a note to README.md and added the header to toboot-api.h.

[lealanko-rt]

This is perfect, thanks!