[oe] Splitting meta-oe?

[Burton, Ross]

On 17 February 2017 at 18:02, Martin Jansa <martin.jansa at gmail.com> wrote:

> 1) RSS is good thing.
>
> 2) The breakage wasn't caused by lack of maintainers (at least I don't
>    think that I or Joe were the bottleneck for integrating the fixes).
>
> 3) More maintainers doesn't mean more contributions from people actually
>    using now broken components, it's actually easier to just send a fix
>    than to be a maintainer of some layer just to be able to also merge
>    your fix yourself.
>
> 4) It doesn't look so dramatic if it turns out that 200 of those
>    blacklisted recipes weren't actually used by anyone still active in
>    OE ecosystem.
>
> 5) If someone wants to replace me as meta-oe maintainer, go ahead, it
>    stopped being fun for me long time ago, now it's just slightly annoying
>    routine which takes my free time I would rather invest in something
>    cooler
>

I'll probably reply to this properly when I'm not rushing between various
things, but I want to make it clear that I think the work you (JaMa) has
been doing on meta-oe is beyond legendary and I've no problem at all with
that.  I just wonder if it would be easier to deal with stale layers that
nobody is actually using if they were separate repositories instead of
being part of the meta-oe umbrella.

But they're not my layers so I have no say, and obviously everyone else
disagrees! :)

Ross