1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.PYTHON

  • DebConf22 -- Python Team BoF + Sprint?

    From =?UTF-8?Q?Louis-Philippe_V=c3=a9ron@21:1/5 to All on Sun Mar 20 23:00:01 2022
    Hello team!

    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 :)

    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

    I don't think any of this is controversial, but I'll give y'all a few
    days to reply before submitting the talks :)

    [1]: https://debconf22.debconf.org/cfp/
    [2]: https://github.com/sandrotosi/dpt-repos-check/blob/main/violations.txt

    --
    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
    ⢿⡄⠘⠷⠚⠋ pollo@debian.org / veronneau.org
    ⠈⠳⣄

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stefano Rivera@21:1/5 to All on Sat Mar 26 23:10:04 2022
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Louis-Philippe_V=c3=a9ron@21:1/5 to Stefano Rivera on Mon Mar 28 18:20:01 2022
    On 2022-03-26 18 h 02, Stefano Rivera wrote:
    Hi Louis-Philippe (2022.03.20_21:51:45_+0000)
    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.

    I've just submitted the sprint too, the description links to:

    https://wiki.debian.org/DebConf/22/Sprints

    Which links to:

    https://pad.riseup.net/p/dc22pythonsprint-keep

    Please add relevant goals there :)


    --
    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
    ⢿⡄⠘⠷⠚⠋ pollo@debian.org / veronneau.org
    ⠈⠳⣄

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Louis-Philippe_V=c3=a9ron@21:1/5 to All on Wed Jul 6 19:50:01 2022
    On 2022-03-28 12 h 17, Louis-Philippe Véronneau wrote:
    On 2022-03-26 18 h 02, Stefano Rivera wrote:
    Hi Louis-Philippe (2022.03.20_21:51:45_+0000)
    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.

    I've just submitted the sprint too, the description links to:

    https://wiki.debian.org/DebConf/22/Sprints

    Which links to:

    https://pad.riseup.net/p/dc22pythonsprint-keep

    Please add relevant goals there :)

    Hello folks!

    The Python Team BoF has been scheduled on Saturday July 23rd at 14:00.

    https://debconf22.debconf.org/talks/8-python-team-bof/

    As for the sprint, let's meet during DebCamp, on Friday 15th!

    --
    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
    ⢿⡄⠘⠷⠚⠋ pollo@debian.org / veronneau.org
    ⠈⠳⣄

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)