[meta-freescale] [RFC PATCH] fsl-commity-bsp: Add meta-qt5

Otavio Salvador otavio at ossystems.com.br
Mon Mar 24 07:26:32 PDT 2014

On Mon, Mar 24, 2014 at 10:08 AM, Daiane.Angolini at freescale.com
<Daiane.Angolini at freescale.com> wrote:
>> I am not sure we ought to include it or not. I see valid points for both
>> and I will focus my answer in the cons:
>>  * Documentation: our Release Notes, User Guide and FAQ are still
>> uncomplete. Add new stuff will only make it worse as those will also need
>> to be documented.
>>  * Tests: We see limited tests using the images we have and people does not
>> provide much feedback when we open the test form. More things will only
>> complicate it more.
> Until here I understand. And I agree.
>>  * Size: more metadata means more updates and maintenance. We need more
>> people helping the metadata maintenance before extend it.
> We already have almost 100% of the boards with maintainers. What do you mean, when you
> say we need more maintenance before extend the metadata?
> I still don´t have a clear idea if I like or dislike the idea of downloading more meta layers by default.
> I´m still deciding ;)

We need to split the maintainership areas:

* boards: Yes, most of board has someone committed nowadays and this
is awesome. This help us to get tests and feedback from those boards
and more people to help to address board specific things. However this
does not address the rest of meta-fsl-arm ...

* core BSP support: here we have some people working. You and me has
been doing most of work until now and Lauren has been started to
contribute more to this since Freescale started to work in the
3.10.17-1.0.0 BSP. Here we need a lot of help and it does affect
/every/ board we use/add/maintain ...

* technology specific support: here is where we are beginning. This
involves a lot of commitment and time. Here is where Qt5 and Chromium
are going to be covered. Currently we have no one really committed to
either and we cannot supply something in FSL Community BSP which is
not /maintained/ and for maintained I mean someone watching it and
doing the rework/improvements/commitments need for it to keep working
when Qt5 5.3 or Chromium 40 is released.

So it is a extensive topic; I hope it is clear now why I see we need
more people involved to grow.

Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

More information about the meta-freescale mailing list