License compatibility considerations

[chrysn]

I'm considering adding the iso-20022-camt as a dependency to a data conversion tool, but the tool will eventually need to be distributable through Debian, which is not possible with the current license (eg. due to the "must make [...] publicly available") clause.

The current license apparently serves to discourage extending use by EF competitors that is not propagated back. To my understanding, this goal might be achieved while simultaneously allowing use with Debian by doing an "EF-LPL OR AGPL-3.0-or-later" dual-licensing: AGPL places requirements that are in many regards stricter (eg. it makes requirements on showing prominently visible copyright notices in user interfaces) and thus rather unattractive for users, but it is usable in distribution contexts. Please consider adding such a licensing option.

One caveat to be aware of but that is easily addressed is that unlike EF-LPL's item (2)c, AGPL does not implicitly contain an implicit CLA. However, this should just as well be achievable by stating the requirement to transfer copyright in the CONTRIBUTING file. Some projects require contributed commits to sign off these terms (example, not precisely for copyright transfer but for license agreement); this may or may not be necessary in this case.