[yocto] Web HOB planning discussion

[Barros Pena, Belen]

Hi all,

Thanks for the feedback: loads of interesting stuff there. We'll keep it all in mind when working on the next iteration.

If you think of anything else, please post it here.

Cheers

Belen

From: <Osier-mixon>, Jeffrey <jeffrey.osier-mixon at intel.com<mailto:jeffrey.osier-mixon at intel.com>>
Date: Wednesday, 13 June 2012 19:00
To: "Stewart, David C" <david.c.stewart at intel.com<mailto:david.c.stewart at intel.com>>
Cc: Konstantinos Papagiannopoulos <hello at konputer.net<mailto:hello at konputer.net>>, "yocto at yoctoproject.org<mailto:yocto at yoctoproject.org>" <yocto at yoctoproject.org<mailto:yocto at yoctoproject.org>>, Jim Kosem <jim at halfman.com<mailto:jim at halfman.com>>
Subject: Re: [yocto] Web HOB planning discussion

I agree, it is looking really interesting. Some comments below.

On Wed, Jun 13, 2012 at 10:39 AM, Stewart, David C <david.c.stewart at intel.com<mailto:david.c.stewart at intel.com>> wrote:
* This could be a great way for an organization to implement a workflow process using YP, rather than try to invent one themselves. We have gotten the feedback that some larger organizations want something like this, so I'm pleased with that direction.

Agreed - I have fielded a few questions about this as well

* With the above in mind, a key meta-usage is installing and configuring the server. For example, I could imagine an organization wanting to easily customize the home page with their own news and design information, etc.

* I could also see the opportunity for an OSV or service provider to brand the interface with their own goodness and extending it with their own features so this might be another meta-usage.

* And while I'm on a roll... whenever we talk about how the administrator installs this, we need consider how they update from a previous version, particularly if they have customized the home screen or other bits.

If branding & customization happen in CSS, the whole customization part should be portable from one version to another (as long as no one breaks anything structural). If we want to enable customization of functionality, though - e.g. pre-filter package selection, restrict certain features... - I could see that being tricky to implement in a portable way.

* Project creation and member add/remove should perhaps be an administrator role and password protected?

I vote yes on user management, but why password-protect project creation?

Other thoughts:

My feeling is that both Hob and WebHob will be most useful as tools to get people started. At some point, anyone who is doing more esoteric work than the Hob allows will need to learn how to get their hands dirty with recipes, config files, etc. For that reason, I really like the workflow focus, as that translates directly to the expected workflow of the whole build system. I suggest a future step might be guided configuration, guided recipe (and layer?) creation, and other progressive types of features that also show the workflow in action the way the current Hob does.

And I totally agree that the usability work you guys have done is making a huge difference in design. I like it! Want more!
--
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org<http://yoctoproject.org/>

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.