@proceedings {1895,
	title = {How are Developers Treating License Inconsistency Issues? A Case Study on License Inconsistency Evolution in FOSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {69-79},
	publisher = {Springer},
	abstract = {A license inconsistency is the presence of two or more source files that evolved from the same original file containing different licenses. In our previous study, we have shown that license inconsistencies do exist in open source projects and may lead to potential license violation problems. In this study, we try to find out whether the issues of license inconsistencies are properly solved by analyzing two versions of a FOSS distribution{\textemdash}Debian{\textemdash}and investigate the evolution patterns of license inconsistencies. Findings are: license inconsistencies occur mostly because the original copyright owner updated the license while the reusers were still using the old version of the source files with the old license; most license inconsistencies would disappear when the reusers synchronize their project from the upstream, while some would exist permanently if reusers decide not to synchronize anymore. Legally suspicious cases have not been found yet in those Debian distributions.},
	keywords = {Code clone, debian, License inconsistency, licenses, Software license},
	doi = {10.1007/978-3-319-57735-7_8},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_8},
	author = {Y. Wu and Manabe, Yuki and Daniel M. Germ{\'a}n and Inoue, K.}
}
@proceedings {1888,
	title = {Technical Lag in Software Compilations: Measuring How Outdated a Software Deployment Is},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {182 - 192},
	publisher = {Springer International Publishing},
	abstract = {Large software compilations based on free, open source software (FOSS) packages are the basis for many software systems. When they are deployed in production, specific versions of the packages in the compilation are selected for installation. Over time, those versions become outdated with respect to the upstream software from which they are produced, and from the components available in the compilations as well. The fact that deployed components are outdated is not a problem in itself, but there is a price to pay for not being "as much updated as reasonable". This includes bug fixes and new features that could, at least potentially, be interesting for the deployed system. Therefore, a balance has to be maintained between "being up-to-date" and "keeping the good old working versions". This paper proposes a theoretical model (the "technical lag") for measuring how outdated a system is, with the aim of assisting in the decisions about upgrading in production. The paper explores several ways in which technical lag can be implemented, depending on requirements. As an illustration, it presents as well some specific cases in which the evolution of technical lag is computed.},
	isbn = {978-3-319-57735-7},
	issn = {1868-422X},
	doi = {10.1007/978-3-319-57735-7_17},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_17},
	author = {Gonz{\'a}lez-Barahona, J.M. and Sherwood, P. and Robles, G. and Izquierdo, D.},
	editor = {Balaguer, Federico and Di Cosmo, Roberto and Garrido, Alejandra and Kon, Fabio and Gregorio Robles and Zacchiroli, Stefano}
}
@proceedings {1900,
	title = {Understanding When to Adopt a Library: A Case Study on ASF Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {128-138},
	publisher = {Springer},
	abstract = {Software libraries are widely used by both industrial and open source client projects. Ideally, a client user of a library should adopt the latest version that the library project releases. However, sometimes the latest version is not better than a previous version. This is because the latest version may include additional developer effort to test and integrate all changed features. In this study, our main goal is to better understand the relationship between adoption of library versions and its release cycle. Specifically, we conducted an empirical study of release cycles for 23 libraries and how they were adopted by 415 Apache Software Foundation (ASF) client projects. Our findings show that software projects are quicker to update earlier rapid-release libraries compared to library projects with a longer release cycle. Moreover, results suggest that software projects are more likely to adopt the latest version of a rapid-release library compared to libraries with a longer release cycles.},
	keywords = {adoption, apache, apache software foundation, libraries},
	doi = {10.1007/978-3-319-57735-7_13},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_13},
	author = {Ihara, Akinori and Daiki Fujibayashi and Hirohiko Suwa and Raula Gaikovina Kula and Kenichi Matsumoto}
}
@conference {Izquierdo-Cortazar:2017:UMT:3084226.3084247,
	title = {Using Metrics to Track Code Review Performance},
	booktitle = {Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering},
	series = {EASE{\textquoteright}17},
	year = {2017},
	pages = {214{\textendash}223},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {During 2015, some members of the Xen Project Advisory Board became worried about the performance of their code review process. The Xen Project is a free, open source software project developing one of the most popular virtualization platforms in the industry. They use a pre-commit peer review process similar to that in the Linux kernel, based on email messages. They had observed a large increase over time in the number of messages related to code review, and were worried about how this could be a signal of problems with their code review process.

To address these concerns, we designed and conducted, with their continuous feedback, a detailed analysis focused on finding these problems, if any. During the study, we dealt with the methodological problems of Linux-like code review, and with the deeper issue of finding metrics that could uncover the problems they were worried about. For having a benchmark, we run the same analysis on a similar project, which uses very similar code review practices: the Linux Netdev (Netdev) project. As a result, we learned how in fact the Xen Project had some problems, but at the moment of the analysis those were already under control. We found as well how different the Xen and Netdev projects were behaving with respect to code review performance, despite being so similar from many points of view.

In this paper we show the results of both analyses, and propose a comprehensive methodology, fully automated, to study Linux-style code review. We discuss also the problems of getting significant metrics to track improvements or detect problems in this kind of code review.},
	keywords = {code review, data mining, Software development analytics},
	isbn = {978-1-4503-4804-1},
	doi = {10.1145/3084226.3084247},
	url = {http://doi.acm.org/10.1145/3084226.3084247},
	author = {Izquierdo-Cortazar, Daniel and Sekitoleko, Nelson and Jesus M. Gonzalez-Barahona and Kurth, Lars}
}
@proceedings {1819,
	title = {Analyzing the Decision Criteria of Software Developers Based on Prospect Theory},
	year = {2016},
	note = {they sent a survey to developers and used flossmole to harvest the email addresses},
	month = {03/2016},
	abstract = {To enhance the quality of software, many software development support tools and software development methodologies have been proposed. However, not all proposed tools and methodologies are widely used in software development. We assume that the evaluation of tools and methodologies by developers is different from the evaluation by researchers, and that this is one of the reasons why the tools and methodologies are not widely used. We analyzed the decision criteria of software developers as applied to the tools and methodologies, to clarify whether the difference exists or not. In behavioral economics, there are theories which assume people have biases, and they do not always act reasonably. In the experiment, we made a questionnaire based on behavioral economics, and collected answers from open source software developers. The results suggest that developers do not always act to maximize expected profit because of the certainty effect and ambiguity aversion. Therefore, we should reconsider the evaluation criteria of tools such as the f-measure or AUC, which mainly focus on the expected profit. },
	keywords = {flossmole},
	url = {http://se-naist.jp/pman3/pman3.cgi?DOWNLOAD=579},
	attachments = {https://flosshub.org/sites/flosshub.org/files/saner2016-kina.pdf},
	author = {Kanako Kina and Tsunoda, Masateru and Tamada, Haruaki and Hiroshi Igaki}
}
@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}
}
@proceedings {1763,
	title = {A Dataset of High Impact Bugs: Manually-Classified Issue Reports},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The importance of supporting test and maintenance
activities in software development has been increasing, since
recent software systems have become large and complex. Although
in the field of Mining Software Repositories (MSR) there
are many promising approaches to predicting, localizing, and
triaging bugs, most of them do not consider impacts of each
bug on users and developers but rather treat all bugs with equal
weighting, excepting a few studies on high impact bugs including
security, performance, blocking, and so forth. To make MSR
techniques more actionable and effective in practice, we need
deeper understandings of high impact bugs. In this paper we
introduced our dataset of high impact bugs which was created
by manually reviewing four thousand issue reports in four open
source projects (Ambari, Camel, Derby and Wicket).},
	keywords = {ambari, camel, derby, wicket},
	url = {http://oss.sys.wakayama-u.ac.jp/publications/pman3.cgi?DOWNLOAD=141},
	attachments = {https://flosshub.org/sites/flosshub.org/files/5594a518.pdf},
	author = {Ohira, Masao and Yutaro Kashiwa and Yosuke Yamatani and Hayato Yoshiyuki and Yoshiya Maeda and Nachai Limsettho and Keisuke Fujino and Hata, Hideaki and Ihara, Akinori and Kenichi Matsumoto}
}
@proceedings {1727,
	title = {Enabling the Definition and Enforcement of Governance Rules in Open Source Systems},
	volume = {2},
	year = {2015},
	month = {05/2015},
	pages = {505-514},
	publisher = {ACM/IEEE},
	abstract = {Governance rules in software development projects
help to prioritize and manage their development tasks, and
contribute to the long-term sustainability of the project by
clarifying how core and external contributors should collaborate
in order to advance the project during its whole lifespan. Despite
their importance, specially in Open Source Software (OSS)
projects, these rules are usually implicit or scattered in the
project documentation/tools (e.g., tracking-systems or forums),
hampering the correct understanding of the development process.
We propose to enable the explicit definition and enforcement of
governance rules for OSS projects. We believe this brings several
important benefits, including improvements in the transparency
of the process, its traceability and the semi-automation of the
governance itself. Our approach has been implemented on top of
Mylyn, a project-management Eclipse plug-in supporting most
popular tracking-systems.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icse2015-governance-validated.pdf},
	author = {Izquierdo, Javier Luis Canovas and Cabot, Jordi}
}
@inbook {1734,
	title = {Examining Usability Work and Culture in OSS},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {58-67},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Organizational culture has been recognized as an influential factor affecting the successes and failures of usability work in organizations; however, there is a lack of research on organizational culture in open source software (OSS) development. This paper shows that there are different kinds of cultures in OSS development projects and builds propositions on the relationship between culture and usability work in OSS development projects. Partly those are derived from the literature, partly from an exploratory empirical inquiry. We speculate whether there is an ideal culture type for usability work in OSS development or whether usability work should be modified to fit the different cultures of OSS development projects.
},
	keywords = {culture, empirical study, open source software, Usability},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_6},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_6},
	author = {Rajanen, Mikko and Iivari, Netta},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {1789,
	title = {The FLOSS History in Japan: An Ethnographic Approach},
	year = {2015},
	month = {08/2015},
	abstract = {This paper reports an overview of the Internet history project
which especially focuses on Free / Libre / Open-Source Software
(FLOSS) history. The project adopts an ethnographical
approach and it aims to compose a chronicle on the
growth of FLOSS history in Japan. An outcome of the
project is expected to be not only a record but a compass
for younger generations. The project has already started
and conducted several interviews. In this paper, an interim
report of our analysis based on the interviews is presented.},
	url = {http://www.opensym.org/os2015/proceedings-files/p105-iio.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p105-iio.pdf},
	author = {Iio, Jun and Hatta, Masayuki and Ko Kazaana}
}
@conference {1798,
	title = {Integrating Open Source Software Repositories on the Web through Linked Data},
	booktitle = {2015 IEEE International Conference on Information Reuse and Integration (IRI)2015 IEEE International Conference on Information Reuse and Integration},
	year = {2015},
	pages = {114 - 121},
	publisher = {IEEE},
	organization = {IEEE},
	address = {San Francisco, CA, USA},
	abstract = {In this paper, we propose a novel approach to the problem of integrating code forges based on metadata (e.g., programming language, database, intended audience, operating system), similar software projects and software developers. We review the current problems in integrating metadata of different code forges and argue that Semantic Web technologies are suitable for representing and integrating knowledge contained inside these code forges. Further, we show the advantages of interlinking metadata of software projects to other relevant data sources on the Web, which will enable querying more information from the Web. Moreover, we compute the overlapping between code forges based on similar software developers and argue the benefit of interlinking similar software developers and software projects across different code forges through examples.
},
	doi = {10.1109/IRI.2015.27},
	author = {Iqbal, Aftab and Decker, Stefan}
}
@proceedings {1769,
	title = {Investigating Code Review Practices in Defective Files: An Empirical Study of the Qt System},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Software code review is a well-established software
quality practice. Recently, Modern Code Review (MCR) has been
widely adopted in both open source and proprietary projects.
To evaluate the impact that characteristics of MCR practices
have on software quality, this paper comparatively studies MCR
practices in defective and clean source code files. We investigate
defective files along two perspectives: 1) files that will eventually
have defects (i.e., future-defective files) and 2) files that have
historically been defective (i.e., risky files). Through an empirical
study of 11,736 reviews of changes to 24,486 files from the Qt
open source project, we find that both future-defective files and
risky files tend to be reviewed less rigorously than their clean
counterparts. We also find that the concerns addressed during
the code reviews of both defective and clean files tend to enhance
evolvability, i.e., ease future maintenance (like documentation),
rather than focus on functional issues (like incorrect program
logic). Our findings suggest that although functionality concerns
are rarely addressed during code review, the rigor of the
reviewing process that is applied to a source code file throughout
a development cycle shares a link with its defect proneness.},
	keywords = {code review, software quality},
	url = {http://sail.cs.queensu.ca/publications/pubs/msr2015-thongtanunam.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015-thongtanunam.pdf},
	author = {Patanamon Thongtanunam and McIntosh, Shane and Hassan, Ahmed E. and Hajimu Iida}
}
@proceedings {1776,
	title = {A Method to Detect License Inconsistencies in Large-Scale Open Source Projects},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The reuse of free and open source software (FOSS)
components is becoming more and more popular. They usually
contain one or more software licenses describing the requirements
and conditions which should be followed when been reused.
Licenses are usually written in the header of source code files as
program comments. Removing or modifying the license header
by re-distributors will result in the inconsistency of license with
its ancestor, and may potentially cause license infringement. But
to the best of our knowledge, no research has been devoted
to investigate such kind of license infringements nor license
inconsistencies. In this paper, we describe and categorize different
types of license inconsistencies and propose a feasible method to
detect them. Then we apply this method to Debian 7.5 and present
the license inconsistencies found in it. With a manual analysis, we
summarized various reasons behind these license inconsistencies,
some of which imply license infringement and require the attention
from the developers. This analysis also exposes the difficulty
to discover license infringements, highlighting the usefulness of
finding and maintaining source code provenance.},
	url = {http://sel.ist.osaka-u.ac.jp/lab-db/betuzuri/archive/992/992.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/992.pdf},
	author = {Yuhao Wu and Manabe, Yuki and Tetsuya Kanda and Daniel M. German and Inoue, Katsuro}
}
@conference {1797,
	title = {On the Need of Integrating Social Media Channels and Open Source Software Repositories},
	booktitle = {2015 IEEE International Conference on Information Reuse and Integration (IRI)2015 IEEE International Conference on Information Reuse and Integration},
	year = {2015},
	pages = {396 - 402},
	publisher = {IEEE},
	organization = {IEEE},
	address = {San Francisco, CA, USA},
	abstract = {The growing interest in the usage of social media channels have attracted the open source software community to adopt an identity in order to disseminate project-related information to a wider audience. We foresee the need to integrate social media channels and open source software repositories in order to get an integrated view on the software project not only from the software development perspective but also from social perspective. Therefore, in this paper we study the usage of Twitter by software developers through harvesting their project-related activities on Twitter. In particular, we present the most frequently used hashtags by software developers and further investigate if project-related hashtags are the most frequent and commonly used hashtags by software developers. Based on our findings, we argue that relevant information from social media channels should be integrated with the open source software repositories in order to provide a homogeneous view on a software project.
},
	doi = {10.1109/IRI.2015.66},
	author = {Iqbal, Aftab and Decker, Stefan}
}
@inbook {1738,
	title = {A Qualitative Study on the Adoption of Open Source Software in Information Technology Outsourcing Organizations},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {103-113},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {The purpose of this paper is to identify the influence of Outsourcing on Open source software (OSS) and further investigate the factors that impact the adoption of OSS in global Information Technology (IT) outsourcing organizations serviced by Indian IT services providers. This exploratory research adopted positivism research philosophy and qualitative approach. An in-depth interview was conducted with ten participants across IT outsourcing organizations, IT service providers, and OSS service providers. The results show that IT outsourcing was not found to have an impact on OSS adoption. However, eight factors including management support and OSS support availability was identified to influence OSS adoption. IT services providers can utilize this research model to increase their understanding of why some IT outsourcing organizations choose to adopt OSS, while seemingly similar ones facing similar market conditions do not.
},
	keywords = {Diffusion of innovation, Indian IT, IT outsourcing, open source software, OSS adoption, TOE},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_10},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_10},
	author = {Ramanathan, Lakshmanan and Iyer, Sundaresan Krishnan},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1595,
	title = {Analyzing the Relationship between the License of Packages and Their Files in Free and Open Source Software},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {51-60},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {Free and Open Source Software (FOSS) is widely reused today. To reuse FOSS one must accept the conditions imposed by the software license under which the component is made available. This is complicated by the fact that often FOSS packages contain files from many licenses. In this paper we analyze the source code of packages in the Fedora Core Linux distribution with the goal of discovering the relationship between the license of a source package, and the license of the files it contains. For this purpose we create license inclusion graphs. Our results show that more modern reciprocal licenses such as the General Public License v3 tend to include files of less licenses than its previous versions, and that packages under an Apache License tend to contain only files under the same license.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_6},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_6},
	author = {Manabe, Yuki and German, DanielM. and Inoue, Katsuro},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@book {1591,
	title = {Code Review Analytics: WebKit as Case Study},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Mobile Open Source Technologies. 10th IFIP WG 2.13 International Conference on Open Source Systems, OSS 2014, San Jos{\'e}, Costa Rica, May 6-9, 2014. Proceedings},
	volume = {427},
	year = {2014},
	pages = {1 - 10},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {During the last years, most of the large free / open source software projects have included code review as an usual, or even mandatory practice for changes to their code. In many cases it is implemented as a process in which a developer proposing some change needs to ask for a review by another developer before it can enter the code base. Code reviews, therefore, become a critical process for the project, which could cause delays in contributions being accepted, and risk to become a bottleneck if not enough reviewers are available. In this paper we present a methodology designed to analyze the code review process, to determine its main characteristics and parameters, and to detect potential problems with it. We also present how we have applied this methodology to the WebKit project, learning about the main characteristics of how code review works in their case.},
	isbn = {978-3-642-55128-4},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-55128-4_1},
	author = {Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Izquierdo-Cort{\'a}zar, Daniel and Gregorio Robles and Mario Gallegos},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, Anthony I.}
}
@conference {Robles:2014:EDE:2597073.2597107,
	title = {Estimating Development Effort in Free/Open Source Software Projects by Mining Software Repositories: A Case Study of OpenStack},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {222{\textendash}231},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Because of the distributed and collaborative nature of free / open source software (FOSS) projects, the development effort invested in a project is usually unknown, even after the software has been released. However, this information is becoming of major interest, especially ---but not only--- because of the growth in the number of companies for which FOSS has become relevant for their business strategy. In this paper we present a novel approach to estimate effort by considering data from source code management repositories. We apply our model to the OpenStack project, a FOSS project with more than 1,000 authors, in which several tens of companies cooperate. Based on data from its repositories and together with the input from a survey answered by more than 100 developers, we show that the model offers a simple, but sound way of obtaining software development estimations with bounded margins of error.
},
	keywords = {effort estimation, free software, mining software repositories, open source, openstack},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597107},
	url = {http://doi.acm.org/10.1145/2597073.2597107},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles_0.pdf},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Cervig{\'o}n, Carlos and Capiluppi, Andrea and Izquierdo-Cort{\'a}zar, Daniel}
}
@conference {1720,
	title = {Evaluating Software Product Quality: A Systematic Mapping Study},
	booktitle = {2014 Joint Conference of the International Workshop on Software Measurement IWSM-MENSURA},
	year = {2014},
	pages = {141 - 151},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Rotterdam, Netherlands},
	abstract = {Evaluating software product quality (SPQ) is an important task to ensure the quality of software products. In this paper a systematic mapping study was performed to summarize the existing SPQ evaluation (SPQE) approaches in literature and to classify the selected studies according to seven classification criteria: SPQE approaches, research types, empirical types, data sets used in the empirical evaluation of these studies, artifacts, SQ models, and SQ characteristics. Publication channels and trends were also identified. 57 papers were selected. The results show that the main publication sources of the papers identified were journals. Data mining techniques are the most frequently approaches reported in literature. Solution proposals were the main research type identified. The majority of the selected papers were history-based evaluations using existing data, which were mainly obtained from open source software projects and domain specific projects. Source code was the main artifacts used by SPQE approaches. Well-known SQ models were mentioned by half of the selected papers and reliability is the SQ characteristic through which SPQE was mainly achieved. SPQE-related subjects seem to attract more interest from researchers since the past years. },
	doi = {10.1109/IWSM.Mensura.2014.30},
	url = {http://www.scielo.org.mx/pdf/cys/v19n3/v19n3a11.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/v19n3a11.pdf},
	author = {Ouhbi, Sofia and Idri, Ali and Aleman, Jose Luis Fernandez and Toval, Ambrosio}
}
@conference {1704,
	title = {Industry Questions about Open Source Software in Business: Research Directions and Potential Answers},
	booktitle = {2014 6th International Workshop on Empirical Software Engineering in Practice (IWESEP)2014 6th International Workshop on Empirical Software Engineering in Practice},
	year = {2014},
	pages = {55 - 59},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Osaka, Japan},
	abstract = {As open source software (OSS) has become an integral part of today{\textquoteright}s software businesses, many software companies rely on OSS to develop their customer solutions and products. On the other hand, they face various concerns in using OSS, such as technical support, quality, security and licensing issues. This paper focuses on OSS-related FAQ in industry, and tries to answer them or to provide research directions based on lessons learned from recent mining OSS repository researches.
},
	doi = {10.1109/IWESEP.2014.12},
	author = {Ihara, Akinori and Monden, Akito and Matsumoto, Ken-ichi}
}
@article {1817,
	title = {Understanding Contributor to Developer Turnover Patterns in OSS Projects: A Case Study of Apache Projects},
	journal = {ISRN Software Engineering},
	volume = {201411},
	year = {2014},
	month = {2014},
	pages = {1 - 10},
	abstract = {OSS projects are dynamic in nature. Developers
contribute to a project for a certain period of time and later
leave the project or join other projects of high interest. Hence,
the OSS community always welcomes members who can attain
the role of a developer in a project. In this paper, we investigate
contributions made by members who have attained the role of
a developer. In particular, we study the contributions made by
the members in terms of bugs reported, comments on bugs,
source-code patch submissions, and their social relation with
other members of an OSS community. Further, we study the
significance of nondevelopers contribution and investigate if
and to what extent they play a role in the long-term survival
of an OSS project. Moreover, we investigate the ratio of
contributions made by a member before and after attaining
the role of a developer. We have outlined 4 research questions
in this regard and further discuss our findings based on the
research questions by taking into account data from software
repositories of 4 different Apache projects.},
	keywords = {apache},
	doi = {10.1155/2014/535724},
	author = {Iqbal, Aftab}
}
@proceedings {1552,
	title = {Analyzing Social Behavior of Software Developers Across Different Communication Channels},
	year = {2013},
	abstract = {Software developers use different project repositories (i.e., mailing list, bug tracking repositories, discussion forums etc.) to interact with each other or to solve software related problems. The growing interest in the usage of social media channels (i.e., Twitter, Facebook, LinkedIn) have also attracted the open source software community and software developers to adopt an identity in order to disseminate project-related information to a wider audience. Much research has been carried out to analyze the social behavior of software developers in different project repositories but so far no one has tried to study the social communication patterns of developers in other social media channels. We in this paper presents a new dimension to the social aspects of software developers and study if the social communication patterns of software developers is different on project repositories and social media channels (i.e., Twitter).},
	keywords = {communication, developer, social media},
	url = {http://index.ksi.edu/conf/seke/2013/cr/296.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/iqbal_a_et_al_june_2013.pdf},
	author = {Iqbal, Aftab and M Karnstedt and M Hausenblas}
}
@book {1542,
	title = {Authoritative Linked Data Descriptions of Debian Source Packages Using ADMS.SW},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {168 - 181},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {he Debian Package Tracking System is a Web dashboard for Debian contributors and advanced users. This central tool publishes the status of subsequent releases of source packages in the Debian distribution.

It has been improved to generate RDF meta-data documenting the source packages, their releases and links to other packaging artifacts, using the ADMS.SW 1.0 model. This constitutes an authoritative source of machine-readable Debian {\textquotedblleft}facts{\textquotedblright} and proposes a reference URI naming scheme for Linked Data resources about Debian packages.

This should enable the interlinking of these Debian package descriptions with other ADMS.SW or DOAP descriptions of FLOSS projects available on the Semantic Web also using Linked Data principles. This will be particularly interesting for traceability with upstream projects whose releases are packaged in Debian, derivative distributions reusing Debian source packages, or with other FLOSS distributions.},
	keywords = {debian},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_12},
	author = {Olivier Berger and Christian Bac},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1536,
	title = {Community Dynamics in Open Source Software Projects: Aging and Social Reshaping},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {80 - 96},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

An undeniable factor for an open source software (OSS) project success is a vital community built around it. An OSS community not only needs to be established, but also to be persisted. This is not guaranteed considering the voluntary nature of participation in OSS. The dynamic analysis of the OSS community evolution can be used to extract indicators to rate the current stability of a community and to predict its future development. Despite the great amount of studies on mining project communication and development repositories, the evolution of OSS communities is rarely addressed. This paper presents an approach to analyze the OSS community history. We combine adapted demography measures to study community aging and social analysis to investigate the dynamics of community structures. The approach is applied to the communication and development history of three bioinformatics OSS communities over eleven years. First, in all three projects a survival rate pattern is identified. This finding allows us to define the minimal number of newcomers required for the further positive community growth. Second, dynamic social analysis shows that the node betweenness in combination with the network diameter can be used as an indicator for significant changes in the community core and the quality of community recovery after these modifications.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_6},
	author = {Hannemann, Anna and Klamma, Ralf},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1546,
	title = {A Dual Model of Open Source License Growth},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	note = {uses ohloh snapshot, march 2008},
	pages = {245 - 256},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Every open source project needs to decide on an open source license. This decision is of high economic relevance: Just which license is the best one to help the project grow and attract a community? The most common question is: Should the project choose a restrictive (reciprocal) license or a more permissive one? As an important step towards answering this question, this paper analyses actual license choice and correlated project growth from ten years of open source projects. It provides closed analytical models and finds that around 2001 a reversal in license choice occurred from restrictive towards permissive licenses.
},
	keywords = {ohloh},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/oss2013.hofmann.pdf},
	author = {Hofmann, Gottfried and Dirk Riehle and Carsten Kolassa and Mauerer, Wolfgang},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1544,
	title = {Effect on Business Growth by Utilization and Contribution of Open Source Software in Japanese IT Companies},
	volume = {404},
	year = {2013},
	pages = {222 - 231},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

