git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santi Béjar" <santi@agolina.net>
To: Johan Herland <johan@herland.net>
Cc: Jakub Narebski <jnareb@gmail.com>,
	git@vger.kernel.org,
	Felipe Contreras <felipe.contreras@gmail.com>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	Peter Baumann <waste.manager@gmx.de>,
	Clemens Buchacher <drizzd@aon.at>,
	David Aguilar <davvid@gmail.com>,
	Erik Faye-Lund <kusmabite@googlemail.com>
Subject: Re: [RFC] Git User's Survey 2009 - trial run
Date: Fri, 26 Jun 2009 11:10:24 +0200	[thread overview]
Message-ID: <adf1fd3d0906260210n15be0576ofb683df6a1ef454c@mail.gmail.com> (raw)
In-Reply-To: <200906260932.43826.johan@herland.net>

2009/6/26 Johan Herland <johan@herland.net>:
> On Thursday 25 June 2009, Jakub Narebski wrote:
>> Current version of survey has 30 questions, as compared to
>> 60 questions last year; the number of free-form essay questions
>> were also greatly reduced.
>
> Good. :)
>
>> The *test* version of this year survey can be now found at
>> the following URL (as in previous year, we use Survs.com)
>>
>>   http://www.survs.com/survey?id=2PIMZGU0&channel=TFN2Y52K7Y
>>
>> Please tell me what you think about questions and about selection
>> of possible answers in single choice/multiple choice questions.
>
> There seems to be some unnecessary overlap among questions 11, 16/17 and 18.

[...]

>
> Some of this overlap is probably unavoidable, but I think some of it
> (especially between 16/17 and 18) can be eliminated without compromising the
> survey. Maybe we can integrate the non-overlapping parts of 18 into the
> other questions, thereby further decreasing the number of questions?
>
> BTW, 17 is just a continuation of 16, AFAICS. Is it possible to just repeat
> the column headers (to break up the table length) and still keep it as one
> question?
>


I agree.

[...]

>
> Otherwise, I like the survey very much.

Me too.

>
>> How long does it take to fill survey?
>
> ~ 5-7 minutes

For me it was 12 minutes, and it was without answering the free form
questions and with good git knowledge.

Santi

  reply	other threads:[~2009-06-26  9:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 19:22 [RFC] Git User's Survey 2009 - trial run Jakub Narebski
2009-06-26  7:32 ` Johan Herland
2009-06-26  9:10   ` Santi Béjar [this message]
2009-06-26 10:55   ` Felipe Contreras
2009-06-26 13:08   ` Jakub Narebski
2009-06-26 14:44     ` Johan Herland
2009-06-28 23:23       ` Jakub Narebski
2009-06-26 10:16 ` Peter Baumann
2009-06-26 15:10   ` Jakub Narebski
2009-06-26 11:12 ` Felipe Contreras
2009-06-26 15:44   ` Jakub Narebski
2009-06-26 19:05     ` Felipe Contreras
2009-06-29 23:21       ` Jakub Narebski
     [not found] ` <665CFE02-78DC-49E5-A9F2-9A614691FBAE@kace.com>
2009-06-26 17:00   ` 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

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

  git send-email \
    --in-reply-to=adf1fd3d0906260210n15be0576ofb683df6a1ef454c@mail.gmail.com \
    --to=santi@agolina.net \
    --cc=davvid@gmail.com \
    --cc=drizzd@aon.at \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=johan@herland.net \
    --cc=kusmabite@googlemail.com \
    --cc=srabbelier@gmail.com \
    --cc=waste.manager@gmx.de \
    /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).