Bacula-users

Re: [Bacula-users] What new feature are you waiting for?

2008-11-06 06:27:10
Subject: Re: [Bacula-users] What new feature are you waiting for?
From: Arno Lehmann <al AT its-lehmann DOT de>
To: "bacula-users AT lists.sourceforge DOT net" <bacula-users AT lists.sourceforge DOT net>
Date: Thu, 06 Nov 2008 12:23:10 +0100
Hi,

I'm writing as a Bacula Systems founder here.

06.11.2008 03:45, Dan Langille wrote:
> On Nov 5, 2008, at 6:23 PM, Florian Heigl wrote:
>> If Kern's "Bacula Inc." would release a real, professional guy that
>> doesn't bloat my configs I'd pay for that any day. But bloating the
>> configs just in case a good gui comes around? hell no!
>>
>> sorry to be that harsh, but in this case I rather speak up on time...
>> florian
> 
> 
> I think you meant GUI, not GUY.  Easy typo.  But AFAIK, Bacula Inc
> is there to provide services, not code.

We have absolutely no problem creating code. Sure, our main objective 
is providing service, but creating add-ony, plugins, new features, or 
whatever you want can also be a valuable service to some customers.

Also, with Kern and Eric in the company, we're strongly involved in 
developing Bacula anyway, so you can expect some code (perhaps even 
code developed under a customer contract) from Bacula Systems anyway.

>  It's been stately quite clearly
> that there will not be two code bases.

That statement remains true - even if Bacula Systems develops core 
Bacula code under a customer contract, that code will be published 
with the regular Bacula sources. That's one of the conditions in all 
our development offerings.

Things *might* be a bit different for add-ons, where restrictively 
licensed third-party code is included; we don't have such a situation 
yet, and I don't think we will see something like this soon (after 
all, even the windows FD is open-source), but I wouldn't say that 
*every* line of code Bacula Systems ever develops will be open source.

Of course, that is no problem for add-ons that don't require linking 
to the Bacula core code, and with the upcoming plugin interfaces, it 
won't even be a problem for plugins - but there might be interesting 
plugins that can not be freely distributed. Again, I don't think we 
have such a situation in the near future.

By the way - among the founders of Bacula Systems, there is no 
disagreement over these points. We all strongly believe in the 
open-source idea, and we all will do our best to keep Bacula 
completely open source, with no closed-source spinoff or dual 
licensing happening.

That said, I wouldn't rule out Bacula Systems creating a commercial, 
closed source configuration tool - you just have to offer enough money ;-)

(But such a configuration tool could also be created by anyone else - 
the configuration file structure and syntax is not exactly hard to 
understand, it's extensively documented, and I guess that both parsing 
an existing configuration and creating a GUI is not exactly rocket 
science. It just seems to be that, while everybody would like a nice 
configuration tool, noone wants it bad enough to actually do the work. 
Which tells us something about the acceptance of text configuration 
files...)

Arno

> 

-- 
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
www.its-lehmann.de

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>