On Thu, Feb 14, 2013 at 5:08 PM, Thomas Goirand <z...@debian.org> 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 that we should form another Alioth project for > that? Wouldn't that be silly? What are the alternatives that you see, if > we are a lot of people willing to do python module team maintenance > using Git?
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 group when they're effectively separate anyway? Of course, there may be some people who are interested in working on both teams, but there's nothing stopping you being a member of both teams if you choose to do so. When you say "I want to maintain my packages in Git, in the team", there are really only two possible implications that I can see: 1) "I want everyone in the team to comply with this way of doing things, even though they don't want to do so", and 2) "I want to do things my own way separate from the rest of the team, but claim to be working as part of the team". Now, written that way, perhaps you can see why this produces a negative reaction from some existing team members, even if you did not mean it in that way? The purpose of the team is to share the maintenance and infrastructure burden for the packages included under the team's umbrella; when you split that infrastructure, you effectively fork the team even if you do not give the fork a new name. Such a fork naturally causes a division of effort, but if you feel that Git vs. SVN makes enough of a difference, then I see no reason why you shouldn't collaborate with other people who feel the same way; it doesn't have to be a "hostile" fork. -- mithrandi, i Ainil en-Balandor, a faer Ambar -- 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/camckhmsu-_0+ovjqrgfomkp3d8swz8pjc3g4i5h6lb8tnxu...@mail.gmail.com
