Core team sync 2024-04-29

[PingXie]

1. Security
   1. Process for security updates
      1. Madelyn has an email alias for OCI and Google. @everyone else send Madelyn an email alias for responsible disclosures.
      2. @everyone send an email to Madelyn
2. New client metrics Input output traffic stats and command process count for each client. #327
   1. Should the command metric be incremented on recursive commands?
      1. We should keep the same, we should update the PR to include recursive commands, open a new PR.
3. Ping's slot migration improvement Slot migration improvement #245
   1. Synchronous wait command.
      1. By default wait for 1 or 5 seconds. Add a new timeout argument for CLUSTER SET SLOT.
   2. Send the data as part of the RDB format
      1. The concern was the impact on clients paused for writes. We concluded that it is a separate topic that can be decoupled hence non-blocking. We'll probably flag SETSLOT as a write command, alternatively as may-replicate. The purpose is to pause it duing CLIENT PAUSE WRITE, so it doesn't produce replication.
4. Governance document
   1. Allowing TSC members that aren't maintainers.
      1. For now, let's merge it. We can solve that problem when we get to it.
5. Docs & website
   1. Markdown
      1. Preference for plain markdown instead of custom tags
   2. Pictures?
      1. Yes, we will still support picture. Preference for text based though.
6. Can we forbid corrupt listpacks? = always sanitize on load
   1. Performance impact
      2. Follow up on the investigation to better understand the insertion performance.
7. iovalkey (node-js client)(ioredis -> iovalkey (Node.js client) #329)
   1. Is it a major decision to accept a client
      1. Yes, it's a major decision.
   2. What should we do about node-js
      1. @madolson reached out to Matteo on twitter to invite to slack to discuss what maintainership might look like.