On Sat, 26 Jul 2025 00:20:05 +0200, Alex Muntada wrote:
Hi,
Oh, hi, what a pleasant surprise :)
Tooling for inactive group members ================================== Existed when we used Alioth, has been discussed a few time since then without any results --> remove from TODO list?Just a couple of days ago I realized that gitlab shows the last activity date on the members list of any group or project, so https://salsa.debian.org/groups/perl-team/modules/-/group_members?with_inherited_permissions=exclude&sort=oldest_last_activity shows the list of direct members (i.e. excluding members coming from debian group) with the oldest last activity first. This date is for any kind of activity in salsa, not only for the modules group context, but I guess it's better than nothing.
Right; I think I also discussed this with another team member 2 years ago; and I'm less optimistic than you -- sure this can be a lower bound (as in: someone who has no activity on salsa in the last N years obviously hasn't done any commits to pkg-perl as well) but in the end it doesn't tell use anything about contributions to pkg-perl (when all activity was somewhere else). But yes, we could remove the no-activity-at-all people.
Using this link as an owner of the modules group, should be easy to walk through the list of members and remove those that don't match the minimum amount of activity. For instance, 15 members out of 127 have no activity since 12.0 was released on June 10th, 2023.
Ok, that sounds good.
Unfortunately, using the API won't work since last_activity_on from /users/:id is available to admins only.
Salsa admins? I guess so, since we are both "owners" and won't get any higher :)
Web scraping could work using the data in <div class="js-group-members-list-app" data-members-data=...> but I'm not sure it's worth the effort.
Ack.
On the other side, there are direct members that are already members through the debian group. I'm guessing that those could be removed and the total amount of 127 direct members would decrease notoriously.
Ack.
I think many of those memberships were added when migrating from alioth because we didn't know yet that groups could become members of other groups too.
I might also be partially responsible for that -- I seem to remember that I added DDs explictly, because -- not sure; to make sure they have all necessary permissions or to make them "real/full" team members, or something? But yes, that's all a bit murky …
Hope this helps!
Totally, thanks for picking up this topic, and I hope you will continue to think and work in this area :)
Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe`-
Attachment:
signature.asc
Description: Digital Signature