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 11:21:12 -0500 [thread overview]
Message-ID: <assp.0195686bfe.6938331.SymzfF0LRJ@wlt> (raw)
In-Reply-To: <20170123025825.08b86fa6@katipo2.lan>
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
On Monday, January 23, 2017 2:58:25 AM EST Kent Fredric wrote:
> On Thu, 19 Jan 2017 16:35:39 -0500
>
> "William L. Thomson Jr." <wlt-ml@o-sinc.com> wrote:
> > I think the concept is still sound. Linode used to offer a $100 for
> > documentation. That was so well received, they had to stop the program due
> > to the backlog. I would not suggest it for documentation etc. But a
> > newsletter, why not.
>
> I think it would be nice if there was an alternative way to earn newsletter
> access via contribution. Because it does seem strange to me to have to pay
> for a newsletter that describes what you're doing yourself in part.
Not paying for newsletter, paying for some of the content. Given an incentive
to spend time on something that may not be directly beneficial.
> 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.
> Or alternatively, instead of relying on a user-pays model in entity, have a
> corporate sponsorship scheme where we give out the newsletter for free, but
> a company foots a bill in exchange for some thanks/promotional/unobtrusive
> advertising.
Corporate sponsors will only sponsor Gentoo if they have a direct benefit.
Right now with how Gentoo is. There is no reason for anyone to give Gentoo
money, individual or corporation.
The more money is put to further development. The more reasons there will be
to donate or sponsor Gentoo.
> IDK. I'm just throwing out ideas and hoping something sticks long enough to
> be useful :)
Ideas are good, but to many toss out ideas not willing to do the work. Or
understanding what it will take to make such ideas come to reality.
--
William L. Thomson Jr.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-01-22 16:21 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. [this message]
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
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.0195686bfe.6938331.SymzfF0LRJ@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