From: "Erik K." <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: New OpenVPN Wiki
Date: Sun, 02 Dec 2012 10:21:03 +0100 [thread overview]
Message-ID: <A48D5832-15CD-499A-A31A-9811064F7966@ipfire.org> (raw)
In-Reply-To: <32303FE9-D463-4E6B-BDB9-351BBE2B6871@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2080 bytes --]
Hi all,
now the english part is also done. For the first in the non public section, but it will comes, if the first overviews are done, i think today/hope into the official section. The relocation of this wiki to official section should be done in 5 Minutes.
So you can find it here --> http://wiki.ipfire.org/nonpublic#openvpn_auf_ipfire_konfigurieren . I used the same structure for english than before for the german, only difference is an :en: in the URL. So there are also new screenshoots in both wikis i improved also the content not only by explaining the new features also by filling in some corrections and additionals.
It might be very helpful if you can go also for corrections in design, grammar or whatever you will find. Please let it me know if you have ideas or critics.
Greetings and a nice first advent for you all.
Erik
Am 30.11.2012 um 19:23 schrieb Erik K.:
> I forgot to link you to the news. In here --> http://planet.ipfire.org/post/core-update-65-goes-into-testing-stage-exciting-new-features you can find the new additionals.
>
> Erik
>
> Am 30.11.2012 um 18:41 schrieb Erik K.:
>
>> Hi all,
>> i want to inform you that i have renewed the OpenVPN wiki causing the actual development and a lot of new additionals. So i needed to renew also the design otherwise the scroll wheel becomes edgy ;-) .
>> So at this time only the german wiki exists, the english one will follow tomorrow i think .
>>
>> So please could you go for corrections and additionals, which might be very nice.
>>
>> The new wiki sections can be found in here --> http://wiki.ipfire.org/de/configuration/services/openvpn/config
>>
>> Thanks and best 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 parent reply other threads:[~2012-12-02 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32303FE9-D463-4E6B-BDB9-351BBE2B6871@ipfire.org>
2012-12-02 9:21 ` Erik K. [this message]
2012-12-02 15:37 ` Erik K.
[not found] <mailman.1.1354446001.8493.documentation@lists.ipfire.org>
2012-12-03 1:28 ` R. W. Rodolico
2012-12-03 7:41 ` Erik K.
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=A48D5832-15CD-499A-A31A-9811064F7966@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