Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #16168 > unrolled thread
| Started by | Emmanuel Arias <eamanu@debian.org> |
|---|---|
| First post | 2024-08-03 06:50 +0200 |
| Last post | 2024-08-04 14:30 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.maint.python
Debian Python Team Sprint Emmanuel Arias <eamanu@debian.org> - 2024-08-03 06:50 +0200
Re: Debian Python Team Sprint Mechtilde <ooo@mechtilde.de> - 2024-08-04 13:20 +0200
Re: Debian Python Team Sprint Andrey Rakhmatullin <wrar@debian.org> - 2024-08-04 14:30 +0200
| From | Emmanuel Arias <eamanu@debian.org> |
|---|---|
| Date | 2024-08-03 06:50 +0200 |
| Subject | Debian Python Team Sprint |
| Message-ID | <J7eSl-2lFq-19@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hi Team, As it was proposed during the Python BoF at DebConf24, it would be nice to try a "one day sprint" each 2 weeks. It would help us work on fixing bug reports and IMO it will be great for newcomers as well. This would also remove the timezone issues we've been having for the irc/live meeting. Now we have the issue to decide when we will start with the periodical sprints. The other point we need to decide is if we should have an approach of free bugs fixing, or if it's better to create a list of goals for the sprint. I prefer the last idea, as it will help us keep metrics on the work done during these sprints. One day sprint each 2 weeks would be a hard workload, so I will propose you a sprint with a duration of 2 weeks. It can not be too much different as we work, but having goals for a sprint can motivate people. If you have a list of bugs to propose, you can send it to the list. I think working to remove dead modules [0] could be a good start. Obviously we could work on RC bugs too. Also, during the Python BoF it was decided to work in provide current best-practice documentation on the wiki. [0] https://wiki.debian.org/Python/Dead%20Batteries Cheers!
[toc] | [next] | [standalone]
| From | Mechtilde <ooo@mechtilde.de> |
|---|---|
| Date | 2024-08-04 13:20 +0200 |
| Message-ID | <J7Hrj-2E35-7@gated-at.bofh.it> |
| In reply to | #16168 |
[Multipart message — attachments visible in raw view] — view raw
+1 I will be there as often as possible Am 03.08.24 um 06:49 schrieb Emmanuel Arias: > Hi Team, > > As it was proposed during the Python BoF at DebConf24, it would be nice > to try a "one day sprint" each 2 weeks. It would help us work on fixing bug reports > and IMO it will be great for newcomers as well. > > This would also remove the timezone issues we've been having for the irc/live meeting. > Now we have the issue to decide when we will start with the periodical sprints. > > The other point we need to decide is if we should have an approach of free bugs fixing, > or if it's better to create a list of goals for the sprint. I prefer the last idea, as > it will help us keep metrics on the work done during these sprints. > > One day sprint each 2 weeks would be a hard workload, so I will propose you a sprint > with a duration of 2 weeks. It can not be too much different as we work, but having > goals for a sprint can motivate people. > > If you have a list of bugs to propose, you can send it to the list. I think working > to remove dead modules [0] could be a good start. Obviously we could work on RC bugs > too. Also, during the Python BoF it was decided to work in provide current > best-practice documentation on the wiki. > > [0] https://wiki.debian.org/Python/Dead%20Batteries > > Cheers! -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
[toc] | [prev] | [next] | [standalone]
| From | Andrey Rakhmatullin <wrar@debian.org> |
|---|---|
| Date | 2024-08-04 14:30 +0200 |
| Message-ID | <J7Ix3-2EFT-1@gated-at.bofh.it> |
| In reply to | #16168 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, Aug 03, 2024 at 01:49:25AM -0300, Emmanuel Arias wrote: > The other point we need to decide is if we should have an approach of free bugs fixing, > or if it's better to create a list of goals for the sprint. I prefer the last idea, as > it will help us keep metrics on the work done during these sprints. In any case we should have a list of ideas for people who want to work but don't have a specific bug in mind. -- WBR, wRAR
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web