From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TSC Meetings for the meeting of June
Date: Sat, 12 Jun 2010 09:37:11 +0200 [thread overview]
Message-ID: <huvdf7$3as$1@dough.gmane.org> (raw)
In-Reply-To: <1276292268.29314.2660.camel@rex>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11-06-10 23:37, Richard Purdie wrote:
> On Fri, 2010-06-11 at 20:29 +0200, Koen Kooi wrote:
>>> Personally the org.openembedded.dev branch name does not bother me
>>> although I know master is the 'standard' git name.
>>> Afaik renaming does not really solve a problem.
>>
>> Ah well, seeing that the TSC completely failed to implement anything of
>> the things they decided on last month I think we can stop worrying about
>> this for the next few months. Does the TSC use FIFO or LIFO for their
>> targets?
>
> You've always got to be destructive and negative ;-).
>
> How about suggesting the TSC improves its process by assigning actions
> to people? That would be a bit more constructive and might address the
> problem.
>
> We're all volunteers doing this, we all have lots of things we're all
> involved in and we do the best we can.
>
> There is also nothing stopping anyone from helping the TSC, it was asked
> to make a decision, not necessarily implement it although I'd agree it
> would be desirable if someone on the TSC could help.
>
> FWIW, I'm about to take a weeks vacation which is my first proper
> holiday in a long time. I'll pay for it when I get back but until then
> I'm aiming to enjoy it.
>
> See you when I get back ;-).
My 2 weeks holiday starts on monday, although mine will be filled with
studying for exams :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMEzkmMkyGM64RGpERAoytAJ0cInkxyh8EdFw5AIJGyrIbLfH+1ACgqvta
SOBkogx6f+o6q2aJx1C54n0=
=sbsa
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-06-12 7:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 13:03 TSC Meetings for the meeting of June Holger Freyther
2010-06-09 13:25 ` Michael Smith
2010-06-09 13:53 ` Frans Meulenbroeks
2010-06-09 14:57 ` Chris Larson
2010-06-09 16:53 ` Philip Balister
2010-06-09 17:37 ` Khem Raj
2010-06-11 8:06 ` Frans Meulenbroeks
2010-06-11 18:29 ` Koen Kooi
2010-06-11 21:37 ` Richard Purdie
2010-06-12 7:37 ` Koen Kooi [this message]
2010-06-12 11:12 ` Frans Meulenbroeks
2010-06-12 11:47 ` Graeme Gregory
2010-06-12 12:20 ` Frans Meulenbroeks
2010-06-30 10:26 ` Holger Freyther
2010-06-30 11:05 ` Koen Kooi
2010-06-30 13:04 ` Frans Meulenbroeks
2010-06-30 13:19 ` Holger Freyther
2010-07-01 8:56 ` Koen Kooi
2010-07-01 11:52 ` Frans Meulenbroeks
2010-07-01 12:07 ` Graeme Gregory
2010-07-01 13:43 ` Frans Meulenbroeks
2010-07-01 17:59 ` Mark Brown
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='huvdf7$3as$1@dough.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox