同步阅读进度,多语言翻译,过滤屏幕蓝光,评论分享,更多完整功能,更好读书体验,试试 阅读 ‧ 电子书库
Chapter�燨pen Source
Programming in the New Unix燙ommunity
Table of Contents
Unix and Open Source
Best Practices for Working with Open-Source Developers
Good Patching PracticeGood Project- and Archive-Naming PracticeGood Development PracticeGood Distribution-Making PracticeGood Communication PracticeThe Logic of Licenses: How to Pick One
Why You Should Use a Standard License
Varieties of Open-Source Licensing
We concluded Chapter�a> by observing the largest-scale pattern in Unix's history; it flourished when its practices most closely approximated open source, and stagnated when they did not. We then asserted in Chapter�/a> that open-source development tools tend to be of high quality. We'll begin this chapter by sketching an explanation of how and why open-source development works. Most of its behaviors are simply intensifications of long-established Unix-tradition practices.
We'll then descend from realm of abstraction and describe some of the most important folk customs that Unix has picked up from the open-source community — in particular, the community-evolved guidelines for what a good source-code release looks like. Many of these customs could be profitably adopted by developers on other modern operating systems as well.
We'll describe these customs on the assumption that you are developing open source; most are still good ideas even if you are writing proprietary software. The open-source assumption is also historically appropriate, because many of these customs found their way back into proprietary Unix shops via ubiquitous open-source tools like patch(1), Emacs, and GCC.
Prev Up Next
Best Practices for Writing Unix Documentation Home 燯nix and Open Source
请支持我们,让我们可以支付服务器费用。
使用微信支付打赏