Re: How does team maintenace of python module works?

❦ 22 février 2013 16:12 CET, Thomas Goirand  : >>> From a server in a data center in Seattle, it took me 90 seconds >>> to download the packaging sources of python-eventlet. Compare >>> this to the 4 seconds it takes me to clone python-warlock from >>> Alioth, upstream source included !!! >> your

Re: How does team maintenace of python module works?

On 02/22/2013 03:57 PM, Piotr Ożarowski wrote: > [Thomas Goirand, 2013-02-22] >> From a server in a data center in Seattle, it took me 90 seconds >> to download the packaging sources of python-eventlet. Compare >> this to the 4 seconds it takes me to clone python-warlock from >> Alioth, upstream so

Re: How does team maintenace of python module works?

On Friday, February 22, 2013 03:14:30 PM Thomas Goirand wrote: ... > The problem is that with SVN, it takes so much time and space > (as each tag will generate some files), so you might have been > fooled into thinking it would also with Git. But the reality simply > not that at all. ... I almost

Re: How does team maintenace of python module works?

Hi, On Wed, Feb 20, 2013 at 11:46:31PM -0500, Barry Warsaw wrote: > """ > 9. Git history is a bunch of lies > The primary output of development work should be source code. Is a > well-maintained history really such an important by-product? Most of the > arguments for rebase, in particular, rely on

Re: How does team maintenace of python module works?

[Thomas Goirand, 2013-02-22] > From a server in a data center in Seattle, it took me 90 seconds > to download the packaging sources of python-eventlet. Compare > this to the 4 seconds it takes me to clone python-warlock from > Alioth, upstream source included !!! your data is wrong (see below). I

Re: How does team maintenace of python module works?

On 02/21/2013 01:59 AM, Scott Kitterman wrote: > I don't keep local copies of things I don't work on regularly, so for team > packages I would be downloading all of it. I thought about it for a long time. Then I tried again today, and now, I don't buy into this "it takes too much time to download

Re: How does team maintenace of python module works?

[Thomas Goirand, 2013-02-21] > git-buildpackage takes some time to learn. > > I think it might be worth trying git-stuff (eg: the package). > I know few people who use it and are happy with it. sure, I will try it. Migrate packages and describe the workflow on wiki and I will test it. How about

Re: How does team maintenace of python module works?

On 02/21/2013 04:55 PM, Piotr Ożarowski wrote: > Can we go back to DPMT/PAPT workflow? Git vs. Bzr vs. Hg war is not > that relevant (and we already know which VCS won, at least in Debian ;P) > > Can we focus on what we want (without taking VCS into account if > possible) so that those who will pro

Re: How does team maintenace of python module works?

Can we go back to DPMT/PAPT workflow? Git vs. Bzr vs. Hg war is not that relevant (and we already know which VCS won, at least in Debian ;P) Can we focus on what we want (without taking VCS into account if possible) so that those who will propose workflow/tools/do the initial migration can start w

Re: How does team maintenace of python module works?

On 02/21/2013 02:26 PM, Scott Kitterman wrote: > >> I undertand that learning Git after BZR is hard, because learning BZR after >> Git is equally painful. I think that the key difficulty is whether a >> system is learned first or second, not the system itself. >> >> This is where git-buildpackage

Re: How does team maintenace of python module works?

On Thu, 2013-02-21 at 12:08 +0800, Chow Loong Jin wrote: > On 21/02/2013 11:58, Scott Kitterman wrote: > > I'm all for easy. I have yet to see a full source (regardless of VCS) or > > git > > workflow that I didn't find more complex and harder to remember/do > > correctly > > than what we have

Re: How does team maintenace of python module works?

On 02/21/2013 02:29 PM, Scott Kitterman wrote: > I've tried doing this. Then I looked back and noticed that I was spending a > LOT of time making the VCS pretty, just in case and rarely had to revert > anything. It turned out I was spending a lot of time to save a little time > and that's just

Re: How does team maintenace of python module works?

On 02/21/2013 01:36 PM, Scott Kitterman wrote: > Agreed. > > I always liked this one http://netsplit.com/2009/02/17/git-sucks/ (enough to > be able to find it 4 years later). > > Scott K Lucky, 4 years later, the error messages of Git are much much more helpful than they used to be (in fact, since

Re: How does team maintenace of python module works?

On Feb 20, 2013 11:57 PM, "Dmitrijs Ledkovs" wrote: > > On 19 February 2013 23:49, Ludovic Gasc wrote: > > > > On Feb 19, 2013 11:21 PM, "Barry Warsaw" wrote: > >> > >> On Feb 19, 2013, at 09:42 PM, Thomas Kluyver wrote: > >> > > > > I can do that this week-end. I've only a github account to pub

Re: How does team maintenace of python module works?

On Thursday, February 21, 2013 02:02:09 PM Chow Loong Jin wrote: > On 21/02/2013 12:46, Barry Warsaw wrote: > > #9 on Steve Bennett's list is right on target IMHO, but I've had this > > discussion so many times before, I don't have much energy for it again. > > > > """ > > 9. Git history is a bunc

