2022年，做开源的朋友–参与开源的3个F原则

看到社区伙伴分享的一篇文章The Three F’s of Open Source Development，讲的是面对开源的态度，翻译下，分享给开源社区上的朋友。为公司效力，要有狠忍滚的觉悟；面对开源社区，也要有3F的觉悟。^_^。

翻译该文，不代表赞同原作者的全部观点。参与开源社区是个共赢的过程，向社区反馈缺陷，提交修复代码，都是非常鼓励的。不能辱骂开源软件维护者，社区参与者不应该抱怨，减少戾气，而是积极参与贡献，优化改进。下面开始翻译。

我编写并发布开源代码，经常收到有关我发布的内容的错误修复，补丁，请求和问题。大多数反馈都是令人尊重、有帮助的。但是，偶尔会有其他请求。在我计划屏蔽和忽略他们之前，会重定向该页面给他们以示警告。

I write and publish open source code. I quite often get bug fixes, patches, requests and questions regarding the things I have published. Most of the feedback is respectful and helpful. However occasionally there are other requests. This page is where I plan to redirect them as a final warning before I block and ignore them.

参与开源社区时，请了解下3F原则。The three F’s to open source development.

Fix it, Fork it, F**k off.

1、Fix it 修复缺陷

如果您发现错误，注意到功能缺失，不正确或误导性的文档，或者想要增强功能，您的第一个选择是提出修复请求。在所选的错误/需求跟踪系统中提交问题。即使是对维护者发一条推文也可能足够好。但是，这不是您唯一的选择。您可以选择自己修复补丁后提交补丁，或者如果您缺乏技能，请向其他人支付费用。你也可以付钱给维护者来为你解决这个问题。如果有足够的价值让你提出问题，也许有足够的价值来支付来解决它？

If you find a bug, notice missing, incorrect or misleading documentation, or want an enhancement, your first option is to make a request to fix it. Raise the issue in the bug/request tracker of choice. Heck even a tweet at the owner might be good enough. However that is not your only option. You can choose submit a patch after you fix it yourself, or if you lack the skills, pay someone else to do so. You could also offer to pay the maintainer to resolve this for you. If there is enough value for you to raise the issue, perhaps there is enough value to pay to resolve it?

但是，维护者有权拒绝您的补丁，关闭您提交的错误issue或拒绝您的付款提议，因为这是他们的项目。那么你应该生气并开始辱骂他们吗？不，您应该转到下一个F。

The maintainer however has all rights to reject your patch, close your bug ticket or turn down your offer of payment. It is their project. So should you get angry and start abusing them? No. You should move to the next F of open source software.

2、Fork it 另起炉灶

如果维护者拒绝进行更改，那么您可以选择分叉项目。如果你的项目变得更好，它自然会得到更多的关注，更具包容性。有许多成功的分叉项目 https://en.wikipedia.org/wiki/List_of_software_forks ，所以这是一个可行的策略。没有技能？请记住，您始终可以付钱给某人来维护您的分叉项目，或者将您想要的更改实施到您自己的版本中。

If the maintainer refuses to make your change, then you have the option to fork the project. If your project becomes better it will naturally gain more attention and be more inclusive. There are many successful forked projects https://en.wikipedia.org/wiki/List_of_software_forks so this is a viable strategy. Don’t have the skills? Remember you can always pay someone to maintain your fork, or to implement the changes you want into your own version.

3、F**k off 安静离开

最后一种选择是安静走开，如果您不愿意提交补丁，维护分叉或付款修复。没有必要辱骂维护者，反复提交错误缺陷，通过推特骚扰他们。所有这些都导致人们不想免费贡献他们的时间和专业知识，它也使你成为一个讨厌鬼。永远记住，你是在与一个真正的人交谈，仅仅因为他们关于如何实施项目的想法与你自己的想法不一致，并不意味着你有任何权利辱骂他们。

The last option is to frankly bugger off. If you are unwilling to either submit a patch, maintain a fork or put your money where you mouth is just go away. There is no need to abuse the maintainer, repeatedly post the bug, harass them over twitter. All this results in is people wanting to not contribute their time and expertise for free. It also makes you a douche-bag. Always remember you are talking to a real human being, and just because their ideas of how to implement a project are not in line with your own does not mean you have any right to abuse them.

参考资料

• The Three F’s of Open Source Development