Account Options>

  1. Sign in
VXL Version Control Survey
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
$
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
|
 
Still loading...
ABCDEFGHIJKLMNOPQRSTU
1
TimestampSample Question 1What is your involvement in the VXL community?Would you like to see VXL migrate from subversion to git?What is your level of experience with git?How long have you been a user or maintainer of VXL?What is your name?What is your affiliation?Additional commentsE-mail address
2
1/23/2013 9:40:26I'm an occasional VXL contributer., I'm a VXL user who uses development releases (i.e. trunk)Yes. I would prefer to use git when working with VXL.Experienced (use git on a daily basis, comfortable with branchy work flows, merging, rebasing, etc)10 yearsMatt LeottaKitwarematt.leotta@kitware.com
3
1/23/2013 13:53:06I'm a VXL user who uses development releases (i.e. trunk)Yes. I would prefer to use git when working with VXL.Experienced (use git on a daily basis, comfortable with branchy work flows, merging, rebasing, etc)2 yearsHo CheungUniversity of Houstonhocheung20@gmail.com
4
1/23/2013 13:53:10I'm a VXL user who uses development releases (i.e. trunk), I'm a VXL user who uses stable releasesYes. I would prefer to use git when working with VXL.Experienced (use git on a daily basis, comfortable with branchy work flows, merging, rebasing, etc)~10 yearsRoddy Collinskitwareroddy.collins@kitware.com
5
1/23/2013 14:02:54I'm an occasional VXL contributer.Yes. I would prefer to use git when working with VXL.Expert (comfortable with much of the git internal plumbing, understand the core of how git works)9 yearsRicardo FabbriState University of Rio de Janeiro / Brown University Graduate and CollaboratorYou can find some of my past comments below.

I think using git-svn is too slow and makes codebase dependent on the server, like Matt mentioned. Using git directly is very fast, as Linus is very concerned about performance - he actually codes-in many performance-critical parts of Git - like compression and hashing algorithms - in assembly language. Also, Linus actually wrote Git so that it is very reliable and robust to corruption problems on the server and client - unlike SVN. Other than that, here's what I've recently posted on the maintainers list:

I am 100% for Git. Since I've started using it in 2008 in many
situations - from personal projects to team projects to corporate
environments to writing scientific papers, it has proven to be quite
useful, fast, robust and practical. The main feature I like is to be
able to commit offline (fast), and also to be able to have multiple
branches easily to develop new features. Having the whole history
available has also helped a lot in hunting down and fixing bugs.
Moving to Git is a major gain (unlike CVS to SVN).
rfabbri@gmail.com
6
1/23/2013 14:02:15I'm an occasional VXL contributer.I don't care.Novice (use git occasionally, understand basic operations, more comfortable using git in a linear way like CVS or SVN) several years
7
1/23/2013 14:35:33I'm an active VXL maintainer and frequent contributer.Yes. I would prefer to use git when working with VXL.Novice (use git occasionally, understand basic operations, more comfortable using git in a linear way like CVS or SVN) 7 yearsIsabel RestrepoBrown Universitymaria_resstrepo@brown.edu
8
1/23/2013 14:36:31I'm a VXL user who uses stable releasesYes. I would prefer to use git when working with VXL.Experienced (use git on a daily basis, comfortable with branchy work flows, merging, rebasing, etc)2 yearsKitware
9
1/23/2013 14:53:06I'm an active VXL maintainer and frequent contributer.Yes. I would prefer to use git when working with VXL.Experienced (use git on a daily basis, comfortable with branchy work flows, merging, rebasing, etc)Amitha PereraKitware, Inc.amitha.perera@kitware.com
10
1/23/2013 14:53:51I'm an active VXL maintainer and frequent contributer.Yes. I would prefer to use git when working with VXL.Expert (comfortable with much of the git internal plumbing, understand the core of how git works)4yChuck AtkinsKitware
11
1/23/2013 15:01:55I'm a VXL user who uses development releases (i.e. trunk)Yes. I would prefer to use git when working with VXL.Experienced (use git on a daily basis, comfortable with branchy work flows, merging, rebasing, etc)2 monthsM JacksonBlueQuartz SoftwareToo hard to just compile what is needed, but that is another topic to discuss.mike.jackson@bluequartz.net
12
1/23/2013 15:31:18I'm an active VXL maintainer and frequent contributer.Yes. I would prefer to use git when working with VXL.No Experience (know about git, have some idea about what it can do, but never used it) ~9 yearsDaniel CrispellVision Systems, Inc.
have used Mercurial and like it a lot. Not familiar enough with git to understand the differences, but willing to learn. (Mercurial is somewhat more "user friendly" from what I gather, though)
dan@visionsystemsinc.com
13
1/23/2013 16:45:36I'm a VXL user who uses development releases (i.e. trunk), I'm a VXL user who uses stable releasesNo. I see no benefit to working with git, and I would prefer to stick with subversion.No Experience (know about git, have some idea about what it can do, but never used it) 3 years
14
1/23/2013 17:18:40I'm an active VXL maintainer and frequent contributer.Yes. I would prefer to use git when working with VXL.No Experience (know about git, have some idea about what it can do, but never used it) 12 yearsJoseph L. MundyBrown University
15
1/23/2013 18:00:01I'm an occasional VXL contributer., I'm a VXL user who uses development releases (i.e. trunk)I don't care.Novice (use git occasionally, understand basic operations, more comfortable using git in a linear way like CVS or SVN) 11 yearsFred WheelerGEMy impression is that Git is the way of the future (present?) and VXL should adopt it to stay current. This should largely be a decision made by the current frequent contributors to VXL. I am happy to learn Git as needed if/when VXL makes this move.fred.wheeler@gmail.com
16
1/23/2013 21:07:23I'm a VXL user who uses development releases (i.e. trunk)Yes. I would prefer to use git when working with VXL.Experienced (use git on a daily basis, comfortable with branchy work flows, merging, rebasing, etc)7yearJudaKitware
17
1/23/2013 21:40:54Former VXL user who may use it again some timeMaybe. I see benefits to working with git, but I also see good reasons to stick with subversion.Experienced (use git on a daily basis, comfortable with branchy work flows, merging, rebasing, etc)4 yearsWright State University
18
1/23/2013 22:54:08I'm a VXL user who uses stable releasesI don't care.Novice (use git occasionally, understand basic operations, more comfortable using git in a linear way like CVS or SVN)
19
1/24/2013 6:12:28I'm an occasional VXL contributer.Maybe. I see benefits to working with git, but I also see good reasons to stick with subversion.No Experience (know about git, have some idea about what it can do, but never used it) 13 yearsIan ScottImorphicsI am concerned about history. We need to be able to find old versions of VXL. If the svn version numbers and tags can be transferred to git, that would be ideal.

