From: Holger Schurig <holgerschurig@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: 802.11 development process - extended documentation
Date: Tue, 2 Mar 2010 11:15:10 +0100 [thread overview]
Message-ID: <201003021115.10858.holgerschurig@gmail.com> (raw)
In-Reply-To: <43e72e891002241618w10d5c45ar9303f074d0228217@mail.gmail.com>
First impression: nice idea
Second impression: too complex (entangled and slightly confusing mix)
Suggestion: make it simpler by divide & conquer, e.g. make two or more
pictures. Putting everything into one picture is too much, let people learn
little-by-little, based on concepts.
For example, make a picture with only the way of a patch towards Linus.
Patch flow in a picture should be structured, linear. Not circular.
Suggestion: make it from top-to-bottom. And not start in the middle of the
picture.
Also, put names towards below the pictures. Who knows the face of of Linville?
Only insiders. But "outsiders" (like me) have to scroll down to the text
description, then up again ... not nice.
Also, the text list below the picture starts with Linus, then comes Stephen.
It should sorted differently. As the scope of this page is about wireless
patches, everything (pic & text) should start at John W.
--
http://www.holgerschurig.de
prev parent reply other threads:[~2010-03-02 8:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 0:18 802.11 development process - extended documentation Luis R. Rodriguez
2010-02-25 0:34 ` Benoit PAPILLAULT
2010-02-25 0:43 ` Luis R. Rodriguez
2010-02-25 1:05 ` Luis R. Rodriguez
2010-02-25 2:34 ` Benoit PAPILLAULT
2010-02-25 2:37 ` Stephen Hemminger
2010-02-25 5:11 ` Luis R. Rodriguez
2010-02-25 4:53 ` Jaswinder Singh Rajput
2010-02-25 5:19 ` Luis R. Rodriguez
2010-02-25 7:11 ` Willy Tarreau
2010-03-01 19:57 ` John W. Linville
2010-03-01 23:37 ` Nick Kossifidis
2010-03-02 10:15 ` Holger Schurig [this message]
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=201003021115.10858.holgerschurig@gmail.com \
--to=holgerschurig@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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).