[bathtub365]

Putting a restriction on the definition of open source that limits discussion to those with the time and ability to submit patches sounds, to me, like the opposite of openness. A piece of open source software being used by people outside the development group is a resounding endorsement of both the product itself and the model of open source development that led to the product being so accessible. Developers know that writing software is hard, and receiving criticism or feedback on software you worked on can be hard, too, but I think it’s ultimately to the benefit of the community of both developers and users that shortcomings (or unexpected behaviour) in the software are known. It helps people make informed decisions on what software they choose to use in their personal life, or even what software they trust to run their business on.

[sjwright]

It's not a restriction on the definition of open source. A truly open source marketplace has space for apps that do shitty things—and for forks that do fewer shitty things.

If anything is a restriction of open source, it's demanding that the developers of Atom implement a feature the way you want. If you don't like their code or their stewardship, badgering them on this one point doesn't fix the underlying difference in principles.