git (was: Making packaging Python modules fun again)

2014-01-27 Thread W. Martin Borgert 
On 2014-01-27 00:14, Nicolas Dandrimont wrote:
(a lot)

I agree with everything.

If somebody has time to update my packages to modern helpers,
convert them from svn to git, or enable Python 3, please go on!

About git: This needs clarification, e.g. will we settle on gbp?
Shall our branch be master (gpbs default) or debian (more
intuitive when one works with upstream)? Will we use the
pristine-tar branch or pristine tar files? Etc.


-- 
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/20140127091158.ga12...@fama.tangosoft.com

Re: Making packaging Python modules fun again (was: Re: Indeed, python-concurrent.futures is the same)

2014-01-27 Thread Elena ``of Valhalla'' 
On 2014-01-27 at 00:14:12 +0100, Nicolas Dandrimont wrote:
 It has been a while since I have been meaning to post a message like this. I

Thanks for writing this

  - Be more welcoming to newcomers. I think that the proof of previous work
policy is a hurdle that we would be better off without. The worst that 
 could
happen is that someone starts packaging something and then the package
languishes in svn. 

I don't know about this: in my case the proof of previous work was 
just a package submitted on mentors, and it was my first package 
for debian ever, still not in a great shape, not a big hurdle.

On the other hand, having to declare which packages you intend 
to work on when joining the team is probably helping maintaing 
the idea that you should only look at your own things and 
not dare touch anything else.

-- 
Elena ``of Valhalla''


-- 
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/20140127102313.gb2...@virginsteele.home.trueelena.org

Re: Making packaging Python modules fun again

2014-01-27 Thread Matthias Klose 
Am 27.01.2014 00:14, schrieb Nicolas Dandrimont:
 - Adding Python 3 support when upstream has it

I think this should make it into the python policy.

  Matthias


-- 
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/52e67a05.8010...@debian.org

Re: Making packaging Python modules fun again

2014-01-27 Thread Thomas Goirand 
On 01/27/2014 11:23 PM, Matthias Klose wrote:
 Am 27.01.2014 00:14, schrieb Nicolas Dandrimont:
 - Adding Python 3 support when upstream has it
 
 I think this should make it into the python policy.
 
   Matthias

I agree.

Thomas


-- 
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/52e6a1bb.4010...@debian.org

Re: Joining the PAPT with roundup

2014-01-27 Thread Kai Storbeck 
On 15/01/2014 23:47, Piotr Ożarowski wrote:
 [Kai Storbeck, 2014-01-15]
 My Alioth username is kaisan-guest, and I would like to request a
 repository on Alioth for roundup.
 
 Welcome on board!
 

Hi Piotr, and the rest,

Thanks a lot.

I've now uploaded my old version of roundup, being version 1.4.20 from
wheezy.

What is considered good practice for a package maintained by a non-DM/DD?

Should I replay my git commits on subversion, or can I create a huge
commit that will show the work done up to now?

Would someone be interested in the small intermediate commits? They
sound boring to me :)

Cheers!
Kai



signature.asc
Description: OpenPGP digital signature