git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [RFC] Git User's Survey 2008
Date: Thu, 24 Jul 2008 01:30:30 +0200	[thread overview]
Message-ID: <200807240130.31649.jnareb@gmail.com> (raw)
In-Reply-To: <200807231654.18019.robin.rosenberg.lists@dewire.com>

Dnia środa 23. lipca 2008 16:54, Robin Rosenberg napisał:
> onsdagen den 23 juli 2008 15.18.40 skrev Johannes Schindelin:
>> On Wed, 23 Jul 2008, Jakub Narebski wrote:
>>> On Wed, 23 Jul 2008, Johannes Schindelin wrote:
>>>> On Wed, 23 Jul 2008, Jakub Narebski wrote:
>>>> 
>>>>>    04. Which programming languages you are proficient with?
>>>>>        (The choices include programming languages used by git)
>>>>>        (zero or more: multiple choice)
>>>>>      - C, shell, Perl, Python, Tcl/Tk
>>>>>      + (should we include other languages, like C++, Java, PHP,
>>>>>         Ruby,...?)
>>>> 
>>>> Yes, I think this should be a long list.
>>> 
>>> I'd rather not have a "laundry list" of languages.  I have put C++
>>> because QGit uses it, Java because of egit/jgit, PHP for web
>>> interfaces, Ruby because of GitHub and because of Ruby comminity
>>> choosing Git.  I should perhaps add Emacs Lisp, HTML+CSS and
>>> JavaScript here.  What other languages should be considered?
>> 
>> C# at least, since we had one (pretty unsuccessful) attempt at 
>> reimplementing Git in it.
> 
> What is the reason for the question? Do we want to know what languages
> people would like to contribute to Git in or do we want to know what "kind"
> of programmers are attracted by Git?  Making it a long list should make
> it easier to tabulate the responses.

The idea is, I think, to know what languages people could contribute
to Git; see analysis of this question at GitSurvey2007 page on git wiki:
  http://git.or.cz/gitwiki/GitSurvey2007#head-ecb5564d71e4093e2e93e508380407a26dbcbdea

C++ is for QGit, Java for egit/jgit, C# for git#/widgit and perhaps
Git-Cheetah, PHP for web interfaces, Ruby because of GitHub, Python
because some contrib is in Python, Emacs Lisp for git.el, HTML+CSS
and JavaScript for web interfaces; perhaps we should also add AsciiDoc
for documentation.  And of course "I am not programmer" response...

But I'm not too tied to this question; I guess it can be simply
removed if it doesn't offer some important (for us) information.

