Agenda for 2011-02-14 meeting

[Koen Kooi]

Op 11 feb 2011, om 17:23 heeft Tom Rini het volgende geschreven:

> On 02/11/2011 08:41 AM, Koen Kooi wrote:
>> 
>> Op 11 feb 2011, om 16:09 heeft Stefan Schmidt het volgende geschreven:
>> 
>>> Hello.
>>> 
>>> If nobody else wants to beat me with it (do it!) I could take care of my
>>> proposed secretary stuff like agenda and meeting minutes.
>>> 
>>> On Fri, 2011-02-11 at 12:15, Koen Kooi wrote:
>>>> 
>>>> Op 11 feb 2011, om 08:55 heeft Stefan Schmidt het volgende geschreven:
>>>> 
>>>>> List of agenda items. Please fill up...
>>>>> 
>>>>> Agenda 2011-02-14 meeting
>>>>> -------------------------
>>>>> 
>>>>> 1) Setup oe-core repo and import yocto with history but without bitbake. Decide
>>>>>  who will take this action item. [Proposed: Koen, Khem]
>>>>> 
>>>>> 2) Agree on meeting date, time and meeting lead. [Proposed: Stefan]
>>>>> 
>>>>> 3) Discuss how we get OE metadata into the oe-core repo without loosing to much
>>>>>  histroy and credits of the original authors. [Proposed: Stefan]
>>>> 
>>>> x) access model for OE core and other layers
>>>> 
>>>> x + 1) guidelines for layers, e.g. encourage distro layers or not
>>>> 
>>>> x + 2) timeline for changes, e.g. OE releases, yocto milestones, etc
>>>> 
>>>> x + 3) definition of OE core
>>>> 
>>>> x + 4) OE goals and guarantees for OE-core, which distros and machines to we recommend and 'test'?
>>> 
>>> y) Quickly discuss if we are fine with having the IRC meeting (read-only) open
>>>   for interested community member. (Interest expressed from several ones)
>> 
>> I'm against that, it leads to chatter in backchannels that isn't needed or wanted. The archive of this list and minutes should be enough.
> 
> I'm for it.  I know that other projects like Jenkins have their meetings in public.  I don't think we need to adopt the formal bits of how they run it, but using say #oe-tsc, setting it to moderated and giving the TSC members voices should be enough.  We should however ask that observers be just that, observing, rather than messaging folks to argue their point further

Seeing what kind of people are OE developers, that's not going to work. I feel quite strongly about this. In the first TSC we did the private meetings and public minutes, which worked quite well.