From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Git User's Survey 2009 - trial run
Date: Fri, 26 Jun 2009 22:05:48 +0300 [thread overview]
Message-ID: <94a0d4530906261205o6e4195dub4e38e8dccbd9258@mail.gmail.com> (raw)
In-Reply-To: <200906261744.04610.jnareb@gmail.com>
On Fri, Jun 26, 2009 at 6:44 PM, Jakub Narebski<jnareb@gmail.com> wrote:
> On Fri, 26 June 2009, Felipe Contreras wrote:
>> 2009/6/25 Jakub Narebski <jnareb@gmail.com>:
>
>> > I have created _proposed_ version of questions for upcoming
>> > "Git User's Survey 2009", based on (a bit of) feedback on git
>> > mailing list:
>> > "[RFH] Questions for Git User's Survey 2009"
>> > Msg-Id: <200905291855.03328.jnareb@gmail.com>
>> > http://thread.gmane.org/gmane.comp.version-control.git/120287
>> > and comments on #git IRC channel on FreeNode.
>> >
>> > 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.
>> >
>> >
>> > 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
<snip/>
> +8. How did/do you obtain Git?
>
> It is IMHO more interesting how people upgrade Git, than just how
> they installed it.
Sure, but it can be assumed from how it was installed:
* Some kind of package management (automatically updated)
* In other binary form (manually)
* From a source tarball (manually)
* From git.git repository (manually)
<snip/>
>> Also, I would like to see a list of areas users would like improvements:
>> XX. In you opinion, which areas need improvement?
>> * user-interface
>> * documentation
>> * performance
>> * more features
>> * other
>>
>> Is there a way for users to assign points? eg. user-interface: 2,
>> documentation: 1, more features: 1
>
> We can always use 'matrix' form, with columns corresponding to importance
> of a given area for improvement (1-3, or 1-5 numeric range). Because
> asking user to order from most important to least important (one can
> enforce this on Survs.com by requiring only one answer with given column
> selected) would be too difficult and confusing.
I see, in that case I think a matrix form would do.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2009-06-26 19:05 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
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 [this message]
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=94a0d4530906261205o6e4195dub4e38e8dccbd9258@mail.gmail.com \
--to=felipe.contreras@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.
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).