Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11257 > unrolled thread
| Started by | Faidon Liambotis <paravoid@debian.org> |
|---|---|
| First post | 2019-01-21 13:10 +0100 |
| Last post | 2019-01-28 12:40 +0100 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.debian.maint.python
Request to join the Python team Faidon Liambotis <paravoid@debian.org> - 2019-01-21 13:10 +0100
Re: Request to join the Python team Scott Kitterman <debian@kitterman.com> - 2019-01-25 22:30 +0100
Re: Request to join the Python team Ondrej Novy <novy@ondrej.org> - 2019-01-28 10:50 +0100
Re: Request to join the Python team Scott Kitterman <debian@kitterman.com> - 2019-01-28 12:40 +0100
| From | Faidon Liambotis <paravoid@debian.org> |
|---|---|
| Date | 2019-01-21 13:10 +0100 |
| Subject | Request to join the Python team |
| Message-ID | <xiGyS-ln-13@gated-at.bofh.it> |
Hi, I'd like to be added to the Python team Salsa group (either PAPT, DPMT, or both -- see below). My salsa login is "paravoid". I've prepared multiple updates to the "tox" package, including a (much) newer upstream, and I'd like to be able to push those changes and make an upload to Debian. In terms of experience, I maintain a Python package already (python-maxminddb, under collab-maint) and have sponsored other packages in the past that were maintained by DPMT. I'm actually a bit confused on where "tox" belongs -- Maintainer field seems to be set to PAPT, but in salsa it's under python-modules. It could be argued that it belongs in either, as it's a Python application used to develop and test other Python modules and applications... I actually don't really mind, but I would need access to both groups to be able to move it in Salsa. On that note... what is the Maintainer field supposed to be post-Alioth? For DPMT, I see some packages in the archive with Debian Python Modules Team <team+python-modules@tracker.debian.org> but nothing similar for PAPT. PAPT's page on wiki seems outdated, as is policy.rst on that front. Finally, I've read python-modules policy.rst, and acknowledge that. That said, that policy dictates the use of git-dpm, but Ondřej Nový has already migrated tox to gbp, and I'd rather keep that change. Regards, Faidon
[toc] | [next] | [standalone]
| From | Scott Kitterman <debian@kitterman.com> |
|---|---|
| Date | 2019-01-25 22:30 +0100 |
| Message-ID | <xkhcZ-2c4-7@gated-at.bofh.it> |
| In reply to | #11257 |
I've added you to both DPMT and PAPT. As discussed on IRC, I think PAPT is the right answer for Tox. Scott K On Monday, January 21, 2019 01:17:00 PM Faidon Liambotis wrote: > Hi, > > I'd like to be added to the Python team Salsa group (either PAPT, DPMT, > or both -- see below). My salsa login is "paravoid". > > I've prepared multiple updates to the "tox" package, including a (much) > newer upstream, and I'd like to be able to push those changes and make > an upload to Debian. In terms of experience, I maintain a Python package > already (python-maxminddb, under collab-maint) and have sponsored other > packages in the past that were maintained by DPMT. > > I'm actually a bit confused on where "tox" belongs -- Maintainer field > seems to be set to PAPT, but in salsa it's under python-modules. It > could be argued that it belongs in either, as it's a Python application > used to develop and test other Python modules and applications... I > actually don't really mind, but I would need access to both groups to be > able to move it in Salsa. > > On that note... what is the Maintainer field supposed to be post-Alioth? > For DPMT, I see some packages in the archive with > Debian Python Modules Team <team+python-modules@tracker.debian.org> > but nothing similar for PAPT. PAPT's page on wiki seems outdated, as is > policy.rst on that front. > > Finally, I've read python-modules policy.rst, and acknowledge that. > That said, that policy dictates the use of git-dpm, but Ondřej Nový has > already migrated tox to gbp, and I'd rather keep that change. > > Regards, > Faidon
[toc] | [prev] | [next] | [standalone]
| From | Ondrej Novy <novy@ondrej.org> |
|---|---|
| Date | 2019-01-28 10:50 +0100 |
| Message-ID | <xlbIe-3h0-13@gated-at.bofh.it> |
| In reply to | #11279 |
[Multipart message — attachments visible in raw view] — view raw
Hi, pá 25. 1. 2019 v 22:20 odesílatel Scott Kitterman <debian@kitterman.com> napsal: > I've added you to both DPMT and PAPT. As discussed on IRC, I think PAPT > is > the right answer for Tox. > thanks Scott. > > I'm actually a bit confused on where "tox" belongs -- Maintainer field > > seems to be set to PAPT, but in salsa it's under python-modules. It > > could be argued that it belongs in either, as it's a Python application > > used to develop and test other Python modules and applications... I > > actually don't really mind, but I would need access to both groups to be > > able to move it in Salsa. > tox should be in PAPT and it's: https://salsa.debian.org/python-team/applications/tox python-team/applications = PATP. > > On that note... what is the Maintainer field supposed to be post-Alioth? > > For DPMT, I see some packages in the archive with > > Debian Python Modules Team <team+python-modules@tracker.debian.org> > > but nothing similar for PAPT. PAPT's page on wiki seems outdated, as is > > policy.rst on that front. > current (and only) valid Maintainer/Uploaders field is: Python Applications Packaging Team <python-apps-team@lists.alioth.debian.org > team+python-modules@tracker.debian.org is wrong (even for DPMT). > Finally, I've read python-modules policy.rst, and acknowledge that. > > That said, that policy dictates the use of git-dpm, but Ondřej Nový has > > already migrated tox to gbp, and I'd rather keep that change. > please use gbp for PAPT and DPMT. Policy is a bit outdated, sorry for this. Thank you. -- Best regards Ondřej Nový
[toc] | [prev] | [next] | [standalone]
| From | Scott Kitterman <debian@kitterman.com> |
|---|---|
| Date | 2019-01-28 12:40 +0100 |
| Message-ID | <xldqG-4Jl-9@gated-at.bofh.it> |
| In reply to | #11287 |
On January 28, 2019 9:28:59 AM UTC, Ondrej Novy <novy@ondrej.org> wrote: >Hi, > >pá 25. 1. 2019 v 22:20 odesílatel Scott Kitterman ><debian@kitterman.com> >napsal: > >> I've added you to both DPMT and PAPT. As discussed on IRC, I think >PAPT >> is >> the right answer for Tox. >> > >thanks Scott. > > >> > I'm actually a bit confused on where "tox" belongs -- Maintainer >field >> > seems to be set to PAPT, but in salsa it's under python-modules. It >> > could be argued that it belongs in either, as it's a Python >application >> > used to develop and test other Python modules and applications... I >> > actually don't really mind, but I would need access to both groups >to be >> > able to move it in Salsa. >> > >tox should be in PAPT and it's: >https://salsa.debian.org/python-team/applications/tox > >python-team/applications = PATP. FYI, It's there now because I moved it. At the time he asked it was in DPMT. Thanks for clearing up the maintainer part of the question. Scott K
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web