From: Robert Buchholz <rbu@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] g15 and freevo up for grabs
Date: Mon, 18 Jan 2010 17:56:08 +0100 [thread overview]
Message-ID: <201001181756.12060.rbu@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
Hello,
I want to drop maintenance for some of the packages that I have acquired
over the years. Some of them are still co-maintained, some are now
unmaintained.
=== Freevo ===
Freevo is split up in different Python components. They are all
maintained by a herd, but a dedicated maintainer is needed.
media-tv/freevo # media-tv herd
dev-python/kaa-base # python herd
dev-python/kaa-display # python herd
dev-python/kaa-imlib2 # python herd
dev-python/kaa-metadata # python herd
dev-python/pynotifier # python herd
== G15 tools ===
These packages are now without a maintainer:
app-misc/g15macro
app-misc/g15message
dev-libs/libg15render
media-plugins/audacious-g15-spectrum
app-misc/g15mpd
app-misc/g15stats # already maintainer-needed
These are maintained by Chainsaw:
app-misc/g15composer
app-misc/g15daemon
dev-libs/libg15
Most g15 tools are part of the LCD herd. Since that is only actively
myself, it does not help. I will replace the herd association in four
weeks if no new maintainer steps up or a new "g15" herd is formed.
Otherwise the lack of maintenance is just hidden.
Thanks,
Robert
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2010-01-18 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 16:56 Robert Buchholz [this message]
2010-01-18 20:29 ` [gentoo-dev] g15 and freevo up for grabs Robin H. Johnson
2010-01-18 22:53 ` Tony "Chainsaw" Vroon
2010-01-19 3:09 ` Robin H. Johnson
2010-01-19 4:24 ` Doug Goldstein
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=201001181756.12060.rbu@gentoo.org \
--to=rbu@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