git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: David Bainbridge <david.bainbridge@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Git User's Survey 2010 (resend)
Date: Sun, 4 Jul 2010 13:14:45 +0200	[thread overview]
Message-ID: <201007041314.50591.jnareb@gmail.com> (raw)
In-Reply-To: <AANLkTimbpOEpi8QOqTOMav0whmLeHz3vQq_0KDnblRIK@mail.gmail.com>

On Sun, 4 July 2010, David Bainbridge wrote:

> First, as someone working in a company that is adopting Git can I say
> that I found the results of previous surveys useful? So I think that
> these surveys should continue :-)

Thank you very much for the words of encouragement.

> I think that the reduction of free text fields is good ... I am
> concerned that if I point several hundred users at the this survey and
> encourage them to respond that you should not get swamped!

I had idea of running some kind of natural text processing analyser
for analysis of free-form responses[1], but nothing came out of this
(currently).

[1]:http://stackoverflow.com/questions/887954/how-to-categorize-and-tabularize-free-form-answers-to-a-question-in-a-survey

> 
> The surveys are actually useful for making people more aware of what
> Git can do, and the other tools associated with Git, so this is
> something of bear in mind.

Well, this year there is no question about how often one uses specified
git commands.  In my opinion it made responding to survey too long, and
it was not balanced by people learning about new commands, I don't
think.

> Have you considered the question: 'How long have you been using Git?'.
> This combined the expertise level might yield some useful information,
> and could provide some weighting for the 'Getting started' questions
> too. There are some problems with the question in that it could be,
> say, 2 years intermittent use, or 2 years continuous use, and these
> are different, of course.

Well, such question was replaced by the question about one's own
proficiency in Git in 2009 survey (IIRC).

> > === 06. 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

The problem with question "How long have you been using Git?" (beside
what you have mentioned) is that it is hard to answer correctly / in
detail for longer times.

Perhaps something like this:

=== xx. How long have you been using Git? ===
(single choice, with other)

 * less than week
 * between a week and a month
 * a few months
 * a few years
 * duration (please give units)

What do you think?

> The demographic information is useful if you want to understand
> whether Git is (for example) considered less usable in countries where
> English is not the native language. But then if you want to know the
> native language of the user rather than where they live then perhaps
> this should be asked? (I was born in the UK, but now live in Sweden
> ... so I am perhaps more conscious of this!). Where you are born does
> not necessarily identify your native language either.

The problem with this question in the past was twofold: first, people
sometimes mistok it for question about _programming languages.  Second
should this question be about primary language / languages, or about
language ones prefer the computer to communicate with?
 
> Do you want to separate work usage and 'non-work' usage at all? The
> two experiences may be completely different. If I am working at home I
> can use what ever I want, and work how I want. This will probably not
> be the case in a corporate environment, so I would report one set of
> results for 'work' and another for 'non-work'. This could generate two
> survey returns for a single user. Is this intended?

Hmmmm... food for though.  It can be mentioned somewhere close to
beginning that one can fill this survey more than once (from different
computers if using default version with cookies) for different roles
one plays.  Perhaps with checkbox "additional role" (aka. "I have already
filed this survey" ;-))...
 

> Just a couple of thoughts :-)

Thanks a lot for your comments.  I appreciate it.

-- 
Jakub Narebski
Poland

  reply	other threads:[~2010-07-04 11:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-03 19:58 [RFC] Git User's Survey 2010 (resend) Jakub Narebski
2010-07-04  0:21 ` Ævar Arnfjörð Bjarmason
2010-07-04  8:13   ` Jakub Narebski
2010-07-07  9:18     ` Yann Dirson
2010-07-07 21:43       ` Jakub Narebski
2010-07-10 11:01   ` Felipe Contreras
2010-07-04  9:07 ` David Bainbridge
2010-07-04 11:14   ` Jakub Narebski [this message]
2010-07-04 20:48     ` David Bainbridge
2010-07-05  7:19       ` Jakub Narebski
2010-07-04 22:43 ` Scott Chacon
2010-07-04 23:48   ` Jakub Narebski
2010-07-07 12:28 ` Yann Dirson
2010-07-07 21:37   ` Jakub Narebski
2010-07-08  7:24     ` Yann Dirson
2010-07-10 11:31 ` Felipe Contreras
2010-07-10 19:58   ` Jakub Narebski
2010-07-11  9:57     ` Felipe Contreras
2010-07-11 17:42       ` Jakub Narebski
2010-07-12 10:14         ` David Bainbridge
2010-07-12 10:19           ` Felipe Contreras
2010-07-12 10:22             ` David Bainbridge
2010-08-09 21:59 ` Felipe Contreras
2010-08-10 22:16   ` Jakub Narebski

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=201007041314.50591.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=david.bainbridge@gmail.com \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).