On Aug 06, 2014, at 08:47 AM, Raphael Hertzog wrote: >(That said I'm also rather annoyed by the fact that the team hasn't switched >to git yet.)
We've had these discussions on this mailing list before, but I think we should discuss it at Debconf. While obviously we won't have full representation (whatever that means ;) from team members, we should take advantage of the high bandwidth setting to discuss the future vcs for the Python teams. In the past we've all had the important and worthy goal of using a consistent packaging and workflow for team maintained projects. However, if folks are abandoning the team in order to use git, then we already have fragmentation, and it will only increase. I'm not particularly a git fan, but it's clear where this is heading. :) I don't think the question is if, but when and how. There are at least two git-based packaging tools and workflows: gbp and git-dpm. In my limited exposure, I've had problems with the former but have been pretty happy with the latter. There's also this interesting thread: https://lists.ubuntu.com/archives/ubuntu-devel/2014-August/038418.html What I really want to avoid is having to think about which vcs or workflow team packages have adopted. I really value the ability to use the same tool (svn-buildpackage) and workflow for all team packages. It makes it easy to do drive-by fixes and updates. I'm happy to adopt something else, but I don't want to adopt 5, 10, or M number of something elses. ;) We need a plan for transition, documentation for team members, and volunteers to see it through. I am offering to help. I hope the intersection of Debian, Python, and git fans will come to Debconf and help us lay the groundwork for a successful team-wide transition. Cheers, -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140806091809.5c942...@anarchist.wooz.org
