Preparations for Samba 4.0 RC1
abartlet at samba.org
Mon Sep 3 16:25:42 MDT 2012
On Mon, 2012-09-03 at 20:58 +0200, Karolin Seeger wrote:
> On Thu, Aug 30, 2012 at 09:30:21PM +1000, Andrew Bartlett wrote:
> > On Thu, 2012-08-30 at 12:09 +0200, Karolin Seeger wrote:
> > We need to remove the 3/4 distinction, and the best way to do that is to
> > remove the Samba4-HOWTO (it is empty of content) and rename all the -3
> > directories back to just the base name. Then just add the binaries just
> > as if they were any other new binary.
> I agree.
> > The bigger task of making the Samba-HOWTO acknowledge the AD DC and be
> > up to date will be the more difficult thing.
> What about stopping to ship the HOWTO Collection pdf file? I do really
> appreciate the tremendous work John, Jelmer and others put into it!
> The problem is that there are several issues (broken links etc.) and a lot
> of build issues and the most important issue: It's really out of date
> meanwhile. So what about putting the HOWTO Collection on the webserver as
> it is and stop shipping it with the tarballs. The Wiki would be the up to
> date alternative then (we can add a text file with the urls and mention it
> in the release notes).
I agree. I just did a grep to see what it would take to remove
references to security=share and security=server from our docs, and
while removing them would not be too difficult, walking over the
tutorials to verify the result is a much larger task.
While the oldest stuff is in the HOWTO (because it started as a
collection of already quite old documents): the same applies to the 'By
Example' book and 'Using Samba', and between them there is presumably
many other things that are now quite out of date as well.
The wiki and the Samba4 HOWTO has shown itself to be an excellent modal
for user-owned (not just user-contributed) documentation. It gets a
little unwieldy at times (as every user fills in their system-specific
details), but it (and the automation of the provision script) is the
primary reason why most Samba 4.0 AD users find it 'just works'. Being
a wiki means it is very easy to hand the editing task back to our
community, whereas accepting patches for GIT-hosted doc-book built
documentation is much heavier-weight.
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
More information about the samba-technical