From: Jakub Narebski <jnareb@gmail.com>
To: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Git User's Survey 2007
Date: Mon, 30 Jul 2007 02:21:23 +0200 [thread overview]
Message-ID: <200707300221.23511.jnareb@gmail.com> (raw)
In-Reply-To: <4d8e3fd30707290950lce19ef4g103cbb7ad1abbe23@mail.gmail.com>
Paolo Ciarrocchi wrote:
> On 7/27/07, Jakub Narebski <jnareb@gmail.com> wrote:
>> First there is a question about the form of survey. Should we use web
>> based survey, as the survey before (http://www.survey.net.nz), sending
>> emails with link to this survey, or perhaps do email based survey,
>> with email Reply-To: address put for this survey alone?
>
> I vote for the survey.net.nz approach. I think that from a user
> prospective that's the right thing to do, we can have "multiple choice
> questions" and avoid some of the more common mistakes.
I think it also better (especially that I started devising questions
with multiple-choice and single-choice answers in mind...).
>> Third, where to send survey to? I was thinking about git mailing list,
>> LKML, and mailing list for git projects found on GitProjects page on
>> GIT wiki. Do you want to add some address? Or should info about GIT
>> User's Survey 2007 be sent also to one of on-line magazines like
>> LinuxToday, or asked to put on some blog?
>
> I think that one of the mistakes I did when I sent out the first
> survey was to not contact any magazines and blog.
Any proposals? Besides LWN, NewsForge, Slashdot?
>> ----
>> About you
>>
>> 1. What country are you in?
>
> I know that lot of people will disagree with me but from a pure
> statistical prospective I'd like to add a couple of questions about
> gender and age.
>
> I understand very well that these questions will not be useful for
> making git any better but it will be interesting to have a better
> picture abut the git customer base.
I'm not sure it would add any important informatant information;
although "age" (years, or age bracket?) could be useful.
>> How you use GIT
>> 8. Which porcelains do you use?
>> (zero or more: multiple choice)
>> - core-git, cogito, StGIT, pg, guilt, other
IsiSetup
> git-gui ?
>
>> 9. Which git GUI do you use
>> (zero or more: multiple choice)
>> - gitk, git-gui, qgit, gitview, giggle, other
tig, instaweb, (h)gct, qct, KGit
I consider git-gui an UI (like qgit or tig), not a porcelain. To be
a porcelains tool need to add some SCM functionality not present in
git-core.
> How about adding a question about whether the user migrated from a
> different SCM? If so, from which SCM and why?
I have added, suggested [somewhat] by Andy Parkins, the following
set of questions:
----
Other SCMs
1. What other SCM did you use?
2. What other SCM do you use currently?
3. What other SCM do you use as a main SCM for your project
instead of git, if any? Why?
* example: Mercurial, better MS Windows support
5. What would you require from git to enable you to change,
if you use other SCM for your project?
4. Do your git repository interact with other SCM? Or what SCM
did you import from? What tool did/do you use?
* examples: CVS, import: fromcvs, interaction: git-cvsserver;
Subversion, git-svn
----
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-07-30 0:21 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 1:58 Git User's Survey 2007 Jakub Narebski
2007-07-25 16:19 ` Marco Costalba
2007-07-26 4:52 ` Steven Grimm
2007-07-27 11:20 ` [RFC] " Jakub Narebski
2007-07-27 12:21 ` Nguyen Thai Ngoc Duy
2007-07-27 13:01 ` Andy Parkins
2007-07-27 19:07 ` Jakub Narebski
2007-07-28 8:02 ` Andy Parkins
2007-07-29 16:50 ` Paolo Ciarrocchi
2007-07-29 17:05 ` Paolo Ciarrocchi
2007-07-30 0:21 ` Jakub Narebski [this message]
2007-07-30 3:35 ` Shawn O. Pearce
2007-07-30 13:40 ` Jakub Narebski
2007-07-30 7:44 ` Paolo Ciarrocchi
2007-07-30 13:26 ` Jakub Narebski
2007-07-30 19:26 ` David Kastrup
2007-07-30 21:12 ` Junio C Hamano
2007-07-30 21:37 ` Jakub Narebski
2007-07-30 22:38 ` David Kastrup
2007-07-30 21:25 ` Nguyen Thai Ngoc Duy
2007-07-30 21:35 ` Jakub Narebski
2007-07-30 20:56 ` [RFC (take 2) " Jakub Narebski
2007-07-31 0:32 ` Shawn O. Pearce
2007-07-31 0:45 ` Jakub Narebski
2007-07-31 1:09 ` Shawn O. Pearce
2007-07-31 1:24 ` Junio C Hamano
2007-07-31 1:31 ` Shawn O. Pearce
2007-07-31 11:22 ` Jakub Narebski
2007-07-31 11:33 ` Paolo Ciarrocchi
2007-07-31 12:30 ` Jakub Narebski
2007-07-31 16:35 ` Git User's Survey 2007 - web survey site Jakub Narebski
2007-07-31 19:07 ` Paolo Ciarrocchi
2007-08-02 4:51 ` Martin Langhoff
2007-08-02 13:04 ` Paolo Ciarrocchi
2007-08-04 0:50 ` [RFC (take 3)] Git User's Survey 2007 Jakub Narebski
2007-08-04 5:41 ` Shawn O. Pearce
2007-08-04 12:10 ` Jakub Narebski
2007-08-04 7:40 ` David Kastrup
2007-08-05 20:06 ` Jakub Narebski
2007-08-06 0:29 ` Johannes Schindelin
2007-08-05 9:30 ` Asger Ottar Alstrup
2007-08-06 1:17 ` Jakub Narebski
2007-08-06 5:48 ` Asger Ottar Alstrup
2007-08-06 15:44 ` Jakub Narebski
2007-08-05 20:51 ` [RFC (take 4)] " Jakub Narebski
2007-08-14 1:51 ` [RFC (final)] " Jakub Narebski
-- strict thread matches above, loose matches on Subject: below --
2007-08-14 22:38 [RFC} " 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=200707300221.23511.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=paolo.ciarrocchi@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).