Re: How does team maintenace of python module works?

On Thursday, February 21, 2013 01:52:59 PM Chow Loong Jin wrote: > (Re-posted back on list. Sorry ScottK.) > > On 21/02/2013 12:37, Scott Kitterman wrote: > > With git (I've never used gpb, and maybe that's my problem) I end up > > having to do things like: > > > > git clone git://git.debian.org/

Re: How does team maintenace of python module works?

On Thursday, February 21, 2013 03:00:56 PM Charles Plessy wrote: > Le Wed, Feb 20, 2013 at 11:02:15PM -0500, Scott Kitterman a écrit : > > On Thursday, February 21, 2013 11:08:13 AM Chow Loong Jin wrote: > > ... > > > > > That argument applies to any VCS that you don't use on a daily basis. > > >

Re: How does team maintenace of python module works?

On Thursday, February 21, 2013 01:57:11 PM Thomas Goirand wrote: > On 02/21/2013 12:32 PM, Barry Warsaw wrote: > > On Feb 20, 2013, at 11:02 PM, Scott Kitterman wrote: > >> It is to a degree, but the learning curve for git is subtantially steeper > >> than for other VCS. I've learned CVS, SVN, BZR

Re: How does team maintenace of python module works?

On 21/02/2013 12:46, Barry Warsaw wrote: > #9 on Steve Bennett's list is right on target IMHO, but I've had this > discussion so many times before, I don't have much energy for it again. > > """ > 9. Git history is a bunch of lies > The primary output of development work should be source code. Is

Re: How does team maintenace of python module works?

Le Wed, Feb 20, 2013 at 11:02:15PM -0500, Scott Kitterman a écrit : > On Thursday, February 21, 2013 11:08:13 AM Chow Loong Jin wrote: > ... > > That argument applies to any VCS that you don't use on a daily basis. You > > use bzr on a daily basis and forget how to use git. I use git on a daily > >

Re: How does team maintenace of python module works?

On 02/21/2013 12:32 PM, Barry Warsaw wrote: > On Feb 20, 2013, at 11:02 PM, Scott Kitterman wrote: > >> It is to a degree, but the learning curve for git is subtantially steeper >> than for other VCS. I've learned CVS, SVN, BZR, and Git at one time or >> another and there is no question in my mind

Re: How does team maintenace of python module works?

On Wednesday, February 20, 2013 11:46:31 PM Barry Warsaw wrote: > >At least with git, you know when you've rewritten history -- you're no > >longer on the same commit. > > #9 on Steve Bennett's list is right on target IMHO, but I've had this > discussion so many times before, I don't have much ene

Re: How does team maintenace of python module works?

(Re-posted back on list. Sorry ScottK.) On 21/02/2013 12:37, Scott Kitterman wrote: > With git (I've never used gpb, and maybe that's my problem) I end up having > to > do things like: > > git clone git://git.debian.org/….git > for branch in pristine-tar debian/unstable ; do git branch --track

Re: How does team maintenace of python module works?

On Thu, Feb 21, 2013 at 12:37 PM, Scott Kitterman wrote: > That's the sort of thing that convinces me it's too hard. The fact that I > have to manually make the association between individual local and remove > branches is just insane. This has changed with git from experimental, it sets up the

