Provide field in server/client to disclose source code repository for forks

[KiTTYsh]

Problem

When self-hosting, operators may make changes to the code they are hosting. Disclosing the modified code is a requirement of AGPL, to my understanding, either explicitly or upon request.

In my particular case example, I have used AI to tackle a couple of bug fixes. The easy answer might be to push those changes upstream, but I don't understand the changes the AI made and cannot make a PR to the project in good faith as a result, so my next step in licensing compliance is to disclose my fork. I do not maintain a marketing site for my instance, which might've been the next logical place to disclose such information.

I'd like to avoid the friction of requiring contact to retrieve the source code, but even if that were the route that I wanted to take, it also comes to mind that my contact information isn't disclosed anywhere user-facing, either.

Proposal

Create an environment variable or database-held configuration option, an attribute in /.well-known/fluxer, and a display field in the client, potentially somewhere close to the version information in the settings sidebar, to link to the source code that is currently powering the server.

Notes

Conceptual result:

Checks

• I searched existing discussions.

[Kamalaja]

This may be something we do, however another option is to upload your code to a public git repo

[KiTTYsh]

Creating a public git repo would be a prerequisite.

This idea provides the operator with a clean way to associate their running instance with that repository.

[Kamalaja]

Makes sense! I think the most likely locations would end up being here and in communities as well, due to federation.