To be fair, we can be doing better with regards to making sure the source code for changes which are pushed to prod are immediately available on our public repository. We are in the middle of migrating from gitlab to a self-hosted gitea instance, and when we have CI deploying from gitea, this will be sorted out.
The GNU AGPL license is a very stringent license. Personally I love it because the silicon valley douchebros haven't found a way to undermine it yet. It works for Mastodon, and it should work for us - but it requires extra steps to be in strict compliance. Legally speaking, the upstream developers have access to our private development repository, and if anyone wants a copy of the code running on our public infrastructure, they are entitled to it upon request. We have incorporated git hashes into our version numbers so this can be verified.
To be fair, we can be doing better with regards to making sure the source code for changes which are pushed to prod are immediately available on our public repository. We are in the middle of migrating from gitlab to a self-hosted gitea instance, and when we have CI deploying from gitea, this will be sorted out.
The GNU AGPL license is a very stringent license. Personally I love it because the silicon valley douchebros haven't found a way to undermine it yet. It works for Mastodon, and it should work for us - but it requires extra steps to be in strict compliance. Legally speaking, the upstream developers have access to our private development repository, and if anyone wants a copy of the code running on our public infrastructure, they are entitled to it upon request. We have incorporated git hashes into our version numbers so this can be verified.