@pangoSE I supposed we’ve pulled your leg enough now, but you were asking for it
Obviously the WMF and the OSMF are really the only two larger global organisations in the space of crowd source data and there are lots of similarities between the organisations, but many differences too. In any case your question is quite justified.
But to understand the joking you need to know that the WMF is widely considered to have completely lost its way and purpose. You might want to start off reading User:Guy Macon/Wikipedia has Cancer - Wikipedia (5 years old now), and then go on to more recent material on running ads in developing countries, claiming that there is a danger of WP being shut down even though it could easily be run for dozens of years with existing funds. Or the millions that were spent over the last couple of years devising a strategy of which the most notable outcome was creating a paid API service with the sole paying customer google already being the the largest donor to the organization.
So while most people would agree that there is a lot that can be learnt from the WMF, it is mainly what -not- to do.
PS: to be fair the WMF does do lots of good things, it is just buried in a pile of …
I think, their practice of trying (and paid for) multiple different ways of improving and innovating the service, and then discarding some, might work for OSMF. Currently OSMF operates from a point of necessity: not enough options, so we have to settle for what we have or can afford.
I thought that (per " Wikipedia has Cancer" linked already above) their need to try and throw away multiple different approaches in parallel was simply due to having too much money, and keeping fundraising rolling to support the size of the organisation for its own sake rather than any technical need?
One aspect of the WMF which we could copy at least to a small extent is how they support additional projects besides Wikipedia. Wikimedia Commons and Wikidata are quite large and significant initiatives in their own right (even though they have obvious synergies with Wikipedia), and I find some of the smaller projects such as Wikivoyage useful as well.
For the OSMF, this could mean integrating things like OpenHistoricalMap. There’s a recurring pattern of conflict where people attempt to add data to OSM that don’t really belong (say, former railway lines). These conversations would be a lot less heated if there was some other place for them to put it. And it would be a lot easier for an organization that already knows how to to run the infrastructure for a crowdsourced map database to host another instance than it is for someone to start an independent project + organization from scratch.
Not a comment on WMF itself (I simply don’t know enough) but a reminder that the easiest way to not have projects fail, is to never attempt any projects! That’s not too justify failure but a view that we need to be comfortable with some risk of failure if we want to progress more projects. The key thing is learning and not repeating mistakes; much easier said than done!
While I would agree with the sentiment, this is actually part of what I suggested in the Overture thread, the WMF has been massively criticized by the Wikimedia commons community (and other secondary projects) for barely keeping them on life support.
When evaluating the WMFs efficiency (or rather lack thereof) I think it is important to concentrate on what the involved and affected communities say (and not what right wing conspiracy theorists conjure up)…
Maybe I misunderstood you, so… at the risk of taking seriously a reply that was meant as a joke:
This triggers me a lot. If the WMF (or OSMF) has tons of money they don’t need then they should either do something useful with it, or save it for future needs and stop asking for donations as if they’re desperately dying.
If I’m understanding this correctly, they received 160M$ in cash donations/contributions between June 30 of 2021 and 2022?
From the “Wikipedia has Cancer” page I got the same impression as @SomeoneElse:
That it has been used for some (long term) widely used services instead of those being either run by their devs on their own HW or being migrated to a properly supported (by the OSMF) production service.