All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: <rant>the current yocto FAQ is pretty much valueless</rant>
Date: Tue, 26 Jun 2012 10:55:52 +0100	[thread overview]
Message-ID: <4FE98728.5040201@r-finger.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1206260459040.8547@oneiric>

On 26/06/12 10:09, Robert P. J. Day wrote:
> A bad Frequently Asked Questions (FAQ) sheet is one that is composed
> not of the questions people actually ask, but of the questions the
> FAQ's author wishes people would ask. Perhaps you've seen the type
> before:

Nice quote, but unfortunately based on the literal meaning the acronym
rather then insight into the function of a FAQ; asking the right
questions is far more important than finding answers ... ;-)


> "how can i use the yocto prebuilt toolchains to save build time?"

Perhaps your question is not asked frequently enough to merit inclusion
in a FAQ, or perhaps it's an a far too advanced topic for a FAQ?


>   a *bad* FAQ would be:
> 
> "Does the Yocto Project have a special governance model, or is it
> managed as an open source project?"

Just because you are not interested in the answer does not make it a
question you should think about ...


>   no, what they ask is, "hey, rob, how can i add a single package to
> an existing target?"  a question that, i should point out, is not
> answered definitively in the existing docs *anywhere*.

There are two correct answers to this: the first one is RTFM; the second
one is that if you want an explicit link to the section of the manual
that explains it to be included in the FAQ, you should write the
appropriate entry for the FAQ and contribute it instead of ranting on
the list.

Tomas


  parent reply	other threads:[~2012-06-26  9:55 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26  9:09 <rant>the current yocto FAQ is pretty much valueless</rant> Robert P. J. Day
2012-06-26  9:35 ` Jack Mitchell
2012-06-26  9:55 ` Tomas Frydrych [this message]
2012-06-26 10:09 ` Paul Eggleton
2012-06-26 10:18   ` Robert P. J. Day
2012-06-26 15:46   ` Darren Hart
2012-06-26 16:06     ` Paul Eggleton
2012-06-26 16:38       ` Tomas Frydrych
2012-06-26 16:53         ` Robert P. J. Day
2012-06-26 17:18           ` Tomas Frydrych
2012-06-26 17:59             ` Brian Duffy
2012-06-27  9:39               ` Tomas Frydrych
2012-06-26 18:52             ` Tim Bird
2012-06-27  9:09               ` Tomas Frydrych
2012-06-27 14:59                 ` Koen Kooi
2012-06-27 16:43                   ` Chris Hallinan
2012-06-27 17:27                     ` Koen Kooi
2012-06-27 20:14                   ` Tomas Frydrych
2012-06-27 21:58                     ` Koen Kooi
2012-06-28  7:44                       ` Tomas Frydrych
2012-07-01 16:23                         ` Philip Balister
2012-06-27 21:14           ` Philip Balister
2012-06-27 21:51           ` Philip Balister
2012-06-26 11:29 ` Koen Kooi
2012-06-26 14:40   ` Rifenbark, Scott M
2012-06-26 15:45     ` Robert P. J. Day
2012-06-26 15:50       ` Rifenbark, Scott M
2012-06-26 16:18       ` Paul Eggleton
2012-06-26 16:26         ` Robert P. J. Day
2012-06-26 16:33           ` Paul Eggleton
2012-06-26 16:51             ` Robert P. J. Day
2012-06-26 17:02               ` Paul Eggleton
2012-06-26 17:05                 ` Robert P. J. Day
2012-06-26 17:09                   ` Paul Eggleton
2012-06-26 17:14                     ` Robert P. J. Day
2012-06-26 17:08                 ` Rifenbark, Scott M
2012-06-26 17:12                   ` Robert P. J. Day
2012-06-27 16:42   ` Jeff Osier-Mixon

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=4FE98728.5040201@r-finger.com \
    --to=tf+lists.yocto@r-finger.com \
    --cc=yocto@yoctoproject.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.