From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jakub Narebski Subject: [RFCv2] Questions for "Git User's Survey 2011" Date: Sat, 3 Sep 2011 03:43:54 +0200 Message-ID: <201109030343.55575.jnareb@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Cc: =?iso-8859-1?q?=C6var_Arnfj=F6r=F0_Bjarmason?= , Phil Hord , Jens Lehmann , Heiko Voigt To: git@vger.kernel.org X-From: git-owner@vger.kernel.org Sat Sep 03 03:44:16 2011 Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QzfHK-0001OE-Uw for gcvg-git-2@lo.gmane.org; Sat, 03 Sep 2011 03:44:15 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752836Ab1ICBoJ (ORCPT ); Fri, 2 Sep 2011 21:44:09 -0400 Received: from mail-fx0-f46.google.com ([209.85.161.46]:64893 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752377Ab1ICBoF (ORCPT ); Fri, 2 Sep 2011 21:44:05 -0400 Received: by fxh19 with SMTP id 19so2143174fxh.19 for ; Fri, 02 Sep 2011 18:44:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=zsTojvp26r6NaW9Jn7bNspV25Lo3xe8+/i6sb9YEqEE=; b=EtrlenvHc3OYbmRSePd09FB+7YJ5bOV8Y75I4gGcg2Wnl5HftFyaW7+JD11VchJKT+ AhxrpGrZerpWwuaz5WjHPn6It6Hv58GOe2Dk4dsPNhHWryoqL/7r0numu6Vgq74yFbok Zt8oBKmj3430jiBp3/uPXbqZdbc9WBJpYKoyw= Received: by 10.223.22.16 with SMTP id l16mr2766676fab.62.1315014243945; Fri, 02 Sep 2011 18:44:03 -0700 (PDT) Received: from [192.168.1.13] (abwo246.neoplus.adsl.tpnet.pl [83.8.238.246]) by mx.google.com with ESMTPS id q23sm443794fae.1.2011.09.02.18.43.59 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 02 Sep 2011 18:44:00 -0700 (PDT) User-Agent: KMail/1.9.3 Content-Disposition: inline Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: This is last call for feedback (comments) on contents of this year Git User's Survey. Thanks to generocity of Survs.com, we have been gifted with premium annual plan (last year Git User's Survey had more than 8000 responses!). This plan will last till 26 October 2011, so I am planning on having the survey for 4 weeks, in September: 5 September 2011 -- 2 October 2011 You can see test version of survey at https://www.survs.com/survey/VEBXFGJ9B0 Note that all answers in this test channel will be deleted! Below there is the content of the proposed survey. New questions include: * List git tools that you use (optional) * What do you use submodules for? * Do you use paid git hosting, and if so, why? * If you self-host git repositories, what tools do you use? * What other version control systems do you use beside Git? * What gave you most trouble learning, understanding and using Git? * Did you give help about Git? What medium did you use? * What gave you most trouble explaining and teaching Git? = Git User's Survey 2011 (proposal) = == About you == === 01. What country do you live in? === (Country of residence) (free-form single line) NOTES: ^^^^^^ This question originally read "What country are you from?" === 02. How old are you (in years)? === (Single number) (free-form single line) === 03. Does Git include code or documentation by you? === (Are you a Git developer?) (single choice) * Yes * No NOTES: ^^^^^^ This is here to correlate other responses with Git developers. == Getting started with Git == === 04. Have you found Git easy to learn? === (single choice) * Very easy * Easy * Reasonably easy * Hard * Very hard === 05. Have you found Git easy to use? === (single choice) * Very easy * Easy * Reasonably easy * Hard * Very hard NOTES: ^^^^^^ Those two questions, considered alone, doesn't tell us much. If one use git, then usually one does not think it is too hard to use (unless forced to use git by external circumstances, like project he/she works on using git). On the other hand those two questions together give us some mesaure of git learning curve, telling us if people consider git easy to use but hard to learn, or vice versa ;-) === 06. Which Git version(s) are you using? === (multiple choice, with other) + pre 1.3 + 1.3.x + 1.4.x + 1.5.x + 1.6.x + 1.7.x + 1.7.x-rcN version (release candidate) + minor (maintenance) release 1.x.y.z + 'master' branch of official git repository + 'next' branch of official git repository + 'pu' branch of official git repository + version from msysGit / Git for Windows fork repository + JGit implementation (e.g. via Eclipse plugin, EGit) + other, please specify Description: ~~~~~~~~~~~~ You can find git version by using `git --version` or `git version`. "Minor release" is additional specification, so if you for example use git version 1.7.4.5, please check both "1.7.x" and "minor release"; if you use "v1.7.6-rc3" please check both "1.7.x" and "-rcN version" NOTES: ^^^^^^ The "-rcN version" is new option. === 07. Rate your own proficiency with Git: === (single choice) * 1. novice * 2. casual, needs advice * 3. everyday use * 4. can offer advice * 5. know it very well Description: ~~~~~~~~~~~~ You can think of it as 1-5 numerical grade of your proficiency in Git. NOTES: ^^^^^^ This question tell us penetration of announcements of Git User's Survey 2011; did we get to all, or only to git gurus? It is also useful for correlating with other responses, for example to know which features are used by novices, and which by gurus. Note that the answers are here to stay because of "backwards compatibility", i.e. to be able to easy compare with earlier surveys. == How you use Git == === 08. I use Git for (check all that apply): === (multiple choice, with other) NOTES: ^^^^^^ Answers to this question probe different direction. + work projects + unpaid projects + proprietary projects + OSS development (also public domain, and published & unlicensed) + private (unpublished), in house + code (programming) and its documentation + data, documents (also e.g. static website) + sharing data or sync + managing configuration files + backup + backend for wiki, blog, or other web app + bugtracker / issue tracker + frontend to other SCM (e.g. git-svn) + other (please specify) Description: ~~~~~~~~~~~~ Note that above choices are neither orthogonal nor exclusive. You might want to check multiple answers even for a single repository. === 09. How do/did you obtain Git (install and/or upgrade)? === (multiple choice, with other) Note that this question is multiple choices question because one can install Git in different ways on different machines or on different operating systems. + binary package + source package or script (automatic compiling) + source tarball (extract, make, make install) + pull from (main) repository + preinstalled / sysadmin job + other - please specify (if none of the above apply) Description: ~~~~~~~~~~~~ Explanation: "binary package" covers pre-compiled binary (e.g. from rpm or deb binary packages); "source package" covers things like deb-src and SRPMS / *.src.rpm; "source script" is meant to cover installation in source-based distributions, like 'emerge' in Gentoo. Automatic update (apt, yum, etc.) in most cases means binary package install; unless one uses source-based distribution like Gentoo, CRUX, or SourceMage, where automatic update means using source package (or source script). The option named "preinstalled / sysadmin job" means that either you didn't need to install git because it was preinstalled (and you didn't upgrade); or that you have to ask system administrator to have git installed or upgraded. Note that this question is multiple choices question because one can install Git in different ways on different machines or on different operating systems. NOTES: ^^^^^^ What I didn't take into account in above explanation is operating systems with packaging systems different that the one used by various Linux distributions. In short: if to have git installed you compile it, you use source package or source tarball. If the installation onvolves anything more than 'make install' (or manual copying), then it is most probably source package or script. This for example means that "msysGit" installer is source package, and "Git for Windows" is binary package, if I understand it correctly. === 10. On which operating system(s) do you use Git? === (multiple choice, with other) + GNU/Linux (includes MeeGo) + MacOS X (Darwin) + MS Windows/msysGit (MINGW) + MS Windows/Cygwin + some MS Windows (unknown or other) + FreeBSD, OpenBSD, NetBSD, etc. + Solaris / OpenSolaris / Illuminati / IllumOS + other Unix + Other, please specify Description: ~~~~~~~~~~~~ On Unix-based operating system you can get the name of operation system by running `uname` (or `uname -o`). NOTES: ^^^^^^ How to detect if it is msysGit or Cygwin from within? Perhaps we should have just "MS Windows"... === 11. What Git interfaces, implementations and frontends do you use? === (multiple choice, with other) + JGit (Java implementation), e.g. via Eclipse plugin + NGit or Git# (C# implementation) + Dulwich (pure-Python implementation) + Git::PurePerl (Perl implementation) + git.js (JavaScript) + libgit2 bindings + git (core) commandline ? Cogito (DEPRECATED) + Easy Git + Pyrite + I don't know, I only use (graphical) tools ? pg aka Patchy Git (DEPRECATED) + StGIT + Guilt + TopGit + Zit + other (please specify) NOTES: ^^^^^^ This version is going back to split from 2008 survey, rather than having everything put together like in 2009 one. There are, of course, problems with both choices. The problem with split part is that people can have troubls with distinguising between interfaces, implementations, frontends and tools (although "I don't know ..." answer should, I think, help here). The problem with having it everything together is that the list of possible answers gets long and a bit unwieldy. BTW are there any implementations and frontends that should be added to the list above? === 12. What kind of Git tools do you use? === (multiple choice, with other) If a tool is both history viewer, and commit tool, please choose the option that corresponds to how do you use this tool. + editor/IDE VC integration (e.g. EGit (for Eclipse), TextMate bundle, magit (for GNU Emacs)) + build tool integration (e.g. git plugin for Maven, gitbuilder, Parabuild) + filemanager / shell extension (e.g. git-cheetah, TortoiseGit) + filesystem interface (e.g. gitfs, figfs) + graphical history viewer/browser (e.g. gitk) + graphical commit tool (e.g. git-gui) + graphical diff and/or merge tool (e.g. Kompare, Meld) + graphical blame or pickaxe tool (e.g. 'git gui blame') + tool to manage git repositories (e.g. Gitosis, Gitolite) + git-instaweb, or self-hosted web interface (e.g. gitweb, cgit) + self-hosted code review system (e.g. Gerrit) + self-hosted git software forge (e.g. Gitorious, GitHub:FI, InDefero) + patch management interface (e.g. StGit, Guilt) + tracking some files out-of-band (e.g. git-annex, git-media) + storing metadata (e.g. metastore, gitperms, git-cache-meta) + managing composite repositories (e.g. git-subtree, gitslave, repo) + my own scripts (for daily use) + my own scripts (for special tasks) + other kind (please specify) Description: ~~~~~~~~~~~~ Here graphics diff tool means tools such as Kompare, and graphical merge tool means tools such as Meld and KDiff3. Those answers include graphical merge and diff tools used by programmers editors and IDEs. "graphical history browser (any)" covers tools such as gitk, QGit, Giggle, tig etc., but also built-in git commands such as "git log --graph" and "git show-branch". If you use one of mentioned tools *as* history browser, mark both a tool and "graphical history browser (any)"; if you use some graphical history viewer not listed here, please both mark this answer and specify it in the "other tool" answer. Similarly for other answers marked "(any)". === 13. List git tools that you use (optional) === (free form, essay) Description: ~~~~~~~~~~~~ Please include only frontends, interfaces and tools that have support for Git (so e.g. EGit applies, but Eclipse doesn't). Please either use comma separated list of tools, or put each tool in a separate line. That would make analysis of answers simpler. Thanks in advance. NOTES: ^^^^^^ Replaced list of tools from 2009 with free-form question. === 14. What do you use submodules for? === (multiple choice, with other) + I don't use submodules at all + I use submodules + I use repo + I use git-subtree + I use gitslave + to import repositories maintained by others + for your own (or your organization's) code shared between different projects + to separate large and/or many files for performance reasons + to separate data which you don't want (or aren't allowed) to disclose + Other, please specify NOTES: ^^^^^^ New. Requested by Jens Lehmann. === 15. Which of the following Git features do you use? === (multiple choice, with other) + git bundle (off-line transport) + eol conversion (crlf or eol) + gitattributes (any) + custom diff/merge driver + word diff + merge strategy options (e.g. -Xrenormalize) + textconv + submodules (subprojects) + subtree merge (optionally git-subtree) + partial (sparse) checkout, + assume-unchanged bit + separate worktree / core.worktree + multiple worktrees (e.g. git-new-worktree) + gitdir mechanism (.git file pointing to repository) + remote helpers (e.g. ::
URLs) + alternates mechanism (sharing object database) + stash (optionally "git stash --keep-index") + shallow clone (e.g. "git clone --depth=") + detaching HEAD (e.g. "git checkout --detach") + commit message templates + interactive commit / per-hunk comitting / partial commit + interactive rebase (small scale history editing) + git-filter-branch or equivalent (large history rewriting) + bisect (optionally "git bisect run