@proceedings {1919,
	title = {A Large-Scale Study on the Usage of Testing Patterns that Address Maintainability Attributes},
	year = {2017},
	note = {"we conducted a large-scale empirical study to measure
the application of software testing in the open source community"

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

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

data url: https://goo.gl/Mc7tHk},
	month = {05/2017},
	pages = {391-401},
	abstract = {Test case maintainability is an important concern,
especially in open source and distributed development environments
where projects typically have high contributor turnover
with varying backgrounds and experience, and where code
ownership changes often. Similar to design patterns, patterns
for unit testing promote maintainability quality attributes such
as ease of diagnoses, modifiability, and comprehension. In this
paper, we report the results of a large-scale study on the usage
of four xUnit testing patterns which can be used to satisfy these
maintainability attributes. This is a first-of-its-kind study which
developed automated techniques to investigate these issues across
82,447 open source projects, and the findings provide more insight
into testing practices in open source projects. Our results indicate
that only 17\% of projects had test cases, and from the 251
testing frameworks we studied, 93 of them were being used.
We found 24\% of projects with test files implemented patterns
that could help with maintainability, while the remaining did
not use these patterns. Multiple qualitative analyses indicate that
usage of patterns was an ad-hoc decision by individual developers,
rather than motivated by the characteristics of the project, and
that developers sometimes used alternative techniques to address
maintainability concerns.},
	keywords = {maintenance, mining software repositories, msr, Unit Test Frameworks, Unit Test Patterns, Unit Testing},
	author = {Danielle Gonzalez and Joanna C.S. Santos and Andrew Popovich and Mehdi Mirakhorli and Mei Nagappan}
}
@article {kazman2016evaluating,
	title = {Evaluating the Effects of Architectural Documentation: A Case Study of a Large Scale Open Source Project},
	journal = {IEEE Transactions on Software Engineering},
	volume = {42},
	number = {3},
	year = {2016},
	pages = {220{\textendash}260},
	publisher = {IEEE},
	abstract = {Sustaining large open source development efforts requires recruiting new participants; however, a lack of
architectural documentation might inhibit new participants since large amounts of project knowledge are unavailable to
newcomers. We present the results of a multitrait, multimethod analysis of the effects of introducing architectural documentation
into a substantial open source project{\textemdash}the Hadoop Distributed File System (HDFS). HDFS had only minimal architectural
documentation, and we wanted to discover whether the putative benefits of architectural documentation could be observed over
time. To do this, we created and publicized an architecture document and then monitored its usage and effects on the project.
The results were somewhat ambiguous: by some measures the architecture documentation appeared to effect the project but
not by others. Perhaps of equal importance is our discovery that the project maintained, in its web-accessible JIRA archive of
software issues and fixes, enough architectural discussion to support architectural thinking and reasoning. This {\textquotedblleft}emergent{\textquotedblright}
architecture documentation served an important purpose in recording core project members{\textquoteright} architectural concerns and
resolutions. However, this emergent architecture documentation did not serve all project members equally well; it appears that
those on the periphery of the project{\textemdash}newcomers and adopters{\textemdash}still require explicit architecture documentation, as we will
show.},
	author = {Kazman, Rick and Goldenson, Dennis and Monarch, Ira and Nichols, William and Valetto, Giuseppe}
}
@proceedings {1827,
	title = {A Large-Scale Study on Repetitiveness, Containment, and Composability of Routines in Open-Source Projects},
	year = {2016},
	month = {05/2016},
	pages = {362-373},
	abstract = {Source code in software systems has been shown to have a good
degree of repetitiveness at the lexical, syntactical, and API usage
levels. This paper presents a large-scale study on the repetitiveness,
containment, and composability of source code at the semantic level.
We collected a large dataset consisting of 9,224 Java projects with
2.79M class files, 17.54M methods with 187M SLOCs. For each
method in a project, we build the program dependency graph (PDG)
to represent a routine, and compare PDGs with one another as well
as the subgraphs within them. We found that within a project, 12.1\%
of the routines are repeated, and most of them repeat from 2{\textendash}7 times.
As entirety, the routines are quite project-specific with only 3.3\% of
them exactly repeating in 1{\textendash}4 other projects with at most 8 times.
We also found that 26.1\% and 7.27\% of the routines are contained
in other routine(s), i.e., implemented as part of other routine(s) elsewhere
within a project and in other projects, respectively. Except for
trivial routines, their repetitiveness and containment is independent
of their complexity. Defining a subroutine via a per-variable slicing
subgraph in a PDG, we found that 14.3\% of all routines have all
of their subroutines repeated. A high percentage of subroutines in
a routine can be found/reused elsewhere. We collected 8,764,971
unique subroutines (with 323,564 unique JDK subroutines) as basic
units for code searching/synthesis. We also provide practical
implications of our findings to automated tools.},
	doi = {http://dx.doi.org/10.1145/2901739.2901759},
	author = {Nguyen, Anh Duc and Nguyen, Hoan Anh and Nguyen, Tien N.}
}
@mastersthesis {1855,
	title = {Open Source Software Ecosystem: A Systematic Literature Review},
	year = {2016},
	month = {05/2016},
	type = {Masters Thesis},
	address = {University of Oulu},
	abstract = {Background: Currently having a software ecosystem is vital for many technology businesses. For this reason, understanding of software ecosystem and its benefits and also the elements of each software ecosystem can help business and software communities to emerge and orchestrate the products ecosystem optimally. Moreover, an interesting phenomenon in computer science and information technology is open source software and systems which enable users to participate in developing and using the software at many scales, from a simple mobile application to large-scale business systems and ICT applications.},
	doi = {10.13140/RG.2.1.2254.1049},
	url = {https://www.researchgate.net/publication/305994372_Open_Source_Software_Ecosystem_A_Systematic_Literature_Review},
	author = {Javad Nasserifar}
}
@inbook {L{\'o}pez2016,
	title = {OSSAP {\textendash} A Situational Method for Defining Open Source Software Adoption Processes},
	booktitle = {Advanced Information Systems Engineering: 28th International Conference, CAiSE 2016, Ljubljana, Slovenia, June 13-17, 2016. Proceedings},
	year = {2016},
	pages = {524{\textendash}539},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Organizations are increasingly becoming Open Source Software (OSS) adopters, either as a result of a strategic decision or just as a consequence of technological choices. The strategy followed to adopt OSS shapes organizations{\textquoteright} businesses; therefore methods to assess such impact are needed. In this paper, we propose OSSAP, a method for defining OSS Adoption business Processes, built using a Situational Method Engineering (SME) approach. We use SME to combine two well-known modelling methods, namely goal-oriented models (using i*) and business process models (using BPMN), with a pre-existing catalogue of goal-oriented OSS adoption strategy models. First, we define a repository of reusable method chunks, including the guidelines to apply them. Then, we define OSSAP as a composition of those method chunks to help organizations to improve their business processes in order to integrate the best fitting OSS adoption strategy. We illustrate it with an example of application in a telecommunications company.
},
	isbn = {978-3-319-39696-5},
	doi = {10.1007/978-3-319-39696-5_32},
	url = {http://dx.doi.org/10.1007/978-3-319-39696-5_32},
	author = {L{\'o}pez, Lidia and Costal, Dolors and Ralyt{\'e}, Jolita and Franch, Xavier and M{\'e}ndez, Luc{\'\i}a and Annosi, Maria Carmela},
	editor = {Nurcan, Selmin and Soffer, Pnina and Bajec, Marko and Eder, Johann}
}
@inbook {1737,
	title = {Smart Route Planning Using Open Data and Participatory Sensing},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {91-100},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Smart cities are not merely the infusion of technology into a city{\textquoteright}s infrastructure, but also require citizens interacting with their urban environment in a smart and informed manner. Transportation is key aspect of smart cities. In this paper, we present a smart route planning open-source system; SMART-GH utilizes open data and participatory sensing, where citizens actively participate in collecting data about the city in their daily environment, e.g., noise, air pollution, etc. SMART-GH then augments the routing logic with sensor data to answer queries such as {\textquoteleft}return the least noisy route{\textquoteright}. SMART-GH enables citizens to make smarter decisions about their daily commute, and subsequently improve their quality of life.
},
	keywords = {Open-data, open-source, Participatory sensing, Smart-city-routing},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_9},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nallur15.pdf},
	author = {Nallur, Vivek and Elgammal, Amal and Clarke, Siobh{\'a}n},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {export:232407,
	title = {The Uniqueness of Changes: Characteristics and Applications},
	year = {2015},
	month = {05/2015},
	abstract = {Changes in software development come in many forms. Some changes are frequent, idiomatic, or repetitive (e.g. adding checks for nulls or logging important values) while others are unique. We hypothesize that unique changes are different from the more common similar (or non-unique) changes in important ways; they may require more expertise or represent code that is more complex or prone to mistakes. As such, these changes are worthy of study. In this paper, we present a definition of unique changes and provide a method for identifying them in software project history. Based on the results of applying our technique on the Linux kernel and two large projects at Microsoft, we present an empirical study of unique changes. We explore how prevalent unique changes are and characterize where they occur along the architecture of the project. We further investigate developers{\textquoteright} contribution towards uniqueness of changes. We also describe potential applications of leveraging the uniqueness of change and implement two such applications, evaluating the risk of changes based on uniqueness and providing change recommendations for non-unique changes.},
	keywords = {linux kernel},
	url = {http://research.microsoft.com/apps/pubs/default.aspx?id=232407},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MSR-TR-2014-149.pdf},
	author = {Ray, Baishakhi and Meiyappan Nagappan and Christian Bird and Nachiappan Nagappan and Zimmermann, Thomas}
}
@proceedings {1786,
	title = {Utilization and Development Contribution of Open Source Software in Japanese IT Companies: An Exploratory Study of the Effect on Business Growth (2nd report based on 2014 survey)},
	year = {2015},
	month = {08/2015},
	abstract = {The usage of Open Source Software (OSS) has been extended in a
wide range of business fields not only IT industries. Behind this
current situation, there are tremendous inputs by the volunteer
engineers in the development communities. In this series of
studies, we have conducted questionnaire survey to Japanese IT
companies in 2012 and 2013, and then analyzed the relation
between OSS utilization and development contribution, and how
these affect the business growth. Our study revealed that Japanese
IT companies are rather free riders of OSS, the volume of
development contributions are far less than that of utilization.
From our previous studies, it was anticipated that some OSSrelated
factors were affecting the business growth; however, clear
evidence has not been found. In autumn 2014, we conducted the
questionnaire survey for the third time and this paper presents the
survey results as the second report of the continued research. We
constructed the simplified Logistic Model to investigate the
influential factors on business growth. However, no clear
evidence was found as the same as the previous study. In
summary, we conclude that there are some form of relationships
between OSS utilization and development contribution, but these
are not the determinant factors on the business growth in the
Japanese IT companies at present. },
	url = {http://www.opensym.org/os2015/proceedings-files/p102-tansho.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p102-tansho.pdf},
	author = {Tansho, Terutaka and Noda, Tetsuo}
}
@conference {1692,
	title = {Hackers on Forking},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {All open source licenses allow the copying of an existing body of code for use as the basis of a separate development project. This practice is commonly known as forking the code. This paper presents the results of a study in which 11 programmers were interviewed about their opinions on the right to fork and the impact of forking on open source software development.

The results show that there is a general consensus among programmers{\textquoteright} views regarding both the favourable and unfavourable aspects that stem from the right to fork. Interestingly, while all programmers noted potential downsides to the right to fork, it was seen by all as an integral component of open source software, and a right that must not be infringed regardless of circumstance or outcome.},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641590},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p06.pdf},
	author = {Nyman, Linus}
}
@conference {1691,
	title = {Older Adults and Free/Open Source Software},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {The global population is aging rapidly, and older adults are becoming increasingly technically savvy. This paper explores ways to engage these individuals to contribute to free/open source software (FOSS) projects. We conducted a pilot diary study to explore motivations, barriers, and the contribution processes of first-time contributors in a real time, qualitative manner. In addition, we measured their self-efficacy before and after their participation. We found that what drove participants were intrinsic motivations, altruism, and internal values, which differed from previous work with older adults and with the general FOSS population. We also found that self-efficacy did not change significantly, even when participants encountered significant barriers or setbacks. The top 3 barriers were lack of communication, installation issues, and documentation issues. We found that asking for and receiving help, and avoiding difficult development environments were more likely to lead to success. To verify these results, we encourage a future large-scale diary study that involves multiple demographics. Given our pilot study, we recommend that future outreach efforts involving older adults focus on how to effectively communicate and build community amongst older contributors.
},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641589},
	author = {Davidson, Jennifer and Umme Ayda Mannan and Rithika Naik and Ishneet Dua and Jensen, Carlos}
}
@inbook {1621,
	title = {A Study of the Effect on Business Growth by Utilization and Contribution of Open Source Software in Japanese IT Companies},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {216-217},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

To analyze how OSS effects business growth both through simple use and by deeper engagement as a stakeholder in OSS community, we did questionnaire research to Japanese IT companies in 2012 and 2013. We analyze the progress of utilization and contribution of OSS, and the impact on business growth indicators by them.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_32},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_32},
	author = {Noda, Tetsuo and Tansho, Terutaka},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@proceedings {1522,
	title = {Boa: A Language and Infrastructure for Analyzing Ultra-Large-Scale Software Repositories},
	year = {2013},
	month = {05/2013},
	pages = {422-431},
	abstract = {In today{\textquoteright}s software-centric world, ultra-large-scale software repositories, e.g. SourceForge (350,000+ projects), GitHub (250,000+ projects), and Google Code (250,000+ projects) are the new library of Alexandria. They contain an enormous corpus of software and information about software. Scientists and engineers alike are interested in analyzing this wealth of information both for curiosity as well as for testing important hypotheses. However, systematic extraction of relevant data from these repositories and analysis of such data for testing hypotheses is hard, and best left for mining software repository (MSR) experts! The goal of Boa, a domain-specific language and infrastructure described here, is to ease testing MSR-related hypotheses. We have implemented Boa and provide a web-based interface to Boa{\textquoteright}s infrastructure. Our evaluation demonstrates that Boa substantially reduces programming efforts, thus lowering the barrier to entry. We also see drastic improvements in scalability. Last but not least, reproducing an experiment conducted using Boa is just a matter of re-running small Boa programs provided by previous researchers.},
	keywords = {ease of use, forge, github, google code, lower barrier to entry, mining, repository, reproducible, scalable, Software, sourceforge},
	author = {Dyer, Robert and Nguyen, Hoan Anh and Rajan, Hridesh and Nguyen, Tien N.}
}
@proceedings {1507,
	title = {Bug Resolution Catalysts: Identifying Essential Non-committers from Bug Repositories},
	year = {2013},
	month = {05/2013},
	abstract = {Bugs are inevitable in software projects. Resolving bugs is the primary activity in software maintenance. Developers, who fix bugs through code changes, are naturally important participants in bug resolution. However, there are other participants in these projects who do not perform any code commits. They can be reporters reporting bugs; people having a deep technical know-how of the software and providing valuable insights on how to solve the bug; bug-tossers who re-assign the bugs to the right set of developers. Even though all of them act on the bugs by tossing and commenting, not all of them may be crucial for bug resolution. In this paper, we formally define essential non-committers and try to identify these bug resolution catalysts. We empirically study 98304 bug reports across 11 open source and 5 commercial software projects for validating the existence of such catalysts. We propose a network analysis based approach to construct a Minimal Essential Graph that identifies such people in a project. Finally, we suggest ways of leveraging this information for bug triaging and bug report summarization.},
	author = {Mani, Senthil and Seema Nagar and Debdoot Mukherjee and Ramasuri Narayanam and Sinha, Vibha Singhal and Amit A. Nanavati}
}
@proceedings {1512,
	title = {Discovering, Reporting, and Fixing Performance Bugs},
	year = {2013},
	month = {05/2013},
	abstract = {Software performance is critical for how users perceive the quality of software products. Performance bugs---programming errors that cause significant performance degradation---lead to poor user experience and low system throughput. Designing effective techniques to address performance bugs requires a deep understanding of how performance bugs are discovered, reported, and fixed. In this paper, we study how performance bugs are discovered, reported to developers, and fixed by developers, and compare the results with those for non-performance bugs. We study performance and non-performance bugs from three popular code bases: Eclipse JDT, Eclipse SWT, and Mozilla. First, we find little evidence that fixing performance bugs has a higher chance to introduce new functional bugs than fixing non-performance bugs, which implies that developers may not need to be overconcerned about fixing performance bugs. Second, although fixing performance bugs is about as error-prone as fixing nonperformance bugs, fixing performance bugs is more difficult than fixing non-performance bugs, indicating that developers need better tool support for fixing performance bugs and testing performance bug patches. Third, unlike many non-performance bugs, a large percentage of performance bugs are discovered through code reasoning, not through users observing the negative effects of the bugs (e.g., performance degradation) or through profiling. The result suggests that techniques to help developers reason about performance, better test oracles, and better profiling techniques are needed for discovering performance bugs.},
	keywords = {bugs, eclipse, mozilla, performance bugs},
	author = {Adrian Nistor and Tian Jiang and Tan, Lin}
}
@book {1544,
	title = {Effect on Business Growth by Utilization and Contribution of Open Source Software in Japanese IT Companies},
	volume = {404},
	year = {2013},
	pages = {222 - 231},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

The expanded use of Open Source Software (OSS), and the expansion of the market caused by this adoption has led to a corresponding increase in the number of businesses acting as stakeholders in the field. Some of these are pure users of OSS technology but a great number are developers of such technology, and can be understood to have a substantial investment in this paradigm. It is reasonable to assume that such businesses are rational actors, and that their investment or contribution to the field implies a positive economic benefit either currently obtained or assumed as a return in the future. This paper analyzes how OSS affects Japanese IT companies{\textquoteright} business growth both through simple use and by deeper engagement as a stakeholder in OSS community. This is the first time that such a link between the utilization of OSS and economic growth has been explored in the context of Japan, and it can hopefully lay a foundation for further study regarding the real economic value of this approach to software.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_16},
	author = {Noda, Tetsuo and Tansho, Terutaka and Coughlan, Shane},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@book {1530,
	title = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification Empirical Study of the Relation between Open Source Software Use and Productivity of Japan{\textquoteright}s Information Service Industries},
	volume = {404},
	year = {2013},
	pages = {18 - 29},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

This paper analyzes the relation between OSS (Open Source Software) use and the performance of Japanese information service industry. We first estimate the market value of OSS, an issue which only a few studies have specifically addressed. The results are then used to analyze the economic effect of OSS. Although our study has some methodological limitations regarding the calculation of the market value of OSS, we demonstrate that the economic effect of OSS is generally positive.},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_2},
	author = {Noda, Tetsuo and Tanihana, Keisuke},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {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}
}
@proceedings {1469,
	title = {The Effect of Open Source Licensing on the Evolution of Business Strategy},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {344-349},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {This paper explores how the approach underlying Open Source development has encouraged a greater sharing of knowledge in related business and legal affairs, and subsequently leads to the emergence of Open Source-driven collaboration by enterprises to address challenges. We use an Economic approach to propose a theoretical framework for Open Source business analysis and provide a defined sample of real-world developments to support its initial findings. We conclude that the need to develop effective Open Source governance solutions has led to widespread collaboration regarding business and legal challenges by stakeholders in the field, and that this collaboration will increase to improve efficiency as the market matures.},
	author = {Noda, Tetsuo and Tansho, Terutaka and Coughlan, Shane}
}
@proceedings {1447,
	title = {OSS Integration Issues and Community Support: An Integrator Perspective},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {129-143},
	publisher = {IFIP AICT},
	abstract = {The reuse and integration of Open Source Software (OSS) components provided by OSS communities is becoming an economical and strategic need for today{\textquoteright}s organizations. The integration of OSS components provides many benefits, but also risks and challenges. One of the most important risks is the lack of effective and timely OSS community support for dealing with possible integration problems. For gaining an understanding of the common problems that organizations face when integrating OSS components, and the role played by OSS communities, we performed an exploratory study on 25 OSS integration projects from different European organizations. The results show that the main way of reducing integration problems was the use of OSS components from well-established communities; therefore very few integration problems were identified. In most of the cases these problems were successfully solved with the support from the OSS community and/or colleagues. In addition, contrary to the common belief that understanding code from someone else is a hard and undesirable task, some integrators consider OSS code even more understandable than their own code.},
	author = {Ayala, Claudia and Cruzes, Daniela S. and Nguyen, Anh Duc and Conradi, Reidar and Franch, Xavier and Höst, Martin and Ali Babar, Muhammad}
}
@proceedings {1459,
	title = {Perspectives on Code Forking and Sustainability in Open Source Software},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {274-279},
	publisher = {IFIP AICT,  Springer},
	abstract = {The ability to create high-quality software artifacts that are usable over time is one of the essential requirements of the software business. In such a setting, open source software offers excellent opportunities for sustainability. In particular, safeguarding mechanisms against planned obsolescence by any single actor are built into the definition of open source. The most powerful of these mechanisms is the ability to fork the project. In this paper we argue that the possibility to fork serves as the invisible hand of sustainability that ensures that code remains open and that the code that best serves the community lives on. Furthermore, the mere option to fork provides a mechanism for safeguarding against despotic decisions by the project lead, who is thus guided in their actions to consider the best interest of the community.},
	author = {Nyman, Linus and Mikkonen, Tommi and Juho Lindman and Fougère, Martin}
}
@proceedings {1456,
	title = {A Qualitative Method for Mining Open Source Software Repositories},
	volume = {378},
	year = {2012},
	note = {The method proposed by this study employs content analysis Krippendorff [10], a classification technique that is frequently applied to interview and focus group data. The objective of content analysis is to ask quantitative questions about qualitative data. The approach is similar to the grounded theory method, but differs from grounded theory in that the results are quantitative rather than qualitative: content analysis produces results such as, {\textquotedblleft}49\% of messages submitted to project mailing lists were sent by core developers.{\textquotedblright}},
	month = {09/2012},
	pages = {256-261},
	publisher = {IFIP AICT,  Springer},
	abstract = {The volume of data archived in open source software project repositories makes automated, quantitative techniques attractive for extracting and analyzing information from these archives. However, many kinds of archival data include blocks of natural language text that are difficult to analyze automatically.

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

The method was applied in a case study of developer and user forum discussions of an open source electronic medical record project. The study demonstrates that the qualitative repository mining method can be employed to derive useful results quickly yet accurately. These results would not be possible using a strictly automated approach.},
	keywords = {content analysis, Electronic Medical Record, Qualitative Research},
	author = {Noll, John and Seichter, Dominik and Beecham, Sarah}
}
@conference {bird2012www,
	title = {Who? What? Where? Examining Distributed Development in Two Large Open Source Projects},
	booktitle = {Proceedings of the Working Conference on Mining Software Repositories},
	year = {2012},
	abstract = {To date, a large body of knowledge has been built up around understanding open source software development. However, there is limited research on examining levels of geographic and organizational distribution within open source software projects, despite many studies examining these same aspects in commercial contexts. We set out to fill this gap in OSS knowledge by manually collecting data for two large, mature, successful projects in an effort to assess how distributed both geographically and organizationally. Both Firefox and Eclipse have been the subject of many studies and are ubiquitous in the areas of software development and internet usage respectively. Further, both receive substantial development contributions from many companies. As such, both are worthy of study in order to understand the development processes that they use, how distributed the projects are, and what, if any, relationship distribution has with quality. To this end, we identified the top contributors that made 95\% of the changes over multiple major releases of Firefox and Eclipse and determined their geographic locations and organizational affiliations. We found that Firefox is very geographically distributed with over a third of its components receiving major contributions from developers on different continents, and that components that are highly distributed have no more defects than those that are not. In contrast, Eclipse is directed and developed largely by one company; with IBM making 96\% of the total commits (49\% coming from one lab in Ottawa, Canada). We further examined the distribution in each project{\textquoteright}s constituent subsystems and report the relationship of pre- and post-release defects with geographic and organizational factors.},
	keywords = {eclipse, Firefox},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2012www.pdf},
	author = {Christian Bird and Nachiappan Nagappan}
}
@article {1806,
	title = {An empirical study of software architectures{\textquoteright} effect on product quality},
	journal = {Journal of Systems and Software},
	volume = {84},
	year = {2011},
	note = {"We first collected meta-data on the 21,094 most highly ranked Java projects on 2009-03-17 from SourceForge for which it was possible to get such data. Here {\textquotedblleft}Java projects{\textquotedblright} were defined as projects belonging to {\textquotedblleft}trove{\textquotedblright} 198 at SourceForge and {\textquotedblleft}rank{\textquotedblright} was the SourceForge ranking of projects. The data consisted of characteristics such as number of bugs, time of latest file upload, number of developers, number of open bugs, and SourceForge {\textquotedblleft}rank{\textquotedblright}." They did not use FLOSSmole, "A more complete analysis of the project status, could be performed by mining the FLOSSMole database (Howison et al., 2006)."},
	month = {7/2011},
	pages = {1233 - 1243},
	abstract = {Software architecture is concerned with the structure of software systems and is generally agreed to influence software quality. Even so, little empirical research has been performed on the relationship between software architecture and software quality. Basedon 1,141 open source Java projects, we calculate three software architecture metrics (measuring classes per package, normalizeddistance, and a new metric introduced by us concerning the excess of coupling degree) and analyze to which extent these metricsare related to product metrics (defect ratio, download rate, methods per class, and method complexity). We conclude that there area number of significant relationships between product metrics and architecture metrics.  In particular, the number of open defectsdepends significantly on all our architecture measures.},
	keywords = {flossmole cited, java},
	issn = {01641212},
	doi = {10.1016/j.jss.2011.02.037},
	url = {http://www.sciencedirect.com/science/article/pii/S0164121211000574},
	author = {Hansen, Klaus Marius and Jonasson, Kristjan and Neukirchen, Helmut}
}
@proceedings {1301,
	title = {Standing Situations and Issues of Open Source Policy in East Asian Nations: Outcomes of Open Source Research Workshop of East Asia},
	year = {2011},
	month = {10/2011},
	pages = {379-384},
	publisher = {Springer},
	abstract = {East Asia nations have made some progress with this technology, and started to introduce OSS for e-government systems during the early part of this century. Many countries granted it a central role in their policies. The reasons for this include adoption of software based on standard specification, liberation from vender lock-in, or opposition to the market control of proprietary software. However, the primary reason is to reduce adoption costs for e-government systems. While this policy work is useful, there is a great deal more that needs to be done. The OSS adoption policy in each nation of East Asia must be accompanied by technological progress in domestic IT service industries or US multinationals will expand at the cost of local businesses. If this continues unchecked it will create a new form of lock-in for East Asian nations. Some Asian nations are trying to promote their domestic IT service industries, putting their OSS adoption policy to practical use, and this workshop will provide case studies of that work. It will also provide a forum for discussing current challenges and opportunities around both policy and practical implementation issues across Asia.},
	author = {Noda, Tetsuo and Tansho, Terutaka and Coughlan, Shane}
}
@proceedings {1287,
	title = {To Fork or Not to Fork: Fork Motivations in SourceForge Projects},
	year = {2011},
	note = {"Using this search function, we compiled a list of all of the programs with the word {\textquotedblleft}fork{\textquotedblright}..."
"We then analyzed the motivations stated in the descriptions of the forked programs...."
"Based on the descriptions entered by the developer, we were able to identify motivations for 381 of the forks."
},
	month = {10/2011},
	pages = {259-268},
	publisher = {Springer},
	abstract = {A project fork occurs when software developers take a copy of source code from one software package and use it to begin an independent development work that is maintained separately from its origin. Although forking in open source software does not require the permission of the original authors, the new version, nevertheless, competes for the attention of the same developers that have worked on the original version. The motivations developers have for performing forks are many, but in general they have received little attention. In this paper, we present the results of a study of forks performed in SourceForge (http://sourceforge.net/) and list the developers{\textquoteright} motivations for their actions. The main motivation, seen in close to half of the cases of forking, was content modification; either adding content to the original program or focusing the content to the needs of a specific segment of users. In a quarter of the cases the motivation was technical modification; either porting the program to new hardware or software, or improving the original.},
	keywords = {fork rate, sourceforge},
	author = {Nyman, Linus and Mikkonen, Tommi}
}
@inbook {springerlink:10.1007/978-3-642-13244-5_20,
	title = {Download Patterns and Releases in Open Source Software Projects: A Perfect Symbiosis?},
	booktitle = {Open Source Software: New Horizons},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {319},
	year = {2010},
	note = {"We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository."},
	pages = {252-267},
	publisher = {Springer Boston},
	organization = {Springer Boston},
	abstract = {Software usage by end-users is one of the factors used to evaluate the success of software projects. In the context of open source software, there is no single and non-controversial measure of usage, though. Still, one of the most used and readily available measure is data about projects downloads. Nevertheless, download counts and averages do not convey as much information as the patterns in the original downloads time series. In this research, we propose a method to increase the expressiveness of mere download rates by considering download patterns against software releases. We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository. Findings show that projects with similar usage can have indeed different levels of sensitivity to releases, revealing different behaviors of users. Future research will develop further the pattern recognition approach to automatically categorize open source projects according to their download patterns.},
	keywords = {flossmole, oss2010, sourceforge},
	url = {http://dx.doi.org/10.1007/978-3-642-13244-5_20},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s and Madey, Gregory and Noll, John}
}
@book {1249,
	title = {Open Source Software Developer and Project Networks},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: New Horizons},
	volume = {319},
	year = {2010},
	note = {no information on data gathering procedures},
	pages = {407 - 412},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {This paper outlines complex network concepts and how social networks are built from Open Source Software (OSS) data. We present an initial study of the social networks of three different OSS forges, BerliOS Developer, GNU Savannah, and SourceForge. Much research has been done on snapshot or conflated views of these networks, especially SourceForge, due to the size of the SourceForge community. The degree distribution, connectedness, centrality, and scale-free nature of SourceForge has been presented for the network at particular points in time. However, very little research has been done on how the network grows, how connections were made, especially during its infancy, and how these metrics evolve over time. },
	keywords = {berlios, savannah, sourceforge},
	isbn = {978-3-642-13244-5},
	issn = {1861-2288},
	doi = {10.1007/978-3-642-13244-5_39},
	author = {Madey, G. and van Antwerp, M.},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Madey, Gregory R. and Noll, John}
}
@conference {955,
	title = {Perspectives on bugs in the Debian bug tracking system},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {86 - 89},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Bugs in Debian differ from regular software bugs. They are usually associated with packages, instead of software modules. They are caused and fixed by source package uploads instead of code commits. The majority are reported by individuals who appear in the bug database once, and only once. There also exists a small group of bug reporters with over 1,000 bug reports each to their name. We also explore our idea that a high bug-frequency for an individual package might be an indicator of popularity instead of poor quality.},
	keywords = {bug reports, debian, msr challenge, popularity},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463288},
	attachments = {https://flosshub.org/sites/flosshub.org/files/86bugs-debian.pdf},
	author = {Davies, Julius and Hanyu Zhang and Nussbaum, Lucas and Daniel M. German}
}
@conference {952,
	title = {The Ultimate Debian Database: Consolidating bazaar metadata for Quality Assurance and data mining},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {52 - 61},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {FLOSS distributions like RedHat and Ubuntu require a lot more complex infrastructures than most other FLOSS projects. In the case of community-driven distributions like Debian, the development of such an infrastructure is often not very organized, leading to new data sources being added in an impromptu manner while hackers set up new services that gain acceptance in the community. Mixing and matching data is then harder than should be, albeit being badly needed for Quality Assurance and data mining. Massive refactoring and integration is not a viable solution either, due to the constraints imposed by the bazaar development model. This paper presents the Ultimate Debian Database (UDD), which is the countermeasure adopted by the Debian project to the above "data hell". UDD gathers data from various data sources into a single, central SQL database, turning Quality Assurance needs that could not be easily implemented before into simple SQL queries. The paper also discusses the customs that have contributed to the data hell, the lessons learnt while designing UDD, and its applications and potentialities for data mining on FLOSS distributions.},
	keywords = {debian, metadata, udd},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463277},
	attachments = {https://flosshub.org/sites/flosshub.org/files/52msr2010-udd.pdf},
	author = {Nussbaum, Lucas and Zacchiroli, Stefano}
}
@conference {969,
	title = {Validity of network analyses in Open Source Projects},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	note = {"We have mined archival records of developer mailing lists to generate reply-to social networks for the three OSS projects: Apache, MySQL, and Perl."

"For each of these projects, we construct an information flow network based on messages that are sent as replies to previous messages....We use this methodology on all mined data to create a network of mailing list participants. "},
	pages = {201 - 209},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Social network methods are frequently used to analyze networks derived from Open Source Project communication and collaboration data. Such studies typically discover patterns in the information flow between contributors or contributions in these projects. Social network metrics have also been used to predict defect occurrence. However, such studies often ignore or side-step the issue of whether (and in what way) the metrics and networks of study are influenced by inadequate or missing data. In previous studies email archives of OSS projects have provided a useful trace of the communication and co-ordination activities of the participants. These traces have been used to construct social networks that are then subject to various types of analysis. However, during the construction of these networks, some assumptions are made, that may not always hold; this leads to incomplete, and sometimes incorrect networks. The question then becomes, do these errors affect the validity of the ensuing analysis? In this paper we specifically examine the stability of network metrics in the presence of inadequate and missing data. The issues that we study are: 1) the effect of paths with broken information flow (i.e. consecutive edges which are out of temporal order) on measures of centrality of nodes in the network, and 2) the effect of missing links on such measures. We demonstrate on three different OSS projects that while these issues do change network topology, the metrics used in the analysis are stable with respect to such changes.},
	keywords = {apache, email archives, mailing lists, missing data, mysql, perl, social networks},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463342},
	attachments = {https://flosshub.org/sites/flosshub.org/files/201NetworkAnalysis.pdf},
	author = {Nia, Roozbeh and Christian Bird and Devanbu, Premkumar and Filkov, Vladimir}
}
@book {1250,
	title = {Warehousing and Studying Open Source Versioning Metadata},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: New Horizons (OSS 2010)},
	volume = {319},
	year = {2010},
	pages = {413 - 418},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {In this paper, we describe the downloading and warehousing of Open Source Software (OSS) versioning metadata from SourceForge, BerliOS Developer, and GNU Savannah. This data enables and supports research in areas such as software engineering, open source phenomena, social network analysis, data mining, and project management. This newly-formed database containing Concurrent Versions System (CVS) and Subversion (SVN) metadata offers new research opportunities for large-scale OSS development analysis. The CVS and SVN data is juxtaposed with the SourceForge.net Research Data Archive [5] for the purpose of performing more powerful and interesting queries. We also present an initial statistical analysis of some of the most active projects. },
	keywords = {berlios, cvs, savannah, scm, sourceforge, srda, subversion, svn},
	isbn = {978-3-642-13244-5},
	issn = {1861-2288},
	doi = {10.1007/978-3-642-13244-5_40},
	author = {van Antwerp, M. and Madey, G.},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Madey, Gregory R. and Noll, John}
}
@conference {937,
	title = {Assigning bug reports using a vocabulary-based expertise model of developers},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {131 - 140},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {For popular software systems, the number of daily submitted bug reports is high. Triaging these incoming reports is a time consuming task. Part of the bug triage is the assignment of a report to a developer with the appropriate expertise. In this paper, we present an approach to automatically suggest developers who have the appropriate expertise for handling a bug report. We model developer expertise using the vocabulary found in their source code contributions and compare this vocabulary to the vocabulary of bug reports. We evaluate our approach by comparing the suggested experts to the persons who eventually worked on the bug. Using eight years of Eclipse development as a case study, we achieve 33.6\% top-1 precision and 71.0\% top-10 recall.},
	keywords = {bug reports, bugzilla, develect, developers, eclipse, expertise, scm},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069491},
	attachments = {https://flosshub.org/sites/flosshub.org/files/131AssigningBugReports.pdf},
	author = {Matter, Dominique and Kuhn, Adrian and Nierstrasz, Oscar}
}
@article {Subramaniam:2009:DOS:1480545.1480824,
	title = {Determinants of open source software project success: A longitudinal study},
	journal = {Decis. Support Syst.},
	volume = {46},
	year = {2009},
	month = {January},
	pages = {576{\textendash}585},
	publisher = {Elsevier Science Publishers B. V.},
	address = {Amsterdam, The Netherlands, The Netherlands},
	abstract = {In this paper, we investigate open source software (OSS) success using longitudinal data on OSS projects. We find that restrictive OSS licenses have an adverse impact on OSS success. On further analysis, restrictive OSS license is found to be negatively associated with developer interest, but is positively associated with the interest of non-developer users and project administrators. We also show that developer and non-developer interest in the OSS project and the project activity levels in any time period significantly affect the project success measures in subsequent time period. The implications of our findings for OSS research and practice are discussed. },
	keywords = {contributors, developers, licenses, longitudinal study, Open source project, OSS, project success, restrictive, Software project success},
	issn = {0167-9236},
	doi = {10.1016/j.dss.2008.10.005},
	url = {http://portal.acm.org/citation.cfm?id=1480545.1480824},
	author = {Subramaniam, Chandrasekar and Sen, Ravi and Nelson, Matthew L.}
}
@conference {bird2009pat,
	title = {{Putting it All Together: Using Socio-Technical Networks to Predict Failures}},
	booktitle = {Proceedings of the 17th International Symposium on Software Reliability Engineering},
	year = {2009},
	note = {First, we build each type of network separately and use network analysis on both to gather metrics for use in a predictive model. Second, we build a socio-technical network which combines the nodes and edges from both the dependency network and the contribution network and use metrics gathered from this network in a predictive model.
We evaluate our approach by collecting data from Mi- crosoft Windows Vista and ECLIPSE development and using logistic regression analysis.},
	abstract = {Studies have shown that social factors in development organizations have a dramatic effect on software quality. Separately, program dependency information has also been used successfully to predict which software components are more fault prone. Interestingly, the influence of these two phenomena have only been studied separately. Intuition and practical experience suggests, however, that task assignment (i.e. who worked on which components and how much) and dependency structure (which components have dependencies on others) together interact to influence the quality of the resulting software. We study the influence of combined socio-technical software networks on the fault-proneness of individual software components within a system. The network properties of a software component in this combined network are able to predict if an entity is failure prone with greater accuracy than prior methods which use dependency or contribution information in isolation. We evaluate our approach in different settings by using it on Windows Vista and across six releases of the Eclipse development environment including using models built from one release to predict failure prone components in the next release. We compare this to previous work. In every case, our method performs as well or better and is able to more accurately identify those software components that have more post-release failures, with precision and recall rates as high as 85\%.},
	keywords = {eclipse, microsoft, social network, vista, windows},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2009pat.pdf},
	author = {Christian Bird and Nachiappan Nagappan and Devanbu, Premkumar and Gall, Harald and Brendan Murphy}
}
@conference {765,
	title = {The role of patch review in software evolution: an analysis of the mozilla firefox},
	booktitle = {The joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops},
	year = {2009},
	month = {08/2009},
	pages = {9-18},
	publisher = {ACM},
	organization = {ACM},
	type = {Paper in Conference Proceedings},
	address = {Amsterdam, The Netherlands},
	abstract = {Patch review is the basic mechanism for validating the design and implementation of patches and maintaining consistency in some commercial and Free/Libre/Open Source Software (FLOSS) projects. We examine the inner-workings of the development process of the successful and mature Mozilla foundation and highlight how different parties involved affect and steer the process. Although reviewers are the primary actors in the patch review process, success in the process can only be achieved if the community supports reviewers adequately. Peer developers play the supporting role by offering insight and ideas that help create more quality patches. Moreover, they reduce the huge patch backlog reviewers have to clear by identifying and eliminating immature patches.},
	keywords = {inspection, open source development},
	isbn = {978-1-60558-678-6},
	doi = {http://doi.acm.org/10.1145/1595808.1595813},
	url = {http://ase.cpsc.ucalgary.ca/ase/uploads/Publications/iwpse31-nurolahzade.pdf},
	author = {Mehrdad Nurolahzade},
	editor = {Seyed Mehdi Nasehi and Shahedul Huq Khandkar and Shreya Rawal}
}
@conference {852,
	title = {Short and Tweet: Experiments on Recommending Content from Information},
	booktitle = {Proceedings of the 28th annual conference on Human Factors in Computing Systems},
	year = {2009},
	month = {04/10/10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Atlanta, GA},
	author = {Chen, J and Nairn, R. and Nelson, L. and Bernstein, M. and Chi, E.}
}
@article {Fang:2009:USP:1554441.1554443,
	title = {Understanding Sustained Participation in Open Source Software Projects},
	journal = {J. Manage. Inf. Syst.},
	volume = {25},
	year = {2009},
	month = {April},
	pages = {9{\textendash}50},
	publisher = {M. E. Sharpe, Inc.},
	address = {Armonk, NY, USA},
	abstract = {Prior research into open source software (OSS) developer participation has emphasized individuals{\textquoteright} motivations for joining these volunteer communities, but it has failed to explain why people stay or leave in the long run. Building upon Lave and Wenger{\textquoteright}s theory of legitimate peripheral participation (LPP), this paper offers a longitudinal investigation of one OSS community in which sustained participation is hypothesized to be associated with the coevolution of two major elements of LPP theory: "situated learning" (the process of acting knowledgeably and purposefully in the world) and "identity construction" (the process of being identified within the community). To test this hypothesis, data were collected from multiple sources, including online public project documents, electronic mail messages, tracker messages, and log files. Results from qualitative analyses revealed that initial conditions to participate did not effectively predict long-term participation, but that situated learning and identity construction behaviors were positively linked to sustained participation. Furthermore, this study reveals that sustained participants distinguished themselves by consistently engaging in situated learning that both made conceptual (advising others) and practical contributions (improving the code). Implications and future research are discussed.},
	keywords = {Communities Of Practice, Legitimate Peripheral Participation, Open Source Projects, Open Source Software Community, Qualitative Study},
	issn = {0742-1222},
	doi = {10.2753/MIS0742-1222250401},
	url = {http://portal.acm.org/citation.cfm?id=1554441.1554443},
	author = {Fang, Yulin and Neufeld, Derrick}
}
@conference {804,
	title = {Users of Open Source Software - How do they get help?},
	booktitle = {HICSS 2009},
	year = {2009},
	abstract = {A study was conducted across multiple open source software online technical help communities. This paper presents the types of discussions that occur, the types of questions asked and the type of responses that are given. The implications for socio-technical design are considered, exploring how help requests and discussions can be used to improve future help-giving, documentation and interface and functionality redesign.},
	keywords = {technical help},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.489},
	author = {Singh, V and Twidale, M.B and Nichols, D.M}
}
@article {10.1109/HICSS.2009.1005,
	title = {Users of Open Source Software - How Do They Get Help?},
	journal = {42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	note = {"we collected twenty threads each from eight different websites making a total of 160 threads"},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {A study was conducted across multiple open source software online technical help communities. This paper presents the types of discussions that occur, the types of questions asked and the type of responses that are given. The implications for socio-technical design are considered, exploring how help requests and discussions can be used to improve future help-giving, documentation and interface and functionality redesign.},
	keywords = {technical help},
	isbn = {978-0-7695-3450-3},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.1005},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-04.pdf},
	author = {Singh, Vandana and Michael B Twidale and David M Nichols}
}
@conference {595,
	title = {What Constitutes Open Source? A Study of the Vista Electronic Medical Record Software},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	year = {2009},
	month = {2009///},
	pages = {310 - 319},
	publisher = {Springer},
	organization = {Springer},
	chapter = {27},
	abstract = {Strictly speaking, Open Source Software is any program that is covered by an Open Source Software license. However, the notion of Open Source Software Development conjures images of high-quality, market dominating products developed by armies of volunteer programmers, who work only for the joy of programming. Certainly, banner projects like Apache, the Linux kernel, and Mozilla/Firefox resemble this notion, even if they do employ significant numbers of paid programmers. This paper examines three Open Source Software projects related to the Vista Electronic Medical Record system developed and maintained by the U.S. Department of Veterans Affairs and released to the public domain. While all three claim to be {\textquotedblleft}Open Source{\textquotedblright} projects, there is considerable deviation from the strong community-oriented model that Linux, Apache, and Mozilla represent.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/What\%20Constitues\%20Open\%20Source.pdf},
	author = {Noll, John}
}
@conference {861,
	title = {Altruism, Selfishness, and Destructiveness on the Social Web},
	booktitle = {5th International Conference on Adaptive Hypermedia and Adaptive Web-Based Systems},
	year = {2008},
	month = {7/29/2008},
	pages = {9-11},
	publisher = {Springer-Verlag},
	organization = {Springer-Verlag},
	address = {Hannover, Germany},
	isbn = {978-3-540-70984-8 },
	author = {Riedl, J.},
	editor = {Nejdl, W., Kay, J., Pu, P., Herder, E.}
}
@conference {Hill:2008:AAM:1370750.1370771,
	title = {AMAP: automatically mining abbreviation expansions in programs to enhance software maintenance tools},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {79{\textendash}88},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {When writing software, developers often employ abbreviations in identifier names. In fact, some abbreviations may never occur with the expanded word, or occur more often in the code. However, most existing program comprehension and search tools do little to address the problem of abbreviations, and therefore may miss meaningful pieces of code or relationships between software artifacts. In this paper, we present an automated approach to mining abbreviation expansions from source code to enhance software maintenance tools that utilize natural language information. Our scoped approach uses contextual information at the method, program, and general software level to automatically select the most appropriate expansion for a given abbreviation. We evaluated our approach on a set of 250 potential abbreviations and found that our scoped approach provides a 57\% improvement in accuracy over the current state of the art.},
	keywords = {automatic abbreviation expansion, azureus, itext.net, liferay, maintenance, natural language, openoffice.org, program comprehension, source code, tiger envelopes, tools},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370771},
	url = {http://doi.acm.org/10.1145/1370750.1370771},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p79-hill.pdf},
	author = {Hill, Emily and Fry, Zachary P. and Boyd, Haley and Sridhara, Giriprasad and Novikova, Yana and Pollock, Lori and Vijay-Shanker, K.}
}
@conference {1815,
	title = {An Exploratory Study on the Evolution of OSS Developer Communities},
	booktitle = {Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008)},
	year = {2008},
	pages = {305 - 305},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, HI, USA},
	abstract = {Software is developed in a dynamic context where team structure, requirements, and processes evolve together with the product. Although researchers have been studying the evolution of software systems since the early 70s, the study on the evolution of software development teams remains rare. Such evolutionary patterns and their impact on software quality are especially important in the context of OSS (Open Source Software) development, where a group of volunteer developers collaborate online for an extended period of time. By analyzing how social networks of developers evolve over time while building OSS products, we can gain knowledge and experience to improve the effectiveness and efficiency of resource management and distribution in future OSS projects. To this end, we studied the evolution of the developer communities using a suite of OSS products developed under the KOffice project. We found that in general, the social networks of OSS developer communities change over time in certain ways. Identifying such patterns can help OSS managers better understand the unique process of OSS development and improve their management and coordination of the projects.
},
	doi = {10.1109/HICSS.2008.58},
	url = {https://www.researchgate.net/publication/221184171_An_Exploratory_Study_on_the_Evolution_of_OSS_Developer_Communities},
	author = {Ngamkajornwiwat, Kawin and Zhang, Dongsong and Koru, A. Gunes and Zhou, Lina and Nolker, and Robert}
}
@mastersthesis {484,
	title = {Licensing Freedom; An Ethical Analysis of Free and Open Source Software Licenses},
	year = {2008},
	month = {January},
	abstract = {Free and open source software enables users to use, read and modify the source code of computer programs. In proprietary software, access to the source code is not given and users are generally not permitted to use, read and modify the source code. Opponents of a proprietary system state that proprietary software is morally wrong and in this thesis, the arguments they use are evaluated.Several licensing schemes can be used as an addition to copyright law to give users the rights described above. The most important division between these different licenses can be made on the basis of the use of the copyleft principle. This principle obliges the licensee to distribute modified versions of the software under the same, or similar terms as the original license. In this thesis, this obligation is seen as a restriction on the freedom of the individual. Comparisons and possible justifications will give better insight in this supposed contradiction.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Thesis_SaskiavandeNieuwenhof.pdf},
	author = {Saskia van de Nieuwenhof}
}
@booklet {525,
	title = {Open Source: The Next Big Thing In Technology Transfer to Developing Nations},
	year = {2008},
	month = {March},
	abstract = {Free Open Source (FOS) should be one of the least expensive and most effective solutions for technology and knowledge transfer to developing nations. This concept has diffused to several fields such as software, hardware, and content. FOS offers not only a low cost alternative for technology acquisition, but also for networking based on cooperation. In addition, the transaction costs of communication, licensing and negotiations are minimized, freeing up funds for real development. In this paper, FOS incentives, indicators, and measures are explained and the advantages of FOS as a viable technology and knowledge transfer tool for developing countries are highlighted.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1569088836.pdf},
	author = {Jamil Alkhatib and Mohab Anis and Hamid Noori}
}
@conference {533,
	title = {Requirements Acquisition in Open Source Development: Firefox 2.0},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {69 - 79},
	publisher = {Springer},
	organization = {Springer},
	chapter = {6},
	abstract = {Open Source Software Development appears to depart radically from conventional notions of software engineering. In particular, requirements for Open Source projects seem to be asserted rather than elicited. This paper examines features of the latest major release of the Firefox web browser in attempt to understand how prevalent this phenomenon is. Using archives of mailing lists and issue tracking databases, these features were traced from first mention to release, to determine the process by which requirements are proposed, adopted, and implemented in Firefox. The results confirm the importance of user participation as developers of open source products.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Requirements\%20Acquisition.pdf},
	author = {Noll, John}
}
@conference {WeiBgerber:2008:SPG:1370750.1370767,
	title = {Small patches get in!},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {67{\textendash}76},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {While there is a considerable amount of research on analyzing the change information stored in software repositories, only few researcher have looked at software changes contained in email archives in form of patches. In this paper we look at the email archives of two open source projects and answer questions like the following: How many emails contain patches? How long does it take for a patch to be accepted? Does the size of the patch influence its chances to be accepted or the duration until it gets accepted? Obviously, the answers to these questions can be helpful for the authors of patches, in particular because some of the answers are surprising.},
	keywords = {case study, cvs, email, email archives, flac, mailing list, openafs, patch acceptance, patches, revision control, scm},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370767},
	url = {http://doi.acm.org/10.1145/1370750.1370767},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p67-weissgerber.pdf},
	author = {Wei{\ss}gerber, Peter and Neu, Daniel and Diehl, Stephan}
}
@conference {1003,
	title = {Evaluating the Harmfulness of Cloning: A Change Based Experiment},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {18 - 18},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Cloning is considered a harmful practice for software maintenance because it requires consistent changes of the entities that share a cloned fragment. However this claim has not been refuted or confirmed empirically. Therefore, we have developed a prototype tool, CloneTracker, in order to study the rate of change of applications containing clones. This paper describes CloneTracker and illustrates its preliminary application on a case study.},
	keywords = {ccfinder, clone, clones, clonetracker, cloning, ctags, cvs, dnsjava, maintenance, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.8},
	author = {Lozano, Angela and Wermelinger, Michel and Nuseibeh, Bashar}
}
@conference {625,
	title = {Innovation in Open Source Software Development: A Tale of Two Features},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	note = {"archives of project discussion forums were then examined to determine when the feature was first proposed, how it was debated, and when it was ultimately adopted"},
	month = {2007///},
	pages = {109 - 120},
	publisher = {Springer},
	organization = {Springer},
	chapter = {9},
	abstract = {Open Source Software Development appears to depart radically from conventional notions of software engineering. In particular, requirements for Open Source projects seem to be asserted rather than elicited. This paper examines two features of selected open source products: {\textquotedblleft}tabbed browsing{\textquotedblright} as realized in the Firefox web browser, and {\textquotedblleft}edge magnetism{\textquotedblright} found in the Gnome desktop environment{\textquoteright}s Metacity window manager. Using archives of mailing lists and issue tracking databases, these features were traced from first mention to release, in attempt to discover the process by which requirements are proposed, adopted, and implemented in their respective Open Source projects. The results confirm the importance of user participation in Open Source projects.
},
	keywords = {email, email archives, features, Firefox, gnome, mailing list, metacity, mozilla},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Innovation\%20in\%20OSS.pdf},
	author = {Noll, John}
}
@mastersthesis {486,
	title = {Open Source Software: The use of open source},
	year = {2007},
	abstract = {This thesis explores the reasons behind the poor level of adoption of open source web GIS software, and whether it is due to poor awareness about open source concepts or due to technical deficiencies in the open source tools. The research was done in 2 major phases; the first phase involved conducting surveys to measure the awareness and attitudes towards open source. The surveys examined three categories of people involved in the IT industry, namely: decision makers, software developers, and end users. The measurement of awareness was done by developing an Awareness Indicator and a Sentiment Indicator for each category. These indicators were developed by the author during the course of the study in order to provide a measurable and descriptive indication of the results. The second phase involved performing a comparative analysis between MapServer a leading open source web GIS tool, and three of the leading proprietary web GIS software, namely: ESRI{\textquoteright}s ArcIMS, Intergraph{\textquoteright}s GeoMedia WebMap, and MapInfo{\textquoteright}s MapXtreme.

The results of the research provide an insight on how different categories of people view open source, and demonstrate that lack of awareness about open source concepts and its competencies may be a major reason behind the poor adoption of open source solutions. The results of the comparative analysis also demonstrate that MapServer is technically equivalent to its commercial counter parts.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OpenSourceGIS.pdf},
	author = {Mahmoud Refaat Nasr}
}
@conference {634,
	title = {Reusing an open source application {\textemdash} practical experiences with a mobile CRM pilot},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	year = {2007},
	month = {2007///},
	pages = {217 - 222},
	publisher = {Springer},
	organization = {Springer},
	chapter = {18},
	abstract = {We discuss experiences in extending an open source CRM application to develop a new server-based mobile business application. Combining the application code reuse with incremental development process allowed successful development of a pilot application in a tight schedule. In particular, it enabled a quick start for customer-driven development, diminished risks related to the baseline application itself, and provided the flexibility needed in experimental pilot development.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Reusing\%20an\%20Open\%20Source\%20Application.pdf},
	author = {Akkanen, Jyrki and Demeter, Hunor and Eppel, Tam{\'a}s and Iv{\'a}nfi, Zolt{\'a}n and Nurminen, Jukka and Stenman, Petri}
}
@conference {993,
	title = {Spam Filter Based Approach for Finding Fault-Prone Software Modules},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {4 - 4},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Because of the increase of needs for spam e-mail detection, the spam filtering technique has been improved as a convenient and effective technique for text mining. We propose a novel approach to detect fault-prone modules in a way that the source code modules are considered as text files and are applied to the spam filter directly. In order to show the applicability of our approach, we conducted experimental applications using source code repositories of Java based open source developments. The result of experiments shows that our approach can classify more than 75\% of software modules correctly.},
	keywords = {argouml, bug reports, classification, eclipse, java, modules, scm, spam, text mining},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300004.pdf},
	author = {Mizuno, Osamu and Ikami, Shiro and Nakaichi, Shuya and Kikuno, Tohru}
}
@unpublished {flosswp366,
	title = {The use of open source GIS software and its impact on organizations},
	year = {2007},
	month = {September},
	abstract = {This thesis explores the reasons behind the poor level of adoption of open source web GIS software, and whether it is due to poor awareness about open source concepts or due to technical deficiencies in the open source tools. The research was done in 2 major phases; the first phase involved conducting surveys to measure the awareness and attitudes towards open source. The surveys examined three categories of people involved in the IT industry, namely: decision makers, software developers, and end users. The measurement of awareness was done by developing an Awareness Indicator and a Sentiment Indicator for each category. These indicators were developed by the author during the course of the study in order to provide a measurable and descriptive indication of the results. The second phase involved performing a comparative analysis between MapServer a leading open source web GIS tool, and three of the leading proprietary web GIS software, namely: ESRI???s ArcIMS, Intergraph???s GeoMedia WebMap, and MapInfo???s MapXtreme. The results of the research provide an insight on how different categories of people view open source, and demonstrate that lack of awareness about open source concepts and its competencies may be a major reason behind the poor adoption of open source solutions. The results of the comparative analysis also demonstrate that MapServer is technically equivalent to its commercial counter parts.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OS_GIS.pdf},
	author = {Mahmoud Refaat Nasr}
}
@article {flosswp338,
	title = {What motivates Wikipedians: motivations for Wikipedia content contribution},
	year = {2007},
	month = {January},
	abstract = {Contributors??? motivations are critical for sustaining Wikipedia and other collaborative user-generated content outlets. Such outlets are based on contributions by people who volunteer their time and talent for the creation of content in return for no monetary reward. Therefore, in order to understand what underlies user-generated content contribution, we would need to find out what motivates volunteer content contributors. The results of a survey of 151 Wikipedia contributors indicate that the top motivations for contribution are Fun and Ideology. As expected, it was found that the levels of each of the motivations Fun, Values, Understanding, Enhancement, Protective, and Career were positively correlated with contribution level. Somewhat unexpectedly, contribution level was not correlated significantly with the Ideology and Social motivations.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Nov_Wikipedia_motivations_opensource.mit.edu.pdf},
	author = {Oded Nov}
}
@article {895,
	title = {Multi-Modal Modeling, Analysis and Validation of Open Source Software Development Processes},
	journal = {Intern. J. Internet Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	pages = {49-63},
	abstract = {Understanding the context, structure, activities, and content of software development processes found in practice has been and remains a challenging problem. In the world of free/open source software development, discovering and understanding what processes are used in particular projects is important in determining how they are similar to or different from those advocated by the software engineering community. Prior studies have revealed that development processes in F/OSSD projects are different in a number of ways. In this paper, we describe how a variety of modeling perspectives and techniques are used to elicit, analyze, and validate software development processes found in F/OSSD projects, with examples drawn from studies of the software requirements process found in the NetBeans.org project.},
	keywords = {empirical studies of software engineering, open source software development, process modeling, requirements processes, software process},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Scacchi-Jensen-Noll-Elliott-OSSC05.pdf},
	author = {Walt Scacchi and Chris Jensen and Noll, J. and Elliott, M.}
}
@article {808,
	title = {Usability processes in open source projects},
	journal = {Software Process: Improvement and Practice},
	volume = {11},
	year = {2006},
	month = {03/2006},
	pages = {149 - 162},
	abstract = {We explore how some open source projects address issues of usability. We describe the mechanisms, techniques and technology used by open source communities to design and refine the interfaces to their programs. In particular we consider how these developers cope with their distributed community, lack of domain expertise, limited resources and separation from their users. We also discuss how bug reporting and discussion systems can be improved to better support bug reporters and open source developers.},
	issn = {1099-1670},
	doi = {10.1002/spip.256},
	author = {David M Nichols and Michael B Twidale}
}
@proceedings {citeulike:3052508,
	title = {Development Success in Open Source Software Projects: Exploring the Impact of Copylefted Licenses},
	year = {2005},
	abstract = {Copyleft prevents the source code of open source software (OSS) from being privately appropriated. The ethos of the OSS movement suggests that volunteer developers may particularly value and contribute to copylefted projects. Based on social movement theory, we hypothesized that copylefted OSS projects are more likely than non-copylefted OSS projects to succeed in the development process, in terms of two key indicators: developer membership and developer productivity. We performed an exploratory study using data from 62 relevant OSS projects spanning an average of three years of development time. We found that copylefted projects were associated with higher developer membership and productivity. This is the first study to empirically test the relationship between copylefted licenses and OSS project success. Implications for OSS project initiators as well as future research directions are discussed.},
	keywords = {contributions, copyleft, developer, developers, membership, productivity, project success, success},
	url = {http://aisel.isworld.org/password.asp?Vpath=AMCIS/2005\&\#38;PDFpath=OSSDAU01-1167.pdf},
	author = {Colazo, Jorge A. and Fang, Yulin and Neufeld, Derrick J.}
}
@article {63,
	title = {The Jikes research virtual machine project: Building an open-source research community},
	journal = {Ibm Systems Journal},
	volume = {44},
	number = {2},
	year = {2005},
	note = {Times Cited: 3},
	pages = {399-417},
	abstract = {This paper describes the evolution of the Jikes (TM) Research Virtual Machine project from an IBM internal research project, called Jalapeno, into an open-source project. After summarizing the original goals of the project, we discuss the motivation for releasing it as an open-source project and the activities performed to ensure the success of the project. Throughout, we highlight the unique challenges of developing and maintaining an open-source project designed specifically to support a research community.},
	author = {Alpern, B. and Augart, S. and Blackburn, S. M. and Butrico, M. and Cocchi, A. and Cheng, P. and Dolby, J. and Fink, S. and Grove, D. and Hind, M. and McKinley, K. S. and Mergen, M. and Moss, J. E. B. and Ngo, T. and Sarkar, V. and Trapp, M.}
}
@conference {741,
	title = {Modular Design and the Development of Complex Artifacts: Lessons from Free/Open Source Software},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {162-171},
	abstract = {Organizational and managerial theories of modularity applied to the design and production of complex artifacts are used to interpret the rise and success of development methodologies and practices in Free/Open Source software projects. Strengths and risks of the adoption of a modular approach in software project management are introduced and are related to the achievements of various Free/Open Source Software projects (among them: the GNU operating system, the Linux kernel, the HURD kernel). It is suggested that mindful implementation of the principles of modularity may improve the rate of success of many Free/Open Source software projects. Specific case studies here depicted, as well as indirect observation of common programming practices employed by Free/Open Source developers and users, suggest a possible revision towards an improved theory of modularity that may be extended also to settings different from software production.},
	url = {http://pascal.case.unibz.it/handle/2038/979},
	author = {Alessandro Narduzzo and Rossi, Alessandro}
}
@conference {715,
	title = {Multi-Modal Modeling of Open Source Software Requirements Processes},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {1-8},
	abstract = {Understanding the context, structure, activities, and content of software development processes found in practice has been and remains a challenging problem. In the world of free/open source software development, discovering and understanding what processes are used in particular projects is important in determining how they are similar to or different from those advocated by the software engineering community. Prior studies however have revealed that the requirements processes in OSSD projects are different in a number of ways, including the general lack of explicit software requirements specifications. In this paper, we describe how a variety of modeling perspectives and techniques are used to elicit, analyze, and validate software requirements processes found in OSSD projects, with examples drawn from studies of the NetBeans.org project.},
	url = {http://pascal.case.unibz.it/handle/2038/975},
	author = {Walt Scacchi and Chris Jensen and Noll, John and Elliott, Margaret}
}
@conference {745,
	title = {Quantifying the Interest in Open Source Systems: Case South-East Finland},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {192-195},
	abstract = {Open source systems (OSS) has emerged as one of the most interesting phenomena in software engineering today. Unfortunately, only little hard data is available to quantify the interest in OSS in commercially operating software houses. As a part of a local initiative to increase the alignment between the software industry and software engineering research and education, a state of the practice survey was conducted in the local software houses. Due to the globally recognized interest in OSS some explorative questions on the topic were included in the survey. The results of the survey indicate widespread interest in OSS in the industry, and even though the study had a strictly regional focus, the results provide quantitative support for future research on OSS.},
	url = {http://pascal.case.unibz.it/handle/2038/1434},
	author = {Nikula, Uolevi and Jantunen, Sami}
}
@conference {Neamtiu:2005:USC:1083142.1083143,
	title = {Understanding source code evolution using abstract syntax tree matching},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {2-6},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Mining software repositories at the source code level can provide a greater understanding of how software evolves. We present a tool for quickly comparing the source code of different versions of a C program. The approach is based on partial abstract syntax tree matching, and can track simple changes to global variables, types and functions. These changes can characterize aspects of software evolution useful for answering higher level questions. In particular, we consider how they could be used to inform the design of a dynamic software updating system. We report results based on measurements of various versions of popular open source programs, including BIND, OpenSSH, Apache, Vsftpd and the Linux kernel.},
	keywords = {abstract syntax trees, apache, bind, evolution, linux, openssh, software evolution, source code, source code analysis, vsftpd},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083143},
	url = {http://doi.acm.org/10.1145/1082983.1083143},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2Understanding.pdf},
	author = {Neamtiu, Iulian and Foster, Jeffrey S. and Hicks, Michael}
}
@conference {Kim:2005:UCG:1083142.1083146,
	title = {Using a clone genealogy extractor for understanding and supporting evolution of code clones},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {17-23},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Programmers often create similar code snippets or reuse existing code snippets by copying and pasting. Code clones {\textemdash}syntactically and semantically similar code snippets{\textemdash}can cause problems during software maintenance because programmers may need to locate code clones and change them consistently. In this work, we investigate (1) how code clones evolve, (2) how many code clones impose maintenance challenges, and (3) what kind of tool or engineering process would be useful for maintaining code clones.
Based on a formal definition of clone evolution, we built a clone genealogy tool that automatically extracts the history of code clones from a source code repository (CVS). Our clone genealogy tool enables several analyses that reveal evolutionary characteristics of code clones. Our initial results suggest that aggressive refactoring may not be the best solution for all code clones; thus, we propose alternative tool solutions that assist in maintaining code clones using clone genealogy information.},
	keywords = {clone, clone detection, cvs, developers, evolution, maintenance, refactoring, source code},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083146},
	url = {http://doi.acm.org/10.1145/1082983.1083146},
	attachments = {https://flosshub.org/sites/flosshub.org/files/17Using.pdf},
	author = {Kim, Miryung and Notkin, David}
}
@conference {724,
	title = {Using Open Source Tools to Support Collaboration Within CALIBRE},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {61-65},
	abstract = {This paper describes the deployment of Plone, an Open-Source content management system, to support the activities of CALIBRE, an EU-funded coordination action integrating research into Libre software. The criteria by which Plone was selected are described, and the goodness of fit to these criteria is analysed. As a coordination action, CALIBRE involves 12 partners with different requirements and characteristics. The CALIBRE Working Environment (CWE) must therefore support a variety of users with different levels of technical expertise and expectations. Implementation of the support infrastructure for CALIBRE is ongoing, and has provided some interesting insights into the benefits of the use of libre software. Although Plone has not been explicitly developed as a collaboration infrastructure, with its wealth of plugins, it has proven highly adaptable for this purpose.},
	url = {http://pascal.case.unibz.it/handle/2038/1555},
	author = {Adams, Paul and Nutter, David and Rank, Stephen and Boldyreff, Cornelia}
}
@conference {778,
	title = {Using Plone To Support Collaborative Research},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {296-297},
	keywords = {collaboration environment, collaborative research, content management system, open source, plugin},
	url = {http://pascal.case.unibz.it/handle/2038/1558},
	author = {Adams, Paul and Nutter, David and Rank, Stephen and Boldyreff, Cornelia}
}
@proceedings {1188,
	title = {Communication and Conflict Issues in Collaborative Software Research Projects},
	year = {2004},
	pages = {14-17},
	abstract = {The Open Source Component Artefact Repository (OSCAR) was developed under the auspices of the GENESIS project to store data produced during the software development process. Significant problems were encountered during the course of the project in both the development itself and management of the project. The reasons for and potential solutions to these problems are examined with the intention of developing a set of guidelines to enable participants in other collaborative projects to avoid these pitfalls.
We wish to make it clear that we attach no opprobrium to any of the participants in the GENESIS project as many of the issues we outline below have solutions only visible with hindsight. Instead, we seek to provide a fair-minded critique of our role and the mistakes we made in a fairly typical two-year EU research project, and to provide a set of recommendations for other similar projects, in order that they can (attempt to) avoid suffering similarly.},
	keywords = {artefact, cvs, genesis, oscar},
	attachments = {https://flosshub.org/sites/flosshub.org/files/boldyreff15-18.pdf},
	author = {Boldyreff, Cornelia and Nutter, David and Rank, Stephen}
}
@book {122,
	title = {Cyberscience: Research in the Age of the Internet},
	year = {2003},
	publisher = {Austrian Academy of Sciences},
	organization = {Austrian Academy of Sciences},
	address = {Vienna},
	author = {Michael Nentwich}
}
@article {flosswp87,
	title = {Modularity in Action: GNU/Linux and Free/Open Source Software Development Model Unleashed},
	year = {2003},
	month = {May},
	abstract = {Organizational and managerial theories of modularity applied to the design and production of complex artifacts are used to interpret the rise and success of Free/Open Source Software. Strengths and risks of the adoption of a modular approach in software project management are introduced and are related to the achievements of the GNU/Linux project. It is suggested that mindful implementation of the principles of modularity may improve the rate of success of many Free/Open Source software projects. Authors suggest a possible revision towards an improved theory of modularity that may be extended also to settings different from software production.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/narduzzorossi.pdf},
	author = {Alessandro Narduzzo}
}
@article {123,
	title = {Open source software development and Lotka{\textquoteright}s Law: Bibliometric patterns in programming},
	journal = {Journal of the American Society for Information Science and Technology},
	volume = {54},
	number = {2},
	year = {2003},
	note = {"Two lead- ing metadata repositories are the Linux Software Map (LSM) and Sourceforge, both of which were used for this research."
"For this article, we examined data listing the number of registered developers for each software project hosted by Sourceforge."
"The data we obtained from the LSM collection were taken mainly from the Author: field of LSM records. The Author: field in LSM records gives us the ability to track the author of record for a software package. LSM metadata also include a list of maintainers, primary software distribution sites, date of update and other items."
"The data we obtained from Sourceforge consist of a list of developer ID numbers, followed by the number of projects on which the individual is listed as a developer, then the number of projects on which the individual is listed as an administrator. These data were provided for all 33,892 individuals registered to work on projects hosted by Sourceforge in July 2001."},
	pages = {169-178},
	abstract = {This research applies Lotka{\textquoteright}s Law to metadata on open source software development. Lotka{\textquoteright}s Law predicts the proportion of authors at different levels of productivity. Open source software development harnesses the creativity of thousands of programmers worldwide, is important to the progress of the Internet and many other computing environments, and yet has not been widely researched. We examine metadata from the Linux Software Map (LSM), which documents many open source projects, and Sourceforge, one of the largest resources for open source developers. Authoring patterns found are comparable to prior studies of Lotka{\textquoteright}s Law for scientific and scholarly publishing. Lotka{\textquoteright}s Law was found to be effective in understanding software development productivity patterns, and offer promise in predicting aggregate behavior of open source developers.},
	keywords = {developers, linux, linux software map, lsm, sourceforge, team size},
	doi = {10.1002/asi.10177},
	author = {Newby, G. B. and Greenberg, J. and Jones, P.}
}
@article {flosswp71,
	title = {Open Source Software Development: Some Historical Perspectives},
	year = {2003},
	month = {January},
	abstract = {In this paper we suggest that historical studies of technology can help us to account for some, perplexing (at least for traditional economic reasoning) features of open source software development. When looked in historical perspective, open source software seems to be a particular case of what Robert Allen has termed "collective invention". We explore the interpretive value of this historical parallel in detail, comparing open source software with two remarkable episodes of nineteenth century technical advances.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nuvolari.pdf},
	author = {Alessandro Nuvolari}
}
@proceedings {1166,
	title = {Open-Source Development Processes and Tools},
	year = {2003},
	pages = {15-18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/15-18.pdf},
	author = {Boldyreff, Cornelia and Lavery, J. and Nutter, David and Rank, Stephen}
}
@article {flosswp97,
	title = {Participatory Usability: supporting proactive users},
	journal = {Proceedings of the 4th Annual Conference of the ACM Special Interest Group on Computer Human Interaction - New Zealand Chapter (CHINZ{\textquoteright}03)},
	year = {2003},
	month = {June},
	pages = {63{\textendash}68},
	publisher = {ACM SIGCHI New Zealand.},
	abstract = {After software has been released the opportunities for users to influence development can often be limited. In this paper we review the research on post-deployment usability and make explicit its connections to open source software development. We describe issues involved in the design of end-user reporting tools with reference to the Safari web browser and a digital library prototype.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nicholsmckaytwidale.pdf},
	author = {David M Nichols and Dana McKay and Michael B Twidale}
}
@article {Nichols02usabilityand,
	title = {The Usability of Open Source Software},
	journal = {First Monday},
	volume = {8},
	year = {2003},
	abstract = {Open source communities have successfully developed a great deal of software although most computer users only use proprietary applications. The usability of open source software is often regarded as one reason for this limited distribution. In this paper we review the existing evidence of the usability of open source software and discuss how the characteristics of open source development influence usability. We describe how existing human-computer interaction techniques can be used to leverage distributed networked communities, of developers and users, to address issues of usability.},
	url = {http://firstmonday.org/article/view/1018/939},
	author = {David M Nichols and Michael B Twidale}
}
@conference {Nakakoji:2002:EPO:512035.512055,
	title = {Evolution patterns of open-source software systems and communities},
	booktitle = {Proceedings of the International Workshop on Principles of Software Evolution},
	series = {IWPSE {\textquoteright}02},
	year = {2002},
	pages = {76{\textendash}85},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open-Source Software (OSS) development is regarded as a successful model of encouraging "natural product evolution". To understand how this "natural product evolution" happens, we have conducted a case study of four typical OSS projects. Unlike most previous studies on software evolution that focus on the evolution of the system per se, our study takes a broader perspective: It examines not only the evolution of OSS systems, but also the evolution of the associated OSS communities, as well as the relationship between the two types of evolution.Through the case study, we have found that while collaborative development within a community is the essential characteristic of OSS, different collaboration models exist, and that the difference in collaboration model results in different evolution patterns of OSS systems and communities. To treat such differences systematically, we propose to classify OSS into three types: Exploration-Oriented, Utility-Oriented, and Service-Oriented. Such a classification can provide guidance on the creation and maintenance of sustainable OSS development and communities.},
	keywords = {case study, open-source software (OSS), open-source software community, software evolution},
	isbn = {1-58113-545-9},
	doi = {10.1145/512035.512055},
	url = {http://doi.acm.org/10.1145/512035.512055},
	author = {Nakakoji, Kumiyo and Yamamoto, Yasuhiro and Nishinaka, Yoshiyuki and Kishida, Kouichi and Ye, Yunwen}
}
@conference {1152,
	title = {Open-Source Artefact Management},
	booktitle = {2nd Workshop on Open Source Software Engineering at ICSE 2002},
	year = {2002},
	abstract = {This paper presents the GENESIS project, which aims to develop an open-source, lightweight, process-aware (and process-neutral) workflow management system. In particular OSCAR, the artefact repository is discussed. The requirements of a system for artefact management and storage are described, and the concept of active artefacts is explained. The software engineering methods which will be used in the project are described, and some examples of the open-source tools which may be used are described.},
	keywords = {artefacts, artifacts, genesis, oscar, workflow},
	attachments = {https://flosshub.org/sites/flosshub.org/files/BoldyreffNutterRank.pdf},
	author = {Boldyreff, Cornelia and Nutter, David and Rank, Stephen}
}
@article {flosswp56,
	title = {Permanently Beta: Responsive Organization in the Internet Era},
	year = {2002},
	month = {September},
	abstract = {How has the process of technological change in the Internet era influenced the way we organize economic activities? In this paper we discuss how information technologies foster the emergent design and user-driven design of websites and other online media, as well as products and organizations offline. A cycle of testing, feedback, and innovation facilitates ongoing negotiations around making products and around organizing that production. We call the organizational state of flux that emerges from these negotiations Permanently Beta. Beta testing, open source software, and interactive communities manifest aspects of permanently beta organization.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/neff-stark.pdf},
	author = {Gina Neff}
}
@conference {Dinkelacker:2002:POS:581339.581363,
	title = {Progressive open source},
	booktitle = {Proceedings of the 24th International Conference on Software Engineering},
	series = {ICSE {\textquoteright}02},
	year = {2002},
	pages = {177{\textendash}184},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The success of several Open Source{\texttrademark} software systems, e.g., Apache, Bind, Emacs, and Linux, has recently sparked interest in studying and emulating the software engineering principles underlying this innovative development and use model. Certain aspects of the Open Source development method, e.g., community building, open discussions for requirements and features, and evolvable and modular designs are having fundamental and far reaching consequences on general software engineering practices.To leverage such Open Source methods and tools, we have defined an innovative software engineering paradigm for large corporations: Progressive Open Source (POS). POS leverages the power of Open Source methods and tools for large corporations in a progressive manner: starting from completely within the corporation, to include partner businesses, and eventually complete Open Source. In this paper we present the design goals and principles for POS. We illustrate POS with two programs in HP: Corporate Source and the Collaborative Development Program (CDP). We present early results from both these programs suggesting the power and necessity of POS for all modern large corporations.},
	keywords = {companies},
	isbn = {1-58113-472-X},
	doi = {10.1145/581339.581363},
	url = {http://doi.acm.org/10.1145/581339.581363},
	author = {Dinkelacker, Jamie and Garg, Pankaj K. and Miller, Rob and Nelson, Dean}
}
@article {flosswp98,
	title = {Usability and Open Source Software},
	journal = {Working Paper 02/10, Department of Computer Science, University of Waikato},
	year = {2002},
	month = {December},
	publisher = {Department of Computer Science, University of Waikato},
	abstract = {Open source communities have successfully developed many pieces of software although most computer users only use proprietary applications. The usability of open source software is often regarded as one reason for this limited distribution. In this paper we review the existing evidence of the usability of open source software and discuss how the characteristics of open-source development influence usability. We describe how existing human-computer interaction techniques can be used to leverage distributed networked communities, of developers and users, to address issues of usability.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nicholstwidale1.pdf},
	author = {David M Nichols and Michael B Twidale}
}
@article {flosswp31,
	title = {Managing Information Quality in Virtual Communities of Practice},
	year = {2001},
	month = {November},
	abstract = {In this paper we review how the new economics of information enable a new paradigm of collaboration. Spearheaded by the Open Source community, this evolutionary approach to collaborative content creation is a way to address information quality in virtual communities of practice. Based on experience gained in community projects, a few simple steps toward improving the quality of information in virtual communities are presented and illustrated.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/neus.pdf},
	author = {Andreas Neus}
}
@conference {1147,
	title = {Open Source Software Developments in XP Style},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nisinaka.pdf},
	author = {Nishinaka, Y.}
}
@conference {1146,
	title = {Taxonomy of Open Source Software Development},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	keywords = {jun, linux, postgresql, wingnut},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nakakojiyamamoto.PDF},
	author = {Nakakoji, K. and Yamamoto, Y.}
}
@article {flosswp47,
	title = {Usability and open-source software development},
	journal = {Proceedings of the Symposium on Computer Human Interaction},
	year = {2001},
	month = {June},
	pages = {49{\textendash}54},
	publisher = {ACM SIGCHI New Zealand},
	abstract = {This paper reports a usability study of the open-source Greenstone Digital Library collection-building software. The problems highlighted by the study are analysed to identify their likely source within the social context of Greenstone{\textquoteright}s development environment. We discuss how characteristics of open-source software development influence the usability of resulting software products.},
	keywords = {Greenstone, user study},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nichols.pdf},
	author = {David M Nichols and Kirsten Thomson and Stuart A Yeates}
}
