[yocto-ab] Themes for the 1.3 development cycle

[Richard Purdie]

I've talked to a number of people both at ELC and elsewhere about what
we should be looking as overall themes for the 1.3 cycle (making the
assumption we're going for a 1.3?). People have a lot of different ideas
but the things that seemed to be the common themes to me are:

Continuity / Refresh
====================

The usual keeping up to date with various upstream project, continue to
work on the quality of the metadata and keeping up to date with bug
fixing.

Stabilization & Adoption
========================

We've introduced a lot of changes. I think now may be a good time to
catch our breath so to speak and ensure everything is complete,
functional, well tested and has the right level of polish.

We also need to encourage adoption of the project by OSV and Silicon
Vendors and look at ways we can advance and integrate Shoeleather-type
board labs (from semis and OSVs).

Usability
=========

Introduce WebHob?
Continue improving error messages
Reserve time to jump on usability issues as they come up


I think these themes give us scope and room to make some valuable
changes to the system but also give us time to be able to help users
with adoption, address any usability issues that might arise and in
general move the project forwards.

Just to be clear about next steps from here, I think its something like:

a) AB discusses the topics and comes to some consensus
b) The topics get published and discussion starts with maintainers and 
   developers about the specific things they'd like to see in 1.3
c) Items are added to the bugzilla as enhancement requests (This can 
   happen at any time and I'm hoping we already have many there)
d) Song (our programme manager) and I will starts discussing who is able
   to take on which tasks and put engineering plans in place as/where 
   necessary.

I want to ensure anyone who wants to be involved at any step of this
process is involved. Particularly, if there are people who want to be
involved at step d), please let Song/me know. I realise community
contributions for example can't be placed on a schedule like this but it
will at least give us some overall plan for the things where we can do
that.

I'm imagining there will be discussion of the topics and additional
enhancement requests from the in person discussions at Collab summit but
I think there is no reason we can't have some kind of plan by then.

I'll open this for discussion at this point...

Cheers,

Richard