All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pat Erley <pat-lkml@erley.org>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: Holger Schurig <holgerschurig@gmail.com>,
	linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Linux wireless GSoC 2010 project ideas
Date: Thu, 04 Feb 2010 17:36:15 -0500	[thread overview]
Message-ID: <4B6B4BDF.7010303@erley.org> (raw)
In-Reply-To: <87wrytjt9d.fsf@purkki.valot.fi>

On 02/04/10 03:32, Kalle Valo wrote:
> <pat-lkml@erley.org> writes:
> 
>>> Would you document this on the wireless WIKI at 
>>> wireless.kernel.org ?
>>>
>>> Maybe as different articles, so that this can be a basis of 
>>> several "HOWTO" articles.
>>
>> Yeah, I will try to find the time soon.  Any hints as to what needs to be 
>> documented?  It is, at least in my opinion, pretty trivial to pull off, so
>> I'm not certain that anything more than an entry explaining how to create
>> additional interfaces is necessary.  Feel free to throw some ideas as to
>> what all you'd like to see in the documentation, and I'll write it (them?)
> 
> Based on my experiences helping not-so-skilled people:
> 
> o even trivial issues need to be documented, assume that the reader
>   knows nothing
> 
> o examples are best, also try explain in detail what the example
>   actually does
> 
> o make sure examples really work and are correct :)
> 
> o pointers for more information (if there are any)
> 
> Just my 0.02 EUR.
> 
ok, I'll see what I can come up with.  It's all pretty simple, but you're 
right, there's not a lot of documentation about it out there.

Pat

  reply	other threads:[~2010-02-04 22:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 21:38 Linux wireless GSoC 2010 project ideas Luis R. Rodriguez
2010-01-28 22:06 ` Till Kamppeter
2010-01-28 22:14   ` Luis R. Rodriguez
2010-02-04  4:52   ` Hin-Tak Leung
2010-02-17 17:07   ` [lsb-discuss] " Alexey Khoroshilov
2010-01-28 23:15 ` Frederic Weisbecker
2010-01-28 23:23   ` Luis R. Rodriguez
2010-01-28 23:31     ` Greg KH
2010-01-28 23:41       ` Frederic Weisbecker
2010-01-28 23:51     ` Till Kamppeter
2010-03-09 22:43       ` Frederic Weisbecker
2010-03-12  8:12         ` Till Kamppeter
2010-03-18  3:40           ` Frederic Weisbecker
2010-03-12  8:59         ` Till Kamppeter
2010-03-12  9:38           ` [lsb-discuss] " Denis Silakov
2010-03-12  9:57             ` Till Kamppeter
2010-03-21 19:49             ` Frederic Weisbecker
2010-01-31 21:03 ` Witold Sowa
2010-01-31 21:20   ` Johannes Berg
2010-02-01 18:01     ` Luis R. Rodriguez
2010-02-01 20:14       ` Maxim Levitsky
2010-02-01 20:17         ` david
2010-02-01 21:31           ` Maxim Levitsky
2010-02-03  9:23             ` Holger Schurig
2010-02-01 22:12         ` Nick Bowler
2010-02-02  4:25           ` Pat Erley
2010-02-03  9:25             ` Holger Schurig
2010-02-03 14:24               ` pat-lkml
2010-02-03 18:48                 ` Luis R. Rodriguez
2010-02-05  5:16                   ` Pat Erley
2010-02-05 15:49                     ` Luis R. Rodriguez
2010-02-04  8:32                 ` Kalle Valo
2010-02-04 22:36                   ` Pat Erley [this message]
2010-02-22 21:25 ` Luis R. Rodriguez

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=4B6B4BDF.7010303@erley.org \
    --to=pat-lkml@erley.org \
    --cc=holgerschurig@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.