This question was closed
as a dupe of
Personally, I think there's a subtle enough difference to disagree with the duplicate identification and it seems well on the way to being reopened.
But these questions raise a different issue. As they stand, each question has problems: too broad, too similar, and the underlying problem is not specific to FLOSS projects.
But it is a problem which is exacerbated by some aspects of a project being FLOSS. A new, small, and unfunded project does not have some of the advantages of a commercially backed effort in breaking into the growing ecosystems surrounding the 2 main commercial operating systems.
Both Windows and OSX are moving to more and more to a model where users are directed very forcefully to an "App store" as the officially blessed source of new apps. Even Ubuntu has a similar mechanism.
Commercial/Proprietary projects take the costs (time and money) of getting into these stores as just part of the price of doing business. They also have the advantage of providing a single point of contact, with official legal standing, that lets them negotiate with the store owners.
Add to this the growing fear (vs awareness and education) of users around the risks, pros, and cons of installing "unblessed" software and the influence of popular virus checkers.
This all adds up to a (hopefully unintentional) barrier to entry for new FLOSS projects.
So I can see that a question such as "How do I get my FLOSS app approved by the XYZ store?" or "How do I get my FLOSS software whitelisted by ABC Virus checker?" have specific relevance to FLOSS work.
On the other hand, we could end up with almost identical questions for each App Store and each Virus Checker. With answers which may regularly become outdated and inaccurate.
SO has a specific close reason for this type of question:
"Questions about general computing hardware and software are off-topic for Stack Overflow unless they directly involve tools used primarily for programming. You may be able to get help on Super User."
I think we need to decide whether this type of question is on-topic here and - if not - what close reason we should use (assuming we are not yet ready for custom close reasons).
And then, if we decide to let them in, we need to help the OP refine their questions into an acceptable form and try to answer them.