@proceedings {1913,
	title = {An Empirical Analysis of Build Failures in the Continuous Integration Workflows of Java-Based Open-Source Software},
	year = {2017},
	note = {"empirical study of CI build
failures in 14 Java-based OSS projects. We extract and analyze
data from publicly available GitHub repositories and Travis-CI
build logs"},
	month = {05/2017},
	pages = {345-355},
	abstract = {{\textemdash}Continuous Integration (CI) has become a common
practice in both industrial and open-source software development.
While CI has evidently improved aspects of the software
development process, errors during CI builds pose a threat to
development efficiency. As an increasing amount of time goes
into fixing such errors, failing builds can significantly impair the
development process and become very costly. We perform an indepth
analysis of build failures in CI environments. Our approach
links repository commits to data of corresponding CI builds.
Using data from 14 open-source Java projects, we first identify
14 common error categories. Besides test failures, which are by
far the most common error category (up to >80\% per project),
we also identify noisy build data, e.g., induced by transient Git
interaction errors, or general infrastructure flakiness. Second,
we analyze which factors impact the build results, taking into
account general process and specific CI metrics. Our results
indicate that process metrics have a significant impact on the
build outcome in 8 of the 14 projects on average, but the strongest
influencing factor across all projects is overall stability in the
recent build history. For 10 projects, more than 50\% (up to 80\%)
of all failed builds follow a previous build failure. Moreover, the
fail ratio of the last k=10 builds has a significant impact on build
results for all projects in our dataset.},
	keywords = {build errors, continuous integration, correlation analysis, msr},
	author = {Thomas Rausch and Waldemar Hummer and Philipp Leitner and Stefan Schulte}
}
@article {1872,
	title = {Empirical analysis of search based algorithms to identify change prone classes of open source software},
	journal = {Computer Languages, Systems \& Structures},
	volume = {47},
	year = {2017},
	month = {01/2017},
	pages = {211 - 231},
	abstract = {There are numerous reasons leading to change in software such as changing requirements, changing technology, increasing customer demands, fixing of defects etc. Thus, identifying and analyzing the change-prone classes of the software during software evolution is gaining wide importance in the field of software engineering. This would help software developers to judiciously allocate the resources used for testing and maintenance. Software metrics can be used for constructing various classification models which can be used for timely identification of change prone classes. Search based algorithms which form a subset of machine learning algorithms can be utilized for constructing prediction models to identify change prone classes of software. Search based algorithms use a fitness function to find the best optimal solution among all the possible solutions. In this work, we analyze the effectiveness of hybridized search based algorithms for change prediction. In other words, the aim of this work is to find whether search based algorithms are capable for accurate model construction to predict change prone classes. We have also constructed models using machine learning techniques and compared the performance of these models with the models constructed using Search Based Algorithms. The validation is carried out on two open source Apache projects, Rave and Commons Math. The results prove the effectiveness of hybridized search based algorithms in predicting change prone classes of software. Thus, they can be utilized by the software developers to produce an efficient and better developed software.},
	keywords = {Change proneness; Metrics; Object oriented paradigm; Search based algorithms; Software quality; Empirical validation},
	issn = {14778424},
	doi = {10.1016/j.cl.2016.10.001},
	author = {Bansal, Ankita}
}
@conference {vlas2017evolutionary,
	title = {Evolutionary Software Requirements Factors and their Effect on Open Source Project Attractiveness},
	booktitle = {Proceedings of the 50th Hawaii International Conference on System Sciences (HICSS)},
	year = {2017},
	month = {01/2017},
	abstract = {Successful projects effectively manage their requirements.
How the mix of different requirements evolves throughout a
successful project life-cycle is poorly understood. Moreover,
requirements practices may be changing, according to the
authors of the New RE{\textemdash}a model of six critical requirements
factors. The New RE focuses on leveraging existing
components to create new functionality. This practice is also
central to open-source development. Thus, to understand the
proposed New RE model and its relationship to open-source
development, in this study, we analyze over 200 projects from
GitHub.com and compare them with a prior analysis of 31
projects from SourceForge. The results show that many of the
proposed New RE factors are related to project attractiveness,
which is important for open-source project success.},
	url = {http://scholarspace.manoa.hawaii.edu/bitstream/10125/41806/1/paper0657.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper0657.pdf},
	author = {Vlas, Radu and Robinson, William and Vlas, Cristina}
}
@article {adams2016empirical,
	title = {An empirical study of integration activities in distributions of open source software},
	journal = {Empirical Software Engineering},
	volume = {21},
	number = {3},
	year = {2016},
	pages = {960{\textendash}1001},
	publisher = {Springer},
	abstract = {Reuse of software components, either closed or open source, is considered to be one of the most important best practices in software engineering, since it reduces development cost and improves software quality. However, since reused components are (by definition) generic, they need to be customized and integrated into a specific system before they can be useful. Since this integration is system-specific, the integration effort is non-negligible and increases maintenance costs, especially if more than one component needs to be integrated. This paper performs an empirical study of multi-component integration in the context of three successful open source distributions (Debian, Ubuntu and FreeBSD). Such distributions integrate thousands of open source components with an operating system kernel to deliver a coherent software product to millions of users worldwide. We empirically identified seven major integration activities performed by the maintainers of these distributions, documented how these activities are being performed by the maintainers, then evaluated and refined the identified activities with input from six maintainers of the three studied distributions. The documented activities provide a common vocabulary for component integration in open source distributions and outline a roadmap for future research on software integration.

},
	url = {http://mcis.soccerlab.polymtl.ca/publications/2016/integration_oss_distribution.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/integration_oss_distribution.pdf},
	author = {Adams, Bram and Kavanagh, Ryan and Hassan, Ahmed E. and Daniel M. German}
}
@article {kazman2016evaluating,
	title = {Evaluating the Effects of Architectural Documentation: A Case Study of a Large Scale Open Source Project},
	journal = {IEEE Transactions on Software Engineering},
	volume = {42},
	number = {3},
	year = {2016},
	pages = {220{\textendash}260},
	publisher = {IEEE},
	abstract = {Sustaining large open source development efforts requires recruiting new participants; however, a lack of
architectural documentation might inhibit new participants since large amounts of project knowledge are unavailable to
newcomers. We present the results of a multitrait, multimethod analysis of the effects of introducing architectural documentation
into a substantial open source project{\textemdash}the Hadoop Distributed File System (HDFS). HDFS had only minimal architectural
documentation, and we wanted to discover whether the putative benefits of architectural documentation could be observed over
time. To do this, we created and publicized an architecture document and then monitored its usage and effects on the project.
The results were somewhat ambiguous: by some measures the architecture documentation appeared to effect the project but
not by others. Perhaps of equal importance is our discovery that the project maintained, in its web-accessible JIRA archive of
software issues and fixes, enough architectural discussion to support architectural thinking and reasoning. This {\textquotedblleft}emergent{\textquotedblright}
architecture documentation served an important purpose in recording core project members{\textquoteright} architectural concerns and
resolutions. However, this emergent architecture documentation did not serve all project members equally well; it appears that
those on the periphery of the project{\textemdash}newcomers and adopters{\textemdash}still require explicit architecture documentation, as we will
show.},
	author = {Kazman, Rick and Goldenson, Dennis and Monarch, Ira and Nichols, William and Valetto, Giuseppe}
}
@proceedings {1825,
	title = {Externalization of Software Behavior by the Mining of Norms},
	year = {2016},
	month = {05/2016},
	pages = {223-234},
	abstract = {Open Source Software Development (OSSD) often suffers from conflicting views and actions due to the perceived flat and open ecology of an open source community. This often manifests itself as a lack of codified knowledge that is easily accessible for community members. How decisions are made and expectations of a software system are often described in detail through the many forms of social communications that take place within a community. These social interactions form norms which are influential in dictating what behaviors are expected in a community and of the system. In this paper, we provide a tool which mines these social interactions (in the form of bug reports) and extract norms of the system, externalizing this information into a codified form that allows others within the community to be aware of without having witnessed the social interactions.},
	doi = {http://dx.doi.org/10.1145/2901739.2901744},
	author = {Daniel Avery and Dam, Hoa Khanh and Savarimuthu, Bastin Tony Roy and Aditya Ghose}
}
@conference {blincoeMSR15,
	title = {Ecosystems in GitHub and a Method for Ecosystem Identification using Reference Coupling},
	booktitle = {12th Working Conference on Mining Software Repositories},
	series = {MSR},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {Software projects are not developed in isolation.
Recent research has shifted to studying software ecosystems,
communities of projects that depend on each other and are
developed together. However, identifying technical dependencies
at the ecosystem level can be challenging. In this paper, we
propose a new method, known as reference coupling, for detecting
technical dependencies between projects. The method establishes
dependencies through user-specified cross-references between
projects. We use our method to identify ecosystems in GitHubhosted
projects, and we identify several characteristics of the
identified ecosystems. We find that most ecosystems are centered
around one project and are interconnected with other ecosystems.
The predominant type of ecosystems are those that develop
tools to support software development. We also found that the
project owners{\textquoteright} social behaviour aligns well with the technical
dependencies within the ecosystem, but project contributors{\textquoteright}
social behaviour does not align with these dependencies. We
conclude with a discussion on future research that is enabled
by our reference coupling method.},
	url = {http://kblincoe.github.io/publications/2015_MSR_Ecosystems_CameraReady.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2015_MSR_Ecosystems_CameraReady.pdf},
	author = {Blincoe, Kelly and Harrison, Francis and Damian, Daniela}
}
@proceedings {1772,
	title = {An Empirical Study of Architectural Change in Open-Source Software Systems},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {From its very inception, the study of software
architecture has recognized architectural decay as a regularly
occurring phenomenon in long-lived systems. Architectural decay
is caused by repeated changes to a system during its lifespan.
Despite decay{\textquoteright}s prevalence, there is a relative dearth of empirical
data regarding the nature of architectural changes that may lead
to decay, and of developers{\textquoteright} understanding of those changes. In
this paper, we take a step toward addressing that scarcity by
conducting an empirical study of changes found in software
architectures spanning several hundred versions of 14 opensource
systems. Our study reveals several new findings regarding
the frequency of architectural changes in software systems, the
common points of departure in a system{\textquoteright}s architecture during
maintenance and evolution, the difference between system-level
and component-level architectural change, and the suitability
of a system{\textquoteright}s implementation-level structure as a proxy for its
architecture.},
	keywords = {architectural change, architecture recovery, open-source systems, software architecture, software evolution},
	url = {http://softarch.usc.edu/~pooyan/publications/emparch_msr15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/emparch_msr15.pdf},
	author = {Duc Minh Le and Pooyan Behnamghader and Joshua Garcia{\textdaggerdbl} Daniel Link and Arman Shahbazian and Nenad Medvidovic}
}
@conference {1795,
	title = {An Empirical Study of Developer Quality},
	booktitle = {2015 International Conference on Software Quality, Reliability and Security - Companion (QRS-C)},
	year = {2015},
	month = {08/2015},
	pages = {202 - 209},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Human factors have attracted more and more attention in software engineering. Of many kinds of developer metrics proposed, developer quality is important. Recently, some researchers measure a developer{\textquoteright}s quality as the rate of his/hernon bug-introducing commits. In this paper, we conduct an empirical study of this developer quality metric. We use the data of six open source software projects and get the following conclusions: (1) the values of developer quality in a project are uniformly distributed in a certain range, (2) developer quality tends to increase with software evolution, (3) developers with more contribution are more likely to have higher developer quality, (4) ownership does not have a consistent and significant correlation with developer quality. These results can provide project leaders and team members with some guides to improve developer quality, and thus improve software quality.},
	doi = {10.1109/QRS-C.2015.33},
	author = {Qiu, Yilin and Zhang, Weiqiang and Zou, Weiqin and Liu, Jia and Liu, Qin}
}
@conference {1822,
	title = {An Empirical Study of Developer Quality},
	booktitle = {2015 International Conference on Software Quality, Reliability and Security - Companion (QRS-C)},
	year = {2015},
	pages = {202 - 209},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Human factors have attracted more and more attention in software engineering. Of many kinds of developer metrics proposed, developer quality is important. Recently, some researchers measure a developer{\textquoteright}s quality as the rate of his/hernon bug-introducing commits. In this paper, we conduct an empirical study of this developer quality metric. We use the data of six open source software projects and get the following conclusions: (1) the values of developer quality in a project are uniformly distributed in a certain range, (2) developer quality tends to increase with software evolution, (3) developers with more contribution are more likely to have higher developer quality, (4) ownership does not have a consistent and significant correlation with developer quality. These results can provide project leaders and team members with some guides to improve developer quality, and thus improve software quality.
},
	doi = {10.1109/QRS-C.2015.33},
	author = {Qiu, Yilin and Zhang, Weiqiang and Zou, Weiqin and Liu, Jia and Liu, Qin}
}
@inbook {1730,
	title = {An Empirical Study of the Relation Between Strong Change Coupling and Defects Using History and Social Metrics in the Apache Aries Project},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {3-12},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Change coupling is an implicit relationship observed when artifacts change together during software evolution. The literature leverages change coupling analysis for several purposes. For example, researchers discovered that change coupling is associated with software defects and reveals relationships between software artifacts that cannot be found by scanning code or documentation. In this paper, we empirically investigate the strongest change couplings from the Apache Aries project to characterize and identify their impact in software development. We used historical and social metrics collected from commits and issue reports to build classification models to identify strong change couplings. Historical metrics were used because change coupling is a phenomenon associated with recurrent co-changes found in the software history. In turn, social metrics were used because developers often interact with each other in issue trackers to accomplish the tasks. Our classification models showed high accuracy, with 70-99 \% F-measure and 88-99 \% AUC. Using the same set of metrics, we also predicted the number of future defects for the artifacts involved in strong change couplings. More specifically, we were able to predict 45.7 \% of defects where these strong change couplings reoccurred in the post-release. These findings suggest that developers and projects managers should detect and monitor strong change couplings, because they can be associated with defects and tend to happen again in the subsequent release.},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_1},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_1},
	author = {Wiese, Igor Scaliante and Kuroda, Rodrigo Takashi and Re, Reginaldo and Oliva, Gustavo Ansaldi and Gerosa, MarcoAur{\'e}lio},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@article {sharif2015empirically,
	title = {An empirically-based characterization and quantification of information seeking through mailing lists during open source developers{\textquoteright} software evolution},
	journal = {Information and Software Technology},
	volume = {57},
	year = {2015},
	pages = {77{\textendash}94},
	publisher = {Elsevier},
	abstract = {Context
Several authors have proposed information seeking as an appropriate perspective for studying software evolution. Empirical evidence in this area suggests that substantial time delays can accrue, due to the unavailability of required information, particularly when this information must travel across geographically distributed sites.

Objective
As a first step in addressing the time delays that can occur in information seeking for distributed Open Source (OS) programmers during software evolution, this research characterizes the information seeking of OS developers through their mailing lists.

Method
A longitudinal study that analyses 17 years of developer mailing list activity in total, over 6 different OS projects is performed, identifying the prevalent information types sought by developers, from a qualitative, grounded analysis of this data. Quantitative analysis of the number-of-responses and response time-lag is also performed.

Results
The analysis shows that Open Source developers are particularly implementation centric and team focused in their use of mailing lists, mirroring similar findings that have been reported in the literature. However novel findings include the suggestion that OS developers often require support regarding the technology they use during development, that they refer to documentation fairly frequently and that they seek implementation-oriented specifics based on system design principles that they anticipate in advance. In addition, response analysis suggests a large variability in the response rates for different types of questions, and particularly that participants have difficulty ascertaining information on other developer{\textquoteright}s activities.

Conclusion
The findings provide insights for those interested in supporting the information needs of OS developer communities: They suggest that the tools and techniques developed in support of co-located developers should be largely mirrored for these communities: that they should be implementation centric, and directed at illustrating {\textquotedblleft}how{\textquotedblright} the system achieves its functional goals and states. Likewise they should be directed at determining the reason for system bugs: a type of question frequently posed by OS developers but less frequently responded to.},
	keywords = {Information seeking software maintenance; Open source software; Qualitative empirical study},
	doi = {10.1016/j.infsof.2014.09.003},
	url = {http://www.sciencedirect.com/science/article/pii/S095058491400202X},
	author = {Sharif, Khaironi Y and English, Michael and Ali, Nour and Exton, Chris and Collins, JJ and Buckley, Jim}
}
@proceedings {1727,
	title = {Enabling the Definition and Enforcement of Governance Rules in Open Source Systems},
	volume = {2},
	year = {2015},
	month = {05/2015},
	pages = {505-514},
	publisher = {ACM/IEEE},
	abstract = {Governance rules in software development projects
help to prioritize and manage their development tasks, and
contribute to the long-term sustainability of the project by
clarifying how core and external contributors should collaborate
in order to advance the project during its whole lifespan. Despite
their importance, specially in Open Source Software (OSS)
projects, these rules are usually implicit or scattered in the
project documentation/tools (e.g., tracking-systems or forums),
hampering the correct understanding of the development process.
We propose to enable the explicit definition and enforcement of
governance rules for OSS projects. We believe this brings several
important benefits, including improvements in the transparency
of the process, its traceability and the semi-automation of the
governance itself. Our approach has been implemented on top of
Mylyn, a project-management Eclipse plug-in supporting most
popular tracking-systems.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icse2015-governance-validated.pdf},
	author = {Izquierdo, Javier Luis Canovas and Cabot, Jordi}
}
@article {1746,
	title = {Evaluation of FLOSS by Analyzing Its Software Evolution:},
	journal = {Journal of Information Technology Research},
	volume = {8},
	year = {2015},
	month = {01/2015},
	pages = {62 - 81},
	abstract = {In today{\textquoteright}s world, management often rely on FLOSS (Free/Libre/Open Source Software) systems to run their organizations. However, the nature of FLOSS is different from the software they have been using in the last decades. Its development model is distributed, and its authors are diverse as many volunteers and companies may collaborate in the project. In this paper, we want to shed some light on how to evaluate a FLOSS system by looking at the Moodle platform, which is currently the most used learning management system among educational institutions worldwide. In contrast with other evaluation models that have been proposed so far, the one we present is based on retrieving historical information that can be obtained publicly from the Internet, allowing us to study its evolution. As a result, we will show how by using our methodology management can take informed decisions that lower the risk that organizations face when investing in a FLOSS system.  },
	keywords = {free software, LMS, moodle, open source, software engineering, software evaluation, software evolution},
	issn = {1938-7865},
	doi = {10.4018/JITR.2015010105},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Evaluation\%20of\%20FLOSS\%20by\%20Analyzing\%20its\%20Software\%20Evolution\%20-\%20An\%20Example\%20Using\%20the\%20Moodle\%20Platform.pdf},
	author = {Macho, H{\'e}ctor J. and Gregorio Robles and Gonz{\'a}lez-Barahona, Jesus M}
}
@inbook {1734,
	title = {Examining Usability Work and Culture in OSS},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {58-67},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Organizational culture has been recognized as an influential factor affecting the successes and failures of usability work in organizations; however, there is a lack of research on organizational culture in open source software (OSS) development. This paper shows that there are different kinds of cultures in OSS development projects and builds propositions on the relationship between culture and usability work in OSS development projects. Partly those are derived from the literature, partly from an exploratory empirical inquiry. We speculate whether there is an ideal culture type for usability work in OSS development or whether usability work should be modified to fit the different cultures of OSS development projects.
},
	keywords = {culture, empirical study, open source software, Usability},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_6},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_6},
	author = {Rajanen, Mikko and Iivari, Netta},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {roblesestimating,
	title = {Estimating Development Effort in Free/Open Source Software Projects by Mining Software Repositories: A Case Study of OpenStack},
	year = {2014},
	month = {05/2014},
	abstract = {Because of the distributed and collaborative nature of free/open source software (FOSS) projects, the development effort invested in a project is usually unknown, even after the software has been released. However, this information is becoming of major interest, especially - but not only- because of the growth in the number of companies for which FOSS has become relevant for their business strategy. In this paper we present a novel approach to estimate effort by considering data from source code management repositories. We apply our model to the OpenStack project, a FOSS
project with more than 1,000 authors, in which several tens of companies cooperate. Based on data from its repositories and together with the input from a survey answered by more than 100 developers, we show that the model offers a simple, but sound way of obtaining software development estimations
with bounded margins of error.},
	keywords = {effort estimation, openstack},
	url = {http://gsyc.urjc.es/~grex/repro/2014-msr-effort/msr14-robles-estimating-effort.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr14-robles-estimating-effort.pdf},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jesus M and Cervig{\'o}n, Carlos and Capiluppi, Andrea}
}
@conference {Robles:2014:EDE:2597073.2597107,
	title = {Estimating Development Effort in Free/Open Source Software Projects by Mining Software Repositories: A Case Study of OpenStack},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {222{\textendash}231},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Because of the distributed and collaborative nature of free / open source software (FOSS) projects, the development effort invested in a project is usually unknown, even after the software has been released. However, this information is becoming of major interest, especially ---but not only--- because of the growth in the number of companies for which FOSS has become relevant for their business strategy. In this paper we present a novel approach to estimate effort by considering data from source code management repositories. We apply our model to the OpenStack project, a FOSS project with more than 1,000 authors, in which several tens of companies cooperate. Based on data from its repositories and together with the input from a survey answered by more than 100 developers, we show that the model offers a simple, but sound way of obtaining software development estimations with bounded margins of error.
},
	keywords = {effort estimation, free software, mining software repositories, open source, openstack},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597107},
	url = {http://doi.acm.org/10.1145/2597073.2597107},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles_0.pdf},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Cervig{\'o}n, Carlos and Capiluppi, Andrea and Izquierdo-Cort{\'a}zar, Daniel}
}
@conference {1720,
	title = {Evaluating Software Product Quality: A Systematic Mapping Study},
	booktitle = {2014 Joint Conference of the International Workshop on Software Measurement IWSM-MENSURA},
	year = {2014},
	pages = {141 - 151},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Rotterdam, Netherlands},
	abstract = {Evaluating software product quality (SPQ) is an important task to ensure the quality of software products. In this paper a systematic mapping study was performed to summarize the existing SPQ evaluation (SPQE) approaches in literature and to classify the selected studies according to seven classification criteria: SPQE approaches, research types, empirical types, data sets used in the empirical evaluation of these studies, artifacts, SQ models, and SQ characteristics. Publication channels and trends were also identified. 57 papers were selected. The results show that the main publication sources of the papers identified were journals. Data mining techniques are the most frequently approaches reported in literature. Solution proposals were the main research type identified. The majority of the selected papers were history-based evaluations using existing data, which were mainly obtained from open source software projects and domain specific projects. Source code was the main artifacts used by SPQE approaches. Well-known SQ models were mentioned by half of the selected papers and reliability is the SQ characteristic through which SPQE was mainly achieved. SPQE-related subjects seem to attract more interest from researchers since the past years. },
	doi = {10.1109/IWSM.Mensura.2014.30},
	url = {http://www.scielo.org.mx/pdf/cys/v19n3/v19n3a11.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/v19n3a11.pdf},
	author = {Ouhbi, Sofia and Idri, Ali and Aleman, Jose Luis Fernandez and Toval, Ambrosio}
}
@inbook {1615,
	title = {An Exploration of Code Quality in FOSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {181-190},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

It is a widely held belief that Free/Open Source Software (FOSS) development leads to the creation of software with the same, if not higher quality compared to that created using proprietary software development models. However there is little research on evaluating the quality of FOSS code, and the impact of project characteristics such as age, number of core developers, code-base size, etc. In this exploratory study, we examined 110 FOSS projects, measuring the quality of the code and architectural design using code smells. We found that, contrary to our expectations, the overall quality of the code is not affected by the size of the code base, but that it was negatively impacted by the growth of the number of code contributors. Our results also show that projects with more core developers don{\textquoteright}t necessarily have better code quality.
},
	keywords = {Code Quality, FOSS, open source software, success metrics},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_26},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_26},
	author = {Ahmed, Iftekhar and Ghorashi, Soroush and Jensen, Carlos},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Wu:2014:EES:2556420.2556483,
	title = {Exploring the Ecosystem of Software Developers on GitHub and Other Platforms},
	booktitle = {Proceedings of the Companion Publication of the 17th ACM Conference on Computer Supported Cooperative Work \&\#38; Social Computing},
	series = {CSCW Companion {\textquoteright}14},
	year = {2014},
	pages = {265{\textendash}268},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {GitHub provides various social features for developers to collaborate with others. Those features are important for developers to coordinate their work (Dabbish et al., 2012; Marlow et al., 2013). We hypothesized that the social system of GitHub users was bound by system interactions such that contributing to similar code repositories would lead to users following one another on GitHub or vice versa. Using a quadratic assignment procedure (QAP) correlation, however, only a weak correlation among followship and production activities (code, issue, and wiki contributions) was found. Survey with GitHub users revealed an ecosystem on the Internet for software developers, which includes many platforms, such as Forrst, Twitter, and Hacker News, among others. Developers make social introductions and other interactions on these platforms and engage with one anther on GitHub. Due to these preliminary findings, we describe GitHub as a part of a larger ecosystem of developer interactions.
},
	keywords = {ecosystem, follow, github, social connection},
	isbn = {978-1-4503-2541-7},
	doi = {10.1145/2556420.2556483},
	url = {http://doi.acm.org/10.1145/2556420.2556483},
	author = {Wu, Yu and Kropczynski, Jessica and Shih, Patrick C. and Carroll, John M.}
}
@proceedings {1508,
	title = {The Eclipse and Mozilla Defect Tracking Dataset: A Genuine Dataset for Mining Bug Information},
	year = {2013},
	note = {Intended to be an "open bug database" or baseline for multiple studies in the community. 14 bug attributes [id, product, summary, status, etc], some change over time and some do not. Data set: github.com/ansymo/msr2013-bug_dataset},
	month = {05/2013},
	abstract = {The analysis of bug reports is an important subfield within the mining software repositories community. It explores the rich data available in defect tracking systems to uncover interesting and actionable information about the bug triaging process. While bug data is readily accessible from systems like Bugzilla and JIRA, a common database schema and a curated dataset could significantly enhance future research because it allows for easier replication. Consequently, in this paper we propose the Eclipse and Mozilla Defect Tracking Dataset, a representative database of bug data, filtered to contain only genuine defects (i.e., no feature requests) and designed to cover the whole bug-triage life cycle (i.e., store all intermediate actions). We have used this dataset ourselves for predicting bug severity, for studying bug-fixing time and for identifying erroneously assigned components. github.com/ansymo/msr2013-bug_dataset},
	url = {http://github.com/ansymo/msr2013-bug_dataset},
	author = {Lamkanfi, Ahmed and Javier P{\'e}rez and Demeyer, Serge}
}
@book {1544,
	title = {Effect on Business Growth by Utilization and Contribution of Open Source Software in Japanese IT Companies},
	volume = {404},
	year = {2013},
	pages = {222 - 231},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

The expanded use of Open Source Software (OSS), and the expansion of the market caused by this adoption has led to a corresponding increase in the number of businesses acting as stakeholders in the field. Some of these are pure users of OSS technology but a great number are developers of such technology, and can be understood to have a substantial investment in this paradigm. It is reasonable to assume that such businesses are rational actors, and that their investment or contribution to the field implies a positive economic benefit either currently obtained or assumed as a return in the future. This paper analyzes how OSS affects Japanese IT companies{\textquoteright} business growth both through simple use and by deeper engagement as a stakeholder in OSS community. This is the first time that such a link between the utilization of OSS and economic growth has been explored in the context of Japan, and it can hopefully lay a foundation for further study regarding the real economic value of this approach to software.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_16},
	author = {Noda, Tetsuo and Tansho, Terutaka and Coughlan, Shane},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@article {1865,
	title = {The Effects of Diversity in Global, Distributed Collectives: A Study of Open Source Project Success},
	journal = {Information Systems Research},
	volume = {24},
	year = {2013},
	month = {06/2013},
	pages = {312 - 333},
	abstract = {Diversity is a defining characteristic of global collectives facilitated by the Internet. Though substantial evidence suggests that diversity has profound implications for a variety of outcomes including performance, member engagement, and withdrawal behavior, the effects of diversity have been predominantly investigated in the context of organizational workgroups or virtual teams. We use a diversity lens to study the success of nontraditional virtual work groups exemplified by open source software (OSS) projects. Building on the diversity literature, we propose that three types of diversity (separation, variety, and disparity) influence two critical outcomes for OSS projects: community engagement and market success. We draw on the OSS literature to further suggest that the effects of diversity on market success are moderated by the application development stage. We instantiate the operational definitions of three forms of diversity to the unique context of open source projects. Using archival data from 357 projects hosted on SourceForge, we find that disparity diversity, reflecting variation in participants{\textquoteright} contribution-based reputation, is positively associated with success. The impact of separation diversity, conceptualized as culture and measured as diversity in the spoken language and country of participants, has a negative impact on community engagement but an unexpected positive effect on market success. Variety diversity, reflected in dispersion in project participant roles, positively influences community engagement and market success. The impact of diversity on market success is conditional on the development stage of the project. We discuss how the study{\textquoteright}s findings advance the literature on antecedents of OSS success, expand our theoretical understanding of diversity, and present the practical implications of the results for managers of distributed collectives.},
	issn = {1526-5536},
	doi = {10.1287/isre.1120.0435},
	author = {Sherae Daniel and Ritu Agarwal and Stewart, Katherine J.}
}
@book {1535,
	title = {The Emergence of Quality Assurance Practices in Free/Libre Open Source Software: A Case Study},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {271 - 276},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

As the user base of Free/Libre Open Source Software (FLOSS) diversifies, the need for higher quality is becoming more evident. This implies a more complex development model that includes various steps which were previously associated exclusively with proprietary development such as a formal quality assurance step (QA). However, little research has been done on how implementing formal quality assurance impacts the structure of FLOSS communities. This study aims to start filling this gap by analyzing interactions within such a community. Plone is just one among many FLOSS projects that acknowledged the importance of verification by implementing a quality assurance step.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_21},
	author = {Barham, Adina},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1505,
	title = {An Empirical Study of the Fault-Proneness of Clone Mutation and Clone Migration },
	year = {2013},
	month = {05/2013},
	abstract = {When implementing new features into a software system, developers may duplicate several lines of code to reuse some existing code segments. This action creates code clones in the software system. The literature has documented different types of code clone (e.g., Type-1, Type-2, and Type-3). Once created, code clones evolve as they are modified during both the development and maintenance phases of the software system. The evolution of code clones across the revisions of a software system is known as a clone genealogy. Existing work has investigated the fault-proneness of Type-1 and Type-2 clone genealogies. In this study, we investigate clone genealogies containing Type-3 clones. We analyze three long lived software systems APACHE-ANT, ARGOUML, and JBOSS, which are all written in JAVA. Using the NICAD clone detection tool, we build clone genealogies and examine two evolutionary phenomena on clones: the mutation of the type of a clone during the evolution of a system, and the migration of clone segments across the repositories of a software system. Results show that 1) mutation and migration occur frequently in software systems; 2) the mutation of a clone group to Type-2 or Type-3 clones increases the risk for faults; 3) increasing the distance between code segments in a clone group also increases the risk for faults. Index Terms: Types of clones; clone genealogy; clone migration; fault-proneness.},
	author = {Shuai Xie and Foutse Khomh and Ying Zou}
}
@article {syeed2013evolution,
	title = {Evolution of Open Source Software Projects: A Systematic Literature Review},
	journal = {Journal of Software},
	volume = {8},
	number = {11},
	year = {2013},
	pages = {2815{\textendash}2829},
	abstract = {Open Source Software (OSS) is continuously gaining acceptance in commercial organizations. It is in this regard that those organizations strive for a better understanding of evolutionary aspects of OSS projects. The study of evolutionary patterns of OSS projects and communities has received substantial attention from the research community over the last decade. These efforts have resulted in an ample set of research results for which there is a need for up-to-date comprehensive overviews and literature surveys.

This paper reports on a systematic literature survey aimed at the identification and structuring of research on evolution of OSS projects. In this review we systematically selected and reviewed 101 articles published in relevant venues. The study outcome provides insight in what constitutes the main contributions of the field, identifies gaps and opportunities, and distills several important future research directions.},
	keywords = {flosshub},
	attachments = {https://flosshub.org/sites/flosshub.org/files/9913-25310-1-PB.pdf},
	author = {Syeed, Mahbubul and Hammouda, Imed and Syat{\"a}, Tarja}
}
@article {1631,
	title = {The evolution of the laws of software evolution},
	journal = {ACM Computing Surveys},
	volume = {46},
	year = {2013},
	month = {11/2013},
	pages = {1 - 28},
	abstract = { After more than 40 years of life, software evolution should be considered as a mature field. However, despite such a long history, many research questions still remain open, and controversial studies about the validity of the laws of software evolution are common. During the first part of these 40 years the laws themselves evolved to adapt to changes in both the research and the software industry environments. This process of adaption to new paradigms, standards, and practices stopped about 15 years ago, when the laws were revised for the last time. However, most controversial studies have been raised during this latter period. Based on a systematic and comprehensive literature review, in this paper we describe how and when the laws, and the software evolution field, evolved. We also address the current state of affairs about the validity of the laws, how they are perceived by the research community, and the developments and challenges that are likely to occur in the coming years.},
	issn = {03600300},
	doi = {10.1145/2543581.2543595},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2013HerraizRRG_CSUR.pdf},
	author = {Herraiz, Israel and Rodriguez, Daniel and Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@book {1537,
	title = {Exploring Collaboration Networks in Open-Source Projects},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {97 - 108},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Analysis of developer collaboration networks presents an opportunity for understanding and thus improving the software development process. Discovery of these networks, however, presents a challenge since the collaboration relationships are initially not known. In this work we apply an approach for discovering collaboration networks of open source developers from Version Control Systems (VCS). It computes similarities among developers based on common file changes, constructs the network of collaborating developers and applies filtering techniques to improve the readability of the visualized network. We use the approach in case studies of three different projects from open source (phpMyAdmin, Eclipse Data Tools Platform and Gnu Compiler Collection) to learn their organizational structure and patterns. Our results indicate that with little effort the approach is capable of revealing aspects of these projects that were previously not known or would require a lot of effort to discover manually via other means, such as reading project documentation and forums.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_7},
	author = {Jermakovics, Andrejs and Sillitti, Alberto and Succi, Giancarlo},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1469,
	title = {The Effect of Open Source Licensing on the Evolution of Business Strategy},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {344-349},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {This paper explores how the approach underlying Open Source development has encouraged a greater sharing of knowledge in related business and legal affairs, and subsequently leads to the emergence of Open Source-driven collaboration by enterprises to address challenges. We use an Economic approach to propose a theoretical framework for Open Source business analysis and provide a defined sample of real-world developments to support its initial findings. We conclude that the need to develop effective Open Source governance solutions has led to widespread collaboration regarding business and legal challenges by stakeholders in the field, and that this collaboration will increase to improve efficiency as the market matures.},
	author = {Noda, Tetsuo and Tansho, Terutaka and Coughlan, Shane}
}
@conference {1375,
	title = {The Effects of Diversity in Global, Distributed Collectives: A Study of Open Source Project Success},
	booktitle = {Information Systems Research},
	year = {2012},
	abstract = {Diversity is a defining characteristic of global collectives facilitated by the Internet. Though substantial evidence suggests that diversity has profound implications for a variety of outcomes including performance, member engagement, and withdrawal behavior, the effects of diversity have been predominantly investigated in the context of organizational workgroups or virtual teams. We use a diversity lens to study the success of non-traditional virtual work groups exemplified by open source software (OSS) projects. Building on the diversity literature, we propose that three types of diversity (separation, variety and disparity) influence two critical outcomes for OSS projects: community engagement and market success. We draw on the OSS literature to further suggest that the effects of diversity on market success are moderated by the application development stage. We instantiate the operational definitions of three forms of diversity to the unique context of open source projects. Using archival data from 357 projects hosted on SourceForge, we find that disparity diversity, reflecting variation in participants{\textquoteleft} contribution-based reputation, is positively associated with success. The impact of separation diversity, conceptualized as culture and measured as diversity in the spoken language and country of participants, has a negative impact on community engagement but an unexpected positive effect on market success. Variety diversity, reflected in dispersion in project participant roles, positively influences community engagement and market success. The impact of diversity on market success is conditional on the development stage of the project. We discuss how the study{\textquoteleft}s findings advance the literature on antecedents of OSS success, expand our theoretical understanding of diversity, and present the practical implications of the results for managers of distributed collectives.},
	keywords = {diversity, global collectives, open source software},
	attachments = {https://flosshub.org/sites/flosshub.org/files/isr_2012.pdf},
	author = {Daniel, Sherae L. and Ritu Agarwal and Stewart, Katherine J.}
}
@proceedings {1445,
	title = {Emerging Hackerspaces {\textendash} Peer-Production Generation},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {94-111},
	publisher = {IFIP AICT},
	abstract = {This paper describes a peer-production movement, the hackerspace movement, its members and values. The emergence of hackerspaces, fablabs and makerspaces is changing how hacker communities and other like-minded communities function. Thus, an understanding of the nature of hackerspaces helps in detailing the features of contemporary peer-production. Building on previous work on {\textquoteright}fabbing{\textquoteright}, two different sets of results are presented: (1) empirical observations from a longitudinal study of hackerspace participants; and (2) a theoretical description of hacker generations as a larger context in which peer-production can be located. With regard to (1), research data has been collected through prolonged observation of hackerspace communities and two surveys.},
	keywords = {COMMUNITY, fabbing, fablab, hackerspace, makerspace, MOTIVATION, movement, open source, peer-production, Survey, sustainability},
	author = {Moilanen, Jarkko}
}
@conference {1316,
	title = {An Empirical Study of Volunteer Members{\textquoteright} Perceived Turnover in Open Source Software Projects},
	booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences},
	year = {2012},
	note = {"After designing the questionnaire, we conducted a web-based survey by inviting developers working in sourceforge.net and launchpad.net."},
	month = {01/2012},
	pages = {3396-3405},
	abstract = {Turnover of volunteer members and the ensuing instability bring about severe problems to open source software (OSS) projects. To better understand it, we based our study on Herzberg ́s two-factor theory to investigate the influence of hygiene factors on volunteer members ́ dissatisfaction and perceived turnover. After empirically testing the research model, we found shortcomings in project regulation and administration are the key reason for volunteer members ́ dissatisfaction, followed by future rewards and personal needs for software functionalities. By contrast, a possible lack of supportive working relationship among OSS developers was not found to be a trigger for developer dissatisfaction. Dissatisfaction was confirmed to be a significant predictor of perceived turnover. The results demonstrates generalized hygiene factors cannot unreflectively be transferred into the OSS context because volunteer members ́ personal expectation has a weaker influence on perceived turnover than objective attributes of OSS project. Our study further makes suggestions for project administrators.},
	keywords = {developers, launchpad, sourceforge, Survey},
	author = {Yu, Yiqing and Benlian, Alexander and Hess, Thomas}
}
@article {1399,
	title = {The evolution of Java build systems},
	journal = {Empirical Software Engineering},
	volume = {17},
	year = {2012},
	month = {8/2012},
	pages = {578 - 608},
	abstract = {Build systems are responsible for transforming static source code artifacts into executable software. While build systems play such a crucial role in software development and maintenance, they have been largely ignored by software evolution researchers. However, a firm understanding of build system aging processes is needed in order to allow project managers to allocate personnel and resources to build system maintenance tasks effectively, and reduce the build maintenance overhead on regular development activities. In this paper, we study the evolution of build systems based on two popular Java build languages (i.e., ANT and Maven) from two perspectives: (1) a static perspective, where we examine the complexity of build system specifications using software metrics adopted from the source code domain; and (2) a dynamic perspective, where the complexity and coverage of representative build runs are measured. Case studies of the build systems of six open source build projects with a combined history of 172 releases show that build system and source code size are highly correlated, with source code restructurings often requiring build system restructurings. Furthermore, we find that Java build systems evolve dynamically in terms of duration and recursive depth of the directory hierarchy. },
	keywords = {ant, build, maven, scm, source code analysis},
	issn = {1573-7616},
	doi = {10.1007/s10664-011-9169-5},
	author = {McIntosh, Shane and Adams, Bram and Hassan, Ahmed E.}
}
@proceedings {1377,
	title = {Examining Turnover in Open Source Software Projects Using a Logistic Hierarchical Linear Modeling Approach},
	volume = {378},
	year = {2012},
	month = {09/2012},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Developer turnover in open source software projects is a critical and insufficiently researched problem. Previous research has focused on understanding the developer motivations to contribute using either the individual developer perspective or the project perspective. In this exploratory study we argue that because the developers are embedded in projects it is imperative to include both perspectives. We analyze turnover in open source software projects by including both individual developer level factors, as well as project specific factors. Using the Logistic Hierarchical Linear Modeling approach allows us to empirically examine the factors influencing developer turnover and also how these factors differ among developers and projects.},
	keywords = {Logistic Hierarchical Linear Modeling, sourceforge, turnover},
	author = {Sharma, P.N. and Hulland, J. and Daniel, S.}
}
@proceedings {1446,
	title = {Exploring the Barriers and Enablers to the Use of Open Educational Resources by University Academics in Africa},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {112-128},
	publisher = {IFIP AICT},
	abstract = {Considerable effort has gone into Open Educational Resource (OER) initiatives in the past decade. These initiatives have created free, high quality educational resources for everyone and anyone to use. However, these open and free resources appear to remain largely unused by university academics on the educationally resource-poor African continent. The objectives of the research study are to explore the inhibitors and enablers are experienced by academics that use OER, and what barriers prevent academics from using OER. The sample consists of academics from East, West and Southern Africa. Information was gathered by means of a survey questionnaire. A modified version of the Unified Theory of Acceptance and Use of Technology model was used to identify the influence of certain factors on a user{\textquoteright}s intention to adopt OER. Some of the key findings indicate that Performance Expectancy and Effort Expectancy have a positive effect on a user{\textquoteright}s Behavioural Intention to use OER, and the latter has a strong influence on the Actual Use of OER. Facilitating Conditions do not have a statistically significant impact. Additionally, significant differences were found in the barriers which users and potential users of OER have identified as either limiting their current use of OER, or negatively affecting their intention to use OER. These barriers include discovery, relevance, context and individual resources. Addressing these factors could lead to a more widespread adoption of Open Educational Resources in Africa and, consequently, more pervasive and higher quality educational opportunities.},
	author = {Percy, Tanya and Van Belle, Jean-Paul}
}
@proceedings {1450,
	title = {Exploring the Role of Commercial Stakeholders in Open Source Software Evolution},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {178-200},
	publisher = {IFIP AICT},
	abstract = {It has been lately established that a major success or failure factor of an OSS project is whether or not it involves a commercial company, or more extremely, when a project is managed by a commercial software corporation. As documented recently, the success of the Eclipse project can be largely attributed to IBM{\textquoteright}s project management, since the upper part of the developer hierarchy is dominated by its staff. This paper reports on the study of the evolution of three different Open Source (OSS) projects {\textemdash} the Eclipse and jEdit IDEs and the Moodle e-learning system {\textemdash} looking at whether they have benefited from the contribution of commercial companies. With the involvement of commercial companies, it is found that OSS projects achieve sustained productivity, increasing amounts of output produced and intake of new developers. It is also found that individual and commercial contributions show similar stages: developer intake, learning effect, sustained contributions and, finally, abandonment of the project. This preliminary evidence suggests that a major success factor for OSS is the involvement of a commercial company, or more radically, when project management is in hands of a commercial entity.},
	author = {Capiluppi, Andrea and Stol, Klaas-Jan and Boldyreff, Cornelia}
}
@proceedings {1451,
	title = {Exploring the Role of Outside Organizations in Free / Open Source Software Projects},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {201-215},
	publisher = {IFIP AICT},
	abstract = {Free/Open Source Software (FOSS) projects have a reputation for being grass-roots efforts driven by individual contributors volunteering their time and effort. While this may be true for a majority of smaller projects, it is not always the case for large projects. As projects grow in size, importance and complexity, many come to depend on corporations, universities, NGO{\textquoteright}s and governments, for support and contributions, either financially or through seconded staff. As outside organizations get involved in projects, how does this affect their governance, transparency and direction? To study this question we gathered bug reports and commit logs for GCC and the Linux Kernel. We found that outside organizations contribute a majority of code but rarely participate in bug triaging. Therefore their code does not necessarily address the needs of others and may distort governance and direction. We conclude that projects should examine their dependence on outside organizations},
	keywords = {bug reports, commit, Community sustainability, Contributor affiliation, gcc, governance, linux kernel, Participation metrics},
	url = {http://research.engr.oregonstate.edu/hci/sites/research.engr.oregonstate.edu.hci/files/papers/forrest2012exploring.pdf},
	author = {Forrest, Darren and Jensen, Carlos and Mohan, Nitin and Davidson, Jennifer}
}
@article {1418,
	title = {Effort estimation of FLOSS projects: a study of the Linux kernel},
	journal = {Empirical Software Engineering},
	year = {2011},
	pages = {1-29},
	abstract = {Empirical research on Free/Libre/Open Source Software (FLOSS) has shown that developers tend to cluster around two main roles: {\textquotedblleft}core{\textquotedblright} contributors differ from {\textquotedblleft}peripheral{\textquotedblright} developers in terms of a larger number of responsibilities and a higher productivity pattern. A further, cross-cutting characterization of developers could be achieved by associating developers with {\textquotedblleft}time slots{\textquotedblright}, and different patterns of activity and effort could be associated to such slots. Such analysis, if replicated, could be used not only to compare different FLOSS communities, and to evaluate their stability and maturity, but also to determine within projects, how the effort is distributed in a given period, and to estimate future needs with respect to key points in the software life-cycle (e.g., major releases). This study analyses the activity patterns within the Linux kernel project, at first focusing on the overall distribution of effort and activity within weeks and days; then, dividing each day into three 8-hour time slots, and focusing on effort and activity around major releases. Such analyses have the objective of evaluating effort, productivity and types of activity globally and around major releases. They enable a comparison of these releases and patterns of effort and activities with traditional software products and processes, and in turn, the identification of company-driven projects (i.e., working mainly during office hours) among FLOSS endeavors. The results of this research show that, overall, the effort within the Linux kernel community is constant (albeit at different levels) throughout the week, signalling the need of updated estimation models, different from those used in traditional 9am{\textendash}5pm, Monday to Friday commercial companies. It also becomes evident that the activity before a release is vastly different from after a release, and that the changes show an increase in code complexity in specific time slots (notably in the late night hours), which will later require additional maintenance efforts.},
	keywords = {complexity, effort estimation, Effort models, mining software repositories, open source software},
	issn = {1573-7616},
	doi = {10.1007/s10664-011-9191-7},
	url = {http://www.springerlink.com/content/612r616k8t52m867/fulltext.html},
	author = {Capiluppi, Andrea and Izquierdo-Cort{\'a}zar, Daniel}
}
@article {1320,
	title = {An Empirical Study of Open Source Software Usability},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {1 - 16},
	abstract = {Recent years have seen a sharp increase in the use of open source projects by common novice users; Open Source Software (OSS) is thus no longer a reserved arena for software developers and computer gurus. Although user-centered designs are gaining popularity in OSS, usability is still not considered one of the prime objectives in many design scenarios. This paper analyzes industry users{\textquoteright} perception of usability factors, including understandability, learnability, operability, and attractiveness on OSS usability. The research model of this empirical study establishes the relationship between the key usability factors and OSS usability from industrial perspective. In order to conduct the study, a data set of 105 industry users is included. The results of the empirical investigation indicate the significance of the key factors for OSS usability.},
	keywords = {Survey},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011010101},
	author = {Raza, Arif and Capretz, Luiz Fernando and Ahmed, Faheem}
}
@article {1806,
	title = {An empirical study of software architectures{\textquoteright} effect on product quality},
	journal = {Journal of Systems and Software},
	volume = {84},
	year = {2011},
	note = {"We first collected meta-data on the 21,094 most highly ranked Java projects on 2009-03-17 from SourceForge for which it was possible to get such data. Here {\textquotedblleft}Java projects{\textquotedblright} were defined as projects belonging to {\textquotedblleft}trove{\textquotedblright} 198 at SourceForge and {\textquotedblleft}rank{\textquotedblright} was the SourceForge ranking of projects. The data consisted of characteristics such as number of bugs, time of latest file upload, number of developers, number of open bugs, and SourceForge {\textquotedblleft}rank{\textquotedblright}." They did not use FLOSSmole, "A more complete analysis of the project status, could be performed by mining the FLOSSMole database (Howison et al., 2006)."},
	month = {7/2011},
	pages = {1233 - 1243},
	abstract = {Software architecture is concerned with the structure of software systems and is generally agreed to influence software quality. Even so, little empirical research has been performed on the relationship between software architecture and software quality. Basedon 1,141 open source Java projects, we calculate three software architecture metrics (measuring classes per package, normalizeddistance, and a new metric introduced by us concerning the excess of coupling degree) and analyze to which extent these metricsare related to product metrics (defect ratio, download rate, methods per class, and method complexity). We conclude that there area number of significant relationships between product metrics and architecture metrics.  In particular, the number of open defectsdepends significantly on all our architecture measures.},
	keywords = {flossmole cited, java},
	issn = {01641212},
	doi = {10.1016/j.jss.2011.02.037},
	url = {http://www.sciencedirect.com/science/article/pii/S0164121211000574},
	author = {Hansen, Klaus Marius and Jonasson, Kristjan and Neukirchen, Helmut}
}
@conference {1304,
	title = {Entering the circle of trust},
	booktitle = {Proceeding of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"we started by analyzing 219 projects"
},
	month = {05/2011},
	pages = {133-142},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {The success of an open-source project depends to a large degree on the proactive and constructive participation by the developer community. An important role that developers play in a project is that of a code committer. However, code-commit privilege is typically restricted to the core group of a project. In this paper, we study the phenomenon of the induction of external developers as code committers. The trustworthiness of an external developer is one of the key factors that determines the granting of commit privileges. Therefore, we formulate different hypotheses to explain how the trust is established in practice. To investigate our hypotheses, we developed an automated approach based on mining code repositories and bug-tracking systems. We implemented the approach and performed an empirical study, using the Eclipse projects, to test the hypotheses. Our results indicate that, most frequently, developers establish trust and credibility in a project by contributing to the project in a non-committer role. Moreover, the employing organization of a developer is another factor--although a less significant one--that influences trust.},
	keywords = {bug tracking, bug tracking system, commits, committers, core, developers, eclipse, trust},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985462},
	author = {Mani, Senthil and Sinha, Saurabh and Sinha, Vibha Singhal}
}
@conference {1216,
	title = {Experiences Mining Open Source Release Histories},
	booktitle = {International Conference on Software and Systems Process (ICSSP 2011) },
	year = {2011},
	note = {"First, we selected the projects to initially target, using several criteria to get a broad picture of the open source landscape. Second, we collected the actual data, using a framework of parsers and some manual inspection. Third, we standardized and inserted the data into a database for later use."

"but we plan to eventually cross reference our list of projects with existing open source project information (such as FLOSSmole) to take advantage of the work already done by other researchers."

"For each release, we collected the following data: the project it belonged to, the date the release was published, the type of release, the release label (version number) and the source of the data"

discussion of their difficulties

"We conclude that programmatically creating a release history database from existing open source data is not trivial,"

"We have currently collected 1579 distinct releases from 22 different open source projects"},
	month = {05/2011},
	abstract = {Software releases form a critical part of the life cycle of a software project. Typically, each project produces releases in its own way, using various methods of versioning, archiving, announcing and publishing the release. Understanding the release history of a software project can shed light on the project history, as well as the release process used by that project, and how those processes change. However, many factors make automating the retrieval of release history information difficult, such as the many sources of data, a lack of relevant standards and a disparity of tools used to create releases.

In spite of the large amount of raw data available, no attempt has been made to create a release history database of a large number of projects in the open source ecosystem. This paper presents our experiences, including the tools, techniques and pitfalls, in our early work to create a software release history database which will be of use to future researchers who want to study and model the release engineering process in greater depth.},
	keywords = {doap, flossmole cited, life cycle, release engineering, release history, release management, releases},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icssp11short-p034-tsay.pdf},
	author = {Jason Tsay and Wright, Hyrum and Perry, Dewayne}
}
@conference {Bacchelli:2011:EEE:1985793.1985999,
	title = {Exploring, exposing, and exploiting emails to include human factors in software engineering},
	booktitle = {Companion to the Proceedings of the 33rd International Conference on Software Engineering},
	series = {ICSE {\textquoteright}11},
	year = {2011},
	note = {This paper is a summary of work in the field, for the doctoral consortium.},
	pages = {1074{\textendash}1077},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Researchers mine software repositories to support software maintenance and evolution. The analysis of the structured data, mainly source code and changes, has several benefits and offers precise results. This data, however, leaves communication in the background, and does not permit a deep investigation of the human factor, which is crucial in software engineering.

Software repositories also archive documents, such as emails or comments, that are used to exchange knowledge among people - we call it "people-centric information." By covering this data, we include the human factor in our analysis, yet its unstructured nature makes it currently sub-exploited.

Our work, by focusing on email communication and by implementing the necessary tools, investigates methods for exploring, exposing, and exploiting unstructured data. We believe it is possible to close the gap between development and communication, extract opinions, habits, and views of developers, and link implementation to its rationale; we see in a future where software analysis and development is routinely augmented with people-centric information.},
	keywords = {email communication, toolset, unstructured data},
	isbn = {978-1-4503-0445-0},
	doi = {10.1145/1985793.1985999},
	url = {http://doi.acm.org/10.1145/1985793.1985999},
	author = {Bacchelli, Alberto}
}
@article {1856,
	title = {The Economic Case for Open Source Foundations},
	journal = {Computer},
	volume = {43},
	year = {2010},
	month = {01/2010},
	pages = {86 - 90},
	abstract = {An open source foun-da-tion is a group of peo-ple and com-pa-nies that has come together to jointly develop com-mu-nity open source soft-ware. Exam-ples include the Apache Soft-ware Foun-da-tion, the Eclipse Foun-da-tion, and the Gnome Foun-da-tion. There are many rea-sons why soft-ware devel-op-ment firms join and sup-port a foun-da-tion. One com-mon eco-nomic moti-va-tion is to save costs in the devel-op-ment of the soft-ware by spread-ing them over the par-tic-i-pat-ing par-ties. How-ever, this is just the begin-ning. Beyond shar-ing costs, par-tic-i-pat-ing firms can increase their rev-enue through the pro-vi-sion and increased sale of com-ple-men-tary prod-ucts. Also, by estab-lish-ing a suc-cess-ful open source plat-form, soft-ware firms can com-pete more effec-tively across tech-nol-ogy stacks and thereby increase their address-able mar-ket. Not to be neglected, com-mu-nity open source soft-ware is a com-mon good, cre-at-ing increased gen-eral wel-fare and hence good-will for the involved com-pa-nies.},
	issn = {0018-9162},
	doi = {10.1109/MC.2010.24},
	url = {http://dirkriehle.com/2010/01/06/the-economic-case-for-open-source-foundations/},
	author = {Dirk Riehle}
}
@conference {951,
	title = {The evolution of ANT build systems},
	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 = {42 - 51},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Build systems are responsible for transforming static source code artifacts into executable software. While build systems play such a crucial role in software development and maintenance, they have been largely ignored by software evolution researchers. With a firm understanding of build system aging processes, project managers could allocate personnel and resources to build system maintenance tasks more effectively, reducing the build maintenance overhead on regular development activities. In this paper, we study the evolution of ANT build systems from two perspectives: (1) a static perspective, where we examine the build system specifications using software metrics adopted from the source code domain; and (2) a dynamic perspective where representative sample build runs are conducted and their output logs are analyzed. Case studies of four open source ANT build systems with a combined history of 152 releases show that not only do ANT build systems evolve, but also that they need to react in an agile manner to changes in the source code.},
	keywords = {ant, argouml, build, eclipse, jboss, maintenance, metrics, source code, tomcat},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463341},
	attachments = {https://flosshub.org/sites/flosshub.org/files/42msr2010_mcintosh.pdf},
	author = {McIntosh, Shane and Adams, Bram and Hassan, Ahmed E.}
}
@conference {1258,
	title = {Exploring Complexity in Open Source Software: Evolutionary Patterns, Antecedents, and Outcomes},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)},
	year = {2010},
	note = {"The sample of projects was drawn from SourceForge"
"projects were selected that were built with C++."
"Applying the selection criteria generated a total of 108 projects for analysis"
"Scientific Toolwork{\textquoteright}s Understand (version 1.4)"},
	pages = {1 - 11},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {Software complexity is important to researchers and managers, yet much is unknown about how complexity evolves over the life of a software application and whether different dimensions of software complexity may exhibit similar or different evolutionary patterns. Using cross-sectional and longitudinal data on a sample of 108 open source projects, this research investigated how the complexity of open source project releases varied throughout the life of the project. Functional data analysis was applied to the release histories of the projects and recurring evolutionary patterns were derived. There were projects that saw little evolution, according to their measures of size and structural complexity. However, projects that displayed some evolution often differed on the pattern of evolution depending on whether size or structural complexity was examined. Factors that contribute to and result from the patterns of complexity were evaluated, and implications for research and practice are presented.},
	keywords = {complexity, evolution, fda, life cycle, sourceforge, srda},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.198},
	attachments = {https://flosshub.org/sites/flosshub.org/files/10-07-02.pdf},
	author = {Darcy, David P. and Daniel, Sherae L. and Stewart, Katherine J.}
}
@conference {950,
	title = {An extensive comparison of bug prediction approaches},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {31 - 41},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Reliably predicting software defects is one of software engineering{\textquoteright}s holy grails. Researchers have devised and implemented a plethora of bug prediction approaches varying in terms of accuracy, complexity and the input data they require. However, the absence of an established benchmark makes it hard, if not impossible, to compare approaches. We present a benchmark for defect prediction, in the form of a publicly available data set consisting of several software systems, and provide an extensive comparison of the explanative and predictive power of well-known bug prediction approaches, together with novel approaches we devised. Based on the results, we discuss the performance and stability of the approaches with respect to our benchmark and deduce a number of insights on bug prediction models.},
	keywords = {apache, bug reports, eclipse, famix, lucene, mylyn, prediction, scm},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463279},
	attachments = {https://flosshub.org/sites/flosshub.org/files/31dambrosLanzaRobbes31.pdf},
	author = {D{\textquoteright}Ambros, Marco and Lanza, Michele and Robbes, Romain}
}
@conference {1358,
	title = {Extracting source code from e-mails},
	booktitle = {Proceedings of ICPC 2010 (18th IEEE International Conference on Program Comprehension)},
	year = {2010},
	note = {"We want to extract source code fragments from e-mail messages. To do this, we first need to select e-mails that contain source code fragments, and then we extract such fragments from the content in which they are enclosed."

"we manually build a statistically significant benchmark taking sample e- mails from five unrelated open source Java software systems."

},
	pages = {24-33},
	abstract = {E-mails, used by developers and system users to communicate over a broad range of topics, offer a valuable source of information. If archived, e-mails can be mined to support program comprehension activities and to provide views of a software system that are alternative and complementary to those offered by the source code.

However, e-mails are written in natural language, and therefore contain noise that makes it difficult to retrieve the important data. Thus, before conducting an effective system analysis and extracting data for program comprehension, it is necessary to select the relevant messages, and to expose only the meaningful information.

In this work we focus both on classifying e-mails that hold fragments of the source code of a system, and on extracting the source code pieces inside the e-mail. We devised and analyzed a number of lightweight techniques to accomplish these tasks. To assess the validity of our techniques, we manually inspected and annotated a statistically significant number of e-mails from five unrelated open source software systems written in Java. With such a benchmark in place, we measured the effectiveness of each technique in terms of precision and recall.},
	keywords = {argouml, email, freenet, jmeter, mailing lists, mina, natural language, openjpa, source code},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icpc2010.pdf},
	author = {Bacchelli, Alberto and D{\textquoteright}Ambros, Marco and Lanza, Michele}
}
@article {10.1109/HICSS.2009.687,
	title = {Easier Said than Done: An Empirical Investigation of Software Design and Quality in Open Source Software Development},
	journal = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	note = {"projects that do not exhibit obvious corporate or organizational sponsorship or involvement, projects with at least one software release in a relatively mature development stage (Beta or Production/Stable), projects exhibiting a minimum level of project activity, and products written only using Java."
"The frame includes approximately 180 projects from which a random sample of 46 was drawn"
"For each project, we sample each major software release (e.g. 1.x, 2.x) as our unit of analysis for a total of 203 releases."
"We calculate the degree of modularity for each major software release sampled using the source code contained in each release"
"To measure intrinsic software quality, we calculate the number of static bugs and software complexity based on objective evaluations of the source code included in the software release using two static source code analysis tools"
"To assess customer satisfaction, we use three measures of software quality previously identified in OSS research as a proxy for software quality and OSS project success [3]: number of bugs reported, percentage of bugs closed, and time to close bugs."},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {We empirically examine the relationship between software design modularity and software quality in open source software (OSS) development projects. Conventional wisdom suggests that degree of software modularity affects software quality. An analysis of 203 software releases in 46 OSS projects hosted on SourceForge.net lends support for a more complex relationship between software modularity and software quality than conventional wisdom suggests. We find that software modularity is associated with reduced software complexity, an increased number of static software bugs, and a mixed relationship with the percentage of bugs closed. We do not find empirical evidence supporting any relationship between modularity and other measures of customer satisfaction. In addition to empirically testing the relationship between modularity and quality, we introduce new measures of software modularity and software quality. Implications are developed for the theory of modularity and the practice of software development.},
	keywords = {modularity, quality, source code, sourceforge},
	isbn = {978-0-7695-3450-3},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.687},
	attachments = {https://flosshub.org/sites/flosshub.org/files/09-14-05.pdf},
	author = {Conley, Caryn A. and Lee Sproull}
}
@conference {585,
	title = {An Empirical Study of the Reuse of Software Licensed under the GNU General Public License},
	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 = {185 - 198},
	publisher = {Springer},
	organization = {Springer},
	chapter = {17},
	abstract = {Software licensing is a complex issue in free and open source software (FOSS), specially when it involves the redistribution of derived works. The creation of derivative works created from components with different FOSS licenses poses complex challenges, particularly when one of the components is licensed under the terms of one of the versions of the GNU General Public License (GPL). This paper describes an empirical study of the manner in which GPLed licensed software is combined with components under different FOSS licenses. We have discovered that FOSS software developers have found interesting methods to create derivative works with GPLed software that legally circumvent the apparent restrictions of the GPL. In this paper we document these methods and show that FOSS licenses interact in complex and unexpected ways. In most of these cases the goal of the developers (both licensors and licensees) is to further increase the commons of FOSS.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_17},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Empirical\%20Study\%20of\%20the\%20Reuse\%20of\%20Software.pdf},
	author = {German, Daniel and Gonz{\'a}lez-Barahona, Jes{\'u}s}
}
@article {838,
	title = {Envisioning National and International Research on the Multidisciplinary Empirical Science of Free/Open Source Software},
	year = {2009},
	month = {Spring 2009},
	author = {Walt Scacchi and Kevin Crowston and Madey, Greg and Squire, Megan}
}
@conference {579,
	title = {Estimating Commit Sizes Efficiently},
	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 = {105 - 115},
	publisher = {Springer},
	organization = {Springer},
	chapter = {11},
	abstract = {The quantitative analysis of software projects can provide insights that let us better understand open source and other software development projects. An important variable used in the analysis of software projects is the amount of work being contributed, the commit size. Unfortunately, post-facto, the commit size can only be estimated, not measured. This paper presents several algorithms for estimating the commit size. Our performance evaluation shows that simple, straightforward heuristics are superior to the more complex text-analysis-based algorithms. Not only are the heuristics significantly faster to compute, they also deliver more accurate results when estimating commit sizes. Based on this experience, we design and present an algorithm that improves on the heuristics, can be computed equally fast, and is more accurate than any of the prior approaches.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_11},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Estimating\%20Commit\%20Sizes\%20Effciently.pdf},
	author = {Hofmann, Philipp and Dirk Riehle}
}
@article {10.1109/HICSS.2009.713,
	title = {Evaluating Longitudinal Success of Open Source Software Projects: A Social Network Perspective},
	journal = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	note = {"We collect data of various OSS projects over an extended period of 13 months and utilize cross-sectional time-series panel data analysis methods..."
"we observe and analyze the developers{\textquoteright} interactions through bug, patch, support request, and feature request (BPSF) tracking systems hosted on SourceForge.net"
"Three criteria are adopted to select useful projects: projects are selected from top 7000 ranked projects; projects have at least three developers; and there are enough interactions to ensure that each sociomatrix is equal to or larger than 3{\texttimes}3 matrix..."},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {To date, numerous open source projects are hosted on many online repositories. While some of these projects are active and thriving, some projects are either languishing or showing no development activities at all. This phenomenon thus begs the important question of what are the influential factors that affect the success of open source projects. In a quest to deepen our understanding of the evolution of open source projects, this research aims to analyze the success of open source projects by using the theoretical lens of social network analysis. Based on extensive analyses of data collected from online repositories, we study the impact of the communication patterns of software development teams on the demand and supply outcomes of these projects, while accounting for project-specific characteristics. Using panel data analysis of data over 13 months, we find significant impacts of communication patterns on project outcomes over the long term.},
	keywords = {bug tracking system, communication, project success, social network analysis, sourceforge},
	isbn = {978-0-7695-3450-3},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.713},
	attachments = {https://flosshub.org/sites/flosshub.org/files/09-02-12.pdf},
	author = {Jing Wu and Khim Yong Goh}
}
@conference {931,
	title = {Evaluating process quality in GNOME based on change request data},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {95 - 98},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {The lifecycle of defects reports and enhancement requests collected in the Bugzilla database of the GNOME project provides valuable information on the evolution of the change request process and for the assessment of process quality in the GNOME sub projects. We present a quality model for the analysis of quality characteristics that is based on evaluating metrics on the Bugzilla database, and illustrate it with a comparative evaluation for 25 of the largest products within GNOME.},
	keywords = {bugzilla, bugzillametrics.org, change analysis, change history, gnome, msr challenge, qmetric},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069485},
	attachments = {https://flosshub.org/sites/flosshub.org/files/95ProcessQualityInGNOME.pdf},
	author = {Schackmann, Holger and Lichter, Horst}
}
@conference {941,
	title = {Evolution of the core team of developers in libre software projects},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {167 - 170},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {In many libre (free, open source) software projects, most of the development is performed by a relatively small number of persons, the "core team". The stability and permanence of this group of most active developers is of great importance for the evolution and sustainability of the project. In this position paper we propose a quantitative methodology to study the evolution of core teams by analyzing information from source code management repositories. The most active developers in different periods are identified, and their activity is calculated over time, looking for core team evolution patterns.},
	keywords = {core, cvs, cvsanaly, developers, evolution, gimp, scm},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069497},
	attachments = {https://flosshub.org/sites/flosshub.org/files/167core-evolution.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Herraiz, Israel}
}
@conference {1646,
	title = {An Examination of the Use of Open Source Software Processes as a Global Software Development Solution for Commercial Software Engineering},
	booktitle = {2009 35th Euromicro Conference on Software Engineering and Advanced Applications},
	year = {2009},
	pages = {20 - 27},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Patras, Greece},
	abstract = {This paper outlines the phenomenon of Inner Source software development and places it in the context of existing open source literature. Our study includes an analysis of multiple case studies of Inner Source in use in large scale global software development companies. The lessons learned from these case studies help us to contrast traditional open source principles with Inner Source principles, and we then gather these lessons, to create our preliminary framework, in order to make sense of when and how firms can adopt Inner Source. Our framework helps to make sense of the practical issues of adopting and managing Inner Source. We have highlighted the emerging trends in the Inner Source phenomenon and surrounding areas. Awareness of this may be of great benefit to researchers in the area and industrial practitioners.},
	isbn = {978-0-7695-3784-9},
	doi = {10.1109/SEAA.2009.86},
	author = {Gaughan, Gary and Fitzgerald, Brian and Maha Shaikh}
}
@conference {1262,
	title = {An Exploratory Study on the Two New Trends in Open Source Software: End-Users and Service},
	booktitle = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	note = {used sourceforge data
"We created our dataset by restricting our attention to projects that have production/stable and mature development status"
"we limited our sample to two categories: developers and end-users/desktop"
"We manually compiled a total of 200 projects, 100 each of the most downloaded projects from developers and end-users/desktop categories during the period of March 4 to March 23, 2008. "},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, Hawaii, USA},
	abstract = {Many have been envisaging the emergence of Open Source Software (OSS) for general end-users and the enhancements in providing services and support, as the most critical factors for OSS success, and at the same time, the most critical issues which are holding back the OSS movement. While these two distinct waves in OSS evolution have become more observable, researchers have not yet explored the characteristics of these two distinct new waves. The current study found evidence for these two waves and further explored the two waves by empirically examining two hundred projects hosted in Sourceforge.net. We compared the characteristics of OSS projects that are intended for two disparate audiences: developers and end-users and found that projects for end-users supported more languages but also had more restrictive licenses as compared to projects for developers.},
	keywords = {developers, intended audiences, sourceforge},
	isbn = {978-0-7695-3450-3},
	doi = {10.1109/HICSS.2009.63},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-05.pdf},
	author = {Namjoo Choi and Chengular-Smith, I.}
}
@article {Koch2008345,
	title = {Effort modeling and programmer participation in open source software projects},
	journal = {Information Economics and Policy (Empirical Issues in Open Source Software)},
	volume = {20},
	number = {4},
	year = {2008},
	note = {"Using a two-step approach, first a detailed case study on one project, GNOME, will be undertaken, then a large data set retrieved from a project hosting site, SourceForge.net, will be used to validate the results."

CVS was the main source of data

"e-mails sent to the different project discussion lists were identified as an additional source of information especially on communication and coordination besides the CVS-repository"

basic counts were calculated for developer discussion levels},
	month = {12/2008},
	pages = {345 - 355},
	abstract = {This paper develops models for programmer participation and effort estimation in open source software projects and employs the results to assess the efficiency of open source software creation. Successful development of such models will be important for decision makers of various kinds. We propose hypotheses based on a prior case study on manpower function and effort modeling. A large data set retrieved from a project repository is used to test these hypotheses. The main results are that if Norden-Rayleigh-based approaches are used, they need to be complemented in order to account for the addition of new features during a product life cycle, and that programmer-participation based effort models result in distinctly lower estimations of effort than those based on output metrics, such as lines of code.},
	keywords = {cvs, developers, email, email archives, gnome, lines of code, scm, Software repository mining, source code, sourceforge},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.06.004},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4SSND1J-1/2/c857fa1493e19aa7fe4297dedb077b3a},
	attachments = {https://flosshub.org/sites/flosshub.org/files/KochEffortModeling.pdf},
	author = {Koch, Stefan}
}
@proceedings {865,
	title = {Emerging Issues in the Acquisition of Open Source Software within the U.S. Department of Defense},
	volume = {1},
	year = {2008},
	month = {06/2008},
	pages = {230-244},
	address = {Naval Postgraduate School, Monterey, CA},
	author = {Alspaugh, Thomas and Walt Scacchi}
}
@inbook {866,
	title = {Emerging Patterns of Intersection and Segmentation when Computerization Movements Interact},
	booktitle = {Computerization Movements and Technology Diffusion: From Mainframes to Ubiquitous Computing},
	year = {2008},
	pages = {381-404},
	publisher = { Information Today, Inc.},
	organization = { Information Today, Inc.},
	author = {Walt Scacchi},
	editor = {Kraemer, K.L. and Elliott, M.}
}
@conference {542,
	title = {Empirical Analysis of the Bug Fixing Process in Open Source Projects},
	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 = {187 - 196},
	publisher = {Springer},
	organization = {Springer},
	chapter = {15},
	abstract = {Monitoring the performance of processes is often considered critical in classic engineering fields. However, in the area of software engineering (and especially in the Open Source context) it seems that the literature has not yet taken into consideration the problem of identifying the process characteristics and performance of debugging. The aim of this paper is the identification of the performance characteristics of the bug fixing process of Open Source applications, focusing on continuity and efficiency indicators. The importance of such indicators is even more relevant today, since Open Source software is now adopted also in many business contexts. We have analyzed the debugging process of 9 active and popular Open Source projects, collecting a dataset comprising more than 65,000 closed bugs. Results have highlighted four types of bug fixing processes that can be distinguished by considering temporal continuity and efficiency dimensions.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_15},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Empirical\%20Analysis\%20of\%20the\%20Bug\%20Fixinf\%20Process.pdf},
	author = {Francalanci, Chiara and Merlo, Francesco}
}
@booklet {480,
	title = {An Empirical Investigation into the Adoption of Open Source Software in Hospitals},
	year = {2008},
	month = {October},
	abstract = {Open source software (OSS) has gained considerable attention recently in health care. Yet, how and why OSS is being adopted within hospitals in particular remains a poorly understood issue. This research attempts to further this understanding. A mixed-method research approach was used to explore the extent of OSS adoption in hospitals as well as the factors facilitating and inhibiting adoption. The findings suggest a very limited adoption of OSS in hospitals. Hospitals tend to adopt general-purpose instead of domain-specific OSS. We found that software vendors are the critical factor facilitating the adoption of OSS in hospitals. Conversely, lack of in-house development, as well as a perceived lack of security, quality, and accountability of OSS products were factors inhibiting adoption. An empirical model is presented to illustrate the factors facilitating and inhibiting the adoption of OSS in hospitals.},
	author = {Gilberto Munoz and Carolyn Seaman}
}
@article {1100,
	title = {An Empirical Study on the Relationship Between Software Design Quality, Development Effort and Governance in Open Source Projects},
	journal = {IEEE Transactions on Software Engineering},
	volume = {34},
	year = {2008},
	note = {"empirical data from a sample of 75 major OS projects"
no PDF to confirm [ms]},
	month = {11/2008},
	pages = {765 - 782},
	abstract = {The relationship among software design quality, development effort, and governance practices is a traditional research problem. However, the extent to which consolidated results on this relationship remain valid for open source (OS) projects is an open research problem. An emerging body of literature contrasts the view of open source as an alternative to proprietary software and explains that there exists a continuum between closed and open source projects. This paper hypothesizes that as projects approach the OS end of the continuum, governance becomes less formal. In turn a less formal governance is hypothesized to require a higher-quality code as a means to facilitate coordination among developers by making the structure of code explicit and facilitate quality by removing the pressure of deadlines from contributors. However, a less formal governance is also hypothesized to increase development effort due to a more cumbersome coordination overhead. The verification of research hypotheses is based on empirical data from a sample of 75 major OS projects. Empirical evidence supports our hypotheses and suggests that software quality, mainly measured as coupling and inheritance, does not increase development effort, but represents an important managerial variable to implement the more open governance approach that characterizes OS projects which, in turn, increases development effort.},
	keywords = {effort estimation, governance, quality, source code},
	issn = {0098-5589},
	doi = {10.1109/TSE.2008.68},
	author = {Capra, E. and Francalanci, C. and Merlo, F.}
}
@article {10.1109/TSE.2008.68,
	title = {An Empirical Study on the Relationship Between Software Design Quality, Development Effort and Governance in Open Source Projects},
	journal = {IEEE Transactions on Software Engineering},
	volume = {34},
	year = {2008},
	note = {supplemental material attached},
	pages = {765-782},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {The relationship among software design quality, development effort, and governance practices is a traditional research problem. However, the extent to which consolidated results on this relationship remain valid for open source (OS) projects is an open research problem. An emerging body of literature contrasts the view of open source as an alternative to proprietary software and explains that there exists a continuum between closed and open source projects. This paper hypothesizes that as projects approach the OS end of the continuum, governance becomes less formal. In turn a less formal governance is hypothesized to require a higher-quality code as a means to facilitate coordination among developers by making the structure of code explicit and facilitate quality by removing the pressure of deadlines from contributors. However, a less formal governance is also hypothesized to increase development effort due to a more cumbersome coordination overhead. The verification of research hypotheses is based on empirical data from a sample of 75 major OS projects. Empirical evidence supports our hypotheses and suggests that software quality, mainly measured as coupling and inheritance, does not increase development effort, but represents an important managerial variable to implement the more open governance approach that characterizes OS projects which, in turn, increases development effort.},
	issn = {0098-5589},
	doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.2008.68},
	attachments = {https://flosshub.org/sites/flosshub.org/files/tts2008060765s.pdf},
	author = {Capra, Eugenio and Francalanci, Chiara and Merlo, Francesco}
}
@conference {flosswp1938,
	title = {eResearch Workflows for Studying Free and Open Source Software Development},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275},
	year = {2008},
	month = {July},
	pages = {405{\textendash}411},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper introduces eResearch workflow tools as a model for the research community studying free and open source software and its development. The paper first introduces eResearch as increasingly practiced in fields such as astrophysics and biology, then contrasts the practice of research on free and open source software. After outlining suitable research data sets the paper introduces a class of tools known as scientific workflow frameworks, focusing on one?Taverna?and introducing its features. To further explain the tool a complete workflow used for original research on FLOSS is described. Finally the paper considers the trade-offs inherent in these tools.},
	author = {Howison, James and Andrea Wiggins and Kevin Crowston}
}
@conference {566,
	title = {eResearch Workflows for Studying Free and Open Source Software Development},
	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 = {405 - 411},
	publisher = {Springer},
	organization = {Springer},
	chapter = {39},
	abstract = {This paper introduces eResearch workflow tools as a model for the research community studying free and open source software and its development. The paper first introduces eResearch as increasingly practiced in fields such as astrophysics and biology,then contrasts the practice of research on free and open source software. After outlining suitable research data sets the paper introduces a class of tools known as scientific workflow frameworks, focusing on one{\textemdash}Taverna{\textemdash}and introducing its features.To further explain the tool a complete workflow used for original research on FLOSS is described. Finally the paper considers the trade-offs inherent in these tools.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_39},
	attachments = {https://flosshub.org/sites/flosshub.org/files/eResearch\%20Workflows.pdf},
	author = {Howison, James and Andrea Wiggins and Kevin Crowston}
}
@unpublished {flosswp415,
	title = {eScience for Free/Libre Open Source Software Researchers},
	year = {2008},
	month = {August},
	publisher = {FLOSSpapers},
	type = {Working Paper},
	abstract = {This paper presents a case study of the application of eScience tools and practices for the social science research community studying Free/Libre Open Source Software (FLOSS) development practices. We first describe what we mean by eScience and introduce research on FLOSS to motivate the need for eScience tools and approaches. We then describe our initial efforts to introduce eScience tools for FLOSS research, potential obstacles, and how the use of such tools might affect the practice of research in this field.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/eResearch2008iCS-working.pdf},
	author = {Kevin Crowston and Andrea Wiggins and James Howison}
}
@article {1091,
	title = {Evaluating the performance of open source software projects using data envelopment analysis},
	journal = {Information Management \& Computer Security},
	volume = {16},
	year = {2008},
	note = {"The data set used for this research consists of 34 OSS software projects listed on sourceforge.net." "only highly ranked projects in the security domain were considered."
"Ultimately data were collected on the 34 highest ranked security-based OSS software projects on Sourcefore.net."[sic]
fields: bug (?), developers, rank, downloads, Kperdownload (?)},
	month = {2008},
	pages = {449 - 462},
	abstract = {	

Purpose {\textendash} The purpose of this paper is to develop and test a model of the relative performance of open source software (OSS) projects.

Design/methodology/approach {\textendash} This paper evaluates the relative performance of OSS projects by evaluating multiple project inputs and multiple project outputs by using a data envelopment analysis (DEA) model. The DEA model produces an efficiency score for each project based on project inputs and outputs. The method of producing an efficiency score is based on the convex envelopment technology structure. The efficiency measure quantifies a {\textquotedblleft}distance{\textquotedblright} to an efficient frontier.

Findings {\textendash} The DEA model produced an index of corresponding intensities linking an inefficient project to its benchmark efficient project(s). The inefficiency measures produced an ordering of inefficient projects. Eight projects were found to be {\textquotedblleft}efficient{\textquotedblright} and used as benchmarking projects.

Research limitations/implications {\textendash} This research is limited to only security-based OSS projects. Future research on other areas of OSS projects is warranted.

Practical implications {\textendash} The result of this research is a practical model that can be used by OSS project developers to evaluate the relative performance of their projects and make resource decisions.

Originality/value {\textendash} This research extends the work of previous studies that have examined the relative performance of software development projects in a traditional development environment. As a result of this research, OSS projects can now be adequately benchmarked and evaluated according to project performance. An OSS project manger can effectively use these results to critically evaluate resources for their project and judge the relative efficiency of the resources.},
	keywords = {dea, efficiency, Project performance, sourceforge},
	issn = {0968-5227},
	doi = {10.1108/09685220810920530},
	author = {Wray, Barry and Mathieu, Richard and Teets, J.}
}
@conference {SGKL09,
	title = {Evaluating the Quality of Open Source Software},
	booktitle = {Electronic Notes in Theoretical Computer Science},
	volume = {233},
	year = {2008},
	note = {"the software source code and the associated data stored in the version control system, the bug tracking databases, the mailing lists, and the wikis allow us to evaluate quality in a transparent way"
"The data collection system collects the raw data from open source projects"
Mailing lists are measured in: Number of unique subscribers, Number of messages in user/support list per month, Number of messages in developers list per month, Average thread depth},
	month = {03/2009},
	pages = {5{\textendash}28},
	publisher = {The Reengineering Forum},
	organization = {The Reengineering Forum},
	abstract = {Traditionally, research on quality attributes was either kept under wraps within the organization that performed it, or carried out by outsiders using narrow, black-box techniques. The emergence of open source software has changed this picture allowing us to evaluate both software products and the processes that yield them. Thus, the software source code and the associated data stored in the version control system, the bug tracking databases, the mailing lists, and the wikis allow us to evaluate quality in a transparent way. Even better, the large number of (often competing) open source projects makes it possible to contrast the quality of comparable systems serving the same domain. Furthermore, by combining historical source code snapshots with significant events, such as bug discoveries and fixes, we can further dig into the causes and effects of problems. Here we present motivating examples, tools, and techniques that can be used to evaluate the quality of open source (and by extension also proprietary) software. },
	keywords = {bug tracking system, email, email archives, mailing list, metrics, open source, process quality attributes, product quality attributes, source code, SQO-OSS, wiki},
	doi = {10.1016/j.entcs.2009.02.058},
	url = {http://www.dmst.aueb.gr/dds/pubs/conf/2008-SQM-SQOOSS/html/SGKL09.html},
	attachments = {https://flosshub.org/sites/flosshub.org/files/entcs-sqooss.pdf},
	author = {Diomidis Spinellis and Gousios, Georgios and Vassilios Karakoidas and Panagiotis Louridas and Paul J. Adams and Samoladas, Ioannis and Ioannis Stamelos}
}
@conference {Chang:2008:ESC:1370750.1370766,
	title = {Evaluation of source code copy detection methods on freebsd},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {61{\textendash}66},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Studies have shown that substantial code reuse is common in open source and in commercial projects. However, the precise extent of reuse and its impact on productivity and quality are not well investigated in the open source context. Previously, we have introduced a simple-to-use method that needs only a set of file pathnames to identifies directories that share filenames and partially validated its performance on a set of closed-source projects. To evaluate this method and to improve reuse detection at the file level, we apply it and four additional file copy detection methods that utilize the underlying content of multiple versions of the source code on the FreeBSD project. The evaluation quantified unique advantages of each method and showed that the filename method detected roughly half of all reuse cases. We are still faced with a challenge to scale the content based methods to large repositories containing all versions of open source files.},
	keywords = {clone, cloning, code copying, freebsd, version control},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370766},
	url = {http://doi.acm.org/10.1145/1370750.1370766},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p61-chang.pdf},
	author = {Chang, Hung-Fu and Audris Mockus}
}
@conference {Alonso:2008:EIV:1370750.1370780,
	title = {Expertise identification and visualization from CVS},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {125{\textendash}128},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {As software evolves over time, the identification of expertise becomes an important problem. Component ownership and team awareness of such ownership are signals of solid project. Ownership and ownership awareness are also issues in open-source software (OSS) projects. Indeed, the membership in OSS projects is dynamic with team members arriving and leaving. In large open source projects, specialists who know the system very well are considered experts. How can one identify the experts in a project by mining a particular repository like the source code? Have they gotten help from other people?

We provide an approach using classification of the source code tree as a path to derive the expertise of the committers. Because committers may get help from other people, we also retrieve their contributors. We also provide a visualization that helps to further explore the repository via committers and categories. We present a prototype implementation that describes our research using the Apache HTTP Web server project as a case study.},
	keywords = {apache, classification, committers, components, contributors, expertise, expertise identification, repository, scm, source code},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370780},
	url = {http://doi.acm.org/10.1145/1370750.1370780},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p125-alonso.pdf},
	author = {Alonso, Omar and Premkumar T. Devanbu and Gertz, Michael}
}
@article {Giuri2008305,
	title = {Explaining leadership in virtual teams: The case of open source software},
	journal = {Information Economics and Policy},
	volume = {20},
	number = {4},
	year = {2008},
	note = {Empirical Issues in Open Source Software},
	pages = {305 - 315},
	abstract = {This paper contributes to the open source software (OSS) literature by investigating the likelihood that a participant becomes a project leader. Project leaders are key actors in a virtual community and are crucial to the success of the OSS model. Knowledge of the forces that lead to the emergence of project managers among the multitude of participants is still limited. We aim to fill this gap in the literature by analyzing the association between the roles played by an individual who is registered with a project, and a set of individual-level and project-level characteristics. In line with the theory of occupational choice elaborated by (Lazear, E.P., 2002. Entrepreneurship. NBER Working Paper No. 9109, Cambridge, Mass; Lazear, E.P., 2004. Balanced skills and entrepreneurship, American Economic Review 94, pp. 208-211), we find that OSS project leaders possess diversified skill sets which are needed to select the inputs provided by various participants, motivate contributors, and coordinate their efforts. Specialists, like pure developers, are endowed with more focused skill sets. Moreover, we find that the degree of modularity of the development process is positively associated with the presence of project leaders. That result is consistent with the modern theory of modular production (Baldwin, C.Y., Clark, K.B., 1997. Managing in an age of modularity. Harvard Business Review September-October. pp. 84-93; Mateos-Garcia, J., Steinmueller, W.E., 2003. The Open Source Way of Working: A New Paradigm for the Division of Labour in Software Development? SPRU - Science and Technology Policy Studies. Open Source Movement Research INK Working Paper, No. 1; Aoki, M., 2004. An organizational architecture of T-form: Silicon Valley clustering and its institutional coherence. Industrial and Corporate Change 13, pp. 967-981).},
	keywords = {contributors, Human capital, leadership, roles, sourceforge, team},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.06.002},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4SRW10C-1/2/5ce36096ba3947338962268b54a5a7a9},
	author = {Paola Giuri and Francesco Rullani and Salvatore Torrisi}
}
@conference {1815,
	title = {An Exploratory Study on the Evolution of OSS Developer Communities},
	booktitle = {Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008)},
	year = {2008},
	pages = {305 - 305},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, HI, USA},
	abstract = {Software is developed in a dynamic context where team structure, requirements, and processes evolve together with the product. Although researchers have been studying the evolution of software systems since the early 70s, the study on the evolution of software development teams remains rare. Such evolutionary patterns and their impact on software quality are especially important in the context of OSS (Open Source Software) development, where a group of volunteer developers collaborate online for an extended period of time. By analyzing how social networks of developers evolve over time while building OSS products, we can gain knowledge and experience to improve the effectiveness and efficiency of resource management and distribution in future OSS projects. To this end, we studied the evolution of the developer communities using a suite of OSS products developed under the KOffice project. We found that in general, the social networks of OSS developer communities change over time in certain ways. Identifying such patterns can help OSS managers better understand the unique process of OSS development and improve their management and coordination of the projects.
},
	doi = {10.1109/HICSS.2008.58},
	url = {https://www.researchgate.net/publication/221184171_An_Exploratory_Study_on_the_Evolution_of_OSS_Developer_Communities},
	author = {Ngamkajornwiwat, Kawin and Zhang, Dongsong and Koru, A. Gunes and Zhou, Lina and Nolker, and Robert}
}
@conference {Hata:2008:EFF:1370750.1370772,
	title = {An extension of fault-prone filtering using precise training and a dynamic threshold},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {89{\textendash}98},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Fault-prone module detection in source code is important for assurance of software quality. Most previous fault-prone detection approaches have been based on software metrics. Such approaches, however, have difficulties in collecting the metrics and in constructing mathematical models based on the metrics. To mitigate such difficulties, we have proposed a novel approach for detecting fault-prone modules using a spam-filtering technique, named Fault-Prone Filtering. In our approach, fault-prone modules are detected in such a way that the source code modules are considered as text files and are applied to the spam filter directly. In practice, we use the training only errors procedure and apply this procedure to fault-prone. Since no pre-training is required, this procedure can be applied to an actual development field immediately. This paper describes an extension of the training only errors procedures. We introduce a precise unit of training, "modified lines of code," instead of methods. In addition, we introduce the dynamic threshold for classification. The result of the experiment shows that our extension leads to twice the precision with about the same recall, and improves 15\% on the best F1 measurement.},
	keywords = {eclipse, fault-prone modules, spam filter, text mining},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370772},
	url = {http://doi.acm.org/10.1145/1370750.1370772},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p89-hata.pdf},
	author = {Hata, Hideaki and Mizuno, Osamu and Kikuno, Tohru}
}
@conference {551,
	title = {Extracting Generally Applicable Patterns from Object-Oriented Programs for the Purpose of Test Case Creation},
	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 = {281 - 287},
	publisher = {Springer},
	organization = {Springer},
	chapter = {24},
	abstract = {This paper presents an experiment performed on three large open source applications. The applications were instrumented automatically with a total of 10,494 instrumentation points. The purpose of the instrumentation was to collect and store data during the execution of each application that later could be analyzed off-line. Data analysis, on the collected data, allowed for the creation of test cases (test data, test fixtures and test evaluators) in addition to finding object message patterns for object-oriented software.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_24},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Extracting\%20Generally\%20Applicable\%20Patterns.pdf},
	author = {Torkar, Richard and Feldt, Robert and Gorschek, Tony}
}
@conference {972,
	title = {Extracting structural information from bug reports},
	booktitle = {Proceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {27-30},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {In software engineering experiments, the description of bug reports is typically treated as natural language text, although it often contains stack traces, source code, and patches. Neglecting such structural elements is a loss of valuable information; structure usually leads to a better performance of machine learning approaches. In this paper, we present a tool called infoZilla that detects structural elements from bug reports with near perfect accuracy and allows us to extract them. We anticipate that infoZilla can be used to leverage data from bug reports at a different granularity level that can facilitate interesting research in the future.},
	keywords = {bug reports, eclipse, enumerations, infozilla, natural language, patches, source code, stack trace},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370757},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p27-bettenburg.pdf},
	author = {Premraj, Rahul and Zimmermann, Thomas and Kim, Sunghun and Bettenburg, Nicolas}
}
@article {flosswp355,
	title = {An Economic Model of Open Source Software Adoption},
	year = {2007},
	month = {May},
	abstract = {This paper examines the competitive strengths of open source versus commercial software from an economic perspective. It uses a simple model of rational software selection to derive the competitive strengths of open source and commercial software models, how they can balance each other, and what the threshold or tipping point for mass adoption of open source software would be. It shows that open source software has the advantage when their commercial competitors have excessively high profit margins or when the software product???s features are not scalable due to heterogeneous user requirements.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/economic_model_of_open_source_adoption.pdf},
	author = {Si Chen}
}
@booklet {492,
	title = {The Economic Motivation of Open Source: Stakeholder Perspectives},
	year = {2007},
	month = {April},
	abstract = {Open source software has changed the rules of the game, impacting significantly the economic behavior of stakeholders in the software ecosystem. In this new environment, developers strive to be committers, vendors feel pressure to produce open source products, and system integrators anticipate boosting profits.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/computer-2007.pdf},
	author = {Dirk Riehle}
}
@conference {633,
	title = {EDOS Distribution System: a P2P architecture for open-source content dissemination},
	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 = {209 - 215},
	publisher = {Springer},
	organization = {Springer},
	chapter = {17},
	abstract = {The open-source software communities currently face an increasing complexity of managing the software content among theirs developers and contributors. This is mainly due to the continuously growing size of the software, the high frequency of the updates, and the heterogeneity of the participants. We propose a distribution system that tackles two main issues in the software content management: efficient content dissemination through a P2P system architecture, and advanced information system capabilities, using a distributed index for resource location.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_17},
	attachments = {https://flosshub.org/sites/flosshub.org/files/EDOS\%20Distribution\%20System.pdf},
	author = {Abiteboul, Serge and Dar, Itay and Pop, Radu and Vasile, Gabriel and Vodislav, Dan}
}
@conference {661,
	title = {EDOS-Tools Tutorial: EDOS Tools for Linux Distributions Dependencies Management and Quality Assurance},
	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 = {363 - 364},
	publisher = {Springer},
	organization = {Springer},
	chapter = {45},
	abstract = {Free and Open Source Software (FOSS) distributions are the results of the effort of third party actors in collecting independently developed software products, in a consistent and usable form. The widespread adoption of these distributions as infrastructural components in many strategic contexts of the information technology society has drawn the attention on the issues regarding how to handle the complexity of assembling and managing a huge number of (packaged) components and how to guarantee their quality. This tutorial will describe how the EDOS project has tackled these issues. First it will describe the problems related to the quality assurance of Linux distributions and will present the tools that have been developed to manage testing process. It will then introduce the problems that occur when managing inter-package relations in large package repositories and will showcase tools that can be used to analyze and manage large package repositories.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_45},
	attachments = {https://flosshub.org/sites/flosshub.org/files/EDOIS-\%20Tools\%20Tutorials.pdf},
	author = {D{\'e}chelle, Fran{\c c}ois and Mancinelli, Fabio}
}
@conference {643,
	title = {Effect of Coupling on Defect Proneness in Evolutionary Open-Source Software Development},
	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 = {271 - 276},
	publisher = {Springer},
	organization = {Springer},
	chapter = {27},
	abstract = {Previous research on closed-source software found that highly coupled software modules were more defect prone, which makes it important to understand the effect of coupling on defect proneness in open-source software (OSS) projects. For this purpose, we used Cox proportional hazards modeling with recurrent events. We found that the effect of coupling was significant, and we quantified this effect on defect proneness.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Effect\%20of\%20Coupling\%20on\%20Defect.pdf},
	author = {G{\"u}nes Koru, A. and Zhang, Dongsong and Liu, Hongfang}
}
@conference {622,
	title = {Emergent Decision-Making Practices in Free/Libre Open Source Software (Floss) Development Teams},
	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 = {71 - 84},
	publisher = {Springer},
	organization = {Springer},
	chapter = {6},
	abstract = {We seek to identify work practices that make Free/Libre Open Source Software (FLOSS) development teams effective. Particularly important to team effectiveness is decision making. In this paper, we report on an inductive qualitative analysis of 360 decision episodes of six FLOSS development teams. Our analysis revealed diversity in decision-making practices that seem to be related to differences in overall team characteristics and effectiveness.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Emergent\%20Decision-Making.pdf},
	author = {Robert Heckman and Kevin Crowston and Eseryel, U. and Howison, James and Eileen Allen and Li, Qing}
}
@book {1803,
	title = {Emerging Free and Open Source Software PracticesVolunteers in Large Libre Software Projects},
	series = {Emerging Free and Open Source Software Practices},
	year = {2007},
	pages = {1 - 24},
	publisher = {IGI Global},
	organization = {IGI Global},
	abstract = {Most libre (free, open source) software projects rely on the work of volunteers. Therefore, attracting people who contribute their time and technical skills is of paramount importance, both in technical and economic terms. This reliance on volunteers leads to some fundamental management challenges: Volunteer contributions are inherently difficult to predict, plan, and manage, especially in the case of large projects. In this chapter we present an analysis of the evolution over time of the human resources in large libre software projects, using the Debian project, one of the largest and most complex libre software projects based mainly in voluntary work, as a case study. We have performed a quantitative investigation of data corresponding to roughly seven years, studying how volunteer involvement has affected the software released by the project, and the developer community itself.
},
	doi = {10.4018/978-1-59904-210-7.ch001},
	url = {http://www.igi-global.com/chapter/volunteers-large-libre-software-projects/10080},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Martin Michlmayr},
	editor = {Sowe, Sulayman K. and Stamelos, Ioannis G. and Samoladas, Ioannis}
}
@article {flosswp343,
	title = {EMOS/1: An Evolution Metrics Model for Open Source Software},
	year = {2007},
	month = {March},
	abstract = {Open Source Software (OSS) has become the subject of much commercial and academic interest of last. Providing quantitative metrics for OSS evolution has also become an urgent issue. However, most existing studies of software evolution have been performed on systems developed within a single company using traditional management techniques. These metrics models are not suitable for measuring OSS evolution. In this paper, we designed a preliminary evolution metrics model named EMOS/1 which contains a set of new metrics defined for evaluating OSS specially. The most significant novelty of this model is that it takes some properties of Open Source Community (OSC) into consideration. In another word, we measure the evolution of OSS and OSC together. We also provide a lightweight case study on Ubuntu project using EMOS/1. We find out the Open Source Community and its members also play essential role in OSS evolution. We expect our model can bring better understandings and explanations of phenomena in open source development and evolution.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/EMOS1.pdf},
	author = {Yi Wang and Defeng Guo}
}
@article {flosswp327,
	title = {An Empirical Investigation of Code Contribution, Communication Participation and Release Strategies in Open Source Software Development: A Conditional Hazard Model Approach},
	year = {2007},
	month = {January},
	abstract = {This study uses data from over 200 open source software (OSS) projects hosted at Sourceforge to empirically examine how OSS development characteristics affect project progress. Consistent with prior studies, we find that core developers (i.e., top 20 \% of the most contributing developers) develop about 80\% of the code. We also find that a group of developers that is about 50\% larger than the core group is responsible for 80\% of the communication. On average, the top 30\% developers contribute about 81\% of the messages. It is observed that projects with a clearly identified core group of developers conducting most of the coding are more efficient for project progress. We also find that highly participative peripheral group in communication positively affects project progress. In addition, high level of communication interactivity, measured by the number of email threads and average thread depth, enables a project to progress well. Our results also show that projects that draw upon the larger OSS community for beta testing progress faster. We find that the projects that do not progress well are associated with the following major factors: (i) lack of a core developer group, (ii) dormant peripheral group in communication, (iii) low communication interactivity exemplified by the lack of depth in threaded communications, and (iv) over-dependence on internal community for beta testing.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/singh_fan_tan.pdf},
	author = {Param Vir Singh and Ming Fan and Yong Tan}
}
@conference {1003,
	title = {Evaluating the Harmfulness of Cloning: A Change Based Experiment},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {18 - 18},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Cloning is considered a harmful practice for software maintenance because it requires consistent changes of the entities that share a cloned fragment. However this claim has not been refuted or confirmed empirically. Therefore, we have developed a prototype tool, CloneTracker, in order to study the rate of change of applications containing clones. This paper describes CloneTracker and illustrates its preliminary application on a case study.},
	keywords = {ccfinder, clone, clones, clonetracker, cloning, ctags, cvs, dnsjava, maintenance, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.8},
	author = {Lozano, Angela and Wermelinger, Michel and Nuseibeh, Bashar}
}
@conference {623,
	title = {Experiences on Product Development with 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 = {85 - 96},
	publisher = {Springer},
	organization = {Springer},
	chapter = {7},
	abstract = {This article discusses Nokia{\textquoteright}s experiences of using open source in commercial product development. It presents the development model used in the creation of mobile consumer devices and highlights the opportunities and challenges experienced. This article concludes that the main benefits come from the utilization of already available open source components, and from their quality and flexibility. It illustrates the challenges and solutions faced when mixing open and closed development models at Nokia.
},
	keywords = {gtk, linux, nokia, tablet},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Experiences\%20on\%20Product\%20Development.pdf},
	author = {Jaaksi, Ari}
}
@conference {624,
	title = {Exploring the Effects of Coordination and Communication Tools on the Efficiency of Open Source Projects using Data Envelopment Analysis},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	note = {"based on the date january 8, 2007, we selected the 30 most often downloaded projects from Sourceforge.net"},
	month = {2007///},
	pages = {97 - 108},
	publisher = {Springer},
	organization = {Springer},
	chapter = {8},
	abstract = {In this paper, we propose to explore possible benefits of communication and coordination tools in open source projects using data envelopment analysis (DEA), a general method for efficiency comparisons. DEA offers several advantages: It is a non-parametric optimization method without any need for the user to define any relations between different factors or a production function, can account for economies or diseconwhile omies of scale, and is able to deal with multi-input, multi-output systems in which the factors have different scales. Using a data set of 30 open source project retrieved from SourceForge.net, we demonstrate the application of DEA, showing that the efficiency of the projects is in general relatively high. Regarding the effects of tool employment on the efficiency of projects, the results were surprising: Most of the possible tools, and overall usage, showed a negative relationship to efficiency.
},
	keywords = {metadata, sourceforge},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_8},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Exploring\%20the\%20Effects\%20Coodination.pdf},
	author = {Koch, Stefan}
}
@mastersthesis {1487,
	title = {The Economical Aspects of Free Software and Open Source Software Solutions in Modern Business},
	year = {2006},
	type = {Master Thesis},
	abstract = {In the study economical aspects of Free / Open Source Software applications in commercial environment have been examined including main differences of commercial software development projects versus FOSS. Courtesy of Computer Science \& Engineering department of University of Notre Dame statistical data from sourceforge.net projects have been analysed to show advantages and features of FOSS development. Empirical study also supports possible business models and strategies based on FOSS usage. },
	attachments = {https://flosshub.org/sites/flosshub.org/files/theeconomical_v2.pdf},
	author = {Borucki, Blazej}
}
@conference {Amor:2006:EEC:1139113.1139116,
	title = {Effort Estimation by Characterizing Developer Activity},
	booktitle = {Proceedings of the 2006 International Workshop on Economics Driven Software Engineering Research},
	series = {EDSER {\textquoteright}06},
	year = {2006},
	pages = {3{\textendash}6},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {During the latest years libre (free, open source) software has gained a lot of attention from the industry. Following this interest, the research community is also studying it. For instance, many teams are performing quantitative analysis on the large quantity of data which is publicly available from the development repositories maintained by libre software projects. However, not much of this research is focused on cost or effort estimations, despite its importance (for instance, for companies developing libre software or collaborating with libre software projects), and the availability of some data which could be useful for this purpose. Our position is that classical effort estimation models can be improved from the study of these data, at least when applied to libre software. In this paper, we focus on the characterization of developer activity, which we argue can improve effort estimation. This activity can be traced with a lot of detail, and the resulting data can also be used for validation of any effort estimation model.
},
	keywords = {developer characterization, effort estimation, mining software repositories, open source software, software economics},
	isbn = {1-59593-396-4},
	doi = {10.1145/1139113.1139116},
	url = {http://doi.acm.org/10.1145/1139113.1139116},
	author = {Amor, Juan Jose and Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@proceedings {107,
	title = {Emergent decision-making practices in technology-supported self-organizing distributed teams},
	year = {2006},
	address = {Milwaukee, WI, 10{\textendash}13 Dec},
	author = {Robert Heckman and Kevin Crowston and Li, Qing and Eileen Allen and Eseryel, U. Yeliz and James Howison and Wei, Kangning}
}
@conference {flosswp406,
	title = {Emergent Decision-making Practices in Technology-Supported Self-Organizing Distributed Teams},
	booktitle = {Twenty Seventh International Conference on Information Systems},
	year = {2006},
	pages = {1{\textendash}12},
	abstract = {We seek to identify work practices that make technology-supported self-organizing distributed (or virtual) teams (TSSODT for short) effective in producing outputs satisfactory to their sponsors, meeting the needs of their members and continuing to function. A particularly important practice for team effectiveness is decision making: are the right decisions made at the right time to get the work done in a way that satisfies team sponsors, keeps contributors happy and engaged, and enables continued team success? In this research-in-progress paper, we report on an inductive qualitative analysis of 120 decision episodes taken by 2 Free/libre Open Source Software development teams (the completed paper will include 360 episodes from 6 teams). Our analysis revealed differences in the performance of the two teams that seems to be related to differences in overall project effectiveness.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/decision_making_practices.pdf},
	author = {Robert Heckman and Kevin Crowston and Li, Qing and Eileen Allen and Eseryel, U. Yeliz and James Howison}
}
@conference {Robles:2006:ESE:1172962.1173018,
	title = {Empirical Software Engineering Research on Free/Libre/Open Source Software},
	booktitle = {Proceedings of the 22nd IEEE International Conference on Software Maintenance},
	series = {ICSM {\textquoteright}06},
	year = {2006},
	pages = {347{\textendash}350},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {Public available data sources are an important knowledge generator from which researchers can obtain, mostly in a non-intrusive way, data and facts from software projects. We present a methodological approach to the data sources commonly found in libre (free, open source) software projects over the Internet, explain how to extract these data and enhance them and offer some ways of analyzing it from various perspectives. The whole process has been implemented with tools that automatize the process so that an ample amount of analysis from various angles (that range from software maintenance and software evolution to the social structure of the underlying organization in charge of the development) of a huge amount of software projects has been used as case studies. This work demonstrates that it is possible to build research methodologies that can be applied to a large quantity of software projects and that empirical software engineering studies have not to refer to a limited number of software projects. Although specifically targeted to libre software development, many of the techniques and lessons learned can be generally applied to other types of software environments.},
	isbn = {0-7695-2354-4},
	doi = {10.1109/ICSM.2006.25},
	url = {http://dx.doi.org/10.1109/ICSM.2006.25},
	author = {Gregorio Robles}
}
@article {flosswp298,
	title = {An Empirical Study on Implementing FLOSS in Schools},
	journal = {Social Informatics: An Information Society for All? In Remembrance of Rob Kling, the proceedings of the 7th {\textquoteright}Human Choice and Computers{\textquoteright} conference},
	year = {2006},
	publisher = {Springer Science and Business Media},
	abstract = {This empirical paper shows how free/libre open source software (FLOSS) contributes to mutual and collaborative learning in an educational environment. Unlike proprietary software, FLOSS allows extensive customisation of software and supports the needs of local users better. In this paper, we observes how implementing FLOSS in an Italian high school challenges the conventional relationship between end users themselves (e.g. teachers and students) and that between users and developers. The findings will shed some light on the social aspects of FLOSS-based computerization - including the role of FLOSS in social and organizational change in educational environments and the ways that the social organization of FLOSS are influenced by social forces and social practices.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LinZini_HCC7.pdf},
	author = {Yu-wei Lin and Enrico Zini}
}
@article {1233,
	title = {An Empirical Study on the Migration to OpenOffice.org in a Public Administration},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	year = {2006},
	month = {33/2006},
	pages = {64 - 80},
	abstract = {The aim of the article is to report the results of a migration to Open Source Software (OSS) in one public administration. The migration focuses on the office automation field and, in particular, on the OpenOffice.org suite. We have analysed the transition to OSS considering qualitative and quantitative data collected with the aid of different tools. All the data have been always considered from the point of view of the different stakeholders involved, IT managers, IT technicians, and users. The results of the project have been largely satisfactory. However the results cannot be generalised due to some constraints, like the environment considered and the parallel use of the old solution. Nevertheless, we think that the data collected can be of valuable aid to managers wishing to evaluate a possible transition to OSS.},
	issn = {1554-1053},
	doi = {10.4018/jitwe.2006070105},
	author = {Rossi, B. and Scotto, M. and Sillitti, A. and Succi, G.}
}
@article {flosswp358,
	title = {The evolution of free/libre open source software},
	year = {2006},
	month = {December},
	abstract = {The Free Libre Open Source Software represents an outstanding example of ???open development model of technological knowledge???. It has been studied in several researches that produced valuable illustrations of the way it works. Our understanding of its principal features is growing exponentially and an entire new literature on open source has been created. However there appears to be an important gap in the literature: the origin of the phenomenon. The following chapter attempts to tackle this issue by analyzing the long-term technological history of the Free Open Source Software; the main research questions at stake are: ???Is the phenomenon completely new? and if it is not totally new, where does it come from???? and, more generally, ???how did open source software developed over time????. As a consequence the present work focuses primarily on the analysis of the free/open source software history of technological change over a period of almost sixty years. I adopted a multidisciplinary approach to analyse the network of relations emerging between inventions and technological innovations, as well as economic determinants and intellectual property rights regimes throughout the period considered. Therefore, I attempted to investigate the origins of the phenomenon as a way of understanding its evolution.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Benussi\%282006\%29_The_evolution_of_FLOSS_1.pdf},
	author = {Lorenzo Benussi}
}
@conference {689,
	title = {Evolution of Open Source Communities},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	note = {"we took snapshots of its membership at regular intervals"
"we chose a one year period"
"we retrieve the list of core developers ordered by their number of inbound messages, as noted above."},
	pages = {21 - 32},
	publisher = {Springer},
	organization = {Springer},
	abstract = {The goal of this paper is to document the evolution of a portfolio of related open source communities over time. As a case study, we explore the subprojects of the Apache project, one of the largest and most visible open source projects. We extract the community structure from the mailing list data, and study how the subcommunities evolve, and are interrelated over time. Our analysis leads us to propose the following hypotheses about the growth of open source communities: (1) communities add new developers by a process of preferential attachment; (2) links between existing communities are also subject to preferential attachment; (3) developers will migrate between communities together with other collaborators; and (4) information flow follows project dependencies. In particular, we are concerned with the underlying factors that motivate the migration between communities, such as information flow, co-worker ties, and project dependencies.
},
	keywords = {apache, COMMUNITY, core, developers, email, email archives, mailing list, membership},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Evolution\%20of\%20Open\%20Source\%20Communities.pdf},
	author = {Weiss, Michael and Moroiu, Gabriella and Zhao, Ping}
}
@conference {D{\textquoteright}Ambros:2006:ERV:1137983.1137992,
	title = {The evolution radar: visualizing integrated logical coupling information},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {26{\textendash}32},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In software evolution research logical coupling has extensively been used to recover the hidden dependencies between source code artifacts. They would otherwise go lost because of the file-based nature of current versioning systems. Previous research has dealt with low-level couplings between files, leading to an explosion of data to be analyzed, or has abstracted the logical couplings to module level, leading to a loss of detailed information. In this paper we propose a visualization-based approach which integrates both file-level and module-level logical coupling information. This not only facilitates an in-depth analysis of the logical couplings at all granularity levels, it also leads to a precise characterization of the system modules in terms of their logical coupling dependencies.},
	keywords = {change management, cvs, evolution, logical coupling, mozilla, scm, source code, thunderbird, tinderbox, visualization},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137992},
	url = {http://doi.acm.org/10.1145/1137983.1137992},
	attachments = {https://flosshub.org/sites/flosshub.org/files/26TheEvolutionRadar.pdf},
	author = {D{\textquoteright}Ambros, Marco and Lanza, Michele and Lungu, Mircea}
}
@conference {Jiang:2006:EEC:1137983.1138030,
	title = {Examining the evolution of code comments in PostgreSQL},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {179{\textendash}180},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {It is common, especially in large software systems, for developers to change code without updating its associated comments due to their unfamiliarity with the code or due to time constraints. This is a potential problem since outdated comments may confuse or mislead developers who perform future development. Using data recovered from CVS, we study the evolution of code comments in the PostgreSQL project. Our study reveals that over time the percentage of commented functions remains constant except for early fluctuation due to the commenting style of a particular active developer.},
	keywords = {code comments, comments, cvs, evolution, functions, maintenance, mining challenge, msr challenge, postgresql, software evolution, software maintenance, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138030},
	url = {http://doi.acm.org/10.1145/1137983.1138030},
	attachments = {https://flosshub.org/sites/flosshub.org/files/179ExaminingTheEvolution.pdf},
	author = {Zhen Ming Jiang and Hassan, Ahmed E.}
}
@booklet {515,
	title = {Exit \& Voice in Free \& Open Source Software Licensing:  Moderating the Rein over Software Users},
	year = {2006},
	month = {Jan},
	abstract = {This article analyzes the interplay between exit and voice for user adoption of Free and Open Source Software (FOSS), as these two are conceptualized in Albert O. Hirschman{\textquoteright}s book Exit, Voice, and Loyalty:  Responses to Decline in Firms, Organizations and States.  Exit and voice cooperatively sustain FOSS through the institutional mechanism of the FOSS license.  Four situations demonstrate this.  First, even with attendant uncertainties in its novel legal landscape, users adopt FOSS to escape proprietary licensed software.  This exit is tinged with indirect voice.  Second, this indirect voice arises from collaborative projects to develop FOSS.  The very same code and license that provides the exit carries the voice.  Third, complementing exit by users are technologists who contribute, extracurricularly, to open source projects, signaling their affiliation with FOSS.  Fourth, from its beginning, the FOSS movement has expressed its voice.  Its norm entrepreneurs use rhetoric and persuasion to reinforce FOSS{\textquoteright}s disciplining effect on an entire industry.  These four situations highlight exit and voice combinations for copyright based open source licensing and patent law.  The FOSS copyright based licensing scheme helps channel FOSS into uses where exit and voice are concentrated and synergistically reinforce.  The interplay with patent law generates voice because patent law, at least theoretically, inhibits exit to FOSS and thus pressurizes the voice mechanism in Hirschman{\textquoteright}s framework.  Understanding FOSS based combinations of exit and voice in light of this framework helps participants and policy makers formulate legal, licensing and policy strategies to guide the movement and respond to its evolution.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Vetter.Exit_.and_.Voice_.in_.FOSS_.Licensing85.Oregon.L.Rev_.183.\%282006\%29.pdf},
	author = {Greg R Vetter}
}
@article {Ripoche2006,
	title = {Experiences in Automating the Analysis of Linguistic Interactions for the Study of Distributed Collectives},
	journal = {Computer Supported Cooperative Work (CSCW)},
	volume = {15},
	number = {2},
	year = {2006},
	note = {flossmole is mentioned in passing},
	pages = {149{\textendash}183},
	abstract = {An important issue faced by research on distributed collective practices is the amount and nature of the data available for study. While persistent mediated interaction offers unprecedented opportunities for research, the wealth and richness of available data pose issues on their own, calling for new methods of investigation. In such a context, automated tools can offer coverage, both within and across collectives. In this paper, we investigate the potential contributions of semantic analyses of linguistic interactions for the study of collective processes and practices. In other words, we are interested in discovering how linguistic interaction is related to collective action, as well as in exploring how computational tools can make use of these relationships for the study of distributed collectives.},
	keywords = {flossmole cited},
	issn = {1573-7551},
	doi = {10.1007/s10606-006-9017-0},
	url = {http://dx.doi.org/10.1007/s10606-006-9017-0},
	author = {Gabriel Ripoche and Sansonnet, Jean-Paul}
}
@conference {690,
	title = {Exploring the potential of OSS in Air Traffic Management},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {173 - 179},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper introduces a project that aims at defining an Open Source Software (OSS) policy in the field of Air Traffic Management (ATM). In order to develop such a policy, we chose to investigate first a set of predictive hypotheses. Our four initial hypotheses were presented, refined and discussed in bi-lateral meetings with experts in the ATM field and in several conferences and workshops with OSS experts. At a roundtable, jointly organized by CALIBRE and EUROCONTROL, we confronted early open source experiences and insights in the ATM domain with experiences and knowledge from a panel of OSS experts and practitioners from academia and industry. The revised initial hypotheses are presented using a fixed format that should facilitate further evolution of these hypotheses.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_17},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Exploring\%20the\%20potential\%20of\%20OSS.pdf},
	author = {Hardy, Jean-Luc and Bourgois, Marc}
}
@conference {902,
	title = {An Economic Model of User Rating in an Online Recommender System},
	booktitle = {10th International Conference on User Modeling},
	year = {2005},
	address = {Edinburgh, UK},
	author = {F.M. Harper and X. Li and Y. Chen and Konstan, J.A.}
}
@conference {766,
	title = {Economics approaching OSS: reviewing 15 years of debate},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {268},
	abstract = {The work aims at reviewing the theoretical literature on the development and diffusion of Open Source Software (OSS) relevant to an economic approach. It provides a synthetic picture of the areas of economic analysis for OSS, by attempting to frame relevant research efforts into a taxonomy based on attributes of innovation and process of diffusion. The main contributions investigating in the past decade the economic theoretical models beyond the {\textquotedblleft}open{\textquotedblright} way of producing and distributing software goods analyse: i) its supposed nature of complex public good, ii) the production process and distributed work organisation, iii) the evaluation of its impact on the software market, both at market level and at firm level. The relationship of the open source model with knowledge appropriation and reuse, and with innovation diffusion to support economic growth and social wealth would help drawing related economics and policy issues.},
	url = {http://pascal.case.unibz.it/handle/2038/765},
	author = {De Prato, Giuditta}
}
@conference {725,
	title = {EDOS: Environment for the Development and Distribution of Open Source Software},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {66-70},
	abstract = {The open-source software community is now comprised of a very large and growing number of contributors and users. The GNU/Linux operating system for instance has an estimated 18 million users worldwide and its contributing developers can be counted by thousands. The critical mass of contributors taking part in various opensource projects has helped to ensure high quality for open source software. However, despite the achievements of the open-source software industry, there are issues in the production of large scale open-source software (OSS) such as the GNU/Linux operating system that have to be addressed as the numbers of users, of contributors, and of available applications grow. EDOS is a European project supported by IST started October 2004 and ending in 2007, whose objective is to provide a new generation of methodologies, theoretical models, technical tools and quality models specifically tailored to OSS engineering and to software distribution over the Interne...},
	url = {http://pascal.case.unibz.it/handle/2038/737},
	author = {Abiteboul, Serge and Leroy, Xavier and Vrdoljak, Boris and Di Cosmo, Roberto and Fermigier, St{\'e}fane and Lauri{\`e}re, St{\'e}phane and Lepied, Fr{\'e}d{\'e}ric and Pop, Radu and Villard, Florent and Smets, Jean-Paul and Bryce, Ciar{\'a}n and Dittrich, Klaus R. and Milo, Tova and Sagi, Assaf and Shtossel, Yotam and Panto, Eleonora}
}
@unpublished {flosswp235,
	title = {Effects of Open Source Software on the Business Patterns of Software Industry},
	year = {2005},
	month = {September},
	abstract = {Open source software is a phenomenon that has potential to change the traditional patterns of business behavior. Research committed so far has not evaluated the entire scale of potential changes, which is the purpose of this explorative thesis. Previous literature on the subject can be divided into history of the phenomenon, explaining the nature of the phenomenon, and a more general discussion about strategies and business models in the software business. By using these theories this thesis provides a framework for analysing the entire phenomenon. The framework is put to use in the empirical part. Data consist of interviews of experts in the field. An analysis of the data is done using narrative methods. The analysis yield eleven narratives that describe the phenomenon. Four of the narratives reveal effects. On the basis of the responses gathered, open source software can change competition environment, customer expectations, the importance of competence, and platform thinking.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lindman.pdf},
	author = {Juho Lindman}
}
@conference {Robles05anempirical,
	title = {An empirical approach to Software Archaeology},
	booktitle = {In: Poster Proceedings of the International Conference on Software Maintenance},
	year = {2005},
	pages = {47{\textendash}50},
	abstract = {The term {\textquotedblleft}software archaeology {\textquotedblright} provides a useful metaphor of the tasks that a software developer has to face when performing maintenance on large software projects. The source code of a program at any point in time is the result of many different changes performed in the past, usually by several people, which can be tracked when a version control system is used. We have designed a methodology for analyzing with detail the age of the source code in such cases, and have applied it to several large software projects. As a part of the methodology, we define a set of indexes which can help to characterize the history of a software system, and discuss how those could be used to estimate its past and future maintenance. We also show how our approach to software archaeology is simple both conceptually and computationally, but still very powerful at uncovering useful information.},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Herraiz, Israel}
}
@article {102,
	title = {Empirical validation of object-oriented metrics on open source software for fault prediction},
	journal = {IEEE Transactions on Software Engineering},
	volume = {31},
	number = {10},
	year = {2005},
	note = {"This paper describes how we calculated the object-oriented metrics given by Chidamber and Kemerer to illustrate how fault-proneness detection of the source code of the open source Web and e-mail suite called Mozilla can be carried out. We checked the values obtained against the number of bugs found in its bug database - called Bugzilla - using regression and machine learning methods to validate the usefulness of these metrics for fault-proneness prediction. We also compared the metrics of several versions of Mozilla to see how the predicted fault-proneness of the software system changed during its development cycle."
metrics, 
wmc weighted methods per class, 
dit depth of inheritance, 
rfc response for a class,
noc number of children,
cbo coupling between object classes,
cohesion,
lines of code, loc, sloc
chidamber and kemerer metrics},
	pages = {897-910},
	abstract = {Open source software systems are becoming increasingly important these days. Many companies are investing in open source projects and lots of them are also using such software in their own work. But, because open source software is often developed with a different management style than the industrial ones, the quality and reliability of the code needs to be studied. Hence, the characteristics of the source code of these projects need to be measured to obtain more information about it. This paper describes how we calculated the object-oriented metrics given by Chidamber and Kemerer to illustrate how fault-proneness detection of the source code of the open source Web and e-mail suite called Mozilla can be carried out. We checked the values obtained against the number of bugs found in its bug database - called Bugzilla - using regression and machine learning methods to validate the usefulness of these metrics for fault-proneness prediction. We also compared the metrics of several versions of Mozilla to see how the predicted fault-proneness of the software system changed during its development cycle.},
	keywords = {bugs, bugzilla, cbo, defects, dit, fault-prone modules, faults, lcom, lcomn, loc, metrics, mozilla, noc, object-oriented, rfc, source code, wmc},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.115.8372\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Gyimothy.pdf},
	author = {Gyimothy, T. and Ferenc, R. and Siket, I.}
}
@conference {Liu:2005:ESE:1062455.1062566,
	title = {Enriching software engineering courses with service-learning projects and the open-source approach},
	booktitle = {Proceedings of the 27th international conference on Software engineering},
	series = {ICSE {\textquoteright}05},
	year = {2005},
	pages = {613{\textendash}614},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Real-world software engineers deal with complex problem. Yet many software engineering courses do not involve projects of enough complexity to give students such experience. We sense that service-learning projects, while difficult to manage and sustain, can serve a crucial role in this regard. Through trials in a senior-level software engineering course, we discovered that the open-source approach works well to enable students to work on large, multiple-term service-learning projects. We developed GROw, a cross-term, cross-team educational software process to meet the challenges of adopting complex, real-world projects in one-term courses, and to sustain service learning.},
	keywords = {education, pedagogical, service learning, software engineering education},
	isbn = {1-58113-963-2},
	doi = {10.1145/1062455.1062566},
	url = {http://doi.acm.org/10.1145/1062455.1062566},
	author = {Liu, Chang}
}
@conference {Gorg:2005:EDR:1083142.1083148,
	title = {Error detection by refactoring reconstruction},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {29-33},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In many cases it is not sufficient to perform a refactoring only at one location of a software project. For example, refactorings may have to be performed consistently to several classes in the inheritance hierarchy, e.g. subclasses or implementing classes, to preserve equal behavior.In this paper we show how to detect incomplete refactorings - which can cause long standing bugs because some of them do not cause compiler errors - by analyzing software archives. To this end we reconstruct the class inheritance hierarchies, as well as refactorings on the level of methods. Then, we relate these refactorings to the corresponding hierarchy in order to find missing refactorings and thus, errors and inconsistencies that have been introduced in a software project at some point of the history.Finally. we demonstrate our approach by case studies on two open source projects.},
	keywords = {bugs, class, inheritance, jedit, refactoring, tomcat},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083148},
	url = {http://doi.acm.org/10.1145/1082983.1083148},
	attachments = {https://flosshub.org/sites/flosshub.org/files/29ErrorDetection.pdf},
	author = {G{\"o}rg, Carsten and Wei{\ss}gerber, Peter}
}
@conference {719,
	title = {Evaluating the Quality and Quantity of Data on Open Source Software Projects},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {29-36},
	abstract = {In this paper, we provide a preliminary evaluation of the quality and quantity of data on open source (OS) projects, provided at the SourceForge.net portal. We have derived a dataset of approximately 50000 projects from SourceForge. Using several indicators of project activity, we identify two samples from the entire dataset: the {\textquoteleft}most active{\textquoteright} OS projects (a total of 456 projects, ~0.9\% of the entire dataset), and those projects with active code development (5826 projects, ~11.6\%). The number of projects that are active across all of our main indicators of activity account for less than 1\% of the projects on the portal. This suggests that many OS projects being registered on SourceForge are {\textquoteleft}impulse{\textquoteright} projects, which do not gather sufficient interest from developers or users to {\textquoteleft}activate{\textquoteright} those projects and make them {\textquoteleft}successful{\textquoteright}. It also suggests that researchers, developers and users should be careful about how they use OS portals.},
	url = {http://pascal.case.unibz.it/handle/2038/733},
	author = {Rainer, Austen and Gale, Stephen}
}
@article {130,
	title = {Evolution and growth in large libre software projects},
	journal = {Principles of Software Evolution, Eighth International Workshop on},
	year = {2005},
	pages = {165-174},
	author = {Gregorio Robles and Amor, J. J. and Jesus M. Gonzalez-Barahona and Herraiz, I.}
}
@conference {740,
	title = {Evolution of Open Source Software Systems {\textendash} A Large-Scale Investigation},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {148-153},
	abstract = {In this paper, the evolution of a large sample of open source software projects will be analysed. The evolution of commercial systems has been an issue that has long been a center of research, thus a coherent theoretical framework of software evolution has been developed and empirically tested. Therefore these results can be used to compare the situation in open source projects to the evolution of commercial projects. This allows to assess whether the underlying software process indeed significantly differs. The data collection methodology relying on a large software repository and the respective source code control systems is described, and an overview on the collected data on several thousand projects is given. The evolutionary behaviour is explored using both a linear and a quadratic model, with the quadratic model significantly outperforming the linear one. The most interesting fact is that while in the mean the growth rate is decreasing over time according to the l...},
	url = {http://pascal.case.unibz.it/handle/2038/863},
	author = {Koch, Stefan}
}
@conference {800,
	title = {Evolution of Open-Source Code Bases EVOSC 2005},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {359},
	abstract = {The very essence of open- source software is that
it enables custom evolutions. These evolutions should be
designed and managed carefully, since merging the main
trunk with custom branches is often critical for inheriting
evolutions that are not at the core interest of the independent
developer.},
	author = {Mattia Monga and Andrea Trentini}
}
@conference {731,
	title = {Evolution of Volunteer Participation in Libre Software Projects: Evidence from Debian},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	note = {"For each release we have retrieved the corresponding sources.gz file (see below) from the Debian archive. From it we have extracted information about the packages and their maintainers...."
},
	pages = {100-107},
	abstract = {Most libre software projects rely on the work of volunteers. Therefore, attracting people who contribute their time and technical skills is of paramount importance, both in technical and economic terms. This reliance on volunteers leads to some fundamental management challenges: volunteer contributions are inherently difficult to predict, plan and manage, especially in the case of large projects. In this paper we analyze the evolution in time of the human resources of one of the largest and most complex libre software projects composed primarily of volunteers, the Debian project. Debian currently has around 1300 volunteers working on several tasks: much activity is focused on packaging software applications and libraries, but there is also major work related to the maintenance of the infrastructure needed to sustain the development. We have performed a quantitative investigation of data from almost seven years, studying how volunteer involvement has affected the software...},
	keywords = {contributors, debian, maintainers, PopCon, popularity, Volunteers},
	url = {http://pascal.case.unibz.it/handle/2038/857},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles_barahona_michlmayr-evolution_participation.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Martin Michlmayr}
}
@proceedings {897,
	title = {Experiences in Discovering, Modeling, and Reenacting Open Source Software Development Processes},
	year = {2005},
	month = {May},
	publisher = {Springer-Verlag},
	address = {Beijing, China},
	author = {Chris Jensen and Walt Scacchi},
	editor = {Li, Mingshu and Boehm, Barry and Osterweil, Leon J.}
}
@conference {792,
	title = {Experiences teaching a graduate course in Open Source Software Engineering},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {326-328},
	abstract = {This paper describes the early experiences of a graduate course in open source software engineering at the Department of Computer Science at the University Victoria. It includes a description of the motivation for the course, its structure and evaluation methods. It concludes with a discussion of the lessons learned and its future.},
	keywords = {course, FOSS, MOTIVATION, open source, open source software engineering},
	url = {http://pascal.case.unibz.it/handle/2038/971},
	author = {Daniel M. German}
}
@article {flosswp184,
	title = {Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary Code (updated)},
	year = {2005},
	note = {"For each design, we report data on the number of source files, the number of dependencies, the density of the DSM (i.e., the number of dependencies per source file pair) the propagation cost and the clustered cost. We also provide data on the average complexity of source files, in terms of the number of functions and lines of code."},
	month = {June},
	abstract = {This paper reports data from a study that seeks to characterize the differences in design structure between complex software products. In particular, we use Design Structure Matrices (DSMs) to map the dependencies between the elements of a design and define metrics that allow us to compare the structures of different designs. We first use these metrics to compare the architectures of two software products - the Linux operating system and the Mozilla web browser - that were developed via contrasting modes of organization: specifically, open source versus proprietary development. We then track the evolution of Mozilla, paying particular attention to a purposeful "re-design" effort that was undertaken with the intention of making the product more "modular." We find significant differences in structure between Linux and the first version of Mozilla, suggesting that Linux had a more modular architecture. We also find that the redesign of Mozilla resulted in an architecture that was significantly more modular than that of its predecessor, and indeed, than that of Linux. Our results, while exploratory, are consistent with a view that different modes of organization are associated with designs that possess different structures. However, we also illustrate that purposeful managerial actions can have a large impact on structure. This latter result is important given recent moves to release proprietary software into the public domain. These moves are likely to fail unless the product possesses an architecture that facilitates participation. Our paper provides evidence that a tightly-coupled design can be adapted to meet this objective.},
	keywords = {complexity, cost, dependencies, functions, lines of code, linux, loc, mozilla, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/maccormackrusnakbaldwin2.pdf},
	author = {Alan MacCormack and John Rusnak and Carliss Baldwin}
}
@conference {775,
	title = {eZPA portale e-government per enti locali},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {289-290},
	abstract = {Tra i numerosi settori in cui Internet sta intervenendo con una forte carica di {\textquotedblleft}modernizzazione{\textquotedblright}, quello dell{\textquoteright}e- Government, inteso come possibilit{\`a} per tutti gli utenti, per tutti i cittadini, di gestire il rapporto con la Pubblica Amministrazione, anche on line, sta producendo gli effetti maggiormente innovativi. L{\textquoteright}occasione fornitaci dall{\textquoteright}amministrazione del Comune di Ozzano dell{\textquoteright}Emilia ha permesso di sviluppare l{\textquoteright}applicazione eZPA, scritta con software a codice sorgente aperto e rilasciata con licenza GNU-GPL (General Publish Licence), liberamente utilizzabile e modificabile. Il portale consente la fruibilit{\`a} telematica dei servizi comunali sia ai clienti esterni (cittadini e imprese), sia agli utenti interni (dipendenti e collaboratori comunali), attraverso una struttura di sportelli fisici/virtuali. In particolare, l{\textquoteright}utilizzo della metafora di comunicazione {\textquotedblleft}Evento della vita{\textquotedblright},[1] raccomandata dalle linee guida del Ministro per l{\textquoteright}Innovazione e le Tecnologie, ha ...},
	keywords = {e-government, enti locali, INTERNET, open source, pubblica amministrazione},
	url = {http://pascal.case.unibz.it/handle/2038/874},
	author = {Colognesi, Cristina and Guandalini, Stefano}
}
@article {flosswp157,
	title = {The Economics of Open Source Hijacking and Declining Quality of Digital Information Resources: A Case for Copyleft},
	year = {2004},
	month = {April},
	abstract = {The economics of information goods suggest the need of institutional intervention to address the problem of revenue extraction from investments in resources characterized by high fixed costs of production and low marginal costs of reproduction and distribution. Solutions to the appropriation issue, such as copyright, are supposed to guarantee an incentive for innovative activities at the price of few vices marring their rationale. In the case of digital information resources, apart from conventional inefficiencies, copyright shows an extra vice since it might be used perversely as a tool to hijack and privatise collectively provided open source and open content knowledge assemblages. Whilst the impact of hijacking on open source software development may be uncertain or uneven, some risks are clear in the case of open content works. The paper presents some evidence of malicious effects of hijacking in the Internet search market by discussing the case of The Open Directory Project. Furthermore, it calls for a wider use of novel institutional remedies such as copyleft and Creative Commons licensing, built upon the paradigm of copyright customisation.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ciffolili.pdf},
	author = {Andrea Ciffolilli}
}
@article {flosswp199,
	title = {The Economics of Technology Sharing: Open Source and Beyond},
	year = {2004},
	month = {December},
	abstract = {This paper reviews our understanding of the growing open source movement. We highlight how many aspects of open source software appear initially puzzling to an economist. As we have acknowledge, our ability to answer confidently many of the issues raised here questions is likely to increase as the open source movement itself grows and evolves. At the same time, it is heartening to us how much of open source activities can be understood within existing economic frameworks, despite the presence of claims to the contrary. The labor and industrial organization literatures provide lenses through which the structure of open source projects, the role of contributors, and the movement{\textquoteright}s ongoing evolution can be viewed.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lernertirole3.pdf},
	author = {Josh Lerner}
}
@article {127,
	title = {An empirical study of open-source and closed-source software products},
	journal = {Ieee Transactions on Software Engineering},
	volume = {30},
	number = {4},
	year = {2004},
	note = {Times Cited: 8},
	pages = {246-256},
	abstract = {This paper describes an empirical study of open-source and closed-source software projects. The motivation for this research is to quantitatively investigate common perceptions about open-source projects, and to validate these perceptions through an empirical study. This paper investigates the hypothesis that open-source software grows more quickly, but does not find evidence to support this. The project growth is similar for all the projects in the analysis, indicating that other factors may limit growth. The hypothesis that creativity is more prevalent in open-source software is also examined, and evidence to support this hypothesis is found using the metric of functions added over time. The concept of open-source projects succeeding because of their simplicity is not supported by the analysis, nor is the hypothesis of open-source projects being more modular. However, the belief that defects are found and fixed more rapidly in open-source projects is supported by an analysis of the functions modified. The paper finds support for two of the five common beliefs and concludes that, when implementing or switching to the open-source development model, practitioners should ensure that an appropriate metrics Collection strategy is in place to verify the perceived benefits.},
	author = {Paulson, J. W. and Succi, G. and Eberlein, A.}
}
@article {flosswp163,
	title = {Epistemologically Multiple Actor-Centred System: or EMACS at Work!},
	year = {2004},
	month = {May},
	abstract = {This paper analyses the innovation process of EMACS (short for Editing MACroS) from a socio-technical perspective. I investigates how actors from different backgrounds contribute multiple ways of knowing, understanding and resolving problems that arise in the innovation process. The analysis of EMACS is especially useful since it spans the period that saw the origins of the free software movement and the subsequent development of a broader free/libre open source software (FLOSS) social world.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin.pdf},
	author = {Yu-wei Lin}
}
@article {flosswp176,
	title = {Executable source code and non-executable source code},
	year = {2004},
	month = {June},
	abstract = {The concept of source code, understood as the source components used to obtain a binary, ready to execute version of a program, comprises currently more than source code written in a programming language. Specially when we move apart from systems-programming and enter the realm of end-user applications, we find source files with documentation, interface specifications, internationalization and localization modules, multimedia files, etc. All of them are source code in the sense that the developer works directly with them, and the application is built automatically using them as input. This paper discusses the relationship between {\textquoteright}classical{\textquoteright} source code (usually written in a programming language) and these other files by analyzing a publicly-available software versioning repository. Aspects that have been studied include the nature of the software repository, the different mixtures of source code found in several software projects stored in it, the specialization of developers to the different tasks, etc.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles-barahona_source_code.pdf},
	author = {Gregorio Robles}
}
@article {flosswp170,
	title = {An Experimental Study of Open Innovation using MASTERMIND},
	year = {2004},
	month = {August},
	abstract = {This paper presents the first experimental results on open innovation, which is defined to be a method to solve problems with other people by revealing some or the complete history of algorithm already used. An important example is open source. Our data from human subjects show that non-modular payoff structure drives the convergence to a Nash equilibrium, in which commission price to helpers converge to zero but helpers will not stop solving problems for others. By non-modularity, we mean that the total production (or payoff) of a team is zero if either one of its members fails to produce at least at a certain level. In the experiment, subjects produce by solving a variant of a popular board game called MASTERMIND. Theoretically, free-riding leads to zero commission price. This removes a signaling function of price for the difficulty levels of work remaining. Empirically, however, it is not sufficient to cause the catastrophic outcome of zero payoff. This provides a basis for us to hypothesize that open innovation is a key explanation because it allows subjects to directly observe the history of work already done and potentially direct more resources to the more difficult tasks.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/chiao2.pdf},
	author = {Benjamin Hak-Fung Chiao}
}
@proceedings {1201,
	title = {Exploiting the Collaboration between Open Source Developers and Research},
	year = {2004},
	pages = {97-99},
	abstract = {In this paper it is argued that open source developers and research projects carrying out user requirement analysis should collaborate at a closer level. In particular, we discuss how developers could take advantage of the knowledge generated by COSPA, a research project aimed at studying and supporting the introduction of open source software in the Public Administration. COSPA focuses on office automation and desktop system software and it could thus provide developers with user requirements from one of the main "corporate" users of software. To this aim, the project has established an "observer" status, by means of which interested parties may access COSPA{\textquoteright}s results, thereby fostering collaboration and increasing dissemination of knowledge.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/succi98-100.pdf},
	author = {Succi, G. and Zuliani, P.}
}
@article {flosswp73,
	title = {The Ecology of Open Source Software Development},
	year = {2003},
	month = {January},
	abstract = {A number of theories have emerged to explain the success of open source software, mainly from economics and law. We analyze a very large sample of OSS projects and find striking patterns in the overall structure of the development community. The distribution of projects on a range of activity measures is spectacularly skewed, with only a relatively tiny number of projects showing evidence of the strong collaborative activity which is supposed to characterize OSS. Our findings are consistent with prior, smaller-scale empirical research. We argue that these findings pose problems for the dominant accounts of OSS. We suggest that the gulf between active and inactive projects may be explained by social-structural features of the community which have received little attention in the existing literature. We suggest some hypotheses that might better predict the observed ecology of projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/healyschussman.pdf},
	author = {Kieran Healy}
}
@article {flosswp66,
	title = {An Economic Theory of Free and Open Source Software: A Tour from Lighthouse to Chinese-Style Socialism (revised version)},
	year = {2003},
	month = {December},
	abstract = {The theory is that free and open source software is private property under the guise of common property. Such software is distributed mostly under the GNU General Public License. The intents in The GNU Manifesto suggest striking similarities between this license and communism. The resulting economic properties, however, are similar to those of Chinese-style socialism: both resulted from an increased separation of legal and economic ownership. The phenomenal growth of China in the last twenty five years and of such software in the past few years could be attributed to such separation.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/chiao.pdf},
	author = {Benjamin Hak-Fung Chiao}
}
@article {flosswp55,
	title = {The Economics of Free Software for a Competitive Firm},
	year = {2003},
	month = {February},
	abstract = {This paper builds a simple economic model of the profit seeking firm with a choice between producing an open source and proprietary solutions. Differences between public and viral licenses are discussed from the firm{\textquoteright}s perpective. Advocacy issues are omitted entirely, and the model requires no math beyond subtraction. The decision of a firm to adopt an open source product rather than purchase is also discussed, but is seen as a trivial and uninteresting problem.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hawkins.pdf},
	author = {Richard Hawkins}
}
@article {flosswp111,
	title = {Episodes of Collective Invention},
	year = {2003},
	month = {August},
	abstract = {The process of developing technology through open discussion has been called collective invention. Open source software projects have this form. This paper documents two earlier episodes of collective invention and proposes a general model based on search theory. One episode was the development of mass production steel in the U.S. (1866-1885), and the second with early personal computers (1975-1985). Technical people openly discussed and shared these developing technologies between firms. Collective invention episodes begin with an invention or a change in legal restrictions. Hobbyists and startup firms experiment with practical methods of production and share their results through a social network whose members gradually form a new industry.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/meyer.pdf},
	author = {Peter Meyer}
}
@article {1099,
	title = {Evidences in the evolution of OS projects through Changelog Analyses},
	journal = {Proceedings of the 3rd ICSE Workshop on Open Source},
	year = {2003},
	note = {"In this study we concentrate on a very large sample (406 projects) selected randomly from an OS portal[20]" (freshmeat)

"We define three clusters of projects: {\textquoteright}large{\textquoteright} projects as long as they are based on more than 1000KB(40KLOC)..."},
	pages = {19-24},
	abstract = {Most empirical studies about Open Source (OS) projects or products are vertical and usually deal with the flagship, successful projects. There is a substantial lack of horizontal studies to shed light on the whole population of projects, including failures. This paper presents a horizontal study aimed at characterizing OS projects. We analyze a sample of around 400 projects from a popular OS project repository. Each project is characterized by a number of attributes. We analyze these attributes statically and over time. The main results show that few projects are capable of attracting a meaningful community of developers. The majority of projects is made by few (in many cases one) person with a very slow pace of evolution. We then try to observe how many projects count on a substantial number of developers, and analyze those projects more deeply. The goal is to achieve a better insight in the dynamics of open source development. The initial results of this analysis, especially growth in code size and tendency to stability in modularity, seem to be in line with traditional close source development.},
	keywords = {classification, freshmeat, loc, modularity, repository, size, sloc, source code},
	url = {http://hdl.handle.net/10552/1037},
	attachments = {https://flosshub.org/sites/flosshub.org/files/capiluppi2003.pdf},
	author = {Capiluppi, Andrea}
}
@proceedings {104,
	title = {Economic incentives for participating in open source software projects},
	year = {2002},
	note = {"The data for this research come from two primary sources: Apache project archives and a targeted survey of Apache participants. Archival data are open source project artifacts such as e-mail and source code archives, source code version control meta-data, and developer Web sites"
independent variables: patch, committer, work experience, programming experience, education, job switch, firm size, firm public, industry},
	pages = {365{\textendash}372},
	abstract = {Using the Internet as a basis for communication, collaboration, and storage of artifacts, the open source community is producing software of a quality that was previously thought to be achievable only by professional engineers following strict software development paradigms. This accomplishment is even more astounding as developers contribute to the source code without any remuneration. Open source leaders as well as academics have proposed theories about the motivation of open source developers that are rooted in diverse fields such as social psychology and anthropology. However, Lerner and Tirole (2000) argue that developer participation in open source projects may, in part, be explained by existing economic theory regarding career concerns. This research seeks to confirm or disconfirm the existence of economic returns to participation in open source development. Our findings suggest that greater open source participation per se, as measured in contributions made, is not associated with wage increases. However, a higher status in a merit-based ranking within the Apache Project is associated with significantly higher wages. This suggests that employers do not reward the gain in experience through open source participation as an increase in human capital. The results are also consistent with the notion that a high rank within the Apache Software Foundation is a credible signal of the productive capacity of a programmer.},
	keywords = {apache, contributions, email, email archives, mailing list, organizational sponsorship, participation, patch, scm, source code, Survey, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/42.pdf},
	author = {Il-Horn Hann and Jeff Roberts and Sandra Slaughter and Roy Fielding}
}
@article {flosswp60,
	title = {The Economics of Open Source Networks},
	year = {2002},
	month = {October},
	abstract = {The open-source movement is becoming an overarching feature of knowledgecreating environments and this research investigates the mechanisms whereby such a model comes into existence. Far from being the result of gifts of anonymous benefactors, the open-source model is the outcome of a conveyance of informative, valuative and incitive signals that larger sets of potential contributors construe in a subjective fashion. This study challenges the gift-economy metaphor and cautions the argument that open-source software is a reliable and generally applicable model for the forthcoming digital age.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/iannacci.pdf},
	author = {Federico Iannaci}
}
@article {1251,
	title = {The Economics of Open Source Software: A Survey of the Early Literature},
	journal = {Review of Network Economics},
	volume = {1},
	number = {1},
	year = {2002},
	month = {03/2002},
	abstract = {This paper reviews the recent literature on the economics of open source software. Two different sets of issues are addressed. The first looks at the incentives of programmers to participate in open source projects. The second considers the business models used by profit-making firms in the open source industry, and the effects on existing closed source firms. Some possible future research directions are also given.},
	keywords = {business, commercial software, incentives, MOTIVATION},
	attachments = {https://flosshub.org/sites/flosshub.org/files/schiff.pdf},
	author = {Schiff, A.}
}
@article {1862,
	title = {Editorial: Open source software engineering},
	journal = {IEE Proceedings - Software},
	volume = {149},
	year = {2002},
	month = {2002},
	pages = {1},
	issn = {14625970},
	doi = {10.1049/ip-sen:20020363},
	attachments = {https://flosshub.org/sites/flosshub.org/files/20020363.pdf},
	author = {Feller, J. and Fitzgerald, B. and van der Hoek, A.}
}
@article {1117,
	title = {Effort, co-operation and co-ordination in an open source software project: GNOME},
	journal = {Information Systems Journal},
	volume = {12},
	year = {2002},
	note = {"Also retrieved by a Perl script were the postings to the relevant discussion lists including the sender, the subject, time and complete text. For analysis of the posting behaviour of the programmers, the short name that each programmer uses for checkins had to be matched to the full name or email address used for postings. For 175 persons, this has been possible using several regular expressions with human check-up."},
	month = {01/2002},
	pages = {27 - 42},
	abstract = {This paper presents results from research into open source projects from a software engineering perspective. The research methodology employed relies on public data retrieved from the CVS repository of the GNOME project and relevant discussion groups. This methodology is described, and results concerning the special characteristics of open source software development are given. These data are used for a first approach to estimating the total effort to be expended.},
	keywords = {cvs, discussion, effort estimation, gnome},
	issn = {1365-2575},
	doi = {10.1046/j.1365-2575.2002.00110.x},
	author = {Koch, Stefan and Schneider, Georg}
}
@unpublished {flosswp49,
	title = {The Emergence of a new commercial actor: community managed software projects (Please contact the author for the dissertation)},
	year = {2002},
	month = {June},
	abstract = {Institutional theory has matured to the point where we know a great deal about how institutions, once formed, are reproduced. We know less about how they are constructed. This study examines how social movements might inspire the creation of new organizing mechanisms. If new organizational forms result from recombination of existing elements, how might challenging and defending groups affect their construction? An inductive, ethnographic approach was used to examine interactions between community managed software projects from the free software and open source social movements (challengers) and established firms in the software industry (defenders). With interviews of seventy contributors and close examination of the practices used by four projects to manage their interactions with firms., I find that both community projects and firms made changes in their practices and form to better collaborate.},
	author = {Siobhan O{\textquoteright}Mahony}
}
@conference {1156,
	title = {The evolution of the GNOME Project},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {The GNOME Project is an attempt to create a GUI desktop for Unix systems. Originally started by a handful of volunteers in 1996, GNOME has become the desktop of choice for Solaris, HP-UX, and Red Hat Linux, and it is currently developed by a team of approximately five hundred people around the world. The importance of GNOME to the Unix world has attracted the attention of several software companies who are actively participating in its development. At the same time, some of its volunteer developers have created enterprises who expect to sell services and products around GNOME. This extended abstract describes, first, the development model of GNOME, then the influence that private companies had had on the project: on one hand they are contributing a large amount of resources to the project, accelerating its development, and increasing its reliability and documentation; and on the other hand, the GNOME Foundation has been created to maintain the goal of the project to provide a free (as in freedom) software desktop for Unix, and avoid that the commercial interests of these partners could jeopardize the interests of the community.},
	keywords = {commercial software, gnome, organizational sponsorship},
	attachments = {https://flosshub.org/sites/flosshub.org/files/German.pdf},
	author = {Daniel M. German}
}
@conference {Nakakoji:2002:EPO:512035.512055,
	title = {Evolution patterns of open-source software systems and communities},
	booktitle = {Proceedings of the International Workshop on Principles of Software Evolution},
	series = {IWPSE {\textquoteright}02},
	year = {2002},
	pages = {76{\textendash}85},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open-Source Software (OSS) development is regarded as a successful model of encouraging "natural product evolution". To understand how this "natural product evolution" happens, we have conducted a case study of four typical OSS projects. Unlike most previous studies on software evolution that focus on the evolution of the system per se, our study takes a broader perspective: It examines not only the evolution of OSS systems, but also the evolution of the associated OSS communities, as well as the relationship between the two types of evolution.Through the case study, we have found that while collaborative development within a community is the essential characteristic of OSS, different collaboration models exist, and that the difference in collaboration model results in different evolution patterns of OSS systems and communities. To treat such differences systematically, we propose to classify OSS into three types: Exploration-Oriented, Utility-Oriented, and Service-Oriented. Such a classification can provide guidance on the creation and maintenance of sustainable OSS development and communities.},
	keywords = {case study, open-source software (OSS), open-source software community, software evolution},
	isbn = {1-58113-545-9},
	doi = {10.1145/512035.512055},
	url = {http://doi.acm.org/10.1145/512035.512055},
	author = {Nakakoji, Kumiyo and Yamamoto, Yasuhiro and Nishinaka, Yoshiyuki and Kishida, Kouichi and Ye, Yunwen}
}
@proceedings {142,
	title = {An exploratory study of factors influencing the level of vitality and popularity of open source projects},
	year = {2002},
	pages = {853{\textendash}857},
	author = {Katherine Stewart and Ammeter, A. P.}
}
@conference {stewart2002an-explorat,
	title = {An Exploratory Study of Factors Influencing the Level of Vitality and Popularity of Open Source Projects},
	booktitle = {ICIS 2002. Proceedings of International Conference on Information Systems 2002},
	year = {2002},
	note = {"We are currently tracking publicly available data on 240 open source projects registered on the freshmeat Website." "First, we randomly selected a total of 120 projects from the utilities, software development, and games and entertainment areas. We then selected 120 projects from these forums that had been registered on the site during the two weeks prior to the start of our data collection effort."},
	month = {2002},
	pages = {1-5},
	abstract = {In this research, we ask the question: What differentiates successful from unsuccessful open source software projects? Using a sample of 240 open source projects, we examine how organizational sponsorship, target audience (developer versus end user), license choice, and development status interact over time to influence the extent to which open source software projects attract user attention and developer activity.},
	keywords = {activity, audience, developers, freshmeat, license analysis, licenses, organizational sponsorship, project success, roles, status, target audience, users},
	author = {Stewart, Katherine J. and Ammeter, Tony}
}
@article {flosswp48,
	title = {Exploring the Open Source Software Phenomenon: Issues for Organization Science},
	year = {2002},
	month = {April},
	abstract = {Currently two models of innovation are prevalent in organization science. The "private investment" model assumes returns to the innovator results from private goods and efficient regimes of intellectual property protection. The "collective action" model assumes that under conditions of market failure, innovators collaborate in order to produce a public good. In this paper we propose that open source software development is an exemplar of a compound model of innovation that contains elements of both the private investment and the collective action models. We describe a new set of research questions this model raises for scholars in organization science.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hippelkrogh.pdf},
	author = {von Hippel, Eric}
}
@conference {1155,
	title = {Exploring the Strengths and Limits of Open Source Software Engineering Processes: A Research Agenda},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {Many researchers have investigated the nature and characteristics of open source software (OSS) projects and their developer communities. In this position paper, after examining some success factors, we discuss potential limits on the replicability and portability of OSS engineering processes. Based on this analysis, we propose a research agenda to better understand the current nature of the processes and thus the strengths and the limitations.},
	keywords = {replicability, requirements, research, research agenda},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonScozzi.pdf},
	author = {Kevin Crowston and Barbara Scozzi}
}
@article {flosswp19,
	title = {Epistemic Communities, Situated Learning and Open Source Software},
	year = {2001},
	month = {July},
	abstract = {This paper analyzes open source software development as an epistemic community where each individual open source software project is perceived as a single epistemic community. Open source software development is a learning process where the involved parties contribute to, and learn from, the community. It is discovered that theory of epistemic communities does indeed contribute to the understanding of open source software development.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kasperedwards-ec.pdf},
	author = {Kasper Edwards}
}
@proceedings {140,
	title = {An exploratory study of ideology and trust in open source development groups},
	year = {2001},
	note = {"To do this, we scanned information in the public domain to develop a preliminary understanding of the context. We then identified 48 OS projects using www.sourceforge.net, an on-line open source meeting place that provides information on open source efforts and hosts code repositories. Projects were selected to represent a variety of types of software, licenses, and group sizes. We contacted administrators or project leaders and asked them to complete open-ended questionnaires regarding their experience and views on open source development."},
	abstract = {Open source (OS) software development has been the subject of heightened interest among organizational scholars because of the novel social coordination practices that signal a departure from traditional proprietary software development. We propose that trust among group members in open source development groups (OSDGs) plays a key role in facilitating their success. Trust is important in this context because of the risk of opportunistic behavior by other members who volunteers may not have met and may never expect to meet, as well as a lack of explicit market contracts or common organizational affiliation. The open source community is differentiated by a coherent ideology that emphasizes a distinct set of interrelated norms, beliefs, and values. These serve to create incentives for open source practices that eschew conventional transactional norms in favor of a gift culture and a focus on reputations. In this study, we primarily examine the role of the shared ideology in enabling the development of affective and cognitive trust in OSDGs. We further examine how this trust leads to desired outcomes - group efficacy and effectiveness. The study is based on exploratory interviews, examination of archival records and a preliminary survey to understand the specific conditions of open source efforts on which this work-in-progress report is based. This is being followed-up by empirical testing of our research model through a survey of a broad variety of OSDGs. This study would contribute to a clarification of the role of trust in enabling software groups to work effectively and help to understand the bases of trust in ideology-permeated groups.},
	keywords = {contributors, groups, ideology, license analysis, licenses, metadata, open source, sourceforge, Survey, team, team size, teams, trust, types},
	doi = {10.1.1.104.638},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.104.638\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/stewartGosain2001.pdf},
	author = {Katherine Stewart and Gosain, S.}
}
@article {flosswp5,
	title = {Economic Model for Impact of Open Source Software},
	year = {2000},
	month = {November},
	abstract = {This paper presents an economic model of the impact of Open Source Software (OSS) upon a commercial software market. Agents are used to model the users (buyers), the companies (sellers), the code bank (marketplace), and the OSS community (source of free goods). The effect of introducing open source products into an equilibrium commercial market is investigated with respect to demand structure.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osseconomics.pdf},
	author = {Asif Khalak}
}
@article {flosswp18,
	title = {Economics of Open Source Software},
	year = {2000},
	month = {December},
	abstract = {A simple model of open source software is presented. Individual user-programmers decide whether to invest their valuable time and effort to develop a software application that will become a public good if so developed. The benefits and drawbacks of open source versus profit driven developments are presented. The effect of changing the population size of user-programmers is considered; finite and asymptotic results (relevant for some of the larger projects that exist) are given.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/johnsonopensource.pdf},
	author = {Justin Pappas Johnson}
}
@article {flosswp11,
	title = {Essence of Distributed Work: The Case of the Linux Kernel},
	year = {2000},
	month = {November},
	abstract = {This paper provides a historical account of how the Linux operating system kernel was developed from three different perspectives. Each focuses on different critical factors in its success at the individual, group, and community levels. The paper concludes by summarizing the factors important in the successful distributed development of the Linux kernel, and the implications for organizationally managed distributed work arrangements.},
	author = {JY Moon}
}
@conference {Godfrey:2000:EOS:850948.853411,
	title = {Evolution in Open Source Software: A Case Study},
	booktitle = {Proceedings of the International Conference on Software Maintenance (ICSM{\textquoteright}00)},
	series = {ICSM {\textquoteright}00},
	year = {2000},
	note = {"We examined 96 kernel versions..."
.c files, .h files only
loc, lines of code
number of functions
number of modules},
	pages = {131{\textendash}},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {Most studies of software evolution have been performed on systems developed within a single company using traditional management techniques. With the widespread availability of several large software systems that have been developed using an {\textquoteright}open source{\textquoteright} development approach, we now have a chance to examine these systems in detail, and see if their evolutionary narratives are significantly different from commercially developed systems. This paper summarizes our preliminary investigations into the evolution of the best known open source system: the Linux operating system kernel. Because Linux is large (over two million lines of code in the most recent version) and because its development model is not as tightly planned and managed as most industrial software processes, we had expected to find that Linux was growing more slowly as it got bigger and more complex. Instead, we have found that Linux has been growing at a super-linear rate for several years. In this paper, we explore the evolution of the Linux kernel both at the system level and within the major subsystems, and we discuss why we think Linux continues to exhibit such strong growth.},
	keywords = {evolution, functions, growth, lines of code, linux, linux kernel, loc, source code},
	isbn = {0-7695-0753-0},
	url = {http://portal.acm.org/citation.cfm?id=850948.853411},
	attachments = {https://flosshub.org/sites/flosshub.org/files/godfrey00.pdf},
	author = {Godfrey, Michael W. and Tu, Qiang}
}
@article {114,
	title = {An Empirical Approach to Studying Software Evolution},
	journal = {IEEE Transactions On Software Engineering},
	volume = {25},
	number = {4},
	year = {1999},
	abstract = {With the approach of the new millennium, a primary focus in software engineering involves issues relating to upgrading, migrating, and evolving existing software systems. In this environment, the role of careful empirical studies as the basis for improving software maintenance processes, methods, and tools is highlighted. One of the most important processes that merits empirical evaluation is software evolution. Software evolution refers to the dynamic behavior of software systems as they are maintained and enhanced over their lifetimes. Software evolution is particularly important as systems in organizations become longer-lived. However, evolution is challenging to study due to the longitudinal nature of the phenomenon in addition to the usual difficulties in collecting empirical data. In this paper, we describe a set of methods and techniques that we have developed and adapted to empirically study software evolution. Our longitudinal empirical study involves collecting, coding, and analyzing more than 25,000 change events to 23 commercial software systems over a 20-year period. Using data from two of the systems, we illustrate the efficacy of flexible phase mapping and gamma sequence analytic methods originally developed in social psychology to examine group problem solving processes. We have adapted these techniques in the context of our study to identify and understand the phases through which a software system travels as it evolves over time. We contrast this approach with time series analysis, the more traditional way of studying longitudinal data. Our work demonstrates the advantages of applying methods and techniques from other domains to software engineering and illustrates how, despite difficulties, software evolution can be empirically studied.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/EmpiricalApproachSwEvolution_SlaughterKemerer1999.pdf},
	author = {Kemerer, Chris F. and Sandra Slaughter}
}
