Getting involved with the discussion in and around an open-source project is a great way to make a contribution - and your patches will be considered more seriously if you're contributing positively in any way you can. Joining an existing project means there are other people already interested, and with so much time invested already, they may be more resistant to moving to a new project. Take advantage of the existing interest and join something already in progress!
purely my opinion: Open source relies heavily on community support (for me the keyword is "community"), so starting a project similar to what already exists is really dividing the community, rather then bringing it together. So in short, dive in and dedicate your knowledge to the existing project. I am sure everyone will be glad to have an educated and skillful person on board.
I'd opt for helping out with pulseaudio, since that way you can build off their existing infrastructure rather than chipping away at it with competition. No sense in reinventing the wheel (or the wheel manufacturing process).
For FOSS, I would only suggest starting a new project if the existing software projects were so totally broken you don't think there's any hope for them. (Or as an educational experience, of course)
当您的域是 Linux 音频时，有很多需要了解，然后才能声称“知道如何解决它”。 ALSA、PulseAudio等项目的负责人都思考过这个问题。
很有可能已经有聪明、有能力的人在思考你所感知的问题。 几乎可以肯定，帮助他们重新开始会更好。
另请注意，真正问题可能是配置和部署问题，而不是底层代码。 这可能是一个更容易解决的问题。
The time to start a new project is when you see an unaddressed problem and know how to fix it...
When your domain is Linux audio, there is a lot to know, before you can claim to "know how to fix it". The people responsible for ALSA, PulseAudio, and other projects have thought about this problem.
Odds are very good that there are smart and capable people already thinking about the problems that you perceive. You are almost certainly better off helping them that starting over again.
Also note that there is a chance that the real problem is one of configuration and deployment, not underling code. And that might be a simpler problem to contribute to.
It would be silly to preemptively fork the project when you don't know if you have to. Submit your patches. If they aren't being responsively handled (or the whole design needs to be redone) then think about possibly forking.
发布评论
评论（7）
参与开源项目内部和周围的讨论是做出贡献的好方法 - 如果您以任何方式做出积极贡献，您的补丁将得到更认真的考虑。 加入现有项目意味着其他人已经感兴趣，并且已经投入了大量时间，他们可能更不愿意转向新项目。 利用现有的兴趣并加入已经在进行中的事情！
Getting involved with the discussion in and around an open-source project is a great way to make a contribution - and your patches will be considered more seriously if you're contributing positively in any way you can. Joining an existing project means there are other people already interested, and with so much time invested already, they may be more resistant to moving to a new project. Take advantage of the existing interest and join something already in progress!
纯粹是我的意见：
开源在很大程度上依赖于社区支持（对我来说，关键词是“社区”），因此启动一个与现有项目类似的项目实际上是在分裂社区，而不是将其聚集在一起。 简而言之，深入研究并将您的知识奉献给现有项目。 我相信每个人都会很高兴有一个受过教育且技术精湛的人在船上。
purely my opinion:
Open source relies heavily on community support (for me the keyword is "community"), so starting a project similar to what already exists is really dividing the community, rather then bringing it together. So in short, dive in and dedicate your knowledge to the existing project. I am sure everyone will be glad to have an educated and skillful person on board.
我会选择帮助pulseaudio，因为这样你就可以构建他们现有的基础设施，而不是通过竞争来削弱它。 重新发明轮子（或轮子制造过程）没有任何意义。
对于自由开源软件，如果现有的软件项目完全崩溃，你认为它们没有任何希望，我只会建议开始一个新项目。 （当然，或者作为一种教育经历）
I'd opt for helping out with pulseaudio, since that way you can build off their existing infrastructure rather than chipping away at it with competition. No sense in reinventing the wheel (or the wheel manufacturing process).
For FOSS, I would only suggest starting a new project if the existing software projects were so totally broken you don't think there's any hope for them. (Or as an educational experience, of course)
当您发现未解决的问题并知道如何解决它时，就开始启动新项目...
当您的域是 Linux 音频时，有很多需要了解，然后才能声称“知道如何解决它”。 ALSA、PulseAudio等项目的负责人都思考过这个问题。
很有可能已经有聪明、有能力的人在思考你所感知的问题。 几乎可以肯定，帮助他们重新开始会更好。
另请注意，真正问题可能是配置和部署问题，而不是底层代码。 这可能是一个更容易解决的问题。
The time to start a new project is when you see an unaddressed problem and know how to fix it...
When your domain is Linux audio, there is a lot to know, before you can claim to "know how to fix it". The people responsible for ALSA, PulseAudio, and other projects have thought about this problem.
Odds are very good that there are smart and capable people already thinking about the problems that you perceive. You are almost certainly better off helping them that starting over again.
Also note that there is a chance that the real problem is one of configuration and deployment, not underling code. And that might be a simpler problem to contribute to.
请不要启动另一个 Linux 音频系统。 阅读 Linux 音频：一团糟 和 欢迎来到丛林，然后再编写任何代码。
Please, don't start Yet Another Linux Audio System. Read Linux audio: it's a mess and Welcome To The Jungle before you code anything.
我会提交补丁。 否则，您将面临发明轮子并加剧混乱的风险。
Joel 间接对此进行了描述。
I would submit patches. Otherwise, you risk inventing the wheel and adding to the chaos.
Joel wrote about this indirectly.
当您不知道是否必须这样做时，先发制人地分叉该项目是愚蠢的。 提交您的补丁。 如果它们没有得到响应式处理（或者整个设计需要重做）那么考虑可能的分叉。
It would be silly to preemptively fork the project when you don't know if you have to. Submit your patches. If they aren't being responsively handled (or the whole design needs to be redone) then think about possibly forking.