Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Emmanuel Arias Newsgroups: linux.debian.maint.python Subject: DPT ideas to organize Date: Fri, 14 Jun 2024 15:30:01 +0200 Message-ID: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Jun 14 13:26:12 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=1.59 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, BODY_8BITS=1.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FOURLA=0.1, HTML_MESSAGE=2, LDO_WHITELIST=-5, META_ATTENDEES_DBSPAM1=5, RCVD_IN_DNSWL_NONE=-0.0001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .yaerobi. - helo: .mail-lf1-x12b.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Gm-Message-State: AOJu0YwzrQZfWyx+fEiw5m+TVW/fAAQRIEzeNMdDl3moRSTtbEniY0P0 WBs2TfT4WESdwFyAxZr5zVRodwLhyUPsaQYXH1tEh9ml3TE8p20YsprbjhnQgecZLqaWRb1Enl3 NlWXel4BF7teSSRUld5tNk3sCj7nlqFawZ8QKXluOn2q3diMxcyc= X-Google-SMTP-Source: AGHT+IFd7dOGDzIWvk3a3zNTKNY+FiwP+nCoA+jBexN/BtXUMya7u+JG0Q2o/QuFTlzN4SzhERw2uC8VU3iJNJwzgq4= X-Received: by 2002:ac2:514d:0:b0:52c:8fe7:ac29 with SMTP id 2adb3069b0e04-52ca6e650cbmr1797491e87.17.1718371549437; Fri, 14 Jun 2024 06:25:49 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000cbfe36061ad98d43" X-Mailing-List: archive/latest/21960 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAFNO5ofDb+3kh0MnuLzk1SiRZchLwzznyPzqk3q41GLkZNQnVw@mail.gmail.com Approved: robomod@news.nic.it Lines: 101 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Fri, 14 Jun 2024 10:25:38 -0300 X-Original-Message-ID: Xref: csiph.com linux.debian.maint.python:15924 --000000000000cbfe36061ad98d43 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi team, Sorry for the subject, this mail is more like questions than given ideas :-). After reading the DPL's contact and its responses, it got me thinking - and this is also a personal feeling - that the DPT is a place where I can seek help. This is beneficial because we understand that if we encounter a Debian packaging issue specific to Python, we can expect a prompt response from experienced people within the team. However, it's true that each one maintains their own packages, while some others fix RC bugs. But IMHO we lack like clear direction to follow as a team. While ultimately, we just need to ensure that the packages under the DPT umbrella are up-to-date with upstream and free of RC bugs as much as possible. I don't know if that 'direction' is needed. I understand that our team's priority is to address 3.12 bugs [0], as mentioned in the irc topic. I know that some people are already working on this, and they don't necessarily need to seek permission before tackling an RC bug. However, perhaps we could attempt to organize our efforts better. Maybe we could identify packages that are candidates for removal like [1] and try to reduce the list of RC bugs. Another question is: what should we do with packages that are not under the team's umbrella but are affecting Python 3.12? On the other hand, we could assess if there are any improvements needed in our tools, such as pybuild, or determine which packages require, for instance, autopkgtests, lintian, etc. Or maybe we can start making short IRC meetings once a week or every two weeks? Experienced members of the team, do you think this is feasible given the DPT workflow? I would like to hear the opinion from the team :-) [0] https://deb.li/3T4QN [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D1025181 cheers, Emmanuel Arias =E2=A2=80=E2=A3=B4=E2=A0=BE=E2=A0=BB=E2=A2=B6=E2=A3=A6=E2=A0=80 =E2=A3=BE=E2=A0=81=E2=A2=A0=E2=A0=92=E2=A0=80=E2=A3=BF=E2=A1=81 eamanu@de= bian.org =E2=A2=BF=E2=A1=84=E2=A0=98=E2=A0=B7=E2=A0=9A=E2=A0=8B=E2=A0=80 OpenPGP: = FA9DEC5DE11C63F1 =E2=A0=88=E2=A0=B3=E2=A3=84 --000000000000cbfe36061ad98d43 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi team,

Sorry for the subject, this mail is more l= ike questions than given ideas
:-).

After reading the DPL's c= ontact and its responses, it got me
thinking - and this is also a person= al feeling - that the DPT is a
place where I can seek help. This is bene= ficial because we understand
that if we encounter a Debian packaging iss= ue specific to Python, we
can expect a prompt response from experienced = people within the team.

However, it's true that each one maintai= ns their own packages, while
some others fix RC bugs. But IMHO we lack l= ike clear direction to follow
as a team. While ultimately, we just need = to ensure that the packages
under the DPT umbrella are up-to-date with u= pstream and free of RC bugs as
much as possible. I don't know if tha= t 'direction' is needed.

I understand that our team's pr= iority is to address 3.12 bugs [0], as
mentioned in the irc topic. I kno= w that some people=C2=A0 are already
working on this, and they don't= necessarily need to seek permission
before tackling an RC bug. However,= perhaps we could attempt to organize
our efforts better. Maybe we could= identify packages that are candidates
for removal like [1] and try to r= educe the list of RC bugs. Another
question is: what should we do with p= ackages that are not under the
team's umbrella but are affecting Pyt= hon 3.12?

On the other hand, we could assess if there are any improv= ements needed
in our tools, such as pybuild, or determine which packages= require, for
instance, autopkgtests, lintian, etc. Or maybe we can star= t making short
IRC meetings once a week or every two weeks? Experienced = members
of the team, do you think this is feasible given the DPT workflo= w? I
would like to hear the opinion from the team :-)
<= div>


[0= ]=C2=A0https://deb.li/3T4QN


cheers,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Emmanuel Arias

=C2=A0=E2=A2=80=E2=A3=B4=E2=A0=BE=E2=A0=BB=E2=A2=B6=E2=A3=A6= =E2=A0=80
=C2=A0=E2=A3=BE=E2=A0= =81=E2=A2=A0=E2=A0=92=E2=A0=80=E2=A3=BF=E2=A1=81=C2=A0 eamanu@debian.org
<= font face=3D"monospace">=C2=A0=E2=A2=BF=E2=A1=84=E2=A0=98=E2=A0=B7=E2=A0=9A= =E2=A0=8B=E2=A0=80=C2=A0 OpenPGP:=C2=A0FA9DEC5DE11C63F1
=C2=A0= =E2=A0=88=E2=A0=B3=E2=A3=84
--000000000000cbfe36061ad98d43--