Rename CNCF SIGs to avoid confusion with other types of SIG #549
Comments
|
cc @parispittman -- I believe Paris has been working on alternate names as a part of SIG Contributor Strategy |
|
i never finished it but it's here https://hackmd.io/UWWVsKkrTsuZ7W2x3qxTzA i highly recommend the rename. |
|
Renaming sounds like a good idea to me. I like "TOC <> Council" or "<> TOC Council" (TOCC) It might also be a good idea to come up with a list of choices and hold a vote. My two cents. |
|
How about TOC Advisory Council (TAC)? |
|
@chira001 has proposed renaming for 'Technical Advisory Group' in the Feb 16 TOC meeting. |
|
I'm calling for a vote on the proposal to change the names of CNCF SIGs to CNCF TAGs (technical advisory group). This will also constitute an experiment in TOC voting by GitHub. Please cast your vote by adding a comment in the form +1/-1 [binding]. +1 binding |
|
+1 (non binding) |
|
+1 (non-binding) |
|
+1 (non-binding)
…On Tue, Feb 16, 2021 at 6:47 PM Alex Chircop ***@***.***> wrote:
+1 (non-binding)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#549 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABRTD77VVFRYEVZ5H67VF5LS7L72DANCNFSM4SIOW5YA>
.
|
|
+1 (nb) |
|
+1 (non-binding) |
|
+1 nb
|
1 similar comment
|
+1 nb |
|
+1 non-binding |
1 similar comment
|
+1 non-binding |
|
+1 (non-binding) |
1 similar comment
|
+1 (non-binding) |
|
+1 non-binding |
|
+1 binding |
|
+1 nb |
1 similar comment
|
+1 nb |
|
I was never a fan of overloading the meaning of SIG. This seems like a step in the right direction. |
|
+/- 0 non-binding I agree that "CNCF SIG" is confusing next to "K8s SIG". With my SIG O11y chair hat on, I feel our mode of operation is aligned with how Working Groups in RIPE and IETF work; which is what I model my actions as chair upon. While there are plenty of hits for "Technical Advisory Group" on Google, Wikipedia does not list "TAG" as such and I feel as if uncommon naming might increase confusion. As such, I would personally lean towards "WG" as a strong opinion loosely held. What matters in the end is the work done within the groups. |
|
-1 non-binding Originally, I disliked the name SIG and felt WG (Working Group) was fine, but TOC drove rename/redefinition, including strongly advocating for using exact name as K8s uses. I was never involved in Kubernetes SIGs, but had good experiences with ACM SIGGraph and thought of that as a great model -- a large group of members, where a subset would be more active and contribute to defining programs and activities (where one activity is advising the TOC). Agree that the work is what matters and don't expect that name change will affect the operation of any of the groups. If y'all decided to change the name, I think it will make outreach outside of CNCF require a bit more explanation of the inner workings of CNCF/TOC to explain TAG-Security, maybe we should consider short-hand abbreviated of cn-security, CNSecurity, or cncf/security. Sarah Allen, SIG-Security co-chair |
|
@RichiH we also have WGs though, as part of the SIGs.... |
|
+1 nonbinding |
I do like "Workgroup" > "technical advisory group". But both > "SIG". |
|
@justincormack That is a good point. In my nomenclature, the SIGs would be part of the WGs, but that would be too confusing of a flip and not solve the naming dominance of K8s. Renaming the current SIGs to WGs, and the current WGs to something else would make more sense to me coming from an ISP & networking background, but that is a minority position, which is fine. For the avoidance of bikeshedding I +/-0 on purpose. |
|
+1 non-binding |
1 similar comment
|
+1 non-binding |
|
+1 non-binding |
|
+1 |
|
+1 nb Just a quick note, OpenSSF which is also part of LF uses the WG (Working Group) nomenclature. Maybe it would be a good idea to be aligned with them since both foundations belong to the same parent foundation?
|
|
+1 nb |
|
+1 non-binding |
|
+1 binding with SIGs(TAGs) already having working groups within them, I like that this proposal doesn’t have those potential cascading effects. Plus, I just like TAG. |
|
+1 Binding |
|
It used to create confusion until we starting referring to the groups as "CNCF SIG-X" or "Kubernetes SIG-Y". I hardly hear a mention of any SIG without a preface of the organization it is affiliated with in case the context is not already clear. Semantics matter. Established recognized names also matter. For SIG-Security, the exercise to rename would be exceedingly onerous as it would require:
So here are other solutions to consider:
Or we could just leave it as is. We've got along just fine for a now seemingly long time. When confusion arises, we can always clarify which organization or project does the SIG belong to. |
|
There is undoubtedly confusion - on an almost daily basis I speak with people who are confused between the two forms of SIG. CNCF staff will help support the change. |
|
@lizrice there is definitely some term overloading, but is there enough to disaggregate them at this point? I don't tend to see people being confused and if there is confusion, people tend to ask which one they are discussing. I worry that there will be significant work to modify existing resources which may cause additional confusion when they point at something that has been renamed. K8s has working groups in addition to SIGs. Many CNCF projects have their own SIGs. The term SIG also predates both K8s and CNCF. Perhaps we can raise awareness around the naming convention, say CNCF SIG or K8s SIG (or SPIRE SIG or NSM SIG) instead of just SIG. |
|
+1 non-binding for SIG -> TAG renaming. Initially i found SIGs confusing since it was an unfamiliar term. Its a thing one needs to google once. So, renaming SIG to TAG inside CNCF will not fix the former issue, but at least the latter. |
|
+1 non-binding (and I'm looking forward to the day where SIGs -> K8s and TAGs -> CNCF) |
|
+1 non-binding for SIG -> TAG rename |
|
+1 binding |
2 similar comments
|
+1 binding |
|
+1 binding |
|
K8s SIG Security says "thanks" -- this is indeed a source of confusion! |
|
Retroactive +1 nb! EDIT: Tracking for SIG ContribStrat rename --> cncf/tag-contributor-strategy#99 |
|
The proposal to rename Special Interest Groups to Technical Advisory Groups (#549) has been approved. 8/11 +1 NB 0: -1 |
and others
It's increasingly confusing that we have groups called Special Interest Groups (SIGs) some of which operate at the CNCF-wide level, and others that are project-specific in Kubernetes. Since the Kubernetes project adopted the term first, I propose they should keep the term SIG and we could rename the CNCF-wide ones that report in to the TOC. For similar reasons let's not use Working Group (WG) since some of those exist already.
Some initial ideas:
Thoughts?
The text was updated successfully, but these errors were encountered: