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: DNS Forwarding + Wireless Client + Tor [week two]
Date: Sat, 17 Aug 2013 12:41:23 +0200	[thread overview]
Message-ID: <1376736083.18941.105.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <1376328506.18941.33.camel@rice-oxley.tremer.info>

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

Hey,

almost one week has passed since we started working on these three
topics. It's a bit sad, that so few participated and worked on something
else instead.

So I think that is nothing to do on the DNS Forwarding and Wireless
Client pages and that we can pass that over to the translators.

Since, we want to release Tor very soon, we need to do the same with the
Tor documentation as well. One paragraph has not been written and if
there is no interest in doing that, I will just remove that and people
need to find the information somewhere else.

This is:
http://wiki.ipfire.org/en/addons/tor/client#use_the_tor_proxy_with_your_web_browser

If somebody wants to work on that, please raise your hand. Otherwise,
this will just be removed.

Have a nice weekend!

-Michael

On Mon, 2013-08-12 at 19:28 +0200, Michael Tremer wrote:
> Hello,
> 
> On Mon, 2013-08-12 at 19:16 +0200, SCHUH Karl, SCHUH-TV wrote:
> > Hi Michael,
> > maybe it would be more important if start the translation process. If someone wanted to start a translation, he could look up the english version, if it were stable or if it was worked upon. But there can be other rules to avoid a translation of a page, which is to be changed (as it happened to me with the NDS-forward-page). :-)
> 
> I stated this several times on here, but here it is again: Writing
> documentation does not care about translation. There is nobody who can
> keep track of all languages.
> 
> As long as a page is written, reviewed and has not been approved to be
> finished, starting a translation is non-sense and must never be done.
> 
> -Michael
> 
> > 
> > Best regards,
> > Karl 
> > 
> > ----- Ursprüngliche Mail -----
> > > Well, I didn't feel that it made much sense, because if someone is
> > > actually working on a page, the wiki software will lock it, so that
> > > there won't be any conflicts.
> > > Otherwise, I didn't think that the team is big enough to divide it
> > > into
> > > several groups who each work on a page.
> > > 
> > > Why do you think do we need this?
> > > 
> > > -Michael
> > 
> 
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation


  reply	other threads:[~2013-08-17 10:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-10 13:13 Michael Tremer
2013-08-10 16:05 ` SCHUH Karl, SCHUH-TV
2013-08-12 15:55   ` Michael Tremer
2013-08-12 17:16     ` SCHUH Karl, SCHUH-TV
2013-08-12 17:28       ` Michael Tremer
2013-08-17 10:41         ` Michael Tremer [this message]
     [not found] <CAKTTqHOX5OMVSeLVwvPKAQ1sR=9xgWDKA+VJNOZrnT+nSNWTGQ@mail.gmail.com>
2013-08-17 11:00 ` Michael Tremer
2013-08-19  6:46   ` R. W. Rodolico
2013-08-19 20:13     ` Michael Tremer
2013-08-21  0:53       ` R. W. Rodolico
2013-08-21 18:34         ` 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=1376736083.18941.105.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