It's been more than a year since last Git User's Survey. It would be interesting to find what changed since then. Therefore the idea to have another survey. I have put the survey on Survey.Net, but *please* don't fill it yet. Please check out the questions and answers, and note if there are any mistakes, missed possible answers, or bad type for a question (for example shorttext vs textarea). I am planning to send the info below to git projects' mailing lists (see below), git mailing list, LWN, NewsForge and Slashdot. If you think of place to send information about git survey to, please do comment. Please also comment (and correct) on the form of this survey announcement (which basically is stolen from Paolo, from previous survey). Pasky, could you please put info about git survey (when it would start of course) on git homepage, perhaps on git wiki front page, and in #git channel description? References to be: http://git.or.cz/gitwiki/GitSurvey2007 http://thread.gmane.org/gmane.comp.version-control.git/53665 ---- Linux-MIPS, Linux-NFS, OpenVZ, Agave, collectd, CRUX Linux, dash DirectFB, Eddt, Elinks, LilyPond, Herrie, netconf, KDbg, Palava, Paraslash, OLPC, Sidestep, SourceMage Linux, Tangram 2, Thousand Parsec, U-Boot, X.Org, XCB, D-Bus, HAL, Cairo, Mesa3D, WINE, XMMS2, XStrikeForce (XSF). Some of the projects I cannot send email to, because their lists are subscribe only (e.g. itools, Openbox). For some I haven't found email/mailing list. ---- 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 three weeks 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.survey.net.nz/survey.php?94e135ff41e871a1ea5bcda3ee1856d9 ---- About you 01. What country are you in? 02. What is your preferred non-programming language? 03. How old are you? 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 Getting started with GIT 05. How did you hear about GIT? 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? 08. What did you find hardest? 09. When did you start using git? From which version? * (date, or version, or both) Other SCMs 10. What other SCM do you use? 11. Why did you choose GIT? 12. Why did you choose other SCMs? 13. What would you require from GIT to enable you to change, if you use other SCM for your project? 14. Did you import your repository from foreign SCM? Which SCM? 15. What tool did you use for import? 16. Do your GIT repository interact with other SCM? Which SCM? 17. What tool did/do you use to interact? How you use GIT 18. Do you use GIT for work, unpaid projects, or both? work/unpaid projects/both/none(*) (*)I use git to interact with some project I'm interested in 19. How do you obtain GIT? Source tarball, binary package, or pull the main repository? - binary package/source tarball/pull from main repository 20. What hardware platforms do you use GIT on? * examples: i386, x86_64, ARM, PowerPC, Alpha, g5, ... 21. What OS (please include the version) do you use GIT on? * examples: Linux, MS Windows (Cygwin/MinGW/gitbox), IRIX, HP-UX, Solaris, FreeBSD, ... (please give kernel version and distribution for Linux) 22. What projects do you track (or download) using GIT (or git web interface)? 23. How many people do you collaborate with using GIT? 24. How big are the repositories that you work on? (e.g. how many files, how much disk space, how deep is the history?) * number of files in repository: "git ls-tree -r HEAD | wc -l" * largest file under version control * pack size of freshly cloned fully packed repository * number of commits in straight line, number of commits in branch ("git rev-list --first-parent HEAD | wc -l", "git rev-list HEAD | wc -l") 25. How many different projects do you manage using GIT? 26. Which porcelains do you use? (zero or more: multiple choice) - core-git, cogito (deprecated), StGIT, guilt, pg (deprecated), my own scripts, other 27. Which git GUI do you use (zero or more: multiple choice) - CLI, gitk, git-gui, qgit, gitview, giggle, tig, instaweb, (h)gct, qct, KGit, git.el, other 28. Which (main) git web interface do you use for your projects? - gitweb/cgit/wit (Ruby)/git-php/other 29. How do you publish/propagate your changes? (zero or more: multiple choice) - push, pull request, format-patch + email, bundle, other 30. Does git.git repository include code produced by you? - yes/no Internationalization 31. Is translating GIT required for wider adoption? - yes/no/somewhat 32. What do you need translated? * examples: git-gui, qgit, git messages, manpages, user's manual 33. For what language do you need translation for? What you think of GIT 34. Overall, how happy are you with GIT? - unhappy/not so happy/happy/very happy/completely ecstatic 35. How does GIT compare to other SCM tools you have used? - worse/equal (or comparable)/better 36. What do you like about using GIT? 37. What would you most like to see improved about GIT? (features, bugs, plug-ins, documentation, ...) 38. If you want to see GIT more widely used, what do you think we could do to make this happen? Changes in GIT (since year ago, or since you started using it) 39. Did you participate in previous Git User's Survey? - yes/no 40. What improvements you wanted got implemented? 41. What improvements you wanted didn't get implemented? 42. How do you compare current version with version from year ago? - current version is: better/worse/no changes 43. Which of the new features do you use? (zero or more: multiple choice) - git-gui, bundle, eol conversion, gitattributes, submodules, worktree, #release notes, #user's manual, reflog, stash, shallow clone, detached HEAD, #fast-import, mergetool, interactive rebase, commit template, blame improvements, #other (not mentioned here) Documentation 44. Do you use the GIT wiki? - yes/no 45. Do you find GIT wiki useful? - yes/no/somewhat 46. Do you contribute to GIT wiki? - yes/no/only corrections or spam removal 47. Do you find GIT's on-line help (homepage, documentation) useful? - yes/no/somewhat 48. Do you find help distributed with GIT useful (manpages, manual, tutorial, HOWTO, release notes)? - yes/no/somewhat 49. Do you contribute to GIT documentation? - yes/no 50. What could be improved on the GIT homepage? 51. What topics would you like to have on GIT wiki? 52. What could be improved in GIT documentation? Getting help, staying in touch 53. Have you tried to get GIT help from other people? - yes/no 54. If yes, did you get these problems resolved quickly and to your liking? - yes/no 55. Would commerical (paid) support from a support vendor be of interest to you/your organization? 56. Do you read the mailing list? 57. If yes, do you find it useful? - yes/no (optional) 58. Do you find traffic levels on GIT mailing list OK. - yes/no? (optional) 59. Do you use the IRC channel (#git on irc.freenode.net)? - yes/no 60. If yes, do you find IRC channel useful? - yes/no (optional) 61. Did you have problems getting GIT help on mailing list or on IRC channel? What were it? What could be improved? Open forum 62. What other comments or suggestions do you have that are not covered by the questions above? -- Jakub Narebski Poland - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
