@proceedings {1808,
	title = {How Do Free/Open Source Developers Pick Their Tools? A Delphi Study of the Debian Project},
	year = {2016},
	abstract = {Free and Open Source Software (FOSS) has come to play a critical role in the global software industry. Organizations are widely adopting FOSS and interacting with open source communities, and hence organizations have a considerable interest in seeing these communities flourishing. Very little research has focused on the tools used to develop that software. Given the absence of organizational policies and mandate that would occur in a traditional environment, an open question is how FOSS developers decide what tools to use. In this paper we report on a policy delphi study conducted in the Debian Project, one of the largest FOSS projects. Drawing from data collected in three phases from a panel of 21 experts, we identified 15 factors that affect their decision to adopt tools. This in turn can help FOSS communities to define a suitable policy of actions, in order to improve their processes.},
	keywords = {Delphi, Free/Open Source Software, Qualitative Study, study, tools},
	url = {https://www.researchgate.net/publication/291312269_How_Do_FreeOpen_Source_Developers_Pick_Their_Tools_A_Delphi_Study_of_the_Debian_Project},
	author = {Martin Krafft and Stol, Klaas-Jan and Fitzgerald, Brian}
}
@article {1747,
	title = {Inner Source--Adopting Open Source Development Practices within Organizations: A Tutorial},
	journal = {IEEE Software},
	year = {2015},
	month = {07/2015},
	pages = {1 - 1},
	publisher = {IEEE},
	abstract = {Inner source, the adoption and tailoring of Open Source development practices inside organizations, is a topic of increasing interest. While Inner Source offers a number of benefits, in our experience many practitioners are unclear as to what Inner Source is, and what steps to take towards adoption. In this article we present a tutorial in which we outline nine key factors, pertaining to product, process and organization, which we have found to be important in working with organizations who are interested in Inner Source. This paper illustrates these nine factors with three inner source initiatives that we have studied. },
	issn = {0740-7459},
	doi = {10.1109/MS.2014.77},
	author = {Stol, Klaas-Jan and Fitzgerald, Brian}
}
@article {1637,
	title = {Microblogging in Open Source Software Development: The Case of Drupal and Twitter},
	journal = {IEEE Software},
	volume = {31},
	year = {2014},
	month = {7/2014},
	pages = {72 - 80},
	abstract = {Microblogging is a popular form of social media that has quickly permeated both enterprise and open source communities. However, exactly how open source communities can leverage microblogging isn{\textquoteright}t yet well understood. The authors investigate how Drupal{\textquoteright}s open source community uses Twitter, a household name in microblogging. Their analysis of group and individual accounts of Drupal developers reveals that they take on similar but distinct roles. Both serve as communicators of essential links to a vast and growing community knowledge base, such as work artifacts, issues, documentation, and blog posts, but community members often express positive emotions when tweeting about work, which reinforces a sense of community.},
	issn = {0740-7459},
	doi = {10.1109/MS.2013.98},
	author = {Wang, Xiaofang and Kuzmickaja, Ilona and Stol, Klaas-Jan and Abrahamsson, Pekka and Fitzgerald, Brian}
}
@proceedings {1450,
	title = {Exploring the Role of Commercial Stakeholders in Open Source Software Evolution},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {178-200},
	publisher = {IFIP AICT},
	abstract = {It has been lately established that a major success or failure factor of an OSS project is whether or not it involves a commercial company, or more extremely, when a project is managed by a commercial software corporation. As documented recently, the success of the Eclipse project can be largely attributed to IBM{\textquoteright}s project management, since the upper part of the developer hierarchy is dominated by its staff. This paper reports on the study of the evolution of three different Open Source (OSS) projects {\textemdash} the Eclipse and jEdit IDEs and the Moodle e-learning system {\textemdash} looking at whether they have benefited from the contribution of commercial companies. With the involvement of commercial companies, it is found that OSS projects achieve sustained productivity, increasing amounts of output produced and intake of new developers. It is also found that individual and commercial contributions show similar stages: developer intake, learning effect, sustained contributions and, finally, abandonment of the project. This preliminary evidence suggests that a major success factor for OSS is the involvement of a commercial company, or more radically, when project management is in hands of a commercial entity.},
	author = {Capiluppi, Andrea and Stol, Klaas-Jan and Boldyreff, Cornelia}
}
@article {1383,
	title = {A comparative study of challenges in integrating Open Source Software and Inner Source Software},
	journal = {Information and Software Technology},
	volume = {53},
	year = {2011},
	month = {12/2011},
	pages = {1319 - 1336},
	abstract = {Context

Several large software-developing organizations have adopted Open Source Software development (OSSD) practices to develop in-house components that are subsequently integrated into products. This phenomenon is also known as {\textquotedblleft}Inner Source{\textquotedblright}. While there have been several reports of successful cases of this phenomenon, little is known about the challenges that practitioners face when integrating software that is developed in such a setting.
Objective

The objective of this study was to shed light on challenges related to building products with components that have been developed within an Inner Source development environment.
Method

Following an initial systematic literature review to generate seed category data constructs, we performed an in-depth exploratory case study in an organization that has a significant track record in the implementation of Inner Source. Data was gathered through semi-structured interviews with participants from a range of divisions across the organization. Interviews were transcribed and analyzed using qualitative data analysis techniques.
Results

We have identified a number of challenges and approaches to address them, and compared the findings to challenges related to development with OSS products reported in the literature. We found that many challenges identified in the case study could be mapped to challenges related to integration of OSS.
Conclusion

The results provide important insights into common challenges of developing with OSS and Inner Source and may help organizations to understand how to improve their software development practices by adopting certain OSSD practices. The findings also identify the areas that need further research.
Highlights

► We performed a case study that has adopted Open Source development practices. ► We studied the challenges encountered and approaches taken by the organization. ► We performed a systematic review to identify challenges related to Open Source. ► We compared the findings from the review to the findings from the case study. ► Most identified challenges could be mapped to the findings from the literature.},
	keywords = {Open Source Software;     Inner Source;     Software development;     Challenges;     Case study;     Empirical studies},
	issn = {09505849},
	doi = {10.1016/j.infsof.2011.06.007},
	url = {http://www.sciencedirect.com/science/article/pii/S095058491100142X},
	author = {Stol, Klaas-Jan and Ali Babar, Muhammad and Avgeriou, Paris and Fitzgerald, Brian}
}
@proceedings {1279,
	title = {The Importance of Architectural Knowledge in Integrating Open Source Software},
	year = {2011},
	month = {10/2011},
	pages = {142-158},
	publisher = {Springer},
	abstract = {Open Source Software (OSS) is increasingly used in Component-Based Software Development (CBSD) of large software systems. An important issue in CBSD is selection of suitable components. Various OSS selection methods have been proposed, but most of them do not consider the software architecture aspects of OSS products. The Software Architecture (SA) research community refers to a product{\textquoteright}s architectural information, such as design decisions and underlying rationale, and used architecture patterns, as Architecture Knowledge (AK). In order to investigate the importance of AK of OSS components in integration, we conducted an exploratory empirical study. Based on in-depth interviews with 12 IT professionals, this paper presents insights into the following questions: 1) what AK of OSS is needed? 2) Why is AK of OSS needed? 3) Is AK of OSS generally available? And 4) what is the relative importance of AK? Based on these new insights, we provide a research agenda to further the research field of software architecture in OSS.},
	keywords = {architectural knowledge, component-based development, Open Source Software integration, OSS Integrator, software architecture, Survey},
	author = {Stol, Klaas-Jan and Ali Babar, Muhammad and Avgeriou, Paris}
}
@proceedings {1280,
	title = {Successful Reuse of Software Components: A Report from the Open Source Perspective},
	year = {2011},
	month = {10/2011},
	pages = {159-176},
	publisher = {Springer},
	abstract = {A promising way of software reuse is Component-Based Software Development (CBSD). There is an increasing number of OSS products available that can be freely used in product development. However, OSS communities themselves have not yet taken full advantage of the {\textquotedblleft}reuse mechanism{\textquotedblright}. Many OSS projects duplicate effort and code, even when sharing the same application domain and topic. One successful counter-example is the FFMpeg multimedia project, since several of its components are widely and consistently reused into other OSS projects. This paper documents the history of the libavcodec library of components from the FFMpeg project, which at present is reused in more than 140 OSS projects. Most of the recipients use it as a black-box component, although a number of OSS projects keep a copy of it in their repositories, and modify it as such. In both cases, we argue that libavcodec is a successful example of reusable OSS library of components.},
	keywords = {component-based software development, OSS components, Software reuse},
	author = {Capiluppi, Andrea and Boldyreff, Cornelia and Stol, Klaas-Jan}
}
@conference {583,
	title = {Reporting Empirical Research in Open Source Software: The State of Practice},
	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 = {156 - 169},
	publisher = {Springer},
	organization = {Springer},
	chapter = {15},
	abstract = {Background: The number of reported empirical studies of Open Source Software (OSS) has continuously been increasing. However, there has been no effort to systematically review the state of the practice of reporting empirical studies of OSS with respect to the recommended standards of performing and reporting empirical studies in software engineering. It is important to understand, how to report empirical studies of OSS in order to make them useful for practitioners and researchers.
Research aim: The aim of our research is to gain insights in the state of the practice of reporting empirical studies of OSS in order to identify the gaps to be filled for improving the quality of evidence being provided for OSS.
Method: To that end, we decided to systematically review the empirical studies of OSS. A total of 63 papers reporting empirical studies were selected from the four editions of the Proceedings of the International Conference on Open Source Systems. The data were extracted and synthesised from the selected papers for analysis.
Results and conclusions: We have found that the quality of the reported OSS-related empirical studies needs to be significantly improved. Based on the results of our systematic review and general principles of reporting good empirical research, we present a set of guidelines for reporting OSS-related empirical studies. The suggested guidelines are expected to help the research community to improve the quality of reported studies.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_15},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Reporting\%20Empirical\%20Research.pdf},
	author = {Stol, Klaas-Jan and Ali Babar, Muhammad}
}