Re: How does team maintenace of python module works?

On Thursday, February 21, 2013 12:08:45 PM Chow Loong Jin wrote: > On 21/02/2013 11:58, Scott Kitterman wrote: > > On Thursday, February 21, 2013 11:12:58 AM Chow Loong Jin wrote: > >> On 21/02/2013 01:59, Scott Kitterman wrote: > >>> I've done the boring bits enough that my fingers mostly do them

Re: How does team maintenace of python module works?

On Feb 21, 2013, at 12:15 PM, Chow Loong Jin wrote: >I'll admit that git isn't the simplest one, the others are not perfect either. >To this day, I can't for the life of me figure out how to use CVS. Thank >goodness git-cvsimport works. Of course, CVS is 20+ years old so its ancient model is work

Re: How does team maintenace of python module works?

On Feb 20, 2013, at 11:02 PM, Scott Kitterman wrote: >It is to a degree, but the learning curve for git is subtantially steeper >than for other VCS. I've learned CVS, SVN, BZR, and Git at one time or >another and there is no question in my mind which one, by a lot, is the most >complex to learn.

Re: How does team maintenace of python module works?

On 21/02/2013 12:02, Scott Kitterman wrote: > It is to a degree, but the learning curve for git is subtantially steeper > than > for other VCS. I've learned CVS, SVN, BZR, and Git at one time or another > and > there is no question in my mind which one, by a lot, is the most complex to > lear

Re: How does team maintenace of python module works?

On 21/02/2013 11:58, Scott Kitterman wrote: > On Thursday, February 21, 2013 11:12:58 AM Chow Loong Jin wrote: >> On 21/02/2013 01:59, Scott Kitterman wrote: >>> I've done the boring bits enough that my fingers mostly do them without >>> much attention from my brain. If I were going to abandon my

Re: How does team maintenace of python module works?

On Thursday, February 21, 2013 11:08:13 AM Chow Loong Jin wrote: ... > That argument applies to any VCS that you don't use on a daily basis. You > use bzr on a daily basis and forget how to use git. I use git on a daily > basis and forget how to use svn/bzr and have to relearn it any time someone >

Re: How does team maintenace of python module works?

On Thursday, February 21, 2013 11:12:58 AM Chow Loong Jin wrote: > On 21/02/2013 01:59, Scott Kitterman wrote: > > I've done the boring bits enough that my fingers mostly do them without > > much attention from my brain. If I were going to abandon my current > > approach, I'd have to see significa

Re: How does team maintenace of python module works?

On Feb 21, 2013, at 11:08 AM, Chow Loong Jin wrote: >That argument applies to any VCS that you don't use on a daily basis. You use >bzr on a daily basis and forget how to use git. I use git on a daily basis and >forget how to use svn/bzr and have to relearn it any time someone forces me to >use on

Re: How does team maintenace of python module works?

On 21/02/2013 01:59, Scott Kitterman wrote: > I've done the boring bits enough that my fingers mostly do them without much > attention from my brain. If I were going to abandon my current approach, I'd > have to see significant advantages for a new way and I don't. Somehow I can only read this as

Re: How does team maintenace of python module works?

On 20/02/2013 23:45, Scott Kitterman wrote: > On Wednesday, February 20, 2013 11:23:44 PM Thomas Goirand wrote: > [...] >> If you are modifying some packages, it's to upload them at some point. >> In such case, you will need the upstream tarball, right? I don't see where >> the waste of bandwidth i

Re: How does team maintenace of python module works?

On 21/02/2013 01:43, Piotr Ożarowski wrote: > does git-buildpackage work with git submodules (with debian dir as a > separate git repo)? It should. I wrote the initial patch for submodule support in git-buildpackage. -- Kind regards, Loong Jin signature.asc Description: OpenPGP digital signat

Re: How does team maintenace of python module works?

On 19 February 2013 23:49, Ludovic Gasc wrote: > > On Feb 19, 2013 11:21 PM, "Barry Warsaw" wrote: >> >> On Feb 19, 2013, at 09:42 PM, Thomas Kluyver wrote: >> > > I can do that this week-end. I've only a github account to publish the git > repository, unless somebody else has an access for a bet

Re: How does team maintenace of python module works?

