Re: Joining the team! Again with policy acceptance.

[Scott Kitterman]

On Sunday, March 5, 2023 12:51:59 PM EST Scarlett Moore wrote:
> Hi!
> My name is Scarlett Moore, I have been working on https://salsa.debian.org/
> mycroftai-team which consists of many python packages relating to voice AI.
> Mycroft is no more, but forked. I would like to move these packages to the
> python umbrella so as to be useful everywhere and of course consistency,
> team maintained. I will of course continue maintaining and not dump them
> here, I will also help elsewhere as needed.
> I have read and accept
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/polic
> y.rst My salsa ID is @sgmoore.
> Thank you for your consideration,
> Scarlett

Welcome to the team.

Scott K

signature.asc
Description: This is a digitally signed message part.

Re: Joining the team

[Antonio Valentino]

Hi Sebastiaan,

Il 23/12/22 14:16, Sebastiaan Couwenberg ha scritto:
Please add sebastic to the team on Salsa, I'd like to help by pushing 
commits for packages maintained in the team that are part of the 
dependency chain of the packages I help maintain.


Case in point: python-numpy-groupies (#1026885)

I have read and accept the team policy.

Kind Regards,

Bas



I have some work done for numpy_groupies in 
https://salsa.debian.org/antonio.valentino/numpy-groupies.



cheers
--
Antonio Valentino

Re: Joining the team

[Stefano Rivera]

Hi Sebastiaan (2022.12.23_13:16:38_+)
> Please add sebastic to the team on Salsa, I'd like to help by pushing
> commits for packages maintained in the team that are part of the dependency
> chain of the packages I help maintain.

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team to maintain pydrive

[Stefano Rivera]

Hi Sebastien (2022.12.09_12:18:38_+)
> I would like to add pydrive [1]  to Debian (I'm currently maintaining it for
> Ubuntu as a opt-depends of deja-dup to be able to back-up on gdrive). I
> think it makes sense for it to be under the python team umbrella.
> I might occasionally contribute to updates or fixes on desktop components
> maintained by the team.

Added. Welcome to the team!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team

[Stefano Rivera]

Hi Marcin (2022.10.20_06:56:35_+)
> I want to join the team to maintain a new package, ledgerhelpers [1]
> within the team.
> My Salsa login is porridge

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team

[Stefano Rivera]

Hi Andrea (2022.09.24_10:09:26_+)
> I'm [currently packaging][1] a C++ library which depends on [Poxy], a
> documentation generator currently not packaged by Debian. I don't know much
> about Python (I especially don't know anything about its ecosystem), so I
> believe that joining the team is a good way to learn a bit how to package
> Python programs.

Added, welcome.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team

[Stefano Rivera]

Hi Emanuele (2022.08.29_19:39:17_+)
> I'd like to join the debian-python team to help with general QA work on
> all packages.
> 
> My salsa login is ema.

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team

[Stefano Rivera]

Hi Matt (2022.07.17_23:21:03_+)
> I am interested in joining the Python team, or at least helping out a
> bit if I can.  I work a lot with Python, and I'm currently maintaining
> a tiny module (python-decouple) and working on a second (python-
> public).. my non-Python experience in Debian includes a bunch of perl
> in the latest adduser. :)

Added, sorry about the delay. Welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team

[Stefano Rivera]

Hi Ben (2022.06.01_20:42:21_+)
> I sent this message to the mailing list over a month ago and also asked
> about it on IRC, getting no response from either platform. The Wiki says
> this is how I join the team, so I'm just sending it again.

Sorry about the delay. Welcome to the team!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: joining the team

[Stefano Rivera]

Hi Salman (2021.05.24_10:55:23_+)
> I would like to join the team and help maintaining *prospector* package
> which has been removed from Stable and Testing but is still in Sid in a
> broken state.

Added, welcome.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team

[Stefano Rivera]

Hi Pablo (2021.05.21_03:17:57_+)
> I'm Pablo Mestre, currently I maintein 4 packages in Debian[1]. I'd like
> to join the Debian Python team partly to help maintain the packages
> colortest-python[2] and python-language-server[3].

Added, welcome!

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team

[Stefano Rivera]

Hi Dave (2021.05.20_16:56:59_+)
> I'm Dave Jones, currently at Canonical where I work on Raspberry Pi related
> things. I'm also the author of / contributor to a few (largely Pi related)
> Python packages, including gpiozero (which is currently in Debian). I'd like
> to join the Debian Python team partly to help maintain the packages where
> I'm involved with the upstream (such as gpiozero), and partly in the hopes
> of helping get some of the Python packages which only exist in Raspbian
> upstream to Debian.

Added, welcome.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team request

[Stefano Rivera]

Hi Anton (2021.04.07_21:07:15_+)
> I want to update some packages (for example astral - sure, respecting the
> release policy) and also add some newer ones. I have read [1] and accept it. 
> My
> salsa-login is gladk.

Added, welcome to the team.

> Please give me maintainer-permissions, so I will be able to setup CI-pipelines
> for packages which I touch.

Yeah, that's the standard level for the python team.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team

[Stefano Rivera]

Hi Stephan (2021.05.06_21:27:11_+)

> My Salsa login is stephanlachnit.
> 
> I have read the policy and accept it.

Added to the Salsa project.

Welcome to the team.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team request

[Anton Gladky]

Friendly reminder.

Anton


Am Mi., 7. Apr. 2021 um 23:07 Uhr schrieb Anton Gladky :

> Hi,
>
> Please add me to the python-team.
>
> I want to update some packages (for example astral - sure, respecting the
> release policy) and also add some newer ones. I have read [1] and accept
> it. My
> salsa-login is gladk.
>
> Please give me maintainer-permissions, so I will be able to setup
> CI-pipelines
> for packages which I touch.
>
> Thank you
>
> [1]
> https://salsa.debian.org/python-team/tools/python-modules/blob/maste/policy.rst
>
>
> Anton
>

Re: joining the team

[Ondrej Novy]

Hi,

st 3. 3. 2021 v 21:28 odesílatel Daniel Milde  napsal:

> I would like to join the Python team.
>

welcome :)

-- 
Best regards
 Ondřej Nový

Re: Joining the team

[nicoo]

On Sun, Jan 31, 2021 at 06:32:14PM -0500, Sandro Tosi wrote:
> > > Added!
> please name the project as the source package name, not "Easy Ansi"

