git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Dan Chokola" <dan@chokola.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git User's Survey 2007 partial summary
Date: Sun, 26 Aug 2007 23:24:18 -0400	[thread overview]
Message-ID: <61e816970708262024m1cbbfd4dxfeb10b56397670b8@mail.gmail.com> (raw)
In-Reply-To: <200708270251.05762.jnareb@gmail.com>

On 8/26/07, Jakub Narebski <jnareb@gmail.com> wrote:
> 04. Which programming languages are you proficient with?
>
> It losk like there is only 3/4 people proficient in Perl as compared to
> Python; it looks like Python is more popular. C is most popular, with
> only a few (if everything is all right with the results page) people
> proficient in Tcl/Tk. I'm sorry, git-gui and gitk guys; it looks like
> not many developers...
>

Ruby people, represent! (Hopefully I'm not the only one.)

> 28. Which (main) git web interface do you use for your projects?
>
> Most use gitweb (which is distributed with git), 7 use cgit, 1 wit
> (Ruby), most probably XMMS2 project, 1 git-php (I wonder who...), and
> there are 20 "other" answers, which I am most curious about. What are
> they?
>

All right! Someone actually uses my crappy Wit interface!

> 55. Would commerical (paid) support from a support vendor be of interest
> to you/your organization?
>
> Only 44 answers yes, 217 no, 126 not applicable (which was menat to
> encompass people who do not use git for work).
>

Are questions like this at all indicative of where Git is looking towards going?

> --
> Jakub Narebski
> Poland

-- 
Dan Chokola

  parent reply	other threads:[~2007-08-27  3:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-18 23:28 Git User's Survey 2007 Jakub Narebski
2007-08-18 23:59 ` Jakub Narebski
2007-08-19 12:17   ` Matthieu Moy
2007-08-25 22:26   ` Jakub Narebski
2007-08-19 13:03 ` Jan Engelhardt
2007-08-27  0:51 ` Git User's Survey 2007 partial summary Jakub Narebski
2007-08-27  1:40   ` Shawn O. Pearce
2007-08-27  9:01     ` Johannes Schindelin
2007-08-27 11:15     ` Jakub Narebski
2007-08-27 11:28       ` Gábor Farkas
2007-08-27 12:23         ` David Kastrup
2007-08-27 13:19           ` Gábor Farkas
2007-08-27 13:50             ` Johannes Schindelin
2007-08-27 13:55               ` David Kastrup
2007-08-27 12:27         ` Mike Hommey
2007-08-27 13:31           ` Gábor Farkas
2007-08-27 11:42       ` Johannes Schindelin
2007-08-27 15:42       ` Torgil Svensson
2007-08-27  3:24   ` Dan Chokola [this message]
2007-08-27  8:48     ` Johannes Schindelin
2007-08-27  8:57       ` Benoit SIGOURE
2007-08-27  9:26         ` Johannes Schindelin
2007-08-27  9:54     ` Andreas Ericsson
2007-08-27 23:48     ` Jakub Narebski
2007-08-27  5:45   ` David Kastrup
2007-08-27 15:43     ` Theodore Tso
2007-08-27  8:07   ` Benoit SIGOURE
2007-09-02  8:33 ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=61e816970708262024m1cbbfd4dxfeb10b56397670b8@mail.gmail.com \
    --to=dan@chokola.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).