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

Debian Python Team Sprint

Path	csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod
From	Emmanuel Arias <eamanu@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Debian Python Team Sprint
Date	Sat, 03 Aug 2024 06:50:01 +0200
Message-ID	<J7eSl-2lFq-19@gated-at.bofh.it> (permalink)
X-Original-To	Debian Python Team List <debian-python@lists.debian.org>
X-Mailbox-Line	From debian-python-request@lists.debian.org Sat Aug 3 04:49:50 2024
Old-Return-Path	<eamanu@debian.org>
X-Amavis-Spam-Status	No, score=-114.01 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, CAPINIT=0.5, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no
MIME-Version	1.0
Content-Type	multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="pPERp/cJtzYufmK4"
Content-Disposition	inline
X-Debian-User	eamanu
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/22206
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/Zq221Uj8iztMClXh@eamanu
Approved	robomod@news.nic.it
Lines	52
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Sat, 3 Aug 2024 01:49:25 -0300
X-Original-Message-ID	<Zq221Uj8iztMClXh@eamanu>
Xref	csiph.com linux.debian.maint.python:16168

Show key headers only | View raw

[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!

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

Thread

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

csiph-web