From: "R. W. Rodolico" <rodo@dailydata.net>
To: documentation@lists.ipfire.org
Subject: Re: Aw: Re: IPFire Wiki Workflow
Date: Fri, 12 Jul 2013 12:58:18 -0500 [thread overview]
Message-ID: <assp.090552c1cb.51E043BA.7000704@dailydata.net> (raw)
In-Reply-To: <trinity-be1dce43-2ed9-42a4-a02f-a55adf4dba1d-1373631053193@3capp-gmx-bs19>
[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]
On 07/12/2013 07:10 AM, Bernhard Bitsch wrote:
>
>> On your note about that development has to be involved in this as well:
>> Agreed and I already talked to Arne and Stevee how we can do that in the
>> least time consuming way, because we also don't have much time and loads
>> of things to work on.
> Sorry, documentation is not an addon, but a essential part of development.
>
>> Writing articles in more than one language is an absolute no-go.
> Agreed. ;)
>
>> We will leave it at English and write down the most important things one needs
>> to know about a certain add-on or what ever.
> Most developpers are native german speakers. Why not using german?
I vote for English, and not because I am a native speaker, but for the
assumption that more people use it as a second language than German. I
speak English and (very poor) Spanish. I have Russian, Filipino, German
and Spanish native speakers I correspond with regularly because they
learned English in school.
I can't speak for other countries, but in the US, most of the
multilingual learn Spanish, French, German, Russian, Mandarin and
Japanese. However, I believe most of the multilingual in other countries
learn English as their second language, then go on to other languages
after that. I am speaking from my own experience, however, so I may be
wrong on this.
>
>> I also think that developers are not the best people to write end-user
>> documentation. It is getting to complex and not suitable for beginners
>> any way.
> Also agreed. But without a basic documentation a non-developper can't write a end user doc.
> The devs mainly know about the internals. A non-dev can only study the behaviour or ask the devs.
>
> - Bernhard
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
>
--
R. W. "Rod" Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
http://www.dailydata.net
214.827.2170
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: rodo.vcf --]
[-- Type: text/x-vcard, Size: 233 bytes --]
begin:vcard
fn:R. W. Rodolico
n:Rodolico;R. W.
org:Daily Data, Inc.
adr:;;POB 140465;Dallas;TX;75214-0465;US
email;internet:rodo@dailydata.net
title:President
tel;work:214.827.2170
url:http://www.dailydata.net
version:2.1
end:vcard
next prev parent reply other threads:[~2013-07-12 17:58 UTC|newest]
Thread overview: 14+ 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
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 [this message]
[not found] <CAKTTqHOz9S5JQ__HT8eJTRozqn9Q_kmy_=124Yn5E=160cTdng@mail.gmail.com>
2013-07-13 16:20 ` Michael Tremer
2013-07-19 12:46 ` Michael Tremer
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=assp.090552c1cb.51E043BA.7000704@dailydata.net \
--to=rodo@dailydata.net \
--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