On 9/9/25 11:37 AM, G. Branden Robinson wrote:
At 2025-09-09T10:54:29-0400, Chet Ramey wrote:
On 9/9/25 10:23 AM, G. Branden Robinson wrote:
[Martin D. Kealey wrote:]
Savane <https://savannah.nongnu.org/p/administration> (the
software that runs on Savannah) only seems to offer “group
membership” roles as a way to restrict who can make changes,
meaning that all group membership has to be approved by existing
maintainers;
Correct, because "group membership" appears to be its parlance for
"development team".
You can be an administrator or a contributor. I am an administrator
for two groups: Bash and Readline.
In groff's group membership list, categories seem to be arranged a
little differently, into "technicians", "tracker managers", and "group
admins".
https://savannah.gnu.org/project/memberlist.php?group=groff
But this wouldn't be the first time I've noticed Savannah's site
documentation being a bit loose with terminology. On other hand, I am
an irascible stickler for same, and swift to critique inconsistency.
Being a contributor means being one of the developers: "Type below the
name of the group you want to contribute to. Joining a group means
getting write access to the repositories of the group, and involves
responsibilities."
Can you share a link to where you see that?
https://savannah.gnu.org/my/groups.php
if it does implement observer status then that feature is not
enabled on Savannah.
Anyone can be an observer.
Does that mean they get emailed on all ticket activity (barring the
ticket being marked "private", I suppose--a feature groff has never
used)?
That I don't know. I am pretty sure that anyone can see any activity on
an issue that's not marked `private' using the web interface. I have
things set so that bug-bash gets support and bug notifications via email,
but not patch notifications. (I should add `all updates' to those.)
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU [email protected] http://tiswww.cwru.edu/~chet/
