Heitor, você é conhecido no Brasil por ter enganado seus clientes. Você mesmo sabe o que aconteceu, ou já esqueceu tudo isso? Vamos esperar para ver quem mais, entre seus antigos clientes, se manifestará sobre o assunto. Um vigarista sempre será um vigarista e um mentiroso sempre será um mentiroso.
________________________________ From: Rob Gerber <[email protected]> Sent: Tuesday, April 28, 2026 10:03 PM To: Heitor Faria <[email protected]> Cc: bacula-users <[email protected]> Subject: Re: [Bacula-users] PodHeitor Incremental Accelerator, Ransomware Detection and Remediation Plugin for Bacula I am not a lawyer, or an expert in AGPLv3. I will try to help, but please understand that I may make a mistake. It is complicated, but no, I very much doubt that Bacula Enterprise is violating any licenses. The right to license any code belongs to the entity or person who owns the copyright on that code. Bacula Systems owns the copyright to the Bacula Enterprise code. They can release it under any license they wish. They have released some of the Bacula Enterprise code in Bacula CE under the AGPL. They can also choose to release Bacula Enterprise code under any other license they wish. I think it might be more complicated for code to go backwards, from Bacula CE to Bacula Enterprise. For this reason, the Bacula CE project probably requires any CE contributors to transfer (assign) copyright of the contributed code to the Bacula CE project foundation. The Bacula CE project can then license the contributed code back to Bacula Systems, under any license they wish. I believe most Bacula CE developers are employees of Bacula Systems. As the copyright holder of code you personally authored, you are entitled to license it under any terms you wish. However, you wish to use your code as part of another software project, Bacula CE. Bacula CE's license (AGPLv3) explicitly requires that any code that that interacts "too closely" with bacula also be licensed AGPLv3. What does "too closely" mean? I am not certain, but I have heard that an AGPLv3 program cannot use libraries not licensed AGPLv3. Based on what Radoslaw and others are saying, I suspect plugins are also covered by this restriction. I think there are probably limits to the "infectious" nature of the AGPLv3. Radoslaw's program only interacts via the bconsole interface, in the same way a human might. Maybe this is a clue to ways to work around this issue. Maybe a config file is not covered by the AGPLv3, for example. Read carefully what Radoslaw said about using MetaPlugin. Maybe it can help you. Understanding the requirements of the licenses of the open source projects you wish to use is just as important as the code you write, maybe moreso. You should be aware that AIs are very unskilled for legal tasks. You should not rely on an AI to assist with legal advice. You need to retain an experienced intellectual property lawyer. Robert Gerber 402-237-8692 [email protected]<mailto:[email protected]> On Tue, Apr 28, 2026, 1:07 PM Heitor Faria <[email protected]<mailto:[email protected]>> wrote: So I guess Bacula Systems product, Bacula Enterprise, violates AGPL too... 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, 13:05, Radosław Korzeniewski <[email protected]<mailto:[email protected]>> escreveu: Hi, wt., 28 kwi 2026 o 18:25 Heitor Faria <[email protected]<mailto:[email protected]>> napisał(a): PVT. Not joking. Why dont you find is a valid solution? b/c you do not have the right to change the license of the product you do not own. (caveat: I'm assuming you did not get a dual-license from Bacula Systems for your product, right?) Your patch does not change the license, so it will be useless from the legal standpoint. Sure, you can do whatever you want in your own lab. You can mix and match licenses, change the code, produce the new code, even proclaim independence for this mix. Nobody's care. But when you want to publish or provide services to your customers, you need to comply with the license. You can't build a commercial solution without publishing or providing services. All you can do is to split/separate your product on the AGPLv3 and the proprietary parts. As I wrote, I did something like this for IBAdmin - an advanced webgui which does not violate AGPLv3 b/c it is just exec('bconsole') to manage Bacula. No plugins, no problem. So, to follow these principles you can use MetaPlugin infrastructure to provide two layer solutions - plugin and backend. In this case all you need is to provide opensource (AGPLv3) FD plugin based on MetaPlugin protocol. This should work for application plugins like K8S available in Bacula or vSphere advertised by you. On the other hand, your "Incremental Accelerator, Ransomware Detection and Remediation Plugin" is already two layer solution (as I can understand from the overall architecture), so only the FD part needs to be AGPLv3 compliant and your "PodHeitor Sentinel Daemon" can use any license you want - as long as the boundary is unix socket/named pipes as described at the architecture. Ask for advice from your local Intellectual Property lawyer to ensure your ideas are compliant and your business can survive. I wish you a very well for your new business solution. Fingers crossed. best regards -- Radosław Korzeniewski [email protected]<mailto:[email protected]> _______________________________________________ Bacula-users mailing list [email protected]<mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
