From: Jakub Narebski <hidden> Date: 2016-06-15 22:44:59
It's been around a year since last Git User's Survey. It would be
interesting to find what changed since then. For example to see if
there were visible improvements in easing learning curve and in
usability. Therefore the idea to have another survey.
(If there is no suck^W volunteer to create survey, announce it, and
finally summarize results and publish summary on Git Wiki, I would do
the 2008 survey.)
First there is a question about the form of survey. Should we use web
based survey, as the survey before (http://www.survey.net.nz), sending
emails with link to this survey, or perhaps do email based survey,
with email Reply-To: address put for this survey alone? Should we use
the same web survey service as before (found by Paolo Ciarrocchi for
first, 2006 survey, and used also for 2007 survey), or is there one
better (it would better be free, and without limitations on the number
of responses; in 2006 there were around 117 responses, in 2007 there
were 683 individual responses).
Second, what questions should be put in the survey, and in the case of
single choice and ultiple choice questions what possible answers
should be? I'd rather avoid free-form questions, even if they are more
interesting, as they are PITA to analyse and summarize, especially to
create some kind of histogram from free-form replies data (some of 2007
free-form responses are not fully summarized even now). Below are
slightly extended questions from the last survey. Please comment on
it.
Third, where to send survey to / where to publish information about the
survey? Last year the announcement was send to git mailing list, to
LKML (Linux kernel mailing list), and mailing list for git projects
found on GitProjects page on GIT wiki. Now that the number of projects
using Git as version control system has grown, I don't think it would
be good idea to "spam" all those mailing list; and if we don't send
notice to all other projects I'm not sure if we should include LKML.
Last year survey announcement was put on Git Homepage (thanks Pasky),
and on front page of Git Wiki; info about survey was also put on two
git hosting sites: kernel.org and repo.or.cz. It would be nice if it
was possible to put announcement about Git User's Survey 2008 at front
pages of other Git hosting sites, like GitHub (one of most popular, I
think), Gitorious, Freedesktop.org. If you know some other popular Git
hosting sites, and even better if you know who to contact about putting
survey announcement, please write. Is there some channel that I have
forgot about? Should info/announcement about Git User's Survey 2008 be
sent also to one of on-line magazines like LinuxToday or LWN, or asked
to put on some blog? I'll add it as journal entry for #git on Ohloh,
and try to make it so it would appear in "News" section for Ohloh
project page for Git: http://www.ohloh.net/projects/git.
Fourth, how long should the survey last? When sending announcement we
should say where notice about Git User's Survey 2008 should be taken
down. Last year the survey was meant to take three weeks, but was up
longer.
Below there is initial version of announcement email (I should probably
come up also with boilerplate announcement for web pages), and initial
version of this year round of questions. Comments are prefixed by '+',
and does not mean to be included in the survey text.
----
Hi all,
We would like to ask you a few questions about your use of the Git
version control system. This survey is mainly to understand who is
using Git, how and why.
The results will be published to the Git wiki and discussed on the git
mailing list.
We'll close the survey in <duration> starting from today, <date>.
Please devote a few minutes of your time to fill this simple
questionnaire, it will help a lot the git community to understand your
needs, what you like of git, and of course what you don't like of it.
The survey can be found here:
<survey URL>
----
About you
01. What country are you in?
02. What is your preferred non-programming language?
(or) What is the language you want computer communicate with you?
03. How old are you (in years)?
(free form, integer)
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Getting started with GIT
05. How did you hear about Git?
(single choice?, in 2007 it was free-form)
- Linux kernel news (LKML, LWN, KernelTrap, KernelTraffic,...),
news site or magazine, blog entry, some project uses it,
presentation or seminar (real life, not on-line), SCM research,
IRC, mailing list, other Internet, other off-line, other(*)
+ the problem is with having not very long list (not too many
choices), but spanning all possibilities.
+ is this question interesting/important to have in survey?
06. Did you find GIT easy to learn?
- very easy/easy/reasonably/hard/very hard
07. What helped you most in learning to use it?
(free form question)
08. What did you find hardest in learning Git?
What did you find harderst in using Git?
(free form question)
09. When did you start using git? From which version?
- pre 1.0, 1.0, 1.1, 1.2, 1.3, 1.4, 1.5
+ might be important when checking "what did you find hardest" etc.
+ perhaps we should ask in addition to this question, or in place
of this question (replacing it) what git version one uses; it
should be multiple choice, and allow 'master', 'next', 'pu',
'dirty (with own modifications)' versions in addition.
Other SCMs (shortened compared with 2007 survey)
10. What other SCM did or do you use?
(zero or more: multiple choice)
- CVS, Subversion, GNU Arch or arch clone (ArX, tla, ...),
Bazaar-NG, Darcs, Mercurial, Monotone, SVK, AccuRev, Perforce,
BitKeeper, ClearCase, MS Visual Source Safe, MS Visual Studio
Team System, custom, other(*)
10b.If you selected other above, what SCM it was?
(free form)
11. Why did you choose Git? (if you use Git)
What do you like about using Git?
(free form, not to be tabulated)
12. Why did you choose other SCMs? (if you use other SCMs)
What do you like about using other SCMs?
Note: please write name of SCMs you are talking about.
(free form, not to be tabulated).
How you use Git
13. Do you use Git for work, unpaid projects, or both?
(single choice)
- work/unpaid projects/both
14. How do you obtain Git?
- binary package/source package or source script(*)/
source tarball/pull from main repository
(*) this includes source based distributions like Gentoo
+ added new option: source package or source script
+ should this be multiple choice?
15. What operating system do you use Git on?
(one or more: multiple choice, as one can use more than one OS)
- Linux, *BSD (FreeBSD, OpenBSD, etc.), MS Windows/Cygwin,
MS Windows/msysGit, MacOS X, other UNIX, other
+ "What hardware platforms do you use GIT on?" question was
removed; should it stay?
15b.If you selected "other UNIX", or "other", what operating system
or systems it was/were?
(free form)
16. Which porcelains / interfaces / implementations do you use?
(zero or more: multiple choice)
- core-git, Cogito (deprecated), StGIT, Guilt, pg (deprecated),
Pyrite, Easy Git, IsiSetup, jgit, my own scripts, other
16b.If you selected "other porcelain", what is its name?
(free form)
17. Which git GUI (commit tool or history viewer, or both) do you use
(zero or more: multiple choice)
- CLI, gitk, git-gui, qgit, gitview, giggle, tig, instaweb,
(h)gct, qct, KGit, git-cola / ugit, GitNub, Pyrite, git.el, other
17b.If you selected "other GUI", what is its name?
(free form)
18. Which (main) git web interface do you use for your projects?
(zero or more: multiple choice)
- gitweb, cgit, wit (Ruby), git-php, viewgit (PHP), other
+ should there be a question about web server (Apache, IIS, ...)
used to host git web interface?
18b.If you selected "other web interface", what it was?
(free form)
19. How do you publish/propagate your changes?
(zero or more: multiple choice)
- push, pull request, format-patch + email, bundle, other
19b.If the way you publish your changes is not mentioned above, how
do you publish your changes?
(free form)
20. Does git.git repository include code produced by you?
- yes/no
What you think of Git
21. Overall, how happy are you with Git?
- unhappy/not so happy/happy/very happy/completely ecstatic
22. How does Git compare to other SCM tools you have used?
- worse/equal (or comparable)/better
23. What would you most like to see improved about Git?
(features, bugs, plug-ins, documentation, ...)
24. If you want to see Git more widely used, what do you
think we could do to make this happen?
+ Is this question necessary/useful? Do we need wider adoption?
Changes in Git (since year ago, or since you started using it)
25. Did you participate in previous Git User's Surveys?
(zero or more, multiple choice)
- 2006, 2007
26. How do you compare current version with version from year ago?
- current version is: better/worse/no changes
27. Which of the following features do you use?
(zero or more: multiple choice)
- git-gui or other commit tool, gitk or other history viewer, patch
management interface (e.g. StGIT), bundle, eol conversion,
gitattributes, submodules, separate worktree, reflog, stash,
shallow clone, detaching HEAD, mergetool, interactive rebase,
add --interactive or other partial commit helper, commit
templates, bisect, other (not mentioned here)
+ should probably be sorted in some resemblance of order
+ are there any new features which should be listed here?
28. If you use some important Git features not mentioned above,
what are it?
(free form)
Documentation
29. Do you use the Git wiki?
- yes/no
30. Do you find Git wiki useful?
- yes/no/somewhat
31. Do you contribute to Git wiki?
- yes/no/only corrections or spam removal
32. Do you find Git's on-line help (homepage, documentation) useful?
- yes/no/somewhat
33. Do you find help distributed with Git useful
(manpages, manual, tutorial, HOWTO, release notes)?
- yes/no/somewhat
34. What could be improved on the Git homepage?
(free form)
35. What could be improved in Git documentation?
(free form)
Getting help, staying in touch
36. Have you tried to get Git help from other people?
- yes/no
37. What channel did you use to request help?
(zero or more: multiple choice)
- git mailing list, git users group, IRC, blog post,
other
+ this is one question which doesn't need, I think, explanation
of "other" choice
38. If yes, did you get these problems resolved quickly
and to your liking?
- yes/no
39. Would commerical (paid) support from a support vendor
be of interest to you/your organization?
- yes/no/not applicable
40. Do you read the mailing list?
- yes/no
41. If yes, do you find it useful?
- yes/no (optional)
42. Do you find traffic levels on Git mailing list OK.
- yes/no? (optional)
43. Do you use the IRC channel (#git on irc.freenode.net)?
- yes/no
44. If yes, do you find IRC channel useful?
- yes/no (optional)
45. Did you have problems getting GIT help on mailing list or
on IRC channel? What were it? What could be improved?
(free form)
Open forum
46. What other comments or suggestions do you have that are not
covered by the questions above?
(free form)
--
Jakub Narebski
Poland
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:45:00
Hi,
On Wed, 23 Jul 2008, Jakub Narebski wrote:
First there is a question about the form of survey. Should we use web
based survey, as the survey before (http://www.survey.net.nz), sending
emails with link to this survey, or perhaps do email based survey,
with email Reply-To: address put for this survey alone?
Some people prefer to stay anonymous, so I think email is out.
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Yes, I think this should be a long list.
07. What helped you most in learning to use it?
(free form question)
Is it possible to have multiple choice, with "other" (free-form)? Then
I'd suggest:
Colleague/Instructor, User Manual, Manpages, Tutorials, Tutorials
(elsewhere; not in git.git), Mailing list, IRC, Git Wiki, Other.
08. What did you find hardest in learning Git?
What did you find harderst in using Git?
s/harderst/hardest.
(free form question)
Again, I'd suggest a multiple choice + Other:
The amount of commands, the amount of options, the index (AKA
staging), branching, user interface, bugs, Other.
Other SCMs (shortened compared with 2007 survey)
10. What other SCM did or do you use?
(zero or more: multiple choice)
- CVS, Subversion, GNU Arch or arch clone (ArX, tla, ...),
Bazaar-NG, Darcs, Mercurial, Monotone, SVK, AccuRev, Perforce,
BitKeeper, ClearCase, MS Visual Source Safe, MS Visual Studio
Team System, custom, other(*)
PVCS seems to be pretty popular, too.
11. Why did you choose Git? (if you use Git)
What do you like about using Git?
(free form, not to be tabulated)
Again, to avoid hassles with free-form:
Mandatory: work, mandatory: open source project I am participating
in, speed, scalability, It's What Linus Uses, Other.
12. Why did you choose other SCMs? (if you use other SCMs)
What do you like about using other SCMs?
Note: please write name of SCMs you are talking about.
(free form, not to be tabulated).
Again:
ease-of use, simplicity, existing project uses it, I Do Not Like
Linus, Other
15. What operating system do you use Git on?
(one or more: multiple choice, as one can use more than one OS)
- Linux, *BSD (FreeBSD, OpenBSD, etc.), MS Windows/Cygwin,
MS Windows/msysGit, MacOS X, other UNIX, other
You should include "Dunno", which gets automatically mapped to "MS
Windows/msysGit" ;-)
19. How do you publish/propagate your changes?
(zero or more: multiple choice)
- push, pull request, format-patch + email, bundle, other
git svn
You might laugh, but it is a sad fact that some guy promotes "Using Git
with Google Code" by using git-svn to drive their crappy Subversion.
22. How does Git compare to other SCM tools you have used?
- worse/equal (or comparable)/better
23. What would you most like to see improved about Git?
(features, bugs, plug-ins, documentation, ...)
Maybe here should be another question "What are the most useful features
of Git?" but maybe that is covered by earlier questions.
24. If you want to see Git more widely used, what do you
think we could do to make this happen?
+ Is this question necessary/useful? Do we need wider adoption?
I agree with Junio: this is not so interesting for us; we are no company,
and we have no sales department who could wank of on these answers.
27. Which of the following features do you use?
(zero or more: multiple choice)
- git-gui or other commit tool, gitk or other history viewer, patch
management interface (e.g. StGIT), bundle, eol conversion,
For our Windows friends, we should add " (crlf)" to the last item.
42. Do you find traffic levels on Git mailing list OK.
- yes/no? (optional)
/too low? *ducksandrunsforcover*
44. If yes, do you find IRC channel useful?
- yes/no (optional)
/somewhat. Even if I would be the only one choosing that option.
45. Did you have problems getting GIT help on mailing list or
on IRC channel? What were it? What could be improved?
(free form)
Yeah, I know who will answer to that, and what... "yaddayadda very
unfriendly yaddayadda especially that Johannes guy yaddayadda" (you know
who you are)... *lol*
Thanks Jakub, I think that your effort is very useful.
Ciao,
Dscho
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:00
On Wed, 23 Jul 2008, Johannes Schindelin wrote:
On Wed, 23 Jul 2008, Jakub Narebski wrote:
Some people prefer to stay anonymous, so I think email is out.
quoted
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Yes, I think this should be a long list.
I'd rather not have a "laundry list" of languages. I have put C++
because QGit uses it, Java because of egit/jgit, PHP for web
interfaces, Ruby because of GitHub and because of Ruby comminity
choosing Git. I should perhaps add Emacs Lisp, HTML+CSS and
JavaScript here. What other languages should be considered?
quoted
07. What helped you most in learning to use it?
(free form question)
Is it possible to have multiple choice, with "other" (free-form)? Then
I'd suggest:
Colleague/Instructor, User Manual, Manpages, Tutorials, Tutorials
(elsewhere; not in git.git), Mailing list, IRC, Git Wiki, Other.
By "Tutorials (elsewhere; not in git.git)" you mean here many various
"git guide" pages, like "Git for Computer Scientists", "Git Magic",
etc.?
I'm not sure about having multiple choice vs. free-form question here.
Multiple choice is easier to analyze, especially if one would want
histogram of replies... but free form is more rich. But perhaps
multiple choice with free-form "other" choice would be the best?
Besides proposed choices limit person filling the survey to single
understanding of "what helped you in learning to use Git", which
can be also understood as asking for list of features helping with
learning Git, not only list of documentation and such.
quoted
08. What did you find hardest in learning Git?
What did you find harderst in using Git?
s/harderst/hardest.
quoted
(free form question)
Again, I'd suggest a multiple choice + Other:
The amount of commands, the amount of options, the index (AKA
staging), branching, user interface, bugs, Other.
Here it can be hard to come up with good list of choices. For example
among responses in 2007 survey there were 'inconsistent commands',
'obtuse command messages', 'insufficient/hard to use documentation',
and many more.
I'm not sure if troubles with coming with extensive but not too large
list of options for this question is worth it; I think that we need
only list of responses, and not number of responses (perhaps mentioning
which one occur [much] more frequently).
quoted
Other SCMs (shortened compared with 2007 survey)
10. What other SCM did or do you use?
(zero or more: multiple choice)
- CVS, Subversion, GNU Arch or arch clone (ArX, tla, ...),
Bazaar-NG, Darcs, Mercurial, Monotone, SVK, AccuRev, Perforce,
BitKeeper, ClearCase, MS Visual Source Safe, MS Visual Studio
Team System, custom, other(*)
PVCS seems to be pretty popular, too.
O.K., I'll add it. I think I'd better add RCS too.
quoted
11. Why did you choose Git? (if you use Git)
What do you like about using Git?
(free form, not to be tabulated)
Again, to avoid hassles with free-form:
Mandatory: work, mandatory: open source project I am participating
in, speed, scalability, It's What Linus Uses, Other.
Free form has some hassles. Because here histogram of responses might
be interesting, perhaps it would be good to use multiple choice here.
I would add "features" and/or "unique features" to the list, and also
perhaps "being popular/hype".
quoted
12. Why did you choose other SCMs? (if you use other SCMs)
What do you like about using other SCMs?
Note: please write name of SCMs you are talking about.
(free form, not to be tabulated).
Again:
ease-of use, simplicity, existing project uses it, I Do Not Like
Linus, Other
Again: free form has some hassles, but so does coming up with good
choice of fixed answers in multiple choice question. I'll add
"ease to install on MS Windows" (or something like that) if we decide
to have this question multiple choice.
quoted
15. What operating system do you use Git on?
(one or more: multiple choice, as one can use more than one OS)
- Linux, *BSD (FreeBSD, OpenBSD, etc.), MS Windows/Cygwin,
MS Windows/msysGit, MacOS X, other UNIX, other
You should include "Dunno", which gets automatically mapped to "MS
Windows/msysGit" ;-)
quoted
19. How do you publish/propagate your changes?
(zero or more: multiple choice)
- push, pull request, format-patch + email, bundle, other
git svn
You might laugh, but it is a sad fact that some guy promotes "Using Git
with Google Code" by using git-svn to drive their crappy Subversion.
O.K. I'll add "git-svn (or other to foreign SCM)".
quoted
22. How does Git compare to other SCM tools you have used?
- worse/equal (or comparable)/better
23. What would you most like to see improved about Git?
(features, bugs, plug-ins, documentation, ...)
Maybe here should be another question "What are the most useful features
of Git?" but maybe that is covered by earlier questions.
I think it is. I'd rather try to reduce number of questions...
quoted
24. If you want to see Git more widely used, what do you
think we could do to make this happen?
+ Is this question necessary/useful? Do we need wider adoption?
I agree with Junio: this is not so interesting for us; we are no company,
and we have no sales department who could wank of on these answers.
I'll remove it, then.
quoted
27. Which of the following features do you use?
(zero or more: multiple choice)
- git-gui or other commit tool, gitk or other history viewer, patch
management interface (e.g. StGIT), bundle, eol conversion,
For our Windows friends, we should add " (crlf)" to the last item.
Right. Thanks.
quoted
42. Do you find traffic levels on Git mailing list OK.
- yes/no? (optional)
/too low? *ducksandrunsforcover*
???
quoted
44. If yes, do you find IRC channel useful?
- yes/no (optional)
/somewhat. Even if I would be the only one choosing that option.
I'm sorry about that: I have forgot that this and all similar questions
had triple choice: yes/no/somewhat in the final version of 2007 survey.
I'll correct it.
quoted
45. Did you have problems getting GIT help on mailing list or
on IRC channel? What were it? What could be improved?
(free form)
Yeah, I know who will answer to that, and what... "yaddayadda very
unfriendly yaddayadda especially that Johannes guy yaddayadda" (you know
who you are)... *lol*
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:45:00
Hi,
On Wed, 23 Jul 2008, Jakub Narebski wrote:
On Wed, 23 Jul 2008, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
Some people prefer to stay anonymous, so I think email is out.
quoted
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Yes, I think this should be a long list.
I'd rather not have a "laundry list" of languages. I have put C++
because QGit uses it, Java because of egit/jgit, PHP for web
interfaces, Ruby because of GitHub and because of Ruby comminity
choosing Git. I should perhaps add Emacs Lisp, HTML+CSS and
JavaScript here. What other languages should be considered?
C# at least, since we had one (pretty unsuccessful) attempt at
reimplementing Git in it.
quoted
quoted
07. What helped you most in learning to use it?
(free form question)
Is it possible to have multiple choice, with "other" (free-form)?
But perhaps multiple choice with free-form "other" choice would be the
best?
Uhm, yes, you are right. Why not have multiple choice, with "other")
(free-form)?
quoted
quoted
42. Do you find traffic levels on Git mailing list OK.
- yes/no? (optional)
From: Stephan Beyer <hidden> Date: 2016-06-15 22:45:00
Hi,
Jakub Narebski wrote:
I'd rather avoid free-form questions, even if they are more interesting,
as they are PITA to analyse and summarize, especially to create some
kind of histogram from free-form replies data (some of 2007 free-form
responses are not fully summarized even now).
Then we should use a web-based survey, because e-mail-based will always
be used to write free-form answers, I think.
So for multiple choice questions an "Other" item is often useful, but
-- if the survey service allows it -- I'd prefer if the "Other" item
enables a text input field (free-form) to let the user be more concrete.
Those values are informational only, but could be added to Git User's
Survey 2009, if they occur more than once. :)
Third, where to send survey to / where to publish information about the
survey? Last year the announcement was send to git mailing list, to
LKML (Linux kernel mailing list), and mailing list for git projects
found on GitProjects page on GIT wiki. Now that the number of projects
using Git as version control system has grown, I don't think it would
be good idea to "spam" all those mailing list; and if we don't send
notice to all other projects I'm not sure if we should include LKML.
Hmm, perhaps we could spam some news sites[1] on the web and keep the lists
clean. Of course, this is advertising for git, too ;-)
[1] I could write something for German-speaking pro-linux.de and symlink.ch
though I don't know if they take it as news.
Last year survey announcement was put on Git Homepage (thanks Pasky),
and on front page of Git Wiki; info about survey was also put on two
git hosting sites: kernel.org and repo.or.cz.
Nice. That should be done again ;-)
Last year the survey was meant to take three weeks, but was up longer.
Perhaps this is much too much, but my first thought was: 8 weeks.
Hmm, perhaps 5 weeks?
04. Which programming languages you are proficient with?
This is a really nasty multiple choice question.
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
- Linux kernel news (LKML, LWN, KernelTrap, KernelTraffic,...),
news site or magazine, blog entry, some project uses it,
presentation or seminar (real life, not on-line), SCM research,
IRC, mailing list, other Internet, other off-line, other(*)
- other off-line: told by friend, must be used at job, ...
+ the problem is with having not very long list (not too many
choices), but spanning all possibilities.
Hmmm.
Is this a limitation by the free web-based services or is this due to
survey usability issues?
09. When did you start using git? From which version?
- pre 1.0, 1.0, 1.1, 1.2, 1.3, 1.4, 1.5
+ might be important when checking "what did you find hardest" etc.
+ perhaps we should ask in addition to this question, or in place
of this question (replacing it) what git version one uses; it
should be multiple choice, and allow 'master', 'next', 'pu',
'dirty (with own modifications)' versions in addition.
Hmm, the master/next/pu/dirty question will be a mystery to most git users
that have never cared about git source code.
How you use Git
16. Which porcelains / interfaces / implementations do you use?
(zero or more: multiple choice)
- core-git, Cogito (deprecated), StGIT, Guilt, pg (deprecated),
Pyrite, Easy Git, IsiSetup, jgit, my own scripts, other
I wonder if this could be extended to get an idea how many people use
plumbing directly or, even better, add a question like:
Which of the following git commands or extra git tools do you use regularly?
[list of all plumbing, porcelain and tools like stgit, guilt, etc]
or "... have you never used?", or "...have you ever used?"...
Just to get an idea of what commands are often used by the users.
Perhaps it is even useful to extend that list by some behavior-changing
options, like:
[ ] git add
[ ] git add -i / -p
...
[ ] git am
[ ] git am -i
...
[ ] git merge
[ ] git merge with strategy
...
[ ] git rebase
[ ] git rebase -i
...though this is also handled by question 27 (see below).
Yes, this will be a long list :-)
And don't forget the [ ] other :)
Of course this question could be split into
- extra tools
- guis (like question 17.)
- helpers
- porcelain
- plumbings
Question 27. should be in this section, too:
27. Which of the following features do you use?
(zero or more: multiple choice)
- git-gui or other commit tool, gitk or other history viewer, patch
management interface (e.g. StGIT), bundle, eol conversion,
gitattributes, submodules, separate worktree, reflog, stash,
shallow clone, detaching HEAD, mergetool, interactive rebase,
add --interactive or other partial commit helper, commit
templates, bisect, other (not mentioned here)
+ should probably be sorted in some resemblance of order
+ are there any new features which should be listed here?
Hmm, I'd remove "git-gui or other commit tool, gitk or other history
viewer, patch management interface (e.g. StGIT)".
And depending of the question I just proposed, "interactive rebase",
"add --interactive [...]", "bisect" could be removed, too.
18. Which (main) git web interface do you use for your projects?
(zero or more: multiple choice)
- gitweb, cgit, wit (Ruby), git-php, viewgit (PHP), other
+ should there be a question about web server (Apache, IIS, ...)
used to host git web interface?
No, why should we care about the web server? :)
22. How does Git compare to other SCM tools you have used?
- worse/equal (or comparable)/better
23. What would you most like to see improved about Git?
(features, bugs, plug-ins, documentation, ...)
24. If you want to see Git more widely used, what do you
think we could do to make this happen?
+ Is this question necessary/useful? Do we need wider adoption?
Hmmm,
"Do you miss features in git that you know from other SCMs?"
"If yes, what features are these?"
26. How do you compare current version with version from year ago?
- current version is: better/worse/no changes
Since this is single-choice, a "don't know"/"cannot say" option should
be added.
28. If you use some important Git features not mentioned above,
what are it?
"what are it" sounds somehow funny. Is it correct?
"what are them?" or "what are those?"
Or
"If you use some important Git feature not mentioned above, what is it?"
Documentation
29. Do you use the Git wiki?
- yes/no
30. Do you find Git wiki useful?
- yes/no/somewhat
31. Do you contribute to Git wiki?
- yes/no/only corrections or spam removal
32. Do you find Git's on-line help (homepage, documentation) useful?
- yes/no/somewhat
33. Do you find help distributed with Git useful
(manpages, manual, tutorial, HOWTO, release notes)?
- yes/no/somewhat
34. What could be improved on the Git homepage?
(free form)
35. What could be improved in Git documentation?
(free form)
36. Do you think there is too few documentation on the web?
37. Do you think there is too much documentation on the web?
No ;-) Perhaps:
36. Do you think it is easy to find out how to do a specific task with
git?
Open forum
46. What other comments or suggestions do you have that are not
covered by the questions above?
(free form)
About the survey
47. Do you have any comments about the survey?
48. Should such a survey be repeated next year?
(Or: Would you take part in such a survey next year again?)
[ ] Yes
[ ] No, but 2010 again.
[ ] No, never again.
Just a poor idea to get "feedback" if people like to take part in this
survey or not.
Regards,
Stephan
--
Stephan Beyer [off-list ref], PGP 0x6EDDD207FCC5040F
On Wed, Jul 23, 2008 at 03:25:03AM +0200, Jakub Narebski wrote:
02. What is your preferred non-programming language?
(or) What is the language you want computer communicate with you?
IMHO, the later wording of the question is much better.
05. How did you hear about Git?
(single choice?, in 2007 it was free-form)
- Linux kernel news (LKML, LWN, KernelTrap, KernelTraffic,...),
news site or magazine, blog entry, some project uses it,
presentation or seminar (real life, not on-line), SCM research,
IRC, mailing list, other Internet, other off-line, other(*)
I think "friend" would be a reasonable choice here too.
09. When did you start using git? From which version?
- pre 1.0, 1.0, 1.1, 1.2, 1.3, 1.4, 1.5
+ might be important when checking "what did you find hardest" etc.
+ perhaps we should ask in addition to this question, or in place
of this question (replacing it) what git version one uses; it
should be multiple choice, and allow 'master', 'next', 'pu',
'dirty (with own modifications)' versions in addition.
I think: "What version do you use now?" and "How log do you use git?"
may be more useful here. From which version may give rather confusing
results because someone may "start" with 1.4 a week ago just because
that is the version included in Debian Etch and after realizing that
version 1.4 has serious usability issues upgraded git to 1.5. Besides,
1.5 is around for a long time now (as most as long as all previous
versions), so 1.5 can mean either one month of usage or 18 months...
Dmitry
From: Robin Rosenberg <hidden> Date: 2016-06-15 22:45:00
onsdagen den 23 juli 2008 15.18.40 skrev Johannes Schindelin:
Hi,
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
On Wed, 23 Jul 2008, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
Some people prefer to stay anonymous, so I think email is out.
quoted
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Yes, I think this should be a long list.
I'd rather not have a "laundry list" of languages. I have put C++
because QGit uses it, Java because of egit/jgit, PHP for web
interfaces, Ruby because of GitHub and because of Ruby comminity
choosing Git. I should perhaps add Emacs Lisp, HTML+CSS and
JavaScript here. What other languages should be considered?
C# at least, since we had one (pretty unsuccessful) attempt at
reimplementing Git in it.
What is the reason for the question? Do we want to know what languages
people would like to contribute to Git in or do we want to know what "kind"
of programmers are attracted by Git? Making it a long list should make
it easier to tabulate the responses.
-- robin
On Wed, Jul 23, 2008 at 11:53:27AM +0200, Johannes Schindelin wrote:
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
11. Why did you choose Git? (if you use Git)
What do you like about using Git?
(free form, not to be tabulated)
Again, to avoid hassles with free-form:
Mandatory: work, mandatory: open source project I am participating
in, speed, scalability, It's What Linus Uses, Other.
If we move away from free-form, it should be much more choices here.
- Ability to work offline
- Cryptographic authentication of history.
- Distributed development (pull/push from/to more than one remote repo)
- Easy to extend functionality through scripting
- Efficient storage model
- Elegant design
- Fast
- Good community support
- Rewriting patches before publishing (git rebase, commit --amend)
- Scalability (Efficient handling of large projects)
- Strong support for non-linear development
- Support of wide range of protocols for synchronization.
...
Dmitry
On Wed, 2008-07-23 at 18:38 +0400, Dmitry Potapov wrote:
On Wed, Jul 23, 2008 at 03:25:03AM +0200, Jakub Narebski wrote:
quoted
02. What is your preferred non-programming language?
(or) What is the language you want computer communicate with you?
IMHO, the later wording of the question is much better.
I think these are two separate questions. In my case the first is
(swiss) german, the second is english. I don't like localized software
too much, I always have to think what a certain german term might mean
in english to understand computing-specific texts.
That being said I think that the first question is irrelevant for the
git survey. Maybe we should use the term 'internationalization' or
'localization' somewhere to make clear what we are talking about. While
these terms might scare newbies away we can reasonably expect that they
are known by git users.
Matthias
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:45:00
Hi,
On Wed, 23 Jul 2008, Robin Rosenberg wrote:
onsdagen den 23 juli 2008 15.18.40 skrev Johannes Schindelin:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
On Wed, 23 Jul 2008, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
Some people prefer to stay anonymous, so I think email is out.
quoted
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Yes, I think this should be a long list.
I'd rather not have a "laundry list" of languages. I have put C++
because QGit uses it, Java because of egit/jgit, PHP for web
interfaces, Ruby because of GitHub and because of Ruby comminity
choosing Git. I should perhaps add Emacs Lisp, HTML+CSS and
JavaScript here. What other languages should be considered?
C# at least, since we had one (pretty unsuccessful) attempt at
reimplementing Git in it.
What is the reason for the question? Do we want to know what languages
people would like to contribute to Git in or do we want to know what "kind"
of programmers are attracted by Git? Making it a long list should make
it easier to tabulate the responses.
"could contribute" is more appropriate IMHO. Although you might be right
to ask "would like to contribute"... ;-)
Ciao,
Dscho
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:45:00
Hi,
On Wed, 23 Jul 2008, Dmitry Potapov wrote:
On Wed, Jul 23, 2008 at 11:53:27AM +0200, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
11. Why did you choose Git? (if you use Git)
What do you like about using Git?
(free form, not to be tabulated)
Again, to avoid hassles with free-form:
Mandatory: work, mandatory: open source project I am participating
in, speed, scalability, It's What Linus Uses, Other.
If we move away from free-form, it should be much more choices here.
- Ability to work offline
- Cryptographic authentication of history.
Cryptographically strong integrity check. There is no authentication.
- Distributed development (pull/push from/to more than one remote repo)
- Easy to extend functionality through scripting
- Efficient storage model
- Elegant design
- Fast
- Good community support
- Rewriting patches before publishing (git rebase, commit --amend)
- Scalability (Efficient handling of large projects)
- Strong support for non-linear development
- Support of wide range of protocols for synchronization.
...
From: Stephan Beyer <hidden> Date: 2016-06-15 22:45:00
Hi,
Dmitry Potapov wrote:
On Wed, Jul 23, 2008 at 11:53:27AM +0200, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
11. Why did you choose Git? (if you use Git)
What do you like about using Git?
(free form, not to be tabulated)
Again, to avoid hassles with free-form:
Mandatory: work, mandatory: open source project I am participating
in, speed, scalability, It's What Linus Uses, Other.
If we move away from free-form, it should be much more choices here.
- Ability to work offline
- Cryptographic authentication of history.
- Distributed development (pull/push from/to more than one remote repo)
- Easy to extend functionality through scripting
- Efficient storage model
- Elegant design
- Fast
- Good community support
- Rewriting patches before publishing (git rebase, commit --amend)
- Scalability (Efficient handling of large projects)
- Strong support for non-linear development
- Support of wide range of protocols for synchronization.
...
Heh, I can imagine git users reading that survey and thinking
"What? Git allows me to rewrite patches before publishing?
And it provides cryptographic integrity? Sounds good. *click*"
Nevertheless, the list is fine ;)
Perhaps also: "Good reputation".
Regards.
--
Stephan Beyer [off-list ref], PGP 0x6EDDD207FCC5040F
On Wed, Jul 23, 2008 at 05:43:26PM +0200, Matthias Kestenholz wrote:
On Wed, 2008-07-23 at 18:38 +0400, Dmitry Potapov wrote:
quoted
On Wed, Jul 23, 2008 at 03:25:03AM +0200, Jakub Narebski wrote:
quoted
02. What is your preferred non-programming language?
(or) What is the language you want computer communicate with you?
IMHO, the later wording of the question is much better.
I think these are two separate questions. In my case the first is
(swiss) german, the second is english. I don't like localized software
too much, I always have to think what a certain german term might mean
in english to understand computing-specific texts.
Wellcome to the club of those who don't like localized software :)
That being said I think that the first question is irrelevant for the
git survey.
Exactly. That is why I said the later wording is better. I believe the
implied question was what language would you like Git to talk with you.
Dmitry
From: Petr Baudis <hidden> Date: 2016-06-15 22:45:00
On Wed, Jul 23, 2008 at 03:25:03AM +0200, Jakub Narebski wrote:
18. Which (main) git web interface do you use for your projects?
(zero or more: multiple choice)
- gitweb, cgit, wit (Ruby), git-php, viewgit (PHP), other
+ should there be a question about web server (Apache, IIS, ...)
used to host git web interface?
18b.If you selected "other web interface", what it was?
(free form)
I think many people "just use GitHub", or repo.or.cz, or Gitorious; for
GitHub or Gitorious, there's even no good answer to the question above.
So I would either make a separate question for these or include them in
the list above.
19. How do you publish/propagate your changes?
(zero or more: multiple choice)
- push, pull request, format-patch + email, bundle, other
I agree about the git-svn mention.
Petr "Pasky" Baudis
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:00
On Wed, 23 Jul 2008, Dmitry Potapov wrote:
On Wed, Jul 23, 2008 at 03:25:03AM +0200, Jakub Narebski wrote:
quoted
02. What is your preferred non-programming language?
(or) What is the language you want computer communicate with you?
IMHO, the later wording of the question is much better.
First just satisfies demographic curiosity. Second is more question
about internationalization (i18n).
I'm not sure however if it is worth it, and not just simply remove
this question from the survey.
quoted
05. How did you hear about Git?
(single choice?, in 2007 it was free-form)
- Linux kernel news (LKML, LWN, KernelTrap, KernelTraffic,...),
news site or magazine, blog entry, some project uses it,
presentation or seminar (real life, not on-line), SCM research,
IRC, mailing list, other Internet, other off-line, other(*)
I think "friend" would be a reasonable choice here too.
Or: "word of mouth (off-line)". Good catch, thanks.
quoted
09. When did you start using git? From which version?
- pre 1.0, 1.0, 1.1, 1.2, 1.3, 1.4, 1.5
+ might be important when checking "what did you find hardest" etc.
+ perhaps we should ask in addition to this question, or in place
of this question (replacing it) what git version one uses; it
should be multiple choice, and allow 'master', 'next', 'pu',
'dirty (with own modifications)' versions in addition.
I think: "What version do you use now?" and "How long do you use git?"
may be more useful here. From which version may give rather confusing
results because someone may "start" with 1.4 a week ago just because
that is the version included in Debian Etch and after realizing that
version 1.4 has serious usability issues upgraded git to 1.5. Besides,
1.5 is around for a long time now (as most as long as all previous
versions), so 1.5 can mean either one month of usage or 18 months...
Good idea (provided that for "How long do you use git?" there is an
answer "Don't remember").
Should "What version do you use now?" be multiple choice (using git
on more than one machine / operating system)? What should be possible
choices for "How long do you use git?"? Perhaps.
10. How long do you use git?
(single choice)
- never/few days/few weeks/month/few months/year/few years/
from beginning/I wrote it(*)
+ (*) just kidding ;-)
--
Jakub Narebski
Poland
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:00
On Wed, 23 Jul 2008, Petr Baudis wrote:
On Wed, Jul 23, 2008 at 03:25:03AM +0200, Jakub Narebski wrote:
quoted
18. Which (main) git web interface do you use for your projects?
(zero or more: multiple choice)
- gitweb, cgit, wit (Ruby), git-php, viewgit (PHP), other
+ should there be a question about web server (Apache, IIS, ...)
used to host git web interface?
18b.If you selected "other web interface", what it was?
(free form)
I think many people "just use GitHub", or repo.or.cz, or Gitorious; for
GitHub or Gitorious, there's even no good answer to the question above.
For Gitorious there is a good answer: Gitorious web interface (which
is OSS, and you can deploy on your own).
So I would either make a separate question for these or include them in
the list above.
Fact, I have forgot to add question about which git hosting site one
uses; I have meant to add it in the second version of proposal for
Git User's Survey 2008 questions list.
xx. Which git hosting site do you use for your projects?
(zero or more: multiple choice)
- repo.or.cz, GitHub, Gitorious, kernel.org, freedesktop.org,
Savannah, Assembla, Unfuddle, Alioth, Fedora Hosted, other
+ of course "if other, which"
+ should some other web hosting sites be included as well?
quoted
19. How do you publish/propagate your changes?
(zero or more: multiple choice)
- push, pull request, format-patch + email, bundle, other
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:00
Dnia środa 23. lipca 2008 16:54, Robin Rosenberg napisał:
onsdagen den 23 juli 2008 15.18.40 skrev Johannes Schindelin:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
On Wed, 23 Jul 2008, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Yes, I think this should be a long list.
I'd rather not have a "laundry list" of languages. I have put C++
because QGit uses it, Java because of egit/jgit, PHP for web
interfaces, Ruby because of GitHub and because of Ruby comminity
choosing Git. I should perhaps add Emacs Lisp, HTML+CSS and
JavaScript here. What other languages should be considered?
C# at least, since we had one (pretty unsuccessful) attempt at
reimplementing Git in it.
What is the reason for the question? Do we want to know what languages
people would like to contribute to Git in or do we want to know what "kind"
of programmers are attracted by Git? Making it a long list should make
it easier to tabulate the responses.
The idea is, I think, to know what languages people could contribute
to Git; see analysis of this question at GitSurvey2007 page on git wiki:
http://git.or.cz/gitwiki/GitSurvey2007#head-ecb5564d71e4093e2e93e508380407a26dbcbdea
C++ is for QGit, Java for egit/jgit, C# for git#/widgit and perhaps
Git-Cheetah, PHP for web interfaces, Ruby because of GitHub, Python
because some contrib is in Python, Emacs Lisp for git.el, HTML+CSS
and JavaScript for web interfaces; perhaps we should also add AsciiDoc
for documentation. And of course "I am not programmer" response...
But I'm not too tied to this question; I guess it can be simply
removed if it doesn't offer some important (for us) information.
--
Jakub Narebski
Poland
From: Stephan Beyer <hidden> Date: 2016-06-15 22:45:00
Hi,
Jakub Narebski wrote:
Dnia ?roda 23. lipca 2008 16:54, Robin Rosenberg napisa?:
quoted
onsdagen den 23 juli 2008 15.18.40 skrev Johannes Schindelin:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
On Wed, 23 Jul 2008, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Oha, is this a Git User's Survey or a Git Potential Contributor's Survey?
I thought this is some kind of demographic question about the "programming
background" of the user.
And of course "I am not programmer" response...
This doesn't make sense, does it?
I know that there are non-programmer's who use git for there
configuration files and other non-programming track files, but
this looks somehow wrong in this survey.
Regards.
--
Stephan Beyer [off-list ref], PGP 0x6EDDD207FCC5040F
Dnia ?roda 23. lipca 2008 16:54, Robin Rosenberg napisa?:
quoted
onsdagen den 23 juli 2008 15.18.40 skrev Johannes Schindelin:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
On Wed, 23 Jul 2008, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Oha, is this a Git User's Survey or a Git Potential Contributor's Survey?
I thought this is some kind of demographic question about the "programming
background" of the user.
quoted
And of course "I am not programmer" response...
This doesn't make sense, does it?
I know that there are non-programmer's who use git for there
configuration files and other non-programming track files, but
this looks somehow wrong in this survey.
there are non-programmers who use git to track projects that they want to
be able to run the latest versions of. they don't program, just git pull;
make;make install
David Lang
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:00
On Wed, 23 Jul 2008, Alex Riesen wrote:
Johannes Schindelin, Wed, Jul 23, 2008 11:53:27 +0200:
quoted
quoted
19. How do you publish/propagate your changes?
(zero or more: multiple choice)
- push, pull request, format-patch + email, bundle, other
git svn
a converter using fast-import/fast-export/plumbing
So it would be now:
19. How do you publish/propagate your changes?
(zero or more: multiple choice)
- push, git-svn, foreign SCM (not via git-svn), pull request,
format-patch + email, bundle, other(*)
+ (*)If the way you publish your changes is not on above list,
please explain how do you publish your changes.
--
Jakub Narebski
Poland
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:00
On Wed, 23 July 2008, Stephan Beyer wrote:
Dmitry Potapov wrote:
quoted
On Wed, Jul 23, 2008 at 11:53:27AM +0200, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
11. Why did you choose Git? (if you use Git)
What do you like about using Git?
(free form, not to be tabulated)
Again, to avoid hassles with free-form:
Mandatory: work, mandatory: open source project I am participating
in, speed, scalability, It's What Linus Uses, Other.
If we move away from free-form, it should be much more choices here.
- Ability to work offline
- Cryptographic authentication of history.
- Distributed development (pull/push from/to more than one remote repo)
- Easy to extend functionality through scripting
- Efficient storage model
- Elegant design
- Fast
- Good community support
- Rewriting patches before publishing (git rebase, commit --amend)
- Scalability (Efficient handling of large projects)
- Strong support for non-linear development
- Support of wide range of protocols for synchronization.
...
Heh, I can imagine git users reading that survey and thinking
"What? Git allows me to rewrite patches before publishing?
And it provides cryptographic integrity? Sounds good. *click*"
Nevertheless, the list is fine ;)
Perhaps also: "Good reputation".
Perhaps also: "Because it is popular (hype)", and I hope that
"Ability to track code movement" would have any takers. Although
it is hard to distinguish between 'reasons to choose' and 'favourite
features' list; let's make it more 'reasons to choose' (like "feature
rich").
"Good documentation", perhaps, too?
--
Jakub Narebski
Poland
From: Stephan Beyer <hidden> Date: 2016-06-15 22:45:00
Hi,
david@lang.hm wrote:
quoted
quoted
And of course "I am not programmer" response...
This doesn't make sense, does it?
I know that there are non-programmer's who use git for there
configuration files and other non-programming track files, but
this looks somehow wrong in this survey.
there are non-programmers who use git to track projects that they want to
be able to run the latest versions of. they don't program, just git pull;
make;make install
Ahh, you're totally right. :)
I wonder if those users take part in a Git User's Survey. We'll see. :)
Stephan
--
Stephan Beyer [off-list ref], PGP 0x6EDDD207FCC5040F
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:00
On Tue, 24 July 2008, Stephan Beyer wrote:
Jakub Narebski wrote:
quoted
Dnia środa 23. lipca 2008 16:54, Robin Rosenberg napisał
quoted
onsdagen den 23 juli 2008 15.18.40 skrev Johannes Schindelin:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
On Wed, 23 Jul 2008, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Oha, is this a Git User's Survey or a Git Potential Contributor's Survey?
I thought this is some kind of demographic question about the "programming
background" of the user.
Well, truth to be told it is both. We try here to kill two birds with
one stone: both to have 'programming background' of Git users, and get
to know which parts of code can have many contributors, and which
could have troubles attracting contributors because of the language
they are written in (which is visible in the choice of programming
languages in 2007 survey).
If we want to provide larger number of programming languages to
chose from (with "other" as fallback), we could take for example
top 10 from the TIOBE index, or similar sites:
http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html (for July 2008)
http://lui.arbingersys.com/index.html (Language Usage Indicators, Jul 10, 2008)
This would bring 'Visual Basic', and perhaps 'Assembly' and 'Lisp'
to the list of choices.
quoted
And of course "I am not programmer" response...
This doesn't make sense, does it?
I know that there are non-programmer's who use git for there
configuration files and other non-programming track files, but
this looks somehow wrong in this survey.
This doesn't make sense, does it?
I know that there are non-programmer's who use git for there
configuration files and other non-programming track files, but
this looks somehow wrong in this survey.
there are non-programmers who use git to track projects that they want to
be able to run the latest versions of. they don't program, just git pull;
make;make install
Ahh, you're totally right. :)
I wonder if those users take part in a Git User's Survey. We'll see. :)
it depends on how it gets sent out.
if it's just sent to the git lists you won't have many of those users, if
it's sent to lists of projects that use git (and/or publicised in the
newsletters of those projects) we'll get a lot more of them.
due to the concern abot spamming too many lists, I'd suggest getting in
contact with the project leaders and see what they would like or not like.
I suspect that many of them will be happy to have the survey go out to
their users so that git can improve based on the feedback and their users
can think less about git and more about their project ;-)
if most of the project leaders are willing or eager to get the info out
it seems reasonable to go ahead and send a single message out to the other
lists, but if a lot of them are opposed, definantly don't send it anywhere
you didn't get a response.
David Lang
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:00
Dnia środa 23. lipca 2008 18:00, Johannes Schindelin napisał:
On Wed, 23 Jul 2008, Robin Rosenberg wrote:
quoted
onsdagen den 23 juli 2008 15.18.40 skrev Johannes Schindelin:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
On Wed, 23 Jul 2008, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
Some people prefer to stay anonymous, so I think email is out.
quoted
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Yes, I think this should be a long list.
I'd rather not have a "laundry list" of languages. I have put C++
because QGit uses it, Java because of egit/jgit, PHP for web
interfaces, Ruby because of GitHub and because of Ruby comminity
choosing Git. I should perhaps add Emacs Lisp, HTML+CSS and
JavaScript here. What other languages should be considered?
C# at least, since we had one (pretty unsuccessful) attempt at
reimplementing Git in it.
What is the reason for the question? Do we want to know what languages
people would like to contribute to Git in or do we want to know what "kind"
of programmers are attracted by Git? Making it a long list should make
it easier to tabulate the responses.
"could contribute" is more appropriate IMHO. Although you might be right
to ask "would like to contribute"... ;-)
I think it is both. We would like to know what kind of programmers
(and non-programmers) are attracted to Git, and also what languages
could people contribute to Git.
--
Jakub Narebski
Poland
From: Jon Loeliger <hidden> Date: 2016-06-15 22:45:00
Jakub Narebski wrote:
About you
01. What country are you in?
02. What is your preferred non-programming language?
(or) What is the language you want computer communicate with you?
How about: What is your preferred natural language?
03. How old are you (in years)?
(free form, integer)
04. Which programming languages you are proficient with?
Perhaps:
With which programming languages are you proficient?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
Getting started with GIT
05. How did you hear about Git?
(single choice?, in 2007 it was free-form)
- Linux kernel news (LKML, LWN, KernelTrap, KernelTraffic,...),
news site or magazine, blog entry, some project uses it,
presentation or seminar (real life, not on-line), SCM research,
IRC, mailing list, other Internet, other off-line, other(*)
+ the problem is with having not very long list (not too many
choices), but spanning all possibilities.
So go more general? Don't specify actual news (web)sites.
Don't forge that there is a whole raft of Ruby-n-rails folks who
are embracing Git these days too. They have their own whole 'nuther
set of mailing lists, websites, (news) lists, etc.
+ is this question interesting/important to have in survey?
Look to the history to answer this question. Did we really
learn anything from the earlier surveys by this question?
Maybe it would make more sense to get a feel for which general
camp led them to Git? That is, did they come from the Kernel
side of the world, or Ruby-on-Rails, or self-exploration, etc.
06. Did you find GIT easy to learn?
- very easy/easy/reasonably/hard/very hard
But that has to be contrasted with their _current_ notion
in order to know if they make progress or not. If the
difficulty persists, we're in trouble. If it is just a
steep learning curve, we might be able to address that.
So maybe some variant questions like:
How do you find it now (after some use)?
same [very easy..very hard] scale
How long have you been using Git?
Rate your own Git proficiency:
[noob, casual, I survive, everyday use,
I answer questions from others,
I use plumbing in scripts daily,
Power User, Godly, I am Junio]
07. What helped you most in learning to use it?
(free form question)
08. What did you find hardest in learning Git?
What did you find harderst in using Git?
(free form question)
09. When did you start using git? From which version?
- pre 1.0, 1.0, 1.1, 1.2, 1.3, 1.4, 1.5
It's likely that most people don't know the specific answer
to that question and will just guess, if anything. It is
also semi-subject to time-slide as old installs are made on
different distributions [*cough*] Debian. I think the question
"How long have you been using Git?" Might be more easily
answered and show better data. (Adoption curve.)
+ might be important when checking "what did you find hardest" etc.
+ perhaps we should ask in addition to this question, or in place
of this question (replacing it) what git version one uses; it
should be multiple choice, and allow 'master', 'next', 'pu',
'dirty (with own modifications)' versions in addition.
Other SCMs (shortened compared with 2007 survey)
10. What other SCM did or do you use?
(zero or more: multiple choice)
- CVS, Subversion, GNU Arch or arch clone (ArX, tla, ...),
Bazaar-NG, Darcs, Mercurial, Monotone, SVK, AccuRev, Perforce,
BitKeeper, ClearCase, MS Visual Source Safe, MS Visual Studio
Team System, custom, other(*)
What? No SCCS?
10b.If you selected other above, what SCM it was?
s/it was/was it/
(free form)
11. Why did you choose Git? (if you use Git)
That's a bit vague... First, maybe they didn't choose Git.
Maybe they are on a project where it was mandated.
So, Why did they choose Git for _what_?
Are we trying to ask "Why did you decide to use Git?" ?
What do you like about using Git?
(free form, not to be tabulated)
Presuming they do... :-) So, maybe add:
I enjoy using Git: [-5 .. 0 .. +5]
Git satisfies my use cases: [-5 .. 0 .. +5]
I prefer Git over CVS/SVN: [-5 .. 0 .. +5]
Or so...
12. Why did you choose other SCMs? (if you use other SCMs)
What do you like about using other SCMs?
Note: please write name of SCMs you are talking about.
(free form, not to be tabulated).
How you use Git
13. Do you use Git for work, unpaid projects, or both?
(single choice)
- work/unpaid projects/both
But there are other uses too. I use it for personal crap
like my Brewing Log. Sure, it is an "unpaid project", but
that's not very useful information. Maybe it would make
sense to expand this question into, say, 10 choices that
we feel are likely uses cases and see what the actual
demographics are. That is, the two-part-with-waffle isn't
that informative.
Maybe:
I use Git for: [check all that apply]
Work projects
Personal data
Unpaid Open Source Development
Sharing Data with my Niece
Maintaining my Website
Backending my Blog
etc.
My point here is that we can learn what Git is being
used for, and ....
Although for some reason I can't yet, I would
really like to use Git for:
My Wordpress backend
Maintaining my {pr0n,mp3} Collection
Work projects
Sharing data with my boss
etc.
That would give us a sense of direction possibly.
It might provide a notion as to what people are wanting
to do, but for some reason find it hard to pull off.
That is, help us identify use-cases that are being limited
but would otherwise be adoptive.
14. How do you obtain Git?
- binary package/source package or source script(*)/
source tarball/pull from main repository
(*) this includes source based distributions like Gentoo
+ added new option: source package or source script
+ should this be multiple choice?
15. What operating system do you use Git on?
(one or more: multiple choice, as one can use more than one OS)
- Linux, *BSD (FreeBSD, OpenBSD, etc.), MS Windows/Cygwin,
MS Windows/msysGit, MacOS X, other UNIX, other
+ "What hardware platforms do you use GIT on?" question was
removed; should it stay?
15b.If you selected "other UNIX", or "other", what operating system
or systems it was/were?
(free form)
16. Which porcelains / interfaces / implementations do you use?
(zero or more: multiple choice)
- core-git, Cogito (deprecated), StGIT, Guilt, pg (deprecated),
Pyrite, Easy Git, IsiSetup, jgit, my own scripts, other
16b.If you selected "other porcelain", what is its name?
(free form)
17. Which git GUI (commit tool or history viewer, or both) do you use
(zero or more: multiple choice)
- CLI, gitk, git-gui, qgit, gitview, giggle, tig, instaweb,
(h)gct, qct, KGit, git-cola / ugit, GitNub, Pyrite, git.el, other
17b.If you selected "other GUI", what is its name?
(free form)
18. Which (main) git web interface do you use for your projects?
(zero or more: multiple choice)
- gitweb, cgit, wit (Ruby), git-php, viewgit (PHP), other
+ should there be a question about web server (Apache, IIS, ...)
used to host git web interface?
Probably not. Most people might not even know.
18b.If you selected "other web interface", what it was?
(free form)
19. How do you publish/propagate your changes?
(zero or more: multiple choice)
- push, pull request, format-patch + email, bundle, other
19b.If the way you publish your changes is not mentioned above, how
do you publish your changes?
(free form)
20. Does git.git repository include code produced by you?
- yes/no
What you think of Git
21. Overall, how happy are you with Git?
- unhappy/not so happy/happy/very happy/completely ecstatic
22. How does Git compare to other SCM tools you have used?
- worse/equal (or comparable)/better
23. What would you most like to see improved about Git?
(features, bugs, plug-ins, documentation, ...)
24. If you want to see Git more widely used, what do you
think we could do to make this happen?
+ Is this question necessary/useful? Do we need wider adoption?
Hmmm. See some ramblings of mine above too... :-)
Changes in Git (since year ago, or since you started using it)
25. Did you participate in previous Git User's Surveys?
(zero or more, multiple choice)
- 2006, 2007
26. How do you compare current version with version from year ago?
- current version is: better/worse/no changes
More fine detail needed there? To help identify what people
think have improved and what has not yet improved?
Since you started using Git, rate how the following
functional areas have/have-not improved:
The User Interface [-5 .. 0 .. +5]
The command line interface [-5 .. 0 .. +5]
The intuitive behavior [-5 .. 0 .. +5]
The overall experience
The behavior of 'fetch'
The behavior of "git log'
The config file
etc.
A -5 means it still sucks or got worse, 0 is neutral
or no opinion, and +5 means it rocks or got better.
This would give us direct feedback indicating if we,
as a whole, are headed in the right direction with our
development efforts. It will also directly tell us
which features people find still suck.
We should attempt to get direct feedback on many Git features.
27. Which of the following features do you use?
(zero or more: multiple choice)
- git-gui or other commit tool, gitk or other history viewer, patch
management interface (e.g. StGIT), bundle, eol conversion,
gitattributes, submodules, separate worktree, reflog, stash,
shallow clone, detaching HEAD, mergetool, interactive rebase,
add --interactive or other partial commit helper, commit
templates, bisect, other (not mentioned here)
+ should probably be sorted in some resemblance of order
+ are there any new features which should be listed here?
28. If you use some important Git features not mentioned above,
what are it?
(free form)
Documentation
29. Do you use the Git wiki?
- yes/no
30. Do you find Git wiki useful?
- yes/no/somewhat
31. Do you contribute to Git wiki?
- yes/no/only corrections or spam removal
If "no", why not? [Wikis suck, I don't know the answers, no time...]
32. Do you find Git's on-line help (homepage, documentation) useful?
- yes/no/somewhat
Confusing.
33. Do you find help distributed with Git useful
(manpages, manual, tutorial, HOWTO, release notes)?
- yes/no/somewhat
34. What could be improved on the Git homepage?
(free form)
35. What could be improved in Git documentation?
(free form)
Getting help, staying in touch
36. Have you tried to get Git help from other people?
- yes/no
37. What channel did you use to request help?
(zero or more: multiple choice)
- git mailing list, git users group, IRC, blog post,
other
+ this is one question which doesn't need, I think, explanation
of "other" choice
38. If yes, did you get these problems resolved quickly
and to your liking?
- yes/no
39. Would commerical (paid) support from a support vendor
be of interest to you/your organization?
- yes/no/not applicable
s/commerical/commercial/
40. Do you read the mailing list?
- yes/no
41. If yes, do you find it useful?
- yes/no (optional)
42. Do you find traffic levels on Git mailing list OK.
- yes/no? (optional)
I find the mailing list traffic level to be:
[too low, OK, just right, tolerable, intolerable,
a bit high, absurdly high]
43. Do you use the IRC channel (#git on irc.freenode.net)?
- yes/no
44. If yes, do you find IRC channel useful?
- yes/no (optional)
45. Did you have problems getting GIT help on mailing list or
on IRC channel? What were it? What could be improved?
(free form)
Open forum
46. What other comments or suggestions do you have that are not
covered by the questions above?
(free form)
On Wed, Jul 23, 2008 at 03:25:03AM +0200, Jakub Narebski wrote:
Is there some channel that I have forgot about?
If the start of this survey can be timed to release 1.6.0 then the
announce about Git 1.6.0 release may also contain reference to that
survey, and because release announcements are usually widely distributed
by online magazines such as LinuxToday and LWN, anyone who is interested
in Git will learn about this survey too.
Dmitry
On Wed, Jul 23, 2008 at 11:49:41PM +0200, Jakub Narebski wrote:
On Wed, 23 Jul 2008, Dmitry Potapov wrote:
quoted
On Wed, Jul 23, 2008 at 03:25:03AM +0200, Jakub Narebski wrote:
quoted
02. What is your preferred non-programming language?
(or) What is the language you want computer communicate with you?
IMHO, the later wording of the question is much better.
First just satisfies demographic curiosity. Second is more question
about internationalization (i18n).
I think demographic is largely covered by the first question about
country. As to i18n, I don't think it is fully covered just by the
question about one's language preference to communicate with computer
(which is probably is more correctly to call localization). Possible
questions related to i18n are:
- Do you use file names with non-ASCII characters?
- Do you use text files with non-ASCII characters?
- Do you (or members of your team) use computers with different
character sets and have to deal with non-ASCII characters?
But I guess we do not want to have so many questions. So, maybe
something simple instead:
- Are you satisfied with support for non-ASCII characters in Git?
Should "What version do you use now?" be multiple choice (using git
on more than one machine / operating system)?
I think we already have another question about what OS one uses.
So I believe it should be only version number here.
What should be possible
choices for "How long do you use git?"? Perhaps.
10. How long do you use git?
(single choice)
- never/few days/few weeks/month/few months/year/few years/
from beginning/I wrote it(*)
+ (*) just kidding ;-)
I would rather use numbers like that:
never
less than month
1-3 months
3-6 months
6-12 months
1-2 year
more than 2 years
from the beginning
Dmitry
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:00
On Thu, 24 July 2008, Jon Loeliger wrote:
Jakub Narebski wrote:
quoted
About you
01. What country are you in?
02. What is your preferred non-programming language?
(or) What is the language you want computer communicate with you?
How about: What is your preferred natural language?
Perhaps it is a better formulation. I am not native English speaker.
(But so would be some people who would answer this survey).
The problem with this question is that people does not understand it,
and either do not answer or answer for example with computer language
(C, Perl, or something like that). For 2007 survey, when the question
was formulated as "02. What is your preferred non-programming language?"
there were 37 invalid responses (computer language), and 4 "not
understand" responses out of 662 people who answered this question.
On of the goals (besides curiosity about demographics) of this question
is to get to know if Git core should provide infrastructure for
translating messages, in addition to what already exists for git-gui
and gitk. But as currently there are no other questions about l10n
and i18n perhaps it would be better to simply remove this question.
quoted
03. How old are you (in years)?
(free form, integer)
04. Which programming languages you are proficient with?
Perhaps:
With which programming languages are you proficient?
Again: I am not native English speaker.
quoted
Getting started with GIT
05. How did you hear about Git?
(single choice?, in 2007 it was free-form)
- Linux kernel news (LKML, LWN, KernelTrap, KernelTraffic,...),
news site or magazine, blog entry, some project uses it,
presentation or seminar (real life, not on-line),
SCM research, IRC, mailing list, other Internet,
other off-line, other(*)
+ the problem is with having not very long list (not too many
choices), but spanning all possibilities.
So go more general? Don't specify actual news (web)sites.
I didn't mean here enumerating actual news (web)sites, but to provide
examples.
Don't forge that there is a whole raft of Ruby-n-rails folks who
are embracing Git these days too. They have their own whole 'nuther
set of mailing lists, websites, (news) lists, etc.
quoted
+ is this question interesting/important to have in survey?
Look to the history to answer this question. Did we really
learn anything from the earlier surveys by this question?
Maybe it would make more sense to get a feel for which general
camp led them to Git? That is, did they come from the Kernel
side of the world, or Ruby-on-Rails, or self-exploration, etc.
That is what I think we want to find through this question.
Unfortunately I have found about Git by reading KernelTraffic
and later KernelTrap during the whole "BitKeeper fiasco"; I have
next to no idea about how other people have heard about Git.
Help!?
There is other side to this question, _if_ we were some company, or/and
_if_ we were concerned about making Git more popular, namely to
identify the paces where "advertising" would make most impact.
quoted
06. Did you find GIT easy to learn?
- very easy/easy/reasonably/hard/very hard
But that has to be contrasted with their _current_ notion
in order to know if they make progress or not. If the
difficulty persists, we're in trouble. If it is just a
steep learning curve, we might be able to address that.
So maybe some variant questions like:
How do you find it now (after some use)?
same [very easy..very hard] scale
How long have you been using Git?
The question is here to either dispel the myth that Git is hard to
learn, or find that we have steep learning curve and that we should
perhaps do something about it.
Rate your own Git proficiency:
[noob, casual, I survive, everyday use,
I answer questions from others,
I use plumbing in scripts daily,
Power User, Godly, I am Junio]
Good idea about question about Git proficiency.
quoted
07. What helped you most in learning to use it?
(free form question)
08. What did you find hardest in learning Git?
What did you find harderst in using Git?
(free form question)
09. When did you start using git? From which version?
- pre 1.0, 1.0, 1.1, 1.2, 1.3, 1.4, 1.5
It's likely that most people don't know the specific answer
to that question and will just guess, if anything. It is
also semi-subject to time-slide as old installs are made on
different distributions [*cough*] Debian. I think the question
"How long have you been using Git?" Might be more easily
answered and show better data. (Adoption curve.)
True. I think "How long have you been using Git?" with log-like
multiple choice scale: few days/few weeks/month/few months/year/few
years would be better idea.
On the other hand knowing which version someone started his/her
"Git adventure" would help to find probable causes where some of ideas
about git were already corrected in later versions...
quoted
+ might be important when checking "what did you find
hardest" etc.
+ perhaps we should ask in addition to this question, or in
place of this question (replacing it) what git version one
uses; it should be multiple choice, and allow 'master',
'next', 'pu', 'dirty (with own modifications)' versions
in addition.
It would be next (additional) question, probably multiple choice, and
easy to check out with "git version" or "git --version" command.
quoted
Other SCMs (shortened compared with 2007 survey)
10. What other SCM did or do you use?
(zero or more: multiple choice)
- CVS, Subversion, GNU Arch or arch clone (ArX, tla, ...),
Bazaar-NG, Darcs, Mercurial, Monotone, SVK, AccuRev,
Perforce, BitKeeper, ClearCase, MS Visual Source Safe,
MS Visual Studio Team System, custom, other(*)
What? No SCCS?
Hmmm... SCCS got 18 out of 654 responses, only one less than SVK.
I'd add it to the list of choices for this question, then.
quoted
10b.If you selected other above, what SCM it was?
s/it was/was it/
quoted
(free form)
11. Why did you choose Git? (if you use Git)
That's a bit vague... First, maybe they didn't choose Git.
Maybe they are on a project where it was mandated.
So, Why did they choose Git for _what_?
Are we trying to ask "Why did you decide to use Git?" ?
Yes, that was I wanted to ask. "Why do you use Git? (if you do use it)".
quoted
What do you like about using Git?
(free form, not to be tabulated)
Presuming they do... :-) So, maybe add:
I enjoy using Git: [-5 .. 0 .. +5]
Git satisfies my use cases: [-5 .. 0 .. +5]
I prefer Git over CVS/SVN: [-5 .. 0 .. +5]
Or so...
I'm not sure if it wouldn't be more interesting to have free-form here.
I think we would get quite a number of unique and non-obvious answers.
Besides the above form depends on survey site to be able to create such
matrix of responses...
quoted
How you use Git
13. Do you use Git for work, unpaid projects, or both?
(single choice)
- work/unpaid projects/both
But there are other uses too. I use it for personal crap
like my Brewing Log. Sure, it is an "unpaid project", but
that's not very useful information. Maybe it would make
sense to expand this question into, say, 10 choices that
we feel are likely uses cases and see what the actual
demographics are. That is, the two-part-with-waffle isn't
that informative.
Maybe:
I use Git for: [check all that apply]
Work projects
Personal data
Unpaid Open Source Development
Sharing Data with my Niece
Maintaining my Website
Backending my Blog
etc.
Very good idea. This way we can share this question with question about
kind of data one uses Git for.
By the way, perhaps we should split "Work projects" into "Work projects"
and "Work projects (private git)" to distinguish between cases where Git
is used at work, and where you use Git privately (for example via
git-svn, or git-p4) to interact with other SCM that is used at work.
My point here is that we can learn what Git is being
used for, and ....
Although for some reason I can't yet, I would
really like to use Git for:
My Wordpress backend
Maintaining my {pr0n,mp3} Collection
Work projects
Sharing data with my boss
etc.
That would give us a sense of direction possibly.
It might provide a notion as to what people are wanting
to do, but for some reason find it hard to pull off.
That is, help us identify use-cases that are being limited
but would otherwise be adoptive.
Hmmmm...
quoted
18. Which (main) git web interface do you use for your projects?
(zero or more: multiple choice)
- gitweb, cgit, wit (Ruby), git-php, viewgit (PHP), other
+ should there be a question about web server (Apache,
IIS, webrick, LigHTTPd, ...) used to host git web interface?
Probably not. Most people might not even know.
I can agree with that.
On the other hand the purpose of this question was to get a list
of most popular servers to put example configuration for hosting git
repositories via HTTP(S) protocol, and for setting up gitweb.
quoted
What you think of Git
24. If you want to see Git more widely used, what do you
think we could do to make this happen?
+ Is this question necessary/useful? Do we _need_
wider adoption?
Hmmm. See some ramblings of mine above too... :-)
What ramblings were they?
quoted
Changes in Git (since year ago, or since you started using it)
26. How do you compare current version with version from
year ago?
- current version is: better/worse/no changes
The list of possible answers should (just in case, because you can
simply not answer this question, although some would not know this)
also "I don't know, I didn't use Git for a year".
More fine detail needed there? To help identify what people
think have improved and what has not yet improved?
Since you started using Git, rate how the following
functional areas have/have-not improved:
The User Interface [-5 .. 0 .. +5]
The command line interface [-5 .. 0 .. +5]
The intuitive behavior [-5 .. 0 .. +5]
The overall experience
The behavior of 'fetch'
The behavior of "git log'
The config file
etc.
This of course depends on web survey site allowing such feature
in survey.
A -5 means it still sucks or got worse, 0 is neutral
or no opinion, and +5 means it rocks or got better.
This would give us direct feedback indicating if we,
as a whole, are headed in the right direction with our
development efforts. It will also directly tell us
which features people find still suck.
We should attempt to get direct feedback on many Git features.
The trouble of course would be with coming up with the "laundry list" of
features people did or can have a problem with.
quoted
Documentation
31. Do you contribute to Git wiki?
- yes/no/only corrections or spam removal
If "no", why not?
Good idea.
[Wikis suck, I don't know the answers, no time...]
[We have a wiki???] ;-)
quoted
32. Do you find Git's on-line help (homepage, documentation)
useful?
- yes/no/somewhat
Confusing.
I think it would fall in "somewhat" category I think.
quoted
Getting help, staying in touch
42. Do you find traffic levels on Git mailing list OK.
- yes/no? (optional)
I find the mailing list traffic level to be:
[too low, OK, just right, tolerable, intolerable,
a bit high, absurdly high]
Good idea of expanding the list of answers, otherwise it is hard to
answer this question. Although perceived signal to noise ratio might
be more important than bare traffic.
quoted
Open forum
46. What other comments or suggestions do you have that are not
covered by the questions above?
(free form)
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:00
On Thu, 24 Jul 2008, Dmitry Potapov wrote:
On Wed, Jul 23, 2008 at 03:25:03AM +0200, Jakub Narebski wrote:
quoted
Is there some channel that I have forgot about?
If the start of this survey can be timed to release 1.6.0 then the
announce about Git 1.6.0 release may also contain reference to that
survey, and because release announcements are usually widely distributed
by online magazines such as LinuxToday and LWN, anyone who is interested
in Git will learn about this survey too.
You can send a story to LWN with two weeks notice; IIRC Git user's
Survey 2007 was announced in LWN around the middle of its duration.
I don't know about LinuxToday / Linux.com.
IIRC tentative date for 1.6.0 release is around August 10. It is
quite a bit of time from now. On the other hand that mean lot
of time to prepare questions, and to put survey on the web.
P.S. <tongue in cheek> are there enough of us to Digg / Mixx / Reddit
Git User's Survey 2008 announcement? ;-P </tongue in cheek>
--
Jakub Narebski
Poland
01. What country are you in?
02. What is your preferred non-programming language?
(or) What is the language you want computer communicate with you?
How about: What is your preferred natural language?
Perhaps it is a better formulation. I am not native English speaker.
(But so would be some people who would answer this survey).
According to Wikipedia
(http://en.wikipedia.org/wiki/Natural_language), "natural language"
could include, for example, bee dances. "...a language that is
spoken, written, or signed by animals for general-purpose
communication..." And, it might also exclude constructed languages
like Esperanto and Klingon. How about:
02. What language do you prefer to use when communicating with people?
In case there are, for example, any Klingons, sentient machines, etc.,
in the audience, the sentence does not assume the answerer is human...
:-) It's a tricky question to write.
I'm a total newbie here, by the way.
01. USA
02. Probably best I stick to English, but I'm willing to negotiate.
06. Not sure yet.
09. Last month. I think.
--
:-) Lachele
Lachele Foley
CCRC/UGA
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:01
On Thu, 24 July 2008, Dmitry Potapov wrote:
On Wed, Jul 23, 2008 at 11:49:41PM +0200, Jakub Narebski wrote:
quoted
On Wed, 23 Jul 2008, Dmitry Potapov wrote:
quoted
On Wed, Jul 23, 2008 at 03:25:03AM +0200, Jakub Narebski wrote:
quoted
02. What is your preferred non-programming language?
(or) What is the language you want computer communicate with you?
IMHO, the later wording of the question is much better.
First just satisfies demographic curiosity. Second is more question
about internationalization (i18n).
I think demographic is largely covered by the first question about
country. As to i18n, I don't think it is fully covered just by the
question about one's language preference to communicate with computer
(which is probably is more correctly to call localization). Possible
questions related to i18n are:
- Do you use file names with non-ASCII characters?
- Do you use text files with non-ASCII characters?
- Do you (or members of your team) use computers with different
character sets and have to deal with non-ASCII characters?
But I guess we do not want to have so many questions. So, maybe
something simple instead:
- Are you satisfied with support for non-ASCII characters in Git?
But only if it is free-form question:
xx. Are you satisfied with support for non-ASCII characters in Git?
Yes or No? If no, please explain what you had problems with.
(free form, or rather Yes/No + explanation for No)
If we decide to add more questions about translating Git, I think
we should also add the following:
xx. Which parts of Git would you like/do you need translated?
(zero or more: multiple choice)
- git-gui, gitk, manpages, user's manual, commands messages
quoted
Should "What version do you use now?" be multiple choice (using git
on more than one machine / operating system)?
I think we already have another question about what OS one uses.
So I believe it should be only version number here.
One can use Git on many different machines (for example at work, and
at home), or on multi-boot machine (with more than one operating
system). Each of those machines, and/or each of those operating
systems can use different version of Git. So that is why I think
this should be multiple choice, even if I guess that most people
would select only one answer.
quoted
What should be possible
choices for "How long do you use git?"? Perhaps.
10. How long do you use git?
(single choice)
- never/few days/few weeks/month/few months/year/few years/
from beginning/I wrote it(*)
+ (*) just kidding ;-)
I would rather use numbers like that:
never
less than month
1-3 months
3-6 months
6-12 months
1-2 year
more than 2 years
from the beginning
I think it is even better; I'm not sure if we shouldn't split sub-month
region, for example to provide for people who has heard of git for
first time, but played with it a little bit.
--
Jakub Narebski
Poland
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:01
On Thu, 24 Jul 2008, Lachele Foley wrote:
01. USA
02. Probably best I stick to English, but I'm willing to negotiate.
06. Not sure yet.
09. Last month. I think.
Errr... this email is _not_ a survey. It is an RFC, Request For
Comments, meant to come up with a good list of questions, and good list
of possible answers for single choice/multiple choice questions.
--
Jakub Narebski
Poland
From: Stephan Beyer <hidden> Date: 2016-06-15 22:45:01
quoted
How you use Git
I'd also like to see a question about what kind of content is tracked
using git.
[ ] Source code
[ ] Multimedia files
[ ] LaTeX documents
[ ] Office documents
[ ] Configuration files
[ ] Web content
[ ] the whole root filesystem ;-)
[ ] Other: _________________
Regards.
--
Stephan Beyer [off-list ref], PGP 0x6EDDD207FCC5040F
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:03
On Thu, 24 July 2008, Jakub Narębski wrote:
On Thu, 24 July 2008, Stephan Beyer wrote:
quoted
Jakub Narebski wrote:
quoted
Dnia środa 23. lipca 2008 16:54, Robin Rosenberg napisał
quoted
onsdagen den 23 juli 2008 15.18.40 skrev Johannes Schindelin:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
On Wed, 23 Jul 2008, Johannes Schindelin wrote:
quoted
On Wed, 23 Jul 2008, Jakub Narebski wrote:
quoted
04. Which programming languages you are proficient with?
(The choices include programming languages used by git)
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk
+ (should we include other languages, like C++, Java, PHP,
Ruby,...?)
[...]
If we want to provide larger number of programming languages to
chose from (with "other" as fallback), we could take for example
top 10 from the TIOBE index, or similar sites:
http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html (for July 2008)
http://lui.arbingersys.com/index.html (Language Usage Indicators, Jul 10, 2008)
This would bring 'Visual Basic', and perhaps 'Assembly' and 'Lisp'
to the list of choices.
Perhaps also consider GitHub's list of most popular languages
http://github.com/blog/99-popular-languages
(as mentioned in Petr 'Pasky' Baudis somewhere in git-scm.com thread)
to take into account git popularity among web developers.
This would add 'ERB' (or is it just subset of 'Ruby' as eRuby
implementation?), and 'Common Lisp' (if 'Common Lisp', then
probably also 'Scheme'/'Guile').
There is always free-form 'other'...
--
Jakub Narebski
Poland
>> Jakub Narebski wrote:
>>> Dnia środa 23. lipca 2008 16:54, Robin Rosenberg napisał
>>>> onsdagen den 23 juli 2008 15.18.40 skrev Johannes Schindelin:
>>>>> On Wed, 23 Jul 2008, Jakub Narebski wrote:
>>>>>> On Wed, 23 Jul 2008, Johannes Schindelin wrote:
>>>>>>> On Wed, 23 Jul 2008, Jakub Narebski wrote:
>>>>>>>
>>>>>>>> 04. Which programming languages you are proficient with?
>>>>>>>> (The choices include programming languages used by git)
>>>>>>>> (zero or more: multiple choice)
>>>>>>>> - C, shell, Perl, Python, Tcl/Tk
>>>>>>>> + (should we include other languages, like C++, Java, PHP,
>>>>>>>> Ruby,...?)
>> [...]
>
quoted
If we want to provide larger number of programming languages to
> chose from (with "other" as fallback), we could take for example
> top 10 from the TIOBE index, or similar sites:
> http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html (for July 2008)
> http://lui.arbingersys.com/index.html (Language Usage Indicators, Jul 10, 2008)
>
> This would bring 'Visual Basic', and perhaps 'Assembly' and 'Lisp'
> to the list of choices.
Perhaps also consider GitHub's list of most popular languages
http://github.com/blog/99-popular-languages
(as mentioned in Petr 'Pasky' Baudis somewhere in git-scm.com thread)
to take into account git popularity among web developers.
This would add 'ERB' (or is it just subset of 'Ruby' as eRuby
implementation?), and 'Common Lisp' (if 'Common Lisp', then
probably also 'Scheme'/'Guile').
I have an impression that this 'erb' is a file extension for html file
with embedding ruby, used in ruby on rails. If so it's not worth
adding. If you are going to add Scheme, please remove Guile or you
have to list other Scheme implementations too.
There is always free-form 'other'...
--
Jakub Narebski
Poland
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:11
This is second revision (version) of proposed questions
for Git User's Survey 2008.
First, it was decided that it would be web based survey; I would use
survs.com (new, in beta), unless free version expires or acquires
unbearable restrictions (like no more than 10 questions, no more than
100 replies some survey sites have for non-paid accounts), because it
has some nice features, and allows export of results to CSV format for
further analysis... but I have not checked if the site that was used
for earlier, 2006 and 2007 surveys (http://www.survey.net.nz) doesn't
have those features now (it didn't have when 2007 survey was run).
Note that new features like "matrix" questions and ability to have
'other' selection for single choice and multiple choice questions
affect a bit form of this survey.
Second, what questions should be put in the survey, and in the case of
single choice and multiple choice questions what possible answers
should be? I'd rather avoid free-form questions, even if they are
more interesting, as they are PITA to analyze and summarize,
especially to create some kind of histogram from free-form replies
data (some of 2007 free-form responses are not fully summarized even
now). Below there are proposals for questions for this year survey.
Please comment on them.
By the way, should the survey be divided in pages, or simply use
headers to divide survey into sections?
Third, where to send survey to / where to publish information about the
survey? Last year the announcement was send to git mailing list, to
LKML (Linux kernel mailing list), and mailing list for git projects
found on GitProjects page on GIT wiki. Now that the number of projects
using Git as version control system has grown, I don't think it would
be good idea to "spam" all those mailing list; and if we don't send
notice to all other projects I'm not sure if we should include LKML.
Last year survey announcement was put on Git Homepage (thanks Pasky),
and on front page of Git Wiki; info about survey was also put on two
git hosting sites: kernel.org and repo.or.cz. It would be nice if it
was possible to put announcement about Git User's Survey 2008 at front
pages of other Git hosting sites, like GitHub (one of most popular, I
think), Gitorious, Freedesktop.org. If you know some other popular Git
hosting sites, and even better if you know who to contact about putting
survey announcement, please write. Is there some channel that I have
forgot about? Should info/announcement about Git User's Survey 2008 be
sent also to one of on-line magazines like LinuxToday or LWN, or asked
to put on some blog? I'll add it as journal entry for #git on Ohloh,
and try to make it so it would appear in "News" section for Ohloh
project page for Git: http://www.ohloh.net/projects/git.
Survs.com has nice feature of "channels", which allow to count
responses sent via different means separately; I am using it to
publish URL for 'test' channel - answers from this channel won't be
counted AT ALL!!!
Fourth, how long should the survey last? When sending announcement we
should say where notice about Git User's Survey 2008 should be taken
down. Last year the survey was meant to take three weeks, but was up
longer. I'm thinking about having it last a month, or a month and a
half, starting from September 1.
Below there is second version of announcement email (I should probably
come up also with boilerplate announcement for web pages), and second
version of this year round of questions. Comments are prefixed by
'+', and would not necessary be included in the survey text.
Questions which were reworked are included in square brackets '[...]',
while old version of answers or comments are prefixed with '!'.
BTW should this survey be divided into pages or not (if it will be
on Survs.com, as it is now)?
----
Hi all,
We would like to ask you a few questions about your use of the Git
version control system. This survey is mainly to understand who is
using Git, how and why.
The results will be published to the Git wiki and discussed on the git
mailing list.
We'll close the survey in <duration> starting from today, <date>.
Please devote a few minutes of your time to fill this simple
questionnaire, it will help a lot the git community to understand your
needs, what you like of git, and of course what you don't like of it.
The survey can be found here:
http://www.survs.com/survey?id=M3PIVU72&channel=9XYYGHJ77G
(this is temporary channel URL; responses to this URL would
be, I guess, discarded).
----
About you
xx. What country are you in?
(free form; it would be nice to have pre-filled pull-down
menu, i.e. select form. Survs.com doesn't support it, yet)
xx. How old are you (in years)?
(free form, integer)
xx. Which programming languages you are proficient with?
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk, C++, C#, Java, PHP,
Ruby, Emacs Lisp, Common Lisp or Scheme, Visual Basic,
Delphi, Assembly, other (please specify), I am not programmer
! C, shell, Perl, Python, Tcl/Tk
+ First version included only programming languages used
by git, and some from contrib area
Getting started with GIT
xx. How did you hear about Git?
(single choice?, in 2007 it was free-form)
- Linux kernel news (LKML, LWN, KernelTrap, KernelTraffic,...),
news site or magazine, blog entry, some project uses it,
presentation or seminar (real life, not on-line), SCM research,
IRC, mailing list, told by friend, word of mouth (off-line),
other Internet, must be used at job, other off-line, other(*)
+ the problem is with having not very long list (not too many
choices), but spanning all possibilities.
+ is this question interesting/important to have in survey?
xx. Did you find GIT easy to learn?
- very easy/easy/reasonably/hard/very hard
xx. What helped you most in learning to use it?
(free form question)
xx. What did you find hardest in learning Git?
What did you find hardest in using Git?
(free form question)
xx. Which Git version(s) are you using?
(zero or more, multiple choice:
one can use different versions on different machines)
- pre 1.3, 1.3, 1.4, 1.5, 1.6, master, next
+ might be important when checking "what did you find hardest" etc.
+ perhaps we should ask in addition to this question, or in place
of this question (replacing it) what git version one uses; it
should be multiple choice, and allow 'master', 'next', 'pu',
'dirty (with own modifications)' versions in addition.
xx. How long do you use Git?
- never/less than month/1-3 months/3-6 months/6-12 months/
1-2 year/more than 2 years/from the beginning
! never/few days/few weeks/month/few months/year/few years/
from beginning/I wrote it(*)
+ (*) just kidding ;-)
xx. Does git.git repository include code produced by you?
- yes/no
Other SCMs (shortened compared with 2007 survey)
xx. What other SCM did or do you use?
! (zero or more: multiple choice)
(matrix with the following columns: never/used it/still use)
- SCCS, RCS, CVS, Subversion, Arch or clone (ArX, tla, ...),
Bazaar-NG, Darcs, Mercurial, Monotone, SVK, AccuRev, Perforce,
BitKeeper, ClearCase, MS Visual Source Safe, MS Visual Studio
Team System, PVCS, custom, other (please specify)
xx. Why did you choose/use Git? (if you use Git)
What do you like about using Git?
(free form, not to be tabulated)
xx. Why did you choose/use other SCMs? (if you use other SCMs)
What do you like about using other SCMs?
Note: please write name of SCMs you are talking about.
(free form, not to be tabulated).
xx. Do you miss features in git that you know from other SCMs?
If yes, what features are these (and from which SCM)?
(free form, not to be tabulated).
+ suggested by Stephan Beyer
How you use Git
[xx. Do you use Git for work, unpaid projects, or both?
(single choice)
- work/unpaid projects/both]
xx. I use Git for (check all that apply):
- work projects, unpaid projects, proprietary code development,
OSS development, private (unpublished) development, personal data,
documents, website or web app, sharing data, backup,
wiki/blog backend, frontend to other SCM (git-svn, git-p4),
other (if interesting)
+ Answers above are not orthogonal, neither exclusive.
More than one answer can apply even for single repository.
xx. How do you obtain Git?
- binary package/source package or source script(*)/
source tarball/pull from main repository
(*) this includes source based distributions like Gentoo
+ added new option: source package or source script
+ should this be multiple choice?
xx. What operating system do you use Git on?
(one or more: multiple choice, as one can use more than one OS)
- Linux, FreeBSD, OpenBSD, NetBSD, MacOS X (Darwin),
UnixWare, SCO SV, SunOS, Solaris, AIX, IRIX, HP-UX, Other Unix,
MS Window/Cygwin, MS Windows/msysGit (MINGW), MS Windows/unknown,
Other (please specify).
! Linux, *BSD (FreeBSD, OpenBSD, etc.), MS Windows/Cygwin,
MS Windows/msysGit, MacOS X, other UNIX, other
+ I have added here all the operating systems explicitly
specified in "guessing configuration" part of Makefile
+ You can use 'uname' to get the name of operating system on Unices.
xx. What hardware platforms do you use GIT on?
(one or more: multiple choice, as one can use more than one machine)
- 32bit, 64bit, handheld/portable, other (please specify)
+ It is much simplified compared to previous version, and it is
not a free-form question. Still not sure if even in such
simplified form this question is to stay, or should it be removed.
xx. What editor, IDE or RAD you use working with GIT?
(zero/one or more: multiple choice with 'other')
- Eclipse, NetBeans, IntelliJ IDEA, Visual Studio, KDevelop, Anjuta,
XCode, PIDA, Eric, Dreamweaver, Emacs, Vim, TextMate, Notepad++,
other (please specify)
+ What choices should be in the list of editors and IDE;
or should perhaps this question be free-form?
xx. Which porcelains / interfaces / implementations do you use?
(zero or more: multiple choice)
- core-git, Cogito (deprecated), StGIT, Guilt, pg (deprecated),
TopGit, Pyrite, Easy Git, IsiSetup, jgit, my own scripts,
other (please specify)
xx. Which git GUI (commit tool or history viewer, or both) do you use
(zero or more: multiple choice)
- CLI, gitk, git-gui, qgit, gitview, giggle, tig, instaweb,
(h)gct, qct, KGit, git-cola / ugit, GitNub, Pyrite, git.el,
other (please specify)
xx. Which (main) git web interface do you use for your projects?
(zero or more: multiple choice)
- gitweb, cgit, wit (Ruby), git-php, viewgit (PHP), Gitorious,
other (please specify)
xx. Which git hosting site do you use for your projects?
(zero or more: multiple choice)
- repo.or.cz, GitHub, Gitorious, kernel.org, freedesktop.org,
Savannah, Assembla, Unfuddle, Alioth, Fedora Hosted, other
+ of course "if other, which"
+ should some other web hosting sites be included as well?
xx. How do you publish/propagate your changes?
(zero or more: multiple choice)
- push, pull request, format-patch + email, bundle,
git-svn, foreign SCM (not via git-svn),
other (see also below)
xx. If the way you publish your changes is not mentioned above, how
do you publish your changes? Please explain.
(free form, either input field or textarea)
xx. How often do you use the following forms of git commands or extra
git tools?
(matrix form: never/rare/often)
. git add -i / -p
. git add -u
. git am
. git am -i
. git apply
. git archive
. git bisect
. git bisect run <cmd>
. git bisect replay <logfile>
. git annotate
. git gui blame
. git blame
. git blame -L <start>,<end>
. git blame -S <revs-file>
. git bundle
. git cherry
. git cherry-pick
. git cherry-pick -n
. git citool
. git clean
. git commit
. git commit -a
. git commit <file>...
. git commit -i <file>...
. git commit --amend
. git count-objects
. git cvsexportcommit
. git cvsserver
. git ... --dirstat
. git fetch <options>
. git filter-branch
. git format-patch
. git fsck
. git grep
. git imap-send
. git instaweb
. git log --grep/--author/...
. git log -S<string>
. git log --graph
. git merge
. git merge with strategy
. git merge --squash
. git mergetool
. git pull
. git pull <remote>
. git pull <URL> <ref>
. git push
. git relink
. git rebase
. git rebase -i
. git rebase --onto
. git remote add <name> <URL>
. git remote show <name>
. git remote prune <name>
. git remote update
. git request-pull
. git reset --soft
. git reset [--mixed]
. git reset --hard
. git revert
. git send-email
. git show-branch
. git shortlog
. git shortlog -s
. git stash
. git submodule
. git svn
. git tag
. git tag -a/-s
. git tag -v
. git whatchanged
. git gui
. gitk
. gitprompt
+ (*)rarely is to mean: a few times, or sometimes (from time to time)
+ the list does not include commands which you _have_ to use,
like "git add <file>", "git init"/"git clone" etc.
+ in what order should be those commands; currently they are in
alphabetical order?
xx. Which of the following features do you use?
(zero or more: multiple choice)
- git-gui or other commit tool, gitk or other history viewer, patch
management interface (e.g. StGIT), bundle, eol conversion (crlf),
gitattributes, submodules, separate worktree, reflog, stash,
shallow clone, detaching HEAD, mergetool, interactive rebase,
add --interactive or other partial commit helper, commit
templates, bisect, working with dirty tree, integration with
IDE/editor, other (not mentioned here)
+ should probably be sorted in some resemblance of order
+ are there any new features which should be listed here?
xx. Which features do you find unique and useful ones, compared
to other systems (other SCMs)?
(zero or more: multiple choice)
- [same set as in above question, or almost the same set]
xx. If you use some important Git features not mentioned above,
what are those?
(free form, textarea)
What you think of Git
xx. Overall, how happy are you with Git?
(single choice)
- unhappy/not so happy/happy/very happy/completely ecstatic
xx. How does Git compare to other SCM tools you have used?
(single choice)
- worse/equal (or comparable)/better
xx. What would you most like to see improved about Git?
(features, bugs, plug-ins, documentation, ...)
xx. What tools would you like to see Git support in?
(free form)
Changes in Git (since year ago, or since you started using it)
xx. Did you participate in previous Git User's Surveys?
(zero or more, multiple choice)
- 2006, 2007
xx. How do you compare current version with version from year ago?
- current version is: better/worse/no changes/cannot say
Documentation
xx. Do you use the Git wiki?
- yes/no
xx. Do you find Git wiki useful?
- yes/no/somewhat
xx. Do you contribute to Git wiki?
- yes/no/only corrections or spam removal
xx. Do you find Git's on-line help (homepage, documentation) useful?
- yes/no/somewhat
xx. Do you find help distributed with Git useful
(manpages, manual, tutorial, HOWTO, release notes)?
- yes/no/somewhat
xx. What could be improved on the Git homepage?
(free form)
xx. What could be improved in Git documentation?
(free form)
Translating Git
xx. What is your preferred non-programming language?
(or) What is the language you want computer communicate with you?
xx. What do you need/want to have translated?
(zero or more, multiple choice)
- commands messages, manpages, manual & tutorial etc.,
technical documentation, HOWTOs, git homepage, git wiki,
git-gui/gitk, subcommands and long option names
Getting help, staying in touch
xx. Have you tried to get Git help from other people?
- yes/no
xx. What channel did you use to request help?
(zero or more: multiple choice)
- git mailing list, git users group, IRC, blog post,
asking git guru/colleague, other
+ This is one question which doesn't need, I think, explanation
of "other" choice
xx. If yes, did you get these problems resolved quickly
and to your liking?
- yes/no
xx. Would commercial (paid) support from a support vendor
be of interest to you/your organization?
- yes/no/not applicable
xx. Do you think it is easy to find out how to do a specific task
with git?
- yes/no/not always
xx. Do you read the mailing list?
(multiple choice: zero or more; "none" is just in case)
- none/git@vger.kernel.org/Git For Human Beings/msysGit
xx. If yes, do you find it useful?
- yes/no/somewhat (optional)
[xx. Do you find traffic levels on Git mailing list OK.
- yes/no? (optional)]
xx. Do you find the mailing list traffic level to be:
- too low/OK/just right/tolerable/intolerable/
a bit high/absurdly high/I don't read it
xx. Do you use the IRC channel (#git on irc.freenode.net)?
- yes/no
xx. If yes, do you find IRC channel useful?
- yes/no/somewhat (optional)
xx. Did you have problems getting GIT help on mailing list or
on IRC channel? What were it? What could be improved?
(free form)
Open forum
xx. What other comments or suggestions do you have that are not
covered by the questions above?
(free form)
xx. Should such a survey be repeated next year?
- yes/no/no opinion
--
Jakub Narebski
Poland
17. Which git GUI (commit tool or history viewer, or both) do you use
(zero or more: multiple choice)
- CLI, gitk, git-gui, qgit, gitview, giggle, tig, instaweb,
(h)gct, qct, KGit, git-cola / ugit, GitNub, Pyrite, git.el, other
I am author of kgit and is a dead project i don't think anyone uses it
and should use it.
I have amended the git wiki for the same, can you please amend the
survey,
In other news i have replaced kgit with teamgit
http://www.devslashzero.com/teamgit
Which should be ready soon for prime time, but is not worth to be in
survey since its not officially released yet.
Thanks
BAIN
From: Alex Riesen <hidden> Date: 2016-06-15 22:45:11
2008/8/20 Jakub Narebski [off-list ref]:
About you
xx. What country are you in?
(free form; it would be nice to have pre-filled pull-down
menu, i.e. select form. Survs.com doesn't support it, yet)
xx. How old are you (in years)?
(free form, integer)
xx. Which programming languages you are proficient with?
"Which programming languages ARE you proficient with?"
or maybe simplier
"What programming languages do you use?"
xx. How often do you use the following forms of git commands or extra
git tools?
Some time back there was a script posted on this list which extracted
this statistics from users .bash_history. Maybe reference it here?
xx. Which features do you find unique and useful ones, compared
to other systems (other SCMs)?
The meanings of "unique" and "useful" are unrelated, maybe make this
two separate questions?
xx. If you use some important Git features not mentioned above,
what are those?
"What, in your opinion important, Git feature it is not mentioned above?"
xx. What would you most like to see improved about Git?
you can drop "most": if people think something should be improved,
we (most) likely want to know about it :)
xx. What tools would you like to see Git support in?
"What tools (IDE, RAD, editors) would you like to support Git?"
xx. Did you have problems getting GIT help on mailing list or
on IRC channel? What were it? What could be improved?
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:11
Dnia środa 20. sierpnia 2008 14:04, Petr Baudis napisał:
On Wed, Aug 20, 2008 at 01:34:39PM +0200, Alex Riesen wrote:
quoted
2008/8/20 Jakub Narebski [off-list ref]:
quoted
xx. What tools would you like to see Git support in?
"What tools (IDE, RAD, editors) would you like to support Git?"
Isn't this question more general, like covering also bugtrackers,
automated testing tools and whatnot?
Currently it is:
xx. What tools (or kind of tools) would you like to see Git support in?
(e.g. IDE, RAD, editors, continuous integration, software hosting,
bugtracker, merge tool,...)
(free form)
BTW I think that it should be "Git support in", not "to support Git".
But I am not a native English speaker.
--
Jakub Narebski
Poland
From: Alex Riesen <hidden> Date: 2016-06-15 22:45:11
2008/8/20 Jakub Narebski [off-list ref]:
Dnia środa 20. sierpnia 2008 14:04, Petr Baudis napisał:
quoted
On Wed, Aug 20, 2008 at 01:34:39PM +0200, Alex Riesen wrote:
quoted
2008/8/20 Jakub Narebski [off-list ref]:
quoted
xx. What tools would you like to see Git support in?
"What tools (IDE, RAD, editors) would you like to support Git?"
Isn't this question more general, like covering also bugtrackers,
automated testing tools and whatnot?
Currently it is:
xx. What tools (or kind of tools) would you like to see Git support in?
(e.g. IDE, RAD, editors, continuous integration, software hosting,
bugtracker, merge tool,...)
(free form)
BTW I think that it should be "Git support in", not "to support Git".
From: Stephan Beyer <hidden> Date: 2016-06-15 22:45:11
Hi,
Jakub Narebski wrote:
This is second revision (version) of proposed questions
for Git User's Survey 2008.
Great!
By the way, should the survey be divided in pages, or simply use
headers to divide survey into sections?
Divided pages have a psychological impact, they don't look much and you
can say "Almost there!" on each page.
But headers and one-page surveys have a big advantage for users that pay
for Internet access per time unit: they can go offline, answer the
questions, and go online again to submit the survey.
So I've scrolled across your test survey on survs.com and I think it
should be kept on one page. Looks nice and manageable.
Third, where to send survey to / where to publish information about the
survey?
This question leads me to a question that could be put into the survey:
Where have you read about this survey? (optional)
[Free form]
Fourth, how long should the survey last? When sending announcement we
should say where notice about Git User's Survey 2008 should be taken
down. Last year the survey was meant to take three weeks, but was up
longer. I'm thinking about having it last a month, or a month and a
half, starting from September 1.
And lasting until 2008-10-10? No, I do not really care.
So, some comments on the questions now:
About you
xx. What country are you in?
"What country do you live in?" perhaps?
Getting started with GIT
xx. How did you hear about Git?
There is a typo on survs.com (hear_d_).
Should this by the way be multiple choice?
I have heard about Git several times before I tried it.
I will only quote from survs.com now:
told by friend (word of mouth)
^^^^^^^^^^^^^^^ ? :) I think this should be removed
What other SCM did or do you use?
[..]
custom ( ) ( ) ( )
custom?
20. Which porcelains / interfaces / implementations do you use?
[ ] core-git
Uh, this is ambiguous. Is this our git or some script on top of git?
In both cases, this should be clarified.
22. Which git web interface do you use for your projects/have installed?
(Web interfaces used by git hosting sites do not count[*])
[...]
(*) Unless of cours you are hosting some git hosting site
^^^^^^^^ ^
typo, but I'd rather do s/of cours // and s/$/./ :-)
26. How often do you use the following forms of git commands
or extra git tools?
Never | Rare | Often
| Not yet, but sounds cool ;-)
No no :-)
But I wonder if we could split the "Never" case into several cases with
reasons like:
- Do not know.
- Not yet needed.
- Other (did not understand; tried but did not work; ...)
But this will perhaps bloat the question even more, so we should keep
"Never", though I think the reasons could be interesting.
Could some "Comments" field for question 26 help?
Some other comment: I dislike that there is *one* "Reset" button for
such matrix questions. But I guess you cannot change that?
28. Which of the following features do or did you use?
I think many of the possible replies have been used in several other
questions before, e.g. in
- 21. (gitk, git gui),
- 24. (git bundle),
- 26/27. (git gui, gitk, git stash)
- ...
But this question still seems to makes sense for:
[ ] eol conversion (crlf)
[ ] gitattributes
[ ] reflog (ref@{23})
[ ] shallow clone
[ ] detaching HEAD <- I think several people could have used that without knowing
[ ] commit templates
[ ] integration with IDE/editor
[ ] non-default hooks
And btw:
[ ] working with dirty tree <- Eh? Is this a feature?
Big thanks for your efforts,
Stephan
--
Stephan Beyer [off-list ref], PGP 0x6EDDD207FCC5040F
From: Stephan Beyer <hidden> Date: 2016-06-15 22:45:11
Hi,
I will only quote from survs.com now:
I have btw submitted on survs.com and it didn't say something like
"Thank you blablalba We have received your survey. / Your survey was
saved." or something like that.
It just put me to their "COMING SOON" front page.
Confusing behavior.
Is there some way to change that without writing an e-mail to survs.com
admins? ;-)
Regards,
Stephan
--
Stephan Beyer [off-list ref], PGP 0x6EDDD207FCC5040F
From: Mike Gant <hidden> Date: 2016-06-15 22:45:12
On Tue, Aug 19, 2008 at 7:08 PM, Jakub Narebski [off-list ref] wrote:
This is second revision (version) of proposed questions
for Git User's Survey 2008.
[snip]
xx. Which programming languages you are proficient with?
(zero or more: multiple choice)
- C, shell, Perl, Python, Tcl/Tk, C++, C#, Java, PHP,
Ruby, Emacs Lisp, Common Lisp or Scheme, Visual Basic,
Delphi, Assembly, other (please specify), I am not programmer
! C, shell, Perl, Python, Tcl/Tk
+ First version included only programming languages used
by git, and some from contrib area
Please include an "others" selection that will except a comma
list of languages. I'm an FPGA designer and use Verilog and
VHDL but I know they wouldn't be a common choice.
Mike
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:12
On Wed, 20 Aug 2008, Stephan Beyer wrote:
Jakub Narebski wrote:
quoted
By the way, should the survey be divided in pages, or simply use
headers to divide survey into sections?
Divided pages have a psychological impact, they don't look much and you
can say "Almost there!" on each page.
But headers and one-page surveys have a big advantage for users that pay
for Internet access per time unit: they can go offline, answer the
questions, and go online again to submit the survey.
So I've scrolled across your test survey on survs.com and I think it
should be kept on one page. Looks nice and manageable.
I also prefer single page surveys; it would be better if this survey
was shorter (by the way, how long did you took to complete test survey?),
but there are so many interesting questions...
quoted
Third, where to send survey to / where to publish information about the
survey?
This question leads me to a question that could be put into the survey:
Where have you read about this survey? (optional)
[Free form]
But where to add it? Additionally I'd rather limit free-form questions
to absolute minimum.
This is the question I was lacking, so I'll think about adding it to
the survey.
So, some comments on the questions now:
quoted
About you
xx. What country are you in?
"What country do you live in?" perhaps?
This is better phrasing. Changed.
quoted
Getting started with GIT
xx. How did you hear about Git?
There is a typo on survs.com (hear_d_).
Should this by the way be multiple choice?
I have heard about Git several times before I tried it.
Good idea, I think, and doesn't lead to more work when analysing.
And it would perhaps make it easier to choose appropriate answer.
Changed.
I will only quote from survs.com now:
quoted
told by friend (word of mouth)
^^^^^^^^^^^^^^^ ? :) I think this should be removed
O.K.
quoted
What other SCM did or do you use?
[..]
custom ( ) ( ) ( )
custom?
I mean here custom, not published (or no longer existing) SCM; something
that would be hard to write about.
I agree that it is not the best phrasing.
quoted
20. Which porcelains / interfaces / implementations do you use?
[ ] core-git
Uh, this is ambiguous. Is this our git or some script on top of git?
In both cases, this should be clarified.
There is "my own scripts" at the bottom; I mean here using no additional
porcelain, no interface on top of git command line.
But it is here for completeness only; however if you have some good
explanation for "core-git" option I can put it below this question.
quoted
22. Which git web interface do you use for your projects/have installed?
(Web interfaces used by git hosting sites do not count[*])
[...]
quoted
(*) Unless of cours you are hosting some git hosting site
^^^^^^^^ ^
typo, but I'd rather do s/of cours // and s/$/./ :-)
Thanks. Done.
quoted
26. How often do you use the following forms of git commands
or extra git tools?
Never | Rare | Often
| Not yet, but sounds cool ;-)
No no :-)
But I wonder if we could split the "Never" case into several cases with
reasons like:
- Do not know.
- Not yet needed.
- Other (did not understand; tried but did not work; ...)
But this will perhaps bloat the question even more, so we should keep
"Never", though I think the reasons could be interesting.
Could some "Comments" field for question 26 help?
Now it is 'never/rarely/sometimes/often'. I think there are enough
free form questions that one can put his/her own comments about git
commands in this survey...
Some other comment: I dislike that there is *one* "Reset" button for
such matrix questions. But I guess you cannot change that?
Yes, this is canned web survey site. I can only send feedback,
but I guess so can you (unless this requires subscription/invite...).
quoted
28. Which of the following features do or did you use?
I think many of the possible replies have been used in several other
questions before, e.g. in
- 21. (gitk, git gui),
- 24. (git bundle),
- 26/27. (git gui, gitk, git stash)
- ...
But this question still seems to makes sense for:
[ ] eol conversion (crlf)
[ ] gitattributes
[ ] reflog (ref@{23})
[ ] shallow clone
[ ] detaching HEAD <- I think several people could have used that without knowing
[ ] commit templates
[ ] integration with IDE/editor
[ ] non-default hooks
And btw:
quoted
[ ] working with dirty tree <- Eh? Is this a feature?
This is distinguishing feature. What I mean here that you can use
"git add" and "git commit" (not "git commit -a") and have some
uncommitted changes, like for example change of version in Makefile.
From: Stephan Beyer <hidden> Date: 2016-06-15 22:45:12
Hi,
Jakub Narebski wrote:
quoted
So I've scrolled across your test survey on survs.com and I think it
should be kept on one page. Looks nice and manageable.
I also prefer single page surveys; it would be better if this survey
was shorter
[...]
but there are so many interesting questions...
Yes, there are, but I think the length is ok and all questions are
optional (should this be mentioned somewhere?), right?
So there should be no problem.
(by the way, how long did you took to complete test survey?),
I filled in some stuff here and there and submitted, but I didn't
actually complete the survey.
But I'd say it's manageable within 10 minutes.
quoted
This question leads me to a question that could be put into the survey:
Where have you read about this survey? (optional)
[Free form]
But where to add it? Additionally I'd rather limit free-form questions
to absolute minimum.
If you want to add it nonetheless, then it could be question 60.
quoted
quoted
What other SCM did or do you use?
[..]
custom ( ) ( ) ( )
custom?
I mean here custom, not published (or no longer existing) SCM; something
that would be hard to write about.
This means the difference to "other" is that it is something somebody
has written for herself (or a company product only used in that
company) and "other" is some less popular but public SCM?
I see you've changed it to "custom (non published)". There is a typo:
s/non /non-/ ;)
Btw I wonder if people that are very new to git (perhaps started using
it in 1.6.0) will not know the "SCM" abbreviation. But the possible
choices should make it clear. (And if not, "Never" to everything will be
the right choice.)
quoted
Uh, this is ambiguous. Is this our git or some script on top of git?
In both cases, this should be clarified.
There is "my own scripts" at the bottom; I mean here using no additional
porcelain, no interface on top of git command line.
So just pure, naked git? The real git[tm]^H^H^H^H? ;-)
Ok, if I had not asked, I wouldn't have checked this option.
But it is here for completeness only; however if you have some good
explanation for "core-git" option I can put it below this question.
I think it should be rephrased by "git" or "git (pure)" or "git (core)".
But "core-git" really looks like another tool to me.
quoted
quoted
(*) Unless of cours you are hosting some git hosting site
^^^^^^^^ ^
typo, but I'd rather do s/of cours // and s/$/./ :-)
Thanks. Done.
Now it is:
(*) Unless of course you are hosting some git hosting site
^ ^ ^
I like punctuation:
(*) Unless, of course, you are hosting some git hosting site.
*nitpick* :-)
quoted
quoted
28. Which of the following features do or did you use?
I think many of the possible replies have been used in several other
questions before, e.g. in
- 21. (gitk, git gui),
- 24. (git bundle),
- 26/27. (git gui, gitk, git stash)
- ...
But this question still seems to makes sense for:
[ ] eol conversion (crlf)
[ ] gitattributes
[ ] reflog (ref@{23})
[ ] shallow clone
[ ] detaching HEAD <- I think several people could have used that without knowing
[ ] commit templates
[ ] integration with IDE/editor
[ ] non-default hooks
No comment here? ;-)
When replying to this question I really felt like having answered all
that before.
quoted
And btw:
quoted
[ ] working with dirty tree <- Eh? Is this a feature?
This is distinguishing feature. What I mean here that you can use
"git add" and "git commit" (not "git commit -a")
Sounds like "Taking advantage of using the index".
(Yesterday/today/tomorrow I am using SVN in university and I wished so
much that I had some git or at least git-svn[1] just because of the
*index*.)
OT Footnote [1]:
I tried to install git (and git-svn) into $HOME/root ($HOME/root/bin is
in PATH), but git-svn needs Perl bindings to SVN and they're pain to
install into $HOME/root from source, because it is in the subversion
source, and that needs a lot of Apache stuff and other things.
So does anybody own a quick guide how to get that working without having
to compile subversion from source (and without having root access, of
course)? ... (Some version of subversion is installed, but not the
perl modules. Just copying the .pm files did not seem to work.)
and have some
uncommitted changes, like for example change of version in Makefile.
Ok, this is "working with dirty tree", but I nonetheless wonder if this
is really a feature.
Another general comment: Multiple choice question have the disadvantage
that we cannot distinguish "None" and skipped questions.
So if this is an issue, I wonder if adding a "None of the above" choice
could help. But perhaps this is no issue and can be ignored.
Regards,
Stephan
--
Stephan Beyer [off-list ref], PGP 0x6EDDD207FCC5040F
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:12
Stephan Beyer wrote:
Jakub Narebski wrote:
quoted
quoted
This question leads me to a question that could be put into the survey:
Where have you read about this survey? (optional)
[Free form]
But where to add it? Additionally I'd rather limit free-form questions
to absolute minimum.
If you want to add it nonetheless, then it could be question 60.
I'll added it. It would be useful if there would be survey in
the following years.
quoted
quoted
quoted
What other SCM did or do you use?
[..]
custom ( ) ( ) ( )
custom?
I mean here custom, not published (or no longer existing) SCM; something
that would be hard to write about.
This means the difference to "other" is that it is something somebody
has written for herself (or a company product only used in that
company) and "other" is some less popular but public SCM?
Yes.
I see you've changed it to "custom (non published)". There is a typo:
s/non /non-/ ;)
Thanks, corrected and added explanation below the question.
[...]
quoted
But it is here for completeness only; however if you have some good
explanation for "core-git" option I can put it below this question.
I think it should be rephrased by "git" or "git (pure)" or "git (core)".
But "core-git" really looks like another tool to me.
Done.
quoted
quoted
quoted
(*) Unless of cours you are hosting some git hosting site
^^^^^^^^ ^
typo, but I'd rather do s/of cours // and s/$/./ :-)
Thanks. Done.
Now it is:
quoted
(*) Unless of course you are hosting some git hosting site
^ ^ ^
I like punctuation:
(*) Unless, of course, you are hosting some git hosting site.
*nitpick* :-)
Done.
quoted
quoted
quoted
28. Which of the following features do or did you use?
I think many of the possible replies have been used in several other
questions before, e.g. in
- 21. (gitk, git gui),
- 24. (git bundle),
- 26/27. (git gui, gitk, git stash)
- ...
But this question still seems to makes sense for:
[ ] eol conversion (crlf)
[ ] gitattributes
[ ] reflog (ref@{23})
[ ] shallow clone
[ ] detaching HEAD <- I think several people could have used that without knowing
[ ] commit templates
[ ] integration with IDE/editor
[ ] non-default hooks
No comment here? ;-)
When replying to this question I really felt like having answered all
that before.
They _are_ different questions; yes, some answers repeat themselves
because I tried each question to be self-contained, if possible, so
it should be easy to skip some question and still have full value
in the rest of questions.
quoted
quoted
And btw:
quoted
[ ] working with dirty tree <- Eh? Is this a feature?
This is distinguishing feature. What I mean here that you can use
"git add" and "git commit" (not "git commit -a")
Sounds like "Taking advantage of using the index".
(Yesterday/today/tomorrow I am using SVN in university and I wished so
much that I had some git or at least git-svn[1] just because of the
*index*.)
Hmmm... reading the above I have thought about adding "incremental
committing" to the list of features; I mean here the workflow of
"<edit>; git add; git diff/git diff --cached; <edit>; git add; commit"
But I think I'll just add "the index" to question
30. Which features do you find unique and/or useful ones,
compared to other systems (other SCMs)?
and leave the rest for free-form question 31. following it: "If you use
some important Git features not mentioned above, what are those?".
Another general comment: Multiple choice question have the disadvantage
that we cannot distinguish "None" and skipped questions.
So if this is an issue, I wonder if adding a "None of the above" choice
could help. But perhaps this is no issue and can be ignored.
From: Stephan Beyer <hidden> Date: 2016-06-15 22:45:13
Hi again,
8. Which Git version(s) are you using?
[ ] pre 1.3
[ ] 1.3.x
...
[ ] master
[ ] next
I wonder if people who do not know about master/next being git.git
branches may do "[X] next" because they think they will use the next
version available.
So could you write "master branch of official git repository" and the
same for "next"?
12. What other SCM did or do you use?
...
By "custom (non-published)" it is meant here version control system
which was not released to the public, for example something written
for yourself, or internal company project used only in company.
Better:
"custom (non-published)" means a version control system which has
not been released to the public, for example, something written for
yourself or your company only.
And I am unsure if "SCM" is better than "version control system"
in this sentence, but I do not think this is really important.
16. I use Git for (check all that apply):
...
Note that above choices are neither orthogonal nor exclusive.
You might want to check multiple answers wven for single repository.
^^^^^^^^^ "even for a"
17. How do you obtain Git?
...
[ ] pull form main repository
^^^^ from
Explanation: binary package covers pre-compiled binary; source script
is meant to cover installation in source-based distributions, like
'emerge' in Gentoo.
"pre-compiled binary (e.g. from rpm or deb archives)"
Right?
I think naming two popular package formats of distributors should people
help to get the point.
29. Which of the following features do or did you use?
I still dislike that there are a lot of choices that generate redundancy
to other questions.
On the other hand, scientific surveys always contain (hidden) redundancy
to ensure that the test person gives sane answers.
59. Should Git User's Survey be repeated next year?
( ) Yes
( ) No
( ) no opinion
Reset
I wonder if the "no opinion" choice is not needed because there is the
"Reset" button.
Apropos!
Is it possible to add a header text?
I'd like that there are three things being clarified at the beginning of
the survey page:
* The survey is anonymous, but all information that the users provide will
be publicly available on the wiki.
* The users may skip questions as they like.
* The user needs JavaScript to submit the survey.
I btw do not like the last fact, but since most users nowadays have
JavaScript activated, it may not be that bad.
Also, I still do not get a succesful message after submitting, but that
may be related to the channel (test), if you have configured it like
that. Have you? ;)
Regards,
Stephan
--
Stephan Beyer [off-list ref], PGP 0x6EDDD207FCC5040F
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:13
On Sun, 24 Aug 2008, Stephan Beyer napisał:
Hi again,
quoted
8. Which Git version(s) are you using?
[ ] pre 1.3
[ ] 1.3.x
...
quoted
[ ] master
[ ] next
I wonder if people who do not know about master/next being git.git
branches may do "[X] next" because they think they will use the next
version available.
So could you write "master branch of official git repository" and the
same for "next"?
Thanks. I've added this.
quoted
12. What other SCM did or do you use?
...
quoted
By "custom (non-published)" it is meant here version control system
which was not released to the public, for example something written
for yourself, or internal company project used only in company.
Better:
"custom (non-published)" means a version control system which has
not been released to the public, for example, something written for
yourself or your company only.
Thank you, that is much better.
And I am unsure if "SCM" is better than "version control system"
in this sentence, but I do not think this is really important.
Hmmm...
quoted
16. I use Git for (check all that apply):
...
quoted
Note that above choices are neither orthogonal nor exclusive.
You might want to check multiple answers wven for single repository.
^^^^^^^^^ "even for a"
Corrected. Thanks.
quoted
17. How do you obtain Git?
...
quoted
[ ] pull form main repository
^^^^ from
Corrected. Thanks.
quoted
Explanation: binary package covers pre-compiled binary; source script
is meant to cover installation in source-based distributions, like
'emerge' in Gentoo.
"pre-compiled binary (e.g. from rpm or deb archives)"
Thanks, added.
quoted
59. Should Git User's Survey be repeated next year?
quoted
( ) Yes
( ) No
( ) no opinion
Reset
I wonder if the "no opinion" choice is not needed because there is the
"Reset" button.
Apropos!
Is it possible to add a header text?
It is possible.
I'd like that there are three things being clarified at the beginning of
the survey page:
* The survey is anonymous, but all information that the users provide will
be publicly available on the wiki.
* The users may skip questions as they like.
* The user needs JavaScript to submit the survey.
Thanks for reminding this. I have added this to survey.
I btw do not like the last fact, but since most users nowadays have
JavaScript activated, it may not be that bad.
F**k. I didn't notice this soon enough, and now I'd rather not re-enter
all 60 questions. I have sent feedback that requiring JavaScript to be
able to submit survey is strange.
Survs.com came recommended here on this mailing list. I have chosen it
over editing old www.survey.net.nz because it had "other (please specify)"
for both single answer (radio button) and multiple choice (checkbox)
question; later also because of the "matrix" questions. I didn't realize
that it requires JavaScript to submit... perhaps this would get corrected
before starting point for Git User's Survey 2008 (1 September, or later).
Also, I still do not get a succesful message after submitting, but that
may be related to the channel (test), if you have configured it like
that. Have you? ;)
Yes, that depends on channel configuration, and I have forgot to add it
for this channel.
Thanks again for checking this survey, and for your comments.
BTW. here is analysis of 'test' channel (note that some questions, and
some possible answers, were added after starting 'test' channel):
http://www.survs.com/app/4/wo/Y03N37u4Ou5p9SmoNrc5f0/0.0.33.1.1.1.1.5.1.1.0.1.1.7.11.0.1.0.13.1.1
--
Jakub Narebski
Poland
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:13
This is third (and hopefully last) revision of proposed questions
and announcement for Git User's Survey 2008.
First, it was decided that it would be web based survey. I would use
Survs.com (new, in beta); it is unlikely to change as all questions
are entered there already and moving it would require quite a bit of
work. It was recommended here on the list (I have received courtesy
invitation; thanks a lot); I have chosen it over survey.net.nz, used for
preceding 2006 (by Paolo Ciarrocchi) and 2007 (by me) surveys, because
it has some nice features, and allows export of results to CSV format
for further analysis.
Note that new features like "matrix" questions and ability to have
'other' selection for single choice and multiple choice questions
affect a bit form of this survey. This also affect chance to move
survey to different web survey site.
There are good news and bad news about choosing Survs.com. Good news is
that there would be no problem of free Survs beta account expiring
during running survey, or during analysis. Bad news is that submitting
survey currently requires having JavaScript enabled, which was pointed
out by Stephan Beyer; they are working on it, but I don't know if this
issue would be corrected in time for planned duration of Git User's
Survey 2008.
Second, what possible answers in the case of single answer and multiple
answer questions should be? You can view current version of survey at
provided survey link (see below), currently test one only. Please
point typos, mistakes and errors; I am not native English speaker.
Third, where to send survey to / where to publish information about the
survey? Last year the announcement was send to git mailing list, to
LKML (Linux kernel mailing list), and mailing list for git projects
found on GitProjects page on GIT wiki. Now that the number of projects
using Git as version control system has grown, I don't think it would
be good idea to "spam" all those mailing list; and if we don't send
notice to all other projects I'm not sure if we should include LKML.
Last year survey announcement was put on Git Homepage (thanks Pasky),
and on front page of Git Wiki; info about survey was also put on two
git hosting sites: kernel.org and repo.or.cz. It would be nice if it
was possible to put announcement about Git User's Survey 2008 at front
pages of other Git hosting sites, like GitHub (one of most popular, I
think), Gitorious, Freedesktop.org. If you know some other popular Git
hosting sites, and even better if you know who to contact about putting
survey announcement, please write. Is there some channel that I have
forgot about? Should info/announcement about Git User's Survey 2008 be
sent also to one of on-line magazines like LinuxToday or LWN, or asked
to put on some blog? I'll add it as journal entry for #git on Ohloh,
and try to make it so it would appear in "News" section for Ohloh
project page for Git: http://www.ohloh.net/projects/git.
Survs.com has nice feature of "channels", which allow to count
responses sent via different means separately; I am using it to
publish URL for 'test' channel - answers from this channel won't be
counted AT ALL!!!
I am thinking about asking to put annoncement about Git User's
Survey 2008 at the following places (in parenthesis there are people who
I think can ask to put announcement about survey):
* git.or.cz, Git Homepage (Petr 'Pasky' Baudis)
* git-scm.com, alternate Git Homepage (Scott Chacon)
* http://git.or.cz/gitwiki/FrontPage (it is wiki, after all)
* #git channel subject (one of channel admins, but who?)
* git.kernel.org (John 'Warthog9' Hawley)
* repo.or.cz (Petr 'Pasky' Baudis)
* gitorious.org (???)
* github.com (???)
* ...
What are other git hosting sites, or blogs, or other sites where to ask
to put announcement about this survey?
Fourth, how long should the survey last? When sending announcement we
should say where notice about Git User's Survey 2008 should be taken
down. Last year the survey was meant to take three weeks, but was up
longer. I'm thinking about having it last a month, or a month and a
half, starting from September 1.
Below there is second version of announcement email (I should probably
come up also with boilerplate announcement for web pages). I haven't
put third version of this year round of questions, because text of
survey at Survs.com and what I had written diverged, I'm sorry...
----
Hello all,
We would like to ask you a few questions about your use of the Git
version control system. This survey is mainly to understand who is
using Git, how and why.
The results will be published to the Git wiki and discussed on the git
mailing list.
We'll close the survey in 1 month starting from today, 1 September.
Please devote a few minutes of your time to fill this simple
questionnaire, it will help a lot the git community to understand your
needs, what you like of git, and of course what you don't like of it.
The survey can be found here:
http://www.survs.com/survey?id=M3PIVU72&channel=9XYYGHJ77G
(this is temporary channel URL; responses to this URL would
be, I guess, discarded).
----
You can view survey results (only summary, not individual responses)
at http://www.survs.com/shareResults?survey=M3PIVU72&rndm=OKJQ45LAG8
--
Jakub Narebski
Poland
From: Stephan Beyer <hidden> Date: 2016-06-15 22:45:14
Hi,
Jakub Narebski wrote:
Fourth, how long should the survey last?
I still think Oct 10 (a Friday) is a good date.
This is ~6 weeks - other opinions?
(I should probably come up also with boilerplate announcement for web
pages).
Ok, I've written a text that can be seen as some kind of announcement
template for news on {Open Source,programming,Linux}-related news sites.
--8<--
Git User's Survey Begins
Two weeks after the major release of Git version 1.6.0,
the Git community starts a survey containing 60 questions
that can help to understand the users' needs, behavior,
and what they like and dislike about Git.
<a href="http://git.or.cz">Git</a> is a distributed source code
management system (or in other words: distributed version control system)
that was initially written by Linus Torvalds for the Linux kernel
development after the proprietary BitKeeper system stopped being
free of charge in 2005.
Quickly Git gained popularity and other Open Source projects like
<a href="http://www.x.org/wiki/Development/git">X.org</a>,
<a href="http://git.videolan.org/">VLC</a> or
<a href="http://www.winehq.org/site/git">WINE</a>
began to use it.
There have already been user surveys in
<a href="http://git.or.cz/gitwiki/GitSurvey">2006</a> and
<a href="http://git.or.cz/gitwiki/GitSurvey2007">2007</a>.
Since then, a lot has changed.
Git users are called upon to answer the questions until Oct 10, 2008.
After that date, the results can be found on the
<a href="http://git.or.cz/gitwiki/GitSurvey2008">Git Wiki</a>
in CSV format and in some evaluated form.
Link: http://www.survs.com/survey?id=M3PIVU72&channel=2WXE4BVTW8
or: http://tinyurl.com/gitsurvey2008 (a short link, not yet generated)
or: http://git.or.cz/gitwiki/GitSurvey2008
-->8--
Of course, this is open for improvements and discussion.
BTW, this is explicitly _not_ meant for Git-specific web sites.
There the announcement of the last year might be sufficient, in
some slightly changed form:
--8<--
<a href="...">The Git User's Survey</a> is up!
Please devote a few minutes of your time to fill this simple questionnaire.
It will help the Git community to understand your needs, what you like of
Git, and, of course, what you don't like of it.
-->8--
Regards,
Stephan
--
Stephan Beyer [off-list ref], PGP 0x6EDDD207FCC5040F
From: Jakub Narebski <hidden> Date: 2016-06-15 22:45:15
This is fourth (and hopefully last) revision of proposed questions
and announcement for Git User's Survey 2008. This time is mainly about
creating good cover (announcement) letter, and about where to announce
the survey.
Survey would be at Survs.com, is spite of its deficiencies like
requiring JavaScript to submit (which might get corrected before
planned start of survey); it has some nice features which survey.net.nz
(the site which was used for 2006 and 2007 surveys) doesn't have.
Moving to other _free_ web survey site now would be difficult...
You can view current version of survey at provided survey link (see
below); unfortunately proposed questions (and answers) diverged a bit
from what was entered at Survs.com. It would be possible nevertheless
to get current version of questions, comments, and possible answers, if
required.
Questions that remains: where to send announcement about this survey,
and what should be written in such announcement. I am thinking about
asking to put announcement about Git User's Survey 2008 at the
following places (in parenthesis there are people who, I think,
I can ask to put announcement about survey):
* git.or.cz, Git Homepage (Petr 'Pasky' Baudis)
* git-scm.com, alternate Git Homepage (Scott Chacon)
* http://git.or.cz/gitwiki/FrontPage (it is wiki, after all)
* #git channel subject (one of channel admins, but who?)
* git.kernel.org (John 'Warthog9' Hawley)
* repo.or.cz (Petr 'Pasky' Baudis)
* gitorious.org (???)
* github.com (???)
* ...
What are other git hosting sites, or blogs, or other sites where to ask
to put announcement about this survey?
Below there is new version of announcement email:
-- >8 --
To: git@vger.kernel.org, (probably other sites).
Subject: [ANNOUNCE] Git User's Survey 2008
Hello all,
We would like to ask you a few questions about your use of the Git
version control system. This survey is mainly to understand who is
using Git, how and why.
The results will be published to the Git wiki and discussed on the git
mailing list.
The survey would be open from 1 September till 10 October.
Please devote a few minutes of your time to fill this simple
questionnaire, it will help a lot the git community to understand your
needs, what you like of git, and of course what you don't like of it.
The survey can be found here:
http://www.survs.com/survey?id=M3PIVU72&channel=2WXE4BVTW8
-------
Note that above channel is currently _closed_. If you want to take
a peek at current version of the survey, use "test" channel:
http://www.survs.com/survey?id=M3PIVU72&channel=9XYYGHJ77G
(it should be open, unless I am modifying some questions). You can find
summary analysis (without answers to free-form questions) at:
http://www.survs.com/shareResults?survey=M3PIVU72&rndm=OKJQ45LAG8
Stephan Beyer proposed the following announcement template for news on
{Open Source,programming,Linux}-related news sites (with some small
modifications by me):
-- >8 --
Subject: Git User's Survey 2008 Begins
Two weeks after the major release of Git version 1.6.0,
the Git community starts a survey containing 60 questions
that can help to understand the users' needs, behavior,
and what they like and dislike about Git.
<a href="http://git.or.cz">Git</a> is a distributed source code
management system (or in other words: distributed version control
system) that was initially written by Linus Torvalds for the Linux
kernel development after the proprietary BitKeeper system stopped being
free of charge in 2005. Quickly Git gained popularity and other Open
Source projects like
<a href="http://www.x.org/wiki/Development/git">X.org</a>,
<a href="http://git.videolan.org/">VLC</a> or
<a href="http://www.winehq.org/site/git">WINE</a>
began to use it.
There have already been user surveys in
<a href="http://git.or.cz/gitwiki/GitSurvey">2006</a> and
<a href="http://git.or.cz/gitwiki/GitSurvey2007">2007</a>.
Since then, a lot has changed.
Git users are called upon to answer the questions until Oct 10, 2008.
After that date, the results can be found on the
<a href="http://git.or.cz/gitwiki/GitSurvey2008">Git Wiki</a>
in CSV format, and later in some evaluated form.
Link: http://www.survs.com/survey?id=M3PIVU72&channel=2WXE4BVTW8
or: http://tinyurl.com/gitsurvey2008 (a short link, not yet generated)
or: http://git.or.cz/gitwiki/GitSurvey2008
-- 8< --
And below there is proposed announcement to be put on git-relates sites,
like Git Homepage (git.or.cz and git-scm.com), GitWiki (FrontPage), and
git hosting sites (repo.or.cz, kernel.org, freedesktop.org, gitorious,
github,...
-- >8 --
<a href="...">The Git User's Survey</a> is up!
Please devote a few minutes of your time to fill this simple
questionnaire. It will help the Git community to understand your
needs, what you like of Git, and, of course, what you don't like of
it.
-- 8< --
What is lacking is how the request/announcement _email_ to be send to
administrators of those sites would look like. Help, please?
P.S. In 2006 I think the announcement was put only on git mailing list,
in 2007 beside putting it on repo.or.cz, git.kernel.org and GitWiki it
was send to mailing lists (and newsgroups) for many different projects
which use git for development, as SCM of choice. But the number of
such projects has grown enormously. I wonder if we should send survey
announcements also to individual mailing lists for different projects,
like WINE, OLPC, X.Org, etc.
--
Jakub Narebski
Poland
On Sat, Aug 30, 2008 at 03:33:45AM +0200, Jakub Narebski wrote:
Questions that remains: where to send announcement about this survey,
and what should be written in such announcement. I am thinking about
asking to put announcement about Git User's Survey 2008 at the
following places (in parenthesis there are people who, I think,
I can ask to put announcement about survey):
* git.or.cz, Git Homepage (Petr 'Pasky' Baudis)
* git-scm.com, alternate Git Homepage (Scott Chacon)
* http://git.or.cz/gitwiki/FrontPage (it is wiki, after all)
* #git channel subject (one of channel admins, but who?)
* git.kernel.org (John 'Warthog9' Hawley)
* repo.or.cz (Petr 'Pasky' Baudis)
* gitorious.org (???)
* github.com (???)
For github.com, you would ask Chris Wanstrath or PJ Hyett.
--
Garry Dolley
ARP Networks, Inc.
http://scie.nti.st
Los Angeles County REACT, Unit 336
WQGK336
From: Paolo Ciarrocchi <hidden> Date: 2016-06-15 22:45:16
On Sat, Aug 30, 2008 at 3:33 AM, Jakub Narebski [off-list ref] wrote:
Hi Jakub!
P.S. In 2006 I think the announcement was put only on git mailing list,
No, in 2006 I sent the announcement to the following lists:
wine-users@winehq.org
xmms2-devel@lists.xmms.org
xcb@lists.freedesktop.org
cairo@cairographics.org
u-boot-users@lists.sourceforge.net
git@vger.kernel.org
linux-kernel@vger.kernel.org
linux@ml.bilug.linux.it (my LUG)
Ciao,
--
Paolo
http://paolo.ciarrocchi.googlepages.com/