place where I can seek help. This is beneficial because we understand<br>that if we encounter a Debian packaging issue specific to Python, we<br>can expect a prompt response from experienced people within the team.<br><br>However, it's true thateach one maintains their own packages, while<br>some others fix RC bugs. But IMHO we lack like clear direction to follow<br>as a team. While ultimately, we just need to ensure that the packages<br>under the DPT umbrella are up-to-date with upstream and
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=1025181
I agree with the points you raise. It's true the DPT isn't a very organised entity (although there's much worse teams in Debian :9).
I think more would be possible if we were more organised. Having regular meetings would surely help.
On my side though, I sadly don't have time for that. I'm already part of plenty of Teams in Debian (some of which do have regular meetings, like the DebConf Videoteam) and I only have so many spoons... If others want to push this way, I'll root for you!
That said, if I had more time, I would probably prioritise reviewing and sponsoring more DPT packages, something I haven't done in a while.
Hi,
Am Mon, Jun 17, 2024 at 02:07:55AM -0400 schrieb Louis-Philippe Vronneau:
Another
question is: what should we do with packages that are not under the team's umbrella but are affecting Python 3.12?
Salvage[2] those packages?
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=1025181
I agree with the points you raise. It's true the DPT isn't a very organised entity (although there's much worse teams in Debian :9).
I agree as well (with both ;-) )
I think more would be possible if we were more organised. Having regular meetings would surely help.
Possibly IRC meetings (as far as I know Perl team is doing so) might be
some first step.
On my side though, I sadly don't have time for that. I'm already part of plenty of Teams in Debian (some of which do have regular meetings, like the DebConf Videoteam) and I only have so many spoons... If others want to push this way, I'll root for you!
+1
That said, if I had more time, I would probably prioritise reviewing and sponsoring more DPT packages, something I haven't done in a while.
I'd also recommend the "advent bug squashing party" done by the Debian
Med team. We do team wide bug squashing from Dezember 1st - 24th and everybody tries to squash a personal bug of the day (no matter who is Uploader of the package).
Kind regards
Andreas.
[2] https://wiki.debian.org/PackageSalvaging
--
https://fam-tille.de
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 350 |
Nodes: | 16 (2 / 14) |
Uptime: | 10:29:58 |
Calls: | 7,625 |
Files: | 12,793 |
Messages: | 5,686,539 |