git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "Dan Chokola" <dan@chokola.com>
Cc: git@vger.kernel.org,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Andreas Ericsson <ae@op5.se>
Subject: Re: Git User's Survey 2007 partial summary
Date: Tue, 28 Aug 2007 01:48:29 +0200	[thread overview]
Message-ID: <200708280148.29702.jnareb@gmail.com> (raw)
In-Reply-To: <61e816970708262024m1cbbfd4dxfeb10b56397670b8@mail.gmail.com>

On Mon, Aug 27, 2007, Dan Chokola wrote:
> On 8/26/07, Jakub Narebski <jnareb@gmail.com> wrote:

>> 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? 

This question was actually requested on git mailing list to be in
the survey...

This question is to get to know if there is sufficient demand for
commercial git support for it to be viable. There are two possible
outcomes:

If there is enough demand, then company selling git support can make
a living. Company selling support for git means more git user's (because
some corp needs to have commercial/external support to be present) and
possibly more developers. It is possible that some revenue falls to main
git developers, be it by paying somebody to hack on git, or paying for
some feature or for fixing a bug fast.

If there is not enough demand, better to know it from onset that to have
company which tries to provide git support bancrupt. No failed support
company means no bad publicity on git; it _might_ mean that community
support is enogh for git...


Note that commercial (paid) support does not clash
with GPL. One does not need change in license to have commercial
git support. GPL allows paid support.

-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2007-08-27 23:48 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
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 [this message]
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=200708280148.29702.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ae@op5.se \
    --cc=dan@chokola.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.
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).