@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 {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 {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}
}
@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 {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}
}
@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}
}
@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}
}
@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 {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.}
}
@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 {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}
}
@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 {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}
}
@proceedings {1854,
	title = {Differentiating Communication Styles of Leaders on the Linux Kernel Mailing List},
	year = {2016},
	note = {Slides link: https://docs.google.com/presentation/d/1_5kqOXBYwH33ayfGKCncCtCondfUYtsHSDBS3DBig6Y/edit?usp=sharing
Edited to fix typo in abstract. New version is v3.pdf},
	month = {08/2016},
	publisher = {ACM},
	abstract = {Much communication between developers of free, libre, and open source software (FLOSS) projects happens on email mailing lists. Geographically and temporally dispersed development teams use email as an asynchronous, centralized, persistently stored institutional memory for sharing code samples, discussing bugs, and making decisions. Email is especially important to large, mature projects, such as the Linux kernel, which has thousands of developers and a multi-layered leadership structure. In this paper, we collect and analyze data to understand the communication patterns in such a community. How do the leaders of the Linux Kernel project write in email? What are the salient features of their writing, and can we discern one leader from another? We find that there are clear written markers for two leaders who have been particularly important to recent discussions of leadership style on the Linux Kernel Mailing List (LKML): Linux Torvalds and Greg Kroah-Hartman. Furthermore, we show that it is straightforward to use a machine learning strategy to automatically differentiate these two leaders based on their writing. Our findings will help researchers understand how this community works, and why there is occasional controversy regarding differences in communication styles on the LKML.},
	keywords = {email, flossmole, linus torvalds, linux, lkml},
	attachments = {https://flosshub.org/sites/flosshub.org/files/v3_0.pdf},
	author = {Schneider, Daniel and Spurlock, Scott and Squire, Megan}
}
@proceedings {1866,
	title = {Does the Task Structure of Open Source Projects Matter? Superposition and Value Creation},
	year = {2016},
	month = {11/2016},
	publisher = {AIS},
	abstract = {Collaboration through open superposition describes a process of building free (libre) and open source software (FLOSS), wherein motivationally independent layers of work is sequentially added one-on-top the other over time. This research-in-progress paper theorizes the mechanisms through which superposition influences the value of individual and organizational owned FLOSS projects. We argue for a non-linear relationship between degree of superposition and value of the FLOSS project. Moreover, we posit that the type of ownership will moderate this non-linear relationship. The moderation effect is such that {\textendash} (1) organizational ownership mitigates the influence of degree of superposition on project value (2) under organizational ownership, the optimal value of degree of superposition (the point at which the project value is maximum) is lower as compared to individual owned projects. This research attempts to advance the theory of superposition and unearth the influence of task structure on the value of the FLOSS project.},
	author = {Poonacha K. Medappa and Shirish C. Srivastava}
}
@proceedings {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}
}
@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}
}
@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}
}
@inbook {Abdulwahhab2016,
	title = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {3{\textendash}15},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	address = {Cham},
	abstract = {This paper investigates the position of local open source communities (LOSCs) in the development of open source projects (OSPs). We have conducted an empirical study to examine the role of LOSCs, their way of working, and the benefits/challenges they experience compared to the overall global community. The qualitative investigation consisted of ten semi-structured interviews with members within different LOSCs. The results confirm the importance of LOSCs and the pivotal role they play in the development of OSPs. In many cases, they act as the middleman between individual members and the project{\textquoteright}s global community. However, LOSCs have their own kinds of challenges.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_1},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_1},
	author = {Abdulwahhab, Sinan and Alabady, Yazen and Sattar, Yacoub and Hammouda, Imed},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {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.}
}
@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}
}
@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}
}
@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 {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}
}
@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}
}
@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 {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 {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}
}
@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.}
}
@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}
}
@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 {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}
}
@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 {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.}
}
@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}
}
@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}
}
@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}
}
@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.}
}
@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}
}
@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}
}
@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 {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}
}
@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.}
}
@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 {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.}
}
@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.}
}
@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 {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 {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}
}
@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.}
}
@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}
}
@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 {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}
}
@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.}
}
@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 {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}
}
@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.}
}
@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 {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.}
}
@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.}
}
@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.}
}
@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.}
}
@inbook {1626,
	title = {When Are OSS Developers More Likely to Introduce Vulnerable Code Changes? A Case Study},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {234-236},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

We analyzed peer code review data of the Android Open Source Project (AOSP) to understand whether code changes that introduce security vulnerabilities, referred to as vulnerable code changes (VCC), occur at certain intervals. Using a systematic manual analysis process, we identified 60 VCCs. Our results suggest that AOSP developers were more likely to write VCCs prior to AOSP releases, while during the post-release period they wrote fewer VCCs.
},
	keywords = {FOSS, open source, OSS, security, vulnerability},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_37},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_37},
	author = {Bosu, Amiangshu and Carver, JeffreyC. and Hafiz, Munawar and Hilley, Patrick and Janni, Derek},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1593,
	title = {Who Contributes to What? Exploring Hidden Relationships between FLOSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {21-30},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {In this paper we address the challenge of tracking resembling open source projects by exploiting the information of which developers contribute to which projects. To do this, we have performed a social network study to analyze data collected from the Ohloh repository. Our findings suggest that the more shared contributors two projects have, the more likely they resemble with respect to properties such as project application domain, programming language used and project size.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_3},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_3},
	author = {Syeed, M.M.Mahbubul and Hammouda, Imed},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@proceedings {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}
}
@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 {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}
}
@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 {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}
}
@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}
}
@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}
}
@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.}
}
@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 {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 {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}
}
@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}
}
@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 {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}
}
@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}
}
@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}
}
@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}
}
@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.}
}
@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}
}
@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}
}
@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 {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}
}
@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 {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 {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}
}
@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}
}
@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 {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 {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}
}
@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}
}
@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 {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 {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 {1319,
	title = {Who Will Remain? An Evaluation of Actual Person-Job and Person-Team Fit to Predict Developer Retention in FLOSS Projects},
	booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences},
	year = {2012},
	month = {01/2012},
	pages = {3446-3455},
	abstract = {Many businesses and private households rely on Free Libre Open Source Software (FLOSS). Due to a lack of sustained contributors, however, most FLOSS projects do not survive. The early identification of developers who are likely to remain is thus an eminent challenge for the management of FLOSS initiatives. Previous research has shown that individuals{\textquoteright} subjective assessment is often inaccurate emphasizing the need to objectively evaluate retention behavior. Consistent with the concepts Person-Job (P-J) and Person-Team (P-T) fit from the traditional recruitment literature, we derive objective measures to predict developer retention in FLOSS projects. In an analysis of the contribution behavior of former Google Summer of Code (GSoC) students we reveal that the level of development experience and conversational knowledge is strongly associated with retention. Surprisingly, our analysis reveals that students with abilities that are underrepresented in the project and students with a higher academic education do not remain considerably longer.},
	keywords = {email, email archives, google summer of code, kde, mailing list, students},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2012.644},
	attachments = {https://flosshub.org/sites/flosshub.org/files/45.pdf},
	author = {Schilling, A. and Laumer, S. and Weitzel, T.}
}
@proceedings {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 {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}
}
@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}
}
@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}
}
@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 {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}
}
@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}
}
@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}
}
@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}
}
@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}
}
@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 {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}
}
@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}
}
@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}
}
@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 {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}
}
@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}
}
@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 {961,
	title = {Do stack traces help developers fix bugs?},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {118 - 121},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {A widely shared belief in the software engineering community is that stack traces are much sought after by developers to support them in debugging. But limited empirical evidence is available to confirm the value of stack traces to developers. In this paper, we seek to provide such evidence by conducting an empirical study on the usage of stack traces by developers from the ECLIPSE project. Our results provide strong evidence to this effect and also throws light on some of the patterns in bug fixing using stack traces. We expect the findings of our study to further emphasize the importance of adding stack traces to bug reports and that in the future, software vendors will provide more support in their products to help general users make such information available when filing bug reports.},
	keywords = {bug fixing, bug report, debugging, eclipse, stack trace},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463280},
	attachments = {https://flosshub.org/sites/flosshub.org/files/118-10-msr.pdf},
	author = {Schroter, Adrian and Schr{\"o}ter, Adrian and Bettenburg, Nicolas and Premraj, Rahul}
}
@inbook {springerlink:10.1007/978-3-642-13244-5_20,
	title = {Download Patterns and Releases in Open Source Software Projects: A Perfect Symbiosis?},
	booktitle = {Open Source Software: New Horizons},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {319},
	year = {2010},
	note = {"We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository."},
	pages = {252-267},
	publisher = {Springer Boston},
	organization = {Springer Boston},
	abstract = {Software usage by end-users is one of the factors used to evaluate the success of software projects. In the context of open source software, there is no single and non-controversial measure of usage, though. Still, one of the most used and readily available measure is data about projects downloads. Nevertheless, download counts and averages do not convey as much information as the patterns in the original downloads time series. In this research, we propose a method to increase the expressiveness of mere download rates by considering download patterns against software releases. We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository. Findings show that projects with similar usage can have indeed different levels of sensitivity to releases, revealing different behaviors of users. Future research will develop further the pattern recognition approach to automatically categorize open source projects according to their download patterns.},
	keywords = {flossmole, oss2010, sourceforge},
	url = {http://dx.doi.org/10.1007/978-3-642-13244-5_20},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s and Madey, Gregory and Noll, John}
}
@conference {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 {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}
}
@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}
}
@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 {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}
}
@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 {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 {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}
}
@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.}
}
@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 {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}
}
@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.}
}
@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 {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}
}
@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 {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}
}
@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 {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 {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}
}
@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}
}
@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 {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}
}
@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 {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 {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 {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}
}
@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 {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 {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.}
}
@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 {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 {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 {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}
}
@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 {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 {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}
}
@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}
}
@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}
}
@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 {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 {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}
}
@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.}
}
@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 {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}
}
@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 {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 {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 {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 {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.}
}
@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}
}
@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 {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.}
}
@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.}
}
@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}
}
@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}
}
@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}
}
@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.}
}
@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}
}
@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 {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 {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 {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 {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}
}
@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}
}
@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.}
}
@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 {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 {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 {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 {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.}
}
@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}
}
@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 {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}
}
@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 {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}
}
@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 {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 {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}
}
@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}
}
@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 {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}
}
@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 {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}
}
@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}
}
@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}
}
@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}
}
@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}
}
@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}
}
@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}
}
@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 {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 {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 {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}
}
@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}
}
@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 {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 {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}
}
@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}
}
@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}
}
@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}
}
@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}
}
@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 {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 {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}
}
@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 {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 {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 {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}
}
@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.}
}
@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.}
}
@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.}
}
@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}
}
@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}
}
@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}
}
@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 {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 {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 {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.}
}
@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 {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 {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.}
}
@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 {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 {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}
}
@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}
}
@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.}
}
@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.}
}
@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}
}
@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 {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.}
}
@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 {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.}
}
@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 {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 {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 {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}
}
@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}
}
@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 {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}
}
@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 {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}
}
@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 {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 {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 {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.}
}
@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 {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}
}
@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 {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.}
}
@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}
}
@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}
}
@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 {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}
}
@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}
}
@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}
}
@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.}
}
@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}
}
@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 {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.}
}
@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 {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}
}
@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}
}
@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 {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}
}
@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}
}
@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}
}
@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 {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}
}
@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 {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}
}
@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}
}
@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 {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 {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}
}
@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.}
}
@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 {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}
}
@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.}
}
@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 {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 {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}
}
@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 {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}
}
@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}
}
@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 {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 {74,
	title = {Survival of open-source projects: A population ecology perspective},
	year = {2003},
	keywords = {open source},
	author = {Chengalur-Smith, Shobha and Sidorova, Anna}
}
@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.}
}
@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 {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 {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.}
}
@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}
}
@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}
}
@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 {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 {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}
}
@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}
}
@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 {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}
}
@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}
}
@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}
}
@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.}
}
@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}
}
@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 {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}
}
@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 {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}
}
@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.}
}
@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.}
}
@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 {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}
}
@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}
}
@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 {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 {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}
}
