[Osmf-talk] Core OpenStreetMap software development and support
hbogner at gmail.com
Thu Dec 7 11:00:51 UTC 2017
I agree with "Komяpa".
OSMF is here to support OSM, not to controll it.
"The OpenStreetMap Foundation is an international not-for-profit
organization supporting, but not controlling, the OpenStreetMap Project.
It is dedicated to encouraging the growth, development and distribution
of free geospatial data and to providing geospatial data for anyone to
use and share"
More avalilable at: https://blog.openstreetmap.org/about/
Further more, if you want to help: go and map, get more
mappers(male/female/martian/..., african/asian/european/ penguin/...),
organise workshops/education, help OSMF working groups, advocate OSM
usage, ..., there is a lot that can be done :D
On 04.12.2017 11:47, Darafei "Komяpa" Praliaskouski wrote:
> I'd like to flag an issue with our core software development process.
> openstreetmap.org <http://openstreetmap.org> is a complex system of
> many different servers being currently maintained by operations
> working group. Server hardware are being regularly taken care of, even
> though OWG consists of volunteers.
> If we look at https://github.com/openstreetmap we can see that project
> consists of many parts from software point of view. Some of them are
> maintained (notably JOSM, iD and openstreetmap-carto), but that's not
> the case for the rest. Let's have a look at what happened since June:
> openstreetmap-website, the rails application powering most of osm.org
> <http://osm.org> -
> 81 commits by Tom Hughes, mostly being security and policy tweaks;
> 19 commits by Bryan Housel, mostly being iD editor version bump;
> 18 commits by Andy Allan, mostly being refactorings.
> 277 open issues, 34 non-merged pull requests.
> cgimap, c++ application powering /map call -
> no commits.
> Both projects have major performance issues known for a year, with a
> prototype fix:
> https://github.com/Komzpa/fastmap. There is also an issue with
> replication diffs being implemented on top of unsuitable postgres
> mechanism that may cause data loss in diffs and resurrection of old
> data: https://github.com/openstreetmap/operations/issues/154
> mod_tile/renderd, c toolchain powering our tile servers:
> no commits. 77 issues raised. 19 pull requests waiting to be merged.
> has an issue of under-utilizing rendering server capacity.
> There is big comment on what needs to be improved by apmon:
> osm2pgsql, c(++) application powering our tile servers:
> 10 commits. 84 issues. 8 pull requests open.
> Lack of resources to fix core issues is sometimes leading to
> workarounds that prevent growth:
> - issues with scalability of rendering cluster led to bans and blocks
> of different web sites using openstreetmap's tiles;
> - issue with API database scalability was worked around as "limit
> changeset size to less objects" instead of fixing the underlying API
> slowness and timing out issue. Discussions just blocked after merge:
> OSMF was created as an organization to support the OpenStreetMap
> project and not shape the community. I think that this is precisely
> where OSM needs support and ask OSMF board to provide a way for us all
> to get out of the situation.
> osmf-talk mailing list
> osmf-talk at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the osmf-talk