Licensing Issues

[maximsmol]

The Unlicense

The Unlicense has questionable legal power. We don't have to drop it since imo it most clearly communicates the intent to release to public domain but multi-licensing under another license with better understood legal impact would be great. I suggest one (or all) of these:

• MIT - most widely recognized, but carries an attribution requirement and is not public domain
• BSD0 - unencumbered and explicitly pre-approved for use in Google projects, but not public domain
• CC0 - public domain attribution with appropriate fallback license, has good legal basis as it is designed and maintained by Creative Commons. Appropriate to use in licensing software as opposed to other CC licenses. It is the only not OSI-approved license on this list

Contributor License

Currently migra is in a legal gray zone because it carries no explicit contributor licensing agreement. This can be added retroactively but would require reaching every contributor individually.

We would need to get the contributor license sorted out before we can re-license the code if we are to switch from the Unlicense.

Note: this all primarily applies to migra as a library rather than migra as a CLI tool