The expanded use of Open Source Software (OSS), and the expansion of the market caused by this adoption has led to a corresponding increase in the number of businesses acting as stakeholders in the field. Some of these are pure users of OSS technology but a great number are developers of such technology, and can be understood to have a substantial investment in this paradigm. It is reasonable to assume that such businesses are rational actors, and that their investment or contribution to the field implies a positive economic benefit either currently obtained or assumed as a return in the future. This paper analyzes how OSS affects Japanese IT companies{\textquoteright} business growth both through simple use and by deeper engagement as a stakeholder in OSS community. This is the first time that such a link between the utilization of OSS and economic growth has been explored in the context of Japan, and it can hopefully lay a foundation for further study regarding the real economic value of this approach to software.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_16},
	author = {Noda, Tetsuo and Tansho, Terutaka and Coughlan, Shane},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1535,
	title = {The Emergence of Quality Assurance Practices in Free/Libre Open Source Software: A Case Study},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {271 - 276},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

As the user base of Free/Libre Open Source Software (FLOSS) diversifies, the need for higher quality is becoming more evident. This implies a more complex development model that includes various steps which were previously associated exclusively with proprietary development such as a formal quality assurance step (QA). However, little research has been done on how implementing formal quality assurance impacts the structure of FLOSS communities. This study aims to start filling this gap by analyzing interactions within such a community. Plone is just one among many FLOSS projects that acknowledged the importance of verification by implementing a quality assurance step.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_21},
	author = {Barham, Adina},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1537,
	title = {Exploring Collaboration Networks in Open-Source Projects},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {97 - 108},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Analysis of developer collaboration networks presents an opportunity for understanding and thus improving the software development process. Discovery of these networks, however, presents a challenge since the collaboration relationships are initially not known. In this work we apply an approach for discovering collaboration networks of open source developers from Version Control Systems (VCS). It computes similarities among developers based on common file changes, constructs the network of collaborating developers and applies filtering techniques to improve the readability of the visualized network. We use the approach in case studies of three different projects from open source (phpMyAdmin, Eclipse Data Tools Platform and Gnu Compiler Collection) to learn their organizational structure and patterns. Our results indicate that with little effort the approach is capable of revealing aspects of these projects that were previously not known or would require a lot of effort to discover manually via other means, such as reading project documentation and forums.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_7},
	author = {Jermakovics, Andrejs and Sillitti, Alberto and Succi, Giancarlo},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1532,
	title = {How Healthy Is My Project? Open Source Project Attributes as Indicators of Success},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	note = {"The dataset used has thus been obtained through a third source which has made
the data publicly available [18]. FlossMole.org contains data collected for the period
2006 to December 2009 from which a dataset was compiled of 125,700 projects. "},
	pages = {30 - 44},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {Determining what factors can influence the successful outcome of a software project has been labeled by many scholars and software engineers as a difficult problem. In this paper we use machine learning to create a model that can determine the stage a software project has obtained with some accuracy. Our model uses 8 Open Source project metrics to determine the stage a project is in. We validate our model using two performance measures; the exact success rate of classifying an Open Source Software project and the success rate over an interval of one stage of its actual performance using different scales of our dependent variable. In all cases we obtain an accuracy of above 70\% with one away classification (a classification which is away by one) and about 40\% accuracy with an exact classification. We also determine the factors (according to one classifier) that uses only eight variables among all the variables available in SourceForge, that determine the health of an OSS project.
},
	keywords = {flossmole, sourceforge},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_3},
	url = {http://link.springer.com/chapter/10.1007/978-3-642-38928-3_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OSSHealth_1.0.pdf},
	author = {Piggot, James and Amrit, Chintan},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1533,
	title = {Identifying Success Factors for the Mozilla Project},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {45 - 60},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

The publication of the Netscape source code under free software license and the launch of the Mozilla project constitute a pioneering initiative in the field of free and open source software. However, five years after the publication came years of decline. The market shares rose again after 2004 with the lighter Firefox browser. We propose a case study covering the period from 1998 to 2012. We identify the factors that explain the evolution of the Mozilla project. Our study deepens different success factors identified in the literature. It is based on authors{\textquoteright} experience as well as the abundant literature dedicated to the Netscape company and the Mozilla project. It particularly highlights the importance of the source code complexity, its modularity, the responsibility assignment and the existence of an organisational sponsorship.},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_4},
	author = {Viseur, Robert},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1529,
	title = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification Technological Innovation and Resource Bricolage in Firms: The Role of Open Source Software},
	volume = {404},
	year = {2013},
	pages = {1 - 17},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {Technological resources have been an important source of innovation in companies. They play a key role in the development of new products and services. However, the upfront investment in technical resources to enable the development of these new products and services can be quite high. Therefore, managers ask for well elaborated business cases before making investments. These business cases rely on market research to back up their assumptions rather than in-market testing. We argue that the advent of open source software (OSS) creates an opportunity space for companies to build low-cost prototypes and test their ideas in the market. Little is known about how OSS plays a role in allowing these firms to enhance product development. Using qualitative case studies, the paper sheds light on how OSS acts as a bricolage mechanism for technological innovation in the ICT services industry.},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_1},
	url = {http://link.springer.com/chapter/10.1007/978-3-642-38928-3_1},
	author = {Mahajan, Aarti and Clarysse, Bart},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1530,
	title = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification Empirical Study of the Relation between Open Source Software Use and Productivity of Japan{\textquoteright}s Information Service Industries},
	volume = {404},
	year = {2013},
	pages = {18 - 29},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

