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

[Peter Kindström]

> 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.

We are always interested in hearing other peoples opinion!


> 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).

Maybe you dont know, but there is a wiki up and running already:
   http://wiki.typo3.org/


> 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.

Working this way demands someone to organise the work, I think - 
and we dont have that right now. But if we were more writers (we 
are two active ones right now) and had an organisation, this 
could be a way with some documents.


> 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.

This way its easier to share your work, which I think is more 
difficult in the first suggestion. But it seems there are other 
drawbacks instead...


IMHO the wiki is the best way to create new documentation 
_right_now_. There are more benefits than problems:

  +++ Anyone can help writing anywhere in a document
  ++  Everybody can immediately see the progress
  +   If a writer quits, all his work is still avaliable
  +   You can work from anywhere

  - Everybody can delete text (but old versions are kept?)
  - Are the wiki backed up?
  - Transferring to static documents (SXW)


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

Thanks for pointing out those alternatives. Maybe we wont use 
them right now, but who know later on... If people start joining 
the documentation team, I am sure some people find your 
suggestions better than using the wiki!


/Peter Kindström