Plugin Configuration Files Request

[Corile]

As a matter of fact the launcher used by Disco that was released by Laz and the latest release of FLHook are both GPLv3, which means you (and everyone else in this community) is legally entitled to any source code that is present on the up to date compiled release, and the staff has up to 30 days to comply on the request. Let's see how this ends.

This doesn't work like that. The code that is on GitHub is licensed as GPLv3. The GPLv3 license applies to the code, not the launcher of the FLHook instance running on the Discovery server. If the Discovery team forked the FLHook from GitHub and added additional features to the source code, then they would be bound by GPL and would be required to release the source code. I doubt that is the case, since the only thing that's different are the config files, and config files are not executable as such, hence not bound by GPLv3. (And possibly, even if it was, you could argue that it is not you who is running FLHook but Discovery servers hosted by the Discovery team, so GPL wouldn't even apply here at all).

Because configuration files can often contain confidential information, if your code is licensed on the GPL, that doesn't necessarily mean that you need to disclose your config files. Config files fall under the definition of a "corresponding source" in GPLv3 which need to only be disclosed when they are required to build, install or run the software under GPL. Since FLHook (from what I gather from the OP) runs just fine, but uses outdated configs, GPLv3's definition of "corresponding source" doesn't apply.

---

Reflections on the Revolution in Gallia
Custodi // High City of Heraklion // The Cult of Archangels
Log Filter // Post Creator // Manhattan