git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Christian Chavez <x10an14@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Are there any publicly known funders (companies or otherwise) of git development?
Date: Fri, 19 Mar 2021 21:02:46 +0000	[thread overview]
Message-ID: <YFURduetSoPW/Scd@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAF6oXFsnvvacvUY89s65us7-UprpvV-NaOQ3owGTF25xcJqnkg@mail.gmail.com>

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

On 2021-03-19 at 19:31:56, Christian Chavez wrote:
> Hi!
> 
> Idle curiosity question - stemming from an argument with somewhat
> inebriated co-worker(s):
> > How is the Git development (being an open-source product) pro bono? Done for free?
> 
> Or is there any (publically known - not just an employee "randomly"
> being told to upstream a bugfix) funded effort?
> Such as with the Linux kernel project - where companies/organizations
> put up money for X amount of time/efforts/projects?

There are people in the Git development community who usually work on
Git most or full time as part of their role.  That doesn't mean those
patches immediately make it to the list (oftentimes they are tested and
deployed internally first), but they do generally work on Git most of
the time and their patches do eventually show up on the list.

There are also people who work on Git with their employer's 20% time.  I
believe we have several such contributors here in this case.

There are also people like me who usually contribute independently.  I
have sent patches upstream that directly benefit my employer by fixing a
direct need (in some cases written during work hours, in some cases not,
depending on my employer at the time), but the vast majority of my work
is independent and done on my own time.  There are others who just
contribute independently altogether because they enjoy it.

I would say that of the top 20 contributors historically, I know that 4
fit into the first category, 2 fit into the second category, and 3 more
have some other corporate affiliation known to me (but not into what
category they fall).  There are others who have more recent
contributions who are also known to send patches on behalf of their
employer.  I just don't know about the rest, mostly because it hasn't
come up in context and it's never been important to me.

There are some employers that are well known to employ people in the
first and second categories, as well as some that are known to have
staff that send patches on behalf of their employer.

Hopefully that answers your question reasonably well, even if it's a
little vague because I lack all the details.
-- 
brian m. carlson (he/him or they/them)
Houston, Texas, US

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2021-03-19 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 19:31 Are there any publicly known funders (companies or otherwise) of git development? Christian Chavez
2021-03-19 21:02 ` brian m. carlson [this message]
2021-03-22 11:54   ` Theodore Ts'o

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=YFURduetSoPW/Scd@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=x10an14@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.
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).