Five Steps to Creating a Compliant Open Source Project

Here's Ellan Ponikiewicz, who shared his experience with software development at the Nuance team. Most developers know that open source The code is used as a source code by the engineers in the development process with high frequency, and many software platform-related solutions are also from the open source community masterpiece.Maybe you do not know, and the interaction between open source code Management is a stubborn task, sometimes with the help of Black Duck Software, and here's what the author is saying about the five requirements for compliance with the open source rules.

1. Make a business case

First, the first step is to develop a strong business case for open source regulation, which is the cornerstone. You also need to understand what the basic functionality of the software you create, how to use it, and what solid foundation can you bring to a comprehensive compliance program when combined with open source code? At the Nuance team, we look for the weaknesses and benefits of the current software development process and test the stress on the software while simulating customer needs and maximizing corporate standards.

Get top leadership support

Any successful business has a strong management backing to support the R & D team. In order to gain the support and trust of Nuance leadership, we must list the benefits that a healthy open source compliance program can bring to the company: a better user experience, more patents, and a secure software development environment. More and more customers are asking how we can apply open source software to our solutions, but understanding this is not a difficult task if you have a relatively complex program. Given our use of open source code in proprietary code, the main thing is to protect the transaction process, make it safer and the community work more efficiently. Using these communities and open source code can also reduce the risk in the development process.

3. Identify the appropriate type of system

Choosing the right system for your community is also an important step. Of course, the decision-making process involves several factors: the available system operations and system maintenance staff, the IP infrastructure, the project scope, and a budget that is sufficient. Take the Nuance team as an example. Previously, the development team did not have enough bandwidth to develop and maintain the system itself, and now we rely on Black Duck's experts and tools to solve problems on most of our open source compliance systems.

4. Overview of open source policies and procedures

No matter what kind of open source compliance system you choose, you have to solve a lot of inherent tasks to ensure the success of open source projects. The fourth article refers to the general preparation of appropriate development policies and procedures. When an open-source policy is written, companies need to think about every aspect of their business needs so that they are concerned with what kind of open source components they use to accomplish their development tasks. While some companies prohibit the use of special open source licenses, some companies still make extensive use of open source methods and make their processes known to the public.

5. Internal communication and training

If there is no such a final step, a good open-source policy is ultimately nothing more than empty talk. For the use of open-source software and safety performance experience, predecessors have summed up a lot. Therefore, training and exchange of open source knowledge within the company is necessary to help develop a cohesive open source software that is of great help to the company in open source management and strategic development.

Written in the end: A strong open source compliance program helps help to emphasize user needs, business systems and security issues. At the same time, it is far more useful to create an effective risk response mechanism in advance than just a strategy developed for open source software.