On Wed, 23 Jul 2008, Johannes Schindelin wrote:I'd rather not have a "laundry list" of languages. I have put C++ because QGit uses it, Java because of egit/jgit, PHP for web interfaces, Ruby because of GitHub and because of Ruby comminity choosing Git. I should perhaps add Emacs Lisp, HTML+CSS and JavaScript here. What other languages should be considered? By "Tutorials (elsewhere; not in git.git)" you mean here many various "git guide" pages, like "Git for Computer Scientists", "Git Magic", etc.? I'm not sure about having multiple choice vs. free-form question here. Multiple choice is easier to analyze, especially if one would want histogram of replies... but free form is more rich. But perhaps multiple choice with free-form "other" choice would be the best? Besides proposed choices limit person filling the survey to single understanding of "what helped you in learning to use Git", which can be also understood as asking for list of features helping with learning Git, not only list of documentation and such. Here it can be hard to come up with good list of choices. For example among responses in 2007 survey there were 'inconsistent commands', 'obtuse command messages', 'insufficient/hard to use documentation', and many more. I'm not sure if troubles with coming with extensive but not too large list of options for this question is worth it; I think that we need only list of responses, and not number of responses (perhaps mentioning which one occur [much] more frequently). O.K., I'll add it. I think I'd better add RCS too. Free form has some hassles. Because here histogram of responses might be interesting, perhaps it would be good to use multiple choice here. I would add "features" and/or "unique features" to the list, and also perhaps "being popular/hype". Again: free form has some hassles, but so does coming up with good choice of fixed answers in multiple choice question. I'll add "ease to install on MS Windows" (or something like that) if we decide to have this question multiple choice. O.K. I'll add "git-svn (or other to foreign SCM)". I think it is. I'd rather try to reduce number of questions... I'll remove it, then. Right. Thanks. ??? I'm sorry about that: I have forgot that this and all similar questions had triple choice: yes/no/somewhat in the final version of 2007 survey. I'll correct it. :-) -- Jakub Narebski Poland -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | Og dreams of kernels |
| Jens Axboe | [PATCH 31/33] Fusion: sg chaining support |
| Arnd Bergmann | Re: finding your own dead "CONFIG_" variables |
| Mark Brown | [PATCH 2/2] Subject: natsemi: Allow users to disable workaround for DspCfg reset |
| Tony Breeds | [LGUEST] Look in object dir for .config |
git: | |
| Brian Downing | Re: Git in a Nutshell guide |
| John Benes | Re: master has some toys |
| Matthias Lederhofer | [PATCH 4/7] introduce GIT_WORK_TREE to specify the work tree |
| Alexander Sulfrian | [RFC/PATCH] RE: git calls SSH_ASKPASS even if DISPLAY is not set |
| Junio C Hamano | Re: Rss produced by git is not valid xml? |
| Linux Kernel Mailing List | iSeries: fix section mismatch in iseries_veth |
| Linux Kernel Mailing List | ixbge: remove TX lock and redo TX accounting. |
| Linux Kernel Mailing List | ixgbe: fix several counter register errata |
| Linux Kernel Mailing List | b43: fix build with CONFIG_SSB_PCIHOST=n |
| Linux Kernel Mailing List | 9p: block-based virtio client |
