Hi, Le mer. 12 juin 2024 à 16:22, Thomas Goirand <tho...@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
