<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
As part of the website redesign (still in progress), we have also
reworked the Bacula manuals to fix the broken links between the 5
documents as well as to include a new more modern cover page.&nbsp;
Hopefully before the end of March when the next Bacula release is
scheduled (it may be deferred into April if the testing doesn't go
well), I will also have found the time to do a bit of cleanup of the
manual and backport the cleanups/clarifications that we have made to
the Enterprise manual.&nbsp; <br>
<br>
The current manual has bee taken by the Bareos project, and my name
as the principle author was removed, which given that it is the
fruit of 14 years of hard work, is not acceptable to me.&nbsp; To avoid
this in the future, I am considering (90% decided) to switch the
license from the current <strong>GNU Free Documentation License </strong>to
the <b>Community Commons Attribution-ShareAlike 4.0 International
Public License.<br>
<br>
</b>For you as users, as far as I can see (I am not a lawyer) there
is little difference as the new CC-BY-SA gives you the same rights
and is a Free Software license.&nbsp; The difference is that people who
want to copy or fork it will be required to keep the attributions.&nbsp;
To ensure that the attributions are correct I will start a new
documentation attributions file probably named DOC-AUTHORS which
will contain all the names of the contributors.&nbsp; For those of you
who have contributed with patches, assuming that they were committed
under your name (our current practice), I will pull all such names
from the git repository and start the file with those names.&nbsp;
Obviously, the list I present below needs to be cleaned up a bit,
which I will do before posting the new document, but for the moment,
the contributors are:<br>
<br>
Alexandre Baron &lt;balexfr at users dot sourceforge dot net&gt;<br>
Arno Lehmann &lt;arnol at users dot sourceforge dot net&gt;<br>
aussenwasser &lt;aussenwasser at users dot sourceforge dot net&gt;<br>
Bastian Friedrich &lt;bastian dot friedrich at collax dot com&gt;<br>
Bruno Friedmann &lt;bruno at ioda-net dot ch&gt;<br>
Christopher S dot&nbsp; Hull &lt;csh at raidersolutions dot com&gt;<br>
Dan Langille &lt;dan at langille dot org&gt;<br>
Davide Franco &lt;bacula-dev at dflc dot ch&gt;<br>
Davide Franco &lt;dfranco at dflc dot ch&gt;<br>
Dirk H Bartley &lt;dbartley at schupan dot com&gt;<br>
Eric Bollengier &lt;eric at baculasystems dot com&gt;<br>
Eric Bollengier &lt;eric at eb dot homelinux dot org&gt;<br>
Eric Bollengier &lt;eric at zogi dot (none)&gt;<br>
Frank Sweetser &lt;fes at users dot sourceforge dot net&gt;<br>
James Harper &lt;james dot harper at bendigoit dot com dot au&gt;<br>
Jeremy C dot&nbsp; Reed &lt;jeremy-c-reed at users dot sourceforge dot
net&gt;<br>
Jose Herrera &lt;herrerajs at users dot sourceforge dot net&gt;<br>
Jose Herrera &lt;herrerajs at yahoo dot com&gt;<br>
Jo Simoens &lt;polyglot at users dot sourceforge dot net&gt;<br>
Juan Luis Francis &lt;indpnday at users dot sourceforge dot net&gt;<br>
Karl Cunningham &lt;karlec at users dot sourceforge dot net&gt;<br>
Kermorgant &lt;grizzli at users dot sourceforge dot net&gt;<br>
Kern Sibbald &lt;kern at sibbald dot com&gt;<br>
Landon Fuller &lt;landonf at opendarwin dot org&gt;<br>
Lucas Di Pentima &lt;lucas at lunix dot com dot ar&gt;<br>
Ludovic Strappazon &lt;lstrappazon at users dot sourceforge dot
net&gt;<br>
Marco van Wieringen &lt;mvw at planets dot elm dot net&gt;<br>
Meno Abels &lt;meno dot abels at adviser dot com&gt;<br>
mhallock &lt;mhallock at scs dot uiuc dot edu&gt;<br>
Nicolas Boichat &lt;nicolas at boichat dot ch&gt;<br>
Peter Buschman &lt;peterb at iotk dot com&gt;<br>
Philippe Chauvat &lt;philippe dot chauvat at baculasystems dot
com&gt;<br>
Philipp Storz &lt;Philipp dot Storz at dass-it dot de&gt;<br>
Richard Mortimer &lt;richm at oldelvet dot org dot uk&gt;<br>
Robert Nelson &lt;robertn at the-nelsons dot org&gt;<br>
Scott Barninger &lt;sbarn at scott dot localdomain&gt;<br>
Scott Barninger &lt;scott at barninger dot com&gt;<br>
Sebastien Guilbaud &lt;sebastien dot guilbaud at bull dot net&gt;<br>
Thomas Glatthor &lt;Thomas dot Glatthor at ic3s dot de&gt;<br>
Thomas Mueller &lt;thomas at chaschperli dot ch&gt;<br>
Thorsten Engel &lt;thorsten dot engel at matrix-computer dot com&gt;<br>
Victor Hugo dos Santos &lt;victorhugops at users dot sourceforge dot
net<br>
<br>
<br>
<br>
The purpose of this email is three fold:<br>
<br>
1. To solicit your feedback on this possible license change.&nbsp; For
more details see:<br>
<br>
<a class="moz-txt-link-freetext" href="https://creativecommons.org/licenses/by-sa/4.0/">https://creativecommons.org/licenses/by-sa/4.0/</a><br&gt;
<br>
and<br>
<br>
<a class="moz-txt-link-freetext" href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a><br&gt;
<br>
<br>
2. If you have contributed to the manuals but are not on the above
list and want to be on the list, please send me your name, email
address, and a rough idea of what you contributed.<br>
<br>
3. If you do not want your name on this list, please let me know,
and I will remove it.<br>
<br>
Best regards,<br>
Kern<br>
</body>
</html>

Hello,
Email problems:
A number of you have complained that you could not get a
confirmation when signing up for the bugs database. I thought
this was due to the tight measures we have taken to avoid spam.
However, it was due to an overzealous and incorrect application
of some postfix rules that caused all emails sent by bacula.org
except to its relay sites (which includes me) to be totally blocked.
This is now corrected, and so any new subscriptions should work
fine. In addition, if you previously subscribed, it probably succeeded,
but you simply were unable to get the response.
I regret the inconvenience that this caused.
New website:
Since I am writing to you, I would like to mention that we are working
on a new website design that is more modern, allows blogging,
user feedback, rss feeds, and all such current website features.
The work is scheduled to be complete in the March-April time frame
to coincide with the next release. It will also include a new logo. If
you are interested to see the work in progress, simply visit:
blog.bacula.org
The final result will be significantly different from the current skeleton.
Best regards,
Kern

Hello,
First, I would like to thank all of you who have both on and off the
Bacula lists sent me very kind emails thanking me and encouraging me
in the Bareos affair.
The main purposes of this email are:
1. Bareos
2. Bacula
3. The Bacula Conference
1. Bareos:
The main purpose of this email is not to discuss Bareos, but rather to tell
you where we are with the Bacula project, and assure you that everything is
going quite well. I have written a number of blogs about the Bareos
fork with
two or three more to come in the next few weeks at:
http://blog.bacula.org
So if that subject interests you, that is the place to go for information.
2. Bacula:
I know that some of you are worried about the Bacula project and where
it is going. I want to assure that everything is OK, and that we have
quite a number of exciting new features and many other benefits for
the community coming up. They have been long planned (well before Bareos)
and are just now coming to fruition.
Shortly after the last Bacula release in February 2013 (Bacula version
5.2.13), I learned about the Bareos fork. Out of precaution, I froze the
Bacula community version. With all that you may have heard, you may
wonder if
I have something against forks. Though I consider most forks unnecessary
and a duplication of effort, I am not at all against forks, and in fact
since
2010 (or even earlier) there are several forks of Bacula, all of which have
their place. This is not the case with Bareos, because I believe that
removing author accreditations and taking and distributing proprietary
software
without approval is not acceptable, and even more so in the open
source world. In addition, beginning a fork with an aggressive and abusive
smear campaign against Bacula, Bacula Systems, and myself, only serves
to damage the image of a lot of dedicated people.
On the very positive side of Bacula, the Bareos issues are now clearly
on the
table, so there is no reason to continue with the Bacula code freeze. Of
course during the freeze, work on Bacula continued so that everything that
would have been in any interim release plus more will be in the next version
which is scheduled for late March of April of this year.
As has historically been the case, in addition to a few recent community
contributions, there will be some significant contributions from Bacula
Systems to the next Bacula version. Since the Bareos propaganda has
been, to
say the least, extremely misleading concerning past Bacula Systems
contributions to the community, please see the following link for the "true"
list of contributions to the Bacula project which is easy for anyone to
validate:
http://blog.bacula.org/review-of-major-contributions-to-bacula-since-2008/
The list of flowback contributions to the community from Bacula Systems for
the next version (March-April) now has twenty three new features, plus a new
product, and that number is growing almost daily so will be even bigger
by the
time the release is made. I plan to make the official announcement of these
features at the Bacula Conference in Berlin on 21 March 2014.
We also already have a list of four additional major Bacula Enterprise
features that will flow back in to a subsequent Bacula community version
to be
released toward the end of the year.
3. The Bacula Conference
As I mentioned above, the first International Bacula Users and Partners
Conference (http://www.baculaconference.org/) will be held in Berlin on
the 21st of March 2014. If you have not registered for this Conference,
please do so as seats are filling quickly. Entrance is free. You can
register
at the following link:
http://www.baculaconference.org/register/
During the Conference, I will present Bacula roadmap and make some
important announcements for our community. If you want to meet me, other
developers and contributors to Bacula as well as hear about Bacula Systems,
this is the place to go.
I am excited about the meeting and will be delighted to meet you in Berlin,
Germany on the 21st of March and have the opportunity to have a chat
with each
and everyone. Also, there will be a dinner on the 20th the eve of the
conference, offered by Bacula Systems, so don't forget to reserve your seat
when you register for the Conference day.
Looking forward to seeing you in Berlin,
Kern Sibbald