git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: David Aguilar <davvid@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC] Git User's Survey 2009 - second trial run, and question  about announcing it
Date: Sun, 5 Jul 2009 00:43:58 +0200	[thread overview]
Message-ID: <200907050043.58875.jnareb@gmail.com> (raw)
In-Reply-To: <94a0d4530907040124i32abe421x86e5c8f0839bf2fa@mail.gmail.com>

On Sat, 4 July 2009, Felipe Contreras wrote:
> On Sat, Jul 4, 2009 at 4:26 AM, David Aguilar<davvid@gmail.com> wrote:
>> On Sat, Jul 04, 2009 at 02:19:25AM +0300, Felipe Contreras wrote:
>>> 2009/7/3 Jakub Narebski <jnareb@gmail.com>:
>>>
>>>> 20. Overall, how happy are you with Git?
>>>>    * unhappy
>>>>    * not so happy
>>>>    * happy
>>>>    * very happy
>>>>    * completely ecstatic
>>>
>>> Let's leave room for git haters too:
>>>  * I hate it
>>
>> Umm, let's not.
>>
>> If they hate it, they'll be in the "unhappy" category.
>> And if they hate it, I doubt they'll be filling out this survey.

[...]
>> Let's not encourage them by including including "I hate git"
>> in our survey.
> 
> That's a good point, I just thought it would be nice to spot them;
> which would be easy if they answer "I hate it". But also, if there's
> an extreme positive (completely ecstatic) I thought there should be an
> extreme negative, just in case.
> 
> Probably not important at all.

Hmmm...

On the one hand side it would be better, I think, to have balanced set
of answers, with neutral position in the middle, and unhappy/happy
along the axis.

On the other hand that was the set of answers used in previous surveys,
so if we change it it would be harder to compare against surveys in past
years.

-- 
Jakub Narebski
Poland

  reply	other threads:[~2009-07-04 22:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 23:30 [RFC] Git User's Survey 2009 - second trial run, and question about announcing it Jakub Narebski
2009-07-03  0:22 ` Junio C Hamano
2009-07-03 22:23   ` Jakub Narebski
2009-07-03 23:19 ` Felipe Contreras
2009-07-04  1:26   ` David Aguilar
2009-07-04  8:24     ` Felipe Contreras
2009-07-04 22:43       ` Jakub Narebski [this message]
2009-07-04 23:46         ` Felipe Contreras
2009-07-04 22:40   ` Jakub Narebski
2009-07-04 23:53     ` Felipe Contreras
2009-07-05 17:53       ` Jakub Narebski
2009-07-05 18:30       ` Junio C Hamano
2009-07-05 19:15         ` Felipe Contreras
2009-07-05 19:45           ` Jakub Narebski
2009-07-05 20:12             ` Felipe Contreras
2009-07-06  8:14               ` Andreas Ericsson
2009-07-06 11:16                 ` Jakub Narebski
2009-07-06 12:31                 ` Felipe Contreras
2009-07-06 13:14                   ` Andreas Ericsson
2009-07-06 21:49             ` Elijah Newren
2009-07-04  9:05 ` Martin Renold
2009-07-06 21:44   ` Jakub Narebski
     [not found] ` <40aa078e0907071716k40d6ce9cwc0f9801f4042ef3a@mail.gmail.com>
2009-07-08  1:02   ` 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=200907050043.58875.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=davvid@gmail.com \
    --cc=felipe.contreras@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.
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).