5 common pitfalls in open source projects

Mention of open source, from software, hardware and ideas have become more and more popular, the application form is also more abundant. If the enterprise wants to start a new open source project, the five Open source project "traps" proposed by the OpenSource website should be paid attention to, at the same time, the project execution has been carried out, by understanding that it can be done effectively and smoothly at any stage.

Only you support

If you plan to release an Open-source product, you need to have a deep understanding of what "support you need" means. Don't count on the community to help you provide product support, and everyone will think that what they do is important and supported by millions of people. Also do not expect a large number of community volunteers to spontaneously pour into your support forums to help you answer questions. In open source projects you must be responsible for the project, the team will be responsible for dealing with various issues, encourage http://www.aliyun.com/zixun/aggregation/6579.html "> users to ensure that users can easily achieve product applications."

Innovation leader

For an open source product it means that it is open, and any user can create a process of its own and make changes and submit a merge request to the original author. This means that new features created by the open source community can help improve the product. But do not rely on the innovation of the community to serve you, need to continue to innovate products, the new features of the setup, planning and product improvement, become the leader of innovation.

Open Source Culture

Open source culture is very different from the corporate culture of most enterprises. The culture around an Open-source project team is very important. Volunteers and donors devote their time and talent, but they do not receive direct financial rewards. If money is not a driving factor, what should you use to motivate them? Community atmosphere? Ideal for a great cause? Help friends? Everyone participates in open source projects for different reasons, whatever the reason, as long as they gather together, can form the culture of the project. A product that lacks open source culture is bound to fail.

Key business Objectives

Your open source products and organizations must have a business goal, that is, you must be clear about your choice or vision. If you don't define your business direction correctly, communities and organizations cannot understand why you are making decisions. At the same time, the key business and objectives should be open and transparent. And can be aimed at differences and different opinions, to be prepared to interpret. If your business definition is wrong, it will attract the wrong community support and eventually lead to failure.

The courage to face failure

Everyone is afraid of failure, but a successful open source project needs to be perfected in failure, overcoming obstacles and learning differences. If you are too worried about failure, afraid of trying, afraid of innovation, you will lose the possibility of success. There are many manifestations of fear of failure: indecision, making decisions to please others, or clearly being the right decision but missing the opportunity for fear of making mistakes. Your open source community will feel this information, making this lack of commitment to open source projects finally become worse.

Therefore, before the open source project, if not aware of these five simple things, can lead to significant mistakes. While there are other pitfalls to avoid, open source is not a solution in itself, it is a method, a process, a community, and a product license. Obviously, do not simply declare a project open source, planning open source projects to be confident and ultimately successful.