From: Jakub Narebski <jnareb@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Git User's Survey 2009 - trial run
Date: Tue, 30 Jun 2009 01:21:44 +0200 [thread overview]
Message-ID: <200906300121.44903.jnareb@gmail.com> (raw)
In-Reply-To: <94a0d4530906261205o6e4195dub4e38e8dccbd9258@mail.gmail.com>
On Fri, 26 Jun 2009, Felipe Contreras wrote:
> 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>:
[...]
>> +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)
Hmmm... I'd have to think about it a bit. On one hand side original
version has the advantage of being similar to questions in previous
surveys, making comparison easier. On the other hand side it is more
interesting to ask about how people update git.
BTW. you list does not include my example: I download src.rpm and
rebuild (recompile) it, then install created packages. So it is from
source form, but compiled and installed automatically.
>>> 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.
I would replace then question "21. How does Git compare to other SCM
tools you have used?" which is not good question, especially now that
we don't have the whole "Other SCMs" section with this one to keep
within self-imposed 30 questions limit.
Thanks again for taking your time to review and test
"Git User's Survey 2009"!
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2009-06-29 23:21 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
2009-06-29 23:21 ` Jakub Narebski [this message]
[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=200906300121.44903.jnareb@gmail.com \
--to=jnareb@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).