debian发行版代号
by Kurian Benoy
通过库里安·贝诺(Kurian Benoy)
Gitlab发行工程师和Debian开发人员Balasankar C的访谈 (Interview with Gitlab Distribution Engineer and Debian Developer Balasankar C)
This is another chapter of the series where we interview amazing people who work in the Open source World.
这是本系列的另一章，我们将采访在开源世界工作的杰出人士。
Balasankar (Balu) C is an active Free and Open Source (FOSS) contributor. He has been contributing to various FOSS organisations like Debian, Gnome, Firefox, Swathanthra Malayalam Computing, Diaspora, and WikiGrandhashala for the past 9 years. He is involved in contributions ranging from language computing to software packaging and software development. He is a Debian Developer, Gnome foundation member and Mozillian. Apart from his day job at Gitlab, he contributes most of his time to open source projects.
Balasankar(Balu)C是活跃的自由和开源(FOSS)贡献者。 在过去的9年中， 他为Debian ， Gnome ， Firefox ， Swathanthra Malayalam Computing ，Diaspora和WikiGrandhashala等各种FOSS组织做出了贡献。 他参与的工作范围从语言计算到软件包装和软件开发。 他是Debian开发人员，Gnome基金会成员和Mozillian。 除了在Gitlab上的日常工作外，他大部分时间都用于开源项目。
关于本系列： (About the Series:)
I have been contributing to many Open source projects in organisations like CloudCV and FOSSASIA. It has been a wonderful learning experience for me personally and I’ve met a lot of amazing mentors.
我一直为CloudCV和FOSSASIA等组织的许多开源项目做出贡献。 就我个人而言，这是一次很棒的学习经历，我遇到了很多很棒的导师。
The main aim of this interview series is to motivate more people to contribute to FOSS projects after hearing these stories. I hope you might see some patterns from these amazing people that get you motivated to contribute to Open source projects. As Mario Behling, co-founder FOSSASIA says: just contribute, and opportunities will fly towards you.
本系列访谈的主要目的是在听完这些故事后激发更多的人为FOSS项目做出贡献。 希望您能从这些了不起的人那里看到一些模式，这些模式使您有动力为开源项目做出贡献。 正如FOSSASIA的共同创始人Mario Behling所说：贡献自己，机会就会飞向您。
So without further adieu, here’s the transcript of the interview.
因此，下面是访谈的笔录。
Kurian Benoy: Hello Balu, Thank you for taking the time to do this interview after your amazing talk at Facebook Developer Circle, Kochi.
库里安·贝诺伊(Kurian Benoy)：您好，巴鲁，感谢您在高知Facebook开发者圈的精彩演讲后抽出宝贵时间接受采访。
Balasankar C: No problem. It’s a pleasure to be part of this series.
Balasankar C：没问题。 很高兴成为这个系列的一部分。
Kurian Benoy: What’s the difference between open source and free-software? Some say it’s just politics and that beginners shouldn’t care about it. What do you feel?
Kurian Benoy：开源和自由软件之间有什么区别？ 有人说这只是政治，而初学者不应该在意它。 你感觉怎么样？
Balasankar C: Consider a yellow pencil being placed here. You may say it’s a sharp pencil, considering its functionality. Nithin may say it’s a yellow pencil, considering its appearance. When you think about open source software and free software, this is exactly the difference. Both free software and open source software are based on the four freedoms.
Balasankar C：考虑在这里放置一支黄色铅笔。 考虑到其功能，您可能会说它是一支锋利的铅笔。 考虑到其外观，Nithin可能会说这是一支黄色铅笔。 当您考虑开放源代码软件和自由软件时，这是完全不同的。 自由软件和开源软件都基于这四个自由。
Free software philosophy gives importance to freedom. Open source considers it as a development methodology, where multiple people share and look at the code. This way, bugs can easily be fixed. As Linus Torvalds quotes: “With enough eyeballs, all the bugs are shallow”.
自由软件哲学重视自由。 开源将其视为一种开发方法，多个人可以共享并查看代码。 这样，可以轻松修复错误。 正如莱纳斯·托瓦尔兹(Linus Torvalds)所说：“有了足够的眼球，所有的臭虫都是浅的”。
Open source methodology says, by providing these freedoms, the product itself gets better. Open source gives emphasis on collaborative development, and when multiple people with differing expertise and diversity look at the code, it forms a great product at the end.
开源方法论说，通过提供这些自由，产品本身就会变得更好。 开源强调协作开发，当具有不同专业知识和多样性的多个人查看代码时，最终将形成一个很好的产品。
Free software considers itself as an extension of the society. If you look at how the world has progressed, you can see that it has been through sharing of natural resources, knowledge, techniques, etc.
自由软件将自己视为社会的延伸。 如果您观察世界的进步，就会发现它是通过共享自然资源，知识，技术等而实现的。
When you are coding, more than often you are extending upon, or basing your work on existing knowledge. Access to this knowledge was available to you because its original creators didn’t put barriers in your way. So, ethically, you locking down your creation, thus preventing others from making better stuff out of it, is simply wrong.
在进行编码时，您比以往更多地基于现有知识进行扩展或基于现有知识进行工作。 您可以使用此知识，因为它的原始创建者并未妨碍您。 因此，从伦理上讲，您锁定自己的创作，从而阻止其他人从中创作出更好的东西，这是完全错误的。
Imagine, if you bought a bicycle and the company tells you that you can’t pedal your bicycle backwards or that you can’t change the color of your cycle, it seems illogical. Because you have a sense of ownership over the bicycle and hence know that you have the freedom to work on your cycle without restrictions from the company. Similarly, in the case of Software, it’s your right to understand how it works. So saying that you can’t modify a software you have bought is illogical.
想象一下，如果您购买了一辆自行车，而公司却告诉您您不能向后踩踏板，或者您无法更改自行车的颜色，那似乎是不合逻辑的。 因为您对自行车有一种主人翁感，因此知道您可以不受公司的限制自由地骑自行车。 同样，对于软件，您有权了解其工作方式。 因此说不能修改已购买的软件是不合逻辑的。
To answer your question, no, beginners shouldn’t be concerned about this. I respect Stallman and understand his vision. Open source didn’t make any mistakes. His politics and philosophy about working is necessary and our society is actually built on a sharing culture. Our end goal is still a free software world and we should care about the philosophy. Yet we need to take baby steps and work towards this goal. Such a compromise made to work is open source software. As a beginner, you needn’t be concerned about terms like Free Software, FOSS nor FLOSS. As a beginner, understand that freedom matters and all this is based on the four freedoms.
要回答您的问题，不，初学者不必为此担心。 我尊重斯托曼，理解他的远见。 开源没有犯任何错误。 他关于工作的政治和哲学是必要的，我们的社会实际上是建立在一种共享文化之上的。 我们的最终目标仍然是自由软件的世界，我们应该关注这种哲学。 但是，我们需要采取一些步骤，朝着这个目标努力。 这样的折衷方案是开源软件。 作为初学者，您不必担心诸如自由软件，FOSS或FLOSS之类的术语。 作为初学者，请理解自由很重要，而所有这一切都是基于四种自由。
In the initial years of my free software journey, I was an adamant Free Software advocate, and was very vocal about the term Open Source. But, my views have changed from the experience I gained during the journey, and I have different opinions about the entire situation.
在我从事自由软件之旅的最初几年，我是坚定的自由软件倡导者，并且对“开源”一词非常直言不讳。 但是，从旅途中获得的经验来看，我的观点已经改变，并且我对整个情况有不同的看法。
So, a beginner need not be concerned about getting it right from the beginning itself. You gain this knowledge as you talk with others and work on projects. What is important is that you contribute to projects.
因此，初学者不必担心从一开始就将其正确设置。 与他人交谈并从事项目工作时，您会获得此知识。 重要的是您为项目做出了贡献。
Kurian Benoy: What are best practices to start contributing to an Open source organization?
Kurian Benoy：开始为开源组织做贡献的最佳实践是什么？
Balasankar C: The way you contribute to various open-source projects depends on the type of project and also style of how an Organization functions. What I am going to say is a general workflow on how to contribute:
Balasankar C：您为各种开源项目做出贡献的方式取决于项目的类型以及组织运作方式的风格。 我要说的是有关贡献的一般工作流程：
- Read the contributors’ guide and the README of the projects. 阅读贡献者指南和项目的自述文件。
- Check the issue list of the project. 检查项目的问题列表。
- Read Code styles and the code guidelines to be followed. For example, please don’t leave your code un-indented. ? 阅读代码样式和要遵循的代码准则。 例如，请不要让您的代码缩进。 ？
- Read the source code of the project, which can often be found in GitLab or GitHub. 阅读项目的源代码，通常可以在GitLab或GitHub中找到。
- Attempt to solve the issue. If you can’t, try joining IRC/Gitter rooms related to the project, or any other developer forums. Never hesitate to ask questions. 尝试解决问题。 如果不能，请尝试加入与该项目或任何其他开发人员论坛相关的IRC / Gitter会议室。 毫不犹豫地提问。
- Open a pull request. 打开拉取请求。
- If you find a problem, go on and send an e-mail or interact on forums like Gitter. Start a good conversation with a contributor. 如果发现问题，请继续发送电子邮件或在Gitter之类的论坛上进行互动。 与贡献者开始良好的对话。
- Keep contributing to the project. Contributions can be anything like fixing bugs, documentation, localisation of a particular service, or code contributions. 继续为项目做贡献。 贡献可以是诸如修复错误，文档，特定服务的本地化或代码贡献之类的任何事情。
Kurian Benoy: What do you think about Open-source incentives like Hacktoberfest and others? Beyond getting T-shirt’s what should people focus on with these programs? Will merely a Hacktoberfest make an Open source contributor?
Kurian Benoy：您如何看待Hacktoberfest等开源激励措施？ 除了获得T恤之外，人们还应该关注这些程序？ 仅仅是Hacktoberfest会成为开源贡献者吗？
Balasankar C: The whole idea of Hacktoberfest, according to me, is good and getting a T-shirt is a great motivation to many. Getting a T-shirt is never a problem. After all, companies like to hand you freebies. What matters, is what you have done after the Hacktoberfest. Have you followed up on your pending PRs which are in the feedback phase? Are you still continuing to contribute to Open source? These are the real questions. If the only thing you’ve got out of the Hacktoberfest was a T-shirt, then your T-Shirt becomes pointless.
Balasankar C：根据我的说法，Hacktoberfest的整个构想是好的，获得一件T恤衫对许多人来说是一个很大的动力。 买一件T恤从来都不是问题。 毕竟，公司喜欢给您赠品。 重要的是您在Hacktoberfest之后所做的事情。 您是否已跟踪处于反馈阶段的未决PR？ 您还在继续为开源做贡献吗？ 这些是真正的问题。 如果您仅从Hacktoberfest中脱颖而出，那就是一件T恤，那么您的T恤就毫无意义了。
Essentially, if you didn’t find any passion contributing to FOSS projects, any idea of what the project is about, you essentially wasted your time (the project maintainers at least got a contribution/fix from you. ?
本质上，如果您没有发现对FOSS项目有贡献的热情，对项目的意义有任何想法，那实际上就浪费了您的时间(项目维护者至少从您那里得到了贡献/修复。
The important thing, according to me, is how working on the project inspired you. If it got you curious about fixing the problem you were working on, or got you interested in learning more about the project, it was time well spent. One regular example where I don’t see this happen is Google Summer of Code. Most of the time, participants stop contributing to the project after GSoC, and this often gets raised as a concern - “Are people in GSoC only for money?”
对我来说，重要的是，该项目的工作如何启发了您。 如果它使您对解决正在解决的问题感到好奇，或者对学习更多有关该项目的兴趣感兴趣，那么这就是花费的时间。 我看不到这种情况的一个常规示例是Google Summer of Code。 大多数情况下，参与者在GSoC之后停止为该项目做贡献，而这常常引起人们的关注-“ GSoC中的人是否只是为了钱？”
So, getting a T-Shirt is fun. It is not a taboo. But, it becomes worthy if it got you on a path of contribution.
因此，获得T恤很有趣。 这不是禁忌。 但是，如果它能使您走上贡献之路，就变得很有价值。
Other than getting swag, one reason people do this is to claim themselves as “open source contributors”. What is funny is, most of them don’t realize that it doesn’t take that much to do a proper, continuous contribution to FOSS projects. Basic English learning, and a curiosity to learn and you can be a very successful contributor, and will not have to depend on any gimmicks.
除了赃物外，人们这样做的一个原因是声称自己是“开源贡献者”。 有趣的是，大多数人没有意识到为FOSS项目做出适当，持续的贡献并不需要那么多。 基本的英语学习和学习的好奇心使您可以成为非常成功的贡献者，而不必依赖任何头。
If your thought process is “People in industry are excited to hire open source people, so having all these feathers on my hat would be awesome”, there is a slight problem there. Yes, FOSS contributors have a good opportunity in the industry. But, when it comes to hiring, it is not that difficult to check if you are a proper contributor or not - whether you are a good fit for the company or not. And companies often do that check. ?
如果您的思维过程是“行业内的人们很高兴雇用开源人员，那么在我的帽子上戴上所有这些羽毛会很棒”，那么那里就有一个小问题。 是的，FOSS贡献者在该行业中拥有很好的机会。 但是，在招聘方面，检查您是否是合适的供款人并不困难-您是否适合公司。 公司通常会进行检查。 ？
Kurian Benoy: What’s the difference between GitHub and GitLab. Why should we use GitLab?
Kurian Benoy： GitHub和GitLab有什么区别。 为什么要使用GitLab？
Balasankar C: I will start off by saying good things about GitHub. GitHub has been here for about 12 years and many of the major FOSS projects use GitHub for code hosting. GitHub popularized collaborative development and has helped open source methodology very much.
Balasankar C：首先，我会说一些有关GitHub的好东西。 GitHub已经存在了大约12年，许多主要的FOSS项目都使用GitHub进行代码托管。 GitHub促进了协作开发，并极大地帮助了开源方法。
However, I find GitLab to be superior, from both philosophical and practical points of view. Philosophically, even though GitHub has contributed quite a lot to FOSS, their core code base is still proprietary. Whereas, GitLab has most of its code base released under MIT license, and even the proprietary parts of the code base is “source available” (meaning you can read the code and even clone the repo. You just can’t violate the license).
但是，从哲学和实践的角度来看，我都认为GitLab更具优势。 从哲学上讲，尽管GitHub为FOSS做出了很大贡献，但他们的核心代码库仍然是专有的。 而GitLab的大部分代码库都是根据MIT许可发布的，甚至该代码库的专有部分也可以“获得源代码”(这意味着您可以阅读代码，甚至克隆存储库。您不能违反许可证) 。
From the practical point of view, as a user, I find GitLab to have a much larger collection of features compared to GitHub. Features like Continuous Integration and Continuous Deployment (CI/CD) support for all static site generators in GitLab Pages etc are features that will be useful to many users.
从实际的角度来看，作为用户，我发现GitLab具有比GitHub大得多的功能集合。 对GitLab页面中所有静态站点生成器的持续集成和持续部署(CI / CD)支持等功能对于许多用户而言都是有用的。
I consider GitHub mainly as a “code sharing platform with review ability”, whereas GitLab covers the entire DevOps lifecycle.
我认为GitHub主要是“具有审阅能力的代码共享平台”，而GitLab涵盖了整个DevOps生命周期。
Now, diving a bit into the features of GitLab, I mentioned above it covers the entire DevOps lifecycle. It means, from having an idea and discussing it with your peers, to implementing that code in an IDE to deploying the code to different environments and monitoring those deployments, GitLab provides you tools to do all of this - in the same interface. So, unlike other solutions where you have to jump between multiple services to perform all this, you can just use GitLab.
现在，我稍微提到了GitLab的功能，上面提到了它涵盖了整个DevOps生命周期。 这意味着，从构想和与同行讨论，到在IDE中实施该代码，再到将代码部署到不同的环境并监视这些部署，GitLab提供了在同一个界面中执行所有这些操作的工具。 因此，与其他解决方案不同，在其他解决方案中，您必须在多个服务之间切换才能执行所有这些操作，而您只能使用GitLab。
I mentioned GitLab has a proprietary part too. This mostly involves features that make sense to bigger companies (say, with more that 250 employees) - features like Epics, or Roadmaps, or multiple group issue boards, etc.
我提到过GitLab也有专有部分。 这主要涉及一些对大型公司有意义的功能(例如，拥有250名以上的员工)，例如Epics，Roadmaps或多个小组发行委员会等功能。
Most of the code that a regular user or even a SME needs is available as Free Software. For just this reason, I consider GitLab to have a more friendly approach and commitment towards Free Software.
普通用户甚至中小企业需要的大多数代码都可以作为免费软件获得。 出于这个原因，我认为GitLab对自由软件有更友好的方法和承诺。
Kurian Benoy: We absolutely love Debian! What do you think is the future of Debian?
Kurian Benoy：我们绝对喜欢Debian ！ 您认为Debian的未来如何？
Balasankar C: The future of Debian depends on the future of Linux. If the question is about the Debian packages (with Snaps and Flatpaks and Docker containers here), I don’t think any drastic change will happen anytime soon. We are talking about a huge repository with about 70,000 packages.
Balasankar C： Debian的未来取决于Linux的未来。 如果问题是关于Debian软件包(这里有Snaps，Flatpaks和Docker容器)，我认为短期内不会发生任何重大变化。 我们正在谈论的是一个拥有约70,000个软件包的庞大存储库。
How the technical stack around Debian (packages, build tools, workflows etc.) changes will depend on its derivatives also, mainly Ubuntu. Whatever problems I have with Ubuntu, there is no denying the fact that Ubuntu stands top as the most used GNU/Linux distribution. So, how that company drives the project forwards will have a serious impact on both Debian and other derivative projects.
Debian周围的技术堆栈(软件包，构建工具，工作流程等)如何变化也将取决于其衍生版本，主要是Ubuntu。 不管我在Ubuntu上遇到什么问题，都不能否认Ubuntu是最常用的GNU / Linux发行版。 因此，该公司如何推动项目前进将对Debian和其他衍生项目产生严重影响。
In my opinion, just how RedHat made “Enterprise Linux” a thing, Ubuntu introduced GNU/Linux to home users. Whether it be by their marketing skills, or design decisions, they made a serious impact on the popularity of GNU/Linux.
在我看来，正是RedHat如何使“ Enterprise Linux”成为现实，Ubuntu向家庭用户介绍了GNU / Linux。 无论是通过营销技巧还是设计决策，都对GNU / Linux的普及产生了严重影响。
Personally, I think Debian as an OS badly needs some marketing. I don’t mean we will die without that, but I think it will surely help. I haven’t seen Debian doing any sort of proper publicity efforts, or attempts to make it more popular among home users. It is a huge hit among system administrators, because of its legendary stability, so that position in the market is secure. But if we were to expand the horizons, we will have to think differently.
就个人而言，我认为Debian作为操作系统非常需要一些营销。 我并不是说没有这些我们会死的，但是我认为这一定会有所帮助。 我还没有看到Debian进行任何适当的宣传工作，也没有试图使其在家庭用户中更受欢迎。 由于其传奇般的稳定性，它在系统管理员中倍受青睐，因此可以确保其在市场中的地位。 但是，如果我们扩大视野，我们将不得不以不同的方式思考。
Kurian Benoy: What do you think about Open source Licenses like MIT and GPLv3?
Kurian Benoy：您如何看待MIT和GPLv3等开源许可证？
Balasankar C: This relates to something I mentioned earlier. I consider a society where all software is Free to be a glorious end goal - something, as FOSS evangelists, we all should be working for and strive to achieve. And GPL is the best option in such a society.
Balasankar C：这与我之前提到的事情有关。 我认为，一个免费使用所有软件的社会将成为光荣的最终目标-作为FOSS传播者，我们都应该为实现这一目标而努力奋斗。 在这样的社会中，GPL是最好的选择。
However, to reach that end goal, we have to travel quite a bit, and try to make all sectors understand the cause. This definitely includes industry. It is not a surprise that GPL is not a favorite of industry, because it automatically makes any associated code to be released under GPL (except the cases under mere aggregation, which lets you embed a binary of a GPL licensed software with another software without releasing the whole under GPL license). Industry, by its very nature, has a for-profit mindset, and are wary of anything that can affect that profit. So, “releasing everything you make so that others can modify it and distribute it themselves” is a bit scary for them. Whether they are right or wrong is another discussion, but the fact is that such an issue exists.
但是，要达到这个最终目标，我们必须走很多路，并努力使所有部门了解原因。 这绝对包括行业。 GPL不受业界欢迎并不奇怪，因为GPL会自动使任何相关代码在GPL下发布(仅在聚合情况下除外，它使您可以将GPL许可软件的二进制文件与另一软件嵌入而不发布)。根据GPL许可整体进行)。 从本质上讲，行业具有营利性思维，并且对可能影响利润的任何事物保持警惕。 因此，“释放您所做的一切，以便其他人可以对其进行修改并自行分发”对于他们来说有点吓人。 他们是对还是错是另一个讨论，但事实是存在这样一个问题。
Permissive licenses, in my opinion, cater to this issue. They, while ensuring the immediate user gets all four freedoms, don’t put further restrictions on the developer. I consider them to be a necessary compromise in the current socio-economic situation. The main advantage I see is that, it resulted in companies using FOSS projects and releasing most of their libraries under these licenses - thus making them Free Software. So, in totality, it resulted in more free software in the world. Yes, it is not ideal, but it is unavoidable.
我认为，许可许可证可解决此问题。 他们在确保直接用户获得所有四个自由的同时，不对开发人员施加进一步的限制。 我认为它们是当前社会经济形势下的必要折衷办法。 我看到的主要优点是，这导致公司使用FOSS项目并根据这些许可发布其大多数库，从而使它们成为免费软件。 因此，总的来说，它导致了世界上更多的免费软件。 是的，这不是理想的选择，但这是不可避免的。
(Personally, I recently started licensing all my personal code under both a copyleft and MIT license. I tell my users that I prefer if they used the copyleft license and contributed to the cause, but I leave the decision to the users.)
(我个人最近开始使用copyleft和MIT许可来许可我的所有个人代码。我告诉我的用户，我更喜欢他们是否使用copyleft许可并促成原因，但我将决定留给用户。)
Kurian Benoy: What’s difference between FOSS Enthusiasts and ordinary people who graduate from college?
库里安·贝诺伊(Kurian Benoy)： FOSS爱好者和大学毕业生之间有什么区别？
Balasankar C: This is a question I usually get - as a student why should I contribute to FOSS. From my personal experience, I can guarantee you something. While attending a campus placement interview, if you are a FOSS contributor, you are by default above all of your peers. It is because being a FOSS contributor gives you some specific, and unique skills, that all employers want.
Balasankar C：这是我通常会遇到的一个问题-作为一名学生，为什么我应该为FOSS做出贡献。 根据我的个人经验，我可以向您保证。 在参加校园安置面试时，如果您是FOSS的撰稿人，则默认情况下，您的排名高于所有同行。 这是因为成为FOSS贡献者可以为您提供所有雇主都想要的一些特定而独特的技能。
A mindset to fix problems - You contributed to a FOSS project not because someone forced you or not because you were promised anything. You did it because you were curious about a problem, or an issue, and had a mentality to sit down, spend some time and fix the problem. It doesn’t matter if the fix was just a spelling mistake or a 100 line code implementing a major feature. What matters is that there was a problem and you put in the effort to solve that problem, mainly because you had a passion to do so. Employers love those with passion, because it is that passion that drives innovation and brings in efficiency.
解决问题的心态 -您为FOSS项目做出了贡献，并不是因为有人强迫您，还是因为有人答应了您而没有。 您之所以这样做，是因为您对一个问题或一个问题感到好奇，并且有坐下来，花一些时间来解决问题的心态。 修复只是拼写错误还是实现主要功能的100行代码都没关系。 重要的是存在一个问题，您付出了很多努力去解决这个问题，这主要是因为您有这样做的热情。 雇主喜欢那些充满激情的人，因为正是这种激情推动了创新并带来了效率。
Coding Etiquette - While contributing to a FOSS project, often the people you interact with are people who have been doing this for quite some time. And that experience will be reflected in their feedback to you, and eventually on the work you do. For example, a university training its students on proper coding practices or giving coding guidelines is a rare sight in India. But, industry expects programmers to follow standard guidelines, proper styles, etc. They often bridge this gap by providing a training course to new hires. But, if you are a FOSS contributor, chances that you already know about all this is pretty high, which makes the job of an employer easier.
编码礼节 -在为FOSS项目做贡献时，经常与您互动的人已经从事了相当长的时间。 这些经验将反映在他们对您的反馈中，并最终反映在您所做的工作中。 例如，在印度，一所大学对学生进行正确的编码实践或给出编码准则的培训是很少见的。 但是，行业期望程序员遵循标准准则，适当的样式等。他们通常通过为新员工提供培训课程来弥合这种差距。 但是，如果您是FOSS贡献者，那么您已经很了解这一切的机会非常高，这使雇主的工作变得容易。
Teamwork and tools - Just like coding standards, something else you get familiar while contributing to a FOSS project is teamwork. Most of the FOSS projects involve contributors from all over the world, and it is with this diverse workforce you are regularly communicating and interacting. There is no better opportunity to understand how to work well with a team.
团队合作和工具 -就像编码标准一样，在为FOSS项目做贡献时您会熟悉的其他东西就是团队合作。 大部分FOSS项目都涉及来自世界各地的贡献者，而正是由于这些多样化的员工队伍，您才能定期进行交流和互动。 没有更好的机会来了解如何与团队合作。
Kurian Benoy: Thank you so much for doing this interview.
库里安·贝诺(Kurian Benoy)：非常感谢您接受这次采访。
Thank you for exploring this interview along with me. If you found it resourceful, appreciation in the form of claps, shares would be really appreciated!
感谢您与我一起探索这次采访。 如果您以拍手的形式发现它的足智多谋，升值，您将不胜感激！
Also your feedback helps me to better improve this series in the future, so do comment about the same if any. Until the next Open Source Hero we interview, goodbye and keep on contributing to Open source!
另外，您的反馈意见将帮助我将来更好地改进本系列，因此请对相同内容进行评论。 在我们采访下一个开源英雄之前，再见，并继续为开源做贡献！
debian发行版代号
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
