From: Darren Hart <dvhart@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: <rant>the current yocto FAQ is pretty much valueless</rant>
Date: Tue, 26 Jun 2012 08:46:45 -0700 [thread overview]
Message-ID: <4FE9D965.4070906@linux.intel.com> (raw)
In-Reply-To: <10398861.esnekvBoZU@helios>
On 06/26/2012 03:09 AM, Paul Eggleton wrote:
> On Tuesday 26 June 2012 05:09:34 Robert P. J. Day wrote:
>> in other words, a *good* FAQ might be:
>>
>> "how can i use the yocto prebuilt toolchains to save build time?"
>>
>> a *bad* FAQ would be:
>>
>> "Does the Yocto Project have a special governance model, or is it
>> managed as an open source project?"
>>
>> the kicker is that that last question is, in fact, in the yocto FAQ,
>> along with a number of other questions that have never been asked by
>> anyone in the history of the planet. i chat about yocto with people
>> on a regular basis, and i can assure you, not a single one of them has
>> ever asked, "hey, rob, can you explain yocto's governance model?"
>>
>> 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*.
>
> You bring up a valid point, but I think it might be worth mentioning that the
> current FAQ evolved from a much less technically-oriented version that was
> produced when the project launched. At that time some people *were* asking the
> kind of questions that you're deriding. I think there's still a section of the
> *non-technical* audience who are interested in answers to those questions.
>
> I suggested to Scott R previously that it might be worth having a project FAQ
> (i.e., what is this project about, what is it intended to be used for etc.)
> and a separate technical FAQ which answers the kind of questions you are
> expecting and that we see often on the mailing list. I think one of the
> reasons that hasn't been done is that we're hoping to introduce a Q&A function
> on the website similar to StackOverflow, where everyone can participate but the
> most appropriate answers bubble up to the top. As yet this has not been
> implemented and I'm not sure when it will be, so it may still be worth looking
> into a static technical FAQ on the wiki until it is.
Is "technical FAQ" == "How-Do-I pages" ?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-06-26 15:48 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
2012-06-26 10:09 ` Paul Eggleton
2012-06-26 10:18 ` Robert P. J. Day
2012-06-26 15:46 ` Darren Hart [this message]
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=4FE9D965.4070906@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=paul.eggleton@linux.intel.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.