Collaborative SXW work process, part I [was: Re: [Typo3-documentation] Wiki or SXW]

[Karsten Dambekalns]

Hi,

On 2004-06-19, Jean-Marie Schweizer <jms at marktauftritte.ch> wrote:
> 1. Everything available right now is in SXW
> 2. We do have to deliver the SXW format at some point since there are 
> people who want to download a manual and print it out. Also, we need a 
> transition time where compatibility is important.
 ...
> We might have to settle for a compromise during a transition period if 
> some writers prefer to write with Open Office instead of Wiki.
>
> Maybe we can convert SXW to Wiki? What do you think Sebastian?

Although I'm not in the doc group, and I won't have time for it until
the end of the year (that's for sure), here are my two cents on the
SXW vs. Wiki debate.

I understand you want to have a wiki in place so that everyone can
work on the thing together. But as I see it, it is more realistic if
a writer (or a small group) focuses on a specific part (or chapter).

This is a similar concept to the one used when the current Blender
manual was written (though it was written in Docbook and managed in
CVS during writing).

So I think there may be two ways to solve this 'dilemma' (if it is
one, in fact):

1. Use OpenOffice, but don't write one big document. Instead everyone
writes his chapter and the 'whole manual' is put together by means of
a master document binding the parts together.

If done this way, it is very likely that the tools OpenOffice provides
for collaborative work on a document are sufficient to allow mergin of
changes when a small group is working on a chapter.

2. Use OpenOffice, but set up a structure that allows to sync the
local working copy of the document with a CVS repository. This might
consist of an upload form where I can upload my changed document, it
gets unpacked and checked in to CVS. Afterwards I get an updated
document for download.


Since 2. might involve quite some difficulties (what happens to
conflicts during the process, there would be noone watching...), it
might be worth looking at 1. in more detail to see if it might be way
to go.


Hope this helps, and thanks for at least wanting to work on this!

Karsten