I want to join the Python-Team to package paperless-ng (#986227) and the needed dependencies under the umbrella of the python team.
I would like to join the Debian Python Team. My salsa handle is "mguenther"
I would like to join the Debian Python Team to package some of my
projects, mainly sphinx-lint [1], but maybe also pospell [2], pogrep
[3], and friends created while translating the Python documentation in french.
</div><div>Why I want to join:</div><div>Themain reason is to contribute the hyfetch package to Debian and maintain
I would like to join the Debian Python team.
On Wednesday, 3 April 2024 15:56:48 CEST Pierre-Elliott Bécue wrote:
I've granted you developer access to the package subgroup. You can
create a shedskin project here if you want.
Many thanks for giving me access! Would it make sense to move the existing project into the Python Team's packages collection on Salsa, or is that only permitted for packages that are actually adopted by the team?
If you lack some access, don't hesitate to reach out for help (we are on
#debian-python on OFTC IRC network).
Don't hesitate after some time and contributions to ask for maintainer
access if you need to create new repos.
One step at a time, I think!
Thanks once again,
Then putting the repo in the team namespace makes sense.
On Wed, Apr 03, 2024 at 04:48:44PM +0200, Paul Boddie wrote:
However, I did not presume that I could just set the Maintainer field in debian/control before applying to join the team, nor did I set any particular headers or metadata in the ITP for shedskin to reference the team, since I thought that this might be impolite. I imagine that I would change the Maintainer as noted in the team policy if the package were to
be adopted within the team.
There is no "adopted within the team" process for packages, so you just
put the repo there and put the team into d/control.
On Wednesday, 3 April 2024 15:56:48 CEST Pierre-Elliott Bécue wrote:If you are going to maintain this package in the team then it can and
I've granted you developer access to the package subgroup. You can
create a shedskin project here if you want.
Many thanks for giving me access! Would it make sense to move the existing project into the Python Team's packages collection on Salsa, or is that only permitted for packages that are actually adopted by the team?
Hello,
I would like to request membership of the Debian Python Team. For a while, I have been working on a package for Shed Skin (shedskin) which is a compiler for a dialect of Python.
I previously maintained a package for this software in the Python 2 era, and since it has been made compatible with Python 3, I feel that it would be beneficial to Debian users to have convenient access to it once again. To this
end, I filed an "intent to package" report a while back:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051352
The principal developer of Shed Skin is very encouraging of packaging efforts
and has been responsive to feedback about issues that might otherwise incur distribution-level patches. Personally, I think that the software deserves more exposure, especially when considering some of the transformative effects
it has on some kinds of Python code:
http://shed-skin.blogspot.com/2024/01/fast-doom-wad-renderer-in-999-lines-of.html
I have sought to follow advice provided in the team policy, making a Salsa project available here:
https://salsa.debian.org/pboddie/shedskin
Building on experience with a previous repository (noted in the ITP report), I
have hopefully managed to follow the branching and pristine-tar guidelines, also introducing test running using Salsa CI.
I have read and accept the policy published here:
https://salsa.debian.org/python-team/tools/python-modules/blob/master/ policy.rst
My Salsa login is pboddie.
Thanks in advance for any guidance that might be offered!
I've bumped your access to maintainer, let's try, and I'll downgrade
when you're done.
I've granted you developer access to the package subgroup. You can
create a shedskin project here if you want.
If you lack some access, don't hesitate to reach out for help (we are on #debian-python on OFTC IRC network).
Don't hesitate after some time and contributions to ask for maintainer
access if you need to create new repos.
On Wednesday, 3 April 2024 16:25:10 CEST Andrey Rakhmatullin wrote:Then putting the repo in the team namespace makes sense.
On Wed, Apr 03, 2024 at 04:21:05PM +0200, Paul Boddie wrote:
Many thanks for giving me access! Would it make sense to move the existing
project into the Python Team's packages collection on Salsa, or is that only permitted for packages that are actually adopted by the team?
If you are going to maintain this package in the team then it can and should be in the team namespace, or are you asking about something else?
My aim is to maintain it in the team, yes.
However, I did not presume that I could just set the Maintainer field in debian/control before applying to join the team, nor did I set any particularThere is no "adopted within the team" process for packages, so you just
headers or metadata in the ITP for shedskin to reference the team, since I thought that this might be impolite. I imagine that I would change the Maintainer as noted in the team policy if the package were to be adopted within the team.
On Wednesday, 3 April 2024 19:03:44 CEST Pierre-Elliott Bécue wrote:
Paul Boddie <paul@boddie.org.uk> wrote on 03/04/2024 at 16:21:05+0200:
Many thanks for giving me access! Would it make sense to move the existing >> > project into the Python Team's packages collection on Salsa, or is that
only permitted for packages that are actually adopted by the team?
On the contrary, please do!
It seems that the "transfer project" function would be the most appropriate way of moving the project, but I don't think I am allowed to perform the transfer. In the settings for my project, the pull-down menu only offers transfer to the "moin" group where I have some other projects.
I reviewed the documentation...
https://salsa.debian.org/help/user/project/settings/migrate_projects#transfer-a-project-to-another-namespace
...and I think that the only obstacle is that I am a developer as opposed to a
maintainer. I suppose that I could re-create the project in the group instead,
if that is more appropriate.
Thanks in advance for any assistance that can be offered, and sorry to bring up such tedious administrative issues!
Hello I am Calvin Mwadime Makokha, with @CalvoM as the salsa login.
I would like to join DPT so that I would help maintain python3-inotify
that is up for adoption.
I would like to join the Debian Python Team to help maintain the python-trezor
package. I am the maintainer of the electrum package, which depends on python-trezor, but the version in Debian is so out-of-date that it is currently non-functional.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062442
I have communicated with Richard Ulrich, the current uploader, who indicated he would appreciate help maintaining the package.
My Salsa login is soren.
I have read have read https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst and accept it.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 349 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 107:41:16 |
| Calls: | 7,612 |
| Calls today: | 3 |
| Files: | 12,786 |
| Messages: | 5,683,108 |
| Posted today: | 2 |