On Wed, Feb 20, 2013 at 06:43:11PM +0100, Piotr Ożarowski wrote: > [Thomas Goirand, 2013-02-20] > > I wouldn't > > mind switching to some different way of doing things if the team finds it > > relevant, and if it is more easy and unified across all packages. If so, > > please tell how you would lik

Re: How does team maintenace of python module works?

Thomas Goirand wrote: >On 02/20/2013 11:45 PM, Scott Kitterman wrote: >> On Wednesday, February 20, 2013 11:23:44 PM Thomas Goirand wrote: >>> On 02/20/2013 10:43 PM, Scott Kitterman wrote: First, full source repositories are much larger than debian only repositories. I don't have a f

Re: How does team maintenace of python module works?

Den 20. feb. 2013 16:23, skreiv Thomas Goirand: If that doesn't work, you can use the pristine-tar thing, that should always work. I never used it, probably I should learn, it seems quite convenient. Can anyone give feedback about it? My workflow for anything outside of this team and not intende

Re: How does team maintenace of python module works?

[Thomas Goirand, 2013-02-20] > I wouldn't > mind switching to some different way of doing things if the team finds it > relevant, and if it is more easy and unified across all packages. If so, > please tell how you would like to work. We would loose most of the cool > features I was used to, but so

Re: How does team maintenace of python module works?

On 02/20/2013 11:45 PM, Scott Kitterman wrote: > On Wednesday, February 20, 2013 11:23:44 PM Thomas Goirand wrote: >> On 02/20/2013 10:43 PM, Scott Kitterman wrote: >>> First, full source repositories are much larger than debian only >>> repositories. I don't have a full checkout of all team packag

Re: How does team maintenace of python module works?

On 02/20/2013 11:09 PM, Barry Warsaw wrote: > On Feb 20, 2013, at 10:53 PM, Thomas Goirand wrote: > >>> You better be darn sure that upstream has excellent QA then, and that you >>> know for sure that a tag is correctly assigned to a buildable, tested, QA >>> passed snapshot of the project. >> In w

Re: How does team maintenace of python module works?

On Wednesday, February 20, 2013 11:23:44 PM Thomas Goirand wrote: > On 02/20/2013 10:43 PM, Scott Kitterman wrote: > > First, full source repositories are much larger than debian only > > repositories. I don't have a full checkout of all team packages locally, > > so that means if I'm going to touc

Re: How does team maintenace of python module works?

On 02/20/2013 10:43 PM, Scott Kitterman wrote: > First, full source repositories are much larger than debian only > repositories. > I don't have a full checkout of all team packages locally, so that means if > I'm going to touch a package I don't have to download, it's more time, > bandwidth,

Re: How does team maintenace of python module works?

On Feb 20, 2013, at 10:53 PM, Thomas Goirand wrote: >> You better be darn sure that upstream has excellent QA then, and that you >> know for sure that a tag is correctly assigned to a buildable, tested, QA >> passed snapshot of the project. > >In what way the QA is different because it's a tag ins

Re: How does team maintenace of python module works?

On 20 February 2013 14:53, Thomas Goirand wrote: > In what way the QA is different because it's a tag instead of a tarball ? > I don't understand your reasoning. In both cases, you must make sure > that what you are packaging is buildable, tested, QA, etc. > I think the idea is that, if you prep

Re: How does team maintenace of python module works?

On 02/20/2013 10:23 PM, Barry Warsaw wrote: > On Feb 20, 2013, at 10:14 PM, Thomas Goirand wrote: > >> If sticking to our old habits is not the only valid point, that there >> are real technical reasons why we should never be using a git tag >> as the key for an upstream release, or if you think th

Re: How does team maintenace of python module works?

