All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Yocto usability questions
Date: Tue, 22 Nov 2011 09:23:07 -0600	[thread overview]
Message-ID: <1321975387.2321.25.camel@elmorro> (raw)
In-Reply-To: <4ECB9B23.5060305@ts.fujitsu.com>

Hi Rainer,

On Tue, 2011-11-22 at 04:52 -0800, Rainer Koenig wrote:
> Hi Tom,
> 
> On 18.11.2011 21:54, Tom Zanussi wrote:
> 
> > I'd be happy to work with anyone who wants to in helping getting
> > something like that started, whether it be a variation on the above, or
> > something from scratch, whatever.
> 
> I just added a few FAQ entries to the wiki. I used the questions from
> Chris Tapp and what came to my mind recently. And I used categories, so
> that there is a hope for a sort of workflow. See
> 
> https://wiki.yoctoproject.org/wiki/Category:FAQ
> 
> for details.
> 

I really like this arrangement for the FAQs - it makes it much easier to
find relevant questions (even better if it were eventually categorized
even further e.g. by topic), and more importantly much easier to find
the questions that still need to be answered. ;-)

> > In any case, it would be nice to have some concrete ideas on what would
> > make for a good walked-through example or set of examples...
> 
> Actually I'm still thinking if the wiki approach is helpful or if
> someone (maybe even me) should write a book. ;-)
> 

To me, the wiki does make a lot sense for FAQs at least.  For other
things like examples or walk-throughs or longer articles on specific
topics, I kind of informally think of the wiki as a staging area for
stuff that could eventually go into one of the official Yocto manuals,
most likely the Development Manual, which seems to want to become the
kind of book you're thinking about, and this has already happened in a
couple cases.

If you're thinking more along the lines of something like an O'Reilly
book on Yocto, though, I'm guessing you could probably also find
volunteers for that too here.  ;-)

Tom

> Regards
> Rainer
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto




  reply	other threads:[~2011-11-22 15:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 22:07 Yocto usability questions Jeff Osier-Mixon
2011-11-16 23:39 ` Mark Hatle
2011-11-17  4:03   ` Ourada, Paul
2011-11-17  7:19 ` Koen Kooi
2011-11-17 13:06 ` Rainer Koenig
2011-11-17 14:25   ` Philip Balister
2011-11-17 21:38 ` Chris Tapp
2011-11-17 22:17   ` Brian Duffy
2011-11-17 23:19     ` Osier-mixon, Jeffrey
2011-11-18  9:40   ` Jack Mitchell
2011-11-18 15:02     ` Ourada, Paul
2011-11-18 15:42       ` Philip Balister
2011-11-18 15:56       ` Gary Thomas
2011-11-18 16:00         ` Philip Balister
2011-11-18 16:04           ` Gary Thomas
2011-11-18 16:56             ` Tom Rini
2011-11-18 16:56             ` Jack Mitchell
2011-11-18 17:20       ` Osier-mixon, Jeffrey
2011-11-18 19:40         ` Jeff Osier-Mixon
2011-11-18 20:12     ` Joshua Lock
2011-11-18 20:54       ` Tom Zanussi
2011-11-18 21:31         ` Osier-mixon, Jeffrey
2011-11-18 21:56           ` Chris Tapp
2011-11-18 22:32           ` Philip Balister
2011-11-18 22:36             ` Osier-mixon, Jeffrey
2011-11-22 12:52         ` Rainer Koenig
2011-11-22 15:23           ` Tom Zanussi [this message]
2011-11-22 16:49           ` Joshua Lock
2011-11-22 21:03             ` Chris Tapp
2011-11-22 22:52               ` Joshua Lock
  -- strict thread matches above, loose matches on Subject: below --
2018-12-21  5:16 Prasenjit Mahanti

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=1321975387.2321.25.camel@elmorro \
    --to=tom.zanussi@intel.com \
    --cc=Rainer.Koenig@ts.fujitsu.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.