I think I understand the sentiment behind this post. But a few things give me pause:
> Are you willing to pay 50-100 euros/dollars per year to keep MDN afloat?
I've seen some open-source authors/contributors successfully raise enough money, after they'd pledged to work on their project full-time. So the problem might not necessarily be to raise. But money has this uncanny ability to shift a project's focus. What happens when you raise more money than you actually need for the next 3 years (considering the scope of the project)? Will the project just mention that it doesn't need to raise more and just proceed to do what it's supposed to do? All the while spending and raising sensibly? Or will it find novel and creative ways to spend all this extra cash?
> The problem with expecting volunteers to do this sort of work is that they burn out.
Should we assume that once someone gets a salary they're somehow more resilient to burnout? I'd think that the burnout would be due to a volunteer biting much more than they should. So couldn't this also be an issue of work management and allocation?
> The passionate community has nothing to do with anything, unless they’re willing to pay. A profoundly unscientific poll indicates that only about two-thirds of my responding followers are willing to do so.
Is paying the only way to have helpful resources? I mean, we have the Wikipedia and StackExchange models that seem to provide decent value, even if not on par with MDN's standard. Would it be possible to have a model for MDN that meets somewhere in the middle, such as community contributed contents, moderated, reviewed, and edited by both community and full-time, knowledgeable, and paid staff? Unless I'm mistaken, I think the Linux kernel also follows something similar.
> Are you willing to pay 50-100 euros/dollars per year to keep MDN afloat?
I've seen some open-source authors/contributors successfully raise enough money, after they'd pledged to work on their project full-time. So the problem might not necessarily be to raise. But money has this uncanny ability to shift a project's focus. What happens when you raise more money than you actually need for the next 3 years (considering the scope of the project)? Will the project just mention that it doesn't need to raise more and just proceed to do what it's supposed to do? All the while spending and raising sensibly? Or will it find novel and creative ways to spend all this extra cash?
> The problem with expecting volunteers to do this sort of work is that they burn out.
Should we assume that once someone gets a salary they're somehow more resilient to burnout? I'd think that the burnout would be due to a volunteer biting much more than they should. So couldn't this also be an issue of work management and allocation?
> The passionate community has nothing to do with anything, unless they’re willing to pay. A profoundly unscientific poll indicates that only about two-thirds of my responding followers are willing to do so.
Is paying the only way to have helpful resources? I mean, we have the Wikipedia and StackExchange models that seem to provide decent value, even if not on par with MDN's standard. Would it be possible to have a model for MDN that meets somewhere in the middle, such as community contributed contents, moderated, reviewed, and edited by both community and full-time, knowledgeable, and paid staff? Unless I'm mistaken, I think the Linux kernel also follows something similar.