You can use arrow keys to navigate in the map.
Writing access is a quality of life improvement for developers but not needed for non devs. Voting rights on C level decisions need not to be tied to being a developer and thus should not be tied to writing access.
It would make things easier if we could give developers writing access without promoting them to full voting rights.
Our developer selection process is not robust enough to grant write access to any repo in any scenario.
No non-maintainer should be given voting rights.
It creates a difficult atmosphere if a non-maintainer entity (a company with its personal agenda could buy votes, for example) defines the direction of the project.
Maintainer is just a word for someone with voting rights and writing access. That doesn't mean that anybody can just get voting rights after separating the two. There still can be the same process in place as now for getting them. Essentially people can get write access without voting rights.
A lot of the people vote without knowing the full consequence of a decision. This could skew the vote. Many votes cast are with the feeling of "whatever I'm just here to code". I think we should take that into consideration while distributing voting rights.