@proceedings {1889,
	title = {Investigating Relationships Between FLOSS Foundations and FLOSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {14-22},
	publisher = {Springer},
	abstract = {Foundations function as vital institutional support infrastructures for many of the most successful open source projects, but the role of these support entities remains an understudied phenomenon in FLOSS research. Drawing on Open Hub (formerly known as Ohloh) data, this paper empirically investigates the different ways these entities support projects and interact with different projects and with each other.},
	doi = {10.1007/978-3-319-57735-7_2},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_2},
	author = {Juho Lindman and Hammouda, Imed}
}
@inbook {Hirao2016,
	title = {The Impact of a Low Level of Agreement Among Reviewers in a Code Review Process},
	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 = {97{\textendash}110},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Software code review systems are commonly used in software development. In these systems, many patches are submitted to improve the quality. To verify the quality, voting is commonly used by contributors; however, there still exists a major problem, namely, that reviewers do not always simply reach a broad agreement. In our previous study, we found that consensus is not usually reached, implying that an individual reviewer{\textquoteright}s final decision usually differs from that of the majority of the other reviewers. In this study, we further investigate the reasons why such situations often occur, and provide suggestions for better handling of these problems. Our analysis of the Qt and OpenStack project datasets allow us to suggest that a patch owner should select more appropriate reviewers who often agree with others{\textquoteright} decisions.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_8},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_8},
	author = {Hirao, Toshiki and Ihara, Akinori and Ueda, Yuki and Phannachitta, Passakorn and Matsumoto, Ken-ichi},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@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}
}
@inbook {Gamalielsson2016,
	title = {On Involvement in Open Standards: How Do Organisations Contribute to W3C Standards Through Editorship?},
	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 = {57{\textendash}70},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {On Involvement in Open Standards: How Do Organisations Contribute to W3C Standards Through Editorship?},
	address = {Cham},
	abstract = {Over the years, a number of open standards have been developed and implemented in software for addressing a number of challenges, such as lock-in, interoperability and longevity of software systems and associated digital artefacts. Understanding organisational involvement and collaboration in standardisation is important for informing any future policy and organisational decisions concerning involvement in standardisation. The overarching goal of the study is to establish how organisations contribute to open standards development through editorship. Specifically, the focus is on open standards development in W3C. Through an analysis of editorship for all W3C recommendations we contribute novel findings concerning organisational involvement and collaboration, and highlight contributions from different types of organisations and countries for headquarter of each organisation. We make three principal contributions. First, we establish an overall characterisation of organisational involvement in W3C standardisation. Second, we report on organisational involvement in W3C standardisation over time. Third, we establish organisational collaboration in W3C standardisation through social network analysis.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_5},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_5},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@proceedings {1785,
	title = {An Investigation of Migrating from Proprietary RTOS to Embedded Linux},
	year = {2015},
	month = {08/2015},
	abstract = {Embedded systems and the open source operating system
Linux have been going hand in hand for a long time now.
Companies using Linux for their embedded products are
praising it for being time and cost efficient when it comes to
performance and maintainability. Another solution for embedded
systems is a Real-Time Operating System (RTOS).
The goal of this this paper is to investigate whether a traditional
proprietary RTOS can be substituted with embedded
Linux, and if this kind of migration can lead to reduced licensing
costs and increased general quality of the system.
We used a qualitative research method for this case-study.
The investigation was conducted with interviews as the main
source of information. The result of this study is an empirical
model we named {\textquoteright}Embedded Linux Adoption Model{\textquoteright}.
We concluded that in many cases a proprietary RTOS can
be substituted with embedded Linux without affecting the
critical needs of the system. The study also showed that
many embedded system developers are very receptive to
open source solutions and could think of contributing to the
community.},
	url = {http://www.opensym.org/os2015/proceedings-files/p101-muchow.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p101-muchow.pdf},
	author = {Oscar Muchow and David Ustarbowski and Hammouda, Imed}
}