Thanks for the catch; I didn't realise Gitlab was “smart” about turning the
repository's path stub into a project name.

Now fixed.


signature.asc
Description: PGP signature

Re: Joining the team

[nicoo]

On Sun, Jan 31, 2021 at 05:39:49PM +0100, nicoo wrote:
> Yes, my intent was to go for strong team maintenance (teamwork makes the
> dream work!) but my sleep-deprived self thought I was in the team already.

I just noticed I originally did exactly the reverse of what I meant to,
but it will be fixed shortly (merging and uploading tonight or tomorrow)


signature.asc
Description: PGP signature

Re: Joining the team

[Sandro Tosi]

> > Added!
> >
> > Happy package maintenance :)
>
> Thanks  <3

please name the project as the source package name, not "Easy Ansi"
https://salsa.debian.org/python-team/packages/easy-ansi; also
src:python-easy-ansi, the python- prefix is not strictly required --
anyhow, the salsa project name should match what source package name
you decide to set. please fix Easy Ansi

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Re: Joining the team

[Stefano Rivera]

Hi Louis-Philippe (2021.01.31_21:43:48_+)
> > whether it's fine to enable branch/tag protection
> 
> Nothing on that either.

When we imported packages we set this up. But haven't automated managing
it on all / new packages, yet. (The tools for automation didn't exist at
the time)

> > adding webhooks to tag BTS bugs as pending when a fix is merged
> 
> AFAIK, you don't need to add webhooks for that to work, something (I
> don't know what) scans through all new commits on Salsa and checks for
> relevant BTS info.

As I understood it, that's the tagpending webhook, which we have set up
on all our repos, at import time.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team

[Louis-Philippe Véronneau]

On 2021-01-31 15 h 25, nicoo wrote:
> In particular the CI setup (the usual pipeline?)

Nothing on that, since the Salsa Team has asked us not to use CI
systematically because Salsa CI apparently cannot take the load.

> whether it's fine to enable branch/tag protection

Nothing on that either.

> working through MRs

You're free to ask for MRs, no team policy on this.

> adding webhooks to tag BTS bugs as pending when a fix is merged

AFAIK, you don't need to add webhooks for that to work, something (I
don't know what) scans through all new commits on Salsa and checks for
relevant BTS info.

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



OpenPGP_signature
Description: OpenPGP digital signature

Re: Joining the team

[nicoo]

Hi Stefano,

On Sun, Jan 31, 2021 at 06:19:00PM +, Stefano Rivera wrote:
> Hi nicoo (2021.01.31_16:39:43_+)
> > > cool! Please follow our policy:
> > > https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
> > > to join the team.
> > 
> > I've read and accepted the policy, my login is nicoo, and I mentionned in
> > the previous emails my motivation for joining the team.
> 
> Added!
> 
> Happy package maintenance :)

Thanks  <3


Speaking of the policy, are there conventions about repository setup,
beyond complying with DEP-14? In particular the CI setup (the usual
pipeline?), whether it's fine to enable branch/tag protection and require
working through MRs, adding webhooks to tag BTS bugs as pending when a fix
is merged, ...


Best,

  nicoo


signature.asc
Description: PGP signature

Re: Joining the team

[Stefano Rivera]

Hi nicoo (2021.01.31_16:39:43_+)
> > cool! Please follow our policy:
> > https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
> > to join the team.
> 
> I've read and accepted the policy, my login is nicoo, and I mentionned in
> the previous emails my motivation for joining the team.

Added!

Happy package maintenance :)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team

[nicoo]

Hi Ondrej!

Sorry for the super-late reply, I've been pretty broken in the last couple
of months, unfortunately. I'm trying to take care of myself, though, and
things seem to be looking up over the last few days :3


On Mon, Nov 30, 2020 at 12:32:04PM +0100, Ondrej Novy wrote:
> it's up to you to choose if you want to have strong or weak team
> maintenance.  If you are fine with the Python team members uploading,
> use strong - use team in the Maintainer field.

Yes, my intent was to go for strong team maintenance (teamwork makes the
dream work!) but my sleep-deprived self thought I was in the team already.


> po 23. 11. 2020 v 14:15 odesílatel nicoo  napsal:
> > Second, I would like to join the team  ^.^
>
> cool! Please follow our policy:
> https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
> to join the team.

I've read and accepted the policy, my login is nicoo, and I mentionned in
the previous emails my motivation for joining the team.


Best,

  nicoo  <3


signature.asc
Description: PGP signature

Re: Joining the team

[Stefano Rivera]

Hi Aron (2020.12.27_18:35:29_+)
> I'd like to join the team to maintain some new packages, namely 
> python3-easydict
> and python3-astunparse, which are dependencies of my other package. I believe
> the two packages are more suitable to be maintained in this team, rather than 
> a
> field specific team.

Added, welcome :)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team request for salsa user microjoe-guest

[Romain Porte]

Hi,

2020-12-02 12:50 CET, Romain Porte:
> In order to publish some Python packages that will act as dependencies
> to packages for font management, I would like to join the fonts team.
>
> [...]
>
> I have read the current python-team policy [1] and agree with its terms.
> [1] 
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Gentle reminder to provide me access to python-debian on salsa
for new repository creation.

I have currently 3 packages waiting on mentors.d.n to have the
following repositories created to reserve their names before upload:

 * python-absl
 * python-strictyaml
 * python-vttlib

If access cannot be provided on salsa, I will have to create the
Vcs repositories in my own salsa namespace and remove debian-python@
from the maintainers list of these packages. I would like to avoid this
situation.

> My salsa login is "microjoe-guest".

My login has now be moved to "microjoe", as "-guest" suffix are not
mandatory anymore for non-DD/DM.

Best regards,

Romain.


signature.asc
Description: PGP signature

Re: Joining the team request for salsa user microjoe-guest

[Stefano Rivera]

Hi Romain (2020.12.02_11:50:22_+)
> In order to publish some Python packages that will act as dependencies
> to packages for font management, I would like to join the fonts team.

And the python team, presumably :)

> My salsa login is "microjoe-guest".

Guessing you meant "microjoe".

Added, welcome.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team, ITP and RFS

[Ondrej Novy]

Hi Juhani,

pá 27. 11. 2020 v 17:55 odesílatel Juhani Numminen <
juhaninummin...@gmail.com> napsal:

> Hi!
>
> I'd like to join the Debian Python Team


