git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Kannan Goundan <kannan@cakoose.com>
Cc: git@vger.kernel.org
Subject: Re: Make
Date: Thu, 22 Oct 2015 19:05:24 -0700	[thread overview]
Message-ID: <xmqq37x2qqzf.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <loom.20151023T013752-72@post.gmane.org> (Kannan Goundan's message of "Thu, 22 Oct 2015 23:46:28 +0000 (UTC)")

Kannan Goundan <kannan@cakoose.com> writes:

> Thanks for the explanation.  I didn't realize some projects don't want to
> initialize all their submodules, but the explicit opt-in idea you described
> sounds nice.
>
> I've seen cases where people will financially "sponsor" feature development
> in open source projects.  Is there any precedent for this in the Git
> project?  Is it ok to use this mailing list to ask about such things?

We are unfortunately not set up to handle money well.  For a
background explanation, please go read [*1*], which I wrote my take
on "money" some time ago.  Note that it is an explanation and not a
justification.  It explains why we are not set up to handle money
well and what the issues around money that are troublesome for the
project are.  It does not mean to say that it is a good thing that
it is hard to buy feature with money from our project [*2*].

I do not see (and back then in the discussion I do not think anybody
saw) how we can make "We, a sponsoring company, pay this money to
the project to fund effort Y." work well.  But that of course does
not mean it is impossible to make it work--somebody with a fresh
perspective may come up a way to do so, and that would be a very
welcome development.


[Footnote/Reference]

*1* http://thread.gmane.org/gmane.comp.version-control.git/264993/focus=265215

*2* Just like my message that you are responding to was an
    explanation of the reason why we do not recurse and and
    initialize all submodules by default.

  reply	other threads:[~2015-10-23  2:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 22:50 Make "git checkout" automatically update submodules? Kannan Goundan
2015-10-15 23:21 ` Junio C Hamano
2015-10-22 23:46   ` Make Kannan Goundan
2015-10-23  2:05     ` Junio C Hamano [this message]
2015-10-23  3:46       ` Make "git checkout" automatically update submodules? Kannan Goundan
2015-10-23  6:19         ` Christian Couder
2015-10-23 17:15         ` Junio C Hamano
2015-10-23 17:20 ` Stefan Beller
2015-10-23 19:11   ` Junio C Hamano
2015-10-23 22:51   ` Kannan Goundan

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=xmqq37x2qqzf.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=kannan@cakoose.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).