public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: <gentoo-dev-announce@lists.gentoo.org>
Cc: <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev-announce] Multiple misc. Python packages for grabs
Date: Sat, 29 Oct 2016 23:21:57 +0200	[thread overview]
Message-ID: <20161029232157.172fb126.mgorny@gentoo.org> (raw)

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

Hello,

The Python team is dropping itself from maintainers of the following
packages. As a result, those packages no longer have any maintainer:

app-admin/supervisor
app-editors/leo
app-misc/yworklog
app-text/pdfminer
app-text/pylize
dev-util/bumpversion
dev-util/tailor
net-ftp/pybootd
net-im/turses
net-irc/redirbot
net-misc/charm
net-misc/pycnb
net-misc/whatportis
net-news/rawdog
net-voip/blink
sys-process/glances
www-apps/bitten
x11-misc/menumaker

Those packages are not really part of the Python ecosystem. Most of
them had python@g.o added as a co-maintainer (or in some cases as
the only maintainer, without even bothering to ping us) because
the software in question was written in Python, and never had been
really maintained by the Python team. Once the primary maintainer
abandoned them, they became sole Python team responsibility.

Using this opportunity, I would like to note that there really is no
reason to add Python team as co-maintainers to every software ever
written in Python. The Python team focuses on maintaining tools
and modules needed to use and develop Python on Gentoo.

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 931 bytes --]

                 reply	other threads:[~2016-10-29 21:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20161029232157.172fb126.mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@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