3 ms·
> Or is it more a case of, if we're collapsing, we'll put this in place? No-one would trust that. If you are collapsing you aren't going to care enough, or the
by dspillett 9y ago
> Or is it more a case of, if we're collapsing, we'll put this in place?
No-one would trust that. If you are collapsing you aren't going to care enough, or the people who do/did both care and know what to include (source, build toolchain setup, documentation) have already gone.
It is surprising, given how important it could be, how little the clients bother to check that escrow updates are happening - so even if the contract says otherwise it could often come down to this!
> Are you actively syncing to a private Git repo?
Some do that, but in my experience it is more common to provide a snapshot (a full copy of the relevant parts of your repo(s) with supporting documents), with a new snapshot uploaded with each major or minor release. Sometimes it isn't released based but instead the client dictates escrow is updated "at least once per year or X months" which to my mind shows that part of the contract was written by a legal/admin person without a lot of technical experience.