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@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@lists.ipfire.org > http://lists.ipfire.org/mailman/listinfo/documentation _______________________________________________ Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation