On Sat, 25 Jan 2025 at 17:40:26 +0100, Jonas Smedegaard wrote: > When I post to a discussion at Salsa, then for how long is my post > publicly available?
In general: until the project containing the discussion is deleted. A "project" in Gitlab jargon is the thing that wraps a git repository; more precisely it contains a git repository, an optional issue tracker, an optional wiki, an optional container registry and so on, depending which features were enabled by the project owner. Archiving a project, which is what we (should) do with e.g. obsolete packages that are removed from unstable, doesn't count as deletion: your contributions to discussions in an archived project continue to be part of that project. (I assume the Salsa admins do have a way to permanently redact a discussion thread that contains something illegal or abusive, if it becomes necessary.) > My guess is that my post disappears when the git-repo-project considers > the conversation obsolete (e.g. when a merge request is adopted or > dropped) This is not the case. For example, https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/483 is obsolete (in the sense that we merged the final version of the proposed change), but my review comments on it remain, and so do the 4 older versions of the MR that Paride pushed before we merged the 5th version. Similarly, https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/55 could be considered obsolete (it was closed without being accepted) but you can still read it. Similarly, https://salsa.debian.org/utopia-team/polkit-gnome/-/merge_requests/1, https://salsa.debian.org/utopia-team/polkit-gnome/-/merge_requests/2 and https://salsa.debian.org/utopia-team/polkit-gnome/-/merge_requests/4 are merge requests to an obsolete (archived) project corresponding to a package that we removed from unstable, representing all three possible states (!1 was still open when the project was archived, !2 was accepted, and !4 was rejected) and you can still read those too. Issues behave similarly: you can still read https://salsa.debian.org/ci-team/autopkgtest/-/issues/8 (which I filed in the Salsa issue tracker instead of in the BTS, because there was never an uploaded version of autopkgtest in the archive that had that bug: it is a regression that only ever existed "upstream"). smcv
