Abstract
Infrastructure-as-Code can be designed, developed, and managed with an Open-Source Software approach. While openly embraced by academia, the OSS philosophy typically elicits some skepticism among industrial partners who want to ensure that adopting it will not enable their market competitors or harm them in any way, like by releasing valuable intellectual property into the wild.In this paper, we study this phenomenon from the perspective of game-theory, to then draw conclusions on what information to share, when, why, how, and with whom, so that risks are minimized, and benefits are maximized for each, and every partner engaged in IaC-focused collaborative projects that make use of an OSS approach.