[Bf-docboard] Who's in charge? What's going on?

[Andreas Haferburg]

Hi,

still, I'm a bit confused, but I try to sum up what I understood so far.

When you say "the core guide", you mean the community doc at
http://download.blender.org/documentation/html/ , right?

This core guide is the base for the 2.3 book, which is coming soon. But (this is
not clear to me) the problem is that the core guide was developed using two
licenses(namely OC + Blender Artistic), while the 2.3 book should be published
under OC only, right?

At the moment, there are only two persons, you, Stefano, and Ton, working on the
2.3 book.

When the book is ready, it's contents go back to the site and to the CVS source
at
http://projects.blender.org/projects/docboard/ , but only as html. (xml?
whatever)

Please correct me if I'm wrong.


If it's like that, then I don't understand, why you didn't just continue using
CVS and an open development. Why the freezing? I never wrote a book, so I don't
know what publishers like or need. Has it something to do with layout?

You talk about "developing in parallel", as if there wouldn't be any other
possibility. Why is that? Why not, at some point of time, just taking the CVS
sources, doing the layout, and publishing the book (without the freezing)?

And why are there two CVS projects, one for the docs, and one for Blender itself?
Why can't a developer just change some code, and update the docs, or at least
mark the parts of the docs that have to be updated?

And why isn't the blender.org + blender3d.org source in CVS? Who maintains the
website, anyway? It seems kinda outdated. The probability for someone making an
update would be maybe higher with CVS, because there would be more people with
(easier) access.

All this seem to me kinda complicated. But then again, I'm really new to Blender,
so maybe there are good reasons for all this. I only would like to know them.

> 2 - Writing/accepting as donations other tuts
>     covering areas not covered by old NaN tuts

"Accepting" means proof-reading?

> So if you are willing to collaborate actively as it seems, let's talk of
> tuts :)

What I could do is try out the tutorials and see if I can make them work for the
latest version(2.31a, right?). Should I use DocBook and the styleguide at
http://download.blender.org/documentation/html/x20988.html ?

Sorry about all these questions, but there is not much information out there (or
I simply couldn't find it).

Best regards
Andreas


> -----Original Message-----
> From: bf-docboard-admin@blender.org
> [mailto:bf-docboard-admin@blender.org]On Behalf Of Stefano Selleri
> Sent: Monday, January 05, 2004 8:41 AM
> To: bf-docboard@blender.org
> Subject: Re: [Bf-docboard] Who's in charge? What's going on?
>
>
> Hi!
>
> It is quite sad. Blender is a complex piece of software and documenting it
> is a matching complexity task.
>
> The DocBoard recognized as necessary a 'core' guide, which is
> the one in production, which is to repalce the 2.0 guide
> and is Blender's *manual*
>
> Then there is the need for tutorials, introducing specific aspects
> of Blender
>
> Possibly more items, as a Programmer's guide or so.
>
> The 'core' guide is frozen simply because the material going into the
> 2.3 book is OC license and must go back to the site, once ready, but
> developing
> in parallel would lead to merging problems and, as you might have noticed we
> are not many here :)
>
> Furthermore I called for tutorial people nearly 1 month ago, and noone
> answered...
> We are in need of:
> 1 - Taking old MNaN Tuts and updating to new Blender
> 2 - Writing/accepting as donations other tuts
>     covering areas not covered by old NaN tuts
> 3 - Writing tuts on brand new features.
>
> So if you are willing to collaborate actively as it seems, let's talk of
> tuts :)
>
> Stefano