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: Wed, 27 Jun 2012 10:39:40 +0100 [thread overview]
Message-ID: <4FEAD4DC.40007@r-finger.com> (raw)
In-Reply-To: <CAHrDPkq+vBMoQfsTy9nGz1WMS3QE+bmbf1q7o=DFpW2oH3w6qQ@mail.gmail.com>
Hi,
On 26/06/12 18:59, Brian Duffy wrote:
> No, an FAQ should not get you the expertise to create a commercial grade
> product. Reading the documentation should though. You don't want users to
> have to study source code.
If you were paying for the tools, then that would be a reasonable
expectation, but you are not. It is entirely fair to point out that the
documentation is lacking; it is not at all fair to expect that someone
will fix it for you at their own expense. If you are working on a
commercial product, you can, of course, pay someone to improve the
documentation (and even contribute it back to the project).
Also, I think in the Poky context it is better to talk about developers
rather than users; to build a commercial product, your team will need to
have a pretty solid grasp of every aspect of a Linux system.
Tomas
next prev parent reply other threads:[~2012-06-27 9:39 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
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 [this message]
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=4FEAD4DC.40007@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.