git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Git User's Survey 2008 partial summary, part 2
Date: Thu, 4 Sep 2008 15:23:37 +0200	[thread overview]
Message-ID: <200809041523.40601.jnareb@gmail.com> (raw)
In-Reply-To: <200809031607.19722.jnareb@gmail.com>

This is partial summary of Git User's Survey 2008 after more that 1600 
(yes, that is more 1.6 _thousands_ responses) just after the 4 days
of running the survey.  It is based on "Analysis" page for this survey:
  http://www.survs.com/shareResults?survey=M3PIVU72&rndm=OKJQ45LAG8
 
We have around 1606 individual responses (excluding 21 responses in the 
'testing' channel), as compared to 683 individual responses for 2007 
survey, and (I think) 115 answers (Base = 115) for 2006 survey. 
That is a lot, especially after so short time since staring the 
survey.


03. With which programming languages are you proficient?

Situation changed a bit since last announcement.  Nor Ruby with 59%
dominates a bit over C with 55%.  I guess this is caused by GitHub
crowd: announcement about this survey was posted on GitHub blog
(thanks defunkt!).
 
There are now 22 responses (around 1%) of "I am not a programmer".
This means that you don't need to be a programmer to use Git.

Popular (from what I have glanced) languages in the 'other' section
include Erlang, Lua, OCaml, Haskell, Objective-C; there is Scala, Vala, 
Smalltalk, R, ActionScript, Prolog, SQL, Forth, and even TeX/LaTeX 
mentioned; someone even wrote Brainfuck here. 


04. How did you hear about Git?

Here 'blog entry' and 'some project uses it' with 38% dominates over 
'Linux kernel news' and 'word of mouth' with 22-24%.

Among 'other' there is quite popular Google Tech Talk about Git by Linus 
Torvalds, available on YouTube (which admittedly probably should be as 
one of choices), LKML (Linix kernel mailing list) which probably some 
put as 'Linux kernel news' and some not, FLOSS podcast, GitHub, Ruby 
adopting Git.  Among more unique and interesting 'other' replies there 
is "Faculty Advisor at NSF REU" and "school Professor", "Ruby community 
just went apeshit all of a sudden" ;-) and "Ruby On Rails switching to 
git overnight"; some individual people line 'Randall Schwartz' or 
'Scott Chacon'.


08. Which Git version(s) are you using? (multiple choices)

Most people use current version of git: 70% use git 1.5.x, and 40% use 
git 1.6.x, and only 3 people use pre 1.3.x version.  Note that some
people use different versions on different machines, or on different 
operating systems, so the numbers do not add to 100%.

Around 8% (123 replies) use 'master' branch.  Sorry Junio, it looks like 
it wouldn't be easy to find/detect bugs as soon as they hit 'master', 
before releasing.  (Unfortunately this survey lack question to find how 
many people run *-rcN (release candidate) version, but it is very long 
as it is with 60 questions and 55 minutes average time of answering 
question, and anegdotical evidence (comments) of requiring around 15 
minutes to fill it without spending much time on free-form questions).


25. How do you publish/propagate your changes? (multiple choices)

Most people (92%) simply push to publishing public repository.  Second 
is 'pull request' with 32%; I guess this includes GitHub social thingy.
git-svn as form of publishing changes is third with 27%; thanks Eric 
Wong!  Format-patch + email is only fourth with 22%, but quite close to 
git-svn and pull-request.

For publishing to other SCMs (32 replies, 2% or responses) people use 
git-bzr, git-p4, git-cvsexportcommit, git-acu (AccuRev); some publish 
to Mercurial, ClearCase or Visual SourceSafe.


To be continued...

P.S. Which non free-form questions are you interested most, BTW?
-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2008-09-04 13:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 14:07 Git User's Survey 2008 partial summary Jakub Narebski
2008-09-03 14:45 ` Shawn O. Pearce
2008-09-03 15:20   ` H.Merijn Brand
2008-09-03 16:25     ` Felipe Contreras
2008-09-04  2:43       ` David Aguilar
2008-09-05 22:17         ` Jan Hudec
2008-09-06  4:17           ` David Aguilar
2008-09-03 15:00 ` David Brown
2008-09-03 15:41 ` Scott Chacon
2008-09-03 16:00   ` Jakub Narebski
2008-09-04 13:23 ` Jakub Narebski [this message]
2008-09-06  2:22 ` Git User's Survey 2008 partial summary, part 3 Jakub Narebski
2008-09-06  5:15   ` Shawn O. Pearce
2008-09-06  8:27     ` Andreas Ericsson
2008-09-07 23:07     ` Jonas Fonseca
2008-09-07 23:47       ` Shawn O. Pearce
2008-09-06 22:17 ` Git User's Survey 2008 partial summary, part 4 - how do we use Git Jakub Narebski
2008-09-07  8:31   ` Andreas Ericsson
2008-09-07  8:44     ` Jakub Narebski
2008-09-11 20:14 ` Git User's Survey 2008 partial summary, part 5 - other SCM Jakub Narebski
2008-09-11 21:03   ` Anatol Pomozov
     [not found]     ` <48C98F92.40903@workspacewhiz.com>
2008-09-11 22:05       ` Jakub Narebski
2008-09-11 21:54   ` Jeff King
2008-09-11 22:51   ` david
2008-09-12 10:44     ` Jakub Narebski
2008-09-13 21:11       ` david
2008-09-13 22:03         ` Jakub Narebski
2008-09-15 11:51       ` Mark Brown
2008-09-14 10:45   ` Nguyen Thai Ngoc Duy
2008-09-14 13:32     ` Jakub Narebski
2008-09-15  3:39     ` david
2008-09-15  7:00       ` Andreas Ericsson
2008-09-16 17:12       ` 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=200809041523.40601.jnareb@gmail.com \
    --to=jnareb@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).