分叉一个开源项目的最佳实践是什么? [英] What's the best practice to fork an open source project?

问题描述

我需要自定义一个开源项目.所做的更改是针对特定组织的，对公共项目无用.代码更改包括禁用组织不需要的功能(影响5％的代码)，为组织自定义其他功能(影响20％的代码)以及添加新的自定义功能(添加约10％的新代码). /p>

我可以从当前版本开始，然后从那里进行自定义.但是，原始项目将继续取得进步并引入新功能，我希望能够将这些改进纳入其中.

管理此问题的最佳方法是什么?现在，我只能获得可用的发行版本，但是不久我应该对原始项目的Subversion存储库具有只读访问权限.我是使用Subversion存储库的新手，但也可以将其用于我的代码.

解决方案

最好的办法是不要分叉它.为什么不弄清楚如何对其进行改进，以便它将按您希望的方式工作而不丢失任何现有功能.如果代码大小是个问题，也许您可​​以花一些时间来分叉代码，以提高现有项目的效率.

I need to customize an open-source project. The changes are for a specific organization and will not be useful to the public project. The code changes include disabling features not needed by the organization (affecting 5% of the code), customizing other features for the organization (affecting 20% of the code), and adding new custom features (adding about 10% new code).

I could start with the current version and customize from there. However, the original project continues to make advances and introduce new features, and I would like to be able to incorporate these improvements as they come along.

What's the best way to manage this? Right now, I can only get release versions as they become available, but I should soon have read-only access to the original project's Subversion repository. I'm new to using Subversion repositories, but have them available to use for my code as well.

解决方案

The best thing to do is not to fork it. Why not figure out how to improve it so it will do what you want it to do and not lose any existing functionality. If code size is an issue, maybe you can spend some of the time you would spend forking it on improving the existing projects efficiency.

这篇关于分叉一个开源项目的最佳实践是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！