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: Thu, 19 Jan 2017 16:35:39 -0500 [thread overview]
Message-ID: <assp.0192ba2613.2248857.4jRD0FCrXs@wlt> (raw)
In-Reply-To: <ed389bf7-581f-941c-2247-9c118ec4b626@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1891 bytes --]
I was trying not to chime in, but I figured I will toss it out there. Its in -
nfp archives I think.
When I was a Trustee, I had ideas of Gentoo paying, very small amounts, for
people to work on a monthly/weekly newsletter. This was something VERY
beneficial to developers and the community. But the high quality that was
produced in the past with the GWN, required considerable time. I felt it was
allot for a volunteer, but since it served such benefit. Why not pay to help
ensure it continues.
At the time it was misconstrued into wanting to pay myself. Despite one of my
first acts in reviewing Draft By Laws publicly on -nfp list, was to remove any
provisions that allowed Trustees to pay themselves. That seemed very wrong,
Trustees decide if they can pay themselves.... I never had plans to pay
myself. Sadly some who harrassed me on such topic where exactly the ones I
wanted to see getting paid... Who later in devrel took part on banning me etc.
Amazing how trying to help others went so south.... :(
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.
If people are spending hours putting together a weekly or monthly news letter
simply to inform others. Why not pay them a little for their time? It will
hopefully ensure people are always there to do that. Could help out students
and others.
The Developer Spotlight was good to help introduce people in the project to
each other. You may never work with someone but when they are in the spotlight
you gain a bit of insight you may never have had otherwise. Helps everyone get
to know each other. Not just the technical things going on in the project.
That is up to the community and Trustees.
--
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-19 21:35 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 ` William L. Thomson Jr. [this message]
2017-01-22 13:58 ` [gentoo-project] Rekindling Gentoo News -> Paying for news 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.
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.0192ba2613.2248857.4jRD0FCrXs@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