Login  |  繁體中文
感謝您對「自由軟體鑄造場」的支持與愛護,十多年來「自由軟體鑄造場」受中央研究院支持,並在資訊科學研究所以及資訊科技創新研究中心執行,現已完成階段性的任務。 原網站預計持續維運至 2021年底,網站內容基本上不會再更動。本網站由 Denny Huang 備份封存。
也紀念我們永遠的朋友 李士傑先生(Shih-Chieh Ilya Li)。
For Developers Working with the community

Open Source Software license

We provide Open Source Software license and legal materials via this page.

 

Working with the community

1. What is "the community"?

In open source software the concept of 'the community' is important, because it is the core unit to run the open source software development. Often a community consists of developers of the software, users of the software and other interested people.

Every community is different and has different goals, methods and requirements. An approach that works with one community might not work with another. Some communities welcome corporate cooperation, while others will be quite hostile about it. Bigger communities, like the Linux kernel, almost always welcome corporate cooperation.

2. Why would I want to work with an open source community?

Working with the community has advantages. For example, if you use code from a project and make changes to it, you can benefit from submitting it for inclusion in the "upstream" source. This means that:
  • if a newer version of the software is released, you will not have to apply your changes again * your code will get peer review and will probably be improved
  • it is good PR for your company
  • GPL license management is easier because there are no patches that can be forgotten when making a source code distribution

3. How do I work with an open source community?

There are a few core rules that you will need to follow to increase the chance of a contribution being accepted:
  • Use the coding style that the project uses. The developers are used to this and will sometimes refuse your code if it uses a different style
  • Don't expect that big patches will be accepted right away. Some patches need revision before they are accepted, because they are too specific for one user and don't benefit a lot of users.
  • Be open, and ask questions if you don't understand something.
  • Don't take criticism personally. Many developers can be rude, especially on the Linux kernel mailing lists. This is because writing good code is what they pride in. They expect other people to write good code too, and they are not very subtle. Just remember that it is not personal and it is not a criticism of your company. They just care about code quality.

4. Getting help

There are companies who provide consultancy on working with FOSS and with contributing to communities. Examples include large providers like IBM and HP, small management consultancy companies like Olliance and Opendawn, and engineer-focused consultancies like HMW Consulting and Loohuis Consulting.


Copyright © 2010 Armijn Hemel, gpl-violations.org,
This work is available under the Creative Commons Attribution-No Derivative Works 3.0 Unported license.




Category: For Developers