public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Aw: Re: IPFire Wiki Workflow
Date: Fri, 19 Jul 2013 14:46:06 +0200	[thread overview]
Message-ID: <1374237966.11196.9.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <1373732424.1724.12.camel@rice-oxley.tremer.info>

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

Any reason why this discussion has ended without a result?

Are there any suggestions/opinions about the proposed workflow? Can't
believe that there is nothing to talk about...

-Michael

On Sat, 2013-07-13 at 18:20 +0200, Michael Tremer wrote:
> On Fri, 2013-07-12 at 17:55 +0100, Aaron Philpott wrote:
> > I figure now is the point that I should input somewhat into Michael's
> > thoughts on the Wiki and documentation.
> > 
> > 
> > For those of you who don't me, I'm Aaron (AzzyChill) online and have
> > created one video on IPFire with the plan to develop more in future.
> > I am relatively new to the IPFire project having only really used
> > Untangle for my corporate clients due to its ease of use for both me
> > as an IT support person and my clients as end users of the system I
> > install.
> 
> Welcome :)
> 
> > I mentioned recently in my regular Brew Time segments that IPFire is
> > an amazing project but the support available isn't as good as it could
> > be and so it could put a lot of people off, both seasoned IT
> > professionals and noobs who are going into IT pretty clueless as to
> > what they're doing.
> 
> What made me realize that we have to do more about documentation and
> these things was seeing you being confused about how to install IPFire.
> It's not that you don't have the general knowledge about how to do
> things, but of course you don't have a clue *where* to start when you
> install IPFire for the first time.
> 
> Being not too noob-friendly is okay and to some extend I think we should
> not be too noob-friendly because firewalls are not for noobs.
> But lacking essential information for all other people who start with
> IPFire is not okay.
> 
> > I pretty much agree with everything that Michael has said including
> > the bits about language.  I am from the UK and hence English is my
> > native language, due to failings in the education system of the UK it
> > is also my only language.  One would assume that most residents of
> > Germany speak English as well and so starting from English probably
> > isn't a bad idea.  But language links in with the end plan and the
> > future for IPFire because currently the majority of your users are
> > based in Germany and speak German and so it would make sense to write
> > everything in German and then translate it to other languages.  But if
> > the plan is to try and expand the project to other markets
> > internationally English would be the best language to use because it
> > is an international language.
> 
> That's exactly the point and I don't understand all the fuzz about the
> language. People in America and the UK speak English. Nothing else.
> All the rest of Europe and the Americas and parts of Asia are used to
> communicate in English (at least reading).
> All other Open Source projects are in English. There is not a single
> major project I know that is not running in English.
> 
> And English is also the language for development in the IPFire project.
> We use it in Bugzilla, we use it on our mailing lists, we use it
> everywhere. The majority of the people who use IPFire is not from
> Germany, so there is absolutely no point in choosing any other language
> than English.
> 
> -Michael
> 
> 
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation


  parent reply	other threads:[~2013-07-19 12:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKTTqHOz9S5JQ__HT8eJTRozqn9Q_kmy_=124Yn5E=160cTdng@mail.gmail.com>
2013-07-13 16:20 ` Michael Tremer
2013-07-14 20:00   ` Aw: " Bernhard Bitsch
2013-07-15 11:54     ` Michael Tremer
2013-07-19 12:46   ` Michael Tremer [this message]
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=1374237966.11196.9.camel@rice-oxley.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