@proceedings {1890, title = {Designing for Participation: Three Models for Developer Involvement in Hybrid OSS Projects}, volume = {496}, year = {2017}, month = {05/2017}, pages = {23-33}, publisher = {Springer}, abstract = {This paper reports governance practices of three profit oriented companies that develop OSS software with the help of their respective open development communities. We explore how the companies allow development contributions from external stakeholders, and what knowledge they let out of their internal software development activities. The results lay ground for further research on how to organize openness of the software development process in hybrid setups where the needs of different stakeholders are partly competing - yet complementary.}, keywords = {Community Management, Hybrid open source, open source}, doi = {10.1007/978-3-319-57735-7_3}, url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_3}, author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and Mikkonen, Tommi and M{\"a}nnist{\"o}, Tomi} } @inbook {M{\"a}enp{\"a}{\"a}2016, title = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities}, booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings}, year = {2016}, pages = {134{\textendash}146}, publisher = {Springer International Publishing}, organization = {Springer International Publishing}, chapter = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities}, address = {Cham}, abstract = {Today, the community driven development model extends into a variety of new, often web based collaborations. Among these are hybrid open source development set ups in which various online tools are used to facilitate cooperation between virtual teams of commercial and voluntary stakeholders. As yet, how these relationships form and evolve is not understood extensively. This article presents a longitudinal case study of a smartphone startup that founded its early product development strategy on reliance on feedback from its customers through a web based question and answer forum. With this, the company managed to extend values typical for open source communities to support development of its proprietary software. Our main findings include that the challenge in similar settings lies in striking the right balance between the open and the proprietary {\textendash} while overt openness may risk the competitive advantage of a company, leaving too much behind closed boundaries can create unnecessary friction in the relationship. }, isbn = {978-3-319-39225-7}, doi = {10.1007/978-3-319-39225-7_11}, url = {http://dx.doi.org/10.1007/978-3-319-39225-7_11}, author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and M{\"a}nnist{\"o}, Tomi}, editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman} }