git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Benoit SIGOURE <tsuna@lrde.epita.fr>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git discussion list <git@vger.kernel.org>
Subject: Re: Git User's Survey 2007 partial summary
Date: Mon, 27 Aug 2007 10:57:16 +0200	[thread overview]
Message-ID: <F4DF90B6-7169-4F67-B41D-4AF97D41C5E5@lrde.epita.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0708270946280.28586@racer.site>

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]

On Aug 27, 2007, at 10:48 AM, Johannes Schindelin wrote:

> Hi,
>
> On Sun, 26 Aug 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?
>
> No.  These questions are just questions.  Git is GPLv2, and it will
> probably stay that forever, so you are _free_ to start a commercial
> support scheme for Git, but others are free not to choose it.
>
> I for one could imagine training people, and giving technical  
> support for
> companies needing that support.

You seem to imply that GPLv3 would prevent any form of commercial  
support for Git...

Section 4 of GPLv3:
"you may offer support or warranty protection for a fee."

-- 
Benoit Sigoure aka Tsuna
EPITA Research and Development Laboratory



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 186 bytes --]

  reply	other threads:[~2007-08-27  8:57 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 [this message]
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=F4DF90B6-7169-4F67-B41D-4AF97D41C5E5@lrde.epita.fr \
    --to=tsuna@lrde.epita.fr \
    --cc=Johannes.Schindelin@gmx.de \
    --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).