@proceedings {1890,
	title = {Designing for Participation: Three Models for Developer Involvement in Hybrid OSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {23-33},
	publisher = {Springer},
	abstract = {This paper reports governance practices of three profit oriented companies that develop OSS software with the help of their respective open development communities. We explore how the companies allow development contributions from external stakeholders, and what knowledge they let out of their internal software development activities. The results lay ground for further research on how to organize openness of the software development process in hybrid setups where the needs of different stakeholders are partly competing - yet complementary.},
	keywords = {Community Management, Hybrid open source, open source},
	doi = {10.1007/978-3-319-57735-7_3},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_3},
	author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and Mikkonen, Tommi and M{\"a}nnist{\"o}, Tomi}
}
@proceedings {1894,
	title = {Digging into the Eclipse Marketplace},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {60-65},
	publisher = {Springer},
	abstract = {Eclipse is an integrated development environment that can be extended with plug-ins. Thanks to Eclipse{\textquoteright}s success, a diverse community has been established with members coming from industry, open-source projects, and others, and a marketplace with more than 1.700 different plug-ins developed. Hence, the question arises how this marketplace is composed: Who contributes plug-ins? Which plug-ins are successful? Are there common characteristics or trends? To answer these questions, extensive investigations are necessary. In this paper, we present (i) an initial approach for corresponding analyses and (ii) preliminary results. Overall, we aim to pave the way for further research addressing, for example, motivations to participate in, or the evolution of, open marketplaces.},
	keywords = {Eclipse IDE, Eclipse Marketplace, empirical study, open source},
	doi = {10.1007/978-3-319-57735-7_7},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_7},
	author = {Kr{\"u}ger, J and Corr, N and Schr{\"o}ter, I and Leich, T}
}
@inbook {Kerzazi2017,
	title = {Knowledge Flows Within Open Source Software Projects: A Social Network Perspective},
	booktitle = {Advances in Ubiquitous Networking 2: Proceedings of the UNet{\textquoteright}16},
	year = {2017},
	pages = {247{\textendash}258},
	publisher = {Springer Singapore},
	organization = {Springer Singapore},
	address = {Singapore},
	abstract = {Developing software is knowledge-intensive activity, requiring extensive technical knowledge and awareness. The abstract part of development is the social interactions that drive knowledge flows between contributors, especially for Open Source Software (OSS). This study investigated knowledge sharing and propagation from social perspective using social network analysis (SNA). We mined and analyzed the issue and review histories of three OSS from GitHub. Particular attention has been paid to the socio-interactions through comments from contributors on reviews. We aim at explaining the propagation and density of knowledge flows within contributor networks. The results show that review requests flow from the core contributors toward peripheral contributors and comments on reviews are in a continuous loop from the core teams to the peripherals and back; and the core contributors leverage on their awareness and technical knowledge to increase their notoriety by playing the role of communication brokers supported by comments on work items.},
	keywords = {expertise, Knowledge flows, open source, SNA},
	isbn = {978-981-10-1627-1},
	doi = {10.1007/978-981-10-1627-1_19},
	url = {http://dx.doi.org/10.1007/978-981-10-1627-1_19},
	author = {Kerzazi, Noureddine and El Asri, Ikram},
	editor = {El-Azouzi, Rachid and Menasche, Daniel Sadoc and Sabir, Essa{\"\i}d and De Pellegrini, Francesco and Benjillali, Mustapha}
}
@proceedings {1904,
	title = {OSSpal: Finding and Evaluating Open Source Software},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {193-203},
	publisher = {Springer},
	abstract = {This paper describes the OSSpal project, which is aimed at helping companies, government agencies, and other organizations find high quality free and open source software (FOSS) that meets their needs. OSSpal is a successor to the Business Readiness Rating (BRR), combining quantitative and qualitative evaluation measures for software in various categories. Instead of a purely numeric calculated score OSSpal adds curation of high-quality FOSS projects and individual user reviews of these criteria. Unlike the BRR project, for which there was no automated support, OSSpal has an operational, publicly available website where users may search by project name or category, and enter ratings and reviews for projects.

},
	keywords = {Open source forges, software evaluation, software metrics, Software taxonomy},
	doi = {10.1007/978-3-319-57735-7_18},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_18},
	author = {Wasserman, A. and Guo, X. and McMillian, B. and Qian K. and Wei M.Y. and Xu, Q.}
}
@proceedings {1888,
	title = {Technical Lag in Software Compilations: Measuring How Outdated a Software Deployment Is},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {182 - 192},
	publisher = {Springer International Publishing},
	abstract = {Large software compilations based on free, open source software (FOSS) packages are the basis for many software systems. When they are deployed in production, specific versions of the packages in the compilation are selected for installation. Over time, those versions become outdated with respect to the upstream software from which they are produced, and from the components available in the compilations as well. The fact that deployed components are outdated is not a problem in itself, but there is a price to pay for not being "as much updated as reasonable". This includes bug fixes and new features that could, at least potentially, be interesting for the deployed system. Therefore, a balance has to be maintained between "being up-to-date" and "keeping the good old working versions". This paper proposes a theoretical model (the "technical lag") for measuring how outdated a system is, with the aim of assisting in the decisions about upgrading in production. The paper explores several ways in which technical lag can be implemented, depending on requirements. As an illustration, it presents as well some specific cases in which the evolution of technical lag is computed.},
	isbn = {978-3-319-57735-7},
	issn = {1868-422X},
	doi = {10.1007/978-3-319-57735-7_17},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_17},
	author = {Gonz{\'a}lez-Barahona, J.M. and Sherwood, P. and Robles, G. and Izquierdo, D.},
	editor = {Balaguer, Federico and Di Cosmo, Roberto and Garrido, Alejandra and Kon, Fabio and Gregorio Robles and Zacchiroli, Stefano}
}
@proceedings {1900,
	title = {Understanding When to Adopt a Library: A Case Study on ASF Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {128-138},
	publisher = {Springer},
	abstract = {Software libraries are widely used by both industrial and open source client projects. Ideally, a client user of a library should adopt the latest version that the library project releases. However, sometimes the latest version is not better than a previous version. This is because the latest version may include additional developer effort to test and integrate all changed features. In this study, our main goal is to better understand the relationship between adoption of library versions and its release cycle. Specifically, we conducted an empirical study of release cycles for 23 libraries and how they were adopted by 415 Apache Software Foundation (ASF) client projects. Our findings show that software projects are quicker to update earlier rapid-release libraries compared to library projects with a longer release cycle. Moreover, results suggest that software projects are more likely to adopt the latest version of a rapid-release library compared to libraries with a longer release cycles.},
	keywords = {adoption, apache, apache software foundation, libraries},
	doi = {10.1007/978-3-319-57735-7_13},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_13},
	author = {Ihara, Akinori and Daiki Fujibayashi and Hirohiko Suwa and Raula Gaikovina Kula and Kenichi Matsumoto}
}
@conference {Izquierdo-Cortazar:2017:UMT:3084226.3084247,
	title = {Using Metrics to Track Code Review Performance},
	booktitle = {Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering},
	series = {EASE{\textquoteright}17},
	year = {2017},
	pages = {214{\textendash}223},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {During 2015, some members of the Xen Project Advisory Board became worried about the performance of their code review process. The Xen Project is a free, open source software project developing one of the most popular virtualization platforms in the industry. They use a pre-commit peer review process similar to that in the Linux kernel, based on email messages. They had observed a large increase over time in the number of messages related to code review, and were worried about how this could be a signal of problems with their code review process.

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

In this paper we show the results of both analyses, and propose a comprehensive methodology, fully automated, to study Linux-style code review. We discuss also the problems of getting significant metrics to track improvements or detect problems in this kind of code review.},
	keywords = {code review, data mining, Software development analytics},
	isbn = {978-1-4503-4804-1},
	doi = {10.1145/3084226.3084247},
	url = {http://doi.acm.org/10.1145/3084226.3084247},
	author = {Izquierdo-Cortazar, Daniel and Sekitoleko, Nelson and Jesus M. Gonzalez-Barahona and Kurth, Lars}
}
@proceedings {1921,
	title = {Who Added that Permission to My App? An Analysis of Developer Permission Changes in Open Source Android Apps},
	year = {2017},
	note = {"Our first step was to collect open source Android repositories
from F-Droid ... We collected the git repositories for each
app, ... we recorded
all permissions, including those which were custom. 
At the time of our analysis, F-Droid contained information
for 2,372 open source Android apps. ... This process
identified 1,402 apps that had a AndroidManifest.xml file
with a history of commits... we created a tool
known as Open Source Android Repository Analyzer (oSARA)...we extracted version control
commit information ... extracts all committed AndroidManifest.xml
files from the version control history ...the committed
version of the AndroidManifest.xml file was also extracted
from the repositories, and all metadata was stored in a SQLite
database"},
	month = {05/2017},
	pages = {165-169},
	abstract = {Android applications rely on a permission-based
model to carry out core functionality. Appropriate permission
usage is imperative for ensuring device security and protecting
the user{\textquoteright}s desired privacy levels. But who is making the important
decisions of which permissions the app should request? Are they
experienced developers with the appropriate project knowledge to
make such important decisions, or are these crucial choices being
made by those with relatively minor amounts of contributions to
the project? When are these permission-related decisions being
made in the app{\textquoteright}s development life cycle? We examined 1,402
Android version control repositories containing over 331,318
commits including 18,751 AndroidManifest.xml versions to better
understand when, why, and who is adding permissions to apps.
We found that (I) developers with more experience are more
likely to make permission-based changes (II) permissions are
typically added earlier in apps{\textquoteright} commit lifetime, but their
removal is more sustained throughout the commit lifetime (III)
developers reverting permission-based changes are typically more
experienced than developers who initially made the change being
reverted.},
	keywords = {android, mobile},
	author = {Krutz, Daniel E. and Nuthan Munaiah and Anthony Peruma and Mohamed Wiem Mkaouer}
}
@proceedings {1819,
	title = {Analyzing the Decision Criteria of Software Developers Based on Prospect Theory},
	year = {2016},
	note = {they sent a survey to developers and used flossmole to harvest the email addresses},
	month = {03/2016},
	abstract = {To enhance the quality of software, many software development support tools and software development methodologies have been proposed. However, not all proposed tools and methodologies are widely used in software development. We assume that the evaluation of tools and methodologies by developers is different from the evaluation by researchers, and that this is one of the reasons why the tools and methodologies are not widely used. We analyzed the decision criteria of software developers as applied to the tools and methodologies, to clarify whether the difference exists or not. In behavioral economics, there are theories which assume people have biases, and they do not always act reasonably. In the experiment, we made a questionnaire based on behavioral economics, and collected answers from open source software developers. The results suggest that developers do not always act to maximize expected profit because of the certainty effect and ambiguity aversion. Therefore, we should reconsider the evaluation criteria of tools such as the f-measure or AUC, which mainly focus on the expected profit. },
	keywords = {flossmole},
	url = {http://se-naist.jp/pman3/pman3.cgi?DOWNLOAD=579},
	attachments = {https://flosshub.org/sites/flosshub.org/files/saner2016-kina.pdf},
	author = {Kanako Kina and Tsunoda, Masateru and Tamada, Haruaki and Hiroshi Igaki}
}
@inbook {Kalliamvakou2016,
	title = {Certification of Open Source Software {\textendash} A Scoping Review},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {111{\textendash}122},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Certification of Open Source Software {\textendash} A Scoping Review},
	address = {Cham},
	abstract = {Open source software (OSS) systems are being used for increasingly critical functions in modern societies, e.g., in health care, finance, government, defense, and other safety and security sensitive sectors. There is an increasing interest in software certification as a means to assure quality and dependability of such systems. However, the development processes and organizational structures of OSS projects can be substantially different from traditional closed-source projects. The distributed, {\textquotedblleft}bazaar-style{\textquotedblright} approach to software development in OSS systems is often perceived incompatible with certification. This paper presents the results of a scoping review on certification in OSS systems in order to identify and categorize key issues and provide a comprehensive overview of the current evidence on this topic.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_9},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_9},
	author = {Kalliamvakou, Eirini and Weber, Jens and Knauss, Alessia},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@article {adams2016empirical,
	title = {An empirical study of integration activities in distributions of open source software},
	journal = {Empirical Software Engineering},
	volume = {21},
	number = {3},
	year = {2016},
	pages = {960{\textendash}1001},
	publisher = {Springer},
	abstract = {Reuse of software components, either closed or open source, is considered to be one of the most important best practices in software engineering, since it reduces development cost and improves software quality. However, since reused components are (by definition) generic, they need to be customized and integrated into a specific system before they can be useful. Since this integration is system-specific, the integration effort is non-negligible and increases maintenance costs, especially if more than one component needs to be integrated. This paper performs an empirical study of multi-component integration in the context of three successful open source distributions (Debian, Ubuntu and FreeBSD). Such distributions integrate thousands of open source components with an operating system kernel to deliver a coherent software product to millions of users worldwide. We empirically identified seven major integration activities performed by the maintainers of these distributions, documented how these activities are being performed by the maintainers, then evaluated and refined the identified activities with input from six maintainers of the three studied distributions. The documented activities provide a common vocabulary for component integration in open source distributions and outline a roadmap for future research on software integration.

},
	url = {http://mcis.soccerlab.polymtl.ca/publications/2016/integration_oss_distribution.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/integration_oss_distribution.pdf},
	author = {Adams, Bram and Kavanagh, Ryan and Hassan, Ahmed E. and Daniel M. German}
}
@article {kazman2016evaluating,
	title = {Evaluating the Effects of Architectural Documentation: A Case Study of a Large Scale Open Source Project},
	journal = {IEEE Transactions on Software Engineering},
	volume = {42},
	number = {3},
	year = {2016},
	pages = {220{\textendash}260},
	publisher = {IEEE},
	abstract = {Sustaining large open source development efforts requires recruiting new participants; however, a lack of
architectural documentation might inhibit new participants since large amounts of project knowledge are unavailable to
newcomers. We present the results of a multitrait, multimethod analysis of the effects of introducing architectural documentation
into a substantial open source project{\textemdash}the Hadoop Distributed File System (HDFS). HDFS had only minimal architectural
documentation, and we wanted to discover whether the putative benefits of architectural documentation could be observed over
time. To do this, we created and publicized an architecture document and then monitored its usage and effects on the project.
The results were somewhat ambiguous: by some measures the architecture documentation appeared to effect the project but
not by others. Perhaps of equal importance is our discovery that the project maintained, in its web-accessible JIRA archive of
software issues and fixes, enough architectural discussion to support architectural thinking and reasoning. This {\textquotedblleft}emergent{\textquotedblright}
architecture documentation served an important purpose in recording core project members{\textquoteright} architectural concerns and
resolutions. However, this emergent architecture documentation did not serve all project members equally well; it appears that
those on the periphery of the project{\textemdash}newcomers and adopters{\textemdash}still require explicit architecture documentation, as we will
show.},
	author = {Kazman, Rick and Goldenson, Dennis and Monarch, Ira and Nichols, William and Valetto, Giuseppe}
}
@inbook {Poo-Caama{\~n}o2016,
	title = {Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {147{\textendash}162},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem},
	address = {Cham},
	abstract = {Release management in large-scale software development projects requires significant communication and coordination. It is particularly challenging in Free and Open Source Software (FOSS) ecosystems, in which hundreds of loosely connected developers and their projects need to be coordinated to release software to a schedule. To better understand this process and its challenges, we analyzed over two and half years of communication in the GNOME ecosystem and studied developers{\textquoteright} interactions. We cataloged communication channels, categorized high level communication and coordination activities in one of them, and triangulated our results by interviewing developers. We found that a release schedule, influence instead of direct control, and diversity are factors that impact positively the release process in the GNOME ecosystem. Our results can help organizations build better large-scale teams and show that research focused on individual projects might miss important parts of the picture.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_12},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_12},
	author = {Poo-Caama{\~n}o, Germ{\'a}n and Singer, Leif and Knauss, Eric and Daniel M. German},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@proceedings {1808,
	title = {How Do Free/Open Source Developers Pick Their Tools? A Delphi Study of the Debian Project},
	year = {2016},
	abstract = {Free and Open Source Software (FOSS) has come to play a critical role in the global software industry. Organizations are widely adopting FOSS and interacting with open source communities, and hence organizations have a considerable interest in seeing these communities flourishing. Very little research has focused on the tools used to develop that software. Given the absence of organizational policies and mandate that would occur in a traditional environment, an open question is how FOSS developers decide what tools to use. In this paper we report on a policy delphi study conducted in the Debian Project, one of the largest FOSS projects. Drawing from data collected in three phases from a panel of 21 experts, we identified 15 factors that affect their decision to adopt tools. This in turn can help FOSS communities to define a suitable policy of actions, in order to improve their processes.},
	keywords = {Delphi, Free/Open Source Software, Qualitative Study, study, tools},
	url = {https://www.researchgate.net/publication/291312269_How_Do_FreeOpen_Source_Developers_Pick_Their_Tools_A_Delphi_Study_of_the_Debian_Project},
	author = {Martin Krafft and Stol, Klaas-Jan and Fitzgerald, Brian}
}
@inbook {M{\"a}enp{\"a}{\"a}2016,
	title = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {134{\textendash}146},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities},
	address = {Cham},
	abstract = {Today, the community driven development model extends into a variety of new, often web based collaborations. Among these are hybrid open source development set ups in which various online tools are used to facilitate cooperation between virtual teams of commercial and voluntary stakeholders. As yet, how these relationships form and evolve is not understood extensively. This article presents a longitudinal case study of a smartphone startup that founded its early product development strategy on reliance on feedback from its customers through a web based question and answer forum. With this, the company managed to extend values typical for open source communities to support development of its proprietary software. Our main findings include that the challenge in similar settings lies in striking the right balance between the open and the proprietary {\textendash} while overt openness may risk the competitive advantage of a company, leaving too much behind closed boundaries can create unnecessary friction in the relationship.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_11},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_11},
	author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and M{\"a}nnist{\"o}, Tomi},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@article {Kazuhiro Yamashita2016,
	title = {Magnet or Sticky? Measuring Project Characteristics from the Perspective of Developer Attraction and Retention},
	journal = {Journal of Information Processing},
	volume = {24},
	number = {2},
	year = {2016},
	pages = {339-348},
	abstract = {Open Source Software (OSS) is vital to both end users and enterprises. As OSS systems are becoming a type of infrastructure, long-term OSS projects are desired. For the survival of OSS projects, the projects need to not only retain existing developers, but also attract new developers to grow. To better understand how projects retain and attract contributors, our preliminary study aimed to measure the personnel attraction and retention of OSS projects using a pair of population migration metrics, called Magnet (personnel attraction) and Sticky (retention) metrics. Because the preliminary study analyzed only 90 projects and the 90 projects are not representative of GitHub, this paper extend the preliminary study to better understand the generalizability of the results by analyzing 16, 552 projects of GitHub. Furthermore, we also add a pilot study to investigate the typical duration between releases to find more appropriate release duration. The study results show that (1) approximately 23\% of developers remain in the same projects that the developers contribute to, (2) the larger projects are likely to attract and retain more developers, (3) 53\% of terminal projects eventually decay to a state of fewer than ten developers and (4) 55\% of attractive projects remain in an attractive category.
},
	keywords = {github, retention},
	doi = {10.2197/ipsjjip.24.339},
	url = {https://www.jstage.jst.go.jp/article/ipsjjip/24/2/24_339/_article},
	author = {Yamashita, Kazuhiro and Kamei, Yasutaka and McIntosh, Shane and Hassan, Ahmed E. and Ubayashi, Naoyasu}
}
@article {Krishnamurthy:2016:PDP:2869770.2820618,
	title = {Peripheral Developer Participation in Open Source Projects: An Empirical Analysis},
	journal = {ACM Trans. Manage. Inf. Syst.},
	volume = {6},
	number = {4},
	year = {2016},
	pages = {14:1{\textendash}14:31},
	publisher = {ACM},
	address = {New York, NY, USA},
	abstract = {The success of the Open Source model of software development depends on the voluntary participation of external developers (the peripheral developers), a group that can have distinct motivations from that of project founders (the core developers). In this study, we examine peripheral developer participation by empirically examining approximately 2,600 open source projects. In particular, we hypothesize that peripheral developer participation is higher when the potential for building reputation by gaining recognition from project stakeholders is higher. We consider recognition by internal stakeholders (such as core developers) and external stakeholders (such as end-users and peers). We find a positive association between peripheral developer participation and the potential of stakeholder recognition after controlling for bug reports, feature requests, and other key factors. Our findings provide important insights for OSS founders and corporate managers for open sourcing or OSS adoption decisions.
},
	keywords = {Code ownership, open source software, project management, software metrics},
	issn = {2158-656X},
	doi = {10.1145/2820618},
	url = {http://doi.acm.org/10.1145/2820618},
	author = {Krishnamurthy, Rajiv and Jacob, Varghese and Radhakrishnan, Suresh and Kutsal Dogan}
}
@proceedings {1763,
	title = {A Dataset of High Impact Bugs: Manually-Classified Issue Reports},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The importance of supporting test and maintenance
activities in software development has been increasing, since
recent software systems have become large and complex. Although
in the field of Mining Software Repositories (MSR) there
are many promising approaches to predicting, localizing, and
triaging bugs, most of them do not consider impacts of each
bug on users and developers but rather treat all bugs with equal
weighting, excepting a few studies on high impact bugs including
security, performance, blocking, and so forth. To make MSR
techniques more actionable and effective in practice, we need
deeper understandings of high impact bugs. In this paper we
introduced our dataset of high impact bugs which was created
by manually reviewing four thousand issue reports in four open
source projects (Ambari, Camel, Derby and Wicket).},
	keywords = {ambari, camel, derby, wicket},
	url = {http://oss.sys.wakayama-u.ac.jp/publications/pman3.cgi?DOWNLOAD=141},
	attachments = {https://flosshub.org/sites/flosshub.org/files/5594a518.pdf},
	author = {Ohira, Masao and Yutaro Kashiwa and Yosuke Yamatani and Hayato Yoshiyuki and Yoshiya Maeda and Nachai Limsettho and Keisuke Fujino and Hata, Hideaki and Ihara, Akinori and Kenichi Matsumoto}
}
@inbook {1730,
	title = {An Empirical Study of the Relation Between Strong Change Coupling and Defects Using History and Social Metrics in the Apache Aries Project},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {3-12},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Change coupling is an implicit relationship observed when artifacts change together during software evolution. The literature leverages change coupling analysis for several purposes. For example, researchers discovered that change coupling is associated with software defects and reveals relationships between software artifacts that cannot be found by scanning code or documentation. In this paper, we empirically investigate the strongest change couplings from the Apache Aries project to characterize and identify their impact in software development. We used historical and social metrics collected from commits and issue reports to build classification models to identify strong change couplings. Historical metrics were used because change coupling is a phenomenon associated with recurrent co-changes found in the software history. In turn, social metrics were used because developers often interact with each other in issue trackers to accomplish the tasks. Our classification models showed high accuracy, with 70-99 \% F-measure and 88-99 \% AUC. Using the same set of metrics, we also predicted the number of future defects for the artifacts involved in strong change couplings. More specifically, we were able to predict 45.7 \% of defects where these strong change couplings reoccurred in the post-release. These findings suggest that developers and projects managers should detect and monitor strong change couplings, because they can be associated with defects and tend to happen again in the subsequent release.},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_1},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_1},
	author = {Wiese, Igor Scaliante and Kuroda, Rodrigo Takashi and Re, Reginaldo and Oliva, Gustavo Ansaldi and Gerosa, MarcoAur{\'e}lio},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {1789,
	title = {The FLOSS History in Japan: An Ethnographic Approach},
	year = {2015},
	month = {08/2015},
	abstract = {This paper reports an overview of the Internet history project
which especially focuses on Free / Libre / Open-Source Software
(FLOSS) history. The project adopts an ethnographical
approach and it aims to compose a chronicle on the
growth of FLOSS history in Japan. An outcome of the
project is expected to be not only a record but a compass
for younger generations. The project has already started
and conducted several interviews. In this paper, an interim
report of our analysis based on the interviews is presented.},
	url = {http://www.opensym.org/os2015/proceedings-files/p105-iio.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p105-iio.pdf},
	author = {Iio, Jun and Hatta, Masayuki and Ko Kazaana}
}
@proceedings {KMGSL15,
	title = {Generating the Blueprints of the Java Ecosystem},
	year = {2015},
	note = {To appear},
	month = {05/2015},
	publisher = {IEEE Computer Society},
	url = {http://gaijin.dmst.aueb.gr/~bkarak/poster_msr2015.pdf},
	author = {Vassilios Karakoidas and Mitropoulos, Dimitris and Louridas, Panos and Gousios, Georgios and Diomidis Spinellis}
}
@article {1796,
	title = {An in-depth study of the promises and perils of mining GitHub},
	journal = {Empirical Software Engineering},
	year = {2015},
	publisher = {Springer},
	abstract = {With over 10 million git repositories, GitHub is becoming one of the most important sources of software artifacts on the Internet. Researchers mine the information stored in GitHub{\textquoteright}s event logs to understand how its users employ the site to collaborate on software, but so far there have been no studies describing the quality and properties of the available GitHub data. We document the results of an empirical study aimed at understanding the characteristics of the repositories and users in GitHub; we see how users take advantage of GitHub{\textquoteright}s main features and how their activity is tracked on GitHub and related datasets to point out misalignment between the real and mined data. Our results indicate that while GitHub is a rich source of data on software development, mining GitHub for research purposes should take various potential perils into consideration. For example, we show that the majority of the projects are personal and inactive, and that almost 40\% of all pull requests do not appear as merged even though they were. Also, approximately half of GitHub{\textquoteright}s registered users do not have public activity, while the activity of GitHub users in repositories is not always easy to pinpoint. We use our identified perils to see if they can pose validity threats; we review selected papers from the MSR 2014 Mining Challenge and see if there are potential impacts to consider. We provide a set of recommendations for software engineering researchers on how to approach the data in GitHub.},
	keywords = {github},
	issn = {1573-7616},
	doi = {10.1007/s10664-015-9393-5},
	url = {http://www.gousios.gr/pub/promises-perils-github-extended.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/promises-perils-github-extended.pdf},
	author = {Kalliamvakou, Eirini and Gousios, Georgios and Blincoe, Kelly and Singer, Leif and Daniel M. German and Damian, Daniela}
}
@article {1717,
	title = {An insight into license tools for open source software systems},
	journal = {Journal of Systems and Software},
	volume = {102},
	year = {2015},
	note = {"An additional tool can be found in FLOSSmole ( Howison et al., 2006), which is a central repository containing data and analyses about FLOSS projects collected and prepared in a decentralized manner. Content from FLOSSmole was intended to be used for the construction of an intelligent information system for FLOSS, namely FLOSSWALD (Hanft and Reichle, 2007). "},
	month = {04/2015},
	pages = {72 - 87},
	abstract = {Free/Libre/Open Source Software (FLOSS) has gained a lot of attention lately allowing organizations to incorporate third party source code into their implementations. When open source software libraries are used, software resources may be linked directly or indirectly with multiple open source licenses giving rise to potential license incompatibilities. Adequate support in license use is vital in order to avoid such violations and address how diverse licenses should be handled. In the current work we investigate software licensing giving a critical and comparative overview of existing assistive approaches and tools. These approaches are centered on three main categories: license information identification from source code and binaries, software metadata stored in code repositories, and license modeling and associated reasoning actions. We also give a formalization of the license compatibility problem and demonstrate the role of existing approaches in license use decisions.},
	keywords = {flossmole cited},
	issn = {01641212},
	doi = {10.1016/j.jss.2014.12.050},
	url = {http://www.sciencedirect.com/science/article/pii/S0164121214002945},
	author = {Kapitsaki, Georgia M. and Tselikas, Nikolaos D. and Foukarakis, Ioannis E.}
}
@proceedings {1776,
	title = {A Method to Detect License Inconsistencies in Large-Scale Open Source Projects},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The reuse of free and open source software (FOSS)
components is becoming more and more popular. They usually
contain one or more software licenses describing the requirements
and conditions which should be followed when been reused.
Licenses are usually written in the header of source code files as
program comments. Removing or modifying the license header
by re-distributors will result in the inconsistency of license with
its ancestor, and may potentially cause license infringement. But
to the best of our knowledge, no research has been devoted
to investigate such kind of license infringements nor license
inconsistencies. In this paper, we describe and categorize different
types of license inconsistencies and propose a feasible method to
detect them. Then we apply this method to Debian 7.5 and present
the license inconsistencies found in it. With a manual analysis, we
summarized various reasons behind these license inconsistencies,
some of which imply license infringement and require the attention
from the developers. This analysis also exposes the difficulty
to discover license infringements, highlighting the usefulness of
finding and maintaining source code provenance.},
	url = {http://sel.ist.osaka-u.ac.jp/lab-db/betuzuri/archive/992/992.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/992.pdf},
	author = {Yuhao Wu and Manabe, Yuki and Tetsuya Kanda and Daniel M. German and Inoue, Katsuro}
}
@proceedings {1726,
	title = {Open Source-Style Collaborative Development Practices in Commercial Projects Using GitHub},
	volume = {1},
	year = {2015},
	month = {05/2015},
	pages = {574-585},
	publisher = {ACM/IEEE},
	abstract = {Researchers are currently drawn to study projects
hosted on GitHub due to its popularity, ease of obtaining data,
and its distinctive built-in social features. GitHub has been found
to create a transparent development environment, which together
with a pull request-based workflow, provides a lightweight mechanism
for committing, reviewing and managing code changes.
These features impact how GitHub is used and the benefits it
provides to teams{\textquoteright} development and collaboration. While most of
the evidence we have is from GitHub{\textquoteright}s use in open source software
(OSS) projects, GitHub is also used in an increasing number of
commercial projects. It is unknown how GitHub supports these
projects given that GitHub{\textquoteright}s workflow model does not intuitively
fit the commercial development way of working. In this paper, we
report findings from an online survey and interviews with GitHub
users on how GitHub is used for collaboration in commercial
projects. We found that many commercial projects adopted
practices that are more typical of OSS projects including reduced
communication, more independent work, and self-organization.
We discuss how GitHub{\textquoteright}s transparency and popular workflow can
promote open collaboration, allowing organizations to increase
code reuse and promote knowledge sharing across their teams.},
	keywords = {github},
	doi = {10.1109/ICSE.2015.74},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icse-camera.pdf},
	author = {Kalliamvakou, E and Damian, Daniela and Blincoe, Kelly and Singer, L. and German, Daniel}
}
@inbook {1740,
	title = {The RISCOSS Platform for Risk Management in Open Source Software Adoption},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {124-133},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Managing risks related to OSS adoption is a must for organizations that need to smoothly integrate OSS-related practices in their development processes. Adequate tool support may pave the road to effective risk management and ensure the sustainability of such activity. In this paper, we present the RISCOSS platform for managing risks in OSS adoption. RISCOSS builds upon a highly configurable data model that allows customization to several types of scopes. It implements two different working modes: exploration, where the impact of decisions may be assessed before making them; and continuous assessment, where risk variables (and their possible consequences on business goals) are continuously monitored and reported to decision-makers. The blackboard-oriented architecture of the platform defines several interfaces for the identified techniques, allowing new techniques to be plugged in.
},
	keywords = {Open source adoption, Open Source Projects, open source software, OSS, Risk Management, Software platform},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_12},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_12},
	author = {Franch, X. and Kenett, R. and Mancinelli, F. and Susi, A. and Ameller, D. and Annosi, M.C. and Ben-Jacob, R. and Blumenfeld, Y. and Franco, O.H. and Gross, D. and Lopez, L. and Morandini, M. and Oriol, M. and Siena, A.},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@conference {zanjani2015developer,
	title = {Using Developer-Interaction Trails to Triage Change Requests},
	booktitle = {12th Working Conference on Mining Software Repositories (MSR 2015)},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {The paper presents an approach, namely iHDev, to recommend developers who are most likely to implement incoming change requests. The basic premise of iHDev is that the developers who interacted with the source code relevant to a given change request are most likely to best assist with its resolution. A machine-learning technique is first used to locate source-code entities relevant to the textual description of a given change request. iHDev then mines interaction trails (i.e., Mylyn sessions) associated with these source-code entities to recommend a ranked list of developers. iHDev integrates the interaction trails in a unique way to perform its task, which was not investigated previously. 
An empirical study on open source systems Mylyn and Eclipse Project was conducted to assess the effectiveness of iHDev. A number of change requests were used in the evaluated benchmark. Recall for top one to five recommended developers and Mean Reciprocal Rank (MRR) values are reported. Furthermore, a comparative study with two previous approaches that use commit histories and/or the source-code authorship information for developer recommendation was performed. Results show that iHDev could provide a recall gain of up to 127.27\% with equivalent or improved MRR values by up to 112.5\%.},
	url = {http://www.cabird.com/wp/zanjani2015developer/},
	attachments = {https://flosshub.org/sites/flosshub.org/files/zanjani2015developer.pdf},
	author = {Motahareh Bahrami Zanjani and Kagdi, Huzefa and Christian Bird}
}
@conference {Matragkas:2014:ABO:2597073.2597119,
	title = {Analysing the {\textquoteright}Biodiversity{\textquoteright} of Open Source Ecosystems: The GitHub Case},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {356{\textendash}359},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In nature the diversity of species and genes in ecological communities affects the functioning of these communities. Biologists have found out that more diverse communities appear to be more productive than less diverse communities. Moreover such communities appear to be more stable in the face of perturbations. In this paper, we draw the analogy between ecological communities and Open Source Software (OSS) ecosystems, and we investigate the diversity and structure of OSS communities. To address this question we use the MSR 2014 challenge dataset, which includes data from the top-10 software projects for the top programming languages on GitHub. Our findings show that OSS communities on GitHub consist of 3 types of users (core developers, active users, passive users). Moreover, we show that the percentage of core developers and active users does not change as the project grows and that the majority of members of large projects are passive users.
},
	keywords = {Data and knowledge visualization, data mining, mining challenge, msr challenge},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597119},
	url = {http://doi.acm.org/10.1145/2597073.2597119},
	author = {Matragkas, Nicholas and Williams, James R. and Kolovos, Dimitris S. and Paige, Richard F.}
}
@conference {Mitropoulos:2014:BCM:2597073.2597123,
	title = {The Bug Catalog of the Maven Ecosystem},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {372{\textendash}375},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Examining software ecosystems can provide the research community with data regarding artifacts, processes, and communities. We present a dataset obtained from the Maven central repository ecosystem (approximately 265GB of data) by statically analyzing the repository to detect potential software bugs. For our analysis we used FindBugs, a tool that examines Java bytecode to detect numerous types of bugs. The dataset contains the metrics results that FindBugs reports for every project version (a JAR) included in the ecosystem. For every version we also stored specific metadata such as the JAR{\textquoteright}s size, its dependencies and others. Our dataset can be used to produce interesting research results, as we show in specific examples.
},
	keywords = {findbugs, Maven Repository, msr data showcase, Software Bugs},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597123},
	url = {http://doi.acm.org/10.1145/2597073.2597123},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mitro.pdf},
	author = {Mitropoulos, Dimitris and Vassilios Karakoidas and Louridas, Panos and Gousios, Georgios and Diomidis Spinellis}
}
@inbook {1619,
	title = {The Census of the Brazilian Open-Source Community},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {202-211},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

During a long time, software engineering research has been trying to better understand open-source communities and uncover two fundamental questions: (i) who are the contributors and (i) why they contribute. Most of these researches focus on well-known OSS projects, but little is known about the OSS movement in emerging countries. In this paper, we attempt to fill this gap by presenting a picture of the Brazilian open-source contributor. To achieve this goal, we examined activities from more than 12,400 programmers on Github, during the period of a year. Subsequently, we correlate our findings with a survey that was answered by more than 1,000 active contributors. Our results show that exists an OSS trend in Brazil: most part of the contributors are active, performing around 30 contributions per year, and they contribute to OSS basically by altruism.
},
	keywords = {Brazilian OSS Community, github, OSS},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_30},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_30},
	author = {Pinto, Gustavo and Kamei, Fernando},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Krutz:2014:CCO:2597073.2597127,
	title = {A Code Clone Oracle},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {388{\textendash}391},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Code clones are functionally equivalent code segments. Detecting code clones is important for determining bugs, fixes and software reuse. Code clone detection is also essential for developing fast and precise code search algorithms. How- ever, the challenge of such research is to evaluate that the clones detected are indeed functionally equivalent, consider- ing the majority of clones are not textual or even syntactically identical. The goal of this work is to generate a set of method level code clones with a high confidence to help to evaluate future code clone detection and code search tools to evaluate their techniques. We selected three open source programs, Apache, Python and PostgreSQL, and randomly sampled a total of 1536 function pairs. To confirm whether or not these function pairs indicate a clone and what types of clones they belong to, we recruited three experts who have experience in code clone research and four students who have experience in programming for manual inspection. For confidence of the data, the experts consulted multiple code clone detection tools to make the consensus. To assist manual inspection, we built a tool to automatically load function pairs of interest and record the manual inspection results. We found that none of the 66 pairs are textual identical type- 1 clones, and 9 pairs are type-4 clones. Our data is available at: http://phd.gccis.rit.edu/weile/data/cloneoracle/.
},
	keywords = {clone, Clone Oracle, Code Clone Detection, msr data showcase, software engineering},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597127},
	url = {http://doi.acm.org/10.1145/2597073.2597127},
	attachments = {https://flosshub.org/sites/flosshub.org/files/clone_oracle.pdf},
	author = {Krutz, Daniel E. and Le, Wei}
}
@conference {Wu:2014:EES:2556420.2556483,
	title = {Exploring the Ecosystem of Software Developers on GitHub and Other Platforms},
	booktitle = {Proceedings of the Companion Publication of the 17th ACM Conference on Computer Supported Cooperative Work \&\#38; Social Computing},
	series = {CSCW Companion {\textquoteright}14},
	year = {2014},
	pages = {265{\textendash}268},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {GitHub provides various social features for developers to collaborate with others. Those features are important for developers to coordinate their work (Dabbish et al., 2012; Marlow et al., 2013). We hypothesized that the social system of GitHub users was bound by system interactions such that contributing to similar code repositories would lead to users following one another on GitHub or vice versa. Using a quadratic assignment procedure (QAP) correlation, however, only a weak correlation among followship and production activities (code, issue, and wiki contributions) was found. Survey with GitHub users revealed an ecosystem on the Internet for software developers, which includes many platforms, such as Forrst, Twitter, and Hacker News, among others. Developers make social introductions and other interactions on these platforms and engage with one anther on GitHub. Due to these preliminary findings, we describe GitHub as a part of a larger ecosystem of developer interactions.
},
	keywords = {ecosystem, follow, github, social connection},
	isbn = {978-1-4503-2541-7},
	doi = {10.1145/2556420.2556483},
	url = {http://doi.acm.org/10.1145/2556420.2556483},
	author = {Wu, Yu and Kropczynski, Jessica and Shih, Patrick C. and Carroll, John M.}
}
@conference {Bloemen:2014:GPD:2597073.2597131,
	title = {Gentoo Package Dependencies over Time},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {404{\textendash}407},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source distributions such as Gentoo need to accurately track dependency relations between software packages in order to install working systems. To do this, Gentoo has a carefully authored database containing those relations. In this paper, we extract the Gentoo package dependency graph and its changes over time. The final dependency graph spans 15 thousand open source projects and 80 thousand dependency relations. Furthermore, the development of this graph is tracked over time from the beginning of the Gentoo project in 2000 to the first quarter of 2012, with monthly resolution. The resulting dataset provides many opportunities for research. In this paper we explore cluster analysis to reveals meaningful relations between packages and in a separate paper we analyze changes in the dependencies over time to get insights in the innovation dynamics of open source software.
},
	keywords = {dependencies, gentoo, graph, INNOVATION},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597131},
	url = {http://doi.acm.org/10.1145/2597073.2597131},
	author = {Bloemen, Remco and Amrit, Chintan and Kuhlmann, Stefan and Ord{\'o}{\~n}ez{\textendash}Matamoros, Gonzalo}
}
@conference {Bloemen:2014:IDO:2597073.2597079,
	title = {Innovation Diffusion in Open Source Software: Preliminary Analysis of Dependency Changes in the Gentoo Portage Package Database},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {316{\textendash}319},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper we make the case that software dependencies are a form of innovation adoption. We then test this on the time-evolution of the Gentoo package dependency graph. We find that the Bass model of innovation diffusion fits the growth of the number of packages depending on a given library. Interestingly, we also find that low-level packages have a primarily imitation driven adoption and multimedia libraries have primarily innovation driven growth.
},
	keywords = {dependencies, gentoo, graph, INNOVATION},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597079},
	url = {http://doi.acm.org/10.1145/2597073.2597079},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bloeman.pdf},
	author = {Bloemen, Remco and Amrit, Chintan and Kuhlmann, Stefan and Ord{\'o}{\~n}ez{\textendash}Matamoros, Gonzalo}
}
@inbook {1612,
	title = {A Layered Approach to Managing Risks in OSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {168-171},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

In this paper, we propose a layered approach to managing risks in OSS projects. We define three layers: the first one for defining risk drivers by collecting and summarising available data from different data sources, including human-provided contextual information; the second layer, for converting these risk drivers into risk indicators; the third layer for assessing how these indicators impact the business of the adopting organisation. The contributions are: 1) the complexity of gathering data is isolated in one layer using appropriate techniques, 2) the context needed to interpret this data is provided by expert involvement evaluating risk scenarios and answering questionnaires in a second layer, 3) a pattern-based approach and risk reasoning techniques to link risks to business goals is proposed in the third layer.
},
	keywords = {Layered Model, open source, OSS, Risk Management},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_23},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_23},
	author = {Franch, Xavier and Kenett, Ron and Mancinelli, Fabio and Susi, Angelo and Ameller, David and Ben-Jacob, Ron and Siena, Alberto},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Yamashita:2014:MSO:2597073.2597116,
	title = {Magnet or Sticky? An OSS Project-by-project Typology},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {344{\textendash}347},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {For Open Source Software (OSS) projects, retaining existing contributors and attracting new ones is a major concern. In this paper, we expand and adapt a pair of population migration metrics to analyze migration trends in a collection of open source projects. Namely, we study: (1) project stickiness, i.e., its tendency to retain existing contributors and (2) project magnetism, i.e., its tendency to attract new contributors. Using quadrant plots, we classify projects as attractive (highly magnetic and sticky), stagnant (highly sticky, weakly magnetic), fluctuating (highly magnetic, weakly sticky), or terminal (weakly magnetic and sticky). Through analysis of the MSR challenge dataset, we find that: (1) quadrant plots can effectively identify at-risk projects, (2) stickiness is often motivated by professional activity and (3) transitions among quadrants as a project ages often coincides with interesting events in the evolution history of a project.
},
	keywords = {Developer migration, Magnet, mining challenge, msr challenge, open source, Sticky},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597116},
	url = {http://doi.acm.org/10.1145/2597073.2597116},
	attachments = {https://flosshub.org/sites/flosshub.org/files/yamashita.pdf},
	author = {Yamashita, Kazuhiro and McIntosh, Shane and Kamei, Yasutaka and Ubayashi, Naoyasu}
}
@conference {Eckhardt:2014:MMO:2642803.2642810,
	title = {The Merits of a Meritocracy in Open Source Software Ecosystems},
	booktitle = {Proceedings of the 2014 European Conference on Software Architecture Workshops},
	series = {ECSAW {\textquoteright}14},
	year = {2014},
	pages = {7:1{\textendash}7:6},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The Eclipse open source ecosystem has grown from a small internal IBM project to one of the biggest Integrated Development Environments in the market. Open source communities and ecosystems do not follow the standard governance strategies typically used in large organizations. A meritocracy is a frequently occurring form of governance on different levels in open ecosystems. In this paper we investigate how this form of governance influences the health of projects within the Eclipse ecosystem in terms of the amount of commits within each month. We analyzed the hierarchy of Eclipse, how merits are conceptualized within the ecosystem and the effect of the appointments of mentors and project leads on the amount of commits. From our research, we can conclude that this system is not always as fair as it seems; merits are only a benefit in some cases.},
	keywords = {Ecosystem Health, Meritocracy, open source, Software ecosystems},
	isbn = {978-1-4503-2778-7},
	doi = {10.1145/2642803.2642810},
	url = {http://doi.acm.org/10.1145/2642803.2642810},
	author = {Eckhardt, Evert and Kaats, Erwin and Slinger Jansen and Alves, Carina}
}
@article {1637,
	title = {Microblogging in Open Source Software Development: The Case of Drupal and Twitter},
	journal = {IEEE Software},
	volume = {31},
	year = {2014},
	month = {7/2014},
	pages = {72 - 80},
	abstract = {Microblogging is a popular form of social media that has quickly permeated both enterprise and open source communities. However, exactly how open source communities can leverage microblogging isn{\textquoteright}t yet well understood. The authors investigate how Drupal{\textquoteright}s open source community uses Twitter, a household name in microblogging. Their analysis of group and individual accounts of Drupal developers reveals that they take on similar but distinct roles. Both serve as communicators of essential links to a vast and growing community knowledge base, such as work artifacts, issues, documentation, and blog posts, but community members often express positive emotions when tweeting about work, which reinforces a sense of community.},
	issn = {0740-7459},
	doi = {10.1109/MS.2013.98},
	author = {Wang, Xiaofang and Kuzmickaja, Ilona and Stol, Klaas-Jan and Abrahamsson, Pekka and Fitzgerald, Brian}
}
@conference {Williams:2014:MOP:2597073.2597132,
	title = {Models of OSS Project Meta-information: A Dataset of Three Forges},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	note = {"FLOSSMole [4] is a similar initiative to OSSMETER; it
aims to collect and freely redistribute in different formats
the data of open source software. Differently from OSSMETER,
however, the FLOSSMole project does not provide the
instruments to analyse data, that are simply collected and
made publicly available."},
	pages = {408{\textendash}411},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The process of selecting open-source software (OSS) for adoption is not straightforward as it involves exploring various sources of information to determine the quality, maturity, activity, and user support of each project. In the context of the OSSMETER project, we have developed a forge-agnostic metamodel that captures the meta-information common to all OSS projects. We specialise this metamodel for popular OSS forges in order to capture forge-specific meta-information. In this paper we present a dataset conforming to these metamodels for over 500,000 OSS projects hosted on three popular OSS forges: Eclipse, SourceForge, and GitHub. The dataset enables different kinds of automatic analysis and supports objective comparisons of cross-forge OSS alternatives with respect to a user{\textquoteright}s needs and quality requirements.
},
	keywords = {data mining, flossmole cited},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597132},
	url = {http://doi.acm.org/10.1145/2597073.2597132},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Models_of_OSS_Project_Meta-Information_A_Dataset_of_Three_Forges_draft.pdf},
	author = {Williams, James R. and Di Ruscio, Davide and Matragkas, Nicholas and Di Rocco, Juri and Kolovos, Dimitris S.}
}
@inbook {1592,
	title = {Navigation Support in Evolving Open-Source Communities by a Web-Based Dashboard},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {11-20},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

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

To answer this research question, we first conducted an online survey within different successful OSS communities. The results of our evaluation showed that there is a great interest in community-centered statistics. Therefore, we developed an OSS navigator: a Web-based dashboard for community-oriented reflection of OSS projects. The navigator was filled with data from communication and development repositories of three large bioinformatics OSS projects. The members of these OSS communities tested the prototype. The bioinformatics OSS developers acknowledged the uniqueness of statistics that the NOSE dashboard offers. Especially, graph visualization of the project social network received the highest attention. This network view combined with other community-oriented metrics can significantly enhance the existing visualizations or even be provided as a standalone tool.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_2},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_2},
	author = {Hannemann, Anna and Liiva, Kristjan and Klamma, Ralf},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@proceedings {1569,
	title = {PAID VS. VOLUNTEER WORK IN OPEN SOURCE},
	year = {2014},
	month = {01/2014},
	pages = {3286-3295},
	publisher = {IEEE Computer Society},
	abstract = {Many open source projects have long become commercial. This paper shows just how much of open source software development is paid work and how much has remained volunteer work. Using a conservative approach, we find that about 50\% of all open source software development has been paid work for many years now and that many small projects are fully paid for by companies. However, we also find that any non-trivial project balances the amount of paid developer with volunteer work, and we suggest that the ratio of volunteer to paid work can serve as an indicator for the health of open source projects and aid the management of the respective communities.},
	doi = {10.1109/HICSS.2014.407},
	url = {http://dirkriehle.com/uploads/2013/08/paid-v8-final-web.pdf},
	author = {Dirk Riehle and Riemer, Philipp and Carsten Kolassa and Michael Schmidt}
}
@conference {Kalliamvakou:2014:PPM:2597073.2597074,
	title = {The Promises and Perils of Mining GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {92{\textendash}101},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {With over 10 million git repositories, GitHub is becoming one of the most important source of software artifacts on the Internet. Researchers are starting to mine the information stored in GitHub{\textquoteright}s event logs, trying to understand how its users employ the site to collaborate on software. However, so far there have been no studies describing the quality and properties of the data available from GitHub. We document the results of an empirical study aimed at understanding the characteristics of the repositories in GitHub and how users take advantage of GitHub{\textquoteright}s main features---namely commits, pull requests, and issues. Our results indicate that, while GitHub is a rich source of data on software development, mining GitHub for research purposes should take various potential perils into consideration. We show, for example, that the majority of the projects are personal and inactive; that GitHub is also being used for free storage and as a Web hosting service; and that almost 40\% of all pull requests do not appear as merged, even though they were. We provide a set of recommendations for software engineering researchers on how to approach the data in GitHub.
},
	keywords = {bias, code reviews, git, github, mining software repositories},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597074},
	url = {http://doi.acm.org/10.1145/2597073.2597074},
	attachments = {https://flosshub.org/sites/flosshub.org/files/perils.pdf},
	author = {Kalliamvakou, Eirini and Gousios, Georgios and Blincoe, Kelly and Singer, Leif and Daniel M. German and Damian, Daniela}
}
@conference {Sheoran:2014:UWG:2597073.2597114,
	title = {Understanding "Watchers" on GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {336{\textendash}339},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Users on GitHub can watch repositories to receive notifications about project activity. This introduces a new type of passive project membership. In this paper, we investigate the behavior of watchers and their contribution to the projects they watch. We find that a subset of project watchers begin contributing to the project and those contributors account for a significant percentage of contributors on the project. As contributors, watchers are more confident and contribute over a longer period of time in a more varied way than other contributors. This is likely attributable to the knowledge gained through project notifications.
},
	keywords = {github, mining challenge, msr challenge, repositories, Software Teams, Watchers},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597114},
	url = {http://doi.acm.org/10.1145/2597073.2597114},
	author = {Sheoran, Jyoti and Blincoe, Kelly and Kalliamvakou, Eirini and Damian, Daniela and Ell, Jordan}
}
@inbook {1604,
	title = {Use of Open Software Tools for Data Offloading Techniques Analysis on Mobile Networks},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {111-112},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

This research aims to highlight the benefits of using free software based tools for studying a LTE mobile network with realistic parameters. We will overload this LTE network and offload it through data offloading techniques such as small cells and WiFi offload. For this research, discreteevent open software network simulator ns3 will be implemented. Ns3 is a network simulator based on the programming language C++, and has all the necessary libraries to simulate an LTE and WiFi network.
},
	keywords = {Data Offloading, LTE, ns3, OSS for research and education, small cells, WiFi},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_15},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_15},
	author = {Koo, Jos{\'e}M. and Espino, JuanP. and Armuelles, Iv{\'a}n and Villarreal, Rub{\'e}n},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {hannemann2013adaptive,
	title = {An Adaptive Filter-Framework for the Quality Improvement of Open-Source Software Analysis.},
	booktitle = {Software Engineering},
	year = {2013},
	pages = {143{\textendash}156},
	publisher = {Citeseer},
	organization = {Citeseer},
	abstract = {Knowledge mining in Open-Source Software (OSS) brings a great benefit
for software engineering (SE). The researchers discover, investigate, and even simulate
the organization of development processes within open-source communities in
order to understand the community-oriented organization and to transform its advantages
into conventional SE projects. Despite a great number of different studies on
OSS data, not much attention has been paid to the data filtering step so far. The noise
within uncleaned data can lead to inaccurate conclusions for SE. A special challenge
for data cleaning presents the variety of communicational and development infrastructures
used by OSS projects. This paper presents an adaptive filter-framework supporting
data cleaning and other preprocessing steps. The framework allows to combine
filters in arbitrary order, defining which preprocessing steps should be performed. The
filter-portfolio can by extended easily. A schema matching in case of cross-project
analysis is available. Three filters - spam detection, quotation elimination and core periphery
distinction - were implemented within the filter-framework. In the analysis
of three large-scale OSS projects (BioJava, Biopython, BioPerl), the filtering led to
a significant data modification and reduction. The results of text mining (sentiment
analysis) and social network analysis on uncleaned and cleaned data differ significantly, confirming the importance of the data preprocessing step within OSS empirical
studies.},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.437.5602\&rep=rep1\&type=pdf$\#$page=143},
	author = {Hannemann, Anna and Hackstein, Michael and Klamma, Ralf and Jarke, Matthias}
}
@proceedings {1552,
	title = {Analyzing Social Behavior of Software Developers Across Different Communication Channels},
	year = {2013},
	abstract = {Software developers use different project repositories (i.e., mailing list, bug tracking repositories, discussion forums etc.) to interact with each other or to solve software related problems. The growing interest in the usage of social media channels (i.e., Twitter, Facebook, LinkedIn) have also attracted the open source software community and software developers to adopt an identity in order to disseminate project-related information to a wider audience. Much research has been carried out to analyze the social behavior of software developers in different project repositories but so far no one has tried to study the social communication patterns of developers in other social media channels. We in this paper presents a new dimension to the social aspects of software developers and study if the social communication patterns of software developers is different on project repositories and social media channels (i.e., Twitter).},
	keywords = {communication, developer, social media},
	url = {http://index.ksi.edu/conf/seke/2013/cr/296.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/iqbal_a_et_al_june_2013.pdf},
	author = {Iqbal, Aftab and M Karnstedt and M Hausenblas}
}
@proceedings {1503,
	title = {Apache Commits: Social Network Dataset},
	year = {2013},
	month = {05/2013},
	abstract = {Building non-trivial software is a social endeavor. Therefore, understanding the social network of developers is key to the study of software development organizations. We present a graph representation of the commit behavior of developers within the Apache Software Foundation for 2010 and 2011. Relationships between developers in the network represent collaborative commit behavior. Several similarity and summary metrics have been pre-calculated. The data, along with the tools that were used to create it and some further discussion, can be found at: http://sequoia.cs.byu.edu/lab/?page=artifacts/apacheGraphs},
	author = {MacLean, Alexander C. and Knutson, Charles D.}
}
@book {1536,
	title = {Community Dynamics in Open Source Software Projects: Aging and Social Reshaping},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {80 - 96},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

An undeniable factor for an open source software (OSS) project success is a vital community built around it. An OSS community not only needs to be established, but also to be persisted. This is not guaranteed considering the voluntary nature of participation in OSS. The dynamic analysis of the OSS community evolution can be used to extract indicators to rate the current stability of a community and to predict its future development. Despite the great amount of studies on mining project communication and development repositories, the evolution of OSS communities is rarely addressed. This paper presents an approach to analyze the OSS community history. We combine adapted demography measures to study community aging and social analysis to investigate the dynamics of community structures. The approach is applied to the communication and development history of three bioinformatics OSS communities over eleven years. First, in all three projects a survival rate pattern is identified. This finding allows us to define the minimal number of newcomers required for the further positive community growth. Second, dynamic social analysis shows that the node betweenness in combination with the network diameter can be used as an indicator for significant changes in the community core and the quality of community recovery after these modifications.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_6},
	author = {Hannemann, Anna and Klamma, Ralf},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1502,
	title = {A Dataset from Change History to Support Evaluation  of Software Maintenance Tasks},
	year = {2013},
	month = {05/2013},
	pages = {131-134},
	abstract = {Approaches that support software maintenance need 
to be evaluated and compared against existing ones, in order to 
demonstrate their usefulness in practice. However, oftentimes the 
lack of well-established sets of benchmarks leads to situations 
where these approaches are evaluated using different datasets, 
which results in biased comparisons. In this data paper we 
describe and make publicly available a set of benchmarks from 
six Java applications, which can be used in the evaluation of 
various software engineering (SE) tasks, such as feature location 
and impact analysis. These datasets consist of textual description 
of change requests, the locations in the source code where they 
were implemented, and execution traces. Four of the benchmarks 
were already used in several SE research papers, and two of them 
are new. In addition, we describe in detail the methodology used 
for generating these benchmarks and provide a suite of tools in 
order to encourage other researchers to validate our datasets and 
generate new benchmarks for other subject software systems. 
Our online appendix: http://www.cs.wm.edu/semeru/data/msr13/ },
	url = {http://www.cs.wm.edu/~bdit/publications/MSR13DataPaper_Dit_CRC.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MSR13DataPaper_Dit_CRC.pdf},
	author = {Bogdan Dit and Andrew Holtzhauer and Poshyvanyk, Denys and Kagdi, Huzefa}
}
@book {1546,
	title = {A Dual Model of Open Source License Growth},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	note = {uses ohloh snapshot, march 2008},
	pages = {245 - 256},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Every open source project needs to decide on an open source license. This decision is of high economic relevance: Just which license is the best one to help the project grow and attract a community? The most common question is: Should the project choose a restrictive (reciprocal) license or a more permissive one? As an important step towards answering this question, this paper analyses actual license choice and correlated project growth from ten years of open source projects. It provides closed analytical models and finds that around 2001 a reversal in license choice occurred from restrictive towards permissive licenses.
},
	keywords = {ohloh},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/oss2013.hofmann.pdf},
	author = {Hofmann, Gottfried and Dirk Riehle and Carsten Kolassa and Mauerer, Wolfgang},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1505,
	title = {An Empirical Study of the Fault-Proneness of Clone Mutation and Clone Migration },
	year = {2013},
	month = {05/2013},
	abstract = {When implementing new features into a software system, developers may duplicate several lines of code to reuse some existing code segments. This action creates code clones in the software system. The literature has documented different types of code clone (e.g., Type-1, Type-2, and Type-3). Once created, code clones evolve as they are modified during both the development and maintenance phases of the software system. The evolution of code clones across the revisions of a software system is known as a clone genealogy. Existing work has investigated the fault-proneness of Type-1 and Type-2 clone genealogies. In this study, we investigate clone genealogies containing Type-3 clones. We analyze three long lived software systems APACHE-ANT, ARGOUML, and JBOSS, which are all written in JAVA. Using the NICAD clone detection tool, we build clone genealogies and examine two evolutionary phenomena on clones: the mutation of the type of a clone during the evolution of a system, and the migration of clone segments across the repositories of a software system. Results show that 1) mutation and migration occur frequently in software systems; 2) the mutation of a clone group to Type-2 or Type-3 clones increases the risk for faults; 3) increasing the distance between code segments in a clone group also increases the risk for faults. Index Terms: Types of clones; clone genealogy; clone migration; fault-proneness.},
	author = {Shuai Xie and Foutse Khomh and Ying Zou}
}
@conference {zmzkh-icsm-2013,
	title = {How does Context affect the Distribution of Software Maintainability Metrics?},
	booktitle = {Proceedings of the 29th IEEE International Conference on Software Maintainability},
	series = {ICSM {\textquoteright}13},
	year = {2013},
	note = {"FLOSSMole [25] is another data source, from
where we download descriptions (i.e., application domain)
of SourceForge software systems. Furthermore, we download
latest application domain information4
and monthly download
data5 of studied software systems directly from SourceForge."},
	abstract = {Software metrics have many uses, e.g., defect prediction, effort estimation, and benchmarking an organization against peers and industry standards. In all these cases, metrics may depend on the context, such as the programming language. Here we aim to investigate if the distributions of commonly used metrics do, in fact, vary with six context factors: application domain, programming language, age, lifespan, the number of changes, and the number of downloads. For this preliminary study we select 320 nontrivial software systems from SourceForge. These software systems are randomly sampled from nine popular application domains of SourceForge. We calculate 39 metrics commonly used to assess software maintainability for each software system and use Kruskal Wallis test and Mann-Whitney U test to determine if there are significant differences among the distributions with respect to each of the six context factors. We use Cliff{\textquoteright}s delta to measure the magnitude of the differences and find that all six context factors affect the distribution of 20 metrics and the programming language factor affects 35 metrics. We also briefly discuss how each context factor may affect the distribution of metric values.We expect our results to help software benchmarking and other software engineering methods that rely on these commonly used metrics to be tailored to a particular context.},
	keywords = {benchmark, context, contextual factor, flossmole, large scale, metrics, mining software repositories, sampling, software maintainability, sourceforge, static metrics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icsm2013_contextstudy.pdf},
	author = {Zhang, Feng and Audris Mockus and Ying Zou and Foutse Khomh and Hassan, Ahmed E.}
}
@proceedings {1513,
	title = {Improving Bug Localization using Correlations in Crash Reports},
	year = {2013},
	month = {05/2013},
	abstract = {Nowadays, many software organizations rely on automatic problem reporting tools to collect crash reports directly from users{\textquoteright} environments. These crash reports are later grouped together into crash types. Usually, developers prioritize crash types based on the number of crash reports and file bugs for the top crash types. Because a bug can trigger a crash in different usage scenarios, different crash types are sometimes related to a same bug. Two bugs are correlated when the occurrence of one bug causes the other bug to occur. We refer to a group of crash types related to identical or correlated bugs, as a crash correlation group. In this paper, we propose three rules to identify correlated crash types automatically. We also propose an algorithm to locate and rank buggy files using crash correlation groups. Through an empirical study on Firefox and Eclipse, we show that the three rules can identify crash correlation groups with a precision of 100\% and a recall of 90\% for Firefox and a precision of 79\% and a recall of 65\% for Eclipse. On the top three buggy file candidates, the proposed bug localization algorithm achieves a recall of 62\% and a precision of 42\% for Firefox and a recall of 52\% and a precision of 50\% for Eclipse. On the top 10 buggy file candidates, the recall increases to 92\% for Firefox and 90\% for Eclipse. Developers can combine the proposed crash correlation rules with the new bug localization algorithm to identify and fix correlated crash types all together.},
	keywords = {eclipse, Firefox},
	author = {Shaohua Wang and Foutse Khomh and Ying Zou}
}
@book {1531,
	title = {Is It All Lost? A Study of Inactive Open Source Projects},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification },
	volume = {404},
	year = {2013},
	pages = {61 - 79},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {
Open Source Software (OSS) proponents suggest that when developers lose interest in their project, their last duty is to {\textquotedblleft}hand it off to a competent successor.{\textquotedblright} However, the mechanisms of such a hand-off are not clear, or widely known among OSS developers. As a result, many OSS projects, after a certain long period of evolution, stop evolving, in fact becoming {\textquotedblleft}inactive{\textquotedblright} or {\textquotedblleft}abandoned{\textquotedblright} projects. This paper presents an analysis of the population of projects contained within one of the largest OSS repositories available (SourceForge.net), in order to describe how projects abandoned by their developers can be identified, and to discuss the attributes and characteristics of these inactive projects. In particular, the paper attempts to differentiate projects that experienced maintainability issues from those that are inactive for other reasons, in order to be able to correlate common characteristics to the {\textquotedblleft}failure{\textquotedblright} of these projects.
},
	keywords = {sourceforge},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_5},
	url = {http://staff.lero.ie/stol/files/2013/03/2013-Is-It-All-Lost-A-Study-of-Inactive-Open-Source-Projects.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2013-Is-It-All-Lost-A-Study-of-Inactive-Open-Source-Projects.pdf},
	author = {Khondu, Jymit and Capiluppi, Andrea and Stol, Klaas},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@conference {abdouSEKE2013,
	title = {{Managing Corrective Actions to Closure in Open Source Software Test Process}},
	booktitle = {The 25th International Conference on Software Engineering and Knowledge Engineering (SEKE 2013)},
	year = {2013},
	pages = {306{\textendash}311},
	address = {Boston, USA},
	abstract = {In assessing test process maturity, one of the goals is to manage disciplinary issues. Managing corrective actions to closure is known to aid software quality assurance, in general, and testing process activities, in particular. In this paper, a framework for software testing assessment, namely OSS-TPA, that aims to evaluate corrective actions in OSS test process, is proposed. The OSS-TPA framework is based on earlier studies and relies on a conceptual model for test process activities in OSS development. Using success factors in OSS development, the relationship between the maturity of managing corrective actions and the adoption of OSS is investigated.},
	keywords = {open source software, software engineering, software quality, Software testing, Test Process Improvement.},
	url = {http://index.ksi.edu/conf/seke/2013/cr/282.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/282.pdf},
	author = {Abdou, Tamer and Grogono, Peter and Kamthan, Pankaj}
}
@book {1545,
	title = {Misconceptions and Barriers to Adoption of FOSS in the U.S. Energy Industry},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {232 - 244},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

In this exploratory study, we map the use of free and open source software (FOSS) in the United States energy sector, especially as it relates to cyber security. Through two surveys and a set of semi-structured interviews{\textemdash}targeting both developers and policy makers{\textemdash}we identified key stakeholders, organizations, and FOSS projects, be they rooted in industry, academia, or public policy space that influence software and security practices in the energy sector. We explored FOSS tools, common attitudes and concerns, and challenges with regard to FOSS adoption. More than a dozen themes were identified from interviews and surveys. Of these, drivers for adoption and risks associated with FOSS were the most prevalent. More specifically, the misperceptions of FOSS, the new security challenges presented by the smart grid, and the extensive influence of vendors in this space play the largest roles in FOSS adoption in the energy sector.
},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_17},
	author = {Kuechler, Victor and Jensen, Carlos and Bryant, Deborah},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@article {1566,
	title = {Open Source Community Processes: Implications on Micro and Macro Level},
	journal = {it {\textendash} Information Technology},
	volume = {55},
	number = {5},
	year = {2013},
	pages = {189-194},
	abstract = {In this paper, we will discuss the existence and form of open source community processes, whether they differ between projects, and whether they have any implications on both micro and macro level. We will take a look at how different processes can impact the work and the resulting quality within projects, as well as on macro or project level outcomes like success or efficiency. We will also present as well as validate a research model to explain process adoption and implications.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/itit.2013.1010.pdf},
	author = {Koch, Stefan}
}
@proceedings {1557,
	title = {"Release Early, Release Often"? An Empirical Analysis of Release Strategy in Open Source Software Co-Creation},
	year = {2013},
	abstract = {{\textquotedblleft}Release early, release often{\textquotedblright} is becoming a popular new product introduction strategy in open source software development. We study the influence of release strategies on the download market share of open source projects. Using a panel data set collected from Sourceforge.net, we find that while more frequent releases are associated with better subsequent download market share, the relationship is curvilinear. Too frequent releases could backfire due to the subtle effects on the demand and supply sides of open source software production. From the demand side, we find that releasing frequently may work less effectively in projects with higher adoption costs. From the supply side, fast releases may work less effectively in projects with weak community contributions. Even when the community contributions are strong, the restrictiveness of open source license moderates the effectiveness of releasing early and often. These results have implications for managing open source projects and research on open source software, open innovation, and software adoption.},
	url = {http://aisel.aisnet.org/pacis2013/11},
	attachments = {https://flosshub.org/sites/flosshub.org/files/PACIS2013-002.pdf},
	author = {Chen, Wei and Krishnan, Vish and Zhu, Kevin}
}
@proceedings {1498,
	title = {Who Does What during a Code Review? Datasets of OSS Peer Review Repositories },
	year = {2013},
	month = {05/2013},
	abstract = {We present four datasets that are focused on the general roles of OSS peer review members. With data mined from both an integrated peer review system and code source repositories, our rich datasets comprise of peer review data that was automatically recorded. Using the Android project as a case study, we describe our extraction methodology, the datasets and their application used for three separate studies. Our datasets are available online at http://sdlab.naist.jp/reviewmining/},
	keywords = {android, case study, code review, data set, peer review, roles, source code},
	author = {Kazuki Hamasaki and Raula Gaikovina Kula and Norihiro Yoshida and A. E. Camargo Cruz and Kenji Fujiwara and Hajimu Iida}
}
@proceedings {1443,
	title = {Citizen Engineering: Evolving OSS Practices to Engineering Design and Analysis},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {61-77},
	publisher = {IFIP AICT},
	abstract = {Open Source Software (OSS) development has much in common with concepts such as crowdsourcing, citizen science, collective intelligence, human-based computation, and what we call {\textquotedblleft}Citizen Engineering (CE){\textquotedblright}. We report on several pilot projects that apply these shared principles of OSS development to engineering activities beyond software engineering. CE models harness human computing power from open communities, which commonly consist of a cohort of geographically and/or institutionally scattered citizens - professionals or amateurs - to collaboratively solve real-world problems. In most cases, the problems targeted are challenging to computers, but manageable or trivial to human intelligence. In these systems, while humans play fundamental roles, whether they are project architects or problem solvers, the implementation of CE is greatly facilitated by the advance of information technology, particularly the Internet, considered as "creative mode of user interactivity, not merely a medium between messages and people" [10]. In this paper, we characterize existing citizen engineering practices into 6 major categories, followed by a discussion of 4 ongoing projects, aiming to provide new perspectives and insights for achieving successful CE project designs.},
	author = {Zhai, Zhi and Kijewski-Correa, Tracy and Kareem, Ashan and Hachen, David and Madey, Gregory}
}
@conference {1485,
	title = {A Conceptual Framework for Open Source Software Test Process},
	booktitle = {2012 IEEE 36th IEEE Annual Computer Software and Applications Conference Workshops (COMPSACW)},
	year = {2012},
	pages = {458 - 463},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Izmir, Turkey},
	abstract = {The broad acceptance and use of Open Source Software (OSS) has underscored the necessity of investigating the means of assuring their quality. With the aim of identifying an OSS test process, three well-known OSS projects, namely Apache HTTP server, Mozilla Web browser, and NetBeans IDE were studied. In these studies, three activities were found similar to the activities of the ISO/IEC Test Process Standard. However, major differences were observed in tasks related to each of the test process activities. To systematize the OSS test process, an Open Source Software Test Process Framework (OSS-TPF) is proposed. The alignment of OSS-TPF with the ISO/IEC Test Process Standard is illustrated.},
	isbn = {978-0-7695-4758-9},
	doi = {10.1109/COMPSACW.2012.87},
	url = {http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6341619},
	author = {Abdou, Tamer and Grogono, Peter and Kamthan, Pankaj}
}
@proceedings {1477,
	title = {Future Smart Metering Runs on Open Source {\textendash} Challenges and the GuruxAMI Project},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {389-394},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {More and more devices are coming to Internet and organizations are using more devices to measure things. Challenges include a huge amount of different protocols and a risk of technological lock-in. Because of new innovations and demands new protocols are coming out all the time. Increasing amount of protocols makes it harder to collect data from different data sources and save it to one place. If we want to make tailored reports it is important that we can save all collected data to the one place. This paper presents an overview of how the industrial research project GuruxAMI (Gurux Advanced Metering Infrastructure) tries to solve this problem. An overarching goal of the project is to make an open platform that can be used to collect data from different data sources using different protocols and save collected data to the one place. This will be done by developing Open Source platform that can handle different protocols.},
	author = {Kurunsaari, Mikko}
}
@proceedings {1444,
	title = {Gender Differences in Early Free and Open Source Software Joining Process},
	volume = {378},
	year = {2012},
	note = {"We examined subscriber logs and data for six FOSS projects..."
"We examined the differences between posters and non-posters to determine the attrition rate..."
"Using data from the US Census, we matched names to lists of the most common female and male names. We identified 666 users using this process."},
	month = {09/2012},
	pages = {78-93},
	publisher = {IFIP AICT, Springer},
	address = {Eighth International Conference on Open Source Systems (OSS 2012)},
	abstract = {With the growth of free and open source software (FOSS) and the adoption of FOSS solutions in business and everyday life, it is important that projects serve their growingly diverse user base. The sustainability of FOSS projects relies on a constant influx of new contributors. Several large demo- graphic surveys found that FOSS communities are very homogenous, dominated by young men, similar to the bias existing in the rest of the IT workforce. Building on previous research, we examine mailing list subscriptions and posting statistics of female FOSS participants. New participants often experience their first interaction on a FOSS project{\textquoteright}s mailing list. We explored six FOSS projects {\textendash} Buildroot, Busybox, Jaws, Parrot, uClibc, and Yum. We found a declining rate of female participation from the 8.27\% of subscribers, to 6.63\% of posters, and finally the often reported code contributor rate of 1.5\%. We found a disproportionate attrition rate among women along every step of the FOSS joining process.},
	keywords = {buildroot, busybox, diversity, email, jaws, joining process, mailing lists, parrot, uClibc, Yum},
	author = {Kuechler, Victor and Gilbertson, Claire and Jensen, Carlos}
}
@proceedings {1476,
	title = {How Can Open Standards Be Effectively Implemented in Open Source? Challenges and the ORIOS Project},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {383-388},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Many organisations are currently restricted in their choice of software because of restrictions imposed by existing systems. Challenges include a lack of interoperability and a risk of technological lock-in, which many small companies seek to address by utilising Open Standards and Open Source implementations of such standards when developing and deploying systems. This paper presents an overview of how the industrial research project ORIOS (Open Source software Reference Implementations of Open Standards) seeks to address identified challenges. An overarching goal of the project is to improve understanding within organisations of Open Standards, Open Source Reference Implementations, and the ecosystems around them. This will be done by developing a reference model of necessary and desirable features of an Open Standard, and how Open Standards and their implementations can be utilised by small companies in different usage contexts. An action case study approach will be used as a core strategy for evolving a reference model together with Swedish companies.},
	author = {Lundell, Bj{\"o}rn and AbduraHmanovic, Admir and Andersson, Stefan and Bergström, Erik and Feist, Jonas and Gamalielsson, Jonas and Gustavsson, Tomas and Kahlbom, Roger and Papaxanthis, Konstantin}
}
@article {1879,
	title = {Linux Kernel Development: How Fast it is Going, Who is Doing It, What They are Doing, and Who is Sponsoring It},
	year = {2012},
	month = {03/2012},
	institution = {The Linux Foundation},
	abstract = {The kernel which forms the core of the Linux system is the result of one of the largest cooperative software projects ever attempted. Regular 2-3 month releases deliver stable updates to Linux users, each with signi cant new features, added device support, and improved performance. The rate of change in the kernel is high and increasing, with between 8,000 and 12,000 patches going into each recent kernel release. These releases each contain the work of over 1,000 developers representing nearly 200 corporations.
Since 2005, over 7,800 individual developers from almost 800 different companies have contributed to the kernel. The Linux kernel, thus, has become a common resource developed on a massive scale by companies which are  erce competitors in other areas.
This is the fourth update of this document, which has been published roughly annually since 2008. It covers development through the 3.2 release, with an emphasis on the releases (2.6.36 to 3.2) made since the last update. It has been a busy period, with seven kernel releases created, many signi cant changes made, and continual growth of the kernel developer and user community.
},
	keywords = {corporate, corporations, developers, linux kernel, metrics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lf_kernel_development_2012.pdf},
	author = {Corbet, Jonathan and Greg Kroah-Hartman and Amanda McPherson}
}
@proceedings {1463,
	title = {Open Source, Open Innovation and Intellectual Property Rights {\textendash} A Lightning Talk},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {298-303},
	publisher = {IFIP AICT,  Springer},
	abstract = {Open innovation projects are fast paced aiming at producing a quick proof of concept of an innovative software product. This need for speedy results makes the use of open source components as a basis for the work appealing. Open source brings with it an inherent risk of license conflicts that may become an issue when aiming to develop an innovative demo into an actual product. In this study, the first results of investigating the knowledge the participants of innovation projects have on intellectual property are presented. The effect this may have on the project results is also discussed.},
	author = {Kilamo, Terhi and Hammouda, Imed and Kairamo, Ville and Rasanen, Petri and Saarinen, Jukka P.}
}
@proceedings {1460,
	title = {Open Source Prediction Methods: A Systematic Literature Review},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {280-285},
	publisher = {IFIP AICT,  Springer},
	abstract = {For the adoption of Open Source Software (OSS) components, knowledge of the project development and associated risks with their use is needed. That, in turn, calls for reliable prediction models to support preventive maintenance and building quality software. In this paper, we perform a systematic literature review on the state-of-the- art on predicting OSS projects considering both code and community dimension. We also distill future direction for research in this field.},
	keywords = {Prediction Success, Systematic literature review},
	author = {Syeed, M.M. Mahbubul and Kilamo, Terhi and Hammouda, Imed and Syst{\"a}, Tarja}
}
@conference {1628,
	title = {Software licenses, coverage, and subsumption},
	booktitle = {2012 Fifth International Workshop on Requirements Engineering and Law (RELAW)2012 Fifth IEEE International Workshop on Requirements Engineering and Law (RELAW)},
	year = {2012},
	pages = {17 - 24},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Chicago, IL, USA},
	abstract = {Software licensing issues for a system design, instantiation, or configuration are often complex and difficult to evaluate, and mistakes can be costly. Automated assistance requires a formal representation of the significant features of the software licenses involved. We present results from an analysis directed toward a formal representation capable of covering an entire license. The key to such a representation is to identify the license{\textquoteright}s actions, and relate them to the actions for exclusive rights defined in law and to the actions defined in other licenses. Parameterizing each action by the object(s) acted on, the instrumental entities through which the action is performed, and similar contextual variables enables a subsumption relation among the actions. The resulting formalism is lightweight, flexible enough to support the scope of legal interpretations, and extensible to a wide range of software licenses. We discuss the application of our approach to the Lesser General Public License (LGPL) version 2.1.},
	isbn = {978-1-4673-4381-7},
	doi = {10.1109/RELAW.2012.6347800},
	author = {Alspaugh, Thomas A. and Walt Scacchi and Kawai, Rihoko}
}
@proceedings {1442,
	title = {Step-by-Step Strategies and Case Studies for Embedded Software Companies to Adapt to the FOSS Ecosystem},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {48-60},
	abstract = {Due to the continuous expansion of the FOSS ecosystem and the introduction of high-quality FOSS, FOSS is increasingly used in consumer electronics (CE) such as smartphones, televisions, and cameras. As a result, manufacturers of CE products have developed a close relationship with the FOSS ecosystem. For CE product manufacturers, efficient adaptation to the FOSS ecosystem has become an essential component in their business operations. This paper will divide the activities of CE product manufacturers within the FOSS ecosystem into the following four levels: identification, adoption, compliance, and contribution. It will examine the main activities and obstacles that arise in each level. The paper will also present instances where companies have succeeded in overcoming these obstacles.},
	keywords = {embedded software, FOSS ecosystem},
	author = {Kim, Suhyun and Yoo, Jaehyun and Lee, Myunghwa}
}
@proceedings {1288,
	title = {An Analysis of Author Contribution Patterns in Eclipse Foundation Project Source Code},
	year = {2011},
	note = {"We conducted an observational study on existing Eclipse projects by extracting author attribution data for Java source code files from git repositories."

"Specifically, we consider entropy of source code by counting the number of lines attributed to each author."},
	month = {10/2011},
	pages = {269-281},
	publisher = {Springer},
	abstract = {Collaborative development is a key tenet of open source software, but if not properly understood and managed, it can become a liability. We examine author contribution data for the newest revision of 251,633 Java source files in 592 Eclipse projects. We use this observational data to analyze collaboration patterns within files, and to explore relationships between file size, author count, and code authorship. We calculate author entropy to characterize the contributions of multiple authors to a given file, with an eye toward understanding the degree of collaboration and the most common interaction patterns.},
	keywords = {COLLABORATION, contribution, eclipse, entropy, java},
	author = {Taylor, Quinn C. and Krein, Jonathan L. and MacLean, Alexander C. and Knutson, Charles D.}
}
@proceedings {1291,
	title = {Applying Open Source Practices and Principles in Open Innovation: The Case of the Demola Platform},
	year = {2011},
	month = {10/2011},
	pages = {307-311},
	publisher = {Springer},
	abstract = {In numerous fields, businesses have to rely on rapid development and release cycles. Variant new ideas and concepts can emerge through open innovation as the participants are not limited to the company scope. This makes open innovation an increasingly appealing option for the industry. One such open innovation platform, Demola, allows university students to work on real life industrial cases of their own interest. We have identified similarities with its way of operation to open source software development and find that it offers a viable motivational, organizational and collaborative solution to open innovation.},
	author = {Kilamo, Terhi and Hammouda, Imed and Kairamo, Ville and Rasanen, Petri}
}
@proceedings {1289,
	title = {Cliff Walls: An Analysis of Monolithic Commits Using Latent Dirichlet Allocation},
	year = {2011},
	note = {"Our data set consists of the version control logs of almost 10,000 projects from SourceForge, acquired in late 2006"},
	month = {10/2011},
	pages = {282-298},
	publisher = {Springer},
	abstract = {Artifact-based research provides a mechanism whereby researchers may study the creation of software yet avoid many of the difficulties of direct observation and experimentation. However, there are still many challenges that can affect the quality of artifact-based studies, especially those studies examining software evolution. Large commits, which we refer to as {\textquotedblleft}Cliff Walls,{\textquotedblright} are one significant threat to studies of software evolution because they do not appear to represent incremental development. We used Latent Dirichlet Allocation to extract topics from over 2 million commit log messages, taken from 10,000 SourceForge projects. The topics generated through this method were then analyzed to determine the causes of over 9,000 of the largest commits. We found that branch merges, code imports, and auto-generated documentation were significant causes of large commits. We also found that corrective maintenance tasks, such as bug fixes, did not play a significant role in the creation of large commits.},
	keywords = {artifacts, commit, cvs, LDA, lines of code, log files, scm, sloc, sourceforge, version control},
	author = {Pratt, Landon J. and MacLean, Alexander C. and Knutson, Charles D. and Ringger, Eric K.}
}
@proceedings {1273,
	title = {Developing Architectural Documentation for the Hadoop Distributed File System},
	year = {2011},
	month = {10/2011},
	pages = {50-61},
	publisher = {Springer},
	abstract = {Many open source projects are lacking architectural documentation that describes the major pieces of the system, how they are structured, and how they interact. We have produced architectural documentation for the Hadoop Distributed File System (HDFS), a major open source project. This paper describes our process and experiences in developing this documentation. We illustrate the documentation we have produced and how it differs from existing documentation by describing the redundancy mechanisms used in HDFS for reliability.},
	author = {Bass, Len and Kazman, Rick and Ozkaya, Ipek}
}
@proceedings {1272,
	title = {Ginga-J: An Open Java-Based Application Environment for Interactive Digital Television Services},
	year = {2011},
	month = {10/2011},
	pages = {34-49},
	publisher = {Springer},
	abstract = {This paper aims to present a Ginga-J{\textquoteright}s reference implementation. Although based on a particular platform, the implementation not only works as a proof of concept, but also raised several issues and difficulties on the software architecture project that should be taken into account to ease extensibility and porting to other platforms. Ginga is the standard middleware for the Brazilian DTV System. Its imperative environment (Ginga-J) is based on new JavaDTV specification and mandatory for fixed terrestrial receptors.},
	author = {Kulesza, Raoni and Lima, Jefferson F.A. and Guedes, Alan L. and Junior, Lucenildo L.A. and Meira, Silvio R.L. and Filho, Guido L.S.}
}
@conference {1481,
	title = {Joining Free/Open Source Software Communities: An Analysis of Newbies{\textquoteright} First Interactions on Project Mailing Lists},
	booktitle = {2011 44th Hawaii International Conference on System Sciences (HICSS 2011)},
	year = {2011},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Kauai, HI},
	abstract = {Free/Open source software (FOSS) is an important part of the IT ecosystem. Due to the voluntary nature of participation, continual recruitment is key to the growth and sustainability of these communities. It is therefore important to understand how and why potential contributors fail in the process of transitioning from user to contributor. Most newcomers, or "newbies", have their first interaction with a community through a mailing list. To understand how this first contact influences future interactions, we studied eight mailing lists across four FOSS projects: MediaWiki, GIMP, PostgreSQL, and Subversion. We analyzed discussions initiated by newbies to determine the effect of gender, nationality, politeness, helpfulness and timeliness of response. We found that nearly 80\% of newbie posts received replies, and that receiving timely responses, especially within 48 hours, was positively correlated with future participation. We also found that while the majority of interactions were positive, 1.5\% of responses were rude or hostile.},
	keywords = {email, email archive, gimp, mailing list, mediawiki, postgresql, subversion},
	isbn = {978-1-4244-9618-1},
	doi = {10.1109/HICSS.2011.264},
	author = {Jensen, Carlos and King, Scott and Kuechler, Victor}
}
@proceedings {1277,
	title = {Knowledge Homogeneity and Specialization in the Apache HTTP Server Project},
	year = {2011},
	note = {"Our data set consists of the commit history and email archives for the Apache HTTP Server Project, spanning sixteen years (2/27/1995 - 1/31/2011)"

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

"If specialization exists within the httpd community, we should see distinct communities develop around topics. In addition, unique groups of developers should congregate around specialized subtopics. We examined the data from both angles: topical affinity and topic communities."
},
	month = {10/2011},
	pages = {106-122},
	publisher = {Springer},
	abstract = {We present an analysis of developer communication in the Apache HTTP Server project. Using topic modeling techniques we expose latent conceptual sub-communities arising from developer specialization within the greater developer population. However, we found that among the major contributors to the project, very little specialization exists. We present theories to explain this phenomenon, and suggest further research.},
	keywords = {apache, commits, developer, email, email archive, LDA, mailing list, revision control, revision history, scm, social network analysis, specialization, subversion, svn},
	url = {http://sequoia.cs.byu.edu/lab/files/pubs/MacLean2011a.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MacLean2011a.pdf},
	author = {MacLean, Alexander C. and Pratt, Landon J. and Knutson, Charles D. and Ringger, Eric K.}
}
@proceedings {1292,
	title = {KommGame: A Reputation Environment for Teaching Open Source Software},
	year = {2011},
	month = {10/2011},
	pages = {312-315},
	publisher = {Springer},
	abstract = {The importance of teaching open source software in universities is increasing with the advent of open source as a development and business model. A novel, student centric approach of teaching open source was tried out at Tampere University of Technology where a new environment called KommGame was introduced to assist in teaching open source development. This environment includes a reputation system to motivate learners to participate. In this paper, we present our approach of teaching open source and how the KommGame environment was employed to teach open source software.},
	author = {Goduguluri, Veerakishore and Kilamo, Terhi and Hammouda, Imed}
}
@conference {1520,
	title = {A Secondary Data Archive for Code-Level Debian Metrics},
	booktitle = {2011 Second International Workshop on Replication in Empirical Software Engineering Research (RESER)},
	year = {2011},
	month = {09/2011},
	pages = {43 - 51},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Banff, Alberta, Canada},
	abstract = {In this paper, we describe a new process to collect, calculate, archive, and distribute interesting metrics for all the packages in the standard Debian GNU/Linux installation. Our method replicates and extends previous work done by other groups studying free and open source software systems (FLOSS) in three important ways. First, although there have been other previous studies that attempted to collect a large set of code-level metrics for a small set of projects, and there have been studies that generated a small set of metrics for the large Debian codebase, our project does both: we generate a larger set of metrics for the entire set of Debian packages. Second, our integration of new Debian metadata and additional code-level metrics not gathered before adds several additional layers for exploration. Finally, and most importantly, because we integrate our collection and analysis process into the automated FLOSSmole data store, we ensure timely, repeatable, and very easy comparison, replication and analysis by other groups. Thus our collection activity will continue in an automated fashion even after this paper is published, providing the foundation for additional studies to be conducted later, all freely accessible to any interested research group. After outlining our process, we discuss a few observations about the data, we outline some implications for the research community, and we present opportunities for further research.},
	isbn = {978-1-4673-0972-1},
	doi = {10.1109/RESER.2011.9},
	author = {Kozak, Carter and Squire, Megan}
}
@conference {1303,
	title = {A study of language usage evolution in open source software},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {13-22},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Waikiki, Honolulu, HI, USA},
	abstract = {The use of programming languages such as Java and C in Open Source Software (OSS) has been well studied. However, many other popular languages such as XSL or XML have received minor attention. In this paper, we discuss some trends in OSS development that we observed when considering multiple programming language evolution of OSS. Based on the revision data of 22 OSS projects, we tracked the evolution of language usage and other artefacts such as documentation files, binaries and graphics files. In these systems several different languages and artefact types including C/C++, Java, XML, XSL, Makefile, Groovy, HTML, Shell scripts, CSS, Graphics files, JavaScript, JSP, Ruby, Phyton, XQuery, OpenDocument files, PHP, etc. have been used. We found that the amount of code written in different languages differs substantially. Some of our findings can be summarized as follows: (1) JavaScript and CSS files most often co-evolve with XSL; (2) Most Java developers but only every second C/C++ developer work with XML; (3) and more generally, we observed a significant increase of usage of XML and XSL during recent years and found that Java or C are hardly ever the only language used by a developer. In fact, a developer works with more than 5 different artefact types (or 4 different languages) in a project on average.},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985447},
	author = {Gall, Harald and Karus, Siim}
}
@conference {958,
	title = {Cloning and copying between GNOME projects},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {98 - 101},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {This paper presents an approach to automatically distinguish the copied clone from the original in a pair of clones. It matches the line-by-line version information of a clone to the pair{\textquoteright}s other clone. A case study on the GNOME Desktop Suite revealed a complex flow of reused code between the different subprojects. In particular, it showed that the majority of larger clones (with a minimal size of 28 lines or higher) exist between the subprojects and more than 60\% of the clone pairs can be automatically separated into original and copy.},
	keywords = {clone, gnome, msr challenge, source code},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463290},
	attachments = {https://flosshub.org/sites/flosshub.org/files/98Coning.pdf},
	author = {Krinke, Jens and Gold, Nicolas and Jia, Yue and Binkley, David}
}
@article {1240,
	title = {Impact of Programming Language Fragmentation on Developer Productivity},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	month = {32/2010},
	pages = {41 - 61},
	abstract = {Programmers often develop software in multiple languages. In an effort to study the effects of programming language fragmentation on productivity{\textemdash}and ultimately on a developer{\textquoteright}s problem-solving abilities{\textemdash}the authors present a metric, language entropy, for characterizing the distribution of a developer{\textquoteright}s programming efforts across multiple programming languages. This paper presents an observational study examining the project contributions of a random sample of 500 SourceForge developers. Using a random coefficients model, the authors find a statistically (alpha level of 0.001) and practically significant correlation between language entropy and the size of monthly project contributions. Results indicate that programming language fragmentation is negatively related to the total amount of code contributed by developers within SourceForge, an open source software (OSS) community.},
	keywords = {commits, entropy, language entropy, programming languages, sourceforge, srda},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010040104},
	author = {Krein, Jonathan L. and MacLean, Alexander C. and Knutson, Charles D. and Delorey, Daniel P. and Eggett, Dennis L.}
}
@conference {1359,
	title = {Linking e-mails and source code artifacts},
	booktitle = {Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - ICSE {\textquoteright}10},
	volume = {1},
	year = {2010},
	note = {"we devised a set of lightweight methods, based on regular expressions, to establish the link between e-mails and software artifacts. We evaluated them in terms of precision and recall considering one single Java system. In this paper we overcome a number of limitations of our previous work, resulting in the following contributions:
{\textbullet} An extensive and publicly available1 benchmark and toolset for recovering traceability links between e-mails and source code artifacts. We created our benchmark by analyzing the mailing lists of six different software systems written in four different programming languages. For each system we manually annotated a statistically significant number of e-mails.
{\textbullet} A comprehensive evaluation of linking techniques. We evaluated and compared, in terms of precision and recall, different linking methods, ranging from lightweight grep-style approaches to more complex approa- ches from the information retrieval (IR) field."},
	month = {05/2010},
	pages = {375-384},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Cape Town, South Africa},
	abstract = {E-mails concerning the development issues of a system constitute an important source of information about high-level design decisions, low-level implementation concerns, and the social structure of developers.

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

In this article we present such a benchmark, which we created through the manual inspection of a statistically significant number of e-mails pertaining to six unrelated software systems. We then use our benchmark to measure the effectiveness of a number of approaches, ranging from lightweight approaches based on regular expressions to full-fledged information retrieval approaches.},
	isbn = {9781605587196},
	doi = {10.1145/1806799.1806855},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	author = {Bacchelli, Alberto and Lanza, Michele and Robbes, Romain}
}
@article {1337,
	title = {Open Scientific Entrepreneurship},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {48 - 66},
	abstract = {The objective of this article is to conceptually transfer the concept of open source software (OSS) development to scientific entrepreneurship and to hypothetically discuss the support potentials of this rather new development philosophy for what we than call open scientific entrepreneurship. Therefore, at first the authors will go into conceptual details of scientific entrepreneurship and than of OSS development. Following, the main thrust of the article presents open scientific entrepreneurship from two points of origin: first of all, OSS development as a specific form of scientific e-entrepreneurship and further on potential benefits of opening {\textquotedblleft}traditional{\textquotedblright} scientific entrepreneurship up by looking at specific action fields. These action fields are theoretically based on the process and competence perspective of scientific entrepreneurship. Finally, the general benefits as well as downsides of the concept of openness are discussed on a generic level. It becomes obvious that there is need for balancing the tensions between an open and closed design pattern for scientific entrepreneurship with a general emphasis on the open design perspective.},
	issn = {1942-3934},
	doi = {10.4018/IJOSSP.2010100104},
	author = {von Kortzfleisch, Harald and Schaarschmidt, Mario and Magin, Philipp}
}
@article {1333,
	title = {Open Source Adoption Index},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {48 - 60},
	abstract = {This paper reports the preliminary results of a study conducted to assess and quantify the adoption of Free/Open Source Software (FOSS) by organisations and enterprises. While almost all organisations use FOSS in some form today, there is a wide variation in the manner and extent to which they do so, and presently no quantitative measure exists that can capture the true picture. The present work has built a model with two sets of parameters that, when fed with relevant data about an organisation, generates a single number, the FOSS Adoption Index (FAI), for that organisation. The index is so defined that the higher its value for an organisation, the greater is the extent of FOSS adoption in that organisation. Beyond the single measure FAI that gives a coarse assessment, the model also allows drilling down to finer levels of granularity that provides deeper insights into the status and role of FOSS within a given organisation. Primary data collected for two classes of organisations through questionnaire based surveys and interviews have been used to demonstrate the working of the model as well as its potential usefulness for real world situations.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010070103},
	author = {Saini, Sanjeev K. and Krishnan, C. N. and Rajaram, L. N.}
}
@conference {Meirelles:2010:SRS:1915078.1916012,
	title = {A Study of the Relationships between Source Code Metrics and Attractiveness in Free Software Projects},
	booktitle = {Proceedings of the 2010 Brazilian Symposium on Software Engineering},
	series = {SBES {\textquoteright}10},
	year = {2010},
	pages = {11{\textendash}20},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {A significant number of Free Software projects has been widely used and considered successful. However, there is an even larger number of them that cannot overcome the initial steps towards building an active community of users and developers. In this study, we investigated whether there are relationships between source code metrics and attractiveness, i.e., the ability of a project to attract users and developers. To verify these relationships, we analyzed 6,773 Free Software projects from the SourceForge.net repository. The results indicated that attractiveness is indeed correlated to some source code metrics. This suggests that measurable attributes of the project source code somehow affect the decision to contribute to and adopt a Free Software. The findings described in this paper show that it is relevant for project leaders to monitor source code quality, particularly a few objective metrics, since these can have a positive influence in projects chances of forming a community of contributors and users around their software, enabling further enhancement in quality.},
	keywords = {source code, source code analysis, sourceforge, user satisfaction, users},
	isbn = {978-0-7695-4273-7},
	doi = {10.1109/SBES.2010.27},
	url = {http://dx.doi.org/10.1109/SBES.2010.27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/sourcecode_attractiveness.pdf},
	author = {Meirelles, Paulo and Santos Jr., Carlos and Miranda, Joao and Kon, Fabio and Terceiro, Antonio and Chavez, Christina}
}
@conference {1217,
	title = {Trends That Affect Temporal Analysis Using SourceForge Data},
	booktitle = {5th Workshop on Public Data about Software Development (WoPDaSD 2010)},
	year = {2010},
	note = {"In this paper we examine some of the limitations of artifact data by specifically addressing the applicability of SourceForge data to the study of project evolution."

"For our analysis we examine 9,997 Production/Stable or Maintenance phase projects stored in CVS on SourceForge and extracted in October of 2006 [5]"},
	abstract = {SourceForge is a valuable source of software artifact data for researchers who study project evolution and developer behavior. However, the data exhibit patterns that may bias temporal analyses. Most notable are cliff walls in project source code repository timelines, which indicate large commits that are out of character for the given project. These cliff walls often hide significant periods of development and developer collaboration{\textemdash}a threat to studies that rely on SourceForge repository data. We demonstrate how to identify these cliff walls, discuss reasons for their appearance, and propose preliminary measures for mitigating their effects in evolution-oriented studies.},
	keywords = {cliff walls, committers, cvs, evolution, growth, source code, sourceforge, time, time series},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd001.pdf},
	author = {MacLean, Alexander C. and Pratt, Landon J. and Krein, Jonathan L. and Knutson, Charles D.}
}
@conference {1829,
	title = {Validity concerns in software engineering research},
	booktitle = {Proceedings of the FSE/SDP workshop on Future of software engineering research - FoSER {\textquoteright}10},
	year = {2010},
	note = {"Obtaining a balanced set of data from
open source repositories has been an issue in the open source
research community for some time, and several collections
of data have grown to attempt to solve this problem [11, 13,
20]."},
	pages = {411},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Santa Fe, New Mexico, USANew York, New York, USA},
	abstract = {Empirical studies that use software repository artifacts have become popular in the last decade due to the ready availability of open source project archives. In this paper, we survey empirical studies in the last three years of ICSE and FSE proceedings, and categorize these studies in terms of open source projects vs. proprietary source projects and the diversity of subject programs used in these studies. Our survey has shown that almost half (49\%) of recent empirical studies used solely open source projects. Existing studies either draw general conclusions from these results or explicitly disclaim any conclusions that can extend beyond specific subject software. We conclude that researchers in empirical software engineering must consider the external validity concerns that arise from using only several well-known open source software projects, and that discussion of data source selection is an important discussion topic in software engineering research. Furthermore, we propose a community research infrastructure for software repository benchmarks and sharing the empirical analysis results, in order to address external validity concerns and to raise the bar for empirical software engineering research that analyzes software artifacts. },
	keywords = {flossmole cited},
	isbn = {9781450304276},
	doi = {10.1145/1882362.1882446},
	author = {Wright, Hyrum K. and Kim, Miryung}
}
@conference {937,
	title = {Assigning bug reports using a vocabulary-based expertise model of developers},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {131 - 140},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {For popular software systems, the number of daily submitted bug reports is high. Triaging these incoming reports is a time consuming task. Part of the bug triage is the assignment of a report to a developer with the appropriate expertise. In this paper, we present an approach to automatically suggest developers who have the appropriate expertise for handling a bug report. We model developer expertise using the vocabulary found in their source code contributions and compare this vocabulary to the vocabulary of bug reports. We evaluate our approach by comparing the suggested experts to the persons who eventually worked on the bug. Using eight years of Eclipse development as a case study, we achieve 33.6\% top-1 precision and 71.0\% top-10 recall.},
	keywords = {bug reports, bugzilla, develect, developers, eclipse, expertise, scm},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069491},
	attachments = {https://flosshub.org/sites/flosshub.org/files/131AssigningBugReports.pdf},
	author = {Matter, Dominique and Kuhn, Adrian and Nierstrasz, Oscar}
}
@conference {930,
	title = {Author entropy vs. file size in the GNOME suite of applications},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {91 - 94},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {We present the results of a study in which author entropy was used to characterize author contributions per file. Our analysis reveals three patterns: banding in the data, uneven distribution of data across bands, and file size dependent distributions within bands. Our results suggest that when two authors contribute to a file, large files are more likely to have a dominant author than smaller files.},
	keywords = {author entropy, contributions, gnome, msr challenge},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069484},
	author = {Casebolt, Jason R. and Krein, Jonathan L. and MacLean, Alexander C. and Knutson, Charles D. and Delorey, Daniel P.}
}
@conference {943,
	title = {Automatic labeling of software components and their evolution using log-likelihood ratio of word frequencies in source code},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {175 - 178},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {As more and more open-source software components become available on the Internet we need automatic ways to label and compare them. For example, a developer who searches for reusable software must be able to quickly gain an understanding of retrieved components. This understanding cannot be gained at the level of source code due to the semantic gap between source code and the domain model. In this paper we present a lexical approach that uses the log-likelihood ratios of word frequencies to automatically provide labels for software components. We present a prototype implementation of our labeling/comparison algorithm and provide examples of its application. In particular, we apply the approach to detect trends in the evolution of a software system.},
	keywords = {frequency, hapax, information retrieval, java, junit, keywords, labeling, source code},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069499},
	attachments = {https://flosshub.org/sites/flosshub.org/files/175AutomaticLabeling.pdf},
	author = {Kuhn, Adrian}
}
@conference {581,
	title = {Customization of Open Source Software in Companies},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {129 - 142},
	publisher = {Springer},
	organization = {Springer},
	chapter = {13},
	abstract = {Most papers related to Open Source Software (OSS) discuss the development of OSS, licensing issues, and motivations of developers. Research in the area of customization of OSS is rare, however. The process after the deployment of an OSS within a company remains unknown. There is a danger that it is often unstructured and error-prone since OSS develops in a more complex way than proprietary software. Based on our literature study, modifications of open source code do occur also in organizations outside of the software industry. Customization of applications is more common than customization of infrastructure software in these organizations. Therefore, we examine the process of deployment and adaptation of an OSS application software over several update iterations in great detail. This examination shows that this process has similarities with the process of deployment of proprietary software but it also exhibits important differences. Based on this case study, we also suggest a process model for customization of OSS applications in user organizations.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_13},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Customization\%20of\%20Open\%20Source\%20Software.pdf},
	author = {Ke{\ss}ler, Steffen and Alpar, Paul}
}
@conference {856,
	title = {Facts or Friends? Distinguishing Informational and Conversational Questions in Social QnA Sites (forthcoming)},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2009},
	author = {Harper, F. Maxwell and Moy, D. and Konstan, J.A.}
}
@conference {844,
	title = {A Jury of Your Peers: Quality, Experience and Ownership in Wikipedia},
	booktitle = {The International Symposium on Wiki{\textquoteright}s and Open Collaboration},
	year = {2009},
	month = {10/2009},
	address = {Orlando, FL},
	keywords = {experience,, ownership,, peer, peer,, quality, review,, wikipedia,, wikiwork,},
	author = {Halfaker, A. and Kittur, N. and Kraut, R. and Riedl, J.}
}
@conference {1204,
	title = {Language entropy: A metric for characterization of author programming language distribution},
	booktitle = {4th Workshop on Public Data about Software Development (WoPDaSD 2009)},
	year = {2009},
	note = {The data set used in this study was previously collected for a separate, but related work. It was originally extracted from the SourceForge Research Archive (SFRA), August 2006. For a detailed discussion of the data source, collection tools and processes, and summary statistics, see [6]."

"From the initial data set we extracted a random sample of 500 developers3 along with descriptive details of all revisions that those developers made since the inception of the projects on which they worked. We then condensed this sample by totaling the lines of code added by each developer for each month in which that developer made at least one code submission."
[6] Daniel P. Delorey, Charles D. Knutson, and Alex MacLean. Studying production phase sourceforge projects: A case study using cvs2mysql and sfra+. In Second International Workshop on Public Data about Software Development (WoPDaSD {\textquoteright}07), June 2007.},
	month = {2009},
	abstract = {Programmers are often required to develop in multiple languages. In an effort to study the effects of programming language fragmentation on productivity{\textemdash}and ultimately on a programmer{\textquoteright}s problem solving abilities{\textemdash}we propose a metric, language entropy, for characterizing the distribution of an individual{\textquoteright}s development efforts across multiple programming languages. To evaluate this metric, we present an observational study examining all project contributions (through August 2006) of a random sample of 500 SourceForge developers. Using a random coefficients model, we found a statistically significant correlation (alpha level of 0.05) between language entropy and the size of monthly pro ject contributions (measured in lines of code added). Our results indicate that language entropy is a good candidate for characterizing author programing language distribution.},
	keywords = {contributions, developers, language entropy, lines of code, loc, multiple languages, programming languages, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LanguageEntropy-JonathanKrein.pdf},
	author = {Krein, Jonathan L. and MacLean, Alexander C. and Delorey, Daniel P. and Knutson, Charles D. and Eggett, Dennis L.}
}
@proceedings {1645,
	title = {Mining Programming Language Vocabularies from Source Code},
	year = {2009},
	pages = {12 pp},
	abstract = {We can learn much from the artifacts produced as the by-products of software devel- opment and stored in software repositories. Of all such potential data sources, one of the most important from the perspective of program comprehension is the source code itself. While other data sources give insight into what developers intend a program to do, the source code is the most accurate human-accessible description of what it will do. However, the ability of an individual developer to comprehend a particular source file depends directly on his or her familiarity with the specific features of the programming language being used in the file. This is not unlike the difficulties second-language learners may encounter when attempting to read a text written in a new language. We propose that by applying the techniques used by corpus linguists in the study of natural language texts to a corpus of programming language texts (i.e., source code repositories), we can gain new insights into the communication medium that is programming language. In this paper we lay the foundation for applying corpus linguistic methods to programming language by 1) defining the term {\textquotedblleft}word{\textquotedblright} for programming language, 2) developing data collection tools and a data storage schema for the Java programming language, and 3) presenting an initial analysis of an example linguistic corpus based on version 1.5 of the Java Developers Kit.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/21st-delorey.pdf},
	author = {Delorey, Daniel P. and Knutson, Charles D. and Davies, Mark}
}
@article {1118,
	title = {Monetary donations to an open source software platform},
	journal = {Research Policy},
	volume = {38},
	year = {2009},
	month = {03/2009},
	pages = {404 - 414},
	abstract = {Online open source software platforms, such as Sourceforge.net, play a vital role in creating an ecosystem that enables the creation and growth of open source projects. However, there is little research exploring the interactions between open source stakeholders and the platform. We believe that the sustainability of the platform crucially depends on financial incentives. While platforms can obtain these incentives through multiple means, in this paper we focus on one form of financial incentives{\textemdash}voluntary monetary donations by open source community members. We report findings from two empirical studies that examine factors that impact donations. Study 1 investigates the factors that cause some community members to donate and not others. We find that the decision to donate is impacted by relational commitment with open source software platform, donation to projects and accepting donations from others. Study 2 examines what drives the level of donation. We find that the length of association with the platform and relational commitment affects donation levels.},
	keywords = {Collective action, Donation, Identification, incentives, metadata, MOTIVATION, Open source software platform, projects, Reciprocity, Relational commitment, sourceforge},
	issn = {00487333},
	doi = {10.1016/j.respol.2008.11.004},
	author = {Sandeep Krishnamurthy and Tripathi, Arvind K.}
}
@booklet {859,
	title = {Perceptions and Practices of Usability in the Free/Open Source Software (FOSS) Community},
	number = {CS-2009-26},
	year = {2009},
	publisher = {David R. Cheriton School of Computer Science, University of Waterloo},
	author = {Terry, M. and Kay, M. and Lafreniere, B.}
}
@conference {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 {573,
	title = {Software Engineering in Practice: Design and Architectures of FLOSS Systems},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {34 - 46},
	publisher = {Springer},
	organization = {Springer},
	chapter = {5},
	abstract = {Free/Libre/Open Source Software (FLOSS) practitioners and developers are typically also users of their own systems: as a result, traditional software engineering (SE) processes (e.g., the requirements and design phases), take less time to articulate and negotiate among FLOSS developers. Design and requirements are kept more as informal knowledge, rather than formally described and assessed. This paper attempts to recover the SE concepts of software design and architectures from three FLOSS case studies, sharing the same application domain (i.e., Instant Messaging). Its first objective is to determine whether a common architecture emerges from the three systems, which can be used as shared knowledge for future applications. The second objective is to determine whether these architectures evolve or decay during the evolution of these systems. The results of this study are encouraging: albeit no explicit effort was done by FLOSS developers to define a high-level view of the architecture, a common shared architecture could be distilled for the Instant Messaging application domain. It was also found that, for two of the three systems, the architecture becomes better organised, and the components better specified, as long as the system evolves in time.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Software\%20Engineering\%20in\%20Practice.pdf},
	author = {Capiluppi, Andrea and Knowles, Thomas}
}
@conference {598,
	title = {Undergraduate Research Opportunities in OSS},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {340 - 350},
	publisher = {Springer},
	organization = {Springer},
	chapter = {30},
	abstract = {Using Open Source Software (OSS) in undergraduate teaching in universities is now commonplace. Students use OSS applications and systems in their courses on programming, operating systems, DBMS, web development to name but a few. Studying OSS projects from both a product and a process view also forms part of the software engineering curriculum at various universities. Many students have taken part in OSS projects as well as developers. At the University of Lincoln, under the Undergraduate Research Opportunities Scheme (UROS), undergraduate student researchers have the chance to work over the summer embedded within an existing research centre on a UROS project. Here two such projects within the Centre for Research in Open Source Software (CROSS) are described: Collaborative Development for the XO Laptop (CODEX) and Software Modularity in Open Source Software (SoMOSS). The CODEX project focused on creating resources to support students undertaking software application development for the XO laptop, and the SoMOSS project focused on architectural studies of OSS instant messaging software. Both projects achieved successful research outcomes; more importantly, both student researchers benefited directly from the encouragement and concrete assistance that they received through interaction with the wider OSS research community. Both projects are ongoing and present further research opportunities for students.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_30},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Undergraduate\%20Research\%20Opportunities.pdf},
	author = {Boldyreff, Cornelia and Capiluppi, Andrea and Knowles, Thomas and Munro, James}
}
@conference {534,
	title = {Analysis of Coordination Between Developers and Users in the Apache Community},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {81 - 92},
	publisher = {Springer},
	organization = {Springer},
	chapter = {7},
	abstract = {Coordination is one of the keys for the success of open source software (OSS) communities because geographically distributed members need to collaborate on their work using communication tools (e.g., mailing lists, bulletin board systems, bug tracking systems, and so on). In this paper, we investigated the informal social structure among developers and users by analyzing two mailing lists of developers and users in the Apache community based on betweenness centrality, one centrality measure proposed by Freeman. From the analysis results, we found that (1) participants with high betweenness coordinated activities between developers and users and (2) some participants have been functioning as coordinators in the community for a long time.
},
	keywords = {apache, email, mailing list},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Analysis\%20of\%20Coordination.pdf},
	author = {Kamei, Yasutaka and Matsumoto, Shinsuke and Maeshima, Hirotaka and Onishi, Yoji and Ohira, Masao and Matsumoto, Ken-ichi}
}
@conference {1210,
	title = {Author Entropy: A Metric for Characterization  of Software Authorship Patterns},
	booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)},
	year = {2008},
	note = {used flossmole to get sample of SF developers},
	month = {2008},
	pages = {42-47},
	abstract = {We propose the concept of author entropy and describe how file-level entropy measures may be used to understand and characterize authorship patterns within individual files, as well as across an entire project. As a proof of concept, we compute author entropy for 28,955 files from 33 open-source projects. We explore patterns of author entropy, identify techniques for visualizing author entropy, and propose avenues for further study. },
	keywords = {developers, entropy, flossmole, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/entropy2008.pdf},
	author = {Taylor, Quinn C. and Stevenson, James E. and Delorey, Daniel P. and Knutson, Charles D.}
}
@article {Koch2008345,
	title = {Effort modeling and programmer participation in open source software projects},
	journal = {Information Economics and Policy (Empirical Issues in Open Source Software)},
	volume = {20},
	number = {4},
	year = {2008},
	note = {"Using a two-step approach, first a detailed case study on one project, GNOME, will be undertaken, then a large data set retrieved from a project hosting site, SourceForge.net, will be used to validate the results."

CVS was the main source of data

"e-mails sent to the different project discussion lists were identified as an additional source of information especially on communication and coordination besides the CVS-repository"

basic counts were calculated for developer discussion levels},
	month = {12/2008},
	pages = {345 - 355},
	abstract = {This paper develops models for programmer participation and effort estimation in open source software projects and employs the results to assess the efficiency of open source software creation. Successful development of such models will be important for decision makers of various kinds. We propose hypotheses based on a prior case study on manpower function and effort modeling. A large data set retrieved from a project repository is used to test these hypotheses. The main results are that if Norden-Rayleigh-based approaches are used, they need to be complemented in order to account for the addition of new features during a product life cycle, and that programmer-participation based effort models result in distinctly lower estimations of effort than those based on output metrics, such as lines of code.},
	keywords = {cvs, developers, email, email archives, gnome, lines of code, scm, Software repository mining, source code, sourceforge},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.06.004},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4SSND1J-1/2/c857fa1493e19aa7fe4297dedb077b3a},
	attachments = {https://flosshub.org/sites/flosshub.org/files/KochEffortModeling.pdf},
	author = {Koch, Stefan}
}
@inbook {866,
	title = {Emerging Patterns of Intersection and Segmentation when Computerization Movements Interact},
	booktitle = {Computerization Movements and Technology Diffusion: From Mainframes to Ubiquitous Computing},
	year = {2008},
	pages = {381-404},
	publisher = { Information Today, Inc.},
	organization = { Information Today, Inc.},
	author = {Walt Scacchi},
	editor = {Kraemer, K.L. and Elliott, M.}
}
@conference {SGKL09,
	title = {Evaluating the Quality of Open Source Software},
	booktitle = {Electronic Notes in Theoretical Computer Science},
	volume = {233},
	year = {2008},
	note = {"the software source code and the associated data stored in the version control system, the bug tracking databases, the mailing lists, and the wikis allow us to evaluate quality in a transparent way"
"The data collection system collects the raw data from open source projects"
Mailing lists are measured in: Number of unique subscribers, Number of messages in user/support list per month, Number of messages in developers list per month, Average thread depth},
	month = {03/2009},
	pages = {5{\textendash}28},
	publisher = {The Reengineering Forum},
	organization = {The Reengineering Forum},
	abstract = {Traditionally, research on quality attributes was either kept under wraps within the organization that performed it, or carried out by outsiders using narrow, black-box techniques. The emergence of open source software has changed this picture allowing us to evaluate both software products and the processes that yield them. Thus, the software source code and the associated data stored in the version control system, the bug tracking databases, the mailing lists, and the wikis allow us to evaluate quality in a transparent way. Even better, the large number of (often competing) open source projects makes it possible to contrast the quality of comparable systems serving the same domain. Furthermore, by combining historical source code snapshots with significant events, such as bug discoveries and fixes, we can further dig into the causes and effects of problems. Here we present motivating examples, tools, and techniques that can be used to evaluate the quality of open source (and by extension also proprietary) software. },
	keywords = {bug tracking system, email, email archives, mailing list, metrics, open source, process quality attributes, product quality attributes, source code, SQO-OSS, wiki},
	doi = {10.1016/j.entcs.2009.02.058},
	url = {http://www.dmst.aueb.gr/dds/pubs/conf/2008-SQM-SQOOSS/html/SGKL09.html},
	attachments = {https://flosshub.org/sites/flosshub.org/files/entcs-sqooss.pdf},
	author = {Diomidis Spinellis and Gousios, Georgios and Vassilios Karakoidas and Panagiotis Louridas and Paul J. Adams and Samoladas, Ioannis and Ioannis Stamelos}
}
@conference {1815,
	title = {An Exploratory Study on the Evolution of OSS Developer Communities},
	booktitle = {Proceedings of the 41st Annual Hawaii International Conference on System Sciences (HICSS 2008)},
	year = {2008},
	pages = {305 - 305},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, HI, USA},
	abstract = {Software is developed in a dynamic context where team structure, requirements, and processes evolve together with the product. Although researchers have been studying the evolution of software systems since the early 70s, the study on the evolution of software development teams remains rare. Such evolutionary patterns and their impact on software quality are especially important in the context of OSS (Open Source Software) development, where a group of volunteer developers collaborate online for an extended period of time. By analyzing how social networks of developers evolve over time while building OSS products, we can gain knowledge and experience to improve the effectiveness and efficiency of resource management and distribution in future OSS projects. To this end, we studied the evolution of the developer communities using a suite of OSS products developed under the KOffice project. We found that in general, the social networks of OSS developer communities change over time in certain ways. Identifying such patterns can help OSS managers better understand the unique process of OSS development and improve their management and coordination of the projects.
},
	doi = {10.1109/HICSS.2008.58},
	url = {https://www.researchgate.net/publication/221184171_An_Exploratory_Study_on_the_Evolution_of_OSS_Developer_Communities},
	author = {Ngamkajornwiwat, Kawin and Zhang, Dongsong and Koru, A. Gunes and Zhou, Lina and Nolker, and Robert}
}
@conference {Hata:2008:EFF:1370750.1370772,
	title = {An extension of fault-prone filtering using precise training and a dynamic threshold},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {89{\textendash}98},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Fault-prone module detection in source code is important for assurance of software quality. Most previous fault-prone detection approaches have been based on software metrics. Such approaches, however, have difficulties in collecting the metrics and in constructing mathematical models based on the metrics. To mitigate such difficulties, we have proposed a novel approach for detecting fault-prone modules using a spam-filtering technique, named Fault-Prone Filtering. In our approach, fault-prone modules are detected in such a way that the source code modules are considered as text files and are applied to the spam filter directly. In practice, we use the training only errors procedure and apply this procedure to fault-prone. Since no pre-training is required, this procedure can be applied to an actual development field immediately. This paper describes an extension of the training only errors procedures. We introduce a precise unit of training, "modified lines of code," instead of methods. In addition, we introduce the dynamic threshold for classification. The result of the experiment shows that our extension leads to twice the precision with about the same recall, and improves 15\% on the best F1 measurement.},
	keywords = {eclipse, fault-prone modules, spam filter, text mining},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370772},
	url = {http://doi.acm.org/10.1145/1370750.1370772},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p89-hata.pdf},
	author = {Hata, Hideaki and Mizuno, Osamu and Kikuno, Tohru}
}
@conference {972,
	title = {Extracting structural information from bug reports},
	booktitle = {Proceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {27-30},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {In software engineering experiments, the description of bug reports is typically treated as natural language text, although it often contains stack traces, source code, and patches. Neglecting such structural elements is a loss of valuable information; structure usually leads to a better performance of machine learning approaches. In this paper, we present a tool called infoZilla that detects structural elements from bug reports with near perfect accuracy and allows us to extract them. We anticipate that infoZilla can be used to leverage data from bug reports at a different granularity level that can facilitate interesting research in the future.},
	keywords = {bug reports, eclipse, enumerations, infozilla, natural language, patches, source code, stack trace},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370757},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p27-bettenburg.pdf},
	author = {Premraj, Rahul and Zimmermann, Thomas and Kim, Sunghun and Bettenburg, Nicolas}
}
@inbook {868,
	title = {Movement Ideology vs. User Pragmatism in the Organizational Adoption of Open Source Software},
	booktitle = {Computerization Movements and Technology Diffusion: From Mainframes to Ubiquitous Computing},
	year = {2008},
	pages = {427-452},
	publisher = {Information Today},
	organization = {Information Today},
	address = {Medford, NJ},
	author = {Dedrick, Jason and Joel West},
	editor = {Kraemer, Kenneth L. and Elliott, Margaret}
}
@booklet {526,
	title = {The Open and Closed Styles of Talent Acquisition and Management:  Which takes an edge where},
	year = {2008},
	abstract = {The phenomenal success of Free/Open Source Software during the recent years has led researchers in all related fields to re-think and re-evaluate the studies and concepts, especially those which the open source violates. Talent management and talent acquisition is no exception to this. The sudden rise in open source projects and their success is a cause of motivation for all of us to evaluate their philosophy and implement the same. Proper talent management and acquisition of talent can play a key role in strengthening the industry. Traditional closed management with their classic way of functioning may still look at the open source model as a big mystery. Open source has violated many of the theories of Software Engineering like limited team size, decentralized project management, etc. The concepts of self-motivated individuals, adaptive division of labor, informal or indirect leadership, etc. are the contributions of the open source to the world.

In this paper we discuss these concepts and state their differences with the way of working of closed talent management. Even though open source has various benefits in working, but requirement of a good coordination process, redundancy of development, versioning problems, etc. pose a limitation. We present an analogy of the talent management in the two concepts with that of the natural ecosystem. Talent in open source works in a manner similar to the ant colonies. Here the process is more community oriented and there is no single dictator power. The proprietary, on the other hand, works on talent as the lions ruling the den. There is a hierarchy and that needs to be respected. Only the leader has the right to make final decision, and that is binding. We also take a look into the present conditions of meltdown and show how the open source way is better suited for this scenario. Even though the present firms may be seeing a setback at this time of recession, the impact on firms with an open source way of working is much lighter or none at all. We also discuss the interactions between the two styles of talent management and present a model that can be adopted by the proprietary companies to benefit from open model. Our arguments of the paper not only deal with software, but also on content that comes under the domain of Creative Commons. We have taken the examples of Wikipedia, Sourceforge.net, Linux etc. for the various issues we discuss.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper.pdf},
	author = {Rahul Kala}
}
@conference {562,
	title = {Open Source Project Categorization Based on Growth Rate Analysis and Portfolio Planning Methods},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {375 - 380},
	publisher = {Springer},
	organization = {Springer},
	chapter = {35},
	abstract = {In this paper, we propose to arrive at an assessment and evaluation of open source projects based on an analysis of their growth rates in several aspects. These include code base, developer number, bug reports and downloads. Based on this analysis and assessment, a well-known portfolio planning method, the BCG matrix, is employed for arriving at a very broad classification of open source projects. While this approach naturally results in a loss of detailed information, a top-level categorization is in some domains necessary and of interest.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_35},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Project\%20Categorization.pdf},
	author = {Koch, Stefan and Stix, Volker}
}
@conference {Krogstie:2008:PTB:1368088.1368201,
	title = {Power through brokering: open source community participation in software engineering student projects},
	booktitle = {Proceedings of the 30th international conference on Software engineering},
	series = {ICSE {\textquoteright}08},
	year = {2008},
	pages = {791{\textendash}800},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Many software engineering projects use open source software tools or components. The project team{\textquoteright}s active participation in the open source community may be necessary for the team to use the technology. Based on an in-depth field study of industry software engineering project students interacting with an open source community, we find that participation in the community may affect the team{\textquoteright}s work and learning by strengthening the power of the broker between the team and the community. We outline pitfalls and benefits of having student teams acquire development-related knowledge from open source communities. The findings are relevant to the organization and supervision of software engineering student projects interacting with open source communities.},
	keywords = {Communities Of Practice, computer science education, FLOSS, open source, software engineering, software engineering education},
	isbn = {978-1-60558-079-1},
	doi = {10.1145/1368088.1368201},
	url = {http://doi.acm.org/10.1145/1368088.1368201},
	author = {Krogstie, Birgit R.}
}
@article {502,
	title = {Report on the effectiveness of a FLOSS-like learning community in formal educational settings},
	year = {2008},
	abstract = {This report examines some of the pedagogic principles embodied in Free / Libre Open Source Software (FLOSS) communities and briefly looks at case studies of FLOSS-like approaches in education. It analyzes and evaluates the differences between Free / Libre Open Source Software (FLOSS) communities as informal learning environments and on the other side formal educational settings. The report also point out ways on transferring those FLOSS principles to formal educational settings and looks at existing examples of eLearning delivery and examines why these do not provide the types of constructivist learning environments as observed in FLOSS communities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FLOSSCOM_Wp4_PHASE2_REPORT_d1.pdf},
	author = {Martin J. Weller and Andreas Meiszner and Sowe, Sulayman K. and Athanasis Karoulis}
}
@book {50,
	title = {Two Bits: The Cultural Significance of Free Software and the Internet},
	year = {2008},
	publisher = {Duke University Press},
	organization = {Duke University Press},
	author = {Christoper Kelty}
}
@conference {560,
	title = {Usability in Company Open Source Software Context - Initial Findings from an Empirical Case Study},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {359 - 365},
	publisher = {Springer},
	organization = {Springer},
	chapter = {33},
	abstract = {In the company open source software (OSS) development context, usability is becoming an important issue due to a growing user population, who is only interested in usable applications, not in their development. Companies try to gain a competitive advantage of OSS by utilizing available components, but the openness is difficult to achieve in the business world with licenses, patents and intellectual property rights. This paper analyses usability and user-interface (UI) development in the company OSS context through an interpretive case study in a software development unit of a large, global corporation. Our initial findings suggest that there is a need for human computer interaction specialists in the OSS context. It is revealed that with the software based on OSS, more time can be spent on usability and UI design. In the company{\textquoteright}s viewpoint, there are still many issues involved in deciding what parts of the product will be open source. Especially UI code may remain closed due to competitive advantage and patents.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Usability\%20in\%20Company\%20Open\%20Source.pdf},
	author = {Iivari, Netta and Hedberg, Henrik and Kirves, Tanja}
}
@conference {1005,
	title = {Comparing Approaches to Mining Source Code for Call-Usage Patterns},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {20 - 20},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Two approaches for mining function-call usage patterns from source code are compared. The first approach, itemset mining, has recently been applied to this problem. The other approach, sequential-pattern mining, has not been previously applied to this problem. Here, a call-usage pattern is a composition of function calls that occur in a function definition. Both approaches look for frequently occurring patterns that represent standard usage of functions and identify possible errors. Itemset mining produces unordered patterns, i.e., sets of function calls, whereas, sequential-pattern mining produces partially ordered patterns, i.e., sequences of function calls. The trade-off between the additional ordering context given by sequential-pattern mining and the efficiency of itemset mining is investigated. The two approaches are applied to the Linux kernel v2.6.14 and results show that mining ordered patterns is worth the additional cost.},
	keywords = {function calls, functions, kernel, linux, sequence, sequencing, sequential-pattern mining},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300020.pdf},
	author = {Kagdi, Huzefa and Collard, Michael L. and Maletic, Jonathan I.}
}
@article {springerlink:10.1007/s10588-006-9006-3,
	title = {Correlating temporal communication patterns of the Eclipse open source community with performance and creativity},
	journal = {Computational \&amp; Mathematical Organization Theory},
	volume = {13},
	year = {2007},
	note = {"Social network data was collected from the Eclipse component development groups{\textquoteright} online mailing lists by using the online process tool (Gloor and Zhao, 2004). Data on bugs and enhancements for each group was collected from the Eclipse bugzilla database (Eclipse bugzilla, 2004). The social network data was analyzed with the TeCFlow tool (Gloor and Zhao, 2004)."
"The study is based on data from the three main projects of the Eclipse open source development community, namely {\textquotedblleft}eclipse{\textquotedblright}, {\textquotedblleft}tools{\textquotedblright} and {\textquotedblleft}technology{\textquotedblright}. We have chosen thirty-three different component development groups for analysis."
"The online process tool (online process tool, 2004) was utilized to collect communication data from their mailing list archives. The online process tool runs a robot that searches for URLs in the projects{\textquoteright} mailing list archives to compile a list of the possible URL links. It then extracts communication data as tuples in the form of {\textquotedblleft}sender, receiver, communication type, timestamp, communication contents{\textquotedblright} and stores it in the database. Further, bugs and enhancement data were collected from the Eclipse bugzilla database."},
	pages = {17-27},
	publisher = {Springer Netherlands},
	abstract = {This paper studies the temporal communication patterns of online communities of developers and users of the open source Eclipse Java development environment. It measures the productivity of each community and seeks to identify correlations that exist between group communication characteristics and productivity attributes. The study uses the TeCFlow (Temporal Communication Flow) visualizer to create movie maps of the knowledge flow by analyzing the publicly accessible Eclipse developer mailing lists as an approximation of the social networks of developers and users. Thirty-three different Eclipse communities discussing development and use of components of Eclipse such as the Java Development Tools, the different platform components, the C/C++ Development Tools and the AspectJ extension have been analyzed over a period of six months. The temporal evolution of social network variables such as betweenness centrality, density, contribution index, and degree have been computed and plotted. Productivity of each development group is measured in terms of two indices, namely performance and creativity. Performance of a group is defined as the ratio of new bugs submitted compared with bugs fixed within the same period of time. Creativity is calculated as a function of new features proposed and implemented. Preliminary results indicate that there is a correlation between attributes of social networks such as density and betweenness centrality and group productivity measures in an open source development community. We also find a positive correlation between changes over time in betweenness centrality and creativity, and a negative correlation between changes in betweenness centrality and performance.},
	keywords = {bug fixing, bugs, bugzilla, communication, creativity, developers, eclipse, email, email archives, feature requests, mailing lists, performance, productivity},
	issn = {1381-298X},
	url = {http://dx.doi.org/10.1007/s10588-006-9006-3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/16.pdf},
	author = {Kidane, Yared and Gloor, Peter}
}
@conference {624,
	title = {Exploring the Effects of Coordination and Communication Tools on the Efficiency of Open Source Projects using Data Envelopment Analysis},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	note = {"based on the date january 8, 2007, we selected the 30 most often downloaded projects from Sourceforge.net"},
	month = {2007///},
	pages = {97 - 108},
	publisher = {Springer},
	organization = {Springer},
	chapter = {8},
	abstract = {In this paper, we propose to explore possible benefits of communication and coordination tools in open source projects using data envelopment analysis (DEA), a general method for efficiency comparisons. DEA offers several advantages: It is a non-parametric optimization method without any need for the user to define any relations between different factors or a production function, can account for economies or diseconwhile omies of scale, and is able to deal with multi-input, multi-output systems in which the factors have different scales. Using a data set of 30 open source project retrieved from SourceForge.net, we demonstrate the application of DEA, showing that the efficiency of the projects is in general relatively high. Regarding the effects of tool employment on the efficiency of projects, the results were surprising: Most of the possible tools, and overall usage, showed a negative relationship to efficiency.
},
	keywords = {metadata, sourceforge},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_8},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Exploring\%20the\%20Effects\%20Coodination.pdf},
	author = {Koch, Stefan}
}
@conference {999,
	title = {Mining Software Repositories with iSPAROL and a Software Evolution Ontology},
	booktitle = {Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {10 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {One of the most important decisions researchers face when analyzing the evolution of software systems is the choice of a proper data analysis/exchange format. Most existing formats have to be processed with special programs written specifically for that purpose and are not easily extendible. Most scientists, therefore, use their own database(s) requiring each of them to repeat the work of writing the import/export programs to their format.

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

The paper also shows iSPARQL -- our SPARQL-based Semantic Web query engine containing similarity joins. Together with EvoOnt, iSPARQL can accomplish a sizable number of tasks sought in software repository mining projects, such as an assessment of the amount of change between versions or the detection of bad code smells. To illustrate the usefulness of EvoOnt (and iSPARQL), we perform a series of experiments with a real-world Java project. These show that a number of software analyses can be reduced to simple iSPARQL queries on an EvoOnt dataset.},
	keywords = {database, eclipse, evoont, java, owl, semantic, sparql},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.21},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300010.pdf},
	author = {Kiefer, Christoph and Bernstein, Abraham and Tappolet, Jonas}
}
@conference {873,
	title = {Noticing Notice: A large-scale experiment on the timing of software license agreements.},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2007},
	month = {28/04/2007},
	pages = {607-616},
	publisher = {ACM},
	organization = {ACM},
	address = {San Jose, CA},
	isbn = {978-1-59593-593-9},
	author = {N. Good and J. Grossklags and D. Mulligan and Konstan, J.A.}
}
@conference {1012,
	title = {Prioritizing Warning Categories by Analyzing Software History},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {27 - 27},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Automatic bug finding tools tend to have high false positive rates: most warnings do not indicate real bugs. Usually bug finding tools prioritize each warning category. For example, the priority of "overflow" is 1 and the priority of "jumbled incremental" is 3, but the tools{\textquoteright} prioritization is not very effective.

In this paper, we prioritize warning categories by analyzing the software change history. The underlying intuition is that if warnings from a category are resolved quickly by developers, the warnings in the category are important. Experiments with three bug finding tools (FindBugs, JLint, and PMD) and two open source projects (Columba and jEdit) indicate that different warning categories have very different lifetimes. Based on that observation, we propose a preliminary algorithm for warning category prioritizing.},
	keywords = {bug fixing, change history, columba, findbugs, jedit, jlint, kenyon, pmd, warning},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.26},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300027.pdf},
	author = {Kim, Sunghun and Ernst, Michael D.}
}
@conference {1225,
	title = {Programming Language Trends in Open Source Development: An Evaluation Using Data from All Production Phase SourceForge Projects},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	note = {"Our data were gathered from the SourceForge Research Ar- chive (SFRA) [4] and the CVS repositories Open Source projects hosted on SourceForge. We used cvs2mysql and SFRA+ to collect the data. cvs2mysql gathers data from CVS repositories and writes them to SQL scripts for im- port into a MySQL 5.0 database. The data collected by cvs2mysql are the name of the file, the location of the file in the repository, the type and state of the file, as well as the author, date, number of lines added and removed, and the author{\textquoteright}s message for each revision to the file."},
	abstract = {In this work, we analyze data collected from the CVS repos- itories of 9,997 Open Source projects hosted on SourceForge in an effort to understand trends in programming language usage in the Open Source community between 2000 and 2005. The trends we consider include: 1) the relative popularity of the ten most popular programming languages over time, 2) the use of multiple programming languages by individual programmers and by individual projects, and 3) the programming languages most often used in combination.},
	keywords = {cvs, cvs2mysql, programming languages, sfra, sourceforge, srda},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Delorey2007b.pdf},
	author = {Delorey, Daniel P. and Knutson, Charles D. and Giraud-Carrier, C.}
}
@conference {1227,
	title = {Simulation of the temporal evolution of OSS projects: application to XMMS and MPLAYER},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	author = {Antoniades, Ionannis~ and Kontoyiannis and Ioannis Stamelos and Deligiannis, Ignatios}
}
@conference {875,
	title = {Social Comparisons to Motivate Contributions to an Online Community.},
	booktitle = {Persuasive Technology},
	year = {2007},
	month = {26/04/2007},
	address = {Palo Alto, CA},
	author = {F. Harper and X. Li and Y. Chen and J. Konstan}
}
@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}
}
@article {64,
	title = {Study~of~Available~Tools },
	year = {2007},
	institution = {FLOSSmetrics},
	type = {EU Framework deliverable},
	isbn = {D1.1},
	url = {http://flossmetrics.org/sections/deliverables/docs/deliverables/WP1/D1.1- Study_of_Available_Tools.pdf},
	author = {Antoniades, Ionannis~ and Samoladas, Ioannis and Sowe, Sulayman K. and Gregorio Robles and Koch, Stefan and Fraczek, Ksenia and Hadzisalihovic, Anis}
}
@conference {1212,
	title = {Studying Production Phase SourceForge Projects: An Exploratory Analysis Using cvs2mysql and SFRA},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	month = {2007},
	abstract = {A wealth of data can be extracted from the natural by-products of software development processes and used in empirical studies of software engineering. However, the size and accuracy of such studies depend in large part on the availability of tools that facilitate the collection of data from individual projects and the combination of data from multiple projects. To demonstrate this point, we present our experience gathering and analyzing data from nearly 10,000 open source projects hosted on SourceForge. We describe the tools we developed to collect the data and the ways in which these tools and data may be used by other researchers. We also provide examples of statistics that we have calculated from these data to describe interesting author- and project-level behaviors of the SourceForge community.},
	keywords = {Data Collection, forge, repositories, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Delorey2007c.pdf},
	author = {Delorey, Daniel P. and Knutson, Charles D. and MacLean, Alexander C.}
}
@conference {874,
	title = {Talk Amongst Yourselves: Inviting Users to Participate in Online Conversations.},
	booktitle = {International Conference on Intelligent User Interfaces  },
	series = {Proceedings of the 12th international conference on Intelligent user interfaces},
	year = {2007},
	month = {28/01/2007},
	pages = {62-71},
	publisher = {ACM},
	organization = {ACM},
	address = {Honolulu, Hawaii},
	isbn = {1-59593-481-2},
	author = {F. Harper and D. Frankowski and Drenner, S. and Y. Ren and S. Kiesler and Terveen, L. and Kraut, R. and Riedl, J.}
}
@conference {644,
	title = {The Use of Open Source Software in Enterprise Distributed Computing Environments},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {277 - 282},
	publisher = {Springer},
	organization = {Springer},
	chapter = {28},
	abstract = {Firms increasingly rely on open source software for solving business problems and building mission-critical IT solutions. However, there are numerous issues associated with OSS, including its influence on the total cost of ownership (TCO) and supportability and upgradeability risks. While savings from obtaining a free copy of the software can be significant, software accounts for an average of 10\% of TCO, while the majority of the costs are associated with project staffing. OSS requires significant investment into staffing because it needs to be carefully selected, customized, and installed. In addition, global communities may gather and dissolve at their will, so guarantees of support, revision, and bug fixes are minimal. Yet companies can gain competitive advantage through an ability to customize software to address specific business issues and exercising control over development, revision schedules, and modifications. OSS is not a panacea from the rising software costs. Instead, it is a serious initiative that has benefits, disadvantages, and risks associated with it.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_28},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Use\%20of\%20OSS\%20in\%20Enterprise.pdf},
	author = {Krivoruchko, Jacob}
}
@conference {Tsunoda:2006:AOD:1137983.1138031,
	title = {Analyzing OSS developers{\textquoteright} working time using mailing lists archives},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {181{\textendash}182},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Our mining question is {\textquotedblleft}when OSS developers work?{\textquotedblright} OSS developers{\textquoteright} working time may be a good indicator to understand the development style of a project. (For example, if many developers work in office hour, these might be daily works in a company.)},
	keywords = {developers, email, email archives, mailing lists, mining challenge, msr challenge, overtime work, postgresql, workload},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138031},
	url = {http://doi.acm.org/10.1145/1137983.1138031},
	attachments = {https://flosshub.org/sites/flosshub.org/files/181AnalyzingOSS.pdf},
	author = {Tsunoda, Masateru and Monden, Akito and Kakimoto, Takeshi and Kamei, Yasutaka and Matsumoto, Ken-ichi}
}
@booklet {507,
	title = {Bringing Open Source Software to the Desktop : An In-Depth Study of the Implementation and use of Star Office},
	year = {2006},
	month = {Sept},
	abstract = {Open Source software is coming to the attention of individuals, organisations, and governments worldwide, and is increasingly being adopted by firms for specific business purposes. However, the uptake of end-user desktop OSS applications to date has been modest, and Microsoft products remain the de-facto standard on the corporate desktop. This brings into sharp focus one of the most challenging questions faced by the Open Source community today ... namely, if organisations value low acquisition costs, low total cost of ownership of software, potentially plentiful support, free access to source code, and the wish to avoid proprietary software vendor lock-in, why have more organisations not adopted OSS?  This paper contributes to the existing research by reporting on an in-depth, interpretive, processual study of an attempt by a large Irish Trade Union to replace Microsoft Office with an Open Source alternative, StarOffice.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Bringing_OSS_to_the_Desktop.pdf},
	author = {PJ Wall and Seamas Kelly}
}
@conference {681,
	title = {Call for Quality: Open Source Software Quality Observation},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {57 - 62},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper describes how a Software Quality Observatory works to evaluate and quantify the quality of an Open Source project. Such a quality measurement can be used by organizations intending to deploy an Open Source solution to pick one of the available projects for use. We offer a case description of how the Software Quality Observatory will be applied to the KDE project to document and evaluate its quality practices for outsiders.
},
	keywords = {kde, quality},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Call\%20for\%20Quality.pdf},
	author = {de Groot, Adriaan and K{\"u}gler, Sebastian and Adams, Paul and Gousios, Giorgos}
}
@conference {685,
	title = {Conceptual Modelling as a New Entry in the Bazaar: The Open Model Approach},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {9 - 20},
	publisher = {Springer},
	organization = {Springer},
	abstract = {The present contribution proposes to transfer the main principles of open source software development to a new context: conceptual modelling; an activity closely related to software development. The goal of the proposed {\textquotedblleft}open model{\textquotedblright} approach is to collaboratively develop reference models for everyone to copy, use and refine in a public process. We briefly introduce conceptual modelling and reference models, discuss the cornerstones of an open modelling process, and propose a procedure for initiating, growing and sustaining an open model project. The paper concludes with a discussion of potential benefits and pitfalls.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_2},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Conceptual\%20Modelling\%20as\%20a\%20New\%20Entry.pdf},
	author = {Koch, Stefan and Strecker, Stefan and Frank, Ulrich}
}
@conference {Sager:2006:DSJ:1137983.1138000,
	title = {Detecting similar Java classes using tree algorithms},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {65{\textendash}71},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Similarity analysis of source code is helpful during development to provide, for instance, better support for code reuse. Consider a development environment that analyzes code while typing and that suggests similar code examples or existing implementations from a source code repository. Mining software repositories by means of similarity measures enables and enforces reusing existing code and reduces the developing effort needed by creating a shared knowledge base of code fragments. In information retrieval similarity measures are often used to find documents similar to a given query document. This paper extends this idea to source code repositories. It introduces our approach to detect similar Java classes in software projects using tree similarity algorithms. We show how our approach allows to find similar Java classes based on an evaluation of three tree-based similarity measures in the context of five user-defined test cases as well as a preliminary software evolution analysis of a medium-sized Java project. Initial results of our technique indicate that it (1) is indeed useful to identify similar Java classes, (2)successfully identifies the ex ante and ex post versions of refactored classes, and (3) provides some interesting insights into within-version and between-version dependencies of classes within a Java project.},
	keywords = {change analysis, clones, coogle, eclipse, famix, java, similarity, software evolution, software repositories, source code, tree similarity measures},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138000},
	url = {http://doi.acm.org/10.1145/1137983.1138000},
	attachments = {https://flosshub.org/sites/flosshub.org/files/65Detecting.pdf},
	author = {Sager, Tobias and Bernstein, Abraham and Pinzger, Martin and Kiefer, Christoph}
}
@conference {Kim:2006:LDT:1137983.1138027,
	title = {How long did it take to fix bugs?},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {173{\textendash}174},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The number of bugs (or fixes) is a common factor used to measure the quality of software and assist bug related analysis. For example, if software files have many bugs, they may be unstable. In comparison, the bug-fix time--the time to fix a bug after the bug was introduced--is neglected. We believe that the bug-fix time is an important factor for bug related analysis, such as measuring software quality. For example, if bugs in a file take a relatively long time to be fixed, the file may have some structural problems that make it difficult to make changes. In this report, we compute the bug-fix time of files in ArgoUML and PostgreSQL by identifying when bugs are introduced and when the bugs are fixed. This report includes bug-fix time statistics such as average bug-fix time, and distributions of bug-fix time. We also list the top 20 bug-fix time files of two projects.},
	keywords = {argouml, bug fixing, bugs, mining challenge, msr challenge, postgresql, quality, time},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138027},
	url = {http://doi.acm.org/10.1145/1137983.1138027},
	attachments = {https://flosshub.org/sites/flosshub.org/files/173HowLong.pdf},
	author = {Kim, Sunghun and Whitehead,Jr., E. James}
}
@conference {1094,
	title = {Knowledge Reuse in Open Source Software: An Exploratory Study of 15 Open Source Projects},
	booktitle = {Proceedings of the 38th Annual Hawaii International Conference on System Sciences},
	year = {2006},
	note = {"In a first step, we asked developers of different open source projects to respond to a very short web-based survey."...
"In a second step, we started with gathering data from 15 projects, including interviews. In parallel, the source code, CVS comments and to a certain extent email communication was analyzed to receive a dynamic, and within the limits of the method, complete picture of knowledge reuse practices."
"Projects included games (Adonthell, FlightGear, Xboard), text processing (Abiword), a GNU/Linux desktop (Xfce4), an instant messenger client (Miranda), fax software (HylaFAX), a content management system (Tiki/CMS Groupware), encryption software (OpenSSL), a collaborative music system (iRATE Radio), file sharing networks (GNUnet, Mnet, Freenet), a mailing list manager (Mailman), and an mp3 encoder (Lame)."
"Our data sources included interviews with key developers, source code, CVS comments, mailing lists and various Internet resources"},
	month = {2006},
	pages = {1-10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Big Island, HI, USA},
	abstract = {To date, there is no investigation of knowledge reuse in open source software projects. This paper focuses on the forms of knowledge reuse and the factors impacting on them. It develops a theory drawn from data of 15 open source software projects and finds that the effort to search, integrate and maintain external knowledge influences the form of knowledge to be reused. Implications for firms and innovation research are discussed.},
	keywords = {cvs, email, knowledge reuse, lines of code, loc, source code, Survey},
	doi = {10.1109/HICSS.2005.378},
	url = {http://www.computer.org/csdl/proceedings/hicss/2005/2268/07/22680198b-abs.html},
	author = {von Krogh, G. and Spaeth, S. and Haefliger, S.}
}
@conference {697,
	title = {Life cycle of Defects in Open Source Software Projects},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	note = {"we collected and analyzed defects of the apache http server and mozilla firefox" 
"all the defects reported between X and X were analyzed"},
	pages = {195 - 200},
	publisher = {Springer},
	organization = {Springer},
	abstract = {We studied the maintenance process from the viewpoint of defect management and the defect life cycle. First, we outline a model for the defect life cycle based on ISO/IEC standards, the Framework for Open Source maintenance process, and the Bugzilla defect management system. Thereafter, we analyze defects from two Open Source software projects. The aim of the study was support the maintenance reliability. However, we found that most of the defects did not follow the life-cycle model. Defects were usually directly resolved from initial state without being assigned.
},
	keywords = {apache, defects, Firefox, mozilla},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_19},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Life\%20cycle\%20of\%20Defects\%20in\%20OSS\%20Projects.pdf},
	author = {Koponen, Timo}
}
@book {52,
	title = {Math You Can{\textquoteright}t Use: Patents, Copyright, and Software},
	year = {2006},
	publisher = {Brookings Institution Press},
	organization = {Brookings Institution Press},
	author = {Klemens, B.}
}
@conference {Kim:2006:MPE:1137983.1137995,
	title = {Micro pattern evolution},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {40{\textendash}46},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {When analyzing the evolution history of a software project, we wish to develop results that generalize across projects. One approach is to analyze design patterns, permitting characteristics of the evolution to be associated with patterns, instead of source code. Traditional design patterns are generally not amenable to reliable automatic extraction from source code, yet automation is crucial for scalable evolution analysis. Instead, we analyze {\textquotedblleft}micro pattern{\textquotedblright} evolution; patterns whose abstraction level is closer to source code, and designed to be automatically extractable from Java source code or bytecode. We perform micro-pattern evolution analysis on three open source projects, ArgoUML, Columba, and jEdit to identify micro pattern frequencies, common kinds of pattern evolution, and bug-prone patterns. In all analyzed projects, we found that the micro patterns of Java classes do not change often. Common bug- prone pattern evolution kinds are {\textquoteleft}Pool {\textrightarrow} Pool{\textquoteright}, {\textquoteleft}Implementor {\textrightarrow} NONE{\textquoteright}, and {\textquoteleft}Sampler {\textrightarrow} Sampler{\textquoteright}. Among all pattern evolution	kinds,{\textquoteleft}Box{\textquoteright},{\textquoteleft}CompoundBox{\textquoteright},	{\textquoteleft}Pool{\textquoteright}, {\textquoteleft}CommonState{\textquoteright}, and {\textquoteleft}Outline{\textquoteright} micro patterns have high bug rates, but they have low frequencies and a small number of changes. The pattern evolution kinds that are bug-prone are somewhat similar across projects. The bug-prone pattern evolution kinds of two different periods of the same project are almost identical.},
	keywords = {argouml, bugs, columba, design patterns, evolution, extraction, java, jedit, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137995},
	url = {http://doi.acm.org/10.1145/1137983.1137995},
	attachments = {https://flosshub.org/sites/flosshub.org/files/40MicroPattern.pdf},
	author = {Kim, Sunghun and Pan, Kai and Whitehead,Jr., E. James}
}
@conference {Kagdi:2006:MSC:1137983.1137996,
	title = {Mining sequences of changed-files from version histories},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {47{\textendash}53},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Modern source-control systems, such as Subversion, preserve change-sets of files as atomic commits. However, the specific ordering information in which files were changed is typically not found in these source-code repositories. In this paper, a set of heuristics for grouping change-sets (i.e., log-entries) found in source-code repositories is presented. Given such groups of change-sets, sequences of files that frequently change together are uncovered. This approach not only gives the (unordered) sets of files but supplements them with (partial temporal) ordering information. The technique is demonstrated on a subset of KDE source-code repository. The results show that the approach is able to find sequences of changed-files.},
	keywords = {change, change history, change management, change sequences, heuristics, kde, mining software repositories, scm, sequences, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137996},
	url = {http://doi.acm.org/10.1145/1137983.1137996},
	attachments = {https://flosshub.org/sites/flosshub.org/files/47MiningSequences.pdf},
	author = {Kagdi, Huzefa and Yusuf, Shehnaaz and Maletic, Jonathan I.}
}
@conference {Zimmermann:2006:MVA:1137983.1138001,
	title = {Mining version archives for co-changed lines},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {72{\textendash}75},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Files, classes, or methods have frequently been investigated in recent research on co-change. In this paper, we present a first study at the level of lines. To identify line changes across several versions, we define the annotation graph which captures how lines evolve over time. The annotation graph provides more fine-grained software evolution information such as life cycles of each line and related changes: "Whenever a developer changed line 1 of version.txt she also changed line 25 of Library.java."},
	keywords = {change, change analysis, change management, graph, lines of code, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138001},
	url = {http://doi.acm.org/10.1145/1137983.1138001},
	attachments = {https://flosshub.org/sites/flosshub.org/files/72MiningVersionArchives.pdf},
	author = {Zimmermann, Thomas and Kim, Sunghun and Zeller, Andreas and Whitehead,Jr., E. James}
}
@conference {889,
	title = {Motivating Participation by Displaying the Value of Contribution},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2006},
	month = {22/04/2006},
	pages = {955-958},
	publisher = {ACM},
	organization = {ACM},
	address = {Montreal, Quebec, Canada},
	isbn = {1-59593-372-7},
	author = {Al Mamunur Rashid and Kimberly Ling and Regina D Tassone and Paul Resnick and Robert Kraut and John Riedl}
}
@conference {Knab:2006:PDD:1137983.1138012,
	title = {Predicting defect densities in source code files with decision tree learners},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {119{\textendash}125},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {With the advent of open source software repositories the data available for defect prediction in source files increased tremendously. Although traditional statistics turned out to derive reasonable results the sheer amount of data and the problem context of defect prediction demand sophisticated analysis such as provided by current data mining and machine learning techniques.In this work we focus on defect density prediction and present an approach that applies a decision tree learner on evolution data extracted from the Mozilla open source web browser project. The evolution data includes different source code, modification, and defect measures computed from seven recent Mozilla releases. Among the modification measures we also take into account the change coupling, a measure for the number of change-dependencies between source files. The main reason for choosing decision tree learners, instead of for example neural nets, was the goal of finding underlying rules which can be easily interpreted by humans. To find these rules, we set up a number of experiments to test common hypotheses regarding defects in software entities. Our experiments showed, that a simple tree learner can produce good results with various sets of input data.},
	keywords = {change analysis, data mining, decision tree learner, defect density, defect prediction, mozilla, prediction, release history, scm, source code, version control},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138012},
	url = {http://doi.acm.org/10.1145/1137983.1138012},
	attachments = {https://flosshub.org/sites/flosshub.org/files/119Predicting.pdf},
	author = {Knab, Patrick and Pinzger, Martin and Bernstein, Abraham}
}
@conference {706,
	title = {Retrieving Open Source Software Licenses},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {35 - 46},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Open Source Software maintenance and reuse require identifying and comprehending the applied software licenses. This paper first characterizes software maintenance, and open source software (OSS) reuse which are particularly relevant in this context. The information needs of maintainers and reusers can be supported by reverse engineering tools at different information retrieval levels. The paper presents an automated license retrieval approach called ASLA. User needs, system architecture, tool features, and tool evaluation are presented. The implemented tool features support identifying source file dependencies and licenses in source files, and adding new license templates for identifying licenses. The tool is evaluated against another tool for license information extraction. ASLA requires the source code as available input but is otherwise not limited to OSS. It supports the same programming languages as GCC. License identification coverage is good and the tool is extendable.
},
	keywords = {gaim, license, license analysis, maintenance, mozilla, reuse},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Retrieving\%20Open\%20Source\%20Software\%20Licenses.pdf},
	author = {Tuunanen, Timo and Koskinen, Jussi and K{\"a}rkk{\"a}inen, Tommi}
}
@article {1119,
	title = {Strategic Interaction and Knowledge Sharing in the KDE Developer Mailing List},
	journal = {Management Science},
	volume = {52},
	year = {2006},
	note = {"the threaded discussion from the K Desktop Environment (KDE) developer mailing list was used."
March 15 to March 31, 2000.
128 threads selected.
measures: (1) level of participation measured by number of postings made by indiv. devs in a thread
(2) conversational interactivity (how long is a conversation)
(3) cross-thread connectivity},
	month = {07/2006},
	pages = {1031 - 1042},
	abstract = {In stark contrast with the fully participative "bazaar" imagery of open source software (OSS) development, some recent empirical research has pointed out that much of the OSS development is carried out by a small percentage of developers. This raises serious concerns that concentration of development effort on a few will limit knowledge sharing and underutilize the available resources. Using the notion of strategic interaction, this paper argues that individual developers often interact strategically with other highly resourceful developers by forming a smaller but better organized structure to intensify the types of epistemic interactions that matter most to the OSS development. A general framework of strategic interaction including participation inequality, conversational interactivity, and cross-thread connectivity is proposed to examine its impact on knowledge sharing, and validated using 128 discussion threads from the K Desktop Environment (KDE) developer mailing list. The findings indicate that strategic interaction has expanded knowledge sharing but with the caveat that extreme concentration of development could have an opposite effect. For researchers, this study dovetails the incentive logic by proposing and validating the strategic aspects of OSS participation to better understand the collective dynamics underpinning OSS development. Practitioners can use this approach to evaluate and better support existing knowledge-sharing initiatives.},
	keywords = {developers, email, email archives, kde, knowledge collaboration, knowledge sharing, mailing list},
	issn = {1526-5501},
	doi = {10.1287/mnsc.1060.0551},
	author = {Kuk, George}
}
@article {893,
	title = {User Choices and Regret: Understanding Users{\textquoteright} Decision Process bout Consensually Acquired Spyware},
	journal = {I/S: A Journal of Law and Policy for the Information Society},
	volume = {2},
	number = {2},
	year = {2006},
	month = {01/2006},
	author = {N. Good and J. Grossklags and Konstan, J.A. and D. Mulligan and A. Perzanowski and D. Thaw}
}
@conference {Kakimoto:2006:USB:1137983.1138026,
	title = {Using software birthmarks to identify similar classes and major functionalities},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {171{\textendash}172},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	keywords = {argouml, class, file, mining challenge, msr challenge, multi-dimensional scaling, similarity, software birthmark, source code},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138026},
	url = {http://doi.acm.org/10.1145/1137983.1138026},
	attachments = {https://flosshub.org/sites/flosshub.org/files/171UsingSoftware.pdf},
	author = {Kakimoto, Takeshi and Monden, Akito and Kamei, Yasutaka and Tamada, Haruaki and Tsunoda, Masateru and Matsumoto, Ken-ichi}
}
@conference {Kim:2005:ASC:1083142.1083154,
	title = {Analysis of signature change patterns},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {1{\textendash}5},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software continually changes due to performance improvements, new requirements, bug fixes, and adaptation to a changing operational environment. Common changes include modifications to data definitions, control flow, method/function signatures, and class/file relationships. Signature changes are notable because they require changes at all sites calling the modified function, and hence as a class they have more impact than other change kinds.We performed signature change analysis over software project histories to reveal multiple properties of signature changes, including their kind, frequency, and evolution patterns. These signature properties can be used to alleviate the impact of signature changes. In this paper we introduce a taxonomy of signature change kinds to categorize observed changes. We report multiple properties of signature changes based on an analysis of eight prominent open source projects including the Apache HTTP server, GCC, and Linux 2.5 kernel.},
	keywords = {apache, gcc, kernel, linux, signature change, signature change patterns, software evolution, software evolution path, soure code},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083154},
	url = {http://doi.acm.org/10.1145/1082983.1083154},
	attachments = {https://flosshub.org/sites/flosshub.org/files/64AnalysisOfSignature.pdf},
	author = {Kim, Sunghun and Whitehead,Jr., E. James and Bevan, Jennifer}
}
@article {51,
	title = {Brazil adopts open-source software},
	volume = {2008},
	number = {5 December},
	year = {2005},
	month = {2 June, 2005},
	publisher = {BBC News},
	address = {Sao Paulo},
	url = {http://news.bbc.co.uk/2/hi/business/4602325.stm},
	author = {Kingstone, Steve}
}
@inbook {900,
	title = {A Conceptual Model for Enterprise Adoption of Open Source Software},
	booktitle = {The Standards Edge: Open Season},
	year = {2005},
	pages = {51-62},
	publisher = {Sheridan Books},
	organization = {Sheridan Books},
	address = {Ann Arbor, Mich.},
	author = {Kwan, Stephen K. and Joel West},
	editor = {Bolin, Sherrie}
}
@conference {902,
	title = {An Economic Model of User Rating in an Online Recommender System},
	booktitle = {10th International Conference on User Modeling},
	year = {2005},
	address = {Edinburgh, UK},
	author = {F.M. Harper and X. Li and Y. Chen and Konstan, J.A.}
}
@conference {740,
	title = {Evolution of Open Source Software Systems {\textendash} A Large-Scale Investigation},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {148-153},
	abstract = {In this paper, the evolution of a large sample of open source software projects will be analysed. The evolution of commercial systems has been an issue that has long been a center of research, thus a coherent theoretical framework of software evolution has been developed and empirically tested. Therefore these results can be used to compare the situation in open source projects to the evolution of commercial projects. This allows to assess whether the underlying software process indeed significantly differs. The data collection methodology relying on a large software repository and the respective source code control systems is described, and an overview on the collected data on several thousand projects is given. The evolutionary behaviour is explored using both a linear and a quadratic model, with the quadratic model significantly outperforming the linear one. The most interesting fact is that while in the mean the growth rate is decreasing over time according to the l...},
	url = {http://pascal.case.unibz.it/handle/2038/863},
	author = {Koch, Stefan}
}
@article {flosswp209,
	title = {Free software and open source: The freedom debate and its consequences (Published in First Monday)},
	year = {2005},
	month = {March},
	abstract = {To most outsiders the ethics of software is not something usually considered. To most proficient computer users with a passing interest in this question the ethics of software is recognised as one of the fundamental questions in the digital rights area. To most of the latter, terms such as free software, open source, and their derivatives (FLOSS, FOSS, Software Freedom) are interchangeable. Choosing one over the other is a matter of taste rather than politics. However, to most insiders the question is not one of taste. There is a fundamental difference between the two areas even if they share a similar root. Free software is not the same as open source. The two groups differ in their fundamental philosophical approach to software and its importance to society as a whole. This paper examines the two groups? differing philosophies and explores how their actions have affected software development, access to fundamental software infrastructure, and the development of the concept of freedom.},
	author = {Mathias Klang}
}
@article {49,
	title = {Geeks, Social Imaginaries, and Recursive Publics},
	journal = {Cultural Anthropology},
	volume = {20},
	number = {2},
	year = {2005},
	pages = {185-214},
	publisher = {Blackwell Publishing on behalf of the American Anthropological Association},
	abstract = {This article investigates the social, technical, and legal affiliations among "geeks" (hackers, lawyers, activists, and IT entrepreneurs) on the Internet. The mode of association specific to this group is that of a "recursive public sphere" constituted by a shared imaginary of the technical and legal conditions of possibility for their own association. On the basis of fieldwork conducted in the United States, Europe, and India, I argue that geeks imagine their social existence and relations as much through technical practices (hacking, networking, and code writing) as through discursive argument (rights, identities, and relations). In addition, they consider a "right to tinker" a form of free speech that takes the form of creating, implementing, modifying, or using specific kinds of software (especially Free Software) rather than verbal discourse.},
	isbn = {08867356},
	url = {http://www.jstor.org/stable/3651533},
	author = {Christoper Kelty}
}
@conference {903,
	title = {How Oversight Improves Member-Maintained Communities},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2005},
	publisher = {ACM},
	organization = {ACM},
	address = {Portland OR},
	author = {Cosley, D. and D. Frankowski and S. Kiesler and Terveen, L. and Riedl, J.}
}
@conference {904,
	title = {How Peer Photos Influence Member Participation in Online Communities},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2005},
	publisher = {ACM},
	organization = {ACM},
	address = {Portland, OR},
	author = {Kapoor, N. and Konstan, J.A. and Terveen, L. G.}
}
@article {105,
	title = {Improving Web accessibility through an enhanced open-source browser},
	journal = {Ibm Systems Journal},
	volume = {44},
	number = {3},
	year = {2005},
	note = {Times Cited: 2},
	pages = {573-588},
	abstract = {The accessibilityWorks project provides software enhancements to the Mozilla (TM) Web browser and allows users to control their browsing environment. Although Web accessibility standards specify markup that must be incorporated for Web pages to be accessible, these standards do not ensure a good experience for all Web users. This paper discusses user controls that facilitate a number of adaptations that can greatly increase the usability of Web pages for a diverse population of users. in addition to transformations that change page presentation, innovations are discussed that enable mouse and keyboard input correction as well as vision-based control for users unable to use their hands for computer input.},
	author = {Hanson, V. L. and Brezin, J. P. and Crayne, S. and Keates, S. and Kjeldsen, R. and Richards, J. T. and Swart, C. and Trewin, S.}
}
@article {flosswp229,
	title = {Innovativeness of open source software projects},
	year = {2005},
	month = {August},
	abstract = {The paper addresses an ongoing debate about the innovativeness of open source projects and critically evaluates the innovative potential of 500 most active projects registered by SourceForge.net. The analysis is based on a proposed framework, distinguishing between radical inventions, technology / platform modifications, and marketing innovations. Research findings include relatively low levels of technical newness in the studies sample, alongside high interest of developers and users in the innovative projects. The article discusses the underlying mechanisms, restricting innovativeness of community-driven open source efforts, and postulates the establishment of an institution of idea brokers playing roles corresponding to venture capitalists in the commercial software domain.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/klincewicz.pdf},
	author = {Krzysztof Klincewicz}
}
@article {flosswp200,
	title = {The Launching of Mozilla Firefox - A Case Study in Community-Led Marketing},
	year = {2005},
	month = {January},
	abstract = {Mozilla Firefox is a Free/Libre/Open Source (FLOSS) browser supported by the Mozilla Foundation. This browser was recently released and has met with considerable success- it has been downloaded more than 20 million times and has already taken considerable market share from its prime competitor- Microsoft?s Internet Explorer. In this paper, I chronicle how the efforts of 63000 volunteers led to a community successfully competing with a powerful corporation. I identify four factors as the key facilitators to Firefox? success- complacent competition, product superiority, presence of marketing leader and volunteer support.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/sandeep2.pdf},
	author = {Sandeep Krishnamurthy}
}
@article {flosswp245,
	title = {Linux vs. Windows: A comparison of application and platform innovation incentives for open source and proprietary software platforms},
	year = {2005},
	month = {October},
	abstract = {The paper analyzes and compares the investment incentives of platform and application developers for Linux and Windows. We find that the level of investment in applications is larger when the operating system is open source rather than proprietary. The comparison of the levels of investment in the operating systems depends, among others, on reputation effects and the number of developers. The paper also develops a short case study comparing Windows and Linux and identifies new directions for open source software research.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/economideskatsamakas.pdf},
	author = {Nicholas Economides and Evangelos Katsamakas}
}
@conference {759,
	title = {Risk Assessment of an Open Source Migration Project},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {246-249},
	abstract = {In this paper we investigate the risks of an Open Source migration in the small Public Administration (PA) area. We consider not just technical risks (like security or reliability), but strategic issues (like e-government priorities, mid-term ownership cost items) and some social relations are also taken into consideration.},
	url = {http://pascal.case.unibz.it/handle/2038/1432},
	author = {Drozdik, Sylvester and Kov{\'a}cs, George L. and Kochis, P{\'a}l Zolt{\'a}n}
}
@conference {899,
	title = {Stopping spyware at the gate: a user study of privacy, notice and spyware},
	booktitle = {2005 Symposium on Usable Privacy and Security},
	year = {2005},
	month = {07/2005},
	pages = {43-52},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Pittsburgh, PA},
	keywords = {agreement,, and, Aspects,, Design,, end, EULA,, Experimentation,, Factors,, Human, Legal, license, notice,, of, privacy,, security, service,, spyware,, terms, ToS,, usability,, user},
	isbn = {1-59593-178-3 },
	author = {N. Good and Dhamija, R. and J. Grossklags and D. Thaw and Aronowitz, S. and D. Mulligan and J. Konstan}
}
@article {flosswp246,
	title = {Two-sided competition of proprietary vs. open source technology platforms and the implications for the software industry},
	year = {2005},
	month = {October},
	abstract = {Technology platforms, such as Microsoft Windows, are the hubs of technology industries. We develop a framework to characterize the optimal two-sided pricing strategy of a platform firm, that is, the pricing strategy towards the direct users of the platform as well as towards firms offering applications that are complementary to the platform. We compare industry structures based on a proprietary platform (such as Windows) with those based on an open-source platform (such as Linux) and analyze the structure of competition and industry implications in terms of pricing, sales, profitability, and social welfare. We find that, when the platform is proprietary, the equilibrium prices for the platform, the applications, and the platform access fee for applications may be below marginal cost, and we characterize demand conditions that lead to this. The proprietary applications sector of an industry based on an open source platform may be more profitable than the total profits of a proprietary platform industry. When users have a strong preference for application variety, the total profits of the proprietary industry are larger than the total profits of an industry based on an open source platform. The variety of applications is larger when the platform is open source. When a system based on an open source platform with an independent proprietary application competes with a proprietary system, the proprietary system is likely to dominate the open source platform industry both in terms of marketshare and profitability. This may explain the dominance of Microsoft in the market for PC operating systems.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/economideskatsamakas2.pdf},
	author = {Nicholas Economides and Evangelos Katsamakas}
}
@conference {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 {744,
	title = {Using the Iterated Prisoner{\textquoteright}s Dilemma for Explaining the Evolution of Cooperation in Open Source Communities},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {186-191},
	abstract = {Software development, and especially open source projects, typically involve repeated interactions between participants and groups of participants. We propose to analyse this situation by means of the standard model for the evolution of cooperation, the iterated prisoner{\textquoteright}s dilemma. The prisoner{\textquoteright}s dilemma is a well-known model for a two-person game, in which each side can choose to either cooperate or defect, and in which the payoffs are arranged in a defined hierarchy (e.g. the highest payoff is achieved by defecting while the other player cooperates). As a first step, the prisoner{\textquoteright}s dilemma needs to be formulated for the open source development model, i.e. what constitutes cooperation, playing defect and payoffs. Then, computer simulations using a population of stochastic reactive strategies can be applied, using a strategy{\textquoteright}s payoff as fitness measure for determining its frequency in the next generation. As a further extension, the effects of misinterpretation of other...},
	url = {http://pascal.case.unibz.it/handle/2038/1559},
	author = {Eckert, Daniel and Koch, Stefan and Mitl{\"o}hner, Johann}
}
@conference {Xinyi04fourinteresting,
	title = {Four Interesting Ways in Which History Can Teach Us About Software},
	booktitle = {Proceedings of the 2004 international workshop on Mining software repositories  - MSR {\textquoteright}04},
	year = {2004},
	month = {05/2004},
	pages = {58-62},
	abstract = {In this position paper, we outline four kinds of studies that we have undertaken in trying to understand various aspects of a software system{\textquoteright}s evolutionary history. In each instance, the studies have involved detailed examination of real software systems based on {\textquotedblleft}facts{\textquotedblright} extracted from various kinds of source artifact repositories, as well as the development of accompanying tools to aid in the extraction, abstraction, and comprehension processes. We briefly discuss the goals, results, and methodology of each approach.},
	keywords = {ant, apache, change analysis, clone, clone detection, cvs, evolution, gcc, growth, kepler, linux, midworld, mycore, postgresql, source code, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/58FourInterestingWays.pdf},
	author = {Michael Godfrey and Xinyi Dong and Cory Kapser and Lijie Zou}
}
@proceedings {1186,
	title = {How can Academic Software Research and Open Source Software Development help each other?},
	year = {2004},
	pages = {5-8},
	abstract = {In this paper we discuss a few issues faced in coordinating, managing and implementing academic software research projects and suggest how some of these issues can be addressed by adopting tools and processes from Open Source Software Development. At the same time we also discuss how a few issues in Open Source Software Development (OSSD) projects can be addressed by adopting processes from Academic Software Research.},
	keywords = {academic, education},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ambati6-9.pdf},
	author = {Ambati, V. and Kishore, S.P.}
}
@article {flosswp185,
	title = {Papers from Anthropological Quarterly (Vol 77, No 3) - Social Thought and Commentary: Culture{\textquoteright}s Open Source},
	year = {2004},
	month = {October},
	abstract = {Listing of papers: Christopher M. Kelty | Culture{\textquoteright}s Open Sources: Software, Copyright, and Cultural Critique {\textendash}- Gabriella Coleman | The Political Agnosticism of Free and Open Source Software and the Inadvertent Politics of Contrast {\textendash}- Alex Golub | Copyright and Taboo {\textendash}- Anita Chan | Coding Free Software, Coding Free States: Free Software Legislation and the Politics of Code in Peru{\textendash}- Christopher M. Kelty | Punt To Culture{\textendash}- Rosemary J. Coombe \& Andrew Herman | Rhetorical Virtues: Property, Speech, and the Commons on the World-Wide Web{\textendash}- Glenn Otis Brown | Commentary},
	attachments = {https://flosshub.org/sites/flosshub.org/files/aq_cultures_opensources.pdf},
	author = {Christoper Kelty}
}
@article {1077,
	title = {Profiling an Open Source Project Ecology and Its Programmers},
	journal = {Electronic Markets},
	volume = {14},
	year = {2004},
	month = {6/2004},
	pages = {77 - 88},
	abstract = {While many successful and well-known open source projects produce output of high quality, a general assessment of this development paradigm is still missing. In this paper, an online community of both small and large, successful and failed projects and their programmers is analysed mainly using the version-control data of each project, also according to their productivity and estimation of expended effort. As the results show, there are indeed significant differences between this cooperative development model and the commercial organization of work in the areas explored. Both open source software projects in their size and their programmers{\textquoteright} effort differ significantly, and the evolution of projects{\textquoteright} size over time seems in part to contradict the laws of software evolution proposed for commercial systems. Both the inequality of effort distribution between programmers and an increasing number of developers in a project do not lead to a decrease in productivity, opposing Brooks{\textquoteright}s Law. Effort estimation based on the COCOMO model for commercial organizations shows a large amount of effort expended for the projects, while a more general Norden-Rayleigh modeling shows a distinctly smaller expenditure. This proposes that either a highly efficient development is achieved by this self-organizing cooperative and highly decentralized form of work, or that the participation of users besides programming tasks is enormous and constitutes an economic factor of large proportions. },
	keywords = {affiliation network, brooks law, cocomo, effort estimation, evolution, productivity, project success, scm, size, time, version control},
	issn = {1422-8890},
	doi = {10.1080/10196780410001675031},
	author = {Koch, Stefan}
}
@proceedings {131,
	title = {Remote analysis and measurement of libre software systems by means of the CVSanaly tool},
	year = {2004},
	address = {Edinburgh, Scotland},
	abstract = {Libre (free, open source) software is one of the paradigmatic cases where heavy use of telematic tools and user-driven software development are key points. This paper proposes a methodology for measuring and analyzing remotely big libre software projects using publicly-available data from their version control repositories. By means of a tool called CVSAnalY that has been implemented following this methodology, measurements and analyses can be made in an automatic and non-intrusive way, providing real-time and historical data about the project and its contributors.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles-koch-barahona_cvsanaly.pdf},
	author = {Gregorio Robles and Koch, Stefan and Jesus M. Gonzalez-Barahona}
}
@proceedings {1192,
	title = {WebDAV based Open Source Collaborative Development Environment},
	year = {2004},
	pages = {53-57},
	abstract = {Open source projects are characterized by their distributed developers, openness, and use of a community-based development process. Successful open source projects such as Apache, Linux, and PHP have a web-based Collaborative Development Environment (CDE) that provides source code repository access, knowledge management, discussion lists, bug tracking, and user support. Distributed software development is also increasingly common for commercial software projects, and benefits from using web-based CDEs. GForge, derived from the SourceForge package, is an open web-based CDE that is seeing widespread open source and commercial use. To support remote authoring of web pages and file contents, as well as remote source code access, GForge uses several network protocols, including SSH/SFTP, CVS pserver, and FTP. These protocols inevitably introduce security risks and add administrative work. We modified GForge to eliminate use of FTP, SSH/SFTP, and CVS protocols, using instead a WebDAV-based integration. The new CDE, called Davenport, uses only the HTTP/WebDAV protocol, and HTTP/WebDAV replaces the other protocols without sacrificing functionality. In this paper we describe the architecture and features of Davenport, and show how WebDAV replaces existing network protocols. We discuss the future development directions of CDEs including integration of client side IDEs and using a CDE as a software test bed.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Kim54-58.pdf},
	author = {Kim, S. and Pan, K. and Whitehead, J.}
}
@proceedings {1174,
	title = {On Automatic Categorization of Open Source Software},
	year = {2003},
	pages = {79-83},
	attachments = {https://flosshub.org/sites/flosshub.org/files/79-83.pdf},
	author = {Kawaguchi, S. and Garg, P.K. and Matsushita, M. and Inoue, K.}
}
@article {flosswp85,
	title = {An Introduction to Open Source Communities},
	year = {2003},
	month = {04/2003},
	institution = {Blue Oxen Associates},
	abstract = {This report describes what open source communities are and how they work. It cites relevant research and presents original case studies of two open source projects: TouchGraph and SquirrelMail. It then identifies patterns of collaboration shared by these projects, and describes how these patterns might apply to other types of communities. Finally, it reviews what is still not well understood about open source communities, and proposes several paths for further research.},
	keywords = {free software foundation directory, freshmeat, fsf, sourceforge, squirrelmail, touchgraph},
	attachments = {https://flosshub.org/sites/flosshub.org/files/blueoxen.pdf},
	author = {Eugene Eric Kim}
}
@article {flosswp179,
	title = {Open Source Software - An Economic Assessment},
	year = {2003},
	month = {December},
	abstract = {This study examines whether or not Open Source Software represents an economically suitable alternative to the proprietary commercial software market in terms of creating value-added and economic efficiency. Whereas no significant differences between both production processes are seen for customized software, the study comes to the conclusion that serious economic problems can occur in the field of packaged software. Starting from a discussion on how licenses like the GPL affect the ability to price software (which is usually below economic production costs), the impact of below cost pricing on the coordination capacity of software markets (customer sovereignty, resource allocation, income distribution, adaptability and innovation) and the sustainability of complementary strategies of Open Source business models (with and without cross subsidization of the non-market OSS-core) are described. Throughout the study, the role of the pricing system within a market economy is stressed considering the specific characteristics of software as an economic good. Aspects other than economic are not taken into account.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kalweykoothslangenfurth.pdf},
	author = {Nadine Kalwey}
}
@proceedings {95,
	title = {Open source software in the trenches: Lessons from a large-scale OSS implementation},
	year = {2003},
	keywords = {open source},
	author = {Fitzgerald, Brian and Kenny, Tony}
}
@conference {Ye:2003:TUM:776816.776867,
	title = {Toward an understanding of the motivation Open Source Software developers},
	booktitle = {Proceedings of the 25th International Conference on Software Engineering},
	series = {ICSE {\textquoteright}03},
	year = {2003},
	note = {"Analyzing the emails sent to the mailing fist is one way of understanding the structure of the community."
"Table 2 displays the number of code contributions made by members to the GIMP system and the defined roles of those contributing members. We counted the number of contributions made by each person by analyzing the change log of the system."},
	pages = {419{\textendash}429},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {An Open Source Software (OSS) project is unlikely to be successful unless there is an accompanied community that provides the platform for developers and users to collaborate. Members of such communities are volunteers whose motivation to participate and contribute is of essential importance to the success of OSS projects. In this paper, we aim to create an understanding of what motivates people to participate in OSS communities. We theorize that learning is one of the motivational forces. Our theory is grounded in the learning theory of Legitimate Peripheral Participation, and is supported by analyzing the social structure of OSS communities and the co-evolution between OSS systems and communities. We also discuss practical implications of our theory for creating and maintaining sustainable OSS communities as well as for software engineering research and education.},
	keywords = {change log, COMMUNITY, contributions, contributors, developers, email, email archives, evolution, gimp, log files, mailing list, roles, source code},
	isbn = {0-7695-1877-X},
	url = {http://portal.acm.org/citation.cfm?id=776816.776867},
	attachments = {https://flosshub.org/sites/flosshub.org/files/YeKishida.pdf},
	author = {Ye, Yunwen and Kishida, Kouichi}
}
@article {101,
	title = {The user-developer communication process: a critical case study},
	journal = {Information Systems Journal},
	volume = {13},
	number = {1},
	year = {2003},
	note = {Times Cited: 5},
	pages = {37-68},
	abstract = {Although user participation in systems development is widely believed to have positive impacts on user acceptance, it does not guarantee success and there is still much that we do not know about how and why user participation sometimes delivers positive benefits, but not always. Much of the prior research on user participation assumes that user-developer communication will ensure that the resulting system will be designed to meet users{\textquoteright} needs and will be accepted by them. The nature and quality of the communication between users and developers, however, remains an understudied aspect of user participation. In this paper, we focus on the user-developer communication process. We propose a process model that delineates four stages of communication between users and software developers, and we argue that these stages must occur for user participation to lead to effective outcomes. To illustrate our model, we apply it to analyse a {\textquoteright}critical case study{\textquoteright} of a software project that failed despite high levels of user involvement. We show that when {\textquoteright}communication lapses{\textquoteright} occurred in several of the user-developer communication stages, developers failed to be informed regarding the underlying reasons that users avoided the system. Based on the insights from this case study, we advise researchers and practitioners how to leverage the potential benefits of user participation, rather than take them for granted.},
	author = {Gallivan, M. J. and Keil, M.}
}
@article {flosswp40,
	title = {Cave or Community? An Empirical Examination of 100 Mature Open Source Projects},
	journal = {First Monday},
	volume = {7},
	number = {6},
	year = {2002},
	note = {The author conducts an empirical study of the top 100 mature projects on SourceForge.net to develop an understanding of the F/OSS community. The author sought empirical evidence that would help us understand which is more common- the cave (i.e., lone producer) or the community in F/OSS development. Some key findings include: first, most F/OSS programs are developed by individuals, rather than communities. Second, most OSS programs do not generate a lot of discussion. Third, products with more developers tend to be viewed and downloaded more often. Fourth, the number of developers associated with a project is unrelated to the age of the project.},
	month = {06/2002},
	abstract = {Starting with Eric Raymond{\textquoteright}s groundbreaking work, "The Cathedral and the Bazaar", open-source software (OSS) has commonly been regarded as work produced by a community of developers. Yet, given the nature of software programs, one also hears of developers with no lives that work very hard to achieve great product results. In this paper, I sought empirical evidence that would help us understand which is more common - the cave (i.e., lone producer) or the community. Based on a study of the top 100 mature products on Sourceforge, I find a few surprising things. First, most OSS programs are developed by individuals, rather than communities. The median number of developers in the 100 projects I looked at was 4 and the mode was 1 - numbers much lower than previous numbers reported for highly successful projects! Second, most OSS programs do not generate a lot of discussion. Third, products with more developers tend to be viewed and downloaded more often. Fourth, the number of developers associated with a project was positively correlated to the age of the project. Fifth, the larger the project, the smaller the percent of project administrators.},
	keywords = {age, contributors, developers, project success, registration, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/krishnamurthy.pdf},
	author = {Sandeep Krishnamurthy}
}
@article {1117,
	title = {Effort, co-operation and co-ordination in an open source software project: GNOME},
	journal = {Information Systems Journal},
	volume = {12},
	year = {2002},
	note = {"Also retrieved by a Perl script were the postings to the relevant discussion lists including the sender, the subject, time and complete text. For analysis of the posting behaviour of the programmers, the short name that each programmer uses for checkins had to be matched to the full name or email address used for postings. For 175 persons, this has been possible using several regular expressions with human check-up."},
	month = {01/2002},
	pages = {27 - 42},
	abstract = {This paper presents results from research into open source projects from a software engineering perspective. The research methodology employed relies on public data retrieved from the CVS repository of the GNOME project and relevant discussion groups. This methodology is described, and results concerning the special characteristics of open source software development are given. These data are used for a first approach to estimating the total effort to be expended.},
	keywords = {cvs, discussion, effort estimation, gnome},
	issn = {1365-2575},
	doi = {10.1046/j.1365-2575.2002.00110.x},
	author = {Koch, Stefan and Schneider, Georg}
}
@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}
}
@article {46,
	title = {Free/Libre and Open Source Software: Survey and Study},
	year = {2002},
	author = {Rishab Ayer Ghosh and R{\"u}dige Glott and Krieger, B. and Gregorio Robles}
}
@article {hansen2002open,
	title = {The Open Source approach{\textemdash}opportunities and limitations with respect to security and privacy},
	journal = {Computers \& Security},
	volume = {21},
	number = {5},
	year = {2002},
	pages = {461{\textendash}471},
	publisher = {Elsevier},
	abstract = {Today{\textquoteright}s software often does not even fulfil basic security or privacy requirements. Some people regard the open source paradigm as the solution to this problem. First, we carefully explain the security and privacy aspects of open source, which in particular offer the possibility for a dramatic increase in trustworthiness for and autonomy of the user. We show which expectations for an improvement of the software trustworthiness dilemma are realistic. Finally, we describe measures necessary for developing secure and trustworthy open source systems.},
	keywords = {security},
	url = {https://dud.inf.tu-dresden.de/literatur/HaKP_02OpenSource_0214.doc},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HaKP_02OpenSource_0214.doc},
	author = {Hansen, Marit and K{\"o}hntopp, Kristian and Pfitzmann, Andreas}
}
@article {flosswp58,
	title = {Shaping Code},
	year = {2002},
	month = {September},
	abstract = {This article addresses how society shapes code. The term "code," as we use it, consists of the hardware and software components of information technologies. Code is increasingly being sought as a regulatory mechanism in conjunction with or as an alternative to law for addressing societal concerns such as crime, privacy, intellectual property protection, and revitalizing democratic discourse. This article analyzes how various societal institutions, that create code differentially, influence the technical and social characteristics of the code that is developed by them. The article also provides recommendations on how society can intervene and proactively shape the development of code to vindicate societal concerns and preferences.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shah.pdf},
	author = {Jay Kesan}
}
@conference {1144,
	title = {﻿﻿Conceptual Sociological Model for Open Source Software},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kishida.pdf},
	author = {Kishida, Kouichi}
}
@conference {1138,
	title = {Creating a Free, Dependable Software Engineering Environment for Building Java Applications},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {As open source software engineering becomes more prevalent, employing sound software engineering practices and the tools used to implement these practices becomes more important. This paper examines the current status of free software engineering tools. For each set of tools, we determined the important attributes that would best assist a developer in each stage of the waterfall model. We rated each tool based on predetermined attributes. We used the creation of a graphical user interface based email client in Java to assist in evaluating each tool. Our findings show that there is still a need for free tools to extract UML diagrams, test graphical user interfaces, make configuring Emacs easier, and profile Java applications. In other areas there are free tools that provide satisfactory functionality such as Concurrent Versions System (CVS), GVim, JUnit, JRefactory, GNU Make, Jakarta Ant, Javadoc, and Doc++.},
	keywords = {applications, cvs, Doc++, GNU Make, GVim, Jakarta Ant, java, Javadoc, jrefactory, junit, tools},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bittman.pdf},
	author = {Bittman, M. and Roos, R. and Kapfhammer, G.M.}
}
@article {flosswp25,
	title = {Distributed Knowledge and the Global Organization of Software Development},
	year = {2001},
	month = {February},
	abstract = {Open-source software development is a production model that exploits the distributed intelligence of participants in Internet communities. This model is efficient because of two related reasons: it avoids the inefficiencies of a strong intellectual property regime and it implements concurrently design and testing of software modules. The hazard of open source is that projects can ?fork? into competing versions. However, open-source communities consist of governance structures that constitutionally minimize this danger. Because open source works in a distributed environment, it presents an opportunity for developing coun-tries to participate in frontier innovation.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kogut1.pdf},
	author = {Bruce Kogut}
}
@article {flosswp29,
	title = {Free Software/Free Science},
	year = {2001},
	month = {December},
	abstract = {This paper explores the comparison often made between Free Software and scientific research, and the tendency to discuss both endeavors by positing a role for reputation as the currency of value. It discusses a handful of examples from the history and social study of science to explain how scholars have approached similar issues in understanding scientific activity. It also offers some speculations on the relationship between the metaphorical currency of reputation and real money, and that between metaphorical and actual intellectual property.},
	author = {Christoper Kelty}
}
@conference {1148,
	title = {Introducing a {\textquotedblleft}Street Fair{\textquotedblright} Open source Practice Within Project Based Software Engineering Courses},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {Columbia University and USC, as well as many other universities, have software engineering courses where students work in small teams to develop a product of moderate complexity. Typically such efforts are {\textquotedblleft}closed source{\textquotedblright} where teams do not (or are forbidden) from sharing information and providing assistance to other teams. There are certainly many justifiable reasons for this such as grading uniformity. Yet strong drivers such as grade competition, generally thought to promote quality results (i.e. successful projects), often do not. The authors ran an experiment introducing a style of open source practice called {\textquotedblleft}street fair{\textquotedblright} with surprisingly positive results.},
	keywords = {education, educational resources},
	attachments = {https://flosshub.org/sites/flosshub.org/files/portkaiser.pdf},
	author = {Port, D. and Kaiser, G.}
}
@article {flosswp5,
	title = {Economic Model for Impact of Open Source Software},
	year = {2000},
	month = {November},
	abstract = {This paper presents an economic model of the impact of Open Source Software (OSS) upon a commercial software market. Agents are used to model the users (buyers), the companies (sellers), the code bank (marketplace), and the OSS community (source of free goods). The effect of introducing open source products into an equilibrium commercial market is investigated with respect to demand structure.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osseconomics.pdf},
	author = {Asif Khalak}
}
@article {flosswp7,
	title = {Open Source Software As Consumer Integration Into Production},
	year = {2000},
	month = {October},
	abstract = {The author proposes a model of consumer integration into production as means of understanding the Open Source software phenomenon.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Jenny\%2520Kuan\%2520-\%2520Open\%2520Source\%2520Software\%2520As\%2520Integration\%2520into\%2520Production.pdf},
	author = {Jenny Kuan}
}
@article {flosswp6,
	title = {Results From Software Engineering Research Into Open Source Development Projects Using Public Data},
	number = {22},
	year = {2000},
	institution = {Diskussionspapiere zum T{\"a}tigkeitsfeld Informationsverarbeitung und Informationswirtschaft},
	type = {Discussion Paper},
	abstract = {This paper presents first results from research into open source projects from a software engineering perspective. The research methodology employed relies on public data retrieved from the CVS-repository of the GNOME project and relevant discussion groups. This methodology is described in detail and some of the results concerning the special characteristics of open source software development are given.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/koch-ossoftwareengineering.pdf},
	author = {Koch, Stefan and Schneider Georg}
}
@article {114,
	title = {An Empirical Approach to Studying Software Evolution},
	journal = {IEEE Transactions On Software Engineering},
	volume = {25},
	number = {4},
	year = {1999},
	abstract = {With the approach of the new millennium, a primary focus in software engineering involves issues relating to upgrading, migrating, and evolving existing software systems. In this environment, the role of careful empirical studies as the basis for improving software maintenance processes, methods, and tools is highlighted. One of the most important processes that merits empirical evaluation is software evolution. Software evolution refers to the dynamic behavior of software systems as they are maintained and enhanced over their lifetimes. Software evolution is particularly important as systems in organizations become longer-lived. However, evolution is challenging to study due to the longitudinal nature of the phenomenon in addition to the usual difficulties in collecting empirical data. In this paper, we describe a set of methods and techniques that we have developed and adapted to empirically study software evolution. Our longitudinal empirical study involves collecting, coding, and analyzing more than 25,000 change events to 23 commercial software systems over a 20-year period. Using data from two of the systems, we illustrate the efficacy of flexible phase mapping and gamma sequence analytic methods originally developed in social psychology to examine group problem solving processes. We have adapted these techniques in the context of our study to identify and understand the phases through which a software system travels as it evolves over time. We contrast this approach with time series analysis, the more traditional way of studying longitudinal data. Our work demonstrates the advantages of applying methods and techniques from other domains to software engineering and illustrates how, despite difficulties, software evolution can be empirically studied.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/EmpiricalApproachSwEvolution_SlaughterKemerer1999.pdf},
	author = {Kemerer, Chris F. and Sandra Slaughter}
}
@unpublished {flosswp4,
	title = {Scale and Convention: Programmed Languages in a Regulated America},
	year = {1999},
	month = {December},
	abstract = {This thesis is a combination of an ethnography of an internet healthcare startup company and a philosophical investigation of technical standards, open and closed. Chapters K, L, and M are introductions to three main figures in the Open Source movement between 1998-2000 {\textendash} Richard Stallman, Lawrence Lessig, and Eric Raymond.},
	author = {Christoper Kelty}
}