This paper analyzes the relation between OSS (Open Source Software) use and the performance of Japanese information service industry. We first estimate the market value of OSS, an issue which only a few studies have specifically addressed. The results are then used to analyze the economic effect of OSS. Although our study has some methodological limitations regarding the calculation of the market value of OSS, we demonstrate that the economic effect of OSS is generally positive.},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_2},
	author = {Noda, Tetsuo and Tanihana, Keisuke},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@article {1553,
	title = {Interlinking Developer Identities within and across Open Source Projects: The Linked Data Approach},
	journal = {ISRN Software Engineering},
	volume = {201330692164},
	year = {2013},
	month = {2013},
	pages = {1 - 12},
	abstract = {Software developers use various software repositories in order to interact with each other or to solve related problems. These repositories provide a rich source of information for a wide range of tasks. However, one issue to overcome in order to make this information useful is the identification and interlinking of multiple identities of developers. In this paper, we propose a Linked Data-based methodology to interlink and integrate multiple identities of a developer found in different software repositories of a project as well as across repositories of multiple projects. Providing such interlinking will enable us to keep track of a developer{\textquoteright}s activity not only within a single project but also across multiple projects. The methodology will be presented in general and applied to 5 Apache projects as a case study. Further, we show that the few methods suggested so far are not always appropriate to overcome the developer identification problem.},
	keywords = {developer, identity, linked data},
	doi = {10.1155/2013/58473110.1007/s10664-009-9110-310.1109/TSE.2005.7010.1007/978-0-387-72486-7_4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/584731.pdf},
	author = {Iqbal, Aftab and Hausenblas, Michael}
}
@book {1531,
	title = {Is It All Lost? A Study of Inactive Open Source Projects},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification },
	volume = {404},
	year = {2013},
	pages = {61 - 79},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {
Open Source Software (OSS) proponents suggest that when developers lose interest in their project, their last duty is to {\textquotedblleft}hand it off to a competent successor.{\textquotedblright} However, the mechanisms of such a hand-off are not clear, or widely known among OSS developers. As a result, many OSS projects, after a certain long period of evolution, stop evolving, in fact becoming {\textquotedblleft}inactive{\textquotedblright} or {\textquotedblleft}abandoned{\textquotedblright} projects. This paper presents an analysis of the population of projects contained within one of the largest OSS repositories available (SourceForge.net), in order to describe how projects abandoned by their developers can be identified, and to discuss the attributes and characteristics of these inactive projects. In particular, the paper attempts to differentiate projects that experienced maintainability issues from those that are inactive for other reasons, in order to be able to correlate common characteristics to the {\textquotedblleft}failure{\textquotedblright} of these projects.
},
	keywords = {sourceforge},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_5},
	url = {http://staff.lero.ie/stol/files/2013/03/2013-Is-It-All-Lost-A-Study-of-Inactive-Open-Source-Projects.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2013-Is-It-All-Lost-A-Study-of-Inactive-Open-Source-Projects.pdf},
	author = {Khondu, Jymit and Capiluppi, Andrea and Stol, Klaas},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1545,
	title = {Misconceptions and Barriers to Adoption of FOSS in the U.S. Energy Industry},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {232 - 244},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

In this exploratory study, we map the use of free and open source software (FOSS) in the United States energy sector, especially as it relates to cyber security. Through two surveys and a set of semi-structured interviews{\textemdash}targeting both developers and policy makers{\textemdash}we identified key stakeholders, organizations, and FOSS projects, be they rooted in industry, academia, or public policy space that influence software and security practices in the energy sector. We explored FOSS tools, common attitudes and concerns, and challenges with regard to FOSS adoption. More than a dozen themes were identified from interviews and surveys. Of these, drivers for adoption and risks associated with FOSS were the most prevalent. More specifically, the misperceptions of FOSS, the new security challenges presented by the smart grid, and the extensive influence of vendors in this space play the largest roles in FOSS adoption in the energy sector.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_17},
	author = {Kuechler, Victor and Jensen, Carlos and Bryant, Deborah},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1539,
	title = {Modeling Practices in Open Source Software},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {127 - 139},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

