From: "Erik K." <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] The new Squid Wiki is close to be finished
Date: Mon, 27 Feb 2012 16:06:59 +0100 [thread overview]
Message-ID: <93A0F6BB-A425-485A-BBC2-2F63341F16A4@ipfire.org> (raw)
In-Reply-To: <4F4B98B6.5040306@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2427 bytes --]
Hi Daniel,
thanks for the nice response. Yes if have seen your changes and i added also my value, good idea.
The english wiki is on 0 % i have made there until now nothing cause i think it is better to finish up the german one so for eventual changes i didn´t need to make them twice in the english wiki. There is a lot of text in this wiki but i think the translation goes much faster than the basic development.
The under construction notice is a good idea.
What are you think about the linking system on each site ? I think there can be a little more. It might be great if there are two links in one line like
<-- vorheriger Konfigurationsbereich nächster Konfigurationsbereich -->
but i haven´t found a way until now how i can make this. If you have any ideas feel free to change this wiki ;-)
What are you all thinking about to bring for the first the german wiki in the Public area after correction and supplements ?
Greetings
Erik
Am 27.02.2012 um 15:52 schrieb Daniel Weismüller:
> Hi Erik,
>
> very nice to read this!
> Did you see the changes which I've made here http://wiki.ipfire.org/nonpublic/de/configuration/network/proxy/example_conf?
> What the the english one? Is ready, too? If it is we may port both to the public wiki.
>
> In the section about authentication we should make an "under construction" notice.
>
> - Daniel
>
> Am 27.02.2012 15:25, schrieb Erik K.:
>> Hi all,
>> i´am close to finish the Squid wiki http://wiki.ipfire.org/nonpublic/de/configuration/network/proxy and it might be great if you all could overview it for faults or extensions. The only area which aren´t complete is the authentication http://wiki.ipfire.org/nonpublic/de/configuration/network/proxy/configuration/auth . So i only made the local authentication cause i have no experience with the rest. It might also be great if someone can finish this section.
>>
>> If this wiki was going to be corrected and checked, i will step then to the english translation.
>>
>> Greetings to all
>>
>> Erik
>> _______________________________________________
>> 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
next prev parent reply other threads:[~2012-02-27 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 14:25 Erik K.
2012-02-27 14:52 ` Daniel Weismüller
2012-02-27 15:06 ` Erik K. [this message]
2012-02-27 21:21 ` 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=93A0F6BB-A425-485A-BBC2-2F63341F16A4@ipfire.org \
--to=ummeegge@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