{"thread":{"id":"24279","subject":"[RFC] Git User's Survey 2010 (resend)","startedAt":"2010-07-03T19:58:55Z","lastAt":"2010-08-10T22:16:27Z","messageCount":24,"participants":["Jakub Narebski","Ævar Arnfjörð Bjarmason","David Bainbridge","Scott Chacon","Yann Dirson","Felipe Contreras"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"144753","messageId":"201007032158.57700.jnareb@gmail.com","threadId":"24279","inReplyTo":null,"subject":"[RFC] Git User's Survey 2010 (resend)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-07-03T19:58:55Z","receivedAt":"2010-07-03T19:58:55Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"I'm sorry for broken (badly wrapped) previous version...\n----\n\nI guess it is time for annual (so far) Git User's Survey.  Should\nthere be one?  When should it start, and how long should it last?\n\nhere is how it was for previous surveys:\n * 2009 was open from 15 July   to 15 September 2009 (for 2 months)\n * 2008 was open from 31 August to 14 October 2008 (for 1.5 months)\n * 2007 was open from 20 August to 10 September 2007 (for 20 days)\n        (officially: results are up until 28 September 2007)\n * 2006 was open from 23 July   to 6-12 September 2006 \n   (for a bit less than 2 months)\n\nWith more that 3000 responses in 2008 and 2009 survey, analysing\nfree-form data was hard.  That is why in this proposal there is only\nsingle one free-form response (about missing features).\n\nWhat questions (and with what proposed answers) shound there be in\nthis year survey?  Below there is the content of the proposed survey:\n\n\n= Git User's Survey 2010 (proposal) =\n\n== About you ==\n\nNOTES: \n^^^^^^\nThis section gives us a bit of demographical information about survey\nresponders.  Is it useful?  Should we leave it in survey, or remove it?\n\nShould we for example include 'gender' as one of questions?  Perl Survey\n2010 did.\n\n\n=== 01. What country do you live in? ===\n        (Country of residence)\n(free-form single line)\n\nNOTES:\n^^^^^^\nPerhaps a better solution would be a menu (drop-down list) of countries,\nusing list of current countries.  It would be more work to create it, but\nmight reduce ambiguities and unparsable responses.\n\nWhat I'd like to have is to pre-fill / select default answer based on GeoIP.\nEven better would be to be able to show current position on Google Map, like\ncontributors and users map on Ohloh... but that I think is simply not\npossible with Survs.com, the site to be used for this survey (and I guess\nneither with any other survey site).  One can dream.\n\nPel Survey 2010 also included (from what I remember, and from provided data\nand analysis of survey) also country of origin / country of birth, to\nmeasure mobility.  I wonder if it would make sense to have the same for Git\nUser's Survey 2010...  Note that it would be harder to come up with the list\nof countries for such question, because the country might no longer exists.\nTherefore the list (if present) should be based on all countries that exist\nor existed since 100 years ago (or so).\n\n\n=== 02. How old are you (in years)? ===\n(free-form single line)\n\nNOTES:\n^^^^^^\nInstead of unconstrained free-form response it might be better to have\nsingle choice (or menu) of age ranges.  What do you think?  Of course with\nranges there is question what ranges to use (how to quantize age); goo\nsolution would be to chose ranges corresponding somewhat to the levels of\neducation.\n\n\n== Getting started with Git ==\n\n=== 03. Have you found Git easy to learn? ===\n(single choice)\n\n* Very easy\n* Easy\n* Reasonably easy\n* Hard\n* Very hard\n\n=== 04. Have you found Git easy to use? ===\n(single choice)\n\n* Very easy\n* Easy\n* Reasonably easy\n* Hard\n* Very hard\n\nNOTES:\n^^^^^^ \nThose two questions, considered alone, doesn't tell us much.  If one use\ngit, then usually one does not think it is too hard to use (unless forced to\nuse git by external circumstances, like project he/she works on using git).\nOn the other hand those two questions together give us some mesaure of git\nlearning curve, telling us if people consider git easy to use but hard to\nlearn, or vice versa ;-)\n\nI think it might be also good to have to calculate correlations, e.g. if\npeople who find git hard to use make use of its advanced features.\n\nThe question is: should they stay, or should they go?\n\n\n=== 05. Which Git version(s) are you using? ===\n(multiple choice, with other)\n\n + pre 1.3\n + 1.3.x\n + 1.4.x\n + 1.5.x\n + 1.6.x\n + 1.7.x\n\n + minor (maintenance) release 1.x.y.z\n + 'master' branch of official git repository\n + 'next' branch of official git repository\n + 'pu' branch of official git repository\n + version from msysGit / Git for Windows fork repository\n + git-bigfiles fork\n + JGit implementation (e.g. via Eclipse plugin, EGit)\n\n + other, please specify\n\nNOTES:\n^^^^^^\nA few of possible answers are new in this version of survey, namely 'pu',\nmsysGit, git-bigfiles, JGit, and of course 1.7.x.\n\nThis question is here to stay.\n\n\n=== 06. Rate your own proficiency with Git: ===\n(single choice)\n\n * 1. novice\n * 2. casual, needs advice\n * 3. everyday use\n * 4. can offer advice\n * 5. know it very well\n\nNOTES:\n^^^^^^\nThis question tell us penetration of announcements of Git User's Survey 2010;\ndid we get to all, or only to git gurus?  It is also useful for correlating\nwith other responses, for example to know which features are used by\nnovices, and which by gurus.\n\n\n== How you use Git ==\n\n=== 07. I use Git for (check all that apply): ===\n(multiple choice, with other)\n\nNote that above choices are neither orthogonal nor exclusive.  One\nmight want to check multiple answers even for a single repository.\n\nNOTES:\n^^^^^^\nAnswers to this question probe different direction.\nThis list is interspersed with comments about specific\n(sub)sections.\n\n + work projects\n + unpaid projects\n\nNotes:\n^^^^^^\nThose two are about using git at work vs using git on your own free time.\nThere are of course shades of gray, like using git for work project\nunofficially (e.g.using git-svn as \"fat\" client for company's Subversion\nrepository), or employer allowing to work on non-work OSS project during\nworking hours.  But I'm not sure if they are worth adding.\n\n + proprietary projects\n + OSS development (also public domain, and published & unlicensed)\n + private (unpublished)\n\nNotes:\n^^^^^^\nThose three are about licensing: proprietary / free (open) / unlicensed.\nBy 'OSS development' I mean here also free licenses for documentation and\ndocuments, like GFDL or Creative Commons licenses.\n\n + code (programming)\n + personal data\n + documents (data)\n + static website\n + web app\n + large (> 1MB) binary files\n + often changing binary files\n\nNotes:\n^^^^^^\nThis is about what kind of data do you store in git.  I am a bit unsure\nwhether it is worth separating 'web app'; it is 'code'.\n\nNew in this edition of survey is 'large binary data' and 'often changing\nbinary files'... but should 'large' cutoff be 1MB, or 10MB, or 50MB, or\n100MB?\n\nI'm not sure about having 'personal data'...\n\n + sharing data or sync\n + managing configuration files\n + backup\n + backend for wiki, blog, or other web app\n + frontend to other SCM (e.g. git-svn)\n\nNotes:\n^^^^^^\nThis is about (ab)using git for other things than straighforward source\ncontrol management.  List of possible answers specified here should cover\nmost commonly encountered usages: shdoul we add anything else here?\n\n + other (please specify)\n\n\n=== 08. How do/did you obtain Git (install and/or upgrade)? ===\n(multiple choice, with other)\n\nNote that this question is multiple choices question because one can\ninstall Git in different ways on different machines or on different\noperating systems.\n\n + binary package\n + source package or script\n + source tarball\n + pull from (main) repository\n + preinstalled / sysadmin job\n\n + other - please specify\n\nDescription:\n~~~~~~~~~~~~\nExplanation: \"binary package\" covers pre-compiled binary (e.g.  from\nrpm or deb binary packages); \"source package\" covers things like\ndeb-src and SRPMS / *.src.rpm; \"source script\" is meant to cover\ninstallation in source-based distributions, like 'emerge' in Gentoo.\n\nAutomatic update (apt, yum, etc.) in most cases means binary package\ninstall; unless one uses source-based distribution like Gentoo, CRUX,\nor SourceMage, where automatic update means using source package (or\nsource script).\n\nThe option named \"preinstalled / sysadmin job\" means that either you\ndidn't need to install git because it was preinstalled (and you didn't\nupgrade); or that you have to ask system administrator to have git\ninstalled or upgraded.\n\nNote that this question is multiple choices question because one can\ninstall Git in different ways on different machines or on different\noperating systems.\n\nNOTES:\n^^^^^^\nWhat I didn't take into account in above explanation is operating\nsystems with packaging systems different that the one used by various\nLinux distributions.\n\nIn short: if to have git installed you compile it, you use source\npackage or source tarball.  If the installation onvolves anything more\nthan 'make install' (or manual copying), then it is most probably\nsource package or script.\n\nThis for example means that \"msysGit\" installer is source package, and\n\"Git for Windows\" is binary package, if I understand it correctly.\n\n\n=== 09. On which operating system(s) do you use Git? ===\n(multiple choice, with other)\n\n + Linux (includes MeeGo and Moblin)\n + MacOS X (Darwin)\n + MS Windows/msysGit (MINGW)\n + MS Windows/Cygwin\n + FreeBSD, OpenBSD, NetBSD, etc.\n + other Unix\n\n + iPhone OS\n + Android\n + WebOS\n\n + Other, please specify\n\nNOTES:\n^^^^^^\nThe iPhone OS, Androind and WebOS answers are new this year.\nOpenSolaris died, so I removed it.  I wonder if it is worth it to\ndifferentiate between MS Windows/msysGit and MS Windows/Cygwin, or if\nwe should just have one, single 'MS Windows' choice.\n\n\n=== 10. What do you use to edit contents under version control with Git? ===\n        What kind of editor, IDE or RAD you use working with Git?\n(multiple choice, with other)\n\n + simple text editor\n + programmers editor\n + IDE or RAD\n + WYSIWYG tool\n\n + other kind\n\nDescription:\n~~~~~~~~~~~~\n* \"simple text editor\" option includes editors such as pico, nano,\n  joe, Notepad,\n\n* \"programmets editor\" option includes editors such as Emacs/XEmacs,\n  Vim, TextMate, SciTE (syntax highlighting, autoindentation,\n  integration with other programmers tools, etc.)\n\n* \"IDE (Integrated Development Environment) and RAD (Rapid Application\n  Development)\" option includes tools such as Eclipse, NetBeans IDE,\n  IntelliJ IDE, MS Visual Studio, KDevelop, Anjuta, Xcode,\n  Code::Blocks but also tools such as Quanta+, BlueFish or Screem (for\n  editing HTML, CSS, PHP etc.), and Kile or LEd for LaTeX.\n\n* \"WYSIWYG tools\" option includes word processors such as MS Office or\n  OpenOffice.org, but also tools such as Adobe Acrobat (for PDF) or\n  GIMP (for images), or WYSIWYG DTP tools such as QuarkXPress,\n  PageMaker or Scribus, or WYSIWYG HTML editors such as FrontPage,\n  Dreamweaver or KompoZer.\n\nNOTES:\n^^^^^^\nIs this question useful, or should it be removed from survey?\n\n\n=== 11. What Git interfaces and frontends do you use? ===\n(multiple choice, with other)\n\n + Cogito (DEPRECATED)\n + Easy Git\n + Pyrite\n + I don't know, I only use (graphical) tools\n\n + pg aka Patchy Git (DEPRECATED)\n + StGIT\n + Guilt\n + TopGit\n\n + other (please specify)\n\nNOTES:\n^^^^^^\nThis version is going back to split from 2008 survey, rather than\nhaving everything put together like in 2009 one.  There are, of\ncourse, problems with both choices.  \n\nThe problem with split part is that people can have troubls with\ndistinguising between interfaces, implementations, frontends and tools\n(although \"I don't know ...\"  answer should, I think, help here).  The\nproblem with having it everything together is that the list of\npossible answers gets long and a bit unwieldy.\n\nBTW are there any implementations and frontends that should be added\nto the list above?\n\n\n=== 12. What kind of Git tools do you use? ===\n(multiple choice, with other)\n\nIf a tool is both history viewer, and commit tool, please choose the\noption that corresponds to how do you use this tool.\n\n + editor/IDE VC integration (e.g. EGit, TextMate bundle, magit)\n + filemanager / shell extension (e.g. git-cheetah, TortoiseGit)\n + graphical history viewer/browser (e.g. gitk)\n + graphical commit tool (e.g. git-gui)\n + graphical diff and/or merge tool (e.g. Kompare, Meld)\n + graphical blame or pickaxe tool\n + git-instaweb, or self-hosted web interface\n + tool to manage git repositories (e.g. Gitosis, Gitolite)\n\n + my own scripts (for daily use)\n + my own scripts (for special tasks)\n\nNOTES:\n^^^^^^\nAs the number of tools increases (see InterfacesFrontendsAndTools page\non git wiki), having them listed all there gets a bit unwieldy.  On\nthe other hand it was a good way to find new tools that were not yet\nincluded on IFaT page.  What do you think: should it be about tools,\nor only about kind of tools used with git?\n\nWhat do you think about this list?  IS there something that should not\nbe here?  Or perhaps there is something that should be added to this\nlist?\n\n\n=== 13. Which git hosting site(s) do you use for your project(s)? ===\n        Please check only hosting sites where you publish/push to (with git)\n(multiple choice, with other)\n\n + [http://repo.or.cz repo.or.cz]\n + [http://github.com GitHub]\n + [http://gitorious.org Gitorious]\n + [http://www.indefero.net InDefero]\n\nNotes:\n^^^^^^\nThose are generic git hosting sites, each of them showcasing their own\ntool, all except GitHub open source (it is Girocco for repo.or.cz; for\nthe rest the tool is named the same as the git hosting site).\n\n + [http://savannah.gnu.org Savannah]\n + [http://sourceforge.net SourceForge]\n\nNotes:\n^^^^^^\nGeneric software hosting sites, with git support.  Did I miss\nsomething, should I include yet another site?\n\n + [http://www.assembla.com Assembla]\n + [http://codebasehq.com Codebase]\n + [http://unfuddle.com Unfuddle]\n - [http://codesion.com Codesion]\n - [http://gitfarm.appspot.com GitFarm]\n - [http://www.projectlocker.com ProjectLocker]\n - [http://thechaw.com The Chaw]\n - [http://unfuddle.com Unfuddle]\n\nNotes:\n^^^^^^\nThose are commercial and/or less known git hosting sites.  I am not\nsure which ones of those marked with '-' to include, and whether to\ninclude other sites from GitHosting page on git wiki.  What do you\nthink?\n\n + [http://git.kernel.org kernel.org]\n + [http://www.freedesktop.org/wiki/ freedesktop.org]\n\nNotes:\n^^^^^^\nThose are 'git hosting site for related projects', but are special in\nsome sense.  Should I leave them there, or remove from this list?\n\n + [http://alioth.debian.org Alioth] (Debian)\n + [http://hosted.fedoraproject.org Fedora Hosted]\n\nNotes:\n^^^^^^\nThose are distribution-specific.  Are there any sites that I missed?\nLaunchpad from Ubuntu does not count, as it is Bazaar hosting site,\nnot Git hosting site.\n\n +  git hosting site for related projects\n +  generic site without git support\n +  self hosted\n\nNotes:\n^^^^^^\nAre ther other kinds / typse of sites one can host project using git\non?  What are they?\n\n +  Other (please specify)\n\nNOTES:\n^^^^^^\nI think this question is here to stay.\n\n\n=== 14. How do you fetch/get changes from upstream repositories? ===\n(multiple choice, with other)\n\n + git protocol        (e.g. git://git.example.com/repo.git)\n + ssh                 (e.g. ssh+git://git.example.com/repo.git,\n                             git.example.com:/srv/scm/repo.git)\n + http                (e.g. http://git.example.com/repo.git)\n + rsync (DEPRECATED)  (e.g. rsync://git.example.com/repo.git)\n + filesystem          (e.g. /path/to/repo.git, file:///path/to/repo.git)\n + via git-bundle\n + foreign SCM (e.g. git-svn)\n\n + Other, please specify\n\nDescription:\n~~~~~~~~~~~~\nThis question asks about how do you get changes (updates) from\nprojects you follow into your local repository. It is not about how do\nyou get latest version of Git.\n\nFetching (or rather cloning) via bundle could mean that project\npublishes ready for download bundles to reduce traffic and load on\nserver (HTTP download [of bundle] can be resumed, git-clone currently\ncannot; one can also distribute bundle using P2P).\n\nNOTES:\n^^^^^^\nWhat is new are examples of URLs / URIs for each protocol.\n\nDid I miss anything?  Is this question interesting, and should it\nstay, or should it be removed?\n\n\n=== 15. How do you publish/propagate your changes? ===\n(multiple choice, with other)\n\n + push\n + pull request (+ any form of announcement / notification)\n + format-patch + email\n + format-patch + other (e.g. reviewboard, issue tracker or forum)\n + git bundle\n\n + git-svn (to Subversion repository)\n + git-p4 (to Perforce repository)\n + foreign SCM interface (other than mentioned above)\n\n + other - please specify\n\nDescription:\n~~~~~~~~~~~~\nPublishing via bundle could mean sending bundle via email, or posting\nit on review board (or forum).\n\nInstead of git-format-patch there can be utilized other way of\ngenerating patch (e.g. git-show, git-diff, 'patch' view from gitweb,\netc.)\n\nNOTES:\n^^^^^^\nShould it stay, or should it be removed?  I guess it can be\ninteresting for git hosting sites...  Should we have separate answrs\nfor different kinds of push (ssh, \"dumb\" HTTP(S) with WebDAV, \"smart\"\nHTTP - if it is possible, git:// protocol with push enabled)?\n\n\n=== 16. Which of the following features do you use? ===\n(multiple choice, with other)\n\n + \"smart\" HTTP protocol\n + git bundle (off-line transport)\n + eol conversion (crlf)\n + gitattributes\n + custom diff/merge driver\n + submodules (subprojects)\n + subtree merge (optionally git-subtree)\n + partial (sparse) checkout, or assume-unchanged bit\n + separate worktree / core.worktree\n + multiple worktrees (git-new-worktree)\n + alternates mechanism (sharing object database)\n + stash (optionally \"git stash --keep-index\")\n + shallow clone (e.g. \"git clone --depth=<n>\")\n + detaching HEAD (e.g. \"git checkout HEAD^0\")\n + interactive rebase (small scale history editing)\n + interactive commit / per-hunk comitting / partial commit\n + commit message templates\n + git-filter-branch or equivalent (large history rewriting)\n + bisect (optionally \"git bisect run <script>\")\n + committing with dirty tree (keeping some changes uncommitted)\n + non-default hooks (from contrib/hooks/ or other)\n + shell completion of commands\n + git-aware shell prompt\n + git aliases, shell aliases for git, or own git scripts\n + one-way interaction with other SCMs (from SCM to git)\n + two-way interaction with other SCMs (from SCM to git, from git to SCM)\n + git-cvsserver\n + git notes\n\n + Other, please specify\n\nNOTES:\n^^^^^^\nThe problem is come up not with exhaustive list of features: there are\ntoo many of them to list.  The problem is coming up with list of\nimportant and used enough often features.\n\nSo: what features should be included in this list?  What features\nshould be removed from above list of answers?\n\n\n=== 17. Which of the following features would you like to see implemented in git? ===\n(multiple choice)\n\n + better support for big files (large media)\n + resumable clone/fetch (and other remote operations)\n + GitTorrent Protocol, or git-mirror\n + lazy clone / on-demand fetching of object\n + support for tracking empty directories\n + environmental variables in config, \n   and expanding ~ and ~user in paths in config\n + better undo/abort/continue, and for more commands\n + '-n' like option for each command, which describes what would happen\n + side-by-side diffs and/or color-words diff in gitweb\n + admin and/or write features in gitweb\n + graphical history view in gitweb\n + GUI for rebase in git-gui\n + GUI for creating repository in git-gui\n + filename encoding (in repository vs in filesystem)\n + git push --create\n + localization of command-line messages\n + wholesame directory rename detection\n + graphical merge tool integrated with git-gui\n + union checkouts (some files from one branch, some from other)\n + advisory locking / \"this file is being edited\"\n + \"commands issued\" (or \"command equivalents\") in git-gui / gitk\n + warn before/when rewriting published history\n + built-in gitjour/bananajour support\n + syntax highlighting in git-gui\n\n + other (describe below)\n\nNOTES:\n^^^^^^\nThis is new question, a multiple choice companion to a essay free-form\nquestion below.  Included are a few example features (some from\npartial analysis of \"19. What features would you like implemented in\nGit?\" question in 2009 survey.\n\nWhat features should be mentioned besides those above?  What criteria\nshould we have for including features in this list?\n\n=== 18. Describe what features would you like to have in Git, if it is\n        not on the list above? ===\n(free form, essay length)\n\n\n== What you think of Git ==\n\n=== 19. Overall, how happy are you with Git? ===\n(single choice)\n\n * unhappy\n * not so happy\n * happy\n * very happy\n * completely ecstatic\n\nNOTES:\n^^^^^^\nI'm not sure if this question is at all useful.\n\nThere is also problem, that the current wording is considered biased\nby some, but on the other hand changing wording of answers would make\nit impossible to compare it to answers from previous surveys...\n\n\n=== 20. In your opinion, which areas in Git need improvement? ===\n        Please state your preference.\n(matrix)\n\n   Columns: don't need / a little / some / much\n + user-interface\n + documentation\n + performance\n + more features\n + tools (e.g. GUI)\n + localization (translation)\n\nNOTES:\n^^^^^^\nAre there any general areas that are missing from this list?\nWhat are they?\n\n\n== Changes in Git (since year ago, or since you started using it) ==\n\n=== 21. Did you participate in previous Git User's Surveys? ===\n(multiple choice)\n\n + in 2006\n + in 2007\n + in 2008\n + in 2009\n + none of the above\n\nNOTES:\n^^^^^^ \nThis might be quite useful comparing with previous surveys.  The\nanswer 'none of the above' is new in this survey (as is 'in 2009',\nof course).\n\n\n=== 22. How do you compare the current version with the version from one year ago? ===\n(single choice)\n\n * better\n * no changes\n * worse\n\n * cannot say\n\nNOTES:\n^^^^^^\nThis question was mainly excuse for providing list of main changes\nfrom the year ago.  I think that this question should be removed, as\nit doesn't bring any important information.\n\n\n== Documentation. Getting help. ==\n\n=== 23. How useful have you found the following forms of Git documentation? ===\n(matrix)\n\n  Columns: never used / not useful / somewhat / useful\n + Git Wiki\n + on-line help\n + help distributed with git\n\n\nDescription:\n~~~~~~~~~~~~\n* Git Wiki was to be found at http://git.wiki.kernel.org\n* on-line help includes, among others, Git Homepage (http://git-scm.com),\n  \"Git Community Book\" (http://book.git-scm.com), \"Pro Git\" book\n  (http://progit.org) and Git Reference site (http://gitref.org)\n* help distributed with git include manpages, manual, tutorials, HOWTO,\n  release notes, technical documentation, contrib/examples/\n\nNOTES:\n^^^^^^\nShould we split those answers further, e.g. separating on-line\ntutorials and guides, from on-line tips etc.?\n\n\n=== 24. Have you tried to get help regarding Git from other people? ===\n(single choice)\n\n * Yes\n * No\n\n=== 25. If yes, did you get these problems resolved quickly and to your liking? ===\n(single choice)\n\n * Yes\n * No\n * Somewhat\n\nNOTES:\n^^^^^^\nThose two questions are not very useful.  I think that they should be\nremoved from 2010 survey.\n\n\n=== 26. What channel(s) do you use to request help about git? ===\n(multiple choice, with other)\n\n + git mailing list (git@vger.kernel.org)\n + \"Git for Human Beings\" Google Group\n + msysGit mailing list / Google Group\n + IRC (#git)\n + IRC (other git/SCM related, e.g. #github)\n + request in blog post or on wiki\n + asking git guru/colleague\n + project mailing list, or IRC, or forum\n + Twitter or other microblogging platform\n + instant messaging (IM) like XMPP/Jabber\n + StackOverflow or other StackExchange site\n\n + other (please specify)\n\nNOTES:\n^^^^^^\nAre there any main channels of requesting help that I have missed in\nthe above list of answers?  What are they, and why do you think they\nare important enought to warrant inclusion in above list?\n\n\n=== 27. Which communication channel(s) do you use? ===\n        Do you read the mailing list, or watch IRC channel?\n(multiple choice)\n\n + git@vger.kernel.org (main)\n + Git for Human Beings (Google Group)\n + msysGit\n + #git IRC channel\n + #git-devel IRC channel\n + #github or #gitorious IRC channel\n + #revctrl IRC channel\n\nNOTES:\n^^^^^^\nAre there any communication channels that I have missed?  For example\nis there a separate channel that JGit/EGit developers use?\n\n\n== About this survey. Open forum. ==\n\n=== 28. How did you hear about this Git User's Survey? ===\n(single choice, with other)\n\n * git mailing list\n * git-related mailing list (e.g. msysGit)\n * mailing list or forum of some project\n * #git IRC channel topic\n * announcement on IRC channel\n * git homepage\n * git wiki\n * git hosting site (or blog related to such site)\n * software-related web site\n * news or social news site (e.g. Digg, Reddit)\n * blog (or blog planet)\n * other kind of web site\n * Twitter or other microblogging platform\n\n * other - please specify\n\nNOTES:\n^^^^^^\nThis list would of course be updated to reflect the list of (planned)\nannouncement channels.\n\nThere of course will be announcement on Git Mailing List, and perhaps\nalso on msysGit list / Google Group, and on Git For Human Beings\nGoogle Group (if it exists).  I'll announce it on #git, and ask op to\nput short announcement in channel description, and I can announce it\non other IRC channels.  I would add announcement to main page of Git\nWiki, and as Git Homepage administrator to put announcement about Git\nUser's Survey.\n\nI usually tried to contact administrators of git hosting sites,\nincluding git.kernel.org, repo.or.cz, GitHub, Gitorious, Assembla,\nCodebase and Unfuddle, asking them to put announcement about \nGit User's Survey either somewhere on the site, or in their blog \n(if there is any).  What git hosting sites it is worth to ask?\n\nSidenote: I am thinking about contacting different git hosting sites\n_before_ staring survey, asking them (them = administrators) about\nwhat questions would they like to see.  Do you think thet it is good\nidea?\n\nShould I try to post announcement on mailing list for projects that\nuse git?  There are entirely too many such projects nowadays, and such\nannouncement can be considered spamming by some...\n\nI would like to have announcement of Git User's Survey 2010 at\nLWN.net, but this would need to be send at least two weeks in advance,\nif I remember correctly.  Is it worth it?  What other news site should\nI (or you) send announcement to?\n\nIf you can Digg / Reddit announcment on some site, please do.  I can\nannounce Git User's Survey 2-1- at Twitter, Identi.ca and Plurk, but I\ndon't have wide area of followers.  So please RT.\n\nShould we contact some bloggers (besides asking Junio to put\nannouncement on his blog) to post an anouncement?  Which bloggers\nwould respond positively (perhaps Linus...)?\n\n-- \nJakub Narebski\nPoland\n"},{"id":"144767","messageId":"AANLkTilD8N6rnj9e3KzRB7_q3J0I4cJGx5EduX_UJScC@mail.gmail.com","threadId":"24279","inReplyTo":"201007032158.57700.jnareb@gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2010-07-04T00:21:16Z","receivedAt":"2010-07-04T00:21:16Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n\nThis survey is good stuff. Some minor comments below.\n\n> I guess it is time for annual (so far) Git User's Survey.  Should\n> there be one?  When should it start, and how long should it last?\n>\n> here is how it was for previous surveys:\n>  * 2009 was open from 15 July   to 15 September 2009 (for 2 months)\n>  * 2008 was open from 31 August to 14 October 2008 (for 1.5 months)\n>  * 2007 was open from 20 August to 10 September 2007 (for 20 days)\n>        (officially: results are up until 28 September 2007)\n>  * 2006 was open from 23 July   to 6-12 September 2006\n>   (for a bit less than 2 months)\n>\n> With more that 3000 responses in 2008 and 2009 survey, analysing\n> free-form data was hard.  That is why in this proposal there is only\n> single one free-form response (about missing features).\n>\n> What questions (and with what proposed answers) shound there be in\n> this year survey?  Below there is the content of the proposed survey:\n>\n>\n> = Git User's Survey 2010 (proposal) =\n>\n> == About you ==\n>\n> NOTES:\n> ^^^^^^\n> This section gives us a bit of demographical information about survey\n> responders.  Is it useful?  Should we leave it in survey, or remove it?\n>\n> Should we for example include 'gender' as one of questions?  Perl Survey\n> 2010 did.\n>\n>\n> === 01. What country do you live in? ===\n>        (Country of residence)\n> (free-form single line)\n>\n> NOTES:\n> ^^^^^^\n> Perhaps a better solution would be a menu (drop-down list) of countries,\n> using list of current countries.  It would be more work to create it, but\n> might reduce ambiguities and unparsable responses.\n>\n> What I'd like to have is to pre-fill / select default answer based on GeoIP.\n> Even better would be to be able to show current position on Google Map, like\n> contributors and users map on Ohloh... but that I think is simply not\n> possible with Survs.com, the site to be used for this survey (and I guess\n> neither with any other survey site).  One can dream.\n>\n> Pel Survey 2010 also included (from what I remember, and from provided data\n> and analysis of survey) also country of origin / country of birth, to\n> measure mobility.  I wonder if it would make sense to have the same for Git\n> User's Survey 2010...  Note that it would be harder to come up with the list\n> of countries for such question, because the country might no longer exists.\n> Therefore the list (if present) should be based on all countries that exist\n> or existed since 100 years ago (or so).\n>\n>\n> === 02. How old are you (in years)? ===\n> (free-form single line)\n>\n> NOTES:\n> ^^^^^^\n> Instead of unconstrained free-form response it might be better to have\n> single choice (or menu) of age ranges.  What do you think?  Of course with\n> ranges there is question what ranges to use (how to quantize age); goo\n> solution would be to chose ranges corresponding somewhat to the levels of\n> education.\n>\n>\n> == Getting started with Git ==\n>\n> === 03. Have you found Git easy to learn? ===\n> (single choice)\n>\n> * Very easy\n> * Easy\n> * Reasonably easy\n> * Hard\n> * Very hard\n>\n> === 04. Have you found Git easy to use? ===\n> (single choice)\n>\n> * Very easy\n> * Easy\n> * Reasonably easy\n> * Hard\n> * Very hard\n>\n> NOTES:\n> ^^^^^^\n> Those two questions, considered alone, doesn't tell us much.  If one use\n> git, then usually one does not think it is too hard to use (unless forced to\n> use git by external circumstances, like project he/she works on using git).\n> On the other hand those two questions together give us some mesaure of git\n> learning curve, telling us if people consider git easy to use but hard to\n> learn, or vice versa ;-)\n>\n> I think it might be also good to have to calculate correlations, e.g. if\n> people who find git hard to use make use of its advanced features.\n>\n> The question is: should they stay, or should they go?\n\nThey should probably stay. But they don't really ask the right\nquestion IMO. Which is not whether users think it's difficult to\nlearn, but whether it's unreasonably difficult for the problem they're\nsolving.\n\nI.e. jet aircraft are hard to operate, but they also do neat\nstuff. How hard is Git to learn for the problem it's solving?\n\n> === 05. Which Git version(s) are you using? ===\n> (multiple choice, with other)\n>\n>  + pre 1.3\n>  + 1.3.x\n>  + 1.4.x\n>  + 1.5.x\n>  + 1.6.x\n>  + 1.7.x\n>\n>  + minor (maintenance) release 1.x.y.z\n>  + 'master' branch of official git repository\n>  + 'next' branch of official git repository\n>  + 'pu' branch of official git repository\n>  + version from msysGit / Git for Windows fork repository\n>  + git-bigfiles fork\n>  + JGit implementation (e.g. via Eclipse plugin, EGit)\n>\n>  + other, please specify\n>\n> NOTES:\n> ^^^^^^\n> A few of possible answers are new in this version of survey, namely 'pu',\n> msysGit, git-bigfiles, JGit, and of course 1.7.x.\n>\n> This question is here to stay.\n>\n>\n> === 06. Rate your own proficiency with Git: ===\n> (single choice)\n>\n>  * 1. novice\n>  * 2. casual, needs advice\n>  * 3. everyday use\n>  * 4. can offer advice\n>  * 5. know it very well\n>\n> NOTES:\n> ^^^^^^\n> This question tell us penetration of announcements of Git User's Survey 2010;\n> did we get to all, or only to git gurus?  It is also useful for correlating\n> with other responses, for example to know which features are used by\n> novices, and which by gurus.\n>\n>\n> == How you use Git ==\n>\n> === 07. I use Git for (check all that apply): ===\n> (multiple choice, with other)\n>\n> Note that above choices are neither orthogonal nor exclusive.  One\n> might want to check multiple answers even for a single repository.\n>\n> NOTES:\n> ^^^^^^\n> Answers to this question probe different direction.\n> This list is interspersed with comments about specific\n> (sub)sections.\n>\n>  + work projects\n>  + unpaid projects\n>\n> Notes:\n> ^^^^^^\n> Those two are about using git at work vs using git on your own free time.\n> There are of course shades of gray, like using git for work project\n> unofficially (e.g.using git-svn as \"fat\" client for company's Subversion\n> repository), or employer allowing to work on non-work OSS project during\n> working hours.  But I'm not sure if they are worth adding.\n>\n>  + proprietary projects\n>  + OSS development (also public domain, and published & unlicensed)\n>  + private (unpublished)\n>\n> Notes:\n> ^^^^^^\n> Those three are about licensing: proprietary / free (open) / unlicensed.\n> By 'OSS development' I mean here also free licenses for documentation and\n> documents, like GFDL or Creative Commons licenses.\n>\n>  + code (programming)\n>  + personal data\n>  + documents (data)\n>  + static website\n>  + web app\n>  + large (> 1MB) binary files\n>  + often changing binary files\n>\n> Notes:\n> ^^^^^^\n> This is about what kind of data do you store in git.  I am a bit unsure\n> whether it is worth separating 'web app'; it is 'code'.\n>\n> New in this edition of survey is 'large binary data' and 'often changing\n> binary files'... but should 'large' cutoff be 1MB, or 10MB, or 50MB, or\n> 100MB?\n>\n> I'm not sure about having 'personal data'...\n>\n>  + sharing data or sync\n>  + managing configuration files\n>  + backup\n>  + backend for wiki, blog, or other web app\n>  + frontend to other SCM (e.g. git-svn)\n>\n> Notes:\n> ^^^^^^\n> This is about (ab)using git for other things than straighforward source\n> control management.  List of possible answers specified here should cover\n> most commonly encountered usages: shdoul we add anything else here?\n>\n>  + other (please specify)\n>\n>\n> === 08. How do/did you obtain Git (install and/or upgrade)? ===\n> (multiple choice, with other)\n>\n> Note that this question is multiple choices question because one can\n> install Git in different ways on different machines or on different\n> operating systems.\n>\n>  + binary package\n>  + source package or script\n>  + source tarball\n>  + pull from (main) repository\n>  + preinstalled / sysadmin job\n>\n>  + other - please specify\n>\n> Description:\n> ~~~~~~~~~~~~\n> Explanation: \"binary package\" covers pre-compiled binary (e.g.  from\n> rpm or deb binary packages); \"source package\" covers things like\n> deb-src and SRPMS / *.src.rpm; \"source script\" is meant to cover\n> installation in source-based distributions, like 'emerge' in Gentoo.\n>\n> Automatic update (apt, yum, etc.) in most cases means binary package\n> install; unless one uses source-based distribution like Gentoo, CRUX,\n> or SourceMage, where automatic update means using source package (or\n> source script).\n>\n> The option named \"preinstalled / sysadmin job\" means that either you\n> didn't need to install git because it was preinstalled (and you didn't\n> upgrade); or that you have to ask system administrator to have git\n> installed or upgraded.\n>\n> Note that this question is multiple choices question because one can\n> install Git in different ways on different machines or on different\n> operating systems.\n>\n> NOTES:\n> ^^^^^^\n> What I didn't take into account in above explanation is operating\n> systems with packaging systems different that the one used by various\n> Linux distributions.\n>\n> In short: if to have git installed you compile it, you use source\n> package or source tarball.  If the installation onvolves anything more\n> than 'make install' (or manual copying), then it is most probably\n> source package or script.\n>\n> This for example means that \"msysGit\" installer is source package, and\n> \"Git for Windows\" is binary package, if I understand it correctly.\n>\n>\n> === 09. On which operating system(s) do you use Git? ===\n> (multiple choice, with other)\n>\n>  + Linux (includes MeeGo and Moblin)\n>  + MacOS X (Darwin)\n>  + MS Windows/msysGit (MINGW)\n>  + MS Windows/Cygwin\n>  + FreeBSD, OpenBSD, NetBSD, etc.\n>  + other Unix\n>\n>  + iPhone OS\n>  + Android\n>  + WebOS\n>\n>  + Other, please specify\n>\n> NOTES:\n> ^^^^^^\n> The iPhone OS, Androind and WebOS answers are new this year.\n> OpenSolaris died, so I removed it.  I wonder if it is worth it to\n> differentiate between MS Windows/msysGit and MS Windows/Cygwin, or if\n> we should just have one, single 'MS Windows' choice.\n\nIt's definitely worth differentiating those two.\n\n> === 10. What do you use to edit contents under version control with Git? ===\n>        What kind of editor, IDE or RAD you use working with Git?\n> (multiple choice, with other)\n>\n>  + simple text editor\n>  + programmers editor\n>  + IDE or RAD\n>  + WYSIWYG tool\n>\n>  + other kind\n>\n> Description:\n> ~~~~~~~~~~~~\n> * \"simple text editor\" option includes editors such as pico, nano,\n>  joe, Notepad,\n>\n> * \"programmets editor\" option includes editors such as Emacs/XEmacs,\n>  Vim, TextMate, SciTE (syntax highlighting, autoindentation,\n>  integration with other programmers tools, etc.)\n>\n> * \"IDE (Integrated Development Environment) and RAD (Rapid Application\n>  Development)\" option includes tools such as Eclipse, NetBeans IDE,\n>  IntelliJ IDE, MS Visual Studio, KDevelop, Anjuta, Xcode,\n>  Code::Blocks but also tools such as Quanta+, BlueFish or Screem (for\n>  editing HTML, CSS, PHP etc.), and Kile or LEd for LaTeX.\n>\n> * \"WYSIWYG tools\" option includes word processors such as MS Office or\n>  OpenOffice.org, but also tools such as Adobe Acrobat (for PDF) or\n>  GIMP (for images), or WYSIWYG DTP tools such as QuarkXPress,\n>  PageMaker or Scribus, or WYSIWYG HTML editors such as FrontPage,\n>  Dreamweaver or KompoZer.\n>\n> NOTES:\n> ^^^^^^\n> Is this question useful, or should it be removed from survey?\n>\n>\n> === 11. What Git interfaces and frontends do you use? ===\n> (multiple choice, with other)\n>\n>  + Cogito (DEPRECATED)\n>  + Easy Git\n>  + Pyrite\n>  + I don't know, I only use (graphical) tools\n>\n>  + pg aka Patchy Git (DEPRECATED)\n>  + StGIT\n>  + Guilt\n>  + TopGit\n>\n>  + other (please specify)\n>\n> NOTES:\n> ^^^^^^\n> This version is going back to split from 2008 survey, rather than\n> having everything put together like in 2009 one.  There are, of\n> course, problems with both choices.\n>\n> The problem with split part is that people can have troubls with\n> distinguising between interfaces, implementations, frontends and tools\n> (although \"I don't know ...\"  answer should, I think, help here).  The\n> problem with having it everything together is that the list of\n> possible answers gets long and a bit unwieldy.\n>\n> BTW are there any implementations and frontends that should be added\n> to the list above?\n>\n>\n> === 12. What kind of Git tools do you use? ===\n> (multiple choice, with other)\n>\n> If a tool is both history viewer, and commit tool, please choose the\n> option that corresponds to how do you use this tool.\n>\n>  + editor/IDE VC integration (e.g. EGit, TextMate bundle, magit)\n>  + filemanager / shell extension (e.g. git-cheetah, TortoiseGit)\n>  + graphical history viewer/browser (e.g. gitk)\n>  + graphical commit tool (e.g. git-gui)\n>  + graphical diff and/or merge tool (e.g. Kompare, Meld)\n>  + graphical blame or pickaxe tool\n>  + git-instaweb, or self-hosted web interface\n>  + tool to manage git repositories (e.g. Gitosis, Gitolite)\n>\n>  + my own scripts (for daily use)\n>  + my own scripts (for special tasks)\n>\n> NOTES:\n> ^^^^^^\n> As the number of tools increases (see InterfacesFrontendsAndTools page\n> on git wiki), having them listed all there gets a bit unwieldy.  On\n> the other hand it was a good way to find new tools that were not yet\n> included on IFaT page.  What do you think: should it be about tools,\n> or only about kind of tools used with git?\n>\n> What do you think about this list?  IS there something that should not\n> be here?  Or perhaps there is something that should be added to this\n> list?\n>\n>\n> === 13. Which git hosting site(s) do you use for your project(s)? ===\n>        Please check only hosting sites where you publish/push to (with git)\n> (multiple choice, with other)\n>\n>  + [http://repo.or.cz repo.or.cz]\n>  + [http://github.com GitHub]\n>  + [http://gitorious.org Gitorious]\n>  + [http://www.indefero.net InDefero]\n>\n> Notes:\n> ^^^^^^\n> Those are generic git hosting sites, each of them showcasing their own\n> tool, all except GitHub open source (it is Girocco for repo.or.cz; for\n> the rest the tool is named the same as the git hosting site).\n>\n>  + [http://savannah.gnu.org Savannah]\n>  + [http://sourceforge.net SourceForge]\n>\n> Notes:\n> ^^^^^^\n> Generic software hosting sites, with git support.  Did I miss\n> something, should I include yet another site?\n\nMaybe this should include \"I host my own, e.g. with Gitweb\".\n\n>  + [http://www.assembla.com Assembla]\n>  + [http://codebasehq.com Codebase]\n>  + [http://unfuddle.com Unfuddle]\n>  - [http://codesion.com Codesion]\n>  - [http://gitfarm.appspot.com GitFarm]\n>  - [http://www.projectlocker.com ProjectLocker]\n>  - [http://thechaw.com The Chaw]\n>  - [http://unfuddle.com Unfuddle]\n>\n> Notes:\n> ^^^^^^\n> Those are commercial and/or less known git hosting sites.  I am not\n> sure which ones of those marked with '-' to include, and whether to\n> include other sites from GitHosting page on git wiki.  What do you\n> think?\n>\n>  + [http://git.kernel.org kernel.org]\n>  + [http://www.freedesktop.org/wiki/ freedesktop.org]\n>\n> Notes:\n> ^^^^^^\n> Those are 'git hosting site for related projects', but are special in\n> some sense.  Should I leave them there, or remove from this list?\n>\n>  + [http://alioth.debian.org Alioth] (Debian)\n>  + [http://hosted.fedoraproject.org Fedora Hosted]\n>\n> Notes:\n> ^^^^^^\n> Those are distribution-specific.  Are there any sites that I missed?\n> Launchpad from Ubuntu does not count, as it is Bazaar hosting site,\n> not Git hosting site.\n>\n>  +  git hosting site for related projects\n>  +  generic site without git support\n>  +  self hosted\n>\n> Notes:\n> ^^^^^^\n> Are ther other kinds / typse of sites one can host project using git\n> on?  What are they?\n>\n>  +  Other (please specify)\n>\n> NOTES:\n> ^^^^^^\n> I think this question is here to stay.\n>\n>\n> === 14. How do you fetch/get changes from upstream repositories? ===\n> (multiple choice, with other)\n>\n>  + git protocol        (e.g. git://git.example.com/repo.git)\n>  + ssh                 (e.g. ssh+git://git.example.com/repo.git,\n>                             git.example.com:/srv/scm/repo.git)\n>  + http                (e.g. http://git.example.com/repo.git)\n>  + rsync (DEPRECATED)  (e.g. rsync://git.example.com/repo.git)\n>  + filesystem          (e.g. /path/to/repo.git, file:///path/to/repo.git)\n>  + via git-bundle\n>  + foreign SCM (e.g. git-svn)\n>\n>  + Other, please specify\n\nMaybe git format-patch -> git am. Since it's already this complete.\n\n> Description:\n> ~~~~~~~~~~~~\n> This question asks about how do you get changes (updates) from\n> projects you follow into your local repository. It is not about how do\n> you get latest version of Git.\n>\n> Fetching (or rather cloning) via bundle could mean that project\n> publishes ready for download bundles to reduce traffic and load on\n> server (HTTP download [of bundle] can be resumed, git-clone currently\n> cannot; one can also distribute bundle using P2P).\n>\n> NOTES:\n> ^^^^^^\n> What is new are examples of URLs / URIs for each protocol.\n>\n> Did I miss anything?  Is this question interesting, and should it\n> stay, or should it be removed?\n>\n>\n> === 15. How do you publish/propagate your changes? ===\n> (multiple choice, with other)\n>\n>  + push\n>  + pull request (+ any form of announcement / notification)\n>  + format-patch + email\n>  + format-patch + other (e.g. reviewboard, issue tracker or forum)\n>  + git bundle\n>\n>  + git-svn (to Subversion repository)\n>  + git-p4 (to Perforce repository)\n>  + foreign SCM interface (other than mentioned above)\n>\n>  + other - please specify\n>\n> Description:\n> ~~~~~~~~~~~~\n> Publishing via bundle could mean sending bundle via email, or posting\n> it on review board (or forum).\n>\n> Instead of git-format-patch there can be utilized other way of\n> generating patch (e.g. git-show, git-diff, 'patch' view from gitweb,\n> etc.)\n>\n> NOTES:\n> ^^^^^^\n> Should it stay, or should it be removed?  I guess it can be\n> interesting for git hosting sites...  Should we have separate answrs\n> for different kinds of push (ssh, \"dumb\" HTTP(S) with WebDAV, \"smart\"\n> HTTP - if it is possible, git:// protocol with push enabled)?\n>\n>\n> === 16. Which of the following features do you use? ===\n> (multiple choice, with other)\n>\n>  + \"smart\" HTTP protocol\n>  + git bundle (off-line transport)\n>  + eol conversion (crlf)\n>  + gitattributes\n>  + custom diff/merge driver\n>  + submodules (subprojects)\n>  + subtree merge (optionally git-subtree)\n>  + partial (sparse) checkout, or assume-unchanged bit\n>  + separate worktree / core.worktree\n>  + multiple worktrees (git-new-worktree)\n>  + alternates mechanism (sharing object database)\n>  + stash (optionally \"git stash --keep-index\")\n>  + shallow clone (e.g. \"git clone --depth=<n>\")\n>  + detaching HEAD (e.g. \"git checkout HEAD^0\")\n>  + interactive rebase (small scale history editing)\n>  + interactive commit / per-hunk comitting / partial commit\n>  + commit message templates\n>  + git-filter-branch or equivalent (large history rewriting)\n>  + bisect (optionally \"git bisect run <script>\")\n>  + committing with dirty tree (keeping some changes uncommitted)\n>  + non-default hooks (from contrib/hooks/ or other)\n>  + shell completion of commands\n>  + git-aware shell prompt\n>  + git aliases, shell aliases for git, or own git scripts\n>  + one-way interaction with other SCMs (from SCM to git)\n>  + two-way interaction with other SCMs (from SCM to git, from git to SCM)\n>  + git-cvsserver\n>  + git notes\n>\n>  + Other, please specify\n>\n> NOTES:\n> ^^^^^^\n> The problem is come up not with exhaustive list of features: there are\n> too many of them to list.  The problem is coming up with list of\n> important and used enough often features.\n>\n> So: what features should be included in this list?  What features\n> should be removed from above list of answers?\n>\n>\n> === 17. Which of the following features would you like to see implemented in git? ===\n> (multiple choice)\n>\n>  + better support for big files (large media)\n>  + resumable clone/fetch (and other remote operations)\n>  + GitTorrent Protocol, or git-mirror\n>  + lazy clone / on-demand fetching of object\n>  + support for tracking empty directories\n>  + environmental variables in config,\n>   and expanding ~ and ~user in paths in config\n>  + better undo/abort/continue, and for more commands\n>  + '-n' like option for each command, which describes what would happen\n>  + side-by-side diffs and/or color-words diff in gitweb\n>  + admin and/or write features in gitweb\n>  + graphical history view in gitweb\n>  + GUI for rebase in git-gui\n>  + GUI for creating repository in git-gui\n>  + filename encoding (in repository vs in filesystem)\n>  + git push --create\n>  + localization of command-line messages\n>  + wholesame directory rename detection\n>  + graphical merge tool integrated with git-gui\n>  + union checkouts (some files from one branch, some from other)\n>  + advisory locking / \"this file is being edited\"\n>  + \"commands issued\" (or \"command equivalents\") in git-gui / gitk\n>  + warn before/when rewriting published history\n>  + built-in gitjour/bananajour support\n>  + syntax highlighting in git-gui\n>\n>  + other (describe below)\n>\n> NOTES:\n> ^^^^^^\n> This is new question, a multiple choice companion to a essay free-form\n> question below.  Included are a few example features (some from\n> partial analysis of \"19. What features would you like implemented in\n> Git?\" question in 2009 survey.\n>\n> What features should be mentioned besides those above?  What criteria\n> should we have for including features in this list?\n\nI think \"submodules that Just Work(TM)\" or something similar should be\nincluded. I.e. something the user doesn't have to worry about anymore\nthan they do a normal tree entry. Git's complex submodule support is\nsomething I often hear complaints about.\n\n> === 18. Describe what features would you like to have in Git, if it is\n>        not on the list above? ===\n> (free form, essay length)\n>\n>\n> == What you think of Git ==\n>\n> === 19. Overall, how happy are you with Git? ===\n> (single choice)\n>\n>  * unhappy\n>  * not so happy\n>  * happy\n>  * very happy\n>  * completely ecstatic\n>\n> NOTES:\n> ^^^^^^\n> I'm not sure if this question is at all useful.\n>\n> There is also problem, that the current wording is considered biased\n> by some, but on the other hand changing wording of answers would make\n> it impossible to compare it to answers from previous surveys...\n>\n>\n> === 20. In your opinion, which areas in Git need improvement? ===\n>        Please state your preference.\n> (matrix)\n>\n>   Columns: don't need / a little / some / much\n>  + user-interface\n>  + documentation\n>  + performance\n>  + more features\n>  + tools (e.g. GUI)\n>  + localization (translation)\n>\n> NOTES:\n> ^^^^^^\n> Are there any general areas that are missing from this list?\n> What are they?\n>\n>\n> == Changes in Git (since year ago, or since you started using it) ==\n>\n> === 21. Did you participate in previous Git User's Surveys? ===\n> (multiple choice)\n>\n>  + in 2006\n>  + in 2007\n>  + in 2008\n>  + in 2009\n>  + none of the above\n>\n> NOTES:\n> ^^^^^^\n> This might be quite useful comparing with previous surveys.  The\n> answer 'none of the above' is new in this survey (as is 'in 2009',\n> of course).\n>\n>\n> === 22. How do you compare the current version with the version from one year ago? ===\n> (single choice)\n>\n>  * better\n>  * no changes\n>  * worse\n>\n>  * cannot say\n>\n> NOTES:\n> ^^^^^^\n> This question was mainly excuse for providing list of main changes\n> from the year ago.  I think that this question should be removed, as\n> it doesn't bring any important information.\n>\n>\n> == Documentation. Getting help. ==\n>\n> === 23. How useful have you found the following forms of Git documentation? ===\n> (matrix)\n>\n>  Columns: never used / not useful / somewhat / useful\n>  + Git Wiki\n>  + on-line help\n>  + help distributed with git\n>\n>\n> Description:\n> ~~~~~~~~~~~~\n> * Git Wiki was to be found at http://git.wiki.kernel.org\n> * on-line help includes, among others, Git Homepage (http://git-scm.com),\n>  \"Git Community Book\" (http://book.git-scm.com), \"Pro Git\" book\n>  (http://progit.org) and Git Reference site (http://gitref.org)\n> * help distributed with git include manpages, manual, tutorials, HOWTO,\n>  release notes, technical documentation, contrib/examples/\n>\n> NOTES:\n> ^^^^^^\n> Should we split those answers further, e.g. separating on-line\n> tutorials and guides, from on-line tips etc.?\n>\n>\n> === 24. Have you tried to get help regarding Git from other people? ===\n> (single choice)\n>\n>  * Yes\n>  * No\n>\n> === 25. If yes, did you get these problems resolved quickly and to your liking? ===\n> (single choice)\n>\n>  * Yes\n>  * No\n>  * Somewhat\n>\n> NOTES:\n> ^^^^^^\n> Those two questions are not very useful.  I think that they should be\n> removed from 2010 survey.\n>\n>\n> === 26. What channel(s) do you use to request help about git? ===\n> (multiple choice, with other)\n>\n>  + git mailing list (git@vger.kernel.org)\n>  + \"Git for Human Beings\" Google Group\n>  + msysGit mailing list / Google Group\n>  + IRC (#git)\n>  + IRC (other git/SCM related, e.g. #github)\n>  + request in blog post or on wiki\n>  + asking git guru/colleague\n>  + project mailing list, or IRC, or forum\n>  + Twitter or other microblogging platform\n>  + instant messaging (IM) like XMPP/Jabber\n>  + StackOverflow or other StackExchange site\n>\n>  + other (please specify)\n>\n> NOTES:\n> ^^^^^^\n> Are there any main channels of requesting help that I have missed in\n> the above list of answers?  What are they, and why do you think they\n> are important enought to warrant inclusion in above list?\n>\n>\n> === 27. Which communication channel(s) do you use? ===\n>        Do you read the mailing list, or watch IRC channel?\n> (multiple choice)\n>\n>  + git@vger.kernel.org (main)\n>  + Git for Human Beings (Google Group)\n>  + msysGit\n>  + #git IRC channel\n>  + #git-devel IRC channel\n>  + #github or #gitorious IRC channel\n>  + #revctrl IRC channel\n>\n> NOTES:\n> ^^^^^^\n> Are there any communication channels that I have missed?  For example\n> is there a separate channel that JGit/EGit developers use?\n\nFWIW: There were two non-bots on #git-devel when I joined it.\n\n> == About this survey. Open forum. ==\n>\n> === 28. How did you hear about this Git User's Survey? ===\n> (single choice, with other)\n>\n>  * git mailing list\n>  * git-related mailing list (e.g. msysGit)\n>  * mailing list or forum of some project\n>  * #git IRC channel topic\n>  * announcement on IRC channel\n>  * git homepage\n>  * git wiki\n>  * git hosting site (or blog related to such site)\n>  * software-related web site\n>  * news or social news site (e.g. Digg, Reddit)\n>  * blog (or blog planet)\n>  * other kind of web site\n>  * Twitter or other microblogging platform\n>\n>  * other - please specify\n>\n> NOTES:\n> ^^^^^^\n> This list would of course be updated to reflect the list of (planned)\n> announcement channels.\n>\n> There of course will be announcement on Git Mailing List, and perhaps\n> also on msysGit list / Google Group, and on Git For Human Beings\n> Google Group (if it exists).  I'll announce it on #git, and ask op to\n> put short announcement in channel description, and I can announce it\n> on other IRC channels.  I would add announcement to main page of Git\n> Wiki, and as Git Homepage administrator to put announcement about Git\n> User's Survey.\n>\n> I usually tried to contact administrators of git hosting sites,\n> including git.kernel.org, repo.or.cz, GitHub, Gitorious, Assembla,\n> Codebase and Unfuddle, asking them to put announcement about\n> Git User's Survey either somewhere on the site, or in their blog\n> (if there is any).  What git hosting sites it is worth to ask?\n>\n> Sidenote: I am thinking about contacting different git hosting sites\n> _before_ staring survey, asking them (them = administrators) about\n> what questions would they like to see.  Do you think thet it is good\n> idea?\n\nYes, definitely.\n\n> Should I try to post announcement on mailing list for projects that\n> use git?  There are entirely too many such projects nowadays, and such\n> announcement can be considered spamming by some...\n\nYeah. Definitely for the big ones like the \"Projects using Git\" listed\non git-scm.com. I don't think it'll be considered spam.\n\n> I would like to have announcement of Git User's Survey 2010 at\n> LWN.net, but this would need to be send at least two weeks in advance,\n> if I remember correctly.  Is it worth it?  What other news site should\n> I (or you) send announcement to?\n\nreddit, digg, hackernews, slashdot, ...\n\n> If you can Digg / Reddit announcment on some site, please do.  I can\n> announce Git User's Survey 2-1- at Twitter, Identi.ca and Plurk, but I\n> don't have wide area of followers.  So please RT.\n>\n> Should we contact some bloggers (besides asking Junio to put\n> announcement on his blog) to post an anouncement?  Which bloggers\n> would respond positively (perhaps Linus...)?\n"},{"id":"144772","messageId":"201007041013.40563.jnareb@gmail.com","threadId":"24279","inReplyTo":"AANLkTilD8N6rnj9e3KzRB7_q3J0I4cJGx5EduX_UJScC@mail.gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-07-04T08:13:35Z","receivedAt":"2010-07-04T08:13:35Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"On Sun, 4 Jul 2010, Ævar Arnfjörð Bjarmason wrote:\n> 2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n\n[...]\n> > == Getting started with Git ==\n> >\n> > === 03. Have you found Git easy to learn? ===\n> > (single choice)\n> >\n> > * Very easy\n> > * Easy\n> > * Reasonably easy\n> > * Hard\n> > * Very hard\n> >\n> > === 04. Have you found Git easy to use? ===\n> > (single choice)\n> >\n> > * Very easy\n> > * Easy\n> > * Reasonably easy\n> > * Hard\n> > * Very hard\n> >\n> > NOTES:\n> > ^^^^^^\n> > Those two questions, considered alone, doesn't tell us much.  If one use\n> > git, then usually one does not think it is too hard to use (unless forced to\n> > use git by external circumstances, like project he/she works on using git).\n> > On the other hand those two questions together give us some mesaure of git\n> > learning curve, telling us if people consider git easy to use but hard to\n> > learn, or vice versa ;-)\n> >\n> > I think it might be also good to have to calculate correlations, e.g. if\n> > people who find git hard to use make use of its advanced features.\n> >\n> > The question is: should they stay, or should they go?\n> \n> They should probably stay. But they don't really ask the right\n> question IMO. Which is not whether users think it's difficult to\n> learn, but whether it's unreasonably difficult for the problem they're\n> solving.\n> \n> I.e. jet aircraft are hard to operate, but they also do neat\n> stuff. How hard is Git to learn for the problem it's solving?\n\nThe problem is how to formulate question about this issue.  We cannot\nreally ask about perceived accidental and essential (inherent)\ncomplexity, can we?\n\nPerhaps something like this:\n\n=== xx. Have you found distributed version control easy? ===\n(multiple choice)\n\n + Very easy\n + Easy\n + Reasonably easy\n + Hard\n + Very hard\n\nOr something like that, with separate question if DVCS is difficult\nor not.\n\nAlternatively we could ask about _relative_ ease of learning / use.\nBut I don't think this would go well (and I don't think we could get\ngood answers from that).\n\n[...] \n> > === 14. How do you fetch/get changes from upstream repositories? ===\n> > (multiple choice, with other)\n> >\n> >  + git protocol        (e.g. git://git.example.com/repo.git)\n> >  + ssh                 (e.g. ssh+git://git.example.com/repo.git,\n> >                             git.example.com:/srv/scm/repo.git)\n> >  + http                (e.g. http://git.example.com/repo.git)\n> >  + rsync (DEPRECATED)  (e.g. rsync://git.example.com/repo.git)\n> >  + filesystem          (e.g. /path/to/repo.git, file:///path/to/repo.git)\n> >  + via git-bundle\n> >  + foreign SCM (e.g. git-svn)\n> >\n> >  + Other, please specify\n> \n> Maybe git format-patch -> git am. Since it's already this complete.\n\nDoes anybody use git-format-patch + git-am for *fetching* (and cloning)?\n\n[...]\n> > === 17. Which of the following features would you like to see implemented in git? ===\n> > (multiple choice)\n> >\n> >  + better support for big files (large media)\n> >  + resumable clone/fetch (and other remote operations)\n> >  + GitTorrent Protocol, or git-mirror\n> >  + lazy clone / on-demand fetching of object\n> >  + support for tracking empty directories\n> >  + environmental variables in config,\n> >   and expanding ~ and ~user in paths in config\n> >  + better undo/abort/continue, and for more commands\n> >  + '-n' like option for each command, which describes what would happen\n> >  + side-by-side diffs and/or color-words diff in gitweb\n> >  + admin and/or write features in gitweb\n> >  + graphical history view in gitweb\n> >  + GUI for rebase in git-gui\n> >  + GUI for creating repository in git-gui\n> >  + filename encoding (in repository vs in filesystem)\n> >  + git push --create\n> >  + localization of command-line messages\n> >  + wholesame directory rename detection\n> >  + graphical merge tool integrated with git-gui\n> >  + union checkouts (some files from one branch, some from other)\n> >  + advisory locking / \"this file is being edited\"\n> >  + \"commands issued\" (or \"command equivalents\") in git-gui / gitk\n> >  + warn before/when rewriting published history\n> >  + built-in gitjour/bananajour support\n> >  + syntax highlighting in git-gui\n> >\n> >  + other (describe below)\n> >\n> > NOTES:\n> > ^^^^^^\n> > This is new question, a multiple choice companion to a essay free-form\n> > question below.  Included are a few example features (some from\n> > partial analysis of \"19. What features would you like implemented in\n> > Git?\" question in 2009 survey.\n> >\n> > What features should be mentioned besides those above?  What criteria\n> > should we have for including features in this list?\n> \n> I think \"submodules that Just Work(TM)\" or something similar should be\n> included. I.e. something the user doesn't have to worry about anymore\n> than they do a normal tree entry. Git's complex submodule support is\n> something I often hear complaints about.\n\nI'll add 'better submodule support' to this list.\n\n[...] \n> > === 27. Which communication channel(s) do you use? ===\n> >        Do you read the mailing list, or watch IRC channel?\n> > (multiple choice)\n> >\n> >  + git@vger.kernel.org (main)\n> >  + Git for Human Beings (Google Group)\n> >  + msysGit\n> >  + #git IRC channel\n> >  + #git-devel IRC channel\n> >  + #github or #gitorious IRC channel\n> >  + #revctrl IRC channel\n> >\n> > NOTES:\n> > ^^^^^^\n> > Are there any communication channels that I have missed?  For example\n> > is there a separate channel that JGit/EGit developers use?\n> \n> FWIW: There were two non-bots on #git-devel when I joined it.\n\nWell, Git User's Surveys always served more or less accidentally as\nthe source of information about git and git community (\"we have wiki?\"\nfrom the first survey ;-))\n\n> > == About this survey. Open forum. ==\n> >\n> > === 28. How did you hear about this Git User's Survey? ===\n> > (single choice, with other)\n> >\n> >  * git mailing list\n> >  * git-related mailing list (e.g. msysGit)\n> >  * mailing list or forum of some project\n> >  * #git IRC channel topic\n> >  * announcement on IRC channel\n> >  * git homepage\n> >  * git wiki\n> >  * git hosting site (or blog related to such site)\n> >  * software-related web site\n> >  * news or social news site (e.g. Digg, Reddit)\n> >  * blog (or blog planet)\n> >  * other kind of web site\n> >  * Twitter or other microblogging platform\n> >\n> >  * other - please specify\n> >\n> > NOTES:\n> > ^^^^^^\n> > This list would of course be updated to reflect the list of (planned)\n> > announcement channels.\n> >\n> > There of course will be announcement on Git Mailing List, and perhaps\n> > also on msysGit list / Google Group, and on Git For Human Beings\n> > Google Group (if it exists).  I'll announce it on #git, and ask op to\n> > put short announcement in channel description, and I can announce it\n> > on other IRC channels.  I would add announcement to main page of Git\n> > Wiki, and as Git Homepage administrator to put announcement about Git\n> > User's Survey.\n> >\n> > I usually tried to contact administrators of git hosting sites,\n> > including git.kernel.org, repo.or.cz, GitHub, Gitorious, Assembla,\n> > Codebase and Unfuddle, asking them to put announcement about\n> > Git User's Survey either somewhere on the site, or in their blog\n> > (if there is any).  What git hosting sites it is worth to ask?\n> >\n> > Sidenote: I am thinking about contacting different git hosting sites\n> > _before_ staring survey, asking them (them = administrators) about\n> > what questions would they like to see.  Do you think thet it is good\n> > idea?\n> \n> Yes, definitely.\n\nWhich ones?  I'll definitely contact GitHub, try to contact J.H. about\ngit.kernel.org and pasky about repo.or.cz, and contact admins/contact\nof Assembla, Codebase, Unfuddle.  Who else to contact?\n\n> \n> > Should I try to post announcement on mailing list for projects that\n> > use git?  There are entirely too many such projects nowadays, and such\n> > announcement can be considered spamming by some...\n> \n> Yeah. Definitely for the big ones like the \"Projects using Git\" listed\n> on git-scm.com. I don't think it'll be considered spam.\n\nThe questions is: which ones are big?  Those on Git Homepage?  Those\non \"Git (software)\" page on Git Wiki?  Which ones to try to contact\nbesides those on this list (and what list if there is '?' here)?\n\n * Linux kernel (LKML)\n * Android (?)\n\n * Debian (DWN list / wiki)\n * Fedora (?)\n * openSUSE (?)\n\n * GIMP (?)\n * GNOME (newren's blog?)\n * jQuery? (?)\n * OLPC? (olpc-devel?)\n * Perl (perlbuzz, some Perl blogger?)\n * Ruby on Rails (RubyForge, ?)\n * Samba? (mailin list IIRC?)\n * VLC? (vlc mailing list)\n * Wine? (?)\n * X.Org (freedesktop.org wiki?)\n\nSidenote: I can also try to post announcement on various wikis that\nhost some (more or less specific) information about how to do git\ndevelopment for given project.\n\n> > I would like to have announcement of Git User's Survey 2010 at\n> > LWN.net, but this would need to be send at least two weeks in advance,\n> > if I remember correctly.  Is it worth it?  What other news site should\n> > I (or you) send announcement to?\n> \n> reddit, digg, hackernews, slashdot, ...\n\nReddit, Digg and HackerNews are social news sites, and all require\nhaving some official (or at least official-sounding) already existing\npage with official announcement (GMane link, or GitWiki page?).  All\nwould also rquire upvoting...\n \n> > If you can Digg / Reddit announcment on some site, please do.  I can\n> > announce Git User's Survey 2-1- at Twitter, Identi.ca and Plurk, but I\n> > don't have wide area of followers.  So please RT.\n> >\n> > Should we contact some bloggers (besides asking Junio to put\n> > announcement on his blog) to post an anouncement?  Which bloggers\n> > would respond positively (perhaps Linus...)?\n\nI can try to contact masukomi[1] (Kate Rhodes) and rtomayko[2]\n(Ryan Tomayko), both of whom have written positively about Git\nin the past, Junio C Hamano[3] of course, and perhaps also\nLinus Torvalds[4]\n\n[1] http://weblog.masukomi.org/\n[2] http://tomayko.com/\n[3] http://gitster.livejournal.com/\n[4] http://torvalds-family.blogspot.com/\n\nYou all can help, of course...\n\n-- \nJakub Narebski\nPoland\n"},{"id":"144774","messageId":"AANLkTimbpOEpi8QOqTOMav0whmLeHz3vQq_0KDnblRIK@mail.gmail.com","threadId":"24279","inReplyTo":"201007032158.57700.jnareb@gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"David Bainbridge","fromEmail":"david.bainbridge@gmail.com","sentAt":"2010-07-04T09:07:17Z","receivedAt":"2010-07-04T09:07:17Z","isPatch":false,"sender":{"key":"david.bainbridge@gmail.com","avatar":"https://gravatar.com/avatar/1689d4383c7d0d399e2803ddbbecf83b7a4cb9bff89f45917e28b351933ccef1?d=mp&s=160"},"body":"Hi Jakub,\n\nFirst, as someone working in a company that is adopting Git can I say\nthat I found the results of previous surveys useful? So I think that\nthese surveys should continue :-)\n\nI think that the reduction of free text fields is good ... I am\nconcerned that if I point several hundred users at the this survey and\nencourage them to respond that you should not get swamped!\n\nThe surveys are actually useful for making people more aware of what\nGit can do, and the other tools associated with Git, so this is\nsomething of bear in mind.\n\nHave you considered the question: 'How long have you been using Git?'.\nThis combined the expertise level might yield some useful information,\nand could provide some weighting for the 'Getting started' questions\ntoo. There are some problems with the question in that it could be,\nsay, 2 years intermittent use, or 2 years continuous use, and these\nare different, of course.\n\nThe demographic information is useful if you want to understand\nwhether Git is (for example) considered less usable in countries where\nEnglish is not the native language. But then if you want to know the\nnative language of the user rather than where they live then perhaps\nthis should be asked? (I was born in the UK, but now live in Sweden\n... so I am perhaps more conscious of this!). Where you are born does\nnot necessarily identify your native language either.\n\nDo you want to separate work usage and 'non-work' usage at all? The\ntwo experiences may be completely different. If I am working at home I\ncan use what ever I want, and work how I want. This will probably not\nbe the case in a corporate environment, so I would report one set of\nresults for 'work' and another for 'non-work'. This could generate two\nsurvey returns for a single user. Is this intended?\n\nJust a couple of thoughts :-)\n\nDavid Bainbridge\nSweden\n\n\n2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n> I'm sorry for broken (badly wrapped) previous version...\n> ----\n>\n> I guess it is time for annual (so far) Git User's Survey.  Should\n> there be one?  When should it start, and how long should it last?\n>\n> here is how it was for previous surveys:\n>  * 2009 was open from 15 July   to 15 September 2009 (for 2 months)\n>  * 2008 was open from 31 August to 14 October 2008 (for 1.5 months)\n>  * 2007 was open from 20 August to 10 September 2007 (for 20 days)\n>        (officially: results are up until 28 September 2007)\n>  * 2006 was open from 23 July   to 6-12 September 2006\n>   (for a bit less than 2 months)\n>\n> With more that 3000 responses in 2008 and 2009 survey, analysing\n> free-form data was hard.  That is why in this proposal there is only\n> single one free-form response (about missing features).\n>\n> What questions (and with what proposed answers) shound there be in\n> this year survey?  Below there is the content of the proposed survey:\n>\n>\n> = Git User's Survey 2010 (proposal) =\n>\n> == About you ==\n>\n> NOTES:\n> ^^^^^^\n> This section gives us a bit of demographical information about survey\n> responders.  Is it useful?  Should we leave it in survey, or remove it?\n>\n> Should we for example include 'gender' as one of questions?  Perl Survey\n> 2010 did.\n>\n>\n> === 01. What country do you live in? ===\n>        (Country of residence)\n> (free-form single line)\n>\n> NOTES:\n> ^^^^^^\n> Perhaps a better solution would be a menu (drop-down list) of countries,\n> using list of current countries.  It would be more work to create it, but\n> might reduce ambiguities and unparsable responses.\n>\n> What I'd like to have is to pre-fill / select default answer based on GeoIP.\n> Even better would be to be able to show current position on Google Map, like\n> contributors and users map on Ohloh... but that I think is simply not\n> possible with Survs.com, the site to be used for this survey (and I guess\n> neither with any other survey site).  One can dream.\n>\n> Pel Survey 2010 also included (from what I remember, and from provided data\n> and analysis of survey) also country of origin / country of birth, to\n> measure mobility.  I wonder if it would make sense to have the same for Git\n> User's Survey 2010...  Note that it would be harder to come up with the list\n> of countries for such question, because the country might no longer exists.\n> Therefore the list (if present) should be based on all countries that exist\n> or existed since 100 years ago (or so).\n>\n>\n> === 02. How old are you (in years)? ===\n> (free-form single line)\n>\n> NOTES:\n> ^^^^^^\n> Instead of unconstrained free-form response it might be better to have\n> single choice (or menu) of age ranges.  What do you think?  Of course with\n> ranges there is question what ranges to use (how to quantize age); goo\n> solution would be to chose ranges corresponding somewhat to the levels of\n> education.\n>\n>\n> == Getting started with Git ==\n>\n> === 03. Have you found Git easy to learn? ===\n> (single choice)\n>\n> * Very easy\n> * Easy\n> * Reasonably easy\n> * Hard\n> * Very hard\n>\n> === 04. Have you found Git easy to use? ===\n> (single choice)\n>\n> * Very easy\n> * Easy\n> * Reasonably easy\n> * Hard\n> * Very hard\n>\n> NOTES:\n> ^^^^^^\n> Those two questions, considered alone, doesn't tell us much.  If one use\n> git, then usually one does not think it is too hard to use (unless forced to\n> use git by external circumstances, like project he/she works on using git).\n> On the other hand those two questions together give us some mesaure of git\n> learning curve, telling us if people consider git easy to use but hard to\n> learn, or vice versa ;-)\n>\n> I think it might be also good to have to calculate correlations, e.g. if\n> people who find git hard to use make use of its advanced features.\n>\n> The question is: should they stay, or should they go?\n>\n>\n> === 05. Which Git version(s) are you using? ===\n> (multiple choice, with other)\n>\n>  + pre 1.3\n>  + 1.3.x\n>  + 1.4.x\n>  + 1.5.x\n>  + 1.6.x\n>  + 1.7.x\n>\n>  + minor (maintenance) release 1.x.y.z\n>  + 'master' branch of official git repository\n>  + 'next' branch of official git repository\n>  + 'pu' branch of official git repository\n>  + version from msysGit / Git for Windows fork repository\n>  + git-bigfiles fork\n>  + JGit implementation (e.g. via Eclipse plugin, EGit)\n>\n>  + other, please specify\n>\n> NOTES:\n> ^^^^^^\n> A few of possible answers are new in this version of survey, namely 'pu',\n> msysGit, git-bigfiles, JGit, and of course 1.7.x.\n>\n> This question is here to stay.\n>\n>\n> === 06. Rate your own proficiency with Git: ===\n> (single choice)\n>\n>  * 1. novice\n>  * 2. casual, needs advice\n>  * 3. everyday use\n>  * 4. can offer advice\n>  * 5. know it very well\n>\n> NOTES:\n> ^^^^^^\n> This question tell us penetration of announcements of Git User's Survey 2010;\n> did we get to all, or only to git gurus?  It is also useful for correlating\n> with other responses, for example to know which features are used by\n> novices, and which by gurus.\n>\n>\n> == How you use Git ==\n>\n> === 07. I use Git for (check all that apply): ===\n> (multiple choice, with other)\n>\n> Note that above choices are neither orthogonal nor exclusive.  One\n> might want to check multiple answers even for a single repository.\n>\n> NOTES:\n> ^^^^^^\n> Answers to this question probe different direction.\n> This list is interspersed with comments about specific\n> (sub)sections.\n>\n>  + work projects\n>  + unpaid projects\n>\n> Notes:\n> ^^^^^^\n> Those two are about using git at work vs using git on your own free time.\n> There are of course shades of gray, like using git for work project\n> unofficially (e.g.using git-svn as \"fat\" client for company's Subversion\n> repository), or employer allowing to work on non-work OSS project during\n> working hours.  But I'm not sure if they are worth adding.\n>\n>  + proprietary projects\n>  + OSS development (also public domain, and published & unlicensed)\n>  + private (unpublished)\n>\n> Notes:\n> ^^^^^^\n> Those three are about licensing: proprietary / free (open) / unlicensed.\n> By 'OSS development' I mean here also free licenses for documentation and\n> documents, like GFDL or Creative Commons licenses.\n>\n>  + code (programming)\n>  + personal data\n>  + documents (data)\n>  + static website\n>  + web app\n>  + large (> 1MB) binary files\n>  + often changing binary files\n>\n> Notes:\n> ^^^^^^\n> This is about what kind of data do you store in git.  I am a bit unsure\n> whether it is worth separating 'web app'; it is 'code'.\n>\n> New in this edition of survey is 'large binary data' and 'often changing\n> binary files'... but should 'large' cutoff be 1MB, or 10MB, or 50MB, or\n> 100MB?\n>\n> I'm not sure about having 'personal data'...\n>\n>  + sharing data or sync\n>  + managing configuration files\n>  + backup\n>  + backend for wiki, blog, or other web app\n>  + frontend to other SCM (e.g. git-svn)\n>\n> Notes:\n> ^^^^^^\n> This is about (ab)using git for other things than straighforward source\n> control management.  List of possible answers specified here should cover\n> most commonly encountered usages: shdoul we add anything else here?\n>\n>  + other (please specify)\n>\n>\n> === 08. How do/did you obtain Git (install and/or upgrade)? ===\n> (multiple choice, with other)\n>\n> Note that this question is multiple choices question because one can\n> install Git in different ways on different machines or on different\n> operating systems.\n>\n>  + binary package\n>  + source package or script\n>  + source tarball\n>  + pull from (main) repository\n>  + preinstalled / sysadmin job\n>\n>  + other - please specify\n>\n> Description:\n> ~~~~~~~~~~~~\n> Explanation: \"binary package\" covers pre-compiled binary (e.g.  from\n> rpm or deb binary packages); \"source package\" covers things like\n> deb-src and SRPMS / *.src.rpm; \"source script\" is meant to cover\n> installation in source-based distributions, like 'emerge' in Gentoo.\n>\n> Automatic update (apt, yum, etc.) in most cases means binary package\n> install; unless one uses source-based distribution like Gentoo, CRUX,\n> or SourceMage, where automatic update means using source package (or\n> source script).\n>\n> The option named \"preinstalled / sysadmin job\" means that either you\n> didn't need to install git because it was preinstalled (and you didn't\n> upgrade); or that you have to ask system administrator to have git\n> installed or upgraded.\n>\n> Note that this question is multiple choices question because one can\n> install Git in different ways on different machines or on different\n> operating systems.\n>\n> NOTES:\n> ^^^^^^\n> What I didn't take into account in above explanation is operating\n> systems with packaging systems different that the one used by various\n> Linux distributions.\n>\n> In short: if to have git installed you compile it, you use source\n> package or source tarball.  If the installation onvolves anything more\n> than 'make install' (or manual copying), then it is most probably\n> source package or script.\n>\n> This for example means that \"msysGit\" installer is source package, and\n> \"Git for Windows\" is binary package, if I understand it correctly.\n>\n>\n> === 09. On which operating system(s) do you use Git? ===\n> (multiple choice, with other)\n>\n>  + Linux (includes MeeGo and Moblin)\n>  + MacOS X (Darwin)\n>  + MS Windows/msysGit (MINGW)\n>  + MS Windows/Cygwin\n>  + FreeBSD, OpenBSD, NetBSD, etc.\n>  + other Unix\n>\n>  + iPhone OS\n>  + Android\n>  + WebOS\n>\n>  + Other, please specify\n>\n> NOTES:\n> ^^^^^^\n> The iPhone OS, Androind and WebOS answers are new this year.\n> OpenSolaris died, so I removed it.  I wonder if it is worth it to\n> differentiate between MS Windows/msysGit and MS Windows/Cygwin, or if\n> we should just have one, single 'MS Windows' choice.\n>\n>\n> === 10. What do you use to edit contents under version control with Git? ===\n>        What kind of editor, IDE or RAD you use working with Git?\n> (multiple choice, with other)\n>\n>  + simple text editor\n>  + programmers editor\n>  + IDE or RAD\n>  + WYSIWYG tool\n>\n>  + other kind\n>\n> Description:\n> ~~~~~~~~~~~~\n> * \"simple text editor\" option includes editors such as pico, nano,\n>  joe, Notepad,\n>\n> * \"programmets editor\" option includes editors such as Emacs/XEmacs,\n>  Vim, TextMate, SciTE (syntax highlighting, autoindentation,\n>  integration with other programmers tools, etc.)\n>\n> * \"IDE (Integrated Development Environment) and RAD (Rapid Application\n>  Development)\" option includes tools such as Eclipse, NetBeans IDE,\n>  IntelliJ IDE, MS Visual Studio, KDevelop, Anjuta, Xcode,\n>  Code::Blocks but also tools such as Quanta+, BlueFish or Screem (for\n>  editing HTML, CSS, PHP etc.), and Kile or LEd for LaTeX.\n>\n> * \"WYSIWYG tools\" option includes word processors such as MS Office or\n>  OpenOffice.org, but also tools such as Adobe Acrobat (for PDF) or\n>  GIMP (for images), or WYSIWYG DTP tools such as QuarkXPress,\n>  PageMaker or Scribus, or WYSIWYG HTML editors such as FrontPage,\n>  Dreamweaver or KompoZer.\n>\n> NOTES:\n> ^^^^^^\n> Is this question useful, or should it be removed from survey?\n>\n>\n> === 11. What Git interfaces and frontends do you use? ===\n> (multiple choice, with other)\n>\n>  + Cogito (DEPRECATED)\n>  + Easy Git\n>  + Pyrite\n>  + I don't know, I only use (graphical) tools\n>\n>  + pg aka Patchy Git (DEPRECATED)\n>  + StGIT\n>  + Guilt\n>  + TopGit\n>\n>  + other (please specify)\n>\n> NOTES:\n> ^^^^^^\n> This version is going back to split from 2008 survey, rather than\n> having everything put together like in 2009 one.  There are, of\n> course, problems with both choices.\n>\n> The problem with split part is that people can have troubls with\n> distinguising between interfaces, implementations, frontends and tools\n> (although \"I don't know ...\"  answer should, I think, help here).  The\n> problem with having it everything together is that the list of\n> possible answers gets long and a bit unwieldy.\n>\n> BTW are there any implementations and frontends that should be added\n> to the list above?\n>\n>\n> === 12. What kind of Git tools do you use? ===\n> (multiple choice, with other)\n>\n> If a tool is both history viewer, and commit tool, please choose the\n> option that corresponds to how do you use this tool.\n>\n>  + editor/IDE VC integration (e.g. EGit, TextMate bundle, magit)\n>  + filemanager / shell extension (e.g. git-cheetah, TortoiseGit)\n>  + graphical history viewer/browser (e.g. gitk)\n>  + graphical commit tool (e.g. git-gui)\n>  + graphical diff and/or merge tool (e.g. Kompare, Meld)\n>  + graphical blame or pickaxe tool\n>  + git-instaweb, or self-hosted web interface\n>  + tool to manage git repositories (e.g. Gitosis, Gitolite)\n>\n>  + my own scripts (for daily use)\n>  + my own scripts (for special tasks)\n>\n> NOTES:\n> ^^^^^^\n> As the number of tools increases (see InterfacesFrontendsAndTools page\n> on git wiki), having them listed all there gets a bit unwieldy.  On\n> the other hand it was a good way to find new tools that were not yet\n> included on IFaT page.  What do you think: should it be about tools,\n> or only about kind of tools used with git?\n>\n> What do you think about this list?  IS there something that should not\n> be here?  Or perhaps there is something that should be added to this\n> list?\n>\n>\n> === 13. Which git hosting site(s) do you use for your project(s)? ===\n>        Please check only hosting sites where you publish/push to (with git)\n> (multiple choice, with other)\n>\n>  + [http://repo.or.cz repo.or.cz]\n>  + [http://github.com GitHub]\n>  + [http://gitorious.org Gitorious]\n>  + [http://www.indefero.net InDefero]\n>\n> Notes:\n> ^^^^^^\n> Those are generic git hosting sites, each of them showcasing their own\n> tool, all except GitHub open source (it is Girocco for repo.or.cz; for\n> the rest the tool is named the same as the git hosting site).\n>\n>  + [http://savannah.gnu.org Savannah]\n>  + [http://sourceforge.net SourceForge]\n>\n> Notes:\n> ^^^^^^\n> Generic software hosting sites, with git support.  Did I miss\n> something, should I include yet another site?\n>\n>  + [http://www.assembla.com Assembla]\n>  + [http://codebasehq.com Codebase]\n>  + [http://unfuddle.com Unfuddle]\n>  - [http://codesion.com Codesion]\n>  - [http://gitfarm.appspot.com GitFarm]\n>  - [http://www.projectlocker.com ProjectLocker]\n>  - [http://thechaw.com The Chaw]\n>  - [http://unfuddle.com Unfuddle]\n>\n> Notes:\n> ^^^^^^\n> Those are commercial and/or less known git hosting sites.  I am not\n> sure which ones of those marked with '-' to include, and whether to\n> include other sites from GitHosting page on git wiki.  What do you\n> think?\n>\n>  + [http://git.kernel.org kernel.org]\n>  + [http://www.freedesktop.org/wiki/ freedesktop.org]\n>\n> Notes:\n> ^^^^^^\n> Those are 'git hosting site for related projects', but are special in\n> some sense.  Should I leave them there, or remove from this list?\n>\n>  + [http://alioth.debian.org Alioth] (Debian)\n>  + [http://hosted.fedoraproject.org Fedora Hosted]\n>\n> Notes:\n> ^^^^^^\n> Those are distribution-specific.  Are there any sites that I missed?\n> Launchpad from Ubuntu does not count, as it is Bazaar hosting site,\n> not Git hosting site.\n>\n>  +  git hosting site for related projects\n>  +  generic site without git support\n>  +  self hosted\n>\n> Notes:\n> ^^^^^^\n> Are ther other kinds / typse of sites one can host project using git\n> on?  What are they?\n>\n>  +  Other (please specify)\n>\n> NOTES:\n> ^^^^^^\n> I think this question is here to stay.\n>\n>\n> === 14. How do you fetch/get changes from upstream repositories? ===\n> (multiple choice, with other)\n>\n>  + git protocol        (e.g. git://git.example.com/repo.git)\n>  + ssh                 (e.g. ssh+git://git.example.com/repo.git,\n>                             git.example.com:/srv/scm/repo.git)\n>  + http                (e.g. http://git.example.com/repo.git)\n>  + rsync (DEPRECATED)  (e.g. rsync://git.example.com/repo.git)\n>  + filesystem          (e.g. /path/to/repo.git, file:///path/to/repo.git)\n>  + via git-bundle\n>  + foreign SCM (e.g. git-svn)\n>\n>  + Other, please specify\n>\n> Description:\n> ~~~~~~~~~~~~\n> This question asks about how do you get changes (updates) from\n> projects you follow into your local repository. It is not about how do\n> you get latest version of Git.\n>\n> Fetching (or rather cloning) via bundle could mean that project\n> publishes ready for download bundles to reduce traffic and load on\n> server (HTTP download [of bundle] can be resumed, git-clone currently\n> cannot; one can also distribute bundle using P2P).\n>\n> NOTES:\n> ^^^^^^\n> What is new are examples of URLs / URIs for each protocol.\n>\n> Did I miss anything?  Is this question interesting, and should it\n> stay, or should it be removed?\n>\n>\n> === 15. How do you publish/propagate your changes? ===\n> (multiple choice, with other)\n>\n>  + push\n>  + pull request (+ any form of announcement / notification)\n>  + format-patch + email\n>  + format-patch + other (e.g. reviewboard, issue tracker or forum)\n>  + git bundle\n>\n>  + git-svn (to Subversion repository)\n>  + git-p4 (to Perforce repository)\n>  + foreign SCM interface (other than mentioned above)\n>\n>  + other - please specify\n>\n> Description:\n> ~~~~~~~~~~~~\n> Publishing via bundle could mean sending bundle via email, or posting\n> it on review board (or forum).\n>\n> Instead of git-format-patch there can be utilized other way of\n> generating patch (e.g. git-show, git-diff, 'patch' view from gitweb,\n> etc.)\n>\n> NOTES:\n> ^^^^^^\n> Should it stay, or should it be removed?  I guess it can be\n> interesting for git hosting sites...  Should we have separate answrs\n> for different kinds of push (ssh, \"dumb\" HTTP(S) with WebDAV, \"smart\"\n> HTTP - if it is possible, git:// protocol with push enabled)?\n>\n>\n> === 16. Which of the following features do you use? ===\n> (multiple choice, with other)\n>\n>  + \"smart\" HTTP protocol\n>  + git bundle (off-line transport)\n>  + eol conversion (crlf)\n>  + gitattributes\n>  + custom diff/merge driver\n>  + submodules (subprojects)\n>  + subtree merge (optionally git-subtree)\n>  + partial (sparse) checkout, or assume-unchanged bit\n>  + separate worktree / core.worktree\n>  + multiple worktrees (git-new-worktree)\n>  + alternates mechanism (sharing object database)\n>  + stash (optionally \"git stash --keep-index\")\n>  + shallow clone (e.g. \"git clone --depth=<n>\")\n>  + detaching HEAD (e.g. \"git checkout HEAD^0\")\n>  + interactive rebase (small scale history editing)\n>  + interactive commit / per-hunk comitting / partial commit\n>  + commit message templates\n>  + git-filter-branch or equivalent (large history rewriting)\n>  + bisect (optionally \"git bisect run <script>\")\n>  + committing with dirty tree (keeping some changes uncommitted)\n>  + non-default hooks (from contrib/hooks/ or other)\n>  + shell completion of commands\n>  + git-aware shell prompt\n>  + git aliases, shell aliases for git, or own git scripts\n>  + one-way interaction with other SCMs (from SCM to git)\n>  + two-way interaction with other SCMs (from SCM to git, from git to SCM)\n>  + git-cvsserver\n>  + git notes\n>\n>  + Other, please specify\n>\n> NOTES:\n> ^^^^^^\n> The problem is come up not with exhaustive list of features: there are\n> too many of them to list.  The problem is coming up with list of\n> important and used enough often features.\n>\n> So: what features should be included in this list?  What features\n> should be removed from above list of answers?\n>\n>\n> === 17. Which of the following features would you like to see implemented in git? ===\n> (multiple choice)\n>\n>  + better support for big files (large media)\n>  + resumable clone/fetch (and other remote operations)\n>  + GitTorrent Protocol, or git-mirror\n>  + lazy clone / on-demand fetching of object\n>  + support for tracking empty directories\n>  + environmental variables in config,\n>   and expanding ~ and ~user in paths in config\n>  + better undo/abort/continue, and for more commands\n>  + '-n' like option for each command, which describes what would happen\n>  + side-by-side diffs and/or color-words diff in gitweb\n>  + admin and/or write features in gitweb\n>  + graphical history view in gitweb\n>  + GUI for rebase in git-gui\n>  + GUI for creating repository in git-gui\n>  + filename encoding (in repository vs in filesystem)\n>  + git push --create\n>  + localization of command-line messages\n>  + wholesame directory rename detection\n>  + graphical merge tool integrated with git-gui\n>  + union checkouts (some files from one branch, some from other)\n>  + advisory locking / \"this file is being edited\"\n>  + \"commands issued\" (or \"command equivalents\") in git-gui / gitk\n>  + warn before/when rewriting published history\n>  + built-in gitjour/bananajour support\n>  + syntax highlighting in git-gui\n>\n>  + other (describe below)\n>\n> NOTES:\n> ^^^^^^\n> This is new question, a multiple choice companion to a essay free-form\n> question below.  Included are a few example features (some from\n> partial analysis of \"19. What features would you like implemented in\n> Git?\" question in 2009 survey.\n>\n> What features should be mentioned besides those above?  What criteria\n> should we have for including features in this list?\n>\n> === 18. Describe what features would you like to have in Git, if it is\n>        not on the list above? ===\n> (free form, essay length)\n>\n>\n> == What you think of Git ==\n>\n> === 19. Overall, how happy are you with Git? ===\n> (single choice)\n>\n>  * unhappy\n>  * not so happy\n>  * happy\n>  * very happy\n>  * completely ecstatic\n>\n> NOTES:\n> ^^^^^^\n> I'm not sure if this question is at all useful.\n>\n> There is also problem, that the current wording is considered biased\n> by some, but on the other hand changing wording of answers would make\n> it impossible to compare it to answers from previous surveys...\n>\n>\n> === 20. In your opinion, which areas in Git need improvement? ===\n>        Please state your preference.\n> (matrix)\n>\n>   Columns: don't need / a little / some / much\n>  + user-interface\n>  + documentation\n>  + performance\n>  + more features\n>  + tools (e.g. GUI)\n>  + localization (translation)\n>\n> NOTES:\n> ^^^^^^\n> Are there any general areas that are missing from this list?\n> What are they?\n>\n>\n> == Changes in Git (since year ago, or since you started using it) ==\n>\n> === 21. Did you participate in previous Git User's Surveys? ===\n> (multiple choice)\n>\n>  + in 2006\n>  + in 2007\n>  + in 2008\n>  + in 2009\n>  + none of the above\n>\n> NOTES:\n> ^^^^^^\n> This might be quite useful comparing with previous surveys.  The\n> answer 'none of the above' is new in this survey (as is 'in 2009',\n> of course).\n>\n>\n> === 22. How do you compare the current version with the version from one year ago? ===\n> (single choice)\n>\n>  * better\n>  * no changes\n>  * worse\n>\n>  * cannot say\n>\n> NOTES:\n> ^^^^^^\n> This question was mainly excuse for providing list of main changes\n> from the year ago.  I think that this question should be removed, as\n> it doesn't bring any important information.\n>\n>\n> == Documentation. Getting help. ==\n>\n> === 23. How useful have you found the following forms of Git documentation? ===\n> (matrix)\n>\n>  Columns: never used / not useful / somewhat / useful\n>  + Git Wiki\n>  + on-line help\n>  + help distributed with git\n>\n>\n> Description:\n> ~~~~~~~~~~~~\n> * Git Wiki was to be found at http://git.wiki.kernel.org\n> * on-line help includes, among others, Git Homepage (http://git-scm.com),\n>  \"Git Community Book\" (http://book.git-scm.com), \"Pro Git\" book\n>  (http://progit.org) and Git Reference site (http://gitref.org)\n> * help distributed with git include manpages, manual, tutorials, HOWTO,\n>  release notes, technical documentation, contrib/examples/\n>\n> NOTES:\n> ^^^^^^\n> Should we split those answers further, e.g. separating on-line\n> tutorials and guides, from on-line tips etc.?\n>\n>\n> === 24. Have you tried to get help regarding Git from other people? ===\n> (single choice)\n>\n>  * Yes\n>  * No\n>\n> === 25. If yes, did you get these problems resolved quickly and to your liking? ===\n> (single choice)\n>\n>  * Yes\n>  * No\n>  * Somewhat\n>\n> NOTES:\n> ^^^^^^\n> Those two questions are not very useful.  I think that they should be\n> removed from 2010 survey.\n>\n>\n> === 26. What channel(s) do you use to request help about git? ===\n> (multiple choice, with other)\n>\n>  + git mailing list (git@vger.kernel.org)\n>  + \"Git for Human Beings\" Google Group\n>  + msysGit mailing list / Google Group\n>  + IRC (#git)\n>  + IRC (other git/SCM related, e.g. #github)\n>  + request in blog post or on wiki\n>  + asking git guru/colleague\n>  + project mailing list, or IRC, or forum\n>  + Twitter or other microblogging platform\n>  + instant messaging (IM) like XMPP/Jabber\n>  + StackOverflow or other StackExchange site\n>\n>  + other (please specify)\n>\n> NOTES:\n> ^^^^^^\n> Are there any main channels of requesting help that I have missed in\n> the above list of answers?  What are they, and why do you think they\n> are important enought to warrant inclusion in above list?\n>\n>\n> === 27. Which communication channel(s) do you use? ===\n>        Do you read the mailing list, or watch IRC channel?\n> (multiple choice)\n>\n>  + git@vger.kernel.org (main)\n>  + Git for Human Beings (Google Group)\n>  + msysGit\n>  + #git IRC channel\n>  + #git-devel IRC channel\n>  + #github or #gitorious IRC channel\n>  + #revctrl IRC channel\n>\n> NOTES:\n> ^^^^^^\n> Are there any communication channels that I have missed?  For example\n> is there a separate channel that JGit/EGit developers use?\n>\n>\n> == About this survey. Open forum. ==\n>\n> === 28. How did you hear about this Git User's Survey? ===\n> (single choice, with other)\n>\n>  * git mailing list\n>  * git-related mailing list (e.g. msysGit)\n>  * mailing list or forum of some project\n>  * #git IRC channel topic\n>  * announcement on IRC channel\n>  * git homepage\n>  * git wiki\n>  * git hosting site (or blog related to such site)\n>  * software-related web site\n>  * news or social news site (e.g. Digg, Reddit)\n>  * blog (or blog planet)\n>  * other kind of web site\n>  * Twitter or other microblogging platform\n>\n>  * other - please specify\n>\n> NOTES:\n> ^^^^^^\n> This list would of course be updated to reflect the list of (planned)\n> announcement channels.\n>\n> There of course will be announcement on Git Mailing List, and perhaps\n> also on msysGit list / Google Group, and on Git For Human Beings\n> Google Group (if it exists).  I'll announce it on #git, and ask op to\n> put short announcement in channel description, and I can announce it\n> on other IRC channels.  I would add announcement to main page of Git\n> Wiki, and as Git Homepage administrator to put announcement about Git\n> User's Survey.\n>\n> I usually tried to contact administrators of git hosting sites,\n> including git.kernel.org, repo.or.cz, GitHub, Gitorious, Assembla,\n> Codebase and Unfuddle, asking them to put announcement about\n> Git User's Survey either somewhere on the site, or in their blog\n> (if there is any).  What git hosting sites it is worth to ask?\n>\n> Sidenote: I am thinking about contacting different git hosting sites\n> _before_ staring survey, asking them (them = administrators) about\n> what questions would they like to see.  Do you think thet it is good\n> idea?\n>\n> Should I try to post announcement on mailing list for projects that\n> use git?  There are entirely too many such projects nowadays, and such\n> announcement can be considered spamming by some...\n>\n> I would like to have announcement of Git User's Survey 2010 at\n> LWN.net, but this would need to be send at least two weeks in advance,\n> if I remember correctly.  Is it worth it?  What other news site should\n> I (or you) send announcement to?\n>\n> If you can Digg / Reddit announcment on some site, please do.  I can\n> announce Git User's Survey 2-1- at Twitter, Identi.ca and Plurk, but I\n> don't have wide area of followers.  So please RT.\n>\n> Should we contact some bloggers (besides asking Junio to put\n> announcement on his blog) to post an anouncement?  Which bloggers\n> would respond positively (perhaps Linus...)?\n>\n> --\n> Jakub Narebski\n> Poland\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>\n"},{"id":"144777","messageId":"201007041314.50591.jnareb@gmail.com","threadId":"24279","inReplyTo":"AANLkTimbpOEpi8QOqTOMav0whmLeHz3vQq_0KDnblRIK@mail.gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-07-04T11:14:45Z","receivedAt":"2010-07-04T11:14:45Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"On Sun, 4 July 2010, David Bainbridge wrote:\n\n> First, as someone working in a company that is adopting Git can I say\n> that I found the results of previous surveys useful? So I think that\n> these surveys should continue :-)\n\nThank you very much for the words of encouragement.\n\n> I think that the reduction of free text fields is good ... I am\n> concerned that if I point several hundred users at the this survey and\n> encourage them to respond that you should not get swamped!\n\nI had idea of running some kind of natural text processing analyser\nfor analysis of free-form responses[1], but nothing came out of this\n(currently).\n\n[1]:http://stackoverflow.com/questions/887954/how-to-categorize-and-tabularize-free-form-answers-to-a-question-in-a-survey\n\n> \n> The surveys are actually useful for making people more aware of what\n> Git can do, and the other tools associated with Git, so this is\n> something of bear in mind.\n\nWell, this year there is no question about how often one uses specified\ngit commands.  In my opinion it made responding to survey too long, and\nit was not balanced by people learning about new commands, I don't\nthink.\n\n> Have you considered the question: 'How long have you been using Git?'.\n> This combined the expertise level might yield some useful information,\n> and could provide some weighting for the 'Getting started' questions\n> too. There are some problems with the question in that it could be,\n> say, 2 years intermittent use, or 2 years continuous use, and these\n> are different, of course.\n\nWell, such question was replaced by the question about one's own\nproficiency in Git in 2009 survey (IIRC).\n\n> > === 06. Rate your own proficiency with Git: ===\n> > (single choice)\n> >\n> >  * 1. novice\n> >  * 2. casual, needs advice\n> >  * 3. everyday use\n> >  * 4. can offer advice\n> >  * 5. know it very well\n\nThe problem with question \"How long have you been using Git?\" (beside\nwhat you have mentioned) is that it is hard to answer correctly / in\ndetail for longer times.\n\nPerhaps something like this:\n\n=== xx. How long have you been using Git? ===\n(single choice, with other)\n\n * less than week\n * between a week and a month\n * a few months\n * a few years\n * duration (please give units)\n\nWhat do you think?\n\n> The demographic information is useful if you want to understand\n> whether Git is (for example) considered less usable in countries where\n> English is not the native language. But then if you want to know the\n> native language of the user rather than where they live then perhaps\n> this should be asked? (I was born in the UK, but now live in Sweden\n> ... so I am perhaps more conscious of this!). Where you are born does\n> not necessarily identify your native language either.\n\nThe problem with this question in the past was twofold: first, people\nsometimes mistok it for question about _programming languages.  Second\nshould this question be about primary language / languages, or about\nlanguage ones prefer the computer to communicate with?\n \n> Do you want to separate work usage and 'non-work' usage at all? The\n> two experiences may be completely different. If I am working at home I\n> can use what ever I want, and work how I want. This will probably not\n> be the case in a corporate environment, so I would report one set of\n> results for 'work' and another for 'non-work'. This could generate two\n> survey returns for a single user. Is this intended?\n\nHmmmm... food for though.  It can be mentioned somewhere close to\nbeginning that one can fill this survey more than once (from different\ncomputers if using default version with cookies) for different roles\none plays.  Perhaps with checkbox \"additional role\" (aka. \"I have already\nfiled this survey\" ;-))...\n \n\n> Just a couple of thoughts :-)\n\nThanks a lot for your comments.  I appreciate it.\n\n-- \nJakub Narebski\nPoland\n"},{"id":"144783","messageId":"AANLkTim0HypdTEwsTUQ-G8C3mAoZ-7Ro3zB4z7-hpFq2@mail.gmail.com","threadId":"24279","inReplyTo":"201007041314.50591.jnareb@gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"David Bainbridge","fromEmail":"david.bainbridge@gmail.com","sentAt":"2010-07-04T20:48:45Z","receivedAt":"2010-07-04T20:48:45Z","isPatch":false,"sender":{"key":"david.bainbridge@gmail.com","avatar":"https://gravatar.com/avatar/1689d4383c7d0d399e2803ddbbecf83b7a4cb9bff89f45917e28b351933ccef1?d=mp&s=160"},"body":"Hi Jakub,\n\nIt sounds like I was revisiting old territory in some cases :-)\n\nThe thoughts about free text analysis were interesting though ...\n\nOn 4 July 2010 13:14, Jakub Narebski <jnareb@gmail.com> wrote:\n> On Sun, 4 July 2010, David Bainbridge wrote:\n>\n>> Have you considered the question: 'How long have you been using Git?'.\n>> This combined the expertise level might yield some useful information,\n>> and could provide some weighting for the 'Getting started' questions\n>> too. There are some problems with the question in that it could be,\n>> say, 2 years intermittent use, or 2 years continuous use, and these\n>> are different, of course.\n>\n> Well, such question was replaced by the question about one's own\n> proficiency in Git in 2009 survey (IIRC).\n>\n>> > === 06. Rate your own proficiency with Git: ===\n>> > (single choice)\n>> >\n>> >  * 1. novice\n>> >  * 2. casual, needs advice\n>> >  * 3. everyday use\n>> >  * 4. can offer advice\n>> >  * 5. know it very well\n>\n> The problem with question \"How long have you been using Git?\" (beside\n> what you have mentioned) is that it is hard to answer correctly / in\n> detail for longer times.\n>\n> Perhaps something like this:\n>\n> === xx. How long have you been using Git? ===\n> (single choice, with other)\n>\n>  * less than week\n>  * between a week and a month\n>  * a few months\n>  * a few years\n>  * duration (please give units)\n>\n> What do you think?\n\nI think that the granularity is about right. I think we could imagine\nwhere we would expect people to be proficiency-wise with those\nperiods. Not sure about the last option ... You have everything from\ndays, to weeks to months to years in the main options. What did you\nhave in mind?\n\n>\n>> The demographic information is useful if you want to understand\n>> whether Git is (for example) considered less usable in countries where\n>> English is not the native language. But then if you want to know the\n>> native language of the user rather than where they live then perhaps\n>> this should be asked? (I was born in the UK, but now live in Sweden\n>> ... so I am perhaps more conscious of this!). Where you are born does\n>> not necessarily identify your native language either.\n>\n> The problem with this question in the past was twofold: first, people\n> sometimes mistok it for question about _programming languages.  Second\n> should this question be about primary language / languages, or about\n> language ones prefer the computer to communicate with?\n\nObviously you have been though this loop before! But perhaps if you\nare using drop-down lists then this makes it obvious what is required.\nI guess both the programming language, and the preferred interaction\nlanguage could be relevant.\n\nWe may want to know whether Git is more 'acceptable' to the Java\ncommunity or the C/C++ community for example, or whether certain\nsuggestions for improvement are coming from a community around a\nparticular language.\n\nThen with the human languages this could drive the localization of the\ncommands, as well as the documentation localization. Interesting ...\n\n>\n>> Do you want to separate work usage and 'non-work' usage at all? The\n>> two experiences may be completely different. If I am working at home I\n>> can use what ever I want, and work how I want. This will probably not\n>> be the case in a corporate environment, so I would report one set of\n>> results for 'work' and another for 'non-work'. This could generate two\n>> survey returns for a single user. Is this intended?\n>\n> Hmmmm... food for though.  It can be mentioned somewhere close to\n> beginning that one can fill this survey more than once (from different\n> computers if using default version with cookies) for different roles\n> one plays.  Perhaps with checkbox \"additional role\" (aka. \"I have already\n> filed this survey\" ;-))...\n>\n\nThats sounds reasonable ... I think it is probably useful to capture a\nuser-role response. The priorities of users and their needs may be\ncompletely different in a work situation.\n\n>\n>> Just a couple of thoughts :-)\n>\n> Thanks a lot for your comments.  I appreciate it.\n\nNo problem ... I will have another read through your original mail and\nsee if there is anything else!\n\nAll the best,\n\nDavid Bainbridge\nSweden\n> --\n> Jakub Narebski\n> Poland\n>\n"},{"id":"144787","messageId":"AANLkTik1JCMTSlzeKfkAChkrJGq_KeAOqy7iGkMtKsR8@mail.gmail.com","threadId":"24279","inReplyTo":"201007032158.57700.jnareb@gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Scott Chacon","fromEmail":"schacon@gmail.com","sentAt":"2010-07-04T22:43:49Z","receivedAt":"2010-07-04T22:43:49Z","isPatch":false,"sender":{"key":"schacon@gmail.com","avatar":"https://gravatar.com/avatar/9b13a8a078e1dcf8588c4eea9554445d51ebed6c41b51f56f4d96738130b05c6?d=mp&s=160"},"body":"Hey,\n\n2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n> === 09. On which operating system(s) do you use Git? ===\n> (multiple choice, with other)\n>\n>  + Linux (includes MeeGo and Moblin)\n>  + MacOS X (Darwin)\n>  + MS Windows/msysGit (MINGW)\n>  + MS Windows/Cygwin\n>  + FreeBSD, OpenBSD, NetBSD, etc.\n>  + other Unix\n>\n>  + iPhone OS\n>  + Android\n>  + WebOS\n>\n>  + Other, please specify\n>\n> NOTES:\n> ^^^^^^\n> The iPhone OS, Androind and WebOS answers are new this year.\n> OpenSolaris died, so I removed it.  I wonder if it is worth it to\n> differentiate between MS Windows/msysGit and MS Windows/Cygwin, or if\n> we should just have one, single 'MS Windows' choice.\n\nAre any of these new options relevant?  I'm pretty sure there is no\nworking Git implementation in iOS, Android or WebOS.  Why were they\nadded?  There are some libraries for iOS, but I'm pretty involved in\nalmost all of them and as far as I know you can't really do anything\ninteresting with them yet.  And I'm pretty sure Android and certainly\nWebOS don't have working implementations yet either.\n\nScott\n"},{"id":"144788","messageId":"201007050148.51549.jnareb@gmail.com","threadId":"24279","inReplyTo":"AANLkTik1JCMTSlzeKfkAChkrJGq_KeAOqy7iGkMtKsR8@mail.gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-07-04T23:48:45Z","receivedAt":"2010-07-04T23:48:45Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"On Mon, 5 Jul 2010, Scott Chacon wrote:\n> 2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n> > === 09. On which operating system(s) do you use Git? ===\n> > (multiple choice, with other)\n> >\n> >  + Linux (includes MeeGo and Moblin)\n> >  + MacOS X (Darwin)\n> >  + MS Windows/msysGit (MINGW)\n> >  + MS Windows/Cygwin\n> >  + FreeBSD, OpenBSD, NetBSD, etc.\n> >  + other Unix\n> >\n> >  + iPhone OS\n> >  + Android\n> >  + WebOS\n> >\n> >  + Other, please specify\n> >\n> > NOTES:\n> > ^^^^^^\n> > The iPhone OS, Androind and WebOS answers are new this year.\n> > OpenSolaris died, so I removed it.  I wonder if it is worth it to\n> > differentiate between MS Windows/msysGit and MS Windows/Cygwin, or if\n> > we should just have one, single 'MS Windows' choice.\n> \n> Are any of these new options relevant?  I'm pretty sure there is no\n> working Git implementation in iOS, Android or WebOS.  Why were they\n> added?  There are some libraries for iOS, but I'm pretty involved in\n> almost all of them and as far as I know you can't really do anything\n> interesting with them yet.  And I'm pretty sure Android and certainly\n> WebOS don't have working implementations yet either.\n\nI have added those because (perhaps by mistake or misunderstanding)\nthere were a few such answers in 'other' operating system answer.\n\n-- \nJakub Narebski\nPoland\n"},{"id":"144800","messageId":"201007050919.01490.jnareb@gmail.com","threadId":"24279","inReplyTo":"AANLkTim0HypdTEwsTUQ-G8C3mAoZ-7Ro3zB4z7-hpFq2@mail.gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-07-05T07:19:00Z","receivedAt":"2010-07-05T07:19:00Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"On Sun, 4 July 2010, David Bainbridge wrote:\n\n> It sounds like I was revisiting old territory in some cases :-)\n\nNevertheless the discussion is interesting.\n> \n> The thoughts about free text analysis were interesting though ...\n\nSidenote: analysis of free-form questions and of 'other, please specify'\nresponses was done with the help of program anyway.  But it only did\ncounting, and you had to categorize by hand.\n> \n> On 4 July 2010 13:14, Jakub Narebski <jnareb@gmail.com> wrote:\n>> On Sun, 4 July 2010, David Bainbridge wrote:\n>>\n>>> Have you considered the question: 'How long have you been using Git?'.\n>>> This combined the expertise level might yield some useful information,\n>>> and could provide some weighting for the 'Getting started' questions\n>>> too. There are some problems with the question in that it could be,\n>>> say, 2 years intermittent use, or 2 years continuous use, and these\n>>> are different, of course.\n>>\n>> Well, such question was replaced by the question about one's own\n>> proficiency in Git in 2009 survey (IIRC).\n>>\n>>>> === 06. Rate your own proficiency with Git: ===\n>>>> (single choice)\n>>>>\n>>>>  * 1. novice\n>>>>  * 2. casual, needs advice\n>>>>  * 3. everyday use\n>>>>  * 4. can offer advice\n>>>>  * 5. know it very well\n>>\n>> The problem with question \"How long have you been using Git?\" (beside\n>> what you have mentioned) is that it is hard to answer correctly / in\n>> detail for longer times.\n>>\n>> Perhaps something like this:\n>>\n>> === xx. How long have you been using Git? ===\n>> (single choice, with other)\n>>\n>>  * less than week\n>>  * between a week and a month\n>>  * a few months\n>>  * a few years\n>>  * duration (please give units)\n    * I don't remember\n>>\n>> What do you think?\n> \n> I think that the granularity is about right. I think we could imagine\n> where we would expect people to be proficiency-wise with those\n> periods. Not sure about the last option ... You have everything from\n> days, to weeks to months to years in the main options. What did you\n> have in mind?\n\nScratch last option.  What I had in mind that when people more or less\nremember when the started using git, they could write e.g. \"7 weeks\",\nor \"5 months\".  Let's leave only pre-defined answers... but leave\nquestion about proficiency in git too; this would help distinguish\nbetween continuous use and sporadic (intermittent) use.\n\n>>> The demographic information is useful if you want to understand\n>>> whether Git is (for example) considered less usable in countries where\n>>> English is not the native language. But then if you want to know the\n>>> native language of the user rather than where they live then perhaps\n>>> this should be asked? (I was born in the UK, but now live in Sweden\n>>> ... so I am perhaps more conscious of this!). Where you are born does\n>>> not necessarily identify your native language either.\n>>\n>> The problem with this question in the past was twofold: first, people\n>> sometimes mistok it for question about _programming languages.  Second\n>> should this question be about primary language / languages, or about\n>> language ones prefer the computer to communicate with?\n> \n> Obviously you have been though this loop before! But perhaps if you\n> are using drop-down lists then this makes it obvious what is required.\n> I guess both the programming language, and the preferred interaction\n> language could be relevant.\n> \n> We may want to know whether Git is more 'acceptable' to the Java\n> community or the C/C++ community for example, or whether certain\n> suggestions for improvement are coming from a community around a\n> particular language.\n\nI can bring back the question about programming languages, with or\nwithout 'other, please specify' free-form answer.  I wonder about\nwording: should it be (as before) about being \"proficient\" in the\nprogramming language, or about simply \"using with git\"?  Should it\nperhaps be matrix form, asking about proficiency in given programming\nlanguage?\n \n> Then with the human languages this could drive the localization of the\n> commands, as well as the documentation localization. Interesting ...\n\nYes, it would be interesting, as the localization is back (!) thanks\nto Ævar's work on adding i18n infrastructure to git (C, shell, Perl)\nfor localizing command messages.\n\nIf this question is back, then perhaps also question about what\none would like to have localized: GUI tools (gitk, git-gui - they\nare localized, but perhaps not in one's preferred language), command\nmessages (porcelain), documentation i.e. manpages (here for us is\na question about technology to use), commit message templates\n(e.g. \"Merge foo into bar\", \"Revert nnn\").  Have I missed something?\n\nBy the way, the important question is also which questions to remove,\nnot only what questions to add.\n\n>>> Do you want to separate work usage and 'non-work' usage at all? The\n>>> two experiences may be completely different. If I am working at home I\n>>> can use what ever I want, and work how I want. This will probably not\n>>> be the case in a corporate environment, so I would report one set of\n>>> results for 'work' and another for 'non-work'. This could generate two\n>>> survey returns for a single user. Is this intended?\n>>\n>> Hmmmm... food for though.  It can be mentioned somewhere close to\n>> beginning that one can fill this survey more than once (from different\n>> computers if using default version with cookies) for different roles\n>> one plays.  Perhaps with checkbox \"additional role\" (aka. \"I have already\n>> filed this survey\" ;-))...\n> \n> Thats sounds reasonable ... I think it is probably useful to capture a\n> user-role response. The priorities of users and their needs may be\n> completely different in a work situation.\n\nWell, the version with specifying roles might be overly complicated.\nI think it would be enough to have checkbox saying\n\n  I have already filled this survey in different role\n\nto catch number of responders as opposed to number of responses.\n\n-- \nJakub Narebski\nPoland\n"},{"id":"145016","messageId":"loom.20100707T105938-93@post.gmane.org","threadId":"24279","inReplyTo":"201007041013.40563.jnareb@gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Yann Dirson","fromEmail":"ydirson@free.fr","sentAt":"2010-07-07T09:18:55Z","receivedAt":"2010-07-07T09:18:55Z","isPatch":false,"sender":{"key":"ydirson@free.fr","avatar":null},"body":"Jakub Narebski <jnareb <at> gmail.com> writes:\n> === xx. Have you found distributed version control easy? ===\n> (multiple choice)\n> \n>  + Very easy\n>  + Easy\n>  + Reasonably easy\n>  + Hard\n>  + Very hard\n> \n> Or something like that, with separate question if DVCS is difficult\n> or not.\n> \n> Alternatively we could ask about _relative_ ease of learning / use.\n> But I don't think this would go well (and I don't think we could get\n> good answers from that).\n\nRelated to that, would be whether the user was familiar with DVCS before\nstarting to use git, or even familiar with VCS - the answers would be different\nfor people for whom git is the first VCS they ever used, or for people having\nused other DVCS before...\n\n> Well, Git User's Surveys always served more or less accidentally as\n> the source of information about git and git community (\"we have wiki?\"\n> from the first survey )\n\nCount me in for \"we have git new-worktree ?\" :)\nIn fact, I found nothing by that name in git's tree or in the wiki's\nInterfacesFrontendsAndTools.  Google finally pointed me to contrib/ where I\nnoticed workdir/git-new-workdir.\n\nIt may be worth to use a URL for publicizing non-mainstream stuff.  That's\nbetter as publicizing goes, and makes it easy to crowdsource discovery of\nmistakes or outdated things.\n"},{"id":"145017","messageId":"loom.20100707T112304-178@post.gmane.org","threadId":"24279","inReplyTo":"201007032158.57700.jnareb@gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Yann Dirson","fromEmail":"ydirson@free.fr","sentAt":"2010-07-07T12:28:46Z","receivedAt":"2010-07-07T12:28:46Z","isPatch":false,"sender":{"key":"ydirson@free.fr","avatar":null},"body":"Jakub Narebski <jnareb <at> gmail.com> writes:\n\n> === 07. I use Git for (check all that apply): ===\n[...]\n>  + work projects\n>  + unpaid projects\n\n\"Unpaid\" could be further split between personnal use, cooperating in\npublic projects (includes \"OSS development\" below), working for NGO's\nand the like.\n\n> === 08. How do/did you obtain Git (install and/or upgrade)? ===\n> (multiple choice, with other)\n[...]\n> Description:\n> ~~~~~~~~~~~~\n> Explanation: \"binary package\" covers pre-compiled binary (e.g.  from\n> rpm or deb binary packages); \"source package\" covers things like\n> deb-src and SRPMS / *.src.rpm; \"source script\" is meant to cover\n> installation in source-based distributions, like 'emerge' in Gentoo.\n\nDo we care about particular binary packages, like distro-provided,\ndistro backports, RPMs for kernel.org and similar \"official as in\nlisted on git-scm.org\" packages, 3rd-party packages (maybe with\n\"please specify\").\n\n> === 09. On which operating system(s) do you use Git? ===\n[...]\n> OpenSolaris died, so I removed it.\n\nIt does not seem to have died, only \"free-beer solaris\" seems to -\nopensolaris.org still shows activity.  And even so, people may still\nhave been using machines installed with it.\n\n\n> === 11. What Git interfaces and frontends do you use? ===\n[...]\n> The problem with split part is that people can have troubls with\n> distinguising between interfaces, implementations, frontends and tools\n> (although \"I don't know ...\"  answer should, I think, help here).  The\n> problem with having it everything together is that the list of\n> possible answers gets long and a bit unwieldy.\n\n\"interface\" is confusing, as shown by the need for \"I only use\n(graphical) tools\".  Use \"command-line interfaces and frontends\"\ninstead ?\n\n\n> === 12. What kind of Git tools do you use? ===\n> (multiple choice, with other)\n[...]\n>  + graphical blame or pickaxe tool\n\nMention gitk as example here ?\n\n> === 16. Which of the following features do you use? ===\n> (multiple choice, with other)\n[...]\n>  + one-way interaction with other SCMs (from SCM to git)\n\nOne-way from git to other SCM ?  I'm sure we care if many people do that :)\n\n> === 17. Which of the following features would you like to see implemented in\ngit? ===\n\n+ sophisticated diffcore stages (eg. directory rename, indent detection,\n  content move)\n\n> What features should be mentioned besides those above?  What criteria\n> should we have for including features in this list?\n\nNot sure if any reasonable idea that appeared on the list should be\nleft out.  Answers would provide feedback for features not necessarily\ninteresting to the average git@vger reader, but still appealing to our\nusers.\n\n\n> === 22. How do you compare the current version with the version from one year\nago? ===\n[...]\n> This question was mainly excuse for providing list of main changes\n> from the year ago.  I think that this question should be removed, as\n> it doesn't bring any important information.\n\nIt still says whether the work done on dev side is seen as valuable by\nend users.\n\n> === 23. How useful have you found the following forms of Git documentation? ===\n[...]\n>  + on-line help\n\nSpell as \"online\" ?  At least I had difficulties to parse it :)\n\n\n> === 28. How did you hear about this Git User's Survey? ===\n> (single choice, with other)\n\n+ relaying by co-workers bridging the team to the community\n\nHTH,\n-- \nYann\n"},{"id":"145059","messageId":"m3k4p7m0sv.fsf@localhost.localdomain","threadId":"24279","inReplyTo":"loom.20100707T112304-178@post.gmane.org","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-07-07T21:37:36Z","receivedAt":"2010-07-07T21:37:36Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Yann Dirson <ydirson@free.fr> writes:\n> Jakub Narebski <jnareb <at> gmail.com> writes:\n> \n> > === 07. I use Git for (check all that apply): ===\n> [...]\n> >  + work projects\n> >  + unpaid projects\n> \n> \"Unpaid\" could be further split between personnal use, cooperating in\n> public projects (includes \"OSS development\" below), working for NGO's\n> and the like.\n\n\"Unpaid projects\" simply means here not work (related).  I am not sure\nif adding other options is worth it; I'd rather not have too many\npossibile answers for a question.\n \n> > === 08. How do/did you obtain Git (install and/or upgrade)? ===\n> > (multiple choice, with other)\n> [...]\n> > Description:\n> > ~~~~~~~~~~~~\n> > Explanation: \"binary package\" covers pre-compiled binary (e.g.  from\n> > rpm or deb binary packages); \"source package\" covers things like\n> > deb-src and SRPMS / *.src.rpm; \"source script\" is meant to cover\n> > installation in source-based distributions, like 'emerge' in Gentoo.\n> \n> Do we care about particular binary packages, like distro-provided,\n> distro backports, RPMs for kernel.org and similar \"official as in\n> listed on git-scm.org\" packages, 3rd-party packages (maybe with\n> \"please specify\").\n\nNo, I don't think we do worry about this.\n \n> > === 09. On which operating system(s) do you use Git? ===\n> [...]\n> > OpenSolaris died, so I removed it.\n> \n> It does not seem to have died, only \"free-beer solaris\" seems to -\n> opensolaris.org still shows activity.  And even so, people may still\n> have been using machines installed with it.\n\nNevertheless it's install base, as shown by previous surveys, is IMVHO\ntoo small for it to have it as a separate option.\n \n> > === 11. What Git interfaces and frontends do you use? ===\n> [...]\n> > The problem with split part is that people can have troubls with\n> > distinguising between interfaces, implementations, frontends and tools\n> > (although \"I don't know ...\"  answer should, I think, help here).  The\n> > problem with having it everything together is that the list of\n> > possible answers gets long and a bit unwieldy.\n> \n> \"interface\" is confusing, as shown by the need for \"I only use\n> (graphical) tools\".  Use \"command-line interfaces and frontends\"\n> instead ?\n \nThat's a good idea.  Thanks.\n \n> > === 12. What kind of Git tools do you use? ===\n> > (multiple choice, with other)\n> [...]\n> >  + graphical blame or pickaxe tool\n> \n> Mention gitk as example here ?\n\nYou meant here \"git gui blame\", didn't you?\n\n> > === 16. Which of the following features do you use? ===\n> > (multiple choice, with other)\n> [...]\n> >  + one-way interaction with other SCMs (from SCM to git)\n> \n> One-way from git to other SCM ?  I'm sure we care if many people do that :)\n\nOne way from SCM to git.\n\n> > === 17. Which of the following features would you like to see implemented in\n> git? ===\n> \n> + sophisticated diffcore stages (eg. directory rename, indent detection,\n>   content move)\n\nThanks.\n\nBTW. I think wholesame directory rename detection is one of proposed\nfeatures already.\n\n> > What features should be mentioned besides those above?  What criteria\n> > should we have for including features in this list?\n> \n> Not sure if any reasonable idea that appeared on the list should be\n> left out.  Answers would provide feedback for features not necessarily\n> interesting to the average git@vger reader, but still appealing to our\n> users.\n\nI don't think ideas about _internal_ changes need to be here.  Also,\nI do not remember _every_ feature proposel that appeared on the list...\n \n> > === 22. How do you compare the current version with the version from one year\n> ago? ===\n> [...]\n> > This question was mainly excuse for providing list of main changes\n> > from the year ago.  I think that this question should be removed, as\n> > it doesn't bring any important information.\n> \n> It still says whether the work done on dev side is seen as valuable by\n> end users.\n\nEgo stroking ;-))))\n\nI'm not sure if it is worth having this question.  If there were any\nbig controversial changes, perhaps...\n\n> > === 23. How useful have you found the following forms of Git documentation? ===\n> [...]\n> >  + on-line help\n> \n> Spell as \"online\" ?  At least I had difficulties to parse it :)\n \nO.K.\n \n> > === 28. How did you hear about this Git User's Survey? ===\n> > (single choice, with other)\n> \n> + relaying by co-workers bridging the team to the community\n\nHmmm... good catch.\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"145062","messageId":"m3fwzvm0jc.fsf@localhost.localdomain","threadId":"24279","inReplyTo":"loom.20100707T105938-93@post.gmane.org","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-07-07T21:43:16Z","receivedAt":"2010-07-07T21:43:16Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Yann Dirson <ydirson@free.fr> writes:\n\n> Jakub Narebski <jnareb <at> gmail.com> writes:\n> > === xx. Have you found distributed version control easy? ===\n> > (multiple choice)\n> > \n> >  + Very easy\n> >  + Easy\n> >  + Reasonably easy\n> >  + Hard\n> >  + Very hard\n> > \n> > Or something like that, with separate question if DVCS is difficult\n> > or not.\n> > \n> > Alternatively we could ask about _relative_ ease of learning / use.\n> > But I don't think this would go well (and I don't think we could get\n> > good answers from that).\n> \n> Related to that, would be whether the user was familiar with DVCS before\n> starting to use git, or even familiar with VCS - the answers would be different\n> for people for whom git is the first VCS they ever used, or for people having\n> used other DVCS before...\n\nRelative ease of use of Git as compared to perceived ease of\ndistributed version control as generic subject.\n\nBut I don't think it is a good way to go (and get meaningfull\nanswers).\n \n> > Well, Git User's Surveys always served more or less accidentally as\n> > the source of information about git and git community (\"we have wiki?\"\n> > from the first survey )\n> \n> Count me in for \"we have git new-worktree ?\" :)\n> In fact, I found nothing by that name in git's tree or in the wiki's\n> InterfacesFrontendsAndTools.  Google finally pointed me to contrib/ where I\n> noticed workdir/git-new-workdir.\n> \n> It may be worth to use a URL for publicizing non-mainstream stuff.  That's\n> better as publicizing goes, and makes it easy to crowdsource discovery of\n> mistakes or outdated things.\n\nHmmm... perhaps it would be worth to create GitContrib page on Git\nWiki, and link it from InterfacesFrontendsAndTools page...\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"145096","messageId":"loom.20100708T091339-404@post.gmane.org","threadId":"24279","inReplyTo":"m3k4p7m0sv.fsf@localhost.localdomain","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Yann Dirson","fromEmail":"ydirson@free.fr","sentAt":"2010-07-08T07:24:34Z","receivedAt":"2010-07-08T07:24:34Z","isPatch":false,"sender":{"key":"ydirson@free.fr","avatar":null},"body":"Jakub Narebski <jnareb <at> gmail.com> writes:\n> > > === 12. What kind of Git tools do you use? ===\n> > > (multiple choice, with other)\n> > [...]\n> > >  + graphical blame or pickaxe tool\n> > \n> > Mention gitk as example here ?\n> \n> You meant here \"git gui blame\", didn't you?\n\nWell, yes - that comes from the fact I only use the it from gitk :)\n\n> > > === 16. Which of the following features do you use? ===\n> > > (multiple choice, with other)\n> > [...]\n> > >  + one-way interaction with other SCMs (from SCM to git)\n> > \n> > One-way from git to other SCM ?  I'm sure we care if many people do that :)\n> \n> One way from SCM to git.\n\nNo, I was really suggesting to ask whether people work on a remote git repo\nusing another VCS, much like we do access other VCS' repo using git.  Not sure\nwhether this survey would reach those users, though.\n\n \n> > + sophisticated diffcore stages (eg. directory rename, indent detection,\n> >   content move)\n> \n> Thanks.\n> \n> BTW. I think wholesame directory rename detection is one of proposed\n> features already.\n\nd'oh - how could I miss it :)\n\n\n> > > What features should be mentioned besides those above?  What criteria\n> > > should we have for including features in this list?\n> > \n> > Not sure if any reasonable idea that appeared on the list should be\n> > left out.  Answers would provide feedback for features not necessarily\n> > interesting to the average git <at> vger reader, but still appealing to our\n> > users.\n> \n> I don't think ideas about _internal_ changes need to be here.  Also,\n> I do not remember _every_ feature proposel that appeared on the list...\n\nAt some point[1] we had a volunteer secretary willing to take note of bugs.  I\njust went to see whether proposed features were tracked as well, but it appears\nthat initiative has stalled already :(\n\nhttp://marc.info/?l=git&m=126299754631066&w=4\n\nBest regards,\n-- \nYann\n"},{"id":"145270","messageId":"AANLkTilVAmImt7VefBlnmLunOjQyyRg5yp-3EgXXTnGX@mail.gmail.com","threadId":"24279","inReplyTo":"AANLkTilD8N6rnj9e3KzRB7_q3J0I4cJGx5EduX_UJScC@mail.gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2010-07-10T11:01:26Z","receivedAt":"2010-07-10T11:01:26Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Sun, Jul 4, 2010 at 3:21 AM, Ævar Arnfjörð Bjarmason\n<avarab@gmail.com> wrote:\n> 2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n>\n> This survey is good stuff. Some minor comments below.\n\nPlease remove the context of the mail you are not replying to.\n\nIt's very difficult to read otherwise.\n\n-- \nFelipe Contreras\n"},{"id":"145271","messageId":"AANLkTike2cKMtrHA12vsFjTI9MFne3oaRQoj1BQKoTrM@mail.gmail.com","threadId":"24279","inReplyTo":"201007032158.57700.jnareb@gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2010-07-10T11:31:33Z","receivedAt":"2010-07-10T11:31:33Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n> I guess it is time for annual (so far) Git User's Survey.  Should\n> there be one?  When should it start, and how long should it last?\n\nYes, I think there should definitely be one! IMO one month is enough.\n\n> With more that 3000 responses in 2008 and 2009 survey, analysing\n> free-form data was hard.  That is why in this proposal there is only\n> single one free-form response (about missing features).\n\nThat's a good idea.\n\n> == About you ==\n>\n> NOTES:\n> ^^^^^^\n> This section gives us a bit of demographical information about survey\n> responders.  Is it useful?  Should we leave it in survey, or remove it?\n>\n> Should we for example include 'gender' as one of questions?  Perl Survey\n> 2010 did.\n\nI don't see the point of 'gender'. What does that tells us?\n\n> === 02. How old are you (in years)? ===\n> (free-form single line)\n>\n> NOTES:\n> ^^^^^^\n> Instead of unconstrained free-form response it might be better to have\n> single choice (or menu) of age ranges.  What do you think?  Of course with\n> ranges there is question what ranges to use (how to quantize age); goo\n> solution would be to chose ranges corresponding somewhat to the levels of\n> education.\n\nWhat's wrong with a free-form? I think that's easy and it works.\n\n> === 10. What do you use to edit contents under version control with Git? ===\n>        What kind of editor, IDE or RAD you use working with Git?\n> (multiple choice, with other)\n[...]\n> NOTES:\n> ^^^^^^\n> Is this question useful, or should it be removed from survey?\n\nI think this is useful to correlate communities.\n\n> === 15. How do you publish/propagate your changes? ===\n> (multiple choice, with other)\n[...]\n> NOTES:\n> ^^^^^^\n> Should it stay, or should it be removed?  I guess it can be\n> interesting for git hosting sites...  Should we have separate answrs\n> for different kinds of push (ssh, \"dumb\" HTTP(S) with WebDAV, \"smart\"\n> HTTP - if it is possible, git:// protocol with push enabled)?\n\nI think this question should stay. It would also help projects to\ndecide how to accept patches based on what most git users are familiar\nwith.\n\n> === 16. Which of the following features do you use? ===\n> (multiple choice, with other)\n[...]\n> NOTES:\n> ^^^^^^\n> The problem is come up not with exhaustive list of features: there are\n> too many of them to list.  The problem is coming up with list of\n> important and used enough often features.\n>\n> So: what features should be included in this list?  What features\n> should be removed from above list of answers?\n\nI propose to add:\n + git stage/cache/index\n\nWe really are not sure how many people are actually aware of it, are we?\n\nAnd IMO new features should go on the top.\n\n> === 19. Overall, how happy are you with Git? ===\n> (single choice)\n[...]\n> NOTES:\n> ^^^^^^\n> I'm not sure if this question is at all useful.\n\nI think it is. Otherwise how do we know that people are happy with it?\n\n> === 20. In your opinion, which areas in Git need improvement? ===\n>        Please state your preference.\n> (matrix)\n[...]\n> NOTES:\n> ^^^^^^\n> Are there any general areas that are missing from this list?\n> What are they?\n\nHow about:\n + communication channels\n\nI think if users have trouble reporting issues, asking questions, we\nshould catch that.\n\n> === 22. How do you compare the current version with the version from one year ago? ===\n> (single choice)\n[...]\n> NOTES:\n> ^^^^^^\n> This question was mainly excuse for providing list of main changes\n> from the year ago.  I think that this question should be removed, as\n> it doesn't bring any important information.\n\nYeah, and I think many people don't even notice the changes as they\ncome, but learn slowly features that have been there since a long time\nago.\n\n> === 28. How did you hear about this Git User's Survey? ===\n> (single choice, with other)\n[...]\n> NOTES:\n> ^^^^^^\n> This list would of course be updated to reflect the list of (planned)\n> announcement channels.\n\n> Should I try to post announcement on mailing list for projects that\n> use git?  There are entirely too many such projects nowadays, and such\n> announcement can be considered spamming by some...\n\nI still maintain that we need an official blog (not planet). Last year\nthe most popular way of finding about the survey was through blog\nposts, but you argued that it was because you didn't spam mailing\nlists.\n\nhttp://article.gmane.org/gmane.comp.version-control.git/124609\n\nI still think it's unnecessary to spam mailing lists, but if it helps\nus reach considerably more people, we should do it.\n\nHopefully after this year's result we will know for sure ;)\n\nThanks for doing this. Cheers.\n\n-- \nFelipe Contreras\n"},{"id":"145279","messageId":"201007102158.25961.jnareb@gmail.com","threadId":"24279","inReplyTo":"AANLkTike2cKMtrHA12vsFjTI9MFne3oaRQoj1BQKoTrM@mail.gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-07-10T19:58:12Z","receivedAt":"2010-07-10T19:58:12Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"On Sat, 10 July 2010, Felipe Contreras wrote:\n> 2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n\n> > I guess it is time for annual (so far) Git User's Survey.  Should\n> > there be one?  When should it start, and how long should it last?\n> \n> Yes, I think there should definitely be one! IMO one month is enough.\n\nBy the way, I think it is important that Git User's Survey 2010 lasts\npast the holidays, i.e. into September or even October, even at the\ncost of lasting two months, and not one month.\n\nWhat do you think about this?\n\n> > == About you ==\n> >\n> > NOTES:\n> > ^^^^^^\n> > This section gives us a bit of demographical information about survey\n> > responders.  Is it useful?  Should we leave it in survey, or remove it?\n> >\n> > Should we for example include 'gender' as one of questions?  Perl Survey\n> > 2010 did.\n> \n> I don't see the point of 'gender'. What does that tells us?\n\nWell, one can say that 'age' doesn't tell us much either.\n\nSidenote: country of residence, besides giving a bit of demographical\ninformation, it also gives us information about where we could organize\nmini Git Together (beside the large one at Google, after GSoC Mentors\nSummit).  It would be even better if Survs.com provided Google Map \ngadget to mark point of residence... :-)\n \n> > === 02. How old are you (in years)? ===\n> > (free-form single line)\n> >\n> > NOTES:\n> > ^^^^^^\n> > Instead of unconstrained free-form response it might be better to have\n> > single choice (or menu) of age ranges.  What do you think?  Of course with\n> > ranges there is question what ranges to use (how to quantize age); goo\n> > solution would be to chose ranges corresponding somewhat to the levels of\n> > education.\n> \n> What's wrong with a free-form? I think that's easy and it works.\n\nO.K., I agree that it is not that hard to analyze free-form in this case.\n\n> > === 10. What do you use to edit contents under version control with Git? ===\n> >        What kind of editor, IDE or RAD you use working with Git?\n> > (multiple choice, with other)\n> [...]\n> > NOTES:\n> > ^^^^^^\n> > Is this question useful, or should it be removed from survey?\n> \n> I think this is useful to correlate communities.\n\nHmmm...\n\n> > === 15. How do you publish/propagate your changes? ===\n> > (multiple choice, with other)\n> [...]\n> > NOTES:\n> > ^^^^^^\n> > Should it stay, or should it be removed?  I guess it can be\n> > interesting for git hosting sites...  Should we have separate answrs\n> > for different kinds of push (ssh, \"dumb\" HTTP(S) with WebDAV, \"smart\"\n> > HTTP - if it is possible, git:// protocol with push enabled)?\n> \n> I think this question should stay. It would also help projects to\n> decide how to accept patches based on what most git users are familiar\n> with.\n\nAll right.\n\n> > === 16. Which of the following features do you use? ===\n> > (multiple choice, with other)\n> [...]\n> > NOTES:\n> > ^^^^^^\n> > The problem is come up not with exhaustive list of features: there are\n> > too many of them to list.  The problem is coming up with list of\n> > important and used enough often features.\n> >\n> > So: what features should be included in this list?  What features\n> > should be removed from above list of answers?\n> \n> I propose to add:\n>  + git stage/cache/index\n> \n> We really are not sure how many people are actually aware of it, are we?\n> \n> And IMO new features should go on the top.\n\nGood idea!\n\nThis and the next question about _proposed_ features are IMHO hardest\nto create well.\n\n> > === 19. Overall, how happy are you with Git? ===\n> > (single choice)\n> [...]\n> > NOTES:\n> > ^^^^^^\n> > I'm not sure if this question is at all useful.\n> \n> I think it is. Otherwise how do we know that people are happy with it?\n\nWell, I think there is rather heavy bias that if people are unhappy\nwith Git, they wouldn't be using it (well, unless they have to), and\nthey wouldn't be responding to this Git User's Survey (because they\ndidn't found it, for example).\n \n> > === 20. In your opinion, which areas in Git need improvement? ===\n> >        Please state your preference.\n> > (matrix)\n> [...]\n> > NOTES:\n> > ^^^^^^\n> > Are there any general areas that are missing from this list?\n> > What are they?\n> \n> How about:\n>  + communication channels\n> \n> I think if users have trouble reporting issues, asking questions, we\n> should catch that.\n\nO.K.\n\n  + communication channels (incl. requesting help)\n\n> > === 22. How do you compare the current version with the version from one year ago? ===\n> > (single choice)\n> [...]\n> > NOTES:\n> > ^^^^^^\n> > This question was mainly excuse for providing list of main changes\n> > from the year ago.  I think that this question should be removed, as\n> > it doesn't bring any important information.\n> \n> Yeah, and I think many people don't even notice the changes as they\n> come, but learn slowly features that have been there since a long time\n> ago.\n\nO.K.  I think that Git matured enough that improvements are not of the\nkind that make usable out of unusable (or vice versa).\n\nO'd remove this question, then.\n\n> > === 28. How did you hear about this Git User's Survey? ===\n> > (single choice, with other)\n> [...]\n> > NOTES:\n> > ^^^^^^\n> > This list would of course be updated to reflect the list of (planned)\n> > announcement channels.\n> \n> > Should I try to post announcement on mailing list for projects that\n> > use git?  There are entirely too many such projects nowadays, and such\n> > announcement can be considered spamming by some...\n> \n> I still maintain that we need an official blog (not planet). Last year\n> the most popular way of finding about the survey was through blog\n> posts, but you argued that it was because you didn't spam mailing\n> lists.\n> \n> http://article.gmane.org/gmane.comp.version-control.git/124609\n> \n> I still think it's unnecessary to spam mailing lists, but if it helps\n> us reach considerably more people, we should do it.\n> \n> Hopefully after this year's result we will know for sure ;)\n\nWell, there is Junio's blog, there is GitHub blog, and there is\nhttp://gitlog.wordpress.com/\n\nWell, let's spam mailing lists in the name od \"science\"! ;-))))\n\n-- \nJakub Narebski\nPoland\n"},{"id":"145322","messageId":"AANLkTikQF_tMHz28k2pdpVdtbnE6EDZiKQbwmMTlp-c9@mail.gmail.com","threadId":"24279","inReplyTo":"201007102158.25961.jnareb@gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2010-07-11T09:57:13Z","receivedAt":"2010-07-11T09:57:13Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Sat, Jul 10, 2010 at 10:58 PM, Jakub Narebski <jnareb@gmail.com> wrote:\n> On Sat, 10 July 2010, Felipe Contreras wrote:\n>> 2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n>\n>> > I guess it is time for annual (so far) Git User's Survey.  Should\n>> > there be one?  When should it start, and how long should it last?\n>>\n>> Yes, I think there should definitely be one! IMO one month is enough.\n>\n> By the way, I think it is important that Git User's Survey 2010 lasts\n> past the holidays, i.e. into September or even October, even at the\n> cost of lasting two months, and not one month.\n>\n> What do you think about this?\n\nMy feeling is that the longer it is, the easier it's for people to\npostpone it, and then forget about it.\n\nBut I don't have a strong opinion either way.\n\n>> > == About you ==\n>> >\n>> > NOTES:\n>> > ^^^^^^\n>> > This section gives us a bit of demographical information about survey\n>> > responders.  Is it useful?  Should we leave it in survey, or remove it?\n>> >\n>> > Should we for example include 'gender' as one of questions?  Perl Survey\n>> > 2010 did.\n>>\n>> I don't see the point of 'gender'. What does that tells us?\n>\n> Well, one can say that 'age' doesn't tell us much either.\n\nI disagree. I think younger people, specially the ones who have not\nbeen tainted by CVS, might find git easier to learn. Without this\nquestion it's not possible to find that correlation.\n\n>> > === 10. What do you use to edit contents under version control with Git? ===\n>> >        What kind of editor, IDE or RAD you use working with Git?\n>> > (multiple choice, with other)\n>> [...]\n>> > NOTES:\n>> > ^^^^^^\n>> > Is this question useful, or should it be removed from survey?\n>>\n>> I think this is useful to correlate communities.\n>\n> Hmmm...\n\nSorry, I thought the answers would be the actual application used:\nVim, Eclipse, MS Visual Studio, etc. If not, then I don't see the\npoint.\n\nAt least I remember finding out that most people use vim in some\nprevious survey, and I found that interesting.\n\n>> > === 19. Overall, how happy are you with Git? ===\n>> > (single choice)\n>> [...]\n>> > NOTES:\n>> > ^^^^^^\n>> > I'm not sure if this question is at all useful.\n>>\n>> I think it is. Otherwise how do we know that people are happy with it?\n>\n> Well, I think there is rather heavy bias that if people are unhappy\n> with Git, they wouldn't be using it (well, unless they have to), and\n> they wouldn't be responding to this Git User's Survey (because they\n> didn't found it, for example).\n\nThere's people that would rather be using something else for various\nreasons, but need to use git. Also, there's people that think that git\nis the best option, but not particularly ecstatic with it.\n\n-- \nFelipe Contreras\n"},{"id":"145331","messageId":"201007111942.54847.jnareb@gmail.com","threadId":"24279","inReplyTo":"AANLkTikQF_tMHz28k2pdpVdtbnE6EDZiKQbwmMTlp-c9@mail.gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-07-11T17:42:52Z","receivedAt":"2010-07-11T17:42:52Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"On Sun, 11 Jul 2010, Felipe Contreras wrote:\n> On Sat, Jul 10, 2010 at 10:58 PM, Jakub Narebski <jnareb@gmail.com> wrote:\n>> On Sat, 10 July 2010, Felipe Contreras wrote:\n>>> 2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n>>>>\n>>>> I guess it is time for annual (so far) Git User's Survey.  Should\n>>>> there be one?  When should it start, and how long should it last?\n>>>\n>>> Yes, I think there should definitely be one! IMO one month is enough.\n>>\n>> By the way, I think it is important that Git User's Survey 2010 lasts\n>> past the holidays, i.e. into September or even October, even at the\n>> cost of lasting two months, and not one month.\n>>\n>> What do you think about this?\n> \n> My feeling is that the longer it is, the easier it's for people to\n> postpone it, and then forget about it.\n\nHmmm... I haven't thought about this issue.  I certainly don't plan\nfor Git User's Survey 2010 to last longer than 2 months.  We can\nalways send / post reminders that the survey is coming to be closed.\n\nThe problem with duration of last year survey was that some announcements\ngot delayed because of holidays.\n\n> But I don't have a strong opinion either way.\n\nI think that 15 August to 15 September, or to 15 October would be\ngood time (this is currently preliminary only).\n\n>>>> == About you ==\n>>>>\n>>>> NOTES:\n>>>> ^^^^^^\n>>>> This section gives us a bit of demographical information about survey\n>>>> responders.  Is it useful?  Should we leave it in survey, or remove it?\n>>>>\n>>>> Should we for example include 'gender' as one of questions?  Perl Survey\n>>>> 2010 did.\n>>>\n>>> I don't see the point of 'gender'. What does that tells us?\n>>\n>> Well, one can say that 'age' doesn't tell us much either.\n> \n> I disagree. I think younger people, specially the ones who have not\n> been tainted by CVS, might find git easier to learn. Without this\n> question it's not possible to find that correlation.\n\nO.K., you convinced me: I'll leave age, but not add gender.\n \n>>>> === 10. What do you use to edit contents under version control with Git? ===\n>>>>        What kind of editor, IDE or RAD you use working with Git?\n>>>> (multiple choice, with other)\n>>> [...]\n>>>> NOTES:\n>>>> ^^^^^^\n>>>> Is this question useful, or should it be removed from survey?\n>>>\n>>> I think this is useful to correlate communities.\n>>\n>> Hmmm...\n> \n> Sorry, I thought the answers would be the actual application used:\n> Vim, Eclipse, MS Visual Studio, etc. If not, then I don't see the\n> point.\n> \n> At least I remember finding out that most people use vim in some\n> previous survey, and I found that interesting.\n\nThe problem is with not going overboard with number of possible answers,\nbut we can always take results of previous survey as hint (though \nI don't remember if free-form questions are analyzed yet)/\n\n>>>> === 19. Overall, how happy are you with Git? ===\n>>>> (single choice)\n>>> [...]\n>>>> NOTES:\n>>>> ^^^^^^\n>>>> I'm not sure if this question is at all useful.\n>>>\n>>> I think it is. Otherwise how do we know that people are happy with it?\n>>\n>> Well, I think there is rather heavy bias that if people are unhappy\n>> with Git, they wouldn't be using it (well, unless they have to), and\n>> they wouldn't be responding to this Git User's Survey (because they\n>> didn't found it, for example).\n> \n> There's people that would rather be using something else for various\n> reasons, but need to use git. Also, there's people that think that git\n> is the best option, but not particularly ecstatic with it.\n\nAll right, let's keep it.\n\n-- \nJakub Narebski\nPoland\n"},{"id":"145355","messageId":"AANLkTimenfNbx0rfKV26xzhyiw-Ccr0QzeO51Q3pKr3K@mail.gmail.com","threadId":"24279","inReplyTo":"201007111942.54847.jnareb@gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"David Bainbridge","fromEmail":"david.bainbridge@gmail.com","sentAt":"2010-07-12T10:14:41Z","receivedAt":"2010-07-12T10:14:41Z","isPatch":false,"sender":{"key":"david.bainbridge@gmail.com","avatar":"https://gravatar.com/avatar/1689d4383c7d0d399e2803ddbbecf83b7a4cb9bff89f45917e28b351933ccef1?d=mp&s=160"},"body":"Hi Jakub,\n\nSorry about disappearing ... I had a product release to deal with :-)\n\nSome interesting things have come up while I have been away.However,\nI have lost track of what the survey looks like now! Can we see the\ncurrent state somewhere?\n\nOn the question of spamming here is another aspect; if I send mail to\neveryone on a public list then it is spam. If I send a message to\neveryone at work asking them to respond then I am just doing my job.\nThe problem is how to address the unpaid volunteer sector of the open\nsource community without being perceived as spamming.\n\nRegards\n\nDavid Bainbridge\nSweden\n"},{"id":"145356","messageId":"AANLkTikZV5bTqQlsnksnX6rWrH_M8iTq5tEtHRdjohay@mail.gmail.com","threadId":"24279","inReplyTo":"AANLkTimenfNbx0rfKV26xzhyiw-Ccr0QzeO51Q3pKr3K@mail.gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2010-07-12T10:19:06Z","receivedAt":"2010-07-12T10:19:06Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Mon, Jul 12, 2010 at 1:14 PM, David Bainbridge\n<david.bainbridge@gmail.com> wrote:\n> On the question of spamming here is another aspect; if I send mail to\n> everyone on a public list then it is spam. If I send a message to\n> everyone at work asking them to respond then I am just doing my job.\n> The problem is how to address the unpaid volunteer sector of the open\n> source community without being perceived as spamming.\n\nNote that perhaps spamming is not the right word.\n\nI think the plan is to send the mail only to the communities that use\ngit, so chances are that many people would be interested on filling\nout the survey. It has been done in previous years, and I think nobody\ncomplained.\n\n-- \nFelipe Contreras\n"},{"id":"145357","messageId":"AANLkTina0oNDuZNEhAjQXcCNaqySPzFhLhNvb5TltVdz@mail.gmail.com","threadId":"24279","inReplyTo":"AANLkTikZV5bTqQlsnksnX6rWrH_M8iTq5tEtHRdjohay@mail.gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"David Bainbridge","fromEmail":"david.bainbridge@gmail.com","sentAt":"2010-07-12T10:22:42Z","receivedAt":"2010-07-12T10:22:42Z","isPatch":false,"sender":{"key":"david.bainbridge@gmail.com","avatar":"https://gravatar.com/avatar/1689d4383c7d0d399e2803ddbbecf83b7a4cb9bff89f45917e28b351933ccef1?d=mp&s=160"},"body":"OK, thanks for explaining Felipe,\n\nUsing development communities in this way makes sense.\n\nThanks\n\nDavid\n\nOn 12 July 2010 12:19, Felipe Contreras <felipe.contreras@gmail.com> wrote:\n> On Mon, Jul 12, 2010 at 1:14 PM, David Bainbridge\n> <david.bainbridge@gmail.com> wrote:\n>> On the question of spamming here is another aspect; if I send mail to\n>> everyone on a public list then it is spam. If I send a message to\n>> everyone at work asking them to respond then I am just doing my job.\n>> The problem is how to address the unpaid volunteer sector of the open\n>> source community without being perceived as spamming.\n>\n> Note that perhaps spamming is not the right word.\n>\n> I think the plan is to send the mail only to the communities that use\n> git, so chances are that many people would be interested on filling\n> out the survey. It has been done in previous years, and I think nobody\n> complained.\n>\n> --\n> Felipe Contreras\n>\n"},{"id":"147564","messageId":"AANLkTi=tmL66pe3pzgTYzopo=GnqDmHpPbvnicsUzN0m@mail.gmail.com","threadId":"24279","inReplyTo":"201007032158.57700.jnareb@gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2010-08-09T21:59:17Z","receivedAt":"2010-08-09T21:59:17Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n> I'm sorry for broken (badly wrapped) previous version...\n> ----\n>\n> I guess it is time for annual (so far) Git User's Survey.  Should\n> there be one?  When should it start, and how long should it last?\n\nYou might ind this useful:\nTop 10 Sites for Creating Surveys\nhttp://www.techlearning.com/article/31924\n\n-- \nFelipe Contreras\n"},{"id":"147694","messageId":"201008110016.28751.jnareb@gmail.com","threadId":"24279","inReplyTo":"AANLkTi=tmL66pe3pzgTYzopo=GnqDmHpPbvnicsUzN0m@mail.gmail.com","subject":"Re: [RFC] Git User's Survey 2010 (resend)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-08-10T22:16:27Z","receivedAt":"2010-08-10T22:16:27Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"On Mon, 9 Aug 2010, Felipe Contreras wrote:\n> 2010/7/3 Jakub Narebski <jnareb@gmail.com>:\n> >\n> > I guess it is time for annual (so far) Git User's Survey.  Should\n> > there be one?  When should it start, and how long should it last?\n> \n> You might ind this useful:\n> Top 10 Sites for Creating Surveys\n> http://www.techlearning.com/article/31924\n\nThanks for the link, but I think that at least for \"Git User's Survey \n2010\" I would stay with current Survs.com, as I have already entered \nsurvey there.  Thanks to Survs.com admins we have Premium plan since\nSurvs.com got out of beta, which would last to Sep 22, 2011, so it is\ngood for at least this year survey.\n\nOne short note about presented sites: Git User's Surveys needs more\nthan 1000 replies that is the limit for free plan for some of those\nsites, and IMHO a good survey needs more than 10 questions.  Also\nI very much prefer to have it possible to get the raw data out of\nsurvey site (as it was done with all Git User's Surveys, except the\nvery first one).\n\n-- \nJakub Narebski\nPoland\n"}]}