From: Hagen Paul Pfeifer <hagen@jauu.net>
To: "Niccolò Belli" <darkbasic@linuxsystems.it>
Cc: lartc@vger.kernel.org,
"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>,
Linux Networking Developer Mailing List <netdev@vger.kernel.org>
Subject: Re: [Announce] LARTC wiki available
Date: Thu, 29 Dec 2011 17:19:20 +0100 [thread overview]
Message-ID: <20111229161919.GA2948@hell> (raw)
In-Reply-To: <4EFC34E5.4040202@linuxsystems.it>
* Niccolò Belli | 2011-12-29 10:37:41 [+0100]:
>> What about
>>
>> http://www.linuxfoundation.org/collaborate/workgroups/networking/group
>
>I saw it, but I didn't like it because unregistered users cannot edit
>the wiki and even registered users need an invite. Also, it seems
>quite confusing, a traditional wiki is a better solution in my
>opinion.
Anybody knows that network stack lacks documentation - no doubt. Maybe a wiki
is an adequate concept (beside man pages and in Kernel docs). Everybody, not
restricted to kernel hackers, can edit documentation and add examples.
Maybe the netem wiki page at
http://www.linuxfoundation.org/collaborate/workgroups/networking/netem
is a good example for a good documented subsystem.
But I don't like the idea to outhouse the existing wiki. Why two wikis? What
happened with the wiki server if you leave the university? So maybe the user
restriction on linuxfoundation.org should be changed? I strongly suggest to
keep to documentation as tightly as possible to linuxfoundation (or
https://www.wiki.kernel.org/).
Hagen
next prev parent reply other threads:[~2011-12-29 16:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 15:52 [Announce] LARTC wiki available Niccolò Belli
2011-12-29 0:27 ` Hagen Paul Pfeifer
2011-12-29 9:37 ` Niccolò Belli
2011-12-29 16:19 ` Hagen Paul Pfeifer [this message]
2011-12-29 17:13 ` Niccolò Belli
2011-12-29 19:04 ` John A. Sullivan III
2012-01-02 12:48 ` Ed W
2012-01-02 13:07 ` Niccolò Belli
2012-06-01 16:42 ` Niccolò Belli
2012-06-01 19:12 ` Julien Vehent
2012-06-02 14:37 ` Andy Furniss
2012-06-02 14:43 ` Andy Furniss
2012-06-02 15:50 ` Eric Dumazet
2012-06-02 16:58 ` Andy Furniss
2012-06-03 2:36 ` Jesper Dangaard Brouer
2012-06-03 20:05 ` Philip Prindeville
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=20111229161919.GA2948@hell \
--to=hagen@jauu.net \
--cc=darkbasic@linuxsystems.it \
--cc=lartc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).