How is open source made?

Open source software is the shortest route that can now bring innovation to market. When it comes to the reputation of millions of developers and will download new code under open source licenses for new tasks, you can almost feel the world's technology baseline has been higher. But will the far-reaching effects of open source stop at this moment?

Over the past few years, GitHub is one of the most popular cloud-controlled versions and versions of the library service, but gradually, people no longer think so. Recently, at a small conference, several managers in several companies agreed to promote the development of open source code through collaborative, autonomous organization, and distributed approaches--for the development of http://www.aliyun.com/zixun/aggregation/12997.html " > Enterprise software provides a more attractive new model.

Actually, what does this model look like? In a RedMonk meeting, Ryan Tomayko, who claims to be GitHub's first developer employee, succinctly describes the core idea of the idea:

In other words, the simplicity of the process is also a necessary condition for efficient operation, compared with a complex enterprise development organization. As a distributed and collaborative open source organization, GitHub has certain restrictions on the smooth running of open source projects. All communications must be electronic and published, and the participants are generally widely distributed everywhere, so this is an open audit trail and accountability for all issues discussed. Each job is done asynchronously, so there is little dependency and bottlenecks to avoid.

GitHub itself is a platform that can provide an open platform for this collaboration pattern. In fact, it is hard to overestimate the impact of GitHub in accelerating the pace of software development, as it has brought more and more ease to participation and collaboration.

All of the participants have already deployed the GitHub Enterprise version of the mainland. As the platform opens up, what happens when you apply the open source model to the enterprise, and people choose their favorite projects to develop?

How can you ensure that developers meet security and compliance goals, especially if the OpenSSL has crashed? I think many enterprise development organizations will reject these thinking and doubt the impact of the "agile" workflow. But the idea of open source cannot be completely abandoned.

But it's hard to ignore the huge innovation impact that open source and GitHub have on software development. At the Realtime Conference conference held a year ago, Mikeal Rogers that Node.js's astonishing success was due to the presence of GitHub, which lowered the entry threshold for the project.

But the question is: Can a popular open source model work well in a business? Can it be grafted into an existing enterprise development culture, or does it need to be properly transformed? One thing is for sure, the success of open source innovation means that this model should not be overlooked.

From: http://code.csdn.net/news/2820266