git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Stephan Beyer <s-beyer@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC v2] Git User's Survey 2008
Date: Thu, 21 Aug 2008 13:11:23 +0200	[thread overview]
Message-ID: <200808211311.24600.jnareb@gmail.com> (raw)
In-Reply-To: <20080820211852.GA27226@leksak.fem-net>

On Wed, 20 Aug 2008, Stephan Beyer wrote:
> Jakub Narebski wrote:
> 
> > By the way, should the survey be divided in pages, or simply use
> > headers to divide survey into sections?
> 
> Divided pages have a psychological impact, they don't look much and you
> can say "Almost there!" on each page.
> 
> But headers and one-page surveys have a big advantage for users that pay
> for Internet access per time unit: they can go offline, answer the
> questions, and go online again to submit the survey.
> 
> So I've scrolled across your test survey on survs.com and I think it
> should be kept on one page. Looks nice and manageable.

I also prefer single page surveys; it would be better if this survey
was shorter (by the way, how long did you took to complete test survey?),
but there are so many interesting questions...
 
> > Third, where to send survey to / where to publish information about the 
> > survey?
> 
> This question leads me to a question that could be put into the survey:
> 
> 	Where have you read about this survey? (optional)
> 	[Free form]

But where to add it?  Additionally I'd rather limit free-form questions
to absolute minimum.

This is the question I was lacking, so I'll think about adding it to
the survey.

> So, some comments on the questions now:
> 
> > About you
> > 
> >    xx. What country are you in?
> 
> "What country do you live in?" perhaps?

This is better phrasing.  Changed.
 
> > Getting started with GIT
> > 
> >    xx. How did you hear about Git?
> 
> There is a typo on survs.com (hear_d_).
> Should this by the way be multiple choice?
> I have heard about Git several times before I tried it.
 
Good idea, I think, and doesn't lead to more work when analysing.
And it would perhaps make it easier to choose appropriate answer.

Changed. 

> I will only quote from survs.com now:
> 
> > told by friend (word of mouth)
>                  ^^^^^^^^^^^^^^^ ? :) I think this should be removed

O.K.

> > What other SCM did or do you use?
> >[..]
> >  custom ( ) ( ) ( )
> 
> custom?

I mean here custom, not published (or no longer existing) SCM; something
that would be hard to write about.

I agree that it is not the best phrasing.

> > 20. Which porcelains / interfaces / implementations do you use?
> >  [ ] core-git
> 
> Uh, this is ambiguous.  Is this our git or some script on top of git?
> In both cases, this should be clarified.

There is "my own scripts" at the bottom; I mean here using no additional
porcelain, no interface on top of git command line.

But it is here for completeness only; however if you have some good
explanation for "core-git" option I can put it below this question.

> > 22. Which git web interface do you use for your projects/have installed?
> > (Web interfaces used by git hosting sites do not count[*])
> [...]
> > (*) Unless of cours you are hosting some git hosting site
>              ^^^^^^^^                                      ^
> 	     typo, but I'd rather do s/of cours //   and s/$/./ :-)

Thanks.  Done.

> > 26. How often do you use the following forms of git commands
> > or extra git tools?
> >
> >		Never | Rare | Often
>                                      | Not yet, but sounds cool   ;-)
> 
> No no :-)
> 
> But I wonder if we could split the "Never" case into several cases with
> reasons like:
>  - Do not know.
>  - Not yet needed.
>  - Other (did not understand; tried but did not work; ...)
> 
> But this will perhaps bloat the question even more, so we should keep
> "Never", though I think the reasons could be interesting.
> Could some "Comments" field for question 26 help?

Now it is 'never/rarely/sometimes/often'.  I think there are enough
free form questions that one can put his/her own comments about git
commands in this survey...

> Some other comment: I dislike that there is *one* "Reset" button for
> such matrix questions. But I guess you cannot change that?

Yes, this is canned web survey site.  I can only send feedback,
but I guess so can you (unless this requires subscription/invite...).

> > 28. Which of the following features do or did you use?
> 
> I think many of the possible replies have been used in several other
> questions before, e.g. in 
>  - 21. (gitk, git gui), 
>  - 24. (git bundle),
>  - 26/27. (git gui, gitk, git stash)
>  - ...
> 
> But this question still seems to makes sense for:
>  [ ] eol conversion (crlf)
>  [ ] gitattributes
>  [ ] reflog (ref@{23})
>  [ ] shallow clone
>  [ ] detaching HEAD   <- I think several people could have used that without knowing
>  [ ] commit templates
>  [ ] integration with IDE/editor
>  [ ] non-default hooks
> 
> And btw:
> > [ ] working with dirty tree      <- Eh? Is this a feature?

This is distinguishing feature.  What I mean here that you can use
"git add" and "git commit" (not "git commit -a") and have some
uncommitted changes, like for example change of version in Makefile.

> Big thanks for your efforts,
>   Stephan

You are welcome.

