Jakub Narebski <jnareb@xxxxxxxxx> writes: > This is second revision (version) of proposed questions > for Git User's Survey 2008. Very nicely done. > Getting started with GIT > > xx. How did you hear about Git? > (single choice?, in 2007 it was free-form) > - Linux kernel news (LKML, LWN, KernelTrap, KernelTraffic,...), > news site or magazine, blog entry, some project uses it, > presentation or seminar (real life, not on-line), SCM research, > IRC, mailing list, told by friend, word of mouth (off-line), > other Internet, must be used at job, other off-line, other(*) > + the problem is with having not very long list (not too many > choices), but spanning all possibilities. > + is this question interesting/important to have in survey? I'd say this is more interesting than "what programming language do you speak". > xx. Which Git version(s) are you using? > (zero or more, multiple choice: > one can use different versions on different machines) > - pre 1.3, 1.3, 1.4, 1.5, 1.6, master, next > + might be important when checking "what did you find hardest" etc. This is a very good idea. "What is hardest" grouped by "How proficient are you with git". > Other SCMs (shortened compared with 2007 survey) > > xx. What other SCM did or do you use? > ! (zero or more: multiple choice) > (matrix with the following columns: never/used it/still use) "Plan to use"? > - SCCS, RCS, CVS, Subversion, Arch or clone (ArX, tla, ...), > Bazaar-NG, Darcs, Mercurial, Monotone, SVK, AccuRev, Perforce, > BitKeeper, ClearCase, MS Visual Source Safe, MS Visual Studio > Team System, PVCS, custom, other (please specify) With this number of "other systems", it is easier to pick if they are sorted alphabetically. > How you use Git > > xx. Which (main) git web interface do you use for your projects? > (zero or more: multiple choice) > - gitweb, cgit, wit (Ruby), git-php, viewgit (PHP), Gitorious, > other (please specify) You have reworded this question on the site but it has typo "Unless of cours you are hosting..." (s/cours y/course y/). > xx. How do you publish/propagate your changes? > (zero or more: multiple choice) > - push, pull request, format-patch + email, bundle, > git-svn, foreign SCM (not via git-svn), > other (see also below) cvsexportcommit? > xx. If the way you publish your changes is not mentioned above, how > do you publish your changes? Please explain. > (free form, either input field or textarea) > xx. How often do you use the following forms of git commands or extra > git tools? > (matrix form: never/rare/often) "never, rarely, *sometimes*, often"? > . git add -i / -p > . git add -u > . git am > . git am -i > . git apply "apply --whitespace=fix"? > . git cvsserver "git daemon" and "git daemon (pushing enabled)" as separate items. > . git ... --dirstat "diff --check"? > . git pull "pull --rebase"? > . git pull <remote> > . git pull <URL> <ref> > . git push Separate "(empty) vs <remote> vs <URL> <refspec>" entries for "git push"? Also for "git fetch"? > . git stash "git stash pop"? "git stash save --keep-index"? > + in what order should be those commands; currently they are in > alphabetical order? That is the most sensible. > xx. Which of the following features do you use? > (zero or more: multiple choice) > - git-gui or other commit tool, gitk or other history viewer, patch > management interface (e.g. StGIT), bundle, eol conversion (crlf), > gitattributes, submodules, separate worktree, reflog, stash, If you single out "eol conversion", perhaps separate "whitespace attributes" out of generic "gitattributes"? s/separate worktree/& (git-new-workdir)/; > Documentation > > xx. What could be improved on the Git homepage? > (free form) > xx. What could be improved in Git documentation? > (free form) "What can/will you do to help improve them?"? > Translating Git > > xx. What is your preferred non-programming language? > (or) What is the language you want computer communicate with you? > xx. What do you need/want to have translated? > (zero or more, multiple choice) > - commands messages, manpages, manual & tutorial etc., > technical documentation, HOWTOs, git homepage, git wiki, > git-gui/gitk, subcommands and long option names LOL on the last one ;-) Please keep it --- we may find amusing results. > Getting help, staying in touch > > xx. Have you tried to get Git help from other people? > - yes/no > xx. What channel did you use to request help? > (zero or more: multiple choice) > - git mailing list, git users group, IRC, blog post, > asking git guru/colleague, other You have "IRC (#git)". Perhaps a separate item "IRC (#github)"? > Open forum > > xx. What other comments or suggestions do you have that are not > covered by the questions above? > (free form) > xx. Should such a survey be repeated next year? > - yes/no/no opinion "Such a", meaning "This"? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
