> Step 2: take responsibility for all the content of that GitHub link being free of copyright infingements, patent violations, etc.
You already do this when using any open-source software (because your legal right to use it depends on upstream's legal right to distribute it to you), so if any other FOSS license is okay then so is AGPL by this metric.
> And you missed step 0: convince the boss there’s a good reason why your e-commerce storefront needs to have a link to a GitHub page on it.
You already do this for license text / copyright info when using software under nearly any other FOSS license (unless you thought those attribution requirements in the MIT/ISC/BSD/etc. licenses were mere suggestions?).
You already do this when using any open-source software (because your legal right to use it depends on upstream's legal right to distribute it to you), so if any other FOSS license is okay then so is AGPL by this metric.
> And you missed step 0: convince the boss there’s a good reason why your e-commerce storefront needs to have a link to a GitHub page on it.
You already do this for license text / copyright info when using software under nearly any other FOSS license (unless you thought those attribution requirements in the MIT/ISC/BSD/etc. licenses were mere suggestions?).