public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: Patrick Lauer <patrick@gentoo.org>
Subject: Re: [gentoo-project] Corporate affiliations of Council members
Date: Tue, 23 Jun 2020 23:50:34 +0300	[thread overview]
Message-ID: <6271494.IoEIV5pvuq@farino> (raw)
In-Reply-To: <38ba2c99-d811-8cd7-de2b-ca607f393ba8@gentoo.org>

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

Am Dienstag, 23. Juni 2020, 20:48:04 EEST schrieb Patrick Lauer:

> (And this is why I'm against things like the current py2 purge: There is
> code out there that works, can't be rewritten to py3 in a reasonable
> time*, and hasn't been rewritten in another language yet. There is no

> tl;dr: I want to be lazy, so stop breaking stuff ;)

You gotta be kidding me. 

If your employer wants to work on obsolete (yes) stuff, he should task you 
with maintaining it. 

In the context of a distribution that does *not* only mean "keep things until 
they are so rotten you can't distinguish them from the floor anymore", but it 
also means fixing bugs and keeping the dependency tree in a sane state.

So, in this case I would strongly recommend to the higher-ups of A***** to pay 
you (or anyone else) to commit to keeping 
* not just what *you* need in Python2 maintained and working, but
* to maintain the whole python-related package tree in a consistent state 
then. 
Not just complaining that others don't volunteer the work.

(This argument applies equally to other cases, like S***.)

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, qa, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-23 20:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 16:18 [gentoo-project] Corporate affiliations of Council members Michał Górny
2020-06-22 17:07 ` Brian Dolbec
2020-06-22 17:36 ` Robin H. Johnson
2020-06-22 18:20   ` Rich Freeman
2020-06-22 18:15 ` Matt Turner
2020-06-22 18:56 ` Alec Warner
2020-06-22 20:17   ` Michał Górny
2020-06-23 21:17   ` Andreas K. Hüttel
2020-06-24  5:53     ` Michał Górny
2020-06-24 11:23       ` Rich Freeman
2020-06-22 19:36 ` Ulrich Mueller
2020-06-22 20:32 ` William Hubbs
2020-06-23 13:33 ` Thomas Deutschmann
2020-06-23 17:48 ` Patrick Lauer
2020-06-23 20:50   ` Andreas K. Hüttel [this message]
2020-06-24 19:30     ` Patrick Lauer
2020-06-24 20:00       ` David Seifert
2020-06-24 20:08       ` Andreas K. Hüttel
2020-06-24 20:22         ` Patrick Lauer
2020-06-26 13:39           ` Andreas K. Huettel
2020-06-23 21:02 ` Andreas K. Hüttel
2020-06-26  1:41 ` Max Magorsch
2020-06-26  3:23 ` Aaron Bauman
2020-06-27 13:51 ` Mikle Kolyada
2020-06-28 19:57 ` Georgy Yakovlev
  -- strict thread matches above, loose matches on Subject: below --
2020-07-02 17:14 Richard Yao

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=6271494.IoEIV5pvuq@farino \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=patrick@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