Re: IPFire Wiki Workflow

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 3338 bytes --]

Hello,

one very important note, which apparently didn't come across:

My intention was, that there is only one "instance" of the workflow
running at the same time and not an extra iteration per page.

If you do an different things at different times, it will get hard to
keep track about what is currently done. That doesn't make any sense to
me.


On Wed, 2013-07-31 at 20:51 +0200, Erik K. wrote:
> > 
> >> - In point (B) shouldn´t be not also the german translations in there as a point (2) ?
> > 
> > No,  the idea is to write the content in English first. And after that
> > has been finished and been reviewed (C), we start translating.
> > 
> > I guess the translation teams will organize themselves in a way they
> > like. They are usually much smaller and do not need a lot of
> > coordination.
> > 
> > The workflow implies one very import thing: English first.
> > No content is ever created first in any other language than English.
> > After it has been reviewed, we start translations into second languages.
> 
> I think also, for the first the docu team is very small and for sure as time goes by, there will be a good way how to do it. So should the workflow be adjusted in point (D) with the german translation ? I think it is a good idea if we bring on the german translation also as a fix point, otherwise we can run in a reversed situation to now that the english parts will grow and the german part will hobbles afterwards. Or do we abolish the german wiki ?

As the very last note on languages: Writing documentation does not need
to care about other languages (!= English). So details about the
translation process do not need to be included in the documentation
workflow.

Translations come AFTER content has been written. That's the only
relation between writing documentation and translating documentation.

We do not drop the German wiki at any point if there are enough people
to contribute to it. That's the same with other languages. If someone
wants to do it, that's fine and we will support that.

> 
> > 
> >> - The testing of the written articles should be mentioned i think, cause it is not enough to understand what this software should do, the software needs to be tested in every single function so a quality management will be done too.
> > 
> > This should be part of the review.
> 
> O.K. so part (C), should we adjust it in the workflow ?

Please add that note to the explanation below.

> >> A question: Should i start as a coordinator to list some important topics ? Or do we need a little longer ?
> > 
> > This list should be open (as basically everything). I suppose it's best
> > to create an extra wiki page for that and write down what needs to be
> > done. In addition to that we should set a priority and write down notes
> > about what particularly needs to be improved on an article.
> 
> Something like this --> http://wiki.ipfire.org/de/todo ? Please extend if you have some ideas.

This is in the wrong language are, obviously.

In general, there should be two kinds of lists:
1) A list of which articles is currently worked on.
2) A list of items that is to be scheduled for next iteration.

Again: Don't care about German at this point. Don't add percentages,
because how do you calculate these?

Michael