Working on continuous integration for "open source" technologies and software as knowledge.

Integration solutions are based on integrity of teamwork, integrity between different people/different teams. You should have integrated vision on goals, problems, solutions, pros and cons, estimates of value-ability, efforts.

why do I believe that " open source " can create added business value ?

Work with "open source" means that you are working in open space, in open world. Not only each line of code is open, but all questions are open. What is  the problem definition, what are the possible solutions ? pros, cons ? Why did you try to propose new implementation but not fix for existing ? Open discussion, it is very expensive thing but it can be very valuable because open discussion helps to validate. To validate approach, use case, feature, hypothesis, ideas.  Only if you can organize open discussion you can attract new users,  power that can validate, verify, improve. Of course sometimes it can be too expensive. But in real life you should realize that there is no absolute private world/private discussion, everything will be merged in some open discussion and will be part of open world.

It is business question, because it is about open market. And it is about special competitive advantage on market: you are open because you are ready for competition and you are ready for competition because you are the best and the fastest.

Some people thinks that openness is not secure and there are security cons. But I believe that security professionals can confirm that openness helps be more secure and helps have better security.

Are you ready for evaluation, verification of your business ideas, of you technical solutions ? Do you believe that your solutions are efficient,  competitive,  secure ?  What is the value of such questions ? I believe that your customers are your investors and your investors are you customers. It is big team of players in big game. And game is creation of knowledges and maintenance of knowledge models in actual state.

levels of evaluation and long-term strategy

Private knowledge it is such knowledge that are not ready for open evaluation.   Not ready for open evaluation in your team, in your department, in your company,  on market, in community. And important thing that in science, for example, huge value and big result is achieved when you have proofed failure of validation. "Which way does not work " A lot of projects were failed because they tried to keep private such type of knowledges.