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

},
	doi = {10.1007/978-3-319-57735-7_9},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_9},
	author = {Lundell, Bj{\"o}rn and Gamalielsson, Jonas and Stefan Tengblad and Bahram Hooshyar Yousefi and Thomas Fischer and Gert Johansson and Bengt Rodung and Mattsson, Anders and Johan Oppmark and Gustavsson, Tomas and Feist, Jonas and Stefan Landemoo and Erik L{\"o}nroth}
}
@proceedings {1916,
	title = {Advancing Open Science with Version Control and Blockchains},
	year = {2017},
	month = {05/2017},
	pages = {13-14},
	abstract = {The scientific community is facing a crisis of reproducibility:
confidence in scientific results is damaged by
concerns regarding the integrity of experimental data and the
analyses applied to that data. Experimental integrity can be
compromised inadvertently when researchers overlook some
important component of their experimental procedure, or intentionally
by researchers or malicious third-parties who are
biased towards ensuring a specific outcome of an experiment.
The scientific community has pushed for {\textquotedblleft}open science{\textquotedblright} to add
transparency to the experimental process, asking researchers to
publicly register their data sets and experimental procedures.
We argue that the software engineering community can leverage
its expertise in tracking traceability and provenance of source
code and its related artifacts to simplify data management for
scientists. Moreover, by leveraging smart contract and blockchain
technologies, we believe that it is possible for such a system to
guarantee end-to-end integrity of scientific data and results while
supporting collaborative research.},
	keywords = {blockchain, replication, reproducible},
	author = {Jonathan Bell and Thomas D. LaToza and Foteini Baldmitsi and Angelos Stavrou}
}
@conference {Murphy:2017:CEF:3017680.3017682,
	title = {Community Engagement with Free and Open Source Software},
	booktitle = {Proceedings of the 2017 ACM SIGCSE Technical Symposium on Computer Science Education},
	series = {SIGCSE {\textquoteright}17},
	year = {2017},
	pages = {669{\textendash}670},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {A common refrain from Senior Exit Surveys and Alumni Surveys is the desire to work on "real-world," "practical" and "hands-on" projects using industry-ready tools and development environments. To assuage this, institutions have moved towards adopting Free and Open Source Software (FOSS) as an avenue to provide meaningful, applied learning interventions to students. Through these experiences, students benefit from engagement with various communities including: the community of contributors to the FOSS project; the community of local software developers; the community of citizens who reside in the local area; the community of students at their institution and others; and, the community of people impacted by the FOSS project. These engagements motivate students, enhance their communication and technical skills, allow them to grow and become more confident, help them form professional networks, and provide the "real-world" projects they seek. In this panel, we will discuss our experiences in engaging students with five different types of communities as part of incorporating FOSS into our courses, focusing on how other educators can provide the same benefits to their students as well. In order to satisfy the time constraints of the panel, the last two authors will present together.},
	keywords = {free and open source software (FOSS), humanitarian free and open source software (HFOSS), localized free and open source software (LFOSS), under-represented minorities (URM)},
	isbn = {978-1-4503-4698-6},
	doi = {10.1145/3017680.3017682},
	url = {http://doi.acm.org/10.1145/3017680.3017682},
	author = {Murphy, Christian and Buffardi, Kevin and Dehlinger, Josh and Lambert, Lynn and Veilleux, Nanette}
}
@proceedings {1912,
	title = {Developer Turnover in Global, Industrial Open Source Projects: Insights from Applying Survival Analysis},
	year = {2017},
	note = {we study five industrial OSS projects of different
sizes (in terms of software size, contributors and number
of companies involved) and examine whether the duration
of developers staying in a project is related to following
four factors: (i) the time of first contribution, (ii) the rate of
maintaining own files, (iii) the main action type, and (iv) the
main job type

projects:
WikiMedia, OpenStack, GlusterFS from Red
Hat, Xen Project from the Linux Foundation and Apache
CloudStack},
	month = {05/2017},
	pages = {66-75},
	abstract = {Large open source software projects often have
a globally distributed development team. Studies have shown
developer turnover has a significant impact on the project success.
Frequent developer turnover may lead to loss of productivity due
to lacking relevant knowledge and spending extra time learning
how projects work. Thus, lots of attention has been paid to which
factors are related to developer retention; however, few of them
focus on the impact of activities of individual developers.
In this paper, we study five open source projects from
different organizations and examine whether developer turnover
is affected by when they start contributing and what types of
contributions they are making. Our study reveals that developers
have higher chances to survive in software projects when they
1) start contributing to the project earlier; 2) mainly modify
instead of creating files; 3) mainly code instead of dealing with
documentations. Our results also shed lights on the potential
approaches to improving developer retention.},
	keywords = {survival analysis},
	author = {Bin Lin and Gregorio Robles and Serebrenik, Alexander}
}
@proceedings {1894,
	title = {Digging into the Eclipse Marketplace},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {60-65},
	publisher = {Springer},
	abstract = {Eclipse is an integrated development environment that can be extended with plug-ins. Thanks to Eclipse{\textquoteright}s success, a diverse community has been established with members coming from industry, open-source projects, and others, and a marketplace with more than 1.700 different plug-ins developed. Hence, the question arises how this marketplace is composed: Who contributes plug-ins? Which plug-ins are successful? Are there common characteristics or trends? To answer these questions, extensive investigations are necessary. In this paper, we present (i) an initial approach for corresponding analyses and (ii) preliminary results. Overall, we aim to pave the way for further research addressing, for example, motivations to participate in, or the evolution of, open marketplaces.},
	keywords = {Eclipse IDE, Eclipse Marketplace, empirical study, open source},
	doi = {10.1007/978-3-319-57735-7_7},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_7},
	author = {Kr{\"u}ger, J and Corr, N and Schr{\"o}ter, I and Leich, T}
}
@proceedings {1913,
	title = {An Empirical Analysis of Build Failures in the Continuous Integration Workflows of Java-Based Open-Source Software},
	year = {2017},
	note = {"empirical study of CI build
failures in 14 Java-based OSS projects. We extract and analyze
data from publicly available GitHub repositories and Travis-CI
build logs"},
	month = {05/2017},
	pages = {345-355},
	abstract = {{\textemdash}Continuous Integration (CI) has become a common
practice in both industrial and open-source software development.
While CI has evidently improved aspects of the software
development process, errors during CI builds pose a threat to
development efficiency. As an increasing amount of time goes
into fixing such errors, failing builds can significantly impair the
development process and become very costly. We perform an indepth
analysis of build failures in CI environments. Our approach
links repository commits to data of corresponding CI builds.
Using data from 14 open-source Java projects, we first identify
14 common error categories. Besides test failures, which are by
far the most common error category (up to >80\% per project),
we also identify noisy build data, e.g., induced by transient Git
interaction errors, or general infrastructure flakiness. Second,
we analyze which factors impact the build results, taking into
account general process and specific CI metrics. Our results
indicate that process metrics have a significant impact on the
build outcome in 8 of the 14 projects on average, but the strongest
influencing factor across all projects is overall stability in the
recent build history. For 10 projects, more than 50\% (up to 80\%)
of all failed builds follow a previous build failure. Moreover, the
fail ratio of the last k=10 builds has a significant impact on build
results for all projects in our dataset.},
	keywords = {build errors, continuous integration, correlation analysis, msr},
	author = {Thomas Rausch and Waldemar Hummer and Philipp Leitner and Stefan Schulte}
}
@conference {Sharma:2017:IDE:3084226.3084271,
	title = {Investigating Developers{\textquoteright} Email Discussions During Decision-making in Python Language Evolution},
	booktitle = {Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering},
	series = {EASE{\textquoteright}17},
	year = {2017},
	pages = {286{\textendash}291},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Context: Open Source Software (OSS) developers use mailing lists as their main forum for discussing the evolution of a project. However, the use of mailing lists by developers for decision-making has not received much research attention. Objective: We have explored this issue by studying developers{\textquoteright} email discussions around Python Enhancement Proposals (PEPs). Method: Our dataset comprised 42,672 emails from six different mailing lists pertaining to PEP development. We performed multiple forms of analysis on these emails, involving both quantitative measures (e.g., frequency) and deeper analysis of specific PEP discussions (i.e., outlier analysis). Results: Out of three PEP types (Informational, Process and Standard Track), Standard Track PEPs attract a large amount of discussion (both in volume and average number of messages per proposal). Our study also identified specific PEP states and topics that generated a disproportionate amount of discussion. Conclusion: Our outcomes point to several opportunities for improving the management of an OSS team based on the knowledge generated from discussions. We have also identified several interesting avenues for future work such as identifying individuals or groups that present persuasive arguments during decision-making.},
	keywords = {Decision-making, Email discussions, Python development},
	isbn = {978-1-4503-4804-1},
	doi = {10.1145/3084226.3084271},
	url = {http://doi.acm.org/10.1145/3084226.3084271},
	author = {Sharma, Pankajeshwara and Savarimuthu, Bastin Tony Roy and Stanger, Nigel and Licorish, Sherlock A. and Rainer, Austen}
}
@conference {1925,
	title = {Investigating developers{\textquoteright} email discussions during decision-making in Python language evolution},
	booktitle = {Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering  - EASE{\textquoteright}17},
	year = {2017},
	pages = {286 - 291},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Karlskrona, SwedenNew York, New York, USA},
	abstract = {Context: Open Source Software (OSS) developers use mailing lists as their main forum for discussing the evolution of a project. However, the use of mailing lists by developers for decision-making has not received much research attention. Objective: We have explored this issue by studying developers{\textquoteright} email discussions around Python Enhancement Proposals (PEPs). Method: Our dataset comprised 42,672 emails from six different mailing lists pertaining to PEP development. We performed multiple forms of analysis on these emails, involving both quantitative measures (e.g., frequency) and deeper analysis of specific PEP discussions (i.e., outlier analysis). Results: Out of three PEP types (Informational, Process and Standard Track), Standard Track PEPs attract a large amount of discussion (both in volume and average number of messages per proposal). Our study also identified specific PEP states and topics that generated a disproportionate amount of discussion. Conclusion: Our outcomes point to several opportunities for improving the management of an OSS team based on the knowledge generated from discussions. We have also identified several interesting avenues for future work such as identifying individuals or groups that present persuasive arguments during decision-making.},
	isbn = {9781450348041},
	doi = {10.1145/3084226.3084271},
	url = {https://www.researchgate.net/publication/317486549_Investigating_developers\%27_email_discussions_during_decision-making_in_Python_language_evolution},
	author = {Stanger, Nigel and Rainer, Austen and Licorish, Sherlock A. and Sharma, Pankajeshwara and Savarimuthu, Bastin Tony Roy}
}
@proceedings {1889,
	title = {Investigating Relationships Between FLOSS Foundations and FLOSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {14-22},
	publisher = {Springer},
	abstract = {Foundations function as vital institutional support infrastructures for many of the most successful open source projects, but the role of these support entities remains an understudied phenomenon in FLOSS research. Drawing on Open Hub (formerly known as Ohloh) data, this paper empirically investigates the different ways these entities support projects and interact with different projects and with each other.},
	doi = {10.1007/978-3-319-57735-7_2},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_2},
	author = {Juho Lindman and Hammouda, Imed}
}
@proceedings {1911,
	title = {Machine Learning-Based Detection of Open Source License Exceptions},
	year = {2017},
	note = {"We address these questions by first performing a large scale mining-based study... [W]e analyzed the  source code of 51,754 projects written in six different programming languages (Ruby, Javascript, Python, C, C++, and C$\#$) hosted on GitHub. },
	month = {05/2017},
	pages = {118-129},
	abstract = {From a legal perspective, software licenses govern the redistribution, reuse, and modification of software as both source and binary code. Free and Open Source Software (FOSS) licenses vary in the degree to which they are permissive or restrictive in allowing redistribution or modification under licenses different from the original one(s). In certain cases developers may modify the license by appending to it an exception to specifically allow reuse or modification under a particular condition. These exceptions are an important factor to consider for license compliance analysis since they modify the standard (and widely understood_ terms of the original license. In this work, we first perform a large-scale empirical study on the change history of over 51k FOSS systems aimed at quantitatively investigating the prevalence of known license exceptions and identifying new ones. Subsequently, we performed a study on the detection of license exceptions by relying on machine learning. We evaluated the license exception classification with four different supervised learners and sensitivity analysis. Finally we present a categorization of license exceptions and explain their implications.},
	keywords = {classifier, empirical studies, license, machine learning},
	doi = {10.1109/ICSE.2017.19},
	author = {Vendome, Christopher and Mario Linares-Vasquez and Bavota, Gabriele and Di Penta, Massimiliano and Daniel M. German and Poshyvanyk, Denys}
}
@proceedings {1892,
	title = {Measuring Perceived Trust in Open Source Software Communities},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {49-54},
	publisher = {Springer},
	abstract = {We investigate the different aspects of measuring trust in Open Source Software (OSS) communities. In the theoretical part we review seminal works related to trust in OSS development. This investigation provides background to our empirical part where we measure trust in a community (in terms of kudo). Our efforts provide further avenues to develop trust-based measurement tools. These are helpful for academics and practitioners interesting in quantifiable traits of OSS trust.},
	doi = {10.1007/978-3-319-57735-7_5},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_5},
	author = {Syeed, M.M. Mahbubul and Juho Lindman and Hammouda, Imed}
}
@proceedings {1926,
	title = {Open Source Communities as Liminal Ecosystems},
	year = {2017},
	abstract = {In this paper, we propose a study to explore the movement of individuals engaged in open source communities. Although there is extensive literature on open source communities and growing body of knowledge on corporate engagement in open source communities, our understanding of the movements of individuals within these communities is limited. To analyze these movements, we build on Arnold Van Gennep and Victor Turners{\textquoteright} theories on liminality. Through this lens, we build an understanding of the movements of individual members within open source communities.},
	url = {http://aisel.aisnet.org/mwais2017/45},
	author = {Kevin Lumbard and Matt Germonprez}
}
@proceedings {1893,
	title = {The Open Source Officer Role {\textendash} Experiences},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {55-59},
	publisher = {Springer},
	abstract = {This papers describe the Open Source Officer role and the experiences from introducing this role in several companies. We outline the role description, main responsibilities, and interfaces to other roles and organizations. We investigated the role in several organization and bring interesting discrepancies and overlaps of how companies operate with OSS.

},
	keywords = {governance, inner source, maturity models},
	doi = {10.1007/978-3-319-57735-7_6},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_6},
	author = {Mols, CE and Wnuk, K and Lin{\r a}ker, J}
}
@proceedings {1917,
	title = {Understanding the Impressions, Motivations, and Barriers of One Time Code Contributors to FLOSS Projects: A Survey},
	year = {2017},
	month = {05/2017},
	pages = {187-197},
	abstract = {Successful Free/Libre Open Source Software
(FLOSS) projects must attract and retain high-quality talent.
Researchers have invested considerable effort in the study of
core and peripheral FLOSS developers. To this point, one critical
subset of developers that have not been studied are One-Time
code Contributors (OTC) {\textendash} those that have had exactly one patch
accepted. To understand why OTCs have not contributed another
patch and provide guidance to FLOSS projects on retaining
OTCs, this study seeks to understand the impressions, motivations,
and barriers experienced by OTCs. We conducted an online
survey of OTCs from 23 popular FLOSS projects. Based on the
184 responses received, we observed that OTCs generally have
positive impressions of their FLOSS project and are driven by a
variety of motivations. Most OTCs primarily made contributions
to fix bugs that impeded their work and did not plan on becoming
long term contributors. Furthermore, OTCs encounter a number
of barriers that prevent them from continuing to contribute to the
project. Based on our findings, there are some concrete actions
FLOSS projects can take to increase the chances of converting
OTCs into long-term contributors.},
	keywords = {newcomers, One Time Contributors, Qualitative Research, Survey},
	author = {Amanda Lee and Carver, Jeffrey C. and Bosu, Amiangshu}
}
@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}
}
@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 {1847,
	title = {License usage and changes: a large-scale study on gitHub},
	journal = {Empirical Software Engineering},
	year = {2016},
	abstract = {Open source software licenses determine, from a legal point of view, under which conditions software can be integrated and redistributed. The reason why developers of a project adopt (or change) a license may depend on various factors, e.g., the need for ensuring compatibility with certain third-party components, the perspective towards redistribution or commercialization of the software, or the need for protecting against somebody else{\textquoteright}s commercial usage of the software. This paper reports a large empirical study aimed at quantitatively and qualitatively investigating when and why developers adopt or change software licenses. Specifically, we first identify license changes in 1,731,828 commits, representing the entire history of 16,221 Java projects hosted on GitHub. Then, to understand the rationale of license changes, we perform a qualitative analysis on 1,160 projects written in seven different programming languages, namely C, C++, C$\#$, Java, Javascript, Python, and Ruby{\textemdash}following an open coding approach inspired by grounded theory{\textemdash}on commit messages and issue tracker discussions concerning licensing topics, and whenever possible, try to build traceability links between discussions and changes. On one hand, our results highlight how, in different contexts, license adoption or changes can be triggered by various reasons. On the other hand, the results also highlight a lack of traceability of when and why licensing changes are made. This can be a major concern, because a change in the license of a system can negatively impact those that reuse it. In conclusion, results of the study trigger the need for better tool support in guiding developers in choosing/changing licenses and in keeping track of the rationale of license changes.},
	issn = {1573-7616},
	doi = {10.1007/s10664-016-9438-4},
	author = {Vendome, Christopher and Bavota, Gabriele and Di Penta, Massimiliano and Linares-V{\'a}squez, Mario and German, Daniel and Poshyvanyk, Denys}
}
@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}
}
@inbook {L{\'o}pez2016,
	title = {OSSAP {\textendash} A Situational Method for Defining Open Source Software Adoption Processes},
	booktitle = {Advanced Information Systems Engineering: 28th International Conference, CAiSE 2016, Ljubljana, Slovenia, June 13-17, 2016. Proceedings},
	year = {2016},
	pages = {524{\textendash}539},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Organizations are increasingly becoming Open Source Software (OSS) adopters, either as a result of a strategic decision or just as a consequence of technological choices. The strategy followed to adopt OSS shapes organizations{\textquoteright} businesses; therefore methods to assess such impact are needed. In this paper, we propose OSSAP, a method for defining OSS Adoption business Processes, built using a Situational Method Engineering (SME) approach. We use SME to combine two well-known modelling methods, namely goal-oriented models (using i*) and business process models (using BPMN), with a pre-existing catalogue of goal-oriented OSS adoption strategy models. First, we define a repository of reusable method chunks, including the guidelines to apply them. Then, we define OSSAP as a composition of those method chunks to help organizations to improve their business processes in order to integrate the best fitting OSS adoption strategy. We illustrate it with an example of application in a telecommunications company.
},
	isbn = {978-3-319-39696-5},
	doi = {10.1007/978-3-319-39696-5_32},
	url = {http://dx.doi.org/10.1007/978-3-319-39696-5_32},
	author = {L{\'o}pez, Lidia and Costal, Dolors and Ralyt{\'e}, Jolita and Franch, Xavier and M{\'e}ndez, Luc{\'\i}a and Annosi, Maria Carmela},
	editor = {Nurcan, Selmin and Soffer, Pnina and Bajec, Marko and Eder, Johann}
}
@inbook {Abdulwahhab2016,
	title = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {3{\textendash}15},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {The Role of Local Open Source Communities in the Development of Open Source Projects},
	address = {Cham},
	abstract = {This paper investigates the position of local open source communities (LOSCs) in the development of open source projects (OSPs). We have conducted an empirical study to examine the role of LOSCs, their way of working, and the benefits/challenges they experience compared to the overall global community. The qualitative investigation consisted of ten semi-structured interviews with members within different LOSCs. The results confirm the importance of LOSCs and the pivotal role they play in the development of OSPs. In many cases, they act as the middleman between individual members and the project{\textquoteright}s global community. However, LOSCs have their own kinds of challenges.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_1},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_1},
	author = {Abdulwahhab, Sinan and Alabady, Yazen and Sattar, Yacoub and Hammouda, Imed},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {AbbaspourAsadollah2016,
	title = {A Study of Concurrency Bugs in an Open Source Software},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {16{\textendash}31},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {A Study of Concurrency Bugs in an Open Source Software},
	address = {Cham},
	abstract = {Concurrent programming puts demands on software debugging and testing, as concurrent software may exhibit problems not present in sequential software, e.g., deadlocks and race conditions. In aiming to increase efficiency and effectiveness of debugging and bug-fixing for concurrent software, a deep understanding of concurrency bugs, their frequency and fixing-times would be helpful. Similarly, to design effective tools and techniques for testing and debugging concurrent software understanding the differences between non-concurrency and concurrency bugs in real-word software would be useful. This paper presents an empirical study focusing on understanding the differences and similarities between concurrency bugs and other bugs, as well as the differences among various concurrency bug types in terms of their severity and their fixing time. Our basis is a comprehensive analysis of bug reports covering several generations of an open source software system. The analysis involves a total of 4872 bug reports from the last decade, including 221 reports related to concurrency bugs. We found that concurrency bugs are different from other bugs in terms of their fixing time and their severity. Our findings shed light on concurrency bugs and could thereby influence future design and development of concurrent software, their debugging and testing, as well as related tools.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_2},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_2},
	author = {Abbaspour Asadollah, Sara and Sundmark, Daniel and Eldh, Sigrid and Hansson, Hans~ and Enoiu, Eduard Paul},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@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}
}
@inbook {1735,
	title = {On the Availability and Effectiveness of Open Source Software for Digital Signing of PDF Documents},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {71-80},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Digital signatures are important in order to ensure the integrity and authenticity of information communicated over the Internet involving different stakeholders within and beyond the borders of different nations. The topic has gained increased interest in the European context and there is legislation and project initiatives aiming to facilitate use and standardisation of digital signatures. Open standards and open source implementations of open standards are important means for the interoperability and long-term maintenance of software systems implementing digital signatures. In this paper we report from a study aiming to establish the availability and effectiveness of software provided under an open source license for digital signing and validation of PDF documents. Specifically, we characterise the use of digital signatures in Swedish Governmental agencies, report on the interoperability of open source and proprietary licensed software for digital signatures in PDF documents, and establish the effectiveness of software provided under an open source license for validation of digital signatures in PDF documents.
},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_7},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_7},
	author = {Gamalielsson, Jonas and Jakobsson, Fredrik and Lundell, Bj{\"o}rn and Feist, Jonas and Gustavsson, Tomas and Landqvist, Fredric},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@article {1802,
	title = {Candoia: A Platform and an Ecosystem for Building and Deploying Versatile Mining Software Repositories Tools},
	year = {2015},
	note = {" In terms of its focus,
the Candoia platform is closer to Bevan et al.{\textquoteright}s Kenyon [9],
Bajracharya et al.{\textquoteright}s Sourcerer [6], Gousios and Spinellis{\textquoteright}s Alitheia
Core [32, 31], Howison et al.{\textquoteright}s FLOSSMole [39] and different from
Boetticher et al.{\textquoteright}s PROMISE Repository [69], Gonz{\'a}lez-Barahona
and Robles{\textquoteright}s open-access data repositories [29], Black Duck OpenHub
(aka Ohloh) [13], GHTorrent [30, 33], Ossher et al.{\textquoteright}s SourcererDB
[64], the SourceForge Research Data Archive (SRDA) [28],
and Boa [25]. },
	month = {11/2015},
	institution = {Iowa State University},
	abstract = {Research on mining software repositories (MSR) has shown great
promise during the last decade in solving many challenging software
engineering problems. There exists, however, a {\textquoteleft}valley of death{\textquoteright}
between these significant innovations in the MSR research and their
deployment in practice. The significant cost of converting a prototype
to software; need to provide support for a wide variety of tools
and technologies e.g. CVS, SVN, Git, Bugzilla, Jira, Issues, etc,
to improve applicability; and the high cost of customizing tools to
practitioner-specific settings are some key hurdles in transition to
practice. We describe Candoia, a platform and an ecosystem that
is aimed at bridging this valley of death between innovations in
MSR research and their deployment in practice. We have implemented
Candoia and provide facilities to build and publish MSR
ideas as Candoia apps. Our evaluation demonstrates that Candoia
drastically reduces the cost of converting an idea to an app, thus
reducing the barrier to transitioning research findings into practice.
We also see versatility, in Candoia app{\textquoteright}s ability to work with a variety
of tools and technologies that the platform supports. Finally,
we find that customizing Candoia app to fit project-specific needs
is often well within the grasp of developers.},
	keywords = {Analysis of software and its evolution, Application specific development environments, flossmole cited, msr, research to practice, software evolution, software repositories},
	url = {http://lib.dr.iastate.edu/cgi/viewcontent.cgi?article=1378\&context=cs_techreports},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Candoia-\%20A\%20Platform\%20and\%20an\%20Ecosystem\%20for\%20Building\%20and\%20Deploying\%20V.pdf},
	author = {Nitin M. Tiwari and Dalton D. Mills and Ganesha Upadhyaya and Eric Lin and Rajan, Hridesh}
}
@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 {1772,
	title = {An Empirical Study of Architectural Change in Open-Source Software Systems},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {From its very inception, the study of software
architecture has recognized architectural decay as a regularly
occurring phenomenon in long-lived systems. Architectural decay
is caused by repeated changes to a system during its lifespan.
Despite decay{\textquoteright}s prevalence, there is a relative dearth of empirical
data regarding the nature of architectural changes that may lead
to decay, and of developers{\textquoteright} understanding of those changes. In
this paper, we take a step toward addressing that scarcity by
conducting an empirical study of changes found in software
architectures spanning several hundred versions of 14 opensource
systems. Our study reveals several new findings regarding
the frequency of architectural changes in software systems, the
common points of departure in a system{\textquoteright}s architecture during
maintenance and evolution, the difference between system-level
and component-level architectural change, and the suitability
of a system{\textquoteright}s implementation-level structure as a proxy for its
architecture.},
	keywords = {architectural change, architecture recovery, open-source systems, software architecture, software evolution},
	url = {http://softarch.usc.edu/~pooyan/publications/emparch_msr15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/emparch_msr15.pdf},
	author = {Duc Minh Le and Pooyan Behnamghader and Joshua Garcia{\textdaggerdbl} Daniel Link and Arman Shahbazian and Nenad Medvidovic}
}
@conference {1795,
	title = {An Empirical Study of Developer Quality},
	booktitle = {2015 International Conference on Software Quality, Reliability and Security - Companion (QRS-C)},
	year = {2015},
	month = {08/2015},
	pages = {202 - 209},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Human factors have attracted more and more attention in software engineering. Of many kinds of developer metrics proposed, developer quality is important. Recently, some researchers measure a developer{\textquoteright}s quality as the rate of his/hernon bug-introducing commits. In this paper, we conduct an empirical study of this developer quality metric. We use the data of six open source software projects and get the following conclusions: (1) the values of developer quality in a project are uniformly distributed in a certain range, (2) developer quality tends to increase with software evolution, (3) developers with more contribution are more likely to have higher developer quality, (4) ownership does not have a consistent and significant correlation with developer quality. These results can provide project leaders and team members with some guides to improve developer quality, and thus improve software quality.},
	doi = {10.1109/QRS-C.2015.33},
	author = {Qiu, Yilin and Zhang, Weiqiang and Zou, Weiqin and Liu, Jia and Liu, Qin}
}
@conference {1822,
	title = {An Empirical Study of Developer Quality},
	booktitle = {2015 International Conference on Software Quality, Reliability and Security - Companion (QRS-C)},
	year = {2015},
	pages = {202 - 209},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Human factors have attracted more and more attention in software engineering. Of many kinds of developer metrics proposed, developer quality is important. Recently, some researchers measure a developer{\textquoteright}s quality as the rate of his/hernon bug-introducing commits. In this paper, we conduct an empirical study of this developer quality metric. We use the data of six open source software projects and get the following conclusions: (1) the values of developer quality in a project are uniformly distributed in a certain range, (2) developer quality tends to increase with software evolution, (3) developers with more contribution are more likely to have higher developer quality, (4) ownership does not have a consistent and significant correlation with developer quality. These results can provide project leaders and team members with some guides to improve developer quality, and thus improve software quality.
},
	doi = {10.1109/QRS-C.2015.33},
	author = {Qiu, Yilin and Zhang, Weiqiang and Zou, Weiqin and Liu, Jia and Liu, Qin}
}
@proceedings {KMGSL15,
	title = {Generating the Blueprints of the Java Ecosystem},
	year = {2015},
	note = {To appear},
	month = {05/2015},
	publisher = {IEEE Computer Society},
	url = {http://gaijin.dmst.aueb.gr/~bkarak/poster_msr2015.pdf},
	author = {Vassilios Karakoidas and Mitropoulos, Dimitris and Louridas, Panos and Gousios, Georgios and Diomidis Spinellis}
}
@inbook {1740,
	title = {The RISCOSS Platform for Risk Management in Open Source Software Adoption},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {124-133},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Managing risks related to OSS adoption is a must for organizations that need to smoothly integrate OSS-related practices in their development processes. Adequate tool support may pave the road to effective risk management and ensure the sustainability of such activity. In this paper, we present the RISCOSS platform for managing risks in OSS adoption. RISCOSS builds upon a highly configurable data model that allows customization to several types of scopes. It implements two different working modes: exploration, where the impact of decisions may be assessed before making them; and continuous assessment, where risk variables (and their possible consequences on business goals) are continuously monitored and reported to decision-makers. The blackboard-oriented architecture of the platform defines several interfaces for the identified techniques, allowing new techniques to be plugged in.
},
	keywords = {Open source adoption, Open Source Projects, open source software, OSS, Risk Management, Software platform},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_12},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_12},
	author = {Franch, X. and Kenett, R. and Mancinelli, F. and Susi, A. and Ameller, D. and Annosi, M.C. and Ben-Jacob, R. and Blumenfeld, Y. and Franco, O.H. and Gross, D. and Lopez, L. and Morandini, M. and Oriol, M. and Siena, A.},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {1711,
	title = {A Study of Demand-Driven Documentation in Two Open Source Projects},
	year = {2015},
	publisher = {IEEE},
	abstract = {We investigate how demand-driven documentation
is used by open source projects. Our study relies on questions
and answers (i.e., demand-driven documentation) posted to Stack
Overflow and focuses on two projects: Apache POI and Fennec
(Firefox for Android). We find that the demand-driven documentation
provided by respective community is of good quality and
contributions are made within an acceptable amount of time.
We conclude that demand-driven documentation can be suitable
as a primary information source if other resources accompany
it, e.g., websites. However, the suitability is closely related to
size and activity of the project{\textquoteright}s community. We also investigate
whether the type of project (e.g., API, application, product, etc.)
matters, and find that given the nature of a forum, projects
where the intended users are developers have larger and more
active communities and are thus better suited for demand-driven
documentation.},
	author = {Andersson, Jessica and Larsson, Sofia and Ericsson, Morgan and Wingkvist, Anna}
}
@inbook {1739,
	title = {Surveying the Adoption of FLOSS by Public Administration Local Organizations},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {114-123},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Background. The introduction of Open Source Software technologies in the Public Administration plays a key role in the spread of Open Source Software. The state of the art in the adoption of Open Source Software solutions in the Public Administration is not very well known even in areas like Lombardy, which is Italy{\textquoteright}s largest and most developed region.
Goal. The goal of the investigation documented in this paper is to obtain a clear picture about the introduction of Open Source Software technologies in the Public Administration, the obstacles to their adoption, and the willingness of stakeholders to proceed with their introduction.
Method. We carried out a qualitative and quantitative survey that was submitted to a representative part of the Public Administrations in Lombardy.
Results. The analysis of the qualitative and quantitative information shows that several Public Administrations are already using Open Source Software technologies, though not in all application areas. The savings are one frequently cited incentive to the adoption of Open Source Software. However, one obstacle is the fact that a comprehensive law on software in the Public Administration has not yet been approved.
Conclusions. Our analysis provides results that indicate a common understanding of incentives, obstacles, and opportunities for Open Source Software technologies in Public Administrations.},
	keywords = {FLOSS adoption, Italy, Public administrations, Survey},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_11},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_11},
	author = {Tosi, Davide and Lavazza, Luigi and Morasca, Sandro and Chiappa, Marco},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {1752,
	title = {Why Power Laws? An Explanation from Fine-Grained Code Changes},
	year = {2015},
	note = {"The data used in this section come from four open source Java projects. We used CVSANALY to collect data from their Git repositories."},
	abstract = {Throughout the years, empirical studies have found
power law distributions in various measures across many software
systems. However, surprisingly little is known about how
they are produced. What causes these power law distributions?
We offer an explanation from the perspective of fine-grained
code changes. A model based on preferential attachment and selforganized
criticality is proposed to simulate software evolution.
The experiment shows that the simulation is able to render power
law distributions out of fine-grained code changes, suggesting
preferential attachment and self-organized criticality are the
underlying mechanism causing the power law distributions in
software systems.},
	keywords = {Apache Maven, cvsanaly, eclipse, git, Google Guice, java, jedit, open source},
	url = {https://users.soe.ucsc.edu/~linzhp/msr2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015.pdf},
	author = {Zhongpeng Lin and Jim Whitehead}
}
@conference {Mitropoulos:2014:BCM:2597073.2597123,
	title = {The Bug Catalog of the Maven Ecosystem},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {372{\textendash}375},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Examining software ecosystems can provide the research community with data regarding artifacts, processes, and communities. We present a dataset obtained from the Maven central repository ecosystem (approximately 265GB of data) by statically analyzing the repository to detect potential software bugs. For our analysis we used FindBugs, a tool that examines Java bytecode to detect numerous types of bugs. The dataset contains the metrics results that FindBugs reports for every project version (a JAR) included in the ecosystem. For every version we also stored specific metadata such as the JAR{\textquoteright}s size, its dependencies and others. Our dataset can be used to produce interesting research results, as we show in specific examples.
},
	keywords = {findbugs, Maven Repository, msr data showcase, Software Bugs},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597123},
	url = {http://doi.acm.org/10.1145/2597073.2597123},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mitro.pdf},
	author = {Mitropoulos, Dimitris and Vassilios Karakoidas and Louridas, Panos and Gousios, Georgios and Diomidis Spinellis}
}
@conference {Krutz:2014:CCO:2597073.2597127,
	title = {A Code Clone Oracle},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {388{\textendash}391},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Code clones are functionally equivalent code segments. Detecting code clones is important for determining bugs, fixes and software reuse. Code clone detection is also essential for developing fast and precise code search algorithms. How- ever, the challenge of such research is to evaluate that the clones detected are indeed functionally equivalent, consider- ing the majority of clones are not textual or even syntactically identical. The goal of this work is to generate a set of method level code clones with a high confidence to help to evaluate future code clone detection and code search tools to evaluate their techniques. We selected three open source programs, Apache, Python and PostgreSQL, and randomly sampled a total of 1536 function pairs. To confirm whether or not these function pairs indicate a clone and what types of clones they belong to, we recruited three experts who have experience in code clone research and four students who have experience in programming for manual inspection. For confidence of the data, the experts consulted multiple code clone detection tools to make the consensus. To assist manual inspection, we built a tool to automatically load function pairs of interest and record the manual inspection results. We found that none of the 66 pairs are textual identical type- 1 clones, and 9 pairs are type-4 clones. Our data is available at: http://phd.gccis.rit.edu/weile/data/cloneoracle/.
},
	keywords = {clone, Clone Oracle, Code Clone Detection, msr data showcase, software engineering},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597127},
	url = {http://doi.acm.org/10.1145/2597073.2597127},
	attachments = {https://flosshub.org/sites/flosshub.org/files/clone_oracle.pdf},
	author = {Krutz, Daniel E. and Le, Wei}
}
@conference {Tymchuk:2014:COP:2597073.2597093,
	title = {Collaboration in Open-source Projects: Myth or Reality?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {304{\textendash}307},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {One of the fundamental principles of open-source projects is that they foster collaboration among developers, disregarding their geographical location or personal background. When it comes to software repositories collaboration is a rather ephemeral phenomenon which lacks a clear definition, and it must therefore be mined and modeled. This throws up the question whether what is mined actually maps to reality.

In this paper we investigate collaboration by modeling it using a number of diverse approaches that we then compare to a ground truth obtained by surveying a substantial set of developers of the Pharo open-source community. Our findings indicate that the notion of collaboration must be revisited, as it is undermined by a number of factors that are often tackled in imprecise ways or not taken into account at all.},
	keywords = {COLLABORATION, Software ecosystems},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597093},
	url = {http://doi.acm.org/10.1145/2597073.2597093},
	author = {Tymchuk, Yuriy and Mocci, Andrea and Lanza, Michele}
}
@conference {Saini:2014:DMA:2597073.2597134,
	title = {A Dataset for Maven Artifacts and Bug Patterns Found in Them},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {416{\textendash}419},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper, we present data downloaded from Maven, one of the most popular component repositories. The data includes the binaries of 186,392 components, along with source code for 161,025. We identify and organize these components into groups where each group contains all the versions of a library. In order to asses the quality of these components, we make available report generated by the FindBugs tool on 64,574 components. The information is also made available in the form of a database which stores total number, type, and priority of bug patterns found in each component, along with its defect density. We also describe how this dataset can be useful in software engineering research.
},
	keywords = {Empirical Research, Empirical software engineering, findbugs, maven, software quality},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597134},
	url = {http://doi.acm.org/10.1145/2597073.2597134},
	author = {Saini, Vaibhav and Sajnani, Hitesh and Ossher, Joel and Lopes, Cristina V.}
}
@inbook {1617,
	title = {Flow Research SXP Agile Methodology for FOSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {195-198},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

This paper aims to explain a procedure that takes into account the different research processes carried out in developing an open-source, allowing control and management. This study is the SXP methodology applied in this type of project was carried out, allowing the validity of the basis of this research.
},
	keywords = {methodology SXP, open-source, production, research, Software},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_28},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_28},
	author = {Pe{\~n}alver Romero, GladysMarsi and Leyva Samada, LisandraIsabel and Abad, AbelMeneses},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1592,
	title = {Navigation Support in Evolving Open-Source Communities by a Web-Based Dashboard},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {11-20},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

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

