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

Re: [RFC] Git User's Survey 2008

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 23, 2008, 16:43 UTC
Message-ID
<7vwsjcft5g.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<200807231508.42334.jnareb@gmail.com>
Jakub Narebski <jnareb@gmail.com> writes:
Show 19 quoted lines
> 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.
>> 
>> >    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?

I refrained saying this in my initial response, but my initial reaction was "Why are you even asking this?".

Yes, "getting to know you" demographics are customary done in surveys, and you kept it to the minimum which is also good, but I do not think this particular question is very interesting. For one thing, the question assumes the participant is a programmer, and we are giving an impression that we are interested in better programmers. Do we *still* require users to be a programmer to use git? I do not think so. Having to answer "none of these" to this question would make you feel unnecessarily bad, even if you are not a programmer and you know at the intellectual level that it is not your flaw not to be proficient in any.

Asking about geographic location and preferred human languages might help to gauge what l10n are desired for GUIs, but even there, don't forget that we are no company. We do not research markets and translate messages to missing languages, however popular, before being asked. That's not how we operate. So the result of these questions will be mainly to satisfy our curiosity, nothing more.

"What kind of content do you track" might also be an equally interesting question. It also falls into the curiosity department, though.

> 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...

And when you expect very many respondents, (1) you cannot afford to free-form; and (2) statistics over multiple choices, as long as choices are well seeded, will give you a good enough overview picture.

> Again: free form has some hassles, but so does coming up with good
> choice of fixed answers in multiple choice question.

You need to do at least one or the other, and I do not think there is any way to avoid that. Without a good choices, histogram would become useless (not necessarily because the answer will be dominated by "Other", but the seeing the choices tends to set the frame of mind when/before somebody answers the question). With free-form, you will spend the rest of your life analyzing to get any useful insight.

Previous: Nguyen Thai Ngoc DuyNext: Jakub Narebski
Message 42 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.