@inbook {Abdulwahhab2016,
	title = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {3{\textendash}15},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	address = {Cham},
	abstract = {This paper investigates the position of local open source communities (LOSCs) in the development of open source projects (OSPs). We have conducted an empirical study to examine the role of LOSCs, their way of working, and the benefits/challenges they experience compared to the overall global community. The qualitative investigation consisted of ten semi-structured interviews with members within different LOSCs. The results confirm the importance of LOSCs and the pivotal role they play in the development of OSPs. In many cases, they act as the middleman between individual members and the project{\textquoteright}s global community. However, LOSCs have their own kinds of challenges.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_1},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_1},
	author = {Abdulwahhab, Sinan and Alabady, Yazen and Sattar, Yacoub and Hammouda, Imed},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {1743,
	title = {The Right to a Contribution: An Exploratory Survey on How Organizations Address It},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {157-167},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Free and Open Source Software (FOSS) projects are characterized by the opportunity to attract external contributors, where contributions can be in any form of copyrightable material, such as code or documentation. In most of them it is understood that contributions would be licensed in similar or compatible terms than the project{\textquoteright}s license. Some projects require a copyright transfer from the contributor to an organization for the work contributed to a project, such documents are known as copyright assignment agreements. In a way, it is similar to the copyright transfer than some researchers grant to a publisher. In this work we present an exploratory survey of the multiple visions of copyright assignments, and aggregate them in a work that researchers and practitioners could use to get informed of the alternatives available in the literature. We expect that our findings help inform practitioners on legal concerns when receiving external contributions.
},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_15},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_15},
	author = {Poo-Caama{\~n}o, Germ{\'a}n and German, DanielM.},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1740,
	title = {The RISCOSS Platform for Risk Management in Open Source Software Adoption},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {124-133},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Managing risks related to OSS adoption is a must for organizations that need to smoothly integrate OSS-related practices in their development processes. Adequate tool support may pave the road to effective risk management and ensure the sustainability of such activity. In this paper, we present the RISCOSS platform for managing risks in OSS adoption. RISCOSS builds upon a highly configurable data model that allows customization to several types of scopes. It implements two different working modes: exploration, where the impact of decisions may be assessed before making them; and continuous assessment, where risk variables (and their possible consequences on business goals) are continuously monitored and reported to decision-makers. The blackboard-oriented architecture of the platform defines several interfaces for the identified techniques, allowing new techniques to be plugged in.
},
	keywords = {Open source adoption, Open Source Projects, open source software, OSS, Risk Management, Software platform},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_12},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_12},
	author = {Franch, X. and Kenett, R. and Mancinelli, F. and Susi, A. and Ameller, D. and Annosi, M.C. and Ben-Jacob, R. and Blumenfeld, Y. and Franco, O.H. and Gross, D. and Lopez, L. and Morandini, M. and Oriol, M. and Siena, A.},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@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 {966,
	title = {Replaying IDE interactions to evaluate and improve change prediction approaches},
	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 = {161 - 170},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Change prediction helps developers by recommending program entities that will have to be changed alongside the entities currently being changed. To evaluate their accuracy, current change prediction approaches use data from versioning systems such as CVS or SVN. These data sources provide a coarse-grained view of the development history that flattens the sequence of changes in a single commit. They are thus not a valid basis for evaluation in the case of development-style prediction, where the order of the predictions has to match the order of the changes a developer makes. We propose a benchmark for the evaluation of change prediction approaches based on fine-grained change data recorded from IDE usage. Moreover, the change prediction approaches themselves can use the more accurate data to fine-tune their prediction. We present an evaluation procedure and use it on several change prediction approaches, both novel and from the literature, and report on the results.},
	keywords = {cbse, change based software evolution, change prediction, changes, commit, cvs, development history, eclipseeye, ide, mylyn, spyware, svn},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463278},
	attachments = {https://flosshub.org/sites/flosshub.org/files/161Robbes2010changePrediction.pdf},
	author = {Robbes, Romain and Pollet, Damien and Lanza, Michele}
}
@conference {947,
	title = {Replicating MSR: A study of the potential replicability of papers published in the Mining Software Repositories proceedings},
	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 = {171 - 180},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {This paper is the result of reviewing all papers published in the proceedings of the former International Workshop on Mining Software Repositories (MSR) (2004-2006) and now Working Conference on MSR (2007-2009). We have analyzed the papers that contained any experimental analysis of software projects for their potentiality of being replicated. In this regard, three main issues have been addressed: i) the public availability of the data used as case study, ii) the public availability of the processed dataset used by researchers and iii) the public availability of the tools and scripts. A total number of 171 papers have been analyzed from the six workshops/working conferences up to date. Results show that MSR authors use in general publicly available data sources, mainly from free software repositories, but that the amount of publicly available processed datasets is very low. Regarding tools and scripts, for a majority of papers we have not been able to find any tool, even for papers where the authors explicitly state that they have built one. Lessons learned from the experience of reviewing the whole MSR literature and some potential solutions to lower the barriers of replicability are finally presented and discussed.},
	keywords = {data, literature review, msr, replication},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463348},
	url = {http://gsyc.urjc.es/~grex/msr2010},
	attachments = {https://flosshub.org/sites/flosshub.org/files/171MSR_2010_69.final_.pdf},
	author = {Gregorio Robles}
}
@conference {herraiz2009research,
	title = {Research friendly software repositories},
	booktitle = {Proceedings of the joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops},
	year = {2009},
	note = {"In spite of these rich availability of software repositories,
the heterogeneity of the data makes it difficult to apply studies
at a large scale, although some research projects, like
FLOSSMole [10] or FLOSSMetrics [8] are addressing these
issues and aim to provide datasets about thousands of libre
software projects for research purposes."

(more)},
	pages = {19{\textendash}24},
	publisher = {ACM},
	organization = {ACM},
	abstract = {What is the future of software evolution? In 1974, Meir M. Lehman had a vision of software evolution being driven by empirical studies of software repositories, and of a theory based on those empirical results. However, that scenario is yet to come. Software evolution studies are often based on a few cases, because the needed information is scarce, dispersed and incomplete. Their conclusions are not generalizable, slowing down the progress of this research discipline. Libre (free / open source) software supposes an opportunity to alleviate this situation. In this paper we describe the existing approaches to provide research datasets that are mining libre software repositories, and propose an agenda based on the concept of research friendly software repositories, which provides finer granularity and integrated data.},
	keywords = {flossmetrics, flossmole cited},
	attachments = {https://flosshub.org/sites/flosshub.org/files/herraiz-Research-Friendly-sw-repos.pdf},
	author = {Herraiz, I. and Robles, G. and Gonzalez-Barahona, J.M.}
}
@conference {H{\"a}rtig09roitzsch:the,
	title = {Roitzsch: The Mathematics of Obscurity: On the Trustworthiness of Open Source},
	booktitle = {9th Workshop on the Economics of Information Security (WEIS)},
	year = {2009},
	pages = {2016{\textendash}2023},
	publisher = {ACM},
	organization = {ACM},
	abstract = {It is more difficult to find errors when source code is secret.
More people search for errors when source code is
public. These counteracting effects are pivotal to the question
whether openness fosters security. Errors in software
are found by people with either constructive contribution or
exploitation in mind. Focusing exclusively on this discovery
aspect, we present a probabilistic model, which allows us to
compare the open source and closed source situations.
We start out with our assumptions explained using a simple
introductory model. We then extend this to what we
believe to be an adequate model of a bug-hunting process
conducted by multiple competing parties. The model employs
an asymmetric race paradigm. One of the surprising
results is that even an arbitrarily large group with good intentions
cannot safely dominate the evil attackers. Instead,
they are limited by a significant upper bound in their winning
chances.},
	url = {http://www.econinfosec.org/archive/weis2010/papers/session6/weis2010_haertig.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/weis2010_haertig.pdf},
	author = {Hermann H{\"a}rtig and Claude-joachim Hamann and Michael Roitzsch and Technische Universit{\"a}t Dresden}
}
@conference {765,
	title = {The role of patch review in software evolution: an analysis of the mozilla firefox},
	booktitle = {The joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops},
	year = {2009},
	month = {08/2009},
	pages = {9-18},
	publisher = {ACM},
	organization = {ACM},
	type = {Paper in Conference Proceedings},
	address = {Amsterdam, The Netherlands},
	abstract = {Patch review is the basic mechanism for validating the design and implementation of patches and maintaining consistency in some commercial and Free/Libre/Open Source Software (FLOSS) projects. We examine the inner-workings of the development process of the successful and mature Mozilla foundation and highlight how different parties involved affect and steer the process. Although reviewers are the primary actors in the patch review process, success in the process can only be achieved if the community supports reviewers adequately. Peer developers play the supporting role by offering insight and ideas that help create more quality patches. Moreover, they reduce the huge patch backlog reviewers have to clear by identifying and eliminating immature patches.},
	keywords = {inspection, open source development},
	isbn = {978-1-60558-678-6},
	doi = {http://doi.acm.org/10.1145/1595808.1595813},
	url = {http://ase.cpsc.ucalgary.ca/ase/uploads/Publications/iwpse31-nurolahzade.pdf},
	author = {Mehrdad Nurolahzade},
	editor = {Seyed Mehdi Nasehi and Shahedul Huq Khandkar and Shreya Rawal}
}
@conference {843,
	title = {rv you{\textquoteright}re dumb: Identifying Discarded Work in Wiki Article History},
	booktitle = {The Fifth International Symposium on Wiki{\textquoteright}s and Open Collaboration},
	year = {2009},
	month = {10/25/2009},
	address = {Orlando, FL},
	author = {Ekstrand, M.D. and Riedl, J.T.}
}
@conference {973,
	title = {On the relation of refactorings and software defect prediction},
	booktitle = {Proceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {35-38},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {This paper analyzes the influence of evolution activities such as refactoring on software defects. In a case study of five open source projects we used attributes of software evolution to predict defects in time periods of six months. We use versioning and issue tracking systems to extract 110 data mining features, which are separated into refactoring and non-refactoring related features. These features are used as input into classification algorithms that create prediction models for software defects. We found out that refactoring related features as well as non-refactoring related features lead to high quality prediction models. Additionally, we discovered that refactorings and defects have an inverse correlation: The number of software defects decreases, if the number of refactorings increased in the preceding time period. As a result, refactoring should be a significant part of both bug fixes and other evolutionary changes to reduce software defects.},
	keywords = {argouml, bug fixing, bug reports, defects, evolution, jboss, liferay, prediction, refactoring, spring, weka, xdoclet},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370759},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p35-ratzinger.pdf},
	author = {Sigmund, Thomas and Gall, Harald C. and Ratzinger, Jacek}
}
@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 {884,
	title = {Recommenders Everywhere: The WikiLens Community-Maintained Recommender System},
	booktitle = {Wikisym 2007},
	year = {2007},
	address = {Montreal, Quebec, Canada},
	isbn = {978-1-59593-861-9},
	author = {Dan Frankowski and Shyong K. Lam and Shilad Sen and Harper, F. Maxwell and Scott Yilek and Michael Cassano and John Riedl}
}
@proceedings {131,
	title = {Remote analysis and measurement of libre software systems by means of the CVSanaly tool},
	year = {2004},
	address = {Edinburgh, Scotland},
	abstract = {Libre (free, open source) software is one of the paradigmatic cases where heavy use of telematic tools and user-driven software development are key points. This paper proposes a methodology for measuring and analyzing remotely big libre software projects using publicly-available data from their version control repositories. By means of a tool called CVSAnalY that has been implemented following this methodology, measurements and analyses can be made in an automatic and non-intrusive way, providing real-time and historical data about the project and its contributors.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles-koch-barahona_cvsanaly.pdf},
	author = {Gregorio Robles and Koch, Stefan and Jesus M. Gonzalez-Barahona}
}
@conference {Gasser04researchinfrastructure,
	title = {Research Infrastructure for Empirical Science of F/OSS},
	booktitle = {Proc. Intern. Workshop on Mining Software Repositories},
	year = {2004},
	pages = {12-16},
	abstract = {F/OSS research faces a new and unusual situation: the traditional difficulties of gathering enough empirical data have been replaced by issues of dealing with enormous amounts of freely available data from many disparate sources (forums, code, bug reports, etc.) At present no means exist for assembling these data under common access points and frameworks for comparative, longitudinal, and collaborative research. Gathering and maintaining large F/OSS data collections reliably and making them usable present several research challenges. For example, current projects usually rely on {\textquotedblleft}web scraping{\textquotedblright} or on direct access to raw data from groups that generate it, and both of these methods require unique effort for each new corpus, or even for updating existing corpora. In this paper we identify several common needs and critical factors in F/OSS empirical research, and suggest orientations and recommendations for the design of a shared research infrastructure.},
	keywords = {data, Data Collection, empirical, infrastructure},
	attachments = {https://flosshub.org/sites/flosshub.org/files/12ResearchInfrastructure.pdf},
	author = {Gasser, Les and Gabriel Ripoche and Sandusky, Robert J.}
}
@article {flosswp80,
	title = {Re-working by the Linux Kernel developers},
	year = {2003},
	month = {February},
	abstract = {Technology design is generally a matter of re-working existing systems rather than the designing of entirely novel artifacts. In this paper I explore part of a computer operating system called Linux that is designed to be re-worked by its users, a process I call {\textquoteright}designing for redesign{\textquoteright}. I examine the practices of reworking within this development effort using some concepts gleaned from activity theory, a meta-theoretical model that particularly focuses on the simultaneously material and conceptual aspects of artifacts. This work is two-fold; first to examine design as part of a larger activity of re-working, and second, to begin to put together a model of socio-technical activity that incorporates the complex epistemological and ontological conditions that characterize current human conditions. Understanding the sociality and materiality of "knowing" and "doing" in technologized society means unpacking what we mean when we talk of {\textquoteright}access{\textquoteright} and understanding {\textquoteright}use{\textquoteright} as often an activity of re-working.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ratto.pdf},
	author = {Matt Ratto}
}
@article {60,
	title = {The Revenge of the Hackers},
	year = {1999},
	pages = {207--219},
	author = {Raymond, E.S.}
}
