Peter Johnson

@thinkovation when you say 'our perspective' are you speaking as a representative of this project team?

The domain I'm accessing it from is different from the one listed: https://break.solana.com/start?cluster=devnet

We'd be happy to accept a PR for this, I don't have an ARM Mac so I can't test this unfortunately but we should be able to set it up...

regarding `pbf2json`, we are already building `pbf2json.linux-arm` and bundling it in the `npm` module: ```js path.join(__dirname, 'build', util.format( 'pbf2json.%s-%s', os.platform(), os.arch() ) ) ``` ```bash /tmp ❯ ls -lah node_modules/pbf2json/build...

It was simple enough https://github.com/pelias/pbf2json/pull/107

> Does the scope of this issue include derivatives/auxiliaries like [pelias/libpostal-service](https://hub.docker.com/r/pelias/libpostal-service)? Yes, I think it's all-or-nothing, partial support isn't particularly helpful. We would be happy to accept contributions, I doubt...

Each repo has its own CI script such as this: https://github.com/pelias/api/blob/master/.github/workflows/push.yml#L42 Rather than repeat everything per-repo it just executes this script: https://github.com/pelias/ci-tools/blob/master/build-docker-images.sh

Hi @ddelange, we are planning to discuss this in a team meeting today, can you please hold off any more PRs until we chat about what we'd like to do.

I didn't have time to look through them yet, were there any PRs where the CI failed?