All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: openembedded-architecture@lists.openembedded.org,
	Jens Rehsack <rehsack@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [Openembedded-architecture] Proposal: community maintained recipes in oe-core
Date: Thu, 07 May 2020 14:32:16 +0100	[thread overview]
Message-ID: <5c29774137778c7e4fe33421edff0a0d645575cd.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8K_3=pQQrLZD1D+vFhSxLsRTDxTsYB1r8wMZw7f4whKg@mail.gmail.com>

On Thu, 2020-05-07 at 15:24 +0200, Alexander Kanavin wrote:
> On Thu, 7 May 2020 at 14:38, Jens Rehsack <rehsack@gmail.com> wrote:
> > > I agree there should be a way to update maintainers e-main once
> > we determine they are not longer willing to take part in that
> > program or absent. I believe this an issue in general for
> > OpenSource has had to address over the years.
> > > 
> > > My plan is to experiment with this for the python3* recipes in
> > oe-core for a start: they've been bouncing between various people
> > over the past couple of years, but no active maintainer has
> > emerged.
> > 
> > I'd like to see 'non-systemd init' in, either :)
> 
> On a technical level this means updating maintainers.inc entries to
> list oe-core list as the email address; the next AUH round (in a week
> or so) will go as usual (because it's the first post-release one),
> and depending on how maintainers react, and who hasn't sent anything
> at all for a long time, I will propose something specific.

I agree we do need to do something and it was briefly discussed by the
YP TSC who basically agreed we need to tweak things.

Firstly though, we could do with digging out Ross' original emails and
properly documenting "maintainers" on the wiki. I thought we'd done
that but none of us could find it with a quick search which is bad if
it does exist.

Is anyone willing to summarise the current process on the wiki based on
those emails? (or point at the page if it does exist!)

Cheers,

Richard


      reply	other threads:[~2020-05-07 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 11:35 Proposal: community maintained recipes in oe-core Alexander Kanavin
2020-05-03 22:16 ` [Openembedded-architecture] " akuster
2020-05-05 11:48   ` Alexander Kanavin
2020-05-07 12:38     ` [OE-core] " Jens Rehsack
2020-05-07 13:24       ` Alexander Kanavin
2020-05-07 13:32         ` Richard Purdie [this message]

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=5c29774137778c7e4fe33421edff0a0d645575cd.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-architecture@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rehsack@gmail.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.