@proceedings {1890,
	title = {Designing for Participation: Three Models for Developer Involvement in Hybrid OSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {23-33},
	publisher = {Springer},
	abstract = {This paper reports governance practices of three profit oriented companies that develop OSS software with the help of their respective open development communities. We explore how the companies allow development contributions from external stakeholders, and what knowledge they let out of their internal software development activities. The results lay ground for further research on how to organize openness of the software development process in hybrid setups where the needs of different stakeholders are partly competing - yet complementary.},
	keywords = {Community Management, Hybrid open source, open source},
	doi = {10.1007/978-3-319-57735-7_3},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_3},
	author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and Mikkonen, Tommi and M{\"a}nnist{\"o}, Tomi}
}
@proceedings {1912,
	title = {Developer Turnover in Global, Industrial Open Source Projects: Insights from Applying Survival Analysis},
	year = {2017},
	note = {we study five industrial OSS projects of different
sizes (in terms of software size, contributors and number
of companies involved) and examine whether the duration
of developers staying in a project is related to following
four factors: (i) the time of first contribution, (ii) the rate of
maintaining own files, (iii) the main action type, and (iv) the
main job type

projects:
WikiMedia, OpenStack, GlusterFS from Red
Hat, Xen Project from the Linux Foundation and Apache
CloudStack},
	month = {05/2017},
	pages = {66-75},
	abstract = {Large open source software projects often have
a globally distributed development team. Studies have shown
developer turnover has a significant impact on the project success.
Frequent developer turnover may lead to loss of productivity due
to lacking relevant knowledge and spending extra time learning
how projects work. Thus, lots of attention has been paid to which
factors are related to developer retention; however, few of them
focus on the impact of activities of individual developers.
In this paper, we study five open source projects from
different organizations and examine whether developer turnover
is affected by when they start contributing and what types of
contributions they are making. Our study reveals that developers
have higher chances to survive in software projects when they
1) start contributing to the project earlier; 2) mainly modify
instead of creating files; 3) mainly code instead of dealing with
documentations. Our results also shed lights on the potential
approaches to improving developer retention.},
	keywords = {survival analysis},
	author = {Bin Lin and Gregorio Robles and Serebrenik, Alexander}
}
@article {1924,
	title = {Developers, Quality Control and Download Volume in Open Source Software (OSS) Projects},
	journal = {Journal of Organizational and End User Computing},
	volume = {29},
	year = {2017},
	month = {04/2017},
	pages = {43 - 66},
	abstract = {The open-source software (OSS) movement is often analogized as a commons, where products are developed by and consumed in an open community. However, does a larger commons automatically beget success or does the phenomenon fall prey to the tragedy of the commons? This research forwards and empirically investigates the curvilinear relationship between developers and OSS project quality and a project{\textquoteright}s download volume. Using segmented regression on over 12,000 SourceForge OSS projects, findings suggest an inflection point in the number of contributing developers on download volume {\textendash} suggesting increasing and diminishing returns to scale from adding developers to OSS projects. Findings support the economic principle of the tragedy of the commons, a concept where an over-allocated (large number) of developers, even in an open-source environment, can lead to resource mismanagement and reduce the benefit of a public good, i.e. the OSS project.
},
	issn = {1546-5012},
	doi = {10.4018/JOEUC.2017040103},
	author = {Hill, Geoffrey and Datta, Pratim and Vander Weerdt, Candice}
}
@proceedings {1894,
	title = {Digging into the Eclipse Marketplace},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {60-65},
	publisher = {Springer},
	abstract = {Eclipse is an integrated development environment that can be extended with plug-ins. Thanks to Eclipse{\textquoteright}s success, a diverse community has been established with members coming from industry, open-source projects, and others, and a marketplace with more than 1.700 different plug-ins developed. Hence, the question arises how this marketplace is composed: Who contributes plug-ins? Which plug-ins are successful? Are there common characteristics or trends? To answer these questions, extensive investigations are necessary. In this paper, we present (i) an initial approach for corresponding analyses and (ii) preliminary results. Overall, we aim to pave the way for further research addressing, for example, motivations to participate in, or the evolution of, open marketplaces.},
	keywords = {Eclipse IDE, Eclipse Marketplace, empirical study, open source},
	doi = {10.1007/978-3-319-57735-7_7},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_7},
	author = {Kr{\"u}ger, J and Corr, N and Schr{\"o}ter, I and Leich, T}
}
@proceedings {1907,
	title = {Do Software Developers Understand Open Source Licenses?},
	year = {2017},
	note = {Data: We report on the results of a survey that asked
developers about 42 different cases of the use of code under
different open source licenses. To make the survey tractable
for developers to answer, we focused on three popular open
source licenses (GNU GPL 3.0, GNU LGPL 3.0 and MPL
2.0)

Findings: The survey results indicate that most of the 375 respondents
to our survey struggle with understanding the interaction of
open source licenses in both simple and complex software
development cases},
	month = {05/2017},
	pages = {1-11},
	abstract = {{\textemdash}Software provided under open source licenses is
widely used, from forming high-profile stand-alone applications
(e.g., Mozilla Firefox) to being embedded in commercial offerings
(e.g., network routers). Despite the high frequency of use of open
source licenses, there has been little work about whether software
developers understand the open source licenses they use. To our
knowledge, only one survey has been conducted, which focused
on which licenses developers choose and when they encounter
problems with licensing open source software. To help fill the
gap of whether or not developers understand the open source
licenses they use, we conducted a survey that posed development
scenarios involving three popular open source licenses (GNU GPL
3.0, GNU LGPL 3.0 and MPL 2.0) both alone and in combination.
The 375 respondents to the survey, who were largely developers,
gave answers consistent with those of a legal expert{\textquoteright}s opinion in
62\% of 42 cases. Although developers clearly understood cases
involving one license, they struggled when multiple licenses were
involved. An analysis of the quantitative and qualitative results of
the study indicate a need for tool support to help guide developers
in understanding this critical information attached to software
components.},
	keywords = {license, Survey},
	doi = {10.1109/ICPC.2017.7},
	author = {Almeida, Daniel A. and Murphy, Gail C. and Wilson, Greg and Hoye, Mike}
}
@proceedings {1824,
	title = {Data Sets: The Circle of Life in Ruby Hosting, 2003-2015},
	year = {2016},
	month = {05/2016},
	pages = {452-455},
	publisher = {IEEE},
	abstract = {Studying software repositories and hosting services can provide valuable insights into the behaviors of large groups of software developers and their projects. Traditionally, most analysis of metadata collected from hosting services has been conducted by specifying some short window of time, typically just a few years. To date, few - if any - studies have been built from data comprising the entirety of a repository{\textquoteright}s lifespan: from its birth to its death, and rebirth. Thus, the first contribution of this data set is to support the historical analysis of over ten years of collected metadata from the now-defunct RubyForge project hosting site, as well as the follow-on successor to RubyForge, the RubyGems hosting facility. The data sets and sample analyses in this paper will be relevant to researchers studying both software evolution and the distributed software development process.},
	url = {https://docs.google.com/presentation/d/1rtdrwkfxt-p5gQBwMNT1WDlLMg0pJ4gxfM5jSAH-UUA/edit?usp=sharing},
	attachments = {https://flosshub.org/sites/flosshub.org/files/preprint.pdf},
	author = {Squire, Megan}
}
@article {1861,
	title = {The Debsources Dataset: two decades of free and open source software},
	journal = {Empirical Software Engineering},
	year = {2016},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {We present the Debsources Dataset: distribution metadata and source code metrics spanning two decades of Free and Open Source Software (FOSS) history, seen through the lens of the Debian distribution. Debsources is a software platform used to gather, search, and publish on the Web the full source code of the Debian operating system, as well as measures about it. A notable public instance of Debsources is available at http://sources.debian.net, it includes both current and historical releases of Debian. Plugins to compute popular source code metrics (lines of code, defined symbols, disk usage) and other derived data (e.g., Checksums) have been written, integrated, and run on all the source code available on sources.debian.net. The Debsources Dataset is a PostgreSQL database dump of sources.debian.net metadata, as of February 10th, 2015. The dataset contains both Debian-specific metadata -- e.g., which software packages are available in which release, which source code file belong to which package, release dates, etc. -- and source code information gathered by running Debsources plugins. The Debsources Dataset offer a very long-term historical view of the macro-level evolution and constitution of FOSS through the lens of popular, representative FOSS projects of their times.},
	keywords = {debian, metadata, postgresql},
	issn = {1573-7616},
	doi = {10.1007/s10664-016-9461-5},
	url = {https://matthieu.io/dl/papers/debsources-ese-2016.pdf},
	author = {Caneill, Matthieu and Daniel M. Germ{\'a}n and Zacchiroli, Stefano}
}
@proceedings {1854,
	title = {Differentiating Communication Styles of Leaders on the Linux Kernel Mailing List},
	year = {2016},
	note = {Slides link: https://docs.google.com/presentation/d/1_5kqOXBYwH33ayfGKCncCtCondfUYtsHSDBS3DBig6Y/edit?usp=sharing
Edited to fix typo in abstract. New version is v3.pdf},
	month = {08/2016},
	publisher = {ACM},
	abstract = {Much communication between developers of free, libre, and open source software (FLOSS) projects happens on email mailing lists. Geographically and temporally dispersed development teams use email as an asynchronous, centralized, persistently stored institutional memory for sharing code samples, discussing bugs, and making decisions. Email is especially important to large, mature projects, such as the Linux kernel, which has thousands of developers and a multi-layered leadership structure. In this paper, we collect and analyze data to understand the communication patterns in such a community. How do the leaders of the Linux Kernel project write in email? What are the salient features of their writing, and can we discern one leader from another? We find that there are clear written markers for two leaders who have been particularly important to recent discussions of leadership style on the Linux Kernel Mailing List (LKML): Linux Torvalds and Greg Kroah-Hartman. Furthermore, we show that it is straightforward to use a machine learning strategy to automatically differentiate these two leaders based on their writing. Our findings will help researchers understand how this community works, and why there is occasional controversy regarding differences in communication styles on the LKML.},
	keywords = {email, flossmole, linus torvalds, linux, lkml},
	attachments = {https://flosshub.org/sites/flosshub.org/files/v3_0.pdf},
	author = {Schneider, Daniel and Spurlock, Scott and Squire, Megan}
}
@proceedings {1866,
	title = {Does the Task Structure of Open Source Projects Matter? Superposition and Value Creation},
	year = {2016},
	month = {11/2016},
	publisher = {AIS},
	abstract = {Collaboration through open superposition describes a process of building free (libre) and open source software (FLOSS), wherein motivationally independent layers of work is sequentially added one-on-top the other over time. This research-in-progress paper theorizes the mechanisms through which superposition influences the value of individual and organizational owned FLOSS projects. We argue for a non-linear relationship between degree of superposition and value of the FLOSS project. Moreover, we posit that the type of ownership will moderate this non-linear relationship. The moderation effect is such that {\textendash} (1) organizational ownership mitigates the influence of degree of superposition on project value (2) under organizational ownership, the optimal value of degree of superposition (the point at which the project value is maximum) is lower as compared to individual owned projects. This research attempts to advance the theory of superposition and unearth the influence of task structure on the value of the FLOSS project.},
	author = {Poonacha K. Medappa and Shirish C. Srivastava}
}
@proceedings {1710,
	title = {Data Mining Behavioral Transitions in Open Source Repositories},
	year = {2015},
	pages = {5280-5289},
	publisher = {IEEE},
	abstract = {Open-source repository data can be automatically mined
using sequence mining methods to provide high-level
feedback on project status. GitHub.com projects are
acquired, sequence-mined, clustered, and regressed to
analyze project characteristics. Such results can be presented
to project managers, as part of a display generated by an
automated monitoring system. Such monitoring systems
provide high-level feedback in real-time. This project is a
preliminary step in a larger research project aimed at
understanding and monitoring FLOSS projects using this
process modeling approach. },
	author = {Robinson, William and Tianjie Deng}
}
@proceedings {1762,
	title = {A Data Set for Social Diversity Studies of GitHub Teams},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Like any other team oriented activity, the software
development process is effected by social diversity in the programmer
teams. The effect of team diversity can be significant,
but also complex, especially in decentralized teams. Discerning
the precise contribution of diversity on teams{\textquoteright} effectiveness
requires quantitative studies of large data sets.
Here we present for the first time a large data set of social
diversity attributes of programmers in GITHUB teams. Using
alias resolution, location data, and gender inference techniques,
we collected a team social diversity data set of 23,493 GITHUB
projects. We illustrate how the data set can be used in practice
with a series of case studies, and we hope its availability will foster
more interest in studying diversity issues in software teams.},
	keywords = {ghtorrent, github},
	url = {http://www.win.tue.nl/~aserebre/cr-msr-data-15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cr-msr-data-15.pdf},
	author = {Vasilescu, Bogdan and Serebrenik, Alexander and Filkov, Vladimir}
}
@proceedings {1760,
	title = {A Dataset For API Usage},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {An Application Programming Interface (API) provides
a specific set of functionalities to a developer. The main aim
of an API is to encourage the reuse of already existing functionality.
There has been some work done into API popularity trends,
API evolution and API usage. For all the aforementioned research
avenues there has been a need to mine the usage of an API in
order to perform any kind of analysis. Each one of the approaches
that has been employed in the past involved a certain degree
of inaccuracy as there was no type check that takes place. We
introduce an approach that takes type information into account
while mining API method invocations and annotation usages.
This approach accurately makes a connection between a method
invocation and the class of the API to which the method belongs
to. We try collecting as many usages of an API as possible, this
is achieved by targeting projects hosted on GitHub. Additionally,
we look at the history of every project to collect the usage of an
API from earliest version onwards. By making such a large and
rich dataset public, we hope to stimulate some more research in
the field of APIs with the aid of accurate API usage samples.},
	url = {http://sback.it/publications/msr2015data.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015data.pdf},
	author = {Anand Ashok Sawant and Bacchelli, Alberto}
}
@proceedings {1763,
	title = {A Dataset of High Impact Bugs: Manually-Classified Issue Reports},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The importance of supporting test and maintenance
activities in software development has been increasing, since
recent software systems have become large and complex. Although
in the field of Mining Software Repositories (MSR) there
are many promising approaches to predicting, localizing, and
triaging bugs, most of them do not consider impacts of each
bug on users and developers but rather treat all bugs with equal
weighting, excepting a few studies on high impact bugs including
security, performance, blocking, and so forth. To make MSR
techniques more actionable and effective in practice, we need
deeper understandings of high impact bugs. In this paper we
introduced our dataset of high impact bugs which was created
by manually reviewing four thousand issue reports in four open
source projects (Ambari, Camel, Derby and Wicket).},
	keywords = {ambari, camel, derby, wicket},
	url = {http://oss.sys.wakayama-u.ac.jp/publications/pman3.cgi?DOWNLOAD=141},
	attachments = {https://flosshub.org/sites/flosshub.org/files/5594a518.pdf},
	author = {Ohira, Masao and Yutaro Kashiwa and Yosuke Yamatani and Hayato Yoshiyuki and Yoshiya Maeda and Nachai Limsettho and Keisuke Fujino and Hata, Hideaki and Ihara, Akinori and Kenichi Matsumoto}
}
@proceedings {1758,
	title = {A Dataset of the Activity of the git Super-repository of Linux in 2012},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {This dataset documents the activity in the public
portion of the git Super-repository of the Linux kernel during
2012. In a distributed version control system, such as git, the
Super-repository is the collection of all the repositories (repos)
used for development. In such a Super-repository, some repos
will be accessible only by their owners (they are private, and
are located in places that are unreachable to other users) while
others are available to other members of the team. The latter
public repositories are used as avenues through which commits
flow from one developer to another. During the last six weeks of
2011, we proceeded to automatically discover the public portion
of the Super-repository of Linux. Then, in 2012, every 3 hrs,
each of these public repositories was queried to see what new
commits it had and what commits had disappeared from it
using a process we call continuous mining. This resulted in the
identification of 533,513 different commits across 451 different
public repositories and how they propagated through the Linux
Super-repository, including the repository of Linus Torvalds (i.e.,
the main repository of the Linux kernel). This information could
help us understand how kernel contributors use git, how they
collaborate and how commits are integrated into the Linux kernel
and into the repositories of organizations that distribute the
kernel.
This dataset is at http://turingmachine.org/2015/linuxGit},
	url = {http://turingmachine.org/2015/linuxGit/msr-data-git-linux.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr-data-git-linux.pdf},
	author = {Daniel M. German and Adams, Bram and Hassan, Ahmed E.}
}
@proceedings {1757,
	title = {The Debsources Dataset: Two Decades of Debian Source Code Metadata},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {We present the Debsources Dataset: distribution
metadata and source code metrics spanning two decades of Free
and Open Source Software (FOSS) history, seen through the lens
of the Debian distribution.
Debsources is a software platform used to gather, search, and
publish on the Web the full source code of the Debian operating
system, as well as measures about it. A notable public instance
of Debsources is available at http://sources.debian.net; it includes
both current and historical releases of Debian. Plugins to compute
popular source code metrics (lines of code, defined symbols,
disk usage) and other derived data (e.g., checksums) have been
written, integrated, and run on all the source code available on
sources.debian.net.
The Debsources Dataset is a PostgreSQL database dump
of sources.debian.net metadata, as of February 10th, 2015.
The dataset contains both Debian-specific metadata{\textemdash}e.g., which
software packages are available in which release, which source
code file belong to which package, release dates, etc.{\textemdash}and source
code information gathered by running Debsources plugins.
The Debsources Dataset offer a very long-term historical view
of the macro-level evolution and constitution of FOSS through
the lens of popular, representative FOSS projects of their times.},
	keywords = {debian},
	url = {https://upsilon.cc/~zack/research/publications/debsources-msr-2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/debsources-msr-2015.pdf},
	author = {Zacchiroli, Stefano}
}
@proceedings {1722,
	title = {The diffusion of pastebin tools to enhance communication in FLOSS mailing lists},
	year = {2015},
	month = {05/2015},
	pages = {45-57},
	abstract = {This paper describes how software developers who use mailing lists to communicate reacted and adjusted to a new supplementary collaboration tool, called a pastebin service. Using publicly-available archives of 8800 mailing lists, we examine the adoption of the pastebin tool by software developers and compare it to the model presented in Diffusion of Innovation (DoI) theory. We then compare the rate at which software developers decided whether to accept or reject the new pastebin tools. We find that the overall rate of pastebin adoption follows the S-curve predicted by classic DoI theory. We then compare the individual pastebin services and their rates of adoption, as well as the reaction of different communities to the new tools and the various rationales for accepting or rejecting them.},
	doi = {http://dx.doi.org/10.1007/978-3-319-17837-0_5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/pastebinOSS2015Preprint.pdf},
	author = {Squire, Megan and Smith, Amber}
}
@mastersthesis {1773,
	title = {Do Bugs Foreshadow Vulnerabilities? A Study of the Chromium Project},
	year = {2015},
	type = {Thesis},
	address = {Rochester Institute of Technology},
	abstract = {As developers face ever-increasing pressure to engineer secure software, researchers are building an understanding of security-sensitive bugs (i.e. vulnerabilities). Research into mining software repositories has greatly increased our understanding of software quality via empirical study of bugs. However, conceptually vulnerabilities are different from bugs: they represent abusive functionality as opposed to wrong or insufficient functionality commonly associated with traditional, non-security bugs. In this study, we performed an in-depth analysis of the Chromium project to empirically examine the relationship between bugs and vulnerabilities. We mined 374,686 bugs and 703 post-release vulnerabilities over five Chromium releases that span six years of development. Using logistic regression analysis, we examined how various categories of pre-release bugs and review experiences (e.g. stability, compatibility, etc.) are associated with post-release vulnerabilities. While we found statistically significant correlations between our metrics and post-release vulnerabilities, we also found the association to be weak. Number of features, SLOC, and number of pre-release security bugs are, in general, more closely associated with post-release vulnerabilities than any of our non-security bug categories. In a separate analysis, we found that the files with highest defect density did not intersect with the files of highest vulnerability density. These results indicate that bugs and vulnerabilities are empirically dissimilar groups, warranting the need for more research targeting vulnerabilities specifically.},
	url = {http://scholarworks.rit.edu/theses/8695/},
	author = {Felivel Camilo}
}
@conference {Saini:2014:DMA:2597073.2597134,
	title = {A Dataset for Maven Artifacts and Bug Patterns Found in Them},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {416{\textendash}419},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper, we present data downloaded from Maven, one of the most popular component repositories. The data includes the binaries of 186,392 components, along with source code for 161,025. We identify and organize these components into groups where each group contains all the versions of a library. In order to asses the quality of these components, we make available report generated by the FindBugs tool on 64,574 components. The information is also made available in the form of a database which stores total number, type, and priority of bug patterns found in each component, along with its defect density. We also describe how this dataset can be useful in software engineering research.
},
	keywords = {Empirical Research, Empirical software engineering, findbugs, maven, software quality},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597134},
	url = {http://doi.acm.org/10.1145/2597073.2597134},
	author = {Saini, Vaibhav and Sajnani, Hitesh and Ossher, Joel and Lopes, Cristina V.}
}
@conference {Gousios:2014:DPD:2597073.2597122,
	title = {A Dataset for Pull-based Development Research},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {368{\textendash}371},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Pull requests form a new method for collaborating in distributed software development. To study the pull request distributed development model, we constructed a dataset of almost 900 projects and 350,000 pull requests, including some of the largest users of pull requests on Github. In this paper, we describe how the project selection was done, we analyze the selected features and present a machine learning tool set for the R statistics environment.
},
	keywords = {Distributed software development, Empirical software engineering, msr data showcase, pull request, pull-based development},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597122},
	url = {http://doi.acm.org/10.1145/2597073.2597122},
	attachments = {https://flosshub.org/sites/flosshub.org/files/pullreqs-dataset.pdf},
	author = {Gousios, Georgios and Zaidman, Andy}
}
@conference {Passos:2014:DFA:2597073.2597124,
	title = {A Dataset of Feature Additions and Feature Removals from the Linux Kernel},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {376{\textendash}379},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {This paper describes a dataset of feature additions and removals in the Linux kernel evolution history, spanning over seven years of kernel development. Features, in this context, denote configurable system options that users select when creating customized kernel images. The provided dataset is the largest corpus we are aware of capturing feature additions and removals, allowing researchers to assess the kernel evolution from a feature-oriented point-of-view. Furthermore, the dataset can be used to better understand how features evolve over time, and how different artifacts change as a result. One particular use of the dataset is to provide a real-world case to assess existing support for feature traceability and evolution. In this paper, we detail the dataset extraction process, the underlying database schema, and example queries. The dataset is directly available at our Bitbucket repository: https://bitbucket.org/lpassos/kconfigdb
},
	keywords = {evolution, linux, msr data showcase, Traceability, Version Control History},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597124},
	url = {http://doi.acm.org/10.1145/2597073.2597124},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kernel.pdf},
	author = {Passos, Leonardo and Czarnecki, Krzysztof}
}
@conference {Brunet:2014:DDD:2597073.2597115,
	title = {Do Developers Discuss Design?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {340{\textendash}343},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Design is often raised in the literature as important to attaining various properties and characteristics in a software system. At least for open-source projects, it can be hard to find evidence of ongoing design work in the technical artifacts produced as part of the development. Although developers usually do not produce specific design documents, they do communicate about design in different ways. In this paper, we provide quantitative evidence that developers address design through discussions in commits, issues, and pull requests. To achieve this, we built a discussions{\textquoteright} classifier and automatically labeled 102,122 discussions from 77 projects. Based on this data, we make four observations about the projects: i) on average, 25\% of the discussions in a project are about design; ii) on average, 26\% of developers contribute to at least one design discussion; iii) only 1\% of the developers contribute to more than 15\% of the discussions in a project; and iv) these few developers who contribute to a broad range of design discussions are also the top committers in a project.
},
	keywords = {Design Discussions, empirical study, machine learning, mining challenge, msr challenge},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597115},
	url = {http://doi.acm.org/10.1145/2597073.2597115},
	attachments = {https://flosshub.org/sites/flosshub.org/files/brunet.pdf},
	author = {Brunet, Jo{\~a}o and Murphy, Gail C. and Terra, Ricardo and Figueiredo, Jorge and Serey, Dalton}
}
@conference {Murgia:2014:DFE:2597073.2597086,
	title = {Do Developers Feel Emotions? An Exploratory Analysis of Emotions in Software Artifacts},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {262{\textendash}271},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software development is a collaborative activity in which developers interact to create and maintain a complex software system. Human collaboration inevitably evokes emotions like joy or sadness, which can affect the collaboration either positively or negatively, yet not much is known about the individual emotions and their role for software development stakeholders. In this study, we analyze whether development artifacts like issue reports carry any emotional information about software development. This is a first step towards verifying the feasibility of an automatic tool for emotion mining in software development artifacts: if humans cannot determine any emotion from a software artifact, neither can a tool. Analysis of the Apache Software Foundation issue tracking system shows that developers do express emotions (in particular gratitude, joy and sadness). However, the more context is provided about an issue report, the more human raters start to doubt and nuance their interpretation of emotions. More investigation is needed before building a fully automatic emotion mining tool.
},
	keywords = {Emotion Mining, Empirical Software Engineer- ing, Issue Report},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597086},
	url = {http://doi.acm.org/10.1145/2597073.2597086},
	attachments = {https://flosshub.org/sites/flosshub.org/files/murgia.pdf},
	author = {Murgia, Alessandro and Tourani, Parastou and Adams, Bram and Ortu, Marco}
}
@inbook {1611,
	title = {Does Contributor Characteristics Influence Future Participation? A Case Study on Google Chromium Issue Tracking System},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {164-167},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Understanding and measuring factors influencing future participation is relevant to organizations. This information is useful for planning and strategic decision-making. In this work, we measure contributor characteristics and compute attrition to investigate their relationship by mining Issue Tracking System. We conduct experiments on four year data extracted from Google Chromium Issue Tracking System. Experimental results show that the likelihood of future participation increases with increase in relevance of role in project and level of participation in previous time-interval.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_22},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_22},
	author = {Rastogi, Ayushi and Sureka, Ashish},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@book {1590,
	title = {Drawing the Big Picture: Temporal Visualization of Dynamic Collaboration Graphs of OSS Software Forks},
	series = {10th IFIP WG 2.13 International Conference on Open Source Systems, OSS 2014, San Jos{\'e}, Costa Rica, May 6-9, 2014. Proceedings},
	volume = {427},
	year = {2014},
	pages = {41 - 50},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {How can we understand FOSS collaboration better? Can social issues that emerge be identified and addressed as they happen? Can the community heal itself, become more transparent and inclusive, and promote diversity? We propose a technique to address these issues by quantitative analysis and temporal visualization of social dynamics in FOSS communities. We used social network analysis metrics to identify growth patterns and unhealthy dynamics; This gives the community a heads-up when they can still take action to ensure the sustainability of the project.},
	isbn = {978-3-642-55128-4},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-55128-4_5},
	author = {Amir Azarbakht and Jensen, Carlos},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, Anthony I.}
}
@conference {Rozas:2014:DCP:2641580.2641624,
	title = {Drupal As a Commons-Based Peer Production Community: A Sociological Perspective},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {36:1{\textendash}36:2},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The aim of this research consists of extracting a set of insights related to the dynamics, group decision making procedures, motivations to contribute and mechanisms employed in the coordination of Commons-Based Peer Production communities, using as a case study the community responsible for the development of the Free/Libre Open Source Software Drupal. A sociological perspective is taken for this purpose, and a set of social research qualitative and quantitative methods employed for the study of online communities (virtual ethnography) are being used.
},
	keywords = {Activity Theory, Commons-Based Peer Production, drupal, Free/Libre Open Source Software, Virtual Ethnography},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641624},
	url = {http://doi.acm.org/10.1145/2641580.2641624},
	author = {Rozas, David}
}
@proceedings {1502,
	title = {A Dataset from Change History to Support Evaluation  of Software Maintenance Tasks},
	year = {2013},
	month = {05/2013},
	pages = {131-134},
	abstract = {Approaches that support software maintenance need 
to be evaluated and compared against existing ones, in order to 
demonstrate their usefulness in practice. However, oftentimes the 
lack of well-established sets of benchmarks leads to situations 
where these approaches are evaluated using different datasets, 
which results in biased comparisons. In this data paper we 
describe and make publicly available a set of benchmarks from 
six Java applications, which can be used in the evaluation of 
various software engineering (SE) tasks, such as feature location 
and impact analysis. These datasets consist of textual description 
of change requests, the locations in the source code where they 
were implemented, and execution traces. Four of the benchmarks 
were already used in several SE research papers, and two of them 
are new. In addition, we describe in detail the methodology used 
for generating these benchmarks and provide a suite of tools in 
order to encourage other researchers to validate our datasets and 
generate new benchmarks for other subject software systems. 
Our online appendix: http://www.cs.wm.edu/semeru/data/msr13/ },
	url = {http://www.cs.wm.edu/~bdit/publications/MSR13DataPaper_Dit_CRC.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MSR13DataPaper_Dit_CRC.pdf},
	author = {Bogdan Dit and Andrew Holtzhauer and Poshyvanyk, Denys and Kagdi, Huzefa}
}
@proceedings {1512,
	title = {Discovering, Reporting, and Fixing Performance Bugs},
	year = {2013},
	month = {05/2013},
	abstract = {Software performance is critical for how users perceive the quality of software products. Performance bugs---programming errors that cause significant performance degradation---lead to poor user experience and low system throughput. Designing effective techniques to address performance bugs requires a deep understanding of how performance bugs are discovered, reported, and fixed. In this paper, we study how performance bugs are discovered, reported to developers, and fixed by developers, and compare the results with those for non-performance bugs. We study performance and non-performance bugs from three popular code bases: Eclipse JDT, Eclipse SWT, and Mozilla. First, we find little evidence that fixing performance bugs has a higher chance to introduce new functional bugs than fixing non-performance bugs, which implies that developers may not need to be overconcerned about fixing performance bugs. Second, although fixing performance bugs is about as error-prone as fixing nonperformance bugs, fixing performance bugs is more difficult than fixing non-performance bugs, indicating that developers need better tool support for fixing performance bugs and testing performance bug patches. Third, unlike many non-performance bugs, a large percentage of performance bugs are discovered through code reasoning, not through users observing the negative effects of the bugs (e.g., performance degradation) or through profiling. The result suggests that techniques to help developers reason about performance, better test oracles, and better profiling techniques are needed for discovering performance bugs.},
	keywords = {bugs, eclipse, mozilla, performance bugs},
	author = {Adrian Nistor and Tian Jiang and Tan, Lin}
}
@conference {Venkataramani:2013:DTE:2487788.2487832,
	title = {Discovery of Technical Expertise from Open Source Code Repositories},
	booktitle = {Proceedings of the 22Nd International Conference on World Wide Web Companion},
	series = {WWW {\textquoteright}13 Companion},
	year = {2013},
	pages = {97{\textendash}98},
	publisher = {International World Wide Web Conferences Steering Committee},
	organization = {International World Wide Web Conferences Steering Committee},
	address = {Republic and Canton of Geneva, Switzerland},
	abstract = {Online Question and Answer websites for developers have emerged as the main forums for interaction during the software development process. The veracity of an answer in such websites is typically verified by the number of {\textquoteright}upvotes{\textquoteright} that the answer garners from peer programmers using the same forum. Although this mechanism has proved to be extremely successful in rating the usefulness of the answers, it does not lend itself very elegantly to model the expertise of a user in a particular domain. In this paper, we propose a model to rank the expertise of the developers in a target domain by mining their activity in different opensource projects. To demonstrate the validity of the model, we built a recommendation system for StackOverflow which uses the data mined from GitHub.
},
	keywords = {github, knowledge discovery, recommendations, source code repository, stackoverflow, technical expertise},
	isbn = {978-1-4503-2038-2},
	url = {http://dl.acm.org/citation.cfm?id=2487788.2487832},
	author = {Venkataramani, Rahul and Gupta, Atul and Asadullah, Allahbaksh and Muddu, Basavaraju and Bhat, Vasudev}
}
@proceedings {1494,
	title = {Do Software Categories Impact Coupling Metrics?},
	year = {2013},
	month = {05/2013},
	pages = {217-220},
	abstract = {Software metrics is a valuable mechanism to assess
the quality of software systems. Metrics can help the automated
analysis of the growing data available in software repositories.
Coupling metrics is a kind of software metrics that have been
extensively used since the seventies to evaluate several software
properties related to maintenance, evolution and reuse tasks. For
example, several works have shown that we can use coupling
metrics to assess the reusability of software artifacts available in
repositories. However, thresholds for software metrics to indicate
adequate coupling levels are still a matter of discussion. In this
paper, we investigate the impact of software categories on the
coupling level of software systems. We have found that different
categories may have different levels of coupling, suggesting that
we need special attention when comparing software systems in
different categories and when using predefined thresholds
already available in the literature.
},
	url = {http://www.facom.ufu.br/~marcmaia/preprints/msr13-SouzaMaia-CategoriesAndCoupling.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr13-SouzaMaia-CategoriesAndCoupling.pdf},
	author = {Lucas Batista Leite de Souza and Marcelo de Almeida Maia}
}
@book {1546,
	title = {A Dual Model of Open Source License Growth},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	note = {uses ohloh snapshot, march 2008},
	pages = {245 - 256},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Every open source project needs to decide on an open source license. This decision is of high economic relevance: Just which license is the best one to help the project grow and attract a community? The most common question is: Should the project choose a restrictive (reciprocal) license or a more permissive one? As an important step towards answering this question, this paper analyses actual license choice and correlated project growth from ten years of open source projects. It provides closed analytical models and finds that around 2001 a reversal in license choice occurred from restrictive towards permissive licenses.
},
	keywords = {ohloh},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/oss2013.hofmann.pdf},
	author = {Hofmann, Gottfried and Dirk Riehle and Carsten Kolassa and Mauerer, Wolfgang},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@conference {1317,
	title = {Describing the Software Forge Ecosystem},
	booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences},
	year = {2012},
	note = {http://flossmole.org/content/everything-you-ever-wanted-know-about-software-forges-code-forges-june-2011},
	month = {01/2012},
	pages = {3416-3425},
	abstract = {Code forges are online software systems that are designed to support teams doing software development work. There have been few if any attempts in the research literature to describe the web of people, projects, and tools that make up the free, libre, and open source (FLOSS) forge ecosystem. The main contributions of this paper are (1) to introduce a classification of FLOSS-oriented forges according to their characteristics; (2) to describe the forge-level and project-level data and artifacts currently available at each FLOSS forge; (3) to show various patterns already discovered in the FLOSS forge ecosystem, such as timelines of creation or arrangements by size or feature; (4) to make some recommendations to forge providers and data collectors about how to expose the structure and information in the forges; and (5) to describe the effort needed to extend our publicly- available information about the FLOSS forge ecosystem into the future.},
	keywords = {features, FLOSS, forge, hosting, metrics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/SquireWilliamsHICSS2012.pdf},
	author = {Squire, Megan and Williams, David}
}
@proceedings {1448,
	title = {Designing Secure Systems Based on Open Architectures with Open Source and Closed Source Components},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {144-159},
	abstract = {The development and evolution of secure open architecture systems has received insufficient consideration. Such systems are composed of both open source and closed software software components subject to different security requirements in an architecture in which evolution can occur by evolving existing components, replacing them, or refactoring their interfaces, interconnections and configuration. But this may result in possible security requirements conflicts and organizational liability for failure to fulfill security obligations. We are developing an approach for understanding and modeling software security requirements as security licenses, as well as for analyzing conflicts among groups of such licenses in realistic system contexts and for guiding the acquisition, integration, or development of systems with open source components in such an environment. Consequently, this paper reports on our efforts to extend our existing approach to specifying and analyzing software Intellectual Property (IP) licenses to now address software security licenses that can be associated with secure OA systems.},
	author = {Walt Scacchi and Alspaugh, Thomas}
}
@conference {1680,
	title = {Developing an h-index for OSS developers},
	booktitle = {2012 9th IEEE Working Conference on Mining Software Repositories (MSR)},
	year = {2012},
	pages = {251 - 254},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Zurich},
	abstract = {The public data available in Open Source Software (OSS) repositories has been used for many practical reasons: detecting community structures; identifying key roles among developers; understanding software quality; predicting the arousal of bugs in large OSS systems, and so on; but also to formulate and validate new metrics and proof-of-concepts on general, non-OSS specific, software engineering aspects. One of the results that has not emerged yet from the analysis of OSS repositories is how to help the {\textquotedblleft}career advancement{\textquotedblright} of developers: given the available data on products and processes used in OSS development, it should be possible to produce measurements to identify and describe a developer, that could be used externally as a measure of recognition and experience. This paper builds on top of the h-index, used in academic contexts, and which is used to determine the recognition of a researcher among her peers. By creating similar indices for OSS (or any) developers, this work could help defining a baseline for measuring and comparing the contributions of OSS developers in an objective, open and reproducible way.},
	isbn = {978-1-4673-1760-3},
	doi = {10.1109/MSR.2012.6224288},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MSR2012.pdf},
	author = {A. Capiluppi and Serebrenik, A. and Youssef, A.}
}
@proceedings {1475,
	title = {Discussion on the Problems to be Solved toward the Migration to OSS Productivity Software in the Business Enterprises},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {377-382},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {In recent years, there is a tendency to migrate from proprietary productivity software to open-source productivity software, especially in government offices and municipal offices. ODPG (OpenOffice.org \& OpenDocument Format Promotion Group, Japan) is an organization founded in order to promote the migration to the OSS productivity software in private enterprises as well. In the case evaluation work group of ODPG, business solutions about use of OpenOffice.org have been discussed many times, for the purpose of supporting the migration to OpenOffice.org, by collecting and feeding back the information of case studies useful for the member companies. This paper reports several subjects and solutions, such as promotion strategy for OpenOffice.org to be widely used, the problem in file exchange with the other stakeholders, preparation of use environment, and security issues, which were discussed in the work group.},
	author = {Iio, Jun and Ogawa, Tomotaka}
}
@proceedings {1458,
	title = {Do More Experienced Developers Introduce Fewer Bugs?},
	volume = {378},
	year = {2012},
	note = {"Some Mozilla Foundation projects have been the selected case of study for this paper. The analysis is based on the Mercurial repository which offers a list of repositories that can be easily cloned. As a summary, 19 projects were analyzed, with more than 100,000 commits, more than 2,500 authors and around 4 years of history up to June 2011."},
	month = {09/2012},
	pages = {268-273},
	publisher = {IFIP AICT,  Springer},
	abstract = {Developer experience is a common matter of study in the software maintenance and evolution research literature. However it is still not well understood if less experienced developers are more prone to introduce errors in the source code than their more experienced colleagues. This paper aims to study the relationships between experience and the bug introduction ratio using the Mozilla community as case of study.
As results, statistical differences among developers with different levels of experience has not been observed, when the expected result would have been the opposite1.},
	keywords = {mercurial, mozilla, scm, source code analysis},
	author = {Izquierdo-Cort{\'a}zar, Daniel and Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M.}
}
@proceedings {1462,
	title = {Does OSS Affect E-Government Growth? An Econometric Analysis on the Impacting Factors},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {292-297},
	publisher = {IFIP AICT,  Springer},
	abstract = {Inspired by the OSS values, an increasing number of different forms of open initiatives have come to the fore. In the context of eGovernment the notion of open government has met wide acceptance among nations and became closely related to one of its goals. Open government shares with OSS the notions of collaboration, participation and transparency and many actions towards OSS into eGovernment reform policies, have been recorded worldwide. The study investigates the relationship between OSS growth and eGovernment. A theoretical framework of the theories of institutionalism, growth and human capital is proposed as the guiding theoretical lens to identify possible influencing factors that together with OSS are evaluated for their magnitude of impact on eGovernment growth across different economic environments.},
	keywords = {eGovernment adoption, growth theory, human capital theory, institutionalism},
	author = {Lakka, Spyridoula and Stamati, Teta and Martakos, Draculis}
}
@proceedings {1273,
	title = {Developing Architectural Documentation for the Hadoop Distributed File System},
	year = {2011},
	month = {10/2011},
	pages = {50-61},
	publisher = {Springer},
	abstract = {Many open source projects are lacking architectural documentation that describes the major pieces of the system, how they are structured, and how they interact. We have produced architectural documentation for the Hadoop Distributed File System (HDFS), a major open source project. This paper describes our process and experiences in developing this documentation. We illustrate the documentation we have produced and how it differs from existing documentation by describing the redundancy mechanisms used in HDFS for reliability.},
	author = {Bass, Len and Kazman, Rick and Ozkaya, Ipek}
}
@conference {1313,
	title = {Do comments explain codes adequately?},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {242-245},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Comment lines in the software source code include descriptions of codes, usage of codes, copyrights, unused codes, comments, and so on. It is required for comments to explain the content of written code adequately, since the wrong description in the comment may causes further bug and confusion in maintenance.

In this paper, we try to clarify a research question: "In which projects do comments describe the code adequately?" To answer this question, we selected the group 1 of mining challenge and used data obtained from Eclipse and Netbeans. Since it is difficult to answer the above question directly, we define the distance between codes and comments. By utilizing the fault-prone module prediction technique, we can answer the alternative question from the data of two projects. The result shows that Eclipse project has relatively adequate comments.},
	keywords = {comments, eclipse, msr challenge, netbeans, prediction},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985482},
	author = {Mizuno, Osamu and Hirata, Yukinao}
}
@conference {1309,
	title = {Do time of day and developer experience affect commit bugginess},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"we study the latest versions of the Linux kernel and PostgreSQL, which have 222,332 and 31,098 commits, respectively. We study the correlation between a commit{\textquoteright}s bugginess and the time of day of the commit, the day of week of the commit, and the experience and commit frequency of the commit authors. In addition, we study several other commit characteristics, such as comment-only fixes and bug lifetimes."},
	month = {05/2011},
	pages = {153-162},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Modern software is often developed over many years with hundreds of thousands of commits. Commit metadata is a rich source of social characteristics, including the commit{\textquoteright}s time of day and the experience and commit frequency of its author. The "bugginess" of a commit is also a critical property of that commit. In this paper, we investigate the correlation between a commit{\textquoteright}s social characteristics and its "bugginess"; such results can be very useful for software developers and software engineering researchers. For instance, developers or code reviewers might be well-advised to thoroughly verify commits that are more likely to be buggy. In this paper, we study the correlation between a commit{\textquoteright}s bugginess and the time of day of the commit, the day of week of the commit, and the experience and commit frequency of the commit authors. We survey two widely-used open source projects: the Linux kernel and PostgreSQL.

Our main findings include: (1) commits submitted between midnight and 4 AM (referred to as late-night commits) are significantly buggier and commits between 7 AM and noon are less buggy, implying that developers may want to double-check their own latenight commits; (2) daily-committing developers produce less-buggy commits, indicating that we may want to promote the practice of daily-committing developers reviewing other developers{\textquoteright} commits; and (3) the bugginess of commits versus day-of-week varies for different software projects.},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985464},
	author = {Tan, Lin and Lam, Patrick and Eyolfson, Jon}
}
@article {1330,
	title = {Data Mining User Activity in Free and Open Source Software (FOSS)/ Open Learning Management Systems},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {65 - 75},
	abstract = {Free and Open Source Software (FOSS)/Open Educational Systems development projects abound in higher education today. Many universities worldwide have adopted open source software like ATutor and Moodle as an alternative to commercial or homegrown systems. The move to open source learning management systems entails many special considerations, including usage analysis facilities. The tracking of users and their activities poses major technical and analytical challenges within web-based systems. This paper examines how user activity tracking challenges are met with data mining techniques, particularly web usage mining methods, in four different open learning management systems: ATutor, LON-CAPA, Moodle, and Sakai. As examples of data mining technologies adapted within widely used systems, they represent important first steps for moving educational data mining outside the research laboratory. Moreover, as examples of different open source development contexts, exemplify the potential for programmatic integration of data mining technology processes in the future. As open systems mature in the use of educational data mining, they move closer to the long-sought goal of achieving more interactive, personalized, adaptive learning environments online on a broad scale.},
	keywords = {data mining, education, student},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010010105},
	author = {McGrath, Owen}
}
@article {1328,
	title = {Developing a Dynamic and Responsive Online Learning Environment},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {32 - 48},
	abstract = {Charles Stuart University adopted the open source software, Sakai, as the foundation for the university{\textquoteright}s new, integrated Online Learning Environment. This study explores whether a pedagogical advantage exists in adopting such an open source learning management system. Research suggests that the community source approach to development of open source software has many inherent pedagogical advantages, but this paper examines whether this is due to the choice of open source software or simply having access to appropriate technology for learning and teaching in the 21st century. The author also addresses the challenges of the project management methodology and processes in the large-scale implementation of an open-source courseware management solution at the institutional level. Consequently, this study outlines strategies that an institution can use to harness the potential of a community source approach to software development to meet the institutional and individual user needs into the future. },
	keywords = {education, learning, sakai},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010010103},
	author = {Buchan, Janet}
}
@conference {961,
	title = {Do stack traces help developers fix bugs?},
	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 = {118 - 121},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {A widely shared belief in the software engineering community is that stack traces are much sought after by developers to support them in debugging. But limited empirical evidence is available to confirm the value of stack traces to developers. In this paper, we seek to provide such evidence by conducting an empirical study on the usage of stack traces by developers from the ECLIPSE project. Our results provide strong evidence to this effect and also throws light on some of the patterns in bug fixing using stack traces. We expect the findings of our study to further emphasize the importance of adding stack traces to bug reports and that in the future, software vendors will provide more support in their products to help general users make such information available when filing bug reports.},
	keywords = {bug fixing, bug report, debugging, eclipse, stack trace},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463280},
	attachments = {https://flosshub.org/sites/flosshub.org/files/118-10-msr.pdf},
	author = {Schroter, Adrian and Schr{\"o}ter, Adrian and Bettenburg, Nicolas and Premraj, Rahul}
}
@inbook {springerlink:10.1007/978-3-642-13244-5_20,
	title = {Download Patterns and Releases in Open Source Software Projects: A Perfect Symbiosis?},
	booktitle = {Open Source Software: New Horizons},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {319},
	year = {2010},
	note = {"We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository."},
	pages = {252-267},
	publisher = {Springer Boston},
	organization = {Springer Boston},
	abstract = {Software usage by end-users is one of the factors used to evaluate the success of software projects. In the context of open source software, there is no single and non-controversial measure of usage, though. Still, one of the most used and readily available measure is data about projects downloads. Nevertheless, download counts and averages do not convey as much information as the patterns in the original downloads time series. In this research, we propose a method to increase the expressiveness of mere download rates by considering download patterns against software releases. We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository. Findings show that projects with similar usage can have indeed different levels of sensitivity to releases, revealing different behaviors of users. Future research will develop further the pattern recognition approach to automatically categorize open source projects according to their download patterns.},
	keywords = {flossmole, oss2010, sourceforge},
	url = {http://dx.doi.org/10.1007/978-3-642-13244-5_20},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s and Madey, Gregory and Noll, John}
}
@conference {572,
	title = {Design Evolution of an Open Source Project Using an Improved Modularity Metric},
	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 = {20 - 33},
	publisher = {Springer},
	organization = {Springer},
	chapter = {4},
	abstract = {Modularity of an open source software code base has been associated with community growth, incentives for voluntary contribution, and a reduction in free riding. As a theoretical construct, it links open source software to other domains of research, including organization theory, the economics of industry structure, and new product development; however, measuring the modularity of an open source software design has proven difficult, especially for large and complex systems. Building on previous work on Design Structure Matrices (DSMs), this paper describes two contributions towards a method for examining the evolving modularity of large-scale software systems: (1) an algorithm and new modularity metric for comparing code bases of different size; and (2) evolution analysis of Apache Tomcat to illustrate the insights gained from this approach. Over a ten-year period, the modularity of Tomcat continually increased, except in three instances: with each major change to the architecture or implementation, modularity first declined, then increased in the subsequent version to fully compensate for the decline.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Design\%20Evolution\%20of\%20an\%20Open\%20Source\%20Project.pdf},
	author = {Milev, Roberto and Muegge, Steven and Weiss, Michael}
}
@conference {1244,
	title = {Design Information Sharing Across Multiple Knowledge Systems in a FLOSS Community},
	booktitle = {iConference {\textquoteright}09},
	year = {2009},
	month = {02/2009},
	abstract = {This paper explores support for design information sharing between the distinct knowledge systems and skill sets of interactive system designers and developers. The paper focuses on the challenges of sharing information among groups of designers, developers, and users with multiple knowledge systems in the context of free/libre/open source software (FLOSS) communities. Bringing design to FLOSS communities introduces new knowledge into a solitary community of practice, and discussion ensues about how exploiting the {\textquoteright}symmetry of ignorance{\textquoteright} can enhance information sharing through design in CodePlex, an open source project hosting community website. Finally, design mockups illustrate how CodePlex serves as a boundary object supporting design information sharing across distinct knowledge systems.},
	keywords = {codeplex, developers, information sharing},
	attachments = {https://flosshub.org/sites/flosshub.org/files/finalDraft41.pdf},
	author = {Bach, Paula}
}
@article {Subramaniam:2009:DOS:1480545.1480824,
	title = {Determinants of open source software project success: A longitudinal study},
	journal = {Decis. Support Syst.},
	volume = {46},
	year = {2009},
	month = {January},
	pages = {576{\textendash}585},
	publisher = {Elsevier Science Publishers B. V.},
	address = {Amsterdam, The Netherlands, The Netherlands},
	abstract = {In this paper, we investigate open source software (OSS) success using longitudinal data on OSS projects. We find that restrictive OSS licenses have an adverse impact on OSS success. On further analysis, restrictive OSS license is found to be negatively associated with developer interest, but is positively associated with the interest of non-developer users and project administrators. We also show that developer and non-developer interest in the OSS project and the project activity levels in any time period significantly affect the project success measures in subsequent time period. The implications of our findings for OSS research and practice are discussed. },
	keywords = {contributors, developers, licenses, longitudinal study, Open source project, OSS, project success, restrictive, Software project success},
	issn = {0167-9236},
	doi = {10.1016/j.dss.2008.10.005},
	url = {http://portal.acm.org/citation.cfm?id=1480545.1480824},
	author = {Subramaniam, Chandrasekar and Sen, Ravi and Nelson, Matthew L.}
}
@article {1346,
	title = {Discourses on User Participation},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {44 - 59},
	abstract = {Users should participate in information technology (IT) artifact development, but it has proven to be challenging. This applies also in the open source software (OSS) development. This chapter critically examines discursive construction of user participation in academic literatures and in practice, in IT artifact development. First three academic discourses constructing user participation are discussed. Then the discursive construction of user participation is explored in OSS development literature. Afterwards, results from several empirical, interpretive case studies are outlined. Some of them have been carried out in the IT artifact product development organizations, others in the OSS development context. Clear similarities can be identified in the discourses constructing user participation in these divergent IT artifact development contexts. The academic discourses on user participation clearly also legitimate certain ways of constructing user participation in practice. The OSS development literature bears resemblance mainly with the Human Computer Interaction (HCI) discourse on user participation. Therefore, it is argued that especially the HCI community should carefully reflect on what kinds of discourses on user participation it advocates and deems as legitimate.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009070104},
	author = {Iivari, Netta}
}
@conference {571,
	title = {Domain Drivers in the Modularization of FLOSS Systems},
	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 = {3 - 19},
	publisher = {Springer},
	organization = {Springer},
	chapter = {3},
	abstract = {The classification of software systems into types has been achieved in the past by observing both their specifications and behavioral patterns: the SPE classification, for instance, and its further supplements and refinements, has identified the S-type (i.e., fully specified), the P-type (i.e., specified but dependent on the context) and the E-type (i.e., addressing evolving problems) among the software systems. In order to detect types, and establish similarities, among Free/Libre/Open Source Software (FLOSS) systems, this paper considers three modular characteristics (functions, files and folders) and their evolution: how they are evolving with size, if they are constant across systems, and whether recurring evolutionary patterns are observed. Using these various-grained characteristics,a set of models for the evolution of modularization are extracted from evolving systems, and then used to extract similarities and types from a wide sample of FLOSS projects. This paper provides three contributions: first, it shows that several models are needed to encompass the variety of modularization patterns; second, it provides three types of models (uni-variate, bi-variate and tri-variate) for the evolution of modularization, with significant goodness-of-fit{\textquoteright}s. Finally, it shows that two of these patterns alone can interpolate the modular characteristics of the vast majority of a random choice of FLOSS projects.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Domain\%20Drivers\%20in\%20the\%20Modularization.pdf},
	author = {Capiluppi, Andrea}
}
@mastersthesis {79,
	title = {Design for quality: The case of Open Source Software Development},
	volume = {PhD},
	year = {2008},
	school = {New York University},
	type = {doctoral dissertation},
	address = {New York, NY},
	author = {Conley, Caryn A.}
}
@conference {557,
	title = {Detecting Agility of Open Source Projects Through Developer Engagement},
	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 = {333 - 341},
	publisher = {Springer},
	organization = {Springer},
	chapter = {30},
	abstract = {The principles behind the agile development methods and common practise within the Open Source community are vastly different. In recent years there has been a rise of interest in these, in order to detect and inform on areas of compatible shared practises. This paper argues that it is possible to quantify the level of agility displayed by Open Source projects. An indicator of agility, the Mean Developer Engagement (MDE) metric is introduced and tested through the analysis of public project data. Projects sampled from two repositories (KDE and SourceForge) are studied and a hypothesis is formulated: projects from the two samples display a similar level of MDE. This paper provides two main contributions: first, the MDE metric is shown to vary significantly between the KDE and SourceForge projects. Second, by combining MDE with a project{\textquoteright}s lifespan, it is also shown that SourceForge projects have insufficient uptake of new developers resulting in more active, shorter, initial activity, and in a quicker {\textquotedblleft}burning out{\textquotedblright} of the projects.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_30},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Detecting\%20Agility\%20of\%20Open\%20Source\%20Projects.pdf},
	author = {Adams, Paul and Capiluppi, Andrea and de Groot, Adriaan}
}
@conference {970,
	title = {Determinism and evolution},
	booktitle = {Proceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {1-9},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {It has been proposed that software evolution follows a Self-Organized Criticality (SOC) dynamics. This fact is supported by the presence of long range correlations in the time series of the number of changes made to the source code over time. Those long range correlations imply that the current state of the project was determined time ago. In other words, the evolution of the software project is governed by a sort of determinism. But this idea seems to contradict intuition. To explore this apparent contradiction, we have performed an empirical study on a sample of 3,821 libre (free, open source) software projects, finding that their evolution projects is short range correlated. This suggests that the dynamics of software evolution may not be SOC, and therefore that the past of a project does not determine its future except for relatively short periods of time, at least for libre software.},
	keywords = {changes, evolution, source code, sourceforge},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370752},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p1-herraiz.pdf},
	author = {Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Gregorio Robles and Herraiz, Israel}
}
@booklet {522,
	title = {Developing {\textquoteright}FLOSS{\textquoteright} - A Market Driven Investment: First Evidence from a Francophone Companies Survey},
	year = {2008},
	abstract = {Over the last few years, FLOSS (""Free Libre Open Source Software"") has become a commercially viable reality of the first order. It is viewed as an extreme case of open innovation (Chesbrough, 2003), and thus of a laboratory for analysing innovation production in Internet based/knowledge based industries.

It the FLOSS field an increasing number of companies are getting involved in the communities of development (Lakhani \& Wolf 2005). Scholars (see, for instance Dahlander \& Wallin 2006) has analysed this as a way to control a complementary asset, without owning it (as defined by Teece 1986, Teece \& al. 1997). In this article, we defend the idea that involvement can be of different intensity, from complementary to specific asset, and that this intensity depends of the market of the firm.

To do so, we surveyed francophone companies (France, Belgium, Switzerland) affirming a utilization of FLOSS in their commercial activity. Based on roughly 500 companies concerned, we obtained 141 usable responses and, via an ascendant hierarchical clustering (AHC) we statistically verified a link between FLOSS commercial strategies and degree of involvement into communities. We propose a typology of commercial strategies explaining this differences in involvement.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/NJullien_firms_strategies_regarding_FLOSS_octobre.pdf , https://flosshub.org/sites/flosshub.org/files/Jullien_4-2008.pdf},
	author = {Nicolas Jullien}
}
@article {1084,
	title = {Dynamics of innovation in an "open source" collaboration environment: lurking, laboring, and launching FLOSS projects on SourceForge},
	journal = {Industrial and Corporate Change},
	volume = {17},
	year = {2008},
	note = {"For the purposes of this study, we are able to draw upon micro-level data pertaining to the activities undertaken during the period between the beginning of September 2000 and December 2002 by the entire cohort of 222,835 individuals who had registered on SF.net during the 14 months from September 1, 2000 through October 26, 2001."
"The statistical analysis in this article is based upon an edited dataset (referred to here as the SFnetDataset) covering the SourceForge cohort of 222,835 individuals who registered on SF.net during the 14 months from September 1, 2000 through October 26, 2001."
They appear to be using their own dataset which is from 2000-2001 even though this paper is from 2008},
	month = {07/2008},
	pages = {647 - 710},
	abstract = {A systems analysis perspective is adopted to examine the critical properties of the Free/Libre/Open Source Software (FLOSS) mode of innovation, as reflected on the SourceForge platform (SF.net). This approach re-scales March{\textquoteright}s (1991) framework and applies it to characterize the {\textquotedblleft}innovation system{\textquotedblright} of a {\textquotedblleft}distributed organization{\textquotedblright} of interacting agents in a virtual collaboration environment, rather than to innovation within a firm. March (1991) views the process of innovation at the organizational level as the coupling of sub-processes of exploration and exploitation. Correspondingly, the innovation system of the virtual collaboration environment represented by SF.net is an emergent property of two {\textquotedblleft}coupled{\textquotedblright} processes: one involves the interactions among agents searching the locale for information and knowledge resources to use in designing novel software products (i.e., exploration), and the other involves the mobilization of individuals{\textquoteright} capabilities for application in the software development projects that become established on the platform (i.e., exploitation). The micro-dynamics of this system are studied empirically by constructing transition probability matrices representing the movements of 222,835 SF.net users among seven different activity states, which range from {\textquotedblleft}lurking{\textquotedblright} (not contributing or contributing to projects without becoming a member) to {\textquotedblleft}laboring{\textquotedblright} (joining one or more projects as members), and to {\textquotedblleft}launching{\textquotedblright} (founding one or more projects) within each successive 6-month interval. The estimated probabilities are found to form first-order Markov chains describing ergodic processes. This makes it possible the computation of the equilibrium distribution of agents among the states, thereby suppressing transient effects and revealing persisting patterns of project joining and project launching. The latter show the FLOSS innovation process on SF.net to be highly dissipative: a very large proportion of the registered {\textquotedblleft}developers{\textquotedblright} fail to become even minimally active on the platform. There is nevertheless an active core of mobile project joiners, and a (still smaller) core of project founders who persist in creating new projects. The structure of these groups{\textquoteright} interactions (as displayed within the 3-year period examined) is investigated in detail, and it is shown that it would be sufficient to sustain both the exploration and exploitation phases of the platform{\textquoteright}s global dynamics.},
	keywords = {contributors, core, developers, roles, SFnetDataset, sourceforge, users, virtual communities, virtual organization, virtual organizations},
	issn = {1464-3650},
	doi = {10.1093/icc/dtn026},
	author = {David, P. A. and Rullani, F.}
}
@conference {658,
	title = {Data and analyses sharing to support research on free/libre open source software},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {355 - 356},
	publisher = {Springer},
	organization = {Springer},
	chapter = {42},
	abstract = {Research on FLOSS has relied on several different kinds of scientific evidence, such as the archives created by the FLOSS developers, versioned code repositories, mailing list messages and bug and issue tracking repositories [1]. FLOSS teams retain and make public archives of many of their activities as by-products of their open technology-supported collaboration. However, the easy availability of primary data provides a misleading picture of ease of conducting research on FLOSS. Precisely because these data are by-products, they are generally not in a form that is useful for researchers. Instead potentially useful data is locked up in HTML pages, CVS log files, text-only mailing list archives or dumps of website databases. FLOSS research projects, therefore, expend significant energy collecting and re-structuring these archives for their research, which is repetitive and wasteful [2]. Furthermore, different researchers will extract different data at different points in time, take different approaches to processing and cleaning data and make different decisions about analyses, but without all of these decisions being visible, auditable or reproducible. In principle, these latter problems can be addressed by individual researchers better documenting what they have done. However, research publications typically have restrictions on publication lengths that make complete discussion impossible. Furthermore, published papers are just the tip of the iceberg, and knowing what others have done does not necessarily make it any easier to replicate the results.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_42},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Data\%20and\%20analyses\%20sharing.pdf}
}
@proceedings {118,
	title = {Design architecture, developer networks and performance of open source software projects},
	year = {2007},
	keywords = {NotreDameArchive},
	author = {Xiang Liu and Bala Iyer}
}
@conference {1011,
	title = {Detecting Patch Submission and Acceptance in OSS Projects},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {26 - 26},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {The success of open source software (OSS) is completely dependent on the work of volunteers who contribute their time and talents. The submission of patches is the major way that participants outside of the core group of developers make contributions. We argue that the process of patch submission and acceptance into the codebase is an important piece of the open source puzzle and that the use of patch-related data can be helpful in understanding how OSS projects work. We present our methods in identifying the submission and acceptance of patches and give results and evaluation in applying these methods to the Apache webserver, Python interpreter, Postgres SQL database, and (with limitations) MySQL database projects. In addition, we present valuable ways in which this data has been and can be used.},
	keywords = {apache, contributions, mysql, patches, postgresql, python, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300026.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem}
}
@conference {992,
	title = {Determining Implementation Expertise from Bug Reports},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {2 - 2},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {As developers work on a software product they accumulate expertise, including expertise about the code base of the software product. We call this type of expertise "implementation expertise". Knowing the set of developers who have implementation expertise for a software product has many important uses. This paper presents an empirical evaluation of two approaches to determining implementation expertise from the data in source and bug repositories. The expertise sets created by the approaches are compared to those provided by experts and evaluated using the measures of precision and recall. We found that both approaches are good at finding all of the appropriate developers, although they vary in how many false positives are returned.},
	keywords = {bug reports, developers, eclipse, expertise, repository, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300002.pdf},
	author = {Anvik, John and Murphy, Gail C.}
}
@conference {639,
	title = {Different Bug Fixing Regimes? A Preliminary Case for Superbugs},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {247 - 252},
	publisher = {Springer},
	organization = {Springer},
	chapter = {23},
	abstract = {The paper investigates the processes by which bugs are fixed in open-source software projects. Focusing on Mozilla and combining data from both its bug tracker (Bugzilla) and from its CVS, we suggest that: a) Some bugs resist beyond the first patch applied to the main branch of the source code in relation to them, which we denote as superbugs; b) There might exist different bug fixing regimes; c) priority and severity flags as defined in bug repositories are not optimized for superbugs and might lead to a involuntary side effects; d) The survival time of superbugs is influenced by the nature of the discussions within Bugzilla, by bug dependencies and by the provision of contextual elements.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Different\%20Bug\%20Fixing\%20Regimes.pdf},
	author = {Jean-Michel Dalle and den Besten, Matthijs}
}
@article {flosswp332,
	title = {Do firms take part in the projects of the OS community. Some preliminary evidence and a research agenda},
	year = {2007},
	month = {January},
	abstract = {The Open Source (OS) software has progressively gained economic importance in recent years, and more and more commercial firms are getting involved, to various extents, in the OS movement. While a number of studies have investigated motivations and business models of OS-based software companies, very few works have examined whether and how firms actively participate to open projects. This paper contributes to the literature by providing empirical evidence on the role and the activities of software houses in community developed projects. The research also proposes an original methodology of large-scale primary data collection from OS project repositories and linked Web sites. The findings show how different today???s OS movement is from its origins and how important firm involvement has become, not only numerically but also for the deepness of its impact on community projects. Finally, further research developments are suggested.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper_firm_involvement_MIT.pdf},
	author = {Andrea Bonaccorsi and Dario Lorenzi and Monica Merito and Cristina Rossi}
}
@article {flosswp350,
	title = {Dragging developers towards the core. How the Free/Libre/Open Source Software community enhances developers{\textquoteright} contribution},
	year = {2007},
	month = {January},
	abstract = {The paper presents a dynamic perspective on the landscape of Free/Libre/Open Source Software (FLOSS) developers{\textquoteright} motivations and tries to isolate mechanisms sustaining developers{\textquoteright} contribution over time. The first part of the paper uses data gathered by the empirical studies relative to the FLOSS case to judge the relative importance of each group of incentives detected by the literature. In the second part of the paper, the same data are used to further characterize developers{\textquoteright} motivations in dynamics terms, showing how the relative importance of different incentives changes over time. Drawing inspiration from these results, the third part of the paper identifies a specific mechanism fostering developers{\textquoteright} contribution to the community activities, namely that: "Independently of developers{\textquoteright} exogenous preferences, the more their exposure to the FLOSS community social environment, the more their contribution to the community activities". The key point of this hypothesis is that, if the exposure to the FLOSS community social environment is able to foster developers{\textquoteright} contribution beyond the level granted by their predetermined preferences, this leads directly to the evidence that the FLOSS community is provided with a mechanism sustaining and enhancing developers{\textquoteright} incentives to produce and diffuse code. In the last part of the paper, data relative to 14,497 developers working on SourceForge.net during two years (2001-2002) are employed to estimate a model testing the aforementioned hypothesis. Endogeneity problems are explicitly accounted for, and robustness checks are performed in order to make sure that the observed confirmation of the hypothesis is actually an empirically grounded result.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rullani_socenv.pdf},
	author = {Francesco Rullani}
}
@article {flosswp348,
	title = {Dual Licensing in Open Source Software Markets},
	year = {2007},
	month = {May},
	abstract = {Dual licensing has proved to be a sustainable business model for various commercial software vendors employing open source strategies. In this paper we study the main characteristics of dual licensing and under which conditions it represents a profitable commercial strategy. We show that dual licensing is a form of versioning, whereby the software vendor uses the open source licensing terms in order to induce commercial customers to select the proprietary version of the software. Furthermore, we show that the software vendor prefers dual licensing to a fully proprietary strategy when the customers are very sensitive to the reciprocal terms of the open source license.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dual_lic.pdf},
	author = {Stefano Comino and Fabio M. Manenti}
}
@conference {Sager:2006:DSJ:1137983.1138000,
	title = {Detecting similar Java classes using tree algorithms},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {65{\textendash}71},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Similarity analysis of source code is helpful during development to provide, for instance, better support for code reuse. Consider a development environment that analyzes code while typing and that suggests similar code examples or existing implementations from a source code repository. Mining software repositories by means of similarity measures enables and enforces reusing existing code and reduces the developing effort needed by creating a shared knowledge base of code fragments. In information retrieval similarity measures are often used to find documents similar to a given query document. This paper extends this idea to source code repositories. It introduces our approach to detect similar Java classes in software projects using tree similarity algorithms. We show how our approach allows to find similar Java classes based on an evaluation of three tree-based similarity measures in the context of five user-defined test cases as well as a preliminary software evolution analysis of a medium-sized Java project. Initial results of our technique indicate that it (1) is indeed useful to identify similar Java classes, (2)successfully identifies the ex ante and ex post versions of refactored classes, and (3) provides some interesting insights into within-version and between-version dependencies of classes within a Java project.},
	keywords = {change analysis, clones, coogle, eclipse, famix, java, similarity, software evolution, software repositories, source code, tree similarity measures},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138000},
	url = {http://doi.acm.org/10.1145/1137983.1138000},
	attachments = {https://flosshub.org/sites/flosshub.org/files/65Detecting.pdf},
	author = {Sager, Tobias and Bernstein, Abraham and Pinzger, Martin and Kiefer, Christoph}
}
@article {flosswp322,
	title = {Developer Learning Dynamics in Open Source Software Projects: A Hidden Markov Model Analysis},
	year = {2006},
	month = {December},
	abstract = {This work proposes a dynamic model of developer learning in open source software (OSS) projects. A Hidden Markov Model (HMM) is proposed to explain how the code contribution behaviors of OSS de-velopers change as their levels of knowledge on their projects increase. In this model, discrete hidden states represent the unobserved knowledge levels of developers, and their observed code contribution be-haviors are modeled as state dependent. Developers??? knowledge levels evolve as they learn about the pro-jects over time. Two modes of learning are considered: learning-by-doing (code development) and learn-ing through interactions with peers. The model is calibrated using data spanning six years for 25 OSS pro-jects and 251 developers hosted at Sourceforge. The proposed model identifies three knowledge states (high, medium, and low) and estimates the impact of the two modes of learning on the transition of devel-opers between the three knowledge states. The model results suggest that in the low knowledge state de-velopers exhibit the greatest inertia, followed by those in the medium and high states. Both modes of learning are found to have varying impact across the three knowledge states. Interactions with peers ap-pear to be an important source of learning for developers in all states. A developer in the low state learns only through participation in threads started by others. Prior code contribution and starting discussion by initiating threads do not impact the knowledge level of a developer in the low state. Initiating threads, par-ticipating in threads started by others, and prior code contributions have positive impacts on the knowl-edge level of a developer in the medium or high state and, hence, influence his long term code contribu-tion behavior. Explanations for these varying impacts of learning activities on the transitions of develop-ers between the three states are provided. We also find a lack of persistence of knowledge in all states. The HMM better describes the data than a latent class model which would suggests that the learning ac-tivities have a long term, dynamic impact, rather than an immediate, static impact on the code contribu-tion behavior of a developer.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/singh-youn-tan.pdf},
	author = {Param Vir Singh and Nara Youn and Yong Tan}
}
@conference {688,
	title = {Development Platforms as a Niche for Software Companies in Open Source Software},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {341 - 342},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Without Abstract},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Development\%20Platforms\%20as\%20a\%20Niche.pdf},
	author = {Savonnet, Marinette and Leclercq, Eric and Terrasse, Marie-No{\"e}lle and Grison, Thierry and Becker, George and Farizy, Anne and Denoyelle, Ludovic}
}
@inbook {894,
	title = {Discovering, Modeling, and Reenacting Open Source Software Development Processes},
	booktitle = {New Trends in Software Process Modeling},
	series = {Series in Software Engineering and Knowledge Engineering},
	volume = {18},
	year = {2006},
	pages = {1-20},
	author = {Chris Jensen and Walt Scacchi}
}
@conference {751,
	title = {Defining a Distributed Agile Methodology for an Open Source Scenario},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {209-214},
	abstract = {In this paper we propose and describe an agile methodology for distributed development (MADD - Methodology for Agile Distributed Development). In particular, it{\textquoteright}s illustrated a set of best practices to apply in a distributed and agile context, chosen on the base of their impact software quality and team interoperation. Beyond the proposed methodology, we show the results of a survey that we submitted to various contributors of Open Source projects. The survey has been of support to the definition of the MADD, helping to more understand and estimate if, how and how much agile practices and values are already present in the OS world, that today represents one of the most emblematic examples of distributed development. The MADD methodology will be adopted on a software development project at the University of Cagliari (Italy), by a group of students that will work like an Open Source community.},
	url = {http://pascal.case.unibz.it/handle/2038/766},
	author = {Angioni, Manuela and Sanna, Raffaella and Soro, Alessandro}
}
@conference {732,
	title = {Defining the Total Cost of Ownership for the Transition to Open Source Systems},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {108-112},
	abstract = {This paper provides a a framework to evaluate the transition to a OSS software solution in terms of returns and losses in the context of Public Administrations. The ultimate goal of the framework is to identify costs that are not easy to trace or that are not usually collected like user acceptance. The framework has been conducted using a Total Cost of Ownership approach, which is the most frequently used model to conduct cost comparisons between two or more IT systems. The study further implements the Goal Question Metric paradigm to identify the cost metrics. The framework relies various methods to collect the data, including questionnaires with end-users, qualitative interviews with IT-managers and company balance sheets. An example of framework{\textquoteright}s use is provided.},
	url = {http://pascal.case.unibz.it/handle/2038/774},
	author = {Russo, Barbara and Braghin, Chiara and Gasperi, Paolo and Sillitti, Alberto and Succi, Giancarlo}
}
@book {flosswp210,
	title = {Democratizing Innovation},
	year = {2005},
	month = {April},
	publisher = {MIT Press},
	organization = {MIT Press},
	abstract = {Innovation is rapidly becoming democratized. Users, aided by improvements in computer and communications technology, increasingly can develop their own new products and services. These innovating users{\textendash}both individuals and firms{\textendash}often freely share their innovations with others, creating user-innovation communities and a rich intellectual commons. In Democratizing Innovation, Eric von Hippel looks closely at this emerging user-centered innovation system. He explains why and when users find it profitable to develop new products and services for themselves, and why it often pays users to reveal their innovations freely for the use of all. The trend toward democratized innovation can be seen in software and information products{\textendash}most notably in the free and open-source software movement{\textendash}but also in physical products. He shows that product and service development is concentrated among "lead users," who are ahead on marketplace trends and whose innovations are often commercially attractive. Von Hippel argues that manufacturers should redesign their innovation processes and systematically seek out innovations developed by users. User innovation has a positive impact on social welfare, and von Hippel proposes that government policies, including R\&D subsidies and tax credits, should be realigned to eliminate biases against it. An electronic version of this book is available under a Creative Commons license.},
	author = {von Hippel, Eric}
}
@conference {Robles:2005:DIM:1083142.1083162,
	title = {Developer identification methods for integrated data from various sources},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {106-110},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Studying a software project by mining data from a single repository has been a very active research field in software engineering during the last years. However, few efforts have been devoted to perform studies by integrating data from various repositories, with different kinds of information, which would, for instance, track the different activities of developers. One of the main problems of these multi-repository studies is the different identities that developers use when they interact with different tools in different contexts. This makes them appear as different entities when data is mined from different repositories (and in some cases, even from a single one). In this paper we propose an approach, based on the application of heuristics, to identify the many identities of developers in such cases, and a data structure for allowing both the anonymized distribution of information, and the tracking of identities for verification purposes. The methodology will be presented in general, and applied to the GNOME project as a case example. Privacy issues and partial merging with new data sources will also be considered and discussed.},
	keywords = {anonymization, bug tracker, developers, email, email address, gnome, identity, mailing list, privacy, source code, version control},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083162},
	url = {http://doi.acm.org/10.1145/1082983.1083162},
	attachments = {https://flosshub.org/sites/flosshub.org/files/106DeveloperIdentification.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@proceedings {citeulike:3052508,
	title = {Development Success in Open Source Software Projects: Exploring the Impact of Copylefted Licenses},
	year = {2005},
	abstract = {Copyleft prevents the source code of open source software (OSS) from being privately appropriated. The ethos of the OSS movement suggests that volunteer developers may particularly value and contribute to copylefted projects. Based on social movement theory, we hypothesized that copylefted OSS projects are more likely than non-copylefted OSS projects to succeed in the development process, in terms of two key indicators: developer membership and developer productivity. We performed an exploratory study using data from 62 relevant OSS projects spanning an average of three years of development time. We found that copylefted projects were associated with higher developer membership and productivity. This is the first study to empirically test the relationship between copylefted licenses and OSS project success. Implications for OSS project initiators as well as future research directions are discussed.},
	keywords = {contributions, copyleft, developer, developers, membership, productivity, project success, success},
	url = {http://aisel.isworld.org/password.asp?Vpath=AMCIS/2005\&\#38;PDFpath=OSSDAU01-1167.pdf},
	author = {Colazo, Jorge A. and Fang, Yulin and Neufeld, Derrick J.}
}
@conference {796,
	title = {Development-oriented Open Source eLearning Tool Evaluation: the Edukalibre Approach},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {341-344},
	author = {Botturi, Luca and Chris Tebb and Vania Dimitrova and Drew Withworth and Julika Matravers and Jutta Geldermann and Isabelle Hubert}
}
@proceedings {1517,
	title = {Digesting Virtual {\textquotedblleft}Geek{\textquotedblright} Culture: The Summarization of Technical Internet Relay Chats},
	year = {2005},
	month = {06/2005},
	pages = {298-305},
	address = {Ann Arbor, MI, USA},
	abstract = {This paper describes a summarization system for technical chats and emails on the Linux kernel. To reflect the complexity and sophistication of the discussions, they are clustered according to subtopic structure on the sub-message level, and immediate responding pairs are identified through machine learning methods. A resulting summary consists of one or more mini-summaries, each on a subtopic from the discussion.},
	keywords = {computational linguistics, irc, linux, summarizing},
	url = {http://acl.ldc.upenn.edu/P/P05/P05-1037.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/P05-1037.pdf},
	author = {Liang Zhou and Edouard Hovy}
}
@conference {753,
	title = {Distributed Software Platforms for Rehabilitating Obsolete Hardware},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {220-223},
	abstract = {The diffusion of ICTs created the issue of a huge quantity of old computers to be discarded (E-waste). Sustainable dismantle is becoming a global enviromental emergency. Trashware movement is spreading worldwide, aiming to profitably reuse discarded computers as an alternative to dismantling them. Trashware is deeply related to the Open Source and Free Software movements. The aim of this piece of research is to combine Trashware to clustering, in order to verify if further optimisations are possible. Experiments were conducted on clusters of old machines and results are hereby presented.},
	url = {http://pascal.case.unibz.it/handle/2038/782},
	author = {Russo, Ruggero and Lamanna, Davide and Baldoni, Roberto}
}
@conference {780,
	title = {Doctoral Symposium at OSS 2005},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {300},
	author = {Russo, Barbara}
}
@proceedings {906,
	title = {Data Mining for Software Process Discovery in Open Source Software Development Communities},
	year = {2004},
	month = {May},
	address = {Edinburgh, Scotland, UK},
	author = {Chris Jensen and Walt Scacchi}
}
@article {flosswp156,
	title = {Decoding the "Free/Open Source (F/OSS) Puzzle" - a Survey ofTheretical and Empirical Contributions},
	year = {2004},
	month = {April},
	abstract = {F/OSS software has been described by many as a puzzle. In the past five years, it has stimulated the curiosity of scholars in a variety of fields, including economics, law, psychology, anthropology and computer science, so that the number of contributions on the subject has increased exponentially. The purpose of this paper is to provide a sufficiently comprehensive account of these contributions in order to draw some general conclusions on the state of our understanding of the phenomenon and identify directions for future research. The exercise suggests that what is puzzling about F/OSS is not so much the fact that people freely contribute to a good they make available to all, but rather the complexity of its institutional structure and its ability to organizationally evolve over time.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rossi.pdf},
	author = {Maria Alessandra Rossi}
}
@conference {77,
	title = {Do the Rich Get Richer? The Impact of Power Laws on Open Source Development Projects},
	booktitle = {2004 Open Source Conference (OSCON)},
	year = {2004},
	type = {conference presentation},
	address = {Portland, OR, USA},
	keywords = {open source, power law, social network analysis, sourceforge},
	author = {Conklin, Megan}
}
@conference {flosswp137,
	title = {Defining Open Source Software Project Success},
	booktitle = {Twenty-Fourth International Conference on Information Systems},
	year = {2003},
	month = {December},
	abstract = {Information systems success is one of the most widely used dependent variables in information systems research. In this paper, we identify a range of measures that can be used to assess the success of open source software (OSS) projects. We identify measures based on a review of the literature, a consideration of the OSS development process and an analysis of the opinions of OSS developers. For each measure, we provide examples of how they might be used in a study of OSS development.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowstonannabihowison.pdf},
	author = {Kevin Crowston and Hala Annabi and James Howison}
}
@article {flosswp125,
	title = {Determining the Distribution of Maintenance Categories: Survey versus Measurement},
	year = {2003},
	month = {October},
	abstract = {In 1978, Lientz, Swanson, and Tompkins ("LST") published the results of a survey on software maintenance. They found that 17.4\% of maintenance effort was categorized as corrective in nature, 18.2\% as adaptive, 60.3\% as perfective, and 4.1\% was categorized as other. We contrast this survey-based result with our empirical results from the analysis of data for the repeated maintenance of a commercial real-time product and two open-source products, the Linux kernel and GCC. For all three products and at both levels of granularity we considered, our observed distributions of maintenance categories were statistically very highly significantly different from LST. In particular, corrective maintenance was always more than twice the LST value.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lst.preprint.pdf},
	author = {Jin Schach}
}
@conference {1109,
	title = {Distributed Collective Practices and F/OSS Problem Management: Perspective and Methods},
	booktitle = {Conference on Cooperation, Innovation \& Technology (CITE 2003)},
	year = {2003},
	note = {"We have begun studying in detail the general issues raised above using a large collection of research data from the Mozilla project"
"Our Bugzilla snapshot contains over 128,000 problem reports, of which about 88,000 have been resolved"},
	abstract = {This paper presents the state of our research on Distributed Collective Practices (DCPs) in Free/Open-Source Software (F/OSS) projects, focusing on sensemaking and resolution of software problems. We are exploring the hypothesis that variations in the content and in the articulation of these socio-technical processes have an impact on the outcome of the activity of F/OSS collectives, and more specifically on problem resolution. Our preliminary techniques for combining qualitative data analysis with automated process extraction result in a scalable analysis method called Computational Amplification (CA). We are applying CA to 128,000 problem reports from the Mozilla F/OSS project. The paper illustrates how CA is used to create multidimensional process models and shows types of conclusions we can reach.},
	keywords = {Automated process extraction, bug fixing, bug reports, bugzilla, Collective knowledge management, Information extraction from natural language texts, mozilla, Software problem management},
	author = {Gasser, Les and Gabriel Ripoche}
}
@article {flosswp107,
	title = {Dual Licensing in Open Source Software Industry},
	year = {2003},
	month = {January},
	abstract = {This paper analyses how several open source companies use dual licensing: both open source and proprietary licenses for one product. Three case studies based on the experiences of companies Sleepycat Software Inc., MySQL AB, and TrollTech AS illustrate the issue. Especially the legal and economic requirements of dual licensing are identified.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/valimaki.pdf},
	author = {Mikko Valimaki}
}
@article {flosswp118,
	title = {Dynamic Mixed Duopoly: A Model Motivated by Linux vs. Windows},
	year = {2003},
	month = {September},
	abstract = {This paper analyzes a dynamic mixed duopoly in which a profit-maximizing competitor interacts with a competitor that prices at zero (or marginal cost), with the cumulation of output affecting their relative positions over time. The modeling effort is motivated by interactions between Linux, an open-source operating system, and Microsofts Windows in the computer server segment, and consequently emphasizes demand-side learning effects that generate dynamic scale economies (or network externalities). Analytical characterizations of the equilibrium under such conditions are offered, and some comparative static and welfare effects are examined.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/masanellghemawat.pdf},
	author = {Ramon Casadesus-Masanell}
}
@article {1115,
	title = {De-Bugging open source software licensing},
	journal = {University of Pittsburgh Law Review},
	volume = {64},
	number = {1},
	year = {2002},
	month = {2002},
	pages = {75-103},
	keywords = {licensing},
	attachments = {https://flosshub.org/sites/flosshub.org/files/debugopensource.pdf},
	author = {Gomulkiewicz, R.W.}
}
@article {flosswp64,
	title = {Development Costs and Open Source Software},
	year = {2002},
	month = {November},
	abstract = {This paper analyzes the effect of the development cost on an open source software enhancement that is developed by individual programmers in an Internet community. It considers a situation in which each programmer{\textquoteright}s cost of development is common knowledge but his valuation of the enhancement is his private information, with other programmers knowing about only its distribution. Depending on the distribution functions of programmers{\textquoteright} valuations of the enhancement, a programmer with a lower development cost may have a less incentive to develop. As the development cost decreases, the enhancement may be less likely to be developed, and some programmers may be worse off.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/xxu.pdf},
	author = {Xiaopeng Xu}
}
@unpublished {flosswp28,
	title = {Detecting Dominant Design},
	year = {2001},
	month = {May},
	abstract = {This paper derives a framework for the emergence of a dominant design in the web server market. Particular attention is given to factors important in network-based economies including network effects, standards, complimentary assets and technological change. A complete examination of the web server industry from its origins in the Internet through to today{\textquoteright}s market dominated by the products of open-source and proprietary software provides interesting insights into the application of the emergence framework.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/jordan.pdf},
	author = {John Jordan}
}
@article {flosswp25,
	title = {Distributed Knowledge and the Global Organization of Software Development},
	year = {2001},
	month = {February},
	abstract = {Open-source software development is a production model that exploits the distributed intelligence of participants in Internet communities. This model is efficient because of two related reasons: it avoids the inefficiencies of a strong intellectual property regime and it implements concurrently design and testing of software modules. The hazard of open source is that projects can ?fork? into competing versions. However, open-source communities consist of governance structures that constitutionally minimize this danger. Because open source works in a distributed environment, it presents an opportunity for developing coun-tries to participate in frontier innovation.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kogut1.pdf},
	author = {Bruce Kogut}
}
@article {witten2001does,
	title = {Does open source improve system security?},
	journal = {IEEE Software},
	volume = {18},
	number = {5},
	year = {2001},
	pages = {57{\textendash}61},
	publisher = {IEEE},
	abstract = {An attacker
could examine
public source
code to find
flaws in a
system. So, is
source code
access a net
gain or loss for
security? The
authors
consider this
question from
several
perspectives
and tentatively
conclude that
having source
code available
should work in
favor of system
security.},
	keywords = {security},
	url = {https://pdfs.semanticscholar.org/71f6/01579ad1c373ed59a19eba0396f7f0cb7a0e.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/01579ad1c373ed59a19eba0396f7f0cb7a0e.pdf},
	author = {Witten, Brian and Landwehr, Carl and Caloyannides, Michael}
}
@article {913,
	title = {Dimensions of information systems success},
	journal = {Communications of the Association for Information Systems},
	volume = {20},
	number = {2},
	year = {1999},
	pages = {61},
	author = {Seddon, PB and Staples, S and Patnayakuni, R and Bowtell, M}
}
