Path: csiph.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!bofh.it!news.nic.it!robomod
From: Nilesh Patra <nilesh@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Please enable me transfering python-bioblend to Debian Med team
Date: Wed, 22 Dec 2021 20:50:01 +0100
Message-ID: <DxfMB-u7-1@gated-at.bofh.it>
References: <Dw6V3-8h1-1@gated-at.bofh.it> <DwOCJ-Q8-3@gated-at.bofh.it> <DxdB8-7Jp-11@gated-at.bofh.it> <DxeQx-8ny-1@gated-at.bofh.it> <Dxfjz-kT-7@gated-at.bofh.it>
Old-Return-Path: <nilesh@debian.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="1wRNkakYBdKlEyOi"
Content-Disposition: inline
Organization: The Debian Project
Approved: robomod@news.nic.it
Lines: 127
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:13792


--1wRNkakYBdKlEyOi
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Pierre-Elliot,

On Wed, Dec 22, 2021 at 08:06:01PM +0100, Pierre-Elliott B=C3=A9cue wrote:
> >> I'm sorry but pressuring to take over a package is not really fine. If
> >> you're not happy with the time it takes for an answer, you can try to
> >> fill an ITS and if the procedure goes to its end then you may take ove=
r.
> >
> > Please note:  The people involved are the same.  We are members of
> > both teams but consider the Debian Med team more appropriate.  We
> > are simply missing the permissions to do the move properly.
>=20
> I am aware of that.
>=20
> Yet, the fact that you are members of both teams doesn't entitle you to
> decide such a transfer, even if you had the technical rights to do so.

Hmm, I am not sure what the problem in such a case would be (permission in =
both teams)
Steffen is the maintainer (uploader if you might prefer it that way) and he=
 has
agreed already[1] -- so what's the problem?

[1]: https://lists.debian.org/debian-med/2021/12/msg00119.html

> I therefore stand my point: the way Debian is made has not changed
> recently, and taking over still requires a formal approval from the
> maintainer, which you are not.
>=20
> The only alternatives are either an ITS or MIA team orphaning their
> packages, but as the maintainer is an active team, the latter will not
> happen.

I do not think it is sensible to take consensus from an entire team to
move a single package.
Honestly speaking, we really do not need to make team transfer=20
debian processes such a high friction ones -- it just stalls the work for n=
o good reason.
The package has not seen uploads since more than two years, I really doubt =
anyone in the team feels strong
ly about not moving it.

If you are talking about Ond=C5=99ej doing the uploads apart from the initi=
al uploads,
then you probably are also aware that Ond=C5=99ej does a number of team-mai=
ntained package
uploads to fix bugs, does updates and so on (a lot of us do so, for that ma=
tter albeit in other teams)
I really don't think that he has a personal interest in every single one of=
 those packages (including this one)
but we should hear from him.

> >> and they could be willing to check that no one in the team objects.

Sure but how are you making a "check" here? I do have admin access in a few=
 teams, and speaking for
myself: I  would send out
an email to the list, wait for a time frame (maximum 1 week) and check if s=
omeone has any comments
If not, I would make a move.
So we already have a mail in the debian-python mailing list, and no objecti=
ons so far, so ....

I would have probably done more to ask for consensus better (asking on IRC =
channels etc) but admittedly, we only
have 24 hours in the day, and several dozens of packages to do.

> I think you missed the second part of my sentence you're quoting.

I recetified this above.

> >> Steffen only did the first upload. I'd suggest to contact Ondrej (Cc-e=
d).
> >>=20
> >> In the meantime, Nilesh is member of the Python team and therefore can
> >> do an update of the package (but not change the maintainer).
> >
> > I'm a member myself - but the upload should happen in the Debian
> > Med team.  This is the point of my mail.
>=20
> I disagree.
>=20
> Either the python team accepts the package to be transferred and it
> indeed should happen there.=20

Please don't repeat your points. You wrote the same stuff above (wrt MIA, I=
TS etc)

> This probably means we should have a stanza in the DPT policy about
> transfer of maintainership.

This would be definitely helpful.

PS: I do not mean to be disrespectful, please do not interpret my reply tha=
t way, I am
only trying to reason it out.

Regards,
Nilesh

--1wRNkakYBdKlEyOi
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmHDgG0ACgkQALrnSzQz
afFYSxAAokKhInIR03cD6zLlYE5ApUsr1FLiml0YyGFPQN2DEZKkjw1oTM5w6Wn/
EBapIF4gc6P5wQej2jAQY5Q6xRPOStWH2cF8dN+GCdo6IaL5b1t6MfcU1fs5aNDN
FmiEWV00jEIyYu5d7mTY80GACdXOsO6cGmAAAqfQpgM1WG3onz4r3e60UvI5S83W
TzEQF09l8r0XDZHdmLJ6VNFfLipWylqR41A5Mti311LV1TSuXa5JW43KBOkHDXv7
fAQCv0+AvbOXzNaeqaKzTAw2ujuhwJzGavxQPJVhK3zFv0u9dUNgTcOhIM1aKiIr
vahBRpGXJABuIve4iRc/T+Xj8BipVReUcK2VYSfJ8WM9rIGIza5RxEwDrCyC8zPu
Se6R5O7I3IbXOeDDiU08VHuq77xNTuimWx22eFJQC0Fq7Fyhqub22ym319s3L38F
aBU1Oi27RHK9dz6tCQtvHAUMq/w1UOFXCEt/VBcZgGq0LzBIhkMQtQ9hiFZxukRl
q8pZYd1GfvkO30AdvrJlVNbhsSZnoTIokT5TOovgQyEyZ9/xi2KDYqnRsfIbMiiP
QNj6FxEmjbzcILeQFUYgXmht0025jMDeaqDqs1Lzi6QlO9pofS7x2kJCpQwjJHr2
axGnBZYiGqy9rIk05QEDFgMeDI/brf0GOSx5w3QB0qFGCN+lZww=
=jImF
-----END PGP SIGNATURE-----

--1wRNkakYBdKlEyOi--