All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Adrian Bunk <bunk@stusta.de>, Ross Burton <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 08/11] lrzsz: remove the recipe
Date: Thu, 21 Nov 2019 16:41:45 +0000	[thread overview]
Message-ID: <870a198dc47ec63b0741ad8abe44b55378d2a818.camel@linuxfoundation.org> (raw)
In-Reply-To: <20191121153610.GA28013@localhost>

On Thu, 2019-11-21 at 17:36 +0200, Adrian Bunk wrote:
> There are also two higher level topics that should be discussed:
> 
> 1. Removal of maintainers.inc
> There is some nitpicking that every recipe needs a maintainer.
> For the package in question the maintainer is not involved in the 
> discussion, and doesn't seem to have been asked for support or
> asked regarding the suggested removal.

There are pros and cons to having it. Having people who help look after
specific recipes is appreciated. Some maintainers are more active than
others and people's free time varies. We found one of the corner cases
here, the fact there are some surprises no one.

If we remove it does the situation improve? I'd say not.

FWIW the number of recipes up to date has improved recently (or feels
to have) and the process does encourage people to send updates.

Reality is there are shades of grey. By that I mean that we are never
going to have a 100% definitive/defined process which works all of the
time in every case.

We're doing the best we can and I'm not sure this discussion is going
to be productive as I don't see a path where this discussion improves
things.

> 2. Who is responsible for fixing gettext breakages in meta-oe?
> Alexander or Khem?

or the wider community? They can certainly help.

Cheers,

Richard



  reply	other threads:[~2019-11-21 16:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 13:44 [PATCH 01/11] man-pages: correct the SRC_URI Alexander Kanavin
2019-11-20 13:44 ` [PATCH 02/11] man-pages: update to 5.03 Alexander Kanavin
2019-11-20 13:44 ` [PATCH 03/11] dummy-sdk-package.inc: do not include files into RREPLACES Alexander Kanavin
2019-11-23 14:37   ` Richard Purdie
2019-11-20 13:44 ` [PATCH 04/11] gettext-minimal-native: update to 0.20.1 Alexander Kanavin
2019-11-20 13:44 ` [PATCH 05/11] gettext: " Alexander Kanavin
2019-11-20 13:44 ` [PATCH 06/11] e2fsprogs: fix build issues with the latest version of gettext Alexander Kanavin
2019-11-20 13:44 ` [PATCH 07/11] console-tools: remove the recipe Alexander Kanavin
2019-11-20 13:44 ` [PATCH 08/11] lrzsz: " Alexander Kanavin
2019-11-20 19:49   ` Adrian Bunk
2019-11-20 20:00     ` Alexander Kanavin
2019-11-20 20:17       ` Adrian Bunk
2019-11-20 21:12         ` Alexander Kanavin
2019-11-20 21:38       ` Phil Blundell
2019-11-20 22:12         ` Alexander Kanavin
2019-11-20 22:32           ` Phil Blundell
2019-11-20 22:56             ` Alexander Kanavin
2019-11-20 23:18               ` Adrian Bunk
2019-11-21  9:24                 ` Ross Burton
2019-11-21 10:10                   ` Richard Purdie
2019-11-21 13:59                     ` Phil Blundell
2019-11-22  0:49                       ` Ross Burton
2019-11-25 12:07                       ` Ross Burton
2019-11-26 11:59                         ` Phil Blundell
2019-11-26 12:06                           ` Phil Blundell
2019-11-26 14:49                             ` Ross Burton
2019-11-27 14:32                           ` Ross Burton
2019-11-27 15:07                             ` Phil Blundell
2019-11-21 15:36                   ` Adrian Bunk
2019-11-21 16:41                     ` Richard Purdie [this message]
2019-11-20 13:44 ` [PATCH 09/11] p11-kit: convert to meson Alexander Kanavin
2019-11-23 23:04   ` Richard Purdie
2019-11-25 16:53     ` Alexander Kanavin
2019-11-20 13:44 ` [PATCH 10/11] mc: backport a patch to fix builds with latest gettext Alexander Kanavin
2019-11-20 13:44 ` [PATCH 11/11] systemtap: update to 4.2 Alexander Kanavin

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=870a198dc47ec63b0741ad8abe44b55378d2a818.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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.