It is widely accepted that modeling in software engineering increases productivity and results in better code quality. Yet, modeling adoption remains low. The open source community, in particular, remains almost entirely code centric. In this paper, we explore the reasons behind such limited adoption of modeling practices among open source developers. We highlight characteristics of modeling tools that would encourage their adoption. We propose Umple as a solution where both modeling and coding elements are treated uniformly. In this approach, models can be manipulated textually and code can be edited visually. We also report on the Umple compiler itself as a case study of an open source project where contributors, using the above approach, have and continue to routinely commit code and model over a number of years.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Modeling-Practices-in-Open-Source-Software.pdf},
	author = {Badreddin, Omar and Lethbridge, Timothy and Elassar, Maged},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1543,
	title = {An Open Source Monitoring Framework for Enterprise SOA},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {182 - 193},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Web services monitoring is currently emerging as an effective way to trace faults in services at runtime. The lack of testing information provided by web services specifications was an indication that other methods need to be used to assess the quality of web services. This is mainly due to the fact that it is difficult to simulate the client infrastructure during testing of web services. Monitoring consists of inspecting services at runtime and taking adequate actions when unacceptable events occur. Monitoring could be performed by different stakeholders and could target different properties of services. Predominantly, monitoring is performed by service providers to manage their internal resources and balance their requests load. In our effort to improve the monitoring infrastructures, we propose a monitoring framework in which all the participants (services providers, services requestors) can contribute to monitoring and at the same time have direct access to the monitoring data. This paper describes a monitoring framework developed as part of NEXOF-RA project. The framework offers a set of capabilities for a collaborative monitoring of web services. The paper presents motivations, system design, implementation and usage of the framework.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_13},
	author = {El Ioini, Nabil and Garibbo, Alessandro and Sillitti, Alberto and Succi, Giancarlo},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1541,
	title = {A Preliminary Analysis of Localization in Free Software: How Translations Are Performed},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {153 - 167},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Software is more than just source code. There is a myriad of elements that compose a software project, among others documentation, translations, multimedia, artwork, marketing. In this paper, we focus on the translation efforts that free, libre, open source software (FLOSS) projects undergo to provide their software in multiple languages. We have therefore analyzed a large amount of projects for their support and procedures regarding translations, if they exist. Our results show that many, but not all, projects offer some type of support and specify some ways to those wanting to contribute. Usually, projects from a more traditional libre software domain are more prone to ease such tasks. However, there is no general way to contribute, as formats and procedures are often project-specific. We have identified as well a high number of translation-supporting tools, with many projects having their own one. All in all, information about how to contribute is the main factor for having a very internationalized application. Projects accepting and giving credit to contributing translators have high levels of internationalization, even if the process is rudimentary.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_11},
	author = {Reina, Laura Arjona and Gregorio Robles and Jesus M. Gonzalez-Barahona},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1540,
	title = {The Role of Microblogging in OSS Knowledge Management},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {140 - 152},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Given that microblogging has been shown to play a valuable role in knowledge management within companies, it is useful to understand how it is being used in relation to OSS. This project studies tweets related to 12 open source projects and keywords, ranging from web content management systems (CMSes) to general office applications. It found considerable differences in the content and exchange of tweets, especially between specialist products such as CMSes and office suites such as OpenOffice. Tweets concerning the more specialist projects tended to provide information rather than updates on the user{\textquoteright}s current status. We found a high proportion of event-driven traffic for some CMS projects, and a lower proportion for the office products and groups of projects.
},
	keywords = {twitter},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_10},
	author = {Lewis, Jonathan},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@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}
}
@book {1534,
	title = {Towards a Reference Model on How to Utilise Open Standards in Open Source Projects: Experiences Based on Drupal},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {257 - 263},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

It is known that standards implemented in Open Source software (OSS) can promote a competitive market, reduce the risk for lock-in and improve interoperability, whilst there is limited knowledge concerning the relationship between standards and their implementations in OSS. In this paper we report from an ongoing case study conducted in the context of the ORIOS (Open Source software Reference Implementations of Open Standards) project in which influences between OSS communities and software standard communities are investigated. The study focuses on the Drupal project and three of its implemented standards (RDFa, CMIS, and OpenID).
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_19},
	author = {Andersson, Stefan and Feist, Jonas and Gustavsson, Tomas and Strindberg, Henrik and Gamalielsson, Jonas and Lundell, Bj{\"o}rn and Grahn, Alexander},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@article {1810,
	title = {Understanding How Companies Interact with Free Software Communities},
	journal = {IEEE Software},
	volume = {30},
	year = {2013},
	month = {9/2013},
	pages = {38 - 45},
	abstract = {When free, open source software development communities work with companies that use their output, it{\textquoteright}s especially important for both parties to understand how this collaboration is performing. The use of data analytics techniques on software development repositories can improve factual knowledge about performance metrics.
},
	issn = {0740-7459},
	doi = {10.1109/MS.2013.95},
	author = {Jesus M. Gonzalez-Barahona and Izquierdo-Cortazar, Daniel and Maffulli, Stefano and Gregorio Robles}
}
@article {1554,
	title = {Using software analytics to understand how companies interact in free software communities},
	journal = {IEEE Software},
	year = {2013},
	month = {2013},
	pages = {1 - 1},
	abstract = {

Free, open source software development communities may become large and complex. They may also be a focus of interest for competing companies relying on their outcomes, with their employees joining the development and maintenance effort. In those cases it is specially important for both companies and communities to understand how this collaboration is working, and how it matches their policies and expectations. In this paper we show two cases (OpenStack and WebKit) which we have studied using analytics techniques on the data obtained from their software development repositories. From them, we conclude that analytics on this data can improve the factual knowledge about how development communities are performing in aspects which are of interest to companies, and fundamental to ensure transparency and fairness.
},
	keywords = {openstack, webkit},
	issn = {0740-7459},
	doi = {10.1109/MS.2013.95},
	author = {Gonzalez-Barahona, Jesus and Izquierdo, Daniel and Maffulli, Stefano and Gregorio Robles}
}
@proceedings {1498,
	title = {Who Does What during a Code Review? Datasets of OSS Peer Review Repositories },
	year = {2013},
	month = {05/2013},
	abstract = {We present four datasets that are focused on the general roles of OSS peer review members. With data mined from both an integrated peer review system and code source repositories, our rich datasets comprise of peer review data that was automatically recorded. Using the Android project as a case study, we describe our extraction methodology, the datasets and their application used for three separate studies. Our datasets are available online at http://sdlab.naist.jp/reviewmining/},
	keywords = {android, case study, code review, data set, peer review, roles, source code},
	author = {Kazuki Hamasaki and Raula Gaikovina Kula and Norihiro Yoshida and A. E. Camargo Cruz and Kenji Fujiwara and Hajimu Iida}
}
@proceedings {1475,
	title = {Discussion on the Problems to be Solved toward the Migration to OSS Productivity Software in the Business Enterprises},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {377-382},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {In recent years, there is a tendency to migrate from proprietary productivity software to open-source productivity software, especially in government offices and municipal offices. ODPG (OpenOffice.org \& OpenDocument Format Promotion Group, Japan) is an organization founded in order to promote the migration to the OSS productivity software in private enterprises as well. In the case evaluation work group of ODPG, business solutions about use of OpenOffice.org have been discussed many times, for the purpose of supporting the migration to OpenOffice.org, by collecting and feeding back the information of case studies useful for the member companies. This paper reports several subjects and solutions, such as promotion strategy for OpenOffice.org to be widely used, the problem in file exchange with the other stakeholders, preparation of use environment, and security issues, which were discussed in the work group.},
	author = {Iio, Jun and Ogawa, Tomotaka}
}
@proceedings {1458,
	title = {Do More Experienced Developers Introduce Fewer Bugs?},
	volume = {378},
	year = {2012},
	note = {"Some Mozilla Foundation projects have been the selected case of study for this paper. The analysis is based on the Mercurial repository which offers a list of repositories that can be easily cloned. As a summary, 19 projects were analyzed, with more than 100,000 commits, more than 2,500 authors and around 4 years of history up to June 2011."},
	month = {09/2012},
	pages = {268-273},
	publisher = {IFIP AICT,  Springer},
	abstract = {Developer experience is a common matter of study in the software maintenance and evolution research literature. However it is still not well understood if less experienced developers are more prone to introduce errors in the source code than their more experienced colleagues. This paper aims to study the relationships between experience and the bug introduction ratio using the Mozilla community as case of study.
As results, statistical differences among developers with different levels of experience has not been observed, when the expected result would have been the opposite1.},
	keywords = {mercurial, mozilla, scm, source code analysis},
	author = {Izquierdo-Cort{\'a}zar, Daniel and Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M.}
}
@conference {1640,
	title = {Integrating developer-related information across open source repositories},
	booktitle = {2012 IEEE 13th International Conference on Information Reuse \& Integration (IRI)2012 IEEE 13th International Conference on Information Reuse \& Integration (IRI)},
	year = {2012},
	pages = {69 - 76},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Las Vegas, NV, USA},
	abstract = {Software developers use various software repositories in order to interact with each other or to solve software related problems. They are required to adopt an identity for each of the software repositories they wanted to use. Quite often developers are also found on different code forges developing open source projects. It is worth mentioning that the information relevant to the developers are distributed on the Web among different data sources each requires an ID and an authentication mechanism. In this paper, we propose to interlink the identities of a developer across different data sources on the Web. Further, we show the benefit of integrating developer-related information from different data sources using some real-world scenarios.},
	isbn = {978-1-4673-2283-6},
	doi = {10.1109/IRI.2012.6302993},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Iqbal_A_et_al_Aug_2012.pdf},
	author = {Iqbal, Aftab and Hausenblas, Michael}
}
@article {1589,
	title = {Integrating FLOSS repositories on the Web},
	year = {2012},
	note = {"To provide the researchers easy access to the project{\textquoteright}s data, two research projects were initiated (with slightly different objective)
by the FLOSS research community which are FLOSSmole and FLOSSMetrics , also known as {\textquotedblleft}repository of repositories (RoR){\textquotedblright}. These RoRs were created to consolidate metadata and analysis of projects from a variety of code forges into a centralized place for use by the researchers in academia and industry.

"In this paper, we take into consideration only project{\textquoteright}s metadata from the code forges which are
made available to download by the FLOSSmole community. Further, we only study Googlecode
and Sourceforge data for this paper, although our methods extend to other code forges as well.

Names are not available for the developers in the database dump of
Googlecode provided by FLOSSmole, so we consider matching only developer ID(s) in the case of
Googlecode."},
	month = {2012},
	abstract = {This paper provides a novel approach to the problem of integrating data from multiple code forges of FLOSS. We review the current problems in integrating the data from multiple forges and argue that Semantic Web technologies are suitable for representing knowledge contained in code forges. Further, we show the advantage of linking the metadata of projects to other data sources on the Web which will enable querying extra information from the Web. The paper briefly describes how the modeling is achieved and what benefits can be obtained by enabling linking to other relevant data sources already available on the Web.},
	keywords = {flossmole, google code, sourceforge},
	url = {https://www.researchgate.net/publication/259757473_Integrating_FLOSS_repositories_on_the_Web},
	attachments = {https://flosshub.org/sites/flosshub.org/files/DERI-TR-AFTAB-2012-12-10_0.pdf},
	author = {Iqbal, Aftab and Cyganiak, Richard and Hausenblas, Michael}
}
@conference {1813,
	title = {Modification and developer metrics at the function level: Metrics for the study of the evolution of a software project},
	booktitle = {2012 3rd International Workshop on Emerging Trends in Software Metrics (WETSoM)},
	year = {2012},
	pages = {49 - 55},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Zurich, Switzerland},
	abstract = {Software evolution, and particularly its growth, has been mainly studied at the file (also sometimes referred as module) level. In this paper we propose to move from the physical towards a level that includes semantic information by using functions or methods for measuring the evolution of a software system. We point out that use of functions-based metrics has many advantages over the use of files or lines of code. We demonstrate our approach with an empirical study of two Free/Open Source projects: a community-driven project, Apache, and a company-led project, Novell Evolution. We discovered that most functions never change; when they do their number of modifications is correlated with their size, and that very few authors who modify each; finally we show that the departure of a developer from a software project slows the evolution of the functions that she authored.
},
	isbn = {978-1-4673-1763-4},
	doi = {10.1109/WETSoM.2012.6226993},
	author = {Gregorio Robles and Herraiz, Israel and Daniel M. German and Izquierdo-Cortazar, Daniel}
}
@article {1324,
	title = {Are Developers Fixing Their Own Bugs?},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	note = {"The analysis is focused at the level of lines of code and it uses the information stored in the source code management system"},
	pages = {23 - 42},
	abstract = {The process of fixing software bugs plays a key role in the maintenance activities of a software project. Ideally, code ownership and responsibility should be enforced among developers working on the same artifacts, so that those introducing buggy code could also contribute to its fix. However, especially in FLOSS projects, this mechanism is not clearly understood: in particular, it is not known whether those contributors fixing a bug are the same introducing and seeding it in the first place. This paper analyzes the comm-central FLOSS project, which hosts part of the Thunderbird, SeaMonkey, Lightning extensions and Sunbird projects from the Mozilla community. The analysis is focused at the level of lines of code and it uses the information stored in the source code management system. The results of this study show that in 80\% of the cases, the bug-fixing activity involves source code modified by at most two developers. It also emerges that the developers fixing the bug are only responsible for 3.5\% of the previous modifications to the lines affected; this implies that the other developers making changes to those lines could have made that fix. In most of the cases the bug fixing process in comm-central is not carried out by the same developers than those who seeded the buggy code.},
	keywords = {bug fixing, developers, loc, scm},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011040102},
	author = {Izquierdo-Cortazar, Daniel and Capiluppi, Andrea and Jesus M. Gonzalez-Barahona}
}
@article {1418,
	title = {Effort estimation of FLOSS projects: a study of the Linux kernel},
	journal = {Empirical Software Engineering},
	year = {2011},
	pages = {1-29},
	abstract = {Empirical research on Free/Libre/Open Source Software (FLOSS) has shown that developers tend to cluster around two main roles: {\textquotedblleft}core{\textquotedblright} contributors differ from {\textquotedblleft}peripheral{\textquotedblright} developers in terms of a larger number of responsibilities and a higher productivity pattern. A further, cross-cutting characterization of developers could be achieved by associating developers with {\textquotedblleft}time slots{\textquotedblright}, and different patterns of activity and effort could be associated to such slots. Such analysis, if replicated, could be used not only to compare different FLOSS communities, and to evaluate their stability and maturity, but also to determine within projects, how the effort is distributed in a given period, and to estimate future needs with respect to key points in the software life-cycle (e.g., major releases). This study analyses the activity patterns within the Linux kernel project, at first focusing on the overall distribution of effort and activity within weeks and days; then, dividing each day into three 8-hour time slots, and focusing on effort and activity around major releases. Such analyses have the objective of evaluating effort, productivity and types of activity globally and around major releases. They enable a comparison of these releases and patterns of effort and activities with traditional software products and processes, and in turn, the identification of company-driven projects (i.e., working mainly during office hours) among FLOSS endeavors. The results of this research show that, overall, the effort within the Linux kernel community is constant (albeit at different levels) throughout the week, signalling the need of updated estimation models, different from those used in traditional 9am{\textendash}5pm, Monday to Friday commercial companies. It also becomes evident that the activity before a release is vastly different from after a release, and that the changes show an increase in code complexity in specific time slots (notably in the late night hours), which will later require additional maintenance efforts.},
	keywords = {complexity, effort estimation, Effort models, mining software repositories, open source software},
	issn = {1573-7616},
	doi = {10.1007/s10664-011-9191-7},
	url = {http://www.springerlink.com/content/612r616k8t52m867/fulltext.html},
	author = {Capiluppi, Andrea and Izquierdo-Cort{\'a}zar, Daniel}
}
@proceedings {1276,
	title = {A Review of Tool Support for User-Related Communication in FLOSS Development},
	year = {2011},
	note = {"We have carried out a literature review addressing communication in FLOSS projects, and contrasted the findings with Human-Computer Interaction (HCI) literature on user-developer communication."},
	month = {10/2011},
	pages = {90-105},
	abstract = {Free/Libre/Open Source Software (FLOSS) projects rely on Internet tools for communication and in coordinating their work. Communication between developers is well supported in FLOSS projects, but user-developer communication has proven out to be challenging. This paper examines the following questions: {\textquotedblright}What kinds of means for communication exist in FLOSS projects for user-developer communication? What kinds of means should there be?{\textquotedblright} We have carried out a literature review addressing communication in FLOSS projects, and contrasted the findings with Human-Computer Interaction (HCI) literature on user-developer communication. HCI literature indicates that user-developer communication is needed during requirements construction, design and evaluation tasks, and HCI specialists are needed for orchestrating the communication and the user related tasks. Communication during the evaluation task is somewhat supported in FLOSS projects, but design and requirements construction are badly in need for support, even though ideas have already been presented. In addition, HCI specialists are in need of different kinds of communication support in FLOSS projects.},
	keywords = {Free/Libre/Open Source Software, Human-Computer Interaction, literature review, Tool Support, User-Developer Communication},
	author = {Rantalinen, Aapo and Hedberg, Henrik and Iivari, Netta}
}
@conference {959,
	title = {Finding file clones in FreeBSD Ports Collection},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {102 - 105},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {In Open Source System (OSS) development, software components are often imported and reused; for this reason we might expect that files are copied in multiple projects (file clones). In this paper, we propose a file clone detection tool called FCFinder and show the analysis performed with it on the FreeBSD Ports Collection, a large OSS project collection. We found many file clones among similar or related projects, which are systematically introduced from base projects.},
	keywords = {clone, freebsd, msr challenge, source code},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463293},
	attachments = {https://flosshub.org/sites/flosshub.org/files/102FreeBSDClones.pdf},
	author = {Sasaki, Yusuke and Yamamoto, Tetsuo and Hayase, Yasuhiro and Inoue, Katsuro}
}
@article {1219,
	title = {Repositories with Public Data about Software Development},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	month = {04/2010},
	pages = {1 - 13},
	abstract = {Empirical research on software development based on data obtained from project repositories and code forges is increasingly gaining attention in the software engineering research community. The studies in this area typically start by retrieving or monitoring some subset of data found in the repository or forge, and this data is later analyzed to find interesting patterns. However, retrieving information from these locations can be a challenging task. Meta-repositories providing public information about software development are useful tools that can simplify and streamline the research process. Public data repositories that collect and clean the data from other project repositories or code forges can help ensure that research studies are based on good quality data. This paper provides some insight as to how these meta-repositories (sometimes called a {\textquotedblleft}repository of repositories{\textquotedblright}, RoR) of data about open source projects should be used to help researchers. This paper describes in detail two of the most widely used collections of data about software development: FLOSSmole and FLOSSMetrics.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010040101},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ijossp2010.pdf},
	author = {Jesus M. Gonzalez-Barahona and Izquierdo-Cortazar, Daniel and Squire, Megan}
}
@conference {967,
	title = {Should I contribute to this discussion?},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {181 - 190},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town},
	abstract = {Development mailing lists play a central role in facilitating communication in open source projects. Since these lists frequently host design and project discussions, knowledgeable contribution to these discussion threads is essential to avoid mis-communication that might slow-down the progress of a project. However, given the sheer volume of emails on these lists, it is easy to miss important discussions. To find out how developers are able to deal with mailing list discussions, we study the main factors that encourage developers to contribute to the development mailing lists. We develop personalized models to automatically identify discussion threads that a developer would contribute to based on his previous contribution behavior. Case studies on development mailing lists of three open source projects (Apache, PostgreSQL and Python) show that the average accuracy of our models is 89-85\% and that the models vary significantly between different developers.},
	keywords = {apache, contributions, developers, email, email archives, mailing lists, postgresql, python},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463345},
	attachments = {https://flosshub.org/sites/flosshub.org/files/181ibrahim-msr2010.pdf},
	author = {Ibrahim, Walid M and Bettenburg, Nicolas and Shihab, Emad and Adams, Bram and Hassan, Ahmed E.}
}
@conference {599,
	title = {4th International Workshop on Public Data about Software Development},
	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 = {351 - 352},
	publisher = {Springer},
	organization = {Springer},
	chapter = {31},
	abstract = {Libre (free, open source) projects offer publicly available data sources. The research community is starting to produce, use and exchange large data sets of information. These data sets have to be retrieved, purged, described, and can be published for public consumption by other groups. Their availability allows for the decoupling of research activities, the reproducibility of research results, and even the collaboration (and competition) in the analysis of data. This activity is frequently presented at workshops and conferences, but since the focus of these conferences is not specific to the use of public data, discussions of techniques and experiences are not as deep and fruitful as they could be. This workshop is once again (for the fourth year in a row) such a place. We will host discussions specifically about these sorts of public data sets about software development, how they are retrieved, how they can be analyzed and mined, how they can be exchanged and extended.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/4the\%20International\%20Workshop\%20on\%20Public\%20Data.pdf},
	author = {Gonz{\'a}lez-Barahona, Jes{\'u}s and Squire, Megan and Izquierdo-Cort{\'a}zar, Daniel}
}
@conference {1809,
	title = {On the Analysis of Contributions from Privileged Users in Virtual Open Communities},
	booktitle = {2009 42nd Hawaii International Conference on System Sciences},
	year = {2009},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, Hawaii, USA},
	abstract = {Collaborative projects built around virtual communities on the Internet have gained momentum over the last decade. Nevertheless, their rapid growth rate rises some questions:which is the most effective approach to manage and organize their content creation process? Can these communities scale, controlling their projects as their size continues to grow over time? To answer these questions, we undertake a quantitative analysis of privileged users in FLOSS development projects and in Wikipedia. From our results, we conclude that the inequality level of user contributions in both types of initiatives is remarkably distinct, even though both communities present almost identical patterns regard-ing the number of distinct contributors per file (in FLOSS  projects) or per article (in Wikipedia). As a result, totally open projects like Wikipedia can effectively deal with faster growing rates, while FLOSS projects may be affected by bottlenecks on committers who play critical roles.},
	isbn = {978-0-7695-3450-3},
	doi = {10.1109/HICSS.2009.328},
	author = {Ortega, Felipe and Izquierdo-Cort{\'a}zar, Daniel and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Gregorio Robles}
}
@conference {606,
	title = {Assessing FLOSS Communities: An Experience Report from the QualOSS Project},
	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 = {364 - 364},
	publisher = {Springer},
	organization = {Springer},
	chapter = {38},
	abstract = {This paper presents work done in the QualOSS (Quality of Open Source Software) research project,which aims at building a methodology and tools to help in the assessment of the quality of FLOSS (free, libre, open source software) endeavors. In particular, we introduce the research done to evaluate the FLOSS endeavor communities. Following the Goal-Question-Metric paradigm, QUALOSS describes goals, the associated questions and then metrics that allow to answer the questions.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_38},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Assessing\%20FLOSS\%20Communities.pdf},
	author = {Izquierdo-Cortazar, Daniel and Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s and Deprez, Jean-Christophe}
}
@article {1346,
	title = {Discourses on User Participation},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {44 - 59},
	abstract = {Users should participate in information technology (IT) artifact development, but it has proven to be challenging. This applies also in the open source software (OSS) development. This chapter critically examines discursive construction of user participation in academic literatures and in practice, in IT artifact development. First three academic discourses constructing user participation are discussed. Then the discursive construction of user participation is explored in OSS development literature. Afterwards, results from several empirical, interpretive case studies are outlined. Some of them have been carried out in the IT artifact product development organizations, others in the OSS development context. Clear similarities can be identified in the discourses constructing user participation in these divergent IT artifact development contexts. The academic discourses on user participation clearly also legitimate certain ways of constructing user participation in practice. The OSS development literature bears resemblance mainly with the Human Computer Interaction (HCI) discourse on user participation. Therefore, it is argued that especially the HCI community should carefully reflect on what kinds of discourses on user participation it advocates and deems as legitimate.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009070104},
	author = {Iivari, Netta}
}
@conference {590,
	title = {Integrating HCI Specialists into Open Source Software Development Projects},
	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 = {251 - 263},
	publisher = {Springer},
	organization = {Springer},
	chapter = {22},
	abstract = {Typical open source software (OSS) development projects are organized around technically talented developers, whose communication is based on technical aspects and source code. Decision-making power is gained through proven competence and activity in the project, and non-technical end-user opinions are too many times neglected. In addition, also human-computer interaction (HCI) specialists have encountered difficulties in trying to participate in OSS projects, because there seems to be no clear authority and responsibility for them. In this paper, based on HCI and OSS literature, we introduce an extended OSS development project organization model that adds a new level of communication and roles for attending human aspects of software. The proposed model makes the existence of HCI specialists visible in the projects, and promotes interaction between developers and the HCI specialists in the course of a project.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_22},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Intergrating\%20HCI\%20Specialists.pdf},
	author = {Hedberg, Henrik and Iivari, Netta}
}
@conference {1812,
	title = {Measuring the performance of open source development communities: The QualOSS approach},
	booktitle = {MetriKon 2009 - Praxis der Software-Messung : Tagungsband des DASMA Software Metrik Kongresses},
	year = {2009},
	abstract = {Free and Open Source Software (F/OSS) has an increasing importance for the software industry. Similar to traditional (closed) software acquisition, F/OSS acquisition requires an assessment of whether its quality is sufficient for the intended purpose, and of whether the chances of being maintained and supported in the future, as well as of keeping certain quality standards over time, are sufficiently high. The first one of these aspects is strictly product related, and can be assessed using techniques that are not specific to F/OSS. The last two aspects, however, are related to the community developing the software, and require novel approaches to be evaluated properly.
In this paper, we present an approach toward a comprehensive measurement framework for F/OSS projects, developed in the EU project QualOSS. Although this approach takes into account product quality as well as process maturity and sustainability of the underlying F/OSS community, we concentrate here on its community-related aspects. After describing our quality model and assessment techniques in some detail, we close with a description of our ongoing evaluation effort and a discussion of lessons learned.},
	url = {http://publica.fraunhofer.de/documents/N-117870.html},
	author = {Soto, Martin and Izquierdo-Cort{\'a}zar, Daniel and Ciolkowski, Marcus}
}
@article {1236,
	title = {Tools for the Study of the Usual Data Sources found in Libre Software Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	month = {31/2009},
	pages = {24 - 45},
	abstract = {Due to the open nature of Free/Libre/Open Source software projects, researchers have gained access to a rich set of development-related information. Although this information is publicly available on the Internet, obtaining and analyzing it in a convenient way is not an easy task and many considerations have to be taken into account. In this paper we present the most important data sources that can be found in libre software projects and that are studied by the research community: source code, source code management systems, mailing lists and bug tracking systems. We will give advice for the problems that can be found when retrieving and preparing the data sources for a posterior analysis, as well as provide information about the tools that support these tasks.},
	keywords = {bug tracking systems, data sources, mailing lists, scm, tools},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009010102},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles.pdf},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Izquierdo-Cortazar, Daniel and Herraiz, Israel}
}
@article {10.1109/HICSS.2009.1014,
	title = {Using Software Archaeology to Measure Knowledge Loss in Software Projects Due to Developer Turnover},
	journal = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {Developer turnover can result in a major problem when developing software. When senior developers abandon a software project, they leave a knowledge gap that has to be managed. In addition, new (junior) developers require some time in order to achieve the desired level of productivity. In this paper, we present a methodology to measure the effect of knowledge loss due to developer turnover in software projects. For a given software project, we measure the quantity of code that has been authored by developers that do not belong to the current development team, which we define as orphaned code. Besides, we study how orphaned code is managed by the project. Our methodology is based on the concept of software archaeology, a derivation of software evolution. As case studies we have selected four FLOSS (free, libre, open source software) projects, from purely driven by volunteers to company-supported. The application of our methodology to these case studies will give insight into the turnover that these projects suffer and how they have managed it and shows that this methodology is worth being augmented in future research.},
	keywords = {attrition, case study, developers, evince, evolution, gimp, growth, knowledge collaboration, lines of code, nautilus, quality, sloc, turnover},
	isbn = {978-0-7695-3450-3},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.1014},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-08.pdf},
	author = {Izquierdo-Cortazar, Daniel and Gregorio Robles and Ortega, Felipe and Jesus M. Gonzalez-Barahona}
}
@conference {584,
	title = {What Does It Take to Develop a Million Lines of Open Source Code?},
	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 = {170 - 184},
	publisher = {Springer},
	organization = {Springer},
	chapter = {16},
	abstract = {This article presents a preliminary and exploratory study of the relationship between size, on the one hand, and effort, duration and team size, on the other, for 11 Free/Libre/Open Source Software (FLOSS) projects with current size ranging between between 0.6 and 5.3 million lines of code (MLOC). Effort was operationalised based on the number of active committers per month. The extracted data did not fit well an early version of the closed-source cost estimation model COCOMO for proprietary software, overall suggesting that, at least to some extent, FLOSS communities are more productive than closed-source teams. This also motivated the need for FLOSS-specific effort models. As a first approximation, we evaluated 16 linear regression models involving different pairs of attributes. One of our experiments was to calculate the net size, that is, to remove any suspiciously large outliers or jumps in the growth trends. The best model we found involved effort against net size, accounting for 79 percent of the variance. This model was based on data excluding a possible outlier (Eclipse), the largest project in our sample. This suggests that different effort models may be needed for certain categories of FLOSS projects. Incidentally, for each of the 11 individual FLOSS projects we were able to model the net size trends with very high accuracy (R 2 >= 0.98). Of the 11 projects, 3 have grown superlinearly, 5 linearly and 3 sublinearly, suggesting that in the majority of the cases accumulated complexity is either well controlled or don{\textquoteright}t constitute a growth constraining factor.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_16},
	attachments = {https://flosshub.org/sites/flosshub.org/files/What\%20Does\%20it\%20Take\%20to\%20Develop.pdf},
	author = {Fernandez-Ramil, Juan and Izquierdo-Cortazar, Daniel and Mens, Tom}
}
@conference {530,
	title = {Mapping Linux Security Targets to Existing Test Suites},
	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 = {29 - 45},
	publisher = {Springer},
	organization = {Springer},
	chapter = {3},
	abstract = {The Common Criteria standard provides an infrastructure for evaluating security functions of IT products and for certifying that security policies claimed by product suppliers are correctly enforced by the security functions themselves. Certifying Open Source software (OSS) can pave the way to OSS adoption in a number of security-conscious application environments. Recent experiences in certifying Linux distributions has pointed out the problem of finding a mapping between descriptions of OSS security functions and existingtest suites developed independently, such as the Linux Test Project. In this paper, we describe a mechanism, based on matching techniques, which semiautomatically associates security functions to existing test suite such as the ones developed by Open Source communities.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Mapping\%20Linux\%20Security\%20Targets.pdf},
	author = {Ardagna, C. and Damiani, E. and Ioini, N. and Frati, F. and Giovannini, P. and Tchokpon, R.}
}
@article {1814,
	title = {Relationship between size, effort, duration and number of contributors in large FLOSS projects},
	journal = { 7th BElgian-NEtherlands software eVOLution workshop - BENEVOL 2008},
	year = {2008},
	abstract = {This contribution presents initial results in the study of the relationship between size,
effort, duration and number of contributors in eleven evolving Free/Libre Open Source
Software (FLOSS) projects, in the range from approx. 650,000 to 5,300,000 lines of
code. Our initial motivation was to estimate how much effort is involved in achieving
a large FLOSS system. Software cost estimation for proprietary projects has been an
active area of study for many years (e.g. [1][2][3]). However, to our knowledge, no previous
similar research has been conducted in FLOSS effort estimation. This research
can help planning the evolution of future FLOSS projects and in comparing them with
proprietary systems. Companies that are actively developing FLOSS may benefit from
such estimates [4]. Such estimates may also help to identify the productivity {\textquoteright}baseline{\textquoteright}
for evaluating improvements in process, methods and tools for FLOSS evolution},
	url = {http://oro.open.ac.uk/27317/1/},
	author = {Ramil, J.F. and Izquierdo-Cort{\'a}zar, Daniel and Mens, Tom}
}
@conference {560,
	title = {Usability in Company Open Source Software Context - Initial Findings from an Empirical Case Study},
	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 = {359 - 365},
	publisher = {Springer},
	organization = {Springer},
	chapter = {33},
	abstract = {In the company open source software (OSS) development context, usability is becoming an important issue due to a growing user population, who is only interested in usable applications, not in their development. Companies try to gain a competitive advantage of OSS by utilizing available components, but the openness is difficult to achieve in the business world with licenses, patents and intellectual property rights. This paper analyses usability and user-interface (UI) development in the company OSS context through an interpretive case study in a software development unit of a large, global corporation. Our initial findings suggest that there is a need for human computer interaction specialists in the OSS context. It is revealed that with the software based on OSS, more time can be spent on usability and UI design. In the company{\textquoteright}s viewpoint, there are still many issues involved in deciding what parts of the product will be open source. Especially UI code may remain closed due to competitive advantage and patents.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Usability\%20in\%20Company\%20Open\%20Source.pdf},
	author = {Iivari, Netta and Hedberg, Henrik and Kirves, Tanja}
}
@conference {1007,
	title = {Analysis of the Linux Kernel Evolution Using Code Clone Coverage},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {22 - 22},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Most studies of the evolution of software systems are based on the comparison of simple software metrics. In this paper, we present our preliminary investigation of the evolution of the Linux kernel using code-clone analysis and the code-clone coverage metrics. We examined 136 versions of the stable Linux kernel using a distributed extension of the code clone detection tool CCFinder. The result is shown as a heat map.},
	keywords = {ccfinder, clone, cloning, kernel, linux, metrics, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300022.pdf},
	author = {Livieri, Simone and Higo, Yoshiki and Matsushita, Makoto and Inoue, Katsuro}
}
@proceedings {118,
	title = {Design architecture, developer networks and performance of open source software projects},
	year = {2007},
	keywords = {NotreDameArchive},
	author = {Xiang Liu and Bala Iyer}
}
@conference {634,
	title = {Reusing an open source application {\textemdash} practical experiences with a mobile CRM pilot},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	year = {2007},
	month = {2007///},
	pages = {217 - 222},
	publisher = {Springer},
	organization = {Springer},
	chapter = {18},
	abstract = {We discuss experiences in extending an open source CRM application to develop a new server-based mobile business application. Combining the application code reuse with incremental development process allowed successful development of a pilot application in a tight schedule. In particular, it enabled a quick start for customer-driven development, diminished risks related to the baseline application itself, and provided the flexibility needed in experimental pilot development.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Reusing\%20an\%20Open\%20Source\%20Application.pdf},
	author = {Akkanen, Jyrki and Demeter, Hunor and Eppel, Tam{\'a}s and Iv{\'a}nfi, Zolt{\'a}n and Nurminen, Jukka and Stenman, Petri}
}
@conference {993,
	title = {Spam Filter Based Approach for Finding Fault-Prone Software Modules},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {4 - 4},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Because of the increase of needs for spam e-mail detection, the spam filtering technique has been improved as a convenient and effective technique for text mining. We propose a novel approach to detect fault-prone modules in a way that the source code modules are considered as text files and are applied to the spam filter directly. In order to show the applicability of our approach, we conducted experimental applications using source code repositories of Java based open source developments. The result of experiments shows that our approach can classify more than 75\% of software modules correctly.},
	keywords = {argouml, bug reports, classification, eclipse, java, modules, scm, spam, text mining},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300004.pdf},
	author = {Mizuno, Osamu and Ikami, Shiro and Nakaichi, Shuya and Kikuno, Tohru}
}
@article {111,
	title = {Social dynamics of free and open source team communications},
	journal = {Proceedings of the IFIP 2nd International Conference on Open Source Software, Lake Como, Italy},
	year = {2006},
	author = {James Howison and Inoue, K. and Kevin Crowston}
}
@conference {708,
	title = {Social dynamics of free and open source team communications},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {06/2006},
	pages = {319 - 330},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper furthers inquiry into the social structure of free and open source software (FLOSS) teams by undertaking social network analysis across time. Contrary to expectations, we confirmed earlier findings of a wide distribution of centralizations even when examining the networks over time. The paper also provides empirical evidence that while change at the center of FLOSS projects is relatively uncommon, participation across the project communities is highly skewed, with many participants appearing for only one period. Surprisingly, large project teams are not more likely to undergo change at their centers.
},
	keywords = {bug fixing, bug reports, bug tracker, bug tracking, bugs, communications, Dynamic social networks, FLOSS teams, Human Factors, social network analysis, software development, sourceforge},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_32},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Social\%20dynamics\%20of\%20free\%20and\%20open\%20source\%20team.pdf},
	author = {Howison, James and Inoue, Keisuke and Kevin Crowston}
}
@conference {699,
	title = {On the Weickian Model in the Context of Open Source Software Development: Some Preliminary Insights},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {3 - 8},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Despite being regarded as a path-breaking model of organising, Weick{\textquoteright}s Enactment-Selection-Retention (ESR) model has been labelled too abstract a model find any practical applications. This paper attempts to show that exploration-oriented open source projects represent valuable case studies where Weick{\textquoteright}s ESR model can be applied. By taking the Linux case study as a case in point, it is argued that a qualitative analysis of micro interactions (i.e. double interacts) might reveal broad organising patterns. Preliminary implications in terms of coordination and knowledge making processes are discussed in the final section.
},
	keywords = {case study, linux},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/On\%20the\%20Weickian\%20Model\%20in\%20the\%20Context.pdf},
	author = {Iannacci, Federico}
}
@article {flosswp220,
	title = {Anarchy and Source Code - What does the Free Software Movement have to do with Anarchism?},
	year = {2005},
	month = {March},
	abstract = {What does the hacker ethic have to do with anarchism? Why does Richard Stallman, an outstanding personality of the free software movement, described himself as an anarchist? We should not imagine the anarchists of the Free Software Movement to be like the cartoon image: A scruffy looking lunatic, with a crazy glint in his eyes and bristling with weapons. Instead of chaos, Stallman postulates a new form of order for the intellectual property in the terms of the hacker ethic - the access to knowledge should be free, decentralized, anti-bureaucratic and anti-authoritarian.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/imhorst.pdf},
	author = {Christian Imhorst}
}
@article {flosswp215,
	title = {Coordination Processes in Open Source Software Development: The Linux Case Study},
	year = {2005},
	month = {April},
	abstract = {Although open source projects have been subject to extensive study, their coordination processes are still poorly understood. Drawing on organization theory, this paper sets out to remedy this imbalance by showing that large-scale open source projects exhibit three main coordination mechanisms, namely standardization, loose coupling and partisan mutual adjustment. Implications in terms of electronically-mediated communications and networked interdependencies are discussed in the final sections where a new light is cast on the concept of structuring as a by-product of localized adjustments.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/iannacci3.pdf},
	author = {Federico Iannaci}
}
@proceedings {1174,
	title = {On Automatic Categorization of Open Source Software},
	year = {2003},
	pages = {79-83},
	attachments = {https://flosshub.org/sites/flosshub.org/files/79-83.pdf},
	author = {Kawaguchi, S. and Garg, P.K. and Matsushita, M. and Inoue, K.}
}
@article {flosswp99,
	title = {The Linux Managing Model},
	year = {2003},
	month = {July},
	abstract = {This study focuses on the distinguishing traits of the Linux managing model. It introduces the concept of process to capture the idea of impermanence, dissolvability and change. Far from being a predictable flow of programming, assembling and releasing activities, it is suggested that the Linux development process displays a stream of activities that keep feeding back into each other, thus creating a complex and unpredictable outcome. The paper further introduces the concept of contingent response patterns to investigate the interaction flows occurring on the Linux mailing lists and subsume patch postings, bug reports and the associated reviewing and debugging activities under its umbrella. The enactment-selection-retention (ESR) model is subsequently brought forward to conceptualize this process as enactment of programming skills subject to selection activities conducted by Torvalds who retains the selected features and feeds them back to the developers? pool to undergo further enactment activities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/iannacci2.pdf},
	author = {Federico Iannaci}
}
@article {flosswp60,
	title = {The Economics of Open Source Networks},
	year = {2002},
	month = {October},
	abstract = {The open-source movement is becoming an overarching feature of knowledgecreating environments and this research investigates the mechanisms whereby such a model comes into existence. Far from being the result of gifts of anonymous benefactors, the open-source model is the outcome of a conveyance of informative, valuative and incitive signals that larger sets of potential contributors construe in a subjective fashion. This study challenges the gift-economy metaphor and cautions the argument that open-source software is a reliable and generally applicable model for the forthcoming digital age.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/iannacci.pdf},
	author = {Federico Iannaci}
}
@conference {Yamauchi:2000:CLM:358916.359004,
	title = {Collaboration with Lean Media: how open-source software succeeds},
	booktitle = {Proceedings of the 2000 ACM conference on Computer supported cooperative work (CSCW)},
	series = {CSCW {\textquoteright}00},
	year = {2000},
	pages = {329{\textendash}338},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open-source software, usually created by volunteer programmers dispersed worldwide, now competes with that developed by software firms. This achievement is particularly impressive as open-source programmers rarely meet. They rely heavily on electronic media, which preclude the benefits of face-to-face contact that programmers enjoy within firms. In this paper, we describe findings that address this paradox based on observation, interviews and quantitative analyses of two open-source projects. The findings suggest that spontaneous work coordinated afterward is effective, rational organizational culture helps achieve agreement among members and communications media moderately support spontaneous work. These findings can imply a new model of dispersed collaboration.},
	keywords = {cooperative work, cvs, distributed work, electronic media, INNOVATION, open-source, software engineering},
	isbn = {1-58113-222-0},
	doi = {10.1145/358916.359004},
	url = {http://doi.acm.org/10.1145/358916.359004},
	author = {Yamauchi, Yutaka and Yokozawa, Makoto and Shinohara, Takeshi and Ishida, Toru}
}
