public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Rekindling Gentoo News -> Paying for news
Date: Mon, 23 Jan 2017 06:57:43 +1300	[thread overview]
Message-ID: <20170123065743.5093af2b@katipo2.lan> (raw)
In-Reply-To: <assp.019554771d.12835251.giaNYXg4P6@wlt>

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

On Sun, 22 Jan 2017 12:17:25 -0500
"William L. Thomson Jr." <wlt-ml@o-sinc.com> wrote:

> I do not see businesses spending money on Gentoo for a variety of factors. As 
> a business owner myself I have no incentive. Gentoo would waste my money and 
> not direct it toward development. Gentoo has no plans to use the money to 
> further development.
> 
> I would be better off doing what companies do now. Hire people who are Gentoo 
> developers, and/or can become one. Then I can pay them to do directly what I 
> want. By passing anything within Gentoo, Trustees, Council, etc.
> 
> Companies are doing this now. They have no reason to give money to Gentoo

When you talk about yourself, I think you're not asking the right question.

Given:

- There are opensource organisations
- There are companies that give them money
- This is a thing
- These organisations typically don't have focused directed outcomes from said
  donations ( because if the donations were earmarked it would be a payment,
  for services rendered, not a donation )

Why do companies give their money away?

Also, have you considered Gentoo *could* create workflows where given gentoo
developers do specified volumes of work, planned in advance, for pay, using
money given to them by organisations? 

Grant Structure.

And its not like Gentoo doesn't need developers, or have lots of ugly things
that require somebody to basically be a full time developer to get it done.

Hence, Companies that *USE* Gentoo are the primary audience *because* they use Gentoo,
and are thus a natural benefactor from any Gentoo improvement.

And as Gentoo is important to their businesses success, it makes sense to invest in that
infrastructure you're otherwise getting for free.





[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-01-22 17:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15  7:41 [gentoo-project] Rekindling Gentoo News Matthew Marchese
2017-01-15  9:11 ` Seemant Kulleen
2017-01-15  9:36 ` [gentoo-project] Re: [gentoo-dev] " Michał Górny
2017-01-15  9:43   ` Matthew Marchese
2017-01-15 14:22 ` [gentoo-project] " Andreas K. Huettel
2017-01-15 22:20 ` M. J. Everitt
2017-01-19 21:35 ` [gentoo-project] Rekindling Gentoo News -> Paying for news William L. Thomson Jr.
2017-01-22 13:58   ` Kent Fredric
2017-01-22 16:21     ` William L. Thomson Jr.
2017-01-22 16:57       ` Kent Fredric
2017-01-22 17:13         ` William L. Thomson Jr.
2017-01-22 17:00       ` Kent Fredric
2017-01-22 17:17         ` William L. Thomson Jr.
2017-01-22 17:57           ` Kent Fredric [this message]
2017-01-22 18:16             ` William L. Thomson Jr.
2017-01-22 17:02       ` Kent Fredric
2017-01-22 17:21         ` William L. Thomson Jr.
2017-01-22 17:41           ` Kent Fredric
2017-01-22 17:51             ` William L. Thomson Jr.
2017-01-22 18:04               ` Kent Fredric
2017-01-22 17:05       ` Kent Fredric
2017-01-22 17:27         ` William L. Thomson Jr.

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=20170123065743.5093af2b@katipo2.lan \
    --to=kentnl@gentoo.org \
    --cc=gentoo-project@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox