1 |
On Thu, 19 Jan 2017 16:35:39 -0500 |
2 |
"William L. Thomson Jr." <wlt-ml@××××××.com> wrote: |
3 |
|
4 |
> I think the concept is still sound. Linode used to offer a $100 for |
5 |
> documentation. That was so well received, they had to stop the program due to |
6 |
> the backlog. I would not suggest it for documentation etc. But a newsletter, |
7 |
> why not. |
8 |
|
9 |
I think it would be nice if there was an alternative way to earn newsletter access |
10 |
via contribution. Because it does seem strange to me to have to pay for a newsletter |
11 |
that describes what you're doing yourself in part. |
12 |
|
13 |
But implementing proof-of-work schemes here is hard and prone to gamification |
14 |
downsides, so I just concede its probably not easy, and leave this question open |
15 |
to somebody else who thinks they know of a useful way. |
16 |
|
17 |
> If people are spending hours putting together a weekly or monthly news letter |
18 |
> simply to inform others. Why not pay them a little for their time? It will |
19 |
> hopefully ensure people are always there to do that. Could help out students |
20 |
> and others. |
21 |
|
22 |
It may be worth considering getting volume licensing, ie: advertise to |
23 |
companies to either buy a block of subscriptions themselves which they can grant |
24 |
access to X number of people. |
25 |
|
26 |
Or alternatively, instead of relying on a user-pays model in entity, have a |
27 |
corporate sponsorship scheme where we give out the newsletter for free, but a company |
28 |
foots a bill in exchange for some thanks/promotional/unobtrusive advertising. |
29 |
|
30 |
This would of course have strict requirements as which sorts of companies could |
31 |
do this, like they'd have to be using Gentoo in some capacity. |
32 |
|
33 |
And that sponsorship model is well used by quite a few OpenSource things, because it |
34 |
looks good for the company to be visibly supporting OpenSource. |
35 |
|
36 |
But like, somebody will probably say they hate this idea because its relying on non-free |
37 |
platforms in some capacity for money or something. *shrug* |
38 |
|
39 |
> |
40 |
> The Developer Spotlight was good to help introduce people in the project to |
41 |
> each other. You may never work with someone but when they are in the spotlight |
42 |
> you gain a bit of insight you may never have had otherwise. Helps everyone get |
43 |
> to know each other. Not just the technical things going on in the project. |
44 |
|
45 |
Side note: I hear LWN are looking for writers https://lwn.net/op/AuthorGuide.lwn |
46 |
|
47 |
So there's opportunity here for whoever does our newsletter may find themselves able |
48 |
to help them out as well, and possibly save some effort in writing for both. |
49 |
|
50 |
Or that could be deemed as a conflict of interest, idk. |
51 |
|
52 |
But I know LWN quote stuff said here all the time, so one of their editors is |
53 |
already a fan in some regards. |
54 |
|
55 |
Maybe we can convince them to come to the dark side? :P |
56 |
|
57 |
Or maybe we can cut some sort of article federation deal, where we show LWN our |
58 |
first drafts of the newsletters, and they get first-pick on any articles, and federate |
59 |
them behind their paywall, and then we release those articles with our own newsletter |
60 |
after the subscription period has passed: |
61 |
|
62 |
https://lwn.net/op/AuthorGuide.lwn # Copyrights and further reproduction |
63 |
|
64 |
> Authors retain the copyrights for their work. |
65 |
> |
66 |
> We ask that you grant LWN exclusive rights to publish your work during the LWN |
67 |
> subscription period - currently up to two weeks after publication. |
68 |
> |
69 |
> Thereafter, we retain the right to publish the material, and release it under the |
70 |
> Creative Commons Attribution-ShareAlike 4.0 license (CC BY-SA 4.0). |
71 |
> |
72 |
> After the subscription period, authors may republish their work however they wish. |
73 |
|
74 |
|
75 |
IDK. I'm just throwing out ideas and hoping something sticks long enough to be useful :) |