@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}
}
@proceedings {1892,
	title = {Measuring Perceived Trust in Open Source Software Communities},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {49-54},
	publisher = {Springer},
	abstract = {We investigate the different aspects of measuring trust in Open Source Software (OSS) communities. In the theoretical part we review seminal works related to trust in OSS development. This investigation provides background to our empirical part where we measure trust in a community (in terms of kudo). Our efforts provide further avenues to develop trust-based measurement tools. These are helpful for academics and practitioners interesting in quantifiable traits of OSS trust.},
	doi = {10.1007/978-3-319-57735-7_5},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_5},
	author = {Syeed, M.M. Mahbubul and Juho Lindman and Hammouda, Imed}
}
@inbook {Bibi2016,
	title = {A Bayesian Belief Network for Modeling Open Source Software Maintenance Productivity},
	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 = {32{\textendash}44},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {A Bayesian Belief Network for Modeling Open Source Software Maintenance Productivity},
	address = {Cham},
	abstract = {Maintenance is one of the most effort consuming activities in the software development lifecycle. Efficient maintenance within short release cycles depends highly on the underlying source code structure, in the sense that complex modules are more difficult to maintain. In this paper we attempt to unveil and discuss relationships between maintenance productivity, the structural quality of the source code and process metrics like the type of a release and the number of downloads. To achieve this goal, we developed a Bayesian Belief Network (BBN) involving several maintainability predictors and three managerial indices for maintenance (i.e., duration, production, and productivity) on 20 open source software projects. The results suggest that maintenance duration depends on inheritance, coupling, and process metrics. On the other hand maintenance production and productivity depend mostly on code quality metrics.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_3},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_3},
	author = {Bibi, Stamatia and Apostolos Ampatzoglou and Ioannis Stamelos},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Rodr{\'\i}guez-P{\'e}rez2016,
	title = {BugTracking: A Tool to Assist in the Identification of Bug Reports},
	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 = {192{\textendash}198},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {BugTracking: A Tool to Assist in the Identification of Bug Reports},
	address = {Cham},
	abstract = {Issue tracking systems are used, in most software projects, but in particular in almost all free open source software, to record many different kinds of issues: bug reports, feature requests, maintenance tickets and even design discussions. Identifying which of those issues are bug reports is not a trivial task. When researchers want to conduct studies on the bug reports, managed by a software development project, first of all they need to perform this identification.
The job for researchers here is very different from the bug triaging that researchers do. In the latter case, people with a considerate experience in the project make a decision based on the information available at that time (maybe just a short comment by some user), asking, if needed, for more details. In the former case, researchers usually have not that experience in the project, but they have at their use all the information produced, until the moment the issue was closed. This may include not only all comments and actions on the issue tracking system, but for example, discussions about a fix in the code review system, or the final fixing patch in the source code management system. Having all that information conveyed to the researchers, in an easy, flexible and quick way, accelerates and makes their decision process much more reliable. It simplifies large scale manual analysis of issues (in hundreds or thousands), helping researchers to ensure that they are really working with what they intend to work: bug reports.
This paper presents a tool designed to solve exactly the problem of providing the researchers with all the relevant information needed to decide whether an issue corresponds to a bug report or not. The tool uses information extracted automatically from the projects repositories. It offers a web-based interface which allows collaboration, traceability and transparency of the identification of bug reports. All this makes the process easier, faster, and more reliable.},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_16},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_16},
	author = {Rodr{\'\i}guez-P{\'e}rez, Gema and Gonzalez-Barahona, Jes{\'u}s M. and Gregorio Robles and Dalipaj, Dorealda and Sekitoleko, Nelson},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Kalliamvakou2016,
	title = {Certification of Open Source Software {\textendash} A Scoping Review},
	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 = {111{\textendash}122},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Certification of Open Source Software {\textendash} A Scoping Review},
	address = {Cham},
	abstract = {Open source software (OSS) systems are being used for increasingly critical functions in modern societies, e.g., in health care, finance, government, defense, and other safety and security sensitive sectors. There is an increasing interest in software certification as a means to assure quality and dependability of such systems. However, the development processes and organizational structures of OSS projects can be substantially different from traditional closed-source projects. The distributed, {\textquotedblleft}bazaar-style{\textquotedblright} approach to software development in OSS systems is often perceived incompatible with certification. This paper presents the results of a scoping review on certification in OSS systems in order to identify and categorize key issues and provide a comprehensive overview of the current evidence on this topic.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_9},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_9},
	author = {Kalliamvakou, Eirini and Weber, Jens and Knauss, Alessia},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Murphy2016,
	title = {Classifying Organizational Adoption of Open Source Software: A Proposal},
	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 = {123{\textendash}133},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Classifying Organizational Adoption of Open Source Software: A Proposal},
	address = {Cham},
	abstract = {Staged adoption models are a common feature of information systems (IS) adoption literature, yet these are rarely used in open source software (OSS) adoption studies. In this paper, a staged model for classifying the organizational adoption of OSS is proposed, based upon a critical review of existing staged adoption models and factors identified from OSS adoption literature. Innovations in the proposed model include: defined transition pathways between stages, additional stages and a decomposition of cessation of use into four distinct pathways.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_10},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_10},
	author = {Murphy, Stephen and Cox, Sharon},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Harzl2016,
	title = {Combining FOSS and Kanban: An Action Research},
	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 = {71{\textendash}84},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Combining FOSS and Kanban: An Action Research},
	address = {Cham},
	abstract = {Even though Free and Open Source Software (FOSS) and Agile Software Development (ASD) have been recognized as important ways to develop software, share some similarities, and have many success stories, there is a lack of research regarding the comprehensive integration of both practices. This study attempts to consolidate these methods and to answer if FOSS and ASD can be combined successfully. Action Reseach (AR) is conducted with one sub-team of a large FOSS project. We performed two action research cycles based on the Kanban method. This paper has two main contributions; first, it describes a real world situation, where Kanban is applied to a FOSS project, and second, it suggests two new Kanban practices. These two methods are targeted specifically at FOSS projects and their characteristics.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_6},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_6},
	author = {Harzl, Annemarie},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Crowston2016,
	title = {Core-Periphery Communication and the Success of Free/Libre Open Source Software Projects},
	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 = {45{\textendash}56},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {We examine the relationship between communications by core and peripheral members and Free/Libre Open Source Software project success. The study uses data from 74 projects in the Apache Software Foundation Incubator. We conceptualize project success in terms of success building a community, as assessed by graduation from the Incubator. We compare successful and unsuccessful projects on volume of communication by core (committer) and peripheral community members and on use of inclusive pronouns as an indication of efforts to create intimacy among team members. An innovation of the paper is that use of inclusive pronouns is measured using natural language processing techniques. We find that core and peripheral members differ in their volume of contribution and in their use of inclusive pronouns, and that volume of communication is related to project success.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_4},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_4},
	author = {Kevin Crowston and Shamshurin, Ivan},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Poo-Caama{\~n}o2016,
	title = {Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem},
	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 = {147{\textendash}162},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem},
	address = {Cham},
	abstract = {Release management in large-scale software development projects requires significant communication and coordination. It is particularly challenging in Free and Open Source Software (FOSS) ecosystems, in which hundreds of loosely connected developers and their projects need to be coordinated to release software to a schedule. To better understand this process and its challenges, we analyzed over two and half years of communication in the GNOME ecosystem and studied developers{\textquoteright} interactions. We cataloged communication channels, categorized high level communication and coordination activities in one of them, and triangulated our results by interviewing developers. We found that a release schedule, influence instead of direct control, and diversity are factors that impact positively the release process in the GNOME ecosystem. Our results can help organizations build better large-scale teams and show that research focused on individual projects might miss important parts of the picture.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_12},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_12},
	author = {Poo-Caama{\~n}o, Germ{\'a}n and Singer, Leif and Knauss, Eric and Daniel M. German},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@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}
}
@inbook {Berger2016,
	title = {An Open Continuous Deployment Infrastructure for a Self-driving Vehicle Ecosystem},
	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 = {177{\textendash}183},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {An Open Continuous Deployment Infrastructure for a Self-driving Vehicle Ecosystem},
	address = {Cham},
	abstract = {Self-driving vehicles are an ongoing research and engineering topic even though first automotive OEMs started to deploy such features to their premium vehicles. Chalmers University of Technology and University of Gothenburg are operating and maintaining a vehicle laboratory comprising 1/10 scaled cars, a Volvo XC90, and a Volvo FH truck to conduct studies with automated driving. This laboratory is used both from researchers from different disciplines and in education. The experimental software for all these platforms is powered by the same software environment for different hardware architectures. Therefore, maintaining and deploying new features and bugfixes to the users of this laboratory in a fast way needs to be organized in a reproducible yet easily maintainable manner. This paper outlines our open approach to encapsulate our build, test, and deployment process using VirtualBox, Docker, and Jenkins.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_14},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_14},
	author = {Berger, Christian},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Abdulwahhab2016,
	title = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	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 = {3{\textendash}15},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	address = {Cham},
	abstract = {This paper investigates the position of local open source communities (LOSCs) in the development of open source projects (OSPs). We have conducted an empirical study to examine the role of LOSCs, their way of working, and the benefits/challenges they experience compared to the overall global community. The qualitative investigation consisted of ten semi-structured interviews with members within different LOSCs. The results confirm the importance of LOSCs and the pivotal role they play in the development of OSPs. In many cases, they act as the middleman between individual members and the project{\textquoteright}s global community. However, LOSCs have their own kinds of challenges.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_1},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_1},
	author = {Abdulwahhab, Sinan and Alabady, Yazen and Sattar, Yacoub and Hammouda, Imed},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {AbbaspourAsadollah2016,
	title = {A Study of Concurrency Bugs in an Open Source Software},
	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 = {16{\textendash}31},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {A Study of Concurrency Bugs in an Open Source Software},
	address = {Cham},
	abstract = {Concurrent programming puts demands on software debugging and testing, as concurrent software may exhibit problems not present in sequential software, e.g., deadlocks and race conditions. In aiming to increase efficiency and effectiveness of debugging and bug-fixing for concurrent software, a deep understanding of concurrency bugs, their frequency and fixing-times would be helpful. Similarly, to design effective tools and techniques for testing and debugging concurrent software understanding the differences between non-concurrency and concurrency bugs in real-word software would be useful. This paper presents an empirical study focusing on understanding the differences and similarities between concurrency bugs and other bugs, as well as the differences among various concurrency bug types in terms of their severity and their fixing time. Our basis is a comprehensive analysis of bug reports covering several generations of an open source software system. The analysis involves a total of 4872 bug reports from the last decade, including 221 reports related to concurrency bugs. We found that concurrency bugs are different from other bugs in terms of their fixing time and their severity. Our findings shed light on concurrency bugs and could thereby influence future design and development of concurrent software, their debugging and testing, as well as related tools.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_2},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_2},
	author = {Abbaspour Asadollah, Sara and Sundmark, Daniel and Eldh, Sigrid and Hansson, Hans~ and Enoiu, Eduard Paul},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Coman2016,
	title = {Towards Open Source/Data in the Context of Higher Education: Pragmatic Case Studies Deployed in Romania},
	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 = {184{\textendash}191},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Towards Open Source/Data in the Context of Higher Education: Pragmatic Case Studies Deployed in Romania},
	address = {Cham},
	abstract = {The open source ideology is unfortunately not so popular in Romania. This subject represents, to this day, an untackled problem especially in various local educational areas. The paper describes an interesting initiative taken this year by the Faculty of Computer Science, University of Ia{\c s}i, Romania to change the collective opinion by progressively pushing the new generations of students through a binding process with the ideas involved in the open source philosophy. Three ongoing initiatives addressing this problem are detailed, including the results we have obtained so far through them, and also the steps that are planned to be taken soon on the matter.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_15},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_15},
	author = {Coman, Alexandru and C{\^\i}tea, Alexandru and Buraga, Sabin C.},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Heppler2016,
	title = {Who Cares About My Feature Request?},
	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 = {85{\textendash}96},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Previous studies on issue tracking systems for open source software (OSS) focused mainly on requests for bug fixes. However, requests to add a new feature or an improvement to an OSS project are often also made in an issue tracking system. These inquiries are particularly important because they determine the further development of the software. This study examines if there is any difference between requests of the IBM developer community and other sources in terms of the likelihood of successful implementation. Our study consists of a case study of the issue tracking system BugZilla in the Eclipse integrated development environment (IDE). Our hypothesis, which was that feature requests from outsiders have less chances of being implemented, than feature requests from IBM developers, was confirmed.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_7},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_7},
	author = {Heppler, Lukas and Eckert, Remo and Stuermer, Matthias},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Robles2016,
	title = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	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 = {163{\textendash}173},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	address = {Cham},
	abstract = {Women are underrepresented in the IT sector. But the situation in FLOSS (free, libre, open source software) development is really extreme in this respect: past publications and studies show a female participation of around 2 \% to 5 \% and have shed some light into this problem. In this paper, we give an update the state of knowledge to the current situation of gender in FLOSS, by analyzing the results of surveying more than 2,000 contributors to FLOSS projects in 2013, of which more than 200 were women. Our findings confirm that women enter the FLOSS community later than men, do primarily other tasks than coding, participate less if they have children, and have slightly different reasons to enter (and to stay in) the development communities they join. However, we also find evidence that women are joining FLOSS projects in higher numbers in recent years, and that the share of women devoting few hours per week to FLOSS and full-time dedication is higher than for men. All in all, comparing our results with the ones from the 2000s, the context of participation of women in FLOSS has not changed much.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_13},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_13},
	author = {Gregorio Robles and Reina, Laura Arjona and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Dom{\'\i}nguez, Santiago Due{\~n}as},
	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}
}
@conference {Syeed:2014:SCR:2641580.2641586,
	title = {Socio-Technical Congruence in the Ruby Ecosystem},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {2:1{\textendash}2:9},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Existing studies show that open source projects may enjoy high levels of socio-technical congruence despite their open and distributed character. Such observations are yet to be confirmed in the case of larger open source ecosystems in which developers contribute to different projects within the ecosystem. In this paper, we empirically study the relationships between the developer coordination activities and the project dependency structure in the Ruby ecosystem. Our motivation is to verify whether the ecosystem context maintains the high socio-technical congruence levels observed in many smaller scale FLOSS (Free/Libre Open Source Software) projects. Our study results show that the collaboration pattern among the developers in Ruby ecosystem is not necessarily shaped by the communication needs indicated by the dependencies among the ecosystem projects.
},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641586},
	url = {http://doi.acm.org/10.1145/2641580.2641586},
	author = {Syeed, M.M. Mahbubul and Hansen, Klaus Marius and Hammouda, Imed and Manikas, Konstantinos}
}
@inbook {1593,
	title = {Who Contributes to What? Exploring Hidden Relationships between FLOSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {21-30},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {In this paper we address the challenge of tracking resembling open source projects by exploiting the information of which developers contribute to which projects. To do this, we have performed a social network study to analyze data collected from the Ohloh repository. Our findings suggest that the more shared contributors two projects have, the more likely they resemble with respect to properties such as project application domain, programming language used and project size.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_3},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_3},
	author = {Syeed, M.M.Mahbubul and Hammouda, Imed},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@article {syeed2013evolution,
	title = {Evolution of Open Source Software Projects: A Systematic Literature Review},
	journal = {Journal of Software},
	volume = {8},
	number = {11},
	year = {2013},
	pages = {2815{\textendash}2829},
	abstract = {Open Source Software (OSS) is continuously gaining acceptance in commercial organizations. It is in this regard that those organizations strive for a better understanding of evolutionary aspects of OSS projects. The study of evolutionary patterns of OSS projects and communities has received substantial attention from the research community over the last decade. These efforts have resulted in an ample set of research results for which there is a need for up-to-date comprehensive overviews and literature surveys.

This paper reports on a systematic literature survey aimed at the identification and structuring of research on evolution of OSS projects. In this review we systematically selected and reviewed 101 articles published in relevant venues. The study outcome provides insight in what constitutes the main contributions of the field, identifies gaps and opportunities, and distills several important future research directions.},
	keywords = {flosshub},
	attachments = {https://flosshub.org/sites/flosshub.org/files/9913-25310-1-PB.pdf},
	author = {Syeed, Mahbubul and Hammouda, Imed and Syat{\"a}, Tarja}
}
@book {1538,
	title = {Socio-technical Congruence in OSS Projects: Exploring Conway{\textquoteright}s Law in FreeBSD},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {109 - 126},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Software development requires effective communication, coordination and collaboration among developers working on interdependent modules of the same project. The need for coordination is even more evident in open source projects where development is often more dispersed and distributed. In this paper, we study the match between the coordination needs established by the technical domain (i.e. source code) and the actual coordination activities carried out by the development team, such hypothetical match is also known as socio-technical congruence. We carry out our study by empirically examining Conway{\textquoteright}s law in FreeBSD project. Our study shows that the congruence measure is significantly high in FreeBSD and that the congruence value remains stable as the project matured.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_8},
	author = {Syeed, M.M. Mahbubul and Hammouda, Imed},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1463,
	title = {Open Source, Open Innovation and Intellectual Property Rights {\textendash} A Lightning Talk},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {298-303},
	publisher = {IFIP AICT,  Springer},
	abstract = {Open innovation projects are fast paced aiming at producing a quick proof of concept of an innovative software product. This need for speedy results makes the use of open source components as a basis for the work appealing. Open source brings with it an inherent risk of license conflicts that may become an issue when aiming to develop an innovative demo into an actual product. In this study, the first results of investigating the knowledge the participants of innovation projects have on intellectual property are presented. The effect this may have on the project results is also discussed.},
	author = {Kilamo, Terhi and Hammouda, Imed and Kairamo, Ville and Rasanen, Petri and Saarinen, Jukka P.}
}
@proceedings {1460,
	title = {Open Source Prediction Methods: A Systematic Literature Review},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {280-285},
	publisher = {IFIP AICT,  Springer},
	abstract = {For the adoption of Open Source Software (OSS) components, knowledge of the project development and associated risks with their use is needed. That, in turn, calls for reliable prediction models to support preventive maintenance and building quality software. In this paper, we perform a systematic literature review on the state-of-the- art on predicting OSS projects considering both code and community dimension. We also distill future direction for research in this field.},
	keywords = {Prediction Success, Systematic literature review},
	author = {Syeed, M.M. Mahbubul and Kilamo, Terhi and Hammouda, Imed and Syst{\"a}, Tarja}
}
@proceedings {1471,
	title = {OSSLI: Architecture Level Management of Open Source Software Legality Concerns},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {356-361},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {This paper presents a tool that addresses the legality concerns of open source at the level of software architecture, early in the development activity. The tool demonstrates the significance of licensing concerns at the architectural level by extending existing modeling tools with support for open source licensing issues.},
	author = {Lokhman, Alexander and Luoto, Antti and Abdul-Rahman, Salum and Hammouda, Imed}
}
@proceedings {1291,
	title = {Applying Open Source Practices and Principles in Open Innovation: The Case of the Demola Platform},
	year = {2011},
	month = {10/2011},
	pages = {307-311},
	publisher = {Springer},
	abstract = {In numerous fields, businesses have to rely on rapid development and release cycles. Variant new ideas and concepts can emerge through open innovation as the participants are not limited to the company scope. This makes open innovation an increasingly appealing option for the industry. One such open innovation platform, Demola, allows university students to work on real life industrial cases of their own interest. We have identified similarities with its way of operation to open source software development and find that it offers a viable motivational, organizational and collaborative solution to open innovation.},
	author = {Kilamo, Terhi and Hammouda, Imed and Kairamo, Ville and Rasanen, Petri}
}
@proceedings {1292,
	title = {KommGame: A Reputation Environment for Teaching Open Source Software},
	year = {2011},
	month = {10/2011},
	pages = {312-315},
	publisher = {Springer},
	abstract = {The importance of teaching open source software in universities is increasing with the advent of open source as a development and business model. A novel, student centric approach of teaching open source was tried out at Tampere University of Technology where a new environment called KommGame was introduced to assist in teaching open source development. This environment includes a reputation system to motivate learners to participate. In this paper, we present our approach of teaching open source and how the KommGame environment was employed to teach open source software.},
	author = {Goduguluri, Veerakishore and Kilamo, Terhi and Hammouda, Imed}
}
@article {1325,
	title = {Tool Assisted Analysis of Open Source Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {43 - 78},
	abstract = {Open Source Software (OSS) is currently a widely adopted approach to developing and distributing software. OSS code adoption requires an understanding of the structure of the code base. For a deeper understanding of the maintenance, bug fixing and development activities, the structure of the developer community also needs to be understood, especially the relations between the code and community structures. This, in turn, is essential for the development and maintenance of software containing OSS code. This paper proposes a method and support tool for exploring the relations of the code base and community structures of OSS projects. The method and proposed tool, Binoculars, rely on generic and reusable query operations, formal definitions of which are given in the paper. The authors demonstrate the applicability of Binoculars with two examples. The authors analyze a well-known and active open source project, FFMpeg, and the open source version of the IaaS cloud computing project Eucalyptus.},
	keywords = {artifacts, tools},
	issn = {1942-3934},
	doi = {10.4018/IJOSSP.2011040103},
	author = {Syeed, M.M. Mahbubul and Aaltonen, Timo and Hammouda, Imed and Syst{\"a}, Tarja}
}
@conference {1221,
	title = {From Proprietary to Open Source: Building a Network of Trust},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	abstract = {When a corporation is about to release a product as open source a large network of trust must be built and maintained. Open source and commercial domains have radically different aspects of trust. Still, trust is vital in products survival in both settings. This paper focuses on building cognitive, or rational, trust in both commercial and open source domains. We set the view angle so that trust can be approached via the various relationships between the stakeholders involved in the community building process. Towards this goal, the paper focuses on the first steps of the process by proposing a set of best practices.},
	keywords = {oss2010, osscomm, workshop},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm001.pdf},
	author = {Sirkkala, Petri and Hammouda, Imed and Aaltonen, Timo}
}
@conference {1220,
	title = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	abstract = {The Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010) aims at building a commu- nity of researchers and practitioners to share experiences and discuss chal- lenges involved in building and maintaining open source communities. De- tailed	information	regarding	the	workshop	is	available	at http://tutopen.cs.tut.fi/oscomm10/.},
	keywords = {oscomm, oscomm2010, oss2010, workshop},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm000.pdf},
	author = {Hammouda, Imed and Aaltonen, Timo and Capiluppi, Andrea}
}
@conference {600,
	title = {First International Workshop on Building Sustainable Open Source Communities (OSCOMM 2009)},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {353 - 354},
	publisher = {Springer},
	organization = {Springer},
	chapter = {32},
	abstract = {The First International Workshop on Building Sustainable Open Source Communities aims at building a community of researchers and practitioners to share experiences and discuss challenges involved in building and maintaining open source communities.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_32},
	attachments = {https://flosshub.org/sites/flosshub.org/files/First\%20International\%20Workshop.pdf},
	author = {Hammouda, Imed and Aaltonen, Timo and Capiluppi, Andrea}
}
@conference {575,
	title = {Opening Industrial Software: Planting an Onion},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {57 - 69},
	publisher = {Springer},
	organization = {Springer},
	chapter = {7},
	abstract = {This paper studies the problem of building open source communities for industrial software that was originally developed as closed source. We present a conceptual framework for planning the early stages of the release process highlighting the main stakeholders and concerns involved. The framework is illustrated by means of three industrial software platforms reporting first experiences of the community building process. In order to measure the effectiveness of the approach, the use of a quantitative and qualitative evaluation framework is advocated.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Opening\%20Industrial\%20Software.pdf},
	author = {Sirkkala, Petri and Aaltonen, Timo and Hammouda, Imed}
}
@conference {Orsila:2009:TIO:1527033.1527037,
	title = {Trust issues in open source software development},
	booktitle = {Proceedings of the Warm Up Workshop for ACM/IEEE ICSE 2010},
	series = {WUP {\textquoteright}09},
	year = {2009},
	note = {"We have selected two highly reusable libraries, zlib and FFmpeg. The software repository of the projects were downloaded, but mining the information is not an easy task and we considered various sources {\textemdash} such as bug reports, mailing lists, IRC conversations, and source code comments {\textemdash} in addition to the revision history. "},
	pages = {9{\textendash}12},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source software and the associated development model holds great promise, but the issue of trust is a major challenge. This applies to companies wishing to adopt the open source model but also within open source projects. We investigate this issue by data mining open source repositories to study two related phenomena: update propagation and distributed version control.},
	keywords = {ffmpeg, trust, version control, zlib},
	isbn = {978-1-60558-565-9},
	doi = {10.1145/1527033.1527037},
	url = {http://doi.acm.org/10.1145/1527033.1527037},
	author = {Orsila, Heikki and Geldenhuys, Jaco and Ruokonen, Anna and Hammouda, Imed}
}
@conference {540,
	title = {Update Propagation Practices in Highly Reusable Open Source Components},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {159 - 170},
	publisher = {Springer},
	organization = {Springer},
	chapter = {13},
	abstract = {In today{\textquoteright}s business and software arena, more and more companies are adopting open source software. An example of this rising phenomenon is to base software products on highly reusable open source components. In this scenario, the evolution of the software product is coupled with the evolution of the open source component. A common assumption is that component updates are immediately and regularly propagated to the project. This paper investigates this assumption empirically by studying update propagation practices in two popular open source libraries, zlib and FFmpeg. For each library, we analyze various repository sources with information such as bug reports, revision history, and source code. The results of the case studies suggest that update propagation is subject to several technical and non-technical factors including the way the open source library is used, the extent to which updates are documented, and the degree of community involvement. Based on these findings, we propose a set of recommendations that would allow better follow-up of updates and smoother update propagation.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_13},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Update\%20Propagation\%20Practice.pdf},
	author = {Orsila, Heikki and Geldenhuys, Jaco and Ruokonen, Anna and Hammouda, Imed}
}
