On Tue, Apr 29, 2025 at 02:12:22PM +0200, Roi Martin wrote: > Actually, when I was reading SshAccess [1] in the Savannah documentation > I found these paragraphs: > > SSH access is allowed for registered users who are a member of at > least one active Savannah group. If you are not a member of any group, > then you can use anonymous https access. > > [...] > > If you're not member of any Savannah group, no account will be created > on the system - you will have your web account, but not system > access. A system account will be created after you become a member of > at least one active group. > > And I somehow thought that requesting access to the "emacs" group [2] > would give me *read-only* access to their repositories.
No, such a request makes the user a pending member, and pending memberships don't count. Can you suggest an improvement for that page that would have prevented your misinterpretation? > What do you mean by "use the 'member' clone"? Is it just cloning the > repo via SSH? I mean that the command line will be just like for the members of the group, though it would be read-only until admins of that group approve your membership, e.g. git clone jroimar...@git.savannah.gnu.org:/srv/git/emacs.git > > The authenticated access must be more stable. If you wish, we could > > arrange it for you meanwhile. > > If that means more work on your side or you doing something special, no > worries, I can wait until you roll out the new infrastructure. If it is > something easy, then having a more stable authenticated access would be > great. But, again, I don't want to put more work on you. No much work. I've just added you to one of orphaned groups. Please try.
signature.asc
Description: PGP signature
