[oe] TSC Meeting 2010/03/02

Richard Purdie rpurdie at rpsys.net
Wed Mar 3 11:35:49 UTC 2010

TSC Meeting 2010/03/02

We moved the time to Tuesday since I couldn't make Thursday.
Unfortunately Mickey couldn't make Tuesday due to a last minute meeting
but four of us met anyway to discuss various issues. The outcome of
various topics was:

Code of Conduct

We agreed we need one but also that its outside the remit of what the
TSC should be discussing. We don't feel something heavy and draconian
with every action spelt out is a sensible idea but we should have some
guidelines behaviour can be judged against. In this respect we could do
a lot worse than adopt the Ubuntu CoC

We'd like to propose to the e.V. board and members that the Ubuntu CoC
should be adopted (wording adjusted to suit OE) by the OE e.V.

The one problem here is that we don't have a community council. The TSC
could serve as this but we'd prefer to split this work to a dedicated
group. We'd like to ask the members to discuss this and see what people
feel is the best thing to do.


We agreed to hold TSC elections in April which means calling for
candidates soon. We'd like to see active people wanting to move OE
forward and would love to see come competition for the TSC places. Now
we've established the format and input required hopefully more people
will feel comfortable coming forward. For more information about what
the role involves please talk to any existing TSC member.


People do seem to use Angstrom as a target for certain discussions. The
people involved have got on and made a success of a distribution and
people should respect that. There are some customisations which could be
more generic so other people would be more comfortable using them. These
should be discussed and the Angstrom devs are amenable to that but
breaking Angstrom for the benefit of others isn't really fair.

Splitting Angstrom into its own directories (e.g. for images) is going a
full circle as Angstrom did have that and was coerced into merging
things. No solution will please everyone but before the TSC can get
involved, discussions need to happen with clear proposals. Angstrom is
not perfect but it has gone out there and achieved things which is worth
keeping in mind.

Developer Effort

Rather than discussions such as the above, how about injecting that
energy into adopting the new staging, BBCLASSEXTEND and -nativesdk code?


Mentioned briefly, no concerned we raised above those expressed already.
Having coherent layer handling is desirable and the bitbake team will
continue its work accordingly.

Other Business

Apologies have been made to the TSC for my absence at the last meeting.
There was some confusion on my part over the protocols and I didn't 
think the meeting was happening.


Your TSC

Graeme Gregory (XorA)
Koen Kooi
Chris Larson (kergoth)
Michael 'Mickey' Lauer (mickeyl)
Richard Purdie (RP)

More information about the Openembedded-devel mailing list