All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tanu Kaskinen" <tanuk@iki.fi>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: I wish to drop my recipe maintainer duties
Date: Mon, 14 Dec 2020 21:07:36 +0200	[thread overview]
Message-ID: <e4085caa6fe95c5d09a23a850fe8748c93323af4.camel@iki.fi> (raw)

Hello,

I haven't lately had time to do OE work, or maybe the lack of time is
more rooted in lack of motivation since I don't objectively have a very
busy life, but in any case, I think it's time for me to step down as a
recipe maintainer. When in 2015 I transitioned from being paid for the
work to a volunteer, I had plans to use OE in hobby projects, but those
projects haven't materialized, so I don't really have any connection to
OE other than being a recipe maintainer. My experience of the community
has been very positive, it has always been nice to work with you, thank
you for that!

Should I post a maintainers.inc patch that changes all my recipes to to
unassigned, or should they or some of them be directly transferred to
someone else?

I will still post some patches for pulseaudio that convert the recipe
from autotools to meson. I've had them ready since the last feature
freeze, and I intended to submit them today, but I found out (as I read
the mailing list for the first time in three months) that the recipe
has had a major version update, so I'll have to redo some tests first.

-- 
Tanu


             reply	other threads:[~2020-12-14 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 19:07 Tanu Kaskinen [this message]
2020-12-14 19:16 ` [OE-core] I wish to drop my recipe maintainer duties Alexander Kanavin
2020-12-14 23:00   ` Richard Purdie
2020-12-16 12:11 ` Ross Burton

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=e4085caa6fe95c5d09a23a850fe8748c93323af4.camel@iki.fi \
    --to=tanuk@iki.fi \
    --cc=openembedded-core@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.