Like a business, the success of open source is generally not solely dependent on the quality of the engineering alone. That is, where success is defined by popu

Like a business, the success of open source is generally not solely dependent on the quality of the engineering alone. That is, where success is defined by popularity, # of public contributors/users, etc. Also like a business, you don’t try to do everything — you delegate against your weaknesses. You just need to convince one social person to contribute, and cover whatever social media nonsense is required. Note that any project that scales in count eventually becomes primarily a human management and communication problem, irrespective of what’s being produced, or how. Either drop the goal of scaling up, or set your expectations accordingly (and delegate as needed). Of course, sometimes doing nothing at all is all you need (a few users uses it successfully, and it spreads by word of mouth), but really this is just delegation by accident. Your users are taking the responsibility of communication onto themselves (and it will eventually fragment as different gossip ping groups get split-brained), and the project will eventually centralize communication or die under its own weight.