With over 500 open issues it is fairly difficult for contributors to identify issues with high importance to work on. We have the good first issue label to indicate low hanging fruits suitable also for less experienced developers. But we don't have any good starting point to find the most important tasks.
This is not meant as a list for newcomers, it is mostly about strategic issues that need substantial work but that are significant to make progress on other things and to really move the style forward.
[ ] the move to the flex backend, #4431, mostly needs discussion and consensus building on if or not to have the separate transport tables, a few smaller issues with the admin boundary rendering need addressing but fixes for those have already been suggested.
[ ] disentangling the use of blue and purple color in the style, currently blue colors are used very non-systematically for various often unrelated features (transport symbols - #3631, several different kinds of water related symbols, cycleways, water lines and polygons). And the use of purple for admin boundaries (#3489) is constraining us quite massively in improving consistency of our color scheme. Requires working on consensus. Solving this would facilitate addressing a large number of issues, in particular
1224
1748
1781
1793
1934
3461
3670
3896
3895
[ ] developing a data preprocessing strategy, needed in particular for getting rid of the remaining non-OSM data - see #2172, requires working on a consensus how to approach this.
[ ] developing a strategy on rendering of explicit and implicit road access restrictions, #214, requires working on a consensus how to approach this - depending on the outcome of this could mean major cartographic redesign of the roads rendering, in particular needed for consistently depicting road mapping differentiated by means of transport (like cycling roads, bus only roads etc.)
Much of this has consensus building as the main first prerequisite. See also #3951.
With over 500 open issues it is fairly difficult for contributors to identify issues with high importance to work on. We have the good first issue label to indicate low hanging fruits suitable also for less experienced developers. But we don't have any good starting point to find the most important tasks.
This is not meant as a list for newcomers, it is mostly about strategic issues that need substantial work but that are significant to make progress on other things and to really move the style forward.
1224
1748
1781
1793
1934
3461
3670
3896
3895
Much of this has consensus building as the main first prerequisite. See also #3951.