Re: How does team maintenace of python module works?

2013-02-14 Thread Tristan Seligmann
On Thu, Feb 14, 2013 at 5:08 PM, Thomas Goirand wrote: > During these exchanges, I have already found that there's at least 4 > people (including myself) who would like to use Git. And that's without > including all the members of the Openstack packaging team, who might > also help. Do you think t

Re: How does team maintenace of python module works?

2013-02-14 Thread Thomas Kluyver
On 14 February 2013 22:54, Matthias Klose wrote: > > That causes problems when newcomers don't want to learn > > deprecated packaging methods, and aren't allowed to update packages to > use > > the recommended helper. > > Agreed, so why not helping with it? Again, why not helping here? > I'm not

Re: How does team maintenace of python module works?

2013-02-14 Thread Jakub Wilk
* Piotr Ożarowski , 2013-02-14, 23:49: One of the main points of these teams is to allow other members easy access to debian directory / keep track of VCS changes (which I fail to do lately, but did send some replies from -commits mailing list in the past). Keeping package files somewhere where

Re: How does team maintenace of python module works?

2013-02-14 Thread Matthias Klose
Am 14.02.2013 21:54, schrieb Thomas Kluyver: > On 14 February 2013 20:29, Barry Warsaw wrote: > >> I look at the switch to dh_python2 as an example. > > > I don't think it's a particularly good example, though. Lots of packages > continue to use the older helpers, and not due to a lack of time

Re: How does team maintenace of python module works?

2013-02-14 Thread Piotr Ożarowski
[Barry Warsaw, 2013-02-14] > Switching to git or any other dvcs isn't going to happen just by asking for > it. Someone would have to step up and actually do a lot of hard work to make > it happen. Look at all the work done by upstream Python to get it onto > Mercurial. It was *a lot* of work, ma

Re: How does team maintenace of python module works?

2013-02-14 Thread Scott Kitterman
On Thursday, February 14, 2013 04:53:23 PM Barry Warsaw wrote: > On Feb 14, 2013, at 08:54 PM, Thomas Kluyver wrote: > >I don't think it's a particularly good example, though. Lots of packages > >continue to use the older helpers, and not due to a lack of time - attempts > >to move away from the de

Re: How does team maintenace of python module works?

2013-02-14 Thread Barry Warsaw
On Feb 14, 2013, at 08:54 PM, Thomas Kluyver wrote: >I don't think it's a particularly good example, though. Lots of packages >continue to use the older helpers, and not due to a lack of time - attempts >to move away from the deprecated helpers still seem to meet considerable >resistance. That cau

Python Software Foundation: Python Trademark at Risk

2013-02-14 Thread Dmitrijs Ledkovs
Dear All, Full article: http://pyfound.blogspot.co.uk/2013/02/python-trademark-at-risk-in-europe-we.html There is a company in the UK that is trying to trademark the use of the term "Python" for all software, services, servers... pretty much anything having to do with a computer. Specifically, i

Re: How does team maintenace of python module works?

2013-02-14 Thread Thomas Kluyver
On 14 February 2013 20:29, Barry Warsaw wrote: > I look at the switch to dh_python2 as an example. I don't think it's a particularly good example, though. Lots of packages continue to use the older helpers, and not due to a lack of time - attempts to move away from the deprecated helpers still

Re: How does team maintenace of python module works?

2013-02-14 Thread Barry Warsaw
On Feb 15, 2013, at 01:25 AM, Thomas Goirand wrote: >All this is very far from being *forbidden* to send packages to the >python module team using Git and maintain them this way. Of the three main dvcs's, I personally dislike git the most, but I'm resigned to the fact that it's essentially won th

Re: How does team maintenace of python module works?

2013-02-14 Thread Thomas Goirand
On 02/15/2013 02:04 AM, Dmitry Shachnev wrote: > I'm not against switching to Git Hi Dmitry, I believe there's some misunderstanding, so I must make it square. Again, I'm *not* asking for a full switch (or any switch at all) of all (or even some) packages of the python module team. I have *NEVER*

Re: How does team maintenace of python module works?

2013-02-14 Thread Dmitry Shachnev
I'm not against switching to Git, but one of the arguments last time was that maintaining packages in different places will make mass-commits like [1] more difficult. [1]: http://anonscm.debian.org/viewvc/python-modules?view=revision&revision=18483 -- Dmitry Shachnev On Thu, Feb 14, 2013 at 9:2

Re: How does team maintenace of python module works?

2013-02-14 Thread Thomas Goirand
On 02/15/2013 12:41 AM, Sandro Tosi wrote: > On Thu, Feb 14, 2013 at 4:08 PM, Thomas Goirand wrote: >> Sandro, I have some problems with such an answer, especially when I >> tried to remain polite. This is an incentive so that I change my tone as >> well, and that's not what I would expect from De

Re: How does team maintenace of python module works?

2013-02-14 Thread Thomas Kluyver
On 14 February 2013 16:41, Sandro Tosi wrote: > so please search into the mailing list archive about the several > iterations of such discussion and the outcome of them. The most recent discussion I found with a quick search started nearly 2 years ago. Nobody appeared to be arguing strongly aga

RFR: python-qrcode -- native python module to generate QR codes

2013-02-14 Thread Cornelius Kölbel
Hello, I created and uploaded a debian package with a python module: * Package name: qrcode Version : 2.4.2-1 Upstream Author : Lincoln Loop * URL : https://github.com/lincolnloop/python-qrcode * License : BSD (2 clause) MIT/X11 (BSD like) Section

Re: How does team maintenace of python module works?

2013-02-14 Thread Sandro Tosi
On Thu, Feb 14, 2013 at 4:08 PM, Thomas Goirand wrote: > Sandro, I have some problems with such an answer, especially when I > tried to remain polite. This is an incentive so that I change my tone as > well, and that's not what I would expect from Debian packaging teams. so please search into the

Re: How does team maintenace of python module works?

2013-02-14 Thread Thomas Goirand
On 02/14/2013 08:52 PM, Thomas Kluyver wrote: > Please don't be put off by the somewhat hostile atmosphere that seems to > be an unfortunate feature of this list. There seem to be historical > tensions between some of the senior members. > > Thomas It is indeed not a very welcoming start at all.

Re: How does team maintenace of python module works?

2013-02-14 Thread Thomas Kluyver
On 14 February 2013 12:12, Thomas Goirand wrote: > Is there a valid reason despite history? Is there a chance that this > rule may be reconsidered? It'd be really nice, as I'm sure I wouldn't be > the only one happy with such decision. > I don't know the history, but I'll voice my support for al

Re: How does team maintenace of python module works?

2013-02-14 Thread Sandro Tosi
On Thu, Feb 14, 2013 at 1:12 PM, Thomas Goirand wrote: > On 02/14/2013 04:53 PM, Sandro Tosi wrote: If the team is in Maintainer field, I think you can freely upload the new version. See

Re: How does team maintenace of python module works?

2013-02-14 Thread Thomas Goirand
On 02/14/2013 04:53 PM, Sandro Tosi wrote: >>> If the team is in Maintainer field, I think you can freely upload the >>> new version. See >>> >>> for details. > > Bug fixing is always fine for t

Re: How does team maintenace of python module works?

2013-02-14 Thread Sandro Tosi
>> If the team is in Maintainer field, I think you can freely upload the >> new version. See >> >> for details. Bug fixing is always fine for team-maintained pkgs, but just throwing a new upstre