Package: lists.debian.org
Severity: wishlist
Hi listmasters,
please accept the former mailing list
Debian Wine Party <pkg-wine-pa...@lists.alioth.debian.org>
on lists.debian.org.
I'm not formally requesting this yet, since I'd like to first have some
official endorsement from the old team admins on alioth, and some
general feedback on the details below.
Further I wasn't the owner of the old list. I assume the owner of the
old list was ovek at arcticnet.no, who wasn't active in the team (and
Debian afaik) since 2011. Do you have access to the old subscribers
list, or know a way to get it?
If you're generally ok with the request, please tell me your formal
requirements for the new owner (DD?). I'm a member of the Wine team (as
DM with upload rights for wine, wine-development and winetricks, and as
developer in wine-team@salsa).
If you need more information I'd be happy to give answers.
The old archive is at
https://alioth-lists-archive.debian.net/pipermail/pkg-wine-party/
I'll ask the other maintainers and other probably interested persons to
write to this bug. From the Wine perspective I discuss this at #897120.
Following are my proposed answers to the questions on
https://www.debian.org/MailingLists/HOWTO_start_list
Name:
-----
debian-wine
Rationale:
----------
The list is used to coordinate the maintainers and interested persons in
wine
wine-development
wine-gecko-N.NN (2.21 and 2.24 in the archive)
winetricks
exe-thumbnailer
The old list was used mostly, but not exclusively, for automated mails
(bugs and archive uploads). But it was also used for direct team
communication, and I assume not having a common address for these
packages would be a major drawback for the Wine _team_. E.g. it was my
personal entry point in maintaining Wine after filing a few bugs.
The list is a single contact point for both Wine source packages (one
tracking stable, the other development upstream releases, while
sometimes bugs are reassigned from one to the other). I get it that a
tracker.d.o team would help to manage this
two-source-packages-for-one-upstream setup, but at least for now, e.g.
without a public archive for tracker, I don't see this as sufficient.
In the case of wine-gecko, which needs a new source package with every
new version, it would also help to follow the development, or (since
development is currently stalled) to re-start it.
Short description:
------------------
Maintenance of the Debian Wine and related packages
Long description:
-----------------
Discussions about the packaging in Debian of Wine and related packages.
This list is not moderated; posting is allowed by anyone.
Posting address: debian-w...@lists.debian.org
Category:
---------
Developers
Subscription Policy:
--------------------
open
Post Policy:
------------
open
Web Archive:
------------
yes
Greets
jre
