How to select an Open Source Library

The rich open-source resources provide convenience for developers, but how to find the open-source libraries suitable for their own projects among the many open-source resources (Editor's note: the Libraries here refer to the frameworks, function libraries, class libraries, or other components available in development .) What about it? Foreign developer Daniel marbach (his introduction) Detailed related skills in his blog.

Daniel marbach believes that the use of open-source libraries can greatly increase the development speed. He often encourages his team members to select open-source libraries for development. His selection tips are as follows:

1. select an appropriate open source license based on the nature of your project.

For the customers and application objects of the software you develop, it is very important to apply the license. For example, in a regulated environment, only apache2 is available.

2. determine the type of problem you want to solve.

For example, is software distribution, caching, persistence, or loose coupling required?

3. Extract problematic meta tags and descriptive phrases.

For example, if the problem you want to solve is about the Optimal Path on multiple machines, your tags or phrases may be genetic algorithms, Job-Shop scheduling, planning charts, optimization scheduling algorithms, and shortest paths.

4. Browse codeplex, Google Code or SourceForge (github.com is also a valuable website), and list the open source libraries that have been initially filtered out.

For example, in the IOC/di list, you can find ninject, structuremap, autofac, Windsor, and other open-source projects.

5. Find the home page of these projects, view the latest project progress, and mark those projects that have not been updated for a long time or that have stopped development.

Pay attention to the news, announcements, submission records, and website updates on the homepage. I usually delete items from the list that haven't been updated for more than 6 months.

6. Go to the code library page and find the relevant test components.

We recommend that you delete a project without a unit test component from the list. Maybe you think this requirement is too harsh. But if there is no unit test, how can we ensure the quality of this project?

7. Confirm relevant documents on the project homepage.

Delete the items that do not have a document, code example, or applicable guide from the selected project list. After all, learning a new tool or framework requires a certain amount of effort. A comprehensive and meticulous document is very necessary.

8. Retrieve the project source code from the version control system and check whether there are extension points ).

The ideal open-source library or framework does not limit your use of a specific log framework or dependency injection container (di container ). Multiple extension points provide you with the possibility of customized log systems and containers.

There are other filtering principles that you can examine based on your project requirements:

> Is a build script attached )?

> Does the open-source project team continue to use the same integrated development environment?

> Is there a clear road map for this open-source project?

> Is there an issue tracker in this project )?

> Are Community patches coming soon?

> Is the feedback on this project quick in the community?

> Are other developers happy to use the open-source library and learn about the project in the community?

> How many active project contributors are there?

> Is version number management clear?

> What are the improvements and integration of the Project for specific needs from the community?

Csdn Translation

Link: http://www.planetgeek.ch/2010/06/20/how-to-select-open-source-libraries/