Operations/Minutes/2025-08-07

From OpenStreetMap Foundation

OpenStreetMap Foundation, Operations Meeting - Draft minutes

These minutes do not go through a formal acceptance process.
This is not strictly an Operations Working Group (OWG) meeting.

Thursday 7 August 2025, 19:00 London time
Location: Video room at https://osmvideo.cloud68.co

Participants

Minutes by Dorothea Kazazi, including some notes from Grant.


New action items from this meeting

  • Grant to nudge, let them know that we don't need more than 10 Gbit cards and to propose the server to be used initially as a raster server. [Topic: .tw server]
  • Grant to 1) create AWS account + S3 buckets, 2) start from what we log for raster tiles, and 3) set the logging compression to zstd. [Topic: Vector Tile Logging]

SotM Europe 2025 - OPS meeting

Grant and Tom are planning to go but haven't booked tickets yet.

Paul will do a talk on the Vector Tiles server and a lightning talk for people who want to use the Vector Tiles server.

Suggestions

  • Do an OPS talk/lightning talk. Deadline for submissions: August 31

Decision: Have an OPS in-person meeting after the conference on long-term planning. There is a OPS budget line for travel.


Taiwanese server

They provided a good machine. Grant proposed vector or raster server (good for SA Asia, as currently going through US) - there is a need for both. They will provide the credentials next week.

On network cards

  • They seem they want to provide 100 Gbit network cards (single or dual).
  • We don't need more than 10 Gbit cards.
  • We most likely won't top 1 Gbit, but the 10 Gbit cards are more robust and have more offloading.

Action item: Grant to nudge, let them know that we don't need more than 10 Gbit cards and to propose the server to be used initially as a raster server.


OpenStreetMap Core Software Engineer applications

Topic proposed by Minh. Related to https://blog.openstreetmap.org/2025/08/01/apply-to-be-the-openstreetmap-core-software-engineer/

Decision: public minutes to state "discussed briefly".


Vector Tile Logging

Suggestions

  • Publish the Vector Tile logs, as currently vector tiles go up to zoom 14 and granularity is lost, compared to zoom 18/19.
  • Grant to set up the Fastly components to get the initial data in .csv and preserve the headers.
    • Will use a different S3 account.
    • Create bucket, accounts, permissions initially.
    • Will start from what we log for raster tiles.
  • Grant will set the logging compression to zstd, as it seems supported by Athena.
  • Add extra headers.

Other points mentioned during discussion

  • Current restrictions: 10 requests from 3 unique IPs.

Action item: Grant to 1) create AWS account + S3 buckets, 2) start from what we log for raster tiles, and 3) set the logging compression to zstd.

Pending question: What can we make public?


Any other business

Serving Vector Tiles style

https://github.com/openstreetmap/operations/issues/1263

Currently serving colorful https://vector.openstreetmap.org/demo/shortbread/colorful.json, which discourages people from looking into it. Do we want to host a style for the public to use forever?

Suggestion: Use versioning.

Issue: The assets (fonts, glyphs) are more of an issue than the style.

Options from https://github.com/openstreetmap/operations/issues/1263

  • The status quo, where we host https://vector.openstreetmap.org/demo/shortbread/colorful.json and related assets with CORS headers that allow cross-site usage but don't publish it or commit to hosting a style at that URL.
  • Host colorful.json and assets but use CORS headers to restrict its usage to OSM domains
  • Have openstreetmap-website generate the style JSON but still rely on vector.osm.org for other assets.
  • Commit to publishing a style + assets with CORS headers that allow cross-site usage

Suggestions

  • Make the style as public as possible - incurs a burden.
    • Would need to figure out a url for it.
    • Provide the stylesheet for debugging purposes.

Other points mentioned during discussion

  • The style is more stable than the VT, if shortbread upgrades.
  • Off the shelf it is an invalid style, unless people do customisations.
  • Paul is committed to sticking to shortbread - if we switch to something else, we will use a different style.
  • Previously there was no best practise for sprites.
  • The ticket is a good technical discussion.
  • VT are not very usable to other people unless we provide a stylesheet.

'Decision: follow-up on tickets.


Fastly offered improving caching

Fastly offered us help on improving caching for vector tiles.

On purging

  • Fastly mentions purging as an option in their documentation. They have latency response-times guarantees on purges and also support multiple keys.
  • Wikimedia is doing purges from center to the edge for public access to all of their pages.
  • We might not want to waste time on purging. It might not be too bad for vector tiles.
  • We can do purges based on cache key.

Other points mentioned during discussion

  • Caching for the style is not an easy matter.
  • Tech work for caching style is easy because it changes less frequently.

Action items

  • 2025-07-24 Grant to set-up a test for OWG's review [Topic: Switching www.osm.org to Fastly frontend]
  • 2025-07-24 Grant to do the Mailman 2 to 3 conversion [Topic: Mailing lists] - https://github.com/openstreetmap/operations/issues/1264
  • 2025-07-24 DONE (TomH testing now via osm-website ticket): Grant to investigate getting an Apple developer account via OSMF Business account [Topic: Apple Login]
  • 2025-06-12 Tom still to run OSMDBT test. OPS then to plan a maintenance window for the OSM.org postgres database update. [Topic: OSM.org postgres database]
  • 2025-06-12 DONE (We should have tested planetdump-ng and osmdbt, could test on dev instances instead.): Tom to look into plausibility of OSM.org postgres upgrade: Tom will do a dry-run on a disconnected promoted slave to test upgrade. Secondary will need to be re-synced after the upgrade. Need to confirm the downstream affect on (planet-dump-ng). [Topic: OSM.org postgres database]
  • 2025-06-12OPS to plan a maintenance window for the OSM.org postgres database update. [Topic: OSM.org postgres database]
  • 2025-05-01 Grant to follow-up with Australian hosting again. [Topic: OSUOSL funding / issues]
  • 2025-05-01 Grant to see if other University offers are still available and what hardware would be required. [Topic: OSUOSL funding / issues
  • 2025-03-20 Grant to follow-up with the South African contact about the potential hardware donation from a mobile network. [Topic: New offers of Servers Australia and South Africa]
  • 2025-03-20 Grant to run an SQL query to identify more email providers used by spammers. [Topic: Spam] #2025-05-01 Grant has created a small list of disposable email providers.
  • 2024-09-19 Grant to create an IP blocklist script. [Topic: Cloudflare keep enabled Reportage] - Discussion during 2024-07-25 OPS to make a reasonable evaluation whether to go with Cloudflare, Fastly or none.

Action items that have been stricken-through are completed, removed, or have been moved to GitHub tickets.