@proceedings {1921,
	title = {Who Added that Permission to My App? An Analysis of Developer Permission Changes in Open Source Android Apps},
	year = {2017},
	note = {"Our first step was to collect open source Android repositories
from F-Droid ... We collected the git repositories for each
app, ... we recorded
all permissions, including those which were custom. 
At the time of our analysis, F-Droid contained information
for 2,372 open source Android apps. ... This process
identified 1,402 apps that had a AndroidManifest.xml file
with a history of commits... we created a tool
known as Open Source Android Repository Analyzer (oSARA)...we extracted version control
commit information ... extracts all committed AndroidManifest.xml
files from the version control history ...the committed
version of the AndroidManifest.xml file was also extracted
from the repositories, and all metadata was stored in a SQLite
database"},
	month = {05/2017},
	pages = {165-169},
	abstract = {Android applications rely on a permission-based
model to carry out core functionality. Appropriate permission
usage is imperative for ensuring device security and protecting
the user{\textquoteright}s desired privacy levels. But who is making the important
decisions of which permissions the app should request? Are they
experienced developers with the appropriate project knowledge to
make such important decisions, or are these crucial choices being
made by those with relatively minor amounts of contributions to
the project? When are these permission-related decisions being
made in the app{\textquoteright}s development life cycle? We examined 1,402
Android version control repositories containing over 331,318
commits including 18,751 AndroidManifest.xml versions to better
understand when, why, and who is adding permissions to apps.
We found that (I) developers with more experience are more
likely to make permission-based changes (II) permissions are
typically added earlier in apps{\textquoteright} commit lifetime, but their
removal is more sustained throughout the commit lifetime (III)
developers reverting permission-based changes are typically more
experienced than developers who initially made the change being
reverted.},
	keywords = {android, mobile},
	author = {Krutz, Daniel E. and Nuthan Munaiah and Anthony Peruma and Mohamed Wiem Mkaouer}
}
@inbook {Heppler2016,
	title = {Who Cares About My Feature Request?},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {85{\textendash}96},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Previous studies on issue tracking systems for open source software (OSS) focused mainly on requests for bug fixes. However, requests to add a new feature or an improvement to an OSS project are often also made in an issue tracking system. These inquiries are particularly important because they determine the further development of the software. This study examines if there is any difference between requests of the IBM developer community and other sources in terms of the likelihood of successful implementation. Our study consists of a case study of the issue tracking system BugZilla in the Eclipse integrated development environment (IDE). Our hypothesis, which was that feature requests from outsiders have less chances of being implemented, than feature requests from IBM developers, was confirmed.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_7},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_7},
	author = {Heppler, Lukas and Eckert, Remo and Stuermer, Matthias},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Robles2016,
	title = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {163{\textendash}173},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	address = {Cham},
	abstract = {Women are underrepresented in the IT sector. But the situation in FLOSS (free, libre, open source software) development is really extreme in this respect: past publications and studies show a female participation of around 2 \% to 5 \% and have shed some light into this problem. In this paper, we give an update the state of knowledge to the current situation of gender in FLOSS, by analyzing the results of surveying more than 2,000 contributors to FLOSS projects in 2013, of which more than 200 were women. Our findings confirm that women enter the FLOSS community later than men, do primarily other tasks than coding, participate less if they have children, and have slightly different reasons to enter (and to stay in) the development communities they join. However, we also find evidence that women are joining FLOSS projects in higher numbers in recent years, and that the share of women devoting few hours per week to FLOSS and full-time dedication is higher than for men. All in all, comparing our results with the ones from the 2000s, the context of participation of women in FLOSS has not changed much.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_13},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_13},
	author = {Gregorio Robles and Reina, Laura Arjona and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Dom{\'\i}nguez, Santiago Due{\~n}as},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@proceedings {1830,
	title = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	year = {2016},
	month = {05/2016},
	pages = {163-173},
	publisher = {Springer},
	abstract = {Women are underrepresented in the IT sector. But the situation in FLOSS (free, libre, open source software) development is really extreme in this respect: past publications and studies show a female participation of around 2\% to 5\% and have shed some light into this problem. In this paper, we give an update the state of knowledge tot he current situation of gender in FLOSS, by analyzing the results of surveying more than 2,000 contributors to FLOSS projects in 2013, of which more than 200 were women. Our findings confirm that women enter the FLOSS community later than men, do primarily other tasks than coding, participate less if they have children, and have slightly different reasons to enter (and to stay in) the development communities they join. However, we also find evidence that women are joiningFLOSS projects in higher numbers in recent years, and that the share of women devoting few hours per week to FLOSS and full-time dedication is higher than for men. All in all, comparing our results with the ones from the 2000s, the context of participation of women in FLOSS has not changed much. 
},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper-pre.pdf},
	author = {Gregorio Robles and Reina, Laura Arjona and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Due{\~n}as Dominguez, Santiago}
}
@proceedings {1766,
	title = {Wait For It: Determinants of Pull Request Evaluation Latency on GitHub},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The pull-based development model, enabled by git
and popularised by collaborative coding platforms like BitBucket,
Gitorius, and GitHub, is widely used in distributed software
teams. While this model lowers the barrier to entry for potential
contributors (since anyone can submit pull requests to any repository),
it also increases the burden on integrators (i.e., members
of a project{\textquoteright}s core team, responsible for evaluating the proposed
changes and integrating them into the main development line),
who struggle to keep up with the volume of incoming pull
requests. In this paper we report on a quantitative study that tries
to resolve which factors affect pull request evaluation latency
in GitHub. Using regression modeling on data extracted from
a sample of GitHub projects using the Travis-CI continuous
integration service, we find that latency is a complex issue,
requiring many independent variables to explain adequately.},
	url = {https://bvasiles.github.io/papers/msr15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr15.pdf},
	author = {Yu, Yue and Wang, Huaimin and Filkov, Vladimir and Devanbu, Premkumar and Vasilescu, Bogdan}
}
@proceedings {1775,
	title = {What is the Gist? Understanding the Use of Public Gists on GitHub},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	keywords = {gist, github},
	author = {Weiliang Wang and Poo-Caama{\~n}o, Germ{\'a}n and Evan Wilde and German, Daniel}
}
@article {1686,
	title = {Why and How Should Open Source Projects Adopt Time-Based Releases?},
	journal = {IEEE Software, 32(2)},
	year = {2015},
	abstract = {Traditional release strategies have a number of associated problems, which can be overcome by time-based release management. We present findings from interviews with key members of seven prominent volunteer-based open source projects, all of which have adopted a time-based release strategy. We discuss the importance of release planning, the numerous challenges that can result from a lack of such planning, and the benefits of time-based releases. Finally, we discuss how an open source project can adopt a time-based release strategy.},
	url = {https://www.researchgate.net/publication/268815678_Why_and_How_Should_Open_Source_Projects_Adopt_Time-Based_Releases},
	author = {Martin Michlmayr and Fitzgerald, Brian}
}
@proceedings {1752,
	title = {Why Power Laws? An Explanation from Fine-Grained Code Changes},
	year = {2015},
	note = {"The data used in this section come from four open source Java projects. We used CVSANALY to collect data from their Git repositories."},
	abstract = {Throughout the years, empirical studies have found
power law distributions in various measures across many software
systems. However, surprisingly little is known about how
they are produced. What causes these power law distributions?
We offer an explanation from the perspective of fine-grained
code changes. A model based on preferential attachment and selforganized
criticality is proposed to simulate software evolution.
The experiment shows that the simulation is able to render power
law distributions out of fine-grained code changes, suggesting
preferential attachment and self-organized criticality are the
underlying mechanism causing the power law distributions in
software systems.},
	keywords = {Apache Maven, cvsanaly, eclipse, git, Google Guice, java, jedit, open source},
	url = {https://users.soe.ucsc.edu/~linzhp/msr2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015.pdf},
	author = {Zhongpeng Lin and Jim Whitehead}
}
@proceedings {1768,
	title = {Will they like this? Evaluating Code Contributions With Language Models},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Popular open-source software projects receive and
review contributions from a diverse array of developers, many
of whom have little to no prior involvement with the project. A
recent survey reported that reviewers consider conformance to
the project{\textquoteright}s code style to be one of the top priorities when evaluating
code contributions on Github. We propose to quantitatively
evaluate the existence and effects of this phenomenon. To this aim
we use language models, which were shown to accurately capture
stylistic aspects of code. We find that rejected changesets do
contain code significantly less similar to the project than accepted
ones; furthermore, the less similar changesets are more likely
to be subject to thorough review. Armed with these results we
further investigate whether new contributors learn to conform to
the project style and find that experience is positively correlated
with conformance to the project{\textquoteright}s code style.},
	url = {http://sback.it/publications/msr2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015_0.pdf},
	author = {Vincent J. Hellendoorn and Premkumar T. Devanbu and Bacchelli, Alberto}
}
@inbook {1626,
	title = {When Are OSS Developers More Likely to Introduce Vulnerable Code Changes? A Case Study},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {234-236},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

We analyzed peer code review data of the Android Open Source Project (AOSP) to understand whether code changes that introduce security vulnerabilities, referred to as vulnerable code changes (VCC), occur at certain intervals. Using a systematic manual analysis process, we identified 60 VCCs. Our results suggest that AOSP developers were more likely to write VCCs prior to AOSP releases, while during the post-release period they wrote fewer VCCs.
},
	keywords = {FOSS, open source, OSS, security, vulnerability},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_37},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_37},
	author = {Bosu, Amiangshu and Carver, JeffreyC. and Hafiz, Munawar and Hilley, Patrick and Janni, Derek},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1593,
	title = {Who Contributes to What? Exploring Hidden Relationships between FLOSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {21-30},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {In this paper we address the challenge of tracking resembling open source projects by exploiting the information of which developers contribute to which projects. To do this, we have performed a social network study to analyze data collected from the Ohloh repository. Our findings suggest that the more shared contributors two projects have, the more likely they resemble with respect to properties such as project application domain, programming language used and project size.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_3},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_3},
	author = {Syeed, M.M.Mahbubul and Hammouda, Imed},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@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 {1497,
	title = {Why So Complicated? Simple Term Filtering and Weighting for Location-Based Bug Report Assignment Recommendation},
	year = {2013},
	month = {05-2013},
	pages = {2-11},
	abstract = {Large software development projects receive many
bug reports and each of these reports needs to be triaged. An
important step in the triage process is the assignment of the
report to a developer. Most previous eorts towards improving
bug report assignment have focused on using an activity-based
approach. We address some of the limitations of activity-based
approaches by proposing a two-phased location-based approach
where bug report assignment recommendations are based on the
predicted location of the bug. The proposed approach utilizes
a noun extraction process on several information sources to
determine bug location information and a simple term weighting
scheme to provide a bug report assignment recommendation.
We found that by using a location-based approach, we achieved
an accuracy of 89.41\% and 59.76\% when recommending five
developers for the Eclipse and Mozilla projects, respectively.},
	keywords = {bug, bug report assignment, eclipse, File Activity Histories, Mining Software Artifacts, mozilla, Named Entity Recognition, POS Filtering},
	url = {http://www.cwu.edu/~janvik/papers/msr2013.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2013.pdf}
}
@proceedings {1499,
	title = {Will My Patch Make It? And How Fast?: Case Study on the Linux Kernel},
	year = {2013},
	month = {05/2013},
	abstract = {The Linux kernel follows an extremely distributed reviewing and integration process supported by 130 developer mailing lists and a hierarchy of dozens of Git repositories for version control. Since not every patch can make it and of those that do, some patches require a lot more reviewing and integration effort than others, developers, reviewers and integrators need support for estimating which patches are worthwhile to spend effort on and which ones do not stand a chance. This paper cross- links and analyzes eight years of patch reviews from the kernel mailing lists and committed patches from the Git repository to understand which patches are accepted and how long it takes those patches to get to the end user. We found that 33\% of the patches makes it into a Linux release, and that most of them need 3 to 6 months for this. Furthermore, that patches developed by more experienced developers are more easily accepted and faster reviewed and integrated. Additionally, reviewing time is impacted by submission time, the number of affected subsystems by the patch and the number of requested reviewers.},
	author = {Yujuan Jiang and Adams, Bram and Daniel M. German}
}
@conference {bird2012www,
	title = {Who? What? Where? Examining Distributed Development in Two Large Open Source Projects},
	booktitle = {Proceedings of the Working Conference on Mining Software Repositories},
	year = {2012},
	abstract = {To date, a large body of knowledge has been built up around understanding open source software development. However, there is limited research on examining levels of geographic and organizational distribution within open source software projects, despite many studies examining these same aspects in commercial contexts. We set out to fill this gap in OSS knowledge by manually collecting data for two large, mature, successful projects in an effort to assess how distributed both geographically and organizationally. Both Firefox and Eclipse have been the subject of many studies and are ubiquitous in the areas of software development and internet usage respectively. Further, both receive substantial development contributions from many companies. As such, both are worthy of study in order to understand the development processes that they use, how distributed the projects are, and what, if any, relationship distribution has with quality. To this end, we identified the top contributors that made 95\% of the changes over multiple major releases of Firefox and Eclipse and determined their geographic locations and organizational affiliations. We found that Firefox is very geographically distributed with over a third of its components receiving major contributions from developers on different continents, and that components that are highly distributed have no more defects than those that are not. In contrast, Eclipse is directed and developed largely by one company; with IBM making 96\% of the total commits (49\% coming from one lab in Ottawa, Canada). We further examined the distribution in each project{\textquoteright}s constituent subsystems and report the relationship of pre- and post-release defects with geographic and organizational factors.},
	keywords = {eclipse, Firefox},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2012www.pdf},
	author = {Christian Bird and Nachiappan Nagappan}
}
@conference {1319,
	title = {Who Will Remain? An Evaluation of Actual Person-Job and Person-Team Fit to Predict Developer Retention in FLOSS Projects},
	booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences},
	year = {2012},
	month = {01/2012},
	pages = {3446-3455},
	abstract = {Many businesses and private households rely on Free Libre Open Source Software (FLOSS). Due to a lack of sustained contributors, however, most FLOSS projects do not survive. The early identification of developers who are likely to remain is thus an eminent challenge for the management of FLOSS initiatives. Previous research has shown that individuals{\textquoteright} subjective assessment is often inaccurate emphasizing the need to objectively evaluate retention behavior. Consistent with the concepts Person-Job (P-J) and Person-Team (P-T) fit from the traditional recruitment literature, we derive objective measures to predict developer retention in FLOSS projects. In an analysis of the contribution behavior of former Google Summer of Code (GSoC) students we reveal that the level of development experience and conversational knowledge is strongly associated with retention. Surprisingly, our analysis reveals that students with abilities that are underrepresented in the project and students with a higher academic education do not remain considerably longer.},
	keywords = {email, email archives, google summer of code, kde, mailing list, students},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2012.644},
	attachments = {https://flosshub.org/sites/flosshub.org/files/45.pdf},
	author = {Schilling, A. and Laumer, S. and Weitzel, T.}
}
@proceedings {1269,
	title = {What kind of commons is free software?},
	year = {2011},
	note = {Available under a CreativeCommons BY-NC-SA license (http://creativecommons.org/licenses/by-nc-sa/3.0/). The presentation slides are also attached; paper{\textquoteright}s LaTeX source files can be found at http://www.mediafire.com/?7k9dxbkna0x6irl},
	month = {06/2011},
	address = {Berlin, Germany},
	abstract = {This paper analyzes free software under the light of commons theories, and tries to answer whether it is a managed or open access commons. It briefly presents commons studies and its main concepts, as well as the discussion on immaterial commons, arguing that goods{\textquoteright} intrinsic characteristics should not be viewed as absolute, but rather contextualized in social struggles. Then, it proposes a two-tier structure for analyzing free software as a commons, considering its dual nature as source and machine code. The two connected layers of the proposal - use and development - are characterized according to commons theory categories; Android and software forking are explored as examples. It concludes that the first layer resembles an open access commons, but with intensional boundaries, and that the second one resembles multiple managed commons. This disparity is associated with the category of nested enterprises and with the layers{\textquoteright} relations to appropriation and production.},
	keywords = {commons, COMMUNITY, free software, governance},
	issn = {1613-0073},
	url = {http://ceur-ws.org/Vol-739/paper_10.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/VIEIRA.pdf , https://flosshub.org/sites/flosshub.org/files/VIEIRA_presentation_0.odp},
	author = {Vieira, Miguel Said}
}
@conference {1311,
	title = {What topics do Firefox and Chrome contributors discuss?},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {234-237},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Firefox and Chrome are two very popular open source Web browsers, implemented in C/C++. This paper analyzes what topics were discussed in Firefox and Chrome bug reports over time. To this aim, we indexed the text contained in bug reports submitted each semester of the project history, and identified topics using Latent Dirichlet Allocation (LDA). Then, we investigated to what extent Firefox and Chrome developers/contributors discussed similar topics, either in different periods, or over the same period. Results indicate a non-negligible overlap of topics, mainly on issues related to page layouting, user interaction, and multimedia contents.},
	keywords = {bug reports, chrome, Firefox, LDA, msr challenge},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985480},
	author = {Zagarese, Quirino and Distante, Damiano and Di Penta, Massimiliano and Bernardi, Mario Luca and Sementa, Carmine}
}
@proceedings {1378,
	title = {When Cultures Clash: Participation in Open Source Communities and Its Implications For Organizational Commitment},
	number = {7},
	year = {2011},
	abstract = {Software applications developed within the OSS community have enjoyed tremendous success and for-profit organizations are keen to tap into this significant pool of software development talent (Chesbrough 2003; Feller et al. 2008). Examples companies include Netscape, IBM and Google (Maccormack et al. 2006). These companies seek to benefit from the talent of a global and sometimes voluntary workforce by paying some employees to contribute to OSS projects (Raymond 1999, Shah 2006). This merging of open and traditional software development may cause developer stress based on conflicting OSS community and traditional software development norms. Specifically, developers must balance company intellectual property concerns with the reciprocal and community-based norms that drive OSS development (Stewart and Gosain 2006). When these values are not in sync, contributors that aim to abide by conflicting values may exhibit dysfunctional attitudes. Employee stress with respect to their role can be destructive to organizational outcomes (Maas and Matejka 2009; Aranya and Ferris 1984). This study develops an OSS context specific model that describes the relationship between clashing software development cultures and employee organizational commitment. We leverage the rich OSS literature and the research that focuses on organizational-professional conflict (OPC) to develop hypotheses linking clashing cultures and organizational commitment. These hypotheses are tested using a combination of archival data and a survey of 127 GNOME developers. The findings presented in this paper contribute to OSS literature and offer findings that will enable organizations to more successfully engage OSS communities.},
	keywords = {gnome},
	url = { http://aisel.aisnet.org/icis2011/proceedings/projmanagement/7 },
	author = {Daniel, Sherae L. and Maruping, Likoebe M. and Cataldo, Marcelo and Herbsleb, James}
}
@book {1250,
	title = {Warehousing and Studying Open Source Versioning Metadata},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: New Horizons (OSS 2010)},
	volume = {319},
	year = {2010},
	pages = {413 - 418},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {In this paper, we describe the downloading and warehousing of Open Source Software (OSS) versioning metadata from SourceForge, BerliOS Developer, and GNU Savannah. This data enables and supports research in areas such as software engineering, open source phenomena, social network analysis, data mining, and project management. This newly-formed database containing Concurrent Versions System (CVS) and Subversion (SVN) metadata offers new research opportunities for large-scale OSS development analysis. The CVS and SVN data is juxtaposed with the SourceForge.net Research Data Archive [5] for the purpose of performing more powerful and interesting queries. We also present an initial statistical analysis of some of the most active projects. },
	keywords = {berlios, cvs, savannah, scm, sourceforge, srda, subversion, svn},
	isbn = {978-3-642-13244-5},
	issn = {1861-2288},
	doi = {10.1007/978-3-642-13244-5_40},
	author = {van Antwerp, M. and Madey, G.},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Madey, Gregory R. and Noll, John}
}
@article {1239,
	title = {Weaving a Semantic Web Across OSS Repositories},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	month = {32/2010},
	pages = {29 - 40},
	abstract = {Several public repositories and archives of {\textquotedblleft}facts{\textquotedblright} about libre software projects, maintained either by open source communities or by research communities, have been flourishing over the Web in recent years. These have enabled new analysis and support for new quality assurance tasks. This paper presents some complementary existing tools, projects and models proposed both by OSS actors or research initiatives that are likely to lead to useful future developments in terms of study of the FLOSS phenomenon, and also to the very practitioners in the FLOSS development projects. A goal of the research conducted within the HELIOS project is to address bugs traceability issues. In this regard, the authors investigate the potential of using Semantic Web technologies in navigating between many different bugtracker systems scattered all over the open source ecosystem. By using Semantic Web techniques, it is possible to interconnect the databases containing data about open-source software projects development, which enables OSS partakers to identify resources, annotate them, and further interlink those using dedicated properties and collectively designing a distributed semantic graph.},
	keywords = {archive, bug, bugtracker, database, debian, forge, interoperability, ontology, OSLC-CM, RDF, repository of repositories, semantic, semantic Web},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010040103},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd2009-olivier-berger.pdf},
	author = {Olivier Berger and Valentin Vlasceanu and Christian Bac and Quang Vu Dang and Lauriere, St{\'e}phane}
}
@article {10.1109/TSE.2010.63,
	title = {What Makes a Good Bug Report?},
	journal = {IEEE Transactions on Software Engineering},
	volume = {36},
	year = {2010},
	note = {"o find out which matter most, we asked 872 devel-
opers from the APACHE, ECLIPSE, and MOZILLA projects to:
1. Complete a survey on important information in bug reports and the problems they faced with them. We received a total of 156 responses to our survey (Section 2 and 3).
2. Rate the quality of bug reports from very poor to very good on a five-point Likert scale [22]. We received a total of 1,186 votes for 289 randomly selected bug reports (Section 4).
In addition, we asked 1,354 reporters1 from the same projects to complete a similar survey, out of which 310 responded. "},
	pages = {618-643},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {In software development, bug reports provide crucial information to developers. However, these reports widely differ in their quality. We conducted a survey among developers and users of APACHE, ECLIPSE, and MOZILLA to find out what makes a good bug report.
The analysis of the 466 responses revealed an information mis- match between what developers need and what users supply. Most developers consider steps to reproduce, stack traces, and test cases as helpful, which are at the same time most difficult to provide for users. Such insight is helpful to design new bug tracking tools that guide users at collecting and providing more helpful information.
Our CUEZILLA prototype is such a tool and measures the quality of new bug reports; it also recommends which elements should be added to improve the quality. We trained CUEZILLA on a sample of 289 bug reports, rated by developers as part of the survey. In our experiments, CUEZILLA was able to predict the quality of 31{\textendash}48\% of bug reports accurately.},
	keywords = {bug report, Survey},
	issn = {0098-5589},
	doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.2010.63},
	url = {http://dl.acm.org/citation.cfm?id=1453146},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bettenburg-fse-2008.pdf},
	author = {Zimmermann, Thomas and Premraj, Rahul and Bettenburg, Nicolas and Sascha Just and Schroter, Adrian and Weiss, Cathrin}
}
@article {1326,
	title = {What{\textquoteright}s all the FOSS?},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {1 - 14},
	abstract = {Philosophical, financial, practical, and pedagogical considerations have prompted educators to take a serious look at Free and Open Source Software (FOSS) as an alternative to proprietary software. To better understand the overall concept of FOSS, this article provides a brief history of FOSS as well as a summary of its definition, philosophy, and major areas of research, including strengths and limitations, diffusion in education and educational uses as well as a look at the opportunities, issues, and challenges associated with FOSS. In conclusion, the authors speculate how FOSS, along with advances in E-Learning and other emerging technologies, will positively shape our educational future. },
	issn = {1942-3934},
	doi = {10.4018/jossp.2010010101},
	author = {Huett, Jason B. and Sharp, Jason H. and Huett, Kimberly C.}
}
@conference {953,
	title = {When process data quality affects the number of bugs: Correlations in software engineering datasets},
	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 = {62 - 71},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Software engineering process information extracted from version control systems and bug tracking databases are widely used in empirical software engineering. In prior work, we showed that these data are plagued by quality deficiencies, which vary in its characteristics across projects. In addition, we showed that those deficiencies in the form of bias do impact the results of studies in empirical software engineering. While these findings affect software engineering researchers the impact on practitioners has not yet been substantiated. In this paper we, therefore, explore (i) if the process data quality and characteristics have an influence on the bug fixing process and (ii) if the process quality as measured by the process data has an influence on the product (i.e., software) quality. Specifically, we analyze six Open Source as well as two Closed Source projects and show that process data quality and characteristics have an impact on the bug fixing process: the high rate of empty commit messages in Eclipse, for example, correlates with the bug report quality. We also show that the product quality - measured by number of bugs reported - is affected by process data quality measures. These findings have the potential to prompt practitioners to increase the quality of their software process and its associated data quality.},
	keywords = {apache, bug reports, eclipse, gnome, log files, mozilla, netbeans, openoffice.org, version control},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463286},
	attachments = {https://flosshub.org/sites/flosshub.org/files/62bachmann-msr10.pdf},
	author = {Bachmann, Adrian and Bernstein, Abraham}
}
@conference {1205,
	title = {Weaving~a~Semantic~Web~across~OSS~repositories: a~spotlight~on~bts-link,~UDD,~SWIM},
	booktitle = {4th Workshop on Public Data about Software Development (WoPDaSD 2009)},
	year = {2009},
	note = {position paper; non-experimental},
	abstract = {Several  public  repositories  and  archives  of  facts  about  libre software  projects,  developed either  by open  source  communities  or by research communities,  have been flourishing over  the Web in  the  recent  years.  These  enable  new analysis  and  support  new quality assurance tasks. 

By  using  Semantic  Web  techniques,  the  databases  containing data  about  open-source  software projects development can  be interconnected,  hence  letting  OSS  partakers  identify  resources, annotate  them  and  further  interlink  them  using  dedicated properties,  collectively  designing  a  distributed  semantic  graph. Such  links  expressed  with  standard  Semantic  techniques  are paving  the  way  to  new  applications  (including  ones  meant  for {\textquotedblleft}end-users{\textquotedblright}).  For  instance  this  may have  an  impact  on  the  way research efforts  are  conducted  (less  fragmented),  and  could  also be  used  by  development  communities  to  improve  Quality Assurance tasks. 

A goal  of the  research  conducted  within  the  HELIOS project, is to  address  bugtracker  synchronization  issues.  For that, the potential of using Semantic  Web  technologies  in  navigating between many different  bugtracker  systems scattered all  over the open source ecosystem is being investigated. 

This  position  paper  presents  some  existing  tools,  projects  and models  proposed  by  OSS  actors  that  are  complementary  to research  initiatives,  and  that  are  likely to  lead  to  useful  future  developments:  UDD (Ultimate  Debian  Database)  and  bts-link, developed by the  Debian community,  and  SWIM (Semantic Web enabled Issue Manager) developed by Mandriva. 

The  HELIOS team welcomes  comments  on the  future  paths  that  can  be  considered  in  using  the  Semantic  Web  approach  for improving these projects. },
	keywords = {bts-link, bug tracker, bugzilla, debian, ecosystem, helios, mandriva, semantic Web, swim, udd},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HELIOS-WOPDASD-improved-Olivier.pdf},
	author = {Olivier Berger and Valentin Vlasceanu and Christian Bac and Lauri{\`e}re, St{\'e}phane}
}
@conference {939,
	title = {On what basis to recommend: Changesets or interactions?},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {155 - 158},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Different flavours of recommendation systems have been proposed to help software developers perform software evolution tasks. A number of these recommendation systems are based on changesets. When changeset information is used, recommendations are based on only the end result of the activity undertaken to complete a task. In this paper, we report on an investigation that compared how recommendations based on changesets compare to recommendations based on interactions collected as a programmer performed the task that resulted in a changeset. To provide a common basis for the comparison, our investigation considered how bug reports considered similar based on changeset information compare to bug reports considered similar based on interaction information. We found that there is no direct relationship between the bug reports found similar with the different methods, suggesting that each comparison methods captures a different aspect of the problem.},
	keywords = {bug reports, changeset, eclipse, mylyn},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069494},
	author = {Rastkar, Sarah and Murphy, Gail C.}
}
@conference {595,
	title = {What Constitutes Open Source? A Study of the Vista Electronic Medical Record Software},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	year = {2009},
	month = {2009///},
	pages = {310 - 319},
	publisher = {Springer},
	organization = {Springer},
	chapter = {27},
	abstract = {Strictly speaking, Open Source Software is any program that is covered by an Open Source Software license. However, the notion of Open Source Software Development conjures images of high-quality, market dominating products developed by armies of volunteer programmers, who work only for the joy of programming. Certainly, banner projects like Apache, the Linux kernel, and Mozilla/Firefox resemble this notion, even if they do employ significant numbers of paid programmers. This paper examines three Open Source Software projects related to the Vista Electronic Medical Record system developed and maintained by the U.S. Department of Veterans Affairs and released to the public domain. While all three claim to be {\textquotedblleft}Open Source{\textquotedblright} projects, there is considerable deviation from the strong community-oriented model that Linux, Apache, and Mozilla represent.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/What\%20Constitues\%20Open\%20Source.pdf},
	author = {Noll, John}
}
@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}
}
@article {1338,
	title = {What Makes Free/Libre Open Source Software (FLOSS) Projects Successful? An Agent-Based Model of FLOSS Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {1 - 13},
	abstract = {The last few years have seen a rapid increase in the number of Free/Libre Open Source Software (FLOSS) projects. Some of these projects, such as Linux and the Apache web server, have become phenomenally successful. However, for every successful FLOSS project there are dozens of FLOSS projects which never succeed. These projects fail to attract developers and/or consumers and, as a result, never get off the ground. The aim of this research is to better understand why some FLOSS projects flourish while others wither and die. This article presents a simple agent-based model that is calibrated on key patterns of data from SourceForge, the largest online site hosting open source projects. The calibrated model provides insight into the conditions necessary for FLOSS success and might be used for scenario analysis of future developments of FLOSS.},
	keywords = {Agent-Based Model, Emergent Properties, FLOSS, open source, Prediction Success, Simulation},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009040101},
	url = {http://www.public.asu.edu/~majansse/pubs/ijossp09.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ijossp09.pdf},
	author = {Radtke, Nicholas P. and Janssen, Marco A. and Collofello, James S.}
}
@conference {849,
	title = {Is Wikipedia Growing a Longer Tail?},
	booktitle = {ACM 2009 International Conference on Supporting Group Work},
	year = {2009},
	month = {05/10/2009},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Sanibel Island, FL},
	author = {Lam, S.K. and Riedl, J.}
}
@conference {851,
	title = {Wikipedians are born, not made: a study of power editors on Wikipedia},
	booktitle = {ACM 2009 International Conference on Group Work},
	year = {2009},
	month = {05/10/2009},
	pages = {51-60},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Sanibel Island, FL},
	keywords = {computer-supported, cooperative, interaction, web-based, work,},
	author = {Panciera, K. and Halfaker, A. and Terveen, L.}
}
@conference {604,
	title = {Workshop {\textendash} Serious Games and Open Source: Practice and Futures},
	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 = {361 - 362},
	publisher = {Springer},
	organization = {Springer},
	chapter = {36},
	abstract = {Computer games are increasingly used throughout our society with people playing on the bus, at home and at work. Computer games thus affect larger and larger number of people and areas in the society of today. There are even scholars who advocate that games create better environments for learning than traditional classrooms. This situation motivates the use of games and game technology for additional purposes, e.g. education, training, health care or marketing.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/.1007/978-3-642-02032-2_36},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Workshop\%20Serious\%20Games\%20and\%20Open\%20Source.pdf},
	author = {Backlund, Per and Lundell, Bj{\"o}rn and Walt Scacchi}
}
@conference {Hindle:2008:LCT:1370750.1370773,
	title = {What do large commits tell us?: a taxonomical study of large commits},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {99{\textendash}108},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Research in the mining of software repositories has frequently ignored commits that include a large number of files (we call these large commits). The main goal of this paper is to understand the rationale behind large commits, and if there is anything we can learn from them. To address this goal we performed a case study that included the manual classification of large commits of nine open source projects. The contributions include a taxonomy of large commits, which are grouped according to their intention. We contrast large commits against small commits and show that large commits are more perfective while small commits are more corrective. These large commits provide us with a window on the development practices of maintenance teams.},
	keywords = {boost, bug fixing, egroupware, enlightenment, evolution, firebird, large commits, maintenance, mysql, postgresql, samba, software evolution, source control system, spring},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370773},
	url = {http://doi.acm.org/10.1145/1370750.1370773},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p99-hindle.pdf},
	author = {Hindle, Abram and Daniel M. German and Holt, Ric}
}
@conference {Pohl:2008:DNM:1370114.1370135,
	title = {What dynamic network metrics can tell us about developer roles},
	booktitle = {Proceedings of the 2008 international workshop on Cooperative and human aspects of software engineering (CHASE {\textquoteright}08)},
	series = {CHASE {\textquoteright}08},
	year = {2008},
	note = {paper d/l from http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.217.4765

this particular paper focuses on building the SNA using co-authorship of files in Tomcat.},
	pages = {81{\textendash}84},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software development is heavily dependent on the participants of the process and their roles within the process. Each developer has his specific skills and interests and hence contributes to the project in a different way. While some programmers work on separate modules, others developers integrate these modules towards the final product. To identify such different groups of people one approach is to work with methods taken from social network analysis. To this end, a social network has to be defined in a suitable way, and appropriate analysis strategies have to be chosen. This paper shows how a network of software developers could be defined based on information in a software repository, and what it can possibly tell about roles of developers (and what not) in the process of the application server Tomcat.},
	keywords = {identifying roles, social network analysis},
	isbn = {978-1-60558-039-5},
	doi = {10.1145/1370114.1370135},
	url = {http://doi.acm.org/10.1145/1370114.1370135},
	attachments = {https://flosshub.org/sites/flosshub.org/files/10.1.1.217.4765.pdf},
	author = {Pohl, Mathias and Diehl, Stephan}
}
@conference {561,
	title = {Willingness to Cooperate Within the Open Source Software Domain},
	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 = {367 - 373},
	publisher = {Springer},
	organization = {Springer},
	chapter = {34},
	abstract = {Open Source Software (OSS) is an increasingly hot topic in the business domain. One of the key benefits mentioned is the unlimited access to the source code, which enables large communities to continuously improve a software application and prevents vendor lock-in. How attractive these benefits may be, the market for OSS however remains limited. In the Netherlands research consisting of 7 interviews and a survey among 206 Open Source Software Service providers (with a 34\% response rate) was done to determine whether service providers wanted to cooperate in an Association that will set quality levels and guarantees to its members and their customers.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_34},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Willingness\%20to\%20Cooperate.pdf},
	author = {Ravesteyn, Pascal and Silvius, Gilbert}
}
@conference {807,
	title = {Web Mash-ups and Patchwork Prototyping: User-driven technological innovation with Web 2.0 and Open Source Software},
	booktitle = {2007 40th Annual Hawaii International Conference on System Sciences (HICSS{\textquoteright}07)2007 40th Annual Hawaii International Conference on System Sciences (HICSS{\textquoteright}07)},
	year = {2007},
	pages = {86 - 86},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, HI, USA},
	abstract = {The recent emergence of web mash-ups and open
source software is driving the development of new
practices in software and systems development. In this
paper we explore novel practices of user-driven
innovation through an examination of several case
studies which illustrate how users and developers are
exploiting the proliferation of open APIs and open
source systems. Developers can rapidly create proofs
of concept that are robust enough for actual use by
combining preexisting software components. The
underlying programming processes involved make use
of tried-and-true software development techniques,
and may not appear innovative at first. However, the
application of these practices and techniques to
problem solving by non-programmers shows a high
degree of creative innovation, giving rise to new ways
of thinking about technology design and production.},
	isbn = {0-7695-2755-8},
	issn = {1530-1605},
	doi = {10.1109/HICSS.2007.612},
	author = {Floyd, I.R. and Jones, M.C. and Rathi, D. and Twidale, M.B}
}
@conference {1008,
	title = {What Can OSS Mailing Lists Tell Us? A Preliminary Psychometric Text Analysis of the Apache Developer Mailing List},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {23 - 23},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Developer mailing lists are a rich source of information about Open Source Software (OSS) development. The unstructured nature of email makes extracting information difficult. We use a psychometrically-based linguistic analysis tool, the LIWC, to examine the Apache httpd server developer mailing list. We conduct three preliminary experiments to assess the appropriateness of this tool for information extraction from mailing lists. First, using LIWC dimensions that are correlated with the big five personality traits, we assess the personality of four top developers against a baseline for the entire mailing list. The two developers that were responsible for the major Apache releases had similar personalities. Their personalities were different from the baseline and the other developers. Second, the first and last 50 emails for two top developers who have left the project are examined. The analysis shows promise in understanding why developers join and leave a project. Third, we examine word usage on the mailing list for two major Apache releases. The differences may reflect the relative success of each release.},
	keywords = {apache, developers, email, joining, liwc, mailing lists, personality},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.35},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300023.pdf},
	author = {Peter C. Rigby and Hassan, Ahmed E.}
}
@article {flosswp338,
	title = {What motivates Wikipedians: motivations for Wikipedia content contribution},
	year = {2007},
	month = {January},
	abstract = {Contributors??? motivations are critical for sustaining Wikipedia and other collaborative user-generated content outlets. Such outlets are based on contributions by people who volunteer their time and talent for the creation of content in return for no monetary reward. Therefore, in order to understand what underlies user-generated content contribution, we would need to find out what motivates volunteer content contributors. The results of a survey of 151 Wikipedia contributors indicate that the top motivations for contribution are Fun and Ideology. As expected, it was found that the levels of each of the motivations Fun, Values, Understanding, Enhancement, Protective, and Career were positively correlated with contribution level. Somewhat unexpectedly, contribution level was not correlated significantly with the Ideology and Social motivations.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Nov_Wikipedia_motivations_opensource.mit.edu.pdf},
	author = {Oded Nov}
}
@conference {1213,
	title = {Working with Open Source Development Data: Considerations triggered by a study of bug scenarios},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	month = {2007},
	abstract = {The retrieval and preparation of public data on software development calls for more than just technical skills. In 
addition, care and judgement are needed to avoid disproportionate costs to the providers of data or unnecessary embarrassment to the participants tracked in the data. Taking the extraction of bug scenarios as a use case, we illustrate these concerns and discuss how they could be translated into social requirements that would help to make retrieval and preparation a sustainable exercise. In particular, we call for more efforts to establish institutional repositories of public data on software development and, besides, we suggest that reviewers could play a role in making sure that empirical research is performed in a way that does not bring the long-term relationship between software developers and researchers in jeopardy. },
	keywords = {bug reports, bug scenarios, Data Collection},
	attachments = {https://flosshub.org/sites/flosshub.org/files/denBesten-wopdasd.pdf},
	author = {den Besten, Matthijs and Masmoudi, H{\'e}la and Jean-Michel Dalle}
}
@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}
}
@conference {Canfora:2006:BRK:1137983.1138032,
	title = {Where is bug resolution knowledge stored?},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {183{\textendash}184},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {ArgoUML uses both CVS and Bugzilla to keep track of bug-fixing activities since 1998. A common practice is to reference source code changes resolving a bug stored in Bugzilla by inserting the id number of the bug in the CVS commit notes. This relationship reveals useful to predict code entities impacted by a new bug report.In this paper we analyze ArgoUML software repositories with a tool, we have implemented, showing what are Bugzilla fields that better predict such impact relationship, that is where knowledge about bug resolution is stored.},
	keywords = {argouml, bugs, bugzilla, cvs, impact analysis, mining challenge, mining software repositories, msr challenge, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138032},
	url = {http://doi.acm.org/10.1145/1137983.1138032},
	attachments = {https://flosshub.org/sites/flosshub.org/files/183WhereIsBug.pdf},
	author = {Canfora, Gerardo and Cerulo, Luigi}
}
@conference {Anvik:2006:FTB:1134285.1134336,
	title = {Who should fix this bug?},
	booktitle = {Proceedings of the 28th international conference on Software engineering},
	series = {ICSE {\textquoteright}06},
	year = {2006},
	pages = {361{\textendash}370},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source development projects typically support an open bug repository to which both developers and users can report bugs. The reports that appear in this repository must be triaged to determine if the report is one which requires attention and if it is, which developer will be assigned the responsibility of resolving the report. Large open source developments are burdened by the rate at which new bug reports appear in the bug repository. In this paper, we present a semi-automated approach intended to ease one part of this process, the assignment of reports to a developer. Our approach applies a machine learning algorithm to the open bug repository to learn the kinds of reports each developer resolves. When a new report arrives, the classifier produced by the machine learning technique suggests a small number of developers suitable to resolve the report. With this approach, we have reached precision levels of 57\% and 64\% on the Eclipse and Firefox development projects respectively. We have also applied our approach to the gcc open source development with less positive results. We describe the conditions under which the approach is applicable and also report on the lessons we learned about applying machine learning to repositories used in open source development.},
	keywords = {bug fixing, bug report, bug report assignment, bug triage, eclipse, Firefox, gcc, issue tracking, machine learning, problem tracking},
	isbn = {1-59593-375-1},
	doi = {10.1145/1134285.1134336},
	url = {http://doi.acm.org/10.1145/1134285.1134336},
	author = {Anvik, John and Hiew, Lyndon and Murphy, Gail C.}
}
@conference {815,
	title = {Wikifying your interface:  Facilitating Community-Based Interface Translation},
	booktitle = {Proceedings of the 6th ACM conference on Designing Interactive systems  - DIS {\textquoteright}06},
	year = {2006},
	pages = {321-330},
	publisher = {ACM Press},
	organization = {ACM Press},
	abstract = {We explore the application of a wiki-based technology and
style of interaction to enabling the incremental translation
of a collaborative application into a number of different
languages, including variant English language interfaces
better suited to the needs of particular user communities.
The development work allows us to explore in more detail
the design space of functionality and interfaces relating to
tailoring, customization, personalization and localization,
and the challenges of designing to support ongoing
incremental contributions by members of different use
communities.},
	isbn = {1595933670},
	doi = {10.1145/1142405.1142453},
	author = {Jones, M.C. and Rathi, D. and Twidale, M.B}
}
@article {flosswp206,
	title = {Webservice Protocol Design for Economic Liberty and Observability},
	year = {2005},
	month = {March},
	abstract = {One big potential benefit of the webservices paradigm is in reducing the costs of inter-firm business transactions. That should allow small and medium-sized enterprises to compete successfully with big firms. This paper considers specifically the economic needs of peer-to-peer business alliances, defined as multiparty business alliances which are not under the control of any single firm or any small group of alliance members, so that each participating firm has full economic liberty. This organisational form is appropriate for example for Free Software businesses. The main conclusions are that achieving economic observability of business transactions is of great importance, and that this is difficult to achieve with the Remote Procedure Calls paradigm of JINI or XML / HTTP / SOAP based webservices. The problem can be overcome by using the SXDF / QQP / QRPC suite of webservice protocols,},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bollow.pdf},
	author = {Norbert Bollow}
}
@conference {799,
	title = {What is the significance of Open Source Software for the education and training community?},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {353-358},
	abstract = {There is growing interest in the education community in the development and use of Open Source Software. This paper explains the ideas behind OSS and how what its significance is for education. It examines regional and national initiatives to promote the use of OSS. The paper considers the advantages of OSS and potential problems. It goes on to look at the idea of open content and the sharing of learning content, and provides short case studies. The paper concludes that the major significance of OSS and open content is in the new social relations engendered and in fostering innovation in e-learning, both in application development and new pedagogies.},
	keywords = {economic issues, education, open source, pedagocic impact, training},
	url = {http://pascal.case.unibz.it/handle/2038/1563},
	author = {Attwell, Graham}
}
@conference {Sliwerski:2005:CIF:1083142.1083147,
	title = {When do changes induce fixes?},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {24-28},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {As a software system evolves, programmers make changes that sometimes cause problems. We analyze CVS archives for fix-inducing changes{\textemdash}changes that lead to problems, indicated by fixes. We show how to automatically locate fix-inducing changes by linking a version archive (such as CVS) to a bug database (such as BUGZILLA). In a first investigation of the MOZILLA and ECLIPSE history, it turns out that fix-inducing changes show distinct patterns with respect to their size and the day of week they were applied.},
	keywords = {bugzilla, change analysis, cvs, eclipse, evolution, mozilla},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083147},
	url = {http://doi.acm.org/10.1145/1082983.1083147},
	attachments = {https://flosshub.org/sites/flosshub.org/files/24WhenDoChanges.pdf},
	author = {Sliwerski, J and Zimmermann, Thomas and Zeller, Andreas}
}
@article {flosswp1738,
	title = {Why and how-to contribute to libre software when you integrate them into an in-house application ?},
	journal = {Proceedings of the 1st International Conference on Open Source Systems},
	year = {2005},
	month = {June},
	pages = {113{\textendash}118},
	abstract = {Free or open source software are common tools that everybody can use and customise at its convenience to create in-house applications. Using and customising free software is not sufficient to ensure that this in-house application will be maintainable at mid or long term. This paper draws lessons from our in-house project, the development of a groupware Web platform for researchers, to help defining a policy through which efficient contributions can be made to open source software so that the in-house projects may remain viable.},
	author = {Christian Bac and Olivier Berger and V{\'e}ronique Deborde and Benoit Hamet}
}
@inbook {53,
	title = {Why hackers do what they do: Understanding motivation and effort in free/open source software projects},
	booktitle = {Perspectives on Free and Open Source Software},
	year = {2005},
	publisher = {MIT Press},
	organization = {MIT Press},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lakhaniwolf.pdf},
	author = {Karim R Lakhani and Wolf, R.},
	editor = {Feller, J. and Fitzgerald, Brian and Hissam, S. and Karim R Lakhani}
}
@conference {801,
	title = {Workshop on "Open Source and Multimedia"},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {360},
	author = {Julien Bourgeois and Fran{\c c}ois Spies and Dodero, Gabriella and Vittoria Gianuzzi}
}
@article {flosswp171,
	title = {Waiting for F/OSS: Coordinating the Production of Free/Open Source Software},
	year = {2004},
	month = {August},
	abstract = {Trade-off between producing F/OSS module and free-riding is analyzed as game of war of attrition, in which modules developed and potential are heterogeneous. It may be optimal to produce "high-profile" module that creates reputation and signals programming ability. It may be optimal to volunteer strategically for "low-profile" module even if high-profile module is available to speed up development process and reduce costs of waiting. Even if waiting brings opportunity to free ride, there may be rush to develop high-profile module at the opportunity. Model provides explanation for how large-scale F/OSS projects can be coordinated without markets and prices nor hierarchies such as firms.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/stenborg.pdf},
	author = {Markku Stenborg}
}
@proceedings {1192,
	title = {WebDAV based Open Source Collaborative Development Environment},
	year = {2004},
	pages = {53-57},
	abstract = {Open source projects are characterized by their distributed developers, openness, and use of a community-based development process. Successful open source projects such as Apache, Linux, and PHP have a web-based Collaborative Development Environment (CDE) that provides source code repository access, knowledge management, discussion lists, bug tracking, and user support. Distributed software development is also increasingly common for commercial software projects, and benefits from using web-based CDEs. GForge, derived from the SourceForge package, is an open web-based CDE that is seeing widespread open source and commercial use. To support remote authoring of web pages and file contents, as well as remote source code access, GForge uses several network protocols, including SSH/SFTP, CVS pserver, and FTP. These protocols inevitably introduce security risks and add administrative work. We modified GForge to eliminate use of FTP, SSH/SFTP, and CVS protocols, using instead a WebDAV-based integration. The new CDE, called Davenport, uses only the HTTP/WebDAV protocol, and HTTP/WebDAV replaces the other protocols without sacrificing functionality. In this paper we describe the architecture and features of Davenport, and show how WebDAV replaces existing network protocols. We discuss the future development directions of CDEs including integration of client side IDEs and using a CDE as a software test bed.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Kim54-58.pdf},
	author = {Kim, S. and Pan, K. and Whitehead, J.}
}
@article {flosswp139,
	title = {When Consumers Produce on the Internet: The Relationship between Cognitive-affective, Socially-based, and Behavioral Involvement of Prosumers},
	year = {2004},
	month = {February},
	abstract = {This article advances our understanding of the motivational sources for consumer involvement in online joint innovation. The {\textquoteright}free{\textquoteright} or {\textquoteright}open-source{\textquoteright} software movement is the largest socio-technical network and most visible empirical evidence of this new phenomenon. The paper promotes a behavioral view of involvement and offers a conceptualization and empirical evidence of the relationship between cognitive-affective, socially-based and behavioral involvement in online joint production. An Internet survey with 1486 contributors to open-source software revealed that the extent of behavioral involvement is strongly related to the structure and strength of relationships between different motivations. The relationship between concern for self and concern for others especially distinguishes the level of contribution to online projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hemetsberger1.pdf},
	author = {Andrea Hemetsberger}
}
@proceedings {103,
	title = {Why developers participate in open source software projects: an empirical investigation},
	year = {2004},
	keywords = {Survey},
	author = {Il-Horn Hann and Jeff Roberts and Sandra Slaughter}
}
@article {DBLP:journals/electronicmarkets/VemuriB04,
	title = {Will the Open Source Movement Survive a Litigious Society?},
	journal = {Electronic Markets},
	volume = {14},
	number = {2},
	year = {2004},
	pages = {114-123},
	abstract = {Since no one is willing to undertake costly research and development to create innovation, incentives in the form of patents were instituted to motivate R\&D. In software development, contrary to economic intuition, open source software has emerged as a viable alternative source of innovation. The patenting system has performed reasonably well in enhancing many other technologies. Since the mid-1990s patenting of software and business methods is increasingly accepted in the United States. The legitimacy of many of these new patents is subject to controversy and debate. In this paper we examine the trend, rate of litigation and disposition of US patents in the US Federal Courts. We find that litigation rates of software and business method patents is four times that of all other patents and is increasing. A majority of patent litigations are not won by the perpetrator of the lawsuits. The open source software community is not immune to heightened patent litigations. Since software development is incremental, the paths of OSS and commercial development are entwined. The spillover of patent litigation into OSS may have disastrous consequences: It may increase the {\textquoteright}cost{\textquoteright} of OSS, dissuade volunteer developers and make OSS less attractive to users. },
	keywords = {courts, INNOVATION, lawsuit, litigation, patents, software patents},
	author = {Vijay K. Vemuri and Vince Bertone}
}
@article {flosswp52,
	title = {Why open source software can succeed},
	journal = {RP Special Issue},
	year = {2003},
	month = {February},
	abstract = {The paper discusses three key economic problems raised by the emergence and diffusion of open source software: motivation, coordination, and diffusion under a dominant standard. First the movement took off through the activity of a software development community that deliberately did not follow profit motivations. Second, a hierarchical coordination emerged without the support of an organization with proprietary rights. Third, Linux and other open source systems diffused in an evnvironment dominated by established proprietary standards, which benefited from significant increasing returns. The paper show that recent developments in the theory of critical mass in the diffusion of technologies with network externality may help to explain these phenomena.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-bonaccorsirossi.pdf},
	author = {Andrea Bonaccorsi}
}
@proceedings {1176,
	title = {Why OSS Folks Think SE Folks Are Clue-Impaired},
	year = {2003},
	pages = {91-97},
	attachments = {https://flosshub.org/sites/flosshub.org/files/91-97.pdf},
	author = {Bart Massey}
}
@conference {1158,
	title = {Where Do Open Source Requirements Come From (And What Should We Do About It)?},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {The collection and specification of software requirements is one of the most intense areas of software engineering research. This makes it a natural area to explore when considering open-source software. In this paper, I argue that the sources of open-source software requirements differ in some important respects from the sources of commercial software project requirements. This has some interesting implications for both open-source and commercial development.},
	keywords = {requirements},
	attachments = {https://flosshub.org/sites/flosshub.org/files/massey.pdf},
	author = {Bart Massey}
}
@conference {1157,
	title = {Why Do Developers Contribute to Open Source Projects? First Evidence of Economic Incentives},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	note = {"The data for this research come from two primary sources: Apache project archives and a targeted survey of Apache participants. Archival data are open source project artifacts such as email and source code archives, source code version control meta-data and developer web sites."},
	abstract = {The availability of commercial quality, free software products such as the Apache HTTP (web) server or the Linux operating system has focused significant attention on the open source development process by which these products were created. One of the more perplexing aspects of open source software projects is why developers freely devote their time and energy to these projects. While many open source participants cite idealistic motives for participation, Lerner and Tirole (2000) argue that developer participation in open source projects may, in part, be explained by existing economic theory regarding career concerns. This research seeks to confirm or disconfirm the existence of economic returns to participation in open source development. Preliminary results of our empirical investigation suggest that greater open source participation per se, as measured in contributions made, does not lead to wage increases. However, a higher status in a merit-based ranking within the Apache Project does lead to significantly higher wages. This suggests that employers do not reward the gain in experience through open source participation as an increase in human capital. The results are also consistent with the notion that a high rank within the Apache Software Foundation is a credible signal of the productive capacity of a programmer.},
	keywords = {apache, contributions, cvs, developers, ECONOMICS, email, email archives, financial, Human capital, mailing list, MOTIVATION, participation, source code, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HannRobertsSlaughterFielding.pdf},
	author = {Il-Horn Hann and Jeff Roberts and Sandra Slaughter and Roy Fielding}
}
@conference {1159,
	title = {Why Not Improve Coordination in Distributed Software Development by Stealing Good Ideas from Open Source?},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	keywords = {apache, communication, coordination, distributed},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MockusHerbsleb.pdf},
	author = {Audris Mockus and Herbsleb, James}
}
@article {106,
	title = {Working for free? Motivations for participating in open-source projects},
	journal = {International Journal of Electronic Commerce},
	volume = {6},
	number = {3},
	year = {2002},
	note = {Times Cited: 24},
	pages = {25-39},
	abstract = {The success of the Linux operating system has demonstrated the viability of open-source software, an alternative form of software development that challenges traditional assumptions about software markets. Understanding why developers participate in open-source projects is crucial for assessing the impact of open-source software. Their motivations fall into two broad categories: internal factors (e.g., intrinsic motivation, altruism) and external rewards (e.g., expected future returns, personal needs). The results of a survey administered to open-source programmers are summarized.},
	author = {Hars, A. and Ou, S. S.}
}
@article {47,
	title = {Working for Free? Motivations for Participating in Open-Source Projects},
	journal = {International Journal of Electronic Commerce},
	volume = {6},
	number = {3},
	year = {2002},
	pages = {25--39},
	publisher = {ME Sharpe},
	author = {Hars, A.}
}
@article {flosswp20,
	title = {The Web of Knowledge: An Investigation of Knowledge Exchange in Networks of Practice},
	year = {2001},
	month = {October},
	abstract = {Electronic ties are loosening the constraints of organizational structure and physical proximity to allow connectivity between individuals who would otherwise find it difficult to identify and sustain contact with others who share the similar interests. This paper explores the knowledge exchange processes in extra-organizational networks of practice by studying three technical newsgroups. We argue that the development of relational social capital is a vital component for transforming electronic posting forums into ongoing networks of practice. The results reveal that relational social capital exists on networks of practice and shows a strong relationship with knowledge exchange processes over and above the influence of individual motivation and ability.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Farajwasko.pdf},
	author = {Samer Faraj}
}