To answer this research question, we first conducted an online survey within different successful OSS communities. The results of our evaluation showed that there is a great interest in community-centered statistics. Therefore, we developed an OSS navigator: a Web-based dashboard for community-oriented reflection of OSS projects. The navigator was filled with data from communication and development repositories of three large bioinformatics OSS projects. The members of these OSS communities tested the prototype. The bioinformatics OSS developers acknowledged the uniqueness of statistics that the NOSE dashboard offers. Especially, graph visualization of the project social network received the highest attention. This network view combined with other community-oriented metrics can significantly enhance the existing visualizations or even be provided as a standalone tool.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_2},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_2},
	author = {Hannemann, Anna and Liiva, Kristjan and Klamma, Ralf},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {1676,
	title = {OCData Hackathon @ CSCW 2014},
	booktitle = {Proceedings of the 17th ACM conference on Computer supported cooperative work \& social computing},
	year = {2014},
	pages = {317 - 318},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Baltimore, Maryland, USANew York, New York, USA},
	abstract = {Online Communities data is prevalent in CSCW research, but the approaches to collecting, managing, analyzing and visualizing large scale social data varies on a lab by lab basis. The OCData hackathon is aimed at creating a community opportunity to share approaches to online communities research at the level of data. Integrating data, tools and theories to address interesting research questions remains a challenge for the community.},
	isbn = {9781450325417},
	doi = {10.1145/2556420.2558865},
	author = {Goggins, Sean and Andrea Wiggins and Susan Winter and Brian Butler}
}
@conference {Guo:2014:ODC:2597073.2597094,
	title = {Oops! Where Did That Code Snippet Come from?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {52{\textendash}61},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {A kernel oops is an error report that logs the status of the Linux kernel at the time of a crash. Such a report can provide valuable first-hand information for a Linux kernel maintainer to conduct postmortem debugging. Recently, a repository has been created that systematically collects kernel oopses from Linux users. However, debugging based on only the information in a kernel oops is difficult. We consider the initial problem of finding the offending line, i.e., the line of source code that incurs the crash. For this, we propose a novel algorithm based on approximate sequence matching, as used in bioinformatics, to automatically pinpoint the offending line based on information about nearby machine-code instructions, as found in a kernel oops. Our algorithm achieves 92\% accuracy compared to 26\% for the traditional approach of using only the oops instruction pointer.},
	keywords = {debugging, linux kernel, oops, sequence alignment},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597094},
	url = {http://doi.acm.org/10.1145/2597073.2597094},
	attachments = {https://flosshub.org/sites/flosshub.org/files/guo.pdf},
	author = {Guo, Lisong and Lawall, Julia and Muller, Gilles}
}
@inbook {1616,
	title = {Polytrix: A Pacto-Powered Polyglot Test Matrix},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {191-194},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

We have created a polyglot test framework named Polytrix to compare, benchmark, and independently verify a suite of open-source OpenStack SDKs that each target a different programming language. The framework validates sample code from each SDK against a shared test scenario to validate that each SDK correctly implements a given scenario. It uses Pacto for integration contract testing between the SDKs and the OpenStack services, and generates test reports that help compare and document each SDK. It is designed so interactive training materials can be generated in future versions.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_27},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_27},
	author = {Lincoln, Max and Alves, Fernando},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Guzman:2014:SAC:2597073.2597118,
	title = {Sentiment Analysis of Commit Comments in GitHub: An Empirical Study},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {352{\textendash}355},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Emotions have a high impact in productivity, task quality, creativity, group rapport and job satisfaction. In this work we use lexical sentiment analysis to study emotions expressed in commit comments of different open source projects and analyze their relationship with different factors such as used programming language, time and day of the week in which the commit was made, team distribution and project approval. Our results show that projects developed in Java tend to have more negative commit comments, and that projects that have more distributed teams tend to have a higher positive polarity in their emotional content. Additionally, we found that commit comments written on Mondays tend to a more negative emotion. While our results need to be confirmed by a more representative sample they are an initial step into the study of emotions and related factors in open source projects.
},
	keywords = {Human Factors in Software Engineering, mining challenge, msr challenge, sentiment analysis},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597118},
	url = {http://doi.acm.org/10.1145/2597073.2597118},
	author = {Guzman, Emitza and Az{\'o}car, David and Li, Yang}
}
@article {1716,
	title = {Sourcerer: An infrastructure for large-scale collection and analysis of open-source code},
	journal = {Science of Computer Programming},
	volume = {79},
	year = {2014},
	month = {1/2014},
	pages = {241 - 259},
	abstract = {A large amount of open source code is now available online, presenting a great potential resource for software developers. This has motivated software engineering researchers to develop tools and techniques to allow developers to reap the benefits of these billions of lines of source code. However, collecting and analyzing such a large quantity of source code presents a number of challenges. Although the current generation of open source code search engines provides access to the source code in an aggregated repository, they generally fail to take advantage of the rich structural information contained in the code they index. This makes them significantly less useful than Sourcerer for building state-of-the-art software engineering tools, as these tools often require access to both the structural and textual information available in source code.We have developed Sourcerer, an infrastructure for large-scale collection and analysis of open source code. By taking full advantage of the structural information extracted from source code in its repository, Sourcerer provides a foundation upon which state-of-the-art search engines and related tools can easily be built. We describe the Sourcerer infrastructure, present the applications that we have built on top of it, and discuss how existing tools could benefit from using Sourcerer.},
	issn = {01676423},
	doi = {10.1016/j.scico.2012.04.008},
	author = {Bajracharya, Sushil and Ossher, Joel and Lopes, Cristina}
}
@proceedings {1571,
	title = {Theorizing Modes of Open Source Software Development},
	year = {2014},
	month = {01/2014},
	pages = {4568-4577},
	publisher = {IEEE Computer Society},
	abstract = {Open Source Software (OSS) development is distributed across actors and artifacts and involves translating diffuse representations into distinct sets of contiguous code artifacts. Despite the highly distributed and dynamic nature of OSS development, it is often described in unitary, monolithic terms {\textendash} an unfortunate situation which masks considerable variance across OSS development processes. Therefore we explore reasons for systematic variance in these processes so as to enable more effective OSS development practices. Drawing on theory of distributed cognition, we develop a language of cognitive translations, which occur within and across distributed social arrangements and structural conditions of sharing knowledge. This language provides micro-foundations for understanding how different modes of OSS development emerge. Through examining how generative characteristics of social and structural distributions in OSS shape distinct development pathways, we propose a theoretically derived typology explaining the characteristics, dynamics, and conditions for success of different modes of OSS development.},
	doi = {10.1109/HICSS.2014.560},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Theorizing\%20Modes\%20of\%20Open\%20Source\%20Software\%20Development.pdf},
	author = {Aron Lindberg and Xuan Xiao and Kalle Lyytinen}
}
@inbook {1630,
	title = {The Babel of Software Development: Linguistic Diversity in Open Source},
	booktitle = {Social Informatics},
	series = {Lecture Notes in Computer Science},
	volume = {8238},
	year = {2013},
	pages = {391-404},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	isbn = {978-3-319-03259-7},
	doi = {10.1007/978-3-319-03260-3_34},
	url = {http://dx.doi.org/10.1007/978-3-319-03260-3_34},
	attachments = {https://flosshub.org/sites/flosshub.org/files/socinfo13.pdf},
	author = {Vasilescu, Bogdan and Serebrenik, Alexander and Brand, MarkG.J.},
	editor = {Jatowt, Adam and Lim, Ee-Peng and Ding, Ying and Miura, Asako and Tezuka, Taro and Dias, Ga{\"e}l and Tanaka, Katsumi and Flanagin, Andrew and Dai, BingTian}
}
@proceedings {1491,
	title = {Communication in Open Source Software Development Mailing Lists},
	year = {2013},
	note = {"The entire dataset used in the experiment, including the cards, the resolved aliases, and detailed statistical results, can be downloaded from ..." http://www.st.ewi.tudelft.nl/~guzzi/oss-communication/},
	month = {05/2013},
	pages = {277-286},
	abstract = {Open source software (OSS) development teams use
electronic means, such as emails, instant messaging, or forums,
to conduct open and public discussions. Researchers investigated
mailing lists considering them as a hub for project communication. Prior work focused on specific aspects of emails, for example
the handling of patches, traceability concerns, or social networks.
This led to insights pertaining to the investigated aspects, but not
to a comprehensive view of what developers communicate about.
Our objective is to increase the understanding of development
mailing lists communication.
We quantitatively and qualitatively analyzed a sample of 506
email threads from the development mailing list of a major OSS
project, Lucene. Our investigation reveals that implementation
details are discussed only in about 35\% of the threads, and that
a range of other topics is discussed. Moreover, core developers
participate in less than 75\% of the threads. We observed that the
development mailing list is not the main player in OSS project
communication, as it also includes other channels such as the
issue repository.},
	keywords = {email, lucene, mailling list},
	url = {http://www.st.ewi.tudelft.nl/~guzzi/downloads/Guzzi2013msr.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Guzzi2013msr.pdf},
	author = {Guzzi, Anja and Bacchelli, Alberto and Lanza, Michele and Pinzger, Martin and van Deursen, Arie}
}
@proceedings {1508,
	title = {The Eclipse and Mozilla Defect Tracking Dataset: A Genuine Dataset for Mining Bug Information},
	year = {2013},
	note = {Intended to be an "open bug database" or baseline for multiple studies in the community. 14 bug attributes [id, product, summary, status, etc], some change over time and some do not. Data set: github.com/ansymo/msr2013-bug_dataset},
	month = {05/2013},
	abstract = {The analysis of bug reports is an important subfield within the mining software repositories community. It explores the rich data available in defect tracking systems to uncover interesting and actionable information about the bug triaging process. While bug data is readily accessible from systems like Bugzilla and JIRA, a common database schema and a curated dataset could significantly enhance future research because it allows for easier replication. Consequently, in this paper we propose the Eclipse and Mozilla Defect Tracking Dataset, a representative database of bug data, filtered to contain only genuine defects (i.e., no feature requests) and designed to cover the whole bug-triage life cycle (i.e., store all intermediate actions). We have used this dataset ourselves for predicting bug severity, for studying bug-fixing time and for identifying erroneously assigned components. github.com/ansymo/msr2013-bug_dataset},
	url = {http://github.com/ansymo/msr2013-bug_dataset},
	author = {Lamkanfi, Ahmed and Javier P{\'e}rez and Demeyer, Serge}
}
@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}
}
@book {1539,
	title = {Modeling Practices in Open Source Software},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {127 - 139},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

It is widely accepted that modeling in software engineering increases productivity and results in better code quality. Yet, modeling adoption remains low. The open source community, in particular, remains almost entirely code centric. In this paper, we explore the reasons behind such limited adoption of modeling practices among open source developers. We highlight characteristics of modeling tools that would encourage their adoption. We propose Umple as a solution where both modeling and coding elements are treated uniformly. In this approach, models can be manipulated textually and code can be edited visually. We also report on the Umple compiler itself as a case study of an open source project where contributors, using the above approach, have and continue to routinely commit code and model over a number of years.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Modeling-Practices-in-Open-Source-Software.pdf},
	author = {Badreddin, Omar and Lethbridge, Timothy and Elassar, Maged},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@conference {1721,
	title = {Orion: A Software Project Search Engine with Integrated Diverse Software Artifacts},
	booktitle = {2013 18th International Conference on Engineering of Complex Computer Systems (ICECCS)},
	year = {2013},
	note = {The FLOSSMole12, Flossmetrics [3] and
Sourcerer [1] projects collect data and/or provide statistics on
their collected data, but are not suitable for selecting a subset
or identifying a unique project based on desired properties.},
	pages = {242 - 245},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Singapore, Singapore},
	abstract = {What projects contain more than 10, 000 lines of code developed by less than 10 people and are still actively maintained with a high bug-fixing rate? To address the challenges for answering such enquiries, we develop an integrated search engine architecture that combines information from different types of software repositories from multiple sources. Our search engine facilitates the construction and execution of complex search queries using a uniform interface that transparently correlates different artifacts of project development and maintenance, such as source code information, version control systems metadata, bug tracking systems elements, and metadata on developer activities and interactions extracted from hosting platforms. We have built an extensible system with an initial capability of over 100, 000 projects collected from the web, featuring various software development artifacts. Using scenarios, we illustrate the benefits of such a search engine for different kinds of project seekers. 
},
	keywords = {flossmole cited},
	doi = {10.1109/ICECCS.2013.42},
	url = {http://www.mysmu.edu/faculty/davidlo/papers/iceccs13-projectsearch.pdf},
	author = {Bissyande, Tegawende F. and Thung, Ferdian and Lo, David and Jiang, Lingxiao and Reveillere, Laurent}
}
@book {1540,
	title = {The Role of Microblogging in OSS Knowledge Management},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {140 - 152},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

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

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

"Using
FLOSSmole [8] and FLOSSmetrics [9] as case studies, similar
systems as such are called {\textquotedblleft}repository of repositories (RoR){\textquotedblright} and
basic requirements of these systems are proposed. "},
	pages = {1 - 7},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Changsha, China},
	abstract = {Free / Libre / Open Source Software (FLOSS) data, such as bug reports, mailing lists and related webpages, contains valuable information for reusing open source software projects. Before conducting further experiment on FLOSS data, researchers often need to download these data into a local storage system. We refer to this pre-process as FLOSS data retrieval, which in many cases can be a challenging task. In this paper, we proposed a crawler framework to ease the process of FLOSS data retrieval. To cope with various types of FLOSS data scattered on the Internet, we designed the framework in a scalable manner where a crawler program can be easily plugged into the system to extend its functionality. Researchers can perform the retrieval process on datasets of various types and sources simply by adding new configurations to the system. We have implemented the framework and provided basic functions via web-based interfaces. We presented the usage of the system by a detailed case study where we retrieved various types of datasets related to Apache Lucene project using our framework.},
	keywords = {flossmole cited},
	isbn = {9781450323697},
	doi = {10.1145/2532443.2532454},
	author = {Yanzhen Zou and Bing Zie and Zhang, Lingxiao}
}
@book {1534,
	title = {Towards a Reference Model on How to Utilise Open Standards in Open Source Projects: Experiences Based on Drupal},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {257 - 263},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

It is known that standards implemented in Open Source software (OSS) can promote a competitive market, reduce the risk for lock-in and improve interoperability, whilst there is limited knowledge concerning the relationship between standards and their implementations in OSS. In this paper we report from an ongoing case study conducted in the context of the ORIOS (Open Source software Reference Implementations of Open Standards) project in which influences between OSS communities and software standard communities are investigated. The study focuses on the Drupal project and three of its implemented standards (RDFa, CMIS, and OpenID).
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_19},
	author = {Andersson, Stefan and Feist, Jonas and Gustavsson, Tomas and Strindberg, Henrik and Gamalielsson, Jonas and Lundell, Bj{\"o}rn and Grahn, Alexander},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@article {1400,
	title = {Analyzing and mining a code search engine usage log},
	journal = {Empirical Software Engineering},
	volume = {17},
	year = {2012},
	month = {8/2012},
	pages = {424 - 466},
	abstract = {This paper presents an analysis of a year long usage log of Koders, the first commercially available Internet-Scale code search engine (http://www.koders.com). The usage log comprises about ten million activities from more than three million users. Analysis of the usage data shows that despite of attracting a large number of visitors, Koders has a very sparse usage and that it lacks regular usage from many of its users. When compared to Web search, search behavior in Koders showed many similar patterns. A topic modeling analysis of the usage data shows what topics users of Koders are looking for. Observations on the prevalence of these topics among the users, and observations on how search and download activities vary across topics, lead to the conclusion that users who find code search engines usable are those who already know to a high level of specificity what to look for. This paper also presents a general categorization of these topics that provides insights on the different ways code search engine users express their queries. It identifies various forms of queries in Koders{\textquoteright}s log and the kinds of results addressed by the queries. It also provides several suggestions for improvements in code search engines based on the analysis of usage, topics, and query forms. The work presented in this paper is the first of its kind that reveals several insights on the usage of an Internet-Scale code search engine.},
	keywords = {code search, koders, search, search engine, topics},
	issn = {1573-7616},
	doi = {10.1007/s10664-010-9144-6},
	author = {Bajracharya, Sushil Krishna and Lopes, Cristina Videira}
}
@conference {1357,
	title = {Content classification of developer emails},
	booktitle = {Proceedings of the 34th IEEE/ACM International Conference On Software Engineering (ICSE 2012)},
	year = {2012},
	note = {We created a web application to manually classify email content in the chosen categories. We classified a statistically significant set of emails from four java open source software (OSS) systems, used to evaluate the accuracy of our approach.
The contributions of this paper are:
1) a novel approach that fuses parsing and ML techniques
for classification of email lines;
2) a web application to manually classify email content; 3) the manual classification of a statistically significant
sample set of emails (for a total of 67,792 lines) from mailing lists of four different software systems{\textendash}in the form of a freely available benchmark; and
4) the empirical evaluation of our approach against the benchmark},
	month = {06/2012},
	abstract = {Emails related to the development of a software system contain information about design choices and issues encountered during the development process. Exploiting the knowledge embedded in emails with automatic tools is challenging, due to the unstructured, noisy and mixed language nature of this communication medium. Natural language text is often not well-formed and is interleaved with languages with other syntaxes, such as code or stack traces.

We present an approach to classify email content at line level. Our technique classifies email lines in five categories (i.e., text, junk, code, patch, and stack trace) to allow one to subsequently apply ad hoc analysis techniques for each category. We evaluated our approach on a statistically significant set of emails gathered from mailing lists of four unrelated open source systems.},
	keywords = {email, Emails, Empirical software engineering, mailing list, natural language, Unstructured Data Mining},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icse2012.pdf},
	author = {Bacchelli, Alberto and Dal Sasso, Tommaso and D{\textquoteright}Ambros, Marco and Lanza, Michele}
}
@proceedings {1462,
	title = {Does OSS Affect E-Government Growth? An Econometric Analysis on the Impacting Factors},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {292-297},
	publisher = {IFIP AICT,  Springer},
	abstract = {Inspired by the OSS values, an increasing number of different forms of open initiatives have come to the fore. In the context of eGovernment the notion of open government has met wide acceptance among nations and became closely related to one of its goals. Open government shares with OSS the notions of collaboration, participation and transparency and many actions towards OSS into eGovernment reform policies, have been recorded worldwide. The study investigates the relationship between OSS growth and eGovernment. A theoretical framework of the theories of institutionalism, growth and human capital is proposed as the guiding theoretical lens to identify possible influencing factors that together with OSS are evaluated for their magnitude of impact on eGovernment growth across different economic environments.},
	keywords = {eGovernment adoption, growth theory, human capital theory, institutionalism},
	author = {Lakka, Spyridoula and Stamati, Teta and Martakos, Draculis}
}
@proceedings {1476,
	title = {How Can Open Standards Be Effectively Implemented in Open Source? Challenges and the ORIOS Project},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {383-388},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Many organisations are currently restricted in their choice of software because of restrictions imposed by existing systems. Challenges include a lack of interoperability and a risk of technological lock-in, which many small companies seek to address by utilising Open Standards and Open Source implementations of such standards when developing and deploying systems. This paper presents an overview of how the industrial research project ORIOS (Open Source software Reference Implementations of Open Standards) seeks to address identified challenges. An overarching goal of the project is to improve understanding within organisations of Open Standards, Open Source Reference Implementations, and the ecosystems around them. This will be done by developing a reference model of necessary and desirable features of an Open Standard, and how Open Standards and their implementations can be utilised by small companies in different usage contexts. An action case study approach will be used as a core strategy for evolving a reference model together with Swedish companies.},
	author = {Lundell, Bj{\"o}rn and AbduraHmanovic, Admir and Andersson, Stefan and Bergström, Erik and Feist, Jonas and Gamalielsson, Jonas and Gustavsson, Tomas and Kahlbom, Roger and Papaxanthis, Konstantin}
}
@proceedings {1441,
	title = {Long-Term Sustainability of Open Source Software Communities beyond a Fork: A Case Study of LibreOffice},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {29-47},
	publisher = {IFIP AICT},
	abstract = {Many organisations have requirements for long-term sustainable software systems and associated communities. In this paper we consider long-term sustainability of Open Source software communities in Open Source projects involving a fork. There is currently a lack of studies in the literature that address how specific Open Source software communities are affected by a fork. We report from a case study aiming to investigate the developer community around the LibreOffice project, which is a fork from the OpenOffice.org project. The results strongly suggest a long-term sustainable community and that there are no signs of stagnation in the project 15 months after the fork. Our analysis provides details on the LibreOffice developer community and how it has evolved from the OpenOffice.org community with respect to project activity, long-term involvement of committers, and organisational influence over time. The findings from our analysis of the LibreOffice project make an important contribution towards a deeper understanding of challenges regarding long-term sustainability of Open Source software communities.},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn}
}
@conference {1318,
	title = {Network-Based Analysis of the Structure and Evolution of an Open Source Software Product},
	booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences},
	year = {2012},
	note = {"raw data about the product structure is extracted from the source code"},
	month = {01/2012},
	pages = {3436-3445},
	abstract = {In this paper, an analysis of product structures in open source software (OSS) at both product level and module level is presented. At the product level, the product structures are modeled as complex networks, and the evolutionary characteristics of product structures are analyzed by using network analysis metrics. At the module level, linking mechanisms, which describe how a module is attached with other modules, are proposed. The linking mechanisms are modeled as probability functions dependent on the degrees of linking modules. A case study from an open source software project, Drupal, is presented. The evolutionary trends of Drupal product structures are analyzed and discussed. Finally, a model is presented to illustrate the effects of linking mechanisms at the module level on the product structures at the system level. The results indicate that the model built using the proposed linking mechanisms generates networks whose evolutionary characteristics are close to that of the original network.},
	keywords = {drupal, source code},
	author = {Le, Qize and Panchal, Jitesh H.}
}
@proceedings {1471,
	title = {OSSLI: Architecture Level Management of Open Source Software Legality Concerns},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {356-361},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {This paper presents a tool that addresses the legality concerns of open source at the level of software architecture, early in the development activity. The tool demonstrates the significance of licensing concerns at the architectural level by extending existing modeling tools with support for open source licensing issues.},
	author = {Lokhman, Alexander and Luoto, Antti and Abdul-Rahman, Salum and Hammouda, Imed}
}
@proceedings {1459,
	title = {Perspectives on Code Forking and Sustainability in Open Source Software},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {274-279},
	publisher = {IFIP AICT,  Springer},
	abstract = {The ability to create high-quality software artifacts that are usable over time is one of the essential requirements of the software business. In such a setting, open source software offers excellent opportunities for sustainability. In particular, safeguarding mechanisms against planned obsolescence by any single actor are built into the definition of open source. The most powerful of these mechanisms is the ability to fork the project. In this paper we argue that the possibility to fork serves as the invisible hand of sustainability that ensures that code remains open and that the code that best serves the community lives on. Furthermore, the mere option to fork provides a mechanism for safeguarding against despotic decisions by the project lead, who is thus guided in their actions to consider the best interest of the community.},
	author = {Nyman, Linus and Mikkonen, Tommi and Juho Lindman and Fougère, Martin}
}
@proceedings {1442,
	title = {Step-by-Step Strategies and Case Studies for Embedded Software Companies to Adapt to the FOSS Ecosystem},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {48-60},
	abstract = {Due to the continuous expansion of the FOSS ecosystem and the introduction of high-quality FOSS, FOSS is increasingly used in consumer electronics (CE) such as smartphones, televisions, and cameras. As a result, manufacturers of CE products have developed a close relationship with the FOSS ecosystem. For CE product manufacturers, efficient adaptation to the FOSS ecosystem has become an essential component in their business operations. This paper will divide the activities of CE product manufacturers within the FOSS ecosystem into the following four levels: identification, adoption, compliance, and contribution. It will examine the main activities and obstacles that arise in each level. The paper will also present instances where companies have succeeded in overcoming these obstacles.},
	keywords = {embedded software, FOSS ecosystem},
	author = {Kim, Suhyun and Yoo, Jaehyun and Lee, Myunghwa}
}
@proceedings {1468,
	title = {A Study on OSS Marketing and Communication Strategies},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {338-343},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {The goal of every open source project is to gain as many satisfied users as possible. To this end, open source software producers should focus on both product development and communication. Currently, most open source projects are mainly concerned with developing code using the most appealing technologies and introducing fancy features. On the contrary, open source software producers seem to lack good communication strategies. In this paper we describe the communication strategies adopted by three successful companies that are active in open source software development. The goal of the paper is to provide some hints that could help other open source software producers identify communication strategies that are effective in promoting their products on the market.},
	author = {del Bianco, Vieri and Lavazza, Luigi and Lenarduzzi, Valentina and Morasca, Sandro and Taibi, Davide and Tosi, Davide}
}
@conference {1319,
	title = {Who Will Remain? An Evaluation of Actual Person-Job and Person-Team Fit to Predict Developer Retention in FLOSS Projects},
	booktitle = {45th Hawai{\textquoteright}i International Conference on System Sciences},
	year = {2012},
	month = {01/2012},
	pages = {3446-3455},
	abstract = {Many businesses and private households rely on Free Libre Open Source Software (FLOSS). Due to a lack of sustained contributors, however, most FLOSS projects do not survive. The early identification of developers who are likely to remain is thus an eminent challenge for the management of FLOSS initiatives. Previous research has shown that individuals{\textquoteright} subjective assessment is often inaccurate emphasizing the need to objectively evaluate retention behavior. Consistent with the concepts Person-Job (P-J) and Person-Team (P-T) fit from the traditional recruitment literature, we derive objective measures to predict developer retention in FLOSS projects. In an analysis of the contribution behavior of former Google Summer of Code (GSoC) students we reveal that the level of development experience and conversational knowledge is strongly associated with retention. Surprisingly, our analysis reveals that students with abilities that are underrepresented in the project and students with a higher academic education do not remain considerably longer.},
	keywords = {email, email archives, google summer of code, kde, mailing list, students},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2012.644},
	attachments = {https://flosshub.org/sites/flosshub.org/files/45.pdf},
	author = {Schilling, A. and Laumer, S. and Weitzel, T.}
}
@conference {1309,
	title = {Do time of day and developer experience affect commit bugginess},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"we study the latest versions of the Linux kernel and PostgreSQL, which have 222,332 and 31,098 commits, respectively. We study the correlation between a commit{\textquoteright}s bugginess and the time of day of the commit, the day of week of the commit, and the experience and commit frequency of the commit authors. In addition, we study several other commit characteristics, such as comment-only fixes and bug lifetimes."},
	month = {05/2011},
	pages = {153-162},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Modern software is often developed over many years with hundreds of thousands of commits. Commit metadata is a rich source of social characteristics, including the commit{\textquoteright}s time of day and the experience and commit frequency of its author. The "bugginess" of a commit is also a critical property of that commit. In this paper, we investigate the correlation between a commit{\textquoteright}s social characteristics and its "bugginess"; such results can be very useful for software developers and software engineering researchers. For instance, developers or code reviewers might be well-advised to thoroughly verify commits that are more likely to be buggy. In this paper, we study the correlation between a commit{\textquoteright}s bugginess and the time of day of the commit, the day of week of the commit, and the experience and commit frequency of the commit authors. We survey two widely-used open source projects: the Linux kernel and PostgreSQL.

Our main findings include: (1) commits submitted between midnight and 4 AM (referred to as late-night commits) are significantly buggier and commits between 7 AM and noon are less buggy, implying that developers may want to double-check their own latenight commits; (2) daily-committing developers produce less-buggy commits, indicating that we may want to promote the practice of daily-committing developers reviewing other developers{\textquoteright} commits; and (3) the bugginess of commits versus day-of-week varies for different software projects.},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985464},
	author = {Tan, Lin and Lam, Patrick and Eyolfson, Jon}
}
@proceedings {1297,
	title = {Forge.mil: A Case Study for Utilizing Open Source Methodologies Inside of Government},
	year = {2011},
	month = {10/2011},
	pages = {334-337},
	publisher = {Springer},
	abstract = {In late 2008, DISA (Defense Information Systems Agency), the global IT arm of the US Department of Defense, embarked upon a project to create an internal collaboration and software application lifecycle management system. Beyond simply fielding yet another tool, the Forge.mil effort was designed to fundamentally change the way the DoD developed and acquired software technology and systems. The method of this change was the application of Open Source principles inside of the larger DoD community, including ideas such as meritocracy and code sharing, as well as Agile and collaborative software development. This lightning talk will explain the rationale behind Forge.mil, how it was developed using Open Source principles, and how it continues to influence technology acquisition within the DoD in both practice and policy changes.},
	author = {Martin, Guy and Lippold, Aaron}
}
@proceedings {1272,
	title = {Ginga-J: An Open Java-Based Application Environment for Interactive Digital Television Services},
	year = {2011},
	month = {10/2011},
	pages = {34-49},
	publisher = {Springer},
	abstract = {This paper aims to present a Ginga-J{\textquoteright}s reference implementation. Although based on a particular platform, the implementation not only works as a proof of concept, but also raised several issues and difficulties on the software architecture project that should be taken into account to ease extensibility and porting to other platforms. Ginga is the standard middleware for the Brazilian DTV System. Its imperative environment (Ginga-J) is based on new JavaDTV specification and mandatory for fixed terrestrial receptors.},
	author = {Kulesza, Raoni and Lima, Jefferson F.A. and Guedes, Alan L. and Junior, Lucenildo L.A. and Meira, Silvio R.L. and Filho, Guido L.S.}
}
@article {1322,
	title = {The Ontology of the OSS Business Model},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {39 - 59},
	abstract = {This study focuses on theory building providing a holistic conceptual framework that consists of an ontology based OSS business model and an OSS business model taxonomy. The study extends existing theory in OSS business models and corresponding taxonomies, based on the structured-case methodological approach. An exploratory study is conducted in two research cycles, for the identification, validation, and evaluation of the critical constructs of an OSS business model. Results reveal that OSS business models differ from traditional software business models, having specific features that affect the software value chain, the infrastructure, and the revenue model of an OSS oriented firm.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011010103},
	author = {Lakka, Spyridoula and Stamati, Teta and Michalakelis, Christos and Martakos, Dracoulis}
}
@proceedings {1296,
	title = {Open Source and Open Data: Business Perspectives from the Frontline},
	year = {2011},
	month = {10/2011},
	pages = {330-333},
	publisher = {Springer},
	abstract = {Open data initiatives on governmental data seem often to be linked to small software companies, which also use and release software under OSS licenses. This paper calls for more research to understand the similarities between open data and open source software vendors. We build a theoretical linkage between the more established OSS research and emerging research on open data in the context of small software companies.},
	author = {Juho Lindman and Tammisto, Yulia}
}
@proceedings {1299,
	title = {Open Source Software for Model Driven Development: A Case Study},
	year = {2011},
	month = {10/2011},
	pages = {348-367},
	publisher = {Springer},
	abstract = {Model Driven Development (MDD) is widely used in the embedded systems domain, and many proprietary and Open Source tools exist that support MDD. The potential for sustainability of such tools needs to assessed prior to any organisational adoption. In this paper we report from a case study conducted in a consultancy company context aiming to investigate Open Source tools for MDD. For the company it was interesting to explore the two Open Source modelling tools Topcased and Papyrus for potential adoption. The focus for our case study is on assessing the health of the ecosystems for the two investigated Open Source projects by means of quantitative analysis of publically available data sources about Open Source projects. The health of ecosystems is an important prerequisite for a long term sustainable OSS (Open Source Software) tool-chain in the MDD area, which can aid strategic decision making for potential adoption within a company context. We have established details on the extent to which developers and users are active in two specific OSS ecosystems, and identified organisational influence for both ecosystems. We find that the investigated tools are promising regarding the health of their ecosystems, and a natural next step for the company would be to proceed with a pilot study in order to analyse the effectiveness of the investigated tools in company contexts.},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn and Mattsson, Anders}
}
@conference {957,
	title = {Assessment of issue handling efficiency},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {94 - 97},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {We mined the issue database of GNOME to assess how issues are handled. How many issues are submitted and resolved? Does the backlog grow or decrease? How fast are issues resolved? Does issue resolution speed increase or decrease over time? In which subproject are issues handled most efficiently? To answer such questions, we apply several visualization and quantification instruments to the raw issue data. In particular, we aggregate issues into four risk categories, based on their resolution time. These categories are the basis both for visualizing and ranking, which are used in concert for issue database exploration.},
	keywords = {bug reports, bug tracking, classification, gnome, msr challenge, visualization},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463292},
	attachments = {https://flosshub.org/sites/flosshub.org/files/94bluijtenMSR2010.pdf},
	author = {Luijten, Bart and Visser, Joost and Zaidman, Andy}
}
@conference {963,
	title = {Automated dependency resolution for open source software},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {130 - 140},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Opportunities for software reuse are plentiful, thanks in large part to the widespread adoption of open source processes and the availability of search engines for locating relevant artifacts. One challenge presented by open source software reuse is simply getting a newly downloaded artifact to build/run in the first place. The artifact itself likely reuses other artifacts, and so depends on their being located to function properly. While merely tedious in the individual case, this can cause serious difficulties for those seeking to study open source software. It is simply not feasible to manually resolve dependencies for thousands of projects, and many forms of analysis require declarative completeness. In this paper we present a method for automatically resolving dependencies for open source software. It works by cross-referencing a project{\textquoteright}s missing type information with a repository of candidate artifacts. We have implemented this method on top of the Sourcerer, an infrastructure for the large-scale indexing and analysis of open source code. The performance of our resolution algorithm was evaluated in two parts. First, for a small number of popular open source projects, we manually examined the artifacts suggested by our system to determine if they were appropriate. Second, we applied the algorithm to the 13,241 projects in the Sourcerer managed repository to evaluate the rate of resolution success. The results demonstrate the feasibility of this approach, as the algorithm located all of the required artifacts needed by 3,904 additional projects, increasing the percentage of declaratively complete projects in Sourcerer from 39\% to 69\%.},
	keywords = {dependencies, java, source code, sourcerer},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463346},
	author = {Ossher, Joel and Bajracharya, Sushil and Lopes, Cristina}
}
@conference {950,
	title = {An extensive comparison of bug prediction approaches},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {31 - 41},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Reliably predicting software defects is one of software engineering{\textquoteright}s holy grails. Researchers have devised and implemented a plethora of bug prediction approaches varying in terms of accuracy, complexity and the input data they require. However, the absence of an established benchmark makes it hard, if not impossible, to compare approaches. We present a benchmark for defect prediction, in the form of a publicly available data set consisting of several software systems, and provide an extensive comparison of the explanative and predictive power of well-known bug prediction approaches, together with novel approaches we devised. Based on the results, we discuss the performance and stability of the approaches with respect to our benchmark and deduce a number of insights on bug prediction models.},
	keywords = {apache, bug reports, eclipse, famix, lucene, mylyn, prediction, scm},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463279},
	attachments = {https://flosshub.org/sites/flosshub.org/files/31dambrosLanzaRobbes31.pdf},
	author = {D{\textquoteright}Ambros, Marco and Lanza, Michele and Robbes, Romain}
}
@conference {1358,
	title = {Extracting source code from e-mails},
	booktitle = {Proceedings of ICPC 2010 (18th IEEE International Conference on Program Comprehension)},
	year = {2010},
	note = {"We want to extract source code fragments from e-mail messages. To do this, we first need to select e-mails that contain source code fragments, and then we extract such fragments from the content in which they are enclosed."

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

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

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

In this work we focus both on classifying e-mails that hold fragments of the source code of a system, and on extracting the source code pieces inside the e-mail. We devised and analyzed a number of lightweight techniques to accomplish these tasks. To assess the validity of our techniques, we manually inspected and annotated a statistically significant number of e-mails from five unrelated open source software systems written in Java. With such a benchmark in place, we measured the effectiveness of each technique in terms of precision and recall.},
	keywords = {argouml, email, freenet, jmeter, mailing lists, mina, natural language, openjpa, source code},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icpc2010.pdf},
	author = {Bacchelli, Alberto and D{\textquoteright}Ambros, Marco and Lanza, Michele}
}
@article {1134,
	title = {A Fistful of Dollars: Financial Rewards, Payment Norms, and Motivation Crowding in Open Source Software Development},
	year = {2010},
	month = {04/2010},
	institution = {ssrn},
	address = {ssrn},
	abstract = {Existing literature on open source software (OSS) maintains that intrinsic motivation and extrinsic financial rewards have a unidimensionally positive effect on the motivation of individual developers. Based on self-determination theory, which underlies most of these studies, we challenge this assumption. We argue that the effect of payment on both intrinsic motivation and total motivation of OSS developers is far more complex. To illustrate our point, we introduce the concept of individuals{\textquoteright} norms about payment to the field of OSS. In doing so, we are able to show that payment norms moderate the effect of payment on intrinsic motivation and total motivation. Conducting a scenario experiment, we find that intrinsic motivation decreases for individuals with norms against payment. This effect becomes even stronger when analyzing for mediation effects. Total motivation is impacted positively by payment, but the effect turns insignificant for individuals with norms for payment. Our findings help explain the results of previous studies in which OSS developers did not seem to be affected by motivation crowding. They further contribute to the more general debate on how to manage individuals in the absence of formal contracts. From a practical perspective, we show that financial rewards may create a management dilemma for OSS project leaders. },
	keywords = {developers, experiment, financial, MOTIVATION},
	author = {Oliver Alexy and Martin Leitner}
}
@conference {1359,
	title = {Linking e-mails and source code artifacts},
	booktitle = {Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - ICSE {\textquoteright}10},
	volume = {1},
	year = {2010},
	note = {"we devised a set of lightweight methods, based on regular expressions, to establish the link between e-mails and software artifacts. We evaluated them in terms of precision and recall considering one single Java system. In this paper we overcome a number of limitations of our previous work, resulting in the following contributions:
{\textbullet} An extensive and publicly available1 benchmark and toolset for recovering traceability links between e-mails and source code artifacts. We created our benchmark by analyzing the mailing lists of six different software systems written in four different programming languages. For each system we manually annotated a statistically significant number of e-mails.
{\textbullet} A comprehensive evaluation of linking techniques. We evaluated and compared, in terms of precision and recall, different linking methods, ranging from lightweight grep-style approaches to more complex approa- ches from the information retrieval (IR) field."},
	month = {05/2010},
	pages = {375-384},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Cape Town, South Africa},
	abstract = {E-mails concerning the development issues of a system constitute an important source of information about high-level design decisions, low-level implementation concerns, and the social structure of developers.

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

In this article we present such a benchmark, which we created through the manual inspection of a statistically significant number of e-mails pertaining to six unrelated software systems. We then use our benchmark to measure the effectiveness of a number of approaches, ranging from lightweight approaches based on regular expressions to full-fledged information retrieval approaches.},
	isbn = {9781605587196},
	doi = {10.1145/1806799.1806855},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	author = {Bacchelli, Alberto and Lanza, Michele and Robbes, Romain}
}
@article {1329,
	title = {Open for Social},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {49 - 64},
	abstract = {Online learning in K-12 and higher education has been growing rapidly, and open source software has the potential to improve the quality of e-learning. This paper describes how FOSS enables turning e-learning from a potentially restrictive framing of the education experience to an emergent and social experience. The authors identify several key elements of the FOSS model that position open source initiatives to contribute to the emergent and social nature of experience in e-learning. The authors also describe several challenges to developing FOSS in a community of educators for e-learning. These elements and challenges are illustrated in a brief case report about the development of an open source software system called Context-aware Activity Notification System (CANS). CANS (http://cansaware.com) is a notification system that integrates with collaborative work and learning systems and is designed around the importance of awareness of user activity, a user{\textquoteright}s social context and personal notification preferences. },
	keywords = {education},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010010104},
	author = {Laffey, James and Schmidt, Matthew and Amelung, Christopher}
}
@article {1336,
	title = {Open Source Software Systems},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {28 - 47},
	abstract = {Complex software systems and the huge amounts of data they produce are becoming an integral part of our organizations. We are also becoming increasingly dependent on high quality software products in our everyday lives. These systems {\textquoteleft}evolve{\textquoteright} as we identify and correct existing defects, provide new functionalities, or increase their nonfunctional qualities - such as security, maintainability, performance, etc. Simultaneously, more software development projects are distributed over multiple locations (often globally) and are often several millions of dollars in development costs. Consequently, as the Internet continually eliminates geographic boundaries, the concept of doing business within a single country has given way to companies focusing on competing in an international marketplace. The digitalization of work and the reorganization of work processes across many organizations have resulted in routine and/or commodity components being outsourced.},
	issn = {1942-3934},
	doi = {10.4018/IJOSSP.2010100103},
	author = {Lenin, R. B. and Ramaswamy, S. and Yu, Liguo and Govindan, R. B.}
}
@conference {949,
	title = {Predicting the severity of a reported bug},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {The severity of a reported bug is a critical factor in deciding how soon it needs to be fixed. Unfortunately, while clear guidelines exist on how to assign the severity of a bug, it remains an inherent manual process left to the person reporting the bug. In this paper we investigate whether we can accurately predict the severity of a reported bug by analyzing its textual description using text mining algorithms. Based on three cases drawn from the open-source community (Mozilla, Eclipse and GNOME), we conclude that given a training set of sufficient size (approximately 500 reports per severity), it is possible to predict the severity with a reasonable accuracy (both precision and recall vary between 0.65-0.75 with Mozilla and Eclipse; 0.70-0.85 in the case of GNOME).},
	keywords = {bug reports, eclipse, gnome, mozilla, severity, text mining},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463284},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1lamkanfiDemeyer1.pdf},
	author = {Lamkanfi, Ahmed and Demeyer, Serge and Giger, Emanuel and Goethals, Bart}
}
@conference {966,
	title = {Replaying IDE interactions to evaluate and improve change prediction approaches},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {161 - 170},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Change prediction helps developers by recommending program entities that will have to be changed alongside the entities currently being changed. To evaluate their accuracy, current change prediction approaches use data from versioning systems such as CVS or SVN. These data sources provide a coarse-grained view of the development history that flattens the sequence of changes in a single commit. They are thus not a valid basis for evaluation in the case of development-style prediction, where the order of the predictions has to match the order of the changes a developer makes. We propose a benchmark for the evaluation of change prediction approaches based on fine-grained change data recorded from IDE usage. Moreover, the change prediction approaches themselves can use the more accurate data to fine-tune their prediction. We present an evaluation procedure and use it on several change prediction approaches, both novel and from the literature, and report on the results.},
	keywords = {cbse, change based software evolution, change prediction, changes, commit, cvs, development history, eclipseeye, ide, mylyn, spyware, svn},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463278},
	attachments = {https://flosshub.org/sites/flosshub.org/files/161Robbes2010changePrediction.pdf},
	author = {Robbes, Romain and Pollet, Damien and Lanza, Michele}
}
@conference {1222,
	title = {Responsiveness as a measure for assessing the health of OSS ecosystems},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	note = {"Data was collected from the GMANE (gmane.org) archives of the SourceForge {\textquotedblleft}Nagios-devel{\textquotedblright} mailing list for the period from January 2004 to October 2009". response time, responsiveness. "},
	month = {05/2010},
	abstract = {The health of an Open Source ecosystem is an important decision factor when considering the adoption of Open Source software or when monitoring a seeded Open Source project. In this paper we introduce responsiveness as a qualitative measure of the quality of replies within mailing lists, which can be used for assessing ecosystem health. We consider one specific metric of responsiveness in this paper, and that is the response time of follow-up messages in mailing lists. We also describe a way for characterising the nature of communication in messages with short and long response times. The approach is tested in the context of the Nagios project, and we particularly focus on the responsiveness for contributors acting in their professional roles as core developers. Our contribution is a step towards a deeper understanding of voluntary support provided in mailing lists of OSS projects.},
	keywords = {email, email archives, gmane, mailing lists, nagios, response time, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm002.pdf},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn and Lings, Brian}
}
@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 {1239,
	title = {Weaving a Semantic Web Across OSS Repositories},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	month = {32/2010},
	pages = {29 - 40},
	abstract = {Several public repositories and archives of {\textquotedblleft}facts{\textquotedblright} about libre software projects, maintained either by open source communities or by research communities, have been flourishing over the Web in recent years. These have enabled new analysis and support for new quality assurance tasks. This paper presents some complementary existing tools, projects and models proposed both by OSS actors or research initiatives that are likely to lead to useful future developments in terms of study of the FLOSS phenomenon, and also to the very practitioners in the FLOSS development projects. A goal of the research conducted within the HELIOS project is to address bugs traceability issues. In this regard, the authors investigate the potential of using Semantic Web technologies in navigating between many different bugtracker systems scattered all over the open source ecosystem. By using Semantic Web techniques, it is possible to interconnect the databases containing data about open-source software projects development, which enables OSS partakers to identify resources, annotate them, and further interlink those using dedicated properties and collectively designing a distributed semantic graph.},
	keywords = {archive, bug, bugtracker, database, debian, forge, interoperability, ontology, OSLC-CM, RDF, repository of repositories, semantic, semantic Web},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010040103},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd2009-olivier-berger.pdf},
	author = {Olivier Berger and Valentin Vlasceanu and Christian Bac and Quang Vu Dang and Lauriere, St{\'e}phane}
}
@conference {1360,
	title = {Benchmarking Lightweight Techniques to Link E-Mails and Source Code},
	booktitle = {2009 16th Working Conference on Reverse Engineering},
	year = {2009},
	note = {"We present different lightweight approaches that, exploiting the specific characteristics of e-mails and the ones of the source code, are capable of establishing a bi-directional link between source code entities and e-mails"

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

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

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

To overcome this issue, we manually inspected a statistically significant number of e-mails pertaining to the ArgoUML system. Based on this benchmark, we present a variety of lightweight techniques to assign e-mails to software artifacts and measure their effectiveness in terms of precision and recall.},
	keywords = {argouml, email, mailing lists},
	isbn = {978-0-7695-3867-9},
	doi = {10.1109/WCRE.2009.44},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wcre2009.pdf},
	author = {Bacchelli, Alberto and D{\textquoteright}Ambros, Marco and Lanza, Michele and Robbes, Romain}
}
@conference {574,
	title = {Beyond the Business Model: Incentives for Organizations to Publish Software Source Code},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {47 - 56},
	publisher = {Springer},
	organization = {Springer},
	chapter = {6},
	abstract = {The software stack opened under Open Source Software (OSS) licenses is growing rapidly. Commercial actors have released considerable amounts of previously proprietary source code. These actions beg the question why companies choose a strategy based on giving away software assets? Research on outbound OSS approach has tried to answer this question with the concept of the {\textquotedblleft}OSS business model{\textquotedblright}. When studying the reasons for code release, we have observed that the business model concept is too generic to capture the many incentives organizations have. Conversely, in this paper we investigate empirically what the companies{\textquoteright} incentives are by means of an exploratory case study of three organizations in different stages of their code release. Our results indicate that the companies aim to promote standardization, obtain development resources, gain cost savings, improve the quality of software, increase the trustworthiness of software, or steer OSS communities. We conclude that future research on outbound OSS could benefit from focusing on the heterogeneous incentives for code release rather than on revenue models.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Beyond\%20the\%20Business\%20Model.pdf},
	author = {Juho Lindman and Juutilainen, Juha-Pekka and Rossi, Matti}
}
@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 {931,
	title = {Evaluating process quality in GNOME based on change request data},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {95 - 98},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {The lifecycle of defects reports and enhancement requests collected in the Bugzilla database of the GNOME project provides valuable information on the evolution of the change request process and for the assessment of process quality in the GNOME sub projects. We present a quality model for the analysis of quality characteristics that is based on evaluating metrics on the Bugzilla database, and illustrate it with a comparative evaluation for 25 of the largest products within GNOME.},
	keywords = {bugzilla, bugzillametrics.org, change analysis, change history, gnome, msr challenge, qmetric},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069485},
	attachments = {https://flosshub.org/sites/flosshub.org/files/95ProcessQualityInGNOME.pdf},
	author = {Schackmann, Holger and Lichter, Horst}
}
@conference {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 {602,
	title = {A Joint Workshop of QACOS and OSSPL},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {357 - 358},
	publisher = {Springer},
	organization = {Springer},
	chapter = {34},
	abstract = {The OSS movement, which originated from a pragmatic need to share code among individuals, has grown to become a major force behind inter-organizational reuse of platforms, components and code. The use of open source software to build single or family of systems (i.e., product line development) appears to be a profitable way to quality software products. On the other hand, because of the diverse use of open source software, product line development is an attractive way of working in open source
communities. The configuration mechanisms used in open source communities may be applicable within software product lines variability management. In addition, product line organizations are usually involved in distributed development, which works very efficiently within open source communities, leading to high quality products. However, at present, there is limited interaction between the open source and product line development communities.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_34},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Joint\%20Workshop\%20of\%20QACOS.pdf},
	author = {Ali Babar, Muhammad and Lundell, Bj{\"o}rn and van der Linden, Frank}
}
@conference {608,
	title = {Libre Software in Spanish Public Administrations},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {366 - 366},
	publisher = {Springer},
	organization = {Springer},
	chapter = {40},
	abstract = {Libre software started to be used in Public Administrations in Spain during the 1990s, in some isolated but interesting experiences.During the early 2000s, and specially in some regional governments, libre software started to be considered as an integral part of ITrelated policies. In 2007, it was evident that many experiences related to libre software were running in Public Administrations with different levels of success. However, no study had looked into the details of these experiences, and no comprehensive analysis had been performed to better understand the different factors that affect them.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_40},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Libre\%20Software.pdf},
	author = {Ortega, Felipe and Lafuente, Isabel and Gato, Jose and Gonz{\'a}lez-Barahona, Jes{\'u}s}
}
@conference {935,
	title = {Mining search topics from a code search engine usage log},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {111 - 120},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {We present a topic modeling analysis of a year long usage log of Koders, one of the major commercial code search engines. This analysis contributes to the understanding of what users of code search engines are looking for. Observations on the prevalence of these topics among the users, and on how search and download activities vary across topics, leads to the conclusion that users who find code search engines usable are those who already know to a high level of specificity what to look for. This paper presents a general categorization of these topics that provides insights on the different ways code search engine users express their queries. The findings support the conclusion that existing code search engines provide only a subset of the various information needs of the users when compared to the categories of queries they look at.},
	keywords = {analysis, black duck, koders, log, logfile, search, source code},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069489},
	author = {Bajracharya, Sushil and Lopes, Cristina}
}
@conference {932,
	title = {Mining the coherence of GNOME bug reports with statistical topic models},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {99 - 102},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {We adapt latent Dirichlet allocation to the problem of mining bug reports in order to define a new information-theoretic measure of coherence. We then apply our technique to a snapshot of the GNOME Bugzilla database consisting of 431,863 bug reports for multiple software projects. In addition to providing an unsupervised means for modeling report content, our results indicate substantial promise in applying statistical text mining algorithms for estimating bug report quality. Complete results are available from our supplementary materials Web site at http://sourcerer.ics.uci.edu/msr2009/gnome_coherence.html.},
	keywords = {bug reports, bugzilla, gnome, msr challenge, quality, sourcerer},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069486},
	author = {Linstead, Erik and Baldi, Pierre}
}
@article {1339,
	title = {Open Source Software Governance Serving Technological Agility},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {14 - 27},
	abstract = {The development of open source software is currently arousing increasing interest in the IT world. This research inquires some specific paths enlarging the traditional view over open source software in inquiring the US Department of Defense (DoD) and the dynamics associated its front- and back-office activities. We explain how distinguishing basic administration from operational constraints and weapon R\&D dynamics introduces specific governance concerns among public and private stakeholders. By no longer defining open source solutions as mere goods, but as services characterized by a flow of knowledge, we particularly highlight new emerging strategies of technological acquisition. Our analysis leads to revise the traditional role focusing mainly on cost issues and introduces open source software with distinctive properties serving the management of innovation and technological agility at the level of complex systems, exemplified here with the constraints associated to weapon systems and the Network centric warfare doctrine},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009040102},
	author = {Le Texier, Thomas and Versailles, David W.}
}
@conference {596,
	title = {Openness to Standard Document Formats in Swedish Public Sector Organisations},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {320 - 329},
	publisher = {Springer},
	organization = {Springer},
	chapter = {28},
	abstract = {There is a strong movement in Europe to promote products that support open, well-documented standards. Directives and proposals at European and national levels have been developed in this area. There is in particular an increasing recognition of the need for governmental organisations to support and promote standard document formats. This vision can stand in stark contrast with the reality of those document formats which can currently be accepted and produced by those organisations. In this paper we address the question: to what extent can and do Swedish governmental organisations respond appropriately when presented with a document in a format that conforms to an open standard? We find that a small minority of organisations can actually do so, whereas all are willing and able to accept documents in a proprietary format. The study also highlights a lack of transparency in organisations regarding formats which should be accepted and used for communication with the general public.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_28},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Openness\%20to\%20Standard\%20Document\%20Formats.pdf},
	author = {Lundell, Bj{\"o}rn and Lings, Brian}
}
@conference {611,
	title = {Panel: Governance in Open Source Projects and Communities},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {370 - 370},
	publisher = {Springer},
	organization = {Springer},
	chapter = {43},
	abstract = {{\textquotedblleft}Although considerable research has been devoted to the growth and expansion of open source communities and the comparison between the efficiency of corporate structures and community structures in the field of software development, rather less attention has been paid to their governance structures (control, monitoring, supervision){\textquotedblright} (Lattemann and Stieglitz 2005).
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_43},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Panel\%20Governnance.pdf},
	author = {Bolici, Francesco and de Laat, Paul and Ljungberg, Jan and Pontiggia, Andrea and Rossi Lamastra, Cristina}
}
@conference {610,
	title = {Panel: Open Source in the Public Sector},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {368 - 369},
	publisher = {Springer},
	organization = {Springer},
	chapter = {42},
	abstract = {Open Source Software (OSS) is becoming mainstream, and it is perhaps not surprising that public sector organisations seek to explore the potential of OSS in financially difficult times. Today, OSS has become an issue of strategic importance for many public sector organisations. In addition, related to OSS, many organisations and governments are also acknowledging Open Standards as important for addressing various lock-in scenarios.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_42},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Panel\%20Open\%20Source.pdf},
	author = {Lundell, Bj{\"o}rn and Amundsen, Morten and Ghosh, Rishab and Hardy, Jean-Luc and Sj{\"o}sw{\"a}rd, Per-Ola}
}
@conference {593,
	title = {Peeling the Onion},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {284 - 297},
	publisher = {Springer},
	organization = {Springer},
	chapter = {25},
	abstract = {According to the now widely accepted {\textquotedblleft}onion-model{\textquotedblright} of the organization of open source software development, an open source project typically relies on a core of developers that is assisted by a larger periphery of users. But what does the role of the periphery consist of? Raymond{\textquoteright}s Linus{\textquoteright}s Law which states that {\textquotedblleft}given enough eyeballs all bugs are shallow{\textquotedblright} suggests at least one important function: the detection of defects. Yet, what are the ways through which core and periphery interact with each other? With the help of text-mining methods, we study the treatment of bugs that affected the Firefox Internet browser as reflected in the discussions and actions recorded in Mozilla{\textquoteright}s issue tracking system Bugzilla. We find various patterns in the modes of interactions between core and peripheral members of the community. For instance, core members seem to engage more frequently with the periphery when the latter proposes a solution (a patch). This leads us to conclude that Alan Cox{\textquoteright}s dictum {\textquotedblleft}show me the code{\textquotedblright}, perhaps even more than Linus{\textquoteright}s law, seems to be the dominant rule that governs the development of software like Firefox.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_25},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Peeling\%20the\%20Onion.pdf},
	author = {Masmoudi, H{\'e}la and den Besten, Matthijs and de Loupy, Claude and Jean-Michel Dalle}
}
@booklet {859,
	title = {Perceptions and Practices of Usability in the Free/Open Source Software (FOSS) Community},
	number = {CS-2009-26},
	year = {2009},
	publisher = {David R. Cheriton School of Computer Science, University of Waterloo},
	author = {Terry, M. and Kay, M. and Lafreniere, B.}
}
@conference {586,
	title = {Quality of Open Source Software: The QualiPSo Trustworthiness Model},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {199 - 212},
	publisher = {Springer},
	organization = {Springer},
	chapter = {18},
	abstract = {Trustworthiness is one of the main issues upon which the decision whether to adopt an Open-Source Software (OSS) product is based. The work described here is part of an activity that has the goals of 1) defining an adequate notion of trustworthiness of software products and artifacts and 2) identifying a number of factors that influence it. Specifically, this paper reports about the identification of the {\textquotedblleft}dimensions{\textquotedblright} of trustworthiness, i.e., of the high-level qualities that software products and artefacts have to posses in order to be considered trustworthy. These dimensions are described by means of a conceptual model of trustworthiness, which comprises the representation of the factors that affect the user{\textquoteright}s perception of trustworthiness, as well as the objective characteristics of the products that contribute to {\textquotedblleft}build{\textquotedblright} trustworthi-ness. The aforementioned model is equipped with a measurement plan that de-scribes, at the operational level, how to perform the evaluation of the trustwor-thiness of OSS products. The proposed model provides the basis to build quantitative models of the trustworthiness of OSS products and artifacts that are able to explain the relationships between the (objectively observable) characteristics of OSS products and the level of trustworthiness perceived by the users of such products.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Quality\%20of\%20Open\%20Source\%20Software.pdf},
	author = {del Bianco, Vieri and Lavazza, Luigi and Morasca, Sandro and Taibi, Davide}
}
@conference {945,
	title = {SourcererDB: An aggregated repository of statically analyzed and cross-linked open source Java projects},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {183 - 186},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {The open source movement has made vast quantities of source code available online for free, providing an extremely large dataset for empirical study and potential resuse. A major difficulty in exploiting this potential fully is that the data are currently scattered between competing source code repositories, none of which are structured for empirical analysis and cross-project comparison. As a result, software researchers and developers are left to compile their own datasets, resulting in duplicated effort and limited results. To address this challenge, we built SourcererDB, an aggregated repository of statically analyzed and cross-linked open source Java projects. SourcererDB contains local snapshots of 2,852 Java projects taken from Sourceforge, Apache and Java.net. These projects are statically analyzed to extract rich structural information, which is then stored in a relational database. References to entities in the 16,058 external jars are resolved and grouped, allowing for cross-project usage information to be accessed easily. This paper describes: (a) the mechanism for resolving and grouping these cross-project references, (b) the structure of and the metamodel for the SourcererDB repository, and (d) end-user dataset access mechanisms. Our goal in building SourcererDB is to provide a rich dataset of source code to facilitate the sharing of extracted data and to encourage reuse and repeatability of experiments.},
	keywords = {apache, integration, java, java.net, project, repository, sourceforge, SourcererDB},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069501},
	author = {Ossher, Joel and Bajracharya, Sushil and Linstead, Erik and Baldi, Pierre and Lopes, Cristina}
}
@conference {1066,
	title = {SourcererDB: An aggregated repository of statically analyzed and cross-linked open source Java projects},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)},
	year = {2009},
	pages = {183 - 186},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {The open source movement has made vast quantities of source code available online for free, providing an extremely large dataset for empirical study and potential re-use. A major difficulty in exploiting this potential fully is that the data are currently scattered between competing source code repositories, none of which are structured for empirical analysis and cross-project comparison. As a result, software researchers and developers are left to compile their own datasets, resulting in duplicated effort and limited results. To address this challenge, we built SourcererDB, an aggregated repository of statically analyzed and cross-linked open source Java projects. SourcererDB contains local snapshots of 2,852 Java projects taken from Sourceforge, Apache and Java.net. These projects are statically analyzed to extract rich structural information, which is then stored in a relational database. References to entities in the 16,058 external jars are resolved and grouped, allowing for cross-project usage information to be accessed easily. This paper describes: (a) the mechanism for resolving and grouping these cross-project references, (b) the structure of and the metamodel for the SourcererDB repository, and (d) end-user dataset access mechanisms. Our goal in building SourcererDB is to provide a rich dataset of source code to facilitate the sharing of extracted data and to encourage reuse and repeatability of experiments.},
	keywords = {apache, java, java.net, source code, sourceforge, sourcerer},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069501},
	author = {Ossher, Joel and Bajracharya, Sushil and Linstead, Erik and Baldi, Pierre and Lopes, Cristina}
}
@inbook {855,
	title = {Understanding Requirements for Open Source Software},
	booktitle = {Design Requirements Engineering: A Ten-Year Perspective},
	series = {Lecture Notes in Business Information Processing},
	volume = {14},
	year = {2009},
	pages = {467-494},
	publisher = {Springer-Verlag},
	organization = {Springer-Verlag},
	author = {Walt Scacchi},
	editor = {Lyytinen, K. and Loucopoulos, P. and Mylopoulos, J. and Robinson, W.}
}
@conference {938,
	title = {Using association rules to study the co-evolution of production \& test code},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {151 - 154},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Unit tests are generally acknowledged as an important aid to produce high quality code, as they provide quick feedback to developers on the correctness of their code. In order to achieve high quality, well-maintained tests are needed. Ideally, tests co-evolve with the production code to test changes as soon as possible. In this paper, we explore an approach based on association rule mining to determine whether production and test code co-evolve synchronously. Through two case studies, one with an open source and another one with an industrial software system, we show that our association rule mining approach allows one to assess the co-evolution of product and test code in a software project and, moreover, to uncover the distribution of programmer effort over pure coding, pure testing, or a more test-driven-like practice.},
	keywords = {association rules, checkstyle, source code, unit test},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069493},
	attachments = {https://flosshub.org/sites/flosshub.org/files/151UsingAssociation.pdf},
	author = {Lubsen, Zeeger and Zaidman, Andy and Pinzger, Martin}
}
@conference {933,
	title = {Visualizing Gnome with the Small Project Observatory},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {103 - 106},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {We analyzed the gnome family of systems with the small project observatory, our online ecosystem visualization platform. We begin by briefly introducing the model of SPO. We then observe and discuss several phases in the activity of the gnome ecosystem. We follow and look at how the contributors are distributed between writing source code and doing other activities such as internationalization. We end with a visual overview of the activity of more than 900 contributors in the 10 years of existence of gnome.},
	keywords = {bugzilla, contributions, gnome, msr challenge, spo, visualization},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069487},
	attachments = {https://flosshub.org/sites/flosshub.org/files/103Lung2009a.pdf},
	author = {Lungu, Mircea and Malnati, Jacopo and Lanza, Michele}
}
@conference {1205,
	title = {Weaving~a~Semantic~Web~across~OSS~repositories: a~spotlight~on~bts-link,~UDD,~SWIM},
	booktitle = {4th Workshop on Public Data about Software Development (WoPDaSD 2009)},
	year = {2009},
	note = {position paper; non-experimental},
	abstract = {Several  public  repositories  and  archives  of  facts  about  libre software  projects,  developed either  by open  source  communities  or by research communities,  have been flourishing over  the Web in  the  recent  years.  These  enable  new analysis  and  support  new quality assurance tasks. 

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

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

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

The  HELIOS team welcomes  comments  on the  future  paths  that  can  be  considered  in  using  the  Semantic  Web  approach  for improving these projects. },
	keywords = {bts-link, bug tracker, bugzilla, debian, ecosystem, helios, mandriva, semantic Web, swim, udd},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HELIOS-WOPDASD-improved-Olivier.pdf},
	author = {Olivier Berger and Valentin Vlasceanu and Christian Bac and Lauri{\`e}re, St{\'e}phane}
}
@conference {849,
	title = {Is Wikipedia Growing a Longer Tail?},
	booktitle = {ACM 2009 International Conference on Supporting Group Work},
	year = {2009},
	month = {05/10/2009},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Sanibel Island, FL},
	author = {Lam, S.K. and Riedl, J.}
}
@conference {604,
	title = {Workshop {\textendash} Serious Games and Open Source: Practice and Futures},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {361 - 362},
	publisher = {Springer},
	organization = {Springer},
	chapter = {36},
	abstract = {Computer games are increasingly used throughout our society with people playing on the bus, at home and at work. Computer games thus affect larger and larger number of people and areas in the society of today. There are even scholars who advocate that games create better environments for learning than traditional classrooms. This situation motivates the use of games and game technology for additional purposes, e.g. education, training, health care or marketing.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/.1007/978-3-642-02032-2_36},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Workshop\%20Serious\%20Games\%20and\%20Open\%20Source.pdf},
	author = {Backlund, Per and Lundell, Bj{\"o}rn and Walt Scacchi}
}
@conference {563,
	title = {Applying Open Source Development Practices Inside a Company},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {381 - 387},
	publisher = {Springer},
	organization = {Springer},
	chapter = {36},
	abstract = {Open Source Software development is seen as a panacea by many companies. The promise of community-style development, innovation and cost savings drive the wider adoption of OSS in companies. However, it is still difficult to institutionalize the open and agile culture of sharing innovation especially into larger departmentalized organizations. The aim of this research paper is to investigate the characteristics of one successful OSS development implementation approach limited inside a company (Inner source). Based on our data, we argue that there are possibilities for employing OSS as a new kind of development process within a company and leveraging thus the innovation potential inside the company.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_36},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Applying\%20Open\%20Source\%20Development.pdf},
	author = {Juho Lindman and Rossi, Matti and Marttiin, Pentti}
}
@conference {548,
	title = {Archetypal Internet-Scale Source Code Searching},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {257 - 263},
	publisher = {Springer},
	organization = {Springer},
	chapter = {21},
	abstract = {Programmers often search for Open Source code to use in their projects. To understand how and why programmers search for source code, we onducted a web-based survey and collected data from 69 respondents, including 58 specific examples of searches. Analyzing these anecdotes, we found that they could be categorized along two orthogonal dimensions: motivation (reuse vs. reference example) and size of search target. The targets of these searches could range in size from a block (a few lines of code) to a subsystem (e.g. library or API), to an entire system. Within these six combinations of motivations and target sizes, nine repeating motifs, or archetypes, were created to characterize Internet-scale source code searching. Tools used for searching and the criteria for selecting a component are also discussed. We conclude with guidance on how these archetypes can inform better evaluation of Internet-scale code search engines, as well as the design of new features for these tools.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_21},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Archetypal\%20Internet-Scale\%20Source.pdf},
	author = {Umarji, Medha and Sim, Susan and Lopes, Crista}
}
@conference {556,
	title = {Assessing Innovation in the Software Sector: Proprietary vs. FOSS Production Mode. Preliminary Evidence from the Italian Case},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {325 - 331},
	publisher = {Springer},
	organization = {Springer},
	chapter = {29},
	abstract = {Innovation in the software sector is a widely debated issue. Which are the most important dimensions to assess innovation in this field? Can we measure innovative processes carried out by software companies and what kind of innovation do they develop? Are FOSS solutions more innovative than proprietary ones? These are the research questions we endeavor to answer in this paper providing some empirical evidence, obtained using an original methodology of collecting experts{\textquoteright} evaluations on the innovation level of 134 solutions provided by a group of Italian Small and Medium Enterprises.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Assessing\%20Innovation\%20in\%20the\%20Software\%20Sector.pdf},
	author = {Dario Lorenzi and Cristina Rossi}
}
@conference {flosswp408,
	title = {Asynchronous Decision-Making in Distributed Teams},
	booktitle = {Computer Supported Cooperative Work 2008},
	year = {2008},
	month = {July},
	pages = {1{\textendash}2},
	abstract = {Extensive use of CSCW applications can influence group decision-making practices. Unlike previous research focused on the influence of synchronous ICTs, our study examines how group decisions are made in asynchronous communication channels. Our inductive qualitative analysis of 360 decision episodes of six FLOSS projects revealed diversity in decision-making practices, which appears to be related to differences in project effectiveness and task type. We also find that standardization of procedures through CSCW tools transforms the nature of some software development work from non-routine to standard procedure.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CSCW2008FLOSSposter_sub.pdf , https://flosshub.org/sites/flosshub.org/files/CSCW2008Poster11x17sub.pdf},
	author = {Li, Qing and Robert Heckman and Eileen Allen and Kevin Crowston and Eseryel, U. Yeliz and James Howison and Andrea Wiggins}
}
@conference {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.}
}
@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 {SGKL09,
	title = {Evaluating the Quality of Open Source Software},
	booktitle = {Electronic Notes in Theoretical Computer Science},
	volume = {233},
	year = {2008},
	note = {"the software source code and the associated data stored in the version control system, the bug tracking databases, the mailing lists, and the wikis allow us to evaluate quality in a transparent way"
"The data collection system collects the raw data from open source projects"
Mailing lists are measured in: Number of unique subscribers, Number of messages in user/support list per month, Number of messages in developers list per month, Average thread depth},
	month = {03/2009},
	pages = {5{\textendash}28},
	publisher = {The Reengineering Forum},
	organization = {The Reengineering Forum},
	abstract = {Traditionally, research on quality attributes was either kept under wraps within the organization that performed it, or carried out by outsiders using narrow, black-box techniques. The emergence of open source software has changed this picture allowing us to evaluate both software products and the processes that yield them. Thus, the software source code and the associated data stored in the version control system, the bug tracking databases, the mailing lists, and the wikis allow us to evaluate quality in a transparent way. Even better, the large number of (often competing) open source projects makes it possible to contrast the quality of comparable systems serving the same domain. Furthermore, by combining historical source code snapshots with significant events, such as bug discoveries and fixes, we can further dig into the causes and effects of problems. Here we present motivating examples, tools, and techniques that can be used to evaluate the quality of open source (and by extension also proprietary) software. },
	keywords = {bug tracking system, email, email archives, mailing list, metrics, open source, process quality attributes, product quality attributes, source code, SQO-OSS, wiki},
	doi = {10.1016/j.entcs.2009.02.058},
	url = {http://www.dmst.aueb.gr/dds/pubs/conf/2008-SQM-SQOOSS/html/SGKL09.html},
	attachments = {https://flosshub.org/sites/flosshub.org/files/entcs-sqooss.pdf},
	author = {Diomidis Spinellis and Gousios, Georgios and Vassilios Karakoidas and Panagiotis Louridas and Paul J. Adams and Samoladas, Ioannis and Ioannis Stamelos}
}
@conference {972,
	title = {Extracting structural information from bug reports},
	booktitle = {Proceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {27-30},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {In software engineering experiments, the description of bug reports is typically treated as natural language text, although it often contains stack traces, source code, and patches. Neglecting such structural elements is a loss of valuable information; structure usually leads to a better performance of machine learning approaches. In this paper, we present a tool called infoZilla that detects structural elements from bug reports with near perfect accuracy and allows us to extract them. We anticipate that infoZilla can be used to leverage data from bug reports at a different granularity level that can facilitate interesting research in the future.},
	keywords = {bug reports, eclipse, enumerations, infozilla, natural language, patches, source code, stack trace},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370757},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p27-bettenburg.pdf},
	author = {Premraj, Rahul and Zimmermann, Thomas and Kim, Sunghun and Bettenburg, Nicolas}
}
@article {862,
	title = {Getting Clear About Communities in Open Innovation},
	journal = {Industry \& Innovation},
	volume = {15},
	year = {2008},
	month = {4/2008},
	pages = {223 - 231},
	author = {Joel West and Lakhani, Karim}
}
@booklet {494,
	title = {Guest Editorial of the Special Issue on Socio-technical Dynamics in the Free/Libre Open Source Software (FLOSS) Social World},
	year = {2008},
	month = {Jan},
	abstract = {This special issue is the first volume in academia dedicated to a qualitative inquiry on dynamics in the FLOSS development and implementation, even if it is not alone in this endeavour (see e.g., Coleman, 2004; Kelty, 2005). Such a qualitative inquiry challenges the universally vocal and normative way of depicting FLOSS culture and practices (e.g., a homogeneous gift-giving and volunteering culture). The special issue encourages a practice-based and holistic view to exploring multiple cultures and practices in developing, localising, appropriating, and customising FLOSS. It also addresses the diversity in FLOSS communities through asking how seemingly global FLOSS cultures are translated into different contexts and locales. The importance of such an emphasis on how FLOSS technologies and practices diffract as they travel is nicely encapsulated by Haraway (1992) in her optic metaphor of white light that diffracts through a prism and becomes a rainbow. In light of this metaphor, a piece of FLOSS software is never really the same; when reproduced and shared, it is both the same (the standard) and something else in the mean time.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Guest_editorial_Lin\%26Risan.pdf},
	author = {Yu-wei Lin and Lars Risan}
}
@conference {536,
	title = {Mining for Practices in Community Collections: Finds From Simple Wikipedia},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {105 - 120},
	publisher = {Springer},
	organization = {Springer},
	chapter = {9},
	abstract = {The challenges of commons based peer production are usually associated with the development of complex software projects such as Linux and Apache. But the case of open content production should not be treated as a trivial one. For instance, while the task of maintaining a collection of encyclopedic articles might seem negligible compared to the one of keeping together a software system with its many modules and interdependencies, it still poses quite demanding problems. In this paper, we describe the methods and practices adopted by Simple Wikipedia to keep its articles easy to read. Based on measurements of article readability and similarity, we conclude that while the mechanisms adopted by the community had some effect, in the long run more efforts and new practices might be necessary in order to maintain an acceptable level of readability in the Simple Wikipedia collection.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Mining\%20for\%20Practices.pdf},
	author = {den Besten, Matthijs and Rossi, Alessandro and Gaio, Loris and Loubser, Max and Jean-Michel Dalle}
}
@conference {547,
	title = {An Open Integrated Environment for Transparent Fuzzy Agents Design},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {249 - 255},
	publisher = {Springer},
	organization = {Springer},
	chapter = {20},
	abstract = {Recently, computational agents received significant attention in computer science research community. In fact, intelligent agents is a powerful artificial intelligence technology showing considerable promise as a new paradigm for mainstream software development and able to offer new ways of abstraction, decomposition, and organization that fit well with our natural view of the world. However, despite their promise, intelligent agents are still scarce in the market place. A key reason for this is that developing intelligent agent software requires significant training and skill. Artificial Intelligence methodologies and computer networking tools represent the necessary basic knowledge to design and implement advanced agents oriented systems. This papers introduces an integrated development environment supporting the agents developers to design fuzzy-based agents in a simple and fast way. Proposed framework has been realized by integration of theoretical methodologies as fuzzy logic and labeled tree, together with OSS tools as JaxMe2.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/An\%20Open\%20Integrated\%20Environment.pdf},
	author = {Acampora, Giovanni and Loia, Vincenzo}
}
@conference {568,
	title = {Open Source Environments for Collaborative Experiments in e-Science},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {415 - 416},
	publisher = {Springer},
	organization = {Springer},
	chapter = {41},
	abstract = {Open Source Software (OSS) for e-Science should make reference to the paradigm of a distributed surrounding over a multi system mix of Web Services and Grid technologies, allowing data exchanging through services, according to standards in the area of the Grid and of Service Oriented Computing (SOC). In fact, biologists, medical doctors, and scientists are often involved in time consuming experiments and are aware of the degree of difficulty in validating or rejecting a given hypothesis by lab experiments. The benefits of OSS for e-Science consider that as many operating nodes as possible can work cooperatively sharing data, resources, and software, thus avoiding the bottleneck of licenses for distributed use of tools needed to perform cooperative scientific experiments. In particular, this chapter presents an architecture based on nodes equipped with a Grid and with Web Services in order to access OSS, showing how scientific experiments can be enacted through the use of a cooperation among OSS sites. Such a choice, besides reducing the cost of the experiments, would support distributed introduction of OSS among other actors of the dynamical networks, thus supporting the awareness about OSS and their diffusion. An OSS environment for cooperative scientific experiments (e-experiments) can effectively support the distributed execution of different classes of experiments, from visualization to model identification through clustering and rules generation, in various application fields, such as bioinformatics, neuro-informatics, tele-monitoring,or drug discovery. By applying Web Services and Grid computing, an experiment or a simulation can be executed in a cooperative way on various computation nodes of a network equipped with OSS, allowing data exchange among researchers. Our environment  formalizes experiments as cooperative services on various computational nodes of a grid network. Basic elements are models, languages, and support tools creating a virtual
network of organizational responsibility of the global experiments, according to rules under which each node can execute local services to be accessed by other nodes in order to achieve the whole experiment{\textquoteright}s results.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_41},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Environments.pdf},
	author = {Bosin, Andrea and Dess{\'\i}, Nicoletta and Fugini, Maria and Liberati, Diego and Pes, Barbara}
}
@conference {567,
	title = {Panel: Opportunities and Risks for Open Source Software in Industry},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {413 - 414},
	publisher = {Springer},
	organization = {Springer},
	chapter = {40},
	abstract = {Open Source Software (OSS) is a multi-faceted phenomenon which has become an issue of strategic importance for many commercial organisations. Stemming from an ideological issue, with emphasis on freedom and community values, we have recently seen a broader interest in the Open Source phenomenon amongst practitioners in many companies. A number of SMEs and large companies are currently exploring the potential of Open Source, and for some it has become core to their business and development activities.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_40},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Panel\%20Opportunities\%20\%26\%20Risks.pdf},
	author = {Feller, Joseph and Lundell, Bj{\"o}rn and Marttiin, Pentti and Walt Scacchi and Schellingerhout, Nico}
}
@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}
}
@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 {564,
	title = {Towards The Evaluation of OSS Trustworthiness: Lessons Learned From The Observation of Relevant OSS Projects},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {389 - 395},
	publisher = {Springer},
	organization = {Springer},
	chapter = {37},
	abstract = {To facilitate the adoption of open-source software (OSS) in industry, it is important to provide potential users (i.e., those who could decide to adopt OSS) with the means for evaluating the trustworthiness of OS products. This paper presents part of the work done in the QualiPSo project for this purpose. A set of factors that are believed to affect the perception of trustworthiness are introduced. In order to test the feasibility of deriving a correct, complete and reliable evaluation of trustworthiness on the basis of these factors, a set of well-known OSS projects have been chosen. Then, the possibility to assess the proposed factors on each project was verified: not all the factors appear to be observable or measurable. The paper reports what information is available to support the evaluation and what is not. This knowledge is considered to be useful to users, who are warned that there are still dark areas in the characterization of OSS products, and to developers, who should provide more data and characteristics on their products in order to support their adoption.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Toward\%20the\%20Evaluation\%20of\%20OSS.pdf},
	author = {Taibi, Davide and del Bianco, Vieri and Carbonare, Davide and Lavazza, Luigi and Morasca, Sandro}
}
@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 {882,
	title = {Creating, Destroying, and Restoring Value in Wikipedia},
	booktitle = {Conference on Supporting Group Work},
	year = {2007},
	author = {Reid Priedhorsky and Jilin Chen and Shyong K. Lam and Katherine Panciera and Loren Terveen and John Riedl}
}
@proceedings {118,
	title = {Design architecture, developer networks and performance of open source software projects},
	year = {2007},
	keywords = {NotreDameArchive},
	author = {Xiang Liu and Bala Iyer}
}
@article {flosswp332,
	title = {Do firms take part in the projects of the OS community. Some preliminary evidence and a research agenda},
	year = {2007},
	month = {January},
	abstract = {The Open Source (OS) software has progressively gained economic importance in recent years, and more and more commercial firms are getting involved, to various extents, in the OS movement. While a number of studies have investigated motivations and business models of OS-based software companies, very few works have examined whether and how firms actively participate to open projects. This paper contributes to the literature by providing empirical evidence on the role and the activities of software houses in community developed projects. The research also proposes an original methodology of large-scale primary data collection from OS project repositories and linked Web sites. The findings show how different today???s OS movement is from its origins and how important firm involvement has become, not only numerically but also for the deepness of its impact on community projects. Finally, further research developments are suggested.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper_firm_involvement_MIT.pdf},
	author = {Andrea Bonaccorsi and Dario Lorenzi and Monica Merito and Cristina Rossi}
}
@conference {643,
	title = {Effect of Coupling on Defect Proneness in Evolutionary Open-Source Software Development},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {271 - 276},
	publisher = {Springer},
	organization = {Springer},
	chapter = {27},
	abstract = {Previous research on closed-source software found that highly coupled software modules were more defect prone, which makes it important to understand the effect of coupling on defect proneness in open-source software (OSS) projects. For this purpose, we used Cox proportional hazards modeling with recurrent events. We found that the effect of coupling was significant, and we quantified this effect on defect proneness.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Effect\%20of\%20Coupling\%20on\%20Defect.pdf},
	author = {G{\"u}nes Koru, A. and Zhang, Dongsong and Liu, Hongfang}
}
@conference {622,
	title = {Emergent Decision-Making Practices in Free/Libre Open Source Software (Floss) Development Teams},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {71 - 84},
	publisher = {Springer},
	organization = {Springer},
	chapter = {6},
	abstract = {We seek to identify work practices that make Free/Libre Open Source Software (FLOSS) development teams effective. Particularly important to team effectiveness is decision making. In this paper, we report on an inductive qualitative analysis of 360 decision episodes of six FLOSS development teams. Our analysis revealed diversity in decision-making practices that seem to be related to differences in overall team characteristics and effectiveness.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Emergent\%20Decision-Making.pdf},
	author = {Robert Heckman and Kevin Crowston and Eseryel, U. and Howison, James and Eileen Allen and Li, Qing}
}
@conference {1003,
	title = {Evaluating the Harmfulness of Cloning: A Change Based Experiment},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {18 - 18},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Cloning is considered a harmful practice for software maintenance because it requires consistent changes of the entities that share a cloned fragment. However this claim has not been refuted or confirmed empirically. Therefore, we have developed a prototype tool, CloneTracker, in order to study the rate of change of applications containing clones. This paper describes CloneTracker and illustrates its preliminary application on a case study.},
	keywords = {ccfinder, clone, clones, clonetracker, cloning, ctags, cvs, dnsjava, maintenance, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.8},
	author = {Lozano, Angela and Wermelinger, Michel and Nuseibeh, Bashar}
}
@booklet {491,
	title = {Free/libre open source software implementation in schools: Evidence from the field and implications for the future},
	year = {2007},
	month = {Sept},
	abstract = {This empirical paper shows how free/libre open source software (FLOSS) contributes to mutual and collaborative learning in an educational environment. Unlike proprietary software, FLOSS allows extensive customisation of software to support the needs of local users better. This also allows users to participate more proactively in the development and implementation process of a FLOSS-based system. In this paper, we observes how implementing FLOSS in an Italian high school challenges the conventional relationship between end users themselves (e.g. teachers and students) and that between users and developers. The findings will shed some light on the social aspects of FLOSS-based computerization - including the role of FLOSS in social and organizational change in educational environments and the ways that the social organization of FLOSS are influenced by social forces and social practices.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Lin\%26Zini.pdf},
	author = {Yu-wei Lin and Enrico Zini}
}
@booklet {488,
	title = {Innovativeness of software solutions: evidence from an alternative methodology. Comparing Free/Open Source and proprietary products},
	year = {2007},
	month = {Dec},
	abstract = {The issue of innovation processes taking place in the software sector  is currently widely debated. Challenging questions arise about what products/services have to be considered innovative, and whether a specific artefact is innovative or not. In this framework, the widespread success of the Free/Open Source Software (FOSS) put forward new research issues, dealing with whether and how programs developed according to the new production paradigm turn out to be more innovative than traditional ones. In this framework, this paper aims at contributing to the literature by addressing three main research questions: (i) are software solutions produced by Small and Medium Enterprises (SMEs) innovative? (ii) What kinds of innovations are implemented? And, finally, (iii) are programs based on FOSS more innovative than proprietary ones?Basing on a sample of 134 software solutions produced by Italian SMEs and using an original methodology to asses the problem of evaluating innovation in the software field, we provides some first insights of what emerges if we set aside the traditional innovation indicators and endower to build alternative metrics, specifically developed to target the complexity of the innovation processes in the software markets.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lorenzi_rossi_MIT_20071220.pdf , https://flosshub.org/sites/flosshub.org/files/Alexy_Henkel_-_Promoting_the_Penguin_-_SSRN.pdf},
	author = {Dario Lorenzi and Cristina Rossi}
}
@conference {646,
	title = {Learning Through Practical Involvement in the OSS Ecosystem: Experiences from a Masters Assignment},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {289 - 294},
	publisher = {Springer},
	organization = {Springer},
	chapter = {30},
	abstract = {Increased awareness of and interest in Open Source has led to a number of university teaching initiatives, at both national and European level. In this paper we present experiences from a practical assignment designed to give students on an Open Source Masters course an insight into real involvement in Open Source projects. It discusses the motivations for the assignment, and how it was set up and executed. It reports on post facto student feedback, and reflects on a parallel, reduced exercise offered at undergraduate level. We find that the learning experience was both positive and valuable in that it gave real insight into Open Source participation, and also encouraged further participation in Open Source projects by students after the course had completed.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_30},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Learning\%20through\%20practical\%20involvement.pdf},
	author = {Lundell, Bj{\"o}rn and Persson, Anna and Lings, Brian}
}
@conference {1015,
	title = {Mining Eclipse Developer Contributions via Author-Topic Models},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {30 - 30},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {We present the results of applying statistical author-topic models to a subset of the Eclipse 3.0 source code consisting of 2,119 source files and 700,000 lines of code from 59 developers. This technique provides an intuitive and automated framework with which to mine developer contributions and competencies from a given code base while simultaneously extracting software function in the form of topics. In addition to serving as a convenient summary for program function and developer activities, our study shows that topic models provide a meaningful, effective, and statistical basis for developer similarity analysis.},
	keywords = {contributions, developers, eclipse, expertise, mining challenge, msr challenge, source code, topics},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300030.pdf},
	author = {Linstead, Erik and Rigor, Paul and Bajracharya, Sushil and Lopes, Cristina and Baldi, Pierre}
}
@article {flosswp368,
	title = {Norms, Rewards, and their Effect on the Motivation of Open Source Software Developers},
	year = {2007},
	month = {September},
	abstract = {In this study, we conduct a scenario experiment testing the effect of monetary rewards on intrinsic motivation of open source software (OSS) developers. While we observe no difference in intrinsic motivation between the payment and no payment scenario, total motivation increases when a monetary reward is offered. We find that self-reported interest increases in the payment scenario when there is a norm for payment, whereas it decreases when there is a norm for no payment. We conclude that, under certain preconditions, monetary rewards may well be used in OSS development.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Alexy_Leitner_-_Norms_Rewards_and_Their_Effect_on_the_Motivation_of_OSS_Developers.pdf},
	author = {Oliver Alexy and Martin Leitner}
}
@conference {618,
	title = {Open Source Collaboration for Fostering Off-The-Shelf Components Selection},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {17 - 30},
	publisher = {Springer},
	organization = {Springer},
	chapter = {2},
	abstract = {The use of Off-The-Shelf software components in Component- Based Development implies many challenges. One of them is the lack of available and well-suited data to support selection of suitable OTS components. This paper proposes a feasible and incremental way to federate and reuse the different efforts for finding, selecting, and maintaining OTS components in a structured way. This is done not only for supporting OTS components selection, but also to overcome reported problems with the integration and maintenance of component repositories. It is based on the {\textquotedblleft}open source collaboration{\textquotedblright} idea to incrementally build an OTS components reuse infrastructure, enabling automatic support for OTS selection processes.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_2},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Collaboration.pdf},
	author = {Ayala, Claudia and S{\o}ensen, Carl-Fredrik and Conradi, Reidar and Franch, Xavier and Li, Jingyue}
}
@article {flosswp360,
	title = {Open Source Software and Economic Growth: A Classical Division of Labor Perspective},
	year = {2007},
	month = {August},
	abstract = {The article turns to classical economic insights on the division of labor and to institutional reasoning to identify some costs and benefits of Open Source Software (OSS) and proprietary software production. It suggests that, thanks to its licenses, OSS favors market expansion more than proprietary software does by tapping into spontaneous work input. The spontaneous tapping leads to a division of labor that exhibits what the article calls redundant economies. By generating a circle of knowledge growth, reuse, and sharing, redundant economies lead to increasing returns, which are crucial for economic growth.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/0SSGROWTHMIT.pdf},
	author = {Giampaolo Garzarelli and Yasmina Reem Limam and Bj{\o}rn Thomassen}
}
@conference {665,
	title = {Open Source Software and Product Lines 2007},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {375 - 376},
	publisher = {Springer},
	organization = {Springer},
	chapter = {49},
	abstract = {Embedded industries have invested a lot in the introduction of software product lines in their software development. In addition, using open source software appears to be a profitable way to obtain good software. This is also applicable for organizations doing product line engineering. On the other hand, because of the diverse use of open source software, product line development is an attractive way of working in open source communities. In fact, the configuration mechanisms used in open source communities may be applicable within software product lines as well. In addition, product line organisations are usually involved in distributed development, which works very efficiently within open source communities. However, at present, there is limited interaction between the open source and product line development communities. The aim for the workshop is to explore what the two communities can learn from each other and to develop a better understanding of how the two communities can benefit from each other. The workshop deals with the following issues:
 
{\textendash}Community: Ownership, control and management of product line assets in an open source community
{\textendash}Visibility of the code: when it is valuable to share proprietary code and how to take the right decision.
{\textendash}Architecture Views: Creation of different levels of architecture visibility: proprietary, among closed consortium, public.
{\textendash}Is this possible?
{\textendash}Product line requirements roadmaps and planning in open source development
{\textendash}Variability management: Using the open source community to evolve components and being explicit about variability
{\textendash}Variability representation: in an open source community
{\textendash}Deployment: Open source for the platform and in applications
{\textendash}Heterogeneous processes: Cohabitation of product line management and agile processes
{\textendash}Tools: Open source asset management tools in product line development
{\textendash}Domain and application engineering and their meaning in an open source context
{\textendash}Recovery and recognition of a product line in an open source asset base
{\textendash}Legal: Aspects dealing with evolutionary, variability or distribution of development relating to legal risks involving: liability, warranties, patent infringements etc.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_49},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OSS\%20and\%20product\%20lines\%202007.pdf},
	author = {van der Linden, Frank and Lundell, Bj{\"o}rn}
}
@conference {630,
	title = {OpenBQR: a framework for the assessment of OSS},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {173 - 186},
	publisher = {Springer},
	organization = {Springer},
	chapter = {14},
	abstract = {People and organizations that are considering the adoption of OSS, or that need to choose among different OS products face the problem of evaluating OSS in a systematic, sound and complete way. While several proposals concerning the evaluation of costs and benefits exist, little attention has been given to the evaluation of technical qualities and, in general, to the {\textquotedblleft}usage-oriented{\textquotedblright} issues. In this paper the existing proposals are examined, the different types of qualities and issues that are relevant to potential users are described, and a coherent and innovative method for the evaluation of OSS is proposed. The proposed method is expected to support the potential user in the evaluation and choice of OSS in a flexible way, taking into account all the aspects that are relevant to the user.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_14},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OpenBQR.pdf},
	author = {Taibi, Davide and Lavazza, Luigi and Morasca, Sandro}
}
@conference {651,
	title = {Perceptions on F/OSS Adoption},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {319 - 324},
	publisher = {Springer},
	organization = {Springer},
	chapter = {35},
	abstract = {This paper aims to reveal results of a survey run by the tOSSad1 project. The majority of survey variables devised to capture perception of public administrators around Europe regarding the importance they attach to the factors such as F/OSS product quality, availability of support, expertise and documentation, TCO, vendor lock-in, political influence, administrative attitudes, productivity, and training costs, all of which intermingle with financial, technical, legal, and personal issues. The analysis consist of depiction of respondents{\textquoteright} administration profile in terms of their F/OSS usage and adoption, descriptive summary and analyses of factors mentioned above, and statistical inferential analyses of survey items. Some valid statistical tests are conducted to understand, to discuss and to see the extend and significance of any F/OSS adoption generalizations for Europe based on the findings of this particular survey.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_35},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Perceptions\%20on\%20F\%20OSS.pdf},
	author = {Ozel, Bulent and Jovanovic, Uros and Oba, Beyza and van Leeuwen, Manon}
}
@conference {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}
}
@article {flosswp405,
	title = {Self-organization of teams for free/libre open source software development},
	journal = {Information and Software Technology Journal},
	volume = {49},
	number = {564-575},
	year = {2007},
	note = {"First, the data from these projects that we needed for analysis had to be publicly available (ruling out projects that limit access to their email lists or trackers). Second, we chose the projects that had more than 7 members"..."projects that have attracted numerous developers beyond the initial project founders, are continuing to release software, have numerous downloads and have an active user community that provides feedback"
"3 FLOSS projects were selected for analysis, namely Gaim, eGroupWare and Compiere ERP."

all had sourceforge hosting

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

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

no pdf},
	month = {Apr-Jun},
	pages = {25-40},
	abstract = {Drawing on social network theories and previous studies, this research examines the dynamics of social network structures in open source software (OSS) teams. Three projects were selected from SourceForge.net in terms of their similarities as well as their differences. Monthly data were extracted from the bug tracking systems in order to achieve a longitudinal view of the interaction pattern of each project. Social network analysis was used to generate the indices of social structure. The finding suggests that the interaction pattern of OSS projects evolves from a single hub at the beginning to a corel periphery model as the projects move forward.},
	keywords = {bug tracking, bugs, COMMUNITY, INNOVATION, longitudinal study, MODEL, open source, social, social network analysis, social networks, sourceforge, structure},
	isbn = {1063-8016},
	author = {Long, Y. and Siau, K.}
}
@mastersthesis {483,
	title = {"A system that works for me" - an anthropological analysis of computer hackers{\textquoteright} shared use and development of the Ubuntu system},
	year = {2007},
	month = {June},
	abstract = {Based on 6 months of anthropological fieldwork both on-line and in-person among the developers working to develop and maintain the Ubuntu Linux system, this thesis examines the individual and collaborative day-to-day practices of these developers as they relate to the computer operating system that is the result of their labour. Despite being spread across the industrialized world, these ""hackers"" socialise, share their knowledge, and come to depend on each other in their work across the Internet, as well as in their in-person meetings at conferences and summits. I argue that these shared and negotiated on-line and in-person practices constitute a community of practice (Wenger 1998) rooted in a more than 40-year old "oral"computing tradition based on the Unix operating system.
Taking the Ubuntu system as my point of departure, I examine the network of practices, processes and actors in which it has been constructed, and
through a strategically selected constellation of theories drawn from anthropology, philosophy, and new media studies, I seek to describe and analyze the three central dimensions of a community of practice. I conclude by suggesting that it is the possibility to adopt, learn, configure, and even build the system according to their own needs, which opens the meritocratic community of practice for new contributors to scale the steep curve of learning necessary to enter and learn among them. In this way, the Ubuntu hackers come to share more than just the same system, they come to share a common history, and, to a certain extent, a shared identity through their practice.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ubuntu.pdf},
	author = {Andreas Lloyd}
}
@article {120,
	title = {Applying Social Network Analysis Techniques to Community-Driven Libre Software Projects},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	abstract = {Source code management repositories of large, long-lived libre (free, open source) software projects can be a source of valuable data about the organizational structure, evolution, and knowledge exchange in the corresponding development communities. Unfortunately, the sheer volume of the available information renders it almost unusable without applying methodologies which highlight the relevant information for a given aspect of the project. Such methodology is proposed in this article, based on well known concepts from the social networks analysis field, which can be used to study the relationships among developers and how they collaborate in different parts of a project. It is also applied to data mined from some well known projects (Apache, GNOME, and KDE), focusing on the characterization of their collaboration network architecture. These cases help to understand the potentials of the methodology and how it is applied, but also shows some relevant results which open new paths in the understanding of the informal organization of libre software development communities.},
	keywords = {apache, conway{\textquoteright}s law, cvs, gnome, kde, scm, social network analysis, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/06_Lopez_ijitwe_sna.pdf},
	author = {L{\'o}pez-Fern{\'a}ndez, L. and Gregorio Robles and Jesus M. Gonzalez-Barahona and Herraiz, I.}
}
@conference {D{\textquoteright}Ambros:2006:AER:1137983.1138029,
	title = {Applying the evolution radar to PostgreSQL},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {177{\textendash}178},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	keywords = {cvs, documentation, evolution, evolution radar, logical coupling, makefile, mining challenge, msr challenge, postgresql, re-engineering, refactoring, release history, rhdb, source code, version control, visualization},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138029},
	url = {http://doi.acm.org/10.1145/1137983.1138029},
	attachments = {https://flosshub.org/sites/flosshub.org/files/177ApplyingEvolution.pdf},
	author = {D{\textquoteright}Ambros, Marco and Lanza, Michele}
}
@conference {887,
	title = {Because I Carry My Cell Phone Anyway: Functional Location-Based Reminder Applications},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2006},
	month = {22/04/2006},
	pages = {889-898},
	publisher = {ACM},
	organization = {ACM},
	address = {Montreal, Quebec, Canada},
	isbn = {1-59593-372-7},
	author = {Ludford, P. and D. Frankowski and Reily, K. and Wilms, K. and Terveen, L.}
}
@conference {684,
	title = {Comparing macro development for personal productivity tools: an experience in validating accessibility of Talking Books},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {247 - 252},
	publisher = {Springer},
	organization = {Springer},
	abstract = {We describe an experience in developing macros for both Power Point and Impress, to be used in accessibility validation for educational multimedia (Talking Books) designed for visually impaired people. Minor disadvantages in the use of Impress are outlined, which however do not constitute a serious obstacle to adoption of Open Source tools for our purposes.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_24},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Comparing\%20macro\%20development.pdf},
	author = {Dodero, Gabriella and Lupi, Katia and Piffero, Erika}
}
@article {90,
	title = {Core and periphery in Free/Libre and Open Source software team communications},
	journal = {Proceedings of the 39th Annual Hawaii International Conference on System Sciences-Volume 06},
	year = {2006},
	abstract = {The concept of the core group of developers is important and often discussed in empirical studies of FLOSS projects. This paper examines the question, "how does one empirically distinguish the core?" Being able to identify the core members of a FLOSS development project is important because many of the processes necessary for successful projects likely involve core members differently than peripheral members, so analyses that mix the two groups will likely yield invalid results. 

We compare 3 analysis approaches to identify the core: the named list of developers, a Bradford{\textquoteright}s law analysis that takes as the core the most frequent contributors and a social network analysis of the interaction pattern that identifies the core in a core-and-periphery structure. We apply these measures to the interactions around bug fixing for 116 SourceForge projects. The 3 techniques identify different individuals as core members; examination of which individuals are identified leads to suggestions for refining the measures. All 3 measures though suggest that the core of FLOSS projects is a small fraction of the total number of contributors.},
	keywords = {bug fixing, contributions, contributors, core, developers, social network analysis, sourceforge, team},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and Howison, James}
}
@conference {688,
	title = {Development Platforms as a Niche for Software Companies in Open Source Software},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {341 - 342},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Without Abstract},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Development\%20Platforms\%20as\%20a\%20Niche.pdf},
	author = {Savonnet, Marinette and Leclercq, Eric and Terrasse, Marie-No{\"e}lle and Grison, Thierry and Becker, George and Farizy, Anne and Denoyelle, Ludovic}
}
@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}
}
@article {flosswp298,
	title = {An Empirical Study on Implementing FLOSS in Schools},
	journal = {Social Informatics: An Information Society for All? In Remembrance of Rob Kling, the proceedings of the 7th {\textquoteright}Human Choice and Computers{\textquoteright} conference},
	year = {2006},
	publisher = {Springer Science and Business Media},
	abstract = {This empirical paper shows how free/libre open source software (FLOSS) contributes to mutual and collaborative learning in an educational environment. Unlike proprietary software, FLOSS allows extensive customisation of software and supports the needs of local users better. In this paper, we observes how implementing FLOSS in an Italian high school challenges the conventional relationship between end users themselves (e.g. teachers and students) and that between users and developers. The findings will shed some light on the social aspects of FLOSS-based computerization - including the role of FLOSS in social and organizational change in educational environments and the ways that the social organization of FLOSS are influenced by social forces and social practices.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LinZini_HCC7.pdf},
	author = {Yu-wei Lin and Enrico Zini}
}
@conference {D{\textquoteright}Ambros:2006:ERV:1137983.1137992,
	title = {The evolution radar: visualizing integrated logical coupling information},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {26{\textendash}32},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In software evolution research logical coupling has extensively been used to recover the hidden dependencies between source code artifacts. They would otherwise go lost because of the file-based nature of current versioning systems. Previous research has dealt with low-level couplings between files, leading to an explosion of data to be analyzed, or has abstracted the logical couplings to module level, leading to a loss of detailed information. In this paper we propose a visualization-based approach which integrates both file-level and module-level logical coupling information. This not only facilitates an in-depth analysis of the logical couplings at all granularity levels, it also leads to a precise characterization of the system modules in terms of their logical coupling dependencies.},
	keywords = {change management, cvs, evolution, logical coupling, mozilla, scm, source code, thunderbird, tinderbox, visualization},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137992},
	url = {http://doi.acm.org/10.1145/1137983.1137992},
	attachments = {https://flosshub.org/sites/flosshub.org/files/26TheEvolutionRadar.pdf},
	author = {D{\textquoteright}Ambros, Marco and Lanza, Michele and Lungu, Mircea}
}
@article {Grewal:2006:LLL:1246148.1246155,
	title = {Location, Location, Location: How Network Embeddedness Affects Project Success in Open Source Systems},
	journal = {Management Science},
	volume = {52},
	number = {7},
	year = {2006},
	month = {July},
	pages = {1043{\textendash}1056},
	publisher = {INFORMS},
	address = {Institute for Operations Research and the Management Sciences (INFORMS), Linthicum, Maryland, USA},
	abstract = {The community-based model for software development in open source environments is becoming a viable alternative to traditional firm-based models. To better understand the workings of open source environments, we examine the effects of network embeddedness---or the nature of the relationship among projects and developers---on the success of open source projects. We find that considerable heterogeneity exists in the network embeddedness of open source projects and project managers. We use a visual representation of the affiliation network of projects and developers as well as a formal statistical analysis to demonstrate this heterogeneity and to investigate how these structures differ across projects and project managers. Our main results surround the effect of this differential network embeddedness on project success. We find that network embeddedness has strong and significant effects on both technical and commercial success, but that those effects are quite complex. We use latent class regression analysis to show that multiple regimes exist and that some of the effects of network embeddedness are positive under some regimes and negative under others. We use project age and number of page views to provide insights into the direction of the effect of network embeddedness on project success. Our findings show that different aspects of network embeddedness have powerful but subtle effects on project success and suggest that this is a rich environment for further study.},
	keywords = {affiliation network, age, developers, latent class analysis, network embeddedness, open source software, page views, perl, project success, registration, sourceforge},
	issn = {0025-1909},
	doi = {10.1287/mnsc.1060.0550},
	url = {http://portal.acm.org/citation.cfm?id=1246148.1246155},
	author = {Grewal, Rajdeep and Lilien, Gary L. and Mallapragada, Girish}
}
@conference {Zimmermann:2006:MAM:1137983.1138025,
	title = {Mining additions of method calls in ArgoUML},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {169{\textendash}170},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper we refine the classical co-change to the addition of method calls. We use this concept to find usage patterns and to identify cross-cutting concerns for ArgoUML.},
	keywords = {argouml, change analysis, eclipse, function calls, mining challenge, msr challenge, pattern, source code, xelopes},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138025},
	url = {http://doi.acm.org/10.1145/1137983.1138025},
	attachments = {https://flosshub.org/sites/flosshub.org/files/169MiningAdditions.pdf},
	author = {Zimmermann, Thomas and Breu, Silvia and Lindig, Christian and Livshits, Benjamin}
}
@conference {Breu:2006:MEC:1137983.1138006,
	title = {Mining eclipse for cross-cutting concerns},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {94{\textendash}97},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software may contain functionality that does not align with its architecture. Such cross-cutting concerns do not exist from the beginning but emerge over time. By analysing where developers add code to a program, our history-based mining identifies cross-cutting concerns in a two-step process. First, we mine CVS archives for sets of methods where a call to a specific single method was added. In a second step, such simple cross-cutting concerns are combined to complex cross-cutting concerns. To compute these efficiently, we apply formal concept analysis{\textemdash}an algebraic theory. History-based mining scales well: we are the first to report aspects mined from an industrial-sized project like Eclipse. For example, we identified a locking concern that crosscuts 1284 methods.},
	keywords = {aspects, concept analysis, cvs, eclipse, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138006},
	url = {http://doi.acm.org/10.1145/1137983.1138006},
	attachments = {https://flosshub.org/sites/flosshub.org/files/94MiningEclipse.pdf},
	author = {Breu, Silvia and Zimmermann, Thomas and Lindig, Christian}
}
@conference {889,
	title = {Motivating Participation by Displaying the Value of Contribution},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2006},
	month = {22/04/2006},
	pages = {955-958},
	publisher = {ACM},
	organization = {ACM},
	address = {Montreal, Quebec, Canada},
	isbn = {1-59593-372-7},
	author = {Al Mamunur Rashid and Kimberly Ling and Regina D Tassone and Paul Resnick and Robert Kraut and John Riedl}
}
@article {flosswp342,
	title = {New Perspectives on Public Goods Production: Policy Implications of Open Source Software},
	year = {2006},
	month = {December},
	abstract = {This article reveals some empirical data regarding the trend of evolving open source software (OSS) policies globally. Additionally, this article investigates why so many governments are considering support of OSS development, and weighs the pros and cons of such policies. The ultimate conclusion is that when two systems are equally suitable, governments may reasonably choose OSS over proprietary software because software industry market failures may justify such support of OSS development. While governments considering supporting OSS are primarily concerned with significant switching costs and incompatibility problems, OSS is actually superior to proprietary software because it increases compatibility and consequently decreases switching costs in the long term. Further, OSS will not only help developing countries build their information technology capabilities, but will also promote competition in the software market.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LeeOSS.pdf},
	author = {Jyh-An Lee}
}
@conference {704,
	title = {Perceptions and Uptake of Open Source in Swedish Organisations},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {155 - 163},
	publisher = {Springer},
	organization = {Springer},
	abstract = {There are many different ways in which Open Source ideas can be adopted by business, and influence the way in which companies do business. A number of different surveys have been conducted in different countries with the purpose of understanding the state of practice with respect to Open Source in companies. A number of different business models have been observed, ranging from the use of Open Source infrastructure products to basing a company{\textquoteright}s entire business model on Open Source. In this paper we report on a study of the perceptions of Open Source and the uptake of open source products and development models in Swedish companies. We investigate this from the standpoint of stakeholders in those companies which have an expressed interest in Open Source, allowing a more in-depth analysis of the extent to which Open Source has influenced business thinking. From our analysis we find that uptake is much higher than reported in earlier studies, but is still concentrated in SMEs, consistent with the findings of previous studies. There is increased evidence of interest beyond the simple use of OS components at the (LAMP) infrastructure level. In particular, a significant proportion of the companies are in a symbiotic relationship with the OS community, supporting both through participation in existing projects and the release of new software under OS licences.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_15},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Perceptions\%20and\%20Uptake\%20of\%20Open\%20Source.pdf},
	author = {Lundell, Bj{\"o}rn and Lings, Brian and Lindqvist, Edvin}
}
@conference {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}
}
@inbook {896,
	title = {Understanding Free/Open Source Software Evolution},
	booktitle = {Software Evolution and Feedback: Theory and Practice},
	year = {2006},
	pages = {181-206},
	publisher = {John Wiley and Sons Inc.},
	organization = {John Wiley and Sons Inc.},
	address = {New York},
	author = {Walt Scacchi},
	editor = {Madhavji, N.H. and Lehman, M.M. and Ramil, J.F. and Perry, D.}
}
@article {1079,
	title = {Are All Open Source Projects Created Equal? Understanding the Sustainability of Open Source Software Development Model},
	journal = {AMCIS 2005 Proceedings},
	number = {435},
	year = {2005},
	note = {uses first 300 most active projects on Sourceforge: {\textquoteright}Our data sample consists of 300 open source software development projects hosted in the Sourceforge.Net. They are the first 300 active projects ranked by Sourceforge.Net....Our dependent variable in the model to measure the success of the projects is the number of downloads. It is an essential variable to show how successful the project is. Generally, more number of downloads means a more successful project. Independent variables include: development status, project lifespan, number of developers, number of messages in the forums, number of mailing list, number of bug report, number of patch report, number of CVS report, number of file releases and also number of news release."},
	abstract = {A very intriguing question in Open Source software (OSS) development is: why there are only a few open source projects succeed, while the majority of projects never do. In this research, we examine the factors that may influence the performance of OSS projects. We particularly focus on the OSS{\textquoteright}s core developers{\textquoteright} role in the project{\textquoteright}s success. Extant research has yet to distinguish core developers and non-core developers from the community at large. The different roles of the core developers and non-core developers in OSS projects{\textquoteright} success still remain unclear. Our research contributes to the literature by separating the core developers from the development forces in general and empirically examining the core developers{\textquoteright} importance. Drawing the evidences from our extensive dataset of 300 open source projects, we demonstrated that core developers{\textquoteright} leadership and project advocation are crucial in determining the fate of the OSS projects. Our research could provide better understanding of OSS sustainability. It could also give practical advice to the OSS community on how to make the project successful.},
	keywords = {contributors, core, developers, downloads, metadata, project success, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LongYuan.pdf},
	author = {Long, J. and Yuan, M.J.}
}
@conference {729,
	title = {Communication, coordination and control in distributed development: an OSS case study},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {88-92},
	abstract = {It has been claimed that distributed development practices in OSS development may be a model for enterprise development practices of the future. With this in mind, we have conducted a study of one OSS project, namely ArgoUML, with a view to understanding development practice within the project, and specifically to considering possible differences from traditional (non-OSS) distributed development conducted in a commercial project. We do this by explicitly considering issues of communication, coordination and control. Our findings suggest that primary differences lie in control and resulting project structures, motivated through differing goals. We comment on the open question of how the advantages of one development context can be realised in the other.},
	url = {http://pascal.case.unibz.it/handle/2038/769},
	author = {Persson, Anna and Lings, Brian and Lundell, Bj{\"o}rn and Mattsson, Anders and {\"A}rlig, Ulf}
}
@conference {743,
	title = {Communication from scratch: towards accessible open source information systems},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {179-186},
	abstract = {This paper is intended to provide an overview of a unifying and inclusive approach to open source information systems. In this respect the paper matches the fundamental aims of the Open Source Systems (2005) Conference. This approach can be characterised as communication from scratch. Firstly, we will provide an explanation of our approach to inclusive design and consider emerging perspectives on the nature of accessibility in the wider sense. Secondly, we will introduce the concept of communication from scratch and provide an explanation of the benefits of a convergent gradualism. Thirdly we will explain how these ideas have helped to shape our understanding of open source information processing, a concept which encompasses several of the conference themes and provides a unifying interface to our earlier work on accessible system design. Lastly, we will provide some concrete examples of the communication from scratch approach (crossing several domains) and introduce, ...},
	url = {http://pascal.case.unibz.it/handle/2038/759},
	author = {Crombie, David and Lenoir, Roger and McKenzie, Neil}
}
@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 {753,
	title = {Distributed Software Platforms for Rehabilitating Obsolete Hardware},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {220-223},
	abstract = {The diffusion of ICTs created the issue of a huge quantity of old computers to be discarded (E-waste). Sustainable dismantle is becoming a global enviromental emergency. Trashware movement is spreading worldwide, aiming to profitably reuse discarded computers as an alternative to dismantling them. Trashware is deeply related to the Open Source and Free Software movements. The aim of this piece of research is to combine Trashware to clustering, in order to verify if further optimisations are possible. Experiments were conducted on clusters of old machines and results are hereby presented.},
	url = {http://pascal.case.unibz.it/handle/2038/782},
	author = {Russo, Ruggero and Lamanna, Davide and Baldoni, Roberto}
}
@conference {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 {725,
	title = {EDOS: Environment for the Development and Distribution of Open Source Software},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {66-70},
	abstract = {The open-source software community is now comprised of a very large and growing number of contributors and users. The GNU/Linux operating system for instance has an estimated 18 million users worldwide and its contributing developers can be counted by thousands. The critical mass of contributors taking part in various opensource projects has helped to ensure high quality for open source software. However, despite the achievements of the open-source software industry, there are issues in the production of large scale open-source software (OSS) such as the GNU/Linux operating system that have to be addressed as the numbers of users, of contributors, and of available applications grow. EDOS is a European project supported by IST started October 2004 and ending in 2007, whose objective is to provide a new generation of methodologies, theoretical models, technical tools and quality models specifically tailored to OSS engineering and to software distribution over the Interne...},
	url = {http://pascal.case.unibz.it/handle/2038/737},
	author = {Abiteboul, Serge and Leroy, Xavier and Vrdoljak, Boris and Di Cosmo, Roberto and Fermigier, St{\'e}fane and Lauri{\`e}re, St{\'e}phane and Lepied, Fr{\'e}d{\'e}ric and Pop, Radu and Villard, Florent and Smets, Jean-Paul and Bryce, Ciar{\'a}n and Dittrich, Klaus R. and Milo, Tova and Sagi, Assaf and Shtossel, Yotam and Panto, Eleonora}
}
@unpublished {flosswp235,
	title = {Effects of Open Source Software on the Business Patterns of Software Industry},
	year = {2005},
	month = {September},
	abstract = {Open source software is a phenomenon that has potential to change the traditional patterns of business behavior. Research committed so far has not evaluated the entire scale of potential changes, which is the purpose of this explorative thesis. Previous literature on the subject can be divided into history of the phenomenon, explaining the nature of the phenomenon, and a more general discussion about strategies and business models in the software business. By using these theories this thesis provides a framework for analysing the entire phenomenon. The framework is put to use in the empirical part. Data consist of interviews of experts in the field. An analysis of the data is done using narrative methods. The analysis yield eleven narratives that describe the phenomenon. Four of the narratives reveal effects. On the basis of the responses gathered, open source software can change competition environment, customer expectations, the importance of competence, and platform thinking.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lindman.pdf},
	author = {Juho Lindman}
}
@conference {Liu:2005:ESE:1062455.1062566,
	title = {Enriching software engineering courses with service-learning projects and the open-source approach},
	booktitle = {Proceedings of the 27th international conference on Software engineering},
	series = {ICSE {\textquoteright}05},
	year = {2005},
	pages = {613{\textendash}614},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Real-world software engineers deal with complex problem. Yet many software engineering courses do not involve projects of enough complexity to give students such experience. We sense that service-learning projects, while difficult to manage and sustain, can serve a crucial role in this regard. Through trials in a senior-level software engineering course, we discovered that the open-source approach works well to enable students to work on large, multiple-term service-learning projects. We developed GROw, a cross-term, cross-team educational software process to meet the challenges of adopting complex, real-world projects in one-term courses, and to sustain service learning.},
	keywords = {education, pedagogical, service learning, software engineering education},
	isbn = {1-58113-963-2},
	doi = {10.1145/1062455.1062566},
	url = {http://doi.acm.org/10.1145/1062455.1062566},
	author = {Liu, Chang}
}
@proceedings {897,
	title = {Experiences in Discovering, Modeling, and Reenacting Open Source Software Development Processes},
	year = {2005},
	month = {May},
	publisher = {Springer-Verlag},
	address = {Beijing, China},
	author = {Chris Jensen and Walt Scacchi},
	editor = {Li, Mingshu and Boehm, Barry and Osterweil, Leon J.}
}
@booklet {489,
	title = {Framework for Governance in Open Source Projects},
	year = {2005},
	month = {Jan},
	abstract = {In recent years, the development of software in open source communities has attracted immense attention from research and practice. The idea of commercial quality, free software, and open source code accelerated the development of well-designed open source software such as Linux, Apache tools, or Perl.Intrinsic motivation, group identification processes, learning, and career concerns are the key drivers for a successful cooperation among the participants. These factors and most mechanisms of control, coordination, and monitoring forms of open source communities can hardly be explained by traditional organizational theories. In particular, the micro and macro structures of open source communities and their mode of operation are hardly compatible with the central assumption of the New Institutional Theory, like opportunistic behavior.The aim of this contribution is to identify factors that sustain the motivation of the community members over the entire life cycle of an open source project. Adequate coordination and controlling mechanisms for the governance in open source communities may be extracted.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Governance-in-OpenSourceProjects.pdf},
	author = {Christoph Lattemann and Stefan Stieglitz}
}
@article {flosswp226,
	title = {Fun and Software Development},
	year = {2005},
	month = {July},
	abstract = {This study gathered 1330 answers about fun and software development from open source developers as well as 114 answers from programmers working in commercial software projects. The analysis of these data proves that fun plays an important role when software developers decide to get engaged in an open source project. Moreover, the comparison of the answers gives evidence for the hypothesis that programming in an open source project is significantly more fun compared to the same activity under commercial conditions. The reasons for this fact are that open source projects are able to attract software developers with a credible project vision and that they can offer them an optimal challenge.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/BLuthiger_Fun_SoftwareDevel_OSS2005.pdf},
	author = {Benno Luthiger Stoll}
}
@article {flosswp208,
	title = {Gender issues in the FLOSS development},
	year = {2005},
	month = {March},
	abstract = {The FLOSS development is responding to the ICT development in various ways. This essay describes and analyses challenges (societal and organisational) and advantages (e.g. new models for mobile and collaborative work online), particularly regarding gender issues, encountered in the recent FLOSS development. The focus of the essay is not only on the claims made women in the existed FLOSS community about the tensions between male and female developers{\textquoteright} interests and ways of doings, but also on the current obstacles against bringing more women, who are not technically competent, to participate in the FLOSS development. This paper concludes with suggestions on how to create rules and resources and the creation of a common FLOSS space for both genders.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin3_gender.pdf},
	author = {Yu-wei Lin}
}
@proceedings {117,
	title = {A human capital perspective of organizational intention to adopt open source software},
	year = {2005},
	keywords = {Survey},
	author = {Yan Li and Chuan-Hoo Tan and Hock-Hai Teo and Alex Siow}
}
@article {flosswp211,
	title = {Hybrid Innovation - How Does the Collaboration Between the FLOSS Community and Corporations Happen?},
	year = {2005},
	month = {April},
	abstract = {Unlike innovation based on a strong professional culture involving close collaboration between professionals in academia and/or corporations, the current Free/Libre Open Source Software (FLOSS) development entails a global knowledge network, which consists of 1) a heterogeneous community of individuals and organisations who do not necessarily have professional backgrounds in computer science but competent skills to understand programming and working in a public domain; 2) corporations. This paper highlights the importance of the hybrid form of developing and implementing software, and also identifies several key factors shaping the collaboration between OSS firms and the community.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin4_hybrid.pdf},
	author = {Yu-wei Lin}
}
@conference {781,
	title = {Idealism and Commercialism {\textendash} Developing Free/Libre and Open Source Software in Private Businesses},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {301-302},
	abstract = {This paper presents a PhD research project undertaken as part of a larger project aimed at paying sociological attention to different forms of distribution of knowledge, including program code. We want to investigate empirically how the commons knows as free/open source software is actually made. In my PhD project I study the use and development of FLOSS in private businesses, focusing on professional developers working in private businesses and at the same time participating in the FLOSS community. The theoretical starting point is theories of power, dominance and legitimacy by Max Weber and Pierre Bourdieu.},
	keywords = {dominance, FLOSS, FLOSS community, free/libre, legitimacy, linux, open source, Private Businesses, social organisation, theories of power},
	url = {http://pascal.case.unibz.it/handle/2038/970},
	author = {Lundestad, Christian V.}
}
@conference {771,
	title = {Linux on the portuguese schools: the Caixa M{\'a}gica experience},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {279-280},
	abstract = {This article depicts the experience of Caixa M{\'a}gica
in the deployment of 14.000 computers with dual boot in the
portuguese schools. Caixa M{\'a}gica role was preparing its
Linux distribution to become friendly to students and
teachers.
This project was very successful and is now beginning with a
second phase with 5.000 more computers.
In this experience report with present some of the obstacles
and achievements accomplished in {\textquotedblleft}Salas TIC{\textquotedblright}.},
	author = {Susana Nunes, and Fl{\'a}vio Moringa and Miguel Louren{\c c}o and Paulo Trezentos}
}
@conference {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}
}
@article {flosswp230,
	title = {A Techno-Feminist Perspective on the Free/Libre Open Source Software Development},
	year = {2005},
	month = {August},
	abstract = {This paper tries to analyse the FLOSS development from a "techno-feminist" perspective (Wajcman 2004). Staying away from a reductionism that simplifies the gender issue in the FLOSS community to the level of a fight between men and women, the issues I attempt to address include not only the inequality that women face in computing, but also other inequalities that other users face mainly emerging from the power relationships between expert and lay (namely, developer and user) in software design. Instead of splitting women and men in the FLOSS development, this analysis helps motivate both men and women to work together, reduce the gender gap, and improve the disadvantaged statuses of women and a wider users community in the FLOSS development.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin5.pdf},
	author = {Yu-wei Lin}
}
@conference {739,
	title = {Understanding the Open-Source Software Development Process: a Case Study with CVSChecker},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {154-161},
	abstract = {The open-source process model is emerging as a new lightweight paradigm for software development and has already produced several successful products. This process is fundamentally different from more traditional analysis- and design-driven processes, which raises a set of interesting research questions: what activities are carried out in open-source projects and by whom? Are there typical or exceptional patterns? CVSChecker is a tool designed to analyze the performance of individual developers and the work-distribution patterns of teams based on historical source-code repository data. In this paper, we report on a case study conducted using CVSChecker to examine a small open-source project. We discuss the insights that the CVSChecker analysis produced regarding this project and compare them to results from previous case studies performed with senior student teams.},
	url = {http://pascal.case.unibz.it/handle/2038/1551},
	author = {Liu, Ying and Stroulia, Eleni and Erdogmus, Hakan}
}
@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}
}
@article {flosswp175,
	title = {Applying Social Network Analysis to the Information in CVS Repositories},
	year = {2004},
	month = {June},
	abstract = {The huge quantities of data available in the CVS repositories of large, long-lived libre (free, open source) software projects, and the many interrelationships among those data offer opportunities for extracting large amounts of valuable information about their structure, evolution and internal processes. Unfortunately, the sheer volume of that information renders it almost unusable without applying methodologies which highlight the relevant information for a given aspect of the project. In this paper, we propose the use of a well known set of methodologies (social network analysis) for characterizing libre software projects, their evolution over time and their internal structure. In addition, we show how we have applied such methodologies to real cases, and extract some preliminary conclusions from that experience.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/llopez-sna-short.pdf},
	author = {Luis Lopez}
}
@booklet {Lopez-Fernandez_applyingsocial,
	title = {Applying Social Network Analysis to the Information in CVS Repositories},
	howpublished = {International Workshop on Mining Software Repositories (MSR 2004)},
	year = {2004},
	pages = {101-105},
	abstract = {The huge quantities of data available in the CVS repositories of large, long-lived libre (free, open source) software projects, and the many interrelationships among those data offer opportunities for extracting large amounts of valuable information about their structure, evolution and internal processes. Unfortunately, the sheer volume of that information renders it almost unusable without applying methodologies which highlight the relevant information for a given aspect of the project. In this paper, we propose the use of a well known set of methodologies (social network analysis) for characterizing libre software projects, their evolution over time and their internal structure. In addition, we show how we have applied such methodologies to real cases, and extract some preliminary conclusions from that experience.},
	keywords = {apache, complex networks, cvs, gnome, kde, libre software engineering, source code, source code repositories, visualization techniques, vizualization},
	attachments = {https://flosshub.org/sites/flosshub.org/files/101ApplyingSocial.pdf},
	author = {L{\'o}pez-Fern{\'a}ndez, L. and Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@proceedings {1190,
	title = {Community structure of modules in the Apache project},
	year = {2004},
	pages = {44-48},
	abstract = {The relationships among modules in a software project of a certain size can give us much information about its internal organization and a way to control and monitor development activities and evolution of large libre software projects. In this paper, we show how information available in CVS repositories can be used to study the structure of the modules in a project when they are related by the people working in them, and how techniques taken from the social networks fields can be used to highlight the characteristics of that structure. As a case example, we also show some results of applying this methodology to the Apache project in several points in time. Among other facts, it is shown how the project evolves and is self-structuring, with developer communities of modules corresponding to semantically related families of modules.},
	keywords = {apache, cvs, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/gonzalezBarahona44-48.pdf},
	author = {Jesus M. Gonzalez-Barahona and Luis Lopez and Gregorio Robles}
}
@article {flosswp199,
	title = {The Economics of Technology Sharing: Open Source and Beyond},
	year = {2004},
	month = {December},
	abstract = {This paper reviews our understanding of the growing open source movement. We highlight how many aspects of open source software appear initially puzzling to an economist. As we have acknowledge, our ability to answer confidently many of the issues raised here questions is likely to increase as the open source movement itself grows and evolves. At the same time, it is heartening to us how much of open source activities can be understood within existing economic frameworks, despite the presence of claims to the contrary. The labor and industrial organization literatures provide lenses through which the structure of open source projects, the role of contributors, and the movement{\textquoteright}s ongoing evolution can be viewed.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lernertirole3.pdf},
	author = {Josh Lerner}
}
@article {flosswp163,
	title = {Epistemologically Multiple Actor-Centred System: or EMACS at Work!},
	year = {2004},
	month = {May},
	abstract = {This paper analyses the innovation process of EMACS (short for Editing MACroS) from a socio-technical perspective. I investigates how actors from different backgrounds contribute multiple ways of knowing, understanding and resolving problems that arise in the innovation process. The analysis of EMACS is especially useful since it spans the period that saw the origins of the free software movement and the subsequent development of a broader free/libre open source software (FLOSS) social world.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin.pdf},
	author = {Yu-wei Lin}
}
@mastersthesis {flosswp188,
	title = {Hacking Practices and Software Development: A Social Worlds Analysis of ICT Innovation and the Role of Free/Libre Open Source Software},
	year = {2004},
	note = {Through use of social worlds theory and qualitative research methods, this thesis explores hackers{\textquoteright} practices and their relationships with the computing world and the wider society from a socio-technical perspective. The hacker social world comprises actors from diverse social-technical backgrounds who share a constellation of im/material practices, namely open source practices (OSPs). Through engaging with these collective practices, actors and actants communicate, negotiate, and shape each other{\textquoteright}s identities, practices and understandings of the innovation structure and system in various aspects. In examining the diverse articulations and performances in which hacker culture and hacker identity are both reflected and constructed, the thesis tries to contextualise and deconstruct the ICT architecture we take for granted, as well as the innovations made possible by this architecture.The major findings of my research are: (1) As a community of open source practices, the FLOSS social world allows diverse actors to engage in the innovation process and therefore fosters a greater innovation resource than other relatively conventional software engineering models. (2) The strategic collaboration between the public (i.e. the free software community) and the private (i.e. information technology corporations) sectors symbolises a pattern of hybrid innovation that entails complex communications and networks, though stabilizing these can be problematic. (3) Tacit knowledge anchored in everyday experiences is particularly valued in a community-based innovation system where social networking and information sharing are extensive. (4) The development of FLOSS democratises software innovation process and allows lay people to develop their understanding and knowledge of a shared problem/issue, especially through the web, to challenge established views on the issue.},
	month = {September},
	abstract = {Through use of social worlds theory and qualitative research methods, this thesis explores hackers{\textquoteright} practices and their relationships with the computing world and the wider society from a socio-technical perspective. Through engaging with a constellation of open source practices (OSPs), actors and actants communicate, negotiate, and shape each other?s identities, practices and understandings of the innovation structure and system in various aspects. In examining the diverse articulations and performances in which hacker culture and hacker identity are both reflected and constructed, the thesis tries to contextualise and deconstruct the ICT architecture we take for granted, as well as the innovations made possible by this architecture.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin2.pdf},
	author = {Yu-wei Lin}
}
@article {1389,
	title = {New tricks: how open source changed the way my team works},
	journal = {IEEE Software},
	volume = {21},
	year = {2004},
	month = {01/2004},
	pages = {68 - 72},
	abstract = {A commercial software team contributed to an open source implementation of the Windows API on X-Windows and Unix. Wine is an open source implementation of the Windows API, a compatibility layer that lets native windows programs run on X-Windows and Unix. With our contribution filling in some gaps, our client planned to include Wine with a slightly modified product. Expecting chaos in the organization and code, the team instead found a structured community with procedures all its own. The version control tool on the Wine team is CVS (concurrent version system), an open source, network-transparent version control system. Patches on Wine are relatively small, which makes them easier to review and less risky to add to the source tree.},
	issn = {0740-7459},
	doi = {10.1109/MS.2004.1259222},
	url = {http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=1259222},
	author = {Lussier, S.}
}
@proceedings {1193,
	title = {Organizational Structure of {\textquotedblleft}User Collaboration Community{\textquotedblright}: Insights from the Case of an Open Source Software Project},
	year = {2004},
	pages = {58-64},
	abstract = {Current literatures on organization innovation do not investigate the innovation model which is composed of "network between individuals". Therefore, this study proposes the concept of the "User Collaboration Community", tries to understand this new phenomenon by conducting OSS project is the subject of this analysis, borrows the observation variables and propositions adopted by Mintzberg on structures of the innovative organization. This study further infers the conceptual framework and a series of hypothesis on the organizational structure of the user collaboration community. We expect that the proposition of this hypothesis will function as a concrete description and presentation of the innovation model of the "User Collaboration Community".},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lee59-65.pdf},
	author = {Lee, J.F and Chan, T.Y}
}
@article {flosswp155,
	title = {Theory Development for Organizational Platform of User Collaboration Innovation Community},
	year = {2004},
	month = {March},
	abstract = {This study proposes the concept of the ?User Collaboration Innovation Community?, tries to understand this new phenomenon by conducting projects where the opening of source software is the subject of this analysis, borrows the observation variables and propositions adopted by Mintzberg on structures of the innovative organization, and summarizes the opinions of scholars of organizational economics, the relationship between property rights and organization performance. This study further infers a series of conceptual framework and propositions on the relationships among ?organization structure, property right, and organization innovation? for ?the organizational platform of the user collaboration innovation community?. We expect that the construction of this concept framework will function as a concrete description and presentation of the innovation model of the User Collaboration Innovation Community and will serve as a clear path to be followed for continuous research in the future.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/leechan2.pdf},
	author = {Jen-Fang Lee}
}
@proceedings {1175,
	title = {Adopting Open-Source Software Engineering in Computer Science Education},
	year = {2003},
	pages = {85-89},
	keywords = {education},
	attachments = {https://flosshub.org/sites/flosshub.org/files/85-89.pdf},
	author = {Liu, C.}
}
@conference {DBLP:conf/csmr/CapiluppiLM03,
	title = {Characteristics of Open Source Projects},
	booktitle = {7th European Conference on Software Maintenance and Reengineering (CSMR{\textquoteright}03)},
	year = {2003},
	note = {"We analyze a sample of around 400 projects from a popular OS project repository. "
no pdf to confirm what projects these are or what the repository is.[ms]},
	pages = {317-},
	abstract = {Most empirical studies about Open Source (OS)projects or products are vertical and usually deal with the flagship, successful projects. There is a substantial lack of horizontal studies to shed light on the whole population of projects, including failures. This paper presents a horizontal study aimed at characterizing OS projects. We analyze a sample of around 400 projects from a popular OS project repository. Each project is characterized by a number of attributes. We analyze these attributes statically and over time. The main results show that few projects are capable of attracting a meaningful community of developers. The majority of projects is made by few (in many cases one) person with a very slow pace of evolution.},
	keywords = {evolution, project success, repository},
	author = {Capiluppi, Andrea and Patricia Lago and Maurizio Morisio}
}
@article {146,
	title = {Community, joining, and specialization in open source software innovation: a case study},
	journal = {Research Policy},
	volume = {32},
	number = {7},
	year = {2003},
	note = {first, telephone interviews
"Secondly, we collected the project{\textquoteright}s public email conversations stored in the projects{\textquoteright} 
mailing lists which is archived on Freenet{\textquoteright}s website"
"The third source of data included the history of changes to the software code available 
via the project{\textquoteright}s software repository within the CVS ({\textquoteleft}Concurrent Versioning System{\textquoteright}) source 
code management tool"
"Fourthly, in order obtain contextual understanding of the project we collected publicly 
available documents related to open source in general and to the project in particular. Among 
the most important sources were the Freenet project web pages (e.g. the Frequently Asked 
Questions (FAQ)7), Ian Clarke{\textquoteright}s master thesis (1999), newspaper interviews with the core 
developers, and a technical paper (Clarke, Sandberg, Wiley, \& Hong, 2000) describing the 
Freenet project written by some of the developers."},
	pages = {1217-1241},
	abstract = {This paper develops an inductive theory of the open source software innovation process by focussing on the creation of Freenet, a project aimed at developing a decentralized and anonymous peer-to-peer electronic file sharing network. We are particularly interested in the strategies and processes by which new people join the existing community of software developers, and how they initially contribute code. Analyzing data from multiple sources on the Freenet software development process, we generate the constructs of "joining script", We are grateful to helpful comments from two anonymous reviewers. We also thank Chris Argyris, John Seely Brown, Eric von Hippel, Stefan Haefliger, Petra Kugler, Heike Bruch, Simon Gchter, Simon Peck, and Hari Tsoukas for helpful comments and suggestions. Ben Ho and Craig Lebowitz provided technical assistance with data importation and parsing. We would like to thank Ian Clarke and the Freenet developers for their willingness to participate in our study and providing key insights into the open source development process. Karim R. Lakhani would like to acknowledge the generous support of The Boston Consulting Group and Canada{\textquoteright}s Social Science and Humanities Research Council doctoral fellowship. Georg von Krogh and Sebastian Spaeth acknowledge the generous support from the Research Foundation at the University of St. Gallen.},
	keywords = {cvs, email, email archives, freenet, INNOVATION, mailing lists, roles, source code},
	doi = {http://dx.doi.org/10.1016/S0048-7333(03)00050-7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/krogh03.pdf},
	author = {Georg von Krogh and Spaeth, S. and Karim R Lakhani}
}
@article {2003,
	title = {From a Firm-Based to a Community-Based Model of Knowledge Creation: The Case of the Linux Kernel Development},
	journal = {Organization Science},
	volume = {14},
	number = {6},
	year = {2003},
	note = {"we study the Linux development community mainly by analyzing the artifacts that the Linux developers have produced. A key output of knowledge creation activities is the artifacts. The most important artifact, of course, is the Linux operating system source code."
"Along with the source code, a "Credits" text file and a "MAINTAINERS" text file are distributed to the users."
"An equally important artifact is the development activities archived in the Linux-kernel mailing list"..."Using the weekly Linux-kernel email archive for years 1995 to 2000 as a key source of data, we focus on people who have sent at least one email to the Linux-kernel mailing list. "
"In addition, we examine the developers{\textquoteright} demographic distributions, working patterns, and motivations by analyzing the raw data from an on-line survey"},
	pages = {pp. 633-649},
	publisher = {INFORMS},
	abstract = {We propose a new model of knowledge creation in purposeful, loosely coordinated, distributed systems, as an alternative to a firm-based one. Specifically, using the case of the Linux kernel development project, we build a model of community-based, evolutionary knowledge creation to study how thousands of talented volunteers, dispersed across organizational and geographical boundaries, collaborate via the Internet to produce a knowledge-intensive, innovative product of high quality. By comparing and contrasting the Linux model with the traditional/commercial model of software development and firm-based knowledge creation efforts, we show how the proposed model of knowledge creation expands beyond the boundary of the firm. Our model suggests that the product development process can be effectively organized as an evolutionary process of learning driven by criticism and error correction. We conclude by offering some theoretical implications of our community-based model of knowledge creation for the literature of organizational learning, community life, and the uses of knowledge in society.},
	keywords = {credits, developers, email, email archives, knowledge creation, linux kernel, mailing list, maintainers, scm, source code, Survey, Volunteers},
	issn = {10477039},
	url = {http://www.jstor.org/stable/4135125},
	author = {Lee, Gwendolyn K. and Cole, Robert E.}
}
@article {flosswp105,
	title = {How Firm Initiation and Control of Projects Affects Open-Source Development},
	year = {2003},
	month = {May},
	abstract = {After witnessing the success of open-source projects such as Linux and Apache, firms have sought to appropriate the open-source development model and integrate it into their own projects. Firms face a dilemma, however, since their initiation and control of open-source projects affects the traditional open-source development model in significant ways. Once a firm takes the role of starting and guiding an open-source project, the open-source development model that attracted the firm is forever altered. This paper examines the effects commercial firms have on the open-source development model when they initiate and control open-source projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/long.pdf},
	author = {Anthony Long}
}
@article {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 {flosswp100,
	title = {The Knowledge Ecology of Open-Source Software Projects},
	year = {2003},
	note = {http://www.mendeley.com/research/the-knowledge-ecology-of-opensource-software-projects/},
	month = {July},
	abstract = {In this paper we characterize the processes of knowledge making in open-source software projects as an ecology of agents, artifacts, rules, resources, activities, practices and interactions. In order to grasp its dynamic features we consider open-source software projects as interactive systems based on dense interactions between humans and technical artifacts within electronic media. Technology, rather than formal or informal organization, embodies most of the conditions for governance in open-source software projects, hence becoming a critical pathway to the understanding of collective task accomplishment, coordination and knowledge making processes. Based on an in-depth analysis of two open-source software projects, we examine three kinds of artifacts, respectively inscribing technical, organizational, and institutional knowledge. Our preliminary findings support the ecological view, that the contradictory requirements of innovation and stability in project-based knowledge making are balanced by mechanisms of variation, selection, and stabilization.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lanzaramorner.pdf},
	author = {Giovan R Lanzara}
}
@article {flosswp82,
	title = {Open Source as a Signalling Device - An Economic Analysis},
	year = {2003},
	month = {March},
	abstract = {Open source projects produce goods or standards that do not allow for the appropriation of private returns by those who contribute to these projects. In this paper we analyze why programmers will nevertheless invest their time and effort to code open source software. We argue that the particular way in which open source projects are managed and especially how contributions are attributed to individual agents, allows the best programmers to create a signal that more mediocre programmers cannot achieve. Through setting themselves apart they can turn this signal into monetary rewards that correspond to their superior capabilities. With this incentive they will forgo the immediate rewards they could earn in software companies producing proprietary software by restricting the access to the source code of their product. Whenever institutional arrangements are in place that enable the acquisition of such a signal and the subsequent substitution into monetary rewards, the contribution to open source projects and the resulting public good is a feasible outcome that can be explained by standard economic theory.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/leemoisaweiss.pdf},
	author = {Samuel Lee}
}
@proceedings {1166,
	title = {Open-Source Development Processes and Tools},
	year = {2003},
	pages = {15-18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/15-18.pdf},
	author = {Boldyreff, Cornelia and Lavery, J. and Nutter, David and Rank, Stephen}
}
@conference {1153,
	title = {Characterizing the OSS process},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	note = {"We have considered two well-known Open Source portals (FreshMeat [1] and SourceForge [2] )."
"Using pseudo-random sampling we have selected a sample of 400 projects (mostly from FreshMeat). Each project is described by several variables (programming language, type of license, size of source code, type of documentation available and others). By indirect means (analysis of the Changelog file, or CVS) it is also possible to compute the number of people working on the project, and the number of external contributors. From FreshMeat we get both a vitality index, that considers the number of releases per time period, and a popularity index, which is a first measure of the interest of users to the project (project URL hits, mixed with subscriptions to it)."},
	abstract = {The Open Source model of software development has gained the attention of both the business, the practitioners{\textquoteright} and the research communities. The Open Source process has been described by the seminal paper by Eric Raymond [4] and [5]. However, sound empirical studies are still very limited [3], [6].
Our goal is to investigate the OS process by empirical means, to analyze, characterize it, and possibly model it with quantitative models. It should be noted that the Open Source process provides open process and product data, and therefore is a rare opportunity for empirical research.
Our initial research focus is on the characterization of the process, starting from the evolution of OS projects. In traditional projects, a significant number of releases in a short time is usually considered an instability factor [7] and [8], while in the OSS community, it is an evidence of vitality, shows the commitment of the authors and the power of attraction of other programmers [9]. Is it possible to characterize the vitality of projects? And, can vitality be traced to some other characteristics of a project?},
	keywords = {bugs, change log, classification, cvs, downloads, freshmeat, metadata, patches, popularity, project success, release history, sourceforge, vitality},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CapiluppiLagoMorisio.pdf},
	author = {Capiluppi, Andrea and Patricia Lago and Maurizio Morisio}
}
@article {flosswp50,
	title = {Open standard: role of externalities and impact on the industry structure},
	year = {2002},
	month = {July},
	abstract = {Conceding a part of property rights appears counter-intuitive in regards to the Porterian and Resources-Based frameworks. However industrial economics literature and recent examples suggest that this strategy is fruitful to develop network externalities and consequently to impose a standard in network industries. This article explores the role of the sponsor and the impacts of an open property rights strategy on the industry structure. Drawing on the empirical data collected from the U.S. Roleplaying Game industry, our results reveal that: 1) the open approach promoted by a sponsor does not work effectively without network industries specific resources; 2) this strategy induces new entries that benefits to the sponsor; 3) the firms in the industry do not change their technological trajectories except those which are well endowed with resources.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lecocqdemil.pdf},
	author = {Xavier Lecocq}
}
@article {flosswp63,
	title = {The Scope of Open Source Licensing},
	journal = {Journal of Law, Economics and Organization},
	volume = {21},
	number = {1},
	year = {2002},
	month = {2005},
	pages = {20-56},
	abstract = {This paper is an initial exploration of the determinants of open source license choice. It first enumerates the various considerations that should figure into the licensor{\textquoteright}s choice of contractual terms, in particular highlighting how the decision is shaped not just by the preferences of the licensor itself, but also by that of the community of developers. The paper then presents an empirical analysis of the determinants of license choice using the SourceForge database, a compilation of nearly 40,000 open source projects. Projects geared toward end-users tend to have restrictive licenses, while those oriented toward developers are less likely to do so. Projects that are designed to run on commercial operating systems and those geared towards the Internet are less likely to have restrictive licenses. Finally, projects that are likely to be attractive to consumers such as games are more likely to have restrictive licenses.},
	keywords = {developers, license, licenses, permissive, restrictive, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lernertirole2.pdf},
	author = {Josh Lerner and Jean Tirole}
}
@article {54,
	title = {Code, Culture and Cash: The Fading Altruism of Open Source Development},
	journal = {First Monday},
	volume = {6},
	number = {12},
	year = {2001},
	note = {"I collected information on the country of residence for key contributors to the two projects. In the case of Linux, I relied on information located in the CREDITS file of all major kernel releases (from version 1.0 to version 2.4.9) [22]. For Gnome, I gathered developer-contact information from the project{\textquoteright}s web-site. Where information on the home-country of developers was not explicitly available, I performed private research to ascertain said information, or - in the last-case scenario - trusted information in the provided e-mail address of developers to infer home-country from domain ownership [23]. In the case of Linux, to avoid bias that might be introduced over time as developers migrated internationally, developers are continually counted as residents of the countries they were associated with when their names first entered the CREDITS file"},
	abstract = {The nexus of open source development appears to have shifted to Europe over the last ten years. This paper explains why this trend undermines cultural arguments about "hacker ethics" and "post-scarcity" gift economies. It suggests that classical economic theory offers a more succinct explanation for the peculiar international distribution of open source development: hacking rises and falls inversely to its opportunity cost. This finding throws doubt on the Schumpeterian assumption that the efficiency of industrial systems can be measured without reference to the social institutions that bind them.},
	keywords = {credits, email address, european, geography, gnome, linux},
	url = {http://131.193.153.231/www/issues/issue6_12/lancashire/index.html},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Lancashire.pdf},
	author = {David Lancashire}
}
@article {witten2001does,
	title = {Does open source improve system security?},
	journal = {IEEE Software},
	volume = {18},
	number = {5},
	year = {2001},
	pages = {57{\textendash}61},
	publisher = {IEEE},
	abstract = {An attacker
could examine
public source
code to find
flaws in a
system. So, is
source code
access a net
gain or loss for
security? The
authors
consider this
question from
several
perspectives
and tentatively
conclude that
having source
code available
should work in
favor of system
security.},
	keywords = {security},
	url = {https://pdfs.semanticscholar.org/71f6/01579ad1c373ed59a19eba0396f7f0cb7a0e.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/01579ad1c373ed59a19eba0396f7f0cb7a0e.pdf},
	author = {Witten, Brian and Landwehr, Carl and Caloyannides, Michael}
}
@book {56,
	title = {The future of ideas: the fate of the commons in a connected world},
	year = {2001},
	publisher = {Random House},
	organization = {Random House},
	author = {Lessig, L.}
}
@conference {1135,
	title = {Software Architectures and Open Source Software {\textendash} Where can Research Leverage the Most?},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	month = {05/2001},
	abstract = {Software architectures have been playing a central role in software engineering research for some years now. They are considered of pivotal importance in the success of complex software systems development. However, with the emergence of Open Source Software (OSS) development, a new opportunity for studying architectural issues arises. In this paper, we introduce accepted notions of software architectures (Section 2), discuss some of the known issues in OSS (Section 3), resulting in a set of aspects we consider to be relevant for future research (Section 4).},
	keywords = {architecture, software architecture},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ariefgaceklawrie.pdf},
	author = {Arief, B. and Gacek, C. and Lawrie, T.}
}
@article {flosswp9,
	title = {The Linux Kernel Development As a Model of Knowledge Creation},
	year = {2000},
	month = {October},
	abstract = {Applying the method of induction theory building, the authors have developed a case study based on the Linux kernel development process to build a model of Open Source knowledge creation.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LinuxKernelDevelopmentAbstract.pdf},
	author = {Gwendolyn Lee}
}
@article {58,
	title = {Open source movements as a model for organising},
	journal = {European Journal of Information Systems},
	volume = {9},
	year = {2000},
	pages = {208--216},
	abstract = {Open source software such as the operating system Linux has in a few years created much attention as an alternative way to develop and distribute software. Open source is to let anyone have access to the source code, so that they can modify it. Open source could be seen as a movement, where communities of highly skilled programmers collectively develop software, often of a quality that outperforms commercial proprietary software. These movements are based on virtual networking on Internet and the web. They are loosely coupled communities kept together by strong common values related to hacker culture. Work seems to be totally distributed, delegated and loosely coupled. The highly skilled members contribute by pride to the collective effort of free software development. In this paper the open source phenomena is investigated from different perspectives. In this paper it is claimed that the open source movements is one key to the understanding of future forms of organizations, knowledge work and business.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/20000077.pdf},
	author = {Ljungberg, J.}
}
@article {flosswp10,
	title = {The Simple Economics of Open Source},
	year = {2000},
	month = {March},
	abstract = {This paper makes a preliminary exploration of the economics of open source software. The authors highlight the extent to which labor economics, especially the literature of career concerns can explain many of these project features.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Josh\%2520Lerner\%2520and\%2520Jean\%2520Triole\%2520-\%2520The\%2520Simple\%2520Economics\%2520of\%2520Open\%2520Source.pdf},
	author = {Josh Lerner}
}
@book {55,
	title = {Code and Other Laws of Cyberspace},
	year = {1999},
	publisher = {Basic Books},
	organization = {Basic Books},
	author = {Lessig, L.}
}