welcome :)


> Also, I would like to ask for a new git repository for the package.
> Would you mind creating one in the standard location
> https://salsa.debian.org/python-team/packages/python-pysol-cards?
>

the name of the repository should be the same as the source package name.
If that's correct, you can create that repository yourself now.

-- 
Best regards
 Ondřej Nový

Re: Joining the team

[Ondrej Novy]

Hi nicoo,

po 23. 11. 2020 v 14:15 odesílatel nicoo  napsal:

> First, an apology: it seems I misremembered being in the team, and
> uploaded to
> NEW a bunch of packages with the team in `Uploaders`.  While I guess that's
> technically valid (I'm fine with the Python team uploading to them), I am
> not
> exactly comfortable with having done so without being a team member or
> clearing
> it first with you all.
>

it's up to you to choose if you want to have strong or weak team
maintenance.
If you are fine with the Python team members uploading, use strong -
use team in the Maintainer field.

Second, I would like to join the team  ^.^
>

cool! Please follow our policy:
https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
to join the team.

Thanks.

-- 
Best regards
 Ondřej Nový

Re: Joining the team

[Brian May]

Thomas Goirand  writes:

> Because joining a team, putting packages in them, and enforcing strong
> ownership, is not logic at all. I know you like to do this way, but this
> shouldn't be what we advise for new comers.

Agreed. In my opinion what the policy allows and what is best practise
are two different things.

If you want strong ownership, you can get that already by not having the
package part of the team. To invite people to do so as part of the
Debian policy just makes the policy more complicated (and confusing)
then it needs to be. And creates needless conflicts within our team.

Depending on what you want, You are also free to follow the packaging
guidelines, policies, etc, even if the package isn't formally part of
the team. You could even join this group
https://wiki.debian.org/LowThresholdNmu and allow others to make changes
to your packages without going through the slow NMU process.
-- 
Brian May 

Re: Joining the team

[Sandro Tosi]

On Mon, Nov 23, 2020 at 6:50 PM Thomas Goirand  wrote:
>
> On 11/23/20 10:10 PM, Sandro Tosi wrote:
> >>> First, an apology: it seems I misremembered being in the team, and 
> >>> uploaded to
> >>> NEW a bunch of packages with the team in `Uploaders`.
> >>
> >> Please put the team as Maintainer, and yourself as Uploaders.
> >
> > why? that's not a requirement:
> > https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#maintainership
>
> Because joining a team, putting packages in them, and enforcing strong
> ownership, is not logic at all.

that's your opinion, and the policy disagrees with you. this team
welcomes everyone that is willing to follow our policies and its
rules.

> I know you like to do this way, but this
> shouldn't be what we advise for new comers.

that's also what nicoo prefers, given he chose exactly that way for
maintaining his packages.

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Re: Joining the team

[Thomas Goirand]

On 11/23/20 10:10 PM, Sandro Tosi wrote:
>>> First, an apology: it seems I misremembered being in the team, and uploaded 
>>> to
>>> NEW a bunch of packages with the team in `Uploaders`.
>>
>> Please put the team as Maintainer, and yourself as Uploaders.
> 
> why? that's not a requirement:
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#maintainership

Because joining a team, putting packages in them, and enforcing strong
ownership, is not logic at all. I know you like to do this way, but this
shouldn't be what we advise for new comers.

Cheers,

Thomas Goirand (zigo)

Re: Joining the team

[Sandro Tosi]

> > First, an apology: it seems I misremembered being in the team, and uploaded 
> > to
> > NEW a bunch of packages with the team in `Uploaders`.
>
> Please put the team as Maintainer, and yourself as Uploaders.

why? that's not a requirement:
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#maintainership

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Re: Joining the team

[Thomas Goirand]

On 11/23/20 2:15 PM, nicoo wrote:
> Hi everyone!
> 
> First, an apology: it seems I misremembered being in the team, and uploaded to
> NEW a bunch of packages with the team in `Uploaders`.

Please put the team as Maintainer, and yourself as Uploaders.

Cheers,

Thomas Goirand (zigo)

Re: Joining the team

[chris . macnaughton]

> 
> welcome :)
> 
Thanks!
Chris

Re: Joining the team

[Ondrej Novy]

Hi,

st 30. 9. 2020 v 14:25 odesílatel Chris MacNaughton <
chris.macnaugh...@canonical.com> napsal:

> - I want to join the python-modules team so that I can help improve both
> Debian and Ubuntu's stance with python dependencies for OpenStack!
>

welcome :)

-- 
Best regards
 Ondřej Nový

Re: Joining the team

[Chris MacNaughton]

On 24-09-2020 16:33, Ondrej Novy wrote:
> that's cool! Please follow policy how to join
> team: 
> https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst
> 
>  

Hey!

- I want to join the python-modules team so that I can help improve both
Debian and Ubuntu's stance with python dependencies for OpenStack!
- I am icey (https://salsa.debian.org/icey) on Salsa
- I have read and accept
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst

Thanks!
Chris "icey" MacNaughton



OpenPGP_0x74BAF13D12E6A841.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Re: Joining the team

[Ondrej Novy]

Hi,

po 14. 9. 2020 v 8:11 odesílatel Chris MacNaughton <
chris.macnaugh...@canonical.com> napsal:

> Hey team,
>
> I'm Chris MacNaughton (icey) and I've been working on packaging for
> OpenStack in Ubuntu for about six months now and would love to help
> contribute upstream a bit. I'm working on a new package that's an
> OpenStack dependency now and would prefer to work that more in Debian,
> rather than maintaining a separate library in Ubuntu so it seems like a
> great time to get in touch! Zigo asked me to see about joining this team
> if I'll be working on doing these kinds of things upstream so here I am!
>

that's cool! Please follow policy how to join team:
https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst

Thank you.

-- 
Best regards
 Ondřej Nový

Re: Joining the team (again)

[Scott Kitterman]

On Sunday, March 1, 2020 2:53:13 PM EST Georg Faerber wrote:
> Dear all,
> 
> I was part of the team in the past as 'georg-guest', I would like to
> join again as 'georg'. I do maintain anorack and mwic.
> 
> I've read the team policy and accept it.
> 
> Thanks,
> Georg

Welcome back.

Scott K

signature.asc
Description: This is a digitally signed message part.

Re: Joining the team

[Stefano Rivera]

Hi Georg (2019.05.28_13:04:24_+0200)
> I became a DD now, could someone please add my new account "georg" to
> the team?

Done. Sorry about the delay.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: Joining the team

[Georg Faerber]

Hi,

On 18-03-15 22:04:39, Georg Faerber wrote:
> I would like to join the team.
> 
> I'm intending to package mwic [1], Misspelled Words In Context, which
> is a spell-checker that groups possible misspellings and shows them in
> their contexts. This is useful for checking technical documents that
> often contain words that are not included in standard dictionaries.
> The upstream author is Jakub Wilk.
> 
> I maintain some packages [2], and became a DM recently [3].
> 
> I'm "georg-guest" on salsa.d.o.
> 
> I've read the team policy and accept it.
> 
> [...]
> 
> [1] https://jwilk.net/software/mwic
> [2] https://qa.debian.org/developer.php?login=georg%40riseup.net
> [3] https://nm.debian.org/process/419

I became a DD now, could someone please add my new account "georg" to
the team?

Thanks,
cheers,
Georg


signature.asc
Description: PGP signature

Re: Joining the team

[Ondrej Novy]

Hi,

2018-04-18 17:31 GMT+02:00 Joel Cross :
>
> ...  it has been suggested that I join this team.


welcome :)

