git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] Git User's Survey 2008

From
Stephan Beyer <s-beyer@gmx.net>
Date
Jul 23, 2008, 14:12 UTC
Message-ID
<20080723141224.GA17648@leksak.fem-net>
In-Reply-To
<200807230325.04184.jnareb@gmail.com>
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. :)

Show 7 quoted lines
> 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.
Show 5 quoted lines
>        (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,...?)
Perhaps yes.
The programming language list
	https://www.ohloh.net/tools
could be a start %)
>      - 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?

Show 7 quoted lines
>    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:
Show 10 quoted lines
>    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.

Show 5 quoted lines
>    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? :)
Show 7 quoted lines
>    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?"

Show 17 quoted lines
> 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?
Show 5 quoted lines
> 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 <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
Previous: Jakub NarebskiNext: Stephan Beyer
Message 50 of 93 in “[RFC] Git User's Survey 2008”
  1. Jakub NarebskiJul 23, 2008
  2. Junio C HamanoJul 23, 2008
  3. HP-UX issues (WAS: Re: [RFC] Git User's Survey 2008)Miklos Vajna, Jul 23, 2008
  4. Jakub NarebskiJul 23, 2008
  5. Miklos VajnaJul 23, 2008
  6. Jakub NarebskiJul 23, 2008
  7. Marek ZawirskiJul 24, 2008
  8. Mailing lists, was Re: [RFC] Git User's Survey 2008Johannes Schindelin, Jul 24, 2008
  9. Shawn O. PearceJul 25, 2008
  10. Junio C HamanoJul 25, 2008
  11. Jakub NarebskiJul 25, 2008
  12. Shawn O. PearceJul 25, 2008
  13. Junio C HamanoJul 25, 2008
  14. Shawn O. PearceJul 25, 2008
  15. Jakub NarebskiJul 26, 2008
  16. Marek ZawirskiJul 26, 2008
  17. Shawn O. PearceJul 26, 2008
  18. Jean-François VeilletteJul 26, 2008
  19. Petr BaudisJul 25, 2008
  20. Jing XueJul 26, 2008
  21. Jakub NarebskiJul 26, 2008
  22. Shawn O. PearceJul 26, 2008
  23. Jakub NarebskiJul 26, 2008
  24. Johannes SchindelinJul 26, 2008
  25. Scott ChaconJul 26, 2008
  26. Jakub NarebskiJul 24, 2008
  27. Johannes SchindelinJul 23, 2008
  28. Jakub NarebskiJul 23, 2008
  29. Johannes SchindelinJul 23, 2008
  30. Robin RosenbergJul 23, 2008
  31. Johannes SchindelinJul 23, 2008
  32. Jakub NarebskiJul 24, 2008
  33. Jakub NarebskiJul 23, 2008
  34. Johannes SchindelinJul 23, 2008
  35. Stephan BeyerJul 23, 2008
  36. david@lang.hmJul 24, 2008
  37. Stephan BeyerJul 24, 2008
  38. david@lang.hmJul 24, 2008
  39. Jakub NarebskiJul 24, 2008
  40. Jakub NarebskiJul 26, 2008
  41. Nguyen Thai Ngoc DuyJul 27, 2008
  42. Junio C HamanoJul 23, 2008
  43. Jakub NarebskiJul 24, 2008
  44. Dmitry PotapovJul 23, 2008
  45. Johannes SchindelinJul 23, 2008
  46. Stephan BeyerJul 23, 2008
  47. Jakub NarebskiJul 24, 2008
  48. Alex RiesenJul 23, 2008
  49. Jakub NarebskiJul 24, 2008
  50. Stephan BeyerJul 23, 2008
  51. Stephan BeyerJul 24, 2008
  52. Dmitry PotapovJul 23, 2008
  53. Matthias KestenholzJul 23, 2008
  54. Dmitry PotapovJul 23, 2008
  55. Jakub NarebskiJul 23, 2008
  56. Dmitry PotapovJul 24, 2008
  57. Jakub NarebskiJul 24, 2008
  58. Petr BaudisJul 23, 2008
  59. Jakub NarebskiJul 23, 2008
  60. Jon LoeligerJul 24, 2008
  61. Jakub NarebskiJul 24, 2008
  62. Lachele Foley (Lists)Jul 24, 2008
  63. Jakub NarebskiJul 24, 2008
  64. Dmitry PotapovJul 24, 2008
  65. Jakub NarebskiJul 24, 2008
  66. Jakub NarebskiJul 31, 2008
  67. [RFC v2] Git User's Survey 2008Jakub Narebski, Aug 20, 2008
  68. Alex RiesenAug 20, 2008
  69. Petr BaudisAug 20, 2008
  70. Jakub NarebskiAug 20, 2008
  71. Alex RiesenAug 20, 2008
  72. Junio C HamanoAug 20, 2008
  73. Jakub NarebskiAug 21, 2008
  74. Junio C HamanoAug 21, 2008
  75. Jakub NarebskiAug 21, 2008
  76. Stephan BeyerAug 20, 2008
  77. Stephan BeyerAug 20, 2008
  78. Jakub NarebskiAug 21, 2008
  79. Stephan BeyerAug 21, 2008
  80. Jakub NarebskiAug 22, 2008
  81. Mike GantAug 21, 2008
  82. Stephan BeyerAug 24, 2008
  83. Jakub NarebskiAug 25, 2008
  84. Abhijit BhopatkarAug 20, 2008
  85. [RFC v3] Git User's Survey 2008Jakub Narebski, Aug 25, 2008
  86. Stephan BeyerAug 28, 2008
  87. [RFC v4] Git User's Survey 2008 (cover letters)Jakub Narebski, Aug 30, 2008
  88. Garry DolleyAug 30, 2008
  89. Paolo CiarrocchiSep 1, 2008
  90. Miguel ArrozJul 23, 2008
  91. Jakub NarebskiJul 23, 2008
  92. Sverre RabbelierJul 24, 2008
  93. Jakub NarebskiAug 25, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.