@proceedings {1896,
	title = {Addressing Lock-in, Interoperability, and Long-Term Maintenance Challenges Through Open Source: How Can Companies Strategically Use Open Source?},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {80-88},
	publisher = {Springer},
	abstract = {This industry paper reports on how strategic use of open source in company contexts can provide effective support for addressing the fundamental challenges of lock-in, interoperability, and longevity of software and associated digital assets. The fundamental challenges and an overview of an ongoing collaborative research project are presented. Through a conceptual model for open source usage in company contexts we characterise how companies engage with open source and elaborate on how the fundamental challenges can be effectively addressed through open source usage in company contexts.

},
	doi = {10.1007/978-3-319-57735-7_9},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_9},
	author = {Lundell, Bj{\"o}rn and Gamalielsson, Jonas and Stefan Tengblad and Bahram Hooshyar Yousefi and Thomas Fischer and Gert Johansson and Bengt Rodung and Mattsson, Anders and Johan Oppmark and Gustavsson, Tomas and Feist, Jonas and Stefan Landemoo and Erik L{\"o}nroth}
}
@proceedings {1901,
	title = {Adoption of Academic Tools in Open Source Communities: The Debian Case Study},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {139-150},
	publisher = {Springer},
	abstract = {Component repositories play a key role in the open software ecosystem. Managing the evolution of these repositories is a challenging task, and maintainers are confronted with a number of complex issues that need automatic tools to be adressed properly.

In this paper, we present an overview of 10 years of research in this field and the process leading to the adoption of our tools in a FOSS community. We focus on the Debian distribution and in particular we look at the issues arising during the distribution lifecycle: ensuring buildability of source packages, detecting packages that cannot be installed and bootstrapping the distribution on a new architecture. We present three tools, distcheck, buildcheck and botch, that we believe of general interest for other open source component repositories.

The lesson we have learned during this journey may provide useful guidance for researchers willing to see their tools broadly adopted by the community.},
	keywords = {components, debian, distribution},
	doi = {10.1007/978-3-319-57735-7_14},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_14},
	author = {Abate, Pietro and Di Cosmo, Roberto}
}
@proceedings {1916,
	title = {Advancing Open Science with Version Control and Blockchains},
	year = {2017},
	month = {05/2017},
	pages = {13-14},
	abstract = {The scientific community is facing a crisis of reproducibility:
confidence in scientific results is damaged by
concerns regarding the integrity of experimental data and the
analyses applied to that data. Experimental integrity can be
compromised inadvertently when researchers overlook some
important component of their experimental procedure, or intentionally
by researchers or malicious third-parties who are
biased towards ensuring a specific outcome of an experiment.
The scientific community has pushed for {\textquotedblleft}open science{\textquotedblright} to add
transparency to the experimental process, asking researchers to
publicly register their data sets and experimental procedures.
We argue that the software engineering community can leverage
its expertise in tracking traceability and provenance of source
code and its related artifacts to simplify data management for
scientists. Moreover, by leveraging smart contract and blockchain
technologies, we believe that it is possible for such a system to
guarantee end-to-end integrity of scientific data and results while
supporting collaborative research.},
	keywords = {blockchain, replication, reproducible},
	author = {Jonathan Bell and Thomas D. LaToza and Foteini Baldmitsi and Angelos Stavrou}
}
@proceedings {1902,
	title = {Assessing Code Authorship: The Case of the Linux Kernel},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {151-163},
	publisher = {Springer},
	abstract = {Code authorship is a key information in large-scale open-source systems. Among others, it allows maintainers to assess division of work and identify key collaborators. Interestingly, open-source communities lack guidelines on how to manage authorship. This could be mitigated by setting to build an empirical body of knowledge on how authorship-related measures evolve in successful open-source communities. Towards that direction, we perform a case study on the Linux kernel. Our results show that: (a) only a small portion of developers (26\%) makes significant contributions to the code base; (b) the distribution of the number of files per author is highly skewed{\textemdash}a small group of top-authors (3\%) is responsible for hundreds of files, while most authors (75\%) are responsible for at most 11 files; (c) most authors (62\%) have a specialist profile; (d) authors with a high number of co-authorship connections tend to collaborate with others with less connections.},
	keywords = {code authorship, developer network, linux kernel},
	doi = {10.1007/978-3-319-57735-7_15},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_15},
	author = {Guilherme Avelino and Passos, Leonardo and Andre Hora and Marco Tulio Valente}
}
@proceedings {1898,
	title = {Challenges in Validating FLOSS Configuration},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {101-114},
	publisher = {Springer},
	abstract = {Developers invest much effort into validating configuration during startup of free/libre and open source software (FLOSS) applications. Nevertheless, hardly any tools exist to validate configuration files to detect misconfigurations earlier. This paper aims at understanding the challenges to provide better tools for configuration validation. We use mixed methodology: (1) We analyzed 2,683 run-time configuration accesses in the source-code of 16 applications comprising 50 million lines of code. (2) We conducted a questionnaire survey with 162 FLOSS contributors completing the survey. We report our experiences about building up a FLOSS community that tackles the issues by unifying configuration validation with an external configuration access specification.

We discovered that information necessary for validation is often missing in the applications and FLOSS developers dislike dependencies on external packages for such validations.},
	doi = {10.1007/978-3-319-57735-7_11},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_11},
	author = {Raab, M and Barany, G}
}
@proceedings {1910,
	title = {Charting the market disruptive nature of Open Source: Experiences from Sony Mobile },
	year = {2017},
	month = {05/2017},
	pages = {175-176},
	abstract = {Open Source Software (OSS) has substantial impact
on how software-intensive firms develop products and deliver
value to the customers. These companies need both strategic
and operational support on how to adapt OSS as a part of their
products and how to adjust processes and organizations to
increase the benefits from OSS participation. This work
presents the key insights from the journey that Sony Mobile
has made from a company developing proprietary software to
a respected member of OSS communities. We framed the
experiences into an Open Source Maturity Model that includes
two scenarios: engineering-driven and business-driven open
source. We outline the most important decisions, roles,
processes and implications. },
	keywords = {ecosystem, poster, software business},
	author = {Mols, CE and Wnuk, K}
}
@proceedings {1915,
	title = {Classifying code comments in Java open-source software systems},
	year = {2017},
	note = {"we conducted an in-depth analysis of the
comments in the source code files of six major OSS systems
in Java"},
	month = {05/2017},
	pages = {227-237},
	abstract = {Code comments are a key software component
containing information about the underlying implementation.
Several studies have shown that code comments enhance the
readability of the code. Nevertheless, not all the comments have
the same goal and target audience. In this paper, we investigate
how six diverse Java OSS projects use code comments, with the
aim of understanding their purpose. Through our analysis, we
produce a taxonomy of source code comments; subsequently, we
investigate how often each category occur by manually classifying
more than 2,000 code comments from the aforementioned
projects. In addition, we conduct an initial evaluation on how
to automatically classify code comments at line level into our
taxonomy using machine learning; initial results are promising
and suggest that an accurate classification is within reach.},
	keywords = {java, Survey},
	author = {Luca Pascarella and Bacchelli, Alberto}
}
@conference {Murphy:2017:CEF:3017680.3017682,
	title = {Community Engagement with Free and Open Source Software},
	booktitle = {Proceedings of the 2017 ACM SIGCSE Technical Symposium on Computer Science Education},
	series = {SIGCSE {\textquoteright}17},
	year = {2017},
	pages = {669{\textendash}670},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {A common refrain from Senior Exit Surveys and Alumni Surveys is the desire to work on "real-world," "practical" and "hands-on" projects using industry-ready tools and development environments. To assuage this, institutions have moved towards adopting Free and Open Source Software (FOSS) as an avenue to provide meaningful, applied learning interventions to students. Through these experiences, students benefit from engagement with various communities including: the community of contributors to the FOSS project; the community of local software developers; the community of citizens who reside in the local area; the community of students at their institution and others; and, the community of people impacted by the FOSS project. These engagements motivate students, enhance their communication and technical skills, allow them to grow and become more confident, help them form professional networks, and provide the "real-world" projects they seek. In this panel, we will discuss our experiences in engaging students with five different types of communities as part of incorporating FOSS into our courses, focusing on how other educators can provide the same benefits to their students as well. In order to satisfy the time constraints of the panel, the last two authors will present together.},
	keywords = {free and open source software (FOSS), humanitarian free and open source software (HFOSS), localized free and open source software (LFOSS), under-represented minorities (URM)},
	isbn = {978-1-4503-4698-6},
	doi = {10.1145/3017680.3017682},
	url = {http://doi.acm.org/10.1145/3017680.3017682},
	author = {Murphy, Christian and Buffardi, Kevin and Dehlinger, Josh and Lambert, Lynn and Veilleux, Nanette}
}
@proceedings {1875,
	title = {Considering the use of walled gardens for FLOSS project communication},
	year = {2017},
	month = {05/2017},
	abstract = {At its core, free, libre, and open source software (FLOSS) is defined by its adherence to a set of licenses that give various freedoms to the users of the software, for example the ability to use the software, to read or modify its source code, and to distribute the software to others. In addition, many FLOSS projects and developers also champion other values related to "freedom" and "openness", such as transparency, for example in communication and decision-making, or community-orientedness, for example in broadening access, collaboration, and participation. This paper explores how one increasingly common software development practice - communicating inside non-archived, third-party "walled gardens" - puts these FLOSS values into conflict. If communities choose to use non-archived walled gardens for communication, they may be prioritizing one type of openness (broad participation) over another (transparency). We use 18 FLOSS projects as a sample to describe how walled gardens are currently being used for intra-project communication, as well as to determine whether or not these projects provide archives of these communications. Findings will be useful to the FLOSS community as a whole as it seeks to under- stand the evolution and impact of its communication choices.},
	keywords = {apache, chat, communication, email, free software, irc, mailing list, open source, Slack, Stack Overflow, teams, Wordpress},
	doi = {10.1007/978-3-319-57735-7_1},
	url = {https://link.springer.com/content/pdf/10.1007\%2F978-3-319-57735-7_1.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/preprint_0.pdf},
	author = {Squire, Megan}
}
@proceedings {1890,
	title = {Designing for Participation: Three Models for Developer Involvement in Hybrid OSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {23-33},
	publisher = {Springer},
	abstract = {This paper reports governance practices of three profit oriented companies that develop OSS software with the help of their respective open development communities. We explore how the companies allow development contributions from external stakeholders, and what knowledge they let out of their internal software development activities. The results lay ground for further research on how to organize openness of the software development process in hybrid setups where the needs of different stakeholders are partly competing - yet complementary.},
	keywords = {Community Management, Hybrid open source, open source},
	doi = {10.1007/978-3-319-57735-7_3},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_3},
	author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and Mikkonen, Tommi and M{\"a}nnist{\"o}, Tomi}
}
@proceedings {1912,
	title = {Developer Turnover in Global, Industrial Open Source Projects: Insights from Applying Survival Analysis},
	year = {2017},
	note = {we study five industrial OSS projects of different
sizes (in terms of software size, contributors and number
of companies involved) and examine whether the duration
of developers staying in a project is related to following
four factors: (i) the time of first contribution, (ii) the rate of
maintaining own files, (iii) the main action type, and (iv) the
main job type

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

Findings: The survey results indicate that most of the 375 respondents
to our survey struggle with understanding the interaction of
open source licenses in both simple and complex software
development cases},
	month = {05/2017},
	pages = {1-11},
	abstract = {{\textemdash}Software provided under open source licenses is
widely used, from forming high-profile stand-alone applications
(e.g., Mozilla Firefox) to being embedded in commercial offerings
(e.g., network routers). Despite the high frequency of use of open
source licenses, there has been little work about whether software
developers understand the open source licenses they use. To our
knowledge, only one survey has been conducted, which focused
on which licenses developers choose and when they encounter
problems with licensing open source software. To help fill the
gap of whether or not developers understand the open source
licenses they use, we conducted a survey that posed development
scenarios involving three popular open source licenses (GNU GPL
3.0, GNU LGPL 3.0 and MPL 2.0) both alone and in combination.
The 375 respondents to the survey, who were largely developers,
gave answers consistent with those of a legal expert{\textquoteright}s opinion in
62\% of 42 cases. Although developers clearly understood cases
involving one license, they struggled when multiple licenses were
involved. An analysis of the quantitative and qualitative results of
the study indicate a need for tool support to help guide developers
in understanding this critical information attached to software
components.},
	keywords = {license, Survey},
	doi = {10.1109/ICPC.2017.7},
	author = {Almeida, Daniel A. and Murphy, Gail C. and Wilson, Greg and Hoye, Mike}
}
@proceedings {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}
}
@proceedings {1895,
	title = {How are Developers Treating License Inconsistency Issues? A Case Study on License Inconsistency Evolution in FOSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {69-79},
	publisher = {Springer},
	abstract = {A license inconsistency is the presence of two or more source files that evolved from the same original file containing different licenses. In our previous study, we have shown that license inconsistencies do exist in open source projects and may lead to potential license violation problems. In this study, we try to find out whether the issues of license inconsistencies are properly solved by analyzing two versions of a FOSS distribution{\textemdash}Debian{\textemdash}and investigate the evolution patterns of license inconsistencies. Findings are: license inconsistencies occur mostly because the original copyright owner updated the license while the reusers were still using the old version of the source files with the old license; most license inconsistencies would disappear when the reusers synchronize their project from the upstream, while some would exist permanently if reusers decide not to synchronize anymore. Legally suspicious cases have not been found yet in those Debian distributions.},
	keywords = {Code clone, debian, License inconsistency, licenses, Software license},
	doi = {10.1007/978-3-319-57735-7_8},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_8},
	author = {Y. Wu and Manabe, Yuki and Daniel M. Germ{\'a}n and Inoue, K.}
}
@proceedings {1909,
	title = {How Does Contributors{\textquoteright} Involvement Influence the Build Status of an Open-Source Software Project?},
	year = {2017},
	note = {We used the data released by TravisTorrent
on 06-Dec-2016 as our main data source.},
	month = {05/2017},
	pages = {475-478},
	abstract = {The recent introduction of the pull-based development
model promoted agile development practices such as
Code Reviews and Continuous Integration (CI). CI, in particular,
is currently a standard development practice in opensource
software (OSS) projects. Although it is well-known that
OSS contributors have different involvements (e.g., while some
developers drive the project, there is a long tail of peripheral
developers), little is known about how the contributor{\textquoteright}s degree
of participation can influence the build status of an OSS project.
Through TravisTorrent{\textquoteright}s dataset, we compare the success rates
of builds made by casual and non-casual contributors and what
factors on their contributions may influence the build result. Our
results suggest that there is no representative difference between
their build success (they are similar in 85\% of the analyzed
projects), meaning that being a casual contributor is not a strong
indicator for creating failing builds. Also, factors like the size
of their contributions and the number of project configurations
(jobs) have the potential of impacting the build success.},
	keywords = {travis torrent},
	author = {Reboucas, Marcel and Santos, Renato O. and Pinto, Gustavo and Fernando Castor}
}
@proceedings {1908,
	title = {How Open Source Projects use Static Code Analysis Tools in Continuous Integration Pipelines},
	year = {2017},
	note = {Data: the paper studies the use of ASCATs (Automated Static Code Analysis Tools) within CI pipelines of 20 popular Java open source projects hosted on GitHub and using Travis CI to support CI activities},
	month = {05/2017},
	pages = {334-344},
	abstract = {Static analysis tools are often used by software developers
to entail early detection of potential faults, vulnerabilities,
code smells, or to assess the source code adherence to coding
standards and guidelines. Also, their adoption within Continuous
Integration (CI) pipelines has been advocated by researchers and
practitioners. This paper studies the usage of static analysis tools
in 20 Java open source projects hosted on GitHub and using
Travis CI as continuous integration infrastructure. Specifically,
we investigate (i) which tools are being used and how they are
configured for the CI, (ii) what types of issues make the build fail
or raise warnings, and (iii) whether, how, and after how long are
broken builds and warnings resolved. Results indicate that in the
analyzed projects build breakages due to static analysis tools are
mainly related to adherence to coding standards, and there is also
some attention to missing licenses. Build failures related to tools
identifying potential bugs or vulnerabilities occur less frequently,
and in some cases such tools are activated in a {\textquotedblleft}softer{\textquotedblright} mode,
without making the build fail. Also, the study reveals that build
breakages due to static analysis tools are quickly fixed by actually
solving the problem, rather than by disabling the warning, and
are often properly documented.},
	keywords = {continuous integration, empirical study, static analysis},
	doi = {10.1109/MSR.2017.2},
	author = {Zampetti, Fiorella and Scalabrino, Simone and Oliveto, Rocco and Canfora, Gerardo and Di Penta, Massimiliano}
}
@conference {Sharma:2017:IDE:3084226.3084271,
	title = {Investigating Developers{\textquoteright} Email Discussions During Decision-making in Python Language Evolution},
	booktitle = {Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering},
	series = {EASE{\textquoteright}17},
	year = {2017},
	pages = {286{\textendash}291},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Context: Open Source Software (OSS) developers use mailing lists as their main forum for discussing the evolution of a project. However, the use of mailing lists by developers for decision-making has not received much research attention. Objective: We have explored this issue by studying developers{\textquoteright} email discussions around Python Enhancement Proposals (PEPs). Method: Our dataset comprised 42,672 emails from six different mailing lists pertaining to PEP development. We performed multiple forms of analysis on these emails, involving both quantitative measures (e.g., frequency) and deeper analysis of specific PEP discussions (i.e., outlier analysis). Results: Out of three PEP types (Informational, Process and Standard Track), Standard Track PEPs attract a large amount of discussion (both in volume and average number of messages per proposal). Our study also identified specific PEP states and topics that generated a disproportionate amount of discussion. Conclusion: Our outcomes point to several opportunities for improving the management of an OSS team based on the knowledge generated from discussions. We have also identified several interesting avenues for future work such as identifying individuals or groups that present persuasive arguments during decision-making.},
	keywords = {Decision-making, Email discussions, Python development},
	isbn = {978-1-4503-4804-1},
	doi = {10.1145/3084226.3084271},
	url = {http://doi.acm.org/10.1145/3084226.3084271},
	author = {Sharma, Pankajeshwara and Savarimuthu, Bastin Tony Roy and Stanger, Nigel and Licorish, Sherlock A. and Rainer, Austen}
}
@conference {1925,
	title = {Investigating developers{\textquoteright} email discussions during decision-making in Python language evolution},
	booktitle = {Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering  - EASE{\textquoteright}17},
	year = {2017},
	pages = {286 - 291},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Karlskrona, SwedenNew York, New York, USA},
	abstract = {Context: Open Source Software (OSS) developers use mailing lists as their main forum for discussing the evolution of a project. However, the use of mailing lists by developers for decision-making has not received much research attention. Objective: We have explored this issue by studying developers{\textquoteright} email discussions around Python Enhancement Proposals (PEPs). Method: Our dataset comprised 42,672 emails from six different mailing lists pertaining to PEP development. We performed multiple forms of analysis on these emails, involving both quantitative measures (e.g., frequency) and deeper analysis of specific PEP discussions (i.e., outlier analysis). Results: Out of three PEP types (Informational, Process and Standard Track), Standard Track PEPs attract a large amount of discussion (both in volume and average number of messages per proposal). Our study also identified specific PEP states and topics that generated a disproportionate amount of discussion. Conclusion: Our outcomes point to several opportunities for improving the management of an OSS team based on the knowledge generated from discussions. We have also identified several interesting avenues for future work such as identifying individuals or groups that present persuasive arguments during decision-making.},
	isbn = {9781450348041},
	doi = {10.1145/3084226.3084271},
	url = {https://www.researchgate.net/publication/317486549_Investigating_developers\%27_email_discussions_during_decision-making_in_Python_language_evolution},
	author = {Stanger, Nigel and Rainer, Austen and Licorish, Sherlock A. and Sharma, Pankajeshwara and Savarimuthu, Bastin Tony Roy}
}
@proceedings {1889,
	title = {Investigating Relationships Between FLOSS Foundations and FLOSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {14-22},
	publisher = {Springer},
	abstract = {Foundations function as vital institutional support infrastructures for many of the most successful open source projects, but the role of these support entities remains an understudied phenomenon in FLOSS research. Drawing on Open Hub (formerly known as Ohloh) data, this paper empirically investigates the different ways these entities support projects and interact with different projects and with each other.},
	doi = {10.1007/978-3-319-57735-7_2},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_2},
	author = {Juho Lindman and Hammouda, Imed}
}
@inbook {Kerzazi2017,
	title = {Knowledge Flows Within Open Source Software Projects: A Social Network Perspective},
	booktitle = {Advances in Ubiquitous Networking 2: Proceedings of the UNet{\textquoteright}16},
	year = {2017},
	pages = {247{\textendash}258},
	publisher = {Springer Singapore},
	organization = {Springer Singapore},
	address = {Singapore},
	abstract = {Developing software is knowledge-intensive activity, requiring extensive technical knowledge and awareness. The abstract part of development is the social interactions that drive knowledge flows between contributors, especially for Open Source Software (OSS). This study investigated knowledge sharing and propagation from social perspective using social network analysis (SNA). We mined and analyzed the issue and review histories of three OSS from GitHub. Particular attention has been paid to the socio-interactions through comments from contributors on reviews. We aim at explaining the propagation and density of knowledge flows within contributor networks. The results show that review requests flow from the core contributors toward peripheral contributors and comments on reviews are in a continuous loop from the core teams to the peripherals and back; and the core contributors leverage on their awareness and technical knowledge to increase their notoriety by playing the role of communication brokers supported by comments on work items.},
	keywords = {expertise, Knowledge flows, open source, SNA},
	isbn = {978-981-10-1627-1},
	doi = {10.1007/978-981-10-1627-1_19},
	url = {http://dx.doi.org/10.1007/978-981-10-1627-1_19},
	author = {Kerzazi, Noureddine and El Asri, Ikram},
	editor = {El-Azouzi, Rachid and Menasche, Daniel Sadoc and Sabir, Essa{\"\i}d and De Pellegrini, Francesco and Benjillali, Mustapha}
}
@proceedings {1919,
	title = {A Large-Scale Study on the Usage of Testing Patterns that Address Maintainability Attributes},
	year = {2017},
	note = {"we conducted a large-scale empirical study to measure
the application of software testing in the open source community"

Our novel approach
includes a data set of 82,447 open source projects written in
48 languages

The data used in this study include 82,447 open source
projects, 251 unit testing frameworks, and 4 unit testing
patterns

data url: https://goo.gl/Mc7tHk},
	month = {05/2017},
	pages = {391-401},
	abstract = {Test case maintainability is an important concern,
especially in open source and distributed development environments
where projects typically have high contributor turnover
with varying backgrounds and experience, and where code
ownership changes often. Similar to design patterns, patterns
for unit testing promote maintainability quality attributes such
as ease of diagnoses, modifiability, and comprehension. In this
paper, we report the results of a large-scale study on the usage
of four xUnit testing patterns which can be used to satisfy these
maintainability attributes. This is a first-of-its-kind study which
developed automated techniques to investigate these issues across
82,447 open source projects, and the findings provide more insight
into testing practices in open source projects. Our results indicate
that only 17\% of projects had test cases, and from the 251
testing frameworks we studied, 93 of them were being used.
We found 24\% of projects with test files implemented patterns
that could help with maintainability, while the remaining did
not use these patterns. Multiple qualitative analyses indicate that
usage of patterns was an ad-hoc decision by individual developers,
rather than motivated by the characteristics of the project, and
that developers sometimes used alternative techniques to address
maintainability concerns.},
	keywords = {maintenance, mining software repositories, msr, Unit Test Frameworks, Unit Test Patterns, Unit Testing},
	author = {Danielle Gonzalez and Joanna C.S. Santos and Andrew Popovich and Mehdi Mirakhorli and Mei Nagappan}
}
@proceedings {1905,
	title = {Longitudinal Analysis of the Run-up to a Decision to Break-up (Fork) in a Community},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {204-217},
	publisher = {Springer},
	abstract = {In this paper, we use a developer-oriented statistical approach to understand what causes people in complex software development networks to decide to fork (break away), and what changes a community goes through in the run-up to a decision to break-up. Developing complex software systems is complex. Software developers interact. They may have the same or different goals, communication styles, or values. Interactions can be healthy or troubled. Troubled interactions cause troubled communities, that face failure. Some of these failures manifest themselves as a community split (known as forking). These failures affects many people; developers and users. Can we save troubled projects? We statistically model the longitudinal socio-grams of software developers and present early indicators and warning signs that can be used to predict an imminent break-up decision.

},
	keywords = {community of software developers, forks, longitudinal study},
	doi = {10.1007/978-3-319-57735-7_19},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_19},
	author = {Amirhosein {\textquotedblleft}Emerson{\textquotedblright} Azarbakht and Jensen, Carlos}
}
@proceedings {1911,
	title = {Machine Learning-Based Detection of Open Source License Exceptions},
	year = {2017},
	note = {"We address these questions by first performing a large scale mining-based study... [W]e analyzed the  source code of 51,754 projects written in six different programming languages (Ruby, Javascript, Python, C, C++, and C$\#$) hosted on GitHub. },
	month = {05/2017},
	pages = {118-129},
	abstract = {From a legal perspective, software licenses govern the redistribution, reuse, and modification of software as both source and binary code. Free and Open Source Software (FOSS) licenses vary in the degree to which they are permissive or restrictive in allowing redistribution or modification under licenses different from the original one(s). In certain cases developers may modify the license by appending to it an exception to specifically allow reuse or modification under a particular condition. These exceptions are an important factor to consider for license compliance analysis since they modify the standard (and widely understood_ terms of the original license. In this work, we first perform a large-scale empirical study on the change history of over 51k FOSS systems aimed at quantitatively investigating the prevalence of known license exceptions and identifying new ones. Subsequently, we performed a study on the detection of license exceptions by relying on machine learning. We evaluated the license exception classification with four different supervised learners and sensitivity analysis. Finally we present a categorization of license exceptions and explain their implications.},
	keywords = {classifier, empirical studies, license, machine learning},
	doi = {10.1109/ICSE.2017.19},
	author = {Vendome, Christopher and Mario Linares-Vasquez and Bavota, Gabriele and Di Penta, Massimiliano and Daniel M. German and Poshyvanyk, Denys}
}
@article {1868,
	title = {Managing knowledge sharing in distributed innovation from the perspective of developers: empirical study of open source software projects in China},
	journal = {Technology Analysis \& Strategic Management},
	volume = {2929143029},
	year = {2017},
	month = {01/2017},
	pages = {1 - 22},
	abstract = {Knowledge sharing is the key factor that influences the performance of open source software (OSS) projects, which are the representative cases of distributed innovation. This paper aims to explore the mechanism of knowledge sharing in OSS projects from the perspective of developers in China. A quantitative method with the analysis of 403 valid questionnaires is adopted. A series of hypotheses about how distributed innovation (independent variables) influences knowledge sharing (mediating variable) and then affects the performance of OSS projects (dependent variable) are tested and approved. On the one side, we argue that developers will actively affect knowledge sharing in terms of participative motivation, social network and organisational culture. On the other hand, users may also affect the knowledge sharing when considering innovation willingness and capacity. It is interesting to find that social network is the most important factor in Chinese cases. It is strongly recommended to strengthen the collaboration between software companies and OSS communities.},
	keywords = {Distributed innovation, knowledge sharing, performance of OSS projects, user innovation},
	issn = {1465-3990},
	doi = {http://dx.doi.org/10.1080/09537325.2016.1194387},
	author = {Chen, Xiaohong and Zhou, Yuan and Probert, David and Su, Jun}
}
@proceedings {1892,
	title = {Measuring Perceived Trust in Open Source Software Communities},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {49-54},
	publisher = {Springer},
	abstract = {We investigate the different aspects of measuring trust in Open Source Software (OSS) communities. In the theoretical part we review seminal works related to trust in OSS development. This investigation provides background to our empirical part where we measure trust in a community (in terms of kudo). Our efforts provide further avenues to develop trust-based measurement tools. These are helpful for academics and practitioners interesting in quantifiable traits of OSS trust.},
	doi = {10.1007/978-3-319-57735-7_5},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_5},
	author = {Syeed, M.M. Mahbubul and Juho Lindman and Hammouda, Imed}
}
@proceedings {1926,
	title = {Open Source Communities as Liminal Ecosystems},
	year = {2017},
	abstract = {In this paper, we propose a study to explore the movement of individuals engaged in open source communities. Although there is extensive literature on open source communities and growing body of knowledge on corporate engagement in open source communities, our understanding of the movements of individuals within these communities is limited. To analyze these movements, we build on Arnold Van Gennep and Victor Turners{\textquoteright} theories on liminality. Through this lens, we build an understanding of the movements of individual members within open source communities.},
	url = {http://aisel.aisnet.org/mwais2017/45},
	author = {Kevin Lumbard and Matt Germonprez}
}
@proceedings {1893,
	title = {The Open Source Officer Role {\textendash} Experiences},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {55-59},
	publisher = {Springer},
	abstract = {This papers describe the Open Source Officer role and the experiences from introducing this role in several companies. We outline the role description, main responsibilities, and interfaces to other roles and organizations. We investigated the role in several organization and bring interesting discrepancies and overlaps of how companies operate with OSS.

},
	keywords = {governance, inner source, maturity models},
	doi = {10.1007/978-3-319-57735-7_6},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_6},
	author = {Mols, CE and Wnuk, K and Lin{\r a}ker, J}
}
@proceedings {1904,
	title = {OSSpal: Finding and Evaluating Open Source Software},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {193-203},
	publisher = {Springer},
	abstract = {This paper describes the OSSpal project, which is aimed at helping companies, government agencies, and other organizations find high quality free and open source software (FOSS) that meets their needs. OSSpal is a successor to the Business Readiness Rating (BRR), combining quantitative and qualitative evaluation measures for software in various categories. Instead of a purely numeric calculated score OSSpal adds curation of high-quality FOSS projects and individual user reviews of these criteria. Unlike the BRR project, for which there was no automated support, OSSpal has an operational, publicly available website where users may search by project name or category, and enter ratings and reviews for projects.

},
	keywords = {Open source forges, software evaluation, software metrics, Software taxonomy},
	doi = {10.1007/978-3-319-57735-7_18},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_18},
	author = {Wasserman, A. and Guo, X. and McMillian, B. and Qian K. and Wei M.Y. and Xu, Q.}
}
@proceedings {1914,
	title = {Practices and Perceptions of UML Use in Open Source Projects},
	year = {2017},
	month = {05/2017},
	pages = {203-212},
	abstract = {Context: Open Source is getting more and more
collaborative with industry. At the same time, modeling is today
playing a crucial role in development of, e.g., safety critical
software. Goal: However, there is a lack of research about the
use of modeling in Open Source. Our goal is to shed some
light into the motivation and benefits of the use of modeling
and its use within project teams. Method: In this study, we
perform a survey among Open Source developers. We focus on
projects that use the Unified Modeling Language (UML) as a
representative for software modeling. Results: We received 485
answers of contributors of 458 different Open Source projects.
Conclusion: Collaboration seems to be the most important
motivation for using UML. It benefits new contributors and
contributors who do not create models. Teams use UML during
communication and planning of joint implementation efforts.},
	keywords = {architecture documentation, communication, effectiveness of UML, github, MOTIVATION, UML},
	author = {Truong Ho-Quang and Hebig, Regina and Gregorio Robles and Chaudron, Michel R. V. and Miguel Angel Fernandez}
}
@article {1869,
	title = {Predicting bug-fixing time: A replication study using an open source software project},
	journal = {Journal of Systems and Software},
	year = {2017},
	month = {2/2017},
	abstract = {Background: On projects with tight schedules and limited budgets, it may not be possible to resolve all known bugs before the next release. Estimates of the time required to fix known bugs (the {\textquotedblleft}bug fixing time{\textquotedblright}) would assist managers in allocating bug fixing resources when faced with a high volume of bug reports.

Aim: In this work, we aim to replicate a model for predicting bug fixing time with open source data from Bugzilla Firefox.

Method: To perform the replication study, we follow the replication guidelines put forth by Carver [J. C. Carver, Towards reporting guidelines for experimental replications: a proposal, in: 1st International Workshop on Replication in Empirical Software Engineering, 2010.]. Similar to the original study, we apply a Markov-based model to predict the number of bugs that can be fixed monthly. In addition, we employ Monte-Carlo simulation to predict the total fixing time for a given number of bugs. We then use the k-nearest neighbors algorithm to classify fixing times into slow and fast.

Result: The results of the replicated study on Firefox are consistent with those of the original study. The results show that there are similarities in the bug handling behaviour of both systems.

Conclusion: We conclude that the model that estimates the bug fixing time is robust enough to be generalized, and we can rely on this model for our future research.},
	keywords = {Replication study; Bug fixing time; Effort estimation; Software maintainability; Deferred bugs},
	issn = {01641212},
	doi = {10.1016/j.jss.2017.02.021},
	author = {Akbarinasaji, Shirin and Caglayan, Bora and Bener, Ayse}
}
@proceedings {1891,
	title = {Principled Evaluation of Strengths and Weaknesses in FLOSS Communities: A Systematic Mixed Methods Maturity Model Approach},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {34-46},
	publisher = {Springer},
	abstract = {Context: Free and Open Source Software usually results from intricate socio-technical dynamics operating in a diverse and geographically dispersed community. Understanding the fundamental underpinnings of healthy and thriving communities is of paramount importance to evaluate existing efforts and identify improvement opportunities. Objective: This paper presents a novel reference model for evaluating the maturity of FLOSS communities by mixing quantitative and qualitative methods. Method: We build upon established guidelines for Design Science research in order to devise a well-informed and expressive maturity model, describing how those methods and procedures were used in the design and development of such a model. Results: We present the model structure and functions, as well as instructions on how to instantiate it as evaluations of FLOSS communities. The use of the proposed maturity model is demonstrated in four FLOSS communities. Conclusion: Whilst instantiating the model may be burdensome if aiming at sketchy evaluations, results indicate our model effectively captures the maturity regardless aspects such as community size and lifetime.},
	keywords = {Design science research, Discourse communities, evaluation, FLOSS communities, maturity models, Mixed methods research},
	doi = {10.1007/978-3-319-57735-7_4},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_4},
	author = {Andrade, S and Saraiva, F.}
}
@article {1920,
	title = {Process Aspects and Social Dynamics of Contemporary Code Review: Insights from Open Source Development and Industrial Practice at Microsoft},
	journal = {IEEE Transactions on Software Engineering},
	volume = {43},
	year = {2017},
	note = {" We sent the survey
to code review participants from 36 popular OSS projects
and received 287 responses"},
	month = {1/2017},
	pages = {56 - 75},
	abstract = {Many open source and commercial developers practice contemporary code review, a lightweight, informal, tool-based code
review process. To better understand this process and its benefits, we gathered information about code review practices via surveys of
open source software developers and developers from Microsoft. The results of our analysis suggest that developers spend
approximately 10-15 percent of their time in code reviews, with the amount of effort increasing with experience. Developers consider
code review important, stating that in addition to finding defects, code reviews offer other benefits, including knowledge sharing,
community building, and maintaining code quality. The quality of the code submitted for review helps reviewers form impressions about
their teammates, which can influence future collaborations. We found a large amount of similarity between the Microsoft and OSS
respondents. One interesting difference is that while OSS respondents view code review as an important method of impression
formation, Microsoft respondents found knowledge dissemination to be more important. Finally, we found little difference between
distributed and co-located Microsoft teams. Our findings identify the following key areas that warrant focused research: 1) exploring the
non-technical benefits of code reviews, 2) helping developers in articulating review comments, and 3) assisting reviewers{\textquoteright} program
comprehension during code reviews.},
	keywords = {code review, commercial projects, peer impressions, Survey},
	issn = {1939-3520},
	doi = {10.1109/TSE.2016.2576451},
	url = {https://amiangshu.com/papers/CodeReview-TSE-2016.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CodeReview-TSE-2016.pdf},
	author = {Bosu, Amiangshu and Carver, Jeffrey C. and Christian Bird and Orbeck, Jonathan and Chockley, Christopher}
}
@proceedings {1899,
	title = {Progression and Forecast of a Curated Web-of-Trust: A Study on the Debian Project{\textquoteright}s Cryptographic Keyring},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {117-127},
	publisher = {Springer},
	abstract = {The Debian project is one of the largest free software undertakings worldwide. It is geographically distributed, and participation in the project is done on a voluntary basis, without a single formal employee or directly funded person. As we will explain, due to the nature of the project, its authentication needs are very strict{\textemdash}User/password schemes are way surpassed, and centralized trust management schemes such as PKI are not compatible with its distributed and flat organization; fully decentralized schemes such as the PGP Web of Trust are insuficient by themselves. The Debian project has solved this need by using what we termed a {\textquotedblleft}curated Web of Trust{\textquotedblright}.

We will explain some lessons learned from a massive key migration process that was triggered in 2014. We will present the social insight we have found from examining the relationships expressed as signatures in this curated Web of Trust, some recommendations on personal key-signing policies, and a statistical study and forecast on aging, refreshment and survival of project participants stemming from an analysis on their key-handling.},
	keywords = {cryptography, curated Web of Trust, debian, Keyring, trust management},
	doi = {10.1007/978-3-319-57735-7_12},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_12},
	author = {Gunnar Wolf and V{\'\i}ctor Gonz{\'a}lez Quiroga}
}
@proceedings {1903,
	title = {Release Early, Release Often and Release on Time. An Empirical Case Study of Release Management},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {167-181},
	publisher = {Springer},
	abstract = {The dictum of {\textquotedblleft}Release early, release often.{\textquotedblright} by Eric Raymond as the Linux modus operandi highlights the importance of release management in open source software development. Nevertheless, there are very few empirical studies addressing release management in open source software development. It is already known that most open source software communities adopt either feature-based or time-based release strategies. Each of these has its advantages and disadvantages that are context-specific. Recent research reported that many prominent open source software projects have moved from feature-based to time-based releases. In this longitudinal case study, we narrate how OpenStack shifted towards a liberal six-month release cycle. If prior research discussed why projects should adopt time-based releases and how they can adopt such a strategy, we discuss how OpenStack adapted its software development processes, its organizational design and its tools toward a hybrid release management strategy {\textemdash} a strive for balancing the benefits and drawbacks of feature-based and time-based release strategies.},
	keywords = {openstack, release management},
	doi = {10.1007/978-3-319-57735-7_16},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_16},
	author = {Teixeira, Jose}
}
@proceedings {1888,
	title = {Technical Lag in Software Compilations: Measuring How Outdated a Software Deployment Is},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {182 - 192},
	publisher = {Springer International Publishing},
	abstract = {Large software compilations based on free, open source software (FOSS) packages are the basis for many software systems. When they are deployed in production, specific versions of the packages in the compilation are selected for installation. Over time, those versions become outdated with respect to the upstream software from which they are produced, and from the components available in the compilations as well. The fact that deployed components are outdated is not a problem in itself, but there is a price to pay for not being "as much updated as reasonable". This includes bug fixes and new features that could, at least potentially, be interesting for the deployed system. Therefore, a balance has to be maintained between "being up-to-date" and "keeping the good old working versions". This paper proposes a theoretical model (the "technical lag") for measuring how outdated a system is, with the aim of assisting in the decisions about upgrading in production. The paper explores several ways in which technical lag can be implemented, depending on requirements. As an illustration, it presents as well some specific cases in which the evolution of technical lag is computed.},
	isbn = {978-3-319-57735-7},
	issn = {1868-422X},
	doi = {10.1007/978-3-319-57735-7_17},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_17},
	author = {Gonz{\'a}lez-Barahona, J.M. and Sherwood, P. and Robles, G. and Izquierdo, D.},
	editor = {Balaguer, Federico and Di Cosmo, Roberto and Garrido, Alejandra and Kon, Fabio and Gregorio Robles and Zacchiroli, Stefano}
}
@proceedings {1897,
	title = {Understanding the Effects of Practices on KDE Ecosystem Health},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {89-100},
	publisher = {Springer},
	abstract = {Open source software ecosystems have adjusted and evolved a set of practices over the years to support the delivery of sustainable software. However, few studies have investigated the impacts of such practices on the health of these ecosystems. In this paper, we present the results of an ethnographic-based study conducted during the Latin-American KDE users and contributors meeting (LaKademy 2015) with the goal of collecting practices used within the KDE ecosystem and understanding how they affect ecosystem health. The analysis was based on softgoal interdependency graphs adapted to represent practices and relate them to non-functional requirements and goals. Our results provide a preliminary insight to understand how KDE ecosystem community interacts, which working practices have been adopted and how they affect ecosystem health.

},
	keywords = {Ethnographic studies, Open source software ecosystems, Software ecosystem health, Software practices},
	doi = {10.1007/978-3-319-57735-7_10},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_10},
	author = {Simone da Silva Amorim and John D. McGregor and Eduardo Santana de Almeida and Christina von Flach Garcia Chavez}
}
@proceedings {1917,
	title = {Understanding the Impressions, Motivations, and Barriers of One Time Code Contributors to FLOSS Projects: A Survey},
	year = {2017},
	month = {05/2017},
	pages = {187-197},
	abstract = {Successful Free/Libre Open Source Software
(FLOSS) projects must attract and retain high-quality talent.
Researchers have invested considerable effort in the study of
core and peripheral FLOSS developers. To this point, one critical
subset of developers that have not been studied are One-Time
code Contributors (OTC) {\textendash} those that have had exactly one patch
accepted. To understand why OTCs have not contributed another
patch and provide guidance to FLOSS projects on retaining
OTCs, this study seeks to understand the impressions, motivations,
and barriers experienced by OTCs. We conducted an online
survey of OTCs from 23 popular FLOSS projects. Based on the
184 responses received, we observed that OTCs generally have
positive impressions of their FLOSS project and are driven by a
variety of motivations. Most OTCs primarily made contributions
to fix bugs that impeded their work and did not plan on becoming
long term contributors. Furthermore, OTCs encounter a number
of barriers that prevent them from continuing to contribute to the
project. Based on our findings, there are some concrete actions
FLOSS projects can take to increase the chances of converting
OTCs into long-term contributors.},
	keywords = {newcomers, One Time Contributors, Qualitative Research, Survey},
	author = {Amanda Lee and Carver, Jeffrey C. and Bosu, Amiangshu}
}
@proceedings {1900,
	title = {Understanding When to Adopt a Library: A Case Study on ASF Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {128-138},
	publisher = {Springer},
	abstract = {Software libraries are widely used by both industrial and open source client projects. Ideally, a client user of a library should adopt the latest version that the library project releases. However, sometimes the latest version is not better than a previous version. This is because the latest version may include additional developer effort to test and integrate all changed features. In this study, our main goal is to better understand the relationship between adoption of library versions and its release cycle. Specifically, we conducted an empirical study of release cycles for 23 libraries and how they were adopted by 415 Apache Software Foundation (ASF) client projects. Our findings show that software projects are quicker to update earlier rapid-release libraries compared to library projects with a longer release cycle. Moreover, results suggest that software projects are more likely to adopt the latest version of a rapid-release library compared to libraries with a longer release cycles.},
	keywords = {adoption, apache, apache software foundation, libraries},
	doi = {10.1007/978-3-319-57735-7_13},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_13},
	author = {Ihara, Akinori and Daiki Fujibayashi and Hirohiko Suwa and Raula Gaikovina Kula and Kenichi Matsumoto}
}
@proceedings {1918,
	title = {Using Gamification to Orient and Motivate Students to Contribute to OSS Projects},
	year = {2017},
	month = {05/2017},
	pages = {36-42},
	abstract = {Students can benefit from contributing to Open Source Software (OSS), since they can enrich their portfolio and learn with real world projects. However, sometimes students are demotivated to contribute due to entrance barriers. On the other hand, gamification is widely used to engage and motivate people to accomplish tasks and improve their performance. The goal of this work is to analyze the use of gamification to orient and motivate undergraduate students to overcome onboarding barriers and engage to OSS projects. To achieve this goal, we implemented four gaming elements (Quests, Points, Ranking, and Levels) in GitLab and assessed the environment by means of a study conducted with 17 students within a real OSS project (JabRed). At the end of the study, the students evaluated their experience through a questionnaire. We found that the Quest element helped to guide participants and keep them motivated and points helped by providing feedback on students{\textquoteright} performed tasks. We conclude that the gamified environment oriented the students in an attempt to make a contribution and that gamification can motivate and orient newcomers{\textquoteright} to engage to OSS projects. },
	keywords = {engagement, gamification, MOTIVATION, newcomers, students},
	author = {Guilherme C. Diniz and Marco A. Graciotto Silva and Marco Gerosa and Steinmacher, Igor}
}
@conference {Izquierdo-Cortazar:2017:UMT:3084226.3084247,
	title = {Using Metrics to Track Code Review Performance},
	booktitle = {Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering},
	series = {EASE{\textquoteright}17},
	year = {2017},
	pages = {214{\textendash}223},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {During 2015, some members of the Xen Project Advisory Board became worried about the performance of their code review process. The Xen Project is a free, open source software project developing one of the most popular virtualization platforms in the industry. They use a pre-commit peer review process similar to that in the Linux kernel, based on email messages. They had observed a large increase over time in the number of messages related to code review, and were worried about how this could be a signal of problems with their code review process.

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

In this paper we show the results of both analyses, and propose a comprehensive methodology, fully automated, to study Linux-style code review. We discuss also the problems of getting significant metrics to track improvements or detect problems in this kind of code review.},
	keywords = {code review, data mining, Software development analytics},
	isbn = {978-1-4503-4804-1},
	doi = {10.1145/3084226.3084247},
	url = {http://doi.acm.org/10.1145/3084226.3084247},
	author = {Izquierdo-Cortazar, Daniel and Sekitoleko, Nelson and Jesus M. Gonzalez-Barahona and Kurth, Lars}
}
@proceedings {1921,
	title = {Who Added that Permission to My App? An Analysis of Developer Permission Changes in Open Source Android Apps},
	year = {2017},
	note = {"Our first step was to collect open source Android repositories
from F-Droid ... We collected the git repositories for each
app, ... we recorded
all permissions, including those which were custom. 
At the time of our analysis, F-Droid contained information
for 2,372 open source Android apps. ... This process
identified 1,402 apps that had a AndroidManifest.xml file
with a history of commits... we created a tool
known as Open Source Android Repository Analyzer (oSARA)...we extracted version control
commit information ... extracts all committed AndroidManifest.xml
files from the version control history ...the committed
version of the AndroidManifest.xml file was also extracted
from the repositories, and all metadata was stored in a SQLite
database"},
	month = {05/2017},
	pages = {165-169},
	abstract = {Android applications rely on a permission-based
model to carry out core functionality. Appropriate permission
usage is imperative for ensuring device security and protecting
the user{\textquoteright}s desired privacy levels. But who is making the important
decisions of which permissions the app should request? Are they
experienced developers with the appropriate project knowledge to
make such important decisions, or are these crucial choices being
made by those with relatively minor amounts of contributions to
the project? When are these permission-related decisions being
made in the app{\textquoteright}s development life cycle? We examined 1,402
Android version control repositories containing over 331,318
commits including 18,751 AndroidManifest.xml versions to better
understand when, why, and who is adding permissions to apps.
We found that (I) developers with more experience are more
likely to make permission-based changes (II) permissions are
typically added earlier in apps{\textquoteright} commit lifetime, but their
removal is more sustained throughout the commit lifetime (III)
developers reverting permission-based changes are typically more
experienced than developers who initially made the change being
reverted.},
	keywords = {android, mobile},
	author = {Krutz, Daniel E. and Nuthan Munaiah and Anthony Peruma and Mohamed Wiem Mkaouer}
}
@proceedings {1819,
	title = {Analyzing the Decision Criteria of Software Developers Based on Prospect Theory},
	year = {2016},
	note = {they sent a survey to developers and used flossmole to harvest the email addresses},
	month = {03/2016},
	abstract = {To enhance the quality of software, many software development support tools and software development methodologies have been proposed. However, not all proposed tools and methodologies are widely used in software development. We assume that the evaluation of tools and methodologies by developers is different from the evaluation by researchers, and that this is one of the reasons why the tools and methodologies are not widely used. We analyzed the decision criteria of software developers as applied to the tools and methodologies, to clarify whether the difference exists or not. In behavioral economics, there are theories which assume people have biases, and they do not always act reasonably. In the experiment, we made a questionnaire based on behavioral economics, and collected answers from open source software developers. The results suggest that developers do not always act to maximize expected profit because of the certainty effect and ambiguity aversion. Therefore, we should reconsider the evaluation criteria of tools such as the f-measure or AUC, which mainly focus on the expected profit. },
	keywords = {flossmole},
	url = {http://se-naist.jp/pman3/pman3.cgi?DOWNLOAD=579},
	attachments = {https://flosshub.org/sites/flosshub.org/files/saner2016-kina.pdf},
	author = {Kanako Kina and Tsunoda, Masateru and Tamada, Haruaki and Hiroshi Igaki}
}
@inbook {Bibi2016,
	title = {A Bayesian Belief Network for Modeling Open Source Software Maintenance Productivity},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {32{\textendash}44},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {A Bayesian Belief Network for Modeling Open Source Software Maintenance Productivity},
	address = {Cham},
	abstract = {Maintenance is one of the most effort consuming activities in the software development lifecycle. Efficient maintenance within short release cycles depends highly on the underlying source code structure, in the sense that complex modules are more difficult to maintain. In this paper we attempt to unveil and discuss relationships between maintenance productivity, the structural quality of the source code and process metrics like the type of a release and the number of downloads. To achieve this goal, we developed a Bayesian Belief Network (BBN) involving several maintainability predictors and three managerial indices for maintenance (i.e., duration, production, and productivity) on 20 open source software projects. The results suggest that maintenance duration depends on inheritance, coupling, and process metrics. On the other hand maintenance production and productivity depend mostly on code quality metrics.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_3},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_3},
	author = {Bibi, Stamatia and Apostolos Ampatzoglou and Ioannis Stamelos},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Rodr{\'\i}guez-P{\'e}rez2016,
	title = {BugTracking: A Tool to Assist in the Identification of Bug Reports},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {192{\textendash}198},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {BugTracking: A Tool to Assist in the Identification of Bug Reports},
	address = {Cham},
	abstract = {Issue tracking systems are used, in most software projects, but in particular in almost all free open source software, to record many different kinds of issues: bug reports, feature requests, maintenance tickets and even design discussions. Identifying which of those issues are bug reports is not a trivial task. When researchers want to conduct studies on the bug reports, managed by a software development project, first of all they need to perform this identification.
The job for researchers here is very different from the bug triaging that researchers do. In the latter case, people with a considerate experience in the project make a decision based on the information available at that time (maybe just a short comment by some user), asking, if needed, for more details. In the former case, researchers usually have not that experience in the project, but they have at their use all the information produced, until the moment the issue was closed. This may include not only all comments and actions on the issue tracking system, but for example, discussions about a fix in the code review system, or the final fixing patch in the source code management system. Having all that information conveyed to the researchers, in an easy, flexible and quick way, accelerates and makes their decision process much more reliable. It simplifies large scale manual analysis of issues (in hundreds or thousands), helping researchers to ensure that they are really working with what they intend to work: bug reports.
This paper presents a tool designed to solve exactly the problem of providing the researchers with all the relevant information needed to decide whether an issue corresponds to a bug report or not. The tool uses information extracted automatically from the projects repositories. It offers a web-based interface which allows collaboration, traceability and transparency of the identification of bug reports. All this makes the process easier, faster, and more reliable.},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_16},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_16},
	author = {Rodr{\'\i}guez-P{\'e}rez, Gema and Gonzalez-Barahona, Jes{\'u}s M. and Gregorio Robles and Dalipaj, Dorealda and Sekitoleko, Nelson},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Kalliamvakou2016,
	title = {Certification of Open Source Software {\textendash} A Scoping Review},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {111{\textendash}122},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Certification of Open Source Software {\textendash} A Scoping Review},
	address = {Cham},
	abstract = {Open source software (OSS) systems are being used for increasingly critical functions in modern societies, e.g., in health care, finance, government, defense, and other safety and security sensitive sectors. There is an increasing interest in software certification as a means to assure quality and dependability of such systems. However, the development processes and organizational structures of OSS projects can be substantially different from traditional closed-source projects. The distributed, {\textquotedblleft}bazaar-style{\textquotedblright} approach to software development in OSS systems is often perceived incompatible with certification. This paper presents the results of a scoping review on certification in OSS systems in order to identify and categorize key issues and provide a comprehensive overview of the current evidence on this topic.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_9},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_9},
	author = {Kalliamvakou, Eirini and Weber, Jens and Knauss, Alessia},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Murphy2016,
	title = {Classifying Organizational Adoption of Open Source Software: A Proposal},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {123{\textendash}133},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Classifying Organizational Adoption of Open Source Software: A Proposal},
	address = {Cham},
	abstract = {Staged adoption models are a common feature of information systems (IS) adoption literature, yet these are rarely used in open source software (OSS) adoption studies. In this paper, a staged model for classifying the organizational adoption of OSS is proposed, based upon a critical review of existing staged adoption models and factors identified from OSS adoption literature. Innovations in the proposed model include: defined transition pathways between stages, additional stages and a decomposition of cessation of use into four distinct pathways.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_10},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_10},
	author = {Murphy, Stephen and Cox, Sharon},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Harzl2016,
	title = {Combining FOSS and Kanban: An Action Research},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {71{\textendash}84},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Combining FOSS and Kanban: An Action Research},
	address = {Cham},
	abstract = {Even though Free and Open Source Software (FOSS) and Agile Software Development (ASD) have been recognized as important ways to develop software, share some similarities, and have many success stories, there is a lack of research regarding the comprehensive integration of both practices. This study attempts to consolidate these methods and to answer if FOSS and ASD can be combined successfully. Action Reseach (AR) is conducted with one sub-team of a large FOSS project. We performed two action research cycles based on the Kanban method. This paper has two main contributions; first, it describes a real world situation, where Kanban is applied to a FOSS project, and second, it suggests two new Kanban practices. These two methods are targeted specifically at FOSS projects and their characteristics.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_6},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_6},
	author = {Harzl, Annemarie},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Crowston2016,
	title = {Core-Periphery Communication and the Success of Free/Libre Open Source Software Projects},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {45{\textendash}56},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {We examine the relationship between communications by core and peripheral members and Free/Libre Open Source Software project success. The study uses data from 74 projects in the Apache Software Foundation Incubator. We conceptualize project success in terms of success building a community, as assessed by graduation from the Incubator. We compare successful and unsuccessful projects on volume of communication by core (committer) and peripheral community members and on use of inclusive pronouns as an indication of efforts to create intimacy among team members. An innovation of the paper is that use of inclusive pronouns is measured using natural language processing techniques. We find that core and peripheral members differ in their volume of contribution and in their use of inclusive pronouns, and that volume of communication is related to project success.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_4},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_4},
	author = {Kevin Crowston and Shamshurin, Ivan},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@proceedings {1824,
	title = {Data Sets: The Circle of Life in Ruby Hosting, 2003-2015},
	year = {2016},
	month = {05/2016},
	pages = {452-455},
	publisher = {IEEE},
	abstract = {Studying software repositories and hosting services can provide valuable insights into the behaviors of large groups of software developers and their projects. Traditionally, most analysis of metadata collected from hosting services has been conducted by specifying some short window of time, typically just a few years. To date, few - if any - studies have been built from data comprising the entirety of a repository{\textquoteright}s lifespan: from its birth to its death, and rebirth. Thus, the first contribution of this data set is to support the historical analysis of over ten years of collected metadata from the now-defunct RubyForge project hosting site, as well as the follow-on successor to RubyForge, the RubyGems hosting facility. The data sets and sample analyses in this paper will be relevant to researchers studying both software evolution and the distributed software development process.},
	url = {https://docs.google.com/presentation/d/1rtdrwkfxt-p5gQBwMNT1WDlLMg0pJ4gxfM5jSAH-UUA/edit?usp=sharing},
	attachments = {https://flosshub.org/sites/flosshub.org/files/preprint.pdf},
	author = {Squire, Megan}
}
@article {1861,
	title = {The Debsources Dataset: two decades of free and open source software},
	journal = {Empirical Software Engineering},
	year = {2016},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {We present the Debsources Dataset: distribution metadata and source code metrics spanning two decades of Free and Open Source Software (FOSS) history, seen through the lens of the Debian distribution. Debsources is a software platform used to gather, search, and publish on the Web the full source code of the Debian operating system, as well as measures about it. A notable public instance of Debsources is available at http://sources.debian.net, it includes both current and historical releases of Debian. Plugins to compute popular source code metrics (lines of code, defined symbols, disk usage) and other derived data (e.g., Checksums) have been written, integrated, and run on all the source code available on sources.debian.net. The Debsources Dataset is a PostgreSQL database dump of sources.debian.net metadata, as of February 10th, 2015. The dataset contains both Debian-specific metadata -- e.g., which software packages are available in which release, which source code file belong to which package, release dates, etc. -- and source code information gathered by running Debsources plugins. The Debsources Dataset offer a very long-term historical view of the macro-level evolution and constitution of FOSS through the lens of popular, representative FOSS projects of their times.},
	keywords = {debian, metadata, postgresql},
	issn = {1573-7616},
	doi = {10.1007/s10664-016-9461-5},
	url = {https://matthieu.io/dl/papers/debsources-ese-2016.pdf},
	author = {Caneill, Matthieu and Daniel M. Germ{\'a}n and Zacchiroli, Stefano}
}
@proceedings {1854,
	title = {Differentiating Communication Styles of Leaders on the Linux Kernel Mailing List},
	year = {2016},
	note = {Slides link: https://docs.google.com/presentation/d/1_5kqOXBYwH33ayfGKCncCtCondfUYtsHSDBS3DBig6Y/edit?usp=sharing
Edited to fix typo in abstract. New version is v3.pdf},
	month = {08/2016},
	publisher = {ACM},
	abstract = {Much communication between developers of free, libre, and open source software (FLOSS) projects happens on email mailing lists. Geographically and temporally dispersed development teams use email as an asynchronous, centralized, persistently stored institutional memory for sharing code samples, discussing bugs, and making decisions. Email is especially important to large, mature projects, such as the Linux kernel, which has thousands of developers and a multi-layered leadership structure. In this paper, we collect and analyze data to understand the communication patterns in such a community. How do the leaders of the Linux Kernel project write in email? What are the salient features of their writing, and can we discern one leader from another? We find that there are clear written markers for two leaders who have been particularly important to recent discussions of leadership style on the Linux Kernel Mailing List (LKML): Linux Torvalds and Greg Kroah-Hartman. Furthermore, we show that it is straightforward to use a machine learning strategy to automatically differentiate these two leaders based on their writing. Our findings will help researchers understand how this community works, and why there is occasional controversy regarding differences in communication styles on the LKML.},
	keywords = {email, flossmole, linus torvalds, linux, lkml},
	attachments = {https://flosshub.org/sites/flosshub.org/files/v3_0.pdf},
	author = {Schneider, Daniel and Spurlock, Scott and Squire, Megan}
}
@proceedings {1866,
	title = {Does the Task Structure of Open Source Projects Matter? Superposition and Value Creation},
	year = {2016},
	month = {11/2016},
	publisher = {AIS},
	abstract = {Collaboration through open superposition describes a process of building free (libre) and open source software (FLOSS), wherein motivationally independent layers of work is sequentially added one-on-top the other over time. This research-in-progress paper theorizes the mechanisms through which superposition influences the value of individual and organizational owned FLOSS projects. We argue for a non-linear relationship between degree of superposition and value of the FLOSS project. Moreover, we posit that the type of ownership will moderate this non-linear relationship. The moderation effect is such that {\textendash} (1) organizational ownership mitigates the influence of degree of superposition on project value (2) under organizational ownership, the optimal value of degree of superposition (the point at which the project value is maximum) is lower as compared to individual owned projects. This research attempts to advance the theory of superposition and unearth the influence of task structure on the value of the FLOSS project.},
	author = {Poonacha K. Medappa and Shirish C. Srivastava}
}
@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}
}
@article {1849,
	title = {Folding and unfolding : balancing openness and transparency in open source communities},
	journal = { Information Systems Research},
	year = {2016},
	publisher = {Institute for Operations Research and the Management Sciences},
	abstract = {Open source communities rely on the espoused premise of complete openness and transparency of source code and development process. Yet, openness and transparency at times need to be balanced out with moments of less open and transparent work. Through our detailed study of Linux Kernel development we build a theory that explains that transparency and openness are nuanced and changing qualities that certain developers manage as they use multiple digital technologies and create, in moments of needs, more opaque and closed digital spaces of work. We refer to these spaces as digital folds. Our paper contributes to extant literature: by providing a process theory of how transparency and openness are balanced with opacity and closure in open source communities according to the needs of the development work; by conceptualizing the nature of digital folds and their role in providing quiet spaces of work: and, by articulating how the process of digital folding and unfolding is made far more possible by select elite actors{\textquoteright} navigating the line between the pragmatics of coding and the accepted ideology of openness and transparency.

},
	url = {http://wrap.warwick.ac.uk/78627/},
	author = {Maha Shaikh and Vaast, Emmanuelle}
}
@inbook {Poo-Caama{\~n}o2016,
	title = {Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {147{\textendash}162},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem},
	address = {Cham},
	abstract = {Release management in large-scale software development projects requires significant communication and coordination. It is particularly challenging in Free and Open Source Software (FOSS) ecosystems, in which hundreds of loosely connected developers and their projects need to be coordinated to release software to a schedule. To better understand this process and its challenges, we analyzed over two and half years of communication in the GNOME ecosystem and studied developers{\textquoteright} interactions. We cataloged communication channels, categorized high level communication and coordination activities in one of them, and triangulated our results by interviewing developers. We found that a release schedule, influence instead of direct control, and diversity are factors that impact positively the release process in the GNOME ecosystem. Our results can help organizations build better large-scale teams and show that research focused on individual projects might miss important parts of the picture.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_12},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_12},
	author = {Poo-Caama{\~n}o, Germ{\'a}n and Singer, Leif and Knauss, Eric and Daniel M. German},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@proceedings {1808,
	title = {How Do Free/Open Source Developers Pick Their Tools? A Delphi Study of the Debian Project},
	year = {2016},
	abstract = {Free and Open Source Software (FOSS) has come to play a critical role in the global software industry. Organizations are widely adopting FOSS and interacting with open source communities, and hence organizations have a considerable interest in seeing these communities flourishing. Very little research has focused on the tools used to develop that software. Given the absence of organizational policies and mandate that would occur in a traditional environment, an open question is how FOSS developers decide what tools to use. In this paper we report on a policy delphi study conducted in the Debian Project, one of the largest FOSS projects. Drawing from data collected in three phases from a panel of 21 experts, we identified 15 factors that affect their decision to adopt tools. This in turn can help FOSS communities to define a suitable policy of actions, in order to improve their processes.},
	keywords = {Delphi, Free/Open Source Software, Qualitative Study, study, tools},
	url = {https://www.researchgate.net/publication/291312269_How_Do_FreeOpen_Source_Developers_Pick_Their_Tools_A_Delphi_Study_of_the_Debian_Project},
	author = {Martin Krafft and Stol, Klaas-Jan and Fitzgerald, Brian}
}
@proceedings {1826,
	title = {How Software Developers Use Work Breakdown Relationships in Issue Repositories},
	year = {2016},
	month = {05/2016},
	pages = {281-285},
	abstract = {Software developers use issues as a means to describe a range
of activities to be undertaken on a software system, including
features to be added and defects that require fixing. When
creating issues, software developers expend manual effort
to specify relationships between issues, such as one issue
blocking another or one issue being a sub-task of another.
In particular, developers use a variety of relationships to express
how work is to be broken down on a project. To better
understand how software developers use work breakdown relationships
between issues, we manually coded a sample of
work breakdown relationships from three open source systems.
We report on our findings and describe how the recognition
of work breakdown relationships opens up new ways
to improve software development techniques.},
	doi = {http://dx.doi.org/10.1145/2901739.2901779},
	author = {C. Albert Thompson and Murphy, Gail C. and Palyart, Marc and Marko Ga{\v s}paric}
}
@inbook {Hirao2016,
	title = {The Impact of a Low Level of Agreement Among Reviewers in a Code Review Process},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {97{\textendash}110},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Software code review systems are commonly used in software development. In these systems, many patches are submitted to improve the quality. To verify the quality, voting is commonly used by contributors; however, there still exists a major problem, namely, that reviewers do not always simply reach a broad agreement. In our previous study, we found that consensus is not usually reached, implying that an individual reviewer{\textquoteright}s final decision usually differs from that of the majority of the other reviewers. In this study, we further investigate the reasons why such situations often occur, and provide suggestions for better handling of these problems. Our analysis of the Qt and OpenStack project datasets allow us to suggest that a patch owner should select more appropriate reviewers who often agree with others{\textquoteright} decisions.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_8},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_8},
	author = {Hirao, Toshiki and Ihara, Akinori and Ueda, Yuki and Phannachitta, Passakorn and Matsumoto, Ken-ichi},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {M{\"a}enp{\"a}{\"a}2016,
	title = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {134{\textendash}146},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities},
	address = {Cham},
	abstract = {Today, the community driven development model extends into a variety of new, often web based collaborations. Among these are hybrid open source development set ups in which various online tools are used to facilitate cooperation between virtual teams of commercial and voluntary stakeholders. As yet, how these relationships form and evolve is not understood extensively. This article presents a longitudinal case study of a smartphone startup that founded its early product development strategy on reliance on feedback from its customers through a web based question and answer forum. With this, the company managed to extend values typical for open source communities to support development of its proprietary software. Our main findings include that the challenge in similar settings lies in striking the right balance between the open and the proprietary {\textendash} while overt openness may risk the competitive advantage of a company, leaving too much behind closed boundaries can create unnecessary friction in the relationship.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_11},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_11},
	author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and M{\"a}nnist{\"o}, Tomi},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Gamalielsson2016,
	title = {On Involvement in Open Standards: How Do Organisations Contribute to W3C Standards Through Editorship?},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {57{\textendash}70},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {On Involvement in Open Standards: How Do Organisations Contribute to W3C Standards Through Editorship?},
	address = {Cham},
	abstract = {Over the years, a number of open standards have been developed and implemented in software for addressing a number of challenges, such as lock-in, interoperability and longevity of software systems and associated digital artefacts. Understanding organisational involvement and collaboration in standardisation is important for informing any future policy and organisational decisions concerning involvement in standardisation. The overarching goal of the study is to establish how organisations contribute to open standards development through editorship. Specifically, the focus is on open standards development in W3C. Through an analysis of editorship for all W3C recommendations we contribute novel findings concerning organisational involvement and collaboration, and highlight contributions from different types of organisations and countries for headquarter of each organisation. We make three principal contributions. First, we establish an overall characterisation of organisational involvement in W3C standardisation. Second, we report on organisational involvement in W3C standardisation over time. Third, we establish organisational collaboration in W3C standardisation through social network analysis.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_5},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_5},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@proceedings {1827,
	title = {A Large-Scale Study on Repetitiveness, Containment, and Composability of Routines in Open-Source Projects},
	year = {2016},
	month = {05/2016},
	pages = {362-373},
	abstract = {Source code in software systems has been shown to have a good
degree of repetitiveness at the lexical, syntactical, and API usage
levels. This paper presents a large-scale study on the repetitiveness,
containment, and composability of source code at the semantic level.
We collected a large dataset consisting of 9,224 Java projects with
2.79M class files, 17.54M methods with 187M SLOCs. For each
method in a project, we build the program dependency graph (PDG)
to represent a routine, and compare PDGs with one another as well
as the subgraphs within them. We found that within a project, 12.1\%
of the routines are repeated, and most of them repeat from 2{\textendash}7 times.
As entirety, the routines are quite project-specific with only 3.3\% of
them exactly repeating in 1{\textendash}4 other projects with at most 8 times.
We also found that 26.1\% and 7.27\% of the routines are contained
in other routine(s), i.e., implemented as part of other routine(s) elsewhere
within a project and in other projects, respectively. Except for
trivial routines, their repetitiveness and containment is independent
of their complexity. Defining a subroutine via a per-variable slicing
subgraph in a PDG, we found that 14.3\% of all routines have all
of their subroutines repeated. A high percentage of subroutines in
a routine can be found/reused elsewhere. We collected 8,764,971
unique subroutines (with 323,564 unique JDK subroutines) as basic
units for code searching/synthesis. We also provide practical
implications of our findings to automated tools.},
	doi = {http://dx.doi.org/10.1145/2901739.2901759},
	author = {Nguyen, Anh Duc and Nguyen, Hoan Anh and Nguyen, Tien N.}
}
@article {966,
	title = {License Compliance in Open Source Cybersecurity Projects},
	journal = {Technology Innovation Management Review},
	volume = {6},
	year = {2016},
	month = {02/2016},
	pages = {28-35},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {Developers of cybersecurity software often include and rely upon open source software packages in their commercial software products. Before open source code is absorbed into a proprietary product, developers must check the package license to see if the project is permissively licensed, thereby allowing for commercial-friendly inheritance and redistribution. However, there is a risk that the open source package license could be inaccurate due to being silently contaminated with restrictively licensed open source code that may prohibit the sale or confidentiality of commercial derivative work. Contamination of commercial products could lead to expensive remediation costs, damage to the company{\textquoteright}s reputation, and costly legal fees. In this article, we report on our preliminary analysis of more than 200 open source cybersecurity projects to identify the most frequently used license types and languages and to look for evidence of permissively licensed open source projects that are likely contaminated by restrictive licensed material (i.e., containing commercial-unfriendly code). Our analysis identified restrictive license contamination cases occurring in permissively licensed open source projects. Furthermore, we found a high proportion of code that lacked copyright attribution. We expect that the results of this study will: i) provide managers and developers with an understanding of how contamination can occur, ii) provide open source communities with an understanding on how they can better protect their intellectual property by including licenses and copyright information in their code, and ii) provide entrepreneurs with an understanding of the open source cybersecurity domain in terms of licensing and contamination and how they affect decisions about cybersecurity software architectures.},
	issn = {1927-0321},
	author = {Ahmed Shah and Selman Selman and Ibrahim Abualhaol}
}
@article {1847,
	title = {License usage and changes: a large-scale study on gitHub},
	journal = {Empirical Software Engineering},
	year = {2016},
	abstract = {Open source software licenses determine, from a legal point of view, under which conditions software can be integrated and redistributed. The reason why developers of a project adopt (or change) a license may depend on various factors, e.g., the need for ensuring compatibility with certain third-party components, the perspective towards redistribution or commercialization of the software, or the need for protecting against somebody else{\textquoteright}s commercial usage of the software. This paper reports a large empirical study aimed at quantitatively and qualitatively investigating when and why developers adopt or change software licenses. Specifically, we first identify license changes in 1,731,828 commits, representing the entire history of 16,221 Java projects hosted on GitHub. Then, to understand the rationale of license changes, we perform a qualitative analysis on 1,160 projects written in seven different programming languages, namely C, C++, C$\#$, Java, Javascript, Python, and Ruby{\textemdash}following an open coding approach inspired by grounded theory{\textemdash}on commit messages and issue tracker discussions concerning licensing topics, and whenever possible, try to build traceability links between discussions and changes. On one hand, our results highlight how, in different contexts, license adoption or changes can be triggered by various reasons. On the other hand, the results also highlight a lack of traceability of when and why licensing changes are made. This can be a major concern, because a change in the license of a system can negatively impact those that reuse it. In conclusion, results of the study trigger the need for better tool support in guiding developers in choosing/changing licenses and in keeping track of the rationale of license changes.},
	issn = {1573-7616},
	doi = {10.1007/s10664-016-9438-4},
	author = {Vendome, Christopher and Bavota, Gabriele and Di Penta, Massimiliano and Linares-V{\'a}squez, Mario and German, Daniel and Poshyvanyk, Denys}
}
@article {Kazuhiro Yamashita2016,
	title = {Magnet or Sticky? Measuring Project Characteristics from the Perspective of Developer Attraction and Retention},
	journal = {Journal of Information Processing},
	volume = {24},
	number = {2},
	year = {2016},
	pages = {339-348},
	abstract = {Open Source Software (OSS) is vital to both end users and enterprises. As OSS systems are becoming a type of infrastructure, long-term OSS projects are desired. For the survival of OSS projects, the projects need to not only retain existing developers, but also attract new developers to grow. To better understand how projects retain and attract contributors, our preliminary study aimed to measure the personnel attraction and retention of OSS projects using a pair of population migration metrics, called Magnet (personnel attraction) and Sticky (retention) metrics. Because the preliminary study analyzed only 90 projects and the 90 projects are not representative of GitHub, this paper extend the preliminary study to better understand the generalizability of the results by analyzing 16, 552 projects of GitHub. Furthermore, we also add a pilot study to investigate the typical duration between releases to find more appropriate release duration. The study results show that (1) approximately 23\% of developers remain in the same projects that the developers contribute to, (2) the larger projects are likely to attract and retain more developers, (3) 53\% of terminal projects eventually decay to a state of fewer than ten developers and (4) 55\% of attractive projects remain in an attractive category.
},
	keywords = {github, retention},
	doi = {10.2197/ipsjjip.24.339},
	url = {https://www.jstage.jst.go.jp/article/ipsjjip/24/2/24_339/_article},
	author = {Yamashita, Kazuhiro and Kamei, Yasutaka and McIntosh, Shane and Hassan, Ahmed E. and Ubayashi, Naoyasu}
}
@proceedings {1927,
	title = {Managing Hidden Dependencies in OO Software: a Study Based on Open Source Projects},
	year = {2016},
	month = {11/2016},
	abstract = {Dependency-based software change impact analysis is the domain concerned with estimating sets of artifacts impacted by a change to a related artifact. Research has shown that analysing the various class dependency types independently will not reveal a complete estimate of impact sets. Therefore, dependency types are combined to improve the precision of estimated when compared to impact sets. Software classes can be linked in different ways; for instance semantically, if their meaning is somewhat related or, structurally, if one class depends on the services of other classes. {\textquoteright}Hidden{\textquoteright} dependencies arise when two classes, linked structurally, do not share the same semantic namespace or when semantically dependent classes do not share a structural link. With the goal of revealing hidden dependencies during change impact analysis, we empirically investigated the interplay between structural and semantic class dependencies in object-oriented software systems. Results show that (i) semantic and structural links are significantly associated, (ii) the strengths of those links does not play a significant role and, (iii) a significant number of dependencies are hidden. We propose refactoring techniques to deal with hidden dependencies, based on existing design patterns. Our approach has the potential for reducing refactoring and testing effort.},
	author = {Nemitari Ajienka and Capiluppi, Andrea and Counsell, Steve}
}
@inbook {Berger2016,
	title = {An Open Continuous Deployment Infrastructure for a Self-driving Vehicle Ecosystem},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {177{\textendash}183},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {An Open Continuous Deployment Infrastructure for a Self-driving Vehicle Ecosystem},
	address = {Cham},
	abstract = {Self-driving vehicles are an ongoing research and engineering topic even though first automotive OEMs started to deploy such features to their premium vehicles. Chalmers University of Technology and University of Gothenburg are operating and maintaining a vehicle laboratory comprising 1/10 scaled cars, a Volvo XC90, and a Volvo FH truck to conduct studies with automated driving. This laboratory is used both from researchers from different disciplines and in education. The experimental software for all these platforms is powered by the same software environment for different hardware architectures. Therefore, maintaining and deploying new features and bugfixes to the users of this laboratory in a fast way needs to be organized in a reproducible yet easily maintainable manner. This paper outlines our open approach to encapsulate our build, test, and deployment process using VirtualBox, Docker, and Jenkins.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_14},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_14},
	author = {Berger, Christian},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@mastersthesis {1855,
	title = {Open Source Software Ecosystem: A Systematic Literature Review},
	year = {2016},
	month = {05/2016},
	type = {Masters Thesis},
	address = {University of Oulu},
	abstract = {Background: Currently having a software ecosystem is vital for many technology businesses. For this reason, understanding of software ecosystem and its benefits and also the elements of each software ecosystem can help business and software communities to emerge and orchestrate the products ecosystem optimally. Moreover, an interesting phenomenon in computer science and information technology is open source software and systems which enable users to participate in developing and using the software at many scales, from a simple mobile application to large-scale business systems and ICT applications.},
	doi = {10.13140/RG.2.1.2254.1049},
	url = {https://www.researchgate.net/publication/305994372_Open_Source_Software_Ecosystem_A_Systematic_Literature_Review},
	author = {Javad Nasserifar}
}
@inbook {L{\'o}pez2016,
	title = {OSSAP {\textendash} A Situational Method for Defining Open Source Software Adoption Processes},
	booktitle = {Advanced Information Systems Engineering: 28th International Conference, CAiSE 2016, Ljubljana, Slovenia, June 13-17, 2016. Proceedings},
	year = {2016},
	pages = {524{\textendash}539},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Organizations are increasingly becoming Open Source Software (OSS) adopters, either as a result of a strategic decision or just as a consequence of technological choices. The strategy followed to adopt OSS shapes organizations{\textquoteright} businesses; therefore methods to assess such impact are needed. In this paper, we propose OSSAP, a method for defining OSS Adoption business Processes, built using a Situational Method Engineering (SME) approach. We use SME to combine two well-known modelling methods, namely goal-oriented models (using i*) and business process models (using BPMN), with a pre-existing catalogue of goal-oriented OSS adoption strategy models. First, we define a repository of reusable method chunks, including the guidelines to apply them. Then, we define OSSAP as a composition of those method chunks to help organizations to improve their business processes in order to integrate the best fitting OSS adoption strategy. We illustrate it with an example of application in a telecommunications company.
},
	isbn = {978-3-319-39696-5},
	doi = {10.1007/978-3-319-39696-5_32},
	url = {http://dx.doi.org/10.1007/978-3-319-39696-5_32},
	author = {L{\'o}pez, Lidia and Costal, Dolors and Ralyt{\'e}, Jolita and Franch, Xavier and M{\'e}ndez, Luc{\'\i}a and Annosi, Maria Carmela},
	editor = {Nurcan, Selmin and Soffer, Pnina and Bajec, Marko and Eder, Johann}
}
@article {Krishnamurthy:2016:PDP:2869770.2820618,
	title = {Peripheral Developer Participation in Open Source Projects: An Empirical Analysis},
	journal = {ACM Trans. Manage. Inf. Syst.},
	volume = {6},
	number = {4},
	year = {2016},
	pages = {14:1{\textendash}14:31},
	publisher = {ACM},
	address = {New York, NY, USA},
	abstract = {The success of the Open Source model of software development depends on the voluntary participation of external developers (the peripheral developers), a group that can have distinct motivations from that of project founders (the core developers). In this study, we examine peripheral developer participation by empirically examining approximately 2,600 open source projects. In particular, we hypothesize that peripheral developer participation is higher when the potential for building reputation by gaining recognition from project stakeholders is higher. We consider recognition by internal stakeholders (such as core developers) and external stakeholders (such as end-users and peers). We find a positive association between peripheral developer participation and the potential of stakeholder recognition after controlling for bug reports, feature requests, and other key factors. Our findings provide important insights for OSS founders and corporate managers for open sourcing or OSS adoption decisions.
},
	keywords = {Code ownership, open source software, project management, software metrics},
	issn = {2158-656X},
	doi = {10.1145/2820618},
	url = {http://doi.acm.org/10.1145/2820618},
	author = {Krishnamurthy, Rajiv and Jacob, Varghese and Radhakrishnan, Suresh and Kutsal Dogan}
}
@conference {1858,
	title = {The quest for open source projects that use UML},
	booktitle = {Proceedings of the ACM/IEEE 19th International Conference on Model Driven Engineering Languages and Systems - MODELS {\textquoteright}16},
	year = {2016},
	pages = {173 - 183},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Context: While industrial use of UML was studied intensely,little is known about UML use in Free/Open Source Soft-ware (FOSS) projects. Goal: We aim at systematically mining GitHub projects to answer the question when mod-els, if used, are created and updated throughout the whole project{\textquoteright}s life-span. Method: We present a semi-automated approach to collect UML stored in images, .xmi, and .uml files and scanned ten percent of all GitHub projects (1.24million). Our focus was on number and role of contributors that created/updated models and the time span during which this happened. Results: We identified and studied 21 316 UML diagrams within 3 295 projects. Conclusion: Creating/updating of UML happens most often during a very short phase at the project start. For 12\% of the models duplicates were found, which are in average spread across 1.88 projects. Finally, we contribute a list of GitHub projects that include UML files.},
	isbn = {9781450343213},
	doi = {10.1145/2976767.2976778},
	url = {https://www.researchgate.net/publication/308869547_The_quest_for_open_source_projects_that_use_UML_mining_GitHub},
	author = {fernandez, miguel angel and Hebig, Regina and Quang, Truong Ho and Chaudron, Michel R. V.}
}
@inbook {Abdulwahhab2016,
	title = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {3{\textendash}15},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	address = {Cham},
	abstract = {This paper investigates the position of local open source communities (LOSCs) in the development of open source projects (OSPs). We have conducted an empirical study to examine the role of LOSCs, their way of working, and the benefits/challenges they experience compared to the overall global community. The qualitative investigation consisted of ten semi-structured interviews with members within different LOSCs. The results confirm the importance of LOSCs and the pivotal role they play in the development of OSPs. In many cases, they act as the middleman between individual members and the project{\textquoteright}s global community. However, LOSCs have their own kinds of challenges.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_1},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_1},
	author = {Abdulwahhab, Sinan and Alabady, Yazen and Sattar, Yacoub and Hammouda, Imed},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@article {1864,
	title = {Roles and politeness behavior in community-based free/libre open source software development},
	journal = {Information \& Management},
	year = {2016},
	month = {11/2016},
	abstract = {Community-based Free/Libre Open Source Software (FLOSS) development relies on contributions from both core and peripheral members. Prior research on core{\textendash}periphery has focused on software coding-related behaviors. We study how core{\textendash}periphery roles are related to social-relational behavior in terms of politeness behavior. Data from two FLOSS projects suggest that both core and peripheral members use more positive politeness strategies than negative strategies. Further, core and peripheral members use different strategies to protect positive face in positive politeness, which we term respect and intimacy, respectively. Our results contribute to FLOSS research and politeness theory.

},
	keywords = {Core{\textendash}periphery structure, open source software development, Politeness behavior},
	issn = {03787206},
	doi = {10.1016/j.im.2016.11.006},
	url = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Group_maintenance\%20paper\%20to\%20share.pdf},
	author = {Kangning Wei and Kevin Crowston and Eseryel, U.Yeliz and Robert Heckman}
}
@conference {Vasilescu:2016:SLM:2884781.2884875,
	title = {The Sky is Not the Limit: Multitasking Across GitHub Projects},
	booktitle = {Proceedings of the 38th International Conference on Software Engineering (ICSE 2016)},
	series = {ICSE {\textquoteright}16},
	year = {2016},
	pages = {994{\textendash}1005},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software development has always inherently required multitasking: developers switch between coding, reviewing, testing, designing, and meeting with colleagues. The advent of software ecosystems like GitHub has enabled something new: the ability to easily switch between projects. Developers also have social incentives to contribute to many projects; prolific contributors gain social recognition and (eventually) economic rewards. Multitasking, however, comes at a cognitive cost: frequent context-switches can lead to distraction, sub-standard work, and even greater stress. In this paper, we gather ecosystem-level data on a group of programmers working on a large collection of projects. We develop models and methods for measuring the rate and breadth of a developers{\textquoteright} context-switching behavior, and we study how context-switching affects their productivity. We also survey developers to understand the reasons for and perceptions of multitasking. We find that the most common reason for multitasking is interrelationships and dependencies between projects. Notably, we find that the rate of switching and breadth (number of projects) of a developer{\textquoteright}s work matter. Developers who work on many projects have higher productivity if they focus on few projects per day. Developers that switch projects too much during the course of a day have lower productivity as they work on more projects overall. Despite these findings, developers perceptions of the benefits of multitasking are varied.
},
	keywords = {github, multitasking, productivity},
	isbn = {978-1-4503-3900-1},
	doi = {10.1145/2884781.2884875},
	url = {http://doi.acm.org/10.1145/2884781.2884875},
	author = {Vasilescu, Bogdan and Blincoe, Kelly and Xuan, Qi and Casalnuovo, Casey and Damian, Daniela and Devanbu, Premkumar and Filkov, Vladimir}
}
@inbook {AbbaspourAsadollah2016,
	title = {A Study of Concurrency Bugs in an Open Source Software},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {16{\textendash}31},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {A Study of Concurrency Bugs in an Open Source Software},
	address = {Cham},
	abstract = {Concurrent programming puts demands on software debugging and testing, as concurrent software may exhibit problems not present in sequential software, e.g., deadlocks and race conditions. In aiming to increase efficiency and effectiveness of debugging and bug-fixing for concurrent software, a deep understanding of concurrency bugs, their frequency and fixing-times would be helpful. Similarly, to design effective tools and techniques for testing and debugging concurrent software understanding the differences between non-concurrency and concurrency bugs in real-word software would be useful. This paper presents an empirical study focusing on understanding the differences and similarities between concurrency bugs and other bugs, as well as the differences among various concurrency bug types in terms of their severity and their fixing time. Our basis is a comprehensive analysis of bug reports covering several generations of an open source software system. The analysis involves a total of 4872 bug reports from the last decade, including 221 reports related to concurrency bugs. We found that concurrency bugs are different from other bugs in terms of their fixing time and their severity. Our findings shed light on concurrency bugs and could thereby influence future design and development of concurrent software, their debugging and testing, as well as related tools.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_2},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_2},
	author = {Abbaspour Asadollah, Sara and Sundmark, Daniel and Eldh, Sigrid and Hansson, Hans~ and Enoiu, Eduard Paul},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@article {1857,
	title = {Is there a wage premium for volunteer OSS engagement? {\textendash} signalling, learning and noise},
	journal = {Applied Economics},
	year = {2016},
	month = {09/2016},
	pages = {1 - 16},
	publisher = {Routledge},
	abstract = {Volunteer-based open-source production has become a significant new model for the organization of software development. Economics often pictures this phenomenon as a case of signaling: Individuals engage in the volunteer programming of open-source software (OSS) as a labor-market signal resulting in a wage premium. Yet, this explanation could so far not be empirically tested. The present paper fills this gap by estimating an upper-bound composite wage premium of voluntary OSS contributions and by separating the potential signaling effect of OSS engagement from other effects. Although some 70\% of OSS contributors believe that OSS involvement benefits their careers, we find no actual labor market premium for OSS engagement. The presence of other motives such as fun of play or altruism render OSS contributions too noisy to function as a signal.},
	keywords = {open source software, peer production, signalling, voluntary work, wage formation},
	issn = {1466-4283},
	doi = {10.1080/00036846.2016.1218427},
	author = {Bitzer, J{\"u}rgen and Geishecker, Ingo and Schr{\"o}der, Philipp J. H.}
}
@conference {1874,
	title = {Towards Developing a Theory of Toxicity in the Context of Free/Open Source Software \& Peer Production Communities},
	year = {2016},
	abstract = {Information technology usage has positive aspects, but it has been acknowledged that there also exist negative ones that must be studied in more depth. Behaviors such as teasing and abusing are a main concern for Free/Open Source Software (FOSS) and peer production project leaders. Indeed, they have recurrently used the words "toxic" and "poison" to qualify behaviors threatening their communities{\textquoteright} survival. Community health has been defined as the extent to which the vital systems of an online community are continuously performing normally. This definition is based on the metaphor of "online community as a living organism" , which brings the focus on the inner workings of communities and is particularly suited to study behaviors occurring within it. In this research project, we mobilize this organismic metaphor and borrow ideas from the Toxicology discipline to develop a theory of toxicity in FOSS and \& peer production communities. There has been a substantial amount of research attention on {\textquoteright}toxic{\textquoteright} and {\textquoteright}poisonous{\textquoteright} behaviors at the individual level of analysis. Nonetheless, the higher-level concern of their interplay and implications on the life and health of FOSS/peer production communities, is still vastly unexplored. We would like to partake to the SIGOPEN 2016 Developmental Workshop for Openness Research to help us move our work forward with the ultimate objective to develop a theory of toxicity in the context of FOSS and peer production projects. },
	url = {https://www.researchgate.net/publication/311672787_Towards_Developing_a_Theory_of_Toxicity_in_the_Context_of_FreeOpen_Source_Software_Peer_Production_Communities},
	author = {Carillo, Kevin Daniel Andre and Josianne Marsan and Bogdan Negoita Warwick}
}
@inbook {Coman2016,
	title = {Towards Open Source/Data in the Context of Higher Education: Pragmatic Case Studies Deployed in Romania},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {184{\textendash}191},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Towards Open Source/Data in the Context of Higher Education: Pragmatic Case Studies Deployed in Romania},
	address = {Cham},
	abstract = {The open source ideology is unfortunately not so popular in Romania. This subject represents, to this day, an untackled problem especially in various local educational areas. The paper describes an interesting initiative taken this year by the Faculty of Computer Science, University of Ia{\c s}i, Romania to change the collective opinion by progressively pushing the new generations of students through a binding process with the ideas involved in the open source philosophy. Three ongoing initiatives addressing this problem are detailed, including the results we have obtained so far through them, and also the steps that are planned to be taken soon on the matter.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_15},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_15},
	author = {Coman, Alexandru and C{\^\i}tea, Alexandru and Buraga, Sabin C.},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Heppler2016,
	title = {Who Cares About My Feature Request?},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {85{\textendash}96},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Previous studies on issue tracking systems for open source software (OSS) focused mainly on requests for bug fixes. However, requests to add a new feature or an improvement to an OSS project are often also made in an issue tracking system. These inquiries are particularly important because they determine the further development of the software. This study examines if there is any difference between requests of the IBM developer community and other sources in terms of the likelihood of successful implementation. Our study consists of a case study of the issue tracking system BugZilla in the Eclipse integrated development environment (IDE). Our hypothesis, which was that feature requests from outsiders have less chances of being implemented, than feature requests from IBM developers, was confirmed.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_7},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_7},
	author = {Heppler, Lukas and Eckert, Remo and Stuermer, Matthias},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@proceedings {1830,
	title = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	year = {2016},
	month = {05/2016},
	pages = {163-173},
	publisher = {Springer},
	abstract = {Women are underrepresented in the IT sector. But the situation in FLOSS (free, libre, open source software) development is really extreme in this respect: past publications and studies show a female participation of around 2\% to 5\% and have shed some light into this problem. In this paper, we give an update the state of knowledge tot he current situation of gender in FLOSS, by analyzing the results of surveying more than 2,000 contributors to FLOSS projects in 2013, of which more than 200 were women. Our findings confirm that women enter the FLOSS community later than men, do primarily other tasks than coding, participate less if they have children, and have slightly different reasons to enter (and to stay in) the development communities they join. However, we also find evidence that women are joiningFLOSS projects in higher numbers in recent years, and that the share of women devoting few hours per week to FLOSS and full-time dedication is higher than for men. All in all, comparing our results with the ones from the 2000s, the context of participation of women in FLOSS has not changed much. 
},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper-pre.pdf},
	author = {Gregorio Robles and Reina, Laura Arjona and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Due{\~n}as Dominguez, Santiago}
}
@inbook {Robles2016,
	title = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {163{\textendash}173},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	address = {Cham},
	abstract = {Women are underrepresented in the IT sector. But the situation in FLOSS (free, libre, open source software) development is really extreme in this respect: past publications and studies show a female participation of around 2 \% to 5 \% and have shed some light into this problem. In this paper, we give an update the state of knowledge to the current situation of gender in FLOSS, by analyzing the results of surveying more than 2,000 contributors to FLOSS projects in 2013, of which more than 200 were women. Our findings confirm that women enter the FLOSS community later than men, do primarily other tasks than coding, participate less if they have children, and have slightly different reasons to enter (and to stay in) the development communities they join. However, we also find evidence that women are joining FLOSS projects in higher numbers in recent years, and that the share of women devoting few hours per week to FLOSS and full-time dedication is higher than for men. All in all, comparing our results with the ones from the 2000s, the context of participation of women in FLOSS has not changed much.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_13},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_13},
	author = {Gregorio Robles and Reina, Laura Arjona and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Dom{\'\i}nguez, Santiago Due{\~n}as},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@proceedings {1759,
	title = {An Architectural Evolution Dataset},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {A good evolution process and a good architecture
can greatly support the maintainability of long-lived, large software
systems. We present AREVOL, a dataset for the empirical
study of architectural evolution. The dataset comprises two
popular systems from the same domain and using the same
component model, to make comparative studies possible. Besides
the original component metadata, AREVOL includes scripts to
obtain simplified models that nevertheless support rich studies of
architectural evolution, as the authors{\textquoteright} previous work has shown.},
	url = {http://oro.open.ac.uk/42318/1/wermelinger15msr.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wermelinger15msr.pdf},
	author = {Wermelinger, Michel and Yu, Yijun}
}
@conference {VGZ15,
	title = {Automatically Prioritizing Pull Requests},
	booktitle = {Proceedings of the 12th International Conference on Mining Software Repositories},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {In previous work, we observed that in the pull-based
development model integrators face challenges with regard to prioritizing
work in the face of multiple concurrent pull requests. We
present the design and initial implementation of a prototype pull
request prioritisation tool called PRioritizer. PRioritizer works
like a priority inbox for pull requests, recommending the top pull
requests the project owner should focus on. A preliminary user
study showed that PRioritizer provides functionality that GitHub
is currently lacking, even though users need more insight into
how the priority ranking is established to make PRioritizer really
useful.},
	url = {http://www.gousios.gr/pub/prioritizer.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/prioritizer.pdf},
	author = {van der Veen, Erik and Gousios, Georgios and Zaidman, Andy}
}
@inbook {1735,
	title = {On the Availability and Effectiveness of Open Source Software for Digital Signing of PDF Documents},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {71-80},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Digital signatures are important in order to ensure the integrity and authenticity of information communicated over the Internet involving different stakeholders within and beyond the borders of different nations. The topic has gained increased interest in the European context and there is legislation and project initiatives aiming to facilitate use and standardisation of digital signatures. Open standards and open source implementations of open standards are important means for the interoperability and long-term maintenance of software systems implementing digital signatures. In this paper we report from a study aiming to establish the availability and effectiveness of software provided under an open source license for digital signing and validation of PDF documents. Specifically, we characterise the use of digital signatures in Swedish Governmental agencies, report on the interoperability of open source and proprietary licensed software for digital signatures in PDF documents, and establish the effectiveness of software provided under an open source license for validation of digital signatures in PDF documents.
},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_7},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_7},
	author = {Gamalielsson, Jonas and Jakobsson, Fredrik and Lundell, Bj{\"o}rn and Feist, Jonas and Gustavsson, Tomas and Landqvist, Fredric},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@conference {1800,
	title = {Big data analytics on large-scale socio-technical software engineering archives},
	booktitle = {2015 3rd International Conference on Information and Communication Technology (ICoICT )2015 3rd International Conference on Information and Communication Technology (ICoICT)},
	year = {2015},
	pages = {65 - 69},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Nusa Dua, Bali, Indonesia},
	abstract = {Given the fast growing nature of software engineering data in online software repositories and open source communities, it would be helpful to analyse these assets to discover valuable information about the software engineering development process and other related data. Big Data Analytics (BDA) techniques and frameworks can be applied on these data resources to achieve a high-performance and relevant data collection and analysis. Software engineering is a socio-technical process which needs development team collaboration and technical knowledge to develop a high-quality application. GitHub, as an online social coding foundation, contains valuable information about the software engineers{\textquoteright} communications and project life cycles. In this paper, unsupervised data mining techniques are applied on the data collected by general Big Data approaches to analyse GitHub projects, source codes and interactions. Source codes and projects are clustered using features and metrics derived from historical data in repositories, object oriented programming metrics and the influences of developers on source codes.
},
	doi = {10.1109/ICoICT.2015.7231398},
	author = {Bayati, Shahabedin and Parsons, David and Susnjak, Teo and Heidary, Marzieh}
}
@article {1802,
	title = {Candoia: A Platform and an Ecosystem for Building and Deploying Versatile Mining Software Repositories Tools},
	year = {2015},
	note = {" In terms of its focus,
the Candoia platform is closer to Bevan et al.{\textquoteright}s Kenyon [9],
Bajracharya et al.{\textquoteright}s Sourcerer [6], Gousios and Spinellis{\textquoteright}s Alitheia
Core [32, 31], Howison et al.{\textquoteright}s FLOSSMole [39] and different from
Boetticher et al.{\textquoteright}s PROMISE Repository [69], Gonz{\'a}lez-Barahona
and Robles{\textquoteright}s open-access data repositories [29], Black Duck OpenHub
(aka Ohloh) [13], GHTorrent [30, 33], Ossher et al.{\textquoteright}s SourcererDB
[64], the SourceForge Research Data Archive (SRDA) [28],
and Boa [25]. },
	month = {11/2015},
	institution = {Iowa State University},
	abstract = {Research on mining software repositories (MSR) has shown great
promise during the last decade in solving many challenging software
engineering problems. There exists, however, a {\textquoteleft}valley of death{\textquoteright}
between these significant innovations in the MSR research and their
deployment in practice. The significant cost of converting a prototype
to software; need to provide support for a wide variety of tools
and technologies e.g. CVS, SVN, Git, Bugzilla, Jira, Issues, etc,
to improve applicability; and the high cost of customizing tools to
practitioner-specific settings are some key hurdles in transition to
practice. We describe Candoia, a platform and an ecosystem that
is aimed at bridging this valley of death between innovations in
MSR research and their deployment in practice. We have implemented
Candoia and provide facilities to build and publish MSR
ideas as Candoia apps. Our evaluation demonstrates that Candoia
drastically reduces the cost of converting an idea to an app, thus
reducing the barrier to transitioning research findings into practice.
We also see versatility, in Candoia app{\textquoteright}s ability to work with a variety
of tools and technologies that the platform supports. Finally,
we find that customizing Candoia app to fit project-specific needs
is often well within the grasp of developers.},
	keywords = {Analysis of software and its evolution, Application specific development environments, flossmole cited, msr, research to practice, software evolution, software repositories},
	url = {http://lib.dr.iastate.edu/cgi/viewcontent.cgi?article=1378\&context=cs_techreports},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Candoia-\%20A\%20Platform\%20and\%20an\%20Ecosystem\%20for\%20Building\%20and\%20Deploying\%20V.pdf},
	author = {Nitin M. Tiwari and Dalton D. Mills and Ganesha Upadhyaya and Eric Lin and Rajan, Hridesh}
}
@conference {Hata:2015:CSO:2819321.2819325,
	title = {Characteristics of Sustainable OSS Projects: A Theoretical and Empirical Study},
	booktitle = {Proceedings of the Eighth International Workshop on Cooperative and Human Aspects of Software Engineering},
	series = {CHASE {\textquoteright}15},
	year = {2015},
	note = {Slideshare: http://www.slideshare.net/hideakihata5/characteristics-of-sustainable-oss-projects-a-theoretical-and-empirical-study},
	pages = {15{\textendash}21},
	publisher = {IEEE Press},
	organization = {IEEE Press},
	address = {Piscataway, NJ, USA},
	abstract = {How can we attract developers? What can we do to incentivize developers to write code? We started the study by introducing the population pyramid visualization to software development communities, called software population pyramids, and found a typical pattern in shapes. This pattern comes from the differences in attracting coding contributors and discussion contributors. To understand the causes of the differences, we then build game-theoretical models of the contribution situation. Based on these results, we again analyzed the projects empirically to support the outcome of the models, and found empirical evidence. The answers to the initial questions are clear. To incentivize developers to code, the projects should prepare documents, or the projects or third parties should hire developers, and these are what sustainable projects in GitHub did in reality. In addition, making innovations to reduce the writing costs can also have an impact in attracting coding contributors.},
	url = {http://dl.acm.org/citation.cfm?id=2819321.2819325},
	author = {Hata, Hideaki and Todo, Taiki and Onoue, Saya and Kenichi Matsumoto}
}
@proceedings {1774,
	title = {Characterization and prediction of issue-related risks in software projects},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Identifying risks relevant to a software project and
planning measures to deal with them are critical to the success
of the project. Current practices in risk assessment mostly rely
on high-level, generic guidance or the subjective judgements
of experts. In this paper, we propose a novel approach to
risk assessment using historical data associated with a software
project. Specifically, our approach identifies patterns of past
events that caused project delays, and uses this knowledge to
identify risks in the current state of the project. A set of risk
factors characterizing {\textquotedblleft}risky{\textquotedblright} software tasks (in the form of
issues) were extracted from five open source projects: Apache,
Duraspace, JBoss, Moodle, and Spring. In addition, we performed
feature selection using a sparse logistic regression model to
select risk factors with good discriminative power. Based on
these risk factors, we built predictive models to predict if an
issue will cause a project delay. Our predictive models are able
to predict both the risk impact (i.e. the extend of the delay)
and the likelihood of a risk occurring. The evaluation results
demonstrate the effectiveness of our predictive models, achieving
on average 48\%{\textendash}81\% precision, 23\%{\textendash}90\% recall, 29\%{\textendash}71\%
F-measure, and 70\%{\textendash}92\% Area Under the ROC Curve. Our
predictive models also have low error rates: 0.39{\textendash}0.75 for Macroaveraged
Mean Cost-Error and and 0.7{\textendash}1.2 for Macro-averaged
Mean Absolute Error},
	url = {http://www.uow.edu.au/~hoa/papers/msr-2015-preprint.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr-2015-preprint.pdf},
	author = {Morakot Choetkiertikul and Dam, Hoa Khanh and Truyen Tran and Aditya Ghose}
}
@proceedings {1750,
	title = {Co-evolution of Infrastructure and Source Code - An Empirical Study},
	year = {2015},
	month = {05/2015},
	abstract = {Infrastructure-as-code automates the process of
configuring and setting up the environment (e.g., servers, VMs
and databases) in which a software system will be tested and/or
deployed, through textual specification files in a language like
Puppet or Chef. Since the environment is instantiated automatically
by the infrastructure languages{\textquoteright} tools, no manual
intervention is necessary apart from maintaining the infrastructure
specification files. The amount of work involved with such
maintenance, as well as the size and complexity of infrastructure
specification files, have not yet been studied empirically. Through
an empirical study of the version control system of 265 OpenStack
projects, we find that infrastructure files are large and churn
frequently, which could indicate a potential of introducing bugs.
Furthermore, we found that the infrastructure code files are
coupled tightly with the other files in a project, especially test files,
which implies that testers often need to change infrastructure
specifications when making changes to the test framework and
tests.},
	keywords = {openstack},
	url = {http://mcis.polymtl.ca/publications/2015/msrjojo.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msrjojo.pdf},
	author = {Yujuan Jiang and Adams, Bram}
}
@proceedings {1710,
	title = {Data Mining Behavioral Transitions in Open Source Repositories},
	year = {2015},
	pages = {5280-5289},
	publisher = {IEEE},
	abstract = {Open-source repository data can be automatically mined
using sequence mining methods to provide high-level
feedback on project status. GitHub.com projects are
acquired, sequence-mined, clustered, and regressed to
analyze project characteristics. Such results can be presented
to project managers, as part of a display generated by an
automated monitoring system. Such monitoring systems
provide high-level feedback in real-time. This project is a
preliminary step in a larger research project aimed at
understanding and monitoring FLOSS projects using this
process modeling approach. },
	author = {Robinson, William and Tianjie Deng}
}
@proceedings {1762,
	title = {A Data Set for Social Diversity Studies of GitHub Teams},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Like any other team oriented activity, the software
development process is effected by social diversity in the programmer
teams. The effect of team diversity can be significant,
but also complex, especially in decentralized teams. Discerning
the precise contribution of diversity on teams{\textquoteright} effectiveness
requires quantitative studies of large data sets.
Here we present for the first time a large data set of social
diversity attributes of programmers in GITHUB teams. Using
alias resolution, location data, and gender inference techniques,
we collected a team social diversity data set of 23,493 GITHUB
projects. We illustrate how the data set can be used in practice
with a series of case studies, and we hope its availability will foster
more interest in studying diversity issues in software teams.},
	keywords = {ghtorrent, github},
	url = {http://www.win.tue.nl/~aserebre/cr-msr-data-15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cr-msr-data-15.pdf},
	author = {Vasilescu, Bogdan and Serebrenik, Alexander and Filkov, Vladimir}
}
@proceedings {1760,
	title = {A Dataset For API Usage},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {An Application Programming Interface (API) provides
a specific set of functionalities to a developer. The main aim
of an API is to encourage the reuse of already existing functionality.
There has been some work done into API popularity trends,
API evolution and API usage. For all the aforementioned research
avenues there has been a need to mine the usage of an API in
order to perform any kind of analysis. Each one of the approaches
that has been employed in the past involved a certain degree
of inaccuracy as there was no type check that takes place. We
introduce an approach that takes type information into account
while mining API method invocations and annotation usages.
This approach accurately makes a connection between a method
invocation and the class of the API to which the method belongs
to. We try collecting as many usages of an API as possible, this
is achieved by targeting projects hosted on GitHub. Additionally,
we look at the history of every project to collect the usage of an
API from earliest version onwards. By making such a large and
rich dataset public, we hope to stimulate some more research in
the field of APIs with the aid of accurate API usage samples.},
	url = {http://sback.it/publications/msr2015data.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015data.pdf},
	author = {Anand Ashok Sawant and Bacchelli, Alberto}
}
@proceedings {1763,
	title = {A Dataset of High Impact Bugs: Manually-Classified Issue Reports},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The importance of supporting test and maintenance
activities in software development has been increasing, since
recent software systems have become large and complex. Although
in the field of Mining Software Repositories (MSR) there
are many promising approaches to predicting, localizing, and
triaging bugs, most of them do not consider impacts of each
bug on users and developers but rather treat all bugs with equal
weighting, excepting a few studies on high impact bugs including
security, performance, blocking, and so forth. To make MSR
techniques more actionable and effective in practice, we need
deeper understandings of high impact bugs. In this paper we
introduced our dataset of high impact bugs which was created
by manually reviewing four thousand issue reports in four open
source projects (Ambari, Camel, Derby and Wicket).},
	keywords = {ambari, camel, derby, wicket},
	url = {http://oss.sys.wakayama-u.ac.jp/publications/pman3.cgi?DOWNLOAD=141},
	attachments = {https://flosshub.org/sites/flosshub.org/files/5594a518.pdf},
	author = {Ohira, Masao and Yutaro Kashiwa and Yosuke Yamatani and Hayato Yoshiyuki and Yoshiya Maeda and Nachai Limsettho and Keisuke Fujino and Hata, Hideaki and Ihara, Akinori and Kenichi Matsumoto}
}
@proceedings {1758,
	title = {A Dataset of the Activity of the git Super-repository of Linux in 2012},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {This dataset documents the activity in the public
portion of the git Super-repository of the Linux kernel during
2012. In a distributed version control system, such as git, the
Super-repository is the collection of all the repositories (repos)
used for development. In such a Super-repository, some repos
will be accessible only by their owners (they are private, and
are located in places that are unreachable to other users) while
others are available to other members of the team. The latter
public repositories are used as avenues through which commits
flow from one developer to another. During the last six weeks of
2011, we proceeded to automatically discover the public portion
of the Super-repository of Linux. Then, in 2012, every 3 hrs,
each of these public repositories was queried to see what new
commits it had and what commits had disappeared from it
using a process we call continuous mining. This resulted in the
identification of 533,513 different commits across 451 different
public repositories and how they propagated through the Linux
Super-repository, including the repository of Linus Torvalds (i.e.,
the main repository of the Linux kernel). This information could
help us understand how kernel contributors use git, how they
collaborate and how commits are integrated into the Linux kernel
and into the repositories of organizations that distribute the
kernel.
This dataset is at http://turingmachine.org/2015/linuxGit},
	url = {http://turingmachine.org/2015/linuxGit/msr-data-git-linux.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr-data-git-linux.pdf},
	author = {Daniel M. German and Adams, Bram and Hassan, Ahmed E.}
}
@proceedings {1757,
	title = {The Debsources Dataset: Two Decades of Debian Source Code Metadata},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {We present the Debsources Dataset: distribution
metadata and source code metrics spanning two decades of Free
and Open Source Software (FOSS) history, seen through the lens
of the Debian distribution.
Debsources is a software platform used to gather, search, and
publish on the Web the full source code of the Debian operating
system, as well as measures about it. A notable public instance
of Debsources is available at http://sources.debian.net; it includes
both current and historical releases of Debian. Plugins to compute
popular source code metrics (lines of code, defined symbols,
disk usage) and other derived data (e.g., checksums) have been
written, integrated, and run on all the source code available on
sources.debian.net.
The Debsources Dataset is a PostgreSQL database dump
of sources.debian.net metadata, as of February 10th, 2015.
The dataset contains both Debian-specific metadata{\textemdash}e.g., which
software packages are available in which release, which source
code file belong to which package, release dates, etc.{\textemdash}and source
code information gathered by running Debsources plugins.
The Debsources Dataset offer a very long-term historical view
of the macro-level evolution and constitution of FOSS through
the lens of popular, representative FOSS projects of their times.},
	keywords = {debian},
	url = {https://upsilon.cc/~zack/research/publications/debsources-msr-2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/debsources-msr-2015.pdf},
	author = {Zacchiroli, Stefano}
}
@proceedings {1722,
	title = {The diffusion of pastebin tools to enhance communication in FLOSS mailing lists},
	year = {2015},
	month = {05/2015},
	pages = {45-57},
	abstract = {This paper describes how software developers who use mailing lists to communicate reacted and adjusted to a new supplementary collaboration tool, called a pastebin service. Using publicly-available archives of 8800 mailing lists, we examine the adoption of the pastebin tool by software developers and compare it to the model presented in Diffusion of Innovation (DoI) theory. We then compare the rate at which software developers decided whether to accept or reject the new pastebin tools. We find that the overall rate of pastebin adoption follows the S-curve predicted by classic DoI theory. We then compare the individual pastebin services and their rates of adoption, as well as the reaction of different communities to the new tools and the various rationales for accepting or rejecting them.},
	doi = {http://dx.doi.org/10.1007/978-3-319-17837-0_5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/pastebinOSS2015Preprint.pdf},
	author = {Squire, Megan and Smith, Amber}
}
@mastersthesis {1773,
	title = {Do Bugs Foreshadow Vulnerabilities? A Study of the Chromium Project},
	year = {2015},
	type = {Thesis},
	address = {Rochester Institute of Technology},
	abstract = {As developers face ever-increasing pressure to engineer secure software, researchers are building an understanding of security-sensitive bugs (i.e. vulnerabilities). Research into mining software repositories has greatly increased our understanding of software quality via empirical study of bugs. However, conceptually vulnerabilities are different from bugs: they represent abusive functionality as opposed to wrong or insufficient functionality commonly associated with traditional, non-security bugs. In this study, we performed an in-depth analysis of the Chromium project to empirically examine the relationship between bugs and vulnerabilities. We mined 374,686 bugs and 703 post-release vulnerabilities over five Chromium releases that span six years of development. Using logistic regression analysis, we examined how various categories of pre-release bugs and review experiences (e.g. stability, compatibility, etc.) are associated with post-release vulnerabilities. While we found statistically significant correlations between our metrics and post-release vulnerabilities, we also found the association to be weak. Number of features, SLOC, and number of pre-release security bugs are, in general, more closely associated with post-release vulnerabilities than any of our non-security bug categories. In a separate analysis, we found that the files with highest defect density did not intersect with the files of highest vulnerability density. These results indicate that bugs and vulnerabilities are empirically dissimilar groups, warranting the need for more research targeting vulnerabilities specifically.},
	url = {http://scholarworks.rit.edu/theses/8695/},
	author = {Felivel Camilo}
}
@conference {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.}
}
@inbook {1741,
	title = {First Results About Motivation and Impact of License Changes in Open Source Projects},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {137-145},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Free and open source software is characterized by the freedoms and criteria that are warranted by specific licenses. These licenses describe the rights and duties of the licensors and licensees. However, a licensing change may be necessary in the life of an open source project to meet legal developments or to allow the implementation of new business models. This paper examines the motivations and impacts of license changes in open source projects. After a state of the art on the subject, a set of case studies where projects changed their license is presented. Then a set of motivations to change licenses, the ways to legally make this change, the problems caused by this change and a set of benefits of the license change are discussed.
},
	keywords = {Business model, Contributor agreement, intellectual property, license, open source},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_13},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_13},
	author = {Viseur, Robert and Gregorio Robles},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {1708,
	title = {FLOSS as a source for profanity and insults: Collecting the data},
	year = {2015},
	note = {http://flossdata.syr.edu/data/insults/},
	month = {1/2015},
	publisher = {IEEE},
	abstract = {An important task in machine learning and natural language processing is to learn to recognize different types of human speech, including humor, sarcasm, insults, and profanity. In this paper we describe our method to produce test and training data sets to assist in this task. Our test data sets are taken from the domain of free, libre, and open source software (FLOSS) development communities. We describe our process in constructing helper sets of relevant data, such as profanity lists, lists of insults, and lists of projects with their codes of conduct. Contributions of this paper are to describe the background literature on computer-aided methods of recognizing insulting or profane speech, to describe the parameters of data sets that are useful in this work, and to outline how FLOSS communities are such a rich source of insulting or profane speech data. We then describe our data sets in detail, including how we created these data sets, and provide some initial guidelines for usage.
},
	doi = {10.1109/HICSS.2015.623},
	url = {https://docs.google.com/presentation/d/1DIkv_Qrq0mPtbkS3eCH2w-Ly4nvz0h5qy8y8NjZjhMU/edit?usp=sharing},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hicssInsultsv2.pdf},
	author = {Squire, Megan and Gazda, Rebecca}
}
@proceedings {1789,
	title = {The FLOSS History in Japan: An Ethnographic Approach},
	year = {2015},
	month = {08/2015},
	abstract = {This paper reports an overview of the Internet history project
which especially focuses on Free / Libre / Open-Source Software
(FLOSS) history. The project adopts an ethnographical
approach and it aims to compose a chronicle on the
growth of FLOSS history in Japan. An outcome of the
project is expected to be not only a record but a compass
for younger generations. The project has already started
and conducted several interviews. In this paper, an interim
report of our analysis based on the interviews is presented.},
	url = {http://www.opensym.org/os2015/proceedings-files/p105-iio.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p105-iio.pdf},
	author = {Iio, Jun and Hatta, Masayuki and Ko Kazaana}
}
@proceedings {1713,
	title = {Gender and Tenure Diversity in GitHub Teams},
	year = {2015},
	abstract = {Software development is usually a collaborative venture.
Open Source Software (OSS) projects are no exception; indeed,
by design, the OSS approach can accommodate teams
that are more open, geographically distributed, and dynamic
than commercial teams. This, we find, leads to OSS teams
that are quite diverse. Team diversity, predominantly in of-
fline groups, is known to correlate with team output, mostly
with positive effects. How about in OSS?
Using GITHUB, the largest publicly available collection of
OSS projects, we studied how gender and tenure diversity
relate to team productivity and turnover. Using regression
modeling of GITHUB data and the results of a survey, we
show that both gender and tenure diversity are positive and
significant predictors of productivity, together explaining a
sizable fraction of the data variability. These results can
inform decision making on all levels, leading to better outcomes
in recruiting and performance.},
	keywords = {gender, github, team},
	url = {http://bvasiles.github.io/papers/chi15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/chi15.pdf},
	author = {Vasilescu, Bogdan and Posnett, Daryl and Ray, Baishakhi and van den Brand, Mark G.J. and Serebrenik, Alexander and Devanbu, Premkumar and Filkov, Vladimir}
}
@proceedings {KMGSL15,
	title = {Generating the Blueprints of the Java Ecosystem},
	year = {2015},
	note = {To appear},
	month = {05/2015},
	publisher = {IEEE Computer Society},
	url = {http://gaijin.dmst.aueb.gr/~bkarak/poster_msr2015.pdf},
	author = {Vassilios Karakoidas and Mitropoulos, Dimitris and Louridas, Panos and Gousios, Georgios and Diomidis Spinellis}
}
@proceedings {1771,
	title = {A Historical Analysis of Debian Package Incompatibilities},
	year = {2015},
	abstract = {Users and developers of software distributions are often confronted with installation problems due to conflicting packages. A prototypical example of this are the Linux distributions such as Debian. Conflicts between packages have been studied under different points of view in the literature, in particular for the Debian operating system, but little is known about how these package conflicts evolve over time. This article presents an extensive analysis of the evolution of package incompatibilities, spanning a decade of the life of the Debian stable and testing distributions for its most popular architecture, i386. Using the technique of survival analysis, this empirical study sheds some light on the origin and evolution of package incompatibilities, and provides the basis for building indicators that may be used to improve the quality of package-based distributions.
},
	url = {http://di.umons.ac.be/details.aspx?pub=b5a887bd-0612-4439-8f66-ec37803a32db},
	author = {Claes Maelick and Mens Tom and Di Cosmo Robert and Vouillon Jerome}
}
@inbook {1732,
	title = {How Developers Acquire FLOSS Skills},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {23-32},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {With the increasing prominence of open collaboration as found in free/libre/open source software projects and other joint production communities, potential participants need to acquire skills. How these skills are learned has received little research attention. This article presents a large-scale survey (5,309 valid responses) in which users and developers of the beta release of a popular file download application were asked which learning styles were used to acquire technical and social skills. We find that the extent to which a person acquired the relevant skills through informal methods tends to be higher if the person is a free/libre/open source code contributor, while being a professional software developer does not have this effect. Additionally, younger participants proved more likely to make use of formal methods of learning. These insights will help individuals, commercial companies, educational institutions, governments and open collaborative projects decide how they promote learning.
},
	keywords = {competencies, Informal learning, Non-formal learning, open source, Skills, Software developer},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_3},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/oss-2015.pdf},
	author = {Barcomb, Ann and Grottke, Michael and Stauffert, Jan-Philipp and Dirk Riehle and Jahn, Sabrina},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1733,
	title = {Implicit Coordination: A Case Study of the Rails OSS Project},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {35-44},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Previous studies on coordination in OSS projects have studied explicit communication. Research has theorized on the existence of coordination without direct communication or implicit coordination in OSS projects, suggesting that it contributes to their success. However, due to the intangible nature of implicit coordination, no studies have confirmed these theories. We describe how implicit coordination can now be measured in modern collaborative development environments. Through a case study of a popular OSS GitHub-hosted project, we report on how and why features that support implicit coordination are used.
},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_4},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_4},
	author = {Blincoe, Kelly and Damian, Daniela},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@article {1796,
	title = {An in-depth study of the promises and perils of mining GitHub},
	journal = {Empirical Software Engineering},
	year = {2015},
	publisher = {Springer},
	abstract = {With over 10 million git repositories, GitHub is becoming one of the most important sources of software artifacts on the Internet. Researchers mine the information stored in GitHub{\textquoteright}s event logs to understand how its users employ the site to collaborate on software, but so far there have been no studies describing the quality and properties of the available GitHub data. We document the results of an empirical study aimed at understanding the characteristics of the repositories and users in GitHub; we see how users take advantage of GitHub{\textquoteright}s main features and how their activity is tracked on GitHub and related datasets to point out misalignment between the real and mined data. Our results indicate that while GitHub is a rich source of data on software development, mining GitHub for research purposes should take various potential perils into consideration. For example, we show that the majority of the projects are personal and inactive, and that almost 40\% of all pull requests do not appear as merged even though they were. Also, approximately half of GitHub{\textquoteright}s registered users do not have public activity, while the activity of GitHub users in repositories is not always easy to pinpoint. We use our identified perils to see if they can pose validity threats; we review selected papers from the MSR 2014 Mining Challenge and see if there are potential impacts to consider. We provide a set of recommendations for software engineering researchers on how to approach the data in GitHub.},
	keywords = {github},
	issn = {1573-7616},
	doi = {10.1007/s10664-015-9393-5},
	url = {http://www.gousios.gr/pub/promises-perils-github-extended.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/promises-perils-github-extended.pdf},
	author = {Kalliamvakou, Eirini and Gousios, Georgios and Blincoe, Kelly and Singer, Leif and Daniel M. German and Damian, Daniela}
}
@article {1747,
	title = {Inner Source--Adopting Open Source Development Practices within Organizations: A Tutorial},
	journal = {IEEE Software},
	year = {2015},
	month = {07/2015},
	pages = {1 - 1},
	publisher = {IEEE},
	abstract = {Inner source, the adoption and tailoring of Open Source development practices inside organizations, is a topic of increasing interest. While Inner Source offers a number of benefits, in our experience many practitioners are unclear as to what Inner Source is, and what steps to take towards adoption. In this article we present a tutorial in which we outline nine key factors, pertaining to product, process and organization, which we have found to be important in working with organizations who are interested in Inner Source. This paper illustrates these nine factors with three inner source initiatives that we have studied. },
	issn = {0740-7459},
	doi = {10.1109/MS.2014.77},
	author = {Stol, Klaas-Jan and Fitzgerald, Brian}
}
@article {1717,
	title = {An insight into license tools for open source software systems},
	journal = {Journal of Systems and Software},
	volume = {102},
	year = {2015},
	note = {"An additional tool can be found in FLOSSmole ( Howison et al., 2006), which is a central repository containing data and analyses about FLOSS projects collected and prepared in a decentralized manner. Content from FLOSSmole was intended to be used for the construction of an intelligent information system for FLOSS, namely FLOSSWALD (Hanft and Reichle, 2007). "},
	month = {04/2015},
	pages = {72 - 87},
	abstract = {Free/Libre/Open Source Software (FLOSS) has gained a lot of attention lately allowing organizations to incorporate third party source code into their implementations. When open source software libraries are used, software resources may be linked directly or indirectly with multiple open source licenses giving rise to potential license incompatibilities. Adequate support in license use is vital in order to avoid such violations and address how diverse licenses should be handled. In the current work we investigate software licensing giving a critical and comparative overview of existing assistive approaches and tools. These approaches are centered on three main categories: license information identification from source code and binaries, software metadata stored in code repositories, and license modeling and associated reasoning actions. We also give a formalization of the license compatibility problem and demonstrate the role of existing approaches in license use decisions.},
	keywords = {flossmole cited},
	issn = {01641212},
	doi = {10.1016/j.jss.2014.12.050},
	url = {http://www.sciencedirect.com/science/article/pii/S0164121214002945},
	author = {Kapitsaki, Georgia M. and Tselikas, Nikolaos D. and Foukarakis, Ioannis E.}
}
@conference {1798,
	title = {Integrating Open Source Software Repositories on the Web through Linked Data},
	booktitle = {2015 IEEE International Conference on Information Reuse and Integration (IRI)2015 IEEE International Conference on Information Reuse and Integration},
	year = {2015},
	pages = {114 - 121},
	publisher = {IEEE},
	organization = {IEEE},
	address = {San Francisco, CA, USA},
	abstract = {In this paper, we propose a novel approach to the problem of integrating code forges based on metadata (e.g., programming language, database, intended audience, operating system), similar software projects and software developers. We review the current problems in integrating metadata of different code forges and argue that Semantic Web technologies are suitable for representing and integrating knowledge contained inside these code forges. Further, we show the advantages of interlinking metadata of software projects to other relevant data sources on the Web, which will enable querying more information from the Web. Moreover, we compute the overlapping between code forges based on similar software developers and argue the benefit of interlinking similar software developers and software projects across different code forges through examples.
},
	doi = {10.1109/IRI.2015.27},
	author = {Iqbal, Aftab and Decker, Stefan}
}
@proceedings {1769,
	title = {Investigating Code Review Practices in Defective Files: An Empirical Study of the Qt System},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Software code review is a well-established software
quality practice. Recently, Modern Code Review (MCR) has been
widely adopted in both open source and proprietary projects.
To evaluate the impact that characteristics of MCR practices
have on software quality, this paper comparatively studies MCR
practices in defective and clean source code files. We investigate
defective files along two perspectives: 1) files that will eventually
have defects (i.e., future-defective files) and 2) files that have
historically been defective (i.e., risky files). Through an empirical
study of 11,736 reviews of changes to 24,486 files from the Qt
open source project, we find that both future-defective files and
risky files tend to be reviewed less rigorously than their clean
counterparts. We also find that the concerns addressed during
the code reviews of both defective and clean files tend to enhance
evolvability, i.e., ease future maintenance (like documentation),
rather than focus on functional issues (like incorrect program
logic). Our findings suggest that although functionality concerns
are rarely addressed during code review, the rigor of the
reviewing process that is applied to a source code file throughout
a development cycle shares a link with its defect proneness.},
	keywords = {code review, software quality},
	url = {http://sail.cs.queensu.ca/publications/pubs/msr2015-thongtanunam.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015-thongtanunam.pdf},
	author = {Patanamon Thongtanunam and McIntosh, Shane and Hassan, Ahmed E. and Hajimu Iida}
}
@proceedings {1785,
	title = {An Investigation of Migrating from Proprietary RTOS to Embedded Linux},
	year = {2015},
	month = {08/2015},
	abstract = {Embedded systems and the open source operating system
Linux have been going hand in hand for a long time now.
Companies using Linux for their embedded products are
praising it for being time and cost efficient when it comes to
performance and maintainability. Another solution for embedded
systems is a Real-Time Operating System (RTOS).
The goal of this this paper is to investigate whether a traditional
proprietary RTOS can be substituted with embedded
Linux, and if this kind of migration can lead to reduced licensing
costs and increased general quality of the system.
We used a qualitative research method for this case-study.
The investigation was conducted with interviews as the main
source of information. The result of this study is an empirical
model we named {\textquoteright}Embedded Linux Adoption Model{\textquoteright}.
We concluded that in many cases a proprietary RTOS can
be substituted with embedded Linux without affecting the
critical needs of the system. The study also showed that
many embedded system developers are very receptive to
open source solutions and could think of contributing to the
community.},
	url = {http://www.opensym.org/os2015/proceedings-files/p101-muchow.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p101-muchow.pdf},
	author = {Oscar Muchow and David Ustarbowski and Hammouda, Imed}
}
@proceedings {1729,
	title = {A Large Scale Study of License Usage on GitHub},
	volume = {2},
	year = {2015},
	note = {14.9\% of projects have a license file.},
	month = {05/2015},
	pages = {772-774},
	publisher = {ACM/IEEE},
	abstract = {The open source community relies upon licensing
in order to govern the distribution, modification, and reuse of
existing code. These licenses evolve to better suit the requirements
of the development communities and to cope with unaddressed
or new legal issues. In this paper, we report the results of a large
empirical study conducted over the change history of 16,221 open
source Java projects mined from GitHub. Our study investigates
how licensing usage and adoption changes over a period of ten
years. We consider both the distribution of license usage within
projects of a rapidly growing forge and the extent that new
versions of licenses are introduced in these projects.},
	keywords = {github, license},
	author = {Vendome, Christopher}
}
@booklet {1781,
	title = {Lessons Learned from Applying Social Network Analysis on an Industrial Free/Libre/Open Source Software Ecosystem},
	year = {2015},
	abstract = {Many software projects are no longer done in-house by a single organization. Instead, we are in a new age where software is developed by a networked community of individuals and organizations, which base their relations to each other on mutual interest. Paradoxically, recent research suggests that software development can actually be jointly-developed by rival firms. For instance, it is known that the mobile-device makers Apple and Samsung kept collaborating in open source projects while running expensive patent wars in the court. Taking a case study approach, we explore how rival firms collaborate in the open source arena by employing a multi-method approach that combines qualitative analysis of archival data (QA) with mining software repositories (MSR) and Social Network Analysis (SNA). While exploring collaborative processes within the OpenStack ecosystem, our research contributes to Software Engineering research by exploring the role of groups, sub-communities and business models within a high-networked open source ecosystem. Surprising results point out that competition for the same revenue model (i.e., operating conflicting business models) does not necessary affect collaboration within the ecosystem. Moreover, while detecting the different sub-communities of the OpenStack community, we found out that the expected social tendency of developers to work with developers from same firm (i.e., homophony) did not hold within the OpenStack ecosystem. Furthermore, while addressing a novel, complex and unexplored open source case, this research also contributes to the management literature in coopetition strategy and high-tech entrepreneurship with a rich description on how heterogeneous actors within a high-networked ecosystem (involving individuals, startups, established firms and public organizations) joint-develop a complex infrastructure for big-data in the open source arena.},
	keywords = {business models, cloud computing, homophily, open source, Open-Coopetition, openstack, social network analysis, Software ecosystems},
	url = {http://arxiv.org/abs/1507.04587},
	author = {Teixeira, Jose and Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@conference {HG15,
	title = {Matching GitHub developer profiles to job advertisements},
	booktitle = {Proceedings of the 12th International Conference on Mining Software Repositories},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {GitHub is a social coding platform that enables
developers to efficiently work on projects, connect with other
developers, collaborate and generally {\textquotedblleft}be seen{\textquotedblright} by the community.
This visibility also extends to prospective employers and HR
personnel who may use GitHub to learn more about a developer{\textquoteright}s
skills and interests. We propose a pipeline that automatizes this
process and automatically suggests matching job advertisements
to developers, based on signals extracting from their activities on
GitHub.},
	url = {http://www.gousios.gr/pub/dev-profiles.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dev-profiles.pdf},
	author = {Hauff, Claudia and Gousios, Georgios}
}
@proceedings {1790,
	title = {Measuring the Crowd {\textendash} A Preliminary Taxonomy of Crowdsourcing Metrics},
	year = {2015},
	month = {08/2015},
	abstract = {Crowdsourcing initiatives benefit from tapping into diversity. A
vast plethora of disparate individuals, organizations, frameworks
and skillsets can all play a role in sourcing solutions to a
challenge. Nevertheless, while crowdsourcing has become a
pervasive phenomenon, there is a paucity of research that
addresses how the crowdsourcing process is measured. Whereas
research has advanced various taxonomies of crowdsourcing none
to date have specifically addressed the issue of measuring either
specific stages of the crowdsourcing process or the process as a
whole. As a first step towards achieving this goal, this research-inprogress
paper examines crowdsourcing at the operational level
with a view towards (i) identifying the parts of the process (ii)
identifying what can be measured and (iii) categorising
operational metrics to facilitate deployment in practice. The
taxonomy advanced is overarching in nature and can be deployed
across disciplines. Furthermore, the preliminary taxonomy
presented will offer practitioners a comprehensive list of metrics
that will enable them to facilitate comparison across various
crowdsourcing initiatives.},
	url = {http://www.opensym.org/os2015/proceedings-files/p200-cullina.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p200-cullina.pdf},
	author = {Eoin Cullina and Kieran Conboy and Morgan, Lorraine}
}
@proceedings {1776,
	title = {A Method to Detect License Inconsistencies in Large-Scale Open Source Projects},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The reuse of free and open source software (FOSS)
components is becoming more and more popular. They usually
contain one or more software licenses describing the requirements
and conditions which should be followed when been reused.
Licenses are usually written in the header of source code files as
program comments. Removing or modifying the license header
by re-distributors will result in the inconsistency of license with
its ancestor, and may potentially cause license infringement. But
to the best of our knowledge, no research has been devoted
to investigate such kind of license infringements nor license
inconsistencies. In this paper, we describe and categorize different
types of license inconsistencies and propose a feasible method to
detect them. Then we apply this method to Debian 7.5 and present
the license inconsistencies found in it. With a manual analysis, we
summarized various reasons behind these license inconsistencies,
some of which imply license infringement and require the attention
from the developers. This analysis also exposes the difficulty
to discover license infringements, highlighting the usefulness of
finding and maintaining source code provenance.},
	url = {http://sel.ist.osaka-u.ac.jp/lab-db/betuzuri/archive/992/992.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/992.pdf},
	author = {Yuhao Wu and Manabe, Yuki and Tetsuya Kanda and Daniel M. German and Inoue, Katsuro}
}
@proceedings {1748,
	title = {Mining Component Repositories for Installability Issues},
	year = {2015},
	month = {05/2015},
	abstract = {Component repositories play an increasingly relevant
role in software life-cycle management, from software
distribution to end-user, to deployment and upgrade management.
Software components shipped via such repositories are
equipped with rich metadata that describe their relationship (e.g.,
dependencies and conflicts) with other components.
In this practice paper we show how to use a tool, distcheck,
that uses component metadata to identify all the components in
a repository that cannot be installed (e.g., due to unsatisfiable
dependencies), provides detailed information to help developers
understanding the cause of the problem, and fix it in the
repository.
We report about detailed analyses of several repositories: the
Debian distribution, the OPAM package collection, and Drupal
modules. In each case, distcheck is able to efficiently identify not
installable components and provide valuable explanations of the
issues. Our experience provides solid ground for generalizing the
use of distcheck to other component repositories.},
	keywords = {drupal, opam},
	url = {http://www.dicosmo.org/preprints/msr-2015-distcheck.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr-2015-distcheck.pdf},
	author = {Abate, Pietro and Di Cosmo, Roberto and Gesbert, Louis and Fabrice Le Fessant and Ralf Treinen and Zacchiroli, Stefano}
}
@proceedings {1751,
	title = {Mining Energy-Aware Commits},
	year = {2015},
	month = {05/2015},
	abstract = {Over the last years, energy consumption has become
a first-class citizen in software development practice. While
energy-efficient solutions on lower-level layers of the software
stack are well-established, there is convincing evidence that even
better results can be achieved by encouraging practitioners to
participate in the process. For instance, previous work has shown
that using a newer version of a concurrent data structure can
yield a 2.19x energy savings when compared to the old associative
implementation [75]. Nonetheless, little is known about how much
software engineers are employing energy-efficient solutions in
their applications and what solutions they employ for improving
energy-efficiency. In this paper we present a qualitative study
of {\textquotedblleft}energy-aware commits{\textquotedblright}. Using Github as our primary data
source, we perform a thorough analysis on an initial sample of
2,189 commits and carefully curate a set of 371 energy-aware
commits spread over 317 real-world non-trivial applications.
Our study reveals that software developers heavily rely on lowlevel
energy management approaches, such as frequency scaling
and multiple levels of idleness. Also, our findings suggest that
ill-chosen energy saving techniques can impact the correctness
of an application. Yet, we found what we call {\textquotedblleft}energy-aware
interfaces{\textquotedblright}, which are means for clients (e.g., developers or endusers)
to save energy in their applications just by using a function,
abstracting away the low-level implementation details.},
	url = {http://gustavopinto.org/lost+found/msr2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/energy.pdf},
	author = {Irineu Moura and Pinto, Gustavo and Felipe Ebert and Fernando Castor}
}
@proceedings {1728,
	title = {Mining Software Repositories for Social Norms},
	volume = {2},
	year = {2015},
	pages = {627-630},
	abstract = {Social norms facilitate coordination and cooperation
among individuals, thus enable smoother functioning of social
groups such as the highly distributed and diverse open source
software development (OSSD) communities. In these communities,
norms are mostly implicit and hidden in huge records
of human-interaction information such as emails, discussions
threads, bug reports, commit messages and even source code. This
paper aims to introduce a new line of research on extracting social
norms from the rich data available in software repositories. Initial
results include a study of coding convention violations in JEdit,
ArgoUML and Glassfish projects. It also presents a new lifecycle
model for norms in OSSD communities and demonstrates
how a number of norms extracted from the Python development
community follow this life-cycle model.},
	author = {Dam, Hoa Khanh and Savarimuthu, Bastin Tony Roy and Daniel Avery and Aditya Ghose}
}
@proceedings {1725,
	title = {Mining StackOverflow to Filter out Off-topic IRC Discussion},
	year = {2015},
	month = {05/2015},
	pages = {4 pages},
	abstract = {Internet Relay Chat (IRC) is a commonly used tool by OpenSource developers. Developers use IRC channels to discuss programming related problems, but much of the discussion is irrelevant and off-topic. Essentially if we treat IRC discussions like email messages, and apply spam filtering, we can try to filter out the spam (the off-topic discussions) from the ham (the programming discussions). Yet we need labelled data that unfortunately takes time to curate.
To avoid costly curration in order to filter out off-topic discussions, we need positive and negative data-sources. On- line discussion forums, such as StackOverflow, are very effective for solving programming problems. By engaging in open-data, StackOverflow data becomes a powerful source of labelled text regarding programming. This work shows that we can train classifiers using StackOverflow posts as positive examples of on-topic programming discussion. YouTube video comments, notorious for their lack of quality, serve as training set of off- topic discussion. By exploiting these datasets, accurate classifiers can be built, tested and evaluated that require very little effort for end-users to deploy and exploit.},
	keywords = {irc, topics},
	url = {http://webdocs.cs.ualberta.ca/~hindle1/2015/shaiful-mining_so.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shaiful-mining_so.pdf},
	author = {Shaiful Alam Chowdhury and Hindle, Abram}
}
@proceedings {1755,
	title = {Mining StackOverflow to Filter out Off-topic IRC Discussion},
	year = {2015},
	month = {05/2015},
	abstract = {Internet Relay Chat (IRC) is a commonly used
tool by OpenSource developers. Developers use IRC channels
to discuss programming related problems, but much of the
discussion is irrelevant and off-topic. Essentially if we treat IRC
discussions like email messages, and apply spam filtering, we can
try to filter out the spam (the off-topic discussions) from the ham
(the programming discussions). Yet we need labelled data that
unfortunately takes time to curate.
To avoid costly curration in order to filter out off-topic
discussions, we need positive and negative data-sources. Online
discussion forums, such as StackOverflow, are very effective
for solving programming problems. By engaging in open-data,
StackOverflow data becomes a powerful source of labelled text
regarding programming. This work shows that we can train
classifiers using StackOverflow posts as positive examples of
on-topic programming discussion. YouTube video comments,
notorious for their lack of quality, serve as training set of offtopic
discussion. By exploiting these datasets, accurate classifiers
can be built, tested and evaluated that require very little effort
for end-users to deploy and exploit.},
	keywords = {irc, Stack Overflow, youtube},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shaiful-mining_so_0.pdf},
	author = {Shaiful Alam Chowdhury and Hindle, Abram}
}
@conference {barcomb:2015:multiple,
	title = {A multiple case study of small free software businesses as social entrepreneurships},
	booktitle = {Proceedings of the 11th International Symposium on Open Collaboration (OpenSym 2015)},
	year = {2015},
	abstract = {Free/libre and open source software are frequently described as a single community or movement. The difference between free software and open source ideology may influence founders, resulting in different types of companies being created. Specifically, the relationship between free/libre software ideology and social entrepreneurships is investigated. This paper presents seven case studies of businesses, five of which were founded by people who  identify with the free/libre software movement. The result is a theory that small businesses founded by free/libre software advocates have three characteristics of social entrepreneurships. First, social benefit is prioritized over wealth creation. Second, the business{\textquoteright}s social mission is not incidental but is furthered through its for-profit activities, rather than supported by the company{\textquoteright}s profits. Third, the company{\textquoteright}s success is defined in part by the success of its social mission Free/libre software entrepreneurs who recognize their activities as social entrepreneurships can benefit from the existing literature on the unique challenges faced by socially-oriented businesses.},
	keywords = {free software, open source software, public good, small business, social entrepreneurship, social ventures},
	url = {https://opus4.kobv.de/opus4-fau/frontdoor/index/index/docId/6334},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p100-barcomb.pdf},
	author = {Barcomb, Ann}
}
@conference {1797,
	title = {On the Need of Integrating Social Media Channels and Open Source Software Repositories},
	booktitle = {2015 IEEE International Conference on Information Reuse and Integration (IRI)2015 IEEE International Conference on Information Reuse and Integration},
	year = {2015},
	pages = {396 - 402},
	publisher = {IEEE},
	organization = {IEEE},
	address = {San Francisco, CA, USA},
	abstract = {The growing interest in the usage of social media channels have attracted the open source software community to adopt an identity in order to disseminate project-related information to a wider audience. We foresee the need to integrate social media channels and open source software repositories in order to get an integrated view on the software project not only from the software development perspective but also from social perspective. Therefore, in this paper we study the usage of Twitter by software developers through harvesting their project-related activities on Twitter. In particular, we present the most frequently used hashtags by software developers and further investigate if project-related hashtags are the most frequent and commonly used hashtags by software developers. Based on our findings, we argue that relevant information from social media channels should be integrated with the open source software repositories in order to provide a homogeneous view on a software project.
},
	doi = {10.1109/IRI.2015.66},
	author = {Iqbal, Aftab and Decker, Stefan}
}
@proceedings {1791,
	title = {Open Innovation for Innovation Tools: the Case of Co-Design Platforms},
	year = {2015},
	month = {08/2015},
	abstract = {This paper explores the dynamics of openness and enclosure of
innovation activities with IT artifacts on the example of co-design
platforms. While modern information and communication technologies
offer many new possibilities for innovation, they also
subject innovation to the underlying technical structures, which
can misdirect the activities on the platform. In order to avoid this,
we propose an open innovation approach for open innovation
solutions. We perform an empirical study on two co-design platforms
which become subjects of innovation themselves in an open
laboratory in the downtown area of a European city. Visitors to
the laboratory are allowed to engage in innovate activities regarding
the co-design platforms in whatever way they want. The results
show that they do not only address technical improvements
of the platforms, but also look into new directions to make the
platforms more relevant or to replace them by other ways of innovating
in the given contexts.},
	url = {http://www.opensym.org/os2015/proceedings-files/p201-fritzsche.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p201-fritzsche.pdf},
	author = {Albrecht Fritzsche and Angela Roth and Kathrin Moslein}
}
@inbook {1782,
	title = {Open Source Technology Development},
	booktitle = {Handbook of Science and Technology Convergence},
	year = {2015},
	pages = {1-9},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {In this chapter, we introduce the practices of free/libre open source software (FLOSS) development as an instance of the convergence of technological affordances with novel social practices to create a novel mode of work. We then consider how FLOSS software might be used for various scientific applications, perhaps leading to a convergence of current distinct disciplines. We conclude by considering how the technologies and practices of FLOSS development might be applied to other settings, thus leading to further convergence of those settings.
},
	keywords = {Free/Libre Open Source Software},
	doi = {10.1007/978-3-319-04033-2_29-1},
	url = {http://dx.doi.org/10.1007/978-3-319-04033-2_29-1},
	author = {Kevin Crowston},
	editor = {Bainbridge, William Sims and Roco, Mihail C.}
}
@proceedings {1726,
	title = {Open Source-Style Collaborative Development Practices in Commercial Projects Using GitHub},
	volume = {1},
	year = {2015},
	month = {05/2015},
	pages = {574-585},
	publisher = {ACM/IEEE},
	abstract = {Researchers are currently drawn to study projects
hosted on GitHub due to its popularity, ease of obtaining data,
and its distinctive built-in social features. GitHub has been found
to create a transparent development environment, which together
with a pull request-based workflow, provides a lightweight mechanism
for committing, reviewing and managing code changes.
These features impact how GitHub is used and the benefits it
provides to teams{\textquoteright} development and collaboration. While most of
the evidence we have is from GitHub{\textquoteright}s use in open source software
(OSS) projects, GitHub is also used in an increasing number of
commercial projects. It is unknown how GitHub supports these
projects given that GitHub{\textquoteright}s workflow model does not intuitively
fit the commercial development way of working. In this paper, we
report findings from an online survey and interviews with GitHub
users on how GitHub is used for collaboration in commercial
projects. We found that many commercial projects adopted
practices that are more typical of OSS projects including reduced
communication, more independent work, and self-organization.
We discuss how GitHub{\textquoteright}s transparency and popular workflow can
promote open collaboration, allowing organizations to increase
code reuse and promote knowledge sharing across their teams.},
	keywords = {github},
	doi = {10.1109/ICSE.2015.74},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icse-camera.pdf},
	author = {Kalliamvakou, E and Damian, Daniela and Blincoe, Kelly and Singer, L. and German, Daniel}
}
@proceedings {1787,
	title = {On the openness of digital platforms/ecosystems},
	year = {2015},
	month = {08/2015},
	abstract = {A plenitude of technology is neither developed in-house nor
simply outsourced in dyadic relationships. Instead, we are in
a new age where technologies are developed by a networked
community of actors and organizations, which base their
relations dynamically to each other on a common interest.
Such dynamic and networked complexity of technology development
is often theoretical explored around the concept
of platform, and more recently by employing the concept of
ecosystem in an analogy to natural ecosystems. Following the
success of open-source software, academics have long been
examining openness in digital platforms/ecosystems; however
most contributions take the perspective of a single stakeholder
from the many that constitute a digital platform/ecosystem.
Predominantly, they take the sole perspective of platform
providers, those bundling hardware and software or more
rarely, the perspective of third-party software developers developing
valuable software {\textquoteright}apps{\textquoteright} that add value to the overall
platform. In this conceptual article, we grasp openness more
holistically, both by acknowledging that openness means different
things to different people and involve all stakeholders
within the platforms/ecosystems. Towards the development
of a theory of openness within digital settings, we propose
six novel aspects of openness for enabling a greater understanding
of the open-source software movement with a digital
platforms/ecosystems perspective. Moreover, we invite scholars
to reconsider the more predominating product-dominant
logic in open-source software research to a more holistic logic
embracing platforms and ecosystem thinking.},
	url = {http://www.opensym.org/os2015/proceedings-files/p103-teixeira.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p103-teixeira.pdf},
	author = {Teixeira, Jose}
}
@conference {1859,
	title = {OSSEAN: Mining Crowd Wisdom in Open Source Communities},
	booktitle = {2015 IEEE Symposium on Service-Oriented System Engineering (SOSE)},
	year = {2015},
	pages = {367 - 371},
	publisher = {IEEE},
	organization = {IEEE},
	address = {San Francisco Bay, CA, USA},
	abstract = {Nowadays open source software represents a successful crowd-based software production model and is becoming an ecosystem combining huge amounts of software producers (such as software developers) and consumers (such as software users and customers). Lots of research work has been conducted on analyzing software artifacts created by producers, but few of them reveal the power of feedback from consumers which we believe is very important for the evaluation and evolution of open source software. This paper introduces OSSEAN, a platform for Open Source Software Evaluating, Analyzing and Networking. OSSEAN divides the open source communities into two groups: software production communities and software consumption communities. The former contain structured software artifacts such as projects, source code and issues, while the latter are full of textual documents with rich semantics of user feedback. We show the power of OSSEAN with some interesting demos by analyzing more than 200 thousands of open source projects and 10 million documents.},
	keywords = {flossmole},
	doi = {10.1109/SOSE.2015.51},
	author = {Yin, Gang and Wang, Tao and Wang, Huaimin and Fan, Qiang and Zhang, Yang and Yu, Yue and Yang, Cheng}
}
@inbook {1738,
	title = {A Qualitative Study on the Adoption of Open Source Software in Information Technology Outsourcing Organizations},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {103-113},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {The purpose of this paper is to identify the influence of Outsourcing on Open source software (OSS) and further investigate the factors that impact the adoption of OSS in global Information Technology (IT) outsourcing organizations serviced by Indian IT services providers. This exploratory research adopted positivism research philosophy and qualitative approach. An in-depth interview was conducted with ten participants across IT outsourcing organizations, IT service providers, and OSS service providers. The results show that IT outsourcing was not found to have an impact on OSS adoption. However, eight factors including management support and OSS support availability was identified to influence OSS adoption. IT services providers can utilize this research model to increase their understanding of why some IT outsourcing organizations choose to adopt OSS, while seemingly similar ones facing similar market conditions do not.
},
	keywords = {Diffusion of innovation, Indian IT, IT outsourcing, open source software, OSS adoption, TOE},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_10},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_10},
	author = {Ramanathan, Lakshmanan and Iyer, Sundaresan Krishnan},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@conference {Spi15c,
	title = {A Repository with 44 Years of {Unix} Evolution},
	booktitle = {MSR {\textquoteright}15: Proceedings of the 12th Working Conference on Mining Software Repositories},
	year = {2015},
	note = {Best Data Showcase Award},
	month = {05/2015},
	pages = {13{\textendash}16},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {The evolution of the Unix operating system is made available as a version-control repository, covering the period from its inception in 1972 as a five thousand line kernel, to 2015 as a widely-used 26 million line system. The repository contains 659 thousand commits and 2306 merges. The repository employs the commonly used Git system for its storage, and is hosted on the popular GitHub archive. It has been created by synthesizing with custom software 24 snapshots of systems developed at Bell Labs, Berkeley University, and the 386BSD team, two legacy repositories, and the modern repository of the open source FreeBSD system. In total, 850 individual contributors are identified, the early ones through primary research. The data set can be used for empirical research in software engineering, information systems, and software archaeology.},
	doi = {10.1109/MSR.2015.6},
	url = {http://www.dmst.aueb.gr/dds/pubs/conf/2015-MSR-Unix-History/html/Spi15c.html},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Spi15c.pdf},
	author = {Diomidis Spinellis}
}
@inbook {1743,
	title = {The Right to a Contribution: An Exploratory Survey on How Organizations Address It},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {157-167},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Free and Open Source Software (FOSS) projects are characterized by the opportunity to attract external contributors, where contributions can be in any form of copyrightable material, such as code or documentation. In most of them it is understood that contributions would be licensed in similar or compatible terms than the project{\textquoteright}s license. Some projects require a copyright transfer from the contributor to an organization for the work contributed to a project, such documents are known as copyright assignment agreements. In a way, it is similar to the copyright transfer than some researchers grant to a publisher. In this work we present an exploratory survey of the multiple visions of copyright assignments, and aggregate them in a work that researchers and practitioners could use to get informed of the alternatives available in the literature. We expect that our findings help inform practitioners on legal concerns when receiving external contributions.
},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_15},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_15},
	author = {Poo-Caama{\~n}o, Germ{\'a}n and German, DanielM.},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1740,
	title = {The RISCOSS Platform for Risk Management in Open Source Software Adoption},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {124-133},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Managing risks related to OSS adoption is a must for organizations that need to smoothly integrate OSS-related practices in their development processes. Adequate tool support may pave the road to effective risk management and ensure the sustainability of such activity. In this paper, we present the RISCOSS platform for managing risks in OSS adoption. RISCOSS builds upon a highly configurable data model that allows customization to several types of scopes. It implements two different working modes: exploration, where the impact of decisions may be assessed before making them; and continuous assessment, where risk variables (and their possible consequences on business goals) are continuously monitored and reported to decision-makers. The blackboard-oriented architecture of the platform defines several interfaces for the identified techniques, allowing new techniques to be plugged in.
},
	keywords = {Open source adoption, Open Source Projects, open source software, OSS, Risk Management, Software platform},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_12},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_12},
	author = {Franch, X. and Kenett, R. and Mancinelli, F. and Susi, A. and Ameller, D. and Annosi, M.C. and Ben-Jacob, R. and Blumenfeld, Y. and Franco, O.H. and Gross, D. and Lopez, L. and Morandini, M. and Oriol, M. and Siena, A.},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@article {1794,
	title = {On the role of FOSS business models and participation architectures in supporting open innovation},
	year = {2015},
	month = {08/2015},
	abstract = {Most research regarding innovation in free and open source
software (FOSS) pertains to identifying supporting conditions for
promoting code contribution. This raises concerns about the ability
of FOSS communities to remain innovative based only on the
perspectives of developer-users. Preliminary research suggests
different open source business models may provide motivation to
support greater involvement of non-developer users. This research
focuses on understanding the relationship between business model
and supporting participation architectures, beyond users{\textquoteright} code
contributions, to enable user participation in design of the software. },
	url = {http://www.opensym.org/os2015/proceedings-files/c102-purcell.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/c102-purcell.pdf},
	author = {Michelle W. Purcell}
}
@inbook {1731,
	title = {Scaling and Internationalizing an Agile FOSS Project: Lessons Learned},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {13-22},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {This paper describes problems that arose with the scaling and internationalization of the open source project Catrobat. The problems we faced were the lack of a centralized user management, insufficient scaling of our communication channels, and the necessity to adapt agile development techniques to remote collaboration. To solve the problems we decided to use a mix of open source tools (Git, IRC, LDAP) and commercial solutions (Jira, Confluence, GitHub) because we believe that this mix best fits our needs. Other projects can benefit from the lessons we learned during the reorganization of our knowledge base and communication tools, as infrastructure changes can be very labor-intensive and time-consuming.},
	keywords = {Agile development, communication, Distributed software development, Documentation management, Internationalization, kanban, Scaling},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_2},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_2},
	author = {Fellhofer, Stephan and Harzl, Annemarie and Slany, Wolfgang},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {1715,
	title = {"Should we move to Stack Overflow?" Measuring the utility of social media for developer support},
	year = {2015},
	month = {05/2015},
	pages = {10pp},
	publisher = {IEEE},
	abstract = {Stack Overflow is an enormously popular question-and-answer web site intended for software developers to help each other with programming issues. Some software projects aimed at developers (for example, application programming interfaces, application engines, cloud services, development frameworks, and the like) are closing their self-supported developer discussion forums and mailing lists and instead directing developers to use special-purpose tags on Stack Overflow. The goals of this paper are to document the main reasons given for moving developer support to Stack Overflow, and then to collect and analyze data from a group of software projects that have done this, in order to show whether the expected quality of support was actually achieved. The analysis shows that for all four software projects in this study, two of the desired quality indicators, developer participation and response time, did show improvements on Stack Overflow as compared to mailing lists and forums. However, we also found several projects that moved back from Stack Overflow, despite achieving these desired improvements. The results of this study are applicable to a wide variety of software projects that provide developer support using social media.},
	keywords = {developer support, forums, mailing list, metrics, quality, social media, Stack Overflow, technical support},
	attachments = {https://flosshub.org/sites/flosshub.org/files/SEIP2015stackv2.pdf},
	author = {Squire, Megan}
}
@inbook {1737,
	title = {Smart Route Planning Using Open Data and Participatory Sensing},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {91-100},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Smart cities are not merely the infusion of technology into a city{\textquoteright}s infrastructure, but also require citizens interacting with their urban environment in a smart and informed manner. Transportation is key aspect of smart cities. In this paper, we present a smart route planning open-source system; SMART-GH utilizes open data and participatory sensing, where citizens actively participate in collecting data about the city in their daily environment, e.g., noise, air pollution, etc. SMART-GH then augments the routing logic with sensor data to answer queries such as {\textquoteleft}return the least noisy route{\textquoteright}. SMART-GH enables citizens to make smarter decisions about their daily commute, and subsequently improve their quality of life.
},
	keywords = {Open-data, open-source, Participatory sensing, Smart-city-routing},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_9},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nallur15.pdf},
	author = {Nallur, Vivek and Elgammal, Amal and Clarke, Siobh{\'a}n},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {1788,
	title = {Software Patents: A Replication Study},
	year = {2015},
	month = {08/2015},
	abstract = {Previous research has documented the legal and economic aspects
of software patents. To study the evolution in the granting of software
patents we reproduced and extended part of the empirical
study on software patents conducted by Bessen and Hunt. The
original study established a criteria to identify software patents,
and provided a look at the evolution of patents granted until 2002.
We present a simple approach to retrieve patents from the full text
database provided by the United States Patent and Trademark Of-
fice (USPTO), which is freely accessible. We also present the evolution
of software patents since the original study, and which we
also present separated by major technological firms. Our research
shows a continuous increase in the number of software patents
granted higher, both in number of patents granted (in absolute numbers)
and in proportion of overall patents (in relative terms). The
relevance of studying the evolution of software patents relies in
the challenges to find prior-art, either for practitioners looking for
patenting as well as for examiners evaluating granting a new patent.},
	url = {http://www.opensym.org/os2015/proceedings-files/p104-poo-caamano.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p104-poo-caamano.pdf},
	author = {Poo-Caama{\~n}o, Germ{\'a}n and Daniel M. German}
}
@article {1805,
	title = {Stigmergic coordination in FLOSS development teams: Integrating explicit and implicit mechanisms},
	journal = {Cognitive Systems Research},
	year = {2015},
	month = {12/2015},
	abstract = {The vast majority of literature on coordination in team-based projects has drawn on a conceptual separation between explicit (e.g. plans, feedbacks) and implicit coordination mechanisms (e.g. mental maps, shared knowledge). This analytical distinction presents some limitations in explaining how coordination is reached in organizations characterized by distributed teams, scarce face to face meetings and fuzzy and changing lines of authority, as in free/libre open source software (FLOSS) development.

Analyzing empirical illustrations from two FLOSS projects, we highlight the existence of a peculiar model, stigmergic coordination, which includes aspects of both implicit and explicit mechanisms. The work product itself (implicit) and the characteristics under which it is shared (explicit) play an under-appreciated role in helping software developers manage dependencies as they arise. We develop this argument beyond the existing literature by working with an existing coordination framework, considering the role that the codebase itself might play at each step. We also discuss the features and the practices to support stigmergic coordination in distributed teams, as well as recommendations for future research. {\textquotedblleft}Not everything that implicitly exists needs to be rendered explicit{\textquotedblright} (Sloterdijk, 2009, p. 3).},
	keywords = {Coordination mechanisms, distributed teams, FLOSS teams, Stigmergic coordination},
	issn = {13890417},
	doi = {10.1016/j.cogsys.2015.12.003},
	url = {http://www.sciencedirect.com/science/article/pii/S1389041715000339},
	attachments = {https://flosshub.org/sites/flosshub.org/files/COGSYS-RS-\%28HHS\%29-\%282015\%29-\%283\%29.pdf},
	author = {Bolici, Francesco and Howison, James and Kevin Crowston}
}
@proceedings {1711,
	title = {A Study of Demand-Driven Documentation in Two Open Source Projects},
	year = {2015},
	publisher = {IEEE},
	abstract = {We investigate how demand-driven documentation
is used by open source projects. Our study relies on questions
and answers (i.e., demand-driven documentation) posted to Stack
Overflow and focuses on two projects: Apache POI and Fennec
(Firefox for Android). We find that the demand-driven documentation
provided by respective community is of good quality and
contributions are made within an acceptable amount of time.
We conclude that demand-driven documentation can be suitable
as a primary information source if other resources accompany
it, e.g., websites. However, the suitability is closely related to
size and activity of the project{\textquoteright}s community. We also investigate
whether the type of project (e.g., API, application, product, etc.)
matters, and find that given the nature of a forum, projects
where the intended users are developers have larger and more
active communities and are thus better suited for demand-driven
documentation.},
	author = {Andersson, Jessica and Larsson, Sofia and Ericsson, Morgan and Wingkvist, Anna}
}
@inbook {1739,
	title = {Surveying the Adoption of FLOSS by Public Administration Local Organizations},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {114-123},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Background. The introduction of Open Source Software technologies in the Public Administration plays a key role in the spread of Open Source Software. The state of the art in the adoption of Open Source Software solutions in the Public Administration is not very well known even in areas like Lombardy, which is Italy{\textquoteright}s largest and most developed region.
Goal. The goal of the investigation documented in this paper is to obtain a clear picture about the introduction of Open Source Software technologies in the Public Administration, the obstacles to their adoption, and the willingness of stakeholders to proceed with their introduction.
Method. We carried out a qualitative and quantitative survey that was submitted to a representative part of the Public Administrations in Lombardy.
Results. The analysis of the qualitative and quantitative information shows that several Public Administrations are already using Open Source Software technologies, though not in all application areas. The savings are one frequently cited incentive to the adoption of Open Source Software. However, one obstacle is the fact that a comprehensive law on software in the Public Administration has not yet been approved.
Conclusions. Our analysis provides results that indicate a common understanding of incentives, obstacles, and opportunities for Open Source Software technologies in Public Administrations.},
	keywords = {FLOSS adoption, Italy, Public administrations, Survey},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_11},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_11},
	author = {Tosi, Davide and Lavazza, Luigi and Morasca, Sandro and Chiappa, Marco},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1736,
	title = {A Systematic Approach for Evaluating BPM Systems: Case Studies on Open Source and Proprietary Tools},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {81-90},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Business Process Management Systems (BPMS) provide support for modeling, developing, deploying, executing and evaluating business processes in an organization. Selecting a BPMS is not a trivial task, not only due to the many existing alternatives, both in the open source and proprietary realms, but also because it requires a thorough evaluation of its capabilities, contextualizing them in the organizational environment in which they will be used. In this paper we present a methodology to guide the systematic evaluation of BPMS that takes into account the specific needs of each organization. It provides a list of key characteristics of BPMS which are ranked by the organization and evaluated using test cases and quantitative criteria. We also present case studies of open source and proprietary BPMS evaluations following our proposal.
},
	keywords = {Business Process Management Systems (BPMS), Evaluation methodology, Open source and proprietary BPMS, Systematic approach},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_8},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_8},
	author = {Delgado, Andrea and Calegari, Daniel and Milanese, Pablo and Falcon, Renatta and Garc{\'\i}a, Esteban},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {1767,
	title = {Toward Reusing Code Changes},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Existing techniques have succeeded to help developers
implement new code. However, they are insufficient to help to
change existing code. Previous studies have proposed techniques
to support bug fixes but other kinds of code changes such
as function enhancements and refactorings are not supported
by them. In this paper, we propose a novel system that helps
developers change existing code. Unlike existing techniques, our
system can support any kinds of code changes if similar code
changes occurred in the past. Our research is still on very early
stage and we have not have any implementation or any prototype
yet. This paper introduces our research purpose, an outline of our
system, and how our system is different from existing techniques.},
	keywords = {apache},
	url = {http://sdl.ist.osaka-u.ac.jp/~higo/data/ICSE15-MSR-05-p052.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ICSE15-MSR-05-p052.pdf},
	author = {Higo, Yoshiki and Akio Ohtani and Shinpei Hayashi and Hata, Hideaki and Kusumoto Shinji}
}
@proceedings {1792,
	title = {Toward understanding new feature request systems as participation architectures for supporting open innovation },
	year = {2015},
	month = {08/2015},
	abstract = {Most research regarding innovation in open source software
communities pertains to identifying supporting conditions for
promoting code contribution as a way to innovate the software.
Instead, this paper seeks to identify social and technological
affordances of new feature request systems and their potential to
support open innovation through integration of peripheral
community members{\textquoteright} ideas for advancing the software. Initial
findings from the first of a planned study of multiple open source
software communities are presented to identify attributes of
effective participation architectures.},
	url = {http://www.opensym.org/os2015/proceedings-files/p202-purcell.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p202-purcell.pdf},
	author = {Michelle W. Purcell}
}
@booklet {1709,
	title = {Understanding and Supporting the Choice of an Appropriate Task to Start With In Open Source Software Communities },
	howpublished = {Hawaii International Conference on System Sciences 48},
	year = {2015},
	pages = {5299-5308},
	publisher = {IEEE},
	abstract = {Open Source Software (OSS) projects leverage the
contribution of outsiders. In fact, the sustainability of
many projects relies on retaining some of these
newcomers. Usually these communities do not
coordinate the work of the newcomers, who go to the
issue trackers and self-select a task to start with. We
found that {\textquotedblleft}finding a way to start{\textquotedblright} was reported as an
important issue by practitioners. To further investigate
this specific barrier, we conducted a qualitative
analysis with data obtained from semi-structured
interviews with 36 subjects from 14 different projects,
including newcomers and experienced members. We
used procedures of Grounded Theory {\textendash} open and axial
coding {\textendash} to analyze the data. We found that newcomers
are not confident enough to choose their initial task
and they need information about the tasks or direction
from the community to support choosing a task more
suitable for them. We also present a set of strategies
identified in the literature, interviews, and state-of-the practice
that can provide newcomers with such
information, enabling them to be more confident when
choosing their first tasks and collaborate with the
community. },
	keywords = {coordination, joining process, new developer, newcomers, onboarding, open source software, task selection},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HICSS-48_present.pdf},
	author = {Steinmacher, Igor and Conte, Tayana and Gerosa, MarcoAur{\'e}lio}
}
@proceedings {export:232407,
	title = {The Uniqueness of Changes: Characteristics and Applications},
	year = {2015},
	month = {05/2015},
	abstract = {Changes in software development come in many forms. Some changes are frequent, idiomatic, or repetitive (e.g. adding checks for nulls or logging important values) while others are unique. We hypothesize that unique changes are different from the more common similar (or non-unique) changes in important ways; they may require more expertise or represent code that is more complex or prone to mistakes. As such, these changes are worthy of study. In this paper, we present a definition of unique changes and provide a method for identifying them in software project history. Based on the results of applying our technique on the Linux kernel and two large projects at Microsoft, we present an empirical study of unique changes. We explore how prevalent unique changes are and characterize where they occur along the architecture of the project. We further investigate developers{\textquoteright} contribution towards uniqueness of changes. We also describe potential applications of leveraging the uniqueness of change and implement two such applications, evaluating the risk of changes based on uniqueness and providing change recommendations for non-unique changes.},
	keywords = {linux kernel},
	url = {http://research.microsoft.com/apps/pubs/default.aspx?id=232407},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MSR-TR-2014-149.pdf},
	author = {Ray, Baishakhi and Meiyappan Nagappan and Christian Bird and Nachiappan Nagappan and Zimmermann, Thomas}
}
@proceedings {1754,
	title = {Unveiling Exception Handling Bug Hazards in Android based on GitHub and Google Code Issues},
	year = {2015},
	month = {05/2015},
	abstract = {This paper reports on a study mining the exception
stack traces included in 159,048 issues reported on Android
projects hosted in GitHub (482 projects) and Google Code (157
projects). The goal of this study is to investigate whether stack
trace information can reveal bug hazards related to exception
handling code that may lead to a decrease in application robustness.
Overall 6,005 exception stack traces were extracted,
and subjected to source code and bytecode analysis. The outcomes
of this study include the identification of the following
bug hazards: (i) unexpected cross-type exception wrappings (for
instance, trying to handle an instance of OutOfMemoryError
{\textquotedblleft}hidden{\textquotedblright} in a checked exception) which can make the exceptionrelated
code more complex and negatively impact the application
robustness; (ii) undocumented runtime exceptions thrown by both
the Android platform and third party libraries; and (iii) undocumented
checked exceptions thrown by the Android Platform.
Such undocumented exceptions make difficult, and most of the
times infeasible for the client code to protect against {\textquotedblleft}unforeseen{\textquotedblright}
situations that may happen while calling third-party code. This
study provides further insights on such bug hazards and the
robustness threats they impose to Android apps as well as to
other systems based on the Java exception model.},
	keywords = {github, google code},
	url = {http://www.gousios.gr/pub/android-stacks.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/android-stacks.pdf},
	author = {Roberta Coelho and Lucas Almeida and Gousios, Georgios and van Deursen, Arie}
}
@conference {zanjani2015developer,
	title = {Using Developer-Interaction Trails to Triage Change Requests},
	booktitle = {12th Working Conference on Mining Software Repositories (MSR 2015)},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {The paper presents an approach, namely iHDev, to recommend developers who are most likely to implement incoming change requests. The basic premise of iHDev is that the developers who interacted with the source code relevant to a given change request are most likely to best assist with its resolution. A machine-learning technique is first used to locate source-code entities relevant to the textual description of a given change request. iHDev then mines interaction trails (i.e., Mylyn sessions) associated with these source-code entities to recommend a ranked list of developers. iHDev integrates the interaction trails in a unique way to perform its task, which was not investigated previously. 
An empirical study on open source systems Mylyn and Eclipse Project was conducted to assess the effectiveness of iHDev. A number of change requests were used in the evaluated benchmark. Recall for top one to five recommended developers and Mean Reciprocal Rank (MRR) values are reported. Furthermore, a comparative study with two previous approaches that use commit histories and/or the source-code authorship information for developer recommendation was performed. Results show that iHDev could provide a recall gain of up to 127.27\% with equivalent or improved MRR values by up to 112.5\%.},
	url = {http://www.cabird.com/wp/zanjani2015developer/},
	attachments = {https://flosshub.org/sites/flosshub.org/files/zanjani2015developer.pdf},
	author = {Motahareh Bahrami Zanjani and Kagdi, Huzefa and Christian Bird}
}
@proceedings {1786,
	title = {Utilization and Development Contribution of Open Source Software in Japanese IT Companies: An Exploratory Study of the Effect on Business Growth (2nd report based on 2014 survey)},
	year = {2015},
	month = {08/2015},
	abstract = {The usage of Open Source Software (OSS) has been extended in a
wide range of business fields not only IT industries. Behind this
current situation, there are tremendous inputs by the volunteer
engineers in the development communities. In this series of
studies, we have conducted questionnaire survey to Japanese IT
companies in 2012 and 2013, and then analyzed the relation
between OSS utilization and development contribution, and how
these affect the business growth. Our study revealed that Japanese
IT companies are rather free riders of OSS, the volume of
development contributions are far less than that of utilization.
From our previous studies, it was anticipated that some OSSrelated
factors were affecting the business growth; however, clear
evidence has not been found. In autumn 2014, we conducted the
questionnaire survey for the third time and this paper presents the
survey results as the second report of the continued research. We
constructed the simplified Logistic Model to investigate the
influential factors on business growth. However, no clear
evidence was found as the same as the previous study. In
summary, we conclude that there are some form of relationships
between OSS utilization and development contribution, but these
are not the determinant factors on the business growth in the
Japanese IT companies at present. },
	url = {http://www.opensym.org/os2015/proceedings-files/p102-tansho.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p102-tansho.pdf},
	author = {Tansho, Terutaka and Noda, Tetsuo}
}
@inbook {1742,
	title = {On the Variability of the BSD and MIT Licenses},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {146-156},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {The MIT/X11 and the BSD are two of the most important family of Free and Open Source (FOSS) licenses. Because these licenses are to be inserted into the files that use it, and because they are expected to be changed by those who use them, their text has suffered alterations over time. Some of this variability is the result of licenses containing template fields which allow the license to be customized to include information such as the copyright holder name. Other variability can be attributed to changes in spelling, punctuation, and adding or removing conditions. This study empirically evaluated the extent that the BSD and MIT/X11 family of licenses are varied, and the manner and frequency in which license texts vary from the original definition. The study found that the BSD family has little variability, with a significant proportion fitting the common standard. The MIT/X11 family of licenses exhibited significantly more variation, with a higher propensity to customize the license text. In addition, the MIT/X11 license has spawned several specialized variants which likely constitute different legal meanings. Based on these findings, recommendations are proposed on what variability needs to be accommodated by the Software Package Data Exchange (SPDX) which is in the process of standardizing the allowed variability of both licenses.
},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_14},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_14},
	author = {Maryka, Trevor and German, DanielM. and Poo-Caama{\~n}o, Germ{\'a}n},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@article {1793,
	title = {Volunteer Management in Open Source Communities},
	year = {2015},
	month = {08/2015},
	abstract = {Open source community management is largely ad-hoc and
relies on practitioner guides. Yet there is a great deal of information
about volunteer management in the general volunteering
literature, open source literature and general volunteering
guides which could be relevant to open source communities
if it were categorized and validated. Bringing these
different sources of information together also reveals gaps in
our understanding of volunteer management in open source
which I hope to address.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/c101-barcomb.pdf},
	author = {Barcomb, Ann}
}
@proceedings {1766,
	title = {Wait For It: Determinants of Pull Request Evaluation Latency on GitHub},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The pull-based development model, enabled by git
and popularised by collaborative coding platforms like BitBucket,
Gitorius, and GitHub, is widely used in distributed software
teams. While this model lowers the barrier to entry for potential
contributors (since anyone can submit pull requests to any repository),
it also increases the burden on integrators (i.e., members
of a project{\textquoteright}s core team, responsible for evaluating the proposed
changes and integrating them into the main development line),
who struggle to keep up with the volume of incoming pull
requests. In this paper we report on a quantitative study that tries
to resolve which factors affect pull request evaluation latency
in GitHub. Using regression modeling on data extracted from
a sample of GitHub projects using the Travis-CI continuous
integration service, we find that latency is a complex issue,
requiring many independent variables to explain adequately.},
	url = {https://bvasiles.github.io/papers/msr15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr15.pdf},
	author = {Yu, Yue and Wang, Huaimin and Filkov, Vladimir and Devanbu, Premkumar and Vasilescu, Bogdan}
}
@proceedings {1775,
	title = {What is the Gist? Understanding the Use of Public Gists on GitHub},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	keywords = {gist, github},
	author = {Weiliang Wang and Poo-Caama{\~n}o, Germ{\'a}n and Evan Wilde and German, Daniel}
}
@article {1686,
	title = {Why and How Should Open Source Projects Adopt Time-Based Releases?},
	journal = {IEEE Software, 32(2)},
	year = {2015},
	abstract = {Traditional release strategies have a number of associated problems, which can be overcome by time-based release management. We present findings from interviews with key members of seven prominent volunteer-based open source projects, all of which have adopted a time-based release strategy. We discuss the importance of release planning, the numerous challenges that can result from a lack of such planning, and the benefits of time-based releases. Finally, we discuss how an open source project can adopt a time-based release strategy.},
	url = {https://www.researchgate.net/publication/268815678_Why_and_How_Should_Open_Source_Projects_Adopt_Time-Based_Releases},
	author = {Martin Michlmayr and Fitzgerald, Brian}
}
@proceedings {1752,
	title = {Why Power Laws? An Explanation from Fine-Grained Code Changes},
	year = {2015},
	note = {"The data used in this section come from four open source Java projects. We used CVSANALY to collect data from their Git repositories."},
	abstract = {Throughout the years, empirical studies have found
power law distributions in various measures across many software
systems. However, surprisingly little is known about how
they are produced. What causes these power law distributions?
We offer an explanation from the perspective of fine-grained
code changes. A model based on preferential attachment and selforganized
criticality is proposed to simulate software evolution.
The experiment shows that the simulation is able to render power
law distributions out of fine-grained code changes, suggesting
preferential attachment and self-organized criticality are the
underlying mechanism causing the power law distributions in
software systems.},
	keywords = {Apache Maven, cvsanaly, eclipse, git, Google Guice, java, jedit, open source},
	url = {https://users.soe.ucsc.edu/~linzhp/msr2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015.pdf},
	author = {Zhongpeng Lin and Jim Whitehead}
}
@proceedings {1768,
	title = {Will they like this? Evaluating Code Contributions With Language Models},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Popular open-source software projects receive and
review contributions from a diverse array of developers, many
of whom have little to no prior involvement with the project. A
recent survey reported that reviewers consider conformance to
the project{\textquoteright}s code style to be one of the top priorities when evaluating
code contributions on Github. We propose to quantitatively
evaluate the existence and effects of this phenomenon. To this aim
we use language models, which were shown to accurately capture
stylistic aspects of code. We find that rejected changesets do
contain code significantly less similar to the project than accepted
ones; furthermore, the less similar changesets are more likely
to be subject to thorough review. Armed with these results we
further investigate whether new contributors learn to conform to
the project style and find that experience is positively correlated
with conformance to the project{\textquoteright}s code style.},
	url = {http://sback.it/publications/msr2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015_0.pdf},
	author = {Vincent J. Hellendoorn and Premkumar T. Devanbu and Bacchelli, Alberto}
}
@inbook {1596,
	title = {Adapting SCRUM to the Italian Army: Methods and (Open) Tools},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {61-69},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Many software-related technologies, including software development methodologies, quality models, etc. have been developed due to the huge software needs of the Department of Defense (DoD) of the United States. Therefore, it is not surprising that the DoD is promoting open source software and agile approaches into the development processes of the defense contractors. The quality of many open source product has been demonstrated to be comparable to the close source ones and in many cases even higher and the effectiveness of agile approaches has been demonstrated in many industrial settings. Moreover, the availability of the source code makes open source products attractive for obvious reasons (e.g., security, long term maintenance, etc.). Following this trend, also the Italian Army has started using open source software and promotes its usage into the development processes of its contractors, also promoting agile approaches in many contexts focusing on the SCRUM methodology. This paper provides an overview of the SCRUM development process adopted by the Italian Army for the development of software systems using open source technologies.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_7},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_7},
	author = {Cotugno, FrancoRaffaele and Messina, Angelo},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1614,
	title = {The Agile Management of Development Projects of Software Combining Scrum, Kanban and Expert Consultation},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {176-180},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

At the University of Informatics Sciences (UCI), Havana, Cuba, it is found The Center of Free Solutions of Software (CESOL) who has an informatic project named {\textquotedblleft}Auditing of Source Code{\textquotedblright} (ACF). This project has as objective to develop an open source software solution to auditing the source code of several software solutions with an agile projects management. In the present investigation have been showed the experiences obtained in the mixed application of two methods of agile projects management; Kanban and Scrum, together with the method Judgment of Expert, during the stage of construction of the lifecycle of ACF, when it is was performed a quality auditing by specialists of the CALISOFT company. In the auditing were detected several errors and to resolve them was necessary to estimate efforts, time and to revalue the lifecycle of the project. Moreover, the investigation show how this method can be used as a guide for young project managers for a correct planification and how can be used as a personal organizational method.
},
	keywords = {Agile management of projects, kanban, scrum},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_25},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_25},
	author = {Febles Parker, MichelEvaristo and Monte, YusleydiFern{\'a}ndez},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Matragkas:2014:ABO:2597073.2597119,
	title = {Analysing the {\textquoteright}Biodiversity{\textquoteright} of Open Source Ecosystems: The GitHub Case},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {356{\textendash}359},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In nature the diversity of species and genes in ecological communities affects the functioning of these communities. Biologists have found out that more diverse communities appear to be more productive than less diverse communities. Moreover such communities appear to be more stable in the face of perturbations. In this paper, we draw the analogy between ecological communities and Open Source Software (OSS) ecosystems, and we investigate the diversity and structure of OSS communities. To address this question we use the MSR 2014 challenge dataset, which includes data from the top-10 software projects for the top programming languages on GitHub. Our findings show that OSS communities on GitHub consist of 3 types of users (core developers, active users, passive users). Moreover, we show that the percentage of core developers and active users does not change as the project grows and that the majority of members of large projects are passive users.
},
	keywords = {Data and knowledge visualization, data mining, mining challenge, msr challenge},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597119},
	url = {http://doi.acm.org/10.1145/2597073.2597119},
	author = {Matragkas, Nicholas and Williams, James R. and Kolovos, Dimitris S. and Paige, Richard F.}
}
@inbook {1595,
	title = {Analyzing the Relationship between the License of Packages and Their Files in Free and Open Source Software},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {51-60},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {Free and Open Source Software (FOSS) is widely reused today. To reuse FOSS one must accept the conditions imposed by the software license under which the component is made available. This is complicated by the fact that often FOSS packages contain files from many licenses. In this paper we analyze the source code of packages in the Fedora Core Linux distribution with the goal of discovering the relationship between the license of a source package, and the license of the files it contains. For this purpose we create license inclusion graphs. Our results show that more modern reciprocal licenses such as the General Public License v3 tend to include files of less licenses than its previous versions, and that packages under an Apache License tend to contain only files under the same license.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_6},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_6},
	author = {Manabe, Yuki and German, DanielM. and Inoue, Katsuro},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1597,
	title = {Applying the Submission Multiple Tier (SMT) Matrix to Detect Impact on Developer Interest on Open Source Project Survivability},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {70-75},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

There is a significant relationship between project activity and developer interest on Open Source (OS) projects. Total project activity submission count number can be an indicator for gauging developer interest. The higher the project activity submission of a project is, the larger developer interest in a project. My paper proposed that applying a Submission Multiple Tier (SMT) matrix can detect the impact of developer interest on project activity. Results showed more volume of OS projects with low project activity than high. Activity submission results also showed that developers are more likely to review than correct projects, with the first priority to find and fix bugs. Further research is needed to determine the impact of project activity type on developer motivation to contribute, participate and support OS projects.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_8},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_8},
	author = {Chua, BeeBee},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1625,
	title = {Automation of Agricultural Irrigation System with Open Source},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {232-233},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

In this present job, we seek to develop a prototype of an automated agricultural irrigation system, monitored and controlled remotely. For that, we will use inexpensive tools, flexibility and support such as Arduino, XBee and Android. Arduino and XBee, will be responsible of the automating the system. Android will achieve the remote monitoring and control from anywhere in the world where there is cellular service and Internet. In this way we can give the farmer the comfort and security that he don{\textquoteright}t get with a manually controlled system.
},
	keywords = {ADK, android, Arduino, XBee},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_36},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_36},
	author = {Quezada, BladimirJaimeP{\'e}rez and Fern{\'a}ndez, Javier},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1610,
	title = {Barriers Faced by Newcomers to Open Source Projects: A Systematic Review},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {153-163},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {
To remain sustainable, some open source projects need a constant influx of new volunteers, or newcomers. However, the newcomers face different kinds of problems when onboarding to a project. In this paper we present the results of a systematic literature review aiming at identifying the barriers that a newcomer can face when contributing to an Open Source Software project. We identified and analyzed 21 studies that evidence this kind of problem. As a result we provide a hierarchical model that relies on five categories of barriers: finding a way to start, social interactions, code issues, documentation problems and newcomers{\textquoteright} knowledge. The most evidenced barriers are newcomers{\textquoteright} previous technical skills, receiving response from community, centrality of social contacts, and finding the appropriate way to start contributing. This classification provides a baseline for further researches related to newcomers onboarding.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_21},
	url = {http://flosscoach.com/publications/IST2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/IST2015.pdf},
	author = {Steinmacher, Igor and Silva, MarcoAur{\'e}lioGraciotto and Gerosa, MarcoAur{\'e}lio},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@proceedings {1573,
	title = {"A bit of code": How the Stack Overflow Community Creates Quality Postings},
	year = {2014},
	month = {01/2014},
	pages = {1425-1434},
	publisher = {IEEE Computer Society},
	abstract = {The Stack Overflow web site is an online community where programmers can ask and answer one another{\textquoteright}s questions, earning points and badges. The site offers guidance in the form of a Frequently Asked Questions (FAQ), beginning with "What kind of questions can I ask here?" The answer explains that "the best Stack Overflow questions have a bit of source code in them". This paper explores the role of source code and non-source code text on Stack Overflow in both questions and answers. The primary contribution of this paper is to provide a more detailed understanding of whether the presence of source code (and how much) actually will produce the "best" Stack Overflow questions or answers. A second contribution of this paper is to determine how the non-code portions of the text might also contribute the "best" Stack Overflow postings.  },
	keywords = {COLLABORATION, collaborative development, data mining, developer network, knowledge collaboration, open content, text mining},
	doi = {http://dx.doi.org/10.1109/HICSS.2014.185},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hicssSMFinalWatermark.pdf},
	author = {Squire, Megan and Funkhouser, Christian}
}
@inbook {1624,
	title = {Book Locator: Books Manager},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {230-231},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

After performing a study of digital books organizing tools, it{\textquoteright}s observed that these don{\textquoteright}t count on a multi platform integration, and those who do, don{\textquoteright}t count on the elements pursued in the investigation. It is decided then to proceed to the implementation of a book organizer software, taking an initial requirements list from the studied tools, following the guidelines of the collaborative and open source development. It has been developed to its version 4.1, which after going through different development processes, detecting mistakes and adding new functionalities that join to the requirements list, it{\textquoteright}s fully functional.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_35},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_35},
	author = {Garc{\'\i}a Rivas, Dairelys},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Mitropoulos:2014:BCM:2597073.2597123,
	title = {The Bug Catalog of the Maven Ecosystem},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {372{\textendash}375},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Examining software ecosystems can provide the research community with data regarding artifacts, processes, and communities. We present a dataset obtained from the Maven central repository ecosystem (approximately 265GB of data) by statically analyzing the repository to detect potential software bugs. For our analysis we used FindBugs, a tool that examines Java bytecode to detect numerous types of bugs. The dataset contains the metrics results that FindBugs reports for every project version (a JAR) included in the ecosystem. For every version we also stored specific metadata such as the JAR{\textquoteright}s size, its dependencies and others. Our dataset can be used to produce interesting research results, as we show in specific examples.
},
	keywords = {findbugs, Maven Repository, msr data showcase, Software Bugs},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597123},
	url = {http://doi.acm.org/10.1145/2597073.2597123},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mitro.pdf},
	author = {Mitropoulos, Dimitris and Vassilios Karakoidas and Louridas, Panos and Gousios, Georgios and Diomidis Spinellis}
}
@inbook {1619,
	title = {The Census of the Brazilian Open-Source Community},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {202-211},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

During a long time, software engineering research has been trying to better understand open-source communities and uncover two fundamental questions: (i) who are the contributors and (i) why they contribute. Most of these researches focus on well-known OSS projects, but little is known about the OSS movement in emerging countries. In this paper, we attempt to fill this gap by presenting a picture of the Brazilian open-source contributor. To achieve this goal, we examined activities from more than 12,400 programmers on Github, during the period of a year. Subsequently, we correlate our findings with a survey that was answered by more than 1,000 active contributors. Our results show that exists an OSS trend in Brazil: most part of the contributors are active, performing around 30 contributions per year, and they contribute to OSS basically by altruism.
},
	keywords = {Brazilian OSS Community, github, OSS},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_30},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_30},
	author = {Pinto, Gustavo and Kamei, Fernando},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {ValdiviaGarcia:2014:CPB:2597073.2597099,
	title = {Characterizing and Predicting Blocking Bugs in Open Source Projects},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {72{\textendash}81},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {As software becomes increasingly important, its quality becomes an increasingly important issue. Therefore, prior work focused on software quality and proposed many prediction models to identify the location of software bugs, to estimate their fixing-time, etc. However, one special type of severe bugs is blocking bugs. Blocking bugs are software bugs that prevent other bugs from being fixed. These blocking bugs may increase maintenance costs, reduce overall quality and delay the release of the software systems.

In this paper, we study blocking-bugs in six open source projects and propose a model to predict them. Our goal is to help developers identify these blocking bugs early on. We collect the bug reports from the bug tracking systems of the projects, then we obtain 14 different factors related to, for example, the textual description of the bug, the location the bug is found in and the people involved with the bug. Based on these factors we build decision trees for each project to predict whether a bug will be a blocking bug or not. Then, we analyze these decision trees in order to determine which factors best indicate these blocking bugs. Our results show that our prediction models achieve F-measures of 15-42\%, which is a two- to four-fold improvement over the baseline random predictors. We also find that the most important factors in determining blocking bugs are the comment text, comment size, the number of developers in the CC list of the bug report and the reporter{\textquoteright}s experience. Our analysis shows that our models reduce the median time to identify a blocking bug by 3-18 days.},
	keywords = {Code Metrics, Post-release Defects, Process Metrics},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597099},
	url = {http://doi.acm.org/10.1145/2597073.2597099},
	attachments = {https://flosshub.org/sites/flosshub.org/files/garcia.pdf},
	author = {Valdivia Garcia, Harold and Shihab, Emad}
}
@conference {Krutz:2014:CCO:2597073.2597127,
	title = {A Code Clone Oracle},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {388{\textendash}391},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Code clones are functionally equivalent code segments. Detecting code clones is important for determining bugs, fixes and software reuse. Code clone detection is also essential for developing fast and precise code search algorithms. How- ever, the challenge of such research is to evaluate that the clones detected are indeed functionally equivalent, consider- ing the majority of clones are not textual or even syntactically identical. The goal of this work is to generate a set of method level code clones with a high confidence to help to evaluate future code clone detection and code search tools to evaluate their techniques. We selected three open source programs, Apache, Python and PostgreSQL, and randomly sampled a total of 1536 function pairs. To confirm whether or not these function pairs indicate a clone and what types of clones they belong to, we recruited three experts who have experience in code clone research and four students who have experience in programming for manual inspection. For confidence of the data, the experts consulted multiple code clone detection tools to make the consensus. To assist manual inspection, we built a tool to automatically load function pairs of interest and record the manual inspection results. We found that none of the 66 pairs are textual identical type- 1 clones, and 9 pairs are type-4 clones. Our data is available at: http://phd.gccis.rit.edu/weile/data/cloneoracle/.
},
	keywords = {clone, Clone Oracle, Code Clone Detection, msr data showcase, software engineering},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597127},
	url = {http://doi.acm.org/10.1145/2597073.2597127},
	attachments = {https://flosshub.org/sites/flosshub.org/files/clone_oracle.pdf},
	author = {Krutz, Daniel E. and Le, Wei}
}
@book {1591,
	title = {Code Review Analytics: WebKit as Case Study},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Mobile Open Source Technologies. 10th IFIP WG 2.13 International Conference on Open Source Systems, OSS 2014, San Jos{\'e}, Costa Rica, May 6-9, 2014. Proceedings},
	volume = {427},
	year = {2014},
	pages = {1 - 10},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {During the last years, most of the large free / open source software projects have included code review as an usual, or even mandatory practice for changes to their code. In many cases it is implemented as a process in which a developer proposing some change needs to ask for a review by another developer before it can enter the code base. Code reviews, therefore, become a critical process for the project, which could cause delays in contributions being accepted, and risk to become a bottleneck if not enough reviewers are available. In this paper we present a methodology designed to analyze the code review process, to determine its main characteristics and parameters, and to detect potential problems with it. We also present how we have applied this methodology to the WebKit project, learning about the main characteristics of how code review works in their case.},
	isbn = {978-3-642-55128-4},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-55128-4_1},
	author = {Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Izquierdo-Cort{\'a}zar, Daniel and Gregorio Robles and Mario Gallegos},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, Anthony I.}
}
@conference {Aggarwal:2014:CPD:2597073.2597120,
	title = {Co-evolution of Project Documentation and Popularity Within Github},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {360{\textendash}363},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Github is a very popular collaborative software-development platform that provides typical source-code management and issue tracking features augmented by strong social-networking features such as following developers and watching projects. These features help "spread the word" about individuals and projects, building the reputation of the former and increasing the popularity of the latter. In this paper, we investigate the relation between project popularity and regular, consistent documentation updates. We found strong indicators that consistently popular projects exhibited consistent documentation effort and that this effort tended to attract more documentation collaborators. We also found that frameworks required more documentation effort than libraries to achieve similar adoption success, especially in the initial phase.
},
	keywords = {Cross Correlation, Documentation Change, mining challenge, msr challenge, popularity},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597120},
	url = {http://doi.acm.org/10.1145/2597073.2597120},
	author = {Aggarwal, Karan and Hindle, Abram and Stroulia, Eleni}
}
@conference {Tymchuk:2014:COP:2597073.2597093,
	title = {Collaboration in Open-source Projects: Myth or Reality?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {304{\textendash}307},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {One of the fundamental principles of open-source projects is that they foster collaboration among developers, disregarding their geographical location or personal background. When it comes to software repositories collaboration is a rather ephemeral phenomenon which lacks a clear definition, and it must therefore be mined and modeled. This throws up the question whether what is mined actually maps to reality.

In this paper we investigate collaboration by modeling it using a number of diverse approaches that we then compare to a ground truth obtained by surveying a substantial set of developers of the Pharo open-source community. Our findings indicate that the notion of collaboration must be revisited, as it is undermined by a number of factors that are often tackled in imprecise ways or not taken into account at all.},
	keywords = {COLLABORATION, Software ecosystems},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597093},
	url = {http://doi.acm.org/10.1145/2597073.2597093},
	author = {Tymchuk, Yuriy and Mocci, Andrea and Lanza, Michele}
}
@article {9400325220140301,
	title = {COLLABORATION THROUGH OPEN SUPERPOSITION: A THEORY OF THE OPEN SOURCE WAY.},
	journal = {MIS Quarterly},
	volume = {38},
	number = {1},
	year = {2014},
	pages = {29 - A9},
	abstract = {This paper develops and illustrates the theory of collaboration through open superposition: the process of depositing motivationally independent layers of work on top of each other over time. The theory is developed in a study of community-based free and open source software (FLOSS) development, through a research arc of discovery (participant observation), replication (two archival case studies), and theorization. The theory explains two key findings: (1) the overwhelming majority of work is accomplished with only a single programmer working on any one task, and (2) tasks that appear too large for any one individual are more likely to be deferred until they are easier rather than being undertaken through structured team work. Moreover, the theory explains how working through open superposition can lead to the discovery of a work breakdown that results in complex, functionally interdependent, work being accomplished without crippling search costs. We identify a set of socio-technical},
	keywords = {COLLABORATION, COMPUTER programmers, COMPUTER programming, COMPUTER software, coordination, FREEWARE (Computer software), INFORMATION storage \& retrieval systems, open source software, research, socio-technical system},
	issn = {02767783},
	author = {Howison, James and Kevin Crowston}
}
@inbook {1606,
	title = {Considerations Regarding the Creation of a Post-graduate Master{\textquoteright}s Degree in Free Software},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {123-132},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Free software has gained importance over the last few years, and can be found in almost any sphere in which {\textquoteleft}software processes{\textquoteright} are important. However, even when universities and higher education establishments include subjects concerning free programming and technologies in their curriculums, their graduates tend to attain limited technological, organisational and philosophical knowledge that limits them as regards their participation in, management and development of free software projects. This gap in skills and knowledge has recently led to a series of post-graduate studies whose objective is to offer students the possibility of acquiring competencies that will allow them to become experts in free software. This paper presents a study concerning the offers for post-graduate studies in free software that currently exist, with the intention of creating similar post-graduate studies in Ecuador.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_17},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_17},
	author = {Montes Le{\'o}n, SergioRa{\'u}l and Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}sM. and S{\'a}nchez C., LuisE.},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@proceedings {1685,
	title = {Continuous integration in a social-coding world: Empirical evidence from GitHub},
	year = {2014},
	pages = {5 pages},
	abstract = {Continuous integration is a software engineering practice of frequently merging all developer working copies with a shared main branch, e.g., several times a day.
With the advent of GITHUB, a platform well known for its {\textquotedblleft}social coding{\textquotedblright} features that aid collaboration and sharing, and currently the largest code host in the open source world, collaborative software development has never been more prominent. In GITHUB development one can distinguish between two types of developer contributions to a project: direct ones, coming from a typically small group of developers with write access to the main project repository, and indirect ones, coming from developers who fork the main repository, update their copies locally, and submit pull requests for review and merger.
In this paper we explore how GITHUB developers use continuous integration as well as whether the contribution type (direct versus indirect) and different project characteristics (e.g., main programming language, or project age) are associated with the success of the automatic builds.},
	keywords = {github},
	url = {http://conferences.computer.org/icsme/2014/papers/6146a401.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ICSME2014ERA.pdf},
	author = {Vasilescu, Bogdan and Serebrenik, Alexander and Schuylenberg, Stef and Wulms, Jules and Brand, Mark G.J.}
}
@inbook {1605,
	title = {Crafting a Systematic Literature Review on Open-Source Platforms},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {113-122},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

This working paper unveils the crafting of a systematic literature review on open-source platforms. The high-competitive mobile devices market, where several players such as Apple, Google, Nokia and Microsoft run a platforms- war with constant shifts in their technological strategies, is gaining increasing attention from scholars. It matters, then, to review previous literature on past platforms-wars, such as the ones from the PC and game-console industries, and assess its implications to the current mobile devices platforms-war. The paper starts by justifying the purpose and rationale behind this literature review on open-source platforms. The concepts of open-source software and computer-based platforms were then discussed both individually and in unison, in order to clarify the core-concept of {\textquotedblleft}open-source platform{\textquotedblright} that guides this literature review. The detailed design of the employed methodological strategy is then presented as the central part of this paper. The paper concludes with preliminary findings organizing previous literature on open-source platforms for the purpose of guiding future research in this area.
},
	keywords = {Ecosystems, FLOSS, open-source, Platforms, R\&D Management},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_16},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_16},
	author = {Teixeira, Jose and Baiyere, Abayomi},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {1694,
	title = {Cream of the crop},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {In open content communities like Wikipedia and StackOverflow and in open source software projects, a small proportion of users produce a majority of the content and take on much of the required community maintenance work. Understanding this class of users is crucial to creating and sustaining healthy communities. We carried out a mixed-method study of core contributors to the Cyclopath geographic wiki and bicycle routing web site. We present our findings and organize our discussion using concepts from activity theory. We found that the Cyclopath core contributors aren{\textquoteright}t the dedicated cyclists and that the characteristics of the community shape the site, the rules, and the tools for contributing. Additionally, we found that numerous aspects about the surrounding ecology of related systems and communities may help to shape how the site functions and views itself. We draw implications for future research and design from these findings.
},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641609},
	author = {Katherine Panciera and Mikhil Masli and Loren Terveen}
}
@inbook {1620,
	title = {Cuban GNU/Linux Nova Distribution for Server Computers},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {212-215},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

This article presents the novelties offered by the new version of GNU / Linux Nova distribution in its server edition, exposing the new features such as network attached storage, distributed files system, charge balance for PostgreSQL database servers and thin clients, as well as the basic features of a standard server. All these developments are obtained from the integration with the server management platform Zentyal designed to facilitate the work of the end users of the variant of this Cuban distribution.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_31},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_31},
	author = {Rosales Rosa, Eugenio and Fuentes Rodr{\'\i}guez, JuanManuel and F{\'\i}rvida Don{\'e}stevez, AbelAlfonso and Garc{\'\i}a Rivas, Dairelys},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Saini:2014:DMA:2597073.2597134,
	title = {A Dataset for Maven Artifacts and Bug Patterns Found in Them},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {416{\textendash}419},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper, we present data downloaded from Maven, one of the most popular component repositories. The data includes the binaries of 186,392 components, along with source code for 161,025. We identify and organize these components into groups where each group contains all the versions of a library. In order to asses the quality of these components, we make available report generated by the FindBugs tool on 64,574 components. The information is also made available in the form of a database which stores total number, type, and priority of bug patterns found in each component, along with its defect density. We also describe how this dataset can be useful in software engineering research.
},
	keywords = {Empirical Research, Empirical software engineering, findbugs, maven, software quality},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597134},
	url = {http://doi.acm.org/10.1145/2597073.2597134},
	author = {Saini, Vaibhav and Sajnani, Hitesh and Ossher, Joel and Lopes, Cristina V.}
}
@conference {Gousios:2014:DPD:2597073.2597122,
	title = {A Dataset for Pull-based Development Research},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {368{\textendash}371},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Pull requests form a new method for collaborating in distributed software development. To study the pull request distributed development model, we constructed a dataset of almost 900 projects and 350,000 pull requests, including some of the largest users of pull requests on Github. In this paper, we describe how the project selection was done, we analyze the selected features and present a machine learning tool set for the R statistics environment.
},
	keywords = {Distributed software development, Empirical software engineering, msr data showcase, pull request, pull-based development},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597122},
	url = {http://doi.acm.org/10.1145/2597073.2597122},
	attachments = {https://flosshub.org/sites/flosshub.org/files/pullreqs-dataset.pdf},
	author = {Gousios, Georgios and Zaidman, Andy}
}
@conference {Passos:2014:DFA:2597073.2597124,
	title = {A Dataset of Feature Additions and Feature Removals from the Linux Kernel},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {376{\textendash}379},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {This paper describes a dataset of feature additions and removals in the Linux kernel evolution history, spanning over seven years of kernel development. Features, in this context, denote configurable system options that users select when creating customized kernel images. The provided dataset is the largest corpus we are aware of capturing feature additions and removals, allowing researchers to assess the kernel evolution from a feature-oriented point-of-view. Furthermore, the dataset can be used to better understand how features evolve over time, and how different artifacts change as a result. One particular use of the dataset is to provide a real-world case to assess existing support for feature traceability and evolution. In this paper, we detail the dataset extraction process, the underlying database schema, and example queries. The dataset is directly available at our Bitbucket repository: https://bitbucket.org/lpassos/kconfigdb
},
	keywords = {evolution, linux, msr data showcase, Traceability, Version Control History},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597124},
	url = {http://doi.acm.org/10.1145/2597073.2597124},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kernel.pdf},
	author = {Passos, Leonardo and Czarnecki, Krzysztof}
}
@conference {Brunet:2014:DDD:2597073.2597115,
	title = {Do Developers Discuss Design?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {340{\textendash}343},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Design is often raised in the literature as important to attaining various properties and characteristics in a software system. At least for open-source projects, it can be hard to find evidence of ongoing design work in the technical artifacts produced as part of the development. Although developers usually do not produce specific design documents, they do communicate about design in different ways. In this paper, we provide quantitative evidence that developers address design through discussions in commits, issues, and pull requests. To achieve this, we built a discussions{\textquoteright} classifier and automatically labeled 102,122 discussions from 77 projects. Based on this data, we make four observations about the projects: i) on average, 25\% of the discussions in a project are about design; ii) on average, 26\% of developers contribute to at least one design discussion; iii) only 1\% of the developers contribute to more than 15\% of the discussions in a project; and iv) these few developers who contribute to a broad range of design discussions are also the top committers in a project.
},
	keywords = {Design Discussions, empirical study, machine learning, mining challenge, msr challenge},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597115},
	url = {http://doi.acm.org/10.1145/2597073.2597115},
	attachments = {https://flosshub.org/sites/flosshub.org/files/brunet.pdf},
	author = {Brunet, Jo{\~a}o and Murphy, Gail C. and Terra, Ricardo and Figueiredo, Jorge and Serey, Dalton}
}
@conference {Murgia:2014:DFE:2597073.2597086,
	title = {Do Developers Feel Emotions? An Exploratory Analysis of Emotions in Software Artifacts},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {262{\textendash}271},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software development is a collaborative activity in which developers interact to create and maintain a complex software system. Human collaboration inevitably evokes emotions like joy or sadness, which can affect the collaboration either positively or negatively, yet not much is known about the individual emotions and their role for software development stakeholders. In this study, we analyze whether development artifacts like issue reports carry any emotional information about software development. This is a first step towards verifying the feasibility of an automatic tool for emotion mining in software development artifacts: if humans cannot determine any emotion from a software artifact, neither can a tool. Analysis of the Apache Software Foundation issue tracking system shows that developers do express emotions (in particular gratitude, joy and sadness). However, the more context is provided about an issue report, the more human raters start to doubt and nuance their interpretation of emotions. More investigation is needed before building a fully automatic emotion mining tool.
},
	keywords = {Emotion Mining, Empirical Software Engineer- ing, Issue Report},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597086},
	url = {http://doi.acm.org/10.1145/2597073.2597086},
	attachments = {https://flosshub.org/sites/flosshub.org/files/murgia.pdf},
	author = {Murgia, Alessandro and Tourani, Parastou and Adams, Bram and Ortu, Marco}
}
@inbook {1611,
	title = {Does Contributor Characteristics Influence Future Participation? A Case Study on Google Chromium Issue Tracking System},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {164-167},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Understanding and measuring factors influencing future participation is relevant to organizations. This information is useful for planning and strategic decision-making. In this work, we measure contributor characteristics and compute attrition to investigate their relationship by mining Issue Tracking System. We conduct experiments on four year data extracted from Google Chromium Issue Tracking System. Experimental results show that the likelihood of future participation increases with increase in relevance of role in project and level of participation in previous time-interval.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_22},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_22},
	author = {Rastogi, Ayushi and Sureka, Ashish},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@book {1590,
	title = {Drawing the Big Picture: Temporal Visualization of Dynamic Collaboration Graphs of OSS Software Forks},
	series = {10th IFIP WG 2.13 International Conference on Open Source Systems, OSS 2014, San Jos{\'e}, Costa Rica, May 6-9, 2014. Proceedings},
	volume = {427},
	year = {2014},
	pages = {41 - 50},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {How can we understand FOSS collaboration better? Can social issues that emerge be identified and addressed as they happen? Can the community heal itself, become more transparent and inclusive, and promote diversity? We propose a technique to address these issues by quantitative analysis and temporal visualization of social dynamics in FOSS communities. We used social network analysis metrics to identify growth patterns and unhealthy dynamics; This gives the community a heads-up when they can still take action to ensure the sustainability of the project.},
	isbn = {978-3-642-55128-4},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-55128-4_5},
	author = {Amir Azarbakht and Jensen, Carlos},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, Anthony I.}
}
@conference {Rozas:2014:DCP:2641580.2641624,
	title = {Drupal As a Commons-Based Peer Production Community: A Sociological Perspective},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {36:1{\textendash}36:2},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The aim of this research consists of extracting a set of insights related to the dynamics, group decision making procedures, motivations to contribute and mechanisms employed in the coordination of Commons-Based Peer Production communities, using as a case study the community responsible for the development of the Free/Libre Open Source Software Drupal. A sociological perspective is taken for this purpose, and a set of social research qualitative and quantitative methods employed for the study of online communities (virtual ethnography) are being used.
},
	keywords = {Activity Theory, Commons-Based Peer Production, drupal, Free/Libre Open Source Software, Virtual Ethnography},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641624},
	url = {http://doi.acm.org/10.1145/2641580.2641624},
	author = {Rozas, David}
}
@proceedings {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.}
}
@conference {Romo:2014:FGD:2641580.2641592,
	title = {Filling the Gaps of Development Logs and Bug Issue Data},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {8:1{\textendash}8:4},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {It has been suggested that the data from bug repositories is not always in sync or complete compared to the logs detailing the actions of developers on source code.

In this paper, we trace two sources of information relative to software bugs: the change logs of the actions of developers and the issues reported as bugs. The aim is to identify and quantify the discrepancies between the two sources in recording and storing the developer logs relative to bugs.

Focussing on the databases produced by two mining software repository tools, CVSAnalY and Bicho, we use part of the SZZ algorithm to identify bugs and to compare how the "defects-fixing changes" are recorded in the two databases. We use a working example to show how to do so.

The results indicate that there is a significant amount of information, not in sync when tracing bugs in the two databases. We, therefore, propose an automatic approach to re-align the two databases, so that the collected information is mirrored and in sync.},
	keywords = {Bug traceability, bug-fixing commits},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641592},
	url = {http://doi.acm.org/10.1145/2641580.2641592},
	author = {Romo, Bilyaminu Auwal and Capiluppi, Andrea and Hall, Tracy}
}
@conference {Robles:2014:FSD:2597073.2597129,
	title = {FLOSS 2013: A Survey Dataset About Free Software Contributors: Challenges for Curating, Sharing, and Combining},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {396{\textendash}399},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this data paper we describe a data set obtained by means of performing an on-line survey to over 2,000 Free Libre Open Source Software (FLOSS) contributors. The survey includes questions related to personal characteristics (gender, age, civil status, nationality, etc.), education and level of English, professional status, dedication to FLOSS projects, reasons and motivations, involvement and goals. We describe as well the possibilities and challenges of using private information from the survey when linked with other, publicly available data sources. In this regard, an example of data sharing will be presented and legal, ethical and technical issues will be discussed.
},
	keywords = {anonymization, data combining, data sharing, ethics, free software, microdata, msr data showcase, open data, open source, privacy, Survey},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597129},
	url = {http://doi.acm.org/10.1145/2597073.2597129},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr14gregorio.pdf},
	author = {Gregorio Robles and Reina, Laura Arjona and Serebrenik, Alexander and Vasilescu, Bogdan and Gonz{\'a}lez-Barahona, Jes{\'u}s M.}
}
@inbook {1617,
	title = {Flow Research SXP Agile Methodology for FOSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {195-198},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

This paper aims to explain a procedure that takes into account the different research processes carried out in developing an open-source, allowing control and management. This study is the SXP methodology applied in this type of project was carried out, allowing the validity of the basis of this research.
},
	keywords = {methodology SXP, open-source, production, research, Software},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_28},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_28},
	author = {Pe{\~n}alver Romero, GladysMarsi and Leyva Samada, LisandraIsabel and Abad, AbelMeneses},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@proceedings {1567,
	title = {Forge++: The changing landscape of FLOSS development},
	year = {2014},
	note = {Note, Georgios Gousios, the author of GHTorrent, has this to say about the Github programming language query given in the paper:

"GHTorrent only records the primary language of a repository at the time the repository data was requested, as this is the only thing the Github API returns. Therefore, your query is correct but the interpretation of the results may be not."},
	month = {01/2014},
	pages = {3266-3275},
	publisher = {IEEE Computer Society},
	abstract = {Software forges are centralized online systems that provide useful tools to help distributed development teams work together, especially in free, libre, and open source software (FLOSS). Forge-provided tools may include web space, version control systems, mailing lists and communication forums, bug tracking systems, file downloads, wikis, and the like. Empirical software engineering researchers can mine the artifacts from these tools to better understand how FLOSS is made. As the landscape of distributed software development has grown and changed, the tools needed to make FLOSS have changed as well. There are three newer tools at the center of FLOSS development today: distributed version control based forges (like Github), programmer question-and-answer communities (like Stack Overflow), and pastebin tools (like Gist or Pastebin.com). These tools are extending and changing the toolset used for FLOSS development, and redefining what a software forge looks like. The main contributions of this paper are to describe each of these tools, to identify the data and artifacts available for mining from these tools, and to outline some of the ways researchers can use these artifacts to continue to understand how FLOSS is made.},
	doi = {10.1109/HICSS.2014.405},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hicssFLOSSfinalWatermark_0.pdf},
	author = {Squire, Megan}
}
@inbook {1598,
	title = {FOSS Service Management and Incidences},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {76-79},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

The Free Open Source Software (FOSS) solutions have been reaching a high demand, usage and global recognition, not only in the development of applications for companies and institutions also in the management of services and incidents. With the upswing of Information Technology (IT), the development of tools that enable the reporting of problems and incidents on any organization or company is necessary. Every day you need more applications, software generally, that make easier the user{\textquoteright}s actions. This paper describes the need to use these tools and recount the development of a web application that allows the management of reports and incidents from users of Nova, the GNU/Linux Cuban distribution.
},
	keywords = {FOSS, service management and incidences},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_9},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_9},
	author = {Ortiz, SusanaS{\'a}nchez and P{\'e}rez Benitez, Alfredo},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@proceedings {1636,
	title = {Free/Open Source Software projects as early MOOCs},
	year = {2014},
	month = {04/2014},
	pages = {874-883},
	abstract = {This paper presents Free/Libre/Open Source Software (FLOSS) Projects as early Massive Online Open Courses (MOOCs). Being software development a process where learning and collaboration is of major importance, FLOSS projects have in common many characteristics with MOOCs. This is because many FLOSS projects (such as Linux, Apache, GNOME or KDE, among others) are massive, they are open to anyone to participate, and are driven mainly by telematic means. We therefore present the research literature that has studied FLOSS projects from points of view that are close to learning and discuss how the FLOSS community has approached many of the issues related to acquiring knowledge and skills over the Internet and compare them to how currently MOOCs, both xMOOCs and cMOOCs, address these situations.
},
	keywords = {education, FLOSS, learning, mooc},
	doi = {10.1109/EDUCON.2014.6826200},
	author = {Robles, G. and Plaza, H. and Gonzalez-Barahona, J.M.}
}
@conference {Bloemen:2014:GPD:2597073.2597131,
	title = {Gentoo Package Dependencies over Time},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {404{\textendash}407},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source distributions such as Gentoo need to accurately track dependency relations between software packages in order to install working systems. To do this, Gentoo has a carefully authored database containing those relations. In this paper, we extract the Gentoo package dependency graph and its changes over time. The final dependency graph spans 15 thousand open source projects and 80 thousand dependency relations. Furthermore, the development of this graph is tracked over time from the beginning of the Gentoo project in 2000 to the first quarter of 2012, with monthly resolution. The resulting dataset provides many opportunities for research. In this paper we explore cluster analysis to reveals meaningful relations between packages and in a separate paper we analyze changes in the dependencies over time to get insights in the innovation dynamics of open source software.
},
	keywords = {dependencies, gentoo, graph, INNOVATION},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597131},
	url = {http://doi.acm.org/10.1145/2597073.2597131},
	author = {Bloemen, Remco and Amrit, Chintan and Kuhlmann, Stefan and Ord{\'o}{\~n}ez{\textendash}Matamoros, Gonzalo}
}
@proceedings {1572,
	title = {Governance of Open Source Electronic Health Record Projects: A Successful Case of a Hybrid Model},
	year = {2014},
	month = {01/2014},
	pages = {2798-2807},
	publisher = {IEEE Computer Society},
	abstract = {Electronic Health Records (EHRs) are at the heart of most health system reforms. As an increasing number of hospitals are adopting open source EHRs and as many questions are still unanswered for potential adopters of open source EHRs, analyzing the governance of such systems has become important. Due to the increased diversity of sponsors and stakeholders of open source software (OSS) over the past few years, numerous governance models of OSS projects have emerged. In contrast to earlier {\textquotedblleft}community-managed{\textquotedblright} governance model s, these emergent models are characterized by the sponsorship of a corporation or a not-for-profit entity or by other hybrid forms. This paper reports on the investigation of such a hybrid model of open source EHR project governance adopted with success by a large Canadian hospital. The case study provides rich insights for other hospitals wishing to adopt an EHR of the open source type.},
	doi = {10.1109/HICSS.2014.350},
	author = {Placide Poba-Nzaou and Josianne Marsan and Guy Pare and Louis Raymond}
}
@conference {1692,
	title = {Hackers on Forking},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {All open source licenses allow the copying of an existing body of code for use as the basis of a separate development project. This practice is commonly known as forking the code. This paper presents the results of a study in which 11 programmers were interviewed about their opinions on the right to fork and the impact of forking on open source software development.

The results show that there is a general consensus among programmers{\textquoteright} views regarding both the favourable and unfavourable aspects that stem from the right to fork. Interestingly, while all programmers noted potential downsides to the right to fork, it was seen by all as an integral component of open source software, and a right that must not be infringed regardless of circumstance or outcome.},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641590},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p06.pdf},
	author = {Nyman, Linus}
}
@inbook {1594,
	title = {How Do Social Interaction Networks Influence Peer Impressions Formation? A Case Study},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {31-40},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {Due to their lack of physical interaction, Free and Open Source Software (FOSS) participants form impressions of their teammates largely based on sociotechnical mechanisms including: code commits, code reviews, mailing-lists, and bug comments. These mechanisms may have different effects on peer impression formation. This paper describes a social network analysis of the WikiMedia project to determine which type of interaction has the most favorable characteristics for impressions formation. The results suggest that due to lower centralization, high interactivity, and high degree of interactions between participants, the code review interactions have the most favorable characteristics to support impression formation among FOSS participants.},
	keywords = {COLLABORATION, FOSS, open source, OSS, social network analysis},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_4},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_4},
	author = {Bosu, Amiangshu and Carver, JeffreyC.},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Vasilescu:2014:SQS:2531602.2531659,
	title = {How Social Q\&A Sites Are Changing Knowledge Sharing in Open Source Software Communities},
	booktitle = {Proceedings of the 17th ACM Conference on Computer Supported Cooperative Work \&\#38; Social Computing},
	series = {CSCW {\textquoteright}14},
	year = {2014},
	pages = {342{\textendash}354},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Historically, mailing lists have been the preferred means for coordinating development and user support activities. With the emergence and popularity growth of social Q\&A sites such as the StackExchange network (e.g., StackOverflow), this is beginning to change. Such sites offer different socio-technical incentives to their participants than mailing lists do, e.g., rich web environments to store and manage content collaboratively, or a place to showcase their knowledge and expertise more vividly to peers or potential recruiters. A key difference between StackExchange and mailing lists is gamification, i.e., StackExchange participants compete to obtain reputation points and badges. In this paper, we use a case study of R (a widely-used tool for data analysis) to investigate how mailing list participation has evolved since the launch of StackExchange. Our main contribution is the assembly of a joint data set from the two sources, in which participants in both the texttt{r-help} mailing list and StackExchange are identifiable. This permits their activities to be linked across the two resources and also over time. With this data set we found that user support activities show a strong shift away from texttt{r-help}. In particular, mailing list experts are migrating to StackExchange, where their behaviour is different. First, participants active both on texttt{r-help} and on StackExchange are more active than those who focus exclusively on only one of the two. Second, they provide faster answers on StackExchange than on texttt{r-help}, suggesting they are motivated by the emph{gamified} environment. To our knowledge, our study is the first to directly chart the changes in behaviour of specific contributors as they migrate into gamified environments, and has important implications for knowledge management in software engineering.},
	keywords = {a, crowdsourced knowledge, gamification., mailing lists, open source, social q\&\#38},
	isbn = {978-1-4503-2540-0},
	doi = {10.1145/2531602.2531659},
	url = {http://doi.acm.org/10.1145/2531602.2531659},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cscw14.pdf},
	author = {Vasilescu, Bogdan and Serebrenik, Alexander and Devanbu, Prem and Filkov, Vladimir}
}
@inbook {1618,
	title = {How to Support Newcomers Onboarding to Open Source Software Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {199-201},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

While onboarding an open source software (OSS) project, contributors face many different barriers that hinder their contribution, leading in many cases to dropout. Many projects leverage the contribution of outsiders and the sustainability of the project relies on retaining some of these newcomers. In this research, we aim at understanding the barriers that hinder onboarding of newcomers to OSS projects, by means of different empirical approaches, and proposing a set of strategies that can be used to support the first step of newcomers.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_29},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_29},
	author = {Steinmacher, Igor and Gerosa, MarcoAur{\'e}lio},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Thorne:2014:YRM:2641580.2641582,
	title = {How You Run a Meeting Says a Lot About Your Values: Participatory Practices for Open Communities},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {42:1{\textendash}42:1},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Live events are some of the best ways to see the power dynamics and philosophical bent of a community. Many communities, open and closed, glorify sitting in a darkened room and being inspired by a sage on the stage. And then there are events about participation: making and learning with fellow participants around shared passions and interests. The session argues for the use of participatory methods at events as a way to manifest open values. We{\textquoteright}ll unpack some techniques and case studies, as well as practice ourselves.
},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641582},
	url = {http://doi.acm.org/10.1145/2641580.2641582},
	author = {Thorne, Michelle}
}
@conference {Ahmed:2014:IAC:2641580.2641585,
	title = {The Impact of Automatic Crash Reports on Bug Triaging and Development in Mozilla},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1:1{\textendash}1:8},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Free/Open Source Software projects often rely on users submitting bug reports. However, reports submitted by novice users may lack information critical to developers, and the process may be intimidating and difficult. To gather more and better data, projects deploy automatic crash reporting tools, which capture stack traces and memory dumps when a crash occurs. These systems potentially generate large volumes of data, which may overwhelm developers, and their presence may discourage users from submitting traditional bug reports. In this paper, we examine Mozilla{\textquoteright}s automatic crash reporting system and how it affects their bug triaging process. We find that fewer than 0.00009\% of crash reports end up in a bug report, but as many as 2.33\% of bug reports have data from crash reports added. Feedback from developers shows that despite some problems, these systems are valuable. We conclude with a discussion of the pros and cons of automatic crash reporting systems.
},
	keywords = {Automatic Crash reporting, debugging, FOSS, Free/Open Source Software, Open Bug Reporting, testing},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641585},
	url = {http://doi.acm.org/10.1145/2641580.2641585},
	author = {Ahmed, Iftekhar and Mohan, Nitin and Jensen, Carlos}
}
@conference {2014:ICS:2641580.2641625,
	title = {Impact of Collaboration on Structural Software Quality},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {37:1{\textendash}37:3},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The structural quality of a codebase is a key determining factor in the software{\textquoteright}s total cost of ownership, yet it is notoriously difficult to measure or predict. In this doctoral research we leverage the power of open source repositories to understand the factors that influence structural quality (and by extension fault-proneness) in the context of the patterns of collaborative behaviour exhibited by contributors. The objective is to further our understanding of how such behaviour impacts structural quality with the end goal being to inform management decision making across the industry in the pursuit of better software engineering practices.
},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641625},
	url = {http://doi.acm.org/10.1145/2641580.2641625}
}
@inbook {1602,
	title = {Improving Mozilla{\textquoteright}s In-App Payment Platform},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {103-106},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Nowadays, an in-app payment mechanism is offered in most existing mobile payment solutions. However, current solutions are not flexible and impose certain restrictions: users are limited to predefined payment options and merchants need to adapt their payment mechanisms to each payment provider they use. Ideally mobile payments should be as flexible as possible to be able to target various markets together with users{\textquoteright} spending habits. Mozilla wants to promote an open approach in mobile payments by offering a flexible, easily accessible solution. This solution is analyzed, its shortcomings and possible improvements are discussed leading to an original proposal.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_13},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_13},
	author = {Janczukowicz, Ewa and Bouabdallah, Ahmed and Braud, Arnaud and Fromentoux, Ga{\"e}l and Bonnin, Jean-Marie},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {1704,
	title = {Industry Questions about Open Source Software in Business: Research Directions and Potential Answers},
	booktitle = {2014 6th International Workshop on Empirical Software Engineering in Practice (IWESEP)2014 6th International Workshop on Empirical Software Engineering in Practice},
	year = {2014},
	pages = {55 - 59},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Osaka, Japan},
	abstract = {As open source software (OSS) has become an integral part of today{\textquoteright}s software businesses, many software companies rely on OSS to develop their customer solutions and products. On the other hand, they face various concerns in using OSS, such as technical support, quality, security and licensing issues. This paper focuses on OSS-related FAQ in industry, and tries to answer them or to provide research directions based on lessons learned from recent mining OSS repository researches.
},
	doi = {10.1109/IWESEP.2014.12},
	author = {Ihara, Akinori and Monden, Akito and Matsumoto, Ken-ichi}
}
@conference {1693,
	title = {Initial Results from the Study of the Open Source Sector in Belgium},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 5},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {The economy of FLOSS (Free and open source software) has been the subject of numerous studies and publications, particularly on the issue of business models. However, there are fewer studies on the local networks of FLOSS providers. This research focuses on the ecosystem of Belgian FLOSS providers and, more specifically, their geographical distribution, the activities, technologies and software they support, their business models, their economic performance and the relationships between companies. The research is based on a directory containing nearly 150 companies. This directory led to the creation of a specialized search engine that helped to improve annotation. The research also uses financial data provided by the Belgian Central Balance Sheet Office. The initial results of this study show a concentration in major economic areas. The businesses are more active in the services and are heavily involved activities such as infrastructure software and Web development, activities which were common in the early years of free software development. Services for the support of business software is also common. A first analysis of the graph of relationships between providers{\textquoteright} websites highlights the role that is played by the multinational IT companies, by FLOSS editors, by commercial FLOSS associations and especially by the Walloon centers of competence that offer vast training catalogs that are dedicated to FLOSS. This research opens up many perspectives for improving the automation of the company directory updates, the analysis of the relationship between enterprises, and the automation of the financial analysis of companies.
},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641591},
	author = {Viseur, Robert}
}
@conference {Bloemen:2014:IDO:2597073.2597079,
	title = {Innovation Diffusion in Open Source Software: Preliminary Analysis of Dependency Changes in the Gentoo Portage Package Database},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {316{\textendash}319},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper we make the case that software dependencies are a form of innovation adoption. We then test this on the time-evolution of the Gentoo package dependency graph. We find that the Bass model of innovation diffusion fits the growth of the number of packages depending on a given library. Interestingly, we also find that low-level packages have a primarily imitation driven adoption and multimedia libraries have primarily innovation driven growth.
},
	keywords = {dependencies, gentoo, graph, INNOVATION},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597079},
	url = {http://doi.acm.org/10.1145/2597073.2597079},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bloeman.pdf},
	author = {Bloemen, Remco and Amrit, Chintan and Kuhlmann, Stefan and Ord{\'o}{\~n}ez{\textendash}Matamoros, Gonzalo}
}
@conference {Rahman:2014:IPR:2597073.2597121,
	title = {An Insight into the Pull Requests of GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {364{\textendash}367},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Given the increasing number of unsuccessful pull requests in GitHub projects, insights into the success and failure of these requests are essential for the developers. In this paper, we provide a comparative study between successful and unsuccessful pull requests made to 78 GitHub base projects by 20,142 developers from 103,192 forked projects. In the study, we analyze pull request discussion texts, project specific information (e.g., domain, maturity), and developer specific information (e.g., experience) in order to report useful insights, and use them to contrast between successful and unsuccessful pull requests. We believe our study will help developers overcome the issues with pull requests in GitHub, and project administrators with informed decision making.
},
	keywords = {Commit comments, mining challenge, msr challenge, pull request, topic model},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597121},
	url = {http://doi.acm.org/10.1145/2597073.2597121},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rahman.pdf},
	author = {Rahman, Mohammad Masudur and Chanchal K. Roy}
}
@conference {1690,
	title = {"The Institutionalization of Digital Openness"},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 2},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {Around the world national and municipal governments launch open data initiatives with declared goals like increased efficiency, transparency or economic growth. However, although little of these effects have been proven, more and more administrations open up their datasets to the public. The dissertation project describes this phenomenon as the ongoing institutionalization of digital openness in the field of public sector information. With empirical evidence from three case studies in large European cities the research project intends to theorize how NGOs, hackers and certain civil servants turn open data into an institution, which more and more public bodies feel the need to adapt to.
},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641626},
	author = {Maximilian Heimst{\"a}dt}
}
@conference {Zhang:2014:ISM:2666539.2666572,
	title = {Investigating Social Media in GitHub{\textquoteright}s Pull-requests: A Case Study on Ruby on Rails},
	booktitle = {Proceedings of the 1st International Workshop on Crowd-based Software Development Methods and Technologies},
	series = {CrowdSoft 2014},
	year = {2014},
	pages = {37{\textendash}41},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In GitHub, pull-request mechanism is an outstanding social development method by integrating with many social media. Many studies have explored that social media has an important effect on software development. @-mention as a typical social media, is a useful tool in social platform. In this paper, we made a quantitative analysis of @-mention in pull-requests of the project Ruby on Rails. First, we make a convictive statistics of the popularity of pull-request mechanism in GitHub. Then we investigate the current situation of @-mention in the Ruby on Rails. Our empirical analysis results find some insights of @-mention.
},
	keywords = {@-mention, github, pull-request, social media},
	isbn = {978-1-4503-3224-8},
	doi = {10.1145/2666539.2666572},
	url = {http://doi.acm.org/10.1145/2666539.2666572},
	author = {Zhang, Yang and Yin, Gang and Yu, Yue and Wang, Huaimin}
}
@proceedings {1568,
	title = {It{\textquoteright}s Not Only about Writing Code: An Investigation of the Notion of Citizenship Behaviors in the Context of Free/Libre/Open Source Software Communities},
	year = {2014},
	month = {01/2014},
	pages = {3276-3285},
	publisher = {IEEE Computer Society},
	abstract = {Attracting a large number of new contributors has been seen as a way to ensure the survival, long-term success, and sustainability of Free/Libre/Open Source Software (FLOSS) communities. However, this appears to be a necessary, but not a sufficient condition, as the well-being of FLOSS communities also relies on members behaving as {\textquotedblleft}good citizens,{\textquotedblright} to nurture and protect the community. This paper investigates the notion of FLOSS community citizenship behaviors in light of the organizational citizenship behaviors literature. Relying on 11 semi-structured interviews with FLOSS project leaders and community managers, the papers identifies key instances of citizenship behaviors along two dimensions: CCB-I (community citizenship behaviors oriented towards the benefits of other individuals), and CCB-P (community citizenship behaviors oriented towards the benefits of the project and its community).},
	doi = {10.1109/HICSS.2014.406},
	author = {Carillo, Kevin Daniel Andre and Huff, Sid and Chawner, Brenda}
}
@inbook {1612,
	title = {A Layered Approach to Managing Risks in OSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {168-171},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

In this paper, we propose a layered approach to managing risks in OSS projects. We define three layers: the first one for defining risk drivers by collecting and summarising available data from different data sources, including human-provided contextual information; the second layer, for converting these risk drivers into risk indicators; the third layer for assessing how these indicators impact the business of the adopting organisation. The contributions are: 1) the complexity of gathering data is isolated in one layer using appropriate techniques, 2) the context needed to interpret this data is provided by expert involvement evaluating risk scenarios and answering questionnaires in a second layer, 3) a pattern-based approach and risk reasoning techniques to link risks to business goals is proposed in the third layer.
},
	keywords = {Layered Model, open source, OSS, Risk Management},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_23},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_23},
	author = {Franch, Xavier and Kenett, Ron and Mancinelli, Fabio and Susi, Angelo and Ameller, David and Ben-Jacob, Ron and Siena, Alberto},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Gousios:2014:LGG:2597073.2597126,
	title = {Lean GHTorrent: GitHub Data on Demand},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {384{\textendash}387},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In recent years, GitHub has become the largest code host in the world, with more than 5M developers collaborating across 10M repositories. Numerous popular open source projects (such as Ruby on Rails, Homebrew, Bootstrap, Django or jQuery) have chosen GitHub as their host and have migrated their code base to it. GitHub offers a tremendous research potential. For instance, it is a flagship for current open source development, a place for developers to showcase their expertise to peers or potential recruiters, and the platform where social coding features or pull requests emerged. However, GitHub data is, to date, largely underexplored. To facilitate studies of GitHub, we have created GHTorrent, a scalable, queriable, offline mirror of the data offered through the GitHub REST API. In this paper we present a novel feature of GHTorrent designed to offer customisable data dumps on demand. The new GHTorrent data-on-demand service offers users the possibility to request via a web form up-to-date GHTorrent data dumps for any collection of GitHub repositories. We hope that by offering customisable GHTorrent data dumps we will not only lower the "barrier for entry" even further for researchers interested in mining GitHub data (thus encourage researchers to intensify their mining efforts), but also enhance the replicability of GitHub studies (since a snapshot of the data on which the results were obtained can now easily accompany each study).
},
	keywords = {data on demand, dataset, github, msr data showcase},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597126},
	url = {http://doi.acm.org/10.1145/2597073.2597126},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lean-ghtorrent_0.pdf},
	author = {Gousios, Georgios and Vasilescu, Bogdan and Serebrenik, Alexander and Zaidman, Andy}
}
@inbook {1607,
	title = {Lessons Learned from Teaching Open Source Software Development},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {133-142},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Free/Open Source Software allows students to learn valuable real world skills and experiences, as well as a create a portfolio to show future employers. However, the learning curve to joining FOSS can be daunting, often leading newcomers to walk away frustrated. Universities therefore need to find ways to provide a structured introduction to students, helping them overcome the barriers to entry. This paper describes two courses taught at two universities, built around a Communities of Practice model, and the lessons learned from these. Suggestions and insights are shared for how to structure and evaluate such courses for maximum effect.
},
	keywords = {education, FOSS, Free/Open Source Software},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_18},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_18},
	author = {Morgan, Becka and Jensen, Carlos},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Yamashita:2014:MSO:2597073.2597116,
	title = {Magnet or Sticky? An OSS Project-by-project Typology},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {344{\textendash}347},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {For Open Source Software (OSS) projects, retaining existing contributors and attracting new ones is a major concern. In this paper, we expand and adapt a pair of population migration metrics to analyze migration trends in a collection of open source projects. Namely, we study: (1) project stickiness, i.e., its tendency to retain existing contributors and (2) project magnetism, i.e., its tendency to attract new contributors. Using quadrant plots, we classify projects as attractive (highly magnetic and sticky), stagnant (highly sticky, weakly magnetic), fluctuating (highly magnetic, weakly sticky), or terminal (weakly magnetic and sticky). Through analysis of the MSR challenge dataset, we find that: (1) quadrant plots can effectively identify at-risk projects, (2) stickiness is often motivated by professional activity and (3) transitions among quadrants as a project ages often coincides with interesting events in the evolution history of a project.
},
	keywords = {Developer migration, Magnet, mining challenge, msr challenge, open source, Sticky},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597116},
	url = {http://doi.acm.org/10.1145/2597073.2597116},
	attachments = {https://flosshub.org/sites/flosshub.org/files/yamashita.pdf},
	author = {Yamashita, Kazuhiro and McIntosh, Shane and Kamei, Yasutaka and Ubayashi, Naoyasu}
}
@conference {1823,
	title = {"May the fork be with you": novel metrics to analyze collaboration on GitHub},
	booktitle = {Proceedings of the 5th International Workshop on Emerging Trends in Software Metrics - WETSoM 2014},
	year = {2014},
	note = {"According to FLOSSmole [8] (Free Libre OpenSource Software)
statistics, GitHub had 191765 repositories publicly
available at May 2012."},
	pages = {37 - 43},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Multi{\textendash}repository software projects are becoming more and
more popular, thanks to web{\textendash}based facilities such as GitHub.
Code and process metrics generally assume a single repository
must be analyzed, in order to measure the characteristics
of a codebase. Thus they are not apt to measure how
much relevant information is hosted in multiple repositories
contributing to the same codebase. Nor can they feature
the characteristics of such a distributed development process.
We present a set of novel metrics, based on an original
classification of commits, conceived to capture some interesting
aspects of a multi{\textendash}repository development process. We
also describe an efficient way to build a data structure that
allows to compute these metrics on a set of Git repositories.
Interesting outcomes, obtained by applying our metrics
on a large sample of projects hosted on GitHub, show the
usefulness of our contribution.},
	keywords = {flossmole, github},
	isbn = {9781450328548},
	doi = {10.1145/2593868.2593875},
	url = {http://marbiaz.github.io/docs/Biazzini14b.pdf},
	author = {Marco Biazzini and Benoit Baudry}
}
@unpublished {1799,
	title = {Measuring the Health of Open Source Software Ecosystems: Moving Beyond the Scope of Project Health},
	year = {2014},
	abstract = {Background. The livelihood of an open source ecosystem is important to different ecosystem participants: software developers, end-users, investors, and participants want to know whether their ecosystem is healthy and performing well. Currently, there exists no working operationalization available that can be used to determine the health of open source ecosystems. Health is typically looked at from a project scope, not from an ecosystem scope. Objectives. With such an operationalization, stakeholders can make better decisions on whether to invest in an ecosystem: developers can select the healthiest ecosystem to join, keystone organizers can establish which governance techniques are effective, and end-users can select ecosystems that are robust, will live long, and prosper. Method. Design research is used to create the health operationalization. The evaluation step is done using four ecosystem health projects from literature. Results. The Open Source Ecosystem Health Operationalization is provided, which establishes the health of a complete software ecosystem, using the data from collections of open source projects that belong to the ecosystem. Conclusion. The groundwork is done, by providing a summary of research challenges, for more research in ecosystem health. With the operationalization in hand, re- searchers no longer need to start from scratch when researching open source ecosystems{\textquoteright} health.},
	keywords = {open source ecosystems, Software ecosystem health, Software repository mining},
	url = {https://www.dropbox.com/s/borc730uw32kkzp/SECOhealth.pdf?dl=0},
	attachments = {https://flosshub.org/sites/flosshub.org/files/SECOhealth\%20\%281\%29.pdf},
	author = {Slinger Jansen}
}
@conference {Eckhardt:2014:MMO:2642803.2642810,
	title = {The Merits of a Meritocracy in Open Source Software Ecosystems},
	booktitle = {Proceedings of the 2014 European Conference on Software Architecture Workshops},
	series = {ECSAW {\textquoteright}14},
	year = {2014},
	pages = {7:1{\textendash}7:6},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The Eclipse open source ecosystem has grown from a small internal IBM project to one of the biggest Integrated Development Environments in the market. Open source communities and ecosystems do not follow the standard governance strategies typically used in large organizations. A meritocracy is a frequently occurring form of governance on different levels in open ecosystems. In this paper we investigate how this form of governance influences the health of projects within the Eclipse ecosystem in terms of the amount of commits within each month. We analyzed the hierarchy of Eclipse, how merits are conceptualized within the ecosystem and the effect of the appointments of mentors and project leads on the amount of commits. From our research, we can conclude that this system is not always as fair as it seems; merits are only a benefit in some cases.},
	keywords = {Ecosystem Health, Meritocracy, open source, Software ecosystems},
	isbn = {978-1-4503-2778-7},
	doi = {10.1145/2642803.2642810},
	url = {http://doi.acm.org/10.1145/2642803.2642810},
	author = {Eckhardt, Evert and Kaats, Erwin and Slinger Jansen and Alves, Carina}
}
@inbook {1613,
	title = {A Methodology for Managing FOSS Migration Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {172-175},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Since 2005, the Free Software Center (CESOL) at the University of Information Science (UCI) in Havana, Cuba, has conducted several free and open source software (FOSS) migration projects for various organizations. The experience gained from these projects enabled the creation of a FOSS Migration Methodology which documented how the technical elements of a project of this kind should be executed. Despite the usefulness of this methodology, the projects that have been undertaken experienced difficulties that were, in most cases, directly related to their management. This research aims to improve the methodology and minimize management-related challenges thereby improving the quality of migration projects. The proposed methodology was applied in a project that ran in a higher education organization and the results prove that the methodology enhanced the quality of the migration project.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_24},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_24},
	author = {Go{\~n}i, Angel and Boodraj, Maheshwar and Cabreja, Yordanis},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@article {1637,
	title = {Microblogging in Open Source Software Development: The Case of Drupal and Twitter},
	journal = {IEEE Software},
	volume = {31},
	year = {2014},
	month = {7/2014},
	pages = {72 - 80},
	abstract = {Microblogging is a popular form of social media that has quickly permeated both enterprise and open source communities. However, exactly how open source communities can leverage microblogging isn{\textquoteright}t yet well understood. The authors investigate how Drupal{\textquoteright}s open source community uses Twitter, a household name in microblogging. Their analysis of group and individual accounts of Drupal developers reveals that they take on similar but distinct roles. Both serve as communicators of essential links to a vast and growing community knowledge base, such as work artifacts, issues, documentation, and blog posts, but community members often express positive emotions when tweeting about work, which reinforces a sense of community.},
	issn = {0740-7459},
	doi = {10.1109/MS.2013.98},
	author = {Wang, Xiaofang and Kuzmickaja, Ilona and Stol, Klaas-Jan and Abrahamsson, Pekka and Fitzgerald, Brian}
}
@article {mcdonald2014modeling,
	title = {MODELING DISTRIBUTED COLLABORATION ON GITHUB},
	journal = {Advances in Complex Systems},
	year = {2014},
	publisher = {World Scientific},
	abstract = {In this paper, we apply concepts from Distributed Leadership, a theory suggesting that leadership is shared among members of an organization, to frame models of contribution that we uncover in five relatively successful open source software (OSS) projects hosted on GitHub. In this qualitative, comparative case study, we show how these projects make use of GitHub features such as pull requests (PRs). We find that projects in which member PRs are more frequently merged with the codebase experience more sustained participation. We also find that projects with higher success rates among contributors and higher contributor retention tend to have more distributed (non-centralized) practices for reviewing and processing PRs. The relationships between organizational form and GitHub practices are enabled and made visible as a result of GitHub{\textquoteright}s novel interface. Our results demonstrate specific dimensions along which these projects differ and explicate a framework that warrants testing in future studies of OSS, particularly GitHub.},
	author = {McDONALD, NORA and Blincoe, Kelly and PETAKOVIC, EVA and Goggins, Sean}
}
@conference {Williams:2014:MOP:2597073.2597132,
	title = {Models of OSS Project Meta-information: A Dataset of Three Forges},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	note = {"FLOSSMole [4] is a similar initiative to OSSMETER; it
aims to collect and freely redistribute in different formats
the data of open source software. Differently from OSSMETER,
however, the FLOSSMole project does not provide the
instruments to analyse data, that are simply collected and
made publicly available."},
	pages = {408{\textendash}411},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The process of selecting open-source software (OSS) for adoption is not straightforward as it involves exploring various sources of information to determine the quality, maturity, activity, and user support of each project. In the context of the OSSMETER project, we have developed a forge-agnostic metamodel that captures the meta-information common to all OSS projects. We specialise this metamodel for popular OSS forges in order to capture forge-specific meta-information. In this paper we present a dataset conforming to these metamodels for over 500,000 OSS projects hosted on three popular OSS forges: Eclipse, SourceForge, and GitHub. The dataset enables different kinds of automatic analysis and supports objective comparisons of cross-forge OSS alternatives with respect to a user{\textquoteright}s needs and quality requirements.
},
	keywords = {data mining, flossmole cited},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597132},
	url = {http://doi.acm.org/10.1145/2597073.2597132},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Models_of_OSS_Project_Meta-Information_A_Dataset_of_Three_Forges_draft.pdf},
	author = {Williams, James R. and Di Ruscio, Davide and Matragkas, Nicholas and Di Rocco, Juri and Kolovos, Dimitris S.}
}
@conference {Beller:2014:MCR:2597073.2597082,
	title = {Modern Code Reviews in Open-source Projects: Which Problems Do They Fix?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {202{\textendash}211},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Code review is the manual assessment of source code by humans, mainly intended to identify defects and quality problems. Modern Code Review (MCR), a lightweight variant of the code inspections investigated since the 1970s, prevails today both in industry and open-source software (OSS) systems. The objective of this paper is to increase our understanding of the practical benefits that the MCR process produces on reviewed source code. To that end, we empirically explore the problems fixed through MCR in OSS systems. We manually classified over 1,400 changes taking place in reviewed code from two OSS projects into a validated categorization scheme. Surprisingly, results show that the types of changes due to the MCR process in OSS are strikingly similar to those in the industry and academic systems from literature, featuring the similar 75:25 ratio of maintainability-related to functional problems. We also reveal that 7{\textendash}35\% of review comments are discarded and that 10{\textendash}22\% of the changes are not triggered by an explicit review comment. Patterns emerged in the review data; we investigated them revealing the technical factors that influence the number of changes due to the MCR process. We found that bug-fixing tasks lead to fewer changes and tasks with more altered files and a higher code churn have more changes. Contrary to intuition, the person of the reviewer had no impact on the number of changes.
},
	keywords = {code review, defects, open source software},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597082},
	url = {http://doi.acm.org/10.1145/2597073.2597082},
	attachments = {https://flosshub.org/sites/flosshub.org/files/beller.pdf},
	author = {Beller, Moritz and Bacchelli, Alberto and Zaidman, Andy and Juergens, Elmar}
}
@inbook {1592,
	title = {Navigation Support in Evolving Open-Source Communities by a Web-Based Dashboard},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {11-20},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

The co-evolution of communities and systems in open-source software (OSS) projects is an established research topic. There are plenty of different studies of OSS community and system evolution available. However, most of the existing OSS project visualization tools provide source code oriented metrics with little support for communities. At the same time, self-reflection helps OSS community members to understand what is happening within their community. Considering missing community-centered OSS visualizations, we investigated the following research question: Are the OSS communities interested in a visualization platform, which reflects community evolution? If so, what aspects should it reflect?

To answer this research question, we first conducted an online survey within different successful OSS communities. The results of our evaluation showed that there is a great interest in community-centered statistics. Therefore, we developed an OSS navigator: a Web-based dashboard for community-oriented reflection of OSS projects. The navigator was filled with data from communication and development repositories of three large bioinformatics OSS projects. The members of these OSS communities tested the prototype. The bioinformatics OSS developers acknowledged the uniqueness of statistics that the NOSE dashboard offers. Especially, graph visualization of the project social network received the highest attention. This network view combined with other community-oriented metrics can significantly enhance the existing visualizations or even be provided as a standalone tool.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_2},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_2},
	author = {Hannemann, Anna and Liiva, Kristjan and Klamma, Ralf},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {1676,
	title = {OCData Hackathon @ CSCW 2014},
	booktitle = {Proceedings of the 17th ACM conference on Computer supported cooperative work \& social computing},
	year = {2014},
	pages = {317 - 318},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Baltimore, Maryland, USANew York, New York, USA},
	abstract = {Online Communities data is prevalent in CSCW research, but the approaches to collecting, managing, analyzing and visualizing large scale social data varies on a lab by lab basis. The OCData hackathon is aimed at creating a community opportunity to share approaches to online communities research at the level of data. Integrating data, tools and theories to address interesting research questions remains a challenge for the community.},
	isbn = {9781450325417},
	doi = {10.1145/2556420.2558865},
	author = {Goggins, Sean and Andrea Wiggins and Susan Winter and Brian Butler}
}
@conference {1691,
	title = {Older Adults and Free/Open Source Software},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {The global population is aging rapidly, and older adults are becoming increasingly technically savvy. This paper explores ways to engage these individuals to contribute to free/open source software (FOSS) projects. We conducted a pilot diary study to explore motivations, barriers, and the contribution processes of first-time contributors in a real time, qualitative manner. In addition, we measured their self-efficacy before and after their participation. We found that what drove participants were intrinsic motivations, altruism, and internal values, which differed from previous work with older adults and with the general FOSS population. We also found that self-efficacy did not change significantly, even when participants encountered significant barriers or setbacks. The top 3 barriers were lack of communication, installation issues, and documentation issues. We found that asking for and receiving help, and avoiding difficult development environments were more likely to lead to success. To verify these results, we encourage a future large-scale diary study that involves multiple demographics. Given our pilot study, we recommend that future outreach efforts involving older adults focus on how to effectively communicate and build community amongst older contributors.
},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641589},
	author = {Davidson, Jennifer and Umme Ayda Mannan and Rithika Naik and Ishneet Dua and Jensen, Carlos}
}
@conference {Guo:2014:ODC:2597073.2597094,
	title = {Oops! Where Did That Code Snippet Come from?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {52{\textendash}61},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {A kernel oops is an error report that logs the status of the Linux kernel at the time of a crash. Such a report can provide valuable first-hand information for a Linux kernel maintainer to conduct postmortem debugging. Recently, a repository has been created that systematically collects kernel oopses from Linux users. However, debugging based on only the information in a kernel oops is difficult. We consider the initial problem of finding the offending line, i.e., the line of source code that incurs the crash. For this, we propose a novel algorithm based on approximate sequence matching, as used in bioinformatics, to automatically pinpoint the offending line based on information about nearby machine-code instructions, as found in a kernel oops. Our algorithm achieves 92\% accuracy compared to 26\% for the traditional approach of using only the oops instruction pointer.},
	keywords = {debugging, linux kernel, oops, sequence alignment},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597094},
	url = {http://doi.acm.org/10.1145/2597073.2597094},
	attachments = {https://flosshub.org/sites/flosshub.org/files/guo.pdf},
	author = {Guo, Lisong and Lawall, Julia and Muller, Gilles}
}
@inbook {1601,
	title = {Open Source Mobile Virtual Machines: An Energy Assessment of Dalvik vs. ART},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {93-102},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Dalvik Virtual Machine is Open Source Software and an important part of the Android OS and its better understanding and energy optimization can significantly contribute to the overall greenness of the mobile environment. With the introduction of the OSS solution, named Android Runtime (ART) an attempt of performance and energy consumption optimization was made. In this paper we investigate and compare the performance of the Dalvik virtual and ART from energy perspective. In order to answer our research questions we executed a set of benchmarks in identical experimental setup for both runtimes, while measuring the energy spent and percentage of battery discharge. The results showed that in most of the use case scenarios Ahead-Of-Time compilation process of ART is overall more energy efficient than the Just-In- Time one of Dalvik.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_12},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_12},
	author = {Georgiev, AntonB. and Sillitti, Alberto and Succi, Giancarlo},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Farah:2014:OSA:2597073.2597135,
	title = {OpenHub: A Scalable Architecture for the Analysis of Software Quality Attributes},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {420{\textendash}423},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {There is currently a vast array of open source projects available on the web, and although they are searchable by name or description in the search engines, there is no way to search for projects by how well they perform on a given set of quality attributes (e.g. usability or maintainability). With OpenHub, we present a scalable and extensible architecture for the static and runtime analysis of open source repositories written in Python, presenting the architecture and pinpointing future possibilities with it.
},
	keywords = {architecture, github, python, Quality Attributes},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597135},
	url = {http://doi.acm.org/10.1145/2597073.2597135},
	author = {Farah, Gabriel and Tejada, Juan Sebastian and Correal, Dario}
}
@article {1635,
	title = {Opening up to open source: looking at how Moodle was adopted in higher education},
	journal = {Open Learning: The Journal of Open, Distance and e-Learning},
	volume = {28},
	year = {2014},
	pages = {187-200},
	abstract = {The Virtual Learning Environment (VLE) has grown to become a piece of complex infrastructure that is now deemed to be critical to higher educational provision. This paper looks at Moodle and its adoption in higher education. Moodle{\textquoteright}s origins, as an open source VLE, are investigated and its growth examined in the context of how higher educational institutions adopt VLEs.

},
	issn = {1469-9958},
	doi = {10.1080/02680513.2013.856289},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Moodle-Adoption-in-Higher-Education-Eamon_Costello.pdf},
	author = {Costello, Eamon}
}
@inbook {1599,
	title = {Open-Source Software Entrepreneurial Business Modelling},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {80-82},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

This poster aims to facilitate business planning of bootstrapping entrepreneurs who are developing a high-tech business by open-source approach. It draws on scholarly works on business modelling and open-source software to provide a practical tool for entrepreneurs establishing a business by open-source approach. Built on top of established business modelling frameworks, the Open-Source Software Entrepreneurial Business Modelling (OSS_EBM) can be a useful strategic management and entrepreneurial tool. It enables strategists and entrepreneurs to describe, design, challenge, invent, brainstorm, pivot, analyze and improve upon open-source business models.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_10},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_10},
	author = {Teixeira, Jose and Salminen, Joni},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@proceedings {1569,
	title = {PAID VS. VOLUNTEER WORK IN OPEN SOURCE},
	year = {2014},
	month = {01/2014},
	pages = {3286-3295},
	publisher = {IEEE Computer Society},
	abstract = {Many open source projects have long become commercial. This paper shows just how much of open source software development is paid work and how much has remained volunteer work. Using a conservative approach, we find that about 50\% of all open source software development has been paid work for many years now and that many small projects are fully paid for by companies. However, we also find that any non-trivial project balances the amount of paid developer with volunteer work, and we suggest that the ratio of volunteer to paid work can serve as an indicator for the health of open source projects and aid the management of the respective communities.},
	doi = {10.1109/HICSS.2014.407},
	url = {http://dirkriehle.com/uploads/2013/08/paid-v8-final-web.pdf},
	author = {Dirk Riehle and Riemer, Philipp and Carsten Kolassa and Michael Schmidt}
}
@inbook {1603,
	title = {A Performance Analysis of Wireless Mesh Networks Implementations Based on Open Source Software},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {107-110},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Wireless mesh networks (WMNs) have emerged as a promising technology, capable of provide broadband connectivity at low cost. Implementations based on Open Source Software of these networks offer advantages for providing broadband networking communications in scenarios where cabling is too expensive or prohibitive such as rural environments. In this paper we evaluate the performance of small scale wireless mesh WMN routing protocols for WMNs: B.A.T.M.A.N. Advanced and the 802.11s standard. We also compare an OpenFlow controller implemented over the WMN, verifying their bandwidth, datagram loss and jitter.
},
	keywords = {network performance, Open Source Software for research and innovation, OpenFlow, OpenWRT, Wireless Mesh Networks},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_14},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_14},
	author = {Armuelles Voinov, Iv{\'a}n and Cede{\~n}o, AidelenChung and Chung, Joaqu{\'\i}n and Gonz{\'a}lez, Grace},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1616,
	title = {Polytrix: A Pacto-Powered Polyglot Test Matrix},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {191-194},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

We have created a polyglot test framework named Polytrix to compare, benchmark, and independently verify a suite of open-source OpenStack SDKs that each target a different programming language. The framework validates sample code from each SDK against a shared test scenario to validate that each SDK correctly implements a given scenario. It uses Pacto for integration contract testing between the SDKs and the OpenStack services, and generates test reports that help compare and document each SDK. It is designed so interactive training materials can be generated in future versions.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_27},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_27},
	author = {Lincoln, Max and Alves, Fernando},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1623,
	title = {PROINFODATA: Monitoring a Large Park of Computational Laboratories},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {226-229},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

This paper briefly presents a model for monitoring a large, heterogeneous and geographically scattered computer park. The data collection is performed by a software agent. The collected data are sent to the central server over the Internet, and stored by the storage system. An on-line portal makes up the visualization system, featuring charts, reports, and other tools for assessing the state of the park. This system is currently monitoring circa 150,000 machines.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_34},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_34},
	author = {Possamai, CleideL.B. and Pasqualin, Diego and Weingaertner, Daniel and Todt, Eduardo and Castilho, MarcosA. and Bona, LuisC.E. and Almeida, EduardoCunha},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Kalliamvakou:2014:PPM:2597073.2597074,
	title = {The Promises and Perils of Mining GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {92{\textendash}101},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {With over 10 million git repositories, GitHub is becoming one of the most important source of software artifacts on the Internet. Researchers are starting to mine the information stored in GitHub{\textquoteright}s event logs, trying to understand how its users employ the site to collaborate on software. However, so far there have been no studies describing the quality and properties of the data available from GitHub. We document the results of an empirical study aimed at understanding the characteristics of the repositories in GitHub and how users take advantage of GitHub{\textquoteright}s main features---namely commits, pull requests, and issues. Our results indicate that, while GitHub is a rich source of data on software development, mining GitHub for research purposes should take various potential perils into consideration. We show, for example, that the majority of the projects are personal and inactive; that GitHub is also being used for free storage and as a Web hosting service; and that almost 40\% of all pull requests do not appear as merged, even though they were. We provide a set of recommendations for software engineering researchers on how to approach the data in GitHub.
},
	keywords = {bias, code reviews, git, github, mining software repositories},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597074},
	url = {http://doi.acm.org/10.1145/2597073.2597074},
	attachments = {https://flosshub.org/sites/flosshub.org/files/perils.pdf},
	author = {Kalliamvakou, Eirini and Gousios, Georgios and Blincoe, Kelly and Singer, Leif and Daniel M. German and Damian, Daniela}
}
@conference {1687,
	title = {Recommending relevant projects via user behaviour: an exploratory study on github},
	booktitle = {Proceedings of the 1st International Workshop on Crowd-based Software Development Methods and Technologies - CrowdSoft 2014},
	year = {2014},
	pages = {25 - 30},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Hong Kong, ChinaNew York, New York, USA},
	abstract = {Social coding sites (e.g., Github) provide various features like Forking and Sending Pull-requests to support crowd-based software engineering. When using these features, a large amount of user behavior data is recorded. User behavior data can reflect developers preferences and interests in software development activities. Online service providers in many fields have been using user behavior data to discover user preferences and interests to achieve various purposes. In the field of software engineering however, there has been few studies in mining large amount of user behavior data. Our goal is to design an approach based on user behavior data, to recommend relevant open source projects to developers, which can be helpful in activities like searching for the right open source solutions to quickly build prototypes. In this paper, we explore the possibilities of such a method by conducting a set of experiments on selected data sets from Github. We find it a promising direction in mining projects{\textquoteright} relevance from user behavior data. Our study also obtain some important issues that is worth considering in this method.},
	isbn = {9781450332248},
	doi = {10.1145/2666539.2666570},
	url = {http://dl.acm.org/citation.cfm?id=2666570},
	author = {Zhang, Lingxiao and Yanzhen Zou and Bing Xie and Zixiao Zhu}
}
@conference {Pletea:2014:SES:2597073.2597117,
	title = {Security and Emotion: Sentiment Analysis of Security Discussions on GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {348{\textendash}351},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Application security is becoming increasingly prevalent during software and especially web application development. Consequently, countermeasures are continuously being discussed and built into applications, with the goal of reducing the risk that unauthorized code will be able to access, steal, modify, or delete sensitive data. In this paper we gauged the presence and atmosphere surrounding security-related discussions on GitHub, as mined from discussions around commits and pull requests. First, we found that security related discussions account for approximately 10\% of all discussions on GitHub. Second, we found that more negative emotions are expressed in security-related discussions than in other discussions. These findings confirm the importance of properly training developers to address security concerns in their applications as well as the need to test applications thoroughly for security vulnerabilities in order to reduce frustration and improve overall project atmosphere.
},
	keywords = {github, mining challenge, msr challenge, security, sentiment analysis},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597117},
	url = {http://doi.acm.org/10.1145/2597073.2597117},
	attachments = {https://flosshub.org/sites/flosshub.org/files/pletea.pdf},
	author = {Pletea, Daniel and Vasilescu, Bogdan and Serebrenik, Alexander}
}
@conference {Guzman:2014:SAC:2597073.2597118,
	title = {Sentiment Analysis of Commit Comments in GitHub: An Empirical Study},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {352{\textendash}355},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Emotions have a high impact in productivity, task quality, creativity, group rapport and job satisfaction. In this work we use lexical sentiment analysis to study emotions expressed in commit comments of different open source projects and analyze their relationship with different factors such as used programming language, time and day of the week in which the commit was made, team distribution and project approval. Our results show that projects developed in Java tend to have more negative commit comments, and that projects that have more distributed teams tend to have a higher positive polarity in their emotional content. Additionally, we found that commit comments written on Mondays tend to a more negative emotion. While our results need to be confirmed by a more representative sample they are an initial step into the study of emotions and related factors in open source projects.
},
	keywords = {Human Factors in Software Engineering, mining challenge, msr challenge, sentiment analysis},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597118},
	url = {http://doi.acm.org/10.1145/2597073.2597118},
	author = {Guzman, Emitza and Az{\'o}car, David and Li, Yang}
}
@article {1745,
	title = {SENTIMENT ANALYSIS OF FREE/OPEN SOURCE DEVELOPERS: PRELIMINARY FINDINGS FROM A CASE STUDY},
	journal = {Revista Eletr{\^o}nica de Sistemas de Informa{\c c}{\~a}o},
	volume = {13},
	year = {2014},
	month = {08/2014},
	abstract = {Software development is a human intensive activity. And as such, how developers face their tasks is of major importance. In an environment such as the one that is common in FOSS (free/open source software) projects where professionals (i.e., paid developers) share the development effort with volunteers, the morale of the development and user community is of major importance. In this paper, we present a preliminary analysis using sentiment analysis techniques to a FOSS project. We therefore mine the mailing list of a project and apply these techniques to the most relevant participants. Although the application is at this time limited, we hope that this experience can be of benefit in the future to determine situations that may affect the developers or the project, such as low productivity, developer abandonment, project forking, etc. },
	keywords = {developer productivity, FLOSS, mailing lists, natural language processing, openSUSE, sentiment analysis, software development; software repository mining},
	doi = {10.5329/RESI.2014.1302006},
	url = {http://189.16.45.2/ojs/index.php/reinfo/article/view/1677},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1677-6732-1-PB.pdf},
	author = {Rousinopoulos, Athanasios-Ilias and Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M.}
}
@booklet {1588,
	title = {The Small World Network Effect in Software Project Teams},
	year = {2014},
	note = {"This data was collected
using the freely available FLOSSmole[14]
datasets of free and open source projects. Two
datasets were analyzed {\textendash} data from from the popular
open source project site Freecode,
1 and another
from the open source software repository SourceForge.
2 The Freecode dataset contained data up
to September 2013, while the SourceForge dataset
was slightly older with data gathered up to June
2009. "},
	abstract = {Team cohesion and the dynamics of team formation are important parts of any project, with software projects being no exception. An interesting aspect of team building is the relationships formed between the team members. Because of these relationships, representing software team members as a graph may be a natural way to explore team dynamics. As team members move between projects, these graphs be- come more and more connected as team members col- laborate and form new relationships. We show that this connectivity, known as the {\textquotedblleft}small world effect,{\textquotedblright} has a positive impact on team performance when the connectivity levels are moderate. Performance de- grades, however, at both very high and very low lev- els of connectivity. This aligns with similar research findings of non-software teams.},
	keywords = {flossmole},
	url = {https://www.researchgate.net/publication/259217372_The_Small_World_Network_Effect_in_Software_Project_Teams},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kpeterson-small-world-software.pdf},
	author = {Kevin Peterson}
}
@inbook {1609,
	title = {Smart TV with Free Technologies in Support of Teaching-Learning Process},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {147-152},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

The digital divide created between Cuba and the rest of the world has forced us to use alternative technologies in order to preserve and strengthen the achievements of the Revolution in the field of education. One of the actions undertaken in this regard consists of making audiovisual equipment and media become a supplementary element of the teacher{\textquoteright}s educational work, and thus ensuring the rational use of the aforesaid media. This paper shows how to use a new trend of information technology and communications, using hybrid or smart TVs. This low-cost solution for low energy consumption, conceived as part of the educational process at all levels of the Island, provides some technical aspects and also shows, in the outline, some other ideas for incorporating this technology into the teaching-learning process. The results of laboratory tests are likewise shown.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_20},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_20},
	author = {Rosales Rosa, Eugenio and F{\'\i}rvida Don{\'e}stevez, AbelAlfonso and Gonz{\'a}lez Mu{\~n}o, Marielis and Fuentes, AllanPierra},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@mastersthesis {1718,
	title = {Social aspects of collaboration in online software communities},
	year = {2014},
	abstract = {Software engineering is inherently a collaborative venture, involving many stakeholders that coordinate their efforts to produce large software systems. In distributed (online) settings, endemic to open-source software (OSS) development, such collaborations span geographies and cultures. Contributors with different skill sets, personalities, cultural backgrounds, or geographic locations self-organise in online software communities and voluntarily contribute to a collaborative effort, such as developing and evolving software systems, offering user support, or sharing knowledge. Myriads of online software communities exist. Among the most visible are those around the Linux operating system and its various distributions, the Gnome desktop environment, the Apache or Mozilla software foundations or, more recently, the GitHub repository hosting platform, or the Stack Exchange network of question and answer sites (e.g., Stack Overflow for programming-related questions).

Different communities operate by different rules and offer different incentives to contribute. More traditional communities such as Gnome or Apache rely mostly on the intrinsic motivations of developers. In contrast, younger communities offer social media and gamification features (e.g., contributors to Stack Overflow are rewarded for their activity with reputation points and badges) as well as increased visibility to peers (e.g., the activity and achievements of GitHub and Stack Overflow contributors are aggregated and displayed on public profile pages). Furthermore, online software communities are often interdependent. For example, a Gnome contributor may engage simultaneously in different communities part of the Gnome ecosystem, where she may take on different roles or instead choose to specialise in similar tasks. Similarly, a GitHub contributor may participate simultaneously in Stack Overflow, where she may seek help from peers or instead share her knowledge and expertise to help educate others.

Starting from the recent realisation of the empirical software engineering research community that social aspects are at least as important for the success of distributed collaborations as technical ones, this dissertation is an attempt to understand collaboration in representative online software communities from a social perspective. To this end, we mines and analyses a wealth of publicly available trace data using state-of-the-art statistical techniques, from various standpoints outlined below. The work in this dissertation sits at the intersection of two research communities, computer-supported cooperative work (CSCW) and software engineering (SE). Consequently, it offers contributions to both SE and CSCW, ranging from methods and tools to mine and analyse large amounts of (social) trace data, to practical implications for software maintainability, software team management, knowledge management or community design.

First, we propose individual-level measures of workload, involvement, and specialisation of labour in online software development communities, and report on a case study of the Gnome ecosystem community. Additionally, we propose a community-level measure of skill diversity with respect to a certain technical skill, such as knowledge of a given programming language. Social interactions between contributors to software development communities and their degree of participation have been reported repeatedly to influence software quality and complexity. Similarly, skill heterogeneity in a software community is important for the community{\textquoteright}s survival and performance.

Second, we analyse the effects of simultaneously contributing to multiple communities on individual working rhythms. We focus on developers contributing source code to GitHub repositories while seeking and sharing knowledge on Stack Overflow. Despite the popularity of Stack Overflow, its role in the work cycle of OSS developers is yet to be understood. On the one hand, participation in it has the potential to increase the knowledge of individual developers thus improving and speeding up the development process. On the other hand, participation in Stack Overflow may interrupt the regular working rhythm of a developer, hence also possibly slow down the development process. We show that active GitHub contributors typically engage in Stack Overflow as experts, asking few questions and providing many answers for others. Moreover, despite the interruptions incurred, the Stack Overflow activity rate correlates with the code changing rate on GitHub.

Third, we chart the changes in behaviour of contributors to online knowledge sharing communities as they migrate into gamified environments. To this end, we assemble a joint data set for R (a widely-used tool for data analysis) by integrating data from mailing lists and Stack Exchange sites, having activities of individual contributors linked across the two resources and also over time. We find that user support activities show a strong shift away from mailing lists (historically the hub for development and user support activities in online software communities) and towards Stack Exchange. Moreover, knowledge providers contributing to both communities provide faster answers on Stack Exchange than on the mailing list, and their total output increases after the transition.

Fourth, we revisit the gamified Stack Overflow environment from the perspectives of gender representation and participation patterns, in comparison to traditional information sharing venues such as mailing lists. In addition to encouraging competitiveness through its gamification features, anecdotal evidence around Stack Overflow suggests that it is an unfriendly community that promotes one-upmanship, or fosters flame-wars and the down-voting of individuals. We find that while women are under-represented in all studied communities, they show different participation patterns on Stack Overflow, where they disengage sooner than men. However, relative to the duration of their engagement in the community, women on Stack Overflow are at least as active as men.

Fifth, we address the recurring mining software repositories challenge of inconsistent identity data. To this end, we analyse the robustness of two representative existing identity merging algorithms with respect to different types of noise typical of software repositories, and we propose a new identity merging algorithm inspired by Latent Semantic Analysis, a popular information retrieval technique expected to perform well in presence of noise. Using data extracted from Gnome Git repositories, we evaluate the performance of our algorithm empirically by means of cross-validation, and show an improvement over existing approaches in terms of precision and recall on worst-case input data.

Last, we provide an example of the applicability of methods developed or refined as part of this work beyond online software communities. Specifically, we propose a metrics suite to study the health of software engineering conferences and conference communities, measuring such attributes as stability, openness to new authors, or introversion. Using this metrics suite, we assess the health of 11 established software engineering conferences over a period of more than 10 years. In general, we find that software engineering conferences are healthy, with some notable differences depending on the chosen health metric, or a conference{\textquoteright}s wide or narrow scope. Beyond demonstrating the generalisability of our techniques, this latter study has implications for conference steering committees or program committee chairs wishing to assess their selection process, or prospective authors trying to decide in which conferences to publish.},
	url = {http://www.win.tue.nl/ipa/?event=social-aspects-of-collaboration-in-online-software-communities},
	author = {Vasilescu, Bogdan}
}
@mastersthesis {1719,
	title = {Social aspects of collaboration in online software communities},
	year = {2014},
	abstract = {Software engineering is inherently a collaborative venture, involving many stakeholders that coordinate their efforts to produce large software systems. In distributed (online) settings, endemic to open-source software (OSS) development, such collaborations span geographies and cultures. Contributors with different skill sets, personalities, cultural backgrounds, or geographic locations self-organise in online software communities and voluntarily contribute to a collaborative effort, such as developing and evolving software systems, offering user support, or sharing knowledge. Myriads of online software communities exist. Among the most visible are those around the Linux operating system and its various distributions, the Gnome desktop environment, the Apache or Mozilla software foundations or, more recently, the GitHub repository hosting platform, or the Stack Exchange network of question and answer sites (e.g., Stack Overflow for programming-related questions).

Different communities operate by different rules and offer different incentives to contribute. More traditional communities such as Gnome or Apache rely mostly on the intrinsic motivations of developers. In contrast, younger communities offer social media and gamification features (e.g., contributors to Stack Overflow are rewarded for their activity with reputation points and badges) as well as increased visibility to peers (e.g., the activity and achievements of GitHub and Stack Overflow contributors are aggregated and displayed on public profile pages). Furthermore, online software communities are often interdependent. For example, a Gnome contributor may engage simultaneously in different communities part of the Gnome ecosystem, where she may take on different roles or instead choose to specialise in similar tasks. Similarly, a GitHub contributor may participate simultaneously in Stack Overflow, where she may seek help from peers or instead share her knowledge and expertise to help educate others.

Starting from the recent realisation of the empirical software engineering research community that social aspects are at least as important for the success of distributed collaborations as technical ones, this dissertation is an attempt to understand collaboration in representative online software communities from a social perspective. To this end, we mines and analyses a wealth of publicly available trace data using state-of-the-art statistical techniques, from various standpoints outlined below. The work in this dissertation sits at the intersection of two research communities, computer-supported cooperative work (CSCW) and software engineering (SE). Consequently, it offers contributions to both SE and CSCW, ranging from methods and tools to mine and analyse large amounts of (social) trace data, to practical implications for software maintainability, software team management, knowledge management or community design.

First, we propose individual-level measures of workload, involvement, and specialisation of labour in online software development communities, and report on a case study of the Gnome ecosystem community. Additionally, we propose a community-level measure of skill diversity with respect to a certain technical skill, such as knowledge of a given programming language. Social interactions between contributors to software development communities and their degree of participation have been reported repeatedly to influence software quality and complexity. Similarly, skill heterogeneity in a software community is important for the community{\textquoteright}s survival and performance.

Second, we analyse the effects of simultaneously contributing to multiple communities on individual working rhythms. We focus on developers contributing source code to GitHub repositories while seeking and sharing knowledge on Stack Overflow. Despite the popularity of Stack Overflow, its role in the work cycle of OSS developers is yet to be understood. On the one hand, participation in it has the potential to increase the knowledge of individual developers thus improving and speeding up the development process. On the other hand, participation in Stack Overflow may interrupt the regular working rhythm of a developer, hence also possibly slow down the development process. We show that active GitHub contributors typically engage in Stack Overflow as experts, asking few questions and providing many answers for others. Moreover, despite the interruptions incurred, the Stack Overflow activity rate correlates with the code changing rate on GitHub.

Third, we chart the changes in behaviour of contributors to online knowledge sharing communities as they migrate into gamified environments. To this end, we assemble a joint data set for R (a widely-used tool for data analysis) by integrating data from mailing lists and Stack Exchange sites, having activities of individual contributors linked across the two resources and also over time. We find that user support activities show a strong shift away from mailing lists (historically the hub for development and user support activities in online software communities) and towards Stack Exchange. Moreover, knowledge providers contributing to both communities provide faster answers on Stack Exchange than on the mailing list, and their total output increases after the transition.

Fourth, we revisit the gamified Stack Overflow environment from the perspectives of gender representation and participation patterns, in comparison to traditional information sharing venues such as mailing lists. In addition to encouraging competitiveness through its gamification features, anecdotal evidence around Stack Overflow suggests that it is an unfriendly community that promotes one-upmanship, or fosters flame-wars and the down-voting of individuals. We find that while women are under-represented in all studied communities, they show different participation patterns on Stack Overflow, where they disengage sooner than men. However, relative to the duration of their engagement in the community, women on Stack Overflow are at least as active as men.

Fifth, we address the recurring mining software repositories challenge of inconsistent identity data. To this end, we analyse the robustness of two representative existing identity merging algorithms with respect to different types of noise typical of software repositories, and we propose a new identity merging algorithm inspired by Latent Semantic Analysis, a popular information retrieval technique expected to perform well in presence of noise. Using data extracted from Gnome Git repositories, we evaluate the performance of our algorithm empirically by means of cross-validation, and show an improvement over existing approaches in terms of precision and recall on worst-case input data.

Last, we provide an example of the applicability of methods developed or refined as part of this work beyond online software communities. Specifically, we propose a metrics suite to study the health of software engineering conferences and conference communities, measuring such attributes as stability, openness to new authors, or introversion. Using this metrics suite, we assess the health of 11 established software engineering conferences over a period of more than 10 years. In general, we find that software engineering conferences are healthy, with some notable differences depending on the chosen health metric, or a conference{\textquoteright}s wide or narrow scope. Beyond demonstrating the generalisability of our techniques, this latter study has implications for conference steering committees or program committee chairs wishing to assess their selection process, or prospective authors trying to decide in which conferences to publish.},
	url = {http://www.win.tue.nl/ipa/?event=social-aspects-of-collaboration-in-online-software-communities}
}
@conference {Syeed:2014:SCR:2641580.2641586,
	title = {Socio-Technical Congruence in the Ruby Ecosystem},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {2:1{\textendash}2:9},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Existing studies show that open source projects may enjoy high levels of socio-technical congruence despite their open and distributed character. Such observations are yet to be confirmed in the case of larger open source ecosystems in which developers contribute to different projects within the ecosystem. In this paper, we empirically study the relationships between the developer coordination activities and the project dependency structure in the Ruby ecosystem. Our motivation is to verify whether the ecosystem context maintains the high socio-technical congruence levels observed in many smaller scale FLOSS (Free/Libre Open Source Software) projects. Our study results show that the collaboration pattern among the developers in Ruby ecosystem is not necessarily shaped by the communication needs indicated by the dependencies among the ecosystem projects.
},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641586},
	url = {http://doi.acm.org/10.1145/2641580.2641586},
	author = {Syeed, M.M. Mahbubul and Hansen, Klaus Marius and Hammouda, Imed and Manikas, Konstantinos}
}
@conference {Vasilescu:2014:SDH:2556420.2556833,
	title = {Software Developers Are Humans, Too!},
	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 = {97{\textendash}100},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open-source communities can be seen as knowledge-sharing ecosystems: participants learn from the community and from one another, and share their knowledge through contributions to the source code repositories or by offering support to users. With the emergence and growing popularity of social media sites targeting software developers (e.g., StackOverflow, GitHub), the paths through which knowledge flows within open-source software knowledge-sharing ecosystems are also beginning to change. My dissertation research seeks to raise our understanding of these changes.},
	keywords = {human aspects, open-source, software developers},
	isbn = {978-1-4503-2541-7},
	doi = {10.1145/2556420.2556833},
	url = {http://doi.acm.org/10.1145/2556420.2556833},
	author = {Vasilescu, Bogdan}
}
@article {1716,
	title = {Sourcerer: An infrastructure for large-scale collection and analysis of open-source code},
	journal = {Science of Computer Programming},
	volume = {79},
	year = {2014},
	month = {1/2014},
	pages = {241 - 259},
	abstract = {A large amount of open source code is now available online, presenting a great potential resource for software developers. This has motivated software engineering researchers to develop tools and techniques to allow developers to reap the benefits of these billions of lines of source code. However, collecting and analyzing such a large quantity of source code presents a number of challenges. Although the current generation of open source code search engines provides access to the source code in an aggregated repository, they generally fail to take advantage of the rich structural information contained in the code they index. This makes them significantly less useful than Sourcerer for building state-of-the-art software engineering tools, as these tools often require access to both the structural and textual information available in source code.We have developed Sourcerer, an infrastructure for large-scale collection and analysis of open source code. By taking full advantage of the structural information extracted from source code in its repository, Sourcerer provides a foundation upon which state-of-the-art search engines and related tools can easily be built. We describe the Sourcerer infrastructure, present the applications that we have built on top of it, and discuss how existing tools could benefit from using Sourcerer.},
	issn = {01676423},
	doi = {10.1016/j.scico.2012.04.008},
	author = {Bajracharya, Sushil and Ossher, Joel and Lopes, Cristina}
}
@proceedings {1570,
	title = {Structural Changes Associated with the Temporal Dispersion of Teams: Evidence from Open Source Software Projects},
	year = {2014},
	month = {01/2014},
	pages = {300-309},
	publisher = {IEEE Computer Society},
	abstract = {This study relies on Media Synchronicity Theory and Social Network Analysis to analyze how the structure of collaboration networks change when collaborating teams become temporally dispersed. The empirical test of hypotheses using ordinary least squares with archival data from 230 Open Source Software projects shows that the collaboration structure networks of more temporally dispersed teams are sparser and more centralized, and these associations are stronger in those teams exhibiting higher relative performance.},
	doi = {10.1109/HICSS.2014.45},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HICSS47\%20Structural\%20Changes\%20vs\%20TD\%20FINAL.pdf},
	author = {Colazo, Jorge A.}
}
@conference {Padhye:2014:SEC:2597073.2597113,
	title = {A Study of External Community Contribution to Open-source Projects on GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {332{\textendash}335},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open-source software projects are primarily driven by community contribution. However, commit access to such projects{\textquoteright} software repositories is often strictly controlled. These projects prefer to solicit external participation in the form of patches or pull requests. In this paper, we analyze a set of 89 top-starred GitHub projects and their forks in order to explore the nature and distribution of such community contribution. We first classify commits (and developers) into three categories: core, external and mutant, and study the relative sizes of each of these classes through a ring-based visualization. We observe that projects written in mainstream scripting languages such as JavaScript and Python tend to include more external participation than projects written in upcoming languages such as Scala. We also visualize the geographic spread of these communities via geocoding. Finally, we classify the types of pull requests submitted based on their labels and observe that bug fixes are more likely to be merged into the main projects as compared to feature enhancements.
},
	keywords = {community participation, core committers, external contribution, mining challenge, mining software repositories, msr challenge, Open-source software, pull requests},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597113},
	url = {http://doi.acm.org/10.1145/2597073.2597113},
	author = {Padhye, Rohan and Mani, Senthil and Sinha, Vibha Singhal}
}
@inbook {1621,
	title = {A Study of the Effect on Business Growth by Utilization and Contribution of Open Source Software in Japanese IT Companies},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {216-217},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

To analyze how OSS effects business growth both through simple use and by deeper engagement as a stakeholder in OSS community, we did questionnaire research to Japanese IT companies in 2012 and 2013. We analyze the progress of utilization and contribution of OSS, and the impact on business growth indicators by them.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_32},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_32},
	author = {Noda, Tetsuo and Tansho, Terutaka},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@article {thomas2014studying,
	title = {Studying software evolution using topic models},
	journal = {Science of Computer Programming},
	volume = {80},
	year = {2014},
	pages = {457{\textendash}479},
	publisher = {Elsevier},
	abstract = {Topic models are generative probabilistic models which have been applied to information
retrieval to automatically organize and provide structure to a text corpus. Topic models
discover topics in the corpus, which represent real world concepts by frequently cooccurring
words. Recently, researchers found topics to be effective tools for structuring
various software artifacts, such as source code, requirements documents, and bug reports.
This research also hypothesized that using topics to describe the evolution of software
repositories could be useful for maintenance and understanding tasks. However, research
has yet to determine whether these automatically discovered topic evolutions describe the
evolution of source code in a way that is relevant or meaningful to project stakeholders, and
thus it is not clear whether topic models are a suitable tool for this task.
In this paper, we take a first step towards evaluating topic models in the analysis of
software evolution by performing a detailed manual analysis on the source code histories
of two well-known and well-documented systems, JHotDraw and jEdit. We define and
compute various metrics on the discovered topic evolutions and manually investigate how
and why the metrics evolve over time. We find that the large majority (87\%{\textendash}89\%) of topic
evolutions correspond well with actual code change activities by developers. We are thus
encouraged to use topic models as tools for studying the evolution of a software system.},
	keywords = {Latent Dirichlet allocation, mining software repositories, software evolution, topic model},
	url = {http://sail.cs.queensu.ca/publications/pubs/Thomas-2012-SCP.pdf},
	author = {Stephen W. Thomas and Adams, Bram and Hassan, Ahmed E. and Blostein, Dorothea}
}
@inbook {1608,
	title = {A Successful OSS Adaptation and Integration in an e-Learning Platform: TEC Digital},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {143-146},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

E-learning projects in many universities are focused on adapting or installing a software platform to upload teaching materials and sometimes to open discussion forums. However, it is totally possible to extend the learning management system (LMS) as a complete service platform for students and instructors including more advanced services. This paper shows the progressive integration of services and applications in TEC Digital as the open source e-learning platform of the Costa Rica Institute of Technology. This integration experience could be used as a case of study for other universities.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_19},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_19},
	author = {Chacon-Rivas, Mario and Garita, Cesar},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@proceedings {1571,
	title = {Theorizing Modes of Open Source Software Development},
	year = {2014},
	month = {01/2014},
	pages = {4568-4577},
	publisher = {IEEE Computer Society},
	abstract = {Open Source Software (OSS) development is distributed across actors and artifacts and involves translating diffuse representations into distinct sets of contiguous code artifacts. Despite the highly distributed and dynamic nature of OSS development, it is often described in unitary, monolithic terms {\textendash} an unfortunate situation which masks considerable variance across OSS development processes. Therefore we explore reasons for systematic variance in these processes so as to enable more effective OSS development practices. Drawing on theory of distributed cognition, we develop a language of cognitive translations, which occur within and across distributed social arrangements and structural conditions of sharing knowledge. This language provides micro-foundations for understanding how different modes of OSS development emerge. Through examining how generative characteristics of social and structural distributions in OSS shape distinct development pathways, we propose a theoretically derived typology explaining the characteristics, dynamics, and conditions for success of different modes of OSS development.},
	doi = {10.1109/HICSS.2014.560},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Theorizing\%20Modes\%20of\%20Open\%20Source\%20Software\%20Development.pdf},
	author = {Aron Lindberg and Xuan Xiao and Kalle Lyytinen}
}
@inbook {1600,
	title = {Towards Understanding of Structural Attributes of Web APIs Using Metrics Based on API Call Responses},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {83-92},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

The latest trend across different industries is to move towards (open) web APIs. Creating a successful API, however, is not easy. A lot depends on consumers and their interest and willingness to work with the exposed interface. Structural quality, learning difficulty, design consistency, and backwards compatibility are some of the important factors in this process. The question, however, is how one can measure and track such attributes. This paper presents the beginnings of a measurement framework for web APIs that is based on the information readily available both to API providers and API consumers - API call responses. In particular, we analyze the tree-based hierarchical structure of JSON and XML data returned from API calls. We propose a set of easy-to-compute metrics as a starting point and describe sample usage scenarios. These metrics are illustrated by examples from some of the popular open web APIs.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_11},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_11},
	author = {Janes, Andrea and Remencius, Tadas and Sillitti, Alberto and Succi, Giancarlo},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@mastersthesis {1641,
	title = {Understanding contributor behaviour within Free/Libre/Open Source Software communities: A socialization perspective},
	year = {2014},
	abstract = {Attracting a large number of new contributors has been seen as a way to ensure the survival, long-term success, and sustainability of Free/Libre/Open Source Software (FLOSS) communities. However, this appears to be a necessary, but not a sufficient condition, as the well-being of FLOSS communities also relies on members performing behaviours that nurture and protect the community.
 Despite a large body of research on FLOSS communities, few studies have been undertaken to explore the influence of a participant{\textquoteright}s socialization experience on their contribution behaviour. In addition, there has been relatively little research that has adopted a community-level view of FLOSS community participants{\textquoteright} contribution that goes beyond the mere notion of writing lines of code.
 The purpose of this study is to develop and rigorously test a socialization model that predicts contributor behaviour in the FLOSS community context.
 Drawing upon theories of socialization and citizenship behaviours from organizational behaviour research, this research develops and tests two separate but related research models. The first model proposes the direct impact of socialization factors on two performance-related dependent variables: task performance and community citizenship behaviours. The second model hypothesizes a mediating effect of two proximal socialization variables, social identification and social integration, between the socialization factors and the dependent variables.
 An exploratory study involving eleven FLOSS community leaders, managers, and experienced members was first conducted, to investigate the key variables that characterize FLOSS community newcomer socialization experience as well as the various instances of citizenship behaviours that are specific to the FLOSS community context. The analysis of the interview data revealed the existence of six socialization variables: task segregation, task purposefulness, interaction intensity, mentoring, joining structuredness, and supportiveness. Two sets of FLOSS community citizenship behaviours (CCB) were identified drawing on the citizenship behaviour literature. The first set, labelled CCB-I, comprised citizenship behaviours directed towards the benefit of individuals. The second set, CCB-P, included citizenship behaviours directed towards the benefit of the project. The findings were integrated in the two conceptual models.
 Subsequently, a research instrument was developed, following an extensive purification process that consisted of card sorting and expert review rounds, and a survey pretest. A pilot study assessed responses from 46 FLOSS contributors from two large FLOSS communities. Overall, the scales demonstrated high reliability and showed adequate construct validity. The analysis of the pilot study suggested the existence of a third CCB dimension, named CCB-C, that characterizes citizenship behaviours that are oriented towards the benefit of a project{\textquoteright}s community.
 The main study was based on an online survey involving 327 respondents from twelve large FLOSS communities. Using Partial Least Squares (PLS), the collected data was used to test the two models. The results showed the overall superior predictive capability of the model hypothesizing the mediating effect of both social identification and social integration.
 Task performance was found to be directly predicted by task purposefulness as well as by interaction intensity and supportiveness through the mediation of social identification. Meanwhile, CCB was found to be impacted by the direct effect of task segregation and task purposefulness, and by interaction intensity and supportiveness through the mediation of both social identification and social integration. The existence of the third CCB dimension, CCB-C, was confirmed.},
	url = {http://hdl.handle.net/10063/3378},
	author = {Carillo, Kevin Daniel Andre}
}
@article {1817,
	title = {Understanding Contributor to Developer Turnover Patterns in OSS Projects: A Case Study of Apache Projects},
	journal = {ISRN Software Engineering},
	volume = {201411},
	year = {2014},
	month = {2014},
	pages = {1 - 10},
	abstract = {OSS projects are dynamic in nature. Developers
contribute to a project for a certain period of time and later
leave the project or join other projects of high interest. Hence,
the OSS community always welcomes members who can attain
the role of a developer in a project. In this paper, we investigate
contributions made by members who have attained the role of
a developer. In particular, we study the contributions made by
the members in terms of bugs reported, comments on bugs,
source-code patch submissions, and their social relation with
other members of an OSS community. Further, we study the
significance of nondevelopers contribution and investigate if
and to what extent they play a role in the long-term survival
of an OSS project. Moreover, we investigate the ratio of
contributions made by a member before and after attaining
the role of a developer. We have outlined 4 research questions
in this regard and further discuss our findings based on the
research questions by taking into account data from software
repositories of 4 different Apache projects.},
	keywords = {apache},
	doi = {10.1155/2014/535724},
	author = {Iqbal, Aftab}
}
@conference {Teixeira:2014:UCO:2641580.2641627,
	title = {Understanding Coopetition in the Open-Source Arena: The Cases of WebKit and OpenStack},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {39:1{\textendash}39:5},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In an era of software crisis, the move of firms towards distributed software development teams is being challenged by emerging collaboration issues. On this matter, the open-source phenomenon may shed some light, as successful cases on distributed collaboration in the open-source community have been recurrently reported. In our research we explore collaboration networks in the WebKit and OpenStack high-networked open-source projects, by mining their source-code version-control-systems data with Social Network Analysis (SNA). Our approach allows us to observe how key events in the industry affect open-source collaboration networks over time. With our findings, we highlight the explanatory power from network visualizations capturing the collaborative dynamics of high-networked software projects over time. Moreover, we argue that competing companies that sell similar products in the same market, can collaborate in the open-source community while publicly manifesting intense rivalry (e.g. Apple vs Samsung patent-wars). After integrating our findings with the current body of theoretical knowledge in management strategy, economics, strategic alliances and coopetition, we propose the novel notion of open-coopetition, where rival firms collaborate with competitors in the open-source community. We argue that classical coopetition management theories do not fully explain the competitive and collaborative issues that are simultaneously present and interconnected in the WebKit and OpenStack open-source communities. We propose the development of the novel open-coopetition theory for a better understanding on how rival-firms collaborate with competitors by open-source manners.
},
	keywords = {COLLABORATION, Competition, Coopetition, Ecosystems, FLOSS, Open-Coopetition, open-source, OSS, Strategic Alliances},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641627},
	url = {http://doi.acm.org/10.1145/2641580.2641627},
	author = {Teixeira, Jose}
}
@conference {Sheoran:2014:UWG:2597073.2597114,
	title = {Understanding "Watchers" on GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {336{\textendash}339},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Users on GitHub can watch repositories to receive notifications about project activity. This introduces a new type of passive project membership. In this paper, we investigate the behavior of watchers and their contribution to the projects they watch. We find that a subset of project watchers begin contributing to the project and those contributors account for a significant percentage of contributors on the project. As contributors, watchers are more confident and contribute over a longer period of time in a more varied way than other contributors. This is likely attributable to the knowledge gained through project notifications.
},
	keywords = {github, mining challenge, msr challenge, repositories, Software Teams, Watchers},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597114},
	url = {http://doi.acm.org/10.1145/2597073.2597114},
	author = {Sheoran, Jyoti and Blincoe, Kelly and Kalliamvakou, Eirini and Damian, Daniela and Ell, Jordan}
}
@inbook {1622,
	title = {USB Device Management in GNU/Linux Systems},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {218-225},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Protecting the access to USB ports has the same priority for information security than firewalls and antivirus software. Nowadays there are some tools that allow us to monitor and regulate the access to USB devices, but all of them are distributed under proprietary licenses. This work presents an application that solves the mentioned problem: ?{\textquoteright}How controlling the access to USB mass storage devices in GNU/Linux Operating Systems?
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_33},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_33},
	author = {Deroncel{\'e}, EdilbertoBlez and Fuentes, AllanPierra and Tejera Hern{\'a}ndez, DayanaCaridad and C{\'a}ceres Navarro, Haniel and F{\'\i}rvida Donest{\'e}vez, AbelAlfonso and Febles Parker, MichelEvaristo},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1604,
	title = {Use of Open Software Tools for Data Offloading Techniques Analysis on Mobile Networks},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {111-112},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

This research aims to highlight the benefits of using free software based tools for studying a LTE mobile network with realistic parameters. We will overload this LTE network and offload it through data offloading techniques such as small cells and WiFi offload. For this research, discreteevent open software network simulator ns3 will be implemented. Ns3 is a network simulator based on the programming language C++, and has all the necessary libraries to simulate an LTE and WiFi network.
},
	keywords = {Data Offloading, LTE, ns3, OSS for research and education, small cells, WiFi},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_15},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_15},
	author = {Koo, Jos{\'e}M. and Espino, JuanP. and Armuelles, Iv{\'a}n and Villarreal, Rub{\'e}n},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Barcomb:2014:VAR:2641580.2641628,
	title = {Volunteer Attraction and Retention in Open Source Communities},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {40:1{\textendash}40:2},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The importance of volunteers in open source has led to the position of community manager becoming more common in foundations and projects. Yet the advice for volunteer management and retention is fragmented, incomplete, contradictory, and has not been empirically examined. Our aim is to fill this gap by creating a comprehensive guidebook of best practices drawing from open source practitioner guides and general literature on volunteering, and to subject a subset of practices to empirical study. A method for evaluating volunteer attrition in terms of value to the organization will also be developed.
},
	keywords = {Community Management, FLOSS, open source, Recruitment, Service Duration, Volunteer Management, Volunteer Retention, Volunteers},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641628},
	url = {http://doi.acm.org/10.1145/2641580.2641628},
	author = {Barcomb, Ann}
}
@inbook {1626,
	title = {When Are OSS Developers More Likely to Introduce Vulnerable Code Changes? A Case Study},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {234-236},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

We analyzed peer code review data of the Android Open Source Project (AOSP) to understand whether code changes that introduce security vulnerabilities, referred to as vulnerable code changes (VCC), occur at certain intervals. Using a systematic manual analysis process, we identified 60 VCCs. Our results suggest that AOSP developers were more likely to write VCCs prior to AOSP releases, while during the post-release period they wrote fewer VCCs.
},
	keywords = {FOSS, open source, OSS, security, vulnerability},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_37},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_37},
	author = {Bosu, Amiangshu and Carver, JeffreyC. and Hafiz, Munawar and Hilley, Patrick and Janni, Derek},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1593,
	title = {Who Contributes to What? Exploring Hidden Relationships between FLOSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {21-30},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {In this paper we address the challenge of tracking resembling open source projects by exploiting the information of which developers contribute to which projects. To do this, we have performed a social network study to analyze data collected from the Ohloh repository. Our findings suggest that the more shared contributors two projects have, the more likely they resemble with respect to properties such as project application domain, programming language used and project size.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_3},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_3},
	author = {Syeed, M.M.Mahbubul and Hammouda, Imed},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {hannemann2013adaptive,
	title = {An Adaptive Filter-Framework for the Quality Improvement of Open-Source Software Analysis.},
	booktitle = {Software Engineering},
	year = {2013},
	pages = {143{\textendash}156},
	publisher = {Citeseer},
	organization = {Citeseer},
	abstract = {Knowledge mining in Open-Source Software (OSS) brings a great benefit
for software engineering (SE). The researchers discover, investigate, and even simulate
the organization of development processes within open-source communities in
order to understand the community-oriented organization and to transform its advantages
into conventional SE projects. Despite a great number of different studies on
OSS data, not much attention has been paid to the data filtering step so far. The noise
within uncleaned data can lead to inaccurate conclusions for SE. A special challenge
for data cleaning presents the variety of communicational and development infrastructures
used by OSS projects. This paper presents an adaptive filter-framework supporting
data cleaning and other preprocessing steps. The framework allows to combine
filters in arbitrary order, defining which preprocessing steps should be performed. The
filter-portfolio can by extended easily. A schema matching in case of cross-project
analysis is available. Three filters - spam detection, quotation elimination and core periphery
distinction - were implemented within the filter-framework. In the analysis
of three large-scale OSS projects (BioJava, Biopython, BioPerl), the filtering led to
a significant data modification and reduction. The results of text mining (sentiment
analysis) and social network analysis on uncleaned and cleaned data differ significantly, confirming the importance of the data preprocessing step within OSS empirical
studies.},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.437.5602\&rep=rep1\&type=pdf$\#$page=143},
	author = {Hannemann, Anna and Hackstein, Michael and Klamma, Ralf and Jarke, Matthias}
}
@article {1642,
	title = {All complaints are not created equal: text analysis of open source software defect reports},
	journal = {Empirical Software Engineering},
	volume = {18},
	year = {2013},
	month = {2/2013},
	pages = {117 - 138},
	abstract = {As the use of Open Source Software (OSS) systems increases in the corporate environment, it is important to examine the maintenance process of these projects. OSS projects allow end users to directly submit reports in case of any operational issues. Timely resolution of these defect reports requires effective management of maintenance resources. This study analyzes the usefulness of the textual content of the defect reports as an early indicator of their resolution time. Text Mining techniques are used to categorize defect reports of five OSS projects. Significant variation in the defect resolution time amongst the resulting categories, for each of the sample projects, indicates that a text based classification of defect reports can be useful in early assessment of resolution time before source code level analysis. Such technique can assist in allocation of sufficient maintenance resources to targeted defects and also enable project teams to manage customer expectations regarding defect resolution times.
},
	issn = {1573-7616},
	doi = {10.1007/s10664-012-9197-9},
	author = {Raja, Uzma}
}
@proceedings {1552,
	title = {Analyzing Social Behavior of Software Developers Across Different Communication Channels},
	year = {2013},
	abstract = {Software developers use different project repositories (i.e., mailing list, bug tracking repositories, discussion forums etc.) to interact with each other or to solve software related problems. The growing interest in the usage of social media channels (i.e., Twitter, Facebook, LinkedIn) have also attracted the open source software community and software developers to adopt an identity in order to disseminate project-related information to a wider audience. Much research has been carried out to analyze the social behavior of software developers in different project repositories but so far no one has tried to study the social communication patterns of developers in other social media channels. We in this paper presents a new dimension to the social aspects of software developers and study if the social communication patterns of software developers is different on project repositories and social media channels (i.e., Twitter).},
	keywords = {communication, developer, social media},
	url = {http://index.ksi.edu/conf/seke/2013/cr/296.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/iqbal_a_et_al_june_2013.pdf},
	author = {Iqbal, Aftab and M Karnstedt and M Hausenblas}
}
@proceedings {1503,
	title = {Apache Commits: Social Network Dataset},
	year = {2013},
	month = {05/2013},
	abstract = {Building non-trivial software is a social endeavor. Therefore, understanding the social network of developers is key to the study of software development organizations. We present a graph representation of the commit behavior of developers within the Apache Software Foundation for 2010 and 2011. Relationships between developers in the network represent collaborative commit behavior. Several similarity and summary metrics have been pre-calculated. The data, along with the tools that were used to create it and some further discussion, can be found at: http://sequoia.cs.byu.edu/lab/?page=artifacts/apacheGraphs},
	author = {MacLean, Alexander C. and Knutson, Charles D.}
}
@proceedings {1488,
	title = {Apache-Affiliated Twitter Screen Names: A Dataset},
	year = {2013},
	month = {05/2013},
	abstract = {This paper describes a new dataset containing Twitter screen names for members of the projects affiliated with the Apache Software Foundation (ASF). The dataset includes the confirmed Twitter screen names, as well as the real name as listed on Twitter, and the user identification as used within the Apache organization. The paper also describes the process used to collect and clean this data, and shows some sample queries for learning how to use the data. The dataset has been donated to the FLOSSmole project and is available for download (https://code. google.com/p/flossmole/downloads/detail?name=apacheTwitter2013-Jan.zip) or direct querying via a database client. },
	keywords = {apache, dataset, twitter},
	attachments = {https://flosshub.org/sites/flosshub.org/files/apacheTwitterPREPRINT.pdf , https://flosshub.org/sites/flosshub.org/files/MSR\%20presentation.pdf},
	author = {Squire, Megan}
}
@conference {Paschalidou:2013:ADE:2490257.2490264,
	title = {An application of data envelopment analysis to software quality assessment},
	booktitle = {Proceedings of the 6th Balkan Conference in Informatics},
	series = {BCI {\textquoteright}13},
	year = {2013},
	pages = {228{\textendash}235},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Data Envelopment Analysis (DEA) is a non-parametric technique which involves the use of linear programming methods to measure the efficiency of a homogenous set of units. These units are known as Decision Making Units (DMUs) and defined by multiple input and output data. Efficiencies are measured relative to a piece-wise surface (efficient frontier) which envelops the data, thus justifying the name of the technique. Although DEA has been mostly used in production economics, its application in the context of software quality evaluation seems to be a promising approach. This study provides an application of DEA to assess the evolution of two open-source software projects in terms of selected metric values for successive versions of each project. What is really interesting in DEA is that a single efficiency score is calculated for each version despite the often convoluted overall picture of the metric values. According to a simplified view of DEA, there are two categories of units, the efficient (onto the efficient frontier) and the inefficient ones. Each inefficient unit is characterized by a reference set of peers which involves all the efficient units "operating" closer to that unit. Through the consideration of the reference set of the inefficient versions of each project, the metrics that require improvement, as well as the extent of improvement, could be estimated. These results could assist software developers in identifying design issues that require further improvement. Notwithstanding the fact that there are a number of issues to be further investigated, the applicability of DEA and other operations research tools in the context of software quality might yield interesting results.
},
	keywords = {dea, design metrics, software evolution, software quality},
	isbn = {978-1-4503-1851-8},
	doi = {10.1145/2490257.2490264},
	url = {http://doi.acm.org/10.1145/2490257.2490264},
	author = {Paschalidou, Georgia and Stiakakis, Emmanouil and Chatzigeorgiou, Alexander}
}
@conference {1559,
	title = {Applying a Rule-Based Natural Language Classifier to Open Source Requirements: a Demonstration of Theory Exploration},
	booktitle = {2013 46th Hawaii International Conference on System Sciences (HICSS)2013 46th Hawaii International Conference on System Sciences},
	year = {2013},
	pages = {3158 - 3167},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Wailea, HI, USA},
	abstract = {Open source projects requirements are mostly informal, text descriptions found in requests, forums, and other correspondence. Understanding of such requirements can provide insight into the nature of open source projects. Previously, we have demonstrated the Requirements Classifier for Natural Language (RCNL), which aids in NL requirements analysis. Herein, we demonstrate how the RCNL can aid in theory building. From its application to 16 open source projects, we conjecture a simple wave theory of requirements innovation: innovations expressed in requirements appear as a wave that is reflected in a subsequent wave of features that is reflected in a subsequent wave of product downloads. Although the theory is a conjecture, the process of its exploration demonstrates how RCNL can be used to explore theories about open source projects -- theory exploration that would otherwise be intractable because of the difficulty in analyzing NL artifacts for requirements properties.},
	isbn = {978-0-7695-4892-0},
	doi = {10.1109/HICSS.2013.97},
	author = {Vlas, Radu and Robinson, William N.}
}
@book {1542,
	title = {Authoritative Linked Data Descriptions of Debian Source Packages Using ADMS.SW},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {168 - 181},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {he Debian Package Tracking System is a Web dashboard for Debian contributors and advanced users. This central tool publishes the status of subsequent releases of source packages in the Debian distribution.

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

This should enable the interlinking of these Debian package descriptions with other ADMS.SW or DOAP descriptions of FLOSS projects available on the Semantic Web also using Linked Data principles. This will be particularly interesting for traceability with upstream projects whose releases are packaged in Debian, derivative distributions reusing Debian source packages, or with other FLOSS distributions.},
	keywords = {debian},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_12},
	author = {Olivier Berger and Christian Bac},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@inbook {1630,
	title = {The Babel of Software Development: Linguistic Diversity in Open Source},
	booktitle = {Social Informatics},
	series = {Lecture Notes in Computer Science},
	volume = {8238},
	year = {2013},
	pages = {391-404},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	isbn = {978-3-319-03259-7},
	doi = {10.1007/978-3-319-03260-3_34},
	url = {http://dx.doi.org/10.1007/978-3-319-03260-3_34},
	attachments = {https://flosshub.org/sites/flosshub.org/files/socinfo13.pdf},
	author = {Vasilescu, Bogdan and Serebrenik, Alexander and Brand, MarkG.J.},
	editor = {Jatowt, Adam and Lim, Ee-Peng and Ding, Ying and Miura, Asako and Tezuka, Taro and Dias, Ga{\"e}l and Tanaka, Katsumi and Flanagin, Andrew and Dai, BingTian}
}
@proceedings {1522,
	title = {Boa: A Language and Infrastructure for Analyzing Ultra-Large-Scale Software Repositories},
	year = {2013},
	month = {05/2013},
	pages = {422-431},
	abstract = {In today{\textquoteright}s software-centric world, ultra-large-scale software repositories, e.g. SourceForge (350,000+ projects), GitHub (250,000+ projects), and Google Code (250,000+ projects) are the new library of Alexandria. They contain an enormous corpus of software and information about software. Scientists and engineers alike are interested in analyzing this wealth of information both for curiosity as well as for testing important hypotheses. However, systematic extraction of relevant data from these repositories and analysis of such data for testing hypotheses is hard, and best left for mining software repository (MSR) experts! The goal of Boa, a domain-specific language and infrastructure described here, is to ease testing MSR-related hypotheses. We have implemented Boa and provide a web-based interface to Boa{\textquoteright}s infrastructure. Our evaluation demonstrates that Boa substantially reduces programming efforts, thus lowering the barrier to entry. We also see drastic improvements in scalability. Last but not least, reproducing an experiment conducted using Boa is just a matter of re-running small Boa programs provided by previous researchers.},
	keywords = {ease of use, forge, github, google code, lower barrier to entry, mining, repository, reproducible, scalable, Software, sourceforge},
	author = {Dyer, Robert and Nguyen, Hoan Anh and Rajan, Hridesh and Nguyen, Tien N.}
}
@proceedings {1507,
	title = {Bug Resolution Catalysts: Identifying Essential Non-committers from Bug Repositories},
	year = {2013},
	month = {05/2013},
	abstract = {Bugs are inevitable in software projects. Resolving bugs is the primary activity in software maintenance. Developers, who fix bugs through code changes, are naturally important participants in bug resolution. However, there are other participants in these projects who do not perform any code commits. They can be reporters reporting bugs; people having a deep technical know-how of the software and providing valuable insights on how to solve the bug; bug-tossers who re-assign the bugs to the right set of developers. Even though all of them act on the bugs by tossing and commenting, not all of them may be crucial for bug resolution. In this paper, we formally define essential non-committers and try to identify these bug resolution catalysts. We empirically study 98304 bug reports across 11 open source and 5 commercial software projects for validating the existence of such catalysts. We propose a network analysis based approach to construct a Minimal Essential Graph that identifies such people in a project. Finally, we suggest ways of leveraging this information for bug triaging and bug report summarization.},
	author = {Mani, Senthil and Seema Nagar and Debdoot Mukherjee and Ramasuri Narayanam and Sinha, Vibha Singhal and Amit A. Nanavati}
}
@article {Ampatzoglou2013131,
	title = {Building and mining a repository of design pattern instances: Practical and research benefits},
	journal = {Entertainment Computing},
	volume = {4},
	number = {2},
	year = {2013},
	note = {flossmole cited},
	pages = {131 - 142},
	abstract = {Design patterns are well-known design solutions that are reported to produce substantial benefits with respect to software quality. However, to our knowledge there are no scientific efforts on gathering information on software projects that use design patterns. This paper introduces a web repository of design patterns instances that have been used in open source projects. The usefulness of such a repository lies in the provision of a base of knowledge, where developers can identify reusable components and researchers can find a mined data set. Currently, 141 open source projects have been considered and more than 4500 pattern instances have been found and recorded in the database of the repository. The evaluation of the repository has been performed from an academic and a practical point of view. The results suggest that the repository can be useful for both experienced and inexperienced users. However, the benefits of using the repository are more significant for inexperienced users. },
	keywords = {flossmole cited, repository},
	issn = {1875-9521},
	doi = {10.1016/j.entcom.2012.10.002},
	url = {http://www.sciencedirect.com/science/article/pii/S1875952112000195},
	author = {Apostolos Ampatzoglou and Olia Michou and Ioannis Stamelos}
}
@proceedings {1491,
	title = {Communication in Open Source Software Development Mailing Lists},
	year = {2013},
	note = {"The entire dataset used in the experiment, including the cards, the resolved aliases, and detailed statistical results, can be downloaded from ..." http://www.st.ewi.tudelft.nl/~guzzi/oss-communication/},
	month = {05/2013},
	pages = {277-286},
	abstract = {Open source software (OSS) development teams use
electronic means, such as emails, instant messaging, or forums,
to conduct open and public discussions. Researchers investigated
mailing lists considering them as a hub for project communication. Prior work focused on specific aspects of emails, for example
the handling of patches, traceability concerns, or social networks.
This led to insights pertaining to the investigated aspects, but not
to a comprehensive view of what developers communicate about.
Our objective is to increase the understanding of development
mailing lists communication.
We quantitatively and qualitatively analyzed a sample of 506
email threads from the development mailing list of a major OSS
project, Lucene. Our investigation reveals that implementation
details are discussed only in about 35\% of the threads, and that
a range of other topics is discussed. Moreover, core developers
participate in less than 75\% of the threads. We observed that the
development mailing list is not the main player in OSS project
communication, as it also includes other channels such as the
issue repository.},
	keywords = {email, lucene, mailling list},
	url = {http://www.st.ewi.tudelft.nl/~guzzi/downloads/Guzzi2013msr.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Guzzi2013msr.pdf},
	author = {Guzzi, Anja and Bacchelli, Alberto and Lanza, Michele and Pinzger, Martin and van Deursen, Arie}
}
@book {1536,
	title = {Community Dynamics in Open Source Software Projects: Aging and Social Reshaping},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {80 - 96},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

An undeniable factor for an open source software (OSS) project success is a vital community built around it. An OSS community not only needs to be established, but also to be persisted. This is not guaranteed considering the voluntary nature of participation in OSS. The dynamic analysis of the OSS community evolution can be used to extract indicators to rate the current stability of a community and to predict its future development. Despite the great amount of studies on mining project communication and development repositories, the evolution of OSS communities is rarely addressed. This paper presents an approach to analyze the OSS community history. We combine adapted demography measures to study community aging and social analysis to investigate the dynamics of community structures. The approach is applied to the communication and development history of three bioinformatics OSS communities over eleven years. First, in all three projects a survival rate pattern is identified. This finding allows us to define the minimal number of newcomers required for the further positive community growth. Second, dynamic social analysis shows that the node betweenness in combination with the network diameter can be used as an indicator for significant changes in the community core and the quality of community recovery after these modifications.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_6},
	author = {Hannemann, Anna and Klamma, Ralf},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1502,
	title = {A Dataset from Change History to Support Evaluation  of Software Maintenance Tasks},
	year = {2013},
	month = {05/2013},
	pages = {131-134},
	abstract = {Approaches that support software maintenance need 
to be evaluated and compared against existing ones, in order to 
demonstrate their usefulness in practice. However, oftentimes the 
lack of well-established sets of benchmarks leads to situations 
where these approaches are evaluated using different datasets, 
which results in biased comparisons. In this data paper we 
describe and make publicly available a set of benchmarks from 
six Java applications, which can be used in the evaluation of 
various software engineering (SE) tasks, such as feature location 
and impact analysis. These datasets consist of textual description 
of change requests, the locations in the source code where they 
were implemented, and execution traces. Four of the benchmarks 
were already used in several SE research papers, and two of them 
are new. In addition, we describe in detail the methodology used 
for generating these benchmarks and provide a suite of tools in 
order to encourage other researchers to validate our datasets and 
generate new benchmarks for other subject software systems. 
Our online appendix: http://www.cs.wm.edu/semeru/data/msr13/ },
	url = {http://www.cs.wm.edu/~bdit/publications/MSR13DataPaper_Dit_CRC.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MSR13DataPaper_Dit_CRC.pdf},
	author = {Bogdan Dit and Andrew Holtzhauer and Poshyvanyk, Denys and Kagdi, Huzefa}
}
@proceedings {1512,
	title = {Discovering, Reporting, and Fixing Performance Bugs},
	year = {2013},
	month = {05/2013},
	abstract = {Software performance is critical for how users perceive the quality of software products. Performance bugs---programming errors that cause significant performance degradation---lead to poor user experience and low system throughput. Designing effective techniques to address performance bugs requires a deep understanding of how performance bugs are discovered, reported, and fixed. In this paper, we study how performance bugs are discovered, reported to developers, and fixed by developers, and compare the results with those for non-performance bugs. We study performance and non-performance bugs from three popular code bases: Eclipse JDT, Eclipse SWT, and Mozilla. First, we find little evidence that fixing performance bugs has a higher chance to introduce new functional bugs than fixing non-performance bugs, which implies that developers may not need to be overconcerned about fixing performance bugs. Second, although fixing performance bugs is about as error-prone as fixing nonperformance bugs, fixing performance bugs is more difficult than fixing non-performance bugs, indicating that developers need better tool support for fixing performance bugs and testing performance bug patches. Third, unlike many non-performance bugs, a large percentage of performance bugs are discovered through code reasoning, not through users observing the negative effects of the bugs (e.g., performance degradation) or through profiling. The result suggests that techniques to help developers reason about performance, better test oracles, and better profiling techniques are needed for discovering performance bugs.},
	keywords = {bugs, eclipse, mozilla, performance bugs},
	author = {Adrian Nistor and Tian Jiang and Tan, Lin}
}
@conference {Venkataramani:2013:DTE:2487788.2487832,
	title = {Discovery of Technical Expertise from Open Source Code Repositories},
	booktitle = {Proceedings of the 22Nd International Conference on World Wide Web Companion},
	series = {WWW {\textquoteright}13 Companion},
	year = {2013},
	pages = {97{\textendash}98},
	publisher = {International World Wide Web Conferences Steering Committee},
	organization = {International World Wide Web Conferences Steering Committee},
	address = {Republic and Canton of Geneva, Switzerland},
	abstract = {Online Question and Answer websites for developers have emerged as the main forums for interaction during the software development process. The veracity of an answer in such websites is typically verified by the number of {\textquoteright}upvotes{\textquoteright} that the answer garners from peer programmers using the same forum. Although this mechanism has proved to be extremely successful in rating the usefulness of the answers, it does not lend itself very elegantly to model the expertise of a user in a particular domain. In this paper, we propose a model to rank the expertise of the developers in a target domain by mining their activity in different opensource projects. To demonstrate the validity of the model, we built a recommendation system for StackOverflow which uses the data mined from GitHub.
},
	keywords = {github, knowledge discovery, recommendations, source code repository, stackoverflow, technical expertise},
	isbn = {978-1-4503-2038-2},
	url = {http://dl.acm.org/citation.cfm?id=2487788.2487832},
	author = {Venkataramani, Rahul and Gupta, Atul and Asadullah, Allahbaksh and Muddu, Basavaraju and Bhat, Vasudev}
}
@proceedings {1494,
	title = {Do Software Categories Impact Coupling Metrics?},
	year = {2013},
	month = {05/2013},
	pages = {217-220},
	abstract = {Software metrics is a valuable mechanism to assess
the quality of software systems. Metrics can help the automated
analysis of the growing data available in software repositories.
Coupling metrics is a kind of software metrics that have been
extensively used since the seventies to evaluate several software
properties related to maintenance, evolution and reuse tasks. For
example, several works have shown that we can use coupling
metrics to assess the reusability of software artifacts available in
repositories. However, thresholds for software metrics to indicate
adequate coupling levels are still a matter of discussion. In this
paper, we investigate the impact of software categories on the
coupling level of software systems. We have found that different
categories may have different levels of coupling, suggesting that
we need special attention when comparing software systems in
different categories and when using predefined thresholds
already available in the literature.
},
	url = {http://www.facom.ufu.br/~marcmaia/preprints/msr13-SouzaMaia-CategoriesAndCoupling.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr13-SouzaMaia-CategoriesAndCoupling.pdf},
	author = {Lucas Batista Leite de Souza and Marcelo de Almeida Maia}
}
@book {1546,
	title = {A Dual Model of Open Source License Growth},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	note = {uses ohloh snapshot, march 2008},
	pages = {245 - 256},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Every open source project needs to decide on an open source license. This decision is of high economic relevance: Just which license is the best one to help the project grow and attract a community? The most common question is: Should the project choose a restrictive (reciprocal) license or a more permissive one? As an important step towards answering this question, this paper analyses actual license choice and correlated project growth from ten years of open source projects. It provides closed analytical models and finds that around 2001 a reversal in license choice occurred from restrictive towards permissive licenses.
},
	keywords = {ohloh},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/oss2013.hofmann.pdf},
	author = {Hofmann, Gottfried and Dirk Riehle and Carsten Kolassa and Mauerer, Wolfgang},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@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}
}
@book {1579,
	title = {Finding Source Code on the Web for Remix and Reuse},
	series = {Infrastructure for Building Code Search Applications for Developers},
	year = {2013},
	note = {In "further reading": "Although not a code search infrastructure, FLOSSmole [13] is another major undertaking
in building large collection of metadata about open source projects on the
Web. Currently, FLOSSmole reports a massive data collection of more than 500,000
open source projects in its web site [32]. For code search infrastructure builders,
now it is possible to leverage FLOSSmole{\textquoteright}s project metadata to build code repositories
instead of spending an effort in implementing custom spiders and crawlers for
code."},
	pages = {135 - 164},
	publisher = {Springer New York},
	organization = {Springer New York},
	address = {New York, NY},
	abstract = {The large availability of open source code on the Web provides great opportunities to build useful code search applications for developers. Building such applications requires addressing several challenges inherent in collecting and analyzing code from open source repositories to make them available for search. An infrastructure that supports collection, analysis, and search services for open source code available on the Web can greatly facilitate building effective code search applications. This chapter presents such an infrastructure called Sourcerer that facilitates collection, analysis, and search of source code available in code repositories on the Web. This chapter provides useful information to researchers and implementors of code search applications interested in harnessing the large availability of source code in the repositories on the Web. In particular, this chapter highlights key aspects of Sourcerer that supports combining Software Engineering and Information Retrieval techniques to build effective code search applications.},
	keywords = {code search, flossmole cited},
	isbn = {978-1-4614-6596-6},
	doi = {10.1007/978-1-4614-6596-6_8},
	url = {http://www.drsusansim.org/papers/FindingCodeontheWeb-20120822.pdf},
	author = {Bajracharya, Sushil Krishna},
	editor = {Sim, Susan Elliott and Gallardo-Valencia, Rosalva E.}
}
@conference {1684,
	title = {Gendered Patterns of Politeness in Free/Libre Open Source Software Development},
	booktitle = {2013 46th Hawaii International Conference on System Sciences (HICSS)2013 46th Hawaii International Conference on System Sciences},
	year = {2013},
	pages = {3168 - 3177},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Wailea, HI, USA},
	isbn = {978-0-7695-4892-0},
	doi = {10.1109/HICSS.2013.240},
	url = {https://www.ischool.utexas.edu/~eymoon/pdf/hicss46\%20eymoon\%20(proceeding).pdf},
	author = {Moon, Eunyoung}
}
@conference {G13,
	title = {The GHTorrent dataset and tool suite},
	booktitle = {MSR {\textquoteright}13: Proceedings of the 9th Working Conference on Mining Software Repositories},
	year = {2013},
	note = {Example of how to use the data/tool: http://www.gousios.gr/blog/on-github-pull-requests/},
	month = {05/2013},
	abstract = {A common requirement of many empirical software engineering studies is the acquisition and curation of data from software repositories. During the last few years, GitHub has emerged as a popular project hosting, mirroring and collaboration platform. GitHub provides an extensive REST API, which enables researchers to retrieve both the commits to the projects{\textquoteright} repositories and events generated through user actions on project resources. GHTorrent aims to create a scalable off line mirror of GitHub{\textquoteright}s event streams and persistent data, and offer it to the research community as a service. In this paper, we present the project{\textquoteright}s design and initial implementation and demonstrate how the provided datasets can be queried and processed.},
	url = {http://www.gousios.gr/bibliography/G13.html},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ghtorrent-dataset-toolsuite.pdf},
	author = {Gousios, Georgios}
}
@proceedings {1510,
	title = {A Historical Dataset for the Gnome Ecosystem},
	year = {2013},
	month = {05/2013},
	abstract = {We present a dataset of the open source software ecosystem Gnome from a social point of view. We have collected historical data about the contributors to all Gnome projects stored on git.gnome.org, taking into account the problem of identity matching, and associating different activity types to the contributors. This type of information is very useful to complement the traditional, source-code related information one can obtain by mining and analyzing the actual source code. The dataset can be obtained at https://bitbucket.org/mgoeminne/sgl-flossmetric-dbmerge.},
	keywords = {cvsanaly, flossmetrics, gnome},
	author = {Mathieu Goeminne and Ma{\"e}lick Claes and Mens, Tom}
}
@conference {zmzkh-icsm-2013,
	title = {How does Context affect the Distribution of Software Maintainability Metrics?},
	booktitle = {Proceedings of the 29th IEEE International Conference on Software Maintainability},
	series = {ICSM {\textquoteright}13},
	year = {2013},
	note = {"FLOSSMole [25] is another data source, from
where we download descriptions (i.e., application domain)
of SourceForge software systems. Furthermore, we download
latest application domain information4
and monthly download
data5 of studied software systems directly from SourceForge."},
	abstract = {Software metrics have many uses, e.g., defect prediction, effort estimation, and benchmarking an organization against peers and industry standards. In all these cases, metrics may depend on the context, such as the programming language. Here we aim to investigate if the distributions of commonly used metrics do, in fact, vary with six context factors: application domain, programming language, age, lifespan, the number of changes, and the number of downloads. For this preliminary study we select 320 nontrivial software systems from SourceForge. These software systems are randomly sampled from nine popular application domains of SourceForge. We calculate 39 metrics commonly used to assess software maintainability for each software system and use Kruskal Wallis test and Mann-Whitney U test to determine if there are significant differences among the distributions with respect to each of the six context factors. We use Cliff{\textquoteright}s delta to measure the magnitude of the differences and find that all six context factors affect the distribution of 20 metrics and the programming language factor affects 35 metrics. We also briefly discuss how each context factor may affect the distribution of metric values.We expect our results to help software benchmarking and other software engineering methods that rely on these commonly used metrics to be tailored to a particular context.},
	keywords = {benchmark, context, contextual factor, flossmole, large scale, metrics, mining software repositories, sampling, software maintainability, sourceforge, static metrics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icsm2013_contextstudy.pdf},
	author = {Zhang, Feng and Audris Mockus and Ying Zou and Foutse Khomh and Hassan, Ahmed E.}
}
@book {1532,
	title = {How Healthy Is My Project? Open Source Project Attributes as Indicators of Success},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	note = {"The dataset used has thus been obtained through a third source which has made
the data publicly available [18]. FlossMole.org contains data collected for the period
2006 to December 2009 from which a dataset was compiled of 125,700 projects. "},
	pages = {30 - 44},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {Determining what factors can influence the successful outcome of a software project has been labeled by many scholars and software engineers as a difficult problem. In this paper we use machine learning to create a model that can determine the stage a software project has obtained with some accuracy. Our model uses 8 Open Source project metrics to determine the stage a project is in. We validate our model using two performance measures; the exact success rate of classifying an Open Source Software project and the success rate over an interval of one stage of its actual performance using different scales of our dependent variable. In all cases we obtain an accuracy of above 70\% with one away classification (a classification which is away by one) and about 40\% accuracy with an exact classification. We also determine the factors (according to one classifier) that uses only eight variables among all the variables available in SourceForge, that determine the health of an OSS project.
},
	keywords = {flossmole, sourceforge},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_3},
	url = {http://link.springer.com/chapter/10.1007/978-3-642-38928-3_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OSSHealth_1.0.pdf},
	author = {Piggot, James and Amrit, Chintan},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1533,
	title = {Identifying Success Factors for the Mozilla Project},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {45 - 60},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

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

This paper analyzes the relation between OSS (Open Source Software) use and the performance of Japanese information service industry. We first estimate the market value of OSS, an issue which only a few studies have specifically addressed. The results are then used to analyze the economic effect of OSS. Although our study has some methodological limitations regarding the calculation of the market value of OSS, we demonstrate that the economic effect of OSS is generally positive.},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_2},
	author = {Noda, Tetsuo and Tanihana, Keisuke},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1501,
	title = {The Impact of Tangled Code Changes},
	year = {2013},
	month = {05/2013},
	abstract = {When interacting with version control systems, developers often commit unrelated or loosely related code changes
in a single transaction. When analyzing the version history, such
tangled changes will make all changes to all modules appear
related, possibly compromising the resulting analyses through
noise and bias. In an investigation of five open-source JAVA
projects, we found up to 15\% of all bug fixes to consist of multiple
tangled changes. Using a multi-predictor approach to untangle
changes, we show that on average at least 16.6\% of all source
files are incorrectly associated with bug reports. We recommend
better change organization to limit the impact of tangled changes.},
	keywords = {bias, data quality, history, java, mining software repositories, noise, tangled code changes, version control},
	url = {http://www.kim-herzig.de/wp-content/uploads/2013/03/msr2013-untangling.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2013-untangling.pdf},
	author = {Kim Herzig and Zeller, Andreas}
}
@proceedings {1513,
	title = {Improving Bug Localization using Correlations in Crash Reports},
	year = {2013},
	month = {05/2013},
	abstract = {Nowadays, many software organizations rely on automatic problem reporting tools to collect crash reports directly from users{\textquoteright} environments. These crash reports are later grouped together into crash types. Usually, developers prioritize crash types based on the number of crash reports and file bugs for the top crash types. Because a bug can trigger a crash in different usage scenarios, different crash types are sometimes related to a same bug. Two bugs are correlated when the occurrence of one bug causes the other bug to occur. We refer to a group of crash types related to identical or correlated bugs, as a crash correlation group. In this paper, we propose three rules to identify correlated crash types automatically. We also propose an algorithm to locate and rank buggy files using crash correlation groups. Through an empirical study on Firefox and Eclipse, we show that the three rules can identify crash correlation groups with a precision of 100\% and a recall of 90\% for Firefox and a precision of 79\% and a recall of 65\% for Eclipse. On the top three buggy file candidates, the proposed bug localization algorithm achieves a recall of 62\% and a precision of 42\% for Firefox and a recall of 52\% and a precision of 50\% for Eclipse. On the top 10 buggy file candidates, the recall increases to 92\% for Firefox and 90\% for Eclipse. Developers can combine the proposed crash correlation rules with the new bug localization algorithm to identify and fix correlated crash types all together.},
	keywords = {eclipse, Firefox},
	author = {Shaohua Wang and Foutse Khomh and Ying Zou}
}
@proceedings {1506,
	title = {Intensive Metrics for the Study of the Evolution of Open Source Projects: Case Studies from Apache Software Foundation Projects},
	year = {2013},
	month = {05/2013},
	abstract = {Based on the empirical evidence that the ratio of email messages in public mailing lists to versioning system commits has remained relatively constant along the history of the Apache Software Foundation (ASF), this paper has as goal to study what can be inferred from such a metric for projects of the ASF. We have found that the metric seems to be an intensive metric as it is independent of the size of the project, its activity, or the number of developers, and remains relatively independent of the technology or functional area of the project. Our analysis provides evidence that the metric is related to the technical effervescence and popularity of project, and as such can be a good candidate to measure its healthy evolution. Other, similar metrics -like the ratio of developer messages to commits and the ratio of issue tracker messages to commits- are studied for several projects as well, in order to see if they have similar characteristics.},
	url = {http://oa.upm.es/14698/1/paper.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper_1.pdf},
	author = {Gala, Santiago and Gregorio Robles and Jesus M. Gonzalez-Barahona and Herraiz Tabernero, Israel}
}
@article {1553,
	title = {Interlinking Developer Identities within and across Open Source Projects: The Linked Data Approach},
	journal = {ISRN Software Engineering},
	volume = {201330692164},
	year = {2013},
	month = {2013},
	pages = {1 - 12},
	abstract = {Software developers use various software repositories in order to interact with each other or to solve related problems. These repositories provide a rich source of information for a wide range of tasks. However, one issue to overcome in order to make this information useful is the identification and interlinking of multiple identities of developers. In this paper, we propose a Linked Data-based methodology to interlink and integrate multiple identities of a developer found in different software repositories of a project as well as across repositories of multiple projects. Providing such interlinking will enable us to keep track of a developer{\textquoteright}s activity not only within a single project but also across multiple projects. The methodology will be presented in general and applied to 5 Apache projects as a case study. Further, we show that the few methods suggested so far are not always appropriate to overcome the developer identification problem.},
	keywords = {developer, identity, linked data},
	doi = {10.1155/2013/58473110.1007/s10664-009-9110-310.1109/TSE.2005.7010.1007/978-0-387-72486-7_4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/584731.pdf},
	author = {Iqbal, Aftab and Hausenblas, Michael}
}
@proceedings {1514,
	title = {INVocD: Identifier Name Vocabulary Dataset },
	year = {2013},
	month = {05/2013},
	abstract = {INVocD is a database of the identifier name declarations and vocabulary found in 60 FLOSS Java projects where the source code structure is recorded and the identifier name vocabulary is made directly available, offering advantages for identifier name research over conventional source code models. The database has been used to support a range of research projects from identifier name analysis to concept location, and provides many opportunities to researchers. INVocD may be downloaded from http://oro.open.ac.uk/36992},
	author = {Simon Butler and Wermelinger, Michel and Yu, Yijun and Helen Sharp}
}
@book {1531,
	title = {Is It All Lost? A Study of Inactive Open Source Projects},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification },
	volume = {404},
	year = {2013},
	pages = {61 - 79},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {
Open Source Software (OSS) proponents suggest that when developers lose interest in their project, their last duty is to {\textquotedblleft}hand it off to a competent successor.{\textquotedblright} However, the mechanisms of such a hand-off are not clear, or widely known among OSS developers. As a result, many OSS projects, after a certain long period of evolution, stop evolving, in fact becoming {\textquotedblleft}inactive{\textquotedblright} or {\textquotedblleft}abandoned{\textquotedblright} projects. This paper presents an analysis of the population of projects contained within one of the largest OSS repositories available (SourceForge.net), in order to describe how projects abandoned by their developers can be identified, and to discuss the attributes and characteristics of these inactive projects. In particular, the paper attempts to differentiate projects that experienced maintainability issues from those that are inactive for other reasons, in order to be able to correlate common characteristics to the {\textquotedblleft}failure{\textquotedblright} of these projects.
},
	keywords = {sourceforge},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_5},
	url = {http://staff.lero.ie/stol/files/2013/03/2013-Is-It-All-Lost-A-Study-of-Inactive-Open-Source-Projects.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2013-Is-It-All-Lost-A-Study-of-Inactive-Open-Source-Projects.pdf},
	author = {Khondu, Jymit and Capiluppi, Andrea and Stol, Klaas},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1521,
	title = {It{\textquoteright}s Not a Bug, It{\textquoteright}s a Feature: How Misclassification Impacts Bug Prediction},
	year = {2013},
	month = {05/2013},
	pages = {392-401},
	abstract = {In a manual examination of more than 7,000 issue reports from the bug databases of five open-source projects, we found 33.8\% of all bug reports to be misclassified{\textemdash}that is, rather than referring to a code fix, they resulted in a new feature, an update to documentation, or an internal refactoring. This misclassification introduces bias in bug prediction models, confusing bugs and features: On average, 39\% of files marked as defective actually never had a bug. We discuss the impact of this misclassification on earlier studies and recommend manual data validation for future studies.},
	keywords = {bias, bug reports, data quality, mining software repositories, noise},
	author = {Kim Herzig and Sascha Just and Zeller, Andreas}
}
@conference {1783,
	title = {Linchpin Developers in Open Source Software Projects},
	booktitle = {Artificial Intelligence and Applications},
	year = {2013},
	note = {"The datasources used have been FLOSSmole[5], providing statistical data about each  project.   From  this  repository  we  extracted  the  role assumed by the developers, and domains of participation. "

"We compared our dataset, mined from the FLOSSmole repository [5], based on Sourceforge data, with the one given in [9]. "},
	publisher = {ACTAPRESS},
	organization = {ACTAPRESS},
	address = {Innsbruck, AustriaCalgary,AB,Canada},
	abstract = {In Open Source Software (OSS) development, the so-called linchpin developers are those that contribute contemporaneously to several projects, contributing to keeping the community tied together. While such developers have been identified in previous research, their importance within the OSS community has not been widely discussed. The main objective of this work is to analyze their {\textquotedblleft}weaving{\textquotedblright} role across projects. With this aim, we mined software repositories, using text mining techniques as log-likehood ratio and co-word analysis, further building social networks of developers within emerging communities. The findings show that linchpin developers generally attach in a preferential way to projects in a single specific domain. They tend to be more {\textquotedblleft}project managers{\textquotedblright}, and {\textquotedblleft}all-hands-persons{\textquotedblright}, meaning that they bring multi-disciplinary experience across projects. They tend to cover the same role across projects. They generally have high centrality in their projects, and contribute to create projects that ease the transition from a fragmented projects community to a more core-periphery community.
},
	keywords = {flossmole},
	doi = {10.2316/P.2013.796-018},
	url = {https://www.researchgate.net/publication/266632252_Linchpin_Developers_in_Open_Source_Software_Projects},
	author = {Corona, Erika Ingrid Mastranzo and Rossi, Bruno}
}
@proceedings {1500,
	title = {Linux Variability Anomalies: What Causes Them and How Do They Get Fixed?},
	year = {2013},
	month = {05/2013},
	abstract = {The Linux kernel is one of the largest configurable open source software systems implementing static variability. In Linux, variability is scattered over three different artifacts: source code files, Kconfig files, and Makefiles. Previous work detected inconsistencies between these artifacts that led to anomalies in the intended variability of Linux. We call these variability anomalies. However, there has been no work done to analyze how these variability anomalies are introduced in the first place, and how they get fixed. In this work, we provide an analysis of the causes and fixes of variability anomalies in Linux. We first perform an exploratory case study that uses an existing set of patches which solve variability anomalies to identify patterns for their causes. The observations we make from this dataset allow us to develop four research questions which we then answer in a confirmatory case study on the scope of the whole Linux kernel. We show that variability anomalies exist for several releases in the kernel before they get fixed, and that contrary to our initial suspicion, typos in feature names do not commonly cause these anomalies. Our results show that variability anomalies are often introduced through incomplete patches that change Kconfig definitions without properly propagating these changes to the rest of the system. Anomalies are then commonly fixed through changes to the code rather than to Kconfig files.},
	author = {Sarah Nadi and Christian Dietrich and Reinhard Tartler and Holt, Richard C. and Daniel Lohmann}
}
@article {bettenburg2013management,
	title = {Management of community contributions},
	journal = {Empirical Software Engineering},
	year = {2013},
	pages = {1{\textendash}38},
	publisher = {Springer},
	abstract = {In recent years, many companies have realized that collaboration with a thriving user or developer community is a major factor in creating innovative technology driven by market demand. As a result, businesses have sought ways to stimulate contributions from developers outside their corporate walls, and integrate external developers into their development process. To support software companies in this process, this paper presents an empirical study on the contribution management processes of two major, successful, open source software ecosystems. We contrast a for-profit (ANDROID) system having a hybrid contribution style, with a not-for-profit (LINUX kernel) system having an open contribution style. To guide our comparisons, we base our analysis on a conceptual model of contribution management that we derived from a total of seven major open-source software systems. A quantitative comparison based on data mined from the ANDROID code review system and the LINUX kernel code review mailing lists shows that both projects have significantly different contribution management styles, suited to their respective market goals, but with individual advantages and disadvantages that are important for practitioners. Contribution management is a real-world problem that has received very little attention from the research community so far. Both studied systems (LINUX and ANDROID) employ different strategies and techniques for managing contributions, and both approaches are valuable examples for practitioners. Each approach has specific advantages and disadvantages that need to be carefully evaluated by practitioners when adopting a contribution management process in practice.},
	keywords = {android, contribution, linux, management},
	url = {http://link.springer.com/article/10.1007/s10664-013-9284-6},
	author = {Bettenburg, Nicolas and Hassan, Ahmed E. and Adams, Bram and Daniel M. German}
}
@conference {abdouSEKE2013,
	title = {{Managing Corrective Actions to Closure in Open Source Software Test Process}},
	booktitle = {The 25th International Conference on Software Engineering and Knowledge Engineering (SEKE 2013)},
	year = {2013},
	pages = {306{\textendash}311},
	address = {Boston, USA},
	abstract = {In assessing test process maturity, one of the goals is to manage disciplinary issues. Managing corrective actions to closure is known to aid software quality assurance, in general, and testing process activities, in particular. In this paper, a framework for software testing assessment, namely OSS-TPA, that aims to evaluate corrective actions in OSS test process, is proposed. The OSS-TPA framework is based on earlier studies and relies on a conceptual model for test process activities in OSS development. Using success factors in OSS development, the relationship between the maturity of managing corrective actions and the adoption of OSS is investigated.},
	keywords = {open source software, software engineering, software quality, Software testing, Test Process Improvement.},
	url = {http://index.ksi.edu/conf/seke/2013/cr/282.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/282.pdf},
	author = {Abdou, Tamer and Grogono, Peter and Kamthan, Pankaj}
}
@proceedings {1509,
	title = {The Maven Repository Dataset of Metrics, Changes, and Dependencies},
	year = {2013},
	month = {05/2013},
	abstract = {We present the Maven Dependency Dataset (MDD), containing metrics, changes and dependencies of 148,253 jar files. Metrics and changes have been calculated at the level of individual methods, classes and packages of multiple library versions. A complete call graph is also presented which includes call, inheritance, containment and historical relationships between all units of the entire repository. In this paper, we describe our dataset and the methodology used to obtain it. We present different conceptual views of MDD and we also describe limitations and data quality issues that researchers using this data should be aware of. http://data.3tu.nl/repository/uuid:68a0e837-4fda-407a-949e-a159546e67b6},
	keywords = {maven},
	doi = {dx.doi.org/10.4121/uuid:68a0e837-4fda-407a-949e-a159546e67b6},
	url = {http://data.3tu.nl/repository/uuid:68a0e837-4fda-407a-949e-a159546e67b6},
	author = {Steven Raemaekers and van Deursen, Arie and Visser, Joost}
}
@conference {1525,
	title = {Mining Developer Contribution in Open Source Software Using Visualization Techniques},
	booktitle = {2013 Third International Conference on Intelligent System Design and Engineering Applications (ISDEA)},
	year = {2013},
	pages = {934 - 937},
	publisher = {IEEE},
	organization = {IEEE},
	address = {China, Hong Kong},
	abstract = {

The research of developers{\textquoteright} contribution is an important part of the software evolution area. It allows project owners to find potential long-term contributors earlier and helps the newcomers to improve their behaviors. In this paper, we examined the contribution characteristics of developers in open source environment based on visual analysis, and presented approaches from three aspects-influencing factors, time characteristics and region characteristics. Our analysis used data from github and revealed some regular patterns. We found that the code which newcomers started to contribute with more people engaged in would lead to less contribution in some degree. We also found that there{\textquoteright}s a relation between developers{\textquoteright} early and later period contribution. In addition, developers from different regions were more likely to have dominant relationship. Our findings may provide some support for future research in the area of software evolution.},
	keywords = {github},
	isbn = {978-0-7695-4923-1},
	doi = {10.1109/ISDEA.2012.223},
	author = {Ben, Xu and Beijun, Shen and Weicheng, Yang}
}
@proceedings {1495,
	title = {Mining Source Code Repositories at Massive Scale using Language Modeling},
	year = {2013},
	month = {05/2013},
	abstract = {The tens of thousands of high-quality open source
software projects on the Internet raise the exciting possibility
of studying software development by finding patterns across
truly large source code repositories. This could enable new tools
for developing code, encouraging reuse, and navigating large
projects. In this paper, we build the first giga-token probabilistic
language model of source code, based on 352 million lines of
Java. This is 100 times the scale of the pioneering work by
Hindle et al. The giga-token model is significantly better at the
code suggestion task than previous models. More broadly, our
approach provides a new {\textquotedblleft}lens{\textquotedblright} for analyzing software projects,
enabling new complexity metrics based on statistical analysis
of large corpora. We call these metrics
data-driven complexity
metrics. We propose new metrics that measure the complexity of
a code module and the topical centrality of a module to a software
project. In particular, it is possible to distinguish reusable utility
classes from classes that are part of a program{\textquoteright}s core logic based
solely on general information theoretic criteria.},
	url = {http://homepages.inf.ed.ac.uk/csutton/publications/msr2013.pdf},
	author = {Allamanis, Miltiadis and Sutton, Charles}
}
@book {1545,
	title = {Misconceptions and Barriers to Adoption of FOSS in the U.S. Energy Industry},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {232 - 244},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

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

It is widely accepted that modeling in software engineering increases productivity and results in better code quality. Yet, modeling adoption remains low. The open source community, in particular, remains almost entirely code centric. In this paper, we explore the reasons behind such limited adoption of modeling practices among open source developers. We highlight characteristics of modeling tools that would encourage their adoption. We propose Umple as a solution where both modeling and coding elements are treated uniformly. In this approach, models can be manipulated textually and code can be edited visually. We also report on the Umple compiler itself as a case study of an open source project where contributors, using the above approach, have and continue to routinely commit code and model over a number of years.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Modeling-Practices-in-Open-Source-Software.pdf},
	author = {Badreddin, Omar and Lethbridge, Timothy and Elassar, Maged},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1511,
	title = {A Network of Rails: A Graph Dataset of Ruby on Rails and Associated Projects},
	year = {2013},
	month = {05/2013},
	abstract = {Software projects, whether open source, proprietary, or a combination thereof, rarely exist in isolation. Rather, most projects build on a network of people and ideas from dozens, hundreds, or even thousands of other projects. Using the GitHub APIs it is possible to extract these relationships for millions of users and projects. In this paper we present a dataset of a large network of open source projects centered around Ruby on Rails. This dataset provides insight into the relationships between Ruby on Rails and an ecosystem involving 1116 projects. To facilitate understanding of this data in the context of relationships between projects, users, and their activities, it is provided as a graph database suitable for assessing network properties of the community and individuals within those communities and can be found at https://github.com/pridkett/gitminer-data-rails.},
	author = {Wagstrom, Patrick and Jergensen, Corey and Sarma, Anita}
}
@article {1566,
	title = {Open Source Community Processes: Implications on Micro and Macro Level},
	journal = {it {\textendash} Information Technology},
	volume = {55},
	number = {5},
	year = {2013},
	pages = {189-194},
	abstract = {In this paper, we will discuss the existence and form of open source community processes, whether they differ between projects, and whether they have any implications on both micro and macro level. We will take a look at how different processes can impact the work and the resulting quality within projects, as well as on macro or project level outcomes like success or efficiency. We will also present as well as validate a research model to explain process adoption and implications.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/itit.2013.1010.pdf},
	author = {Koch, Stefan}
}
@book {1543,
	title = {An Open Source Monitoring Framework for Enterprise SOA},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {182 - 193},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Web services monitoring is currently emerging as an effective way to trace faults in services at runtime. The lack of testing information provided by web services specifications was an indication that other methods need to be used to assess the quality of web services. This is mainly due to the fact that it is difficult to simulate the client infrastructure during testing of web services. Monitoring consists of inspecting services at runtime and taking adequate actions when unacceptable events occur. Monitoring could be performed by different stakeholders and could target different properties of services. Predominantly, monitoring is performed by service providers to manage their internal resources and balance their requests load. In our effort to improve the monitoring infrastructures, we propose a monitoring framework in which all the participants (services providers, services requestors) can contribute to monitoring and at the same time have direct access to the monitoring data. This paper describes a monitoring framework developed as part of NEXOF-RA project. The framework offers a set of capabilities for a collaborative monitoring of web services. The paper presents motivations, system design, implementation and usage of the framework.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_13},
	author = {El Ioini, Nabil and Garibbo, Alessandro and Sillitti, Alberto and Succi, Giancarlo},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@conference {1721,
	title = {Orion: A Software Project Search Engine with Integrated Diverse Software Artifacts},
	booktitle = {2013 18th International Conference on Engineering of Complex Computer Systems (ICECCS)},
	year = {2013},
	note = {The FLOSSMole12, Flossmetrics [3] and
Sourcerer [1] projects collect data and/or provide statistics on
their collected data, but are not suitable for selecting a subset
or identifying a unique project based on desired properties.},
	pages = {242 - 245},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Singapore, Singapore},
	abstract = {What projects contain more than 10, 000 lines of code developed by less than 10 people and are still actively maintained with a high bug-fixing rate? To address the challenges for answering such enquiries, we develop an integrated search engine architecture that combines information from different types of software repositories from multiple sources. Our search engine facilitates the construction and execution of complex search queries using a uniform interface that transparently correlates different artifacts of project development and maintenance, such as source code information, version control systems metadata, bug tracking systems elements, and metadata on developer activities and interactions extracted from hosting platforms. We have built an extensible system with an initial capability of over 100, 000 projects collected from the web, featuring various software development artifacts. Using scenarios, we illustrate the benefits of such a search engine for different kinds of project seekers. 
},
	keywords = {flossmole cited},
	doi = {10.1109/ICECCS.2013.42},
	url = {http://www.mysmu.edu/faculty/davidlo/papers/iceccs13-projectsearch.pdf},
	author = {Bissyande, Tegawende F. and Thung, Ferdian and Lo, David and Jiang, Lingxiao and Reveillere, Laurent}
}
@book {1541,
	title = {A Preliminary Analysis of Localization in Free Software: How Translations Are Performed},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {153 - 167},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Software is more than just source code. There is a myriad of elements that compose a software project, among others documentation, translations, multimedia, artwork, marketing. In this paper, we focus on the translation efforts that free, libre, open source software (FLOSS) projects undergo to provide their software in multiple languages. We have therefore analyzed a large amount of projects for their support and procedures regarding translations, if they exist. Our results show that many, but not all, projects offer some type of support and specify some ways to those wanting to contribute. Usually, projects from a more traditional libre software domain are more prone to ease such tasks. However, there is no general way to contribute, as formats and procedures are often project-specific. We have identified as well a high number of translation-supporting tools, with many projects having their own one. All in all, information about how to contribute is the main factor for having a very internationalized application. Projects accepting and giving credit to contributing translators have high levels of internationalization, even if the process is rudimentary.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_11},
	author = {Reina, Laura Arjona and Gregorio Robles and Jesus M. Gonzalez-Barahona},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@article {IJC397,
	title = {Preliminary steps toward a general theory of internet-based collective-action in digital information commons: Findings from a study of open source software projects},
	journal = {International Journal of the Commons},
	volume = {7},
	number = {2},
	year = {2013},
	abstract = {This paper presents some of the findings from a 5-year empirical study of FOSS (free/libre and open source software) commons, completed in 2011. FOSS projects are Internet-based common property regimes where the project source code is developed over the Internet. The resulting software is generally distributed with a license that provides users with the freedoms to access, use, read, modify and redistribute the software. In this study we used three different and very large datasets (approximately 107,000; 174,000 and 1400 cases respectively) with information on FOSS projects residing in Sourceforge.net, one of the largest, if not the largest, FOSS repository in the world. We employ various quantitative methods to uncover factors that lead some FOSS projects to ongoing collaborative success, while others become abandoned. After presenting some of our study{\textquoteright}s results, we articulate the collaborative {\textquotedblleft}story{\textquotedblright} of FOSS that emerged. We close the paper by discussing some key findings that can contribute to a general theory of Internet-based collective-action and FOSS-like forms of digital online commons.},
	keywords = {collaborative success and abandonment, common property regime, digital information commons, flossmole, Free/libre software, open source software, sourceforge, srda},
	issn = {1875-0281},
	url = {http://www.thecommonsjournal.org/index.php/ijc/article/view/URN\%3ANBN\%3ANL\%3AUI\%3A10-1-114926},
	author = {Charles Schweik and Robert English}
}
@conference {Scacchi:2013:PSO:2486046.2486068,
	title = {Processes in Securing Open Architecture Software Systems},
	booktitle = {Proceedings of the 2013 International Conference on Software and System Process},
	series = {ICSSP 2013},
	year = {2013},
	pages = {126{\textendash}135},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Our goal is to identify and understand issues that arise in the development and evolution processes for securing open architecture (OA) software systems. OA software systems are those developed with a mix of closed source and open source software components that are configured via an explicit system architectural specification. Such a specification may serve as a reference model or product line model for a family of concurrently sustained OA system versions/variants. We employ a case study focusing on an OA software system whose security must be continually sustained throughout its ongoing development and evolution. We limit our focus to software processes surrounding the architectural design, continuous integration, release deployment, and evolution found in the OA system case study. We also focus on the role automated tools, software development support mechanisms, and development practices play in facilitating or constraining these processes through the case study. Our purpose is to identify issues that impinge on modeling (specification) and integration of these processes, and how automated tools mediate these processes, as emerging research problems areas for the software process research community. Finally, our study is informed by related research found in the prescriptive versus descriptive practice of these processes and tool usage in studies of conventional and open source software development projects.},
	keywords = {configuration, continuous software development, Open architecture, process integration, process modeling, security},
	isbn = {978-1-4503-2062-7},
	doi = {10.1145/2486046.2486068},
	url = {http://doi.acm.org/10.1145/2486046.2486068},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Scacchi-Alspaugh-ICSSP13.pdf},
	author = {Walt Scacchi and Alspaugh, Thomas A.}
}
@proceedings {1489,
	title = {Project Roles in the  Apache Software Foundation: A Dataset},
	year = {2013},
	month = {05/2013},
	abstract = {This paper outlines the steps in the creation and maintenance of a new dataset listing leaders of the various projects of the Apache Software Foundation (ASF). Included in this dataset are different levels of committers to the various ASF project code bases, as well as regular and emeritus members of the ASF, and directors and officers of the ASF. The dataset has been donated to the FLOSSmole project under an open source license, and is available for download (https://code.google.com /p/flossmole/downloads/detail?name=apachePeople2013-Jan.zip), or for direct querying via a database client.},
	keywords = {apache, dataset, roles},
	attachments = {https://flosshub.org/sites/flosshub.org/files/apacheRolesPREPRINT.pdf , https://flosshub.org/sites/flosshub.org/files/MSR\%20presentation_0.pdf},
	author = {Squire, Megan}
}
@proceedings {1557,
	title = {"Release Early, Release Often"? An Empirical Analysis of Release Strategy in Open Source Software Co-Creation},
	year = {2013},
	abstract = {{\textquotedblleft}Release early, release often{\textquotedblright} is becoming a popular new product introduction strategy in open source software development. We study the influence of release strategies on the download market share of open source projects. Using a panel data set collected from Sourceforge.net, we find that while more frequent releases are associated with better subsequent download market share, the relationship is curvilinear. Too frequent releases could backfire due to the subtle effects on the demand and supply sides of open source software production. From the demand side, we find that releasing frequently may work less effectively in projects with higher adoption costs. From the supply side, fast releases may work less effectively in projects with weak community contributions. Even when the community contributions are strong, the restrictiveness of open source license moderates the effectiveness of releasing early and often. These results have implications for managing open source projects and research on open source software, open innovation, and software adoption.},
	url = {http://aisel.aisnet.org/pacis2013/11},
	attachments = {https://flosshub.org/sites/flosshub.org/files/PACIS2013-002.pdf},
	author = {Chen, Wei and Krishnan, Vish and Zhu, Kevin}
}
@proceedings {1561,
	title = {A Replicable Infrastructure for Empirical Studies of Email Archives},
	year = {2013},
	month = {10/2013},
	pages = {43-50},
	publisher = {IEEE},
	address = {Baltimore, MD, USA},
	abstract = {This paper describes a replicable infrastructure solution for conducting empirical software engineering studies based on email mailing list archives. Mailing list emails, such as those affiliated with free, libre, and open source software (FLOSS) projects, are currently archived in several places online, but each research team that wishes to study these email artifacts closely must design their own solution for collection, storage and cleaning of the data. Consequently, research results will be difficult to replicate, especially as the email archive for any living project will still be continually growing. This paper describes a simple, replicable infrastructure for the collection, storage, and cleaning of project email data and analyses.},
	keywords = {apache, cleaning, collection, couchdb, database, document-oriented database, email, lucene, mailing lists, nosql, replication, storage},
	isbn = {978-0-7695-5121-0},
	attachments = {https://flosshub.org/sites/flosshub.org/files/RESERv2.pdf},
	author = {Squire, Megan}
}
@article {1556,
	title = {Research on mining the online co mmunity: a case of Open Source Software community },
	journal = {WSEAS Transactions on Computers},
	volume = {12},
	year = {2013},
	month = {06/2013},
	pages = {233-242},
	abstract = {The development of Open Source Software (OSS) projects is a process of collective innovation in the environment of online community. The paper addresses the challenge of efficiently mining data from OSS web repositories and building models to study OSS community features. Data collection for OSS community study is nontrivial since most OSS projects are develope
d by distributed developers using web tools. We design a mining process which combines web mining and database mining together to identify, extract, filter and analyze data. We address and analyze the difficulty of mining OSS community data. Our work provides a
general solution for researchers to implement advanced techniques, such as web mining, data mining, statistics, and algorithms to collect and analyze online community data. },
	attachments = {https://flosshub.org/sites/flosshub.org/files/5705-185.pdf},
	author = {Yuo, Lan}
}
@book {1540,
	title = {The Role of Microblogging in OSS Knowledge Management},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {140 - 152},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Given that microblogging has been shown to play a valuable role in knowledge management within companies, it is useful to understand how it is being used in relation to OSS. This project studies tweets related to 12 open source projects and keywords, ranging from web content management systems (CMSes) to general office applications. It found considerable differences in the content and exchange of tweets, especially between specialist products such as CMSes and office suites such as OpenOffice. Tweets concerning the more specialist projects tended to provide information rather than updates on the user{\textquoteright}s current status. We found a high proportion of event-driven traffic for some CMS projects, and a lower proportion for the office products and groups of projects.
},
	keywords = {twitter},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_10},
	author = {Lewis, Jonathan},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@conference {1576,
	title = {A scalable crawler framework for FLOSS data},
	booktitle = {Proceedings of the 5th Asia-Pacific Symposium on Internetware - Internetware {\textquoteright}13},
	year = {2013},
	note = {FLOSSmole [8] and FLOSSmetrics [9] retrieved FLOSS data of
various types from famous software forges like SourceForge and
Google code, interface to data sharing and analyzing is also
provided. 

" Typically,
Howison et al. [8] proposed a system called FLOSSmole.
FLOSSmole is a large collection of datasets extracted from
famous software forges such as SourceForge, GitHub, and Google
Code. Datasets in FLOSSmole are mainly metadata describing
various facts about the development of FLOSS projects.
FLOSSmole manages its datasets in an open and collaborative
manner. Most of the data is collected by the FLOSSmole research
team, yet they also accept data donation from other research
groups or similar projects. The scripts and programs that collects
the datasets from the Internet is also open for download and
donation. "

"Using
FLOSSmole [8] and FLOSSmetrics [9] as case studies, similar
systems as such are called {\textquotedblleft}repository of repositories (RoR){\textquotedblright} and
basic requirements of these systems are proposed. "},
	pages = {1 - 7},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Changsha, China},
	abstract = {Free / Libre / Open Source Software (FLOSS) data, such as bug reports, mailing lists and related webpages, contains valuable information for reusing open source software projects. Before conducting further experiment on FLOSS data, researchers often need to download these data into a local storage system. We refer to this pre-process as FLOSS data retrieval, which in many cases can be a challenging task. In this paper, we proposed a crawler framework to ease the process of FLOSS data retrieval. To cope with various types of FLOSS data scattered on the Internet, we designed the framework in a scalable manner where a crawler program can be easily plugged into the system to extend its functionality. Researchers can perform the retrieval process on datasets of various types and sources simply by adding new configurations to the system. We have implemented the framework and provided basic functions via web-based interfaces. We presented the usage of the system by a detailed case study where we retrieved various types of datasets related to Apache Lucene project using our framework.},
	keywords = {flossmole cited},
	isbn = {9781450323697},
	doi = {10.1145/2532443.2532454},
	author = {Yanzhen Zou and Bing Zie and Zhang, Lingxiao}
}
@article {1689,
	title = {A short report on WikiSym + OpenSym 2013},
	journal = {ACM SIGWEB Newsletter},
	year = {2013},
	month = {09/2013},
	pages = {1 - 2},
	abstract = {WikiSym + OpenSym 2013 is the 2013 Joint International Symposium on Open Collaboration, a conference for and by researchers and practitioners of open collaboration, which took place in Hong Kong on Aug 5-7, 2013.},
	issn = {19311745},
	doi = {10.1145/2528272.2528273},
	author = {Dirk Riehle}
}
@book {1538,
	title = {Socio-technical Congruence in OSS Projects: Exploring Conway{\textquoteright}s Law in FreeBSD},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {109 - 126},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Software development requires effective communication, coordination and collaboration among developers working on interdependent modules of the same project. The need for coordination is even more evident in open source projects where development is often more dispersed and distributed. In this paper, we study the match between the coordination needs established by the technical domain (i.e. source code) and the actual coordination activities carried out by the development team, such hypothetical match is also known as socio-technical congruence. We carry out our study by empirically examining Conway{\textquoteright}s law in FreeBSD project. Our study shows that the congruence measure is significantly high in FreeBSD and that the congruence value remains stable as the project matured.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_8},
	author = {Syeed, M.M. Mahbubul and Hammouda, Imed},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@article {gonzalez2013studying,
	title = {Studying the laws of software evolution in a long-lived FLOSS project},
	journal = {Journal of Software: Evolution and Process},
	year = {2013},
	publisher = {Wiley Online Library},
	abstract = {Some free, open-source software projects have been around for quite a long time, the longest living ones dating from the early 1980s. For some of them, detailed information about their evolution is available in source code management systems tracking all their code changes for periods of more than 15 years. This paper examines in detail the evolution of one of such projects, glibc, with the main aim of understanding how it evolved and how it matched Lehman{\textquoteright}s laws of software evolution. As a result, we have developed a methodology for studying the evolution of such long-lived projects based on the information in their source code management repository, described in detail several aspects of the history of glibc, including some activity and size metrics, and found how some of the laws of software evolution may not hold in this case.},
	url = {http://oa.upm.es/21355/1/smr1615.pdf},
	author = {Jesus M. Gonzalez-Barahona and Gregorio Robles and Herraiz, Israel and Ortega, Felipe}
}
@conference {1577,
	title = {Tools in Mining Software Repositories},
	booktitle = {2013 13th International Conference on Computational Science and Its Applications (ICCSA)},
	year = {2013},
	pages = {89 - 98},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Ho Chi Minh City, Vietnam},
	abstract = {Mining software repositories (MSR) is an important area of research. An international workshop on MSR has been established under the umbrella of international conference on software engineering (ICSE) in year 2004. The quality papers received and presented in the workshop has led to initiate full-fledged conference which purely focuses on issues related to mining software engineering data since 2007. This paper is the result of reviewing all the papers published in the proceedings of the conferences on Mining Software Repositories (MSR) and in other related conference/journals. We have analyzed the papers that contained experimental analysis of software projects related to data mining in software engineering. We have identified the data sets, techniques and tools used/ developed/ proposed in these papers. More than half of the papers are involved in the task accomplished by building or using the data mining tools to mine the software engineering data. It is apparent from the results obtained by analyzing these papers that MSR authors process the raw data which in general publicly available. We categorizes different tools used in MSR on the basis of newly developed, traditional data mining tools, prototype developed and scripts. We have shown the type of mining task that has been performed by using these tools along with the datasets used in these studies.},
	doi = {10.1109/ICCSA.2013.22},
	author = {Chaturvedi, K.K. and Sing, V.B. and Singh, Prashast}
}
@book {1534,
	title = {Towards a Reference Model on How to Utilise Open Standards in Open Source Projects: Experiences Based on Drupal},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {257 - 263},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

It is known that standards implemented in Open Source software (OSS) can promote a competitive market, reduce the risk for lock-in and improve interoperability, whilst there is limited knowledge concerning the relationship between standards and their implementations in OSS. In this paper we report from an ongoing case study conducted in the context of the ORIOS (Open Source software Reference Implementations of Open Standards) project in which influences between OSS communities and software standard communities are investigated. The study focuses on the Drupal project and three of its implemented standards (RDFa, CMIS, and OpenID).
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_19},
	author = {Andersson, Stefan and Feist, Jonas and Gustavsson, Tomas and Strindberg, Henrik and Gamalielsson, Jonas and Lundell, Bj{\"o}rn and Grahn, Alexander},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@article {1565,
	title = {Towards base rates in software analytics},
	journal = {Science of Computer Programming},
	year = {2013},
	month = {11/2013},
	abstract = {Nowadays a vast and growing body of open source software (OSS) project data is publicly available on the internet. Despite this public body of project data, the field of software analytics has not yet settled on a solid quantitative base for basic properties such as code size, growth, team size, activity, and project failure. What is missing is a quantification of the base rates of such properties, where other fields (such as medicine) commonly rely on base rates for decision making and the evaluation of experimental results. The lack of knowledge in this area impairs both research activities in the field of software analytics and decision making on software projects in general. This paper contributes initial results of our research towards obtaining base rates using the data available at Ohloh (a large-scale index of OSS projects). Zooming in on the venerable {\textquoteleft}lines of code{\textquoteright} metric for code size and growth, we present and discuss summary statistics and identify further research challenges.},
	keywords = {ohloh},
	issn = {01676423},
	doi = {10.1016/j.scico.2013.11.023},
	url = {http://www.sciencedirect.com/science/article/pii/S0167642313003079},
	author = {Bruntink, Magiel}
}
@article {1706,
	title = {Trends in Free, Libre, Open Source Software Communities: From Volunteers to Companies / Aktuelle Trends in Free-, Libre-, und Open-Source-Software-Gemeinschaften: Von Freiwilligen zu Unternehmen},
	journal = {it - Information Technology},
	volume = {55},
	year = {2013},
	month = {01/2013},
	abstract = {The first free/libre/open source software (FLOSS)
development communities were composed almost exclusively
of volunteers. They were individuals who, despite their
affiliation, contributed to the project on their own. They
decided which project to join, and their contributions were
personal in nature, even when in some cases they were
employees of companies with some interests in the project.
GNU, the first of such communities, and some others that
emerged during the late 1980s and 1990s, followed this
pattern. During the 1990s corporate interests started to
have a role in some FLOSS communities. Companies hired
people from those communities to gain influence, or tasked
their employees to contribute to them, again with the idea
of influencing their decisions. During the 2000s, corporate
communities, in which companies are first-class citizens,
have emerged, changing the rules and redefining the role of
volunteers and non-affiliated individuals. However, the role
of developers, with independence of the company for which
they work, is still important even in these communities.
This paper addresses this transition from volunteer-based
to company-based development communities, and explores
the structure and behavior of the latter.},
	issn = {1611-2776},
	doi = {10.1524/itit.2013.1012},
	url = {http://dirkriehle.com/wp-content/uploads/2013/10/itit.2013.1012.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/itit.2013.1012.pdf},
	author = {Jesus M. Gonzalez-Barahona and Gregorio Robles}
}
@article {1810,
	title = {Understanding How Companies Interact with Free Software Communities},
	journal = {IEEE Software},
	volume = {30},
	year = {2013},
	month = {9/2013},
	pages = {38 - 45},
	abstract = {When free, open source software development communities work with companies that use their output, it{\textquoteright}s especially important for both parties to understand how this collaboration is performing. The use of data analytics techniques on software development repositories can improve factual knowledge about performance metrics.
},
	issn = {0740-7459},
	doi = {10.1109/MS.2013.95},
	author = {Jesus M. Gonzalez-Barahona and Izquierdo-Cortazar, Daniel and Maffulli, Stefano and Gregorio Robles}
}
@proceedings {1504,
	title = {Understanding the Evolution of Type-3 Clones: An Exploratory Study },
	year = {2013},
	month = {05/2013},
	abstract = {Understanding the evolution of clones is important for both understanding the maintenance implications of clones and for building a robust clone management system. To this end, researchers have already conducted a number of studies to analyze the evolution of clones, mostly focusing on Type-1 and Type-2 clones. However, although there are a significant number of Type-3 clones in software systems, we know a little how they actually evolve. In this paper, we perform an exploratory study on the evolution of Type-1, Type-2, and Type-3 clones in six open source software systems written in two different programming languages and compare the result with a previous study to better understand the evolution of Type-3 clones. Our results show that although Type-3 clones are more likely to change inconsistently, the absolute number of consistently changed Type-3 clone classes is greater than that of Type-1 and Type-2. Type-3 clone classes also have a lifespan similar to that of Type-1 and Type-2 clones. In addition, a considerable number of Type-1 and Type-2 clones convert into Type-3 clones during evolution. Therefore, it is important to manage type-3 clones properly to limit their negative impact. However, various automated clone management techniques such as notifying developers about clone changes or linked editing should be chosen carefully due to the inconsistent nature of Type-3 clones.},
	author = {Ripon K. Saha and Chanchal K. Roy and Kevin A. Schneider and Perry, Dewayne E.}
}
@proceedings {1515,
	title = {Using Citation Influence to Predict Software Defects},
	year = {2013},
	month = {05/2013},
	abstract = {The software dependency network reflects structure and the developer contribution network reflects process. Previous studies have used social network properties over these networks to predict whether a software component is defect-prone. However, these studies do not consider the strengths of the dependencies in the networks. In our approach, we use a citation influence topic model to determine dependency strengths among components and developers, analyze weak and strong dependencies separately, and apply social network properties to predict defect-prone components. In experiments on Eclipse and NetBeans, our approach has higher accuracy than prior work.},
	keywords = {eclipse, netbeans, social network},
	author = {Wei Hu and Kenny Wong}
}
@proceedings {1492,
	title = {Using Developer Interaction Data to Compare Expertise Metrics},
	year = {2013},
	month = {05/2013},
	abstract = {The expertise of a software developer is said to be
a crucial factor for the development time required to complete
a task. Even if this hypothesis is intuitive, research has not yet
quantified the effect of developer expertise on development time.
A related problem is that the design space for expertise metrics is
large; out of the various automated expertise metrics proposed,
we do not know which metric most reliably captures expertise.
What prevents a proper evaluation of expertise metrics and
their relation with development time is the lack of data on
development tasks, such as their precise duration. Fortunately,
this data is starting to become available in the form of growing
developer interaction repositories. We show that applying MSR
techniques to these developer interaction repositories gives us the
necessary tools to perform such an evaluation.},
	url = {http://users.dcc.uchile.cl/~rrobbes/p/MSR2013-expertise.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MSR2013-expertise.pdf},
	author = {Robbes, Romain and Rothlisberger, David}
}
@article {1554,
	title = {Using software analytics to understand how companies interact in free software communities},
	journal = {IEEE Software},
	year = {2013},
	month = {2013},
	pages = {1 - 1},
	abstract = {

Free, open source software development communities may become large and complex. They may also be a focus of interest for competing companies relying on their outcomes, with their employees joining the development and maintenance effort. In those cases it is specially important for both companies and communities to understand how this collaboration is working, and how it matches their policies and expectations. In this paper we show two cases (OpenStack and WebKit) which we have studied using analytics techniques on the data obtained from their software development repositories. From them, we conclude that analytics on this data can improve the factual knowledge about how development communities are performing in aspects which are of interest to companies, and fundamental to ensure transparency and fairness.
},
	keywords = {openstack, webkit},
	issn = {0740-7459},
	doi = {10.1109/MS.2013.95},
	author = {Gonzalez-Barahona, Jesus and Izquierdo, Daniel and Maffulli, Stefano and Gregorio Robles}
}
@proceedings {1498,
	title = {Who Does What during a Code Review? Datasets of OSS Peer Review Repositories },
	year = {2013},
	month = {05/2013},
	abstract = {We present four datasets that are focused on the general roles of OSS peer review members. With data mined from both an integrated peer review system and code source repositories, our rich datasets comprise of peer review data that was automatically recorded. Using the Android project as a case study, we describe our extraction methodology, the datasets and their application used for three separate studies. Our datasets are available online at http://sdlab.naist.jp/reviewmining/},
	keywords = {android, case study, code review, data set, peer review, roles, source code},
	author = {Kazuki Hamasaki and Raula Gaikovina Kula and Norihiro Yoshida and A. E. Camargo Cruz and Kenji Fujiwara and Hajimu Iida}
}
@proceedings {1497,
	title = {Why So Complicated? Simple Term Filtering and Weighting for Location-Based Bug Report Assignment Recommendation},
	year = {2013},
	month = {05-2013},
	pages = {2-11},
	abstract = {Large software development projects receive many
bug reports and each of these reports needs to be triaged. An
important step in the triage process is the assignment of the
report to a developer. Most previous eorts towards improving
bug report assignment have focused on using an activity-based
approach. We address some of the limitations of activity-based
approaches by proposing a two-phased location-based approach
where bug report assignment recommendations are based on the
predicted location of the bug. The proposed approach utilizes
a noun extraction process on several information sources to
determine bug location information and a simple term weighting
scheme to provide a bug report assignment recommendation.
We found that by using a location-based approach, we achieved
an accuracy of 89.41\% and 59.76\% when recommending five
developers for the Eclipse and Mozilla projects, respectively.},
	keywords = {bug, bug report assignment, eclipse, File Activity Histories, Mining Software Artifacts, mozilla, Named Entity Recognition, POS Filtering},
	url = {http://www.cwu.edu/~janvik/papers/msr2013.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2013.pdf}
}
@proceedings {1499,
	title = {Will My Patch Make It? And How Fast?: Case Study on the Linux Kernel},
	year = {2013},
	month = {05/2013},
	abstract = {The Linux kernel follows an extremely distributed reviewing and integration process supported by 130 developer mailing lists and a hierarchy of dozens of Git repositories for version control. Since not every patch can make it and of those that do, some patches require a lot more reviewing and integration effort than others, developers, reviewers and integrators need support for estimating which patches are worthwhile to spend effort on and which ones do not stand a chance. This paper cross- links and analyzes eight years of patch reviews from the kernel mailing lists and committed patches from the Git repository to understand which patches are accepted and how long it takes those patches to get to the end user. We found that 33\% of the patches makes it into a Linux release, and that most of them need 3 to 6 months for this. Furthermore, that patches developed by more experienced developers are more easily accepted and faster reviewed and integrated. Additionally, reviewing time is impacted by submission time, the number of affected subsystems by the patch and the number of requested reviewers.},
	author = {Yujuan Jiang and Adams, Bram and Daniel M. German}
}
@article {1419,
	title = {Adoption of free/libre open source software in public organizations: factors of impac},
	journal = {Information Technology \& People},
	volume = {25},
	year = {2012},
	pages = {156-187},
	chapter = {156},
	abstract = {Purpose {\textendash} In this paper the authors aim to investigate the importance of factors for the adoption of free/libre open source software (FLOSS) in the public sector. They seek to evaluate how different factors impact during the initiation and implementation phases of the adoption process.

Design/methodology/approach {\textendash} The authors base the methodological approach on two exploratory case studies with a contrasting result logic. They build a multi-level framework grounded both on literature review, and feedback from stakeholders. They then apply the framework to two case studies to better frame the findings. They consider phases of adoption (initiation, implementation) and the levels of adoption (technological, organizational, environmental, individual).

Findings {\textendash} In the case studies, the authors found the importance of a strong and decision-centric management board to give the impulse for the initiation phase of the process. As perceived by the stakeholders, a strong governmental support is of paramount importance to increase the adoption at the public level, although in the case studies examined the initiation stage started from the impulse of a championing management. Both case studies passed the initiation phase successfully. Continuous employees{\textquoteright} training, organizational objectives consensus, and business process reengineering have been found important for the implementation phase. In the case study in which these factors were not in place, the implementation phase of adoption failed. Environmental factors {\textendash} although relevant for the initiation of the adoption process {\textendash} are less significant during the actual implementation of the adoption process, as the contrasting result logic from the case studies shows.

Research limitations/implications {\textendash} The study refers to two public organizations in a specific environmental setting. No causality among factors has been inferred. Quantitative objective data have been used to determine the success of adoption, for qualitative data multiple sources have been used when possible to limit threats to validity.

Practical implications {\textendash} The framework can be used by stakeholders in public organizations to better frame their adoption strategies and to compare results across institutions. Lessons learnt from the case studies can be useful to drive future adoptions of FLOSS.

Originality/value {\textendash} The framework combines phases of adoption and levels making it possible to frame the analysis of the case studies. It has been operationalized with a set of metrics, and with a protocol for the case studies to increase replicability value.},
	doi = {http://dx.doi.org/10.1108/09593841211232677},
	url = {http://www.emeraldinsight.com/journals.htm?articleid=17036351},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo}
}
@article {1400,
	title = {Analyzing and mining a code search engine usage log},
	journal = {Empirical Software Engineering},
	volume = {17},
	year = {2012},
	month = {8/2012},
	pages = {424 - 466},
	abstract = {This paper presents an analysis of a year long usage log of Koders, the first commercially available Internet-Scale code search engine (http://www.koders.com). The usage log comprises about ten million activities from more than three million users. Analysis of the usage data shows that despite of attracting a large number of visitors, Koders has a very sparse usage and that it lacks regular usage from many of its users. When compared to Web search, search behavior in Koders showed many similar patterns. A topic modeling analysis of the usage data shows what topics users of Koders are looking for. Observations on the prevalence of these topics among the users, and observations on how search and download activities vary across topics, lead to the conclusion that users who find code search engines usable are those who already know to a high level of specificity what to look for. This paper also presents a general categorization of these topics that provides insights on the different ways code search engine users express their queries. It identifies various forms of queries in Koders{\textquoteright}s log and the kinds of results addressed by the queries. It also provides several suggestions for improvements in code search engines based on the analysis of usage, topics, and query forms. The work presented in this paper is the first of its kind that reveals several insights on the usage of an Internet-Scale code search engine.},
	keywords = {code search, koders, search, search engine, topics},
	issn = {1573-7616},
	doi = {10.1007/s10664-010-9144-6},
	author = {Bajracharya, Sushil Krishna and Lopes, Cristina Videira}
}
@article {1395,
	title = {Automated topic naming: supporting cross-project analysis of software maintenance activities},
	journal = {Empirical Software Engineering},
	year = {2012},
	abstract = {Software repositories provide a deluge of software artifacts to analyze. Researchers have attempted to summarize, categorize, and relate these artifacts by using semi-unsupervised machine-learning algorithms, such as Latent Dirichlet Allocation (LDA). LDA is used for concept and topic analysis to suggest candidate word-lists or topics that describe and relate software artifacts. However, these word-lists and topics are difficult to interpret in the absence of meaningful summary labels. Current attempts to interpret topics assume manual labelling and do not use domain-specific knowledge to improve, contextualize, or describe results for the developers. We propose a solution: automated labelled topic extraction. Topics are extracted using LDA from commit-log comments recovered from source control systems. These topics are given labels from a generalizable cross-project taxonomy, consisting of non-functional requirements. Our approach was evaluated with experiments and case studies on three large-scale Relational Database Management System (RDBMS) projects: MySQL, PostgreSQL and MaxDB. The case studies show that labelled topic extraction can produce appropriate, context-sensitive labels that are relevant to these projects, and provide fresh insight into their evolving software development activities. },
	keywords = {LDA, maxdb, mysql, postgresql, topics},
	issn = {1573-7616},
	doi = {10.1007/s10664-012-9209-9},
	author = {Hindle, Abram and Ernst, Neil A. and Godfrey, Michael W. and Mylopoulos, John}
}
@proceedings {1470,
	title = {Binoculars: Comprehending Open Source Projects through Graphs},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {350-355},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Comprehending Open Source Software (OSS) projects requires dealing with huge historical information stored in heterogeneous repositories, such as source code versioning systems, bug tracking system, mailing lists, and revision history logs. In this paper, we present Binoculars, a prototype tool which aims to provide a platform for graph based visualization and exploration of OSS projects. We describe the issues need to be addressed for the design and implementation of a graph based tool and distill lessons learned for future guideline.},
	author = {Syeed, M.M. Mahbubul}
}
@article {1679,
	title = {Carrots and Rainbows: Motivation and Social Practice in Open Source Software Development},
	journal = {Management Information Systems Quarterly},
	volume = {36},
	year = {2012},
	pages = {649-676},
	abstract = {Open source software (OSS) is a social and economic phenomenon that raises fundamental questions about the motivations of contributors to information systems development. Some developers are unpaid volunteers who seek to solve their own technical problems, while others create OSS as part of their employment contract. For the past 10 years, a substantial amount of academic work has theorized about and empirically examined developer motivations. We review this work and suggest considering motivation in terms of the values of the social practice in which developers participate. Based on the social philosophy of Alasdair MacIntyre, we construct a theoretical framework that expands our assumptions about individual motivation to include the idea of a long-term, value-informed quest beyond short-term rewards. This motivation{\textendash}practice framework depicts how the social practice and its supporting institutions mediate between individual motivation and outcome. The framework contains three theoretical conjectures that seek to explain how collectively elaborated standards of excellence prompt developers to produce high-quality software, change institutions, and sustain OSS development. From the framework, we derive six concrete propositions and suggest a new research agenda on motivation in OSS.
},
	url = {https://sspaeth.de/uploads/CarrotsAndRainbows.pdf},
	author = {Georg von Krogh and Stefan Haefliger and Sebastian Spaeth and Martin W. Wallin}
}
@proceedings {1443,
	title = {Citizen Engineering: Evolving OSS Practices to Engineering Design and Analysis},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {61-77},
	publisher = {IFIP AICT},
	abstract = {Open Source Software (OSS) development has much in common with concepts such as crowdsourcing, citizen science, collective intelligence, human-based computation, and what we call {\textquotedblleft}Citizen Engineering (CE){\textquotedblright}. We report on several pilot projects that apply these shared principles of OSS development to engineering activities beyond software engineering. CE models harness human computing power from open communities, which commonly consist of a cohort of geographically and/or institutionally scattered citizens - professionals or amateurs - to collaboratively solve real-world problems. In most cases, the problems targeted are challenging to computers, but manageable or trivial to human intelligence. In these systems, while humans play fundamental roles, whether they are project architects or problem solvers, the implementation of CE is greatly facilitated by the advance of information technology, particularly the Internet, considered as "creative mode of user interactivity, not merely a medium between messages and people" [10]. In this paper, we characterize existing citizen engineering practices into 6 major categories, followed by a discussion of 4 ongoing projects, aiming to provide new perspectives and insights for achieving successful CE project designs.},
	author = {Zhai, Zhi and Kijewski-Correa, Tracy and Kareem, Ashan and Hachen, David and Madey, Gregory}
}
@article {1401,
	title = {Clones: what is that smell?},
	journal = {Empirical Software Engineering},
	volume = {17},
	year = {2012},
	month = {8/2012},
	pages = {503 - 530},
	abstract = {Clones are generally considered bad programming practice in software engineering folklore. They are identified as a bad smell (Fowler et al. 1999) and a major contributor to project maintenance difficulties. Clones inherently cause code bloat, thus increasing project size and maintenance costs. In this work, we try to validate the conventional wisdom empirically to see whether cloning makes code more defect prone. This paper analyses the relationship between cloning and defect proneness. For the four medium to large open source projects that we studied, we find that, first, the great majority of bugs are not significantly associated with clones. Second, we find that clones may be less defect prone than non-cloned code. Third, we find little evidence that clones with more copies are actually more error prone. Fourth, we find little evidence to support the claim that clone groups that span more than one file or directory are more defect prone than collocated clones. Finally, we find that developers do not need to put a disproportionately higher effort to fix clone dense bugs. Our findings do not support the claim that clones are really a {\textquotedblleft}bad smell{\textquotedblright} (Fowler et al. 1999). Perhaps we can clone, and breathe easily, at the same time. },
	issn = {1573-7616},
	doi = {10.1007/s10664-011-9195-3},
	author = {Rahman, Foyzur and Christian Bird and Devanbu, Premkumar}
}
@proceedings {1439,
	title = {A Comprehensive Study of Software Forks: Dates, Reasons and Outcomes},
	volume = {378},
	year = {2012},
	pages = {1-14},
	publisher = {IFIP AICT},
	abstract = {Summary. In general it is assumed that a software product evolves within the authoring company or group of developers that develop the project. However, in some cases different groups of developers make the software evolve in different directions, a situation which is commonly known as a fork. In the case of free software, although forking is a practice that is considered as a last resort, it is inherent to the four freedoms. This paper tries to shed some light on the practice of forking. Therefore, we have identified significant forks, several hundreds in total, and have studied them in depth. Among the issues that have been analyzed for each fork is the date when the forking occurred, the reason of the fork, and the outcome of the fork, i.e., if the original or the forking project are still developed. Our investigation shows, among other results, that forks occur in every software domain, that they have become more frequent in recent years, and that very few forks merge with the original project.},
	keywords = {forking, forks, free software, Legal, open source, social, software evolution, sustainability},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper_0.pdf},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M.}
}
@conference {1485,
	title = {A Conceptual Framework for Open Source Software Test Process},
	booktitle = {2012 IEEE 36th IEEE Annual Computer Software and Applications Conference Workshops (COMPSACW)},
	year = {2012},
	pages = {458 - 463},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Izmir, Turkey},
	abstract = {The broad acceptance and use of Open Source Software (OSS) has underscored the necessity of investigating the means of assuring their quality. With the aim of identifying an OSS test process, three well-known OSS projects, namely Apache HTTP server, Mozilla Web browser, and NetBeans IDE were studied. In these studies, three activities were found similar to the activities of the ISO/IEC Test Process Standard. However, major differences were observed in tasks related to each of the test process activities. To systematize the OSS test process, an Open Source Software Test Process Framework (OSS-TPF) is proposed. The alignment of OSS-TPF with the ISO/IEC Test Process Standard is illustrated.},
	isbn = {978-0-7695-4758-9},
	doi = {10.1109/COMPSACW.2012.87},
	url = {http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6341619},
	author = {Abdou, Tamer and Grogono, Peter and Kamthan, Pankaj}
}
@conference {1357,
	title = {Content classification of developer emails},
	booktitle = {Proceedings of the 34th IEEE/ACM International Conference On Software Engineering (ICSE 2012)},
	year = {2012},
	note = {We created a web application to manually classify email content in the chosen categories. We classified a statistically significant set of emails from four java open source software (OSS) systems, used to evaluate the accuracy of our approach.
The contributions of this paper are:
1) a novel approach that fuses parsing and ML techniques
for classification of email lines;
2) a web application to manually classify email content; 3) the manual classification of a statistically significant
sample set of emails (for a total of 67,792 lines) from mailing lists of four different software systems{\textendash}in the form of a freely available benchmark; and
4) the empirical evaluation of our approach against the benchmark},
	month = {06/2012},
	abstract = {Emails related to the development of a software system contain information about design choices and issues encountered during the development process. Exploiting the knowledge embedded in emails with automatic tools is challenging, due to the unstructured, noisy and mixed language nature of this communication medium. Natural language text is often not well-formed and is interleaved with languages with other syntaxes, such as code or stack traces.

We present an approach to classify email content at line level. Our technique classifies email lines in five categories (i.e., text, junk, code, patch, and stack trace) to allow one to subsequently apply ad hoc analysis techniques for each category. We evaluated our approach on a statistically significant set of emails gathered from mailing lists of four unrelated open source systems.},
	keywords = {email, Emails, Empirical software engineering, mailing list, natural language, Unstructured Data Mining},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icse2012.pdf},
	author = {Bacchelli, Alberto and Dal Sasso, Tommaso and D{\textquoteright}Ambros, Marco and Lanza, Michele}
}
@conference {1317,
	title = {Describing the Software Forge Ecosystem},
	booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences},
	year = {2012},
	note = {http://flossmole.org/content/everything-you-ever-wanted-know-about-software-forges-code-forges-june-2011},
	month = {01/2012},
	pages = {3416-3425},
	abstract = {Code forges are online software systems that are designed to support teams doing software development work. There have been few if any attempts in the research literature to describe the web of people, projects, and tools that make up the free, libre, and open source (FLOSS) forge ecosystem. The main contributions of this paper are (1) to introduce a classification of FLOSS-oriented forges according to their characteristics; (2) to describe the forge-level and project-level data and artifacts currently available at each FLOSS forge; (3) to show various patterns already discovered in the FLOSS forge ecosystem, such as timelines of creation or arrangements by size or feature; (4) to make some recommendations to forge providers and data collectors about how to expose the structure and information in the forges; and (5) to describe the effort needed to extend our publicly- available information about the FLOSS forge ecosystem into the future.},
	keywords = {features, FLOSS, forge, hosting, metrics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/SquireWilliamsHICSS2012.pdf},
	author = {Squire, Megan and Williams, David}
}
@proceedings {1448,
	title = {Designing Secure Systems Based on Open Architectures with Open Source and Closed Source Components},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {144-159},
	abstract = {The development and evolution of secure open architecture systems has received insufficient consideration. Such systems are composed of both open source and closed software software components subject to different security requirements in an architecture in which evolution can occur by evolving existing components, replacing them, or refactoring their interfaces, interconnections and configuration. But this may result in possible security requirements conflicts and organizational liability for failure to fulfill security obligations. We are developing an approach for understanding and modeling software security requirements as security licenses, as well as for analyzing conflicts among groups of such licenses in realistic system contexts and for guiding the acquisition, integration, or development of systems with open source components in such an environment. Consequently, this paper reports on our efforts to extend our existing approach to specifying and analyzing software Intellectual Property (IP) licenses to now address software security licenses that can be associated with secure OA systems.},
	author = {Walt Scacchi and Alspaugh, Thomas}
}
@conference {1680,
	title = {Developing an h-index for OSS developers},
	booktitle = {2012 9th IEEE Working Conference on Mining Software Repositories (MSR)},
	year = {2012},
	pages = {251 - 254},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Zurich},
	abstract = {The public data available in Open Source Software (OSS) repositories has been used for many practical reasons: detecting community structures; identifying key roles among developers; understanding software quality; predicting the arousal of bugs in large OSS systems, and so on; but also to formulate and validate new metrics and proof-of-concepts on general, non-OSS specific, software engineering aspects. One of the results that has not emerged yet from the analysis of OSS repositories is how to help the {\textquotedblleft}career advancement{\textquotedblright} of developers: given the available data on products and processes used in OSS development, it should be possible to produce measurements to identify and describe a developer, that could be used externally as a measure of recognition and experience. This paper builds on top of the h-index, used in academic contexts, and which is used to determine the recognition of a researcher among her peers. By creating similar indices for OSS (or any) developers, this work could help defining a baseline for measuring and comparing the contributions of OSS developers in an objective, open and reproducible way.},
	isbn = {978-1-4673-1760-3},
	doi = {10.1109/MSR.2012.6224288},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MSR2012.pdf},
	author = {A. Capiluppi and Serebrenik, A. and Youssef, A.}
}
@proceedings {1475,
	title = {Discussion on the Problems to be Solved toward the Migration to OSS Productivity Software in the Business Enterprises},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {377-382},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {In recent years, there is a tendency to migrate from proprietary productivity software to open-source productivity software, especially in government offices and municipal offices. ODPG (OpenOffice.org \& OpenDocument Format Promotion Group, Japan) is an organization founded in order to promote the migration to the OSS productivity software in private enterprises as well. In the case evaluation work group of ODPG, business solutions about use of OpenOffice.org have been discussed many times, for the purpose of supporting the migration to OpenOffice.org, by collecting and feeding back the information of case studies useful for the member companies. This paper reports several subjects and solutions, such as promotion strategy for OpenOffice.org to be widely used, the problem in file exchange with the other stakeholders, preparation of use environment, and security issues, which were discussed in the work group.},
	author = {Iio, Jun and Ogawa, Tomotaka}
}
@proceedings {1458,
	title = {Do More Experienced Developers Introduce Fewer Bugs?},
	volume = {378},
	year = {2012},
	note = {"Some Mozilla Foundation projects have been the selected case of study for this paper. The analysis is based on the Mercurial repository which offers a list of repositories that can be easily cloned. As a summary, 19 projects were analyzed, with more than 100,000 commits, more than 2,500 authors and around 4 years of history up to June 2011."},
	month = {09/2012},
	pages = {268-273},
	publisher = {IFIP AICT,  Springer},
	abstract = {Developer experience is a common matter of study in the software maintenance and evolution research literature. However it is still not well understood if less experienced developers are more prone to introduce errors in the source code than their more experienced colleagues. This paper aims to study the relationships between experience and the bug introduction ratio using the Mozilla community as case of study.
As results, statistical differences among developers with different levels of experience has not been observed, when the expected result would have been the opposite1.},
	keywords = {mercurial, mozilla, scm, source code analysis},
	author = {Izquierdo-Cort{\'a}zar, Daniel and Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M.}
}
@proceedings {1462,
	title = {Does OSS Affect E-Government Growth? An Econometric Analysis on the Impacting Factors},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {292-297},
	publisher = {IFIP AICT,  Springer},
	abstract = {Inspired by the OSS values, an increasing number of different forms of open initiatives have come to the fore. In the context of eGovernment the notion of open government has met wide acceptance among nations and became closely related to one of its goals. Open government shares with OSS the notions of collaboration, participation and transparency and many actions towards OSS into eGovernment reform policies, have been recorded worldwide. The study investigates the relationship between OSS growth and eGovernment. A theoretical framework of the theories of institutionalism, growth and human capital is proposed as the guiding theoretical lens to identify possible influencing factors that together with OSS are evaluated for their magnitude of impact on eGovernment growth across different economic environments.},
	keywords = {eGovernment adoption, growth theory, human capital theory, institutionalism},
	author = {Lakka, Spyridoula and Stamati, Teta and Martakos, Draculis}
}
@proceedings {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}
}
@proceedings {1465,
	title = {Forking the Commons: Developmental Tensions and Evolutionary Patterns in Open Source Software},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {310-315},
	publisher = {IFIP AICT,  Springer},
	abstract = {Open source software (OSS) presents opportunities and challenges for developers to exploit its commons based licensing regime by creating specializations of a software technology to address plurality of goals and priorities. By {\textquoteleft}forking{\textquoteright} a new branch of development separate from the main project, development diverges into a path in order to relieve tensions related to specialization, which later encounters new tensions. In this study, we first classify forces and patterns within this divergence process. Such tensions may stem from a variety of sources including internal power conflicts, emergence of new environmental niches such as demand for specialized uses of same software, or differences along stability vs. development speed trade-off. We then present an evolutionary model which combines divergence options available to resolve tensions, and how further tensions emerge. In developing this model we attempt to define open software evolution at the level of systems of software, rather than at individual software project level.},
	keywords = {divergence, forking, software evolution, specialization},
	author = {Gen{\c c}er, Mehmet and {\"O}zel, B{\"u}lent}
}
@proceedings {1454,
	title = {Free and Open Source Software Adoption in Emerging Markets: An Empirical Study in the Education Sector},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {244-249},
	publisher = {IFIP AICT,  Springer},
	abstract = {The adoption of Free and Open Source Software (FOSS) in the education sector in emerging markets holds much promise, but should be accompanied by a well-informed decision to ensure that the potential value is realized. The research conducted provides insight into the pragmatic factors driving the adoption of FOSS in the education environment, as well as those aspects inhibiting adoption. This study indicates an increasing readiness to accept FOSS in the education sector, where the more successful organizations show a readiness to adopt a comprehensive decision model to ensure the installation of appropriate ICT infrastructure, including FOSS, for the future.},
	author = {Gangadharan, G.R. and Butler, Martin}
}
@article {flosswp403,
	title = {Free/Libre Open Source Software: What We Know and What We Do Not Know},
	journal = {ACM Computing Surveys},
	volume = {44},
	year = {2012},
	publisher = {ACM},
	edition = {2},
	abstract = {We review the empirical research on Free/Libre Open Source Software (FLOSS) development and assess the state of the literature. Our review is organized around an input-mediator-output-input (IMOI) model. We start with a description of the articles selected for the review. We then discuss findings of this literature categorized into issues pertaining to inputs (e.g., member characteristics, technology use and project characteristics), processes (software development and social processes), emergent states (e.g., trust and task related states) and outputs (e.g. team performance, FLOSS implementation and project evolution). Based on this review, we suggest research questions, including methodological and theoretical issues, to guide future inquiry in this area.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/floss_review_paper.pdf},
	author = {Kevin Crowston and Kangning Wei and Howison, James and Andrea Wiggins}
}
@proceedings {1461,
	title = {From Open Source Software to Open Source Hardware},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {286-291},
	publisher = {IFIP AICT,  Springer},
	abstract = {The open source software principles progressively give rise to new initiatives for culture (free culture), data (open data) or hardware (open hardware). The open hardware is experiencing a significant growth but the business models and legal aspects are not well known. This paper is dedicated to the economics of open hardware. We define the open hardware concept and determine intellectual property tools we can apply to open hardware, with a strong focus on open source licenses and practices. We next conduct some case studies in order to determine which licenses and business models are used by open hardware companies. We show some strong similarities with open source software and propose new opportunities for future works.},
	author = {Viseur, Robert}
}
@proceedings {1477,
	title = {Future Smart Metering Runs on Open Source {\textendash} Challenges and the GuruxAMI Project},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {389-394},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {More and more devices are coming to Internet and organizations are using more devices to measure things. Challenges include a huge amount of different protocols and a risk of technological lock-in. Because of new innovations and demands new protocols are coming out all the time. Increasing amount of protocols makes it harder to collect data from different data sources and save it to one place. If we want to make tailored reports it is important that we can save all collected data to the one place. This paper presents an overview of how the industrial research project GuruxAMI (Gurux Advanced Metering Infrastructure) tries to solve this problem. An overarching goal of the project is to make an open platform that can be used to collect data from different data sources using different protocols and save collected data to the one place. This will be done by developing Open Source platform that can handle different protocols.},
	author = {Kurunsaari, Mikko}
}
@proceedings {1444,
	title = {Gender Differences in Early Free and Open Source Software Joining Process},
	volume = {378},
	year = {2012},
	note = {"We examined subscriber logs and data for six FOSS projects..."
"We examined the differences between posters and non-posters to determine the attrition rate..."
"Using data from the US Census, we matched names to lists of the most common female and male names. We identified 666 users using this process."},
	month = {09/2012},
	pages = {78-93},
	publisher = {IFIP AICT, Springer},
	address = {Eighth International Conference on Open Source Systems (OSS 2012)},
	abstract = {With the growth of free and open source software (FOSS) and the adoption of FOSS solutions in business and everyday life, it is important that projects serve their growingly diverse user base. The sustainability of FOSS projects relies on a constant influx of new contributors. Several large demo- graphic surveys found that FOSS communities are very homogenous, dominated by young men, similar to the bias existing in the rest of the IT workforce. Building on previous research, we examine mailing list subscriptions and posting statistics of female FOSS participants. New participants often experience their first interaction on a FOSS project{\textquoteright}s mailing list. We explored six FOSS projects {\textendash} Buildroot, Busybox, Jaws, Parrot, uClibc, and Yum. We found a declining rate of female participation from the 8.27\% of subscribers, to 6.63\% of posters, and finally the often reported code contributor rate of 1.5\%. We found a disproportionate attrition rate among women along every step of the FOSS joining process.},
	keywords = {buildroot, busybox, diversity, email, jaws, joining process, mailing lists, parrot, uClibc, Yum},
	author = {Kuechler, Victor and Gilbertson, Claire and Jensen, Carlos}
}
@proceedings {1476,
	title = {How Can Open Standards Be Effectively Implemented in Open Source? Challenges and the ORIOS Project},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {383-388},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Many organisations are currently restricted in their choice of software because of restrictions imposed by existing systems. Challenges include a lack of interoperability and a risk of technological lock-in, which many small companies seek to address by utilising Open Standards and Open Source implementations of such standards when developing and deploying systems. This paper presents an overview of how the industrial research project ORIOS (Open Source software Reference Implementations of Open Standards) seeks to address identified challenges. An overarching goal of the project is to improve understanding within organisations of Open Standards, Open Source Reference Implementations, and the ecosystems around them. This will be done by developing a reference model of necessary and desirable features of an Open Standard, and how Open Standards and their implementations can be utilised by small companies in different usage contexts. An action case study approach will be used as a core strategy for evolving a reference model together with Swedish companies.},
	author = {Lundell, Bj{\"o}rn and AbduraHmanovic, Admir and Andersson, Stefan and Bergström, Erik and Feist, Jonas and Gamalielsson, Jonas and Gustavsson, Tomas and Kahlbom, Roger and Papaxanthis, Konstantin}
}
@article {1397,
	title = {How do open source communities blog?},
	journal = {Empirical Software Engineering},
	year = {2012},
	abstract = {We report on an exploratory study, which aims at understanding how software communities use blogs compared to conventional development infrastructures. We analyzed the behavior of 1,100 bloggers in four large open source communities, distinguishing between committing bloggers and other community members. We observed that these communities intensively use blogs with one new entry every 8 h. A blog entry includes 14 times more words than a commit message. When analyzing the content of the blogs, we found that committers and others bloggers write about similar topics. Most popular topics in committers{\textquoteright} blogs represent high-level concepts such as features and domain concepts, while source code related topics are discussed in 15\% of their posts. Other community members frequently write about community events and conferences as well as configuration and deployment topics. We found that the blogging peak period is usually after the software is released. Moreover, committers are more likely to blog after corrective engineering than after forward engineering and re-engineering activities. Our findings call for a hypothesis-driven research to (a) further understand the role of social media in dissolving the collaboration boundaries between developers and other stakeholders and (b) integrate social media into development processes and tools. },
	keywords = {blog, blogs},
	issn = {1573-7616},
	doi = {10.1007/s10664-012-9211-2},
	author = {Pagano, Dennis and Maalej, Walid}
}
@article {1519,
	title = {How the FLOSS Research Community Uses Email Archives},
	journal = {International Journal of Open Source Software and Processes},
	volume = {4},
	year = {2012},
	note = {classifies 72 FLOSS papers into various analysis categories},
	month = {12/2012},
	pages = {37 - 59},
	abstract = {Artifacts of the software development process, such as source code or emails between developers, are a frequent object of study in empirical software engineering literature. One of the hallmarks of free, libre, and open source software (FLOSS) projects is that the artifacts of the development process are publicly-accessible and therefore easily collected and studied. Thus, there is a long history in the FLOSS research community of using these artifacts to gain understanding about the phenomenon of open source software, which could then be compared to studies of software engineering more generally. This paper looks specifically at how the FLOSS research community has used email artifacts from free and open source projects. It provides a classification of the relevant literature using a publicly-available online repository of papers about FLOSS development using email. The outcome of this paper is to provide a broad overview for the software engineering and FLOSS research communities of how other researchers have used FLOSS email message artifacts in their work},
	keywords = {email, email archives, literature, mailing lists, review, Survey},
	issn = {1942-3934},
	doi = {10.4018/jossp.2012010103},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ijossp_v3_PREPRINT.pdf},
	author = {Squire, Megan}
}
@proceedings {1472,
	title = {Hybrid Business Models in Software Product Industry: Patterns and Challenges},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {362-367},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Operating in software product industry is becoming an increasingly risky proposition. Compressed timeline for product development combined with need to reduce cost has compelled organizations to look at new ways of doing business. One such avenue is combining the erstwhile conflicting practices of open source and closed source software. This industry paper highlights common patterns and challenges encountered in operationalizing such business models. The findings are based on a larger multiple case study research involving six such software products.},
	author = {Deodhar, Swanand J. and Saxena, Kalbhushan C. and Ruohonen, Mikko}
}
@proceedings {1457,
	title = {The Impact of Formal QA Practices on FLOSS Communities {\textendash} The Case of Mozilla},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {262-267},
	publisher = {IFIP AICT,  Springer},
	abstract = {The number of FLOSS projects that include a QA step in the development model is increasing which suggests that a new layer may be emerging in the classic {\textquotedblleft}onion model{\textquotedblright}. This change might affect the information flow within projects and implicitly their sustainability. Communities, the essential resource of FLOSS projects, have been extensively studied but questions concerning QA remain. This paper takes a step towards answering such questions by analyzing QA mailing lists and issue tracker data for the Mozilla group of projects. Because the Bugzilla data set contains over half a million bugs, data processing and analysis is a considerable challenge for this research. The provisional conclusions are that QA activity may not be increasing steadily over time but is dependent on other factors and that the QA team and other groups of contributors form a highly connected network that doesn{\textquoteright}t contain isolates.},
	keywords = {email, information flow, mailing lists, mozilla, quality assurance, social network analysis, test},
	author = {Barham, Adina}
}
@conference {1640,
	title = {Integrating developer-related information across open source repositories},
	booktitle = {2012 IEEE 13th International Conference on Information Reuse \& Integration (IRI)2012 IEEE 13th International Conference on Information Reuse \& Integration (IRI)},
	year = {2012},
	pages = {69 - 76},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Las Vegas, NV, USA},
	abstract = {Software developers use various software repositories in order to interact with each other or to solve software related problems. They are required to adopt an identity for each of the software repositories they wanted to use. Quite often developers are also found on different code forges developing open source projects. It is worth mentioning that the information relevant to the developers are distributed on the Web among different data sources each requires an ID and an authentication mechanism. In this paper, we propose to interlink the identities of a developer across different data sources on the Web. Further, we show the benefit of integrating developer-related information from different data sources using some real-world scenarios.},
	isbn = {978-1-4673-2283-6},
	doi = {10.1109/IRI.2012.6302993},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Iqbal_A_et_al_Aug_2012.pdf},
	author = {Iqbal, Aftab and Hausenblas, Michael}
}
@article {1589,
	title = {Integrating FLOSS repositories on the Web},
	year = {2012},
	note = {"To provide the researchers easy access to the project{\textquoteright}s data, two research projects were initiated (with slightly different objective)
by the FLOSS research community which are FLOSSmole and FLOSSMetrics , also known as {\textquotedblleft}repository of repositories (RoR){\textquotedblright}. These RoRs were created to consolidate metadata and analysis of projects from a variety of code forges into a centralized place for use by the researchers in academia and industry.

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

Names are not available for the developers in the database dump of
Googlecode provided by FLOSSmole, so we consider matching only developer ID(s) in the case of
Googlecode."},
	month = {2012},
	abstract = {This paper provides a novel approach to the problem of integrating data from multiple code forges of FLOSS. We review the current problems in integrating the data from multiple forges and argue that Semantic Web technologies are suitable for representing knowledge contained in code forges. Further, we show the advantage of linking the metadata of projects to other data sources on the Web which will enable querying extra information from the Web. The paper briefly describes how the modeling is achieved and what benefits can be obtained by enabling linking to other relevant data sources already available on the Web.},
	keywords = {flossmole, google code, sourceforge},
	url = {https://www.researchgate.net/publication/259757473_Integrating_FLOSS_repositories_on_the_Web},
	attachments = {https://flosshub.org/sites/flosshub.org/files/DERI-TR-AFTAB-2012-12-10_0.pdf},
	author = {Iqbal, Aftab and Cyganiak, Richard and Hausenblas, Michael}
}
@book {1417,
	title = {Internet Success: A Study of Open Source Software Commons},
	year = {2012},
	note = {Supplementary material available: http://www.umass.edu/opensource/schweik/supplementary.html},
	publisher = {MIT Press},
	organization = {MIT Press},
	type = {Book},
	address = {Cambridge, MA, USA},
	keywords = {flossmole, srda},
	url = {http://tinyurl.com/d3e4545},
	author = {Schweik, C. M. and English, R.}
}
@conference {Alspaugh:2012:LS:2419620.2419854,
	title = {Licensing Security},
	booktitle = {Proceedings of the 2012 Fifth International Workshop on Requirements Engineering and Law (RELAW)},
	series = {RELAW {\textquoteright}12},
	year = {2012},
	pages = {25{\textendash}28},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {There exist legal structures defining the exclusive rights of authors, and means for licensing portions of them to others in exchange for appropriate obligations. We propose an analogous approach for security, in which portions of exclusive security rights owned by system stakeholders may be licensed as needed to others, in exchange for appropriate security obligations. Copyright defines exclusive rights to reproduce, distribute, and produce derivative works, among others. We envision exclusive security rights that might include the right to access a system, the right to run specific programs, and the right to update specific programs or data, among others. Such an approach uses the existing legal structures of licenses and contracts to manage security, as copyright licenses are used to manage copyrights. At present there is no law of {\textquotedblleft}security right{\textquotedblright} as there is a law of copyright, but with the increasing prevalence and prominence of security attacks and abuses, of which Stuxnet and Flame are merely the best known recent examples, such legislation is not implausible. We discuss kinds of security rights and obligations that might produce fruitful results, and how a license structure and approach might prove more effective than security policies.},
	isbn = {978-1-4673-4380-0},
	doi = {10.1109/RELAW.2012.6347799},
	url = {http://dx.doi.org/10.1109/RELAW.2012.6347799},
	author = {Alspaugh, Thomas A. and Walt Scacchi}
}
@proceedings {1467,
	title = {A Linguistic Analysis on How Contributors Solve Software Problems in a Distributed Context},
	volume = {378},
	year = {2012},
	note = {"... a sample of 4109 bug reports was extracted from Bugzilla bug report repository"
"The analysis of our sample allows identifying the roles of participants in this activity according to their hierarchical statutes in the community. "
"we look statistically at words that people use in Bugzilla to discern differences in the discourse and representation between participants (core and periphery)"},
	month = {09/2012},
	pages = {322-330},
	publisher = {IFIP AICT,  Springer},
	abstract = {There is a little understanding of distributed solving activities in Open Source communities. This study aimed to provide some insights in this way. It was applied to the context of Bugzilla, the bug tracking system of Mozilla community. This study investigated the organizational aspects of this meditated, complex and highly distributed context through a linguistic analysis method. The main finding of this research shows that the organization of distributed problem-solving activities in Bugzilla isn{\textquoteright}t based only on the hierarchical distribution of the work between core and periphery participants but on their implication in the interactions. This implication varies according to the status of each one participant in the community. That is why we distinguish their roles, as well as, the established modes to manage such activity.},
	keywords = {bug report, bugzilla, linguistic, text mining},
	author = {Masmoudi, H{\'e}la and Boughzala, Imed}
}
@article {1879,
	title = {Linux Kernel Development: How Fast it is Going, Who is Doing It, What They are Doing, and Who is Sponsoring It},
	year = {2012},
	month = {03/2012},
	institution = {The Linux Foundation},
	abstract = {The kernel which forms the core of the Linux system is the result of one of the largest cooperative software projects ever attempted. Regular 2-3 month releases deliver stable updates to Linux users, each with signi cant new features, added device support, and improved performance. The rate of change in the kernel is high and increasing, with between 8,000 and 12,000 patches going into each recent kernel release. These releases each contain the work of over 1,000 developers representing nearly 200 corporations.
Since 2005, over 7,800 individual developers from almost 800 different companies have contributed to the kernel. The Linux kernel, thus, has become a common resource developed on a massive scale by companies which are  erce competitors in other areas.
This is the fourth update of this document, which has been published roughly annually since 2008. It covers development through the 3.2 release, with an emphasis on the releases (2.6.36 to 3.2) made since the last update. It has been a busy period, with seven kernel releases created, many signi cant changes made, and continual growth of the kernel developer and user community.
},
	keywords = {corporate, corporations, developers, linux kernel, metrics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lf_kernel_development_2012.pdf},
	author = {Corbet, Jonathan and Greg Kroah-Hartman and Amanda McPherson}
}
@proceedings {1441,
	title = {Long-Term Sustainability of Open Source Software Communities beyond a Fork: A Case Study of LibreOffice},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {29-47},
	publisher = {IFIP AICT},
	abstract = {Many organisations have requirements for long-term sustainable software systems and associated communities. In this paper we consider long-term sustainability of Open Source software communities in Open Source projects involving a fork. There is currently a lack of studies in the literature that address how specific Open Source software communities are affected by a fork. We report from a case study aiming to investigate the developer community around the LibreOffice project, which is a fork from the OpenOffice.org project. The results strongly suggest a long-term sustainable community and that there are no signs of stagnation in the project 15 months after the fork. Our analysis provides details on the LibreOffice developer community and how it has evolved from the OpenOffice.org community with respect to project activity, long-term involvement of committers, and organisational influence over time. The findings from our analysis of the LibreOffice project make an important contribution towards a deeper understanding of challenges regarding long-term sustainability of Open Source software communities.},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn}
}
@proceedings {1440,
	title = {A Model of Open Source Developer Foundations},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {15-28},
	publisher = {IFIP AICT},
	abstract = {Many community open source projects are of high economic relevance. As these projects mature, their leaders face a choice of continuing the project as is, making the project join an existing foundation, or creating their own foundation for the project. This article presents a model of open source developer foundations that project leaders can use to compare existing foundations with their needs or to design their own. The model is based on a three- iteration qualitative study involving interviews and supplementary materials review. To demonstrate its usefulness, we apply the model to nine foundations and present their organizational choices in a comparative table format.},
	url = {http://dirkriehle.com/uploads/2012/05/Riehle-MOSDF-v12-Final-Web.pdf},
	author = {Dirk Riehle and Sebastian Berschneider}
}
@conference {1813,
	title = {Modification and developer metrics at the function level: Metrics for the study of the evolution of a software project},
	booktitle = {2012 3rd International Workshop on Emerging Trends in Software Metrics (WETSoM)},
	year = {2012},
	pages = {49 - 55},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Zurich, Switzerland},
	abstract = {Software evolution, and particularly its growth, has been mainly studied at the file (also sometimes referred as module) level. In this paper we propose to move from the physical towards a level that includes semantic information by using functions or methods for measuring the evolution of a software system. We point out that use of functions-based metrics has many advantages over the use of files or lines of code. We demonstrate our approach with an empirical study of two Free/Open Source projects: a community-driven project, Apache, and a company-led project, Novell Evolution. We discovered that most functions never change; when they do their number of modifications is correlated with their size, and that very few authors who modify each; finally we show that the departure of a developer from a software project slows the evolution of the functions that she authored.
},
	isbn = {978-1-4673-1763-4},
	doi = {10.1109/WETSoM.2012.6226993},
	author = {Gregorio Robles and Herraiz, Israel and Daniel M. German and Izquierdo-Cortazar, Daniel}
}
@conference {1318,
	title = {Network-Based Analysis of the Structure and Evolution of an Open Source Software Product},
	booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences},
	year = {2012},
	note = {"raw data about the product structure is extracted from the source code"},
	month = {01/2012},
	pages = {3436-3445},
	abstract = {In this paper, an analysis of product structures in open source software (OSS) at both product level and module level is presented. At the product level, the product structures are modeled as complex networks, and the evolutionary characteristics of product structures are analyzed by using network analysis metrics. At the module level, linking mechanisms, which describe how a module is attached with other modules, are proposed. The linking mechanisms are modeled as probability functions dependent on the degrees of linking modules. A case study from an open source software project, Drupal, is presented. The evolutionary trends of Drupal product structures are analyzed and discussed. Finally, a model is presented to illustrate the effects of linking mechanisms at the module level on the product structures at the system level. The results indicate that the model built using the proposed linking mechanisms generates networks whose evolutionary characteristics are close to that of the original network.},
	keywords = {drupal, source code},
	author = {Le, Qize and Panchal, Jitesh H.}
}
@proceedings {1466,
	title = {A Novel Application of Open Source Technologies to Measure Agile Software Development Process},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {316-321},
	publisher = {IFIP AICT,  Springer},
	abstract = {In the last 10 years Open Source products have been widely used in industry. New methodologies and best practices to develop Open Source software appeared. In this work, we present an application that runs on Android-based mobile phones and collects proximity data with other devices via Bluetooth. The application gives new insights into measuring proximity inside a team of software developers. Data collection process is automatic so that the team members are not distracted from their daily activities. The collected data represent time frames when developers work alone at their machines and when they do Pair Programming with their colleagues.},
	author = {Corral, Luis and Janes, Andrea and Remencius, Tadas and Strumpflohner, Juri and Vlasenko, Jelena}
}
@proceedings {1453,
	title = {Open Source Migration in Greek Public Sector: A Feasibility Study},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {233-243},
	publisher = {IFIP AICT},
	abstract = {Open Source software has been recently recognized by governments as a viable and cost effective solution. However, transition to open source is not a plug-and-play process but one that requires deep knowledge of open source dynamics and of organization{\textquoteright}s operations, budgetary constraints, capacities, ethics and political agenda. As with any IT transition, there are uncertainties and risks that need to be handled in order to maximize the gains for the organization and for the society through the provided services. In this paper we present a feasibility study conducted in 15 Greek public sector organizations with the aim to discover the value this transition brings to a typical public sector organization.},
	author = {Mavridis, Androklis and Fotakidis, Dimitrios and Ioannis Stamelos}
}
@proceedings {1463,
	title = {Open Source, Open Innovation and Intellectual Property Rights {\textendash} A Lightning Talk},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {298-303},
	publisher = {IFIP AICT,  Springer},
	abstract = {Open innovation projects are fast paced aiming at producing a quick proof of concept of an innovative software product. This need for speedy results makes the use of open source components as a basis for the work appealing. Open source brings with it an inherent risk of license conflicts that may become an issue when aiming to develop an innovative demo into an actual product. In this study, the first results of investigating the knowledge the participants of innovation projects have on intellectual property are presented. The effect this may have on the project results is also discussed.},
	author = {Kilamo, Terhi and Hammouda, Imed and Kairamo, Ville and Rasanen, Petri and Saarinen, Jukka P.}
}
@proceedings {1460,
	title = {Open Source Prediction Methods: A Systematic Literature Review},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {280-285},
	publisher = {IFIP AICT,  Springer},
	abstract = {For the adoption of Open Source Software (OSS) components, knowledge of the project development and associated risks with their use is needed. That, in turn, calls for reliable prediction models to support preventive maintenance and building quality software. In this paper, we perform a systematic literature review on the state-of-the- art on predicting OSS projects considering both code and community dimension. We also distill future direction for research in this field.},
	keywords = {Prediction Success, Systematic literature review},
	author = {Syeed, M.M. Mahbubul and Kilamo, Terhi and Hammouda, Imed and Syst{\"a}, Tarja}
}
@proceedings {1455,
	title = {Open-Source Technologies Realizing Social Networks: A Multiple Descriptive Case-Study},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {250-255},
	publisher = {IFIP AICT,  Springer},
	abstract = {This article aims at describing the role of the open-source software phenomenon within high-tech corporations providing social networks and applications. By taking a multiple case study approach, We address what are the open-source software technological components embedded by leading social networking players, and a rich description on how those players collaborate with the open-source community. Our findings, based on a population of three commercial providers of social networks a suggest that open-source plays an important role on the technological development of their social networking platforms. An open-source technological stack for realizing social networks is proposed and several managerial issues dealing with collaboration with open-source communities are explored.},
	keywords = {entrepreneurship, facebook, netlog, social networks, spotify},
	author = {Teixeira, Jose}
}
@proceedings {1464,
	title = {OSS Adoption in South Africa: Applying the TOE Model to a Case Study},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {304-309},
	publisher = {IFIP AICT,  Springer},
	abstract = {This paper presents a case study on the factors that influence the initial adoption of Open Source Software (OSS) in a large South African organization when implementing an OSS PBX platform. The theoretical foundation for this research draws on a number of academic frameworks and models, thus not only providing a practical illustration but also validating their usefulness in guiding OSS adoption.},
	author = {Van Belle, Jean-Paul and Reed, Mark}
}
@proceedings {1474,
	title = {OSS in 2012: A Long-Term Sustainable Alternative for Corporate IT},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {371-376},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {The current internet leaders (Google, Facebook, etc.) all have OSS in their DNA. Traditional corporations still rely mostly on proprietary software for their mission-critical IT systems. But, situation is changing: as tip of the iceberg, major stock exchanges of the world have announced successful migrations to OSS. Many traditional corporations can now follow the OSS path because this market has clearly matured in many relevant aspects for them. In addition, solutions are here to achieve quick, efficient and secure mutations to OSS which must be undoubtedly considered by CIOs as the technological state of the art for 2012.},
	author = {Durand, Didier and Vuattoux, Jean-Luc and Ditscheid, Pierre-Jean}
}
@proceedings {1447,
	title = {OSS Integration Issues and Community Support: An Integrator Perspective},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {129-143},
	publisher = {IFIP AICT},
	abstract = {The reuse and integration of Open Source Software (OSS) components provided by OSS communities is becoming an economical and strategic need for today{\textquoteright}s organizations. The integration of OSS components provides many benefits, but also risks and challenges. One of the most important risks is the lack of effective and timely OSS community support for dealing with possible integration problems. For gaining an understanding of the common problems that organizations face when integrating OSS components, and the role played by OSS communities, we performed an exploratory study on 25 OSS integration projects from different European organizations. The results show that the main way of reducing integration problems was the use of OSS components from well-established communities; therefore very few integration problems were identified. In most of the cases these problems were successfully solved with the support from the OSS community and/or colleagues. In addition, contrary to the common belief that understanding code from someone else is a hard and undesirable task, some integrators consider OSS code even more understandable than their own code.},
	author = {Ayala, Claudia and Cruzes, Daniela S. and Nguyen, Anh Duc and Conradi, Reidar and Franch, Xavier and Höst, Martin and Ali Babar, Muhammad}
}
@proceedings {1471,
	title = {OSSLI: Architecture Level Management of Open Source Software Legality Concerns},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {356-361},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {This paper presents a tool that addresses the legality concerns of open source at the level of software architecture, early in the development activity. The tool demonstrates the significance of licensing concerns at the architectural level by extending existing modeling tools with support for open source licensing issues.},
	author = {Lokhman, Alexander and Luoto, Antti and Abdul-Rahman, Salum and Hammouda, Imed}
}
@proceedings {1459,
	title = {Perspectives on Code Forking and Sustainability in Open Source Software},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {274-279},
	publisher = {IFIP AICT,  Springer},
	abstract = {The ability to create high-quality software artifacts that are usable over time is one of the essential requirements of the software business. In such a setting, open source software offers excellent opportunities for sustainability. In particular, safeguarding mechanisms against planned obsolescence by any single actor are built into the definition of open source. The most powerful of these mechanisms is the ability to fork the project. In this paper we argue that the possibility to fork serves as the invisible hand of sustainability that ensures that code remains open and that the code that best serves the community lives on. Furthermore, the mere option to fork provides a mechanism for safeguarding against despotic decisions by the project lead, who is thus guided in their actions to consider the best interest of the community.},
	author = {Nyman, Linus and Mikkonen, Tommi and Juho Lindman and Fougère, Martin}
}
@proceedings {1456,
	title = {A Qualitative Method for Mining Open Source Software Repositories},
	volume = {378},
	year = {2012},
	note = {The method proposed by this study employs content analysis Krippendorff [10], a classification technique that is frequently applied to interview and focus group data. The objective of content analysis is to ask quantitative questions about qualitative data. The approach is similar to the grounded theory method, but differs from grounded theory in that the results are quantitative rather than qualitative: content analysis produces results such as, {\textquotedblleft}49\% of messages submitted to project mailing lists were sent by core developers.{\textquotedblright}},
	month = {09/2012},
	pages = {256-261},
	publisher = {IFIP AICT,  Springer},
	abstract = {The volume of data archived in open source software project repositories makes automated, quantitative techniques attractive for extracting and analyzing information from these archives. However, many kinds of archival data include blocks of natural language text that are difficult to analyze automatically.

This paper introduces a qualitative analysis method that is transparent and repeatable, leads to objective findings when dealing with qualitative data, and is efficient enough to be applied to large archives.

The method was applied in a case study of developer and user forum discussions of an open source electronic medical record project. The study demonstrates that the qualitative repository mining method can be employed to derive useful results quickly yet accurately. These results would not be possible using a strictly automated approach.},
	keywords = {content analysis, Electronic Medical Record, Qualitative Research},
	author = {Noll, John and Seichter, Dominik and Beecham, Sarah}
}
@article {1484,
	title = {Similarities, challenges and opportunities of Wikipedia content and open source projects},
	journal = {Journal of Software: Evolution and Process},
	year = {2012},
	note = {The Sourceforge repository was chosen as the largest and most representative OSS repository. In order to extract a sample from it, the flossmole.org database [20] was downloaded, containing the basic information of all the Sourceforge projects. The latest available dump of such data, at the time of the extraction (April 2009) contained 126,142 projects. From this database, three filters were applied: one based on the given status of the projects; one classifying the activity of the project, and imposed by the SourceForge site ({\textquotedblleft}active{\textquotedblright} and {\textquotedblleft}inactive{\textquotedblright}); and one relative to the specific topic (or application domain) that each project is developed for.},
	month = {08/2012},
	pages = {n/a - n/a},
	abstract = {Several years of research and evidence have demonstrated that open source software portals often contain a large amount of software projects that simply do not evolve, developed by relatively small communities, struggling to attract a sustained number of contributors. These portals have started to increasingly act as a storage for abandoned projects, and researchers and practitioners should try and point out how to take advantage of such content. Similarly, other online content portals (like Wikipedia) could be harvested for valuable content. In this paper we argue that, even with differences in the requested expertise, many projects reliant on content and contributions by users undergo a similar evolution, and follow similar patterns: when a project fails to attract contributors, it appears to be not evolving, or abandoned. Far from a negative finding, even those projects could provide valuable content that should be harvested and identified based on common characteristics: by using the attributes of {\textquoteleft}usefulness{\textquoteright} and {\textquoteleft}modularity{\textquoteright} we isolate valuable content in both Wikipedia pages and open source software projects. },
	keywords = {flossmole},
	doi = {10.1002/smr.1570},
	url = {https://www.researchgate.net/publication/259684110_Similarities_challenges_and_opportunities_of_Wikipedia_content_and_open_source_projects},
	attachments = {https://flosshub.org/sites/flosshub.org/files/jsep2012.pdf},
	author = {Capiluppi, Andrea}
}
@conference {1523,
	title = {Social coding in GitHub},
	booktitle = {Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work - CSCW {\textquoteright}12},
	year = {2012},
	pages = {1277},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Seattle, Washington, USA},
	abstract = {
Social applications on the web let users track and follow the activities of a large number of others regardless of location or affiliation. There is a potential for this transparency to radically improve collaboration and learning in complex knowledge-based activities. Based on a series of in-depth interviews with central and peripheral GitHub users, we examined the value of transparency for large-scale distributed collaborations and communities of practice. We find that people make a surprisingly rich set of social inferences from the networked activity information in GitHub, such as inferring someone else{\textquoteright}s technical goals and vision when they edit code, or guessing which of several similar projects has the best chance of thriving in the long term. Users combine these inferences into effective strategies for coordinating work, advancing technical skills and managing their reputation.
},
	keywords = {github},
	isbn = {9781450310864},
	doi = {10.1145/2145204.2145396},
	url = {http://www.cs.cmu.edu/afs/cs/Web/People/xia/resources/Documents/cscw2012_Github-paper-FinalVersion-1.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cscw2012_Github-paper-FinalVersion-1.pdf},
	author = {Laura Dabbish and Colleen Stuart and Jason Tsay and Herbsleb, Jim}
}
@article {springerlink:10.1007/s10664-012-9199-7,
	title = {Software Bertillonage},
	journal = {Empirical Software Engineering},
	year = {2012},
	note = {10.1007/s10664-012-9199-7},
	pages = {1-43},
	publisher = {Springer Netherlands},
	abstract = {Deployed software systems are typically composed of many pieces, not all of which may have been created by the main development team. Often, the provenance of included components{\textemdash}such as external libraries or cloned source code{\textemdash}is not clearly stated, and this uncertainty can introduce technical and ethical concerns that make it difficult for system owners and other stakeholders to manage their software assets. In this work, we motivate the need for the recovery of the provenance of software entities by a broad set of techniques that could include signature matching, source code fact extraction, software clone detection, call flow graph matching, string matching, historical analyses, and other techniques. We liken our provenance goals to that of Bertillonage, a simple and approximate forensic analysis technique based on bio-metrics that was developed in 19th century France before the advent of fingerprints. As an example, we have developed a fast, simple, and approximate technique called anchored signature matching for identifying the source origin of binary libraries within a given Java application. This technique involves a type of structured signature matching performed against a database of candidates drawn from the Maven2 repository, a 275 GB collection of open source Java libraries. To show the approach is both valid and effective, we conducted an empirical study on 945 jars from the Debian GNU/Linux distribution, as well as an industrial case study on 81 jars from an e-commerce application. },
	issn = {1382-3256},
	doi = {10.1007/s10664-012-9199-7},
	url = {http://dx.doi.org/10.1007/s10664-012-9199-7},
	author = {Davies, Julius and German, Daniel and Michael Godfrey and Hindle, Abram}
}
@mastersthesis {1438,
	title = {Software Libre y abierto: comunidades y redes de producción digital de bienes comunes},
	year = {2012},
	pages = {269 pages},
	school = {Universidad Nacional Autónoma de México},
	address = {Ciudad de México, México},
	abstract = {This thesis is about a collective form of production that have expanded and strengthen in the global high technology market. It is about FLOSS production. 

The study takes on account that technnologies are not neutral, they emerge as strategies and mechanisms of politics and economic interests. 

Although, FLOSS production is inserted in the capitalist context, the collective work of the communities and networks that produce it is based on ideas about freedom and solidarity.

The types of rules and organization of labour inside of this communities have develop a kind of product that it is well categorized as part of the new commons.

The conclusions at the end of this work pretend to offer a clear approach to the FLOSS production networks dynamics inside the virtual infrastructure. Specifically, it offers an approach of the interaction and forms of cooperation, as well of the individual and collective schemas that motivates the cooperation action of the individuals.},
	keywords = {bienes comunes, commons, comunidades virtuales, FLOSS, flossmole, hackers, redes virtuales, repositories, repositorios, Software libre y abierto, virtual communities, virtual networks},
	url = {http://132.248.9.195/ptd2012/agosto/406008604/Index.html},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Tesis.pdf},
	author = {Tania E. Turner Sen}
}
@conference {1628,
	title = {Software licenses, coverage, and subsumption},
	booktitle = {2012 Fifth International Workshop on Requirements Engineering and Law (RELAW)2012 Fifth IEEE International Workshop on Requirements Engineering and Law (RELAW)},
	year = {2012},
	pages = {17 - 24},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Chicago, IL, USA},
	abstract = {Software licensing issues for a system design, instantiation, or configuration are often complex and difficult to evaluate, and mistakes can be costly. Automated assistance requires a formal representation of the significant features of the software licenses involved. We present results from an analysis directed toward a formal representation capable of covering an entire license. The key to such a representation is to identify the license{\textquoteright}s actions, and relate them to the actions for exclusive rights defined in law and to the actions defined in other licenses. Parameterizing each action by the object(s) acted on, the instrumental entities through which the action is performed, and similar contextual variables enables a subsumption relation among the actions. The resulting formalism is lightweight, flexible enough to support the scope of legal interpretations, and extensible to a wide range of software licenses. We discuss the application of our approach to the Lesser General Public License (LGPL) version 2.1.},
	isbn = {978-1-4673-4381-7},
	doi = {10.1109/RELAW.2012.6347800},
	author = {Alspaugh, Thomas A. and Walt Scacchi and Kawai, Rihoko}
}
@proceedings {1442,
	title = {Step-by-Step Strategies and Case Studies for Embedded Software Companies to Adapt to the FOSS Ecosystem},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {48-60},
	abstract = {Due to the continuous expansion of the FOSS ecosystem and the introduction of high-quality FOSS, FOSS is increasingly used in consumer electronics (CE) such as smartphones, televisions, and cameras. As a result, manufacturers of CE products have developed a close relationship with the FOSS ecosystem. For CE product manufacturers, efficient adaptation to the FOSS ecosystem has become an essential component in their business operations. This paper will divide the activities of CE product manufacturers within the FOSS ecosystem into the following four levels: identification, adoption, compliance, and contribution. It will examine the main activities and obstacles that arise in each level. The paper will also present instances where companies have succeeded in overcoming these obstacles.},
	keywords = {embedded software, FOSS ecosystem},
	author = {Kim, Suhyun and Yoo, Jaehyun and Lee, Myunghwa}
}
@proceedings {1468,
	title = {A Study on OSS Marketing and Communication Strategies},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {338-343},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {The goal of every open source project is to gain as many satisfied users as possible. To this end, open source software producers should focus on both product development and communication. Currently, most open source projects are mainly concerned with developing code using the most appealing technologies and introducing fancy features. On the contrary, open source software producers seem to lack good communication strategies. In this paper we describe the communication strategies adopted by three successful companies that are active in open source software development. The goal of the paper is to provide some hints that could help other open source software producers identify communication strategies that are effective in promoting their products on the market.},
	author = {del Bianco, Vieri and Lavazza, Luigi and Lenarduzzi, Valentina and Morasca, Sandro and Taibi, Davide and Tosi, Davide}
}
@article {1396,
	title = {Studying the impact of social interactions on software quality},
	journal = {Empirical Software Engineering},
	year = {2012},
	note = {bug databases},
	abstract = {Correcting software defects accounts for a significant amount of resources in a software project. To make best use of testing efforts, researchers have studied statistical models to predict in which parts of a software system future defects are likely to occur. By studying the mathematical relations between predictor variables used in these models, researchers can form an increased understanding of the important connections between development activities and software quality. Predictor variables used in past top-performing models are largely based on source code-oriented metrics, such as lines of code or number of changes. However, source code is the end product of numerous interlaced and collaborative activities carried out by developers. Traces of such activities can be found in the various repositories used to manage development efforts. In this paper, we develop statistical models to study the impact of social interactions in a software project on software quality. These models use predictor variables based on social information mined from the issue tracking and version control repositories of two large open-source software projects. The results of our case studies demonstrate the impact of metrics from four different dimensions of social interaction on post-release defects. Our findings show that statistical models based on social information have a similar degree of explanatory power as traditional models. Furthermore, our results demonstrate that social information does not substitute, but rather augments traditional source code-based metrics used in defect prediction models.},
	keywords = {bug tracker, eclipse, Firefox, Human Factors, measurement, metrics, software evolution, Software quality assurance},
	issn = {1573-7616},
	doi = {10.1007/s10664-012-9205-0},
	author = {Bettenburg, Nicolas and Hassan, Ahmed E.}
}
@article {1707,
	title = {Time-Based Release Management in Free and Open Source (FOSS) Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {4},
	year = {2012},
	month = {31/2012},
	pages = {1 - 19},
	abstract = {As the Free and Open Source (FOSS) concept has
matured, its commercial significance has also
increased, and issues such as quality and
sustainability have moved to the fore. In this study,
we focus on time-based release management in large
volunteer FOSS projects, and reveal how it addresses
quality and sustainability issues. We discuss the
differences between release management in the
traditional software context and contrast it with
FOSS settings. Based on detailed case studies of a
number of prominent FOSS projects, we describe the
move to time-based release management and identify
the factors and criteria necessary for a successful
transition. We also consider the implications for
software development more generally in the current
dynamic Internet-enabled environment.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2012010101},
	url = {http://lero.ie/sites/default/files/Lero-TR-2011-04.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Lero-TR-2011-04.pdf},
	author = {Martin Michlmayr and Fitzgerald, Brian}
}
@proceedings {1452,
	title = {Two Evolution Indicators for FOSS Projects},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {216-232},
	publisher = {IFIP AICT},
	abstract = {In this paper we introduce two project evolution indicators. One is showing an increase of downloads of the project and therefore a growing interest of users in the results of the project. The second indica- tor is predicting the future evolution of the project with the submission of new revisions to the concurrent versioning system. Both indicators can provide evidence of the sustainability of a software project. We used the General Linear Model method to statistically formulate the two linear equations that can be used to predict the two indicators. The predicting equations were build by using two stratified data samples one of 760 projects and the second of 880 projects extracted from the SourceForge repository. The six metrics included into the final version of the two models were extracted from a set of thirty project and product metrics as: the number of downloads, the number of developers, etc. We have validated the discriminant and the concurrent validity of the two models by using different statistical tests as the goodness-of-fit and we have used the two models to predict the indicators on two hold-out validation samples. The model predicting the increment of downloads was correct in 75 percent of the cases, the model predicting the submission of new revisions was correct in 93 percent of the cases.},
	keywords = {metrics, sourceforge},
	author = {Petrinja, Etiel and Succi, Giancarlo}
}
@proceedings {1473,
	title = {Two Modes of Product Development: Head-Oriented vs. Release-Oriented},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {368-370},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {In this paper, the concept of two different modes for product development process is proposed. One is {\textquotedblleft}release-oriented{\textquotedblright} product development, which is a fairly common way to develop various products up to now. The other is {\textquotedblleft}head-oriented{\textquotedblright} product development, which is recently observed especially in the field of software/content development. The distinguishing difference and possible merits and demerits of two modes are scrutinized.},
	author = {Hatta, Masayuki}
}
@conference {bettenburg:csmr2012,
	title = {Using Code Search to Link Code Fragments in Discussions and Source Code},
	booktitle = {CSMR {\textquoteright}12: Proceedings of the 16th European Conference on Software Maintenance and Reengineering},
	year = {2012},
	pages = {319-329},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {When discussing software, practitioners often reference parts of the project{\textquoteright}s source code. Such references have different motivations, such as mentoring and guiding less experienced developers, pointing out code that needs changes, or proposing possible strategies for the implementation of future changes. The fact that particular parts of a source code are being discussed makes these parts of the software special. Knowing which code is being talked about the most can not only help practitioners to guide important software engineering and maintenance activities, but also act as a high-level documentation of development activities for managers. In this paper, we use clone-detection as specific instance of a code search based approach for establishing links between code fragments that are discussed by developers and the actual source code of a project. Through a case study on the Eclipse project we explore the traceability links established through this approach, both quantitatively and qualitatively, and compare fuzzy code search based traceability linking to classical approaches, in particular change log analysis and information retrieval. We demonstrate a sample application of code search based traceability links by visualizing those parts of the project that are most discussed in issue reports with a Treemap visualization. The results of our case study show that the traceability links established through fuzzy code search-based traceability linking are conceptually different than classical approaches based on change log analysis or information retrieval.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Bettenburg_2012_CSMR.pdf},
	author = {Bettenburg, Nicolas and Stephen W. Thomas and Hassan, Ahmed E.}
}
@proceedings {1449,
	title = {Using Multiple Case Studies to Analyse Open Source Software Business Sustainability in Sub-Saharan Africa},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {160-177},
	publisher = {IFIP AICT},
	abstract = {Amidst the debate about what sort of technology is appropriate for achieving sustainable development, Free and Open Source Software (FOSS) offers some solutions to today{\textquoteright}s technology problems for many developing countries. However, there is a paucity of empirical evidence to help us understand the potentials FOSS technologies have for small businesses in Sub-Saharan Africa. This research utilizes nine case studies data from seven African countries to find out how entrepreneurs are leveraging FOSS to help them create sustainable business based on openness. The findings show increasing awareness of the business potential of FOSS, and a business model incorporating both FOSS and proprietary software is needed to run a sustainable IT business in these countries. However, the lack of skilled FOSS developer base, the absence of appropriate policies, and poor payment habits by clients are just some of the factors affecting businesses. Other problems encountered, possible solutions to those problems and lessons to be learnt from each case study are also discussed. The research offers entrepreneurs, ICT practitioners, and policy makers the platform to understand the Why and How FOSS technologies are impacting the traditional way of doing business in Sub-Saharan Africa.},
	author = {Sowe, Sulayman K. and McNaughton, Maurice}
}
@article {1681,
	title = {Using Pig as a data preparation language for large-scale mining software repositories studies: An experience report},
	journal = {Journal of Systems and Software},
	volume = {85},
	year = {2012},
	note = {"For example, FLOSSMole (Howison et al., 2006) is a public relational database that contains data extracted from a large number of software repositories. Many researchers use FLOSSMole as a platform. For example, Herraiz et al. (2008) used data in FLOSSMole (Howison et al., 2006) to perform analysis to illustrate that most of the software projects are governed by short term goals rather than long term goals."},
	month = {10/2012},
	pages = {2195 - 2204},
	abstract = {The Mining Software Repositories (MSR) field analyzes software repository data to uncover knowledge and assist development of ever growing, complex systems. However, existing approaches and platforms for MSR analysis face many challenges when performing large-scale MSR studies. Such approaches and platforms rarely scale easily out of the box. Instead, they often require custom scaling tricks and designs that are costly to maintain and that are not reusable for other types of analysis. We believe that the web community has faced many of these software engineering scaling challenges before, as web analyses have to cope with the enormous growth of web data. In this paper, we report on our experience in using a web-scale platform (i.e., Pig) as a data preparation language to aid large-scale MSR studies. Through three case studies, we carefully validate the use of this web platform to prepare (i.e., Extract, Transform, and Load, ETL) data for further analysis. Despite several limitations, we still encourage MSR researchers to leverage Pig in their large-scale studies because of Pig{\textquoteright}s scalability and flexibility. Our experience report will help other researchers who want to scale their analyses.},
	keywords = {flossmole cited},
	issn = {01641212},
	doi = {10.1016/j.jss.2011.07.034},
	url = {http://www.sciencedirect.com/science/article/pii/S0164121211002007},
	author = {Weiyi Shang and Adams, Bram and Hassan, Ahmed E.}
}
@conference {bird2012www,
	title = {Who? What? Where? Examining Distributed Development in Two Large Open Source Projects},
	booktitle = {Proceedings of the Working Conference on Mining Software Repositories},
	year = {2012},
	abstract = {To date, a large body of knowledge has been built up around understanding open source software development. However, there is limited research on examining levels of geographic and organizational distribution within open source software projects, despite many studies examining these same aspects in commercial contexts. We set out to fill this gap in OSS knowledge by manually collecting data for two large, mature, successful projects in an effort to assess how distributed both geographically and organizationally. Both Firefox and Eclipse have been the subject of many studies and are ubiquitous in the areas of software development and internet usage respectively. Further, both receive substantial development contributions from many companies. As such, both are worthy of study in order to understand the development processes that they use, how distributed the projects are, and what, if any, relationship distribution has with quality. To this end, we identified the top contributors that made 95\% of the changes over multiple major releases of Firefox and Eclipse and determined their geographic locations and organizational affiliations. We found that Firefox is very geographically distributed with over a third of its components receiving major contributions from developers on different continents, and that components that are highly distributed have no more defects than those that are not. In contrast, Eclipse is directed and developed largely by one company; with IBM making 96\% of the total commits (49\% coming from one lab in Ottawa, Canada). We further examined the distribution in each project{\textquoteright}s constituent subsystems and report the relationship of pre- and post-release defects with geographic and organizational factors.},
	keywords = {eclipse, Firefox},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2012www.pdf},
	author = {Christian Bird and Nachiappan Nagappan}
}
@conference {1319,
	title = {Who Will Remain? An Evaluation of Actual Person-Job and Person-Team Fit to Predict Developer Retention in FLOSS Projects},
	booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences},
	year = {2012},
	month = {01/2012},
	pages = {3446-3455},
	abstract = {Many businesses and private households rely on Free Libre Open Source Software (FLOSS). Due to a lack of sustained contributors, however, most FLOSS projects do not survive. The early identification of developers who are likely to remain is thus an eminent challenge for the management of FLOSS initiatives. Previous research has shown that individuals{\textquoteright} subjective assessment is often inaccurate emphasizing the need to objectively evaluate retention behavior. Consistent with the concepts Person-Job (P-J) and Person-Team (P-T) fit from the traditional recruitment literature, we derive objective measures to predict developer retention in FLOSS projects. In an analysis of the contribution behavior of former Google Summer of Code (GSoC) students we reveal that the level of development experience and conversational knowledge is strongly associated with retention. Surprisingly, our analysis reveals that students with abilities that are underrepresented in the project and students with a higher academic education do not remain considerably longer.},
	keywords = {email, email archives, google summer of code, kde, mailing list, students},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2012.644},
	attachments = {https://flosshub.org/sites/flosshub.org/files/45.pdf},
	author = {Schilling, A. and Laumer, S. and Weitzel, T.}
}
@article {1381,
	title = {Adopting Free/Libre/Open Source Software Practices, Techniques and Methods for Industrial Use},
	journal = {Journal of the Association for Information Systems},
	volume = {12},
	number = {1},
	year = {2011},
	abstract = {Today{\textquoteright}s software companies face the challenges of highly distributed development projects and constantly changing requirements. This paper proposes the adoption of relevant Free/Libre/Open Source Software (FLOSS) practices in order to improve software development projects in industry. Many FLOSS projects have proven to be very successful, producing high quality products with steady and frequent releases. This study aims to identify FLOSS practices that can be adapted for the corporate environment. To achieve this goal, a framework to compare FLOSS and industrial development methodologies was created. Three successful FLOSS projects were selected as study targets (the Linux Kernel, the FreeBSD operating system, and the JBoss application server), as well as two projects from Ericsson, a large telecommunications company. Based on an analysis of these projects, FLOSS best practices were tailored to fit industrial development environments. The final results consisted of a set of key adoption opportunities that aimed to improve software quality and overall development productivity by importing best practices from the FLOSS environment. The adoption opportunities were then validated at three large corporations.},
	keywords = {freebsd, jboss, linux, linux kernel},
	url = {http://aisel.aisnet.org/jais/vol12/iss1/1},
	author = {Torkar, Richard and Minoves, Pau and Garrig{\'o}s, Janina}
}
@proceedings {1285,
	title = {Adoption of OSS Development Practices by the Software Industry: A Survey},
	year = {2011},
	month = {10/2011},
	pages = {233-243},
	publisher = {Springer},
	abstract = {The paper presents a survey of aspects related to the adoption of Open Source Software by the software industry. The aim of this study was to collect data related to practices and elements in the development process of companies that influence the trust in the quality of the product by potential adopters. The work is part of the research done inside the QualiPSo project and was carried out using a qualitative study based on a structured questionnaire focused on perceptions of experts and development practices used by companies involved in the Open Source Software industry. The results of the survey confirm intuitive concerns related to the adoption of Open Source Software as: the selection of the license, the quality issues addressed, and the development process tasks inside Open Source Software projects. The study uncovered specific aspects related to trust and trustworthiness of the Open Source Software development process that we did not find in previous studies as: the standards implemented by the OSS project, the project{\textquoteright}s roadmap is respected, and the communication channels that are available.},
	keywords = {qualipso, Survey},
	author = {Petrinja, Etiel and Sillitti, Alberto and Succi, Giancarlo}
}
@proceedings {1288,
	title = {An Analysis of Author Contribution Patterns in Eclipse Foundation Project Source Code},
	year = {2011},
	note = {"We conducted an observational study on existing Eclipse projects by extracting author attribution data for Java source code files from git repositories."

"Specifically, we consider entropy of source code by counting the number of lines attributed to each author."},
	month = {10/2011},
	pages = {269-281},
	publisher = {Springer},
	abstract = {Collaborative development is a key tenet of open source software, but if not properly understood and managed, it can become a liability. We examine author contribution data for the newest revision of 251,633 Java source files in 592 Eclipse projects. We use this observational data to analyze collaboration patterns within files, and to explore relationships between file size, author count, and code authorship. We calculate author entropy to characterize the contributions of multiple authors to a given file, with an eye toward understanding the degree of collaboration and the most common interaction patterns.},
	keywords = {COLLABORATION, contribution, eclipse, entropy, java},
	author = {Taylor, Quinn C. and Krein, Jonathan L. and MacLean, Alexander C. and Knutson, Charles D.}
}
@conference {1314,
	title = {Apples vs. oranges?},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"In this MSR challenge report, we compare the source code of two in- dustrial grade Integrated Development Environments (IDE): Netbeans, developed by Oracle Corporation, and Eclipse, developed by the Eclipse Foundation. In the same spirit as [1], our goal is not to identify how similar or different they are, but to identify differences that, if not taken into consideration, might result in biased, and potentially erroneous conclusions."},
	month = {05/2011},
	pages = {246-249},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {We attempt to compare the source code of two Java IDE systems: Netbeans and Eclipse. The result of this experiment shows that many factors, if ignored, could risk a bias in the results, and we posit various observations that should be taken into consideration to minimize such risk.

},
	keywords = {eclipse, netbeans, source code},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985483},
	author = {Davies, Julius and Daniel M. German}
}
@proceedings {1291,
	title = {Applying Open Source Practices and Principles in Open Innovation: The Case of the Demola Platform},
	year = {2011},
	month = {10/2011},
	pages = {307-311},
	publisher = {Springer},
	abstract = {In numerous fields, businesses have to rely on rapid development and release cycles. Variant new ideas and concepts can emerge through open innovation as the participants are not limited to the company scope. This makes open innovation an increasingly appealing option for the industry. One such open innovation platform, Demola, allows university students to work on real life industrial cases of their own interest. We have identified similarities with its way of operation to open source software development and find that it offers a viable motivational, organizational and collaborative solution to open innovation.},
	author = {Kilamo, Terhi and Hammouda, Imed and Kairamo, Ville and Rasanen, Petri}
}
@article {1324,
	title = {Are Developers Fixing Their Own Bugs?},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	note = {"The analysis is focused at the level of lines of code and it uses the information stored in the source code management system"},
	pages = {23 - 42},
	abstract = {The process of fixing software bugs plays a key role in the maintenance activities of a software project. Ideally, code ownership and responsibility should be enforced among developers working on the same artifacts, so that those introducing buggy code could also contribute to its fix. However, especially in FLOSS projects, this mechanism is not clearly understood: in particular, it is not known whether those contributors fixing a bug are the same introducing and seeding it in the first place. This paper analyzes the comm-central FLOSS project, which hosts part of the Thunderbird, SeaMonkey, Lightning extensions and Sunbird projects from the Mozilla community. The analysis is focused at the level of lines of code and it uses the information stored in the source code management system. The results of this study show that in 80\% of the cases, the bug-fixing activity involves source code modified by at most two developers. It also emerges that the developers fixing the bug are only responsible for 3.5\% of the previous modifications to the lines affected; this implies that the other developers making changes to those lines could have made that fix. In most of the cases the bug fixing process in comm-central is not carried out by the same developers than those who seeded the buggy code.},
	keywords = {bug fixing, developers, loc, scm},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011040102},
	author = {Izquierdo-Cortazar, Daniel and Capiluppi, Andrea and Jesus M. Gonzalez-Barahona}
}
@proceedings {1295,
	title = {Aspects of an Open Source Software Sustainable Life Cycle},
	year = {2011},
	month = {10/2011},
	pages = {325-329},
	publisher = {Springer},
	abstract = {In this paper we present a literature overview about OSS sustainability, considering not only financial resources, but also community growth, source code and tools management. Based on these aspects, we define an OSS life cycle that may contribute to OSS projects sustainability.},
	keywords = {Financial Resources, OSS Communities, OSS Sustainability, software maintenance},
	author = {Arantes, Flavia Linhalis and Freire, Fernanda Maria Pereira}
}
@proceedings {1278,
	title = {Building Knowledge in Open Source Software Research in Six Years of Conferences},
	year = {2011},
	note = {RQ1. Is there any social network underlying the research production at the OSS conference series?
RQ2. What are the major streams of research proposed at the OSS conference series?},
	month = {10/2011},
	pages = {123-141},
	publisher = {Springer},
	abstract = {Since its origins, the diffusion of the OSS phenomenon and the information about it has been entrusted to the Internet and its virtual communities of developers. This public mass of data has attracted the interest of researchers and practitioners aiming at formalizing it into a body of knowledge. To this aim, in 2005, a new series of conferences on OSS started to collect and convey OSS knowledge to the research and industrial community. Our work mines articles of the OSS conference series to understand the process of knowledge grounding and the community surrounding it. As such, we propose a semi-automated approach for a systematic mapping study on these articles. We automatically build a map of cross-citations among all the papers of the conferences and then we manually inspect the resulting clusters to identify knowledge building blocks and their mutual relationships. We found that industry-related, quality assurance, and empirical studies often originate or maintain new streams of research.},
	keywords = {Cross-citations, flossmole cited, graph, literature review, network, research, Systematic Mapping Study},
	author = {Mulazzini, Fabio and Rossi, Bruno and Russo, Barbara and Steff, Maximilian}
}
@proceedings {1289,
	title = {Cliff Walls: An Analysis of Monolithic Commits Using Latent Dirichlet Allocation},
	year = {2011},
	note = {"Our data set consists of the version control logs of almost 10,000 projects from SourceForge, acquired in late 2006"},
	month = {10/2011},
	pages = {282-298},
	publisher = {Springer},
	abstract = {Artifact-based research provides a mechanism whereby researchers may study the creation of software yet avoid many of the difficulties of direct observation and experimentation. However, there are still many challenges that can affect the quality of artifact-based studies, especially those studies examining software evolution. Large commits, which we refer to as {\textquotedblleft}Cliff Walls,{\textquotedblright} are one significant threat to studies of software evolution because they do not appear to represent incremental development. We used Latent Dirichlet Allocation to extract topics from over 2 million commit log messages, taken from 10,000 SourceForge projects. The topics generated through this method were then analyzed to determine the causes of over 9,000 of the largest commits. We found that branch merges, code imports, and auto-generated documentation were significant causes of large commits. We also found that corrective maintenance tasks, such as bug fixes, did not play a significant role in the creation of large commits.},
	keywords = {artifacts, commit, cvs, LDA, lines of code, log files, scm, sloc, sourceforge, version control},
	author = {Pratt, Landon J. and MacLean, Alexander C. and Knutson, Charles D. and Ringger, Eric K.}
}
@article {1383,
	title = {A comparative study of challenges in integrating Open Source Software and Inner Source Software},
	journal = {Information and Software Technology},
	volume = {53},
	year = {2011},
	month = {12/2011},
	pages = {1319 - 1336},
	abstract = {Context

Several large software-developing organizations have adopted Open Source Software development (OSSD) practices to develop in-house components that are subsequently integrated into products. This phenomenon is also known as {\textquotedblleft}Inner Source{\textquotedblright}. While there have been several reports of successful cases of this phenomenon, little is known about the challenges that practitioners face when integrating software that is developed in such a setting.
Objective

The objective of this study was to shed light on challenges related to building products with components that have been developed within an Inner Source development environment.
Method

Following an initial systematic literature review to generate seed category data constructs, we performed an in-depth exploratory case study in an organization that has a significant track record in the implementation of Inner Source. Data was gathered through semi-structured interviews with participants from a range of divisions across the organization. Interviews were transcribed and analyzed using qualitative data analysis techniques.
Results

We have identified a number of challenges and approaches to address them, and compared the findings to challenges related to development with OSS products reported in the literature. We found that many challenges identified in the case study could be mapped to challenges related to integration of OSS.
Conclusion

The results provide important insights into common challenges of developing with OSS and Inner Source and may help organizations to understand how to improve their software development practices by adopting certain OSSD practices. The findings also identify the areas that need further research.
Highlights

► We performed a case study that has adopted Open Source development practices. ► We studied the challenges encountered and approaches taken by the organization. ► We performed a systematic review to identify challenges related to Open Source. ► We compared the findings from the review to the findings from the case study. ► Most identified challenges could be mapped to the findings from the literature.},
	keywords = {Open Source Software;     Inner Source;     Software development;     Challenges;     Case study;     Empirical studies},
	issn = {09505849},
	doi = {10.1016/j.infsof.2011.06.007},
	url = {http://www.sciencedirect.com/science/article/pii/S095058491100142X},
	author = {Stol, Klaas-Jan and Ali Babar, Muhammad and Avgeriou, Paris and Fitzgerald, Brian}
}
@proceedings {1273,
	title = {Developing Architectural Documentation for the Hadoop Distributed File System},
	year = {2011},
	month = {10/2011},
	pages = {50-61},
	publisher = {Springer},
	abstract = {Many open source projects are lacking architectural documentation that describes the major pieces of the system, how they are structured, and how they interact. We have produced architectural documentation for the Hadoop Distributed File System (HDFS), a major open source project. This paper describes our process and experiences in developing this documentation. We illustrate the documentation we have produced and how it differs from existing documentation by describing the redundancy mechanisms used in HDFS for reliability.},
	author = {Bass, Len and Kazman, Rick and Ozkaya, Ipek}
}
@conference {1313,
	title = {Do comments explain codes adequately?},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {242-245},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Comment lines in the software source code include descriptions of codes, usage of codes, copyrights, unused codes, comments, and so on. It is required for comments to explain the content of written code adequately, since the wrong description in the comment may causes further bug and confusion in maintenance.

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

Our main findings include: (1) commits submitted between midnight and 4 AM (referred to as late-night commits) are significantly buggier and commits between 7 AM and noon are less buggy, implying that developers may want to double-check their own latenight commits; (2) daily-committing developers produce less-buggy commits, indicating that we may want to promote the practice of daily-committing developers reviewing other developers{\textquoteright} commits; and (3) the bugginess of commits versus day-of-week varies for different software projects.},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985464},
	author = {Tan, Lin and Lam, Patrick and Eyolfson, Jon}
}
@article {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 {1321,
	title = {Factors Affecting the Development of Absorptive Capacity in the Adoption of Open Source Software},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {17 - 38},
	abstract = {Previous research has shown that the knowledge that is available to an organization is an important factor influencing the adoption of open source software (OSS). Hence, it is important that organizations develop their absorptive capacity in order to successfully adopt OSS. Absorptive capacity refers to the ability of an organization to acquire, assimilate, and exploit new knowledge. However, no study has specifically investigated how organizations can develop their absorptive capacity by acquiring knowledge about OSS. This paper addresses this gap in research by investigating the organizational knowledge assimilation process within the context of the adoption of OSS. Based on a case study conducted at the Flemish government, a framework that is grounded in literature and that illustrates which contextual factors influence the development of absorptive capacity in the context of the adoption of OSS was developed.},
	keywords = {adoption, government},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011010102},
	author = {Ven, Kris and De Bruyn, Peter}
}
@inbook {1586,
	title = {FLOSS Project Effectiveness Measures},
	booktitle = {Successful OSS Project Design and Implementation},
	year = {2011},
	pages = {149-168},
	publisher = {Gower},
	organization = {Gower},
	abstract = {In this chapter, we develop and illustrate measures of the effectiveness of FLOSS
projects. FLOSS is a broad term used to embrace software that is developed
and released under either a {\textquotedblleft}free software{\textquotedblright} or an {\textquotedblleft}open source{\textquotedblright} license. While
the free software and the open source movements are distinct, both kinds of
licenses allow users to obtain and distribute the software{\textquoteright}s original source
without charge (software is {\textquotedblleft}free as in beer{\textquotedblright}) and to inspect, modify, and
redistribute modifications to the source code. While the open source movement
views these freedoms pragmatically (as a development methodology), the
free software movement emphasizes the meaning of {\textquotedblleft}free as in speech,{\textquotedblright}
which is captured by the French/Spanish libre, and one of their methods of
supporting those freedoms is {\textquotedblleft}copyleft,{\textquotedblright} famously embodied in the General
Public License, meaning that derivative works must be made available under
the same license terms as the original. This chapter focuses on development
practices in distributed work, which are largely shared across the movements.
For example, many (though by no means all) FLOSS developers contribute to
projects as volunteers without working for a common organization or being
paid. We therefore use the acronym FLOSS to refer collectively to free/libre and
open source software. 

It is important to develop measures of effectiveness for FLOSS projects for
at least two reasons. First, having such measures should be useful for FLOSS
project managers in assessing their projects. In some cases, FLOSS projects are
sponsored by third parties, so measures are useful for sponsors to understand
the return on their investment. Second, FLOSS is an increasingly visible and
copied mode of systems development. Millions of users depend on FLOSS
systems such as Linux and on the Internet, which is itself heavily dependent
on FLOSS tools, but as Scacchi (2002a, p. 1) notes, {\textquotedblleft}little is known about how
people in these communities coordinate software development across different
settings, or about what software processes, work practices, and organizational
contexts are necessary to their success.{\textquotedblright} An EU/NSF workshop on priorities for
FLOSS research identified the need both for learning from open source modes
of organization and production that could perhaps be applied to other areas
and for a concerted effort on open source in itself, for itself (Ghosh 2002). But to
be able to learn from teams that are working well, we need to have a definition
of working well.

In the following sections of the chapter, we will first discuss several
measures of project effectiveness, and then the procedure we used to obtain
data with which to operationalize these measures, followed by the details of
the analysis approach. We then present the results of this analysis and discuss
the implications of these results. We then illustrate how these measures can be
used to compare projects as part of a research study. We conclude with some
suggestions for future research. },
	url = {http://library.trec.co.ir/pdfTemp/97805660879501.pdf$\#$page=164},
	author = {Kevin Crowston and Howison, James}
}
@mastersthesis {1415,
	title = {FLOSSSim: Understanding the Free/Libre Open Source Software (FLOSS) Development Process through Agent-Based Modeling},
	year = {2011},
	pages = {323},
	type = {PhD Dissertation},
	address = {Arizona State University, Tempe, AZ, USA},
	abstract = {Free/Libre Open Source Software (FLOSS) is the product of volunteers collaborating to build software in an open, public manner. The large number of FLOSS projects, combined with the data that is inherently archived with this online process, make studying this phenomenon attractive. Some FLOSS projects are very functional, well-known, and successful, such as Linux, the Apache Web Server, and Firefox. However, for every successful FLOSS project there are 100{\textquoteright}s of projects that are unsuccessful. These projects fail to attract sufficient interest from developers and users and become inactive or abandoned before useful functionality is achieved. The goal of this research is to better understand the open source development process and gain insight into why some FLOSS projects succeed while others fail.

This dissertation presents an agent-based model of the FLOSS development process. The model is built around the concept that projects must manage to attract contributions from a limited pool of participants in order to progress. In the model developer and user agents select from a landscape of competing FLOSS projects based on perceived utility. Via the selections that are made and subsequent contributions, some projects are propelled to success while others remain stagnant and inactive.

Findings from a diverse set of empirical studies of FLOSS projects are used to formulate the model, which is then calibrated on empirical data from multiple sources of public FLOSS data. The model is able to reproduce key characteristics observed in the FLOSS domain and is capable of making accurate predictions. The model is used to gain a better understanding of the FLOSS development process, including what it means for FLOSS projects to be successful and what conditions increase the probability of project success. It is shown that FLOSS is a producer-driven process, and project factors that are important for developers selecting projects are identified. In addition, it is shown that projects are sensitive to when core developers make contributions, and the exhibited bandwagon effects mean that some projects will be successful regardless of competing projects. Recommendations for improving software engineering in general based on the positive characteristics of FLOSS are also presented.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FLOSSSim_final.pdf},
	author = {Radtke, Nicholas P.}
}
@proceedings {1297,
	title = {Forge.mil: A Case Study for Utilizing Open Source Methodologies Inside of Government},
	year = {2011},
	month = {10/2011},
	pages = {334-337},
	publisher = {Springer},
	abstract = {In late 2008, DISA (Defense Information Systems Agency), the global IT arm of the US Department of Defense, embarked upon a project to create an internal collaboration and software application lifecycle management system. Beyond simply fielding yet another tool, the Forge.mil effort was designed to fundamentally change the way the DoD developed and acquired software technology and systems. The method of this change was the application of Open Source principles inside of the larger DoD community, including ideas such as meritocracy and code sharing, as well as Agile and collaborative software development. This lightning talk will explain the rationale behind Forge.mil, how it was developed using Open Source principles, and how it continues to influence technology acquisition within the DoD in both practice and policy changes.},
	author = {Martin, Guy and Lippold, Aaron}
}
@proceedings {1283,
	title = {Framing the Conundrum of Total Cost of Ownership of Open Source Software},
	year = {2011},
	month = {10/2011},
	pages = {208-219},
	publisher = {Springer},
	abstract = {This paper reflects the results of phase I of our study on the total cost of ownership (TCO) of open source software adoption. Not only have we found TCO to be an intriguing issue but it is contentious, baffling and each company approaches it in a distinctive manner (and sometimes not at all). In effect it is a conundrum that needs unpacking before it can be explained and understood. Our paper discusses the components of TCO as total cost of ownership and total cost of acquisition (and besides). Using this broad dichotomy and its various components we then analyze our data to make sense of procurement decisions in relation to open source software in the public sector and private companies.},
	keywords = {benefits, exit costs, open source software, software adoption, Survey, tco, total cost of ownership},
	author = {Maha Shaikh and Cornford, Tony}
}
@proceedings {1272,
	title = {Ginga-J: An Open Java-Based Application Environment for Interactive Digital Television Services},
	year = {2011},
	month = {10/2011},
	pages = {34-49},
	publisher = {Springer},
	abstract = {This paper aims to present a Ginga-J{\textquoteright}s reference implementation. Although based on a particular platform, the implementation not only works as a proof of concept, but also raised several issues and difficulties on the software architecture project that should be taken into account to ease extensibility and porting to other platforms. Ginga is the standard middleware for the Brazilian DTV System. Its imperative environment (Ginga-J) is based on new JavaDTV specification and mandatory for fixed terrestrial receptors.},
	author = {Kulesza, Raoni and Lima, Jefferson F.A. and Guedes, Alan L. and Junior, Lucenildo L.A. and Meira, Silvio R.L. and Filho, Guido L.S.}
}
@proceedings {1298,
	title = {Health Informatics: The Relevance of Open Source and Multilevel Modeling},
	year = {2011},
	month = {10/2011},
	pages = {338-347},
	publisher = {Springer},
	abstract = {Health information features significant spatial-temporal and domain complexities, which brings challenges to the implementation of patient-centered, interoperable and semantically coherent healthcare information systems. This position paper supports the idea that the multilevel modeling approach is essential to ensure interoperability at the semantic level, but true interoperability is only achieved by the adoption of open standards, and open source implementations are needed for promote competition based on software quality. The Multilevel Healthcare Information Modelling (MLHIM) specifications are presented as the fully open source multilevel modeling reference implementation, and best practices for the development of multilevel- based open source healthcare applications are suggested.},
	keywords = {Health informatics, multilevel modeling, open source software},
	author = {Cavalini, Luciana T. and Cook, Timothy W.}
}
@proceedings {1282,
	title = {A Historical Account of the Value of Free and Open Source Software: From Software Commune to Commercial Commons},
	year = {2011},
	note = {"In order to understand how perceptions of FOSS software have developed over time, we have traced justifying arrangements that historically have been used to define the value of FOSS. This has been done by going through canonical texts and previous research [3]; i.e. we look at research and publications considered to have had a major impact on the perception of FOSS...."

Software Commune, software bazaar, public commons},
	month = {10/2011},
	pages = {196-207},
	publisher = {Springer},
	abstract = {Free and open source software has transformed from what has been characterized as a resistance movement against proprietary software to become a commercially viable form of software development, integrated in various forms with proprietary software business. In this paper we explain this development as a dependence on historical formations, shaped by different ways of justifying the use of open source during different periods of time. These formations are described as arrangements of different justificatory logics within a certain time frame or a certain group of actors motivating the use of free and open source software by referring to different potentialities. The justificatory arrangements change over time, and tracing these changes makes it easier to understand how the cultural, economic and social practices of open source movements are currently being absorbed and adopted in a commercial context.},
	keywords = {Free and Open Source Software, Historical approach, Justification}
}
@conference {1307,
	title = {How do developers blog?},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {publishing frequency, post structure, word usage, publication patterns, content},
	month = {05/2011},
	pages = {123-132},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {We report on an exploratory study, which aims at understanding how software developers use social media compared to conventional development infrastructures. We analyzed the blogging and the committing behavior of 1,100 developers in four large open source communities. We observed that these communities intensively use blogs with one new entry about every 8 hours. A blog entry includes 14 times more words than a commit message. When analyzing the content of the blogs, we found that most popular topics represent high-level concepts such as functional requirements and domain concepts. Source code related topics are covered in less than 15\% of the posts. Our results also show that developers are more likely to blog after corrective engineering and management activities than after forward engineering and re-engineering activities. Our findings call for a hypothesis-driven research to further understand the role of social media in software engineering and integrate it into development processes and tools.},
	keywords = {blog, communication, developer, eclipse, gnome, LDA, postgres, python},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985461},
	author = {Maalej, Walid and Pagano, Dennis}
}
@proceedings {1270,
	title = {Impact of Stakeholder Type and Collaboration on Issue Resolution Time in OSS Projects},
	year = {2011},
	note = {"First, we characterize the difference in the average amount of resolved issues and issue resolution time between a volunteer assignee and a firm-paid assignee....Second, we investigate collaboration among stakeholders in OSS projects by using Social network metrics and analysis. Last, we explore the impact of the collaboration measures on issue resolution time."

"Three OSS projects were selected for our study, namely Qt, Qpid and Geronimo"

"All software issues were collected from JIRA repositories...Issue resolution time was computed by using the created time field and the issue resolved time field."},
	month = {10/2011},
	pages = {1-16},
	publisher = {Springer},
	abstract = {Initialized by a collective contribution of volunteer developers, Open source software (OSS) attracts an increasing involvement of commercial firms. Many OSS projects are composed of a mix group of firm-paid and volunteer developers, with different motivations, collaboration practices and working styles. As OSS development consists of collaborative works in nature, it is important to know whether these differences have an impact on collaboration between difference types of stakeholders, which lead to an influence in the project outcomes. In this paper, we empirically investigate the firm-paid participation in resolving OSS evolution issues, the stakeholder collaboration and its impact on OSS issue resolution time. The results suggest that though a firm-paid assigned developer resolves much more issues than a volunteer developer does, there is no difference in issue resolution time between them. Besides, the more important factor that influences the issue resolution time comes from the collaboration among stakeholders rather than from individual characteristics.},
	keywords = {COLLABORATION, companies, coordination, defects, feature requests, geronimo, jira, qpid, qt, social network analysis, volunteer},
	author = {Duc, Ach Nguyen and Cruzes, Daniela S. and Ayala, Claudia and Conradi, Reidar}
}
@proceedings {1279,
	title = {The Importance of Architectural Knowledge in Integrating Open Source Software},
	year = {2011},
	month = {10/2011},
	pages = {142-158},
	publisher = {Springer},
	abstract = {Open Source Software (OSS) is increasingly used in Component-Based Software Development (CBSD) of large software systems. An important issue in CBSD is selection of suitable components. Various OSS selection methods have been proposed, but most of them do not consider the software architecture aspects of OSS products. The Software Architecture (SA) research community refers to a product{\textquoteright}s architectural information, such as design decisions and underlying rationale, and used architecture patterns, as Architecture Knowledge (AK). In order to investigate the importance of AK of OSS components in integration, we conducted an exploratory empirical study. Based on in-depth interviews with 12 IT professionals, this paper presents insights into the following questions: 1) what AK of OSS is needed? 2) Why is AK of OSS needed? 3) Is AK of OSS generally available? And 4) what is the relative importance of AK? Based on these new insights, we provide a research agenda to further the research field of software architecture in OSS.},
	keywords = {architectural knowledge, component-based development, Open Source Software integration, OSS Integrator, software architecture, Survey},
	author = {Stol, Klaas-Jan and Ali Babar, Muhammad and Avgeriou, Paris}
}
@conference {Sethanandha:2011:IOS:1985793.1986018,
	title = {Improving open source software patch contribution process: methods and tools},
	booktitle = {Proceedings of the 33rd International Conference on Software Engineering},
	series = {ICSE {\textquoteright}11},
	year = {2011},
	pages = {1134{\textendash}1135},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The patch contribution process (PCP) is very important to the sustainability of OSS projects. Nevertheless, there are several issues on patch contribution in mature OSS projects, which include time consuming process, lost and ignored patches, slow review process. These issues are recognized by researchers and OSS projects, but have not been addressed. In this dissertation, I apply Kanban method to guide process improvement and tools development to reduce PCP cycle time.},
	keywords = {coordination, free software, kanban, lean methods, open source software, patches, productivity},
	isbn = {978-1-4503-0445-0},
	doi = {10.1145/1985793.1986018},
	url = {http://doi.acm.org/10.1145/1985793.1986018},
	author = {Bhuricha Deen Sethanandha}
}
@conference {1306,
	title = {Java generics adoption},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"we automatically analyzed 20 open source software projects. We analyzed the top {\textquotedblleft}most used{\textquotedblright} projects according to ohloh.net, including only projects with significant amounts of Java code"

"The 20 selected projects were Ant, Azureus, CheckStyle, Commons Collections, Free- Mind, FindBugs, Jetty, JEdit, JDT, JUnit, Eclipse-cs, Hibernate, Log4j, Lucene, Maven, the Spring Frame- work, Squirrel-SQL, Subclipse, Weka, and Xerces."

"In mining the full version histories of these 20 projects, we analyzed the full content of each version of each Java source file, a total of 548,982,841 lines."},
	month = {05/2011},
	pages = {3-12},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Support for generic programming was added to the Java language in 2004, representing perhaps the most significant change to one of the most widely used programming languages today. Researchers and language designers anticipated this addition would relieve many long-standing problems plaguing developers, but surprisingly, no one has yet measured whether generics actually provide such relief. In this paper, we report on the first empirical investigation into how Java generics have been integrated into open source software by automatically mining the history of 20 popular open source Java programs, traversing more than 500 million lines of code in the process. We evaluate five hypotheses, each based on assertions made by prior researchers, about how Java developers use generics. For example, our results suggest that generics do not significantly reduce the number of type casts and that generics are usually adopted by a single champion in a project, rather than all committers.},
	keywords = {commits, generics, java, source code, version history},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985446},
	author = {Christian Bird and Murphy-Hill, Emerson and Parnin, Chris}
}
@conference {1481,
	title = {Joining Free/Open Source Software Communities: An Analysis of Newbies{\textquoteright} First Interactions on Project Mailing Lists},
	booktitle = {2011 44th Hawaii International Conference on System Sciences (HICSS 2011)},
	year = {2011},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Kauai, HI},
	abstract = {Free/Open source software (FOSS) is an important part of the IT ecosystem. Due to the voluntary nature of participation, continual recruitment is key to the growth and sustainability of these communities. It is therefore important to understand how and why potential contributors fail in the process of transitioning from user to contributor. Most newcomers, or "newbies", have their first interaction with a community through a mailing list. To understand how this first contact influences future interactions, we studied eight mailing lists across four FOSS projects: MediaWiki, GIMP, PostgreSQL, and Subversion. We analyzed discussions initiated by newbies to determine the effect of gender, nationality, politeness, helpfulness and timeliness of response. We found that nearly 80\% of newbie posts received replies, and that receiving timely responses, especially within 48 hours, was positively correlated with future participation. We also found that while the majority of interactions were positive, 1.5\% of responses were rude or hostile.},
	keywords = {email, email archive, gimp, mailing list, mediawiki, postgresql, subversion},
	isbn = {978-1-4244-9618-1},
	doi = {10.1109/HICSS.2011.264},
	author = {Jensen, Carlos and King, Scott and Kuechler, Victor}
}
@proceedings {1277,
	title = {Knowledge Homogeneity and Specialization in the Apache HTTP Server Project},
	year = {2011},
	note = {"Our data set consists of the commit history and email archives for the Apache HTTP Server Project, spanning sixteen years (2/27/1995 - 1/31/2011)"

"we 1) mapped the committers to email records, 2) cleaned the email records to remove extraneous information, 3) identified topics of discussion in the resulting messages, and 4) constructed a social network model from committers and topics."

"If specialization exists within the httpd community, we should see distinct communities develop around topics. In addition, unique groups of developers should congregate around specialized subtopics. We examined the data from both angles: topical affinity and topic communities."
},
	month = {10/2011},
	pages = {106-122},
	publisher = {Springer},
	abstract = {We present an analysis of developer communication in the Apache HTTP Server project. Using topic modeling techniques we expose latent conceptual sub-communities arising from developer specialization within the greater developer population. However, we found that among the major contributors to the project, very little specialization exists. We present theories to explain this phenomenon, and suggest further research.},
	keywords = {apache, commits, developer, email, email archive, LDA, mailing list, revision control, revision history, scm, social network analysis, specialization, subversion, svn},
	url = {http://sequoia.cs.byu.edu/lab/files/pubs/MacLean2011a.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MacLean2011a.pdf},
	author = {MacLean, Alexander C. and Pratt, Landon J. and Knutson, Charles D. and Ringger, Eric K.}
}
@proceedings {1292,
	title = {KommGame: A Reputation Environment for Teaching Open Source Software},
	year = {2011},
	month = {10/2011},
	pages = {312-315},
	publisher = {Springer},
	abstract = {The importance of teaching open source software in universities is increasing with the advent of open source as a development and business model. A novel, student centric approach of teaching open source was tried out at Tampere University of Technology where a new environment called KommGame was introduced to assist in teaching open source development. This environment includes a reputation system to motivate learners to participate. In this paper, we present our approach of teaching open source and how the KommGame environment was employed to teach open source software.},
	author = {Goduguluri, Veerakishore and Kilamo, Terhi and Hammouda, Imed}
}
@proceedings {1284,
	title = {Libre Software as an Innovation Enabler in India: Experiences of a Bangalorian Software SME},
	year = {2011},
	month = {10/2011},
	pages = {220-232},
	publisher = {Springer},
	abstract = {Free/Libre and open source software (FLOSS) has been advocated for its presumed capacity to support native software industries in developing countries. It is said to create new spaces for exploration and to lower entry barriers to mature software markets, for example. However, little empirical research has been conducted concerning FLOSS business in a developing country setting and, thus, there is not much evidence to support or refute these claims. This paper presents a business case study conducted in India, a country branded as a {\textquoteright}software powerhouse{\textquoteright} of the developing world. The findings show how FLOSS has opened up significant opportunities for the case company, especially in terms of improving its innovative capability and upgrading in the software value chain. On the other hand, they also highlight some challenges to FLOSS involvement that rise specifically from the Indian context.},
	keywords = {free software, India, INNOVATION, open source, software business},
	author = {Henttonen, Katja}
}
@proceedings {1281,
	title = {License Update and Migration Processes in Open Source Software Projects},
	year = {2011},
	note = {"The case studies in this report are part of an ongoing, multi-year research project discovering and modeling open source software processes. Our research methodology is ethnographically informed, applying a grounded theory to the analysis of artifacts found in OSS projects. The primary data sources in this study come from mailing list archives of the Apache and NetBeans projects."},
	month = {10/2011},
	pages = {177-195},
	publisher = {Springer},
	abstract = {Open source software (OSS) has increasingly been the subject of research efforts. Central to this focus is the nature under which the software can be distributed, used, and modified and the causes and consequent effects on software development, usage, and distribution. At present, we have little understanding of, what happens when these licenses change, what motivates such changes, and how new licenses are created, updated, and deployed. Similarly, little attention has been paid to the agreements under which contributions are made to OSS projects and the impacts of changes to these agreements. We might also ask these same questions regarding the licenses governing how individuals and groups contribute to OSS projects. This paper focuses on addressing these questions with case studies of processes by which the Apache Software Foundation{\textquoteright}s creation and migration to Version 2.0 of the Apache Software License and the NetBeans project{\textquoteright}s migration to the Joint Licensing Agreement.},
	keywords = {apache, case study, email, email archive, license evolution, mailing list, netbeans, open source, process},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1.pdf},
	author = {Chris Jensen and Walt Scacchi}
}
@proceedings {1274,
	title = {Modding as an Open Source Approach to Extending Computer Game Systems},
	year = {2011},
	month = {10/2011},
	pages = {62-74},
	publisher = {Springer},
	abstract = {This paper examines what is known so far about the role of open source software development within the world of game mods and modding practices. Game modding has become a leading method for developing games by customizing or creating OSS extensions to game software in general, and to proprietary closed source software games in particular. What, why, and how OSS and CSS come together within an application system is the subject for this study. The research method is observational and qualitative, so as to highlight current practices and issues that can be associated with software engineering and game studies foundations. Numerous examples of different game mods and modding practices are identified throughout.},
	keywords = {games, modding, mods},
	author = {Walt Scacchi}
}
@conference {Jergensen:2011:OPM:2025113.2025127,
	title = {The onion patch: migration in open source ecosystems},
	booktitle = {Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering},
	series = {ESEC/FSE {\textquoteright}11},
	year = {2011},
	pages = {70{\textendash}80},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Past research established that individuals joining an Open Source community typically follow a socialization process called "the onion model": newcomers join a project by first contributing at the periphery through mailing list discussions and bug trackers and as they develop skill and reputation within the community they advance to central roles of contributing code and making design decisions. However, the modern Open Source landscape has fewer projects that operate independently and many projects under the umbrella of software ecosystems that bring together projects with common underlying components, technology, and social norms. Participants in such an ecosystems may be able to utilize a significant amount of transferrable knowledge when moving between projects in the ecosystem and, thereby, skip steps in the onion model. In this paper, we examine whether the onion model of joining and progressing in a standalone Open Source project still holds true in large project ecosystems and how the model might change in such settings.},
	keywords = {contribution model, open source software, project ecosystem},
	isbn = {978-1-4503-0443-6},
	doi = {10.1145/2025113.2025127},
	url = {http://doi.acm.org/10.1145/2025113.2025127},
	author = {Jergensen, Corey and Sarma, Anita and Wagstrom, Patrick}
}
@article {1322,
	title = {The Ontology of the OSS Business Model},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {39 - 59},
	abstract = {This study focuses on theory building providing a holistic conceptual framework that consists of an ontology based OSS business model and an OSS business model taxonomy. The study extends existing theory in OSS business models and corresponding taxonomies, based on the structured-case methodological approach. An exploratory study is conducted in two research cycles, for the identification, validation, and evaluation of the critical constructs of an OSS business model. Results reveal that OSS business models differ from traditional software business models, having specific features that affect the software value chain, the infrastructure, and the revenue model of an OSS oriented firm.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011010103},
	author = {Lakka, Spyridoula and Stamati, Teta and Michalakelis, Christos and Martakos, Dracoulis}
}
@proceedings {1296,
	title = {Open Source and Open Data: Business Perspectives from the Frontline},
	year = {2011},
	month = {10/2011},
	pages = {330-333},
	publisher = {Springer},
	abstract = {Open data initiatives on governmental data seem often to be linked to small software companies, which also use and release software under OSS licenses. This paper calls for more research to understand the similarities between open data and open source software vendors. We build a theoretical linkage between the more established OSS research and emerging research on open data in the context of small software companies.},
	author = {Juho Lindman and Tammisto, Yulia}
}
@proceedings {1299,
	title = {Open Source Software for Model Driven Development: A Case Study},
	year = {2011},
	month = {10/2011},
	pages = {348-367},
	publisher = {Springer},
	abstract = {Model Driven Development (MDD) is widely used in the embedded systems domain, and many proprietary and Open Source tools exist that support MDD. The potential for sustainability of such tools needs to assessed prior to any organisational adoption. In this paper we report from a case study conducted in a consultancy company context aiming to investigate Open Source tools for MDD. For the company it was interesting to explore the two Open Source modelling tools Topcased and Papyrus for potential adoption. The focus for our case study is on assessing the health of the ecosystems for the two investigated Open Source projects by means of quantitative analysis of publically available data sources about Open Source projects. The health of ecosystems is an important prerequisite for a long term sustainable OSS (Open Source Software) tool-chain in the MDD area, which can aid strategic decision making for potential adoption within a company context. We have established details on the extent to which developers and users are active in two specific OSS ecosystems, and identified organisational influence for both ecosystems. We find that the investigated tools are promising regarding the health of their ecosystems, and a natural next step for the company would be to proceed with a pilot study in order to analyse the effectiveness of the investigated tools in company contexts.},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn and Mattsson, Anders}
}
@article {1323,
	title = {OSS-TMM},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {1 - 22},
	abstract = {Open Source Software (OSS) products do not usually follow traditional software engineering development paradigms. Specifically, testing activities in OSS development may be quite different from those carried out in Closed Source Software (CSS) development. As testing and verification require a good deal of resources in OSS, it is necessary to have ways to assess and improve OSS testing processes. This paper provides a set of testing guidelines and issues that OSS developers can use to decide which testing techniques make most sense for their OSS products. This paper 1) provides a checklist that helps OSS developers identify the most useful testing techniques according to the main characteristics of their products, and 2) outlines a proposal for a method that helps assess the maturity of OSS testing processes. The method is a proposal of a Maturity Model for testing processes (called OSS-TMM). To show its usefulness, the authors apply the method to seven real-life projects. Specifically, the authors apply the method to BusyBox, Apache Httpd, and Eclipse Test \& Performance Tools Platform to show how the checklist supports and guides the testing process of these OSS products.},
	keywords = {testing},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011040101},
	author = {Morasca, Sandro and Taibi, Davide and Tosi, Davide}
}
@proceedings {1290,
	title = {Package Upgrade Robustness: An Analysis for GNU/Linux Package Management Systems},
	year = {2011},
	month = {10/2011},
	pages = {299-306},
	publisher = {Springer},
	abstract = {GNU/Linux systems are today used in servers, desktops, mobile and embedded devices. One of the critical operations is the installation and maintenance of software packages in the system. Currently there are no frameworks or tools for evaluating Package Management Systems (PMSs), such as RPM, in Linux and for measuring their reliability. The authors perform an analysis of the robustness of the RPM engine and discuss some of the current limitations. This article contributes to the enhancement of Software Reliability in Linux by providing a framework and testing tools under an open source license. These tools can easily be extended to other PMSs such as DEB packages or Gentoo Portage.},
	keywords = {linux, package management, rpm},
	author = {Thomson, John and Guerrriro, Andre and Paulo Trezentos and Johnson, Jeff}
}
@article {1420,
	title = {Path dependent stochastic models to detect planned and actual technology use: A case study of OpenOffice},
	journal = {Information and Software Technology},
	volume = {53},
	year = {2011},
	month = {11/2011},
	pages = {1209 - 1226},
	abstract = {Abstract
Context

Adopting IT innovation in organizations is a complex decision process driven by technical, social and economic issues. Thus, those organizations that decide to adopt innovation take a decision of uncertain success of implementation, as the actual use of a new technology might not be the one expected. The misalignment between planned and effective use of innovation is called assimilation gap.
Objective

This research aims at defining a quantitative instrument for measuring the assimilation gap and applying it to the case of the adoption of OSS.
Method

In this paper, we use the theory of path dependence and increasing returns of Arthur. In particular, we model the use of software applications (planned or actual) by stochastic processes defined by the daily amounts of files created with the applications. We quantify the assimilation gap by comparing the resulting models by measures of proximity.
Results

We apply and validate our method to a real case study of introduction of OpenOffice. We have found a gap between the planned and the effective use despite well-defined directives to use the new OS technology. These findings suggest a need of strategy re-calibration that takes into account environmental factors and individual attitudes.
Conclusions

The theory of path dependence is a valid instrument to model the assimilation gap provided information on strategy toward innovation and quantitative data on actual use are available.},
	keywords = {Actual use of technology, Path dependence, Technology adoption, Urn models},
	issn = {09505849},
	doi = {10.1016/j.infsof.2011.05.002},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584911001042},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo}
}
@proceedings {1275,
	title = {Preparing FLOSS for Future Network Paradigms: A Survey on Linux Network Management},
	year = {2011},
	month = {10/2011},
	pages = {75-89},
	publisher = {Springer},
	abstract = {Operating system tools must fulfill the requirements generated by the advances in networking paradigms. To understand the current state of the Free, Libre and Open Source Software (FLOSS) ecosystem, we present a survey on the main tools used to manage and interact with the network, and how they are organized in Linux-based operating systems. Based on the survey results, we present a reference Linux network stack that can serve as the basis for future heterogeneous network environments, contributing towards a standardized approach in Linux. Using this stack, and focusing on dynamic and spontaneous network interactions, we present an evolution path for network related technologies, contributing to Linux as a network research operating system and to FLOSS as a whole.},
	keywords = {linux, networking, Survey},
	author = {Matos, Alfredo and Thomson, John and Paulo Trezentos}
}
@conference {1406,
	title = {Process Mining Software Repositories},
	booktitle = {15th European Conference on Software Maintenance and Reengineering (CSMR 2011) },
	year = {2011},
	pages = {5 - 14},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Oldenburg, Germany},
	abstract = {Software developers{\textquoteright} activities are in general recorded in software repositories such as version control systems, bug trackers and mail archives. While abundant information is usually present in such repositories, successful information extraction is often challenged by the necessity to simultaneously analyze different repositories and to combine the information obtained.

We propose to apply process mining techniques, originally developed for business process analysis, to address this challenge. However, in order for process mining to become applicable, different software repositories should be combined, and {\textquotedblleft}related{\textquotedblright} software development events should be matched: e.g., mails sent about a file, modifications of the file and bug reports that can be traced back to it.

The combination and matching of events has been implemented in FRASR (FRamework for Analyzing Software Repositories), augmenting the process mining framework ProM. FRASR has been successfully applied in a series of case studies addressing such aspects of the development process as roles of different developers and the way bug reports are handled.},
	keywords = {amsn, email, email archives, gcc, mailing list, Process mining, software repositories},
	isbn = {978-1-61284-259-2},
	doi = {10.1109/CSMR.2011.5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2011-03_CSMR.pdf},
	author = {Poncin, Wouter and Serebrenik, Alexander and Brand, Mark van den}
}
@article {1384,
	title = {On qualitative methodologies and dispersed communities: Reflections on the process of investigating an open source community},
	journal = {Information and Software Technology},
	volume = {53},
	year = {2011},
	month = {9/2011},
	pages = {981 - 993},
	abstract = {Context

Qualitative methodologies hold much potential for building an understanding of the principles and practices of free and open source software (FOSS) communities. Yet there is a scarcity in the literature of discussions focused on the practical and methodological challenges of this particular research context.
Objective

This paper formulates and addresses a number of questions regarding the applicability of qualitative methodologies for the study of FOSS communities. It reflects on the challenges of such approaches as seen in previous research efforts and discusses how they manifest in research practice through a thorough description of a case study of a community called PyPy.
Method

The paper primarily discusses interpretive research approaches which are based on ethnographic data collection methods. The study under discussion was an exploratory case study utilizing multiple methods, including participant observation, virtual ethnography, and open-ended questionnaires. Grounded Theory was used for data analysis.
Results

Two broad sets of challenges are highlighted in relation to the multidimensionality of the FOSS phenomenon and the difficulty of qualitative analysis of activities in long-term context. Additional issues identified relate to potential problems with focus and the need for reflexivity, but also to the extent of the study and the importance of maintaining an active relationship with the core community group.
Conclusion

This paper provides an overview {\textendash} grounded in practical research experience and linked to insights from the literature {\textendash} of methodological issues in the specific research area of qualitative studies of FOSS communities, which up until now has been lacking.},
	keywords = {case study, Collaborative practice, Distributed software development, Free open source communities, Qualitative methodologies},
	issn = {09505849},
	doi = {10.1016/j.infsof.2011.01.012},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584911000413},
	author = {Sigfridsson, Anders and Sheehan, Anne}
}
@proceedings {1276,
	title = {A Review of Tool Support for User-Related Communication in FLOSS Development},
	year = {2011},
	note = {"We have carried out a literature review addressing communication in FLOSS projects, and contrasted the findings with Human-Computer Interaction (HCI) literature on user-developer communication."},
	month = {10/2011},
	pages = {90-105},
	abstract = {Free/Libre/Open Source Software (FLOSS) projects rely on Internet tools for communication and in coordinating their work. Communication between developers is well supported in FLOSS projects, but user-developer communication has proven out to be challenging. This paper examines the following questions: {\textquotedblright}What kinds of means for communication exist in FLOSS projects for user-developer communication? What kinds of means should there be?{\textquotedblright} We have carried out a literature review addressing communication in FLOSS projects, and contrasted the findings with Human-Computer Interaction (HCI) literature on user-developer communication. HCI literature indicates that user-developer communication is needed during requirements construction, design and evaluation tasks, and HCI specialists are needed for orchestrating the communication and the user related tasks. Communication during the evaluation task is somewhat supported in FLOSS projects, but design and requirements construction are badly in need for support, even though ideas have already been presented. In addition, HCI specialists are in need of different kinds of communication support in FLOSS projects.},
	keywords = {Free/Libre/Open Source Software, Human-Computer Interaction, literature review, Tool Support, User-Developer Communication},
	author = {Rantalinen, Aapo and Hedberg, Henrik and Iivari, Netta}
}
@article {1398,
	title = {The search for a research method for studying OSS process innovation},
	journal = {Empirical Software Engineering},
	volume = {16},
	year = {2011},
	month = {8/2011},
	pages = {514 - 537},
	abstract = {Medium-sized, open-participation Open Source Software (OSS) projects do not usually perform explicit software process improvement on any routine basis. It would be useful to understand how to get such a project to accept a process improvement proposal and hence to perform process innovation. We want to determine an effective and feasible qualitative research method for studying the above question. We present (narratively) a case study of how we worked towards and eventually found such a research method. The case involves four attempts at collecting suitable data about innovation episodes (direct participation (twice), polling developers for episodes, manually finding episodes in mailing list archives) and the adaptation of the Grounded Theory data analysis methodology. Direct participation allows gathering rather rich data, but does not allow for observing a sufficiently large number of innovation episodes. Polling developers for episodes did not prove to be useful. Using mailing list archives to find data to be analyzed is both feasible and effective. We also describe how the data thus found can be analyzed based on the Grounded Theory Method with suitable adjustments. By-and-large, our findings ought to apply to studying various phenomena in OSS development processes that are similarly heavyweight and infrequent. However, specific details may block this possibility and we cannot predict which details that might be. The amount of effort involved in direct participation approaches to qualitative research can easily be underestimated. Also, survey approaches are not well-suited for many process issues in OSS, because too few developers are sufficiently process-conscious. An approach based on passive observation is a viable alternative in the OSS context due to the availability of large amounts of fairly complete archival data. },
	keywords = {argouml, Bochs, bugzilla, Flyspray, FreeDOS, gEDA, grounded theory, Grub, Innovation introduction, KVM, mailing list, Methodology, MonetDB, open source, Request Tracket, Rox, U-Boot, Xfce},
	issn = {1573-7616},
	doi = {10.1007/s10664-011-9160-1},
	author = {Prechelt, Lutz and Oezbek, Christopher}
}
@conference {1520,
	title = {A Secondary Data Archive for Code-Level Debian Metrics},
	booktitle = {2011 Second International Workshop on Replication in Empirical Software Engineering Research (RESER)},
	year = {2011},
	month = {09/2011},
	pages = {43 - 51},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Banff, Alberta, Canada},
	abstract = {In this paper, we describe a new process to collect, calculate, archive, and distribute interesting metrics for all the packages in the standard Debian GNU/Linux installation. Our method replicates and extends previous work done by other groups studying free and open source software systems (FLOSS) in three important ways. First, although there have been other previous studies that attempted to collect a large set of code-level metrics for a small set of projects, and there have been studies that generated a small set of metrics for the large Debian codebase, our project does both: we generate a larger set of metrics for the entire set of Debian packages. Second, our integration of new Debian metadata and additional code-level metrics not gathered before adds several additional layers for exploration. Finally, and most importantly, because we integrate our collection and analysis process into the automated FLOSSmole data store, we ensure timely, repeatable, and very easy comparison, replication and analysis by other groups. Thus our collection activity will continue in an automated fashion even after this paper is published, providing the foundation for additional studies to be conducted later, all freely accessible to any interested research group. After outlining our process, we discuss a few observations about the data, we outline some implications for the research community, and we present opportunities for further research.},
	isbn = {978-1-4673-0972-1},
	doi = {10.1109/RESER.2011.9},
	author = {Kozak, Carter and Squire, Megan}
}
@conference {1308,
	title = {Social interactions around cross-system bug fixings},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"We rely on information stored in versioning database and mailing lists of both systems and develop methods to reconstruct and integrate different historical database"},
	month = {05/2011},
	pages = {143-152},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Cross-system bug fixing propagation is frequent among systems having similar characteristics, using a common framework, or, in general, systems with cloned source code fragments. While previous studies showed that clones tend to be properly maintained within a single system, very little is known about cross-system bug management.

This paper describes an approach to mine explicitly documented cross-system bug fixings, and to relate their occurrences to social characteristics of contributors discussing through the project mailing lists--e.g., degree, betweenness, and brokerage--as well as to the contributors{\textquoteright} activity on source code.

The paper reports results of an empirical study carried out on FreeBSD and OpenBSD kernels. The study shows that the phenomenon of cross-system bug fixing between these two projects occurs often, despite the limited overlap of contributors. The study also shows that cross-system bug fixings mainly involve contributors with the highest degree, betweenness and brokerage level, as well as contributors that change the source code more than others.},
	keywords = {bug fixing, bug tracking system, committers, email, email archives, freebsd, mailing list, openbsd},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985463},
	author = {Cerulo, Luigi and Cimitile, Marta and Di Penta, Massimiliano and Canfora, Gerardo}
}
@article {1386,
	title = {Sociomaterial bricolage: The creation of location-spanning work practices by global software developers},
	journal = {Information and Software Technology},
	volume = {53},
	year = {2011},
	month = {9/2011},
	pages = {955 - 968},
	abstract = {Context

Studies on global software development have documented severe coordination and communication problems among coworkers due to geographic dispersion and consequent dependency on technology. These problems are exacerbated by increase in the complexity of work undertaken by global teams. However, despite these problems, global software development is on the rise and firms are adopting global practices across the board, raising the question: What does successful global software development look like and what can we learn from its practitioners?
Objective

This study draws on practice-based studies of work to examine successful work practices of global software developers. The primary aim of this study was to understand how workers develop practices that allow them to function effectively across geographically dispersed locations.
Method

An ethnographically-informed field study was conducted with data collection at two international locations of a firm. Interview, observation and archival data were collected. A total of 42 interviews and 3 weeks of observations were conducted.
Results

Teams spread across different locations around the world developed work practices through sociomaterial bricolage. Two facets of technology use were necessary for the creation of these practices: multiplicity of media and relational personalization at dyadic and team levels. New practices were triggered by the need to achieve a work-life balance, which was disturbed by global development. Reflecting on my role as a researcher, I underscore the importance of understanding researchers{\textquoteright} own frames of reference and using research practices that mirror informants{\textquoteright} work practices.
Conclusion

Software developers on global teams face unique challenges which necessitate a shift in their work practices. Successful teams are able to create practices that span locations while still being tied to location based practices. Inventive use of material and social resources is central to the creation of these practices.},
	keywords = {Global software development, Interpretive analysis, interviews, Qualitative field study, Sociomaterial bricolage, Virtual teams, Work practices},
	issn = {09505849},
	doi = {10.1016/j.infsof.2011.01.014},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584911000437},
	author = {Johri, Aditya}
}
@booklet {bird2011scc,
	title = {Sociotechnical Coordination and Collaboration in Open Source Software},
	howpublished = {Proceedings of the 27th IEEE International Conference on Software Maintenance},
	year = {2011},
	publisher = {IEEE},
	abstract = {Over the past decade, a new style of software development, termed open source software (OSS) has emerged and has originated large, mature, stable, and widely used software projects. As software continues to grow in size and complexity, so do development teams. Consequently, coordination and communication within these teams play larger roles in productivity and software quality. My dissertation focuses on the relationships between developers in large open source projects and how software affects and is affected by these relationships. Fortunately, source code repository histories, mailing list archives, and bug databases from OSS projects contain latent data from which we can reconstruct a rich view of a project over time and analyze these sociotechnical relationships. We present methods of obtaining and analyzing this data as well as the results of empirical studies whose goal is to answer questions that can help stakeholders understand and make decisions about their own teams. We answer questions such as {\textquotedblleft}Do large OSS project really have a disorganized bazaar-like structure?{\textquotedblright} {\textquotedblleft}What is the relationship between social and development behavior in OSS?{\textquotedblright}
{\textquotedblleft}How does one progress from a project newcomer to a full-fledged, core developer?{\textquotedblright} and others in an attempt to understand how large, successful OSS projects work and also to contrast them with projects in commercial settings.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2011scc.pdf},
	author = {Christian Bird}
}
@conference {Meneely:2011:SDN:1985793.1985832,
	title = {Socio-technical developer networks: should we trust our measurements?},
	booktitle = {Proceedings of the 33rd International Conference on Software Engineering},
	series = {ICSE {\textquoteright}11},
	year = {2011},
	pages = {281{\textendash}290},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software development teams must be properly structured to provide effectiv collaboration to produce quality software. Over the last several years, social network analysis (SNA) has emerged as a popular method for studying the collaboration and organization of people working in large software development teams. Researchers have been modeling networks of developers based on socio-technical connections found in software development artifacts. Using these developer networks, researchers have proposed several SNA metrics that can predict software quality factors and describe the team structure. But do SNA metrics measure what they purport to measure? The objective of this research is to investigate if SNA metrics represent socio-technical relationships by examining if developer networks can be corroborated with developer perceptions. To measure developer perceptions, we developed an online survey that is personalized to each developer of a development team based on that developer{\textquoteright}s SNA metrics. Developers answered questions about other members of the team, such as identifying their collaborators and the project experts. A total of 124 developers responded to our survey from three popular open source projects: the Linux kernel, the PHP programming language, and the Wireshark network protocol analyzer. Our results indicate that connections in the developer network are statistically associated with the collaborators whom the developers named. Our results substantiate that SNA metrics represent socio-technical relationships in open source development projects, while also clarifying how the developer network can be interpreted by researchers and practitioners.},
	keywords = {developer network, developers, linux, linux kernel, PHP, social network analysis, Survey, wireshark},
	isbn = {978-1-4503-0445-0},
	doi = {10.1145/1985793.1985832},
	url = {http://doi.acm.org/10.1145/1985793.1985832},
	author = {Meneely, Andrew and Williams, Laurie}
}
@proceedings {1294,
	title = {Something of a Potemkin Village? Acid2 and Mozilla{\textquoteright}s Efforts to Comply with HTML4},
	year = {2011},
	month = {10/2011},
	pages = {320-324},
	publisher = {Springer},
	abstract = {The real point here is that the Acid3 test isn{\textquoteright}t a broad-spectrum standards-support test. It{\textquoteright}s a showpiece, and something of a Potemkin village at that. Which is a shame, because what{\textquoteright}s really needed right now is exhaustive test suites for specifications{\textemdash} XHTML, CSS, DOM, SVG.},
	author = {den Besten, Matthijs and Jean-Michel Dalle}
}
@proceedings {1301,
	title = {Standing Situations and Issues of Open Source Policy in East Asian Nations: Outcomes of Open Source Research Workshop of East Asia},
	year = {2011},
	month = {10/2011},
	pages = {379-384},
	publisher = {Springer},
	abstract = {East Asia nations have made some progress with this technology, and started to introduce OSS for e-government systems during the early part of this century. Many countries granted it a central role in their policies. The reasons for this include adoption of software based on standard specification, liberation from vender lock-in, or opposition to the market control of proprietary software. However, the primary reason is to reduce adoption costs for e-government systems. While this policy work is useful, there is a great deal more that needs to be done. The OSS adoption policy in each nation of East Asia must be accompanied by technological progress in domestic IT service industries or US multinationals will expand at the cost of local businesses. If this continues unchecked it will create a new form of lock-in for East Asian nations. Some Asian nations are trying to promote their domestic IT service industries, putting their OSS adoption policy to practical use, and this workshop will provide case studies of that work. It will also provide a forum for discussing current challenges and opportunities around both policy and practical implementation issues across Asia.},
	author = {Noda, Tetsuo and Tansho, Terutaka and Coughlan, Shane}
}
@conference {1303,
	title = {A study of language usage evolution in open source software},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {13-22},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Waikiki, Honolulu, HI, USA},
	abstract = {The use of programming languages such as Java and C in Open Source Software (OSS) has been well studied. However, many other popular languages such as XSL or XML have received minor attention. In this paper, we discuss some trends in OSS development that we observed when considering multiple programming language evolution of OSS. Based on the revision data of 22 OSS projects, we tracked the evolution of language usage and other artefacts such as documentation files, binaries and graphics files. In these systems several different languages and artefact types including C/C++, Java, XML, XSL, Makefile, Groovy, HTML, Shell scripts, CSS, Graphics files, JavaScript, JSP, Ruby, Phyton, XQuery, OpenDocument files, PHP, etc. have been used. We found that the amount of code written in different languages differs substantially. Some of our findings can be summarized as follows: (1) JavaScript and CSS files most often co-evolve with XSL; (2) Most Java developers but only every second C/C++ developer work with XML; (3) and more generally, we observed a significant increase of usage of XML and XSL during recent years and found that Java or C are hardly ever the only language used by a developer. In fact, a developer works with more than 5 different artefact types (or 4 different languages) in a project on average.},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985447},
	author = {Gall, Harald and Karus, Siim}
}
@proceedings {1280,
	title = {Successful Reuse of Software Components: A Report from the Open Source Perspective},
	year = {2011},
	month = {10/2011},
	pages = {159-176},
	publisher = {Springer},
	abstract = {A promising way of software reuse is Component-Based Software Development (CBSD). There is an increasing number of OSS products available that can be freely used in product development. However, OSS communities themselves have not yet taken full advantage of the {\textquotedblleft}reuse mechanism{\textquotedblright}. Many OSS projects duplicate effort and code, even when sharing the same application domain and topic. One successful counter-example is the FFMpeg multimedia project, since several of its components are widely and consistently reused into other OSS projects. This paper documents the history of the libavcodec library of components from the FFMpeg project, which at present is reused in more than 140 OSS projects. Most of the recipients use it as a black-box component, although a number of OSS projects keep a copy of it in their repositories, and modify it as such. In both cases, we argue that libavcodec is a successful example of reusable OSS library of components.},
	keywords = {component-based software development, OSS components, Software reuse},
	author = {Capiluppi, Andrea and Boldyreff, Cornelia and Stol, Klaas-Jan}
}
@conference {1310,
	title = {System compatibility analysis of Eclipse and Netbeans based on bug data},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {230-233},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Waikiki, Honolulu, HI, USANew York, New York, USA},
	abstract = {Eclipse and Netbeans are two top of the line Integrated Development Environments (IDEs) for Java development. Both of them provide support for a wide variety of development tasks and have a large user base. This paper provides an analysis and comparison for the compatibility and stability of Eclipse and Netbeans on the three most commonly used operating systems, Windows, Linux and Mac OS. Both IDEs are programmed in Java and use a Bugzilla issue tracker to track reported bugs and feature requests. We looked into the Bugzilla repository databases of these two IDEs, which contains the bug records and histories of these two IDEs. We used some basic data mining techniques to analyze some historical statistics of the bug data. Based on the analysis, we try to answer certain stability-comparison oriented questions in the paper, so that users can have a better idea which of these two IDEs is designed better to work on different platforms.

},
	keywords = {bug tracking system, bugzilla, eclipse, ms challenge, netbeans, version history},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985479},
	author = {Baik, Eilwoo and Devanbu, Premkar and Wang, Xinlei (Oscar)}
}
@conference {1312,
	title = {A tale of two browsers},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {238-241},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {We explore the space of open source systems and their user communities by examining the development artifact histories of two popular web browsers -- Firefox and Chrome -- as well as usage data. By examining the data and addressing a number of research questions, two very different profiles emerge: Firefox, as the older and established system, with long product version cycles but short bug fix cycles, and a user base that is slow to adopt newer versions; and Chrome, as the new and fast evolving system, with short version cycles, longer bug fix cycles, and a user base that very quickly adopts new versions as they become available (due largely to Chrome{\textquoteright}s mandatory automatic updates).

},
	keywords = {chrome, development history, Firefox, msr challenge},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985481},
	author = {Davis, Ian and Godfrey, Michael W. and Baysal, Olga}
}
@conference {Stroulia:2011:TDS:1984665.1984670,
	title = {Teaching distributed software engineering with UCOSP: the undergraduate capstone open-source project},
	booktitle = {Proceedings of the 2011 Community Building Workshop on Collaborative Teaching of Globally Distributed Software Development},
	series = {CTGDSD {\textquoteright}11},
	year = {2011},
	pages = {20{\textendash}25},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software engineering courses in computer-science departments are meant to prepare students for the practice of designing, developing, understanding and maintaining software in the real world. The effectiveness of these courses have potentially a tremendous impact on the software industry, since it is through these courses that students must learn the state-of-the-art process and the tools of their eventual "trade", so that they can bring this knowledge to their job and thus advance the actual state of practice. The value of "learning software engineering" through project-based courses has long been recognized by educators and practitioners alike. In this paper, we discuss our experience with a distributed project-based course, which infuses the students{\textquoteright} learning experience with an increased degree of realism, which, we believe, further improves the quality of their learning and advances their readiness to join the profession.},
	keywords = {distributed, education, pedagogical, project-based courses, software engineering education},
	isbn = {978-1-4503-0590-7},
	doi = {10.1145/1984665.1984670},
	url = {http://doi.acm.org/10.1145/1984665.1984670},
	author = {Stroulia, Eleni and Bauer, Ken and Craig, Michelle and Reid, Karen and Wilson, Greg}
}
@proceedings {1300,
	title = {The Third Generation of OSS: A Three-Stage Evolution from Gift to Commerce-Economy},
	year = {2011},
	month = {10/2011},
	pages = {368-378},
	publisher = {Springer},
	abstract = {Linux is penetrating into mobile software as the basis for a mobile middleware platform. It is accelerating the increasing visibility of open source software (OSS) components in mobile middleware platforms. Considering the 10-million lines of code of OSS-based industrial platforms such as a mobile middleware platform, engagement in foundations is inevitable for large-scale packages of OSS for industrial solutions. The author discusses the driving factors toward a foundation-based OSS and the transition of the underlying economy types to analyze the transitions to the third-generation OSS.},
	author = {Yamakami, Toshihiko}
}
@proceedings {1287,
	title = {To Fork or Not to Fork: Fork Motivations in SourceForge Projects},
	year = {2011},
	note = {"Using this search function, we compiled a list of all of the programs with the word {\textquotedblleft}fork{\textquotedblright}..."
"We then analyzed the motivations stated in the descriptions of the forked programs...."
"Based on the descriptions entered by the developer, we were able to identify motivations for 381 of the forks."
},
	month = {10/2011},
	pages = {259-268},
	publisher = {Springer},
	abstract = {A project fork occurs when software developers take a copy of source code from one software package and use it to begin an independent development work that is maintained separately from its origin. Although forking in open source software does not require the permission of the original authors, the new version, nevertheless, competes for the attention of the same developers that have worked on the original version. The motivations developers have for performing forks are many, but in general they have received little attention. In this paper, we present the results of a study of forks performed in SourceForge (http://sourceforge.net/) and list the developers{\textquoteright} motivations for their actions. The main motivation, seen in close to half of the cases of forking, was content modification; either adding content to the original program or focusing the content to the needs of a specific segment of users. In a quarter of the cases the motivation was technical modification; either porting the program to new hardware or software, or improving the original.},
	keywords = {fork rate, sourceforge},
	author = {Nyman, Linus and Mikkonen, Tommi}
}
@article {1325,
	title = {Tool Assisted Analysis of Open Source Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {43 - 78},
	abstract = {Open Source Software (OSS) is currently a widely adopted approach to developing and distributing software. OSS code adoption requires an understanding of the structure of the code base. For a deeper understanding of the maintenance, bug fixing and development activities, the structure of the developer community also needs to be understood, especially the relations between the code and community structures. This, in turn, is essential for the development and maintenance of software containing OSS code. This paper proposes a method and support tool for exploring the relations of the code base and community structures of OSS projects. The method and proposed tool, Binoculars, rely on generic and reusable query operations, formal definitions of which are given in the paper. The authors demonstrate the applicability of Binoculars with two examples. The authors analyze a well-known and active open source project, FFMpeg, and the open source version of the IaaS cloud computing project Eucalyptus.},
	keywords = {artifacts, tools},
	issn = {1942-3934},
	doi = {10.4018/IJOSSP.2011040103},
	author = {Syeed, M.M. Mahbubul and Aaltonen, Timo and Hammouda, Imed and Syst{\"a}, Tarja}
}
@proceedings {1271,
	title = {Towards a Unified Definition of Open Source Quality},
	year = {2011},
	note = {"In order to answer the research question, how is quality defined in the FLOSS literature, we performed a literature review."

"we searched Google Scholar for journal articles and conference papers containing the terms {\textquotedblleft}open source{\textquotedblright} and {\textquotedblleft}quality{\textquotedblright}"

"This process left us with 24 papers, to which we then added 16 from the quality and defect-fixing categories in [34] that met the above stated criteria.
This left us with 40 papers that defined quality and performed some form of empirical validation of that definition."

"there is little consensus in the FLOSS literature when it comes to defining quality."

defect resolution versus modularity: "Defect resolution rates (amount of defects resolved, speed of resolution) are the best way to measure a community{\textquoteright}s commitment to quality, because they recognize that FLOSS is not a static product, but ever evolving. These rates should be calculated per release, and not cumulatively, because the cycle of FLOSS evolution is the release. Researchers should be careful to only include defects and not new feature requests, duplicates, or poorly reported bugs into their calculations.
Modularity is being touted as the main driver of FLOSS quality success, but it needs to be further defined and studied in order to understand how it works."},
	month = {10/2011},
	pages = {17-33},
	publisher = {Springer},
	abstract = {Software quality needs to be specified and evaluated in order to determine the success of a development project, but this is a challenge with Free/Libre Open Source Software (FLOSS) because of its permanently emergent state. This has not deterred the growth of the assumption that FLOSS is higher quality than traditionally developed software, despite of mixed research results. With this literature review, we found the reason for these mixed results is that that quality is being defined, measured, and evaluated differently. We report the most popular definitions, such as software structure measures, process measures, such as defect fixing, and maturity assessment models. The way researchers have built their samples has also contributed to the mixed results with different project properties being considered and ignored. Because FLOSS projects are evolving, their quality is too, and it must be measured using metrics that take into account its community{\textquoteright}s commitment to quality rather than just its software structure. Challenges exist in defining what constitutes a defect or bug, and the role of modularity in affecting FLOSS quality.},
	keywords = {literature review, measurement, open source, quality, Software},
	author = {Ruiz, Claudia and Robinson, William}
}
@proceedings {1286,
	title = {Towards Improving OSS Products Selection {\textendash} Matching Selectors and OSS Communities Perspectives},
	year = {2011},
	month = {10/2011},
	pages = {244-258},
	publisher = {Springer},
	abstract = {Adopting third-party software is becoming an economical and strategic need for today organizations. A fundamental part of its successful adoption is the informed selection of products that best fit the organization needs. One of the main current problems hampering selection, specially of OSS products is the vast amount of unstructured, incomplete, evolvable and widespread information about products that highly increases the risks of taking a wrong decision. In this paper, we aim to inform and provide evidence to OSS communities that help them to envisage improvements on their information rendering strategies to satisfy industrial OSS selectors{\textquoteright} needs. Our results are from the matching between the informational needs of 23 OSS selectors from diverse software-intensive organizations, and the in-depth study of 9 OSS communities of different sizes and domains. The results evidenced specific areas of improvement that might help to enhance the industrial OSS selection practice.},
	keywords = {empirical study, information rendering strategy, open source software, selection},
	author = {Ayala, Claudia and Cruzes, Daniela S. and Franch, Xavier and Conradi, Reidar}
}
@conference {Bougie:2011:TUT:1984701.1984707,
	title = {Towards understanding twitter use in software engineering: preliminary findings, ongoing challenges and future questions},
	booktitle = {Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering},
	series = {Web2SE {\textquoteright}11},
	year = {2011},
	note = {paper d/l from http://www.thechiselgroup.org/publications/content/towards-understanding-twitter-use-software-engineering-preliminary-findings-ong

"From this site, we selected the top 30 individuals for the topics Linux and Eclipse. We chose these two topics based on their potential to expose "tweeters" from a large operating system community as well as an IDE development community. We also decided to investigate a project for which all committers use Twitter. Through a colleague, we were informed that the MXUnit project lists the Twitter user names for all eight of its committers. The MXUnit project [5] is a small, open source ColdFusion test framework that is written as an Eclipse plug-in."},
	pages = {31{\textendash}36},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {There has been some research conducted around the motivation for the use of Twitter and the value brought by micro-blogging tools to individuals and business environments. This paper builds on our understanding of how the phenomenon affects the population which birthed the technology: Software Engineers. We find that the Software Engineering community extensively leverages Twitter{\textquoteright}s capabilities for conversation and information sharing and that use of the tool is notably different between distinct Software Engineering groups. Our work exposes topics for future research and outlines some of the challenges in exploring this type of data.},
	keywords = {eclipse, linux, mxunit, social media, software development, twitter, web 2.0},
	isbn = {978-1-4503-0595-2},
	doi = {10.1145/1984701.1984707},
	url = {http://doi.acm.org/10.1145/1984701.1984707},
	attachments = {https://flosshub.org/sites/flosshub.org/files/WEB2SE2011.pdf},
	author = {Bougie, Gargi and Starke, Jamie and Storey, Margaret-Anne and Daniel M. German}
}
@conference {Bougie:2011:TUT:1984701.1984707,
	title = {Towards understanding twitter use in software engineering: preliminary findings, ongoing challenges and future questions},
	booktitle = {Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering},
	series = {Web2SE {\textquoteright}11},
	year = {2011},
	note = {paper d/l from http://www.thechiselgroup.org/publications/content/towards-understanding-twitter-use-software-engineering-preliminary-findings-ong

"From this site, we selected the top 30 individuals for the topics Linux and Eclipse. We chose these two topics based on their potential to expose "tweeters" from a large operating system community as well as an IDE development community. We also decided to investigate a project for which all committers use Twitter. Through a colleague, we were informed that the MXUnit project lists the Twitter user names for all eight of its committers. The MXUnit project [5] is a small, open source ColdFusion test framework that is written as an Eclipse plug-in."},
	pages = {31{\textendash}36},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {There has been some research conducted around the motivation for the use of Twitter and the value brought by micro-blogging tools to individuals and business environments. This paper builds on our understanding of how the phenomenon affects the population which birthed the technology: Software Engineers. We find that the Software Engineering community extensively leverages Twitter{\textquoteright}s capabilities for conversation and information sharing and that use of the tool is notably different between distinct Software Engineering groups. Our work exposes topics for future research and outlines some of the challenges in exploring this type of data.},
	keywords = {eclipse, linux, mxunit, social media, software development, twitter, web 2.0},
	isbn = {978-1-4503-0595-2},
	doi = {10.1145/1984701.1984707},
	url = {http://doi.acm.org/10.1145/1984701.1984707},
	attachments = {https://flosshub.org/sites/flosshub.org/files/WEB2SE2011_0.pdf},
	author = {Bougie, Gargi and Starke, Jamie and Storey, Margaret-Anne and Daniel M. German}
}
@conference {Rigby:2011:UBB:1985793.1985867,
	title = {Understanding broadcast based peer review on open source software projects},
	booktitle = {Proceedings of the 33rd International Conference on Software Engineering},
	series = {ICSE {\textquoteright}11},
	year = {2011},
	note = {http://helium.cs.uvic.ca/other/Rigby2011ICSE.pdf

5 projects},
	pages = {541{\textendash}550},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software peer review has proven to be a successful technique in open source software (OSS) development. In contrast to industry, where reviews are typically assigned to specific individuals, changes are broadcast to hundreds of potentially interested stakeholders. Despite concerns that reviews may be ignored, or that discussions will deadlock because too many uninformed stakeholders are involved, we find that this approach works well in practice. In this paper, we describe an empirical study to investigate the mechanisms and behaviours that developers use to find code changes they are competent to review. We also explore how stakeholders interact with one another during the review process. We manually examine hundreds of reviews across five high profile OSS projects. Our findings provide insights into the simple, community-wide techniques that developers use to effectively manage large quantities of reviews. The themes that emerge from our study are enriched and validated by interviewing long-serving core developers.},
	keywords = {apache, case studies, email, freebsd, grounded theory, kde, linux, linux kernel, open source software, peer review, subversion},
	isbn = {978-1-4503-0445-0},
	doi = {10.1145/1985793.1985867},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Rigby2011ICSE.pdf},
	author = {Peter C. Rigby and Storey, Margaret-Anne}
}
@article {howison2010validity-issues,
	title = {Validity Issues in the Use of Social Network Analysis with Digital Trace data},
	journal = {Journal of the Association for Information Systems},
	volume = {12},
	year = {2011},
	chapter = {Article 2},
	abstract = {There is an exciting natural match between social network analysis methods and the growth of data sources produced by social interactions via information technologies, from online communities to corporate information systems. Information Systems researchers have not been slow to embrace this combination of method and data. Such systems increasingly provide "digital trace data" that provide new research opportunities. Yet digital trace data are substantively different from the survey and interview data for which network analysis measures and interpretations were originally developed. This paper examines ten validity issues associated with the combination of data digital trace data and social network analysis methods, with examples from the IS literature, to provide recommendations for improving the validity of research using this combination.},
	keywords = {information system, Online Communities, social network analysis, Virtuality},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HowisonSNADigitalTraceData-WorkingPaper.pdf},
	author = {Howison, James and Andrea Wiggins and Kevin Crowston}
}
@proceedings {1293,
	title = {Virtual Health Information Infrastructures: A Scalable Regional Model},
	year = {2011},
	month = {10/2011},
	pages = {316-319},
	publisher = {Springer},
	abstract = {Integrating research, education and evidence-based medical practice requires complex infrastructures and network linkages among these critical activities. This research examines communities of practice and open source software tools in development of scalable virtual infrastructures for the regional Virtual Health Library of the Latin American and Caribbean Health Sciences System (Bireme) and embedded national cases. Virtual infrastructures refer to an environment characterized by overlapping distribution networks accessible through Internet portals and websites designed to facilitate integrated use of available resources. Case analysis shows engagement of interdisciplinary communities of practice for scalable virtual infrastructure design. This research program considers theory and methods for study of transferability of the Latin American model to large health care systems in other cultures.},
	keywords = {Bireme, Communities Of Practice, culture, open source systems, virtual infrastructures},
	author = {Seror, Ann}
}
@conference {1305,
	title = {Visualizing collaboration and influence in the open-source software community},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"This data set includes the complete social graph of 500,000 follow links as well as over 1,000,000 commits and 50,000 users."

"...a large fraction of [GitHub] users provide a location in their profile, which we can turn into geographic coordinates using a geocoding API like PlaceFinder...

"For each repository, we extract the owner, collaborator, and contributor usernames, plus branch names. New user- names help to find new repositories, while branch names are used to fetch commit metadata. Using this method, the crawler uncovered 40,860 code repositories, representing 33,388 unique project names and 1,219,872 individual commits."

"In addition to crawled data, we use the complete GitHub user follower graph from Jan 19, 2011. This graph includes 452,248 links connecting 106,247 unique users, 47\% (49,500) of which could be geocoded with the PlaceFinder API"},
	month = {05/2011},
	pages = {223-226},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {We apply visualization techniques to user profiles and repository metadata from the GitHub source code hosting service. Our motivation is to identify patterns within this development community that might otherwise remain obscured. Such patterns include the effect of geographic distance on developer relationships, social connectivity and influence among cities, and variation in project-specific contribution styles (e.g., centralized vs. distributed). Our analysis examines directed graphs in which nodes represent users{\textquoteright} geographic locations and edges represent (a) follower relationships, (b) successive commits, or (c) contributions to the same project. We inspect this data using a set of visualization techniques: geo-scatter maps, small multiple displays, and matrix diagrams. Using these representations, and tools based on them, we develop hypotheses about the larger GitHub community that would be difficult to discern using traditional lists, tables, or descriptive statistics. These methods are not intended to provide conclusive answers; instead, they provide a way for researchers to explore the question space and communicate initial insights.},
	keywords = {COLLABORATION, data exploration, geography, geoscatter, github, graph, mapping, metadata, open source, social graph, user profiles, visualization},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985476},
	url = {http://vis.stanford.edu/files/2011-GotHub-MSR.pdf},
	author = {Marschner, Eli and Rosenfeld, Evan and Heer, Jeffrey and Heller, Brandon}
}
@proceedings {1269,
	title = {What kind of commons is free software?},
	year = {2011},
	note = {Available under a CreativeCommons BY-NC-SA license (http://creativecommons.org/licenses/by-nc-sa/3.0/). The presentation slides are also attached; paper{\textquoteright}s LaTeX source files can be found at http://www.mediafire.com/?7k9dxbkna0x6irl},
	month = {06/2011},
	address = {Berlin, Germany},
	abstract = {This paper analyzes free software under the light of commons theories, and tries to answer whether it is a managed or open access commons. It briefly presents commons studies and its main concepts, as well as the discussion on immaterial commons, arguing that goods{\textquoteright} intrinsic characteristics should not be viewed as absolute, but rather contextualized in social struggles. Then, it proposes a two-tier structure for analyzing free software as a commons, considering its dual nature as source and machine code. The two connected layers of the proposal - use and development - are characterized according to commons theory categories; Android and software forking are explored as examples. It concludes that the first layer resembles an open access commons, but with intensional boundaries, and that the second one resembles multiple managed commons. This disparity is associated with the category of nested enterprises and with the layers{\textquoteright} relations to appropriation and production.},
	keywords = {commons, COMMUNITY, free software, governance},
	issn = {1613-0073},
	url = {http://ceur-ws.org/Vol-739/paper_10.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/VIEIRA.pdf , https://flosshub.org/sites/flosshub.org/files/VIEIRA_presentation_0.odp},
	author = {Vieira, Miguel Said}
}
@conference {1311,
	title = {What topics do Firefox and Chrome contributors discuss?},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {234-237},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Firefox and Chrome are two very popular open source Web browsers, implemented in C/C++. This paper analyzes what topics were discussed in Firefox and Chrome bug reports over time. To this aim, we indexed the text contained in bug reports submitted each semester of the project history, and identified topics using Latent Dirichlet Allocation (LDA). Then, we investigated to what extent Firefox and Chrome developers/contributors discussed similar topics, either in different periods, or over the same period. Results indicate a non-negligible overlap of topics, mainly on issues related to page layouting, user interaction, and multimedia contents.},
	keywords = {bug reports, chrome, Firefox, LDA, msr challenge},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985480},
	author = {Zagarese, Quirino and Distante, Damiano and Di Penta, Massimiliano and Bernardi, Mario Luca and Sementa, Carmine}
}
@proceedings {1378,
	title = {When Cultures Clash: Participation in Open Source Communities and Its Implications For Organizational Commitment},
	number = {7},
	year = {2011},
	abstract = {Software applications developed within the OSS community have enjoyed tremendous success and for-profit organizations are keen to tap into this significant pool of software development talent (Chesbrough 2003; Feller et al. 2008). Examples companies include Netscape, IBM and Google (Maccormack et al. 2006). These companies seek to benefit from the talent of a global and sometimes voluntary workforce by paying some employees to contribute to OSS projects (Raymond 1999, Shah 2006). This merging of open and traditional software development may cause developer stress based on conflicting OSS community and traditional software development norms. Specifically, developers must balance company intellectual property concerns with the reciprocal and community-based norms that drive OSS development (Stewart and Gosain 2006). When these values are not in sync, contributors that aim to abide by conflicting values may exhibit dysfunctional attitudes. Employee stress with respect to their role can be destructive to organizational outcomes (Maas and Matejka 2009; Aranya and Ferris 1984). This study develops an OSS context specific model that describes the relationship between clashing software development cultures and employee organizational commitment. We leverage the rich OSS literature and the research that focuses on organizational-professional conflict (OPC) to develop hypotheses linking clashing cultures and organizational commitment. These hypotheses are tested using a combination of archival data and a survey of 127 GNOME developers. The findings presented in this paper contribute to OSS literature and offer findings that will enable organizations to more successfully engage OSS communities.},
	keywords = {gnome},
	url = { http://aisel.aisnet.org/icis2011/proceedings/projmanagement/7 },
	author = {Daniel, Sherae L. and Maruping, Likoebe M. and Cataldo, Marcelo and Herbsleb, James}
}
@article {1388,
	title = {Adoption of open source software in software-intensive organizations {\textendash} A systematic literature review},
	journal = {Information and Software Technology},
	volume = {52},
	year = {2010},
	month = {11/2010},
	pages = {1133 - 1154},
	abstract = {Context

Open source software (OSS) is changing the way organizations develop, acquire, use, and commercialize software.
Objective

This paper seeks to identify how organizations adopt OSS, classify the literature according to these ways of adopting OSS, and with a focus on software development evaluate the research on adoption of OSS in organizations.
Method

Based on the systematic literature review method we reviewed publications from 24 journals and seven conference and workshop proceedings, published between 1998 and 2008. From a population of 24,289 papers, we identified 112 papers that provide empirical evidence on how organizations actually adopt OSS.
Results

We show that adopting OSS involves more than simply using OSS products. We moreover provide a classification framework consisting of six distinctly different ways in which organizations adopt OSS. This framework is used to illustrate some of the opportunities and challenges organizations meet when approaching OSS, to show that OSS can be adopted successfully in different ways, and to organize and review existing research. We find that existing research on OSS adoption does not sufficiently describe the context of the organizations studied, and it fails to benefit fully from related research fields. While existing research covers a large number of topics, it contains very few closely related studies. To aid this situation, we offer directions for future research.
Conclusion

The implications of our findings are twofold. On the one hand, practitioners should embrace the many opportunities OSS offers, but consciously evaluate the consequences of adopting it in their own context. They may use our framework and the success stories provided by the literature in their own evaluations. On the other hand, researchers should align their work, and perform more empirical research on topics that are important to organizations. Our framework may be used to position this research and to describe the context of the organization they are studying.},
	keywords = {open source software, organizations, software development, Systematic literature review},
	issn = {09505849},
	doi = {10.1016/j.infsof.2010.05.008},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584910000972},
	author = {Hauge, {\O}yvind and Ayala, Claudia and Conradi, Reidar}
}
@article {1331,
	title = {An Analysis of the Adoption of Open Source Software by Local Public Administrations},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {1 - 29},
	abstract = {The wide diffusion of open source software (OSS) is driving discussion among scholars on a set of issues, including its adoption by public administrations (PA). Previous works discussed a few factors that drive the decision to adopt OSS and did not address the potential benefits in terms of e-government that OSS may bring to PA. This paper fills these gaps. The analysis is based on the Emilia-Romagna region of Italy and studies the adoption of software (both proprietary and open source) by local PA. The results show there is increased adoption of OSS in several different domains of application, both servers and desktop clients. Among the motivations to adopt OSS, dependence on software suppliers is important. Its adoption also positively affects the variety and extent of interactivity of local public e-services.},
	keywords = {government},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010070101},
	author = {Rentocchini, Francesco and Tartari, Dimitri}
}
@article {1382,
	title = {Analysis of virtual communities supporting OSS projects using social network analysis},
	journal = {Information and Software Technology},
	volume = {52},
	year = {2010},
	month = {3/2010},
	pages = {296 - 303},
	abstract = {This paper analyses the behaviour of virtual communities for Open Source Software (OSS) projects. The development of OSS projects relies on virtual communities, which are built on relationships among members, being their final objective sharing knowledge and improving the underlying project. This study addresses the interactive collaboration in these kinds of communities applying social network analysis (SNA). In particular, SNA techniques will be used to identify those members playing a middle-man role among other community members. Results will illustrate the importance of this role to achieve successful virtual communities.},
	keywords = {arm, email, Knowledge brokers, linux, mailing list, open source software, social network analysis, virtual communities},
	issn = {09505849},
	doi = {10.1016/j.infsof.2009.10.007},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584909001888},
	author = {Toral, S.L. and Mart{\'\i}nez-Torres, M.R. and Barrero, F.}
}
@conference {1256,
	title = {Analyzing Leadership Dynamics in Distributed Group Communication},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)},
	year = {2010},
	note = {"Our analysis examines the communication patterns in two FLOSS development projects, Fire and Gaim"
"These data were imported into a database to allow automated analysis. The Fire data set includes about 1,800 events in the user email list, 7,800 messages in the developer venues, and 1,300 events in the combined trackers, spanning a period of 54 months. The significantly larger Gaim data set included over 41,000 events in the user forum, over 30,000 events in the developer venues, and about 20,000 events in the trackers, generated over 78 months."
"The dynamic network analysis was performed using a scientific workflow tool, Taverna Workbench"},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {We apply social network analysis (SNA) to examine the dynamics of leadership in distributed groups, specifically Free/Libre Open Source Software development projects, and its relation to group performance. Based on prior work on leadership in distributed groups, we identify leaders with those who make the highest level of contribution to the group and assess the degree of leadership by measuring centralization of communications. We compare the dynamics of leadership in two FLOSS projects, one more and one less effective. We find that in both projects, centralization was higher in developer-oriented communications venues than in user-oriented venues, suggesting higher degrees of leadership in developer venues. However, we do not find a consistent relation between centralization and effectiveness. We suggest that SNA can instead be useful for identifying interesting periods in the history of the project, e.g., periods where the leadership of the project is in transition.},
	keywords = {core, DYNAMICS, email, email archives, fire, flossmole, gaim, leadership, mailing list, project success, social network analysis, srda},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.62},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-06-02.pdf},
	author = {Kevin Crowston and Andrea Wiggins and Howison, James}
}
@conference {957,
	title = {Assessment of issue handling efficiency},
	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 = {94 - 97},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {We mined the issue database of GNOME to assess how issues are handled. How many issues are submitted and resolved? Does the backlog grow or decrease? How fast are issues resolved? Does issue resolution speed increase or decrease over time? In which subproject are issues handled most efficiently? To answer such questions, we apply several visualization and quantification instruments to the raw issue data. In particular, we aggregate issues into four risk categories, based on their resolution time. These categories are the basis both for visualizing and ranking, which are used in concert for issue database exploration.},
	keywords = {bug reports, bug tracking, classification, gnome, msr challenge, visualization},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463292},
	attachments = {https://flosshub.org/sites/flosshub.org/files/94bluijtenMSR2010.pdf},
	author = {Luijten, Bart and Visser, Joost and Zaidman, Andy}
}
@article {1816,
	title = {Atratividade de projetos de software livre: import{\^a}ncia te{\'o}rica e estrat{\'e}gias para administra{\c c}{\~a}o},
	journal = {Revista de Administra{\c c}{\~a}o de Empresas},
	volume = {50},
	year = {2010},
	month = {2010},
	pages = {424 - 438},
	abstract = {Milhares de Projetos de Software Livre (PSL) foram e continuam sendo criados na Internet. Esse cen{\'a}rio aumenta as oportunidades de colabora{\c c}{\~a}o tanto quanto acirra a concorr{\^e}ncia por usu{\'a}rios e contribuidores, que elevariam esses projetos a n{\'\i}veis superiores aos que seriam alcan{\c c}ados por seus fundadores sozinhos. E dado que o aprimoramento por meio de colabora{\c c}{\~a}o {\'e} o principal objetivo dos fundadores de PSL, a import{\^a}ncia de entender e administrar a capacidade de atrair usu{\'a}rios e contribuidores fica estabelecida. Para auxiliar pesquisadores e fundadores nesse desafio, o conceito de atratividade {\'e} introduzido neste artigo, que desenvolve um ferramental te{\'o}rico-gerencial sobre as causas, indicadores e consequ{\^e}ncias da atratividade, viabilizando sua administra{\c c}{\~a}o estrat{\'e}gica.},
	keywords = {flossmole},
	doi = {10.1590/S0034-75902010000400007},
	author = {Santos Jr, Carlos Denner dos}
}
@conference {963,
	title = {Automated dependency resolution for open source software},
	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 = {130 - 140},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Opportunities for software reuse are plentiful, thanks in large part to the widespread adoption of open source processes and the availability of search engines for locating relevant artifacts. One challenge presented by open source software reuse is simply getting a newly downloaded artifact to build/run in the first place. The artifact itself likely reuses other artifacts, and so depends on their being located to function properly. While merely tedious in the individual case, this can cause serious difficulties for those seeking to study open source software. It is simply not feasible to manually resolve dependencies for thousands of projects, and many forms of analysis require declarative completeness. In this paper we present a method for automatically resolving dependencies for open source software. It works by cross-referencing a project{\textquoteright}s missing type information with a repository of candidate artifacts. We have implemented this method on top of the Sourcerer, an infrastructure for the large-scale indexing and analysis of open source code. The performance of our resolution algorithm was evaluated in two parts. First, for a small number of popular open source projects, we manually examined the artifacts suggested by our system to determine if they were appropriate. Second, we applied the algorithm to the 13,241 projects in the Sourcerer managed repository to evaluate the rate of resolution success. The results demonstrate the feasibility of this approach, as the algorithm located all of the required artifacts needed by 3,904 additional projects, increasing the percentage of declaratively complete projects in Sourcerer from 39\% to 69\%.},
	keywords = {dependencies, java, source code, sourcerer},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463346},
	author = {Ossher, Joel and Bajracharya, Sushil and Lopes, Cristina}
}
@conference {948,
	title = {Beyond replication: An example of the potential benefits of replicability in the mining of software repositories community},
	booktitle = {1st Workshop on Replication in Empirical Software Engineering Research},
	year = {2010},
	month = {05/2010},
	keywords = {literature review, msr, replication},
	author = {Gregorio Robles and Daniel M. German}
}
@conference {968,
	title = {Can development work describe itself?},
	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 = {191 - 200},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Work descriptions are informal notes taken by developers to summarize work achieved in a particular session. Existing studies indicate that maintaining them is a distracting task, which costs a developer more than 30 min. a day. The goal of this research is to analyze the purposes of work descriptions, and find out if automated tools can assist developers in efficiently creating them. For this, we mine a large dataset of heterogeneous work descriptions from open source and commercial projects. We analyze the semantics of these documents and identify common information entities and granularity levels. Information on performed actions, concerned artifacts, references and new work, shows the work management purpose of work descriptions. Information on problems, rationale and experience shows their knowledge sharing purpose. We discuss how work description information, in particular information used for work management, can be generated by observing developers{\textquoteright} interactions. Our findings have many implications for next generation software engineering tools.},
	keywords = {developer interactions, work descriptions},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463344},
	author = {Maalej, Walid and Happel, Hans-Jorg}
}
@conference {954,
	title = {Clones: What is that smell?},
	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 = {72 - 81},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Clones are generally considered bad programming practice in software engineering folklore. They are identified as a bad smell and a major contributor to project maintenance difficulties. Clones inherently cause code bloat, thus increasing project size and maintenance costs. In this work, we try to validate the conventional wisdom empirically to see whether cloning makes code more defect prone. This paper analyses relationship between cloning and defect proneness. We find that, first, the great majority of bugs are not significantly associated with clones. Second, we find that clones may be less defect prone than non-cloned code. Finally, we find little evidence that clones with more copies are actually more error prone. Our findings do not support the claim that clones are really a "bad smell". Perhaps we can clone, and breathe easy, at the same time.},
	keywords = {apache, bug fix revisions, bugs, clone, evolution, gimp, nautilus, scm, source code},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463343},
	attachments = {https://flosshub.org/sites/flosshub.org/files/72rahman2010cws.pdf},
	author = {Rahman, Foyzur and Christian Bird and Devanbu, Premkumar}
}
@conference {958,
	title = {Cloning and copying between GNOME projects},
	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 = {98 - 101},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {This paper presents an approach to automatically distinguish the copied clone from the original in a pair of clones. It matches the line-by-line version information of a clone to the pair{\textquoteright}s other clone. A case study on the GNOME Desktop Suite revealed a complex flow of reused code between the different subprojects. In particular, it showed that the majority of larger clones (with a minimal size of 28 lines or higher) exist between the subprojects and more than 60\% of the clone pairs can be automatically separated into original and copy.},
	keywords = {clone, gnome, msr challenge, source code},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463290},
	attachments = {https://flosshub.org/sites/flosshub.org/files/98Coning.pdf},
	author = {Krinke, Jens and Gold, Nicolas and Jia, Yue and Binkley, David}
}
@inbook {836,
	title = {Collaboration Practices and Affordances in Free/Open Source Software Development},
	booktitle = {Collaborative Software Engineering},
	year = {2010},
	pages = {307-328},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This chapter examines collaborative work practices, development processes, project and community dynamics, and other socio-technical relationships in free and open source software development (FOSSD). It also describes what kinds of collaboration affordances facilitate collaborative work in FOSSD projects. It reviews a set of empirical studies of FOSSD that articulate different levels of analysis. Finally, there is discussion of limitations and constraints in understanding what collaboration practices and affordances arise in FOSSD studies and how they work, and then to emerging opportunities for future FOSSD studies.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CoSE-Scacchi-Chapter.pdf},
	author = {Walt Scacchi},
	editor = {Finkelstein, A. and van der Hoek, A. and Grundy, J. and Mistr{\'\i}k, I. and Whitehead, J.}
}
@conference {960,
	title = {A comparative exploration of FreeBSD bug lifetimes},
	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 = {106 - 109},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {In this paper, we explore the viability of mining the basic data provided in bug repositories to predict bug lifetimes. We follow the method of Lucas D. Panjer as described in his paper, Predicting Eclipse Bug Lifetimes. However, in place of Eclipse data, the FreeBSD bug repository is used. We compare the predictive accuracy of five different classification algorithms applied to the two data sets. In addition, we propose future work on whether there is a more informative way of classifying bugs than is considered by current bug tracking systems.},
	keywords = {bug reports, bug tracking, classification, eclipse, msr challenge, prediction},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463291},
	attachments = {https://flosshub.org/sites/flosshub.org/files/106ChallengeGargi.pdf},
	author = {Bougie, Gargi and Treude, Christoph and Daniel M. German and Storey, Margaret-Anne}
}
@conference {1483,
	title = {Creating and evolving developer documentation},
	booktitle = {Proceedings of the eighteenth ACM SIGSOFT international symposium},
	year = {2010},
	pages = {127},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Santa Fe, New Mexico, USANew York, New York, USA},
	abstract = {Developer documentation helps developers learn frameworks and libraries. To better understand how documentation in open source projects is created and maintained, we performed a qualitative study in which we interviewed core contributors who wrote developer documentation and developers who read documentation. In addition, we studied the evolution of 19 documents by analyzing more than 1500 document revisions. We identified the decisions that contributors make, the factors influencing these decisions and the consequences for the project. Among many findings, we observed how working on the documentation could improve the code quality and how constant interaction with the projects{\textquoteright} community positively impacted the documentation.},
	isbn = {9781605587912},
	doi = {10.1145/1882291.1882312},
	author = {Dagenais, Barth{\'e}l{\'e}my and Robillard, Martin P.}
}
@article {1330,
	title = {Data Mining User Activity in Free and Open Source Software (FOSS)/ Open Learning Management Systems},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {65 - 75},
	abstract = {Free and Open Source Software (FOSS)/Open Educational Systems development projects abound in higher education today. Many universities worldwide have adopted open source software like ATutor and Moodle as an alternative to commercial or homegrown systems. The move to open source learning management systems entails many special considerations, including usage analysis facilities. The tracking of users and their activities poses major technical and analytical challenges within web-based systems. This paper examines how user activity tracking challenges are met with data mining techniques, particularly web usage mining methods, in four different open learning management systems: ATutor, LON-CAPA, Moodle, and Sakai. As examples of data mining technologies adapted within widely used systems, they represent important first steps for moving educational data mining outside the research laboratory. Moreover, as examples of different open source development contexts, exemplify the potential for programmatic integration of data mining technology processes in the future. As open systems mature in the use of educational data mining, they move closer to the long-sought goal of achieving more interactive, personalized, adaptive learning environments online on a broad scale.},
	keywords = {data mining, education, student},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010010105},
	author = {McGrath, Owen}
}
@article {1328,
	title = {Developing a Dynamic and Responsive Online Learning Environment},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {32 - 48},
	abstract = {Charles Stuart University adopted the open source software, Sakai, as the foundation for the university{\textquoteright}s new, integrated Online Learning Environment. This study explores whether a pedagogical advantage exists in adopting such an open source learning management system. Research suggests that the community source approach to development of open source software has many inherent pedagogical advantages, but this paper examines whether this is due to the choice of open source software or simply having access to appropriate technology for learning and teaching in the 21st century. The author also addresses the challenges of the project management methodology and processes in the large-scale implementation of an open-source courseware management solution at the institutional level. Consequently, this study outlines strategies that an institution can use to harness the potential of a community source approach to software development to meet the institutional and individual user needs into the future. },
	keywords = {education, learning, sakai},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010010103},
	author = {Buchan, Janet}
}
@conference {961,
	title = {Do stack traces help developers fix bugs?},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {118 - 121},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {A widely shared belief in the software engineering community is that stack traces are much sought after by developers to support them in debugging. But limited empirical evidence is available to confirm the value of stack traces to developers. In this paper, we seek to provide such evidence by conducting an empirical study on the usage of stack traces by developers from the ECLIPSE project. Our results provide strong evidence to this effect and also throws light on some of the patterns in bug fixing using stack traces. We expect the findings of our study to further emphasize the importance of adding stack traces to bug reports and that in the future, software vendors will provide more support in their products to help general users make such information available when filing bug reports.},
	keywords = {bug fixing, bug report, debugging, eclipse, stack trace},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463280},
	attachments = {https://flosshub.org/sites/flosshub.org/files/118-10-msr.pdf},
	author = {Schroter, Adrian and Schr{\"o}ter, Adrian and Bettenburg, Nicolas and Premraj, Rahul}
}
@inbook {springerlink:10.1007/978-3-642-13244-5_20,
	title = {Download Patterns and Releases in Open Source Software Projects: A Perfect Symbiosis?},
	booktitle = {Open Source Software: New Horizons},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {319},
	year = {2010},
	note = {"We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository."},
	pages = {252-267},
	publisher = {Springer Boston},
	organization = {Springer Boston},
	abstract = {Software usage by end-users is one of the factors used to evaluate the success of software projects. In the context of open source software, there is no single and non-controversial measure of usage, though. Still, one of the most used and readily available measure is data about projects downloads. Nevertheless, download counts and averages do not convey as much information as the patterns in the original downloads time series. In this research, we propose a method to increase the expressiveness of mere download rates by considering download patterns against software releases. We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository. Findings show that projects with similar usage can have indeed different levels of sensitivity to releases, revealing different behaviors of users. Future research will develop further the pattern recognition approach to automatically categorize open source projects according to their download patterns.},
	keywords = {flossmole, oss2010, sourceforge},
	url = {http://dx.doi.org/10.1007/978-3-642-13244-5_20},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s and Madey, Gregory and Noll, John}
}
@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}
}
@conference {959,
	title = {Finding file clones in FreeBSD Ports Collection},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {102 - 105},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {In Open Source System (OSS) development, software components are often imported and reused; for this reason we might expect that files are copied in multiple projects (file clones). In this paper, we propose a file clone detection tool called FCFinder and show the analysis performed with it on the FreeBSD Ports Collection, a large OSS project collection. We found many file clones among similar or related projects, which are systematically introduced from base projects.},
	keywords = {clone, freebsd, msr challenge, source code},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463293},
	attachments = {https://flosshub.org/sites/flosshub.org/files/102FreeBSDClones.pdf},
	author = {Sasaki, Yusuke and Yamamoto, Tetsuo and Hayase, Yasuhiro and Inoue, Katsuro}
}
@article {1134,
	title = {A Fistful of Dollars: Financial Rewards, Payment Norms, and Motivation Crowding in Open Source Software Development},
	year = {2010},
	month = {04/2010},
	institution = {ssrn},
	address = {ssrn},
	abstract = {Existing literature on open source software (OSS) maintains that intrinsic motivation and extrinsic financial rewards have a unidimensionally positive effect on the motivation of individual developers. Based on self-determination theory, which underlies most of these studies, we challenge this assumption. We argue that the effect of payment on both intrinsic motivation and total motivation of OSS developers is far more complex. To illustrate our point, we introduce the concept of individuals{\textquoteright} norms about payment to the field of OSS. In doing so, we are able to show that payment norms moderate the effect of payment on intrinsic motivation and total motivation. Conducting a scenario experiment, we find that intrinsic motivation decreases for individuals with norms against payment. This effect becomes even stronger when analyzing for mediation effects. Total motivation is impacted positively by payment, but the effect turns insignificant for individuals with norms for payment. Our findings help explain the results of previous studies in which OSS developers did not seem to be affected by motivation crowding. They further contribute to the more general debate on how to manage individuals in the absence of formal contracts. From a practical perspective, we show that financial rewards may create a management dilemma for OSS project leaders. },
	keywords = {developers, experiment, financial, MOTIVATION},
	author = {Oliver Alexy and Martin Leitner}
}
@conference {1221,
	title = {From Proprietary to Open Source: Building a Network of Trust},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	abstract = {When a corporation is about to release a product as open source a large network of trust must be built and maintained. Open source and commercial domains have radically different aspects of trust. Still, trust is vital in products survival in both settings. This paper focuses on building cognitive, or rational, trust in both commercial and open source domains. We set the view angle so that trust can be approached via the various relationships between the stakeholders involved in the community building process. Towards this goal, the paper focuses on the first steps of the process by proposing a set of best practices.},
	keywords = {oss2010, osscomm, workshop},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm001.pdf},
	author = {Sirkkala, Petri and Hammouda, Imed and Aaltonen, Timo}
}
@article {1335,
	title = {Helping to Bridge the Digital Divide with Free Software and Services},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {13 - 27},
	abstract = {The growing importance of digital media in citizens{\textquoteright} participation in government is a major issue in obtaining government services, elections and campaigning in the 21st century. In order to participate in the consumption and creation of online media, citizens must have access to, and knowledge of, appropriate technology resources. There exists a gap between those who have access to technology and those who do not A gap commonly referred to as the digital divide. While there are many different aspects to the digital divide one of them is access to the software necessary to participate in digital media. A potential solution to the software component of the digital divide is the use of open source software and free online services. Implementing these solutions can play a part in narrowing the digital divide and producing better informed citizens more capable of participating in the modern electoral process.},
	issn = {1942-3934},
	doi = {10.4018/IJOSSP.2010100102},
	author = {Caudill, Jason G.}
}
@article {1327,
	title = {Higher Education and FOSS for e-Learning},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {15 - 31},
	abstract = {This paper examines the paradox of FOSS adoption in U.S. institutions of higher education, where campus-wide deployment of FOSS for e-learning lags far behind adoption for technical infrastructure applications. Drawing on the fields of organizational management, information systems, and education, the author argues that the gap between FOSS advocacy and the enterprise-wide deployment of FOSS for e-learning is a consequence of the divergent perspectives of two organizational sub-cultures{\textemdash}the technologist and the academic{\textemdash}and the extent to which those sub-cultures are likely to embrace FOSS. The author recommends (a) collaborative needs analysis/assessment prior to a go/no go adoption decision, and (b) broad dissemination of total cost of ownership (TCO) data by institutions deploying FOSS for e-learning enterprise-wide. This discussion satisfies e-learning administrators and practitioners seeking research-based, cross-disciplinary evidence about the FOSS decision-making process and also assists educators seeking to expand student knowledge of e-learning technology options. },
	keywords = {education},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010010102},
	author = {Williams van Rooij, Shahron}
}
@conference {965,
	title = {Identifying licensing of jar archives using a code-search approach},
	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 = {151 - 160},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Free and open source software strongly promotes the reuse of source code. Some open source Java components/libraries are distributed as jar archives only containing the bytecode and some additional information. For whoever wanting to integrate this jar in her own project, it is important to determine the license(s) of the code from which the jar archive was produced, as this affects the way that such component can be used. This paper proposes an automatic approach to determine the license of jar archives, combining the use of a code-search engine with the automatic classification of licenses contained in textual flies enclosed in the jar. Results of an empirical study performed on 37 jars - from 17 different systems - indicate that this approach is able to successfully infer the jar licenses in over 95\% of the cases, but that in many cases the license in textual flies may differ from the one of the classes contained in the jar.},
	keywords = {apache, bytecode, classification, eclipse, google code, jar, java, licenses, source code},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463282},
	attachments = {https://flosshub.org/sites/flosshub.org/files/151msr2010.pdf},
	author = {Di Penta, Massimiliano and Daniel M. German and Antoniol, Giuliano}
}
@proceedings {1380,
	title = {The Impact of Person-Organization Fit on Turnover in Open Source Software Projects},
	number = {13},
	year = {2010},
	abstract = {Participant turnover in open source software development is a critical problem. Using Schneider{\textquoteright}s (1987) Attraction Selection and Attrition Framework and the notion of Person- Organization fit, we hypothesize about the relationship between a participant{\textquoteright}s fit with an open source project and turnover. Specifically we predict that value fit, needs-supplies fit and demandsabilities fit between a participant and a particular project will have a negative association with participant turnover and that the role of the participant in the project acts a moderator. An empirical study is designed to examine the hypotheses using a combination of survey and archival data. Since for-profit companies are increasingly leveraging open source software development, implications of our findings will be useful for project managers seeking to retain talented contributors in the absence of financial compensation.},
	url = {http://aisel.aisnet.org/icis2010_submissions/13},
	author = {Sharma, P.N. and Daniel, Sherae L. and Chung, Ting-Ting (Rachel)}
}
@article {1240,
	title = {Impact of Programming Language Fragmentation on Developer Productivity},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	month = {32/2010},
	pages = {41 - 61},
	abstract = {Programmers often develop software in multiple languages. In an effort to study the effects of programming language fragmentation on productivity{\textemdash}and ultimately on a developer{\textquoteright}s problem-solving abilities{\textemdash}the authors present a metric, language entropy, for characterizing the distribution of a developer{\textquoteright}s programming efforts across multiple programming languages. This paper presents an observational study examining the project contributions of a random sample of 500 SourceForge developers. Using a random coefficients model, the authors find a statistically (alpha level of 0.001) and practically significant correlation between language entropy and the size of monthly project contributions. Results indicate that programming language fragmentation is negatively related to the total amount of code contributed by developers within SourceForge, an open source software (OSS) community.},
	keywords = {commits, entropy, language entropy, programming languages, sourceforge, srda},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010040104},
	author = {Krein, Jonathan L. and MacLean, Alexander C. and Knutson, Charles D. and Delorey, Daniel P. and Eggett, Dennis L.}
}
@conference {1257,
	title = {The Importance of Social Network Structure in the Open Source Software Developer Community},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences},
	year = {2010},
	note = {"Using data from the SourceForge Research Data Archive [2, 9] and the new dataset of concurrent versions system (CVS) metadata described in [8]..." (M. Van Antwerp. Studying open source versioning metadata. Master{\textquoteright}s thesis, University of NotreDame, Notre Dame, IN, January 2009)
"To measure long-term popularity, we used the SourceForge activity percentile."},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {This paper outlines the motivations and methods for analyzing the developer network of open source software (OSS) projects. Previous work done by Hinds [5] suggested social network structure was instrumental towards the success of an OSS project, as measured by activity and output. The follow-up paper by Hinds [4] discovered that his hypotheses, based on social network theory and previous research on the importance of subgroup connectedness, were vastly different than the results of his study of over 100 successful OSS projects. He concluded that the social network structure had no significant effect on project success. We outline how his approach disregarded potentially important factors and through a new study evaluate the role of the OSS developer network as it pertains to long-term project popularity. We also present an initial investigation into the adequacy of using the SourceForge activity percentile as a long-term success metric. In contrast with Hinds, we show that previously existing developer-developer ties are an indicator of past and future project popularity.},
	keywords = {developers, popularity, project success, social network analysis, sourceforge, srda},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.385},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-06-07.pdf},
	author = {Matthew Van Antwerp and Madey, Greg}
}
@article {1744,
	title = {Investigating the Acquisition of Software Systems that Rely on Open Architecture and Open Source Software},
	year = {2010},
	abstract = {In 2007-08, we began an investigation of problems, issues, and opportunities that arise during the acquisition of software systems that rely on open architectures and open source software. The current effort funded for 2009 seeks to continue and build on the results in this area, while refining its focus to center on the essential constraints and tradeoffs we have identified for software-intensive systems with open architecture (OA) and continuously evolving open source software (OSS) elements. The U.S. Air Force, Army, and Navy have all committed to an open technology development strategy that encourages the acquisition of software systems whose requirements include the development or composition of an OA for such systems, and the use of OSS systems, components, or development processes when appropriate. Our goal is to further develop and document foundations for emerging policy and guidance for acquiring software systems that require OA and that incorporate OSS elements. This report documents and describes the findings and results that we have produced as a result of our research into the area of the acquisition of software systems that rely on OA and OSS. In particular, it includes four research papers that have been refereed, reviewed, presented, and published in national and international research conferences, symposia, and workshops.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/a530243.pdf},
	author = {Walt Scacchi and Alspaugh, Thomas and Hazeline U. Asuncion}
}
@unpublished {1242,
	title = {Investigating the Geography of Open Source Software through Github},
	year = {2010},
	note = {"We collected our data through Github{\textquoteright}s public API, which offers the same data as available on the Github{\textquoteright}s website but presents it in a structured format for simpler processing. The data were collected from May to July of 2010"

"The data collection followed a recursive procedure. We started with a single account, belonging to one of Github{\textquoteright}s founders. We then identified accounts connected to this user, then looked for accounts connected to the newly found ones, repeating this procedure until we achieved closure. New accounts were identified through the four kinds of connections mentioned in the previous section: (1) those that follow accounts collected earlier, (2) those followed by the accounts collected earlier, (3) those whose repositories were being {\textquotedblleft}watched{\textquotedblright} by accounts collected earlier, (4) those who had made code contributions to the repositories watched by accounts collected earlier."},
	abstract = {The paper presents an empirical study of the geography of open source software development that looks at Github, a popular project hosting website. We show that developers are highly clustered and concentrated primarily in North America and Western and Northern Europe, though a substantial minority is present in other regions. Code contributions and attention show a strong local bias. Users in North America account for a larger share of received contributions than of contributions made. They also receive a disproportionate amount of attention.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Takhteyev-Hilts-2010.pdf},
	author = {Yuri Takhteyev and Andrew Hilts}
}
@proceedings {1379,
	title = {Learning in Open Source Software (OSS) Development: How Developer Interactions in Culturally Diverse Projects Impact the Acquisition of Collaboration and Learning Skills},
	year = {2010},
	abstract = {Participants in an OSS/FLOSS development project often span national and organizational boundaries, as developers from different countries and corporations join the project. A project team{\textquoteright}s national and organizational culture creates opportunities for learning from others, but may also lead to conflict and inhibit learning. This research examines developers{\textquoteright} learning in an OSS project, and the cultural context in which learning takes place. We focus on single- and doubleloop learning and examine the impact of the team{\textquoteright}s national and organizational culture on a developer{\textquoteright}s learning. Archival and survey data are collected from two large-scale Sourceforge projects. This research can contribute to the OSS literature by examining the impact of team interactions on developers{\textquoteright} learning. Practically, administrators and managers stand to gain insight into the learning benefits of participation in OSS projects, and thus better assess their value as a training ground for global software development.},
	keywords = {sourceforge},
	url = {http://aisel.aisnet.org/icis2010_submissions/66/},
	author = {Diamant, I. and Daniel, S.L.}
}
@conference {1255,
	title = {{\textquoteright}Letting go of Control{\textquoteright} to Embrace Open Source: Implications for Company and Community},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)},
	year = {2010},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {It is increasingly understood across the information technology and services sector that engagement with the open source software model can serve as a means for firms to capture intellectual energy, learn about productive software processes, access relevant technical skills, identify and recruit staff, as well as obtain valuable resources including code. This paper reports a study undertaken within two large global IT companies that have been actively involved with open source for more than ten years. The study involved over 30 semi-structured interviews with employees of the companies drawn from top, middle, and lower level management, and included active and experienced developer as well as open source community members. Our findings indicate how these companies have adapted their day-to-day management practices to take into account the need for flexibility and freedom expected by open source communities. This paper focuses on how they {\textquoteright}let go of control{\textquoteright} and what the implications of this are for both companies and the communities involved. Our data reveals a number of themes and in this paper we focus on three principal ones; issues of requirements, total cost of adoption, and alignment of open source engagement with long term company strategy.},
	keywords = {adoption, companies, interviews, organizations},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-06-01.pdf},
	author = {Maha Shaikh and Cornford, Tony}
}
@conference {1359,
	title = {Linking e-mails and source code artifacts},
	booktitle = {Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - ICSE {\textquoteright}10},
	volume = {1},
	year = {2010},
	note = {"we devised a set of lightweight methods, based on regular expressions, to establish the link between e-mails and software artifacts. We evaluated them in terms of precision and recall considering one single Java system. In this paper we overcome a number of limitations of our previous work, resulting in the following contributions:
{\textbullet} An extensive and publicly available1 benchmark and toolset for recovering traceability links between e-mails and source code artifacts. We created our benchmark by analyzing the mailing lists of six different software systems written in four different programming languages. For each system we manually annotated a statistically significant number of e-mails.
{\textbullet} A comprehensive evaluation of linking techniques. We evaluated and compared, in terms of precision and recall, different linking methods, ranging from lightweight grep-style approaches to more complex approa- ches from the information retrieval (IR) field."},
	month = {05/2010},
	pages = {375-384},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Cape Town, South Africa},
	abstract = {E-mails concerning the development issues of a system constitute an important source of information about high-level design decisions, low-level implementation concerns, and the social structure of developers.

Establishing links between e-mails and the software artifacts they discuss is a non-trivial problem, due to the inherently informal nature of human communication. Different approaches can be brought into play to tackle this traceability issue, but the question of how they can be evaluated remains unaddressed, as there is no recognized benchmark against which they can be compared.

In this article we present such a benchmark, which we created through the manual inspection of a statistically significant number of e-mails pertaining to six unrelated software systems. We then use our benchmark to measure the effectiveness of a number of approaches, ranging from lightweight approaches based on regular expressions to full-fledged information retrieval approaches.},
	isbn = {9781605587196},
	doi = {10.1145/1806799.1806855},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	author = {Bacchelli, Alberto and Lanza, Michele and Robbes, Romain}
}
@conference {bird2010lee,
	title = {{Linkster: Enabling Efficient Manual Mining}},
	booktitle = {Demonstration Track, Proceedings of the 17th SIGSOFT Symposium on Foundations of Software Engineering},
	year = {2010},
	note = {"LINKSTER efficiently displays, integrates, and allows inspection and annotation of information from three main sources of data: source code repositories, developer mailing lists archives, and bug tracking databases. LINKSTER requires access to a source code repository for file content and a database which contains the raw mined repository, mailing list, and bug tracking information. All notes and annotations made by the user are also recorded in the database."},
	publisher = {ACM},
	organization = {ACM},
	abstract = {While many uses of mined software engineering data are automatic in nature, some techniques and studies either require, or can be improved, by manual methods. Unfortunately, manually inspecting, analyzing, and annotating mined data can be difficult and tedious, especially when information from multiple sources must be integrated. Oddly, while there are numerous tools and frameworks for automatically mining and analyzing data, there is a dearth of tools which facilitate manual methods. To fill this void, we have developed LINKSTER, a tool which integrates data from bug databases, source code repositories, and mailing list archives to allow manual inspection and annotation. LINKSTER has already been used successfully by an OSS project lead to obtain data for one empirical study.},
	keywords = {artifacts, bug, bug tracking, data mining, email, mailing lists, open source, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2010lee.pdf},
	author = {Christian Bird and Adrian Bachman and Rahman, Foyzur and Bernstein, Abraham}
}
@conference {1218,
	title = {A Longitudinal Study on Collaboration Networks and Decision to Participate in a FLOSS Community},
	booktitle = {5th Workshop on Public Data about Software Development (WoPDaSD 2010)},
	year = {2010},
	note = {"we chose as a case of study Epiphany, which is the default web browser of the GNOME graphical desktop environment"

"We collected all relevant data by parsing all the bug reports in GNOME Bugzilla repository relative to Epiphany. The data collection and storing was done using Bicho (v. 0.4 rev. 7198), a software part of the FLOSSMetric project [14]."},
	abstract = {In this paper we conjecture that individual decisions of FLOSS (Free/Libre Open Source Software) developers to take on a task are influenced by network relations generated by collaboration among project members. In order to explore our conjecture we collected data on a FLOSS project team consisting of 227 developers committed since 2002 to the development of a web browser. We reconstructed 2-mode co- collaboration networks (software developer by bug) in which a tie represents an action taken by a developer in order to solve a specific bug. Co-collaboration networks were collected at five points in time during a six-month development cycle of the software. We report and discuss results of longitudinal actor-based modeling that we specify to test for the influence of local network structures on developer{\textquoteright}s decision to take action on a specific bug. The study controls for bug-specific and developer-specific characteristics that may also affect developers{\textquoteright} decisions exogenously. We also control for priority and severity levels assigned by the team to bugs in an attempt to manage voluntary contribution.},
	keywords = {bicho, bug fixing, bug reports, bugzilla, COLLABORATION, developers, epiphany, flossmetrics, gnome, social network analysis},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd002.pdf},
	author = {Guido Conaldi and Tonellato, Marco}
}
@conference {837,
	title = {Lurking? Cyclopaths? A Quantitative Lifecyle Analysis of User Behavior in a Geowiki},
	booktitle = {ACM Conference on Computer-Human Interaction (CHI)},
	year = {2010},
	month = {04/2010},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Atlanta, GA},
	keywords = {content,, geographic, geowiki,, information,, lurking, open, volunteer, volunteered, Wiki,, work,},
	author = {Panciera, K. and Priedhorsky, R. and Erickson, T. and Terveen, L.}
}
@conference {956,
	title = {Mining security changes in FreeBSD},
	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 = {90 - 93},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Current research on historical project data is rarely touching on the subject of security related information. Learning how security is treated in projects and which parts of a software are historically security relevant or prone to security changes can enhance the security strategy of a software project. We present a mining methodology for security related changes by modifying an existing method of software repository analysis. We use the gathered security changes to find out more about the nature of security in the FreeBSD project and we try to establish a link between the identified security changes and a tracker for security issues (security advisories). We give insights how security is presented in the FreeBSD project and show how the mined data and known security problems are connected.},
	keywords = {freebsd, msr challenge, security},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463289},
	author = {Mauczka, Andreas and Schanes, Christian and Fankhauser, Florian and Bernhart, Mario and Grechenig, Thomas}
}
@conference {964,
	title = {Mining subclassing directives to improve framework reuse},
	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 = {141 - 150},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {To help developers in using frameworks, good documentation is crucial. However, it is a challenge to create high quality documentation especially of hotspots in white-box frameworks. This paper presents an approach to documentation of object-oriented white-box frameworks which mines from client code four different kinds of documentation items, which we call subclassing directives. A case study on the Eclipse JFace user-interface framework shows that the approach can improve the state of API documentation w.r.t. subclassing directives.},
	keywords = {api, documentation, eclipse, frameworks, jface, source code},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463347},
	attachments = {https://flosshub.org/sites/flosshub.org/files/141Mining-Subclassing-Directives-to-Improve-Framework-Reuse.pdf},
	author = {Bruch, Marcel and Mezini, Mira and Monperrus, Martin}
}
@conference {1224,
	title = {On the Need for OSS Patch Contribution Tools},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	abstract = {Open Source Software (OSS) projects and systems have become significant parts of the software economy. The sustainability of an OSS project depends largely on community contributions. The patch contribution process is important to OSS projects. Nevertheless, there are several issues negatively impacting patch contribution in mature OSS projects. These issues can be addressed by improving tools to support the patch contribution process.},
	keywords = {apache, kanban, patch, patch acceptance, patches},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm004.pdf},
	author = {Bhuricha Deen Sethanandha and Bart Massey and William Jones}
}
@conference {Oezbek:2010:OCS:1833272.1833274,
	title = {The onion has cancer: some social network analysis visualizations of open source project communication},
	booktitle = {Proceedings of the 3rd International Workshop on Emerging Trends in Free/Libre/Open Source Software Research and Development (FLOSS {\textquoteright}10)},
	series = {FLOSS {\textquoteright}10},
	year = {2010},
	note = {paper d/l from www.inf.fu-berlin.de/~oezbek/pub/OezThiPre10-SNA.pdf

"We study the introduction of process innovations in Open Source projects [33] by manually extracting innovation episodes from arch- ives of mailing-lists and analyzing these episodes qualitatively by the Grounded Theory Method [38]."

"we took all messages from the mailing-list archives in 2007 of the projects we were studying, turned each participant into a node (unifying multi- ple e-mail addresses where needed [6]), and computed relationship strength between A and B as the number of e-mails that are a reply of B to a message from A or vice versa, according to the in-reply-to header of the e-mail."

Our data set covers 11 of the 13 projects (from 7 different do- mains, selected from mailing-list archive Gmane to build a diverse set of projects) for which we analyzed innovation episodes. They include three workflow applications (Bugzilla, Flyspray, Request Tracker), two desktop environments (Rox, Xfce), two design tools (ArgoUML, a UML CASE tool; gEDA, a set of electronic design automation tools), one bootloader (Grub), one hardware emulator (Bochs), one operating system (FreeDOS), and one database man- agement system (MonetDB).},
	pages = {5{\textendash}10},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Background: People contribute to OSS projects in wildly different degrees, from reporting a single defect once and never coming back to spending many hours each workday on the project over several years - or anything in between. It is a common conception that these degrees of participation sort the participants into a number of similar groups which are layered like the peels of an onion: The onion model. Objective: We check whether this model of gradually different degrees of participation is valid with respect to the participation in OSS project mailing-list traffic. Methods: We perform social network analysis based on replies to mailing-list messages and use visualization to check the nature of three different groups of participants. Results: There appears to be a discontinuity with respect to core members: The degree to which very active core members (as opposed to less active co-developers) react to e-mails of senders from the project{\textquoteright}s periphery is significantly higher than would be expected from their level of activity in general. Limitations: The effect might be an artifact of the assumption that each mailing-list message can be treated the same. Conclusions: We conclude that core member status may be qualitatively (rather than just quantitatively) different and the transition of individual mailing-list participants towards ever higher participation is qualitatively discontinuous.},
	keywords = {argouml, Bochs, bugzilla, communication structure, Flyspray, gEDA, Grub, MonetDB, open source process, request tracker, Rox, social network analysis, Xfce},
	isbn = {978-1-60558-978-7},
	doi = {10.1145/1833272.1833274},
	url = {http://doi.acm.org/10.1145/1833272.1833274},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OezThiPre10-SNA.pdf},
	author = {Oezbek, Christopher and Prechelt, Lutz and Thiel, Florian}
}
@conference {Hissam,
	title = {On Open and Collaborative Software Development in the DoD},
	booktitle = {Seventh Annual Acquisition Research Symposium, {NPS} Proceedings -},
	volume = {1},
	number = {1},
	year = {2010},
	month = {04/2010},
	pages = {219{\textendash}235},
	publisher = {Naval Postgraduate School},
	organization = {Naval Postgraduate School},
	address = {Monterey, California},
	abstract = {The US Department of Defense (specifically, but not limited to, the DoD CIO{\textquoteright}s Clarifying Guidance Regarding Open Source Software, DISA{\textquoteright}s launch of Forge.mil and OSD{\textquoteright}s Open Technology Development Roadmap Plan) has called for increased use of open source software and the adoption of best practices from the free/open source software (F/OSS) community to foster greater reuse and innovation between programs in the DoD. In our paper, we examine some key aspects of open and collaborative software development inspired by the success of the F/OSS movement as it might manifest itself within the US DoD. This examination is made from two perspectives: the reuse potential among DoD programs sharing software and the incentives, strategies and policies that will be required to foster a culture of collaboration needed to achieve the benefits indicative of F/OSS. Our conclusion is that to achieve predictable and expected reuse, not only are technical infrastructures needed, but also a shift to the business practices in the software development and delivery pattern seen in the traditional acquisition lifecycle is needed. Thus, there is potential to overcome the challenges discussed within this paper to engender a culture of openness and community collaboration to support the DoD mission.},
	keywords = {collaborative development, open source software, reuse, software engineering},
	url = {http://www.acquisitionresearch.net/cms/_files/FY2010/NPS-AM-10-037.pdf},
	author = {Hissam, S. A. and Weinstock, C. and Bass, L.}
}
@article {1334,
	title = {Open Educational Resources in E-Learning},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {1 - 12},
	abstract = {According to Dr. B.R. Ambedkar{\textquoteright}s definition (Deshpande \& Mugridge, 1994), Open Educational Resources (OER) are based on the philosophical view of knowledge as a collective, social product. In the last years the relevance of OER has been widely acknowledged and a high magnitude impact is to be expected for OER in the near future (Atkins et al, 2007), (Wiley \& Gurrell, 2009), especially as a masterpiece in e-learning development. The aim of this chapter is to present an overview of OER in e-learning, focused on two fundamental aspects: (i) technical issues, mainly standards, and (ii) socio-economic and legal questions. This way the chapter deals with the most relevant issues in this matter: Which is the OER{\textquoteright}s role in education, especially for e-learning performance? Which are the technical resources and current standards needed for them? Which socio-economics and legal aspects influence the diffusion and use of OER?},
	issn = {1942-3934},
	doi = {10.4018/IJOSSP.2010100101},
	author = {Rejas-Muslera, Ricardo J. and Garc{\'\i}a-Tejedor, Alvaro J. and Rodriguez, Olga Pe{\~n}alba}
}
@article {1329,
	title = {Open for Social},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {49 - 64},
	abstract = {Online learning in K-12 and higher education has been growing rapidly, and open source software has the potential to improve the quality of e-learning. This paper describes how FOSS enables turning e-learning from a potentially restrictive framing of the education experience to an emergent and social experience. The authors identify several key elements of the FOSS model that position open source initiatives to contribute to the emergent and social nature of experience in e-learning. The authors also describe several challenges to developing FOSS in a community of educators for e-learning. These elements and challenges are illustrated in a brief case report about the development of an open source software system called Context-aware Activity Notification System (CANS). CANS (http://cansaware.com) is a notification system that integrates with collaborative work and learning systems and is designed around the importance of awareness of user activity, a user{\textquoteright}s social context and personal notification preferences. },
	keywords = {education},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010010104},
	author = {Laffey, James and Schmidt, Matthew and Amelung, Christopher}
}
@article {1337,
	title = {Open Scientific Entrepreneurship},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {48 - 66},
	abstract = {The objective of this article is to conceptually transfer the concept of open source software (OSS) development to scientific entrepreneurship and to hypothetically discuss the support potentials of this rather new development philosophy for what we than call open scientific entrepreneurship. Therefore, at first the authors will go into conceptual details of scientific entrepreneurship and than of OSS development. Following, the main thrust of the article presents open scientific entrepreneurship from two points of origin: first of all, OSS development as a specific form of scientific e-entrepreneurship and further on potential benefits of opening {\textquotedblleft}traditional{\textquotedblright} scientific entrepreneurship up by looking at specific action fields. These action fields are theoretically based on the process and competence perspective of scientific entrepreneurship. Finally, the general benefits as well as downsides of the concept of openness are discussed on a generic level. It becomes obvious that there is need for balancing the tensions between an open and closed design pattern for scientific entrepreneurship with a general emphasis on the open design perspective.},
	issn = {1942-3934},
	doi = {10.4018/IJOSSP.2010100104},
	author = {von Kortzfleisch, Harald and Schaarschmidt, Mario and Magin, Philipp}
}
@article {1333,
	title = {Open Source Adoption Index},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {48 - 60},
	abstract = {This paper reports the preliminary results of a study conducted to assess and quantify the adoption of Free/Open Source Software (FOSS) by organisations and enterprises. While almost all organisations use FOSS in some form today, there is a wide variation in the manner and extent to which they do so, and presently no quantitative measure exists that can capture the true picture. The present work has built a model with two sets of parameters that, when fed with relevant data about an organisation, generates a single number, the FOSS Adoption Index (FAI), for that organisation. The index is so defined that the higher its value for an organisation, the greater is the extent of FOSS adoption in that organisation. Beyond the single measure FAI that gives a coarse assessment, the model also allows drilling down to finer levels of granularity that provides deeper insights into the status and role of FOSS within a given organisation. Primary data collected for two classes of organisations through questionnaire based surveys and interviews have been used to demonstrate the working of the model as well as its potential usefulness for real world situations.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010070103},
	author = {Saini, Sanjeev K. and Krishnan, C. N. and Rajaram, L. N.}
}
@book {1249,
	title = {Open Source Software Developer and Project Networks},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: New Horizons},
	volume = {319},
	year = {2010},
	note = {no information on data gathering procedures},
	pages = {407 - 412},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {This paper outlines complex network concepts and how social networks are built from Open Source Software (OSS) data. We present an initial study of the social networks of three different OSS forges, BerliOS Developer, GNU Savannah, and SourceForge. Much research has been done on snapshot or conflated views of these networks, especially SourceForge, due to the size of the SourceForge community. The degree distribution, connectedness, centrality, and scale-free nature of SourceForge has been presented for the network at particular points in time. However, very little research has been done on how the network grows, how connections were made, especially during its infancy, and how these metrics evolve over time. },
	keywords = {berlios, savannah, sourceforge},
	isbn = {978-3-642-13244-5},
	issn = {1861-2288},
	doi = {10.1007/978-3-642-13244-5_39},
	author = {Madey, G. and van Antwerp, M.},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Madey, Gregory R. and Noll, John}
}
@article {1336,
	title = {Open Source Software Systems},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {28 - 47},
	abstract = {Complex software systems and the huge amounts of data they produce are becoming an integral part of our organizations. We are also becoming increasingly dependent on high quality software products in our everyday lives. These systems {\textquoteleft}evolve{\textquoteright} as we identify and correct existing defects, provide new functionalities, or increase their nonfunctional qualities - such as security, maintainability, performance, etc. Simultaneously, more software development projects are distributed over multiple locations (often globally) and are often several millions of dollars in development costs. Consequently, as the Internet continually eliminates geographic boundaries, the concept of doing business within a single country has given way to companies focusing on competing in an international marketplace. The digitalization of work and the reorganization of work processes across many organizations have resulted in routine and/or commodity components being outsourced.},
	issn = {1942-3934},
	doi = {10.4018/IJOSSP.2010100103},
	author = {Lenin, R. B. and Ramaswamy, S. and Yu, Liguo and Govindan, R. B.}
}
@conference {962,
	title = {OSS developers context-specific Preferred Representational systems: A initial Neurolinguistic text analysis of the Apache mailing list},
	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 = {126 - 129},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Open Source Software (OSS) mailing lists are used by developers to discuss software engineering tasks performed in the project. In the last years, researchers have been conducting mailing lists linguistic analyses for understanding the intricacies of OSS development. An unpublished approach for that is to use NeuroLinguistic Theory (NT). NT postulates the use of a Preferred Representational cognitive System (PRS) in specific contexts. This means that different resources and cognitive channels are used by developers in order to understand software, but what types of representational systems are the preferred by software engineers? This paper introduces a psychometrically-based neuro-linguistic analysis tool to classify developers, and presents early results of an experiment to assess the PRS of four top developers against a baseline of the Apache server mailing list.},
	keywords = {apache, email, email archives, mailing lists, neurolinguistics},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463339},
	author = {Junior, Methanias Colaco and Mendonca, Manoel and Farias, Mario and Henrique, Paulo}
}
@conference {835,
	title = {Paying attention to each other in visible work communities: Modeling bursty systems of multiple activity streams},
	booktitle = {SocialCom/PASSAT(2010)},
	year = {2010},
	note = {Uses open source projects to study, but this is not about open source, per se.},
	month = {2010},
	pages = {276-281},
	abstract = {Online work projects, from open source to wikipedia, have emerged as an important phenomenon. These communities offer exciting opportunities to investigate social processes because they leave traces of their activity over time. Unlike traditional work teams, the participants in these communities are widely dispersed and work without centralized management. The question arises, then, as to the extent to which these are in fact communities: is the group simply the sum of the individuals that make it up, or does the group function as a social unit? We explore this question in the temporal domain.
We argue that the rapid visibility of others{\textquoteright} work afforded by the information systems used by these projects reaches out and attracts the attention of others who are peripherally aware of the group{\textquoteright}s online space, prompting them to begin or intensify their participation, binding separate individual streams of activity into a social entity.

Previous work has suggested that for certain types of bursty social behavior (e.g. email), the frequency of the behavior is not homogeneously distributed but rather can be divided into two generative mechanisms: active sessions and passive background participation. We extend this work for the case of multiple conditionally independent streams of behavior, where each stream is generated by these two generative mechanisms. Our model can characterized by a double-chain hidden Markov model, allowing efficient inference using expectation-maximization. We apply this model to visible work communities by modeling each participant as a single stream of behavior, assessing transition probabilities between active sessions of different participants. This allows us to examine the extent to which the various members of the community are influenced by the active participation of others. Our results indicate that an active session by a participant at least triples the likelihood of another participant beginning an active session.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/olson2010paying-attentio.pdf},
	author = {Olson, Jamie F and Howison, James and Carley, Kathleen}
}
@conference {955,
	title = {Perspectives on bugs in the Debian bug tracking system},
	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 = {86 - 89},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Bugs in Debian differ from regular software bugs. They are usually associated with packages, instead of software modules. They are caused and fixed by source package uploads instead of code commits. The majority are reported by individuals who appear in the bug database once, and only once. There also exists a small group of bug reporters with over 1,000 bug reports each to their name. We also explore our idea that a high bug-frequency for an individual package might be an indicator of popularity instead of poor quality.},
	keywords = {bug reports, debian, msr challenge, popularity},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463288},
	attachments = {https://flosshub.org/sites/flosshub.org/files/86bugs-debian.pdf},
	author = {Davies, Julius and Hanyu Zhang and Nussbaum, Lucas and Daniel M. German}
}
@conference {949,
	title = {Predicting the severity of a reported bug},
	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 = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {The severity of a reported bug is a critical factor in deciding how soon it needs to be fixed. Unfortunately, while clear guidelines exist on how to assign the severity of a bug, it remains an inherent manual process left to the person reporting the bug. In this paper we investigate whether we can accurately predict the severity of a reported bug by analyzing its textual description using text mining algorithms. Based on three cases drawn from the open-source community (Mozilla, Eclipse and GNOME), we conclude that given a training set of sufficient size (approximately 500 reports per severity), it is possible to predict the severity with a reasonable accuracy (both precision and recall vary between 0.65-0.75 with Mozilla and Eclipse; 0.70-0.85 in the case of GNOME).},
	keywords = {bug reports, eclipse, gnome, mozilla, severity, text mining},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463284},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1lamkanfiDemeyer1.pdf},
	author = {Lamkanfi, Ahmed and Demeyer, Serge and Giger, Emanuel and Goethals, Bart}
}
@article {1558,
	title = {Proposed Application of Data Mining Techniques for Clustering Software Projects},
	journal = {INFOCOMP Special Edition},
	year = {2010},
	note = {"Using data available on the web, mainly in software
repositories, a collaborative project called FLOSSmole
was created to collect, share, and store comparable data
and analysis of the FLOSS development for academic
research. The project is based on continuous data collection
and analysis efforts of many research groups,
reducing duplication and promoting compatibility both
in the data sources of FLOSS software, as well as in research
and analysis [6]. In the FLOSSmole project, data
was collected in different software repositories. This
data was stored in relational databases (SQL), and available
on FLOSSmole Project website [2]. For this study,
we used the database collected from SourceForge repository,
as they are the largest repository of projects today,
and it is well known among developers."

},
	pages = {43-48},
	abstract = {Software projects always generate a lot of data, ranging from informal documentation to a database with thousands of lines of code. This information extracted from software projects takes even greater when it comes to OSS (Open Source Software). Such data may include source code base, historical change in the software, bug reports, mailing lists, among others. Using data mining techniques, we can extract valuable knowledge of this set of in formation, thus providing improvements throughout the process of software development. The results can be used to improve the quality of software, or even to manage the project in order to obtain maximum efficiency. This article proposes the application of data mining techniques to cluster software projects, cites the advantages that can be obtained with these techniques, and illustrates the application of data mining in a Open Source Software database},
	keywords = {flossmole},
	attachments = {https://flosshub.org/sites/flosshub.org/files/art06.pdf},
	author = {Rezende, Henrique Ribiero and Esmin, Ahmed Ali Abdalla}
}
@conference {Wiggins:2010,
	title = {Reclassifying Success and Tragedy in {FLOSS} Projects},
	booktitle = {Proceedings of the International Conference on Open Source Systems (OSS)},
	year = {2010},
	month = {31 May{\textendash}2 June},
	address = {Notre Dame, IN, USA},
	abstract = {This paper presents the results of a replication of English \& Schweik{\textquoteright}s 2007 paper classifying FLOSS projects according to their stage of growth and indicators of success. We recreated the analysis using a comparable data set from 2006, with one additional point in time. We also expanded upon the original results by applying different criteria for evaluating the rate of new software releases for sustainability of project activity. We discuss the points of convergence and divergence from the original work from these extensions of the classification, and their implications for studying FLOSS development using archival data. The paper contributes new analysis of operationalizing success in FLOSS projects, with discussion of implications of the findings.},
	keywords = {FLOSS},
	author = {Andrea Wiggins and Kevin Crowston}
}
@conference {966,
	title = {Replaying IDE interactions to evaluate and improve change prediction approaches},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {161 - 170},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Change prediction helps developers by recommending program entities that will have to be changed alongside the entities currently being changed. To evaluate their accuracy, current change prediction approaches use data from versioning systems such as CVS or SVN. These data sources provide a coarse-grained view of the development history that flattens the sequence of changes in a single commit. They are thus not a valid basis for evaluation in the case of development-style prediction, where the order of the predictions has to match the order of the changes a developer makes. We propose a benchmark for the evaluation of change prediction approaches based on fine-grained change data recorded from IDE usage. Moreover, the change prediction approaches themselves can use the more accurate data to fine-tune their prediction. We present an evaluation procedure and use it on several change prediction approaches, both novel and from the literature, and report on the results.},
	keywords = {cbse, change based software evolution, change prediction, changes, commit, cvs, development history, eclipseeye, ide, mylyn, spyware, svn},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463278},
	attachments = {https://flosshub.org/sites/flosshub.org/files/161Robbes2010changePrediction.pdf},
	author = {Robbes, Romain and Pollet, Damien and Lanza, Michele}
}
@conference {947,
	title = {Replicating MSR: A study of the potential replicability of papers published in the Mining Software Repositories proceedings},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {171 - 180},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {This paper is the result of reviewing all papers published in the proceedings of the former International Workshop on Mining Software Repositories (MSR) (2004-2006) and now Working Conference on MSR (2007-2009). We have analyzed the papers that contained any experimental analysis of software projects for their potentiality of being replicated. In this regard, three main issues have been addressed: i) the public availability of the data used as case study, ii) the public availability of the processed dataset used by researchers and iii) the public availability of the tools and scripts. A total number of 171 papers have been analyzed from the six workshops/working conferences up to date. Results show that MSR authors use in general publicly available data sources, mainly from free software repositories, but that the amount of publicly available processed datasets is very low. Regarding tools and scripts, for a majority of papers we have not been able to find any tool, even for papers where the authors explicitly state that they have built one. Lessons learned from the experience of reviewing the whole MSR literature and some potential solutions to lower the barriers of replicability are finally presented and discussed.},
	keywords = {data, literature review, msr, replication},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463348},
	url = {http://gsyc.urjc.es/~grex/msr2010},
	attachments = {https://flosshub.org/sites/flosshub.org/files/171MSR_2010_69.final_.pdf},
	author = {Gregorio Robles}
}
@article {1219,
	title = {Repositories with Public Data about Software Development},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	month = {04/2010},
	pages = {1 - 13},
	abstract = {Empirical research on software development based on data obtained from project repositories and code forges is increasingly gaining attention in the software engineering research community. The studies in this area typically start by retrieving or monitoring some subset of data found in the repository or forge, and this data is later analyzed to find interesting patterns. However, retrieving information from these locations can be a challenging task. Meta-repositories providing public information about software development are useful tools that can simplify and streamline the research process. Public data repositories that collect and clean the data from other project repositories or code forges can help ensure that research studies are based on good quality data. This paper provides some insight as to how these meta-repositories (sometimes called a {\textquotedblleft}repository of repositories{\textquotedblright}, RoR) of data about open source projects should be used to help researchers. This paper describes in detail two of the most widely used collections of data about software development: FLOSSmole and FLOSSMetrics.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010040101},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ijossp2010.pdf},
	author = {Jesus M. Gonzalez-Barahona and Izquierdo-Cortazar, Daniel and Squire, Megan}
}
@conference {1222,
	title = {Responsiveness as a measure for assessing the health of OSS ecosystems},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	note = {"Data was collected from the GMANE (gmane.org) archives of the SourceForge {\textquotedblleft}Nagios-devel{\textquotedblright} mailing list for the period from January 2004 to October 2009". response time, responsiveness. "},
	month = {05/2010},
	abstract = {The health of an Open Source ecosystem is an important decision factor when considering the adoption of Open Source software or when monitoring a seeded Open Source project. In this paper we introduce responsiveness as a qualitative measure of the quality of replies within mailing lists, which can be used for assessing ecosystem health. We consider one specific metric of responsiveness in this paper, and that is the response time of follow-up messages in mailing lists. We also describe a way for characterising the nature of communication in messages with short and long response times. The approach is tested in the context of the Nagios project, and we particularly focus on the responsiveness for contributors acting in their professional roles as core developers. Our contribution is a step towards a deeper understanding of voluntary support provided in mailing lists of OSS projects.},
	keywords = {email, email archives, gmane, mailing lists, nagios, response time, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm002.pdf},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn and Lings, Brian}
}
@conference {1220,
	title = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	abstract = {The Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010) aims at building a commu- nity of researchers and practitioners to share experiences and discuss chal- lenges involved in building and maintaining open source communities. De- tailed	information	regarding	the	workshop	is	available	at http://tutopen.cs.tut.fi/oscomm10/.},
	keywords = {oscomm, oscomm2010, oss2010, workshop},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm000.pdf},
	author = {Hammouda, Imed and Aaltonen, Timo and Capiluppi, Andrea}
}
@conference {967,
	title = {Should I contribute to this discussion?},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {181 - 190},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town},
	abstract = {Development mailing lists play a central role in facilitating communication in open source projects. Since these lists frequently host design and project discussions, knowledgeable contribution to these discussion threads is essential to avoid mis-communication that might slow-down the progress of a project. However, given the sheer volume of emails on these lists, it is easy to miss important discussions. To find out how developers are able to deal with mailing list discussions, we study the main factors that encourage developers to contribute to the development mailing lists. We develop personalized models to automatically identify discussion threads that a developer would contribute to based on his previous contribution behavior. Case studies on development mailing lists of three open source projects (Apache, PostgreSQL and Python) show that the average accuracy of our models is 89-85\% and that the models vary significantly between different developers.},
	keywords = {apache, contributions, developers, email, email archives, mailing lists, postgresql, python},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463345},
	attachments = {https://flosshub.org/sites/flosshub.org/files/181ibrahim-msr2010.pdf},
	author = {Ibrahim, Walid M and Bettenburg, Nicolas and Shihab, Emad and Adams, Bram and Hassan, Ahmed E.}
}
@article {Singh:2010:SEI:1824760.1824763,
	title = {The small-world effect: The influence of macro-level properties of developer collaboration networks on open-source project success},
	journal = {ACM Trans. Softw. Eng. Methodol.},
	volume = {20},
	number = {2},
	year = {2010},
	pages = {6:1{\textendash}6:27},
	publisher = {ACM},
	address = {New York, NY, USA},
	abstract = {In this study we investigate the impact of community-level networks{\textemdash}relationships that exist among developers in an OSS community{\textemdash}on the productivity of member developers. Specifically, we argue that OSS community networks characterized by small-world properties would positively influence the productivity of the member developers by providing them with speedy and reliable access to more quantity and variety of information and knowledge resources. Specific hypotheses are developed and tested using longitudinal data on a large panel of 4,279 projects from 15 different OSS communities hosted at Sourceforge. Our results suggest that significant variation exists in small-world properties of OSS communities at Sourceforge. After accounting for project, foundry, and time-specific observed and unobserved effects, we found a statistically significant relationship between small-world properties of a community and the technical and commercial success of the software produced by its members. In contrast to the findings of prior research, we also found the lack of a significant relationship between closeness and betweenness centralities of the project teams and their success. These results were robust to a number of controls and model specifications.},
	keywords = {collaborative software development, online community, open source software development, productivity, small world networks, social networks, sourceforge, team formation},
	issn = {1049-331X},
	doi = {10.1145/1824760.1824763},
	url = {http://doi.acm.org/10.1145/1824760.1824763},
	author = {Param Vir Singh}
}
@mastersthesis {barcomb:2010:sociability,
	title = {The Sociability of Free Software: A GNU Look at Free Software Identified Businesses as Social Entrepreneurships},
	year = {2010},
	school = {Maastricht University},
	type = {masters},
	abstract = {This research strives to address the gap in the literature surrounding companies which identify with the philosophical values associated with the Free Software movement, which have historically been associated with Open Source businesses. It investigates whether ethically-motivated Free Software identified companies resemble social entrepreneurships. This work also examines whether there are significant differences between the business practices of Free Software identified companies, Free Software, and Open Source enterprises in order to assess if it is appropriate to address them as a group. The study is based on seven case studies, and includes one company which is a Free Software business, but does not identify with the Free Software philosophy, as well as one company which is ethically-motivated but identifies with Open Source rather than Free Software. The results indicate that there is good reason to believe that adherence to Free Software philosophy creates socially-aware businesses, which may be social entrepreneurships. No problems were discovered with the practice of grouping together Free Software and Open Source companies in the study of business practices, provided that a broad definition of success is used.
},
	keywords = {free software, open source software, public good, small business, social entrepreneurship, social ventures},
	url = {http://barcomb.org/cgi/paper.cgi?paper=barcomb:2010:sociability},
	attachments = {https://flosshub.org/sites/flosshub.org/files/barcomb-2010-sociability.pdf},
	author = {Barcomb, Ann}
}
@conference {Meirelles:2010:SRS:1915078.1916012,
	title = {A Study of the Relationships between Source Code Metrics and Attractiveness in Free Software Projects},
	booktitle = {Proceedings of the 2010 Brazilian Symposium on Software Engineering},
	series = {SBES {\textquoteright}10},
	year = {2010},
	pages = {11{\textendash}20},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {A significant number of Free Software projects has been widely used and considered successful. However, there is an even larger number of them that cannot overcome the initial steps towards building an active community of users and developers. In this study, we investigated whether there are relationships between source code metrics and attractiveness, i.e., the ability of a project to attract users and developers. To verify these relationships, we analyzed 6,773 Free Software projects from the SourceForge.net repository. The results indicated that attractiveness is indeed correlated to some source code metrics. This suggests that measurable attributes of the project source code somehow affect the decision to contribute to and adopt a Free Software. The findings described in this paper show that it is relevant for project leaders to monitor source code quality, particularly a few objective metrics, since these can have a positive influence in projects chances of forming a community of contributors and users around their software, enabling further enhancement in quality.},
	keywords = {source code, source code analysis, sourceforge, user satisfaction, users},
	isbn = {978-0-7695-4273-7},
	doi = {10.1109/SBES.2010.27},
	url = {http://dx.doi.org/10.1109/SBES.2010.27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/sourcecode_attractiveness.pdf},
	author = {Meirelles, Paulo and Santos Jr., Carlos and Miranda, Joao and Kon, Fabio and Terceiro, Antonio and Chavez, Christina}
}
@conference {1223,
	title = {Success and Abandonment in Open Source Commons: Selected Findings from an Empirical Study of Sourceforge.net Projects},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	note = {"we utilize data collected from August through October 2006 on 107,747 OSS projects hosted on the open source hosting site Sourceforge.net (SF henceforth). We combined SF project data gathered by the FLOSSmole project (Howison et al., 2006) with other SF data we {\textquotedblleft}crawled{\textquotedblright} ourselves"},
	month = {05/2010},
	abstract = {Some open source software collaborations are sustained over long periods of time and across several versions of a software product, while others become abandoned even before the first version of the product has been developed. In this study, we identify factors that might be responsible for one or the other of these collaborative trajectories. We examine 107,747 open source software projects hosted on Sourceforge.net in August 2006 using data available through the FLOSSmole Project. We employ Classification and Regression Tree modeling and Random Forests statistical approaches to begin to establish an understanding of how various project attributes, especially physical and community ones, contribute to project success or abandonment. We find that factors associated with success and abandonment differ for projects in the early stage of development (pre-first release) compared to projects that have had a first release, and that product utility, project vision, leadership, and group-size are associated with success in open source collaborations. We also find that successful open source projects exist across all types of software and not simply in areas associated with the open source {\textquotedblleft}movement.{\textquotedblright} Other evidence suggests that Sourceforge.net may play an important role in {\textquotedblleft}intellectual match-making.{\textquotedblright}},
	keywords = {abandonment, flossmole, metadata, project failure, project success, sourceforge, time},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm003.pdf},
	author = {Schweik, C. M. and English, R. and Paienjton, Q. and Haire, S.}
}
@conference {Rastkar:2010:SSA:1806799.1806872,
	title = {Summarizing software artifacts: a case study of bug reports},
	booktitle = {Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1},
	series = {ICSE {\textquoteright}10},
	year = {2010},
	pages = {505{\textendash}514},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Many software artifacts are created, maintained and evolved as part of a software development project. As software developers work on a project, they interact with existing project artifacts, performing such activities as reading previously filed bug reports in search of duplicate reports. These activities often require a developer to peruse a substantial amount of text. In this paper, we investigate whether it is possible to summarize software artifacts automatically and effectively so that developers could consult smaller summaries instead of entire artifacts. To provide focus to our investigation, we consider the generation of summaries for bug reports. We found that existing conversation-based generators can produce better results than random generators and that a generator trained specifically on bug reports can perform statistically better than existing conversation-based generators. We demonstrate that humans also find these generated summaries reasonable indicating that summaries might be used effectively for many tasks.},
	keywords = {bug reports, eclipse, gnome, human-centric software engineering, kde, machine learning, mozilla},
	isbn = {978-1-60558-719-6},
	doi = {10.1145/1806799.1806872},
	url = {http://doi.acm.org/10.1145/1806799.1806872},
	author = {Rastkar, Sarah and Murphy, Gail C. and Murray, Gabriel}
}
@article {1385,
	title = {Survival analysis on the duration of open source projects},
	journal = {Information and Software Technology},
	volume = {52},
	year = {2010},
	note = {"For the purposes of our study we used data coming only from source code repositories."},
	month = {9/2010},
	pages = {902 - 922},
	abstract = {Context

Open source (FLOSS) project survivability is an important piece of information for many open source stakeholders. Coordinators of open source projects would like to know the chances for the survival of the projects they coordinate. Companies are also interested in knowing how viable a project is in order to either participate or invest in it, and volunteers want to contribute to vivid projects.
Objective

The purpose of this article is the application of survival analysis techniques for estimating the future development of a FLOSS project.
Method

In order to apply such approach, duration data regarding FLOSS projects from the FLOSSMETRICS (This work was partially supported by the European Community{\textquoteright}s Sixth Framework Program under the Contract FP6-033982) database were collected. Such database contains metadata for thousands of FLOSS projects, derived from various forges. Subsequently, survival analysis methods were employed to predict the survivability of the projects, i.e. their probability of continuation in the future, by examining their duration, combined with other project characteristics such as their application domain and number of committers.
Results

It was shown how probability of termination or continuation may be calculated and how a prediction model may be built to upraise project future. In addition, the benefit of adding more committers to FLOSS projects was quantified.
Conclusion

Analysis results demonstrate the usefulness of the proposed framework for assessing the survival probability of a FLOSS project.
},
	keywords = {flossmetrics, prediction, source code, survival analysis},
	issn = {09505849},
	doi = {10.1016/j.infsof.2010.05.001},
	author = {Samoladas, Ioannis and Lefteris Angelis and Ioannis Stamelos}
}
@article {1376,
	title = {Sustainability of Open-Source Projects: A Longitudinal Study},
	journal = {Journal of the Association for Information Systems},
	volume = {11},
	number = {5},
	year = {2010},
	abstract = {This paper examines the factors that influence the long-term sustainability of FLOSS projects. A model of project sustainability based on organizational ecology is developed and tested empirically. Data about activity and contribution patterns over the course of five years for 2,772 projects registered with SourceForge is analyzed. Our results suggest that the size of the project{\textquoteright}s development base, project age and the size of niche occupied by the project are positively related to the project{\textquoteright}s ability to attract user and/or developer resources. The ability to attract resources is an indicator of the perceived project legitimacy, which in turn is a strong predictor of the project{\textquoteright}s future sustainability. Thus a project{\textquoteright}s ability to attract developer and user resources is shown to play a mediating role between the demographic (size and age) and ecological (niche) characteristics of the project and its future sustainability. Our results support the applicability of tenets of organizational ecology related to the liability of smallness, the liability of newness, and population characteristics (niche size) to the FLOSS development environment. The implications of the results for future research and practice are discussed.},
	keywords = {contribution, developers, sourceforge, sustainability},
	url = {http://aisel.aisnet.org/jais/vol11/iss11/5/},
	author = {Chengular-Smith, I. and Sidorova, Anna and Daniel, Sherae L.}
}
@conference {anbalagan2010towards,
	title = {Towards a bayesian approach in modeling the disclosure of unique security faults in open source projects},
	booktitle = {Software Reliability Engineering (ISSRE), 2010 IEEE 21st International Symposium on},
	year = {2010},
	pages = {101{\textendash}110},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {Software security has both an objective and a subjective component. A lot of the information available about that today is focused on security vulnerabilities and their disclosure. It is less frequent that security breaches and failures rates are reported, even in open source projects. Disclosure of security problems can take several forms. A disclosure can be accompanied by a release of the fix for the problem, or not. The latter category can be further divided into {\textquotedblright}voluntary{\textquotedblright} and {\textquotedblright}involuntary{\textquotedblright} security issues. In widely used software there is also considerable variability in the operational profile under which the software is used. This profile is further modified by attacks on the software that may be triggered by security disclosures. Therefore a comprehensive model of software security qualities of a product needs to incorporate both objective measures, such as security problem disclosure, repair and, failure rates, as well as less objective metrics such as implied variability in the operational profile, influence of attacks, and subjective impressions of exposure and severity of the problems, etc. We show how a classical Bayesian model can be adapted for use in the security context. The model is discussed and assessed using data from three open source software project releases. Our results show that the model is suitable for use with a certain subset of disclosed security faults, but that additional work will be needed to identify appropriate shape and scaling functions that would accurately reflect end-user perceptions associated with security problems.},
	keywords = {security},
	url = {http://ai2-s2-pdfs.s3.amazonaws.com/edcf/0b13ae1e6317c7e31f6b8783f669b978ffb3.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/0b13ae1e6317c7e31f6b8783f669b978ffb3.pdf},
	author = {Anbalagan, Prasanth and Vouk, Mladen}
}
@conference {1259,
	title = {Towards an Openness Rating System for Open Source Software},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)},
	year = {2010},
	pages = {1 - 8},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {Many open source software projects are not very open to third party developers. The point of open source is to enable anyone to fix bugs or add desired capabilities without holding them hostage to the original developers. This principle is important because an open source project{\textquoteright}s developers may be unresponsive or unable to meet third party needs, even if funding support for requested improvements is offered.This paper presents a simple rating system for evaluating the openness of software distributions. The rating system considers factors such as platform portability, documentation, licensing, and contribution policy. Several popular open source products are rated in order to illustrate the efficacy of the rating system.},
	keywords = {alice, case study, contribution, documentation, freespire, galib, latex, license, linux, linux kernel, mediaportal, openness, openoffice, opensolaris, rating, unicon},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.405},
	attachments = {https://flosshub.org/sites/flosshub.org/files/10-07-04.pdf},
	author = {Bein, Wolfgang and Jeffery, Clinton}
}
@conference {1217,
	title = {Trends That Affect Temporal Analysis Using SourceForge Data},
	booktitle = {5th Workshop on Public Data about Software Development (WoPDaSD 2010)},
	year = {2010},
	note = {"In this paper we examine some of the limitations of artifact data by specifically addressing the applicability of SourceForge data to the study of project evolution."

"For our analysis we examine 9,997 Production/Stable or Maintenance phase projects stored in CVS on SourceForge and extracted in October of 2006 [5]"},
	abstract = {SourceForge is a valuable source of software artifact data for researchers who study project evolution and developer behavior. However, the data exhibit patterns that may bias temporal analyses. Most notable are cliff walls in project source code repository timelines, which indicate large commits that are out of character for the given project. These cliff walls often hide significant periods of development and developer collaboration{\textemdash}a threat to studies that rely on SourceForge repository data. We demonstrate how to identify these cliff walls, discuss reasons for their appearance, and propose preliminary measures for mitigating their effects in evolution-oriented studies.},
	keywords = {cliff walls, committers, cvs, evolution, growth, source code, sourceforge, time, time series},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd001.pdf},
	author = {MacLean, Alexander C. and Pratt, Landon J. and Krein, Jonathan L. and Knutson, Charles D.}
}
@conference {952,
	title = {The Ultimate Debian Database: Consolidating bazaar metadata for Quality Assurance and data mining},
	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 = {52 - 61},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {FLOSS distributions like RedHat and Ubuntu require a lot more complex infrastructures than most other FLOSS projects. In the case of community-driven distributions like Debian, the development of such an infrastructure is often not very organized, leading to new data sources being added in an impromptu manner while hackers set up new services that gain acceptance in the community. Mixing and matching data is then harder than should be, albeit being badly needed for Quality Assurance and data mining. Massive refactoring and integration is not a viable solution either, due to the constraints imposed by the bazaar development model. This paper presents the Ultimate Debian Database (UDD), which is the countermeasure adopted by the Debian project to the above "data hell". UDD gathers data from various data sources into a single, central SQL database, turning Quality Assurance needs that could not be easily implemented before into simple SQL queries. The paper also discusses the customs that have contributed to the data hell, the lessons learnt while designing UDD, and its applications and potentialities for data mining on FLOSS distributions.},
	keywords = {debian, metadata, udd},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463277},
	attachments = {https://flosshub.org/sites/flosshub.org/files/52msr2010-udd.pdf},
	author = {Nussbaum, Lucas and Zacchiroli, Stefano}
}
@article {1332,
	title = {Using Open Source Software Components to Implement a Modular Web 2.0 Design for Map-Based Discussions},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {30 - 47},
	abstract = {This paper discusses the research-based origins and modular architecture of an open source geospatial tool that facilitates synchronous individual and group discussions using the medium of a Web map service. The software draws on existing open source geospatial projects and associated libraries and techniques that have evolved as part of the new generation of Web applications. The purpose of the software is discussed, highlighting the fusion of existing open source projects to produce new tools. Two case studies are briefly discussed to illustrate the value an open source approach brings to communities who would remain otherwise outside the reach of proprietary software tools. The paper concludes with comments on the project{\textquoteright}s future evolution as an open source participatory mapping platform.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010070102},
	author = {Leahy, Michael G. and Hall, G. Brent}
}
@article {1387,
	title = {Using the DEMO methodology for modeling open source software development processes},
	journal = {Information and Software Technology},
	volume = {52},
	year = {2010},
	month = {6/2010},
	pages = {656 - 671},
	abstract = {Context

Open source software development (OSSD) process modeling has received increasing interest in recent years. These efforts aim to identify common elements in the development process between multiple open source software (OSS) projects. However, the complexity inherent to OSSD process modeling puts significant demands on the modeling language.
Objective

In this paper, we propose that the Design and Engineering Methodology for Organizations (DEMO) may provide an interesting alternative to develop OSSD process models. DEMO exhibits two unique features within the context of OSSD process modeling. First, DEMO analyzes processes at the ontological level and provides high-level process descriptions, instead of focusing on the implementation level. Second, DEMO studies the communication patterns between human actors, instead of the sequences in which activities are performed.
Method

We investigate the feasibility of using DEMO to construct OSSD process models by means of a case study. DEMO models were constructed to describe the NetBeans Requirements and Release process. In addition, the quality of these DEMO models was evaluated using a quality framework for conceptual modeling.
Results

Our results showed that our DEMO models exhibited a high level of abstraction, thereby reducing the complexity of the OSSD process models. In addition, the evaluation of the models developed in this paper by using the quality framework for conceptual modeling showed that the models were of high quality.
Conclusions

We have shown that the DEMO methodology can be successfully used to model OSSD processes and to obtain abstract and high-quality OSSD process models. However, given some potential drawbacks with respect to understandability and implementability, we primarily propose the use of DEMO within OSSD process modeling as an analysis tool that should be complemented with other techniques and models for communication and reenactment purposes.},
	keywords = {DEMO, Enterprise ontology, open source software, Software process modeling},
	issn = {09505849},
	doi = {10.1016/j.infsof.2010.02.002},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584910000157},
	author = {Huysmans, Philip and Ven, Kris and Verelst, Jan}
}
@conference {1829,
	title = {Validity concerns in software engineering research},
	booktitle = {Proceedings of the FSE/SDP workshop on Future of software engineering research - FoSER {\textquoteright}10},
	year = {2010},
	note = {"Obtaining a balanced set of data from
open source repositories has been an issue in the open source
research community for some time, and several collections
of data have grown to attempt to solve this problem [11, 13,
20]."},
	pages = {411},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Santa Fe, New Mexico, USANew York, New York, USA},
	abstract = {Empirical studies that use software repository artifacts have become popular in the last decade due to the ready availability of open source project archives. In this paper, we survey empirical studies in the last three years of ICSE and FSE proceedings, and categorize these studies in terms of open source projects vs. proprietary source projects and the diversity of subject programs used in these studies. Our survey has shown that almost half (49\%) of recent empirical studies used solely open source projects. Existing studies either draw general conclusions from these results or explicitly disclaim any conclusions that can extend beyond specific subject software. We conclude that researchers in empirical software engineering must consider the external validity concerns that arise from using only several well-known open source software projects, and that discussion of data source selection is an important discussion topic in software engineering research. Furthermore, we propose a community research infrastructure for software repository benchmarks and sharing the empirical analysis results, in order to address external validity concerns and to raise the bar for empirical software engineering research that analyzes software artifacts. },
	keywords = {flossmole cited},
	isbn = {9781450304276},
	doi = {10.1145/1882362.1882446},
	author = {Wright, Hyrum K. and Kim, Miryung}
}
@conference {969,
	title = {Validity of network analyses in Open Source Projects},
	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},
	note = {"We have mined archival records of developer mailing lists to generate reply-to social networks for the three OSS projects: Apache, MySQL, and Perl."

"For each of these projects, we construct an information flow network based on messages that are sent as replies to previous messages....We use this methodology on all mined data to create a network of mailing list participants. "},
	pages = {201 - 209},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Social network methods are frequently used to analyze networks derived from Open Source Project communication and collaboration data. Such studies typically discover patterns in the information flow between contributors or contributions in these projects. Social network metrics have also been used to predict defect occurrence. However, such studies often ignore or side-step the issue of whether (and in what way) the metrics and networks of study are influenced by inadequate or missing data. In previous studies email archives of OSS projects have provided a useful trace of the communication and co-ordination activities of the participants. These traces have been used to construct social networks that are then subject to various types of analysis. However, during the construction of these networks, some assumptions are made, that may not always hold; this leads to incomplete, and sometimes incorrect networks. The question then becomes, do these errors affect the validity of the ensuing analysis? In this paper we specifically examine the stability of network metrics in the presence of inadequate and missing data. The issues that we study are: 1) the effect of paths with broken information flow (i.e. consecutive edges which are out of temporal order) on measures of centrality of nodes in the network, and 2) the effect of missing links on such measures. We demonstrate on three different OSS projects that while these issues do change network topology, the metrics used in the analysis are stable with respect to such changes.},
	keywords = {apache, email archives, mailing lists, missing data, mysql, perl, social networks},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463342},
	attachments = {https://flosshub.org/sites/flosshub.org/files/201NetworkAnalysis.pdf},
	author = {Nia, Roozbeh and Christian Bird and Devanbu, Premkumar and Filkov, Vladimir}
}
@book {1250,
	title = {Warehousing and Studying Open Source Versioning Metadata},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: New Horizons (OSS 2010)},
	volume = {319},
	year = {2010},
	pages = {413 - 418},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {In this paper, we describe the downloading and warehousing of Open Source Software (OSS) versioning metadata from SourceForge, BerliOS Developer, and GNU Savannah. This data enables and supports research in areas such as software engineering, open source phenomena, social network analysis, data mining, and project management. This newly-formed database containing Concurrent Versions System (CVS) and Subversion (SVN) metadata offers new research opportunities for large-scale OSS development analysis. The CVS and SVN data is juxtaposed with the SourceForge.net Research Data Archive [5] for the purpose of performing more powerful and interesting queries. We also present an initial statistical analysis of some of the most active projects. },
	keywords = {berlios, cvs, savannah, scm, sourceforge, srda, subversion, svn},
	isbn = {978-3-642-13244-5},
	issn = {1861-2288},
	doi = {10.1007/978-3-642-13244-5_40},
	author = {van Antwerp, M. and Madey, G.},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Madey, Gregory R. and Noll, John}
}
@article {1239,
	title = {Weaving a Semantic Web Across OSS Repositories},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	month = {32/2010},
	pages = {29 - 40},
	abstract = {Several public repositories and archives of {\textquotedblleft}facts{\textquotedblright} about libre software projects, maintained either by open source communities or by research communities, have been flourishing over the Web in recent years. These have enabled new analysis and support for new quality assurance tasks. This paper presents some complementary existing tools, projects and models proposed both by OSS actors or research initiatives that are likely to lead to useful future developments in terms of study of the FLOSS phenomenon, and also to the very practitioners in the FLOSS development projects. A goal of the research conducted within the HELIOS project is to address bugs traceability issues. In this regard, the authors investigate the potential of using Semantic Web technologies in navigating between many different bugtracker systems scattered all over the open source ecosystem. By using Semantic Web techniques, it is possible to interconnect the databases containing data about open-source software projects development, which enables OSS partakers to identify resources, annotate them, and further interlink those using dedicated properties and collectively designing a distributed semantic graph.},
	keywords = {archive, bug, bugtracker, database, debian, forge, interoperability, ontology, OSLC-CM, RDF, repository of repositories, semantic, semantic Web},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010040103},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd2009-olivier-berger.pdf},
	author = {Olivier Berger and Valentin Vlasceanu and Christian Bac and Quang Vu Dang and Lauriere, St{\'e}phane}
}
@article {10.1109/TSE.2010.63,
	title = {What Makes a Good Bug Report?},
	journal = {IEEE Transactions on Software Engineering},
	volume = {36},
	year = {2010},
	note = {"o find out which matter most, we asked 872 devel-
opers from the APACHE, ECLIPSE, and MOZILLA projects to:
1. Complete a survey on important information in bug reports and the problems they faced with them. We received a total of 156 responses to our survey (Section 2 and 3).
2. Rate the quality of bug reports from very poor to very good on a five-point Likert scale [22]. We received a total of 1,186 votes for 289 randomly selected bug reports (Section 4).
In addition, we asked 1,354 reporters1 from the same projects to complete a similar survey, out of which 310 responded. "},
	pages = {618-643},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {In software development, bug reports provide crucial information to developers. However, these reports widely differ in their quality. We conducted a survey among developers and users of APACHE, ECLIPSE, and MOZILLA to find out what makes a good bug report.
The analysis of the 466 responses revealed an information mis- match between what developers need and what users supply. Most developers consider steps to reproduce, stack traces, and test cases as helpful, which are at the same time most difficult to provide for users. Such insight is helpful to design new bug tracking tools that guide users at collecting and providing more helpful information.
Our CUEZILLA prototype is such a tool and measures the quality of new bug reports; it also recommends which elements should be added to improve the quality. We trained CUEZILLA on a sample of 289 bug reports, rated by developers as part of the survey. In our experiments, CUEZILLA was able to predict the quality of 31{\textendash}48\% of bug reports accurately.},
	keywords = {bug report, Survey},
	issn = {0098-5589},
	doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.2010.63},
	url = {http://dl.acm.org/citation.cfm?id=1453146},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bettenburg-fse-2008.pdf},
	author = {Zimmermann, Thomas and Premraj, Rahul and Bettenburg, Nicolas and Sascha Just and Schroter, Adrian and Weiss, Cathrin}
}
@article {1326,
	title = {What{\textquoteright}s all the FOSS?},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {1 - 14},
	abstract = {Philosophical, financial, practical, and pedagogical considerations have prompted educators to take a serious look at Free and Open Source Software (FOSS) as an alternative to proprietary software. To better understand the overall concept of FOSS, this article provides a brief history of FOSS as well as a summary of its definition, philosophy, and major areas of research, including strengths and limitations, diffusion in education and educational uses as well as a look at the opportunities, issues, and challenges associated with FOSS. In conclusion, the authors speculate how FOSS, along with advances in E-Learning and other emerging technologies, will positively shape our educational future. },
	issn = {1942-3934},
	doi = {10.4018/jossp.2010010101},
	author = {Huett, Jason B. and Sharp, Jason H. and Huett, Kimberly C.}
}
@conference {953,
	title = {When process data quality affects the number of bugs: Correlations in software engineering datasets},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {62 - 71},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Software engineering process information extracted from version control systems and bug tracking databases are widely used in empirical software engineering. In prior work, we showed that these data are plagued by quality deficiencies, which vary in its characteristics across projects. In addition, we showed that those deficiencies in the form of bias do impact the results of studies in empirical software engineering. While these findings affect software engineering researchers the impact on practitioners has not yet been substantiated. In this paper we, therefore, explore (i) if the process data quality and characteristics have an influence on the bug fixing process and (ii) if the process quality as measured by the process data has an influence on the product (i.e., software) quality. Specifically, we analyze six Open Source as well as two Closed Source projects and show that process data quality and characteristics have an impact on the bug fixing process: the high rate of empty commit messages in Eclipse, for example, correlates with the bug report quality. We also show that the product quality - measured by number of bugs reported - is affected by process data quality measures. These findings have the potential to prompt practitioners to increase the quality of their software process and its associated data quality.},
	keywords = {apache, bug reports, eclipse, gnome, log files, mozilla, netbeans, openoffice.org, version control},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463286},
	attachments = {https://flosshub.org/sites/flosshub.org/files/62bachmann-msr10.pdf},
	author = {Bachmann, Adrian and Bernstein, Abraham}
}
@conference {601,
	title = {1st International Workshop on: {\textquoteleft}Designing for Participatory Learning{\textquoteright} Building from Open Source Success to Develop Free Ways to Share and Learn},
	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 = {355 - 356},
	publisher = {Springer},
	organization = {Springer},
	chapter = {33},
	abstract = {The Open Source world shows how volunteer collaboration can lead to great products and to great learning. We want to further explore at this workshop what happens using approaches from that community to break barriers between teachers and learners for today{\textquoteright}s Internet-savvy young people to design and co-construct sites for participatory learning. The aim of this workshop is to explore the barriers for this type of learning in higher education settings. Content creation, knowledge exchange, community
dynamics, and the impact on the boundary between formal and informal education are key subjects of this workshop.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1st\%20International\%20Workshop\%20on.pdf},
	author = {Andreas Meiszner and Ioannis Stamelos and Sowe, Sulayman}
}
@conference {599,
	title = {4th International Workshop on Public Data about Software Development},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {351 - 352},
	publisher = {Springer},
	organization = {Springer},
	chapter = {31},
	abstract = {Libre (free, open source) projects offer publicly available data sources. The research community is starting to produce, use and exchange large data sets of information. These data sets have to be retrieved, purged, described, and can be published for public consumption by other groups. Their availability allows for the decoupling of research activities, the reproducibility of research results, and even the collaboration (and competition) in the analysis of data. This activity is frequently presented at workshops and conferences, but since the focus of these conferences is not specific to the use of public data, discussions of techniques and experiences are not as deep and fruitful as they could be. This workshop is once again (for the fourth year in a row) such a place. We will host discussions specifically about these sorts of public data sets about software development, how they are retrieved, how they can be analyzed and mined, how they can be exchanged and extended.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/4the\%20International\%20Workshop\%20on\%20Public\%20Data.pdf},
	author = {Gonz{\'a}lez-Barahona, Jes{\'u}s and Squire, Megan and Izquierdo-Cort{\'a}zar, Daniel}
}
@article {1348,
	title = {An Agent Simulation Study on Conflict, Community Climate and Innovation in Open Source Communities},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {1 - 25},
	abstract = {More than ever the complexity of innovation requires group efforts, as teams of scientists and engineers from diverse backgrounds work together to solve problems. One of the significant problems in understanding emergence of innovation involves how virtual innovation organizations and communities govern and coordinate to maximize innovation output. An agent simulation study is conducted to examine the impact of culture and conflict management styles on collective creativity in open source innovation systems. Findings suggest that decentralized coordination schemes such as emergent selection such as found in utility communities and moderate degrees of assertiveness and cooperation for conflict management result in higher incidence of innovation.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009100101},
	author = {Yilmaz, Levent}
}
@conference {839,
	title = {Amassing and indexing a large sample of version control systems: towards the census of public source code history},
	booktitle = {6th IEEE Working Conference on Mining Software Repositories},
	year = {2009},
	note = {Related work: "For example, FLOSSMole [8]
collects the list of projects and their metadata from SourceForge,
FreshMeat, Free Software Foundation (FSF), RubyForge,
and ObjectWeb. "

"The list of
home pages from open source directories such as FSF or
FLOSSMole could provide a focused set of web pages for
the search"

"To get the list of projects for SourceForge we used
FLOSSMole project [8] that collects the list of SourceForge
projects and their metadata. We use project ID, because it
was used to specify the VCS URL within the SourceForge
repository."},
	month = {May 16{\textendash}17},
	abstract = {The source code and its history represent the output and process of software development activities and are an in- valuable resource for study and improvement of software development practice. While individual projects and groups of projects have been extensively analyzed, some fundamental questions, such as the spread of innovation or genealogy of the source code, can be answered only by considering the entire universe of publicly available source code and its history. We describe methods we developed over the last six years to gather, index, and update an approximation of such a universal repository for publicly accessible version control systems and for the source code inside a large corporation. While challenging, the task is achievable with limited resources. The bottlenecks in network bandwidth, processing, and disk access can be dealt with using inherent parallelism of the tasks and suitable tradeoffs between the amount of storage and computations, but a completely automated discovery of public version control systems may require enticing participation of the sampled projects. Such universal repository would allow studies of global properties and origins of the source code that are not possible through other means.},
	keywords = {bazaar, cvs, flossmole, git, mercurial, source code, sourceforge, subversion, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/11amassing.pdf},
	author = {Audris Mockus}
}
@conference {1809,
	title = {On the Analysis of Contributions from Privileged Users in Virtual Open Communities},
	booktitle = {2009 42nd Hawaii International Conference on System Sciences},
	year = {2009},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, Hawaii, USA},
	abstract = {Collaborative projects built around virtual communities on the Internet have gained momentum over the last decade. Nevertheless, their rapid growth rate rises some questions:which is the most effective approach to manage and organize their content creation process? Can these communities scale, controlling their projects as their size continues to grow over time? To answer these questions, we undertake a quantitative analysis of privileged users in FLOSS development projects and in Wikipedia. From our results, we conclude that the inequality level of user contributions in both types of initiatives is remarkably distinct, even though both communities present almost identical patterns regard-ing the number of distinct contributors per file (in FLOSS  projects) or per article (in Wikipedia). As a result, totally open projects like Wikipedia can effectively deal with faster growing rates, while FLOSS projects may be affected by bottlenecks on committers who play critical roles.},
	isbn = {978-0-7695-3450-3},
	doi = {10.1109/HICSS.2009.328},
	author = {Ortega, Felipe and Izquierdo-Cort{\'a}zar, Daniel and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Gregorio Robles}
}
@conference {577,
	title = {Analysis of Open Source Software Development Iterations by Means of Burst Detection Techniques},
	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 = {83 - 93},
	publisher = {Springer},
	organization = {Springer},
	chapter = {9},
	abstract = {A highly efficient bug fixing process and quick release cycles are considered key properties of the open source software development methodology. In this paper, we study the relation between code activities (such as lines of code added per commit), bug fixing activities, and software release dates in a subset of open source projects. To study the phenomenon, we gathered a large data set about the evolution of 5 major open source projects. We compared activities by means of a burst detection technique to discover temporal peaks in time-series. We found quick adaptation of issue tracking activities in proximity of releases, and a distribution of coding activities across releases. Results show the importance of the application type/domain for the evaluation of the development process.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Analysis\%20of\%20Open\%20Source\%20Software.pdf},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo}
}
@proceedings {847,
	title = {Analyzing Software Licenses in Open Architecture Software Systems},
	year = {2009},
	month = {05/2009},
	address = {Vancouver, Canada},
	author = {Alspaugh, Thomas and Hazeline U. Asuncion and Walt Scacchi}
}
@conference {606,
	title = {Assessing FLOSS Communities: An Experience Report from the QualOSS Project},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {364 - 364},
	publisher = {Springer},
	organization = {Springer},
	chapter = {38},
	abstract = {This paper presents work done in the QualOSS (Quality of Open Source Software) research project,which aims at building a methodology and tools to help in the assessment of the quality of FLOSS (free, libre, open source software) endeavors. In particular, we introduce the research done to evaluate the FLOSS endeavor communities. Following the Goal-Question-Metric paradigm, QUALOSS describes goals, the associated questions and then metrics that allow to answer the questions.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_38},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Assessing\%20FLOSS\%20Communities.pdf},
	author = {Izquierdo-Cortazar, Daniel and Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s and Deprez, Jean-Christophe}
}
@conference {937,
	title = {Assigning bug reports using a vocabulary-based expertise model of developers},
	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 = {131 - 140},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {For popular software systems, the number of daily submitted bug reports is high. Triaging these incoming reports is a time consuming task. Part of the bug triage is the assignment of a report to a developer with the appropriate expertise. In this paper, we present an approach to automatically suggest developers who have the appropriate expertise for handling a bug report. We model developer expertise using the vocabulary found in their source code contributions and compare this vocabulary to the vocabulary of bug reports. We evaluate our approach by comparing the suggested experts to the persons who eventually worked on the bug. Using eight years of Eclipse development as a case study, we achieve 33.6\% top-1 precision and 71.0\% top-10 recall.},
	keywords = {bug reports, bugzilla, develect, developers, eclipse, expertise, scm},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069491},
	attachments = {https://flosshub.org/sites/flosshub.org/files/131AssigningBugReports.pdf},
	author = {Matter, Dominique and Kuhn, Adrian and Nierstrasz, Oscar}
}
@conference {605,
	title = {Assurance Evaluation for OSS Adoption in a Telco Context},
	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 = {363 - 363},
	publisher = {Springer},
	organization = {Springer},
	chapter = {37},
	abstract = {Software Assurance (SwA) is a complex concept that involves different stages of a software development process and may be defined differently depending on its focus, as for instance software quality, security, or dependability. In Computer Science, the term assurance is referred to all activities necessary to provide enough confidence that a software product will satisfy its users{\textquoteright} functional and non-functional requirements.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Assurance\%20Evaluation\%20for\%20OSS.pdf},
	author = {Ardagna, Claudio and Banzi, Massimo and Damiani, Ernesto and El Ioini, Nabil and Frati, Fulvio}
}
@conference {930,
	title = {Author entropy vs. file size in the GNOME suite of applications},
	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 = {91 - 94},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {We present the results of a study in which author entropy was used to characterize author contributions per file. Our analysis reveals three patterns: banding in the data, uneven distribution of data across bands, and file size dependent distributions within bands. Our results suggest that when two authors contribute to a file, large files are more likely to have a dominant author than smaller files.},
	keywords = {author entropy, contributions, gnome, msr challenge},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069484},
	author = {Casebolt, Jason R. and Krein, Jonathan L. and MacLean, Alexander C. and Knutson, Charles D. and Delorey, Daniel P.}
}
@conference {943,
	title = {Automatic labeling of software components and their evolution using log-likelihood ratio of word frequencies in source code},
	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 = {175 - 178},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {As more and more open-source software components become available on the Internet we need automatic ways to label and compare them. For example, a developer who searches for reusable software must be able to quickly gain an understanding of retrieved components. This understanding cannot be gained at the level of source code due to the semantic gap between source code and the domain model. In this paper we present a lexical approach that uses the log-likelihood ratios of word frequencies to automatically provide labels for software components. We present a prototype implementation of our labeling/comparison algorithm and provide examples of its application. In particular, we apply the approach to detect trends in the evolution of a software system.},
	keywords = {frequency, hapax, information retrieval, java, junit, keywords, labeling, source code},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069499},
	attachments = {https://flosshub.org/sites/flosshub.org/files/175AutomaticLabeling.pdf},
	author = {Kuhn, Adrian}
}
@conference {1360,
	title = {Benchmarking Lightweight Techniques to Link E-Mails and Source Code},
	booktitle = {2009 16th Working Conference on Reverse Engineering},
	year = {2009},
	note = {"We present different lightweight approaches that, exploiting the specific characteristics of e-mails and the ones of the source code, are capable of establishing a bi-directional link between source code entities and e-mails"

"We analyzed ArgoUML1, a UML modelling tool written in Java, developed over the course of approximately 9 years, and made available under the BSD Open Source License. We consider the release 0.28 (March 2009) that comprehends 2,197 classes. We employed the lightweight approaches to map such classes to the related e-mails in ArgoUML mailing lists.
ArgoUML e-mails are stored in six mailing lists (see Table I), for a total amount of 79,175 messages"

Figure 4 is helpful to understand what this does.},
	pages = {205 - 214},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Lille, France},
	abstract = {During the evolution of a software system, a large amount of information, which is not always directly related to the source code, is produced. Several researchers have provided evidence that the contents of mailing lists represent a valuable source of information: Through e-mails, developers discuss design decisions, ideas, known problems and bugs, etc. which are otherwise not to be found in the system.

A technical challenge in this context is how to establish the missing link between free-form e-mails and the system artifacts they refer to. Although the range of approaches is vast, establishing their accuracy remains a problem, as there is no benchmark against which to compare their performance.

To overcome this issue, we manually inspected a statistically significant number of e-mails pertaining to the ArgoUML system. Based on this benchmark, we present a variety of lightweight techniques to assign e-mails to software artifacts and measure their effectiveness in terms of precision and recall.},
	keywords = {argouml, email, mailing lists},
	isbn = {978-0-7695-3867-9},
	doi = {10.1109/WCRE.2009.44},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wcre2009.pdf},
	author = {Bacchelli, Alberto and D{\textquoteright}Ambros, Marco and Lanza, Michele and Robbes, Romain}
}
@conference {574,
	title = {Beyond the Business Model: Incentives for Organizations to Publish Software Source Code},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {47 - 56},
	publisher = {Springer},
	organization = {Springer},
	chapter = {6},
	abstract = {The software stack opened under Open Source Software (OSS) licenses is growing rapidly. Commercial actors have released considerable amounts of previously proprietary source code. These actions beg the question why companies choose a strategy based on giving away software assets? Research on outbound OSS approach has tried to answer this question with the concept of the {\textquotedblleft}OSS business model{\textquotedblright}. When studying the reasons for code release, we have observed that the business model concept is too generic to capture the many incentives organizations have. Conversely, in this paper we investigate empirically what the companies{\textquoteright} incentives are by means of an exploratory case study of three organizations in different stages of their code release. Our results indicate that the companies aim to promote standardization, obtain development resources, gain cost savings, improve the quality of software, increase the trustworthiness of software, or steer OSS communities. We conclude that future research on outbound OSS could benefit from focusing on the heterogeneous incentives for code release rather than on revenue models.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Beyond\%20the\%20Business\%20Model.pdf},
	author = {Juho Lindman and Juutilainen, Juha-Pekka and Rossi, Matti}
}
@article {1237,
	title = {Bridging the Gap between Agile and Free Software Approaches},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	month = {31/2009},
	pages = {58 - 71},
	abstract = {Agile sprints are short events where a small team collocates in order to work on particular aspects of the overall project for a short period of time. Sprinting is a process that has been observed also in Free Software projects: these two paradigms, sharing common principles and values have shown several commonalities of practice. This article evaluates the impact of sprinting on a Free Software project through the analysis of code repository logs: sprints from two Free Software projects (Plone and KDE PIM) are assessed and two hypotheses are formulated: do sprints increase productivity? Are Free Software projects more productive after sprints compared with before? The primary contribution of this article is to show how sprinting creates a large increase in productivity both during the event, and immediately after the event itself: this argues for more in-depth studies focussing on the nature of sprinting.},
	keywords = {agile, kde, lines of code, loc, plone, productivity, scm, scrum, sprints, subversion},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009010104},
	author = {Paul J. Adams and Capiluppi, Andrea}
}
@conference {609,
	title = {The Case Study of an F/OSS Virtualization Platform Deployment and Quantitative Results},
	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 = {367 - 367},
	publisher = {Springer},
	organization = {Springer},
	chapter = {41},
	abstract = {In this paper we present practical experiences and results from the deployment of an F/OSS virtualization platform. EKT{\textquoteright}s (NDC) core IT infrastructure was transformed to a virtualized one, using exclusively F/OSS, while severe budget and timing constraints were in place. This migration was initiated in order to better cope with EKT{\textquoteright}s services requirements, while accommodating at the same time the need for the in house development of a large scale open access infrastructure. The benefits derived from this migration were not only generic virtualization benefits, such as the quantifiable reduced power consumption and cost reduction through consolidation, but also F/OSS virtualization specific ones.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_41},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Case\%20Study\%20of\%20an\%20F\%20OSS.pdf},
	author = {Stathopoulos, Panagiotis and Soumplis, Alexandros and Houssos, Nikos}
}
@conference {587,
	title = {Challenges of the Open Source Component Marketplace in the Industry},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	year = {2009},
	month = {2009///},
	pages = {213 - 224},
	publisher = {Springer},
	organization = {Springer},
	chapter = {19},
	abstract = {The reuse of Open Source Software components available on the Internet is playing a major role in the development of Component Based Software Systems. Nevertheless, the special nature of the OSS marketplace has taken the {\textquotedblleft}classical{\textquotedblright} concept of software reuse based on centralized repositories to a completely different arena based on massive reuse over Internet. In this paper we provide an overview of the actual state of the OSS marketplace, and report preliminary findings about how companies interact with this marketplace to reuse OSS components. Such data was gathered from interviews in software companies in Spain and Norway. Based on these results we identify some challenges aimed to improve the industrial reuse of OSS components.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_19},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Challenges\%20of\%20the\%20Open\%20Source.pdf},
	author = {Ayala, Claudia and Hauge, {\O}yvind and Conradi, Reidar and Franch, Xavier and Li, Jingyue and Velle, Ketil}
}
@conference {582,
	title = {Choosing Open Source ERP Systems: What Reasons Are There For Doing So?},
	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 = {143 - 155},
	publisher = {Springer},
	organization = {Springer},
	chapter = {14},
	abstract = {Enterprise resource planning (ERP) systems attract a high attention and open source software does it as well. The question is then if, and if so, when do open source ERP systems take off. The paper describes the status of open source ERP systems. Based on literature review of ERP system selection criteria based on Web of Science articles, it discusses reported reasons for choosing open source or proprietary ERP systems. Last but not least, the article presents some conclusions that could act as input for future research. The paper aims at building up a foundation for the basic question: What are the reasons for an organization to adopt open source ERP systems.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_14},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Choosing\%20Open\%20Source\%20ERP.pdf},
	author = {Johansson, Bj{\"o}rn and Sudzina, Frantisek}
}
@conference {929,
	title = {Code siblings: Technical and legal implications of copying code between applications},
	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 = {81 - 90},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Source code cloning does not happen within a single system only. It can also occur between one system and another. We use the term code sibling to refer to a code clone that evolves in a different system than the code from which it originates. Code siblings can only occur when the source code copyright owner allows it and when the conditions imposed by such license are not incompatible with the license of the destination system. In some situations copying of source code fragments are allowed - legally - in one direction, but not in the other. In this paper, we use clone detection, license mining and classification, and change history techniques to understand how code siblings - under different licenses - flow in one direction or the other between Linux and two BSD Unixes, FreeBSD and OpenBSD. Our results show that, in most cases, this migration appears to happen according to the terms of the license of the original code being copied, favoring always copying from less restrictive licenses towards more restrictive ones. We also discovered that sometimes code is inserted to the kernels from an outside source.},
	keywords = {bsd, fossology, freebsd, linux, openbsd, source code},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069483},
	attachments = {https://flosshub.org/sites/flosshub.org/files/81CodeSiblings.pdf},
	author = {Daniel M. German and Di Penta, Massimiliano and Gueheneuc, Yann-Gael and Antoniol, Giuliano}
}
@article {1344,
	title = {Collaboration in Open Source Domains},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {17 - 28},
	abstract = {Free and open source software (F/OSS) developers have a tendency to build feature-centric projects rather than following a user-centered design, ignoring the necessity of usability in the resulting product. While there are many reasons behind this, the main cause can be stated as the lack of awareness of usability from developers{\textquoteright} point of view and little interaction of project stakeholders with Human-Computer Interaction (HCI) studies. This chapter examines different types of collaboration methods of usability experts and developers focusing particularly on open source projects, together with potential issues envisaged during the communication phases. The chapter also focuses on the collaboration trends and patterns of HCI experts, developers and users with an emphasis on concerns related to inefficient exploitation of current tools and technologies and provide an open usability engineering method which could be exploited in distributed projects},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009070102},
	author = {G{\"o}rkem {\c C}etin and G{\"o}kt{\"u}rk, Mehmet}
}
@article {1241,
	title = {Collaborative Software Development Using R-Forge},
	journal = {The R Journal},
	volume = {1},
	number = {1},
	year = {2009},
	month = {05/2009},
	pages = {9-14},
	abstract = {Open source software (OSS) is typically created in a decentralized self-organizing process by a community of developers having the same or similar interests (see the famous essay by Raymond, 1999). A key factor for the success of OSS over the last two decades is the Internet: Developers who rarely meet face-to-face can employ new means of communication, both for rapidly writing and deploying software (in the spirit of Linus Torvald{\textquoteright}s {\textquotedblleft}release early, release often paradigm{\textquotedblright}). Therefore, many tools emerged that assist a collaborative software development process, including in particular tools for source code management (SCM) and version control.
In the R world, SCM is not a new idea; in fact, the R Development Core Team has always been using SCM tools for the R sources, first by means of Concurrent Versions System (CVS, see Cederqvist et al., 2006), and then via Subversion (SVN, see Pilato et al., 2004). A central repository is hosted by ETH Zürich mainly for managing the development of the base R system. Mailing lists like R-help, R-devel and many others are currently the main communication channels in the R community.
First, we present the core features that R- Forge offers to the R community. Second, we give a hands-on tutorial on how users and developers can get started with R-Forge. In particular, we illustrate how people can register, set up new projects, use R- Forge{\textquoteright}s SCM facilities, provide their packages on R-Forge, host a project-specific website, and how package maintainers submit a package to the Compre- hensive R Archive Network (CRAN, http://CRAN. R-project.org/). Finally, we summarize recent developments and give a brief outlook to future work.},
	keywords = {forge, R, scm, source code repositories, statistics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rjournal.pdf},
	author = {Stefan Theu{\ss}l and Achim Zeileis}
}
@conference {1264,
	title = {The Commit Size Distribution of Open Source Software},
	booktitle = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	note = {"We use the database of the open source analytics firm Ohloh Inc."
"This article is based on a March 2008 database snapshot, which contains 9,363 completely crawled and analyzed projects covering a time frame from January 1990 to February 2008."
"The Ohloh database provides the complete configuration management history of each crawled project (to the extent available on the web). Thus, every single commit action of all the projects over their entire history is available."
"We measure the size of commits in this paper in source lines of code (SLoC) using Ohloh{\textquoteright}s own open source diff too"},
	pages = {1 - 8},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, Hawaii, USA},
	abstract = {With the growing economic importance of open source, we need to improve our understanding of how open source software development processes work. The analysis of code contributions to open source projects is an important part of such research. In this paper we analyze the size of code contributions to more than 9,000 open source projects. We review the total distribution and distinguish three categories of code contributions using a size-based heuristic: single focused commits, aggregate team contributions, and repository refactorings. We find that both the overall distribution and the individual categories follow a power law. We also suggest that distinguishing these commit categories by size will benefit future analyses.},
	keywords = {commits, configuration management, history, lines of code, sloc, source code},
	isbn = {978-0-7695-3450-3},
	doi = {10.1109/HICSS.2009.421},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-07.pdf},
	author = {Arafat, O. and Dirk Riehle}
}
@article {1349,
	title = {Communication Network Characteristics of Open Source Communities},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {26 - 48},
	abstract = {Empirical research has shown that social network structure is a critical success factor for various kinds of work groups. The authors extended this research to a new type of work group{\textemdash}the open source software project community{\textemdash}with the objective of exploring the role of communication networks within these intriguing projects. Using archival data from 143 open source project groups, the authors compiled six measures of social network structure and analyzed these in relation to four measures of group success. This study found that the social network structures of these project communities did not appear to be critical success factors at all, but rather they had no significant impact on success or their effect was opposite of that seen in prior studies of work groups. Various conjectures were suggested that might explain these results, offering opportunities for further research.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009100102},
	author = {Hinds, David and Lee, Ronald M.}
}
@article {1414,
	title = {Competition and production of digital public goods},
	journal = {International Journal of Intelligent Control and Systems},
	volume = {14},
	number = {1},
	year = {2009},
	pages = {77-86},
	chapter = {77},
	abstract = {With the Internet has come the phenomenon of people volunteering to work on digital public goods such as open source software and online encyclopedia articles. Presumably, the success of individual public goods has an effect on attracting volunteers. However, the definition of success is ill-defined. This paper explores the impact of different success metrics on a simple public goods model. The findings show that the different success metrics considered do have an impact on the behavior of the model, with the largest differences being between consumer-oriented and producer-oriented metrics. This indicates that many proposed success metrics may be mapped into one of these two categories and within a category, all success metrics measure the same phenomenon. We argue that the characteristics of producer-oriented metrics more closely match real world phenomena, indicating that public goods are driven by producer, and not consumer, interests.},
	keywords = {digital public goods, FLOSS, open source software, sourceforge, success metrics, wikipedia},
	url = {http://www.public.asu.edu/~majansse/pubs/ijics2009.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ijics2009.pdf},
	author = {Radtke, Nicholas P. and Janssen, Marco A.}
}
@article {1341,
	title = {Consumer Welfare and Market Structure in a Model of Competition between Open Source and Proprietary Software},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {43 - 65},
	abstract = {I consider a Vickrey-Salop model of spatial product differentiation with quasi-linear utility functions and contrast two modes of production, the proprietary model where entrepreneurs sell software to the users, and the open source model where users participate in software development. I show that the OS model of production may be more efficient from the point of view of welfare than the proprietary model, but that an OS industry is vulnerable to entry by entrepreneurs while a proprietary industry can resist entry by OS projects. A mixed industry where OS and proprietary development methods coexist may exhibit large OS projects cohabiting with more specialized proprietary projects, and is more efficient than the proprietary model of production from the point of view of welfare.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009040104},
	author = {Gaudeul, Alexia}
}
@article {1347,
	title = {A Cost Model of Open Source Software Adoption},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {60 - 82},
	abstract = {A limited budget for IT may lock public bodies in obsolete inefficient solutions slowing down their process of innovation. Various actions of estimating, controlling, and reducing IT costs have been already performed at national and European levels and Open Source Software (OSS) has been often pointed as a promising alternative that may also render public services and the underlying business processes more transparent and accessible to citizens. In this chapter, we propose a model of cost of a migration to OSS as a decision making instrument that helps public bodies being autonomous and independent in the IT adoption. The model is empirically validated in the real daily operations of more than 3,500 users. If adopted systematically our model might be a powerful tool to support transformational government and to establish an empirical open knowledge base on the economic advantages of OSS on which to found future strategies of OSS adoption.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009070105},
	author = {Russo, Barbara and Succi, Giancarlo}
}
@conference {581,
	title = {Customization of Open Source Software in Companies},
	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 = {129 - 142},
	publisher = {Springer},
	organization = {Springer},
	chapter = {13},
	abstract = {Most papers related to Open Source Software (OSS) discuss the development of OSS, licensing issues, and motivations of developers. Research in the area of customization of OSS is rare, however. The process after the deployment of an OSS within a company remains unknown. There is a danger that it is often unstructured and error-prone since OSS develops in a more complex way than proprietary software. Based on our literature study, modifications of open source code do occur also in organizations outside of the software industry. Customization of applications is more common than customization of infrastructure software in these organizations. Therefore, we examine the process of deployment and adaptation of an OSS application software over several update iterations in great detail. This examination shows that this process has similarities with the process of deployment of proprietary software but it also exhibits important differences. Based on this case study, we also suggest a process model for customization of OSS applications in user organizations.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_13},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Customization\%20of\%20Open\%20Source\%20Software.pdf},
	author = {Ke{\ss}ler, Steffen and Alpar, Paul}
}
@conference {572,
	title = {Design Evolution of an Open Source Project Using an Improved Modularity Metric},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {20 - 33},
	publisher = {Springer},
	organization = {Springer},
	chapter = {4},
	abstract = {Modularity of an open source software code base has been associated with community growth, incentives for voluntary contribution, and a reduction in free riding. As a theoretical construct, it links open source software to other domains of research, including organization theory, the economics of industry structure, and new product development; however, measuring the modularity of an open source software design has proven difficult, especially for large and complex systems. Building on previous work on Design Structure Matrices (DSMs), this paper describes two contributions towards a method for examining the evolving modularity of large-scale software systems: (1) an algorithm and new modularity metric for comparing code bases of different size; and (2) evolution analysis of Apache Tomcat to illustrate the insights gained from this approach. Over a ten-year period, the modularity of Tomcat continually increased, except in three instances: with each major change to the architecture or implementation, modularity first declined, then increased in the subsequent version to fully compensate for the decline.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Design\%20Evolution\%20of\%20an\%20Open\%20Source\%20Project.pdf},
	author = {Milev, Roberto and Muegge, Steven and Weiss, Michael}
}
@conference {1244,
	title = {Design Information Sharing Across Multiple Knowledge Systems in a FLOSS Community},
	booktitle = {iConference {\textquoteright}09},
	year = {2009},
	month = {02/2009},
	abstract = {This paper explores support for design information sharing between the distinct knowledge systems and skill sets of interactive system designers and developers. The paper focuses on the challenges of sharing information among groups of designers, developers, and users with multiple knowledge systems in the context of free/libre/open source software (FLOSS) communities. Bringing design to FLOSS communities introduces new knowledge into a solitary community of practice, and discussion ensues about how exploiting the {\textquoteright}symmetry of ignorance{\textquoteright} can enhance information sharing through design in CodePlex, an open source project hosting community website. Finally, design mockups illustrate how CodePlex serves as a boundary object supporting design information sharing across distinct knowledge systems.},
	keywords = {codeplex, developers, information sharing},
	attachments = {https://flosshub.org/sites/flosshub.org/files/finalDraft41.pdf},
	author = {Bach, Paula}
}
@article {Subramaniam:2009:DOS:1480545.1480824,
	title = {Determinants of open source software project success: A longitudinal study},
	journal = {Decis. Support Syst.},
	volume = {46},
	year = {2009},
	month = {January},
	pages = {576{\textendash}585},
	publisher = {Elsevier Science Publishers B. V.},
	address = {Amsterdam, The Netherlands, The Netherlands},
	abstract = {In this paper, we investigate open source software (OSS) success using longitudinal data on OSS projects. We find that restrictive OSS licenses have an adverse impact on OSS success. On further analysis, restrictive OSS license is found to be negatively associated with developer interest, but is positively associated with the interest of non-developer users and project administrators. We also show that developer and non-developer interest in the OSS project and the project activity levels in any time period significantly affect the project success measures in subsequent time period. The implications of our findings for OSS research and practice are discussed. },
	keywords = {contributors, developers, licenses, longitudinal study, Open source project, OSS, project success, restrictive, Software project success},
	issn = {0167-9236},
	doi = {10.1016/j.dss.2008.10.005},
	url = {http://portal.acm.org/citation.cfm?id=1480545.1480824},
	author = {Subramaniam, Chandrasekar and Sen, Ravi and Nelson, Matthew L.}
}
@article {1346,
	title = {Discourses on User Participation},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {44 - 59},
	abstract = {Users should participate in information technology (IT) artifact development, but it has proven to be challenging. This applies also in the open source software (OSS) development. This chapter critically examines discursive construction of user participation in academic literatures and in practice, in IT artifact development. First three academic discourses constructing user participation are discussed. Then the discursive construction of user participation is explored in OSS development literature. Afterwards, results from several empirical, interpretive case studies are outlined. Some of them have been carried out in the IT artifact product development organizations, others in the OSS development context. Clear similarities can be identified in the discourses constructing user participation in these divergent IT artifact development contexts. The academic discourses on user participation clearly also legitimate certain ways of constructing user participation in practice. The OSS development literature bears resemblance mainly with the Human Computer Interaction (HCI) discourse on user participation. Therefore, it is argued that especially the HCI community should carefully reflect on what kinds of discourses on user participation it advocates and deems as legitimate.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009070104},
	author = {Iivari, Netta}
}
@conference {571,
	title = {Domain Drivers in the Modularization of FLOSS Systems},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {3 - 19},
	publisher = {Springer},
	organization = {Springer},
	chapter = {3},
	abstract = {The classification of software systems into types has been achieved in the past by observing both their specifications and behavioral patterns: the SPE classification, for instance, and its further supplements and refinements, has identified the S-type (i.e., fully specified), the P-type (i.e., specified but dependent on the context) and the E-type (i.e., addressing evolving problems) among the software systems. In order to detect types, and establish similarities, among Free/Libre/Open Source Software (FLOSS) systems, this paper considers three modular characteristics (functions, files and folders) and their evolution: how they are evolving with size, if they are constant across systems, and whether recurring evolutionary patterns are observed. Using these various-grained characteristics,a set of models for the evolution of modularization are extracted from evolving systems, and then used to extract similarities and types from a wide sample of FLOSS projects. This paper provides three contributions: first, it shows that several models are needed to encompass the variety of modularization patterns; second, it provides three types of models (uni-variate, bi-variate and tri-variate) for the evolution of modularization, with significant goodness-of-fit{\textquoteright}s. Finally, it shows that two of these patterns alone can interpolate the modular characteristics of the vast majority of a random choice of FLOSS projects.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Domain\%20Drivers\%20in\%20the\%20Modularization.pdf},
	author = {Capiluppi, Andrea}
}
@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.}
}
@conference {856,
	title = {Facts or Friends? Distinguishing Informational and Conversational Questions in Social QnA Sites (forthcoming)},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2009},
	author = {Harper, F. Maxwell and Moy, D. and Konstan, J.A.}
}
@conference {600,
	title = {First International Workshop on Building Sustainable Open Source Communities (OSCOMM 2009)},
	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 = {353 - 354},
	publisher = {Springer},
	organization = {Springer},
	chapter = {32},
	abstract = {The First International Workshop on Building Sustainable Open Source Communities aims at building a community of researchers and practitioners to share experiences and discuss challenges involved in building and maintaining open source communities.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_32},
	attachments = {https://flosshub.org/sites/flosshub.org/files/First\%20International\%20Workshop.pdf},
	author = {Hammouda, Imed and Aaltonen, Timo and Capiluppi, Andrea}
}
@conference {1203,
	title = {Flat for the few, steep for the many: Structural cohesion as  a measure of hierarchy in FLOSS communities},
	booktitle = {4th Workshop on Public Data about Software Development (WoPDaSD 2009)},
	year = {2009},
	note = {"The FLOSS project selected as case study is the GNOME web browser Epiphany. The communication network was  generated tracing backwards mail threads in the development mailing list. "},
	month = {2009},
	abstract = {A discrepancy exists between the emphasis posed by practitioners on decentralized and non-hierarchical communication in Free/Libre Open Source Software (FLOSS) communities and empirical evidence of their hierarchical structure. In order to explain this apparent paradox it is here hypothesized that in FLOSS communities local sub-groups exist and are less hierarchical, more decentralized than the whole social network to which they belong. A measure of structural cohesion based on network node connectivity is proposed as an effective method to test whether FLOSS communication networks can be decomposed in nested hierarchies of progressively less centralized sub-groups. Preliminary results from a case study that are consistent with the hypothesis are presented and discussed. },
	keywords = {case study, email, email archives, epiphany, gnome, mailing list, social network analysis},
	attachments = {https://flosshub.org/sites/flosshub.org/files/guido-conaldi-flat-for-the-few.pdf},
	author = {Guido Conaldi}
}
@conference {589,
	title = {FLOSS UX Design: An Analysis of User Experience Design in Firefox and OpenOffice.org},
	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 = {237 - 250},
	publisher = {Springer},
	organization = {Springer},
	chapter = {21},
	abstract = {We describe two cases of open user experience (UX) design using the Firefox web browser and OpenOffice.org office suite as case studies. We analyze the social complexity of integrating UX practices into the two open source projects using activity awareness, a framework for understanding team performance in collective endeavors of significant scope, duration, and complexity. The facets of activity awareness are common ground, community of practice, social capital, and human development. We found that differences between the communities include different strategies for community building, UX status in the community, type of open UX design, and different ways to share information.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_21},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Floss\%20UX\%20Desing.pdf},
	author = {Bach, Paula and Carroll, John}
}
@article {1343,
	title = {A Framework for Understanding the Open Source Revolution},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {1 - 16},
	abstract = {Traditional software engineering methodologies have mostly evolved from the environment of proprietary, large-scale software systems. Here, software design principles operate within a hierarchical decision-making context. Development of banking, enterprise resource and complex weapons systems all fit this paradigm. However, another paradigm for developing software-intensive systems has emerged, the paradigm of open source software. Although from a traditional perspective open source projects might look like chaos, their real-world results have been spectacular. This chapter presents open source software development as a fundamentally new paradigm driven by economics and facilitated by new processes. The new paradigm{\textquoteright}s revolutionary aspects are explored, a framework for describing the massive impact brought about by the new paradigm is proposed, and directions of future research are outlined. The proposed framework{\textquoteright}s goals are to help the understanding of the open source paradigm as a new economic revolution and stimulate research in designing open source software.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009070101},
	author = {Elpern, Jeff and Dascalu, Sergiu}
}
@conference {936,
	title = {From work to word: How do software developers describe their work?},
	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 = {121 - 130},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Developers take notes about their work sessions, either to remember the work status and share it with collaborators, or because employers explicitly require this for project management matters. We report on an exploratory study which aims at understanding how software developers describe their work. We analyzed more than 750,000 work descriptions of about 2,000 professionals taken over 8 years in three settings. We observed several similarities in the content and time meta-data of work descriptions. Most frequent terms, such as top-30 performed activities, are used consistently. Particular templates such as ldquoACTION concerning ARTIFACT because of CAUSErdquo occur frequently. Developers described sessions that last 30-120 min. 4-16 times a day. Maintaining diaries seems to consume between 3-6\% of the total work time, and in 10\% of the sessions, developers did not describe their work in sufficient detail. We argue that our results make the first step towards automatically generating work diaries for software developers.},
	keywords = {apache, developers, diaries, eureka, mycomp, scm, work management system},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069490},
	author = {Maalej, Walid and Happel, Hans-Jorg}
}
@conference {594,
	title = {Group Maintenance Behaviors of Core and Peripherial Members of Free/Libre Open Source Software Teams},
	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 = {298 - 309},
	publisher = {Springer},
	organization = {Springer},
	chapter = {26},
	abstract = {Group Maintenance is pro-social, discretionary, and relation-building behavior that occurs between members of groups in order to maintain reciprocal trust and cooperation. This paper considers how Free/libre Open Source Software (FLOSS) teams demonstrate such behaviors within the context of e-mail, as this is the primary medium through which such teams communicate. We compare group maintenance behaviors between both core and peripheral members of these groups, as well as behaviors between a group that remains producing software today and one which has since dissolved. Our findings indicate that negative politeness tactics (those which show respect for the autonomy of others) may be the most instrumental group maintenance behaviors that contribute to a FLOSS group{\textquoteright}s ability to survive and continue software production.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_26},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Group\%20Maintenance\%20Behavior.pdf},
	author = {Scialdone, Michael and Li, Na and Robert Heckman and Kevin Crowston}
}
@conference {578,
	title = {Heartbeat: Measuring Active User Base and Potential User Interest in FLOSS Projects},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {94 - 104},
	publisher = {Springer},
	organization = {Springer},
	chapter = {10},
	abstract = {This paper presents a novel method and algorithm to measure the size of an open source project{\textquoteright}s user base and the level of potential user interest that it generates. Previously unavailable download data at a daily resolution confirms hypothesized patterns related to release cycles. In short, regular users rapidly download the software after a new release giving a way to measure the active user base. In contrast, potential new users download the application independently of the release cycle, and the daily download figures tend to plateau at this rate when a release has not been made for some time. An algorithm for estimating these measures from download time series is demonstrated and the measures are examined over time in two open source projects.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_10},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Heatbeat\%20Measuring\%20Active\%20Use.pdf},
	author = {Andrea Wiggins and Howison, James and Kevin Crowston}
}
@conference {570,
	title = {How Open Source Can Still Save the World},
	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 = {2 },
	chapter = {2},
	abstract = {Many of the worlds{\textquoteright} major problems - economic distress, natural disaster responses, broken health care systems, education crises, and more - are not fundamentally information technology issues. However, in every case mentioned and more, there exist opportunities for Open Source software to uniquely change the way we can address these problems. At times this is about addressing a need for which no sufficient commercial market exists. For others, it is in the way Open Source licenses free the recipient from obligations to the creators, creating a relationship of mutual empowerment rather than one of dependency. For yet others, it is in the way the open collaborative processes that form around Open Source software provide a neutral ground for otherwise competitive parties to find a greatest common set of mutual needs to address together rather than in parallel. Several examples of such software exist today and are gaining traction. Governments, NGOs, and businesses are beginning to recognize the potential and are organizing to meet it. How far can this be taken?
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_2},
	attachments = {https://flosshub.org/sites/flosshub.org/files/How\%20Open\%20Source\%20Can\%20Still\%20Save\%20the\%20World.pdf},
	author = {Behlendorf, Brian}
}
@article {Beecher2009739,
	title = {Identifying exogenous drivers and evolutionary stages in FLOSS projects},
	journal = {Journal of Systems and Software},
	volume = {82},
	number = {5},
	year = {2009},
	pages = {739 - 750},
	abstract = {The success of a Free/Libre/Open Source Software (FLOSS) project has been evaluated in the past through the number of commits made to its configuration management system, number of developers and number of users. Most studies, based on a popular FLOSS repository (SourceForge), have concluded that the vast majority of projects are failures. This study{\textquoteright}s empirical results confirm and expand conclusions from an earlier and more limited work. Not only do projects from different repositories display different process and product characteristics, but a more general pattern can be observed. Projects may be considered as early inceptors in highly visible repositories, or as established projects within desktop-wide projects, or finally as structured parts of FLOSS distributions. These three possibilities are formalized into a framework of transitions between repositories. The framework developed here provides a wider context in which results from FLOSS repository mining can be more effectively presented. Researchers can draw different conclusions based on the overall characteristics studied about an Open Source software project{\textquoteright}s potential for success, depending on the repository that they mine. These results also provide guidance to OSS developers when choosing where to host their project and how to distribute it to maximize its evolutionary success.},
	keywords = {developers, forge, forges, repositories, repository, scm, software repositories, sourceforge, success, users},
	issn = {0164-1212},
	doi = {DOI: 10.1016/j.jss.2008.10.026},
	url = {http://www.sciencedirect.com/science/article/B6V0N-4TVTJFS-1/2/e32ecee1bcb54bd4a5dff6d5e3daca8d},
	author = {Karl Beecher and Capiluppi, Andrea and Boldyreff, Cornelia}
}
@article {1352,
	title = {Identifying How Determinants Impact Security-Based Open Source Software Project Success Using Rule Induction},
	journal = {International Journal of Electronic Marketing and Retailing},
	volume = {2},
	number = {4},
	year = {2009},
	month = {2009},
	pages = {352-362},
	author = {Wray, Barry and Mathieu, Richard and Teets, J.}
}
@conference {580,
	title = {The Importance of External Support in the Adoption of Open Source Server Software},
	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 = {116 - 128},
	publisher = {Springer},
	organization = {Springer},
	chapter = {12},
	abstract = {IT managers seem to be hesitant to adopt OSS in the absence of professional support. Previous qualitative studies have indeed suggested that the availability of external support is important for the adoption of OSS. Therefore, we feel it is interesting to gain more insight into the role of external support in the adoption process. To this end, we performed a web survey involving 95 Belgian organizations. Our data suggests a balanced picture. As expected, our results show that the majority of organizations in our sample rely on commercial support such as vendor or third party support. Even organizations that have deployed OSS to a large extent{\textemdash}and that are therefore likely to have some experience and familiarity with OSS{\textemdash}rely on commercial support. Nevertheless, a considerable proportion of organizations indicated not to rely on commercial support, which suggests that internal expertise can be sufficient for successful adoption. Finally, and most surprisingly, we have found that the OSS community is used by a large proportion of organizations. This indicates that the OSS community is a valuable source of external support for organizations. Nevertheless, it appears that it is primarily used by organizations with a rather strong background in IT.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_12},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Importance\%20of\%20Extertnal\%20Support.pdf},
	author = {Ven, Kris and Verelst, Jan}
}
@article {1340,
	title = {Innovation, Imitation and Open Source},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {28 - 42},
	abstract = {An extensive empirical literature indicates that, even without formal intellectual property rights, innovators enjoy a variety of first-mover advantages and that {\textquoteleft}imitation{\textquoteright} is itself a costly activity. There is also accumulating evidence that an {\textquoteleft}open{\textquoteright} approach to knowledge production can deliver substantial efficiency advantages. This article introduces a formal framework incorporating all of these factors. We examine the relative performance of an {\textquoteleft}open{\textquoteright} versus a {\textquoteleft}closed{\textquoteright} (proprietary) regime, and explicitly characterize the circumstances in which an open approach, despite its effect on facilitating imitation, results in a higher level of innovation.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009040103},
	author = {Pollock, Rufus}
}
@conference {590,
	title = {Integrating HCI Specialists into Open Source Software Development Projects},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {251 - 263},
	publisher = {Springer},
	organization = {Springer},
	chapter = {22},
	abstract = {Typical open source software (OSS) development projects are organized around technically talented developers, whose communication is based on technical aspects and source code. Decision-making power is gained through proven competence and activity in the project, and non-technical end-user opinions are too many times neglected. In addition, also human-computer interaction (HCI) specialists have encountered difficulties in trying to participate in OSS projects, because there seems to be no clear authority and responsibility for them. In this paper, based on HCI and OSS literature, we introduce an extended OSS development project organization model that adds a new level of communication and roles for attending human aspects of software. The proposed model makes the existence of HCI specialists visible in the projects, and promotes interaction between developers and the HCI specialists in the course of a project.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_22},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Intergrating\%20HCI\%20Specialists.pdf},
	author = {Hedberg, Henrik and Iivari, Netta}
}
@article {1231,
	title = {Integrating Projects from Multiple Open Source Code Forges},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	month = {31/2009},
	pages = {46 - 57},
	abstract = {Much of the data about free, libre, and open source (FLOSS) software development comes from studies of code forges or code repositories used for managing projects. This paper presents a method for integrating data about open source projects by way of matching projects (entities) across multiple code forges. After a review of the relevant literature, a few of the methods are chosen and applied to the FLOSS domain, including a comparison of some simple scoring systems for pairwise project matches. Finally, the paper describes limitations of this approach and recommendations for future work.},
	keywords = {data integration, forges},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009010103},
	author = {Squire, Megan}
}
@proceedings {845,
	title = {Intellectual Property Rights Requirements for Heterogeneously Licensed Systems},
	year = {2009},
	month = {09/2009},
	address = {Atlanta, GA},
	author = {Alspaugh, Thomas and Hazeline U. Asuncion and Walt Scacchi}
}
@conference {602,
	title = {A Joint Workshop of QACOS and OSSPL},
	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 = {357 - 358},
	publisher = {Springer},
	organization = {Springer},
	chapter = {34},
	abstract = {The OSS movement, which originated from a pragmatic need to share code among individuals, has grown to become a major force behind inter-organizational reuse of platforms, components and code. The use of open source software to build single or family of systems (i.e., product line development) appears to be a profitable way to quality software products. On the other hand, because of the diverse use of open source software, product line development is an attractive way of working in open source
communities. The configuration mechanisms used in open source communities may be applicable within software product lines variability management. In addition, product line organizations are usually involved in distributed development, which works very efficiently within open source communities, leading to high quality products. However, at present, there is limited interaction between the open source and product line development communities.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_34},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Joint\%20Workshop\%20of\%20QACOS.pdf},
	author = {Ali Babar, Muhammad and Lundell, Bj{\"o}rn and van der Linden, Frank}
}
@conference {844,
	title = {A Jury of Your Peers: Quality, Experience and Ownership in Wikipedia},
	booktitle = {The International Symposium on Wiki{\textquoteright}s and Open Collaboration},
	year = {2009},
	month = {10/2009},
	address = {Orlando, FL},
	keywords = {experience,, ownership,, peer, peer,, quality, review,, wikipedia,, wikiwork,},
	author = {Halfaker, A. and Kittur, N. and Kraut, R. and Riedl, J.}
}
@conference {1204,
	title = {Language entropy: A metric for characterization of author programming language distribution},
	booktitle = {4th Workshop on Public Data about Software Development (WoPDaSD 2009)},
	year = {2009},
	note = {The data set used in this study was previously collected for a separate, but related work. It was originally extracted from the SourceForge Research Archive (SFRA), August 2006. For a detailed discussion of the data source, collection tools and processes, and summary statistics, see [6]."

"From the initial data set we extracted a random sample of 500 developers3 along with descriptive details of all revisions that those developers made since the inception of the projects on which they worked. We then condensed this sample by totaling the lines of code added by each developer for each month in which that developer made at least one code submission."
[6] Daniel P. Delorey, Charles D. Knutson, and Alex MacLean. Studying production phase sourceforge projects: A case study using cvs2mysql and sfra+. In Second International Workshop on Public Data about Software Development (WoPDaSD {\textquoteright}07), June 2007.},
	month = {2009},
	abstract = {Programmers are often required to develop in multiple languages. In an effort to study the effects of programming language fragmentation on productivity{\textemdash}and ultimately on a programmer{\textquoteright}s problem solving abilities{\textemdash}we propose a metric, language entropy, for characterizing the distribution of an individual{\textquoteright}s development efforts across multiple programming languages. To evaluate this metric, we present an observational study examining all project contributions (through August 2006) of a random sample of 500 SourceForge developers. Using a random coefficients model, we found a statistically significant correlation (alpha level of 0.05) between language entropy and the size of monthly pro ject contributions (measured in lines of code added). Our results indicate that language entropy is a good candidate for characterizing author programing language distribution.},
	keywords = {contributions, developers, language entropy, lines of code, loc, multiple languages, programming languages, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LanguageEntropy-JonathanKrein.pdf},
	author = {Krein, Jonathan L. and MacLean, Alexander C. and Delorey, Daniel P. and Knutson, Charles D. and Eggett, Dennis L.}
}
@conference {944,
	title = {Learning from defect removals},
	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 = {179 - 182},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Recent research has tried to identify changes in source code repositories that fix bugs by linking these changes to reports in issue tracking systems. These changes have been traced back to the point in time when they were previously modified as a way of identifying bug introducing changes. But we observe that not all changes linked to bug tracking systems are fixing bugs; some are enhancing the code. Furthermore, not all fixes are applied at the point in the code where the bug was originally introduced. We flesh out these observations with a manual review of several software projects, and use this opportunity to see how many defects are in the scope of static analysis tools.},
	keywords = {bug fixing, bugzilla, change management, cherry, cvs, eclipse, groovy, launching, source code, svn, text editor},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069500},
	attachments = {https://flosshub.org/sites/flosshub.org/files/179LearnFromDefects-MSR09.pdf},
	author = {Ayewah, Nathaniel and Pugh, William}
}
@conference {842,
	title = {Learning to Recognize Valuable Tags},
	booktitle = {International Conference on Intelligent User Interfaces},
	year = {2009},
	month = {2/8/2009},
	publisher = {ACM},
	organization = {ACM},
	address = {Sanibel Island, FL},
	author = {Sen, S. and Vig, J. and Riedl, J.}
}
@conference {608,
	title = {Libre Software in Spanish Public Administrations},
	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 = {366 - 366},
	publisher = {Springer},
	organization = {Springer},
	chapter = {40},
	abstract = {Libre software started to be used in Public Administrations in Spain during the 1990s, in some isolated but interesting experiences.During the early 2000s, and specially in some regional governments, libre software started to be considered as an integral part of ITrelated policies. In 2007, it was evident that many experiences related to libre software were running in Public Administrations with different levels of success. However, no study had looked into the details of these experiences, and no comprehensive analysis had been performed to better understand the different factors that affect them.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_40},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Libre\%20Software.pdf},
	author = {Ortega, Felipe and Lafuente, Isabel and Gato, Jose and Gonz{\'a}lez-Barahona, Jes{\'u}s}
}
@conference {858,
	title = {Making New Friends, but Keep the Old - Recommending People on Social Networking Sites (forthcoming)},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2009},
	author = {Chen, J and Geyer, W. and Dugan, C. and Muller, M. and Guy, I.}
}
@conference {923,
	title = {MapReduce as a general framework to support research in Mining Software Repositories (MSR)},
	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 = {21 - 30},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Researchers continue to demonstrate the benefits of Mining Software Repositories (MSR) for supporting software development and research activities. However, as the mining process is time and resource intensive, they often create their own distributed platforms and use various optimizations to speed up and scale up their analysis. These platforms are project-specific, hard to reuse, and offer minimal debugging and deployment support. In this paper, we propose the use of MapReduce, a distributed computing platform, to support research in MSR. As a proof-of-concept, we migrate J-REX, an optimized evolutionary code extractor, to run on Hadoop, an open source implementation of MapReduce. Through a case study on the source control repositories of the Eclipse, BIRT and Datatools projects, we demonstrate that the migration effort to MapReduce is minimal and that the benefits are significant, as running time of the migrated J-REX is only 30\% to 50\% of the original J-REX{\textquoteright}s. This paper documents our experience with the migration, and highlights the benefits and challenges of the MapReduce framework in the MSR community.},
	keywords = {hadoop, mapreduce},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069477},
	attachments = {https://flosshub.org/sites/flosshub.org/files/21MSR2009-MSR-0114-Shang-Weiyi.pdf},
	author = {Weiyi Shang and Zhen Ming Jiang and Adams, Bram and Hassan, Ahmed E.}
}
@article {1252,
	title = {On the Maturity of Open Source BPM Systems},
	journal = {BP Trends},
	year = {2009},
	note = {"Figure 1 shows a snapshot (from 3rd of July 2008) of the most downloaded workflow and BPM systems distributed through a code repository. The systems in the figure are ordered historically with respect to month and year of their registration. The code repositories searched for this snapshot were SourceForge, RubyForge, ObjectWebForge, Tigris.org, BountySource, BerliOS, JavaForge and GNU Savannah"},
	month = {06/2009},
	pages = {(11 pages)},
	abstract = {Two major trends in the area of information systems development are the growing interest for Workflow and Busi- ness Process Management (BPM) systems and the increasing acceptance and spread of open source software. This development raises the following questions:
1. What are the prominent representatives of current open source Workflow and BPM systems? 2. What is the maturity level of these systems?
Seeking answers to these questions we have performed a study. First an overview of the existing open source systems was made and three systems: jBPM, OpenWFE, and Enhydra Shark, selected for further analysis. Then a detailed analysis on the selected systems was performed. The results from this analysis were documented and the developers invited to comment. Based on the feedback from the developers the results were revisited and the study finalized [5]. In this article we summarise the study and reflect on the area of open source BPM systems.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bpm.pdf},
	author = {Wohed, P. and ter Hofstede, A.H.M. and Russell, N. and Andersson, B. and van der Aalst, W.M.P}
}
@conference {1812,
	title = {Measuring the performance of open source development communities: The QualOSS approach},
	booktitle = {MetriKon 2009 - Praxis der Software-Messung : Tagungsband des DASMA Software Metrik Kongresses},
	year = {2009},
	abstract = {Free and Open Source Software (F/OSS) has an increasing importance for the software industry. Similar to traditional (closed) software acquisition, F/OSS acquisition requires an assessment of whether its quality is sufficient for the intended purpose, and of whether the chances of being maintained and supported in the future, as well as of keeping certain quality standards over time, are sufficiently high. The first one of these aspects is strictly product related, and can be assessed using techniques that are not specific to F/OSS. The last two aspects, however, are related to the community developing the software, and require novel approaches to be evaluated properly.
In this paper, we present an approach toward a comprehensive measurement framework for F/OSS projects, developed in the EU project QualOSS. Although this approach takes into account product quality as well as process maturity and sustainability of the underlying F/OSS community, we concentrate here on its community-related aspects. After describing our quality model and assessment techniques in some detail, we close with a description of our ongoing evaluation effort and a discussion of lessons learned.},
	url = {http://publica.fraunhofer.de/documents/N-117870.html},
	author = {Soto, Martin and Izquierdo-Cort{\'a}zar, Daniel and Ciolkowski, Marcus}
}
@conference {942,
	title = {On mining data across software repositories},
	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 = {171 - 174},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Software repositories provide abundance of valuable information about open source projects. With the increase in the size of the data maintained by the repositories, automated extraction of such data from individual repositories, as well as of linked information across repositories, has become a necessity. In this paper we describe a framework that uses web scraping to automatically mine repositories and link information across repositories. We discuss two implementations of the framework. In the first implementation, we automatically identify and collect security problem reports from project repositories that deploy the Bugzilla bug tracker using related vulnerability information from the National Vulnerability Database. In the second, we collect security problem reports for projects that deploy the Launchpad bug tracker along with related vulnerability information from the National Vulnerability Database. We have evaluated our tool on various releases of Fedora, Ubuntu, Suse, RedHat, and Firefox projects. The percentage of security bugs identified using our tool is consistent with that reported by other researchers.},
	keywords = {bug reports, bugzilla, Fedora, Firefox, htmlscraper, integration, launchpad, national vulnerability database, RedHat, Suse, tracker, Ubuntu},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069498},
	attachments = {https://flosshub.org/sites/flosshub.org/files/171MiningAcrossmsr09.pdf},
	author = {Anbalagan, Prasanth and Vouk, Mladen}
}
@proceedings {1645,
	title = {Mining Programming Language Vocabularies from Source Code},
	year = {2009},
	pages = {12 pp},
	abstract = {We can learn much from the artifacts produced as the by-products of software devel- opment and stored in software repositories. Of all such potential data sources, one of the most important from the perspective of program comprehension is the source code itself. While other data sources give insight into what developers intend a program to do, the source code is the most accurate human-accessible description of what it will do. However, the ability of an individual developer to comprehend a particular source file depends directly on his or her familiarity with the specific features of the programming language being used in the file. This is not unlike the difficulties second-language learners may encounter when attempting to read a text written in a new language. We propose that by applying the techniques used by corpus linguists in the study of natural language texts to a corpus of programming language texts (i.e., source code repositories), we can gain new insights into the communication medium that is programming language. In this paper we lay the foundation for applying corpus linguistic methods to programming language by 1) defining the term {\textquotedblleft}word{\textquotedblright} for programming language, 2) developing data collection tools and a data storage schema for the Java programming language, and 3) presenting an initial analysis of an example linguistic corpus based on version 1.5 of the Java Developers Kit.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/21st-delorey.pdf},
	author = {Delorey, Daniel P. and Knutson, Charles D. and Davies, Mark}
}
@conference {935,
	title = {Mining search topics from a code search engine usage log},
	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 = {111 - 120},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {We present a topic modeling analysis of a year long usage log of Koders, one of the major commercial code search engines. This analysis contributes to the understanding of what users of code search engines are looking for. Observations on the prevalence of these topics among the users, and on how search and download activities vary across topics, leads to the conclusion that users who find code search engines usable are those who already know to a high level of specificity what to look for. This paper presents a general categorization of these topics that provides insights on the different ways code search engine users express their queries. The findings support the conclusion that existing code search engines provide only a subset of the various information needs of the users when compared to the categories of queries they look at.},
	keywords = {analysis, black duck, koders, log, logfile, search, source code},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069489},
	author = {Bajracharya, Sushil and Lopes, Cristina}
}
@conference {928,
	title = {Mining source code to automatically split identifiers for software analysis},
	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 = {71 - 80},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Automated software engineering tools (e.g., program search, concern location, code reuse, quality assessment, etc.) increasingly rely on natural language information from comments and identifiers in code. The first step in analyzing words from identifiers requires splitting identifiers into their constituent words. Unlike natural languages, where space and punctuation are used to delineate words, identifiers cannot contain spaces. One common way to split identifiers is to follow programming language naming conventions. For example, Java programmers often use camel case, where words are delineated by uppercase letters or non-alphabetic characters. However, programmers also create identifiers by concatenating sequences of words together with no discernible delineation, which poses challenges to automatic identifier splitting. In this paper, we present an algorithm to automatically split identifiers into sequences of words by mining word frequencies in source code. With these word frequencies, our identifier splitter uses a scoring technique to automatically select the most appropriate partitioning for an identifier. In an evaluation of over 8000 identifiers from open source Java programs, our Samurai approach outperforms the existing state of the art techniques.},
	keywords = {java, samurai, sourceforge},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069482},
	attachments = {https://flosshub.org/sites/flosshub.org/files/71EnslenandHillandPollockandVijayShanker.pdf},
	author = {Enslen, Eric and Hill, Emily and Pollock, Lori and Vijay-Shanker, K.}
}
@conference {932,
	title = {Mining the coherence of GNOME bug reports with statistical topic models},
	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 = {99 - 102},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {We adapt latent Dirichlet allocation to the problem of mining bug reports in order to define a new information-theoretic measure of coherence. We then apply our technique to a snapshot of the GNOME Bugzilla database consisting of 431,863 bug reports for multiple software projects. In addition to providing an unsupervised means for modeling report content, our results indicate substantial promise in applying statistical text mining algorithms for estimating bug report quality. Complete results are available from our supplementary materials Web site at http://sourcerer.ics.uci.edu/msr2009/gnome_coherence.html.},
	keywords = {bug reports, bugzilla, gnome, msr challenge, quality, sourcerer},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069486},
	author = {Linstead, Erik and Baldi, Pierre}
}
@article {1118,
	title = {Monetary donations to an open source software platform},
	journal = {Research Policy},
	volume = {38},
	year = {2009},
	month = {03/2009},
	pages = {404 - 414},
	abstract = {Online open source software platforms, such as Sourceforge.net, play a vital role in creating an ecosystem that enables the creation and growth of open source projects. However, there is little research exploring the interactions between open source stakeholders and the platform. We believe that the sustainability of the platform crucially depends on financial incentives. While platforms can obtain these incentives through multiple means, in this paper we focus on one form of financial incentives{\textemdash}voluntary monetary donations by open source community members. We report findings from two empirical studies that examine factors that impact donations. Study 1 investigates the factors that cause some community members to donate and not others. We find that the decision to donate is impacted by relational commitment with open source software platform, donation to projects and accepting donations from others. Study 2 examines what drives the level of donation. We find that the length of association with the platform and relational commitment affects donation levels.},
	keywords = {Collective action, Donation, Identification, incentives, metadata, MOTIVATION, Open source software platform, projects, Reciprocity, Relational commitment, sourceforge},
	issn = {00487333},
	doi = {10.1016/j.respol.2008.11.004},
	author = {Sandeep Krishnamurthy and Tripathi, Arvind K.}
}
@article {1351,
	title = {Motivation of Open Source Developers},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {65 - 81},
	abstract = {The motivational drivers of open source software developers have been researched by various investigators since about 2000. This work shows that developers are motivated by different extrinsic and intrinsic drivers, among them community aspirations, reciprocity and fairness, creative impulses, and monetary and career ambitions. There has been some work done in studying whether the profile of developer motivations is constant across open source projects or is sensitive to project organizational design. Among the many factors that could influence the mix of motives of OS developers is the license under which the work is performed. Licenses range in openness between those such as the GNU GPL that severely restrict the freedom of developers to mingle their OS code with proprietary code to those such as BSD licenses which allow programmers much greater latitude in integrating open source code with proprietary code. In addition to formal rules, meritocracies emerge to reward effort and performance, and also to direct, coordinate, and control other participants. The authors discuss these variables and how they may be related to motivations.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009100104},
	author = {Allyn, Mark R. and Misra, Ram B.}
}
@conference {1263,
	title = {Multiple Social Networks Analysis of FLOSS Projects using Sargas},
	booktitle = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	note = {"The interval of analysis for the first three networks was from 2003/02/24 to 2003/11/03. These networks were created using the OSSNetwork tool [18]. The source code of the PMD project was collected starting on 2002/06/24..."
"Transflow performs a co-changes analysis of the source code modification history and creates a matrix where software components are connected by taking into account the frequency that they have been changed together (i.e., in the same check-in): if two files have been changed together in the same check-in, an edge is created to link these two files."},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, Hawaii, USA},
	abstract = {Due to their characteristics and claimed advantages, several researchers have been investigating free and open-source projects. Different aspects are being studied: for instance, what motivates developers to join FLOSS projects, the tools, processes and practices used in FLOSS projects, the evolution of FLOSS communities among other things. Researchers have studied collaboration and coordination of open source software developers using an approach known as social network analysis and have gained important insights about these projects. Most researchers, however, have not focused on the integrated study of these networks and, accordingly, in their interrelationships. This paper describes an approach and tool to combine multiple social networks to study the evolution of open-source projects. Our tool, named Sargas, allows comparison and visualization of different social networks at the same time. Initial results of our analysis can be used to extend the "onion-model" of open source participation.},
	keywords = {case study, multiple social networks, ossnetwork, pmd, social network analysis, transflow},
	isbn = {978-0-7695-3450-3},
	doi = {10.1109/HICSS.2009.316},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-06.pdf},
	author = {de Sousa, S.F. and Balieiro, M.A. and dos R. Costa, J.M. and de Souza, C.R.B.}
}
@conference {603,
	title = {NESSI OSS Workshop},
	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 = {359 - 360},
	publisher = {Springer},
	organization = {Springer},
	chapter = {35},
	abstract = {The NESSI Technology Platform aims to provide a unified view for European research and development in Services Architectures and Software Infrastructures that will define technologies for new, open, industrial solutions and societal applications that enhance the safety, security and well-being of citizens.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_35},
	attachments = {https://flosshub.org/sites/flosshub.org/files/NESSI\%20OSS\%20Workshop.pdf}
}
@article {1342,
	title = {Open Source and Commercial Software Platforms},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {67 - 80},
	abstract = {In this article, we consider the dynamics and competition between two software platforms (Open Source and proprietary software). Potential user-developers can adopt one of the two platforms in order to develop and sell new applications based on the platform. We consider the static issue first and then use a simple dynamic system where the dynamics comes from the development efforts (spillovers) made on each platforms. In this context, we first identify the conditions for the two platforms to coexist in the long run. From this baseline, we then consider different strategies for the editor. A first strategy is for the editor to {\textquotedblleft}show the code{\textquotedblright} of its software, so as to develop more compatible products. A second strategy is to strategically monitor the compatibility degree between the proprietary and OS platform. In both cases, we analyze whether a mixed industry may be sustainable in the long run.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009040105},
	author = {Darmon, Eric and Torre, Dominique}
}
@conference {569,
	title = {Open Source Is Changing the Way Work Gets Done},
	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 = {1 },
	publisher = {Springer},
	organization = {Springer},
	chapter = {1},
	abstract = {Open source software is changing not only the way the software industry works, but also the way work gets done. In the open source software model, individuals and companies collaborate together to produce software. They learn new ways of getting work done that are based on meritocracy and little management. In addition, they learn ways of communication that work well across large groups and virtual environments. These new ways of communicating and getting work done are changing the nature of work across all industries, not just the software industry, industries like mobile technology providers and medical equipment. Come learn how the open source software model is changing the way individuals and companies work and collaborate.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20is\%20Changing.pdf},
	author = {Peters, Stormy}
}
@article {1235,
	title = {Open Source Software Adoption: Anatomy of Success and Failure},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	number = {1},
	year = {2009},
	month = {01/2009},
	pages = {1-23},
	abstract = {Current estimates suggest widespread adoption of open source software (OSS) in organizations worldwide. However, the problematic nature of OSS adoption is readily evidenced in the fairly frequent reports of problems, unforeseen hold-ups, and outright abandonment of OSS implementation over time. Hibernia Hospital, an Irish public sector organization, have embarked on the adoption of a range of OSS applications over several years, some of which have been successfully deployed and remain in live use within the organisation, whereas others, despite achieving high levels of assimilation over a number of years, have not been ultimately retained in live use in the organization. Using a longitudinal case study, we discuss in depth the deployment process for two OSS applications {\textendash} the desktop application suite whose deployment was unsuccessful ultimately, and the email application which was successfully deployed. To our knowledge, this is the first such in-depth study into successful and unsuccessful OSS implementation.},
	keywords = {adoption, project failure, project success},
	doi = {10.4018/jossp.2009010101},
	author = {Fitzgerald, Brian}
}
@article {1339,
	title = {Open Source Software Governance Serving Technological Agility},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {14 - 27},
	abstract = {The development of open source software is currently arousing increasing interest in the IT world. This research inquires some specific paths enlarging the traditional view over open source software in inquiring the US Department of Defense (DoD) and the dynamics associated its front- and back-office activities. We explain how distinguishing basic administration from operational constraints and weapon R\&D dynamics introduces specific governance concerns among public and private stakeholders. By no longer defining open source solutions as mere goods, but as services characterized by a flow of knowledge, we particularly highlight new emerging strategies of technological acquisition. Our analysis leads to revise the traditional role focusing mainly on cost issues and introduces open source software with distinctive properties serving the management of innovation and technological agility at the level of complex systems, exemplified here with the constraints associated to weapon systems and the Network centric warfare doctrine},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009040102},
	author = {Le Texier, Thomas and Versailles, David W.}
}
@conference {575,
	title = {Opening Industrial Software: Planting an Onion},
	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 = {57 - 69},
	publisher = {Springer},
	organization = {Springer},
	chapter = {7},
	abstract = {This paper studies the problem of building open source communities for industrial software that was originally developed as closed source. We present a conceptual framework for planning the early stages of the release process highlighting the main stakeholders and concerns involved. The framework is illustrated by means of three industrial software platforms reporting first experiences of the community building process. In order to measure the effectiveness of the approach, the use of a quantitative and qualitative evaluation framework is advocated.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Opening\%20Industrial\%20Software.pdf},
	author = {Sirkkala, Petri and Aaltonen, Timo and Hammouda, Imed}
}
@conference {596,
	title = {Openness to Standard Document Formats in Swedish Public Sector Organisations},
	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 = {320 - 329},
	publisher = {Springer},
	organization = {Springer},
	chapter = {28},
	abstract = {There is a strong movement in Europe to promote products that support open, well-documented standards. Directives and proposals at European and national levels have been developed in this area. There is in particular an increasing recognition of the need for governmental organisations to support and promote standard document formats. This vision can stand in stark contrast with the reality of those document formats which can currently be accepted and produced by those organisations. In this paper we address the question: to what extent can and do Swedish governmental organisations respond appropriately when presented with a document in a format that conforms to an open standard? We find that a small minority of organisations can actually do so, whereas all are willing and able to accept documents in a proprietary format. The study also highlights a lack of transparency in organisations regarding formats which should be accepted and used for communication with the general public.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_28},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Openness\%20to\%20Standard\%20Document\%20Formats.pdf},
	author = {Lundell, Bj{\"o}rn and Lings, Brian}
}
@conference {611,
	title = {Panel: Governance in Open Source Projects and Communities},
	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 = {370 - 370},
	publisher = {Springer},
	organization = {Springer},
	chapter = {43},
	abstract = {{\textquotedblleft}Although considerable research has been devoted to the growth and expansion of open source communities and the comparison between the efficiency of corporate structures and community structures in the field of software development, rather less attention has been paid to their governance structures (control, monitoring, supervision){\textquotedblright} (Lattemann and Stieglitz 2005).
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_43},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Panel\%20Governnance.pdf},
	author = {Bolici, Francesco and de Laat, Paul and Ljungberg, Jan and Pontiggia, Andrea and Rossi Lamastra, Cristina}
}
@conference {610,
	title = {Panel: Open Source in the Public Sector},
	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 = {368 - 369},
	publisher = {Springer},
	organization = {Springer},
	chapter = {42},
	abstract = {Open Source Software (OSS) is becoming mainstream, and it is perhaps not surprising that public sector organisations seek to explore the potential of OSS in financially difficult times. Today, OSS has become an issue of strategic importance for many public sector organisations. In addition, related to OSS, many organisations and governments are also acknowledging Open Standards as important for addressing various lock-in scenarios.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_42},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Panel\%20Open\%20Source.pdf},
	author = {Lundell, Bj{\"o}rn and Amundsen, Morten and Ghosh, Rishab and Hardy, Jean-Luc and Sj{\"o}sw{\"a}rd, Per-Ola}
}
@article {Barcellini2009533,
	title = {Participation in online interaction spaces: Design-use mediation in an Open Source Software community},
	journal = {International Journal of Industrial Ergonomics},
	volume = {39},
	number = {3},
	year = {2009},
	note = {<ce:title>Selected papers from ECCE 2007, the 25th Anniversary Conference of the European Conference on Cognitive Ergonomics</ce:title>},
	pages = {533 - 540},
	abstract = {This research aims at characterizing emerging roles fostering design-use mediation during the Open Source Software (OSS) design process through the analysis of participation. Studying OSS is of particular interest: (1) to investigate socio-technical settings supporting user participation to the design process, which is considered to be the major strength of OSS design; (2) to gain insights into supporting the changing nature of the software industry, which is becoming more and more distributed and global, and which is thus increasingly making use of OSS design tools and methods. In this research, we characterized effective roles of participants, i.e. participation, on the basis of activities analysis in three online interaction spaces (discussion, documentation and implementation) during a continuous {\textquotedblleft}pushed-by-users{\textquotedblright} design process of the Python project. Participation is targeted through a methodology articulating: (1) structural analyses (organization of the discussions, regularity and involvement of participants, quotes-based social network) in usage-oriented and development-oriented mailing lists of the projects{\textquoteright} discussion space; (2) actions to the code and documentation made by participants in the implementation and documentation spaces. Besides the importance of the users{\textquoteright} contribution to the process, OSS design is fostered by some key-participants, the cross-participants, who act as boundary spanners between the developers and the users, helping them to go beyond some barriers to participation. These findings can be reinforced developing software to automate the structural analysis of discussions and actions to the code and documentation.},
	keywords = {Distributed participatory design},
	issn = {0169-8141},
	doi = {10.1016/j.ergon.2008.10.013},
	url = {http://www.sciencedirect.com/science/article/pii/S0169814108001637},
	author = {Barcellini, Flore and D{\'e}tienne, Fran{\c c}oise and Burkhardt, Jean-Marie}
}
@conference {593,
	title = {Peeling the Onion},
	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 = {284 - 297},
	publisher = {Springer},
	organization = {Springer},
	chapter = {25},
	abstract = {According to the now widely accepted {\textquotedblleft}onion-model{\textquotedblright} of the organization of open source software development, an open source project typically relies on a core of developers that is assisted by a larger periphery of users. But what does the role of the periphery consist of? Raymond{\textquoteright}s Linus{\textquoteright}s Law which states that {\textquotedblleft}given enough eyeballs all bugs are shallow{\textquotedblright} suggests at least one important function: the detection of defects. Yet, what are the ways through which core and periphery interact with each other? With the help of text-mining methods, we study the treatment of bugs that affected the Firefox Internet browser as reflected in the discussions and actions recorded in Mozilla{\textquoteright}s issue tracking system Bugzilla. We find various patterns in the modes of interactions between core and peripheral members of the community. For instance, core members seem to engage more frequently with the periphery when the latter proposes a solution (a patch). This leads us to conclude that Alan Cox{\textquoteright}s dictum {\textquotedblleft}show me the code{\textquotedblright}, perhaps even more than Linus{\textquoteright}s law, seems to be the dominant rule that governs the development of software like Firefox.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_25},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Peeling\%20the\%20Onion.pdf},
	author = {Masmoudi, H{\'e}la and den Besten, Matthijs and de Loupy, Claude and Jean-Michel Dalle}
}
@booklet {859,
	title = {Perceptions and Practices of Usability in the Free/Open Source Software (FOSS) Community},
	number = {CS-2009-26},
	year = {2009},
	publisher = {David R. Cheriton School of Computer Science, University of Waterloo},
	author = {Terry, M. and Kay, M. and Lafreniere, B.}
}
@conference {924,
	title = {A platform for software engineering research},
	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 = {31 - 40},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Research in the fields of software quality, maintainability and evolution requires the analysis of large quantities of data, which often originate from open source software projects. Collecting and preprocessing data, calculating metrics, and synthesizing composite results from a large corpus of project artifacts is a tedious and error prone task lacking direct scientific value. The Alitheia Core tool is an extensible platform for software quality analysis that is designed specifically to facilitate software engineering research on large and diverse data sources, by integrating data collection and preprocessing phases with an array of analysis services, and presenting the researcher with an easy to use extension mechanism. Alitheia Core aims to be the basis of an ecosystem of shared tools and research data that will enable researchers to focus on their research questions at hand, rather than spend time on re-implementing analysis tools. In this paper, we present the Alitheia Core platform in detail and demonstrate its usefulness in mining software repositories by guiding the reader through the steps required to execute a simple experiment.},
	keywords = {alitheia core},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069478},
	attachments = {https://flosshub.org/sites/flosshub.org/files/31gousios.pdf},
	author = {Gousios, Georgios and Diomidis Spinellis}
}
@conference {DBLP:conf/msr/BirdRBHGD09,
	title = {The promises and perils of mining git},
	booktitle = {Proceedings of the 6th International Working Conference on Mining Software Repositories, MSR 2009},
	year = {2009},
	pages = {1-10},
	abstract = {We are now witnessing the rapid growth of decentralized source code management (DSCM) systems, in which every developer has her own repository. DSCMs facilitate a style of collaboration in which work output can flow sideways (and privately) between collaborators, rather than always up and down (and publicly) via a central repository. Decentralization comes with both the promise of new data and the peril of its misinterpretation. We focus on git, a very popular DSCM used in high-profile projects. Decentralization, and other features of git, such as automatically recorded contributor attribution, lead to richer content histories, giving rise to new questions such as "How do contributions flow between developers to the official project repository?" However, there are pitfalls. Commits may be reordered, deleted, or edited as they move between repositories. The semantics of terms common to SCMs and DSCMs sometimes differ markedly, potentially creating confusion. For example, a commit is immediately visible to all developers in centralized SCMs, but not in DSCMs. Our goal is to help researchers interested in DSCMs avoid these and other perils when mining and analyzing git data.},
	keywords = {dscm, git, mining, scm, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1promisePeril.pdf},
	author = {Christian Bird and Peter C. Rigby and Earl T. Barr and David J. Hamilton and Daniel M. Germ{\'a}n and Premkumar T. Devanbu}
}
@conference {576,
	title = {Providing Commercial Open Source Software: Lessons Learned},
	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 = {70 - 82},
	publisher = {Springer},
	organization = {Springer},
	chapter = {8},
	abstract = {Even though companies like Sun, IBM, MySQL and others have released several commercial Open Source Software (OSS) products, little evidence exist of how to successfully launch such products and establish a living community around them. This paper presents a case study from a small software company succeeding at establishing a business model and a vivid community around their own OSS products. Based on this case study, the paper presents lessons learned which could help other OSS providers.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_8},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Providing\%20Commercial\%20Open\%20Source.pdf},
	author = {Hauge, {\O}yvind and Ziemer, Sven}
}
@conference {bird2009pat,
	title = {{Putting it All Together: Using Socio-Technical Networks to Predict Failures}},
	booktitle = {Proceedings of the 17th International Symposium on Software Reliability Engineering},
	year = {2009},
	note = {First, we build each type of network separately and use network analysis on both to gather metrics for use in a predictive model. Second, we build a socio-technical network which combines the nodes and edges from both the dependency network and the contribution network and use metrics gathered from this network in a predictive model.
We evaluate our approach by collecting data from Mi- crosoft Windows Vista and ECLIPSE development and using logistic regression analysis.},
	abstract = {Studies have shown that social factors in development organizations have a dramatic effect on software quality. Separately, program dependency information has also been used successfully to predict which software components are more fault prone. Interestingly, the influence of these two phenomena have only been studied separately. Intuition and practical experience suggests, however, that task assignment (i.e. who worked on which components and how much) and dependency structure (which components have dependencies on others) together interact to influence the quality of the resulting software. We study the influence of combined socio-technical software networks on the fault-proneness of individual software components within a system. The network properties of a software component in this combined network are able to predict if an entity is failure prone with greater accuracy than prior methods which use dependency or contribution information in isolation. We evaluate our approach in different settings by using it on Windows Vista and across six releases of the Eclipse development environment including using models built from one release to predict failure prone components in the next release. We compare this to previous work. In every case, our method performs as well or better and is able to more accurately identify those software components that have more post-release failures, with precision and recall rates as high as 85\%.},
	keywords = {eclipse, microsoft, social network, vista, windows},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2009pat.pdf},
	author = {Christian Bird and Nachiappan Nagappan and Devanbu, Premkumar and Gall, Harald and Brendan Murphy}
}
@article {Capiluppi200989,
	title = {Quality Factors and Coding Standards - a Comparison Between Open Source Forges},
	journal = {Electronic Notes in Theoretical Computer Science},
	volume = {233},
	year = {2009},
	note = {Proceedings of the International Workshop on Software Quality and Maintainability (SQM 2008)},
	pages = {89 - 103},
	abstract = {Enforcing adherence to standards in software development in order to produce high quality software artefacts has long been recognised as best practice in traditional software engineering. In a distributed heterogeneous development environment such those found within the Open Source paradigm, coding standards are informally shared and adhered to by communities of loosely coupled developers. Following these standards could potentially lead to higher quality software. This paper reports on the empirical analysis of two major forges where OSS projects are hosted. The first one, the KDE forge, provides a set of guidelines and coding standards in the form of a coding style that developers may conform to when producing the code source artefacts. The second studied forge, SourceForge, imposes no formal coding standards on developers. A sample of projects from these two forges has been analysed to detect whether the SourceForge sample, where no coding standards are reinforced, has a lower quality than the sample from KDE. Results from this analysis form a complex picture; visually, all the selected metrics show a clear divide between the two forges, but from the statistical standpoint, clear distinctions cannot be drawn amongst these quality related measures in the two forge samples.},
	keywords = {artefacts, artifacts, coding standards, coding style, complexity, forge, forges, kde, metrics, quality, source code, sourceforge},
	issn = {1571-0661},
	doi = {DOI: 10.1016/j.entcs.2009.02.063},
	url = {http://www.sciencedirect.com/science/article/B75H1-4VXDKRV-7/2/abcc2be2c4c3998e4bc9b53473ca2d81},
	author = {Capiluppi, Andrea and Boldyreff, Cornelia and Karl Beecher and Paul J. Adams}
}
@conference {586,
	title = {Quality of Open Source Software: The QualiPSo Trustworthiness Model},
	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 = {199 - 212},
	publisher = {Springer},
	organization = {Springer},
	chapter = {18},
	abstract = {Trustworthiness is one of the main issues upon which the decision whether to adopt an Open-Source Software (OSS) product is based. The work described here is part of an activity that has the goals of 1) defining an adequate notion of trustworthiness of software products and artifacts and 2) identifying a number of factors that influence it. Specifically, this paper reports about the identification of the {\textquotedblleft}dimensions{\textquotedblright} of trustworthiness, i.e., of the high-level qualities that software products and artefacts have to posses in order to be considered trustworthy. These dimensions are described by means of a conceptual model of trustworthiness, which comprises the representation of the factors that affect the user{\textquoteright}s perception of trustworthiness, as well as the objective characteristics of the products that contribute to {\textquotedblleft}build{\textquotedblright} trustworthi-ness. The aforementioned model is equipped with a measurement plan that de-scribes, at the operational level, how to perform the evaluation of the trustwor-thiness of OSS products. The proposed model provides the basis to build quantitative models of the trustworthiness of OSS products and artifacts that are able to explain the relationships between the (objectively observable) characteristics of OSS products and the level of trustworthiness perceived by the users of such products.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Quality\%20of\%20Open\%20Source\%20Software.pdf},
	author = {del Bianco, Vieri and Lavazza, Luigi and Morasca, Sandro and Taibi, Davide}
}
@conference {1811,
	title = {The QualOSS open source assessment model measuring the performance of open source communities},
	booktitle = {2009 3rd International Symposium on Empirical Software Engineering and Measurement (ESEM)2009 3rd International Symposium on Empirical Software Engineering and Measurement},
	year = {2009},
	pages = {498 - 501},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Lake Buena Vista, FL, USA},
	abstract = {Open Source Software (OSS) has an increasing importance for the software industry. Similar to traditional (closed) software acquisition, OSS acquisition requires an assessment of whether its quality is sufficient for the intended purpose, and whether the chances of being maintained and supported in the future, as well as of keeping certain quality standards over time, are sufficiently high. In this paper, we present an approach toward a comprehensive measurement framework for OSS projects, developed in the EU project QualOSS. This approach takes into account product quality as well as process maturity and sustainability of the underlying OSS community.
},
	isbn = {978-1-4244-4842-5},
	doi = {10.1109/ESEM.2009.5314237},
	author = {Soto, Martin and Ciolkowski, Marcus}
}
@conference {592,
	title = {Reassessing Brooks{\textquoteright} Law for the Free Software Community},
	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 = {274 - 283},
	publisher = {Springer},
	organization = {Springer},
	chapter = {24},
	abstract = {Proponents of Free Software have argued that some of the most established software engineering principles do not fully apply when considered in an open, distributed approach. Among these principles, {\textquotedblleft}Brooks{\textquoteright} Law{\textquotedblright} has been questioned in the Free Software context: large teams of developers, contrary to the law, will not need an increasingly growing number of communication channels. As advocates claim, this is due to the internal haracteristics of the Free Software process: the high modularity of the code helps developers to work on comparted sections, without the need to coordinate with all other contriutors.
This paper examines Brooks{\textquoteright} Law in a Free Software context, and it studies the interaction of contributors to a large Free Software project, KDE. The network of interactions is analyzed and a summary term, the {\textquotedblleft}compaction{\textquotedblright}, is dynamically evaluated to test how the coordination mechanism evolves over time in the project. This paper argues that the claim of advocates holds true, but with limitations: in the KDE project, the few initial developers needed a significant amount of communication. The growth of KDE brought the need to break the number of overall communication channels to a significant extent. Finally, an established amount of 300 developers currently needs the same amount of communication as when the developers were only 10. We interpret this result by arguing that Brooks{\textquoteright} Law holds true among the core developers of any large Free Software project.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_24},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Reassessing\%20Brook\%27s\%20Law.pdf},
	author = {Capiluppi, Andrea and Adams, Paul}
}
@conference {607,
	title = {Release Mismanagement in Open Source},
	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 = {365 - 365},
	publisher = {Springer},
	organization = {Springer},
	chapter = {39},
	abstract = {To a user, unreleased software is nonexistent software, even in open source projects which make the source code readily accessible. Every project requires regular software releases to encourage adoption and attract developers. Different projects approach the task of releasing software in variousways [2], and many experience breakdowns in their release process at some point during their evolution [3]. This poster presents examples of these instances, and how projects are learning from and improving upon them.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_39},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Release\%20Mismanagement.pdf},
	author = {Wright, Hyrum and Perry, Dewayne}
}
@conference {583,
	title = {Reporting Empirical Research in Open Source Software: The State of Practice},
	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 = {156 - 169},
	publisher = {Springer},
	organization = {Springer},
	chapter = {15},
	abstract = {Background: The number of reported empirical studies of Open Source Software (OSS) has continuously been increasing. However, there has been no effort to systematically review the state of the practice of reporting empirical studies of OSS with respect to the recommended standards of performing and reporting empirical studies in software engineering. It is important to understand, how to report empirical studies of OSS in order to make them useful for practitioners and researchers.
Research aim: The aim of our research is to gain insights in the state of the practice of reporting empirical studies of OSS in order to identify the gaps to be filled for improving the quality of evidence being provided for OSS.
Method: To that end, we decided to systematically review the empirical studies of OSS. A total of 63 papers reporting empirical studies were selected from the four editions of the Proceedings of the International Conference on Open Source Systems. The data were extracted and synthesised from the selected papers for analysis.
Results and conclusions: We have found that the quality of the reported OSS-related empirical studies needs to be significantly improved. Based on the results of our systematic review and general principles of reporting good empirical research, we present a set of guidelines for reporting OSS-related empirical studies. The suggested guidelines are expected to help the research community to improve the quality of reported studies.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_15},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Reporting\%20Empirical\%20Research.pdf},
	author = {Stol, Klaas-Jan and Ali Babar, Muhammad}
}
@conference {herraiz2009research,
	title = {Research friendly software repositories},
	booktitle = {Proceedings of the joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops},
	year = {2009},
	note = {"In spite of these rich availability of software repositories,
the heterogeneity of the data makes it difficult to apply studies
at a large scale, although some research projects, like
FLOSSMole [10] or FLOSSMetrics [8] are addressing these
issues and aim to provide datasets about thousands of libre
software projects for research purposes."

(more)},
	pages = {19{\textendash}24},
	publisher = {ACM},
	organization = {ACM},
	abstract = {What is the future of software evolution? In 1974, Meir M. Lehman had a vision of software evolution being driven by empirical studies of software repositories, and of a theory based on those empirical results. However, that scenario is yet to come. Software evolution studies are often based on a few cases, because the needed information is scarce, dispersed and incomplete. Their conclusions are not generalizable, slowing down the progress of this research discipline. Libre (free / open source) software supposes an opportunity to alleviate this situation. In this paper we describe the existing approaches to provide research datasets that are mining libre software repositories, and propose an agenda based on the concept of research friendly software repositories, which provides finer granularity and integrated data.},
	keywords = {flossmetrics, flossmole cited},
	attachments = {https://flosshub.org/sites/flosshub.org/files/herraiz-Research-Friendly-sw-repos.pdf},
	author = {Herraiz, I. and Robles, G. and Gonzalez-Barahona, J.M.}
}
@article {1082,
	title = {Returns from social capital in open source software networks},
	journal = {Journal of Evolutionary Economics},
	volume = {19},
	year = {2009},
	note = {"The data we use in this analysis come from the SourceForge.net Research Data (Department of Computer Science and Engineering, University of Notre Dame)." "Particularly, our dataset is a sub-sample of 2,962 valid observations over twelve months of projects aimed at developing games{\textquoteright} software. To get this sample, we look at the monthly dumps of data and select all projects that belong to the category of GNU Public License (GPL) [6]. "
dependent variable: performance (number of downloads); independent variable: social network ("Here we measure ties among projects through the individuals{\textquoteright} member and contributor roles at projects on the network over time.)},
	month = {4/2009},
	pages = {277 - 295},
	abstract = {Open Source Software projects base their operation on a collaborative structure for knowledge exchange in the form of provision or reception of information, expertise, and feedback on the creation of source code. Here, we address the direction of these knowledge flows among projects throughout social networks and their impact on project success. We identify the roles of membership or contribution that individuals play within projects. We found that connections through contributors who bring their knowledge to the project, improve project success, and that connection through members, who transfer their knowledge towards other projects, enhance project success. Finally, we found that ties through shared membership and contributions hamper project success. The analysis of knowledge flows and their impact on project success imply a translation of returns from investment in social capital, where investment takes the shape of knowledge flows and the returns mean the projects{\textquoteright} diffusion over the network.},
	keywords = {contributors, developers, games, gpl, project success, roles, social capital, social network analysis, social networks, sourceforge, srda, teams},
	issn = {1432-1386},
	doi = {10.1007/s00191-008-0125-5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Mendez-DuronGarcia.pdf},
	author = {M{\'e}ndez-Dur{\'o}n, Rebeca and Garc{\'\i}a, Clara E.}
}
@conference {H{\"a}rtig09roitzsch:the,
	title = {Roitzsch: The Mathematics of Obscurity: On the Trustworthiness of Open Source},
	booktitle = {9th Workshop on the Economics of Information Security (WEIS)},
	year = {2009},
	pages = {2016{\textendash}2023},
	publisher = {ACM},
	organization = {ACM},
	abstract = {It is more difficult to find errors when source code is secret.
More people search for errors when source code is
public. These counteracting effects are pivotal to the question
whether openness fosters security. Errors in software
are found by people with either constructive contribution or
exploitation in mind. Focusing exclusively on this discovery
aspect, we present a probabilistic model, which allows us to
compare the open source and closed source situations.
We start out with our assumptions explained using a simple
introductory model. We then extend this to what we
believe to be an adequate model of a bug-hunting process
conducted by multiple competing parties. The model employs
an asymmetric race paradigm. One of the surprising
results is that even an arbitrarily large group with good intentions
cannot safely dominate the evil attackers. Instead,
they are limited by a significant upper bound in their winning
chances.},
	url = {http://www.econinfosec.org/archive/weis2010/papers/session6/weis2010_haertig.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/weis2010_haertig.pdf},
	author = {Hermann H{\"a}rtig and Claude-joachim Hamann and Michael Roitzsch and Technische Universit{\"a}t Dresden}
}
@conference {765,
	title = {The role of patch review in software evolution: an analysis of the mozilla firefox},
	booktitle = {The joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops},
	year = {2009},
	month = {08/2009},
	pages = {9-18},
	publisher = {ACM},
	organization = {ACM},
	type = {Paper in Conference Proceedings},
	address = {Amsterdam, The Netherlands},
	abstract = {Patch review is the basic mechanism for validating the design and implementation of patches and maintaining consistency in some commercial and Free/Libre/Open Source Software (FLOSS) projects. We examine the inner-workings of the development process of the successful and mature Mozilla foundation and highlight how different parties involved affect and steer the process. Although reviewers are the primary actors in the patch review process, success in the process can only be achieved if the community supports reviewers adequately. Peer developers play the supporting role by offering insight and ideas that help create more quality patches. Moreover, they reduce the huge patch backlog reviewers have to clear by identifying and eliminating immature patches.},
	keywords = {inspection, open source development},
	isbn = {978-1-60558-678-6},
	doi = {http://doi.acm.org/10.1145/1595808.1595813},
	url = {http://ase.cpsc.ucalgary.ca/ase/uploads/Publications/iwpse31-nurolahzade.pdf},
	author = {Mehrdad Nurolahzade},
	editor = {Seyed Mehdi Nasehi and Shahedul Huq Khandkar and Shreya Rawal}
}
@proceedings {846,
	title = {The Role of Software Licenses in Open Architecture Ecosystems},
	year = {2009},
	month = {09/2009},
	address = {Falls Church, VA},
	author = {Alspaugh, Thomas and Hazeline U. Asuncion and Walt Scacchi}
}
@conference {843,
	title = {rv you{\textquoteright}re dumb: Identifying Discarded Work in Wiki Article History},
	booktitle = {The Fifth International Symposium on Wiki{\textquoteright}s and Open Collaboration},
	year = {2009},
	month = {10/25/2009},
	address = {Orlando, FL},
	author = {Ekstrand, M.D. and Riedl, J.T.}
}
@article {schryen2009security,
	title = {Security of Open Source and Closed Source Software: An Empirical Comparison of Published Vulnerabilities},
	journal = {AMCIS 2009 Proceedings},
	year = {2009},
	pages = {387},
	abstract = {Reviewing literature on open source and closed source security reveals that the discussion is often determined by biased attitudes toward one of these development styles. The discussion specifically lacks appropriate metrics, methodology and hard data. This paper contributes to solving this problem by analyzing and comparing published vulnerabilities of eight open source software and nine closed source software packages, all of which are widely deployed. Thereby, it provides an extensive empirical analysis of vulnerabilities in terms of mean time between vulnerability disclosures, the development of disclosure over time, and the severity of vulnerabilities, and allows for validating models provided in the literature. The investigation reveals that (a) the mean time between vulnerability disclosures was lower for open source software in half of the cases, while the other cases show no differences, (b) in contrast to literature assumption, 14 out of 17 software packages showed a significant linear or piecewise linear correlation between time and the number of published vulnerabilities, and (c) regarding the severity of vulnerabilities, no significant differences were found between open source and closed source.},
	keywords = {closed source software, empirical comparison, open source software, security, Vulnerabilities},
	url = {http://epub.uni-regensburg.de/21296/1/Schryen_-_AMCIS_09_-_Security_of_open_source_and_closed_source_software_-_Web_version.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Schryen_-_AMCIS_09_-_Security_of_open_source_and_closed_source_software_-_Web_version.pdf},
	author = {Schryen, Guido}
}
@conference {852,
	title = {Short and Tweet: Experiments on Recommending Content from Information},
	booktitle = {Proceedings of the 28th annual conference on Human Factors in Computing Systems},
	year = {2009},
	month = {04/10/10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Atlanta, GA},
	author = {Chen, J and Nairn, R. and Nelson, L. and Bernstein, M. and Chi, E.}
}
@conference {573,
	title = {Software Engineering in Practice: Design and Architectures of FLOSS Systems},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {34 - 46},
	publisher = {Springer},
	organization = {Springer},
	chapter = {5},
	abstract = {Free/Libre/Open Source Software (FLOSS) practitioners and developers are typically also users of their own systems: as a result, traditional software engineering (SE) processes (e.g., the requirements and design phases), take less time to articulate and negotiate among FLOSS developers. Design and requirements are kept more as informal knowledge, rather than formally described and assessed. This paper attempts to recover the SE concepts of software design and architectures from three FLOSS case studies, sharing the same application domain (i.e., Instant Messaging). Its first objective is to determine whether a common architecture emerges from the three systems, which can be used as shared knowledge for future applications. The second objective is to determine whether these architectures evolve or decay during the evolution of these systems. The results of this study are encouraging: albeit no explicit effort was done by FLOSS developers to define a high-level view of the architecture, a common shared architecture could be distilled for the Instant Messaging application domain. It was also found that, for two of the three systems, the architecture becomes better organised, and the components better specified, as long as the system evolves in time.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Software\%20Engineering\%20in\%20Practice.pdf},
	author = {Capiluppi, Andrea and Knowles, Thomas}
}
@proceedings {811,
	title = {Software Informatics?},
	year = {2009},
	abstract = {The paper proposes the term {\textquoteright}software informatics{\textquoteright} to describe research on the individual, collaborative, and social aspects of software production and use, spanning multiple representations of software from design, to source code, to application. It does this with a particular focus on information processes around software development. As more applications are web-based or available online for download and increasing amounts of source code is also available online, the information processes surrounding software are changing the way that software is created, appropriated and redesigned. Traditional distinctions between software developer and end-user are blurring, with software development processes occurring along a continuum of the proportion of original code written to develop the application, from build from scratch, through library and API calls, copy-paste programming, web mashup development, end-user programming, to creative design through the selection and combination of existing applications. All these design activities have much in common and can benefit from being studied as a whole.},
	url = {http://hdl.handle.net/2142/9600},
	author = {Jones, M. Cameron and Michael B Twidale}
}
@proceedings {848,
	title = {Software Licenses, Open Source Components, and Open Architectures},
	year = {2009},
	month = {05/2009},
	address = {Monterey, CA},
	author = {Alspaugh, Thomas and Hazeline U. Asuncion and Walt Scacchi}
}
@conference {945,
	title = {SourcererDB: An aggregated repository of statically analyzed and cross-linked open source Java 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 = {183 - 186},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {The open source movement has made vast quantities of source code available online for free, providing an extremely large dataset for empirical study and potential resuse. A major difficulty in exploiting this potential fully is that the data are currently scattered between competing source code repositories, none of which are structured for empirical analysis and cross-project comparison. As a result, software researchers and developers are left to compile their own datasets, resulting in duplicated effort and limited results. To address this challenge, we built SourcererDB, an aggregated repository of statically analyzed and cross-linked open source Java projects. SourcererDB contains local snapshots of 2,852 Java projects taken from Sourceforge, Apache and Java.net. These projects are statically analyzed to extract rich structural information, which is then stored in a relational database. References to entities in the 16,058 external jars are resolved and grouped, allowing for cross-project usage information to be accessed easily. This paper describes: (a) the mechanism for resolving and grouping these cross-project references, (b) the structure of and the metamodel for the SourcererDB repository, and (d) end-user dataset access mechanisms. Our goal in building SourcererDB is to provide a rich dataset of source code to facilitate the sharing of extracted data and to encourage reuse and repeatability of experiments.},
	keywords = {apache, integration, java, java.net, project, repository, sourceforge, SourcererDB},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069501},
	author = {Ossher, Joel and Bajracharya, Sushil and Linstead, Erik and Baldi, Pierre and Lopes, Cristina}
}
@conference {1066,
	title = {SourcererDB: An aggregated repository of statically analyzed and cross-linked open source Java projects},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)},
	year = {2009},
	pages = {183 - 186},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {The open source movement has made vast quantities of source code available online for free, providing an extremely large dataset for empirical study and potential re-use. A major difficulty in exploiting this potential fully is that the data are currently scattered between competing source code repositories, none of which are structured for empirical analysis and cross-project comparison. As a result, software researchers and developers are left to compile their own datasets, resulting in duplicated effort and limited results. To address this challenge, we built SourcererDB, an aggregated repository of statically analyzed and cross-linked open source Java projects. SourcererDB contains local snapshots of 2,852 Java projects taken from Sourceforge, Apache and Java.net. These projects are statically analyzed to extract rich structural information, which is then stored in a relational database. References to entities in the 16,058 external jars are resolved and grouped, allowing for cross-project usage information to be accessed easily. This paper describes: (a) the mechanism for resolving and grouping these cross-project references, (b) the structure of and the metamodel for the SourcererDB repository, and (d) end-user dataset access mechanisms. Our goal in building SourcererDB is to provide a rich dataset of source code to facilitate the sharing of extracted data and to encourage reuse and repeatability of experiments.},
	keywords = {apache, java, java.net, source code, sourceforge, sourcerer},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069501},
	author = {Ossher, Joel and Bajracharya, Sushil and Linstead, Erik and Baldi, Pierre and Lopes, Cristina}
}
@article {1350,
	title = {Strategies for Improving Open Source Software Usability},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {49 - 64},
	abstract = {The Open Source Software (OSS) movement has had enormous impact on how software is created and continues to attract interest from researchers, software developers and users. A factor that may be inhibiting OSS from achieving greater success is usability, a fundamental characteristic to user acceptance of software. Motivated by the uniquely user-driven nature of the open source model and the extensive user base that participates in OSS projects, the authors propose an exploratory learning method and an associated web-based inspection environment that enables non-experts to contribute to open source usability inspection. This tool uses patternbased usability guidelines to help identify usability knowledge during inspection. The method emphasizes outlining and exploration features which the authors have formally evaluated and the results of which are described. Data collected from a qualitative study indicates positive impact of the proposed method in helping end-users inspect software and achieve better results in discovering usability problems.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009100103},
	author = {Zhao, Luyin and Deek, Fadi P. and McHugh, James A.}
}
@conference {1518,
	title = {Studying the use of developer IRC meetings in open source projects},
	booktitle = {2009 IEEE International Conference on Software Maintenance (ICSM)},
	year = {2009},
	pages = {147 - 156},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Edmonton, AB, Canada},
	abstract = {Open source developers communicate with each other via various online outlets. Thus far, mailing lists have been the main coordination mechanism. However, our previous study shows that the use of developer IRC meetings is increasing in recent years. In this paper, we perform a study on the IRC meetings of two large open source projects: the GTK+ and Evolution projects. We explore three dimensions: who participates in the meetings, what do they discuss and how do they run the meetings. We find (1) that a small and stable number of the participants contribute the majority of messages in meetings, (2) that there are commonly discussed topics as well as project specific topics (3) that meeting styles vary across different projects.},
	keywords = {evolution, gtk, irc},
	isbn = {978-1-4244-4897-5},
	doi = {10.1109/ICSM.2009.5306333},
	url = {http://sail.cs.queensu.ca/publications/pubs/icsm2009_shihab.pdf},
	author = {Shihab, Emad and Zhen Ming Jiang and Hassan, Ahmed E.}
}
@conference {840,
	title = {Succession: Measuring Transfer of Code and Developer Productivity},
	booktitle = {2009 International Conference on Software Engineering},
	year = {2009},
	month = {May 12{\textendash}22},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Vancouver, CA},
	author = {Audris Mockus}
}
@conference {1807,
	title = {Supporting Situation Awareness in FLOSS Projects by Semantical Aggregation of Tools Feeds},
	booktitle = {Internet-Based Systems (SITIS 2009)2009 Fifth International Conference on Signal Image Technology and Internet Based Systems},
	year = {2009},
	note = {"The FLOSSmole  project provides public data about FLOSSdevelopment for academic research. It includes data and analysisfrom SourceForge, Freshmeat, RubyForge, ObjectWeb"},
	pages = {423 - 429},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Marakesh, Morocco},
	abstract = {It is rather difficult to monitor or visualize what can be the contribution of a member in a collaboration project, especially when the project uses multiple tools to produce its results. This is the case for collaborative development of FLOSS software, that uses Wiki, bug tracker, mailing lists and source code management tools. This paper presents an approach to data collection by using aggregation of feeds published by the different tools of a software forge. To allow this aggregation, collected data is semantically reformatted into Semantic Web standards: RDF, DC, DOAP, FOAF and EvoOnt. Resulting data can then be processed, re-published or displayed to project members. This approach was used to implement a supervision module that is integrated into the PicoForge platform. This module is able to draw a live graph of the social community out of the different sources of data, and in turn exports semantic feeds for other uses.},
	isbn = {978-1-4244-5740-3},
	doi = {10.1109/SITIS.2009.72},
	author = {Quang Vu Dang and Christian Bac and Olivier Berger and Valentin Vlasceanu}
}
@mastersthesis {1243,
	title = {Supporting the user experience in free/libre/open source software development},
	year = {2009},
	abstract = {With the increasing number and awareness of free/libre/open source software (FLOSS) projects, Internet users can download a FLOSS tool that meets just about any need. The user experience of projects, however, varies greatly and identifying FLOSS projects that offer a positive user experience (UX) is challenging. FLOSS projects center on software developer activities with little attention to user-centered design activities that could increase the user experience on the project. The purpose of this dissertation is to understand open source software ecology in order to bring support for user experience design activities on FLOSS projects. CodePlex, an open source project hosting website, serves as the open source software ecology.

The research consists of two phases, a descriptive science phase and a design science phase. In the descriptive phase fieldwork in the form of ethnomethodologically informed ethnography describes the everyday activities of three groups: the team that produces CodePlex, the participants who use CodePlex to produce open source projects, and user experience practitioners who bring their expertise to design software with a positive user experience. The descriptive phase also includes an analysis of activity awareness of the three groups. The design science phase consists of a claims analysis that provides design rationale for a design that proposes to support UX activities on CodePlex. The results show that activity awareness contributes to the socio-technical solution where UX activities can be supported as a new community of practice, with features that support building social capital. The UX support features include a UX workspace where UX contributors recognize their value and other features that support the presence of UX throughout the project site and the CodePlex community.

This dissertation contributes empirical materials from the descriptions of everyday activities of the three groups and analytic materials generated from the activity awareness and claims analyses that are translated into design representations. Specifically the contributions include (1) mechanisms of articulation work of the three groups and how the mechanisms contribute to the design representation; (2) the demonstration of a translation science in computersupported cooperative work (CSCW) and human-computer interaction (HCI); and (3) an understanding of how UX activities and software engineering activities integrate.},
	keywords = {codeplex},
	author = {Bach, Paula}
}
@conference {591,
	title = {A Survey of Usability Practices in Free/Libre/Open Source Software},
	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 = {264 - 273},
	publisher = {Springer},
	organization = {Springer},
	chapter = {23},
	abstract = {A review of case studies about usability in eight Free/Libre/Open Source Software (FLOSS) projects showed that an important issue regarding a usability initiative in the project was the lack of user research. User research is a key component in the user-centered design (UCD) process and a necessary step for creating usable products. Reasons why FLOSS projects suffered from a lack of user research included poor or unclear project leadership, cultural differences between developer and designers, and a lack of usability engineers. By identifying these critical issues, the FLOSS usability community can begin addressing problems in the efficacy of usability activities and work towards creating more usable FLOSS products.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Survey\%20of\%20Usability\%20Practices.pdf},
	author = {Paul, Celeste}
}
@conference {588,
	title = {A Survey on Firms{\textquoteright} Participation in Open Source Community Projects},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	year = {2009},
	month = {2009///},
	pages = {225 - 236},
	publisher = {Springer},
	organization = {Springer},
	chapter = {20},
	abstract = {The role of firms in commercial Open Source projects (e.g., former MySQL, EnterpriseDB, SugarCRM) is a consolidated and generally accepted fact. On other hand, community Open Source projects, which are built upon communities and not directly associated with firms, are commonly perceived to be based mainly on the work of volunteers. Up to now, firms{\textquoteright} role in these projects has been poorly investigated. We conducted a survey on 1,302 SourceForge.net projects to inquire about the level and the typology of involvement of firms. We propose three different models for firm participation and provide empirical evidence on their diffusion in SourceForge.net.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Survey\%20on\%20Firns\%27\%20Participation.pdf},
	author = {Capra, Eugenio and Francalanci, Chiara and Merlo, Francesco and Rossi Lamastra, Cristina}
}
@article {1345,
	title = {The System for Population Kinetics},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {29 - 43},
	abstract = {This chapter describes the System for Population Kinetics (SPK), a novel Web service for performing population kinetic analysis. Population kinetic analysis is a widely-used tool for extracting information about the probability distributions of unknown parameters in kinetic models. The statistical population model is usually hierarchical, with a nested structure encompassing both variation between subjects and residual unexplained variation associated with the model predictions. The complexity of the analysis is largely driven by the nonlinearity of the models employed. Here, we provide a concise introduction to the topic and a historical perspective for the benefit of the reader who is new to these concepts. Next, we briefly describe the SPK open source system and its multi-tiered architecture, indicating the user goals it set to achieve and elucidating its practical usage with examples.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009070103},
	author = {Vicini, Paolo}
}
@conference {841,
	title = {Tagommenders: Connecting Users to Items through Tags},
	booktitle = {International World Wide Web Conference},
	year = {2009},
	month = {4/20/2009},
	publisher = {ACM},
	organization = {ACM},
	address = {Madrid, Spain},
	author = {Sen, S. and Vig, J. and Riedl, J.}
}
@conference {853,
	title = {Tagsplanations: Explaining Recommendations using Tags},
	booktitle = {International Conference on Intelligent User Interfaces},
	year = {2009},
	month = {02/08/2009},
	address = {Sanibel Island, FL},
	keywords = {recommender, SYSTEMS, tagging,},
	author = {Vig, J. and Sen, S. and Riedl, J.}
}
@article {1238,
	title = {Teaching Software Engineering with Free/Libre Open Source Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	month = {31/2009},
	pages = {72 - 90},
	abstract = {One of the major problems in software engineering education is the involvement of students in real world software projects. Industry projects are a solution, but in many cases they are hard to find and student participation can be problematic due to cultural, familiarization and other practical reasons. The abundance of Free / Libre Open Source Software (FLOSS) projects is a neat solution, offering multi-lingual, multicultural environments in virtually every application domain, at different levels of project size, maturity, organization etc. The paper analyzes how acquisition of practical experience on several basic and advanced software engineering topics can be achieved by working in a FLOSS project. The kind of skills that can be acquired are those requested by the Overview Report for Computing Curricula by ACM and topics examined are those of the Software Engineering Body of Knowledge, by IEEE. Also software engineering areas that require special care or that may not prove suitable for such treatment are identified. Various isolated teaching cases pertaining to this approach are presented and discussed.},
	keywords = {curriculum, education, teaching, undergraduate},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009010105},
	author = {Ioannis Stamelos}
}
@article {1236,
	title = {Tools for the Study of the Usual Data Sources found in Libre Software Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	month = {31/2009},
	pages = {24 - 45},
	abstract = {Due to the open nature of Free/Libre/Open Source software projects, researchers have gained access to a rich set of development-related information. Although this information is publicly available on the Internet, obtaining and analyzing it in a convenient way is not an easy task and many considerations have to be taken into account. In this paper we present the most important data sources that can be found in libre software projects and that are studied by the research community: source code, source code management systems, mailing lists and bug tracking systems. We will give advice for the problems that can be found when retrieving and preparing the data sources for a posterior analysis, as well as provide information about the tools that support these tasks.},
	keywords = {bug tracking systems, data sources, mailing lists, scm, tools},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009010102},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles.pdf},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Izquierdo-Cortazar, Daniel and Herraiz, Israel}
}
@conference {926,
	title = {Tracking concept drift of software projects using defect prediction quality},
	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 = {51 - 60},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Defect prediction is an important task in the mining of software repositories, but the quality of predictions varies strongly within and across software projects. In this paper we investigate the reasons why the prediction quality is so fluctuating due to the altering nature of the bug (or defect) fixing process. Therefore, we adopt the notion of a concept drift, which denotes that the defect prediction model has become unsuitable as set of influencing features has changed - usually due to a change in the underlying bug generation process (i.e., the concept). We explore four open source projects (Eclipse, OpenOffice, Netbeans and Mozilla) and construct file-level and project-level features for each of them from their respective CVS and Bugzilla repositories. We then use this data to build defect prediction models and visualize the prediction quality along the time axis. These visualizations allow us to identify concept drifts and - as a consequence - phases of stability and instability expressed in the level of defect prediction quality. Further, we identify those project features, which are influencing the defect prediction quality using both a tree induction-algorithm and a linear regression model. Our experiments uncover that software systems are subject to considerable concept drifts in their evolution history. Specifically, we observe that the change in number of authors editing a file and the number of defects fixed by them contribute to a project{\textquoteright}s concept drift and therefore influence the defect prediction quality. Our findings suggest that project managers using defect prediction models for decision making should be aware of the actual phase of stability or instability due to a potential concept drift.},
	keywords = {bugzilla, cvs, defect prediction, eclipse, mozilla, netbeans, openoffice},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069480},
	attachments = {https://flosshub.org/sites/flosshub.org/files/51MSR2009_0111_Ekanayake_Jayalath.pdf},
	author = {Ekanayake, Jayalath and Tappolet, Jonas and Gall, Harald C. and Bernstein, Abraham}
}
@conference {Orsila:2009:TIO:1527033.1527037,
	title = {Trust issues in open source software development},
	booktitle = {Proceedings of the Warm Up Workshop for ACM/IEEE ICSE 2010},
	series = {WUP {\textquoteright}09},
	year = {2009},
	note = {"We have selected two highly reusable libraries, zlib and FFmpeg. The software repository of the projects were downloaded, but mining the information is not an easy task and we considered various sources {\textemdash} such as bug reports, mailing lists, IRC conversations, and source code comments {\textemdash} in addition to the revision history. "},
	pages = {9{\textendash}12},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source software and the associated development model holds great promise, but the issue of trust is a major challenge. This applies to companies wishing to adopt the open source model but also within open source projects. We investigate this issue by data mining open source repositories to study two related phenomena: update propagation and distributed version control.},
	keywords = {ffmpeg, trust, version control, zlib},
	isbn = {978-1-60558-565-9},
	doi = {10.1145/1527033.1527037},
	url = {http://doi.acm.org/10.1145/1527033.1527037},
	author = {Orsila, Heikki and Geldenhuys, Jaco and Ruokonen, Anna and Hammouda, Imed}
}
@conference {850,
	title = {Two peers are better than one: aggregating peer reviews for computing assignments is surprisingly accurate},
	booktitle = {ACM 2009 International Conference on Supporting Group Work},
	year = {2009},
	month = {05/10/2009},
	pages = {115-124},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Sanibel Island, FL},
	isbn = {978-1-60558-500-0 },
	author = {Reily, K. and Finnerty, P.L. and Terveen, L.}
}
@conference {598,
	title = {Undergraduate Research Opportunities in OSS},
	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 = {340 - 350},
	publisher = {Springer},
	organization = {Springer},
	chapter = {30},
	abstract = {Using Open Source Software (OSS) in undergraduate teaching in universities is now commonplace. Students use OSS applications and systems in their courses on programming, operating systems, DBMS, web development to name but a few. Studying OSS projects from both a product and a process view also forms part of the software engineering curriculum at various universities. Many students have taken part in OSS projects as well as developers. At the University of Lincoln, under the Undergraduate Research Opportunities Scheme (UROS), undergraduate student researchers have the chance to work over the summer embedded within an existing research centre on a UROS project. Here two such projects within the Centre for Research in Open Source Software (CROSS) are described: Collaborative Development for the XO Laptop (CODEX) and Software Modularity in Open Source Software (SoMOSS). The CODEX project focused on creating resources to support students undertaking software application development for the XO laptop, and the SoMOSS project focused on architectural studies of OSS instant messaging software. Both projects achieved successful research outcomes; more importantly, both student researchers benefited directly from the encouragement and concrete assistance that they received through interaction with the wider OSS research community. Both projects are ongoing and present further research opportunities for students.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_30},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Undergraduate\%20Research\%20Opportunities.pdf},
	author = {Boldyreff, Cornelia and Capiluppi, Andrea and Knowles, Thomas and Munro, James}
}
@conference {Yatani:2009:UWO:1518701.1518853,
	title = {Understanding how and why open source contributors use diagrams in the development of Ubuntu},
	booktitle = {Proceedings of the 27th international conference on Human factors in computing systems},
	series = {CHI {\textquoteright}09},
	year = {2009},
	note = {"To examine how and why diagrams are used in any and all aspects of the software development process of an OSS project, we performed a series of semi-structured interviews with contributors to one particular effort{\textemdash}Ubuntu."
"Our study was divided into two phases. First, we asked participants to complete a questionnaire and provide us with information and materials for discussion. The questionnaire featured questions about participants{\textquoteright} OSS experience, project participation, their roles in each project, and basic demographics. We also asked participants to share diagrams they had created, modified or used as part of their work on Ubuntu. In the second phase of the study, we conducted semi-structured interviews with participants."},
	pages = {995{\textendash}1004},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Some of the most interesting differences between Open Source Software (OSS) development and commercial co-located software development lie in the communication and collaboration practices of these two groups of developers. One interesting practice is that of diagramming. Though well studied and important in many aspects of co-located software development (including communication and collaboration among developers), its role in OSS development has not been thoroughly studied. In this paper, we report our investigation on how and why Ubuntu contributors use diagrams in their work. Our study shows that diagrams are not actively used in many scenarios where they commonly would in co-located software development efforts. We describe differences in the use and practices of diagramming, their possible reasons, and present design considerations for potential systems aimed at better supporting diagram use in OSS development.},
	keywords = {developers, diagramming, interviews, open source software (oss), software development, Ubuntu, visual representation},
	isbn = {978-1-60558-246-7},
	doi = {http://doi.acm.org/10.1145/1518701.1518853},
	url = {http://doi.acm.org/10.1145/1518701.1518853},
	author = {Yatani, Koji and Chung, Eunyoung and Jensen, Carlos and Truong, Khai N.}
}
@inbook {855,
	title = {Understanding Requirements for Open Source Software},
	booktitle = {Design Requirements Engineering: A Ten-Year Perspective},
	series = {Lecture Notes in Business Information Processing},
	volume = {14},
	year = {2009},
	pages = {467-494},
	publisher = {Springer-Verlag},
	organization = {Springer-Verlag},
	author = {Walt Scacchi},
	editor = {Lyytinen, K. and Loucopoulos, P. and Mylopoulos, J. and Robinson, W.}
}
@article {Fang:2009:USP:1554441.1554443,
	title = {Understanding Sustained Participation in Open Source Software Projects},
	journal = {J. Manage. Inf. Syst.},
	volume = {25},
	year = {2009},
	month = {April},
	pages = {9{\textendash}50},
	publisher = {M. E. Sharpe, Inc.},
	address = {Armonk, NY, USA},
	abstract = {Prior research into open source software (OSS) developer participation has emphasized individuals{\textquoteright} motivations for joining these volunteer communities, but it has failed to explain why people stay or leave in the long run. Building upon Lave and Wenger{\textquoteright}s theory of legitimate peripheral participation (LPP), this paper offers a longitudinal investigation of one OSS community in which sustained participation is hypothesized to be associated with the coevolution of two major elements of LPP theory: "situated learning" (the process of acting knowledgeably and purposefully in the world) and "identity construction" (the process of being identified within the community). To test this hypothesis, data were collected from multiple sources, including online public project documents, electronic mail messages, tracker messages, and log files. Results from qualitative analyses revealed that initial conditions to participate did not effectively predict long-term participation, but that situated learning and identity construction behaviors were positively linked to sustained participation. Furthermore, this study reveals that sustained participants distinguished themselves by consistently engaging in situated learning that both made conceptual (advising others) and practical contributions (improving the code). Implications and future research are discussed.},
	keywords = {Communities Of Practice, Legitimate Peripheral Participation, Open Source Projects, Open Source Software Community, Qualitative Study},
	issn = {0742-1222},
	doi = {10.2753/MIS0742-1222250401},
	url = {http://portal.acm.org/citation.cfm?id=1554441.1554443},
	author = {Fang, Yulin and Neufeld, Derrick}
}
@article {10.1109/HICSS.2009.998,
	title = {Understanding the Nature and Production Model of Hybrid Free and Open Source Systems: The Case of Varnish},
	journal = {42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	pages = {1-11},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {This is a detailed interpretive case study analysis of an open source software project, called Varnish. The conceptual framework is based on the literature covering issues of commons based production models and the organization of open source projects. The comparative analysis reveals that Varnish is a hybrid project, encompassing the features of open source software while managed by a company as a proprietary project would. It is also hybrid in the sense that it employs a combination of hierarchical and commons based peer production model features. This mix of characters addresses a variety of problems related to each of the aforementioned categories.},
	keywords = {case study, organizational sponsorship, peer production, varnish},
	isbn = {978-0-7695-3450-3},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.998},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-02.pdf},
	author = {Zegaye Seifu Wubishet}
}
@conference {934,
	title = {On the use of Internet Relay Chat (IRC) meetings by developers of the GNOME GTK+ project},
	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 = {107 - 110},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Developers of open source projects are distributed across the world. They rely on email, mailing lists, instant messaging, IRC channels and more recently IRC meetings to communicate. Most of the studies thus far focus on the use of mailing lists by OSS developers, however, an increasing number of open source projects are using IRC meetings to hold developer meetings. In this paper, we mine the $\#$gtk-devel IRC meeting channel and study the usage of the IRC meetings held by the GNOME GTK+ core developers and maintainers. We look at three different dimensions: the discussion volume of the meetings, the number of participants attending the meetings and the activity of these participants. Our findings show that IRC meetings are gaining popularity among open source developers and maintainers: the IRC meeting discussions are increasing in volume, have increasing attendance levels, and the participants actively contribute to the meetings. To the best of our knowledge, this is the first study on the use of developer IRC meetings by OSS developers.},
	keywords = {gnome, gtk, irc, msr challenge},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069488},
	attachments = {https://flosshub.org/sites/flosshub.org/files/107MSR2009-MSR-0130-Shihab-Emad.pdf},
	author = {Shihab, Emad and Zhen Ming Jiang and Hassan, Ahmed E.}
}
@conference {804,
	title = {Users of Open Source Software - How do they get help?},
	booktitle = {HICSS 2009},
	year = {2009},
	abstract = {A study was conducted across multiple open source software online technical help communities. This paper presents the types of discussions that occur, the types of questions asked and the type of responses that are given. The implications for socio-technical design are considered, exploring how help requests and discussions can be used to improve future help-giving, documentation and interface and functionality redesign.},
	keywords = {technical help},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.489},
	author = {Singh, V and Twidale, M.B and Nichols, D.M}
}
@article {10.1109/HICSS.2009.1005,
	title = {Users of Open Source Software - How Do They Get Help?},
	journal = {42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	note = {"we collected twenty threads each from eight different websites making a total of 160 threads"},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {A study was conducted across multiple open source software online technical help communities. This paper presents the types of discussions that occur, the types of questions asked and the type of responses that are given. The implications for socio-technical design are considered, exploring how help requests and discussions can be used to improve future help-giving, documentation and interface and functionality redesign.},
	keywords = {technical help},
	isbn = {978-0-7695-3450-3},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.1005},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-04.pdf},
	author = {Singh, Vandana and Michael B Twidale and David M Nichols}
}
@conference {938,
	title = {Using association rules to study the co-evolution of production \& test code},
	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 = {151 - 154},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Unit tests are generally acknowledged as an important aid to produce high quality code, as they provide quick feedback to developers on the correctness of their code. In order to achieve high quality, well-maintained tests are needed. Ideally, tests co-evolve with the production code to test changes as soon as possible. In this paper, we explore an approach based on association rule mining to determine whether production and test code co-evolve synchronously. Through two case studies, one with an open source and another one with an industrial software system, we show that our association rule mining approach allows one to assess the co-evolution of product and test code in a software project and, moreover, to uncover the distribution of programmer effort over pure coding, pure testing, or a more test-driven-like practice.},
	keywords = {association rules, checkstyle, source code, unit test},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069493},
	attachments = {https://flosshub.org/sites/flosshub.org/files/151UsingAssociation.pdf},
	author = {Lubsen, Zeeger and Zaidman, Andy and Pinzger, Martin}
}
@conference {597,
	title = {Using FLOSS Project Metadata in the Undergraduate Classroom},
	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 = {330 - 339},
	publisher = {Springer},
	organization = {Springer},
	chapter = {29},
	abstract = {This paper describes our efforts to use the large amounts of data available from public repositories of free, libre, and open source software (FLOSS) in our undergraduate classrooms to teach concepts that would have previously been taught using other types of data from other sources.
},
	keywords = {artificial intelligence, database, education, teaching, undergraduate, undergraduate research},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Using\%20FLOSS\%20Project\%20Metadata.pdf},
	author = {Squire, Megan and Duvall, Shannon}
}
@conference {940,
	title = {Using Latent Dirichlet Allocation for automatic categorization of software},
	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 = {163 - 166},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {In this paper, we propose a technique called LACT for automatically categorizing software systems in open-source repositories. LACT is based on latent Dirichlet Allocation, an information retrieval method which is used to index and analyze source code documents as mixtures of probabilistic topics. For an initial evaluation, we performed two studies. In the first study, LACT was compared against an existing tool, MUDABlue, for classifying 41 software systems written in C into problem domain categories. The results indicate that LACT can automatically produce meaningful category names and yield classification results comparable to MUDABlue. In the second study, we applied LACT to 43 software systems written in different programming languages such as C/C++, Java, C$\#$, PHP, and Perl. The results indicate that LACT can be used effectively for the automatic categorization of software systems regardless of the underlying programming language or paradigm. Moreover, both studies indicate that LACT can identify several new categories that are based on libraries, architectures, or programming languages, which is a promising improvement as compared to manual categorization and existing techniques.},
	keywords = {categorization, category mining, lact, mudablue, multiple languages, repository},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069496},
	attachments = {https://flosshub.org/sites/flosshub.org/files/163MSR2009_TianPos.pdf},
	author = {Tian, Kai and Revelle, Meghan and Poshyvanyk, Denys}
}
@article {10.1109/HICSS.2009.1014,
	title = {Using Software Archaeology to Measure Knowledge Loss in Software Projects Due to Developer Turnover},
	journal = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {Developer turnover can result in a major problem when developing software. When senior developers abandon a software project, they leave a knowledge gap that has to be managed. In addition, new (junior) developers require some time in order to achieve the desired level of productivity. In this paper, we present a methodology to measure the effect of knowledge loss due to developer turnover in software projects. For a given software project, we measure the quantity of code that has been authored by developers that do not belong to the current development team, which we define as orphaned code. Besides, we study how orphaned code is managed by the project. Our methodology is based on the concept of software archaeology, a derivation of software evolution. As case studies we have selected four FLOSS (free, libre, open source software) projects, from purely driven by volunteers to company-supported. The application of our methodology to these case studies will give insight into the turnover that these projects suffer and how they have managed it and shows that this methodology is worth being augmented in future research.},
	keywords = {attrition, case study, developers, evince, evolution, gimp, growth, knowledge collaboration, lines of code, nautilus, quality, sloc, turnover},
	isbn = {978-0-7695-3450-3},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.1014},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-08.pdf},
	author = {Izquierdo-Cortazar, Daniel and Gregorio Robles and Ortega, Felipe and Jesus M. Gonzalez-Barahona}
}
@article {Au20099,
	title = {Virtual organizational learning in open source software development projects},
	journal = {Information \& Management},
	volume = {46},
	number = {1},
	year = {2009},
	pages = {9 - 15},
	abstract = {We studied virtual organizational learning in open source software (OSS) development projects. Specifically, our research focused on learning effects of OSS projects and the factors that affect the learning process. The number and percentage of resolved bugs and bug resolution time of 118 SourceForge.net OSS projects were used to measure the learning effects. Projects were characterized by project type, number and experience of developers, number of bugs, and bug resolution time. Our results provided evidence of virtual organizational learning in OSS development projects and support for several factors as determinants of performance. Team size was a significant predictor, with mid-sized project teams functioning best. Teams of three to seven developers exhibited the highest efficiency over time and teams of eight to 15 produced the lowest mean time for bug resolution. Increasing the percentage of bugs assigned to specific developers or boosting developer participation in other OSS projects also improved performance. Furthermore, project type introduced variability in project team performance.},
	keywords = {bug fixing, bugs, learning, Project performance, sourceforge, team size, teams, virtual organization},
	issn = {0378-7206},
	doi = {DOI: 10.1016/j.im.2008.09.004},
	url = {http://www.sciencedirect.com/science/article/B6VD0-4V1D7NT-1/2/a3bbf7652c674f753398160b8f05f6e9},
	author = {Yoris A. Au and Darrell Carpenter and Xiaogang Chen and Jan G. Clark}
}
@article {1402,
	title = {Visual querying and analysis of large software repositories},
	journal = {Empirical Software Engineering},
	volume = {14},
	year = {2009},
	month = {6/2009},
	pages = {316 - 340},
	abstract = {We present a software framework for mining software repositories. Our extensible framework enables the integration of data extraction from repositories with data analysis and interactive visualization. We demonstrate the applicability of the framework by presenting several case studies performed on industry-size software repositories. In each study we use the framework to give answers to one or several software engineering questions addressing a specific project. Next, we validate the answers by comparing them with existing project documentation, by interviewing domain experts and by detailed analyses of the source code. The results show that our framework can be used both for supporting case studies on mining software repository techniques and for building end-user tools for software maintenance support. },
	issn = {1573-7616},
	doi = {10.1007/s10664-008-9068-6},
	author = {Voinea, Lucian and Telea, Alexandru}
}
@conference {933,
	title = {Visualizing Gnome with the Small Project Observatory},
	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 = {103 - 106},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {We analyzed the gnome family of systems with the small project observatory, our online ecosystem visualization platform. We begin by briefly introducing the model of SPO. We then observe and discuss several phases in the activity of the gnome ecosystem. We follow and look at how the contributors are distributed between writing source code and doing other activities such as internationalization. We end with a visual overview of the activity of more than 900 contributors in the 10 years of existence of gnome.},
	keywords = {bugzilla, contributions, gnome, msr challenge, spo, visualization},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069487},
	attachments = {https://flosshub.org/sites/flosshub.org/files/103Lung2009a.pdf},
	author = {Lungu, Mircea and Malnati, Jacopo and Lanza, Michele}
}
@article {Xu2009151,
	title = {Volunteers{\textquoteright} involvement in online community based software development},
	journal = {Information \& Management},
	volume = {46},
	number = {3},
	year = {2009},
	note = {"Data were collected through an online survey and by searching project archives. On Sourceforge.net, each developer was uniquely identified with a user account, and the developer{\textquoteright}s performance was assessed through the number of function points accepted by the project in a certain time period, obtained through conversion and calculation from the project{\textquoteright}s code repository. Data for other constructs were obtained from the developers{\textquoteright} response to the online survey. "
"a developer{\textquoteright}s performance was measured by the number of function points made and accepted into the project during the observed time period."

project age, development status, license type, number of developers},
	pages = {151 - 158},
	abstract = {We sought to gain understanding of voluntary developers{\textquoteright} involvement in open source software (OSS) projects. Data were collected from voluntary developers working on open source projects. Our findings indicated that a voluntary developer{\textquoteright}s involvement was very important to his or her performance and that involvement was dependent on individual motivations (personal software needs, reputation and skills gaining expectation, enjoyment in open source coding) and project community factors (leadership effectiveness, interpersonal relationship, community ideology). Our work contributes theoretically and empirically to the body of OSS research and has practical implications for OSS project management.},
	keywords = {age, developers, effectiveness, function points, ideology, leadership, MOTIVATION, scm, sourceforge, status, Survey, team size, Volunteers},
	issn = {0378-7206},
	doi = {DOI: 10.1016/j.im.2008.12.005},
	url = {http://www.sciencedirect.com/science/article/B6VD0-4VP1CN0-1/2/8e1c7be4fcedd1419209c5c843ffa923},
	author = {Bo Xu and Donald R. Jones and Bingjia Shao}
}
@conference {1205,
	title = {Weaving~a~Semantic~Web~across~OSS~repositories: a~spotlight~on~bts-link,~UDD,~SWIM},
	booktitle = {4th Workshop on Public Data about Software Development (WoPDaSD 2009)},
	year = {2009},
	note = {position paper; non-experimental},
	abstract = {Several  public  repositories  and  archives  of  facts  about  libre software  projects,  developed either  by open  source  communities  or by research communities,  have been flourishing over  the Web in  the  recent  years.  These  enable  new analysis  and  support  new quality assurance tasks. 

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

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

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

The  HELIOS team welcomes  comments  on the  future  paths  that  can  be  considered  in  using  the  Semantic  Web  approach  for improving these projects. },
	keywords = {bts-link, bug tracker, bugzilla, debian, ecosystem, helios, mandriva, semantic Web, swim, udd},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HELIOS-WOPDASD-improved-Olivier.pdf},
	author = {Olivier Berger and Valentin Vlasceanu and Christian Bac and Lauri{\`e}re, St{\'e}phane}
}
@conference {939,
	title = {On what basis to recommend: Changesets or interactions?},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {155 - 158},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Different flavours of recommendation systems have been proposed to help software developers perform software evolution tasks. A number of these recommendation systems are based on changesets. When changeset information is used, recommendations are based on only the end result of the activity undertaken to complete a task. In this paper, we report on an investigation that compared how recommendations based on changesets compare to recommendations based on interactions collected as a programmer performed the task that resulted in a changeset. To provide a common basis for the comparison, our investigation considered how bug reports considered similar based on changeset information compare to bug reports considered similar based on interaction information. We found that there is no direct relationship between the bug reports found similar with the different methods, suggesting that each comparison methods captures a different aspect of the problem.},
	keywords = {bug reports, changeset, eclipse, mylyn},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069494},
	author = {Rastkar, Sarah and Murphy, Gail C.}
}
@conference {595,
	title = {What Constitutes Open Source? A Study of the Vista Electronic Medical Record Software},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	year = {2009},
	month = {2009///},
	pages = {310 - 319},
	publisher = {Springer},
	organization = {Springer},
	chapter = {27},
	abstract = {Strictly speaking, Open Source Software is any program that is covered by an Open Source Software license. However, the notion of Open Source Software Development conjures images of high-quality, market dominating products developed by armies of volunteer programmers, who work only for the joy of programming. Certainly, banner projects like Apache, the Linux kernel, and Mozilla/Firefox resemble this notion, even if they do employ significant numbers of paid programmers. This paper examines three Open Source Software projects related to the Vista Electronic Medical Record system developed and maintained by the U.S. Department of Veterans Affairs and released to the public domain. While all three claim to be {\textquotedblleft}Open Source{\textquotedblright} projects, there is considerable deviation from the strong community-oriented model that Linux, Apache, and Mozilla represent.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/What\%20Constitues\%20Open\%20Source.pdf},
	author = {Noll, John}
}
@conference {584,
	title = {What Does It Take to Develop a Million Lines of Open Source Code?},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {170 - 184},
	publisher = {Springer},
	organization = {Springer},
	chapter = {16},
	abstract = {This article presents a preliminary and exploratory study of the relationship between size, on the one hand, and effort, duration and team size, on the other, for 11 Free/Libre/Open Source Software (FLOSS) projects with current size ranging between between 0.6 and 5.3 million lines of code (MLOC). Effort was operationalised based on the number of active committers per month. The extracted data did not fit well an early version of the closed-source cost estimation model COCOMO for proprietary software, overall suggesting that, at least to some extent, FLOSS communities are more productive than closed-source teams. This also motivated the need for FLOSS-specific effort models. As a first approximation, we evaluated 16 linear regression models involving different pairs of attributes. One of our experiments was to calculate the net size, that is, to remove any suspiciously large outliers or jumps in the growth trends. The best model we found involved effort against net size, accounting for 79 percent of the variance. This model was based on data excluding a possible outlier (Eclipse), the largest project in our sample. This suggests that different effort models may be needed for certain categories of FLOSS projects. Incidentally, for each of the 11 individual FLOSS projects we were able to model the net size trends with very high accuracy (R 2 >= 0.98). Of the 11 projects, 3 have grown superlinearly, 5 linearly and 3 sublinearly, suggesting that in the majority of the cases accumulated complexity is either well controlled or don{\textquoteright}t constitute a growth constraining factor.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_16},
	attachments = {https://flosshub.org/sites/flosshub.org/files/What\%20Does\%20it\%20Take\%20to\%20Develop.pdf},
	author = {Fernandez-Ramil, Juan and Izquierdo-Cortazar, Daniel and Mens, Tom}
}
@article {1338,
	title = {What Makes Free/Libre Open Source Software (FLOSS) Projects Successful? An Agent-Based Model of FLOSS Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {1 - 13},
	abstract = {The last few years have seen a rapid increase in the number of Free/Libre Open Source Software (FLOSS) projects. Some of these projects, such as Linux and the Apache web server, have become phenomenally successful. However, for every successful FLOSS project there are dozens of FLOSS projects which never succeed. These projects fail to attract developers and/or consumers and, as a result, never get off the ground. The aim of this research is to better understand why some FLOSS projects flourish while others wither and die. This article presents a simple agent-based model that is calibrated on key patterns of data from SourceForge, the largest online site hosting open source projects. The calibrated model provides insight into the conditions necessary for FLOSS success and might be used for scenario analysis of future developments of FLOSS.},
	keywords = {Agent-Based Model, Emergent Properties, FLOSS, open source, Prediction Success, Simulation},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009040101},
	url = {http://www.public.asu.edu/~majansse/pubs/ijossp09.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ijossp09.pdf},
	author = {Radtke, Nicholas P. and Janssen, Marco A. and Collofello, James S.}
}
@conference {849,
	title = {Is Wikipedia Growing a Longer Tail?},
	booktitle = {ACM 2009 International Conference on Supporting Group Work},
	year = {2009},
	month = {05/10/2009},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Sanibel Island, FL},
	author = {Lam, S.K. and Riedl, J.}
}
@conference {851,
	title = {Wikipedians are born, not made: a study of power editors on Wikipedia},
	booktitle = {ACM 2009 International Conference on Group Work},
	year = {2009},
	month = {05/10/2009},
	pages = {51-60},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Sanibel Island, FL},
	keywords = {computer-supported, cooperative, interaction, web-based, work,},
	author = {Panciera, K. and Halfaker, A. and Terveen, L.}
}
@conference {604,
	title = {Workshop {\textendash} Serious Games and Open Source: Practice and Futures},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {361 - 362},
	publisher = {Springer},
	organization = {Springer},
	chapter = {36},
	abstract = {Computer games are increasingly used throughout our society with people playing on the bus, at home and at work. Computer games thus affect larger and larger number of people and areas in the society of today. There are even scholars who advocate that games create better environments for learning than traditional classrooms. This situation motivates the use of games and game technology for additional purposes, e.g. education, training, health care or marketing.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/.1007/978-3-642-02032-2_36},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Workshop\%20Serious\%20Games\%20and\%20Open\%20Source.pdf},
	author = {Backlund, Per and Lundell, Bj{\"o}rn and Walt Scacchi}
}
@conference {544,
	title = {Adoption of Open Source in the Software Industry},
	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 = {211 - 221},
	publisher = {Springer},
	organization = {Springer},
	chapter = {17},
	abstract = {Is Open Source Software (OSS) undergoing a transformation to a more commercially viable form? We have performed a survey to investigate the adoption of OSS in the Norwegian software industry. The survey was based on an extensive screening of software companies, with more than 700 responses. The survey results support the transformation predicted by Fitzgerald [4]. Close to 50\% of the software industry integrate OSS components into vertical solutions serving all major business sectors. In addition, more than 30\% of the 95 respondents in our survey have more than 40\% of their income from OSS related services or software. The extensive adoption of OSS in the software industry may be a precursor of the OSS adoption in other business sectors.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_17},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Adaption\%20of\%20Open\%20Source.pdf},
	author = {Hauge, {\O}yvind and S{\o}rensen, Carl-Fredrik and Conradi, Reidar}
}
@conference {1208,
	title = {Advances in the Sourceforge Research Data Archive},
	booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)},
	year = {2008},
	month = {2009},
	pages = {25-29},
	abstract = {The SourceForge Research Data Archive (SRDA), located at http://zerlot.cse.nd.edu, is a collection of Open Source Software (OSS) data and resources [6]. Over 100 researchers worldwide use the archive for research in many fields. In this paper, we describe the recent changes, the work in progress, and future plans for making the archive easier to use and for allowing more advanced research to be done with the data available.},
	keywords = {forge, forges, repositories, repository, sourceforge, srda},
	attachments = {https://flosshub.org/sites/flosshub.org/files/srda2008.pdf},
	author = {Matthew Van Antwerp and Madey, Greg}
}
@article {denBesten2008316,
	title = {The allocation of collaborative efforts in open-source software},
	journal = {Information Economics and Policy},
	volume = {20},
	number = {4},
	year = {2008},
	note = {"we have selected a set of 10 large open-source projects"
apache, cvs, gaim, gcc, ghostscript, mozilla, netbsd, openssh, postgresql, python
"Our data were extracted from logs of development activity generated by software version control systems. For each project in the selection, we extracted CVS development logs"
"We notably computed for each file in the sample, and for each month in its history, the number of distinct maintainers that had committed a change during that month, and the number of commits, the blocks of code addition, each file had received during that month."
"other variables used in the regressions are proxies for the size, age, and granularity of files; the size of a file is represented as its number of lines of code (LOCs), its age by its creation date (Youth), and its granularity by the number of functions it contains."},
	pages = {316 - 322},
	abstract = {The article investigates the allocation of collaborative efforts among core developers (maintainers) of open-source software by analyzing on-line development traces (logs) for a set of 10 large projects. Specifically, we investigate whether the division of labor within open-source projects is influenced by characteristics of software code. We suggest that the collaboration among maintainers tends to be influenced by different measures of code complexity. We interpret these findings by providing preliminary evidence that the organization of open-source software development would self-adapt to characteristics of the code base, in a {\textquoteright}stigmergic{\textquoteright} manner.},
	keywords = {age, apache, complexity, cvs, division of labor, functions, gaim, gcc, ghostscript, lines of code, loc, log files, mozilla, netbsd, openssh, postgresql, python, revision control, scm, size, source code, Stigmergy, version control},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.06.003},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4SSG4PN-1/2/88b3824c30a31c18929d8a5ca6d64f62},
	author = {den Besten, Matthijs and Jean-Michel Dalle and Galia, Fabrice}
}
@conference {861,
	title = {Altruism, Selfishness, and Destructiveness on the Social Web},
	booktitle = {5th International Conference on Adaptive Hypermedia and Adaptive Web-Based Systems},
	year = {2008},
	month = {7/29/2008},
	pages = {9-11},
	publisher = {Springer-Verlag},
	organization = {Springer-Verlag},
	address = {Hannover, Germany},
	isbn = {978-3-540-70984-8 },
	author = {Riedl, J.},
	editor = {Nejdl, W., Kay, J., Pu, P., Herder, E.}
}
@conference {Hill:2008:AAM:1370750.1370771,
	title = {AMAP: automatically mining abbreviation expansions in programs to enhance software maintenance tools},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {79{\textendash}88},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {When writing software, developers often employ abbreviations in identifier names. In fact, some abbreviations may never occur with the expanded word, or occur more often in the code. However, most existing program comprehension and search tools do little to address the problem of abbreviations, and therefore may miss meaningful pieces of code or relationships between software artifacts. In this paper, we present an automated approach to mining abbreviation expansions from source code to enhance software maintenance tools that utilize natural language information. Our scoped approach uses contextual information at the method, program, and general software level to automatically select the most appropriate expansion for a given abbreviation. We evaluated our approach on a set of 250 potential abbreviations and found that our scoped approach provides a 57\% improvement in accuracy over the current state of the art.},
	keywords = {automatic abbreviation expansion, azureus, itext.net, liferay, maintenance, natural language, openoffice.org, program comprehension, source code, tiger envelopes, tools},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370771},
	url = {http://doi.acm.org/10.1145/1370750.1370771},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p79-hill.pdf},
	author = {Hill, Emily and Fry, Zachary P. and Boyd, Haley and Sridhara, Giriprasad and Novikova, Yana and Pollock, Lori and Vijay-Shanker, K.}
}
@conference {534,
	title = {Analysis of Coordination Between Developers and Users in the Apache Community},
	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 = {81 - 92},
	publisher = {Springer},
	organization = {Springer},
	chapter = {7},
	abstract = {Coordination is one of the keys for the success of open source software (OSS) communities because geographically distributed members need to collaborate on their work using communication tools (e.g., mailing lists, bulletin board systems, bug tracking systems, and so on). In this paper, we investigated the informal social structure among developers and users by analyzing two mailing lists of developers and users in the Apache community based on betweenness centrality, one centrality measure proposed by Freeman. From the analysis results, we found that (1) participants with high betweenness coordinated activities between developers and users and (2) some participants have been functioning as coordinators in the community for a long time.
},
	keywords = {apache, email, mailing list},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Analysis\%20of\%20Coordination.pdf},
	author = {Kamei, Yasutaka and Matsumoto, Shinsuke and Maeshima, Hirotaka and Onishi, Yoji and Ohira, Masao and Matsumoto, Ken-ichi}
}
@conference {Wermelinger:2008:AEE:1370750.1370783,
	title = {Analyzing the evolution of eclipse plugins},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {133{\textendash}136},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Eclipse is a good example of a modern component-based complex system that is designed for long-term evolution, due to its architecture of reusable and extensible components. This paper presents our preliminary results about the evolution of Eclipse{\textquoteright}s architecture, based on a lightweight and scalable analysis of the metadata in Eclipse{\textquoteright}s sources. We find that the development of Eclipse follows a systematic process: most architectural changes take place in milestones, and maintenance releases only make exceptional changes to component dependencies. We also found a stable architectural core that remains since the first release.},
	keywords = {architectural evolution, cvs, eclipse, metadata, msr challenge, releases, source code},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370783},
	url = {http://doi.acm.org/10.1145/1370750.1370783},
	author = {Wermelinger, Michel and Yu, Yijun}
}
@conference {563,
	title = {Applying Open Source Development Practices Inside a Company},
	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 = {381 - 387},
	publisher = {Springer},
	organization = {Springer},
	chapter = {36},
	abstract = {Open Source Software development is seen as a panacea by many companies. The promise of community-style development, innovation and cost savings drive the wider adoption of OSS in companies. However, it is still difficult to institutionalize the open and agile culture of sharing innovation especially into larger departmentalized organizations. The aim of this research paper is to investigate the characteristics of one successful OSS development implementation approach limited inside a company (Inner source). Based on our data, we argue that there are possibilities for employing OSS as a new kind of development process within a company and leveraging thus the innovation potential inside the company.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_36},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Applying\%20Open\%20Source\%20Development.pdf},
	author = {Juho Lindman and Rossi, Matti and Marttiin, Pentti}
}
@conference {Wang:2008:ADD:1368088.1368151,
	title = {An approach to detecting duplicate bug reports using natural language and execution information},
	booktitle = {Proceedings of the 30th international conference on Software engineering},
	series = {ICSE {\textquoteright}08},
	year = {2008},
	pages = {461{\textendash}470},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {An open source project typically maintains an open bug repository so that bug reports from all over the world can be gathered. When a new bug report is submitted to the repository, a person, called a triager, examines whether it is a duplicate of an existing bug report. If it is, the triager marks it as DUPLICATE and the bug report is removed from consideration for further work. In the literature, there are approaches exploiting only natural language information to detect duplicate bug reports. In this paper we present a new approach that further involves execution information. In our approach, when a new bug report arrives, its natural language information and execution information are compared with those of the existing bug reports. Then, a small number of existing bug reports are suggested to the triager as the most similar bug reports to the new bug report. Finally, the triager examines the suggested bug reports to determine whether the new bug report duplicates an existing bug report. We calibrated our approach on a subset of the Eclipse bug repository and evaluated our approach on a subset of the Firefox bug repository. The experimental results show that our approach can detect 67\%-93\% of duplicate bug reports in the Firefox bug repository, compared to 43\%-72\% using natural language information alone.},
	keywords = {bug report, duplicate bug report, execution information, information retrieval, natural language},
	isbn = {978-1-60558-079-1},
	doi = {10.1145/1368088.1368151},
	url = {http://doi.acm.org/10.1145/1368088.1368151},
	author = {Wang, Xiaoyin and Zhang, Lu and Xie, Tao and Anvik, John and Sun, Jiasu}
}
@conference {548,
	title = {Archetypal Internet-Scale Source Code Searching},
	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 = {257 - 263},
	publisher = {Springer},
	organization = {Springer},
	chapter = {21},
	abstract = {Programmers often search for Open Source code to use in their projects. To understand how and why programmers search for source code, we onducted a web-based survey and collected data from 69 respondents, including 58 specific examples of searches. Analyzing these anecdotes, we found that they could be categorized along two orthogonal dimensions: motivation (reuse vs. reference example) and size of search target. The targets of these searches could range in size from a block (a few lines of code) to a subsystem (e.g. library or API), to an entire system. Within these six combinations of motivations and target sizes, nine repeating motifs, or archetypes, were created to characterize Internet-scale source code searching. Tools used for searching and the criteria for selecting a component are also discussed. We conclude with guidance on how these archetypes can inform better evaluation of Internet-scale code search engines, as well as the design of new features for these tools.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_21},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Archetypal\%20Internet-Scale\%20Source.pdf},
	author = {Umarji, Medha and Sim, Susan and Lopes, Crista}
}
@conference {1211,
	title = {Are FLOSS developers committing to CVS/SVN as much as  they are talking in mailing lists? Challenges for Integrating  data from Multiple Repositories},
	booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)},
	year = {2008},
	month = {09/2008},
	pages = {49-54},
	abstract = {This paper puts forward a framework for investigating Free and Open Source Software (F/OSS) developers activities in both source code and mailing lists repositories. We used data dumps of fourteen pro jects from the FLOSSMetrics (FM) retrieval system. Our intentions are (i) to present a possible methodology, its advantages and disadvantages which can benefit future researchers using some aspects of the FM retrieval system{\textquoteright}s data dumps, and (ii) discuss our initial research results on the contributions developers make to both coding and lists activities.},
	keywords = {cvs, cvsanaly, developers, email, email archives, flossmetrics, mailing list, mlstats, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/49-542008.pdf},
	author = {Sowe, Sulayman K. and Samoladas, Ioannis and Ioannis Stamelos and Lefteris Angelis}
}
@conference {556,
	title = {Assessing Innovation in the Software Sector: Proprietary vs. FOSS Production Mode. Preliminary Evidence from the Italian Case},
	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 = {325 - 331},
	publisher = {Springer},
	organization = {Springer},
	chapter = {29},
	abstract = {Innovation in the software sector is a widely debated issue. Which are the most important dimensions to assess innovation in this field? Can we measure innovative processes carried out by software companies and what kind of innovation do they develop? Are FOSS solutions more innovative than proprietary ones? These are the research questions we endeavor to answer in this paper providing some empirical evidence, obtained using an original methodology of collecting experts{\textquoteright} evaluations on the innovation level of 134 solutions provided by a group of Italian Small and Medium Enterprises.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Assessing\%20Innovation\%20in\%20the\%20Software\%20Sector.pdf},
	author = {Dario Lorenzi and Cristina Rossi}
}
@conference {flosswp408,
	title = {Asynchronous Decision-Making in Distributed Teams},
	booktitle = {Computer Supported Cooperative Work 2008},
	year = {2008},
	month = {July},
	pages = {1{\textendash}2},
	abstract = {Extensive use of CSCW applications can influence group decision-making practices. Unlike previous research focused on the influence of synchronous ICTs, our study examines how group decisions are made in asynchronous communication channels. Our inductive qualitative analysis of 360 decision episodes of six FLOSS projects revealed diversity in decision-making practices, which appears to be related to differences in project effectiveness and task type. We also find that standardization of procedures through CSCW tools transforms the nature of some software development work from non-routine to standard procedure.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CSCW2008FLOSSposter_sub.pdf , https://flosshub.org/sites/flosshub.org/files/CSCW2008Poster11x17sub.pdf},
	author = {Li, Qing and Robert Heckman and Eileen Allen and Kevin Crowston and Eseryel, U. Yeliz and James Howison and Andrea Wiggins}
}
@conference {1210,
	title = {Author Entropy: A Metric for Characterization  of Software Authorship Patterns},
	booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)},
	year = {2008},
	note = {used flossmole to get sample of SF developers},
	month = {2008},
	pages = {42-47},
	abstract = {We propose the concept of author entropy and describe how file-level entropy measures may be used to understand and characterize authorship patterns within individual files, as well as across an entire project. As a proof of concept, we compute author entropy for 28,955 files from 33 open-source projects. We explore patterns of author entropy, identify techniques for visualizing author entropy, and propose avenues for further study. },
	keywords = {developers, entropy, flossmole, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/entropy2008.pdf},
	author = {Taylor, Quinn C. and Stevenson, James E. and Delorey, Daniel P. and Knutson, Charles D.}
}
@book {48,
	title = {Biobazaar: The Open Source Revolution and Biotechnology},
	year = {2008},
	publisher = {Harvard University Press},
	organization = {Harvard University Press},
	author = {Janet Hope}
}
@conference {971,
	title = {Branching and merging in the repository},
	booktitle = {the 2008 international workshopProceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {19-22},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Two of the most complex operations version control software allows a user to perform are branching and merging. Branching provides the user the ability to create a copy of the source code to allow changes to be stored in version control but outside of the trunk. Merging provides the user the ability to copy changes from a branch to the trunk. Performing a merge can be a tedious operation and one that may be error prone. In this paper, we compare file revisions found on branches with those found on the trunk to determine when a change that is applied to a branch is moved to the trunk. This will allow us to study how developers use merges and to determine if merges are in fact more error prone than other commits.},
	keywords = {argouml, changes, cvs2svn, diffj, revision, scm, source code, version control},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370754},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p19-williams.pdf},
	author = {Spacco, Jamie and Williams, Chadd C.}
}
@article {Crowston:2008,
	title = {Bug Fixing Practices within Free/Libre Open Source Software Development Teams},
	journal = {Journal of Database Management},
	volume = {19},
	number = {2},
	year = {2008},
	note = {"Projects to be studied were selected from those hosted on SourceForge, (http://sourceforge.net/)"
"we chose projects for which data we need for our analysis are publicly available, meaning a large number of bug reports"
"we chose teams with more than 8 developers"
"Only 140 projects of SourceForge met the first two requirements in 2002 when we drew our sample"
kicq, gaim, phpmyadmin, dynapi
"First, we obtained data indica- tive of the effectiveness of each project, such as its level of activity, number of downloads and development status"
"we elected to use objective data about the bug- fixing process. Hence, the main source of data about the bug-fixing process was obtained from the archives of the bug tracking system, which is the tool used to support the bug-fixing process"},
	pages = {1{\textendash}30},
	abstract = {Free/libre open source software (FLOSS, e.g., Linux or Apache) is primarily developed by distributed teams. Developers contribute from around the world and coordinate their activity almost exclusively by means of email and bulletin boards, yet some how profit from the advantages and evade the challenges of distributed software development. In this article we investigate the structure and the coordination practices adopted by development teams during the bug-fixing process, which is considered one of main areas of FLOSS project success. In particular, based on a codification of the messages recorded in the bug tracking system of four projects, we identify the accomplished tasks, the adopted coordination mechanisms, and the role undertaken by both the FLOSS development team and the FLOSS community. We conclude with suggestions for further research.},
	keywords = {activity, bug tracker, bug tracking system, coordination, downloads, dynapi, effectiveness, FLOSS, gaim, kicq, phpmyadmin, project success, size, status},
	issn = {1063-8016},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonScozziJDBM2008.pdf},
	author = {Kevin Crowston and Barbara Scozzi}
}
@article {147,
	title = {The business of open source},
	journal = {Communications of the ACM},
	volume = {51},
	number = {4},
	year = {2008},
	note = {Times Cited: 0},
	pages = {41-46},
	author = {Watson, R. T. and Boudreau, M. C. and York, P. T. and Greiner, M. E. and Wynn, D.}
}
@article {1391,
	title = {Challenges and strategies in the use of Open Source Software by Independent Software Vendors},
	journal = {Information and Software Technology},
	volume = {50},
	year = {2008},
	month = {8/2008},
	pages = {991 - 1002},
	abstract = {Open Source Software (OSS) has already been adopted by a large number of organizations. An important {\textendash} but sometimes neglected {\textendash} group of OSS users are Independent Software Vendors (ISVs). ISVs often develop their applications on top of OSS platform software. Frequently, this requires making several extensions and modifications to these OSS components. We identify a number of challenges that ISVs face in handling these extensions and modifications. Next, we describe several strategies ISVs can follow in maintaining these modifications. Finally, we suggest an opportunity for a closer collaboration between OSS projects and ISVs which could be mutually beneficial.},
	keywords = {Contributing, Independent Software Vendor},
	issn = {09505849},
	doi = {10.1016/j.infsof.2007.09.001},
	author = {Ven, Kris and Mannaert, Herwig}
}
@booklet {493,
	title = {Champions of Revealing - The Role of Open Source Developers in Commercial Firms},
	year = {2008},
	month = {Jan},
	abstract = {The link between firms engaging in open source software (OSS) development and the OSS community is established by individual developers. This linkage might entail a principal-agent issue due to the developer{\textquoteright}s double allegiance to firm and OSS community, and expose the firm to the risk of losing intellectual property. Using both interviews and a large-scale survey, I substantiate the importance of the developer{\textquoteright}s role. However, neither interview data nor regression analysis show indications of commercially harmful revealing behavior induced by ""Free Software ideology."" Management, on the other hand, sometimes seems to be overly concerned about openness. I conclude that a more positive stance towards openness will allow firms to better share in the benefits of open innovation processes.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Henkel_Champions_of_revealing_2008-01.pdf},
	author = {Joachim Henkel}
}
@conference {549,
	title = {Channeling Firefox Developers: Mom and Dad Aren{\textquoteright}t Happy Yet},
	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 = {265 - 271},
	publisher = {Springer},
	organization = {Springer},
	chapter = {22},
	abstract = {Firefox, a browser targeted at mainstream users, has been one of the big successes of open source development in recent years. That Firefox succeeded where earlier attempts failed is undoubtedly due to the particular choices that were made in the process of development. In this paper, we look at this process in more detail. Mining bug reports and feature requests related to Firefox in Mozilla{\textquoteright}s Bugzilla bug tracker system, we find that the attention developers devoted to reports and requests was influenced by several factors. Most importantly, other things being equal, reports and requests from outsiders increasingly tend to be ignored. While such behavior may have helped to shield Firefox from the {\textquotedblleft}alpha-geek power user{\textquotedblright} in the early stages of development, it also makes it difficult for {\textquotedblleft}mom and dad{\textquotedblright} to let their voice be heard even after they have adopted Firefox.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_22},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Channeling\%20Firefox\%20Developers.pdf},
	author = {Jean-Michel Dalle and den Besten, Matthijs and Masmoudi, H{\'e}la}
}
@booklet {517,
	title = {Claiming Copyleft in Open Source Software:  What if the Free Software Foundation{\textquoteright}s General Public License (GPL) had been Patented?},
	year = {2008},
	month = {Jan},
	abstract = {Patent law, by necessity, needs some way to evaluate inventiveness. Otherwise, it will grant rights to advances not worth ""the embarrassment of an exclusive patent."" The innovations of version two of the Free Software Foundation{\textquoteright}s (FSF) GNU General Public License (GPLv2), arriving in 1991, could not, under U.S. patent law at that time, have been meaningfully measured against patent law{\textquoteright}s criteria, often referred to as the five elements of patentability. The first element of patentability, statutory subject matter, would have excluded the GPLv2{\textquoteright}s copyright-based licensing technique as a ""business method."" A variety of industry developments in the decades following GPLv2{\textquoteright}s arrival, combined with the license{\textquoteright}s potent ideological force and clever use of copyright law, propelled FOSS licensing into a prominent and path-breaking place within information technology worldwide. Its force and presence, and lightning-rod character, have grown over time, with GPLv2 remaining the dominant license in mind-share, if not code-share. In addition, all of this occurred without patent protection for GPLv2{\textquoteright}s unique licensing technique. This then raises the counter-factual inquiry for this symposium article: what might have occurred differently if GPLv2{\textquoteright}s licensing method had been patentable? In other words, if the U.S. patent law of statutory subject matter in 1991 was sufficiently permissive, and if the FSF and Richard Stallman successfully patented the novel licensing approaches of GPLv2, would patent protection have altered the FOSS movement{\textquoteright}s two-decade trajectory through information technology and the Internet? If so, can we estimate in what ways? The Article{\textquoteright}s assessment is that GPLv2 could readily meet the other four elements of patentability (with non-obviousness being the closest call compared to prior sublicensing schemes), and that the FOSS trajectory would change minimally, due to a variety of factors, including practical constraints on the enforcement potency of patent claims to GPLv2, competition from other types of FOSS licensing, and strategic considerations for a variety of players and camps within the FOSS movement. However, in the counterfactual, license proliferation diminishes, and dual licensing may be foreclosed.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Vetter.ClaimingCopyleftInOSS-WhatIfGPLPatented.2008Mich.St_.L.Rev_.279.pdf},
	author = {Greg R Vetter}
}
@conference {1206,
	title = {Collecting data from distributed FOSS projects},
	booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)},
	year = {2008},
	note = {"We selected three projects from the initial set of projects: Linux 2.6, an operating system kernel, gimp, a graphics program, and Blender, a 3d content creation suite."
"To acquire data from each data source, we wrote special programs based on the earlier prototypes....The first program extracts information from mailing list archives....The second program obtains bug reports from bug tracking systems....The third program obtains source code from network-accessible version control systems and runs metric calculations on it."},
	month = {2009},
	pages = {8-13},
	abstract = {A key trait of Free and Open Source Software (foss) development is its distributed nature. Nevertheless, two project-level operations, the fork and the merge of program code, are among the least well understood events in the lifespan of a foss project. Some projects have explicitly adopted these operations as the primary means of concurrent development. In this study, we examine the effect of highly distributed software development, as found in the Linux kernel project, on collection and modelling of software development data. We find that distributed development calls for sophisticated temporal modelling techniques where several versions of the source code tree can exist at once. Attention must be turned towards the methods of quality assurance and peer review that projects employ to manage these parallel source trees. Our analysis indicates that two new metrics, fork rate and merge rate, could be useful for determining the role of distributed version control systems in foss projects. The study 
presents a preliminary data set consisting of version control and mailing list data. },
	keywords = {bitkeeper, bug tracking system, cvs, distributed, email archive, fork rate, git, life cycle, linux, linux kernel, mailing list, merge rate, subversion, svn, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/fagerholm.pdf},
	author = {Fagerholm, Fabian and Taina, Juha}
}
@booklet {511,
	title = {Competitive Implications of Software Open-Sourcing},
	year = {2008},
	month = {Aug},
	abstract = {This paper is concerned with the economic trade-offs associated with open-sourcing, the business strategy of releasing free open-source versions of commercial software products. The effect of the release of open-source versions on the customers{\textquoteright} perception of products is an important determinant of open-sourcing outcomes. We model open-sourcing as a strategic option for firms that compete in the market for software products. Of particular importance in our model is the effect of open-sourcing on customer values and the possibility for better customization offered by the open-source products. We show that open-sourcing can arise as an equilibrium outcome in our simple two-stage game. If the enhancement of customer values from open-sourcing is moderate or high, firms may find it optimal to release open-source versions of their products.},
	url = {http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1185374},
	author = {Jai Asundi and Octavian Carare and Kutsal Dogan}
}
@conference {1209,
	title = {Computer support for discovering oss processes},
	booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)},
	year = {2008},
	month = {2008},
	pages = {31-33},
	abstract = {Large scale open source software (OSS) projects offer a wide range of documentation of the software processes that have enabled their success. Discovering these processes has been shown to be difficult to achieve.  This paper describes our experiences with providing computer support for discovering OSS processes from project data.  We discuss challenges of collecting and analyzing data from multiple types of project artifacts and how to address them. },
	keywords = {artifacts, Firefox, process management, zotero},
	attachments = {https://flosshub.org/sites/flosshub.org/files/jensen2008.pdf},
	author = {Chris Jensen and Walt Scacchi}
}
@conference {1460670,
	title = {The confusion of crowds: non-dyadic help interactions},
	booktitle = {CSCW {\textquoteright}08: Proceedings of the 2008 ACM conference on Computer supported cooperative work},
	year = {2008},
	pages = {699{\textendash}702},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Help-giving interactions in open source technical support 
often involve more people than the conventional help-giver 
help-seeker pair. Contributions include lightweight but 
useful me-too contributions from fellow help-seekers. 
Problems with the reuse of help documentation may be 
resolved by contextualized discussions, and those 
discussions themselves are found to be substantially reused. },
	keywords = {help-giving, technical help},
	isbn = {978-1-60558-007-4},
	doi = {http://doi.acm.org/10.1145/1460563.1460670},
	author = {Singh, V and Twidale, M.B}
}
@conference {504,
	title = {Continuous Integration in Open Source Software Development},
	booktitle = {Fourth International Conference on Open Source Software},
	year = {2008},
	month = {Sept},
	abstract = {Commercial software firms are increasingly using and contributing to open source software. Thus, they need to understand and work with open source software development processes. This paper investigates whether the practice of continuous integration of agile software development methods has had an impact on open source software projects. Using fine-granular data from more than 5000 active open source software projects we analyze the size of code contributions over a project{\textquoteright}s life-span. Code contribution size has stayed flat. We interpret this to mean that open source software development has not changed its code integration practices. In particular, within the limits of this study, we claim that the practice of continuous integration has not yet significantly influenced the behavior of open source software developers.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/oss-2008-continuous-integration-final.pdf},
	author = {Amit Deshpande and Dirk Riehle}
}
@conference {550,
	title = {Continuous Integration in 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 = {273 - 280},
	publisher = {Springer},
	organization = {Springer},
	chapter = {23},
	abstract = {Commercial software firms are increasingly using and contributing to open source software. Thus, they need to understand and work with open source software development processes. This paper investigates whether the practice of continuous integration of agile software development methods has had an impact on open source software projects. Using fine-granular data from more than 5000 active open source software projects we analyze the size of code contributions over a project{\textquoteright}s life-span. Code contribution size has stayed flat. We interpret this to mean that open source software development has not changed its code integration practices. In particular, within the limits of this study, we claim that the practice of continuous integration has not yet significantly influenced the behavior of open source software developers.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Continous\%20Integration.pdf},
	author = {Amit Deshpande and Dirk Riehle}
}
@conference {870,
	title = {Crafting the initial user experience to achieve community goals},
	booktitle = {ACM Conference on recommender Systems},
	year = {2008},
	publisher = {ACM},
	organization = {ACM},
	address = {Lausanne, Switzerland},
	isbn = {978-1-60558-093-7},
	author = {Drenner, S. and Sen, S. and Terveen, L.}
}
@conference {1207,
	title = {Cross-repository data linking with RDF and OWL},
	booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)},
	year = {2008},
	note = {non-experimental},
	month = {2009},
	pages = {15-22},
	abstract = {This paper provides an approach to the problem of integrating data from multiple research repositories for FLOSS 
data. It introduces semantic web technologies (RDF, OWL, OWL-DL reasoners and SPARQL) to argue that these are useful for building shared research infrastructure. The paper illustrates its point by describing parts of an ontology developed for the integration and analysis of project communications drawn from FLOSSmole, the Notre Dame archive and direct collection of data. RDF vocabularies provide a way to agree on things we agree about as well as a way to be clearer about ways in which we disagree.},
	keywords = {data integration, flossmole, forges, integration, owl, RDF, repositories, semantic, semantic Web, sparql, srda},
	attachments = {https://flosshub.org/sites/flosshub.org/files/howison2008.pdf},
	author = {Howison, James}
}
@mastersthesis {79,
	title = {Design for quality: The case of Open Source Software Development},
	volume = {PhD},
	year = {2008},
	school = {New York University},
	type = {doctoral dissertation},
	address = {New York, NY},
	author = {Conley, Caryn A.}
}
@conference {557,
	title = {Detecting Agility of Open Source Projects Through Developer Engagement},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {333 - 341},
	publisher = {Springer},
	organization = {Springer},
	chapter = {30},
	abstract = {The principles behind the agile development methods and common practise within the Open Source community are vastly different. In recent years there has been a rise of interest in these, in order to detect and inform on areas of compatible shared practises. This paper argues that it is possible to quantify the level of agility displayed by Open Source projects. An indicator of agility, the Mean Developer Engagement (MDE) metric is introduced and tested through the analysis of public project data. Projects sampled from two repositories (KDE and SourceForge) are studied and a hypothesis is formulated: projects from the two samples display a similar level of MDE. This paper provides two main contributions: first, the MDE metric is shown to vary significantly between the KDE and SourceForge projects. Second, by combining MDE with a project{\textquoteright}s lifespan, it is also shown that SourceForge projects have insufficient uptake of new developers resulting in more active, shorter, initial activity, and in a quicker {\textquotedblleft}burning out{\textquotedblright} of the projects.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_30},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Detecting\%20Agility\%20of\%20Open\%20Source\%20Projects.pdf},
	author = {Adams, Paul and Capiluppi, Andrea and de Groot, Adriaan}
}
@conference {970,
	title = {Determinism and evolution},
	booktitle = {Proceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {1-9},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {It has been proposed that software evolution follows a Self-Organized Criticality (SOC) dynamics. This fact is supported by the presence of long range correlations in the time series of the number of changes made to the source code over time. Those long range correlations imply that the current state of the project was determined time ago. In other words, the evolution of the software project is governed by a sort of determinism. But this idea seems to contradict intuition. To explore this apparent contradiction, we have performed an empirical study on a sample of 3,821 libre (free, open source) software projects, finding that their evolution projects is short range correlated. This suggests that the dynamics of software evolution may not be SOC, and therefore that the past of a project does not determine its future except for relatively short periods of time, at least for libre software.},
	keywords = {changes, evolution, source code, sourceforge},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370752},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p1-herraiz.pdf},
	author = {Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Gregorio Robles and Herraiz, Israel}
}
@booklet {522,
	title = {Developing {\textquoteright}FLOSS{\textquoteright} - A Market Driven Investment: First Evidence from a Francophone Companies Survey},
	year = {2008},
	abstract = {Over the last few years, FLOSS (""Free Libre Open Source Software"") has become a commercially viable reality of the first order. It is viewed as an extreme case of open innovation (Chesbrough, 2003), and thus of a laboratory for analysing innovation production in Internet based/knowledge based industries.

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

To do so, we surveyed francophone companies (France, Belgium, Switzerland) affirming a utilization of FLOSS in their commercial activity. Based on roughly 500 companies concerned, we obtained 141 usable responses and, via an ascendant hierarchical clustering (AHC) we statistically verified a link between FLOSS commercial strategies and degree of involvement into communities. We propose a typology of commercial strategies explaining this differences in involvement.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/NJullien_firms_strategies_regarding_FLOSS_octobre.pdf , https://flosshub.org/sites/flosshub.org/files/Jullien_4-2008.pdf},
	author = {Nicolas Jullien}
}
@article {1084,
	title = {Dynamics of innovation in an "open source" collaboration environment: lurking, laboring, and launching FLOSS projects on SourceForge},
	journal = {Industrial and Corporate Change},
	volume = {17},
	year = {2008},
	note = {"For the purposes of this study, we are able to draw upon micro-level data pertaining to the activities undertaken during the period between the beginning of September 2000 and December 2002 by the entire cohort of 222,835 individuals who had registered on SF.net during the 14 months from September 1, 2000 through October 26, 2001."
"The statistical analysis in this article is based upon an edited dataset (referred to here as the SFnetDataset) covering the SourceForge cohort of 222,835 individuals who registered on SF.net during the 14 months from September 1, 2000 through October 26, 2001."
They appear to be using their own dataset which is from 2000-2001 even though this paper is from 2008},
	month = {07/2008},
	pages = {647 - 710},
	abstract = {A systems analysis perspective is adopted to examine the critical properties of the Free/Libre/Open Source Software (FLOSS) mode of innovation, as reflected on the SourceForge platform (SF.net). This approach re-scales March{\textquoteright}s (1991) framework and applies it to characterize the {\textquotedblleft}innovation system{\textquotedblright} of a {\textquotedblleft}distributed organization{\textquotedblright} of interacting agents in a virtual collaboration environment, rather than to innovation within a firm. March (1991) views the process of innovation at the organizational level as the coupling of sub-processes of exploration and exploitation. Correspondingly, the innovation system of the virtual collaboration environment represented by SF.net is an emergent property of two {\textquotedblleft}coupled{\textquotedblright} processes: one involves the interactions among agents searching the locale for information and knowledge resources to use in designing novel software products (i.e., exploration), and the other involves the mobilization of individuals{\textquoteright} capabilities for application in the software development projects that become established on the platform (i.e., exploitation). The micro-dynamics of this system are studied empirically by constructing transition probability matrices representing the movements of 222,835 SF.net users among seven different activity states, which range from {\textquotedblleft}lurking{\textquotedblright} (not contributing or contributing to projects without becoming a member) to {\textquotedblleft}laboring{\textquotedblright} (joining one or more projects as members), and to {\textquotedblleft}launching{\textquotedblright} (founding one or more projects) within each successive 6-month interval. The estimated probabilities are found to form first-order Markov chains describing ergodic processes. This makes it possible the computation of the equilibrium distribution of agents among the states, thereby suppressing transient effects and revealing persisting patterns of project joining and project launching. The latter show the FLOSS innovation process on SF.net to be highly dissipative: a very large proportion of the registered {\textquotedblleft}developers{\textquotedblright} fail to become even minimally active on the platform. There is nevertheless an active core of mobile project joiners, and a (still smaller) core of project founders who persist in creating new projects. The structure of these groups{\textquoteright} interactions (as displayed within the 3-year period examined) is investigated in detail, and it is shown that it would be sufficient to sustain both the exploration and exploitation phases of the platform{\textquoteright}s global dynamics.},
	keywords = {contributors, core, developers, roles, SFnetDataset, sourceforge, users, virtual communities, virtual organization, virtual organizations},
	issn = {1464-3650},
	doi = {10.1093/icc/dtn026},
	author = {David, P. A. and Rullani, F.}
}
@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}
}
@conference {558,
	title = {Facilitating Social Network Studies of FLOSS using the OSSNetwork Environment},
	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 = {343 - 350},
	publisher = {Springer},
	organization = {Springer},
	chapter = {31},
	abstract = {Open source projects are typical examples of successful distributed software development projects. Understanding how coordination in these projects takes place can provide important lessons to Software Engineering researchers and practitioners. This understanding has been achieved using different research methods, including, surveys, case studies and social network analysis. However, to conduct these studies each researcher needs to build his own infra-structure from the scratch, a time consuming and error-prone task. This paper aims to alleviate this problem by describing an environment, the OSSNetwork, which allows the automatic data collection of open source repositories. Data collected by the OSSNetwork is aimed to support the construction, visualization, and analysis of social networks. This environment is extensible, therefore facilitating empirical studies of open source projects.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Facilitating\%20Social\%20Network\%20Studies.pdf},
	author = {Balieiro, Marco and de J{\'u}nior, Samuel and De Souza, Cleidson}
}
@article {521,
	title = {FLOSS-like education transfer report},
	year = {2008},
	month = {Sept},
	abstract = {Free/Libre and Open Source Software (FLOSS) communities are not only an exemplar for successful software development, but also for well working learning environments. Yet little is known about how learning occurs in the FLOSS communities and what the underlying success factors are. FLOSS communities might be seen as an example of {\textquoteright}Best Practice{\textquoteright} in how ICT can help to improve education in terms of learning processes, up to date content and open inclusive education where no learner is excluded from participation.The FLOSSCOM project was undertaken in order to evaluate how learning in FLOSS is organised and if, to which degree, and how FLOSS learning principles can be transferred to and used for the improvement of ICT supported formal education. Precisely, the FLOSSPOLS project intended to- identify the factors that contribute to successful knowledge construction in informal learning communities, such as the FLOSS communities- analyze the effectiveness of a FLOSS-like learning community in a formal educational setting- provide case studies, scenarios and guidelines for teachers and decision-makers on how to successfully embed such learning communities within formal educational environments to enhance student progression, retention and achievement- evaluate the project and disseminate the results to the wider community.This report is the third and final report of the FLOSSCOM project. It aims to provide scenarios and guidelines for teachers and decision-makers as practical documentation on how principles of FLOSS-like informal learning communities might be transferred to formal educational environments.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FLOSSCOM_WP5_PHASE_3_REPORT.pdf},
	author = {Andreas Meiszner}
}
@conference {529,
	title = {Forging A Community {\textendash} Not: Experiences On Establishing An Open Source Project},
	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 = {15 - 27},
	publisher = {Springer},
	organization = {Springer},
	chapter = {2},
	abstract = {Open source has recently become a practical and advocated fashion to develop, integrate, and license software. As a consequence, open source communities that commonly perform the development work are becoming important in the practice of software engineering. A community that is lively can often produce high-quality systems that continuously grow in terms of features, whereas communities that do not gain interest will inevitably perish. Despite their newly established central role, creation, organization, and management of such communities have not yet been widely studied from the viewpoint of software engineering practices. In this paper, we discuss experiences gained in the scope of Laika, an open source project established to develop an integrated software development environment for developing applications that run in Linux based mobile devices.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_2},
	attachments = {https://flosshub.org/sites/flosshub.org/files/forging\%20a\%20community.pdf},
	author = {J{\"a}rvensivu, Juha and Mikkonen, Tommi}
}
@conference {Gobeille:2008:FP:1370750.1370763,
	title = {The FOSSology project},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {47{\textendash}50},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {By its nature, the availability of FOSS has given computer scientists a large body of software and software projects to analyze. By having available source, version control system metadata, and open project communities, much can be learned about a software project, software development and collaborative project development. The goal of the FOSSology project is to create a public, open source software repository, together with tools to facilitate analysis, storage, and sharing of open source software and its metadata. FOSSology does license detection today.},
	keywords = {abiword, fossology, license analysis, licenses},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370763},
	url = {http://doi.acm.org/10.1145/1370750.1370763},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p47-gobeille.pdf},
	author = {Gobeille, Robert}
}
@booklet {512,
	title = {The Foundations of Openness},
	year = {2008},
	month = {Jul},
	abstract = {This project explores the notion of openness in software projects. It contextualizes different facets of openness and considers their individual and collective usefulness. It provides a tentative evaluative schema to allow others to weigh up specific criteria that may be important to them. It acknowledges that these criteria may have different weightings for different people, e.g. governance vs open standards vs code licence. The object is *not* a blanket recommendation for openness in all facets of a project. Rather it is a tool for projects, and those who use those projects, to investigate and illuminate the choices being made as well as the implication of open and closed approaches.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Foundations-of-openness-V2-release.pdf},
	author = {Pia Waugh and Randy Metcalfe}
}
@conference {528,
	title = {A Framework for Evaluating Managerial Styles 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 = {1 - 14},
	publisher = {Springer},
	organization = {Springer},
	chapter = {1},
	abstract = {This paper presents the Software Project Governance Framework (SPGF) for characterizing management of software projects, based on mechanisms used for communication and collaboration, the organizational structure of projects, and testing and quality assurance procedures. The framework was developed and validated from interviews and surveys with leaders of more than 70 commercial and community-based software projects, including both closed and open source projects.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/framework\%20for\%20evaluating\%20Mangerial\%20Style.pdf},
	author = {Capra, Eugenio and Wasserman, Anthony}
}
@conference {555,
	title = {A Framework to Abstract The Design Practices of e-Learning System 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 = {317 - 323},
	publisher = {Springer},
	organization = {Springer},
	chapter = {28},
	abstract = {The use of ALT (Advanced Learning Technologies) creates dynamic sharing and exchanging between open source communities that diffuse e-learning systems. In our opinion, the designer practices define new perspectives on e-learning design which are not structured and highlighted enough. This article shows the capabilities of a generic framework to analyse the design practices on a open source project and to explicit these practices. We describe how the semantics for architectural specifications proposed by RM-ODP (Reference Model-Open Distributed Process) framework were applied on an e-learning system project to analyse the principles of invariants, structural and functional.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_28},
	attachments = {https://flosshub.org/sites/flosshub.org/files/A\%20Framework\%20to\%20Abstract\%20the\%20Design\%20Project.pdf},
	author = {Corbiere, Alain}
}
@article {GonzalezBarahona2008356,
	title = {Geographic origin of libre software developers},
	journal = {Information Economics and Policy},
	volume = {20},
	number = {4},
	year = {2008},
	note = {Empirical Issues in Open Source Software},
	pages = {356 - 363},
	abstract = {This paper examines the claim that libre (free, open source) software involves global development. The anecdotal evidence is that developers usually work in teams including individuals residing in many different geographical areas, time zones and even continents and that, as a whole, the libre software community is also diverse in terms of national origin. However, its exact composition is difficult to capture, since there are few records of the geographical location of developers. Past studies have been based on surveying a limited (and sometimes biased) sample and extrapolating that sample to the global distribution of developers. In this paper we present an alternate approach in which databases are analyzed to create traces of information from which the geographical origin of developers can be inferred. Applying this technique to the SourceForge users database and the mailing lists archives from several large projects, we have estimated the geographical origin of more than one million individuals who are closely related to the libre software development process. The paper concludes that the result is a good proxy for the actual distribution of libre software developers working on global projects.},
	keywords = {developers, email, email address, email archives, geography, mailing list, open source software, sourceforge, timezone, users},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.07.001},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4T3DCPK-1/2/3981dfbc523eae1d1ce65fb1f0c0edb7},
	author = {Jesus M. Gonzalez-Barahona and Gregorio Robles and Roberto Andradas-Izquierdo and Rishab Aiyer Ghosh}
}
@article {862,
	title = {Getting Clear About Communities in Open Innovation},
	journal = {Industry \& Innovation},
	volume = {15},
	year = {2008},
	month = {4/2008},
	pages = {223 - 231},
	author = {Joel West and Lakhani, Karim}
}
@proceedings {864,
	title = {Governance in Open Source Software Development Projects: Towards a Model for Network-Centric Edge Organizations},
	year = {2008},
	month = {07/2008},
	address = {Bellevue, WA},
	author = {Walt Scacchi and Chris Jensen}
}
@booklet {494,
	title = {Guest Editorial of the Special Issue on Socio-technical Dynamics in the Free/Libre Open Source Software (FLOSS) Social World},
	year = {2008},
	month = {Jan},
	abstract = {This special issue is the first volume in academia dedicated to a qualitative inquiry on dynamics in the FLOSS development and implementation, even if it is not alone in this endeavour (see e.g., Coleman, 2004; Kelty, 2005). Such a qualitative inquiry challenges the universally vocal and normative way of depicting FLOSS culture and practices (e.g., a homogeneous gift-giving and volunteering culture). The special issue encourages a practice-based and holistic view to exploring multiple cultures and practices in developing, localising, appropriating, and customising FLOSS. It also addresses the diversity in FLOSS communities through asking how seemingly global FLOSS cultures are translated into different contexts and locales. The importance of such an emphasis on how FLOSS technologies and practices diffract as they travel is nicely encapsulated by Haraway (1992) in her optic metaphor of white light that diffracts through a prism and becomes a rainbow. In light of this metaphor, a piece of FLOSS software is never really the same; when reproduced and shared, it is both the same (the standard) and something else in the mean time.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Guest_editorial_Lin\%26Risan.pdf},
	author = {Yu-wei Lin and Lars Risan}
}
@article {44,
	title = {Hacker practice: Moral genres and the cultural articulation of liberalism},
	journal = {Anthropological Theory},
	volume = {8},
	number = {3},
	year = {2008},
	pages = {255},
	author = {Coleman, E.G. and Golub, A.}
}
@booklet {481,
	title = {How Do Firms Make Use of Open Source Communities?},
	howpublished = {Long Range Planning},
	volume = {41},
	number = {6},
	year = {2008},
	note = {"To obtain more information about the firms{\textquoteright} relationships with their respective communities, we followed mailing lists and forums over a three-month period, checking them at least three times a week. "
"Firm data. Secondary sources, including annual reports, company directories, business and specialist press and homepages, were used to gather information on firms"},
	month = {Dec},
	pages = {629-649},
	abstract = {Relying on four in-depth case studies of firms involved with open source software, we investigate how firms make use of open source communities, and how that use is associated with their business models. Three themes - accessing, aligning and assimilating -are inductively developed for how the firms relate to the external knowledge created in the communities. For each theme, we make an argument about the tactics associated with each theme and their positive and negative consequences. The findings are related to the literature on the open and distributed nature of innovation, and various theoretical and managerial implications are discussed.},
	keywords = {case study, cendio, email, mailing list, mysql, roxen, secondary data, sot},
	url = {http://www.acm.jhu.edu/~paulproteus/tmp/sdarticle.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dahlandermagnusson2008.pdf},
	author = {Linus Dahlander and M Magnusson}
}
@article {breach2m,
	title = {I{\textquoteright}m not chatting, i{\textquoteright}m innovating! locating lead users in open source software communities},
	year = {2008},
	abstract = {The Lead User Method recognizes that certain end users of products are a valuable source {\textendash} in some industries the only source {\textendash} of new product innovations. Organizations that seek out these lead users and invite them to assist with the new product development process will produce products that perform far better in the marketplace than those developed by traditional methods based on research and development and market research. The individuals who author Open Source Software (OSS) {\textendash} complex and high-quality computer software that is typically distributed free of charge and without restrictions on use {\textendash} appear to share many common characteristics with lead users. These skilled computer programmers develop their software collaboratively, and often form large communities that congregate in Internet {\textquoteright}chat rooms{\textquoteright} to discuss and manage their software development projects. In response to a call for further research to improve the performance of the lead user method, this paper integrates concepts from the fields of innovation management, data visualization and open source software to a proposal to improve the process of identifying lead users in OSS communities},
	keywords = {irc},
	url = {http://www.geoffbreach.com/files/9512/6939/7089/Breach\%202008\%20Im\%20Not\%20Chatting\%20Im\%20Innovating.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Breach\%202008\%20Im\%20Not\%20Chatting\%20Im\%20Innovating.pdf},
	author = {Breach, Geoff}
}
@conference {Parnin:2008:ICD:1370750.1370765,
	title = {Improving change descriptions with change contexts},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {51{\textendash}60},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software archives are one of the best sources available to researchers for understanding the software development process. However, much detective work is still necessary in order to unravel the software development story. During this process, researchers must isolate changes and follow their trails over time. In support of this analysis, several research tools have provided different representations for connecting the many changes extracted from software archives. Most of these tools are based on textual analysis of source code and use line-based differencing between software versions. This approach limits the ability to process changes structurally resulting in less concise and comparable items. Adoption of structure-based approaches have been hampered by complex implementations and overly verbose change descriptions. We present a technique for expressing changes that is fine-grained but preserves some structural aspects. The structural information itself may not have changed, but instead provides a context for interpreting the change. This in turn, enables more relevant and concise descriptions in terms of software types and programming activities. We apply our technique to common challenges that researchers face, and then we discuss and compare our results with other techniques.},
	keywords = {bytecode analysis, cecil, change management, change pairs, semantic diff, zedgraph},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370765},
	url = {http://doi.acm.org/10.1145/1370750.1370765},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p51-parnin.pdf},
	author = {Parnin, Chris and G{\"o}rg, Carsten}
}
@conference {flosswp1737,
	title = {Improving community awareness in software forges by semantical aggregation of tools feeds},
	booktitle = {3nd International Workshop on Public Data about Software Development (WoPDaSD 2008), Milano, Italy, September 2008},
	year = {2008},
	abstract = {It is rather difficult to monitor or visualize what can be the contribution of a member in a project, especially when the project uses multiple tools to produce its results. This is the case for collaborative development of FLOSS software, that use Wiki, bug tracker, mailing lists and source code management tools. This paper presents an approach to data collection by using aggregation of feeds published by the different tools of a software forge. To allow this aggregation, collected data is semantically reformatted into Semantic Web standards: RDF, DC, DOAP, and FOAF. Resulting data can then be processed, republished or displayed to project members. We implemented this approach in a supervision module that has been integrated into the PicoForge platform. This module is able do draw a live graph of the social community out of the different sources of data, and in turn export semantic feeds for other uses.},
	keywords = {community of practice, DOAF., FOAF, free and open source software development, public data, RDF, semantic Web, social filtering, social network analysis},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Paper4.pdf},
	author = {Quang Vu Dang and Christian Bac and Olivier Berger and Xuan Sang Dao}
}
@unpublished {flosswp393,
	title = {The indirect debate and the community. How the periphery and the core relate in the Free/Open Source Software community},
	year = {2008},
	month = {June},
	abstract = {The present paper analyzes the relationship between the core and the periphery in the Free/Open Source innovation model. Considering the core as the "sparring partner" of the periphery, and not vice versa, the present discussion tries to apply a view opposite to the most diffused one. The first passages of the paper are meant to characterize the periphery, its functions, and the source of the realized division of labor with the core. It is shown that this specific schema is the consequence of the self-organizing nature of the FOSS model, that needs to dissipate resources to assure that the whole dynamics does not cease. However, this peculiar division of labor is possible only if the periphery and the core share the same set of interpretative schemes, norms and vision of the authoritative configuration of the community. To understand how this last passage is possible, I develop a conceptual model based on Wenger{\textquoteright}s concept of imagination and alignment, usually kept in the background by the literature on FOSS, and on the idea of dissonance (e.g. Kuran, 1998). Eventually, the paper tries discuss the relevant properties of the periphery (invisibility, atomization and instability) emerging from the analysis of the possible flaws of the process},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rullani_periphery.pdf},
	author = {Francesco Rullani}
}
@conference {Twidale2008,
	title = {Infrastructures From the Bottom-Up and the Top-Down: Can They Meet in the Middle?},
	booktitle = {Proceedings PDC 2008},
	year = {2008},
	pages = {238-241},
	abstract = {Based on a study of participatory design in the development of cyberinfrastructure involving the rapid composition of open source software and web services, we consider cases where researchers create their own ad hoc infrastructures out of available software. We compare "top- down" and "bottom-up" cyberinfrastructure development and speculate on whether the two approaches can be productively combined.},
	author = {Twidale, M.B and Floyd, I.R.}
}
@proceedings {813,
	title = {Infrastructures From the Bottom-Up and the Top-Down: Can They Meet in the Middle?},
	year = {2008},
	pages = {238-241.},
	abstract = {Based on a study of participatory design in the development of cyberinfrastructure involving the rapid composition of open source software and web services, we consider cases where researchers create their own ad hoc infrastructures out of available software. We compare "top- down" and "bottom-up" cyberinfrastructure development and speculate on whether the two approaches can be productively combined.},
	url = {http://hdl.handle.net/2142/9526},
	author = {Twidale, M.B and Floyd, I.R.}
}
@conference {Zhang:2008:ISG:1370750.1370785,
	title = {An initial study of the growth of eclipse defects},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {141{\textendash}144},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {We analyze the Eclipse defect data from June 2004 to November 2007, and find that the growth of the number of defects can be well modeled by polynomial functions. Furthermore, we can predict the number of future Eclipse defects based on the nature of defect growth.},
	keywords = {bug reports, defect growth model, defect prediction, eclipse, msr challenge, polynomial regression},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370785},
	url = {http://doi.acm.org/10.1145/1370750.1370785},
	author = {Zhang, Hongyu}
}
@article {1120,
	title = {The institutions of open source software: Examining the Debian community*},
	journal = {Information Economics and Policy},
	volume = {20},
	year = {2008},
	note = {"using primary data from its mailing lists archives, handbooks written to inform potential and actual community members, and previous analyses of institutional evolution and political conflict"

no discussion of which lists, how many, or when they were gathered...?[ms]},
	month = {12/2008},
	pages = {333 - 344},
	abstract = {Free and open source software activities involve and, perhaps, evolve institutions (rules, norms and standards) that influence the formation, growth, and demise of communities. Community institutions are attractors for some individuals while discouraging other individuals from entering or continuing to participate. Their suitability may change as a community grows. This paper examines the institutions of the Debian community where issues of community identity, distribution of authority, and decentralisation have facilitated growth and development. These same institutions have also resulted in conflicts regarding community purposes and the quality and delivery of the community{\textquoteright}s output. We examine the institutional redesign undertaken to address these problems and derive implications for F/LOS communities and companies.},
	keywords = {authority, COMMUNITY, conflict, debian, decentralization, growth, institutions, leadership},
	issn = {01676245},
	doi = {10.1016/j.infoecopol.2008.06.001},
	attachments = {https://flosshub.org/sites/flosshub.org/files/The_institutions_of_open_source_software-_IR.pdf},
	author = {Mateos Garcia, J. and Steinmueller, W.E.}
}
@booklet {509,
	title = {Intellectual Property Rights and Ex-Post Transaction Costs: the Case of Open and Closed Source Software},
	year = {2008},
	abstract = {The economic characteristics of software and transaction costs explain, why closed source and open source software co-exist. It is about the efficient use of a non- and anti-scarce resource. But because of ex-post transaction costs that lead to information asymmetries, some property rights regarding the resource ""source code"" are not exclusively separable. Thus, the first best allocation of property rights, that would yield an optimal usage of a source code, is not realizable. Or, that is to say, a first best realization of contracts is not feasible.

Hence, open and closed source software are two second best arrangements, both with specific assets and drawbacks. The principle of closed source benefits from direct (monetary) incentives and control, but has limits in its scope (size) because of transaction costs. Open source, on the one hand, benefits from its openness that creates spillovers and enables to incorporate human capital that is not acquirable for closed source firms. On the other hand, there are costs of openness, such as coordination costs (consensus finding, etc.) the danger of free riding or under provision, or forking.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wp_2008_047.pdf},
	author = {von Engelhardt, Sebastian}
}
@article {flosswp376,
	title = {Involving Software Engineering Students in Open Source Software Projects: Experiences from a Pilot Study},
	year = {2008},
	month = {June},
	abstract = {Anecdotal and research evidences show that the Free and Open Source Software (F/OSS) development model has produced a paradigm shift in the way we develop, support, and distribute software. This shift is not only redefining the software industry but also the way we teach and learn in our software engineering (SE) courses. But for many universities F/OSS is seen as an optional low cost technology to support the IT infrastructure and administrational duties. Few see F/OSS as an opportunity for students to learn the SE concepts and skills we teach. Furthermore, it is still an open question as to whether the F/OSS methodology can be effectively used to teach SE courses within the formally structured curriculum in most universities. This paper discusses F/OSS projects as bazaars of learning that offer a meaningful learning context. The discussion is centered on a pilot study in which students were involved in software testing in F/OSS projects. We present the teaching and learning framework we used in the pilot study and report on our experiences, lessons learned, and some practical problems we encountered. Our grading and evaluation approach show that the students did relatively well as bug hunters and reporters. Results from two online surveys indicate that students are motivated in participating in software testing in the bazaar, and they are willing to participate in project activities long after their graduation. The study reveals one possible way SE educators can teach and integrate F/OSS into their formal curricular structure.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bazaars_of_learning.pdf},
	author = {Sowe, Sulayman K. and Ioannis Stamelos}
}
@article {68,
	title = {JADE: A software framework for developing multi-agent applications. Lessons learned},
	journal = {Information and Software Technology},
	volume = {50},
	year = {2008},
	note = {Times Cited: 0},
	pages = {10-21},
	abstract = {Since a number of years agent technology is considered one of the most innovative technologies for the development of distributed software systems. While not yet a mainstream approach in software engineering at large, a lot of work on agent technology has been done, many research results and applications have been presented, and some software products exists which have moved from the research community to the industrial community. One of these is JADE, a software framework that facilitates development of interoperable intelligent multi-agent systems and that is distributed under an Open Source License. JADE is a very mature product, used by a heterogeneous community of users both in research activities and in industrial applications. This paper presents JADE and its technological components together with a discussion of the possible reasons for its success and lessons learned from the somewhat detached perspective possible nine years after its inception. (c) 2007 Elsevier B.V. All rights reserved.},
	author = {Bellifemine, F. and Caire, G. and Poggi, A. and Rimassa, G.}
}
@proceedings {72,
	title = {A large-scale study of MySpace: Observations and implications for online social networks},
	year = {2008},
	month = {March 30{\textendash}April 2},
	address = {Seattle, WA},
	author = {James Caverle and Steve Webb}
}
@conference {bird2008lss,
	title = {{Latent Social Structure in Open Source Projects}},
	booktitle = {SIGSOFT {\textquoteright}08/FSE-16: Proceedings of the 16th ACM SIGSOFT Symposium on Foundations of Software Engineering},
	year = {2008},
	note = {We first identified the projects of interest and mined the developer mailing list archives and source code repositories of each of the projects. Next, we filtered the mailing list messages and created a social network of the participants over 3-month intervals. We then calculated the community structure of each social network. Following that, the relevance of the divisions of participants was evaluated quantitatively using mined source code development data and qualitatively by manual methods.},
	pages = {24{\textendash}35},
	publisher = {ACM},
	organization = {ACM},
	abstract = {Commercial software project managers design project organizational structure carefully, mindful of available skills, division of labour, geographical boundaries, etc. These organizational {\textquotedblleft}cathedrals{\textquotedblright} are to be contrasted with the "bazaar-like" nature of Open Source Software (OSS) Projects, which have no pre-designed organizational structure. Any structure that exists is dynamic, self-organizing, latent, and usually not explicitly stated. Still, in large, complex, successful, OSS projects, we do expect that subcommunities will form spontaneously within the developer teams. Studying these subcommunities, and their behavior can shed light on how successful OSS projects self-organize. This phenomenon could well hold important lessons for how commercial software teams might be organized. Building on known well-established techniques for detecting community structure in complex networks, we extract and study latent subcommunities from the email social network of several projects: Apache HTTPD, Python, PostgresSQL, Perl, and Apache ANT. We then validate them with software development activity history. Our results show that subcommunities do indeed spontaneously arise within these projects as the projects evolve. These subcommunities manifest most strongly in technical discussions, and are significantly connected with collaboration behaviour.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2008lss.pdf},
	author = {Christian Bird and David Pattison and Raissa D{\textquoteright}Souza and Filkov, Vladimir and Devanbu, Premkumar}
}
@mastersthesis {484,
	title = {Licensing Freedom; An Ethical Analysis of Free and Open Source Software Licenses},
	year = {2008},
	month = {January},
	abstract = {Free and open source software enables users to use, read and modify the source code of computer programs. In proprietary software, access to the source code is not given and users are generally not permitted to use, read and modify the source code. Opponents of a proprietary system state that proprietary software is morally wrong and in this thesis, the arguments they use are evaluated.Several licensing schemes can be used as an addition to copyright law to give users the rights described above. The most important division between these different licenses can be made on the basis of the use of the copyleft principle. This principle obliges the licensee to distribute modified versions of the software under the same, or similar terms as the original license. In this thesis, this obligation is seen as a restriction on the freedom of the individual. Comparisons and possible justifications will give better insight in this supposed contradiction.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Thesis_SaskiavandeNieuwenhof.pdf},
	author = {Saskia van de Nieuwenhof}
}
@conference {535,
	title = {Lost and Gained in Translation: Adoption of Open Source Software Development at Hewlett-Packard},
	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 = {93 - 104},
	publisher = {Springer},
	organization = {Springer},
	chapter = {8},
	abstract = {What happens when an organization form that has emerged in one context is brought into a different context? In this paper, a longitudinal field study approach is used to explore how Hewlett-Packard (HP) molded open source software development (OSSD) into a proprietary software development approach called {\textquotedblleft}Progressive Open Source{\textquotedblright} (POS). With the help of actornetwork theory, we understand this as a process of translation and find that some central characteristics of OSSD where lost in the translation into POS while other characteristics were gained.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_8},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Lost\%20\%26\%20Gained\%20in\%20Translation.pdf},
	author = {Melian, Catharina and M{\"a}hring, Magnus}
}
@mastersthesis {485,
	title = {Managing Firm-Sponsored Open Source Communities},
	year = {2008},
	month = {May},
	abstract = {The interest and use of open source software and methodology has gained an increasing amount of commercial attention, and we are currently witnessing that established proprietary software firms are taking a step further by opening their own software projects in an attempt to create firm-sponsored open source communities. Siobhan O{\textquoteright}Mahony{\textquoteright}s research finds that these firms have to handle a tension between openness and control in their product development, but little research has been done to detail how this balance is achieved. I have studied the American software company Novell and the openSUSE project, largely guided by an inductive, qualitative approach supplemented by some quantitative methods. In the study I draw upon Niklas Luhmann{\textquoteright}s theory of autopoietic social systems to create a distinction between the sponsor firm and the sponsored community, and I investigate the mechanisms that hold the two systems together despite their differences in interests. I argue that there are several elements that ensure a tight coupling between the two systems, including the boundary objects situated between them, the shared communication channels and the efforts of the marginal people whom have roles in both systems. A primary contribution to the theory of boundary objects is a distinction between what I describe as supportive-objects and target-objects. I argue that the latter holds a strong motivating power that should be appended to our understanding of individuals{\textquoteright} and collectives{\textquoteright} motivation to participate in open source software projects. I explore several possible future scenarios for the evolution of firm-sponsored communities, and find that Novell is pursuing a strategy for managing openness in such a community.},
	author = {Jan Fredrik Stoveland}
}
@conference {530,
	title = {Mapping Linux Security Targets to Existing Test Suites},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {29 - 45},
	publisher = {Springer},
	organization = {Springer},
	chapter = {3},
	abstract = {The Common Criteria standard provides an infrastructure for evaluating security functions of IT products and for certifying that security policies claimed by product suppliers are correctly enforced by the security functions themselves. Certifying Open Source software (OSS) can pave the way to OSS adoption in a number of security-conscious application environments. Recent experiences in certifying Linux distributions has pointed out the problem of finding a mapping between descriptions of OSS security functions and existingtest suites developed independently, such as the Linux Test Project. In this paper, we describe a mechanism, based on matching techniques, which semiautomatically associates security functions to existing test suite such as the ones developed by Open Source communities.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Mapping\%20Linux\%20Security\%20Targets.pdf},
	author = {Ardagna, C. and Damiani, E. and Ioini, N. and Frati, F. and Giovannini, P. and Tchokpon, R.}
}
@article {499,
	title = {The Material and Social Dynamics of Motivation: Contributions to Open Source Language Technology Development},
	journal = {Science Studies},
	number = {2},
	year = {2008},
	note = {"I conducted a two-phased qualitative analysis on multiple data (thematic phone-inter- views, notes from OpenOffice.org conference 2004 meetings, historical documents, mailing list discussions, homepages, Google, blogs, real-time video and audio presentations from OpenOffice.org conference 2005)."},
	abstract = {Volunteer motivation has been a central theme in Free/Libre/Open Source Software (FLOSS) literature. This research has been largely dominated by economists who rely in their surveys on the distinction between intrinsic and extrinsic motivations and the "hacker ethic" for profit juxtaposition. The paper argues that survey-based analytical frameworks and research designs have led to a focus on some motivational attributions at the expense of others. It then presents a case study that explores dynamic, non individualistic and content-sensitive aspects of motivations. The approach is based on socio-cultural psychology and the author{\textquoteright}s observations of a hybrid firm-community FLOSS project, OpenOffice.org. Instead of separating intrinsic motivations from extrinsic ones, it is argued that complex and changing patterns of motivations are tied to changing objects and personal histories prior to and during participation. The boundary between work and hobby in an individual{\textquoteright}s participation path is blurred and shifting.},
	keywords = {contributions, developers, email, email archives, mailing list, MOTIVATION, openoffice, openoffice.org, secondary data, Volunteers},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Freeman.pdf},
	author = {Stephanie Freeman}
}
@conference {545,
	title = {Migration Discourse Structures: Escaping Microsoft{\textquoteright}s Desktop Path},
	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 = {223 - 235},
	publisher = {Springer},
	organization = {Springer},
	chapter = {18},
	abstract = {Most studies of FOSS organizational migration projects focus solely on technological and economical aspects, neglecting the importance of organizational discourse structures for migration decisions as well as success. In looking at the case of the municipality of Munich this paper uses structuration theory in combination with discourse analysis to explain why and how in this case actors were able to overcome strong barriers to migration in the field of desktop software.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Migration\%20Discourse\%20Structure.pdf},
	author = {Dobusch, Leonhard}
}
@conference {536,
	title = {Mining for Practices in Community Collections: Finds From Simple Wikipedia},
	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 = {105 - 120},
	publisher = {Springer},
	organization = {Springer},
	chapter = {9},
	abstract = {The challenges of commons based peer production are usually associated with the development of complex software projects such as Linux and Apache. But the case of open content production should not be treated as a trivial one. For instance, while the task of maintaining a collection of encyclopedic articles might seem negligible compared to the one of keeping together a software system with its many modules and interdependencies, it still poses quite demanding problems. In this paper, we describe the methods and practices adopted by Simple Wikipedia to keep its articles easy to read. Based on measurements of article readability and similarity, we conclude that while the mechanisms adopted by the community had some effect, in the long run more efforts and new practices might be necessary in order to maintain an acceptable level of readability in the Simple Wikipedia collection.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Mining\%20for\%20Practices.pdf},
	author = {den Besten, Matthijs and Rossi, Alessandro and Gaio, Loris and Loubser, Max and Jean-Michel Dalle}
}
@conference {Schuler:2008:MUE:1370750.1370779,
	title = {Mining usage expertise from version archives},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {121{\textendash}124},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In software development, there is an increasing need to find and connect developers with relevant expertise. Existing expertise recommendation systems are mostly based on variations of the Line 10 Rule: developers who changed a file most often have the most implementation expertise. In this paper, we introduce the concept of usage expertise, which manifests itself whenever developers are using functionality, e.g., by calling API methods. We present preliminary results for the ECLIPSE project that demonstrate that our technique allows to recommend experts for files with no or little history, identify developers with similar expertise, and measure the usage of API methods.},
	keywords = {api, computer-supported cooperative work, eclipse, expertise, recommendation, scm, software repository, source code},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370779},
	url = {http://doi.acm.org/10.1145/1370750.1370779},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p121-schuler.pdf},
	author = {Schuler, David and Zimmermann, Thomas}
}
@article {867,
	title = {Mobilization of Software Developers: The Free Software Movement},
	journal = {(revised version in) Information, Technology and People},
	volume = {20},
	year = {2008},
	pages = {4-33},
	author = {Elliott, M. and Walt Scacchi}
}
@conference {flosswp402,
	title = {The motivational arc of massive virtual collaboration},
	booktitle = {IFIP WG 9.5, International Working Conference on Virtuality and Society: Massive Virtual Communities},
	year = {2008},
	month = {February},
	pages = {1{\textendash}13},
	abstract = {Massive virtual collaborations (MVC) involve large numbers of mostly unpaid contributors collectively creating new content. Wikipedia is the most dramatic example of MVC; smaller-scale examples include contributors to blogs and discussion groups and teams of programmers and users developing free/libre open source software (FLOSS). In this paper, we propose a model of motivations for contribution to MVC that integrates various theoretical perspectives. The model extends prior work by distinguishing three different levels of contribution to projects (initial, sustained and meta) and by capturing the dynamic and recursive effects of contributions on emergent individual and project states.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowston_fagnot_ifip.pdf},
	author = {Kevin Crowston and Isabelle Fagnot}
}
@inbook {868,
	title = {Movement Ideology vs. User Pragmatism in the Organizational Adoption of Open Source Software},
	booktitle = {Computerization Movements and Technology Diffusion: From Mainframes to Ubiquitous Computing},
	year = {2008},
	pages = {427-452},
	publisher = {Information Today},
	organization = {Information Today},
	address = {Medford, NJ},
	author = {Dedrick, Jason and Joel West},
	editor = {Kraemer, Kenneth L. and Elliott, Margaret}
}
@conference {553,
	title = {The Networked Forge: New Environments for Libre 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 = {299 - 306},
	publisher = {Springer},
	organization = {Springer},
	chapter = {26},
	abstract = {Libre (free, open source) software forges (sites hosting the development infrastructure for a collection of projects) have been stable in architecture, services and concept since they become popular during the late 1990s. During this time several problems that cannot be solved without dramatic design changes have become evident. To overcome them, we propose a new concept, the {\textquotedblleft}networked forge{\textquotedblright}, focused on addressing the core characteristics of libre software development and the needs of developers. The key of this proposal is to re-engineer forges as a net of distributed components which can be composed and configured according to the needs of users, using a combination of web 2.0, semantic web and mashup technologies. This approach is flexible enough to accommodate different development processes, while at the same time interoperates with current facilities.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_26},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Networked\%20Forge.pdf},
	author = {Gonzalez-Barahona, Jesus and Mart{\'\i}nez, Andr{\'e}s and Polo, Alvaro and Hierro, Juan and Reyes, Marcos and Soriano, Javier and Fern{\'a}ndez, Rafael}
}
@conference {Holmes:2008:NGE:1370750.1370787,
	title = {A newbie{\textquoteright}s guide to eclipse APIs},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {149{\textendash}152},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Eclipse has evolved from a fledgling Java IDE into a mature software ecosystem. One of the greatest benefits Eclipse provides developers is flexibility; however, this is not without cost. New Eclipse developers often find the framework to be large and confusing. Determining which parts of the framework they should be using can be a difficult task as Eclipse documentation tends to be either very high-level, focusing on the design of the framework, or low-level, focusing on specific APIs. We have developed a tool called PopCon that provides a bridge between high-level design documentation and low-level API documentation by statically analyzing a framework and several of its clients and providing a ranked list of the relative popularity of its APIs. We have applied PopCon to the Eclipse framework for this challenge to help newbie Eclipse developers identify some of the most relevant APIs for their tasks.},
	keywords = {API popularity, documentation, eclipse, mining software repositories, module, msr challenge, PopCon, popularity},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370787},
	url = {http://doi.acm.org/10.1145/1370750.1370787},
	author = {Holmes, Reid and Walker, Robert J.}
}
@booklet {526,
	title = {The Open and Closed Styles of Talent Acquisition and Management:  Which takes an edge where},
	year = {2008},
	abstract = {The phenomenal success of Free/Open Source Software during the recent years has led researchers in all related fields to re-think and re-evaluate the studies and concepts, especially those which the open source violates. Talent management and talent acquisition is no exception to this. The sudden rise in open source projects and their success is a cause of motivation for all of us to evaluate their philosophy and implement the same. Proper talent management and acquisition of talent can play a key role in strengthening the industry. Traditional closed management with their classic way of functioning may still look at the open source model as a big mystery. Open source has violated many of the theories of Software Engineering like limited team size, decentralized project management, etc. The concepts of self-motivated individuals, adaptive division of labor, informal or indirect leadership, etc. are the contributions of the open source to the world.

In this paper we discuss these concepts and state their differences with the way of working of closed talent management. Even though open source has various benefits in working, but requirement of a good coordination process, redundancy of development, versioning problems, etc. pose a limitation. We present an analogy of the talent management in the two concepts with that of the natural ecosystem. Talent in open source works in a manner similar to the ant colonies. Here the process is more community oriented and there is no single dictator power. The proprietary, on the other hand, works on talent as the lions ruling the den. There is a hierarchy and that needs to be respected. Only the leader has the right to make final decision, and that is binding. We also take a look into the present conditions of meltdown and show how the open source way is better suited for this scenario. Even though the present firms may be seeing a setback at this time of recession, the impact on firms with an open source way of working is much lighter or none at all. We also discuss the interactions between the two styles of talent management and present a model that can be adopted by the proprietary companies to benefit from open model. Our arguments of the paper not only deal with software, but also on content that comes under the domain of Creative Commons. We have taken the examples of Wikipedia, Sourceforge.net, Linux etc. for the various issues we discuss.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper.pdf},
	author = {Rahul Kala}
}
@conference {547,
	title = {An Open Integrated Environment for Transparent Fuzzy Agents Design},
	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 = {249 - 255},
	publisher = {Springer},
	organization = {Springer},
	chapter = {20},
	abstract = {Recently, computational agents received significant attention in computer science research community. In fact, intelligent agents is a powerful artificial intelligence technology showing considerable promise as a new paradigm for mainstream software development and able to offer new ways of abstraction, decomposition, and organization that fit well with our natural view of the world. However, despite their promise, intelligent agents are still scarce in the market place. A key reason for this is that developing intelligent agent software requires significant training and skill. Artificial Intelligence methodologies and computer networking tools represent the necessary basic knowledge to design and implement advanced agents oriented systems. This papers introduces an integrated development environment supporting the agents developers to design fuzzy-based agents in a simple and fast way. Proposed framework has been realized by integration of theoretical methodologies as fuzzy logic and labeled tree, together with OSS tools as JaxMe2.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/An\%20Open\%20Integrated\%20Environment.pdf},
	author = {Acampora, Giovanni and Loia, Vincenzo}
}
@conference {568,
	title = {Open Source Environments for Collaborative Experiments in e-Science},
	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 = {415 - 416},
	publisher = {Springer},
	organization = {Springer},
	chapter = {41},
	abstract = {Open Source Software (OSS) for e-Science should make reference to the paradigm of a distributed surrounding over a multi system mix of Web Services and Grid technologies, allowing data exchanging through services, according to standards in the area of the Grid and of Service Oriented Computing (SOC). In fact, biologists, medical doctors, and scientists are often involved in time consuming experiments and are aware of the degree of difficulty in validating or rejecting a given hypothesis by lab experiments. The benefits of OSS for e-Science consider that as many operating nodes as possible can work cooperatively sharing data, resources, and software, thus avoiding the bottleneck of licenses for distributed use of tools needed to perform cooperative scientific experiments. In particular, this chapter presents an architecture based on nodes equipped with a Grid and with Web Services in order to access OSS, showing how scientific experiments can be enacted through the use of a cooperation among OSS sites. Such a choice, besides reducing the cost of the experiments, would support distributed introduction of OSS among other actors of the dynamical networks, thus supporting the awareness about OSS and their diffusion. An OSS environment for cooperative scientific experiments (e-experiments) can effectively support the distributed execution of different classes of experiments, from visualization to model identification through clustering and rules generation, in various application fields, such as bioinformatics, neuro-informatics, tele-monitoring,or drug discovery. By applying Web Services and Grid computing, an experiment or a simulation can be executed in a cooperative way on various computation nodes of a network equipped with OSS, allowing data exchange among researchers. Our environment  formalizes experiments as cooperative services on various computational nodes of a grid network. Basic elements are models, languages, and support tools creating a virtual
network of organizational responsibility of the global experiments, according to rules under which each node can execute local services to be accessed by other nodes in order to achieve the whole experiment{\textquoteright}s results.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_41},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Environments.pdf},
	author = {Bosin, Andrea and Dess{\'\i}, Nicoletta and Fugini, Maria and Liberati, Diego and Pes, Barbara}
}
@conference {562,
	title = {Open Source Project Categorization Based on Growth Rate Analysis and Portfolio Planning Methods},
	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 = {375 - 380},
	publisher = {Springer},
	organization = {Springer},
	chapter = {35},
	abstract = {In this paper, we propose to arrive at an assessment and evaluation of open source projects based on an analysis of their growth rates in several aspects. These include code base, developer number, bug reports and downloads. Based on this analysis and assessment, a well-known portfolio planning method, the BCG matrix, is employed for arriving at a very broad classification of open source projects. While this approach naturally results in a loss of detailed information, a top-level categorization is in some domains necessary and of interest.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_35},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Project\%20Categorization.pdf},
	author = {Koch, Stefan and Stix, Volker}
}
@conference {565,
	title = {Open Source Reference Systems for Biometric Verification of Identity},
	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 = {397 - 404},
	publisher = {Springer},
	organization = {Springer},
	chapter = {38},
	abstract = {This paper focuses on the common evaluation framework which was developed by the BioSecure Network of Excellence during the European FP6 project BioSecure (Biometrics for Secure authentication). This framework, which is composed of open-source reference systems, publicly available databases, assessment protocols and benchmarking results, introduces a new experimental methodology for conducting, reporting and comparing experiments for biometric systems, participating to standardisation efforts. Its use will permit to make a link between different published works. It provides also the necessary tools to assure the reproducibility of the benchmarking biometric experiments. This framework can be considered as a re-liable and innovative process to evaluate the progress of research in the field of bio-metrics.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_38},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Reference\%20Systems.pdf},
	author = {Mayoue, Aur{\'e}lien and Petrovska-Delacr{\'e}taz, Dijana}
}
@article {flosswp8,
	title = {Open Source Software: Free Provision of a Complex Public Good},
	year = {2008},
	month = {April},
	abstract = {Open source software, developed by volunteers, appears counter to conventional wisdom about private provision of public goods. Standard arguments suggest that proprietary provision should be more efficient. But complex open source products challenge commercially-developed software in quality and market share. I argue that the complexity of software changes the results. With complex software, standard products cannot address all consumer needs and proprietary custom solutions are not always offered. Open source allows consumers to create their own customizations. When such user-customizations are then shared, open source products grow in quality and features. Open source extends the market for complex products.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lakhanivonhippelusersupport.pdf},
	author = {Jim Bessen}
}
@article {flosswp1,
	title = {Open Source Software: Free Provision of a Complex Public Good},
	year = {2008},
	month = {April},
	abstract = {Open source software, developed by volunteers, appears counter to conventional wisdom about private provision of public goods. Standard arguments suggest that proprietary provision should be more efficient. But complex open source products challenge commercially-developed software in quality and market share. I argue that the complexity of software changes the results. With complex software, standard products cannot address all consumer needs and proprietary custom solutions are not always offered. Open source allows consumers to create their own customizations. When such user-customizations are then shared, open source products grow in quality and features. Open source extends the market for complex products.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/opensrc.pdf},
	author = {Jim Bessen}
}
@conference {Rigby:2008:OSS:1368088.1368162,
	title = {Open source software peer review practices: a case study of the apache server},
	booktitle = {Proceedings of the 30th International Conference on Software Engineering (ICSE 2008)},
	series = {ICSE {\textquoteright}08},
	year = {2008},
	note = {http://faculty.salisbury.edu/~xswang/Research/Papers/SERelated/testing/p541-rigby.pdf},
	pages = {541{\textendash}550},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Peer review is seen as an important quality assurance mechanism in both industrial development and the open source software (OSS) community. The techniques for performing inspections have been well studied in industry; in OSS development, peer reviews are less well understood. We examine the two peer review techniques used by the successful, mature Apache server project: review-then-commit and commit-then-review. Using archival records of email discussion and version control repositories, we construct a series of metrics that produces measures similar to those used in traditional inspection experiments. Specifically, we measure the frequency of review, the level of participation in reviews, the size of the artifact under review, the calendar time to perform a review, and the number of reviews that find defects. We provide a comparison of the two Apache review techniques as well as a comparison of Apache review to inspection in an industrial project. We conclude that Apache reviews can be described as (1) early, frequent reviews (2) of small, independent, complete contributions (3) conducted asynchronously by a potentially large, but actually small, group of self-selected experts (4) leading to an efficient and effective peer review technique.},
	keywords = {apache, cvs, email, inspection, mining software repositories (email), open source software, peer review, version control},
	isbn = {978-1-60558-079-1},
	doi = {10.1145/1368088.1368162},
	url = {http://doi.acm.org/10.1145/1368088.1368162},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p541-rigby.pdf},
	author = {Peter C. Rigby and Daniel M. German and Storey, Margaret-Anne}
}
@booklet {525,
	title = {Open Source: The Next Big Thing In Technology Transfer to Developing Nations},
	year = {2008},
	month = {March},
	abstract = {Free Open Source (FOS) should be one of the least expensive and most effective solutions for technology and knowledge transfer to developing nations. This concept has diffused to several fields such as software, hardware, and content. FOS offers not only a low cost alternative for technology acquisition, but also for networking based on cooperation. In addition, the transaction costs of communication, licensing and negotiations are minimized, freeing up funds for real development. In this paper, FOS incentives, indicators, and measures are explained and the advantages of FOS as a viable technology and knowledge transfer tool for developing countries are highlighted.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1569088836.pdf},
	author = {Jamil Alkhatib and Mohab Anis and Hamid Noori}
}
@conference {537,
	title = {Open to Grok. How do Hackers{\textquoteright} Practices Produce Hackers?},
	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 = {121 - 129},
	publisher = {Springer},
	organization = {Springer},
	chapter = {10},
	abstract = {How do hackers{\textquoteright} practices produce hackers{\textquoteright} identities? In this paper we argue that the association between science fiction and software programs is rooted in hackers{\textquoteright} practices, defining how hackers{\textquoteright} knowledge{\textquoteright} emerge. The mediation is the one of the Heinlein verb {\textquotedblleft}to grok{\textquotedblright}, part of the Jargon file and of the name of a code browser, OpenGrok, the technology mediating the relationship between OpenSolaris developers and the code base. Starting with a description of the peculiarity of the verb {\textquotedblleft}to grok{\textquotedblright}, and its connection with a non-Cartesian view of knowledge, we discuss how the history of OpenGrok and its use by developers make this knowledge part of hackers{\textquoteright} practices and identities, as someone involved in a true, deep understanding of software.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_10},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20to\%20Grok.pdf},
	author = {D{\textquoteright}Andrea, Vincenzo and De Paoli, Stefano and Teli, Maurizio}
}
@conference {531,
	title = {Overview on Trust in Large FLOSS Communities},
	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 = {47 - 56},
	publisher = {Springer},
	organization = {Springer},
	chapter = {4},
	abstract = {The paper presents a survey of mature Free/Libre Open Source Software communities. The main focus of the survey is the collection of data related to the practices of these communities related to trust elements in their products. The survey is carried out using a structured questionnaire about thoughts and practices followed by Free/Libre Open Source Software communities. The survey focuses on the analysis of the development processes adopted by such communities. The results of the survey confirms basic ideas related to Free/Libre Open Source Software and explains in more detail specific issues related to trust and trustworthiness of the Free/Libre Open Source Software development process.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Overview\%20on\%20Trust.pdf},
	author = {Petrinja, Etiel and Sillitti, Alberto and Succi, Giancarlo}
}
@conference {567,
	title = {Panel: Opportunities and Risks for Open Source Software in Industry},
	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 = {413 - 414},
	publisher = {Springer},
	organization = {Springer},
	chapter = {40},
	abstract = {Open Source Software (OSS) is a multi-faceted phenomenon which has become an issue of strategic importance for many commercial organisations. Stemming from an ideological issue, with emphasis on freedom and community values, we have recently seen a broader interest in the Open Source phenomenon amongst practitioners in many companies. A number of SMEs and large companies are currently exploring the potential of Open Source, and for some it has become core to their business and development activities.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_40},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Panel\%20Opportunities\%20\%26\%20Risks.pdf},
	author = {Feller, Joseph and Lundell, Bj{\"o}rn and Marttiin, Pentti and Walt Scacchi and Schellingerhout, Nico}
}
@article {501,
	title = {PhD Candidate Paper},
	journal = {Science Studies},
	number = {2},
	year = {2008},
	month = {Feb},
	abstract = {National legislation to mandate the use or consideration of Free/Libre and Open Source Software (FLOSS) in government institutions is increasingly emerging as a strategy for FLOSS advocates in Latin America and the broader developing world. Such movements for the political use and regulation of FLOSS mark a distinct turn in the objectives and work of FLOSS advocates, whose activities largely focused on the dissemination of FLOSS as a technological artifact. This paper investigates the network of diverse actors involved in promoting FLOSS legislation in Peru, one of the first nations where a movement for FLOSS legislation emerged. It emphasizes that crucial to the work of FLOSS{\textquoteright} network actors is not their merely technological productivity, but their cultural and political productivity - that is, their ability to produce diverse body of meaning made both evident and mobile in narratives of FLOSS use and adoption.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Chan_ScienceStudies.pdf},
	author = {Anita Say Chan}
}
@conference {532,
	title = {PMLite: An Open Source Solution for Process Monitoring},
	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 = {57 - 68},
	publisher = {Springer},
	organization = {Springer},
	chapter = {5},
	abstract = {Process Monitoring represents a big challenge for organizations that aim to manage software projects adopting different development paradigms. In fact, across-process enterprise-level measurement campaigns can be difficult to enact since process attributes to retrieve are semantically diverse and may be difficult to integrate. In this paper, we present PMLite (Process Monitoring Lite) an open source solution to this problem. PMLite is based on an open metamodel and paves the way to the definition of ad-hoc open monitoring frameworks.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/PMLite.pdf},
	author = {Colombo, Alberto and Damiani, Ernesto and Frati, Fulvio}
}
@conference {Krogstie:2008:PTB:1368088.1368201,
	title = {Power through brokering: open source community participation in software engineering student projects},
	booktitle = {Proceedings of the 30th international conference on Software engineering},
	series = {ICSE {\textquoteright}08},
	year = {2008},
	pages = {791{\textendash}800},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Many software engineering projects use open source software tools or components. The project team{\textquoteright}s active participation in the open source community may be necessary for the team to use the technology. Based on an in-depth field study of industry software engineering project students interacting with an open source community, we find that participation in the community may affect the team{\textquoteright}s work and learning by strengthening the power of the broker between the team and the community. We outline pitfalls and benefits of having student teams acquire development-related knowledge from open source communities. The findings are relevant to the organization and supervision of software engineering student projects interacting with open source communities.},
	keywords = {Communities Of Practice, computer science education, FLOSS, open source, software engineering, software engineering education},
	isbn = {978-1-60558-079-1},
	doi = {10.1145/1368088.1368201},
	url = {http://doi.acm.org/10.1145/1368088.1368201},
	author = {Krogstie, Birgit R.}
}
@booklet {520,
	title = {Preparing the Ne(x)t Generation: Lessons learnt from Free/Libre Open Source Software and their Communities},
	year = {2008},
	month = {Sept},
	abstract = {In this article, the authors Andreas Meiszner, R{\~A}{\textonequarter}diger Glott and Sulayaman K. Sowe, examine the lessons that can be learnt from the Free / Libre Open and Source Software (FLOSS) communities. FLOSS communities, as good practice examples of Open Participatory Learning Ecosystems, illustrate possible pathways for higher education to go beyond the limits of the current Open Educational Resource move.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/GUNI_paper_proceedings_Meiszner_Glott_Sowe.pdf},
	author = {Andreas Meiszner and R{\"u}dige Glott and Sowe, Sulayman K.}
}
@unpublished {flosswp387,
	title = {Promoting the Penguin: Who is Advocating Open Source Software in Commercial Settings?},
	year = {2008},
	month = {March},
	abstract = {Most firms that use or develop software today face the questions of whether and how to engage in open source software (OSS). Yet, little is known about the process of OSS adoption and diffusion within corporations. Guided by the models of Rogers (innovation diffusion) and Davis (Technology Acceptance Model), we develop a theoretical framework of how job function influences individuals? proclivity to support their employers? adoption of OSS and OSS practices. We argue that job function determines an individual?s tasks, and that different tasks are differentially affected by OSS. Our study is based on interviews and a large-scale survey in a multinational corporation. Distinguishing between developers, testers, software architects, project managers, and managers, we find greater engagement in OSS to be favored most strongly by testers. Excepting project managers, developers, despite having the most experience with OSS, are the least favorably disposed to greater corporate OSS engagement. A corporation interested in adopting OSS should thus take into account the job function-related incentives of each individual. More generally, we propose that models predicting IT adoption behavior be extended to account for the ways in which individual adopters interact with the innovation at hand, which will be determined largely by their job functions.},
	author = {Oliver Alexy and Joachim Henkel}
}
@conference {559,
	title = {Reflection on Knowledge Sharing in F/OSS 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 = {351 - 358},
	publisher = {Springer},
	organization = {Springer},
	chapter = {32},
	abstract = {Knowledge sharing between software project participants simplifies a range of decision-making processes and helps improve the way software is being developed, distributed, and supported. However, research in this area has traditionally been very difficult because the source of knowledge, the code, has been a guarded secret and software developers and users inhabit different worlds. F/OSS projects have changed the way we perceive and understand knowledge sharing in distributed software development. This short paper presents our current understanding, and what needs to be done in terms of empirical research in knowledge sharing in F/OSS projects.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_32},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Reflection\%20on\%20Knowledge\%20Sharing.pdf},
	author = {Sowe, Sulayman and Ioannis Stamelos}
}
@conference {973,
	title = {On the relation of refactorings and software defect prediction},
	booktitle = {Proceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {35-38},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {This paper analyzes the influence of evolution activities such as refactoring on software defects. In a case study of five open source projects we used attributes of software evolution to predict defects in time periods of six months. We use versioning and issue tracking systems to extract 110 data mining features, which are separated into refactoring and non-refactoring related features. These features are used as input into classification algorithms that create prediction models for software defects. We found out that refactoring related features as well as non-refactoring related features lead to high quality prediction models. Additionally, we discovered that refactorings and defects have an inverse correlation: The number of software defects decreases, if the number of refactorings increased in the preceding time period. As a result, refactoring should be a significant part of both bug fixes and other evolutionary changes to reduce software defects.},
	keywords = {argouml, bug fixing, bug reports, defects, evolution, jboss, liferay, prediction, refactoring, spring, weka, xdoclet},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370759},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p35-ratzinger.pdf},
	author = {Sigmund, Thomas and Gall, Harald C. and Ratzinger, Jacek}
}
@article {1814,
	title = {Relationship between size, effort, duration and number of contributors in large FLOSS projects},
	journal = { 7th BElgian-NEtherlands software eVOLution workshop - BENEVOL 2008},
	year = {2008},
	abstract = {This contribution presents initial results in the study of the relationship between size,
effort, duration and number of contributors in eleven evolving Free/Libre Open Source
Software (FLOSS) projects, in the range from approx. 650,000 to 5,300,000 lines of
code. Our initial motivation was to estimate how much effort is involved in achieving
a large FLOSS system. Software cost estimation for proprietary projects has been an
active area of study for many years (e.g. [1][2][3]). However, to our knowledge, no previous
similar research has been conducted in FLOSS effort estimation. This research
can help planning the evolution of future FLOSS projects and in comparing them with
proprietary systems. Companies that are actively developing FLOSS may benefit from
such estimates [4]. Such estimates may also help to identify the productivity {\textquoteright}baseline{\textquoteright}
for evaluating improvements in process, methods and tools for FLOSS evolution},
	url = {http://oro.open.ac.uk/27317/1/},
	author = {Ramil, J.F. and Izquierdo-Cort{\'a}zar, Daniel and Mens, Tom}
}
@conference {flosswp392,
	title = {Replication of FLOSS Research as eResearch},
	booktitle = {Oxford e-Research Conference 2008},
	year = {2008},
	month = {May},
	abstract = {We are working to introduce the ideas of eResearch to a multi-disciplinary research domain: those researchers examining Free/Libre and Open Source Software (FLOSS) and its development (Howison, Wiggins, \& Crowston, 2008).The first phase of this work focused on building a repository for data on FLOSS teams, FLOSSmole (Howison, Conklin, \& Crowston, 2006), and collaborating with other nascent data repositories in the field. Recently we have begun a second phase, which is to introduce another established principle of eResearch, that of broader collaboration through shared workflows accessing these data repositories. To provide an example of the potential value of this principle, we are replicating seminal FLOSS papers using eResearch approaches. This paper describes research outcomes and lessons learned from translating published literature into eResearch workflows.},
	keywords = {eResearch eScience},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Wiggins-FLOSS-eResearch.pdf},
	author = {Andrea Wiggins and James Howison and Kevin Crowston}
}
@article {502,
	title = {Report on the effectiveness of a FLOSS-like learning community in formal educational settings},
	year = {2008},
	abstract = {This report examines some of the pedagogic principles embodied in Free / Libre Open Source Software (FLOSS) communities and briefly looks at case studies of FLOSS-like approaches in education. It analyzes and evaluates the differences between Free / Libre Open Source Software (FLOSS) communities as informal learning environments and on the other side formal educational settings. The report also point out ways on transferring those FLOSS principles to formal educational settings and looks at existing examples of eLearning delivery and examines why these do not provide the types of constructivist learning environments as observed in FLOSS communities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FLOSSCOM_Wp4_PHASE2_REPORT_d1.pdf},
	author = {Martin J. Weller and Andreas Meiszner and Sowe, Sulayman K. and Athanasis Karoulis}
}
@conference {533,
	title = {Requirements Acquisition in Open Source Development: Firefox 2.0},
	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 = {69 - 79},
	publisher = {Springer},
	organization = {Springer},
	chapter = {6},
	abstract = {Open Source Software Development appears to depart radically from conventional notions of software engineering. In particular, requirements for Open Source projects seem to be asserted rather than elicited. This paper examines features of the latest major release of the Firefox web browser in attempt to understand how prevalent this phenomenon is. Using archives of mailing lists and issue tracking databases, these features were traced from first mention to release, to determine the process by which requirements are proposed, adopted, and implemented in Firefox. The results confirm the importance of user participation as developers of open source products.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Requirements\%20Acquisition.pdf},
	author = {Noll, John}
}
@article {863,
	title = {The Role of Participation Architecture in Growing Sponsored Open Source Communities},
	journal = {Industry \& Innovation},
	volume = {15},
	year = {2008},
	month = {4/2008},
	pages = {145 - 168},
	author = {Joel West and Siobhan O{\textquoteright}Mahony}
}
@article {1392,
	title = {Self-organization process in open-source software: An empirical study},
	journal = {Information and Software Technology},
	volume = {50},
	year = {2008},
	month = {4/2008},
	pages = {361 - 374},
	abstract = {Software systems must continually evolve to adapt to new functional requirements or quality requirements to remain competitive in the marketplace. However, different software systems follow different strategies to evolve, affecting both the release plan and the quality of these systems. In this paper, software evolution is considered as a self-organization process and the difference between closed-source software and open-source software is discussed in terms of self-organization. In particular, an empirical study of the evolution of Linux from version 2.4.0 to version 2.6.13 is reported. The study shows how open-source software systems self-organize to adapt to functional requirements and quality requirements.},
	keywords = {Empirical study;, evolution, linux, requirements, Self-organization, software evolution},
	issn = {09505849},
	doi = {10.1016/j.infsof.2007.02.018},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584907000225},
	author = {Yu, Liguo}
}
@booklet {518,
	title = {Slouching toward Open Innovation:  Free and Open Source Software (FOSS) for Electronic Health Information},
	year = {2008},
	month = {Dec},
	abstract = {The potential for Free and Open Source Software (FOSS) to enable open innovation in a particular software market depends on the characteristics of that market. From this premise, using a case study approach, this Article argues that some software markets have characteristics that inherently disfavor initiating or expanding the use of FOSS and its unique mode of licensing the intellectual property that underlies software. The case study involves software to manage health information for hospitals or physician groups in the form of the electronic medical record, or EMR. Proprietary software venders supply most of the products for this software market. Recently, the U.S. government undertook experimental steps to promote a FOSS package for EMR, raising the question as to whether the EMR software market is amenable to FOSS. This Article describes various factors that might signal a FOSS disfavoring market, including low technical aptitude among users, differences among users in their work flow and software interface needs, users with dispassionate computing agendas, and entrenched proprietary competitors in an area supporting minimal complementary goods or services. FOSS, however, might be able to overcome these impedances in a particular software market if its unique motivational mix is strong enough. This Article describes potential facilitators to support this possibility. One such facilitator, specifically for the EMR market, but perhaps generally for other markets, may be safe harbors for FOSS development within any relevant anti-collaboration and anti-tinkering laws. Licensing facilitators include emphasizing approaches such as dual licensing or promoting FOSS contributions by contractors engaged by users. This Article concludes by mentioning potential non-licensing facilitators to augment the FOSS motivational mix for markets that might disfavor it.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/VetterSlouchingTowardOpenInnovation-FOSSforEHI_6.29.2008.pdf},
	author = {Greg R Vetter}
}
@conference {WeiBgerber:2008:SPG:1370750.1370767,
	title = {Small patches get in!},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {67{\textendash}76},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {While there is a considerable amount of research on analyzing the change information stored in software repositories, only few researcher have looked at software changes contained in email archives in form of patches. In this paper we look at the email archives of two open source projects and answer questions like the following: How many emails contain patches? How long does it take for a patch to be accepted? Does the size of the patch influence its chances to be accepted or the duration until it gets accepted? Obviously, the answers to these questions can be helpful for the authors of patches, in particular because some of the answers are surprising.},
	keywords = {case study, cvs, email, email archives, flac, mailing list, openafs, patch acceptance, patches, revision control, scm},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370767},
	url = {http://doi.acm.org/10.1145/1370750.1370767},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p67-weissgerber.pdf},
	author = {Wei{\ss}gerber, Peter and Neu, Daniel and Diehl, Stephan}
}
@conference {538,
	title = {Social Dynamics of FLOSS Team Communication Across Channels},
	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 = {131 - 142},
	publisher = {Springer},
	organization = {Springer},
	chapter = {11},
	abstract = {This paper extends prior investigation into the social dynamics of free and open source (FLOSS) teams by examining the methodological questions arising from research using social network analysis on open source projects. We evaluate the validity of data sampling by examining dynamics of communication centralization, which vary across multiple communication channels. We also introduce a method for intensity-based smoothing in dynamic social network analysis.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_11},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Social\%20Dynamics\%20of\%20Floss.pdf},
	author = {Andrea Wiggins and Howison, James and Kevin Crowston}
}
@conference {552,
	title = {Social Networking Technologies for Free-Open Source E-Learning Systems},
	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 = {289 - 297},
	publisher = {Springer},
	organization = {Springer},
	chapter = {25},
	abstract = {In this paper, we illustrate our methodology for academic teaching, based on cooperative learning paradigm, which also relies on cutting edge e-learning techniques. We use Web 2.0 resources to fulfill requirements for an interactive-constructivistic {\textquotedblleft}learning space{\textquotedblright}, where blended-teaching paradigm may be proficiently applied. We extend an existing Free/Open Source Software Learning Management System, to create a cooperative and community-based learning space adherent to our proposal.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_25},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Social\%20Networking\%20Technologies.pdf},
	author = {Di Cerbo, Francesco and Dodero, Gabriella and Succi, Giancarlo}
}
@article {Barcellini2008141,
	title = {A socio-cognitive analysis of online design discussions in an Open Source Software community},
	journal = {Interacting with Computers},
	volume = {20},
	number = {1},
	year = {2008},
	pages = {141 - 165},
	abstract = {This paper is an analysis of online discussions in an Open Source Software (OSS) design community, the Python project. Developers of Python are geographically distributed and work online asynchronously. The objective of our study is to understand and to model the dynamics of the OSS design process that takes place in mailing list exchanges. We develop a method to study distant and asynchronous collaborative design activity based on an analysis of quoting practices. We analyze and visualize three aspects of the online dynamics: social, thematic temporal, and design. We show that roles emerge during discussions according to the involvement and the position of the participants in the discussions and how they influence participation in the design discussions. In our analysis of the thematic temporal dynamics of discussion, we examine how themes of discussion emerge, diverge, and are refined over time. To understand the design dynamics, we perform a content analysis of messages exchanged between developers to reveal how the online discussions reflect the {\textquotedblleft}work flow{\textquotedblright} of the project: it provides us with a picture of the collaborative design process in the OSS community. These combined results clarify how knowledge and artefacts are elaborated in this epistemic, exploration-oriented, OSS community. Finally, we outline the need to automate of our method to extend our results. The proposed automation could have implications for both researchers and participants in OSS communities.},
	keywords = {Role},
	issn = {0953-5438},
	doi = {10.1016/j.intcom.2007.10.004},
	url = {http://www.sciencedirect.com/science/article/pii/S0953543807000793},
	author = {Barcellini, Flore and D{\'e}tienne, Fran{\c c}oise and Burkhardt, Jean-Marie and Warren Sack}
}
@conference {Thummalapenta:2008:SDF:1370750.1370775,
	title = {SpotWeb: detecting framework hotspots via mining open source repositories on the web},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {109{\textendash}112},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The essentials of modern software development (such as low cost and high efficiency) demand software developers to make intensive reuse of existing open source frameworks or libraries (generally referred as frameworks) available on the web. However, developers often face challenges in reusing these frameworks due to several factors such as the complexity and lack of proper documentation. In this paper, we propose a code-search-engine-based approach that tries to detect hotspots in a given framework by mining code examples gathered from open source repositories available on the web; these hotspots are the APIs that are frequently reused.

Hotspots can serve as starting points for developers in understanding and reusing the given framework. We developed a tool, called SpotWeb, for frameworks or libraries written in Java and conducted two case studies with two open source frameworks JUnit and Log4j. We also show that the detected hotspots of Log4j and JUnit are consistent with their respective documentations.},
	keywords = {code reuse, code search engine, frameworks, hotspots, junit, log4j, repositories},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370775},
	url = {http://doi.acm.org/10.1145/1370750.1370775},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p109-thummalapenta.pdf},
	author = {Thummalapenta, Suresh and Xie, Tao}
}
@conference {546,
	title = {The SQO-OSS Quality Model: Measurement Based Open Source Software Evaluation},
	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 = {237 - 248},
	publisher = {Springer},
	organization = {Springer},
	chapter = {19},
	abstract = {Software quality evaluation has always been an important part of software business. The quality evaluation process is usually based on hierarchical quality models that measure various aspects of software quality and deduce a characterization of the product quality being evaluated. The particular nature of open source software has rendered existing models inappropriate for detailed quality evaluations. In this paper, we present a hierarchical quality model that evaluates source code and community processes, based on automatic calculation of metric values and their correlation to a set of predefined quality profiles.1
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_19},
	attachments = {https://flosshub.org/sites/flosshub.org/files/SQO-OSS\%20Quality\%20Model.pdf},
	author = {Samoladas, Ioannis and Gousios, Georgios and Diomidis Spinellis and Ioannis Stamelos}
}
@article {135,
	title = {A statistical framework for analyzing the duration of software projects},
	journal = {Empirical Software Engineering},
	volume = {13},
	number = {2},
	year = {2008},
	note = {Times Cited: 0},
	pages = {147-184},
	abstract = {The duration of a software project is a very important feature, closely related to its cost. Various methods and models have been proposed in order to predict not only the cost of a software project but also its duration. Since duration is essentially the random length of a time interval from a starting to a terminating event, in this paper we present a framework of statistical tools, appropriate for studying and modeling the distribution of the duration. The idea for our approach comes from the parallelism of duration to the life of an entity which is frequently studied in biostatistics by a certain statistical methodology known as survival analysis. This type of analysis offers great flexibility in modeling the duration and in computing various statistics useful for inference and estimation. As in any other statistical methodology, the approach is based on datasets of measurements on projects. However, one of the most important advantages is that we can use in our data information not only from completed projects, but also from ongoing projects. In this paper we present the general principles of the methodology for a comprehensive duration analysis and we also illustrate it with applications to known data sets. The analysis showed that duration is affected by various factors such as customer participation, use of tools, software logical complexity, user requirements volatility and staff tool skills.},
	author = {Sentas, P. and Lefteris Angelis and Ioannis Stamelos}
}
@conference {Siy:2008:SDW:1370750.1370784,
	title = {Summarizing developer work history using time series segmentation: challenge report},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {137{\textendash}140},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Temporal segmentation partitions time series data with the intent of producing more homogeneous segments. It is a technique used to preprocess data so that subsequent time series analysis on individual segments can detect trends that may not be evident when performing time series analysis on the entire dataset.

This technique allows data miners to partition a large dataset without making any assumption of periodicity or any other a priori knowledge of the dataset{\textquoteright}s features.

We investigate the insights that can be gained from the application of time series segmentation to software version repositories. Software version repositories from large projects contain on the order of hundreds of thousands of timestamped entries or more. It is a continuing challenge to aggregate such data so that noise is reduced and important characteristics are brought out.

In this paper, we present a way to summarize developer work history in terms of the files they have modified over time by segmenting the CVS change data of individual Eclipse developers. We show that the files they modify tends to change significantly over time though most of them tend to work within the same directories.},
	keywords = {contributions, cvs, developers, eclipse, msr challenge, temporal segmentation, time series, work history},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370784},
	url = {http://doi.acm.org/10.1145/1370750.1370784},
	author = {Siy, Harvey and Chundi, Parvathi and Subramaniam, Mahadevan}
}
@conference {Spinellis:2008:TFK:1368088.1368140,
	title = {A tale of four kernels},
	booktitle = {Proceedings of the 30th international conference on Software engineering},
	series = {ICSE {\textquoteright}08},
	year = {2008},
	pages = {381{\textendash}390},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The FreeBSD, GNU/Linux, Solaris, and Windows operating systems have kernels that provide comparable facilities. Interestingly, their code bases share almost no common parts, while their development processes vary dramatically. We analyze the source code of the four systems by collecting metrics in the areas of file organization, code structure, code style, the use of the C preprocessor, and data organization. The aggregate results indicate that across various areas and many different metrics, four systems developed using wildly different processes score comparably. This allows us to posit that the structure and internal quality attributes of a working, non-trivial software artifact will represent first and foremost the engineering requirements of its construction, with the influence of process being marginal, if any.},
	keywords = {comparison, freebsd, linux, open source, opensolaris, proprietary software, windows, wrk},
	isbn = {978-1-60558-079-1},
	doi = {10.1145/1368088.1368140},
	url = {http://doi.acm.org/10.1145/1368088.1368140},
	author = {Diomidis Spinellis}
}
@conference {Pattison:2008:TWP:1370750.1370776,
	title = {Talk and work: a preliminary report},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {113{\textendash}116},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Developers in Open Source Software (OSS) projects communicate using mailing lists. By convention, the mailing lists used only for task-related discussions, so they are primarily concerned with the software under development, and software process issues (releases, etc.). We focus on the discussions concerning the software, and study the frequency with which software entities (functions, methods, classes, etc) are mentioned in the mail. We find a strong, striking, cumulative relationship between this mention count in the email, and the number of times these entities are included in changes to the software. When we study the same phenomena over a series of time-intervals, the relationship is much less strong. This suggests some interesting avenues for future research.},
	keywords = {ant, apache, email, mailing lists, postgresql, python, scm, source code},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370776},
	url = {http://doi.acm.org/10.1145/1370750.1370776},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p113-pattison.pdf},
	author = {Pattison, David S. and Bird, Christian A. and Premkumar T. Devanbu}
}
@conference {554,
	title = {To What Extent Does It Pay to Approach Open Source Software for a Big Telco Player?},
	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 = {307 - 315},
	publisher = {Springer},
	organization = {Springer},
	chapter = {27},
	abstract = {In this paper we describe the strategy under adoption in Telecom Italia (TI) Technology Department toward open source software. This stems from trying to create synergy among big Telco Player to increase knowledge and influence over strategic communities to the evaluation of the creation of new communities over internally developed applications. In particular here the approach and the expectations in starting the community on WADE (Workflow and Agent Development Environment) is described. This is a platform used to develop mission critical applications and is the main evolution of JADE a popular Open Source framework for the development of interoperable intelligent multi-agent systems. It adds to JADE the support for the execution of tasks defined according to the workflow metaphor as well as a number of mechanisms that help managing the complexity of the distribution both in terms of administration and fault tolerance. The idea is to use WADE as a mean to gather critical information on the opportunity of approaching OS as a strategic mean toward the development of always more important application in Operating Support System for TI, possibly also involving other great Telco Players For this reason great care is being paid in setting up the Community environment and in deciding which metrics are to be extracted from it, since the result will be the input for a strategic decision in TI.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/To\%20What\%20Extent\%20Does\%20it\%20Pay\%20to\%20Approach.pdf},
	author = {Banzi, Massimo and Bruno, Guido and Caire, Giovanni}
}
@conference {543,
	title = {The Total Growth of Open Source},
	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 = {197 - 209},
	publisher = {Springer},
	organization = {Springer},
	chapter = {16},
	abstract = {Software development is undergoing a major change away from a fully closed software process towards a process that incorporates open source software in products and services. Just how significant is that change? To answer this question we need to look at the overall growth of open source as well as its growth rate. In this paper, we quantitatively analyze the growth of more than 5000 active and popular open source software projects. We show that the total amount of source code as well as the total number of open source projects is growing at an exponential rate. Previous research showed linear and quadratic growth in lines of source code of individual open source projects. Our work shows that open source is expanding into new domains and applications at an exponential rate.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_16},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Total\%20Growth\%20of\%20Open\%20Source.pdf},
	author = {Amit Deshpande and Dirk Riehle}
}
@conference {539,
	title = {Towards a Global Research Infrastructure for Multidisciplinary Study of Free/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 = {143 - 158},
	publisher = {Springer},
	organization = {Springer},
	chapter = {12},
	abstract = {The Free/Open Source Software (F/OSS) research community is growing across and within multiple disciplines. This community faces a new and unusual situation. The traditional difficulties of gathering enough empirical data have been replaced by issues of dealing with enormous amounts of freely available public data from many disparate sources (online discussion forums, source code directories, bug reports, OSS Web portals, etc.). Consequently, these data are being discovered, gathered, analyzed, and used to support multidisciplinary research. However at present, no means exist for assembling these data under common access points and frameworks for comparative, longitudinal, and collaborative research across disciplines. Gathering and maintaining large F/OSS data collections reliably and making them usable present several research challenges. For example, current projects usually rely on direct access to, and mining of raw data from groups that generate it, and both of these methods require unique effort for each new corpus, or even for updating existing corpora. In this paper, we identify several needs and critical factors in F/OSS empirical research across disciplines, and suggest recommendations for design of a global research infrastructure for multi-disciplinary research into F/OSS development.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_12},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Towards\%20a\%20Global\%20Research\%20Infrastracture.pdf},
	author = {Gasser, Les and Walt Scacchi}
}
@inbook {869,
	title = {Towards a Global Research Infrastructure for Multidisciplinary Study of Free/Open Source Software Development},
	booktitle = {Open Source Development, Communities and Quality},
	series = {IFIP International Federation for Information Processing},
	volume = {275},
	year = {2008},
	pages = {143-158},
	publisher = {Springer},
	organization = {Springer},
	address = {Boston},
	author = {Gasser, Les and Walt Scacchi},
	editor = {Russo, B. and Damiani, E. and Hissan, S. and Lundell, B. and Succi, G.}
}
@conference {Herraiz:2008:TSB:1370750.1370786,
	title = {Towards a simplification of the bug report form in eclipse},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {145{\textendash}148},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {We believe that the bug report form of Eclipse contains too many fields, and that for some fields, there are too many options. In this MSR challenge report, we focus in the case of the severity field. That field contains seven different levels of severity. Some of them seem very similar, and it is hard to distinguish among them. Users assign severity, and developers give priority to the reports depending on their severity. However, if users can not distinguish well among the various severity options, they will probably assign different priorities to bugs that require the same priority. We study the mean time to close bugs reported in Eclipse, and how the severity assigned by users affects this time. The results shows that classifying by time to close, there are less clusters of bugs than levels of severity. We therefore conclude that there is a need to make a simpler bug report form.},
	keywords = {bug fixing, bug report, bug tracking system, classification, eclipse, msr challenge, severity},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370786},
	url = {http://doi.acm.org/10.1145/1370750.1370786},
	author = {Herraiz, Israel and Daniel M. German and Jesus M. Gonzalez-Barahona and Gregorio Robles}
}
@conference {564,
	title = {Towards The Evaluation of OSS Trustworthiness: Lessons Learned From The Observation of Relevant OSS 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 = {389 - 395},
	publisher = {Springer},
	organization = {Springer},
	chapter = {37},
	abstract = {To facilitate the adoption of open-source software (OSS) in industry, it is important to provide potential users (i.e., those who could decide to adopt OSS) with the means for evaluating the trustworthiness of OS products. This paper presents part of the work done in the QualiPSo project for this purpose. A set of factors that are believed to affect the perception of trustworthiness are introduced. In order to test the feasibility of deriving a correct, complete and reliable evaluation of trustworthiness on the basis of these factors, a set of well-known OSS projects have been chosen. Then, the possibility to assess the proposed factors on each project was verified: not all the factors appear to be observable or measurable. The paper reports what information is available to support the evaluation and what is not. This knowledge is considered to be useful to users, who are warned that there are still dark areas in the characterization of OSS products, and to developers, who should provide more data and characteristics on their products in order to support their adoption.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Toward\%20the\%20Evaluation\%20of\%20OSS.pdf},
	author = {Taibi, Davide and del Bianco, Vieri and Carbonare, Davide and Lavazza, Luigi and Morasca, Sandro}
}
@article {Sadowski2008323,
	title = {Transition of governance in a mature open software source community: Evidence from the Debian case},
	journal = {Information Economics and Policy},
	volume = {20},
	number = {4},
	year = {2008},
	note = {"We primarily used internal documents related to the contents and context of different Debian projects."
"Furthermore, we attended several Debian conferences and were {\textquoteleft}{\textquoteleft}lurking around{\textquotedblright} on the Debian mailing lists, websites, IRC channels, etc."},
	pages = {323 - 332},
	abstract = {As open source software (OSS) communities mature, they have to introduce a variety of governance mechanisms to manage the participation of their members and to coordinate the launch of new releases. The Debian community introduced new mechanisms of informal administrative control based on a constitution, elected leaders, and used interactive communication channels. We show that these control mechanisms were introduced as a response to emerging innovative opportunities due to the usage of source packages and to the need to build a responsive organization within the Debian OSS community.},
	keywords = {debian, governance},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.05.001},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4SHF4BS-1/2/579ba679ee43d7c77302f3595334dd24},
	author = {Bert M. Sadowski and Gaby Sadowski-Rasters and Geert Duysters}
}
@book {50,
	title = {Two Bits: The Cultural Significance of Free Software and the Internet},
	year = {2008},
	publisher = {Duke University Press},
	organization = {Duke University Press},
	author = {Christoper Kelty}
}
@booklet {519,
	title = {Ubuntuism, Commodification, and the Software Dialectic.},
	year = {2008},
	month = {Sept},
	abstract = {"Free as in speech, but not free as in beer," is the refrain made famous by Richard Stallman, the standard-bearer of the free software movement. However, many free software advocates seem to be of the opinion that the purity of free software is somehow tainted by any preoccupation with money or profit. Inevitably, this has implications for the economic sustainability of free software, for without a source of income, how can free software hope to survive? The challenge of finding a way to ensure economic sustainability without sacrificing the ideals of free software is what we have termed the "software dialectic.""While the literature on the economics of free software is already quite substantial, in this essay we approach the subject by considering first principles, such as the difference between wealth and money, how the market chooses what to produce, and what the laws of thermodynamics have to do with economics. Finally, even though the ideas expressed in this essay apply to free software in general, here we shall be focusing on that particular incarnation of free software known as the GNU/Linux system.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Ubuntuism_Commodification_and_the_Software_Dialectic.pdf},
	author = {Mike Chege}
}
@conference {Sudakrishnan:2008:UBF:1370750.1370761,
	title = {Understanding bug fix patterns in verilog},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {39{\textendash}42},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Today, many electronic systems are developed using a hardware description language, a kind of software that can be converted into integrated circuits or programmable logic devices. Like traditional software projects, hardware projects have bugs, and significant developer time is spent fixing them. A useful first step toward reducing bugs in hardware is developing an understanding of the frequency of different types of errors. Once the most common types are known, it is then possible to focus attention on eliminating them. As most hardware projects use software configuration management repositories, these can be mined for the textual bug fix changes. In this project, we analyze the bug fix history of four hardware projects written in Verilog and manually define 25 bug fix patterns. The frequency of each bug type is then computed for all projects. We find that 29 -- 55\% of the bug fix pattern instances in Verilog involve assignment statements, while 18 -- 25\% are related to if statements.},
	keywords = {bug fixing, error classification, hdl, verilog, VHDL},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370761},
	url = {http://doi.acm.org/10.1145/1370750.1370761},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p39-sudakrishnan.pdf},
	author = {Sudakrishnan, Sangeetha and Madhavan, Janaki and Whitehead,Jr., E. James and Renau, Jose}
}
@article {138,
	title = {Understanding knowledge sharing activities in free/open source software projects: An empirical study},
	journal = {Journal of Systems and Software},
	volume = {81},
	number = {3},
	year = {2008},
	note = {"Our study utilized data from the Debian project lists archives.... The Debian project hosts over 100 lists on all aspects related to the project. From the Debian lists archives (Debian Mailing Lists) we selected two high volume mailing lists. The following lists are analyzed in our study:
{\textbullet} Debian-user. This list is specifically dedicated to help and discussion among users of Debian who speak English. {\textbullet} Debian-devel. This list is specifically dedicated to discus-
sion about technical development topics.
Our data collection period for both lists was from January 2000 to December 2005. We obtained archived mbox files of the two lists. Each file is a single text file containing one month of archived email messages. Every email message has a unique message-id, together with other identification fields defined by the Internet Message Format (RFC) 2822 (Internet Message Format, 2001)."},
	pages = {431-446},
	abstract = {Free/Open Source Software (F/OSS) projects are people-oriented and knowledge intensive software development environments. Many researchers focused on mailing lists to study coding activities of software developers. How expert software developers interact with each other and with non-developers in the use of community products have received little attention. This paper discusses the altruistic sharing of knowledge between knowledge providers and knowledge seekers in the Developer and User mailing lists of the Debian project. We analyze the posting and replying activities of the participants by counting the number of email messages they posted to the lists and the number of replies they made to questions others posted. We found out that participants interact and share their knowledge a lot, their positing activity is fairly highly correlated with their replying activity, the characteristics of posting and replying activities are different for different kinds of lists, and the knowledge sharing activity of self-organizing Free/Open Source communities could best be explained in terms of what we called "Fractal Cubic Distribution" rather than the power-law distribution mostly reported in the literature. The paper also proposes what could be researched in knowledge sharing activities in F/OSS projects mailing list and for what purpose. The research findings add to {\textquoteright} our understanding of knowledge sharing activities in F/OSS projects. (C) 2007 Elsevier Inc. All rights reserved.},
	keywords = {debian, email, email archives, mailing list},
	attachments = {https://flosshub.org/sites/flosshub.org/files/JSS_0.pdf},
	author = {Sowe, Sulayman K. and Ioannis Stamelos and Lefteris Angelis}
}
@conference {540,
	title = {Update Propagation Practices in Highly Reusable Open Source Components},
	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 = {159 - 170},
	publisher = {Springer},
	organization = {Springer},
	chapter = {13},
	abstract = {In today{\textquoteright}s business and software arena, more and more companies are adopting open source software. An example of this rising phenomenon is to base software products on highly reusable open source components. In this scenario, the evolution of the software product is coupled with the evolution of the open source component. A common assumption is that component updates are immediately and regularly propagated to the project. This paper investigates this assumption empirically by studying update propagation practices in two popular open source libraries, zlib and FFmpeg. For each library, we analyze various repository sources with information such as bug reports, revision history, and source code. The results of the case studies suggest that update propagation is subject to several technical and non-technical factors including the way the open source library is used, the extent to which updates are documented, and the degree of community involvement. Based on these findings, we propose a set of recommendations that would allow better follow-up of updates and smoother update propagation.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_13},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Update\%20Propagation\%20Practice.pdf},
	author = {Orsila, Heikki and Geldenhuys, Jaco and Ruokonen, Anna and Hammouda, Imed}
}
@conference {560,
	title = {Usability in Company Open Source Software Context - Initial Findings from an Empirical Case Study},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {359 - 365},
	publisher = {Springer},
	organization = {Springer},
	chapter = {33},
	abstract = {In the company open source software (OSS) development context, usability is becoming an important issue due to a growing user population, who is only interested in usable applications, not in their development. Companies try to gain a competitive advantage of OSS by utilizing available components, but the openness is difficult to achieve in the business world with licenses, patents and intellectual property rights. This paper analyses usability and user-interface (UI) development in the company OSS context through an interpretive case study in a software development unit of a large, global corporation. Our initial findings suggest that there is a need for human computer interaction specialists in the OSS context. It is revealed that with the software based on OSS, more time can be spent on usability and UI design. In the company{\textquoteright}s viewpoint, there are still many issues involved in deciding what parts of the product will be open source. Especially UI code may remain closed due to competitive advantage and patents.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Usability\%20in\%20Company\%20Open\%20Source.pdf},
	author = {Iivari, Netta and Hedberg, Henrik and Kirves, Tanja}
}
@article {Barcellini:2008:UDM:1379919.1380288,
	title = {User and developer mediation in an Open Source Software community: Boundary spanning through cross participation in online discussions},
	journal = {Int. J. Hum.-Comput. Stud.},
	volume = {66},
	number = {7},
	year = {2008},
	pages = {558{\textendash}570},
	publisher = {Academic Press, Inc.},
	address = {Duluth, MN, USA},
	abstract = {The aim of this research is to analyse how design and use are mediated in Open Source Software (OSS) design. Focusing on the Python community, our study examines a {\textquoteright}{\textquoteright}pushed-by-users{\textquoteright}{\textquoteright} design proposal through the discussions occurring in two mailing-lists: one, user-oriented and the other, developer-oriented. To characterize the links between users and developers, we investigate the activities and references (knowledge sharing) performed by the contributors to these two mailing-lists. We found that the participation of users remains local to their community. However, several key participants act as boundary spanners between the user and the developer communities. This emerging role is characterized by cross-participation in parallel same-topic discussions in both mailing-lists, cohesion between cross-participants, the occupation of a central position in the social network linking users and developers, as well as active, distinctive and adapted contributions. The user championing the proposal acts as a key boundary spanner coordinating the process and using explicit linking strategies. We argue that OSS design may be considered as a form of {\textquoteright}{\textquoteright}role emerging design{\textquoteright}{\textquoteright}, i.e. design organized and pushed through emerging roles and through a balance between these roles. The OSS communities seem to provide a suitable socio-technical environment to enable such role emergence. },
	keywords = {Boundary spanners, Cross-participants, Distributed design, Open Source Software Community, Role emerging design},
	issn = {1071-5819},
	doi = {10.1016/j.ijhcs.2007.10.008},
	url = {http://dx.doi.org/10.1016/j.ijhcs.2007.10.008},
	author = {Barcellini, Flore and D{\'e}tienne, Fran{\c c}oise and Burkhardt, Jean-Marie}
}
@conference {541,
	title = {Using Social Network Analysis Techniques to Study Collaboration between a FLOSS Community and a Company},
	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 = {171 - 186},
	publisher = {Springer},
	organization = {Springer},
	chapter = {14},
	abstract = {Because of the sheer volume of information available in FLOSS repositories, simple analysis have to face the problems of filtering the relevant information. Hence, it is essential to apply methodologies that highlight that information for a given aspect of the project. In this paper, some techniques from the social sciences have been used on data from version control systems to extract information about the development process of FLOSS projects with the aim of highlighting several processes that occur in FLOSS projects and that are difficult to obtain by other means. In particular, the collaboration between the FLOSS community and a company has been studied by selecting two projects as case studies. The results highlight aspects such as efficiency in the development process, release management and leadership turnover.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_14},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Using\%20Social\%20Network.pdf},
	author = {Martinez-Romo, Juan and Gregorio Robles and Gonzalez-Barahona, Jesus and Ortu{\~n}o-Perez, Miguel}
}
@conference {Hindle:2008:LCT:1370750.1370773,
	title = {What do large commits tell us?: a taxonomical study of large commits},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {99{\textendash}108},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Research in the mining of software repositories has frequently ignored commits that include a large number of files (we call these large commits). The main goal of this paper is to understand the rationale behind large commits, and if there is anything we can learn from them. To address this goal we performed a case study that included the manual classification of large commits of nine open source projects. The contributions include a taxonomy of large commits, which are grouped according to their intention. We contrast large commits against small commits and show that large commits are more perfective while small commits are more corrective. These large commits provide us with a window on the development practices of maintenance teams.},
	keywords = {boost, bug fixing, egroupware, enlightenment, evolution, firebird, large commits, maintenance, mysql, postgresql, samba, software evolution, source control system, spring},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370773},
	url = {http://doi.acm.org/10.1145/1370750.1370773},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p99-hindle.pdf},
	author = {Hindle, Abram and Daniel M. German and Holt, Ric}
}
@conference {Pohl:2008:DNM:1370114.1370135,
	title = {What dynamic network metrics can tell us about developer roles},
	booktitle = {Proceedings of the 2008 international workshop on Cooperative and human aspects of software engineering (CHASE {\textquoteright}08)},
	series = {CHASE {\textquoteright}08},
	year = {2008},
	note = {paper d/l from http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.217.4765

this particular paper focuses on building the SNA using co-authorship of files in Tomcat.},
	pages = {81{\textendash}84},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software development is heavily dependent on the participants of the process and their roles within the process. Each developer has his specific skills and interests and hence contributes to the project in a different way. While some programmers work on separate modules, others developers integrate these modules towards the final product. To identify such different groups of people one approach is to work with methods taken from social network analysis. To this end, a social network has to be defined in a suitable way, and appropriate analysis strategies have to be chosen. This paper shows how a network of software developers could be defined based on information in a software repository, and what it can possibly tell about roles of developers (and what not) in the process of the application server Tomcat.},
	keywords = {identifying roles, social network analysis},
	isbn = {978-1-60558-039-5},
	doi = {10.1145/1370114.1370135},
	url = {http://doi.acm.org/10.1145/1370114.1370135},
	attachments = {https://flosshub.org/sites/flosshub.org/files/10.1.1.217.4765.pdf},
	author = {Pohl, Mathias and Diehl, Stephan}
}
@conference {561,
	title = {Willingness to Cooperate Within the Open Source Software Domain},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {367 - 373},
	publisher = {Springer},
	organization = {Springer},
	chapter = {34},
	abstract = {Open Source Software (OSS) is an increasingly hot topic in the business domain. One of the key benefits mentioned is the unlimited access to the source code, which enables large communities to continuously improve a software application and prevents vendor lock-in. How attractive these benefits may be, the market for OSS however remains limited. In the Netherlands research consisting of 7 interviews and a survey among 206 Open Source Software Service providers (with a 34\% response rate) was done to determine whether service providers wanted to cooperate in an Association that will set quality levels and guarantees to its members and their customers.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_34},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Willingness\%20to\%20Cooperate.pdf},
	author = {Ravesteyn, Pascal and Silvius, Gilbert}
}
@conference {664,
	title = {1st International Workshop on Trust in Open Source Software (TOSS)},
	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 = {371 - 373},
	publisher = {Springer},
	organization = {Springer},
	chapter = {48},
	abstract = {The 1st International Workshop on Trust in Open Source Software (TOSS) focuses on one of the major factors in the adoption of software solutions: the trustworthiness of OSS, which has influenced the widespread adoption of OSS in industry. Software quality aspects have been investigated for a long time in the academia but the usage/production of OSS is creating new challenges and the points of view of the industry and the academia may differ, especially on the trustworthiness of OSS. The aim of the workshop is to open a communication channel between the industry and the academia focusing on this issue and promote a long lasting discussion on it. The workshop tries to identify the different points of views and the different approaches that can result in benefits for the software industry.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_48},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1st\%20Intl\%20Workshop\%20on\%20Trust.pdf},
	author = {Morasca, Sandro and Sillitti, Alberto}
}
@conference {667,
	title = {2nd International Workshop on Public Data about Software Development (WoPDaSD 2007)},
	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 = {381 - 383},
	publisher = {Springer},
	organization = {Springer},
	chapter = {51},
	abstract = {Exchange of detailed data about software development between research teams, and specifically about data available from public repositories of libre (free, open source) software projects is becoming more and more common. This workshop will explore the benefits and problems of such exchange, and the steps needed to foster it. As a case example of data exchange, the workshop organizers suggest two large datasets to be analyzed by participants.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_51},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2nd\%20Intl\%20Workshop\%20on\%20Public\%20Data.pdf},
	author = {Gonzalez-Barahona, Jesus and Conklin, Megan and Gregorio Robles}
}
@article {flosswp362,
	title = {An Analysis of Involvement of HCI Experts in Distributed Software Development: Practical Issues},
	year = {2007},
	month = {July},
	abstract = {Abstract. Traditionally, free and open source software (F/OSS) developers have focused more on the features of a specific application, most of the time ignoring the necessity of user-centric design. This has mainly stemmed from the fact that developers have little interaction with HCI studies, knowledge bases and reports. Moreover, the lack of user interface designers has resulted in a lack of awareness of this area. As a consequence, the user centric design phenomenon within F/OSS applications has been neglected. In this paper, we have mentioned various problems that would slow down a F/OSS project development towards a user-engineered software, and investigated the ways that HCI experts and developers interact with each other and researched bug reporting systems by means of eligibility to issue usability bugs. For the conclusion part, we have explored possible ways to achieve a user-centric design in a project with asynchronous interaction among geographically distributed developers.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cetin-verzulli-sandra},
	author = {G{\"o}rkem {\c C}etin and Damiano Verzulli and Sandra Frings}
}
@article {flosswp370,
	title = {Analysis of the Informal Learning Environment of FLOSS (Free / Libre Open Source Software) Communities},
	year = {2007},
	month = {July},
	abstract = {The general concept behind Free/Libre/Open Source Software (henceforth FLOSS) is making the source code of software accessible to anyone who wants to obtain it. Binaries or executables are available via the Internet and can be {\textquoteright}freely{\textquoteright} downloaded and used. Prolific licensing agreements such as the General Public License (GPL) define the rights users have over the product. In the literature, many terms are in use to describe the FLOSS phenomenon. Notably, Free Software (FS), a term used by Free Software Foundation (FSF) and Open Source Software (OSS) used by the Open Source Initiative (OSI). In addition, Free Open Source Software (FOSS), Libre Software (LS), and Free/Libre/Open Source Software (FLOSS) are terms frequently used by researchers. In this report the term FLOSS is used to refer to users??? freedom to use, modify, distribute, or even sell the software with little obligations as in propriety or closed source software. When a user modifies the software, he/she can either choose to keep changes made private or altruistically return them to the FLOSS community so that everyone can benefit from his derived work. FLOSS development did not begin with the inception of the Linux operating system, in 1991. Rather, the concept existed since the formation of SHARE ??? a working group set up to coordinate the programming work of the IBM 701, in 1952 (Sowe, 2007b). In the academic environment, software development and distribution among researchers and departments is not new, and goes back to the earliest days of software in university environments when software was developed to solve practical problems and could be freely shared. However, what is now true is that FLOSS has fundamentally changed the way we develop and distribute software. Enable by the Internet, geographically distributed individuals voluntarily contribute to a project by means of the Bazaar model (Raymond, 1999). Extensive peer collaboration allows project participants to write code, debug, test, and integrate software. Communities in various projects provide support services such as suggestions for products features, act as distributing organs, answer queries, help new members having problems with the software. FLOSS development not only exemplifies a viable software development approach, but also a model for the creation of self-learning and self-organizing communities (Sowe, et al. 2006c). FLOSS is also a virtual learning context in which both professional software developers and novice users benefit by leveraging their knowledge and information access repertoire. The context enable them to participate at their own convenience and learn (coding or other software related task) at their own pace (Sowe, et al. 2005; page 297). Furthermore, learners can conclude on the learning scope themselves (what to do) and decide on the method of acquiring the knowledge (how to do it). Knowledge acquisition is accomplished, for example, by having access to a large code-base, studying online documentation, asking more experienced members for assistance. In essence knowledge is acquired in FLOSS through learning by doing, which represents the drill-and-practice approach in normal constructivist environments. However, the FLOSS virtual learning context is not without its downside. Apart from physical isolation and detachment from face-to-face interaction commonly associated with virtual learning environments, learning in FLOSS requires access to Internet and moderate computer facilities. In addition, a high degree of computer literacy, reading, writing, and typing is required to participate effectively. The environment is also not conflict free. Flaming, the feeling of being ignored in a dominant discussion, disinterestedness, long delays in receiving responses from communities, the expenditure of searching through discussion archives to see issues previously raised in the communities, access rights to participate in some community activities are all major concerns in the management of the FLOSS learning context (Sowe, et al. 2005). In recent times, FLOSS is making inroads not only in business and software industries but in colleges and universities as well. There is increased interest in the FLOSS learning environment (Sowe, et al., 2004; Bacon and Dillion, 2006) and in FLOSS projects as bazaars of learning (Sowe, et al., 2006). As Faber (2002) noted, FLOSS is both an alternative teaching methodology and an educational model. The main objective of FLOSSCom is using the principles of informal learning environments of FLOSS communities to improve Information and Communication Technology (ICT) supported formal education. Despite the influence and popularity of FLOSS and the benefit inherent in its methodology, educational institutions have been slow to adapt. This can partly due to the fact that the FLOSS environment is fundamentally different from the formal learning environment in most institutions. The focus of this report is collate and report on the learning activities of individuals in various FLOSS communities. The report benefits from the experiences and expositions of various authors in order to provide a synergy and a fresh look into the learning environment of FLOSS communities. FLOSS communities, like other online communities (e.g. Community of Practice (CoPs)) have many interrelated elements that define the dynamics of the community. As such, this report is divided into 5 major sections, each focusing on a specific aspect of the learning environment of FLOSS communities with a 6th section summarizing the main findings. Section 1: The first part of the report is an introduction to FLOSS. The historical account of FLOSS is presented together with the many meanings of the term. This is followed by the demographic distribution of FLOSS participants and an explanation of what FLOSS communities are. Section 2: The next chapter examines the role of learning and knowledge exchange within the FLOSS community. It includes a description of the composition and roles of members within communities and what motivates various groups of individuals to participate in FLOSS. Section 3: After clarifying the role of learning in the FLOSS community the next chapter focuses on the content of learning processes in FLOSS. This chapter examines both, what skills are learnt and how the skills learnt within the FLOSS community are evaluated. The latter aspect is considered from the perspective of FLOSS community members as well as from the perspective of employers. Section 4: The fourth chapter examines how learning is organized within the FLOSS community. It examines the interaction between community members with regard to learning processes, the learning resources (except for technological resources) that are available and used within FLOSS communities, and the concrete learning processes. Section 5: This section looks at the technological resources used within FLOSS communities. FLOSS projects are almost exclusively administered online and one of the most important prerequisites for their coordination and cooperation is provided by the functionality of various communication and groupware tools. Section 6: The last section of the report proposes the project???s approach to learning in FLOSS. A preliminary set of guidelines as they apply to the principles of informal learning environments of FLOSS communities to improve ICT supported formal education are offered. These preliminary guidelines will be continuously amended in the following phase of the FLOSSCom project.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FLOSSCom_WP2_Phase_1_Report_v070709_1.pdf},
	author = {R{\"u}dige Glott and Andreas Meiszner and Sowe, Sulayman K.}
}
@conference {1007,
	title = {Analysis of the Linux Kernel Evolution Using Code Clone Coverage},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {22 - 22},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Most studies of the evolution of software systems are based on the comparison of simple software metrics. In this paper, we present our preliminary investigation of the evolution of the Linux kernel using code-clone analysis and the code-clone coverage metrics. We examined 136 versions of the stable Linux kernel using a distributed extension of the code clone detection tool CCFinder. The result is shown as a heat map.},
	keywords = {ccfinder, clone, cloning, kernel, linux, metrics, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300022.pdf},
	author = {Livieri, Simone and Higo, Yoshiki and Matsushita, Makoto and Inoue, Katsuro}
}
@conference {636,
	title = {Authenticating from multiple authentication sources in a collaborative platform},
	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 = {229 - 234},
	publisher = {Springer},
	organization = {Springer},
	chapter = {20},
	abstract = {This paper presents a proposal to address the need for multiple authentication sources for users of collaborative work platforms. The proposed approach, developed for the needs of GET and Picolibre, relies on a generic solution that integrate groupware servers in a Shibboleth infrastructure. We have developed adapters for this integration, that we contributed to the phpGroupware
project. This document should serve as a basis for discussion in order to validate the level of generality of the proposed approach. We hope that this approach can also help maintainers of other collaboration platforms, who want to integrate a park of deployed platforms with external user identification and authentication services, get a better view of solutions available with Shibboleth.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Authenticating\%20from\%20multiple.pdf},
	author = {Quang Vu Dang and Olivier Berger and Christian Bac and Hamet, Beno{\^\i}t}
}
@conference {649,
	title = {Benefits and Drawbacks of Open Source Software: An Exploratory Study of Secondary Software Firms},
	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 = {307 - 312},
	publisher = {Springer},
	organization = {Springer},
	chapter = {33},
	abstract = {Much of the assessment of OSS benefits and drawbacks has been based on anecdotal evidence appearing in practitioner publications, white papers, web articles etc. To a greater extent this research has tended to concentrate more on the technical benefits and drawbacks of OSS rather than their business counterparts. Furthermore, public administrations and companies operating within the primary software sector have traditionally been the focus for research on OSS benefits and drawbacks. Taking the viewpoint of IS/IT managers in 13 companies operating in the secondary software sector in Europe, this paper examines their experiences of the benefits/drawbacks of OSS.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Benefits\%20and\%20Drawbacks.pdf},
	author = {Morgan, Lorraine and Finnegan, Patrick}
}
@article {flosswp357,
	title = {Business models in FLOSS-based companies},
	year = {2007},
	month = {May},
	abstract = {The sustainability of Free/Libre/Open Source Software (FLOSS) has recently become an important aspect of the overall open source phenomenon, and as such has received a significant research attention. Since 1999, several articles addressed the role of licenses, communities and business models in FLOSS-based companies, but mostly from a theoretical point of view. In this article, we present the result of a detailed analysis of 80 FLOSS-based companies and business models, using publicly available data on service offers, mailing list archives, online articles and when available public financial data. The result is a simplified and effective classification that can be used as a guide to companies willing to offer services in the same area, and an analysis on how the community process is influenced by the choice of licensing and business model.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OSSEMP07-daffara.pdf},
	author = {Carlo Daffara}
}
@conference {673,
	title = {Can Knowledge Management be Open Source?},
	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 = {59 - 70},
	publisher = {Springer},
	organization = {Springer},
	chapter = {5},
	abstract = {As we move further into a knowledge economy where collaboration and innovation are increasingly central to organisational effectiveness, enterprises need to pay more attention to the informal networks that exist within the organisation. Wikis may provide a more appropriate knowledge management capability and environment to capture tacit knowledge. Where traditional organisational cultures see that knowledge management must be tightly protected, Wikis opt for an open source approach where knowledge is shared and distributed for innovation to continue. This paper aims to explicate more participatory organisational processes of creation, accumulation and maintenance of knowledge. It uses Activity Theory as a framework to describe the components of an activity system where a Wiki is a tool mediating employee-based knowledge management activities and thereby democratising organisational knowledge.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Can\%20Knowledge\%20Management.pdf},
	author = {Pfaff, Charmaine and Hasan, Helen}
}
@conference {629,
	title = {Community Structure, Individual Participation and the Social Construction of Merit},
	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 = {161 - 172},
	publisher = {Springer},
	organization = {Springer},
	chapter = {13},
	abstract = {FLOSS communities are often described as meritocracies. We consider merit as a social construction that structures the community as a whole by allocating prestige to its participants on the basis of what they do. It implies a hierarchy of the different activities (web maintenance, writing code, bug report...) within the project. We present a study based on the merging of two datasets. We analyze the archive of KDE mailing lists using a social network. We also use responses to a questionnaire of KDE participants. Results bring empirical evidences showing that this hierarchy structures the community of KDE by allocating more central position to participants with more prestigious activities. We also show that this hierarchy structures individuals participation by giving greater {\textquotedblleft}membership esteem{\textquotedblright} to members involved in more prestigious activities.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_13},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Community\%20Structure\%20Individual.pdf},
	author = {Studer, Matthias}
}
@conference {1005,
	title = {Comparing Approaches to Mining Source Code for Call-Usage Patterns},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {20 - 20},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Two approaches for mining function-call usage patterns from source code are compared. The first approach, itemset mining, has recently been applied to this problem. The other approach, sequential-pattern mining, has not been previously applied to this problem. Here, a call-usage pattern is a composition of function calls that occur in a function definition. Both approaches look for frequently occurring patterns that represent standard usage of functions and identify possible errors. Itemset mining produces unordered patterns, i.e., sets of function calls, whereas, sequential-pattern mining produces partially ordered patterns, i.e., sequences of function calls. The trade-off between the additional ordering context given by sequential-pattern mining and the efficiency of itemset mining is investigated. The two approaches are applied to the Linux kernel v2.6.14 and results show that mining ordered patterns is worth the additional cost.},
	keywords = {function calls, functions, kernel, linux, sequence, sequencing, sequential-pattern mining},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300020.pdf},
	author = {Kagdi, Huzefa and Collard, Michael L. and Maletic, Jonathan I.}
}
@conference {648,
	title = {Context-Dependent Evaluation Methodology for 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 = {301 - 306},
	publisher = {Springer},
	organization = {Springer},
	chapter = {32},
	abstract = {Many evaluation methodologies have been proposed to mitigate the risks of choosing Open Source Software as an effective solution to an enterprise{\textquoteright}s problem. This work extracts the shared traits from the most important and widely known evaluation models, and re-applies them to create a new methodology. This methodology has been designed both to be used for the creation of a common knowledge base, and to be specialized for application in the context of the particular breed of small and medium-size enterprises found on the Italian ground.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_32},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Context-Dependent\%20Evaluation.pdf},
	author = {Cabano, Michele and Monti, Cesare and Piancastelli, Giulio}
}
@conference {626,
	title = {Corporate Involvement of Libre Software: Study of Presence in Debian Code over Time},
	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 = {121 - 132},
	publisher = {Springer},
	organization = {Springer},
	chapter = {10},
	abstract = {Although much of the research on the libre (free, open source) phenomenon has been focused on the involvement of volunteers, the role of companies is also important in many projects. In fact, during the last years, the involvement of companies in the libre software world seems to be raising. In this paper we present an study that shows, quantitatively, how important this involvement is in the production of the largest collection of code available for Linux: the Debian GNU/Linux distribution. By studying copyright attributions in source code, we have identified those companies with more attributed code, and the trend of corporate presence in Debian from 1998 to 2004.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_10},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Corporate\%20Involvement\%20of\%20Libro.pdf},
	author = {Gregorio Robles and Due{\~n}as, Santiago and Gonzalez-Barahona, Jesus}
}
@conference {996,
	title = {Correlating Social Interactions to Release History during Software Evolution},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {7 - 7},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {In this paper, we propose a method to reason about the nature of software changes by mining and correlating discussion archives. We employ an information retrieval approach to find correlation between source code change history and history of social interactions surrounding these changes. We apply our correlation method on two software systems, LSEdit and Apache Ant. The results of these exploratory case studies demonstrate the evidence of similarity between the content of free-form text emails among developers and the actual modifications in the code. We identify a set of correlation patterns between discussion and changed code vocabularies and discover that some releases referred to as minor should instead fall under the major category. These patterns can be used to give estimations about the type of a change and time needed to implement it.},
	keywords = {ant, apache, change management, developers, discussion, effort estimation, lsedit, mailing lists, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300007.pdf},
	author = {Baysal, Olga and Malton, Andrew J.}
}
@article {springerlink:10.1007/s10588-006-9006-3,
	title = {Correlating temporal communication patterns of the Eclipse open source community with performance and creativity},
	journal = {Computational \&amp; Mathematical Organization Theory},
	volume = {13},
	year = {2007},
	note = {"Social network data was collected from the Eclipse component development groups{\textquoteright} online mailing lists by using the online process tool (Gloor and Zhao, 2004). Data on bugs and enhancements for each group was collected from the Eclipse bugzilla database (Eclipse bugzilla, 2004). The social network data was analyzed with the TeCFlow tool (Gloor and Zhao, 2004)."
"The study is based on data from the three main projects of the Eclipse open source development community, namely {\textquotedblleft}eclipse{\textquotedblright}, {\textquotedblleft}tools{\textquotedblright} and {\textquotedblleft}technology{\textquotedblright}. We have chosen thirty-three different component development groups for analysis."
"The online process tool (online process tool, 2004) was utilized to collect communication data from their mailing list archives. The online process tool runs a robot that searches for URLs in the projects{\textquoteright} mailing list archives to compile a list of the possible URL links. It then extracts communication data as tuples in the form of {\textquotedblleft}sender, receiver, communication type, timestamp, communication contents{\textquotedblright} and stores it in the database. Further, bugs and enhancement data were collected from the Eclipse bugzilla database."},
	pages = {17-27},
	publisher = {Springer Netherlands},
	abstract = {This paper studies the temporal communication patterns of online communities of developers and users of the open source Eclipse Java development environment. It measures the productivity of each community and seeks to identify correlations that exist between group communication characteristics and productivity attributes. The study uses the TeCFlow (Temporal Communication Flow) visualizer to create movie maps of the knowledge flow by analyzing the publicly accessible Eclipse developer mailing lists as an approximation of the social networks of developers and users. Thirty-three different Eclipse communities discussing development and use of components of Eclipse such as the Java Development Tools, the different platform components, the C/C++ Development Tools and the AspectJ extension have been analyzed over a period of six months. The temporal evolution of social network variables such as betweenness centrality, density, contribution index, and degree have been computed and plotted. Productivity of each development group is measured in terms of two indices, namely performance and creativity. Performance of a group is defined as the ratio of new bugs submitted compared with bugs fixed within the same period of time. Creativity is calculated as a function of new features proposed and implemented. Preliminary results indicate that there is a correlation between attributes of social networks such as density and betweenness centrality and group productivity measures in an open source development community. We also find a positive correlation between changes over time in betweenness centrality and creativity, and a negative correlation between changes in betweenness centrality and performance.},
	keywords = {bug fixing, bugs, bugzilla, communication, creativity, developers, eclipse, email, email archives, feature requests, mailing lists, performance, productivity},
	issn = {1381-298X},
	url = {http://dx.doi.org/10.1007/s10588-006-9006-3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/16.pdf},
	author = {Kidane, Yared and Gloor, Peter}
}
@conference {882,
	title = {Creating, Destroying, and Restoring Value in Wikipedia},
	booktitle = {Conference on Supporting Group Work},
	year = {2007},
	author = {Reid Priedhorsky and Jilin Chen and Shyong K. Lam and Katherine Panciera and Loren Terveen and John Riedl}
}
@article {flosswp371,
	title = {The Creation of the Entrepreneurial Spirit and the Formation Of Alliances With Africa},
	year = {2007},
	month = {January},
	abstract = {The paper argues that there are internal governance problems within the African polity which need to be resolved before a successful creation of entrepreneurial alliances between Africa and the rest of the world. It also argues that past issues such as colonialism and imperialism pale into insignificance particularly among the new generation if they observe the absence of ethics among the current political leadership in the continent. There is also some discussion about the need for the developed world, notwithstanding the internal continental problems, to brush up its act in relation to the formation of alliances in Africa. Finally the paper argues the formation of alliances with Africa should not be limited to the traditioanl alliance partners of Europe and the America, but be flexible enough to allow new entrants such as China and India.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/WITTENBERG.pdf},
	author = {Jabulani Mzaliya}
}
@conference {658,
	title = {Data and analyses sharing to support research on free/libre open source software},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {355 - 356},
	publisher = {Springer},
	organization = {Springer},
	chapter = {42},
	abstract = {Research on FLOSS has relied on several different kinds of scientific evidence, such as the archives created by the FLOSS developers, versioned code repositories, mailing list messages and bug and issue tracking repositories [1]. FLOSS teams retain and make public archives of many of their activities as by-products of their open technology-supported collaboration. However, the easy availability of primary data provides a misleading picture of ease of conducting research on FLOSS. Precisely because these data are by-products, they are generally not in a form that is useful for researchers. Instead potentially useful data is locked up in HTML pages, CVS log files, text-only mailing list archives or dumps of website databases. FLOSS research projects, therefore, expend significant energy collecting and re-structuring these archives for their research, which is repetitive and wasteful [2]. Furthermore, different researchers will extract different data at different points in time, take different approaches to processing and cleaning data and make different decisions about analyses, but without all of these decisions being visible, auditable or reproducible. In principle, these latter problems can be addressed by individual researchers better documenting what they have done. However, research publications typically have restrictions on publication lengths that make complete discussion impossible. Furthermore, published papers are just the tip of the iceberg, and knowing what others have done does not necessarily make it any easier to replicate the results.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_42},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Data\%20and\%20analyses\%20sharing.pdf}
}
@proceedings {118,
	title = {Design architecture, developer networks and performance of open source software projects},
	year = {2007},
	keywords = {NotreDameArchive},
	author = {Xiang Liu and Bala Iyer}
}
@conference {1011,
	title = {Detecting Patch Submission and Acceptance in OSS Projects},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {26 - 26},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {The success of open source software (OSS) is completely dependent on the work of volunteers who contribute their time and talents. The submission of patches is the major way that participants outside of the core group of developers make contributions. We argue that the process of patch submission and acceptance into the codebase is an important piece of the open source puzzle and that the use of patch-related data can be helpful in understanding how OSS projects work. We present our methods in identifying the submission and acceptance of patches and give results and evaluation in applying these methods to the Apache webserver, Python interpreter, Postgres SQL database, and (with limitations) MySQL database projects. In addition, we present valuable ways in which this data has been and can be used.},
	keywords = {apache, contributions, mysql, patches, postgresql, python, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300026.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem}
}
@conference {992,
	title = {Determining Implementation Expertise from Bug Reports},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {2 - 2},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {As developers work on a software product they accumulate expertise, including expertise about the code base of the software product. We call this type of expertise "implementation expertise". Knowing the set of developers who have implementation expertise for a software product has many important uses. This paper presents an empirical evaluation of two approaches to determining implementation expertise from the data in source and bug repositories. The expertise sets created by the approaches are compared to those provided by experts and evaluated using the measures of precision and recall. We found that both approaches are good at finding all of the appropriate developers, although they vary in how many false positives are returned.},
	keywords = {bug reports, developers, eclipse, expertise, repository, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300002.pdf},
	author = {Anvik, John and Murphy, Gail C.}
}
@conference {639,
	title = {Different Bug Fixing Regimes? A Preliminary Case for Superbugs},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {247 - 252},
	publisher = {Springer},
	organization = {Springer},
	chapter = {23},
	abstract = {The paper investigates the processes by which bugs are fixed in open-source software projects. Focusing on Mozilla and combining data from both its bug tracker (Bugzilla) and from its CVS, we suggest that: a) Some bugs resist beyond the first patch applied to the main branch of the source code in relation to them, which we denote as superbugs; b) There might exist different bug fixing regimes; c) priority and severity flags as defined in bug repositories are not optimized for superbugs and might lead to a involuntary side effects; d) The survival time of superbugs is influenced by the nature of the discussions within Bugzilla, by bug dependencies and by the provision of contextual elements.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Different\%20Bug\%20Fixing\%20Regimes.pdf},
	author = {Jean-Michel Dalle and den Besten, Matthijs}
}
@article {flosswp332,
	title = {Do firms take part in the projects of the OS community. Some preliminary evidence and a research agenda},
	year = {2007},
	month = {January},
	abstract = {The Open Source (OS) software has progressively gained economic importance in recent years, and more and more commercial firms are getting involved, to various extents, in the OS movement. While a number of studies have investigated motivations and business models of OS-based software companies, very few works have examined whether and how firms actively participate to open projects. This paper contributes to the literature by providing empirical evidence on the role and the activities of software houses in community developed projects. The research also proposes an original methodology of large-scale primary data collection from OS project repositories and linked Web sites. The findings show how different today???s OS movement is from its origins and how important firm involvement has become, not only numerically but also for the deepness of its impact on community projects. Finally, further research developments are suggested.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper_firm_involvement_MIT.pdf},
	author = {Andrea Bonaccorsi and Dario Lorenzi and Monica Merito and Cristina Rossi}
}
@article {flosswp350,
	title = {Dragging developers towards the core. How the Free/Libre/Open Source Software community enhances developers{\textquoteright} contribution},
	year = {2007},
	month = {January},
	abstract = {The paper presents a dynamic perspective on the landscape of Free/Libre/Open Source Software (FLOSS) developers{\textquoteright} motivations and tries to isolate mechanisms sustaining developers{\textquoteright} contribution over time. The first part of the paper uses data gathered by the empirical studies relative to the FLOSS case to judge the relative importance of each group of incentives detected by the literature. In the second part of the paper, the same data are used to further characterize developers{\textquoteright} motivations in dynamics terms, showing how the relative importance of different incentives changes over time. Drawing inspiration from these results, the third part of the paper identifies a specific mechanism fostering developers{\textquoteright} contribution to the community activities, namely that: "Independently of developers{\textquoteright} exogenous preferences, the more their exposure to the FLOSS community social environment, the more their contribution to the community activities". The key point of this hypothesis is that, if the exposure to the FLOSS community social environment is able to foster developers{\textquoteright} contribution beyond the level granted by their predetermined preferences, this leads directly to the evidence that the FLOSS community is provided with a mechanism sustaining and enhancing developers{\textquoteright} incentives to produce and diffuse code. In the last part of the paper, data relative to 14,497 developers working on SourceForge.net during two years (2001-2002) are employed to estimate a model testing the aforementioned hypothesis. Endogeneity problems are explicitly accounted for, and robustness checks are performed in order to make sure that the observed confirmation of the hypothesis is actually an empirically grounded result.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rullani_socenv.pdf},
	author = {Francesco Rullani}
}
@article {flosswp348,
	title = {Dual Licensing in Open Source Software Markets},
	year = {2007},
	month = {May},
	abstract = {Dual licensing has proved to be a sustainable business model for various commercial software vendors employing open source strategies. In this paper we study the main characteristics of dual licensing and under which conditions it represents a profitable commercial strategy. We show that dual licensing is a form of versioning, whereby the software vendor uses the open source licensing terms in order to induce commercial customers to select the proprietary version of the software. Furthermore, we show that the software vendor prefers dual licensing to a fully proprietary strategy when the customers are very sensitive to the reciprocal terms of the open source license.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dual_lic.pdf},
	author = {Stefano Comino and Fabio M. Manenti}
}
@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}
}
@conference {669,
	title = {FOCSE: An OWA-based Evaluation Framework for OS Adoption in Critical Environments},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	pages = {3-16},
	publisher = {Springer},
	organization = {Springer},
	chapter = {1},
	abstract = {While the vast majority of European and US companies increasingly use open source software for non-key applications, a much smaller number of companies have deployed it in critical areas such as security and access control. This is partly due to residual difficulties in performing and documenting the selection process of open source solutions. In this paper we describe the FOCSE metrics framework, supporting a specific selection process for security-related open source code. FOCSE is based on a set of general purpose metrics suitable for evaluating open source frameworks in general; however, it includes some specific metrics expressing security solutions{\textquoteright} capability of responding to continuous change in threats. We show FOCSE at work in two use cases about selecting two different types of security-related open source solutions, i.e. Single Sign-On and Secure Shell applications.
 },
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FOCSE\%20\%20an\%20\%20OWA.pdf},
	author = {Ardagna, Claudio and Damiani, Ernesto and Frati, Fulvio}
}
@conference {1017,
	title = {Forecasting the Number of Changes in Eclipse Using Time Series Analysis},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {32 - 32},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {In order to predict the number of changes in the following months for the project Eclipse, we have applied a statistical (non-explanatory) model based on time series analysis. We have obtained the monthly number of changes in the CVS repository of Eclipse, using the CVSAnalY tool. The input to our model was the filtered series of the number of changes per month, and the output was the number of changes per month for the next three months. Then we aggregated the results of the three months to obtain the total number of changes in the given period in the challenge.},
	keywords = {change management, cvs, cvsanaly, eclipse, prediction},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.10},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300032.pdf},
	author = {Herraiz, Israel and Jesus M. Gonzalez-Barahona and Gregorio Robles}
}
@conference {668,
	title = {FOSLET 07 {\textemdash} Workshop on Free and Open Source Learning Environments and Tools},
	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 = {385 - 387},
	publisher = {Springer},
	organization = {Springer},
	chapter = {52},
	abstract = {Web-based Learning Environments supported by Course Management Systems (also known as Learning Management Systems) are nowadays a valid solution for institutions, companies, schools and universities that deliver eLearning or support blended-learning activities. Learning Environments are used to distribute information and content material to learners, prepare and deliver assignments and tests, engage in discussions, and manage distance classes without time and space restrictions.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_52},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FOSLET\%2007\%20workshop.pdf},
	author = {Botturi, Luca and Mazza, Riccardo and Tardini, Stefano}
}
@booklet {491,
	title = {Free/libre open source software implementation in schools: Evidence from the field and implications for the future},
	year = {2007},
	month = {Sept},
	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 to support the needs of local users better. This also allows users to participate more proactively in the development and implementation process of a FLOSS-based system. 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/Lin\%26Zini.pdf},
	author = {Yu-wei Lin and Enrico Zini}
}
@conference {640,
	title = {Free/Open Services: Conceptualization, Classification, and Commercialization},
	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 = {253 - 258},
	publisher = {Springer},
	organization = {Springer},
	chapter = {24},
	abstract = {The concept of Free/Open Services (F/O-Services) emerges by bringing together services with Free/Open Source Software (FOSS). F/O-Services enable the creation of transparent composite services collectively and allow people and other services to access them. This paper extends the concept of F/O-Services beyond the level of open interfaces, analyzing the associated licensing interpretations and exploring the notion of open service dependencies. Further, the paper overviews the business models for F/O-Services as a part of this social mechanism of exchange.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_24},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Free\%20Open\%20Services.pdf},
	author = {Gangadharan, G. and D{\textquoteright}Andrea, Vincenzo and Weiss, Michael}
}
@conference {653,
	title = {Free/Open Source Software Adoption, Public Policies and Development Indicators: An International Comparison},
	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 = {331 - 336},
	publisher = {Springer},
	organization = {Springer},
	chapter = {37},
	abstract = {Despite the growing body of research on the inner workings of FOSS development, there are few studies on its relation with broader developments in society. In this study we have attempted a preliminary investigation of (1) how FOSS prevalence is related to economic and human development indicators of countries, (2) whether public policies regarding FOSS emerge in a consistent relation with these indicators in several clusters of countries constructed from the United Nation{\textquoteright}s human development index, and (3) the relation of software piracy to development indicators. Our results point to relative significance of non-economic factors in FOSS adoption, lack of consistent policies among public agencies, and irrelevance of non-economic factors on software piracy. In addition, the study demonstrates the possibility of developing FOSS indices for larger scale diagnosis and strategizing.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Free\%20OSS\%20Adoption.pdf},
	author = {Schmidbauer, Harald and Gen{\c c}er, Mehmet and Tunal{\i}o_lu, Vehbi}
}
@conference {878,
	title = {Free/Open Source Software Development: Recent Research Results and Emerging Opportunities},
	booktitle = {Proc. European Software Engineering Conference and ACM SIGSOFT Symposium on the Foundations of Software Engineering},
	year = {2007},
	publisher = {ACM},
	organization = {ACM},
	address = {Dubrovnik, Croatia},
	author = {Walt Scacchi}
}
@inbook {879,
	title = {Free/Open Source Software Development: Recent Research Results and Methods},
	booktitle = { Advances in Computers},
	volume = {69},
	year = {2007},
	pages = {243-295},
	author = {Walt Scacchi},
	editor = {Zelkowitz, M.V.}
}
@article {flosswp373,
	title = {From Exchange to Contributions: Generalizing Peer Production into the Physical World},
	year = {2007},
	month = {October},
	abstract = {Peer production is a new mode of production that has emerged in the areas of software and content production during the last decades {\textendash} a mode of production based on sharing and cooperation. We discuss whether and how peer production can be extended into the realm of physical production and whether a society is possible in which peer production is the primary mode of production. We investigate which problems need to be solved for the generalization of peer production and how they can be addressed in the context of individual peer projects as well as society as a whole. Our findings indicate there is no inherent reason for peer production to remain limited to the sphere of information. We analyze how we may expect a society whose economy is based on free cooperation in a multitude of peer projects to work and how such a society compares with societies based on market production or planned production. We show that the differences are striking, and that such a peer economy would grant people an unprecedented amount of control over their own lives, while avoiding the unpleasant effects of other modes of production.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/peer-economy.pdf},
	author = {Christian Siefkes}
}
@article {76,
	title = {From planning to mature: On the success of open source projects},
	journal = {Research Policy},
	volume = {36},
	year = {2007},
	note = {Times Cited: 0},
	pages = {1575-1586},
	abstract = {Open source is an example of user-centric innovation initiated by an individual or group of users to satisfy their specific needs; the more a software evolves towards a stable release able to address the requirements of its developers, the more successful the project. In this paper we use a large data-set obtained from SourceForge.net to estimate the relationship between a series of different characteristics of OS projects and the probability of evolution of the source code from a preliminary release to a mature version. We show that while projects distributed under highly restrictive licensing terms (GPL) have a significantly smaller probability of reaching a stable release, applications towards sophisticated users have a larger probability of evolving in the development status. Interestingly, we find that the size of the "community of developers" increases the chances of progress but this effect decreases as the community gets larger, a signal of possible coordination problems. (C) 2007 Elsevier B.V. All rights reserved.},
	author = {Stefano Comino and Fabio M. Manenti and Parisi, M. L.}
}
@conference {671,
	title = {From the Cathedral to the Bazaar: An Empirical Study of the Lifecycle of Volunteer Community Projects},
	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 = {31 - 44},
	publisher = {Springer},
	organization = {Springer},
	chapter = {3},
	abstract = {Some free software and open source projects have been extremely successful in the past. The success of a project is often related to the number of developers it can attract: a larger community of developers (the {\textquoteleft}bazaar{\textquoteright}) identifies and corrects more software defects and adds more features via a peer-review process. In this paper two free software projects (Wine and Arla) are empirically explored in order to characterize their software lifecycle, development processes and communities. Both the projects show a phase where the number of active developers and the actual work performed on the system is constant, or does not grow: we argued that this phase corresponds to the one termed {\textquoteleft}cathedral{\textquoteright} in the literature. One of the two projects (Wine) shows also a second phase: a sudden growing amount of developers corresponds to a similar growing output produced: we termed this as the {\textquoteleft}bazaar{\textquoteright} phase, and we also argued that this phase was not achieved for the other system. A further analysis revealed that the transition between {\textquoteleft}cathedral{\textquoteright} and {\textquoteleft}bazaar{\textquoteright} was a phase by itself in Wine, achieved by creating a growing amount of new modules, which attracted new developers.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/From\%20the\%20Cathedral.pdf},
	author = {Capiluppi, Andrea and Martin Michlmayr}
}
@article {497,
	title = {The functioning of a free software community: entanglement of three regulation modes - control, autonomous, and distributed},
	journal = {Science Studies},
	number = {2},
	year = {2007},
	abstract = {This paper consider FLOSS communities as ""going concerns"" which necessitate a minimum of order and common, shared, social rules to function. Through an in-depth and diachronic analysis of the Spip project, we present two classical modes of social regulation: a control regulation centred on the product and an autonomous regulation reflecting the differentiated commitments. Our data shows that the meaning, value and legitimacy of contributors{\textquoteright} involvements are defined and rated more collectively, through exchanges, judgments, and evaluations. A third regulation mode, called distributed community regulation and aimed at creating and transforming shared rules that produces recognition and stratification, is then presented.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Science_Studies_02-2007-Demaziere_Horn_Zune.pdf},
	author = {Didier Demazi{\`e}re and Francois Horn and Marc Zune}
}
@article {75,
	title = {Global and Temporal Analysis of Social Positions at SourceForge. net},
	journal = {Third International Conference on Open Source Systems, IFIP WG},
	volume = {2},
	year = {2007},
	author = {Christley, S. and Madey, G.}
}
@conference {642,
	title = {Guiding the Discovery of Open Source Software Processes with a Reference Model},
	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 = {265 - 270},
	publisher = {Springer},
	organization = {Springer},
	chapter = {26},
	abstract = {This paper describes a reference model for open source software (OSS) processes and its application towards discovering such processes from OSS project artifacts. This reference model is the means to map evidence of an enacted process to a classification of agents, resources, tools, and activities that characterize the process.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_26},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Guiding\%20the\%20Discovery.pdf},
	author = {Chris Jensen and Walt Scacchi}
}
@conference {991,
	title = {How Long Will It Take to Fix This Bug?},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {1},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Predicting the time and effort for a software problem has long been a difficult task. We present an approach that automatically predicts the fixing effort, i.e., the person-hours spent on fixing an issue. Our technique leverages existing issue tracking systems: given a new issue report, we use the Lucene framework to search for similar, earlier reports and use their average time as a prediction. Our approach thus allows for early effort estimation, helping in assigning issues and scheduling stable releases. We evaluated our approach using effort data from the JBoss project. Given a sufficient number of issues reports, our automatic predictions are close to the actual effort; for issues that are bugs, we are off by only one hour, beating naive predictions by a factor of four.},
	keywords = {bug fixing, bug reports, effort estimation, jboss, lucene, prediction, time},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.13},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300001.pdf},
	author = {Weiss, Cathrin and Premraj, Rahul and Zimmermann, Thomas and Zeller, Andreas}
}
@conference {660,
	title = {How to Gather FLOSS Metrics},
	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 = {361 - 362},
	publisher = {Springer},
	organization = {Springer},
	chapter = {44},
	abstract = {In this half-day tutorial, participants will gain hands-on exposure to key technologies for data collection about open source projects.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_44},
	attachments = {https://flosshub.org/sites/flosshub.org/files/How\%20to\%20gather\%20Floss\%20Metrics.pdf},
	author = {Conklin, Megan and Gonzalez-Barahona, Jesus and Gregorio Robles}
}
@conference {1001,
	title = {Identifying Changed Source Code Lines from Version Repositories},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {14 - 14},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Observing the evolution of software systems at different levels of granularity has been a key issue for a number of studies, aiming at predicting defects or at studying certain phenomena, such as the presence of clones or of crosscutting concerns. Versioning systems such as CVS and SVN, however, only provide information about lines added or deleted by a contributor: any change is shown as a sequence of additions and deletions. This provides an erroneous estimate of the amount of code changed.

This paper shows how the evolution of changes at source code line level can be inferred from CVS repositories, by combining information retrieval techniques and the Levenshtein edit distance. The application of the proposed approach to the ArgoUML case study indicates a high precision and recall.},
	keywords = {argouml, cvs, levenshtein, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.14},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300014.pdf},
	author = {Canfora, Gerardo and Cerulo, Luigi and Di Penta, Massimiliano}
}
@article {1416,
	title = {Identifying Success and Abandonment of Free/Libre and Open Source (FLOSS) Commons: A Preliminary Classification of Sourceforge.net projects},
	journal = {Upgrade: The European Journal for the Informatics Professional},
	volume = {VIII},
	year = {2007},
	pages = {54-59},
	abstract = {Free/Libre and Open Source Software (FLOSS) projects are a form of commons where individuals work collectively to produce software that is a public, rather than a private, good. The famous phrase {\textquotedblleft}Tragedy of the Commons{\textquotedblright} describes a situation where a natural resource commons, such as a pasture, or a water supply, gets depleted because of overuse. The tragedy in FLOSS commons is distinctly different: It occurs when collective action ceases before a software product is produced or reaches its full potential. This paper builds on previous work about defining success in FLOSS projects by taking a collective action perspective. We first report the results of interviews with FLOSS developers regarding our ideas about success and failure in FLOSS projects. Building on those interviews and previous work, we then describe our criteria for defining success/tragedy in FLOSS commons. Finally, we discuss the results of a preliminary classification of nearly all projects hosted on Sourceforge.net as of August 2006.},
	keywords = {flossmole, sourceforge, success},
	url = {http://www.cepis.org/upgrade/files/full-VI-07.pdf},
	author = {English, R. and Schweik, C. M.}
}
@article {94,
	title = {Identifying Success and Tragedy of FLOSS Commons: A Preliminary Classification of Sourceforge. net Projects},
	journal = {Emerging Trends in FLOSS Research and Development, 2007. FLOSS{\textquoteright}07. First International Workshop on},
	year = {2007},
	pages = {11-11},
	author = {English, R. and Schweik, C. M.}
}
@conference {1013,
	title = {Impact of the Creation of the Mozilla Foundation in the Activity of Developers},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {28 - 28},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {During 2003, the Mozilla project transitioned from company-promoted (sponsored by AOL) to community-promoted (sponsored by the Mozilla Foundation). What happened to the group of developers during this transition? There was any significant impact on its activity or composition? To answer these questions, we have performed an analysis of the CVS repository of Mozilla, using the CVSAnalY tool, finding little on activity, but dramatic changes in the the composition of the development team.},
	keywords = {cvs, cvsanaly, developers, mining challenge, mozilla, msr challenge, revision history},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.15},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300028.pdf},
	author = {Jesus M. Gonzalez-Barahona and Gregorio Robles and Herraiz, Israel}
}
@article {hoepman2007increased,
	title = {Increased security through open source},
	journal = {Communications of the ACM},
	volume = {50},
	number = {1},
	year = {2007},
	pages = {79{\textendash}83},
	publisher = {ACM},
	abstract = {The last few years have shown a worldwide rise in the attention for, and
actual use of, open source software (OSS), most notably of the operating
system Linux and various applications running on top of it. Various major
companies and governments are adopting OSS. As a result, there are many
publications concerning its advantages and disadvantages. The ongoing discussions
cover a wide range of topics, such as Windows versus Linux, cost
issues, intellectual property rights, development methods, etc. Here we wish
to focus on security issues surrounding OSS. It has become a reasonably
well-established conviction within the computer security community that
publishing designs and protocols contributes to the security of systems built
on them. But should one go all the way and publish source code as well?
That is the fundamental question that we wish to address in this paper.},
	keywords = {security},
	url = {https://arxiv.org/pdf/0801.3924.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/0801.3924.pdf},
	author = {Hoepman, Jaap-Henk and Jacobs, Bart}
}
@conference {632,
	title = {Influence in the Linux Kernel Community},
	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 = {203 - 208},
	publisher = {Springer},
	organization = {Springer},
	chapter = {16},
	abstract = {Several success stories of open source (OS) products have been seen during last decade. Due to the economical importance of the products, it is important to know who are the ones who have the largest influence to the products. Is there a dominant player in developing communities? In this paper1 the aspect is studied with respect to the Linux Kernel community. We show that the influence is centered to a small number of core people, and corporates have a large impact to the development. Moreover, we enumerate the most influential companies.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_16},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Influence\%20in\%20the\%20Linux\%20Kernel.pdf},
	author = {Aaltonen, Timo and Jokinen, Jyke}
}
@article {flosswp380,
	title = {Information Policies and Open Source Software in Developing Countries},
	journal = {Journal of American Society of Information Science and Technology},
	volume = {58},
	number = {1},
	year = {2007},
	month = {January},
	pages = {121{\textendash}132},
	abstract = {Many authors propose that open source software (OSS) is a good strategy to bring information and communication technologies to developing countries. Nevertheless, the use of OSS needs to be more than just adopting Linux as the standard for operating systems. Adoption of OSS is not only a choice of software, but also a means of acquiring knowledge. Developing countries have to use OSS as a way to gain knowledge about the technology itself and as a way of creating technology products that fit their specific needs. In this article, the authors introduce a model of OSS based on its essential characteristics to understand how developing countries may use OSS to achieve their development goals. The authors argue that there are two defining properties of any open source software. The first property is the potential for shared conceptualization and the second is the potential for modularity. By assessing how each OSS project satisfies these two conditions, a taxonomy is built for open source projects. This taxonomy will help the development of more sensible policies to promote the use of open source in developing countries.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/camara_fonseca_OSS_developing_countries.pdf},
	author = {Gilberto C{\^a}mara and Frederico Fonseca}
}
@article {flosswp329,
	title = {Information Policies and Open Source Software in Developing Countries},
	year = {2007},
	month = {January},
	abstract = {Many authors propose that open source software (OSS) is a good strategy to bring information and communication technologies to developing countries. Nevertheless, the use of OSS needs to be more than just adopting Linux as the standard for operating systems. Adoption of OSS is not only a choice of software, but also a means of acquiring knowledge. Developing countries have to use OSS as a way to gain knowledge about the technology itself and as a way of creating technology products that fit their specific needs. In this article, the authors introduce a model of OSS based on its essential characteristics to understand how developing countries may use OSS to achieve their development goals. The authors argue that there are two defining properties of any open source software. The first property is the potential for shared conceptualization and the second is the potential for modularity. By assessing how each OSS project satisfies these two conditions, a taxonomy is built for open source projects. This taxonomy will help the development of more sensible policies to promote the use of open source in developing countries.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/camara_fonseca_jasist_oss_submission_jan06.pdf},
	author = {Gilberto C{\^a}mara and Frederico Fonseca}
}
@conference {625,
	title = {Innovation in Open Source Software Development: A Tale of Two Features},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	note = {"archives of project discussion forums were then examined to determine when the feature was first proposed, how it was debated, and when it was ultimately adopted"},
	month = {2007///},
	pages = {109 - 120},
	publisher = {Springer},
	organization = {Springer},
	chapter = {9},
	abstract = {Open Source Software Development appears to depart radically from conventional notions of software engineering. In particular, requirements for Open Source projects seem to be asserted rather than elicited. This paper examines two features of selected open source products: {\textquotedblleft}tabbed browsing{\textquotedblright} as realized in the Firefox web browser, and {\textquotedblleft}edge magnetism{\textquotedblright} found in the Gnome desktop environment{\textquoteright}s Metacity window manager. Using archives of mailing lists and issue tracking databases, these features were traced from first mention to release, in attempt to discover the process by which requirements are proposed, adopted, and implemented in their respective Open Source projects. The results confirm the importance of user participation in Open Source projects.
},
	keywords = {email, email archives, features, Firefox, gnome, mailing list, metacity, mozilla},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Innovation\%20in\%20OSS.pdf},
	author = {Noll, John}
}
@booklet {488,
	title = {Innovativeness of software solutions: evidence from an alternative methodology. Comparing Free/Open Source and proprietary products},
	year = {2007},
	month = {Dec},
	abstract = {The issue of innovation processes taking place in the software sector  is currently widely debated. Challenging questions arise about what products/services have to be considered innovative, and whether a specific artefact is innovative or not. In this framework, the widespread success of the Free/Open Source Software (FOSS) put forward new research issues, dealing with whether and how programs developed according to the new production paradigm turn out to be more innovative than traditional ones. In this framework, this paper aims at contributing to the literature by addressing three main research questions: (i) are software solutions produced by Small and Medium Enterprises (SMEs) innovative? (ii) What kinds of innovations are implemented? And, finally, (iii) are programs based on FOSS more innovative than proprietary ones?Basing on a sample of 134 software solutions produced by Italian SMEs and using an original methodology to asses the problem of evaluating innovation in the software field, we provides some first insights of what emerges if we set aside the traditional innovation indicators and endower to build alternative metrics, specifically developed to target the complexity of the innovation processes in the software markets.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lorenzi_rossi_MIT_20071220.pdf , https://flosshub.org/sites/flosshub.org/files/Alexy_Henkel_-_Promoting_the_Penguin_-_SSRN.pdf},
	author = {Dario Lorenzi and Cristina Rossi}
}
@conference {650,
	title = {Introducing Usability Practices to OSS: The Insiders{\textquoteright} Experience},
	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 = {313 - 318},
	publisher = {Springer},
	organization = {Springer},
	chapter = {34},
	abstract = {This paper presents a case study of introducing usability practices to a small open source project called Carrot2. We describe our experiences from a point of view of an active Carrot2 developer, who is at the same time a usability enthusiast and practitioner. We perform a critical analysis of the system{\textquoteright}s original user interface and describe the steps we took to improve it. We also analyse the success factors and the impact of the whole redesign process.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_34},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Introducing\%20Usability\%20Practices.pdf},
	author = {Osi{\'n}ski, Stanis{\l}aw and Weiss, Dawid}
}
@conference {659,
	title = {Introduction to OSS 2007 Tutorial Program},
	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 = {359 - 360},
	publisher = {Springer},
	organization = {Springer},
	chapter = {43},
	abstract = {Today, most software researchers and professionals consider Open Source as a greatly successful paradigm for large-scale production of high-quality software systems. However, most of them would probably agree that successfully applying this paradigm requires dealing with a number of important issues. One of the best reasons to attend OSS conference series is being able to discuss these issues in an unprecedented gathering of top-notch researchers, developers, and leaders from all avenues of the open source movement. Attending good tutorials, in particular, is a great opportunity for getting in touch with new ideas and discussing them in depth with real experts.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_43},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Introduction\%20to\%20OSS\%202007.pdf},
	author = {Damiani, Ernesto}
}
@conference {656,
	title = {Introduction to Panel Discussions at the Third International Conference on Open Source Systems {\textemdash} OSS 2007},
	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 = {351 - 352},
	publisher = {Springer},
	organization = {Springer},
	chapter = {40},
	abstract = {Two diverse, stimulating and important panel discussions are included in this year{\textquoteright}s programme on open source systems. The first panel explores the diverse set of legal issues and risks that arise as governments increasingly adopt open source systems. Governments are attracted to open source software systems by the potential cost savings, open standards and protocols, and the flexibility, adaptability and reliability of the systems. However, there are serious legal issues and liabilities that can arise when governments adopt open source systems. This panel identifies and examines potential legal risks and liabilities from open source systems adoption in the government context. Some of the important legal concerns discussed by this panel include intellectual property rights, licensing, and protection of sensitive or confidential information. The second panel is organized as a debate in which the panelists will consider the advantages and disadvantages of the sharing of research data and analyses by open source systems researchers. The area of open source systems has attracted numerous researchers from many different disciplines. In part, the attraction of research on open source systems is due to the public information available about open source communities. Using this information, researchers have been uncovering fascinating insights about how open source systems are developed and used and how open source communities function. Unfortunately, as noted by this panel, the work products of this research are not readily available to the public. This prevents new researchers from validating, building upon and extending the research already conducted by others. However, making research work products available to the others, while potentially valuable, has associated disadvantages. For example, certain kinds of data collected by a researcher (such as surveys or other confidential information) may not be released to the public, given human subjects concerns. In addition, it can require substantial cost and effort on the part of the researcher to make research work products understandable and usable by others. This panel debates the issues surrounding the pros and cons of making open source systems research work products available to researchers.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_40},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Introduction\%20to\%20Panel\%20Discussions.pdf},
	author = {Sandra Slaughter}
}
@conference {663,
	title = {Introduction to Workshops at the Third International Conference on Open Source Systems {\textemdash} OSS 2007},
	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 = {369 - 369},
	publisher = {Springer},
	organization = {Springer},
	chapter = {47},
	abstract = {The International Conference on Open Source Systems owes its success to the increasing desire of researchers and academicians to engage in open conversation and sharing with the open source community regarding its{\textquoteright}motivations, products, processes and data. This diverse representation of the growing practical and academic interest in Open Source Systems and its impact on the software engineering community is represented in the five workshops that accompany this year{\textquoteright}s conference. OSS 2007 welcomes these workshops as participants engage, in an informal setting, driven by fundamental academic interests, or by more applied industrial or commercial interests to discuss technical issues, exchange research ideas, and to develop a community in the field of Open Source Software and/or Systems.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_47},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Introduction\%20\%20to\%20Workshops.pdf},
	author = {Hissam, Scott}
}
@article {126,
	title = {Investigating recognition-based performance in an open content community: A social capital perspective},
	journal = {Information \& Management},
	volume = {44},
	number = {3},
	year = {2007},
	note = {Times Cited: 0},
	month = {Apr},
	pages = {240-252},
	abstract = {As the open source movement grows, it becomes important to understand the dynamics that affect the motivation of participants who contribute their time freely to such projects. One important motivation that has been identified is the desire for formal recognition in the open source community. We investigated the impact of social capital in participants{\textquoteright} social networks on their recognition-based performance; i.e., the formal status they are accorded in the community. We used a sample of 465 active participants in the Wikipedia open content encyclopedia community to investigate the effects of two types of social capital and found that network closure, measured by direct and indirect ties, had a significant positive effect on increasing participants{\textquoteright} recognition-based performance. Structural holes had mixed effects on participants{\textquoteright} status, but were generally a source of social capital. (C) 2007 Elsevier B.V. All rights reserved.},
	keywords = {open content, recognition-based performance, social capital, social networks, social status, virtual communities},
	isbn = {0378-7206},
	author = {Okoli, C. and Oh, Wonseok}
}
@proceedings {149,
	title = {Investigating success of open source software projects: A social network perspective},
	year = {2007},
	keywords = {CollectedOwnData NoShare},
	author = {Jing Wu and Khim-Yong Goh and Qian Tang}
}
@proceedings {871,
	title = {Knowledge Work Artifacts: Kernel Cousins for Free/Open Source Software Development},
	year = {2007},
	month = {Nov 4-7},
	pages = {177-186},
	address = {Sanibel Island, FL},
	author = {Elliott, M. and Ackerman, Mark S. and Walt Scacchi}
}
@conference {637,
	title = {Learning and the imperative of production in Free/Open Source 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 = {235 - 240},
	publisher = {Springer},
	organization = {Springer},
	chapter = {21},
	abstract = {This paper examines the role of learning in structuring access and participation in F/OS communities. In particular it highlights the challenges and barriers to access faced by new developers and the expectations of senior developers regarding the mindsets and capabilities of new contributors. It is argued that learning in F/OS is inextricably connected with the demand for continuous production. The evidence presented is drawn from interviews conducted with inexperienced and experienced contributors from the GNOME and KDE projects. The author challenges the view of learning as an enculturation process and the paper contributes to the understanding of power relations among established and peripheral members in communities of practice.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_21},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Learning\%20and\%20the\%20imprative\%20of\%20production.pdf},
	author = {Evangelia Berdou}
}
@conference {646,
	title = {Learning Through Practical Involvement in the OSS Ecosystem: Experiences from a Masters Assignment},
	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 = {289 - 294},
	publisher = {Springer},
	organization = {Springer},
	chapter = {30},
	abstract = {Increased awareness of and interest in Open Source has led to a number of university teaching initiatives, at both national and European level. In this paper we present experiences from a practical assignment designed to give students on an Open Source Masters course an insight into real involvement in Open Source projects. It discusses the motivations for the assignment, and how it was set up and executed. It reports on post facto student feedback, and reflects on a parallel, reduced exercise offered at undergraduate level. We find that the learning experience was both positive and valuable in that it gave real insight into Open Source participation, and also encouraged further participation in Open Source projects by students after the course had completed.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_30},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Learning\%20through\%20practical\%20involvement.pdf},
	author = {Lundell, Bj{\"o}rn and Persson, Anna and Lings, Brian}
}
@conference {657,
	title = {Legal issues for free and open source software in government},
	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 = {353 - 354},
	publisher = {Springer},
	organization = {Springer},
	chapter = {41},
	abstract = {As more governments begin to adopt and release free and open source software, it is important to be able to readily recognise and identify the associated legal risks and potential liabilities. This panel will examine and discuss the most common of these associated risks and liabilities. These issues include, but are not limited to: 

  indemnities against claims of intellectual property  infringement from third parties
  requirements of consumer protection and antitrust legislation
  obligations to redistribute source, and when they arise
  enforceability of free software licences
  layering and combining of licences
  dual-licensing
  licence incompatibility
  software patent liability
  contemporary developments in software licensing
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_41},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Legal\%20Issues\%20for\%20Free\%20and\%20OSS.pdf},
	author = {Nic Suzor and Fitzgerald, Brian and Perry, Mark}
}
@conference {654,
	title = {Levels of Formality in FOSS Communities},
	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 = {337 - 342},
	publisher = {Springer},
	organization = {Springer},
	chapter = {38},
	abstract = {One of the aspects of Free and Open Source Software (FOSS) which may act as a significant deterrent to its adoption, is the method used to collaboratively develop the software and provide support through the use of communities. It is not until this method is examined more closely that its many advantages can be realised. The method can, however, seem very disorganised especially when compared with traditional proprietary development styles. A key difference between these two development approaches lies in the management of projects, and perhaps as a consequence, in the level of formality in the community environment.
This paper presents the results of empirical survey research investigating FOSS community participants{\textquoteright} views on the level of formality in FOSS, and the way in which this affects both development and support provision activities. The paper then concludes by analysing what can be learnt from the participant{\textquoteright}s views.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_38},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Levels\%20of\%20Formality.pdf},
	author = {Schofield, Andrew and Cooper, Grahame}
}
@conference {1018,
	title = {Local and Global Recency Weighting Approach to Bug Prediction},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {33 - 33},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Finding and fixing software bugs is a challenging maintenance task, and a significant amount of effort is invested by software development companies on this issue. In this paper, we use the Eclipse project{\textquoteright}s recorded software bug history to predict occurrence of future bugs. The history contains information on when bugs have been reported and subsequently fixed.},
	keywords = {bug fixing, bug reports, eclipse, maintenance, prediction},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.17},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300033.pdf},
	author = {Joshi, Hemant and Zhang, Chuanlei and Ramaswamy, S. and Bayrak, Coskun}
}
@article {flosswp378,
	title = {Love and other demons: game theory in enterpreneurial and love relationships},
	year = {2007},
	month = {December},
	abstract = {The article studies the risk aversion and information assymetry differences in two fields of relationships: between partners and in a loving couple.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ARTICULO_1-del_amor_y_otros_demonios-_teoria_de_juegos_en_las_relaciones_empresariales_y_amorosas.pdf},
	author = {Guillermo Flores and Alejandro Mendighetti and Jorge S{\'a}nchez}
}
@mastersthesis {482,
	title = {Managing the Bazaar: Commercialization and peripheral participation in mature, community-led Free/Open source software projects},
	year = {2007},
	month = {Nov},
	abstract = {The thesis investigates two fundamental dynamics of participation and collaboration in mature, community-led Free/Open Source (F/OS) software projects - commercialization and peripheral participation. The two primary case studies of the research are the GNOME and KDE communities.The thesis contributes insights into how the gift economy is embedded in the exchange economy and the role of peripheral contributors. The analysis indicates that community-integrated paid developers have a key role in project development, maintaining the infrastructure aspects of the code base. The analysis suggests that programming and non-programming contributors are distinct in their make-up, priorities and rhythms of participation, and that learning plays an important role in controlling access. The results show that volunteers are important drivers of peripheral activities, such as translation and documentation. The term "autonomous peripherality"" is used to capture the unique characteristics of these activities. These findings support the argument that centrality and peripherality are associated with the division of labour, which, in turn, is associated with employment relations and frameworks of institutional support. The thesis shows how the tensions produced by commercialization and peripheral participation are interwoven with values of meritocracy, ritual and  strategic enactment of the idea of community as well as with tools and techniques developed to address the emergence of a set of problems specific to management and governance. These are characterized as "technologies of communities."},
	attachments = {https://flosshub.org/sites/flosshub.org/files/PhD_Berdou.pdf},
	author = {Evangelia Berdou}
}
@article {Wang:2007:MEO:1317471.1317479,
	title = {Measuring the evolution of open source software systems with their communities},
	journal = {SIGSOFT Softw. Eng. Notes},
	volume = {32},
	year = {2007},
	note = {"1. M1: The number of modules in software system at a series of specific moment.
2. CD: The number of developers (code contributors) at a series of specific moment.
3. MC: The correlation of M1 and CD."
"We get the information of Modules from the Launchpad[1] which is a distributed collaborative infrastructure for Ubuntu and other open source software development. Ubuntu mainly grows though a manner of adding new packages. So, we treat packages as the modules we mention before. In Ubuntu community, some members are in charge of auditing the packages and add them to Ubuntu, here developers are refers them."},
	month = {November},
	publisher = {ACM},
	address = {New York, NY, USA},
	abstract = {Open Source Software (OSS) has become the subject of much commercial and academic interest in last few years. As traditional software, OSS also evolves to fulfill the need of stakeholders. Therefore, 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 inadequate to measure OSS evolution. In this paper, we describe a preliminary evolution metrics set for evaluating OSS. The most significant novelty of this model is that it takes specific 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 this metrics set. We find out that the Open Source Community and its members also play essential role in OSS evolution. We expect this metrics model can bring better understandings and explanations of phenomena in open source development and evolution.},
	keywords = {evolution, launchpad, metrics, open source community, open source software, Ubuntu},
	issn = {0163-5948},
	doi = {http://doi.acm.org/10.1145/1317471.1317479},
	url = {http://doi.acm.org/10.1145/1317471.1317479},
	author = {Yi Wang and Defeng Guo and Shi, Huihui}
}
@article {125,
	title = {Membership herding and network stability in the open source community: The Ising perspective},
	journal = {Management Science},
	volume = {53},
	number = {7},
	year = {2007},
	month = {Jul},
	pages = {1086-1101},
	abstract = {The aim of this paper is twofold: (1) to conceptually understand membership dynamics in the open source software (OSS) community, and (2) to explore how different network characteristics (i.e., network size and connectivity) influence the stability of an OSS network. Through the lens of Ising theory, which is widely accepted in physics, we investigate basic patterns of interaction and present fresh conceptual insight into dynamic and reciprocal relations among OSS community members. We also perform computer simulations based on empirical data collected from two actual OSS communities. Key findings include: (1) membership herding is highly present when external influences (e.g., the availability of other OSS projects) are weak, but decreases significantly when external influences increase, (2) propensity for membership herding is most likely to be seen in a large network with random connectivity, and (3) for large networks, when external influences are weak, random connectivity will result in higher network strength than scale-free connectivity (as external influences increase, however, the reverse phenomenon is observed). In addition, scale-free connectivity appears to be less volatile than random connectivity in response to an increase in the strength of external influences. We conclude with several implications that may be of significance to OSS stakeholders in particular, and to a broader range of online communities in general.},
	keywords = {BEHAVIOR, DYNAMICS, ECONOMICS, INNOVATION, INVESTMENT, Ising theory, membership herding, MODEL, MOTIVATION, network connectivity, network stability, open source, PHASE-TRANSITION, UNCERTAINTY},
	isbn = {0025-1909},
	author = {Oh, Wonseok and Jeon, Sangyong}
}
@article {flosswp331,
	title = {Micro-dynamics of Free and Open Source Software Development. Lurking, laboring and launching new projects on SourceForge},
	year = {2007},
	month = {January},
	abstract = {Quantitative methods are employed to describe two fundamental processes in the creation of free (libre) and open source software (FLOSS) that are at work in the collaborative development environment of the SourceForge.Net platform: resource mobilization and "entrepreneurial initiatives" which generate new development projects. The micro dynamics of the individuals{\textquoteright} involvements in these processes are analysed by defining "activity states" that correspond to "lurking" (not contributing or contributing to projects without become a member), "laboring" (joining one or more projects as members), and "launching" (founding one or more projects). The transition probability matrices constructed from observations on the activities of 222,835 individuals who registered on SF.net (during a 14-month period, mainly in 2001) characterize first-order Markov chains describing processes that are ergodic. The computation of the limiting "equilibrium" distribution of individual joining and launching activities is not used here to produce long-run predictions, because the time window of the available data is too short. Instead, it is conceived as an instrument to isolate the main forces acting in the underlying entrepreneurial and recruitment dynamics at work on the platform "shaking off" the weaker tendencies. It is shown that, although only a small proportion of the considered cohorts of SF.net registrants become even minimally active, the active "core" of project members and project founders is able to attract an increasing number of developers. SourceForge is seen to be more than an attractor of projects that are being "born again" under open source licenses: this virtual collaborative development environment shares the regenerative properties of tangible "industrial districts" that give rise to new, innovative enterprises. Implications for the exploitation and exploitation processes at work in the FLOSS model and about its sustainability are also derived.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/davidrullani.pdf},
	author = {Paul A. David and Francesco Rullani}
}
@conference {997,
	title = {Mining CVS Repositories to Understand Open-Source Project Developer Roles},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {8 - 8},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {This paper presents a model to represent the interactions of distributed open-source software developers and utilizes data mining techniques to derive developer roles. The model is then applied on case studies of two open-source projects, ORAC-DR and Mediawiki with encouraging results.},
	keywords = {cvs, developer interaction, developers, mediawiki, orac-dr, roles, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.19},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300008.pdf},
	author = {Yu, Liguo and Ramaswamy, Srini}
}
@conference {1015,
	title = {Mining Eclipse Developer Contributions via Author-Topic Models},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {30 - 30},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {We present the results of applying statistical author-topic models to a subset of the Eclipse 3.0 source code consisting of 2,119 source files and 700,000 lines of code from 59 developers. This technique provides an intuitive and automated framework with which to mine developer contributions and competencies from a given code base while simultaneously extracting software function in the form of topics. In addition to serving as a convenient summary for program function and developer activities, our study shows that topic models provide a meaningful, effective, and statistical basis for developer similarity analysis.},
	keywords = {contributions, developers, eclipse, expertise, mining challenge, msr challenge, source code, topics},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300030.pdf},
	author = {Linstead, Erik and Rigor, Paul and Bajracharya, Sushil and Lopes, Cristina and Baldi, Pierre}
}
@conference {999,
	title = {Mining Software Repositories with iSPAROL and a Software Evolution Ontology},
	booktitle = {Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {10 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {One of the most important decisions researchers face when analyzing the evolution of software systems is the choice of a proper data analysis/exchange format. Most existing formats have to be processed with special programs written specifically for that purpose and are not easily extendible. Most scientists, therefore, use their own database(s) requiring each of them to repeat the work of writing the import/export programs to their format.

We present EvoOnt, a software repository data exchange format based on the Web Ontology Language (OWL). EvoOnt includes software, release, and bug-related information. Since OWL describes the semantics of the data, EvoOnt is (1) easily extendible, (2) comes with many existing tools, and (3) allows to derive assertions through its inherent Description Logic reasoning capabilities.

The paper also shows iSPARQL -- our SPARQL-based Semantic Web query engine containing similarity joins. Together with EvoOnt, iSPARQL can accomplish a sizable number of tasks sought in software repository mining projects, such as an assessment of the amount of change between versions or the detection of bad code smells. To illustrate the usefulness of EvoOnt (and iSPARQL), we perform a series of experiments with a real-world Java project. These show that a number of software analyses can be reduced to simple iSPARQL queries on an EvoOnt dataset.},
	keywords = {database, eclipse, evoont, java, owl, semantic, sparql},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.21},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300010.pdf},
	author = {Kiefer, Christoph and Bernstein, Abraham and Tappolet, Jonas}
}
@conference {1000,
	title = {Mining Workspace Updates in CVS},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {11 - 11},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {The version control archive CVS records not only all changes in a project but also activity data such as when developers create or update their workspaces. Furthermore, CVS records when it has to integrate changes because of parallel development. In this paper, we analyze the CVS activity data of four large open-source projects GCC, JBOSS, JEDIT, and PYTHON to investigate parallel development: What is the degree of parallel development? How frequently do conflicts occur during updates and how are they resolved? How do we identify changes that contain integrations?},
	keywords = {change management, cvs, developers, gcc, jboss, jedit, python, workspaces},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.22},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300011.pdf},
	author = {Zimmermann, Thomas}
}
@article {flosswp1604,
	title = {Motivating job design as a factor in open source governance},
	journal = {J Manage Governance},
	volume = {11},
	number = {2},
	year = {2007},
	month = {May},
	pages = {129{\textendash}137},
	publisher = {Springer Science+Business Media},
	abstract = {Successful open source software (OSS) projects can be considered as examples of how ambitious work results can be achieved in web-based collaboration even when monetary incentives are low or absent. While former explorations of motivational processes in OSS projects primarily focused on person-oriented aspects such as motives, interests, and expected benefits of contributors, job-related factors have been largely neglected. After discussing the limitations of a personoriented focus, a research perspective is suggested that concentrates on job design and work context in OSS based on frameworks from work psychology. A theoretical analysis is presented discussing job characteristics of successful OSS projects as potential explanations of the high motivation of OSS contributors. Compared to a person-oriented perspective, the results of a job-oriented approach might be better transferable to other projects (both OSS and ??closed source?? software development) and provide guidelines for the governance of successful web-based collaboration.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/fulltext.pdf},
	author = {Guido Hertel}
}
@conference {631,
	title = {Network Analysis of the SourceForge.net Community},
	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 = {187 - 200},
	publisher = {Springer},
	organization = {Springer},
	chapter = {15},
	abstract = {Software is central to the functioning of modern computer-based society. The OSS (Open Source Software) phenomenon is a novel, widely growing approach to develop both applications and infrastructure software. In this research, we studied the community network of the SourceForge.net, especially the structure and evolution of the community network, to understand the Open Source Software movement. We applied three different analyses on the network, including structure analysis, centrality analysis and path analysis. By applying these analyses, we are able to gain insights of the network development and its influence to individual developments.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_15},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Network\%20Analysis\%20of\%20the\%20SourceForge.pdf},
	author = {Gao, Yongqin and Madey, Greg}
}
@article {flosswp368,
	title = {Norms, Rewards, and their Effect on the Motivation of Open Source Software Developers},
	year = {2007},
	month = {September},
	abstract = {In this study, we conduct a scenario experiment testing the effect of monetary rewards on intrinsic motivation of open source software (OSS) developers. While we observe no difference in intrinsic motivation between the payment and no payment scenario, total motivation increases when a monetary reward is offered. We find that self-reported interest increases in the payment scenario when there is a norm for payment, whereas it decreases when there is a norm for no payment. We conclude that, under certain preconditions, monetary rewards may well be used in OSS development.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Alexy_Leitner_-_Norms_Rewards_and_Their_Effect_on_the_Motivation_of_OSS_Developers.pdf},
	author = {Oliver Alexy and Martin Leitner}
}
@conference {873,
	title = {Noticing Notice: A large-scale experiment on the timing of software license agreements.},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2007},
	month = {28/04/2007},
	pages = {607-616},
	publisher = {ACM},
	organization = {ACM},
	address = {San Jose, CA},
	isbn = {978-1-59593-593-9},
	author = {N. Good and J. Grossklags and D. Mulligan and Konstan, J.A.}
}
@conference {995,
	title = {Open Borders? Immigration in Open Source Projects},
	booktitle = {Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {6 - 6},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Open source software is built by teams of volunteers. Each project has a core team of developers, who have the authority to commit changes to the repository; this team is the elite, committed foundation of the project, selected through a meritocratic process from a larger number of people who participate on the mailing list. Most projects carefully regulate admission of outsiders to full developer privileges; some projects even have formal descriptions of this process. Understanding the factors that influence the "who, how and when" of this process is critical, both for the sustainability of FLOSS projects, and for outside stakeholders who want to gain entry and succeed. In this paper we mount a quantitative case study of the process by which people join FLOSS projects, using data mined from the Apache web server, Postgres, and Python. We develop a theory of open source project joining, and evaluate this theory based on our data.},
	keywords = {apache, core, joining, postgresql, python, team},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300006.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem and Swaminathan, Anand and Hsu, Greta}
}
@article {flosswp328,
	title = {Open Source and the software industry. How firms do business out of an open innovation paradigm},
	year = {2007},
	month = {January},
	abstract = {Open Source Software (OSS) represents an ???open innovation??? paradigm based on knowledge produced and shared by developers and users. The paper inquires how OSS challenges the three Teece???s building blocks. New findings from a large survey of European software companies, show that within the OSS paradigm: (i) OSS can be a sustainable business model even in the absence of any appropriability; (ii) complementary assets are distributed collectively and made widely available without the need for dedicated contractual arrangements; (iii) a de facto dominant design may stem from a community of users/producers even independently of the presence of powerful large companies.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper_euram_2007.pdf},
	author = {Andrea Bonaccorsi and Monica Merito and Rossi Cristina and Lucia Piscitello}
}
@article {1390,
	title = {An Open Source Approach to Developing Software in a Small Organization},
	journal = {IEEE Software},
	volume = {24},
	year = {2007},
	month = {01/2007},
	pages = {46 - 53},
	abstract = {This article is part of a special issue on Software Engineering Challenges in Small Software Organizations. The software development approach that developers at Kitware use borrows techniques from agile development and Extreme Programming and emphasizes long-term, ongoing projects. The company has used this approach on open source and closed-source projects in a wide range of sizes},
	keywords = {Cross-platform, Small-business, software engineering, Software testing},
	issn = {0740-7459},
	doi = {10.1109/MS.2007.5},
	author = {Martin, Ken and Hoffman, Bill}
}
@conference {618,
	title = {Open Source Collaboration for Fostering Off-The-Shelf Components Selection},
	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 = {17 - 30},
	publisher = {Springer},
	organization = {Springer},
	chapter = {2},
	abstract = {The use of Off-The-Shelf software components in Component- Based Development implies many challenges. One of them is the lack of available and well-suited data to support selection of suitable OTS components. This paper proposes a feasible and incremental way to federate and reuse the different efforts for finding, selecting, and maintaining OTS components in a structured way. This is done not only for supporting OTS components selection, but also to overcome reported problems with the integration and maintenance of component repositories. It is based on the {\textquotedblleft}open source collaboration{\textquotedblright} idea to incrementally build an OTS components reuse infrastructure, enabling automatic support for OTS selection processes.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_2},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Collaboration.pdf},
	author = {Ayala, Claudia and S{\o}ensen, Carl-Fredrik and Conradi, Reidar and Franch, Xavier and Li, Jingyue}
}
@booklet {516,
	title = {Open Source Licensing \& Scattering Opportunism in Software Standards},
	year = {2007},
	month = {Jan},
	abstract = {Despite their beneficial influence on interoperability and markets, problems of detrimental opportunism occur with technology standards, including standards implemented in software, which this Article calls "Software Standards." Inspired by new perspectives on the study of semicommons in the history of real property, this Article contemplates the substitutability of free and open source software ("FOSS") for traditional standard-setting approaches. Standards are analogous to semicommons, where public and private use interact, raising the possibility of opportunistic influence on the Software Standard to increase private gain at the expense of the public benefit in a more uniform standard.  With its source code disclosure requirement, FOSS shifts and dampens this opportunism, although various limits influence the reach of its effect. The political economy around a standard will express itself differently under a FOSS implementation, and clearing intellectual property rights in the standard is no more certain than under the traditional standard-setting approach.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Vetter.OSS_.ScatteringOpportunism.FINAL_.withAppendixA.pdf},
	author = {Greg R Vetter}
}
@article {flosswp360,
	title = {Open Source Software and Economic Growth: A Classical Division of Labor Perspective},
	year = {2007},
	month = {August},
	abstract = {The article turns to classical economic insights on the division of labor and to institutional reasoning to identify some costs and benefits of Open Source Software (OSS) and proprietary software production. It suggests that, thanks to its licenses, OSS favors market expansion more than proprietary software does by tapping into spontaneous work input. The spontaneous tapping leads to a division of labor that exhibits what the article calls redundant economies. By generating a circle of knowledge growth, reuse, and sharing, redundant economies lead to increasing returns, which are crucial for economic growth.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/0SSGROWTHMIT.pdf},
	author = {Giampaolo Garzarelli and Yasmina Reem Limam and Bj{\o}rn Thomassen}
}
@conference {652,
	title = {Open Source Software and Open Data Standards as a form of Technology Adoption: a Case Study},
	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 = {325 - 330},
	publisher = {Springer},
	organization = {Springer},
	chapter = {36},
	abstract = {The process of technology adoption has been studied for long time to give instruments to evaluate the best strategies to ease the introduction of technology. While the main research on Open Source Software focuses mainly on the development process, team collaboration and programmers{\textquoteright} motivations, very few studies consider Open Source Software in this context. In this paper, we provide an overview of literature on technology adoption that can be useful to relate the concepts. We then provide a case study with historical data about file generation and usage across time to evaluate the adoption of Open Source Software and Open Data Standards in the specific case provided.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_36},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OSS\%20and\%20Open\%20Data\%20Standards.pdf},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo}
}
@conference {665,
	title = {Open Source Software and Product Lines 2007},
	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 = {375 - 376},
	publisher = {Springer},
	organization = {Springer},
	chapter = {49},
	abstract = {Embedded industries have invested a lot in the introduction of software product lines in their software development. In addition, using open source software appears to be a profitable way to obtain good software. This is also applicable for organizations doing product line engineering. On the other hand, because of the diverse use of open source software, product line development is an attractive way of working in open source communities. In fact, the configuration mechanisms used in open source communities may be applicable within software product lines as well. In addition, product line organisations are usually involved in distributed development, which works very efficiently within open source communities. However, at present, there is limited interaction between the open source and product line development communities. The aim for the workshop is to explore what the two communities can learn from each other and to develop a better understanding of how the two communities can benefit from each other. The workshop deals with the following issues:
 
{\textendash}Community: Ownership, control and management of product line assets in an open source community
{\textendash}Visibility of the code: when it is valuable to share proprietary code and how to take the right decision.
{\textendash}Architecture Views: Creation of different levels of architecture visibility: proprietary, among closed consortium, public.
{\textendash}Is this possible?
{\textendash}Product line requirements roadmaps and planning in open source development
{\textendash}Variability management: Using the open source community to evolve components and being explicit about variability
{\textendash}Variability representation: in an open source community
{\textendash}Deployment: Open source for the platform and in applications
{\textendash}Heterogeneous processes: Cohabitation of product line management and agile processes
{\textendash}Tools: Open source asset management tools in product line development
{\textendash}Domain and application engineering and their meaning in an open source context
{\textendash}Recovery and recognition of a product line in an open source asset base
{\textendash}Legal: Aspects dealing with evolutionary, variability or distribution of development relating to legal risks involving: liability, warranties, patent infringements etc.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_49},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OSS\%20and\%20product\%20lines\%202007.pdf},
	author = {van der Linden, Frank and Lundell, Bj{\"o}rn}
}
@proceedings {136,
	title = {Open source software development and the small world phenomenon: an empirical investigations of macro level colaboration network properties on project success},
	year = {2007},
	keywords = {NotreDameArchive},
	author = {Param Vir Singh}
}
@booklet {506,
	title = {Open Source Software Development as a Model for Internet Governance},
	year = {2007},
	month = {Sept},
	abstract = {Internet governance and open source software development alike are most effectively achieved through a balance of decentralisation and control. For Internet governance, this is found in governance by network, in which governmental and private stakeholders, and the hierarchical and decentralised mechanisms of governance they respectively favour, are brought together. However if the stakeholders{\textquoteright} power is unequal, so will be the balance of the network. The case of open source software development provides the key to ensuring that stakeholders are not oppressed in a network unbalanced by hierarchical power. This relies on the phenomenon of exit-based empowerment that flows from the open source software licence. However, it can be extended to the design of governance networks given certain idealising assumptions, and even when these do not hold, useful lessons for the future reform of Internet governance arrangements remain.},
	author = {Jeremy Malcolm}
}
@article {springerlink:10.1007/s10368-007-0086-4,
	title = {Open source software: Motivation and restrictive licensing},
	journal = {International Economics and Economic Policy},
	volume = {4},
	year = {2007},
	note = {"We employ a unique data set consisting of 71 open source projects hosted at the SourceForge web site. The 71 projects in the sample were chosen (in January 2000)"
"This sample was observed over an 18-month period from January 2002 through the middle of 2003, with data collected at 2-month intervals."
"We are grateful to NERA for providing us with the data."
"Although we only have data on a relatively small sample of the projects hosted SourceForge, the sample is unique because of data on lines of code as well as data on different versions of the program. The latter is a potentially important control variable, since a change in version may necessitate additional lines of code.
Our data set contains information on the size of the open source projects in the form of source lines of code (SLOC). Using SLOC as a performance measure is not always ideal; nevertheless, this performance measure is employed in the profession and the literature.15 For our purposes, SLOC is in fact an ideal measure, because we want to measure the effort that is put into the project, rather than whether a project succeeds."
},
	pages = {209-225},
	publisher = {Springer Berlin / Heidelberg},
	abstract = {Open source software (OSS) is an economic paradox. Development of open source software is often done by unpaid volunteers and the source code is typically freely available. Surveys suggest that status, signaling, and intrinsic motivations play an important role in inducing developers to invest effort. Contribution to an OSS project is rewarded by adding one{\textquoteright}s name to the list of contributors which is publicly observable. Such incentives imply that programmers may have little incentive to contribute beyond the threshold level required for being listed as a contributor. Using a unique data set we empirically examine this hypothesis. We find that the output per contributor in open source projects is much higher when licenses are less restrictive and more commercially oriented. These results indeed suggest a status, signaling, or intrinsic motivation for participation in OSS projects with restrictive licenses.},
	keywords = {contributions, contributors, developers, incentives, license analysis, licenses, lines of code, loc, MOTIVATION, restrictive, scm, size, status, version history},
	issn = {1612-4804},
	url = {http://dx.doi.org/10.1007/s10368-007-0086-4},
	author = {Fershtman, Chaim and Gandal, Neil}
}
@mastersthesis {486,
	title = {Open Source Software: The use of open source},
	year = {2007},
	abstract = {This thesis explores the reasons behind the poor level of adoption of open source web GIS software, and whether it is due to poor awareness about open source concepts or due to technical deficiencies in the open source tools. The research was done in 2 major phases; the first phase involved conducting surveys to measure the awareness and attitudes towards open source. The surveys examined three categories of people involved in the IT industry, namely: decision makers, software developers, and end users. The measurement of awareness was done by developing an Awareness Indicator and a Sentiment Indicator for each category. These indicators were developed by the author during the course of the study in order to provide a measurable and descriptive indication of the results. The second phase involved performing a comparative analysis between MapServer a leading open source web GIS tool, and three of the leading proprietary web GIS software, namely: ESRI{\textquoteright}s ArcIMS, Intergraph{\textquoteright}s GeoMedia WebMap, and MapInfo{\textquoteright}s MapXtreme.

The results of the research provide an insight on how different categories of people view open source, and demonstrate that lack of awareness about open source concepts and its competencies may be a major reason behind the poor adoption of open source solutions. The results of the comparative analysis also demonstrate that MapServer is technically equivalent to its commercial counter parts.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OpenSourceGIS.pdf},
	author = {Mahmoud Refaat Nasr}
}
@conference {638,
	title = {Open source technologies for visually impaired people},
	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 = {241 - 246},
	publisher = {Springer},
	organization = {Springer},
	chapter = {22},
	abstract = {We describe two open source applications which we have experienced as very useful aids for the integration of people suffering from visual impairments, from hypovision to actual blindness. The first application is based on speech synthesis and has been experienced by disabled university students. The second experience is oriented to schoolchildren with low residual vision, and it provides their educators and parents with easy to use tools for image manipulation, especially designed for exploiting
residual visual abilities.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_22},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Technologies\%20for\%20Visually\%20.pdf},
	author = {Boccacci, Patrizia and Carrega, Veronica and Dodero, Gabriella}
}
@article {ford2007open,
	title = {Open vs. closed: which source is more secure?},
	journal = {Queue},
	volume = {5},
	number = {1},
	year = {2007},
	pages = {32{\textendash}38},
	publisher = {ACM},
	abstract = {There is no better way to start an argument among a group of developers than proclaiming Operating System A to be {\textquotedblleft}more secure{\textquotedblright} than Operating System B. I know this from first-hand experience, as previous papers I have published on this topic have led to reams of heated e-mails directed at me{\textemdash}including some that were, quite literally, physically threatening. Despite the heat (not light!) generated from attempting to investigate the relative security of different software projects, investigate we must.

Understanding why products are (and are not) secure is a critical stepping stone toward building better software.

Before wading into these dangerous waters, we should clarify the question. All too often when comparing open and closed source approaches, the question is unconsciously interpreted as Windows versus Linux. While that{\textquoteright}s a fantastic question to knock around, doing so is a very narrow way of looking at the world, as it ignores many other projects in both the open and closed source worlds. Although it{\textquoteright}s foolish to ignore the data points the Windows/Linux world provides, they are simply examples of the process. So, let us first strip away the misconception that the question is about these particular platforms and recognize its real breadth.

With this in mind, our answer requires three crucial definitions in order to have meaning: {\textquotedblleft}What is open source?{\textquotedblright}; {\textquotedblleft}What is closed source?{\textquotedblright}; and, surprisingly, {\textquotedblleft}What is security?{\textquotedblright} The first two we can deal with quickly; the third is a lot subtler, however, so we shall tackle it first.},
	url = {http://queue.acm.org/detail.cfm?id=1217267},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p32-ford.pdf},
	author = {Ford, Richard}
}
@conference {630,
	title = {OpenBQR: a framework for the assessment of OSS},
	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 = {173 - 186},
	publisher = {Springer},
	organization = {Springer},
	chapter = {14},
	abstract = {People and organizations that are considering the adoption of OSS, or that need to choose among different OS products face the problem of evaluating OSS in a systematic, sound and complete way. While several proposals concerning the evaluation of costs and benefits exist, little attention has been given to the evaluation of technical qualities and, in general, to the {\textquotedblleft}usage-oriented{\textquotedblright} issues. In this paper the existing proposals are examined, the different types of qualities and issues that are relevant to potential users are described, and a coherent and innovative method for the evaluation of OSS is proposed. The proposed method is expected to support the potential user in the evaluation and choice of OSS in a flexible way, taking into account all the aspects that are relevant to the user.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_14},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OpenBQR.pdf},
	author = {Taibi, Davide and Lavazza, Luigi and Morasca, Sandro}
}
@article {flosswp361,
	title = {Out of Box Experience Issues of Free and Open Source Software},
	year = {2007},
	month = {July},
	abstract = {Abstract. This study addresses the Out-Of-Box Experience (OOBE) usability issues of Free and Open Source Software (F/OSS) considering outcomes of distributed development process and high number of available product choices. A methodology is presented, usability experiments are conducted and results are discussed. The objective was to determine key factors that affect usability of F/OSS during OOBE and first hours of use. We concluded that OOBE of F/OSS was significant in software usability perception and possible adoption. User experience, visible structure, consistency and functionality of the interface had significant impact on OOBE and first hours of use. Neither online support, nor product box appearance appeared as important.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/gokturkcetin},
	author = {G{\"o}kt{\"u}rk Mehmet and G{\"o}rkem {\c C}etin}
}
@inbook {812,
	title = {Patchworks of Open-Source Software: High-Fidelity Low-cost Prototypes. },
	booktitle = {The Handbook of Research on Open Source Software. },
	year = {2007},
	pages = {126-140.},
	publisher = {Idea Group, Inc.},
	organization = {Idea Group, Inc.},
	author = {Jones, M.C. and Floyd, I.R. and Twidale, M.B}
}
@article {flosswp375,
	title = {Penguin in a new suit: A tale of how de novo entrants emerged to harness free and open source communities},
	year = {2007},
	month = {October},
	abstract = {A growing body of literature has explored the motivations for individuals to take part in free and open source software (FOSS), yet how firms participate is largely an unattended research area. Building on information from an extensive dataset of secondary sources and 30 in-depth interviews, I show that de novo entrants have emerged in conjunction with a changing institutional infrastructure and a more pragmatic attitude toward firms that focus on technological benefits rather than ideology. To understand how these firms try to harness the work of these communities, I use the empirical data to derive a 2*2 matrix of different approaches. The X axis reflects whether or not the firms initiated a new community or relied on communities founded by peers, whereas the Y axis represents the degree of participation of the firm in the community. This taxonomy illustrates how de novo entrant are initiating new forms of communities or joining communities established by peers. This suggests that while many of the central pillars of FOSS remains, de novo entrants have emerged to find new ways of making business resulting in various implications for firm strategies and knowledge disclosure. PLEASE EMAIL IF YOU LIKE A COPY OF THE PAPER!},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dahlander2007.pdf},
	author = {Linus Dahlander}
}
@conference {651,
	title = {Perceptions on F/OSS Adoption},
	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 = {319 - 324},
	publisher = {Springer},
	organization = {Springer},
	chapter = {35},
	abstract = {This paper aims to reveal results of a survey run by the tOSSad1 project. The majority of survey variables devised to capture perception of public administrators around Europe regarding the importance they attach to the factors such as F/OSS product quality, availability of support, expertise and documentation, TCO, vendor lock-in, political influence, administrative attitudes, productivity, and training costs, all of which intermingle with financial, technical, legal, and personal issues. The analysis consist of depiction of respondents{\textquoteright} administration profile in terms of their F/OSS usage and adoption, descriptive summary and analyses of factors mentioned above, and statistical inferential analyses of survey items. Some valid statistical tests are conducted to understand, to discuss and to see the extend and significance of any F/OSS adoption generalizations for Europe based on the findings of this particular survey.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_35},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Perceptions\%20on\%20F\%20OSS.pdf},
	author = {Ozel, Bulent and Jovanovic, Uros and Oba, Beyza and van Leeuwen, Manon}
}
@conference {1016,
	title = {Predicting Defects and Changes with Import Relations},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {31 - 31},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Lowering the number of defects and estimating the development time of a software project are two important goals of software engineering. To predict the number of defects and changes we train models with import relations. This enables us to decrease the number of defects by more efficient testing and to assess the effort needed in respect to the number of changes.},
	keywords = {defects, eclipse, effort estimation, mining challenge, msr challenge, prediction},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.24},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300031.pdf},
	author = {Schroter, Adrian}
}
@conference {1014,
	title = {Predicting Eclipse Bug Lifetimes},
	booktitle = {Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {29 - 29},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {In non-trivial software development projects planning and allocation of resources is an important and difficult task. Estimation of work time to fix a bug is commonly used to support this process. This research explores the viability of using data mining tools to predict the time to fix a bug given only the basic information known at the beginning of a bug{\textquoteright}s lifetime. To address this question, a historical portion of the Eclipse Bugzilla database is used for modeling and predicting bug lifetimes. A bug history transformation process is described and several data mining models are built and tested. Interesting behaviours derived from the models are documented. The models can correctly predict up to 34.9\% of the bugs into a discretized log scaled lifetime class.},
	keywords = {bug fixing, bugzilla, classification, eclipse, effort estimation, mining challenge, msr challenge, prediction, weka},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.25},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300029.pdf},
	author = {Panjer, Lucas D.}
}
@conference {1214,
	title = {A Preliminary Analysis of Publicly Available FLOSS Measurements: Towards Discovering Maintainability Trends},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	note = {used SourceKibitzer data downloaded from FLOSSmole},
	month = {2007},
	abstract = {The spread of free/libre/open source software (FLOSS) and the openness of its development model offer researchers a valuable source of information regarding software data. The creation of large portals, which host a vast amount of FLOSS projects make it easy to create large datasets with valuable information regarding the FLOSS development process. In addition initiatives such as FLOSSMole provide researchers with a single point and continuing access to those data. Up to now the majority of datasets from FLOSSMole offered data regarding the development process and not the code itself. From February 2007 FLOSSMole offers data donated 
by SourceKibitzer, which contain source code metrics for FLOSS projects written in Java. In this paper we provide 
a premilinary analysis on those data using machine learning techniques, such as classification rules and decision trees. Using the first available data from February 2007, we tried to build rules that can be used in order to estimate the future values of metrics offered for March. Here we present some preliminary results that are encouraging and deserve to be further analyzed in future releases of SourceKibitzer datasets. },
	keywords = {decision tree, flossmole, java, machine learning, metrics, sourcekibitzer},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Samolades2007.pdf},
	author = {Samoladas, Ioannis and Bibi, Stamatia and Ioannis Stamelos and Sowe, Sulayman K. and Deligiannis, Ignatios}
}
@conference {1012,
	title = {Prioritizing Warning Categories by Analyzing Software History},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {27 - 27},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Automatic bug finding tools tend to have high false positive rates: most warnings do not indicate real bugs. Usually bug finding tools prioritize each warning category. For example, the priority of "overflow" is 1 and the priority of "jumbled incremental" is 3, but the tools{\textquoteright} prioritization is not very effective.

In this paper, we prioritize warning categories by analyzing the software change history. The underlying intuition is that if warnings from a category are resolved quickly by developers, the warnings in the category are important. Experiments with three bug finding tools (FindBugs, JLint, and PMD) and two open source projects (Columba and jEdit) indicate that different warning categories have very different lifetimes. Based on that observation, we propose a preliminary algorithm for warning category prioritizing.},
	keywords = {bug fixing, change history, columba, findbugs, jedit, jlint, kenyon, pmd, warning},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.26},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300027.pdf},
	author = {Kim, Sunghun and Ernst, Michael D.}
}
@proceedings {66,
	title = {Productivity effects of information diffusion in email networks},
	year = {2007},
	address = {Montr{\'e}al, PQ, Canada},
	author = {Sinan Aral and Erik Brynjolfsson and Marshall Van Alstyne}
}
@conference {1225,
	title = {Programming Language Trends in Open Source Development: An Evaluation Using Data from All Production Phase SourceForge Projects},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	note = {"Our data were gathered from the SourceForge Research Ar- chive (SFRA) [4] and the CVS repositories Open Source projects hosted on SourceForge. We used cvs2mysql and SFRA+ to collect the data. cvs2mysql gathers data from CVS repositories and writes them to SQL scripts for im- port into a MySQL 5.0 database. The data collected by cvs2mysql are the name of the file, the location of the file in the repository, the type and state of the file, as well as the author, date, number of lines added and removed, and the author{\textquoteright}s message for each revision to the file."},
	abstract = {In this work, we analyze data collected from the CVS repos- itories of 9,997 Open Source projects hosted on SourceForge in an effort to understand trends in programming language usage in the Open Source community between 2000 and 2005. The trends we consider include: 1) the relative popularity of the ten most popular programming languages over time, 2) the use of multiple programming languages by individual programmers and by individual projects, and 3) the programming languages most often used in combination.},
	keywords = {cvs, cvs2mysql, programming languages, sfra, sourceforge, srda},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Delorey2007b.pdf},
	author = {Delorey, Daniel P. and Knutson, Charles D. and Giraud-Carrier, C.}
}
@conference {672,
	title = {Project Entity Matching across FLOSS Repositories},
	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 = {45 - 57},
	publisher = {Springer},
	organization = {Springer},
	chapter = {4},
	abstract = {Much of the data about free, libre, and open source (FLOSS) software development comes from studies of code repositories used for managing projects. This paper presents a method for integrating data about open source projects by way of matching projects (entities) and deleting duplicates across multiple code repositories. After a review of the relevant literature, a few of the methods are chosen and applied to the FLOSS domain, including a simple scoring system for confidence in pairwise project matches. Finally, the paper describes limitations of this approach and recommendations for future work.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Project\%20Entity\%20Matching.pdf},
	author = {Conklin, Megan}
}
@article {flosswp367,
	title = {Promoting the Penguin: Who is Advocating Open Source Software in Commercial Settings?},
	year = {2007},
	month = {August},
	abstract = {Most firms that use or develop software today face the questions of whether and how to engage in open source software. Yet, little is known about the process of OSS adoption and diffusion within corporations. Guided by the theoretical frameworks of Rogers (innovation diffusion) and Davis (Technology Acceptance Model), we develop a model of how job function influences individuals??? proclivity to support their employers??? adoption of OSS and OSS practices. We argue that job function determines which tasks in the software development process are part of an individual???s daily routine, and that different tasks are differentially affected by OSS. Our study is based on interviews with 25 individuals and a large-scale survey distributed to 249 participants in the telecommunications department of a multinational company. The results, although consistent with theoretical considerations, are nevertheless surprising. Distinguishing between developers, software testers, software architects, project managers, and managers, we find greater involvement in OSS activities to be favored most strongly by software testers, followed by software architects and managers. Excepting project managers, developers, despite having the most experience with OSS, are the least favorably disposed to greater corporate engagement in OSS. A corporation interested in adopting OSS and open innovation processes should thus take into account the job function-related incentives of each individual as well as various organizational factors. More generally, we propose that models developed to predict IT adoption behavior be extended to account for the ways in which individual adopters interact with the innovation at hand, which we maintain will be determined largely by their job functions.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Alexy_Henkel_-_Promoting_the_Penguin.pdf},
	author = {Oliver Alexy and Joachim Henkel}
}
@article {flosswp369,
	title = {Putting a Value on Openness: The Effect of Product Source Code Releases on the Market Value of Firms},
	year = {2007},
	month = {October},
	abstract = {This study examines the effect of releasing the source code of commercial software products as open source software on the market value of firms. Using a sample of 30 software companies in the time span from 1 January 1999 to 30 April 2007, I find that market valuation is influenced by investor sentiment???abnormal returns take a curvilinear shape over time???and the business model firms choose for their OSS efforts???non-existence of an explicit revenue model is punished by the capital market. From my findings, I deduce several implications for IT-related event studies and research on open innovation processes.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Alexy_-_Putting_a_Value_on_Openness.pdf},
	author = {Oliver Alexy and Joachim Henkel}
}
@unpublished {flosswp363,
	title = {Quality Improvement in Volunteer Free and Open Source Software Projects},
	year = {2007},
	month = {March},
	abstract = {Free and open source software has had a major impact on the computer industry since the late 1990s and has changed the way software is perceived, developed and deployed in many areas. Free and open source software, or FOSS, is typically developed in a collaborative fashion and the majority of contributors are volunteers. Even though this collaborative form of development has produced a significant body of software, the development process is often described as unstructured and unorganized. This dissertation studies the FOSS phenomenon from a quality perspective and investigates where improvements to the development process are possible. In particular, the focus is on release management since this is concerned with the delivery of a high quality product to end-users. This research has identified considerable interest amongst the FOSS community in a novel release management strategy, time based releases. In contrast to traditional development which is feature-driven, time based releases use time rather than features as the criterion for the creation of a new release. Releases are made after a specific interval, and new features that have been completed and sufficiently tested since the last release are included in the new version. This dissertation explores why, and under which circumstances, the time based release strategy is a viable alternative to feature-driven development and discusses factors that influence a successful implementation of this release strategy. It is argued that this release strategy acts as a coordination mechanism in large volunteer projects that are geographically dispersed. The time based release strategy allows a more controlled development and release process in projects which have little control of their contributors and therefore contributes to the quality of the output.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/michlmayr-phd.pdf},
	author = {Martin Michlmayr}
}
@conference {662,
	title = {Quality Specification, Testing and Certification of Bespoken, Open Source and Commercial Off-The-Shelf Systems},
	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 = {365 - 366},
	publisher = {Springer},
	organization = {Springer},
	chapter = {46},
	abstract = {The seminar will cover the principles as well as the best practices of software system quality assurance (comprising inspection, verification, validation, black and white box test, measurement and assessment, and the normative quality characteristics) for procedural, object-oriented, aspectoriented and agent-based dependable software. Attendees will exercise proven techniques for goal-directed quality specification, testing, measurement, scaling and assessment for software certification. Assessment of both the software product as well as the software process will be discussed with respect to its relevance for such acceptance assessments. A standardized process model for measurement, assessment and certification of dependable software will be used to make the attendees familiar with this comprehensive assessment procedure and to learn how to embed it into today{\textquoteright}s standardized or non-standardized software processes.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_46},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Quality\%20Specification\%20Testing.pdf},
	author = {Hausen, Hans-Ludwig}
}
@conference {883,
	title = {The Quest for Quality Tags.},
	booktitle = {Conference on Supporting Group Work},
	year = {2007},
	author = {Shilad Sen and Harper, F. Maxwell and Adam LaPitz and John Riedl}
}
@conference {884,
	title = {Recommenders Everywhere: The WikiLens Community-Maintained Recommender System},
	booktitle = {Wikisym 2007},
	year = {2007},
	address = {Montreal, Quebec, Canada},
	isbn = {978-1-59593-861-9},
	author = {Dan Frankowski and Shyong K. Lam and Shilad Sen and Harper, F. Maxwell and Scott Yilek and Michael Cassano and John Riedl}
}
@conference {994,
	title = {Recommending Emergent Teams},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {5 - 5},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {To build successful complex software systems, developers must collaborate with each other to solve issues. To facilitate this collaboration, specialized tools, such as chat and screen sharing, are being integrated into development environments. Currently, these tools require a developer to maintain a list of other developers with whom they may wish to communicate and to determine who within this list has expertise for a specific situation. For large, dynamic projects, like several successful open-source projects, these requirements place an unreasonable burden on the developer. In this paper, we show how the structure of a team emerges from how developers change software artifacts. We introduce the Emergent Expertise Locator (EEL) that uses emergent team information to propose experts to a developer within their development environment as the developer works. We found that EEL produces, on average, results with higher precision and higher recall than an existing heuristic for expertise recommendation.},
	keywords = {bugzilla, developers, eclipse, evolution, expertise, Firefox, teams},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300005.pdf},
	author = {Minto, Shawn and Murphy, Gail C.}
}
@conference {647,
	title = {Release Management in Free Software Projects: Practices and Problems},
	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 = {295 - 300},
	publisher = {Springer},
	organization = {Springer},
	chapter = {31},
	abstract = {Release management plays an important role in every software project since it is concerned with the delivery of a high quality product to end-users. This paper explores release practices employed by volunteer free software projects and shows problems that occur. A challenge that has been identified is the difficulty of coordinating a distributed team of volunteers in order to align their work for a release.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Release\%20Management\%20in\%20Free\%20Software.pdf},
	author = {Martin Michlmayr and Hunt, Francis and Probert, David}
}
@conference {1004,
	title = {Release Pattern Discovery via Partitioning: Methodology and Case Study},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {19 - 19},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {The development of Open Source systems produces a variety of software artifacts such as source code, version control records, bug reports, and email discussions. Since the development is distributed across different tool environments and developer practices, any analysis of project behavior must be inferred from whatever common artifacts happen to be available. In this paper, we propose an approach to characterizing a project{\textquoteright}s behavior around the time of major and minor releases; we do this by partitioning the observed activities, such as artifact check-ins, around the dates of major and minor releases, and then look for recognizable patterns. We validate this approach by means of a case study on the MySQL database system; in this case study, we found patterns which suggested MySQL was behaving consistently within itself. These patterns included testing and documenting that took place more before a release than after and that the rate of source code changes dipped around release time.},
	keywords = {bitkeeper, bt2csv, cvs, evolution, mysql, releases, revision history, scm, softchange, version control},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.28},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300019.pdf},
	author = {Hindle, Abram and Godfrey, Michael W. and Holt, Richard C.}
}
@conference {634,
	title = {Reusing an open source application {\textemdash} practical experiences with a mobile CRM pilot},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	year = {2007},
	month = {2007///},
	pages = {217 - 222},
	publisher = {Springer},
	organization = {Springer},
	chapter = {18},
	abstract = {We discuss experiences in extending an open source CRM application to develop a new server-based mobile business application. Combining the application code reuse with incremental development process allowed successful development of a pilot application in a tight schedule. In particular, it enabled a quick start for customer-driven development, diminished risks related to the baseline application itself, and provided the flexibility needed in experimental pilot development.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Reusing\%20an\%20Open\%20Source\%20Application.pdf},
	author = {Akkanen, Jyrki and Demeter, Hunor and Eppel, Tam{\'a}s and Iv{\'a}nfi, Zolt{\'a}n and Nurminen, Jukka and Stenman, Petri}
}
@article {flosswp326,
	title = {Role Migration and Advancement Processes in OSSD Projects: A Comparative Case Study},
	year = {2007},
	month = {May},
	abstract = {Socio-technical processes have come to the forefront of recent analysis of the open source software development (OSSD) world. Interest in making these processes explicit is mounting from industry and the software process community, as well as among those who may become contributors to an OSSD organization. This paper serves to close this gap by providing an analysis of the role migration and project career advancement process, and role-sets within, that we have observed within three large OSSD project organizations: Mozilla.org, Apache.org, and NetBeans.org.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Jensen-Scacchi-ICSE-2007.pdf},
	author = {Chris Jensen and Walt Scacchi}
}
@article {86,
	title = {The role of face-to-face meetings in technology-supported self-organizing distributed teams},
	journal = {Ieee Transactions on Professional Communication},
	volume = {50},
	number = {3},
	year = {2007},
	note = {Times Cited: 0},
	pages = {185-203},
	abstract = {We examine the role of face-to-face meetings in the context of technology-supported self-organizing distributed (or virtual teams), specifically Free/Libre Open Source Software (FLOSS) development teams. Based on a qualitative inductive analysis of data from interviews and observations at FLOSS conferences, we identify a variety of settings in which developers meet face-to-face, and we point out the activities performed in these settings and the benefits obtained. Contrary to conventional wisdom about distributed teams, FLOSS developers generally do not meet face-to-face until the project is well under way. An additional benefit offace-to-face meetings is time away from a regular job and speed of interaction for certain kinds of tasks.},
	author = {Kevin Crowston and James Howison and Chengetai Masango and Eseryel, U. Yeliz}
}
@conference {635,
	title = {The role of trust in OSS communities {\textemdash} Case Linux Kernel community},
	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 = {223 - 228},
	publisher = {Springer},
	organization = {Springer},
	chapter = {19},
	abstract = {Open source software development has been the subject of interest among businesses as well as in the academic world. OSS enables many possibilities for companies but also sets new kinds of challenges. Because of the characteristics of the OSS phenomenon we propose that trust in OSS communities plays a key role in facilitating their success. Therefore, the aim of this study is to explore the factors that affect trust in OSS communities. The data is gathered by a survey aimed to Linux Kernel developers. Among other results it may be concluded that the most important factors affecting trust seem to be other developers{\textquoteright} skills, reputation as well as the formal and informal practices.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_19},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Role\%20of\%20Trust\%20in\%20OSS.pdf},
	author = {Antikainen, Maria and Aaltonen, Timo and V{\"a}is{\"a}nen, Jaani}
}
@article {877,
	title = {Seeking Open Infrastructure: Contrasting Open Standards, Open Source and Open Innovation},
	journal = {First Monday},
	volume = {12},
	year = {2007},
	month = {06/2007},
	author = {Joel West}
}
@article {flosswp405,
	title = {Self-organization of teams for free/libre open source software development},
	journal = {Information and Software Technology Journal},
	volume = {49},
	number = {564-575},
	year = {2007},
	note = {"First, the data from these projects that we needed for analysis had to be publicly available (ruling out projects that limit access to their email lists or trackers). Second, we chose the projects that had more than 7 members"..."projects that have attracted numerous developers beyond the initial project founders, are continuing to release software, have numerous downloads and have an active user community that provides feedback"
"3 FLOSS projects were selected for analysis, namely Gaim, eGroupWare and Compiere ERP."

all had sourceforge hosting

Data: "The primary data used for our study were interactions on the main developer communication forum, either a developer mailing list or web-based discussion forum."

Analysis: "For this project, we inductively content-analyzed developer email interactions to identify the task assignment mechanisms used in the process. We coded each instance of task assignment identified on three dimensions: who assigned the task, to whom, and how"
},
	abstract = {This paper provides empirical evidence about how free/libre open source software development teams self-organize their work. Following a case study methodology, we examined developer interaction data from three active and successful FLOSS projects using qualitative research methods, specifically inductive content analysis, to identify the task-assignment mechanisms used by the participants. We found that "self-assignment" was the most common mechanism across three FLOSS projects. This mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research.},
	keywords = {case study, compiere, coordination, DESIGN, distributed teams, egroupware, email, email archives, forum, free/libre open source software development, gaim, INTERNET, mailing list, metadata, qualitative research methods, self-organizing teams, sourceforge, SYSTEMS, task assignment, WORK},
	attachments = {https://flosshub.org/sites/flosshub.org/files/task_assignment_final.pdf},
	author = {Kevin Crowston and Li, Qing and Kangning Wei and Eseryel, U. Yeliz and Howison, James}
}
@conference {645,
	title = {Shared Assumption Concerning Technical Determination in Apache Web Server Developer Community},
	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 = {283 - 288},
	publisher = {Springer},
	organization = {Springer},
	chapter = {29},
	abstract = {Our main finding is that OSS community seems to coordinate its activities by relying on technical determination. First, we review previous literature to understand OSS community coordination mechanisms. Then we empirically review OSS Apache Web Server community by using qualitative case study methods. Our data consist of developer list{\textquoteright}s email-discussions. Finally, we speculate that coordination rests on community{\textquoteright}s members{\textquoteright} shared assumption concerning technical determination.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Shared\%20Assumption\%20Concering.pdf},
	author = {Juho Lindman}
}
@conference {1227,
	title = {Simulation of the temporal evolution of OSS projects: application to XMMS and MPLAYER},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	author = {Antoniades, Ionannis~ and Kontoyiannis and Ioannis Stamelos and Deligiannis, Ignatios}
}
@proceedings {144,
	title = {Social capital, structural holes and team composition: collaborative networks of the open source software community},
	year = {2007},
	keywords = {NotreDameArchive},
	author = {Yong Tan and Vijay Mookerjee and Param Vir Singh}
}
@conference {875,
	title = {Social Comparisons to Motivate Contributions to an Online Community.},
	booktitle = {Persuasive Technology},
	year = {2007},
	month = {26/04/2007},
	address = {Palo Alto, CA},
	author = {F. Harper and X. Li and Y. Chen and J. Konstan}
}
@article {119,
	title = {Social network structures in open source software development teams},
	journal = {Journal of Database Management},
	volume = {18},
	number = {2},
	year = {2007},
	note = {"Three projects were selected from SourceForge.net in terms of their similarities as well as their differences. Monthly data were extracted from the bug tracking systems in order to achieve a longitudinal view of the interaction pattern of each project. Social network analysis was used to generate the indices of social structure."

no pdf},
	month = {Apr-Jun},
	pages = {25-40},
	abstract = {Drawing on social network theories and previous studies, this research examines the dynamics of social network structures in open source software (OSS) teams. Three projects were selected from SourceForge.net in terms of their similarities as well as their differences. Monthly data were extracted from the bug tracking systems in order to achieve a longitudinal view of the interaction pattern of each project. Social network analysis was used to generate the indices of social structure. The finding suggests that the interaction pattern of OSS projects evolves from a single hub at the beginning to a corel periphery model as the projects move forward.},
	keywords = {bug tracking, bugs, COMMUNITY, INNOVATION, longitudinal study, MODEL, open source, social, social network analysis, social networks, sourceforge, structure},
	isbn = {1063-8016},
	author = {Long, Y. and Siau, K.}
}
@conference {993,
	title = {Spam Filter Based Approach for Finding Fault-Prone Software Modules},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {4 - 4},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Because of the increase of needs for spam e-mail detection, the spam filtering technique has been improved as a convenient and effective technique for text mining. We propose a novel approach to detect fault-prone modules in a way that the source code modules are considered as text files and are applied to the spam filter directly. In order to show the applicability of our approach, we conducted experimental applications using source code repositories of Java based open source developments. The result of experiments shows that our approach can classify more than 75\% of software modules correctly.},
	keywords = {argouml, bug reports, classification, eclipse, java, modules, scm, spam, text mining},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300004.pdf},
	author = {Mizuno, Osamu and Ikami, Shiro and Nakaichi, Shuya and Kikuno, Tohru}
}
@conference {627,
	title = {Sprint-driven development: working, learning and the process of enculturation in the PyPy community},
	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 = {133 - 146},
	publisher = {Springer},
	organization = {Springer},
	chapter = {11},
	abstract = {In this paper we examine sprint-driven software development as it occurs in a specific Open Source community, PyPy. Applying a situated learning perspective, we report the findings from a study focused on the activities leading up to, taking place during, and following after sprints. The study included analyses of sprint reports, email archives and other documents available on the community website, as well as a one-week period of direct observation of a specific sprint. The objective of the study was to elaborate on how the practices of sprint-driven development in the PyPy community facilitate learning, the dissemination of knowledge among its members and the expansion of the Open Source community. This paper aims to assess how sprint-driven development can facilitate situated learning in distributed software development by describing the practices applied in PyPy.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_11},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Spring-driven\%20development.pdf},
	author = {Sigfridsson, Anders and Avram, Gabriela and Sheehan, Anne and Sullivan, Daniel}
}
@conference {655,
	title = {Stakeholder value, usage, needs and obligations from differnet types of F/LOSS licenses},
	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 = {343 - 348},
	publisher = {Springer},
	organization = {Springer},
	chapter = {39},
	abstract = {This paper discusses different types of Stakeholders of F/LOSS, their needs, the value, usage, and obligations that stakeholders have for different types of F/LOSS licenses. Stakeholders include Developers: Individuals, Projects, Embedded Systems. Vendors: Dominant, Niche, F/LOSS. Packagers. End Users. Organisations: Disseminators, Internally, Externally Used.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_39},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Skakteholder\%20value\%20usage.pdf},
	author = {Skidmore, Darren}
}
@article {64,
	title = {Study~of~Available~Tools },
	year = {2007},
	institution = {FLOSSmetrics},
	type = {EU Framework deliverable},
	isbn = {D1.1},
	url = {http://flossmetrics.org/sections/deliverables/docs/deliverables/WP1/D1.1- Study_of_Available_Tools.pdf},
	author = {Antoniades, Ionannis~ and Samoladas, Ioannis and Sowe, Sulayman K. and Gregorio Robles and Koch, Stefan and Fraczek, Ksenia and Hadzisalihovic, Anis}
}
@conference {1212,
	title = {Studying Production Phase SourceForge Projects: An Exploratory Analysis Using cvs2mysql and SFRA},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	month = {2007},
	abstract = {A wealth of data can be extracted from the natural by-products of software development processes and used in empirical studies of software engineering. However, the size and accuracy of such studies depend in large part on the availability of tools that facilitate the collection of data from individual projects and the combination of data from multiple projects. To demonstrate this point, we present our experience gathering and analyzing data from nearly 10,000 open source projects hosted on SourceForge. We describe the tools we developed to collect the data and the ways in which these tools and data may be used by other researchers. We also provide examples of statistics that we have calculated from these data to describe interesting author- and project-level behaviors of the SourceForge community.},
	keywords = {Data Collection, forge, repositories, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Delorey2007c.pdf},
	author = {Delorey, Daniel P. and Knutson, Charles D. and MacLean, Alexander C.}
}
@conference {1002,
	title = {Studying Versioning Information to Understand Inheritance Hierarchy Changes},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {16 - 16},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {With the widespread adoption of object-oriented programming, changing the inheritance hierarchy became an inherent part of today{\textquoteright}s software maintenance activities. Unfortunately, little is known about the "state-of-the-practice" with respect to changing an application{\textquoteright}s inheritance hierarchy, and consequently we do not know how the change process can be improved. In this paper, we report on a study of the hierarchy changes stored in a versioning system to explore the answers to three research questions: (1) why are hierarchy changes made? (2) what kind of hierarchy changes are made? (3) what is the impact of these changes? Based on the results of this study, we formulate 7 hypotheses which should be investigated further to make conclusive interpretations on how hierarchy changes fit in the actual change process.},
	keywords = {argouml, change management, inheritance, jedit},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.30},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300016.pdf},
	author = {Rysselberghe, Filip Van and Demeyer, Serge}
}
@conference {641,
	title = {Surveying Industrial Roles in 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 = {259 - 264},
	publisher = {Springer},
	organization = {Springer},
	chapter = {25},
	abstract = {Industry uses Open Source Software (OSS) to a greater and greater extent. We have defined four industrial OSS roles; OSS provider, OSS integrator, OSS participant and Inner Source Software (ISS) participant. Based on these four roles we have performed a survey in the ITEA COSI project. We provide initial answers to what motivates companies to undertake these roles, what are the advantages and challenges of undertaking them, and which development practices they use while undertaking these roles.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_25},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Surveying\%20Industrial\%20Roles.pdf},
	author = {Hauge, {\O}yvind and S{\o}rensen, Carl-Fredrik and R{\o}sdal, Andreas}
}
@mastersthesis {483,
	title = {"A system that works for me" - an anthropological analysis of computer hackers{\textquoteright} shared use and development of the Ubuntu system},
	year = {2007},
	month = {June},
	abstract = {Based on 6 months of anthropological fieldwork both on-line and in-person among the developers working to develop and maintain the Ubuntu Linux system, this thesis examines the individual and collaborative day-to-day practices of these developers as they relate to the computer operating system that is the result of their labour. Despite being spread across the industrialized world, these ""hackers"" socialise, share their knowledge, and come to depend on each other in their work across the Internet, as well as in their in-person meetings at conferences and summits. I argue that these shared and negotiated on-line and in-person practices constitute a community of practice (Wenger 1998) rooted in a more than 40-year old "oral"computing tradition based on the Unix operating system.
Taking the Ubuntu system as my point of departure, I examine the network of practices, processes and actors in which it has been constructed, and
through a strategically selected constellation of theories drawn from anthropology, philosophy, and new media studies, I seek to describe and analyze the three central dimensions of a community of practice. I conclude by suggesting that it is the possibility to adopt, learn, configure, and even build the system according to their own needs, which opens the meritocratic community of practice for new contributors to scale the steep curve of learning necessary to enter and learn among them. In this way, the Ubuntu hackers come to share more than just the same system, they come to share a common history, and, to a certain extent, a shared identity through their practice.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ubuntu.pdf},
	author = {Andreas Lloyd}
}
@conference {874,
	title = {Talk Amongst Yourselves: Inviting Users to Participate in Online Conversations.},
	booktitle = {International Conference on Intelligent User Interfaces  },
	series = {Proceedings of the 12th international conference on Intelligent user interfaces},
	year = {2007},
	month = {28/01/2007},
	pages = {62-71},
	publisher = {ACM},
	organization = {ACM},
	address = {Honolulu, Hawaii},
	isbn = {1-59593-481-2},
	author = {F. Harper and D. Frankowski and Drenner, S. and Y. Ren and S. Kiesler and Terveen, L. and Kraut, R. and Riedl, J.}
}
@article {flosswp352,
	title = {A test of Lazear{\textquoteright}s theory of entrepreneurship in the Open Source Software virtual community},
	year = {2007},
	month = {March},
	abstract = {This paper studies the emergence of entrepreneurs and their skill profile in the open source software community. We test the hypothesis that entrepreneurs, carrying out complex, multi-task activities, have more balanced skill sets compared with individuals who are less involved in project management activities. Our empirical analysis employs the SourceForge dataset containing information on 77,039 individuals working in 54,229 OSS projects. We estimate logit and ordered logit models to explore the likelihood that an individual is a project founder or manager. Our main regressors include individual attributes like skill level and diversity, and project-level controls. Results support our hypothesis.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/giurirullanitorrisi.pdf},
	author = {Paola Giuri and Francesco Rullani and Salvatore Torrisi}
}
@conference {666,
	title = {Toward a New Industrial Organization? OSS in Economic and Managerial Perspective},
	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 = {377 - 379},
	publisher = {Springer},
	organization = {Springer},
	chapter = {50},
	abstract = {At present, an more and more users are running Open Source software (OSS) on their systems. Major companies, like IBM, Oracle, or Sun Microsystems, have now started to make significant investments in developing open communities and creating a portfolio of systems incorporating OSS applications into their design. Meanwhile, an increasing number of firms are entering the market by offering OSS-based solutions to their customers, often supplying a mix of proprietary and open solutions through hybrid business models. In this context, economists and management scientists are now moving beyond the state of puzzlement that has driven much of the initial attention towards OSS. Located in the context of OSS2007 in order to foster close and fruitful interactions with scholars from various other disciplines, this workshop aims at contributing to the current evolutions of the economic and managerial research agendas about OSS, and thus to provide, first, an assessment of where we {\textemdash} economics and management scholars - are about OSS, and, second, an analysis of the renewed directions in which we should consider inquiring further in the near future, focusing notably on business, production, diffusion and innovation models.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_50},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Toward\%20a\%20new\%20indusctial\%20Org.pdf},
	author = {Dalle, Jean and Cristina Rossi and Francesco Rullani}
}
@conference {1006,
	title = {Towards a Theoretical Model for Software Growth},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {21 - 21},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Software growth (and more broadly, software evolution) is usually considered in terms of size or complexity of source code. However in different studies, usually different metrics are used, which make it difficult to compare approaches and results. In addition, not all metrics are equally easy to calculate for a given source code, which leads to the question of which one is the easiest to calculate without losing too much information. To address both issues, in this paper present a comprehensive study, based on the analysis of about 700,000 C source code files, calculating several size and complexity metrics for all of them. For this sample, we have found double Pareto statistical distributions for all metrics considered, and a high correlation between any two of them. This would imply that any model addressing software growth should produce this Pareto distributions, and that analysis based on any of the considered metrics should show a similar pattern, provided the sample of files considered is large enough.},
	keywords = {C, complexity, evolution, freebsd, growth, halstead, lines of code, loc, mccabe, metrics, scm, size, sloc, sloccount, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300021.pdf},
	author = {Herraiz, Israel and Jesus M. Gonzalez-Barahona and Gregorio Robles}
}
@article {flosswp341,
	title = {Towards an Open Ontology for Emergency Response},
	year = {2007},
	month = {January},
	abstract = {Emergency Response and Relief Coordination Efforts are evolving to leverage the efficiencies offered by the internet in the area of real time communication among agents and stakeholders. There is widespread consensus both in the technical and ER community that to improve efficiency of response, information must be shared and web based protocols must be used [22]. In addition to known technical and non-technical obstacles that inhibit the effective and seamless coordination of operations, we identify issues that challenge the development of functional information and communication models. Recent studies in ontology engineering, and evidence from direct observations of open-source work groups in this field, point to the need for an easy to use {\textquoteright}open{\textquoteright} conceptual and semantic framework, defined here broadly as ???Open Ontology??? (OOnt), and a corresponding design and implementation methodology that can be referenced unambiguously and universally by developers and users of information systems designed to support ER operations.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/TOWARDS_AN_OPEN_ONTOLOGY_FOR_ER.pdf},
	author = {Paola Di Maio}
}
@article {495,
	title = {Towards an understanding of FLOSS: Infrastructures, Materiality and the Digital Business Ecosystem},
	journal = {Science Studies},
	number = {2},
	year = {2007},
	abstract = {In this paper we present empirical work detailing the engagement practices of a large FLOSS project, the Digital Business Ecosystem (DBE). In common with many other FLOSS projects, the DBE project focused on the development of infrastructural software components. Infrastructures and FLOSS software exhibit multiplicity: as objects they both change and stay the same. Whilst the implications of multiplicity with respect to infrastructure have been well-documented, with respect to FLOSS, they remain under-explored. Through examining how the DBE engaged new participants we were able to explore the nature of the FLOSS software object by asking the implied question: engagement with what? We draw on recent analysis by Law and Singleton to show how the innovative yet non-existent potentiality of the DBE was as significant to engagement as its steadily growing codebase. We argue that acknowledging the materiality and immateriality of the FLOSS software object has important consequences for management of, and engagement with, FLOSS projects.},
	keywords = {engagement, FLOSS, infrastructures, INNOVATION, materiality},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Darking_Whitley.pdf},
	author = {Mary Darking and Edgar A Whitley}
}
@conference {1724,
	title = {On Understanding How to Introduce an Innovation to an Open Source Project},
	booktitle = {First International Workshop on Emerging Trends in FLOSS Research and Development (FLOSS{\textquoteright}07: ICSE Workshops 2007)First International Workshop on Emerging Trends in FLOSS Research and Development (FLOSS{\textquoteright}07: ICSE Workshops 2007)},
	year = {2007},
	pages = {12 - 12},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {We propose to research the introduction of Software Engineering inventions into Open Source projects (1) to help researchers with creating opportunities for evaluating their tools, methods and process designs in real-life settings, and (2) to help Open Source projects with improving their processes based on state-of-the-art knowledge. Such research will go beyond diffusion and dissemination of inventions to active introduction, and thus increase the chances of adoption. We will discuss the research approach, our preliminary insights, limitations of the approach, and why researchers interested in evaluating their own inventions should be interested in this research. 
},
	isbn = {0-7695-2961-5},
	doi = {10.1109/FLOSS.2007.11},
	author = {Oezbek, Christopher and Prechelt, Lutz}
}
@inbook {880,
	title = {Understanding the Development of Free E-Commerce/E-Business Software: A Resource-Based View},
	booktitle = {Emerging Free and Open Source Software Practices},
	year = {2007},
	pages = {170-190},
	publisher = {IGI Publishing},
	organization = {IGI Publishing},
	address = {Hershey, PA},
	author = {Walt Scacchi},
	editor = {Sowe, S.K. and Stamelos, I. and Samoladas, I}
}
@conference {1226,
	title = {Understanding the KDE Social Structure through Mining of Email Archive},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	note = {"Our data source is constituted by e-mails sent to KDE mailing-lists and archived by MARC"

"Two problems quickly arise: neither the e-mails addresses nor the names can be considered unique. Consequently, we used an in-depth search algorithm to put together {\textquotedblleft}name-email{\textquotedblright} couples corresponding to a same contributor. Indeed, the algorithm suggests possible merges."

"There is a specific mailing list in our data set, kde-commit, which gathers automatic notifications from the revision control system (RCS)....We measure {\textquotedblleft}commit{\textquotedblright} by the number of messages sent to the {\textquotedblleft}kde-commit{\textquotedblright} mailing list. However, we did not count {\textquotedblleft}silent{\textquotedblright} commits, nor usual messages sent to this mailing list."

"We measured activities done in BTS in two ways: {\textquotedblleft}bug opener{\textquotedblright} and {\textquotedblleft}non bug opener{\textquotedblright}.	First, we counted the number of modifications done by the contributor who opened the concerned bug report. "
},
	abstract = {In order to achieve a better understanding of FLOSS social structure, we need a definition of social position. From a theoretical perspective, we propose to think the participation as a trajectory. Empirically, we use optimal matching to build a typology of participation trajectories based on KDE email archives. We show how these trajectories structure the community as a whole by combining these results with a social network analysis.},
	keywords = {bug tracking system, bugzilla, commit, email, email archive, kde, mailing list, participation, revision control, social network analysis},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd_studer_et_all_full.pdf},
	author = {Studer, Matthias and M{\"u}ller, Beno{\^\i}t and Ritschard, Gilbert}
}
@unpublished {flosswp366,
	title = {The use of open source GIS software and its impact on organizations},
	year = {2007},
	month = {September},
	abstract = {This thesis explores the reasons behind the poor level of adoption of open source web GIS software, and whether it is due to poor awareness about open source concepts or due to technical deficiencies in the open source tools. The research was done in 2 major phases; the first phase involved conducting surveys to measure the awareness and attitudes towards open source. The surveys examined three categories of people involved in the IT industry, namely: decision makers, software developers, and end users. The measurement of awareness was done by developing an Awareness Indicator and a Sentiment Indicator for each category. These indicators were developed by the author during the course of the study in order to provide a measurable and descriptive indication of the results. The second phase involved performing a comparative analysis between MapServer a leading open source web GIS tool, and three of the leading proprietary web GIS software, namely: ESRI???s ArcIMS, Intergraph???s GeoMedia WebMap, and MapInfo???s MapXtreme. The results of the research provide an insight on how different categories of people view open source, and demonstrate that lack of awareness about open source concepts and its competencies may be a major reason behind the poor adoption of open source solutions. The results of the comparative analysis also demonstrate that MapServer is technically equivalent to its commercial counter parts.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OS_GIS.pdf},
	author = {Mahmoud Refaat Nasr}
}
@conference {644,
	title = {The Use of Open Source Software in Enterprise Distributed Computing Environments},
	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 = {277 - 282},
	publisher = {Springer},
	organization = {Springer},
	chapter = {28},
	abstract = {Firms increasingly rely on open source software for solving business problems and building mission-critical IT solutions. However, there are numerous issues associated with OSS, including its influence on the total cost of ownership (TCO) and supportability and upgradeability risks. While savings from obtaining a free copy of the software can be significant, software accounts for an average of 10\% of TCO, while the majority of the costs are associated with project staffing. OSS requires significant investment into staffing because it needs to be carefully selected, customized, and installed. In addition, global communities may gather and dissolve at their will, so guarantees of support, revision, and bug fixes are minimal. Yet companies can gain competitive advantage through an ability to customize software to address specific business issues and exercising control over development, revision schedules, and modifications. OSS is not a panacea from the rising software costs. Instead, it is a serious initiative that has benefits, disadvantages, and risks associated with it.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_28},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Use\%20of\%20OSS\%20in\%20Enterprise.pdf},
	author = {Krivoruchko, Jacob}
}
@article {1215,
	title = {Using FLOSSmole Data in Determining Business Readiness Ratings},
	journal = {2nd Workshop on Public Data about Software Development (WopDaSD 2007)},
	year = {2007},
	month = {2007},
	abstract = {This paper is a preliminary report on using FLOSSmole data retrieved from open source repositories (forges) to calculate Business Readiness Rating scores.  },
	keywords = {brr, business readiness rating, flossmole},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Using\%20FLOSSmole\%20Data\%20in\%20Determining\%20Business\%20Readiness\%20Ratings.pdf},
	author = {Wasserman, Anthony and Ashutosh Das}
}
@conference {628,
	title = {Using Repository of Repositories (RoRs) to Study the Growth of F/OSS Projects: A Meta-Analysis Research Approach},
	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 = {147 - 160},
	publisher = {Springer},
	organization = {Springer},
	chapter = {12},
	abstract = {Free/Open Source Software (F/OSS) repositories contain valuable data and their usefulness in studying software development and community activities continues to attract a lot of research attention. A trend in F/OSS studies is the use of metadata stored in a repository of repositories or RoRs. This paper utilizes data obtained from such RoRs -FLOSSmole- to study the types of projects being developed by the F/OSS community. We downloaded projects by topics data in five areas (Database, Internet, Software Development, Communications, and Games/Entertainment) from Flossmole{\textquoteright}s raw and summary data of the sourceforge repository. Time series analysis show the numbers of projects in the five topics are growing linearly. Further analysis supports our hypothesis that F/OSS development is moving {\textquotedblleft}up the stack{\textquotedblright} from developer tools and infrastructure support to end-user applications such as Databases. The findings have implications for the interpretation of the F/OSS landscape, the utilization and adoption of open source databases, and problems researchers might face in obtaining and using data from RoRs.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_12},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Using\%20Repository\%20of\%20Repositories.pdf},
	author = {Sowe, Sulayman and Lefteris Angelis and Stamelos, I. and Y. Manolopoulos}
}
@conference {1009,
	title = {Using Software Distributions to Understand the Relationship among Free and Open Source Software Projects},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {24 - 24},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Success in the open source software world has been measured in terms of metrics such as number of downloads, number of commits, number of lines of code, number of participants, etc. These metrics tend to discriminate towards applications that are small and tend to evolve slowly. A problem is, however, how to identify applications in these latter categories that are important. Software distributions specify the dependencies needed to build and to run a given software application. We use this information to create a dependency graph of the applications contained in such a distribution. We explore the characteristics of this graph, and use it to define some metrics to quantify the dependencies (and dependents) of a given software application. We demonstrate that some applications that are invisible to the final user (such as libraries) are widely used by end-user applications. This graph can be used as a proxy to measure success of small, slowly evolving free and open source software.},
	keywords = {dependencies, evolution, fink, metrics},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.32},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300024.pdf},
	author = {Daniel M. German}
}
@conference {1010,
	title = {Using Software Repositories to Investigate Socio-technical Congruence in Development Projects},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {25 - 25},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {We propose a quantitative measure of socio-technical congruence as an indicator of the performance of an organization in carrying out a software development project. We show how the information necessary to implement that measure can be mined from commonly used software repositories, and we describe how socio-technical congruence can be computed based on that information.},
	keywords = {developers, graph, scm, social networks, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300025.pdf},
	author = {Valetto, Giuseppe and Helander, Mary and Ehrlich, Kate and Chulani, Sunita and Wegman, Mark and Williams, Clay}
}
@conference {881,
	title = {Value Capture and Value Networks in Open Source Vendor Strategies},
	booktitle = {40th Annual Hawaii International Conference on System Sciences (HICSS{\textquoteright}07)},
	year = {2007},
	pages = {176 - 176},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, HI, USA},
	isbn = {0-7695-2755-8},
	author = {Joel West}
}
@conference {998,
	title = {Visual Data Mining in Software Archives to Detect How Developers Work Together},
	booktitle = {Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {9 - 9},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Analyzing the check-in information of open source software projects which use a version control system such as CVS or SUBVERSION can yield interesting and important insights into the programming behavior of developers. As in every major project tasks are assigned to many developers, the development must be coordinated between these programmers.

This paper describes three visualization techniques that help to examine how programmers work together, e.g. if they work as a team or if they develop their part of the software separate from each other. Furthermore, phases of stagnation in the lifetime of a project can be uncovered and thus, possible problems are revealed.

To demonstrate the usefulness of these visualization techniques we performed case studies on two open source projects. In these studies interesting patterns of developers? behavior, e.g. the specialization on a certain module can be observed. Moreover, modules that have been changed by many developers can be identified as well as such ones that have been altered by only one programmer.},
	keywords = {change, coordination, cvs, developers, junit, modules, scm, source code, svn, teams, tomcat, visualization},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.34},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300009.pdf},
	author = {Weissgerber, Peter and Pohl, Mathias and Burch, Michael}
}
@article {flosswp334,
	title = {Voluntary Engagement in an Open Web-based Encyclopedia: Wikipedians, and Why They Do It},
	year = {2007},
	month = {January},
	abstract = {The online encyclopedia Wikipedia can be considered as a highly successful Open Content project, written and maintained completely by volunteers. Little is known, however, about the motives and interests of these volunteers. Results from an online survey among 106 contributors to the German Wikipedia project are presented. As potential predictors of contributors??? engagement and satisfaction, both motives derived from social sciences (e.g., costs-benefits, valence of the Wikipedia goals, identification with Wikipedia, etc.) as well as perceived task characteristics (e.g., task significance, autonomy, skill variety, etc.) were measured. The results reveal that satisfaction ratings of contributors are determined by perceived benefits, identification with the Wikipedia community, and task characteristics. Contributors??? engagement (e.g., hours per week) was particularly determined by their tolerance for opportunity costs and the experienced characteristics of their tasks, the latter effect being partially mediated by intrinsic motivation. Most relevant task characteristics both for contributors??? engagement and satisfaction were autonomy, task significance, and skill variety. Additional motives reported by Wikipedia contributors suggest the importance of generativity.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Schroer_Hertel_Wikipedia_Motivation.pdf},
	author = {Joachim Schroer and Guido Hertel}
}
@conference {807,
	title = {Web Mash-ups and Patchwork Prototyping: User-driven technological innovation with Web 2.0 and Open Source Software},
	booktitle = {2007 40th Annual Hawaii International Conference on System Sciences (HICSS{\textquoteright}07)2007 40th Annual Hawaii International Conference on System Sciences (HICSS{\textquoteright}07)},
	year = {2007},
	pages = {86 - 86},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, HI, USA},
	abstract = {The recent emergence of web mash-ups and open
source software is driving the development of new
practices in software and systems development. In this
paper we explore novel practices of user-driven
innovation through an examination of several case
studies which illustrate how users and developers are
exploiting the proliferation of open APIs and open
source systems. Developers can rapidly create proofs
of concept that are robust enough for actual use by
combining preexisting software components. The
underlying programming processes involved make use
of tried-and-true software development techniques,
and may not appear innovative at first. However, the
application of these practices and techniques to
problem solving by non-programmers shows a high
degree of creative innovation, giving rise to new ways
of thinking about technology design and production.},
	isbn = {0-7695-2755-8},
	issn = {1530-1605},
	doi = {10.1109/HICSS.2007.612},
	author = {Floyd, I.R. and Jones, M.C. and Rathi, D. and Twidale, M.B}
}
@conference {1008,
	title = {What Can OSS Mailing Lists Tell Us? A Preliminary Psychometric Text Analysis of the Apache Developer Mailing List},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {23 - 23},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Developer mailing lists are a rich source of information about Open Source Software (OSS) development. The unstructured nature of email makes extracting information difficult. We use a psychometrically-based linguistic analysis tool, the LIWC, to examine the Apache httpd server developer mailing list. We conduct three preliminary experiments to assess the appropriateness of this tool for information extraction from mailing lists. First, using LIWC dimensions that are correlated with the big five personality traits, we assess the personality of four top developers against a baseline for the entire mailing list. The two developers that were responsible for the major Apache releases had similar personalities. Their personalities were different from the baseline and the other developers. Second, the first and last 50 emails for two top developers who have left the project are examined. The analysis shows promise in understanding why developers join and leave a project. Third, we examine word usage on the mailing list for two major Apache releases. The differences may reflect the relative success of each release.},
	keywords = {apache, developers, email, joining, liwc, mailing lists, personality},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.35},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300023.pdf},
	author = {Peter C. Rigby and Hassan, Ahmed E.}
}
@article {flosswp338,
	title = {What motivates Wikipedians: motivations for Wikipedia content contribution},
	year = {2007},
	month = {January},
	abstract = {Contributors??? motivations are critical for sustaining Wikipedia and other collaborative user-generated content outlets. Such outlets are based on contributions by people who volunteer their time and talent for the creation of content in return for no monetary reward. Therefore, in order to understand what underlies user-generated content contribution, we would need to find out what motivates volunteer content contributors. The results of a survey of 151 Wikipedia contributors indicate that the top motivations for contribution are Fun and Ideology. As expected, it was found that the levels of each of the motivations Fun, Values, Understanding, Enhancement, Protective, and Career were positively correlated with contribution level. Somewhat unexpectedly, contribution level was not correlated significantly with the Ideology and Social motivations.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Nov_Wikipedia_motivations_opensource.mit.edu.pdf},
	author = {Oded Nov}
}
@conference {1213,
	title = {Working with Open Source Development Data: Considerations triggered by a study of bug scenarios},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	month = {2007},
	abstract = {The retrieval and preparation of public data on software development calls for more than just technical skills. In 
addition, care and judgement are needed to avoid disproportionate costs to the providers of data or unnecessary embarrassment to the participants tracked in the data. Taking the extraction of bug scenarios as a use case, we illustrate these concerns and discuss how they could be translated into social requirements that would help to make retrieval and preparation a sustainable exercise. In particular, we call for more efforts to establish institutional repositories of public data on software development and, besides, we suggest that reviewers could play a role in making sure that empirical research is performed in a way that does not bring the long-term relationship between software developers and researchers in jeopardy. },
	keywords = {bug reports, bug scenarios, Data Collection},
	attachments = {https://flosshub.org/sites/flosshub.org/files/denBesten-wopdasd.pdf},
	author = {den Besten, Matthijs and Masmoudi, H{\'e}la and Jean-Michel Dalle}
}
@proceedings {91,
	title = {An absorptive capacity perspective of open source software development group performance},
	year = {2006},
	keywords = {NotreDameArchive},
	author = {Sherae Daniel and Ritu Agarwal and Katherine Stewart}
}
@conference {679,
	title = {Adopting Open Source for Mission-Critical Applications: A Case Study on Single Sign-On},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {209 - 220},
	publisher = {Springer},
	organization = {Springer},
	abstract = {In this paper, we describe a specific selection process for security-related open source code, based on a methodology aimed at evaluating open source security frameworks in general and Single-Sign-On (SSO) systems in particular. Our evaluation criteria for open source security-related software include the community{\textquoteright}s timeliness of reaction against newly discovered vulnerabilities or incidents.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_21},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Adapting\%20OS\%20for\%20Mission-critical\%20Applications.pdf},
	author = {Ardagna, Claudio and Damiani, Ernesto and Frati, Fulvio and Reale, Salvatore}
}
@conference {Tsunoda:2006:AOD:1137983.1138031,
	title = {Analyzing OSS developers{\textquoteright} working time using mailing lists archives},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {181{\textendash}182},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Our mining question is {\textquotedblleft}when OSS developers work?{\textquotedblright} OSS developers{\textquoteright} working time may be a good indicator to understand the development style of a project. (For example, if many developers work in office hour, these might be daily works in a company.)},
	keywords = {developers, email, email archives, mailing lists, mining challenge, msr challenge, overtime work, postgresql, workload},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138031},
	url = {http://doi.acm.org/10.1145/1137983.1138031},
	attachments = {https://flosshub.org/sites/flosshub.org/files/181AnalyzingOSS.pdf},
	author = {Tsunoda, Masateru and Monden, Akito and Kakimoto, Takeshi and Kamei, Yasutaka and Matsumoto, Ken-ichi}
}
@article {120,
	title = {Applying Social Network Analysis Techniques to Community-Driven Libre Software Projects},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	abstract = {Source code management repositories of large, long-lived libre (free, open source) software projects can be a source of valuable data about the organizational structure, evolution, and knowledge exchange in the corresponding development communities. Unfortunately, the sheer volume of the available information renders it almost unusable without applying methodologies which highlight the relevant information for a given aspect of the project. Such methodology is proposed in this article, based on well known concepts from the social networks analysis field, which can be used to study the relationships among developers and how they collaborate in different parts of a project. It is also applied to data mined from some well known projects (Apache, GNOME, and KDE), focusing on the characterization of their collaboration network architecture. These cases help to understand the potentials of the methodology and how it is applied, but also shows some relevant results which open new paths in the understanding of the informal organization of libre software development communities.},
	keywords = {apache, conway{\textquoteright}s law, cvs, gnome, kde, scm, social network analysis, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/06_Lopez_ijitwe_sna.pdf},
	author = {L{\'o}pez-Fern{\'a}ndez, L. and Gregorio Robles and Jesus M. Gonzalez-Barahona and Herraiz, I.}
}
@conference {D{\textquoteright}Ambros:2006:AER:1137983.1138029,
	title = {Applying the evolution radar to PostgreSQL},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {177{\textendash}178},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	keywords = {cvs, documentation, evolution, evolution radar, logical coupling, makefile, mining challenge, msr challenge, postgresql, re-engineering, refactoring, release history, rhdb, source code, version control, visualization},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138029},
	url = {http://doi.acm.org/10.1145/1137983.1138029},
	attachments = {https://flosshub.org/sites/flosshub.org/files/177ApplyingEvolution.pdf},
	author = {D{\textquoteright}Ambros, Marco and Lanza, Michele}
}
@conference {WeiBgerber:2006:RLE:1137983.1138011,
	title = {Are refactorings less error-prone than other changes?},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {112{\textendash}118},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Refactorings are program transformations which should preserve the program behavior. Consequently, we expect that during phases when there are mostly refactorings in the change history of a system, only few new bugs are introduced. For our case study we analyzed the version histories of several open source systems and reconstructed the refactorings performed. Furthermore, we obtained bug reports from various sources depending on the system. Based on this data we identify phases when the above hypothesis holds and those when it doesn{\textquoteright}t.},
	keywords = {argouml, bug reports, bugs, change history, jedit, junit, re-engineering, refactoring, reverse engineering, software evolution, version control},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138011},
	url = {http://doi.acm.org/10.1145/1137983.1138011},
	attachments = {https://flosshub.org/sites/flosshub.org/files/112AreRefactorings.pdf},
	author = {Wei{\ss}gerber, Peter and Diehl, Stephan}
}
@article {85,
	title = {Assessing the health of open source communities},
	journal = {Computer},
	volume = {39},
	number = {5},
	year = {2006},
	note = {Times Cited: 0},
	pages = {89-91},
	author = {Kevin Crowston and James Howison}
}
@conference {887,
	title = {Because I Carry My Cell Phone Anyway: Functional Location-Based Reminder Applications},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2006},
	month = {22/04/2006},
	pages = {889-898},
	publisher = {ACM},
	organization = {ACM},
	address = {Montreal, Quebec, Canada},
	isbn = {1-59593-372-7},
	author = {Ludford, P. and D. Frankowski and Reily, K. and Wilms, K. and Terveen, L.}
}
@conference {680,
	title = {Beyond Low-Hanging Fruit: Seeking the Next Generation in FLOSS Data Mining},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {47 - 56},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper will discuss the motivations and methods for collecting quantitative data about free, libre and open source (FLOSS) software projects. The paper also describes the current state of the art in collecting this data, and some of the problems with this process. Finally, the paper outlines the challenges data miners should look forward to when trying to improve the usefulness of their quantitative data streams.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Beyond\%20Low-Hanging\%20Fruit.pdf},
	author = {Conklin, Megan}
}
@booklet {507,
	title = {Bringing Open Source Software to the Desktop : An In-Depth Study of the Implementation and use of Star Office},
	year = {2006},
	month = {Sept},
	abstract = {Open Source software is coming to the attention of individuals, organisations, and governments worldwide, and is increasingly being adopted by firms for specific business purposes. However, the uptake of end-user desktop OSS applications to date has been modest, and Microsoft products remain the de-facto standard on the corporate desktop. This brings into sharp focus one of the most challenging questions faced by the Open Source community today ... namely, if organisations value low acquisition costs, low total cost of ownership of software, potentially plentiful support, free access to source code, and the wish to avoid proprietary software vendor lock-in, why have more organisations not adopted OSS?  This paper contributes to the existing research by reporting on an in-depth, interpretive, processual study of an attempt by a large Irish Trade Union to replace Microsoft Office with an Open Source alternative, StarOffice.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Bringing_OSS_to_the_Desktop.pdf},
	author = {PJ Wall and Seamas Kelly}
}
@conference {681,
	title = {Call for Quality: Open Source Software Quality Observation},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {57 - 62},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper describes how a Software Quality Observatory works to evaluate and quantify the quality of an Open Source project. Such a quality measurement can be used by organizations intending to deploy an Open Source solution to pick one of the available projects for use. We offer a case description of how the Software Quality Observatory will be applied to the KDE project to document and evaluate its quality practices for outsiders.
},
	keywords = {kde, quality},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Call\%20for\%20Quality.pdf},
	author = {de Groot, Adriaan and K{\"u}gler, Sebastian and Adams, Paul and Gousios, Giorgos}
}
@conference {Gurbani:2006:CSC:1134285.1134352,
	title = {A case study of a corporate open source development model},
	booktitle = {Proceedings of the 28th international conference on Software engineering},
	series = {ICSE {\textquoteright}06},
	year = {2006},
	pages = {472{\textendash}481},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source practices and tools have proven to be highly effective for overcoming the many problems of geographically distributed software development. We know relatively little, however, about the range of settings in which they work. In particular, can corporations use the open source development model effectively for software projects inside the corporate domain? Or are these tools and practices incompatible with development environments, management practices, and market-driven schedule and feature decisions typical of a commercial software house? We present a case study of open source software development methodology adopted by a significant commercial software project in the telecommunications domain. We extract a number of lessons learned from the experience, and identify open research questions.},
	keywords = {architecture, case study, open source, session initiation protocol, software development, vkg},
	isbn = {1-59593-375-1},
	doi = {10.1145/1134285.1134352},
	url = {http://doi.acm.org/10.1145/1134285.1134352},
	author = {Gurbani, Vijay K. and Garvert, Anita and Herbsleb, James D.}
}
@article {891,
	title = {Challenges of open innovation: the paradox of firm investment in open-source software},
	journal = {R\&D Management},
	volume = {36},
	year = {2006},
	month = {06/2006},
	pages = {319 - 331},
	abstract = {<p>\&nbsp;<span class="Apple-style-span" style="font-size: 13px; border-collapse: collapse; line-height: 16px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">Open innovation is a powerful framework encompassing the generation, capture, and employment of intellectual property at the firm level. We identify three fundamental challenges for firms in applying the concept of open innovation: finding creative ways to exploit internal innovation, incorporating external innovation into internal development, and motivating outsiders to supply an ongoing stream of external innovations. This latter challenge involves a paradox, why would firms spend money on R\&amp;D efforts if the results of these efforts are available to rival firms? To explore these challenges, we examine the activity of firms in open-source software to support their innovation strategies. Firms involved in open-source software often make investments that will be shared with real and potential rivals. We identify four strategies firms employ</span></p>},
	author = {Joel West and Gallagher, Scott}
}
@conference {Beyer:2006:CVA:1137983.1138023,
	title = {Co-change visualization applied to PostgreSQL and ArgoUML: (MSR challenge report)},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {165{\textendash}166},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Co-change visualization is a method to recover the subsystem structure of a software system from the version history, based on common changes and visual clustering. This paper presents the results of applying the tool CCVisu which implements co-change visualization, to the two open-source software systems PostgreSQL and ArgoUML The input of the method is the co-change graph, which can be easily extracted by CCVisu from a Cvs version repository. The output is a graph layout that places software artifacts that were often commonly changed at close positions, and artifacts that were rarely co-changed at distant positions. This property of the layout is due to the clustering property of the underlying energy model,which evaluates the quality of a produced layout. The layout can be displayed on the screen, or saved to a file in SVG or VRML format.},
	keywords = {argouml, ccvisu, cvs, force-directed graph layout, graph, mining challenge, msr challenge, postgresql, software clustering, software structure analysis, software visualization, version control, visualization},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138023},
	url = {http://doi.acm.org/10.1145/1137983.1138023},
	attachments = {https://flosshub.org/sites/flosshub.org/files/165Co-Change.pdf},
	author = {Beyer, Dirk}
}
@conference {682,
	title = {Collaborative Maintenance in Large Open-Source Projects},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {233 - 244},
	publisher = {Springer},
	organization = {Springer},
	abstract = {The paper investigates collaborative work among maintainers of open source software by analyzing the logs of a set of 10 large projects. We inquire whether teamwork can be influenced by several characteristics of code. Preliminary results suggest that collaboration among maintainers in most large open-source projects seems to be positively influenced by file vintage and by Halstead volume of files, and negatively by McCabe complexity and size measured in SLOCs. These results could be consistent with an increased attractivity of files created early in the history of a project, and with maintainers being less attracted by more verbose code and by more complex code, although in this last case it might also reflect the fact that more complex files would be de facto more exclusive in terms of maintenance.
},
	keywords = {apache, COLLABORATION, complexity, cvs, gaim, gcc, ghostscript, halstead, lines of code, loc, mccabe, mozilla, netbsd, openssh, postgresql, python, sloc},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Collaborative\%20Maintenance.pdf},
	author = {den Besten, Matthijs and Jean-Michel Dalle and Galia, Fabrice}
}
@unpublished {flosswp336,
	title = {Commons Identity: A Conceptual Model for Designing Brand Identity in Free and Open Source Software Projects},
	year = {2006},
	month = {September},
	abstract = {Purpose: Open Source is a popular term to describe a development and production method based on the free sharing of information. The computer software industry has embraced Open Source practices increasingly since the nineties. Participation in Free and Open Source Software projects is commonly voluntary and there is a need for specialized knowledge surrounding the production of software. This report focuses on the topic area of designing brand identity. Objective: To create a conceptual model for designing brand identity in Free and Open Source Software projects based on Wheeler???s Brand Identity Process of 2006. Design: Participatory action research with three cycles and five interviews conducted online. Participants: Three Free and Open Source Software projects named Sociopath, OpenEats, and Jajuk. Five industry professionals with expertise in branding and Open Source development. Results: Wheeler???s brand identity process is modified towards the Open Source method and incorporates community votes and commons-based peer-review. Outcomes specific to Free and Open Source Software projects are included as exemplary brand identity assets. Furthermore, a preparation phase is added showing the entry into the project???s community. Conclusions: The created model is a practical tool for designing brand identity in Free and Open Source Software projects. Further applications of the model are needed for its evaluation.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/commons_identity.pdf},
	author = {Nicolas Schudel}
}
@conference {683,
	title = {Communication Networks in an Open Source Software Project},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {297 - 306},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This study explores the nature of the social network and the patterns of communication that exist in an open source software development project, the Apache HTTP (WEB) server project. Our analysis of archival data on email communications between developers in the Apache HTTP server project suggests an interesting pattern of communication. We find that the core developers self-organize into three sub-groups that communicate intensely in completing the project. Our analysis also reveals that a few prominent developers who are centrally located in the network are driving communications within the project. We identify the implications of our findings and suggest areas for further research.
},
	keywords = {apache, core, developers, email, email archive, mailing list, participation, social network analysis},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_30},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Communication\%20Networks\%20in\%20an\%20Open\%20Source.pdf},
	author = {Roberts, Jeffrey and Il-Horn Hann and Sandra Slaughter}
}
@conference {684,
	title = {Comparing macro development for personal productivity tools: an experience in validating accessibility of Talking Books},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {247 - 252},
	publisher = {Springer},
	organization = {Springer},
	abstract = {We describe an experience in developing macros for both Power Point and Impress, to be used in accessibility validation for educational multimedia (Talking Books) designed for visually impaired people. Minor disadvantages in the use of Impress are outlined, which however do not constitute a serious obstacle to adoption of Open Source tools for our purposes.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_24},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Comparing\%20macro\%20development.pdf},
	author = {Dodero, Gabriella and Lupi, Katia and Piffero, Erika}
}
@conference {Herraiz:2006:CSN:1116163.1116405,
	title = {Comparison Between SLOCs and Number of Files As Size Metrics for Software Evolution Analysis},
	booktitle = {Proceedings of the Conference on Software Maintenance and Reengineering},
	series = {CSMR {\textquoteright}06},
	year = {2006},
	pages = {206{\textendash}213},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	keywords = {empirical studies, libre software, metrics, software evolution},
	isbn = {0-7695-2536-9},
	url = {http://dl.acm.org/citation.cfm?id=1116163.1116405},
	author = {Herraiz, Israel and Gregorio Robles and Gonzalez-Barahon, Jes us M.}
}
@conference {685,
	title = {Conceptual Modelling as a New Entry in the Bazaar: The Open Model Approach},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {9 - 20},
	publisher = {Springer},
	organization = {Springer},
	abstract = {The present contribution proposes to transfer the main principles of open source software development to a new context: conceptual modelling; an activity closely related to software development. The goal of the proposed {\textquotedblleft}open model{\textquotedblright} approach is to collaboratively develop reference models for everyone to copy, use and refine in a public process. We briefly introduce conceptual modelling and reference models, discuss the cornerstones of an open modelling process, and propose a procedure for initiating, growing and sustaining an open model project. The paper concludes with a discussion of potential benefits and pitfalls.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_2},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Conceptual\%20Modelling\%20as\%20a\%20New\%20Entry.pdf},
	author = {Koch, Stefan and Strecker, Stefan and Frank, Ulrich}
}
@conference {686,
	title = {Contributor Turnover in Libre Software Projects},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {273 - 286},
	publisher = {Springer},
	organization = {Springer},
	abstract = {A common problem that management faces in software companies is the high instability of their staff. In libre (free, open source) software projects, the permanence of developers is also an open issue, with the potential of causing problems amplified by the self-organizing nature that most of them exhibit. Hence, human resources in libre software projects are even more difficult to manage: developers are in most cases not bound by a contract and, in addition, there is not a real management structure concerned about this problem. This raises some interesting questions with respect to the composition of development teams in libre software projects, and how they evolve over time. There are projects lead by their original founders (some sort of {\textquotedblleft}code gods{\textquotedblright}), while others are driven by several different developer groups over time (i.e. the project {\textquotedblleft}regenerates{\textquotedblright} itself). 
In this paper, we propose a quantitative methodology, based on the analysis of the activity in the source code management repositories, to study how these processes (developers leaving, developers joining) affect libre software projects. The basis of it is the analysis of the composition of the core group, the group of developers most active in a project, for several time lapses. We will apply this methodology to several large, well-known libre software projects, and show how it can be used to characterize them. In addition, we will discuss the lessons that can be learned, and the validity of our proposal.
},
	keywords = {apache, committers, core, cvs, cvsanaly, developers, evolution, freebsd, gimp, gnome, kde, mono, mozilla},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_28},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Contributor\%20Turnover\%20in\%20Libre\%20Software\%20Projects.pdf},
	author = {Gregorio Robles and Gonzalez-Barahona, Jesus}
}
@article {90,
	title = {Core and periphery in Free/Libre and Open Source software team communications},
	journal = {Proceedings of the 39th Annual Hawaii International Conference on System Sciences-Volume 06},
	year = {2006},
	abstract = {The concept of the core group of developers is important and often discussed in empirical studies of FLOSS projects. This paper examines the question, "how does one empirically distinguish the core?" Being able to identify the core members of a FLOSS development project is important because many of the processes necessary for successful projects likely involve core members differently than peripheral members, so analyses that mix the two groups will likely yield invalid results. 

We compare 3 analysis approaches to identify the core: the named list of developers, a Bradford{\textquoteright}s law analysis that takes as the core the most frequent contributors and a social network analysis of the interaction pattern that identifies the core in a core-and-periphery structure. We apply these measures to the interactions around bug fixing for 116 SourceForge projects. The 3 techniques identify different individuals as core members; examination of which individuals are identified leads to suggestions for refining the measures. All 3 measures though suggest that the core of FLOSS projects is a small fraction of the total number of contributors.},
	keywords = {bug fixing, contributions, contributors, core, developers, social network analysis, sourceforge, team},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and Howison, James}
}
@conference {687,
	title = {Critical Success Factors for Migrating to OSS-on-the-Desktop: Common Themes across Three South African Case Studies},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {287 - 293},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper investigates the critical success factors associated with the migration from proprietary desktop software to an open source software (OSS) desktop environment in a South African context. A comparative case study analysis approach was adopted whereby three organisations that have migrated to desktop OSS were analysed. For diversity, one case study each was drawn from government, private industry and the educational sector. Most of the findings agree with those in the available literature though there are notable differences in the relative importance of certain factors.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Critical\%20Success\%20Factors\%20for\%20Migrating.pdf},
	author = {Brink, Daniel and Roos, Llewelyn and Weller, James and Van Belle, Jean-Paul}
}
@conference {Sager:2006:DSJ:1137983.1138000,
	title = {Detecting similar Java classes using tree algorithms},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {65{\textendash}71},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Similarity analysis of source code is helpful during development to provide, for instance, better support for code reuse. Consider a development environment that analyzes code while typing and that suggests similar code examples or existing implementations from a source code repository. Mining software repositories by means of similarity measures enables and enforces reusing existing code and reduces the developing effort needed by creating a shared knowledge base of code fragments. In information retrieval similarity measures are often used to find documents similar to a given query document. This paper extends this idea to source code repositories. It introduces our approach to detect similar Java classes in software projects using tree similarity algorithms. We show how our approach allows to find similar Java classes based on an evaluation of three tree-based similarity measures in the context of five user-defined test cases as well as a preliminary software evolution analysis of a medium-sized Java project. Initial results of our technique indicate that it (1) is indeed useful to identify similar Java classes, (2)successfully identifies the ex ante and ex post versions of refactored classes, and (3) provides some interesting insights into within-version and between-version dependencies of classes within a Java project.},
	keywords = {change analysis, clones, coogle, eclipse, famix, java, similarity, software evolution, software repositories, source code, tree similarity measures},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138000},
	url = {http://doi.acm.org/10.1145/1137983.1138000},
	attachments = {https://flosshub.org/sites/flosshub.org/files/65Detecting.pdf},
	author = {Sager, Tobias and Bernstein, Abraham and Pinzger, Martin and Kiefer, Christoph}
}
@article {flosswp322,
	title = {Developer Learning Dynamics in Open Source Software Projects: A Hidden Markov Model Analysis},
	year = {2006},
	month = {December},
	abstract = {This work proposes a dynamic model of developer learning in open source software (OSS) projects. A Hidden Markov Model (HMM) is proposed to explain how the code contribution behaviors of OSS de-velopers change as their levels of knowledge on their projects increase. In this model, discrete hidden states represent the unobserved knowledge levels of developers, and their observed code contribution be-haviors are modeled as state dependent. Developers??? knowledge levels evolve as they learn about the pro-jects over time. Two modes of learning are considered: learning-by-doing (code development) and learn-ing through interactions with peers. The model is calibrated using data spanning six years for 25 OSS pro-jects and 251 developers hosted at Sourceforge. The proposed model identifies three knowledge states (high, medium, and low) and estimates the impact of the two modes of learning on the transition of devel-opers between the three knowledge states. The model results suggest that in the low knowledge state de-velopers exhibit the greatest inertia, followed by those in the medium and high states. Both modes of learning are found to have varying impact across the three knowledge states. Interactions with peers ap-pear to be an important source of learning for developers in all states. A developer in the low state learns only through participation in threads started by others. Prior code contribution and starting discussion by initiating threads do not impact the knowledge level of a developer in the low state. Initiating threads, par-ticipating in threads started by others, and prior code contributions have positive impacts on the knowl-edge level of a developer in the medium or high state and, hence, influence his long term code contribu-tion behavior. Explanations for these varying impacts of learning activities on the transitions of develop-ers between the three states are provided. We also find a lack of persistence of knowledge in all states. The HMM better describes the data than a latent class model which would suggests that the learning ac-tivities have a long term, dynamic impact, rather than an immediate, static impact on the code contribu-tion behavior of a developer.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/singh-youn-tan.pdf},
	author = {Param Vir Singh and Nara Youn and Yong Tan}
}
@conference {688,
	title = {Development Platforms as a Niche for Software Companies in Open Source Software},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {341 - 342},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Without Abstract},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Development\%20Platforms\%20as\%20a\%20Niche.pdf},
	author = {Savonnet, Marinette and Leclercq, Eric and Terrasse, Marie-No{\"e}lle and Grison, Thierry and Becker, George and Farizy, Anne and Denoyelle, Ludovic}
}
@inbook {894,
	title = {Discovering, Modeling, and Reenacting Open Source Software Development Processes},
	booktitle = {New Trends in Software Process Modeling},
	series = {Series in Software Engineering and Knowledge Engineering},
	volume = {18},
	year = {2006},
	pages = {1-20},
	author = {Chris Jensen and Walt Scacchi}
}
@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 {Canfora:2006:FGI:1137983.1138009,
	title = {Fine grained indexing of software repositories to support impact analysis},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {105{\textendash}111},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Versioned and bug-tracked software systems provide a huge amount of historical data regarding source code changes and issues management. In this paper we deal with impact analysis of a change request and show that data stored in software repositories are a good descriptor on how past change requests have been resolved. A fine grained analysis method of software repositories is used to index code at different levels of granularity, such as lines of code and source files, with free text contained in software repositories. The method exploits information retrieval algorithms to link the change request description and code entities impacted by similar past change requests. We evaluate such approach on a set of three open-source projects.},
	keywords = {argouml, change analysis, Firefox, gedit, impact analysis, mining software repositories, scm, source code, version control},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138009},
	url = {http://doi.acm.org/10.1145/1137983.1138009},
	attachments = {https://flosshub.org/sites/flosshub.org/files/105FineGrained.pdf},
	author = {Canfora, Gerardo and Cerulo, Luigi}
}
@article {109,
	title = {FLOSSmole: A Collaborative Repository for FLOSS Research Data and Analyses},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	pages = {17-26},
	author = {James Howison and Conklin, Megan and Kevin Crowston}
}
@conference {41,
	title = {The FLOSSWALD information system on free and open source software},
	booktitle = {9th International Workshop on Learning Software Organizations},
	year = {2006},
	note = {"Using these [FLOSSmole] data we intend to map the respective projects
to their developed software and thus extend the already
existing cases with new attributes or create new we cases
where necessary."

"Our first step
will be to evaluate the data provided by the Debian project
and the FLOSSmole project and design a knowledge base
and case structure to flexibly work with them."},
	month = {10/2006},
	abstract = {We propose the implementation of an intelligent information system on free and open source software. This system will consist of a case-based reasoning (CBR) system and several machine learning modules to maintain the knowledge base and train the CBR system thus enhancing its performance. Our knowledge base will include data on free and open source software provided by the Debian project, the FLOSSmole project, and other public free and open source software directories. We plan to enrich these data by learning additional information such as concepts and different similarities. With this knowledge base, we hope to be able to create an information system that will be capable of answering queries based on precise as well as vague criteria and give intelligent recommendations on software based on the preferences of the user.},
	keywords = {debian, flossmole},
	attachments = {https://flosshub.org/sites/flosshub.org/files/flosswald.pdf},
	author = {Reichle, M. and Hanft, A.}
}
@conference {674,
	title = {A Framework for Teaching Software Testing using F/OSS Methodology},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {261 - 266},
	publisher = {Springer},
	organization = {Springer},
	abstract = {In this paper we discuss a framework for teaching software testing to undergraduate students{\textquoteright} volunteers. The framework uses open source software development methodology and was implemented in the {\textquotedblleft}Introduction to Software Engineering{\textquotedblright} course at the department of Informatics, Aristotle University, Greece. The framework is in three phases, each describing a teaching and learning context in which students get involved in real software projects activities. We report on our teaching experiences, lessons learned and some practical problems we encountered. Results from preliminary evaluation shows that students did well as bug hunters in the bazaar and are willing to  participate in their projects long after graduation.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_26},
	attachments = {https://flosshub.org/sites/flosshub.org/files/A\%20Framework\%20for\%20Teaching\%20Software\%20Testing.pdf},
	author = {Sowe, Sulayman and Ioannis Stamelos and Deligiannis, Ignatios}
}
@unpublished {flosswp297,
	title = {Free and open source software hackers in Turkey},
	year = {2006},
	publisher = {n/a},
	type = {Working Paper},
	abstract = {In recent years, there has been growing interest of governments and firms for Free and Open Source Software (FOSS). However, FOSS is still a puzzlement for a wide spectrum of academic disciplines. Social scientists ask why FOSS hackers participate in FOSS if they do not get any monetary rewards. On the other hand firms ask, how a firm can earn money from FOSS. In this study, motivations of FOSS hackers and firms are taken as an interrelated phenomenon. This study discusses FOSS from the view of hackers in Turkey. In that respect, social conditions that make hackers voluntarily contribute to the FOSS projects and their relationship with the commercial world are explored. 1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/WP.pdf},
	author = {Ibrahim Izlem Gozukeles}
}
@unpublished {flosswp305,
	title = {Free Open Source as a Technology Transfer Tool in the Arab World},
	year = {2006},
	month = {November},
	abstract = {The Arab world has so far minimum contribution to the current global innovation system. Technology transfer is a major factor behind such weakness. Within the context of the Arab world, the Free Open Source (FOS)process could be adopted as a cheap and fast alternative tool for technology transfer. This study will focus on the effectiveness of FOS process on the Technology Transfer and how it will improve the cooperation between research and industrial institutes working in the ICT sector in the Arab world.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Khatib_FOS.pdf},
	author = {Jamil Alkhatib}
}
@unpublished {flosswp335,
	title = {Free/Open Source Software And Business: Forming A Migration Policy},
	year = {2006},
	month = {August},
	abstract = {This paper explores the non-technical issues that arise with migration to Free/Libre and Open Source Software (FLOSS) in Large Scaled Enterprises (LSEs), with special emphasis on human and social issues. The result of the study is a conceptual framework for effective addressing of non-technical issues in a migration policy. The study is of exploratory nature and uses secondary research findings from multiple disciplines: free and open source software, management of human resources, power and conflict, system migration, information systems development, motivation, change management, organizational psychology and social informatics; including anecdotal evidence from FLOSS migrations in practice. A holistic approach has been used during the analysis of the migration issues, based on the key principles of social informatics that IT technology and social contexts are interdependent. The relationship between FLOSS migrations and different organizational contexts is elaborated and it has been found out how lack of vendor support for FLOSS motivates LSEs to improve their self-support of own IT infrastructures. In-depth analysis is performed of the individual and social impact that FLOSS migrations have on enterprise IT personnel, as well as how different individual factors such as age, gender, personal motivations and beliefs may impact on individual migration efforts. The social differences between typical enterprise IT personnel and the FLOSS community are elaborated, as well as how to overcome the communication gap between them. The role of end users in FLOSS migration and relevant issues are discussed. It is proved why staged migration is the most viable option and it is shown how it is related to human and social factors. At the end, a conceptual framework for description of non-technical FLOSS migration issues is discussed, which can be used as a helpful tool in a migration policy.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dissertation_kspirov.pdf},
	author = {Kristijan Spirov}
}
@conference {691,
	title = {From Individual Contribution to Group Learning},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {77 - 90},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Open Source Software (OSS) groups experience many benefits and challenges with respect to the core group{\textquoteright}s effectiveness. In order to capitalize on the benefits and minimize the challenges, OSS groups must learn not only on the individual level, but also on the group level. OSS groups learn by integrating individual contributions into the group{\textquoteright}s product and processes.
This paper reports on the characteristics of the learning process in OSS groups. The study utilized an embedded single case study design that observed and analyzed group learning processes in the Apache Web server OSS project. The study used learning opportunity episodes (LOE) as the embedded unit of analysis and developed and utilized three content analytic schemes to describe the characteristics of the learning process and the factors affecting this process.
},
	keywords = {apache, case study},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_8},
	attachments = {https://flosshub.org/sites/flosshub.org/files/From\%20Individual\%20Contribution\%20to\%20Group\%20Learning.pdf},
	author = {Hala Annabi and Kevin Crowston and Robert Heckman}
}
@conference {Robles:2006:GLD:1137983.1138017,
	title = {Geographic location of developers at SourceForge},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {144{\textendash}150},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The development of libre (free/open source) software is usually performed by geographically distributed teams. Participation in most cases is voluntary, sometimes sporadic, and often not framed by a pre-defined management structure. This means that anybody can contribute, and in principle no national origin has advantages over others, except for the differences in availability and quality of Internet connections and language. However, differences in participation across regions do exist, although there are little studies about them. In this paper we present some data which can be the basis for some of those studies. We have taken the database of users registered at SourceForge, the largest libre software development web-based platform, and have inferred their geographical locations. For this, we have applied several techniques and heuristics on the available data (mainly e-mail addresses and time zones), which are presented and discussed in detail. The results show a snapshot of the regional distribution of SourceForge users, which may be a good proxy of the actual distribution of libre software developers. In addition, the methodology may be of interest for similar studies in other domains, when the available data is similar (as is the case of mailing lists related to software projects).},
	keywords = {distributed, email, email address, free software, geographical location, geography, libre software, mining software repositories, open source software, sourceforge, timezone},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138017},
	url = {http://doi.acm.org/10.1145/1137983.1138017},
	attachments = {https://flosshub.org/sites/flosshub.org/files/144GeographicLocation.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@conference {675,
	title = {A graphical installation system for the GNU/Linux Debian distribution},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {337 - 338},
	publisher = {Springer},
	organization = {Springer},
	abstract = {One of the main objectives of the Centro di Competenza sul Software Libero del Politecnico di Torino is to provide custom GNU/Linux distribution to the Public Administration, small and medium enterprise and schools. Debian GNU/Linux was choosen as the base for the custom distributions because of its strong support of free software and its long-standing technical merits: minimalist hardware requirement, the best available packaging system, support for 13 different architectures and a strict set of quality guidelines adopted by all the active Debian developers. The only foreseeable limitation, the Debian default text-based installer, was overriden by restarting the development of the then-abandoned Debian graphical installer. Now the new graphical installer is developed by tens of people and it will be included in the next official Debian release.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_35},
	attachments = {https://flosshub.org/sites/flosshub.org/files/A\%20graphical\%20installation\%20system.pdf},
	author = {Attilio, Fiandrotti and Di Nunzio, Pierluigi and Di Gregorio, Federico and Meo, Angelo}
}
@article {Crowston:2006a,
	title = {Hierarchy and centralization in Free and Open Source Software team communications},
	journal = {Knowledge, Technology \& Policy},
	volume = {18},
	number = {4},
	year = {2006},
	pages = {65{\textendash}85},
	abstract = {Free/Libre Open Source Software (FLOSS) development teams provide an interesting and convenient setting for studying distributed work. We begin by answering perhaps the most basic question: what is the social structure of these teams? Based on a social network analysis of interactions represented in 62,110 bug reports from 122 large and active projects, we find that some OSS teams are highly centralized, but contrary to expectation, others are not. Projects are mostly quite hierarchical on four measures of hierarchy, consistent with past research but contrary to the popular image of these projects. Furthermore, we find that the level of centralization is negatively correlated with project size, suggesting that larger projects become more modular. The paper makes a further methodological contribution by identifying appropriate analysis approaches for interaction data. We conclude by sketching directions for future research.},
	keywords = {apache, bug fixing, bug tracking, FLOSS, project success, savannah, social network analysis, sourceforge, team size, teams},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHierarchyAndCentralization.pdf},
	author = {Kevin Crowston and Howison, James}
}
@article {flosswp302,
	title = {How free software developers work. The mobilization of "distant communities"},
	year = {2006},
	month = {January},
	abstract = {The work of free software developers is an individual activity carried out in extremely heterogeneous conditions and a collective action with original production methods. We propose to analyze this work starting with the paradoxical notion of a "distant community", that aims to illustrate the tension between, on the one hand, the strength of the sense of belonging to a specific world identifiable in the discourse of the participants and, on the other hand, the distances that separate the contributors in terms of relationships, status, and background. In doing this the aim is to produce a description, necessarily plural, of the different forms of "distant communities" that enables the production of goods in unique social and organizational conditions. More generally speaking, this notion points to methods of coordination that combine two forms of collective action that are usually contrary and antagonistic: a communitarian form based on the subjective feeling of belonging to the same community and a form of partnership based on the coordination of common interests and sharing of objectives (T??nnies, 1887, Weber, 1921). At first, we examine the ways the individual participants organize themselves in order to contribute to a project and we focus on the forms of cooperation and coordination used to deal with the constraints of efficiency and quality associated with the distribution of a product. Secondly, we look at the other side of the coin and examine the ways individual participants take action and we underline the mechanisms of commitment and participation that account for their contribution to the production of free software. These two dimensions, that in our opinion are inseparable, are explored through a survey carried out with free software developers.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CLES_DDFHNJ_juin_2006__vm_Anglais.pdf},
	author = {Didier Demazi{\`e}re and Francois Horn and Nicolas Jullien}
}
@conference {692,
	title = {How is it possible to profit from innovation in the absence of any appropriability?},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {333 - 334},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Open Source Software (OSS) represents an {\textquotedblleft}open innovation{\textquotedblright} paradigm based on knowledge produced and shared by developers and users. New findings from a large survey of European software companies show that: (i) the OSS business model is currently involving almost one third of the industry, although with different intensity; (ii) compared with pure proprietary software producers, OSS firms have a broader product portfolio and are more diversified; moreover, (iii) OSS firms provide more complementary services to their customers; (iv) over time OSS firms increase the share of OS turnover out of the total turnover, becoming more and more OSS oriented; (v) both NOSS and OSS firms do not consider appropriability as a crucial requirement for innovation and do not consider the lack of appropriability as an obstacle to profitability.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/How\%20is\%20it\%20possible\%20to\%20profit.pdf},
	author = {Andrea Bonaccorsi and Lucia Piscitello and Monica Merito and Cristina Rossi}
}
@conference {Kim:2006:LDT:1137983.1138027,
	title = {How long did it take to fix bugs?},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {173{\textendash}174},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The number of bugs (or fixes) is a common factor used to measure the quality of software and assist bug related analysis. For example, if software files have many bugs, they may be unstable. In comparison, the bug-fix time--the time to fix a bug after the bug was introduced--is neglected. We believe that the bug-fix time is an important factor for bug related analysis, such as measuring software quality. For example, if bugs in a file take a relatively long time to be fixed, the file may have some structural problems that make it difficult to make changes. In this report, we compute the bug-fix time of files in ArgoUML and PostgreSQL by identifying when bugs are introduced and when the bugs are fixed. This report includes bug-fix time statistics such as average bug-fix time, and distributions of bug-fix time. We also list the top 20 bug-fix time files of two projects.},
	keywords = {argouml, bug fixing, bugs, mining challenge, msr challenge, postgresql, quality, time},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138027},
	url = {http://doi.acm.org/10.1145/1137983.1138027},
	attachments = {https://flosshub.org/sites/flosshub.org/files/173HowLong.pdf},
	author = {Kim, Sunghun and Whitehead,Jr., E. James}
}
@proceedings {71,
	title = {Identification of coordination requirements: Implications for the design of collaboration and awareness tools},
	year = {2006},
	month = {November},
	address = {Banff, Alberta, Canada},
	keywords = {modularity},
	author = {Cataldo, Marcelo and Wagstrom, Patrick A. and Herbsleb, J. D. and Carley, Kathleen M.}
}
@article {flosswp325,
	title = {Identifying Knowledge Brokers that Yield Software Engineering Knowledge in OSS Projects},
	journal = {Information and Software Technology},
	volume = {46},
	year = {2006},
	note = {Uses the Debian mailing lists "kde", "mentor", and "user". 
the collection period was from January 2001 to September 2004},
	month = {11/2006},
	pages = {1025-1033},
	abstract = {Much research on open source software development concentrates on developer lists and other software repositories to investigate what motivates professional software developers to participate in open source software projects. Little attention has been paid to individuals who spend valuable time in lists helping participants on some mundane yet vital project activities. Using three Debian lists as a case study we investigate the impact of knowledge brokers and their associated activities in open source projects. Social network analysis was used to visualize how participants are affiliated with the lists. The network topology reveals substantial community participation. The consequence of collaborating in mundane activities for the success of open source software projects is discussed. The direct beneficiaries of this research are in the identification of knowledge experts in open source software projects.},
	keywords = {debian, email, email archives, expertise, knowledge sharing, mailing list, project success, social network analysis},
	doi = {10.1016/j.infsof.2005.12.019},
	attachments = {https://flosshub.org/sites/flosshub.org/files/IST-Vol-48-11-2006.pdf},
	author = {Sowe, Sulayman K. and Ioannis Stamelos and Lefteris Angelis}
}
@article {flosswp113,
	title = {The Impact of Ideology on Effectiveness in Open Source Software Development Teams},
	journal = {MIS Quarterly},
	volume = {30},
	number = {2},
	year = {2006},
	note = {"...we collected data related to OSS projects hosted on Sourceforge (www.sourceforge.net)."
"Data was collected using two surveys and from the Sourceforge website."
},
	month = {2006},
	pages = {291-314},
	abstract = {The emerging work on understanding open source software has argued for the importance of understanding what leads to effectiveness in OSS development teams and has pointed to the importance of ideology. This paper develops a framework of the OSS ideology (including specific norms, beliefs, and values) and a theoretical model to show how adherence to components of the ideology impact effectiveness in OSS teams. The model is based on the idea that ideology provides clan control, which is important in OSS development settings because OSS teams generally lack formal behavioral and outcome controls. The paper hypothesizes both direct effects of ideology on OSS team effectiveness and indirect effects via influences on affective trust, cognitive trust, and communication quality. Hypotheses are tested using survey and objective data on OSS projects. Four effectiveness measures are used to capture unique aspects of effectiveness in OSS including both the extent to which a team attracts input from the community and the team{\textquoteright}s success in accomplishing project outcomes. Results support the main thesis that OSS team members{\textquoteright} adherence to the tenets of the OSS community ideology enhances OSS team effectiveness. The study uncovers several differences in the importance of OSS norms, beliefs, and values to different kinds of OSS team effectiveness and discusses implications for theory and practice.},
	keywords = {bug fixing, bug reports, bug tracking, communication, COMMUNITY, effectiveness, feature requests, ideology, metadata, sourceforge, Survey, team effort, team size, trust},
	attachments = {https://flosshub.org/sites/flosshub.org/files/stewartgosain2.pdf},
	author = {Stewart, K. and Gosain, S.}
}
@conference {693,
	title = {Impact of Social Ties on Open Source Project Team Formation},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	note = {"we randomly selected 1030 new projects that were registered between X and X in 2005. A web crawler downloaded the HTML files containing project summary data and developer information on the date of registration."},
	month = {2006///},
	pages = {307 - 317},
	publisher = {Springer},
	organization = {Springer},
	abstract = {In this paper, we empirically examined the role of social ties in OSSD team formation and developer joining behavior. We find that the existence and the amount of prior social relations in the network do increase the probability of an OSS project to attract more developers. Interestingly, for projects without preexisting social ties, developers tend to join the project initiated by people with less OSSD experience. This research fills a gap in the open source literature by conducting an empirical investigation of the role of social relations on project team formation behavior. Furthermore, the adoption of social network analysis, which has received little attention in the OSS literature, can yield some interesting results on the interactions among OSS developers.
},
	keywords = {developers, metadata, social network analysis, sourceforge},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Impact\%20of\%20Social\%20Ties\%20on\%20Open\%20Source\%20Project.pdf},
	author = {Hahn, Jungpil and Moon, Jae and Zhang, Chen}
}
@article {141,
	title = {Impacts of license choice and organizational sponsorship on user interest and development activity in open source software projects},
	journal = {Information Systems Research},
	volume = {17},
	number = {2},
	year = {2006},
	note = {Times Cited: 1},
	pages = {126-144},
	abstract = {What differentiates successful from unsuccessful open source software projects? This paper develops and tests a model of the impacts of license restrictiveness and organizational sponsorship on two indicators of success: user interest in, and development activity on, open source software development projects. Using data gathered from Freshmeat.net and project home pages, the main conclusions derived from the analysis are that (1) license restrictiveness and organizational sponsorship interact to influence user perceptions of the likely utility of open source software in such a way that users are most attracted to projects that are sponsored by nonmarket organizations and that employ nonrestrictive licenses, and (2) licensing and sponsorship address complementary developer motivations such that the influence of licensing on development activity depends on what kind of organizational sponsor a project has. Theoretical and practical implications are discussed, and the paper outlines several avenues for future research.},
	author = {Katherine Stewart and Ammeter, A. P. and Maruping, L. M.}
}
@article {Crowston:2006,
	title = {Information systems success in Free and Open Source Software development: Theory and measures},
	journal = {Software Process{\textendash}Improvement and Practice},
	volume = {11},
	number = {2},
	year = {2006},
	note = {"we continue our examination of success measures using data from Sourceforge..."
"e chose the number of developers (assessed from the records of the project and from bug fixing logs), bug-fixing time, and popularity (assessed from the number of downloads and viewings of project Web pages, and inclusion in distributions). These measures were chosen because they span the reconsidered FLOSS development process discussed above, including inputs (number of developers), process (speed of bug fixing) and output (popularity)."},
	pages = {123{\textendash}148},
	abstract = {Information systems success is one of the most widely used dependent variables in information systems (IS) research, but research on Free/Libre and Open Source software (FLOSS) often fails to appropriately conceptualize this important concept. In this paper, we reconsider what success means within a FLOSS context. We first review existing models of IS success and success variables used in FLOSS research and assess them for their usefulness, practicality and fit to the FLOSS context. Then, drawing on a theoretical model of group effectiveness in the FLOSS development process, as well as an online discussion group with developers, we present additional concepts that are central to an appropriate understanding of success for FLOSS. In order to examine the practicality and validity of this conceptual scheme, the second half of our paper presents an empirical study that demonstrates its operationalization of the chosen measures and assesses their internal validity. We use data from SourceForge to measure the project{\textquoteright}s effectiveness in team building, the speed of the project at responding to bug reports and the project{\textquoteright}s popularity. We conclude by discussing the implications of this study for our proposed extension of IS success in the context of FLOSS development and highlight future directions for research.},
	keywords = {bug fixing, developers, downloads, FLOSS, flossmole, page views, popularity, project success, size, sourceforge, success, team size},
	doi = {10.1002/spip.259},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHowisonAnnabi2006.pdf},
	author = {Kevin Crowston and Howison, James and Hala Annabi}
}
@conference {Askari:2006:ITE:1137983.1138013,
	title = {Information theoretic evaluation of change prediction models for large-scale software},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {126{\textendash}132},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper, we analyze the data extracted from several open source software repositories. We observe that the change data follows a Zipf distribution. Based on the extracted data, we then develop three probabilistic models to predict which files will have changes or bugs. The first model is Maximum Likelihood Estimation (MLE), which simply counts the number of events, i.e., changes or bugs, that happen to each file and normalizes the counts to compute a probability distribution. The second model is Reflexive Exponential Decay (RED) in which we postulate that the predictive rate of modification in a file is incremented by any modification to that file and decays exponentially. The third model is called RED-Co-Change. With each modification to a given file, the RED-Co-Change model not only increments its predictive rate, but also increments the rate for other files that are related to the given file through previous co-changes. We then present an information-theoretic approach to evaluate the performance of different prediction models. In this approach, the closeness of model distribution to the actual unknown probability distribution of the system is measured using cross entropy. We evaluate our prediction models empirically using the proposed information-theoretic approach for six large open source systems. Based on this evaluation, we observe that of our three prediction models, the RED-Co-Change model predicts the distribution that is closest to the actual distribution for all the studied systems.},
	keywords = {bugs, change analysis, cvs, evaluation approach, file, freebsd, information theory, kde, koffice, log files, netbsd, openbsd, postgresql, prediction, prediction models, scm, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138013},
	url = {http://doi.acm.org/10.1145/1137983.1138013},
	attachments = {https://flosshub.org/sites/flosshub.org/files/126InformationTheoretic.pdf},
	author = {Askari, Mina and Holt, Ric}
}
@conference {888,
	title = {Insert Movie Reference Here: A System to Bridge Conversation and Item-Oriented Web Sites},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2006},
	month = {22/04/2006},
	pages = {951-954},
	publisher = {ACM},
	organization = {ACM},
	isbn = {1-59593-372-7},
	author = {Sara Drenner and Max Harper and Dan Frankowski and John Riedl and Loren Terveen}
}
@conference {694,
	title = {Insiders and outsiders: paid contributors and the dynamics of cooperation in community led F/OS projects},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {201 - 208},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper examines the role of paid developers in mature free/open source (F/OS) communities. In particular it provides a typology for their involvement based on their employment and sponsorship arrangements and elaborates a framework for understanding the dynamics of cooperation developing between them and the volunteers based on their community ties. The evidence presented is drawn from individual interviews conducted with volunteer and paid contributors from the GNOME and KDE projects within the context of a PhD research focusing on commercialization and peripheral participation in F/OS communities. The paper highlights the various interdependencies that form between communities and companies and adds to our understanding of the dynamics of commercialization in F/OS projects.
},
	keywords = {gnome, interviews, kde},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Insiders\%20and\%20outsiders.pdf},
	author = {Evangelia Berdou}
}
@conference {695,
	title = {Institutional Entrepreneurs and the Bricolage of Intellectual Property Discourses},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {183 - 193},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Commercial software firms are increasingly becoming involved with open source communities. In this research-in-progress paper I briefly analysed a single firm case that demonstrates how an institutional entrepreneur mixes in an innovative way different discourses in an attempt to legitimise a new mode for developing software applying both open and closed source codes. The institutional entrepreneur does this by creating new distinctions in his daily software developing work. I am not arguing that the institutional entrepreneur is creating these new distinctions in an instrumental rational process, but that the distinctions emerge in sensemaking processes along his {\textquoteleft}doing{\textquoteright} something in the firm.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Institutional\%20Entrepreneurs\%20and\%20the\%20Bricolage.pdf},
	author = {Westenholz, Ann}
}
@article {1232,
	title = {Integration of libre software applications to create a collaborative work platform for researchers at GET},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	month = {07/2006},
	pages = {1-16},
	publisher = {IGI Global},
	abstract = {Libre software provides powerful applications ready to be integrated for the build-up of platforms for internal use in organizations. We describe the architecture of the collaborative work platform which we have integrated, designed for researchers at GET. We present the elements we have learned during this project in particular with respect to contribution to external libre projects, in order to better ensure the maintainability of the internal applications, and to phpGroupware as a framework for specific applications development.},
	keywords = {collaborative work environment, contribution, free software, groupware, in-house applications, libre software, open source software, OpenLDAP, phpGroupware, PicoLibre, ProGET, Sympa, TWiki, WebDAV, wiki},
	author = {Olivier Berger and Christian Bac and Benoit Hamet}
}
@article {flosswp323,
	title = {{\textquoteright}Intellectual Property{\textquoteright} and Knowledge Creation in Disorganisations},
	year = {2006},
	month = {December},
	abstract = {Given the current forms of economic production and corporate markets, the liberating and democratic potential of digital information is counteracted by the concentration of media ownership, as well as by policy, legislation, and the development of proprietary forms of technology. The notion of {\textquoteright}intellectual property{\textquoteright} produces artificial scarcity where digital technology could remove it. This tension between the proprietary and non-proprietary aspects of the information society can be analysed by looking at two types of knowledge creation: organisational and disorganisational. While organisational knowledge work can benefit from a notion of {\textquoteright}intellectual property{\textquoteright}, disorganisational knowledge work is disrupted, if not destroyed, by proprietary barriers on information. This is unfortunate if and when the crucial innovations and ethical potential of the information society are connected to disorganisational communities, even though the organisational type is more visible and better represented in the traditional structures of society.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/14_Vaden_ELEA_3_3_web.pdf},
	author = {Tere Vad{\'e}n}
}
@conference {710,
	title = {The Introduction of OpenOffice.org in the Brussels Public Administration},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {123 - 134},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Open source software is increasingly used by public administrations as an alternative to commercial software. In this paper we present a case study of the transition of the ministerial cabinets of the Brussels-Capital Region towards OpenOffice.org. 
In this case, the decision to use open source software was taken by the Government of the Brussels-Capital Region. The goal of the paper is to outline the implementation trajectory followed and to compare our findings to previous studies in this field as well as other Information Systems literature. Additionally, we discuss how OpenOffice.org was received by end users as well as the IT department that was responsible for the migration. Our findings indicate that although a migration towards OpenOffice.org is feasible, a number of difficulties still remain. For example, end user perceptions of OpenOffice.org are not always favorable and migration costs (document conversion and training) can be significant.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_12},
	attachments = {https://flosshub.org/sites/flosshub.org/files/The\%20Introduction\%20of\%20OpenOffice.org.pdf},
	author = {Ven, Kris and Van Nuffel, Dieter and Verelst, Jan}
}
@conference {1094,
	title = {Knowledge Reuse in Open Source Software: An Exploratory Study of 15 Open Source Projects},
	booktitle = {Proceedings of the 38th Annual Hawaii International Conference on System Sciences},
	year = {2006},
	note = {"In a first step, we asked developers of different open source projects to respond to a very short web-based survey."...
"In a second step, we started with gathering data from 15 projects, including interviews. In parallel, the source code, CVS comments and to a certain extent email communication was analyzed to receive a dynamic, and within the limits of the method, complete picture of knowledge reuse practices."
"Projects included games (Adonthell, FlightGear, Xboard), text processing (Abiword), a GNU/Linux desktop (Xfce4), an instant messenger client (Miranda), fax software (HylaFAX), a content management system (Tiki/CMS Groupware), encryption software (OpenSSL), a collaborative music system (iRATE Radio), file sharing networks (GNUnet, Mnet, Freenet), a mailing list manager (Mailman), and an mp3 encoder (Lame)."
"Our data sources included interviews with key developers, source code, CVS comments, mailing lists and various Internet resources"},
	month = {2006},
	pages = {1-10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Big Island, HI, USA},
	abstract = {To date, there is no investigation of knowledge reuse in open source software projects. This paper focuses on the forms of knowledge reuse and the factors impacting on them. It develops a theory drawn from data of 15 open source software projects and finds that the effort to search, integrate and maintain external knowledge influences the form of knowledge to be reused. Implications for firms and innovation research are discussed.},
	keywords = {cvs, email, knowledge reuse, lines of code, loc, source code, Survey},
	doi = {10.1109/HICSS.2005.378},
	url = {http://www.computer.org/csdl/proceedings/hicss/2005/2268/07/22680198b-abs.html},
	author = {von Krogh, G. and Spaeth, S. and Haefliger, S.}
}
@unpublished {flosswp337,
	title = {Learning and knowledge in FLOSS - Situated learning and organizational knowledge-conversion in community-based free/libre open source software development},
	year = {2006},
	month = {November},
	abstract = {In free/libre open source software development (FLOSS), groups of developers and users working in geographically dispersed settings are supported by a dense network of interactions. The participants are highly skilled in the use of information- and communication technologies, and build the software by relying on extensive peer production and through skillful use of communication tools available on the Internet. In building the software, explicit, formal and structured knowledge in the form of documents, objects, machines and external sources are communicated and stored in ways that make it available for others in the present and future. This knowledge make up an important resource for the members and developers of the community. Another kind, or aspect, of knowledge, often called tacit or soft knowledge, is informal, unstructured, resides in people, and are difficult, or maybe impossible, to articulate. The questions guiding this research is how knowledge, both explicit and tacit, is shared, and how a new member is able take part in the practice and knowledge of the community. The theory of legitimate peripheral participation in communities of practice describes an environment for people to develop knowledge through interaction with others in an environment where knowledge is created, nurtured and sustained. By taking part in the practice as a participant observer, through virtual ethnography, the author describes the practice and communication in this decentralized and knowledge-intensive process. Taking it a step further, the knowledge of the community, and how it is shared within the ???organization???, is explored with a model for managing dynamic aspects of organizational knowledge-creation. The central theme here is that knowledge is created through a continuous dialogue between tacit and explicit knowledge. Logs from Internet Relay Chat (IRC) and interviews with core developers are analyzed, and the author argues that the Plone community is able to share both kinds of knowledge in a complex web of resources and interaction. The analysis further suggest that the FLOSS development-model facilitates access, transparency and participation on premisses that are important for learning.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Learning-and-knowledge-in-FLOSS.pdf},
	author = {Sverre Helge Bolstad}
}
@conference {696,
	title = {Licensing Services: An {\textquotedblleft}Open{\textquotedblright} Perspective},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {143 - 154},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Though service orientation is an incipient technology, the inherently infinite potentiality of services makes them to proliferate seamlessly, serving in myriad domains. Licensing of services enables to regulate the commercial use and modifications of service, retaining the copyright with owner of the service. With the growing influence of open source initiatives today, it becomes a significant topic to analyze {\textquoteleft}open{\textquoteright}ing services. In this paper, we present a concept of {\textquoteleft}open service{\textquoteright} and analyze the implications of open source approach on service licenses.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_14},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Licensing\%20Services\%20\%20An\%20Open\%20Perspective.pdf},
	author = {D{\textquoteright}Andrea, Vincenzo and Gangadharan, G.}
}
@conference {697,
	title = {Life cycle of Defects in Open Source Software Projects},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	note = {"we collected and analyzed defects of the apache http server and mozilla firefox" 
"all the defects reported between X and X were analyzed"},
	pages = {195 - 200},
	publisher = {Springer},
	organization = {Springer},
	abstract = {We studied the maintenance process from the viewpoint of defect management and the defect life cycle. First, we outline a model for the defect life cycle based on ISO/IEC standards, the Framework for Open Source maintenance process, and the Bugzilla defect management system. Thereafter, we analyze defects from two Open Source software projects. The aim of the study was support the maintenance reliability. However, we found that most of the defects did not follow the life-cycle model. Defects were usually directly resolved from initial state without being assigned.
},
	keywords = {apache, defects, Firefox, mozilla},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_19},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Life\%20cycle\%20of\%20Defects\%20in\%20OSS\%20Projects.pdf},
	author = {Koponen, Timo}
}
@article {Grewal:2006:LLL:1246148.1246155,
	title = {Location, Location, Location: How Network Embeddedness Affects Project Success in Open Source Systems},
	journal = {Management Science},
	volume = {52},
	number = {7},
	year = {2006},
	month = {July},
	pages = {1043{\textendash}1056},
	publisher = {INFORMS},
	address = {Institute for Operations Research and the Management Sciences (INFORMS), Linthicum, Maryland, USA},
	abstract = {The community-based model for software development in open source environments is becoming a viable alternative to traditional firm-based models. To better understand the workings of open source environments, we examine the effects of network embeddedness---or the nature of the relationship among projects and developers---on the success of open source projects. We find that considerable heterogeneity exists in the network embeddedness of open source projects and project managers. We use a visual representation of the affiliation network of projects and developers as well as a formal statistical analysis to demonstrate this heterogeneity and to investigate how these structures differ across projects and project managers. Our main results surround the effect of this differential network embeddedness on project success. We find that network embeddedness has strong and significant effects on both technical and commercial success, but that those effects are quite complex. We use latent class regression analysis to show that multiple regimes exist and that some of the effects of network embeddedness are positive under some regimes and negative under others. We use project age and number of page views to provide insights into the direction of the effect of network embeddedness on project success. Our findings show that different aspects of network embeddedness have powerful but subtle effects on project success and suggest that this is a rich environment for further study.},
	keywords = {affiliation network, age, developers, latent class analysis, network embeddedness, open source software, page views, perl, project success, registration, sourceforge},
	issn = {0025-1909},
	doi = {10.1287/mnsc.1060.0550},
	url = {http://portal.acm.org/citation.cfm?id=1246148.1246155},
	author = {Grewal, Rajdeep and Lilien, Gary L. and Mallapragada, Girish}
}
@article {Yu:2006:MKO:1150566.1150571,
	title = {Maintainability of the kernels of open-source operating systems: A comparison of Linux with FreeBSD, NetBSD, and OpenBSD},
	journal = {J. Syst. Softw.},
	volume = {79},
	year = {2006},
	note = {"Data regarding the number and total number of lines of code of kernel and nonkernel modules in the four operating systems are provided in Table 1"
loc, kloc, number of kernel modules, number of nonkernel modules
size 
c files
.h files},
	month = {June},
	pages = {807{\textendash}815},
	publisher = {Elsevier Science Inc.},
	address = {New York, NY, USA},
	abstract = {We compared and contrasted the maintainability of four open-source operating systems: Linux, FreeBSD, NetBSD, and OpenBSD. We used our categorization of common coupling in kernel-based software to highlight future maintenance problems. An unsafe definition is a definition of a global variable that can affect a kernel module if that definition is changed. For each operating system we determined a number of measures, including the number of global variables, the number of instances of global variables in the kernel and overall, as well as the number of unsafe definitions in the kernel and overall. We also computed the value of each our measures per kernel KLOC and per KLOC overall. For every measure and every ratio, Linux compared unfavorably with FreeBSD, NetBSD, and OpenBSD. Accordingly, we are concerned about the future maintainability of Linux. },
	keywords = {abiword, Common coupling, coupling, Definition-use analysis, freebsd, kernel, lines of code, linux, linux kernel, loc, Maintainability, modules, netbsd, Open-source software, openbsd, source code},
	issn = {0164-1212},
	doi = {http://dx.doi.org/10.1016/j.jss.2005.08.014},
	url = {http://dx.doi.org/10.1016/j.jss.2005.08.014},
	attachments = {https://flosshub.org/sites/flosshub.org/files/YuSchachChen.pdf},
	author = {Yu, Liguo and Schach, Stephen R. and Chen, Kai and Heller, Gillian Z. and Offutt, Jeff}
}
@article {flosswp374,
	title = {A man on the inside: Unlocking communities as complementary assets},
	year = {2006},
	month = {October},
	abstract = {Since Teece{\textquoteright}s seminal paper explaining who were the gainers from technological innovation, increased globalization and the information and communication technology revolution have brought newways for firms to organize and appropriate from innovation. A new more open model of innovation suggests that firms can benefit from sources of innovation that stem from outside the firm. The central theme of this paper is how firms try to unlock communities as complementary assets. These communities exist outside firm boundaries beyond ownership or hierarchical control. Because of practices developed by communities to protect their work, firms need to assign individuals to work in these communities in order to gain access to developments and, to an extent, influence the direction of the community. Using network analysis we show that some software firms sponsor individuals to act strategically within a free and open source software (FOSS) community. Firm sponsored individuals interact with more individuals than interact with them, and also they seek to interact with central individuals in the community. However, we can see differences in how individuals interact, depending on whether their affiliation is with a dedicated FOSS firm or an incumbent in the software industry. Apparently, some firm managers believe they need ???a man on the inside??? to be able to gain access to communities. PLEASE EMAIL IF YOU LIKE A COPY OF THE PAPER!},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dahlanderwallin.pdf},
	author = {Linus Dahlander and Martin W. Wallin}
}
@conference {Xie:2006:MMA:1137983.1137997,
	title = {MAPO: mining API usages from open source repositories},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {54{\textendash}57},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {To improve software productivity, when constructing new software systems, developers often reuse existing class libraries or frameworks by invoking their APIs. Those APIs, however, are often complex and not well documented, posing barriers for developers to use them in new client code. To get familiar with how those APIs are used, developers may search the Web using a general search engine to find relevant documents or code examples. Developers can also use a source code search engine to search open source repositories for source files that use the same APIs. Nevertheless, the number of returned source files is often large. It is difficult for developers to learn API usages from a large number of returned results. In order to help developers understand API usages and write API client code more effectively, we have developed an API usage mining framework and its supporting tool called MAPO (for Mining API usages from Open source repositories). Given a query that describes a method, class, or package for an API, MAPO leverages the existing source code search engines to gather relevant source files and conducts data mining. The mining leads to a short list of frequent API usages for developers to inspect. MAPO currently consists of five components: a code search engine, a source code analyzer, a sequence preprocessor, a frequent sequence miner, and a frequent sequence post processor. We have examined the effectiveness of MAPO using a set of various queries. The preliminary results show that the framework is practical for providing informative and succinct API usage patterns.},
	keywords = {api, application programming interfaces, documentation, mining software repositories, pmd, program comprehension, search engine, sequences, source code, source code search engine},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137997},
	url = {http://doi.acm.org/10.1145/1137983.1137997},
	attachments = {https://flosshub.org/sites/flosshub.org/files/54MAPO.pdf},
	author = {Xie, Tao and Pei, Jian}
}
@book {52,
	title = {Math You Can{\textquoteright}t Use: Patents, Copyright, and Software},
	year = {2006},
	publisher = {Brookings Institution Press},
	organization = {Brookings Institution Press},
	author = {Klemens, B.}
}
@conference {Kim:2006:MPE:1137983.1137995,
	title = {Micro pattern evolution},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {40{\textendash}46},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {When analyzing the evolution history of a software project, we wish to develop results that generalize across projects. One approach is to analyze design patterns, permitting characteristics of the evolution to be associated with patterns, instead of source code. Traditional design patterns are generally not amenable to reliable automatic extraction from source code, yet automation is crucial for scalable evolution analysis. Instead, we analyze {\textquotedblleft}micro pattern{\textquotedblright} evolution; patterns whose abstraction level is closer to source code, and designed to be automatically extractable from Java source code or bytecode. We perform micro-pattern evolution analysis on three open source projects, ArgoUML, Columba, and jEdit to identify micro pattern frequencies, common kinds of pattern evolution, and bug-prone patterns. In all analyzed projects, we found that the micro patterns of Java classes do not change often. Common bug- prone pattern evolution kinds are {\textquoteleft}Pool {\textrightarrow} Pool{\textquoteright}, {\textquoteleft}Implementor {\textrightarrow} NONE{\textquoteright}, and {\textquoteleft}Sampler {\textrightarrow} Sampler{\textquoteright}. Among all pattern evolution	kinds,{\textquoteleft}Box{\textquoteright},{\textquoteleft}CompoundBox{\textquoteright},	{\textquoteleft}Pool{\textquoteright}, {\textquoteleft}CommonState{\textquoteright}, and {\textquoteleft}Outline{\textquoteright} micro patterns have high bug rates, but they have low frequencies and a small number of changes. The pattern evolution kinds that are bug-prone are somewhat similar across projects. The bug-prone pattern evolution kinds of two different periods of the same project are almost identical.},
	keywords = {argouml, bugs, columba, design patterns, evolution, extraction, java, jedit, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137995},
	url = {http://doi.acm.org/10.1145/1137983.1137995},
	attachments = {https://flosshub.org/sites/flosshub.org/files/40MicroPattern.pdf},
	author = {Kim, Sunghun and Pan, Kai and Whitehead,Jr., E. James}
}
@conference {711,
	title = {The micro-dynamics of open source software development activity},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {339 - 340},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This study aims to isolate and identify the properties of FLOSS development insofar as these can be revealed by examining the ecology of SF.net. It characterizes the contrast between the many {\textquotedblleft}lurkers{\textquotedblright} and a much smaller core of {\textquotedblleft}entrepreneurial{\textquotedblright} developers who are responsible for launching new projects, and gives an interpretation of the function of platforms such as SF.net as sites that people with a propensity to start open source projects can use to recruit {\textquotedblleft}laborers{\textquotedblright}. It describes the process underpinning the mobility of those who are recruited among the projects that are launched and provides insights on the evolution of developers{\textquoteright} level and mode of involvement in FLOSS production.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_36},
	attachments = {https://flosshub.org/sites/flosshub.org/files/The\%20micro-dynamics\%20of\%20open\%20source.pdf},
	author = {David, Paul and Francesco Rullani}
}
@conference {Zimmermann:2006:MAM:1137983.1138025,
	title = {Mining additions of method calls in ArgoUML},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {169{\textendash}170},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper we refine the classical co-change to the addition of method calls. We use this concept to find usage patterns and to identify cross-cutting concerns for ArgoUML.},
	keywords = {argouml, change analysis, eclipse, function calls, mining challenge, msr challenge, pattern, source code, xelopes},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138025},
	url = {http://doi.acm.org/10.1145/1137983.1138025},
	attachments = {https://flosshub.org/sites/flosshub.org/files/169MiningAdditions.pdf},
	author = {Zimmermann, Thomas and Breu, Silvia and Lindig, Christian and Livshits, Benjamin}
}
@conference {1228,
	title = {Mining CVS Signals},
	booktitle = {1st Workshop on Public Data about Software Development (WoPDaSD 2006)},
	year = {2006},
	pages = {10-19},
	author = {Jean-Michel Dalle and L. Daudet and den Besten, Matthijs}
}
@conference {Breu:2006:MEC:1137983.1138006,
	title = {Mining eclipse for cross-cutting concerns},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {94{\textendash}97},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software may contain functionality that does not align with its architecture. Such cross-cutting concerns do not exist from the beginning but emerge over time. By analysing where developers add code to a program, our history-based mining identifies cross-cutting concerns in a two-step process. First, we mine CVS archives for sets of methods where a call to a specific single method was added. In a second step, such simple cross-cutting concerns are combined to complex cross-cutting concerns. To compute these efficiently, we apply formal concept analysis{\textemdash}an algebraic theory. History-based mining scales well: we are the first to report aspects mined from an industrial-sized project like Eclipse. For example, we identified a locking concern that crosscuts 1284 methods.},
	keywords = {aspects, concept analysis, cvs, eclipse, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138006},
	url = {http://doi.acm.org/10.1145/1137983.1138006},
	attachments = {https://flosshub.org/sites/flosshub.org/files/94MiningEclipse.pdf},
	author = {Breu, Silvia and Zimmermann, Thomas and Lindig, Christian}
}
@conference {Bird:2006:MES:1137983.1138016,
	title = {Mining email social networks},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {137{\textendash}143},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Communication \& Co-ordination activities are central to large software projects, but are difficult to observe and study in traditional (closed-source, commercial) settings because of the prevalence of informal, direct communication modes. OSS projects, on the other hand, use the internet as the communication medium,and typically conduct discussions in an open, public manner. As a result, the email archives of OSS projects provide a useful trace of the communication and co-ordination activities of the participants. However, there are various challenges that must be addressed before this data can be effectively mined. Once this is done, we can construct social networks of email correspondents, and begin to address some interesting questions. These include questions relating to participation in the email; the social status of different types of OSS participants; the relationship of email activity and commit activity (in the CVS repositories) and the relationship of social status with commit activity. In this paper, we begin with a discussion of our infrastructure (including a novel use of Scientific Workflow software) and then discuss our approach to mining the email archives; and finally we present some preliminary results from our data analysis.},
	keywords = {communication, contributions, developers, email, email archives, mailing lists, open source, social networks},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138016},
	url = {http://doi.acm.org/10.1145/1137983.1138016},
	attachments = {https://flosshub.org/sites/flosshub.org/files/137MiningEmail.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem and Gertz, Michael and Swaminathan, Anand}
}
@conference {Bird:2006:MES:1137983.1138033,
	title = {Mining email social networks in Postgres},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {185{\textendash}186},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open Source Software (OSS) projects provide a unique opportunity to gather and analyze publicly available historical data. The Postgres SQL server, for example, has over seven years of recorded development and communication activity. We mined data from both the source code repository and the mailing list archives to examine the relationship between communication and development in Postgres. Along the way, we had to deal with the difficult challenge of resolving email aliases. We used a number of social network analysis measures and statistical techniques to analyze this data. We present our findings in this paper.},
	keywords = {developers, email, email archives, open source, postgresql, scm, social network analysis, social networks, source code, status},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138033},
	url = {http://doi.acm.org/10.1145/1137983.1138033},
	attachments = {https://flosshub.org/sites/flosshub.org/files/185MiningEmail.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem and Gertz, Michael and Swaminathan, Anand}
}
@conference {Robles:2006:MLS:1137983.1137986,
	title = {Mining large software compilations over time: another perspective of software evolution},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {3{\textendash}9},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {With the success of libre (free, open source) software, a new type of software compilation has become increasingly common. Such compilations, often referred to as {\textquoteright}distributions{\textquoteright}, group hundreds, if not thousands, of software applications and libraries written by independent parties into an integrated system. Software compilations raise a number of questions that have not been targeted so far by software evolution, which usually focuses on the evolution of single applications. Undoubtedly, the challenges that software compilations face differ from those found in single software applications. Nevertheless, it can be assumed that both, the evolution of applications and that of software compilations, have similarities and dependencies.In this sense, we identify a dichotomy, common to that in economics, of software evolution in the small (micro-evolution) and in the large (macro-evolution). The goal of this paper is to study the evolution of a large software compilation, mining the publicly available repository of a well-known Linux distribution, Debian. We will therefore investigate changes related to hundreds of millions of lines of code over seven years. The aspects that will be covered in this paper are size (in terms of number of packages and of number of lines of code), use of programming languages, maintenance of packages and file sizes.},
	keywords = {debian, distributions, evolution, large software collections, lines of code, loc, metrics, mining software repositories, size, sloc, sloccount, software evolution, software integrators},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137986},
	url = {http://doi.acm.org/10.1145/1137983.1137986},
	attachments = {https://flosshub.org/sites/flosshub.org/files/3miningLarge.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Martin Michlmayr and Amor, Juan Jose}
}
@conference {WeiBgerber:2006:MRA:1137983.1138028,
	title = {Mining refactorings in ARGOUML},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	note = {"To see if refactorings in ARGOUML have an effect on the occurrence of new bugs and on communication between the developers, we relate the refactorings to bug reports in ISSUEZILLA respectively to mails on the developer mailing list. "},
	pages = {175{\textendash}176},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper we combine the results of our refactoring reconstruc- tion technique with bug, mail and release information to perform process and bug analyses of the ARGOUML CVS archive.},
	keywords = {argouml, bug tracking, bugs, cvs, email, evolution, mining challenge, msr challenge, re-engineering, refactoring, release history},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138028},
	url = {http://doi.acm.org/10.1145/1137983.1138028},
	attachments = {https://flosshub.org/sites/flosshub.org/files/175MiningRefactorings.pdf},
	author = {Wei{\ss}gerber, Peter and Diehl, Stephan and G{\"o}rg, Carsten}
}
@conference {Kagdi:2006:MSC:1137983.1137996,
	title = {Mining sequences of changed-files from version histories},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {47{\textendash}53},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Modern source-control systems, such as Subversion, preserve change-sets of files as atomic commits. However, the specific ordering information in which files were changed is typically not found in these source-code repositories. In this paper, a set of heuristics for grouping change-sets (i.e., log-entries) found in source-code repositories is presented. Given such groups of change-sets, sequences of files that frequently change together are uncovered. This approach not only gives the (unordered) sets of files but supplements them with (partial temporal) ordering information. The technique is demonstrated on a subset of KDE source-code repository. The results show that the approach is able to find sequences of changed-files.},
	keywords = {change, change history, change management, change sequences, heuristics, kde, mining software repositories, scm, sequences, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137996},
	url = {http://doi.acm.org/10.1145/1137983.1137996},
	attachments = {https://flosshub.org/sites/flosshub.org/files/47MiningSequences.pdf},
	author = {Kagdi, Huzefa and Yusuf, Shehnaaz and Maletic, Jonathan I.}
}
@conference {Voinea:2006:MSR:1137983.1138024,
	title = {Mining software repositories with CVSgrab},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {167{\textendash}168},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	keywords = {argouml, cvs, cvsgrab, evolution, mining challenge, msr challenge, postgresql, software visualization, source code, team, visualization},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138024},
	url = {http://doi.acm.org/10.1145/1137983.1138024},
	attachments = {https://flosshub.org/sites/flosshub.org/files/167MiningSoftware.pdf},
	author = {Voinea, Lucian and Telea, Alexandru}
}
@conference {Zimmermann:2006:MVA:1137983.1138001,
	title = {Mining version archives for co-changed lines},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {72{\textendash}75},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Files, classes, or methods have frequently been investigated in recent research on co-change. In this paper, we present a first study at the level of lines. To identify line changes across several versions, we define the annotation graph which captures how lines evolve over time. The annotation graph provides more fine-grained software evolution information such as life cycles of each line and related changes: "Whenever a developer changed line 1 of version.txt she also changed line 25 of Library.java."},
	keywords = {change, change analysis, change management, graph, lines of code, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138001},
	url = {http://doi.acm.org/10.1145/1137983.1138001},
	attachments = {https://flosshub.org/sites/flosshub.org/files/72MiningVersionArchives.pdf},
	author = {Zimmermann, Thomas and Kim, Sunghun and Zeller, Andreas and Whitehead,Jr., E. James}
}
@conference {889,
	title = {Motivating Participation by Displaying the Value of Contribution},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2006},
	month = {22/04/2006},
	pages = {955-958},
	publisher = {ACM},
	organization = {ACM},
	address = {Montreal, Quebec, Canada},
	isbn = {1-59593-372-7},
	author = {Al Mamunur Rashid and Kimberly Ling and Regina D Tassone and Paul Resnick and Robert Kraut and John Riedl}
}
@article {1124,
	title = {Motivation, Governance, and the Viability of Hybrid Forms in Open Source Software Development},
	journal = {Management Science},
	volume = {52},
	year = {2006},
	note = {"Data from three primary sources informed this research (Table 1). All data were collected in 2001{\textendash}2002."
Online project documentation: All publicly available project descriptions, charters, bylaws, meeting minutes, etc.
Mailing lists: Over 2,000 messages read over a three-month period prior to interviews
Interviews 
"Ireadallpostingstoproject-specific and general mailing lists for both communities for a three-month period preceding the interviews. Over 2,000 messages were posted during this period. Read- ing these messages allowed me to gain familiarity with the technology..."},
	month = {07/2006},
	pages = {1000 - 1014},
	abstract = {Open source software projects rely on the voluntary efforts of thousands of software developers, yet we know little about why developers choose to participate in this collective development process. This paper inductively derives a framework for understanding participation from the perspective of the individual software developer based on data from two software communities with different governance structures.

In both communities, a need for software-related improvements drives initial participation. The majority of participants leave the community once their needs are met, however, a small subset remains involved. For this set of developers, motives evolve over time and participation becomes a hobby. These hobbyists are critical to the long-term viability of the software code: They take on tasks that might otherwise go undone and work to maintain the simplicity and modularity of the code. Governance structures affect this evolution of motives. Implications for firms interested in implementing hybrid strategies designed to combine the advantages of open source software development with proprietary ownership and control are discussed.},
	keywords = {email, email archives, governance, INNOVATION, interview, mailing list, MOTIVATION, open source software development, Volunteers},
	issn = {1526-5501},
	doi = {10.1287/mnsc.1060.0553},
	url = {http://faculty.washington.edu/skshah/Shah\%20-\%20Motivation,\%20Governance,\%20Hybrid\%20Forms.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Shah\%20-\%20Motivation\%2C\%20Governance\%2C\%20Hybrid\%20Forms.pdf},
	author = {Shah, Sonali K.}
}
@article {895,
	title = {Multi-Modal Modeling, Analysis and Validation of Open Source Software Development Processes},
	journal = {Intern. J. Internet Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	pages = {49-63},
	abstract = {Understanding the context, structure, activities, and content of software development processes found in practice has been and remains a challenging problem. In the world of free/open source software development, discovering and understanding what processes are used in particular projects is important in determining how they are similar to or different from those advocated by the software engineering community. Prior studies have revealed that development processes in F/OSSD projects are different in a number of ways. In this paper, we describe how a variety of modeling perspectives and techniques are used to elicit, analyze, and validate software development processes found in F/OSSD projects, with examples drawn from studies of the software requirements process found in the NetBeans.org project.},
	keywords = {empirical studies of software engineering, open source software development, process modeling, requirements processes, software process},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Scacchi-Jensen-Noll-Elliott-OSSC05.pdf},
	author = {Walt Scacchi and Chris Jensen and Noll, J. and Elliott, M.}
}
@conference {698,
	title = {Networks of Open Source Health Care Action},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {135 - 141},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper reports on an effort to create a network of both developers and users of a public health information system. Through an analysis of capacity, recruitment, and power in the network, issues related to choice of technologies, global-local tensions, and parameters of institutional collaboration, we illustrate a number of challenges. Comparing OSS principles to a {\textquotedblleft}Networks of Action{\textquotedblright} approach, conditions for learning in organizing training and development of software with participants from Africa, Asia, and Europe, as well as the involvement of advanced students in such efforts are discussed.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_13},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Networks\%20of\%20Open\%20Source\%20Health\%20Care\%20Action.pdf},
	author = {Staring, Knut and Titlestad, Ola}
}
@article {flosswp342,
	title = {New Perspectives on Public Goods Production: Policy Implications of Open Source Software},
	year = {2006},
	month = {December},
	abstract = {This article reveals some empirical data regarding the trend of evolving open source software (OSS) policies globally. Additionally, this article investigates why so many governments are considering support of OSS development, and weighs the pros and cons of such policies. The ultimate conclusion is that when two systems are equally suitable, governments may reasonably choose OSS over proprietary software because software industry market failures may justify such support of OSS development. While governments considering supporting OSS are primarily concerned with significant switching costs and incompatibility problems, OSS is actually superior to proprietary software because it increases compatibility and consequently decreases switching costs in the long term. Further, OSS will not only help developing countries build their information technology capabilities, but will also promote competition in the software market.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LeeOSS.pdf},
	author = {Jyh-An Lee}
}
@conference {Voinea:2006:OFC:1137983.1137993,
	title = {An open framework for CVS repository querying, analysis and visualization},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {33{\textendash}39},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {We present an open framework for visual mining of CVS software repositories. We address three aspects: data extraction, analysis and visualization. We first discuss the challenges of CVS data extraction and storage, and propose a flexible way to deal with CVS implementation inconsistencies. We next present a new technique to enrich the raw data with information about artifacts showing similar evolution. Finally, we propose a visualization backend and show its applicability on industry-size repositories.},
	keywords = {argouml, cvs, cvsgrab, evolution visualization, postgresql, software visualization},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137993},
	url = {http://doi.acm.org/10.1145/1137983.1137993},
	author = {Voinea, Lucian and Telea, Alexandru}
}
@article {1234,
	title = {Open Source in Web-Based Applications},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	year = {2006},
	month = {33/2006},
	pages = {81 - 94},
	abstract = {Business and recreational activities on the global communication infrastructure are increasingly based on the use of remote resources and services, and on the interaction between different, remotely located parties. In such a context, Single Sign-On technologies simplify the log-on process allowing automatic access to secondary domains through a unique log-on operation to the primary domain. In this article, we evaluate different Single Sign-On implementations focusing on the central role of Open Source in the development of Web-based systems. We outline requirements for Single Sign-On systems and evaluate four existing Open Source implementations in terms of degree of fulfilment of those requirements. Finally we compare those Open Source systems with respect to some specific Open Source community patterns.},
	issn = {1554-1053},
	doi = {10.4018/jitwe.2006070106},
	author = {Ardagna, Claudio Agostino and Frati, Fulvio and Gabriele Gianini}
}
@conference {700,
	title = {Open Source in Web-based Periodicals},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {347 - 348},
	publisher = {Springer},
	organization = {Springer},
	abstract = {In this paper we aim to investigate the role of the media in the diffusion of Open Source, analysing three web-based periodicals from Italy, United Kingdom and USA. The influence of the media in our society is wide and we have to look to that direction if we want to seriously investigate the in-depth causes of the different trends. Nevertheless, our results show a picture that may not be familiar to many researchers of the field.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_40},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20in\%20Web-based\%20Periodicals.pdf},
	author = {Baravalle, Andres and Chambers, Sarah}
}
@conference {701,
	title = {Open Source Software Development (OSSD) Based On Software Engineering},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {345 - 346},
	publisher = {Springer},
	organization = {Springer},
	abstract = {With the advent of Open Source Software (OSS) at the end of last century, many proponents believe that OSS is a new software development process and some even advocate OSS as a revolution for software engineering. The Cathedral and the Bazaar is a typical metaphor of the software development methodologies for the Closed Source Software (CSS) and the OSS. By comparing the phased (namely, requirement analysis, document design and system design, coding, testing and maintenance) software development methodology proposed by Software Engineering (SE), and by studying the management tools provided by SourceForge.net, we believe OSS development method not only follows the phased software development process, but also in return enriches the theory of SE.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_39},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Software\%20Development\%20\%28OSSD\%29.pdf},
	author = {Zhu, Dengya and Potdar, Vidyasagar and Chang, Elizabeth}
}
@conference {814,
	title = {Open Source Technical Support: A Look at Peer Help-Giving},
	booktitle = {39th Annual Hawaii International Conference on System Sciences (HICSS{\textquoteright}06)Proceedings of the 39th Annual Hawaii International Conference on System Sciences (HICSS{\textquoteright}06)},
	volume = {6},
	year = {2006},
	pages = {118c},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Kauia, HI, USA},
	abstract = {We explore online technical support of open source software by a study of postings to discussion boards. Our results indicate that there are several types of detail that are required by the help-givers to be able to diagnose and remediate help-seekers{\textquoteright} difficulties. As a result help interactions may iterate somewhat inefficiently. These findings are compared with studies of telephone technical help lines for commercial software, and library reference interviews. By considering certain rather problematic interactions we can identify ways to improve the process.},
	doi = {10.1109/HICSS.2006.370},
	author = {Singh, V and Twidale, M.B and Rathi, D.}
}
@unpublished {flosswp346,
	title = {Open Source \& The Irish Software Industry?},
	year = {2006},
	month = {September},
	abstract = {The open source software movement is a global phenomenon that is having a significant impact on the global software industry. It is changing the way in which software companies and people view the software development process. It is changing the way in which software companies capture value. It is commoditizing segments of the software market and is creating new business models and new ways of capturing value. It is lauded by some and vilified by others. It is often painted in a biblical light ??? David taking on Goliath. Yet, many of the Goliaths??? are also benefiting from this movement. This dissertation explores this - How can companies manage the impacts of the open source software movement to their advantage? This research examines the phenomenon in the context of the Irish Industry. Through a review of the existing literature this dissertation develops and exploratory framework for investigating different factors that might be influential in looking at how Indigenous Irish Software firms might manage the impacts of open source software movement. It weaves facets of different research areas together to produce this framework. The framework is then tested using several techniques including a qualitative survey. The dissertation includes several sections that apply the framework in order to analyze and develop profiles of several different firms. These profiles are then used to look at some of the different strategies and tactics available to firms. In many cases, examples are drawn from the global software industry to illustrate these approaches. The research concludes that there are factors that influence how a firm can manage the impact of the open source movement. It also builds on the initial framework to offer a more complete approach to understanding the factors that change the way in which firms manage the impacts of the open source software movement.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ReducedSizeThesis.pdf},
	author = {Ed Sherwood-Smith}
}
@article {2006,
	title = {Opportunities and Challenges Applying Functional Data Analysis to the Study of Open Source Software Evolution},
	journal = {Statistical Science},
	volume = {21},
	number = {2},
	year = {2006},
	note = {"As part of a larger project, data were collected on 105 OSS	projects hosted online at Sourceforge (sf.net)." "...we limited our data collection to projects that use only the Java programming language and were listed in the Internet and System Networking domains." "... only including these projects that use an OSI approved license..." "had to have posted at least one file on the Sourceforge site as of the time of our initial project selection Fall 2002" "Data were collected on the published release history of each project thatmet the screening criteria. Each release of each project was
analyzed to calculate CplXLCoh. The size of each release was measured using a calculation of the number of lines of code (LOC)"},
	pages = {167-178},
	publisher = {Institute of Mathematical Statistics},
	abstract = {This paper explores the application of functional data analysis (FDA) as a means to study the dynamics of software evolution in the open source context. Several challenges in analyzing the data from software projects are discussed, an approach to overcoming those challenges is described, and preliminary results from the analysis of a sample of open source software (OSS) projects are provided. The results demonstrate the utility of FDA for uncovering and categorizing multiple distinct patterns of evolution in the complexity of OSS projects. These results are promising in that they demonstrate some patterns in which the complexity of software decreased as the software grew in size, a particularly novel result. The paper reports preliminary explorations of factors that may be associated with decreasing complexity patterns in these projects. The paper concludes by describing several next steps for this research project as well as some questions for which more sophisticated analytical techniques may be needed.},
	keywords = {complexity, evolution, fda, java, lines of code, loc, release history, scm, size, sourceforge},
	issn = {08834237},
	url = {http://www.jstor.org/stable/27645747},
	author = {Stewart, Katherine J. and Darcy, David P. and Daniel, Sherae L.}
}
@conference {702,
	title = {Organization of Internet Standards},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {267 - 272},
	publisher = {Springer},
	organization = {Springer},
	abstract = {In this study we look at a body of standards documents in RFCs(Request For Comments) of IETF (Internet Engineering Task Force). The cross references between these documents form a network. Approaches from social network analysis are deployed to assess centrality of artifacts in this network and identify cohesive subgroups and levels of cohesion. Our results demonstrate major groups centered around key standard tracks, and application of network metrics reflect different levels of cohesion for these groups. As application of these techniques in such domains is unusual, possible uses in open source projects for strategizing are discussed.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Organization\%20of\%20Internet\%20Standards.pdf},
	author = {Gen{\c c}er, Mehmet and Oba, Beyza and {\"O}zel, B{\"u}lent and Tunal{\i}o{\u g}lu, V.}
}
@conference {712,
	title = {The Organizational Adoption of Open Source Server Software by Belgian Organizations},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {111 - 122},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This study reports on five case studies in Belgian organizations that currently use open source server software. Respondents were asked about their motivation to use open source server software. Our results indicate that the lower cost, high reliability and availability of external support are the prime reasons why organizations use open source software. The often claimed advantage of open source software of having access to the source code was found relevant only for those organizations who perform development based on open source software. Some factors that were found relevant in previous studies (such as the support of standards) were however deemed less important by the organizations in our sample.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_11},
	attachments = {https://flosshub.org/sites/flosshub.org/files/The\%20Organizational\%20Adoption\%20of\%20OSS\%20Server.pdf},
	author = {Ven, Kris and Verelst, Jan}
}
@conference {703,
	title = {Participation in Free and Open Source Communities: An Empirical Study of Community Members{\textquoteright} Perceptions},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {221 - 231},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Although the defining factors of Free and Open Source Software (FOSS) are generally seen as the availability and accessibility of the source code, it is what these facilitate that is perhaps of more significance. Source code availability allows the sharing of code, skills, knowledge, and effort, focused on a particular piece of software under development. The result of this is the FOSS community, which although often perceived as a single group, is actually many small groups, each bound by a common interest in a particular piece of software and using the Internet as a communication medium. Although there have been studies focusing on the motivation of FOSS developers to contribute to software, there has been little investigation into the motives, attitudes, and the culture within the communities as a whole. There is much more to most of these communities than software development. Many also have extensive support networks for the use of software, portals for research, and social facilities. This paper describes the results of an investigation into how FOSS community members perceive the communities that they belong to, their reasons for being in the community, and the manner in which they participate.
},
	keywords = {Survey},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_22},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Participation\%20in\%20free\%20and\%20open\%20source.pdf},
	author = {Schofield, Andrew and Cooper, Grahame}
}
@conference {704,
	title = {Perceptions and Uptake of Open Source in Swedish Organisations},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {155 - 163},
	publisher = {Springer},
	organization = {Springer},
	abstract = {There are many different ways in which Open Source ideas can be adopted by business, and influence the way in which companies do business. A number of different surveys have been conducted in different countries with the purpose of understanding the state of practice with respect to Open Source in companies. A number of different business models have been observed, ranging from the use of Open Source infrastructure products to basing a company{\textquoteright}s entire business model on Open Source. In this paper we report on a study of the perceptions of Open Source and the uptake of open source products and development models in Swedish companies. We investigate this from the standpoint of stakeholders in those companies which have an expressed interest in Open Source, allowing a more in-depth analysis of the extent to which Open Source has influenced business thinking. From our analysis we find that uptake is much higher than reported in earlier studies, but is still concentrated in SMEs, consistent with the findings of previous studies. There is increased evidence of interest beyond the simple use of OS components at the (LAMP) infrastructure level. In particular, a significant proportion of the companies are in a symbiotic relationship with the OS community, supporting both through participation in existing projects and the release of new software under OS licences.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_15},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Perceptions\%20and\%20Uptake\%20of\%20Open\%20Source.pdf},
	author = {Lundell, Bj{\"o}rn and Lings, Brian and Lindqvist, Edvin}
}
@conference {Knab:2006:PDD:1137983.1138012,
	title = {Predicting defect densities in source code files with decision tree learners},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {119{\textendash}125},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {With the advent of open source software repositories the data available for defect prediction in source files increased tremendously. Although traditional statistics turned out to derive reasonable results the sheer amount of data and the problem context of defect prediction demand sophisticated analysis such as provided by current data mining and machine learning techniques.In this work we focus on defect density prediction and present an approach that applies a decision tree learner on evolution data extracted from the Mozilla open source web browser project. The evolution data includes different source code, modification, and defect measures computed from seven recent Mozilla releases. Among the modification measures we also take into account the change coupling, a measure for the number of change-dependencies between source files. The main reason for choosing decision tree learners, instead of for example neural nets, was the goal of finding underlying rules which can be easily interpreted by humans. To find these rules, we set up a number of experiments to test common hypotheses regarding defects in software entities. Our experiments showed, that a simple tree learner can produce good results with various sets of input data.},
	keywords = {change analysis, data mining, decision tree learner, defect density, defect prediction, mozilla, prediction, release history, scm, source code, version control},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138012},
	url = {http://doi.acm.org/10.1145/1137983.1138012},
	attachments = {https://flosshub.org/sites/flosshub.org/files/119Predicting.pdf},
	author = {Knab, Patrick and Pinzger, Martin and Bernstein, Abraham}
}
@article {flosswp347,
	title = {A preliminary examination of code review processes in open source projects},
	year = {2006},
	month = {January},
	abstract = {In this paper, we provide preliminary answers to the following questions regarding OSS peer review or inspection. What is the patch process and review process used by the projects? What types of review does a the project use? Why are patches rejected? What percentage of patches are rejected? Who performs the review? Are the top developers also the top reviewers? When are reviews performed? What is the frequency of review? How long do reviews take to perform? How does the patch size affect the review? How does merit-based trust among actors affect the review? Are more trusted individuals reviewed less often? How much feedback is provided in the review? What kinds of non-source code patches are reviewed? How does the kind of patch affect the review? What affect does reviewing have on other elements of the patch process? What is the relationship between reviewing and testing? The first two questions are answered in a qualitative manner for GCC, Linux, Mozilla, and Apache. The remaining questions are answered for the Apache project. The most striking similarities among projects is there use of a pre-commit review and requests for small, complete, independent patches. The Apache project also uses a post-commit review of trusted members. Reviews in the Apache project occur very frequently and usually have a review interval of hours. A small core group of reviewers conduct over 80\% of reviews for Apache; however, the number of and actual individuals fluctuates over the 9 years of data we examine.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Rigby2006TR.pdf},
	author = {Peter C. Rigby and Daniel M. German}
}
@conference {705,
	title = {Producing and Interpreting Debug Texts},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {335 - 336},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper presents preliminary findings from an ethnographic study of distributed, parallel debugging in an open source software (OSS) community. Focusing on the OSS developers{\textquoteright} daily activities, I propose the concept of making software debuggable. In so doing, I see a somewhat different story than common narratives of debugging in current OSS research, which describes distributed, parallel debugging as a set of highly cohesive tasks within loosely couple groups. I find that parallel, distributed debugging is rather a closely coupled collective process of producing and interpreting debug texts with high cohesion between the activities of reporting, finding, and understanding bugs.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_34},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Producing\%20and\%20Interpreting\%20Debug\%20Texts.pdf},
	author = {{\O}sterlie, Thomas}
}
@conference {1229,
	title = {Regurgitate: Using GIT For F/LOSS Data Collection},
	booktitle = {1st Workshop on Public Data about Software Development (WoPDaSD 2006)},
	year = {2006},
	abstract = {We have created a new tool, regurgitate, for importing CVS repositories into the GIT source code management system. Important features of GIT include great expressiveness in capturing relationships between revisions and across files as well as extremely high-speed processing. These features make GIT an ideal platform for gathering detailed longitudinal metrics for open source projects. The availability of regurgitate facilitates using GIT as an analysis tool for that majority of open source projects that keep their repositories in CVS. In particular, GIT is fast enough that it is practical to replay the entire development history of a project commit-at-a-time, collecting metrics at each step. We demonstrate this process for a simple metric and a collection of benchmark F/LOSS repositories.},
	keywords = {cvs, cvsanaly, git, history, promise, regurgitate, scm},
	attachments = {https://flosshub.org/sites/flosshub.org/files/massey.pdf},
	author = {Bart Massey and Keith Packard}
}
@conference {706,
	title = {Retrieving Open Source Software Licenses},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {35 - 46},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Open Source Software maintenance and reuse require identifying and comprehending the applied software licenses. This paper first characterizes software maintenance, and open source software (OSS) reuse which are particularly relevant in this context. The information needs of maintainers and reusers can be supported by reverse engineering tools at different information retrieval levels. The paper presents an automated license retrieval approach called ASLA. User needs, system architecture, tool features, and tool evaluation are presented. The implemented tool features support identifying source file dependencies and licenses in source files, and adding new license templates for identifying licenses. The tool is evaluated against another tool for license information extraction. ASLA requires the source code as available input but is otherwise not limited to OSS. It supports the same programming languages as GCC. License identification coverage is good and the tool is extendable.
},
	keywords = {gaim, license, license analysis, maintenance, mozilla, reuse},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Retrieving\%20Open\%20Source\%20Software\%20Licenses.pdf},
	author = {Tuunanen, Timo and Koskinen, Jussi and K{\"a}rkk{\"a}inen, Tommi}
}
@conference {707,
	title = {Reusable Parser Generation from Open Source Compilers},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {343 - 344},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Without Abstract},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_38},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Reusable\%20Parser\%20Generation.pdf},
	author = {Maeda, Kazuaki}
}
@conference {676,
	title = {A Robust Open Source Exchange for Open Source Software Development},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {99 - 108},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper addresses the development of mechanisms for the creation of OSSD exchanges that could be used by developers across any geographical range, as long as all the developers can interact via some open network infrastructure such as the Internet. The structure of these exchanges can range from public repositories such as Sourceforge.net to intra-organizational forums for software development within an enterprise. We examine in particular the structure of an exchange model based on protocols for a robust online marketplace.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_10},
	attachments = {https://flosshub.org/sites/flosshub.org/files/A\%20Robust\%20Open\%20Source\%20Exchange.pdf},
	author = {Basu, Amit}
}
@conference {713,
	title = {The role of mental models in FLOSS development work practices},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {91 - 97},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Shared understandings are important for software development as they guide to effective individual contributions to, and coordination of, the software development process. In this paper, we present the theoretical background and research design for a proposed study on shared mental models within Free/Libre Open Source Software (FLOSS) development teams. In particular, we plan to perform case studies on several projects and to use cognitive maps analysis to represent and compare the mental models of the involved members so as to gauge the degree of common knowledge and the development of a collective mind as well as to better understand the reasons that underlie team members actions and the way common mental models, if any, arise.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/The\%20role\%20of\%20mental\%20medels.pdf},
	author = {Kevin Crowston and Barbara Scozzi}
}
@article {886,
	title = {Scope and Timing of Deployment: Moderators of Organizational Adoption of the Linux Server Platform.},
	journal = {International Journal of IT Standards Research},
	volume = {4},
	year = {2006},
	month = {7/2006},
	pages = {1-23},
	abstract = {<p>\&nbsp;Market selection of product compatibility standards has long been explained through aggregate positive-feedback theoretical models of economic utility. Explaining aggregate patterns of organizational standards adoption requires two additional steps \&mdash; not only differences between organizations, but also differences within organizations.</p><p>Here we present a qualitative study of how organizations do (or do not) adopt a new computer server platform standard, namely Linux using PC-compatible hardware. While discussions of Linux typically focus on its open source origins, our respondents were primarily interested in low price. Despite this relative advantage in price, incumbent standards enjoyed other advantages identified by prior theory, namely network effects and switching costs.</p><p>We show when, how and why such incumbent advantages are overcome by a new standard. We find that Linux adoption within organizations began for uses with a comparatively limited scope of deployment, thus minimizing network effect and switching costs disadvantages. We identify four attributes of information systems that potentially limit the scope of deployment: few links of the system to organizational processes, special-purpose computer systems, new uses and replacement of obsolete systems. We also identify an organizational level variable \&mdash; internal standardization \&mdash; which increases scope of deployment and thus the attractiveness of the incumbent standard.</p><p>\&nbsp;</p>},
	author = {Joel West and Dedrick, Jason}
}
@article {1088,
	title = {Self-Organization Patterns in Wasp and Open Source Communities},
	journal = {IEEE Intelligent Systems},
	volume = {21},
	year = {2006},
	note = {"To investigate such claims, we studied an OSS community{\textquoteright}s social network from a dataset describing the email activity of 120 different software teams"
"Our test data originated from Sourceforge (http://sourceforge.net), a large open source project repository, and included communi- ties ranging from very small networks with one or two members to large networks with thousands of members."
"we limited our consideration to email traffic associated with bug fixes and bug reporting. As other researchers have shown[5] this email subset allows an effective reconstruction of the software community{\textquoteright}s social network."
"We thank Kevin Crowston and James Howison for making their software data publicly available."},
	month = {03/2006},
	pages = {36 - 40},
	abstract = {In this paper, we conducted a comparative study of how social organization takes place in a wasp colony and OSS developer communities. Both these systems display similar global organization patterns, such as hierarchies and clear labor divisions. As our analysis shows, both systems also define interacting agent networks with similar common features that reflect limited information sharing among agents. As far as we know, this is the first research study analyzing the patterns and functional significance of these systems{\textquoteright} weighted-interaction networks. By illuminating the extent to which self-organization is responsible for patterns such as hierarchical structure, we can gain insight into the origins of organization in OSS communities.},
	keywords = {agents, decentralization, developers, email, email archives, flossmole, hierarchy, labor division, organization, self-organizing teams, social network analysis, social networks, sourceforge, teams, wasps},
	issn = {1541-1672},
	doi = {10.1109/MIS.2006.34},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.95.5574\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/valverde.pdf},
	author = {Valverde, S. and Theraulaz, G. and Gautrais, J. and Fourcassie, V. and Sole, R.V.}
}
@article {flosswp351,
	title = {Skills, Division of Labor and Performance in Collective Inventions. Evidence from the Open Source Software},
	year = {2006},
	month = {July},
	abstract = {This paper investigates the role of skills and the division of labor among participants in collective inventions. Our analysis draws on a large sample of projects registered at Sourceforge.net, the world{\textquoteright}s largest incubator of open source software activity. We test the hypothesis that the level of skills of participants and their skill variety are important for project performance. Skill heterogeneity across participants is in line with two fundamental organizational features of the open source development model: team work and modular design. We also explore the hypothesis whether the level of modularization of project activities is an important predictor of performance. Our econometric estimations show that both skill level and skill heterogeneity positively affect projects{\textquoteright} survival and performances. However, the impact of skill diversity is non linear. Design modularity is also positively associated with the performance of the project.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/giuriplonerrullanitorrisi.pdf},
	author = {Paola Giuri and Matteo Ploner and Francesco Rullani and Salvatore Torrisi}
}
@article {111,
	title = {Social dynamics of free and open source team communications},
	journal = {Proceedings of the IFIP 2nd International Conference on Open Source Software, Lake Como, Italy},
	year = {2006},
	author = {James Howison and Inoue, K. and Kevin Crowston}
}
@conference {708,
	title = {Social dynamics of free and open source team communications},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {06/2006},
	pages = {319 - 330},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper furthers inquiry into the social structure of free and open source software (FLOSS) teams by undertaking social network analysis across time. Contrary to expectations, we confirmed earlier findings of a wide distribution of centralizations even when examining the networks over time. The paper also provides empirical evidence that while change at the center of FLOSS projects is relatively uncommon, participation across the project communities is highly skewed, with many participants appearing for only one period. Surprisingly, large project teams are not more likely to undergo change at their centers.
},
	keywords = {bug fixing, bug reports, bug tracker, bug tracking, bugs, communications, Dynamic social networks, FLOSS teams, Human Factors, social network analysis, software development, sourceforge},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_32},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Social\%20dynamics\%20of\%20free\%20and\%20open\%20source\%20team.pdf},
	author = {Howison, James and Inoue, Keisuke and Kevin Crowston}
}
@conference {709,
	title = {Software Patents and Open Source Software in the European Union: Evidences of a Trade-Off?},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {349 - 351},
	publisher = {Springer},
	organization = {Springer},
	abstract = {The present work aims at giving an account of the patenting behaviour in the software sector, focusing on the European Union and pointing out issues regarding a trade-off which would support a policy attitude in favour of a wider diffusion of the Open Source model.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_41},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Software\%20Patents\%20and\%20Open\%20Source\%20Software.pdf},
	author = {Rentocchini, Francesco and De Prato, Giuditta}
}
@article {1119,
	title = {Strategic Interaction and Knowledge Sharing in the KDE Developer Mailing List},
	journal = {Management Science},
	volume = {52},
	year = {2006},
	note = {"the threaded discussion from the K Desktop Environment (KDE) developer mailing list was used."
March 15 to March 31, 2000.
128 threads selected.
measures: (1) level of participation measured by number of postings made by indiv. devs in a thread
(2) conversational interactivity (how long is a conversation)
(3) cross-thread connectivity},
	month = {07/2006},
	pages = {1031 - 1042},
	abstract = {In stark contrast with the fully participative "bazaar" imagery of open source software (OSS) development, some recent empirical research has pointed out that much of the OSS development is carried out by a small percentage of developers. This raises serious concerns that concentration of development effort on a few will limit knowledge sharing and underutilize the available resources. Using the notion of strategic interaction, this paper argues that individual developers often interact strategically with other highly resourceful developers by forming a smaller but better organized structure to intensify the types of epistemic interactions that matter most to the OSS development. A general framework of strategic interaction including participation inequality, conversational interactivity, and cross-thread connectivity is proposed to examine its impact on knowledge sharing, and validated using 128 discussion threads from the K Desktop Environment (KDE) developer mailing list. The findings indicate that strategic interaction has expanded knowledge sharing but with the caveat that extreme concentration of development could have an opposite effect. For researchers, this study dovetails the incentive logic by proposing and validating the strategic aspects of OSS participation to better understand the collective dynamics underpinning OSS development. Practitioners can use this approach to evaluate and better support existing knowledge-sharing initiatives.},
	keywords = {developers, email, email archives, kde, knowledge collaboration, knowledge sharing, mailing list},
	issn = {1526-5501},
	doi = {10.1287/mnsc.1060.0551},
	author = {Kuk, George}
}
@unpublished {flosswp404,
	title = {A structurational perspective on leadership in technology-supported self-organizing small groups},
	year = {2006},
	month = {October},
	publisher = {Syracuse University School of Information Studies},
	type = {Working Paper},
	abstract = {In this conceptual paper, we present a structuration-based theory of leadership behaviours in virtual teams, that is to say, in self-organizing technology-supported small groups such as Free/Libre Open Source Software development teams. Such teams are often composed of members of relatively equal status or who are so disparate in background that formal organizational status seems irrelevant, reducing the usual leadership cues provided by organizational status and title. Building on behavioural leadership theory and structuration theory, we present a two-order theory of leadership. It describes four classes of first-order leadership behaviours (task coordination, substantive task contribution, group maintenance, and boundary spanning) and defines second-order leadership as behaviour that influences changes in the structure that guides group action. Specifically, we suggest that second-order leadership behaviours are those that build structures of signification in the form of interpretive schema, structures of domination in the form of role structures and structures of legitimation in the form of rules and norms. We argue that second-order leadership is enabled by first-order leadership, is therefore action embedded, and is grounded in processes that define the social identity of the group. We propose that effective teams will exhibit a paradoxical combination of shared, distributed first-order leadership complemented by strong, concentrated, and centralized second-order leadership. We conclude by suggesting future research that might be conducted to test and further elaborate our theory.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHeckmanMisiolek.pdf},
	author = {Kevin Crowston and Robert Heckman and Nora Misiolek}
}
@conference {German:2006:SCP:1137983.1138022,
	title = {A study of the contributors of PostgreSQL},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {163{\textendash}164},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {This report describes some characteristics of the development team of PostgreSQL that were uncovered by analyzing the history of its software artifacts as recorded by the project{\textquoteright}s CVS repository.},
	keywords = {contributions, contributors, cvs, developers, mining challenge, mining software repositories, msr challenge, patches, postgresql, revision history, roles, software evolution, source code, team},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138022},
	url = {http://doi.acm.org/10.1145/1137983.1138022},
	attachments = {https://flosshub.org/sites/flosshub.org/files/163AStudyOf.pdf},
	author = {Daniel M. German}
}
@conference {677,
	title = {A study on the introduction of Open Source Software in the Public Administration},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {165 - 171},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper reports about a study on the introduction of Open Source Software (OSS) in a Public Administration located in Europe. The Public Administration examined has introduced OSS as a means to save on the license costs and to have a larger space for customisation purposes. The adoption of new software may have an impact on the employees{\textquoteright} productivity that need to be addressed.
In this article, we compare the usage of OpenOffice.org and Microsoft Office. Data about the usual office activities performed by the users participating to the experimentation have been collected by means of an automated non-invasive data collection tool. The result of this study reports a similar usage pattern of both suites in terms of workload, but a different approach in using functionalities provided by each software. A further analysis on the life cycles of documents elaborated with the office suites seems to validate the similarities among the software solutions examined.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_16},
	attachments = {https://flosshub.org/sites/flosshub.org/files/A\%20study\%20on\%20the\%20introduction\%20of\%20OSS.pdf},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo}
}
@conference {892,
	title = {tagging, community, vocabulary, evolution},
	booktitle = {Computer Supported Cooperative Work},
	year = {2006},
	month = {04/11/2006},
	pages = {181-190},
	publisher = {ACM},
	organization = {ACM},
	address = {Banff, Alberta, Canada},
	isbn = {1-59593-249-6},
	author = {Shilad Sen and Shyong K. Lam and Dan Cosley and Al Mamunur Rashid and Dan Frankowski and Franklin Harper and Jeremy Osterhouse and John Riedl}
}
@conference {1230,
	title = {A tool for the measurement, storage, and pre-elaboration of data supporting the release of public datasets},
	booktitle = {1st Workshop on Public Data about Software Development (WoPDaSD 2006)},
	year = {2006},
	abstract = {The big number of projects producing open source software provides researches with the possibility to measure software artefacts, thus producing a huge amount of data that are available for analysis. In order to be efficient and reliable, the process of data retrieval and analysis needs to be adequately supported by tools. In particular, measurement tools should guarantee that a large amount of artefacts are measured in a coherent and efficient way. They should also guarantee that the delivered measures have a well specified structure and meaning, which should be agreed upon by the community of researchers interested in analysing the data. A problem that such tools have to face is that all the elements involved are highly variable: the data source can be available in different versions; the measures to be carried out can be defined in (often only slightly) different ways; it is usually different the output required by different types of analysis. Another non trivial problem is that measured data have to be stored persistently in a way that lets the user not only retrieve the data, but also the meta-data describing the measurement themselves. In this paper we describe a tool that addresses the requirements described above, and present a first implementation that satisfies several of such requirements. }
}
@conference {678,
	title = {A tool to support the introduction of GNU/Linux desktop system in a professional environment},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {253 - 260},
	publisher = {Springer},
	organization = {Springer},
	abstract = {The introduction of a GNU/Linux-based desktop system in a large company is often problematic, in terms of technical issues but especially for employees{\textquoteright} training costs. Mainly, these obstacles are represented by different hardware configurations that might require several ad-hoc activities to adapt a standard release to the specific environment, including company{\textquoteright}s application profile. On the other hand, GNU/Linux live distributions provide to the users{\textquoteright} community new and interesting capabilities, as self-configuration and better usability, but loosing compatibility with original distributions, that is unaffordable in professionals scenarios. DSS (Debased Scripts Set) is an answer to both questions. It is a live distribution that includes an unmodified Debian-based Linux release and a modular-designed file system.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_25},
	attachments = {https://flosshub.org/sites/flosshub.org/files/A\%20tool\%20to\%20support\%20the\%20introduction.pdf},
	author = {Di Cerbo, Francesco and Favara, Daniele and Scotto, Marco and Sillitti, Alberto and Succi, Giancarlo and Vernazza, Tullio}
}
@conference {1090,
	title = {A Topological Analysis of the Open Souce Software Development Community},
	booktitle = {Proceedings of the 38th Annual Hawaii International Conference on System Sciences},
	year = {2006},
	note = {"We extracted data from a 2003 data dump obtained from SourceForge. "
roles},
	pages = {1-10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Big Island, HI, USA},
	abstract = {The fast growth of OSS has increased the interest in studying the composition of the OSS community and its collaboration mechanisms. Moreover, the success of a project may be related to the underlying social structure of the OSS development community. In this paper, we perform a quantitative analysis of Open Source Software developers by studying the entire development community at SourceForge [26]. Statistics and social network properties are explored to find collaborations and the effects of different members in the OSS development community. Small world phenomenon and scale free behaviors are found in the SourceForge development network. These topological properties may potentially explain the success and efficiency of OSS development practices. We also infer from our analysis that weakly associated but contributing co-developers and active users may be an important factor in OSS development.},
	keywords = {contributors, developers, roles, social network analysis, social networks, sourceforge, srda, users},
	doi = {10.1109/HICSS.2005.57},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.132.6830\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/xuGao.pdf},
	author = {Jin Xu and Gao, Yongqin and Christley, S. and Madey, G.}
}
@conference {714,
	title = {Towards an Ontology for Open Source Software Development},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {65 - 75},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Software development is a knowledge intensive process and the information generated in open source software development projects is typically housed in a central Internet repository. Open source repositories typically contains vast amounts of information, much of it unstructured, meaning that even if a question has previously been discussed and dealt with it is not a trivial task to locate it. This can lead to rework and confusion amongst developers and possibly deter new developers from getting involved in the project in the first place. This paper will present the case for an open source software development ontology. Such an ontology would enable better categorization of information and the development of sophisticated knowledge portals in order to better organize community knowledge and increase efficiency in the open source development process.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Towards\%20an\%20Ontology\%20for\%20OSS\%20Development.pdf},
	author = {Simmons, Gregory and Dillon, Tharam}
}
@article {885,
	title = {Understanding Free/Open Source Software Development Processes},
	journal = {Software Process--Improvement and Practice},
	volume = {11},
	number = {2},
	year = {2006},
	month = {March/April},
	pages = {95-105},
	author = {Walt Scacchi and Feller, Joseph and Fitzgerald, Brian and Hissam, Scott and Lakhani, Karim}
}
@inbook {896,
	title = {Understanding Free/Open Source Software Evolution},
	booktitle = {Software Evolution and Feedback: Theory and Practice},
	year = {2006},
	pages = {181-206},
	publisher = {John Wiley and Sons Inc.},
	organization = {John Wiley and Sons Inc.},
	address = {New York},
	author = {Walt Scacchi},
	editor = {Madhavji, N.H. and Lehman, M.M. and Ramil, J.F. and Perry, D.}
}
@article {1122,
	title = {Understanding the Motivations, Participation, and Performance of Open Source Software Developers: A Longitudinal Study of the Apache Projects},
	journal = {Management Science},
	volume = {52},
	year = {2006},
	note = {"analyzing archival data collected from OSS project records over a period of four years"
"Apart from the source and binary codes of the actual software programs, Apache products include developer websites, change logs, documentation, and developer communications in the form of e-mail archives. From these products, we extracted two types of information: each contributor{\textquoteright}s progression along the Apache career path, and each contributor{\textquoteright}s source code contributions to the project."},
	month = {07/2006},
	pages = {984 - 999},
	abstract = {Understanding what motivates participation is a central theme in the research on open source software (OSS) development. Our study contributes by revealing how the different motivations of OSS developers are interrelated, how these motivations influence participation leading to performance, and how past performance influences subsequent motivations. Drawing on theories of intrinsic and extrinsic motivation, we develop a theoretical model relating the motivations, participation, and performance of OSS developers. We evaluate our model using survey and archival data collected from a longitudinal field study of software developers in the Apache projects. Our results reveal several important findings. First, we find that developers{\textquoteright} motivations are not independent but rather are related in complex ways. Being paid to contribute to Apache projects is positively related to developers{\textquoteright} status motivations but negatively related to their use-value motivations. Perhaps surprisingly, we find no evidence of diminished intrinsic motivation in the presence of extrinsic motivations; rather, status motivations enhance intrinsic motivations. Second, we find that different motivations have an impact on participation in different ways. Developers{\textquoteright} paid participation and status motivations lead to above-average contribution levels, but use-value motivations lead to below-average contribution levels, and intrinsic motivations do not significantly impact average contribution levels. Third, we find that developers{\textquoteright} contribution levels positively impact their performance rankings. Finally, our results suggest that past-performance rankings enhance developers{\textquoteright} subsequent status motivations.},
	keywords = {apache, change logs, contributions, email, email archives, extrinsic motivation, intrinsic motivation, mailing lists, MOTIVATION, open source software, participation, software development performance, source code, status, Survey},
	issn = {1526-5501},
	doi = {10.1287/mnsc.1060.0554},
	author = {Roberts, Jeffrey A. and Il-Horn Hann and Slaughter, Sandra A.}
}
@article {808,
	title = {Usability processes in open source projects},
	journal = {Software Process: Improvement and Practice},
	volume = {11},
	year = {2006},
	month = {03/2006},
	pages = {149 - 162},
	abstract = {We explore how some open source projects address issues of usability. We describe the mechanisms, techniques and technology used by open source communities to design and refine the interfaces to their programs. In particular we consider how these developers cope with their distributed community, lack of domain expertise, limited resources and separation from their users. We also discuss how bug reporting and discussion systems can be improved to better support bug reporters and open source developers.},
	issn = {1099-1670},
	doi = {10.1002/spip.256},
	author = {David M Nichols and Michael B Twidale}
}
@article {893,
	title = {User Choices and Regret: Understanding Users{\textquoteright} Decision Process bout Consensually Acquired Spyware},
	journal = {I/S: A Journal of Law and Policy for the Information Society},
	volume = {2},
	number = {2},
	year = {2006},
	month = {01/2006},
	author = {N. Good and J. Grossklags and Konstan, J.A. and D. Mulligan and A. Perzanowski and D. Thaw}
}
@conference {German:2006:UEA:1137983.1138020,
	title = {Using evolutionary annotations from change logs to enhance program comprehension},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {159{\textendash}162},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Evolutionary annotations are descriptions of how source code evolves over time. Typical source comments, given their static nature, are usually inadequate for describing how a program has evolved over time; instead, source code comments are typically a description of what a program currently does. We propose the use of evolutionary annotations as a way of describing the rationale behind changes applied to a given program (for example "These lines were added to ..."). Evolutionary annotations can assist a software developer in the understanding of how a given portion of source code works by showing him how the source has evolved into its current form.In this paper we describe a method to automatically create evolutionary annotations from change logs, defect tracking systems and mailing lists. We describe the design of a prototype for Eclipse that can filter and present these annotations alongside their corresponding source code and in workbench views. We use Apache as a test case to demonstrate the feasibility of this approach.},
	keywords = {annotations, apache, bug tracking, change history, eclipse, evolutionary, log files, mailing lists, mining software repositories, software evolution, version control},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138020},
	url = {http://doi.acm.org/10.1145/1137983.1138020},
	attachments = {https://flosshub.org/sites/flosshub.org/files/159UsingEvolutionary.pdf},
	author = {Daniel M. German and Peter C. Rigby and Storey, Margaret-Anne}
}
@conference {890,
	title = {Using Intelligent Task Routing and Contribution Review to Help Communities Build Artifacts of Lasting Value},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2006},
	month = {22/04/2006},
	pages = {1037-1046},
	publisher = {ACM},
	organization = {ACM},
	address = {Montreal, Quebec, Canada},
	isbn = {1-59593-372-7},
	author = {Cosley, D. and D. Frankowski and Terveen, L. and Riedl, J.}
}
@conference {Kakimoto:2006:USB:1137983.1138026,
	title = {Using software birthmarks to identify similar classes and major functionalities},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {171{\textendash}172},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	keywords = {argouml, class, file, mining challenge, msr challenge, multi-dimensional scaling, similarity, software birthmark, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138026},
	url = {http://doi.acm.org/10.1145/1137983.1138026},
	attachments = {https://flosshub.org/sites/flosshub.org/files/171UsingSoftware.pdf},
	author = {Kakimoto, Takeshi and Monden, Akito and Kamei, Yasutaka and Tamada, Haruaki and Tsunoda, Masateru and Matsumoto, Ken-ichi}
}
@conference {699,
	title = {On the Weickian Model in the Context of Open Source Software Development: Some Preliminary Insights},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {3 - 8},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Despite being regarded as a path-breaking model of organising, Weick{\textquoteright}s Enactment-Selection-Retention (ESR) model has been labelled too abstract a model find any practical applications. This paper attempts to show that exploration-oriented open source projects represent valuable case studies where Weick{\textquoteright}s ESR model can be applied. By taking the Linux case study as a case in point, it is argued that a qualitative analysis of micro interactions (i.e. double interacts) might reveal broad organising patterns. Preliminary implications in terms of coordination and knowledge making processes are discussed in the final section.
},
	keywords = {case study, linux},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/On\%20the\%20Weickian\%20Model\%20in\%20the\%20Context.pdf},
	author = {Iannacci, Federico}
}
@conference {Canfora:2006:BRK:1137983.1138032,
	title = {Where is bug resolution knowledge stored?},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {183{\textendash}184},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {ArgoUML uses both CVS and Bugzilla to keep track of bug-fixing activities since 1998. A common practice is to reference source code changes resolving a bug stored in Bugzilla by inserting the id number of the bug in the CVS commit notes. This relationship reveals useful to predict code entities impacted by a new bug report.In this paper we analyze ArgoUML software repositories with a tool, we have implemented, showing what are Bugzilla fields that better predict such impact relationship, that is where knowledge about bug resolution is stored.},
	keywords = {argouml, bugs, bugzilla, cvs, impact analysis, mining challenge, mining software repositories, msr challenge, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138032},
	url = {http://doi.acm.org/10.1145/1137983.1138032},
	attachments = {https://flosshub.org/sites/flosshub.org/files/183WhereIsBug.pdf},
	author = {Canfora, Gerardo and Cerulo, Luigi}
}
@conference {Anvik:2006:FTB:1134285.1134336,
	title = {Who should fix this bug?},
	booktitle = {Proceedings of the 28th international conference on Software engineering},
	series = {ICSE {\textquoteright}06},
	year = {2006},
	pages = {361{\textendash}370},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source development projects typically support an open bug repository to which both developers and users can report bugs. The reports that appear in this repository must be triaged to determine if the report is one which requires attention and if it is, which developer will be assigned the responsibility of resolving the report. Large open source developments are burdened by the rate at which new bug reports appear in the bug repository. In this paper, we present a semi-automated approach intended to ease one part of this process, the assignment of reports to a developer. Our approach applies a machine learning algorithm to the open bug repository to learn the kinds of reports each developer resolves. When a new report arrives, the classifier produced by the machine learning technique suggests a small number of developers suitable to resolve the report. With this approach, we have reached precision levels of 57\% and 64\% on the Eclipse and Firefox development projects respectively. We have also applied our approach to the gcc open source development with less positive results. We describe the conditions under which the approach is applicable and also report on the lessons we learned about applying machine learning to repositories used in open source development.},
	keywords = {bug fixing, bug report, bug report assignment, bug triage, eclipse, Firefox, gcc, issue tracking, machine learning, problem tracking},
	isbn = {1-59593-375-1},
	doi = {10.1145/1134285.1134336},
	url = {http://doi.acm.org/10.1145/1134285.1134336},
	author = {Anvik, John and Hiew, Lyndon and Murphy, Gail C.}
}
@conference {815,
	title = {Wikifying your interface:  Facilitating Community-Based Interface Translation},
	booktitle = {Proceedings of the 6th ACM conference on Designing Interactive systems  - DIS {\textquoteright}06},
	year = {2006},
	pages = {321-330},
	publisher = {ACM Press},
	organization = {ACM Press},
	abstract = {We explore the application of a wiki-based technology and
style of interaction to enabling the incremental translation
of a collaborative application into a number of different
languages, including variant English language interfaces
better suited to the needs of particular user communities.
The development work allows us to explore in more detail
the design space of functionality and interfaces relating to
tailoring, customization, personalization and localization,
and the challenges of designing to support ongoing
incremental contributions by members of different use
communities.},
	isbn = {1595933670},
	doi = {10.1145/1142405.1142453},
	author = {Jones, M.C. and Rathi, D. and Twidale, M.B}
}
@conference {Ohira:2005:ACK:1083142.1083163,
	title = {Accelerating cross-project knowledge collaboration using collaborative filtering and social networks},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {111-115},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Vast numbers of free/open source software (F/OSS) development projects use hosting sites such as Java.net and SourceForge.net. These sites provide each project with a variety of software repositories (e.g. repositories for source code sharing, bug tracking, discussions, etc.) as a media for communication and collaboration. They tend to focus on supporting rich collaboration among members in each project. However, a majority of hosted projects are relatively small projects consisting of few developers and often need more resources for solving problems. In order to support cross-project knowledge collaboration in F/OSS development, we have been developing tools to collect data of projects and developers at SourceForge, and to visualize the relationship among them using the techniques of collaborative filtering and social networks. The tools help a developer identify {\textquotedblleft}who should I ask?{\textquotedblright} and {\textquotedblleft}what can I ask?{\textquotedblright} and so on. In this paper, we report a case study of applying the tools to F/OSS projects data collected from SourceForge and how effective the tools can be used for helping cross-project knowledge collaboration.},
	keywords = {collaborative filtering, developers, knowledge collaboration, projects, social networks, sourceforge, visualization tool},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083163},
	url = {http://doi.acm.org/10.1145/1082983.1083163},
	attachments = {https://flosshub.org/sites/flosshub.org/files/111Accelerating.pdf},
	author = {Ohira, Masao and Ohsugi, Naoki and Ohoka, Tetsuya and Matsumoto, Ken-ichi}
}
@article {flosswp233,
	title = {Analysing the technological history of the Open Source Phenomenon: Stories from the Free Software Evolution},
	year = {2005},
	month = {September},
	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 paper attempts to tackle this issue by analyzing the long-term technological history of Free Open Source Software; the main research questions at stake are: is the phenomenon completely new? and if it is not totally new, where it comes form? and, more generally, how open source software developed over time? As a consequence the present work focuses primarily on the analysis of the fee/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. Thus, I attempt to investigate the origins of the phenomenon as a way of understanding its evolution.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/benussi.pdf},
	author = {Lorenzo Benussi}
}
@conference {735,
	title = {An Analysis of COSPA - A Consortium for Open Source in the Public Administration},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {125-129},
	abstract = {This paper reflects on a two-year EU funded specific research targeted project that officially began in January 2004 entitled COSPA, a Consortium for studying, evaluating and supporting the introduction of Open Source Software and Open Data Standards in the Public Administration. COSPA focuses on office automation and desktop system software and aims at rigorously measuring the effort, costs and benefits of a transition to Open Source. The project involves 15 European Universities and Public Administrations from Italy, Hungary, Ireland, Denmark, UK, Belgium and about sixty observers, including the University of Alberto (Canada), Victoria University of Wellington (New Zealand) and the United Nations Educational Scientific and Cultural Organisation (UNESCO).},
	url = {http://pascal.case.unibz.it/handle/2038/624},
	author = {Morgan, Lorraine}
}
@conference {Kim:2005:ASC:1083142.1083154,
	title = {Analysis of signature change patterns},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {1{\textendash}5},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software continually changes due to performance improvements, new requirements, bug fixes, and adaptation to a changing operational environment. Common changes include modifications to data definitions, control flow, method/function signatures, and class/file relationships. Signature changes are notable because they require changes at all sites calling the modified function, and hence as a class they have more impact than other change kinds.We performed signature change analysis over software project histories to reveal multiple properties of signature changes, including their kind, frequency, and evolution patterns. These signature properties can be used to alleviate the impact of signature changes. In this paper we introduce a taxonomy of signature change kinds to categorize observed changes. We report multiple properties of signature changes based on an analysis of eight prominent open source projects including the Apache HTTP server, GCC, and Linux 2.5 kernel.},
	keywords = {apache, gcc, kernel, linux, signature change, signature change patterns, software evolution, software evolution path, soure code},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083154},
	url = {http://doi.acm.org/10.1145/1082983.1083154},
	attachments = {https://flosshub.org/sites/flosshub.org/files/64AnalysisOfSignature.pdf},
	author = {Kim, Sunghun and Whitehead,Jr., E. James and Bevan, Jennifer}
}
@article {flosswp220,
	title = {Anarchy and Source Code - What does the Free Software Movement have to do with Anarchism?},
	year = {2005},
	month = {March},
	abstract = {What does the hacker ethic have to do with anarchism? Why does Richard Stallman, an outstanding personality of the free software movement, described himself as an anarchist? We should not imagine the anarchists of the Free Software Movement to be like the cartoon image: A scruffy looking lunatic, with a crazy glint in his eyes and bristling with weapons. Instead of chaos, Stallman postulates a new form of order for the intellectual property in the terms of the hacker ethic - the access to knowledge should be free, decentralized, anti-bureaucratic and anti-authoritarian.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/imhorst.pdf},
	author = {Christian Imhorst}
}
@article {1079,
	title = {Are All Open Source Projects Created Equal? Understanding the Sustainability of Open Source Software Development Model},
	journal = {AMCIS 2005 Proceedings},
	number = {435},
	year = {2005},
	note = {uses first 300 most active projects on Sourceforge: {\textquoteright}Our data sample consists of 300 open source software development projects hosted in the Sourceforge.Net. They are the first 300 active projects ranked by Sourceforge.Net....Our dependent variable in the model to measure the success of the projects is the number of downloads. It is an essential variable to show how successful the project is. Generally, more number of downloads means a more successful project. Independent variables include: development status, project lifespan, number of developers, number of messages in the forums, number of mailing list, number of bug report, number of patch report, number of CVS report, number of file releases and also number of news release."},
	abstract = {A very intriguing question in Open Source software (OSS) development is: why there are only a few open source projects succeed, while the majority of projects never do. In this research, we examine the factors that may influence the performance of OSS projects. We particularly focus on the OSS{\textquoteright}s core developers{\textquoteright} role in the project{\textquoteright}s success. Extant research has yet to distinguish core developers and non-core developers from the community at large. The different roles of the core developers and non-core developers in OSS projects{\textquoteright} success still remain unclear. Our research contributes to the literature by separating the core developers from the development forces in general and empirically examining the core developers{\textquoteright} importance. Drawing the evidences from our extensive dataset of 300 open source projects, we demonstrated that core developers{\textquoteright} leadership and project advocation are crucial in determining the fate of the OSS projects. Our research could provide better understanding of OSS sustainability. It could also give practical advice to the OSS community on how to make the project successful.},
	keywords = {contributors, core, developers, downloads, metadata, project success, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LongYuan.pdf},
	author = {Long, J. and Yuan, M.J.}
}
@conference {728,
	title = {Assessing the Role of Open Source Software in the European Secondary Software Sector: A Voice from Industry},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {82-87},
	abstract = {This paper addresses the open source software (OSS) phenomenon from an industry perspective and reveals a number of complexities surrounding the role of OSS in the secondary software sector. It presents the research results of an international workshop which was hosted with the explicit intention of extracting the voice of key industrial stakeholders. The data was gathered and analysed using a qualitative approach which revealed the key strengths and weaknesses of OSS from an industrial perspective. This formed the foundations for developing a framework describing the emerging commercial incarnation of OSS (we refer to this as Open Source Software, Inc.) The paper concludes that the European secondary software sector recognise the benefits of leveraging OSS but are aware of key issues pertinent to such an end.},
	url = {http://pascal.case.unibz.it/handle/2038/752},
	author = {{\r A}gerfalk, P{\"a}r J and Deverell, Andrea and Fitzgerald, Brian and Morgan, Lorraine}
}
@article {51,
	title = {Brazil adopts open-source software},
	volume = {2008},
	number = {5 December},
	year = {2005},
	month = {2 June, 2005},
	publisher = {BBC News},
	address = {Sao Paulo},
	url = {http://news.bbc.co.uk/2/hi/business/4602325.stm},
	author = {Kingstone, Steve}
}
@conference {752,
	title = {The calm before the storm? Legal challenges to open source licences},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {215-219},
	abstract = {This paper will concentrate on presenting a legal
analysis of two of the main challenges to open source
software: SCO{\textquoteright}s litigation and software patents. The paper
discusses the validity of such challenges, their possible impact
to the future of open source software, and the possible legal
defences used against them.},
	author = {Gonzalez,  Andres Guadamuz}
}
@conference {779,
	title = {Carrot2 Clustering Framework},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {298-299},
	abstract = {Carrot2 is an Open Source framework for research experiments with querying various textual data sources, processing and presentation of the results. Its main goal is to promote component reuse in order to reduce the effort involved in the development of Information Retrieval software. So far, the most successful and popular application of Carrot2 has been organizing results of Internet searches into easy to browse thematic groups called clusters. In this area, the project successfully competes with commercial counterparts like Vivisimo or iBoogie.},
	keywords = {BSD license, cluster, clustering framework, open source, research, result},
	url = {http://pascal.case.unibz.it/handle/2038/788},
	author = {Weiss, Dawid and Osi{\textasciiacute}nski, Stanis{\l}aw}
}
@conference {795,
	title = {The challenges of creating open source education software: the Gild experience},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {338-340},
	keywords = {COMMUNITY, eclipse, learning environment, novice programmers, open source, programming environment},
	url = {http://pascal.case.unibz.it/handle/2038/1539},
	author = {Daniel M. German and Rigby, Peter and Cubranic, Davor and Storey, Margaret-Anne and Thomson, Suzanne}
}
@conference {722,
	title = {A Cluster Analysis of Open Source Licenses},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {50-53},
	abstract = {Licenses of open source software (OSS) are quiet various but is said to be categorised into three. That is GPL (GNU general Public License) like, LGPL (GNU Lesser general Public License) like, or MPL (Mozilla Public License) like. We check this classification by using our new framework and cluster analysis. And we find another three categories for OSS Licenses.},
	url = {http://pascal.case.unibz.it/handle/2038/618}
}
@conference {78,
	title = {Collaboration Using OSSmole: A repository of FLOSS data and analyses},
	booktitle = {Symposium on Mining Software Repositories},
	year = {2005},
	month = {17 May},
	address = {St. Louis},
	author = {Conklin, Megan and James Howison and Kevin Crowston}
}
@conference {729,
	title = {Communication, coordination and control in distributed development: an OSS case study},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {88-92},
	abstract = {It has been claimed that distributed development practices in OSS development may be a model for enterprise development practices of the future. With this in mind, we have conducted a study of one OSS project, namely ArgoUML, with a view to understanding development practice within the project, and specifically to considering possible differences from traditional (non-OSS) distributed development conducted in a commercial project. We do this by explicitly considering issues of communication, coordination and control. Our findings suggest that primary differences lie in control and resulting project structures, motivated through differing goals. We comment on the open question of how the advantages of one development context can be realised in the other.},
	url = {http://pascal.case.unibz.it/handle/2038/769},
	author = {Persson, Anna and Lings, Brian and Lundell, Bj{\"o}rn and Mattsson, Anders and {\"A}rlig, Ulf}
}
@conference {743,
	title = {Communication from scratch: towards accessible open source information systems},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {179-186},
	abstract = {This paper is intended to provide an overview of a unifying and inclusive approach to open source information systems. In this respect the paper matches the fundamental aims of the Open Source Systems (2005) Conference. This approach can be characterised as communication from scratch. Firstly, we will provide an explanation of our approach to inclusive design and consider emerging perspectives on the nature of accessibility in the wider sense. Secondly, we will introduce the concept of communication from scratch and provide an explanation of the benefits of a convergent gradualism. Thirdly we will explain how these ideas have helped to shape our understanding of open source information processing, a concept which encompasses several of the conference themes and provides a unifying interface to our earlier work on accessible system design. Lastly, we will provide some concrete examples of the communication from scratch approach (crossing several domains) and introduce, ...},
	url = {http://pascal.case.unibz.it/handle/2038/759},
	author = {Crombie, David and Lenoir, Roger and McKenzie, Neil}
}
@article {10.1109/TSE.2005.89,
	title = {Comparing High-Change Modules and Modules with the Highest Measurement Values in Two Large-Scale Open-Source Products},
	journal = {IEEE Transactions on Software Engineering},
	volume = {31},
	year = {2005},
	pages = {625-642},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {Identifying change-prone modules can enable software developers to take focused preventive actions that can reduce maintenance costs and improve quality. Some researchers observed a correlation between change proneness and structural measures, such as size, coupling, cohesion, and inheritance measures. However, the modules with the highest measurement values were not found to be the most troublesome modules by some of our colleagues in industry, which was confirmed by our previous study of six large-scale industrial products. To obtain additional evidence, we identified and compared high-change modules and modules with the highest measurement values in two large-scale open-source products, Mozilla and OpenOffice, and we characterized the relationship between them. Contrary to common intuition, we found through formal hypothesis testing that the top modules in change-count rankings and the modules with the highest measurement values were different. In addition, we observed that high-change modules had fairly high places in measurement rankings, but not the highest places. The accumulated findings from these two open-source products, together with our previous similar findings for six closed-source products, should provide practitioners with additional guidance in identifying the change-prone modules.},
	keywords = {mozilla, openoffice},
	issn = {0098-5589},
	doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.2005.89},
	author = {G{\"u}nes Koru, A. and Tian, Jeff (Jianhui)}
}
@conference {746,
	title = {Competition between Open Source and Proprietary Software, and the Scope for Public Policy},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {196-199},
	abstract = {Open source software (OSS) has become a remarkable competitor of traditional, proprietary software in many markets. This has led advocates of OSS to demand public policy interventions in favor of OSS. The main argument is that OSS mitigates market failures associated with typical features of software markets: economies of scale, direct network effects, switching costs, and systems competition. We study the impact of several policy instruments on social welfare in a duopoly model which incorporates all of the aforementioned features of software markets. Overall, we do not find much support for interventions in favor of OSS. However, systems competition may lead to a situation in which the subsidization of OSS complements increases welfare.},
	url = {http://pascal.case.unibz.it/handle/2038/758},
	author = {Gutsche, Joerg}
}
@inbook {900,
	title = {A Conceptual Model for Enterprise Adoption of Open Source Software},
	booktitle = {The Standards Edge: Open Season},
	year = {2005},
	pages = {51-62},
	publisher = {Sheridan Books},
	organization = {Sheridan Books},
	address = {Ann Arbor, Mich.},
	author = {Kwan, Stephen K. and Joel West},
	editor = {Bolin, Sherrie}
}
@proceedings {89,
	title = {Coordination of Free/Libre Open Source Software development},
	year = {2005},
	note = {"The data used for the study were interactions on the main developer communication venue, either a developer mailing list or online forum"
sourceforge
},
	address = {Las Vegas, NV, USA},
	abstract = {The apparent success of free/libre open source software (FLOSS) development projects such as Linux, Apache, and many others has raised the question, what lessons from FLOSS development can be transferred to mainstream software development? In this paper, we use coordination theory to analyze coordination mechanisms in FLOSS development and compare our analysis with existing literature on coordination in proprietary software development. We examined developer interaction data from three active and successful FLOSS projects and used content analysis to identify the coordination mechanisms used by the participants. We found that there were similarities between the FLOSS groups and the reported practices of the proprietary project in the coordination mechanisms used to manage task-task dependencies. However, we found clear differences in the coordination mechanisms used to manage task-actor dependencies. While published descriptions of proprietary software development involved an elaborate system to locate the developer who owned the relevant piece of code, we found that {\textquotedblleft}self-assignment{\textquotedblright} was the most common mechanism across three FLOSS projects. This coordination mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research.},
	keywords = {case study, compiere, coordination, egroupware, email, email archives, FLOSS, gaim, mailing list},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonWeiLiEseryelHowison.pdf},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and Eseryel, U. Yeliz and Howison, James}
}
@article {flosswp215,
	title = {Coordination Processes in Open Source Software Development: The Linux Case Study},
	year = {2005},
	month = {April},
	abstract = {Although open source projects have been subject to extensive study, their coordination processes are still poorly understood. Drawing on organization theory, this paper sets out to remedy this imbalance by showing that large-scale open source projects exhibit three main coordination mechanisms, namely standardization, loose coupling and partisan mutual adjustment. Implications in terms of electronically-mediated communications and networked interdependencies are discussed in the final sections where a new light is cast on the concept of structuring as a by-product of localized adjustments.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/iannacci3.pdf},
	author = {Federico Iannaci}
}
@conference {761,
	title = {Criteria for the non invasive transition to OpenOffice},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {250-253},
	abstract = {Open Source Software (OSS) is receiving an increasing attention as a possible alternative to proprietary solutions. There are supporters of both the alternatives that stress advantages and disadvantages, but what is missing is an empirical view of a transition with the aid of case studies and controlled experiments. The aim of the paper is to report the results of an empirical investigation in the field of office automation in the Public Administration (PA). The available OSS in the field is introduced in the existing environment while preserving the proprietary solution. The analysis is supported by both qualitative and quantitative data. The effects on productivity and on users{\textquoteright} attitude towards OSS and the emerging criteria for a possible transition are exposed.},
	url = {http://pascal.case.unibz.it/handle/2038/789},
	author = {Rossi, Bruno and Scotto, Marco and Sillitti, Alberto and Succi, Giancarlo}
}
@conference {751,
	title = {Defining a Distributed Agile Methodology for an Open Source Scenario},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {209-214},
	abstract = {In this paper we propose and describe an agile methodology for distributed development (MADD - Methodology for Agile Distributed Development). In particular, it{\textquoteright}s illustrated a set of best practices to apply in a distributed and agile context, chosen on the base of their impact software quality and team interoperation. Beyond the proposed methodology, we show the results of a survey that we submitted to various contributors of Open Source projects. The survey has been of support to the definition of the MADD, helping to more understand and estimate if, how and how much agile practices and values are already present in the OS world, that today represents one of the most emblematic examples of distributed development. The MADD methodology will be adopted on a software development project at the University of Cagliari (Italy), by a group of students that will work like an Open Source community.},
	url = {http://pascal.case.unibz.it/handle/2038/766},
	author = {Angioni, Manuela and Sanna, Raffaella and Soro, Alessandro}
}
@conference {732,
	title = {Defining the Total Cost of Ownership for the Transition to Open Source Systems},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {108-112},
	abstract = {This paper provides a a framework to evaluate the transition to a OSS software solution in terms of returns and losses in the context of Public Administrations. The ultimate goal of the framework is to identify costs that are not easy to trace or that are not usually collected like user acceptance. The framework has been conducted using a Total Cost of Ownership approach, which is the most frequently used model to conduct cost comparisons between two or more IT systems. The study further implements the Goal Question Metric paradigm to identify the cost metrics. The framework relies various methods to collect the data, including questionnaires with end-users, qualitative interviews with IT-managers and company balance sheets. An example of framework{\textquoteright}s use is provided.},
	url = {http://pascal.case.unibz.it/handle/2038/774},
	author = {Russo, Barbara and Braghin, Chiara and Gasperi, Paolo and Sillitti, Alberto and Succi, Giancarlo}
}
@book {flosswp210,
	title = {Democratizing Innovation},
	year = {2005},
	month = {April},
	publisher = {MIT Press},
	organization = {MIT Press},
	abstract = {Innovation is rapidly becoming democratized. Users, aided by improvements in computer and communications technology, increasingly can develop their own new products and services. These innovating users{\textendash}both individuals and firms{\textendash}often freely share their innovations with others, creating user-innovation communities and a rich intellectual commons. In Democratizing Innovation, Eric von Hippel looks closely at this emerging user-centered innovation system. He explains why and when users find it profitable to develop new products and services for themselves, and why it often pays users to reveal their innovations freely for the use of all. The trend toward democratized innovation can be seen in software and information products{\textendash}most notably in the free and open-source software movement{\textendash}but also in physical products. He shows that product and service development is concentrated among "lead users," who are ahead on marketplace trends and whose innovations are often commercially attractive. Von Hippel argues that manufacturers should redesign their innovation processes and systematically seek out innovations developed by users. User innovation has a positive impact on social welfare, and von Hippel proposes that government policies, including R\&D subsidies and tax credits, should be realigned to eliminate biases against it. An electronic version of this book is available under a Creative Commons license.},
	author = {von Hippel, Eric}
}
@conference {Robles:2005:DIM:1083142.1083162,
	title = {Developer identification methods for integrated data from various sources},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {106-110},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Studying a software project by mining data from a single repository has been a very active research field in software engineering during the last years. However, few efforts have been devoted to perform studies by integrating data from various repositories, with different kinds of information, which would, for instance, track the different activities of developers. One of the main problems of these multi-repository studies is the different identities that developers use when they interact with different tools in different contexts. This makes them appear as different entities when data is mined from different repositories (and in some cases, even from a single one). In this paper we propose an approach, based on the application of heuristics, to identify the many identities of developers in such cases, and a data structure for allowing both the anonymized distribution of information, and the tracking of identities for verification purposes. The methodology will be presented in general, and applied to the GNOME project as a case example. Privacy issues and partial merging with new data sources will also be considered and discussed.},
	keywords = {anonymization, bug tracker, developers, email, email address, gnome, identity, mailing list, privacy, source code, version control},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083162},
	url = {http://doi.acm.org/10.1145/1082983.1083162},
	attachments = {https://flosshub.org/sites/flosshub.org/files/106DeveloperIdentification.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@proceedings {citeulike:3052508,
	title = {Development Success in Open Source Software Projects: Exploring the Impact of Copylefted Licenses},
	year = {2005},
	abstract = {Copyleft prevents the source code of open source software (OSS) from being privately appropriated. The ethos of the OSS movement suggests that volunteer developers may particularly value and contribute to copylefted projects. Based on social movement theory, we hypothesized that copylefted OSS projects are more likely than non-copylefted OSS projects to succeed in the development process, in terms of two key indicators: developer membership and developer productivity. We performed an exploratory study using data from 62 relevant OSS projects spanning an average of three years of development time. We found that copylefted projects were associated with higher developer membership and productivity. This is the first study to empirically test the relationship between copylefted licenses and OSS project success. Implications for OSS project initiators as well as future research directions are discussed.},
	keywords = {contributions, copyleft, developer, developers, membership, productivity, project success, success},
	url = {http://aisel.isworld.org/password.asp?Vpath=AMCIS/2005\&\#38;PDFpath=OSSDAU01-1167.pdf},
	author = {Colazo, Jorge A. and Fang, Yulin and Neufeld, Derrick J.}
}
@conference {796,
	title = {Development-oriented Open Source eLearning Tool Evaluation: the Edukalibre Approach},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {341-344},
	author = {Botturi, Luca and Chris Tebb and Vania Dimitrova and Drew Withworth and Julika Matravers and Jutta Geldermann and Isabelle Hubert}
}
@proceedings {1517,
	title = {Digesting Virtual {\textquotedblleft}Geek{\textquotedblright} Culture: The Summarization of Technical Internet Relay Chats},
	year = {2005},
	month = {06/2005},
	pages = {298-305},
	address = {Ann Arbor, MI, USA},
	abstract = {This paper describes a summarization system for technical chats and emails on the Linux kernel. To reflect the complexity and sophistication of the discussions, they are clustered according to subtopic structure on the sub-message level, and immediate responding pairs are identified through machine learning methods. A resulting summary consists of one or more mini-summaries, each on a subtopic from the discussion.},
	keywords = {computational linguistics, irc, linux, summarizing},
	url = {http://acl.ldc.upenn.edu/P/P05/P05-1037.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/P05-1037.pdf},
	author = {Liang Zhou and Edouard Hovy}
}
@conference {753,
	title = {Distributed Software Platforms for Rehabilitating Obsolete Hardware},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {220-223},
	abstract = {The diffusion of ICTs created the issue of a huge quantity of old computers to be discarded (E-waste). Sustainable dismantle is becoming a global enviromental emergency. Trashware movement is spreading worldwide, aiming to profitably reuse discarded computers as an alternative to dismantling them. Trashware is deeply related to the Open Source and Free Software movements. The aim of this piece of research is to combine Trashware to clustering, in order to verify if further optimisations are possible. Experiments were conducted on clusters of old machines and results are hereby presented.},
	url = {http://pascal.case.unibz.it/handle/2038/782},
	author = {Russo, Ruggero and Lamanna, Davide and Baldoni, Roberto}
}
@conference {780,
	title = {Doctoral Symposium at OSS 2005},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {300},
	author = {Russo, Barbara}
}
@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}
}
@conference {773,
	title = {Fare Open Source all{\textquoteright}Istat: il generatore di data-entry per indagini statistiche},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {283-286},
	abstract = {Viene presentata una prima esperienza di sviluppo di software Open Source all{\textquoteright}Istat, che riguarda un sistema generalizzato di data-entry per indagini statistiche. L{\textquoteright}applicazione, in via di rilascio, copre la fase di acquisizione dati propria delle indagini statistiche e consentir{\`a} di generare maschere che potranno essere utilizzate sia in Intranet che sul Web. L{\textquoteright}applicazione descritta, che utilizza PHP e XML come tecnologie fondanti, rappresenta un{\textquoteright}esperienza concreta di sviluppo Open Source nella quale l{\textquoteright}Istat vuole riversare le proprie esperienze specifiche, mettendole poi a disposizione delle altre strutture interessate.},
	keywords = {data-entry, indagini statistiche, open source, PHP, web, XML},
	url = {http://pascal.case.unibz.it/handle/2038/903},
	author = {Altarocca, Francesco and Vaccari, Carlo}
}
@article {99,
	title = {A framework for analyzing levels of analysis issues in studies of e-collaboration},
	journal = {Ieee Transactions on Professional Communication},
	volume = {48},
	number = {1},
	year = {2005},
	note = {Times Cited: 3},
	pages = {87-104},
	abstract = {There has been a proliferation of competing explanations regarding the inconsistent results reported by the e-collaboration literature since its inception. This study advances another possible explanation by investigating the range of multilevel issues that can be encountered in research on the use of synchronous or asynchronous group support systems. We introduce concepts of levels of analysis from the management literature and then examine all empirical studies of e-collaboration from seven information systems journals for the period 1999-2003. We identified a total of 54 studies of e-collaboration in these journals, and after excluding 18 nonconforming studies-those that were primarily conceptual, qualitative, or exploratory only-we analyzed the levels of analysis issues in the remaining 36 empirical studies. Based on our analysis and classification of these studies into six different clusters according to their levels of analysis, we found that a majority of these studies contain one or more problems of levels incongruence that cast doubts on the validity of their results. It is indeed possible that these methodological problems are in part responsible for the inconsistent results reported in this literature, especially since researchers frequent decisions to analyze data at the individual level-even when the theory was formulated at the group level and when the research setting featured individuals working in groups-may very well have artificially inflated the authors{\textquoteright} chances of finding statistically significant results. Based on our discussion of levels of analysis concepts, we hope to provide guidance to empirical researchers who study e-collaboration.},
	author = {Gallivan, M. J. and Benbunan-Fich, R.}
}
@booklet {489,
	title = {Framework for Governance in Open Source Projects},
	year = {2005},
	month = {Jan},
	abstract = {In recent years, the development of software in open source communities has attracted immense attention from research and practice. The idea of commercial quality, free software, and open source code accelerated the development of well-designed open source software such as Linux, Apache tools, or Perl.Intrinsic motivation, group identification processes, learning, and career concerns are the key drivers for a successful cooperation among the participants. These factors and most mechanisms of control, coordination, and monitoring forms of open source communities can hardly be explained by traditional organizational theories. In particular, the micro and macro structures of open source communities and their mode of operation are hardly compatible with the central assumption of the New Institutional Theory, like opportunistic behavior.The aim of this contribution is to identify factors that sustain the motivation of the community members over the entire life cycle of an open source project. Adequate coordination and controlling mechanisms for the governance in open source communities may be extracted.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Governance-in-OpenSourceProjects.pdf},
	author = {Christoph Lattemann and Stefan Stieglitz}
}
@article {flosswp209,
	title = {Free software and open source: The freedom debate and its consequences (Published in First Monday)},
	year = {2005},
	month = {March},
	abstract = {To most outsiders the ethics of software is not something usually considered. To most proficient computer users with a passing interest in this question the ethics of software is recognised as one of the fundamental questions in the digital rights area. To most of the latter, terms such as free software, open source, and their derivatives (FLOSS, FOSS, Software Freedom) are interchangeable. Choosing one over the other is a matter of taste rather than politics. However, to most insiders the question is not one of taste. There is a fundamental difference between the two areas even if they share a similar root. Free software is not the same as open source. The two groups differ in their fundamental philosophical approach to software and its importance to society as a whole. This paper examines the two groups? differing philosophies and explores how their actions have affected software development, access to fundamental software infrastructure, and the development of the concept of freedom.},
	author = {Mathias Klang}
}
@conference {768,
	title = {Free software and research},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {270-271},
	abstract = {Free software licenses are a natural choice in a research environment. In the following, we will try to back this simple statement with some considerations and examples, in an effort to analyse the significant interactions between free software and research.},
	url = {http://pascal.case.unibz.it/handle/2038/864},
	author = {Potort{\`\i}, Francesco}
}
@article {flosswp182,
	title = {Free software development communities as a pedagogic model},
	journal = {Condividere la conoscenza. L{\textquoteright}esempio del software libero},
	year = {2005},
	month = {November},
	publisher = {Unicopli},
	abstract = {The pedagogic interest arising from the emergence of free software development communities is twofold. Firstly, in their production practices these communities set out formative processes as well as educational ones. These practices characterise these communities and are not accessory, to the point that without them the communities could not survive. Secondly, these communities are interesting as they make up a particularly rich epistemological model for the understanding of formative, educational and didactical themes. Having embraced the hacker culture, these communities promote and create an incentive to the free circulation of knowledge without protectionist barriers. However, freedom of knowledge alone is not enough, both in the educational and productive fields, unless it is introduced in an organisational model promoting the participation and engagement of the individuals. The communities of free software development are a particularly interesting organisational model because their structure, based on co-operation and solidarity and opposing centralisation, promote the participation of programmers and users all over the world. Thanks to this kind of organisation, which owes much to a model of delegating leadership, authoritative but not authoritarian, charismatic but not idealised these communities are putting together a very large number of work groups. These are geographically, methodologically and culturally non-homogeneous groups, which despite all predictions create highly competitive products of high quality.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/antonacci.pdf},
	author = {Francesca Antonacci}
}
@article {DBLP:journals/tse/Dinh-TrongB05,
	title = {The FreeBSD Project: A Replication Case Study of Open Source Development},
	journal = {IEEE Trans. Software Eng.},
	volume = {31},
	number = {6},
	year = {2005},
	note = {" we obtained the necessary data from the [FreeBsd] CVS repository, the bug report database, and the e-mail archive. The CVS repository contains all of the code and related documentation that is committed to the project from 1993 until the present. The bug report database contains information describing all reported problems, as well as the status (such as fixed, under test, or open) of each problem. Each bug report is called a PR and assigned a reference number. The e-mail archive contains every e-mail message exchanged between the developers since 1994."

d/l: research.cs.queensu.ca/~ahmed/home/teaching/.../F06/.../free-bsd.pdf},
	pages = {481-494},
	abstract = {Case studies can help to validate claims that open source software development produces higher quality software at lower cost than traditional commercial development. One problem inherent in case studies is external validity{\textemdash}we do not know whether or not results from one case study apply to another development project. We gain or lose confidence in case study results when similar case studies are conducted on other projects. This case study of the FreeBSD project, a long-lived open source project, provides further understanding of open source development. The paper details a method for mining repositories and querying project participants to retrieve key process information. The FreeBSD development process is fairly well-defined with proscribed methods for determining developer responsibilities, dealing with enhancements and defects, and managing releases. Compared to the Apache project, FreeBSD uses 1) a smaller set of core developers{\textemdash}developers who control the code base{\textemdash}that implement a smaller percentage of the system, 2) a larger set of top developers to implement 80 percent of the system, and 3) a more well-defined testing process. FreeBSD and Apache have a similar ratio of core developers to people involved in adapting and debugging the system and people who report problems. Both systems have similar defect densities and the developers are also users in both systems.},
	keywords = {apache, bug reports, contributors, core, cvs, defect density, developers, email, email archive, freebsd, mailing list, scm, source code, users},
	doi = {10.1109/TSE.2005.73},
	attachments = {https://flosshub.org/sites/flosshub.org/files/DinhTrungBieman.pdf},
	author = {Trung T. Dinh-Trong and James M. Bieman}
}
@article {flosswp227,
	title = {From Planning to Mature: on the Determinants of Open Source Take Off},
	year = {2005},
	month = {July},
	abstract = {In this paper we use data from SourceForge.net, the largest open source projects repository, to estimate the main determinants of the progress in the development of a stable and mature code of a software. We find that the less restrictive the licensing terms the larger the likelihood of reaching an advanced development status and that this effect is even stronger for newer projects. We also find that projects geared towards system administrators appear to be the more successful ones. The determinants of projects{\textquoteright} development stage change with the age of the project in many dimensions, i.e. licensing terms, software audience and contents, thus supporting the common perception of opens source as a very dynamic phenomenon. The data seem to suggest that open source is evolving towards more commercial applications.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Comino_Manenti_Parisi.pdf},
	author = {Stefano Comino}
}
@article {73,
	title = {From research prototypes to industrial strength open source products - The ObjectWeb experience},
	journal = {Sofsem 2005:Theory and Practice of Computer Science},
	volume = {3381},
	year = {2005},
	note = {Times Cited: 0},
	pages = {17-27},
	abstract = {Open source software has become a common way of disseminating research results. In this talk, we first introduce the motivations and implications of releasing research prototypes as open source software (OSS). ObjectWeb is an international consortium fostering the development of open source middleware. We give an overview of tools available for OSS development and management based on ObjectWeb. experiences. The infrastructure required for hosting such developments is also described; We report various, experiences and practices of small and large ObjectWeb projects in their way to reach the quality of industrial strength products. Finally, we summarize the lessons learned from the success and failures of these projects.},
	author = {Cecchet, E.}
}
@article {flosswp226,
	title = {Fun and Software Development},
	year = {2005},
	month = {July},
	abstract = {This study gathered 1330 answers about fun and software development from open source developers as well as 114 answers from programmers working in commercial software projects. The analysis of these data proves that fun plays an important role when software developers decide to get engaged in an open source project. Moreover, the comparison of the answers gives evidence for the hypothesis that programming in an open source project is significantly more fun compared to the same activity under commercial conditions. The reasons for this fact are that open source projects are able to attract software developers with a credible project vision and that they can offer them an optimal challenge.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/BLuthiger_Fun_SoftwareDevel_OSS2005.pdf},
	author = {Benno Luthiger Stoll}
}
@conference {786,
	title = {Future Development in the European Software Industry: Patentability of Computer Programs or Open Source Software?},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {311-313},
	abstract = {Economic literature has treated the patent system as an indispensable tool to incentive inventive activity and to foster diffusion of technological improvements, but recent developments have brought at the center of the stage the Open Source phenomenon which is based on completely different mechanisms among which the free disclosure of the inventive steps. This work analyzes changes that are taking place into patent literature in order to give account of the desirability of patents in software sector. In addition some ideas on empirical analysis are put forward: the possibility of measuring the relationship between patents and input of innovation process in the software sector and the influence that private firms will have on Open Source developers motivations.},
	keywords = {european, market segment, open source, os, patent, patent literature, patentability, software industry, software sector},
	url = {http://hdl.handle.net/2038/966},
	author = {Rentocchini, Francesco}
}
@inbook {flosswp207,
	title = {The Future of Open Source. In: Wynants, M. \& J. Cornelis (eds.) How Open is the Future? VUB Brussels University Press, pp. 429-59.},
	year = {2005},
	month = {April},
	abstract = {Open source has seen phenomenal growth in recent years. In many ways, it has been a great success story. Yet it is interesting to study the conditions that would enable the open-source movement to remain viable and thrive also in the future. This chapter explores the driving forces behind the open source model and its constraints, discussing both the factors likely to promote the continuous growth of the open-source movement and those that could lead to its downfall.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/tuomi3_bookchapter.pdf},
	author = {Ilkka Tuomi}
}
@conference {756,
	title = {The future of software as a business artefact},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {231-236},
	abstract = {Rather than look to migration guides for business, or to barriers to adoption of Open Source Software, perhaps we should look to understand what it is that organisations need from their software, it is not just the feature set of the application, but a combination and compromise of the business benefits and business risks, some of which are not inherent in the software feature set, but are interrelated to the needs and pre-existing conditions of the organisation. This paper looks to investigate these aspects of Software to an organisation and to then investigate if Open Source Software can fulfil these factors.},
	url = {http://pascal.case.unibz.it/handle/2038/1540},
	author = {Skidmore, Darren}
}
@article {49,
	title = {Geeks, Social Imaginaries, and Recursive Publics},
	journal = {Cultural Anthropology},
	volume = {20},
	number = {2},
	year = {2005},
	pages = {185-214},
	publisher = {Blackwell Publishing on behalf of the American Anthropological Association},
	abstract = {This article investigates the social, technical, and legal affiliations among "geeks" (hackers, lawyers, activists, and IT entrepreneurs) on the Internet. The mode of association specific to this group is that of a "recursive public sphere" constituted by a shared imaginary of the technical and legal conditions of possibility for their own association. On the basis of fieldwork conducted in the United States, Europe, and India, I argue that geeks imagine their social existence and relations as much through technical practices (hacking, networking, and code writing) as through discursive argument (rights, identities, and relations). In addition, they consider a "right to tinker" a form of free speech that takes the form of creating, implementing, modifying, or using specific kinds of software (especially Free Software) rather than verbal discourse.},
	isbn = {08867356},
	url = {http://www.jstor.org/stable/3651533},
	author = {Christoper Kelty}
}
@article {flosswp208,
	title = {Gender issues in the FLOSS development},
	year = {2005},
	month = {March},
	abstract = {The FLOSS development is responding to the ICT development in various ways. This essay describes and analyses challenges (societal and organisational) and advantages (e.g. new models for mobile and collaborative work online), particularly regarding gender issues, encountered in the recent FLOSS development. The focus of the essay is not only on the claims made women in the existed FLOSS community about the tensions between male and female developers{\textquoteright} interests and ways of doings, but also on the current obstacles against bringing more women, who are not technically competent, to participate in the FLOSS development. This paper concludes with suggestions on how to create rules and resources and the creation of a common FLOSS space for both genders.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin3_gender.pdf},
	author = {Yu-wei Lin}
}
@article {flosswp228,
	title = {The Hacker Ethic and Meaningful Work},
	year = {2005},
	month = {August},
	abstract = {This paper begins with the following proposition: given that we spend a large proportion of our time working, a just society will provide or encourage meaningful work. Hackers have created and broadened spaces where working life can unfold freely, so a proper analysis of the Hacker Ethic ought to be of concern both to philosophers interested in meaningful work, and to academics researching hackers and the free software community. I proceed by first developing an understanding of the Hacker Ethic that highlights a central concern of my essay, that of orientations that I characterise as self-indulgent and social placing conflicting obligations upon individuals. Using Marx{\textquoteright}s conception of alienated as a basis, I go on to show how the Hacker Ethic can to an extent overcome these conflicts by developing a more rounded understanding of the ethic. Finally I raise some concerns for the underdeveloped field of the philosophy of hacking and free software that are particularly pertinent to the paper.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/chance.pdf},
	author = {Tom Chance}
}
@article {vanWendeldeJoode2005109,
	title = {Handling variety: the tension between adaptability and interoperability of open source software},
	journal = {Computer Standards \& Interfaces},
	volume = {28},
	number = {1},
	year = {2005},
	note = {unable to find concise description of the data used [ms]},
	pages = {109 - 121},
	abstract = {Open source software (OSS) offers unprecedented opportunities to create variety. This could lead to incompatibility and fragmentation. To prevent this some form of coordination is needed. This paper explores which mechanisms of coordination are responsible for limiting divergence in OSS. Two cases are examined: Java and Linux. A systematic difference seems to exist between the mechanisms identified in the two communities. With respect to Java, divergence is where possible avoided ex ante, whereas for Linux divergence is foremost reduced ex post. The conclusion discusses this difference and the implications of both types of coordination in respect to interoperability.},
	keywords = {coordination, divergence, java, linux},
	issn = {0920-5489},
	doi = {DOI: 10.1016/j.csi.2004.12.004},
	url = {http://www.sciencedirect.com/science/article/B6TYV-4F6K72H-1/2/c74c64ce51e6f46abf9f39ae945c9e15},
	author = {Ruben van Wendel de Joode and Tineke M. Egyedi}
}
@article {1393,
	title = {Hipikat: a project memory for software development},
	journal = {IEEE Transactions on Software Engineering},
	volume = {31},
	year = {2005},
	month = {06/2005},
	pages = {446 - 465},
	abstract = {Sociological and technical difficulties, such as a lack of informal encounters, can make it difficult for new members of noncollocated software development teams to learn from their more experienced colleagues. To address this situation, we have developed a tool, named Hipikat, that provides developers with efficient and effective access to the group memory for a software development project that is implicitly formed by all of the artifacts produced during the development. This project memory is built automatically with little or no change to existing work practices. After describing the Hipikat tool, we present two studies investigating Hipikat{\textquoteright}s usefulness in software modification tasks. One study evaluated the usefulness of Hipikat{\textquoteright}s recommendations on a sample of 20 modification tasks performed on the Eclipse Java IDE during the development of release 2.1 of the Eclipse software. We describe the study, present quantitative measures of Hipikat{\textquoteright}s performance, and describe in detail three cases that illustrate a range of issues that we have identified in the results. In the other study, we evaluated whether software developers who are new to a project can benefit from the artifacts that Hipikat recommends from the project memory. We describe the study, present qualitative observations, and suggest implications of using project memory as a learning aid for project newcomers.},
	issn = {0098-5589},
	doi = {10.1109/TSE.2005.71},
	author = {Cubranic, D. and Murphy, G. C. and Singer, J. and Booth, K.S.}
}
@article {flosswp236,
	title = {How open is the future (Book - Under creative Commons},
	year = {2005},
	month = {September},
	abstract = {There are two reasons why the free and open-source software issue has become such an inspirational and powerful force today: the rise of the Internet and the growing tendency to protect all intellectual property. Internet technology made it possible to handle massive decentralized projects and irreversibly changed our personal communication and information research. Intellectual property, on the other hand, is a legal instrument which - due to recent excesses - became the symbol of exactly the opposite of what it had been developed for: the protection of the creative process. As a result, free-thinking programmers, scientists, artists, designers, engineers and scholars are daily trying to come up with new ways of creating and sharing knowledge.},
	author = {Marleen Wynants}
}
@conference {903,
	title = {How Oversight Improves Member-Maintained Communities},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2005},
	publisher = {ACM},
	organization = {ACM},
	address = {Portland OR},
	author = {Cosley, D. and D. Frankowski and S. Kiesler and Terveen, L. and Riedl, J.}
}
@conference {904,
	title = {How Peer Photos Influence Member Participation in Online Communities},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2005},
	publisher = {ACM},
	organization = {ACM},
	address = {Portland, OR},
	author = {Kapoor, N. and Konstan, J.A. and Terveen, L. G.}
}
@proceedings {117,
	title = {A human capital perspective of organizational intention to adopt open source software},
	year = {2005},
	keywords = {Survey},
	author = {Yan Li and Chuan-Hoo Tan and Hock-Hai Teo and Alex Siow}
}
@article {flosswp211,
	title = {Hybrid Innovation - How Does the Collaboration Between the FLOSS Community and Corporations Happen?},
	year = {2005},
	month = {April},
	abstract = {Unlike innovation based on a strong professional culture involving close collaboration between professionals in academia and/or corporations, the current Free/Libre Open Source Software (FLOSS) development entails a global knowledge network, which consists of 1) a heterogeneous community of individuals and organisations who do not necessarily have professional backgrounds in computer science but competent skills to understand programming and working in a public domain; 2) corporations. This paper highlights the importance of the hybrid form of developing and implementing software, and also identifies several key factors shaping the collaboration between OSS firms and the community.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin4_hybrid.pdf},
	author = {Yu-wei Lin}
}
@conference {769,
	title = {An Hypergraph Based Approach for Unlocking Power Relations in Rhizomatic Open Source Software Communities},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {272},
	abstract = {This study, first, points the rhizomatic nature of open source software (OSS) communities. Then, it proposes an hypergraph based research methodology both to capture and to analyze dynamics of OSS communities. An exemplary hypergraph theoretical analysis of power antecedence within rhizomatic network of an OSS community is illustrated.},
	url = {http://pascal.case.unibz.it/handle/2038/626},
	author = {{\"O}zel, B{\"u}lent}
}
@unpublished {flosswp238,
	title = {I Walk the Open Road: Toward an Open Source Philosophy},
	year = {2005},
	month = {September},
	abstract = {This paper addresses the concept of "Open Source" in a philosophical way. It argues that open source is a virtual entity with ontological significance beyond the realm of the software movement that granted its naming. The paper includes an examination of the technical language surrounding open source software, progresses through a philosophical exploration of this language removed from the specificity of computer languages and technologies, and then returns to an analysis of The Open Source Definition in the light of the philosophical investigation.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cooksey.pdf},
	author = {Robert Cooksey}
}
@conference {781,
	title = {Idealism and Commercialism {\textendash} Developing Free/Libre and Open Source Software in Private Businesses},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {301-302},
	abstract = {This paper presents a PhD research project undertaken as part of a larger project aimed at paying sociological attention to different forms of distribution of knowledge, including program code. We want to investigate empirically how the commons knows as free/open source software is actually made. In my PhD project I study the use and development of FLOSS in private businesses, focusing on professional developers working in private businesses and at the same time participating in the FLOSS community. The theoretical starting point is theories of power, dominance and legitimacy by Max Weber and Pierre Bourdieu.},
	keywords = {dominance, FLOSS, FLOSS community, free/libre, legitimacy, linux, open source, Private Businesses, social organisation, theories of power},
	url = {http://pascal.case.unibz.it/handle/2038/970},
	author = {Lundestad, Christian V.}
}
@article {105,
	title = {Improving Web accessibility through an enhanced open-source browser},
	journal = {Ibm Systems Journal},
	volume = {44},
	number = {3},
	year = {2005},
	note = {Times Cited: 2},
	pages = {573-588},
	abstract = {The accessibilityWorks project provides software enhancements to the Mozilla (TM) Web browser and allows users to control their browsing environment. Although Web accessibility standards specify markup that must be incorporated for Web pages to be accessible, these standards do not ensure a good experience for all Web users. This paper discusses user controls that facilitate a number of adaptations that can greatly increase the usability of Web pages for a diverse population of users. in addition to transformations that change page presentation, innovations are discussed that enable mouse and keyboard input correction as well as vision-based control for users unable to use their hands for computer input.},
	author = {Hanson, V. L. and Brezin, J. P. and Crayne, S. and Keates, S. and Kjeldsen, R. and Richards, J. T. and Swart, C. and Trewin, S.}
}
@article {flosswp222,
	title = {"Infectious" Open Source Software: Spreading Incentives or Promoting Resistance?},
	year = {2005},
	month = {April},
	abstract = {Some free or open source software infects other software with its licensing terms. Free or open source software is a copyright based licensing system. It typically allows modification and distribution on conditions such as source code availability, royalty-free use and other requirements. Some licenses require distribution of modifications under the same terms. A license is infectious when it has a strong scope for the modifications provision. The scope arises from a broad conception of software derivative works. A strong infectious ambit would apply itself to modified software, and to software intermixed or coupled with non-open-source software. Popular open source software, including the GNU/Linux operating system, uses a license with this feature. This Article assesses the efficacy of broad infectious license terms to determine their incentive effects for open source and proprietary software. The analysis doubts beneficial effects. Rather, on balance, such terms may produce incentives detrimental to interoperability and coexistence between open and proprietary code. As a result, open source licensing should precisely define infectious terms in order to support open source development without countervailing effects and misaligned incentives.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/vetter2.pdf},
	author = {Greg R Vetter}
}
@article {flosswp229,
	title = {Innovativeness of open source software projects},
	year = {2005},
	month = {August},
	abstract = {The paper addresses an ongoing debate about the innovativeness of open source projects and critically evaluates the innovative potential of 500 most active projects registered by SourceForge.net. The analysis is based on a proposed framework, distinguishing between radical inventions, technology / platform modifications, and marketing innovations. Research findings include relatively low levels of technical newness in the studies sample, alongside high interest of developers and users in the innovative projects. The article discusses the underlying mechanisms, restricting innovativeness of community-driven open source efforts, and postulates the establishment of an institution of idea brokers playing roles corresponding to venture capitalists in the commercial software domain.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/klincewicz.pdf},
	author = {Krzysztof Klincewicz}
}
@conference {798,
	title = {An International Master Programme in Free Software in the European Higher Education Space},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {349-352},
	abstract = {The Universitat Oberta de Catalunya (Open University of Catalonia, UOC) offers an International Master programme in Free Software. The first edition of this master programme began on November 2003 and there are about 240 students currently enrolled at the different specialities offered by the program. In this paper, the design, the methodology and the first few conclusions drawn from this higher education experience are discussed and summarized. After this master programme was changed to accomplish with European Higher Education Space (EHES).},
	keywords = {education, free software, FS community, GNU/Linux, learning, master programme, software development, university},
	url = {http://pascal.case.unibz.it/handle/2038/713},
	author = {Meg{\'\i}as, David and Serra, Jordi and Macau, Rafael}
}
@article {flosswp204,
	title = {Intrinsic motivations and profit-oriented firms in Open Source software. Do firms practise what they preach?},
	year = {2005},
	month = {February},
	abstract = {A growing body of economic literature is exploring the incentives of the agents involved in the Open Source movement. However, most empirical analyses focus on individual developers and neglect firms that do business with Open Source software (Open Source firms). This paper contributes to the literature by providing empirical evidence on the incentives of firms that engage in Open Source activities. Data on firms? motivations were collected by a large-scale survey conducted on 146 Italian companies supplying Open Source (OS) solutions and show that intrinsic, community-based incentives do play a role. Nevertheless, these positive attitudes towards the values of the OS community, which are quite surprising by profit-oriented firms, are not in general put into practise. Discrepancy between attitudes and behaviours is a widely investigated phenomenon in social psychology literature. We explore its pattern in our sample, find that it does not concern all the respondents, and single out a group of firms adopting a more consistent behaviour. Our results are in line with the literature on individual motivations in organisations and Open Source business models .},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rossi_motivations.pdf},
	author = {Cristina Rossi}
}
@conference {784,
	title = {An Investigation of Developer and User Activity In FLOSS Projects},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {307-308},
	abstract = {This document outlines research plans to investigate the evolution of a set of FLOSS (Free, Libre, and Open Source Software) projects and their communities by looking at patterns of developer and user activity through a combination of analysis of archived material and interaction with the project communities. The goal of the proposed research is to better understand the dynamics within FLOSS projects and how some projects become successful.},
	keywords = {developer, development, FLOSS, FLOSS project, open source, pattern, portal, project},
	url = {http://pascal.case.unibz.it/handle/2038/712},
	author = {Gale, Stephen}
}
@article {63,
	title = {The Jikes research virtual machine project: Building an open-source research community},
	journal = {Ibm Systems Journal},
	volume = {44},
	number = {2},
	year = {2005},
	note = {Times Cited: 3},
	pages = {399-417},
	abstract = {This paper describes the evolution of the Jikes (TM) Research Virtual Machine project from an IBM internal research project, called Jalapeno, into an open-source project. After summarizing the original goals of the project, we discuss the motivation for releasing it as an open-source project and the activities performed to ensure the success of the project. Throughout, we highlight the unique challenges of developing and maintaining an open-source project designed specifically to support a research community.},
	author = {Alpern, B. and Augart, S. and Blackburn, S. M. and Butrico, M. and Cocchi, A. and Cheng, P. and Dolby, J. and Fink, S. and Grove, D. and Hind, M. and McKinley, K. S. and Mergen, M. and Moss, J. E. B. and Ngo, T. and Sarkar, V. and Trapp, M.}
}
@conference {787,
	title = {Knowledge, Communication and Innovation: the case of Open Source Software as Open Media},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {314-316},
	abstract = {The understanding of the major characteristics of Linux Operative System and, more in general, the analysis of the so-called Open Source Phenomenon, is nowadays a central issue in order to appreciate the ongoing evolution of software industry. Free/Open Source Software model may appears a {\textquotedblleft}revolution{\textquotedblright} in the way of thinking about software development, distribution and use. But, at a closer glance, it reveals itself more as an {\textquotedblleft}evolution{\textquotedblright} along the path of {\textquotedblleft}tinkering with software{\textquotedblright} typical of the Hacker Tech-Culture since the beginning of sixties. In fact the {\textquotedblleft}open source way{\textquotedblright} of developing software results from the hackers habit of sharing technological knowledge and it represents a perfection of this, due to the availably of new communication technologies. The aim of this research is to explain this evolution, to point out its historical, economics and technological determinants and to link it with the evolution of the {\textquotedblleft}communicational medium{\textquotedblright} used by the open source ...},
	keywords = {attributive, Creative Commons, non-commercial},
	url = {http://pascal.case.unibz.it/handle/2038/972},
	author = {Lorenzo Benussi}
}
@article {flosswp200,
	title = {The Launching of Mozilla Firefox - A Case Study in Community-Led Marketing},
	year = {2005},
	month = {January},
	abstract = {Mozilla Firefox is a Free/Libre/Open Source (FLOSS) browser supported by the Mozilla Foundation. This browser was recently released and has met with considerable success- it has been downloaded more than 20 million times and has already taken considerable market share from its prime competitor- Microsoft?s Internet Explorer. In this paper, I chronicle how the efforts of 63000 volunteers led to a community successfully competing with a powerful corporation. I identify four factors as the key facilitators to Firefox? success- complacent competition, product superiority, presence of marketing leader and volunteer support.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/sandeep2.pdf},
	author = {Sandeep Krishnamurthy}
}
@conference {789,
	title = {Legal issues of Open Source Software},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {320-321},
	abstract = {From the legal standpoint, Open Source amounts to distributing rights and obligations in software license agreements in such a way, that they would (1) both grant users control over the program and (2) facilitate the sharing of improvements. The Open Source idea aims at reversing the process usually referred to as proprietary licensing and equaling the rights of the users with these of the authors. To some extent, it attempts to destroy monopolies created by copyright laws and to prevent them to arise again. There is much in the discussion on the legal issues of Open Source. The first voices came from the programmers who started the movement.},
	keywords = {cooperation, copyright law, freedom, intellectual property, legal issue, license, open source software},
	url = {http://pascal.case.unibz.it/handle/2038/974},
	author = {Siewicz, Krzysztof}
}
@conference {Antoniol:2005:LPC:1083142.1083156,
	title = {Linear predictive coding and cepstrum coefficients for mining time variant information from software repositories},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {74-78},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {This paper presents an approach to recover time variant information from software repositories. It is widely accepted that software evolves due to factors such as defect removal, market opportunity or adding new features. Software evolution details are stored in software repositories which often contain the changes history. On the other hand there is a lack of approaches, technologies and methods to efficiently extract and represent time dependent information. Disciplines such as signal and image processing or speech recognition adopt frequency domain representations to mitigate differences of signals evolving in time. Inspired by time-frequency duality, this paper proposes the use of Linear Predictive Coding (LPC) and Cepstrum coefficients to model time varying software artifact histories. LPC or Cepstrum allow obtaining very compact representations with linear complexity. These representations can be used to highlight components and artifacts evolved in the same way or with very similar evolution patterns. To assess the proposed approach we applied LPC and Cepstral analysis to 211 Linux kernel releases (i.e., from 1.0 to 1.3.100), to identify files with very similar size histories. The approach, the preliminary results and the lesson learned are presented in this paper.},
	keywords = {change history, data mining, evolution, files, kernel, linear predictive coding, linux, lpc, size, software evolution, source code},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083156},
	url = {http://doi.acm.org/10.1145/1082983.1083156},
	attachments = {https://flosshub.org/sites/flosshub.org/files/74LinearPredictive.pdf},
	author = {Antoniol, Giuliano and Rollo, Vincenzo Fabio and Venturi, Gabriele}
}
@conference {771,
	title = {Linux on the portuguese schools: the Caixa M{\'a}gica experience},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {279-280},
	abstract = {This article depicts the experience of Caixa M{\'a}gica
in the deployment of 14.000 computers with dual boot in the
portuguese schools. Caixa M{\'a}gica role was preparing its
Linux distribution to become friendly to students and
teachers.
This project was very successful and is now beginning with a
second phase with 5.000 more computers.
In this experience report with present some of the obstacles
and achievements accomplished in {\textquotedblleft}Salas TIC{\textquotedblright}.},
	author = {Susana Nunes, and Fl{\'a}vio Moringa and Miguel Louren{\c c}o and Paulo Trezentos}
}
@article {flosswp245,
	title = {Linux vs. Windows: A comparison of application and platform innovation incentives for open source and proprietary software platforms},
	year = {2005},
	month = {October},
	abstract = {The paper analyzes and compares the investment incentives of platform and application developers for Linux and Windows. We find that the level of investment in applications is larger when the operating system is open source rather than proprietary. The comparison of the levels of investment in the operating systems depends, among others, on reputation effects and the number of developers. The paper also develops a short case study comparing Windows and Linux and identifies new directions for open source software research.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/economideskatsamakas.pdf},
	author = {Nicholas Economides and Evangelos Katsamakas}
}
@conference {777,
	title = {Live! I-Learn @ Home},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {294-295},
	abstract = {In this paper we present a live CD based on GNU/Linux (Knoppix), customized in order to supply a complete working and studying environment for the students of the Corso di Studi in Informatica. In particular, it supplies the Moodle course management system for e-learning complete of the courses of the first year. The aim is to enable the use of such resources off-line and without requiring special skills that will be achieved by studying but that newbies do not have.},
	keywords = {e-learning, environment, GNU/Linux, java, open source, technology},
	url = {http://pascal.case.unibz.it/handle/2038/977},
	author = {Baldoni, Matteo and Baroglio, Cristina and Roversi, Luca and Grandi, Claudio}
}
@conference {791,
	title = {Looking at Free and Open Source Software: A Study about F/OSS Developers{\textquoteright} Culture},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {324-325},
	abstract = {My work will be a cultural study of a F/OSS development project, mixing a symmetric approach with the interaction analysis by Erving Goffman. Methodologically I will approach cyber {\textendash} ethnography.},
	keywords = {cultural analysis, cultural study, cyber, F/OSS developers, open source, software development},
	url = {http://pascal.case.unibz.it/handle/2038/968},
	author = {Teli, Maurizio}
}
@conference {730,
	title = {Measuring Success of Open Source Projects Using Web Search Engines},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {93-99},
	abstract = {What makes an open source project successful? In this paper we show that the traditional factors of success of open source projects, such as the number of downloads, deployments or community activity are inconvenient to collect or insufficient. We then correlate success of an open source project with its popularity on the Web. We show several ideas of how such popularity could be measured using Web search engines and provide experimental results from quantitative analysis of the measures we introduce on representative large samples of open source projects from SourceForge.},
	url = {http://hdl.handle.net/2038/973},
	author = {Weiss, Dawid}
}
@conference {774,
	title = {Migrazione di un Sistema Informativo da UNIX-AIX a UNIX-Linux},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {287-288},
	abstract = {Il presente documento ha come obiettivo quello di descrivere la politica adottata dall{\textquoteright}Istituto Nazionale di Statistica rispetto all{\textquoteright}uso del software Open Source. In particolare vengono descritti i sistemi che attualmente operano su piattaforma Linux, quelli che sono in fase di migrazione e le scelte che si sono fatte nel caso di convivenza tra sistemi {\textquotedblleft}open{\textquotedblright} e sistemi {\textquotedblleft}proprietari{\textquotedblright}. Viene inoltre illustrata l{\textquoteright}architettura hardware scelta nel caso della migrazione di un sistema complesso da piattaforma interamente proprietaria (UNIX AIX) a piattaforma con sistema operativo open Linux Red Hat.},
	keywords = {architettura hardware, linux, migrazione, open source, server, sistema informativo, sistema proprietario, unix aix},
	url = {http://pascal.case.unibz.it/handle/2038/978},
	author = {Colasanti, Cecilia and Patruno, Vincenzo and Vaccari, Carlo}
}
@conference {Fischer:2005:MED:1083142.1083145,
	title = {Mining evolution data of a product family},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {12-16},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Diversification of software assets through changing requirements impose a constant challenge on the developers and maintainers of large software systems. Recent research has addressed the mining for data in software repositories of single products ranging from fine- to coarse grained analyses. But so far, little attention has been payed to mining data about the evolution of product families. In this work, we study the evolution and commonalities of three variants of the BSD (Berkeley Software Distribution), a large open source operating system. The research questions we tackle are concerned with how to generate high level views of the system discovering and indicating evolutionary highlights. To process the large amount of data, we extended our previously developed approach for storing release history information to support the analysis of product families. In a case study we apply our approach on data from three different code repositories representing about 8.5GB of data and 10 years of active development.},
	keywords = {bsd, change analysis, change history, cvs, evolution, freebsd, netbsd, openbsd, release history, source code, text mining},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083145},
	url = {http://doi.acm.org/10.1145/1082983.1083145},
	attachments = {https://flosshub.org/sites/flosshub.org/files/12MiningEvolution.pdf},
	author = {Fischer, Michael and Oberleitner, Johann and Ratzinger, Jacek and Gall, Harald}
}
@conference {Huang:2005:MVH:1083142.1083158,
	title = {Mining version histories to verify the learning process of Legitimate Peripheral Participants},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {84-88},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Since code revisions reflect the extent of human involvement in the software development process, revision histories reveal the interactions and interfaces between developers and modules.We therefore divide developers and modules into groups according to the revision histories of the open source software repository, for example, sourceforge.net. To describe the interactions in the open source development process, we use a representative model, Legitimate Peripheral Participation (LPP) [6], to divide developers into groups such as core and peripheral teams, based on the evolutionary process of learning behavior.With the conventional module relationship, we divide modules into kernel and non-kernel types (such as UI). In the past, groups of developers and modules have been partitioned naturally with informal criteria. In this work, however, we propose a developer-module relationship model to analyze the grouping structures between developers and modules. Our results show some process cases of relative importance on the constructed graph of project development. The graph reveals certain subtle relationships in the interactions between core and non-core team developers, and the interfaces between kernel and non-kernel modules.},
	keywords = {awstats, bzflag, cvs, filezilla, gallery, Legitimate Peripheral Participants (LPP), moodle, open boundary, open source software development process, phpmyadmin, social networks, sourceforge},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083158},
	url = {http://doi.acm.org/10.1145/1082983.1083158},
	attachments = {https://flosshub.org/sites/flosshub.org/files/84MiningVersion.pdf},
	author = {Huang, Shih-Kun and Liu, Kang-min}
}
@conference {741,
	title = {Modular Design and the Development of Complex Artifacts: Lessons from Free/Open Source Software},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {162-171},
	abstract = {Organizational and managerial theories of modularity applied to the design and production of complex artifacts are used to interpret the rise and success of development methodologies and practices in Free/Open Source software projects. Strengths and risks of the adoption of a modular approach in software project management are introduced and are related to the achievements of various Free/Open Source Software projects (among them: the GNU operating system, the Linux kernel, the HURD kernel). It is suggested that mindful implementation of the principles of modularity may improve the rate of success of many Free/Open Source software projects. Specific case studies here depicted, as well as indirect observation of common programming practices employed by Free/Open Source developers and users, suggest a possible revision towards an improved theory of modularity that may be extended also to settings different from software production.},
	url = {http://pascal.case.unibz.it/handle/2038/979},
	author = {Alessandro Narduzzo and Rossi, Alessandro}
}
@conference {715,
	title = {Multi-Modal Modeling of Open Source Software Requirements Processes},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {1-8},
	abstract = {Understanding the context, structure, activities, and content of software development processes found in practice has been and remains a challenging problem. In the world of free/open source software development, discovering and understanding what processes are used in particular projects is important in determining how they are similar to or different from those advocated by the software engineering community. Prior studies however have revealed that the requirements processes in OSSD projects are different in a number of ways, including the general lack of explicit software requirements specifications. In this paper, we describe how a variety of modeling perspectives and techniques are used to elicit, analyze, and validate software requirements processes found in OSSD projects, with examples drawn from studies of the NetBeans.org project.},
	url = {http://pascal.case.unibz.it/handle/2038/975},
	author = {Walt Scacchi and Chris Jensen and Noll, John and Elliott, Margaret}
}
@conference {1682,
	title = {The Mysteries of Open Source Software: Black and White and Red All Over?},
	booktitle = {Proceedings of the 38th Annual Hawaii International Conference on System Sciences},
	year = {2005},
	pages = {196a - 196a},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Big Island, HI, USA},
	abstract = {Open Source Software (OSS) has attracted enormous media and research attention since the term was coined in February 1998. The concept itself is founded on the paradoxical premise that software source code-the {\textquoteright}crown jewels{\textquoteright} for many proprietary software companies-should be provided freely to anyone who wishes to see it. Given this fundamental initial paradox, it is perhaps hardly surprising that the OSS concept is characterised by contradictions, paradoxes and tensions throughout. In this paper we focus specifically on the following issues in relation to OSS: the cathedral v. bazaar development approach; collectivism v. individualism, the bitter strife within the OSS community itself (OSS v. OSS), and between OSS and the Free Software Foundation (OSS v. FSF); whether OSS represents a paradigm shift in the software industry; whether the software is truly open-the Berkeley Conundrum, as we have termed it here; whether OSS truly is high quality software; and whether OSS is a {\textquoteright}one size fits all,{\textquoteright} representing the future model for all software development.
},
	doi = {10.1109/HICSS.2005.609},
	author = {Fitzgerald, B. and Agerfalk, P.J.}
}
@proceedings {133,
	title = {Negotiation and the coordination of information and activity in distributed software problem management},
	year = {2005},
	pages = {187-196},
	publisher = {ACM},
	address = {Sanibel Island, Florida, USA},
	author = {Sandusky, R. J. and Gasser, L.}
}
@article {flosswp241,
	title = {New approaches to intellectual property : from open software to knowledge based industrial activities},
	year = {2005},
	month = {October},
	abstract = {We analyze the question of intellectual property in computer software, showing that both copyright and patents do not fit to the specificities and needs of this industry. The alternative model of Open Source Software, based on a very new juridical concept called GPL "General Public License", tends to take a growing importance. We explain its main characteristics, which consist to impose to the producers to disclose the source-code of the concerned programs and of any further improvement if they re-distribute/resell it. We show that by doing that it introduces a totally different approach of intellectual property within industrial strategies, based on a weaker intellectual protection. We discuss the consequences of such a movement in intistitutional and public policy terms and we enlarge the approach to understand its exemplariness, in the context of a knowledge based economy, for a growing number of industrial activities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/jullienzimmermann.pdf},
	author = {Nicolas Jullien and Jean-Beno\^{\i}t Zimmermann}
}
@inbook {anderson2005open,
	title = {Open and Closed Systems are Equivalent (that is, in an ideal world)},
	booktitle = {Perspectives on free and open source software},
	year = {2005},
	pages = {127-142},
	publisher = {MIT Press},
	organization = {MIT Press},
	abstract = {...In May 2002, I proved a controversial theorem [8]: that, under the standard assumptions of reliability growth theory, it does not matter whether the system is open or closed. Opening a system enables the attacker to discover vulnerabilities more quickly, but it helps the defenders exactly as much.
This caused consternation in some circles, as it was interpreted as a general claim that open systems are no better than closed ones. But that is not what the theorem implies. Most real systems will deviate in important ways from the assumptions of the standard reliability growth model, and it will often be the case that open systems (or closed systems) will be better in some particular application. My theorem lets people concentrate on the differences between open and closed systems that matter in a particular case.},
	keywords = {security},
	isbn = {9780262062466},
	url = {http://www.cl.cam.ac.uk/~rja14/Papers/toulousebook.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/toulousebook.pdf},
	author = {Anderson, Ross}
}
@article {flosswp237,
	title = {Open and Collaborative Biomedical Research: Theory and Evidence},
	year = {2005},
	month = {January},
	abstract = {Although a few commentators have discussed briefly the application of open source-type principles to biomedical research, they have not analyzed carefully how the model is actually being used. In this paper, I draw upon an ongoing, multi-year empirical inquiry into the role of intellectual property in computational biology and associated efforts to evaluate the extent to which the open and collaborative research model may promote socially desirable biomedical innovation ? that is, innovation that produces marginal health benefits in excess of its marginal costs.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rai.pdf},
	author = {Arti Rai}
}
@article {flosswp217,
	title = {Open Beyond Software},
	year = {2005},
	month = {January},
	abstract = {The "community-based" model has generated many of the innovations we use on a daily basis. The social structure created by this model has cultivated many entrepreneurial ventures and even seeded new industries and product categories. In this paper, I discuss three elements of this model and present four exemplars of the model that span fields and centuries. I conclude by reframing our view of the innovation process as driven by the activities of firms and research institutions and discussing implications for firms and policy.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shah4.pdf},
	author = {Sonali Shah}
}
@conference {755,
	title = {Open Source, a development option},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {228-230},
	abstract = {The Open Source (OS) movement is one of the most amazing revolutions in last decades. It is probably the most successful collaborative project in history. Its philosophy: learn, innovate and share, has created an immense knowledge base which has been opened to everyone. It brings technology to everybody and empowers people, communities, governments and companies. The purpose of this paper is to show how OS solutions, methods and communities can support a number of key areas for a nation{\textquoteright}s development, at the same time that generates its own infrastructure which not only supports development but also has the potential to become a main business activity for that nation.},
	url = {http://pascal.case.unibz.it/handle/2038/1261},
	author = {Martinez, Arturo}
}
@conference {754,
	title = {Open Source and Business Model Innovation. The Funambol case},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {224-227},
	abstract = {A comprehensive theoretical framework about open source business models is still missing, notwithstanding a growing number of contributions. This lack of literature is mainly due to the relative newness of the phenomena. This paper aims at giving a contribution to the ongoing discussion about open source business implications. The research hypothesis is that open source represents a disruptive innovation for the software industry. The purpose is to understand, through case study research, how open source companies can develop successful business models. Funambol provides an interesting example of an optimized business model, able to leverage the open source advantage in an emerging market. The paper is structured in three main parts: the first one aims at outlining the research hypothesis and methodology. The second part identifies the unique competitive factors distinguishing open source business and the main business implications. The final part focuses on the analys...},
	url = {http://pascal.case.unibz.it/handle/2038/967},
	author = {Onetti, Alberto and Capobianco, Fabrizio}
}
@conference {793,
	title = {Open Source and IMS Learning Design: Building the Infrastructure for eLearning},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {329-333},
	abstract = {The development of open, flexible eLearning specifications has significant implications for and interactions with the FOSS movement. A short overview of eLearning specifications is provided, focusing on the difference between SCORM and Learning Design (LD). The significance of LD for FOSS is examined, and common values identified. The particular contribution made by FOSS to LD infrastructure is discussed, and the importance of reference applications described. An overview is given of the FOSS applications available, divided into design time and run time, with particular reference to LD editors and the CopperCore Learning Design engine.},
	keywords = {eLearning, eLearning specification, FOSS, infrastructure, Learning Design},
	url = {http://pascal.case.unibz.it/handle/2038/1264},
	author = {Griffiths, David and Blat, Josep and Elferink, Ray and Zondergeld, Sara}
}
@unpublished {flosswp223,
	title = {Open Source Biotechnology},
	year = {2005},
	month = {June},
	abstract = {Building on discussions with public and private sector industry participants, funding agencies, leaders of the free and open source software movement and scholars in a range of disciplines, this PhD thesis assesses the desirability and feasibility of extending open source principles to biotechnology research and development. It argues that "open source biotechnology" is both desirable and broadly feasible, and demonstrates that many of the essential elements of an embryonic open source movement are already present in this field.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hope.pdf},
	author = {Janet Hope}
}
@unpublished {flosswp205,
	title = {Open Source Community Building},
	year = {2005},
	month = {March},
	abstract = {Building an active and helpful community around an open source project is a complex task for its leaders. Therefore investigations in this work are intended to define the optimum starting position of an open source project and to identify recommendable promoting actions by project leaders to enlarge community size in a healthy way. For this paper eight interviews with committed representatives of successful open source projects have led to over 12 hours of conversation about community building. Analysing the statements of these experienced community members exposed helpful activities that led to the presently prospering communities of their projects. Summarizing the conclusions of this qualitative research a table with conditions for successful open source project initialisation and a subject-level promotion matrix of community building could be created. They include suggestions o?n how to start a new open source project and how to improve and increase the community of an already advanced open source project.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/sturmer.pdf},
	author = {Matthias St{\"u}rmer}
}
@conference {803,
	title = {Open Source firms: from community to business},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {362-363},
	abstract = {A large body of literature is now addressing the Open Source (OS) phenomenon. Economic scholars have deeply investigated the incentives of people working within OS community projects; the software production models in absence of explicit hierarchical structures; the successful dissemination of OS programs in environments dominated by proprietary standards; the peculiarities in the management of intellectual property within the OS framework. Theoretical contributions have coupled with the collection of extensive empirical evidence mainly through surveys taken on individual developers. Nowadays a new trend is shaping the OS movement: more and more firms are entering the market by offering software solutions based on the new paradigm (Open Source firms).},
	keywords = {business, COMMUNITY, firms, Open Source firms},
	url = {http://pascal.case.unibz.it/handle/2038/1265},
	author = {Andrea Bonaccorsi and Cristina Rossi}
}
@conference {750,
	title = {Open Source for e-Government Application Integration: a PHP-based solution},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {204-208},
	abstract = {This paper introduces UniGeINT - University of Genoa Integration Tool -, a framework designed to provide integration between several existing tools, databases and data repositories we used in internal administrative processes, by exploiting OSS benefits in terms of costs reduction and bug reporting. Moreover, it adopts state-of-art solutions in Enterprise Application Integration, by using specific design patterns able to match existing IT marrow. So we required in final product common features unmissable for a large scale corporative environment: reliability and fault tolerance, besides to a complete integration with anything previously developed.},
	url = {http://pascal.case.unibz.it/index.jsp},
	author = {Gammeri, Simone and Di Cerbo, Francesco and Scotto, Marco and Succi, Giancarlo and Vernazza, Tullio}
}
@article {flosswp213,
	title = {Open Source Patenting},
	year = {2005},
	month = {April},
	abstract = {The open source and free software movements have used self-perpetuating copyright licenses to maintain open access to publicly distributed software. This model of licensing has now migrated to the field of biotechnology, where patents rather than copyrights dominate proprietary rights. Consequently, a model for open source patenting or free biotechnology presents a constellation of legal issues not typically found in previous open source licensing. This paper discusses several of these issues, including the nature of the rights transferred, the activities that may trigger the terms of the license, and the legal prohibitions on certain forms of licensing.},
	author = {Sara Boettiger}
}
@conference {734,
	title = {Open Source Software in Public Administration. A real example OSS for egovernment Observatories},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {119-124},
	abstract = {Open Source Software (OSS) has risen to great prominence. Briefly, OSS programs are programs whose licenses give users the freedom to run the program for any purpose, to study and modify the program, and to redistribute copies of either the original or modified program (without having to pay royalties to previous developers). In the last years the Italian Public Administrations (PA) points out the benefits of using OSS as a valid alternative to closed source software. The goal of this paper is to illustrate the state of the art of OSS in Italian PA and describe two pratical examples of the use of OSS in the e-government area. Those examples are represented by the local e-government observatories developed respectively by Emilia Romagna and Liguria Regions. A real and settled knowledge about current and past egovernment initiatives in Italy can improve the future planning. For these reasons several Italian Regions developed Observatories for e-Government and Informatio...},
	url = {http://pascal.case.unibz.it/handle/2038/1208},
	author = {Davini, Emanuela and Faggioni, Elisabetta and Granatella, Giampiero and Tartari, Dimitri and Scotto, Marco}
}
@conference {758,
	title = {Open Source software, intrinsic motivations and profit-oriented firms. Do not firms practise what they preach?},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {241-245},
	abstract = {This paper contributes to the literature by
providing empirical evidence on the incentives of firms that
engage in Open Source activities. Data collected by a survey
on 146 Italian companies supplying OS solutions (Open
Source firms) show that (surprisingly) intrinsic, communitybased
incentives do play a role but are not, in general, put into
practise. The discrepancy between attitudes and behaviours is
investigated and firms adopting more consistent behaviours
are singled out. Our results are in line with the literature on
business models of firms entering the Open Source field.},
	author = {Andrea Bonaccorsi and Cristina Rossi}
}
@conference {760,
	title = {Open Source: Toward Innovations through Educational Development in China},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {254-258},
	abstract = {This paper describes the author{\textquoteright}s personal viewpoints toward open source software, particularly for the educational development in China. The current status of China is presented to explain why open source is critical within the Chinese educational domain. We believe that open source is suitable not only for financial reasons, but also because it will provide an efficient solution for China to establish an innovative environment whilst promoting intellectual capacities. The benefits of using open source are ideal for the current situations in the Chinese educational system. In this paper, one example is given about the promotion activities of the open source software Scilab (SCILAB(c)INRIA-ENPC) in the Chinese educational domain since 2001. Activities demonstrate that open source ideas and practices will have a great impact in China. Lessons and progress are demonstrated from these activities. The final goal of the Chinese educational development is to increase innovati...},
	url = {http://pascal.case.unibz.it/handle/2038/1259},
	author = {Hu, Bao-Gang}
}
@conference {736,
	title = {Open-source software in an occupational health application: the case of Heales Medical Ltd.},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {130-134},
	abstract = {In this paper, we provide a case study of a small company, Heales Medical Ltd., that has chosen to use opensource software to develop an online integrated patient management system. We use this case study to examine some preconceptions of open-source technology in the light our experiences of open source in the Heales project. We identify costs and cost savings as being the primary business considerations, and identify software purchase and licensing as key advantages for open-source. We then look at development issues including software evaluation, implementation and programming, and identify these as more costly for open-source, in terms of time and effort expended. We also look at issues to do with open source licensing, which our initial investigations suggest is confusing and requires further analysis. Overall, the ability to modify the source code is regarded as a key benefit of open-source software, but in a business environment like Heales, this is of little imp...},
	url = {http://pascal.case.unibz.it/handle/2038/1257},
	author = {Tiangco, Francis and Stockwell, Alison and Sapsford, John and Rainer, Austen and Swanton, Eamonn}
}
@conference {762,
	title = {OSS implementation solutions for Public Administration applications},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {259-262},
	abstract = {The paper will address the approach used by our company to develop an electronic certified mail solution, called eCertMail, which allows the transmission of documents in electronic form guaranteeing their sending and their reception from a legal point of view, using OS technologies.},
	url = {http://pascal.case.unibz.it/handle/2038/1420},
	author = {Giacalone, Paolo}
}
@conference {767,
	title = {Osservatorio Tecnologico: services for open source software at school},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {269},
	abstract = {Technology Transfer is a keyword in ICT field. OsservatorioTecnologico, the Italian web based national service for technology transfer from ICT to schools, ever since the beginning indicated the Open Source Software (OSS) as one of the main topics. Several services are provided to schools, for example: dissemination of OSS Best Practices in education, guideline about OSS for public sector, monitoring OSS spreading in schools.},
	url = {http://pascal.case.unibz.it/handle/2038/1421},
	author = {Sissa, Giovanna}
}
@conference {723,
	title = {OSSmole: A collaborative repository for FLOSS research data and analyses},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {54-60},
	abstract = {This paper introduces a collaborative project, {\textquotedblleft}OSSmole{\textquotedblright}, designed to gather, share and store comparable data and analyses of free and open source software development for academic research. The project draws on the ongoing collection and analysis efforts of many research groups, reducing duplication, and promoting compatibility both across sources of FLOSS data and across research groups and analyses. The paper outlines current difficulties with the current typical quantitative FLOSS research process and uses these to develop requirements and presents the design of the system.},
	url = {http://pascal.case.unibz.it/handle/2038/1422},
	author = {Howison, James and Conklin, Megan and Kevin Crowston}
}
@conference {772,
	title = {OTRS: un sistema a ticket per la gestione dell{\textquoteright}help desk},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {281},
	abstract = {Descriviamo l{\textquoteright}esperienza di utilizzo di un software a codice sorgente aperto per la gestione a ticket dell{\textquoteright}help desk informatico del D.I.S.I. (Dipartimento di Informatica e Scienze delll{\textquoteright}Informazione) dell{\textquoteright}Universit{\`a} degli Studi di Genova.},
	keywords = {help desk, open source, ticketing system, trouble ticket},
	url = {http://pascal.case.unibz.it/handle/2038/1423},
	author = {Bencetti, Stefano and Verduci, Gianni}
}
@article {flosswp214,
	title = {Penguins, Camels, and Other Birds of a Feather: Brokerage, Boundary Spanning, and Leadership in Open Innovation Communities},
	year = {2005},
	month = {April},
	abstract = {What types of human and social capital identify the emergence of leaders of open innovation communities? Consistent with the norms of an engineering culture, we find that future leaders must first make strong technical contributions. Beyond technical contributions, they must then integrate their voluntary communities in order to avoid the ever present danger of forking and balkanization. This is enabled by two correlated but distinct social positions: brokerage, and boundary spanning between technological modules. An inherent lack of trust associated with brokerage positions can be overcome through physical interaction or contributions within technological boundaries. Successful leaders are thus the product of strong technical contribution and a structural position that can bind the community together.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/flemingwaguespack.pdf},
	author = {Lee Fleming}
}
@conference {Phadke:2005:PRM:1145319.1145337,
	title = {Predicting risky modules in open-source software for high-performance computing},
	booktitle = {Proceedings of the second international workshop on Software engineering for high performance computing system applications},
	series = {SE-HPCS {\textquoteright}05},
	year = {2005},
	pages = {60{\textendash}64},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {This paper presents the position that software-quality modeling of open-source software for high-performance computing can identify modules that have a high risk of bugs.Given the source code for a recent release, a model can predict which modules are likely to have bugs, based on data from past releases. If a user knows which software modules correspond to functionality of interest, then risks to operations become apparent. If the risks are too great, the user may prefer not to upgrade to the most recent release.Of course, such predictions are never perfect. After release, bugs are discovered. Some bugs are missed by the model, and some predicted errors do not occur. A successful model will be accurate enough for informed management action at the time of the predictions.As evidence for this position, this paper summarizes a case study of the Portable Extensible Toolkit for Scientific Computation (PETSC), which is a mathematical library for high-performance computing. Data was drawn from source-code and configuration management logs. The accuracy of logistic-regression and decision-tree models indicated that the methodology is promising. The case study also illustrated several modeling issues.},
	keywords = {C4.5, decision trees, empirical case study, high performance computing, logistic regression, Open-source software, PETSc, software metrics, software quality model, software reliability},
	isbn = {1-59593-117-1},
	doi = {10.1145/1145319.1145337},
	url = {http://doi.acm.org/10.1145/1145319.1145337},
	author = {Phadke, Amit A. and Allen, Edward B.}
}
@conference {Stewart:2005:PAI:1042438.1043100,
	title = {A Preliminary Analysis of the Influences of Licensing and Organizational Sponsorship on Success in Open Source Projects},
	booktitle = {Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences - Volume 07},
	series = {HICSS {\textquoteright}05},
	year = {2005},
	note = {"Publicly available data on open source projects registered on the Freshmeat website (www.freshmeat.net) was used to test the hypotheses. Data was collected from each project{\textquoteright}s Freshmeat website at the start and end of an eight month period (March - December 2002)."
"We first selected three project categories from which to draw our sample. These were utilities, software development, and games."
"Within these categories we further differentiated between new projects, which had been registered on the site within the two weeks prior to our first data collection point and older projects that had been registered more than two weeks prior to our initial data collection."
},
	month = {2005},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {This paper develops and tests a model of the impact of	licensing restrictiveness	and	organizational sponsorship on the popularity and vitality of open source software (OSS) development projects. Using data gathered from Freshmeat.net and OSS project home pages the main conclusions derived from the analysis are that organizational sponsorship has a positive effect on project popularity by easing user concerns about cost and quality and that license restrictiveness may have a negative effect on popularity by reducing the perceived utility of open source software. Theoretical and practical implications are discussed, and the paper outlines several avenues for future research.},
	keywords = {contributors, developers, freshmeat, license analysis, licensing, metadata, popularity, restrictive, users},
	isbn = {0-7695-2268-8-7},
	doi = {http://dx.doi.org/10.1109/HICSS.2005.38},
	url = {http://dx.doi.org/10.1109/HICSS.2005.38},
	author = {Stewart, Katherine J. and Ammeter, Anthony P. and Maruping, Likoebe M.}
}
@conference {764,
	title = {Principles for a Dynamic Software Ecosystem},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {267},
	abstract = {The open source software movement reflects one of the most dramatic developments in today{\textquoteright}s dynamic information technology industry. Interestingly, some commentators have sought to posit open source against proprietary software. This paper argues that while open source and proprietary models may be based on different development and distribution philosophies, neither model is inherently superior.},
	url = {http://pascal.case.unibz.it/handle/2038/1424},
	author = {M{\"u}ller, Beno{\^\i}t}
}
@article {898,
	title = {Process Modeling Across the Web Information Infrastructure},
	journal = {Software Process--Improvement and Practice},
	volume = {10},
	number = {3},
	year = {2005},
	month = {July-September},
	pages = {255-272},
	author = {Chris Jensen and Walt Scacchi}
}
@conference {757,
	title = {Proprietary Software and Open Source Philosophy: a shift in software{\textquoteright}s production methods},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {237-240},
	abstract = {The aim of this paper is to point out that, since the massive growth of Open Source Software (OSS), the production methods of software have changed. The change is not only recognisable within the OSS communities but most evident effects can be also observed in the {\textquotedblleft}proprietary{\textquotedblright} segment of the market. The data analysis has been performed by allocating a variation towards or away from cooperation/ competition according to the direction of about 12,000 communications, articles and technical notes dated from 1998 up to February 2005. A co-evolution path is identifiable: both the OSS and the proprietary models interchange their original market and production strategies. In the case of the OSS segment, market strategies becomes more business oriented; as a result, systems previously based solely on remote users/producers relations exchange some of the redundancy in its process in favour of a more businessdriven and coordinated production process. On the other hand, proprieta...},
	url = {ttp://pascal.case.unibz.it/handle/2038/1425},
	author = {De Prato, Giuditta and Gagliardi, Dimitri}
}
@article {flosswp202,
	title = {The Provision of a Public Good with a direct Provision Technology and Large Number of Agents},
	year = {2005},
	month = {January},
	abstract = {This paper provides a limit result for the provision of a public good in a mechanism design framework as the number of agents gets large. A canonical example for a public good that is produced with a direct provision technology is Open Source Software.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/behringer.pdf},
	author = {Stefan Behringer}
}
@conference {785,
	title = {Quality Improvement in Volunteer Free Software Projects: Exploring the Impact of Release Management},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {309-310},
	abstract = {Even though free software has achieved great popularity and success in recent years, there are a number of product quality challenges facing the open source development model. There is significant room for further quality improvement and one area that deserves special attention is release management. This research will identify problems with current release practices, verify possible advantages of an increasingly popular release model, and develop interventions to improve release management in free software projects. The research also aims to answer the fundamental question as to how volunteer projects can deliver predictable and high quality software.},
	keywords = {free software, open source, process improvement, quality assurance, release management, volunteer projects},
	url = {http://pascal.case.unibz.it/handle/2038/1429},
	author = {Martin Michlmayr}
}
@article {flosswp244,
	title = {Quality Practices and Problems in Free Software Projects},
	year = {2005},
	month = {July},
	abstract = {Free software and open source projects are often perceived to be of high quality. It has been suggested that the high level of quality found in some free software projects is related to the open development model which promotes peer review. While the quality of some free software projects is comparable to if not better than that of closed source software, not all free software projects are successful and of high quality. Even mature and successful projects face quality problems, some of which are related to the unique characteristics of free software and open source as a distributed development model based primarily on volunteers. In exploratory interviews performed with free software and open source developers, common quality practices as well as actual quality problems have been identified. The results of these interviews are presented in this paper to take stock of the current status of quality in free software projects and to act as a starting point for the implementation of quality process improvement strategies.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/michlmayr_hunt_probert-quality_practices_problems.pdf},
	author = {Martin Michlmayr}
}
@conference {745,
	title = {Quantifying the Interest in Open Source Systems: Case South-East Finland},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {192-195},
	abstract = {Open source systems (OSS) has emerged as one of the most interesting phenomena in software engineering today. Unfortunately, only little hard data is available to quantify the interest in OSS in commercially operating software houses. As a part of a local initiative to increase the alignment between the software industry and software engineering research and education, a state of the practice survey was conducted in the local software houses. Due to the globally recognized interest in OSS some explorative questions on the topic were included in the survey. The results of the survey indicate widespread interest in OSS in the industry, and even though the study had a strictly regional focus, the results provide quantitative support for future research on OSS.},
	url = {http://pascal.case.unibz.it/handle/2038/1434},
	author = {Nikula, Uolevi and Jantunen, Sami}
}
@conference {738,
	title = {Quantitative Analysis of Open Source Projects on SourceForge},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {140-147},
	abstract = {Relatively easy accessibility of high volumes of information about open source software makes it an interesting target for quantitative analysis meant to discover some hidden properties and trends of this software development model. In this work we demonstrate how such information can be acquired from the largest open source hosting facility {\textemdash} SourceForge {\textemdash} with nearly minimal effort. We compare our data with an identical data set collected a few months earlier by the OssMole [2] project, of which we were not aware at the time of performing the experiment, but which allowed us to make some interesting cross-comparisons and derive conclusions about temporal changes going on at SourceForge.},
	url = {http://pascal.case.unibz.it/handle/2038/1430},
	author = {Weiss, Dawid}
}
@conference {Williams:2005:RSS:1083142.1083144,
	title = {Recovering system specific rules from software repositories},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {7-11},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {One of the most successful applications of static analysis based bug finding tools is to search the source code for violations of system-specific rules. These rules may describe how functions interact in the code, how data is to be validated or how an API is to be used. To apply these tools, the developer must encode a rule that must be followed in the source code. The difficulty is that many of these system-specific rules are undocumented and "grow" over time as the source code changes. Most research in this area relies on expert programmers to document these little-known rules. In this paper we discuss a method to automatically recover a subset of these rules, function usage patterns, by mining the software repository. We present a preliminary study that applies our work to a large open source software project.},
	keywords = {function usage patterns, functions, source code, wine},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083144},
	url = {http://doi.acm.org/10.1145/1082983.1083144},
	attachments = {https://flosshub.org/sites/flosshub.org/files/7Recovering.pdf},
	author = {Williams, Chadd C. and Hollingsworth, Jeffrey K.}
}
@article {flosswp234,
	title = {Reputation in Open Source Software},
	year = {2005},
	month = {September},
	abstract = {The 1990s and early 2000s have seen the dramatic rise of open source software, with the Linux operating system as the most salient example. This article focuses on the role of reputation in open source. It describes the importance of the reputations of hackers, software vendors, open source projects, and the open source movement. Although reputation has long been used as an explanation of hacker motivation, this article applies the concept of reputation at multiple levels, and identifies the inter-level relations.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/watson.pdf},
	author = {Andrew Watson}
}
@conference {759,
	title = {Risk Assessment of an Open Source Migration Project},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {246-249},
	abstract = {In this paper we investigate the risks of an Open Source migration in the small Public Administration (PA) area. We consider not just technical risks (like security or reliability), but strategic issues (like e-government priorities, mid-term ownership cost items) and some social relations are also taken into consideration.},
	url = {http://pascal.case.unibz.it/handle/2038/1432},
	author = {Drozdik, Sylvester and Kov{\'a}cs, George L. and Kochis, P{\'a}l Zolt{\'a}n}
}
@conference {749,
	title = {A Risk Driven Framework for Open Source Information Systems Development},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {200-203},
	abstract = {This paper attempts to justify the need for a framework to address concerns with the use of open source software for information systems development (ISD). The premise of this argument is that the open source paradigm primarily addresses technical concerns while IS failures tend to be multifaceted in nature. OSS may improve but will not ultimately solve the problems of ISD due to its inherent sociotechnical complexities. Issues of concern for open source ISD are identified in this paper and a theoretical framework is outlined allowing organisations to take a more balanced approach to open source ISD. The framework is predicated upon risk management and a lifecycle that addresses social and organisational concerns throughout the ISD process. The objective of this framework is to aid in avoidance of the social and organisational pitfalls of ISD while leveraging the ability of the OSS paradigm to address software crisis issues. Finally, the implications of this framework a...},
	url = {http://pascal.case.unibz.it/handle/2038/617},
	author = {Conlon, Pat and Carew, Peter}
}
@conference {794,
	title = {SchoolTool: Defining Our Niche in the Open Source Architecture of Schools},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {334-337},
	keywords = {information system, open source, school, student},
	url = {http://pascal.case.unibz.it/handle/2038/1436},
	author = {Hoffman, Tom}
}
@conference {Hindle:2005:SFM:1083142.1083161,
	title = {SCQL: a formal model and a query language for source control repositories},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {100-104},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Source Control Repositories are used in most software projects to store revisions to source code files. These repositories operate at the file level and support multiple users. A generalized formal model of source control repositories is described herein. The model is a graph in which the different entities stored in the repository become vertices and their relationships become edges. We then define SCQL, a first order, and temporal logic based query language for source control repositories. We demonstrate how SCQL can be used to specify some questions and then evaluate them using the source control repositories of five different large software projects.},
	keywords = {evolution, file, gnumeric, modperl, openssl, revision, samba, scm, source code},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083161},
	url = {http://doi.acm.org/10.1145/1082983.1083161},
	attachments = {https://flosshub.org/sites/flosshub.org/files/100scql.pdf},
	author = {Hindle, Abram and Daniel M. German}
}
@article {flosswp232,
	title = {Seeking the Source: Software Source Code as a Social and Technical Artifact},
	year = {2005},
	month = {November},
	abstract = {In distributed software development, two sorts of dependencies can arise. The structure of the software system itself can create dependencies between software elements, while the structure of the development process can create dependencies between software developers. Each of these both shapes and reflects the development process. Our research concerns the extent to which, by looking uniformly at artifacts and activities, we can uncover the structures of software projects, and the ways in which development processes are inscribed into software artifacts. We show how a range of organizational processes and arrangements can be uncovered in software repositories, with implications for collaborative work in large distributed groups such as open source communities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/desouza.pdf},
	author = {De Souza, Cleidson and Jon Froehlich and Paul Dourish}
}
@conference {763,
	title = {Shared Source and Open Solutions: an e-Government Perspective},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {263-266},
	abstract = {Over the past four years, increasing commercialisation has been a significant influence on free and open source software. At the same time, the community based collaborative development model, which generally connotes open source, has also been studied and adopted by traditional software companies. These trends have led to an understanding that what separates open source from other software development approaches is the licensing model rather than the development model. Despite this, the two paradigms are rapidly starting to look very similar as open source is increasingly commercialised and established software companies integrate community based development into their value chain. This paper presents Microsoft{\textquoteright}s experience with its Intellectual Property Sharing programs and Shared Source Initiative. We also present the Solution Sharing Network, an environment that facilitates the sharing of solutions and best practices. We focus here on public sector customers who ...},
	url = {http://pascal.case.unibz.it/handle/2038/736},
	author = {Matusow, Jason and McGibbon, Stephen and Rowe, David}
}
@conference {802,
	title = {Sharing ExperienceS on Agile Methodologies in Open Source Software development SESAMOSS 2005},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {361},
	author = {Gabriele Gianini and Sillitti, Alberto}
}
@conference {Twidale:2005:SBF:1062455.1062468,
	title = {Silver bullet or fool{\textquoteright}s gold: supporting usability in open source software development},
	booktitle = {Proceedings of the 27th international conference on Software engineering},
	series = {ICSE {\textquoteright}05},
	year = {2005},
	pages = {35{\textendash}35},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {At first glance it can look like Open Source Software development violates many, if not all, of the precepts of decades of careful research and teaching in Software Engineering. One could take a classic SE textbook and compare the activities elaborated and advocated in the various chapters with what is actually done in plain sight in the public logs of an OSS project in say SourceForge. For a Professor of Software Engineering this might make for rather depressing reading. Are the principles of SE being rendered obsolete? Has OSS really discovered Brooks{\textquoteright} Silver Bullet? Or is it just a flash in the pan or Fool{\textquoteright}s Gold.In this talk I will mainly look at one aspect of Open Source Development, the {\textquoteright}problem{\textquoteright} of creating usable interfaces, particularly for non-technical end-users. Any approach involves the challenge of how to coordinate distributed collaborative interface analysis and design, given that in conventional software development this is usually done in small teams and almost always face to face. Indeed all the methods in any HCI text just assume same-time same-place work and don{\textquoteright}t map to distributed work, let alone the looser mechanisms of OSS development. Instead what is needed is a form of participatory usability involving the coordination of end users and developers in a constantly evolving redesign process.},
	keywords = {course project, education, lifecycle model, pedagogical, software engineering education, software process},
	isbn = {1-58113-963-2},
	doi = {10.1145/1062455.1062468},
	url = {http://doi.acm.org/10.1145/1062455.1062468},
	author = {Twidale, Michael}
}
@mastersthesis {43,
	title = {The social construction of freedom in free and open source software: Hackers, ethics, and the liberal tradition},
	volume = {PhD},
	year = {2005},
	school = {University of Chicago},
	type = {PhD Dissertation},
	address = {Chicago, Illinois},
	abstract = {This dissertation, based on fieldwork conducted between January 2001 and May 2003 on the Debian free software project and among hackers living in the Bay area, is an ethnography focused on the ethics and politics of free and open source hackers. My aim in this dissertation is to evaluate the rise of expressive rights among hackers as a historically and culturally specific practice of liberal freedom that can only be made sensible through the lens of a hacker technical way of life--in which their pragmatics and poetics are given serious consideration. Moving and integrating various levels of analysis: the phenomenology of technical praxis, the sociological creation of an ethical practice that unfolds in the hacker public sphere and the FOSS project, and the historical rise of reflective signification through overt political dissent, I offer a comprehensive account of how hackers have come to value and enact freedom, what they mean by it, and suggest some ideas about the broader political effects of their practices. Instead of an emphasis of self-determination and individuality based on the acquisition of property, hackers have placed emphasis on individuality as a form of critical self-determination that requires unrestricted access to knowledge in order to constantly develop technical skills and to progress the state of their technical art. Important for the purposes of this dissertation is that hackers challenge one sacred realm of liberal jurisprudence--intellectual property--by drawing on and reformulating ideals from another one--free speech.},
	keywords = {culture, hacker},
	author = {Coleman, E.G.}
}
@conference {717,
	title = {A Social Network Approach To Free/Open Source Software Simulation},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	note = {"Second, we use mailing list archives for three different projects. This gives us a more stringent network measure, since links are generated only when one developer communicates directly with another."
 
"The mailing lists were the developers list from a well deployed database server, the general list for an text and file processing library, and the general list for a smaller F/OSS web browser."},
	pages = {16-23},
	abstract = {Free and Open Source Software (F/OSS) development is a complex process that is just beginning to be understood. The actual development process is frequently characterized as disparate volunteer developers collaborating to create a piece of software. The developers of F/OSS, like most software engineers, spend a significant portion of their time fostering collaboration through various channels social communication. We have analyzed several methods of communication; a social networking site, project mailing lists, and developer weblogs; to gain an understanding of the social network structure behind F/OSS projects. This social network data was used to create a model of F/OSS development that allows for multiple projects, users, and developers with varying goals and socialization methods. Using this model we have been able to replicate some of the known phenomena observed in F/OSS and provide a first step in the creation of a robust model of F/OSS. },
	keywords = {email, mailing list, social network analysis},
	doi = {10.1.1.178.4984},
	url = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.178.4984},
	author = {Wagstrom, Patrick Adam and Herbsleb, James and Carley, Kathleen}
}
@article {84,
	title = {The social structure of Free and Open Source Software development},
	journal = {First Monday},
	volume = {10},
	number = {2},
	year = {2005},
	author = {Kevin Crowston and James Howison}
}
@article {springerlink:10.1007/s10606-005-9000-1,
	title = {Socialization in an Open Source Software Community: A Socio-Technical Analysis},
	journal = {Computer Supported Cooperative Work (CSCW)},
	volume = {14},
	year = {2005},
	note = {"I present the results of my analyses of participation patterns in a particular OSS project, used as a case study: Python. More precisely, I use the Open Source Project Browser to qualitatively track and analyze the trajectories of several project members who evolved (or not) into full-fledged participants. This allows me to later discuss how socialization proceeds in an OSS community such as Python"

"Over the course of 2002, I progressively retrieved the entire email archive of python-dev (the developers{\textquoteright} mailing list) and the CVS source tree for the project. "

"I read the entirety of the messages written by these participants and also looked at the software code they produced. There were striking similarities between their progressions over time, which I will de- scribe shortly. Overall the trajectory of these participants reflects successful socialization in Python: an evolution from newcomer to developer."

http://www2.parc.com/csl/members/nicolas/documents/JCSCW-OSS.pdf},
	pages = {323-368},
	publisher = {Springer Netherlands},
	abstract = {Open Source Software (OSS) development is often characterized as a fundamentally new way to develop software. Past analyses and discussions, however, have treated OSS projects and their organization mostly as a static phenomenon. Consequently, we do not know how these communities of software developers are sustained and reproduced over time through the progressive integration of new members. To shed light on this issue I report on my analyses of socialization in a particular OSS community. In particular, I document the relationships OSS newcomers develop over time with both the social and material aspects of a project. To do so, I combine two mutually informing activities: ethnography and the use of software specially designed to visualize and explore the interacting networks of human and material resources incorporated in the email and code databases of OSS. Socialization in this community is analyzed from two perspectives: as an individual learning process and as a political process. From these analyses it appears that successful participants progressively construct identities as software craftsmen, and that this process is punctuated by specific rites of passage. Successful participants also understand the political nature of software development and progressively enroll a network of human and material allies to support their efforts. I conclude by discussing how these results could inform the design of software to support socialization in OSS projects, as well as practical implications for the future of these projects.},
	keywords = {cvs, developers, email, email archive, mailing list, open source project browser, participation, python, scm, source code, team, tools},
	issn = {0925-9724},
	url = {http://dx.doi.org/10.1007/s10606-005-9000-1},
	author = {DUCHENEAUT, NICOLAS}
}
@conference {790,
	title = {	Socialization practices in FLOSS development teams},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {322-323},
	abstract = {Socialization of new members into Free/Libre Open Source Software (FLOSS) development teams is an important but little studied process in producing effective teams of this type. This is a dissertation proposal for a virtual ethnographic study that looks at the mechanisms and processes used to socialize new members into the team in order to help maintain a common group identity and focus.},
	keywords = {development team, FLOSS, member, open source, socialization},
	url = {http://pascal.case.unibz.it/handle/2038/1438},
	author = {Chengetai Masango}
}
@inbook {901,
	title = {Socio-Technical Interaction Networks in Free/Open Source Software Development Processes},
	booktitle = {Software Process Modeling},
	year = {2005},
	pages = {1-27},
	publisher = {Springer Science+Business Media Inc.},
	organization = {Springer Science+Business Media Inc.},
	address = {New York},
	author = {Walt Scacchi},
	editor = {Acu{\~n}a, S.T. and Juristo, N.}
}
@conference {Fielding:2005:SAO:1062455.1062474,
	title = {Software architecture in an open source world},
	booktitle = {Proceedings of the 27th international conference on Software engineering},
	series = {ICSE {\textquoteright}05},
	year = {2005},
	pages = {43{\textendash}43},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In spite of the hype and hysteria surrounding open source software development, there is very little that can be said of open source in general. Open source projects range in scope from the miniscule, such as the thousands of non-maintained code dumps left behind at the end of class projects, dissertations, and failed commercial ventures, to the truly international, with thousands of developers collaborating, directly or indirectly, on a common platform. One characteristic that is shared by the largest and most successful open source projects, however, is a software architecture designed to promote anarchic collaboration through extensions while at the same time preserving centralized control over the interfaces. This talk features a survey of the state-of-the-practice in open source development in regards to software architecture, with particular emphasis on the modular extensibility interfaces within several of the most successful projects, including Apache httpd, Eclipse, Mozilla Firefox, Linux kernel, and the World Wide Web (which few people recognize as an open source project in itself). These projects fall under the general category of collaborative open source software development, which emphasizes community aspects of software engineering in order to compensate for the often-volunteer nature of core developers and take advantage of the scalability obtainable through Internet-based virtual organizations.},
	keywords = {apache, collaborative open source development, eclipse, extensibility, Firefox, linux, linux kernel, loose coupling, modularity, mozilla, open source, software architecture},
	isbn = {1-58113-963-2},
	doi = {10.1145/1062455.1062474},
	url = {http://doi.acm.org/10.1145/1062455.1062474},
	author = {Roy T. Fielding}
}
@conference {Hawthorne:2005:SEE:1062455.1062581,
	title = {Software engineering education in the era of outsourcing, distributed development, and open source software: challenges and opportunities},
	booktitle = {Proceedings of the 27th international conference on Software engineering},
	series = {ICSE {\textquoteright}05},
	year = {2005},
	pages = {643{\textendash}644},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {As software development becomes increasingly globally distributed, and more software functions are delegated to common open source software (OSS) and commercial off-the-shelf (COTS) components, practicing software engineers face significant challenges for which current software engineering curricula may leave them inadequately prepared. A new multi-faceted distributed development model is emerging that effectively commoditizes many development activities once considered integral to software engineering, while simultaneously requiring practitioners to apply engineering principles in new and often unfamiliar contexts. We discuss the challenges that software engineers face as a direct result of outsourcing and other distributed development approaches that are increasingly being utilized by industry, and some of the key ways we need to evolve software engineering curricula to address these challenges.},
	keywords = {computer science education, contextual learning, education, informatics, software engineering education},
	isbn = {1-58113-963-2},
	doi = {10.1145/1062455.1062581},
	url = {http://doi.acm.org/10.1145/1062455.1062581},
	author = {Hawthorne, Matthew J. and Perry, Dewayne E.}
}
@conference {721,
	title = {Software Problem Management as Information Management in a F/OSS Development Community},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {44-49},
	abstract = {Bug reports created by a large, successful open source software development community show that software problem management (SWPM) is first of all information management and secondarily a problem solving activity. Solving software problems occurs only after a bug report, a first-class information object, has been created and {\textquotedblleft}triaged{\textquotedblright} by community members. One predominant structural feature of defect tracking repositories is the evolving "bug report network" (BRN). Community members create BRNs by progressively asserting various formal and informal relationships between bug reports (BRs). In one F/OSS bug repository under study, participants assert two formal relationships (duplications and dependencies) and various informal relationships (like "see also" references). BRNs can be interpreted as (1) information ordering strategies that support collocation of related BRs, decreasing cognitive and organizational effort; (2) sense-making strategies wherein BRNs provide mor...},
	url = {http://pascal.case.unibz.it/handle/2038/1533},
	author = {Sandusky, Robert J.}
}
@article {flosswp243,
	title = {Software Process Maturity and the Success of Free Software Projects},
	year = {2005},
	month = {October},
	abstract = {The success of free software and open source projects has increased interest in utilizing the open source model for mature software development. However, the ad hoc nature of open source development may result in poor quality software or failures for a number of volunteer projects. In this paper, projects from SourceForge are assessed to test the hypothesis that there is a relationship between process maturity and the success of free software and open source projects. This study addresses the question of whether the maturity of particular software processes differs in unsuccessful and unsuccessful projects. Processes are identified which are key factors in successful free software projects. The insights gained from this study can be used improve the software process used by free software projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/michlmayr1.pdf},
	author = {Martin Michlmayr}
}
@unpublished {flosswp216,
	title = {Some Economic \& Legal Aspects of Open Source Software},
	year = {2005},
	month = {May},
	abstract = {The emergence of open source software as a viable economic model has risen to the forefront in the debate on the future of the information technology industry. However, at first glance, the open source software development model is strikingly enigmatic and counterintuitive. To help better understand this phenomenon, this paper, through market data and economic theory, proceeds to ask and answer three related questions. First, what is the economic relationship between open source software development communities and proprietary software firms? Second, what are the resulting effects on market innovation and innovation incentives? And third, what legal mechanisms allow for the sustainability of open source software and should they be expanded or reduced? This paper concludes that open source activity appears to be generating four economic effects, whose net effect on innovation in the software market is ambiguous.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/frost.pdf},
	author = {Jonathon Frost}
}
@article {128,
	title = {Source code review systems},
	journal = {Ieee Software},
	volume = {22},
	number = {1},
	year = {2005},
	note = {Times Cited: 1},
	pages = {74-77},
	author = {Remillard, J.}
}
@conference {726,
	title = {Stimulating Collaborative Development in Operations Research with libOR},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {71-75},
	abstract = {In this paper we describe the development of libOR, an on-line library for the operations research (OR) community. The design and operation of this website is inspired by the Open Source movement and recent developments such as Wikipedia. In operations research, data sets are exchanged between researchers in order to test the performance of newly developed algorithms. Currently, the exchange of these data sets suffers from many problems. One of the main problems is that data sets are currently exchanged through a centrally maintained website, which makes it slow to respond to new developments. By applying an Open Source approach to content creation, we hope to spur the diffusion of information within the operations research community.},
	url = {http://pascal.case.unibz.it/handle/2038/1534},
	author = {Ven, Kris and S{\"o}rensen, Kenneth and Verelst, Jan and Sevaux, Marc}
}
@conference {899,
	title = {Stopping spyware at the gate: a user study of privacy, notice and spyware},
	booktitle = {2005 Symposium on Usable Privacy and Security},
	year = {2005},
	month = {07/2005},
	pages = {43-52},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Pittsburgh, PA},
	keywords = {agreement,, and, Aspects,, Design,, end, EULA,, Experimentation,, Factors,, Human, Legal, license, notice,, of, privacy,, security, service,, spyware,, terms, ToS,, usability,, user},
	isbn = {1-59593-178-3 },
	author = {N. Good and Dhamija, R. and J. Grossklags and D. Thaw and Aronowitz, S. and D. Mulligan and J. Konstan}
}
@conference {716,
	title = {A structurational perspective on leadership in Free/Libre Open Source Software teams},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {9-15},
	abstract = {In this conceptual paper, we present a structuration- based theory of leadership behaviours in self-organizing distributed teams such as Free/Libre Open Source Software development teams. Such teams are often composed of members of relatively equal status or who are so disparate in background that formal organizational status seems irrelevant, reducing the usual leadership cues provided by organizational status and title. Building on a functional view of leadership and structuration theory, we suggest that leaders are individuals who develop team structures that then guide the actions of team members. Specifically, we examine structures of signification in the form of shared mental models, structures of domination in the form of role structures and structures of legitimation in form of rules and norms. The main contribution of our paper is the integration of various social theories to describe emergent leadership behaviours in distributed teams. We develop a set of prop...},
	url = {http://pascal.case.unibz.it/handle/2038/623},
	author = {Kevin Crowston and Robert Heckman and Hala Annabi and Chengetai Masango}
}
@conference {788,
	title = {Structure, Cohesion, and Open Source Software Success},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {317-319},
	abstract = {This paper proposes a dissertation designed to understand how the open source software (OSS) development group and its associated interest community jointly and independently impact OSS success for a single OSS project.},
	keywords = {interest community, network externalities, open source software, software quality},
	url = {http://pascal.case.unibz.it/handle/2038/1536},
	author = {Sherae Daniel}
}
@conference {737,
	title = {A Successful Business Model for Free Software},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {135-139},
	abstract = {The objective of this article is to offer a return on experience explaining how the legal fundamentals on which Free Software is based allow for a long-lasting business model based on a special kind of expert knowledge-based support that benefits customers and guarantees the creation of a local pool of expertise. This article is based on our experience with GNAT Pro. GNAT Pro is the Free Software development environment for the Ada 95 programming language. It comprises a compiler that is part of GCC (the GNU Compiler Collection), a toolset and graphical Integrated Development Environment, and a set of supporting libraries. Developing, maintaining, and marketing GNAT Pro for ten years have provided significant experience with both technical and non-technical aspects of Free Software. This article summarizes the principal legal and business lessons learned.},
	url = {http://pascal.case.unibz.it/handle/2038/627},
	author = {Ayre, Jamie and Gasperoni, Franco}
}
@article {flosswp230,
	title = {A Techno-Feminist Perspective on the Free/Libre Open Source Software Development},
	year = {2005},
	month = {August},
	abstract = {This paper tries to analyse the FLOSS development from a "techno-feminist" perspective (Wajcman 2004). Staying away from a reductionism that simplifies the gender issue in the FLOSS community to the level of a fight between men and women, the issues I attempt to address include not only the inequality that women face in computing, but also other inequalities that other users face mainly emerging from the power relationships between expert and lay (namely, developer and user) in software design. Instead of splitting women and men in the FLOSS development, this analysis helps motivate both men and women to work together, reduce the gender gap, and improve the disadvantaged statuses of women and a wider users community in the FLOSS development.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin5.pdf},
	author = {Yu-wei Lin}
}
@article {flosswp296,
	title = {Thematic Coherence and Quotation Practices in Open Source Software design-oriented online discussions},
	journal = {Group {\textquoteright}05 Conference Proceedings},
	year = {2005},
	month = {November},
	publisher = {ACM},
	abstract = {This paper presents an analysis of online discussions in Open Source Software (OSS) design. The objective of our work is to understand and model the dynamics of OSS design that take place in mailing list exchanges. We show how quotation practices can be used to locate design relevant data in discussion archives. OSS developers use quotation as a mechanism to maintain the discursive context. To retrace thematic coherence in the online discussions of a major OSS project, Python, we follow how messages are linked through quotation practices. We compare our quotation-based analysis with a more conventional analysis: a thread-based of the reply-to links between messages. The advantages of a quotation-based analysis over a thread-based analysis are outlined. Our analysis reveals also the links between the social structure and elements in the discussion space and how it shapes influence in the design process.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Barcellinietal.pdf},
	author = {F. Barcellini and F. Detienne and J. M. Burkhardt and W. Sack}
}
@article {swire2005theory,
	title = {A Theory of Disclosure for Security and Competitive Reasons: Open Source, Proprietary Software, and Government Systems},
	journal = {Hous. L. Rev.},
	volume = {42},
	year = {2005},
	pages = {1333},
	publisher = {HeinOnline},
	abstract = {A previous article, {\textquotedblleft}A Model for When Disclosure Helps Security: What is
Different about Computer and Network Security?{\textquotedblright} proposed a model for
when disclosure helps or hurts security and provided reasons why computer
security is often different in this respect than physical security.
 This chapter provides a general approach for describing the incentives of actors to
disclose information about their software or systems. A chief point of this
chapter is that the incentives of disclosure depend on two largely independent
assessments: (i) the degree to which disclosure helps or hurts security},
	keywords = {security},
	attachments = {https://flosshub.org/sites/flosshub.org/files/KP21\%2003\%20Swire.pdf},
	author = {Swire, Peter P}
}
@booklet {513,
	title = {The Theory Of FOSS And Its Acceptance In Developing Nations},
	year = {2005},
	abstract = {Free and Open Source Software (FOSS) is on the march across the globe, and it offers a reliable alternative to proprietary, commercial products and addresses the full range of users{\textquoteright} needs. For example FOSS Apache provides the majority of web pages due to its huge installed user base, with the last figures showing Apache occupying 67\% of all web sites world wide.

Since FOSS is world class, (i.e. it is free to share/distribute amongst individuals, clients, offices, etc.) and can be modified according to an individual{\textquoteright}s/organization{\textquoteright}s motives, it may be viewed as a competitor to proprietary and commercial products. For instance, when compared to the existing standard, user-friendly programs that run on Microsoft Windows and Apple operating systems, FOSS offers alternate operating systems that can be used on all computer systems and a range of Internet server software with advanced functionality.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FOSS_IN_POLITICS.pdf},
	author = {Shiyevina Amelia Abdool}
}
@conference {720,
	title = {Towards an Open Source Development Process - Evaluating the Migration to an Open Source Project by Means of the Capability Maturity Model},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {37-43},
	abstract = {In this paper we review the ongoing development of a Web-based community system that has been migrated from a closed software development to an open source project. We identify three different phases in the migration process where the development process changed significantly. We analyse these phases by means of the Capability Maturity Model (CMM). The insights gained show the implications of such a migration process towards open source concerning the process quality of a development process. They also show underlying assumptions of the CMM that do not totally match with developments in this specific case study. As a helpful outcome, our reflection about the ongoing software development process helped identify two crucial factors: reflection about the process is possible even at lower levels and how to handle people{\textquoteright}s fluctuation to sustain a development project.},
	url = {http://pascal.case.unibz.it/handle/2038/1543},
	author = {Bleek, Wolf-Gideon and Finck, Matthias and Pape, Bernd}
}
@conference {782,
	title = {Towards Supporting Agile Practice Within The Libre Software Paradigm},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {303-304},
	abstract = {Individual agile methods have never been practiced as defined, in the same way that Royce{\textquoteright}s waterfall [1] model never reflected actual practice. Instead, practitioners adapted the core principles of these processes in order to suit their needs. Understanding this is key to appreciating the agile mindset. What does exist is a set of principles1 which, when followed loosely, form the agile practices. It is an important part of the agile mentality that the individuals within a project are more important that the process they follow. However, the individual methods do have their own identifying features that make them unique; for example testing must be performed before coding within eXtreme Programming (XP) [2]. However, if practitioners were to apply XP, exactly as Beck describes it, then they are probably not {\textquotedblleft}doing agile{\textquotedblright} as they may not be following the process that suits their needs best. One of the interesting features of the XP method is its requirement of a collocated team. Th...},
	keywords = {agile methods, agile practice, extreme programming, libre software, open source, XP},
	url = {http://pascal.case.unibz.it/handle/2038/1546},
	author = {Adams, Paul and Boldyreff, Cornelia}
}
@conference {797,
	title = {Transfering Libre Software Development Practices to the Production of Educational Resources: the Edukalibre Project},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {341-348},
	abstract = {The transfer of methodologies common in libre (free, open source) sofware development to the domain of educational resources can radically change the way educational content is developed and used, enabling both educational practitioners and students to become actively involved in its creation and distribution. New software architectures and tools are needed to effectively support this process. This paper describes a platform aimed to support the creation of free, collaboratively constructed educational content on the web, which has been developed within the Edukalibre project. It provides easy access to core technologies: a control version system combined with conversion tools to produce several convenient formats for each document. Its modular architecture offers many different interfaces to the users. The Edukalibre platform is distributed as libre software.},
	keywords = {educational resources, information systems, open source, software development practices},
	url = {http://pascal.case.unibz.it/handle/2038/1548},
	author = {Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Chris Tebb and Vania Dimitrova and Chaparro, Diego and Romera, Teo}
}
@article {flosswp246,
	title = {Two-sided competition of proprietary vs. open source technology platforms and the implications for the software industry},
	year = {2005},
	month = {October},
	abstract = {Technology platforms, such as Microsoft Windows, are the hubs of technology industries. We develop a framework to characterize the optimal two-sided pricing strategy of a platform firm, that is, the pricing strategy towards the direct users of the platform as well as towards firms offering applications that are complementary to the platform. We compare industry structures based on a proprietary platform (such as Windows) with those based on an open-source platform (such as Linux) and analyze the structure of competition and industry implications in terms of pricing, sales, profitability, and social welfare. We find that, when the platform is proprietary, the equilibrium prices for the platform, the applications, and the platform access fee for applications may be below marginal cost, and we characterize demand conditions that lead to this. The proprietary applications sector of an industry based on an open source platform may be more profitable than the total profits of a proprietary platform industry. When users have a strong preference for application variety, the total profits of the proprietary industry are larger than the total profits of an industry based on an open source platform. The variety of applications is larger when the platform is open source. When a system based on an open source platform with an independent proprietary application competes with a proprietary system, the proprietary system is likely to dominate the open source platform industry both in terms of marketshare and profitability. This may explain the dominance of Microsoft in the market for PC operating systems.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/economideskatsamakas2.pdf},
	author = {Nicholas Economides and Evangelos Katsamakas}
}
@conference {776,
	title = {Un{\textquoteright}applicazione Open Source: l{\textquoteright}Osservatorio sull{\textquoteright}e-government e la societ{\`a} dell{\textquoteright}informazione},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {291-293},
	abstract = {I processi d{\textquoteright}innovazione, conseguenza dei progetti di e-government, che da alcuni anni interessano gli EELL, possono essere apprezzati solo se osservati nella loro veste di azioni integrate comuni a pi{\`u} soggetti. Predisporre uno strumento logico-tecnologico che colmi le carenze informative e che sia di supporto, alle amministrazioni territoriali, in sede di programmazione e pianificazione delle politiche {\`e} quanto si {\`e} sperimentato in Regione Emilia-Romagna. Sono stati cos{\`\i} realizzati una banca dati ed un applicativo web-based, entrambi basati su componenti software Open Source. Tale scelta {\`e} stata dettata dalla volont{\`a} di diffondere e facilitare questa pratica in altre realt{\`a} territoriali. Questo esperimento, oramai attivit{\`a} consolidata, ha prodotto risultati informativi per il territorio regionale ed {\`e} punto di partenza per un{\textquoteright}evoluzione su scala nazionale.},
	url = {http://pascal.case.unibz.it/handle/2038/1550},
	author = {Tartari, Dimitri}
}
@conference {Neamtiu:2005:USC:1083142.1083143,
	title = {Understanding source code evolution using abstract syntax tree matching},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {2-6},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Mining software repositories at the source code level can provide a greater understanding of how software evolves. We present a tool for quickly comparing the source code of different versions of a C program. The approach is based on partial abstract syntax tree matching, and can track simple changes to global variables, types and functions. These changes can characterize aspects of software evolution useful for answering higher level questions. In particular, we consider how they could be used to inform the design of a dynamic software updating system. We report results based on measurements of various versions of popular open source programs, including BIND, OpenSSH, Apache, Vsftpd and the Linux kernel.},
	keywords = {abstract syntax trees, apache, bind, evolution, linux, openssh, software evolution, source code, source code analysis, vsftpd},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083143},
	url = {http://doi.acm.org/10.1145/1082983.1083143},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2Understanding.pdf},
	author = {Neamtiu, Iulian and Foster, Jeffrey S. and Hicks, Michael}
}
@conference {739,
	title = {Understanding the Open-Source Software Development Process: a Case Study with CVSChecker},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {154-161},
	abstract = {The open-source process model is emerging as a new lightweight paradigm for software development and has already produced several successful products. This process is fundamentally different from more traditional analysis- and design-driven processes, which raises a set of interesting research questions: what activities are carried out in open-source projects and by whom? Are there typical or exceptional patterns? CVSChecker is a tool designed to analyze the performance of individual developers and the work-distribution patterns of teams based on historical source-code repository data. In this paper, we report on a case study conducted using CVSChecker to examine a small open-source project. We discuss the insights that the CVSChecker analysis produced regarding this project and compare them to results from previous case studies performed with senior student teams.},
	url = {http://pascal.case.unibz.it/handle/2038/1551},
	author = {Liu, Ying and Stroulia, Eleni and Erdogmus, Hakan}
}
@conference {783,
	title = {Unreliable Collaborators: Coordination in distributed volunteer teams},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {305-306},
	abstract = {Drawing together the interest, skills and resources of individuals to pursue productive activity is the cornerstone of wealth creation. Recently, new forms of productive activity have emerged that draw together highly motivated, often volunteer, participants to collaborate through low-cost information systems to produce high quality products that rival those produced by wealthy firms and markets. Examples include free (libr{\^A}{\textasciiacute}e) and open source software (FLOSS), such as Linux, and collaboratively edited texts, such as Wikipedia and the Open Directory. There is an opportunity to study these novel activities, to understand their organization, in order to both further their continued success and to assess whether and which of their novel organization techniques might be used in wider domains of human collaborative activity.},
	keywords = {coordination, floss organization, MOTIVATION, open source, volunteer teams},
	url = {http://pascal.case.unibz.it/handle/2038/1552},
	author = {Howison, James}
}
@conference {Kim:2005:UCG:1083142.1083146,
	title = {Using a clone genealogy extractor for understanding and supporting evolution of code clones},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {17-23},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Programmers often create similar code snippets or reuse existing code snippets by copying and pasting. Code clones {\textemdash}syntactically and semantically similar code snippets{\textemdash}can cause problems during software maintenance because programmers may need to locate code clones and change them consistently. In this work, we investigate (1) how code clones evolve, (2) how many code clones impose maintenance challenges, and (3) what kind of tool or engineering process would be useful for maintaining code clones.
Based on a formal definition of clone evolution, we built a clone genealogy tool that automatically extracts the history of code clones from a source code repository (CVS). Our clone genealogy tool enables several analyses that reveal evolutionary characteristics of code clones. Our initial results suggest that aggressive refactoring may not be the best solution for all code clones; thus, we propose alternative tool solutions that assist in maintaining code clones using clone genealogy information.},
	keywords = {clone, clone detection, cvs, developers, evolution, maintenance, refactoring, source code},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083146},
	url = {http://doi.acm.org/10.1145/1082983.1083146},
	attachments = {https://flosshub.org/sites/flosshub.org/files/17Using.pdf},
	author = {Kim, Miryung and Notkin, David}
}
@conference {742,
	title = {Using Open Source Middleware for Securing e-Gov Applications},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {172-178},
	abstract = {Nowadays, a global information infrastructure connects remote parties through the use of large scale networks, and many companies focus on developing e-services based on remote resources and on interaction between remote parties. In such a context, e-Government (e-Gov) systems became of paramount importance for the Public Administration, and many ongoing development projects are targeted on their implementation and release. For open source software to play an important role in this scenario, two main technological requirements must be fulfilled: (i) the identification and optimization of de facto standards for building e-Gov open source software components and (ii) a standard integration strategy of these components into an open source middleware layer, capable of conveying a completely open-source e-Gov solution. In this paper, we argue that e-Gov systems should be constructed on a open source middleware layer, providing full public responsibility in its development. W...},
	url = {http://pascal.case.unibz.it/handle/2038/1553},
	author = {Ardagna, Claudio Agostino and Damiani, Ernesto and Frati, Fulvio and Montel, Martin}
}
@conference {724,
	title = {Using Open Source Tools to Support Collaboration Within CALIBRE},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {61-65},
	abstract = {This paper describes the deployment of Plone, an Open-Source content management system, to support the activities of CALIBRE, an EU-funded coordination action integrating research into Libre software. The criteria by which Plone was selected are described, and the goodness of fit to these criteria is analysed. As a coordination action, CALIBRE involves 12 partners with different requirements and characteristics. The CALIBRE Working Environment (CWE) must therefore support a variety of users with different levels of technical expertise and expectations. Implementation of the support infrastructure for CALIBRE is ongoing, and has provided some interesting insights into the benefits of the use of libre software. Although Plone has not been explicitly developed as a collaboration infrastructure, with its wealth of plugins, it has proven highly adaptable for this purpose.},
	url = {http://pascal.case.unibz.it/handle/2038/1555},
	author = {Adams, Paul and Nutter, David and Rank, Stephen and Boldyreff, Cornelia}
}
@conference {778,
	title = {Using Plone To Support Collaborative Research},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {296-297},
	keywords = {collaboration environment, collaborative research, content management system, open source, plugin},
	url = {http://pascal.case.unibz.it/handle/2038/1558},
	author = {Adams, Paul and Nutter, David and Rank, Stephen and Boldyreff, Cornelia}
}
@conference {744,
	title = {Using the Iterated Prisoner{\textquoteright}s Dilemma for Explaining the Evolution of Cooperation in Open Source Communities},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {186-191},
	abstract = {Software development, and especially open source projects, typically involve repeated interactions between participants and groups of participants. We propose to analyse this situation by means of the standard model for the evolution of cooperation, the iterated prisoner{\textquoteright}s dilemma. The prisoner{\textquoteright}s dilemma is a well-known model for a two-person game, in which each side can choose to either cooperate or defect, and in which the payoffs are arranged in a defined hierarchy (e.g. the highest payoff is achieved by defecting while the other player cooperates). As a first step, the prisoner{\textquoteright}s dilemma needs to be formulated for the open source development model, i.e. what constitutes cooperation, playing defect and payoffs. Then, computer simulations using a population of stochastic reactive strategies can be applied, using a strategy{\textquoteright}s payoff as fitness measure for determining its frequency in the next generation. As a further extension, the effects of misinterpretation of other...},
	url = {http://pascal.case.unibz.it/handle/2038/1559},
	author = {Eckert, Daniel and Koch, Stefan and Mitl{\"o}hner, Johann}
}
@conference {727,
	title = {Virtual Square},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {76-81},
	abstract = {It is common to call {\textquotedblleft}virtual world{\textquotedblright} the set of abstractions given to humans by computers and networks. When the computers and the networks are emulated by programs, i.e. are virtual machines and virtual networks, there is one more layer of virtuality: a kind of virtual squared world. Virtual square (V{\texttwosuperior}) is the project to study how to exploit the possibilities given by multi layered virtuality. V{\texttwosuperior} integrates the existing technologies in system emulation with a new overlay network that is able to integrate virtual machines, real computers and processes. The virtual networking infrastructure, the educational virtual machine uMPS and the user level network virtual machine Ale4NET are original contributions made by this project. All the code developed for Virtual Square as well as all the code of the other virtual machines presented here have been released as Open Source or Free Software.},
	url = {http://pascal.case.unibz.it/handle/2038/1560},
	author = {Davoli, Renzo}
}
@article {flosswp206,
	title = {Webservice Protocol Design for Economic Liberty and Observability},
	year = {2005},
	month = {March},
	abstract = {One big potential benefit of the webservices paradigm is in reducing the costs of inter-firm business transactions. That should allow small and medium-sized enterprises to compete successfully with big firms. This paper considers specifically the economic needs of peer-to-peer business alliances, defined as multiparty business alliances which are not under the control of any single firm or any small group of alliance members, so that each participating firm has full economic liberty. This organisational form is appropriate for example for Free Software businesses. The main conclusions are that achieving economic observability of business transactions is of great importance, and that this is difficult to achieve with the Remote Procedure Calls paradigm of JINI or XML / HTTP / SOAP based webservices. The problem can be overcome by using the SXDF / QQP / QRPC suite of webservice protocols,},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bollow.pdf},
	author = {Norbert Bollow}
}
@conference {799,
	title = {What is the significance of Open Source Software for the education and training community?},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {353-358},
	abstract = {There is growing interest in the education community in the development and use of Open Source Software. This paper explains the ideas behind OSS and how what its significance is for education. It examines regional and national initiatives to promote the use of OSS. The paper considers the advantages of OSS and potential problems. It goes on to look at the idea of open content and the sharing of learning content, and provides short case studies. The paper concludes that the major significance of OSS and open content is in the new social relations engendered and in fostering innovation in e-learning, both in application development and new pedagogies.},
	keywords = {economic issues, education, open source, pedagocic impact, training},
	url = {http://pascal.case.unibz.it/handle/2038/1563},
	author = {Attwell, Graham}
}
@conference {Sliwerski:2005:CIF:1083142.1083147,
	title = {When do changes induce fixes?},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {24-28},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {As a software system evolves, programmers make changes that sometimes cause problems. We analyze CVS archives for fix-inducing changes{\textemdash}changes that lead to problems, indicated by fixes. We show how to automatically locate fix-inducing changes by linking a version archive (such as CVS) to a bug database (such as BUGZILLA). In a first investigation of the MOZILLA and ECLIPSE history, it turns out that fix-inducing changes show distinct patterns with respect to their size and the day of week they were applied.},
	keywords = {bugzilla, change analysis, cvs, eclipse, evolution, mozilla},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083147},
	url = {http://doi.acm.org/10.1145/1082983.1083147},
	attachments = {https://flosshub.org/sites/flosshub.org/files/24WhenDoChanges.pdf},
	author = {Sliwerski, J and Zimmermann, Thomas and Zeller, Andreas}
}
@article {flosswp1738,
	title = {Why and how-to contribute to libre software when you integrate them into an in-house application ?},
	journal = {Proceedings of the 1st International Conference on Open Source Systems},
	year = {2005},
	month = {June},
	pages = {113{\textendash}118},
	abstract = {Free or open source software are common tools that everybody can use and customise at its convenience to create in-house applications. Using and customising free software is not sufficient to ensure that this in-house application will be maintainable at mid or long term. This paper draws lessons from our in-house project, the development of a groupware Web platform for researchers, to help defining a policy through which efficient contributions can be made to open source software so that the in-house projects may remain viable.},
	author = {Christian Bac and Olivier Berger and V{\'e}ronique Deborde and Benoit Hamet}
}
@inbook {53,
	title = {Why hackers do what they do: Understanding motivation and effort in free/open source software projects},
	booktitle = {Perspectives on Free and Open Source Software},
	year = {2005},
	publisher = {MIT Press},
	organization = {MIT Press},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lakhaniwolf.pdf},
	author = {Karim R Lakhani and Wolf, R.},
	editor = {Feller, J. and Fitzgerald, Brian and Hissam, S. and Karim R Lakhani}
}
@conference {801,
	title = {Workshop on "Open Source and Multimedia"},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {360},
	author = {Julien Bourgeois and Fran{\c c}ois Spies and Dodero, Gabriella and Vittoria Gianuzzi}
}
@article {flosswp193,
	title = {Advancing Economic Research on the Free and Open Source Software Mode of Production},
	year = {2004},
	month = {December},
	abstract = {Early contributions to the academic literature on free/libre and open source software (F/LOSS) movements have been directed primarily at identifying the motivations that account for the sustained and often intensive involvement of many people in this non-contractual and unremunerated productive activity. This issue has been particularly prominent in economists{\textquoteright} contributions to the literature, and it reflects a view that widespread voluntary participation in the creation of economically valuable goods that is to be distributed without charge constitutes a significant behavioral anomaly. Undoubtedly, the motivations of F/LOSS developers deserve to be studied more intensively, but not because their behaviors are unique, or historically unprecedented. In this essay we argue that other aspects of the "open source" phenomenon are just as intriguing, if not more so, and possibly are also more consequential topics for economic analysis. We describe the re-focusing and re-direction of empirical and theoretical research in an integrated international project (based at Stanford University/SIEPR) that aims at better understanding a set of less widely discussed topics: the modes of organization, governance and performance of F/LOSS development {\textendash} viewed as a collective distributed mode of production.. We discuss of the significance of tackling those questions in order to assess the potentialities of the "open source way of working" as a paradigm for a broader class of knowledge and information-goods production, and conclude with proposals for the trajectory of future research along that line.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/davidetal.pdf},
	author = {Jean-Michel Dalle}
}
@article {flosswp175,
	title = {Applying Social Network Analysis to the Information in CVS Repositories},
	year = {2004},
	month = {June},
	abstract = {The huge quantities of data available in the CVS repositories of large, long-lived libre (free, open source) software projects, and the many interrelationships among those data offer opportunities for extracting large amounts of valuable information about their structure, evolution and internal processes. Unfortunately, the sheer volume of that information renders it almost unusable without applying methodologies which highlight the relevant information for a given aspect of the project. In this paper, we propose the use of a well known set of methodologies (social network analysis) for characterizing libre software projects, their evolution over time and their internal structure. In addition, we show how we have applied such methodologies to real cases, and extract some preliminary conclusions from that experience.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/llopez-sna-short.pdf},
	author = {Luis Lopez}
}
@booklet {Lopez-Fernandez_applyingsocial,
	title = {Applying Social Network Analysis to the Information in CVS Repositories},
	howpublished = {International Workshop on Mining Software Repositories (MSR 2004)},
	year = {2004},
	pages = {101-105},
	abstract = {The huge quantities of data available in the CVS repositories of large, long-lived libre (free, open source) software projects, and the many interrelationships among those data offer opportunities for extracting large amounts of valuable information about their structure, evolution and internal processes. Unfortunately, the sheer volume of that information renders it almost unusable without applying methodologies which highlight the relevant information for a given aspect of the project. In this paper, we propose the use of a well known set of methodologies (social network analysis) for characterizing libre software projects, their evolution over time and their internal structure. In addition, we show how we have applied such methodologies to real cases, and extract some preliminary conclusions from that experience.},
	keywords = {apache, complex networks, cvs, gnome, kde, libre software engineering, source code, source code repositories, visualization techniques, vizualization},
	attachments = {https://flosshub.org/sites/flosshub.org/files/101ApplyingSocial.pdf},
	author = {L{\'o}pez-Fern{\'a}ndez, L. and Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@article {flosswp143,
	title = {Appropriating the Commons: Firms in Open Source Software},
	year = {2004},
	month = {April},
	abstract = {Firms in open source software (OSS) are active in a field encompassing all the characteristics of a public good, given the non-excludability and non-rivalry nature of OSS. As the case of OSS demonstrates, the fact that many important inputs to the innovative process are public should not be taken to mean that innovators are prevented from capturing private returns. The objective of this paper is to explore how firms appropriate returns from innovations that are created outside the boundaries of firms and in the public domain using the case of OSS. To do so, the paper draws upon an explorative multiple case study of six small firms that attempt to appropriate returns from OSS, with rich empirical evidence from various data sources. The cases illustrate how firms try a variety of approaches to appropriate adequate returns and that selling services seem to be the dominant trend. Firm also balance the relative inefficiency of traditional means of intellectual property right such as patents by putting greater emphasis on first mover advantages and creating network externalities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dahlander2.pdf},
	author = {Linus Dahlander}
}
@article {flosswp138,
	title = {The Architecture of Cooperation: How Code Architecture Mitigates Free Riding in the Open Source Development Model},
	year = {2004},
	month = {January},
	abstract = {We argue that the architecture of a codebase is a critical factor that lies at the heart of the open source development process. To support this argument, we define two observable properties of an architecture: (1) its modularity and (2) its option values. Developers can make informed judgments about modularity and option value from early code releases. Their judgments in turn will influence their decisions to work and to contribute their code back to the community. We go on to suggest that the core of the open source development process can be thought of as two linked games played within a codebase architecture. The first game involves the implicit exchange of effort directed at the modules and option values of a codebase; the second is a Prisoners{\textquoteright} Dilemma game triggered by the irreducible costs of communicating. The implicit exchange of effort among developers is made possible by the the non-rivalrous nature of the codebase and by the modularity and option values of the codebase{\textquoteright}s architecture. This exchange creates value for all participants, both workers and free-riders. In contrast, the Prisoners{\textquoteright} Dilemma is a problem that must be surmounted if the exchanges are to take place. It can be addressed through a combination of reducing the costs of communication, providing rewards, and encouraging repeated interactions. Finally, the initial design and "opening up" of a codebase can be seen as a rational move by an architect who is seeking to test the environment in hopes of initiating exchanges of effort with other developers.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/baldwinclark.pdf},
	author = {Carliss Baldwin}
}
@conference {1052,
	title = {Bug driven bug finders},
	booktitle = {Proceedings of the 2004 international workshop on Mining software repositories  - MSR {\textquoteright}04},
	volume = {2004},
	year = {2004},
	pages = {70 - 74},
	publisher = {IEE},
	organization = {IEE},
	address = {Edinburgh, Scotland, UK},
	abstract = {We describe a method of creating tools to find bugs in software that is driven by the analysis of previously fixed bugs. We present a study of bug databases and software repositories that characterize commonly occurring types of bugs.	Based on the types of bugs that were commonly reported and fixed in the code, we determine what types of bug finding tools should be developed. We have implemented one static checker, a return value usage checker. Novel features of this checker include the use of information from the software repository to try to improve its false positive rate by identifying patterns that have resulted in previous bug fixes.},
	keywords = {apache, bug tracking, bugs},
	doi = {10.1049/ic:20040479},
	attachments = {https://flosshub.org/sites/flosshub.org/files/70BugDrivenBug.pdf},
	author = {Williams, C.C. and Hollingsworth, J.K.}
}
@proceedings {905,
	title = {Collaboration, Leadership, Control, and Conflict Negotiation in the NetBeans.org Community},
	year = {2004},
	month = {May 25},
	address = {Edinburgh, Scotland, UK},
	keywords = {netbeans},
	attachments = {https://flosshub.org/sites/flosshub.org/files/jensen.pdf},
	author = {Chris Jensen and Walt Scacchi}
}
@proceedings {1191,
	title = {Collaboration, Leadership, Control, and Conflict Negotiation in the Netbeans.org Community},
	year = {2004},
	pages = {48-52},
	abstract = {Large open source software development communities are quickly learning that, to be successful, they must integrate efforts not only among the organizations investing developers within the community and unaffiliated volunteer contributors, but also negotiate relationships with external groups hoping to sway the social and technical direction of the community and its products. Leadership and control sharing across organizations and individuals in and between communities are common sources of conflict. Such conflict often leads to breakdowns in collaboration. This paper seeks to explore the negotiation of these conflicts, collaborative efforts, and leadership and control structures in the Netbeans.org community.},
	keywords = {conflict, leadership, netbeans},
	attachments = {https://flosshub.org/sites/flosshub.org/files/jensen_0.pdf},
	author = {Chris Jensen and Walt Scacchi}
}
@article {flosswp221,
	title = {The Collaborative Integrity of Open-Source Software},
	year = {2004},
	month = {August},
	abstract = {This Article analyzes legal protection for open-source software by comparing it to the venerable civil law tradition of moral rights. The comparison focuses on the moral right of integrity, with which one may object to mutilations of her work, even after having parted with the copyright and the object that embodies the work. The parallel apparatus in open-source licensing is conditional permission to use a copyrighted work. The conditions include that source code be available and that software use be royalty-free. These conditions facilitate open-source collaborative software development. At the heart of both systems is the right for creators to control the view that a work presents. In the open-source system, this is the Collaborative Integrity of open-source software. The history and legacy of moral rights help us better understand Collaborative Integrity in open-source software. The right of integrity in some international jurisdictions may apply to software, thus raising questions whether it hurts or helps open-source software. Building from these insights, this Article evaluates whether the Collaborative Integrity in open-source software deserves protection as a separate right, just as the right of integrity developed separately from pecuniary copyright in civil law jurisdictions.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/vetter1.pdf},
	author = {Greg R Vetter}
}
@proceedings {1188,
	title = {Communication and Conflict Issues in Collaborative Software Research Projects},
	year = {2004},
	pages = {14-17},
	abstract = {The Open Source Component Artefact Repository (OSCAR) was developed under the auspices of the GENESIS project to store data produced during the software development process. Significant problems were encountered during the course of the project in both the development itself and management of the project. The reasons for and potential solutions to these problems are examined with the intention of developing a set of guidelines to enable participants in other collaborative projects to avoid these pitfalls.
We wish to make it clear that we attach no opprobrium to any of the participants in the GENESIS project as many of the issues we outline below have solutions only visible with hindsight. Instead, we seek to provide a fair-minded critique of our role and the mistakes we made in a fairly typical two-year EU research project, and to provide a set of recommendations for other similar projects, in order that they can (attempt to) avoid suffering similarly.},
	keywords = {artefact, cvs, genesis, oscar},
	attachments = {https://flosshub.org/sites/flosshub.org/files/boldyreff15-18.pdf},
	author = {Boldyreff, Cornelia and Nutter, David and Rank, Stephen}
}
@article {flosswp174,
	title = {Community structure of modules in the Apache project},
	year = {2004},
	month = {June},
	abstract = {The relationships among modules in a software project of a certain size can give us much information about its internal organization and a way to control and monitor development activities and evolution of large libre software projects. In this paper, we show how information available in CVS repositories can be used to study the structure of the modules in a project when they are related by the people working in them, and how techniques taken from the social networks fields can be used to highlight the characteristics of that structure. As a case example, we also show some results of applying this methodology to the Apache project in several points in time. Among other facts, it is shown how the project evolves and is self-structuring, with developer communities of modules corresponding to semantically related families of modules.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/barahona-apache_structure.pdf},
	author = {Jesus M. Gonzalez-Barahona}
}
@proceedings {1190,
	title = {Community structure of modules in the Apache project},
	year = {2004},
	pages = {44-48},
	abstract = {The relationships among modules in a software project of a certain size can give us much information about its internal organization and a way to control and monitor development activities and evolution of large libre software projects. In this paper, we show how information available in CVS repositories can be used to study the structure of the modules in a project when they are related by the people working in them, and how techniques taken from the social networks fields can be used to highlight the characteristics of that structure. As a case example, we also show some results of applying this methodology to the Apache project in several points in time. Among other facts, it is shown how the project evolves and is self-structuring, with developer communities of modules corresponding to semantically related families of modules.},
	keywords = {apache, cvs, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/gonzalezBarahona44-48.pdf},
	author = {Jesus M. Gonzalez-Barahona and Luis Lopez and Gregorio Robles}
}
@article {flosswp146,
	title = {A Comparative Study of Online User Communities Involvement In Product Innovation and Development},
	year = {2004},
	month = {February},
	abstract = {The literature lacks a conceptual understanding on how different types of online user communities can influence the product innovation and development. Therefore, this research attempts to understand this phenomenon by re-classifying the current online user communities from the perspective of product innovation and development and has resulted in five different models of user communities. We compare and discuss of the five models. Lastly, we will further discuss the deficiencies of the User Collaboration Innovation Communities, theoretically and practically, to suggest the feasibility of the research direction in the future.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/chanlee.pdf},
	author = {Tzu-Ying Chan}
}
@proceedings {1198,
	title = {A Conflict Detected Earlier is a Conflict Resolved Easier},
	year = {2004},
	pages = {82-86},
	abstract = {Open Source development is highly distributed and parallel in nature. There are no definite boundaries, either for people or from where they work. This high level of parallel, distributed development leads to conflicting changes made concurrently by different developers. Be- cause OSS developers lack the kinds of informal coordination opportunities that collocation offers, OSS developers must rely on mailing lists, discussion groups, and tools such as CM and bug tracking systems to try to man- age their parallel efforts such that conflicts do not occur. Unfortunately, these coordination mechanisms are not adequate: it still regularly happens that parallel changes interfere, either via direct overlap or indirect, semantic conflicts. In this paper, we build upon our previous work in raising awareness as a mechanism to support better coordination among developers, and introduce a new integration of our Palantír tool with Eclipse as well as a new visualization of parallel work that we believe is especially useful in Open Source settings.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/sarma83-87.pdf},
	author = {Sarma, A. and van der Hoek, A.}
}
@article {flosswp195,
	title = {The contestation of code: A preliminary investigation into the discourse of the free/libre and open source movements},
	year = {2004},
	month = {April},
	abstract = {This paper uses discourse analysis to examine the free/libre and open source movements. It analyses how they fix elements within the order of discourse of computer code production. It attempts to uncover the key signifiers in their discourses and trace linkages between the sedimented discourses of wider society. Using discourse theory and critical discourse analysis, the theoretical foundations underpinning each of the movements are critically examined and the effect on the wider developer and Internet community is discussed. Additionally, this paper seeks to recommend discursive strategies that could be employed to avoid the threat of colonization by neoliberal discourse and the consequent challenge this has for the ideas of freedom, liberty and community within the developer communities? own discourses.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/berry1.pdf},
	author = {David M. Berry}
}
@article {flosswp166,
	title = {Contrasting Community Building in Sponsored and Community Founded Open Source Projects},
	year = {2004},
	month = {September},
	abstract = {Prior characterizations of open source projects have been based on the model of a community-founded project. More recently, a second model has emerged, where organizations spinout internally developed code to a public forum. Based on field work on open source projects, we compare the lifecycle differences between these two models. We identify problems unique to spinout projects, particularly in attracting and building an external community. We illustrate these issues with a feasibility analysis of a proposed open source project based on VistA, the primary healthcare information system of the U.S. Department of Veterans Affairs. This example illuminates the complexities of building a community after a code base has been developed and suggests that open source software can be used to transfer technology to the private sector.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/westomahony.pdf},
	author = {Joel West}
}
@proceedings {1185,
	title = {Contributing to OS Projects. A Comparison between Individual and Firms},
	year = {2004},
	note = {"Following the approach used in previous surveys on Open Source developers, we prepared an on-line questionnaire;"},
	pages = {18-22},
	abstract = {This paper studies the contributions software firms make to Open Source (OS) projects. Our goal is to ascertain whether they follow the same regularity of pattern seen for individual programmer An exhaustive empirical analysis was carried out using data on project membership1 , project coordination and the contributions made by 146 Italian firms that do business with OS software. We compare our findings with the results of the surveys taken on OS programmers. The availability of the data gathered by Hertel et al. ([10]) on 141 developers of the Linux kernel allowed a direct comparison to be carried out between the two sets2 .},
	keywords = {Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/19-23.pdf},
	author = {Andrea Bonaccorsi and Cristina Rossi}
}
@proceedings {1202,
	title = {Control Objectives in Open Source Projects},
	year = {2004},
	pages = {100-104},
	abstract = {Many studies on Open Source Software Development (OSSD) have been published in the past years. In these studies, OSSD has received positive comments and is proposed as a new way of developing software. We investigate how project management is used in Open Source Software (OSS) projects to exercise control of development activities. Project management in OSSD is worth studying, because research has shown that project management is a critical success factor in traditional software development. We use the COBIT framework to audit project management practices commonly found in OSS projects with the aim of determining which practices are currently missing or can be further improved upon. The framework identifies several potential threats to the long term continuity of OSS projects.},
	keywords = {cobit, project management},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ven101-105.pdf},
	author = {Ven, Kris and Verelst, Jan}
}
@conference {Crowston:2004,
	title = {Coordination practices for bug fixing within FLOSS development teams},
	booktitle = {1st International Workshop on Computer Supported Activity Coordination, 6th International Conference on Enterprise Information Systems},
	year = {2004},
	note = {"First, we chose projects for which data we need for our analysis are publicly available (not all projects allow public access to the bug tracking system). Second, we chose teams with more than 8 members...we tried to select more and less suc- cessful development teams. To this aim we used the definitions of success proposed by [9], who suggest that a project is successful if it is active, the resulting software is downloaded and used and the code matures"

"Kicq, Gaim and PhPmyAdmin were chosen" - effective
DynAPI was chosen as an example of a less effective project" 

"We collected data indicative of the success of each project, such as its level of activity, number of downloads and development status. We then collected data from the archives of the bug tracking system, the tool used to support the bug fixing process"},
	address = {Porto, Portugal},
	abstract = {Free/Libre Open Source Software (FLOSS) is primarily developed by distributed teams. Developers contribute from around the world and coordinate their activity almost exclusively by means of email and bulletin boards. FLOSS development teams some how profit from the advantages and evade the challenges of distributed software development. Despite the relevance of the FLOSS both for research and practice, few studies have investigated the work practices adopted by these development teams. In this paper we investigate the structure and the coordination practices adopted by development teams during the bug-fixing process, which is considered one of main areas of FLOSS project success. In particular, based on a codification of the messages recorded in the bug tracking system of four projects, we identify the accomplished tasks, the adopted coordination mechanisms, and the role undertaken by both the FLOSS development team and the FLOSS community. We conclude with suggestions for further research.},
	keywords = {activity, bug fixing, bug reports, bug tracker, coordination, downloads, dynapi, FLOSS, gaim, kicq, phpmyadmin, status},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonScozzi04coordination.pdf},
	author = {Kevin Crowston and Barbara Scozzi}
}
@article {flosswp203,
	title = {The critical delusion of the condition of digitisation},
	year = {2004},
	month = {December},
	abstract = {This essay analyses how digital media prosthetics, institutionalisation (in particular the manifestations of copyright and patent law which lurk behind vested interests in controlling the transition to a vastly more powerful new world), and the imperatives of corporate planning have come into a conflict so fierce that shared lived experience, increasingly, is forced to undergo a rapid process of commodification. This struggle, which can no longer be defined through the lens of geography or class alone, in turn, points to a not too distant future in which commons-based peer production/consumption is exploited within the context of intense social taylorism and digital fordism with the ultimate goal to turn culture into a paid-for experience, and hence moving the terrain of struggle away from the surplus value of labour to the legitimacy of knowledge sharing and pervasive networking, and how the latter can be monetised and controlled in accordance with anarcho-capitalist agendas. Obviously, the question which we ought to pose to ourselves is how the revolutionary demands of hacking can be guided, assembled, and reproduced, so that this process of commodification is consciously resisted by technology developers and users alike, artists, and all those whose creativity and desire for socially conscious technological innovation and emergent social co-operation have been enhanced by the digital condition we{\textquoteright}re increasingly in the centre of.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dafermos_ccc.pdf},
	author = {George Dafermos}
}
@proceedings {906,
	title = {Data Mining for Software Process Discovery in Open Source Software Development Communities},
	year = {2004},
	month = {May},
	address = {Edinburgh, Scotland, UK},
	author = {Chris Jensen and Walt Scacchi}
}
@article {flosswp156,
	title = {Decoding the "Free/Open Source (F/OSS) Puzzle" - a Survey ofTheretical and Empirical Contributions},
	year = {2004},
	month = {April},
	abstract = {F/OSS software has been described by many as a puzzle. In the past five years, it has stimulated the curiosity of scholars in a variety of fields, including economics, law, psychology, anthropology and computer science, so that the number of contributions on the subject has increased exponentially. The purpose of this paper is to provide a sufficiently comprehensive account of these contributions in order to draw some general conclusions on the state of our understanding of the phenomenon and identify directions for future research. The exercise suggests that what is puzzling about F/OSS is not so much the fact that people freely contribute to a good they make available to all, but rather the complexity of its institutional structure and its ability to organizationally evolve over time.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rossi.pdf},
	author = {Maria Alessandra Rossi}
}
@conference {77,
	title = {Do the Rich Get Richer? The Impact of Power Laws on Open Source Development Projects},
	booktitle = {2004 Open Source Conference (OSCON)},
	year = {2004},
	type = {conference presentation},
	address = {Portland, OR, USA},
	keywords = {open source, power law, social network analysis, sourceforge},
	author = {Conklin, Megan}
}
@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 {flosswp140,
	title = {Fostering cooperation on the Internet: social exchange processes in innovative virtual consumer communities},
	year = {2004},
	month = {February},
	abstract = {Virtual communities of consumers increasingly engage in voluntary collaborative production of digital goods and services which became highly successful in recent years. This paper offers a theoretical conceptualization and empirical evidence of the key elements and processes of exchange in those communities. Within a culture of gift-giving and generalized social exchange, knowledge as the main resource of the community is multiplied by giving it away freely to others and thus, fosters contribution behavior. Friendship, peer reputation and external feed-back provided by a global user community represent highly motivating social rewards which, combined with individual gain of knowledge, constitute a self-sustaining system of exchange.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hemetsberger2.pdf},
	author = {Andrea Hemetsberger}
}
@conference {Xinyi04fourinteresting,
	title = {Four Interesting Ways in Which History Can Teach Us About Software},
	booktitle = {Proceedings of the 2004 international workshop on Mining software repositories  - MSR {\textquoteright}04},
	year = {2004},
	month = {05/2004},
	pages = {58-62},
	abstract = {In this position paper, we outline four kinds of studies that we have undertaken in trying to understand various aspects of a software system{\textquoteright}s evolutionary history. In each instance, the studies have involved detailed examination of real software systems based on {\textquotedblleft}facts{\textquotedblright} extracted from various kinds of source artifact repositories, as well as the development of accompanying tools to aid in the extraction, abstraction, and comprehension processes. We briefly discuss the goals, results, and methodology of each approach.},
	keywords = {ant, apache, change analysis, clone, clone detection, cvs, evolution, gcc, growth, kepler, linux, midworld, mycore, postgresql, source code, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/58FourInterestingWays.pdf},
	author = {Michael Godfrey and Xinyi Dong and Cory Kapser and Lijie Zou}
}
@article {134,
	title = {Free and open source development practices in the game community},
	journal = {Software, IEEE},
	volume = {21},
	number = {1},
	year = {2004},
	pages = {59-66},
	abstract = {Findings from empirical studies of free and open source software systems in different communities show that some common processes and practices exist across the board. The studies focused on software development practices, social processes, technical system configurations, organizational contexts, and interrelationships that give rise to free and open source systems, These distinct communities, and the computer game community in particular, provide examples of common practices.},
	author = {Walt Scacchi}
}
@conference {1105,
	title = {Free \& Open Source Software Creation and {\textquoteleft}the Economy of Regard{\textquoteright}},
	booktitle = {Third EPIP Workshop},
	year = {2004},
	month = {04/2004},
	keywords = {linux, linux kernel, scm, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/DalleDavidGhosh\%20Wolak.pdf},
	author = {Jean-Michel Dalle and Paul A. David and Rishab Ayer Ghosh and Frank A. Wolak}
}
@proceedings {45,
	title = {Free Software Development: Cooperation and Conflict in a Virtual Organizational Culture},
	year = {2004},
	publisher = {IDEA Publishing Group},
	author = {Margret Elliott and Walt Scacchi}
}
@article {907,
	title = {Free/Open Source Software Development Practices in the Computer Game Community},
	journal = {IEEE Software},
	volume = {21},
	number = {1},
	year = {2004},
	month = {January/February},
	pages = {59-67},
	attachments = {https://flosshub.org/sites/flosshub.org/files/scacchi4_0.pdf},
	author = {Walt Scacchi}
}
@proceedings {1195,
	title = {From Bazaar to Kibbutz: How Freedom Deals with Coherence in the Debian Project},
	year = {2004},
	note = {"I am a member of the Debian project since 2000."},
	pages = {71-75},
	abstract = {The goal of obtaining a coherent distribution of software packages where all programs interact smoothly increases its complexity with the number of applications, the number of architectures involved, and the number of system configurations supported. The Debian project aims at producing a software system with thousands of components running on eleven different hardware architectures, with three different operating
system kernels. This paper describes the project and how the work of hundreds of people that never meet one with another can be coordinated to produce reasonably robust and integrated systems.},
	keywords = {debian},
	attachments = {https://flosshub.org/sites/flosshub.org/files/monga72-76.pdf},
	author = {Monga, M.}
}
@article {flosswp178,
	title = {GlueTheos: Automating the Retrieval and Analysis of Data from Publicly Available Software Repositories},
	journal = {Proceedings of the 2004 international workshop on Mining software repositories  - MSR {\textquoteright}04},
	year = {2004},
	month = {05/2004},
	abstract = {For efficient, large scale data mining of publicly available information about libre (free, open source) software projects, automating the retrieval and analysis processes is a must. A system implementing such automation must have into account the many kinds of repositories with interesting information (each with its own structure and access methods), and the many kinds of analysis which can be applied to the retrieved data. In addition, such a system should be capable of interfacing and reusing as much existing software for both retrieving and analyzing data as possible. As a proof of concept of how that system could be, we started sometime ago to implement the GlueTheos system, featuring a modular,flexible architecture which has been already used in several of our studies of libre software projects. In this paper we show its structure, how it can be used, and how it can be extended.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles-barahona-ghosh_gluetheos.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Rishab Ayer Ghosh}
}
@conference {1482,
	title = {Group awareness in distributed software development},
	booktitle = {2004 ACM conference on Computer supported cooperative work  - CSCW {\textquoteright}04},
	year = {2004},
	pages = {72-81},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Open-source software development projects are almost always collaborative and distributed. Despite the difficulties imposed by distance, these projects have managed to produce large, complex, and successful systems. However, there is still little known about how open-source teams manage their collaboration. In this paper we look at one aspect of this issue: how distributed developers maintain group awareness. We interviewed developers, read project communication, and looked at project artifacts from three successful open source projects. We found that distributed developers do need to maintain awareness of one another, and that they maintain both a general awareness of the entire team and more detailed knowledge of people that they plan to work with. Although there are several sources of information, this awareness is maintained primarily through text-based communication (mailing lists and chat systems). These textual channels have several characteristics that help to support the maintenance of awareness, as long as developers are committed to reading the lists and to making their project communication public.},
	keywords = {email, email archive, mailing list},
	isbn = {1581138105},
	doi = {10.1145/1031607.1031621},
	author = {Schneider, Kevin and Gutwin, Carl and Penner, Reagan}
}
@article {flosswp191,
	title = {Hacking Alone? The Effects of Online and Offline Participation on Open Source Community Leadership},
	year = {2004},
	month = {September},
	abstract = {Research on computer mediated communication has examined how a lack of social presence affects participation, communication and leadership in online groups, but until recently, has not examined offline relations or emergent social structures. The few studies examining these issues have not been integrated with research on open source communities. Online communities producing open source software face even greater problems of governance than affinity or interest based online communities, as leadership responsibilities extend beyond mailing list management to managing release dates, public relations, and collaborations with firms. With data from one open source community{\textquoteright}s online and offline networks over three consecutive years, we assess factors affecting voting participation and leadership. We find that the more developers one has met face to face, the more likely one was to vote in a leadership election. Controlling for contributions of code, developers are more likely to hold a top leadership position when they participate more in online discussions. However, online participation in technical discussions did not affect leadership as much as occupying a structurally advantaged position in the community{\textquoteright}s social network. We conclude with theoretical implications that consider the dynamics of online and offline networks for governing distributed online communities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/omahonyferraro2.pdf},
	author = {Siobhan O{\textquoteright}Mahony}
}
@mastersthesis {flosswp188,
	title = {Hacking Practices and Software Development: A Social Worlds Analysis of ICT Innovation and the Role of Free/Libre Open Source Software},
	year = {2004},
	note = {Through use of social worlds theory and qualitative research methods, this thesis explores hackers{\textquoteright} practices and their relationships with the computing world and the wider society from a socio-technical perspective. The hacker social world comprises actors from diverse social-technical backgrounds who share a constellation of im/material practices, namely open source practices (OSPs). Through engaging with these collective practices, actors and actants communicate, negotiate, and shape each other{\textquoteright}s identities, practices and understandings of the innovation structure and system in various aspects. In examining the diverse articulations and performances in which hacker culture and hacker identity are both reflected and constructed, the thesis tries to contextualise and deconstruct the ICT architecture we take for granted, as well as the innovations made possible by this architecture.The major findings of my research are: (1) As a community of open source practices, the FLOSS social world allows diverse actors to engage in the innovation process and therefore fosters a greater innovation resource than other relatively conventional software engineering models. (2) The strategic collaboration between the public (i.e. the free software community) and the private (i.e. information technology corporations) sectors symbolises a pattern of hybrid innovation that entails complex communications and networks, though stabilizing these can be problematic. (3) Tacit knowledge anchored in everyday experiences is particularly valued in a community-based innovation system where social networking and information sharing are extensive. (4) The development of FLOSS democratises software innovation process and allows lay people to develop their understanding and knowledge of a shared problem/issue, especially through the web, to challenge established views on the issue.},
	month = {September},
	abstract = {Through use of social worlds theory and qualitative research methods, this thesis explores hackers{\textquoteright} practices and their relationships with the computing world and the wider society from a socio-technical perspective. Through engaging with a constellation of open source practices (OSPs), actors and actants communicate, negotiate, and shape each other?s identities, practices and understandings of the innovation structure and system in various aspects. In examining the diverse articulations and performances in which hacker culture and hacker identity are both reflected and constructed, the thesis tries to contextualise and deconstruct the ICT architecture we take for granted, as well as the innovations made possible by this architecture.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin2.pdf},
	author = {Yu-wei Lin}
}
@proceedings {1186,
	title = {How can Academic Software Research and Open Source Software Development help each other?},
	year = {2004},
	pages = {5-8},
	abstract = {In this paper we discuss a few issues faced in coordinating, managing and implementing academic software research projects and suggest how some of these issues can be addressed by adopting tools and processes from Open Source Software Development. At the same time we also discuss how a few issues in Open Source Software Development (OSSD) projects can be addressed by adopting processes from Academic Software Research.},
	keywords = {academic, education},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ambati6-9.pdf},
	author = {Ambati, V. and Kishore, S.P.}
}
@article {129,
	title = {How effective developers investigate source code: An exploratory study},
	journal = {Ieee Transactions on Software Engineering},
	volume = {30},
	number = {12},
	year = {2004},
	note = {Times Cited: 6},
	pages = {889-903},
	abstract = {Prior to performing a software change task, developers must discover and understand the subset of the system relevant to the task. Since the behavior exhibited by individual developers when investigating a software system is influenced by intuition, experience, and skill, there is often significant variability in developer effectiveness. To understand the factors that contribute to effective program investigation behavior, we conducted a study of five developers performing a change task on a medium-size open source system. We isolated the factors related to effective program investigation behavior by performing a detailed qualitative analysis of the program investigation behavior of successful and unsuccessful developers. We report on these factors as a set of detailed observations, such as evidence of the phenomenon of inattention blindness by developers skimming source code. In general, our results support the intuitive notion that a methodical and structured approach to program investigation is the most effective. Index Terms-Software evolution, empirical software engineering, program investigation, program understanding.},
	author = {Robillard, M. P. and Coelho, W. and Murphy, G. C.}
}
@article {flosswp187,
	title = {How Free Become Open and Everything Else Under the Sun},
	year = {2004},
	month = {October},
	abstract = {Free and Open Source Software (FOSS) has been adopted as a political tool by leftist activists. At the same time, it has been embraced by large corporations to extend profits and has been criticized as an integral force in late capitalism. It has been adopted by members of the growing Commons movement as a model for limiting the power of capitalism. This essay attempts to confront the variability of these relationships through a cursory analysis of each field and through an look at FOSS philosophy and practice. It argues that Free Software exists as a politically agnostic field of practice{\textendash}built on and through a broadly defined philosophy. It analyzes the way that this philosophy is well suited for the spread of FOSS technologies and its translation into the terms of radically different, even oppositional, social and political movements.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/colemanhill.pdf},
	author = {Biella Coleman}
}
@article {flosswp173,
	title = {How is Open Source affecting software development?},
	year = {2004},
	month = {January},
	abstract = {Paper describes impact of using open source software in general development environments. (From the intro): " The dynamism of open source software development efforts, numerous high-profile success stories, and the novel economic, business, and legal aspects of open source software adoption are justifiably creating a stir in the development community. We software practitioners increasingly face the possibility of using or basing our work on open source components, libraries, frameworks, systems, platforms, and development environments."},
	attachments = {https://flosshub.org/sites/flosshub.org/files/spinellisszyperski.pdf},
	author = {Diomidis Spinellis and Clemens Szyperski}
}
@article {flosswp242,
	title = {How to Have a Successful Free Software Project},
	year = {2004},
	month = {December},
	abstract = {Some free software projects have been extremely successful. This rise to prominence can be attributed to the high quality and suitability of the software. This quality and suitability is achieved through an elaborate peer-review process performed by a large community of users, who act as co-developers to identify and correct software defects and add features. Although this process is crucial to the success of free software projects, there is more to the free software development than the creation of a ?bazaar?. In this paper we draw on existing free software projects to define a lifecycle model for free software. This paper then explores each phase of the lifecycle model and agrees that, while the bazaar phase attracts the most attention, it is the initial modular design that accommodates diverse interventions. Moreover, it is the period of transition from the initial group to the larger community based development that is crucial in determining whether a free software project will succeed or fail.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/senyardmichlmay.pdf},
	author = {Anthony Senyard}
}
@unpublished {flosswp189,
	title = {Implicit theories of "good leadership" in the open-source community},
	year = {2004},
	month = {April},
	abstract = {The goal of this paper is to uncover the implicit theories (a.k.a. personal believes) of open-source developers concerning the characteristics and behaviors of a "good project leader". Three main behavioral factors are discovered to describe such implicit theories: competence, task orientation and person consideration. The conclusions of this study have been drawn from an analysis conducted on data gathered through 138 respondents.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bosco.pdf},
	author = {Gianluca Bosco}
}
@article {capiluppi:23,
	title = {Improving comprehension and cooperation through code structure},
	journal = {IEE Seminar Digests},
	volume = {2004},
	number = {908},
	year = {2004},
	note = {"In this study we measured source code size in three different forms (LOCs, SLOCs, and Kbs of code)."

"Pilot Project: The ARLA System"
},
	pages = {23-28},
	publisher = {IEE},
	abstract = {Defining a relationship between a software system{\textquoteright}s architecture and the process{\textquoteright} efforts is one of the most fascinating questions of software engineering. Apparently, when a system{\textquoteright}s architecture is complex, the process to improve and evolve it will be more difficult. We try to tackle this question from a different point of view: given an open source system, in all the phases of its evolution, we focus on both the aspects of software developers, and the obtained software product. More we observe one of the possible architectures of this system, based on the tree structure derived from source components. First conclusions show that some patterns of tree evolution are recognizable: some branches may appear more promising than other, and are extensively evolved, while other remains in the same status for all the life cycle. More, when the tree structure reaches some status, the process of joining as a core developer seems to forestall. },
	keywords = {arla, code structure, contributors, developers, open source system, scm, software development, software engineering, software process, software product, software system architecture, source code, source components, tree evolution, tree structure},
	doi = {10.1049/ic:20040260},
	url = {http://link.aip.org/link/abstract/IEESEM/v2004/i908/p23/s1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/capiluppi2004.pdf},
	author = {A. Capiluppi}
}
@proceedings {1196,
	title = {In the network: Distributed control in Gentoo Linux},
	year = {2004},
	abstract = {This position paper reports on the findings of an empirical pilot study of Gentoo Linux. Gentoo Linux is an open source Linux distribution developed by a geographically distributed community of volunteers. The reported findings are based on the analysis of a specific episode using actor network theory. With basis in the analysis, it is argued that control in this specific episode can be interpreted as both distributed and local at the same time. Control here being the power to define a problem and make the decision about the appropriate solution to the problem defined. Control, it is argued, is distributed in that it is the function of reciprocal influence among several human and non-human actors. Furthermore, it is argued that control can be interpreted as not inherent in organizational structures or hierarchies, but locally embedded among actors in the decision making process.},
	keywords = {gentoo, linux},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osterlie77-82.pdf},
	author = {{\O}sterlie, T.}
}
@conference {132,
	title = {The influence of network governance factors on success in open source software development projects},
	booktitle = {Twenty-Fifth International Conference on Information Systems},
	year = {2004},
	pages = {427{\textendash}438},
	address = {Washington, DC},
	author = {Glen W. Sagers}
}
@proceedings {1194,
	title = {Inside an Open Source Software Community: Empirical Analysis on Individual and Group Level},
	year = {2004},
	pages = {65-70},
	abstract = {An established Open Source Software community (Apache Cocoon) was explored using an online questionnaire about demographic data and individual and	group-related	factors.	Individual	factors encompassed forms of contributions, motivation, expertise and knowledge. Role structures, expectations towards other members, trust and collaboration issues were analysed at group level. More than 60\% of the developer community completed this questionnaire. Results provide a valuable basis for deeper understanding of knowledge sharing, collaboration and innovation processes in distributed work groups.},
	keywords = {apache, Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/maass66-71.pdf},
	author = {Maass, W.}
}
@article {flosswp194,
	title = {Internet Research: Privacy, Ethics and Alienation ? An Open Source Approach},
	year = {2004},
	month = {December},
	abstract = {This paper examines some of the ethical problems involved in undertaking Internet research and draws on historical accounts as well as contemporary studies to offer an analysis of the issues raised. It argues that privacy is a misleading and confusing concept to apply to the Internet, and that the concept of non-alienation is more resourceful in addressing the many ethical issues surrounding Internet research. Using this as a basis, the paper then investigates the Free/Libre and Open Source research model and argues for the principles of ?open source ethics? in researching the online world, which includes a participatory and democratic research method.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/berry2.pdf},
	author = {David M. Berry}
}
@article {flosswp183,
	title = {Intrinsic Motivation in Open Source Software Development},
	year = {2004},
	month = {September},
	abstract = {This papers sheds light on the puzzling evidence that even though open source software (OSS) is a public good, it is developed for free by highly qualified, young and motivated individuals, and evolves at a rapid pace. We show that once OSS development is understood as the private provision of a public good, these features emerge quite naturally. We adapt a dynamic private-provision-of-public-goods model to reflect key aspects of the OSS phenomenon. In particular, instead of relying on extrinsic motives for programmers (e.g. signaling) the present model is driven by intrinsic motives of OSS programmers, such as user-programmers, play value or homo ludens payoff, and gift culture benefits. Such intrinsic motives feature extensively in the wider OSS literature and contribute new insights to the economic analysis.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bitzerschrettlschroder.pdf},
	author = {Jurgen Bitzer}
}
@article {flosswp158,
	title = {The Jukebox Mode of Innovation: a Model of Commercial Open Source Development},
	year = {2004},
	month = {May},
	abstract = {In this paper, I explore the circumstances under which innovation processes without secrecy or intellectual property protection are viable, and where free revealing of innovations is a profit-maximizing strategy. Motivated by an empirical study of embedded Linux, I develop a duopoly model of quality competition. Firms require two complementary technologies as inputs, but differ with respect to the relative importance of these technologies. I find that a regime with compulsory revealing can lead to higher product qualities and higher profits than a proprietary regime. When the decision to reveal is endogenized, equilibria with voluntary revealing arise, again superior to the proprietary outcome.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/henkel.pdf},
	author = {Joachim Henkel}
}
@conference {1054,
	title = {LASER: a lexical approach to analogy in software reuse},
	booktitle = {International Workshop on Mining Software Repositories (MSR 2004)},
	volume = {2004},
	year = {2004},
	pages = {112 - 116},
	publisher = {IEE},
	organization = {IEE},
	address = {Edinburgh, Scotland, UK},
	abstract = {Software reuse is the process of creating a software system from existing software components, rather than creating it from scratch. With the increase in size and complexity of existing software repositories, the need to provide intelligent support to the programmer becomes more pressing. An analogy is a comparison of certain similarities between things which are otherwise unlike. This concept has shown to be valuable in developing UML-level reuse techniques. In the LASER project we apply lexically-driven Analogy at the code level, rather than at the UML-level, in order to retrieve matching components from a repository of existing components. Using the lexical ontology Word-Net, we have conducted a case study to assess if class and method names in open source applications are used in a semantically meaningful way. Our results demonstrate that both hierarchical reuse and parallel reuse can be enhanced through the use of lexically-driven Analogy.},
	keywords = {class, developers, functions, jrefactory, method, naming, natural language, reuse, source code, wordnet},
	doi = {10.1049/ic:20040487},
	attachments = {https://flosshub.org/sites/flosshub.org/files/112LASER.pdf},
	author = {Amin, R. and Mel O Cinneide and Veale, Tony}
}
@article {flosswp161,
	title = {Legal Issues for the Use of Free and Open Source Software in Government},
	year = {2004},
	month = {January},
	abstract = {This paper examines some of the legal issues that face the uptake of free and open source software in government in Australia. This paper was presented at the {\textquoteright}Linux and Open Source in Government{\textquoteright} conference, part of Linux.Conf.Au 2004 in Adelaide, Australia.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/suzorfitzgeraldbasset.pdf},
	author = {Nic Suzor}
}
@unpublished {flosswp162,
	title = {Linux Adoption by Firms},
	year = {2004},
	month = {May},
	abstract = {The objective of this study is to examine the evolution of the market for Linux based products for the 1993-2003 period. Using data on 317 Linux suppliers available online, the differences in firms? size and in their first products were explored across the adoption stages of the Linux life cycle. Then two temporal patterns of the Linux-market were identified: changes in the entry rate of new Linux suppliers and changes in product diversity. Finally, the attributes of the partnerships formed by four major Linux distributors were examined. The study determined whether the number of partnerships formed by Linux distributors was related to the number of new entrants, whether the motives for partnerships formed by Linux distributors varied over adoption stages, and whether the type of partner selected by Linux distributors was a function of partnership motive. This study builds on the literature on open source software and traditional theories of technology adoption to make three important contributions. First, it develops a method to identify the stages of the life of a new technology. Secondly, it provides a way to measure the temporal patterns of the evolution of a new market. Finally, it validates the densitydependence model using data on open source.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/peng.pdf},
	author = {Zheshi Peng}
}
@article {DBLP:journals/electronicmarkets/Joode04,
	title = {Managing Conflicts in Open Source Communities},
	journal = {Electronic Markets},
	volume = {14},
	number = {2},
	year = {2004},
	pages = {104-113},
	abstract = {An increasing number of companies adopt open source software. These companies will typically pay programmers to participate in the design, development and maintenance of open source software. The programmers, however, are reported to have different interests compared to the voluntary programmers who dominate most open source communities. The diversity of interest will inevitably result in conflicts. To ensure that their interests are achieved, companies should understand how conflicts between their programmers and the voluntary programmers can be managed. The aim of this paper is to identify and discuss mechanisms that are currently present to manage conflicts in open source communities.

The mechanisms identified in this paper are based on an explorative literature study and on 48 semi-structured interviews with programmers from a variety of open source communities. Four mechanisms have been identified and their relevance in the management of conflicts are discussed. They are: third-party intervention; modularity; parallel software development lines; and the exit option. The paper ends with an example of Covalent, which deploys parallel software development lines to manage conflicts in the Apache community. },
	keywords = {abiword, apache, conflict, covalent, interviews, organizational sponsorship, Volunteers},
	author = {Ruben van Wendel de Joode}
}
@article {flosswp201,
	title = {Managing Volunteer Activity in Free Software Projects},
	year = {2004},
	month = {July},
	abstract = {During the last few years, thousands of volunteers have created a large body of free software. Even though this accomplishment shows that the free software development model works, there are some drawbacks associated with this model. Due to the volunteer nature of most free software projects, it is impossible to fully rely on participants. Volunteers may become busy and neglect their duties. This may lead to a steady decrease of quality as work is not being carried out. The problem of inactive volunteers is intensified by the fact that most free software projects are distributed, which makes it hard to quickly identify volunteers who neglect their duties. This paper shows Debian{\textquoteright}s approach to inactive volunteers. Insights presented here can be applied to other free software projects in order to implement effective quality assurance strategies.},
	keywords = {debian, volunteer, volunteer teams},
	attachments = {https://flosshub.org/sites/flosshub.org/files/michlmayr-mia.pdf},
	author = {Martin Michlmayr}
}
@article {1253,
	title = {The many meanings of open source},
	journal = {IEEE Software},
	volume = {21},
	year = {2004},
	note = {"We determined a set of characteristics that are almost always present and others that vary among open source projects, and this serves as the core of this work"
"Section 3 describes some open source characteristics that can be used in determining whether a project is or not open source"},
	month = {01/2004},
	pages = {34 - 40},
	abstract = {The term Open Source is widely applied to describe some software development methodologies. This paper does not provide a judgment on the open source approach, but exposes the fact that simply stating that a project is open source does not provide a precise description of the approach used to support the project. By taking a multi- disciplinary point of view, we propose a collection of characteristics that are common, as well as some that vary among open source projects. The set of open source characteristics we found can be used as a tick-list both for analysing and for setting up open source projects. Our tick-list also provides a starting point for understanding the many meanings of the term open source.},
	keywords = {classification, projects, taxonomy},
	issn = {0740-7459},
	doi = {10.1109/MS.2004.1259206},
	attachments = {https://flosshub.org/sites/flosshub.org/files/gacek.pdf},
	author = {Gacek, C. and Arief, B.}
}
@proceedings {124,
	title = {Membership dynamics and network stability in the open-source community: the ising perspective},
	year = {2004},
	note = {"simulations with the empirical network data that were collected from two actual OSS communities, Linux and Hypermail."

"we initially downloaded nearly 100,000 archived (between 1997 and 2003) LINUX Kernel and Hypermail newsgroup messages posted in a UNIX mailbox format"

"Specific information was obtained regarding the characteristics of these two OSS communities, including the size, the number of average connections per participant, and the hierarchy of each community."},
	abstract = {In this paper, we address the following two questions: (1)How does a participant{\textquoteright}s membership decision affect the others (neighbors) with whom he has collaborated over an extended period of time in an open source software (OSS) network? (2) To what extent do network characteristics (i.e, size and connectivity) mediate the impact of external factors on the OSS participants{\textquoteright} dynamic membership decisions and hence the stability of the network? From the Ising perspective, we present fresh theoretical insight into the dynamic and reciprocal membership relations between OSS participants. We also performed simulations based on empirical data that were collected from two actual OSS communities. Some of the key findings include that (1) membership herding is highly present when the external force is weak, but decreases significantly when the force increases, (2) the propensity for membership herding is most likely to be seen in a large network with a random connectivity, and (3) for large networks, at low external force a random connectivity will perform better than a scale-free counterpart in terms of the network strength. However, as the temperature (external force) increases, the reverse phenomenon is observed. In addition, the scale-free connectivity appears to be less volatile than with the random connectivity in response to the increase in the temperature. We conclude with several implications that may be of significance to OSS stakeholders.},
	keywords = {email, email archive, hypermail, linux, mailing list, membership, membership herding, newsgroup, open source, participants, social network analysis, stakeholders, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OhJeon.pdf},
	author = {Oh, Wonseok and Jeon, Sangyong}
}
@proceedings {1187,
	title = {Migrating a Development Project to Open Source Software Development},
	year = {2004},
	pages = {9-13},
	abstract = {The CommSy-system is a web-based community system, which has been in development since 1999 at the University of Hamburg. It has initially been developed by students and researchers in their spare time. Its last organizational setting was a publicly funded research project, which allowed for full-time and part-time developers. As that project has come to an end, we are aiming at an open source project to ensure continuity by providing a frame for people from different organizations. In this paper we discuss the characteristics of this specific project and of other open source projects to identify a strategy for migrating that particular project to open source. We outline the actions taken to migrate the existing project to open source software development and raise questions concerning the necessary characteristics of an open source project as well as whether the actions will suffice or not.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bleek10-14.pdf},
	author = {Bleek, W-G. and Finck, M.}
}
@conference {Germ04b,
	title = {Mining CVS repositories, the softChange experience},
	booktitle = {Proc. Int{\textquoteright}l Workshop on Mining Software Repositories ({MSR})},
	year = {2004},
	note = {"Mailing lists. Mailing lists are an important source of information about the evolution of the project. We currently correlate MRs [modification requests] to mail messages by using the author and the date attributes of both the MR and the message."},
	pages = {17{\textendash}21},
	abstract = {CVS logs are a rich source of software trails (information left behind by the contributors to the development process, usually in the forms of logs). This paper describes how softChange extracts these trails, and enhances them. This paper also addresses some challenges that CVS fact extraction poses to researchers.},
	keywords = {bugzilla, cvs, email archives, log files, logs, softchange},
	attachments = {https://flosshub.org/sites/flosshub.org/files/17MiningCVS.pdf},
	author = {German, Daniel}
}
@conference {1050,
	title = {Mining version control systems for FACs (frequently applied changes)},
	booktitle = {International Workshop on Mining Software Repositories (MSR 2004)},
	volume = {2004},
	year = {2004},
	pages = {48 - 52},
	publisher = {IEE},
	organization = {IEE},
	address = {Edinburgh, Scotland, UK},
	abstract = {Today, programmers are forced to maintain a software system based on their gut feeling and experience. This paper makes an attempt to turn the software maintenance craft into a more disciplined activity, by mining for frequently applied changes in a version control system. Next to some initial results, we show how this technique allows to recover and study successful maintenance strategies, adopted for the redesign of long{\textendash}lived systems.},
	keywords = {ccfinder, change analysis, change history, clone, clone detection, cvs, maintenance, tomcat, version control},
	doi = {10.1049/ic:20040475},
	attachments = {https://flosshub.org/sites/flosshub.org/files/48MiningVersion.pdf},
	author = {Van Rysselberghe, F. and Demeyer, S}
}
@article {flosswp159,
	title = {Mobilization of Software Developers: The Free Software Movement},
	year = {2004},
	month = {May},
	abstract = {Free/open source software (F/OSS) development projects are growing at a rapid rate. Globally dispersed virtual communities with large groups of software developers contribute time and effort often without pay. One force behind this phenomenon is the Free Software Movement (FSM), a 20 year-old social movement whose purpose is to promote the use of free software instead of proprietary software. We show how the ideology of the FSM influences software development work practices in F/OSS communities and how an occupational community of F/OSS developers has emerged from this movement. We present results from an empirical study of a F/OSS development community, GNUenterprise (GNUe) whose purpose is to build an Enterprise Resource Planning system. We show how the beliefs in freedom and freedom of choice, and the values of cooperative work and community building are manifested in the GNUe norms of informal self-management, immediate acceptance of fellow contributors, and open disclosure.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/elliottscacchi2.pdf},
	author = {Margret Elliott}
}
@article {flosswp167,
	title = {Munich/MIT Suvey: Development of Embedded Linux},
	year = {2004},
	month = {May},
	abstract = {The use of Linux in embedded devices has increased enormously in recent years. Most of the publicly available code for embedded Linux is developed and contributed by commercial firms, not by hobbyists. This raises the question if and how the development process differs from that of other OSS. This issue was addressed in a survey of embedded Linux developers yielding 268 valid responses. This paper is a collection of descriptive results from the survey.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/henkeltins.pdf},
	author = {Joachim Henkel}
}
@article {flosswp145,
	title = {Network Formation via Contests: The Production Process of Open Source Software},
	year = {2004},
	month = {January},
	abstract = {Why do both software developers and firms contribute to the production process of Open Source Software (OSS) despite not receiving direct monetary rewards for it? This papers extends results of the economic literature by modelling the OSS production process as an application contest to a "qualified network". The winners receive reputation and high investments. Investors searching for highly talented applicants profit from the selection mechanism of the OSS production process and finance it to receive inside information. We describe incentives for developers and firms and compare the mechanism with alternatives for its efficiency.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/prufer.pdf},
	author = {Jens Prufer}
}
@article {1389,
	title = {New tricks: how open source changed the way my team works},
	journal = {IEEE Software},
	volume = {21},
	year = {2004},
	month = {01/2004},
	pages = {68 - 72},
	abstract = {A commercial software team contributed to an open source implementation of the Windows API on X-Windows and Unix. Wine is an open source implementation of the Windows API, a compatibility layer that lets native windows programs run on X-Windows and Unix. With our contribution filling in some gaps, our client planned to include Wine with a slightly modified product. Expecting chaos in the organization and code, the team instead found a structured community with procedures all its own. The version control tool on the Wine team is CVS (concurrent version system), an open source, network-transparent version control system. Patches on Wine are relatively small, which makes them easier to review and less risky to add to the source tree.},
	issn = {0740-7459},
	doi = {10.1109/MS.2004.1259222},
	url = {http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=1259222},
	author = {Lussier, S.}
}
@article {flosswp169,
	title = {New ventures based on open innovation - an empirical analysis of start-up firms in embedded Linux},
	year = {2004},
	month = {July},
	abstract = {An important and intriguing aspect of e-entrepreneurship is the formation of new ventures in the domain of open source software (OSS). Previous research on these ventures has primarily looked at the design of business models, yet has neglected other key questions relating to the management of these firms, despite clear indications that some existing insights on venture management cannot be applied to new ventures in OSS. The purpose of this paper is to explore how three key challenges of venture management - the liabilities of newness and smallness of start-ups and market entry barriers - affect new ventures in OSS. Based on empirical data from personal interviews and a large scale survey we find that many of the liabilities that are typically discussed in the entrepreneurship literature are much less of a challenge for new ventures in OSS. Our findings have interesting implications for the emerging theory on e-entrepreneurship, and for entrepreneurs considering to exploit business opportunities in OSS, and more generally business opportunities based on open innovations.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/gruberhenkel.pdf},
	author = {Marc Gruber}
}
@proceedings {1197,
	title = {Open Source and Closed Source Software Development Methodologies},
	year = {2004},
	pages = {105-109},
	abstract = {Open source software development represents a fundamentally new concept in the field of software engineering. Open source development and delivery occurs over the Internet. Developers are not confined to a geographic area. They work voluntarily on a project of their choice. As new requirements emerge, the software is enhanced by the user/developers. In this paper we show a comparative study of open source and closed source software development approaches and present a software life cycle model for open source software development.},
	keywords = {life cycle, lifecycle},
	attachments = {https://flosshub.org/sites/flosshub.org/files/potdar106-110.pdf},
	author = {Potdar, V. and Chang, E.}
}
@article {flosswp218,
	title = {Open Source en el e-learning: ?Una cuesti?n de mente? - An?lisis del fen?meno del Open source en el e-learning, situaci?n actual y tendencias},
	year = {2004},
	month = {January},
	abstract = {Primeramente vamos a ver ?Qu? es el Open source? ?Cu?les son sus objetivos y sus caracter?sticas fundamentales?. En segundo lugar haremos un recorrido hist?rico de los ?ltimos a?os, identificando los principales desarrollos del Open source y sus tendencias, especialmente en el ?rea de la educaci?n superior. En tercer lugar mostramos el Proyecto Sakai, donde un grupo de Universidades de Primer nivel est?n uniendo fuerzas para integrar y para sincronizar su software educativo en una colecci?n de herramientas de Open source para e-learning. A continuaci?n haremos mencionaremos los principales aplicaciones de OS en general. Seguidamente, he de tratar de poner de relieve los aspectos t?cnicos y psicol?gicos que est?n presentes en el Open Source y sus protagonistas y las razones econ?micas, pol?ticas y culturales que se vinculan o crean un contexto favorable al crecimiento de las soluciones de open source en el mercado y especialmente en mercado del e-learning. Finalmente y como s?ntesis de estas cuestiones describimos el caso concreto de la Universidad de Wisconsin, que actualmente junto a otras instituciones educativas se ha sumado en el proyecto Sakai.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/biscay.pdf},
	author = {Carlos Biscay}
}
@book {flosswp149,
	title = {Open Source Jarbuch 2004 (in German)},
	year = {2004},
	month = {March},
	abstract = {The "Open Source Jahrbuch 2004" (open source yearbook 2004) is the first publication in German to cover the topic with an interdisciplinary approach. In contains contributions from practitioners as well as from scientists and aims to supply the reader with a comprehensive picture of how rich the open source phenomenon is. Open source means much more than only software. The subtitle of the book, "Zwischen Softwareentwicklung und Gesellschaftsmodell", i.e. "Between Software Development and Social Model", circumscribes the reach of this new way of dealing with information artefacts. The book is directed towards decision-makers from both politics and business as well as to scientists doing reasearch in this field. It delivers first-hand insights as a basis for understanding the potentials and constraints of open source.},
	author = {Robert A Gehring}
}
@unpublished {flosswp168,
	title = {Open source software development put in an impure public goods context},
	year = {2004},
	month = {June},
	abstract = {The open source software development appears to be a problem of pure public goods contribution, but looking more in depth emerge the classic question posed by Lerner and Tirole: "Why should thousands of top-notch programmers contribute freely to the provision of a public good?". So, the aim of this research is to elaborate a model able to cope with the low level of free riding.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bertelli.pdf},
	author = {Federico Bertelli}
}
@article {flosswp148,
	title = {Open Source Software within organization - Critical factors for consulting},
	year = {2004},
	month = {February},
	abstract = {The consultation of enterprises and organizations regarding the correct implementation of modern information technology is an important segment on the modern consulting market. The main focus of this work is to conduct the consultation in consideration of the topic ?Introduction of Open Source e-Business Technologies?. Due to limited budget funds more and more enterprises are designing their value chain more cost-effective by using web based systems. Mostly all parts of the value chain can be supported by e-business technologies. To further reduce the costs this e-business technologies should be Open Source.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/scherler1.pdf},
	author = {Thorsten Scherler}
}
@article {Chen:2004:OCL:990374.990391,
	title = {Open-Source Change Logs},
	journal = {Empirical Softw. Engg.},
	volume = {9},
	year = {2004},
	note = {"We decided to compare actual differences in the source code with entries in the ChangeLog file. We used lxr, the Linux cross-referencing tool..., to determine the precise differences between two successive software versions. We then compared these differences with the records in the ChangeLog file to check the completeness of the ChangeLog file."
},
	month = {September},
	pages = {197{\textendash}210},
	publisher = {Kluwer Academic Publishers},
	address = {Hingham, MA, USA},
	abstract = {A recent editorial in Empirical Software Engineering suggested that open-source software projects offer a great deal of data that can be used for experimentation. These data not only include source code, but also artifacts such as defect reports and update logs. A common type of update log that experimenters may wish to investigate is the ChangeLog, which lists changes and the reasons for which they were made. ChangeLog files are created to support the development of software rather than for the needs of researchers, so questions need to be asked about the limitations of using them to support research. This paper presents evidence that the ChangeLog files provided at three open-source web sites were incomplete. We examined at least three ChangeLog files for each of three different open-source software products, namely, GNUJSP, GCC-g++, and Jikes. We developed a method for counting changes that ensures that, as far as possible, each individual ChangeLog entry is treated as a single change. For each ChangeLog file, we compared the actual changes in the source code to the entries in the ChangeLog file and discovered significant omissions. For example, using our change-counting method, only 35 of the 93 changes in version 1.11 of Jikes appear in the ChangeLog file{\textemdash}that is, over 62\% of the changes were not recorded there. The percentage of omissions we found ranged from 3.7 to 78.6\%. These are significant omissions that should be taken into account when using ChangeLog files for research. Before using ChangeLog files as a basis for research into the development and maintenance of open-source software, experimenters should carefully check for omissions and inaccuracies.},
	keywords = {change log, gcc, GCC-g, GNUJSP, Jikes, log files, Open-source software, source code},
	issn = {1382-3256},
	doi = {10.1023/B:EMSE.0000027779.70556.d0},
	url = {http://portal.acm.org/citation.cfm?id=990374.990391},
	attachments = {https://flosshub.org/sites/flosshub.org/files/chen.pdf},
	author = {Chen, Kai and Schach, Stephen R. and Yu, Liguo and Offutt, Jeff and Heller, Gillian Z.}
}
@proceedings {1193,
	title = {Organizational Structure of {\textquotedblleft}User Collaboration Community{\textquotedblright}: Insights from the Case of an Open Source Software Project},
	year = {2004},
	pages = {58-64},
	abstract = {Current literatures on organization innovation do not investigate the innovation model which is composed of "network between individuals". Therefore, this study proposes the concept of the "User Collaboration Community", tries to understand this new phenomenon by conducting OSS project is the subject of this analysis, borrows the observation variables and propositions adopted by Mintzberg on structures of the innovative organization. This study further infers the conceptual framework and a series of hypothesis on the organizational structure of the user collaboration community. We expect that the proposition of this hypothesis will function as a concrete description and presentation of the innovation model of the "User Collaboration Community".},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lee59-65.pdf},
	author = {Lee, J.F and Chan, T.Y}
}
@proceedings {1200,
	title = {OSS Project Success: From Internal Dynamics to External Impact},
	year = {2004},
	pages = {92-96},
	abstract = {Success in open source software (OSS) development has been viewed in many different ways. This paper examines the relationship between success in terms of the development efforts devoted to an OSS project and success in terms of the acceptance of the software by stakeholders beyond the immediate development group. Research has discussed the importance of communication, norms, and other factors related to the dynamics of work within open source software development groups. The model proposed here suggests a positioning of these internal dynamics in a larger nomological net explaining variation in the success of OSS efforts.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/stewart93-97.pdf},
	author = {Katherine Stewart}
}
@article {flosswp185,
	title = {Papers from Anthropological Quarterly (Vol 77, No 3) - Social Thought and Commentary: Culture{\textquoteright}s Open Source},
	year = {2004},
	month = {October},
	abstract = {Listing of papers: Christopher M. Kelty | Culture{\textquoteright}s Open Sources: Software, Copyright, and Cultural Critique {\textendash}- Gabriella Coleman | The Political Agnosticism of Free and Open Source Software and the Inadvertent Politics of Contrast {\textendash}- Alex Golub | Copyright and Taboo {\textendash}- Anita Chan | Coding Free Software, Coding Free States: Free Software Legislation and the Politics of Code in Peru{\textendash}- Christopher M. Kelty | Punt To Culture{\textendash}- Rosemary J. Coombe \& Andrew Herman | Rhetorical Virtues: Property, Speech, and the Commons on the World-Wide Web{\textendash}- Glenn Otis Brown | Commentary},
	attachments = {https://flosshub.org/sites/flosshub.org/files/aq_cultures_opensources.pdf},
	author = {Christoper Kelty}
}
@article {flosswp190,
	title = {Patterns of Free Revealing ? Balancing Code Sharing and Protection in Commercial Open Source Development},
	year = {2004},
	month = {September},
	abstract = {Commercial firms increasingly contribute to the development of open source software (OSS). However, a conflict often arises between the requirements of the General Public License to make "derived work" available, and firms? interest to protect their intellectual property embodied in the code. If there are ways to mitigate or solve this conflict, the conditions under which OSS will be an appealing solution to firms become much more general. This paper is the first to provide a quantitative empirical study of this conflict and the ways firms deal with it. I present a study of embedded Linux, based on an online-survey that yielded 268 valid responses. It turns out that firms routinely use various means to protect their developments, while keeping the GPL. Still, they do reveal a considerable share of their code? on average, 49\%. Heterogeneity between firms is analyzed using multivariate analysis. I show how the relative importance of various benefits and downsides of revealing determines a firm?s pattern of revealing. An analysis of reported reasons for revealing and of the type of code that is revealed provides further insights into these patterns. Putting the different dimensions of revealing behavior together, I find that consistent patterns of revealing can be identified for different types of firms.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/henkel2.pdf},
	author = {Joachim Henkel}
}
@proceedings {flosswp181,
	title = {The perils and pitfalls of mining SourceForge},
	year = {2004},
	month = {05/2004},
	pages = {7-11},
	abstract = {SourceForge provides abundant accessible data from Open Source Software development projects, making it an attractive data source for software engineering research. However it is not without theoretical peril and practical pitfalls. In this paper, we outline practical lessons gained from our spidering, parsing and analysis of SourceForge data. SourceForge can be practically difficult: projects are defunct, data from earlier systems has been dumped in and crucial data is hosted outside SourceForge, dirtying the retrieved data. These practical issues play directly into analysis: decisions made in screening projects can reduce the range of variables, skewing data and biasing correlations. SourceForge is theoretically perilous: because it provides easily accessible data items for each project, tempting researchers to fit their theories to these limited data. Worse, few are plausible dependent variables. Studies are thus likely to test the same hypotheses even if they start from different theoretical bases. To avoid these problems, analyses of SourceForge projects should go beyond project level variables and carefully consider which variables are used for screening projects and which for testing hypotheses.},
	keywords = {Data Collection, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/howison04msr.pdf},
	author = {Howison, James and Kevin Crowston}
}
@article {42,
	title = {The Political Agnosticism of Free and Open Source Software and the Inadvertent Politics of Contrast},
	journal = {Anthropological Quarterly},
	volume = {77},
	number = {3},
	year = {2004},
	pages = {507--519},
	publisher = {The George Washington University Institute for Ethnographic Research},
	isbn = {00035491},
	url = {http://www.jstor.org/stable/3318232},
	author = {Coleman, E.G.}
}
@unpublished {flosswp197,
	title = {Political Motives of Developers for Collaboration on GNU/Linux},
	year = {2004},
	month = {August},
	abstract = {This paper examines to what degree developers of the collaboratively produced computer operating system GNU/Linux are politically motivated for their contributions. It first states that software is politically relevant. It then goes on to argue for the political significance of Free Software/Open Source Software (FS/OSS) and discusses the developers ambivalent attitude towards a politicisation of FS/OSS. Centrepiece is a survey carried out with 85 GNU/Linux developers that showed that most of them are conscious of the social relevance of FS/OSS and that their engagement is of a deliberately political nature.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/escher.pdf},
	author = {Tobias Escher}
}
@article {1077,
	title = {Profiling an Open Source Project Ecology and Its Programmers},
	journal = {Electronic Markets},
	volume = {14},
	year = {2004},
	month = {6/2004},
	pages = {77 - 88},
	abstract = {While many successful and well-known open source projects produce output of high quality, a general assessment of this development paradigm is still missing. In this paper, an online community of both small and large, successful and failed projects and their programmers is analysed mainly using the version-control data of each project, also according to their productivity and estimation of expended effort. As the results show, there are indeed significant differences between this cooperative development model and the commercial organization of work in the areas explored. Both open source software projects in their size and their programmers{\textquoteright} effort differ significantly, and the evolution of projects{\textquoteright} size over time seems in part to contradict the laws of software evolution proposed for commercial systems. Both the inequality of effort distribution between programmers and an increasing number of developers in a project do not lead to a decrease in productivity, opposing Brooks{\textquoteright}s Law. Effort estimation based on the COCOMO model for commercial organizations shows a large amount of effort expended for the projects, while a more general Norden-Rayleigh modeling shows a distinctly smaller expenditure. This proposes that either a highly efficient development is achieved by this self-organizing cooperative and highly decentralized form of work, or that the participation of users besides programming tasks is enormous and constitutes an economic factor of large proportions. },
	keywords = {affiliation network, brooks law, cocomo, effort estimation, evolution, productivity, project success, scm, size, time, version control},
	issn = {1422-8890},
	doi = {10.1080/10196780410001675031},
	author = {Koch, Stefan}
}
@article {1113,
	title = {Release criteria for the Linux kernel},
	journal = {First Monday},
	volume = {9},
	number = {4},
	year = {2004},
	note = {"The first was to examine the change logs [10, 11, 12] that are submitted with the public release of a version of the kernel on www.kernel.org [1]. Observations were made on the release nomenclature used in both the 2.4.x series and the 2.5.x (which later became the 2.6.x series). The number of patches incorporated into each release and the elapsed time between releases was recorded. The second approach was to review the Linux kernel mailing list [2] for any evidence of criteria for performing a particular release including any metrics used, tests carried out or bug databases referenced."},
	month = {2004},
	abstract = {Before software is released to its users, software developers will ensure that the software has met specified functional and technical requirements and that it is as free from bugs as possible. Users should be able to have a high degree of confidence that the software will perform as specified and without fault. With open source development practices such as those employed on the Linux kernel project, there are no detailed specifications and little formal testing processes. The questions, then, are what criteria, if any, are used in determining the suitability for release of a particular version of this software, and do users have any degree of confidence in the quality of that release of software? These questions were examined in this study using information from the Linux Kernel Mailing List (LKML), the primary forum for discussion of development issues of the Linux kernel, and change logs submitted with version releases of the Linux kernel. It was determined that very little planning is employed in determining the release of a particular version of the software and that a version of the software is essentially a collection of source patches released at regular intervals with some stabilisation of the code base before each release. Very little attempt is made to verify that the code is bug free, and consequently, the code released is of a largely unknown level of quality. End users are left to decide for themselves the suitability and robustness of a particular version of the software.},
	keywords = {bugs, change log, linux, linux kernel, log files, mailing list, patches, quality, release history},
	url = {http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/1136/1056},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Glance.pdf},
	author = {Glance, D.G.}
}
@proceedings {131,
	title = {Remote analysis and measurement of libre software systems by means of the CVSanaly tool},
	year = {2004},
	address = {Edinburgh, Scotland},
	abstract = {Libre (free, open source) software is one of the paradigmatic cases where heavy use of telematic tools and user-driven software development are key points. This paper proposes a methodology for measuring and analyzing remotely big libre software projects using publicly-available data from their version control repositories. By means of a tool called CVSAnalY that has been implemented following this methodology, measurements and analyses can be made in an automatic and non-intrusive way, providing real-time and historical data about the project and its contributors.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles-koch-barahona_cvsanaly.pdf},
	author = {Gregorio Robles and Koch, Stefan and Jesus M. Gonzalez-Barahona}
}
@conference {Gasser04researchinfrastructure,
	title = {Research Infrastructure for Empirical Science of F/OSS},
	booktitle = {Proc. Intern. Workshop on Mining Software Repositories},
	year = {2004},
	pages = {12-16},
	abstract = {F/OSS research faces a new and unusual situation: the traditional difficulties of gathering enough empirical data have been replaced by issues of dealing with enormous amounts of freely available data from many disparate sources (forums, code, bug reports, etc.) At present no means exist for assembling these data under common access points and frameworks for comparative, longitudinal, and collaborative research. Gathering and maintaining large F/OSS data collections reliably and making them usable present several research challenges. For example, current projects usually rely on {\textquotedblleft}web scraping{\textquotedblright} or on direct access to raw data from groups that generate it, and both of these methods require unique effort for each new corpus, or even for updating existing corpora. In this paper we identify several common needs and critical factors in F/OSS empirical research, and suggest orientations and recommendations for the design of a shared research infrastructure.},
	keywords = {data, Data Collection, empirical, infrastructure},
	attachments = {https://flosshub.org/sites/flosshub.org/files/12ResearchInfrastructure.pdf},
	author = {Gasser, Les and Gabriel Ripoche and Sandusky, Robert J.}
}
@article {flosswp142,
	title = {Sharing and Creating Knowledge in Open-Source Communities The case of KDE},
	year = {2004},
	month = {February},
	abstract = {Our research suggests that knowledge is shared and created in online communities of practice through the establishment of processes and {\textquoteright}technologies{\textquoteright} that enable virtual re-experience for the learners at various levels. It demonstrates that online communities of practice overcome the problem of tacit knowledge transformation through the usage of technological tools, task-related features, analogies and usage scenarios. Three questions guided our research. The first one concentrates on how community members organize content with regard to their daily routines that potentially transforms into knowledge for other members. Secondly, as open-source communities depend on attracting and socializing new members, we inquired how new members are enabled to accumulate the knowledge necessary for becoming a valued member. Thirdly, we asked how members co-create and conceptualize new ideas - create new knowledge - in absence of physical proximity. Re-experience is enabled by modular tasks and transactive group memory, rigid guidance of new members, openness and legitimate peripheral participation, asynchronous communication, and virtual experimentation. Empirical evidence is based on an ethnographic investigation of the KDE project community.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hemreinh.pdf},
	author = {Andrea Hemetsberger}
}
@article {flosswp192,
	title = {SimCode: Agent-based Simulation Modelling of Open-Source Software Development},
	year = {2004},
	month = {November},
	abstract = {We present an original modeling tool, which can be used to study the mechanisms by which free/libre and open source software developers{\textquoteright} code-writing efforts are allocated within open source projects. It is first described analytically in a discrete choice framework, and then simulated using agent-based experiments. Contributions are added sequentially to either existing modules, or to create new modules out of existing ones: as a consequence, the global emerging architecture forms a hierarchical tree. Choices among modules reflect expectations of peer-regard, i.e. developers are more attracted a) to generic modules, b) to launching new ones, and c) to contributing their work to currently active development sites in the project. In this context, we are able - particularly by allowing for the attractiveness of "hot spots"{\textendash} to replicate the high degree of concentration (measured by Gini coefficients) in the distributions of modules sizes. The latter have been found by empirical studies to be a characteristic typical of the code of large projects, such as the Linux kernel. Introducing further a simple social utility function for evaluating the mophology of "software trees," it turns out that the hypothesized developers{\textquoteright} incentive structure that generates high Gini coefficients is not particularly conducive to producing self-organized software code that yields high utility to end-users who want a large and diverse range of applications. Allowing for a simple governance mechanism by the introduction of maintenance rules reveals that "early release" rules can have a positive effect on the social utility rating of the resulting software trees.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dalledavid2.pdf},
	author = {Jean-Michel Dalle}
}
@article {flosswp151,
	title = {Social Forces and Constraint in the Attainment of Community Status},
	year = {2004},
	month = {April},
	abstract = {A study of social forces at work within an online community of free software developers, this paper investigates the manner in which social forces exert pressure that initially shapes and defines an actor{\textquoteright}s status within the community, but eventually constrain that actor{\textquoteright}s movement within a status order. The results of empirical analyses at the dyad level show that, in the process of status attainment, community members tend to evaluate a focal actor{\textquoteright}s reputation according to publicly available social cues. Ironically, these same social cues eventually work to produce stability and constraint in an actor{\textquoteright}s status position by reducing heterogeneity in community status beliefs.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/stewart1.pdf},
	author = {Daniel Stewart}
}
@unpublished {flosswp198,
	title = {The social structure of Free and Open Source software development},
	year = {2004},
	month = {November},
	publisher = {Syracuse University School of Information Studies},
	type = {Working Paper},
	abstract = {Metaphors, such as the Cathedral and Bazaar, used to describe the organization of FLOSS projects typically place them in sharp contrast to proprietary development by emphasizing FLOSS{\textquoteright}s distinctive social and communications structures. But what do we really know about the communication patterns of FLOSS projects? How generalizable are the projects that have been studied? Is there consistency across FLOSS projects? Questioning the assumption of distinctiveness is important because practitioner-advocates from within the FLOSS community rely on features of social structure to describe and account for some of the advantages of FLOSS production. To address this question, we examined 120 project teams from SourceForge, representing a wide range of FLOSS project types, for their communications centralization as revealed in the interactions in the bug tracking system. We found that FLOSS development teams vary widely in their communications centralization, from projects completely centered on one developer to projects that are highly decentralized and exhibit a distributed pattern of conversation between developers and active users.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowstonhowison.pdf},
	author = {Kevin Crowston and James Howison}
}
@article {flosswp153,
	title = {SOS-ware DEVILS[Strategic Open Software DEVelopment ILlnesseS]},
	year = {2004},
	month = {March},
	abstract = {Certain categories of software play a strategic role in contemporary public and private organizations. While software use is accelerated and diffused to more and more people and organisations, software development follows a reverse trend where fewer players form oligopolies, with some of them having almost reached a state of monopoly in certain areas. The evil consequences of such an evolution can be numerous, some of them relate to economic and security dependence and some others to phenomena of knowledge dependence and hysteresis. Within the current paper, we formulate a general framework that categorises the types of illnesses in open strategic software development from a number of viewpoints and the types of damages that could be inflicted to organizations and states as a result of false expectations if these illnesses persist. Finally, we identify the areas where research is considered to be urgently needed.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/blanas1.pdf},
	author = {George Blanas}
}
@article {flosswp152,
	title = {SOS-ware [Strategic Open Software] Perspectives},
	year = {2004},
	month = {March},
	abstract = {Certain types of software play a strategic role in the development of the various aspects of organizational life. One of these roles is knowledge development that can act as a facilitator of economic diamonds. We review the characteristics of strategic software and we try to answer the question whether there can exist open software development that would be able to incorporate these characteristics. Based on this review, and on certain case studies, we present a theory, on how open software might be able to close the gaps in knowledge creation and usage - or the reverse, ie. to become a vehicle for an acceleration of this hysteresis.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/blanas2.pdf},
	author = {George Blanas}
}
@article {flosswp150,
	title = {Status Inertia:The Speed Imperative in the Attainment of Community Status - Paper published as Stewart, Daniel. 2005. "Social Status in an Open Source Community", American Sociological Review, 70:5.},
	year = {2004},
	month = {April},
	abstract = {This paper examines the role of tenure in establishing social status within an online community of free software developers. As tenure increases, an actor{\textquoteright}s status becomes increasingly taken-for-granted, thus making it difficult for actors to generate mobility outside of their current social strata. The results of empirical analyses suggest that the broader community plays a major role in deciding one{\textquoteright}s social position-a judgment that can be made fairly quickly and decisively. Therefore, members of the community who desire high status should work quickly to establish a positive reputation or else run the risk of being cast into an inert low status social position.},
	author = {Daniel Stewart}
}
@article {flosswp172,
	title = {Studying Cooperation and Conflict between Authors with history flow Visualizations},
	year = {2004},
	month = {April},
	abstract = {The Internet has fostered an unconventional and powerful style of collaboration: wiki web sites, where every visitor has the power to become an editor. In this paper we investigate the dynamics of Wikipedia, a prominent, thriving wiki. We make three contributions. First, we introduce a new exploratory data analysis tool, the history flow visualization, which is effective in revealing patterns within the wiki context and which we believe will be useful in other collaborative situations as well. Second, we discuss several collaboration patterns highlighted by this visualization tool and corroborate them with statistical analysis. Third, we discuss the implications of these patterns for the design and governance of online collaborative social spaces. We focus on the relevance of authorship, the value of community surveillance in ameliorating antisocial behavior, and how authors with competing perspectives negotiate their differences. content of the page.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/viegaswattenbergdave.pdf},
	author = {Fernanda Viegas}
}
@article {flosswp155,
	title = {Theory Development for Organizational Platform of User Collaboration Innovation Community},
	year = {2004},
	month = {March},
	abstract = {This study proposes the concept of the ?User Collaboration Innovation Community?, tries to understand this new phenomenon by conducting projects where the opening of source software is the subject of this analysis, borrows the observation variables and propositions adopted by Mintzberg on structures of the innovative organization, and summarizes the opinions of scholars of organizational economics, the relationship between property rights and organization performance. This study further infers a series of conceptual framework and propositions on the relationships among ?organization structure, property right, and organization innovation? for ?the organizational platform of the user collaboration innovation community?. We expect that the construction of this concept framework will function as a concrete description and presentation of the innovation model of the User Collaboration Innovation Community and will serve as a clear path to be followed for continuous research in the future.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/leechan2.pdf},
	author = {Jen-Fang Lee}
}
@proceedings {1189,
	title = {Toward Collaborative Open-Source Technology Transfer},
	year = {2004},
	pages = {34-42},
	abstract = {We analyze several occurrences of open-source technology transfer where research tools or prototypes developed in academic environments are transferred to private actors to be exploited economically. We enlight common characteristics which lead us to suggest that academic duality is a general consequence of the academic design of research tools and prototypes, and that the associated high transfer costs could be reduced first by implementing dual versioning using a dual licensing scheme, by associating a new academic public license with a traditional technology transfer one, and second through the transparent and shared maintenance of products built according to a dual architecture, as it would be precisely allowed by a dedicated collaborative development platform such as LibreSource.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dalle35-43.pdf},
	author = {Jean-Michel Dalle and Guillame Rousseau}
}
@conference {flosswp180,
	title = {Towards a Portfolio of FLOSS project Success Measures},
	booktitle = {Workshop on Open Source Software Engineering, International Conference on Software Engineering},
	year = {2004},
	month = {May},
	abstract = {Project success is one of the most widely used dependent variables in information systems research. However, conventional measures of project success are difficult to apply to Free/Libre Open Source Software projects. In this paper, we present an analysis of four measures of success applied to SourceForge projects: number of members of the extended development community, project activity, bug fixing time and number of downloads. We argue that these four measures provide different insights into the collaboration and control mechanisms of the projects.},
	keywords = {bug fixing, developers, downloads, project success, sourceforge, team, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowston04towards.pdf},
	author = {Kevin Crowston and Hala Annabi and Howison, James and Chengetai Masango}
}
@article {flosswp141,
	title = {Understanding consumers{\textquoteright} collective action on the Internet - a definition and discussion of relevant concepts for research},
	year = {2004},
	month = {February},
	abstract = {This paper offers a new approach for understanding online collaboration and collective action of {\textquoteright}prosumers{\textquoteright}. It is proposed here that theories of collective action and social representations theory, in particular, provide a theoretical framework for studying the structural and social context of online collaboration of consumers, the social actors involved, and how public discourse contributes to shared meaning creation and dissemination in online communities. Processes of naming, classifying, personalizing and institutionalization give their actions ontological reality and contribute to the sustainability of the common effort. An overview and definition of these processes and relevant influencing factors is given and possible indicators of these concepts in open-source communities are highlighted.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hemetsberger3.pdf},
	author = {Andrea Hemetsberger}
}
@article {flosswp165,
	title = {Usability Discussions in Open Source Development},
	year = {2004},
	month = {August},
	abstract = {The public nature of discussion in open source projects provides a valuable resource for understanding the mechanisms of open source software development. In this paper we explore how open source projects address issues of usability. We examine bug reports of several projects to characterise how developers address and resolve issues concerning user interfaces and interaction design. We discuss how bug reporting and discussion systems can be improved to better support bug reporters and open source developers.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/twidalenichols.pdf},
	author = {Michael B Twidale}
}
@proceedings {1199,
	title = {Version Control Tools: A Collaborative Vehicle for Learning in F/OS},
	year = {2004},
	pages = {87-91},
	abstract = {In this paper we explore how version control software participates in learning within free/open source activities (F/OS). We see F/OS in terms of a product, and a community of people engaged in the process of its development, with version control software at the centre of all three activities as they learn and innovate. Learning is analysed through the perspective provided by Bateson{\textquoteright}s Levels of Learning, a relational model that stresses collaboration and conflict as drivers of learning and showing how conflict resolution may lead to higher and more profound or significant learning.},
	keywords = {education},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shaikh88-92.pdf},
	author = {Shaikh, M. and Cornford, T.}
}
@article {flosswp225,
	title = {Viral Contracts or Unenforceable Documents? Contractual Validity of Copyleft Licenses},
	year = {2004},
	month = {August},
	abstract = {This paper asks the question of whether copyleft free software licences constitute valid legal contracts, in particular with regards to the fact that it may create obligations through a distribution chain. There is increasing interest about the non-proprietary licence model expressed in popular documents such as the General Public Licence (GPL), but not enough work has been done in asking perhaps the most important question of all: are these contracts enforceable? Is there really a viral transmission of obligations? To do this the GPL licence will be analysed to try to determine whether or not the terms included are contractually valid.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/guadamuz.pdf},
	author = {Andres Guadamuz-Gonzalez}
}
@article {flosswp171,
	title = {Waiting for F/OSS: Coordinating the Production of Free/Open Source Software},
	year = {2004},
	month = {August},
	abstract = {Trade-off between producing F/OSS module and free-riding is analyzed as game of war of attrition, in which modules developed and potential are heterogeneous. It may be optimal to produce "high-profile" module that creates reputation and signals programming ability. It may be optimal to volunteer strategically for "low-profile" module even if high-profile module is available to speed up development process and reduce costs of waiting. Even if waiting brings opportunity to free ride, there may be rush to develop high-profile module at the opportunity. Model provides explanation for how large-scale F/OSS projects can be coordinated without markets and prices nor hierarchies such as firms.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/stenborg.pdf},
	author = {Markku Stenborg}
}
@proceedings {1192,
	title = {WebDAV based Open Source Collaborative Development Environment},
	year = {2004},
	pages = {53-57},
	abstract = {Open source projects are characterized by their distributed developers, openness, and use of a community-based development process. Successful open source projects such as Apache, Linux, and PHP have a web-based Collaborative Development Environment (CDE) that provides source code repository access, knowledge management, discussion lists, bug tracking, and user support. Distributed software development is also increasingly common for commercial software projects, and benefits from using web-based CDEs. GForge, derived from the SourceForge package, is an open web-based CDE that is seeing widespread open source and commercial use. To support remote authoring of web pages and file contents, as well as remote source code access, GForge uses several network protocols, including SSH/SFTP, CVS pserver, and FTP. These protocols inevitably introduce security risks and add administrative work. We modified GForge to eliminate use of FTP, SSH/SFTP, and CVS protocols, using instead a WebDAV-based integration. The new CDE, called Davenport, uses only the HTTP/WebDAV protocol, and HTTP/WebDAV replaces the other protocols without sacrificing functionality. In this paper we describe the architecture and features of Davenport, and show how WebDAV replaces existing network protocols. We discuss the future development directions of CDEs including integration of client side IDEs and using a CDE as a software test bed.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Kim54-58.pdf},
	author = {Kim, S. and Pan, K. and Whitehead, J.}
}
@article {flosswp139,
	title = {When Consumers Produce on the Internet: The Relationship between Cognitive-affective, Socially-based, and Behavioral Involvement of Prosumers},
	year = {2004},
	month = {February},
	abstract = {This article advances our understanding of the motivational sources for consumer involvement in online joint innovation. The {\textquoteright}free{\textquoteright} or {\textquoteright}open-source{\textquoteright} software movement is the largest socio-technical network and most visible empirical evidence of this new phenomenon. The paper promotes a behavioral view of involvement and offers a conceptualization and empirical evidence of the relationship between cognitive-affective, socially-based and behavioral involvement in online joint production. An Internet survey with 1486 contributors to open-source software revealed that the extent of behavioral involvement is strongly related to the structure and strength of relationships between different motivations. The relationship between concern for self and concern for others especially distinguishes the level of contribution to online projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hemetsberger1.pdf},
	author = {Andrea Hemetsberger}
}
@proceedings {103,
	title = {Why developers participate in open source software projects: an empirical investigation},
	year = {2004},
	keywords = {Survey},
	author = {Il-Horn Hann and Jeff Roberts and Sandra Slaughter}
}
@article {DBLP:journals/electronicmarkets/VemuriB04,
	title = {Will the Open Source Movement Survive a Litigious Society?},
	journal = {Electronic Markets},
	volume = {14},
	number = {2},
	year = {2004},
	pages = {114-123},
	abstract = {Since no one is willing to undertake costly research and development to create innovation, incentives in the form of patents were instituted to motivate R\&D. In software development, contrary to economic intuition, open source software has emerged as a viable alternative source of innovation. The patenting system has performed reasonably well in enhancing many other technologies. Since the mid-1990s patenting of software and business methods is increasingly accepted in the United States. The legitimacy of many of these new patents is subject to controversy and debate. In this paper we examine the trend, rate of litigation and disposition of US patents in the US Federal Courts. We find that litigation rates of software and business method patents is four times that of all other patents and is increasing. A majority of patent litigations are not won by the perpetrator of the lawsuits. The open source software community is not immune to heightened patent litigations. Since software development is incremental, the paths of OSS and commercial development are entwined. The spillover of patent litigation into OSS may have disastrous consequences: It may increase the {\textquoteright}cost{\textquoteright} of OSS, dissuade volunteer developers and make OSS less attractive to users. },
	keywords = {courts, INNOVATION, lawsuit, litigation, patents, software patents},
	author = {Vijay K. Vemuri and Vince Bertone}
}
@article {flosswp154,
	title = {Adaptive entry strategies under dominant standards: Hybrid business models in the Open Source software industry},
	year = {2003},
	month = {March},
	abstract = {Although a growing body of literature is analysing Open Source software (OSS) issues, there is still lack of empirical data on the phenomenon and little is known about firms that enter the software industry by producing under the Open Source license scheme (Open Source firms). This paper is a contribution to fill this gap and focuses on the business models of these firms. We find significant heterogeneity among them, in particular many agents supply both proprietary and Open Source software. We present a model of adoption that studies the intra-firm diffusion of the new paradigm. Explanatory hypotheses are discussed analysing how the characteristics of the Open Source production mode and of network externalities in software demand shape the strategies of firms that entered the OSS field.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bonnacorsirossigiannangeli.pdf},
	author = {Andrea Bonaccorsi}
}
@proceedings {1165,
	title = {Addressing Challenges to Open Source Collaboration with the Semantic Web},
	year = {2003},
	pages = {9-13},
	attachments = {https://flosshub.org/sites/flosshub.org/files/9-13.pdf},
	author = {Ankolekar, A. and Herbsleb, J. D. and Sycara, K.}
}
@proceedings {1175,
	title = {Adopting Open-Source Software Engineering in Computer Science Education},
	year = {2003},
	pages = {85-89},
	keywords = {education},
	attachments = {https://flosshub.org/sites/flosshub.org/files/85-89.pdf},
	author = {Liu, C.}
}
@article {flosswp83,
	title = {The Allocation of Software Development Resources in {\textquoteright}Open Source{\textquoteright} Production},
	year = {2003},
	month = {February},
	abstract = {The paper develops a stochastic simulation model capable of describing the decentralized, micro-level decisions that allocate programming resources both within and among open source/free software (OS/FS) projects, and which critically shape their growth. The core or behavioral kernel of our simulation tool is based on dynamic "growing" trees, and incorporates the effects of the reputational reward structure of OS/FS communities as characterized by Eric S. Raymond (1998). In this regard, our line of investigation also follows recent approaches associated with studies of academic researchers in ?open science? communities. For the purposes of this first step, we mainly focus on showing the ways in which the specific norms of the reward system and organizational rules can shape emergent properties of projects, and we also point to a validation in this framework of the often adovcated, but yet mainly empirical "release early" rule.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dalledavid.pdf},
	author = {Jean-Michel Dalle}
}
@article {flosswp117,
	title = {Alternative Routes in the Digital World: Open Source Software in Africa},
	year = {2003},
	month = {September},
	abstract = {Software allows people to work with computers. Operating Software controls the hardware components and application software provide tools to facilitate and support the users{\textquoteright} work. Most of the softwares are owned by private people or companies and users by licenses to use the software. This type of software is called proprietary or closed source software since the user purchases a license for using the product and the actual product (source code). At present Microsoft and Oracle are the biggest producers of this type software in the world. In the two decades a new approach for software development is emerging. Open Source Software movement is built on the premise that better software is produced when everyone is allowed to modify and change the software. So, in stead of selling user licenses, the product (source code) is distributed. The article discusses the differences between Open and Closed Source Software and reasons that organizations in the African context should decide to embrace the Open Source Software initiative. Several emerging initiatives promoting the use of Open Source Software are considered.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/reijswoudtopi.pdf},
	author = {Victor Van Reijswoud}
}
@article {flosswp102,
	title = {Altruistic individuals, selfish firms? The structure of motivation in Open Source software},
	year = {2003},
	month = {August},
	abstract = {A growing body of economic literature is addressing the incentives of the individuals that take part to the Open Source movement. However, empirical analyses focus on individual developers and neglect firms that do business with Open Source software (OSS). During 2002, we conducted a large-scale survey on 146 Italian firms supplying Open Source solutions in Italy. In this paper our data on firms? motivations are compared with data collected by the surveys made on individual programmers. We aim at analysing the role played by different classes of motivations (social, economic and technological) in determining the involvement of different groups of agents in Open Source},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bnaccorsirossimotivationshort.pdf},
	author = {Andrea Bonaccorsi}
}
@article {flosswp104,
	title = {An analysis of Open Source production in Italy},
	year = {2003},
	month = {August},
	abstract = {Final report of a survey on Italian firms that do business with Open Source software},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bonaccorsirossiccatenieliss.pdf},
	author = {Andrea Bonaccorsi}
}
@article {flosswp219,
	title = {Assessing Free/Open Source Software Quality},
	year = {2003},
	month = {May},
	abstract = {According to its proponents, one of the most acclaimed advantages of Free/Open Source Software (F/OSS) is its superior quality. However, this suggestion is an open issue, since there is little concrete evidence to justify whether F/OSS quality is indeed better or worse than that of proprietary software products. The general perspective of this article is to discuss the current status of F/OSS quality and to assess its performance in various aspects of quality, based on existing literature. Specifically, this article will provide some answers to various questions raised by the assertion concerning the quality of F/OSS. In this regard issues addressed in this article include the quality framework, through which F/OSS quality should be investigated and the performance of F/OSS in various quality factors within this quality framework. Answers to these issues are given by providing evidence from various research papers, empirical studies and reports based on experience about the quality of F/OSS products. The overall results seem to indicate that F/OSS has achieved an acceptable level of quality, although there is more to be done in order to outperform proprietary software.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/samoladasstamelos.pdf},
	author = {Samoladas, Ioannis}
}
@proceedings {1174,
	title = {On Automatic Categorization of Open Source Software},
	year = {2003},
	pages = {79-83},
	attachments = {https://flosshub.org/sites/flosshub.org/files/79-83.pdf},
	author = {Kawaguchi, S. and Garg, P.K. and Matsushita, M. and Inoue, K.}
}
@proceedings {1173,
	title = {Automating the Discovery and Modeling of Open Source Software Development Processes},
	year = {2003},
	pages = {75-78},
	attachments = {https://flosshub.org/sites/flosshub.org/files/75-78.pdf},
	author = {Chris Jensen and Walt Scacchi}
}
@conference {German03automatingthe,
	title = {Automating the measurement of open source projects},
	booktitle = {Proceedings of the 3rd Workshop on Open Source Software Engineering},
	year = {2003},
	note = {"We have chosen to use Evolution to illustrate some of the capabilities of SoftChange. We focus on the data provided by CVS logs and the CVS commit mailing list. Our data includes changes to the CVS repository from April 1998 to January 2003."},
	pages = {63{\textendash}67},
	abstract = {The proliferation of open source projects raises a number of vital economic, social, and software engineering questions that are subject of intense research. Based on experience analyzing numerous open source and commercial projects we propose a set of tools to support extraction and validation of software project data. Such tools would streamline empirical investigation of open source projects and make it possible to test existing and new theories about the nature of open source projects. Our soft- ware includes tools to extract and summarize information from mailing lists, CVS logs, ChangeLog files, and defect tracking databases. More importantly, it cross-links records from various data sources and identifies all contributors for a software change. We illustrate some of the capabilities by analyzing data from Ximian Evolution project.},
	keywords = {bug reports, bug tracking, changelog, cvs, defects, evolution, log files, logs, mailing list, scm, softchange, source code, ximian, ximian evolution},
	attachments = {https://flosshub.org/sites/flosshub.org/files/germanMockus2003.pdf},
	author = {German, Daniel and Audris Mockus}
}
@article {Reinke2003707,
	title = {The availability of source code in relation to timely response to security vulnerabilities},
	journal = {Computers \& Security},
	volume = {22},
	number = {8},
	year = {2003},
	note = {"This paper considers the effects of proprietary software versus non-proprietary software in determining the speed with which a security fix is made available"
"The sources considered are the BugTraq mailing list (available at SecurityFocus.com), the CERT Coordination Center (www.cert.org), and Incidents.org (from the SANS Institute)"
Note that these lists are generic topical discussion lists and not the mailing lists OF a particular open source project.},
	pages = {707 - 724},
	abstract = {Once a vulnerability has been found in an application or service that runs on a computer connected to the Internet, fixing that exploit in a timely fashion is of the utmost importance. There are two parts to fixing vulnerability: a party acting on behalf of the application{\textquoteright}s vendor gives instructions to fix it or makes a patch available that can be downloaded; then someone using that information fixes the computer or application in question. This paper considers the effects of proprietary software versus non-proprietary software in determining the speed with which a security fix is made available, since this can minimize the amount of time that the computer system remains vulnerable.},
	keywords = {bugtraq, cert, email, email archives, mailing list, security, vulnerability},
	issn = {0167-4048},
	doi = {DOI: 10.1016/S0167-4048(03)00011-7},
	url = {http://www.sciencedirect.com/science/article/B6V8G-4B9CV31-C/2/a218fccfaef185af5c122f118b252703},
	author = {John Reinke and Hossein Saiedian}
}
@proceedings {1172,
	title = {Beyond Code: Content Management and the Open Source Development Portal},
	year = {2003},
	pages = {69-73},
	attachments = {https://flosshub.org/sites/flosshub.org/files/69-73.pdf},
	author = {T. Halloran and W. Scherlis and Erenkrantz, J.}
}
@conference {DBLP:conf/ecis/TsiavosH03,
	title = {Beyond good and evil: why open source development for peer-to-peer networks does not necessarily equal to an open society is as imbalanced as copyright law and definitely is not going to make you a better person},
	booktitle = {European Conference on Information Systems (ECIS 2003)},
	year = {2003},
	note = {"In a first stage we collected data related to the development of the Gnutella protocol. The sources included: web sites that were used for hosting forums and file repositories related to the development of the protocol that could be either archived or still operational; messages posted on discussion groups, forums and newsgroups; the design documents of the Gnutella protocol.
In a second stage we gathered material related to the Limewire application. The sources included: operational and archived web sites having been used for the development of the application; applications such as Concurrent Version Systems (CVS) or Bug reporting tools (such as Issuezila), design and implementation documentation and relevant press reports.
The data gathered covered a time span from early 2000 to late November 2002."
"Other sources informed our research and also acted, at times of uncertainty, as forms of triangulation and verification (Lee 1991). These sources include websites such as Slashdot.org and WiredNews; IRC-mediated communications and private messages exchanged between the various developers."},
	month = {2003},
	abstract = {This paper interrogates the claims that open source development is an ideal form of regulatory development. We begin by presenting the literature that offers a framework of modalities of regulation where code, along with laws, markets, and norms shape and influence individual action. Within this framework, it is argued that for an Open Society we need Open Code.	We present the processes through which the Gnutella protocol and the Limewire application are developed by deconstructing the mechanisms of participation and contribution of the individual developers. The techniques of monitoring, modularization and filtering that we identify appear to be inconsistent with open society promises. Instead we suggest a different framing, that of creating nests of interests, whose creators can find refuge from inhabitants of other nests. From that perspective, we suggest that we should stop referring to the war between Copyright and peer-to-peer networks as the battle between good and evil.},
	keywords = {bug reports, cvs, design documents, discussion, discussion forums, documentation, forums, gnutella, issuezilla, limewire, web site},
	attachments = {https://flosshub.org/sites/flosshub.org/files/tsiavosHosein.pdf},
	author = {Prodromos Tsiavos and Ian Hosein}
}
@unpublished {flosswp129,
	title = {The Big Project That Never Ends{\textquoteright}: Role and Task Negotiation Within an Emerging Occupational Community},
	year = {2003},
	month = {December},
	abstract = {This dissertation involved in-depth interviews of over fifty open source developers in two major open source projects. The primary areas of interest were 1) conducting an ethnographic study of the work practices and culture of {\textquoteright}post-burecratic{\textquoteright} organizations to see what lessons these groups may hold for managing intellectual labor and 2) examining whether the open source movement represents a new professional model for software engineering.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mccormick.pdf},
	author = {Chip McCormick}
}
@article {flosswp133,
	title = {Blogging the Market},
	year = {2003},
	month = {December},
	abstract = {Weblogs have been recently characterised as the "open source media". And in much the same way that open source software is been deployed, marketed and sold within both commercial and non-commercial contexts, weblogs can advance both commercial and non-commercial objectives. However, in this primary - research paper, the focus is on the benefits that organisations can seize by embracing weblogs, and how weblogs are bound to revitalise marketplace and workplace conversations. In addition, several case studies are being analysed, ranging from Slashdot and Openflows to Amazon, Macromedia, Groove Networks, and Gizmodo.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dafermos3.pdf},
	author = {George Dafermos}
}
@article {flosswp132,
	title = {Capability Coordination in Modular Organization: Voluntary FS/OSS Production and the Case of Debian GNU/Linux},
	year = {2003},
	month = {November},
	abstract = {The paper analyzes voluntary Free Software/Open Source Software (FS/OSS) organization of work. The empirical setting considered is the Debian GNU/Linux operating system. The paper finds that the production process is hierarchical notwithstanding the modular (nearly decomposable) architecture of software and of voluntary FS/OSS organization. But voluntary FS/OSS project organization is not hierarchical for the same reasons suggested by the most familiar theories of economic organization: hierarchy is justified for coordination of continuous change, rather than for the direction of static production. Hierarchy is ultimately the overhead attached to the benefits engendered by modular organization.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/garzarelligaloppini.pdf},
	author = {Giampaolo Garzarelli}
}
@inbook {flosswp89,
	title = {Chapter 1- Networks of Innovation: Change and Meaning in the Age of the Internet (Oxford University Press)},
	year = {2003},
	month = {June},
	abstract = {Integrating concepts from multiple theoretical disciplines and detailed analyses of the evolution of Internet-related innovations (including computer networking, the World Wide Web and the Linux open source operating system), this book develops foundations for a new theoretical and practical understanding of innovation. It includes a detailed analysis of the Linux open source development model." The table of contents, references, and other related material is available <a href="httP://www.jrc.es/~tuomiil/moreinfo.html">here</a>},
	attachments = {https://flosshub.org/sites/flosshub.org/files/tuomi2.pdf},
	author = {Ilkka Tuomi}
}
@conference {DBLP:conf/csmr/CapiluppiLM03,
	title = {Characteristics of Open Source Projects},
	booktitle = {7th European Conference on Software Maintenance and Reengineering (CSMR{\textquoteright}03)},
	year = {2003},
	note = {"We analyze a sample of around 400 projects from a popular OS project repository. "
no pdf to confirm what projects these are or what the repository is.[ms]},
	pages = {317-},
	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.},
	keywords = {evolution, project success, repository},
	author = {Capiluppi, Andrea and Patricia Lago and Maurizio Morisio}
}
@article {flosswp84,
	title = {Clustering and Dependencies in Free/Open Source Software Development: Methodology and Tools},
	year = {2003},
	note = {source code is the artifact used},
	month = {April},
	abstract = {This paper addresses the problem of measurement of non-monetary economic activity, specifically in the area of free/open source software communities. It describes the problems associated with research on these communities in the absence of measurable monetary transactions, and suggests possible alternatives. A class of techniques using software source code as factual documentation of economic activity is described and a methodology for the extraction, interpretation and analysis of empirical data from software source code is detailed, with the outline of algorithms for identifying collaborative authorship and determining the identity of coherent economic actors in developer communities. Finally, conclusions are drawn from the application of these techniques to a base of software.},
	keywords = {scm, source code, source code analysis},
	url = {http://dxm.org/papers/toulouse2/cluster-final.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cluster-final.pdf},
	author = {Rishab Ayer Ghosh}
}
@article {flosswp109,
	title = {Code, Coding and Coded Perspectives},
	year = {2003},
	month = {January},
	abstract = {Building on computer science I consider code (as opposed to the Web, an instantiation of code) as a new technology of communication. Using the historical and sociological analyses of others, which have examined the results of print on perspectives and society, I offer four scenarios for the results of code. The four scenarios focus on the results of code on quantitative thought: the divergence of scientific perspective with popular reasoning resulting in reduced innovation; a broad-based popular explosion in innovation expanding the basis of reasoning; cypto-anarchy with those empowered by science corrupted with the power; and a loss of certainty of information with a return to tribalism. The last suggests a new era of ignorance, a moment in modern Dark Ages {\textendash} in that an excess of the light of information causes blindness as effectively as its absence. The openness of code is a determinant in the resulting social structure.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/aoir.html},
	author = {L. Jean Camp}
}
@article {flosswp127,
	title = {Collective Action and Communal Resources in Open Source Software Development:The Case of Freenet},
	year = {2003},
	month = {November},
	abstract = {Building on resource mobilization theory, we explore three distinct rewards for individuals to engage in innovative collective action, namely open source software development. The three rewards, which we term communal resources, are reputation, control over technology, and learning opportunities. The collective action (the open source software development project) produces the communal resources in parallel with the actual product (software) and mobilizes programmers to spend time and effort, and contribute their knowledge to the project. Communal resources appear as a byproduct to the production process and represent a public good of second order. We show that they increase in value for individuals along with their involvement in the community. Empirical data from Freenet, an open source software project for peer-to-peer software, illustrates both the levels of involvement and the communal resources.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/vonkroghhaefligerspaeth.pdf},
	author = {Georg von Krogh}
}
@article {146,
	title = {Community, joining, and specialization in open source software innovation: a case study},
	journal = {Research Policy},
	volume = {32},
	number = {7},
	year = {2003},
	note = {first, telephone interviews
"Secondly, we collected the project{\textquoteright}s public email conversations stored in the projects{\textquoteright} 
mailing lists which is archived on Freenet{\textquoteright}s website"
"The third source of data included the history of changes to the software code available 
via the project{\textquoteright}s software repository within the CVS ({\textquoteleft}Concurrent Versioning System{\textquoteright}) source 
code management tool"
"Fourthly, in order obtain contextual understanding of the project we collected publicly 
available documents related to open source in general and to the project in particular. Among 
the most important sources were the Freenet project web pages (e.g. the Frequently Asked 
Questions (FAQ)7), Ian Clarke{\textquoteright}s master thesis (1999), newspaper interviews with the core 
developers, and a technical paper (Clarke, Sandberg, Wiley, \& Hong, 2000) describing the 
Freenet project written by some of the developers."},
	pages = {1217-1241},
	abstract = {This paper develops an inductive theory of the open source software innovation process by focussing on the creation of Freenet, a project aimed at developing a decentralized and anonymous peer-to-peer electronic file sharing network. We are particularly interested in the strategies and processes by which new people join the existing community of software developers, and how they initially contribute code. Analyzing data from multiple sources on the Freenet software development process, we generate the constructs of "joining script", We are grateful to helpful comments from two anonymous reviewers. We also thank Chris Argyris, John Seely Brown, Eric von Hippel, Stefan Haefliger, Petra Kugler, Heike Bruch, Simon Gchter, Simon Peck, and Hari Tsoukas for helpful comments and suggestions. Ben Ho and Craig Lebowitz provided technical assistance with data importation and parsing. We would like to thank Ian Clarke and the Freenet developers for their willingness to participate in our study and providing key insights into the open source development process. Karim R. Lakhani would like to acknowledge the generous support of The Boston Consulting Group and Canada{\textquoteright}s Social Science and Humanities Research Council doctoral fellowship. Georg von Krogh and Sebastian Spaeth acknowledge the generous support from the Research Foundation at the University of St. Gallen.},
	keywords = {cvs, email, email archives, freenet, INNOVATION, mailing lists, roles, source code},
	doi = {http://dx.doi.org/10.1016/S0048-7333(03)00050-7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/krogh03.pdf},
	author = {Georg von Krogh and Spaeth, S. and Karim R Lakhani}
}
@article {flosswp74,
	title = {Community, Joining, and Specialization in Open Source Software Innovation: A Case Study},
	journal = {RP Special Issue},
	year = {2003},
	month = {February},
	abstract = {This paper develops an inductive theory of the open source software innovation process by focussing on the creation of Freenet, a project aimed at developing a decentralized and anonymous peer-to-peer electronic file sharing network. We are particularly interested in the strategies and processes by which new people join the existing community of software developers, and how they initially contribute code. Analyzing data from multiple sources on the Freenet software development process, we generate the constructs of "joining script", "specialization", "contribution barriers", and "feature gifts", and propose relationships among these. Implications for theory and research are discussed.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-vonkroghspaethlakhani.pdf},
	author = {Georg von Krogh}
}
@article {flosswp120,
	title = {Comparing motivations of individual programmers and firms to take part in the Open Source movement. From community to business},
	year = {2003},
	month = {October},
	abstract = {A growing body of economic literature is addressing the incentives of the individuals that take part to the Open Source movement. However, empirical analyses focus on individual developers and neglect firms that do business with Open Source software (OSS). During 2002, we conducted a large-scale survey on 146 Italian firms supplying Open Source solutions in Italy. In this paper our data on firms? motivations are compared with data collected by the surveys made on individual programmers. We aim at analysing the role played by different classes of motivations (social, economic and technological) in determining the involvement of different groups of agents in Open Source activities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bnaccorsirossimotivationlong.pdf},
	author = {Andrea Bonaccorsi}
}
@article {908,
	title = {Continuous Design of Free/Open Source Software: Workshop Report and Research Agenda},
	year = {2003},
	month = {October 15},
	institution = {UCI-UIUC Workshop on Continuous Design of Open Source Software},
	author = {Gasser, Les and Walt Scacchi}
}
@article {flosswp103,
	title = {Contributing to the common pool resources in Open Source software. A comparison between individuals and firms},
	year = {2003},
	month = {August},
	abstract = {This paper studies the contributions to Open Source projects of software firms. Our goal is to analyse whether they follow the same regularities that characterize the behaviour of individual programmers. An exhaustive empirical analysis is carried out using data on project membership, project coordination and contribution efforts of 146 Italian firms that do business with Open Source software. We follow a meta-analytic approach comparing our findings with the results of the surveys conducted on Free Software programmers. Moreover, the availability of the data gathered by Hertel et al. (2003) on 141 developers of the Linux kernel will allow direct comparisons between the two sets.},
	keywords = {developers, linux, linux kernel, Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bnaccorsirossidevelopers.pdf},
	author = {Andrea Bonaccorsi}
}
@article {flosswp136,
	title = {The Contribution of Free Software to Software Evolution},
	year = {2003},
	month = {September},
	abstract = {t is remarkable to think that even without any interest in finding suitable methods and concepts that would allow complex software systems to evolve and remain manageable, the ever growing open source movement has silently managed to establish highly successful evolution techniques over the last two decades. These concepts represent best practices that could be applied equally to a number of today?s most crucial problems concerning the evolution of complex commercial software systems. In this paper, the authors state and explain some of these principles from the perspective of experienced open source developers, and give the rationale as to why the highly dynamic free software development process, as a whole, is entangled with constantly growing code bases and changing project sizes, and how it deals with these successfully.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bauerpizka.pdf},
	author = {Andreas Bauer}
}
@unpublished {flosswp196,
	title = {A critical approach to Open Source Software},
	year = {2003},
	month = {June},
	abstract = {The purpose of this masters{\textquoteright} thesis was to discuss a number of assumptions regarding the benefits of Open Source software projects. By studying what has been written about Open Source combined with a number of own data collections, this thesis argues that: Brooks law is still valid in Open Source projects; Many Open Source projects are failures; Open Source culture is a product of the 90s, not the 70s Open Source is no guarantee for reduced lock-in effects; Our most famous Open Source projects are not built up by nerds working for free, but professionals, employed by commercial companies to contribute to the projects; Large Open Source projects are often hierarchical and bureaucratic Opening your source does not automatically lead to a large number of contributors; Open Source breeds diversity, not a single winner; Open Source projects often targets the community itself, rather than external actors; Companies benefiting from Open Source are often based on traditional business models rather than revolutionary visions. Open Source is not necessarily an efficient way to develop software.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/gorling.pdf},
	author = {Stefan Gorling}
}
@book {122,
	title = {Cyberscience: Research in the Age of the Internet},
	year = {2003},
	publisher = {Austrian Academy of Sciences},
	organization = {Austrian Academy of Sciences},
	address = {Vienna},
	author = {Michael Nentwich}
}
@conference {flosswp137,
	title = {Defining Open Source Software Project Success},
	booktitle = {Twenty-Fourth International Conference on Information Systems},
	year = {2003},
	month = {December},
	abstract = {Information systems success is one of the most widely used dependent variables in information systems research. In this paper, we identify a range of measures that can be used to assess the success of open source software (OSS) projects. We identify measures based on a review of the literature, a consideration of the OSS development process and an analysis of the opinions of OSS developers. For each measure, we provide examples of how they might be used in a study of OSS development.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowstonannabihowison.pdf},
	author = {Kevin Crowston and Hala Annabi and James Howison}
}
@article {flosswp125,
	title = {Determining the Distribution of Maintenance Categories: Survey versus Measurement},
	year = {2003},
	month = {October},
	abstract = {In 1978, Lientz, Swanson, and Tompkins ("LST") published the results of a survey on software maintenance. They found that 17.4\% of maintenance effort was categorized as corrective in nature, 18.2\% as adaptive, 60.3\% as perfective, and 4.1\% was categorized as other. We contrast this survey-based result with our empirical results from the analysis of data for the repeated maintenance of a commercial real-time product and two open-source products, the Linux kernel and GCC. For all three products and at both levels of granularity we considered, our observed distributions of maintenance categories were statistically very highly significantly different from LST. In particular, corrective maintenance was always more than twice the LST value.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lst.preprint.pdf},
	author = {Jin Schach}
}
@conference {1109,
	title = {Distributed Collective Practices and F/OSS Problem Management: Perspective and Methods},
	booktitle = {Conference on Cooperation, Innovation \& Technology (CITE 2003)},
	year = {2003},
	note = {"We have begun studying in detail the general issues raised above using a large collection of research data from the Mozilla project"
"Our Bugzilla snapshot contains over 128,000 problem reports, of which about 88,000 have been resolved"},
	abstract = {This paper presents the state of our research on Distributed Collective Practices (DCPs) in Free/Open-Source Software (F/OSS) projects, focusing on sensemaking and resolution of software problems. We are exploring the hypothesis that variations in the content and in the articulation of these socio-technical processes have an impact on the outcome of the activity of F/OSS collectives, and more specifically on problem resolution. Our preliminary techniques for combining qualitative data analysis with automated process extraction result in a scalable analysis method called Computational Amplification (CA). We are applying CA to 128,000 problem reports from the Mozilla F/OSS project. The paper illustrates how CA is used to create multidimensional process models and shows types of conclusions we can reach.},
	keywords = {Automated process extraction, bug fixing, bug reports, bugzilla, Collective knowledge management, Information extraction from natural language texts, mozilla, Software problem management},
	author = {Gasser, Les and Gabriel Ripoche}
}
@article {flosswp107,
	title = {Dual Licensing in Open Source Software Industry},
	year = {2003},
	month = {January},
	abstract = {This paper analyses how several open source companies use dual licensing: both open source and proprietary licenses for one product. Three case studies based on the experiences of companies Sleepycat Software Inc., MySQL AB, and TrollTech AS illustrate the issue. Especially the legal and economic requirements of dual licensing are identified.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/valimaki.pdf},
	author = {Mikko Valimaki}
}
@article {flosswp118,
	title = {Dynamic Mixed Duopoly: A Model Motivated by Linux vs. Windows},
	year = {2003},
	month = {September},
	abstract = {This paper analyzes a dynamic mixed duopoly in which a profit-maximizing competitor interacts with a competitor that prices at zero (or marginal cost), with the cumulation of output affecting their relative positions over time. The modeling effort is motivated by interactions between Linux, an open-source operating system, and Microsofts Windows in the computer server segment, and consequently emphasizes demand-side learning effects that generate dynamic scale economies (or network externalities). Analytical characterizations of the equilibrium under such conditions are offered, and some comparative static and welfare effects are examined.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/masanellghemawat.pdf},
	author = {Ramon Casadesus-Masanell}
}
@article {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 {1516,
	title = {Free Software Developers as an Occupational Community: Resolving Conflicts and Fostering Collaboration },
	year = {2003},
	month = {11/2003},
	pages = {10 pp},
	abstract = {In this paper, we present results from the study of a free software development virtual organization, the GNU Enterprise (GNUe) project, and how they develop soft ware in a globally distributed free software development project. In particular, examples of how they mitigate and resolve conflict are presented. Conflict arises over the use of a non-free tool to create GNUe graphic, and over the use of a non-free tool for GNUe documentation. The GNUe developers resolve the conflict using internet relay chat (IRC), threaded email discussions, and community digests. We characterize the GNUe developers as an occupational subculture within the occupational community of free/open source software (F/OSS) developers and show how
the beliefs in free software and freedom of choice, and values in cooperative work and community assist GNUe contributors in mitigating and resolving conflict. In addition, we show how, despite fluctuating boundaries of membership in a virtual organization, daily discussions on the GNUe IRC serve to build and perpetuate the global community of GNUe contributors as well as F/OSS developers in general. },
	url = {http://www.ics.uci.edu/~melliott/papers/Elliott-Scacchi-GROUP03.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Elliott-Scacchi-GROUP03.pdf},
	author = {Elliott, Margaret and Walt Scacchi}
}
@article {flosswp95,
	title = {Free Software Development: A Case Study of Software Development in a Virtual Organizational Culture},
	year = {2003},
	month = {April},
	abstract = {This study examines how organizational cultural beliefs and values of a free software virtual organization influence software development processes. This study shows how these beliefs and values are manifested in software development methods, artifacts, and tool choice, as well as how dispersed developers cooperate and resolve conflict in a virtual community.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/eliottscacchi.pdf},
	author = {Margret Elliott}
}
@article {flosswp116,
	title = {Free software engineering: A field to explore},
	year = {2003},
	month = {September},
	abstract = {The challenge of free software is not that of a new competitor who, under the same rules, produces software faster, cheaper and of a better quality. Free software differs from "traditional" software in more fundamental aspects, starting with philosophical reasons and motivations, continuing with new economic and market rules and ending up with a different way of producing software. Software Engineering cannot ignore this phenomenon, and the last five years or so has seen ever more research into all these issues. This article takes a look at the most significant studies in this field and the results they are producing, with a view to providing the reader with a vision of the state of the art and the future prospects of what we have come to call free Software Engineering.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/barahonarobles.pdf},
	author = {Jesus M. Gonzalez-Barahona}
}
@article {flosswp93,
	title = {Free/Open Source Software Development Practices in the Computer Game Community},
	year = {2003},
	month = {April},
	abstract = {This paper provides results from empirical studies that begin to outline some of the processes and practices for how F/OSS systems are developed in different communities. Examples drawn from the world of computer games reveal how processes and practices for the development and propagation of F/OSS technology are intertwined and mutually situated to benefit those motivated to use and contribute to it.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/scacchi4.pdf},
	author = {Walt Scacchi}
}
@article {2003,
	title = {From a Firm-Based to a Community-Based Model of Knowledge Creation: The Case of the Linux Kernel Development},
	journal = {Organization Science},
	volume = {14},
	number = {6},
	year = {2003},
	note = {"we study the Linux development community mainly by analyzing the artifacts that the Linux developers have produced. A key output of knowledge creation activities is the artifacts. The most important artifact, of course, is the Linux operating system source code."
"Along with the source code, a "Credits" text file and a "MAINTAINERS" text file are distributed to the users."
"An equally important artifact is the development activities archived in the Linux-kernel mailing list"..."Using the weekly Linux-kernel email archive for years 1995 to 2000 as a key source of data, we focus on people who have sent at least one email to the Linux-kernel mailing list. "
"In addition, we examine the developers{\textquoteright} demographic distributions, working patterns, and motivations by analyzing the raw data from an on-line survey"},
	pages = {pp. 633-649},
	publisher = {INFORMS},
	abstract = {We propose a new model of knowledge creation in purposeful, loosely coordinated, distributed systems, as an alternative to a firm-based one. Specifically, using the case of the Linux kernel development project, we build a model of community-based, evolutionary knowledge creation to study how thousands of talented volunteers, dispersed across organizational and geographical boundaries, collaborate via the Internet to produce a knowledge-intensive, innovative product of high quality. By comparing and contrasting the Linux model with the traditional/commercial model of software development and firm-based knowledge creation efforts, we show how the proposed model of knowledge creation expands beyond the boundary of the firm. Our model suggests that the product development process can be effectively organized as an evolutionary process of learning driven by criticism and error correction. We conclude by offering some theoretical implications of our community-based model of knowledge creation for the literature of organizational learning, community life, and the uses of knowledge in society.},
	keywords = {credits, developers, email, email archives, knowledge creation, linux kernel, mailing list, maintainers, scm, source code, Survey, Volunteers},
	issn = {10477039},
	url = {http://www.jstor.org/stable/4135125},
	author = {Lee, Gwendolyn K. and Cole, Robert E.}
}
@article {flosswp76,
	title = { Gift economies in the development of open source software: Anthropological reflections},
	journal = {RP Special Issue},
	year = {2003},
	month = {February},
	abstract = {Building on Eric Raymond?s work this article discusses the motivation and rewards that lead some software engineers to participate in the open source movement. It is suggested that software engineers in the open source movement may have sub-groupings which parallel kinship groups such as lineages. Within such groups gift giving is not necessarily or directly reciprocated, instead members work according to the ?axiom of kinship amity? ? direct economic calculation is not appropriate within the group. What Bourdieu calls ?symbolic capital? can be used to understand how people work in order to enhance the reputation (of themselves and their group).},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-zeitlyn.pdf},
	author = {David Zeitlyn}
}
@article {flosswp77,
	title = {Guarding the Commons: How Community Managed Software Projects Protect Their Work},
	journal = {Research Policy},
	volume = {32},
	year = {2003},
	note = {"Data was collected from three primary sources: 1) observation at project and user group meetings, technical presentations and conferences; 2) informant interviews; and 3) project data archived on the Internet that detailed project interactions and structural developments."

"Project data was collected from online archives and included documents such as: mission statements, charters, bylaws, meeting minutes, and mailing list archives."},
	month = {February},
	pages = {1179-1198},
	edition = {7},
	abstract = {Theorists often speculate why open source and free software project contributors give their work away. Although contributors make their work publicly available, they do not forfeit their rights to it. Community managed software projects protect their work by using several legal and normative tactics, which should not be conflated with a disregard for or neglect of intellectual property rights. These tactics allow a project?s intellectual property to be publicly and freely available and yet, governable. Exploration of this seemingly contradictory state may provide new insight into governance models for the management of digital intellectual property.},
	keywords = {Common Pool Resources, email, email archives, intellectual property, mailing list, open source, Public Goods, Software, Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-omahony.pdf},
	author = {Siobhan O{\textquoteright}Mahony}
}
@article {flosswp105,
	title = {How Firm Initiation and Control of Projects Affects Open-Source Development},
	year = {2003},
	month = {May},
	abstract = {After witnessing the success of open-source projects such as Linux and Apache, firms have sought to appropriate the open-source development model and integrate it into their own projects. Firms face a dilemma, however, since their initiation and control of open-source projects affects the traditional open-source development model in significant ways. Once a firm takes the role of starting and guiding an open-source project, the open-source development model that attracted the firm is forever altered. This paper examines the effects commercial firms have on the open-source development model when they initiate and control open-source projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/long.pdf},
	author = {Anthony Long}
}
@article {flosswp75,
	title = {How Open is Open Enough? Melding Proprietary and Open Source Platform Strategies},
	journal = {RP Special Issue},
	year = {2003},
	month = {February},
	abstract = {Computer platforms provide an integrated architecture of hardware and software standards as a basis for developing complementary assets. The most successful platforms were owned by proprietary sponsors that controlled platform evolution and appropriated associated rewards. Responding to the Internet and open source systems, three traditional vendors of proprietary platforms experimented with hybrid strategies which attempted to combine the advantages of open source software while retaining control and differentiation. Such hybrid standards strategies reflect the competing imperatives for adoption and appropriability, and suggest the conditions under which such strategies may be preferable to either the purely open or purely proprietary alternatives.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-west.pdf},
	author = {Joel West}
}
@article {909,
	title = {How open is open enough? Melding proprietary and open source platform strategies},
	journal = {Research Policy},
	volume = {32},
	year = {2003},
	month = {07/2003},
	pages = {1259 - 1285},
	author = {Joel West}
}
@article {116,
	title = {How open source software works: "free" user-to-user assistance},
	journal = {Research Policy},
	volume = {32},
	number = {6},
	year = {2003},
	note = {"The empirical data we collected for study was related to postings to the Apache Usenet help forum, CIWS-U (comp.infosystems.www.servers.unix). "
"For data regarding long-term participation in CIWS-U{\textemdash}who participated, long-term trends, etc.{\textemdash}we examined Usenet posting patterns from 1996 to 1999."
"The Usenet log data was obtained from a World Wide Web service called Deja.com (since acquired by Google)"
survey},
	pages = {923-943},
	abstract = {Research into free and open source software development projects has so far largely focused on how the major tasks of software development are organized and motivated. But a complete project requires the execution of "mundane but necessary" tasks as well. In this paper, we explore how the mundane but necessary task of field support is organized in the case of Apache web server software, and why some project participants are motivated to provide this service gratis to others. We find that the Apache field support system functions effectively. We also find that, when we partition the help system into its component tasks, 98\% of the effort expended by information providers in fact returns direct learning benefits to those providers. This finding considerably reduces the puzzle of why information providers are willing to perform this task "for free." Implications are discussed.},
	keywords = {apache, help, logs, MOTIVATION, participants, Survey, usenet},
	doi = {http://dx.doi.org/10.1016/S0048-7333(02)00095-1},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.110.8172\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lakhani2003.pdf},
	author = {Karim R Lakhani and von Hippel, Eric}
}
@article {69,
	title = {The identity crisis within the IS discipline: Defining and communicating the discipline{\textquoteright}s core properties},
	journal = {MIS Quarterly},
	volume = {27},
	number = {2},
	year = {2003},
	pages = {183{\textendash}194},
	attachments = {https://flosshub.org/sites/flosshub.org/files/westdedrick.pdf},
	author = {Izak Benbasat and Robert W. Zmud}
}
@proceedings {1182,
	title = {Improving Verification, Validation, and Test of the Linux Kernel: the Linux Stabilization Project},
	year = {2003},
	pages = {133-136},
	attachments = {https://flosshub.org/sites/flosshub.org/files/133-136.pdf},
	author = {Craig Thomas}
}
@article {flosswp108,
	title = {The Individual and the Collective in Open Information Communities},
	year = {2003},
	month = {August},
	abstract = {This paper is the written version of an invited talk at the 16th Bled Electronic Conference, Slovenija, June 2003. The text focuses on 2 critical issues for open information communities: how lowering transactions costs linked to becoming an active contributor is an essential factor for their success; and how free (as in freedom) licenses enable new forms of relationships between the individual and the collective. I bring some evidence that this permits to overcome some of the traditional limitations of commons in the physical world. The analysis uses as examples the free Wiki-based encyclopedia Wikipedia and the peer-reviewed free encyclopedia Nupedia, the Slashdot technical news community (commercial), and Web sites using the SPIP free co-operative publishing software.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/aigrain3.pdf},
	author = {Philippe Aigrain}
}
@article {flosswp131,
	title = {Intellectual Property, Open Source and Free Software},
	year = {2003},
	month = {April},
	abstract = {The notion of intellectual property is used in order to create digital commodities. While the commodification of code is useful for certain kinds of knowledge intesive work (the Taylorist forms), it severely disrupts other types of knowledge creation. Applying Scott Lash{\textquoteright}s division of knowledge creation into organisational and disorganisational types, we also gain insight into the different positions towards IP held by different wings of the FOSS community.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/vaden.pdf},
	author = {Tere Vad{\'e}n}
}
@article {flosswp85,
	title = {An Introduction to Open Source Communities},
	year = {2003},
	month = {04/2003},
	institution = {Blue Oxen Associates},
	abstract = {This report describes what open source communities are and how they work. It cites relevant research and presents original case studies of two open source projects: TouchGraph and SquirrelMail. It then identifies patterns of collaboration shared by these projects, and describes how these patterns might apply to other types of communities. Finally, it reviews what is still not well understood about open source communities, and proposes several paths for further research.},
	keywords = {free software foundation directory, freshmeat, fsf, sourceforge, squirrelmail, touchgraph},
	attachments = {https://flosshub.org/sites/flosshub.org/files/blueoxen.pdf},
	author = {Eugene Eric Kim}
}
@proceedings {1180,
	title = {Issues and Experiences in Modeling Open Source Software Development Processes},
	year = {2003},
	pages = {121-125},
	attachments = {https://flosshub.org/sites/flosshub.org/files/121-125.pdf},
	author = {Walt Scacchi}
}
@proceedings {1171,
	title = {Issues in Implementing an Open Source-based XML Repository Manager for Application Maintenance and Adaptation},
	year = {2003},
	pages = {57-62},
	attachments = {https://flosshub.org/sites/flosshub.org/files/57-62.pdf},
	author = {Galatscu, A. and Florian, V. and Costea, L. and Conescu, D.}
}
@unpublished {flosswp164,
	title = {Kategorisierung von Open Source Projekten: Aufbau- und Ablauforganisation (in german) - Categorization of Open Source Projects: Operational and Organizational Structure},
	year = {2003},
	month = {September},
	abstract = {The number of open source projects is growing. The largest part can be found on large develompent portals. But open source is not open source, each project has unique characteristics. This paper examines operational and organizational characteristics, licencing, communication and documentation specifications of open source projects and explains the trove categorization model introduced by SourceForge.net.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/matuska.pdf},
	author = {Martin Matuska}
}
@article {flosswp100,
	title = {The Knowledge Ecology of Open-Source Software Projects},
	year = {2003},
	note = {http://www.mendeley.com/research/the-knowledge-ecology-of-opensource-software-projects/},
	month = {July},
	abstract = {In this paper we characterize the processes of knowledge making in open-source software projects as an ecology of agents, artifacts, rules, resources, activities, practices and interactions. In order to grasp its dynamic features we consider open-source software projects as interactive systems based on dense interactions between humans and technical artifacts within electronic media. Technology, rather than formal or informal organization, embodies most of the conditions for governance in open-source software projects, hence becoming a critical pathway to the understanding of collective task accomplishment, coordination and knowledge making processes. Based on an in-depth analysis of two open-source software projects, we examine three kinds of artifacts, respectively inscribing technical, organizational, and institutional knowledge. Our preliminary findings support the ecological view, that the contradictory requirements of innovation and stability in project-based knowledge making are balanced by mechanisms of variation, selection, and stabilization.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lanzaramorner.pdf},
	author = {Giovan R Lanzara}
}
@article {flosswp128,
	title = {Knowledge Transfer in R\&D Outsourcing (and Linux-Vs-Windows)},
	year = {2003},
	month = {November},
	abstract = {Why did Microsoft not hire all those smart programmers who ended up developing Linux through the internet? Because, we answer, the value of the information about its operating system that Microsoft should have transferred to any of them to render her productive would have been too high compared to her expected individual contribution, so that after writing a contract with Microsoft the typical developer would have run away to sell the acquired knowledge on the market. On the other hand, knowledge transfer in R\&D outsourcing is not always so critical, and for example in the pharmaceutical and chemical industries research contracts are extensively used, usually in the context of a long term relationship between firm and innovator. We analyze this kind of repeated interaction, and find that when the knowledge-transfer problem is not blocking, the firm should transfer to the innovator as much information as it is compatible with the latter{\textquoteright}s incentive constraints.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/modica.pdf},
	author = {Salvatore Modica}
}
@book {flosswp160,
	title = {Legal Issues Relating to Free and Open Source Software},
	year = {2003},
	month = {September},
	abstract = {This is the publication that follows the {\textquoteright}Legal Issues Relating to Free and Open Source Software Conference{\textquoteright} that was held in Brisbane, Australia on 3 July 2002. The conference examined legal and business issues facing the development and implementation of free and open source software. The presenters were lawyers, academics and software developers expert in the area drawn from Australia and the USA.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/opensourcelawbook.pdf},
	author = {Fitzgerald, Brian}
}
@article {flosswp101,
	title = {Licensing schemes in the production and distribution of Open Source software. An empirical investigation},
	year = {2003},
	month = {August},
	abstract = {Contrary to what most people assume, Open source doesn{\textquoteright}t just mean access to the source code. A software is considered Open Source if and only if its distribution terms [i.e. the license] comply with the set of criteria defined by the Open Source Definition (OSD). That is, to say that a code is Open Source is to say that it is subject to a member of a particular category of licenses (McGowan, 2000). As many others in the Open Source field, the research on Open Source licenses suffers from lack of empirical data. Although in the literature there are empirical studies that explore the relationships between license choice and project characteristics (Lerner and Tirole, 2002a), at present we are not aware of surveys that collect data on licensors, that is on firms producing and distributing software on an Open Source basis. This study addresses his shortcoming. We examine the license choice of the firms that supply Open Source products and services and relate it to their structural characteristics, business models and attitudes towards the movement and its community. Between September 2002 and March 2003 we conducted a survey on Italian firms that do business with Open Source software. We asked them to indicate the Open Source licenses with which they work, for the distribution of their software as well as the production process. We made reference to the distinction between copyleft and non-copyleft distribution schemes. Using these data, this paper aims at testing several theoretical hypotheses advanced by the literature on Open Source licenses. In order to make the discussion more lively, for each issue we present the hypothesis and our findings in sequence.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bnaccorsirossilicense.pdf},
	author = {Andrea Bonaccorsi}
}
@article {flosswp99,
	title = {The Linux Managing Model},
	year = {2003},
	month = {July},
	abstract = {This study focuses on the distinguishing traits of the Linux managing model. It introduces the concept of process to capture the idea of impermanence, dissolvability and change. Far from being a predictable flow of programming, assembling and releasing activities, it is suggested that the Linux development process displays a stream of activities that keep feeding back into each other, thus creating a complex and unpredictable outcome. The paper further introduces the concept of contingent response patterns to investigate the interaction flows occurring on the Linux mailing lists and subsume patch postings, bug reports and the associated reviewing and debugging activities under its umbrella. The enactment-selection-retention (ESR) model is subsequently brought forward to conceptualize this process as enactment of programming skills subject to selection activities conducted by Torvalds who retains the selected features and feeds them back to the developers? pool to undergo further enactment activities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/iannacci2.pdf},
	author = {Federico Iannaci}
}
@article {flosswp124,
	title = {Maintainability of the Linux Kernel},
	journal = {Proceedings of the 2nd Workshop on Open Source Software Engineering ICSE2002},
	year = {2003},
	note = {"We have examined 365 versions of Linux.  For every version, we counted the number of 
instances of common (global) coupling between each of the 17 kernel modules and all the other 
modules in that version of Linux."},
	month = {October},
	abstract = {We have examined 365 versions of Linux. For every version, we counted the number of instances of common (global) coupling between each of the 17 kernel modules and all the other modules in that version of Linux. We found that the number of instances of common coupling grows exponentially with version number. This result is significant at the 99.99\% level, and no additional variables are needed to explain this increase. We conclude that, unless Linux is restructured with a bare minimum of common coupling, the dependencies induced by common coupling will, at some future date, make Linux exceedingly hard to maintain without inducing regression faults.},
	keywords = {coupling, kernel, linux, linux kernel, modules, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/linux-maint_0.pdf},
	author = {Schach, Stephen R. and Jin, B. and Wright, D.R.}
}
@article {flosswp122,
	title = {Managing the Boundary of an {\textquoteright}Open{\textquoteright} Project},
	year = {2003},
	month = {October},
	abstract = {In the past ten years, the boundaries between public and open science and commercial research efforts have become more porous. Scholars have thus more critically examined ways in which these two institutional regimes intersect. Large open source software projects have also attracted commercial collaborators and now struggle to develop code in an open public environment that still protects their communal boundaries. This research applies a dynamic social network approach to understand how one community managed software project, Debian, develops a membership process. We examine the project{\textquoteright}s face-to-face social network during a five-year period (1997-2001) to see how changes in the social structure affect the evolution of membership mechanisms and the determination of gatekeepers. While the amount and importance of a contributor{\textquoteright}s work increases the probability that a contributor will become a gatekeeper, those more central in the social network are more likely to become gatekeepers and influence the membership process. A greater understanding of the mechanisms open projects use to manage their boundaries has critical implications for research and knowledge producing communities operating in pluralistic, open and distributed environments.},
	keywords = {debian, membership, social network analysis},
	attachments = {https://flosshub.org/sites/flosshub.org/files/omahonyferraro.pdf},
	author = {Siobhan O{\textquoteright}Mahony}
}
@conference {DBLP:conf/pakdd/ChawlaAD03,
	title = {Mining Open Source Software (OSS) Data Using Association Rules Network},
	booktitle = {Lecture Notes in Computer Science },
	volume = {2637},
	year = {2003},
	pages = {461-466},
	abstract = {The Open Source Software(OSS) movement has attracted considerable attention in the last few years. In this paper we report our results of mining data acquired from SourceForge.net, the largest open source software hosting website. In the process we introduce Association Rules Network(ARN), a (hyper)graphical model to represent a special class of association rules. Using ARNs we discover important relationships between the attributes of successful OSS projects. We verify and validate these relationships using Factor Analysis, a classical statistical technique related to Singular Value Decomposition(SVD).},
	keywords = {arn, association rules, factor analysis, project success, sourceforge, svd},
	author = {Sanjay Chawla and Bavani Arunasalam and Joseph G. Davis}
}
@article {flosswp87,
	title = {Modularity in Action: GNU/Linux and Free/Open Source Software Development Model Unleashed},
	year = {2003},
	month = {May},
	abstract = {Organizational and managerial theories of modularity applied to the design and production of complex artifacts are used to interpret the rise and success of Free/Open Source Software. Strengths and risks of the adoption of a modular approach in software project management are introduced and are related to the achievements of the GNU/Linux project. It is suggested that mindful implementation of the principles of modularity may improve the rate of success of many Free/Open Source software projects. Authors suggest a possible revision towards an improved theory of modularity that may be extended also to settings different from software production.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/narduzzorossi.pdf},
	author = {Alessandro Narduzzo}
}
@article {flosswp78,
	title = {Motivation of Software Developers in Open Source Projects: An Internet-based Survey of Contributors to the Linux Kernel},
	journal = {RP Special Issue},
	year = {2003},
	month = {February},
	abstract = {The motives of 141 contributors to a large Open Source Software project (the Linux kernel) was explored with an internet-based questionnaire study. Measured factors were both derived from discussions within the Linux community as well as from models from social sciences. Participants? engagement was particularly determined by their identification as a Linux developer, by pragmatic motives to improve own software, and by their tolerance of time investments. Moreover, some of the software development was accomplished by teams. Activities in these teams were particularly determined by participants? evaluation of the team goals as well as by their perceived indispensability and self-efficacy.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-hertelniednerherrmann.pdf},
	author = {Guido Hertel}
}
@article {flosswp115,
	title = {Neither market or hierarchy or network: The emerging bazaar governance},
	year = {2003},
	month = {September},
	abstract = {Despite the growing body of literature describing the open-source phenomenon, few contributions have been theoretically grounded and research has largely focused on the software industry. Drawing on transaction cost economics, we go beyond these limitations and advance that open source constitutes a new generic governance structure?which we label bazaar governance? based on a specific contract. We characterize this structure in terms of its strengths and weaknesses and in comparison with market, firm and network structures. We consider how bazaar governance is actualized within an industry and the institutional entrepreneur?s crucial role in this process. Finally, we propose that bazaar governance has a profound impact on the structure of the industry in which it is introduced.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/demillecocq.pdf},
	author = {Benoit Demil}
}
@article {flosswp130,
	title = {Open Source as a Complex Adaptive System - Published in Emergence 5 (3)},
	year = {2003},
	month = {November},
	abstract = {The Open Source community and its activities can be considered to have the characteristics of a system. The Open Source system is distinctive because it is neither controlled by a central authority that defines strategy and organization nor totally chaotic. It can be placed at a middle position between a planned system and a chaotic one. In this sort of position there are non-formal rules which allow the system to produce significant results. The Complex Adaptive System theory can be used to better understand and analyze the Open Source system. This work presents a description of the main characteristics of the functioning of the Open Source community regarding its organizational structure and development process. The concept of complex adaptive system is then introduced and its functioning mechanisms briefly described. Finally, we will interpret the characteristics of the Open Source community in the context of complex adaptive systems theory.},
	author = {Moreno Muffatto}
}
@article {flosswp82,
	title = {Open Source as a Signalling Device - An Economic Analysis},
	year = {2003},
	month = {March},
	abstract = {Open source projects produce goods or standards that do not allow for the appropriation of private returns by those who contribute to these projects. In this paper we analyze why programmers will nevertheless invest their time and effort to code open source software. We argue that the particular way in which open source projects are managed and especially how contributions are attributed to individual agents, allows the best programmers to create a signal that more mediocre programmers cannot achieve. Through setting themselves apart they can turn this signal into monetary rewards that correspond to their superior capabilities. With this incentive they will forgo the immediate rewards they could earn in software companies producing proprietary software by restricting the access to the source code of their product. Whenever institutional arrangements are in place that enable the acquisition of such a signal and the subsequent substitution into monetary rewards, the contribution to open source projects and the resulting public good is a feasible outcome that can be explained by standard economic theory.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/leemoisaweiss.pdf},
	author = {Samuel Lee}
}
@article {flosswp112,
	title = {Open Source: Beyond the Fairytales},
	year = {2003},
	month = {August},
	abstract = {Open source is a software development model that to many is synonymous with a free and free-wheeling operating system juggernaut destined to upend current computer markets. IBM is embracing Linux to unify its hardware product line, and Microsoft is screaming that open source is anti-American and destructive of intellectual property. Analysts and executive have been gathering around open source to find out what it?s all about, and people like Eric Raymond and Linus Torvalds once indistinguishable from society?s stereotype of the elfin programmers working in the dark on the software that powers the digital age have become heroes, spokesmen, and leaders in the new age of anti-monopolistic software. But is this narrow view adequate? Open source, for corporations, has more to do with a particular business strategy than it does with any specific technology. In fact, technology is just another piece of the puzzle for a successful technology company certainly it?s a necessary piece, but often it?s not the distinguishing piece.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/gabrielgoldman.pdf},
	author = {Richard P Gabriel}
}
@proceedings {1184,
	title = {Is Open Source Essentially an Agile Method?},
	year = {2003},
	pages = {143-147},
	attachments = {https://flosshub.org/sites/flosshub.org/files/143-147.pdf},
	author = {Warsta, Juhani and Abrahamsson, Pekka}
}
@proceedings {1183,
	title = {Open Source Methodologies and Mission Critical Software Development},
	year = {2003},
	pages = {137-141},
	attachments = {https://flosshub.org/sites/flosshub.org/files/137-141.pdf},
	author = {Voightman, M.P. and Coleman, C.P.}
}
@article {flosswp179,
	title = {Open Source Software - An Economic Assessment},
	year = {2003},
	month = {December},
	abstract = {This study examines whether or not Open Source Software represents an economically suitable alternative to the proprietary commercial software market in terms of creating value-added and economic efficiency. Whereas no significant differences between both production processes are seen for customized software, the study comes to the conclusion that serious economic problems can occur in the field of packaged software. Starting from a discussion on how licenses like the GPL affect the ability to price software (which is usually below economic production costs), the impact of below cost pricing on the coordination capacity of software markets (customer sovereignty, resource allocation, income distribution, adaptability and innovation) and the sustainability of complementary strategies of Open Source business models (with and without cross subsidization of the non-market OSS-core) are described. Throughout the study, the role of the pricing system within a market economy is stressed considering the specific characteristics of software as an economic good. Aspects other than economic are not taken into account.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kalweykoothslangenfurth.pdf},
	author = {Nadine Kalwey}
}
@article {62,
	title = {Open Source Software and the {\textquoteleft}{\textquoteleft}Private-Collective{\textquoteright}{\textquoteright} Innovation Model: Issues for Organization Science},
	journal = {Organization Science},
	volume = {14},
	number = {2},
	year = {2003},
	pages = {208--223},
	publisher = {Tims Institute of Management Science},
	author = {von Hippel, Eric and Georg von Krogh}
}
@article {flosswp119,
	title = {Open Source Software as an organisational Technology},
	year = {2003},
	month = {July},
	abstract = {This paper is still relatively preliminary, yet it provides a decent introduction to open source, as well as including discussion on various economic issues, contained in the following sections: The benefits of Open Source, Possible incentives that encourage contribution, Barriers to widespread implementation of Open Source.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/barnes.pdf},
	author = {Jonathan Barnes}
}
@article {flosswp88,
	title = {Open Source Software can Improve the Health of the Bank Balance - The Beaumont Hospital Experience},
	year = {2003},
	month = {May},
	abstract = {This study describes the implementation of open source software in a large Irish public sector organization, Beaumont Hospital. The findings reveal a radical shift in open source deployment from invisible horizontal infrastructure systems to highly visible vertical applications. The case study describes the implementation of these systems, the difficulties encountered, and also the benefits in terms of astonishing cost savings of ?13m over 5 years. . Given that Beaumont were already receiving academic pricing discounts for many of their original proprietary closed source applications, the savings for a typical commercial organization could be even higher. The study also identifies the primary drivers in the move to OSS, namely principle, pragmatism and practicality. The study also indicates how a typical company can contribute back to the OSS community in their own unique way, by distributing applications form their own domain of expertise, rather than having to make detailed code contributions to the original code base.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/fitzgeraldkenny.pdf},
	author = {Fitzgerald, Brian}
}
@unpublished {flosswp212,
	title = {Open Source Software Development},
	year = {2003},
	month = {May},
	abstract = {This paper examines applies basic economic theory to Open Source Software Development. Through examination of rational actor behavior I show why economically motivated individuals and firms choose to develop code that to be given away freely. It also examines the various Open Source licenses, including the two most common, the Free Software Foundation?s General Public License (GPL) and Berkeley Software Distribution (BSD) License. Included are case studies to illustrate the workings of Open Source Software projects and how profit seeking firms have attached themselves to them. These case studies include the Apache Web Server, Mozilla, IBM, Microsoft?s Shared Source Initiative, and Red Hat. The associated business plans are also discussed. An executive summary precedes the paper and a glossary is attached to the end.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/greenberg.pdf},
	author = {Robert Greenberg}
}
@article {123,
	title = {Open source software development and Lotka{\textquoteright}s Law: Bibliometric patterns in programming},
	journal = {Journal of the American Society for Information Science and Technology},
	volume = {54},
	number = {2},
	year = {2003},
	note = {"Two lead- ing metadata repositories are the Linux Software Map (LSM) and Sourceforge, both of which were used for this research."
"For this article, we examined data listing the number of registered developers for each software project hosted by Sourceforge."
"The data we obtained from the LSM collection were taken mainly from the Author: field of LSM records. The Author: field in LSM records gives us the ability to track the author of record for a software package. LSM metadata also include a list of maintainers, primary software distribution sites, date of update and other items."
"The data we obtained from Sourceforge consist of a list of developer ID numbers, followed by the number of projects on which the individual is listed as a developer, then the number of projects on which the individual is listed as an administrator. These data were provided for all 33,892 individuals registered to work on projects hosted by Sourceforge in July 2001."},
	pages = {169-178},
	abstract = {This research applies Lotka{\textquoteright}s Law to metadata on open source software development. Lotka{\textquoteright}s Law predicts the proportion of authors at different levels of productivity. Open source software development harnesses the creativity of thousands of programmers worldwide, is important to the progress of the Internet and many other computing environments, and yet has not been widely researched. We examine metadata from the Linux Software Map (LSM), which documents many open source projects, and Sourceforge, one of the largest resources for open source developers. Authoring patterns found are comparable to prior studies of Lotka{\textquoteright}s Law for scientific and scholarly publishing. Lotka{\textquoteright}s Law was found to be effective in understanding software development productivity patterns, and offer promise in predicting aggregate behavior of open source developers.},
	keywords = {developers, linux, linux software map, lsm, sourceforge, team size},
	doi = {10.1002/asi.10177},
	author = {Newby, G. B. and Greenberg, J. and Jones, P.}
}
@article {flosswp71,
	title = {Open Source Software Development: Some Historical Perspectives},
	year = {2003},
	month = {January},
	abstract = {In this paper we suggest that historical studies of technology can help us to account for some, perplexing (at least for traditional economic reasoning) features of open source software development. When looked in historical perspective, open source software seems to be a particular case of what Robert Allen has termed "collective invention". We explore the interpretive value of this historical parallel in detail, comparing open source software with two remarkable episodes of nineteenth century technical advances.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nuvolari.pdf},
	author = {Alessandro Nuvolari}
}
@proceedings {95,
	title = {Open source software in the trenches: Lessons from a large-scale OSS implementation},
	year = {2003},
	keywords = {open source},
	author = {Fitzgerald, Brian and Kenny, Tony}
}
@article {flosswp90,
	title = {Open Source vs Closed Source Software: Public Policies in the Software Market},
	year = {2003},
	month = {June},
	abstract = {This paper analyses the impact of public policies supporting open source software (OSS). Users can be divided between those who know about the existence of OSS, the informed adopters, and the uninformed ones; the presence of uniformed users yields to market failures that justify government intervention. We study three policies: i) mandatory adoption, when government forces public agencies, schools and universities to adopt OSS, ii) information campaign, when the government informs the uninformed users about the existence and the characteristics of OSS and, iii) subsidisation, when consumers are payed a subsidy when adopting OSS. We show that the second policy enhances welfare, the third is always welfare decreasing while mandatory adoption can be either good or bad for society depending on the number of informed and uninformed adopters.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cominomanenti.pdf},
	author = {Stefano Comino}
}
@proceedings {1166,
	title = {Open-Source Development Processes and Tools},
	year = {2003},
	pages = {15-18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/15-18.pdf},
	author = {Boldyreff, Cornelia and Lavery, J. and Nutter, David and Rank, Stephen}
}
@article {1116,
	title = {Organizational learning in open-source software projects: an analysis of debugging data},
	journal = {IEEE Transactions on Engineering Management},
	volume = {50},
	year = {2003},
	month = {11/2003},
	pages = {485 - 493},
	abstract = {This paper studies organizational learning effects in open-source programming projects. Working with data from the Apache and Mozilla projects, the study focuses on three aspects of open-source development. The first is the use of the open-source approach as a hedge against system complexity. The second is the adaptive learning mechanisms realized by the debugging process. The last is the learning curve effects of project-specific experience on bug cycle times. The results indicate that while open-source development is subject to positive learning effects, these effects are not universal, with some projects deriving more benefit than others.},
	keywords = {apache, bugs, complexity, mozilla},
	issn = {0018-9391},
	doi = {10.1109/TEM.2003.820136},
	author = {Huntley, C.L.}
}
@conference {Wynn03organizationalstructure,
	title = {Organizational Structure of Open Source Projects: A Life Cycle Approach},
	booktitle = {Proceedings of 7th Annual Conference of the Southern Association for Information Systems},
	year = {2003},
	note = {"The three graphs in Figure 2 below were taken from smoothed download counts for existing open source projects on Sourceforge.net"
"A random sample of 150 open source projects will be taken from data provided by Sourceforge.net. Each project will be evaluated to determine their current life cycle stage (where possible) using download counts. Next, the project admins, developers, and several identifiable users for each evaluated project will be contacted via email to request completing a brief questionnaire to measure the current focus of the project, formal structure, division of labor, leader role, coordination, level of commitment, user success, and developer success. "},
	abstract = {The structure of open source project communities is discussed in relation to the organizational life cycle. In lieu of sales figures, the download counts for each project are used to identify the life cycle stage of a random sample of open source projects. A research model is proposed that attempts to measure the fit between the life cycle stage and the specific organizational characteristics of these projects (focus, division of labor, role of the leader, level of commitment, and coordination/control) as an indicator of the success of a project as measured by the satisfaction and involvement of both developers and users.},
	keywords = {division of labor, downloads, growth, interview, leadership, life cycle, lifecycle, project success, roles, sourceforge, Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wynn2004.pdf},
	author = {Donald E. Wynn}
}
@article {flosswp97,
	title = {Participatory Usability: supporting proactive users},
	journal = {Proceedings of the 4th Annual Conference of the ACM Special Interest Group on Computer Human Interaction - New Zealand Chapter (CHINZ{\textquoteright}03)},
	year = {2003},
	month = {June},
	pages = {63{\textendash}68},
	publisher = {ACM SIGCHI New Zealand.},
	abstract = {After software has been released the opportunities for users to influence development can often be limited. In this paper we review the research on post-deployment usability and make explicit its connections to open source software development. We describe issues involved in the design of end-user reporting tools with reference to the Safari web browser and a digital library prototype.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nicholsmckaytwidale.pdf},
	author = {David M Nichols and Dana McKay and Michael B Twidale}
}
@unpublished {flosswp86,
	title = {Puzzling with a top-down Blueprint and a bottom-up Network: An explorative analysis of the Open Source World using ITIL and Social Network Analysis},
	year = {2003},
	month = {February},
	abstract = {This paper explains some of the necessary tasks that need to be performed for the construction and maintenance of software. These necessary activities are abstracted from ITIL, a best- practice {\textquoteright}blueprint{\textquoteright}, that is often used by IT companies to structure their processes. Next, using Social Network Analysis, an investigation is conducted to asses how the activities that ITIL describes are performed in the open source {\textquoteright}network{\textquoteright}.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/meerman2.pdf},
	author = {Sanne Te Meerman}
}
@proceedings {1177,
	title = {Quality and the Reliance on Individuals in Free Software Projects},
	year = {2003},
	month = {2003},
	pages = {105-109},
	attachments = {https://flosshub.org/sites/flosshub.org/files/105-109.pdf},
	author = {Martin Michlmayr and Hill, B.M.}
}
@article {flosswp123,
	title = {Quality Impacts of Clandestine Common Coupling},
	year = {2003},
	month = {October},
	abstract = {The number of instances of common coupling between a module M and the other modules can be changed without any explicit change to M; this is termed "clandestine common coupling." This paper presents results from a study of clandestine common coupling in 391 versions of Linux. Specifically, the common coupling between each of 5332 kernel modules and the rest of the product as a whole was measured. In more than half of the new versions, a change in common coupling was observed, even though none of the modules themselves was changed.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/clandestine.preprint.pdf},
	author = {Jin Schach}
}
@proceedings {1170,
	title = {Release Management Within Open Source Projects},
	year = {2003},
	pages = {51-55},
	attachments = {https://flosshub.org/sites/flosshub.org/files/51-55.pdf},
	author = {Erenkrantz, J.}
}
@article {flosswp80,
	title = {Re-working by the Linux Kernel developers},
	year = {2003},
	month = {February},
	abstract = {Technology design is generally a matter of re-working existing systems rather than the designing of entirely novel artifacts. In this paper I explore part of a computer operating system called Linux that is designed to be re-worked by its users, a process I call {\textquoteright}designing for redesign{\textquoteright}. I examine the practices of reworking within this development effort using some concepts gleaned from activity theory, a meta-theoretical model that particularly focuses on the simultaneously material and conceptual aspects of artifacts. This work is two-fold; first to examine design as part of a larger activity of re-working, and second, to begin to put together a model of socio-technical activity that incorporates the complex epistemological and ontological conditions that characterize current human conditions. Understanding the sociality and materiality of "knowing" and "doing" in technologized society means unpacking what we mean when we talk of {\textquoteright}access{\textquoteright} and understanding {\textquoteright}use{\textquoteright} as often an activity of re-working.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ratto.pdf},
	author = {Matt Ratto}
}
@article {96,
	title = {Satisfying heterogeneous user needs via innovation toolkits: the case of Apache security software},
	journal = {Research Policy},
	volume = {32},
	number = {7},
	year = {2003},
	note = {Times Cited: 30},
	pages = {1199-1215},
	abstract = {Manufacturers customarily provide only a few product variants to address the average needs of users in the major segments of markets they serve. When user needs are highly heterogeneous, this approach leaves many seriously dissatisfied. One solution is to enable users to modify products on their own using "innovation toolkits." We explore the effectiveness of this solution in an empirical study of Apache security software. We find high heterogeneity of need in that field, and also find that users modifying their own software to be significantly more satisfied than non-innovating users. We propose that the "user toolkits" solution will be useful in many markets characterized by heterogeneous demand. (C) 2003 Elsevier Science B.V. All rights reserved.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-vonhippelfranke_0.pdf},
	author = {Nik Franke and von Hippel, Eric}
}
@article {flosswp96,
	title = {Simulating an Automated Approach to Discovery and Modeling of Open Source Software Development Processes},
	year = {2003},
	month = {March},
	abstract = {This paper describes a new approach to process discovery that examines the Internet information spaces of open source software development projects. Such knowledge can then be employed to determine the requirements and design of automated process discovery and modeling mechanisms that can be applied to Web-based open source software development projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/jensenscacchi.pdf},
	author = {Chris Jensen}
}
@article {flosswp135,
	title = {Socialization in Open Technical Communities},
	year = {2003},
	month = {December},
	abstract = {While many definitions of openness focus on the character and licenses of the software products, relatively few directly address the character of the social organization that develops those products. This essay offers a definition of openness and considers how that characteristic affects the recruitment and socialization of newcomers to such organizations. The relevance of socialization is clear when one consider the growth of on-line communities, and precariousness of membership in voluntary organizations. I then suggest that "forking," a split of the communities, is integral to the definition of openness and a possible vector of communicating social norms between communities, and that a significant difference between open technical communities and some other open/voluntary communities is the internal orientation of status seeking within the community.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/voluntary.html},
	author = {Joseph Reagle}
}
@article {1877,
	title = {Software security for open-source systems},
	journal = {IEEE Security \& Privacy Magazine},
	volume = {1},
	year = {2003},
	month = {01/2003},
	pages = {38 - 45},
	abstract = {Debate over whether open-source software development leads to more or less secure software has raged for years. Neither is intrinsically correct: open-source software gives both attackers and defenders greater power over system security. Fortunately, several security-enhancing technologies for open-source systems can help defenders improve their security.
},
	keywords = {security},
	issn = {1540-7993},
	doi = {10.1109/MSECP.2003.1176994},
	author = {Cowan, C.}
}
@proceedings {1178,
	title = {Studying the evolution of libre software projects using publicly available data},
	year = {2003},
	month = {2003},
	pages = {111-115},
	attachments = {https://flosshub.org/sites/flosshub.org/files/111-115.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Jose Centeno-Gonz{\'a}lez and Vicente Matellan-Olivera and Luis Rodero-Merino}
}
@conference {1248,
	title = {Supporting Distributed and Decentralized Projects: Drawing Lessons from the Open Source Community},
	booktitle = {1st Workshop on Open Source in an Industrial Context},
	year = {2003},
	note = {"We begin the remainder of the paper with discussion of a survey of open source projects, showing similarities that have arisen in tool usage"},
	month = {10/2003},
	abstract = {Open source projects are typically organized in a distributed and decentralized manner. These factors strongly determine the processes followed and constrain the types of tools that can be utilized. This paper explores how distribution and decentralization have affected processes and tools in existing open source projects with the goals of summarizing the lessons learned and identifying opportunities for improving both. Issues considered include decision-making, accountability, communication, awareness, rationale, managing source code, testing, and release management.},
	keywords = {abiword, apache, debian, freebsd, kde, linux, mozilla, mysql, perl, PHP, postgresql, python, subversion, tomcat, tools},
	attachments = {https://flosshub.org/sites/flosshub.org/files/erenkrantz2003.pdf},
	author = {Erenkrantz, J. and Taylor, R.N.}
}
@proceedings {74,
	title = {Survival of open-source projects: A population ecology perspective},
	year = {2003},
	keywords = {open source},
	author = {Chengalur-Smith, Shobha and Sidorova, Anna}
}
@proceedings {1167,
	title = {Tools for light-weight knowledge sharing in open-source software development},
	year = {2003},
	pages = {25-29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/25-29.pdf},
	author = {Cubranic, Davor and Holmes, Reid and Ying, Annie and Murphy, Gail C.}
}
@proceedings {1179,
	title = {Toward an Empirical Assessment of the Benefits of Open Source Software},
	year = {2003},
	pages = {117-120},
	attachments = {https://flosshub.org/sites/flosshub.org/files/117-120.pdf},
	author = {Russo, Barbara and Zuliani, P. and Succi, G.}
}
@conference {Ye:2003:TUM:776816.776867,
	title = {Toward an understanding of the motivation Open Source Software developers},
	booktitle = {Proceedings of the 25th International Conference on Software Engineering},
	series = {ICSE {\textquoteright}03},
	year = {2003},
	note = {"Analyzing the emails sent to the mailing fist is one way of understanding the structure of the community."
"Table 2 displays the number of code contributions made by members to the GIMP system and the defined roles of those contributing members. We counted the number of contributions made by each person by analyzing the change log of the system."},
	pages = {419{\textendash}429},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {An Open Source Software (OSS) project is unlikely to be successful unless there is an accompanied community that provides the platform for developers and users to collaborate. Members of such communities are volunteers whose motivation to participate and contribute is of essential importance to the success of OSS projects. In this paper, we aim to create an understanding of what motivates people to participate in OSS communities. We theorize that learning is one of the motivational forces. Our theory is grounded in the learning theory of Legitimate Peripheral Participation, and is supported by analyzing the social structure of OSS communities and the co-evolution between OSS systems and communities. We also discuss practical implications of our theory for creating and maintaining sustainable OSS communities as well as for software engineering research and education.},
	keywords = {change log, COMMUNITY, contributions, contributors, developers, email, email archives, evolution, gimp, log files, mailing list, roles, source code},
	isbn = {0-7695-1877-X},
	url = {http://portal.acm.org/citation.cfm?id=776816.776867},
	attachments = {https://flosshub.org/sites/flosshub.org/files/YeKishida.pdf},
	author = {Ye, Yunwen and Kishida, Kouichi}
}
@proceedings {1168,
	title = {Towards a Product Model of Open Source Software in a Commercial Environment},
	year = {2003},
	pages = {31-37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/31-37.pdf},
	author = {Deng, J. and Seifert, T. and Vogel, S.}
}
@article {100,
	title = {Trust, control and the role of interorganizational systems in electronic partnerships},
	journal = {Information Systems Journal},
	volume = {13},
	number = {2},
	year = {2003},
	note = {Times Cited: 12},
	pages = {159-190},
	abstract = {To survive and thrive in today{\textquoteright}s competitive marketplace, organizations are increasingly migrating to new organizational structures in which partnerships and interorganizational systems (IOSs) are becoming more important. The success of these partnerships depends on both trust and control - complex constructs that act on and shape each other over time. Many organizations assume that high levels of trust are necessary for net-enabled electronic partnerships. We examine this assumption from two perspectives: the initial decision to enter into a partnership or alliance, and its ongoing operation. Our findings suggest that researchers have treated trust simplistically, failing to distinguish the need for trust (which is inversely related to the organization{\textquoteright}s ability to control its partners) and the level of trust (which is an actual quantity that may change during the lifetime of the partnership). In many organizations, there is a gap between these two trust dimensions, which management attempts to close by changing the level of control. In this process, the IOS is key. To understand the relationship of IOS use to trust and control, we applied structured content analysis and analytic induction to 16 published case studies and used the results to create a framework for relating trust and control. At the heart of the framework is the recognition that trust and control are not simple substitutes for each other. Rather, they form a dialectic, where it makes sense to consider each construct only in relationship to the other. Using the framework, we identify areas for follow-up research and suggestions for practitioners.},
	author = {Gallivan, M. J. and Depledge, G.}
}
@article {flosswp94,
	title = {Understanding Free/Open Source Software Evolution: Applying, Breaking and Rethinking the Laws of Software Evolution},
	year = {2003},
	month = {April},
	abstract = {This study examines whether the evolution of open source software conforms to the laws of software evolution that have been in development for more than 30 years. Given evidence and data that may not conform, it becomes necessary to consider how the laws and theory might be revamped to better account for the data that characterizes both conventional closed source software and F/OSS system evolution.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/scacchi3.pdf},
	author = {Walt Scacchi}
}
@inbook {flosswp126,
	title = {Understanding the Nature of Participation \& Coordination in Open and Gated Source Software Development Communities},
	year = {2003},
	month = {June},
	abstract = {This paper explores the motivations of participants from two software development communities and finds that most participants are motivated by either a need to use the software or an enjoyment of programming. The latter group, hobbyists or enthusiasts, are critical to the long-term viability and sustainability of open source software code: they take on tasks that might otherwise go undone, are largely need-neutral as they make decisions, and express a desire to maintain the simplicity, elegance, and modularity of the code. The motives of hobbyist evolve over time; most join the community because they have a need for the software and stay because they enjoy programming in the context of a particular community. Governance and licensing structures affect this evolution.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shah3.pdf},
	author = {Sonali Shah}
}
@article {Nichols02usabilityand,
	title = {The Usability of Open Source Software},
	journal = {First Monday},
	volume = {8},
	year = {2003},
	abstract = {Open source communities have successfully developed a great deal of software although most computer users only use proprietary applications. The usability of open source software is often regarded as one reason for this limited distribution. In this paper we review the existing evidence of the usability of open source software and discuss how the characteristics of open source development influence usability. We describe how existing human-computer interaction techniques can be used to leverage distributed networked communities, of developers and users, to address issues of usability.},
	url = {http://firstmonday.org/article/view/1018/939},
	author = {David M Nichols and Michael B Twidale}
}
@article {101,
	title = {The user-developer communication process: a critical case study},
	journal = {Information Systems Journal},
	volume = {13},
	number = {1},
	year = {2003},
	note = {Times Cited: 5},
	pages = {37-68},
	abstract = {Although user participation in systems development is widely believed to have positive impacts on user acceptance, it does not guarantee success and there is still much that we do not know about how and why user participation sometimes delivers positive benefits, but not always. Much of the prior research on user participation assumes that user-developer communication will ensure that the resulting system will be designed to meet users{\textquoteright} needs and will be accepted by them. The nature and quality of the communication between users and developers, however, remains an understudied aspect of user participation. In this paper, we focus on the user-developer communication process. We propose a process model that delineates four stages of communication between users and software developers, and we argue that these stages must occur for user participation to lead to effective outcomes. To illustrate our model, we apply it to analyse a {\textquoteright}critical case study{\textquoteright} of a software project that failed despite high levels of user involvement. We show that when {\textquoteright}communication lapses{\textquoteright} occurred in several of the user-developer communication stages, developers failed to be informed regarding the underlying reasons that users avoided the system. Based on the insights from this case study, we advise researchers and practitioners how to leverage the potential benefits of user participation, rather than take them for granted.},
	author = {Gallivan, M. J. and Keil, M.}
}
@article {flosswp106,
	title = {Version Management Tools: CVS to BK in the Linux Kernel},
	year = {2003},
	month = {May},
	abstract = {Version management tools might be seen as a prerequisite for open source development today as projects become too large to be managed by maintainers alone. Yet the OS process depends on fluid coordination and collaboration, with the underlying qualities of this process based on firm trust and respect for fellow developers. This paper is a study of how debate over version tools reflects governance and decision making in an OS community. The paper is based on a study of the Linux kernel community as it first saw a partial acceptance of the CVS tool, and then later adopted BK. The paper explains the adoption processes in relation to governance concerns, licence issue, and questions of technical performance.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shaikhcornford.pdf},
	author = {Maha Shaikh}
}
@proceedings {1181,
	title = {Version Management Tools: CVS to BK in the Linux Kernel},
	year = {2003},
	pages = {127-131},
	attachments = {https://flosshub.org/sites/flosshub.org/files/127-131.pdf},
	author = {Shaikh, M. and Cornford, T.}
}
@proceedings {1169,
	title = {The Virtual Organizational Culture of a Free Software Development Community},
	year = {2003},
	pages = {45-49},
	attachments = {https://flosshub.org/sites/flosshub.org/files/45-49.pdf},
	author = {Margret Elliott}
}
@article {flosswp52,
	title = {Why open source software can succeed},
	journal = {RP Special Issue},
	year = {2003},
	month = {February},
	abstract = {The paper discusses three key economic problems raised by the emergence and diffusion of open source software: motivation, coordination, and diffusion under a dominant standard. First the movement took off through the activity of a software development community that deliberately did not follow profit motivations. Second, a hierarchical coordination emerged without the support of an organization with proprietary rights. Third, Linux and other open source systems diffused in an evnvironment dominated by established proprietary standards, which benefited from significant increasing returns. The paper show that recent developments in the theory of critical mass in the diffusion of technologies with network externality may help to explain these phenomena.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-bonaccorsirossi.pdf},
	author = {Andrea Bonaccorsi}
}
@proceedings {1176,
	title = {Why OSS Folks Think SE Folks Are Clue-Impaired},
	year = {2003},
	pages = {91-97},
	attachments = {https://flosshub.org/sites/flosshub.org/files/91-97.pdf},
	author = {Bart Massey}
}
@conference {1160,
	title = {Adopting OSS Methods by Adopting OSS Tools},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {The open source movement has created and used a set of software engineering tools with features that fit the characteristics of open source development processes. To a large extent, the open source culture and methodology are conveyed to new developers via the toolset itself, and through the demonstrated usage of these tools on existing projects. The rapid and wide adoption of open source tools stands in stark contrast to the difficulties encountered in adopting traditional CASE tools. This paper explores the characteristics that make these tools adoptable and how adopting them may influence software development processes.},
	keywords = {ant, argouml, bugzilla, cactus, cvs, developers, eclipse, emacs, email, faq, junit, mailing lists, make, netbeans, package management, rpm, scarab, subversion, teams, tools, torque, WORK},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Robbins.pdf},
	author = {Robbins, Jason E.}
}
@article {65,
	title = {Analyzing cloning evolution in the Linux kernel},
	journal = {Information and Software Technology},
	volume = {44},
	number = {13},
	year = {2002},
	pages = {755-765},
	abstract = {Identifying code duplication in large multi-platform software systems is a challenging problem. This is due to a variety of reasons including the presence of high-level programming languages and structures interleaved with hardware-dependent low-level resources and assembler code, the use of GUI-based configuration scripts generating commands to compile the system, and the extremely high number of possible different configurations. This paper studies the extent and the evolution of code duplications in the Linux kernel. Linux is a large, multi-platform software system; it is based on the Open Source concept, and so there are no obstacles in discussing its implementation. In addition, it is decidedly too large to be examined manually: the current Linux kernel release (2.4.18) is about three million LOCs. Nineteen releases, from 2.4.0 to 2.4.18, were processed and analyzed, identifying code duplication among Linux subsystems by means of a metric-based approach. The obtained results support the hypothesis that the Linux system does not contain a relevant fraction of code duplication. Furthermore, code duplication tends to remain stable across releases, thus suggesting a fairly stable structure, evolving smoothly without any evidence of degradation. (C) 2002 Elsevier Science B.V. All rights reserved.},
	keywords = {cvs, kernel, lines of code, linux, loc, project success, source code},
	url = {web.soccerlab.polymtl.ca/~antoniol/publications/.../infsoft2002.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/infsoft2002.pdf},
	author = {Antoniol, G. and Villano, U. and Merlo, E. and Di Penta, M.}
}
@article {flosswp40,
	title = {Cave or Community? An Empirical Examination of 100 Mature Open Source Projects},
	journal = {First Monday},
	volume = {7},
	number = {6},
	year = {2002},
	note = {The author conducts an empirical study of the top 100 mature projects on SourceForge.net to develop an understanding of the F/OSS community. The author sought empirical evidence that would help us understand which is more common- the cave (i.e., lone producer) or the community in F/OSS development. Some key findings include: first, most F/OSS programs are developed by individuals, rather than communities. Second, most OSS programs do not generate a lot of discussion. Third, products with more developers tend to be viewed and downloaded more often. Fourth, the number of developers associated with a project is unrelated to the age of the project.},
	month = {06/2002},
	abstract = {Starting with Eric Raymond{\textquoteright}s groundbreaking work, "The Cathedral and the Bazaar", open-source software (OSS) has commonly been regarded as work produced by a community of developers. Yet, given the nature of software programs, one also hears of developers with no lives that work very hard to achieve great product results. In this paper, I sought empirical evidence that would help us understand which is more common - the cave (i.e., lone producer) or the community. Based on a study of the top 100 mature products on Sourceforge, I find a few surprising things. First, most OSS programs are developed by individuals, rather than communities. The median number of developers in the 100 projects I looked at was 4 and the mode was 1 - numbers much lower than previous numbers reported for highly successful projects! Second, most OSS programs do not generate a lot of discussion. Third, products with more developers tend to be viewed and downloaded more often. Fourth, the number of developers associated with a project was positively correlated to the age of the project. Fifth, the larger the project, the smaller the percent of project administrators.},
	keywords = {age, contributors, developers, project success, registration, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/krishnamurthy.pdf},
	author = {Sandeep Krishnamurthy}
}
@unpublished {flosswp65,
	title = {Characteristics and Applicability of Open Source-Based Product Development Model in Other than Software Industries},
	year = {2002},
	month = {October},
	abstract = {The main objective of this research is to examine the Open Source product development paradigm and its applicability to other than software industries. First part of this paper examines the NPD process, its evolution and main characteristics during years. Than approaches to product development adopted in Open Source projects are presented, with emphasis on the managerial and knowledge related issues, as those are focal to NPD. In the second part Open Source-based Product Development Model is being constructed and its applicability to other than open source software industry verified.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/siedlok.pdf},
	author = {Franciszek Siedlok}
}
@conference {1153,
	title = {Characterizing the OSS process},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	note = {"We have considered two well-known Open Source portals (FreshMeat [1] and SourceForge [2] )."
"Using pseudo-random sampling we have selected a sample of 400 projects (mostly from FreshMeat). Each project is described by several variables (programming language, type of license, size of source code, type of documentation available and others). By indirect means (analysis of the Changelog file, or CVS) it is also possible to compute the number of people working on the project, and the number of external contributors. From FreshMeat we get both a vitality index, that considers the number of releases per time period, and a popularity index, which is a first measure of the interest of users to the project (project URL hits, mixed with subscriptions to it)."},
	abstract = {The Open Source model of software development has gained the attention of both the business, the practitioners{\textquoteright} and the research communities. The Open Source process has been described by the seminal paper by Eric Raymond [4] and [5]. However, sound empirical studies are still very limited [3], [6].
Our goal is to investigate the OS process by empirical means, to analyze, characterize it, and possibly model it with quantitative models. It should be noted that the Open Source process provides open process and product data, and therefore is a rare opportunity for empirical research.
Our initial research focus is on the characterization of the process, starting from the evolution of OS projects. In traditional projects, a significant number of releases in a short time is usually considered an instability factor [7] and [8], while in the OSS community, it is an evidence of vitality, shows the commitment of the authors and the power of attraction of other programmers [9]. Is it possible to characterize the vitality of projects? And, can vitality be traced to some other characteristics of a project?},
	keywords = {bugs, change log, classification, cvs, downloads, freshmeat, metadata, patches, popularity, project success, release history, sourceforge, vitality},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CapiluppiLagoMorisio.pdf},
	author = {Capiluppi, Andrea and Patricia Lago and Maurizio Morisio}
}
@article {70,
	title = {Coase{\textquoteright}s penguin, or, Linux and The Nature of the Firm},
	journal = {Yale Law Journal},
	volume = {112},
	number = {3},
	year = {2002},
	month = {Dec},
	pages = {369-+},
	abstract = {For decades our common understanding of the organization of economic production has been that individuals order their productive activities in one of two ways: either as employees in firms, following the directions of managers, or as individuals in markets, following price signals. This dichotomy was first identified in the early work of Ronald Coase and was developed most explicitly in the work of institutional economist Oliver Williamson. Recently, public attention has focused on a fifteen-year-old phenomenon called free software or open source software. This phenomenon involves thousands, or even tens of thousands, of computer programmers who collaborate on large- and small-scale projects without traditional firm-based or market-based ownership of the resulting product. This Article explains why free software is only one example of a much broader social-economic phenomenon emerging in the digitally networked. environment, a third mode of production that the author calls "commons-based peer production." The Article begins by demonstrating the widespread use of commons-based peer production on the Internet through a number of detailed examples, such as Wikipedia, Slashdot the Open Directory Project, and Google. The Article uses these examples to reveal fundamental characteristics of commons-based peer production that distinguish it from the property- and contract-based modes of firms and markets. The central distinguishing characteristic. is that groups of individuals successfully collaborate on large-scale projects following a diverse cluster of motivational drives and social signals rather than market prices or managerial commands. The Article then explains why this mode has systematic advantages over markets and managerial hierarchies in the digitally networked environment when the object of production is information or culture. First, peer production has an advantage in what the author calls "information opportunity cost," because it loses less information about who might be the best person for a given job. Second, there are substantial increasing allocation gains to be captured from allowing large clusters of potential contributors to interact with large clusters of information resources in search of new projects and opportunities for collaboration. The Article concludes with an overview of how these models use a variety of technological, social, and formal strategies to overcome the collective action problems usually solved in managerial and market-based systems by property, contract, and managerial commands.},
	isbn = {0044-0094},
	author = {Benkler, Y.}
}
@article {Stamelos02codequality,
	title = {Code quality analysis in open source software development},
	journal = {Information Systems Journal},
	volume = {12},
	year = {2002},
	note = {"For our case study, we have used Logiscope{\quotesinglbase} (Telelogic, 2000), a comprehensive set of tools able to perform, automatically, code measurement and comparison with user-defined programming standards"
"Using Logiscope, we examined a sample of 100 C programs found in the SUSE Linux 6.0 release."
metrics collected:
number of statements
cyclomatic complexity
maximum levels
number of paths
unconditional jumps
comment frequency
vocabulary frequency
program length
average size
number of inputs/outputs},
	pages = {43{\textendash}60},
	abstract = {Proponents of open source style software development claim that better software is produced using this model compared with the traditional closed model. However, there is little empirical evidence in support of these claims. In this paper, we present the results of a pilot case study aiming: (a) to understand the implications of structural quality; and (b) to figure out the benefits of structural quality analysis of the code delivered by open source style development. To this end, we have measured quality characteristics of 100 applications written for Linux, using a software measurement tool, and compared the results with the industrial standard that is proposed by the tool. Another target of this case study was to investigate the issue of modularity in open source as this characteristic is being considered crucial by the proponents of open source for this type of software development. We have empirically assessed the relationship between the size of the application components and the delivered quality measured through user satisfaction. We have determined that, up to a certain extent, the average component size of an application is negatively related to the user satisfaction for this application.},
	keywords = {C, Code quality characteristics, functions, linux, metrics, open source development, software measurement, structural code analysis, Suse, user satisfaction},
	author = {Ioannis Stamelos and Lefteris Angelis and Apostolos Oikonomou and Georgios L. Bleris}
}
@conference {1161,
	title = {The Coming Software Revolution},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {The growing adoption of collaborative software development will change the global software industry by altering its economics of scale, location, and price. The growth of non-proprietary code will depress prices in the proprietary sector, and the possession of source code will enable the growth of more software industrial centers around the world; their emergence will threaten the business of current leaders. National governments which see themselves as disadvantaged or even threatened by the current software powers will encourage collaborative software development and the services that this development model drives. Only world-wide draconic legislation by the current software powers has any hope of preserving the status quo.},
	keywords = {ECONOMICS, management, open source, politics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Rosenberg.pdf},
	author = {Rosenberg, D.K.}
}
@article {flosswp37,
	title = {Community Effort in Online Groups? Who Does the Work and Why?},
	year = {2002},
	month = {February},
	abstract = {In this paper, the authors consider how the formal leadership role, personal and community benefits, and community characteristics influence the effort members put into helping their online groups. Results from a survey of Internet listserv owners and other members suggest that though owners, who have a formal leadership role, do more of the effortful community building work than do regular members, other members also take on some of the work. Moreover, members who value different benefits are likely to contribute to the development on an online community in different ways.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/butler.pdf},
	author = {Brian Butler}
}
@article {flosswp38,
	title = {Competing on Open Source: Strategies and Practise},
	year = {2002},
	month = {January},
	abstract = {This paper seeks to address the following issues: How do firms compete with open source? What resources become critical in managing their growth? What strategies do they adopt to co-exist with dominant proprietary software firms? How do they interface with communities of practice to exploit network externalities? What strategies do they adopt to lock-in developers? Based on a multiple case analysis the authors seek to draw initial conclusions about the key strategic aspects that underlie the open source initiatives. Finally they describe how for-profit firms can establish and sustain open source practice.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/madanmohan.pdf},
	author = {T.R. Madanmohan}
}
@article {flosswp57,
	title = {A contribution to the understanding of illegal copying of software: empirical and analytical evidence against conventional wisdom},
	year = {2002},
	month = {June},
	abstract = {The paper analyzes different variables that affect the dynamics among copyrights, illegal copying and software market creation. There is empirical and analytical evidence supporting three major findings. First, proprietary source companies use illegal copying as a source of market creation in the early stages of development of the market. Second, this strategy has positive effects in the software market in the long-term. Third, in presence of an Open Source alternative, proprietary source companies need to use their illegal user base in order to compete better and this strategy becomes optimal.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osorio.pdf},
	author = {Carlos Osorio-Urzua}
}
@article {flosswp53,
	title = {Counting potatoes: The size of Debian 2.2},
	year = {2002},
	month = {March},
	abstract = {Debian is possibly the largest free software distribution, with well over 2,800 source packages in the latest stable release (Debian 2.2) and more than 4,000 source packages in the release currently in preparation. But, how large is "the largest"? We show that Debian 2.2 includes more than 55,000,000 physical SLOC (almost twice than Red Hat 7.1, released about 8 months later), showing that the Debian development model (based on the work of a large group of voluntary developers spread around the world) is at least as capable as other development methods (like the more centralized one) to manage distributions of this size. It is also shown that if Debian had been developed using traditional proprietary methods, that its cost would be close to $1.9 billion. In addition, we offer both an analysis of the programming languages used in the distribution.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/counting-potatoes.html},
	author = {Jesus M. Gonzalez-Barahona}
}
@article {1115,
	title = {De-Bugging open source software licensing},
	journal = {University of Pittsburgh Law Review},
	volume = {64},
	number = {1},
	year = {2002},
	month = {2002},
	pages = {75-103},
	keywords = {licensing},
	attachments = {https://flosshub.org/sites/flosshub.org/files/debugopensource.pdf},
	author = {Gomulkiewicz, R.W.}
}
@article {flosswp64,
	title = {Development Costs and Open Source Software},
	year = {2002},
	month = {November},
	abstract = {This paper analyzes the effect of the development cost on an open source software enhancement that is developed by individual programmers in an Internet community. It considers a situation in which each programmer{\textquoteright}s cost of development is common knowledge but his valuation of the enhancement is his private information, with other programmers knowing about only its distribution. Depending on the distribution functions of programmers{\textquoteright} valuations of the enhancement, a programmer with a lower development cost may have a less incentive to develop. As the development cost decreases, the enhancement may be less likely to be developed, and some programmers may be worse off.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/xxu.pdf},
	author = {Xiaopeng Xu}
}
@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 {flosswp121,
	title = {Forms of labour in information systems},
	year = {2002},
	month = {July},
	abstract = {The idea of technology, including information technology, as a human construction is taken as the basis for the themes to be developed. The possibility of constructing an information dynamic, continuous with the dynamic of capitalism, is considered. Differentiations are made between forms of semiotic labour: semantic from syntactic labour and communal from universal labour. Information retrieval systems and the departure from the labour theory of copyright are considered in relation to the forms of labour distinguished. An information dynamic is constructed. The potential and limitations of syntactic labour are considered. The analytic value of the distinctions developed is differentiated from the possible predictive power of the dynamic indicated.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper135.html},
	author = {Julian Warner}
}
@unpublished {flosswp81,
	title = {A Framework for Open Source Projects},
	year = {2002},
	month = {November},
	abstract = {The historical roots of Open Source are outlined. A comparison between Open Source projects and classical projects highlights strengths and weaknesses of both, and defines their attributes. Existing Open Source theories are evaluated, and the requirements for a framework for Open Source projects are determined. The framework introduces the notions of actors, roles, areas, processes and tools, and depicts their interrelationships in a matrix. Each aspect of the framework is then further developed to serve both as a conceptual foundation for Open Source and a help for organizing and managing Open Source projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rotfuss.pdf},
	author = {Gregor J Rothfuss}
}
@article {flosswp61,
	title = {A Framework for Understanding GPL copylefting vs. non copylefting licenses},
	year = {2002},
	month = {October},
	abstract = {This article provides a framework to discuss the consequences of licensing choices that are applied to publicly funded libre choices. It disucsses these choices from the angle of general public interest and policy. It concludes that one is led to prefer GPL for any libre software component that is publicly funded and when its is providing functionality as part of the common infrastructure of the information society.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/aigrain2.pdf},
	author = {Philippe Aigrain}
}
@article {46,
	title = {Free/Libre and Open Source Software: Survey and Study},
	year = {2002},
	author = {Rishab Ayer Ghosh and R{\"u}dige Glott and Krieger, B. and Gregorio Robles}
}
@article {flosswp110,
	title = {The Governance of Code: Open Land vs. UCITA Land},
	year = {2002},
	month = {September},
	abstract = {Imagine two network societies. In one society, the transfer of information and use of software is governed by the various licenses used to protect open code today. For convenience, we dub this society "Open Land". The other society recently passed a law identical to the new Uniform Computer Information Transactions Act ("UCITA", passed in two U.S. states and pending in several others) to control its information and computer software. We will call this society "UCITA Land". This paper looks at the ways in which Open Land and UCITA Land differ. Although it might initially seem that a licensing framework is trivial in terms of the actual conduct of society, we posit that such frameworks in many ways define the mode of governance of network society. The establishment of a market involves the development of a bundle of rights that both create property and define the rules under which property-based transactions might occur. In Open Land and UCITA Land, fundamentally different approaches to the establishment of those rights lead to vastly different societies.},
	author = {Serena Syme}
}
@book {flosswp72,
	title = {Government Policy Towards Open Source Software (Edited Book)},
	year = {2002},
	month = {December},
	abstract = {Can open source software?software that is usually available without charge and that individuals are free to modify?survive against the fierce competition of proprietary software, such as Microsoft Windows? Should the government intervene on its behalf? This book addresses a host of issues raised by the rapid growth of open source software, including government subsidies for research and development, government procurement policy, and patent and copyright policy. Contributors offer diverse perspectives on a phenomenon that has become a lightning rod for controversy in the field of information technology.},
	author = {Robert Hahn}
}
@article {flosswp51,
	title = {Government Preferences for Promoting Open-Source Software: A Solution in Search of a Problem},
	year = {2002},
	month = {April},
	abstract = {Governments around the world are making or considering efforts to promote open-source software at he expense of proprietary software. This article examines the economic basis for these kinds of government interventions in the market. The article discusses the industrial organization and performance of the proprietary software business and describes how the open-source movement produces and distributes software. It then surveys current government proposals and initiatives to support open-source software and examines whether there is a significant market failure that would justify such intervention in the software industry. The article concludes that there is no evidence of any significant market failures in the provision of commercial software and no evidence that the establishment of policy preferences in favor of open-source software on the part of governments would increase consumer welfare.},
	author = {Bernard Reddy}
}
@article {1095,
	title = {High Quality and Open Source Software Practices},
	journal = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	note = {"We examined the publicly visible portions of these projects from November 2001 through March 2002, ...The SLOC counts for the predominate languages are shown},
	month = {2002},
	abstract = {Surveys suggest that, according to various metrics, the quality and dependability of today{\textquoteright}s open source software is roughly on par with commercial and government developed software. What are the prospects for advancing to much higher levels of quality in open source software? More specifically, what attributes must be possessed by quality-related interventions for them to be feasibly adoptable in open source practice? In order to identify some of these attributes, we conducted a preliminary survey of the quality practices of a number of successful open source projects. We focus, in particular, on attributes related to adoptability by the open source practitioner community.},
	keywords = {apache, bug report, bug tracker, bug tracking system, feature requests, gcc, gnome, kde, lines of code, linux, loc, mozilla, netbeans, perl, position paper, python, sloc, source code, Survey, tomcat, xfree86},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HalloranScherlis.pdf},
	author = {T. Halloran and W. Scherlis}
}
@article {flosswp44,
	title = {Horizontal innovation networks- by and for users},
	year = {2002},
	month = {June},
	abstract = {Innovation development, production, distribution and consumption networks can be built up horizontally with actors consisting only of innovation users. User innovation networks can function entirely independently of manufacturers when (1) at least some users have sufficient incentive to innovate, (2) at least some users have an incentive to voluntarily reveal their innovations, and (3) diffusion of innovations by users is low cost and can compete with commercial production and distribution. In this paper we explore the empirical evidence related to each of these matters and conclude that conditions favorable to user innovation networks are often present in the economy.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/vonhippel3.pdf},
	author = {von Hippel, Eric}
}
@article {flosswp23,
	title = {Institutional Entrepreneurship in the Sponsorship of Common Technological Standards: The Case of SUN Microsystems and Java},
	year = {2002},
	month = {January},
	abstract = {Institutional entrepreneurship implicit in a firm{\textquoteright}s sponsorship of its technology as a common standard is beset by several challenges. These challenges arise from a standard{\textquoteright}s property to enable and constrain even as potential competitors agree to cooperate on its creation. Our exploration of Sun Microsystems{\textquoteright}s sponsorship of its Java technology suggests that standards-in-the-making generate seeds of self-destruction. Our study also identifies the social and political skills that a sponsor deploys to address these challenges.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/sunjavagarud1.pdf},
	author = {Raghu Garud}
}
@article {flosswp41,
	title = {Knowing in Practice: Enacting a Collective Capability in Distributed Organizing},
	journal = {Organization Science},
	volume = {13},
	number = {3},
	year = {2002},
	month = {05/2002},
	abstract = {In this paper, I outline a perspective on knowing in practice which highlights the essential role of human action in knowing how to get things done in complex organizational work. The perspective suggests that knowing is not a static embedded ca- pability or stable disposition of actors, but rather an ongoing social accomplishment, constituted and reconstituted as actors engage the world in practice. In interpreting the findings of an empirical study conducted in a geographically dispersed high- tech organization, I suggest that the competence to do global product development is both collective and distributed, grounded in the everyday practices of organizational members. I conclude by discussing some of the research implications of a perspective on organizational knowing in practice.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/orlikowski.pdf},
	author = {Wanda Orlikowski}
}
@article {flosswp224,
	title = {New economic models, new economy for software},
	year = {2002},
	month = {December},
	abstract = {This report proposes some presentations and analysis of several FLOSS business models, and a juridical analysis of the use of Free licenses. We propose also a synthetical analysis of the impact of FLOSS on the computer industry.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/fichier_rapporte.pdf},
	author = {Melanie Clement-Fontaine}
}
@conference {1163,
	title = {On the Nonmaintainability of Open-Source Software},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	note = {"We downloaded 365 versions of Linux. For each version in turn, we examined the 17 kernel modules and counted the number of lines of code in each module. Then we counted the number of instances of common (global) coupling between each of the kernel modules and all the other modules in that version of Linux. We obtained two primary results."},
	keywords = {Common coupling, coupling, lines of code, linux, linux kernel, loc, metrics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/SchachOffutt.pdf},
	author = {Schach, Stephen R. and Offutt, Jeff}
}
@article {flosswp92,
	title = {Open Acquisition: Combining Open Source Software Development with System Acquisition},
	year = {2002},
	month = {July},
	abstract = {This study explores and develops concepts leading to the combination of best practices from open source software development (OSSD) projects with emerging capabilities for virtual system acquisition. Virtual system acquisition is an evolving approach to demonstrate significant improvements in reducing the cost and cycle time for acquiring software-intensive systems, while improving their quality. It employs techniques from electronic government applications together with those from OSSD.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/scacchi2.pdf},
	author = {Walt Scacchi}
}
@article {flosswp91,
	title = {Open EC/B: A Case Study in Electronic Commerce and Open Source Software Development},
	year = {2002},
	month = {June},
	abstract = {This study investigates how to understand and transform an organizational system for internal or external operations using Open Source E-Commerce or E-Business capabilities. The objective is to identify and characterize the organizational resources and development capabilities that lie at the center of the initiative.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/scacchi1.pdf},
	author = {Walt Scacchi}
}
@article {flosswp42,
	title = {Open Source and the Network Society},
	year = {2002},
	month = {June},
	abstract = {This paper discusses how the open source movement can be regarded as a civil society. Through an analysis and discussion of the recent development in society the context and to a certain extent the prerequisites surrounding the open source movement will be presented. The analysis and discussion of the open source movement will both derive advantage from this basis as well as throw new light back on the recent development in society.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/pedersen.pdf},
	author = {Soren Thing Pedersen}
}
@article {hansen2002open,
	title = {The Open Source approach{\textemdash}opportunities and limitations with respect to security and privacy},
	journal = {Computers \& Security},
	volume = {21},
	number = {5},
	year = {2002},
	pages = {461{\textendash}471},
	publisher = {Elsevier},
	abstract = {Today{\textquoteright}s software often does not even fulfil basic security or privacy requirements. Some people regard the open source paradigm as the solution to this problem. First, we carefully explain the security and privacy aspects of open source, which in particular offer the possibility for a dramatic increase in trustworthiness for and autonomy of the user. We show which expectations for an improvement of the software trustworthiness dilemma are realistic. Finally, we describe measures necessary for developing secure and trustworthy open source systems.},
	keywords = {security},
	url = {https://dud.inf.tu-dresden.de/literatur/HaKP_02OpenSource_0214.doc},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HaKP_02OpenSource_0214.doc},
	author = {Hansen, Marit and K{\"o}hntopp, Kristian and Pfitzmann, Andreas}
}
@article {81,
	title = {Open source, open standards},
	journal = {Information Technology and Libraries},
	volume = {21},
	number = {1},
	year = {2002},
	note = {Times Cited: 1},
	pages = {33-36},
	abstract = {When people speak of open source software they arc referring to computer code-programs that run. But code is only the final step in the information technology process. Prior to Writing code the information technology professional must do analysis to determine the nature of the problem to be solved and the best way to solve it. When software projects fail, the failure is more often than not attributable to shortcomings in the planning and analysis phase rather than in the coding itself. Open source software provides sonic particular challenges for planning since the code itself will be worked on by different programmers and will evolve over time. The success of all open source project will clearly depend on the clarity of the shared vision of the goals of the software and some strong definitions of basic fuctions and how they will work. This all-important work of defining often takes place through standards and the development of standards that everyone can use has become a movement in itself. open standards.},
	author = {Coyle, K.}
}
@conference {1164,
	title = {The Open Source rEvolution - A Pragmatic Approach to Making the Best of It},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	attachments = {https://flosshub.org/sites/flosshub.org/files/WhiteGoldbergScharich.pdf},
	author = {White, T. and Goldberg, J. and Scharich, L.}
}
@unpublished {flosswp39,
	title = {Open Source Software and Software Patents: Finding the Common Ground in a Patent Pool},
	year = {2002},
	month = {May},
	abstract = {Software patents threaten the future of the OSS community, especially with the increased importance of software standards and the change in attitude in the organizations forming these standards. The OSS community does not exercise much influence over the policymakers who have legitimized software patents because of differences between the two groups{\textquoteright} motivations. There are many possible actions the OSS community could take, but an OSS patent pool is the best way for the OSS community to leverage both the patent system and the OSS culture to help protect the future of OSS.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/morgan.pdf},
	author = {Jason V. Morgan}
}
@article {flosswp32,
	title = {Open Source Software and the Economics of Organization},
	year = {2002},
	month = {June},
	abstract = {Open source software development has organizational characteristics that are out of the ordinary. The study suggests that this organization of work can be explained by combining the organizational theory of professions with the one of clubs. The claim is in fact that these organizations are at least as good as firms in sharing rich types of information in real time because (a) constituents have symmetry of absorptive capacity, and (b) software itself is a capital structure embodying knowledge.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/garzarelli.pdf},
	author = {Giampaolo Garzarelli}
}
@article {flosswp68,
	title = {Open Source Software Communities and Industrial Districts: A Useful Comparison?},
	year = {2002},
	month = {February},
	abstract = {Aim of this paper is to add a new and complementary perspective on the existing economic analysis of open-source software by comparing the structure and evolution of open-source software communities and of industrial districts, a peculiar organisational form of production based on a large number of interacting small and medium sized enterprises. The comparison between open-source software communities and industrial districts, in spite of some major differences allows the recognition of the role played by agglomeration economies, an explicit analysis of the incentives structure - governing the private provision of complex public goods-, and an in depth study of the governance structure and evolution of these phenomena. The paper presents some simple simulations which show the dependence of the governance structure{\textquoteright}s evolution on transaction costs dynamics.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/maggioni.pdf},
	author = {Mario Maggioni}
}
@conference {1162,
	title = {Is Open Source Software Development Faster, Better, and Cheaper than Software Engineering?},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {In this paper, I draw attention to the question of determining how open source software development may represent a significant alternative to modern software engineering techniques for developing large-scale software systems. OSSD often entails shorter time frames, producing higher quality systems, and incurring lower costs than may be realized through developing systems according SE techniques. Understanding why and how this may arise is the focus of this paper.},
	keywords = {argouml, quality, tigris},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Scacchi_0.pdf},
	author = {Walt Scacchi}
}
@inbook {Madey_Freeh_Tynan_2002,
	title = {The open source software development phenomenon: An analysis based on social network theory},
	booktitle = {Proceedings of the Eighth Americas Conference on Information Systems},
	year = {2002},
	pages = {1806{\textendash}1813},
	abstract = {The OSS movement is a phenomenon that challenges many traditional theories in economics, software engineering, business strategy, and IT management. Thousands of software programmers are spending tremendous amounts of time and effort writing and debugging software, most often with no direct monetary compensation. The programs, some of which are extremely large and complex, are written without the benefit of traditional project management, change tracking, or error checking techniques. Since the programmers are working outside of a traditional organizational reward structure, accountability is an issue as well. A significant portion of internet e-commerce runs on OSS, and thus many firms have little choice but to trust mission-critical e-commerce systems to run on such software, requiring IT management to deal with new types of socio-technical problems. A better understanding of how the OSS community functions may help IT planners make more informed decisions and develop more effective strategies for using OSS software. We hypothesize that open source software development can be modeled as self-organizing, collaboration, social networks. We analyze structural data on over 39,000 open source projects hosted at SourceForge.net involving over 33,000 developers. We define two software developers to be connected part of a collaboration social network if they are members of the same project, or are connected by a chain of connected developers. Project sizes, developer project participation, and clusters of connected developers are analyzed. We find evidence to support our hypothesis, primarily in the presence of power-law relationships on project sizes (number of developers per project), project membership (number of projects joined by a developer), and cluster sizes. Potential implications for IT researchers, IT managers, and governmental policy makers are discussed.},
	keywords = {developers, social network analysis, social networks, sourceforge},
	url = {http://ais.bepress.com/cgi/viewcontent.cgi?article=1606\&context=amcis2002},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MadeyFreehAmcis2002.pdf},
	author = {Madey, G. and Freeh, V and Tynan, R}
}
@article {flosswp67,
	title = {Open Source Software Production: Climbing on the Shoulders of Giants},
	year = {2002},
	month = {November},
	abstract = {Open source software production is a successful new production model in which a public good is voluntarily provided. We argue that by studying this new production model we gain valuable insight for organization theory beyond software production. Under specific conditions this model can be generalized, contingent on the interplay of motivational, situational, and institutional factors. It is argued that a production model building on the shoulders of predecessors and peers depends on a well balanced portfolio of intrinsic and extrinsic motivation, low costs for contributors and governance mechanisms that do not crowd out intrinsic motivation.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osterlohrotakuster.pdf},
	author = {Margit Osterloh and Sandra Rota}
}
@article {flosswp59,
	title = {Open Source Software Projects as Virtual Organizations: Competency Rallying for Software Development},
	journal = {IEE Proceedings Software},
	volume = {149},
	number = {1},
	year = {2002},
	pages = {3{\textendash}17},
	abstract = {The contribution of this paper is the identification and testing of factors important for the success of Open Source Software (OSS) projects. We present an analysis of OSS communities as virtual organizations and apply Katzy and Crowston{\textquoteright}s (2000) competency rallying (CR) theory to the case of OSS development projects. CR theory suggests that project participants must develop necessary competencies, identify and understand market opportunities, marshal competencies to meet the opportunity and manage a short-term cooperative process. Using data collected from 7477 OSS projects hosted by the SourceForge system (http://sourceforge.net/), we formulate and test a set of specific hypotheses derived from CR theory.},
	keywords = {competencies, competency rallying, coordination, project success, sourceforge, virtual organizations},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowston.pdf},
	author = {Kevin Crowston and Barbara Scozzi}
}
@article {flosswp50,
	title = {Open standard: role of externalities and impact on the industry structure},
	year = {2002},
	month = {July},
	abstract = {Conceding a part of property rights appears counter-intuitive in regards to the Porterian and Resources-Based frameworks. However industrial economics literature and recent examples suggest that this strategy is fruitful to develop network externalities and consequently to impose a standard in network industries. This article explores the role of the sponsor and the impacts of an open property rights strategy on the industry structure. Drawing on the empirical data collected from the U.S. Roleplaying Game industry, our results reveal that: 1) the open approach promoted by a sponsor does not work effectively without network industries specific resources; 2) this strategy induces new entries that benefits to the sponsor; 3) the firms in the industry do not change their technological trajectories except those which are well endowed with resources.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lecocqdemil.pdf},
	author = {Xavier Lecocq}
}
@conference {1152,
	title = {Open-Source Artefact Management},
	booktitle = {2nd Workshop on Open Source Software Engineering at ICSE 2002},
	year = {2002},
	abstract = {This paper presents the GENESIS project, which aims to develop an open-source, lightweight, process-aware (and process-neutral) workflow management system. In particular OSCAR, the artefact repository is discussed. The requirements of a system for artefact management and storage are described, and the concept of active artefacts is explained. The software engineering methods which will be used in the project are described, and some examples of the open-source tools which may be used are described.},
	keywords = {artefacts, artifacts, genesis, oscar, workflow},
	attachments = {https://flosshub.org/sites/flosshub.org/files/BoldyreffNutterRank.pdf},
	author = {Boldyreff, Cornelia and Nutter, David and Rank, Stephen}
}
@article {flosswp22,
	title = {Open-Source vs. Proprietary Software},
	year = {2002},
	month = {January},
	abstract = {The article studies technological competition between open-source and proprietary software using a model from interaction theory. We argue that the organizational structure of open-source software, allowed by openness of source codes and by the subsequent development of dedicated communities, is a key feature which, together with compatibility, can allow open-source software to overcome existing proprietary standards.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dalle2.pdf},
	author = {Jean-Michel Dalle and Nicolas Jullien}
}
@article {flosswp79,
	title = {An Overview of the Software Engineering Process and Tools in the Mozilla Project},
	year = {2002},
	month = {February},
	abstract = {The Mozilla Project is an Open Source Software project which is dedicated to development of the Mozilla Web browser and application framework. Possessing one of the largest and most complex communities of developers among Open Source projects, it presents interesting requirements for a software process and the tools to support it. Over the past four years, process and tools have been refined to a point where they are both stable and effective in serving the project?s needs. This paper describes the software engineering aspect of a large Open Source project. It also covers the software engineering tools used in the Mozilla Project, since theMozilla process and tools are intimately related. These tools include Bugzilla, a Web application designed for bug tracking, bug triage, code review and correction; Tinderbox, an automated build and regression testing system; Bonsai, a tool which performs queries to the CVS code repository; and LXR, a hypertext-based source code browser.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/reismozilla.pdf},
	author = {Christian Robottom Reis}
}
@article {flosswp56,
	title = {Permanently Beta: Responsive Organization in the Internet Era},
	year = {2002},
	month = {September},
	abstract = {How has the process of technological change in the Internet era influenced the way we organize economic activities? In this paper we discuss how information technologies foster the emergent design and user-driven design of websites and other online media, as well as products and organizations offline. A cycle of testing, feedback, and innovation facilitates ongoing negotiations around making products and around organizing that production. We call the organizational state of flux that emerges from these negotiations Permanently Beta. Beta testing, open source software, and interactive communities manifest aspects of permanently beta organization.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/neff-stark.pdf},
	author = {Gina Neff}
}
@conference {Dinkelacker:2002:POS:581339.581363,
	title = {Progressive open source},
	booktitle = {Proceedings of the 24th International Conference on Software Engineering},
	series = {ICSE {\textquoteright}02},
	year = {2002},
	pages = {177{\textendash}184},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The success of several Open Source{\texttrademark} software systems, e.g., Apache, Bind, Emacs, and Linux, has recently sparked interest in studying and emulating the software engineering principles underlying this innovative development and use model. Certain aspects of the Open Source development method, e.g., community building, open discussions for requirements and features, and evolvable and modular designs are having fundamental and far reaching consequences on general software engineering practices.To leverage such Open Source methods and tools, we have defined an innovative software engineering paradigm for large corporations: Progressive Open Source (POS). POS leverages the power of Open Source methods and tools for large corporations in a progressive manner: starting from completely within the corporation, to include partner businesses, and eventually complete Open Source. In this paper we present the design goals and principles for POS. We illustrate POS with two programs in HP: Corporate Source and the Collaborative Development Program (CDP). We present early results from both these programs suggesting the power and necessity of POS for all modern large corporations.},
	keywords = {companies},
	isbn = {1-58113-472-X},
	doi = {10.1145/581339.581363},
	url = {http://doi.acm.org/10.1145/581339.581363},
	author = {Dinkelacker, Jamie and Garg, Pankaj K. and Miller, Rob and Nelson, Dean}
}
@article {flosswp62,
	title = {Protecting the Virtual Commons: self-organizing communities and innovative intellectual property rights regimes},
	year = {2002},
	month = {October},
	abstract = {This paper discusses the tensions between open source communities and proprietary software development and identifies a number of innovative regimes that should deal with these tensions.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/joode.pdf},
	author = {Rueben Van Wendel De Joode}
}
@article {flosswp70,
	title = {Public Subsidies for Open Source? Some Economic Policy Issues of the Software Market},
	year = {2002},
	month = {November},
	abstract = {This paper discusses the economic merits of direct or indirect governmental support for open source projects. Software markets differ from standard textbook markets in three important respects that may give rise to market failures: (i) large economies of scale, (ii) crucially important innovations, (iii) significant network effects and switching costs. We analyze the differences between proprietary software and open source software with respect to these market features and ask whether open source as an alternative to proprietary software can mitigate these problems. Then we discuss the implications of various forms of governmental support for open source.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/schmidtschnitzer.pdf},
	author = {Klaus Schmidt}
}
@article {flosswp45,
	title = {Reconciling investors and donators - The governance structure of open source},
	year = {2002},
	month = {June},
	abstract = {The authors argue that the basic institutional innovation in open source has been the crafting of a governance structure, which enables investment without crowding out donations. The focus of the presented analysis lies on the specific institutional mechanisms, by which the open source governance structure achieves to reconcile the interests of investors and donators.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/jungwirth.pdf},
	author = {Egon Franck}
}
@article {flosswp43,
	title = {Roles and Knowledge Management in Online Technology Communities: An Ethnography Study},
	year = {2002},
	month = {June},
	abstract = {Technical communities are groups who share a common interest in a technology. The literature on technology communities lacks a conceptual understanding of the roles of various players in the online community. An understanding of the different roles the members of the community and the impact of the roles on knowledge management is crucial to manage and sustain such online technical communities. This study based on an ethnographic analysis of two technical communities identifies seven distinct roles. The impact of each of the role on knowledge management activities is discussed.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/madanmohan2.pdf},
	author = {T.R. Madanmohan}
}
@article {flosswp63,
	title = {The Scope of Open Source Licensing},
	journal = {Journal of Law, Economics and Organization},
	volume = {21},
	number = {1},
	year = {2002},
	month = {2005},
	pages = {20-56},
	abstract = {This paper is an initial exploration of the determinants of open source license choice. It first enumerates the various considerations that should figure into the licensor{\textquoteright}s choice of contractual terms, in particular highlighting how the decision is shaped not just by the preferences of the licensor itself, but also by that of the community of developers. The paper then presents an empirical analysis of the determinants of license choice using the SourceForge database, a compilation of nearly 40,000 open source projects. Projects geared toward end-users tend to have restrictive licenses, while those oriented toward developers are less likely to do so. Projects that are designed to run on commercial operating systems and those geared towards the Internet are less likely to have restrictive licenses. Finally, projects that are likely to be attractive to consumers such as games are more likely to have restrictive licenses.},
	keywords = {developers, license, licenses, permissive, restrictive, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lernertirole2.pdf},
	author = {Josh Lerner and Jean Tirole}
}
@booklet {anderson2002security,
	title = {Security in open versus closed systems{\textemdash}the dance of Boltzmann, Coase and Moore},
	year = {2002},
	publisher = {Technical report, Cambridge University, England},
	abstract = {Some members of the open-source and free software com- munity argue that their code is more secure, because vulnerabilities are easier for users to find and fix. Meanwhile the proprietary vendor com- munity maintains that access to source code rather makes things easier for the attackers. In this paper, I argue that this is the wrong way to approach the interaction between security and the openness of design. I show first that under quite reasonable assumptions the security assur- ance problem scales in such a way that making it either easier, or harder, to find attacks, will help attackers and defendants equally. This model may help us focus on and understand those cases where some asymmetry is introduced.
However, there are more pressing security problems for the open source community. The interaction between security and openness is entangled with attempts to use security mechanisms for commercial advantage {\textendash} to entrench monopolies, to control copyright, and above all to control interoperability. As an example, I will discuss TCPA, a recent initiative by Intel and others to build DRM technology into the PC platform. Al- though advertised as providing increased information security for users, it appears to have more to do with providing commercial advantage for vendors, and may pose an existential threat to open systems.},
	keywords = {security},
	url = {http://www.cl.cam.ac.uk/~rja14/Papers/toulouse.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/toulouse.pdf},
	author = {Anderson, Ross}
}
@article {payne2002security,
	title = {On the security of open source software},
	journal = {Information systems journal},
	volume = {12},
	number = {1},
	year = {2002},
	pages = {61{\textendash}78},
	publisher = {Wiley Online Library},
	abstract = {With the rising popularity of so-called {\textquoteleft}open source{\textquoteright} software there has been increasing interest in both its various benefits and disadvantages. In particular, despite its prominent use in providing many aspects of the Internet{\textquoteright}s basic infrastructure, many still question the suitability of such software for the commerce-oriented Internet of the future. This paper evaluates the suitability of open source software with respect to one of the key attributes that tomorrow{\textquoteright}s Internet will require, namely security. It seeks to present a variety of arguments that have been made, both for and against open source security and analyses in relation to empirical evidence of system security from a previous study. The results represent preliminary quantitative evidence concerning the security issues surrounding the use and development of open source software, in particular relative to traditional proprietary software.},
	keywords = {security},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Payne2002_ISJ12_SecurityOSS.pdf},
	author = {Payne, Christian}
}
@article {flosswp58,
	title = {Shaping Code},
	year = {2002},
	month = {September},
	abstract = {This article addresses how society shapes code. The term "code," as we use it, consists of the hardware and software components of information technologies. Code is increasingly being sought as a regulatory mechanism in conjunction with or as an alternative to law for addressing societal concerns such as crime, privacy, intellectual property protection, and revitalizing democratic discourse. This article analyzes how various societal institutions, that create code differentially, influence the technical and social characteristics of the code that is developed by them. The article also provides recommendations on how society can intervene and proactively shape the development of code to vindicate societal concerns and preferences.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shah.pdf},
	author = {Jay Kesan}
}
@unpublished {flosswp54,
	title = {Software Freedom, Open Software and the Participant{\textquoteright}s Motivation - A Multidisciplinary Study},
	year = {2002},
	month = {September},
	abstract = {The success of Free/Open Source Software has demonstrated the viability and often the dominance of an alternative ? almost paradoxical ? form of software development. This innovative organisational formation and operation has, recently, been studied intensively. The current paper deals with the issue of participant?s motivation to join and then to operate in a free/open source software development process. However, it does not adopt a single perspective towards reaching a definite answer. On the contrary, building on accumulative research work, it argues that no single perspective is adequate to explain free/open source software participants? motivation, since each perspective provides a rather limited understanding of the issue.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/tzouris.pdf},
	author = {Menelaos Tzouris}
}
@article {flosswp144,
	title = {TOOL: The Open Opinion Layer},
	year = {2002},
	month = {July},
	abstract = {Shared opinions drive society: what we read, how we vote, and where we shop are all heavily influenced by the choices of others. However, the cost in time and money to systematically share opinions remains high, while the actual performance history of opinion generators is often not tracked. This article explores the development of a distributed open opinion layer, which is given the generic name of TOOL. Similar to the evolution of network protocols as an underlying layer for many computational tasks, we suggest that TOOL has the potential to become a common substrate upon which many scientific, commercial, and social activities will be based.},
	author = {Hasan Masum}
}
@article {Hissam,
	title = {Trust and vulnerability in open source software},
	journal = {Software, {IEE} Proceedings -},
	volume = {149},
	number = {1},
	year = {2002},
	month = {02/2002},
	pages = {47{\textendash}51},
	chapter = {47},
	abstract = {Software plays an ever increasing role in the critical infrastructures that run our cities, manage our economies, and defend our nations. In 1999, the Presidents Information Technology Advisory Committee (PITAC) reported to the United States President the need for software components that are reliable, tested, modelled and secure supporting the development of predictably reliable and secure systems that underscore our critical infrastructures. Open source software (OSS) constitutes a viable source for software components. Some believe that OSS is more reliable and more secure than closed source software (CSS)-due to a phenomenon dubbed {\textquoteright}many eyeballs{\textquoteright}-but is this truly the case? Or does OSS give the cyber criminal an edge that he would likewise not have? We explore OSS from the perspective of the cyber criminal and discuss what the community of software developers and users alike can do to increase their trust in both open source software and closed source software},
	keywords = {closed source software, community of software developers, critical infrastructures, cyber criminal, open source software, PITAC, predictably reliable systems, predictably secure systems, software components, trust, users, vulnerability},
	issn = {1462-5970},
	doi = {10.1049/ip-sen:20020208},
	author = {Hissam, S. A. and Plakosh, D. and Weinstock, C.}
}
@article {121,
	title = {Two case studies of open source software development: Apache and Mozilla},
	journal = {ACM Transactions on Software Engineering and Methodology},
	volume = {11},
	number = {3},
	year = {2002},
	note = {apache data sources:
email, cvs, bug database 
regarding email: "We wrote Perl scripts to extract date, sender identity, message subject, and the message body that was further processed to obtain details on code changes and problem reports (see below). Manual inspection was used to resolve such things as multiple email addresses in cases where all automated techniques failed."
(but the rest of the paper does not address this data source at all)

mozilla data sources
bugzilla, cvs

},
	pages = {309-346},
	abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. In order to begin investigating such claims, we examine data from two major open source projects, the Apache web server and the Mozilla browser. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution intervals for these OSS projects. We develop several hypotheses by comparing the Apache project with several commercial projects. We then test and refine several of these hypotheses, based on an analysis of Mozilla data. We conclude with thoughts about the prospects for high- performance commercial/ open source process hybrids.},
	keywords = {apache, bug fixing, bug reports, bugzilla, change history, core, defect density, email, email archives, mailing list, mozilla, ownership, participation, productivity, scm, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mockusFieldingHerbsleb2002.pdf},
	author = {Audris Mockus and Roy Fielding and Herbsleb, J. D.}
}
@conference {Madey02understandingoss,
	title = {Understanding oss as a self-organizing process},
	booktitle = {In The 2nd Workshop on Open Source Software Engineering at the 24th International Conference on Software Engineering (ICSE2002},
	year = {2002},
	abstract = {We hypothesize that open source software development can be modeled as self-organizing, collaboration, social networks. We analyze structural data on over 39,000 open source projects hosted at SourceForge.net. We define two software developers to be connected {\textemdash} part of a collaboration social network {\textemdash} if they are members of the same project, or are connected by a chain of connected developers. Project sizes, developer project participation, and clusters of connected developers are analyzed. We find evidence to support our hypothesis, primarily in the presence of power-law relationships on project sizes (number of developers per project), project membership (number of projects joined by a developer), and cluster sizes.},
	keywords = {developers, size, social network analysis, social networks, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MadeyFreehTynan.pdf},
	author = {Madey, G. and Freeh, V and Tynan, R}
}
@article {flosswp98,
	title = {Usability and Open Source Software},
	journal = {Working Paper 02/10, Department of Computer Science, University of Waikato},
	year = {2002},
	month = {December},
	publisher = {Department of Computer Science, University of Waikato},
	abstract = {Open source communities have successfully developed many pieces of software although most computer users only use proprietary applications. The usability of open source software is often regarded as one reason for this limited distribution. In this paper we review the existing evidence of the usability of open source software and discuss how the characteristics of open-source development influence usability. We describe how existing human-computer interaction techniques can be used to leverage distributed networked communities, of developers and users, to address issues of usability.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nicholstwidale1.pdf},
	author = {David M Nichols and Michael B Twidale}
}
@conference {1154,
	title = {Version Control: A Case Study in the Challenges and Opportunities for Open Source Software Development},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {The growth of the worldwide open source development effort, driven in part by the recent entrance of large corporations into the open source arena, offers new opportunities to improve the software engineering tools available for that effort. Indeed, the increasing difficulty of managing large open source projects, as well as that of integrating related efforts into new programming environments, represents a challenge that must be met if the rapid growth of open source software is to continue. This position paper addresses these issues in the context of software version control.},
	keywords = {cvs, kernel, linux, linux kernel, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ChuCarrollShieldsWright.pdf},
	author = {Chu-Carroll, M.C. and Sheilds, D. and Wright, J.}
}
@conference {1158,
	title = {Where Do Open Source Requirements Come From (And What Should We Do About It)?},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {The collection and specification of software requirements is one of the most intense areas of software engineering research. This makes it a natural area to explore when considering open-source software. In this paper, I argue that the sources of open-source software requirements differ in some important respects from the sources of commercial software project requirements. This has some interesting implications for both open-source and commercial development.},
	keywords = {requirements},
	attachments = {https://flosshub.org/sites/flosshub.org/files/massey.pdf},
	author = {Bart Massey}
}
@conference {1157,
	title = {Why Do Developers Contribute to Open Source Projects? First Evidence of Economic Incentives},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	note = {"The data for this research come from two primary sources: Apache project archives and a targeted survey of Apache participants. Archival data are open source project artifacts such as email and source code archives, source code version control meta-data and developer web sites."},
	abstract = {The availability of commercial quality, free software products such as the Apache HTTP (web) server or the Linux operating system has focused significant attention on the open source development process by which these products were created. One of the more perplexing aspects of open source software projects is why developers freely devote their time and energy to these projects. While many open source participants cite idealistic motives for participation, Lerner and Tirole (2000) argue that developer participation in open source projects may, in part, be explained by existing economic theory regarding career concerns. This research seeks to confirm or disconfirm the existence of economic returns to participation in open source development. Preliminary results of our empirical investigation suggest that greater open source participation per se, as measured in contributions made, does not lead to wage increases. However, a higher status in a merit-based ranking within the Apache Project does lead to significantly higher wages. This suggests that employers do not reward the gain in experience through open source participation as an increase in human capital. The results are also consistent with the notion that a high rank within the Apache Software Foundation is a credible signal of the productive capacity of a programmer.},
	keywords = {apache, contributions, cvs, developers, ECONOMICS, email, email archives, financial, Human capital, mailing list, MOTIVATION, participation, source code, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HannRobertsSlaughterFielding.pdf},
	author = {Il-Horn Hann and Jeff Roberts and Sandra Slaughter and Roy Fielding}
}
@conference {1159,
	title = {Why Not Improve Coordination in Distributed Software Development by Stealing Good Ideas from Open Source?},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	keywords = {apache, communication, coordination, distributed},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MockusHerbsleb.pdf},
	author = {Audris Mockus and Herbsleb, James}
}
@article {47,
	title = {Working for Free? Motivations for Participating in Open-Source Projects},
	journal = {International Journal of Electronic Commerce},
	volume = {6},
	number = {3},
	year = {2002},
	pages = {25--39},
	publisher = {ME Sharpe},
	author = {Hars, A.}
}
@article {106,
	title = {Working for free? Motivations for participating in open-source projects},
	journal = {International Journal of Electronic Commerce},
	volume = {6},
	number = {3},
	year = {2002},
	note = {Times Cited: 24},
	pages = {25-39},
	abstract = {The success of the Linux operating system has demonstrated the viability of open-source software, an alternative form of software development that challenges traditional assumptions about software markets. Understanding why developers participate in open-source projects is crucial for assessing the impact of open-source software. Their motivations fall into two broad categories: internal factors (e.g., intrinsic motivation, altruism) and external rewards (e.g., expected future returns, personal needs). The results of a survey administered to open-source programmers are summarized.},
	author = {Hars, A. and Ou, S. S.}
}
@article {54,
	title = {Code, Culture and Cash: The Fading Altruism of Open Source Development},
	journal = {First Monday},
	volume = {6},
	number = {12},
	year = {2001},
	note = {"I collected information on the country of residence for key contributors to the two projects. In the case of Linux, I relied on information located in the CREDITS file of all major kernel releases (from version 1.0 to version 2.4.9) [22]. For Gnome, I gathered developer-contact information from the project{\textquoteright}s web-site. Where information on the home-country of developers was not explicitly available, I performed private research to ascertain said information, or - in the last-case scenario - trusted information in the provided e-mail address of developers to infer home-country from domain ownership [23]. In the case of Linux, to avoid bias that might be introduced over time as developers migrated internationally, developers are continually counted as residents of the countries they were associated with when their names first entered the CREDITS file"},
	abstract = {The nexus of open source development appears to have shifted to Europe over the last ten years. This paper explains why this trend undermines cultural arguments about "hacker ethics" and "post-scarcity" gift economies. It suggests that classical economic theory offers a more succinct explanation for the peculiar international distribution of open source development: hacking rises and falls inversely to its opportunity cost. This finding throws doubt on the Schumpeterian assumption that the efficiency of industrial systems can be measured without reference to the social institutions that bind them.},
	keywords = {credits, email address, european, geography, gnome, linux},
	url = {http://131.193.153.231/www/issues/issue6_12/lancashire/index.html},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Lancashire.pdf},
	author = {David Lancashire}
}
@conference {1144,
	title = {﻿﻿Conceptual Sociological Model for Open Source Software},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kishida.pdf},
	author = {Kishida, Kouichi}
}
@conference {1136,
	title = {Configuration Management for Open Source Software},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	month = {05/2001},
	abstract = {Open Source Software (OSS) projects have a seemingly anarchistic way of organising projects and a set-up (many, distributed developers) that is usually considered difficult to handle within the field of configuration management. Still they manage to produce software that is of at least as high a quality as that produced by Conventional Software Development (CSD) projects.
We have investigated more closely what they actually do, and why they are so successful. The goal of the study was to describe their underlying configuration management process, thereby making it explicit, so it can be followed in case others (like commercial companies) want to start an OSS project or a project having similar characteristics. We also analysed to what extent their success is due to a good process, good tools or simply to outstanding people participating in OSS projects. Based on this, lessons could be learned from OSS and possible transferred to conventional ways of developing software. We interviewed key people from three OSS projects (KDE, Mozilla and Linux) to obtain data for our study.},
	keywords = {configuration management, interviews, project success},
	attachments = {https://flosshub.org/sites/flosshub.org/files/asklundbendix.pdf},
	author = {Asklund, U. and Bendix, L.}
}
@conference {1141,
	title = {Corporate Source: Applying Open Source Concepts to a Corporate Environment},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	keywords = {commercial software, hewlett packard, hp, organizational sponsorship},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dinkelackergarg.pdf},
	author = {Dinkelacker, J. and Garg, P.K.}
}
@conference {1138,
	title = {Creating a Free, Dependable Software Engineering Environment for Building Java Applications},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {As open source software engineering becomes more prevalent, employing sound software engineering practices and the tools used to implement these practices becomes more important. This paper examines the current status of free software engineering tools. For each set of tools, we determined the important attributes that would best assist a developer in each stage of the waterfall model. We rated each tool based on predetermined attributes. We used the creation of a graphical user interface based email client in Java to assist in evaluating each tool. Our findings show that there is still a need for free tools to extract UML diagrams, test graphical user interfaces, make configuring Emacs easier, and profile Java applications. In other areas there are free tools that provide satisfactory functionality such as Concurrent Versions System (CVS), GVim, JUnit, JRefactory, GNU Make, Jakarta Ant, Javadoc, and Doc++.},
	keywords = {applications, cvs, Doc++, GNU Make, GVim, Jakarta Ant, java, Javadoc, jrefactory, junit, tools},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bittman.pdf},
	author = {Bittman, M. and Roos, R. and Kapfhammer, G.M.}
}
@unpublished {flosswp28,
	title = {Detecting Dominant Design},
	year = {2001},
	month = {May},
	abstract = {This paper derives a framework for the emergence of a dominant design in the web server market. Particular attention is given to factors important in network-based economies including network effects, standards, complimentary assets and technological change. A complete examination of the web server industry from its origins in the Internet through to today{\textquoteright}s market dominated by the products of open-source and proprietary software provides interesting insights into the application of the emergence framework.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/jordan.pdf},
	author = {John Jordan}
}
@article {flosswp25,
	title = {Distributed Knowledge and the Global Organization of Software Development},
	year = {2001},
	month = {February},
	abstract = {Open-source software development is a production model that exploits the distributed intelligence of participants in Internet communities. This model is efficient because of two related reasons: it avoids the inefficiencies of a strong intellectual property regime and it implements concurrently design and testing of software modules. The hazard of open source is that projects can ?fork? into competing versions. However, open-source communities consist of governance structures that constitutionally minimize this danger. Because open source works in a distributed environment, it presents an opportunity for developing coun-tries to participate in frontier innovation.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kogut1.pdf},
	author = {Bruce Kogut}
}
@article {witten2001does,
	title = {Does open source improve system security?},
	journal = {IEEE Software},
	volume = {18},
	number = {5},
	year = {2001},
	pages = {57{\textendash}61},
	publisher = {IEEE},
	abstract = {An attacker
could examine
public source
code to find
flaws in a
system. So, is
source code
access a net
gain or loss for
security? The
authors
consider this
question from
several
perspectives
and tentatively
conclude that
having source
code available
should work in
favor of system
security.},
	keywords = {security},
	url = {https://pdfs.semanticscholar.org/71f6/01579ad1c373ed59a19eba0396f7f0cb7a0e.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/01579ad1c373ed59a19eba0396f7f0cb7a0e.pdf},
	author = {Witten, Brian and Landwehr, Carl and Caloyannides, Michael}
}
@article {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 {flosswp29,
	title = {Free Software/Free Science},
	year = {2001},
	month = {December},
	abstract = {This paper explores the comparison often made between Free Software and scientific research, and the tendency to discuss both endeavors by positing a role for reputation as the currency of value. It discusses a handful of examples from the history and social study of science to explain how scholars have approached similar issues in understanding scientific activity. It also offers some speculations on the relationship between the metaphorical currency of reputation and real money, and that between metaphorical and actual intellectual property.},
	author = {Christoper Kelty}
}
@book {56,
	title = {The future of ideas: the fate of the commons in a connected world},
	year = {2001},
	publisher = {Random House},
	organization = {Random House},
	author = {Lessig, L.}
}
@conference {Godfrey:2001:GES:602461.602482,
	title = {Growth, evolution, and structural change in open source software},
	booktitle = {Proceedings of the 4th International Workshop on Principles of Software Evolution (IWPSE 2001)},
	series = {IWPSE {\textquoteright}01},
	year = {2001},
	note = {"We measured [linux] system size in uncommented LOC"
"We also examined the growth of several other open source systems, including the VIM text editor, Eric Raymond{\textquoteright}s fetchmail utility, and the GCC compiler suite. "},
	pages = {103{\textendash}106},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Our recent work has addressed how and why software systems evolve over time, with a particular emphasis on software architecture and open source software systems [2, 3, 6]. In this position paper, we present a short summary of two recent projects. First, we have performed a case study on the evolution of the Linux kernel [3], as well as some other open source software (OSS) systems. We have found that several OSS systems appear not to obey some of "Lehman{\textquoteright}s laws" of software evolution [5, 7], and that Linux in particular is continuing to grow at a geometric rate. Currently, we are working on a detailed study of the evolution of one of the subsystems of the Linux kernel: the SCSI drivers subsystem. We have found that cloning, which is usually considered to be an indicator of lazy development and poor process, is quite common and is even considered to be a useful practice. Second, we are developing a tool called Beagle to aid software maintainers in understanding how large systems have changed over time. Beagle integrates data from various static analysis and metrics tools and provides a query engine as well as navigable visualizations. Of particular note, Beagle aims to provide help in modelling long term evolution of systems that have undergone architectural and structural change.},
	keywords = {agile methods, beagle, cloning, evolution, fetchmail, gcc, growth, kernel, lehman{\textquoteright}s laws, lines of code, linux, linux kernel, loc, open source software, software architecture, software evolution, source code, structural change, supporting environments, vim},
	isbn = {1-58113-508-4},
	doi = {http://doi.acm.org/10.1145/602461.602482},
	url = {http://doi.acm.org/10.1145/602461.602482},
	attachments = {https://flosshub.org/sites/flosshub.org/files/tu2001.pdf},
	author = {Michael Godfrey and Tu, Qiang}
}
@article {flosswp16,
	title = {How Communities Support Innovative Activities: As Exploration of Assistance and Sharing Among Innovative Users of Sporting Equipment},
	year = {2001},
	month = {August},
	abstract = {This exploratory study finds that end-user innovators who are members of voluntary sports communities often receive assistance in developing their sports-equipment innovations from fellow community members. Innovation-related information and assistance, as well as the innovations themselves, are freely within these communities. The processes by which these communities operate may be of general interest both within and beyond the consumer product arena; for example, communities of open source software developers appear to operate in similar ways.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/frankeshah.pdf},
	author = {Nik Franke}
}
@article {flosswp46,
	title = {Innovating without Money: Linux and the Open Source Paradigm as an Alternative to Commercial Software Development},
	year = {2001},
	month = {August},
	abstract = {This dissertation analyses two different paradigms used for the development of a operating systems by Microsoft Corporation and the Linux Community. Through the observation of the strategies and methodologies used by these actors in their work, and taking into account the constraints to which they are subject, assesses, from a dynamic perspective, the relative strengths and weaknesses of their competing paradigms. A theoretical model based on Giovanni Dosi?s "Technological Paradigms" framework, incorporating institutional, industrial, social and cultural aspects, is constructed and specifically adapted to the software industry case. The private management of technology issues considered during the analysis of the development processes inside different organisations are linked to questions having to do with the evolution of high technology, networked, markets.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mateos.pdf},
	author = {Mateos Garcia, Juan}
}
@conference {1148,
	title = {Introducing a {\textquotedblleft}Street Fair{\textquotedblright} Open source Practice Within Project Based Software Engineering Courses},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {Columbia University and USC, as well as many other universities, have software engineering courses where students work in small teams to develop a product of moderate complexity. Typically such efforts are {\textquotedblleft}closed source{\textquotedblright} where teams do not (or are forbidden) from sharing information and providing assistance to other teams. There are certainly many justifiable reasons for this such as grading uniformity. Yet strong drivers such as grade competition, generally thought to promote quality results (i.e. successful projects), often do not. The authors ran an experiment introducing a style of open source practice called {\textquotedblleft}street fair{\textquotedblright} with surprisingly positive results.},
	keywords = {education, educational resources},
	attachments = {https://flosshub.org/sites/flosshub.org/files/portkaiser.pdf},
	author = {Port, D. and Kaiser, G.}
}
@conference {1150,
	title = {Leveraging Open-Source Communities To Improve the Quality \& Performance of Open-Source Software},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {Open-source processes have emerged as an effective approach to reduce cycle-time and decrease development and quality assurance costs for certain types of software. they are not without challenges, however, such as decreasing long-term maintenance and evolution costs, improving quality assurance, sustaining end-user confidence and good will, and ensuring the coherency of system-wide software and usability properties. Although aspects of these issues are unique to open-source	development,	well-organized	open-source projects make it easier to address certain of these challenges compared with traditional closed-source approaches to building software.
We have begun a long-term research effort, called Skoll, whose goal is to leverage common open-source project assets, such as their technologically sophisticated worldwide user communities, to devise techniques that address key challenges of open-source software development. In particular, we are conducting a long-term case study of two widely used open-source projects, ACE and TAO, to design, deploy, and evaluate techniques for improving quality through continuous distributed testing and profiling. This position paper presents our view of the pros and cons of open-source processes and outlines the work we are doing to improve the quality and performance of open-source software.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/schmidt.pdf},
	author = {Schmidt, D.C. and Porter, A.}
}
@unpublished {flosswp21,
	title = {Management and Virtual Decentralized Networks: The Linux Project},
	year = {2001},
	month = {September},
	abstract = {This paper examines whether geographically dispersed knowledge workers can virtually collaborate for a project under no central planning. Co-ordination, management and the role of knowledge arise as the central areas of focus. The Linux Project and its development model are selected as a case of analysis and the critical success factors of this organizational design are identified. The study proceeds to the formulation of a framework that can be applied to all kinds of virtual decentralized work and concludes that value creation is maximized when there is intense interaction and uninhibited sharing of information between the organization and the surrounding community.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dafermoslinux.pdf},
	author = {George Dafermos}
}
@article {flosswp31,
	title = {Managing Information Quality in Virtual Communities of Practice},
	year = {2001},
	month = {November},
	abstract = {In this paper we review how the new economics of information enable a new paradigm of collaboration. Spearheaded by the Open Source community, this evolutionary approach to collaborative content creation is a way to address information quality in virtual communities of practice. Based on experience gained in community projects, a few simple steps toward improving the quality of information in virtual communities are presented and illustrated.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/neus.pdf},
	author = {Andreas Neus}
}
@conference {1151,
	title = {Open Source Development: A suitable Method to introduce a standardized communication protocol?},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {Open Source developments like telnet and Apache are very important for an extensive and compatible use of the TCP/IP and the HTTP protocol. Both contain features which rely on a compatible implementation of complex interactions between computers of different platform types. This can be successfully achieved with the help of Open Source.	Reconciliation	of	different interpretations of the standard, clarifications and extensions can be realised by discussion systems	and	some	generally	accepted conciliators of Open Source projects. As long as companies have a commercial interest in selling solutions based on the protocol, it makes economic sense for them to jointly support its common implementation. This paper examines the possibility to use an Open Source reference implementation of the agricultural communication protocols DIN 9684 [1] [2] and ISO 11783 to establish a capable and compatible implementation in agricultural mobile process control and data collection.},
	keywords = {communication protocol, DIN 9684, ISO 11783, open source},
	attachments = {https://flosshub.org/sites/flosshub.org/files/spangler.pdf},
	author = {Spangler, Achim}
}
@conference {1139,
	title = {Open Source Development: An Arthurian Legend},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {OSSD (Open Source Software Development) achieves remarkable success in delivering complex software systems {\textendash} systems which are incredibly reliable and robust {\textendash} in a short amount of time and without even paying anyone! Naturally, in the face of this success, organizations are interested in seeing if the mechanisms behind OSSD success can be migrated into their own practices, hopefully improving their systems and their productivity.
In this paper, we look (lighthearted at first) at the motivations behind those involved in OSSD and describe the problems that need to be overcome if OSSD-type practices can be migrated into traditional organizations.},
	keywords = {commercial software, developers, MOTIVATION},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cook.pdf},
	author = {Cook, J.}
}
@article {flosswp13,
	title = {Open Source Shows the Way - Innovation By and For Users - No Manufacturer Required},
	year = {2001},
	month = {March},
	abstract = {Open source software projects are complete innovation development and consumption communities run by and for users, no manufacturer required. This essay points out that user innovation communities have existed long before and extend far beyond open source software. The example of user innovation communities as the developers of new sports, sporting techniques, and new sporting equipment is described.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/evhippel-osuserinnovation.pdf},
	author = {von Hippel, Eric}
}
@conference {1147,
	title = {Open Source Software Developments in XP Style},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nisinaka.pdf},
	author = {Nishinaka, Y.}
}
@conference {1143,
	title = {Open Source Software: The Other Commercial Software},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {Open source software is a source of components from which systems can be built. Components can also be acquired in the marketplace. There are a myriad of issues that affect software that incorporates commercial components. These issues (and others) also affect open source software. In this paper we examine issues that an organization using open source software is likely to face in light of lessons learned from the world of commercial components},
	keywords = {commercial off-the-shelf software, commercial software, COTS software, open source software},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hissamweinstock.pdf},
	author = {Hissam, S. and Weinstock, C.}
}
@article {912,
	title = {Open Source Standardization: The Rise of Linux in the Network Era},
	journal = {Knowledge, Technology \& Policy},
	volume = {14},
	year = {2001},
	pages = {88-112},
	abstract = {To attract complementary assets, firms that sponsor proprietary de facto compatibility standards must trade off control of the standard against the imperative for adoption. For example, Microsoft and Intel in turn gained pervasive adoption of their technologies by appropriating only a single layer of the standards architecture and encouraging competition in other layers. In reaction to such proprietary strategies, the open source movement relinquished control to maximize adoption. To illustrate this, we examine the rise of the Linux operating system from 1995-2001, particularly the motivations of organizational buyers and suppliers of complementary assets, and Microsoft?s reaction to its success.},
	author = {Joel West and Dedrick, Jason}
}
@article {97,
	title = {Open source standards on software process: A practical application},
	journal = {Ieee Communications Magazine},
	volume = {39},
	number = {4},
	year = {2001},
	note = {Times Cited: 0},
	pages = {116-123},
	abstract = {Standards are generally delivered by means of static documents which are difficult to handle and to learn. Although their source text might have an open access, they do not offer an open source environment which effectively supports their assimilation, comprehension, and use. To achieve this goal, standards regulating the software process should be delivered in different "workable" formats to allow users to immediately start applying them with the support of software tools and methodologies.},
	author = {Freericks, C.}
}
@unpublished {flosswp147,
	title = {Opening The Code: Software Excellence As A Function Of Its Development Environment},
	year = {2001},
	month = {January},
	abstract = {Software is an increasingly important component of the modern world; indeed, software forms the architecture around which today?s digital society is built. Because of the complex interrelationship between computer code, liberty, and the distribution of power in society, the environment in which code is produced makes a tremendous difference in the resulting structure of the world. An "Open" foundation for software development provides a variety of economic and societal benefits, but there are a number of preconditions necessary for its full deployment. One of the primary stumbling blocks is the need for the Open development process to demonstrate its capacity for producing "excellent" software. This thesis tackles that obstacle by first defining excellence in software, and then examining the software ecosystems that surround proprietary and Open Source conceptions of digital property in terms of their incentive structures{\textendash}incentives that either encourage or discourage quality. Herein, this thesis demonstrates that not only can an Open Source development model produce quality software, but it also takes advantage of the complex adaptive systems model of diversity and adaptation to better meet the established criteria of an "ideal" software development system.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mclaughlin.pdf},
	author = {David McLaughlin}
}
@article {flosswp33,
	title = {Peripheral Members in Online Communities},
	year = {2001},
	month = {Unspecified},
	abstract = {Organizations are exploring the role communities play in knowledge management and online communities are attracting more and more attentions. One difference between online communities and conventional communities lies in the large number of peripheral members in online communities, which is the focus of the study. The study empirically verifies the important role peripheral members play in online communities. It also suggests that in addition to benefiting from online communities, peripheral members also contribute to online communities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/zhang.pdf},
	author = {Wei Zhang}
}
@article {flosswp34,
	title = {Positive Intellectual Rights and Information Exchanges},
	year = {2001},
	month = {July},
	abstract = {This paper proposes a reversal in how to consider the rights associated with information, media contents, software and other intellectual entities. The proposed approach sets as its basis a number of positive intellectual rights, defined as to enable wide societal production and exchange of intellectual entities. It then defines how granting of specific attributes of property is necessary as to ensure that the positive rights are not abused to the detriment of some basic values, and are implemented in reality. Such a reversal allows to exploit the benefits of information and communication technology. More generally, it debates right issues for the technology of the intangible.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/aigrain.pdf , https://flosshub.org/sites/flosshub.org/files/aigrain_0.pdf},
	author = {Philippe Aigrain}
}
@conference {1140,
	title = {The ramp-up challenge in open-source software projects},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cubranic.pdf},
	author = {Cubranic, Davor}
}
@conference {1145,
	title = {Reputation Layers for Open-Source Development},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	keywords = {currency, developers, MOTIVATION, reputation},
	attachments = {https://flosshub.org/sites/flosshub.org/files/masum.pdf},
	author = {Hasan Masum}
}
@conference {1135,
	title = {Software Architectures and Open Source Software {\textendash} Where can Research Leverage the Most?},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	month = {05/2001},
	abstract = {Software architectures have been playing a central role in software engineering research for some years now. They are considered of pivotal importance in the success of complex software systems development. However, with the emergence of Open Source Software (OSS) development, a new opportunity for studying architectural issues arises. In this paper, we introduce accepted notions of software architectures (Section 2), discuss some of the known issues in OSS (Section 3), resulting in a set of aspects we consider to be relevant for future research (Section 4).},
	keywords = {architecture, software architecture},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ariefgaceklawrie.pdf},
	author = {Arief, B. and Gacek, C. and Lawrie, T.}
}
@conference {1149,
	title = {Software Development Practices in Open Software Development Communities: A Comparative Case Study},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {This study presents an initial set of findings from an empirical study of social processes, technical system configurations, organizational contexts, and interrelationships that give rise to open software. "Open software", or more narrowly, open source software, represents an approach for communities of like-minded participants to develop software system representations that are intended to be shared freely, rather than offered as closed commercial products. While there is a growing popular literature attesting to open software [DiBona, Ockman, Stone 1999, Fogel 1999], there are very few systematic studies [e.g., Feller and Fitzgerald 2000, Mockus, Fielding, Herbsleb 2000] that informs how these communities produce software. Similarly, little is known about how people in these communities coordinate software development across different settings, or about what software processes, work practices, and organizational contexts are necessary to their success. To the extent that academic research communities and commercial enterprises seek the supposed efficacy of open software [Smarr and Graham 2000], they will need grounded models of the processes and practices of open software development to allow effective investment of their resources. This study investigates four communities engaged in open software development. Case study methods are used to compare practices across communities.},
	keywords = {apache, argouml, astronomy, chandra, games, infrastructure, internet news, mozilla, systems design},
	attachments = {https://flosshub.org/sites/flosshub.org/files/scacchi.pdf},
	author = {Walt Scacchi}
}
@conference {1137,
	title = {Software Engineering Lessons from Open Source Projects},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {The Open Source form of software development has captured the attention of academics and software practitioners alike. Though, this {\textquoteleft}phenomenon{\textquoteright} has been touted by some to be how all software will eventually be developed, many are critical about how far this form of organization will be successful. It is very likely that both the traditional form as well as the Open Source form of organization for software projects may co-exist. The position taken in this paper is that commercial projects can learn important lessons from Open Source projects. This paper tries to capture the elements of Open Source projects that can be applied to traditional commercial projects and the means by which further information can be gathered.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/asundi.pdf},
	author = {Asundi, J.}
}
@conference {1142,
	title = {Software Engineering Research in the Bazaar},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	note = {"To gain a better understanding of a software system, we recover its software architecture from the system{\textquoteright}s source code.
We recovered the architecture of many open source systems such as the Linux kernel [3], the Mozilla browser [5], the Apache web server [7], and the VIM editor [14]. The recovered architecture is browse-able to permit developers to interact with it, [10] shows an example for the Linux kernel."},
	abstract = {During the last five years, our research group has studied the architecture and evolution of several large open source systems {\textemdash} including Linux, GCC, VIM, Mozilla, and Apache {\textemdash} and we have found that open source software systems often exhibit interesting differences when compared to similar commercially-developed systems. Our investigations of these systems have involved the creation of software architecture models, software architecture repair, the creation of a reference architecture for web servers, the study of evolution and growth of open source systems, and the modelling of architectural properties of systems that are apparent only at build time.},
	keywords = {apache, architecture, gcc, kernel, linux, linux kernel, mozilla, open source software, software architecture, Software Engineering Research, source code, vim},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hassangodfreyholt.pdf},
	author = {Hassan, Ahmed E. and Godfrey, Michael W. and Holt, Richard C.}
}
@article {flosswp27,
	title = {The Strategy Finding Task Within Collaborative Networks, Based on an Exemplary Case of the Linux Community},
	year = {2001},
	month = {September},
	abstract = {This article will focus on how the strategy-finding task is performed within virtual organisations in general and in the open source community of Linux in particular. This article will demonstrate that one of the reasons for the success of Linux is the way the strategic finding task is fulfilled in this community.The point to be shown in this paper is the self-organising power and apparent success of emergent ({\textquoteright}bottom up{\textquoteright}) strategy finding processes within the Linux community, ensuring the interaction between change trajectories of both its internal resources and external threats and weaknesses. It will be shown that a number of mechanisms have institutionalised this interaction in the community.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dejoode.pdf},
	author = {Rueben Van Wendel De Joode}
}
@article {98,
	title = {Striking a balance between trust anti control in a virtual organization: a content analysis of open source software case studies},
	journal = {Information Systems Journal},
	volume = {11},
	number = {4},
	year = {2001},
	note = {"I employ secondary analysis of published case studies of OSS projects. I used several search methods to identify such case studies about OSS pro- jects. First, I searched the electronic archives of both ACM and IEEE, using terms such as {\textquoteleft}open source.{\textquoteright} "
"Secondly, I searched on Bell \& Howell/Proquest{\textquoteright}s ABI/Inform, a database of acade- mic and trade publications on business and management (including technology management). Thirdly, I reviewed the {\textquoteleft}position papers{\textquoteright} of the various authors who attended the 1st Work- shop on Open-Source Software Engineering (Feller et al., 2001) for relevant case studies. Fourthly, I searched on Harvard Publishing{\textquoteright}s websites, which contain case studies published"
"Finally, as I located case studies or other publi- cations about OSS projects, I followed references from them to identify other case studies. Although I found literally hundreds of publications about OSS development, there was a much smaller number of case studies"},
	pages = {277-304},
	abstract = {Many organization theorists have predicted the emergence of the networked or virtual firm as a model for the design of future organizations. Researchers have also emphasized the importance of trust as a necessary condition for ensuring the success of virtual organizations. This paper examines the open source software (OSS) {\textquoteright}movement{\textquoteright} as an example of a virtual organization and proposes a model that runs contrary to the belief that trust is critical for virtual organizations. Instead, I argue that various control mechanisms can ensure the effective performance of autonomous agents who participate in virtual organizations. Borrowing from the theory of the {\textquoteright}McDonaldization{\textquoteright} of society, I argue that, given a set of practices to ensure the control, efficiency, predictability and calculability of processes and outcomes in virtual organizations, effective performance may occur in the absence of trust. As support for my argument, I employ content analysis to examine a set of published case studies of OSS projects. My results show that, although that trust is rarely mentioned, ensuring control is an important criterion for effective performance within OSS projects. The case studies feature few references to other dimensions of {\textquoteright}McDonaldization{\textquoteright} (efficiency, predictability and calculability), however, and I conclude that the OSS movement relies on many other forms of social control and self-control, which are often unacknowledged in OSS projects. Through these implicit forms of control, OSS projects are able to secure the cooperation of the autonomous agents that participate in project teams. I conclude by extrapolating from these case studies to other virtual organizations.},
	keywords = {apache, case studies, Control, fetchmail, jun, linux, linux kernel, McDonaldization, mozilla, networked organization, perl, rationalization, trust, virtual organization},
	author = {Gallivan, M. J.}
}
@conference {1146,
	title = {Taxonomy of Open Source Software Development},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	keywords = {jun, linux, postgresql, wingnut},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nakakojiyamamoto.PDF},
	author = {Nakakoji, K. and Yamamoto, Y.}
}
@article {flosswp35,
	title = {Understanding the Requirements for Developing Open Source Software Systems},
	journal = {IEE Proceedings Software},
	volume = {149},
	number = {1},
	year = {2001},
	month = {December},
	pages = {24-39},
	abstract = {This study presents an initial set of findings from an empirical study of social processes, technical system 
configurations, organizational contexts, and interrelationships that give rise to open software. The focus is 
directed at understanding the requirements for open software development efforts, and how the 
development of these requirements differs from those traditional to software engineering and requirements 
engineering. Four open software development communities are described, examined, and compared to help discover what these differences may be. Eight kinds of software informalisms are found to play a critical role in the elicitation, analysis, specification, validation, and management of requirements for developing open software systems. Subsequently, understanding the roles these software informalisms take in a new formulation of the requirements development process for open source software is the focus of this study. This focus enables considering a reformulation of the requirements engineering process and its associated artifacts or (in)formalisms to better account for the requirements for developing open source software systems. },
	attachments = {https://flosshub.org/sites/flosshub.org/files/scacchi.pdf},
	author = {Walt Scacchi}
}
@article {flosswp47,
	title = {Usability and open-source software development},
	journal = {Proceedings of the Symposium on Computer Human Interaction},
	year = {2001},
	month = {June},
	pages = {49{\textendash}54},
	publisher = {ACM SIGCHI New Zealand},
	abstract = {This paper reports a usability study of the open-source Greenstone Digital Library collection-building software. The problems highlighted by the study are analysed to identify their likely source within the social context of Greenstone{\textquoteright}s development environment. We discuss how characteristics of open-source software development influence the usability of resulting software products.},
	keywords = {Greenstone, user study},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nichols.pdf},
	author = {David M Nichols and Kirsten Thomson and Stuart A Yeates}
}
@unpublished {flosswp17,
	title = {The Use of Computer Conferencing as an Organizational Knowledge Transfer},
	year = {2001},
	month = {June},
	abstract = {Electronic bulletin boards were used as an organization-wide problem solving process that transferred private knowledge. Key organizational implications were found.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/willpope.pdf},
	author = {William Pope}
}
@article {flosswp20,
	title = {The Web of Knowledge: An Investigation of Knowledge Exchange in Networks of Practice},
	year = {2001},
	month = {October},
	abstract = {Electronic ties are loosening the constraints of organizational structure and physical proximity to allow connectivity between individuals who would otherwise find it difficult to identify and sustain contact with others who share the similar interests. This paper explores the knowledge exchange processes in extra-organizational networks of practice by studying three technical newsgroups. We argue that the development of relational social capital is a vital component for transforming electronic posting forums into ongoing networks of practice. The results reveal that relational social capital exists on networks of practice and shows a strong relationship with knowledge exchange processes over and above the influence of individual motivation and ability.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Farajwasko.pdf},
	author = {Samer Faraj}
}
@article {flosswp26,
	title = {A Case Study of Open Source Software Development: The Apache Server},
	journal = {Proceedings of the International Conference on Software Engineering (ICSE 2000)},
	year = {2000},
	note = {We used the following archival sources of data:
Developer email list (EMAIL).
Concurrent Version Control archive (CVS).
Problem reporting database (BUGDB).},
	month = {June},
	abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. We examine the development process of a major open source application, the Apache web server. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution interval for this OSS project. This analysis reveals a unique process, which performs well on important measures.},
	keywords = {apache, bug fix revisions, bugs, core, cvs, defect density, developers, email archives, participation, productivity, revision control, revision history, roles, scm, source code, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mockusapache.pdf},
	author = {Audris Mockus and Roy Fielding and Herbsleb, James}
}
@conference {Yamauchi:2000:CLM:358916.359004,
	title = {Collaboration with Lean Media: how open-source software succeeds},
	booktitle = {Proceedings of the 2000 ACM conference on Computer supported cooperative work (CSCW)},
	series = {CSCW {\textquoteright}00},
	year = {2000},
	pages = {329{\textendash}338},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open-source software, usually created by volunteer programmers dispersed worldwide, now competes with that developed by software firms. This achievement is particularly impressive as open-source programmers rarely meet. They rely heavily on electronic media, which preclude the benefits of face-to-face contact that programmers enjoy within firms. In this paper, we describe findings that address this paradox based on observation, interviews and quantitative analyses of two open-source projects. The findings suggest that spontaneous work coordinated afterward is effective, rational organizational culture helps achieve agreement among members and communications media moderately support spontaneous work. These findings can imply a new model of dispersed collaboration.},
	keywords = {cooperative work, cvs, distributed work, electronic media, INNOVATION, open-source, software engineering},
	isbn = {1-58113-222-0},
	doi = {10.1145/358916.359004},
	url = {http://doi.acm.org/10.1145/358916.359004},
	author = {Yamauchi, Yutaka and Yokozawa, Makoto and Shinohara, Takeshi and Ishida, Toru}
}
@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}
}
@conference {Feller:2000:FAO:359640.359723,
	title = {A framework analysis of the open source software development paradigm},
	booktitle = {Proceedings of the twenty first international conference on Information systems},
	series = {ICIS {\textquoteright}00},
	year = {2000},
	pages = {58{\textendash}69},
	publisher = {Association for Information Systems},
	organization = {Association for Information Systems},
	address = {Atlanta, GA, USA},
	abstract = {Open Source Software (OSS) has become the subject of much commercial interest of late. Certainly, OSS seems to hold much promise in addressing the core issues of the software crisis, namely that of software taking too long to develop, exceeding its budget, and not working very well. Indeed, there have been several examples of significant OSS success stories{\textemdash}the Linux operating system, the Apache web server, the BIND domain name resolution utility, to name but a few. However, little by way of rigorous academic research on OSS has been conducted to date. In this study, a framework was derived from two previous frameworks which have been very influential in the IS field, namely that of Zachman{\textquoteright}s IS architecture (ISA) and Checkland{\textquoteright}s CATWOE framework from Soft Systems Methodology (SSM). The resulting framework is used to analyze the OSS approach in detail. The potential future of OSS research is also discussed.},
	url = {http://portal.acm.org/citation.cfm?id=359640.359723},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p58-feller.pdf},
	author = {Feller, Joseph and Fitzgerald, Brian}
}
@article {flosswp12,
	title = {Internet Innovation and Open Source: Actors in the Network},
	year = {2000},
	month = {November},
	abstract = {The paper analyzes the growth and development of the Linux community and demonstrates how it evolves into an ecology of community-centered practices.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Ilkka\%2520Tuomi\%2520-\%2520Actors\%2520in\%2520the\%2520Network.pdf},
	author = {Ilkka Tuomi}
}
@article {flosswp9,
	title = {The Linux Kernel Development As a Model of Knowledge Creation},
	year = {2000},
	month = {October},
	abstract = {Applying the method of induction theory building, the authors have developed a case study based on the Linux kernel development process to build a model of Open Source knowledge creation.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LinuxKernelDevelopmentAbstract.pdf},
	author = {Gwendolyn Lee}
}
@article {58,
	title = {Open source movements as a model for organising},
	journal = {European Journal of Information Systems},
	volume = {9},
	year = {2000},
	pages = {208--216},
	abstract = {Open source software such as the operating system Linux has in a few years created much attention as an alternative way to develop and distribute software. Open source is to let anyone have access to the source code, so that they can modify it. Open source could be seen as a movement, where communities of highly skilled programmers collectively develop software, often of a quality that outperforms commercial proprietary software. These movements are based on virtual networking on Internet and the web. They are loosely coupled communities kept together by strong common values related to hacker culture. Work seems to be totally distributed, delegated and loosely coupled. The highly skilled members contribute by pride to the collective effort of free software development. In this paper the open source phenomena is investigated from different perspectives. In this paper it is claimed that the open source movements is one key to the understanding of future forms of organizations, knowledge work and business.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/20000077.pdf},
	author = {Ljungberg, J.}
}
@article {flosswp7,
	title = {Open Source Software As Consumer Integration Into Production},
	year = {2000},
	month = {October},
	abstract = {The author proposes a model of consumer integration into production as means of understanding the Open Source software phenomenon.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Jenny\%2520Kuan\%2520-\%2520Open\%2520Source\%2520Software\%2520As\%2520Integration\%2520into\%2520Production.pdf},
	author = {Jenny Kuan}
}
@article {flosswp14,
	title = {The Political Economy of Open Source},
	year = {2000},
	month = {June},
	abstract = {The paper describes the open source process and characterizes more fully the economic, technological, and social systems that together constitute this distinct mode of production. The paper explains the open source process, by answering three questions about individual motivations, coordination, and complexity using a compoud argument of microfoundations, economic logic, and social/political structure.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wp140.pdf},
	author = {Steven Weber}
}
@article {flosswp3,
	title = {Profiting From Voluntary Information Spillovers: How Users Benefit By Freely Revealing Their Innovations},
	year = {2000},
	month = {July},
	abstract = {Software users reveal the code they have written to other users for free. This behavior is contrary to conventional wisdom in economics - but is essential to the functioning of an effective user innovation community. This paper explores conditions under which the free revealing of innovations (code, in the case of OS) pays for innovating users.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/evhippel-voluntaryinfospillover.pdf},
	author = {Dietmar Harhoff and Joachim Henkel and von Hippel, Eric}
}
@article {flosswp6,
	title = {Results From Software Engineering Research Into Open Source Development Projects Using Public Data},
	number = {22},
	year = {2000},
	institution = {Diskussionspapiere zum T{\"a}tigkeitsfeld Informationsverarbeitung und Informationswirtschaft},
	type = {Discussion Paper},
	abstract = {This paper presents first 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 in detail and some of the results concerning the special characteristics of open source software development are given.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/koch-ossoftwareengineering.pdf},
	author = {Koch, Stefan and Schneider Georg}
}
@article {flosswp10,
	title = {The Simple Economics of Open Source},
	year = {2000},
	month = {March},
	abstract = {This paper makes a preliminary exploration of the economics of open source software. The authors highlight the extent to which labor economics, especially the literature of career concerns can explain many of these project features.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Josh\%2520Lerner\%2520and\%2520Jean\%2520Triole\%2520-\%2520The\%2520Simple\%2520Economics\%2520of\%2520Open\%2520Source.pdf},
	author = {Josh Lerner}
}
@article {flosswp15,
	title = {Sources and Patterns of Innovation in a Consumer Products Field: Innovations in Sporting Equipment},
	year = {2000},
	month = {November},
	abstract = {This study investigates the innovation histories of 57 important skateboarding, snowboarding, and windsurfing equipment innovations. Contrary to conventional wisdom, equipment for these new sports was not developed by existing sports equipment manufacturing companies. Innovations were instead developed by a few early and active participants in the new sports - users who built innovative equipment for themselves, their friends, and often built businesses focused on producing such equipment in order to appropriate benefit from their innovations and establish a lifestyle around the sport.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shahsportspaper.pdf},
	author = {Sonali Shah}
}
@article {59,
	title = {A Brief History of Hackerdom},
	year = {1999},
	pages = {1--7},
	author = {Raymond, E.S.}
}
@book {55,
	title = {Code and Other Laws of Cyberspace},
	year = {1999},
	publisher = {Basic Books},
	organization = {Basic Books},
	author = {Lessig, L.}
}
@article {913,
	title = {Dimensions of information systems success},
	journal = {Communications of the Association for Information Systems},
	volume = {20},
	number = {2},
	year = {1999},
	pages = {61},
	author = {Seddon, PB and Staples, S and Patnayakuni, R and Bowtell, M}
}
@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}
}
@article {60,
	title = {The Revenge of the Hackers},
	year = {1999},
	pages = {207--219},
	author = {Raymond, E.S.}
}
@unpublished {flosswp4,
	title = {Scale and Convention: Programmed Languages in a Regulated America},
	year = {1999},
	month = {December},
	abstract = {This thesis is a combination of an ethnography of an internet healthcare startup company and a philosophical investigation of technical standards, open and closed. Chapters K, L, and M are introductions to three main figures in the Open Source movement between 1998-2000 {\textendash} Richard Stallman, Lawrence Lessig, and Eric Raymond.},
	author = {Christoper Kelty}
}
@proceedings {108,
	title = {Splitting the organization and integrating the code: Conway{\textquoteright}s law revisited},
	year = {1999},
	pages = {85{\textendash}95},
	publisher = {ACM},
	address = {Los Angeles, CA},
	author = {Herbsleb, J. D. and Rebecca E. Grinter}
}
@article {flosswp24,
	title = {Changing Competitive Dynamics in Network Industries: An Exploration of SUN Microsystems{\textquoteright} Open Systems Strategy},
	year = {1993},
	month = {Unspecified},
	abstract = {An integral part of competition is to deny rivals access to proprietary technical knowledge. Yet, SUN Microsystems provides rivals with easy access to its technical knowledge and encourages them to enter its workstation market. This paper employs theoretical insights on technological systems and network externalities to understand SUN{\textquoteright}s open systems strategy. The paper also explores the changing nature of competition in network industries.},
	author = {Raghu Garud}
}
@article {flosswp383,
	title = {Knee-jerk Anti-LOOPism and other E-mail Phenomena: Oral, Written, and Electronic Patterns in Computer-Mediated Communication},
	number = {WP \3578-93},
	year = {1993},
	month = {June},
	institution = {Massachusetts Institute of Technology},
	type = {Technical Report},
	address = {Cambridge, MA},
	abstract = {This paper reports on an empirical investigation into the on-going electronic interaction of a natural distributed group. Prior organizational research into use of electronic media has focused primarily on usage patterns and only occasionally on a few linguistic features, while linguistics researchers have looked more closely at certain technical aspects of language use in electronic communication. Interested in a broader range of linguistic and textual features that might be exhibited in the electronic mail medium, we conducted an exploratory study of the electronic communication of a task-oriented group over a 27-month period. Using qualitative and quantitative techniques, we found that the electronic mail messages displayed features normally associated with both speech and written discourse, as well as features that seem new to the electronic medium. The use of all three patterns was influenced by characteristics of the medium, the group, and its task.},
	author = {JoAnne Yates and Wanda Orlikowski}
}
@unpublished {flosswp377,
	title = {Game Theory and The Law: The Arbitration System},
	year = {1985},
	month = {January},
	abstract = {The paper refers to a game-theoretic analysis of the nature of legal arbitration, and the effects of prior negotiation. Also, it promotes the use of final-offer arbitration in labor disputes and in the event of an strike.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/TESIS_COMPLETA.pdf},
	author = {Guillermo Flores}
}
