[kakwa_]

I feel this report is missing something when it puts all OSS developers into the same bucket, and somewhat fails to define what an OSS developer actually is.

There is tons of variability depending on many factors like the project complexity, usage or visibility, or the size of the community around it or the audience/userbase.

Technically, I'm an OSS developer, some of my stuff is even packaged in Debian, with a whopping 17 installs according to the package popularity contest... And I cannot say this has burnt me. I get a few bugs reports and PRs here and there and that's all. And I feel most OSS work ends-up in this category, with this report painting a far too bleak picture discouraging people from contributing.

But some projects do become popular or critical pieces of infrastructure, or both. The hobby structure is indeed completely inadequate in such cases. Such projects should not be only held by a solo or a pair of developers coding at night and doing everything.

maybe, they should be offered the possibility to make it their day job, or to have some help from developers doing this as their day job?