Hello,
On 11/26/2013 11:17 AM, Silver Salonen wrote:
> Hi Kern.
>
> Thank you for the information and here are some requests for more
> details :)
>
> On 25.11.2013 18:49, Kern Sibbald wrote:
>> 2. The Bareos fork of Bacula:
>>
>> Unfortunately, despite the fact that Bareos hired one of the best
>> German Open
>> Source lawyers , there were a number of serious copyright violations
>> with their code.
>
> I guess mixing copyright and open source into one sentence makes
> several people quite confused, so can you clarify what are the issues?
All code is licensed one way or another. Virtually all Open Source code
also has a copyright (the GPL is a copyright with
a license). I would not like to burden this list with copyright/license
details, so I will do so in my blog
in detail, and besides right now I am "on vacation" so please excuse me
for not giving any more
details at the moment.
> Is it, for instance, that Bareos wants to change license of the source
> code, but copyright holder does not permit it?
Most of the problems were that they incorrectly added their copyrights
where they legally could
not. I can imagine they would like to change the license, but that is
speculation on my part.
What is not speculation is that they cannot change the copyright license.
>
>> So as Bacula contributors and users, you would be within
>> your rights to feel very upset with Bareos, because they never
>> offered you the code they developed.
>
> I have understood that all of their code is in Github. Isn't it so?
You will need to ask Bareos if all their code is on Github since I don't
have
access to their company. At least the main source code is there.
>
>> I assure that I will do all in my power to ensure that any
>> worthwhile features that Bareos implements will be implemented in
>> Bacula, and most likely better integrated and more robust, and where
>> possible with even more functionality and growth potential.
>
> How would you do it? Would you port the features, possibly making the
> code better?
> Or would you just code the features from scratch?
To keep the Bacula FSFE copyright clean, we will probably need to code the
features from scratch. However, one must realize that when coding a feature
in Bacula, if two people do the same thing, there could be a substantial
overlap
of the code since one would naturally use a lot of the internal subroutines.
>
> I'm sorry, but currently it seems there is some soap opera going on
> between these 2 projects and it is just sad to watch. I really do hope
> that it won't affect good ideas being spread between the 2 projects
> and also in the open etc.
What gives you the idea that there is a soap opera going on? And what
do you find sad?
Hopefully not something that I have done.
Certainly, if Bareos has good ideas, we will be very interested in them as
I have already stated just above. They will clearly directly take
anything from
Bacula that they consider useful.
>
>> 3. Bacula Systems and the FSFE:
>>
>> There are a number of points in the agreement, but probably the most
>> important of all is that Bacula Systems has now put in writing that it is
>> an Open Source company (at its heart), as it has always proclaimed,
>> and will
>> contribute all the Enterprise code it creates to the Bacula Community
>> code
>> base within at most a 5 year period.
>
> So all the Bacula Enterprise features and plugins will ultimately be
> open sourced?
Yes. Some such as our Oracle plugin will not be Open Sources since it
uses the Oracle API which
is proprietary. At the moment, this is the only exception I can think
of though.
> Ie. we would see the delta plugin and vSphere plugin as open-source
> within 5 years counting from the point they were announced?
The answer is yes, but with the nuance that the time period for code
developed prior to the agreement
starts as of the agreement.
>
> Does it also mean that these features, by worst case scenario, in the
> open source version will always be 5 years behind the Enterprise version?
Yes.
> Do you have any features in mind that you would make open sourced
> within the shorter time-frame?
Yes we will probably make many available well before the 5 year period
(I would guess even most features).
I have a number of features in mind that we are internally agreed on and
others that we are
considering. The official announcement on what they are will certainly
be made at the Bacula Conference
or possibly earlier.
Best regards,
Kern
>
> --
> Silver
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