On Wednesday, February 20, 2013 10:14:26 PM Thomas Goirand wrote: > Upstream tarballs, in some cases, is a concept of the past. When > they are released (sometimes, they simply don't exist), it may only > an image based on a git tag. Then using Git tags is often better, > because tags may be PGP si

Re: How does team maintenace of python module works?

On Wednesday, February 20, 2013 04:34:05 PM Thomas Goirand wrote: > On 02/20/2013 12:41 PM, Scott Kitterman wrote: > > This all seems to assume full source branches which is not something I'm > > interested in participating in at all. I've tried it and I find it very > > difficult to work with. >

Re: How does team maintenace of python module works?

On 20/02/13 14:14, Thomas Goirand wrote: > Now, do you know if it is possible to use git-buildpackage > without storing the full upstream source in a branch? Yes, most conveniently done via 'overlay = True' in debian/gbp.conf. You have to supply a copy of the upstream tarball as you would for plai

Re: How does team maintenace of python module works?

On Feb 20, 2013, at 10:14 PM, Thomas Goirand wrote: >If sticking to our old habits is not the only valid point, that there >are real technical reasons why we should never be using a git tag >as the key for an upstream release, or if you think they might be >real difference between the "git archive

Re: How does team maintenace of python module works?

On 02/20/2013 04:57 PM, Matthias Klose wrote: > So there would be no way anymore to build using upstream tarballs? Upstream tarballs, in some cases, is a concept of the past. When they are released (sometimes, they simply don't exist), it may only an image based on a git tag. Then using Git tags i

Re: How does team maintenace of python module works?

Am 20.02.2013 09:31, schrieb Thomas Goirand: > On 02/20/2013 12:38 PM, Scott Kitterman wrote: >> On Wednesday, February 20, 2013 12:23:02 PM Thomas Goirand wrote: >>> The idea to use "git archive" was mostly from Julien Danjou. It's >>> very nice because that way, we can use xz compression, instead

Re: How does team maintenace of python module works?

On 02/20/2013 04:31 PM, Luca BRUNO wrote: > This may suit well for the openstack scenario, however in general I > could see at least two shortcomings: > * pristine upstream tarballs are not used (see the first "should" in > devref §6.7.8.2) > * it assumes that no tarball generation process (eg. m

Re: How does team maintenace of python module works?

On 02/20/2013 12:41 PM, Scott Kitterman wrote: > This all seems to assume full source branches which is not something I'm > interested in participating in at all. I've tried it and I find it very > difficult to work with. > > Currently we have one VCS and one package layout. In the end, we shou

Re: How does team maintenace of python module works?

Thomas Goirand scrisse: > I've found that having a debian/rules entry called "get-vcs-source" > which gets what is needed from upstream works quite nicely. Our > workflow is described here: > > http://openstack.alioth.debian.org/ > > The idea to use "git archive" was mostly from Julien Danjou. I

Re: How does team maintenace of python module works?

On 02/20/2013 12:38 PM, Scott Kitterman wrote: > On Wednesday, February 20, 2013 12:23:02 PM Thomas Goirand wrote: >> The idea to use "git archive" was mostly from Julien Danjou. It's >> very nice because that way, we can use xz compression, instead >> of what upstream provides (that is, github .zi

Re: How does team maintenace of python module works?

On Wednesday, February 20, 2013 12:23:02 PM Thomas Goirand wrote: > On 02/20/2013 06:20 AM, Barry Warsaw wrote: > > * Figure out whether full-source or debian/ only works better (maybe give > > us> > > both repos so we can play with them and discuss the pros and cons from > > actual working ex

Re: How does team maintenace of python module works?

On Wednesday, February 20, 2013 12:23:02 PM Thomas Goirand wrote: > The idea to use "git archive" was mostly from Julien Danjou. It's > very nice because that way, we can use xz compression, instead > of what upstream provides (that is, github .zip or .tar.gz, which > isn't the best). See devref 6

Re: How does team maintenace of python module works?

On 02/20/2013 06:20 AM, Barry Warsaw wrote: > * Figure out whether full-source or debian/ only works better (maybe give us > both repos so we can play with them and discuss the pros and cons from > actual working examples). What is important, I believe, is that git-buildpackage always works.

Re: How does team maintenace of python module works?

On Tuesday, February 19, 2013 05:20:48 PM Barry Warsaw wrote: > On Feb 19, 2013, at 09:42 PM, Thomas Kluyver wrote: > >After that it gets tricky, because we'd knock E out next, but the I'm not > >sure where the votes counted for E (Scott & Barry) should be reallocated. > > If it makes things easie

Re: How does team maintenace of python module works?

Am 20.02.2013 00:53, schrieb Piotr Ożarowski: > [Barry Warsaw, 2013-02-19] >> So I still think it comes down to, them that does the work gets to >> decide, but there *is* work to do. It's clear we don't want multiple >> vcses. So I think you have an opportunity to convince us by: >> >> * Doing a

Re: How does team maintenace of python module works?

On Feb 19, 2013 11:21 PM, "Barry Warsaw" wrote: > > On Feb 19, 2013, at 09:42 PM, Thomas Kluyver wrote: > > >After that it gets tricky, because we'd knock E out next, but the I'm not > >sure where the votes counted for E (Scott & Barry) should be reallocated. > > If it makes things easier, I am es

Re: How does team maintenace of python module works?

[Barry Warsaw, 2013-02-19] > So I still think it comes down to, them that does the work gets to decide, but > there *is* work to do. It's clear we don't want multiple vcses. So I think > you have an opportunity to convince us by: > > * Doing a test migration and putting a test repo up so we can

Re: How does team maintenace of python module works?

On Tuesday 19 February 2013 23:20:48 Barry Warsaw wrote: > If it makes things easier, I am essentially sided with Piotr. The fact > that I don't like git much is immaterial - I want a dvcs and don't have > the time to put into a bzr or hg migration. I don't have time to put > into a git migration

Re: How does team maintenace of python module works?

On Feb 19, 2013, at 09:42 PM, Thomas Kluyver wrote: >After that it gets tricky, because we'd knock E out next, but the I'm not >sure where the votes counted for E (Scott & Barry) should be reallocated. If it makes things easier, I am essentially sided with Piotr. The fact that I don't like git m

Re: How does team maintenace of python module works?

I didn't vote initiall because I read the below as a summary... On 17 February 2013 01:43, Thomas Kluyver wrote: > On 16 February 2013 09:10, Thomas Goirand wrote: >> >> It would be really stupid to only want to "claim" to be working as part >> of the team, that's not at all what I want to do. I

Re: How does team maintenace of python module works?

On Tue, Feb 19, 2013 at 3:42 PM, Thomas Kluyver wrote: > On 19 February 2013 17:55, Thomas Goirand wrote: >> >> Thomas Kluyver >> Seems to be ok with migrating to Git (so, option D) > > > I voted CDBA in the same e-mail that I introduced the poll ;-). Thanks for > summarising the votes. > > Inclu

Re: How does team maintenace of python module works?

On 19 February 2013 17:55, Thomas Goirand wrote: > Thomas Kluyver > Seems to be ok with migrating to Git (so, option D) I voted CDBA in the same e-mail that I introduced the poll ;-). Thanks for summarising the votes. Including Piotr & Andreas, and putting people whose opinion you've described

Re: How does team maintenace of python module works?

Den 19. feb. 2013 18:55, skreiv Thomas Goirand: If the above isn't correct, please let everyone know your view. Thomas My contribution to this team is relatively low volume, but anyways: My vote is, in order of preference, DCAB. I'd also be happy with bzr (which I use for my Ubuntu stuff), but

Re: How does team maintenace of python module works?

FTR: I want to migrate to Git, but I don't have time to do the migration work right now, so I vote for status quo (unless someone will show me the code) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fing

Re: How does team maintenace of python module works?

On 02/20/2013 01:23 AM, Dmitry Shachnev wrote: > On Tue, Feb 19, 2013 at 9:11 PM, Thomas Goirand wrote: >> So far, those who could have vote C or D (this shows in previous reply >> that some could have voted that) didn't bother answering the "poll". > I've already expressed my opinion in this thre

Re: How does team maintenace of python module works?

On 02/20/2013 01:23 AM, Dmitry Shachnev wrote: > On Tue, Feb 19, 2013 at 9:11 PM, Thomas Goirand wrote: >> So far, those who could have vote C or D (this shows in previous reply >> that some could have voted that) didn't bother answering the "poll". > I've already expressed my opinion in this thre

Re: How does team maintenace of python module works?

On Tue, Feb 19, 2013 at 9:11 PM, Thomas Goirand wrote: > So far, those who could have vote C or D (this shows in previous reply > that some could have voted that) didn't bother answering the "poll". I've already expressed my opinion in this thread, but to be formal: my vote is DA. -- Dmitry Shac

Re: How does team maintenace of python module works?

On 02/19/2013 06:08 AM, Thomas Kluyver wrote: > On 18 February 2013 20:46, Ludovic Gasc > wrote: > > I vote D, and I can handle the migration from SVN to Git, I've > done this several times for my work and WYMeditor. > > Are you interested? > > I'm interested p

Re: How does team maintenace of python module works?

On 18 February 2013 22:23, Ludovic Gasc wrote: > I propose to make a poll on the Web (Doodle or other) and ask the question > in another thread, I'm not sure that each subscriber has read this long > thread. > I don't think I'll do that myself - the responses I have seen don't have even the bare

Re: How does team maintenace of python module works?

* Ludovic Gasc , 2013-02-18, 23:23: I propose to make a poll on the Web (Doodle or other) and ask the question in another thread, I'm not sure that each subscriber has read this long thread. And then, if the results are still unsatisfactory, let's create a repo at GitHub and let people vote v

Re: How does team maintenace of python module works?

On Mon, Feb 18, 2013 at 11:08 PM, Thomas Kluyver wrote: > On 18 February 2013 20:46, Ludovic Gasc wrote: > >> I vote D, and I can handle the migration from SVN to Git, I've done this >> several times for my work and WYMeditor. >> >> Are you interested? >> > I'm interested personally, but the vote

Re: How does team maintenace of python module works?

On 18 February 2013 20:46, Ludovic Gasc wrote: > I vote D, and I can handle the migration from SVN to Git, I've done this > several times for my work and WYMeditor. > > Are you interested? > I'm interested personally, but the votes so far suggest there's no real will for any change - the only opt

Re: How does team maintenace of python module works?

On Feb 16, 2013 1:43 PM, "Thomas Kluyver" wrote: > > On 16 February 2013 09:10, Thomas Goirand wrote: >> >> It would be really stupid to only want to "claim" to be working as part >> of the team, that's not at all what I want to do. I'd like to be able to >> help when I can, and receive help when

Re: How does team maintenace of python module works?

* Piotr Ożarowski , 2013-02-14, 23:49: I (as an admin) will (and already did in the past) ask anyone who doesn't keep a team package in SVN to remove DPMT/PAPT from Maintainer/Uploaders (until we officially migrate to something else). Please start with these (they declare Vcs-Git): bugz dajax

Re: How does team maintenace of python module works?

On 17/02/2013 07:10, Barry Warsaw wrote: > [...] > OTOH, there's no doubt there are rough edges. Heck, I would even support a > transition to git if the workflow were largely similar to Ubuntu's source > branches, but with better quilt integration. To me, something like that is my > packaging nir

Re: How does team maintenace of python module works?

On Feb 16, 2013, at 05:51 PM, Scott Kitterman wrote: >You'd also have to get some consensus around full source or debian directory >only branches. I don't think we can split on that either. Agreed! >Personally, I've found nothing but frustration from trying to manage both >Debian packaging and

Re: How does team maintenace of python module works?

On Feb 16, 2013, at 05:10 PM, Thomas Goirand wrote: >3) Upstream uses Git, and I have already lots of git things inside my >package and workflow (I already explained, I have no choice at all), >plus I know there's others willing to use Git, and not having the >possibility to do team work with them

