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:51:56 -0500 [thread overview]
Message-ID: <assp.0195ded36b.3102001.ueZV9Wsjym@wlt> (raw)
In-Reply-To: <20170123064115.22479fa2@katipo2.lan>
[-- Attachment #1: Type: text/plain, Size: 1905 bytes --]
On Monday, January 23, 2017 6:41:15 AM EST Kent Fredric wrote:
> On Sun, 22 Jan 2017 12:21:04 -0500
>
> "William L. Thomson Jr." <wlt-ml@o-sinc.com> wrote:
> > I used an example of Linode paying $100 for documentation.
>
> Ok. So, this is probably where we got derailed.
>
> Its not clear *who* is paying for *what*.
Looks like Linode has increased to $250 from $100
https://www.linode.com/docs/linode-writers-guide/
> The outlay gave the impression that it was creating an LWN-esque
> newsletter, which would take income from subscribers who read it.
No, nothing to do with readers. This is about authors. Paying authors.
> Whereas that suggest there is no such association, and the only changing
> hands of money is "somebody" pays an author to write the article, which
> everyone else then receives for free.
Yes that is the idea. Gentoo pays people for content for the GWN. Along with
editors to put it all together.
> And the only source of income is the people requesting articles.
Income is normal foundation. This would come from Foundation funds, how ever
they were gathered.
> You've covered the "<something at gentoo>" -> "<person who writes article>"
> part of the dynamic, but where the money comes from to make this happen,
> and the scheme under which the money is obtained is not entirely clear.
The Foundation has money now. It rarely spends it, thus people rarely donate.
> Looking back I can see now you didn't write that as such, its just how the
> framing turned out:
>
> "Paying for news" -> "who pays for news"? -> "subscribers pay for news"
People always twist and read what I write in their own ways. We all have
filters we view the world through.
> In short though: Depsite how much you write, I seldom find you "clear" to
> read.
Could be culture differences, maybe even language. Even native English varies
around the world.
--
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 17:52 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
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. [this message]
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.0195ded36b.3102001.ueZV9Wsjym@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