From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: <rant>the current yocto FAQ is pretty much valueless</rant>
Date: Tue, 26 Jun 2012 17:06:04 +0100 [thread overview]
Message-ID: <3153041.1FMPtSpq0x@helios> (raw)
In-Reply-To: <4FE9D965.4070906@linux.intel.com>
On Tuesday 26 June 2012 08:46:45 Darren Hart wrote:
> On 06/26/2012 03:09 AM, Paul Eggleton wrote:
> > 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" ?
Kind of, except most but not all FAQ questions really fit into "How do I...".
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-06-26 16:06 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
2012-06-26 16:06 ` Paul Eggleton [this message]
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=3153041.1FMPtSpq0x@helios \
--to=paul.eggleton@linux.intel.com \
--cc=dvhart@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.