From: "Stewart, David C" <david.c.stewart@intel.com>
To: Tino Breddin <tb@travelping.com>, yocto <yocto@yoctoproject.org>
Subject: Re: Future of WebHob?
Date: Tue, 8 Jan 2013 16:20:35 +0000 [thread overview]
Message-ID: <CD1184C4.1CF74%david.c.stewart@intel.com> (raw)
In-Reply-To: <50EC0433.4020206@travelping.com>
On 1/8/13 3:34 AM, "Tino Breddin" <tb@travelping.com> wrote:
>Hi,
>
>I was wondering what the future plans for WebHob are. I'm aware of the
>wiki design page [1] and the repo [2] and recall having read that it has
>been dropped from release 1.3. However I can't find any further
>information.
Hi Tino - here's the update. We decided to stop work on this version of
webHob because we were lacking some key developer input and we were not
convinced that we were taking the right approach. So what we have right
now is a prototype of this design which was functional at least at some
level (there was a demo of some functionality).
The good news is that we spent the past 6 months doing research with
stakeholders and we now have a proposed roadmap of features based on this
research. This seems to be getting healthy enough that we think we can
start a community process to refine the design and restart development.
We should see an announcement to this mailing list within the next week or
so to invite participation into this process.
>
>Cheers,
>Tino
>
>[1] https://wiki.yoctoproject.org/wiki/Yocto_Web_Hob_Design
>[2] http://git.yoctoproject.org/cgit/cgit.cgi/yocto-webhob-design/
>_______________________________________________
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto
prev parent reply other threads:[~2013-01-08 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 11:34 Future of WebHob? Tino Breddin
2013-01-08 15:31 ` Zhang, Jessica
2013-01-08 15:34 ` Tino Breddin
2013-01-08 16:20 ` Stewart, David C [this message]
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=CD1184C4.1CF74%david.c.stewart@intel.com \
--to=david.c.stewart@intel.com \
--cc=tb@travelping.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.