Hi,
I misunderstood something. It was written on the list that the software is
AGPL, so I assumed that these plugins would also be under the same license. If
I understand this correctly, AGPL software must be published to the public. I
apologize for the misunderstanding; it was my fault. In summary, the Bacula
Community is freely available from the Bacula.org website, while PodHeitor is a
commercial product under a different license.
Thank you for the heads up!
Heitor Faria <[email protected]> schrieb am Dienstag, 28. April 2026 um
18:13:
> 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. That is not a legal challenge; it is a configuration value.
>
> On source code and GitHub: I have made no statement anywhere — on this list
> or elsewhere — indicating that I plan to publish the source code for free on
> GitHub. That is simply not accurate. The licensing model is commercial, all
> rights reserved, and I am still evaluating whether a partial open-source
> release makes sense. I said exactly that in my previous message.
>
> On "plans to publish for free use": I do not know where this came from. I
> would ask that if someone is going to attribute a statement to me on a public
> mailing list, they cite where I said it.
>
> 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 have a genuine technical or licensing question, I am happy to answer
> it.
>
> Best regards,
> Heitor Faria
> PodHeitor
>
> On Tue, Apr 28, 2026 at 6:29 AM A.F.M via Bacula-users
> <[email protected]> wrote:
>
>> Dear all,
>>
>> I am reaching out to address what has become a rather perplexing situation
>> on this mailing list regarding the software in question. Mr. Heitor, I would
>> greatly appreciate it if you could provide some clarity on the current
>> status of your solution.
>>
>> From the discussions that have taken place here, it appears that there are
>> some compelling arguments suggesting that the use of your software may lead
>> to potential legal challenges. This raises some important questions for all
>> of us involved. I would like to invite other users on this list to share
>> their insights regarding the licensing situation of your software, as it is
>> crucial for us to understand the implications before proceeding further.
>>
>> The recent additions to the Bacula community product seem quite promising,
>> and I believe many of us are excited about the possibilities they present.
>> However, without a clear understanding and an official statement regarding
>> the legal aspects, it becomes quite challenging for us to make informed
>> decisions moving forward.
>>
>> Additionally, could you please share the source code of your product? If I
>> am not mistaken, you have plans to do so and intend to publish your product
>> on GitHub for free use. This would certainly help in alleviating some of the
>> concerns and uncertainties that have been raised.
>>
>> Thank you for your attention to this matter, and I look forward to your
>> prompt response and assistance.
>>
>> Arno Lehmann via Bacula-users <[email protected]> schrieb
>> am Montag, 27. April 2026 um 10:29:
>>
>>> Hello Heitor,
>>>
>>> Am 24.04.2026 um 14:38 schrieb Heitor Faria:
>>> > Hello Arno,
>>> >
>>> > Long time, no writing.
>>>
>>> Quite so...
>>>
>>> > Thanks for your feedback. I highly value this.
>>> >
>>> > I would like to understand them a bit better. Are those plugins
>>> > going to
>>> > be Open Source? Do you have any specs and documentation published?
>>> >
>>> > I'm still deciding about the licensing. Any insights? For now, it is
>>> > just full copyright.
>>>
>>> This, frankly, sounds dubious... Full copyright is not telling me
>>> anything. Doe you mean "all rights reserved"?
>>>
>>> > I have all the documentation, which I'm publishing progressively.
>>> > Please verify the AKA Sentinel Plugin Whitepaper: https://
>>> > baculaenterprise.com.br/wp-content/uploads/2026/04/PodHeitor-
>>> > Incremental-Accelerator-Ransomware-Detection-and-Remediation-Plugin.pdf
>>> > <https://baculaenterprise.com.br/wp-content/uploads/2026/04/PodHeitor-
>>> > Incremental-Accelerator-Ransomware-Detection-and-Remediation-Plugin.pdf>
>>>
>>> In this particular case, I see a very specific solution, seems to be a
>>> combination of incremental accelerator where you try to use the change
>>> tracking to also react to bulk changes. Good idea, in a way, although I
>>> doubt it will work reliably. However, that's not based on actual
>>> knowledge as I have not tried your plugin/add-on.
>>>
>>> > Right now, I read big claims and no details at all, your github
>>> > pages do
>>> > not show anything about those,
>>> >
>>> > Because they are still private repositories.
>>>
>>> Do you intend to make those visible?
>>>
>>> > your web site is full of statements I
>>> > find, politely expressed, doubtful, and your offers seem to
>>> > aggressively
>>> > target Bacula Systems and other large backup software.
>>> >
>>> > I wouldn't say aggressive, but competitive.
>>>
>>> Fair enough in some respect, although I must admit I don't see how your
>>> Bacula Enterprise Appliance can be competitive. I also think your
>>> references are to a large extent not yours, but from Bacula Systems. The
>>> same for all the plugins you mention.
>>>
>>> > My plugins were extensively tested in real environments, and
>>> > the experiments are reproducible.
>>> > I will gladly send anyone on this list an RPM, DEB, or exe (depending on
>>> > OS and component) of their choice for personal use or testing purposes.
>>> > I would highly appreciate that, in fact.
>>>
>>> Excellent. For testing in my lab, I'd appreciate a .deb for Debian 12 or 13.
>>>
>>> > Can you show us anything that would kind of prove you can actually
>>> > deliver on those promises? -- After all, you're using this mailing list
>>> > for your marketing, which I consider reasonable (ok, borderline
>>> > reasonable :-) as it's surely interesting for Bacula users, but you're
>>> > not giving us anything to discuss. I want this to remain a
>>> > discussion list.
>>> >
>>> > I'm sorry about the tone and shallowness. Before you sent this, I had
>>> > already instructed my AI to provide more technical details on those
>>> > launch statements.
>>>
>>> And now I'm really disappointed... does this imply I'm conversing with
>>> an AI, not a person now?
>>>
>>> Looking forward to clarifications,
>>>
>>> Arno
>>>
>>> > Regards,
>>> > --
>>> > Heitor faria (Miami)
>>> > https://www.youtube.com/@podheitor <https://www.youtube.com/@podheitor>
>>> > WhatsApp: +1 786-726-1749 | +55 61 98268-4220
>>>
>>> --
>>> Arno Lehmann
>>>
>>> IT-Service Lehmann
>>> Sandstr. 6, 49080 Osnabrück
>>>
>>>
>>>
>>> _______________________________________________
>>> Bacula-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>>
>>
>> _______________________________________________
>> Bacula-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
> --
>
> Atenciosamente,
>
> Heitor faria (Miami)
> https://www.youtube.com/@podheitor
> WhatsApp: +1 786-726-1749 | +55 61 98268-4220
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
