From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bill Traynor <btraynor@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
"Rifenbark, Scott M" <scott.m.rifenbark@intel.com>,
"webhob@yoctoproject.org" <webhob@yoctoproject.org>
Subject: Re: [Webhob] Web Hob documentation?
Date: Thu, 13 Jun 2013 12:37:52 +0100 [thread overview]
Message-ID: <1371123472.20823.50.camel@ted> (raw)
In-Reply-To: <CAN20qYopuBuw_CRZy6aEN++wPNLgO1B2sbW73xaPeVBg3qpyNA@mail.gmail.com>
On Thu, 2013-06-13 at 07:23 -0400, Bill Traynor wrote:
> On Thu, Jun 13, 2013 at 6:59 AM, Barros Pena, Belen
> <belen.barros.pena@intel.com> wrote:
> I am not even sure if need to produce Web Hob documentation
> for the 1.5
> release, but I thought I'd bring it up just in case. Maybe
> something
> lightweight, like the Hob manual page on the website, might be
> enough.
>
> Let me know what you think.
>
> Is Webhob to be a part of BitBake proper? I see that Webhob patches
> are hitting the bitbake-devel list. If the answer is yes, that Webhob
> is to be a part of BitBake and it's source code live within the
> BitBake source tree, then my feeling is that it's documentation should
> be part of the BitBake manual.
I think the answer is "it depends". I think for 1.5 we will need some
basic information about the fact the UI exists, how to start it, what
the capabilities are, the limitations and some indication of future
plans (high level). This would probably be fine in the YP manuals and/or
on the wiki. If we do add any developer oriented docs such as how to
extend/customise it, those would probably be best in the bitbake manual.
Cheers,
Richard
next prev parent reply other threads:[~2013-06-13 11:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 10:59 [Webhob] Web Hob documentation? Barros Pena, Belen
2013-06-13 11:23 ` Bill Traynor
2013-06-13 11:37 ` Richard Purdie [this message]
2013-06-13 12:11 ` Rifenbark, Scott M
2013-06-13 13:28 ` Barros Pena, Belen
2013-06-13 13:44 ` Bill Traynor
2013-06-13 13:55 ` Rifenbark, Scott M
2013-06-13 14:06 ` Barros Pena, Belen
2013-06-13 14:07 ` Rifenbark, Scott M
2013-06-13 14:12 ` Barros Pena, Belen
2013-06-17 6:18 ` Rifenbark, Scott M
2013-07-01 11:24 ` Barros Pena, Belen
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=1371123472.20823.50.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=btraynor@gmail.com \
--cc=paul.eggleton@linux.intel.com \
--cc=scott.m.rifenbark@intel.com \
--cc=webhob@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.