Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #15925

Re: Contacting DPT

From Alexandre Detiste <alexandre.detiste@gmail.com>
Newsgroups linux.debian.maint.python
Subject Re: Contacting DPT
Date 2024-06-14 18:50 +0200
Message-ID <IPihH-2Vet-7@gated-at.bofh.it> (permalink)
References <IMnxf-13EZ-1@gated-at.bofh.it> <IPihH-2Vet-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi,

Le mer. 12 juin 2024 à 16:22, Thomas Goirand <thomas@goirand.fr> a écrit :
> On 6/6/24 17:40, Andreas Tille wrote:
> >    - Do you consider the workload of your team equally shared amongst its
> >      members?
>
> The team probably lacks organization, and there's no clear enough
> strategy for end goals.
>
> I know we're moving toward getting rid of:
> - six
> - mock
> - nose

 and unittest2,
 and zombie-imp,
 and 2to3,
 and cython3-legacy
 and m2r
 and mistune0
 and ...

Even only listing all of these on wiki with
what they could be replaced with would be good starter.

We could rely on the standard transition tracker to see what remains:
   https://release.debian.org/transitions/
or having those get from FTP-Masters an "oldlibs" overide.

I've my own tracker but it's mostly a toy I build to see what could be
done with UDD
and playing around with matplotlib.

An optimal moment to check whether these old dependencies
can be removed seems to be when a new upstream is available.

(m = mock, n=nose, s=six)
$ cat snap
androguard                     m         (depends on Java stuff..)
backblaze-b2                   m n s   (huge)
elasticsearch-curator          m n   (depends on new spun out library too ITP)
fabric                           n               (I tried)
heudiconv                      m            (attempted uploaded to experimental)
mu-editor                      m             (discussion on mailing
list about packaging style went nowhere)
pagure                         m   s

Now I think I could sort this by upstream release date & make an RSS
out of it ;-)


> but is anyone doing any type of coordination for the work to be done ?

I guess people being members of several Teams could give precious help.
I don't see myself pledging to join Teams just to remove
a handful lines from d/control files, and then be gone forever.

> It's been a waaaaay too long.
Agree

Greetings

Back to linux.debian.maint.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Contacting DPT Andreas Tille <tille@debian.org> - 2024-06-06 17:50 +0200
  Re: Contacting DPT Andrey Rakhmatullin <wrar@debian.org> - 2024-06-06 18:50 +0200
  Re: Contacting DPT Scott Kitterman <debian@kitterman.com> - 2024-06-07 06:10 +0200
    Re: Contacting DPT Emmanuel Arias <eamanu@debian.org> - 2024-06-11 21:30 +0200
  Re: Contacting DPT Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-06-14 18:50 +0200
    Re: Contacting DPT Emmanuel Arias <eamanu@debian.org> - 2024-06-20 07:00 +0200
      Re: Contacting DPT Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-06-20 07:10 +0200
  Re: Contacting DPT Louis-Philippe Véronneau <pollo@debian.org> - 2024-06-17 08:10 +0200

csiph-web