-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2008-07-23 23:31 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23  1:25 [RFC] Git User's Survey 2008 Jakub Narebski
2008-07-23  4:39 ` Junio C Hamano
2008-07-23  7:47   ` HP-UX issues (WAS: Re: [RFC] Git User's Survey 2008) Miklos Vajna
2008-07-23 21:38     ` Jakub Narebski
2008-07-23 23:45       ` Miklos Vajna
2008-07-23 11:06   ` [RFC] Git User's Survey 2008 Jakub Narebski
2008-07-24 11:46   ` Marek Zawirski
2008-07-24 12:09     ` Mailing lists, was " Johannes Schindelin
2008-07-25 17:23       ` Shawn O. Pearce
2008-07-25 18:49         ` Junio C Hamano
2008-07-25 21:52           ` Jakub Narebski
2008-07-25 21:57             ` Shawn O. Pearce
2008-07-25 22:11               ` Junio C Hamano
2008-07-25 22:13                 ` Shawn O. Pearce
2008-07-26 10:54                   ` Jakub Narebski
2008-07-26 12:19                     ` Marek Zawirski
2008-07-26 21:50                     ` Shawn O. Pearce
2008-07-26 21:52                       ` Jean-François Veillette
2008-07-25 22:15               ` Petr Baudis
2008-07-26 15:51               ` Jing Xue
2008-07-26 16:47                 ` Jakub Narebski
2008-07-26 17:51                   ` Shawn O. Pearce
2008-07-26 18:17                     ` Jakub Narebski
2008-07-26 19:06                       ` Johannes Schindelin
2008-07-26 18:38                     ` Scott Chacon
2008-07-24 14:07     ` Jakub Narebski
2008-07-23  9:53 ` Johannes Schindelin
2008-07-23 13:08   ` Jakub Narebski
2008-07-23 13:18     ` Johannes Schindelin
2008-07-23 14:54       ` Robin Rosenberg
2008-07-23 16:00         ` Johannes Schindelin
2008-07-24 10:44           ` Jakub Narebski
2008-07-23 23:30         ` Jakub Narebski [this message]
2008-07-23 23:33           ` Johannes Schindelin
2008-07-23 23:53           ` Stephan Beyer
2008-07-24  5:02             ` david
2008-07-24  8:57               ` Stephan Beyer
2008-07-24 10:37                 ` david
2008-07-24  9:52             ` Jakub Narebski
2008-07-26 15:34               ` Jakub Narebski
2008-07-27 11:24                 ` Nguyen Thai Ngoc Duy
2008-07-23 16:43     ` Junio C Hamano
2008-07-24  0:10       ` Jakub Narebski
2008-07-23 14:54   ` Dmitry Potapov
2008-07-23 16:02     ` Johannes Schindelin
2008-07-23 17:01     ` Stephan Beyer
2008-07-24  8:24       ` Jakub Narebski
2008-07-23 17:17   ` Alex Riesen
2008-07-24  8:15     ` Jakub Narebski
2008-07-23 14:12 ` Stephan Beyer
2008-07-24 22:22   ` Stephan Beyer
2008-07-23 14:38 ` Dmitry Potapov
2008-07-23 15:43   ` Matthias Kestenholz
2008-07-23 20:09     ` Dmitry Potapov
2008-07-23 21:49   ` Jakub Narebski
2008-07-24 18:08     ` Dmitry Potapov
2008-07-24 21:06       ` Jakub Narebski
2008-07-23 21:44 ` Petr Baudis
2008-07-23 21:59   ` Jakub Narebski
     [not found] ` <169F15EC-1A58-4C2A-84FC-3D14F7B4F1C5@yahoo.ca>
2008-07-23 22:46   ` Miguel Arroz
2008-07-23 23:49   ` Jakub Narebski
2008-07-24 10:11     ` Sverre Rabbelier
2008-07-24 14:45 ` Jon Loeliger
2008-07-24 18:18   ` Jakub Narebski
2008-07-24 18:50     ` Lachele Foley (Lists)
2008-07-24 21:08       ` Jakub Narebski
2008-07-24 17:57 ` Dmitry Potapov
2008-07-24 18:42   ` Jakub Narebski
2008-07-31 12:48 ` Jakub Narebski
2008-08-20  1:08 ` [RFC v2] " Jakub Narebski
2008-08-20 11:34   ` Alex Riesen
2008-08-20 12:04     ` Petr Baudis
2008-08-20 13:50       ` Jakub Narebski
2008-08-20 18:18         ` Alex Riesen
2008-08-20 20:14   ` Junio C Hamano
2008-08-21  1:30     ` Jakub Narebski
2008-08-21  3:10       ` Junio C Hamano
2008-08-21 11:19         ` Jakub Narebski
2008-08-20 21:18   ` Stephan Beyer
2008-08-20 21:26     ` Stephan Beyer
2008-08-21 11:11     ` Jakub Narebski
2008-08-21 21:26       ` Stephan Beyer
2008-08-22  0:06         ` Jakub Narebski
2008-08-21  3:22   ` Mike Gant
2008-08-24 21:36   ` Stephan Beyer
2008-08-25  0:41     ` Jakub Narebski
     [not found]       ` <20080825012653.GB28160@leksak.fem-net>
2008-08-25  1:56         ` Jakub Narebski
2008-08-20  7:31 ` Abhijit Bhopatkar
2008-08-25 22:08 ` [RFC v3] " Jakub Narebski
2008-08-28  0:28   ` Stephan Beyer
2008-08-30  1:33 ` [RFC v4] Git User's Survey 2008 (cover letters) Jakub Narebski
2008-08-30 19:00   ` Garry Dolley
2008-09-01  7:47   ` Paolo Ciarrocchi

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=200807240130.31649.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg.lists@dewire.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).