<blockquote>
However, MOST of the code developed by Bacula Enterprise are in the form of
Plugins (Vmware, Databases, etc.) (...) that CAN'T be considered derivations /
modifications of the original Bacula Source code.
Bacula plugins are derived work of Bacula code. Please read my discussion with
Kern about 2010 when I start developing a PostgreSQL plugin for Bacula:
Kern Sibbald:
"(...)
There are varying opinions on whether or not a plugin is a derived work or
not, but it is and has always been the opinion of the FSFE that a shared
object (as is the case for Bacula plugins ) is a derived work, which means
that it must have the same license (or at least one that is compatible).
</blockquote>
Hello Mr. Radoslaw: This is more a political / philosofical opinion from FSFE,
but its not law technically right.
<blockquote>
I personally am probably a bit more open to different possibilities, but I
firmly believe that if you are extending Bacula with a plugin , you should
give back to the community by providing it with your source code.
(...)"
</blockquote>
This was probably an option from a Bacula community developer.
<blockquote>
So, I extended a Bacula with a plugin and released it with AGPLv3 license.
Releasing a plugin with a different license is a bit complicated because Bacula
allow plugins with a specific licenses only:
fd_plugins.c:1160:
if (strcmp(info->plugin_license, "Bacula AGPLv3") != 0 &&
strcmp(info->plugin_license, "AGPLv3") != 0) {
Jmsg(NULL, M_ERROR, 0, _("Plugin license incompatible. Plugin=%s
license=%s\n"),
plugin->file, info->plugin_license);
I'm not talking here about Bacula Enterprise because it has a different
license.
best regards
--
Radosław Korzeniewski
</blockquote>
What is the definition of derived work? They are *transformations* from a
original work, like rearrangements, instrumentation, presentation, translation
etc.
We can't say that plugins are derived work, since there is a division between
Bacula core original code and the plugin code. In fact there is not even GPL
plugins (that I know) similar to the ones Bacula Enterprise provide, so we
could no even argue that they are not original code.
A question for every one: if plugins needed to hold the same license that the
core application code, what about the RunBefore / After job scripts? Aren't
they original work? Are they code?
IMHO the license is the *law* for the application, and this law can't embrace
every of its accessories (3rd party libraries, plugins, scripts etc.),because
we would be going into a rights deadlock / inferno / rights instability. Of
course, there is a limit.
Regards,
==============================================================================
Heitor Medrado de Faria - LPIC-III | ITIL-F
02 a 13 de Março - Novo Treinamento Telepresencial Bacula:
http://www.bacula.com.br/?p=2174
61 8268-4220
Site: www.bacula.com.br | Facebook: heitor.faria | Gtalk: heitorfa...@gmail.com
===============================================================================
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
