Snowdrift is an interesting experiment for fundraising platforms because it ramps up contributions based on how many other contributors there are, incentivizing accountability to stakeholders rather than the all-or-nothing approach of threshold pledge funding models like kickstarter.
Oh hey, cool! That’s the new website I’m building.
Happily I was able to convince the team to let me try to launch the beta site in Elm - though it’s because we ran out of Haskell developers and the old codebase was becoming a maintenance burden. As a kid I dabbled in Haskell and loved the Pure FP paradigm but found it too hard to work with (until I found Elm!) and Elm is the only language I love enough to pour such hours into, so I volunteered to do a rewrite knowing that I’d be the only Elm dev for now (but happily planning to teach people and see how the Elm error messages treat them!) and it’s been a fun, albeit slow, journey.
On a more serious note, Snowdrift may actually be more relevant here than just the tech stack. Elm’s creator @evancz has long grappled with the compromises of funding methods for FLO projects like his programming language. Back then he talked about typical funding methods such as being backed by large companies, and the perverse incentives that tend to arise. While it’s not ready just yet, Snowdrift may offer exactly the solution he is looking for. I volunteer for Snowdrift because I think there’s a major need for it in the world. Some teasers from his thread:
I have thought a lot about how to support folks like that in a full-time role so they do not need to make trade-offs like that to meet the expectations of some users, but even if there was a magic wand to get money for that, I’d want to be extremely careful about the long-term incentives it would create.
The main point is that I really think that people underestimate the role of funding in supporting good working relationships in open source languages.