State of the osrm-frontend repository

[fbarbe00]

Hi,
What exactly is the state of the repository? There seem to be a lot of open issues and pull requests.

The docker image hasn't been updated in a while, and does not reflect what can be seen on https://map.project-osrm.org/.

The fork https://github.com/fossgis-routing-server/osrm-frontend (powering https://routing.openstreetmap.de/) seems to have fixed a lot of small issues, why not merge it here?

[frodrigo]

I think we lake of maintainer with knowledge and interest in frontend technologies. The maintainers are more interested in algorithms and data.

@datendelphin I see you are maintaining fossgis-routing-server/osrm-frontend, aren't you ? Maybe you can merge some equivalent PR here or backport some commits... as you also have the maintainer right on this repo ?

[fbarbe00]

I get that! And osrm is an amazing project, because the backend works so well. It'd just be nice if the docker image was updated once to match what is currently visible at https://map.project-osrm.org/.

There are a lot of things that break at the moment, building the docker image with the Dockerfile doesn't work, probably because of the alpine version, since building with alpine:3.7 works fine.

I can try opening a pull request with small fixes, but I don't have experience with this codebase so they'll have to be thoroughly reviewed to see if they make sense.

[fbarbe00]

Done: #381 . I'm quite happy with my changes. Please consider merging and updating the docker image on docker hub

[frodrigo]

@fbarbe00 What do you think of merging this small PR before #324 ?

[michaelschefczyk]

@fbarbe00 Thank you very much for pointing to https://github.com/fossgis-routing-server/osrm-frontend That is very good, but not optimal for self-hosters. The providers are certainly not obliged to consider ease of use for self-hosters in any way. However, in this repository, the attribution is mostly grouped in variables in leaflet_options.js That allows self-hosters to add the legal text required in the respective countries fairly easily and without the need to change that upon every update. The fork has the sponsorship hardcoded in each translation (i18n/xx.js). That is a bit of a hurdle for other uses.