public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Aaron Bauman <bman@gentoo.org>
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council meeting 2021-07-11 - call for agenda items
Date: Tue, 06 Jul 2021 09:02:14 +0200	[thread overview]
Message-ID: <ueeccylft@gentoo.org> (raw)
In-Reply-To: <YON/cbn0oQMqFisE@Aaron-Baumans-MacBook-Pro.local> (Aaron Bauman's message of "Mon, 5 Jul 2021 17:53:53 -0400")

[-- Attachment #1: Type: text/plain, Size: 810 bytes --]

>>>>> On Mon, 05 Jul 2021, Aaron Bauman wrote:

> On Mon, Jul 05, 2021 at 11:42:36PM +0200, Ulrich Mueller wrote:
>> The point is that banning an EAPI doesn't have any noticeable effect.
>> For example, if you look at EAPI 0 (banned on 2016-01-10) and EAPI 4
>> (banned on 2018-04-08), there's neither a cusp nor any change of slope
>> visible for the curves plotted here:
>> https://www.akhuettel.de/~huettel/plots/eapi.php

> We have had the issue in the past. Taking 1 minute to vote on a ban of
> an EAPI in a council meeting is a minute task and enforces the goals
> of the project.

But we don't actually enforce the ban. Doing so would mean adding the
EAPI to eapis-banned in layout.conf, which in turn would imply that
commits of (new or existing) ebuilds with a banned EAPI would be
rejected.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

  reply	other threads:[~2021-07-06  7:02 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05  9:20 [gentoo-project] Council meeting 2021-07-11 - call for agenda items Ulrich Mueller
2021-07-05 10:17 ` Ulrich Mueller
2021-07-05 10:19   ` Ulrich Mueller
2021-07-05 21:19   ` Aaron Bauman
2021-07-05 21:42     ` Ulrich Mueller
2021-07-05 21:53       ` Aaron Bauman
2021-07-06  7:02         ` Ulrich Mueller [this message]
2021-07-06 13:59           ` Thomas Deutschmann
2021-07-06 15:40             ` Ulrich Mueller
2021-07-06 17:42           ` Aaron Bauman
2021-07-06 17:55             ` Ulrich Mueller
2021-07-06 19:32             ` Rich Freeman
2021-07-07 13:45   ` Michał Górny
2021-07-07  1:59 ` Rich Freeman
2021-07-07  6:55   ` Sam Jorna (wraeth)
2021-07-07 11:25     ` Rich Freeman
2021-07-07 13:00       ` Sam Jorna (wraeth)
2021-07-07 11:40   ` Joonas Niilola
2021-07-07 11:51     ` Rich Freeman
2021-07-07 11:57       ` Ben Kohler
2021-07-07 13:41   ` Michał Górny
2021-07-07 20:38   ` Robin H. Johnson
2021-07-07  5:08 ` Robin H. Johnson
2021-07-07  9:27   ` Ulrich Mueller
2021-07-07 11:31     ` Rich Freeman
2021-07-07 20:28       ` Robin H. Johnson
2021-07-07 21:24         ` Rich Freeman
2021-07-08 16:57           ` Robin H. Johnson
2021-07-08 17:43             ` Ulrich Mueller
2021-07-08 17:51               ` Robin H. Johnson
2021-07-25 17:22                 ` Ulrich Mueller
2021-07-08 17:43             ` Rich Freeman
2021-07-07 20:23     ` Robin H. Johnson
2021-07-07 23:00       ` Ulrich Mueller
2021-07-08 16:58         ` Robin H. Johnson
2021-07-08 15:44 ` [gentoo-project] Council meeting 2021-07-11 - agenda Ulrich Mueller

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=ueeccylft@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=bman@gentoo.org \
    --cc=gentoo-project@lists.gentoo.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