public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William L. Thomson Jr." <wlt-ml@o-sinc.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Rekindling Gentoo News -> Paying for news
Date: Sun, 22 Jan 2017 12:17:25 -0500	[thread overview]
Message-ID: <assp.019554771d.12835251.giaNYXg4P6@wlt> (raw)
In-Reply-To: <20170123060052.622b7950@katipo2.lan>

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

On Monday, January 23, 2017 6:00:52 AM EST Kent Fredric wrote:
> On Sun, 22 Jan 2017 11:21:12 -0500
> 
> "William L. Thomson Jr." <wlt-ml@o-sinc.com> wrote:
> > > It may be worth considering getting volume licensing, ie: advertise to
> > > companies to either buy a block of subscriptions themselves which they
> > > can
> > > grant access to X number of people.
> > 
> > Not sure what you mean by advertise.
> 
> On the "Subscribe" page, you get a "Single Developer Subscription" option,
> and a "Company Subscription" option.

Are you implying a paying subscription to a newsletter that should be free? I 
was under the impression you mean like paying for actual advertising, like 
spots in the news letter or on the website.

> Though it would have to be a pretty sizeable company with a lot of staff
> using Gentoo, or the discounted rate would have to be substantiative to work
> out for them.

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

-- 
William L. Thomson Jr.

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

  reply	other threads:[~2017-01-22 17:17 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. [this message]
2017-01-22 17:57           ` Kent Fredric
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=assp.019554771d.12835251.giaNYXg4P6@wlt \
    --to=wlt-ml@o-sinc.com \
    --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