That trap is easy to solve. Fork the bacula-fd code in AGPL and change that plugin_license part. ð
Atenciosamente, Heitor faria (Miami) https://www.youtube.com/@podheitor WhatsApp: +1 786-726-1749 | +55 61 98268-4220 Em ter., 28 de abr. de 2026, 11:52, RadosÅaw Korzeniewski < [email protected]> escreveu: > Hello, > > wt., 28 kwi 2026 o 17:14 Heitor Faria <[email protected]> napisaÅ(a): > >> Hello AFM, >> >> Thank you for writing, though I will be direct: this message contains >> several factual inaccuracies, and I would like to correct them for the >> list's benefit. >> >> On legal challenges: No legal concerns have been raised in this thread >> that apply to my software. The prior discussion was about the >> plugin_license string required by the Bacula FD API â a technical detail I >> have already addressed. >> > > This is not a technical detail, but a valid field describing the proper > license for the whole product. > > >> That is not a legal challenge; it is a configuration value. >> > > For the Bacula Community you can't legally load the plugin which is not > AGPLv3 licensed. You can provide external tools as "full copyright", i.e. I > prepared the proprietary (open-source version is available too) tool - > IBAdmin which manages Bacula Community without any plugin, just with simple > cli execs and sql queries. > > The plugins are proprietary commercial software. The documentation is >> public. Pre-built packages (RPM, DEB, Windows installer) are available for >> evaluation. That has been consistent throughout this discussion. >> > > If you distribute this software, or provide services based on a modified > version of it over a network, you have an obligation to provide the > corresponding source code to the users, unless you have a separate license > that permits otherwise. > > I hope this is clear. > -- > RadosÅaw Korzeniewski > [email protected] >
_______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
