How to handle two teams, one without Satis, one with (and a composer.lock)

We have two teams
- one in a country where internet is fast enough to require a Satis (also they're mostly doing remote-work so there's not one LAN in which we can set up a Satis for them)
- one in China were everything which is not hosted in China is slow as hell, unreliable, sometimes blocked in Which we have a satis

As this is a end-user project, we're using a composer.lock, however if I understand correctly, the composer.lock contains information on where the packages have been downloaded, which mean that if we commit it, then people from the other team will got problem when doing their `composer install` , right ?

of course one solution would be not to commit the composer.lock, but I guess it's far from being optimal

The issue names Satis, Composer, composer.lock, and composer install but mentions no files or tests. Start by clarifying the expected workflow for both teams and reviewing the relevant Composer and Satis documentation; done means a documented, agreed recommendation for using the lock file across both environments.

Written by the indexing model from the issue text.