DD requiesting to join python-modules-team

[Hans-Christoph Steiner]

hey all,

I'm a DD that is working on a couple python module packages. I have
'pyjavaproperties' already in wheezy/unstable and python-pure-otr in the
works, packaged as 'python-potr' since that was the original name and
the library is still called 'potr', i.e. "import potr"

I'm putting the python-modules-team as the Maintainer, if I'm slow to
respond, please feel free to fix and upload issues.

My alioth name is eighthave.

.hc

[Jakub Wilk]

* Hans-Christoph Steiner <ha...@eds.org>, 2012-10-08, 20:14:

>I'm a DD that is working on a couple python module packages. I have
>'pyjavaproperties' already in wheezy/unstable and python-pure-otr in
>the works, packaged as 'python-potr' since that was the original name
>and the library is still called 'potr', i.e. "import potr"

Welcome to the team! :)

Please note that we use Subversion as VCS:
https://wiki.debian.org/Teams/PythonAppsPackagingTeam/HowTo (but replace
"apps" with "modules").

--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-pyt...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2012100908...@jwilk.net

[Hans-Christoph Steiner]

On Oct 9, 2012, at 4:48 AM, Jakub Wilk wrote:

> * Hans-Christoph Steiner <ha...@eds.org>, 2012-10-08, 20:14:
>> I'm a DD that is working on a couple python module packages. I have 'pyjavaproperties' already in wheezy/unstable and python-pure-otr in the works, packaged as 'python-potr' since that was the original name and the library is still called 'potr', i.e. "import potr"
>
> Welcome to the team! :)
>
> Please note that we use Subversion as VCS:
> https://wiki.debian.org/Teams/PythonAppsPackagingTeam/HowTo (but replace "apps" with "modules").

For a team package, is git-buildpackage out of the question? If so, I can convert.

.hc

--
To UNSUBSCRIBE, email to debian-pyt...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/110C41FB-ACCB-49F1...@at.or.at

[Jakub Wilk]

* Hans-Christoph Steiner <ha...@at.or.at>, 2012-10-10, 11:22:

>>Please note that we use Subversion as VCS:
>>https://wiki.debian.org/Teams/PythonAppsPackagingTeam/HowTo (but
>>replace "apps" with "modules").
>For a team package, is git-buildpackage out of the question?

It is. (This is my personal opinion, others may disagree.)

--
Jakub Wilk

--
To UNSUBSCRIBE, email to debian-pyt...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/2012101019...@jwilk.net

[Dmitrijs Ledkovs]

On 10 October 2012 16:22, Hans-Christoph Steiner <ha...@at.or.at> wrote:
>
> On Oct 9, 2012, at 4:48 AM, Jakub Wilk wrote:
>
>> * Hans-Christoph Steiner <ha...@eds.org>, 2012-10-08, 20:14:
>>> I'm a DD that is working on a couple python module packages. I have 'pyjavaproperties' already in wheezy/unstable and python-pure-otr in the works, packaged as 'python-potr' since that was the original name and the library is still called 'potr', i.e. "import potr"
>>
>> Welcome to the team! :)
>>
>> Please note that we use Subversion as VCS:
>> https://wiki.debian.org/Teams/PythonAppsPackagingTeam/HowTo (but replace "apps" with "modules").
>
> For a team package, is git-buildpackage out of the question? If so, I can convert.
>

I doubt you will get hardly any "team" commits for it.
Or team code review from automatic commit emails.

You can check the mailing list archive for the past discussions.
Currently none of the other version control systems / build tools
offer as fluent workflow as the current one for the top
commiters/uploaders/sponsors in the team.

Nothing stops you to use bzr-svn or git-svn though ;-) works like a
charm for me.

Regards,

Dmitrijs.

--
To UNSUBSCRIBE, email to debian-pyt...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/CANBHLUjSouOYkp1EAbZ5Po6p...@mail.gmail.com