[Openembedded-architecture] patchwork (etc) support for BSP layers (OEDAM 2017)

[Otavio Salvador]

On Mon, Mar 6, 2017 at 9:59 PM, Denys Dmytriyenko <denis at denix.org> wrote:
> On Mon, Mar 06, 2017 at 06:59:53PM -0500, Trevor Woerner wrote:
>> On Mon 2017-03-06 @ 09:03:32 AM, akuster808 wrote:
>> > On 03/05/2017 09:43 PM, Trevor Woerner wrote:
>> > > Hi,
>> > >
>> > > One of the items discussed over lunch at the recent OEDAM 2017, but that I
>> > > can't find in the notes, was about including support for more layers in
>> > > patchwork.
>> > I believe this was in the context of the sub layers in meta-openembedded.
>> > OE ( community)  could be driving that work, changes etc.
>>
>> Funny... I remember it the other way around.
>>
>> _I_ brought up this topic in the context of meta-rockchip and it was almost
>> immediately subverted by everyone wanting to talk about Tim Orling's
>> meta-openembedded split up work ...and here we are again :-(
>>
>> So, ignoring Tim's work for the time-being, would it be possible for
>> "non-core" layers (maybe the layers found in the layer index?) to be added to
>> patchwork (and possibly benefit from other available Yocto tooling)?
>>
>> When I brought this up RP immediately questioned whether BSP layers should be
>> hosted on git.yoctoproject.org. Then there was talk about financial
>> contributions. Then someone suggested the Raspberry Pi foundation might want
>> to fund some of this infrastructure for meta-raspberrypi. Then we drifted into
>> the meta-openembedded split-up (and everyone forgot the previous 10 minutes).
>
> The discussion went on and we eventually concluded that *commercial* BSP
> layers can only be hosted on git.yoctoproject.org and benefit from tools like
> patchwork only if the company behind it is a paying member of the Yocto
> Project. If the BSP is rather *community* supported, then it's probably OK
> to provide free resources like git hosting and patchwork. That was my
> understanding - Richard can correct it, if needed.

The requirement of membership for patchwork is non-sense. It is hosted
under openembedded.org domain and as such it is a community resource.
YP Git, CI and whatever is inside YP resources I am fine with
requiring membership or so but patchwork is not and should not be one
of the requiring ones.

It is of our best interest a well maintained and organized set of
layers and review process so it should be make easy for layers to join
our preferred workflow and process.

-- 
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