今天，我是来讲故事的，讲我和开源社区、和 DevStream 的故事。 先讲点废话 有趣的故事，总是有些背景的，我也想讲一些。 首先我想讲讲，我理解的开源是什么 开源不

今天要干嘛？ 今天我要给 KubeKey 挑个刺！ 身为一个 KubeSphere Community Member，至今为止我居然没有用过 KubeKey，是不是很过分？说出来都觉得没脸在 KubeSphere 社区立足啊

This is Tiexin Guo, DevStream PMC Chair (an open-source DevOps project with an enthusiastic community.) And today, we are going to talk about code review. Specifically, we are going to talk about: why do we need to do code reviews how to review; how to do code review on GitHub how to review for open-source projects But if you want to get acquainted with some best practices for reviewing code

一、幕后故事 时光荏苒，岁月如梭…… （🤮太文绉绉了，这不是我的风格） 今天我准备聊聊在 GitHub 上如何玩 Code Review。 突发奇想？心血来潮？不是。 咋回事

本文翻译自 Using AWS S3 to Store DevStream State 从 上一个 release 版本 v0.6.0 开始, DevStream 支持通过 AWS S3 来保存状态了。 在这篇博文里，我们准备掩饰如何使用 AWS S3 来保存 DevStream 的状态。 术语 状态（S

In our latest release v0.6.0, using AWS S3 to store DevStream state is supported. In this blog, we are going to demonstrate the usage of AWS S3 to store DevStream’s state files. Terminology State: if you don’t already know about DevStream state, please read this doc and this blog helps, too. Backend: where to actually store the state file. It can be either local or s3 at the moment. Configuration