From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [TSC] First Meeting
Date: Wed, 30 Dec 2009 09:47:19 +0100 [thread overview]
Message-ID: <hhf42m$n7h$1@ger.gmane.org> (raw)
In-Reply-To: <1262118637.8748.173.camel@dax.rpnet.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 29-12-09 21:30, Richard Purdie wrote:
> On Tue, 2009-12-29 at 19:43 +0100, Koen Kooi wrote:
>> On 29-12-09 16:52, Graeme Gregory wrote:
>>> On Wed, 23 Dec 2009 19:24:18 +0000
>>> Richard Purdie <rpurdie@rpsys.net> wrote:
>>>> On Tue, 2009-12-22 at 14:00 +0000, Graeme Gregory wrote:
>>>>> I think we should try and organise a general one hour chat of the
>>>>> TSC on irc sometime the first week in January (4th - 8th). I think
>>>>> we should probably hold this private discussion just to organise
>>>>> ourselves then organise some form of public meeting later in the
>>>>> month to let the OE community have their say.
>>>>
>>>> Agreed, we should meet and the first week in January sounds good to
>>>> me. Looking at the timezones of the TSC members an afternoon or
>>>> evening GMT probably works best. How about I pick a time, say 8pm-9pm
>>>> on Monday 5th and then we can discuss who that doesn't work for :)
>>>>
>>> That works for me.
>>
>> Both the date and the medium don't work for me. I don't do IRC after
>> office hours anymore, since I'm only on IRC for work related things.
>
> Could you make an IRC meeting if it was during work hours?
That might work
> Is so, I suspect there may be others who might not be able to but we can
> try.
>
> If not, can you suggest an interactive medium that does work? Or are we
> not planning to have any interactive meetings?
Jabber conference rooms?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLOxOWMkyGM64RGpERAm9fAJ9d5BbMLHrxwJiZGJqjy0zKWP/EmQCfWfIt
8s7a+Qky/BQU4M6MBeYeQAQ=
=clRO
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-12-30 8:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 14:00 [TSC] First Meeting Graeme Gregory
2009-12-22 15:47 ` Frans Meulenbroeks
2009-12-22 16:13 ` Graeme Gregory
2009-12-22 16:43 ` Koen Kooi
2009-12-22 16:48 ` Philip Balister
2009-12-23 19:24 ` Richard Purdie
2009-12-23 23:35 ` Richard Purdie
2009-12-29 15:52 ` Graeme Gregory
2009-12-29 18:43 ` Koen Kooi
2009-12-29 20:30 ` Richard Purdie
2009-12-30 8:47 ` Koen Kooi [this message]
2009-12-30 14:45 ` Graeme Gregory
2009-12-31 10:16 ` Frans Meulenbroeks
2009-12-31 10:29 ` Phil Blundell
2010-01-04 10:46 ` Richard Purdie
2010-01-04 10:53 ` Koen Kooi
2010-01-04 11:24 ` Michael 'Mickey' Lauer
2010-01-04 11:46 ` Richard Purdie
2010-01-04 10:57 ` Frans Meulenbroeks
2010-01-04 11:02 ` Graeme Gregory
2010-01-04 11:52 ` Richard Purdie
2010-01-04 15:27 ` Chris Larson
2010-01-04 18:19 ` Michael 'Mickey' Lauer
2010-01-05 11:11 ` Graeme Gregory
2010-01-05 14:43 ` Richard Purdie
2010-01-05 16:26 ` Chris Larson
2010-01-07 8:04 ` Frans Meulenbroeks
2010-01-07 9:18 ` Graeme Gregory
2010-01-10 15:57 ` Rolf Leggewie
2010-01-10 16:16 ` Richard Purdie
2010-01-04 19:06 ` Denys Dmytriyenko
2010-01-04 19:17 ` Phil Blundell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hhf42m$n7h$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.