Regarding the readonly git clones for savannah users. It's nice to have
the recently-added text on the SshAccess page:
Members of a group have a write access to that group's version control
trees and a read-only access to the version control trees of other
public groups. Since 2025-05, any
[[non-idle accounts|IdleAccounts#non-idle]] also have a read-only
access to repositories of public groups.
(Aside: the "a"s should be deleted in "a write" and (2x) "a read".)
However, I suggest going further. The above says it's possible, but few
people will read it there and even fewer will know what command to run
for a given repo (I admit I'm not 100% sure myself).
1) Thus, for more visibility of this feature, I suggest providing the
requisite commands on the auto-generated "Git Repositories" pages such as
https://savannah.gnu.org/git/?group=emacs
https://savannah.gnu.org/git/?group=automake
Right now, those pages strongly imply that https must be used for any
readonly checkout. I imagine a new stanza along these lines on those pages:
"Readonly clone for any Savannah user:
git clone git://...
"
And also perhaps change the label "Member clone:" to
"Read/write clone for group members:", since "member" feels pretty
general. Perhaps even "for GRPNAME group members", where GRPNAME is
the name of the group.
2) I also notice that some packages, notably
https://savannah.gnu.org/projects/emacs
advertises
git clone https://git.savannah.gnu.org/git/emacs.git
as the way to get the repo in their "public info".
Eli, maybe that's something you'd like to change?
3) Finally, I suggest sending a note to savannah-announce about the
git:// alternative for readonly access to any repo, for savannah users.
The more that can be done to get people off https, the better for
everyone. Presumably. --thanks, karl.
