[oe] Minutes, OE TSC meeting, March 10 2011

[Richard Purdie]

On Thu, 2011-03-17 at 09:38 +0100, Frans Meulenbroeks wrote:
> Mark, thanks for the minutes.
> 
> There is one remark I'd like to make and one agenda item i'd like to
> coin for the TSC (I'll do that here since I haven't seen an agenda and
> call for topics for the next TSC meeting)
> 
> 2011/3/17 Mark Hatle <mark.hatle at windriver.com>:
> 
> >
> > Further discussion of deprecation of OE bugzilla.  Yocto intends to keep a bug
> > tracking system for itself.  This might also be the place where OE-Core bugs can
> > be tracked.
> >
> 
> What about the remaining parts of OE?
> Do we also stop to use bugzilla for those?

The current OE bugzilla is a mess, I think that much is clear. Why?

For a bugzilla to work, its needs active maintenance. Yocto has enough
resources to do this for OECore, its is not really able to take on the
whole of OE though, we're simply not resourced to do it. I'd rather take
on something manageable and do it well that try and do too much and do
it badly.

The offer of Yocto looking after OECore bugs and the bugzilla for them
is therefore a positive step but if we want to cover the whole of OE,
the resources need to come from somewhere and there is nobody
volunteering at this time.

I think the TSC is pretty much recommending the existing OE bugzilla
should be shut down as nobody is doing active work with it and it just
misleads people.

> Or will that also be done in the yocto bug tracking system?
> 
> I would like to suggest that the TSC starts to discuss how to deal
> with the non-oe-core recipes that we have.
> We have meta-oe of course. It might be useful to discuss and decide on:
> - do we want to use meta-oe (and if so, how should it be
> sub-structured, e.g. similar to oe-core meta* dirs)

I think the TSC has said yes, it wants to encourage meta-oe and that is
was encouraging a more layered approach there.

> - assuming it'll be meta-oe, how will we deal with it in terms of
> adding recipes, dealing with patches, retention policy, ownership etc
> etc

I think the TSC did discuss and document some of this but its certainly
not crystal clear yet. We're still trying to sort out the documentation
for OE Core though and that is a priority over meta-oe. Note that it
doesn't have to be the just the TSC members who do this and we're open
for any help in writing drafts for discussion...

> - how/where to store deprecated oe-core recipes that are still
> useful/needed (and how to retire them if they are not needed any
> more).

If meta-oe is layered, a layer for these could be created to make this
clear.

Cheers,

Richard