From: William Mills <wmills@ti.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: "Abbas, Mohamed" <mohamed.abbas@intel.com>,
Yocto Project <yocto@yoctoproject.org>,
Darren Hart <dvhart@linux.intel.com>,
"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
"Purdie, Richard" <richard.purdie@intel.com>
Subject: Re: Yocto Project Quick Start Feedback
Date: Fri, 24 Feb 2012 14:06:53 -0500 [thread overview]
Message-ID: <4F47DFCD.90103@ti.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB12379374D02D4@ORSMSX102.amr.corp.intel.com>
On 02/24/2012 01:05 PM, Rifenbark, Scott M wrote:
> The "movie" angle is interesting. Picture this... the opening 1/2 page sets up the packages for Ubuntu, downloads files, builds core-image-sata, and runs qemu. All this done without even telling anyone what YP is. Follow that by "what just happened... we just built and ran an image using the Yocto Project. Then the QS launches into the "Welcome" stuff and flows on as normal. That would be a unique beginning for a technical manual.
I sense some derision in your word "unique"? Thats fine, your doing
most of the work and you have to be happy with it.
However I don't think it is unique. Yes it would be a bad approuch to
use in a reference manual but I have found a number of intros/tutorials
start this way and I always enjoy the approuch. Perhaps the QS at only
9 printed pages is too short to be structured this way. The QS guide
itself is just this "taste of the bigger picture" for the full doc set.
As I said, just some thoughts.
Bill
next prev parent reply other threads:[~2012-02-24 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 0:40 Yocto Project Quick Start Feedback Darren Hart
2012-02-24 15:43 ` Rifenbark, Scott M
2012-02-24 17:44 ` James Abernathy
2012-02-24 17:47 ` William Mills
2012-02-24 18:05 ` Rifenbark, Scott M
2012-02-24 19:06 ` William Mills [this message]
2012-02-24 22:19 ` Rifenbark, Scott M
2012-02-27 12:01 ` Barros Pena, Belen
2012-02-27 15:00 ` Rifenbark, Scott M
2012-02-27 15:22 ` Barros Pena, Belen
2012-02-27 15:27 ` Rifenbark, Scott M
2012-02-27 18:00 ` Osier-mixon, Jeffrey
2012-02-27 18:07 ` Rifenbark, Scott M
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=4F47DFCD.90103@ti.com \
--to=wmills@ti.com \
--cc=dvhart@linux.intel.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=mohamed.abbas@intel.com \
--cc=richard.purdie@intel.com \
--cc=scott.m.rifenbark@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.