project VS awesome-haskell-sponsorship

It is now maintained by this club, I think: https://openwebdocs.org

Open Web Docs is a potential model to draw inspiration from regarding funding: https://openwebdocs.org

Presumably, PostgreSQL has leaders who are responsible for steering the ship. If the project is going to succeed long-term, those leaders have to find ways to keep their contributors happy while also creating an organizational structure that leads to good docs.

Sorry if any of my comments came off naive or obtuse when it comes to open source dynamics. But the reality is that you need good docs, and I'm just trying to give an honest assessment from my experience of the conditions that lead to good docs.

Estelle and the other folks working on Open Web Docs are on the receiving end of sponsorship, and she says she personally has a hard time asking for money. Or to reimburse things like a Grammarly subscription. "Will people get upset if the team meets up in person and uses sponsorship to cover air fare (which, to be clear, OWD didn't do)?"

> Elsewhere in this thread is a link to a separate organization called "OpenWebDocs," which appears to be an outside consortium that contributes to MDN.

Yes, that's what Open Web Docs is. It's funded by individual and corporate contributions, through https://opencollective.com/open-web-docs/. The money goes to pay writers (currently 2 full time, but we are hiring 2 more) to create and maintain independent open web documentation ("open" in the sense of accessible to everyone, "independent" in the sense that it shouldn't represent any one company's view). Currently our work is pretty much entirely focused on MDN, although that's not necessarily going to be the only thing we ever work on. Our 2021 high-level goals: https://github.com/openwebdocs/project/blob/main/2021-goals.... .

Open Web Docs long term roadmap will be published soon. However, the initial goals are focused on supporting MDN's recent infrastructure transition and contributing to core web technology documentation, browser compatibility data, and JavaScript documentation on MDN Web Docs.