Plugin Configuration Files Request

[Sally]

That is so wrong.

They don't need to do that, if they continue to push their code on a non public git they can do that and all you can do is nothing.

But, they can't forbid you to use any of the GPLv3 code they already made public as long as you don't try to make any profit.

Wrong, GPL doesn't have commercial restrictions, in fact commercial distribution is part of freedom 2 (freedom to redistribute), so long you distribute source code or you grant access to it upon request, you can sell it at whatever price you want.

Posting such false facts is literally the worst you could do.

The irony of saying this while doing exactly that, give the GPL a read sometime.

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.

They did add features recently and they did in several instances, the most recent case being the POB rework from a few days ago, and they used a fork from TheStarport which is GPLed to implement such rework, you can check Aingar's profile on Github.

You may not be legally bound to provide configuration files but a template is still necessary to make it work and there are configuration files that are completely missing as pointed out already. The server side issue may be correct, these cases is why AGPL was written, a shame it isn't licensed under AGPL.

---

"I suppose many people will continue moving towards careless computing, because there's a sucker born every minute." - RMS