Re: How does team maintenace of python module works?

On Sat, Feb 16, 2013 at 03:27:08PM +0100, Jakub Wilk wrote: > * Scott Kitterman , 2013-02-16, 09:10: > >On Saturday, February 16, 2013 12:43:02 PM Thomas Kluyver wrote: > >>The following four positions have all been advocated in this thread: > >> > >>A - Maintain the status quo, in which DPMT packa

Re: How does team maintenace of python module works?

On Sunday, February 17, 2013 10:35:01 AM Robert Collins wrote: > On 17 February 2013 08:29, Dmitrijs Ledkovs wrote: > > On 16 February 2013 14:27, Jakub Wilk wrote: > >> * Scott Kitterman , 2013-02-16, 09:10: > >>> On Saturday, February 16, 2013 12:43:02 PM Thomas Kluyver wrote: > The follow

Re: How does team maintenace of python module works?

On 16 February 2013 21:35, Robert Collins wrote: > On 17 February 2013 08:29, Dmitrijs Ledkovs wrote: >> On 16 February 2013 14:27, Jakub Wilk wrote: >>> * Scott Kitterman , 2013-02-16, 09:10: On Saturday, February 16, 2013 12:43:02 PM Thomas Kluyver wrote: > > The following fo

Re: How does team maintenace of python module works?