-- 
Best regards
 Ondřej Nový

Email: n...@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B

Re: Joining the team

[Piotr Ożarowski]

[Georg Faerber, 2018-03-15]
> I would like to join the team.
> 
> I'm intending to package mwic [1], Misspelled Words In Context, which is
> a spell-checker that groups possible misspellings and shows them in
> their contexts. This is useful for checking technical documents that
> often contain words that are not included in standard dictionaries. The
> upstream author is Jakub Wilk.
> 
> I maintain some packages [2], and became a DM recently [3].
> 
> I'm "georg-guest" on salsa.d.o.

welcome :)

> I've read the team policy and accept it.
-- 
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Re: Joining the team

[Georg Faerber]

On 18-03-15 22:04:39, Georg Faerber wrote:
> Hi all,
> 
> I would like to join the team.
> 
> I'm intending to package mwic [1], Misspelled Words In Context, which
> is a spell-checker that groups possible misspellings and shows them in
> their contexts. This is useful for checking technical documents that
> often contain words that are not included in standard dictionaries.
> The upstream author is Jakub Wilk.
> 
> I maintain some packages [2], and became a DM recently [3].
> 
> I'm "georg-guest" on salsa.d.o.
> 
> I've read the team policy and accept it.
> 
> Thanks in advance,
> cheers,
> Georg
> 
> 
> [1] https://jwilk.net/software/mwic
> [2] https://qa.debian.org/developer.php?login=georg%40riseup.net
> [3] https://nm.debian.org/process/419

Friendly ping. mwic is by now in NEW, and I would like to move the repo.

Thanks,
cheers,
Georg


signature.asc
Description: Digital signature

Re: Joining the team

[Ghislain Vaillant]

On Sat, 2017-05-20 at 17:40 +0200, sab wrote:
> 
> On 07/05/2017 17:30, sab wrote:
> > 
> > On 06/05/2017 17:14, Piotr Ożarowski wrote: 
> > > [sab, 2017-05-06] 
> > > > 'https://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/':
> > > >  
> > >  git+ssh://git.debian.org/git/python-modules/packages/python-zxcvbn.git 
> >  Thanks 
> > I have pushed on 
> > git+ssh://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/
> > for all branches. 
> > Now who sponsors the changes? 
> > Regards, 
> > Sabino 
> > 
>  
> Hi!
> How do I make package accepted into experimental?
> https://anonscm.debian.org/cgit/python-modules/packages/python-zxcvbn.git/
> Regards,
> Sabino

You need to request sponsorship for uploading your package [1]. Then,
an interested sponsor should review your packaging and may ask for
further improvement to it prior to the upload.

[1] https://mentors.debian.net/sponsor/rfs-howto

Ghis

Re: Joining the team

[sab]

On 07/05/2017 17:30, sab wrote:



On 06/05/2017 17:14, Piotr Ożarowski wrote:

[sab, 2017-05-06]
'https://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/': 


git+ssh://git.debian.org/git/python-modules/packages/python-zxcvbn.git

Thanks
I have pushed on 
git+ssh://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/

for all branches.
Now who sponsors the changes?
Regards,
Sabino



Hi!

How do I make package accepted into experimental?

https://anonscm.debian.org/cgit/python-modules/packages/python-zxcvbn.git/

Regards,

Sabino

Re: Joining the team

[sab]

On 06/05/2017 17:14, Piotr Ożarowski wrote:

[sab, 2017-05-06]

'https://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/':

git+ssh://git.debian.org/git/python-modules/packages/python-zxcvbn.git

Thanks
I have pushed on 
git+ssh://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/

for all branches.
Now who sponsors the changes?
Regards,
Sabino

Re: Joining the team

[Piotr Ożarowski]

[sab, 2017-05-06]
> 'https://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/':

git+ssh://git.debian.org/git/python-modules/packages/python-zxcvbn.git
-- 
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Re: Joining the team

[sab]

Hi!


On 19/04/2017 23:07, sab wrote:

Hi!


On 10/04/2017 16:44, Barry Warsaw wrote:

On Apr 09, 2017, at 01:13 PM, sab wrote:


https://mentors.debian.net/package/python-zxcvbn

with DPMT as uploader. What's my next step? Have I to create a Git 
repository?

Welcome to the team Sabino.

You'll want to take a look at these two wiki pages.  First is the 
style guide

for DPMT packages.

https://wiki.debian.org/Python/LibraryStyleGuide

The second is our git packaging workflow:

https://wiki.debian.org/Python/GitPackaging

but note that we are still discussing the move away from git-dpm to 
git-pq for

patch queue management.  When that actually happens we'll use:

https://wiki.debian.org/Python/GitPackagingPQ

as a guideline.

Cheers,
-Barry

How can I have permissions to push in git branches: master,upstream or 
pristine-tar?


Regards,
Sabino


I updated all branches: master,upstram and prostine-tar, but I can't push:
git push
fatal: unable to access 
'https://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/': 
The requested URL returned error: 403

What could i do?

Regards,
Sabino

Re: Joining the team

[sprawl]

Hi!


On 10/04/2017 16:44, Barry Warsaw wrote:

On Apr 09, 2017, at 01:13 PM, sab wrote:


