Path: csiph.com!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Stefano Rivera Newsgroups: linux.debian.maint.python Subject: Re: DebConf22 -- Python Team BoF + Sprint? Date: Sat, 26 Mar 2022 23:10:04 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sat Mar 26 22:03:09 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.672 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.831, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_FROM_MX=-3.1; rate: -4.6 Mail-Followup-To: debian-python@lists.debian.org X-Gpg-Public-Key: http://www.rivera.za.net/stefano.gpg MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: NeoMutt/20201127 X-Mailing-List: archive/latest/19837 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20220326220253.ftrwubm6qolx2rz6@satie.tumbleweed.org.za Approved: robomod@news.nic.it Lines: 31 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sat, 26 Mar 2022 22:02:53 +0000 X-Original-Message-ID: <20220326220253.ftrwubm6qolx2rz6@satie.tumbleweed.org.za> X-Original-References: Xref: csiph.com linux.debian.maint.python:14015 Hi Louis-Philippe (2022.03.20_21:51:45_+0000) > The DebConf22 content team has issued a call for papers [1]. As I'm > planning to be there this year, I'd be happy to send a proposal for our > annual BoF :) Yes, please (and I can see that you've submitted it, thanks!) > I think it would also be neat to have a team sprint during DebCamp. Here > are a few ideas of things we could work on: > > * pybuild improvements (getting the autopkgtest MR in would be great) > * general team QA (maybe based on [2]?) > * lintian tags used for the team +1 to a sprint, as usual. I think upstream cpython would also appreciate it if we did a pass through all of our cpython patches and ensured they were forwarded. Ping bugs, etc. Same goes for any core libraries / big packages. I've attempted to document them all, this year, which is a start. But only a start. In many cases forwarding the patch would require clearly defining the bug, writing reproducer scripts, etc. I'd happily mentor people in working on this. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272