On 17 February 2013 08:29, Dmitrijs Ledkovs wrote: > On 16 February 2013 14:27, Jakub Wilk wrote: >> * Scott Kitterman , 2013-02-16, 09:10: >>> >>> On Saturday, February 16, 2013 12:43:02 PM Thomas Kluyver wrote: The following four positions have all been advocated in this thread:

Re: How does team maintenace of python module works?

On Saturday 16 February 2013 20:29:07 Dmitrijs Ledkovs wrote: > A, F.1 - Migrate to Mercurial, if and only if mercurial queues are > fully functional and are used to maintain the debian/patches > sub-repository. > > realisticly i am opposed to a mix of version control systems. > > someone to do t

Re: How does team maintenace of python module works?

On 16 February 2013 14:27, Jakub Wilk wrote: > * Scott Kitterman , 2013-02-16, 09:10: >> >> On Saturday, February 16, 2013 12:43:02 PM Thomas Kluyver wrote: >>> >>> The following four positions have all been advocated in this thread: >>> >>> A - Maintain the status quo, in which DPMT packages may

Re: How does team maintenace of python module works?

On 02/16/2013 08:36 PM, Tristan Seligmann wrote: > But this is exactly the point; if team members are doing work in SVN, > then your packages in Git are not benefitting from this work. Let's be practical for a bit. Some members of the team already said they like to use Git. So we wont have everyo