https://mentors.debian.net/package/python-zxcvbn

with DPMT as uploader. What's my next step? Have I to create a Git repository?

Welcome to the team Sabino.

You'll want to take a look at these two wiki pages.  First is the style guide
for DPMT packages.

https://wiki.debian.org/Python/LibraryStyleGuide

The second is our git packaging workflow:

https://wiki.debian.org/Python/GitPackaging

but note that we are still discussing the move away from git-dpm to git-pq for
patch queue management.  When that actually happens we'll use:

https://wiki.debian.org/Python/GitPackagingPQ

as a guideline.

Cheers,
-Barry

How can I have permissions to push in git branches: master,upstream or 
pristine-tar?


Regards,
Sabino

Re: Joining the team

[sab]

Hi!


On 10/04/2017 16:44, Barry Warsaw wrote:

On Apr 09, 2017, at 01:13 PM, sab wrote:


https://mentors.debian.net/package/python-zxcvbn

with DPMT as uploader. What's my next step? Have I to create a Git repository?

Welcome to the team Sabino.

You'll want to take a look at these two wiki pages.  First is the style guide
for DPMT packages.

https://wiki.debian.org/Python/LibraryStyleGuide

The second is our git packaging workflow:

https://wiki.debian.org/Python/GitPackaging

but note that we are still discussing the move away from git-dpm to git-pq for
patch queue management.  When that actually happens we'll use:

https://wiki.debian.org/Python/GitPackagingPQ

as a guideline.

Cheers,
-Barry

How can I have permissions to push in git branches: master,upstream or 
pristine-tar?


Regards,
Sabino

Re: Joining the team

[Barry Warsaw]

On Apr 09, 2017, at 01:13 PM, sab wrote:

>https://mentors.debian.net/package/python-zxcvbn
>
>with DPMT as uploader. What's my next step? Have I to create a Git repository?

Welcome to the team Sabino.

You'll want to take a look at these two wiki pages.  First is the style guide
for DPMT packages.

https://wiki.debian.org/Python/LibraryStyleGuide

The second is our git packaging workflow:

https://wiki.debian.org/Python/GitPackaging

but note that we are still discussing the move away from git-dpm to git-pq for
patch queue management.  When that actually happens we'll use:

https://wiki.debian.org/Python/GitPackagingPQ

as a guideline.

Cheers,
-Barry

Re: Joining the team

[sab]

Hi,
On 06/04/2017 00:38, Piotr Ożarowski wrote:

[sab, 2017-04-01]

- I'd like to join DPM Team, I'm trying to learn and give my contribution to
Debian, so I have adopted my first orphaned Python package: python-zxcvbn
https://mentors.debian.net/package/python-zxcvbnand I prefer to work in a
dedicated team.

- In Alioth website i'm sprab-guest
- I have read and accept the policy

welcome :)

My package is

https://mentors.debian.net/package/python-zxcvbn

 with DPMT as uploader. What's my next step? Have I to create a Git 
repository?


Best Regards,
Sabino

Re: Joining the team

[Piotr Ożarowski]

[sab, 2017-04-01]
> - I'd like to join DPM Team, I'm trying to learn and give my contribution to
> Debian, so I have adopted my first orphaned Python package: python-zxcvbn
> https://mentors.debian.net/package/python-zxcvbnand I prefer to work in a
> dedicated team.
> 
> - In Alioth website i'm sprab-guest
> - I have read and accept the policy

welcome :)
-- 
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Re: Joining the team

[Piotr Ożarowski]

> krata-guest

welcome! :)

(and sorry for the delay)
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Re: Joining the team

[Piotr Ożarowski]

[Alexis Métaireau, 2016-05-16]
> My Alioth login is "almet-guest", and I've read
> https://python-modules.alioth.debian.org/policy.html and accept it.

welcome on board! :)
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645

Re: Joining the team

[Ian Cordasco]

On Thu, Dec 31, 2015 at 11:21 AM, Scott Kitterman  wrote:
> On Thursday, December 31, 2015 08:31:31 AM Ian Cordasco wrote:
>> Hi everyone,
>>
>> I would like to join the debian-python team. I have read the policy at
>>
>>   https://python-modules.alioth.debian.org/python-modules-policy.html
>>
>> and accept it.
>>
>> My Alioth account is sigmavirus24-guest.
>>
>> I would like to join the team to help package and maintain
>> python-betamax (ITP
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808880) with Daniele
>> Tricoli.
>>
>> I don't maintain any other Debian packages and I'm not part of any
>> other teams, but I'm eager to learn and help.
>>
>> Thanks!
>> Ian
>
> Welcome to the team.

Thank you!

Re: Joining the team

[Daniele Tricoli]

On Thursday, December 31, 2015 08:31:31 AM Ian Cordasco wrote:
> I would like to join the team to help package and maintain
> python-betamax (ITP
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808880) with Daniele
> Tricoli.

I very glad Ian applied to join the DPMT!

I'm happy to have him as a co-maintainer of Betamax, and since he is also 
upstream of both requests and urllib3, if he want to help me maintaining both, 
I will feel honoured! :)

-- 
 Daniele Tricoli 'eriol'
 https://mornie.org

signature.asc
Description: This is a digitally signed message part.

Re: Joining the team

[Scott Kitterman]

On Thursday, December 31, 2015 08:31:31 AM Ian Cordasco wrote:
> Hi everyone,
> 
> I would like to join the debian-python team. I have read the policy at
> 
>   https://python-modules.alioth.debian.org/python-modules-policy.html
> 
> and accept it.
> 
> My Alioth account is sigmavirus24-guest.
> 
> I would like to join the team to help package and maintain
> python-betamax (ITP
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808880) with Daniele
> Tricoli.
> 
> I don't maintain any other Debian packages and I'm not part of any
> other teams, but I'm eager to learn and help.
> 
> Thanks!
> Ian

Welcome to the team.

Scott K

Re: Joining the team

[Paul Tagliamonte]

On Thu, Dec 31, 2015 at 08:31:31AM -0600, Ian Cordasco wrote:
> My Alioth account is sigmavirus24-guest.
> 
> I would like to join the team to help package and maintain
> python-betamax (ITP
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808880) with Daniele
> Tricoli.
> 
> I don't maintain any other Debian packages and I'm not part of any
> other teams, but I'm eager to learn and help.