-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2008-08-21 11:11 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23  1:25 [RFC] Git User's Survey 2008 Jakub Narebski
2008-07-23  4:39 ` Junio C Hamano
2008-07-23  7:47   ` HP-UX issues (WAS: Re: [RFC] Git User's Survey 2008) Miklos Vajna
2008-07-23 21:38     ` Jakub Narebski
2008-07-23 23:45       ` Miklos Vajna
2008-07-23 11:06   ` [RFC] Git User's Survey 2008 Jakub Narebski
2008-07-24 11:46   ` Marek Zawirski
2008-07-24 12:09     ` Mailing lists, was " Johannes Schindelin
2008-07-25 17:23       ` Shawn O. Pearce
2008-07-25 18:49         ` Junio C Hamano
2008-07-25 21:52           ` Jakub Narebski
2008-07-25 21:57             ` Shawn O. Pearce
2008-07-25 22:11               ` Junio C Hamano
2008-07-25 22:13                 ` Shawn O. Pearce
2008-07-26 10:54                   ` Jakub Narebski
2008-07-26 12:19                     ` Marek Zawirski
2008-07-26 21:50                     ` Shawn O. Pearce
2008-07-26 21:52                       ` Jean-François Veillette
2008-07-25 22:15               ` Petr Baudis
2008-07-26 15:51               ` Jing Xue
2008-07-26 16:47                 ` Jakub Narebski
2008-07-26 17:51                   ` Shawn O. Pearce
2008-07-26 18:17                     ` Jakub Narebski
2008-07-26 19:06                       ` Johannes Schindelin
2008-07-26 18:38                     ` Scott Chacon
2008-07-24 14:07     ` Jakub Narebski
2008-07-23  9:53 ` Johannes Schindelin
2008-07-23 13:08   ` Jakub Narebski
2008-07-23 13:18     ` Johannes Schindelin
2008-07-23 14:54       ` Robin Rosenberg
2008-07-23 16:00         ` Johannes Schindelin
2008-07-24 10:44           ` Jakub Narebski
2008-07-23 23:30         ` Jakub Narebski
2008-07-23 23:33           ` Johannes Schindelin
2008-07-23 23:53           ` Stephan Beyer
2008-07-24  5:02             ` david
2008-07-24  8:57               ` Stephan Beyer
2008-07-24 10:37                 ` david
2008-07-24  9:52             ` Jakub Narebski
2008-07-26 15:34               ` Jakub Narebski
2008-07-27 11:24                 ` Nguyen Thai Ngoc Duy
2008-07-23 16:43     ` Junio C Hamano
2008-07-24  0:10       ` Jakub Narebski
2008-07-23 14:54   ` Dmitry Potapov
2008-07-23 16:02     ` Johannes Schindelin
2008-07-23 17:01     ` Stephan Beyer
2008-07-24  8:24       ` Jakub Narebski
2008-07-23 17:17   ` Alex Riesen
2008-07-24  8:15     ` Jakub Narebski
2008-07-23 14:12 ` Stephan Beyer
2008-07-24 22:22   ` Stephan Beyer
2008-07-23 14:38 ` Dmitry Potapov
2008-07-23 15:43   ` Matthias Kestenholz
2008-07-23 20:09     ` Dmitry Potapov
2008-07-23 21:49   ` Jakub Narebski
2008-07-24 18:08     ` Dmitry Potapov
2008-07-24 21:06       ` Jakub Narebski
2008-07-23 21:44 ` Petr Baudis
2008-07-23 21:59   ` Jakub Narebski
     [not found] ` <169F15EC-1A58-4C2A-84FC-3D14F7B4F1C5@yahoo.ca>
2008-07-23 22:46   ` Miguel Arroz
2008-07-23 23:49   ` Jakub Narebski
2008-07-24 10:11     ` Sverre Rabbelier
2008-07-24 14:45 ` Jon Loeliger
2008-07-24 18:18   ` Jakub Narebski
2008-07-24 18:50     ` Lachele Foley (Lists)
2008-07-24 21:08       ` Jakub Narebski
2008-07-24 17:57 ` Dmitry Potapov
2008-07-24 18:42   ` Jakub Narebski
2008-07-31 12:48 ` Jakub Narebski
2008-08-20  1:08 ` [RFC v2] " Jakub Narebski
2008-08-20 11:34   ` Alex Riesen
2008-08-20 12:04     ` Petr Baudis
2008-08-20 13:50       ` Jakub Narebski
2008-08-20 18:18         ` Alex Riesen
2008-08-20 20:14   ` Junio C Hamano
2008-08-21  1:30     ` Jakub Narebski
2008-08-21  3:10       ` Junio C Hamano
2008-08-21 11:19         ` Jakub Narebski
2008-08-20 21:18   ` Stephan Beyer
2008-08-20 21:26     ` Stephan Beyer
2008-08-21 11:11     ` Jakub Narebski [this message]
2008-08-21 21:26       ` Stephan Beyer
2008-08-22  0:06         ` Jakub Narebski
2008-08-21  3:22   ` Mike Gant
2008-08-24 21:36   ` Stephan Beyer
2008-08-25  0:41     ` Jakub Narebski
     [not found]       ` <20080825012653.GB28160@leksak.fem-net>
2008-08-25  1:56         ` Jakub Narebski
2008-08-20  7:31 ` Abhijit Bhopatkar
2008-08-25 22:08 ` [RFC v3] " Jakub Narebski
2008-08-28  0:28   ` Stephan Beyer
2008-08-30  1:33 ` [RFC v4] Git User's Survey 2008 (cover letters) Jakub Narebski
2008-08-30 19:00   ` Garry Dolley
2008-09-01  7:47   ` Paolo Ciarrocchi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200808211311.24600.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=s-beyer@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).