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

Hi Jakub,

It sounds like I was revisiting old territory in some cases :-)

The thoughts about free text analysis were interesting though ...

On 4 July 2010 13:14, Jakub Narebski <jnareb@gmail.com> wrote:
> On Sun, 4 July 2010, David Bainbridge wrote:
>
>> 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?

I think that the granularity is about right. I think we could imagine
where we would expect people to be proficiency-wise with those
periods. Not sure about the last option ... You have everything from
days, to weeks to months to years in the main options. What did you
have in mind?

>
>> 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?

Obviously you have been though this loop before! But perhaps if you
are using drop-down lists then this makes it obvious what is required.
I guess both the programming language, and the preferred interaction
language could be relevant.

We may want to know whether Git is more 'acceptable' to the Java
community or the C/C++ community for example, or whether certain
suggestions for improvement are coming from a community around a
particular language.

Then with the human languages this could drive the localization of the
commands, as well as the documentation localization. Interesting ...

>
>> 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" ;-))...
>

Thats sounds reasonable ... I think it is probably useful to capture a
user-role response. The priorities of users and their needs may be
completely different in a work situation.

>
>> Just a couple of thoughts :-)
>
> Thanks a lot for your comments.  I appreciate it.

No problem ... I will have another read through your original mail and
see if there is anything else!

All the best,

David Bainbridge
Sweden
> --
> Jakub Narebski
> Poland
>

  reply	other threads:[~2010-07-04 20:49 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
2010-07-04 20:48     ` David Bainbridge [this message]
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=AANLkTim0HypdTEwsTUQ-G8C3mAoZ-7Ro3zB4z7-hpFq2@mail.gmail.com \
    --to=david.bainbridge@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /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).