Revision: 828
http://svn.savannah.gnu.org/viewvc/?view=rev&root=administration&revision=828
Author: ineiev
Date: 2025-05-15 10:16:12 -0400 (Thu, 15 May 2025)
Log Message:
-----------
update on VCS access for non-members of any group
Modified Paths:
--------------
trunk/sviki/IdleAccounts.mdwn
trunk/sviki/SshAccess.mdwn
Modified: trunk/sviki/IdleAccounts.mdwn
===================================================================
--- trunk/sviki/IdleAccounts.mdwn 2025-05-13 15:41:56 UTC (rev 827)
+++ trunk/sviki/IdleAccounts.mdwn 2025-05-15 14:16:12 UTC (rev 828)
@@ -18,6 +18,7 @@
follows for 2 weeks, it may be removed. In order to prevent
this, it's sufficient if you do anything from this list:
+<a id="non-idle"></a>
* post a new item in any tracker;
* comment on any item in any tracker;
* actually join any group (mere requests for inclusion don't count).
Modified: trunk/sviki/SshAccess.mdwn
===================================================================
--- trunk/sviki/SshAccess.mdwn 2025-05-13 15:41:56 UTC (rev 827)
+++ trunk/sviki/SshAccess.mdwn 2025-05-15 14:16:12 UTC (rev 828)
@@ -4,9 +4,11 @@
one active Savannah group. If you are not a member of any group, then you
can use anonymous https access.
-Members of a group have write access to that group's version control
-trees and read-only access to the version control trees of other
-public groups.
+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.
The registered GPG keys are not used by Savannah for SSH operations,
even when they include authentication-capable subkeys.
