My question is particularly motivated by the question of what to do for the flatpak, but I guess it applies to the AppImage and Windows and Mac binaries too.
Since the release builds are done with -DBUILD_GPL_PLUGINS=ON and OpenBabel (GPL) is distributed with Avogadro as an essential component, I’m pretty sure that means the flatpak and the various binaries should be GPL-licensed themselves, even though the Avogadro code itself is BSD?
Maybe some subtle updates to the “About Avogadro” window would be appropriate (listing the licenses for the program, the Avogadro code, and for Open Babel), but primarily this is just about making sure the correct license is provided in the flatpak’s metadata
Sure, but in this case it is being provided as part of a bundle, while the binaries remain separate, as in the binaries on GitHub. The situation is analogous to the AppImage really. So should we be declaring the license of the flatpak as BSD-3-Clause
or BSD-3-Clause AND GPL-2.0-only
?
I’m not trying to start a discussion as much as get a judgement call from you as project lead
In the flatpak-builder docs you can see that the flatpak manifest can include an appdata-license field with the description
Replace the appdata (metainfo) project_license field with this string. This is useful as the upstream license is typically only about the application itself, whereas the bundled app can contain other licenses too.
which is what made me wonder about this. If it’s been discussed and settled in the past, apologies.