On 2024-06-06 11 h 40 a.m., Andreas Tille wrote:
- Do you feel good when doing your work in Debian Python team?
Yes.
- Do you consider the workload of your team equally shared amongst its
members?
No, and that's perfectly OK? Some people have more time to give than others.
- Do you have some strategy to gather new contributors for your team?
Not really, but I feel that's generally true for Debian at large :) I
think joining an active team is an easier way to start packaging though.
- I guess you will have your regular DPT meeting at DebConf (which I
intend to join). What do you think about the general team meeting
I registered.
I think it's a great idea and I'll be more than happy to join. I've
heard great things about what other teams have been doing in terms of
workflow and practices and I'd like to learn more.
I feel it would be really positive if we could try to work towards a
more standardised set of "team practices" in Debian, to make the general
packaging experience less chaotic.
- In the beginning of this year there was a change in the policy of DPT.
I'd like to hear your opinion about:
* The process how it went (possibly with suggestions to do better)
* The final result after a couple of months
I'm sad that some people left, but then again, I don't think a solution
that suited everyone was possible.
I feel the status quo created a lot of tensions (especially for some
newcomers who made honest mistakes) and as such, I don't think we
could've reached a consensus and believe a vote was necessary.
- Since a long time we try to migrate from Python3.11 to Python3.12.
* What are your thoughts about the transition process?
* Can you identify some blockers?
* Do you have some suggestions for enhancements of this process?
I've said it many times but I really dislike transitions that are near
the release freeze. It forces us into a crunch and I don't think that's
healthy.
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org
⠈⠳⣄
