@proceedings {1902,
	title = {Assessing Code Authorship: The Case of the Linux Kernel},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {151-163},
	publisher = {Springer},
	abstract = {Code authorship is a key information in large-scale open-source systems. Among others, it allows maintainers to assess division of work and identify key collaborators. Interestingly, open-source communities lack guidelines on how to manage authorship. This could be mitigated by setting to build an empirical body of knowledge on how authorship-related measures evolve in successful open-source communities. Towards that direction, we perform a case study on the Linux kernel. Our results show that: (a) only a small portion of developers (26\%) makes significant contributions to the code base; (b) the distribution of the number of files per author is highly skewed{\textemdash}a small group of top-authors (3\%) is responsible for hundreds of files, while most authors (75\%) are responsible for at most 11 files; (c) most authors (62\%) have a specialist profile; (d) authors with a high number of co-authorship connections tend to collaborate with others with less connections.},
	keywords = {code authorship, developer network, linux kernel},
	doi = {10.1007/978-3-319-57735-7_15},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_15},
	author = {Guilherme Avelino and Passos, Leonardo and Andre Hora and Marco Tulio Valente}
}
@article {1924,
	title = {Developers, Quality Control and Download Volume in Open Source Software (OSS) Projects},
	journal = {Journal of Organizational and End User Computing},
	volume = {29},
	year = {2017},
	month = {04/2017},
	pages = {43 - 66},
	abstract = {The open-source software (OSS) movement is often analogized as a commons, where products are developed by and consumed in an open community. However, does a larger commons automatically beget success or does the phenomenon fall prey to the tragedy of the commons? This research forwards and empirically investigates the curvilinear relationship between developers and OSS project quality and a project{\textquoteright}s download volume. Using segmented regression on over 12,000 SourceForge OSS projects, findings suggest an inflection point in the number of contributing developers on download volume {\textendash} suggesting increasing and diminishing returns to scale from adding developers to OSS projects. Findings support the economic principle of the tragedy of the commons, a concept where an over-allocated (large number) of developers, even in an open-source environment, can lead to resource mismanagement and reduce the benefit of a public good, i.e. the OSS project.
},
	issn = {1546-5012},
	doi = {10.4018/JOEUC.2017040103},
	author = {Hill, Geoffrey and Datta, Pratim and Vander Weerdt, Candice}
}
@proceedings {1907,
	title = {Do Software Developers Understand Open Source Licenses?},
	year = {2017},
	note = {Data: We report on the results of a survey that asked
developers about 42 different cases of the use of code under
different open source licenses. To make the survey tractable
for developers to answer, we focused on three popular open
source licenses (GNU GPL 3.0, GNU LGPL 3.0 and MPL
2.0)

Findings: The survey results indicate that most of the 375 respondents
to our survey struggle with understanding the interaction of
open source licenses in both simple and complex software
development cases},
	month = {05/2017},
	pages = {1-11},
	abstract = {{\textemdash}Software provided under open source licenses is
widely used, from forming high-profile stand-alone applications
(e.g., Mozilla Firefox) to being embedded in commercial offerings
(e.g., network routers). Despite the high frequency of use of open
source licenses, there has been little work about whether software
developers understand the open source licenses they use. To our
knowledge, only one survey has been conducted, which focused
on which licenses developers choose and when they encounter
problems with licensing open source software. To help fill the
gap of whether or not developers understand the open source
licenses they use, we conducted a survey that posed development
scenarios involving three popular open source licenses (GNU GPL
3.0, GNU LGPL 3.0 and MPL 2.0) both alone and in combination.
The 375 respondents to the survey, who were largely developers,
gave answers consistent with those of a legal expert{\textquoteright}s opinion in
62\% of 42 cases. Although developers clearly understood cases
involving one license, they struggled when multiple licenses were
involved. An analysis of the quantitative and qualitative results of
the study indicate a need for tool support to help guide developers
in understanding this critical information attached to software
components.},
	keywords = {license, Survey},
	doi = {10.1109/ICPC.2017.7},
	author = {Almeida, Daniel A. and Murphy, Gail C. and Wilson, Greg and Hoye, Mike}
}
@proceedings {1913,
	title = {An Empirical Analysis of Build Failures in the Continuous Integration Workflows of Java-Based Open-Source Software},
	year = {2017},
	note = {"empirical study of CI build
failures in 14 Java-based OSS projects. We extract and analyze
data from publicly available GitHub repositories and Travis-CI
build logs"},
	month = {05/2017},
	pages = {345-355},
	abstract = {{\textemdash}Continuous Integration (CI) has become a common
practice in both industrial and open-source software development.
While CI has evidently improved aspects of the software
development process, errors during CI builds pose a threat to
development efficiency. As an increasing amount of time goes
into fixing such errors, failing builds can significantly impair the
development process and become very costly. We perform an indepth
analysis of build failures in CI environments. Our approach
links repository commits to data of corresponding CI builds.
Using data from 14 open-source Java projects, we first identify
14 common error categories. Besides test failures, which are by
far the most common error category (up to >80\% per project),
we also identify noisy build data, e.g., induced by transient Git
interaction errors, or general infrastructure flakiness. Second,
we analyze which factors impact the build results, taking into
account general process and specific CI metrics. Our results
indicate that process metrics have a significant impact on the
build outcome in 8 of the 14 projects on average, but the strongest
influencing factor across all projects is overall stability in the
recent build history. For 10 projects, more than 50\% (up to 80\%)
of all failed builds follow a previous build failure. Moreover, the
fail ratio of the last k=10 builds has a significant impact on build
results for all projects in our dataset.},
	keywords = {build errors, continuous integration, correlation analysis, msr},
	author = {Thomas Rausch and Waldemar Hummer and Philipp Leitner and Stefan Schulte}
}
@proceedings {1889,
	title = {Investigating Relationships Between FLOSS Foundations and FLOSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {14-22},
	publisher = {Springer},
	abstract = {Foundations function as vital institutional support infrastructures for many of the most successful open source projects, but the role of these support entities remains an understudied phenomenon in FLOSS research. Drawing on Open Hub (formerly known as Ohloh) data, this paper empirically investigates the different ways these entities support projects and interact with different projects and with each other.},
	doi = {10.1007/978-3-319-57735-7_2},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_2},
	author = {Juho Lindman and Hammouda, Imed}
}
@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 {1914,
	title = {Practices and Perceptions of UML Use in Open Source Projects},
	year = {2017},
	month = {05/2017},
	pages = {203-212},
	abstract = {Context: Open Source is getting more and more
collaborative with industry. At the same time, modeling is today
playing a crucial role in development of, e.g., safety critical
software. Goal: However, there is a lack of research about the
use of modeling in Open Source. Our goal is to shed some
light into the motivation and benefits of the use of modeling
and its use within project teams. Method: In this study, we
perform a survey among Open Source developers. We focus on
projects that use the Unified Modeling Language (UML) as a
representative for software modeling. Results: We received 485
answers of contributors of 458 different Open Source projects.
Conclusion: Collaboration seems to be the most important
motivation for using UML. It benefits new contributors and
contributors who do not create models. Teams use UML during
communication and planning of joint implementation efforts.},
	keywords = {architecture documentation, communication, effectiveness of UML, github, MOTIVATION, UML},
	author = {Truong Ho-Quang and Hebig, Regina and Gregorio Robles and Chaudron, Michel R. V. and Miguel Angel Fernandez}
}
@inbook {Bibi2016,
	title = {A Bayesian Belief Network for Modeling Open Source Software Maintenance Productivity},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {32{\textendash}44},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {A Bayesian Belief Network for Modeling Open Source Software Maintenance Productivity},
	address = {Cham},
	abstract = {Maintenance is one of the most effort consuming activities in the software development lifecycle. Efficient maintenance within short release cycles depends highly on the underlying source code structure, in the sense that complex modules are more difficult to maintain. In this paper we attempt to unveil and discuss relationships between maintenance productivity, the structural quality of the source code and process metrics like the type of a release and the number of downloads. To achieve this goal, we developed a Bayesian Belief Network (BBN) involving several maintainability predictors and three managerial indices for maintenance (i.e., duration, production, and productivity) on 20 open source software projects. The results suggest that maintenance duration depends on inheritance, coupling, and process metrics. On the other hand maintenance production and productivity depend mostly on code quality metrics.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_3},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_3},
	author = {Bibi, Stamatia and Apostolos Ampatzoglou and Ioannis Stamelos},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Rodr{\'\i}guez-P{\'e}rez2016,
	title = {BugTracking: A Tool to Assist in the Identification of Bug Reports},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {192{\textendash}198},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {BugTracking: A Tool to Assist in the Identification of Bug Reports},
	address = {Cham},
	abstract = {Issue tracking systems are used, in most software projects, but in particular in almost all free open source software, to record many different kinds of issues: bug reports, feature requests, maintenance tickets and even design discussions. Identifying which of those issues are bug reports is not a trivial task. When researchers want to conduct studies on the bug reports, managed by a software development project, first of all they need to perform this identification.
The job for researchers here is very different from the bug triaging that researchers do. In the latter case, people with a considerate experience in the project make a decision based on the information available at that time (maybe just a short comment by some user), asking, if needed, for more details. In the former case, researchers usually have not that experience in the project, but they have at their use all the information produced, until the moment the issue was closed. This may include not only all comments and actions on the issue tracking system, but for example, discussions about a fix in the code review system, or the final fixing patch in the source code management system. Having all that information conveyed to the researchers, in an easy, flexible and quick way, accelerates and makes their decision process much more reliable. It simplifies large scale manual analysis of issues (in hundreds or thousands), helping researchers to ensure that they are really working with what they intend to work: bug reports.
This paper presents a tool designed to solve exactly the problem of providing the researchers with all the relevant information needed to decide whether an issue corresponds to a bug report or not. The tool uses information extracted automatically from the projects repositories. It offers a web-based interface which allows collaboration, traceability and transparency of the identification of bug reports. All this makes the process easier, faster, and more reliable.},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_16},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_16},
	author = {Rodr{\'\i}guez-P{\'e}rez, Gema and Gonzalez-Barahona, Jes{\'u}s M. and Gregorio Robles and Dalipaj, Dorealda and Sekitoleko, Nelson},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Kalliamvakou2016,
	title = {Certification of Open Source Software {\textendash} A Scoping Review},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {111{\textendash}122},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Certification of Open Source Software {\textendash} A Scoping Review},
	address = {Cham},
	abstract = {Open source software (OSS) systems are being used for increasingly critical functions in modern societies, e.g., in health care, finance, government, defense, and other safety and security sensitive sectors. There is an increasing interest in software certification as a means to assure quality and dependability of such systems. However, the development processes and organizational structures of OSS projects can be substantially different from traditional closed-source projects. The distributed, {\textquotedblleft}bazaar-style{\textquotedblright} approach to software development in OSS systems is often perceived incompatible with certification. This paper presents the results of a scoping review on certification in OSS systems in order to identify and categorize key issues and provide a comprehensive overview of the current evidence on this topic.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_9},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_9},
	author = {Kalliamvakou, Eirini and Weber, Jens and Knauss, Alessia},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Murphy2016,
	title = {Classifying Organizational Adoption of Open Source Software: A Proposal},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {123{\textendash}133},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Classifying Organizational Adoption of Open Source Software: A Proposal},
	address = {Cham},
	abstract = {Staged adoption models are a common feature of information systems (IS) adoption literature, yet these are rarely used in open source software (OSS) adoption studies. In this paper, a staged model for classifying the organizational adoption of OSS is proposed, based upon a critical review of existing staged adoption models and factors identified from OSS adoption literature. Innovations in the proposed model include: defined transition pathways between stages, additional stages and a decomposition of cessation of use into four distinct pathways.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_10},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_10},
	author = {Murphy, Stephen and Cox, Sharon},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Harzl2016,
	title = {Combining FOSS and Kanban: An Action Research},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {71{\textendash}84},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Combining FOSS and Kanban: An Action Research},
	address = {Cham},
	abstract = {Even though Free and Open Source Software (FOSS) and Agile Software Development (ASD) have been recognized as important ways to develop software, share some similarities, and have many success stories, there is a lack of research regarding the comprehensive integration of both practices. This study attempts to consolidate these methods and to answer if FOSS and ASD can be combined successfully. Action Reseach (AR) is conducted with one sub-team of a large FOSS project. We performed two action research cycles based on the Kanban method. This paper has two main contributions; first, it describes a real world situation, where Kanban is applied to a FOSS project, and second, it suggests two new Kanban practices. These two methods are targeted specifically at FOSS projects and their characteristics.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_6},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_6},
	author = {Harzl, Annemarie},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Crowston2016,
	title = {Core-Periphery Communication and the Success of Free/Libre Open Source Software Projects},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {45{\textendash}56},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {We examine the relationship between communications by core and peripheral members and Free/Libre Open Source Software project success. The study uses data from 74 projects in the Apache Software Foundation Incubator. We conceptualize project success in terms of success building a community, as assessed by graduation from the Incubator. We compare successful and unsuccessful projects on volume of communication by core (committer) and peripheral community members and on use of inclusive pronouns as an indication of efforts to create intimacy among team members. An innovation of the paper is that use of inclusive pronouns is measured using natural language processing techniques. We find that core and peripheral members differ in their volume of contribution and in their use of inclusive pronouns, and that volume of communication is related to project success.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_4},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_4},
	author = {Kevin Crowston and Shamshurin, Ivan},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@article {adams2016empirical,
	title = {An empirical study of integration activities in distributions of open source software},
	journal = {Empirical Software Engineering},
	volume = {21},
	number = {3},
	year = {2016},
	pages = {960{\textendash}1001},
	publisher = {Springer},
	abstract = {Reuse of software components, either closed or open source, is considered to be one of the most important best practices in software engineering, since it reduces development cost and improves software quality. However, since reused components are (by definition) generic, they need to be customized and integrated into a specific system before they can be useful. Since this integration is system-specific, the integration effort is non-negligible and increases maintenance costs, especially if more than one component needs to be integrated. This paper performs an empirical study of multi-component integration in the context of three successful open source distributions (Debian, Ubuntu and FreeBSD). Such distributions integrate thousands of open source components with an operating system kernel to deliver a coherent software product to millions of users worldwide. We empirically identified seven major integration activities performed by the maintainers of these distributions, documented how these activities are being performed by the maintainers, then evaluated and refined the identified activities with input from six maintainers of the three studied distributions. The documented activities provide a common vocabulary for component integration in open source distributions and outline a roadmap for future research on software integration.

},
	url = {http://mcis.soccerlab.polymtl.ca/publications/2016/integration_oss_distribution.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/integration_oss_distribution.pdf},
	author = {Adams, Bram and Kavanagh, Ryan and Hassan, Ahmed E. and Daniel M. German}
}
@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}
}
@inbook {Hirao2016,
	title = {The Impact of a Low Level of Agreement Among Reviewers in a Code Review Process},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {97{\textendash}110},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Software code review systems are commonly used in software development. In these systems, many patches are submitted to improve the quality. To verify the quality, voting is commonly used by contributors; however, there still exists a major problem, namely, that reviewers do not always simply reach a broad agreement. In our previous study, we found that consensus is not usually reached, implying that an individual reviewer{\textquoteright}s final decision usually differs from that of the majority of the other reviewers. In this study, we further investigate the reasons why such situations often occur, and provide suggestions for better handling of these problems. Our analysis of the Qt and OpenStack project datasets allow us to suggest that a patch owner should select more appropriate reviewers who often agree with others{\textquoteright} decisions.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_8},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_8},
	author = {Hirao, Toshiki and Ihara, Akinori and Ueda, Yuki and Phannachitta, Passakorn and Matsumoto, Ken-ichi},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {M{\"a}enp{\"a}{\"a}2016,
	title = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {134{\textendash}146},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities},
	address = {Cham},
	abstract = {Today, the community driven development model extends into a variety of new, often web based collaborations. Among these are hybrid open source development set ups in which various online tools are used to facilitate cooperation between virtual teams of commercial and voluntary stakeholders. As yet, how these relationships form and evolve is not understood extensively. This article presents a longitudinal case study of a smartphone startup that founded its early product development strategy on reliance on feedback from its customers through a web based question and answer forum. With this, the company managed to extend values typical for open source communities to support development of its proprietary software. Our main findings include that the challenge in similar settings lies in striking the right balance between the open and the proprietary {\textendash} while overt openness may risk the competitive advantage of a company, leaving too much behind closed boundaries can create unnecessary friction in the relationship.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_11},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_11},
	author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and M{\"a}nnist{\"o}, Tomi},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Gamalielsson2016,
	title = {On Involvement in Open Standards: How Do Organisations Contribute to W3C Standards Through Editorship?},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {57{\textendash}70},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {On Involvement in Open Standards: How Do Organisations Contribute to W3C Standards Through Editorship?},
	address = {Cham},
	abstract = {Over the years, a number of open standards have been developed and implemented in software for addressing a number of challenges, such as lock-in, interoperability and longevity of software systems and associated digital artefacts. Understanding organisational involvement and collaboration in standardisation is important for informing any future policy and organisational decisions concerning involvement in standardisation. The overarching goal of the study is to establish how organisations contribute to open standards development through editorship. Specifically, the focus is on open standards development in W3C. Through an analysis of editorship for all W3C recommendations we contribute novel findings concerning organisational involvement and collaboration, and highlight contributions from different types of organisations and countries for headquarter of each organisation. We make three principal contributions. First, we establish an overall characterisation of organisational involvement in W3C standardisation. Second, we report on organisational involvement in W3C standardisation over time. Third, we establish organisational collaboration in W3C standardisation through social network analysis.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_5},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_5},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@article {Kazuhiro Yamashita2016,
	title = {Magnet or Sticky? Measuring Project Characteristics from the Perspective of Developer Attraction and Retention},
	journal = {Journal of Information Processing},
	volume = {24},
	number = {2},
	year = {2016},
	pages = {339-348},
	abstract = {Open Source Software (OSS) is vital to both end users and enterprises. As OSS systems are becoming a type of infrastructure, long-term OSS projects are desired. For the survival of OSS projects, the projects need to not only retain existing developers, but also attract new developers to grow. To better understand how projects retain and attract contributors, our preliminary study aimed to measure the personnel attraction and retention of OSS projects using a pair of population migration metrics, called Magnet (personnel attraction) and Sticky (retention) metrics. Because the preliminary study analyzed only 90 projects and the 90 projects are not representative of GitHub, this paper extend the preliminary study to better understand the generalizability of the results by analyzing 16, 552 projects of GitHub. Furthermore, we also add a pilot study to investigate the typical duration between releases to find more appropriate release duration. The study results show that (1) approximately 23\% of developers remain in the same projects that the developers contribute to, (2) the larger projects are likely to attract and retain more developers, (3) 53\% of terminal projects eventually decay to a state of fewer than ten developers and (4) 55\% of attractive projects remain in an attractive category.
},
	keywords = {github, retention},
	doi = {10.2197/ipsjjip.24.339},
	url = {https://www.jstage.jst.go.jp/article/ipsjjip/24/2/24_339/_article},
	author = {Yamashita, Kazuhiro and Kamei, Yasutaka and McIntosh, Shane and Hassan, Ahmed E. and Ubayashi, Naoyasu}
}
@inbook {Berger2016,
	title = {An Open Continuous Deployment Infrastructure for a Self-driving Vehicle Ecosystem},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {177{\textendash}183},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {An Open Continuous Deployment Infrastructure for a Self-driving Vehicle Ecosystem},
	address = {Cham},
	abstract = {Self-driving vehicles are an ongoing research and engineering topic even though first automotive OEMs started to deploy such features to their premium vehicles. Chalmers University of Technology and University of Gothenburg are operating and maintaining a vehicle laboratory comprising 1/10 scaled cars, a Volvo XC90, and a Volvo FH truck to conduct studies with automated driving. This laboratory is used both from researchers from different disciplines and in education. The experimental software for all these platforms is powered by the same software environment for different hardware architectures. Therefore, maintaining and deploying new features and bugfixes to the users of this laboratory in a fast way needs to be organized in a reproducible yet easily maintainable manner. This paper outlines our open approach to encapsulate our build, test, and deployment process using VirtualBox, Docker, and Jenkins.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_14},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_14},
	author = {Berger, Christian},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@conference {1858,
	title = {The quest for open source projects that use UML},
	booktitle = {Proceedings of the ACM/IEEE 19th International Conference on Model Driven Engineering Languages and Systems - MODELS {\textquoteright}16},
	year = {2016},
	pages = {173 - 183},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Context: While industrial use of UML was studied intensely,little is known about UML use in Free/Open Source Soft-ware (FOSS) projects. Goal: We aim at systematically mining GitHub projects to answer the question when mod-els, if used, are created and updated throughout the whole project{\textquoteright}s life-span. Method: We present a semi-automated approach to collect UML stored in images, .xmi, and .uml files and scanned ten percent of all GitHub projects (1.24million). Our focus was on number and role of contributors that created/updated models and the time span during which this happened. Results: We identified and studied 21 316 UML diagrams within 3 295 projects. Conclusion: Creating/updating of UML happens most often during a very short phase at the project start. For 12\% of the models duplicates were found, which are in average spread across 1.88 projects. Finally, we contribute a list of GitHub projects that include UML files.},
	isbn = {9781450343213},
	doi = {10.1145/2976767.2976778},
	url = {https://www.researchgate.net/publication/308869547_The_quest_for_open_source_projects_that_use_UML_mining_GitHub},
	author = {fernandez, miguel angel and Hebig, Regina and Quang, Truong Ho and Chaudron, Michel R. V.}
}
@inbook {Abdulwahhab2016,
	title = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {3{\textendash}15},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	address = {Cham},
	abstract = {This paper investigates the position of local open source communities (LOSCs) in the development of open source projects (OSPs). We have conducted an empirical study to examine the role of LOSCs, their way of working, and the benefits/challenges they experience compared to the overall global community. The qualitative investigation consisted of ten semi-structured interviews with members within different LOSCs. The results confirm the importance of LOSCs and the pivotal role they play in the development of OSPs. In many cases, they act as the middleman between individual members and the project{\textquoteright}s global community. However, LOSCs have their own kinds of challenges.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_1},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_1},
	author = {Abdulwahhab, Sinan and Alabady, Yazen and Sattar, Yacoub and Hammouda, Imed},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@article {1864,
	title = {Roles and politeness behavior in community-based free/libre open source software development},
	journal = {Information \& Management},
	year = {2016},
	month = {11/2016},
	abstract = {Community-based Free/Libre Open Source Software (FLOSS) development relies on contributions from both core and peripheral members. Prior research on core{\textendash}periphery has focused on software coding-related behaviors. We study how core{\textendash}periphery roles are related to social-relational behavior in terms of politeness behavior. Data from two FLOSS projects suggest that both core and peripheral members use more positive politeness strategies than negative strategies. Further, core and peripheral members use different strategies to protect positive face in positive politeness, which we term respect and intimacy, respectively. Our results contribute to FLOSS research and politeness theory.

},
	keywords = {Core{\textendash}periphery structure, open source software development, Politeness behavior},
	issn = {03787206},
	doi = {10.1016/j.im.2016.11.006},
	url = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Group_maintenance\%20paper\%20to\%20share.pdf},
	author = {Kangning Wei and Kevin Crowston and Eseryel, U.Yeliz and Robert Heckman}
}
@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}
}
@inbook {Coman2016,
	title = {Towards Open Source/Data in the Context of Higher Education: Pragmatic Case Studies Deployed in Romania},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {184{\textendash}191},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Towards Open Source/Data in the Context of Higher Education: Pragmatic Case Studies Deployed in Romania},
	address = {Cham},
	abstract = {The open source ideology is unfortunately not so popular in Romania. This subject represents, to this day, an untackled problem especially in various local educational areas. The paper describes an interesting initiative taken this year by the Faculty of Computer Science, University of Ia{\c s}i, Romania to change the collective opinion by progressively pushing the new generations of students through a binding process with the ideas involved in the open source philosophy. Three ongoing initiatives addressing this problem are detailed, including the results we have obtained so far through them, and also the steps that are planned to be taken soon on the matter.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_15},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_15},
	author = {Coman, Alexandru and C{\^\i}tea, Alexandru and Buraga, Sabin C.},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Heppler2016,
	title = {Who Cares About My Feature Request?},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {85{\textendash}96},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Previous studies on issue tracking systems for open source software (OSS) focused mainly on requests for bug fixes. However, requests to add a new feature or an improvement to an OSS project are often also made in an issue tracking system. These inquiries are particularly important because they determine the further development of the software. This study examines if there is any difference between requests of the IBM developer community and other sources in terms of the likelihood of successful implementation. Our study consists of a case study of the issue tracking system BugZilla in the Eclipse integrated development environment (IDE). Our hypothesis, which was that feature requests from outsiders have less chances of being implemented, than feature requests from IBM developers, was confirmed.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_7},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_7},
	author = {Heppler, Lukas and Eckert, Remo and Stuermer, Matthias},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {Robles2016,
	title = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {163{\textendash}173},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	address = {Cham},
	abstract = {Women are underrepresented in the IT sector. But the situation in FLOSS (free, libre, open source software) development is really extreme in this respect: past publications and studies show a female participation of around 2 \% to 5 \% and have shed some light into this problem. In this paper, we give an update the state of knowledge to the current situation of gender in FLOSS, by analyzing the results of surveying more than 2,000 contributors to FLOSS projects in 2013, of which more than 200 were women. Our findings confirm that women enter the FLOSS community later than men, do primarily other tasks than coding, participate less if they have children, and have slightly different reasons to enter (and to stay in) the development communities they join. However, we also find evidence that women are joining FLOSS projects in higher numbers in recent years, and that the share of women devoting few hours per week to FLOSS and full-time dedication is higher than for men. All in all, comparing our results with the ones from the 2000s, the context of participation of women in FLOSS has not changed much.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_13},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_13},
	author = {Gregorio Robles and Reina, Laura Arjona and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Dom{\'\i}nguez, Santiago Due{\~n}as},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@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}
}
@conference {Hata:2015:CSO:2819321.2819325,
	title = {Characteristics of Sustainable OSS Projects: A Theoretical and Empirical Study},
	booktitle = {Proceedings of the Eighth International Workshop on Cooperative and Human Aspects of Software Engineering},
	series = {CHASE {\textquoteright}15},
	year = {2015},
	note = {Slideshare: http://www.slideshare.net/hideakihata5/characteristics-of-sustainable-oss-projects-a-theoretical-and-empirical-study},
	pages = {15{\textendash}21},
	publisher = {IEEE Press},
	organization = {IEEE Press},
	address = {Piscataway, NJ, USA},
	abstract = {How can we attract developers? What can we do to incentivize developers to write code? We started the study by introducing the population pyramid visualization to software development communities, called software population pyramids, and found a typical pattern in shapes. This pattern comes from the differences in attracting coding contributors and discussion contributors. To understand the causes of the differences, we then build game-theoretical models of the contribution situation. Based on these results, we again analyzed the projects empirically to support the outcome of the models, and found empirical evidence. The answers to the initial questions are clear. To incentivize developers to code, the projects should prepare documents, or the projects or third parties should hire developers, and these are what sustainable projects in GitHub did in reality. In addition, making innovations to reduce the writing costs can also have an impact in attracting coding contributors.},
	url = {http://dl.acm.org/citation.cfm?id=2819321.2819325},
	author = {Hata, Hideaki and Todo, Taiki and Onoue, Saya and Kenichi Matsumoto}
}
@proceedings {1763,
	title = {A Dataset of High Impact Bugs: Manually-Classified Issue Reports},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The importance of supporting test and maintenance
activities in software development has been increasing, since
recent software systems have become large and complex. Although
in the field of Mining Software Repositories (MSR) there
are many promising approaches to predicting, localizing, and
triaging bugs, most of them do not consider impacts of each
bug on users and developers but rather treat all bugs with equal
weighting, excepting a few studies on high impact bugs including
security, performance, blocking, and so forth. To make MSR
techniques more actionable and effective in practice, we need
deeper understandings of high impact bugs. In this paper we
introduced our dataset of high impact bugs which was created
by manually reviewing four thousand issue reports in four open
source projects (Ambari, Camel, Derby and Wicket).},
	keywords = {ambari, camel, derby, wicket},
	url = {http://oss.sys.wakayama-u.ac.jp/publications/pman3.cgi?DOWNLOAD=141},
	attachments = {https://flosshub.org/sites/flosshub.org/files/5594a518.pdf},
	author = {Ohira, Masao and Yutaro Kashiwa and Yosuke Yamatani and Hayato Yoshiyuki and Yoshiya Maeda and Nachai Limsettho and Keisuke Fujino and Hata, Hideaki and Ihara, Akinori and Kenichi Matsumoto}
}
@proceedings {1758,
	title = {A Dataset of the Activity of the git Super-repository of Linux in 2012},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {This dataset documents the activity in the public
portion of the git Super-repository of the Linux kernel during
2012. In a distributed version control system, such as git, the
Super-repository is the collection of all the repositories (repos)
used for development. In such a Super-repository, some repos
will be accessible only by their owners (they are private, and
are located in places that are unreachable to other users) while
others are available to other members of the team. The latter
public repositories are used as avenues through which commits
flow from one developer to another. During the last six weeks of
2011, we proceeded to automatically discover the public portion
of the Super-repository of Linux. Then, in 2012, every 3 hrs,
each of these public repositories was queried to see what new
commits it had and what commits had disappeared from it
using a process we call continuous mining. This resulted in the
identification of 533,513 different commits across 451 different
public repositories and how they propagated through the Linux
Super-repository, including the repository of Linus Torvalds (i.e.,
the main repository of the Linux kernel). This information could
help us understand how kernel contributors use git, how they
collaborate and how commits are integrated into the Linux kernel
and into the repositories of organizations that distribute the
kernel.
This dataset is at http://turingmachine.org/2015/linuxGit},
	url = {http://turingmachine.org/2015/linuxGit/msr-data-git-linux.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr-data-git-linux.pdf},
	author = {Daniel M. German and Adams, Bram and Hassan, Ahmed E.}
}
@conference {blincoeMSR15,
	title = {Ecosystems in GitHub and a Method for Ecosystem Identification using Reference Coupling},
	booktitle = {12th Working Conference on Mining Software Repositories},
	series = {MSR},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {Software projects are not developed in isolation.
Recent research has shifted to studying software ecosystems,
communities of projects that depend on each other and are
developed together. However, identifying technical dependencies
at the ecosystem level can be challenging. In this paper, we
propose a new method, known as reference coupling, for detecting
technical dependencies between projects. The method establishes
dependencies through user-specified cross-references between
projects. We use our method to identify ecosystems in GitHubhosted
projects, and we identify several characteristics of the
identified ecosystems. We find that most ecosystems are centered
around one project and are interconnected with other ecosystems.
The predominant type of ecosystems are those that develop
tools to support software development. We also found that the
project owners{\textquoteright} social behaviour aligns well with the technical
dependencies within the ecosystem, but project contributors{\textquoteright}
social behaviour does not align with these dependencies. We
conclude with a discussion on future research that is enabled
by our reference coupling method.},
	url = {http://kblincoe.github.io/publications/2015_MSR_Ecosystems_CameraReady.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2015_MSR_Ecosystems_CameraReady.pdf},
	author = {Blincoe, Kelly and Harrison, Francis and Damian, Daniela}
}
@proceedings {1789,
	title = {The FLOSS History in Japan: An Ethnographic Approach},
	year = {2015},
	month = {08/2015},
	abstract = {This paper reports an overview of the Internet history project
which especially focuses on Free / Libre / Open-Source Software
(FLOSS) history. The project adopts an ethnographical
approach and it aims to compose a chronicle on the
growth of FLOSS history in Japan. An outcome of the
project is expected to be not only a record but a compass
for younger generations. The project has already started
and conducted several interviews. In this paper, an interim
report of our analysis based on the interviews is presented.},
	url = {http://www.opensym.org/os2015/proceedings-files/p105-iio.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p105-iio.pdf},
	author = {Iio, Jun and Hatta, Masayuki and Ko Kazaana}
}
@proceedings {1769,
	title = {Investigating Code Review Practices in Defective Files: An Empirical Study of the Qt System},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Software code review is a well-established software
quality practice. Recently, Modern Code Review (MCR) has been
widely adopted in both open source and proprietary projects.
To evaluate the impact that characteristics of MCR practices
have on software quality, this paper comparatively studies MCR
practices in defective and clean source code files. We investigate
defective files along two perspectives: 1) files that will eventually
have defects (i.e., future-defective files) and 2) files that have
historically been defective (i.e., risky files). Through an empirical
study of 11,736 reviews of changes to 24,486 files from the Qt
open source project, we find that both future-defective files and
risky files tend to be reviewed less rigorously than their clean
counterparts. We also find that the concerns addressed during
the code reviews of both defective and clean files tend to enhance
evolvability, i.e., ease future maintenance (like documentation),
rather than focus on functional issues (like incorrect program
logic). Our findings suggest that although functionality concerns
are rarely addressed during code review, the rigor of the
reviewing process that is applied to a source code file throughout
a development cycle shares a link with its defect proneness.},
	keywords = {code review, software quality},
	url = {http://sail.cs.queensu.ca/publications/pubs/msr2015-thongtanunam.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015-thongtanunam.pdf},
	author = {Patanamon Thongtanunam and McIntosh, Shane and Hassan, Ahmed E. and Hajimu Iida}
}
@proceedings {1785,
	title = {An Investigation of Migrating from Proprietary RTOS to Embedded Linux},
	year = {2015},
	month = {08/2015},
	abstract = {Embedded systems and the open source operating system
Linux have been going hand in hand for a long time now.
Companies using Linux for their embedded products are
praising it for being time and cost efficient when it comes to
performance and maintainability. Another solution for embedded
systems is a Real-Time Operating System (RTOS).
The goal of this this paper is to investigate whether a traditional
proprietary RTOS can be substituted with embedded
Linux, and if this kind of migration can lead to reduced licensing
costs and increased general quality of the system.
We used a qualitative research method for this case-study.
The investigation was conducted with interviews as the main
source of information. The result of this study is an empirical
model we named {\textquoteright}Embedded Linux Adoption Model{\textquoteright}.
We concluded that in many cases a proprietary RTOS can
be substituted with embedded Linux without affecting the
critical needs of the system. The study also showed that
many embedded system developers are very receptive to
open source solutions and could think of contributing to the
community.},
	url = {http://www.opensym.org/os2015/proceedings-files/p101-muchow.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p101-muchow.pdf},
	author = {Oscar Muchow and David Ustarbowski and Hammouda, Imed}
}
@conference {HG15,
	title = {Matching GitHub developer profiles to job advertisements},
	booktitle = {Proceedings of the 12th International Conference on Mining Software Repositories},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {GitHub is a social coding platform that enables
developers to efficiently work on projects, connect with other
developers, collaborate and generally {\textquotedblleft}be seen{\textquotedblright} by the community.
This visibility also extends to prospective employers and HR
personnel who may use GitHub to learn more about a developer{\textquoteright}s
skills and interests. We propose a pipeline that automatizes this
process and automatically suggests matching job advertisements
to developers, based on signals extracting from their activities on
GitHub.},
	url = {http://www.gousios.gr/pub/dev-profiles.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dev-profiles.pdf},
	author = {Hauff, Claudia and Gousios, Georgios}
}
@proceedings {1725,
	title = {Mining StackOverflow to Filter out Off-topic IRC Discussion},
	year = {2015},
	month = {05/2015},
	pages = {4 pages},
	abstract = {Internet Relay Chat (IRC) is a commonly used tool by OpenSource developers. Developers use IRC channels to discuss programming related problems, but much of the discussion is irrelevant and off-topic. Essentially if we treat IRC discussions like email messages, and apply spam filtering, we can try to filter out the spam (the off-topic discussions) from the ham (the programming discussions). Yet we need labelled data that unfortunately takes time to curate.
To avoid costly curration in order to filter out off-topic discussions, we need positive and negative data-sources. On- line discussion forums, such as StackOverflow, are very effective for solving programming problems. By engaging in open-data, StackOverflow data becomes a powerful source of labelled text regarding programming. This work shows that we can train classifiers using StackOverflow posts as positive examples of on-topic programming discussion. YouTube video comments, notorious for their lack of quality, serve as training set of off- topic discussion. By exploiting these datasets, accurate classifiers can be built, tested and evaluated that require very little effort for end-users to deploy and exploit.},
	keywords = {irc, topics},
	url = {http://webdocs.cs.ualberta.ca/~hindle1/2015/shaiful-mining_so.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shaiful-mining_so.pdf},
	author = {Shaiful Alam Chowdhury and Hindle, Abram}
}
@proceedings {1755,
	title = {Mining StackOverflow to Filter out Off-topic IRC Discussion},
	year = {2015},
	month = {05/2015},
	abstract = {Internet Relay Chat (IRC) is a commonly used
tool by OpenSource developers. Developers use IRC channels
to discuss programming related problems, but much of the
discussion is irrelevant and off-topic. Essentially if we treat IRC
discussions like email messages, and apply spam filtering, we can
try to filter out the spam (the off-topic discussions) from the ham
(the programming discussions). Yet we need labelled data that
unfortunately takes time to curate.
To avoid costly curration in order to filter out off-topic
discussions, we need positive and negative data-sources. Online
discussion forums, such as StackOverflow, are very effective
for solving programming problems. By engaging in open-data,
StackOverflow data becomes a powerful source of labelled text
regarding programming. This work shows that we can train
classifiers using StackOverflow posts as positive examples of
on-topic programming discussion. YouTube video comments,
notorious for their lack of quality, serve as training set of offtopic
discussion. By exploiting these datasets, accurate classifiers
can be built, tested and evaluated that require very little effort
for end-users to deploy and exploit.},
	keywords = {irc, Stack Overflow, youtube},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shaiful-mining_so_0.pdf},
	author = {Shaiful Alam Chowdhury and Hindle, Abram}
}
@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.}
}
@article {1805,
	title = {Stigmergic coordination in FLOSS development teams: Integrating explicit and implicit mechanisms},
	journal = {Cognitive Systems Research},
	year = {2015},
	month = {12/2015},
	abstract = {The vast majority of literature on coordination in team-based projects has drawn on a conceptual separation between explicit (e.g. plans, feedbacks) and implicit coordination mechanisms (e.g. mental maps, shared knowledge). This analytical distinction presents some limitations in explaining how coordination is reached in organizations characterized by distributed teams, scarce face to face meetings and fuzzy and changing lines of authority, as in free/libre open source software (FLOSS) development.

Analyzing empirical illustrations from two FLOSS projects, we highlight the existence of a peculiar model, stigmergic coordination, which includes aspects of both implicit and explicit mechanisms. The work product itself (implicit) and the characteristics under which it is shared (explicit) play an under-appreciated role in helping software developers manage dependencies as they arise. We develop this argument beyond the existing literature by working with an existing coordination framework, considering the role that the codebase itself might play at each step. We also discuss the features and the practices to support stigmergic coordination in distributed teams, as well as recommendations for future research. {\textquotedblleft}Not everything that implicitly exists needs to be rendered explicit{\textquotedblright} (Sloterdijk, 2009, p. 3).},
	keywords = {Coordination mechanisms, distributed teams, FLOSS teams, Stigmergic coordination},
	issn = {13890417},
	doi = {10.1016/j.cogsys.2015.12.003},
	url = {http://www.sciencedirect.com/science/article/pii/S1389041715000339},
	attachments = {https://flosshub.org/sites/flosshub.org/files/COGSYS-RS-\%28HHS\%29-\%282015\%29-\%283\%29.pdf},
	author = {Bolici, Francesco and Howison, James and Kevin Crowston}
}
@proceedings {1767,
	title = {Toward Reusing Code Changes},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Existing techniques have succeeded to help developers
implement new code. However, they are insufficient to help to
change existing code. Previous studies have proposed techniques
to support bug fixes but other kinds of code changes such
as function enhancements and refactorings are not supported
by them. In this paper, we propose a novel system that helps
developers change existing code. Unlike existing techniques, our
system can support any kinds of code changes if similar code
changes occurred in the past. Our research is still on very early
stage and we have not have any implementation or any prototype
yet. This paper introduces our research purpose, an outline of our
system, and how our system is different from existing techniques.},
	keywords = {apache},
	url = {http://sdl.ist.osaka-u.ac.jp/~higo/data/ICSE15-MSR-05-p052.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ICSE15-MSR-05-p052.pdf},
	author = {Higo, Yoshiki and Akio Ohtani and Shinpei Hayashi and Hata, Hideaki and Kusumoto Shinji}
}
@proceedings {1768,
	title = {Will they like this? Evaluating Code Contributions With Language Models},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Popular open-source software projects receive and
review contributions from a diverse array of developers, many
of whom have little to no prior involvement with the project. A
recent survey reported that reviewers consider conformance to
the project{\textquoteright}s code style to be one of the top priorities when evaluating
code contributions on Github. We propose to quantitatively
evaluate the existence and effects of this phenomenon. To this aim
we use language models, which were shown to accurately capture
stylistic aspects of code. We find that rejected changesets do
contain code significantly less similar to the project than accepted
ones; furthermore, the less similar changesets are more likely
to be subject to thorough review. Armed with these results we
further investigate whether new contributors learn to conform to
the project style and find that experience is positively correlated
with conformance to the project{\textquoteright}s code style.},
	url = {http://sback.it/publications/msr2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015_0.pdf},
	author = {Vincent J. Hellendoorn and Premkumar T. Devanbu and Bacchelli, Alberto}
}
@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}
}
@article {9400325220140301,
	title = {COLLABORATION THROUGH OPEN SUPERPOSITION: A THEORY OF THE OPEN SOURCE WAY.},
	journal = {MIS Quarterly},
	volume = {38},
	number = {1},
	year = {2014},
	pages = {29 - A9},
	abstract = {This paper develops and illustrates the theory of collaboration through open superposition: the process of depositing motivationally independent layers of work on top of each other over time. The theory is developed in a study of community-based free and open source software (FLOSS) development, through a research arc of discovery (participant observation), replication (two archival case studies), and theorization. The theory explains two key findings: (1) the overwhelming majority of work is accomplished with only a single programmer working on any one task, and (2) tasks that appear too large for any one individual are more likely to be deferred until they are easier rather than being undertaken through structured team work. Moreover, the theory explains how working through open superposition can lead to the discovery of a work breakdown that results in complex, functionally interdependent, work being accomplished without crippling search costs. We identify a set of socio-technical},
	keywords = {COLLABORATION, COMPUTER programmers, COMPUTER programming, COMPUTER software, coordination, FREEWARE (Computer software), INFORMATION storage \& retrieval systems, open source software, research, socio-technical system},
	issn = {02767783},
	author = {Howison, James and Kevin Crowston}
}
@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}
}
@conference {Romo:2014:FGD:2641580.2641592,
	title = {Filling the Gaps of Development Logs and Bug Issue Data},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {8:1{\textendash}8:4},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {It has been suggested that the data from bug repositories is not always in sync or complete compared to the logs detailing the actions of developers on source code.

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

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

The results indicate that there is a significant amount of information, not in sync when tracing bugs in the two databases. We, therefore, propose an automatic approach to re-align the two databases, so that the collected information is mirrored and in sync.},
	keywords = {Bug traceability, bug-fixing commits},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641592},
	url = {http://doi.acm.org/10.1145/2641580.2641592},
	author = {Romo, Bilyaminu Auwal and Capiluppi, Andrea and Hall, Tracy}
}
@conference {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}
}
@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}
}
@proceedings {1568,
	title = {It{\textquoteright}s Not Only about Writing Code: An Investigation of the Notion of Citizenship Behaviors in the Context of Free/Libre/Open Source Software Communities},
	year = {2014},
	month = {01/2014},
	pages = {3276-3285},
	publisher = {IEEE Computer Society},
	abstract = {Attracting a large number of new contributors has been seen as a way to ensure the survival, long-term success, and sustainability of Free/Libre/Open Source Software (FLOSS) communities. However, this appears to be a necessary, but not a sufficient condition, as the well-being of FLOSS communities also relies on members behaving as {\textquotedblleft}good citizens,{\textquotedblright} to nurture and protect the community. This paper investigates the notion of FLOSS community citizenship behaviors in light of the organizational citizenship behaviors literature. Relying on 11 semi-structured interviews with FLOSS project leaders and community managers, the papers identifies key instances of citizenship behaviors along two dimensions: CCB-I (community citizenship behaviors oriented towards the benefits of other individuals), and CCB-P (community citizenship behaviors oriented towards the benefits of the project and its community).},
	doi = {10.1109/HICSS.2014.406},
	author = {Carillo, Kevin Daniel Andre and Huff, Sid and Chawner, Brenda}
}
@inbook {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}
}
@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}
}
@article {thomas2014studying,
	title = {Studying software evolution using topic models},
	journal = {Science of Computer Programming},
	volume = {80},
	year = {2014},
	pages = {457{\textendash}479},
	publisher = {Elsevier},
	abstract = {Topic models are generative probabilistic models which have been applied to information
retrieval to automatically organize and provide structure to a text corpus. Topic models
discover topics in the corpus, which represent real world concepts by frequently cooccurring
words. Recently, researchers found topics to be effective tools for structuring
various software artifacts, such as source code, requirements documents, and bug reports.
This research also hypothesized that using topics to describe the evolution of software
repositories could be useful for maintenance and understanding tasks. However, research
has yet to determine whether these automatically discovered topic evolutions describe the
evolution of source code in a way that is relevant or meaningful to project stakeholders, and
thus it is not clear whether topic models are a suitable tool for this task.
In this paper, we take a first step towards evaluating topic models in the analysis of
software evolution by performing a detailed manual analysis on the source code histories
of two well-known and well-documented systems, JHotDraw and jEdit. We define and
compute various metrics on the discovered topic evolutions and manually investigate how
and why the metrics evolve over time. We find that the large majority (87\%{\textendash}89\%) of topic
evolutions correspond well with actual code change activities by developers. We are thus
encouraged to use topic models as tools for studying the evolution of a software system.},
	keywords = {Latent Dirichlet allocation, mining software repositories, software evolution, topic model},
	url = {http://sail.cs.queensu.ca/publications/pubs/Thomas-2012-SCP.pdf},
	author = {Stephen W. Thomas and Adams, Bram and Hassan, Ahmed E. and Blostein, Dorothea}
}
@inbook {1626,
	title = {When Are OSS Developers More Likely to Introduce Vulnerable Code Changes? A Case Study},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {234-236},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

We analyzed peer code review data of the Android Open Source Project (AOSP) to understand whether code changes that introduce security vulnerabilities, referred to as vulnerable code changes (VCC), occur at certain intervals. Using a systematic manual analysis process, we identified 60 VCCs. Our results suggest that AOSP developers were more likely to write VCCs prior to AOSP releases, while during the post-release period they wrote fewer VCCs.
},
	keywords = {FOSS, open source, OSS, security, vulnerability},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_37},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_37},
	author = {Bosu, Amiangshu and Carver, JeffreyC. and Hafiz, Munawar and Hilley, Patrick and Janni, Derek},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1593,
	title = {Who Contributes to What? Exploring Hidden Relationships between FLOSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {21-30},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {In this paper we address the challenge of tracking resembling open source projects by exploiting the information of which developers contribute to which projects. To do this, we have performed a social network study to analyze data collected from the Ohloh repository. Our findings suggest that the more shared contributors two projects have, the more likely they resemble with respect to properties such as project application domain, programming language used and project size.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_3},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_3},
	author = {Syeed, M.M.Mahbubul and Hammouda, Imed},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {hannemann2013adaptive,
	title = {An Adaptive Filter-Framework for the Quality Improvement of Open-Source Software Analysis.},
	booktitle = {Software Engineering},
	year = {2013},
	pages = {143{\textendash}156},
	publisher = {Citeseer},
	organization = {Citeseer},
	abstract = {Knowledge mining in Open-Source Software (OSS) brings a great benefit
for software engineering (SE). The researchers discover, investigate, and even simulate
the organization of development processes within open-source communities in
order to understand the community-oriented organization and to transform its advantages
into conventional SE projects. Despite a great number of different studies on
OSS data, not much attention has been paid to the data filtering step so far. The noise
within uncleaned data can lead to inaccurate conclusions for SE. A special challenge
for data cleaning presents the variety of communicational and development infrastructures
used by OSS projects. This paper presents an adaptive filter-framework supporting
data cleaning and other preprocessing steps. The framework allows to combine
filters in arbitrary order, defining which preprocessing steps should be performed. The
filter-portfolio can by extended easily. A schema matching in case of cross-project
analysis is available. Three filters - spam detection, quotation elimination and core periphery
distinction - were implemented within the filter-framework. In the analysis
of three large-scale OSS projects (BioJava, Biopython, BioPerl), the filtering led to
a significant data modification and reduction. The results of text mining (sentiment
analysis) and social network analysis on uncleaned and cleaned data differ significantly, confirming the importance of the data preprocessing step within OSS empirical
studies.},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.437.5602\&rep=rep1\&type=pdf$\#$page=143},
	author = {Hannemann, Anna and Hackstein, Michael and Klamma, Ralf and Jarke, Matthias}
}
@proceedings {1552,
	title = {Analyzing Social Behavior of Software Developers Across Different Communication Channels},
	year = {2013},
	abstract = {Software developers use different project repositories (i.e., mailing list, bug tracking repositories, discussion forums etc.) to interact with each other or to solve software related problems. The growing interest in the usage of social media channels (i.e., Twitter, Facebook, LinkedIn) have also attracted the open source software community and software developers to adopt an identity in order to disseminate project-related information to a wider audience. Much research has been carried out to analyze the social behavior of software developers in different project repositories but so far no one has tried to study the social communication patterns of developers in other social media channels. We in this paper presents a new dimension to the social aspects of software developers and study if the social communication patterns of software developers is different on project repositories and social media channels (i.e., Twitter).},
	keywords = {communication, developer, social media},
	url = {http://index.ksi.edu/conf/seke/2013/cr/296.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/iqbal_a_et_al_june_2013.pdf},
	author = {Iqbal, Aftab and M Karnstedt and M Hausenblas}
}
@book {1536,
	title = {Community Dynamics in Open Source Software Projects: Aging and Social Reshaping},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {80 - 96},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

An undeniable factor for an open source software (OSS) project success is a vital community built around it. An OSS community not only needs to be established, but also to be persisted. This is not guaranteed considering the voluntary nature of participation in OSS. The dynamic analysis of the OSS community evolution can be used to extract indicators to rate the current stability of a community and to predict its future development. Despite the great amount of studies on mining project communication and development repositories, the evolution of OSS communities is rarely addressed. This paper presents an approach to analyze the OSS community history. We combine adapted demography measures to study community aging and social analysis to investigate the dynamics of community structures. The approach is applied to the communication and development history of three bioinformatics OSS communities over eleven years. First, in all three projects a survival rate pattern is identified. This finding allows us to define the minimal number of newcomers required for the further positive community growth. Second, dynamic social analysis shows that the node betweenness in combination with the network diameter can be used as an indicator for significant changes in the community core and the quality of community recovery after these modifications.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_6},
	author = {Hannemann, Anna and Klamma, Ralf},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1502,
	title = {A Dataset from Change History to Support Evaluation  of Software Maintenance Tasks},
	year = {2013},
	month = {05/2013},
	pages = {131-134},
	abstract = {Approaches that support software maintenance need 
to be evaluated and compared against existing ones, in order to 
demonstrate their usefulness in practice. However, oftentimes the 
lack of well-established sets of benchmarks leads to situations 
where these approaches are evaluated using different datasets, 
which results in biased comparisons. In this data paper we 
describe and make publicly available a set of benchmarks from 
six Java applications, which can be used in the evaluation of 
various software engineering (SE) tasks, such as feature location 
and impact analysis. These datasets consist of textual description 
of change requests, the locations in the source code where they 
were implemented, and execution traces. Four of the benchmarks 
were already used in several SE research papers, and two of them 
are new. In addition, we describe in detail the methodology used 
for generating these benchmarks and provide a suite of tools in 
order to encourage other researchers to validate our datasets and 
generate new benchmarks for other subject software systems. 
Our online appendix: http://www.cs.wm.edu/semeru/data/msr13/ },
	url = {http://www.cs.wm.edu/~bdit/publications/MSR13DataPaper_Dit_CRC.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MSR13DataPaper_Dit_CRC.pdf},
	author = {Bogdan Dit and Andrew Holtzhauer and Poshyvanyk, Denys and Kagdi, Huzefa}
}
@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}
}
@article {syeed2013evolution,
	title = {Evolution of Open Source Software Projects: A Systematic Literature Review},
	journal = {Journal of Software},
	volume = {8},
	number = {11},
	year = {2013},
	pages = {2815{\textendash}2829},
	abstract = {Open Source Software (OSS) is continuously gaining acceptance in commercial organizations. It is in this regard that those organizations strive for a better understanding of evolutionary aspects of OSS projects. The study of evolutionary patterns of OSS projects and communities has received substantial attention from the research community over the last decade. These efforts have resulted in an ample set of research results for which there is a need for up-to-date comprehensive overviews and literature surveys.

This paper reports on a systematic literature survey aimed at the identification and structuring of research on evolution of OSS projects. In this review we systematically selected and reviewed 101 articles published in relevant venues. The study outcome provides insight in what constitutes the main contributions of the field, identifies gaps and opportunities, and distills several important future research directions.},
	keywords = {flosshub},
	attachments = {https://flosshub.org/sites/flosshub.org/files/9913-25310-1-PB.pdf},
	author = {Syeed, Mahbubul and Hammouda, Imed and Syat{\"a}, Tarja}
}
@article {1631,
	title = {The evolution of the laws of software evolution},
	journal = {ACM Computing Surveys},
	volume = {46},
	year = {2013},
	month = {11/2013},
	pages = {1 - 28},
	abstract = { After more than 40 years of life, software evolution should be considered as a mature field. However, despite such a long history, many research questions still remain open, and controversial studies about the validity of the laws of software evolution are common. During the first part of these 40 years the laws themselves evolved to adapt to changes in both the research and the software industry environments. This process of adaption to new paradigms, standards, and practices stopped about 15 years ago, when the laws were revised for the last time. However, most controversial studies have been raised during this latter period. Based on a systematic and comprehensive literature review, in this paper we describe how and when the laws, and the software evolution field, evolved. We also address the current state of affairs about the validity of the laws, how they are perceived by the research community, and the developments and challenges that are likely to occur in the coming years.},
	issn = {03600300},
	doi = {10.1145/2543581.2543595},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2013HerraizRRG_CSUR.pdf},
	author = {Herraiz, Israel and Rodriguez, Daniel and Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@conference {zmzkh-icsm-2013,
	title = {How does Context affect the Distribution of Software Maintainability Metrics?},
	booktitle = {Proceedings of the 29th IEEE International Conference on Software Maintainability},
	series = {ICSM {\textquoteright}13},
	year = {2013},
	note = {"FLOSSMole [25] is another data source, from
where we download descriptions (i.e., application domain)
of SourceForge software systems. Furthermore, we download
latest application domain information4
and monthly download
data5 of studied software systems directly from SourceForge."},
	abstract = {Software metrics have many uses, e.g., defect prediction, effort estimation, and benchmarking an organization against peers and industry standards. In all these cases, metrics may depend on the context, such as the programming language. Here we aim to investigate if the distributions of commonly used metrics do, in fact, vary with six context factors: application domain, programming language, age, lifespan, the number of changes, and the number of downloads. For this preliminary study we select 320 nontrivial software systems from SourceForge. These software systems are randomly sampled from nine popular application domains of SourceForge. We calculate 39 metrics commonly used to assess software maintainability for each software system and use Kruskal Wallis test and Mann-Whitney U test to determine if there are significant differences among the distributions with respect to each of the six context factors. We use Cliff{\textquoteright}s delta to measure the magnitude of the differences and find that all six context factors affect the distribution of 20 metrics and the programming language factor affects 35 metrics. We also briefly discuss how each context factor may affect the distribution of metric values.We expect our results to help software benchmarking and other software engineering methods that rely on these commonly used metrics to be tailored to a particular context.},
	keywords = {benchmark, context, contextual factor, flossmole, large scale, metrics, mining software repositories, sampling, software maintainability, sourceforge, static metrics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icsm2013_contextstudy.pdf},
	author = {Zhang, Feng and Audris Mockus and Ying Zou and Foutse Khomh and Hassan, Ahmed E.}
}
@proceedings {1501,
	title = {The Impact of Tangled Code Changes},
	year = {2013},
	month = {05/2013},
	abstract = {When interacting with version control systems, developers often commit unrelated or loosely related code changes
in a single transaction. When analyzing the version history, such
tangled changes will make all changes to all modules appear
related, possibly compromising the resulting analyses through
noise and bias. In an investigation of five open-source JAVA
projects, we found up to 15\% of all bug fixes to consist of multiple
tangled changes. Using a multi-predictor approach to untangle
changes, we show that on average at least 16.6\% of all source
files are incorrectly associated with bug reports. We recommend
better change organization to limit the impact of tangled changes.},
	keywords = {bias, data quality, history, java, mining software repositories, noise, tangled code changes, version control},
	url = {http://www.kim-herzig.de/wp-content/uploads/2013/03/msr2013-untangling.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2013-untangling.pdf},
	author = {Kim Herzig and Zeller, Andreas}
}
@proceedings {1506,
	title = {Intensive Metrics for the Study of the Evolution of Open Source Projects: Case Studies from Apache Software Foundation Projects},
	year = {2013},
	month = {05/2013},
	abstract = {Based on the empirical evidence that the ratio of email messages in public mailing lists to versioning system commits has remained relatively constant along the history of the Apache Software Foundation (ASF), this paper has as goal to study what can be inferred from such a metric for projects of the ASF. We have found that the metric seems to be an intensive metric as it is independent of the size of the project, its activity, or the number of developers, and remains relatively independent of the technology or functional area of the project. Our analysis provides evidence that the metric is related to the technical effervescence and popularity of project, and as such can be a good candidate to measure its healthy evolution. Other, similar metrics -like the ratio of developer messages to commits and the ratio of issue tracker messages to commits- are studied for several projects as well, in order to see if they have similar characteristics.},
	url = {http://oa.upm.es/14698/1/paper.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper_1.pdf},
	author = {Gala, Santiago and Gregorio Robles and Jesus M. Gonzalez-Barahona and Herraiz Tabernero, Israel}
}
@article {1553,
	title = {Interlinking Developer Identities within and across Open Source Projects: The Linked Data Approach},
	journal = {ISRN Software Engineering},
	volume = {201330692164},
	year = {2013},
	month = {2013},
	pages = {1 - 12},
	abstract = {Software developers use various software repositories in order to interact with each other or to solve related problems. These repositories provide a rich source of information for a wide range of tasks. However, one issue to overcome in order to make this information useful is the identification and interlinking of multiple identities of developers. In this paper, we propose a Linked Data-based methodology to interlink and integrate multiple identities of a developer found in different software repositories of a project as well as across repositories of multiple projects. Providing such interlinking will enable us to keep track of a developer{\textquoteright}s activity not only within a single project but also across multiple projects. The methodology will be presented in general and applied to 5 Apache projects as a case study. Further, we show that the few methods suggested so far are not always appropriate to overcome the developer identification problem.},
	keywords = {developer, identity, linked data},
	doi = {10.1155/2013/58473110.1007/s10664-009-9110-310.1109/TSE.2005.7010.1007/978-0-387-72486-7_4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/584731.pdf},
	author = {Iqbal, Aftab and Hausenblas, Michael}
}
@proceedings {1521,
	title = {It{\textquoteright}s Not a Bug, It{\textquoteright}s a Feature: How Misclassification Impacts Bug Prediction},
	year = {2013},
	month = {05/2013},
	pages = {392-401},
	abstract = {In a manual examination of more than 7,000 issue reports from the bug databases of five open-source projects, we found 33.8\% of all bug reports to be misclassified{\textemdash}that is, rather than referring to a code fix, they resulted in a new feature, an update to documentation, or an internal refactoring. This misclassification introduces bias in bug prediction models, confusing bugs and features: On average, 39\% of files marked as defective actually never had a bug. We discuss the impact of this misclassification on earlier studies and recommend manual data validation for future studies.},
	keywords = {bias, bug reports, data quality, mining software repositories, noise},
	author = {Kim Herzig and Sascha Just and Zeller, Andreas}
}
@proceedings {1500,
	title = {Linux Variability Anomalies: What Causes Them and How Do They Get Fixed?},
	year = {2013},
	month = {05/2013},
	abstract = {The Linux kernel is one of the largest configurable open source software systems implementing static variability. In Linux, variability is scattered over three different artifacts: source code files, Kconfig files, and Makefiles. Previous work detected inconsistencies between these artifacts that led to anomalies in the intended variability of Linux. We call these variability anomalies. However, there has been no work done to analyze how these variability anomalies are introduced in the first place, and how they get fixed. In this work, we provide an analysis of the causes and fixes of variability anomalies in Linux. We first perform an exploratory case study that uses an existing set of patches which solve variability anomalies to identify patterns for their causes. The observations we make from this dataset allow us to develop four research questions which we then answer in a confirmatory case study on the scope of the whole Linux kernel. We show that variability anomalies exist for several releases in the kernel before they get fixed, and that contrary to our initial suspicion, typos in feature names do not commonly cause these anomalies. Our results show that variability anomalies are often introduced through incomplete patches that change Kconfig definitions without properly propagating these changes to the rest of the system. Anomalies are then commonly fixed through changes to the code rather than to Kconfig files.},
	author = {Sarah Nadi and Christian Dietrich and Reinhard Tartler and Holt, Richard C. and Daniel Lohmann}
}
@article {bettenburg2013management,
	title = {Management of community contributions},
	journal = {Empirical Software Engineering},
	year = {2013},
	pages = {1{\textendash}38},
	publisher = {Springer},
	abstract = {In recent years, many companies have realized that collaboration with a thriving user or developer community is a major factor in creating innovative technology driven by market demand. As a result, businesses have sought ways to stimulate contributions from developers outside their corporate walls, and integrate external developers into their development process. To support software companies in this process, this paper presents an empirical study on the contribution management processes of two major, successful, open source software ecosystems. We contrast a for-profit (ANDROID) system having a hybrid contribution style, with a not-for-profit (LINUX kernel) system having an open contribution style. To guide our comparisons, we base our analysis on a conceptual model of contribution management that we derived from a total of seven major open-source software systems. A quantitative comparison based on data mined from the ANDROID code review system and the LINUX kernel code review mailing lists shows that both projects have significantly different contribution management styles, suited to their respective market goals, but with individual advantages and disadvantages that are important for practitioners. Contribution management is a real-world problem that has received very little attention from the research community so far. Both studied systems (LINUX and ANDROID) employ different strategies and techniques for managing contributions, and both approaches are valuable examples for practitioners. Each approach has specific advantages and disadvantages that need to be carefully evaluated by practitioners when adopting a contribution management process in practice.},
	keywords = {android, contribution, linux, management},
	url = {http://link.springer.com/article/10.1007/s10664-013-9284-6},
	author = {Bettenburg, Nicolas and Hassan, Ahmed E. and Adams, Bram and Daniel M. German}
}
@book {1538,
	title = {Socio-technical Congruence in OSS Projects: Exploring Conway{\textquoteright}s Law in FreeBSD},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {109 - 126},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Software development requires effective communication, coordination and collaboration among developers working on interdependent modules of the same project. The need for coordination is even more evident in open source projects where development is often more dispersed and distributed. In this paper, we study the match between the coordination needs established by the technical domain (i.e. source code) and the actual coordination activities carried out by the development team, such hypothetical match is also known as socio-technical congruence. We carry out our study by empirically examining Conway{\textquoteright}s law in FreeBSD project. Our study shows that the congruence measure is significantly high in FreeBSD and that the congruence value remains stable as the project matured.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_8},
	author = {Syeed, M.M. Mahbubul and Hammouda, Imed},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@article {gonzalez2013studying,
	title = {Studying the laws of software evolution in a long-lived FLOSS project},
	journal = {Journal of Software: Evolution and Process},
	year = {2013},
	publisher = {Wiley Online Library},
	abstract = {Some free, open-source software projects have been around for quite a long time, the longest living ones dating from the early 1980s. For some of them, detailed information about their evolution is available in source code management systems tracking all their code changes for periods of more than 15 years. This paper examines in detail the evolution of one of such projects, glibc, with the main aim of understanding how it evolved and how it matched Lehman{\textquoteright}s laws of software evolution. As a result, we have developed a methodology for studying the evolution of such long-lived projects based on the information in their source code management repository, described in detail several aspects of the history of glibc, including some activity and size metrics, and found how some of the laws of software evolution may not hold in this case.},
	url = {http://oa.upm.es/21355/1/smr1615.pdf},
	author = {Jesus M. Gonzalez-Barahona and Gregorio Robles and Herraiz, Israel and Ortega, Felipe}
}
@proceedings {1515,
	title = {Using Citation Influence to Predict Software Defects},
	year = {2013},
	month = {05/2013},
	abstract = {The software dependency network reflects structure and the developer contribution network reflects process. Previous studies have used social network properties over these networks to predict whether a software component is defect-prone. However, these studies do not consider the strengths of the dependencies in the networks. In our approach, we use a citation influence topic model to determine dependency strengths among components and developers, analyze weak and strong dependencies separately, and apply social network properties to predict defect-prone components. In experiments on Eclipse and NetBeans, our approach has higher accuracy than prior work.},
	keywords = {eclipse, netbeans, social network},
	author = {Wei Hu and Kenny Wong}
}
@proceedings {1498,
	title = {Who Does What during a Code Review? Datasets of OSS Peer Review Repositories },
	year = {2013},
	month = {05/2013},
	abstract = {We present four datasets that are focused on the general roles of OSS peer review members. With data mined from both an integrated peer review system and code source repositories, our rich datasets comprise of peer review data that was automatically recorded. Using the Android project as a case study, we describe our extraction methodology, the datasets and their application used for three separate studies. Our datasets are available online at http://sdlab.naist.jp/reviewmining/},
	keywords = {android, case study, code review, data set, peer review, roles, source code},
	author = {Kazuki Hamasaki and Raula Gaikovina Kula and Norihiro Yoshida and A. E. Camargo Cruz and Kenji Fujiwara and Hajimu Iida}
}
@article {1395,
	title = {Automated topic naming: supporting cross-project analysis of software maintenance activities},
	journal = {Empirical Software Engineering},
	year = {2012},
	abstract = {Software repositories provide a deluge of software artifacts to analyze. Researchers have attempted to summarize, categorize, and relate these artifacts by using semi-unsupervised machine-learning algorithms, such as Latent Dirichlet Allocation (LDA). LDA is used for concept and topic analysis to suggest candidate word-lists or topics that describe and relate software artifacts. However, these word-lists and topics are difficult to interpret in the absence of meaningful summary labels. Current attempts to interpret topics assume manual labelling and do not use domain-specific knowledge to improve, contextualize, or describe results for the developers. We propose a solution: automated labelled topic extraction. Topics are extracted using LDA from commit-log comments recovered from source control systems. These topics are given labels from a generalizable cross-project taxonomy, consisting of non-functional requirements. Our approach was evaluated with experiments and case studies on three large-scale Relational Database Management System (RDBMS) projects: MySQL, PostgreSQL and MaxDB. The case studies show that labelled topic extraction can produce appropriate, context-sensitive labels that are relevant to these projects, and provide fresh insight into their evolving software development activities. },
	keywords = {LDA, maxdb, mysql, postgresql, topics},
	issn = {1573-7616},
	doi = {10.1007/s10664-012-9209-9},
	author = {Hindle, Abram and Ernst, Neil A. and Godfrey, Michael W. and Mylopoulos, John}
}
@article {1679,
	title = {Carrots and Rainbows: Motivation and Social Practice in Open Source Software Development},
	journal = {Management Information Systems Quarterly},
	volume = {36},
	year = {2012},
	pages = {649-676},
	abstract = {Open source software (OSS) is a social and economic phenomenon that raises fundamental questions about the motivations of contributors to information systems development. Some developers are unpaid volunteers who seek to solve their own technical problems, while others create OSS as part of their employment contract. For the past 10 years, a substantial amount of academic work has theorized about and empirically examined developer motivations. We review this work and suggest considering motivation in terms of the values of the social practice in which developers participate. Based on the social philosophy of Alasdair MacIntyre, we construct a theoretical framework that expands our assumptions about individual motivation to include the idea of a long-term, value-informed quest beyond short-term rewards. This motivation{\textendash}practice framework depicts how the social practice and its supporting institutions mediate between individual motivation and outcome. The framework contains three theoretical conjectures that seek to explain how collectively elaborated standards of excellence prompt developers to produce high-quality software, change institutions, and sustain OSS development. From the framework, we derive six concrete propositions and suggest a new research agenda on motivation in OSS.
},
	url = {https://sspaeth.de/uploads/CarrotsAndRainbows.pdf},
	author = {Georg von Krogh and Stefan Haefliger and Sebastian Spaeth and Martin W. Wallin}
}
@proceedings {1443,
	title = {Citizen Engineering: Evolving OSS Practices to Engineering Design and Analysis},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {61-77},
	publisher = {IFIP AICT},
	abstract = {Open Source Software (OSS) development has much in common with concepts such as crowdsourcing, citizen science, collective intelligence, human-based computation, and what we call {\textquotedblleft}Citizen Engineering (CE){\textquotedblright}. We report on several pilot projects that apply these shared principles of OSS development to engineering activities beyond software engineering. CE models harness human computing power from open communities, which commonly consist of a cohort of geographically and/or institutionally scattered citizens - professionals or amateurs - to collaboratively solve real-world problems. In most cases, the problems targeted are challenging to computers, but manageable or trivial to human intelligence. In these systems, while humans play fundamental roles, whether they are project architects or problem solvers, the implementation of CE is greatly facilitated by the advance of information technology, particularly the Internet, considered as "creative mode of user interactivity, not merely a medium between messages and people" [10]. In this paper, we characterize existing citizen engineering practices into 6 major categories, followed by a discussion of 4 ongoing projects, aiming to provide new perspectives and insights for achieving successful CE project designs.},
	author = {Zhai, Zhi and Kijewski-Correa, Tracy and Kareem, Ashan and Hachen, David and Madey, Gregory}
}
@conference {1316,
	title = {An Empirical Study of Volunteer Members{\textquoteright} Perceived Turnover in Open Source Software Projects},
	booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences},
	year = {2012},
	note = {"After designing the questionnaire, we conducted a web-based survey by inviting developers working in sourceforge.net and launchpad.net."},
	month = {01/2012},
	pages = {3396-3405},
	abstract = {Turnover of volunteer members and the ensuing instability bring about severe problems to open source software (OSS) projects. To better understand it, we based our study on Herzberg ́s two-factor theory to investigate the influence of hygiene factors on volunteer members ́ dissatisfaction and perceived turnover. After empirically testing the research model, we found shortcomings in project regulation and administration are the key reason for volunteer members ́ dissatisfaction, followed by future rewards and personal needs for software functionalities. By contrast, a possible lack of supportive working relationship among OSS developers was not found to be a trigger for developer dissatisfaction. Dissatisfaction was confirmed to be a significant predictor of perceived turnover. The results demonstrates generalized hygiene factors cannot unreflectively be transferred into the OSS context because volunteer members ́ personal expectation has a weaker influence on perceived turnover than objective attributes of OSS project. Our study further makes suggestions for project administrators.},
	keywords = {developers, launchpad, sourceforge, Survey},
	author = {Yu, Yiqing and Benlian, Alexander and Hess, Thomas}
}
@article {1399,
	title = {The evolution of Java build systems},
	journal = {Empirical Software Engineering},
	volume = {17},
	year = {2012},
	month = {8/2012},
	pages = {578 - 608},
	abstract = {Build systems are responsible for transforming static source code artifacts into executable software. While build systems play such a crucial role in software development and maintenance, they have been largely ignored by software evolution researchers. However, a firm understanding of build system aging processes is needed in order to allow project managers to allocate personnel and resources to build system maintenance tasks effectively, and reduce the build maintenance overhead on regular development activities. In this paper, we study the evolution of build systems based on two popular Java build languages (i.e., ANT and Maven) from two perspectives: (1) a static perspective, where we examine the complexity of build system specifications using software metrics adopted from the source code domain; and (2) a dynamic perspective, where the complexity and coverage of representative build runs are measured. Case studies of the build systems of six open source build projects with a combined history of 172 releases show that build system and source code size are highly correlated, with source code restructurings often requiring build system restructurings. Furthermore, we find that Java build systems evolve dynamically in terms of duration and recursive depth of the directory hierarchy. },
	keywords = {ant, build, maven, scm, source code analysis},
	issn = {1573-7616},
	doi = {10.1007/s10664-011-9169-5},
	author = {McIntosh, Shane and Adams, Bram and Hassan, Ahmed E.}
}
@proceedings {1377,
	title = {Examining Turnover in Open Source Software Projects Using a Logistic Hierarchical Linear Modeling Approach},
	volume = {378},
	year = {2012},
	month = {09/2012},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Developer turnover in open source software projects is a critical and insufficiently researched problem. Previous research has focused on understanding the developer motivations to contribute using either the individual developer perspective or the project perspective. In this exploratory study we argue that because the developers are embedded in projects it is imperative to include both perspectives. We analyze turnover in open source software projects by including both individual developer level factors, as well as project specific factors. Using the Logistic Hierarchical Linear Modeling approach allows us to empirically examine the factors influencing developer turnover and also how these factors differ among developers and projects.},
	keywords = {Logistic Hierarchical Linear Modeling, sourceforge, turnover},
	author = {Sharma, P.N. and Hulland, J. and Daniel, S.}
}
@article {flosswp403,
	title = {Free/Libre Open Source Software: What We Know and What We Do Not Know},
	journal = {ACM Computing Surveys},
	volume = {44},
	year = {2012},
	publisher = {ACM},
	edition = {2},
	abstract = {We review the empirical research on Free/Libre Open Source Software (FLOSS) development and assess the state of the literature. Our review is organized around an input-mediator-output-input (IMOI) model. We start with a description of the articles selected for the review. We then discuss findings of this literature categorized into issues pertaining to inputs (e.g., member characteristics, technology use and project characteristics), processes (software development and social processes), emergent states (e.g., trust and task related states) and outputs (e.g. team performance, FLOSS implementation and project evolution). Based on this review, we suggest research questions, including methodological and theoretical issues, to guide future inquiry in this area.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/floss_review_paper.pdf},
	author = {Kevin Crowston and Kangning Wei and Howison, James and Andrea Wiggins}
}
@conference {1640,
	title = {Integrating developer-related information across open source repositories},
	booktitle = {2012 IEEE 13th International Conference on Information Reuse \& Integration (IRI)2012 IEEE 13th International Conference on Information Reuse \& Integration (IRI)},
	year = {2012},
	pages = {69 - 76},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Las Vegas, NV, USA},
	abstract = {Software developers use various software repositories in order to interact with each other or to solve software related problems. They are required to adopt an identity for each of the software repositories they wanted to use. Quite often developers are also found on different code forges developing open source projects. It is worth mentioning that the information relevant to the developers are distributed on the Web among different data sources each requires an ID and an authentication mechanism. In this paper, we propose to interlink the identities of a developer across different data sources on the Web. Further, we show the benefit of integrating developer-related information from different data sources using some real-world scenarios.},
	isbn = {978-1-4673-2283-6},
	doi = {10.1109/IRI.2012.6302993},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Iqbal_A_et_al_Aug_2012.pdf},
	author = {Iqbal, Aftab and Hausenblas, Michael}
}
@article {1589,
	title = {Integrating FLOSS repositories on the Web},
	year = {2012},
	note = {"To provide the researchers easy access to the project{\textquoteright}s data, two research projects were initiated (with slightly different objective)
by the FLOSS research community which are FLOSSmole and FLOSSMetrics , also known as {\textquotedblleft}repository of repositories (RoR){\textquotedblright}. These RoRs were created to consolidate metadata and analysis of projects from a variety of code forges into a centralized place for use by the researchers in academia and industry.

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

Names are not available for the developers in the database dump of
Googlecode provided by FLOSSmole, so we consider matching only developer ID(s) in the case of
Googlecode."},
	month = {2012},
	abstract = {This paper provides a novel approach to the problem of integrating data from multiple code forges of FLOSS. We review the current problems in integrating the data from multiple forges and argue that Semantic Web technologies are suitable for representing knowledge contained in code forges. Further, we show the advantage of linking the metadata of projects to other data sources on the Web which will enable querying extra information from the Web. The paper briefly describes how the modeling is achieved and what benefits can be obtained by enabling linking to other relevant data sources already available on the Web.},
	keywords = {flossmole, google code, sourceforge},
	url = {https://www.researchgate.net/publication/259757473_Integrating_FLOSS_repositories_on_the_Web},
	attachments = {https://flosshub.org/sites/flosshub.org/files/DERI-TR-AFTAB-2012-12-10_0.pdf},
	author = {Iqbal, Aftab and Cyganiak, Richard and Hausenblas, Michael}
}
@conference {1813,
	title = {Modification and developer metrics at the function level: Metrics for the study of the evolution of a software project},
	booktitle = {2012 3rd International Workshop on Emerging Trends in Software Metrics (WETSoM)},
	year = {2012},
	pages = {49 - 55},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Zurich, Switzerland},
	abstract = {Software evolution, and particularly its growth, has been mainly studied at the file (also sometimes referred as module) level. In this paper we propose to move from the physical towards a level that includes semantic information by using functions or methods for measuring the evolution of a software system. We point out that use of functions-based metrics has many advantages over the use of files or lines of code. We demonstrate our approach with an empirical study of two Free/Open Source projects: a community-driven project, Apache, and a company-led project, Novell Evolution. We discovered that most functions never change; when they do their number of modifications is correlated with their size, and that very few authors who modify each; finally we show that the departure of a developer from a software project slows the evolution of the functions that she authored.
},
	isbn = {978-1-4673-1763-4},
	doi = {10.1109/WETSoM.2012.6226993},
	author = {Gregorio Robles and Herraiz, Israel and Daniel M. German and Izquierdo-Cortazar, Daniel}
}
@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 {1447,
	title = {OSS Integration Issues and Community Support: An Integrator Perspective},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {129-143},
	publisher = {IFIP AICT},
	abstract = {The reuse and integration of Open Source Software (OSS) components provided by OSS communities is becoming an economical and strategic need for today{\textquoteright}s organizations. The integration of OSS components provides many benefits, but also risks and challenges. One of the most important risks is the lack of effective and timely OSS community support for dealing with possible integration problems. For gaining an understanding of the common problems that organizations face when integrating OSS components, and the role played by OSS communities, we performed an exploratory study on 25 OSS integration projects from different European organizations. The results show that the main way of reducing integration problems was the use of OSS components from well-established communities; therefore very few integration problems were identified. In most of the cases these problems were successfully solved with the support from the OSS community and/or colleagues. In addition, contrary to the common belief that understanding code from someone else is a hard and undesirable task, some integrators consider OSS code even more understandable than their own code.},
	author = {Ayala, Claudia and Cruzes, Daniela S. and Nguyen, Anh Duc and Conradi, Reidar and Franch, Xavier and Höst, Martin and Ali Babar, Muhammad}
}
@proceedings {1471,
	title = {OSSLI: Architecture Level Management of Open Source Software Legality Concerns},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {356-361},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {This paper presents a tool that addresses the legality concerns of open source at the level of software architecture, early in the development activity. The tool demonstrates the significance of licensing concerns at the architectural level by extending existing modeling tools with support for open source licensing issues.},
	author = {Lokhman, Alexander and Luoto, Antti and Abdul-Rahman, Salum and Hammouda, Imed}
}
@conference {1523,
	title = {Social coding in GitHub},
	booktitle = {Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work - CSCW {\textquoteright}12},
	year = {2012},
	pages = {1277},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Seattle, Washington, USA},
	abstract = {
Social applications on the web let users track and follow the activities of a large number of others regardless of location or affiliation. There is a potential for this transparency to radically improve collaboration and learning in complex knowledge-based activities. Based on a series of in-depth interviews with central and peripheral GitHub users, we examined the value of transparency for large-scale distributed collaborations and communities of practice. We find that people make a surprisingly rich set of social inferences from the networked activity information in GitHub, such as inferring someone else{\textquoteright}s technical goals and vision when they edit code, or guessing which of several similar projects has the best chance of thriving in the long term. Users combine these inferences into effective strategies for coordinating work, advancing technical skills and managing their reputation.
},
	keywords = {github},
	isbn = {9781450310864},
	doi = {10.1145/2145204.2145396},
	url = {http://www.cs.cmu.edu/afs/cs/Web/People/xia/resources/Documents/cscw2012_Github-paper-FinalVersion-1.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cscw2012_Github-paper-FinalVersion-1.pdf},
	author = {Laura Dabbish and Colleen Stuart and Jason Tsay and Herbsleb, Jim}
}
@article {springerlink:10.1007/s10664-012-9199-7,
	title = {Software Bertillonage},
	journal = {Empirical Software Engineering},
	year = {2012},
	note = {10.1007/s10664-012-9199-7},
	pages = {1-43},
	publisher = {Springer Netherlands},
	abstract = {Deployed software systems are typically composed of many pieces, not all of which may have been created by the main development team. Often, the provenance of included components{\textemdash}such as external libraries or cloned source code{\textemdash}is not clearly stated, and this uncertainty can introduce technical and ethical concerns that make it difficult for system owners and other stakeholders to manage their software assets. In this work, we motivate the need for the recovery of the provenance of software entities by a broad set of techniques that could include signature matching, source code fact extraction, software clone detection, call flow graph matching, string matching, historical analyses, and other techniques. We liken our provenance goals to that of Bertillonage, a simple and approximate forensic analysis technique based on bio-metrics that was developed in 19th century France before the advent of fingerprints. As an example, we have developed a fast, simple, and approximate technique called anchored signature matching for identifying the source origin of binary libraries within a given Java application. This technique involves a type of structured signature matching performed against a database of candidates drawn from the Maven2 repository, a 275 GB collection of open source Java libraries. To show the approach is both valid and effective, we conducted an empirical study on 945 jars from the Debian GNU/Linux distribution, as well as an industrial case study on 81 jars from an e-commerce application. },
	issn = {1382-3256},
	doi = {10.1007/s10664-012-9199-7},
	url = {http://dx.doi.org/10.1007/s10664-012-9199-7},
	author = {Davies, Julius and German, Daniel and Michael Godfrey and Hindle, Abram}
}
@article {1396,
	title = {Studying the impact of social interactions on software quality},
	journal = {Empirical Software Engineering},
	year = {2012},
	note = {bug databases},
	abstract = {Correcting software defects accounts for a significant amount of resources in a software project. To make best use of testing efforts, researchers have studied statistical models to predict in which parts of a software system future defects are likely to occur. By studying the mathematical relations between predictor variables used in these models, researchers can form an increased understanding of the important connections between development activities and software quality. Predictor variables used in past top-performing models are largely based on source code-oriented metrics, such as lines of code or number of changes. However, source code is the end product of numerous interlaced and collaborative activities carried out by developers. Traces of such activities can be found in the various repositories used to manage development efforts. In this paper, we develop statistical models to study the impact of social interactions in a software project on software quality. These models use predictor variables based on social information mined from the issue tracking and version control repositories of two large open-source software projects. The results of our case studies demonstrate the impact of metrics from four different dimensions of social interaction on post-release defects. Our findings show that statistical models based on social information have a similar degree of explanatory power as traditional models. Furthermore, our results demonstrate that social information does not substitute, but rather augments traditional source code-based metrics used in defect prediction models.},
	keywords = {bug tracker, eclipse, Firefox, Human Factors, measurement, metrics, software evolution, Software quality assurance},
	issn = {1573-7616},
	doi = {10.1007/s10664-012-9205-0},
	author = {Bettenburg, Nicolas and Hassan, Ahmed E.}
}
@proceedings {1473,
	title = {Two Modes of Product Development: Head-Oriented vs. Release-Oriented},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {368-370},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {In this paper, the concept of two different modes for product development process is proposed. One is {\textquotedblleft}release-oriented{\textquotedblright} product development, which is a fairly common way to develop various products up to now. The other is {\textquotedblleft}head-oriented{\textquotedblright} product development, which is recently observed especially in the field of software/content development. The distinguishing difference and possible merits and demerits of two modes are scrutinized.},
	author = {Hatta, Masayuki}
}
@conference {bettenburg:csmr2012,
	title = {Using Code Search to Link Code Fragments in Discussions and Source Code},
	booktitle = {CSMR {\textquoteright}12: Proceedings of the 16th European Conference on Software Maintenance and Reengineering},
	year = {2012},
	pages = {319-329},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {When discussing software, practitioners often reference parts of the project{\textquoteright}s source code. Such references have different motivations, such as mentoring and guiding less experienced developers, pointing out code that needs changes, or proposing possible strategies for the implementation of future changes. The fact that particular parts of a source code are being discussed makes these parts of the software special. Knowing which code is being talked about the most can not only help practitioners to guide important software engineering and maintenance activities, but also act as a high-level documentation of development activities for managers. In this paper, we use clone-detection as specific instance of a code search based approach for establishing links between code fragments that are discussed by developers and the actual source code of a project. Through a case study on the Eclipse project we explore the traceability links established through this approach, both quantitatively and qualitatively, and compare fuzzy code search based traceability linking to classical approaches, in particular change log analysis and information retrieval. We demonstrate a sample application of code search based traceability links by visualizing those parts of the project that are most discussed in issue reports with a Treemap visualization. The results of our case study show that the traceability links established through fuzzy code search-based traceability linking are conceptually different than classical approaches based on change log analysis or information retrieval.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Bettenburg_2012_CSMR.pdf},
	author = {Bettenburg, Nicolas and Stephen W. Thomas and Hassan, Ahmed E.}
}
@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.}
}
@proceedings {1291,
	title = {Applying Open Source Practices and Principles in Open Innovation: The Case of the Demola Platform},
	year = {2011},
	month = {10/2011},
	pages = {307-311},
	publisher = {Springer},
	abstract = {In numerous fields, businesses have to rely on rapid development and release cycles. Variant new ideas and concepts can emerge through open innovation as the participants are not limited to the company scope. This makes open innovation an increasingly appealing option for the industry. One such open innovation platform, Demola, allows university students to work on real life industrial cases of their own interest. We have identified similarities with its way of operation to open source software development and find that it offers a viable motivational, organizational and collaborative solution to open innovation.},
	author = {Kilamo, Terhi and Hammouda, Imed and Kairamo, Ville and Rasanen, Petri}
}
@conference {1313,
	title = {Do comments explain codes adequately?},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {242-245},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Comment lines in the software source code include descriptions of codes, usage of codes, copyrights, unused codes, comments, and so on. It is required for comments to explain the content of written code adequately, since the wrong description in the comment may causes further bug and confusion in maintenance.

In this paper, we try to clarify a research question: "In which projects do comments describe the code adequately?" To answer this question, we selected the group 1 of mining challenge and used data obtained from Eclipse and Netbeans. Since it is difficult to answer the above question directly, we define the distance between codes and comments. By utilizing the fault-prone module prediction technique, we can answer the alternative question from the data of two projects. The result shows that Eclipse project has relatively adequate comments.},
	keywords = {comments, eclipse, msr challenge, netbeans, prediction},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985482},
	author = {Mizuno, Osamu and Hirata, Yukinao}
}
@article {1806,
	title = {An empirical study of software architectures{\textquoteright} effect on product quality},
	journal = {Journal of Systems and Software},
	volume = {84},
	year = {2011},
	note = {"We first collected meta-data on the 21,094 most highly ranked Java projects on 2009-03-17 from SourceForge for which it was possible to get such data. Here {\textquotedblleft}Java projects{\textquotedblright} were defined as projects belonging to {\textquotedblleft}trove{\textquotedblright} 198 at SourceForge and {\textquotedblleft}rank{\textquotedblright} was the SourceForge ranking of projects. The data consisted of characteristics such as number of bugs, time of latest file upload, number of developers, number of open bugs, and SourceForge {\textquotedblleft}rank{\textquotedblright}." They did not use FLOSSmole, "A more complete analysis of the project status, could be performed by mining the FLOSSMole database (Howison et al., 2006)."},
	month = {7/2011},
	pages = {1233 - 1243},
	abstract = {Software architecture is concerned with the structure of software systems and is generally agreed to influence software quality. Even so, little empirical research has been performed on the relationship between software architecture and software quality. Basedon 1,141 open source Java projects, we calculate three software architecture metrics (measuring classes per package, normalizeddistance, and a new metric introduced by us concerning the excess of coupling degree) and analyze to which extent these metricsare related to product metrics (defect ratio, download rate, methods per class, and method complexity). We conclude that there area number of significant relationships between product metrics and architecture metrics.  In particular, the number of open defectsdepends significantly on all our architecture measures.},
	keywords = {flossmole cited, java},
	issn = {01641212},
	doi = {10.1016/j.jss.2011.02.037},
	url = {http://www.sciencedirect.com/science/article/pii/S0164121211000574},
	author = {Hansen, Klaus Marius and Jonasson, Kristjan and Neukirchen, Helmut}
}
@inbook {1586,
	title = {FLOSS Project Effectiveness Measures},
	booktitle = {Successful OSS Project Design and Implementation},
	year = {2011},
	pages = {149-168},
	publisher = {Gower},
	organization = {Gower},
	abstract = {In this chapter, we develop and illustrate measures of the effectiveness of FLOSS
projects. FLOSS is a broad term used to embrace software that is developed
and released under either a {\textquotedblleft}free software{\textquotedblright} or an {\textquotedblleft}open source{\textquotedblright} license. While
the free software and the open source movements are distinct, both kinds of
licenses allow users to obtain and distribute the software{\textquoteright}s original source
without charge (software is {\textquotedblleft}free as in beer{\textquotedblright}) and to inspect, modify, and
redistribute modifications to the source code. While the open source movement
views these freedoms pragmatically (as a development methodology), the
free software movement emphasizes the meaning of {\textquotedblleft}free as in speech,{\textquotedblright}
which is captured by the French/Spanish libre, and one of their methods of
supporting those freedoms is {\textquotedblleft}copyleft,{\textquotedblright} famously embodied in the General
Public License, meaning that derivative works must be made available under
the same license terms as the original. This chapter focuses on development
practices in distributed work, which are largely shared across the movements.
For example, many (though by no means all) FLOSS developers contribute to
projects as volunteers without working for a common organization or being
paid. We therefore use the acronym FLOSS to refer collectively to free/libre and
open source software. 

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

In the following sections of the chapter, we will first discuss several
measures of project effectiveness, and then the procedure we used to obtain
data with which to operationalize these measures, followed by the details of
the analysis approach. We then present the results of this analysis and discuss
the implications of these results. We then illustrate how these measures can be
used to compare projects as part of a research study. We conclude with some
suggestions for future research. },
	url = {http://library.trec.co.ir/pdfTemp/97805660879501.pdf$\#$page=164},
	author = {Kevin Crowston and Howison, James}
}
@proceedings {1292,
	title = {KommGame: A Reputation Environment for Teaching Open Source Software},
	year = {2011},
	month = {10/2011},
	pages = {312-315},
	publisher = {Springer},
	abstract = {The importance of teaching open source software in universities is increasing with the advent of open source as a development and business model. A novel, student centric approach of teaching open source was tried out at Tampere University of Technology where a new environment called KommGame was introduced to assist in teaching open source development. This environment includes a reputation system to motivate learners to participate. In this paper, we present our approach of teaching open source and how the KommGame environment was employed to teach open source software.},
	author = {Goduguluri, Veerakishore and Kilamo, Terhi and Hammouda, Imed}
}
@proceedings {1284,
	title = {Libre Software as an Innovation Enabler in India: Experiences of a Bangalorian Software SME},
	year = {2011},
	month = {10/2011},
	pages = {220-232},
	publisher = {Springer},
	abstract = {Free/Libre and open source software (FLOSS) has been advocated for its presumed capacity to support native software industries in developing countries. It is said to create new spaces for exploration and to lower entry barriers to mature software markets, for example. However, little empirical research has been conducted concerning FLOSS business in a developing country setting and, thus, there is not much evidence to support or refute these claims. This paper presents a business case study conducted in India, a country branded as a {\textquoteright}software powerhouse{\textquoteright} of the developing world. The findings show how FLOSS has opened up significant opportunities for the case company, especially in terms of improving its innovative capability and upgrading in the software value chain. On the other hand, they also highlight some challenges to FLOSS involvement that rise specifically from the Indian context.},
	keywords = {free software, India, INNOVATION, open source, software business},
	author = {Henttonen, Katja}
}
@proceedings {1276,
	title = {A Review of Tool Support for User-Related Communication in FLOSS Development},
	year = {2011},
	note = {"We have carried out a literature review addressing communication in FLOSS projects, and contrasted the findings with Human-Computer Interaction (HCI) literature on user-developer communication."},
	month = {10/2011},
	pages = {90-105},
	abstract = {Free/Libre/Open Source Software (FLOSS) projects rely on Internet tools for communication and in coordinating their work. Communication between developers is well supported in FLOSS projects, but user-developer communication has proven out to be challenging. This paper examines the following questions: {\textquotedblright}What kinds of means for communication exist in FLOSS projects for user-developer communication? What kinds of means should there be?{\textquotedblright} We have carried out a literature review addressing communication in FLOSS projects, and contrasted the findings with Human-Computer Interaction (HCI) literature on user-developer communication. HCI literature indicates that user-developer communication is needed during requirements construction, design and evaluation tasks, and HCI specialists are needed for orchestrating the communication and the user related tasks. Communication during the evaluation task is somewhat supported in FLOSS projects, but design and requirements construction are badly in need for support, even though ideas have already been presented. In addition, HCI specialists are in need of different kinds of communication support in FLOSS projects.},
	keywords = {Free/Libre/Open Source Software, Human-Computer Interaction, literature review, Tool Support, User-Developer Communication},
	author = {Rantalinen, Aapo and Hedberg, Henrik and Iivari, Netta}
}
@article {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}
}
@article {howison2010validity-issues,
	title = {Validity Issues in the Use of Social Network Analysis with Digital Trace data},
	journal = {Journal of the Association for Information Systems},
	volume = {12},
	year = {2011},
	chapter = {Article 2},
	abstract = {There is an exciting natural match between social network analysis methods and the growth of data sources produced by social interactions via information technologies, from online communities to corporate information systems. Information Systems researchers have not been slow to embrace this combination of method and data. Such systems increasingly provide "digital trace data" that provide new research opportunities. Yet digital trace data are substantively different from the survey and interview data for which network analysis measures and interpretations were originally developed. This paper examines ten validity issues associated with the combination of data digital trace data and social network analysis methods, with examples from the IS literature, to provide recommendations for improving the validity of research using this combination.},
	keywords = {information system, Online Communities, social network analysis, Virtuality},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HowisonSNADigitalTraceData-WorkingPaper.pdf},
	author = {Howison, James and Andrea Wiggins and Kevin Crowston}
}
@conference {1305,
	title = {Visualizing collaboration and influence in the open-source software community},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"This data set includes the complete social graph of 500,000 follow links as well as over 1,000,000 commits and 50,000 users."

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

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

"In addition to crawled data, we use the complete GitHub user follower graph from Jan 19, 2011. This graph includes 452,248 links connecting 106,247 unique users, 47\% (49,500) of which could be geocoded with the PlaceFinder API"},
	month = {05/2011},
	pages = {223-226},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {We apply visualization techniques to user profiles and repository metadata from the GitHub source code hosting service. Our motivation is to identify patterns within this development community that might otherwise remain obscured. Such patterns include the effect of geographic distance on developer relationships, social connectivity and influence among cities, and variation in project-specific contribution styles (e.g., centralized vs. distributed). Our analysis examines directed graphs in which nodes represent users{\textquoteright} geographic locations and edges represent (a) follower relationships, (b) successive commits, or (c) contributions to the same project. We inspect this data using a set of visualization techniques: geo-scatter maps, small multiple displays, and matrix diagrams. Using these representations, and tools based on them, we develop hypotheses about the larger GitHub community that would be difficult to discern using traditional lists, tables, or descriptive statistics. These methods are not intended to provide conclusive answers; instead, they provide a way for researchers to explore the question space and communicate initial insights.},
	keywords = {COLLABORATION, data exploration, geography, geoscatter, github, graph, mapping, metadata, open source, social graph, user profiles, visualization},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985476},
	url = {http://vis.stanford.edu/files/2011-GotHub-MSR.pdf},
	author = {Marschner, Eli and Rosenfeld, Evan and Heer, Jeffrey and Heller, Brandon}
}
@proceedings {1378,
	title = {When Cultures Clash: Participation in Open Source Communities and Its Implications For Organizational Commitment},
	number = {7},
	year = {2011},
	abstract = {Software applications developed within the OSS community have enjoyed tremendous success and for-profit organizations are keen to tap into this significant pool of software development talent (Chesbrough 2003; Feller et al. 2008). Examples companies include Netscape, IBM and Google (Maccormack et al. 2006). These companies seek to benefit from the talent of a global and sometimes voluntary workforce by paying some employees to contribute to OSS projects (Raymond 1999, Shah 2006). This merging of open and traditional software development may cause developer stress based on conflicting OSS community and traditional software development norms. Specifically, developers must balance company intellectual property concerns with the reciprocal and community-based norms that drive OSS development (Stewart and Gosain 2006). When these values are not in sync, contributors that aim to abide by conflicting values may exhibit dysfunctional attitudes. Employee stress with respect to their role can be destructive to organizational outcomes (Maas and Matejka 2009; Aranya and Ferris 1984). This study develops an OSS context specific model that describes the relationship between clashing software development cultures and employee organizational commitment. We leverage the rich OSS literature and the research that focuses on organizational-professional conflict (OPC) to develop hypotheses linking clashing cultures and organizational commitment. These hypotheses are tested using a combination of archival data and a survey of 127 GNOME developers. The findings presented in this paper contribute to OSS literature and offer findings that will enable organizations to more successfully engage OSS communities.},
	keywords = {gnome},
	url = { http://aisel.aisnet.org/icis2011/proceedings/projmanagement/7 },
	author = {Daniel, Sherae L. and Maruping, Likoebe M. and Cataldo, Marcelo and Herbsleb, James}
}
@article {1388,
	title = {Adoption of open source software in software-intensive organizations {\textendash} A systematic literature review},
	journal = {Information and Software Technology},
	volume = {52},
	year = {2010},
	month = {11/2010},
	pages = {1133 - 1154},
	abstract = {Context

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

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

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

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

The implications of our findings are twofold. On the one hand, practitioners should embrace the many opportunities OSS offers, but consciously evaluate the consequences of adopting it in their own context. They may use our framework and the success stories provided by the literature in their own evaluations. On the other hand, researchers should align their work, and perform more empirical research on topics that are important to organizations. Our framework may be used to position this research and to describe the context of the organization they are studying.},
	keywords = {open source software, organizations, software development, Systematic literature review},
	issn = {09505849},
	doi = {10.1016/j.infsof.2010.05.008},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584910000972},
	author = {Hauge, {\O}yvind and Ayala, Claudia and Conradi, Reidar}
}
@conference {1256,
	title = {Analyzing Leadership Dynamics in Distributed Group Communication},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)},
	year = {2010},
	note = {"Our analysis examines the communication patterns in two FLOSS development projects, Fire and Gaim"
"These data were imported into a database to allow automated analysis. The Fire data set includes about 1,800 events in the user email list, 7,800 messages in the developer venues, and 1,300 events in the combined trackers, spanning a period of 54 months. The significantly larger Gaim data set included over 41,000 events in the user forum, over 30,000 events in the developer venues, and about 20,000 events in the trackers, generated over 78 months."
"The dynamic network analysis was performed using a scientific workflow tool, Taverna Workbench"},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {We apply social network analysis (SNA) to examine the dynamics of leadership in distributed groups, specifically Free/Libre Open Source Software development projects, and its relation to group performance. Based on prior work on leadership in distributed groups, we identify leaders with those who make the highest level of contribution to the group and assess the degree of leadership by measuring centralization of communications. We compare the dynamics of leadership in two FLOSS projects, one more and one less effective. We find that in both projects, centralization was higher in developer-oriented communications venues than in user-oriented venues, suggesting higher degrees of leadership in developer venues. However, we do not find a consistent relation between centralization and effectiveness. We suggest that SNA can instead be useful for identifying interesting periods in the history of the project, e.g., periods where the leadership of the project is in transition.},
	keywords = {core, DYNAMICS, email, email archives, fire, flossmole, gaim, leadership, mailing list, project success, social network analysis, srda},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.62},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-06-02.pdf},
	author = {Kevin Crowston and Andrea Wiggins and Howison, James}
}
@conference {968,
	title = {Can development work describe itself?},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {191 - 200},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Work descriptions are informal notes taken by developers to summarize work achieved in a particular session. Existing studies indicate that maintaining them is a distracting task, which costs a developer more than 30 min. a day. The goal of this research is to analyze the purposes of work descriptions, and find out if automated tools can assist developers in efficiently creating them. For this, we mine a large dataset of heterogeneous work descriptions from open source and commercial projects. We analyze the semantics of these documents and identify common information entities and granularity levels. Information on performed actions, concerned artifacts, references and new work, shows the work management purpose of work descriptions. Information on problems, rationale and experience shows their knowledge sharing purpose. We discuss how work description information, in particular information used for work management, can be generated by observing developers{\textquoteright} interactions. Our findings have many implications for next generation software engineering tools.},
	keywords = {developer interactions, work descriptions},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463344},
	author = {Maalej, Walid and Happel, Hans-Jorg}
}
@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 {1483,
	title = {Creating and evolving developer documentation},
	booktitle = {Proceedings of the eighteenth ACM SIGSOFT international symposium},
	year = {2010},
	pages = {127},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Santa Fe, New Mexico, USANew York, New York, USA},
	abstract = {Developer documentation helps developers learn frameworks and libraries. To better understand how documentation in open source projects is created and maintained, we performed a qualitative study in which we interviewed core contributors who wrote developer documentation and developers who read documentation. In addition, we studied the evolution of 19 documents by analyzing more than 1500 document revisions. We identified the decisions that contributors make, the factors influencing these decisions and the consequences for the project. Among many findings, we observed how working on the documentation could improve the code quality and how constant interaction with the projects{\textquoteright} community positively impacted the documentation.},
	isbn = {9781605587912},
	doi = {10.1145/1882291.1882312},
	author = {Dagenais, Barth{\'e}l{\'e}my and Robillard, Martin P.}
}
@conference {951,
	title = {The evolution of ANT build systems},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {42 - 51},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Build systems are responsible for transforming static source code artifacts into executable software. While build systems play such a crucial role in software development and maintenance, they have been largely ignored by software evolution researchers. With a firm understanding of build system aging processes, project managers could allocate personnel and resources to build system maintenance tasks more effectively, reducing the build maintenance overhead on regular development activities. In this paper, we study the evolution of ANT build systems from two perspectives: (1) a static perspective, where we examine the build system specifications using software metrics adopted from the source code domain; and (2) a dynamic perspective where representative sample build runs are conducted and their output logs are analyzed. Case studies of four open source ANT build systems with a combined history of 152 releases show that not only do ANT build systems evolve, but also that they need to react in an agile manner to changes in the source code.},
	keywords = {ant, argouml, build, eclipse, jboss, maintenance, metrics, source code, tomcat},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463341},
	attachments = {https://flosshub.org/sites/flosshub.org/files/42msr2010_mcintosh.pdf},
	author = {McIntosh, Shane and Adams, Bram and Hassan, Ahmed E.}
}
@conference {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}
}
@unpublished {1242,
	title = {Investigating the Geography of Open Source Software through Github},
	year = {2010},
	note = {"We collected our data through Github{\textquoteright}s public API, which offers the same data as available on the Github{\textquoteright}s website but presents it in a structured format for simpler processing. The data were collected from May to July of 2010"

"The data collection followed a recursive procedure. We started with a single account, belonging to one of Github{\textquoteright}s founders. We then identified accounts connected to this user, then looked for accounts connected to the newly found ones, repeating this procedure until we achieved closure. New accounts were identified through the four kinds of connections mentioned in the previous section: (1) those that follow accounts collected earlier, (2) those followed by the accounts collected earlier, (3) those whose repositories were being {\textquotedblleft}watched{\textquotedblright} by accounts collected earlier, (4) those who had made code contributions to the repositories watched by accounts collected earlier."},
	abstract = {The paper presents an empirical study of the geography of open source software development that looks at Github, a popular project hosting website. We show that developers are highly clustered and concentrated primarily in North America and Western and Northern Europe, though a substantial minority is present in other regions. Code contributions and attention show a strong local bias. Users in North America account for a larger share of received contributions than of contributions made. They also receive a disproportionate amount of attention.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Takhteyev-Hilts-2010.pdf},
	author = {Yuri Takhteyev and Andrew Hilts}
}
@conference {Hissam,
	title = {On Open and Collaborative Software Development in the DoD},
	booktitle = {Seventh Annual Acquisition Research Symposium, {NPS} Proceedings -},
	volume = {1},
	number = {1},
	year = {2010},
	month = {04/2010},
	pages = {219{\textendash}235},
	publisher = {Naval Postgraduate School},
	organization = {Naval Postgraduate School},
	address = {Monterey, California},
	abstract = {The US Department of Defense (specifically, but not limited to, the DoD CIO{\textquoteright}s Clarifying Guidance Regarding Open Source Software, DISA{\textquoteright}s launch of Forge.mil and OSD{\textquoteright}s Open Technology Development Roadmap Plan) has called for increased use of open source software and the adoption of best practices from the free/open source software (F/OSS) community to foster greater reuse and innovation between programs in the DoD. In our paper, we examine some key aspects of open and collaborative software development inspired by the success of the F/OSS movement as it might manifest itself within the US DoD. This examination is made from two perspectives: the reuse potential among DoD programs sharing software and the incentives, strategies and policies that will be required to foster a culture of collaboration needed to achieve the benefits indicative of F/OSS. Our conclusion is that to achieve predictable and expected reuse, not only are technical infrastructures needed, but also a shift to the business practices in the software development and delivery pattern seen in the traditional acquisition lifecycle is needed. Thus, there is potential to overcome the challenges discussed within this paper to engender a culture of openness and community collaboration to support the DoD mission.},
	keywords = {collaborative development, open source software, reuse, software engineering},
	url = {http://www.acquisitionresearch.net/cms/_files/FY2010/NPS-AM-10-037.pdf},
	author = {Hissam, S. A. and Weinstock, C. and Bass, L.}
}
@conference {962,
	title = {OSS developers context-specific Preferred Representational systems: A initial Neurolinguistic text analysis of the Apache mailing list},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {126 - 129},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Open Source Software (OSS) mailing lists are used by developers to discuss software engineering tasks performed in the project. In the last years, researchers have been conducting mailing lists linguistic analyses for understanding the intricacies of OSS development. An unpublished approach for that is to use NeuroLinguistic Theory (NT). NT postulates the use of a Preferred Representational cognitive System (PRS) in specific contexts. This means that different resources and cognitive channels are used by developers in order to understand software, but what types of representational systems are the preferred by software engineers? This paper introduces a psychometrically-based neuro-linguistic analysis tool to classify developers, and presents early results of an experiment to assess the PRS of four top developers against a baseline of the Apache server mailing list.},
	keywords = {apache, email, email archives, mailing lists, neurolinguistics},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463339},
	author = {Junior, Methanias Colaco and Mendonca, Manoel and Farias, Mario and Henrique, Paulo}
}
@conference {835,
	title = {Paying attention to each other in visible work communities: Modeling bursty systems of multiple activity streams},
	booktitle = {SocialCom/PASSAT(2010)},
	year = {2010},
	note = {Uses open source projects to study, but this is not about open source, per se.},
	month = {2010},
	pages = {276-281},
	abstract = {Online work projects, from open source to wikipedia, have emerged as an important phenomenon. These communities offer exciting opportunities to investigate social processes because they leave traces of their activity over time. Unlike traditional work teams, the participants in these communities are widely dispersed and work without centralized management. The question arises, then, as to the extent to which these are in fact communities: is the group simply the sum of the individuals that make it up, or does the group function as a social unit? We explore this question in the temporal domain.
We argue that the rapid visibility of others{\textquoteright} work afforded by the information systems used by these projects reaches out and attracts the attention of others who are peripherally aware of the group{\textquoteright}s online space, prompting them to begin or intensify their participation, binding separate individual streams of activity into a social entity.

Previous work has suggested that for certain types of bursty social behavior (e.g. email), the frequency of the behavior is not homogeneously distributed but rather can be divided into two generative mechanisms: active sessions and passive background participation. We extend this work for the case of multiple conditionally independent streams of behavior, where each stream is generated by these two generative mechanisms. Our model can characterized by a double-chain hidden Markov model, allowing efficient inference using expectation-maximization. We apply this model to visible work communities by modeling each participant as a single stream of behavior, assessing transition probabilities between active sessions of different participants. This allows us to examine the extent to which the various members of the community are influenced by the active participation of others. Our results indicate that an active session by a participant at least triples the likelihood of another participant beginning an active session.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/olson2010paying-attentio.pdf},
	author = {Olson, Jamie F and Howison, James and Carley, Kathleen}
}
@conference {1220,
	title = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	abstract = {The Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010) aims at building a commu- nity of researchers and practitioners to share experiences and discuss chal- lenges involved in building and maintaining open source communities. De- tailed	information	regarding	the	workshop	is	available	at http://tutopen.cs.tut.fi/oscomm10/.},
	keywords = {oscomm, oscomm2010, oss2010, workshop},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm000.pdf},
	author = {Hammouda, Imed and Aaltonen, Timo and Capiluppi, Andrea}
}
@conference {967,
	title = {Should I contribute to this discussion?},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {181 - 190},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town},
	abstract = {Development mailing lists play a central role in facilitating communication in open source projects. Since these lists frequently host design and project discussions, knowledgeable contribution to these discussion threads is essential to avoid mis-communication that might slow-down the progress of a project. However, given the sheer volume of emails on these lists, it is easy to miss important discussions. To find out how developers are able to deal with mailing list discussions, we study the main factors that encourage developers to contribute to the development mailing lists. We develop personalized models to automatically identify discussion threads that a developer would contribute to based on his previous contribution behavior. Case studies on development mailing lists of three open source projects (Apache, PostgreSQL and Python) show that the average accuracy of our models is 89-85\% and that the models vary significantly between different developers.},
	keywords = {apache, contributions, developers, email, email archives, mailing lists, postgresql, python},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463345},
	attachments = {https://flosshub.org/sites/flosshub.org/files/181ibrahim-msr2010.pdf},
	author = {Ibrahim, Walid M and Bettenburg, Nicolas and Shihab, Emad and Adams, Bram and Hassan, Ahmed E.}
}
@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 {1332,
	title = {Using Open Source Software Components to Implement a Modular Web 2.0 Design for Map-Based Discussions},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {30 - 47},
	abstract = {This paper discusses the research-based origins and modular architecture of an open source geospatial tool that facilitates synchronous individual and group discussions using the medium of a Web map service. The software draws on existing open source geospatial projects and associated libraries and techniques that have evolved as part of the new generation of Web applications. The purpose of the software is discussed, highlighting the fusion of existing open source projects to produce new tools. Two case studies are briefly discussed to illustrate the value an open source approach brings to communities who would remain otherwise outside the reach of proprietary software tools. The paper concludes with comments on the project{\textquoteright}s future evolution as an open source participatory mapping platform.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010070102},
	author = {Leahy, Michael G. and Hall, G. Brent}
}
@article {1387,
	title = {Using the DEMO methodology for modeling open source software development processes},
	journal = {Information and Software Technology},
	volume = {52},
	year = {2010},
	month = {6/2010},
	pages = {656 - 671},
	abstract = {Context

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

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

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

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

We have shown that the DEMO methodology can be successfully used to model OSSD processes and to obtain abstract and high-quality OSSD process models. However, given some potential drawbacks with respect to understandability and implementability, we primarily propose the use of DEMO within OSSD process modeling as an analysis tool that should be complemented with other techniques and models for communication and reenactment purposes.},
	keywords = {DEMO, Enterprise ontology, open source software, Software process modeling},
	issn = {09505849},
	doi = {10.1016/j.infsof.2010.02.002},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584910000157},
	author = {Huysmans, Philip and Ven, Kris and Verelst, Jan}
}
@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 {609,
	title = {The Case Study of an F/OSS Virtualization Platform Deployment and Quantitative Results},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {367 - 367},
	publisher = {Springer},
	organization = {Springer},
	chapter = {41},
	abstract = {In this paper we present practical experiences and results from the deployment of an F/OSS virtualization platform. EKT{\textquoteright}s (NDC) core IT infrastructure was transformed to a virtualized one, using exclusively F/OSS, while severe budget and timing constraints were in place. This migration was initiated in order to better cope with EKT{\textquoteright}s services requirements, while accommodating at the same time the need for the in house development of a large scale open access infrastructure. The benefits derived from this migration were not only generic virtualization benefits, such as the quantifiable reduced power consumption and cost reduction through consolidation, but also F/OSS virtualization specific ones.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_41},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Case\%20Study\%20of\%20an\%20F\%20OSS.pdf},
	author = {Stathopoulos, Panagiotis and Soumplis, Alexandros and Houssos, Nikos}
}
@conference {587,
	title = {Challenges of the Open Source Component Marketplace in the Industry},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	year = {2009},
	month = {2009///},
	pages = {213 - 224},
	publisher = {Springer},
	organization = {Springer},
	chapter = {19},
	abstract = {The reuse of Open Source Software components available on the Internet is playing a major role in the development of Component Based Software Systems. Nevertheless, the special nature of the OSS marketplace has taken the {\textquotedblleft}classical{\textquotedblright} concept of software reuse based on centralized repositories to a completely different arena based on massive reuse over Internet. In this paper we provide an overview of the actual state of the OSS marketplace, and report preliminary findings about how companies interact with this marketplace to reuse OSS components. Such data was gathered from interviews in software companies in Spain and Norway. Based on these results we identify some challenges aimed to improve the industrial reuse of OSS components.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_19},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Challenges\%20of\%20the\%20Open\%20Source.pdf},
	author = {Ayala, Claudia and Hauge, {\O}yvind and Conradi, Reidar and Franch, Xavier and Li, Jingyue and Velle, Ketil}
}
@article {1349,
	title = {Communication Network Characteristics of Open Source Communities},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {26 - 48},
	abstract = {Empirical research has shown that social network structure is a critical success factor for various kinds of work groups. The authors extended this research to a new type of work group{\textemdash}the open source software project community{\textemdash}with the objective of exploring the role of communication networks within these intriguing projects. Using archival data from 143 open source project groups, the authors compiled six measures of social network structure and analyzed these in relation to four measures of group success. This study found that the social network structures of these project communities did not appear to be critical success factors at all, but rather they had no significant impact on success or their effect was opposite of that seen in prior studies of work groups. Various conjectures were suggested that might explain these results, offering opportunities for further research.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009100102},
	author = {Hinds, David and Lee, Ronald M.}
}
@conference {579,
	title = {Estimating Commit Sizes Efficiently},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {105 - 115},
	publisher = {Springer},
	organization = {Springer},
	chapter = {11},
	abstract = {The quantitative analysis of software projects can provide insights that let us better understand open source and other software development projects. An important variable used in the analysis of software projects is the amount of work being contributed, the commit size. Unfortunately, post-facto, the commit size can only be estimated, not measured. This paper presents several algorithms for estimating the commit size. Our performance evaluation shows that simple, straightforward heuristics are superior to the more complex text-analysis-based algorithms. Not only are the heuristics significantly faster to compute, they also deliver more accurate results when estimating commit sizes. Based on this experience, we design and present an algorithm that improves on the heuristics, can be computed equally fast, and is more accurate than any of the prior approaches.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_11},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Estimating\%20Commit\%20Sizes\%20Effciently.pdf},
	author = {Hofmann, Philipp and Dirk Riehle}
}
@conference {941,
	title = {Evolution of the core team of developers in libre software projects},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {167 - 170},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {In many libre (free, open source) software projects, most of the development is performed by a relatively small number of persons, the "core team". The stability and permanence of this group of most active developers is of great importance for the evolution and sustainability of the project. In this position paper we propose a quantitative methodology to study the evolution of core teams by analyzing information from source code management repositories. The most active developers in different periods are identified, and their activity is calculated over time, looking for core team evolution patterns.},
	keywords = {core, cvs, cvsanaly, developers, evolution, gimp, scm},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069497},
	attachments = {https://flosshub.org/sites/flosshub.org/files/167core-evolution.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Herraiz, Israel}
}
@conference {856,
	title = {Facts or Friends? Distinguishing Informational and Conversational Questions in Social QnA Sites (forthcoming)},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2009},
	author = {Harper, F. Maxwell and Moy, D. and Konstan, J.A.}
}
@conference {600,
	title = {First International Workshop on Building Sustainable Open Source Communities (OSCOMM 2009)},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {353 - 354},
	publisher = {Springer},
	organization = {Springer},
	chapter = {32},
	abstract = {The First International Workshop on Building Sustainable Open Source Communities aims at building a community of researchers and practitioners to share experiences and discuss challenges involved in building and maintaining open source communities.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_32},
	attachments = {https://flosshub.org/sites/flosshub.org/files/First\%20International\%20Workshop.pdf},
	author = {Hammouda, Imed and Aaltonen, Timo and Capiluppi, Andrea}
}
@conference {936,
	title = {From work to word: How do software developers describe their work?},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {121 - 130},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Developers take notes about their work sessions, either to remember the work status and share it with collaborators, or because employers explicitly require this for project management matters. We report on an exploratory study which aims at understanding how software developers describe their work. We analyzed more than 750,000 work descriptions of about 2,000 professionals taken over 8 years in three settings. We observed several similarities in the content and time meta-data of work descriptions. Most frequent terms, such as top-30 performed activities, are used consistently. Particular templates such as ldquoACTION concerning ARTIFACT because of CAUSErdquo occur frequently. Developers described sessions that last 30-120 min. 4-16 times a day. Maintaining diaries seems to consume between 3-6\% of the total work time, and in 10\% of the sessions, developers did not describe their work in sufficient detail. We argue that our results make the first step towards automatically generating work diaries for software developers.},
	keywords = {apache, developers, diaries, eureka, mycomp, scm, work management system},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069490},
	author = {Maalej, Walid and Happel, Hans-Jorg}
}
@conference {594,
	title = {Group Maintenance Behaviors of Core and Peripherial Members of Free/Libre Open Source Software Teams},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {298 - 309},
	publisher = {Springer},
	organization = {Springer},
	chapter = {26},
	abstract = {Group Maintenance is pro-social, discretionary, and relation-building behavior that occurs between members of groups in order to maintain reciprocal trust and cooperation. This paper considers how Free/libre Open Source Software (FLOSS) teams demonstrate such behaviors within the context of e-mail, as this is the primary medium through which such teams communicate. We compare group maintenance behaviors between both core and peripheral members of these groups, as well as behaviors between a group that remains producing software today and one which has since dissolved. Our findings indicate that negative politeness tactics (those which show respect for the autonomy of others) may be the most instrumental group maintenance behaviors that contribute to a FLOSS group{\textquoteright}s ability to survive and continue software production.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_26},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Group\%20Maintenance\%20Behavior.pdf},
	author = {Scialdone, Michael and Li, Na and Robert Heckman and Kevin Crowston}
}
@conference {578,
	title = {Heartbeat: Measuring Active User Base and Potential User Interest in FLOSS Projects},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {94 - 104},
	publisher = {Springer},
	organization = {Springer},
	chapter = {10},
	abstract = {This paper presents a novel method and algorithm to measure the size of an open source project{\textquoteright}s user base and the level of potential user interest that it generates. Previously unavailable download data at a daily resolution confirms hypothesized patterns related to release cycles. In short, regular users rapidly download the software after a new release giving a way to measure the active user base. In contrast, potential new users download the application independently of the release cycle, and the daily download figures tend to plateau at this rate when a release has not been made for some time. An algorithm for estimating these measures from download time series is demonstrated and the measures are examined over time in two open source projects.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_10},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Heatbeat\%20Measuring\%20Active\%20Use.pdf},
	author = {Andrea Wiggins and Howison, James and Kevin Crowston}
}
@conference {590,
	title = {Integrating HCI Specialists into Open Source Software Development Projects},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {251 - 263},
	publisher = {Springer},
	organization = {Springer},
	chapter = {22},
	abstract = {Typical open source software (OSS) development projects are organized around technically talented developers, whose communication is based on technical aspects and source code. Decision-making power is gained through proven competence and activity in the project, and non-technical end-user opinions are too many times neglected. In addition, also human-computer interaction (HCI) specialists have encountered difficulties in trying to participate in OSS projects, because there seems to be no clear authority and responsibility for them. In this paper, based on HCI and OSS literature, we introduce an extended OSS development project organization model that adds a new level of communication and roles for attending human aspects of software. The proposed model makes the existence of HCI specialists visible in the projects, and promotes interaction between developers and the HCI specialists in the course of a project.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_22},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Intergrating\%20HCI\%20Specialists.pdf},
	author = {Hedberg, Henrik and Iivari, Netta}
}
@conference {844,
	title = {A Jury of Your Peers: Quality, Experience and Ownership in Wikipedia},
	booktitle = {The International Symposium on Wiki{\textquoteright}s and Open Collaboration},
	year = {2009},
	month = {10/2009},
	address = {Orlando, FL},
	keywords = {experience,, ownership,, peer, peer,, quality, review,, wikipedia,, wikiwork,},
	author = {Halfaker, A. and Kittur, N. and Kraut, R. and Riedl, J.}
}
@conference {923,
	title = {MapReduce as a general framework to support research in Mining Software Repositories (MSR)},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {21 - 30},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Researchers continue to demonstrate the benefits of Mining Software Repositories (MSR) for supporting software development and research activities. However, as the mining process is time and resource intensive, they often create their own distributed platforms and use various optimizations to speed up and scale up their analysis. These platforms are project-specific, hard to reuse, and offer minimal debugging and deployment support. In this paper, we propose the use of MapReduce, a distributed computing platform, to support research in MSR. As a proof-of-concept, we migrate J-REX, an optimized evolutionary code extractor, to run on Hadoop, an open source implementation of MapReduce. Through a case study on the source control repositories of the Eclipse, BIRT and Datatools projects, we demonstrate that the migration effort to MapReduce is minimal and that the benefits are significant, as running time of the migrated J-REX is only 30\% to 50\% of the original J-REX{\textquoteright}s. This paper documents our experience with the migration, and highlights the benefits and challenges of the MapReduce framework in the MSR community.},
	keywords = {hadoop, mapreduce},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069477},
	attachments = {https://flosshub.org/sites/flosshub.org/files/21MSR2009-MSR-0114-Shang-Weiyi.pdf},
	author = {Weiyi Shang and Zhen Ming Jiang and Adams, Bram and Hassan, Ahmed E.}
}
@article {1252,
	title = {On the Maturity of Open Source BPM Systems},
	journal = {BP Trends},
	year = {2009},
	note = {"Figure 1 shows a snapshot (from 3rd of July 2008) of the most downloaded workflow and BPM systems distributed through a code repository. The systems in the figure are ordered historically with respect to month and year of their registration. The code repositories searched for this snapshot were SourceForge, RubyForge, ObjectWebForge, Tigris.org, BountySource, BerliOS, JavaForge and GNU Savannah"},
	month = {06/2009},
	pages = {(11 pages)},
	abstract = {Two major trends in the area of information systems development are the growing interest for Workflow and Busi- ness Process Management (BPM) systems and the increasing acceptance and spread of open source software. This development raises the following questions:
1. What are the prominent representatives of current open source Workflow and BPM systems? 2. What is the maturity level of these systems?
Seeking answers to these questions we have performed a study. First an overview of the existing open source systems was made and three systems: jBPM, OpenWFE, and Enhydra Shark, selected for further analysis. Then a detailed analysis on the selected systems was performed. The results from this analysis were documented and the developers invited to comment. Based on the feedback from the developers the results were revisited and the study finalized [5]. In this article we summarise the study and reflect on the area of open source BPM systems.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bpm.pdf},
	author = {Wohed, P. and ter Hofstede, A.H.M. and Russell, N. and Andersson, B. and van der Aalst, W.M.P}
}
@conference {928,
	title = {Mining source code to automatically split identifiers for software analysis},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {71 - 80},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Automated software engineering tools (e.g., program search, concern location, code reuse, quality assessment, etc.) increasingly rely on natural language information from comments and identifiers in code. The first step in analyzing words from identifiers requires splitting identifiers into their constituent words. Unlike natural languages, where space and punctuation are used to delineate words, identifiers cannot contain spaces. One common way to split identifiers is to follow programming language naming conventions. For example, Java programmers often use camel case, where words are delineated by uppercase letters or non-alphabetic characters. However, programmers also create identifiers by concatenating sequences of words together with no discernible delineation, which poses challenges to automatic identifier splitting. In this paper, we present an algorithm to automatically split identifiers into sequences of words by mining word frequencies in source code. With these word frequencies, our identifier splitter uses a scoring technique to automatically select the most appropriate partitioning for an identifier. In an evaluation of over 8000 identifiers from open source Java programs, our Samurai approach outperforms the existing state of the art techniques.},
	keywords = {java, samurai, sourceforge},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069482},
	attachments = {https://flosshub.org/sites/flosshub.org/files/71EnslenandHillandPollockandVijayShanker.pdf},
	author = {Enslen, Eric and Hill, Emily and Pollock, Lori and Vijay-Shanker, K.}
}
@conference {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 {DBLP:conf/msr/BirdRBHGD09,
	title = {The promises and perils of mining git},
	booktitle = {Proceedings of the 6th International Working Conference on Mining Software Repositories, MSR 2009},
	year = {2009},
	pages = {1-10},
	abstract = {We are now witnessing the rapid growth of decentralized source code management (DSCM) systems, in which every developer has her own repository. DSCMs facilitate a style of collaboration in which work output can flow sideways (and privately) between collaborators, rather than always up and down (and publicly) via a central repository. Decentralization comes with both the promise of new data and the peril of its misinterpretation. We focus on git, a very popular DSCM used in high-profile projects. Decentralization, and other features of git, such as automatically recorded contributor attribution, lead to richer content histories, giving rise to new questions such as "How do contributions flow between developers to the official project repository?" However, there are pitfalls. Commits may be reordered, deleted, or edited as they move between repositories. The semantics of terms common to SCMs and DSCMs sometimes differ markedly, potentially creating confusion. For example, a commit is immediately visible to all developers in centralized SCMs, but not in DSCMs. Our goal is to help researchers interested in DSCMs avoid these and other perils when mining and analyzing git data.},
	keywords = {dscm, git, mining, scm, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1promisePeril.pdf},
	author = {Christian Bird and Peter C. Rigby and Earl T. Barr and David J. Hamilton and Daniel M. Germ{\'a}n and Premkumar T. Devanbu}
}
@conference {576,
	title = {Providing Commercial Open Source Software: Lessons Learned},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {70 - 82},
	publisher = {Springer},
	organization = {Springer},
	chapter = {8},
	abstract = {Even though companies like Sun, IBM, MySQL and others have released several commercial Open Source Software (OSS) products, little evidence exist of how to successfully launch such products and establish a living community around them. This paper presents a case study from a small software company succeeding at establishing a business model and a vivid community around their own OSS products. Based on this case study, the paper presents lessons learned which could help other OSS providers.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_8},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Providing\%20Commercial\%20Open\%20Source.pdf},
	author = {Hauge, {\O}yvind and Ziemer, Sven}
}
@conference {herraiz2009research,
	title = {Research friendly software repositories},
	booktitle = {Proceedings of the joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops},
	year = {2009},
	note = {"In spite of these rich availability of software repositories,
the heterogeneity of the data makes it difficult to apply studies
at a large scale, although some research projects, like
FLOSSMole [10] or FLOSSMetrics [8] are addressing these
issues and aim to provide datasets about thousands of libre
software projects for research purposes."

(more)},
	pages = {19{\textendash}24},
	publisher = {ACM},
	organization = {ACM},
	abstract = {What is the future of software evolution? In 1974, Meir M. Lehman had a vision of software evolution being driven by empirical studies of software repositories, and of a theory based on those empirical results. However, that scenario is yet to come. Software evolution studies are often based on a few cases, because the needed information is scarce, dispersed and incomplete. Their conclusions are not generalizable, slowing down the progress of this research discipline. Libre (free / open source) software supposes an opportunity to alleviate this situation. In this paper we describe the existing approaches to provide research datasets that are mining libre software repositories, and propose an agenda based on the concept of research friendly software repositories, which provides finer granularity and integrated data.},
	keywords = {flossmetrics, flossmole cited},
	attachments = {https://flosshub.org/sites/flosshub.org/files/herraiz-Research-Friendly-sw-repos.pdf},
	author = {Herraiz, I. and Robles, G. and Gonzalez-Barahona, J.M.}
}
@conference {H{\"a}rtig09roitzsch:the,
	title = {Roitzsch: The Mathematics of Obscurity: On the Trustworthiness of Open Source},
	booktitle = {9th Workshop on the Economics of Information Security (WEIS)},
	year = {2009},
	pages = {2016{\textendash}2023},
	publisher = {ACM},
	organization = {ACM},
	abstract = {It is more difficult to find errors when source code is secret.
More people search for errors when source code is
public. These counteracting effects are pivotal to the question
whether openness fosters security. Errors in software
are found by people with either constructive contribution or
exploitation in mind. Focusing exclusively on this discovery
aspect, we present a probabilistic model, which allows us to
compare the open source and closed source situations.
We start out with our assumptions explained using a simple
introductory model. We then extend this to what we
believe to be an adequate model of a bug-hunting process
conducted by multiple competing parties. The model employs
an asymmetric race paradigm. One of the surprising
results is that even an arbitrarily large group with good intentions
cannot safely dominate the evil attackers. Instead,
they are limited by a significant upper bound in their winning
chances.},
	url = {http://www.econinfosec.org/archive/weis2010/papers/session6/weis2010_haertig.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/weis2010_haertig.pdf},
	author = {Hermann H{\"a}rtig and Claude-joachim Hamann and Michael Roitzsch and Technische Universit{\"a}t Dresden}
}
@conference {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.}
}
@article {1236,
	title = {Tools for the Study of the Usual Data Sources found in Libre Software Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	month = {31/2009},
	pages = {24 - 45},
	abstract = {Due to the open nature of Free/Libre/Open Source software projects, researchers have gained access to a rich set of development-related information. Although this information is publicly available on the Internet, obtaining and analyzing it in a convenient way is not an easy task and many considerations have to be taken into account. In this paper we present the most important data sources that can be found in libre software projects and that are studied by the research community: source code, source code management systems, mailing lists and bug tracking systems. We will give advice for the problems that can be found when retrieving and preparing the data sources for a posterior analysis, as well as provide information about the tools that support these tasks.},
	keywords = {bug tracking systems, data sources, mailing lists, scm, tools},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009010102},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles.pdf},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Izquierdo-Cortazar, Daniel and Herraiz, Israel}
}
@conference {Orsila:2009:TIO:1527033.1527037,
	title = {Trust issues in open source software development},
	booktitle = {Proceedings of the Warm Up Workshop for ACM/IEEE ICSE 2010},
	series = {WUP {\textquoteright}09},
	year = {2009},
	note = {"We have selected two highly reusable libraries, zlib and FFmpeg. The software repository of the projects were downloaded, but mining the information is not an easy task and we considered various sources {\textemdash} such as bug reports, mailing lists, IRC conversations, and source code comments {\textemdash} in addition to the revision history. "},
	pages = {9{\textendash}12},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source software and the associated development model holds great promise, but the issue of trust is a major challenge. This applies to companies wishing to adopt the open source model but also within open source projects. We investigate this issue by data mining open source repositories to study two related phenomena: update propagation and distributed version control.},
	keywords = {ffmpeg, trust, version control, zlib},
	isbn = {978-1-60558-565-9},
	doi = {10.1145/1527033.1527037},
	url = {http://doi.acm.org/10.1145/1527033.1527037},
	author = {Orsila, Heikki and Geldenhuys, Jaco and Ruokonen, Anna and Hammouda, Imed}
}
@conference {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 {851,
	title = {Wikipedians are born, not made: a study of power editors on Wikipedia},
	booktitle = {ACM 2009 International Conference on Group Work},
	year = {2009},
	month = {05/10/2009},
	pages = {51-60},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Sanibel Island, FL},
	keywords = {computer-supported, cooperative, interaction, web-based, work,},
	author = {Panciera, K. and Halfaker, A. and Terveen, L.}
}
@conference {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 {flosswp408,
	title = {Asynchronous Decision-Making in Distributed Teams},
	booktitle = {Computer Supported Cooperative Work 2008},
	year = {2008},
	month = {July},
	pages = {1{\textendash}2},
	abstract = {Extensive use of CSCW applications can influence group decision-making practices. Unlike previous research focused on the influence of synchronous ICTs, our study examines how group decisions are made in asynchronous communication channels. Our inductive qualitative analysis of 360 decision episodes of six FLOSS projects revealed diversity in decision-making practices, which appears to be related to differences in project effectiveness and task type. We also find that standardization of procedures through CSCW tools transforms the nature of some software development work from non-routine to standard procedure.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CSCW2008FLOSSposter_sub.pdf , https://flosshub.org/sites/flosshub.org/files/CSCW2008Poster11x17sub.pdf},
	author = {Li, Qing and Robert Heckman and Eileen Allen and Kevin Crowston and Eseryel, U. Yeliz and James Howison and Andrea Wiggins}
}
@book {48,
	title = {Biobazaar: The Open Source Revolution and Biotechnology},
	year = {2008},
	publisher = {Harvard University Press},
	organization = {Harvard University Press},
	author = {Janet Hope}
}
@conference {971,
	title = {Branching and merging in the repository},
	booktitle = {the 2008 international workshopProceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {19-22},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Two of the most complex operations version control software allows a user to perform are branching and merging. Branching provides the user the ability to create a copy of the source code to allow changes to be stored in version control but outside of the trunk. Merging provides the user the ability to copy changes from a branch to the trunk. Performing a merge can be a tedious operation and one that may be error prone. In this paper, we compare file revisions found on branches with those found on the trunk to determine when a change that is applied to a branch is moved to the trunk. This will allow us to study how developers use merges and to determine if merges are in fact more error prone than other commits.},
	keywords = {argouml, changes, cvs2svn, diffj, revision, scm, source code, version control},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370754},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p19-williams.pdf},
	author = {Spacco, Jamie and Williams, Chadd C.}
}
@booklet {493,
	title = {Champions of Revealing - The Role of Open Source Developers in Commercial Firms},
	year = {2008},
	month = {Jan},
	abstract = {The link between firms engaging in open source software (OSS) development and the OSS community is established by individual developers. This linkage might entail a principal-agent issue due to the developer{\textquoteright}s double allegiance to firm and OSS community, and expose the firm to the risk of losing intellectual property. Using both interviews and a large-scale survey, I substantiate the importance of the developer{\textquoteright}s role. However, neither interview data nor regression analysis show indications of commercially harmful revealing behavior induced by ""Free Software ideology."" Management, on the other hand, sometimes seems to be overly concerned about openness. I conclude that a more positive stance towards openness will allow firms to better share in the benefits of open innovation processes.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Henkel_Champions_of_revealing_2008-01.pdf},
	author = {Joachim Henkel}
}
@conference {1207,
	title = {Cross-repository data linking with RDF and OWL},
	booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)},
	year = {2008},
	note = {non-experimental},
	month = {2009},
	pages = {15-22},
	abstract = {This paper provides an approach to the problem of integrating data from multiple research repositories for FLOSS 
data. It introduces semantic web technologies (RDF, OWL, OWL-DL reasoners and SPARQL) to argue that these are useful for building shared research infrastructure. The paper illustrates its point by describing parts of an ontology developed for the integration and analysis of project communications drawn from FLOSSmole, the Notre Dame archive and direct collection of data. RDF vocabularies provide a way to agree on things we agree about as well as a way to be clearer about ways in which we disagree.},
	keywords = {data integration, flossmole, forges, integration, owl, RDF, repositories, semantic, semantic Web, sparql, srda},
	attachments = {https://flosshub.org/sites/flosshub.org/files/howison2008.pdf},
	author = {Howison, James}
}
@conference {970,
	title = {Determinism and evolution},
	booktitle = {Proceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {1-9},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {It has been proposed that software evolution follows a Self-Organized Criticality (SOC) dynamics. This fact is supported by the presence of long range correlations in the time series of the number of changes made to the source code over time. Those long range correlations imply that the current state of the project was determined time ago. In other words, the evolution of the software project is governed by a sort of determinism. But this idea seems to contradict intuition. To explore this apparent contradiction, we have performed an empirical study on a sample of 3,821 libre (free, open source) software projects, finding that their evolution projects is short range correlated. This suggests that the dynamics of software evolution may not be SOC, and therefore that the past of a project does not determine its future except for relatively short periods of time, at least for libre software.},
	keywords = {changes, evolution, source code, sourceforge},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370752},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p1-herraiz.pdf},
	author = {Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Gregorio Robles and Herraiz, Israel}
}
@conference {flosswp1938,
	title = {eResearch Workflows for Studying Free and Open Source Software Development},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275},
	year = {2008},
	month = {July},
	pages = {405{\textendash}411},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper introduces eResearch workflow tools as a model for the research community studying free and open source software and its development. The paper first introduces eResearch as increasingly practiced in fields such as astrophysics and biology, then contrasts the practice of research on free and open source software. After outlining suitable research data sets the paper introduces a class of tools known as scientific workflow frameworks, focusing on one?Taverna?and introducing its features. To further explain the tool a complete workflow used for original research on FLOSS is described. Finally the paper considers the trade-offs inherent in these tools.},
	author = {Howison, James and Andrea Wiggins and Kevin Crowston}
}
@conference {566,
	title = {eResearch Workflows for Studying Free and Open Source Software Development},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {405 - 411},
	publisher = {Springer},
	organization = {Springer},
	chapter = {39},
	abstract = {This paper introduces eResearch workflow tools as a model for the research community studying free and open source software and its development. The paper first introduces eResearch as increasingly practiced in fields such as astrophysics and biology,then contrasts the practice of research on free and open source software. After outlining suitable research data sets the paper introduces a class of tools known as scientific workflow frameworks, focusing on one{\textemdash}Taverna{\textemdash}and introducing its features.To further explain the tool a complete workflow used for original research on FLOSS is described. Finally the paper considers the trade-offs inherent in these tools.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_39},
	attachments = {https://flosshub.org/sites/flosshub.org/files/eResearch\%20Workflows.pdf},
	author = {Howison, James and Andrea Wiggins and Kevin Crowston}
}
@unpublished {flosswp415,
	title = {eScience for Free/Libre Open Source Software Researchers},
	year = {2008},
	month = {August},
	publisher = {FLOSSpapers},
	type = {Working Paper},
	abstract = {This paper presents a case study of the application of eScience tools and practices for the social science research community studying Free/Libre Open Source Software (FLOSS) development practices. We first describe what we mean by eScience and introduce research on FLOSS to motivate the need for eScience tools and approaches. We then describe our initial efforts to introduce eScience tools for FLOSS research, potential obstacles, and how the use of such tools might affect the practice of research in this field.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/eResearch2008iCS-working.pdf},
	author = {Kevin Crowston and Andrea Wiggins and James Howison}
}
@conference {Hata:2008:EFF:1370750.1370772,
	title = {An extension of fault-prone filtering using precise training and a dynamic threshold},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {89{\textendash}98},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Fault-prone module detection in source code is important for assurance of software quality. Most previous fault-prone detection approaches have been based on software metrics. Such approaches, however, have difficulties in collecting the metrics and in constructing mathematical models based on the metrics. To mitigate such difficulties, we have proposed a novel approach for detecting fault-prone modules using a spam-filtering technique, named Fault-Prone Filtering. In our approach, fault-prone modules are detected in such a way that the source code modules are considered as text files and are applied to the spam filter directly. In practice, we use the training only errors procedure and apply this procedure to fault-prone. Since no pre-training is required, this procedure can be applied to an actual development field immediately. This paper describes an extension of the training only errors procedures. We introduce a precise unit of training, "modified lines of code," instead of methods. In addition, we introduce the dynamic threshold for classification. The result of the experiment shows that our extension leads to twice the precision with about the same recall, and improves 15\% on the best F1 measurement.},
	keywords = {eclipse, fault-prone modules, spam filter, text mining},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370772},
	url = {http://doi.acm.org/10.1145/1370750.1370772},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p89-hata.pdf},
	author = {Hata, Hideaki and Mizuno, Osamu and Kikuno, Tohru}
}
@conference {972,
	title = {Extracting structural information from bug reports},
	booktitle = {Proceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {27-30},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {In software engineering experiments, the description of bug reports is typically treated as natural language text, although it often contains stack traces, source code, and patches. Neglecting such structural elements is a loss of valuable information; structure usually leads to a better performance of machine learning approaches. In this paper, we present a tool called infoZilla that detects structural elements from bug reports with near perfect accuracy and allows us to extract them. We anticipate that infoZilla can be used to leverage data from bug reports at a different granularity level that can facilitate interesting research in the future.},
	keywords = {bug reports, eclipse, enumerations, infozilla, natural language, patches, source code, stack trace},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370757},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p27-bettenburg.pdf},
	author = {Premraj, Rahul and Zimmermann, Thomas and Kim, Sunghun and Bettenburg, Nicolas}
}
@conference {553,
	title = {The Networked Forge: New Environments for Libre Software Development},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {299 - 306},
	publisher = {Springer},
	organization = {Springer},
	chapter = {26},
	abstract = {Libre (free, open source) software forges (sites hosting the development infrastructure for a collection of projects) have been stable in architecture, services and concept since they become popular during the late 1990s. During this time several problems that cannot be solved without dramatic design changes have become evident. To overcome them, we propose a new concept, the {\textquotedblleft}networked forge{\textquotedblright}, focused on addressing the core characteristics of libre software development and the needs of developers. The key of this proposal is to re-engineer forges as a net of distributed components which can be composed and configured according to the needs of users, using a combination of web 2.0, semantic web and mashup technologies. This approach is flexible enough to accommodate different development processes, while at the same time interoperates with current facilities.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_26},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Networked\%20Forge.pdf},
	author = {Gonzalez-Barahona, Jesus and Mart{\'\i}nez, Andr{\'e}s and Polo, Alvaro and Hierro, Juan and Reyes, Marcos and Soriano, Javier and Fern{\'a}ndez, Rafael}
}
@conference {Holmes:2008:NGE:1370750.1370787,
	title = {A newbie{\textquoteright}s guide to eclipse APIs},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {149{\textendash}152},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Eclipse has evolved from a fledgling Java IDE into a mature software ecosystem. One of the greatest benefits Eclipse provides developers is flexibility; however, this is not without cost. New Eclipse developers often find the framework to be large and confusing. Determining which parts of the framework they should be using can be a difficult task as Eclipse documentation tends to be either very high-level, focusing on the design of the framework, or low-level, focusing on specific APIs. We have developed a tool called PopCon that provides a bridge between high-level design documentation and low-level API documentation by statically analyzing a framework and several of its clients and providing a ranked list of the relative popularity of its APIs. We have applied PopCon to the Eclipse framework for this challenge to help newbie Eclipse developers identify some of the most relevant APIs for their tasks.},
	keywords = {API popularity, documentation, eclipse, mining software repositories, module, msr challenge, PopCon, popularity},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370787},
	url = {http://doi.acm.org/10.1145/1370750.1370787},
	author = {Holmes, Reid and Walker, Robert J.}
}
@unpublished {flosswp387,
	title = {Promoting the Penguin: Who is Advocating Open Source Software in Commercial Settings?},
	year = {2008},
	month = {March},
	abstract = {Most firms that use or develop software today face the questions of whether and how to engage in open source software (OSS). Yet, little is known about the process of OSS adoption and diffusion within corporations. Guided by the models of Rogers (innovation diffusion) and Davis (Technology Acceptance Model), we develop a theoretical framework of how job function influences individuals? proclivity to support their employers? adoption of OSS and OSS practices. We argue that job function determines an individual?s tasks, and that different tasks are differentially affected by OSS. Our study is based on interviews and a large-scale survey in a multinational corporation. Distinguishing between developers, testers, software architects, project managers, and managers, we find greater engagement in OSS to be favored most strongly by testers. Excepting project managers, developers, despite having the most experience with OSS, are the least favorably disposed to greater corporate OSS engagement. A corporation interested in adopting OSS should thus take into account the job function-related incentives of each individual. More generally, we propose that models predicting IT adoption behavior be extended to account for the ways in which individual adopters interact with the innovation at hand, which will be determined largely by their job functions.},
	author = {Oliver Alexy and Joachim Henkel}
}
@conference {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}
}
@conference {flosswp392,
	title = {Replication of FLOSS Research as eResearch},
	booktitle = {Oxford e-Research Conference 2008},
	year = {2008},
	month = {May},
	abstract = {We are working to introduce the ideas of eResearch to a multi-disciplinary research domain: those researchers examining Free/Libre and Open Source Software (FLOSS) and its development (Howison, Wiggins, \& Crowston, 2008).The first phase of this work focused on building a repository for data on FLOSS teams, FLOSSmole (Howison, Conklin, \& Crowston, 2006), and collaborating with other nascent data repositories in the field. Recently we have begun a second phase, which is to introduce another established principle of eResearch, that of broader collaboration through shared workflows accessing these data repositories. To provide an example of the potential value of this principle, we are replicating seminal FLOSS papers using eResearch approaches. This paper describes research outcomes and lessons learned from translating published literature into eResearch workflows.},
	keywords = {eResearch eScience},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Wiggins-FLOSS-eResearch.pdf},
	author = {Andrea Wiggins and James Howison and Kevin Crowston}
}
@conference {538,
	title = {Social Dynamics of FLOSS Team Communication Across Channels},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {131 - 142},
	publisher = {Springer},
	organization = {Springer},
	chapter = {11},
	abstract = {This paper extends prior investigation into the social dynamics of free and open source (FLOSS) teams by examining the methodological questions arising from research using social network analysis on open source projects. We evaluate the validity of data sampling by examining dynamics of communication centralization, which vary across multiple communication channels. We also introduce a method for intensity-based smoothing in dynamic social network analysis.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_11},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Social\%20Dynamics\%20of\%20Floss.pdf},
	author = {Andrea Wiggins and Howison, James and Kevin Crowston}
}
@inbook {869,
	title = {Towards a Global Research Infrastructure for Multidisciplinary Study of Free/Open Source Software Development},
	booktitle = {Open Source Development, Communities and Quality},
	series = {IFIP International Federation for Information Processing},
	volume = {275},
	year = {2008},
	pages = {143-158},
	publisher = {Springer},
	organization = {Springer},
	address = {Boston},
	author = {Gasser, Les and Walt Scacchi},
	editor = {Russo, B. and Damiani, E. and Hissan, S. and Lundell, B. and Succi, G.}
}
@conference {Herraiz:2008:TSB:1370750.1370786,
	title = {Towards a simplification of the bug report form in eclipse},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {145{\textendash}148},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {We believe that the bug report form of Eclipse contains too many fields, and that for some fields, there are too many options. In this MSR challenge report, we focus in the case of the severity field. That field contains seven different levels of severity. Some of them seem very similar, and it is hard to distinguish among them. Users assign severity, and developers give priority to the reports depending on their severity. However, if users can not distinguish well among the various severity options, they will probably assign different priorities to bugs that require the same priority. We study the mean time to close bugs reported in Eclipse, and how the severity assigned by users affects this time. The results shows that classifying by time to close, there are less clusters of bugs than levels of severity. We therefore conclude that there is a need to make a simpler bug report form.},
	keywords = {bug fixing, bug report, bug tracking system, classification, eclipse, msr challenge, severity},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370786},
	url = {http://doi.acm.org/10.1145/1370750.1370786},
	author = {Herraiz, Israel and Daniel M. German and Jesus M. Gonzalez-Barahona and Gregorio Robles}
}
@conference {540,
	title = {Update Propagation Practices in Highly Reusable Open Source Components},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {159 - 170},
	publisher = {Springer},
	organization = {Springer},
	chapter = {13},
	abstract = {In today{\textquoteright}s business and software arena, more and more companies are adopting open source software. An example of this rising phenomenon is to base software products on highly reusable open source components. In this scenario, the evolution of the software product is coupled with the evolution of the open source component. A common assumption is that component updates are immediately and regularly propagated to the project. This paper investigates this assumption empirically by studying update propagation practices in two popular open source libraries, zlib and FFmpeg. For each library, we analyze various repository sources with information such as bug reports, revision history, and source code. The results of the case studies suggest that update propagation is subject to several technical and non-technical factors including the way the open source library is used, the extent to which updates are documented, and the degree of community involvement. Based on these findings, we propose a set of recommendations that would allow better follow-up of updates and smoother update propagation.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_13},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Update\%20Propagation\%20Practice.pdf},
	author = {Orsila, Heikki and Geldenhuys, Jaco and Ruokonen, Anna and Hammouda, Imed}
}
@conference {560,
	title = {Usability in Company Open Source Software Context - Initial Findings from an Empirical Case Study},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {359 - 365},
	publisher = {Springer},
	organization = {Springer},
	chapter = {33},
	abstract = {In the company open source software (OSS) development context, usability is becoming an important issue due to a growing user population, who is only interested in usable applications, not in their development. Companies try to gain a competitive advantage of OSS by utilizing available components, but the openness is difficult to achieve in the business world with licenses, patents and intellectual property rights. This paper analyses usability and user-interface (UI) development in the company OSS context through an interpretive case study in a software development unit of a large, global corporation. Our initial findings suggest that there is a need for human computer interaction specialists in the OSS context. It is revealed that with the software based on OSS, more time can be spent on usability and UI design. In the company{\textquoteright}s viewpoint, there are still many issues involved in deciding what parts of the product will be open source. Especially UI code may remain closed due to competitive advantage and patents.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Usability\%20in\%20Company\%20Open\%20Source.pdf},
	author = {Iivari, Netta and Hedberg, Henrik and Kirves, Tanja}
}
@conference {Hindle:2008:LCT:1370750.1370773,
	title = {What do large commits tell us?: a taxonomical study of large commits},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {99{\textendash}108},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Research in the mining of software repositories has frequently ignored commits that include a large number of files (we call these large commits). The main goal of this paper is to understand the rationale behind large commits, and if there is anything we can learn from them. To address this goal we performed a case study that included the manual classification of large commits of nine open source projects. The contributions include a taxonomy of large commits, which are grouped according to their intention. We contrast large commits against small commits and show that large commits are more perfective while small commits are more corrective. These large commits provide us with a window on the development practices of maintenance teams.},
	keywords = {boost, bug fixing, egroupware, enlightenment, evolution, firebird, large commits, maintenance, mysql, postgresql, samba, software evolution, source control system, spring},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370773},
	url = {http://doi.acm.org/10.1145/1370750.1370773},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p99-hindle.pdf},
	author = {Hindle, Abram and Daniel M. German and Holt, Ric}
}
@conference {1007,
	title = {Analysis of the Linux Kernel Evolution Using Code Clone Coverage},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {22 - 22},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Most studies of the evolution of software systems are based on the comparison of simple software metrics. In this paper, we present our preliminary investigation of the evolution of the Linux kernel using code-clone analysis and the code-clone coverage metrics. We examined 136 versions of the stable Linux kernel using a distributed extension of the code clone detection tool CCFinder. The result is shown as a heat map.},
	keywords = {ccfinder, clone, cloning, kernel, linux, metrics, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300022.pdf},
	author = {Livieri, Simone and Higo, Yoshiki and Matsushita, Makoto and Inoue, Katsuro}
}
@conference {636,
	title = {Authenticating from multiple authentication sources in a collaborative platform},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {229 - 234},
	publisher = {Springer},
	organization = {Springer},
	chapter = {20},
	abstract = {This paper presents a proposal to address the need for multiple authentication sources for users of collaborative work platforms. The proposed approach, developed for the needs of GET and Picolibre, relies on a generic solution that integrate groupware servers in a Shibboleth infrastructure. We have developed adapters for this integration, that we contributed to the phpGroupware
project. This document should serve as a basis for discussion in order to validate the level of generality of the proposed approach. We hope that this approach can also help maintainers of other collaboration platforms, who want to integrate a park of deployed platforms with external user identification and authentication services, get a better view of solutions available with Shibboleth.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Authenticating\%20from\%20multiple.pdf},
	author = {Quang Vu Dang and Olivier Berger and Christian Bac and Hamet, Beno{\^\i}t}
}
@conference {673,
	title = {Can Knowledge Management be Open Source?},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {59 - 70},
	publisher = {Springer},
	organization = {Springer},
	chapter = {5},
	abstract = {As we move further into a knowledge economy where collaboration and innovation are increasingly central to organisational effectiveness, enterprises need to pay more attention to the informal networks that exist within the organisation. Wikis may provide a more appropriate knowledge management capability and environment to capture tacit knowledge. Where traditional organisational cultures see that knowledge management must be tightly protected, Wikis opt for an open source approach where knowledge is shared and distributed for innovation to continue. This paper aims to explicate more participatory organisational processes of creation, accumulation and maintenance of knowledge. It uses Activity Theory as a framework to describe the components of an activity system where a Wiki is a tool mediating employee-based knowledge management activities and thereby democratising organisational knowledge.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Can\%20Knowledge\%20Management.pdf},
	author = {Pfaff, Charmaine and Hasan, Helen}
}
@conference {622,
	title = {Emergent Decision-Making Practices in Free/Libre Open Source Software (Floss) Development Teams},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {71 - 84},
	publisher = {Springer},
	organization = {Springer},
	chapter = {6},
	abstract = {We seek to identify work practices that make Free/Libre Open Source Software (FLOSS) development teams effective. Particularly important to team effectiveness is decision making. In this paper, we report on an inductive qualitative analysis of 360 decision episodes of six FLOSS development teams. Our analysis revealed diversity in decision-making practices that seem to be related to differences in overall team characteristics and effectiveness.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Emergent\%20Decision-Making.pdf},
	author = {Robert Heckman and Kevin Crowston and Eseryel, U. and Howison, James and Eileen Allen and Li, Qing}
}
@conference {1017,
	title = {Forecasting the Number of Changes in Eclipse Using Time Series Analysis},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {32 - 32},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {In order to predict the number of changes in the following months for the project Eclipse, we have applied a statistical (non-explanatory) model based on time series analysis. We have obtained the monthly number of changes in the CVS repository of Eclipse, using the CVSAnalY tool. The input to our model was the filtered series of the number of changes per month, and the output was the number of changes per month for the next three months. Then we aggregated the results of the three months to obtain the total number of changes in the given period in the challenge.},
	keywords = {change management, cvs, cvsanaly, eclipse, prediction},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.10},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300032.pdf},
	author = {Herraiz, Israel and Jesus M. Gonzalez-Barahona and Gregorio Robles}
}
@article {497,
	title = {The functioning of a free software community: entanglement of three regulation modes - control, autonomous, and distributed},
	journal = {Science Studies},
	number = {2},
	year = {2007},
	abstract = {This paper consider FLOSS communities as ""going concerns"" which necessitate a minimum of order and common, shared, social rules to function. Through an in-depth and diachronic analysis of the Spip project, we present two classical modes of social regulation: a control regulation centred on the product and an autonomous regulation reflecting the differentiated commitments. Our data shows that the meaning, value and legitimacy of contributors{\textquoteright} involvements are defined and rated more collectively, through exchanges, judgments, and evaluations. A third regulation mode, called distributed community regulation and aimed at creating and transforming shared rules that produces recognition and stratification, is then presented.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Science_Studies_02-2007-Demaziere_Horn_Zune.pdf},
	author = {Didier Demazi{\`e}re and Francois Horn and Marc Zune}
}
@conference {1013,
	title = {Impact of the Creation of the Mozilla Foundation in the Activity of Developers},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {28 - 28},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {During 2003, the Mozilla project transitioned from company-promoted (sponsored by AOL) to community-promoted (sponsored by the Mozilla Foundation). What happened to the group of developers during this transition? There was any significant impact on its activity or composition? To answer these questions, we have performed an analysis of the CVS repository of Mozilla, using the CVSAnalY tool, finding little on activity, but dramatic changes in the the composition of the development team.},
	keywords = {cvs, cvsanaly, developers, mining challenge, mozilla, msr challenge, revision history},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.15},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300028.pdf},
	author = {Jesus M. Gonzalez-Barahona and Gregorio Robles and Herraiz, Israel}
}
@article {hoepman2007increased,
	title = {Increased security through open source},
	journal = {Communications of the ACM},
	volume = {50},
	number = {1},
	year = {2007},
	pages = {79{\textendash}83},
	publisher = {ACM},
	abstract = {The last few years have shown a worldwide rise in the attention for, and
actual use of, open source software (OSS), most notably of the operating
system Linux and various applications running on top of it. Various major
companies and governments are adopting OSS. As a result, there are many
publications concerning its advantages and disadvantages. The ongoing discussions
cover a wide range of topics, such as Windows versus Linux, cost
issues, intellectual property rights, development methods, etc. Here we wish
to focus on security issues surrounding OSS. It has become a reasonably
well-established conviction within the computer security community that
publishing designs and protocols contributes to the security of systems built
on them. But should one go all the way and publish source code as well?
That is the fundamental question that we wish to address in this paper.},
	keywords = {security},
	url = {https://arxiv.org/pdf/0801.3924.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/0801.3924.pdf},
	author = {Hoepman, Jaap-Henk and Jacobs, Bart}
}
@conference {663,
	title = {Introduction to Workshops at the Third International Conference on Open Source Systems {\textemdash} OSS 2007},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {369 - 369},
	publisher = {Springer},
	organization = {Springer},
	chapter = {47},
	abstract = {The International Conference on Open Source Systems owes its success to the increasing desire of researchers and academicians to engage in open conversation and sharing with the open source community regarding its{\textquoteright}motivations, products, processes and data. This diverse representation of the growing practical and academic interest in Open Source Systems and its impact on the software engineering community is represented in the five workshops that accompany this year{\textquoteright}s conference. OSS 2007 welcomes these workshops as participants engage, in an informal setting, driven by fundamental academic interests, or by more applied industrial or commercial interests to discuss technical issues, exchange research ideas, and to develop a community in the field of Open Source Software and/or Systems.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_47},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Introduction\%20\%20to\%20Workshops.pdf},
	author = {Hissam, Scott}
}
@article {flosswp1604,
	title = {Motivating job design as a factor in open source governance},
	journal = {J Manage Governance},
	volume = {11},
	number = {2},
	year = {2007},
	month = {May},
	pages = {129{\textendash}137},
	publisher = {Springer Science+Business Media},
	abstract = {Successful open source software (OSS) projects can be considered as examples of how ambitious work results can be achieved in web-based collaboration even when monetary incentives are low or absent. While former explorations of motivational processes in OSS projects primarily focused on person-oriented aspects such as motives, interests, and expected benefits of contributors, job-related factors have been largely neglected. After discussing the limitations of a personoriented focus, a research perspective is suggested that concentrates on job design and work context in OSS based on frameworks from work psychology. A theoretical analysis is presented discussing job characteristics of successful OSS projects as potential explanations of the high motivation of OSS contributors. Compared to a person-oriented perspective, the results of a job-oriented approach might be better transferable to other projects (both OSS and ??closed source?? software development) and provide guidelines for the governance of successful web-based collaboration.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/fulltext.pdf},
	author = {Guido Hertel}
}
@conference {995,
	title = {Open Borders? Immigration in Open Source Projects},
	booktitle = {Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {6 - 6},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Open source software is built by teams of volunteers. Each project has a core team of developers, who have the authority to commit changes to the repository; this team is the elite, committed foundation of the project, selected through a meritocratic process from a larger number of people who participate on the mailing list. Most projects carefully regulate admission of outsiders to full developer privileges; some projects even have formal descriptions of this process. Understanding the factors that influence the "who, how and when" of this process is critical, both for the sustainability of FLOSS projects, and for outside stakeholders who want to gain entry and succeed. In this paper we mount a quantitative case study of the process by which people join FLOSS projects, using data mined from the Apache web server, Postgres, and Python. We develop a theory of open source project joining, and evaluate this theory based on our data.},
	keywords = {apache, core, joining, postgresql, python, team},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300006.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem and Swaminathan, Anand and Hsu, Greta}
}
@article {1390,
	title = {An Open Source Approach to Developing Software in a Small Organization},
	journal = {IEEE Software},
	volume = {24},
	year = {2007},
	month = {01/2007},
	pages = {46 - 53},
	abstract = {This article is part of a special issue on Software Engineering Challenges in Small Software Organizations. The software development approach that developers at Kitware use borrows techniques from agile development and Extreme Programming and emphasizes long-term, ongoing projects. The company has used this approach on open source and closed-source projects in a wide range of sizes},
	keywords = {Cross-platform, Small-business, software engineering, Software testing},
	issn = {0740-7459},
	doi = {10.1109/MS.2007.5},
	author = {Martin, Ken and Hoffman, Bill}
}
@article {flosswp367,
	title = {Promoting the Penguin: Who is Advocating Open Source Software in Commercial Settings?},
	year = {2007},
	month = {August},
	abstract = {Most firms that use or develop software today face the questions of whether and how to engage in open source software. Yet, little is known about the process of OSS adoption and diffusion within corporations. Guided by the theoretical frameworks of Rogers (innovation diffusion) and Davis (Technology Acceptance Model), we develop a model of how job function influences individuals??? proclivity to support their employers??? adoption of OSS and OSS practices. We argue that job function determines which tasks in the software development process are part of an individual???s daily routine, and that different tasks are differentially affected by OSS. Our study is based on interviews with 25 individuals and a large-scale survey distributed to 249 participants in the telecommunications department of a multinational company. The results, although consistent with theoretical considerations, are nevertheless surprising. Distinguishing between developers, software testers, software architects, project managers, and managers, we find greater involvement in OSS activities to be favored most strongly by software testers, followed by software architects and managers. Excepting project managers, developers, despite having the most experience with OSS, are the least favorably disposed to greater corporate engagement in OSS. A corporation interested in adopting OSS and open innovation processes should thus take into account the job function-related incentives of each individual as well as various organizational factors. More generally, we propose that models developed to predict IT adoption behavior be extended to account for the ways in which individual adopters interact with the innovation at hand, which we maintain will be determined largely by their job functions.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Alexy_Henkel_-_Promoting_the_Penguin.pdf},
	author = {Oliver Alexy and Joachim Henkel}
}
@article {flosswp369,
	title = {Putting a Value on Openness: The Effect of Product Source Code Releases on the Market Value of Firms},
	year = {2007},
	month = {October},
	abstract = {This study examines the effect of releasing the source code of commercial software products as open source software on the market value of firms. Using a sample of 30 software companies in the time span from 1 January 1999 to 30 April 2007, I find that market valuation is influenced by investor sentiment???abnormal returns take a curvilinear shape over time???and the business model firms choose for their OSS efforts???non-existence of an explicit revenue model is punished by the capital market. From my findings, I deduce several implications for IT-related event studies and research on open innovation processes.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Alexy_-_Putting_a_Value_on_Openness.pdf},
	author = {Oliver Alexy and Joachim Henkel}
}
@conference {662,
	title = {Quality Specification, Testing and Certification of Bespoken, Open Source and Commercial Off-The-Shelf Systems},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {365 - 366},
	publisher = {Springer},
	organization = {Springer},
	chapter = {46},
	abstract = {The seminar will cover the principles as well as the best practices of software system quality assurance (comprising inspection, verification, validation, black and white box test, measurement and assessment, and the normative quality characteristics) for procedural, object-oriented, aspectoriented and agent-based dependable software. Attendees will exercise proven techniques for goal-directed quality specification, testing, measurement, scaling and assessment for software certification. Assessment of both the software product as well as the software process will be discussed with respect to its relevance for such acceptance assessments. A standardized process model for measurement, assessment and certification of dependable software will be used to make the attendees familiar with this comprehensive assessment procedure and to learn how to embed it into today{\textquoteright}s standardized or non-standardized software processes.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_46},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Quality\%20Specification\%20Testing.pdf},
	author = {Hausen, Hans-Ludwig}
}
@conference {883,
	title = {The Quest for Quality Tags.},
	booktitle = {Conference on Supporting Group Work},
	year = {2007},
	author = {Shilad Sen and Harper, F. Maxwell and Adam LaPitz and John Riedl}
}
@conference {884,
	title = {Recommenders Everywhere: The WikiLens Community-Maintained Recommender System},
	booktitle = {Wikisym 2007},
	year = {2007},
	address = {Montreal, Quebec, Canada},
	isbn = {978-1-59593-861-9},
	author = {Dan Frankowski and Shyong K. Lam and Shilad Sen and Harper, F. Maxwell and Scott Yilek and Michael Cassano and John Riedl}
}
@conference {647,
	title = {Release Management in Free Software Projects: Practices and Problems},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {295 - 300},
	publisher = {Springer},
	organization = {Springer},
	chapter = {31},
	abstract = {Release management plays an important role in every software project since it is concerned with the delivery of a high quality product to end-users. This paper explores release practices employed by volunteer free software projects and shows problems that occur. A challenge that has been identified is the difficulty of coordinating a distributed team of volunteers in order to align their work for a release.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Release\%20Management\%20in\%20Free\%20Software.pdf},
	author = {Martin Michlmayr and Hunt, Francis and Probert, David}
}
@conference {1004,
	title = {Release Pattern Discovery via Partitioning: Methodology and Case Study},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {19 - 19},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {The development of Open Source systems produces a variety of software artifacts such as source code, version control records, bug reports, and email discussions. Since the development is distributed across different tool environments and developer practices, any analysis of project behavior must be inferred from whatever common artifacts happen to be available. In this paper, we propose an approach to characterizing a project{\textquoteright}s behavior around the time of major and minor releases; we do this by partitioning the observed activities, such as artifact check-ins, around the dates of major and minor releases, and then look for recognizable patterns. We validate this approach by means of a case study on the MySQL database system; in this case study, we found patterns which suggested MySQL was behaving consistently within itself. These patterns included testing and documenting that took place more before a release than after and that the rate of source code changes dipped around release time.},
	keywords = {bitkeeper, bt2csv, cvs, evolution, mysql, releases, revision history, scm, softchange, version control},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.28},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300019.pdf},
	author = {Hindle, Abram and Godfrey, Michael W. and Holt, Richard C.}
}
@article {86,
	title = {The role of face-to-face meetings in technology-supported self-organizing distributed teams},
	journal = {Ieee Transactions on Professional Communication},
	volume = {50},
	number = {3},
	year = {2007},
	note = {Times Cited: 0},
	pages = {185-203},
	abstract = {We examine the role of face-to-face meetings in the context of technology-supported self-organizing distributed (or virtual teams), specifically Free/Libre Open Source Software (FLOSS) development teams. Based on a qualitative inductive analysis of data from interviews and observations at FLOSS conferences, we identify a variety of settings in which developers meet face-to-face, and we point out the activities performed in these settings and the benefits obtained. Contrary to conventional wisdom about distributed teams, FLOSS developers generally do not meet face-to-face until the project is well under way. An additional benefit offace-to-face meetings is time away from a regular job and speed of interaction for certain kinds of tasks.},
	author = {Kevin Crowston and James Howison and Chengetai Masango and Eseryel, U. Yeliz}
}
@article {flosswp405,
	title = {Self-organization of teams for free/libre open source software development},
	journal = {Information and Software Technology Journal},
	volume = {49},
	number = {564-575},
	year = {2007},
	note = {"First, the data from these projects that we needed for analysis had to be publicly available (ruling out projects that limit access to their email lists or trackers). Second, we chose the projects that had more than 7 members"..."projects that have attracted numerous developers beyond the initial project founders, are continuing to release software, have numerous downloads and have an active user community that provides feedback"
"3 FLOSS projects were selected for analysis, namely Gaim, eGroupWare and Compiere ERP."

all had sourceforge hosting

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

Analysis: "For this project, we inductively content-analyzed developer email interactions to identify the task assignment mechanisms used in the process. We coded each instance of task assignment identified on three dimensions: who assigned the task, to whom, and how"
},
	abstract = {This paper provides empirical evidence about how free/libre open source software development teams self-organize their work. Following a case study methodology, we examined developer interaction data from three active and successful FLOSS projects using qualitative research methods, specifically inductive content analysis, to identify the task-assignment mechanisms used by the participants. We found that "self-assignment" was the most common mechanism across three FLOSS projects. This mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research.},
	keywords = {case study, compiere, coordination, DESIGN, distributed teams, egroupware, email, email archives, forum, free/libre open source software development, gaim, INTERNET, mailing list, metadata, qualitative research methods, self-organizing teams, sourceforge, SYSTEMS, task assignment, WORK},
	attachments = {https://flosshub.org/sites/flosshub.org/files/task_assignment_final.pdf},
	author = {Kevin Crowston and Li, Qing and Kangning Wei and Eseryel, U. Yeliz and Howison, James}
}
@conference {875,
	title = {Social Comparisons to Motivate Contributions to an Online Community.},
	booktitle = {Persuasive Technology},
	year = {2007},
	month = {26/04/2007},
	address = {Palo Alto, CA},
	author = {F. Harper and X. Li and Y. Chen and J. Konstan}
}
@article {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}
}
@conference {874,
	title = {Talk Amongst Yourselves: Inviting Users to Participate in Online Conversations.},
	booktitle = {International Conference on Intelligent User Interfaces  },
	series = {Proceedings of the 12th international conference on Intelligent user interfaces},
	year = {2007},
	month = {28/01/2007},
	pages = {62-71},
	publisher = {ACM},
	organization = {ACM},
	address = {Honolulu, Hawaii},
	isbn = {1-59593-481-2},
	author = {F. Harper and D. Frankowski and Drenner, S. and Y. Ren and S. Kiesler and Terveen, L. and Kraut, R. and Riedl, J.}
}
@conference {1006,
	title = {Towards a Theoretical Model for Software Growth},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {21 - 21},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Software growth (and more broadly, software evolution) is usually considered in terms of size or complexity of source code. However in different studies, usually different metrics are used, which make it difficult to compare approaches and results. In addition, not all metrics are equally easy to calculate for a given source code, which leads to the question of which one is the easiest to calculate without losing too much information. To address both issues, in this paper present a comprehensive study, based on the analysis of about 700,000 C source code files, calculating several size and complexity metrics for all of them. For this sample, we have found double Pareto statistical distributions for all metrics considered, and a high correlation between any two of them. This would imply that any model addressing software growth should produce this Pareto distributions, and that analysis based on any of the considered metrics should show a similar pattern, provided the sample of files considered is large enough.},
	keywords = {C, complexity, evolution, freebsd, growth, halstead, lines of code, loc, mccabe, metrics, scm, size, sloc, sloccount, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300021.pdf},
	author = {Herraiz, Israel and Jesus M. Gonzalez-Barahona and Gregorio Robles}
}
@conference {1010,
	title = {Using Software Repositories to Investigate Socio-technical Congruence in Development Projects},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {25 - 25},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {We propose a quantitative measure of socio-technical congruence as an indicator of the performance of an organization in carrying out a software development project. We show how the information necessary to implement that measure can be mined from commonly used software repositories, and we describe how socio-technical congruence can be computed based on that information.},
	keywords = {developers, graph, scm, social networks, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300025.pdf},
	author = {Valetto, Giuseppe and Helander, Mary and Ehrlich, Kate and Chulani, Sunita and Wegman, Mark and Williams, Clay}
}
@article {flosswp334,
	title = {Voluntary Engagement in an Open Web-based Encyclopedia: Wikipedians, and Why They Do It},
	year = {2007},
	month = {January},
	abstract = {The online encyclopedia Wikipedia can be considered as a highly successful Open Content project, written and maintained completely by volunteers. Little is known, however, about the motives and interests of these volunteers. Results from an online survey among 106 contributors to the German Wikipedia project are presented. As potential predictors of contributors??? engagement and satisfaction, both motives derived from social sciences (e.g., costs-benefits, valence of the Wikipedia goals, identification with Wikipedia, etc.) as well as perceived task characteristics (e.g., task significance, autonomy, skill variety, etc.) were measured. The results reveal that satisfaction ratings of contributors are determined by perceived benefits, identification with the Wikipedia community, and task characteristics. Contributors??? engagement (e.g., hours per week) was particularly determined by their tolerance for opportunity costs and the experienced characteristics of their tasks, the latter effect being partially mediated by intrinsic motivation. Most relevant task characteristics both for contributors??? engagement and satisfaction were autonomy, task significance, and skill variety. Additional motives reported by Wikipedia contributors suggest the importance of generativity.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Schroer_Hertel_Wikipedia_Motivation.pdf},
	author = {Joachim Schroer and Guido Hertel}
}
@conference {1008,
	title = {What Can OSS Mailing Lists Tell Us? A Preliminary Psychometric Text Analysis of the Apache Developer Mailing List},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {23 - 23},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Developer mailing lists are a rich source of information about Open Source Software (OSS) development. The unstructured nature of email makes extracting information difficult. We use a psychometrically-based linguistic analysis tool, the LIWC, to examine the Apache httpd server developer mailing list. We conduct three preliminary experiments to assess the appropriateness of this tool for information extraction from mailing lists. First, using LIWC dimensions that are correlated with the big five personality traits, we assess the personality of four top developers against a baseline for the entire mailing list. The two developers that were responsible for the major Apache releases had similar personalities. Their personalities were different from the baseline and the other developers. Second, the first and last 50 emails for two top developers who have left the project are examined. The analysis shows promise in understanding why developers join and leave a project. Third, we examine word usage on the mailing list for two major Apache releases. The differences may reflect the relative success of each release.},
	keywords = {apache, developers, email, joining, liwc, mailing lists, personality},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.35},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300023.pdf},
	author = {Peter C. Rigby and Hassan, Ahmed E.}
}
@article {120,
	title = {Applying Social Network Analysis Techniques to Community-Driven Libre Software Projects},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	abstract = {Source code management repositories of large, long-lived libre (free, open source) software projects can be a source of valuable data about the organizational structure, evolution, and knowledge exchange in the corresponding development communities. Unfortunately, the sheer volume of the available information renders it almost unusable without applying methodologies which highlight the relevant information for a given aspect of the project. Such methodology is proposed in this article, based on well known concepts from the social networks analysis field, which can be used to study the relationships among developers and how they collaborate in different parts of a project. It is also applied to data mined from some well known projects (Apache, GNOME, and KDE), focusing on the characterization of their collaboration network architecture. These cases help to understand the potentials of the methodology and how it is applied, but also shows some relevant results which open new paths in the understanding of the informal organization of libre software development communities.},
	keywords = {apache, conway{\textquoteright}s law, cvs, gnome, kde, scm, social network analysis, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/06_Lopez_ijitwe_sna.pdf},
	author = {L{\'o}pez-Fern{\'a}ndez, L. and Gregorio Robles and Jesus M. Gonzalez-Barahona and Herraiz, I.}
}
@article {85,
	title = {Assessing the health of open source communities},
	journal = {Computer},
	volume = {39},
	number = {5},
	year = {2006},
	note = {Times Cited: 0},
	pages = {89-91},
	author = {Kevin Crowston and James Howison}
}
@conference {Gurbani:2006:CSC:1134285.1134352,
	title = {A case study of a corporate open source development model},
	booktitle = {Proceedings of the 28th international conference on Software engineering},
	series = {ICSE {\textquoteright}06},
	year = {2006},
	pages = {472{\textendash}481},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source practices and tools have proven to be highly effective for overcoming the many problems of geographically distributed software development. We know relatively little, however, about the range of settings in which they work. In particular, can corporations use the open source development model effectively for software projects inside the corporate domain? Or are these tools and practices incompatible with development environments, management practices, and market-driven schedule and feature decisions typical of a commercial software house? We present a case study of open source software development methodology adopted by a significant commercial software project in the telecommunications domain. We extract a number of lessons learned from the experience, and identify open research questions.},
	keywords = {architecture, case study, open source, session initiation protocol, software development, vkg},
	isbn = {1-59593-375-1},
	doi = {10.1145/1134285.1134352},
	url = {http://doi.acm.org/10.1145/1134285.1134352},
	author = {Gurbani, Vijay K. and Garvert, Anita and Herbsleb, James D.}
}
@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 {Herraiz:2006:CSN:1116163.1116405,
	title = {Comparison Between SLOCs and Number of Files As Size Metrics for Software Evolution Analysis},
	booktitle = {Proceedings of the Conference on Software Maintenance and Reengineering},
	series = {CSMR {\textquoteright}06},
	year = {2006},
	pages = {206{\textendash}213},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	keywords = {empirical studies, libre software, metrics, software evolution},
	isbn = {0-7695-2536-9},
	url = {http://dl.acm.org/citation.cfm?id=1116163.1116405},
	author = {Herraiz, Israel and Gregorio Robles and Gonzalez-Barahon, Jes us M.}
}
@article {90,
	title = {Core and periphery in Free/Libre and Open Source software team communications},
	journal = {Proceedings of the 39th Annual Hawaii International Conference on System Sciences-Volume 06},
	year = {2006},
	abstract = {The concept of the core group of developers is important and often discussed in empirical studies of FLOSS projects. This paper examines the question, "how does one empirically distinguish the core?" Being able to identify the core members of a FLOSS development project is important because many of the processes necessary for successful projects likely involve core members differently than peripheral members, so analyses that mix the two groups will likely yield invalid results. 

We compare 3 analysis approaches to identify the core: the named list of developers, a Bradford{\textquoteright}s law analysis that takes as the core the most frequent contributors and a social network analysis of the interaction pattern that identifies the core in a core-and-periphery structure. We apply these measures to the interactions around bug fixing for 116 SourceForge projects. The 3 techniques identify different individuals as core members; examination of which individuals are identified leads to suggestions for refining the measures. All 3 measures though suggest that the core of FLOSS projects is a small fraction of the total number of contributors.},
	keywords = {bug fixing, contributions, contributors, core, developers, social network analysis, sourceforge, team},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and Howison, James}
}
@proceedings {107,
	title = {Emergent decision-making practices in technology-supported self-organizing distributed teams},
	year = {2006},
	address = {Milwaukee, WI, 10{\textendash}13 Dec},
	author = {Robert Heckman and Kevin Crowston and Li, Qing and Eileen Allen and Eseryel, U. Yeliz and James Howison and Wei, Kangning}
}
@conference {flosswp406,
	title = {Emergent Decision-making Practices in Technology-Supported Self-Organizing Distributed Teams},
	booktitle = {Twenty Seventh International Conference on Information Systems},
	year = {2006},
	pages = {1{\textendash}12},
	abstract = {We seek to identify work practices that make technology-supported self-organizing distributed (or virtual) teams (TSSODT for short) effective in producing outputs satisfactory to their sponsors, meeting the needs of their members and continuing to function. A particularly important practice for team effectiveness is decision making: are the right decisions made at the right time to get the work done in a way that satisfies team sponsors, keeps contributors happy and engaged, and enables continued team success? In this research-in-progress paper, we report on an inductive qualitative analysis of 120 decision episodes taken by 2 Free/libre Open Source Software development teams (the completed paper will include 360 episodes from 6 teams). Our analysis revealed differences in the performance of the two teams that seems to be related to differences in overall project effectiveness.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/decision_making_practices.pdf},
	author = {Robert Heckman and Kevin Crowston and Li, Qing and Eileen Allen and Eseryel, U. Yeliz and James Howison}
}
@conference {Jiang:2006:EEC:1137983.1138030,
	title = {Examining the evolution of code comments in PostgreSQL},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {179{\textendash}180},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {It is common, especially in large software systems, for developers to change code without updating its associated comments due to their unfamiliarity with the code or due to time constraints. This is a potential problem since outdated comments may confuse or mislead developers who perform future development. Using data recovered from CVS, we study the evolution of code comments in the PostgreSQL project. Our study reveals that over time the percentage of commented functions remains constant except for early fluctuation due to the commenting style of a particular active developer.},
	keywords = {code comments, comments, cvs, evolution, functions, maintenance, mining challenge, msr challenge, postgresql, software evolution, software maintenance, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138030},
	url = {http://doi.acm.org/10.1145/1137983.1138030},
	attachments = {https://flosshub.org/sites/flosshub.org/files/179ExaminingTheEvolution.pdf},
	author = {Zhen Ming Jiang and Hassan, Ahmed E.}
}
@conference {690,
	title = {Exploring the potential of OSS in Air Traffic Management},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {173 - 179},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper introduces a project that aims at defining an Open Source Software (OSS) policy in the field of Air Traffic Management (ATM). In order to develop such a policy, we chose to investigate first a set of predictive hypotheses. Our four initial hypotheses were presented, refined and discussed in bi-lateral meetings with experts in the ATM field and in several conferences and workshops with OSS experts. At a roundtable, jointly organized by CALIBRE and EUROCONTROL, we confronted early open source experiences and insights in the ATM domain with experiences and knowledge from a panel of OSS experts and practitioners from academia and industry. The revised initial hypotheses are presented using a fixed format that should facilitate further evolution of these hypotheses.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_17},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Exploring\%20the\%20potential\%20of\%20OSS.pdf},
	author = {Hardy, Jean-Luc and Bourgois, Marc}
}
@article {109,
	title = {FLOSSmole: A Collaborative Repository for FLOSS Research Data and Analyses},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	pages = {17-26},
	author = {James Howison and Conklin, Megan and Kevin Crowston}
}
@conference {41,
	title = {The FLOSSWALD information system on free and open source software},
	booktitle = {9th International Workshop on Learning Software Organizations},
	year = {2006},
	note = {"Using these [FLOSSmole] data we intend to map the respective projects
to their developed software and thus extend the already
existing cases with new attributes or create new we cases
where necessary."

"Our first step
will be to evaluate the data provided by the Debian project
and the FLOSSmole project and design a knowledge base
and case structure to flexibly work with them."},
	month = {10/2006},
	abstract = {We propose the implementation of an intelligent information system on free and open source software. This system will consist of a case-based reasoning (CBR) system and several machine learning modules to maintain the knowledge base and train the CBR system thus enhancing its performance. Our knowledge base will include data on free and open source software provided by the Debian project, the FLOSSmole project, and other public free and open source software directories. We plan to enrich these data by learning additional information such as concepts and different similarities. With this knowledge base, we hope to be able to create an information system that will be capable of answering queries based on precise as well as vague criteria and give intelligent recommendations on software based on the preferences of the user.},
	keywords = {debian, flossmole},
	attachments = {https://flosshub.org/sites/flosshub.org/files/flosswald.pdf},
	author = {Reichle, M. and Hanft, A.}
}
@conference {691,
	title = {From Individual Contribution to Group Learning},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {77 - 90},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Open Source Software (OSS) groups experience many benefits and challenges with respect to the core group{\textquoteright}s effectiveness. In order to capitalize on the benefits and minimize the challenges, OSS groups must learn not only on the individual level, but also on the group level. OSS groups learn by integrating individual contributions into the group{\textquoteright}s product and processes.
This paper reports on the characteristics of the learning process in OSS groups. The study utilized an embedded single case study design that observed and analyzed group learning processes in the Apache Web server OSS project. The study used learning opportunity episodes (LOE) as the embedded unit of analysis and developed and utilized three content analytic schemes to describe the characteristics of the learning process and the factors affecting this process.
},
	keywords = {apache, case study},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_8},
	attachments = {https://flosshub.org/sites/flosshub.org/files/From\%20Individual\%20Contribution\%20to\%20Group\%20Learning.pdf},
	author = {Hala Annabi and Kevin Crowston and Robert Heckman}
}
@article {Crowston:2006a,
	title = {Hierarchy and centralization in Free and Open Source Software team communications},
	journal = {Knowledge, Technology \& Policy},
	volume = {18},
	number = {4},
	year = {2006},
	pages = {65{\textendash}85},
	abstract = {Free/Libre Open Source Software (FLOSS) development teams provide an interesting and convenient setting for studying distributed work. We begin by answering perhaps the most basic question: what is the social structure of these teams? Based on a social network analysis of interactions represented in 62,110 bug reports from 122 large and active projects, we find that some OSS teams are highly centralized, but contrary to expectation, others are not. Projects are mostly quite hierarchical on four measures of hierarchy, consistent with past research but contrary to the popular image of these projects. Furthermore, we find that the level of centralization is negatively correlated with project size, suggesting that larger projects become more modular. The paper makes a further methodological contribution by identifying appropriate analysis approaches for interaction data. We conclude by sketching directions for future research.},
	keywords = {apache, bug fixing, bug tracking, FLOSS, project success, savannah, social network analysis, sourceforge, team size, teams},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHierarchyAndCentralization.pdf},
	author = {Kevin Crowston and Howison, James}
}
@article {flosswp302,
	title = {How free software developers work. The mobilization of "distant communities"},
	year = {2006},
	month = {January},
	abstract = {The work of free software developers is an individual activity carried out in extremely heterogeneous conditions and a collective action with original production methods. We propose to analyze this work starting with the paradoxical notion of a "distant community", that aims to illustrate the tension between, on the one hand, the strength of the sense of belonging to a specific world identifiable in the discourse of the participants and, on the other hand, the distances that separate the contributors in terms of relationships, status, and background. In doing this the aim is to produce a description, necessarily plural, of the different forms of "distant communities" that enables the production of goods in unique social and organizational conditions. More generally speaking, this notion points to methods of coordination that combine two forms of collective action that are usually contrary and antagonistic: a communitarian form based on the subjective feeling of belonging to the same community and a form of partnership based on the coordination of common interests and sharing of objectives (T??nnies, 1887, Weber, 1921). At first, we examine the ways the individual participants organize themselves in order to contribute to a project and we focus on the forms of cooperation and coordination used to deal with the constraints of efficiency and quality associated with the distribution of a product. Secondly, we look at the other side of the coin and examine the ways individual participants take action and we underline the mechanisms of commitment and participation that account for their contribution to the production of free software. These two dimensions, that in our opinion are inseparable, are explored through a survey carried out with free software developers.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CLES_DDFHNJ_juin_2006__vm_Anglais.pdf},
	author = {Didier Demazi{\`e}re and Francois Horn and Nicolas Jullien}
}
@proceedings {71,
	title = {Identification of coordination requirements: Implications for the design of collaboration and awareness tools},
	year = {2006},
	month = {November},
	address = {Banff, Alberta, Canada},
	keywords = {modularity},
	author = {Cataldo, Marcelo and Wagstrom, Patrick A. and Herbsleb, J. D. and Carley, Kathleen M.}
}
@conference {693,
	title = {Impact of Social Ties on Open Source Project Team Formation},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	note = {"we randomly selected 1030 new projects that were registered between X and X in 2005. A web crawler downloaded the HTML files containing project summary data and developer information on the date of registration."},
	month = {2006///},
	pages = {307 - 317},
	publisher = {Springer},
	organization = {Springer},
	abstract = {In this paper, we empirically examined the role of social ties in OSSD team formation and developer joining behavior. We find that the existence and the amount of prior social relations in the network do increase the probability of an OSS project to attract more developers. Interestingly, for projects without preexisting social ties, developers tend to join the project initiated by people with less OSSD experience. This research fills a gap in the open source literature by conducting an empirical investigation of the role of social relations on project team formation behavior. Furthermore, the adoption of social network analysis, which has received little attention in the OSS literature, can yield some interesting results on the interactions among OSS developers.
},
	keywords = {developers, metadata, social network analysis, sourceforge},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Impact\%20of\%20Social\%20Ties\%20on\%20Open\%20Source\%20Project.pdf},
	author = {Hahn, Jungpil and Moon, Jae and Zhang, Chen}
}
@article {Crowston:2006,
	title = {Information systems success in Free and Open Source Software development: Theory and measures},
	journal = {Software Process{\textendash}Improvement and Practice},
	volume = {11},
	number = {2},
	year = {2006},
	note = {"we continue our examination of success measures using data from Sourceforge..."
"e chose the number of developers (assessed from the records of the project and from bug fixing logs), bug-fixing time, and popularity (assessed from the number of downloads and viewings of project Web pages, and inclusion in distributions). These measures were chosen because they span the reconsidered FLOSS development process discussed above, including inputs (number of developers), process (speed of bug fixing) and output (popularity)."},
	pages = {123{\textendash}148},
	abstract = {Information systems success is one of the most widely used dependent variables in information systems (IS) research, but research on Free/Libre and Open Source software (FLOSS) often fails to appropriately conceptualize this important concept. In this paper, we reconsider what success means within a FLOSS context. We first review existing models of IS success and success variables used in FLOSS research and assess them for their usefulness, practicality and fit to the FLOSS context. Then, drawing on a theoretical model of group effectiveness in the FLOSS development process, as well as an online discussion group with developers, we present additional concepts that are central to an appropriate understanding of success for FLOSS. In order to examine the practicality and validity of this conceptual scheme, the second half of our paper presents an empirical study that demonstrates its operationalization of the chosen measures and assesses their internal validity. We use data from SourceForge to measure the project{\textquoteright}s effectiveness in team building, the speed of the project at responding to bug reports and the project{\textquoteright}s popularity. We conclude by discussing the implications of this study for our proposed extension of IS success in the context of FLOSS development and highlight future directions for research.},
	keywords = {bug fixing, developers, downloads, FLOSS, flossmole, page views, popularity, project success, size, sourceforge, success, team size},
	doi = {10.1002/spip.259},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHowisonAnnabi2006.pdf},
	author = {Kevin Crowston and Howison, James and Hala Annabi}
}
@conference {Askari:2006:ITE:1137983.1138013,
	title = {Information theoretic evaluation of change prediction models for large-scale software},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {126{\textendash}132},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper, we analyze the data extracted from several open source software repositories. We observe that the change data follows a Zipf distribution. Based on the extracted data, we then develop three probabilistic models to predict which files will have changes or bugs. The first model is Maximum Likelihood Estimation (MLE), which simply counts the number of events, i.e., changes or bugs, that happen to each file and normalizes the counts to compute a probability distribution. The second model is Reflexive Exponential Decay (RED) in which we postulate that the predictive rate of modification in a file is incremented by any modification to that file and decays exponentially. The third model is called RED-Co-Change. With each modification to a given file, the RED-Co-Change model not only increments its predictive rate, but also increments the rate for other files that are related to the given file through previous co-changes. We then present an information-theoretic approach to evaluate the performance of different prediction models. In this approach, the closeness of model distribution to the actual unknown probability distribution of the system is measured using cross entropy. We evaluate our prediction models empirically using the proposed information-theoretic approach for six large open source systems. Based on this evaluation, we observe that of our three prediction models, the RED-Co-Change model predicts the distribution that is closest to the actual distribution for all the studied systems.},
	keywords = {bugs, change analysis, cvs, evaluation approach, file, freebsd, information theory, kde, koffice, log files, netbsd, openbsd, postgresql, prediction, prediction models, scm, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138013},
	url = {http://doi.acm.org/10.1145/1137983.1138013},
	attachments = {https://flosshub.org/sites/flosshub.org/files/126InformationTheoretic.pdf},
	author = {Askari, Mina and Holt, Ric}
}
@conference {888,
	title = {Insert Movie Reference Here: A System to Bridge Conversation and Item-Oriented Web Sites},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2006},
	month = {22/04/2006},
	pages = {951-954},
	publisher = {ACM},
	organization = {ACM},
	isbn = {1-59593-372-7},
	author = {Sara Drenner and Max Harper and Dan Frankowski and John Riedl and Loren Terveen}
}
@article {1232,
	title = {Integration of libre software applications to create a collaborative work platform for researchers at GET},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	month = {07/2006},
	pages = {1-16},
	publisher = {IGI Global},
	abstract = {Libre software provides powerful applications ready to be integrated for the build-up of platforms for internal use in organizations. We describe the architecture of the collaborative work platform which we have integrated, designed for researchers at GET. We present the elements we have learned during this project in particular with respect to contribution to external libre projects, in order to better ensure the maintainability of the internal applications, and to phpGroupware as a framework for specific applications development.},
	keywords = {collaborative work environment, contribution, free software, groupware, in-house applications, libre software, open source software, OpenLDAP, phpGroupware, PicoLibre, ProGET, Sympa, TWiki, WebDAV, wiki},
	author = {Olivier Berger and Christian Bac and Benoit Hamet}
}
@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}
}
@article {111,
	title = {Social dynamics of free and open source team communications},
	journal = {Proceedings of the IFIP 2nd International Conference on Open Source Software, Lake Como, Italy},
	year = {2006},
	author = {James Howison and Inoue, K. and Kevin Crowston}
}
@conference {708,
	title = {Social dynamics of free and open source team communications},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {06/2006},
	pages = {319 - 330},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper furthers inquiry into the social structure of free and open source software (FLOSS) teams by undertaking social network analysis across time. Contrary to expectations, we confirmed earlier findings of a wide distribution of centralizations even when examining the networks over time. The paper also provides empirical evidence that while change at the center of FLOSS projects is relatively uncommon, participation across the project communities is highly skewed, with many participants appearing for only one period. Surprisingly, large project teams are not more likely to undergo change at their centers.
},
	keywords = {bug fixing, bug reports, bug tracker, bug tracking, bugs, communications, Dynamic social networks, FLOSS teams, Human Factors, social network analysis, software development, sourceforge},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_32},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Social\%20dynamics\%20of\%20free\%20and\%20open\%20source\%20team.pdf},
	author = {Howison, James and Inoue, Keisuke and Kevin Crowston}
}
@unpublished {flosswp404,
	title = {A structurational perspective on leadership in technology-supported self-organizing small groups},
	year = {2006},
	month = {October},
	publisher = {Syracuse University School of Information Studies},
	type = {Working Paper},
	abstract = {In this conceptual paper, we present a structuration-based theory of leadership behaviours in virtual teams, that is to say, in self-organizing technology-supported small groups such as Free/Libre Open Source Software development teams. Such teams are often composed of members of relatively equal status or who are so disparate in background that formal organizational status seems irrelevant, reducing the usual leadership cues provided by organizational status and title. Building on behavioural leadership theory and structuration theory, we present a two-order theory of leadership. It describes four classes of first-order leadership behaviours (task coordination, substantive task contribution, group maintenance, and boundary spanning) and defines second-order leadership as behaviour that influences changes in the structure that guides group action. Specifically, we suggest that second-order leadership behaviours are those that build structures of signification in the form of interpretive schema, structures of domination in the form of role structures and structures of legitimation in the form of rules and norms. We argue that second-order leadership is enabled by first-order leadership, is therefore action embedded, and is grounded in processes that define the social identity of the group. We propose that effective teams will exhibit a paradoxical combination of shared, distributed first-order leadership complemented by strong, concentrated, and centralized second-order leadership. We conclude by suggesting future research that might be conducted to test and further elaborate our theory.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHeckmanMisiolek.pdf},
	author = {Kevin Crowston and Robert Heckman and Nora Misiolek}
}
@conference {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}
}
@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}
}
@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 {Anvik:2006:FTB:1134285.1134336,
	title = {Who should fix this bug?},
	booktitle = {Proceedings of the 28th international conference on Software engineering},
	series = {ICSE {\textquoteright}06},
	year = {2006},
	pages = {361{\textendash}370},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source development projects typically support an open bug repository to which both developers and users can report bugs. The reports that appear in this repository must be triaged to determine if the report is one which requires attention and if it is, which developer will be assigned the responsibility of resolving the report. Large open source developments are burdened by the rate at which new bug reports appear in the bug repository. In this paper, we present a semi-automated approach intended to ease one part of this process, the assignment of reports to a developer. Our approach applies a machine learning algorithm to the open bug repository to learn the kinds of reports each developer resolves. When a new report arrives, the classifier produced by the machine learning technique suggests a small number of developers suitable to resolve the report. With this approach, we have reached precision levels of 57\% and 64\% on the Eclipse and Firefox development projects respectively. We have also applied our approach to the gcc open source development with less positive results. We describe the conditions under which the approach is applicable and also report on the lessons we learned about applying machine learning to repositories used in open source development.},
	keywords = {bug fixing, bug report, bug report assignment, bug triage, eclipse, Firefox, gcc, issue tracking, machine learning, problem tracking},
	isbn = {1-59593-375-1},
	doi = {10.1145/1134285.1134336},
	url = {http://doi.acm.org/10.1145/1134285.1134336},
	author = {Anvik, John and Hiew, Lyndon and Murphy, Gail C.}
}
@conference {78,
	title = {Collaboration Using OSSmole: A repository of FLOSS data and analyses},
	booktitle = {Symposium on Mining Software Repositories},
	year = {2005},
	month = {17 May},
	address = {St. Louis},
	author = {Conklin, Megan and James Howison and Kevin Crowston}
}
@proceedings {89,
	title = {Coordination of Free/Libre Open Source Software development},
	year = {2005},
	note = {"The data used for the study were interactions on the main developer communication venue, either a developer mailing list or online forum"
sourceforge
},
	address = {Las Vegas, NV, USA},
	abstract = {The apparent success of free/libre open source software (FLOSS) development projects such as Linux, Apache, and many others has raised the question, what lessons from FLOSS development can be transferred to mainstream software development? In this paper, we use coordination theory to analyze coordination mechanisms in FLOSS development and compare our analysis with existing literature on coordination in proprietary software development. We examined developer interaction data from three active and successful FLOSS projects and used content analysis to identify the coordination mechanisms used by the participants. We found that there were similarities between the FLOSS groups and the reported practices of the proprietary project in the coordination mechanisms used to manage task-task dependencies. However, we found clear differences in the coordination mechanisms used to manage task-actor dependencies. While published descriptions of proprietary software development involved an elaborate system to locate the developer who owned the relevant piece of code, we found that {\textquotedblleft}self-assignment{\textquotedblright} was the most common mechanism across three FLOSS projects. This coordination mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research.},
	keywords = {case study, compiere, coordination, egroupware, email, email archives, FLOSS, gaim, mailing list},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonWeiLiEseryelHowison.pdf},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and Eseryel, U. Yeliz and Howison, James}
}
@conference {796,
	title = {Development-oriented Open Source eLearning Tool Evaluation: the Edukalibre Approach},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {341-344},
	author = {Botturi, Luca and Chris Tebb and Vania Dimitrova and Drew Withworth and Julika Matravers and Jutta Geldermann and Isabelle Hubert}
}
@proceedings {1517,
	title = {Digesting Virtual {\textquotedblleft}Geek{\textquotedblright} Culture: The Summarization of Technical Internet Relay Chats},
	year = {2005},
	month = {06/2005},
	pages = {298-305},
	address = {Ann Arbor, MI, USA},
	abstract = {This paper describes a summarization system for technical chats and emails on the Linux kernel. To reflect the complexity and sophistication of the discussions, they are clustered according to subtopic structure on the sub-message level, and immediate responding pairs are identified through machine learning methods. A resulting summary consists of one or more mini-summaries, each on a subtopic from the discussion.},
	keywords = {computational linguistics, irc, linux, summarizing},
	url = {http://acl.ldc.upenn.edu/P/P05/P05-1037.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/P05-1037.pdf},
	author = {Liang Zhou and Edouard Hovy}
}
@conference {902,
	title = {An Economic Model of User Rating in an Online Recommender System},
	booktitle = {10th International Conference on User Modeling},
	year = {2005},
	address = {Edinburgh, UK},
	author = {F.M. Harper and X. Li and Y. Chen and Konstan, J.A.}
}
@conference {Robles05anempirical,
	title = {An empirical approach to Software Archaeology},
	booktitle = {In: Poster Proceedings of the International Conference on Software Maintenance},
	year = {2005},
	pages = {47{\textendash}50},
	abstract = {The term {\textquotedblleft}software archaeology {\textquotedblright} provides a useful metaphor of the tasks that a software developer has to face when performing maintenance on large software projects. The source code of a program at any point in time is the result of many different changes performed in the past, usually by several people, which can be tracked when a version control system is used. We have designed a methodology for analyzing with detail the age of the source code in such cases, and have applied it to several large software projects. As a part of the methodology, we define a set of indexes which can help to characterize the history of a software system, and discuss how those could be used to estimate its past and future maintenance. We also show how our approach to software archaeology is simple both conceptually and computationally, but still very powerful at uncovering useful information.},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Herraiz, Israel}
}
@article {130,
	title = {Evolution and growth in large libre software projects},
	journal = {Principles of Software Evolution, Eighth International Workshop on},
	year = {2005},
	pages = {165-174},
	author = {Gregorio Robles and Amor, J. J. and Jesus M. Gonzalez-Barahona and Herraiz, I.}
}
@article {105,
	title = {Improving Web accessibility through an enhanced open-source browser},
	journal = {Ibm Systems Journal},
	volume = {44},
	number = {3},
	year = {2005},
	note = {Times Cited: 2},
	pages = {573-588},
	abstract = {The accessibilityWorks project provides software enhancements to the Mozilla (TM) Web browser and allows users to control their browsing environment. Although Web accessibility standards specify markup that must be incorporated for Web pages to be accessible, these standards do not ensure a good experience for all Web users. This paper discusses user controls that facilitate a number of adaptations that can greatly increase the usability of Web pages for a diverse population of users. in addition to transformations that change page presentation, innovations are discussed that enable mouse and keyboard input correction as well as vision-based control for users unable to use their hands for computer input.},
	author = {Hanson, V. L. and Brezin, J. P. and Crayne, S. and Keates, S. and Kjeldsen, R. and Richards, J. T. and Swart, C. and Trewin, S.}
}
@article {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 {Huang:2005:MVH:1083142.1083158,
	title = {Mining version histories to verify the learning process of Legitimate Peripheral Participants},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {84-88},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Since code revisions reflect the extent of human involvement in the software development process, revision histories reveal the interactions and interfaces between developers and modules.We therefore divide developers and modules into groups according to the revision histories of the open source software repository, for example, sourceforge.net. To describe the interactions in the open source development process, we use a representative model, Legitimate Peripheral Participation (LPP) [6], to divide developers into groups such as core and peripheral teams, based on the evolutionary process of learning behavior.With the conventional module relationship, we divide modules into kernel and non-kernel types (such as UI). In the past, groups of developers and modules have been partitioned naturally with informal criteria. In this work, however, we propose a developer-module relationship model to analyze the grouping structures between developers and modules. Our results show some process cases of relative importance on the constructed graph of project development. The graph reveals certain subtle relationships in the interactions between core and non-core team developers, and the interfaces between kernel and non-kernel modules.},
	keywords = {awstats, bzflag, cvs, filezilla, gallery, Legitimate Peripheral Participants (LPP), moodle, open boundary, open source software development process, phpmyadmin, social networks, sourceforge},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083158},
	url = {http://doi.acm.org/10.1145/1082983.1083158},
	attachments = {https://flosshub.org/sites/flosshub.org/files/84MiningVersion.pdf},
	author = {Huang, Shih-Kun and Liu, Kang-min}
}
@unpublished {flosswp223,
	title = {Open Source Biotechnology},
	year = {2005},
	month = {June},
	abstract = {Building on discussions with public and private sector industry participants, funding agencies, leaders of the free and open source software movement and scholars in a range of disciplines, this PhD thesis assesses the desirability and feasibility of extending open source principles to biotechnology research and development. It argues that "open source biotechnology" is both desirable and broadly feasible, and demonstrates that many of the essential elements of an embryonic open source movement are already present in this field.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hope.pdf},
	author = {Janet Hope}
}
@conference {760,
	title = {Open Source: Toward Innovations through Educational Development in China},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {254-258},
	abstract = {This paper describes the author{\textquoteright}s personal viewpoints toward open source software, particularly for the educational development in China. The current status of China is presented to explain why open source is critical within the Chinese educational domain. We believe that open source is suitable not only for financial reasons, but also because it will provide an efficient solution for China to establish an innovative environment whilst promoting intellectual capacities. The benefits of using open source are ideal for the current situations in the Chinese educational system. In this paper, one example is given about the promotion activities of the open source software Scilab (SCILAB(c)INRIA-ENPC) in the Chinese educational domain since 2001. Activities demonstrate that open source ideas and practices will have a great impact in China. Lessons and progress are demonstrated from these activities. The final goal of the Chinese educational development is to increase innovati...},
	url = {http://pascal.case.unibz.it/handle/2038/1259},
	author = {Hu, Bao-Gang}
}
@conference {723,
	title = {OSSmole: A collaborative repository for FLOSS research data and analyses},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {54-60},
	abstract = {This paper introduces a collaborative project, {\textquotedblleft}OSSmole{\textquotedblright}, designed to gather, share and store comparable data and analyses of free and open source software development for academic research. The project draws on the ongoing collection and analysis efforts of many research groups, reducing duplication, and promoting compatibility both across sources of FLOSS data and across research groups and analyses. The paper outlines current difficulties with the current typical quantitative FLOSS research process and uses these to develop requirements and presents the design of the system.},
	url = {http://pascal.case.unibz.it/handle/2038/1422},
	author = {Howison, James and Conklin, Megan and Kevin Crowston}
}
@conference {Williams:2005:RSS:1083142.1083144,
	title = {Recovering system specific rules from software repositories},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {7-11},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {One of the most successful applications of static analysis based bug finding tools is to search the source code for violations of system-specific rules. These rules may describe how functions interact in the code, how data is to be validated or how an API is to be used. To apply these tools, the developer must encode a rule that must be followed in the source code. The difficulty is that many of these system-specific rules are undocumented and "grow" over time as the source code changes. Most research in this area relies on expert programmers to document these little-known rules. In this paper we discuss a method to automatically recover a subset of these rules, function usage patterns, by mining the software repository. We present a preliminary study that applies our work to a large open source software project.},
	keywords = {function usage patterns, functions, source code, wine},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083144},
	url = {http://doi.acm.org/10.1145/1082983.1083144},
	attachments = {https://flosshub.org/sites/flosshub.org/files/7Recovering.pdf},
	author = {Williams, Chadd C. and Hollingsworth, Jeffrey K.}
}
@conference {794,
	title = {SchoolTool: Defining Our Niche in the Open Source Architecture of Schools},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {334-337},
	keywords = {information system, open source, school, student},
	url = {http://pascal.case.unibz.it/handle/2038/1436},
	author = {Hoffman, Tom}
}
@conference {Hindle:2005:SFM:1083142.1083161,
	title = {SCQL: a formal model and a query language for source control repositories},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {100-104},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Source Control Repositories are used in most software projects to store revisions to source code files. These repositories operate at the file level and support multiple users. A generalized formal model of source control repositories is described herein. The model is a graph in which the different entities stored in the repository become vertices and their relationships become edges. We then define SCQL, a first order, and temporal logic based query language for source control repositories. We demonstrate how SCQL can be used to specify some questions and then evaluate them using the source control repositories of five different large software projects.},
	keywords = {evolution, file, gnumeric, modperl, openssl, revision, samba, scm, source code},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083161},
	url = {http://doi.acm.org/10.1145/1082983.1083161},
	attachments = {https://flosshub.org/sites/flosshub.org/files/100scql.pdf},
	author = {Hindle, Abram and Daniel M. German}
}
@conference {717,
	title = {A Social Network Approach To Free/Open Source Software Simulation},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	note = {"Second, we use mailing list archives for three different projects. This gives us a more stringent network measure, since links are generated only when one developer communicates directly with another."
 
"The mailing lists were the developers list from a well deployed database server, the general list for an text and file processing library, and the general list for a smaller F/OSS web browser."},
	pages = {16-23},
	abstract = {Free and Open Source Software (F/OSS) development is a complex process that is just beginning to be understood. The actual development process is frequently characterized as disparate volunteer developers collaborating to create a piece of software. The developers of F/OSS, like most software engineers, spend a significant portion of their time fostering collaboration through various channels social communication. We have analyzed several methods of communication; a social networking site, project mailing lists, and developer weblogs; to gain an understanding of the social network structure behind F/OSS projects. This social network data was used to create a model of F/OSS development that allows for multiple projects, users, and developers with varying goals and socialization methods. Using this model we have been able to replicate some of the known phenomena observed in F/OSS and provide a first step in the creation of a robust model of F/OSS. },
	keywords = {email, mailing list, social network analysis},
	doi = {10.1.1.178.4984},
	url = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.178.4984},
	author = {Wagstrom, Patrick Adam and Herbsleb, James and Carley, Kathleen}
}
@article {84,
	title = {The social structure of Free and Open Source Software development},
	journal = {First Monday},
	volume = {10},
	number = {2},
	year = {2005},
	author = {Kevin Crowston and James Howison}
}
@conference {Hawthorne:2005:SEE:1062455.1062581,
	title = {Software engineering education in the era of outsourcing, distributed development, and open source software: challenges and opportunities},
	booktitle = {Proceedings of the 27th international conference on Software engineering},
	series = {ICSE {\textquoteright}05},
	year = {2005},
	pages = {643{\textendash}644},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {As software development becomes increasingly globally distributed, and more software functions are delegated to common open source software (OSS) and commercial off-the-shelf (COTS) components, practicing software engineers face significant challenges for which current software engineering curricula may leave them inadequately prepared. A new multi-faceted distributed development model is emerging that effectively commoditizes many development activities once considered integral to software engineering, while simultaneously requiring practitioners to apply engineering principles in new and often unfamiliar contexts. We discuss the challenges that software engineers face as a direct result of outsourcing and other distributed development approaches that are increasingly being utilized by industry, and some of the key ways we need to evolve software engineering curricula to address these challenges.},
	keywords = {computer science education, contextual learning, education, informatics, software engineering education},
	isbn = {1-58113-963-2},
	doi = {10.1145/1062455.1062581},
	url = {http://doi.acm.org/10.1145/1062455.1062581},
	author = {Hawthorne, Matthew J. and Perry, Dewayne E.}
}
@conference {716,
	title = {A structurational perspective on leadership in Free/Libre Open Source Software teams},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {9-15},
	abstract = {In this conceptual paper, we present a structuration- based theory of leadership behaviours in self-organizing distributed teams such as Free/Libre Open Source Software development teams. Such teams are often composed of members of relatively equal status or who are so disparate in background that formal organizational status seems irrelevant, reducing the usual leadership cues provided by organizational status and title. Building on a functional view of leadership and structuration theory, we suggest that leaders are individuals who develop team structures that then guide the actions of team members. Specifically, we examine structures of signification in the form of shared mental models, structures of domination in the form of role structures and structures of legitimation in form of rules and norms. The main contribution of our paper is the integration of various social theories to describe emergent leadership behaviours in distributed teams. We develop a set of prop...},
	url = {http://pascal.case.unibz.it/handle/2038/623},
	author = {Kevin Crowston and Robert Heckman and Hala Annabi and Chengetai Masango}
}
@conference {Neamtiu:2005:USC:1083142.1083143,
	title = {Understanding source code evolution using abstract syntax tree matching},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {2-6},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Mining software repositories at the source code level can provide a greater understanding of how software evolves. We present a tool for quickly comparing the source code of different versions of a C program. The approach is based on partial abstract syntax tree matching, and can track simple changes to global variables, types and functions. These changes can characterize aspects of software evolution useful for answering higher level questions. In particular, we consider how they could be used to inform the design of a dynamic software updating system. We report results based on measurements of various versions of popular open source programs, including BIND, OpenSSH, Apache, Vsftpd and the Linux kernel.},
	keywords = {abstract syntax trees, apache, bind, evolution, linux, openssh, software evolution, source code, source code analysis, vsftpd},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083143},
	url = {http://doi.acm.org/10.1145/1082983.1083143},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2Understanding.pdf},
	author = {Neamtiu, Iulian and Foster, Jeffrey S. and Hicks, Michael}
}
@conference {783,
	title = {Unreliable Collaborators: Coordination in distributed volunteer teams},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {305-306},
	abstract = {Drawing together the interest, skills and resources of individuals to pursue productive activity is the cornerstone of wealth creation. Recently, new forms of productive activity have emerged that draw together highly motivated, often volunteer, participants to collaborate through low-cost information systems to produce high quality products that rival those produced by wealthy firms and markets. Examples include free (libr{\^A}{\textasciiacute}e) and open source software (FLOSS), such as Linux, and collaboratively edited texts, such as Wikipedia and the Open Directory. There is an opportunity to study these novel activities, to understand their organization, in order to both further their continued success and to assess whether and which of their novel organization techniques might be used in wider domains of human collaborative activity.},
	keywords = {coordination, floss organization, MOTIVATION, open source, volunteer teams},
	url = {http://pascal.case.unibz.it/handle/2038/1552},
	author = {Howison, James}
}
@article {flosswp1738,
	title = {Why and how-to contribute to libre software when you integrate them into an in-house application ?},
	journal = {Proceedings of the 1st International Conference on Open Source Systems},
	year = {2005},
	month = {June},
	pages = {113{\textendash}118},
	abstract = {Free or open source software are common tools that everybody can use and customise at its convenience to create in-house applications. Using and customising free software is not sufficient to ensure that this in-house application will be maintainable at mid or long term. This paper draws lessons from our in-house project, the development of a groupware Web platform for researchers, to help defining a policy through which efficient contributions can be made to open source software so that the in-house projects may remain viable.},
	author = {Christian Bac and Olivier Berger and V{\'e}ronique Deborde and Benoit Hamet}
}
@inbook {53,
	title = {Why hackers do what they do: Understanding motivation and effort in free/open source software projects},
	booktitle = {Perspectives on Free and Open Source Software},
	year = {2005},
	publisher = {MIT Press},
	organization = {MIT Press},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lakhaniwolf.pdf},
	author = {Karim R Lakhani and Wolf, R.},
	editor = {Feller, J. and Fitzgerald, Brian and Hissam, S. and Karim R Lakhani}
}
@conference {1052,
	title = {Bug driven bug finders},
	booktitle = {Proceedings of the 2004 international workshop on Mining software repositories  - MSR {\textquoteright}04},
	volume = {2004},
	year = {2004},
	pages = {70 - 74},
	publisher = {IEE},
	organization = {IEE},
	address = {Edinburgh, Scotland, UK},
	abstract = {We describe a method of creating tools to find bugs in software that is driven by the analysis of previously fixed bugs. We present a study of bug databases and software repositories that characterize commonly occurring types of bugs.	Based on the types of bugs that were commonly reported and fixed in the code, we determine what types of bug finding tools should be developed. We have implemented one static checker, a return value usage checker. Novel features of this checker include the use of information from the software repository to try to improve its false positive rate by identifying patterns that have resulted in previous bug fixes.},
	keywords = {apache, bug tracking, bugs},
	doi = {10.1049/ic:20040479},
	attachments = {https://flosshub.org/sites/flosshub.org/files/70BugDrivenBug.pdf},
	author = {Williams, C.C. and Hollingsworth, J.K.}
}
@proceedings {1198,
	title = {A Conflict Detected Earlier is a Conflict Resolved Easier},
	year = {2004},
	pages = {82-86},
	abstract = {Open Source development is highly distributed and parallel in nature. There are no definite boundaries, either for people or from where they work. This high level of parallel, distributed development leads to conflicting changes made concurrently by different developers. Be- cause OSS developers lack the kinds of informal coordination opportunities that collocation offers, OSS developers must rely on mailing lists, discussion groups, and tools such as CM and bug tracking systems to try to man- age their parallel efforts such that conflicts do not occur. Unfortunately, these coordination mechanisms are not adequate: it still regularly happens that parallel changes interfere, either via direct overlap or indirect, semantic conflicts. In this paper, we build upon our previous work in raising awareness as a mechanism to support better coordination among developers, and introduce a new integration of our Palantír tool with Eclipse as well as a new visualization of parallel work that we believe is especially useful in Open Source settings.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/sarma83-87.pdf},
	author = {Sarma, A. and van der Hoek, A.}
}
@article {flosswp140,
	title = {Fostering cooperation on the Internet: social exchange processes in innovative virtual consumer communities},
	year = {2004},
	month = {February},
	abstract = {Virtual communities of consumers increasingly engage in voluntary collaborative production of digital goods and services which became highly successful in recent years. This paper offers a theoretical conceptualization and empirical evidence of the key elements and processes of exchange in those communities. Within a culture of gift-giving and generalized social exchange, knowledge as the main resource of the community is multiplied by giving it away freely to others and thus, fosters contribution behavior. Friendship, peer reputation and external feed-back provided by a global user community represent highly motivating social rewards which, combined with individual gain of knowledge, constitute a self-sustaining system of exchange.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hemetsberger2.pdf},
	author = {Andrea Hemetsberger}
}
@conference {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 {flosswp158,
	title = {The Jukebox Mode of Innovation: a Model of Commercial Open Source Development},
	year = {2004},
	month = {May},
	abstract = {In this paper, I explore the circumstances under which innovation processes without secrecy or intellectual property protection are viable, and where free revealing of innovations is a profit-maximizing strategy. Motivated by an empirical study of embedded Linux, I develop a duopoly model of quality competition. Firms require two complementary technologies as inputs, but differ with respect to the relative importance of these technologies. I find that a regime with compulsory revealing can lead to higher product qualities and higher profits than a proprietary regime. When the decision to reveal is endogenized, equilibria with voluntary revealing arise, again superior to the proprietary outcome.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/henkel.pdf},
	author = {Joachim Henkel}
}
@article {flosswp167,
	title = {Munich/MIT Suvey: Development of Embedded Linux},
	year = {2004},
	month = {May},
	abstract = {The use of Linux in embedded devices has increased enormously in recent years. Most of the publicly available code for embedded Linux is developed and contributed by commercial firms, not by hobbyists. This raises the question if and how the development process differs from that of other OSS. This issue was addressed in a survey of embedded Linux developers yielding 268 valid responses. This paper is a collection of descriptive results from the survey.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/henkeltins.pdf},
	author = {Joachim Henkel}
}
@article {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.}
}
@article {flosswp190,
	title = {Patterns of Free Revealing ? Balancing Code Sharing and Protection in Commercial Open Source Development},
	year = {2004},
	month = {September},
	abstract = {Commercial firms increasingly contribute to the development of open source software (OSS). However, a conflict often arises between the requirements of the General Public License to make "derived work" available, and firms? interest to protect their intellectual property embodied in the code. If there are ways to mitigate or solve this conflict, the conditions under which OSS will be an appealing solution to firms become much more general. This paper is the first to provide a quantitative empirical study of this conflict and the ways firms deal with it. I present a study of embedded Linux, based on an online-survey that yielded 268 valid responses. It turns out that firms routinely use various means to protect their developments, while keeping the GPL. Still, they do reveal a considerable share of their code? on average, 49\%. Heterogeneity between firms is analyzed using multivariate analysis. I show how the relative importance of various benefits and downsides of revealing determines a firm?s pattern of revealing. An analysis of reported reasons for revealing and of the type of code that is revealed provides further insights into these patterns. Putting the different dimensions of revealing behavior together, I find that consistent patterns of revealing can be identified for different types of firms.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/henkel2.pdf},
	author = {Joachim Henkel}
}
@proceedings {flosswp181,
	title = {The perils and pitfalls of mining SourceForge},
	year = {2004},
	month = {05/2004},
	pages = {7-11},
	abstract = {SourceForge provides abundant accessible data from Open Source Software development projects, making it an attractive data source for software engineering research. However it is not without theoretical peril and practical pitfalls. In this paper, we outline practical lessons gained from our spidering, parsing and analysis of SourceForge data. SourceForge can be practically difficult: projects are defunct, data from earlier systems has been dumped in and crucial data is hosted outside SourceForge, dirtying the retrieved data. These practical issues play directly into analysis: decisions made in screening projects can reduce the range of variables, skewing data and biasing correlations. SourceForge is theoretically perilous: because it provides easily accessible data items for each project, tempting researchers to fit their theories to these limited data. Worse, few are plausible dependent variables. Studies are thus likely to test the same hypotheses even if they start from different theoretical bases. To avoid these problems, analyses of SourceForge projects should go beyond project level variables and carefully consider which variables are used for screening projects and which for testing hypotheses.},
	keywords = {Data Collection, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/howison04msr.pdf},
	author = {Howison, James and Kevin Crowston}
}
@article {flosswp142,
	title = {Sharing and Creating Knowledge in Open-Source Communities The case of KDE},
	year = {2004},
	month = {February},
	abstract = {Our research suggests that knowledge is shared and created in online communities of practice through the establishment of processes and {\textquoteright}technologies{\textquoteright} that enable virtual re-experience for the learners at various levels. It demonstrates that online communities of practice overcome the problem of tacit knowledge transformation through the usage of technological tools, task-related features, analogies and usage scenarios. Three questions guided our research. The first one concentrates on how community members organize content with regard to their daily routines that potentially transforms into knowledge for other members. Secondly, as open-source communities depend on attracting and socializing new members, we inquired how new members are enabled to accumulate the knowledge necessary for becoming a valued member. Thirdly, we asked how members co-create and conceptualize new ideas - create new knowledge - in absence of physical proximity. Re-experience is enabled by modular tasks and transactive group memory, rigid guidance of new members, openness and legitimate peripheral participation, asynchronous communication, and virtual experimentation. Empirical evidence is based on an ethnographic investigation of the KDE project community.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hemreinh.pdf},
	author = {Andrea Hemetsberger}
}
@unpublished {flosswp198,
	title = {The social structure of Free and Open Source software development},
	year = {2004},
	month = {November},
	publisher = {Syracuse University School of Information Studies},
	type = {Working Paper},
	abstract = {Metaphors, such as the Cathedral and Bazaar, used to describe the organization of FLOSS projects typically place them in sharp contrast to proprietary development by emphasizing FLOSS{\textquoteright}s distinctive social and communications structures. But what do we really know about the communication patterns of FLOSS projects? How generalizable are the projects that have been studied? Is there consistency across FLOSS projects? Questioning the assumption of distinctiveness is important because practitioner-advocates from within the FLOSS community rely on features of social structure to describe and account for some of the advantages of FLOSS production. To address this question, we examined 120 project teams from SourceForge, representing a wide range of FLOSS project types, for their communications centralization as revealed in the interactions in the bug tracking system. We found that FLOSS development teams vary widely in their communications centralization, from projects completely centered on one developer to projects that are highly decentralized and exhibit a distributed pattern of conversation between developers and active users.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowstonhowison.pdf},
	author = {Kevin Crowston and James Howison}
}
@conference {flosswp180,
	title = {Towards a Portfolio of FLOSS project Success Measures},
	booktitle = {Workshop on Open Source Software Engineering, International Conference on Software Engineering},
	year = {2004},
	month = {May},
	abstract = {Project success is one of the most widely used dependent variables in information systems research. However, conventional measures of project success are difficult to apply to Free/Libre Open Source Software projects. In this paper, we present an analysis of four measures of success applied to SourceForge projects: number of members of the extended development community, project activity, bug fixing time and number of downloads. We argue that these four measures provide different insights into the collaboration and control mechanisms of the projects.},
	keywords = {bug fixing, developers, downloads, project success, sourceforge, team, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowston04towards.pdf},
	author = {Kevin Crowston and Hala Annabi and Howison, James and Chengetai Masango}
}
@article {flosswp141,
	title = {Understanding consumers{\textquoteright} collective action on the Internet - a definition and discussion of relevant concepts for research},
	year = {2004},
	month = {February},
	abstract = {This paper offers a new approach for understanding online collaboration and collective action of {\textquoteright}prosumers{\textquoteright}. It is proposed here that theories of collective action and social representations theory, in particular, provide a theoretical framework for studying the structural and social context of online collaboration of consumers, the social actors involved, and how public discourse contributes to shared meaning creation and dissemination in online communities. Processes of naming, classifying, personalizing and institutionalization give their actions ontological reality and contribute to the sustainability of the common effort. An overview and definition of these processes and relevant influencing factors is given and possible indicators of these concepts in open-source communities are highlighted.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hemetsberger3.pdf},
	author = {Andrea Hemetsberger}
}
@article {flosswp139,
	title = {When Consumers Produce on the Internet: The Relationship between Cognitive-affective, Socially-based, and Behavioral Involvement of Prosumers},
	year = {2004},
	month = {February},
	abstract = {This article advances our understanding of the motivational sources for consumer involvement in online joint innovation. The {\textquoteright}free{\textquoteright} or {\textquoteright}open-source{\textquoteright} software movement is the largest socio-technical network and most visible empirical evidence of this new phenomenon. The paper promotes a behavioral view of involvement and offers a conceptualization and empirical evidence of the relationship between cognitive-affective, socially-based and behavioral involvement in online joint production. An Internet survey with 1486 contributors to open-source software revealed that the extent of behavioral involvement is strongly related to the structure and strength of relationships between different motivations. The relationship between concern for self and concern for others especially distinguishes the level of contribution to online projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hemetsberger1.pdf},
	author = {Andrea Hemetsberger}
}
@proceedings {103,
	title = {Why developers participate in open source software projects: an empirical investigation},
	year = {2004},
	keywords = {Survey},
	author = {Il-Horn Hann and Jeff Roberts and Sandra Slaughter}
}
@proceedings {1165,
	title = {Addressing Challenges to Open Source Collaboration with the Semantic Web},
	year = {2003},
	pages = {9-13},
	attachments = {https://flosshub.org/sites/flosshub.org/files/9-13.pdf},
	author = {Ankolekar, A. and Herbsleb, J. D. and Sycara, K.}
}
@proceedings {1172,
	title = {Beyond Code: Content Management and the Open Source Development Portal},
	year = {2003},
	pages = {69-73},
	attachments = {https://flosshub.org/sites/flosshub.org/files/69-73.pdf},
	author = {T. Halloran and W. Scherlis and Erenkrantz, J.}
}
@conference {DBLP:conf/ecis/TsiavosH03,
	title = {Beyond good and evil: why open source development for peer-to-peer networks does not necessarily equal to an open society is as imbalanced as copyright law and definitely is not going to make you a better person},
	booktitle = {European Conference on Information Systems (ECIS 2003)},
	year = {2003},
	note = {"In a first stage we collected data related to the development of the Gnutella protocol. The sources included: web sites that were used for hosting forums and file repositories related to the development of the protocol that could be either archived or still operational; messages posted on discussion groups, forums and newsgroups; the design documents of the Gnutella protocol.
In a second stage we gathered material related to the Limewire application. The sources included: operational and archived web sites having been used for the development of the application; applications such as Concurrent Version Systems (CVS) or Bug reporting tools (such as Issuezila), design and implementation documentation and relevant press reports.
The data gathered covered a time span from early 2000 to late November 2002."
"Other sources informed our research and also acted, at times of uncertainty, as forms of triangulation and verification (Lee 1991). These sources include websites such as Slashdot.org and WiredNews; IRC-mediated communications and private messages exchanged between the various developers."},
	month = {2003},
	abstract = {This paper interrogates the claims that open source development is an ideal form of regulatory development. We begin by presenting the literature that offers a framework of modalities of regulation where code, along with laws, markets, and norms shape and influence individual action. Within this framework, it is argued that for an Open Society we need Open Code.	We present the processes through which the Gnutella protocol and the Limewire application are developed by deconstructing the mechanisms of participation and contribution of the individual developers. The techniques of monitoring, modularization and filtering that we identify appear to be inconsistent with open society promises. Instead we suggest a different framing, that of creating nests of interests, whose creators can find refuge from inhabitants of other nests. From that perspective, we suggest that we should stop referring to the war between Copyright and peer-to-peer networks as the battle between good and evil.},
	keywords = {bug reports, cvs, design documents, discussion, discussion forums, documentation, forums, gnutella, issuezilla, limewire, web site},
	attachments = {https://flosshub.org/sites/flosshub.org/files/tsiavosHosein.pdf},
	author = {Prodromos Tsiavos and Ian Hosein}
}
@conference {flosswp137,
	title = {Defining Open Source Software Project Success},
	booktitle = {Twenty-Fourth International Conference on Information Systems},
	year = {2003},
	month = {December},
	abstract = {Information systems success is one of the most widely used dependent variables in information systems research. In this paper, we identify a range of measures that can be used to assess the success of open source software (OSS) projects. We identify measures based on a review of the literature, a consideration of the OSS development process and an analysis of the opinions of OSS developers. For each measure, we provide examples of how they might be used in a study of OSS development.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowstonannabihowison.pdf},
	author = {Kevin Crowston and Hala Annabi and James Howison}
}
@article {flosswp73,
	title = {The Ecology of Open Source Software Development},
	year = {2003},
	month = {January},
	abstract = {A number of theories have emerged to explain the success of open source software, mainly from economics and law. We analyze a very large sample of OSS projects and find striking patterns in the overall structure of the development community. The distribution of projects on a range of activity measures is spectacularly skewed, with only a relatively tiny number of projects showing evidence of the strong collaborative activity which is supposed to characterize OSS. Our findings are consistent with prior, smaller-scale empirical research. We argue that these findings pose problems for the dominant accounts of OSS. We suggest that the gulf between active and inactive projects may be explained by social-structural features of the community which have received little attention in the existing literature. We suggest some hypotheses that might better predict the observed ecology of projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/healyschussman.pdf},
	author = {Kieran Healy}
}
@article {flosswp55,
	title = {The Economics of Free Software for a Competitive Firm},
	year = {2003},
	month = {February},
	abstract = {This paper builds a simple economic model of the profit seeking firm with a choice between producing an open source and proprietary solutions. Differences between public and viral licenses are discussed from the firm{\textquoteright}s perpective. Advocacy issues are omitted entirely, and the model requires no math beyond subtraction. The decision of a firm to adopt an open source product rather than purchase is also discussed, but is seen as a trivial and uninteresting problem.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hawkins.pdf},
	author = {Richard Hawkins}
}
@article {116,
	title = {How open source software works: "free" user-to-user assistance},
	journal = {Research Policy},
	volume = {32},
	number = {6},
	year = {2003},
	note = {"The empirical data we collected for study was related to postings to the Apache Usenet help forum, CIWS-U (comp.infosystems.www.servers.unix). "
"For data regarding long-term participation in CIWS-U{\textemdash}who participated, long-term trends, etc.{\textemdash}we examined Usenet posting patterns from 1996 to 1999."
"The Usenet log data was obtained from a World Wide Web service called Deja.com (since acquired by Google)"
survey},
	pages = {923-943},
	abstract = {Research into free and open source software development projects has so far largely focused on how the major tasks of software development are organized and motivated. But a complete project requires the execution of "mundane but necessary" tasks as well. In this paper, we explore how the mundane but necessary task of field support is organized in the case of Apache web server software, and why some project participants are motivated to provide this service gratis to others. We find that the Apache field support system functions effectively. We also find that, when we partition the help system into its component tasks, 98\% of the effort expended by information providers in fact returns direct learning benefits to those providers. This finding considerably reduces the puzzle of why information providers are willing to perform this task "for free." Implications are discussed.},
	keywords = {apache, help, logs, MOTIVATION, participants, Survey, usenet},
	doi = {http://dx.doi.org/10.1016/S0048-7333(02)00095-1},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.110.8172\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lakhani2003.pdf},
	author = {Karim R Lakhani and von Hippel, Eric}
}
@article {flosswp78,
	title = {Motivation of Software Developers in Open Source Projects: An Internet-based Survey of Contributors to the Linux Kernel},
	journal = {RP Special Issue},
	year = {2003},
	month = {February},
	abstract = {The motives of 141 contributors to a large Open Source Software project (the Linux kernel) was explored with an internet-based questionnaire study. Measured factors were both derived from discussions within the Linux community as well as from models from social sciences. Participants? engagement was particularly determined by their identification as a Linux developer, by pragmatic motives to improve own software, and by their tolerance of time investments. Moreover, some of the software development was accomplished by teams. Activities in these teams were particularly determined by participants? evaluation of the team goals as well as by their perceived indispensability and self-efficacy.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-hertelniednerherrmann.pdf},
	author = {Guido Hertel}
}
@article {1116,
	title = {Organizational learning in open-source software projects: an analysis of debugging data},
	journal = {IEEE Transactions on Engineering Management},
	volume = {50},
	year = {2003},
	month = {11/2003},
	pages = {485 - 493},
	abstract = {This paper studies organizational learning effects in open-source programming projects. Working with data from the Apache and Mozilla projects, the study focuses on three aspects of open-source development. The first is the use of the open-source approach as a hedge against system complexity. The second is the adaptive learning mechanisms realized by the debugging process. The last is the learning curve effects of project-specific experience on bug cycle times. The results indicate that while open-source development is subject to positive learning effects, these effects are not universal, with some projects deriving more benefit than others.},
	keywords = {apache, bugs, complexity, mozilla},
	issn = {0018-9391},
	doi = {10.1109/TEM.2003.820136},
	author = {Huntley, C.L.}
}
@proceedings {1177,
	title = {Quality and the Reliance on Individuals in Free Software Projects},
	year = {2003},
	month = {2003},
	pages = {105-109},
	attachments = {https://flosshub.org/sites/flosshub.org/files/105-109.pdf},
	author = {Martin Michlmayr and Hill, B.M.}
}
@article {96,
	title = {Satisfying heterogeneous user needs via innovation toolkits: the case of Apache security software},
	journal = {Research Policy},
	volume = {32},
	number = {7},
	year = {2003},
	note = {Times Cited: 30},
	pages = {1199-1215},
	abstract = {Manufacturers customarily provide only a few product variants to address the average needs of users in the major segments of markets they serve. When user needs are highly heterogeneous, this approach leaves many seriously dissatisfied. One solution is to enable users to modify products on their own using "innovation toolkits." We explore the effectiveness of this solution in an empirical study of Apache security software. We find high heterogeneity of need in that field, and also find that users modifying their own software to be significantly more satisfied than non-innovating users. We propose that the "user toolkits" solution will be useful in many markets characterized by heterogeneous demand. (C) 2003 Elsevier Science B.V. All rights reserved.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-vonhippelfranke_0.pdf},
	author = {Nik Franke and von Hippel, Eric}
}
@proceedings {1167,
	title = {Tools for light-weight knowledge sharing in open-source software development},
	year = {2003},
	pages = {25-29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/25-29.pdf},
	author = {Cubranic, Davor and Holmes, Reid and Ying, Annie and Murphy, Gail C.}
}
@proceedings {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 {1862,
	title = {Editorial: Open source software engineering},
	journal = {IEE Proceedings - Software},
	volume = {149},
	year = {2002},
	month = {2002},
	pages = {1},
	issn = {14625970},
	doi = {10.1049/ip-sen:20020363},
	attachments = {https://flosshub.org/sites/flosshub.org/files/20020363.pdf},
	author = {Feller, J. and Fitzgerald, B. and van der Hoek, A.}
}
@book {flosswp72,
	title = {Government Policy Towards Open Source Software (Edited Book)},
	year = {2002},
	month = {December},
	abstract = {Can open source software?software that is usually available without charge and that individuals are free to modify?survive against the fierce competition of proprietary software, such as Microsoft Windows? Should the government intervene on its behalf? This book addresses a host of issues raised by the rapid growth of open source software, including government subsidies for research and development, government procurement policy, and patent and copyright policy. Contributors offer diverse perspectives on a phenomenon that has become a lightning rod for controversy in the field of information technology.},
	author = {Robert Hahn}
}
@article {1095,
	title = {High Quality and Open Source Software Practices},
	journal = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	note = {"We examined the publicly visible portions of these projects from November 2001 through March 2002, ...The SLOC counts for the predominate languages are shown},
	month = {2002},
	abstract = {Surveys suggest that, according to various metrics, the quality and dependability of today{\textquoteright}s open source software is roughly on par with commercial and government developed software. What are the prospects for advancing to much higher levels of quality in open source software? More specifically, what attributes must be possessed by quality-related interventions for them to be feasibly adoptable in open source practice? In order to identify some of these attributes, we conducted a preliminary survey of the quality practices of a number of successful open source projects. We focus, in particular, on attributes related to adoptability by the open source practitioner community.},
	keywords = {apache, bug report, bug tracker, bug tracking system, feature requests, gcc, gnome, kde, lines of code, linux, loc, mozilla, netbeans, perl, position paper, python, sloc, source code, Survey, tomcat, xfree86},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HalloranScherlis.pdf},
	author = {T. Halloran and W. Scherlis}
}
@article {hansen2002open,
	title = {The Open Source approach{\textemdash}opportunities and limitations with respect to security and privacy},
	journal = {Computers \& Security},
	volume = {21},
	number = {5},
	year = {2002},
	pages = {461{\textendash}471},
	publisher = {Elsevier},
	abstract = {Today{\textquoteright}s software often does not even fulfil basic security or privacy requirements. Some people regard the open source paradigm as the solution to this problem. First, we carefully explain the security and privacy aspects of open source, which in particular offer the possibility for a dramatic increase in trustworthiness for and autonomy of the user. We show which expectations for an improvement of the software trustworthiness dilemma are realistic. Finally, we describe measures necessary for developing secure and trustworthy open source systems.},
	keywords = {security},
	url = {https://dud.inf.tu-dresden.de/literatur/HaKP_02OpenSource_0214.doc},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HaKP_02OpenSource_0214.doc},
	author = {Hansen, Marit and K{\"o}hntopp, Kristian and Pfitzmann, Andreas}
}
@article {Hissam,
	title = {Trust and vulnerability in open source software},
	journal = {Software, {IEE} Proceedings -},
	volume = {149},
	number = {1},
	year = {2002},
	month = {02/2002},
	pages = {47{\textendash}51},
	chapter = {47},
	abstract = {Software plays an ever increasing role in the critical infrastructures that run our cities, manage our economies, and defend our nations. In 1999, the Presidents Information Technology Advisory Committee (PITAC) reported to the United States President the need for software components that are reliable, tested, modelled and secure supporting the development of predictably reliable and secure systems that underscore our critical infrastructures. Open source software (OSS) constitutes a viable source for software components. Some believe that OSS is more reliable and more secure than closed source software (CSS)-due to a phenomenon dubbed {\textquoteright}many eyeballs{\textquoteright}-but is this truly the case? Or does OSS give the cyber criminal an edge that he would likewise not have? We explore OSS from the perspective of the cyber criminal and discuss what the community of software developers and users alike can do to increase their trust in both open source software and closed source software},
	keywords = {closed source software, community of software developers, critical infrastructures, cyber criminal, open source software, PITAC, predictably reliable systems, predictably secure systems, software components, trust, users, vulnerability},
	issn = {1462-5970},
	doi = {10.1049/ip-sen:20020208},
	author = {Hissam, S. A. and Plakosh, D. and Weinstock, C.}
}
@article {121,
	title = {Two case studies of open source software development: Apache and Mozilla},
	journal = {ACM Transactions on Software Engineering and Methodology},
	volume = {11},
	number = {3},
	year = {2002},
	note = {apache data sources:
email, cvs, bug database 
regarding email: "We wrote Perl scripts to extract date, sender identity, message subject, and the message body that was further processed to obtain details on code changes and problem reports (see below). Manual inspection was used to resolve such things as multiple email addresses in cases where all automated techniques failed."
(but the rest of the paper does not address this data source at all)

mozilla data sources
bugzilla, cvs

},
	pages = {309-346},
	abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. In order to begin investigating such claims, we examine data from two major open source projects, the Apache web server and the Mozilla browser. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution intervals for these OSS projects. We develop several hypotheses by comparing the Apache project with several commercial projects. We then test and refine several of these hypotheses, based on an analysis of Mozilla data. We conclude with thoughts about the prospects for high- performance commercial/ open source process hybrids.},
	keywords = {apache, bug fixing, bug reports, bugzilla, change history, core, defect density, email, email archives, mailing list, mozilla, ownership, participation, productivity, scm, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mockusFieldingHerbsleb2002.pdf},
	author = {Audris Mockus and Roy Fielding and Herbsleb, J. D.}
}
@conference {1157,
	title = {Why Do Developers Contribute to Open Source Projects? First Evidence of Economic Incentives},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	note = {"The data for this research come from two primary sources: Apache project archives and a targeted survey of Apache participants. Archival data are open source project artifacts such as email and source code archives, source code version control meta-data and developer web sites."},
	abstract = {The availability of commercial quality, free software products such as the Apache HTTP (web) server or the Linux operating system has focused significant attention on the open source development process by which these products were created. One of the more perplexing aspects of open source software projects is why developers freely devote their time and energy to these projects. While many open source participants cite idealistic motives for participation, Lerner and Tirole (2000) argue that developer participation in open source projects may, in part, be explained by existing economic theory regarding career concerns. This research seeks to confirm or disconfirm the existence of economic returns to participation in open source development. Preliminary results of our empirical investigation suggest that greater open source participation per se, as measured in contributions made, does not lead to wage increases. However, a higher status in a merit-based ranking within the Apache Project does lead to significantly higher wages. This suggests that employers do not reward the gain in experience through open source participation as an increase in human capital. The results are also consistent with the notion that a high rank within the Apache Software Foundation is a credible signal of the productive capacity of a programmer.},
	keywords = {apache, contributions, cvs, developers, ECONOMICS, email, email archives, financial, Human capital, mailing list, MOTIVATION, participation, source code, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HannRobertsSlaughterFielding.pdf},
	author = {Il-Horn Hann and Jeff Roberts and Sandra Slaughter and Roy Fielding}
}
@conference {1159,
	title = {Why Not Improve Coordination in Distributed Software Development by Stealing Good Ideas from Open Source?},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	keywords = {apache, communication, coordination, distributed},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MockusHerbsleb.pdf},
	author = {Audris Mockus and Herbsleb, James}
}
@article {47,
	title = {Working for Free? Motivations for Participating in Open-Source Projects},
	journal = {International Journal of Electronic Commerce},
	volume = {6},
	number = {3},
	year = {2002},
	pages = {25--39},
	publisher = {ME Sharpe},
	author = {Hars, A.}
}
@article {106,
	title = {Working for free? Motivations for participating in open-source projects},
	journal = {International Journal of Electronic Commerce},
	volume = {6},
	number = {3},
	year = {2002},
	note = {Times Cited: 24},
	pages = {25-39},
	abstract = {The success of the Linux operating system has demonstrated the viability of open-source software, an alternative form of software development that challenges traditional assumptions about software markets. Understanding why developers participate in open-source projects is crucial for assessing the impact of open-source software. Their motivations fall into two broad categories: internal factors (e.g., intrinsic motivation, altruism) and external rewards (e.g., expected future returns, personal needs). The results of a survey administered to open-source programmers are summarized.},
	author = {Hars, A. and Ou, S. S.}
}
@conference {1143,
	title = {Open Source Software: The Other Commercial Software},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {Open source software is a source of components from which systems can be built. Components can also be acquired in the marketplace. There are a myriad of issues that affect software that incorporates commercial components. These issues (and others) also affect open source software. In this paper we examine issues that an organization using open source software is likely to face in light of lessons learned from the world of commercial components},
	keywords = {commercial off-the-shelf software, commercial software, COTS software, open source software},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hissamweinstock.pdf},
	author = {Hissam, S. and Weinstock, C.}
}
@conference {1142,
	title = {Software Engineering Research in the Bazaar},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	note = {"To gain a better understanding of a software system, we recover its software architecture from the system{\textquoteright}s source code.
We recovered the architecture of many open source systems such as the Linux kernel [3], the Mozilla browser [5], the Apache web server [7], and the VIM editor [14]. The recovered architecture is browse-able to permit developers to interact with it, [10] shows an example for the Linux kernel."},
	abstract = {During the last five years, our research group has studied the architecture and evolution of several large open source systems {\textemdash} including Linux, GCC, VIM, Mozilla, and Apache {\textemdash} and we have found that open source software systems often exhibit interesting differences when compared to similar commercially-developed systems. Our investigations of these systems have involved the creation of software architecture models, software architecture repair, the creation of a reference architecture for web servers, the study of evolution and growth of open source systems, and the modelling of architectural properties of systems that are apparent only at build time.},
	keywords = {apache, architecture, gcc, kernel, linux, linux kernel, mozilla, open source software, software architecture, Software Engineering Research, source code, vim},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hassangodfreyholt.pdf},
	author = {Hassan, Ahmed E. and Godfrey, Michael W. and Holt, Richard C.}
}
@article {flosswp26,
	title = {A Case Study of Open Source Software Development: The Apache Server},
	journal = {Proceedings of the International Conference on Software Engineering (ICSE 2000)},
	year = {2000},
	note = {We used the following archival sources of data:
Developer email list (EMAIL).
Concurrent Version Control archive (CVS).
Problem reporting database (BUGDB).},
	month = {June},
	abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. We examine the development process of a major open source application, the Apache web server. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution interval for this OSS project. This analysis reveals a unique process, which performs well on important measures.},
	keywords = {apache, bug fix revisions, bugs, core, cvs, defect density, developers, email archives, participation, productivity, revision control, revision history, roles, scm, source code, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mockusapache.pdf},
	author = {Audris Mockus and Roy Fielding and Herbsleb, James}
}
@article {flosswp3,
	title = {Profiting From Voluntary Information Spillovers: How Users Benefit By Freely Revealing Their Innovations},
	year = {2000},
	month = {July},
	abstract = {Software users reveal the code they have written to other users for free. This behavior is contrary to conventional wisdom in economics - but is essential to the functioning of an effective user innovation community. This paper explores conditions under which the free revealing of innovations (code, in the case of OS) pays for innovating users.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/evhippel-voluntaryinfospillover.pdf},
	author = {Dietmar Harhoff and Joachim Henkel and von Hippel, Eric}
}
@proceedings {108,
	title = {Splitting the organization and integrating the code: Conway{\textquoteright}s law revisited},
	year = {1999},
	pages = {85{\textendash}95},
	publisher = {ACM},
	address = {Los Angeles, CA},
	author = {Herbsleb, J. D. and Rebecca E. Grinter}
}
