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

Re: [RFC v2] Git User's Survey 2008

From
Jakub Narebski <jnareb@gmail.com>
Date
Aug 21, 2008, 11:11 UTC
Message-ID
<200808211311.24600.jnareb@gmail.com>
In-Reply-To
<20080820211852.GA27226@leksak.fem-net>
On Wed, 20 Aug 2008, Stephan Beyer wrote:
Show 14 quoted lines
> Jakub Narebski wrote:
> 
> > 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...
 
Show 7 quoted lines
> > 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.

Show 7 quoted lines
> So, some comments on the questions now:
> 
> > About you
> > 
> >    xx. What country are you in?
> 
> "What country do you live in?" perhaps?
This is better phrasing.  Changed.
 
Show 7 quoted lines
> > 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:
> 
> > told by friend (word of mouth)
>                  ^^^^^^^^^^^^^^^ ? :) I think this should be removed
O.K.
Show 5 quoted lines
> > 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.
Show 5 quoted lines
> > 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.

Show 6 quoted lines
> > 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/$/./ :-)
Thanks.  Done.
Show 17 quoted lines
> > 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...).

Show 21 quoted lines
> > 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?

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.

> Big thanks for your efforts,
>   Stephan
You are welcome.
-- 
Jakub Narebski
Poland
Previous: Stephan BeyerNext: Stephan Beyer
Message 78 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.