I'm also interested in sponsoring Ian's work in d-python, having him in
the team is a huge help

Thanks!
  Paul


signature.asc
Description: PGP signature

Re: Joining the team

[Piotr Ożarowski]

[Dima Kogan, 2015-10-16]
> My Alioth account is dkogan-guest.

welcome on board!

(and sorry for the delay)
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645


signature.asc
Description: PGP signature

Re: Joining the team

[Jackson Doak]

My alioth login is noskcaj-guest

On Sun, Sep 22, 2013 at 7:48 PM, Jackson Doak  wrote:
> I would like to join the python modules team. I already have a number
> of python packages waiting to commit at
> https://mentors.debian.net/packages/uploader/noskcaj%40ubuntu.com . I
> also would like to add the package etm-qt
> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718203) which i will
> upload to mentors soon.
>
> Jackson


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CA+K2i_3JBQarV1qdCWuyNX3=ynyu8s65qxeaqjht_ejn4se...@mail.gmail.com

Re: joining the team

[Piotr Ożarowski]

[Martin Hoefling, 2011-09-16]
> I might just add a packaged "titlecase" module for New York Manual of
> Style alike titlecasing. Moreover, I could also contribute to
> existing packages.

I added you to DPMT (packages in your Ubuntu PPA qualify for this team).
Welcome! :)
-- 
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl  www.griffith.cc   www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645


signature.asc
Description: Digital signature

Re: Joining the team with new packages: rope and ropemacs

[Piotr Ożarowski]

[David Spreen, 2008-07-30]
> I am interested in joining the python-modules team with two new

"netzwurm" user added, welcome

> Any feedback on the packages is appreciated.

* debian/docs - README.txt is listed twice (in both packages)
* rope-0.8.4: python-svn and mercurial packages are missing in
  Depends/Recommends/Suggests
-- 
:wq


pgpcLbHTVRDKV.pgp
Description: PGP signature

Re: Joining the team with new packages: rope and ropemacs

[Ben Finney]

David Spreen <[EMAIL PROTECTED]> writes:

> I am interested in joining the python-modules team with two new
> packages: rope and ropemacs. (binary packages are called python-rope
> and python-ropemacs).

Thank you! I have looked at these programs with interest, and look
forward to having them in Debian.

> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467377
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492931

The package descriptions could be improved, per the guidelines at
http://www.debian.org/doc/developers-reference/ch-best-pkging-practices#s-bpp-pkg-synopsis>
and
http://www.debian.org/doc/developers-reference/best-pkging-practices.html#bpp-pkg-desc>.
The synopses might better be:

Python refactoring library
Emacs mode for Python refactoring

The names "Emacs" and "Python" are properly capitalised that way, so
should be so in the synopsis.

The full descriptions are okay, but are too long (the bullet lists
should be paraphrased only to the essentials) and have too much
indentation (a single space for bulleted list items is customary).

Ropemacs is described as a "plugin"; this term isn't helpful for Emacs
users, where features are implemented via "modes" or other parts. Is
Ropemacs a "major mode", or something else? The description should
inform the user.

> I have one question as to the section of the python-ropemacs
> package. The package provides an emacs mode for Pymacs that is
> usable in emacs and enables all kinds of IDE-like features.
> Technically it is a python module (that's why I put it in section:
> python) but practically it is an emacs mode for python development.
> What do you think should be the proper section?

I think 'devel' is the best section. The over-use of the 'python'
section for packages that are merely implemented in Python makes it
almost meaningless.

