From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Aw: IPFire Wiki Workflow
Date: Thu, 11 Jul 2013 00:24:48 +0200 [thread overview]
Message-ID: <1373495088.10320.31.camel@hughes.tremer.info> (raw)
In-Reply-To: <trinity-76fde065-6681-4398-ba7a-165a77406519-1373490162030@3capp-gmx-bs35>
[-- Attachment #1: Type: text/plain, Size: 2535 bytes --]
On Wed, 2013-07-10 at 23:02 +0200, Bernhard Bitsch wrote:
> At the moment the Wiki is in many places just a collection of articles someone thought of it would be interesting for the community.
> This results in a lack of completeness and actuality.
>
> Therefore your suggestion about a step by step revision of the chapters is good way to achieve higher quality.
I was not only aiming at rewriting one section after an other, but
rather building a workflow where all people have got a certain task and
produce some sophisticated output.
Again, not everything on the wiki is bad.
> Let me add my favourite suggestion: An article should be written by a native speaker, or the "final" version must be corrected and revised by such a team member.
We don't have enough native speakers for all the languages at the
moment. It's one of the problems we have to fix in the beginning.
As a lot of the work on the wiki is translating texts from one language
into an other, most of the team members need to speak more than one
language.
> The main reason is, usually the most exact description of a fact can be done in the language you have the most experience, the mother language. This is an experience from many years of work in software development.
> This means that an article written by someone with knowledge of a topic originates in her/his native language. And should be translated by the translation team. I realise, that this results in scattered Wiki in the first phase. But for clearness we should dare this.
We are all very (maybe most) eloquent in our mother language, but we
also need a common denominator which is English. In our current
situation we don't have any experts who speak for example French.
Therefore nobody is writing original documentation in French. But we do
have people who are able to translate content from English to French and
that helps us to provide documentation to people who only speak French.
I would suggest to make a simple rule, which has to be strictly
followed. It would solve the problem that the different translations are
drifting apart: Every change has to be done in English first. No matter
if it is just adding a tiny piece of information or writing an entire
new page.
By doing that, the translators always have a valid and up to date
reference which is English, which most people speak as a second
language.
> I hope, I was successful in expressing my thoughts in English. ;)
Yes, you were. See? It's already working.
-Michael
next prev parent reply other threads:[~2013-07-10 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 9:46 Michael Tremer
2013-07-10 21:02 ` Aw: " Bernhard Bitsch
2013-07-10 22:24 ` Michael Tremer [this message]
2013-07-11 7:28 ` R. W. Rodolico
2013-07-11 10:01 ` Michael Tremer
2013-07-11 16:18 ` R. W. Rodolico
2013-07-11 17:30 ` Erik K.
2013-07-11 17:54 ` Erik K.
2013-07-11 22:01 ` Michael Tremer
2013-07-12 12:10 ` Aw: " Bernhard Bitsch
2013-07-12 15:02 ` Michael Tremer
2013-07-12 17:58 ` R. W. Rodolico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1373495088.10320.31.camel@hughes.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=documentation@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox