Hey,
so, this is the first try to get things down by the rules of the new wiki workflow [1].
As far as I can see you guys have been working on the DNS forwarding docs and wireless client docs. I would also like to add the documentation about the new Tor addon, which will be released to testers very shortly.
All three of those are pretty advanced as far as I can see, so that we can skip the first week of the schedule where we write things from scratch. This is already done.
Let's directly move on to week number two, were we review what has been done. What I want you to do now is to check if there is everything on the pages you definitely need to know. Is a novice user able to set up the add-on with the information that is provided on the pages? Set up a clean installation of IPFire and work through the guide step by step and check if it works. If so, great! If not, please add the required information and leaves us a note.
If you have some bigger chances, please discuss them with the other guys first. Please only use the lists for discussions that nobody is left out.
It would be great if the native speakers could check the spelling and grammar.
Getting all three guides done until the end of the week would make me really happy.
If you have some spare time, please have a look at the new TODO list I set up in the international area of the wiki [5]. There is a section where you can add pages that need to be improved. There is also one entry by me. This is the list of features we will work on in the next week.
We also don't care about the translation of these pages, yet.
Now, let's start!
-Michael
P.S. The Tor add-on is not available in the testing tree, yet. You will be able to install it by the end of the weekend. So if you need that to review the Tor documentation, please be patient and start with one of the others first.
[1] http://wiki.ipfire.org/projects/docs/workflow [2] http://wiki.ipfire.org/en/configuration/network/dnsforward [3] http://wiki.ipfire.org/en/configuration/system/wlanclient [4] http://wiki.ipfire.org/en/addons/tor/start [5] http://wiki.ipfire.org/todo
Hi, I looked through all three pages and corrected a few typos and minor mistakes. I think this should be clear for novices too.
You are right, the installation page is very long. Since my holiday is ending, I do not have time to work on it at the moment :-(
Why have you dropped the column "who is currently working on this page"?
Regards, Karl
----- Ursprüngliche Mail -----
Hey,
so, this is the first try to get things down by the rules of the new wiki workflow [1].
As far as I can see you guys have been working on the DNS forwarding docs and wireless client docs. I would also like to add the documentation about the new Tor addon, which will be released to testers very shortly.
All three of those are pretty advanced as far as I can see, so that we can skip the first week of the schedule where we write things from scratch. This is already done.
Let's directly move on to week number two, were we review what has been done. What I want you to do now is to check if there is everything on the pages you definitely need to know. Is a novice user able to set up the add-on with the information that is provided on the pages? Set up a clean installation of IPFire and work through the guide step by step and check if it works. If so, great! If not, please add the required information and leaves us a note.
If you have some bigger chances, please discuss them with the other guys first. Please only use the lists for discussions that nobody is left out.
It would be great if the native speakers could check the spelling and grammar.
Getting all three guides done until the end of the week would make me really happy.
If you have some spare time, please have a look at the new TODO list I set up in the international area of the wiki [5]. There is a section where you can add pages that need to be improved. There is also one entry by me. This is the list of features we will work on in the next week.
We also don't care about the translation of these pages, yet.
Now, let's start!
-Michael
P.S. The Tor add-on is not available in the testing tree, yet. You will be able to install it by the end of the weekend. So if you need that to review the Tor documentation, please be patient and start with one of the others first.
[1] http://wiki.ipfire.org/projects/docs/workflow [2] http://wiki.ipfire.org/en/configuration/network/dnsforward [3] http://wiki.ipfire.org/en/configuration/system/wlanclient [4] http://wiki.ipfire.org/en/addons/tor/start [5] http://wiki.ipfire.org/todo
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
Hey,
this is just a quick notification saying that the Tor add-on is now available in the testing branch:
http://planet.ipfire.org/post/the-ipfire-tor-add-on-testers-wanted
On Sat, 2013-08-10 at 18:05 +0200, SCHUH Karl, SCHUH-TV wrote:
Hi, I looked through all three pages and corrected a few typos and minor mistakes. I think this should be clear for novices too.
Thanks for that!
You are right, the installation page is very long. Since my holiday is ending, I do not have time to work on it at the moment :-(
Why have you dropped the column "who is currently working on this page"?
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
Regards, Karl
----- Ursprüngliche Mail -----
Hey,
so, this is the first try to get things down by the rules of the new wiki workflow [1].
As far as I can see you guys have been working on the DNS forwarding docs and wireless client docs. I would also like to add the documentation about the new Tor addon, which will be released to testers very shortly.
All three of those are pretty advanced as far as I can see, so that we can skip the first week of the schedule where we write things from scratch. This is already done.
Let's directly move on to week number two, were we review what has been done. What I want you to do now is to check if there is everything on the pages you definitely need to know. Is a novice user able to set up the add-on with the information that is provided on the pages? Set up a clean installation of IPFire and work through the guide step by step and check if it works. If so, great! If not, please add the required information and leaves us a note.
If you have some bigger chances, please discuss them with the other guys first. Please only use the lists for discussions that nobody is left out.
It would be great if the native speakers could check the spelling and grammar.
Getting all three guides done until the end of the week would make me really happy.
If you have some spare time, please have a look at the new TODO list I set up in the international area of the wiki [5]. There is a section where you can add pages that need to be improved. There is also one entry by me. This is the list of features we will work on in the next week.
We also don't care about the translation of these pages, yet.
Now, let's start!
-Michael
P.S. The Tor add-on is not available in the testing tree, yet. You will be able to install it by the end of the weekend. So if you need that to review the Tor documentation, please be patient and start with one of the others first.
[1] http://wiki.ipfire.org/projects/docs/workflow [2] http://wiki.ipfire.org/en/configuration/network/dnsforward [3] http://wiki.ipfire.org/en/configuration/system/wlanclient [4] http://wiki.ipfire.org/en/addons/tor/start [5] http://wiki.ipfire.org/todo
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
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). :-)
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
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
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_...
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
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_...
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
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
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
Hi Rod,
On Mon, 2013-08-19 at 01:46 -0500, R. W. Rodolico wrote:
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.
If you would also look over the Tor, wireless client and DNS forwarding pages for spelling and grammar that would be great.
If you have even more time, it would be great if you could set up those things with help of the instructions given on the wiki pages. If there is something missing, please add that information.
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.
Right. You may edit those things right away :)
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.
Good that you point out these things, too!
The protocol is SOCKS, which has been used before NAT was invented. It is a simple protocol, where you connect to the SOCKS proxy and tell that proxy where to connect for you. In a very simplified way, you can think of it like HTTP CONNECT.
If you type the Tor proxy into your browser settings it's just important to type it into the SOCKS proxy setting and not as an HTTP proxy. Tor will also warn if you want to use it as a HTTP proxy.
I hope this clears it up a little bit. Feel free to add this to the wiki.
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.
Setting up Tor should be very easy and you don't need to know very much about it. I wouldn't write too much about what Tor is and stuff, because that is covered elsewhere and possibly much better than we could do it.
But we should provide at least a short impression what Tor is for, so that the users can figure out if they should look into it or if it is just not interesting for them.
-Michael
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
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
done with the Tor document. It is MUCH easier to edit than come up with something original. I added text to the Integrating with your web browser, but that was mainly based on reading online; I do not yet have this set up at my office. If someone gets a second, just look at it and make sure I didn't say something stupid.
I took you at your word and felt free to rewrite a couple of sections and/or expand on them. Hopefully, no one will have their feelings hurt; I just rewrote them in a way that made more sense to me.
I think I will have a little time tomorrow (the server is not supposed to be delivered until Thursday, I just found out). I will look at the wireless and DNS at that time.
Rod
On 08/19/2013 03:13 PM, Michael Tremer wrote:
Hi Rod,
On Mon, 2013-08-19 at 01:46 -0500, R. W. Rodolico wrote:
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.
If you would also look over the Tor, wireless client and DNS forwarding pages for spelling and grammar that would be great.
If you have even more time, it would be great if you could set up those things with help of the instructions given on the wiki pages. If there is something missing, please add that information.
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.
Right. You may edit those things right away :)
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.
Good that you point out these things, too!
The protocol is SOCKS, which has been used before NAT was invented. It is a simple protocol, where you connect to the SOCKS proxy and tell that proxy where to connect for you. In a very simplified way, you can think of it like HTTP CONNECT.
If you type the Tor proxy into your browser settings it's just important to type it into the SOCKS proxy setting and not as an HTTP proxy. Tor will also warn if you want to use it as a HTTP proxy.
I hope this clears it up a little bit. Feel free to add this to the wiki.
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.
Setting up Tor should be very easy and you don't need to know very much about it. I wouldn't write too much about what Tor is and stuff, because that is covered elsewhere and possibly much better than we could do it.
But we should provide at least a short impression what Tor is for, so that the users can figure out if they should look into it or if it is just not interesting for them.
-Michael
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
Documentation mailing list Documentation@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/documentation
Hey,
thanks for reviewing that and adding the section, that was still missing.
On Tue, 2013-08-20 at 19:53 -0500, R. W. Rodolico wrote:
done with the Tor document. It is MUCH easier to edit than come up with something original. I added text to the Integrating with your web browser, but that was mainly based on reading online; I do not yet have this set up at my office. If someone gets a second, just look at it and make sure I didn't say something stupid.
I looked through it and I think that everything is fine. You added some more information to some things I did not describe in detail in the first place.
I took you at your word and felt free to rewrite a couple of sections and/or expand on them. Hopefully, no one will have their feelings hurt; I just rewrote them in a way that made more sense to me.
I think I will have a little time tomorrow (the server is not supposed to be delivered until Thursday, I just found out). I will look at the wireless and DNS at that time.
I think that we will declare all three things as finished, now. There has been plenty of time to review that and I guess that we should move on to something new. There is a lot on our table, that needs to be done.
Thanks to all who contributed to this "iteration of the workflow".
-Michael
Rod
On 08/19/2013 03:13 PM, Michael Tremer wrote:
Hi Rod,
On Mon, 2013-08-19 at 01:46 -0500, R. W. Rodolico wrote:
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.
If you would also look over the Tor, wireless client and DNS forwarding pages for spelling and grammar that would be great.
If you have even more time, it would be great if you could set up those things with help of the instructions given on the wiki pages. If there is something missing, please add that information.
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.
Right. You may edit those things right away :)
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.
Good that you point out these things, too!
The protocol is SOCKS, which has been used before NAT was invented. It is a simple protocol, where you connect to the SOCKS proxy and tell that proxy where to connect for you. In a very simplified way, you can think of it like HTTP CONNECT.
If you type the Tor proxy into your browser settings it's just important to type it into the SOCKS proxy setting and not as an HTTP proxy. Tor will also warn if you want to use it as a HTTP proxy.
I hope this clears it up a little bit. Feel free to add this to the wiki.
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.
Setting up Tor should be very easy and you don't need to know very much about it. I wouldn't write too much about what Tor is and stuff, because that is covered elsewhere and possibly much better than we could do it.
But we should provide at least a short impression what Tor is for, so that the users can figure out if they should look into it or if it is just not interesting for them.
-Michael
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
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@lists.ipfire.org
-
Aaron Philpott -
Michael Tremer -
R. W. Rodolico -
SCHUH Karl, SCHUH-TV