public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: "R. W. Rodolico" <rodo@dailydata.net>
To: documentation@lists.ipfire.org
Subject: Re: DNS Forwarding + Wireless Client + Tor [week two]
Date: Mon, 19 Aug 2013 01:46:39 -0500	[thread overview]
Message-ID: <assp.0943b5b98b.5211BF4F.30108@dailydata.net> (raw)
In-Reply-To: <1376737205.18941.107.camel@rice-oxley.tremer.info>

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

Michael,

Just like Aaron, this is a horrible time for me. We are having some
really bad issues here. However, after I build out a couple of
workstations, I should be in a holding pattern until some new hardware
comes in.

I've blocked off some time Tuesday afternoon (GMT-6) as "IPFire Work."
What can I do? I'll need to build out a test router, but that should not
take too long.

Looked at your document. It looks pretty good.

In the line "Be aware, that this is not a HTTP proxy" it should be "Be
aware, that this is not an HTTP proxy" (substitute An for A) to be
grammatically correct. I doubt anyone would notice, however, and the
statement is perfectly readable as is.

Question though. You state that this is "not a HTTP proxy", but if I
understood correctly, it is an IP proxy, so it will work over any
protocol using IP (such as HTTP, HTTPS?). I think the statement needs a
little clarification as to what the impact is.

Anyway, I know very little about Tor, but like I said, just tell me what
to do and, unless something else breaks, I'll spend time on it Tuesday.
Hope that is soon enough. I MAY also have some additional time the rest
of the week; depends on when the new hardware arrives.

Rod

On 08/17/2013 06:00 AM, Michael Tremer wrote:
> Hey,
> 
> I know that you are working very much and I am sure the other do as
> well. That has to be priority, for sure.
> 
> I would be very happy if you could just go through the texts and check
> for bad grammar and such. It should not be too terrible.
> 
> -Michael
> 
> On Sat, 2013-08-17 at 11:57 +0100, Aaron Philpott wrote:
>> Hey Michael 
>>
>> That's a shame. I'd put my hand up but I'm busy with work at the
>> moment (working 50 hours this week) and then the same next week. 
>>
>> I also have to admit I'm not very familiar with Tor having never used
>> it but I'm happy to help if you need me. 
>>
>>
>>
>> Aaron 
>>
>> On 17 Aug 2013 11:41, "Michael Tremer" <michael.tremer(a)ipfire.org>
>> wrote:
>>         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
>>         
>>         _______________________________________________
>>         Documentation mailing list
>>         Documentation(a)lists.ipfire.org
>>         http://lists.ipfire.org/mailman/listinfo/documentation
> 
> _______________________________________________
> 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: 245 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


  reply	other threads:[~2013-08-19  6:46 UTC|newest]

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

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.0943b5b98b.5211BF4F.30108@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