Re: How does team maintenace of python module works?

* Scott Kitterman , 2013-02-16, 09:10: On Saturday, February 16, 2013 12:43:02 PM Thomas Kluyver wrote: The following four positions have all been advocated in this thread: A - Maintain the status quo, in which DPMT packages may only be maintained in SVN. B - As A, but encourage the creation o

Re: How does team maintenace of python module works?

On Saturday, February 16, 2013 12:43:02 PM Thomas Kluyver wrote: > On 16 February 2013 09:10, Thomas Goirand wrote: > > It would be really stupid to only want to "claim" to be working as part > > of the team, that's not at all what I want to do. I'd like to be able to > > help when I can, and rece

Re: How does team maintenace of python module works?

On Sat, Feb 16, 2013 at 11:10 AM, Thomas Goirand wrote: > Oh! Are you *sure* this is what you think of me? It's quite shocking to > read that. It's not that at all. It's: It's what I think are the practical consequences of what you propose. > team)! Well, if I'm not allowed to use Git within the

Re: How does team maintenace of python module works?

On 16 February 2013 09:10, Thomas Goirand wrote: > It would be really stupid to only want to "claim" to be working as part > of the team, that's not at all what I want to do. I'd like to be able to > help when I can, and receive help when I need, which is the point of a > team. > I agree there a

Re: How does team maintenace of python module works?

Tristan Seligmann wrote: > I don't think forming a separate team would be silly at all. I agree with absolutely all of what Ansgar wrote about this. What is important is people doing the work, and being able to find advices. In other words: team work. > When you say "I want to maintain my packag

Re: How does team maintenace of python module works?

On 02/15/2013 01:39, Tristan Seligmann wrote: > I don't think forming a separate team would be silly at all. If you > have a group of people working on Python packages in Git, and a > separate group of people working on Python packages in SVN, what use > is there in pretending that they're the same

Re: How does team maintenace of python module works?

On 02/15/2013 05:21 PM, Dmitry Shachnev wrote: > On Thu, Feb 14, 2013 at 10:54 PM, Thomas Goirand wrote: >> 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

Re: How does team maintenace of python module works?

On Thu, Feb 14, 2013 at 10:54 PM, Thomas Goirand wrote: > 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* > written such thing, so could

Re: How does team maintenace of python module works?

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

  1   2   >