If that isn't going to happen, we'll need to keep a read-only copy of the subversion repository so the existing version citations in users' internal code repositories can still be dereferenced.

I've had a look around a few gitweb sites, and I think it may take a bit of effort to get used to the git approach to history when investigation regressions.

scottim@imorphics.com
20
1/24/2013 7:27:21I'm an occasional VXL contributer., I'm a VXL user who uses stable releasesYes. I would prefer to use git when working with VXL.Experienced (use git on a daily basis, comfortable with branchy work flows, merging, rebasing, etc)6 yearsPeter CarrDisney ResearchDoes SourceForge have the same support for forking and issuing pull requests like GitHub? From my xperience, that seems to be much more popular for contributing code to existing projects than branching and merging.peter.carr@disneyresearch.com
21
1/24/2013 12:30:47I'm a VXL user who uses development releases (i.e. trunk)Yes. I would prefer to use git when working with VXL.Experienced (use git on a daily basis, comfortable with branchy work flows, merging, rebasing, etc)4 yearsBrandon MayerBrown UniversityI use git and github on a daily basis and prefer it over all other methods of version control that I know of.b.mayer1@gmail.com
22
1/24/2013 22:22:09I'm an active VXL maintainer and frequent contributer.Maybe. I see benefits to working with git, but I also see good reasons to stick with subversion.No Experience (know about git, have some idea about what it can do, but never used it) 8yrDualAlign LLC
23
1/25/2013 15:24:22I'm an active VXL maintainer and frequent contributer.Yes. I would prefer to use git when working with VXL.Novice (use git occasionally, understand basic operations, more comfortable using git in a linear way like CVS or SVN) 7 yearsIsabel RestrepoBrown Universitymaria_resstrepo@brown.edu
24
1/28/2013 2:44:37I'm an active VXL maintainer and frequent contributer.Maybe. I see benefits to working with git, but I also see good reasons to stick with subversion.No Experience (know about git, have some idea about what it can do, but never used it) more than 20 yearsPeter VanrooseABIS Training & Consulting, Leuven, Belgium
25
1/28/2013 10:11:41I'm an occasional VXL contributer.Maybe. I see benefits to working with git, but I also see good reasons to stick with subversion.None (what is git?)Lianqing Yuyulq@live.cn
26
2/1/2013 7:28:02I'm a VXL user who uses development releases (i.e. trunk)Yes. I would prefer to use git when working with VXL.Novice (use git occasionally, understand basic operations, more comfortable using git in a linear way like CVS or SVN)
27
3/4/2013 10:44:37I'm an occasional VXL contributer., I'm a VXL user who uses stable releasesYes. I would prefer to use git when working with VXL.Experienced (use git on a daily basis, comfortable with branchy work flows, merging, rebasing, etc)3-4 YearsArslan BasharatKitware, Inc.arslan.basharat@kitware.com
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Sheet1