-- 
 \   “One seldom discovers a true believer that is worth knowing.” |
  `\ —Henry L. Mencken |
_o__)  |
Ben Finney


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Joining the team and RFS python-avc

[Josselin Mouette]

Le mardi 06 novembre 2007 à 05:20 +0100, Bernd Zeimetz a écrit :
> Matthias Klose wrote:
> > proposed policy changes should
> > be filed as bug reports against python-defaults.

What is the point of having this list if it cannot even be used for
discussing policy changes?

You still haven't added the changes that were approved here almost one
year ago. Do we have to submit a bug report and subscribe the list to
this bug if we want to have your feedback?

-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée

Re: Joining the team and RFS python-avc

[Josselin Mouette]

Le mardi 06 novembre 2007 à 01:25 +0100, Bernd Zeimetz a écrit :
> Josselin Mouette wrote:
> >>> Of course they do. What if a package Depends: python2.5, python2.5-avc?
> >> Depends: python2.5, python-avc (>=new_policy_version)
> > 
> > Sorry, but that dependency is incorrect. What if a later python-avc
> > version starts requiring python >= 2.6 ?
> 
> Then you have a problem anyway - all packages Depending on python-avc
> (which is the only sane default for packages which work for all python
> versions AND depend on a different package) will need to be updated.

Erm, no. If a pure-python package uses it, it won't have to change.

> Adding versioned depends again brings us back to the old policy.

Trying desperately to see something "new" in the policy isn't going to
make a point. It took time to notice it, but it is merely an evolution
that allows extensions to be available for several versions of python at
once.

The real thing that brings us back to the former situation is the 70
packages or so which require an upload at each new python version.

-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée

Re: Joining the team and RFS python-avc

[Bernd Zeimetz]

reassign 447231 debian-policy,python-defaults
thanks

[adding the debian-python list again, I guess you've missed it].

Matthias Klose wrote:
> Bernd Zeimetz writes:
>> Then let's maintain it again. We maintain a lot of packages in a team,
>> so I can't see a problem to maintain the policy there, too.
> 
> The policy files are not unmaintained; 

They are. Maintaining is more than having a minimal update every other year.

> proposed policy changes should
> be filed as bug reports against python-defaults.

If that's the preferred way - I'm reassigning a related bug from
d-policy to d-policy AND python-defaults to make sure it's not forgotten.

Also in my opinion the Python policy should be team-maintained
(preferable by a small and _active_ team) like most Python related
packages.

Manoj's Python 'policy' is much more complete, formal and uptodate then
the official one, so it should replace the current one.

-- 
Bernd Zeimetz
<[EMAIL PROTECTED]> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Joining the team and RFS python-avc

[Scott Kitterman]

On Tue, 06 Nov 2007 01:21:31 +0100 Bernd Zeimetz <[EMAIL PROTECTED]> wrote:
>Josselin Mouette wrote:
>> Le mardi 06 novembre 2007 à 00:22 +0100, Bernd Zeimetz a écrit :
>>> Please get the _official_ Python Policy fixed and such requirements
>>> included if you like to have them. 
>> 
>> The official Python policy is currently unmaintained.
>> 
>
>Then let's maintain it again. We maintain a lot of packages in a team,
>so I can't see a problem to maintain the policy there, too.
>
+1 from me.

I'd help.

Scott K

Re: Joining the team and RFS python-avc

[Bernd Zeimetz]

Josselin Mouette wrote:
> Le lundi 05 novembre 2007 à 23:57 +0100, Piotr Ożarowski a écrit :
 * remove "Provides: ${python:Provides}" - architecture independent
>>   
 packages don't need it
>>> Of course they do. What if a package Depends: python2.5, python2.5-avc?
>> Depends: python2.5, python-avc (>=new_policy_version)
> 
> Sorry, but that dependency is incorrect. What if a later python-avc
> version starts requiring python >= 2.6 ?

Then you have a problem anyway - all packages Depending on python-avc
(which is the only sane default for packages which work for all python
versions AND depend on a different package) will need to be updated.
Adding versioned depends again brings us back to the old policy.


-- 
Bernd Zeimetz
<[EMAIL PROTECTED]> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Joining the team and RFS python-avc

[Bernd Zeimetz]

Josselin Mouette wrote:
> Le mardi 06 novembre 2007 à 00:22 +0100, Bernd Zeimetz a écrit :
>> Please get the _official_ Python Policy fixed and such requirements
>> included if you like to have them. 
> 
> The official Python policy is currently unmaintained.
> 

Then let's maintain it again. We maintain a lot of packages in a team,
so I can't see a problem to maintain the policy there, too.

-- 
Bernd Zeimetz
<[EMAIL PROTECTED]> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Joining the team and RFS python-avc

[Josselin Mouette]

Le lundi 05 novembre 2007 à 23:57 +0100, Piotr Ożarowski a écrit :
> > > * remove "Provides: ${python:Provides}" - architecture independent
>   
> > > packages don't need it
> > 
> > Of course they do. What if a package Depends: python2.5, python2.5-avc?
> 
> Depends: python2.5, python-avc (>=new_policy_version)

Sorry, but that dependency is incorrect. What if a later python-avc
version starts requiring python >= 2.6 ?

> Joss, python2.5-avc is not in new policy spirit. 

There is no "spirit" in the policy. There are only ways to obtain
correct dependencies and working packages.

Anyway, my initial reply was wrong: packages don't *need* to provide
${python:Provides}. This field should only be added if some
reverse-dependencies are requiring it (the reason being, without
automatic addition of python2.X-bar dependencies for all
modules/extensions you depend on, these provides are incorrect). 

> Please note that I'm talking about architecture *independent* packages.
> Architecture dependent package *have to* provide pythonX.Y-module.

There shouldn't be any difference between both when it comes to
dependencies. Generally, architecture: all packages won't need them, but
this is not because of their architecture-independence.

-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée

Re: Joining the team and RFS python-avc

[Josselin Mouette]

Le mardi 06 novembre 2007 à 00:22 +0100, Bernd Zeimetz a écrit :
> Please get the _official_ Python Policy fixed and such requirements
> included if you like to have them. 

The official Python policy is currently unmaintained.

-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée

Re: Joining the team and RFS python-avc

[Bernd Zeimetz]

Josselin Mouette wrote:
> Hi,
> 
> Le lundi 05 novembre 2007 à 15:40 +0100, Piotr Ożarowski a écrit :
>> Hi Fabrizio
>>
>>> I am looking for sponsorship for my new python module: python-avc,
>>>ITP http://bugs.debian.org/448646,
>>>mentors http://mentors.debian.net/debian/pool/main/p/python-avc.
>> * remove "Provides: ${python:Provides}" - architecture independent
>> packages don't need it
> 
> Of course they do. What if a package Depends: python2.5, python2.5-avc?

No, they don't.

Please get the _official_ Python Policy fixed and such requirements
included if you like to have them. Neither the wiki nor Manoj's home are
the appropriate place for that. Coming up with random requirements or
undocumented things here is not the way to go.

http://wiki.debian.org/DebianPython/NewPolicy requires Provides:
${python:Provides} in two cases:
- if the package used to build pythonX.Y-foo binary packages
(the package didn't exist before, so I never built such packages)
- if your package provides public extensions.
(no extensions here - please note that it defines an extension as .so
file some lines above)


http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions
says:

2.5 Provides

Provides in packages of the form python-foo must be specified, if the
package contains an extension for more than one python version. Provides
should also be added on request of maintainers who depend on a
non-default python version.

--> Same here - contains an _extension_. An arch:all package doesn't
ship extensions. The policy defines extensions in the same way as the
wiki does.

Not to forget that the policy is still outdated.


Even Manoj's start of a new policy document says the same:
http://people.debian.org/~srivasta/manoj-policy/x316.html#AEN469

Public pure Python modules that have a subset of all python versions
supported, or for public extensions, the Provides field indicates which
versions of Python are supported (for which one may import  the module).
For every version of python supported the package should provide
pythonX.Y-foo packages. This assumes that the package correctly depends
on all the appropriate versions of any version specific module that it
itself requires.

--> We neither have an extension here, nor does it support a _subset_ of
Python versions.


I'd suggest it's time to replace the more than outdated policy by
Manoj's new version, which seems to be fine (didn't read everything yet).


-- 
Bernd Zeimetz
<[EMAIL PROTECTED]> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Joining the team and RFS python-avc

[Piotr Ożarowski]

> Le lundi 05 novembre 2007 à 15:40 +0100, Piotr Ożarowski a écrit :
> > Hi Fabrizio
> > 
> > > I am looking for sponsorship for my new python module: python-avc,
> > >ITP http://bugs.debian.org/448646,
> > >mentors http://mentors.debian.net/debian/pool/main/p/python-avc.
> > 
> > * remove "Provides: ${python:Provides}" - architecture independent
  
> > packages don't need it
> 
> Of course they do. What if a package Depends: python2.5, python2.5-avc?

Depends: python2.5, python-avc (>=new_policy_version)

Joss, python2.5-avc is not in new policy spirit. Think about this
situation: Fabrizio is uploading this package now, it provides
python2.4-avc and python2.5-avc. Some packages are depending on
python2.4-avc and then 2.4 is removed from supported Python versions.
Should Fabrizio upload new version just because 2.4 is no longer
supported? Should he upload new version when 2.6 will be added?
What with package that still depends on python2.4-avc?
Why do we have python-central and python-support then?

Please note that I'm talking about architecture *independent* packages.
Architecture dependent package *have to* provide pythonX.Y-module.

Fabrizio: you're added, welcome in the team :-)
-- 
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-


pgpsNskfMWjrI.pgp
Description: PGP signature

Re: Joining the team and RFS python-avc

[Josselin Mouette]

Hi,

Le lundi 05 novembre 2007 à 15:40 +0100, Piotr Ożarowski a écrit :
> Hi Fabrizio
> 
> > I am looking for sponsorship for my new python module: python-avc,
> >ITP http://bugs.debian.org/448646,
> >mentors http://mentors.debian.net/debian/pool/main/p/python-avc.
> 
> * remove "Provides: ${python:Provides}" - architecture independent
> packages don't need it

Of course they do. What if a package Depends: python2.5, python2.5-avc?

-- 
 .''`.
