mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-23 21:20:42 +08:00
[提交翻译][talk]: 20230309.1 ⭐️ Contribute to open source without code.md (#28864)
* [翻译完成][talk]: 20230309.1 ⭐️ Contribute to open source without code.md * [移动翻译][talk]: 20230309.1 ⭐️ Contribute to open source without code.md * [修复翻译][talk]: 20230309.1 ⭐️ Contribute to open source without code.md
This commit is contained in:
Qian Qian (Cubik)
GitHub
parent
a0e7185c69
commit
fccc6e972c
@ -1,91 +0,0 @@
|
||||
[#]: subject: "Contribute to open source without code"
|
||||
[#]: via: "https://opensource.com/article/23/3/non-code-contribution-open-source"
|
||||
[#]: author: "Debra Chen https://opensource.com/users/debra-chen"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "Cubik65536"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Contribute to open source without code
|
||||
======
|
||||
|
||||
An open source "community" means different things to different people. I think of open source a little like "falling in love" because it is about people and relationships. Treat open source as a community because, without people, there is no source, open or otherwise.
|
||||
|
||||
I'm a member of the [Apache DolphinScheduler][1] community. Because that project is intentionally low-code, it appeals to many [people who aren't software developers][2]. Sometimes, people who don't write code aren't sure whether there's a meaningful way to contribute to an open source project that exists mainly because of source code. I know from experience that there is, and I will explain why in this article.
|
||||
|
||||
### Contributions to the community
|
||||
|
||||
In the Apache DolphinScheduler project, I'm mainly responsible for global operation, influence, and caring for the community.
|
||||
|
||||
Some people say that projects are big trees, with open source being the soil. That's an apt analogy, and it demonstrates the importance of actively nurturing the thing you're trying to help grow.
|
||||
|
||||
I have a simpler idea: Do everything possible to make it good.
|
||||
|
||||
A community requires constant attention, not because it's needy but because it is part of life. Community is the people living amongst you, whether in your physical or online space.
|
||||
|
||||
Since joining the open source community, I have independently initiated and organized events, including:
|
||||
|
||||
- Coordinated on average one meetup in China a month.
|
||||
- Recommended the community participate in the technology shares within the big data field.
|
||||
- Coordinated with almost all of the open source projects within China's "big data" field, visiting and communicating with those communities individually.
|
||||
|
||||
In my opinion, an excellent project should grow in a good ecology. And a community needs to go out to exchange ideas, share resources, and cooperate with other excellent communities. Everyone should feel the benefits brought to the community in their work.
|
||||
|
||||
My overseas expansion follows the same pattern. Of course, it's difficult to do that effectively due to differences in cultures and languages. It takes energy, but it's worth it.
|
||||
|
||||
So far, we have successfully held meetups overseas, including in the United States, India, Singapore, Germany, France, Finland, and more.
|
||||
|
||||
So how do I contribute to DolphinScheduler? Am I committing code to the project? Am I a community manager? Do I have an official title?
|
||||
|
||||
I think of myself as an assistant. I foster communication and connection, and that, as much as any code contribution, is an example of the "Apache Way."
|
||||
|
||||
### Get started with DolphinScheduler
|
||||
|
||||
I first learned about open source when I worked at OpenAtom Foundation as an open source education operation manager. As China's first open source foundation, OpenAtom operates many projects, exemplified by [OpenHarmony][3].
|
||||
|
||||
I joined the DolphinScheduler community and found a group of people who were eager to share knowledge, provide guidance and support, and keen to help others discover a tool they would find useful in their own lives.
|
||||
|
||||
DolphinScheduler aims to be an influential scheduler worldwide, helping teams work in an [Agile][4] and efficient way.
|
||||
|
||||
### First impressions of the community
|
||||
|
||||
It's common to hear complaints from the community about project development. We all have complaints from time to time. Maybe you reported a bug, but the developers didn't address your problem. Or maybe you had a great idea for a feature, but the team ignored it. If you're a member of an open source community, you've heard these grievances before, and if you haven't, you eventually will.
|
||||
|
||||
I've learned that these voices are all important to an open source community. It's a good sign when you hear this feedback because it means the community is willing to find bugs, report them, and ask and answer questions. Hearing those complaints may reveal places in the project's structure that need to be improved. Is there a volunteer from the community who can respond to bug reports and triage them so they get to the right developer? Is there a volunteer group waiting to be formed to respond promptly to questions from newcomers in your project's Discourse or forum?
|
||||
|
||||
A greeter at the door of your open source project can help invite tentative community members in. A greeter can also ensure that there's no "gatekeeping" happening. Everyone's welcome and everyone has something to contribute, even if all they can offer is an atmosphere of helping one another.
|
||||
|
||||
As much as you or I wish we could solve technical issues for everyone, it's not practical. But anyone can be willing to help find a solution—that's one of the great strengths of a community. These users spontaneously serve as their community's "customer service" department.
|
||||
|
||||
Within the DolphinScheduler project, we have many (Yan Jiang, Xu Zhiwu, Zhang Qichen, Wang Yuxiang, Xiang Zihao, Yang Qiyu, Yang Jiahao, Gao Chufeng, and Gao Feng, in no particular order!). Even though they don't develop the solution, they work tirelessly to find the person who can.
|
||||
|
||||
### Words to the community
|
||||
|
||||
If you want to become a committer through non-code contributions or don't have time to make a code contribution, then the first step is to join the community. There's no sign-up form or approval process, but there's also no fast track. You join a community by participating. Through reliable and consistent participation, you develop relationships with others.
|
||||
|
||||
I'm available for a chat and always eager to talk about global event organization, documentation, feedback, and more.
|
||||
|
||||
### Become a committer
|
||||
|
||||
Apache DolphinScheduler faces many challenges. Many companies, even ones that support open source, choose non-open business tooling. I want to work with community partners to make DolphinScheduler a world-class scheduling tool. I hope everyone can harvest the technical achievements they want and that DolphinScheduler helps get them there.
|
||||
|
||||
Join our community and help us promote an open and Agile way of working. Or find a project in need of your non-coding skills. Find out just how cool and fun it is to empower a community of your peers!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/23/3/non-code-contribution-open-source
|
||||
|
||||
作者：[Debra Chen][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[Cubik65536](https://github.com/Cubik65536)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/debra-chen
|
||||
[b]: https://github.com/lkxed/
|
||||
[1]: https://dolphinscheduler.apache.org/en-us
|
||||
[2]: https://opensource.com/article/21/2/what-technical
|
||||
[3]: https://gitee.com/openharmony
|
||||
[4]: https://opensource.com/article/22/5/practical-tips-agile
|
||||
@ -0,0 +1,91 @@
|
||||
[#]: subject: "Contribute to open source without code"
|
||||
[#]: via: "https://opensource.com/article/23/3/non-code-contribution-open-source"
|
||||
[#]: author: "Debra Chen https://opensource.com/users/debra-chen"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "Cubik65536"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
不编写代码也可以为开源项目做出贡献
|
||||
======
|
||||
|
||||
对于不同的人来说，开源“社区”意味着不同的东西。我认为开源有点像“爱情”，因为它是关于人和关系的。把开源当作一个社区，因为没有人，就没有源代码，无论是开源还是闭源。
|
||||
|
||||
我是 [Apache DolphinScheduler][1] 社区的成员。由于该项目有意保持低代码，因此它吸引了许多[非软件开发人员][2]。有时，那些不编写代码的人不确定是否有一种有意义的方式来为主要由源代码组成的开源项目做出贡献。我的经验告诉我，有，我将在本文中解释原因。
|
||||
|
||||
### 向社区做出贡献
|
||||
|
||||
在 Apache DolphinScheduler 项目中，我主要负责全球运营、影响力和社区关怀。
|
||||
|
||||
一些人会说项目是树而开源是土壤。这是一个恰当的比喻，它说明了积极培育你想要帮助成长的东西的重要性。
|
||||
|
||||
我有一个更简单的想法：尽一切可能使其变得更好。
|
||||
|
||||
一个社区需要不断的关注，不是因为它很贪心，而是因为它是生活的一部分。社区是你身边的人，无论是物理空间还是在线空间。
|
||||
|
||||
自从加入开源社区以来，我已经独立发起并组织了一些活动，包括：
|
||||
|
||||
- 平均每月在中国举办一次会议。
|
||||
- 建议社区参与大数据领域内的技术分享。
|
||||
- 协调了中国“大数据”领域几乎所有的开源项目，与这些社区进行了个别访问和交流。
|
||||
|
||||
在我看来，一个优秀的项目应该在一个良好的生态系统中成长。社区需要走出去，交换想法，分享资源，并与其他优秀的社区合作。每个人都应该感受到社区在工作中带来的好处。
|
||||
|
||||
我的海外扩张遵循相同的模式。当然，由于文化和语言的差异，这样做很困难。这需要耗费精力，但这是值得的。
|
||||
|
||||
到目前为止，我们已经在包括美国、印度、新加坡、德国、法国、芬兰等国家成功举办了会议。
|
||||
|
||||
所以我如何为 DolphinScheduler 做出贡献？我是否向项目提交代码？我是社区经理吗？我有正式的职称吗？
|
||||
|
||||
我认为自己是一个助手。我促进沟通和联系，这与任何代码贡献一样，都是“Apache Way”的一个例子。
|
||||
|
||||
### 从 DolphinScheduler 开始
|
||||
|
||||
我第一次接触开源是在 OpenAtom 基金会工作时，担任开源教育运营经理。作为中国第一个开源基金会，OpenAtom 运营了以 [OpenHarmony][3] 为代表的许多项目。
|
||||
|
||||
我加入了 DolphinScheduler 社区并发现了一群热衷于分享知识、提供指导和支持，并热衷于帮助其他人发现对他们自己的生活有用的工具的人。
|
||||
|
||||
DolphinScheduler 旨在成为一个拥有全球影响力的调度系统，帮助团队以 [敏捷][4] 和高效的方式工作。
|
||||
|
||||
### 对社区的第一印象
|
||||
|
||||
听到社区对项目开发的抱怨是一件常见的事情。我们都会时不时地抱怨。也许你报告了一个错误，但开发人员没有解决你的问题。或者，也许你有一个很棒的功能想法，但团队忽略了它。如果你是一个开源社区的成员，你以前就听到过这些不满，如果你没有，你最终会听到。
|
||||
|
||||
我了解到，这些声音对于开源社区来说都很重要。这是一个好现象，因为当你听到这些反馈时，这意味着社区愿意发现错误，报告它们，提出问题和回答问题。听到这些抱怨可能会揭示项目结构中需要改进的地方。社区中是否有志愿者可以回应错误报告并对它们进行分类，以便它们能够被分配给正确的开发人员？是否有一个志愿者组等待成立，以便迅速回应项目论坛或论坛中新人的问题？
|
||||
|
||||
开源项目的门口有一个招待员可以帮助邀请犹豫不决的社区成员。招待员还可以确保没有“门槛”。每个人都受欢迎，每个人都有自己的贡献，即使他们能提供的只是互相帮助的氛围。
|
||||
|
||||
尽管你我都希望能为每个人解决技术问题，但这是不现实的。但任何人都愿意帮助找到解决方案，这是社区的一个伟大优势。这些用户自发地充当了社区的“客户服务”部门。
|
||||
|
||||
在 DolphinScheduler 项目中，我们有很多人（Yan Jiang、Xu Zhiwu、Zhang Qichen、Wang Yuxiang、Xiang Zihao、Yang Qiyu、Yang Jiahao、Gao Chufeng 和 Gao Feng，顺序不分先后！）。即使他们不开发解决方案，他们也不遗余力地寻找能够开发解决方案的人。
|
||||
|
||||
### 给社区的话
|
||||
|
||||
如果你希望通过非代码贡献成为提交者，或者没有时间进行代码贡献，那么第一步就是加入社区。没有注册表格或批准流程，但也没有快速通道。你通过参与加入社区。你通过可靠且持续的参与与其他人建立关系。
|
||||
|
||||
我随时都可以聊天，总是渴望谈论全球活动组织、文档、反馈等。
|
||||
|
||||
### 成为提交者
|
||||
|
||||
Apache DolphinScheduler 面临着许多挑战。大多数公司，即使是支持开源的公司，也会选择非开源的商业工具。我希望与社区合作伙伴一起，使 DolphinScheduler 成为世界级的调度系统。我希望每个人都可以收获他们想要的技术成果，而 DolphinScheduler 可以帮助他们实现这一目标。
|
||||
|
||||
加入我们的社区，帮助我们推广开放和敏捷的工作方式。或者找到一个需要你非编码技能的项目。发现让你的同龄人社区获得力量是多么酷和有趣！
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/23/3/non-code-contribution-open-source
|
||||
|
||||
作者：[Debra Chen][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[Cubik65536](https://github.com/Cubik65536)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/debra-chen
|
||||
[b]: https://github.com/lkxed/
|
||||
[1]: https://dolphinscheduler.apache.org/en-us
|
||||
[2]: https://opensource.com/article/21/2/what-technical
|
||||
[3]: https://gitee.com/openharmony
|
||||
[4]: https://opensource.com/article/22/5/practical-tips-agile
|
||||
Loading…
Reference in New Issue
Block a user