You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 - Consider unifying transport with air-transport and separating accommodation #3631, several different kinds of water related symbols, cycleways, water lines and polygons). And the use of purple for admin boundaries (Admin boundaries color is too prominent and conflicts with other potential uses #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
developing a data preprocessing strategy, needed in particular for getting rid of the remaining non-OSM data - see Replace usage of Natural Earth boundaries data #2172, requires working on a consensus how to approach this.
developing a strategy on rendering of explicit and implicit road access restrictions, Render more specific access tags i.e. bicycle, motor_vehicle etc #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.) Rendering specific access tags #4952 has moved us towards a basic strategy, further details need to be worked out.
Much of this has consensus building as the main first prerequisite. See also #3951.
The text was updated successfully, but these errors were encountered:
developing a strategy on rendering of explicit and implicit road access restrictions
the move to the flex backend
as done. In both cases this is just the first step - we have #5027 for further steps regarding the flex backend and database layout. And we still need to work out the details on our overall strategy regarding access restrictions. #4952 has defined the rough direction, but details like in #5025, #4321 and more generally matter of dealing with exceptions for explicit or implicit restrictions (like pedestrian roads where bicycles are allowed) still need discussion and decisions to be made.
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.
Much of this has consensus building as the main first prerequisite. See also #3951.
The text was updated successfully, but these errors were encountered: