[RFC] Refining the way we communicate deprecations/wide-reaching changes to the project


Stephen Augustus
 

Forwarding here as well, if anyone is interested in leaving feedback.

-- Stephen

---------- Forwarded message ---------
From: Stephen Augustus <stephen.k8s@...>
Date: Wed, Dec 2, 2020, 22:56
Subject: [k8s-steering] [RFC] Refining the way we communicate deprecations/wide-reaching changes to the project
To: Kubernetes developer/contributor discussion <kubernetes-dev@...>
Cc: steering <steering@...>


Hey Kubernetes Community,

tl;dr -- words are hard sometimes and we should take some time and care to assess the way we wield them.

---

As we go through deprecations and infrastructure changes in the project, it might be a worthwhile exercise to assess and refine the way we communicate them.

I can think of a few recent examples that caused some panic and required additional lift from contributors to reframe or contort/extend support to accommodate:
We should consider what it means to turn down a service, piece of functionality, or kubernetes/kubernetes-adjacent system and type of impact it may have for consumers.

Without policing contributors, as maintainers of the project, we also have a responsibility to users to be careful and deliberate with our communications outside of the project, whether it be Twitter, Hacker News, etc., etc.

So how can we improve?

I think depending on the scope of a change, the following SIGs should be involved in crafting comms:
  • SIG Architecture
  • SIG Release
  • SIG Docs
With SIG ContribEx to assist with consistent delivery across our properties.

I'm curious to hear everyone's thoughts here.

-- Stephen

--
You received this message because you are subscribed to the Google Groups "steering" group.
To unsubscribe from this group and stop receiving emails from it, send an email to steering+unsubscribe@....
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/steering/CAOqU-DRtVQRC79v1xM5zVpQ11hWoyqdhgrhOamkVQ3%2B5kJw44A%40mail.gmail.com.

Join cncf-tag-contributor-strategy@lists.cncf.io to automatically receive all group messages.