: :' :  We are debian.org. Lower your prices, surrender your code.
`. `'   We will add your hardware and software distinctiveness to
  `-our own. Resistance is futile.


signature.asc
Description: Ceci est une partie de message	numériquement signée

Re: Joining the team and RFS python-avc

[Bernd Zeimetz]

Fabrizio Pollastri wrote:
> Bernd Zeimetz wrote:
 * you've missed some packages in Depends (for modules: gtk, qt, PyQt4,
 Tkinter)
>>> Since python-avc is multiplatform, a user will probably use only one
>>> among the supported toolkits. So python-avc really needs to depend from
>>> them all or it only suggests them?
>>
>> How is decided which toolkit avc uses?
> 
> By user selection: he imports from python-avc the proper module for the
> desired toolkit, i.e. for gtk 'from avc.avcgtk import *'.

Then I'd add them all to Suggests:

Cheers,

Bernd

-- 
Bernd Zeimetz
<[EMAIL PROTECTED]> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Joining the team and RFS python-avc

[Fabrizio Pollastri]

Bernd Zeimetz wrote:

* you've missed some packages in Depends (for modules: gtk, qt, PyQt4,
Tkinter)

Since python-avc is multiplatform, a user will probably use only one
among the supported toolkits. So python-avc really needs to depend from
them all or it only suggests them?


How is decided which toolkit avc uses?


By user selection: he imports from python-avc the proper module for the 
desired toolkit, i.e. for gtk 'from avc.avcgtk import *'.


--
Cheers,
Fabrizio.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Joining the team and RFS python-avc

[Bernd Zeimetz]

>> * you've missed some packages in Depends (for modules: gtk, qt, PyQt4,
>> Tkinter)
> 
> Since python-avc is multiplatform, a user will probably use only one
> among the supported toolkits. So python-avc really needs to depend from
> them all or it only suggests them?

How is decided which toolkit avc uses?
If there's a preferred one, let's call it foo, I'd add
Recommends: foo | bar | fuzz
if not, I'd add them all to suggests.


Cheers,

Bernd

-- 
Bernd Zeimetz
<[EMAIL PROTECTED]> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Joining the team and RFS python-avc

[Fabrizio Pollastri]

Piotr Ożarowski wrote:

Hi Fabrizio


I am looking for sponsorship for my new python module: python-avc,
   ITP http://bugs.debian.org/448646,
   mentors http://mentors.debian.net/debian/pool/main/p/python-avc.


* remove "Provides: ${python:Provides}" - architecture independent
packages don't need it


 OK.


* you've missed some packages in Depends (for modules: gtk, qt, PyQt4,
Tkinter)


Since python-avc is multiplatform, a user will probably use only one 
among the supported toolkits. So python-avc really needs to depend from 
them all or it only suggests them?




I will take a deeper look and upload[1] this package after work


I would like to join the team, so I can maintain my package within the
team.


I will add you this evening, I don't have my alioth password ATM

[1] if ftp-master.debian.org will be back online, there are some problems
with it now




--
Cheers,
Fabrizio.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Joining the team and RFS python-avc

[Piotr Ożarowski]

Hi Fabrizio

> I am looking for sponsorship for my new python module: python-avc,
>ITP http://bugs.debian.org/448646,
>mentors http://mentors.debian.net/debian/pool/main/p/python-avc.

* remove "Provides: ${python:Provides}" - architecture independent
packages don't need it
* you've missed some packages in Depends (for modules: gtk, qt, PyQt4,
Tkinter)

I will take a deeper look and upload[1] this package after work

> I would like to join the team, so I can maintain my package within the
> team.

I will add you this evening, I don't have my alioth password ATM

[1] if ftp-master.debian.org will be back online, there are some problems
with it now


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Joining the team

[Piotr Ożarowski]

>  I'd like to maintain python-feedparser (and some other packages in a near
> future) within the team.

You're in. Welcome in the group :-)

-- 
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-


pgp3TYlFCsvxK.pgp
Description: PGP signature

Re: Joining the team

[Jan Michael C. Alonzo]

Piotr Ożarowski <[EMAIL PROTECTED]> writes:

> You have been added. I will take a look at your packages later tonight
> (if no one else will volunteer)

Hi! Thank you!

Cheers,

Jan

-- 

There is no comfort without pain; thus we define salvation through suffering.
-- Cato

Re: Joining the team

[Piotr Ożarowski]

> Hi! I would like to join the team so I can maintain my packages within the
> team as well as help out with maintainance of Debian python-related packages.
> I currently maintain python-pmock, and have two python-related [1] packages
> needing sponsorship at mentors.debian.net (related to two outstanding ITPs).
 
> My alioth username is 'jmalonzo-guest'.
> 
> Thank you and I hope this request will be approved.

You have been added. I will take a look at your packages later tonight
(if no one else will volunteer)
-- 
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-


pgpQ5r8cJCpzt.pgp
Description: PGP signature

Re: joining the team & sponsorship request

[Raphael Hertzog]

On Wed, 19 Apr 2006, Panu Kalliokoski wrote:
> Hello.  I'm a non-DD who would like to join the Python modules packaging
> team, mainly to get my own Python package, Selecting, into Debian, but
> possibly also to help out here and there.  My alioth login is
> "atehwa-guest".

You have been added to the project. You will have commit rights tomorrow.
Welcome to the group!

Cheers,
-- 
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]