mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-21 02:10:11 +08:00
Merge branch 'LCTT:master' into linux.cn_translate
This commit is contained in:
Chris Li
GitHub
commit
c9b8c06651
@ -3,28 +3,28 @@
|
||||
[#]: author: "Abhishek Prakash https://itsfoss.com/author/abhishek/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-15750-1.html"
|
||||
|
||||
如何逐步将 GitHub 连接到 VS Code
|
||||
详解：如何将 GitHub 连接到 VS Code
|
||||
======
|
||||
|
||||
![][1]
|
||||
![][0]
|
||||
|
||||
VS Code 无疑是最受欢迎的代码编辑器之一。同样，GitHub 是编码人员中最受欢迎的平台。
|
||||
|
||||
两种微软产品都很好地融合在一起。你可以在 VS Code 中无缝编码并将更改推送到你的 GitHub 仓库。从同一个应用界面完成所有这些工作让生活变得如此轻松。
|
||||
两种微软产品可以很好地融合在一起。你可以在 VS Code 中无缝编码并将更改推送到你的 GitHub 仓库。从同一个应用界面完成所有这些工作让生活变得如此轻松。
|
||||
|
||||
如何将 GitHub 添加到 VS Code？ 其实很容易。
|
||||
|
||||
在本教程中，我将展示：
|
||||
|
||||
- 如何将你的 GitHub 帐户集成到 VS Code 中
|
||||
- 如何将仓库从 GitHub 克隆到 VS Code
|
||||
- 如何将仓库从 GitHub 克隆到 VS Code 中
|
||||
- 如何将你的更改从 VS Code 推送到 GitHub
|
||||
|
||||
听起来不错？ 让我们看看如何去做。
|
||||
听起来不错？让我们看看如何去做。
|
||||
|
||||
### 先决条件
|
||||
|
||||
@ -34,13 +34,13 @@ VS Code 无疑是最受欢迎的代码编辑器之一。同样，GitHub 是编
|
||||
|
||||
![Checking if Git is installed via VS Code][2]
|
||||
|
||||
另一件事是你**应该配置 Git 用户名和电子邮件**。
|
||||
另一件事是你**需要配置 Git 用户名和电子邮件**。
|
||||
|
||||
### 将 GitHub 添加到 VS Code
|
||||
|
||||
VS Code 内置了 GitHub 集成。你不需要安装任何扩展来克隆仓库和推送你的更改。
|
||||
|
||||
从左侧边栏转到源代码选项卡。你应该看到 “**Clone Repository**” 或 “**Publish to GitHub**”（如果你已经打开了一个文件夹）选项。单击 **Clone Repository** 并为其提供 GitHub 仓库链接或单击 “**Clone from GitHub**”。
|
||||
从左侧边栏转到源代码选项卡。你应该看到 “<ruby>克隆仓库<rt>Clone Repository</rt></ruby>” 或 “<ruby>发布到 GitHub<rt>Publish to GitHub</rt></ruby>”（如果你已经打开了一个文件夹）选项。单击 “<ruby>克隆仓库<rt>Clone Repository</rt></ruby>” 并为其提供 GitHub 仓库链接或单击 “<ruby>从 GitHub 克隆<rt>Clone from GitHub</rt></ruby>”。
|
||||
|
||||
![Cloning GitHub repo in VS Code][3]
|
||||
|
||||
@ -48,19 +48,19 @@ VS Code 内置了 GitHub 集成。你不需要安装任何扩展来克隆仓库
|
||||
|
||||
![VS Code asking to sign in to GitHub][4]
|
||||
|
||||
你单击“允许”按钮，它将打开 GitHub 登录页面。
|
||||
你单击“<ruby>允许<rt>Allow</rt></ruby>”按钮，它将打开 GitHub 登录页面。
|
||||
|
||||
![Connect GitHub to VS Code][5]
|
||||
|
||||
如果你尝试克隆一个仓库，你应该会看到这样的消息并单击 **Open**。
|
||||
如果你尝试克隆一个仓库，你应该会看到这样的消息并单击 “<ruby>打开<rt>Open</rt></ruby>”。
|
||||
|
||||
![Opening GitHub repo in VS Code][6]
|
||||
|
||||
这应该需要几秒钟，你应该登录到你的 GitHub 帐户。
|
||||
这应该需要几秒钟，你就会登录到你的 GitHub 帐户。
|
||||
|
||||
#### 你怎么知道你已经使用 VS Code 登录到 GitHub？
|
||||
|
||||
好吧，它将开始在顶部视图中显示你的 GitHub 仓库（如果有的话）（如果你之前按下了克隆存储库）。
|
||||
好吧，它将开始在顶部视图中显示你的 GitHub 仓库（如果有的话）（如果你之前按下了“克隆存储库”）。
|
||||
|
||||
![GitHub repos accessible from VS Code][7]
|
||||
|
||||
@ -80,9 +80,9 @@ VS Code 内置了 GitHub 集成。你不需要安装任何扩展来克隆仓库
|
||||
|
||||
![Open a new window in VS Code][9]
|
||||
|
||||
这将为你提供一个全新、干净的编辑器。**如果看到欢迎屏幕**，你可以从那里单击 “Clone Git Repository” 的快速链接。
|
||||
这将为你提供一个全新、干净的编辑器。**如果看到欢迎屏幕**，你可以从那里单击 “克隆存储库” 的快速链接。
|
||||
|
||||
否则，从左侧边栏转到“源码管理”选项卡，然后单击“克隆仓库”按钮。
|
||||
否则，从左侧边栏转到“<ruby>源码管理<rt>Source Control</rt></ruby>”选项卡，然后单击“<ruby>克隆仓库<rt>Clone Repository</rt></ruby>”按钮。
|
||||
|
||||
它将在顶部打开一个视图。你可以**直接复制 GitHub 仓库的 URL**。它可以自动从中获取克隆链接。
|
||||
|
||||
@ -106,23 +106,23 @@ VS Code 内置了 GitHub 集成。你不需要安装任何扩展来克隆仓库
|
||||
|
||||
现在假设你对代码进行了一些更改并希望将提交推送到你的仓库。
|
||||
|
||||
当你将更改保存到文件中，**VS Code 就会开始用 M 指示修改后的文件**。对于新文件，符号为 U（未跟踪）。
|
||||
当你将更改保存到文件中，**VS Code 就会开始用 “M” 指示修改后的文件**。对于新文件，符号为 “U”（未跟踪）。
|
||||
|
||||
从左侧进入源码控制，输入提交消息，然后单击提交旁边的按钮并选择 Commit & Push。
|
||||
从左侧进入“源码控制”，输入提交消息，然后单击提交旁边的按钮并选择 “<ruby>提交并推送<rt>Commit & Push</rt></ruby>”。
|
||||
|
||||
![Push your changes to GitHub from VS Code][14]
|
||||
|
||||
**_如果你没有配置 Git 用户名和电子邮件，你将看到此错误。_**
|
||||
_如果你没有配置 Git 用户名和电子邮件，你将看到如下错误。_
|
||||
|
||||
![Error in VS Code if Git username and email is not set][15]
|
||||
|
||||
你可以[在全局或仓库级别设置用户名和电子邮件][16]。完全根据你自己的选择。
|
||||
你可以 [在全局或仓库级别设置用户名和电子邮件][16]。完全根据你自己的选择。
|
||||
|
||||
> 📋 对于成功的提交和推送，你不会看到任何错误。已修改文件或新文件旁边的 M 或 U 符号将消失。
|
||||
> 📋 对于成功的提交和推送，你不会看到任何错误。已修改文件或新文件旁边的 “M” 或 “U” 符号将消失。
|
||||
|
||||
**你可以通过进入 GitHub 上的仓库来验证你的推送是否成功。**
|
||||
|
||||
你可以选择在本地提交更改而不推送它们。你也可以在这里使用 git 命令执行所有你以前使用过的操作。有用于创建拉取请求、刷新等等的选项。
|
||||
你可以选择在本地提交更改而不推送它们。你也可以在这里使用 `git` 命令执行所有你以前使用过的操作。有用于创建拉取请求、刷新等等的选项。
|
||||
|
||||
![VS Code gives all kind of Git actions to perform][17]
|
||||
|
||||
@ -130,9 +130,9 @@ VS Code 内置了 GitHub 集成。你不需要安装任何扩展来克隆仓库
|
||||
|
||||
有一个专用的官方扩展，让你还可以**管理其他人对你的仓库的拉取请求并合并它们**。你还可以在此处查看在你的仓库中打开中的问题。这是将 GitHub 与 VS Code 集成的更好方法。
|
||||
|
||||
打开 VS Code，然后转到左侧栏中的扩展选项卡。在这里**搜索 GitHub 拉取请求和问题**。它是 GitHub 本身的官方插件。你可以看到已验证的勾选。
|
||||
打开 VS Code，然后转到左侧栏中的扩展选项卡。在这里**搜索 “GitHub Pull Requests and Issues”**。它是 GitHub 本身的官方插件。你可以看到已验证的勾选。
|
||||
|
||||
单击安装按钮并在你的编辑器上安装[扩展][18]。
|
||||
单击安装按钮并在你的编辑器上安装 [扩展][18]。
|
||||
|
||||
![Installing GitHub extension in VS Code][19]
|
||||
|
||||
@ -142,6 +142,8 @@ VS Code 内置了 GitHub 集成。你不需要安装任何扩展来克隆仓库
|
||||
|
||||
我希望本教程能帮助你将 GitHub 无缝添加到 VS Code。如果你仍然遇到任何问题，请告诉我。
|
||||
|
||||
*（题图：MJ/GitHub VS Code develop illustration in high resolution, very detailed, 8k）*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://itsfoss.com/vs-code-github/
|
||||
@ -149,7 +151,7 @@ via: https://itsfoss.com/vs-code-github/
|
||||
作者：[Abhishek Prakash][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -174,3 +176,4 @@ via: https://itsfoss.com/vs-code-github/
|
||||
[17]: https://itsfoss.com/content/images/2023/04/git-actions-in-vs-code.png
|
||||
[18]: https://itsfoss.com/install-vs-code-extensions/
|
||||
[19]: https://itsfoss.com/content/images/2023/04/install-github-extension-vs-code.png
|
||||
[0]: https://img.linux.net.cn/data/attachment/album/202304/24/160055gt5d5u6dk5f4f5e7.jpg
|
||||
@ -3,30 +3,32 @@
|
||||
[#]: author: "Sourav Rudra https://news.itsfoss.com/author/sourav/"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "XiaotingHuang22"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
[#]: reviewer: "wxy"
|
||||
[#]: publisher: "wxy"
|
||||
[#]: url: "https://linux.cn/article-15749-1.html"
|
||||
|
||||
Valve 发布 Proton 8.0，这对 Linux 游戏玩家和 Steam Deck 用户来说是个好消息
|
||||
Valve 发布 Proton 8.0
|
||||
======
|
||||
|
||||
> Proton 8.0 已经到来，带来了一些改进，以提升 Linux 游戏体验。
|
||||
|
||||
Proton 8.0 的到来改进了 Linux 游戏体验。
|
||||
|
||||
【译者注：Proton 是 V 社开发的兼容层，可以让 Windows 游戏在 Linux 上运行。它是一个软件集合，扩展了流行的 API 翻译层 Wine，提供高性能和低开销的 Vulkan API。】
|
||||
（LCTT 译注：Proton 是 V 社开发的兼容层，可以让 Windows 游戏在 Linux 上运行。它是一个软件集合，扩展了流行的 API 翻译层 Wine，提供高性能和低开销的 Vulkan API。）
|
||||
|
||||
![proton 8][1]
|
||||
![][0]
|
||||
|
||||
Proton 一直是 Linux 游戏玩家的福音，它使 Steam 客户端能够在 Linux 上运行 Windows 生态系统独有的游戏。
|
||||
|
||||
基于流行的 [Wine][2] 兼容层，Proton 多年来一直得益于 Valve 获得更新。
|
||||
基于流行的 [Wine][2] 兼容层，Valve 多年来一直为 Proton 提供更新。
|
||||
|
||||
Proton 8.0 的发布带来了一些令人印象深刻的升级，标志着 Linux 游戏又迈出了重要一步。
|
||||
|
||||
让我们一起来一探究竟。
|
||||
|
||||
**Proton 8.0 有啥新鲜事儿：** Proton 的新版本增加了对许多**新游戏**的**兼容性**和对现有游戏的**错误修复**。
|
||||
**Proton 8.0 有啥新鲜事儿：** Proton 的新版本增加了对许多**新游戏**的**兼容支持**和对现有游戏的**错误修复**。
|
||||
|
||||
例如，一些现有游戏，如 《极限竞速：地平线5》、《车祸模拟器》、《真人快打11》、《最终幻想14》、《汤姆·克兰西系列》的《细胞分裂》都得到了不同程度的修复，使它们比之前表现更好。
|
||||
例如，一些现有游戏，如 《<ruby>极限竞速：地平线 5<rt>Forza Horizon 5</rt></ruby>》、《<ruby>车祸模拟器<rt>BeamNG</rt></ruby>》、《<ruby>真人快打 X<rt>Mortal Combat X</rt></ruby>》、《<ruby>最终幻想 14<rt>Final Fantasy XIV Online</rt></ruby>》、《<ruby>汤姆·克兰西的细胞分裂<rt>Tom Clancy's Splinter Cell</rt></ruby>》都得到了不同程度的修复，使它们比之前表现更好。
|
||||
|
||||
**刚刚提到的新支持的游戏呢？**
|
||||
|
||||
@ -34,24 +36,24 @@ Proton 8.0 的发布带来了一些令人印象深刻的升级，标志着 Linux
|
||||
|
||||
最具期待的一些游戏包括：
|
||||
|
||||
- **《仁王 2 完整版》**
|
||||
- **《海贼无双 4》**
|
||||
- **《死亡空间 2023》**
|
||||
- **《魔咒之地》**
|
||||
- **《无双大蛇 3 终极版》**
|
||||
- 《<ruby>仁王 2 完整版<rt>Nioh 2 – The Complete Edition</rt></ruby>》
|
||||
- 《<ruby>海贼无双 4<rt>One Piece: Pirate Warriors 4</rt></ruby>》
|
||||
- 《<ruby>死亡空间 2023<rt>Dead Space (2023)</rt></ruby>》
|
||||
- 《<ruby>魔咒之地<rt>Forspoken</rt></ruby>》
|
||||
- 《<ruby>无双大蛇 3 终极版<rt>WARRIORS OROCHI 3 Ultimate Definitive Edition</rt></ruby>》
|
||||
|
||||
此外，还有一些可以帮助 Steam Deck 用户的改进，包括：
|
||||
此外，还有一些改进会对 Steam Deck 用户有所帮助，包括：
|
||||
|
||||
- 改进了 Steam Deck 上 《小缇娜的奇幻之地》 的睡眠/恢复功能。
|
||||
- 改进了 Steam Deck 上 《<ruby>小缇娜的奇幻之地<rt>Tiny Tina's Wonderland</rt></ruby>》 的睡眠/恢复功能
|
||||
- 改进了多点触控支持
|
||||
|
||||
**对技术细节更感兴趣？**
|
||||
|
||||
Proton 8.0 基于最近发布的 **Wine 8.0**，它可以利用**更好的 WoW64 32 位支持**、**Direct3D 性能提升**、**游戏控制器及驱动轮的增强支持** 和更多改进。
|
||||
Proton 8.0 基于最近发布的 **Wine 8.0**，它可以提供**更好的 WoW64 32 位支持**、**提升了 Direct3D 性能**、**增强了对游戏控制器及方向盘的支持**等等。
|
||||
|
||||
你可以查看我们的报道以深入了解。
|
||||
|
||||
除此之外，此版本还引入了针对 GNOME 43 上的 **Alt+Tab 问题**、**为游戏启用了 NVIDIA API**、附带 **dxvk v2.1-4-gcaf31033** 等的修复程序。
|
||||
除此之外，此版本还引入了针对 GNOME 43 上的 **Alt+Tab 问题**、**为游戏启用了英伟达 API**、附带的 **dxvk v2.1-4-gcaf31033** 等的修复程序。
|
||||
|
||||
你或许想通过 [发行说明][4] 来探索随 Proton 8.0 一起提供的**有关技术变更和游戏的详细列表**。
|
||||
|
||||
@ -59,11 +61,13 @@ Proton 8.0 基于最近发布的 **Wine 8.0**，它可以利用**更好的 WoW64
|
||||
|
||||
![在 steam play 上运行 proton 8.0 的截图][5]
|
||||
|
||||
如果你使用 Steam，你可以按照我们的指南了解如何在 Linux 上设置 Steam Play (Proton) 并开始 [在 Linux 上玩游戏][6]。
|
||||
如果你使用 Steam，你可以按照我们的指南了解如何在 Linux 上设置 Steam Play （Proton）并开始 [在 Linux 上玩游戏][6]。
|
||||
|
||||
不过，需要注意的是，随着 Proton 8.0 的发布，要想顺利运行系统需要 **至少支持 Vulkan 1.3 的 GPU**。
|
||||
|
||||
你还可以查看 [GitHub 存储库][7]，了解如何从源代码手动安装它。
|
||||
你还可以查看 [GitHub 代码库][7]，了解如何从源代码手动安装它。
|
||||
|
||||
*（题图：MJ/linux game illustration in high resolution, very detailed, 8k）*
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
@ -72,7 +76,7 @@ via: https://news.itsfoss.com/proton-8-0-release/
|
||||
作者：[Sourav Rudra][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[XiaotingHuang22](https://github.com/XiaotingHuang22)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
@ -85,3 +89,4 @@ via: https://news.itsfoss.com/proton-8-0-release/
|
||||
[5]: https://news.itsfoss.com/content/images/2023/04/Proton_8.0_2-1.jpg
|
||||
[6]: https://itsfoss.com/linux-gaming-guide/?ref=news.itsfoss.com
|
||||
[7]: https://github.com/ValveSoftware/Proton?ref=news.itsfoss.com
|
||||
[0]: https://img.linux.net.cn/data/attachment/album/202304/24/113235pz88t69zene1nt6d.jpg
|
||||
@ -1,109 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (rsqrt2b)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (What is an open source evangelist?)
|
||||
[#]: via: (https://opensource.com/article/21/1/open-source-evangelist)
|
||||
[#]: author: (Peter Czanik https://opensource.com/users/czanik)
|
||||
|
||||
What is an open source evangelist?
|
||||
======
|
||||
Learn what it takes to be a bridge between a product's users and its
|
||||
developers.
|
||||
![Teamwork starts with communication][1]
|
||||
|
||||
When people learn that I work as an open source evangelist (focusing on [syslog-ng][2] and [sudo][3]), they often ask me what it's like to represent such well-known names in the Linux world. My short answer: It's good!
|
||||
|
||||
I am part of research and development, so it is never boring. I feel that I make an impact when people implement what they learn from me and when the feedback I collect from users influences the development of the product.
|
||||
|
||||
### What is an evangelist?
|
||||
|
||||
I define an evangelist as a bridge between a software's (or other product's) users and its developers. It is not just about sharing good news with users but also collecting feedback from them.
|
||||
|
||||
Evangelists come from a wide range of backgrounds. Some people have a marketing background with a strong interest in technology. Some are developers who like talking to users. I belong to a third group, "power users," or people with in-depth knowledge about a software product from the user's point of view.
|
||||
|
||||
In my job, I work with many, many users. The syslog-ng user base is enormous. It is available on most Linux distributions and BSD variants. Hundreds of millions of devices run syslog-ng, including both the BMW i3 and the Kindle. Most BSD-based appliances, like FreeNAS, run syslog-ng for logging, as do Linux-based network-attached storages (NAS) devices from Synology and QNAP. I would not be surprised to learn that syslog-ng is running somewhere in space.
|
||||
|
||||
Most Linux and Unix users use sudo since it is installed on almost every Linux machine out there. Its community is huge, with tens of millions of people. People often ask me how I cope with these large numbers of users, but it is not difficult.
|
||||
|
||||
### How I became an evangelist
|
||||
|
||||
My journey to becoming an evangelist was an evolutionary process that spanned nearly 20 years. It started many years ago while I was teaching at a university. My next step was working with POWER/PowerPC Linux users and developers. Finally, I started to cover syslog-ng in my job at [Balabit][4] and later began working with sudo.
|
||||
|
||||
My first job at Balabit was to help Linux distributions update the syslog-ng package to the latest upstream version. As I learned more and more about syslog-ng's details, I was asked to help its users. A year later, I was giving talks about syslog-ng at Hungarian and international conferences. Soon after, the feedback I collected from users started to make an impact on product development.
|
||||
|
||||
Eight years later, in 2018, Balabit was acquired by [One Identity][5], and [Todd Miller][6], sudo's maintainer, became my colleague. Until then, I knew only some basic sudo features, but I became more interested in sudo and learning about its advanced features. Soon, I was also evangelizing sudo and evolving from a syslog-ng evangelist into a more generic open source evangelist.
|
||||
|
||||
### Four pillars of technical evangelism
|
||||
|
||||
Technical evangelists do many things that can be broadly divided into four categories: developer, support, technical product marketing, and product management. I'll look at each of these four pillars of technical evangelism in more detail.
|
||||
|
||||
#### Developer
|
||||
|
||||
I am not a developer, but I do many things that developers do, such as packaging syslog-ng for various Linux distributions and FreeBSD, doing lots of testing, integrating syslog-ng with other software, and testing it on exotic platforms. The developer tasks I do help the community and helps me understand its needs better.
|
||||
|
||||
#### Support
|
||||
|
||||
Following bug trackers, watching the syslog-ng keyword in Google Alerts and Twitter, and reading the mailing list enable me to help our user base better. By helping our users, I also understand their problems better.
|
||||
|
||||
#### Technical product marketing
|
||||
|
||||
I really do not like the term "marketing," but writing blogs and talking at conferences *is *marketing. As a former sysadmin, I know my audience, and we have a common voice. Along with my own Twitter handle, [@PCzanik][7], I also post under the [@sngOSE][8] (syslog-ng open source edition) and [@SudoProject][9] (sudo) handles.
|
||||
|
||||
Twitter is a fantastic platform to collect and share technical news. Marketing is the most visible part of my work as an evangelist, even if it is just one aspect of my job.
|
||||
|
||||
* **Event survival tips for introverts: **When people learn that I am doing this job even though I am an introvert, they often ask me how I do it. Giving a talk or working at a conference booth all day long can be difficult; there are too many people, too much noise. Here are my survival tips for events:
|
||||
* Focus on the results. Events are the best opportunity to collect feedback from users. After your talk, you can have good discussions anywhere, even at the booth or in the hallway. Users give a lot of feedback in real life at events, and remembering their comments helps a lot.
|
||||
* Keep in mind when the event is over. Knowing that you have to stay only one more hour in an environment with a high level of noise helps a lot.
|
||||
* Enjoy that you get to talk to like-minded people who have the same shyness, insecurity, and technical interests as you have.
|
||||
* **Marketing tips during a pandemic: **Many people have asked me how COVID-19 has affected my work since I haven't been able to travel since March 2020. I came back from talking at the [RSA Conference][10] and [Southern California Linux Expo][11] just two days before flights were suspended and borders were closed. Even though all conferences are virtual right now, I can still give talks about sudo and syslog-ng. But this means feedback is missing or minimal—there is no hallway track to meet users nor a dinner for speakers to discuss the latest and greatest technologies. Participation and attention are also less focused, as there are plenty of distractions when people are working from home. I have seen many different efforts to work around this situation. Each has its own drawbacks and advantages:
|
||||
* A global chat room is good for a smaller event. But if an event has more than just a few dozen people, then it turns into a continuous roll of 'Hi from Boston, MA' and similar messages without a chance for a meaningful conversation.
|
||||
* If an event has multiple tracks, a dedicated chat for each track can be helpful. Both the users and the speaker can learn a lot from the questions and remarks posted in the chat. A moderator can make it twice as much useful, keeping the discussion on topic and making sure that questions reach the speaker during the Q&A part of the talk.
|
||||
* A chat roulette is good to connect random strangers and might result in good discussions. But for a speaker, it is way too random.
|
||||
* Tracking chats is good but many people are uncomfortable to post questions or share experiences in public. A possibility for direct chat with the speaker can resolve this problem.
|
||||
|
||||
|
||||
|
||||
#### Product management
|
||||
|
||||
I am not a product manager, even though sometimes I wish that the feedback I collect could be turned directly into features. However, I regularly share users' feedback with developers and product management. In internal discussions, I always represent the users' side rather than the easiest way forward for developers or what will generate the most revenue.
|
||||
|
||||
### Why evangelize broadly known and used software?
|
||||
|
||||
Every Linux user knows sudo, and many of them also know syslog-ng. So why evangelize? Well, most people know just the very basics of these applications, which they learned when they started to play with Linux. But neither is a simple utility that has been in maintenance mode for decades; both are living software still under continuous development.
|
||||
|
||||
What most people know about syslog-ng is that it collects log messages and saves them to text files. But it has a lot of [other features][12], including parsing messages, enriching messages with geographical information, precise message routing (filtering), and saving messages to databases, Hadoop, or message queues.
|
||||
|
||||
Sudo is mostly known as a prefix for administrative commands, but it can do a lot more. It can record sessions that run through it, allowing you to check what your users are doing when they exercise their superpowers through sudo. You can also extend sudo with plugins. [Starting with sudo version 1.9][13], you can even extend sudo in Python, making the process a lot easier.
|
||||
|
||||
### Conclusion
|
||||
|
||||
Being an open source evangelist is a very interesting and fun job, even in the COVID-19 era, which has certainly added difficulties to my work. If you have other questions about the role or have a story about how a technical evangelist or developer advocate has helped you, please share them in the comments.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/21/1/open-source-evangelist
|
||||
|
||||
作者：[Peter Czanik][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/czanik
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/laptop-stickers-team-happy_0.png?itok=G2-GcSPp (Teamwork starts with communication )
|
||||
[2]: https://www.syslog-ng.com/
|
||||
[3]: https://www.sudo.ws/
|
||||
[4]: https://en.wikipedia.org/wiki/Balabit
|
||||
[5]: https://www.oneidentity.com/
|
||||
[6]: https://www.linkedin.com/in/millert/
|
||||
[7]: https://twitter.com/PCzanik
|
||||
[8]: https://twitter.com/sngose
|
||||
[9]: https://twitter.com/SudoProject
|
||||
[10]: https://www.rsaconference.com/usa/us-2020
|
||||
[11]: https://www.socallinuxexpo.org/scale/18x
|
||||
[12]: https://www.syslog-ng.com/community/b/blog/posts/building-blocks-of-syslog-ng
|
||||
[13]: https://opensource.com/article/20/10/sudo-19
|
||||
@ -1,60 +0,0 @@
|
||||
[#]: subject: "Open source matters in data analytics: Here's why"
|
||||
[#]: via: "https://opensource.com/article/22/9/open-source-data-analytics"
|
||||
[#]: author: "Ray Paik https://opensource.com/users/rpaik"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "cool-summer-021"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Open source matters in data analytics: Here's why
|
||||
======
|
||||
Open source is critical in data analysis while providing long-term benefits for the users, community members, and business.
|
||||
|
||||
It's been a little over a year since I wrote my article on Opensource.com, [introducing the Cube community][2]. As I worked with our community members and other vendors, I've become more convinced of the benefits of open source in data analytics. I also think it's good to remind ourselves periodically why open source matters and how it provides long-term benefits for everyone.
|
||||
|
||||
### Benefits of open source for users and customers
|
||||
|
||||
One of the first things I heard from the Cube community was that they often received better support in chat from other community members than they did with proprietary software and a paid support plan. Across many open source communities, I find people who are motivated to help other (especially new) community members and see it as a way of giving back to the community.
|
||||
|
||||
You don't need permission to participate in open source communities. A good open source community isn't for developers only, and people feel there's a culture of trust and feel comfortable enough to have open discussions on chat platforms, forums, and issue trackers. This is especially important for non-developers, such as data engineers or analysts in the data analytics space.
|
||||
|
||||
Of course, with open source software, there's the ability to see and contribute directly to the codebase to fix bugs or add new features. Using an example from the Cube community, GraphQL support was one of our highlights last year, and our community members [contributed to this feature][3].
|
||||
|
||||
There are plenty of benefits to an active community. Even in cases where the vendor cannot release a fix in a timely manner, you can still make the changes yourself and own the runtime while you wait for an "official" fix. Community members and users also don't like being locked in to a vendor's whims, and there's no pressure to upgrade when using open source software.
|
||||
|
||||
Open source communities leave many "bread crumbs" in different tools like GitLab, GitHub, Codeberg, YouTube, and so on, making it a lot easier to gauge not just the volume of activities but also the level of community engagement and culture. So even before trying out the software, you can get a good sense of the community's health (and, by extension, the company) before deciding if this is a technology you want to invest in.
|
||||
|
||||
### Benefits of open source for the company
|
||||
|
||||
There's no better way to lower the barrier to adoption of your software than being open source. Early on, this helps grow adoption among the technical audience. Early adopters then often become some of your most loyal fans for years to come.
|
||||
|
||||
Early adopters are also catalysts for speeding up your development. Their feedback on your product and feature requests (for instance on your issue trackers) will provide insight into real-world use cases. In addition, many of the open source enthusiasts participate in co-development efforts (for example, on your repositories) for new features or bug fixes. Needless to say, this is precious for companies in the early days when there is a shortage of resources in development and product teams.
|
||||
|
||||
As you tend to your community, you will help it grow and diversify. Increased diversity isn't just in demographics or geography. You want users from new industries, or users with different job titles. Using the Cube community as an example, I mostly talked to application developers a year ago, but now I’m meeting with more people that are data consumers or users.
|
||||
|
||||
The collaborative culture in good open source communities lowers the barrier to entry not just for developers but also for others who want to ask questions, share their ideas or make other [non-technical contributions][4]. You get better access to diverse perspectives as your company and community grows.
|
||||
|
||||
Being open source makes it easy to collaborate with other vendors and communities, not just with individual community members. For example, if you want to work with another vendor on a database driver or integration, it's a lot simpler when you can just collaborate across open source repositories.
|
||||
|
||||
### Community matters
|
||||
|
||||
All these benefits lead to lowering the barriers to entry for using your software and collaboration. The open source model will not only help individual software or companies, but it can help accelerate the growth of our entire ecosystem and the industry. I hope to see more open source companies and communities in the data analytics space and for all of us to continue this journey.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/9/open-source-data-analytics
|
||||
|
||||
作者：[Ray Paik][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/rpaik
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/metrics_data_dashboard_system_computer_analytics.png
|
||||
[2]: https://opensource.com/article/21/6/cubejs
|
||||
[3]: https://github.com/cube-js/cube.js/pull/3555
|
||||
[4]: https://opensource.com/article/22/8/non-code-contribution-powers-open-source
|
||||
110
translated/talk/20210108 What is an open source evangelist.md
Normal file
110
translated/talk/20210108 What is an open source evangelist.md
Normal file
@ -0,0 +1,110 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (rsqrt2b)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (What is an open source evangelist?)
|
||||
[#]: via: (https://opensource.com/article/21/1/open-source-evangelist)
|
||||
[#]: author: (Peter Czanik https://opensource.com/users/czanik)
|
||||
|
||||
什么是开源传教士？
|
||||
======
|
||||
了解如何成为产品用户和开发人员之间的桥梁。
|
||||
![Teamwork starts with communication][1]
|
||||
|
||||
当人们得知我是个开源传教士（专注于 [syslog-ng][2] 和 [sudo][3]）的时候，他们经常问我在 Linux 世界如此知名是什么感觉。我的回答非常简短：这很棒！
|
||||
|
||||
我不会感到无聊，因为我是研发的一部分。当人们实践我教他们的东西以及我收集到的用户反馈影响产品开发的时候，我感觉我起了作用。
|
||||
|
||||
### 什么是传教士？
|
||||
|
||||
我将传教士定义为一座桥梁——软件（或其他产品）用户和开发人员之间的桥梁。传教士不仅仅将好消息分享给用户，还要从他们那里收集反馈。
|
||||
|
||||
传教士们有着各式各样的背景：有的具有市场营销背景，对技术有着浓厚的兴趣；有的是喜欢和用户交流的开发人员。我属于第三类——“高级用户”，或者说从用户视角对软件产品有深入了解的人。
|
||||
|
||||
我和很多很多用户一起工作。syslog-ng 的用户群体非常庞大，它适用于大多数 Linux 发行版和 BSD 变体。数以亿计的设备运行着 syslog-ng，其中包括 BMW i3 和 Kindle。大多数基于 BSD 的设备，譬如 FreeNAS，使用 syslog-ng 记录日志 就像基于 Linux 的<ruby>网络附属存储<rt>Network Attached Storage</rt></ruby>（NAS）使用 Synology 和 QNAP 一样。就算 syslog-ng 运行在太空的某处，我也不会感到惊讶。
|
||||
|
||||
|
||||
大多数 Linux 和 Unix 用户使用 sudo，因为它几乎被安装在每一台 Linux 设备上。社区很大，有几千万人。人们经常问我是如何处理那么多用户的，但这并不困难。
|
||||
|
||||
### 我是如何成为一名传教士的
|
||||
|
||||
我成为传教士的旅程是一个跨越近20年的进化过程。它始于许多年前，我在大学教书的时候。我的下一步是和 POWER/PowerPC 的 Linux 用户、开发人员合作。最后，我开始在 [Balabit][4] 的工作中使用 syslog-ng，再后来我开始在 sudo 方面工作。
|
||||
|
||||
|
||||
我在 Balabit 的第一份工作是帮助 Linux 发行版将它们的 syslog-ng 包升级到上游的最新版本。随着我越来越多地了解 syslog-ng 的细节，我被要求帮助它的用户。一年后，我在匈牙利和国际会议上发表关于 syslog-ng 的演说。不久之后，我从用户那里收集到的数据开始对产品开发产生影响。
|
||||
|
||||
八年后，也就是2018年，Balabit 被 [One Identity][5] 收购，sudo 的维护者 [Todd Miller][6] 成为了我的同事。在那之前我只是了解一些基本的 sudo 功能，但我变得对 sudo 更感兴趣并开始了解它的高级功能。很快，我开始传教 sudo，从一名 syslog-ng 传教士进化为一个更一般的开源传教士。
|
||||
|
||||
### 技术传教的四大支柱
|
||||
|
||||
技术传教士做很多事情，大致可以分为四类：开发人员、支持人员、技术产品营销和产品经理
|
||||
|
||||
#### 开发人员
|
||||
|
||||
我不是开发人员，但我做很多开发人员的工作，例如为各式各样的 Linux 发行版和 FreeBSD 打包 syslog-ng，做很多测试，将 syslog-ng 集成到其他软件中并在外国平台上测试。我做的开发人员的工作帮助社区和我自己更好地了解其需求。
|
||||
|
||||
#### 支持人员
|
||||
|
||||
关注 bug 追踪器，在 Google Alerts 和 Twitter 上查看 syslog-ng 关键词以及阅读邮件列表都能让我更好地帮助我们的用户群体。同我帮助他人，我也能能更好地理解他们的问题所在。
|
||||
|
||||
#### 技术产品营销
|
||||
|
||||
我真的不喜欢“营销”这个词，但是写博客和在会议上演说 *确实是* 营销。作为一名前系统管理员，我了解我的听众，我们有共同的声音。除了我自己的 Twitter <ruby>句柄<rt>handle</rt></ruby>（LCTT译者注：可以理解为 Twitter 账号唯一的、不重复的标识符 ），[@PCzanik][7]，我还在 [@sngOSE][8] （syslog-ng 开源版）和 [@SudoProject][9] （sudo）句柄下发帖。
|
||||
|
||||
Twitter 是个收集和分享技术新闻的绝佳平台。即使营销只是我工作的一个方面，它仍是我传教工作中最明显的部分。
|
||||
|
||||
* **给内向者的社交场合生存小贴士：** 当人们了解到即使我是一个内向的人，我仍然从事了这份工作之后，就经常问我是如何做到的。在小会议室成天演讲或工作非常困难：人太多、噪音太多了。我在这里针对这种场合给出一些生存贴士：
|
||||
* 专注于结果。社交场合是从用户那里收集反馈的绝佳机会。等你演讲完，可以随地开始一场好的讨论，甚至在小隔间里或走廊上。用户在现实生活的社交场合里会给出很多反馈，牢记它们的评论会有很多帮助。
|
||||
* 当会议结束的时候，请牢记，在嘈杂的环境中只要再待上一个多小时将很有帮助。
|
||||
* 尽情享受和与你志同道合的人交谈，他们和你一样害羞、和你一样有不安全感、和你有着相同的技术兴趣。
|
||||
* **疫情期间的营销技巧：** 许多人问我 COVID-19 是如何影响我的工作的，因为我从 2020 年开始就不能出行。我刚从 [RSA 大会][10] 和 [南加利福尼亚州 Linux 博览会][11] 上回来，两天后航班就暂停了、边境也关闭了。即使现在也在开虚拟会议，我仍可以做有关 sudo 和 syslog-ng 的演说，但这样反馈就会减少，甚至没有反馈——没有走廊让我和用户见面，也没有晚餐供演讲者讨论最新、最好的技术。会议上注意力比以往更不集中，因为在家里工作总有各种各样的干扰因素。我看到了许多不同的方法试图解决这个问题，每一项都有其优缺点：
|
||||
* 全球聊天室适合举办小型活动。但当会议有超过几十个人时，它将会变成一连串的“大家好，我来自马萨诸塞州，波士顿” 或者类似的无用的消息，从而没有机会进行一些有意义的讨论。
|
||||
* 如果活动是多轨并行的，给每个专题讨论一个轨道是很有用的。演讲者和用户都可以从聊天中发布的问题和评论中学到很多东西。如果有一个主持人，这将成倍地有用。始终记得将讨论限制在主题上，并确保在问答环节中产生的问题传达到演讲者耳中。
|
||||
* 随机抽取聊天者是个随机联系陌生人的好方法，并且能产生好的讨论。不过这种方法对于演讲者来说随机性太高了。
|
||||
* 追踪聊天很好，不过许多人不喜欢公开提问或分享经验。直接与演讲者聊天可以解决这个问题。
|
||||
|
||||
#### 产品经理
|
||||
|
||||
|
||||
我不是产品经理，尽管有时候我希望自己收集到的反馈可以直接转化为功能，但我定期与开发者和产品经理分享用户反馈。在内部讨论中，我总是代表用户一方，而不是考虑开发者如何用用最简单的方法推进产品，或者如何产生最多收益。
|
||||
|
||||
### 为什么要传教广为人知、被广泛使用的软件？
|
||||
|
||||
每个 Linux 用户都知道 sudo，他们中的许多人也知道 syslog-ng。那我们为什么要传教呢？这是因为许多人只知道这些程序的基础知识，这也是他们刚开始使用 Linux 时学到的。但这两款软件都不是简单的、几十年来处于维护模式的实用程序，两者都是仍在持续开发中的有生命力的程序。
|
||||
|
||||
大多数人对 syslog-ng 的了解仅限于它收集日志消息并把消息存储在文本文件中。但 syslog-ng 还有许多 [其他功能][12]，包括解析消息、使用地理信息丰富消息、精确的消息路径（过滤）和把消息存储在数据库、Hadoop 或消息队列中。
|
||||
|
||||
|
||||
sudo 通常被认为是管理员命令的前缀，但它可以做许多其他事情。sudo 可以记录在里面运行的会话，允许你检查用户通过 sudo 使用超级权限做了什么事情。你也可以使用插件扩展 sudo。从 [sudo 的 1.9 版本][13] 开始，你甚至可以用 Python 扩展 sudo，这让过程变得容易得多。
|
||||
|
||||
### 结论
|
||||
|
||||
即使在 COVID-19 时代，成为一名开源传教士也是个非常有趣的工作，这确实增加了我的工作难度。如果你对于这个角色有其他问题或者有关于技术传教士或者开发倡导则如何帮助你的故事，请在评论里分享。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/21/1/open-source-evangelist
|
||||
|
||||
作者：[Peter Czanik][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[rsqrt2b](https://github.com/rsqrt2b)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/czanik
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/laptop-stickers-team-happy_0.png?itok=G2-GcSPp (Teamwork starts with communication )
|
||||
[2]: https://www.syslog-ng.com/
|
||||
[3]: https://www.sudo.ws/
|
||||
[4]: https://en.wikipedia.org/wiki/Balabit
|
||||
[5]: https://www.oneidentity.com/
|
||||
[6]: https://www.linkedin.com/in/millert/
|
||||
[7]: https://twitter.com/PCzanik
|
||||
[8]: https://twitter.com/sngose
|
||||
[9]: https://twitter.com/SudoProject
|
||||
[10]: https://www.rsaconference.com/usa/us-2020
|
||||
[11]: https://www.socallinuxexpo.org/scale/18x
|
||||
[12]: https://www.syslog-ng.com/community/b/blog/posts/building-blocks-of-syslog-ng
|
||||
[13]: https://opensource.com/article/20/10/sudo-19
|
||||
@ -0,0 +1,60 @@
|
||||
[#]: subject: "Open source matters in data analytics: Here's why"
|
||||
[#]: via: "https://opensource.com/article/22/9/open-source-data-analytics"
|
||||
[#]: author: "Ray Paik https://opensource.com/users/rpaik"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "cool-summer-021"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
开源对于数据分析很重要：本文将告诉你为什么
|
||||
======
|
||||
开源对于数据分析非常重要，它能为用户、社区成员和公司带来长远利益。
|
||||
|
||||
我曾经在 Opensource 网站上写过介绍 Cube Community 的文章，至今已过去了一年多。由于和社区会员以及其他供应商在一起工作，我更坚信开源对于数据分析工作是很有好处的。我也认为，需要不断思考开源为什么重要，以及开源是如何为人们带来长远利益的。
|
||||
|
||||
### 开源对于用户和客户的好处
|
||||
|
||||
我从 Cube 社区听说的第一件事就是：他们经常可以从与其他社区成员的交流中得到技术支持，这种支持往往好于使用需要付费的专有软件获得的支持。在很多开源社区中，我发现，社区成员很乐意帮助别人（特别是帮助新手），并且把这种帮助看作回报开源社区的方式。
|
||||
|
||||
在开源社区，你不需要获得某种权限就可以加入。一个好的开源社区不但服务于开发者，而且令人们感觉到有一种信任的文化，认为与他人在聊天室、论坛和问题跟踪工具进行开放式讨论是一件愉快的事。这对于诸如数据工程师或数据分析师之类的非开发者来说也很重要。
|
||||
|
||||
当然，借助开源软件，还可以直接查看代码、修复 BUG 或为项目添加新功能。比如，对于 GraphQL 的支持就是我们去年的亮点，我们的社区成员为项目[贡献了这些功能][3]。
|
||||
|
||||
对一个活跃的社区来说，也是很有好处的。即使当供应商不能及时地发布修复版本，你仍然可以自行修改，并可以在等待官方修复版的这段时间内使用修改后的版本。社区成员和用户也不愿意被供应商的奇思妙想所束缚，而且使用开源软件时也不存在升级的压力。
|
||||
|
||||
开源社区为不同工具（包括GitLab, GitHub, Codeberg, YouTube 等）留下了很多面包屑，这令计算活跃程度和社区参与度更容易。所以即使在试用软件前，你也可以在做决定之前了解到它所在社区的一些情况（包括公司）。
|
||||
|
||||
### 开源对公司的好处
|
||||
|
||||
没有其他办法比开源更能降低使用软件的障碍了。在早期，开源可以提高技术受众的认知度。早期的使用者往往后来会成为你的最忠实的粉丝。
|
||||
|
||||
早期的使用者也是加速产品发展的催化剂。他们对于产品的反馈和功能需求（例如对问题的追踪）能实现对真实用例的洞察。另外，很多开源爱好者可以合作开发（比如通过代码仓库）新功能和进行 BUG 修复。不用说，这对于创业早期的公司来说是很重要的，因为当时缺少开发和产品相关的资源。
|
||||
|
||||
你对社区的关注会令它发展壮大，并且呈现多样化趋势。多样化不仅体现在人数和地域方面。你需要来自新兴行业的用户或从事各种职业的用户。以 Cube 社区为例，我常常会在一年前跟一些开发者交流，但一年后与我交流得更多的是那些数据使用者和用户。
|
||||
|
||||
在较好的开源社区里，合作文化降低了准入门槛，不仅对于开发者，对于其他提问者、分享观点者或愿意作出非技术性贡献的人们来说都是如此。随着公司和社区的发展，你可以更好地接触到不同的观点。
|
||||
|
||||
对包括社区成员在内的广大人群来说，开源使合作变得更容易。例如，你需要跟其他贡献者在同一台数据库上进行合作，如果可以通过开源仓库进行合作，就很方便了。
|
||||
|
||||
### 关于社区
|
||||
|
||||
以上这些好处都降低了使用软件和协作开发的门槛。开源模型不仅对单个软件或公司有帮助，它还能令整个生态和行业加速发展。我希望在数据分析领域看到更多开源的公司和社区，同时希望人们持续关注开源产品。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/22/9/open-source-data-analytics
|
||||
|
||||
作者：[Ray Paik][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/rpaik
|
||||
[b]: https://github.com/lkxed
|
||||
[1]: https://opensource.com/sites/default/files/lead-images/metrics_data_dashboard_system_computer_analytics.png
|
||||
[2]: https://opensource.com/article/21/6/cubejs
|
||||
[3]: https://github.com/cube-js/cube.js/pull/3555
|
||||
[4]: https://opensource.com/article/22/8/non-code-contribution-powers-open-source
|
||||
Loading…
Reference in New Issue
Block a user