A tool we use changed to a source-available licence, and the first useful step was working out whether it applies to us at all.
the questions, in order:
1 does the new licence restrict our use?
— ours is internal infrastructure, not a competing
hosted product. it does not.
2 is the version we run affected?
— no. the change is not retroactive.
3 what would change if we did nothing?
— future versions, under the new terms.
4 is there a fork, and is it real?
— yes, and it is six weeks old.
decision: pin the current version, revisit in six months.The reflex is to migrate immediately and the cost of that is a migration performed under time pressure to escape a restriction that does not apply. Writing the four answers down took an afternoon and produced a decision that could be defended, plus a calendar entry — which is the part that stops “revisit later” meaning never. A fork six weeks old is not yet a thing to bet infrastructure on.