OpenSSL Communities
Mon 1 Sep 2025 4:26PM

Making TAC members aware of decisions to be taken as initiated via GH interactions

MB Michael Baentsch Public Seen by 72

A few weeks back, PR feedback was given as to "something for the TACs to consider" (see https://github.com/openssl/openssl/pull/28076#discussion_r2269378253).

My question now is: How? Tagging those individual TAC member GH IDs I was aware of didn't work -- but then again, I didn't know GH IDs of the "Individual" reps. So..., is there maybe a handle one could use in such GH discussion to make TAC members aware of the issue? Or would a GH tag (say "TAC attention") be worth while introducing to facilitate that? Or would the content issue have to be manually copied out to this messaging tool to have the TACs consider it? Seems a bit wasteful/cumbersome duplicating information that's already in GH.

The related question: Am I right posting this issue here as the "Individual" member that I am? Or isn't this rather something for all communities to consider? Thanks in advance for any feedback and sorry for the noise: All I want is move forward (or close) a PR...

MB

Michael Baentsch Thu 4 Sep 2025 2:09PM

Regarding the General Discussion group (ref), my understanding is that threads there do not automatically notify all community groups.

This doesn't seem quite intuitive. does it? At least I was of the opinion that General Discussion topics are just that: discussed generally, i.e., across all communities.

However, this group is open to everyone—including newcomers—so anyone can join and participate in the discussion, which is not true for some of the other groups. For now, we may still need to manually invite additional people as needed.

Why not automatically make everyone in every community member of the General Discussion group? That way technical discussions of relevance to all communities can get discussed among all and a person raising a question is not inadvertently leaving out people who may be interested in the topic (or get as confused as I did about who gets to see which messages).

MB

Michael Baentsch Thu 4 Sep 2025 2:13PM

For me, any option works; you can also tag me as an individual member.

Thanks for the offer, @Maxim Masiutin . But a) I don't quite understand why (?), so probably more people would wonder in the same way and b) personally think that tagging specific people is the wrong thing to do if a specific role needs to take action (TACs in this case) as people may rotate in and out of such tasks (and more people may share the role -- and I personally like fail-safe mechanisms not just in software :)