How can a PM help Open Source? Where to begin?

Question

Project management

Prehistory
I've been working as a PM for six years now. I organize, improve the efficiency of project workflows, manage product changes, vision, in general, everything that a normal PM does.
Actually, all these six years I have been using linux (not always, of course, but this is due to working software standards) and even to some extent I am an evangelist of this system and other open source solutions (I even installed and configured distributions for my wards myself =).
In general, I really like the concept of Open Source, I believe that the future belongs to it and I am ready to invest my time in this future. But I don't know how to help the movement if I don't know how to program.
Question
How can PM help open source projects? Or just a person without knowledge of the code?
Where can you start?

Answer 1

Probably not, either:
What are you good at? Well, as a person.

Answer 2

Option A: at the main job (only after agreeing with top management) to lobby for the publication of source codes for software that does not affect the business.
Option B: get involved in a developing project and lobby for the publication of non-business subsystems there.
Option B: look for a team that wants to be in the OS but without a manager.
Option D: start your own project that solves a specific business problem with the expectation of publishing the source code + look for like-minded people.
Option D: the same as [D], only not of the same mind, but people for denyushka.
Option E: do you use some open source software? If there are ideas on how to improve, errors are noticed, etc. - write about it in the developer's bug tracker.

Answer 3

From searching for bugs and feature-requests. Moreover, it can be mixed with the study of project code in particular and programming in general.

Answer 4

The main problem of Open Source is, let's say, marketing to the smallest detail: the developers do not understand the purposes for which they write each feature and the project as a whole, and they do not write what people really need (there is no experience, they do not know what is needed) , and what they want to write, so they get bicycles with square wheels, which few people even need for nothing, but cool.
If you practiced a critical approach to a certain area, say, development tools, and had experience, then you could greatly improve some Eclipse by adding really necessary things to it, bringing to mind the raw and throwing out not very necessary things that are thrown into eyes in all menus and this creates a typical Linux usability discomfort. At the same time, you yourself might not be a programmer, you would create technical specifications, and others would perform (and you would have experience from using Eclipse by your wards at work, with whom you actively investigated its problems - a critical approach)
That's just the approach itself writing purely free software that people need at best for nothing, this in itself is not marketing science. And for you, Open Source is exactly free, right?