Hosting BSP layers on oe.org?

[Philip Balister]

On 03/04/2011 01:30 PM, Tom Rini wrote:
> On 03/04/2011 10:10 AM, Koen Kooi wrote:
>> CC: ing the board, although I know Philip is playing in the snow next
>> week.

He has wifi though :) Don't expect great thoughts from me unless the 
snow gets crappy.

I need to think through the BSP issue. I think you guys have touched on 
the key issues. There is also the issue of control of BSP's. (ie commit 
access)

As OE, we are not dogmatic about being open source purists, so there is 
room to just make things work in order maximize people ease of using OE.

Philip

>>
>> Op 4 mrt 2011, om 17:36 heeft Mark Hatle het volgende geschreven:
>>
>>> On 3/4/11 10:30 AM, Koen Kooi wrote:
>>>> Hi,
>>>>
>>>> I'm not sure if this a pure TSC issue, but really like your input on
>>>> this.
>>>> <TI hat on> I would like to host the TI BSP layer(s) on oe.org as
>>>> well as the
>>>> mailinglist(s) and patchwork config(s) to encourage the wider
>>>> community to
>>>> participate. My question is "Do we want that" and if so, "Do we want to
>>>> encourage it?".<TI hat off>
>>>>
>>>> It would be really nice if we can get people (e.g. silicon vendors,
>>>> OEM,
>>>> community developers) to do their OE stuff in the open and host them on
>>>> oe.org. What's your opinion on this?
>>>
>>> Speaking for my involvement in Yocto for a small bit. This was one of
>>> the
>>> things that we had planned early to enable in Yocto. We were not sure
>>> that
>>> purely open source groups such as OE would allow for BSP layers to be
>>> hosted
>>> from their site or not. (Especially when you factor in many BSPs require
>>> proprietary drivers of some type to be fully functional...)
>>>
>>> <back to my TSC role> I would certainly encourage BSP layers under
>>> the umbrella
>>> of Open Embedded. But I have a feeling this is one of the questions
>>> we need to
>>> ask the board about. They're the ones that are going to give us
>>> guidance on
>>> what rules (proprietary or not) as well as if they think it's
>>> appropriate. -- if
>>> they do, we can certainly help guide this within OE.
>>>
>>>> regards,
>>>>
>>>> Koen
>
> With my TSC hat on, I also see this as a board issue, not a TSC issue.
>