In the AGPLv3 text -after the END OF TERMS AND CONDITIONS line- there is this recommendation on How to Apply These Terms to Your New Programs which rather terse and states that there are many ways to offer source code:[...] If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source. For example, if your program is a web application, its interface could display a Source link that leads users to an archive of the code. There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements. [...]And the section 13 it points back to does not provide much more guidance:[...] through some standard or customary means of facilitating copying of software.So what are actual mechanisms implemented by AGPL-licensed projects for users to get the corresponding source code?for a web application with a UI?for an application with no UI and only a REST API?for a command line application?for a library?
Built-in mechanisms to fetch the corresponding source code for AGPLv3-licensed projects
agpl 3.0;source code