[Python-apps-team] Maintain package with Git?

[Dmitrijs Ledkovs]

On 15 November 2012 17:04, Thomas Koch <thomas at koch.ro> wrote:
> W. Martin Borgert:
>> Quoting "Jakub Wilk" <jwilk at debian.org>:
>> > No. We use Subversion.
>>
>> Opion from another unimportant team member:
>>
>> We currently use SVN and I really appreciate that we use only
>> one version control system for all packages of the team. I
>> would, however, accept a general change from Subversion to
>> git, maybe in the timeframe from wheezy release to jessie
>> freeze, if there is a rough consensus about it.
>
> Nice to hear that there's hope... :-) It's funny how you all call yourself
> "unimportant team member". What defines an important team member? But I don't
> want to discuss this.
>

I am also an "unimportant team member".
Nothing is preventing individual people to use {hg,git,bzr}-svn
bridges to interface with the teams svn repository. If you really need
specific features of your VCS.

Before diving into this discussion please google for "git" "bzr" "hg"
in the mailing list archives of the debian-python / apps / modules
lists.

There are benefits which come from participating in the python teams:
* code review of the commit messages
* IRC notifications
* rapid sponsorship (from VCS) and review
* help fixing bugs
* drive-by fixes by team members
* mass bug filing & fixing

To get these benefits, it is expected to play along and use the team
infrastructure.

So far it works very well for both regular contributors and individual
maintainers of single packages.

Other solutions and VCS require changes to the team's toolset and
workflows. While there are subjective benefits to individuals who keep
on proposing the change, so far nobody tried to understand current
usage and services integrated around the central repository.

Also I urge everyone to upgrade to svn1.7 it's very fast and finally
does not pollute directories with .svn dirs.

Regards,

Dmitrijs.