community

community copied to clipboard

Why migrate

KubeEdge is now a CNCF incubating project, migrating slack to CNCF will make it easier to communicate with other communities, and CNCF's slack will also have more historical discussion records.

How to migrate

We will follow the table below to migrate some channels to CNCF's slack. @fisherxu I will archive the channels on that schedule.

To join CNCF slack -> https://slack.cncf.io/

Status	Channel	Users	Date	Migrator	CNCF Channel
	general	>1500	2023.11.30	@fisherxu	kubeedge
	dashboard	<50	2023.11.30	@fisherxu	kubeedge-dashboard
	announcement	>1000	2023.11.30	@fisherxu	kubeedge-announcement
	kubeedge-docs	>1000	2023.11.30	@fisherxu	kubeedge-docs
	kubeedge-dev	>1000	2023.11.30	@fisherxu	kubeedge-dev
	sig-ai	>50	2023.11.30	@jaypume	kubeedge-sig-ai
	sig-robotics	10	2023.11.30	@Poorunga	kubeedge-sig-robotics
	sig-device-iot	>100	2023.11.30	@fisherxu	kubeedge-sig-device-iot
	sig-security	15	2023.11.30	@kevin-wangzefeng	kubeedge-sig-security
	sig-mec	>100	2023.11.30	@kevin-wangzefeng	kubeedge-sig-mec
	summer-of-code	>100	2023.11.30		NA

Migration tasks

• [x] Send out notifications in more community channels about the migration
• [x] Create corresponding Channels under CNCF slack workspace (once created, all users are recommended to start use the new slack channels)
• [ ] #185
• [x] Change channel name in KubeEdge slack and export data including members list and public channel chat history
• [x] Import data to cncf slack workspace (we will need someone from CNCF admin team to help on this)

Thanks @fisherxu for initiating this. Also FYI to all the community members that this have been discussed among @kubeedge/tsc members, and we think the migration is helpful to improve community transparency and neutrality.

I'll second this, would be better for more exposure as well.

Follow-up steps we need to do:

0. Send out notifications in more community channels about the migration
1. Create corresponding Channels under CNCF slack workspace (once created, all users are recommended to start use the new slack channels)
2. Update all slack relevant links, point to new address of KubeEdge slack channels
3. Change channel name in KubeEdge slack and export data including members list and public channel chat history
4. Import data to cncf slack workspace (we will need someone from CNCF admin team to help on this)

/lgtm

Channels under CNCF workspace has been created:

• kubeedge https://cloud-native.slack.com/archives/C066UJZJKQE
• kubeedge-dashboard https://cloud-native.slack.com/archives/C066LNA3015
• kubeedge-announcement https://cloud-native.slack.com/archives/C067DTAF4Q1
• kubeedge-docs https://cloud-native.slack.com/archives/C06718RDHCJ
• kubeedge-dev https://cloud-native.slack.com/archives/C06718TB6F4
• kubeedge-sig-ai https://cloud-native.slack.com/archives/C067DTGJJM7
• kubeedge-sig-robotics https://cloud-native.slack.com/archives/C066LNMUME3
• kubeedge-device-iot https://cloud-native.slack.com/archives/C067Q8J3KTJ
• kubeedge-sig-security https://cloud-native.slack.com/archives/C067Q8LC3T2
• kubeedge-sig-mec https://cloud-native.slack.com/archives/C06716458P5

Archiving time of channels in KubeEdge workspace will be postponed to 11.30, to allow more users to have enough time to migrate.

@kevin-wangzefeng @fisherxu i would highly recommend that notification needs to be posted on each current channels on KubeEdge slack as well.

Sure, thanks for the your reminder :) we will send the notification to each current channels this week