From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH] maintainers.inc: reassign audio recipe maintainership
Date: Mon, 06 Jul 2015 19:49:41 +0100 [thread overview]
Message-ID: <1436208581.27597.67.camel@linuxfoundation.org> (raw)
In-Reply-To: <1436202135.2486.7.camel@tkkaskin-mobl3.ger.corp.intel.com>
On Mon, 2015-07-06 at 20:02 +0300, Tanu Kaskinen wrote:
> On Mon, 2015-07-06 at 19:36 +0300, Alexander Kanavin wrote:
> > On 07/06/2015 07:30 PM, Tanu Kaskinen wrote:
> > b) will you continue to maintain the recipes?
>
> I'd like to, but I haven't agreed about it with anyone. If the Yocto
> project wishes to keep the recipe maintenance within Intel/Windriver,
> that's fine by me.
There is no rule which says maintainers have to be Intel/Windriver. We
have several people who are not and the Yocto Project actively
encourages that (Khem comes to mind as a good example but there are
others). What we do ask is that people involved as maintainers do look
after the recipes they're associated with.
I'd also add that if at any point they can't, please do tell us so we
know, we'd prefer to than the alternatives.
Cheers,
Richard
next prev parent reply other threads:[~2015-07-06 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 16:30 [PATCH] maintainers.inc: reassign audio recipe maintainership Tanu Kaskinen
2015-07-06 16:36 ` Alexander Kanavin
2015-07-06 17:02 ` Tanu Kaskinen
2015-07-06 18:49 ` Richard Purdie [this message]
2015-07-07 10:40 ` Tanu Kaskinen
2015-07-07 13:13 ` Alexander Kanavin
2015-07-07 14:56 ` Tanu Kaskinen
2015-07-07 15:38 ` Tanu Kaskinen
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=1436208581.27597.67.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=poky@yoctoproject.org \
--cc=tanu.kaskinen@linux.intel.com \
/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.