I thought I'd better raise my hand here. As you know I hacked away at
the Bacula documentation back in September but have been rather quiet
since (I have been rushed off my feet with consultancy, preparing
company accounts, and selling rights to a cookery book we published and
hacking on latex to RTF conversion). I would like to pick up the Bacula
documentation cleanup again but I am not sure how much time I can devote
to it; moreover I don't know that I would really classify myself as an
expert when it comes to Bacula, or to backups generally.
As I see it there are several strands to the issue of documentation. It
sounds like there will be a chapter on Bacula in Curtis Preston's
O'Reilly book, which is great but that almost certainly won't really be
enough to act as proper documentation. The current documentation is
(aside from formatting concerns) in a bit of a mess. It looks like it
has acreted material over time and it could do with a major overhaul (I
get worried when bullet lists have more than ten items, but some like
the feature lists have dozens). The could well be structured into a
number of sections (some which could stand as separate documents):
overview, getting started, day-to-day usage, configuration, installation
(as an appendix), and also quick reference material. Most of these
sections already exist in the documentation, but not in a sensible
order, and as the manual I'm looking at has over 50 chapters, the
chapters should be separated into parts.
As I say I would be happy to contribute to the documentation effort, but
I don't know that I could play a lead role. I had wondered about
writing a book myself but I don't know whether I know enough about
Bacula and I don't know whether there is the potential market to make
the reward of author royalties worth the effort involved -- just
reworking the existing documentation looks to me like a major undertaking.
Maybe what is needed is a separate documentation mailing list to gather
together the interested parties and then to draw up a strategy for the
documentation as a sub-project.
Regards
Andrew
Kern Sibbald wrote:
---------- Forwarded Message ----------
Subject: Time for a Bacula book?
Date: Saturday 07 January 2006 01:43
From: John Walker
To: Kern Sibbald <[EMAIL PROTECTED]>
One thing I've regretted over the last 10 years, is that I didn't
take time out in the height of the Speak Freely madness to write a guide for
people interested in deploying it which would probably have been picked up by
O'Reilly since many of their books cover software with far fewer downloads
than Speak Freely.
Maybe the time has come for a Bacula book.
Is there somebody in the Bacula user community, ideally an articulate person
employed by a large-scale site, who would be interested in writing a book
called, say, "Deploying Bacula"? This would be a typical O'Reilly title
which was aimed at the system administrator who wants to roll out Bacula on
their network. A substantial part of the book could be cut and pasted from
the existing HTML documentation as a reference, and additional chapters
could cover the issues in getting autochangers to work, heterogeneous site
support, and complex configurations (multiple storage nodes, encrypted
links, VPN issues, etc.)
Having an O'Reilly title is a huge step up for an OpenSource product.
There's nothing wrong with, as Mike Ford used to say, "making it happen".
===
[Mike Ford is an Autodesk founder and was our first Marketing and Sales
manager -- kes]
=================================
Hello,
Last weekend, John Walker send me the above email, and I think he is right. It
is time to do a Bacula book. This would not be a simple, short, or easy
project because: 1. writing a book is a lot of work (I have never written
one, but I have written a lot of manuals); 2. It is not at all clear that
O'Reilly or any other major publisher would accept a Bacula book as I suspect
that Bacula is relatively unknown ...
Nevertheless, I would like to find someone to undertake this project,
preferrably with the kinds of skills mentioned by John. For my part, I can
work on finding a publisher, contribute a good amount of the work and provide
authorization to use any part of the current manual. In turn, I would expect
that the person or persons who work on this would share any royalties with
the Bacula project; details to be determined ...
Comments?
Does this interest anyone?
Regards Kern
PS: If I remember correctly there is at least one "printing company" that uses
Bacula. If you could be of any help finding a publisher, please let me know.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
