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

},
	doi = {10.1007/978-3-319-57735-7_9},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_9},
	author = {Lundell, Bj{\"o}rn and Gamalielsson, Jonas and Stefan Tengblad and Bahram Hooshyar Yousefi and Thomas Fischer and Gert Johansson and Bengt Rodung and Mattsson, Anders and Johan Oppmark and Gustavsson, Tomas and Feist, Jonas and Stefan Landemoo and Erik L{\"o}nroth}
}
@proceedings {1910,
	title = {Charting the market disruptive nature of Open Source: Experiences from Sony Mobile },
	year = {2017},
	month = {05/2017},
	pages = {175-176},
	abstract = {Open Source Software (OSS) has substantial impact
on how software-intensive firms develop products and deliver
value to the customers. These companies need both strategic
and operational support on how to adapt OSS as a part of their
products and how to adjust processes and organizations to
increase the benefits from OSS participation. This work
presents the key insights from the journey that Sony Mobile
has made from a company developing proprietary software to
a respected member of OSS communities. We framed the
experiences into an Open Source Maturity Model that includes
two scenarios: engineering-driven and business-driven open
source. We outline the most important decisions, roles,
processes and implications. },
	keywords = {ecosystem, poster, software business},
	author = {Mols, CE and Wnuk, K}
}
@conference {Murphy:2017:CEF:3017680.3017682,
	title = {Community Engagement with Free and Open Source Software},
	booktitle = {Proceedings of the 2017 ACM SIGCSE Technical Symposium on Computer Science Education},
	series = {SIGCSE {\textquoteright}17},
	year = {2017},
	pages = {669{\textendash}670},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {A common refrain from Senior Exit Surveys and Alumni Surveys is the desire to work on "real-world," "practical" and "hands-on" projects using industry-ready tools and development environments. To assuage this, institutions have moved towards adopting Free and Open Source Software (FOSS) as an avenue to provide meaningful, applied learning interventions to students. Through these experiences, students benefit from engagement with various communities including: the community of contributors to the FOSS project; the community of local software developers; the community of citizens who reside in the local area; the community of students at their institution and others; and, the community of people impacted by the FOSS project. These engagements motivate students, enhance their communication and technical skills, allow them to grow and become more confident, help them form professional networks, and provide the "real-world" projects they seek. In this panel, we will discuss our experiences in engaging students with five different types of communities as part of incorporating FOSS into our courses, focusing on how other educators can provide the same benefits to their students as well. In order to satisfy the time constraints of the panel, the last two authors will present together.},
	keywords = {free and open source software (FOSS), humanitarian free and open source software (HFOSS), localized free and open source software (LFOSS), under-represented minorities (URM)},
	isbn = {978-1-4503-4698-6},
	doi = {10.1145/3017680.3017682},
	url = {http://doi.acm.org/10.1145/3017680.3017682},
	author = {Murphy, Christian and Buffardi, Kevin and Dehlinger, Josh and Lambert, Lynn and Veilleux, Nanette}
}
@proceedings {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 {1907,
	title = {Do Software Developers Understand Open Source Licenses?},
	year = {2017},
	note = {Data: We report on the results of a survey that asked
developers about 42 different cases of the use of code under
different open source licenses. To make the survey tractable
for developers to answer, we focused on three popular open
source licenses (GNU GPL 3.0, GNU LGPL 3.0 and MPL
2.0)

Findings: The survey results indicate that most of the 375 respondents
to our survey struggle with understanding the interaction of
open source licenses in both simple and complex software
development cases},
	month = {05/2017},
	pages = {1-11},
	abstract = {{\textemdash}Software provided under open source licenses is
widely used, from forming high-profile stand-alone applications
(e.g., Mozilla Firefox) to being embedded in commercial offerings
(e.g., network routers). Despite the high frequency of use of open
source licenses, there has been little work about whether software
developers understand the open source licenses they use. To our
knowledge, only one survey has been conducted, which focused
on which licenses developers choose and when they encounter
problems with licensing open source software. To help fill the
gap of whether or not developers understand the open source
licenses they use, we conducted a survey that posed development
scenarios involving three popular open source licenses (GNU GPL
3.0, GNU LGPL 3.0 and MPL 2.0) both alone and in combination.
The 375 respondents to the survey, who were largely developers,
gave answers consistent with those of a legal expert{\textquoteright}s opinion in
62\% of 42 cases. Although developers clearly understood cases
involving one license, they struggled when multiple licenses were
involved. An analysis of the quantitative and qualitative results of
the study indicate a need for tool support to help guide developers
in understanding this critical information attached to software
components.},
	keywords = {license, Survey},
	doi = {10.1109/ICPC.2017.7},
	author = {Almeida, Daniel A. and Murphy, Gail C. and Wilson, Greg and Hoye, Mike}
}
@proceedings {1895,
	title = {How are Developers Treating License Inconsistency Issues? A Case Study on License Inconsistency Evolution in FOSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {69-79},
	publisher = {Springer},
	abstract = {A license inconsistency is the presence of two or more source files that evolved from the same original file containing different licenses. In our previous study, we have shown that license inconsistencies do exist in open source projects and may lead to potential license violation problems. In this study, we try to find out whether the issues of license inconsistencies are properly solved by analyzing two versions of a FOSS distribution{\textemdash}Debian{\textemdash}and investigate the evolution patterns of license inconsistencies. Findings are: license inconsistencies occur mostly because the original copyright owner updated the license while the reusers were still using the old version of the source files with the old license; most license inconsistencies would disappear when the reusers synchronize their project from the upstream, while some would exist permanently if reusers decide not to synchronize anymore. Legally suspicious cases have not been found yet in those Debian distributions.},
	keywords = {Code clone, debian, License inconsistency, licenses, Software license},
	doi = {10.1007/978-3-319-57735-7_8},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_8},
	author = {Y. Wu and Manabe, Yuki and Daniel M. Germ{\'a}n and Inoue, K.}
}
@conference {1925,
	title = {Investigating developers{\textquoteright} email discussions during decision-making in Python language evolution},
	booktitle = {Proceedings of the 21st International Conference on Evaluation and Assessment in Software Engineering  - EASE{\textquoteright}17},
	year = {2017},
	pages = {286 - 291},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Karlskrona, SwedenNew York, New York, USA},
	abstract = {Context: Open Source Software (OSS) developers use mailing lists as their main forum for discussing the evolution of a project. However, the use of mailing lists by developers for decision-making has not received much research attention. Objective: We have explored this issue by studying developers{\textquoteright} email discussions around Python Enhancement Proposals (PEPs). Method: Our dataset comprised 42,672 emails from six different mailing lists pertaining to PEP development. We performed multiple forms of analysis on these emails, involving both quantitative measures (e.g., frequency) and deeper analysis of specific PEP discussions (i.e., outlier analysis). Results: Out of three PEP types (Informational, Process and Standard Track), Standard Track PEPs attract a large amount of discussion (both in volume and average number of messages per proposal). Our study also identified specific PEP states and topics that generated a disproportionate amount of discussion. Conclusion: Our outcomes point to several opportunities for improving the management of an OSS team based on the knowledge generated from discussions. We have also identified several interesting avenues for future work such as identifying individuals or groups that present persuasive arguments during decision-making.},
	isbn = {9781450348041},
	doi = {10.1145/3084226.3084271},
	url = {https://www.researchgate.net/publication/317486549_Investigating_developers\%27_email_discussions_during_decision-making_in_Python_language_evolution},
	author = {Stanger, Nigel and Rainer, Austen and Licorish, Sherlock A. and Sharma, Pankajeshwara and Savarimuthu, Bastin Tony Roy}
}
@inbook {Kerzazi2017,
	title = {Knowledge Flows Within Open Source Software Projects: A Social Network Perspective},
	booktitle = {Advances in Ubiquitous Networking 2: Proceedings of the UNet{\textquoteright}16},
	year = {2017},
	pages = {247{\textendash}258},
	publisher = {Springer Singapore},
	organization = {Springer Singapore},
	address = {Singapore},
	abstract = {Developing software is knowledge-intensive activity, requiring extensive technical knowledge and awareness. The abstract part of development is the social interactions that drive knowledge flows between contributors, especially for Open Source Software (OSS). This study investigated knowledge sharing and propagation from social perspective using social network analysis (SNA). We mined and analyzed the issue and review histories of three OSS from GitHub. Particular attention has been paid to the socio-interactions through comments from contributors on reviews. We aim at explaining the propagation and density of knowledge flows within contributor networks. The results show that review requests flow from the core contributors toward peripheral contributors and comments on reviews are in a continuous loop from the core teams to the peripherals and back; and the core contributors leverage on their awareness and technical knowledge to increase their notoriety by playing the role of communication brokers supported by comments on work items.},
	keywords = {expertise, Knowledge flows, open source, SNA},
	isbn = {978-981-10-1627-1},
	doi = {10.1007/978-981-10-1627-1_19},
	url = {http://dx.doi.org/10.1007/978-981-10-1627-1_19},
	author = {Kerzazi, Noureddine and El Asri, Ikram},
	editor = {El-Azouzi, Rachid and Menasche, Daniel Sadoc and Sabir, Essa{\"\i}d and De Pellegrini, Francesco and Benjillali, Mustapha}
}
@proceedings {1919,
	title = {A Large-Scale Study on the Usage of Testing Patterns that Address Maintainability Attributes},
	year = {2017},
	note = {"we conducted a large-scale empirical study to measure
the application of software testing in the open source community"

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

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

data url: https://goo.gl/Mc7tHk},
	month = {05/2017},
	pages = {391-401},
	abstract = {Test case maintainability is an important concern,
especially in open source and distributed development environments
where projects typically have high contributor turnover
with varying backgrounds and experience, and where code
ownership changes often. Similar to design patterns, patterns
for unit testing promote maintainability quality attributes such
as ease of diagnoses, modifiability, and comprehension. In this
paper, we report the results of a large-scale study on the usage
of four xUnit testing patterns which can be used to satisfy these
maintainability attributes. This is a first-of-its-kind study which
developed automated techniques to investigate these issues across
82,447 open source projects, and the findings provide more insight
into testing practices in open source projects. Our results indicate
that only 17\% of projects had test cases, and from the 251
testing frameworks we studied, 93 of them were being used.
We found 24\% of projects with test files implemented patterns
that could help with maintainability, while the remaining did
not use these patterns. Multiple qualitative analyses indicate that
usage of patterns was an ad-hoc decision by individual developers,
rather than motivated by the characteristics of the project, and
that developers sometimes used alternative techniques to address
maintainability concerns.},
	keywords = {maintenance, mining software repositories, msr, Unit Test Frameworks, Unit Test Patterns, Unit Testing},
	author = {Danielle Gonzalez and Joanna C.S. Santos and Andrew Popovich and Mehdi Mirakhorli and Mei Nagappan}
}
@proceedings {1893,
	title = {The Open Source Officer Role {\textendash} Experiences},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {55-59},
	publisher = {Springer},
	abstract = {This papers describe the Open Source Officer role and the experiences from introducing this role in several companies. We outline the role description, main responsibilities, and interfaces to other roles and organizations. We investigated the role in several organization and bring interesting discrepancies and overlaps of how companies operate with OSS.

},
	keywords = {governance, inner source, maturity models},
	doi = {10.1007/978-3-319-57735-7_6},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_6},
	author = {Mols, CE and Wnuk, K and Lin{\r a}ker, J}
}
@proceedings {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 {1897,
	title = {Understanding the Effects of Practices on KDE Ecosystem Health},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {89-100},
	publisher = {Springer},
	abstract = {Open source software ecosystems have adjusted and evolved a set of practices over the years to support the delivery of sustainable software. However, few studies have investigated the impacts of such practices on the health of these ecosystems. In this paper, we present the results of an ethnographic-based study conducted during the Latin-American KDE users and contributors meeting (LaKademy 2015) with the goal of collecting practices used within the KDE ecosystem and understanding how they affect ecosystem health. The analysis was based on softgoal interdependency graphs adapted to represent practices and relate them to non-functional requirements and goals. Our results provide a preliminary insight to understand how KDE ecosystem community interacts, which working practices have been adopted and how they affect ecosystem health.

},
	keywords = {Ethnographic studies, Open source software ecosystems, Software ecosystem health, Software practices},
	doi = {10.1007/978-3-319-57735-7_10},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_10},
	author = {Simone da Silva Amorim and John D. McGregor and Eduardo Santana de Almeida and Christina von Flach Garcia Chavez}
}
@proceedings {1900,
	title = {Understanding When to Adopt a Library: A Case Study on ASF Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {128-138},
	publisher = {Springer},
	abstract = {Software libraries are widely used by both industrial and open source client projects. Ideally, a client user of a library should adopt the latest version that the library project releases. However, sometimes the latest version is not better than a previous version. This is because the latest version may include additional developer effort to test and integrate all changed features. In this study, our main goal is to better understand the relationship between adoption of library versions and its release cycle. Specifically, we conducted an empirical study of release cycles for 23 libraries and how they were adopted by 415 Apache Software Foundation (ASF) client projects. Our findings show that software projects are quicker to update earlier rapid-release libraries compared to library projects with a longer release cycle. Moreover, results suggest that software projects are more likely to adopt the latest version of a rapid-release library compared to libraries with a longer release cycles.},
	keywords = {adoption, apache, apache software foundation, libraries},
	doi = {10.1007/978-3-319-57735-7_13},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_13},
	author = {Ihara, Akinori and Daiki Fujibayashi and Hirohiko Suwa and Raula Gaikovina Kula and Kenichi Matsumoto}
}
@proceedings {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}
}
@inbook {Murphy2016,
	title = {Classifying Organizational Adoption of Open Source Software: A Proposal},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {123{\textendash}133},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Classifying Organizational Adoption of Open Source Software: A Proposal},
	address = {Cham},
	abstract = {Staged adoption models are a common feature of information systems (IS) adoption literature, yet these are rarely used in open source software (OSS) adoption studies. In this paper, a staged model for classifying the organizational adoption of OSS is proposed, based upon a critical review of existing staged adoption models and factors identified from OSS adoption literature. Innovations in the proposed model include: defined transition pathways between stages, additional stages and a decomposition of cessation of use into four distinct pathways.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_10},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_10},
	author = {Murphy, Stephen and Cox, Sharon},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@proceedings {1866,
	title = {Does the Task Structure of Open Source Projects Matter? Superposition and Value Creation},
	year = {2016},
	month = {11/2016},
	publisher = {AIS},
	abstract = {Collaboration through open superposition describes a process of building free (libre) and open source software (FLOSS), wherein motivationally independent layers of work is sequentially added one-on-top the other over time. This research-in-progress paper theorizes the mechanisms through which superposition influences the value of individual and organizational owned FLOSS projects. We argue for a non-linear relationship between degree of superposition and value of the FLOSS project. Moreover, we posit that the type of ownership will moderate this non-linear relationship. The moderation effect is such that {\textendash} (1) organizational ownership mitigates the influence of degree of superposition on project value (2) under organizational ownership, the optimal value of degree of superposition (the point at which the project value is maximum) is lower as compared to individual owned projects. This research attempts to advance the theory of superposition and unearth the influence of task structure on the value of the FLOSS project.},
	author = {Poonacha K. Medappa and Shirish C. Srivastava}
}
@article {kazman2016evaluating,
	title = {Evaluating the Effects of Architectural Documentation: A Case Study of a Large Scale Open Source Project},
	journal = {IEEE Transactions on Software Engineering},
	volume = {42},
	number = {3},
	year = {2016},
	pages = {220{\textendash}260},
	publisher = {IEEE},
	abstract = {Sustaining large open source development efforts requires recruiting new participants; however, a lack of
architectural documentation might inhibit new participants since large amounts of project knowledge are unavailable to
newcomers. We present the results of a multitrait, multimethod analysis of the effects of introducing architectural documentation
into a substantial open source project{\textemdash}the Hadoop Distributed File System (HDFS). HDFS had only minimal architectural
documentation, and we wanted to discover whether the putative benefits of architectural documentation could be observed over
time. To do this, we created and publicized an architecture document and then monitored its usage and effects on the project.
The results were somewhat ambiguous: by some measures the architecture documentation appeared to effect the project but
not by others. Perhaps of equal importance is our discovery that the project maintained, in its web-accessible JIRA archive of
software issues and fixes, enough architectural discussion to support architectural thinking and reasoning. This {\textquotedblleft}emergent{\textquotedblright}
architecture documentation served an important purpose in recording core project members{\textquoteright} architectural concerns and
resolutions. However, this emergent architecture documentation did not serve all project members equally well; it appears that
those on the periphery of the project{\textemdash}newcomers and adopters{\textemdash}still require explicit architecture documentation, as we will
show.},
	author = {Kazman, Rick and Goldenson, Dennis and Monarch, Ira and Nichols, William and Valetto, Giuseppe}
}
@proceedings {1826,
	title = {How Software Developers Use Work Breakdown Relationships in Issue Repositories},
	year = {2016},
	month = {05/2016},
	pages = {281-285},
	abstract = {Software developers use issues as a means to describe a range
of activities to be undertaken on a software system, including
features to be added and defects that require fixing. When
creating issues, software developers expend manual effort
to specify relationships between issues, such as one issue
blocking another or one issue being a sub-task of another.
In particular, developers use a variety of relationships to express
how work is to be broken down on a project. To better
understand how software developers use work breakdown relationships
between issues, we manually coded a sample of
work breakdown relationships from three open source systems.
We report on our findings and describe how the recognition
of work breakdown relationships opens up new ways
to improve software development techniques.},
	doi = {http://dx.doi.org/10.1145/2901739.2901779},
	author = {C. Albert Thompson and Murphy, Gail C. and Palyart, Marc and Marko Ga{\v s}paric}
}
@inbook {Hirao2016,
	title = {The Impact of a Low Level of Agreement Among Reviewers in a Code Review Process},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {97{\textendash}110},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Software code review systems are commonly used in software development. In these systems, many patches are submitted to improve the quality. To verify the quality, voting is commonly used by contributors; however, there still exists a major problem, namely, that reviewers do not always simply reach a broad agreement. In our previous study, we found that consensus is not usually reached, implying that an individual reviewer{\textquoteright}s final decision usually differs from that of the majority of the other reviewers. In this study, we further investigate the reasons why such situations often occur, and provide suggestions for better handling of these problems. Our analysis of the Qt and OpenStack project datasets allow us to suggest that a patch owner should select more appropriate reviewers who often agree with others{\textquoteright} decisions.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_8},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_8},
	author = {Hirao, Toshiki and Ihara, Akinori and Ueda, Yuki and Phannachitta, Passakorn and Matsumoto, Ken-ichi},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {M{\"a}enp{\"a}{\"a}2016,
	title = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {134{\textendash}146},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {In-between Open and Closed - Drawing the Fine Line in Hybrid Communities},
	address = {Cham},
	abstract = {Today, the community driven development model extends into a variety of new, often web based collaborations. Among these are hybrid open source development set ups in which various online tools are used to facilitate cooperation between virtual teams of commercial and voluntary stakeholders. As yet, how these relationships form and evolve is not understood extensively. This article presents a longitudinal case study of a smartphone startup that founded its early product development strategy on reliance on feedback from its customers through a web based question and answer forum. With this, the company managed to extend values typical for open source communities to support development of its proprietary software. Our main findings include that the challenge in similar settings lies in striking the right balance between the open and the proprietary {\textendash} while overt openness may risk the competitive advantage of a company, leaving too much behind closed boundaries can create unnecessary friction in the relationship.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_11},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_11},
	author = {M{\"a}enp{\"a}{\"a}, Hanna and Kilamo, Terhi and M{\"a}nnist{\"o}, Tomi},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@article {Kazuhiro Yamashita2016,
	title = {Magnet or Sticky? Measuring Project Characteristics from the Perspective of Developer Attraction and Retention},
	journal = {Journal of Information Processing},
	volume = {24},
	number = {2},
	year = {2016},
	pages = {339-348},
	abstract = {Open Source Software (OSS) is vital to both end users and enterprises. As OSS systems are becoming a type of infrastructure, long-term OSS projects are desired. For the survival of OSS projects, the projects need to not only retain existing developers, but also attract new developers to grow. To better understand how projects retain and attract contributors, our preliminary study aimed to measure the personnel attraction and retention of OSS projects using a pair of population migration metrics, called Magnet (personnel attraction) and Sticky (retention) metrics. Because the preliminary study analyzed only 90 projects and the 90 projects are not representative of GitHub, this paper extend the preliminary study to better understand the generalizability of the results by analyzing 16, 552 projects of GitHub. Furthermore, we also add a pilot study to investigate the typical duration between releases to find more appropriate release duration. The study results show that (1) approximately 23\% of developers remain in the same projects that the developers contribute to, (2) the larger projects are likely to attract and retain more developers, (3) 53\% of terminal projects eventually decay to a state of fewer than ten developers and (4) 55\% of attractive projects remain in an attractive category.
},
	keywords = {github, retention},
	doi = {10.2197/ipsjjip.24.339},
	url = {https://www.jstage.jst.go.jp/article/ipsjjip/24/2/24_339/_article},
	author = {Yamashita, Kazuhiro and Kamei, Yasutaka and McIntosh, Shane and Hassan, Ahmed E. and Ubayashi, Naoyasu}
}
@inbook {L{\'o}pez2016,
	title = {OSSAP {\textendash} A Situational Method for Defining Open Source Software Adoption Processes},
	booktitle = {Advanced Information Systems Engineering: 28th International Conference, CAiSE 2016, Ljubljana, Slovenia, June 13-17, 2016. Proceedings},
	year = {2016},
	pages = {524{\textendash}539},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	address = {Cham},
	abstract = {Organizations are increasingly becoming Open Source Software (OSS) adopters, either as a result of a strategic decision or just as a consequence of technological choices. The strategy followed to adopt OSS shapes organizations{\textquoteright} businesses; therefore methods to assess such impact are needed. In this paper, we propose OSSAP, a method for defining OSS Adoption business Processes, built using a Situational Method Engineering (SME) approach. We use SME to combine two well-known modelling methods, namely goal-oriented models (using i*) and business process models (using BPMN), with a pre-existing catalogue of goal-oriented OSS adoption strategy models. First, we define a repository of reusable method chunks, including the guidelines to apply them. Then, we define OSSAP as a composition of those method chunks to help organizations to improve their business processes in order to integrate the best fitting OSS adoption strategy. We illustrate it with an example of application in a telecommunications company.
},
	isbn = {978-3-319-39696-5},
	doi = {10.1007/978-3-319-39696-5_32},
	url = {http://dx.doi.org/10.1007/978-3-319-39696-5_32},
	author = {L{\'o}pez, Lidia and Costal, Dolors and Ralyt{\'e}, Jolita and Franch, Xavier and M{\'e}ndez, Luc{\'\i}a and Annosi, Maria Carmela},
	editor = {Nurcan, Selmin and Soffer, Pnina and Bajec, Marko and Eder, Johann}
}
@conference {1874,
	title = {Towards Developing a Theory of Toxicity in the Context of Free/Open Source Software \& Peer Production Communities},
	year = {2016},
	abstract = {Information technology usage has positive aspects, but it has been acknowledged that there also exist negative ones that must be studied in more depth. Behaviors such as teasing and abusing are a main concern for Free/Open Source Software (FOSS) and peer production project leaders. Indeed, they have recurrently used the words "toxic" and "poison" to qualify behaviors threatening their communities{\textquoteright} survival. Community health has been defined as the extent to which the vital systems of an online community are continuously performing normally. This definition is based on the metaphor of "online community as a living organism" , which brings the focus on the inner workings of communities and is particularly suited to study behaviors occurring within it. In this research project, we mobilize this organismic metaphor and borrow ideas from the Toxicology discipline to develop a theory of toxicity in FOSS and \& peer production communities. There has been a substantial amount of research attention on {\textquoteright}toxic{\textquoteright} and {\textquoteright}poisonous{\textquoteright} behaviors at the individual level of analysis. Nonetheless, the higher-level concern of their interplay and implications on the life and health of FOSS/peer production communities, is still vastly unexplored. We would like to partake to the SIGOPEN 2016 Developmental Workshop for Openness Research to help us move our work forward with the ultimate objective to develop a theory of toxicity in the context of FOSS and peer production projects. },
	url = {https://www.researchgate.net/publication/311672787_Towards_Developing_a_Theory_of_Toxicity_in_the_Context_of_FreeOpen_Source_Software_Peer_Production_Communities},
	author = {Carillo, Kevin Daniel Andre and Josianne Marsan and Bogdan Negoita Warwick}
}
@article {1802,
	title = {Candoia: A Platform and an Ecosystem for Building and Deploying Versatile Mining Software Repositories Tools},
	year = {2015},
	note = {" In terms of its focus,
the Candoia platform is closer to Bevan et al.{\textquoteright}s Kenyon [9],
Bajracharya et al.{\textquoteright}s Sourcerer [6], Gousios and Spinellis{\textquoteright}s Alitheia
Core [32, 31], Howison et al.{\textquoteright}s FLOSSMole [39] and different from
Boetticher et al.{\textquoteright}s PROMISE Repository [69], Gonz{\'a}lez-Barahona
and Robles{\textquoteright}s open-access data repositories [29], Black Duck OpenHub
(aka Ohloh) [13], GHTorrent [30, 33], Ossher et al.{\textquoteright}s SourcererDB
[64], the SourceForge Research Data Archive (SRDA) [28],
and Boa [25]. },
	month = {11/2015},
	institution = {Iowa State University},
	abstract = {Research on mining software repositories (MSR) has shown great
promise during the last decade in solving many challenging software
engineering problems. There exists, however, a {\textquoteleft}valley of death{\textquoteright}
between these significant innovations in the MSR research and their
deployment in practice. The significant cost of converting a prototype
to software; need to provide support for a wide variety of tools
and technologies e.g. CVS, SVN, Git, Bugzilla, Jira, Issues, etc,
to improve applicability; and the high cost of customizing tools to
practitioner-specific settings are some key hurdles in transition to
practice. We describe Candoia, a platform and an ecosystem that
is aimed at bridging this valley of death between innovations in
MSR research and their deployment in practice. We have implemented
Candoia and provide facilities to build and publish MSR
ideas as Candoia apps. Our evaluation demonstrates that Candoia
drastically reduces the cost of converting an idea to an app, thus
reducing the barrier to transitioning research findings into practice.
We also see versatility, in Candoia app{\textquoteright}s ability to work with a variety
of tools and technologies that the platform supports. Finally,
we find that customizing Candoia app to fit project-specific needs
is often well within the grasp of developers.},
	keywords = {Analysis of software and its evolution, Application specific development environments, flossmole cited, msr, research to practice, software evolution, software repositories},
	url = {http://lib.dr.iastate.edu/cgi/viewcontent.cgi?article=1378\&context=cs_techreports},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Candoia-\%20A\%20Platform\%20and\%20an\%20Ecosystem\%20for\%20Building\%20and\%20Deploying\%20V.pdf},
	author = {Nitin M. Tiwari and Dalton D. Mills and Ganesha Upadhyaya and Eric Lin and Rajan, Hridesh}
}
@conference {Hata:2015:CSO:2819321.2819325,
	title = {Characteristics of Sustainable OSS Projects: A Theoretical and Empirical Study},
	booktitle = {Proceedings of the Eighth International Workshop on Cooperative and Human Aspects of Software Engineering},
	series = {CHASE {\textquoteright}15},
	year = {2015},
	note = {Slideshare: http://www.slideshare.net/hideakihata5/characteristics-of-sustainable-oss-projects-a-theoretical-and-empirical-study},
	pages = {15{\textendash}21},
	publisher = {IEEE Press},
	organization = {IEEE Press},
	address = {Piscataway, NJ, USA},
	abstract = {How can we attract developers? What can we do to incentivize developers to write code? We started the study by introducing the population pyramid visualization to software development communities, called software population pyramids, and found a typical pattern in shapes. This pattern comes from the differences in attracting coding contributors and discussion contributors. To understand the causes of the differences, we then build game-theoretical models of the contribution situation. Based on these results, we again analyzed the projects empirically to support the outcome of the models, and found empirical evidence. The answers to the initial questions are clear. To incentivize developers to code, the projects should prepare documents, or the projects or third parties should hire developers, and these are what sustainable projects in GitHub did in reality. In addition, making innovations to reduce the writing costs can also have an impact in attracting coding contributors.},
	url = {http://dl.acm.org/citation.cfm?id=2819321.2819325},
	author = {Hata, Hideaki and Todo, Taiki and Onoue, Saya and Kenichi Matsumoto}
}
@proceedings {1763,
	title = {A Dataset of High Impact Bugs: Manually-Classified Issue Reports},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The importance of supporting test and maintenance
activities in software development has been increasing, since
recent software systems have become large and complex. Although
in the field of Mining Software Repositories (MSR) there
are many promising approaches to predicting, localizing, and
triaging bugs, most of them do not consider impacts of each
bug on users and developers but rather treat all bugs with equal
weighting, excepting a few studies on high impact bugs including
security, performance, blocking, and so forth. To make MSR
techniques more actionable and effective in practice, we need
deeper understandings of high impact bugs. In this paper we
introduced our dataset of high impact bugs which was created
by manually reviewing four thousand issue reports in four open
source projects (Ambari, Camel, Derby and Wicket).},
	keywords = {ambari, camel, derby, wicket},
	url = {http://oss.sys.wakayama-u.ac.jp/publications/pman3.cgi?DOWNLOAD=141},
	attachments = {https://flosshub.org/sites/flosshub.org/files/5594a518.pdf},
	author = {Ohira, Masao and Yutaro Kashiwa and Yosuke Yamatani and Hayato Yoshiyuki and Yoshiya Maeda and Nachai Limsettho and Keisuke Fujino and Hata, Hideaki and Ihara, Akinori and Kenichi Matsumoto}
}
@proceedings {1772,
	title = {An Empirical Study of Architectural Change in Open-Source Software Systems},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {From its very inception, the study of software
architecture has recognized architectural decay as a regularly
occurring phenomenon in long-lived systems. Architectural decay
is caused by repeated changes to a system during its lifespan.
Despite decay{\textquoteright}s prevalence, there is a relative dearth of empirical
data regarding the nature of architectural changes that may lead
to decay, and of developers{\textquoteright} understanding of those changes. In
this paper, we take a step toward addressing that scarcity by
conducting an empirical study of changes found in software
architectures spanning several hundred versions of 14 opensource
systems. Our study reveals several new findings regarding
the frequency of architectural changes in software systems, the
common points of departure in a system{\textquoteright}s architecture during
maintenance and evolution, the difference between system-level
and component-level architectural change, and the suitability
of a system{\textquoteright}s implementation-level structure as a proxy for its
architecture.},
	keywords = {architectural change, architecture recovery, open-source systems, software architecture, software evolution},
	url = {http://softarch.usc.edu/~pooyan/publications/emparch_msr15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/emparch_msr15.pdf},
	author = {Duc Minh Le and Pooyan Behnamghader and Joshua Garcia{\textdaggerdbl} Daniel Link and Arman Shahbazian and Nenad Medvidovic}
}
@article {1746,
	title = {Evaluation of FLOSS by Analyzing Its Software Evolution:},
	journal = {Journal of Information Technology Research},
	volume = {8},
	year = {2015},
	month = {01/2015},
	pages = {62 - 81},
	abstract = {In today{\textquoteright}s world, management often rely on FLOSS (Free/Libre/Open Source Software) systems to run their organizations. However, the nature of FLOSS is different from the software they have been using in the last decades. Its development model is distributed, and its authors are diverse as many volunteers and companies may collaborate in the project. In this paper, we want to shed some light on how to evaluate a FLOSS system by looking at the Moodle platform, which is currently the most used learning management system among educational institutions worldwide. In contrast with other evaluation models that have been proposed so far, the one we present is based on retrieving historical information that can be obtained publicly from the Internet, allowing us to study its evolution. As a result, we will show how by using our methodology management can take informed decisions that lower the risk that organizations face when investing in a FLOSS system.  },
	keywords = {free software, LMS, moodle, open source, software engineering, software evaluation, software evolution},
	issn = {1938-7865},
	doi = {10.4018/JITR.2015010105},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Evaluation\%20of\%20FLOSS\%20by\%20Analyzing\%20its\%20Software\%20Evolution\%20-\%20An\%20Example\%20Using\%20the\%20Moodle\%20Platform.pdf},
	author = {Macho, H{\'e}ctor J. and Gregorio Robles and Gonz{\'a}lez-Barahona, Jesus M}
}
@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}
}
@proceedings {1771,
	title = {A Historical Analysis of Debian Package Incompatibilities},
	year = {2015},
	abstract = {Users and developers of software distributions are often confronted with installation problems due to conflicting packages. A prototypical example of this are the Linux distributions such as Debian. Conflicts between packages have been studied under different points of view in the literature, in particular for the Debian operating system, but little is known about how these package conflicts evolve over time. This article presents an extensive analysis of the evolution of package incompatibilities, spanning a decade of the life of the Debian stable and testing distributions for its most popular architecture, i386. Using the technique of survival analysis, this empirical study sheds some light on the origin and evolution of package incompatibilities, and provides the basis for building indicators that may be used to improve the quality of package-based distributions.
},
	url = {http://di.umons.ac.be/details.aspx?pub=b5a887bd-0612-4439-8f66-ec37803a32db},
	author = {Claes Maelick and Mens Tom and Di Cosmo Robert and Vouillon Jerome}
}
@proceedings {1769,
	title = {Investigating Code Review Practices in Defective Files: An Empirical Study of the Qt System},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Software code review is a well-established software
quality practice. Recently, Modern Code Review (MCR) has been
widely adopted in both open source and proprietary projects.
To evaluate the impact that characteristics of MCR practices
have on software quality, this paper comparatively studies MCR
practices in defective and clean source code files. We investigate
defective files along two perspectives: 1) files that will eventually
have defects (i.e., future-defective files) and 2) files that have
historically been defective (i.e., risky files). Through an empirical
study of 11,736 reviews of changes to 24,486 files from the Qt
open source project, we find that both future-defective files and
risky files tend to be reviewed less rigorously than their clean
counterparts. We also find that the concerns addressed during
the code reviews of both defective and clean files tend to enhance
evolvability, i.e., ease future maintenance (like documentation),
rather than focus on functional issues (like incorrect program
logic). Our findings suggest that although functionality concerns
are rarely addressed during code review, the rigor of the
reviewing process that is applied to a source code file throughout
a development cycle shares a link with its defect proneness.},
	keywords = {code review, software quality},
	url = {http://sail.cs.queensu.ca/publications/pubs/msr2015-thongtanunam.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015-thongtanunam.pdf},
	author = {Patanamon Thongtanunam and McIntosh, Shane and Hassan, Ahmed E. and Hajimu Iida}
}
@proceedings {1785,
	title = {An Investigation of Migrating from Proprietary RTOS to Embedded Linux},
	year = {2015},
	month = {08/2015},
	abstract = {Embedded systems and the open source operating system
Linux have been going hand in hand for a long time now.
Companies using Linux for their embedded products are
praising it for being time and cost efficient when it comes to
performance and maintainability. Another solution for embedded
systems is a Real-Time Operating System (RTOS).
The goal of this this paper is to investigate whether a traditional
proprietary RTOS can be substituted with embedded
Linux, and if this kind of migration can lead to reduced licensing
costs and increased general quality of the system.
We used a qualitative research method for this case-study.
The investigation was conducted with interviews as the main
source of information. The result of this study is an empirical
model we named {\textquoteright}Embedded Linux Adoption Model{\textquoteright}.
We concluded that in many cases a proprietary RTOS can
be substituted with embedded Linux without affecting the
critical needs of the system. The study also showed that
many embedded system developers are very receptive to
open source solutions and could think of contributing to the
community.},
	url = {http://www.opensym.org/os2015/proceedings-files/p101-muchow.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p101-muchow.pdf},
	author = {Oscar Muchow and David Ustarbowski and Hammouda, Imed}
}
@proceedings {1790,
	title = {Measuring the Crowd {\textendash} A Preliminary Taxonomy of Crowdsourcing Metrics},
	year = {2015},
	month = {08/2015},
	abstract = {Crowdsourcing initiatives benefit from tapping into diversity. A
vast plethora of disparate individuals, organizations, frameworks
and skillsets can all play a role in sourcing solutions to a
challenge. Nevertheless, while crowdsourcing has become a
pervasive phenomenon, there is a paucity of research that
addresses how the crowdsourcing process is measured. Whereas
research has advanced various taxonomies of crowdsourcing none
to date have specifically addressed the issue of measuring either
specific stages of the crowdsourcing process or the process as a
whole. As a first step towards achieving this goal, this research-inprogress
paper examines crowdsourcing at the operational level
with a view towards (i) identifying the parts of the process (ii)
identifying what can be measured and (iii) categorising
operational metrics to facilitate deployment in practice. The
taxonomy advanced is overarching in nature and can be deployed
across disciplines. Furthermore, the preliminary taxonomy
presented will offer practitioners a comprehensive list of metrics
that will enable them to facilitate comparison across various
crowdsourcing initiatives.},
	url = {http://www.opensym.org/os2015/proceedings-files/p200-cullina.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p200-cullina.pdf},
	author = {Eoin Cullina and Kieran Conboy and Morgan, Lorraine}
}
@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 {1751,
	title = {Mining Energy-Aware Commits},
	year = {2015},
	month = {05/2015},
	abstract = {Over the last years, energy consumption has become
a first-class citizen in software development practice. While
energy-efficient solutions on lower-level layers of the software
stack are well-established, there is convincing evidence that even
better results can be achieved by encouraging practitioners to
participate in the process. For instance, previous work has shown
that using a newer version of a concurrent data structure can
yield a 2.19x energy savings when compared to the old associative
implementation [75]. Nonetheless, little is known about how much
software engineers are employing energy-efficient solutions in
their applications and what solutions they employ for improving
energy-efficiency. In this paper we present a qualitative study
of {\textquotedblleft}energy-aware commits{\textquotedblright}. Using Github as our primary data
source, we perform a thorough analysis on an initial sample of
2,189 commits and carefully curate a set of 371 energy-aware
commits spread over 317 real-world non-trivial applications.
Our study reveals that software developers heavily rely on lowlevel
energy management approaches, such as frequency scaling
and multiple levels of idleness. Also, our findings suggest that
ill-chosen energy saving techniques can impact the correctness
of an application. Yet, we found what we call {\textquotedblleft}energy-aware
interfaces{\textquotedblright}, which are means for clients (e.g., developers or endusers)
to save energy in their applications just by using a function,
abstracting away the low-level implementation details.},
	url = {http://gustavopinto.org/lost+found/msr2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/energy.pdf},
	author = {Irineu Moura and Pinto, Gustavo and Felipe Ebert and Fernando Castor}
}
@proceedings {1791,
	title = {Open Innovation for Innovation Tools: the Case of Co-Design Platforms},
	year = {2015},
	month = {08/2015},
	abstract = {This paper explores the dynamics of openness and enclosure of
innovation activities with IT artifacts on the example of co-design
platforms. While modern information and communication technologies
offer many new possibilities for innovation, they also
subject innovation to the underlying technical structures, which
can misdirect the activities on the platform. In order to avoid this,
we propose an open innovation approach for open innovation
solutions. We perform an empirical study on two co-design platforms
which become subjects of innovation themselves in an open
laboratory in the downtown area of a European city. Visitors to
the laboratory are allowed to engage in innovate activities regarding
the co-design platforms in whatever way they want. The results
show that they do not only address technical improvements
of the platforms, but also look into new directions to make the
platforms more relevant or to replace them by other ways of innovating
in the given contexts.},
	url = {http://www.opensym.org/os2015/proceedings-files/p201-fritzsche.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p201-fritzsche.pdf},
	author = {Albrecht Fritzsche and Angela Roth and Kathrin Moslein}
}
@inbook {1740,
	title = {The RISCOSS Platform for Risk Management in Open Source Software Adoption},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {124-133},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Managing risks related to OSS adoption is a must for organizations that need to smoothly integrate OSS-related practices in their development processes. Adequate tool support may pave the road to effective risk management and ensure the sustainability of such activity. In this paper, we present the RISCOSS platform for managing risks in OSS adoption. RISCOSS builds upon a highly configurable data model that allows customization to several types of scopes. It implements two different working modes: exploration, where the impact of decisions may be assessed before making them; and continuous assessment, where risk variables (and their possible consequences on business goals) are continuously monitored and reported to decision-makers. The blackboard-oriented architecture of the platform defines several interfaces for the identified techniques, allowing new techniques to be plugged in.
},
	keywords = {Open source adoption, Open Source Projects, open source software, OSS, Risk Management, Software platform},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_12},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_12},
	author = {Franch, X. and Kenett, R. and Mancinelli, F. and Susi, A. and Ameller, D. and Annosi, M.C. and Ben-Jacob, R. and Blumenfeld, Y. and Franco, O.H. and Gross, D. and Lopez, L. and Morandini, M. and Oriol, M. and Siena, A.},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1739,
	title = {Surveying the Adoption of FLOSS by Public Administration Local Organizations},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {114-123},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Background. The introduction of Open Source Software technologies in the Public Administration plays a key role in the spread of Open Source Software. The state of the art in the adoption of Open Source Software solutions in the Public Administration is not very well known even in areas like Lombardy, which is Italy{\textquoteright}s largest and most developed region.
Goal. The goal of the investigation documented in this paper is to obtain a clear picture about the introduction of Open Source Software technologies in the Public Administration, the obstacles to their adoption, and the willingness of stakeholders to proceed with their introduction.
Method. We carried out a qualitative and quantitative survey that was submitted to a representative part of the Public Administrations in Lombardy.
Results. The analysis of the qualitative and quantitative information shows that several Public Administrations are already using Open Source Software technologies, though not in all application areas. The savings are one frequently cited incentive to the adoption of Open Source Software. However, one obstacle is the fact that a comprehensive law on software in the Public Administration has not yet been approved.
Conclusions. Our analysis provides results that indicate a common understanding of incentives, obstacles, and opportunities for Open Source Software technologies in Public Administrations.},
	keywords = {FLOSS adoption, Italy, Public administrations, Survey},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_11},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_11},
	author = {Tosi, Davide and Lavazza, Luigi and Morasca, Sandro and Chiappa, Marco},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1736,
	title = {A Systematic Approach for Evaluating BPM Systems: Case Studies on Open Source and Proprietary Tools},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {81-90},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Business Process Management Systems (BPMS) provide support for modeling, developing, deploying, executing and evaluating business processes in an organization. Selecting a BPMS is not a trivial task, not only due to the many existing alternatives, both in the open source and proprietary realms, but also because it requires a thorough evaluation of its capabilities, contextualizing them in the organizational environment in which they will be used. In this paper we present a methodology to guide the systematic evaluation of BPMS that takes into account the specific needs of each organization. It provides a list of key characteristics of BPMS which are ranked by the organization and evaluated using test cases and quantitative criteria. We also present case studies of open source and proprietary BPMS evaluations following our proposal.
},
	keywords = {Business Process Management Systems (BPMS), Evaluation methodology, Open source and proprietary BPMS, Systematic approach},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_8},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_8},
	author = {Delgado, Andrea and Calegari, Daniel and Milanese, Pablo and Falcon, Renatta and Garc{\'\i}a, Esteban},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1742,
	title = {On the Variability of the BSD and MIT Licenses},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {146-156},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {The MIT/X11 and the BSD are two of the most important family of Free and Open Source (FOSS) licenses. Because these licenses are to be inserted into the files that use it, and because they are expected to be changed by those who use them, their text has suffered alterations over time. Some of this variability is the result of licenses containing template fields which allow the license to be customized to include information such as the copyright holder name. Other variability can be attributed to changes in spelling, punctuation, and adding or removing conditions. This study empirically evaluated the extent that the BSD and MIT/X11 family of licenses are varied, and the manner and frequency in which license texts vary from the original definition. The study found that the BSD family has little variability, with a significant proportion fitting the common standard. The MIT/X11 family of licenses exhibited significantly more variation, with a higher propensity to customize the license text. In addition, the MIT/X11 license has spawned several specialized variants which likely constitute different legal meanings. Based on these findings, recommendations are proposed on what variability needs to be accommodated by the Software Package Data Exchange (SPDX) which is in the process of standardizing the allowed variability of both licenses.
},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_14},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_14},
	author = {Maryka, Trevor and German, DanielM. and Poo-Caama{\~n}o, Germ{\'a}n},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@article {1686,
	title = {Why and How Should Open Source Projects Adopt Time-Based Releases?},
	journal = {IEEE Software, 32(2)},
	year = {2015},
	abstract = {Traditional release strategies have a number of associated problems, which can be overcome by time-based release management. We present findings from interviews with key members of seven prominent volunteer-based open source projects, all of which have adopted a time-based release strategy. We discuss the importance of release planning, the numerous challenges that can result from a lack of such planning, and the benefits of time-based releases. Finally, we discuss how an open source project can adopt a time-based release strategy.},
	url = {https://www.researchgate.net/publication/268815678_Why_and_How_Should_Open_Source_Projects_Adopt_Time-Based_Releases},
	author = {Martin Michlmayr and Fitzgerald, Brian}
}
@inbook {1596,
	title = {Adapting SCRUM to the Italian Army: Methods and (Open) Tools},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {61-69},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Many software-related technologies, including software development methodologies, quality models, etc. have been developed due to the huge software needs of the Department of Defense (DoD) of the United States. Therefore, it is not surprising that the DoD is promoting open source software and agile approaches into the development processes of the defense contractors. The quality of many open source product has been demonstrated to be comparable to the close source ones and in many cases even higher and the effectiveness of agile approaches has been demonstrated in many industrial settings. Moreover, the availability of the source code makes open source products attractive for obvious reasons (e.g., security, long term maintenance, etc.). Following this trend, also the Italian Army has started using open source software and promotes its usage into the development processes of its contractors, also promoting agile approaches in many contexts focusing on the SCRUM methodology. This paper provides an overview of the SCRUM development process adopted by the Italian Army for the development of software systems using open source technologies.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_7},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_7},
	author = {Cotugno, FrancoRaffaele and Messina, Angelo},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1614,
	title = {The Agile Management of Development Projects of Software Combining Scrum, Kanban and Expert Consultation},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {176-180},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

At the University of Informatics Sciences (UCI), Havana, Cuba, it is found The Center of Free Solutions of Software (CESOL) who has an informatic project named {\textquotedblleft}Auditing of Source Code{\textquotedblright} (ACF). This project has as objective to develop an open source software solution to auditing the source code of several software solutions with an agile projects management. In the present investigation have been showed the experiences obtained in the mixed application of two methods of agile projects management; Kanban and Scrum, together with the method Judgment of Expert, during the stage of construction of the lifecycle of ACF, when it is was performed a quality auditing by specialists of the CALISOFT company. In the auditing were detected several errors and to resolve them was necessary to estimate efforts, time and to revalue the lifecycle of the project. Moreover, the investigation show how this method can be used as a guide for young project managers for a correct planification and how can be used as a personal organizational method.
},
	keywords = {Agile management of projects, kanban, scrum},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_25},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_25},
	author = {Febles Parker, MichelEvaristo and Monte, YusleydiFern{\'a}ndez},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@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.}
}
@inbook {1595,
	title = {Analyzing the Relationship between the License of Packages and Their Files in Free and Open Source Software},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {51-60},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {Free and Open Source Software (FOSS) is widely reused today. To reuse FOSS one must accept the conditions imposed by the software license under which the component is made available. This is complicated by the fact that often FOSS packages contain files from many licenses. In this paper we analyze the source code of packages in the Fedora Core Linux distribution with the goal of discovering the relationship between the license of a source package, and the license of the files it contains. For this purpose we create license inclusion graphs. Our results show that more modern reciprocal licenses such as the General Public License v3 tend to include files of less licenses than its previous versions, and that packages under an Apache License tend to contain only files under the same license.},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_6},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_6},
	author = {Manabe, Yuki and German, DanielM. and Inoue, Katsuro},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Mitropoulos:2014:BCM:2597073.2597123,
	title = {The Bug Catalog of the Maven Ecosystem},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {372{\textendash}375},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Examining software ecosystems can provide the research community with data regarding artifacts, processes, and communities. We present a dataset obtained from the Maven central repository ecosystem (approximately 265GB of data) by statically analyzing the repository to detect potential software bugs. For our analysis we used FindBugs, a tool that examines Java bytecode to detect numerous types of bugs. The dataset contains the metrics results that FindBugs reports for every project version (a JAR) included in the ecosystem. For every version we also stored specific metadata such as the JAR{\textquoteright}s size, its dependencies and others. Our dataset can be used to produce interesting research results, as we show in specific examples.
},
	keywords = {findbugs, Maven Repository, msr data showcase, Software Bugs},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597123},
	url = {http://doi.acm.org/10.1145/2597073.2597123},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mitro.pdf},
	author = {Mitropoulos, Dimitris and Vassilios Karakoidas and Louridas, Panos and Gousios, Georgios and Diomidis Spinellis}
}
@conference {Tymchuk:2014:COP:2597073.2597093,
	title = {Collaboration in Open-source Projects: Myth or Reality?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {304{\textendash}307},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {One of the fundamental principles of open-source projects is that they foster collaboration among developers, disregarding their geographical location or personal background. When it comes to software repositories collaboration is a rather ephemeral phenomenon which lacks a clear definition, and it must therefore be mined and modeled. This throws up the question whether what is mined actually maps to reality.

In this paper we investigate collaboration by modeling it using a number of diverse approaches that we then compare to a ground truth obtained by surveying a substantial set of developers of the Pharo open-source community. Our findings indicate that the notion of collaboration must be revisited, as it is undermined by a number of factors that are often tackled in imprecise ways or not taken into account at all.},
	keywords = {COLLABORATION, Software ecosystems},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597093},
	url = {http://doi.acm.org/10.1145/2597073.2597093},
	author = {Tymchuk, Yuriy and Mocci, Andrea and Lanza, Michele}
}
@inbook {1606,
	title = {Considerations Regarding the Creation of a Post-graduate Master{\textquoteright}s Degree in Free Software},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {123-132},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Free software has gained importance over the last few years, and can be found in almost any sphere in which {\textquoteleft}software processes{\textquoteright} are important. However, even when universities and higher education establishments include subjects concerning free programming and technologies in their curriculums, their graduates tend to attain limited technological, organisational and philosophical knowledge that limits them as regards their participation in, management and development of free software projects. This gap in skills and knowledge has recently led to a series of post-graduate studies whose objective is to offer students the possibility of acquiring competencies that will allow them to become experts in free software. This paper presents a study concerning the offers for post-graduate studies in free software that currently exist, with the intention of creating similar post-graduate studies in Ecuador.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_17},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_17},
	author = {Montes Le{\'o}n, SergioRa{\'u}l and Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}sM. and S{\'a}nchez C., LuisE.},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {1694,
	title = {Cream of the crop},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {In open content communities like Wikipedia and StackOverflow and in open source software projects, a small proportion of users produce a majority of the content and take on much of the required community maintenance work. Understanding this class of users is crucial to creating and sustaining healthy communities. We carried out a mixed-method study of core contributors to the Cyclopath geographic wiki and bicycle routing web site. We present our findings and organize our discussion using concepts from activity theory. We found that the Cyclopath core contributors aren{\textquoteright}t the dedicated cyclists and that the characteristics of the community shape the site, the rules, and the tools for contributing. Additionally, we found that numerous aspects about the surrounding ecology of related systems and communities may help to shape how the site functions and views itself. We draw implications for future research and design from these findings.
},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641609},
	author = {Katherine Panciera and Mikhil Masli and Loren Terveen}
}
@conference {Brunet:2014:DDD:2597073.2597115,
	title = {Do Developers Discuss Design?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {340{\textendash}343},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Design is often raised in the literature as important to attaining various properties and characteristics in a software system. At least for open-source projects, it can be hard to find evidence of ongoing design work in the technical artifacts produced as part of the development. Although developers usually do not produce specific design documents, they do communicate about design in different ways. In this paper, we provide quantitative evidence that developers address design through discussions in commits, issues, and pull requests. To achieve this, we built a discussions{\textquoteright} classifier and automatically labeled 102,122 discussions from 77 projects. Based on this data, we make four observations about the projects: i) on average, 25\% of the discussions in a project are about design; ii) on average, 26\% of developers contribute to at least one design discussion; iii) only 1\% of the developers contribute to more than 15\% of the discussions in a project; and iv) these few developers who contribute to a broad range of design discussions are also the top committers in a project.
},
	keywords = {Design Discussions, empirical study, machine learning, mining challenge, msr challenge},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597115},
	url = {http://doi.acm.org/10.1145/2597073.2597115},
	attachments = {https://flosshub.org/sites/flosshub.org/files/brunet.pdf},
	author = {Brunet, Jo{\~a}o and Murphy, Gail C. and Terra, Ricardo and Figueiredo, Jorge and Serey, Dalton}
}
@conference {Murgia:2014:DFE:2597073.2597086,
	title = {Do Developers Feel Emotions? An Exploratory Analysis of Emotions in Software Artifacts},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {262{\textendash}271},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software development is a collaborative activity in which developers interact to create and maintain a complex software system. Human collaboration inevitably evokes emotions like joy or sadness, which can affect the collaboration either positively or negatively, yet not much is known about the individual emotions and their role for software development stakeholders. In this study, we analyze whether development artifacts like issue reports carry any emotional information about software development. This is a first step towards verifying the feasibility of an automatic tool for emotion mining in software development artifacts: if humans cannot determine any emotion from a software artifact, neither can a tool. Analysis of the Apache Software Foundation issue tracking system shows that developers do express emotions (in particular gratitude, joy and sadness). However, the more context is provided about an issue report, the more human raters start to doubt and nuance their interpretation of emotions. More investigation is needed before building a fully automatic emotion mining tool.
},
	keywords = {Emotion Mining, Empirical Software Engineer- ing, Issue Report},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597086},
	url = {http://doi.acm.org/10.1145/2597073.2597086},
	attachments = {https://flosshub.org/sites/flosshub.org/files/murgia.pdf},
	author = {Murgia, Alessandro and Tourani, Parastou and Adams, Bram and Ortu, Marco}
}
@proceedings {1572,
	title = {Governance of Open Source Electronic Health Record Projects: A Successful Case of a Hybrid Model},
	year = {2014},
	month = {01/2014},
	pages = {2798-2807},
	publisher = {IEEE Computer Society},
	abstract = {Electronic Health Records (EHRs) are at the heart of most health system reforms. As an increasing number of hospitals are adopting open source EHRs and as many questions are still unanswered for potential adopters of open source EHRs, analyzing the governance of such systems has become important. Due to the increased diversity of sponsors and stakeholders of open source software (OSS) over the past few years, numerous governance models of OSS projects have emerged. In contrast to earlier {\textquotedblleft}community-managed{\textquotedblright} governance model s, these emergent models are characterized by the sponsorship of a corporation or a not-for-profit entity or by other hybrid forms. This paper reports on the investigation of such a hybrid model of open source EHR project governance adopted with success by a large Canadian hospital. The case study provides rich insights for other hospitals wishing to adopt an EHR of the open source type.},
	doi = {10.1109/HICSS.2014.350},
	author = {Placide Poba-Nzaou and Josianne Marsan and Guy Pare and Louis Raymond}
}
@conference {1692,
	title = {Hackers on Forking},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {All open source licenses allow the copying of an existing body of code for use as the basis of a separate development project. This practice is commonly known as forking the code. This paper presents the results of a study in which 11 programmers were interviewed about their opinions on the right to fork and the impact of forking on open source software development.

The results show that there is a general consensus among programmers{\textquoteright} views regarding both the favourable and unfavourable aspects that stem from the right to fork. Interestingly, while all programmers noted potential downsides to the right to fork, it was seen by all as an integral component of open source software, and a right that must not be infringed regardless of circumstance or outcome.},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641590},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p06.pdf},
	author = {Nyman, Linus}
}
@conference {Ahmed:2014:IAC:2641580.2641585,
	title = {The Impact of Automatic Crash Reports on Bug Triaging and Development in Mozilla},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1:1{\textendash}1:8},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Free/Open Source Software projects often rely on users submitting bug reports. However, reports submitted by novice users may lack information critical to developers, and the process may be intimidating and difficult. To gather more and better data, projects deploy automatic crash reporting tools, which capture stack traces and memory dumps when a crash occurs. These systems potentially generate large volumes of data, which may overwhelm developers, and their presence may discourage users from submitting traditional bug reports. In this paper, we examine Mozilla{\textquoteright}s automatic crash reporting system and how it affects their bug triaging process. We find that fewer than 0.00009\% of crash reports end up in a bug report, but as many as 2.33\% of bug reports have data from crash reports added. Feedback from developers shows that despite some problems, these systems are valuable. We conclude with a discussion of the pros and cons of automatic crash reporting systems.
},
	keywords = {Automatic Crash reporting, debugging, FOSS, Free/Open Source Software, Open Bug Reporting, testing},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641585},
	url = {http://doi.acm.org/10.1145/2641580.2641585},
	author = {Ahmed, Iftekhar and Mohan, Nitin and Jensen, Carlos}
}
@conference {1704,
	title = {Industry Questions about Open Source Software in Business: Research Directions and Potential Answers},
	booktitle = {2014 6th International Workshop on Empirical Software Engineering in Practice (IWESEP)2014 6th International Workshop on Empirical Software Engineering in Practice},
	year = {2014},
	pages = {55 - 59},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Osaka, Japan},
	abstract = {As open source software (OSS) has become an integral part of today{\textquoteright}s software businesses, many software companies rely on OSS to develop their customer solutions and products. On the other hand, they face various concerns in using OSS, such as technical support, quality, security and licensing issues. This paper focuses on OSS-related FAQ in industry, and tries to answer them or to provide research directions based on lessons learned from recent mining OSS repository researches.
},
	doi = {10.1109/IWESEP.2014.12},
	author = {Ihara, Akinori and Monden, Akito and Matsumoto, Ken-ichi}
}
@conference {1693,
	title = {Initial Results from the Study of the Open Source Sector in Belgium},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 5},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {The economy of FLOSS (Free and open source software) has been the subject of numerous studies and publications, particularly on the issue of business models. However, there are fewer studies on the local networks of FLOSS providers. This research focuses on the ecosystem of Belgian FLOSS providers and, more specifically, their geographical distribution, the activities, technologies and software they support, their business models, their economic performance and the relationships between companies. The research is based on a directory containing nearly 150 companies. This directory led to the creation of a specialized search engine that helped to improve annotation. The research also uses financial data provided by the Belgian Central Balance Sheet Office. The initial results of this study show a concentration in major economic areas. The businesses are more active in the services and are heavily involved activities such as infrastructure software and Web development, activities which were common in the early years of free software development. Services for the support of business software is also common. A first analysis of the graph of relationships between providers{\textquoteright} websites highlights the role that is played by the multinational IT companies, by FLOSS editors, by commercial FLOSS associations and especially by the Walloon centers of competence that offer vast training catalogs that are dedicated to FLOSS. This research opens up many perspectives for improving the automation of the company directory updates, the analysis of the relationship between enterprises, and the automation of the financial analysis of companies.
},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641591},
	author = {Viseur, Robert}
}
@conference {1690,
	title = {"The Institutionalization of Digital Openness"},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 2},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {Around the world national and municipal governments launch open data initiatives with declared goals like increased efficiency, transparency or economic growth. However, although little of these effects have been proven, more and more administrations open up their datasets to the public. The dissertation project describes this phenomenon as the ongoing institutionalization of digital openness in the field of public sector information. With empirical evidence from three case studies in large European cities the research project intends to theorize how NGOs, hackers and certain civil servants turn open data into an institution, which more and more public bodies feel the need to adapt to.
},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641626},
	author = {Maximilian Heimst{\"a}dt}
}
@inbook {1612,
	title = {A Layered Approach to Managing Risks in OSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {168-171},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

In this paper, we propose a layered approach to managing risks in OSS projects. We define three layers: the first one for defining risk drivers by collecting and summarising available data from different data sources, including human-provided contextual information; the second layer, for converting these risk drivers into risk indicators; the third layer for assessing how these indicators impact the business of the adopting organisation. The contributions are: 1) the complexity of gathering data is isolated in one layer using appropriate techniques, 2) the context needed to interpret this data is provided by expert involvement evaluating risk scenarios and answering questionnaires in a second layer, 3) a pattern-based approach and risk reasoning techniques to link risks to business goals is proposed in the third layer.
},
	keywords = {Layered Model, open source, OSS, Risk Management},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_23},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_23},
	author = {Franch, Xavier and Kenett, Ron and Mancinelli, Fabio and Susi, Angelo and Ameller, David and Ben-Jacob, Ron and Siena, Alberto},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@inbook {1607,
	title = {Lessons Learned from Teaching Open Source Software Development},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {133-142},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Free/Open Source Software allows students to learn valuable real world skills and experiences, as well as a create a portfolio to show future employers. However, the learning curve to joining FOSS can be daunting, often leading newcomers to walk away frustrated. Universities therefore need to find ways to provide a structured introduction to students, helping them overcome the barriers to entry. This paper describes two courses taught at two universities, built around a Communities of Practice model, and the lessons learned from these. Suggestions and insights are shared for how to structure and evaluate such courses for maximum effect.
},
	keywords = {education, FOSS, Free/Open Source Software},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_18},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_18},
	author = {Morgan, Becka and Jensen, Carlos},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@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 {1823,
	title = {"May the fork be with you": novel metrics to analyze collaboration on GitHub},
	booktitle = {Proceedings of the 5th International Workshop on Emerging Trends in Software Metrics - WETSoM 2014},
	year = {2014},
	note = {"According to FLOSSmole [8] (Free Libre OpenSource Software)
statistics, GitHub had 191765 repositories publicly
available at May 2012."},
	pages = {37 - 43},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Multi{\textendash}repository software projects are becoming more and
more popular, thanks to web{\textendash}based facilities such as GitHub.
Code and process metrics generally assume a single repository
must be analyzed, in order to measure the characteristics
of a codebase. Thus they are not apt to measure how
much relevant information is hosted in multiple repositories
contributing to the same codebase. Nor can they feature
the characteristics of such a distributed development process.
We present a set of novel metrics, based on an original
classification of commits, conceived to capture some interesting
aspects of a multi{\textendash}repository development process. We
also describe an efficient way to build a data structure that
allows to compute these metrics on a set of Git repositories.
Interesting outcomes, obtained by applying our metrics
on a large sample of projects hosted on GitHub, show the
usefulness of our contribution.},
	keywords = {flossmole, github},
	isbn = {9781450328548},
	doi = {10.1145/2593868.2593875},
	url = {http://marbiaz.github.io/docs/Biazzini14b.pdf},
	author = {Marco Biazzini and Benoit Baudry}
}
@article {mcdonald2014modeling,
	title = {MODELING DISTRIBUTED COLLABORATION ON GITHUB},
	journal = {Advances in Complex Systems},
	year = {2014},
	publisher = {World Scientific},
	abstract = {In this paper, we apply concepts from Distributed Leadership, a theory suggesting that leadership is shared among members of an organization, to frame models of contribution that we uncover in five relatively successful open source software (OSS) projects hosted on GitHub. In this qualitative, comparative case study, we show how these projects make use of GitHub features such as pull requests (PRs). We find that projects in which member PRs are more frequently merged with the codebase experience more sustained participation. We also find that projects with higher success rates among contributors and higher contributor retention tend to have more distributed (non-centralized) practices for reviewing and processing PRs. The relationships between organizational form and GitHub practices are enabled and made visible as a result of GitHub{\textquoteright}s novel interface. Our results demonstrate specific dimensions along which these projects differ and explicate a framework that warrants testing in future studies of OSS, particularly GitHub.},
	author = {McDONALD, NORA and Blincoe, Kelly and PETAKOVIC, EVA and Goggins, Sean}
}
@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.}
}
@conference {1676,
	title = {OCData Hackathon @ CSCW 2014},
	booktitle = {Proceedings of the 17th ACM conference on Computer supported cooperative work \& social computing},
	year = {2014},
	pages = {317 - 318},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Baltimore, Maryland, USANew York, New York, USA},
	abstract = {Online Communities data is prevalent in CSCW research, but the approaches to collecting, managing, analyzing and visualizing large scale social data varies on a lab by lab basis. The OCData hackathon is aimed at creating a community opportunity to share approaches to online communities research at the level of data. Integrating data, tools and theories to address interesting research questions remains a challenge for the community.},
	isbn = {9781450325417},
	doi = {10.1145/2556420.2558865},
	author = {Goggins, Sean and Andrea Wiggins and Susan Winter and Brian Butler}
}
@conference {1691,
	title = {Older Adults and Free/Open Source Software},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {The global population is aging rapidly, and older adults are becoming increasingly technically savvy. This paper explores ways to engage these individuals to contribute to free/open source software (FOSS) projects. We conducted a pilot diary study to explore motivations, barriers, and the contribution processes of first-time contributors in a real time, qualitative manner. In addition, we measured their self-efficacy before and after their participation. We found that what drove participants were intrinsic motivations, altruism, and internal values, which differed from previous work with older adults and with the general FOSS population. We also found that self-efficacy did not change significantly, even when participants encountered significant barriers or setbacks. The top 3 barriers were lack of communication, installation issues, and documentation issues. We found that asking for and receiving help, and avoiding difficult development environments were more likely to lead to success. To verify these results, we encourage a future large-scale diary study that involves multiple demographics. Given our pilot study, we recommend that future outreach efforts involving older adults focus on how to effectively communicate and build community amongst older contributors.
},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641589},
	author = {Davidson, Jennifer and Umme Ayda Mannan and Rithika Naik and Ishneet Dua and Jensen, Carlos}
}
@conference {Guo:2014:ODC:2597073.2597094,
	title = {Oops! Where Did That Code Snippet Come from?},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {52{\textendash}61},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {A kernel oops is an error report that logs the status of the Linux kernel at the time of a crash. Such a report can provide valuable first-hand information for a Linux kernel maintainer to conduct postmortem debugging. Recently, a repository has been created that systematically collects kernel oopses from Linux users. However, debugging based on only the information in a kernel oops is difficult. We consider the initial problem of finding the offending line, i.e., the line of source code that incurs the crash. For this, we propose a novel algorithm based on approximate sequence matching, as used in bioinformatics, to automatically pinpoint the offending line based on information about nearby machine-code instructions, as found in a kernel oops. Our algorithm achieves 92\% accuracy compared to 26\% for the traditional approach of using only the oops instruction pointer.},
	keywords = {debugging, linux kernel, oops, sequence alignment},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597094},
	url = {http://doi.acm.org/10.1145/2597073.2597094},
	attachments = {https://flosshub.org/sites/flosshub.org/files/guo.pdf},
	author = {Guo, Lisong and Lawall, Julia and Muller, Gilles}
}
@conference {Syeed:2014:SCR:2641580.2641586,
	title = {Socio-Technical Congruence in the Ruby Ecosystem},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {2:1{\textendash}2:9},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Existing studies show that open source projects may enjoy high levels of socio-technical congruence despite their open and distributed character. Such observations are yet to be confirmed in the case of larger open source ecosystems in which developers contribute to different projects within the ecosystem. In this paper, we empirically study the relationships between the developer coordination activities and the project dependency structure in the Ruby ecosystem. Our motivation is to verify whether the ecosystem context maintains the high socio-technical congruence levels observed in many smaller scale FLOSS (Free/Libre Open Source Software) projects. Our study results show that the collaboration pattern among the developers in Ruby ecosystem is not necessarily shaped by the communication needs indicated by the dependencies among the ecosystem projects.
},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641586},
	url = {http://doi.acm.org/10.1145/2641580.2641586},
	author = {Syeed, M.M. Mahbubul and Hansen, Klaus Marius and Hammouda, Imed and Manikas, Konstantinos}
}
@conference {Padhye:2014:SEC:2597073.2597113,
	title = {A Study of External Community Contribution to Open-source Projects on GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {332{\textendash}335},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open-source software projects are primarily driven by community contribution. However, commit access to such projects{\textquoteright} software repositories is often strictly controlled. These projects prefer to solicit external participation in the form of patches or pull requests. In this paper, we analyze a set of 89 top-starred GitHub projects and their forks in order to explore the nature and distribution of such community contribution. We first classify commits (and developers) into three categories: core, external and mutant, and study the relative sizes of each of these classes through a ring-based visualization. We observe that projects written in mainstream scripting languages such as JavaScript and Python tend to include more external participation than projects written in upcoming languages such as Scala. We also visualize the geographic spread of these communities via geocoding. Finally, we classify the types of pull requests submitted based on their labels and observe that bug fixes are more likely to be merged into the main projects as compared to feature enhancements.
},
	keywords = {community participation, core committers, external contribution, mining challenge, mining software repositories, msr challenge, Open-source software, pull requests},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597113},
	url = {http://doi.acm.org/10.1145/2597073.2597113},
	author = {Padhye, Rohan and Mani, Senthil and Sinha, Vibha Singhal}
}
@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.}
}
@inbook {1630,
	title = {The Babel of Software Development: Linguistic Diversity in Open Source},
	booktitle = {Social Informatics},
	series = {Lecture Notes in Computer Science},
	volume = {8238},
	year = {2013},
	pages = {391-404},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	isbn = {978-3-319-03259-7},
	doi = {10.1007/978-3-319-03260-3_34},
	url = {http://dx.doi.org/10.1007/978-3-319-03260-3_34},
	attachments = {https://flosshub.org/sites/flosshub.org/files/socinfo13.pdf},
	author = {Vasilescu, Bogdan and Serebrenik, Alexander and Brand, MarkG.J.},
	editor = {Jatowt, Adam and Lim, Ee-Peng and Ding, Ying and Miura, Asako and Tezuka, Taro and Dias, Ga{\"e}l and Tanaka, Katsumi and Flanagin, Andrew and Dai, BingTian}
}
@proceedings {1507,
	title = {Bug Resolution Catalysts: Identifying Essential Non-committers from Bug Repositories},
	year = {2013},
	month = {05/2013},
	abstract = {Bugs are inevitable in software projects. Resolving bugs is the primary activity in software maintenance. Developers, who fix bugs through code changes, are naturally important participants in bug resolution. However, there are other participants in these projects who do not perform any code commits. They can be reporters reporting bugs; people having a deep technical know-how of the software and providing valuable insights on how to solve the bug; bug-tossers who re-assign the bugs to the right set of developers. Even though all of them act on the bugs by tossing and commenting, not all of them may be crucial for bug resolution. In this paper, we formally define essential non-committers and try to identify these bug resolution catalysts. We empirically study 98304 bug reports across 11 open source and 5 commercial software projects for validating the existence of such catalysts. We propose a network analysis based approach to construct a Minimal Essential Graph that identifies such people in a project. Finally, we suggest ways of leveraging this information for bug triaging and bug report summarization.},
	author = {Mani, Senthil and Seema Nagar and Debdoot Mukherjee and Ramasuri Narayanam and Sinha, Vibha Singhal and Amit A. Nanavati}
}
@article {Ampatzoglou2013131,
	title = {Building and mining a repository of design pattern instances: Practical and research benefits},
	journal = {Entertainment Computing},
	volume = {4},
	number = {2},
	year = {2013},
	note = {flossmole cited},
	pages = {131 - 142},
	abstract = {Design patterns are well-known design solutions that are reported to produce substantial benefits with respect to software quality. However, to our knowledge there are no scientific efforts on gathering information on software projects that use design patterns. This paper introduces a web repository of design patterns instances that have been used in open source projects. The usefulness of such a repository lies in the provision of a base of knowledge, where developers can identify reusable components and researchers can find a mined data set. Currently, 141 open source projects have been considered and more than 4500 pattern instances have been found and recorded in the database of the repository. The evaluation of the repository has been performed from an academic and a practical point of view. The results suggest that the repository can be useful for both experienced and inexperienced users. However, the benefits of using the repository are more significant for inexperienced users. },
	keywords = {flossmole cited, repository},
	issn = {1875-9521},
	doi = {10.1016/j.entcom.2012.10.002},
	url = {http://www.sciencedirect.com/science/article/pii/S1875952112000195},
	author = {Apostolos Ampatzoglou and Olia Michou and Ioannis Stamelos}
}
@conference {Venkataramani:2013:DTE:2487788.2487832,
	title = {Discovery of Technical Expertise from Open Source Code Repositories},
	booktitle = {Proceedings of the 22Nd International Conference on World Wide Web Companion},
	series = {WWW {\textquoteright}13 Companion},
	year = {2013},
	pages = {97{\textendash}98},
	publisher = {International World Wide Web Conferences Steering Committee},
	organization = {International World Wide Web Conferences Steering Committee},
	address = {Republic and Canton of Geneva, Switzerland},
	abstract = {Online Question and Answer websites for developers have emerged as the main forums for interaction during the software development process. The veracity of an answer in such websites is typically verified by the number of {\textquoteright}upvotes{\textquoteright} that the answer garners from peer programmers using the same forum. Although this mechanism has proved to be extremely successful in rating the usefulness of the answers, it does not lend itself very elegantly to model the expertise of a user in a particular domain. In this paper, we propose a model to rank the expertise of the developers in a target domain by mining their activity in different opensource projects. To demonstrate the validity of the model, we built a recommendation system for StackOverflow which uses the data mined from GitHub.
},
	keywords = {github, knowledge discovery, recommendations, source code repository, stackoverflow, technical expertise},
	isbn = {978-1-4503-2038-2},
	url = {http://dl.acm.org/citation.cfm?id=2487788.2487832},
	author = {Venkataramani, Rahul and Gupta, Atul and Asadullah, Allahbaksh and Muddu, Basavaraju and Bhat, Vasudev}
}
@proceedings {1494,
	title = {Do Software Categories Impact Coupling Metrics?},
	year = {2013},
	month = {05/2013},
	pages = {217-220},
	abstract = {Software metrics is a valuable mechanism to assess
the quality of software systems. Metrics can help the automated
analysis of the growing data available in software repositories.
Coupling metrics is a kind of software metrics that have been
extensively used since the seventies to evaluate several software
properties related to maintenance, evolution and reuse tasks. For
example, several works have shown that we can use coupling
metrics to assess the reusability of software artifacts available in
repositories. However, thresholds for software metrics to indicate
adequate coupling levels are still a matter of discussion. In this
paper, we investigate the impact of software categories on the
coupling level of software systems. We have found that different
categories may have different levels of coupling, suggesting that
we need special attention when comparing software systems in
different categories and when using predefined thresholds
already available in the literature.
},
	url = {http://www.facom.ufu.br/~marcmaia/preprints/msr13-SouzaMaia-CategoriesAndCoupling.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr13-SouzaMaia-CategoriesAndCoupling.pdf},
	author = {Lucas Batista Leite de Souza and Marcelo de Almeida Maia}
}
@book {1546,
	title = {A Dual Model of Open Source License Growth},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	note = {uses ohloh snapshot, march 2008},
	pages = {245 - 256},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Every open source project needs to decide on an open source license. This decision is of high economic relevance: Just which license is the best one to help the project grow and attract a community? The most common question is: Should the project choose a restrictive (reciprocal) license or a more permissive one? As an important step towards answering this question, this paper analyses actual license choice and correlated project growth from ten years of open source projects. It provides closed analytical models and finds that around 2001 a reversal in license choice occurred from restrictive towards permissive licenses.
},
	keywords = {ohloh},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/oss2013.hofmann.pdf},
	author = {Hofmann, Gottfried and Dirk Riehle and Carsten Kolassa and Mauerer, Wolfgang},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@conference {1684,
	title = {Gendered Patterns of Politeness in Free/Libre Open Source Software Development},
	booktitle = {2013 46th Hawaii International Conference on System Sciences (HICSS)2013 46th Hawaii International Conference on System Sciences},
	year = {2013},
	pages = {3168 - 3177},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Wailea, HI, USA},
	isbn = {978-0-7695-4892-0},
	doi = {10.1109/HICSS.2013.240},
	url = {https://www.ischool.utexas.edu/~eymoon/pdf/hicss46\%20eymoon\%20(proceeding).pdf},
	author = {Moon, Eunyoung}
}
@proceedings {1510,
	title = {A Historical Dataset for the Gnome Ecosystem},
	year = {2013},
	month = {05/2013},
	abstract = {We present a dataset of the open source software ecosystem Gnome from a social point of view. We have collected historical data about the contributors to all Gnome projects stored on git.gnome.org, taking into account the problem of identity matching, and associating different activity types to the contributors. This type of information is very useful to complement the traditional, source-code related information one can obtain by mining and analyzing the actual source code. The dataset can be obtained at https://bitbucket.org/mgoeminne/sgl-flossmetric-dbmerge.},
	keywords = {cvsanaly, flossmetrics, gnome},
	author = {Mathieu Goeminne and Ma{\"e}lick Claes and Mens, Tom}
}
@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.}
}
@book {1529,
	title = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification Technological Innovation and Resource Bricolage in Firms: The Role of Open Source Software},
	volume = {404},
	year = {2013},
	pages = {1 - 17},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {Technological resources have been an important source of innovation in companies. They play a key role in the development of new products and services. However, the upfront investment in technical resources to enable the development of these new products and services can be quite high. Therefore, managers ask for well elaborated business cases before making investments. These business cases rely on market research to back up their assumptions rather than in-market testing. We argue that the advent of open source software (OSS) creates an opportunity space for companies to build low-cost prototypes and test their ideas in the market. Little is known about how OSS plays a role in allowing these firms to enhance product development. Using qualitative case studies, the paper sheds light on how OSS acts as a bricolage mechanism for technological innovation in the ICT services industry.},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_1},
	url = {http://link.springer.com/chapter/10.1007/978-3-642-38928-3_1},
	author = {Mahajan, Aarti and Clarysse, Bart},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@conference {1576,
	title = {A scalable crawler framework for FLOSS data},
	booktitle = {Proceedings of the 5th Asia-Pacific Symposium on Internetware - Internetware {\textquoteright}13},
	year = {2013},
	note = {FLOSSmole [8] and FLOSSmetrics [9] retrieved FLOSS data of
various types from famous software forges like SourceForge and
Google code, interface to data sharing and analyzing is also
provided. 

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

"Using
FLOSSmole [8] and FLOSSmetrics [9] as case studies, similar
systems as such are called {\textquotedblleft}repository of repositories (RoR){\textquotedblright} and
basic requirements of these systems are proposed. "},
	pages = {1 - 7},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Changsha, China},
	abstract = {Free / Libre / Open Source Software (FLOSS) data, such as bug reports, mailing lists and related webpages, contains valuable information for reusing open source software projects. Before conducting further experiment on FLOSS data, researchers often need to download these data into a local storage system. We refer to this pre-process as FLOSS data retrieval, which in many cases can be a challenging task. In this paper, we proposed a crawler framework to ease the process of FLOSS data retrieval. To cope with various types of FLOSS data scattered on the Internet, we designed the framework in a scalable manner where a crawler program can be easily plugged into the system to extend its functionality. Researchers can perform the retrieval process on datasets of various types and sources simply by adding new configurations to the system. We have implemented the framework and provided basic functions via web-based interfaces. We presented the usage of the system by a detailed case study where we retrieved various types of datasets related to Apache Lucene project using our framework.},
	keywords = {flossmole cited},
	isbn = {9781450323697},
	doi = {10.1145/2532443.2532454},
	author = {Yanzhen Zou and Bing Zie and Zhang, Lingxiao}
}
@article {1810,
	title = {Understanding How Companies Interact with Free Software Communities},
	journal = {IEEE Software},
	volume = {30},
	year = {2013},
	month = {9/2013},
	pages = {38 - 45},
	abstract = {When free, open source software development communities work with companies that use their output, it{\textquoteright}s especially important for both parties to understand how this collaboration is performing. The use of data analytics techniques on software development repositories can improve factual knowledge about performance metrics.
},
	issn = {0740-7459},
	doi = {10.1109/MS.2013.95},
	author = {Jesus M. Gonzalez-Barahona and Izquierdo-Cortazar, Daniel and Maffulli, Stefano and Gregorio Robles}
}
@article {1554,
	title = {Using software analytics to understand how companies interact in free software communities},
	journal = {IEEE Software},
	year = {2013},
	month = {2013},
	pages = {1 - 1},
	abstract = {

Free, open source software development communities may become large and complex. They may also be a focus of interest for competing companies relying on their outcomes, with their employees joining the development and maintenance effort. In those cases it is specially important for both companies and communities to understand how this collaboration is working, and how it matches their policies and expectations. In this paper we show two cases (OpenStack and WebKit) which we have studied using analytics techniques on the data obtained from their software development repositories. From them, we conclude that analytics on this data can improve the factual knowledge about how development communities are performing in aspects which are of interest to companies, and fundamental to ensure transparency and fairness.
},
	keywords = {openstack, webkit},
	issn = {0740-7459},
	doi = {10.1109/MS.2013.95},
	author = {Gonzalez-Barahona, Jesus and Izquierdo, Daniel and Maffulli, Stefano and Gregorio Robles}
}
@article {1395,
	title = {Automated topic naming: supporting cross-project analysis of software maintenance activities},
	journal = {Empirical Software Engineering},
	year = {2012},
	abstract = {Software repositories provide a deluge of software artifacts to analyze. Researchers have attempted to summarize, categorize, and relate these artifacts by using semi-unsupervised machine-learning algorithms, such as Latent Dirichlet Allocation (LDA). LDA is used for concept and topic analysis to suggest candidate word-lists or topics that describe and relate software artifacts. However, these word-lists and topics are difficult to interpret in the absence of meaningful summary labels. Current attempts to interpret topics assume manual labelling and do not use domain-specific knowledge to improve, contextualize, or describe results for the developers. We propose a solution: automated labelled topic extraction. Topics are extracted using LDA from commit-log comments recovered from source control systems. These topics are given labels from a generalizable cross-project taxonomy, consisting of non-functional requirements. Our approach was evaluated with experiments and case studies on three large-scale Relational Database Management System (RDBMS) projects: MySQL, PostgreSQL and MaxDB. The case studies show that labelled topic extraction can produce appropriate, context-sensitive labels that are relevant to these projects, and provide fresh insight into their evolving software development activities. },
	keywords = {LDA, maxdb, mysql, postgresql, topics},
	issn = {1573-7616},
	doi = {10.1007/s10664-012-9209-9},
	author = {Hindle, Abram and Ernst, Neil A. and Godfrey, Michael W. and Mylopoulos, John}
}
@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}
}
@proceedings {1462,
	title = {Does OSS Affect E-Government Growth? An Econometric Analysis on the Impacting Factors},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {292-297},
	publisher = {IFIP AICT,  Springer},
	abstract = {Inspired by the OSS values, an increasing number of different forms of open initiatives have come to the fore. In the context of eGovernment the notion of open government has met wide acceptance among nations and became closely related to one of its goals. Open government shares with OSS the notions of collaboration, participation and transparency and many actions towards OSS into eGovernment reform policies, have been recorded worldwide. The study investigates the relationship between OSS growth and eGovernment. A theoretical framework of the theories of institutionalism, growth and human capital is proposed as the guiding theoretical lens to identify possible influencing factors that together with OSS are evaluated for their magnitude of impact on eGovernment growth across different economic environments.},
	keywords = {eGovernment adoption, growth theory, human capital theory, institutionalism},
	author = {Lakka, Spyridoula and Stamati, Teta and Martakos, Draculis}
}
@proceedings {1445,
	title = {Emerging Hackerspaces {\textendash} Peer-Production Generation},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {94-111},
	publisher = {IFIP AICT},
	abstract = {This paper describes a peer-production movement, the hackerspace movement, its members and values. The emergence of hackerspaces, fablabs and makerspaces is changing how hacker communities and other like-minded communities function. Thus, an understanding of the nature of hackerspaces helps in detailing the features of contemporary peer-production. Building on previous work on {\textquoteright}fabbing{\textquoteright}, two different sets of results are presented: (1) empirical observations from a longitudinal study of hackerspace participants; and (2) a theoretical description of hacker generations as a larger context in which peer-production can be located. With regard to (1), research data has been collected through prolonged observation of hackerspace communities and two surveys.},
	keywords = {COMMUNITY, fabbing, fablab, hackerspace, makerspace, MOTIVATION, movement, open source, peer-production, Survey, sustainability},
	author = {Moilanen, Jarkko}
}
@article {1399,
	title = {The evolution of Java build systems},
	journal = {Empirical Software Engineering},
	volume = {17},
	year = {2012},
	month = {8/2012},
	pages = {578 - 608},
	abstract = {Build systems are responsible for transforming static source code artifacts into executable software. While build systems play such a crucial role in software development and maintenance, they have been largely ignored by software evolution researchers. However, a firm understanding of build system aging processes is needed in order to allow project managers to allocate personnel and resources to build system maintenance tasks effectively, and reduce the build maintenance overhead on regular development activities. In this paper, we study the evolution of build systems based on two popular Java build languages (i.e., ANT and Maven) from two perspectives: (1) a static perspective, where we examine the complexity of build system specifications using software metrics adopted from the source code domain; and (2) a dynamic perspective, where the complexity and coverage of representative build runs are measured. Case studies of the build systems of six open source build projects with a combined history of 172 releases show that build system and source code size are highly correlated, with source code restructurings often requiring build system restructurings. Furthermore, we find that Java build systems evolve dynamically in terms of duration and recursive depth of the directory hierarchy. },
	keywords = {ant, build, maven, scm, source code analysis},
	issn = {1573-7616},
	doi = {10.1007/s10664-011-9169-5},
	author = {McIntosh, Shane and Adams, Bram and Hassan, Ahmed E.}
}
@proceedings {1451,
	title = {Exploring the Role of Outside Organizations in Free / Open Source Software Projects},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {201-215},
	publisher = {IFIP AICT},
	abstract = {Free/Open Source Software (FOSS) projects have a reputation for being grass-roots efforts driven by individual contributors volunteering their time and effort. While this may be true for a majority of smaller projects, it is not always the case for large projects. As projects grow in size, importance and complexity, many come to depend on corporations, universities, NGO{\textquoteright}s and governments, for support and contributions, either financially or through seconded staff. As outside organizations get involved in projects, how does this affect their governance, transparency and direction? To study this question we gathered bug reports and commit logs for GCC and the Linux Kernel. We found that outside organizations contribute a majority of code but rarely participate in bug triaging. Therefore their code does not necessarily address the needs of others and may distort governance and direction. We conclude that projects should examine their dependence on outside organizations},
	keywords = {bug reports, commit, Community sustainability, Contributor affiliation, gcc, governance, linux kernel, Participation metrics},
	url = {http://research.engr.oregonstate.edu/hci/sites/research.engr.oregonstate.edu.hci/files/papers/forrest2012exploring.pdf},
	author = {Forrest, Darren and Jensen, Carlos and Mohan, Nitin and Davidson, Jennifer}
}
@article {1397,
	title = {How do open source communities blog?},
	journal = {Empirical Software Engineering},
	year = {2012},
	abstract = {We report on an exploratory study, which aims at understanding how software communities use blogs compared to conventional development infrastructures. We analyzed the behavior of 1,100 bloggers in four large open source communities, distinguishing between committing bloggers and other community members. We observed that these communities intensively use blogs with one new entry every 8 h. A blog entry includes 14 times more words than a commit message. When analyzing the content of the blogs, we found that committers and others bloggers write about similar topics. Most popular topics in committers{\textquoteright} blogs represent high-level concepts such as features and domain concepts, while source code related topics are discussed in 15\% of their posts. Other community members frequently write about community events and conferences as well as configuration and deployment topics. We found that the blogging peak period is usually after the software is released. Moreover, committers are more likely to blog after corrective engineering than after forward engineering and re-engineering activities. Our findings call for a hypothesis-driven research to (a) further understand the role of social media in dissolving the collaboration boundaries between developers and other stakeholders and (b) integrate social media into development processes and tools. },
	keywords = {blog, blogs},
	issn = {1573-7616},
	doi = {10.1007/s10664-012-9211-2},
	author = {Pagano, Dennis and Maalej, Walid}
}
@proceedings {1467,
	title = {A Linguistic Analysis on How Contributors Solve Software Problems in a Distributed Context},
	volume = {378},
	year = {2012},
	note = {"... a sample of 4109 bug reports was extracted from Bugzilla bug report repository"
"The analysis of our sample allows identifying the roles of participants in this activity according to their hierarchical statutes in the community. "
"we look statistically at words that people use in Bugzilla to discern differences in the discourse and representation between participants (core and periphery)"},
	month = {09/2012},
	pages = {322-330},
	publisher = {IFIP AICT,  Springer},
	abstract = {There is a little understanding of distributed solving activities in Open Source communities. This study aimed to provide some insights in this way. It was applied to the context of Bugzilla, the bug tracking system of Mozilla community. This study investigated the organizational aspects of this meditated, complex and highly distributed context through a linguistic analysis method. The main finding of this research shows that the organization of distributed problem-solving activities in Bugzilla isn{\textquoteright}t based only on the hierarchical distribution of the work between core and periphery participants but on their implication in the interactions. This implication varies according to the status of each one participant in the community. That is why we distinguish their roles, as well as, the established modes to manage such activity.},
	keywords = {bug report, bugzilla, linguistic, text mining},
	author = {Masmoudi, H{\'e}la and Boughzala, Imed}
}
@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 {1453,
	title = {Open Source Migration in Greek Public Sector: A Feasibility Study},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {233-243},
	publisher = {IFIP AICT},
	abstract = {Open Source software has been recently recognized by governments as a viable and cost effective solution. However, transition to open source is not a plug-and-play process but one that requires deep knowledge of open source dynamics and of organization{\textquoteright}s operations, budgetary constraints, capacities, ethics and political agenda. As with any IT transition, there are uncertainties and risks that need to be handled in order to maximize the gains for the organization and for the society through the provided services. In this paper we present a feasibility study conducted in 15 Greek public sector organizations with the aim to discover the value this transition brings to a typical public sector organization.},
	author = {Mavridis, Androklis and Fotakidis, Dimitrios and Ioannis Stamelos}
}
@proceedings {1459,
	title = {Perspectives on Code Forking and Sustainability in Open Source Software},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {274-279},
	publisher = {IFIP AICT,  Springer},
	abstract = {The ability to create high-quality software artifacts that are usable over time is one of the essential requirements of the software business. In such a setting, open source software offers excellent opportunities for sustainability. In particular, safeguarding mechanisms against planned obsolescence by any single actor are built into the definition of open source. The most powerful of these mechanisms is the ability to fork the project. In this paper we argue that the possibility to fork serves as the invisible hand of sustainability that ensures that code remains open and that the code that best serves the community lives on. Furthermore, the mere option to fork provides a mechanism for safeguarding against despotic decisions by the project lead, who is thus guided in their actions to consider the best interest of the community.},
	author = {Nyman, Linus and Mikkonen, Tommi and Juho Lindman and Fougère, Martin}
}
@conference {1523,
	title = {Social coding in GitHub},
	booktitle = {Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work - CSCW {\textquoteright}12},
	year = {2012},
	pages = {1277},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Seattle, Washington, USA},
	abstract = {
Social applications on the web let users track and follow the activities of a large number of others regardless of location or affiliation. There is a potential for this transparency to radically improve collaboration and learning in complex knowledge-based activities. Based on a series of in-depth interviews with central and peripheral GitHub users, we examined the value of transparency for large-scale distributed collaborations and communities of practice. We find that people make a surprisingly rich set of social inferences from the networked activity information in GitHub, such as inferring someone else{\textquoteright}s technical goals and vision when they edit code, or guessing which of several similar projects has the best chance of thriving in the long term. Users combine these inferences into effective strategies for coordinating work, advancing technical skills and managing their reputation.
},
	keywords = {github},
	isbn = {9781450310864},
	doi = {10.1145/2145204.2145396},
	url = {http://www.cs.cmu.edu/afs/cs/Web/People/xia/resources/Documents/cscw2012_Github-paper-FinalVersion-1.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cscw2012_Github-paper-FinalVersion-1.pdf},
	author = {Laura Dabbish and Colleen Stuart and Jason Tsay and Herbsleb, Jim}
}
@proceedings {1468,
	title = {A Study on OSS Marketing and Communication Strategies},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {338-343},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {The goal of every open source project is to gain as many satisfied users as possible. To this end, open source software producers should focus on both product development and communication. Currently, most open source projects are mainly concerned with developing code using the most appealing technologies and introducing fancy features. On the contrary, open source software producers seem to lack good communication strategies. In this paper we describe the communication strategies adopted by three successful companies that are active in open source software development. The goal of the paper is to provide some hints that could help other open source software producers identify communication strategies that are effective in promoting their products on the market.},
	author = {del Bianco, Vieri and Lavazza, Luigi and Lenarduzzi, Valentina and Morasca, Sandro and Taibi, Davide and Tosi, Davide}
}
@article {1707,
	title = {Time-Based Release Management in Free and Open Source (FOSS) Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {4},
	year = {2012},
	month = {31/2012},
	pages = {1 - 19},
	abstract = {As the Free and Open Source (FOSS) concept has
matured, its commercial significance has also
increased, and issues such as quality and
sustainability have moved to the fore. In this study,
we focus on time-based release management in large
volunteer FOSS projects, and reveal how it addresses
quality and sustainability issues. We discuss the
differences between release management in the
traditional software context and contrast it with
FOSS settings. Based on detailed case studies of a
number of prominent FOSS projects, we describe the
move to time-based release management and identify
the factors and criteria necessary for a successful
transition. We also consider the implications for
software development more generally in the current
dynamic Internet-enabled environment.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2012010101},
	url = {http://lero.ie/sites/default/files/Lero-TR-2011-04.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Lero-TR-2011-04.pdf},
	author = {Martin Michlmayr and Fitzgerald, Brian}
}
@proceedings {1449,
	title = {Using Multiple Case Studies to Analyse Open Source Software Business Sustainability in Sub-Saharan Africa},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {160-177},
	publisher = {IFIP AICT},
	abstract = {Amidst the debate about what sort of technology is appropriate for achieving sustainable development, Free and Open Source Software (FOSS) offers some solutions to today{\textquoteright}s technology problems for many developing countries. However, there is a paucity of empirical evidence to help us understand the potentials FOSS technologies have for small businesses in Sub-Saharan Africa. This research utilizes nine case studies data from seven African countries to find out how entrepreneurs are leveraging FOSS to help them create sustainable business based on openness. The findings show increasing awareness of the business potential of FOSS, and a business model incorporating both FOSS and proprietary software is needed to run a sustainable IT business in these countries. However, the lack of skilled FOSS developer base, the absence of appropriate policies, and poor payment habits by clients are just some of the factors affecting businesses. Other problems encountered, possible solutions to those problems and lessons to be learnt from each case study are also discussed. The research offers entrepreneurs, ICT practitioners, and policy makers the platform to understand the Why and How FOSS technologies are impacting the traditional way of doing business in Sub-Saharan Africa.},
	author = {Sowe, Sulayman K. and McNaughton, Maurice}
}
@article {1381,
	title = {Adopting Free/Libre/Open Source Software Practices, Techniques and Methods for Industrial Use},
	journal = {Journal of the Association for Information Systems},
	volume = {12},
	number = {1},
	year = {2011},
	abstract = {Today{\textquoteright}s software companies face the challenges of highly distributed development projects and constantly changing requirements. This paper proposes the adoption of relevant Free/Libre/Open Source Software (FLOSS) practices in order to improve software development projects in industry. Many FLOSS projects have proven to be very successful, producing high quality products with steady and frequent releases. This study aims to identify FLOSS practices that can be adapted for the corporate environment. To achieve this goal, a framework to compare FLOSS and industrial development methodologies was created. Three successful FLOSS projects were selected as study targets (the Linux Kernel, the FreeBSD operating system, and the JBoss application server), as well as two projects from Ericsson, a large telecommunications company. Based on an analysis of these projects, FLOSS best practices were tailored to fit industrial development environments. The final results consisted of a set of key adoption opportunities that aimed to improve software quality and overall development productivity by importing best practices from the FLOSS environment. The adoption opportunities were then validated at three large corporations.},
	keywords = {freebsd, jboss, linux, linux kernel},
	url = {http://aisel.aisnet.org/jais/vol12/iss1/1},
	author = {Torkar, Richard and Minoves, Pau and Garrig{\'o}s, Janina}
}
@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 {1278,
	title = {Building Knowledge in Open Source Software Research in Six Years of Conferences},
	year = {2011},
	note = {RQ1. Is there any social network underlying the research production at the OSS conference series?
RQ2. What are the major streams of research proposed at the OSS conference series?},
	month = {10/2011},
	pages = {123-141},
	publisher = {Springer},
	abstract = {Since its origins, the diffusion of the OSS phenomenon and the information about it has been entrusted to the Internet and its virtual communities of developers. This public mass of data has attracted the interest of researchers and practitioners aiming at formalizing it into a body of knowledge. To this aim, in 2005, a new series of conferences on OSS started to collect and convey OSS knowledge to the research and industrial community. Our work mines articles of the OSS conference series to understand the process of knowledge grounding and the community surrounding it. As such, we propose a semi-automated approach for a systematic mapping study on these articles. We automatically build a map of cross-citations among all the papers of the conferences and then we manually inspect the resulting clusters to identify knowledge building blocks and their mutual relationships. We found that industry-related, quality assurance, and empirical studies often originate or maintain new streams of research.},
	keywords = {Cross-citations, flossmole cited, graph, literature review, network, research, Systematic Mapping Study},
	author = {Mulazzini, Fabio and Rossi, Bruno and Russo, Barbara and Steff, Maximilian}
}
@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.}
}
@conference {1313,
	title = {Do comments explain codes adequately?},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {242-245},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Comment lines in the software source code include descriptions of codes, usage of codes, copyrights, unused codes, comments, and so on. It is required for comments to explain the content of written code adequately, since the wrong description in the comment may causes further bug and confusion in maintenance.

In this paper, we try to clarify a research question: "In which projects do comments describe the code adequately?" To answer this question, we selected the group 1 of mining challenge and used data obtained from Eclipse and Netbeans. Since it is difficult to answer the above question directly, we define the distance between codes and comments. By utilizing the fault-prone module prediction technique, we can answer the alternative question from the data of two projects. The result shows that Eclipse project has relatively adequate comments.},
	keywords = {comments, eclipse, msr challenge, netbeans, prediction},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985482},
	author = {Mizuno, Osamu and Hirata, Yukinao}
}
@conference {1304,
	title = {Entering the circle of trust},
	booktitle = {Proceeding of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"we started by analyzing 219 projects"
},
	month = {05/2011},
	pages = {133-142},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {The success of an open-source project depends to a large degree on the proactive and constructive participation by the developer community. An important role that developers play in a project is that of a code committer. However, code-commit privilege is typically restricted to the core group of a project. In this paper, we study the phenomenon of the induction of external developers as code committers. The trustworthiness of an external developer is one of the key factors that determines the granting of commit privileges. Therefore, we formulate different hypotheses to explain how the trust is established in practice. To investigate our hypotheses, we developed an automated approach based on mining code repositories and bug-tracking systems. We implemented the approach and performed an empirical study, using the Eclipse projects, to test the hypotheses. Our results indicate that, most frequently, developers establish trust and credibility in a project by contributing to the project in a non-committer role. Moreover, the employing organization of a developer is another factor--although a less significant one--that influences trust.},
	keywords = {bug tracking, bug tracking system, commits, committers, core, developers, eclipse, trust},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985462},
	author = {Mani, Senthil and Sinha, Saurabh and Sinha, Vibha Singhal}
}
@proceedings {1297,
	title = {Forge.mil: A Case Study for Utilizing Open Source Methodologies Inside of Government},
	year = {2011},
	month = {10/2011},
	pages = {334-337},
	publisher = {Springer},
	abstract = {In late 2008, DISA (Defense Information Systems Agency), the global IT arm of the US Department of Defense, embarked upon a project to create an internal collaboration and software application lifecycle management system. Beyond simply fielding yet another tool, the Forge.mil effort was designed to fundamentally change the way the DoD developed and acquired software technology and systems. The method of this change was the application of Open Source principles inside of the larger DoD community, including ideas such as meritocracy and code sharing, as well as Agile and collaborative software development. This lightning talk will explain the rationale behind Forge.mil, how it was developed using Open Source principles, and how it continues to influence technology acquisition within the DoD in both practice and policy changes.},
	author = {Martin, Guy and Lippold, Aaron}
}
@proceedings {1272,
	title = {Ginga-J: An Open Java-Based Application Environment for Interactive Digital Television Services},
	year = {2011},
	month = {10/2011},
	pages = {34-49},
	publisher = {Springer},
	abstract = {This paper aims to present a Ginga-J{\textquoteright}s reference implementation. Although based on a particular platform, the implementation not only works as a proof of concept, but also raised several issues and difficulties on the software architecture project that should be taken into account to ease extensibility and porting to other platforms. Ginga is the standard middleware for the Brazilian DTV System. Its imperative environment (Ginga-J) is based on new JavaDTV specification and mandatory for fixed terrestrial receptors.},
	author = {Kulesza, Raoni and Lima, Jefferson F.A. and Guedes, Alan L. and Junior, Lucenildo L.A. and Meira, Silvio R.L. and Filho, Guido L.S.}
}
@conference {1307,
	title = {How do developers blog?},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {publishing frequency, post structure, word usage, publication patterns, content},
	month = {05/2011},
	pages = {123-132},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {We report on an exploratory study, which aims at understanding how software developers use social media compared to conventional development infrastructures. We analyzed the blogging and the committing behavior of 1,100 developers in four large open source communities. We observed that these communities intensively use blogs with one new entry about every 8 hours. A blog entry includes 14 times more words than a commit message. When analyzing the content of the blogs, we found that most popular topics represent high-level concepts such as functional requirements and domain concepts. Source code related topics are covered in less than 15\% of the posts. Our results also show that developers are more likely to blog after corrective engineering and management activities than after forward engineering and re-engineering activities. Our findings call for a hypothesis-driven research to further understand the role of social media in software engineering and integrate it into development processes and tools.},
	keywords = {blog, communication, developer, eclipse, gnome, LDA, postgres, python},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985461},
	author = {Maalej, Walid and Pagano, Dennis}
}
@conference {1306,
	title = {Java generics adoption},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"we automatically analyzed 20 open source software projects. We analyzed the top {\textquotedblleft}most used{\textquotedblright} projects according to ohloh.net, including only projects with significant amounts of Java code"

"The 20 selected projects were Ant, Azureus, CheckStyle, Commons Collections, Free- Mind, FindBugs, Jetty, JEdit, JDT, JUnit, Eclipse-cs, Hibernate, Log4j, Lucene, Maven, the Spring Frame- work, Squirrel-SQL, Subclipse, Weka, and Xerces."

"In mining the full version histories of these 20 projects, we analyzed the full content of each version of each Java source file, a total of 548,982,841 lines."},
	month = {05/2011},
	pages = {3-12},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Support for generic programming was added to the Java language in 2004, representing perhaps the most significant change to one of the most widely used programming languages today. Researchers and language designers anticipated this addition would relieve many long-standing problems plaguing developers, but surprisingly, no one has yet measured whether generics actually provide such relief. In this paper, we report on the first empirical investigation into how Java generics have been integrated into open source software by automatically mining the history of 20 popular open source Java programs, traversing more than 500 million lines of code in the process. We evaluate five hypotheses, each based on assertions made by prior researchers, about how Java developers use generics. For example, our results suggest that generics do not significantly reduce the number of type casts and that generics are usually adopted by a single champion in a project, rather than all committers.},
	keywords = {commits, generics, java, source code, version history},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985446},
	author = {Christian Bird and Murphy-Hill, Emerson and Parnin, Chris}
}
@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.}
}
@article {1322,
	title = {The Ontology of the OSS Business Model},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {39 - 59},
	abstract = {This study focuses on theory building providing a holistic conceptual framework that consists of an ontology based OSS business model and an OSS business model taxonomy. The study extends existing theory in OSS business models and corresponding taxonomies, based on the structured-case methodological approach. An exploratory study is conducted in two research cycles, for the identification, validation, and evaluation of the critical constructs of an OSS business model. Results reveal that OSS business models differ from traditional software business models, having specific features that affect the software value chain, the infrastructure, and the revenue model of an OSS oriented firm.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011010103},
	author = {Lakka, Spyridoula and Stamati, Teta and Michalakelis, Christos and Martakos, Dracoulis}
}
@proceedings {1299,
	title = {Open Source Software for Model Driven Development: A Case Study},
	year = {2011},
	month = {10/2011},
	pages = {348-367},
	publisher = {Springer},
	abstract = {Model Driven Development (MDD) is widely used in the embedded systems domain, and many proprietary and Open Source tools exist that support MDD. The potential for sustainability of such tools needs to assessed prior to any organisational adoption. In this paper we report from a case study conducted in a consultancy company context aiming to investigate Open Source tools for MDD. For the company it was interesting to explore the two Open Source modelling tools Topcased and Papyrus for potential adoption. The focus for our case study is on assessing the health of the ecosystems for the two investigated Open Source projects by means of quantitative analysis of publically available data sources about Open Source projects. The health of ecosystems is an important prerequisite for a long term sustainable OSS (Open Source Software) tool-chain in the MDD area, which can aid strategic decision making for potential adoption within a company context. We have established details on the extent to which developers and users are active in two specific OSS ecosystems, and identified organisational influence for both ecosystems. We find that the investigated tools are promising regarding the health of their ecosystems, and a natural next step for the company would be to proceed with a pilot study in order to analyse the effectiveness of the investigated tools in company contexts.},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn and Mattsson, Anders}
}
@article {1323,
	title = {OSS-TMM},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {1 - 22},
	abstract = {Open Source Software (OSS) products do not usually follow traditional software engineering development paradigms. Specifically, testing activities in OSS development may be quite different from those carried out in Closed Source Software (CSS) development. As testing and verification require a good deal of resources in OSS, it is necessary to have ways to assess and improve OSS testing processes. This paper provides a set of testing guidelines and issues that OSS developers can use to decide which testing techniques make most sense for their OSS products. This paper 1) provides a checklist that helps OSS developers identify the most useful testing techniques according to the main characteristics of their products, and 2) outlines a proposal for a method that helps assess the maturity of OSS testing processes. The method is a proposal of a Maturity Model for testing processes (called OSS-TMM). To show its usefulness, the authors apply the method to seven real-life projects. Specifically, the authors apply the method to BusyBox, Apache Httpd, and Eclipse Test \& Performance Tools Platform to show how the checklist supports and guides the testing process of these OSS products.},
	keywords = {testing},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011040101},
	author = {Morasca, Sandro and Taibi, Davide and Tosi, Davide}
}
@proceedings {1275,
	title = {Preparing FLOSS for Future Network Paradigms: A Survey on Linux Network Management},
	year = {2011},
	month = {10/2011},
	pages = {75-89},
	publisher = {Springer},
	abstract = {Operating system tools must fulfill the requirements generated by the advances in networking paradigms. To understand the current state of the Free, Libre and Open Source Software (FLOSS) ecosystem, we present a survey on the main tools used to manage and interact with the network, and how they are organized in Linux-based operating systems. Based on the survey results, we present a reference Linux network stack that can serve as the basis for future heterogeneous network environments, contributing towards a standardized approach in Linux. Using this stack, and focusing on dynamic and spontaneous network interactions, we present an evolution path for network related technologies, contributing to Linux as a network research operating system and to FLOSS as a whole.},
	keywords = {linux, networking, Survey},
	author = {Matos, Alfredo and Thomson, John and Paulo Trezentos}
}
@conference {Meneely:2011:SDN:1985793.1985832,
	title = {Socio-technical developer networks: should we trust our measurements?},
	booktitle = {Proceedings of the 33rd International Conference on Software Engineering},
	series = {ICSE {\textquoteright}11},
	year = {2011},
	pages = {281{\textendash}290},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software development teams must be properly structured to provide effectiv collaboration to produce quality software. Over the last several years, social network analysis (SNA) has emerged as a popular method for studying the collaboration and organization of people working in large software development teams. Researchers have been modeling networks of developers based on socio-technical connections found in software development artifacts. Using these developer networks, researchers have proposed several SNA metrics that can predict software quality factors and describe the team structure. But do SNA metrics measure what they purport to measure? The objective of this research is to investigate if SNA metrics represent socio-technical relationships by examining if developer networks can be corroborated with developer perceptions. To measure developer perceptions, we developed an online survey that is personalized to each developer of a development team based on that developer{\textquoteright}s SNA metrics. Developers answered questions about other members of the team, such as identifying their collaborators and the project experts. A total of 124 developers responded to our survey from three popular open source projects: the Linux kernel, the PHP programming language, and the Wireshark network protocol analyzer. Our results indicate that connections in the developer network are statistically associated with the collaborators whom the developers named. Our results substantiate that SNA metrics represent socio-technical relationships in open source development projects, while also clarifying how the developer network can be interpreted by researchers and practitioners.},
	keywords = {developer network, developers, linux, linux kernel, PHP, social network analysis, Survey, wireshark},
	isbn = {978-1-4503-0445-0},
	doi = {10.1145/1985793.1985832},
	url = {http://doi.acm.org/10.1145/1985793.1985832},
	author = {Meneely, Andrew and Williams, Laurie}
}
@proceedings {1287,
	title = {To Fork or Not to Fork: Fork Motivations in SourceForge Projects},
	year = {2011},
	note = {"Using this search function, we compiled a list of all of the programs with the word {\textquotedblleft}fork{\textquotedblright}..."
"We then analyzed the motivations stated in the descriptions of the forked programs...."
"Based on the descriptions entered by the developer, we were able to identify motivations for 381 of the forks."
},
	month = {10/2011},
	pages = {259-268},
	publisher = {Springer},
	abstract = {A project fork occurs when software developers take a copy of source code from one software package and use it to begin an independent development work that is maintained separately from its origin. Although forking in open source software does not require the permission of the original authors, the new version, nevertheless, competes for the attention of the same developers that have worked on the original version. The motivations developers have for performing forks are many, but in general they have received little attention. In this paper, we present the results of a study of forks performed in SourceForge (http://sourceforge.net/) and list the developers{\textquoteright} motivations for their actions. The main motivation, seen in close to half of the cases of forking, was content modification; either adding content to the original program or focusing the content to the needs of a specific segment of users. In a quarter of the cases the motivation was technical modification; either porting the program to new hardware or software, or improving the original.},
	keywords = {fork rate, sourceforge},
	author = {Nyman, Linus and Mikkonen, Tommi}
}
@conference {1305,
	title = {Visualizing collaboration and influence in the open-source software community},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"This data set includes the complete social graph of 500,000 follow links as well as over 1,000,000 commits and 50,000 users."

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

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

"In addition to crawled data, we use the complete GitHub user follower graph from Jan 19, 2011. This graph includes 452,248 links connecting 106,247 unique users, 47\% (49,500) of which could be geocoded with the PlaceFinder API"},
	month = {05/2011},
	pages = {223-226},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {We apply visualization techniques to user profiles and repository metadata from the GitHub source code hosting service. Our motivation is to identify patterns within this development community that might otherwise remain obscured. Such patterns include the effect of geographic distance on developer relationships, social connectivity and influence among cities, and variation in project-specific contribution styles (e.g., centralized vs. distributed). Our analysis examines directed graphs in which nodes represent users{\textquoteright} geographic locations and edges represent (a) follower relationships, (b) successive commits, or (c) contributions to the same project. We inspect this data using a set of visualization techniques: geo-scatter maps, small multiple displays, and matrix diagrams. Using these representations, and tools based on them, we develop hypotheses about the larger GitHub community that would be difficult to discern using traditional lists, tables, or descriptive statistics. These methods are not intended to provide conclusive answers; instead, they provide a way for researchers to explore the question space and communicate initial insights.},
	keywords = {COLLABORATION, data exploration, geography, geoscatter, github, graph, mapping, metadata, open source, social graph, user profiles, visualization},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985476},
	url = {http://vis.stanford.edu/files/2011-GotHub-MSR.pdf},
	author = {Marschner, Eli and Rosenfeld, Evan and Heer, Jeffrey and Heller, Brandon}
}
@proceedings {1378,
	title = {When Cultures Clash: Participation in Open Source Communities and Its Implications For Organizational Commitment},
	number = {7},
	year = {2011},
	abstract = {Software applications developed within the OSS community have enjoyed tremendous success and for-profit organizations are keen to tap into this significant pool of software development talent (Chesbrough 2003; Feller et al. 2008). Examples companies include Netscape, IBM and Google (Maccormack et al. 2006). These companies seek to benefit from the talent of a global and sometimes voluntary workforce by paying some employees to contribute to OSS projects (Raymond 1999, Shah 2006). This merging of open and traditional software development may cause developer stress based on conflicting OSS community and traditional software development norms. Specifically, developers must balance company intellectual property concerns with the reciprocal and community-based norms that drive OSS development (Stewart and Gosain 2006). When these values are not in sync, contributors that aim to abide by conflicting values may exhibit dysfunctional attitudes. Employee stress with respect to their role can be destructive to organizational outcomes (Maas and Matejka 2009; Aranya and Ferris 1984). This study develops an OSS context specific model that describes the relationship between clashing software development cultures and employee organizational commitment. We leverage the rich OSS literature and the research that focuses on organizational-professional conflict (OPC) to develop hypotheses linking clashing cultures and organizational commitment. These hypotheses are tested using a combination of archival data and a survey of 127 GNOME developers. The findings presented in this paper contribute to OSS literature and offer findings that will enable organizations to more successfully engage OSS communities.},
	keywords = {gnome},
	url = { http://aisel.aisnet.org/icis2011/proceedings/projmanagement/7 },
	author = {Daniel, Sherae L. and Maruping, Likoebe M. and Cataldo, Marcelo and Herbsleb, James}
}
@article {1382,
	title = {Analysis of virtual communities supporting OSS projects using social network analysis},
	journal = {Information and Software Technology},
	volume = {52},
	year = {2010},
	month = {3/2010},
	pages = {296 - 303},
	abstract = {This paper analyses the behaviour of virtual communities for Open Source Software (OSS) projects. The development of OSS projects relies on virtual communities, which are built on relationships among members, being their final objective sharing knowledge and improving the underlying project. This study addresses the interactive collaboration in these kinds of communities applying social network analysis (SNA). In particular, SNA techniques will be used to identify those members playing a middle-man role among other community members. Results will illustrate the importance of this role to achieve successful virtual communities.},
	keywords = {arm, email, Knowledge brokers, linux, mailing list, open source software, social network analysis, virtual communities},
	issn = {09505849},
	doi = {10.1016/j.infsof.2009.10.007},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584909001888},
	author = {Toral, S.L. and Mart{\'\i}nez-Torres, M.R. and Barrero, F.}
}
@conference {968,
	title = {Can development work describe itself?},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {191 - 200},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Work descriptions are informal notes taken by developers to summarize work achieved in a particular session. Existing studies indicate that maintaining them is a distracting task, which costs a developer more than 30 min. a day. The goal of this research is to analyze the purposes of work descriptions, and find out if automated tools can assist developers in efficiently creating them. For this, we mine a large dataset of heterogeneous work descriptions from open source and commercial projects. We analyze the semantics of these documents and identify common information entities and granularity levels. Information on performed actions, concerned artifacts, references and new work, shows the work management purpose of work descriptions. Information on problems, rationale and experience shows their knowledge sharing purpose. We discuss how work description information, in particular information used for work management, can be generated by observing developers{\textquoteright} interactions. Our findings have many implications for next generation software engineering tools.},
	keywords = {developer interactions, work descriptions},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463344},
	author = {Maalej, Walid and Happel, Hans-Jorg}
}
@inbook {836,
	title = {Collaboration Practices and Affordances in Free/Open Source Software Development},
	booktitle = {Collaborative Software Engineering},
	year = {2010},
	pages = {307-328},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This chapter examines collaborative work practices, development processes, project and community dynamics, and other socio-technical relationships in free and open source software development (FOSSD). It also describes what kinds of collaboration affordances facilitate collaborative work in FOSSD projects. It reviews a set of empirical studies of FOSSD that articulate different levels of analysis. Finally, there is discussion of limitations and constraints in understanding what collaboration practices and affordances arise in FOSSD studies and how they work, and then to emerging opportunities for future FOSSD studies.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CoSE-Scacchi-Chapter.pdf},
	author = {Walt Scacchi},
	editor = {Finkelstein, A. and van der Hoek, A. and Grundy, J. and Mistr{\'\i}k, I. and Whitehead, J.}
}
@article {1330,
	title = {Data Mining User Activity in Free and Open Source Software (FOSS)/ Open Learning Management Systems},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {65 - 75},
	abstract = {Free and Open Source Software (FOSS)/Open Educational Systems development projects abound in higher education today. Many universities worldwide have adopted open source software like ATutor and Moodle as an alternative to commercial or homegrown systems. The move to open source learning management systems entails many special considerations, including usage analysis facilities. The tracking of users and their activities poses major technical and analytical challenges within web-based systems. This paper examines how user activity tracking challenges are met with data mining techniques, particularly web usage mining methods, in four different open learning management systems: ATutor, LON-CAPA, Moodle, and Sakai. As examples of data mining technologies adapted within widely used systems, they represent important first steps for moving educational data mining outside the research laboratory. Moreover, as examples of different open source development contexts, exemplify the potential for programmatic integration of data mining technology processes in the future. As open systems mature in the use of educational data mining, they move closer to the long-sought goal of achieving more interactive, personalized, adaptive learning environments online on a broad scale.},
	keywords = {data mining, education, student},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010010105},
	author = {McGrath, Owen}
}
@inbook {springerlink:10.1007/978-3-642-13244-5_20,
	title = {Download Patterns and Releases in Open Source Software Projects: A Perfect Symbiosis?},
	booktitle = {Open Source Software: New Horizons},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {319},
	year = {2010},
	note = {"We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository."},
	pages = {252-267},
	publisher = {Springer Boston},
	organization = {Springer Boston},
	abstract = {Software usage by end-users is one of the factors used to evaluate the success of software projects. In the context of open source software, there is no single and non-controversial measure of usage, though. Still, one of the most used and readily available measure is data about projects downloads. Nevertheless, download counts and averages do not convey as much information as the patterns in the original downloads time series. In this research, we propose a method to increase the expressiveness of mere download rates by considering download patterns against software releases. We apply experimentally our method to the most downloaded projects of SourceForge{\textquoteright}s history crawled through the FLOSSMole repository. Findings show that projects with similar usage can have indeed different levels of sensitivity to releases, revealing different behaviors of users. Future research will develop further the pattern recognition approach to automatically categorize open source projects according to their download patterns.},
	keywords = {flossmole, oss2010, sourceforge},
	url = {http://dx.doi.org/10.1007/978-3-642-13244-5_20},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s and Madey, Gregory and Noll, John}
}
@conference {951,
	title = {The evolution of ANT build systems},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {42 - 51},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Build systems are responsible for transforming static source code artifacts into executable software. While build systems play such a crucial role in software development and maintenance, they have been largely ignored by software evolution researchers. With a firm understanding of build system aging processes, project managers could allocate personnel and resources to build system maintenance tasks more effectively, reducing the build maintenance overhead on regular development activities. In this paper, we study the evolution of ANT build systems from two perspectives: (1) a static perspective, where we examine the build system specifications using software metrics adopted from the source code domain; and (2) a dynamic perspective where representative sample build runs are conducted and their output logs are analyzed. Case studies of four open source ANT build systems with a combined history of 152 releases show that not only do ANT build systems evolve, but also that they need to react in an agile manner to changes in the source code.},
	keywords = {ant, argouml, build, eclipse, jboss, maintenance, metrics, source code, tomcat},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463341},
	attachments = {https://flosshub.org/sites/flosshub.org/files/42msr2010_mcintosh.pdf},
	author = {McIntosh, Shane and Adams, Bram and Hassan, Ahmed E.}
}
@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 {1257,
	title = {The Importance of Social Network Structure in the Open Source Software Developer Community},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences},
	year = {2010},
	note = {"Using data from the SourceForge Research Data Archive [2, 9] and the new dataset of concurrent versions system (CVS) metadata described in [8]..." (M. Van Antwerp. Studying open source versioning metadata. Master{\textquoteright}s thesis, University of NotreDame, Notre Dame, IN, January 2009)
"To measure long-term popularity, we used the SourceForge activity percentile."},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {This paper outlines the motivations and methods for analyzing the developer network of open source software (OSS) projects. Previous work done by Hinds [5] suggested social network structure was instrumental towards the success of an OSS project, as measured by activity and output. The follow-up paper by Hinds [4] discovered that his hypotheses, based on social network theory and previous research on the importance of subgroup connectedness, were vastly different than the results of his study of over 100 successful OSS projects. He concluded that the social network structure had no significant effect on project success. We outline how his approach disregarded potentially important factors and through a new study evaluate the role of the OSS developer network as it pertains to long-term project popularity. We also present an initial investigation into the adequacy of using the SourceForge activity percentile as a long-term success metric. In contrast with Hinds, we show that previously existing developer-developer ties are an indicator of past and future project popularity.},
	keywords = {developers, popularity, project success, social network analysis, sourceforge, srda},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.385},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-06-07.pdf},
	author = {Matthew Van Antwerp and Madey, Greg}
}
@conference {956,
	title = {Mining security changes in FreeBSD},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {90 - 93},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Current research on historical project data is rarely touching on the subject of security related information. Learning how security is treated in projects and which parts of a software are historically security relevant or prone to security changes can enhance the security strategy of a software project. We present a mining methodology for security related changes by modifying an existing method of software repository analysis. We use the gathered security changes to find out more about the nature of security in the FreeBSD project and we try to establish a link between the identified security changes and a tracker for security issues (security advisories). We give insights how security is presented in the FreeBSD project and show how the mined data and known security problems are connected.},
	keywords = {freebsd, msr challenge, security},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463289},
	author = {Mauczka, Andreas and Schanes, Christian and Fankhauser, Florian and Bernhart, Mario and Grechenig, Thomas}
}
@conference {964,
	title = {Mining subclassing directives to improve framework reuse},
	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 = {141 - 150},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {To help developers in using frameworks, good documentation is crucial. However, it is a challenge to create high quality documentation especially of hotspots in white-box frameworks. This paper presents an approach to documentation of object-oriented white-box frameworks which mines from client code four different kinds of documentation items, which we call subclassing directives. A case study on the Eclipse JFace user-interface framework shows that the approach can improve the state of API documentation w.r.t. subclassing directives.},
	keywords = {api, documentation, eclipse, frameworks, jface, source code},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463347},
	attachments = {https://flosshub.org/sites/flosshub.org/files/141Mining-Subclassing-Directives-to-Improve-Framework-Reuse.pdf},
	author = {Bruch, Marcel and Mezini, Mira and Monperrus, Martin}
}
@conference {1224,
	title = {On the Need for OSS Patch Contribution Tools},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	abstract = {Open Source Software (OSS) projects and systems have become significant parts of the software economy. The sustainability of an OSS project depends largely on community contributions. The patch contribution process is important to OSS projects. Nevertheless, there are several issues negatively impacting patch contribution in mature OSS projects. These issues can be addressed by improving tools to support the patch contribution process.},
	keywords = {apache, kanban, patch, patch acceptance, patches},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm004.pdf},
	author = {Bhuricha Deen Sethanandha and Bart Massey and William Jones}
}
@article {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}
}
@book {1249,
	title = {Open Source Software Developer and Project Networks},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: New Horizons},
	volume = {319},
	year = {2010},
	note = {no information on data gathering procedures},
	pages = {407 - 412},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {This paper outlines complex network concepts and how social networks are built from Open Source Software (OSS) data. We present an initial study of the social networks of three different OSS forges, BerliOS Developer, GNU Savannah, and SourceForge. Much research has been done on snapshot or conflated views of these networks, especially SourceForge, due to the size of the SourceForge community. The degree distribution, connectedness, centrality, and scale-free nature of SourceForge has been presented for the network at particular points in time. However, very little research has been done on how the network grows, how connections were made, especially during its infancy, and how these metrics evolve over time. },
	keywords = {berlios, savannah, sourceforge},
	isbn = {978-3-642-13244-5},
	issn = {1861-2288},
	doi = {10.1007/978-3-642-13244-5_39},
	author = {Madey, G. and van Antwerp, M.},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Madey, Gregory R. and Noll, John}
}
@conference {962,
	title = {OSS developers context-specific Preferred Representational systems: A initial Neurolinguistic text analysis of the Apache mailing list},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {126 - 129},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Open Source Software (OSS) mailing lists are used by developers to discuss software engineering tasks performed in the project. In the last years, researchers have been conducting mailing lists linguistic analyses for understanding the intricacies of OSS development. An unpublished approach for that is to use NeuroLinguistic Theory (NT). NT postulates the use of a Preferred Representational cognitive System (PRS) in specific contexts. This means that different resources and cognitive channels are used by developers in order to understand software, but what types of representational systems are the preferred by software engineers? This paper introduces a psychometrically-based neuro-linguistic analysis tool to classify developers, and presents early results of an experiment to assess the PRS of four top developers against a baseline of the Apache server mailing list.},
	keywords = {apache, email, email archives, mailing lists, neurolinguistics},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463339},
	author = {Junior, Methanias Colaco and Mendonca, Manoel and Farias, Mario and Henrique, Paulo}
}
@conference {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 {Rastkar:2010:SSA:1806799.1806872,
	title = {Summarizing software artifacts: a case study of bug reports},
	booktitle = {Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1},
	series = {ICSE {\textquoteright}10},
	year = {2010},
	pages = {505{\textendash}514},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Many software artifacts are created, maintained and evolved as part of a software development project. As software developers work on a project, they interact with existing project artifacts, performing such activities as reading previously filed bug reports in search of duplicate reports. These activities often require a developer to peruse a substantial amount of text. In this paper, we investigate whether it is possible to summarize software artifacts automatically and effectively so that developers could consult smaller summaries instead of entire artifacts. To provide focus to our investigation, we consider the generation of summaries for bug reports. We found that existing conversation-based generators can produce better results than random generators and that a generator trained specifically on bug reports can perform statistically better than existing conversation-based generators. We demonstrate that humans also find these generated summaries reasonable indicating that summaries might be used effectively for many tasks.},
	keywords = {bug reports, eclipse, gnome, human-centric software engineering, kde, machine learning, mozilla},
	isbn = {978-1-60558-719-6},
	doi = {10.1145/1806799.1806872},
	url = {http://doi.acm.org/10.1145/1806799.1806872},
	author = {Rastkar, Sarah and Murphy, Gail C. and Murray, Gabriel}
}
@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.}
}
@book {1250,
	title = {Warehousing and Studying Open Source Versioning Metadata},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: New Horizons (OSS 2010)},
	volume = {319},
	year = {2010},
	pages = {413 - 418},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {In this paper, we describe the downloading and warehousing of Open Source Software (OSS) versioning metadata from SourceForge, BerliOS Developer, and GNU Savannah. This data enables and supports research in areas such as software engineering, open source phenomena, social network analysis, data mining, and project management. This newly-formed database containing Concurrent Versions System (CVS) and Subversion (SVN) metadata offers new research opportunities for large-scale OSS development analysis. The CVS and SVN data is juxtaposed with the SourceForge.net Research Data Archive [5] for the purpose of performing more powerful and interesting queries. We also present an initial statistical analysis of some of the most active projects. },
	keywords = {berlios, cvs, savannah, scm, sourceforge, srda, subversion, svn},
	isbn = {978-3-642-13244-5},
	issn = {1861-2288},
	doi = {10.1007/978-3-642-13244-5_40},
	author = {van Antwerp, M. and Madey, G.},
	editor = {{\r A}gerfalk, P{\"a}r and Boldyreff, Cornelia and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Madey, Gregory R. and Noll, John}
}
@conference {601,
	title = {1st International Workshop on: {\textquoteleft}Designing for Participatory Learning{\textquoteright} Building from Open Source Success to Develop Free Ways to Share and Learn},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {355 - 356},
	publisher = {Springer},
	organization = {Springer},
	chapter = {33},
	abstract = {The Open Source world shows how volunteer collaboration can lead to great products and to great learning. We want to further explore at this workshop what happens using approaches from that community to break barriers between teachers and learners for today{\textquoteright}s Internet-savvy young people to design and co-construct sites for participatory learning. The aim of this workshop is to explore the barriers for this type of learning in higher education settings. Content creation, knowledge exchange, community
dynamics, and the impact on the boundary between formal and informal education are key subjects of this workshop.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1st\%20International\%20Workshop\%20on.pdf},
	author = {Andreas Meiszner and Ioannis Stamelos and Sowe, Sulayman}
}
@conference {839,
	title = {Amassing and indexing a large sample of version control systems: towards the census of public source code history},
	booktitle = {6th IEEE Working Conference on Mining Software Repositories},
	year = {2009},
	note = {Related work: "For example, FLOSSMole [8]
collects the list of projects and their metadata from SourceForge,
FreshMeat, Free Software Foundation (FSF), RubyForge,
and ObjectWeb. "

"The list of
home pages from open source directories such as FSF or
FLOSSMole could provide a focused set of web pages for
the search"

"To get the list of projects for SourceForge we used
FLOSSMole project [8] that collects the list of SourceForge
projects and their metadata. We use project ID, because it
was used to specify the VCS URL within the SourceForge
repository."},
	month = {May 16{\textendash}17},
	abstract = {The source code and its history represent the output and process of software development activities and are an in- valuable resource for study and improvement of software development practice. While individual projects and groups of projects have been extensively analyzed, some fundamental questions, such as the spread of innovation or genealogy of the source code, can be answered only by considering the entire universe of publicly available source code and its history. We describe methods we developed over the last six years to gather, index, and update an approximation of such a universal repository for publicly accessible version control systems and for the source code inside a large corporation. While challenging, the task is achievable with limited resources. The bottlenecks in network bandwidth, processing, and disk access can be dealt with using inherent parallelism of the tasks and suitable tradeoffs between the amount of storage and computations, but a completely automated discovery of public version control systems may require enticing participation of the sampled projects. Such universal repository would allow studies of global properties and origins of the source code that are not possible through other means.},
	keywords = {bazaar, cvs, flossmole, git, mercurial, source code, sourceforge, subversion, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/11amassing.pdf},
	author = {Audris Mockus}
}
@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 {572,
	title = {Design Evolution of an Open Source Project Using an Improved Modularity Metric},
	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 = {20 - 33},
	publisher = {Springer},
	organization = {Springer},
	chapter = {4},
	abstract = {Modularity of an open source software code base has been associated with community growth, incentives for voluntary contribution, and a reduction in free riding. As a theoretical construct, it links open source software to other domains of research, including organization theory, the economics of industry structure, and new product development; however, measuring the modularity of an open source software design has proven difficult, especially for large and complex systems. Building on previous work on Design Structure Matrices (DSMs), this paper describes two contributions towards a method for examining the evolving modularity of large-scale software systems: (1) an algorithm and new modularity metric for comparing code bases of different size; and (2) evolution analysis of Apache Tomcat to illustrate the insights gained from this approach. Over a ten-year period, the modularity of Tomcat continually increased, except in three instances: with each major change to the architecture or implementation, modularity first declined, then increased in the subsequent version to fully compensate for the decline.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Design\%20Evolution\%20of\%20an\%20Open\%20Source\%20Project.pdf},
	author = {Milev, Roberto and Muegge, Steven and Weiss, Michael}
}
@article {838,
	title = {Envisioning National and International Research on the Multidisciplinary Empirical Science of Free/Open Source Software},
	year = {2009},
	month = {Spring 2009},
	author = {Walt Scacchi and Kevin Crowston and Madey, Greg and Squire, Megan}
}
@conference {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 {936,
	title = {From work to word: How do software developers describe their work?},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {121 - 130},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Developers take notes about their work sessions, either to remember the work status and share it with collaborators, or because employers explicitly require this for project management matters. We report on an exploratory study which aims at understanding how software developers describe their work. We analyzed more than 750,000 work descriptions of about 2,000 professionals taken over 8 years in three settings. We observed several similarities in the content and time meta-data of work descriptions. Most frequent terms, such as top-30 performed activities, are used consistently. Particular templates such as ldquoACTION concerning ARTIFACT because of CAUSErdquo occur frequently. Developers described sessions that last 30-120 min. 4-16 times a day. Maintaining diaries seems to consume between 3-6\% of the total work time, and in 10\% of the sessions, developers did not describe their work in sufficient detail. We argue that our results make the first step towards automatically generating work diaries for software developers.},
	keywords = {apache, developers, diaries, eureka, mycomp, scm, work management system},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069490},
	author = {Maalej, Walid and Happel, Hans-Jorg}
}
@article {1352,
	title = {Identifying How Determinants Impact Security-Based Open Source Software Project Success Using Rule Induction},
	journal = {International Journal of Electronic Marketing and Retailing},
	volume = {2},
	number = {4},
	year = {2009},
	month = {2009},
	pages = {352-362},
	author = {Wray, Barry and Mathieu, Richard and Teets, 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.}
}
@conference {858,
	title = {Making New Friends, but Keep the Old - Recommending People on Social Networking Sites (forthcoming)},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2009},
	author = {Chen, J and Geyer, W. and Dugan, C. and Muller, M. and Guy, I.}
}
@article {1351,
	title = {Motivation of Open Source Developers},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {65 - 81},
	abstract = {The motivational drivers of open source software developers have been researched by various investigators since about 2000. This work shows that developers are motivated by different extrinsic and intrinsic drivers, among them community aspirations, reciprocity and fairness, creative impulses, and monetary and career ambitions. There has been some work done in studying whether the profile of developer motivations is constant across open source projects or is sensitive to project organizational design. Among the many factors that could influence the mix of motives of OS developers is the license under which the work is performed. Licenses range in openness between those such as the GNU GPL that severely restrict the freedom of developers to mingle their OS code with proprietary code to those such as BSD licenses which allow programmers much greater latitude in integrating open source code with proprietary code. In addition to formal rules, meritocracies emerge to reward effort and performance, and also to direct, coordinate, and control other participants. The authors discuss these variables and how they may be related to motivations.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009100104},
	author = {Allyn, Mark R. and Misra, Ram B.}
}
@conference {593,
	title = {Peeling the Onion},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {284 - 297},
	publisher = {Springer},
	organization = {Springer},
	chapter = {25},
	abstract = {According to the now widely accepted {\textquotedblleft}onion-model{\textquotedblright} of the organization of open source software development, an open source project typically relies on a core of developers that is assisted by a larger periphery of users. But what does the role of the periphery consist of? Raymond{\textquoteright}s Linus{\textquoteright}s Law which states that {\textquotedblleft}given enough eyeballs all bugs are shallow{\textquotedblright} suggests at least one important function: the detection of defects. Yet, what are the ways through which core and periphery interact with each other? With the help of text-mining methods, we study the treatment of bugs that affected the Firefox Internet browser as reflected in the discussions and actions recorded in Mozilla{\textquoteright}s issue tracking system Bugzilla. We find various patterns in the modes of interactions between core and peripheral members of the community. For instance, core members seem to engage more frequently with the periphery when the latter proposes a solution (a patch). This leads us to conclude that Alan Cox{\textquoteright}s dictum {\textquotedblleft}show me the code{\textquotedblright}, perhaps even more than Linus{\textquoteright}s law, seems to be the dominant rule that governs the development of software like Firefox.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_25},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Peeling\%20the\%20Onion.pdf},
	author = {Masmoudi, H{\'e}la and den Besten, Matthijs and de Loupy, Claude and Jean-Michel Dalle}
}
@conference {bird2009pat,
	title = {{Putting it All Together: Using Socio-Technical Networks to Predict Failures}},
	booktitle = {Proceedings of the 17th International Symposium on Software Reliability Engineering},
	year = {2009},
	note = {First, we build each type of network separately and use network analysis on both to gather metrics for use in a predictive model. Second, we build a socio-technical network which combines the nodes and edges from both the dependency network and the contribution network and use metrics gathered from this network in a predictive model.
We evaluate our approach by collecting data from Mi- crosoft Windows Vista and ECLIPSE development and using logistic regression analysis.},
	abstract = {Studies have shown that social factors in development organizations have a dramatic effect on software quality. Separately, program dependency information has also been used successfully to predict which software components are more fault prone. Interestingly, the influence of these two phenomena have only been studied separately. Intuition and practical experience suggests, however, that task assignment (i.e. who worked on which components and how much) and dependency structure (which components have dependencies on others) together interact to influence the quality of the resulting software. We study the influence of combined socio-technical software networks on the fault-proneness of individual software components within a system. The network properties of a software component in this combined network are able to predict if an entity is failure prone with greater accuracy than prior methods which use dependency or contribution information in isolation. We evaluate our approach in different settings by using it on Windows Vista and across six releases of the Eclipse development environment including using models built from one release to predict failure prone components in the next release. We compare this to previous work. In every case, our method performs as well or better and is able to more accurately identify those software components that have more post-release failures, with precision and recall rates as high as 85\%.},
	keywords = {eclipse, microsoft, social network, vista, windows},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2009pat.pdf},
	author = {Christian Bird and Nachiappan Nagappan and Devanbu, Premkumar and Gall, Harald and Brendan Murphy}
}
@conference {586,
	title = {Quality of Open Source Software: The QualiPSo Trustworthiness Model},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {199 - 212},
	publisher = {Springer},
	organization = {Springer},
	chapter = {18},
	abstract = {Trustworthiness is one of the main issues upon which the decision whether to adopt an Open-Source Software (OSS) product is based. The work described here is part of an activity that has the goals of 1) defining an adequate notion of trustworthiness of software products and artifacts and 2) identifying a number of factors that influence it. Specifically, this paper reports about the identification of the {\textquotedblleft}dimensions{\textquotedblright} of trustworthiness, i.e., of the high-level qualities that software products and artefacts have to posses in order to be considered trustworthy. These dimensions are described by means of a conceptual model of trustworthiness, which comprises the representation of the factors that affect the user{\textquoteright}s perception of trustworthiness, as well as the objective characteristics of the products that contribute to {\textquotedblleft}build{\textquotedblright} trustworthi-ness. The aforementioned model is equipped with a measurement plan that de-scribes, at the operational level, how to perform the evaluation of the trustwor-thiness of OSS products. The proposed model provides the basis to build quantitative models of the trustworthiness of OSS products and artifacts that are able to explain the relationships between the (objectively observable) characteristics of OSS products and the level of trustworthiness perceived by the users of such products.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Quality\%20of\%20Open\%20Source\%20Software.pdf},
	author = {del Bianco, Vieri and Lavazza, Luigi and Morasca, Sandro and Taibi, Davide}
}
@article {1082,
	title = {Returns from social capital in open source software networks},
	journal = {Journal of Evolutionary Economics},
	volume = {19},
	year = {2009},
	note = {"The data we use in this analysis come from the SourceForge.net Research Data (Department of Computer Science and Engineering, University of Notre Dame)." "Particularly, our dataset is a sub-sample of 2,962 valid observations over twelve months of projects aimed at developing games{\textquoteright} software. To get this sample, we look at the monthly dumps of data and select all projects that belong to the category of GNU Public License (GPL) [6]. "
dependent variable: performance (number of downloads); independent variable: social network ("Here we measure ties among projects through the individuals{\textquoteright} member and contributor roles at projects on the network over time.)},
	month = {4/2009},
	pages = {277 - 295},
	abstract = {Open Source Software projects base their operation on a collaborative structure for knowledge exchange in the form of provision or reception of information, expertise, and feedback on the creation of source code. Here, we address the direction of these knowledge flows among projects throughout social networks and their impact on project success. We identify the roles of membership or contribution that individuals play within projects. We found that connections through contributors who bring their knowledge to the project, improve project success, and that connection through members, who transfer their knowledge towards other projects, enhance project success. Finally, we found that ties through shared membership and contributions hamper project success. The analysis of knowledge flows and their impact on project success imply a translation of returns from investment in social capital, where investment takes the shape of knowledge flows and the returns mean the projects{\textquoteright} diffusion over the network.},
	keywords = {contributors, developers, games, gpl, project success, roles, social capital, social network analysis, social networks, sourceforge, srda, teams},
	issn = {1432-1386},
	doi = {10.1007/s00191-008-0125-5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Mendez-DuronGarcia.pdf},
	author = {M{\'e}ndez-Dur{\'o}n, Rebeca and Garc{\'\i}a, Clara E.}
}
@article {1350,
	title = {Strategies for Improving Open Source Software Usability},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {49 - 64},
	abstract = {The Open Source Software (OSS) movement has had enormous impact on how software is created and continues to attract interest from researchers, software developers and users. A factor that may be inhibiting OSS from achieving greater success is usability, a fundamental characteristic to user acceptance of software. Motivated by the uniquely user-driven nature of the open source model and the extensive user base that participates in OSS projects, the authors propose an exploratory learning method and an associated web-based inspection environment that enables non-experts to contribute to open source usability inspection. This tool uses patternbased usability guidelines to help identify usability knowledge during inspection. The method emphasizes outlining and exploration features which the authors have formally evaluated and the results of which are described. Data collected from a qualitative study indicates positive impact of the proposed method in helping end-users inspect software and achieve better results in discovering usability problems.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009100103},
	author = {Zhao, Luyin and Deek, Fadi P. and McHugh, James A.}
}
@conference {840,
	title = {Succession: Measuring Transfer of Code and Developer Productivity},
	booktitle = {2009 International Conference on Software Engineering},
	year = {2009},
	month = {May 12{\textendash}22},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Vancouver, CA},
	author = {Audris Mockus}
}
@conference {588,
	title = {A Survey on Firms{\textquoteright} Participation in Open Source Community Projects},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	year = {2009},
	month = {2009///},
	pages = {225 - 236},
	publisher = {Springer},
	organization = {Springer},
	chapter = {20},
	abstract = {The role of firms in commercial Open Source projects (e.g., former MySQL, EnterpriseDB, SugarCRM) is a consolidated and generally accepted fact. On other hand, community Open Source projects, which are built upon communities and not directly associated with firms, are commonly perceived to be based mainly on the work of volunteers. Up to now, firms{\textquoteright} role in these projects has been poorly investigated. We conducted a survey on 1,302 SourceForge.net projects to inquire about the level and the typology of involvement of firms. We propose three different models for firm participation and provide empirical evidence on their diffusion in SourceForge.net.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Survey\%20on\%20Firns\%27\%20Participation.pdf},
	author = {Capra, Eugenio and Francalanci, Chiara and Merlo, Francesco and Rossi Lamastra, Cristina}
}
@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}
}
@inbook {855,
	title = {Understanding Requirements for Open Source Software},
	booktitle = {Design Requirements Engineering: A Ten-Year Perspective},
	series = {Lecture Notes in Business Information Processing},
	volume = {14},
	year = {2009},
	pages = {467-494},
	publisher = {Springer-Verlag},
	organization = {Springer-Verlag},
	author = {Walt Scacchi},
	editor = {Lyytinen, K. and Loucopoulos, P. and Mylopoulos, J. and Robinson, W.}
}
@conference {933,
	title = {Visualizing Gnome with the Small Project Observatory},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {103 - 106},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {We analyzed the gnome family of systems with the small project observatory, our online ecosystem visualization platform. We begin by briefly introducing the model of SPO. We then observe and discuss several phases in the activity of the gnome ecosystem. We follow and look at how the contributors are distributed between writing source code and doing other activities such as internationalization. We end with a visual overview of the activity of more than 900 contributors in the 10 years of existence of gnome.},
	keywords = {bugzilla, contributions, gnome, msr challenge, spo, visualization},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069487},
	attachments = {https://flosshub.org/sites/flosshub.org/files/103Lung2009a.pdf},
	author = {Lungu, Mircea and Malnati, Jacopo and Lanza, Michele}
}
@conference {939,
	title = {On what basis to recommend: Changesets or interactions?},
	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 = {155 - 158},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Different flavours of recommendation systems have been proposed to help software developers perform software evolution tasks. A number of these recommendation systems are based on changesets. When changeset information is used, recommendations are based on only the end result of the activity undertaken to complete a task. In this paper, we report on an investigation that compared how recommendations based on changesets compare to recommendations based on interactions collected as a programmer performed the task that resulted in a changeset. To provide a common basis for the comparison, our investigation considered how bug reports considered similar based on changeset information compare to bug reports considered similar based on interaction information. We found that there is no direct relationship between the bug reports found similar with the different methods, suggesting that each comparison methods captures a different aspect of the problem.},
	keywords = {bug reports, changeset, eclipse, mylyn},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069494},
	author = {Rastkar, Sarah and Murphy, Gail C.}
}
@conference {584,
	title = {What Does It Take to Develop a Million Lines of Open Source Code?},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {170 - 184},
	publisher = {Springer},
	organization = {Springer},
	chapter = {16},
	abstract = {This article presents a preliminary and exploratory study of the relationship between size, on the one hand, and effort, duration and team size, on the other, for 11 Free/Libre/Open Source Software (FLOSS) projects with current size ranging between between 0.6 and 5.3 million lines of code (MLOC). Effort was operationalised based on the number of active committers per month. The extracted data did not fit well an early version of the closed-source cost estimation model COCOMO for proprietary software, overall suggesting that, at least to some extent, FLOSS communities are more productive than closed-source teams. This also motivated the need for FLOSS-specific effort models. As a first approximation, we evaluated 16 linear regression models involving different pairs of attributes. One of our experiments was to calculate the net size, that is, to remove any suspiciously large outliers or jumps in the growth trends. The best model we found involved effort against net size, accounting for 79 percent of the variance. This model was based on data excluding a possible outlier (Eclipse), the largest project in our sample. This suggests that different effort models may be needed for certain categories of FLOSS projects. Incidentally, for each of the 11 individual FLOSS projects we were able to model the net size trends with very high accuracy (R 2 >= 0.98). Of the 11 projects, 3 have grown superlinearly, 5 linearly and 3 sublinearly, suggesting that in the majority of the cases accumulated complexity is either well controlled or don{\textquoteright}t constitute a growth constraining factor.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_16},
	attachments = {https://flosshub.org/sites/flosshub.org/files/What\%20Does\%20it\%20Take\%20to\%20Develop.pdf},
	author = {Fernandez-Ramil, Juan and Izquierdo-Cortazar, Daniel and Mens, Tom}
}
@conference {1208,
	title = {Advances in the Sourceforge Research Data Archive},
	booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)},
	year = {2008},
	month = {2009},
	pages = {25-29},
	abstract = {The SourceForge Research Data Archive (SRDA), located at http://zerlot.cse.nd.edu, is a collection of Open Source Software (OSS) data and resources [6]. Over 100 researchers worldwide use the archive for research in many fields. In this paper, we describe the recent changes, the work in progress, and future plans for making the archive easier to use and for allowing more advanced research to be done with the data available.},
	keywords = {forge, forges, repositories, repository, sourceforge, srda},
	attachments = {https://flosshub.org/sites/flosshub.org/files/srda2008.pdf},
	author = {Matthew Van Antwerp and Madey, Greg}
}
@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 {563,
	title = {Applying Open Source Development Practices Inside a Company},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {381 - 387},
	publisher = {Springer},
	organization = {Springer},
	chapter = {36},
	abstract = {Open Source Software development is seen as a panacea by many companies. The promise of community-style development, innovation and cost savings drive the wider adoption of OSS in companies. However, it is still difficult to institutionalize the open and agile culture of sharing innovation especially into larger departmentalized organizations. The aim of this research paper is to investigate the characteristics of one successful OSS development implementation approach limited inside a company (Inner source). Based on our data, we argue that there are possibilities for employing OSS as a new kind of development process within a company and leveraging thus the innovation potential inside the company.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_36},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Applying\%20Open\%20Source\%20Development.pdf},
	author = {Juho Lindman and Rossi, Matti and Marttiin, Pentti}
}
@article {1391,
	title = {Challenges and strategies in the use of Open Source Software by Independent Software Vendors},
	journal = {Information and Software Technology},
	volume = {50},
	year = {2008},
	month = {8/2008},
	pages = {991 - 1002},
	abstract = {Open Source Software (OSS) has already been adopted by a large number of organizations. An important {\textendash} but sometimes neglected {\textendash} group of OSS users are Independent Software Vendors (ISVs). ISVs often develop their applications on top of OSS platform software. Frequently, this requires making several extensions and modifications to these OSS components. We identify a number of challenges that ISVs face in handling these extensions and modifications. Next, we describe several strategies ISVs can follow in maintaining these modifications. Finally, we suggest an opportunity for a closer collaboration between OSS projects and ISVs which could be mutually beneficial.},
	keywords = {Contributing, Independent Software Vendor},
	issn = {09505849},
	doi = {10.1016/j.infsof.2007.09.001},
	author = {Ven, Kris and Mannaert, Herwig}
}
@conference {549,
	title = {Channeling Firefox Developers: Mom and Dad Aren{\textquoteright}t Happy Yet},
	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 = {265 - 271},
	publisher = {Springer},
	organization = {Springer},
	chapter = {22},
	abstract = {Firefox, a browser targeted at mainstream users, has been one of the big successes of open source development in recent years. That Firefox succeeded where earlier attempts failed is undoubtedly due to the particular choices that were made in the process of development. In this paper, we look at this process in more detail. Mining bug reports and feature requests related to Firefox in Mozilla{\textquoteright}s Bugzilla bug tracker system, we find that the attention developers devoted to reports and requests was influenced by several factors. Most importantly, other things being equal, reports and requests from outsiders increasingly tend to be ignored. While such behavior may have helped to shield Firefox from the {\textquotedblleft}alpha-geek power user{\textquotedblright} in the early stages of development, it also makes it difficult for {\textquotedblleft}mom and dad{\textquotedblright} to let their voice be heard even after they have adopted Firefox.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_22},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Channeling\%20Firefox\%20Developers.pdf},
	author = {Jean-Michel Dalle and den Besten, Matthijs and Masmoudi, H{\'e}la}
}
@conference {542,
	title = {Empirical Analysis of the Bug Fixing Process in Open Source Projects},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {187 - 196},
	publisher = {Springer},
	organization = {Springer},
	chapter = {15},
	abstract = {Monitoring the performance of processes is often considered critical in classic engineering fields. However, in the area of software engineering (and especially in the Open Source context) it seems that the literature has not yet taken into consideration the problem of identifying the process characteristics and performance of debugging. The aim of this paper is the identification of the performance characteristics of the bug fixing process of Open Source applications, focusing on continuity and efficiency indicators. The importance of such indicators is even more relevant today, since Open Source software is now adopted also in many business contexts. We have analyzed the debugging process of 9 active and popular Open Source projects, collecting a dataset comprising more than 65,000 closed bugs. Results have highlighted four types of bug fixing processes that can be distinguished by considering temporal continuity and efficiency dimensions.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_15},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Empirical\%20Analysis\%20of\%20the\%20Bug\%20Fixinf\%20Process.pdf},
	author = {Francalanci, Chiara and Merlo, Francesco}
}
@booklet {480,
	title = {An Empirical Investigation into the Adoption of Open Source Software in Hospitals},
	year = {2008},
	month = {October},
	abstract = {Open source software (OSS) has gained considerable attention recently in health care. Yet, how and why OSS is being adopted within hospitals in particular remains a poorly understood issue. This research attempts to further this understanding. A mixed-method research approach was used to explore the extent of OSS adoption in hospitals as well as the factors facilitating and inhibiting adoption. The findings suggest a very limited adoption of OSS in hospitals. Hospitals tend to adopt general-purpose instead of domain-specific OSS. We found that software vendors are the critical factor facilitating the adoption of OSS in hospitals. Conversely, lack of in-house development, as well as a perceived lack of security, quality, and accountability of OSS products were factors inhibiting adoption. An empirical model is presented to illustrate the factors facilitating and inhibiting the adoption of OSS in hospitals.},
	author = {Gilberto Munoz and Carolyn Seaman}
}
@article {1100,
	title = {An Empirical Study on the Relationship Between Software Design Quality, Development Effort and Governance in Open Source Projects},
	journal = {IEEE Transactions on Software Engineering},
	volume = {34},
	year = {2008},
	note = {"empirical data from a sample of 75 major OS projects"
no PDF to confirm [ms]},
	month = {11/2008},
	pages = {765 - 782},
	abstract = {The relationship among software design quality, development effort, and governance practices is a traditional research problem. However, the extent to which consolidated results on this relationship remain valid for open source (OS) projects is an open research problem. An emerging body of literature contrasts the view of open source as an alternative to proprietary software and explains that there exists a continuum between closed and open source projects. This paper hypothesizes that as projects approach the OS end of the continuum, governance becomes less formal. In turn a less formal governance is hypothesized to require a higher-quality code as a means to facilitate coordination among developers by making the structure of code explicit and facilitate quality by removing the pressure of deadlines from contributors. However, a less formal governance is also hypothesized to increase development effort due to a more cumbersome coordination overhead. The verification of research hypotheses is based on empirical data from a sample of 75 major OS projects. Empirical evidence supports our hypotheses and suggests that software quality, mainly measured as coupling and inheritance, does not increase development effort, but represents an important managerial variable to implement the more open governance approach that characterizes OS projects which, in turn, increases development effort.},
	keywords = {effort estimation, governance, quality, source code},
	issn = {0098-5589},
	doi = {10.1109/TSE.2008.68},
	author = {Capra, E. and Francalanci, C. and Merlo, F.}
}
@article {10.1109/TSE.2008.68,
	title = {An Empirical Study on the Relationship Between Software Design Quality, Development Effort and Governance in Open Source Projects},
	journal = {IEEE Transactions on Software Engineering},
	volume = {34},
	year = {2008},
	note = {supplemental material attached},
	pages = {765-782},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {The relationship among software design quality, development effort, and governance practices is a traditional research problem. However, the extent to which consolidated results on this relationship remain valid for open source (OS) projects is an open research problem. An emerging body of literature contrasts the view of open source as an alternative to proprietary software and explains that there exists a continuum between closed and open source projects. This paper hypothesizes that as projects approach the OS end of the continuum, governance becomes less formal. In turn a less formal governance is hypothesized to require a higher-quality code as a means to facilitate coordination among developers by making the structure of code explicit and facilitate quality by removing the pressure of deadlines from contributors. However, a less formal governance is also hypothesized to increase development effort due to a more cumbersome coordination overhead. The verification of research hypotheses is based on empirical data from a sample of 75 major OS projects. Empirical evidence supports our hypotheses and suggests that software quality, mainly measured as coupling and inheritance, does not increase development effort, but represents an important managerial variable to implement the more open governance approach that characterizes OS projects which, in turn, increases development effort.},
	issn = {0098-5589},
	doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.2008.68},
	attachments = {https://flosshub.org/sites/flosshub.org/files/tts2008060765s.pdf},
	author = {Capra, Eugenio and Francalanci, Chiara and Merlo, Francesco}
}
@article {1091,
	title = {Evaluating the performance of open source software projects using data envelopment analysis},
	journal = {Information Management \& Computer Security},
	volume = {16},
	year = {2008},
	note = {"The data set used for this research consists of 34 OSS software projects listed on sourceforge.net." "only highly ranked projects in the security domain were considered."
"Ultimately data were collected on the 34 highest ranked security-based OSS software projects on Sourcefore.net."[sic]
fields: bug (?), developers, rank, downloads, Kperdownload (?)},
	month = {2008},
	pages = {449 - 462},
	abstract = {	

Purpose {\textendash} The purpose of this paper is to develop and test a model of the relative performance of open source software (OSS) projects.

Design/methodology/approach {\textendash} This paper evaluates the relative performance of OSS projects by evaluating multiple project inputs and multiple project outputs by using a data envelopment analysis (DEA) model. The DEA model produces an efficiency score for each project based on project inputs and outputs. The method of producing an efficiency score is based on the convex envelopment technology structure. The efficiency measure quantifies a {\textquotedblleft}distance{\textquotedblright} to an efficient frontier.

Findings {\textendash} The DEA model produced an index of corresponding intensities linking an inefficient project to its benchmark efficient project(s). The inefficiency measures produced an ordering of inefficient projects. Eight projects were found to be {\textquotedblleft}efficient{\textquotedblright} and used as benchmarking projects.

Research limitations/implications {\textendash} This research is limited to only security-based OSS projects. Future research on other areas of OSS projects is warranted.

Practical implications {\textendash} The result of this research is a practical model that can be used by OSS project developers to evaluate the relative performance of their projects and make resource decisions.

Originality/value {\textendash} This research extends the work of previous studies that have examined the relative performance of software development projects in a traditional development environment. As a result of this research, OSS projects can now be adequately benchmarked and evaluated according to project performance. An OSS project manger can effectively use these results to critically evaluate resources for their project and judge the relative efficiency of the resources.},
	keywords = {dea, efficiency, Project performance, sourceforge},
	issn = {0968-5227},
	doi = {10.1108/09685220810920530},
	author = {Wray, Barry and Mathieu, Richard and Teets, J.}
}
@conference {Chang:2008:ESC:1370750.1370766,
	title = {Evaluation of source code copy detection methods on freebsd},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {61{\textendash}66},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Studies have shown that substantial code reuse is common in open source and in commercial projects. However, the precise extent of reuse and its impact on productivity and quality are not well investigated in the open source context. Previously, we have introduced a simple-to-use method that needs only a set of file pathnames to identifies directories that share filenames and partially validated its performance on a set of closed-source projects. To evaluate this method and to improve reuse detection at the file level, we apply it and four additional file copy detection methods that utilize the underlying content of multiple versions of the source code on the FreeBSD project. The evaluation quantified unique advantages of each method and showed that the filename method detected roughly half of all reuse cases. We are still faced with a challenge to scale the content based methods to large repositories containing all versions of open source files.},
	keywords = {clone, cloning, code copying, freebsd, version control},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370766},
	url = {http://doi.acm.org/10.1145/1370750.1370766},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p61-chang.pdf},
	author = {Chang, Hung-Fu and Audris Mockus}
}
@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}
}
@article {521,
	title = {FLOSS-like education transfer report},
	year = {2008},
	month = {Sept},
	abstract = {Free/Libre and Open Source Software (FLOSS) communities are not only an exemplar for successful software development, but also for well working learning environments. Yet little is known about how learning occurs in the FLOSS communities and what the underlying success factors are. FLOSS communities might be seen as an example of {\textquoteright}Best Practice{\textquoteright} in how ICT can help to improve education in terms of learning processes, up to date content and open inclusive education where no learner is excluded from participation.The FLOSSCOM project was undertaken in order to evaluate how learning in FLOSS is organised and if, to which degree, and how FLOSS learning principles can be transferred to and used for the improvement of ICT supported formal education. Precisely, the FLOSSPOLS project intended to- identify the factors that contribute to successful knowledge construction in informal learning communities, such as the FLOSS communities- analyze the effectiveness of a FLOSS-like learning community in a formal educational setting- provide case studies, scenarios and guidelines for teachers and decision-makers on how to successfully embed such learning communities within formal educational environments to enhance student progression, retention and achievement- evaluate the project and disseminate the results to the wider community.This report is the third and final report of the FLOSSCOM project. It aims to provide scenarios and guidelines for teachers and decision-makers as practical documentation on how principles of FLOSS-like informal learning communities might be transferred to formal educational environments.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FLOSSCOM_WP5_PHASE_3_REPORT.pdf},
	author = {Andreas Meiszner}
}
@conference {529,
	title = {Forging A Community {\textendash} Not: Experiences On Establishing An Open Source Project},
	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 = {15 - 27},
	publisher = {Springer},
	organization = {Springer},
	chapter = {2},
	abstract = {Open source has recently become a practical and advocated fashion to develop, integrate, and license software. As a consequence, open source communities that commonly perform the development work are becoming important in the practice of software engineering. A community that is lively can often produce high-quality systems that continuously grow in terms of features, whereas communities that do not gain interest will inevitably perish. Despite their newly established central role, creation, organization, and management of such communities have not yet been widely studied from the viewpoint of software engineering practices. In this paper, we discuss experiences gained in the scope of Laika, an open source project established to develop an integrated software development environment for developing applications that run in Linux based mobile devices.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_2},
	attachments = {https://flosshub.org/sites/flosshub.org/files/forging\%20a\%20community.pdf},
	author = {J{\"a}rvensivu, Juha and Mikkonen, Tommi}
}
@booklet {512,
	title = {The Foundations of Openness},
	year = {2008},
	month = {Jul},
	abstract = {This project explores the notion of openness in software projects. It contextualizes different facets of openness and considers their individual and collective usefulness. It provides a tentative evaluative schema to allow others to weigh up specific criteria that may be important to them. It acknowledges that these criteria may have different weightings for different people, e.g. governance vs open standards vs code licence. The object is *not* a blanket recommendation for openness in all facets of a project. Rather it is a tool for projects, and those who use those projects, to investigate and illuminate the choices being made as well as the implication of open and closed approaches.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Foundations-of-openness-V2-release.pdf},
	author = {Pia Waugh and Randy Metcalfe}
}
@booklet {481,
	title = {How Do Firms Make Use of Open Source Communities?},
	howpublished = {Long Range Planning},
	volume = {41},
	number = {6},
	year = {2008},
	note = {"To obtain more information about the firms{\textquoteright} relationships with their respective communities, we followed mailing lists and forums over a three-month period, checking them at least three times a week. "
"Firm data. Secondary sources, including annual reports, company directories, business and specialist press and homepages, were used to gather information on firms"},
	month = {Dec},
	pages = {629-649},
	abstract = {Relying on four in-depth case studies of firms involved with open source software, we investigate how firms make use of open source communities, and how that use is associated with their business models. Three themes - accessing, aligning and assimilating -are inductively developed for how the firms relate to the external knowledge created in the communities. For each theme, we make an argument about the tactics associated with each theme and their positive and negative consequences. The findings are related to the literature on the open and distributed nature of innovation, and various theoretical and managerial implications are discussed.},
	keywords = {case study, cendio, email, mailing list, mysql, roxen, secondary data, sot},
	url = {http://www.acm.jhu.edu/~paulproteus/tmp/sdarticle.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dahlandermagnusson2008.pdf},
	author = {Linus Dahlander and M Magnusson}
}
@article {1120,
	title = {The institutions of open source software: Examining the Debian community*},
	journal = {Information Economics and Policy},
	volume = {20},
	year = {2008},
	note = {"using primary data from its mailing lists archives, handbooks written to inform potential and actual community members, and previous analyses of institutional evolution and political conflict"

no discussion of which lists, how many, or when they were gathered...?[ms]},
	month = {12/2008},
	pages = {333 - 344},
	abstract = {Free and open source software activities involve and, perhaps, evolve institutions (rules, norms and standards) that influence the formation, growth, and demise of communities. Community institutions are attractors for some individuals while discouraging other individuals from entering or continuing to participate. Their suitability may change as a community grows. This paper examines the institutions of the Debian community where issues of community identity, distribution of authority, and decentralisation have facilitated growth and development. These same institutions have also resulted in conflicts regarding community purposes and the quality and delivery of the community{\textquoteright}s output. We examine the institutional redesign undertaken to address these problems and derive implications for F/LOS communities and companies.},
	keywords = {authority, COMMUNITY, conflict, debian, decentralization, growth, institutions, leadership},
	issn = {01676245},
	doi = {10.1016/j.infoecopol.2008.06.001},
	attachments = {https://flosshub.org/sites/flosshub.org/files/The_institutions_of_open_source_software-_IR.pdf},
	author = {Mateos Garcia, J. and Steinmueller, W.E.}
}
@conference {535,
	title = {Lost and Gained in Translation: Adoption of Open Source Software Development at Hewlett-Packard},
	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 = {93 - 104},
	publisher = {Springer},
	organization = {Springer},
	chapter = {8},
	abstract = {What happens when an organization form that has emerged in one context is brought into a different context? In this paper, a longitudinal field study approach is used to explore how Hewlett-Packard (HP) molded open source software development (OSSD) into a proprietary software development approach called {\textquotedblleft}Progressive Open Source{\textquotedblright} (POS). With the help of actornetwork theory, we understand this as a process of translation and find that some central characteristics of OSSD where lost in the translation into POS while other characteristics were gained.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_8},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Lost\%20\%26\%20Gained\%20in\%20Translation.pdf},
	author = {Melian, Catharina and M{\"a}hring, Magnus}
}
@conference {553,
	title = {The Networked Forge: New Environments for Libre Software Development},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {299 - 306},
	publisher = {Springer},
	organization = {Springer},
	chapter = {26},
	abstract = {Libre (free, open source) software forges (sites hosting the development infrastructure for a collection of projects) have been stable in architecture, services and concept since they become popular during the late 1990s. During this time several problems that cannot be solved without dramatic design changes have become evident. To overcome them, we propose a new concept, the {\textquotedblleft}networked forge{\textquotedblright}, focused on addressing the core characteristics of libre software development and the needs of developers. The key of this proposal is to re-engineer forges as a net of distributed components which can be composed and configured according to the needs of users, using a combination of web 2.0, semantic web and mashup technologies. This approach is flexible enough to accommodate different development processes, while at the same time interoperates with current facilities.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_26},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Networked\%20Forge.pdf},
	author = {Gonzalez-Barahona, Jesus and Mart{\'\i}nez, Andr{\'e}s and Polo, Alvaro and Hierro, Juan and Reyes, Marcos and Soriano, Javier and Fern{\'a}ndez, Rafael}
}
@conference {565,
	title = {Open Source Reference Systems for Biometric Verification of Identity},
	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 = {397 - 404},
	publisher = {Springer},
	organization = {Springer},
	chapter = {38},
	abstract = {This paper focuses on the common evaluation framework which was developed by the BioSecure Network of Excellence during the European FP6 project BioSecure (Biometrics for Secure authentication). This framework, which is composed of open-source reference systems, publicly available databases, assessment protocols and benchmarking results, introduces a new experimental methodology for conducting, reporting and comparing experiments for biometric systems, participating to standardisation efforts. Its use will permit to make a link between different published works. It provides also the necessary tools to assure the reproducibility of the benchmarking biometric experiments. This framework can be considered as a re-liable and innovative process to evaluate the progress of research in the field of bio-metrics.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_38},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Reference\%20Systems.pdf},
	author = {Mayoue, Aur{\'e}lien and Petrovska-Delacr{\'e}taz, Dijana}
}
@conference {567,
	title = {Panel: Opportunities and Risks for Open Source Software in Industry},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {413 - 414},
	publisher = {Springer},
	organization = {Springer},
	chapter = {40},
	abstract = {Open Source Software (OSS) is a multi-faceted phenomenon which has become an issue of strategic importance for many commercial organisations. Stemming from an ideological issue, with emphasis on freedom and community values, we have recently seen a broader interest in the Open Source phenomenon amongst practitioners in many companies. A number of SMEs and large companies are currently exploring the potential of Open Source, and for some it has become core to their business and development activities.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_40},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Panel\%20Opportunities\%20\%26\%20Risks.pdf},
	author = {Feller, Joseph and Lundell, Bj{\"o}rn and Marttiin, Pentti and Walt Scacchi and Schellingerhout, Nico}
}
@booklet {520,
	title = {Preparing the Ne(x)t Generation: Lessons learnt from Free/Libre Open Source Software and their Communities},
	year = {2008},
	month = {Sept},
	abstract = {In this article, the authors Andreas Meiszner, R{\~A}{\textonequarter}diger Glott and Sulayaman K. Sowe, examine the lessons that can be learnt from the Free / Libre Open and Source Software (FLOSS) communities. FLOSS communities, as good practice examples of Open Participatory Learning Ecosystems, illustrate possible pathways for higher education to go beyond the limits of the current Open Educational Resource move.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/GUNI_paper_proceedings_Meiszner_Glott_Sowe.pdf},
	author = {Andreas Meiszner and R{\"u}dige Glott and Sowe, Sulayman K.}
}
@article {1814,
	title = {Relationship between size, effort, duration and number of contributors in large FLOSS projects},
	journal = { 7th BElgian-NEtherlands software eVOLution workshop - BENEVOL 2008},
	year = {2008},
	abstract = {This contribution presents initial results in the study of the relationship between size,
effort, duration and number of contributors in eleven evolving Free/Libre Open Source
Software (FLOSS) projects, in the range from approx. 650,000 to 5,300,000 lines of
code. Our initial motivation was to estimate how much effort is involved in achieving
a large FLOSS system. Software cost estimation for proprietary projects has been an
active area of study for many years (e.g. [1][2][3]). However, to our knowledge, no previous
similar research has been conducted in FLOSS effort estimation. This research
can help planning the evolution of future FLOSS projects and in comparing them with
proprietary systems. Companies that are actively developing FLOSS may benefit from
such estimates [4]. Such estimates may also help to identify the productivity {\textquoteright}baseline{\textquoteright}
for evaluating improvements in process, methods and tools for FLOSS evolution},
	url = {http://oro.open.ac.uk/27317/1/},
	author = {Ramil, J.F. and Izquierdo-Cort{\'a}zar, Daniel and Mens, Tom}
}
@article {502,
	title = {Report on the effectiveness of a FLOSS-like learning community in formal educational settings},
	year = {2008},
	abstract = {This report examines some of the pedagogic principles embodied in Free / Libre Open Source Software (FLOSS) communities and briefly looks at case studies of FLOSS-like approaches in education. It analyzes and evaluates the differences between Free / Libre Open Source Software (FLOSS) communities as informal learning environments and on the other side formal educational settings. The report also point out ways on transferring those FLOSS principles to formal educational settings and looks at existing examples of eLearning delivery and examines why these do not provide the types of constructivist learning environments as observed in FLOSS communities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FLOSSCOM_Wp4_PHASE2_REPORT_d1.pdf},
	author = {Martin J. Weller and Andreas Meiszner and Sowe, Sulayman K. and Athanasis Karoulis}
}
@conference {564,
	title = {Towards The Evaluation of OSS Trustworthiness: Lessons Learned From The Observation of Relevant OSS Projects},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {389 - 395},
	publisher = {Springer},
	organization = {Springer},
	chapter = {37},
	abstract = {To facilitate the adoption of open-source software (OSS) in industry, it is important to provide potential users (i.e., those who could decide to adopt OSS) with the means for evaluating the trustworthiness of OS products. This paper presents part of the work done in the QualiPSo project for this purpose. A set of factors that are believed to affect the perception of trustworthiness are introduced. In order to test the feasibility of deriving a correct, complete and reliable evaluation of trustworthiness on the basis of these factors, a set of well-known OSS projects have been chosen. Then, the possibility to assess the proposed factors on each project was verified: not all the factors appear to be observable or measurable. The paper reports what information is available to support the evaluation and what is not. This knowledge is considered to be useful to users, who are warned that there are still dark areas in the characterization of OSS products, and to developers, who should provide more data and characteristics on their products in order to support their adoption.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Toward\%20the\%20Evaluation\%20of\%20OSS.pdf},
	author = {Taibi, Davide and del Bianco, Vieri and Carbonare, Davide and Lavazza, Luigi and Morasca, Sandro}
}
@conference {Sudakrishnan:2008:UBF:1370750.1370761,
	title = {Understanding bug fix patterns in verilog},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {39{\textendash}42},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Today, many electronic systems are developed using a hardware description language, a kind of software that can be converted into integrated circuits or programmable logic devices. Like traditional software projects, hardware projects have bugs, and significant developer time is spent fixing them. A useful first step toward reducing bugs in hardware is developing an understanding of the frequency of different types of errors. Once the most common types are known, it is then possible to focus attention on eliminating them. As most hardware projects use software configuration management repositories, these can be mined for the textual bug fix changes. In this project, we analyze the bug fix history of four hardware projects written in Verilog and manually define 25 bug fix patterns. The frequency of each bug type is then computed for all projects. We find that 29 -- 55\% of the bug fix pattern instances in Verilog involve assignment statements, while 18 -- 25\% are related to if statements.},
	keywords = {bug fixing, error classification, hdl, verilog, VHDL},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370761},
	url = {http://doi.acm.org/10.1145/1370750.1370761},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p39-sudakrishnan.pdf},
	author = {Sudakrishnan, Sangeetha and Madhavan, Janaki and Whitehead,Jr., E. James and Renau, Jose}
}
@conference {541,
	title = {Using Social Network Analysis Techniques to Study Collaboration between a FLOSS Community and a Company},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {171 - 186},
	publisher = {Springer},
	organization = {Springer},
	chapter = {14},
	abstract = {Because of the sheer volume of information available in FLOSS repositories, simple analysis have to face the problems of filtering the relevant information. Hence, it is essential to apply methodologies that highlight that information for a given aspect of the project. In this paper, some techniques from the social sciences have been used on data from version control systems to extract information about the development process of FLOSS projects with the aim of highlighting several processes that occur in FLOSS projects and that are difficult to obtain by other means. In particular, the collaboration between the FLOSS community and a company has been studied by selecting two projects as case studies. The results highlight aspects such as efficiency in the development process, release management and leadership turnover.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_14},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Using\%20Social\%20Network.pdf},
	author = {Martinez-Romo, Juan and Gregorio Robles and Gonzalez-Barahona, Jesus and Ortu{\~n}o-Perez, Miguel}
}
@conference {664,
	title = {1st International Workshop on Trust in Open Source Software (TOSS)},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {371 - 373},
	publisher = {Springer},
	organization = {Springer},
	chapter = {48},
	abstract = {The 1st International Workshop on Trust in Open Source Software (TOSS) focuses on one of the major factors in the adoption of software solutions: the trustworthiness of OSS, which has influenced the widespread adoption of OSS in industry. Software quality aspects have been investigated for a long time in the academia but the usage/production of OSS is creating new challenges and the points of view of the industry and the academia may differ, especially on the trustworthiness of OSS. The aim of the workshop is to open a communication channel between the industry and the academia focusing on this issue and promote a long lasting discussion on it. The workshop tries to identify the different points of views and the different approaches that can result in benefits for the software industry.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_48},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1st\%20Intl\%20Workshop\%20on\%20Trust.pdf},
	author = {Morasca, Sandro and Sillitti, Alberto}
}
@article {flosswp370,
	title = {Analysis of the Informal Learning Environment of FLOSS (Free / Libre Open Source Software) Communities},
	year = {2007},
	month = {July},
	abstract = {The general concept behind Free/Libre/Open Source Software (henceforth FLOSS) is making the source code of software accessible to anyone who wants to obtain it. Binaries or executables are available via the Internet and can be {\textquoteright}freely{\textquoteright} downloaded and used. Prolific licensing agreements such as the General Public License (GPL) define the rights users have over the product. In the literature, many terms are in use to describe the FLOSS phenomenon. Notably, Free Software (FS), a term used by Free Software Foundation (FSF) and Open Source Software (OSS) used by the Open Source Initiative (OSI). In addition, Free Open Source Software (FOSS), Libre Software (LS), and Free/Libre/Open Source Software (FLOSS) are terms frequently used by researchers. In this report the term FLOSS is used to refer to users??? freedom to use, modify, distribute, or even sell the software with little obligations as in propriety or closed source software. When a user modifies the software, he/she can either choose to keep changes made private or altruistically return them to the FLOSS community so that everyone can benefit from his derived work. FLOSS development did not begin with the inception of the Linux operating system, in 1991. Rather, the concept existed since the formation of SHARE ??? a working group set up to coordinate the programming work of the IBM 701, in 1952 (Sowe, 2007b). In the academic environment, software development and distribution among researchers and departments is not new, and goes back to the earliest days of software in university environments when software was developed to solve practical problems and could be freely shared. However, what is now true is that FLOSS has fundamentally changed the way we develop and distribute software. Enable by the Internet, geographically distributed individuals voluntarily contribute to a project by means of the Bazaar model (Raymond, 1999). Extensive peer collaboration allows project participants to write code, debug, test, and integrate software. Communities in various projects provide support services such as suggestions for products features, act as distributing organs, answer queries, help new members having problems with the software. FLOSS development not only exemplifies a viable software development approach, but also a model for the creation of self-learning and self-organizing communities (Sowe, et al. 2006c). FLOSS is also a virtual learning context in which both professional software developers and novice users benefit by leveraging their knowledge and information access repertoire. The context enable them to participate at their own convenience and learn (coding or other software related task) at their own pace (Sowe, et al. 2005; page 297). Furthermore, learners can conclude on the learning scope themselves (what to do) and decide on the method of acquiring the knowledge (how to do it). Knowledge acquisition is accomplished, for example, by having access to a large code-base, studying online documentation, asking more experienced members for assistance. In essence knowledge is acquired in FLOSS through learning by doing, which represents the drill-and-practice approach in normal constructivist environments. However, the FLOSS virtual learning context is not without its downside. Apart from physical isolation and detachment from face-to-face interaction commonly associated with virtual learning environments, learning in FLOSS requires access to Internet and moderate computer facilities. In addition, a high degree of computer literacy, reading, writing, and typing is required to participate effectively. The environment is also not conflict free. Flaming, the feeling of being ignored in a dominant discussion, disinterestedness, long delays in receiving responses from communities, the expenditure of searching through discussion archives to see issues previously raised in the communities, access rights to participate in some community activities are all major concerns in the management of the FLOSS learning context (Sowe, et al. 2005). In recent times, FLOSS is making inroads not only in business and software industries but in colleges and universities as well. There is increased interest in the FLOSS learning environment (Sowe, et al., 2004; Bacon and Dillion, 2006) and in FLOSS projects as bazaars of learning (Sowe, et al., 2006). As Faber (2002) noted, FLOSS is both an alternative teaching methodology and an educational model. The main objective of FLOSSCom is using the principles of informal learning environments of FLOSS communities to improve Information and Communication Technology (ICT) supported formal education. Despite the influence and popularity of FLOSS and the benefit inherent in its methodology, educational institutions have been slow to adapt. This can partly due to the fact that the FLOSS environment is fundamentally different from the formal learning environment in most institutions. The focus of this report is collate and report on the learning activities of individuals in various FLOSS communities. The report benefits from the experiences and expositions of various authors in order to provide a synergy and a fresh look into the learning environment of FLOSS communities. FLOSS communities, like other online communities (e.g. Community of Practice (CoPs)) have many interrelated elements that define the dynamics of the community. As such, this report is divided into 5 major sections, each focusing on a specific aspect of the learning environment of FLOSS communities with a 6th section summarizing the main findings. Section 1: The first part of the report is an introduction to FLOSS. The historical account of FLOSS is presented together with the many meanings of the term. This is followed by the demographic distribution of FLOSS participants and an explanation of what FLOSS communities are. Section 2: The next chapter examines the role of learning and knowledge exchange within the FLOSS community. It includes a description of the composition and roles of members within communities and what motivates various groups of individuals to participate in FLOSS. Section 3: After clarifying the role of learning in the FLOSS community the next chapter focuses on the content of learning processes in FLOSS. This chapter examines both, what skills are learnt and how the skills learnt within the FLOSS community are evaluated. The latter aspect is considered from the perspective of FLOSS community members as well as from the perspective of employers. Section 4: The fourth chapter examines how learning is organized within the FLOSS community. It examines the interaction between community members with regard to learning processes, the learning resources (except for technological resources) that are available and used within FLOSS communities, and the concrete learning processes. Section 5: This section looks at the technological resources used within FLOSS communities. FLOSS projects are almost exclusively administered online and one of the most important prerequisites for their coordination and cooperation is provided by the functionality of various communication and groupware tools. Section 6: The last section of the report proposes the project???s approach to learning in FLOSS. A preliminary set of guidelines as they apply to the principles of informal learning environments of FLOSS communities to improve ICT supported formal education are offered. These preliminary guidelines will be continuously amended in the following phase of the FLOSSCom project.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FLOSSCom_WP2_Phase_1_Report_v070709_1.pdf},
	author = {R{\"u}dige Glott and Andreas Meiszner and Sowe, Sulayman K.}
}
@conference {1007,
	title = {Analysis of the Linux Kernel Evolution Using Code Clone Coverage},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {22 - 22},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Most studies of the evolution of software systems are based on the comparison of simple software metrics. In this paper, we present our preliminary investigation of the evolution of the Linux kernel using code-clone analysis and the code-clone coverage metrics. We examined 136 versions of the stable Linux kernel using a distributed extension of the code clone detection tool CCFinder. The result is shown as a heat map.},
	keywords = {ccfinder, clone, cloning, kernel, linux, metrics, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300022.pdf},
	author = {Livieri, Simone and Higo, Yoshiki and Matsushita, Makoto and Inoue, Katsuro}
}
@conference {649,
	title = {Benefits and Drawbacks of Open Source Software: An Exploratory Study of Secondary Software Firms},
	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 = {307 - 312},
	publisher = {Springer},
	organization = {Springer},
	chapter = {33},
	abstract = {Much of the assessment of OSS benefits and drawbacks has been based on anecdotal evidence appearing in practitioner publications, white papers, web articles etc. To a greater extent this research has tended to concentrate more on the technical benefits and drawbacks of OSS rather than their business counterparts. Furthermore, public administrations and companies operating within the primary software sector have traditionally been the focus for research on OSS benefits and drawbacks. Taking the viewpoint of IS/IT managers in 13 companies operating in the secondary software sector in Europe, this paper examines their experiences of the benefits/drawbacks of OSS.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Benefits\%20and\%20Drawbacks.pdf},
	author = {Morgan, Lorraine and Finnegan, Patrick}
}
@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.}
}
@conference {648,
	title = {Context-Dependent Evaluation Methodology for Open Source Software},
	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 = {301 - 306},
	publisher = {Springer},
	organization = {Springer},
	chapter = {32},
	abstract = {Many evaluation methodologies have been proposed to mitigate the risks of choosing Open Source Software as an effective solution to an enterprise{\textquoteright}s problem. This work extracts the shared traits from the most important and widely known evaluation models, and re-applies them to create a new methodology. This methodology has been designed both to be used for the creation of a common knowledge base, and to be specialized for application in the context of the particular breed of small and medium-size enterprises found on the Italian ground.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_32},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Context-Dependent\%20Evaluation.pdf},
	author = {Cabano, Michele and Monti, Cesare and Piancastelli, Giulio}
}
@conference {996,
	title = {Correlating Social Interactions to Release History during Software Evolution},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {7 - 7},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {In this paper, we propose a method to reason about the nature of software changes by mining and correlating discussion archives. We employ an information retrieval approach to find correlation between source code change history and history of social interactions surrounding these changes. We apply our correlation method on two software systems, LSEdit and Apache Ant. The results of these exploratory case studies demonstrate the evidence of similarity between the content of free-form text emails among developers and the actual modifications in the code. We identify a set of correlation patterns between discussion and changed code vocabularies and discover that some releases referred to as minor should instead fall under the major category. These patterns can be used to give estimations about the type of a change and time needed to implement it.},
	keywords = {ant, apache, change management, developers, discussion, effort estimation, lsedit, mailing lists, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.4},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300007.pdf},
	author = {Baysal, Olga and Malton, Andrew J.}
}
@article {flosswp371,
	title = {The Creation of the Entrepreneurial Spirit and the Formation Of Alliances With Africa},
	year = {2007},
	month = {January},
	abstract = {The paper argues that there are internal governance problems within the African polity which need to be resolved before a successful creation of entrepreneurial alliances between Africa and the rest of the world. It also argues that past issues such as colonialism and imperialism pale into insignificance particularly among the new generation if they observe the absence of ethics among the current political leadership in the continent. There is also some discussion about the need for the developed world, notwithstanding the internal continental problems, to brush up its act in relation to the formation of alliances in Africa. Finally the paper argues the formation of alliances with Africa should not be limited to the traditioanl alliance partners of Europe and the America, but be flexible enough to allow new entrants such as China and India.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/WITTENBERG.pdf},
	author = {Jabulani Mzaliya}
}
@conference {992,
	title = {Determining Implementation Expertise from Bug Reports},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {2 - 2},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {As developers work on a software product they accumulate expertise, including expertise about the code base of the software product. We call this type of expertise "implementation expertise". Knowing the set of developers who have implementation expertise for a software product has many important uses. This paper presents an empirical evaluation of two approaches to determining implementation expertise from the data in source and bug repositories. The expertise sets created by the approaches are compared to those provided by experts and evaluated using the measures of precision and recall. We found that both approaches are good at finding all of the appropriate developers, although they vary in how many false positives are returned.},
	keywords = {bug reports, developers, eclipse, expertise, repository, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300002.pdf},
	author = {Anvik, John and Murphy, Gail C.}
}
@article {flosswp332,
	title = {Do firms take part in the projects of the OS community. Some preliminary evidence and a research agenda},
	year = {2007},
	month = {January},
	abstract = {The Open Source (OS) software has progressively gained economic importance in recent years, and more and more commercial firms are getting involved, to various extents, in the OS movement. While a number of studies have investigated motivations and business models of OS-based software companies, very few works have examined whether and how firms actively participate to open projects. This paper contributes to the literature by providing empirical evidence on the role and the activities of software houses in community developed projects. The research also proposes an original methodology of large-scale primary data collection from OS project repositories and linked Web sites. The findings show how different today???s OS movement is from its origins and how important firm involvement has become, not only numerically but also for the deepness of its impact on community projects. Finally, further research developments are suggested.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper_firm_involvement_MIT.pdf},
	author = {Andrea Bonaccorsi and Dario Lorenzi and Monica Merito and Cristina Rossi}
}
@article {flosswp348,
	title = {Dual Licensing in Open Source Software Markets},
	year = {2007},
	month = {May},
	abstract = {Dual licensing has proved to be a sustainable business model for various commercial software vendors employing open source strategies. In this paper we study the main characteristics of dual licensing and under which conditions it represents a profitable commercial strategy. We show that dual licensing is a form of versioning, whereby the software vendor uses the open source licensing terms in order to induce commercial customers to select the proprietary version of the software. Furthermore, we show that the software vendor prefers dual licensing to a fully proprietary strategy when the customers are very sensitive to the reciprocal terms of the open source license.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dual_lic.pdf},
	author = {Stefano Comino and Fabio M. Manenti}
}
@conference {661,
	title = {EDOS-Tools Tutorial: EDOS Tools for Linux Distributions Dependencies Management and Quality Assurance},
	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 = {363 - 364},
	publisher = {Springer},
	organization = {Springer},
	chapter = {45},
	abstract = {Free and Open Source Software (FOSS) distributions are the results of the effort of third party actors in collecting independently developed software products, in a consistent and usable form. The widespread adoption of these distributions as infrastructural components in many strategic contexts of the information technology society has drawn the attention on the issues regarding how to handle the complexity of assembling and managing a huge number of (packaged) components and how to guarantee their quality. This tutorial will describe how the EDOS project has tackled these issues. First it will describe the problems related to the quality assurance of Linux distributions and will present the tools that have been developed to manage testing process. It will then introduce the problems that occur when managing inter-package relations in large package repositories and will showcase tools that can be used to analyze and manage large package repositories.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_45},
	attachments = {https://flosshub.org/sites/flosshub.org/files/EDOIS-\%20Tools\%20Tutorials.pdf},
	author = {D{\'e}chelle, Fran{\c c}ois and Mancinelli, Fabio}
}
@book {1803,
	title = {Emerging Free and Open Source Software PracticesVolunteers in Large Libre Software Projects},
	series = {Emerging Free and Open Source Software Practices},
	year = {2007},
	pages = {1 - 24},
	publisher = {IGI Global},
	organization = {IGI Global},
	abstract = {Most libre (free, open source) software projects rely on the work of volunteers. Therefore, attracting people who contribute their time and technical skills is of paramount importance, both in technical and economic terms. This reliance on volunteers leads to some fundamental management challenges: Volunteer contributions are inherently difficult to predict, plan, and manage, especially in the case of large projects. In this chapter we present an analysis of the evolution over time of the human resources in large libre software projects, using the Debian project, one of the largest and most complex libre software projects based mainly in voluntary work, as a case study. We have performed a quantitative investigation of data corresponding to roughly seven years, studying how volunteer involvement has affected the software released by the project, and the developer community itself.
},
	doi = {10.4018/978-1-59904-210-7.ch001},
	url = {http://www.igi-global.com/chapter/volunteers-large-libre-software-projects/10080},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Martin Michlmayr},
	editor = {Sowe, Sulayman K. and Stamelos, Ioannis G. and Samoladas, Ioannis}
}
@conference {668,
	title = {FOSLET 07 {\textemdash} Workshop on Free and Open Source Learning Environments and Tools},
	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 = {385 - 387},
	publisher = {Springer},
	organization = {Springer},
	chapter = {52},
	abstract = {Web-based Learning Environments supported by Course Management Systems (also known as Learning Management Systems) are nowadays a valid solution for institutions, companies, schools and universities that deliver eLearning or support blended-learning activities. Learning Environments are used to distribute information and content material to learners, prepare and deliver assignments and tests, engage in discussions, and manage distance classes without time and space restrictions.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_52},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FOSLET\%2007\%20workshop.pdf},
	author = {Botturi, Luca and Mazza, Riccardo and Tardini, Stefano}
}
@article {76,
	title = {From planning to mature: On the success of open source projects},
	journal = {Research Policy},
	volume = {36},
	year = {2007},
	note = {Times Cited: 0},
	pages = {1575-1586},
	abstract = {Open source is an example of user-centric innovation initiated by an individual or group of users to satisfy their specific needs; the more a software evolves towards a stable release able to address the requirements of its developers, the more successful the project. In this paper we use a large data-set obtained from SourceForge.net to estimate the relationship between a series of different characteristics of OS projects and the probability of evolution of the source code from a preliminary release to a mature version. We show that while projects distributed under highly restrictive licensing terms (GPL) have a significantly smaller probability of reaching a stable release, applications towards sophisticated users have a larger probability of evolving in the development status. Interestingly, we find that the size of the "community of developers" increases the chances of progress but this effect decreases as the community gets larger, a signal of possible coordination problems. (C) 2007 Elsevier B.V. All rights reserved.},
	author = {Stefano Comino and Fabio M. Manenti and Parisi, M. L.}
}
@conference {671,
	title = {From the Cathedral to the Bazaar: An Empirical Study of the Lifecycle of Volunteer Community Projects},
	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 = {31 - 44},
	publisher = {Springer},
	organization = {Springer},
	chapter = {3},
	abstract = {Some free software and open source projects have been extremely successful in the past. The success of a project is often related to the number of developers it can attract: a larger community of developers (the {\textquoteleft}bazaar{\textquoteright}) identifies and corrects more software defects and adds more features via a peer-review process. In this paper two free software projects (Wine and Arla) are empirically explored in order to characterize their software lifecycle, development processes and communities. Both the projects show a phase where the number of active developers and the actual work performed on the system is constant, or does not grow: we argued that this phase corresponds to the one termed {\textquoteleft}cathedral{\textquoteright} in the literature. One of the two projects (Wine) shows also a second phase: a sudden growing amount of developers corresponds to a similar growing output produced: we termed this as the {\textquoteleft}bazaar{\textquoteright} phase, and we also argued that this phase was not achieved for the other system. A further analysis revealed that the transition between {\textquoteleft}cathedral{\textquoteright} and {\textquoteleft}bazaar{\textquoteright} was a phase by itself in Wine, achieved by creating a growing amount of new modules, which attracted new developers.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/From\%20the\%20Cathedral.pdf},
	author = {Capiluppi, Andrea and Martin Michlmayr}
}
@article {75,
	title = {Global and Temporal Analysis of Social Positions at SourceForge. net},
	journal = {Third International Conference on Open Source Systems, IFIP WG},
	volume = {2},
	year = {2007},
	author = {Christley, S. and Madey, G.}
}
@article {flosswp378,
	title = {Love and other demons: game theory in enterpreneurial and love relationships},
	year = {2007},
	month = {December},
	abstract = {The article studies the risk aversion and information assymetry differences in two fields of relationships: between partners and in a loving couple.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ARTICULO_1-del_amor_y_otros_demonios-_teoria_de_juegos_en_las_relaciones_empresariales_y_amorosas.pdf},
	author = {Guillermo Flores and Alejandro Mendighetti and Jorge S{\'a}nchez}
}
@conference {631,
	title = {Network Analysis of the SourceForge.net Community},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {187 - 200},
	publisher = {Springer},
	organization = {Springer},
	chapter = {15},
	abstract = {Software is central to the functioning of modern computer-based society. The OSS (Open Source Software) phenomenon is a novel, widely growing approach to develop both applications and infrastructure software. In this research, we studied the community network of the SourceForge.net, especially the structure and evolution of the community network, to understand the Open Source Software movement. We applied three different analyses on the network, including structure analysis, centrality analysis and path analysis. By applying these analyses, we are able to gain insights of the network development and its influence to individual developments.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_15},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Network\%20Analysis\%20of\%20the\%20SourceForge.pdf},
	author = {Gao, Yongqin and Madey, Greg}
}
@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.}
}
@article {flosswp328,
	title = {Open Source and the software industry. How firms do business out of an open innovation paradigm},
	year = {2007},
	month = {January},
	abstract = {Open Source Software (OSS) represents an ???open innovation??? paradigm based on knowledge produced and shared by developers and users. The paper inquires how OSS challenges the three Teece???s building blocks. New findings from a large survey of European software companies, show that within the OSS paradigm: (i) OSS can be a sustainable business model even in the absence of any appropriability; (ii) complementary assets are distributed collectively and made widely available without the need for dedicated contractual arrangements; (iii) a de facto dominant design may stem from a community of users/producers even independently of the presence of powerful large companies.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper_euram_2007.pdf},
	author = {Andrea Bonaccorsi and Monica Merito and Rossi Cristina and Lucia Piscitello}
}
@article {1390,
	title = {An Open Source Approach to Developing Software in a Small Organization},
	journal = {IEEE Software},
	volume = {24},
	year = {2007},
	month = {01/2007},
	pages = {46 - 53},
	abstract = {This article is part of a special issue on Software Engineering Challenges in Small Software Organizations. The software development approach that developers at Kitware use borrows techniques from agile development and Extreme Programming and emphasizes long-term, ongoing projects. The company has used this approach on open source and closed-source projects in a wide range of sizes},
	keywords = {Cross-platform, Small-business, software engineering, Software testing},
	issn = {0740-7459},
	doi = {10.1109/MS.2007.5},
	author = {Martin, Ken and Hoffman, Bill}
}
@booklet {506,
	title = {Open Source Software Development as a Model for Internet Governance},
	year = {2007},
	month = {Sept},
	abstract = {Internet governance and open source software development alike are most effectively achieved through a balance of decentralisation and control. For Internet governance, this is found in governance by network, in which governmental and private stakeholders, and the hierarchical and decentralised mechanisms of governance they respectively favour, are brought together. However if the stakeholders{\textquoteright} power is unequal, so will be the balance of the network. The case of open source software development provides the key to ensuring that stakeholders are not oppressed in a network unbalanced by hierarchical power. This relies on the phenomenon of exit-based empowerment that flows from the open source software licence. However, it can be extended to the design of governance networks given certain idealising assumptions, and even when these do not hold, useful lessons for the future reform of Internet governance arrangements remain.},
	author = {Jeremy Malcolm}
}
@conference {630,
	title = {OpenBQR: a framework for the assessment of OSS},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {173 - 186},
	publisher = {Springer},
	organization = {Springer},
	chapter = {14},
	abstract = {People and organizations that are considering the adoption of OSS, or that need to choose among different OS products face the problem of evaluating OSS in a systematic, sound and complete way. While several proposals concerning the evaluation of costs and benefits exist, little attention has been given to the evaluation of technical qualities and, in general, to the {\textquotedblleft}usage-oriented{\textquotedblright} issues. In this paper the existing proposals are examined, the different types of qualities and issues that are relevant to potential users are described, and a coherent and innovative method for the evaluation of OSS is proposed. The proposed method is expected to support the potential user in the evaluation and choice of OSS in a flexible way, taking into account all the aspects that are relevant to the user.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_14},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OpenBQR.pdf},
	author = {Taibi, Davide and Lavazza, Luigi and Morasca, Sandro}
}
@article {flosswp361,
	title = {Out of Box Experience Issues of Free and Open Source Software},
	year = {2007},
	month = {July},
	abstract = {Abstract. This study addresses the Out-Of-Box Experience (OOBE) usability issues of Free and Open Source Software (F/OSS) considering outcomes of distributed development process and high number of available product choices. A methodology is presented, usability experiments are conducted and results are discussed. The objective was to determine key factors that affect usability of F/OSS during OOBE and first hours of use. We concluded that OOBE of F/OSS was significant in software usability perception and possible adoption. User experience, visible structure, consistency and functionality of the interface had significant impact on OOBE and first hours of use. Neither online support, nor product box appearance appeared as important.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/gokturkcetin},
	author = {G{\"o}kt{\"u}rk Mehmet and G{\"o}rkem {\c C}etin}
}
@unpublished {flosswp363,
	title = {Quality Improvement in Volunteer Free and Open Source Software Projects},
	year = {2007},
	month = {March},
	abstract = {Free and open source software has had a major impact on the computer industry since the late 1990s and has changed the way software is perceived, developed and deployed in many areas. Free and open source software, or FOSS, is typically developed in a collaborative fashion and the majority of contributors are volunteers. Even though this collaborative form of development has produced a significant body of software, the development process is often described as unstructured and unorganized. This dissertation studies the FOSS phenomenon from a quality perspective and investigates where improvements to the development process are possible. In particular, the focus is on release management since this is concerned with the delivery of a high quality product to end-users. This research has identified considerable interest amongst the FOSS community in a novel release management strategy, time based releases. In contrast to traditional development which is feature-driven, time based releases use time rather than features as the criterion for the creation of a new release. Releases are made after a specific interval, and new features that have been completed and sufficiently tested since the last release are included in the new version. This dissertation explores why, and under which circumstances, the time based release strategy is a viable alternative to feature-driven development and discusses factors that influence a successful implementation of this release strategy. It is argued that this release strategy acts as a coordination mechanism in large volunteer projects that are geographically dispersed. The time based release strategy allows a more controlled development and release process in projects which have little control of their contributors and therefore contributes to the quality of the output.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/michlmayr-phd.pdf},
	author = {Martin Michlmayr}
}
@conference {994,
	title = {Recommending Emergent Teams},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {5 - 5},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {To build successful complex software systems, developers must collaborate with each other to solve issues. To facilitate this collaboration, specialized tools, such as chat and screen sharing, are being integrated into development environments. Currently, these tools require a developer to maintain a list of other developers with whom they may wish to communicate and to determine who within this list has expertise for a specific situation. For large, dynamic projects, like several successful open-source projects, these requirements place an unreasonable burden on the developer. In this paper, we show how the structure of a team emerges from how developers change software artifacts. We introduce the Emergent Expertise Locator (EEL) that uses emergent team information to propose experts to a developer within their development environment as the developer works. We found that EEL produces, on average, results with higher precision and higher recall than an existing heuristic for expertise recommendation.},
	keywords = {bugzilla, developers, eclipse, evolution, expertise, Firefox, teams},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300005.pdf},
	author = {Minto, Shawn and Murphy, Gail C.}
}
@conference {647,
	title = {Release Management in Free Software Projects: Practices and Problems},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {295 - 300},
	publisher = {Springer},
	organization = {Springer},
	chapter = {31},
	abstract = {Release management plays an important role in every software project since it is concerned with the delivery of a high quality product to end-users. This paper explores release practices employed by volunteer free software projects and shows problems that occur. A challenge that has been identified is the difficulty of coordinating a distributed team of volunteers in order to align their work for a release.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Release\%20Management\%20in\%20Free\%20Software.pdf},
	author = {Martin Michlmayr and Hunt, Francis and Probert, David}
}
@article {86,
	title = {The role of face-to-face meetings in technology-supported self-organizing distributed teams},
	journal = {Ieee Transactions on Professional Communication},
	volume = {50},
	number = {3},
	year = {2007},
	note = {Times Cited: 0},
	pages = {185-203},
	abstract = {We examine the role of face-to-face meetings in the context of technology-supported self-organizing distributed (or virtual teams), specifically Free/Libre Open Source Software (FLOSS) development teams. Based on a qualitative inductive analysis of data from interviews and observations at FLOSS conferences, we identify a variety of settings in which developers meet face-to-face, and we point out the activities performed in these settings and the benefits obtained. Contrary to conventional wisdom about distributed teams, FLOSS developers generally do not meet face-to-face until the project is well under way. An additional benefit offace-to-face meetings is time away from a regular job and speed of interaction for certain kinds of tasks.},
	author = {Kevin Crowston and James Howison and Chengetai Masango and Eseryel, U. Yeliz}
}
@proceedings {144,
	title = {Social capital, structural holes and team composition: collaborative networks of the open source software community},
	year = {2007},
	keywords = {NotreDameArchive},
	author = {Yong Tan and Vijay Mookerjee and Param Vir Singh}
}
@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}
}
@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 {1226,
	title = {Understanding the KDE Social Structure through Mining of Email Archive},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	note = {"Our data source is constituted by e-mails sent to KDE mailing-lists and archived by MARC"

"Two problems quickly arise: neither the e-mails addresses nor the names can be considered unique. Consequently, we used an in-depth search algorithm to put together {\textquotedblleft}name-email{\textquotedblright} couples corresponding to a same contributor. Indeed, the algorithm suggests possible merges."

"There is a specific mailing list in our data set, kde-commit, which gathers automatic notifications from the revision control system (RCS)....We measure {\textquotedblleft}commit{\textquotedblright} by the number of messages sent to the {\textquotedblleft}kde-commit{\textquotedblright} mailing list. However, we did not count {\textquotedblleft}silent{\textquotedblright} commits, nor usual messages sent to this mailing list."

"We measured activities done in BTS in two ways: {\textquotedblleft}bug opener{\textquotedblright} and {\textquotedblleft}non bug opener{\textquotedblright}.	First, we counted the number of modifications done by the contributor who opened the concerned bug report. "
},
	abstract = {In order to achieve a better understanding of FLOSS social structure, we need a definition of social position. From a theoretical perspective, we propose to think the participation as a trajectory. Empirically, we use optimal matching to build a typology of participation trajectories based on KDE email archives. We show how these trajectories structure the community as a whole by combining these results with a social network analysis.},
	keywords = {bug tracking system, bugzilla, commit, email, email archive, kde, mailing list, participation, revision control, social network analysis},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd_studer_et_all_full.pdf},
	author = {Studer, Matthias and M{\"u}ller, Beno{\^\i}t and Ritschard, Gilbert}
}
@conference {628,
	title = {Using Repository of Repositories (RoRs) to Study the Growth of F/OSS Projects: A Meta-Analysis Research Approach},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {147 - 160},
	publisher = {Springer},
	organization = {Springer},
	chapter = {12},
	abstract = {Free/Open Source Software (F/OSS) repositories contain valuable data and their usefulness in studying software development and community activities continues to attract a lot of research attention. A trend in F/OSS studies is the use of metadata stored in a repository of repositories or RoRs. This paper utilizes data obtained from such RoRs -FLOSSmole- to study the types of projects being developed by the F/OSS community. We downloaded projects by topics data in five areas (Database, Internet, Software Development, Communications, and Games/Entertainment) from Flossmole{\textquoteright}s raw and summary data of the sourceforge repository. Time series analysis show the numbers of projects in the five topics are growing linearly. Further analysis supports our hypothesis that F/OSS development is moving {\textquotedblleft}up the stack{\textquotedblright} from developer tools and infrastructure support to end-user applications such as Databases. The findings have implications for the interpretation of the F/OSS landscape, the utilization and adoption of open source databases, and problems researchers might face in obtaining and using data from RoRs.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_12},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Using\%20Repository\%20of\%20Repositories.pdf},
	author = {Sowe, Sulayman and Lefteris Angelis and Stamelos, I. and Y. Manolopoulos}
}
@conference {1213,
	title = {Working with Open Source Development Data: Considerations triggered by a study of bug scenarios},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	month = {2007},
	abstract = {The retrieval and preparation of public data on software development calls for more than just technical skills. In 
addition, care and judgement are needed to avoid disproportionate costs to the providers of data or unnecessary embarrassment to the participants tracked in the data. Taking the extraction of bug scenarios as a use case, we illustrate these concerns and discuss how they could be translated into social requirements that would help to make retrieval and preparation a sustainable exercise. In particular, we call for more efforts to establish institutional repositories of public data on software development and, besides, we suggest that reviewers could play a role in making sure that empirical research is performed in a way that does not bring the long-term relationship between software developers and researchers in jeopardy. },
	keywords = {bug reports, bug scenarios, Data Collection},
	attachments = {https://flosshub.org/sites/flosshub.org/files/denBesten-wopdasd.pdf},
	author = {den Besten, Matthijs and Masmoudi, H{\'e}la and Jean-Michel Dalle}
}
@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}
}
@conference {689,
	title = {Evolution of Open Source Communities},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	note = {"we took snapshots of its membership at regular intervals"
"we chose a one year period"
"we retrieve the list of core developers ordered by their number of inbound messages, as noted above."},
	pages = {21 - 32},
	publisher = {Springer},
	organization = {Springer},
	abstract = {The goal of this paper is to document the evolution of a portfolio of related open source communities over time. As a case study, we explore the subprojects of the Apache project, one of the largest and most visible open source projects. We extract the community structure from the mailing list data, and study how the subcommunities evolve, and are interrelated over time. Our analysis leads us to propose the following hypotheses about the growth of open source communities: (1) communities add new developers by a process of preferential attachment; (2) links between existing communities are also subject to preferential attachment; (3) developers will migrate between communities together with other collaborators; and (4) information flow follows project dependencies. In particular, we are concerned with the underlying factors that motivate the migration between communities, such as information flow, co-worker ties, and project dependencies.
},
	keywords = {apache, COMMUNITY, core, developers, email, email archives, mailing list, membership},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Evolution\%20of\%20Open\%20Source\%20Communities.pdf},
	author = {Weiss, Michael and Moroiu, Gabriella and Zhao, Ping}
}
@conference {675,
	title = {A graphical installation system for the GNU/Linux Debian distribution},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {337 - 338},
	publisher = {Springer},
	organization = {Springer},
	abstract = {One of the main objectives of the Centro di Competenza sul Software Libero del Politecnico di Torino is to provide custom GNU/Linux distribution to the Public Administration, small and medium enterprise and schools. Debian GNU/Linux was choosen as the base for the custom distributions because of its strong support of free software and its long-standing technical merits: minimalist hardware requirement, the best available packaging system, support for 13 different architectures and a strict set of quality guidelines adopted by all the active Debian developers. The only foreseeable limitation, the Debian default text-based installer, was overriden by restarting the development of the then-abandoned Debian graphical installer. Now the new graphical installer is developed by tens of people and it will be included in the next official Debian release.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_35},
	attachments = {https://flosshub.org/sites/flosshub.org/files/A\%20graphical\%20installation\%20system.pdf},
	author = {Attilio, Fiandrotti and Di Nunzio, Pierluigi and Di Gregorio, Federico and Meo, Angelo}
}
@conference {692,
	title = {How is it possible to profit from innovation in the absence of any appropriability?},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {333 - 334},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Open Source Software (OSS) represents an {\textquotedblleft}open innovation{\textquotedblright} paradigm based on knowledge produced and shared by developers and users. New findings from a large survey of European software companies show that: (i) the OSS business model is currently involving almost one third of the industry, although with different intensity; (ii) compared with pure proprietary software producers, OSS firms have a broader product portfolio and are more diversified; moreover, (iii) OSS firms provide more complementary services to their customers; (iv) over time OSS firms increase the share of OS turnover out of the total turnover, becoming more and more OSS oriented; (v) both NOSS and OSS firms do not consider appropriability as a crucial requirement for innovation and do not consider the lack of appropriability as an obstacle to profitability.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/How\%20is\%20it\%20possible\%20to\%20profit.pdf},
	author = {Andrea Bonaccorsi and Lucia Piscitello and Monica Merito and Cristina Rossi}
}
@conference {693,
	title = {Impact of Social Ties on Open Source Project Team Formation},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	note = {"we randomly selected 1030 new projects that were registered between X and X in 2005. A web crawler downloaded the HTML files containing project summary data and developer information on the date of registration."},
	month = {2006///},
	pages = {307 - 317},
	publisher = {Springer},
	organization = {Springer},
	abstract = {In this paper, we empirically examined the role of social ties in OSSD team formation and developer joining behavior. We find that the existence and the amount of prior social relations in the network do increase the probability of an OSS project to attract more developers. Interestingly, for projects without preexisting social ties, developers tend to join the project initiated by people with less OSSD experience. This research fills a gap in the open source literature by conducting an empirical investigation of the role of social relations on project team formation behavior. Furthermore, the adoption of social network analysis, which has received little attention in the OSS literature, can yield some interesting results on the interactions among OSS developers.
},
	keywords = {developers, metadata, social network analysis, sourceforge},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Impact\%20of\%20Social\%20Ties\%20on\%20Open\%20Source\%20Project.pdf},
	author = {Hahn, Jungpil and Moon, Jae and Zhang, Chen}
}
@article {141,
	title = {Impacts of license choice and organizational sponsorship on user interest and development activity in open source software projects},
	journal = {Information Systems Research},
	volume = {17},
	number = {2},
	year = {2006},
	note = {Times Cited: 1},
	pages = {126-144},
	abstract = {What differentiates successful from unsuccessful open source software projects? This paper develops and tests a model of the impacts of license restrictiveness and organizational sponsorship on two indicators of success: user interest in, and development activity on, open source software development projects. Using data gathered from Freshmeat.net and project home pages, the main conclusions derived from the analysis are that (1) license restrictiveness and organizational sponsorship interact to influence user perceptions of the likely utility of open source software in such a way that users are most attracted to projects that are sponsored by nonmarket organizations and that employ nonrestrictive licenses, and (2) licensing and sponsorship address complementary developer motivations such that the influence of licensing on development activity depends on what kind of organizational sponsor a project has. Theoretical and practical implications are discussed, and the paper outlines several avenues for future research.},
	author = {Katherine Stewart and Ammeter, A. P. and Maruping, L. M.}
}
@article {Grewal:2006:LLL:1246148.1246155,
	title = {Location, Location, Location: How Network Embeddedness Affects Project Success in Open Source Systems},
	journal = {Management Science},
	volume = {52},
	number = {7},
	year = {2006},
	month = {July},
	pages = {1043{\textendash}1056},
	publisher = {INFORMS},
	address = {Institute for Operations Research and the Management Sciences (INFORMS), Linthicum, Maryland, USA},
	abstract = {The community-based model for software development in open source environments is becoming a viable alternative to traditional firm-based models. To better understand the workings of open source environments, we examine the effects of network embeddedness---or the nature of the relationship among projects and developers---on the success of open source projects. We find that considerable heterogeneity exists in the network embeddedness of open source projects and project managers. We use a visual representation of the affiliation network of projects and developers as well as a formal statistical analysis to demonstrate this heterogeneity and to investigate how these structures differ across projects and project managers. Our main results surround the effect of this differential network embeddedness on project success. We find that network embeddedness has strong and significant effects on both technical and commercial success, but that those effects are quite complex. We use latent class regression analysis to show that multiple regimes exist and that some of the effects of network embeddedness are positive under some regimes and negative under others. We use project age and number of page views to provide insights into the direction of the effect of network embeddedness on project success. Our findings show that different aspects of network embeddedness have powerful but subtle effects on project success and suggest that this is a rich environment for further study.},
	keywords = {affiliation network, age, developers, latent class analysis, network embeddedness, open source software, page views, perl, project success, registration, sourceforge},
	issn = {0025-1909},
	doi = {10.1287/mnsc.1060.0550},
	url = {http://portal.acm.org/citation.cfm?id=1246148.1246155},
	author = {Grewal, Rajdeep and Lilien, Gary L. and Mallapragada, Girish}
}
@conference {Robles:2006:MLS:1137983.1137986,
	title = {Mining large software compilations over time: another perspective of software evolution},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {3{\textendash}9},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {With the success of libre (free, open source) software, a new type of software compilation has become increasingly common. Such compilations, often referred to as {\textquoteright}distributions{\textquoteright}, group hundreds, if not thousands, of software applications and libraries written by independent parties into an integrated system. Software compilations raise a number of questions that have not been targeted so far by software evolution, which usually focuses on the evolution of single applications. Undoubtedly, the challenges that software compilations face differ from those found in single software applications. Nevertheless, it can be assumed that both, the evolution of applications and that of software compilations, have similarities and dependencies.In this sense, we identify a dichotomy, common to that in economics, of software evolution in the small (micro-evolution) and in the large (macro-evolution). The goal of this paper is to study the evolution of a large software compilation, mining the publicly available repository of a well-known Linux distribution, Debian. We will therefore investigate changes related to hundreds of millions of lines of code over seven years. The aspects that will be covered in this paper are size (in terms of number of packages and of number of lines of code), use of programming languages, maintenance of packages and file sizes.},
	keywords = {debian, distributions, evolution, large software collections, lines of code, loc, metrics, mining software repositories, size, sloc, sloccount, software evolution, software integrators},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137986},
	url = {http://doi.acm.org/10.1145/1137983.1137986},
	attachments = {https://flosshub.org/sites/flosshub.org/files/3miningLarge.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Martin Michlmayr and Amor, Juan Jose}
}
@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 {1229,
	title = {Regurgitate: Using GIT For F/LOSS Data Collection},
	booktitle = {1st Workshop on Public Data about Software Development (WoPDaSD 2006)},
	year = {2006},
	abstract = {We have created a new tool, regurgitate, for importing CVS repositories into the GIT source code management system. Important features of GIT include great expressiveness in capturing relationships between revisions and across files as well as extremely high-speed processing. These features make GIT an ideal platform for gathering detailed longitudinal metrics for open source projects. The availability of regurgitate facilitates using GIT as an analysis tool for that majority of open source projects that keep their repositories in CVS. In particular, GIT is fast enough that it is practical to replay the entire development history of a project commit-at-a-time, collecting metrics at each step. We demonstrate this process for a simple metric and a collection of benchmark F/LOSS repositories.},
	keywords = {cvs, cvsanaly, git, history, promise, regurgitate, scm},
	attachments = {https://flosshub.org/sites/flosshub.org/files/massey.pdf},
	author = {Bart Massey and Keith Packard}
}
@conference {707,
	title = {Reusable Parser Generation from Open Source Compilers},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {343 - 344},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Without Abstract},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_38},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Reusable\%20Parser\%20Generation.pdf},
	author = {Maeda, Kazuaki}
}
@unpublished {flosswp404,
	title = {A structurational perspective on leadership in technology-supported self-organizing small groups},
	year = {2006},
	month = {October},
	publisher = {Syracuse University School of Information Studies},
	type = {Working Paper},
	abstract = {In this conceptual paper, we present a structuration-based theory of leadership behaviours in virtual teams, that is to say, in self-organizing technology-supported small groups such as Free/Libre Open Source Software development teams. Such teams are often composed of members of relatively equal status or who are so disparate in background that formal organizational status seems irrelevant, reducing the usual leadership cues provided by organizational status and title. Building on behavioural leadership theory and structuration theory, we present a two-order theory of leadership. It describes four classes of first-order leadership behaviours (task coordination, substantive task contribution, group maintenance, and boundary spanning) and defines second-order leadership as behaviour that influences changes in the structure that guides group action. Specifically, we suggest that second-order leadership behaviours are those that build structures of signification in the form of interpretive schema, structures of domination in the form of role structures and structures of legitimation in the form of rules and norms. We argue that second-order leadership is enabled by first-order leadership, is therefore action embedded, and is grounded in processes that define the social identity of the group. We propose that effective teams will exhibit a paradoxical combination of shared, distributed first-order leadership complemented by strong, concentrated, and centralized second-order leadership. We conclude by suggesting future research that might be conducted to test and further elaborate our theory.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHeckmanMisiolek.pdf},
	author = {Kevin Crowston and Robert Heckman and Nora Misiolek}
}
@conference {1090,
	title = {A Topological Analysis of the Open Souce Software Development Community},
	booktitle = {Proceedings of the 38th Annual Hawaii International Conference on System Sciences},
	year = {2006},
	note = {"We extracted data from a 2003 data dump obtained from SourceForge. "
roles},
	pages = {1-10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Big Island, HI, USA},
	abstract = {The fast growth of OSS has increased the interest in studying the composition of the OSS community and its collaboration mechanisms. Moreover, the success of a project may be related to the underlying social structure of the OSS development community. In this paper, we perform a quantitative analysis of Open Source Software developers by studying the entire development community at SourceForge [26]. Statistics and social network properties are explored to find collaborations and the effects of different members in the OSS development community. Small world phenomenon and scale free behaviors are found in the SourceForge development network. These topological properties may potentially explain the success and efficiency of OSS development practices. We also infer from our analysis that weakly associated but contributing co-developers and active users may be an important factor in OSS development.},
	keywords = {contributors, developers, roles, social network analysis, social networks, sourceforge, srda, users},
	doi = {10.1109/HICSS.2005.57},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.132.6830\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/xuGao.pdf},
	author = {Jin Xu and Gao, Yongqin and Christley, S. and Madey, G.}
}
@inbook {896,
	title = {Understanding Free/Open Source Software Evolution},
	booktitle = {Software Evolution and Feedback: Theory and Practice},
	year = {2006},
	pages = {181-206},
	publisher = {John Wiley and Sons Inc.},
	organization = {John Wiley and Sons Inc.},
	address = {New York},
	author = {Walt Scacchi},
	editor = {Madhavji, N.H. and Lehman, M.M. and Ramil, J.F. and Perry, D.}
}
@article {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 {Anvik:2006:FTB:1134285.1134336,
	title = {Who should fix this bug?},
	booktitle = {Proceedings of the 28th international conference on Software engineering},
	series = {ICSE {\textquoteright}06},
	year = {2006},
	pages = {361{\textendash}370},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source development projects typically support an open bug repository to which both developers and users can report bugs. The reports that appear in this repository must be triaged to determine if the report is one which requires attention and if it is, which developer will be assigned the responsibility of resolving the report. Large open source developments are burdened by the rate at which new bug reports appear in the bug repository. In this paper, we present a semi-automated approach intended to ease one part of this process, the assignment of reports to a developer. Our approach applies a machine learning algorithm to the open bug repository to learn the kinds of reports each developer resolves. When a new report arrives, the classifier produced by the machine learning technique suggests a small number of developers suitable to resolve the report. With this approach, we have reached precision levels of 57\% and 64\% on the Eclipse and Firefox development projects respectively. We have also applied our approach to the gcc open source development with less positive results. We describe the conditions under which the approach is applicable and also report on the lessons we learned about applying machine learning to repositories used in open source development.},
	keywords = {bug fixing, bug report, bug report assignment, bug triage, eclipse, Firefox, gcc, issue tracking, machine learning, problem tracking},
	isbn = {1-59593-375-1},
	doi = {10.1145/1134285.1134336},
	url = {http://doi.acm.org/10.1145/1134285.1134336},
	author = {Anvik, John and Hiew, Lyndon and Murphy, Gail C.}
}
@conference {Ohira:2005:ACK:1083142.1083163,
	title = {Accelerating cross-project knowledge collaboration using collaborative filtering and social networks},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {111-115},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Vast numbers of free/open source software (F/OSS) development projects use hosting sites such as Java.net and SourceForge.net. These sites provide each project with a variety of software repositories (e.g. repositories for source code sharing, bug tracking, discussions, etc.) as a media for communication and collaboration. They tend to focus on supporting rich collaboration among members in each project. However, a majority of hosted projects are relatively small projects consisting of few developers and often need more resources for solving problems. In order to support cross-project knowledge collaboration in F/OSS development, we have been developing tools to collect data of projects and developers at SourceForge, and to visualize the relationship among them using the techniques of collaborative filtering and social networks. The tools help a developer identify {\textquotedblleft}who should I ask?{\textquotedblright} and {\textquotedblleft}what can I ask?{\textquotedblright} and so on. In this paper, we report a case study of applying the tools to F/OSS projects data collected from SourceForge and how effective the tools can be used for helping cross-project knowledge collaboration.},
	keywords = {collaborative filtering, developers, knowledge collaboration, projects, social networks, sourceforge, visualization tool},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083163},
	url = {http://doi.acm.org/10.1145/1082983.1083163},
	attachments = {https://flosshub.org/sites/flosshub.org/files/111Accelerating.pdf},
	author = {Ohira, Masao and Ohsugi, Naoki and Ohoka, Tetsuya and Matsumoto, Ken-ichi}
}
@conference {735,
	title = {An Analysis of COSPA - A Consortium for Open Source in the Public Administration},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {125-129},
	abstract = {This paper reflects on a two-year EU funded specific research targeted project that officially began in January 2004 entitled COSPA, a Consortium for studying, evaluating and supporting the introduction of Open Source Software and Open Data Standards in the Public Administration. COSPA focuses on office automation and desktop system software and aims at rigorously measuring the effort, costs and benefits of a transition to Open Source. The project involves 15 European Universities and Public Administrations from Italy, Hungary, Ireland, Denmark, UK, Belgium and about sixty observers, including the University of Alberto (Canada), Victoria University of Wellington (New Zealand) and the United Nations Educational Scientific and Cultural Organisation (UNESCO).},
	url = {http://pascal.case.unibz.it/handle/2038/624},
	author = {Morgan, Lorraine}
}
@conference {728,
	title = {Assessing the Role of Open Source Software in the European Secondary Software Sector: A Voice from Industry},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {82-87},
	abstract = {This paper addresses the open source software (OSS) phenomenon from an industry perspective and reveals a number of complexities surrounding the role of OSS in the secondary software sector. It presents the research results of an international workshop which was hosted with the explicit intention of extracting the voice of key industrial stakeholders. The data was gathered and analysed using a qualitative approach which revealed the key strengths and weaknesses of OSS from an industrial perspective. This formed the foundations for developing a framework describing the emerging commercial incarnation of OSS (we refer to this as Open Source Software, Inc.) The paper concludes that the European secondary software sector recognise the benefits of leveraging OSS but are aware of key issues pertinent to such an end.},
	url = {http://pascal.case.unibz.it/handle/2038/752},
	author = {{\r A}gerfalk, P{\"a}r J and Deverell, Andrea and Fitzgerald, Brian and Morgan, Lorraine}
}
@conference {729,
	title = {Communication, coordination and control in distributed development: an OSS case study},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {88-92},
	abstract = {It has been claimed that distributed development practices in OSS development may be a model for enterprise development practices of the future. With this in mind, we have conducted a study of one OSS project, namely ArgoUML, with a view to understanding development practice within the project, and specifically to considering possible differences from traditional (non-OSS) distributed development conducted in a commercial project. We do this by explicitly considering issues of communication, coordination and control. Our findings suggest that primary differences lie in control and resulting project structures, motivated through differing goals. We comment on the open question of how the advantages of one development context can be realised in the other.},
	url = {http://pascal.case.unibz.it/handle/2038/769},
	author = {Persson, Anna and Lings, Brian and Lundell, Bj{\"o}rn and Mattsson, Anders and {\"A}rlig, Ulf}
}
@conference {743,
	title = {Communication from scratch: towards accessible open source information systems},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {179-186},
	abstract = {This paper is intended to provide an overview of a unifying and inclusive approach to open source information systems. In this respect the paper matches the fundamental aims of the Open Source Systems (2005) Conference. This approach can be characterised as communication from scratch. Firstly, we will provide an explanation of our approach to inclusive design and consider emerging perspectives on the nature of accessibility in the wider sense. Secondly, we will introduce the concept of communication from scratch and provide an explanation of the benefits of a convergent gradualism. Thirdly we will explain how these ideas have helped to shape our understanding of open source information processing, a concept which encompasses several of the conference themes and provides a unifying interface to our earlier work on accessible system design. Lastly, we will provide some concrete examples of the communication from scratch approach (crossing several domains) and introduce, ...},
	url = {http://pascal.case.unibz.it/handle/2038/759},
	author = {Crombie, David and Lenoir, Roger and McKenzie, Neil}
}
@conference {796,
	title = {Development-oriented Open Source eLearning Tool Evaluation: the Edukalibre Approach},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {341-344},
	author = {Botturi, Luca and Chris Tebb and Vania Dimitrova and Drew Withworth and Julika Matravers and Jutta Geldermann and Isabelle Hubert}
}
@conference {725,
	title = {EDOS: Environment for the Development and Distribution of Open Source Software},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {66-70},
	abstract = {The open-source software community is now comprised of a very large and growing number of contributors and users. The GNU/Linux operating system for instance has an estimated 18 million users worldwide and its contributing developers can be counted by thousands. The critical mass of contributors taking part in various opensource projects has helped to ensure high quality for open source software. However, despite the achievements of the open-source software industry, there are issues in the production of large scale open-source software (OSS) such as the GNU/Linux operating system that have to be addressed as the numbers of users, of contributors, and of available applications grow. EDOS is a European project supported by IST started October 2004 and ending in 2007, whose objective is to provide a new generation of methodologies, theoretical models, technical tools and quality models specifically tailored to OSS engineering and to software distribution over the Interne...},
	url = {http://pascal.case.unibz.it/handle/2038/737},
	author = {Abiteboul, Serge and Leroy, Xavier and Vrdoljak, Boris and Di Cosmo, Roberto and Fermigier, St{\'e}fane and Lauri{\`e}re, St{\'e}phane and Lepied, Fr{\'e}d{\'e}ric and Pop, Radu and Villard, Florent and Smets, Jean-Paul and Bryce, Ciar{\'a}n and Dittrich, Klaus R. and Milo, Tova and Sagi, Assaf and Shtossel, Yotam and Panto, Eleonora}
}
@conference {800,
	title = {Evolution of Open-Source Code Bases EVOSC 2005},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {359},
	abstract = {The very essence of open- source software is that
it enables custom evolutions. These evolutions should be
designed and managed carefully, since merging the main
trunk with custom branches is often critical for inheriting
evolutions that are not at the core interest of the independent
developer.},
	author = {Mattia Monga and Andrea Trentini}
}
@conference {731,
	title = {Evolution of Volunteer Participation in Libre Software Projects: Evidence from Debian},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	note = {"For each release we have retrieved the corresponding sources.gz file (see below) from the Debian archive. From it we have extracted information about the packages and their maintainers...."
},
	pages = {100-107},
	abstract = {Most libre software projects rely on the work of volunteers. Therefore, attracting people who contribute their time and technical skills is of paramount importance, both in technical and economic terms. This reliance on volunteers leads to some fundamental management challenges: volunteer contributions are inherently difficult to predict, plan and manage, especially in the case of large projects. In this paper we analyze the evolution in time of the human resources of one of the largest and most complex libre software projects composed primarily of volunteers, the Debian project. Debian currently has around 1300 volunteers working on several tasks: much activity is focused on packaging software applications and libraries, but there is also major work related to the maintenance of the infrastructure needed to sustain the development. We have performed a quantitative investigation of data from almost seven years, studying how volunteer involvement has affected the software...},
	keywords = {contributors, debian, maintainers, PopCon, popularity, Volunteers},
	url = {http://pascal.case.unibz.it/handle/2038/857},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles_barahona_michlmayr-evolution_participation.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Martin Michlmayr}
}
@article {flosswp184,
	title = {Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary Code (updated)},
	year = {2005},
	note = {"For each design, we report data on the number of source files, the number of dependencies, the density of the DSM (i.e., the number of dependencies per source file pair) the propagation cost and the clustered cost. We also provide data on the average complexity of source files, in terms of the number of functions and lines of code."},
	month = {June},
	abstract = {This paper reports data from a study that seeks to characterize the differences in design structure between complex software products. In particular, we use Design Structure Matrices (DSMs) to map the dependencies between the elements of a design and define metrics that allow us to compare the structures of different designs. We first use these metrics to compare the architectures of two software products - the Linux operating system and the Mozilla web browser - that were developed via contrasting modes of organization: specifically, open source versus proprietary development. We then track the evolution of Mozilla, paying particular attention to a purposeful "re-design" effort that was undertaken with the intention of making the product more "modular." We find significant differences in structure between Linux and the first version of Mozilla, suggesting that Linux had a more modular architecture. We also find that the redesign of Mozilla resulted in an architecture that was significantly more modular than that of its predecessor, and indeed, than that of Linux. Our results, while exploratory, are consistent with a view that different modes of organization are associated with designs that possess different structures. However, we also illustrate that purposeful managerial actions can have a large impact on structure. This latter result is important given recent moves to release proprietary software into the public domain. These moves are likely to fail unless the product possesses an architecture that facilitates participation. Our paper provides evidence that a tightly-coupled design can be adapted to meet this objective.},
	keywords = {complexity, cost, dependencies, functions, lines of code, linux, loc, mozilla, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/maccormackrusnakbaldwin2.pdf},
	author = {Alan MacCormack and John Rusnak and Carliss Baldwin}
}
@article {1393,
	title = {Hipikat: a project memory for software development},
	journal = {IEEE Transactions on Software Engineering},
	volume = {31},
	year = {2005},
	month = {06/2005},
	pages = {446 - 465},
	abstract = {Sociological and technical difficulties, such as a lack of informal encounters, can make it difficult for new members of noncollocated software development teams to learn from their more experienced colleagues. To address this situation, we have developed a tool, named Hipikat, that provides developers with efficient and effective access to the group memory for a software development project that is implicitly formed by all of the artifacts produced during the development. This project memory is built automatically with little or no change to existing work practices. After describing the Hipikat tool, we present two studies investigating Hipikat{\textquoteright}s usefulness in software modification tasks. One study evaluated the usefulness of Hipikat{\textquoteright}s recommendations on a sample of 20 modification tasks performed on the Eclipse Java IDE during the development of release 2.1 of the Eclipse software. We describe the study, present quantitative measures of Hipikat{\textquoteright}s performance, and describe in detail three cases that illustrate a range of issues that we have identified in the results. In the other study, we evaluated whether software developers who are new to a project can benefit from the artifacts that Hipikat recommends from the project memory. We describe the study, present qualitative observations, and suggest implications of using project memory as a learning aid for project newcomers.},
	issn = {0098-5589},
	doi = {10.1109/TSE.2005.71},
	author = {Cubranic, D. and Murphy, G. C. and Singer, J. and Booth, K.S.}
}
@conference {798,
	title = {An International Master Programme in Free Software in the European Higher Education Space},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {349-352},
	abstract = {The Universitat Oberta de Catalunya (Open University of Catalonia, UOC) offers an International Master programme in Free Software. The first edition of this master programme began on November 2003 and there are about 240 students currently enrolled at the different specialities offered by the program. In this paper, the design, the methodology and the first few conclusions drawn from this higher education experience are discussed and summarized. After this master programme was changed to accomplish with European Higher Education Space (EHES).},
	keywords = {education, free software, FS community, GNU/Linux, learning, master programme, software development, university},
	url = {http://pascal.case.unibz.it/handle/2038/713},
	author = {Meg{\'\i}as, David and Serra, Jordi and Macau, Rafael}
}
@article {63,
	title = {The Jikes research virtual machine project: Building an open-source research community},
	journal = {Ibm Systems Journal},
	volume = {44},
	number = {2},
	year = {2005},
	note = {Times Cited: 3},
	pages = {399-417},
	abstract = {This paper describes the evolution of the Jikes (TM) Research Virtual Machine project from an IBM internal research project, called Jalapeno, into an open-source project. After summarizing the original goals of the project, we discuss the motivation for releasing it as an open-source project and the activities performed to ensure the success of the project. Throughout, we highlight the unique challenges of developing and maintaining an open-source project designed specifically to support a research community.},
	author = {Alpern, B. and Augart, S. and Blackburn, S. M. and Butrico, M. and Cocchi, A. and Cheng, P. and Dolby, J. and Fink, S. and Grove, D. and Hind, M. and McKinley, K. S. and Mergen, M. and Moss, J. E. B. and Ngo, T. and Sarkar, V. and Trapp, M.}
}
@conference {771,
	title = {Linux on the portuguese schools: the Caixa M{\'a}gica experience},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {279-280},
	abstract = {This article depicts the experience of Caixa M{\'a}gica
in the deployment of 14.000 computers with dual boot in the
portuguese schools. Caixa M{\'a}gica role was preparing its
Linux distribution to become friendly to students and
teachers.
This project was very successful and is now beginning with a
second phase with 5.000 more computers.
In this experience report with present some of the obstacles
and achievements accomplished in {\textquotedblleft}Salas TIC{\textquotedblright}.},
	author = {Susana Nunes, and Fl{\'a}vio Moringa and Miguel Louren{\c c}o and Paulo Trezentos}
}
@conference {755,
	title = {Open Source, a development option},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {228-230},
	abstract = {The Open Source (OS) movement is one of the most amazing revolutions in last decades. It is probably the most successful collaborative project in history. Its philosophy: learn, innovate and share, has created an immense knowledge base which has been opened to everyone. It brings technology to everybody and empowers people, communities, governments and companies. The purpose of this paper is to show how OS solutions, methods and communities can support a number of key areas for a nation{\textquoteright}s development, at the same time that generates its own infrastructure which not only supports development but also has the potential to become a main business activity for that nation.},
	url = {http://pascal.case.unibz.it/handle/2038/1261},
	author = {Martinez, Arturo}
}
@conference {Stewart:2005:PAI:1042438.1043100,
	title = {A Preliminary Analysis of the Influences of Licensing and Organizational Sponsorship on Success in Open Source Projects},
	booktitle = {Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences - Volume 07},
	series = {HICSS {\textquoteright}05},
	year = {2005},
	note = {"Publicly available data on open source projects registered on the Freshmeat website (www.freshmeat.net) was used to test the hypotheses. Data was collected from each project{\textquoteright}s Freshmeat website at the start and end of an eight month period (March - December 2002)."
"We first selected three project categories from which to draw our sample. These were utilities, software development, and games."
"Within these categories we further differentiated between new projects, which had been registered on the site within the two weeks prior to our first data collection point and older projects that had been registered more than two weeks prior to our initial data collection."
},
	month = {2005},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {This paper develops and tests a model of the impact of	licensing restrictiveness	and	organizational sponsorship on the popularity and vitality of open source software (OSS) development projects. Using data gathered from Freshmeat.net and OSS project home pages the main conclusions derived from the analysis are that organizational sponsorship has a positive effect on project popularity by easing user concerns about cost and quality and that license restrictiveness may have a negative effect on popularity by reducing the perceived utility of open source software. Theoretical and practical implications are discussed, and the paper outlines several avenues for future research.},
	keywords = {contributors, developers, freshmeat, license analysis, licensing, metadata, popularity, restrictive, users},
	isbn = {0-7695-2268-8-7},
	doi = {http://dx.doi.org/10.1109/HICSS.2005.38},
	url = {http://dx.doi.org/10.1109/HICSS.2005.38},
	author = {Stewart, Katherine J. and Ammeter, Anthony P. and Maruping, Likoebe M.}
}
@conference {764,
	title = {Principles for a Dynamic Software Ecosystem},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {267},
	abstract = {The open source software movement reflects one of the most dramatic developments in today{\textquoteright}s dynamic information technology industry. Interestingly, some commentators have sought to posit open source against proprietary software. This paper argues that while open source and proprietary models may be based on different development and distribution philosophies, neither model is inherently superior.},
	url = {http://pascal.case.unibz.it/handle/2038/1424},
	author = {M{\"u}ller, Beno{\^\i}t}
}
@conference {785,
	title = {Quality Improvement in Volunteer Free Software Projects: Exploring the Impact of Release Management},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {309-310},
	abstract = {Even though free software has achieved great popularity and success in recent years, there are a number of product quality challenges facing the open source development model. There is significant room for further quality improvement and one area that deserves special attention is release management. This research will identify problems with current release practices, verify possible advantages of an increasingly popular release model, and develop interventions to improve release management in free software projects. The research also aims to answer the fundamental question as to how volunteer projects can deliver predictable and high quality software.},
	keywords = {free software, open source, process improvement, quality assurance, release management, volunteer projects},
	url = {http://pascal.case.unibz.it/handle/2038/1429},
	author = {Martin Michlmayr}
}
@article {flosswp244,
	title = {Quality Practices and Problems in Free Software Projects},
	year = {2005},
	month = {July},
	abstract = {Free software and open source projects are often perceived to be of high quality. It has been suggested that the high level of quality found in some free software projects is related to the open development model which promotes peer review. While the quality of some free software projects is comparable to if not better than that of closed source software, not all free software projects are successful and of high quality. Even mature and successful projects face quality problems, some of which are related to the unique characteristics of free software and open source as a distributed development model based primarily on volunteers. In exploratory interviews performed with free software and open source developers, common quality practices as well as actual quality problems have been identified. The results of these interviews are presented in this paper to take stock of the current status of quality in free software projects and to act as a starting point for the implementation of quality process improvement strategies.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/michlmayr_hunt_probert-quality_practices_problems.pdf},
	author = {Martin Michlmayr}
}
@conference {763,
	title = {Shared Source and Open Solutions: an e-Government Perspective},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {263-266},
	abstract = {Over the past four years, increasing commercialisation has been a significant influence on free and open source software. At the same time, the community based collaborative development model, which generally connotes open source, has also been studied and adopted by traditional software companies. These trends have led to an understanding that what separates open source from other software development approaches is the licensing model rather than the development model. Despite this, the two paradigms are rapidly starting to look very similar as open source is increasingly commercialised and established software companies integrate community based development into their value chain. This paper presents Microsoft{\textquoteright}s experience with its Intellectual Property Sharing programs and Shared Source Initiative. We also present the Solution Sharing Network, an environment that facilitates the sharing of solutions and best practices. We focus here on public sector customers who ...},
	url = {http://pascal.case.unibz.it/handle/2038/736},
	author = {Matusow, Jason and McGibbon, Stephen and Rowe, David}
}
@conference {790,
	title = {	Socialization practices in FLOSS development teams},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {322-323},
	abstract = {Socialization of new members into Free/Libre Open Source Software (FLOSS) development teams is an important but little studied process in producing effective teams of this type. This is a dissertation proposal for a virtual ethnographic study that looks at the mechanisms and processes used to socialize new members into the team in order to help maintain a common group identity and focus.},
	keywords = {development team, FLOSS, member, open source, socialization},
	url = {http://pascal.case.unibz.it/handle/2038/1438},
	author = {Chengetai Masango}
}
@article {flosswp243,
	title = {Software Process Maturity and the Success of Free Software Projects},
	year = {2005},
	month = {October},
	abstract = {The success of free software and open source projects has increased interest in utilizing the open source model for mature software development. However, the ad hoc nature of open source development may result in poor quality software or failures for a number of volunteer projects. In this paper, projects from SourceForge are assessed to test the hypothesis that there is a relationship between process maturity and the success of free software and open source projects. This study addresses the question of whether the maturity of particular software processes differs in unsuccessful and unsuccessful projects. Processes are identified which are key factors in successful free software projects. The insights gained from this study can be used improve the software process used by free software projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/michlmayr1.pdf},
	author = {Martin Michlmayr}
}
@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}
}
@conference {716,
	title = {A structurational perspective on leadership in Free/Libre Open Source Software teams},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {9-15},
	abstract = {In this conceptual paper, we present a structuration- based theory of leadership behaviours in self-organizing distributed teams such as Free/Libre Open Source Software development teams. Such teams are often composed of members of relatively equal status or who are so disparate in background that formal organizational status seems irrelevant, reducing the usual leadership cues provided by organizational status and title. Building on a functional view of leadership and structuration theory, we suggest that leaders are individuals who develop team structures that then guide the actions of team members. Specifically, we examine structures of signification in the form of shared mental models, structures of domination in the form of role structures and structures of legitimation in form of rules and norms. The main contribution of our paper is the integration of various social theories to describe emergent leadership behaviours in distributed teams. We develop a set of prop...},
	url = {http://pascal.case.unibz.it/handle/2038/623},
	author = {Kevin Crowston and Robert Heckman and Hala Annabi and Chengetai Masango}
}
@conference {742,
	title = {Using Open Source Middleware for Securing e-Gov Applications},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {172-178},
	abstract = {Nowadays, a global information infrastructure connects remote parties through the use of large scale networks, and many companies focus on developing e-services based on remote resources and on interaction between remote parties. In such a context, e-Government (e-Gov) systems became of paramount importance for the Public Administration, and many ongoing development projects are targeted on their implementation and release. For open source software to play an important role in this scenario, two main technological requirements must be fulfilled: (i) the identification and optimization of de facto standards for building e-Gov open source software components and (ii) a standard integration strategy of these components into an open source middleware layer, capable of conveying a completely open-source e-Gov solution. In this paper, we argue that e-Gov systems should be constructed on a open source middleware layer, providing full public responsibility in its development. W...},
	url = {http://pascal.case.unibz.it/handle/2038/1553},
	author = {Ardagna, Claudio Agostino and Damiani, Ernesto and Frati, Fulvio and Montel, Martin}
}
@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}
}
@proceedings {1195,
	title = {From Bazaar to Kibbutz: How Freedom Deals with Coherence in the Debian Project},
	year = {2004},
	note = {"I am a member of the Debian project since 2000."},
	pages = {71-75},
	abstract = {The goal of obtaining a coherent distribution of software packages where all programs interact smoothly increases its complexity with the number of applications, the number of architectures involved, and the number of system configurations supported. The Debian project aims at producing a software system with thousands of components running on eleven different hardware architectures, with three different operating
system kernels. This paper describes the project and how the work of hundreds of people that never meet one with another can be coordinated to produce reasonably robust and integrated systems.},
	keywords = {debian},
	attachments = {https://flosshub.org/sites/flosshub.org/files/monga72-76.pdf},
	author = {Monga, M.}
}
@article {129,
	title = {How effective developers investigate source code: An exploratory study},
	journal = {Ieee Transactions on Software Engineering},
	volume = {30},
	number = {12},
	year = {2004},
	note = {Times Cited: 6},
	pages = {889-903},
	abstract = {Prior to performing a software change task, developers must discover and understand the subset of the system relevant to the task. Since the behavior exhibited by individual developers when investigating a software system is influenced by intuition, experience, and skill, there is often significant variability in developer effectiveness. To understand the factors that contribute to effective program investigation behavior, we conducted a study of five developers performing a change task on a medium-size open source system. We isolated the factors related to effective program investigation behavior by performing a detailed qualitative analysis of the program investigation behavior of successful and unsuccessful developers. We report on these factors as a set of detailed observations, such as evidence of the phenomenon of inattention blindness by developers skimming source code. In general, our results support the intuitive notion that a methodical and structured approach to program investigation is the most effective. Index Terms-Software evolution, empirical software engineering, program investigation, program understanding.},
	author = {Robillard, M. P. and Coelho, W. and Murphy, G. C.}
}
@proceedings {1194,
	title = {Inside an Open Source Software Community: Empirical Analysis on Individual and Group Level},
	year = {2004},
	pages = {65-70},
	abstract = {An established Open Source Software community (Apache Cocoon) was explored using an online questionnaire about demographic data and individual and	group-related	factors.	Individual	factors encompassed forms of contributions, motivation, expertise and knowledge. Role structures, expectations towards other members, trust and collaboration issues were analysed at group level. More than 60\% of the developer community completed this questionnaire. Results provide a valuable basis for deeper understanding of knowledge sharing, collaboration and innovation processes in distributed work groups.},
	keywords = {apache, Survey},
	attachments = {https://flosshub.org/sites/flosshub.org/files/maass66-71.pdf},
	author = {Maass, W.}
}
@article {flosswp201,
	title = {Managing Volunteer Activity in Free Software Projects},
	year = {2004},
	month = {July},
	abstract = {During the last few years, thousands of volunteers have created a large body of free software. Even though this accomplishment shows that the free software development model works, there are some drawbacks associated with this model. Due to the volunteer nature of most free software projects, it is impossible to fully rely on participants. Volunteers may become busy and neglect their duties. This may lead to a steady decrease of quality as work is not being carried out. The problem of inactive volunteers is intensified by the fact that most free software projects are distributed, which makes it hard to quickly identify volunteers who neglect their duties. This paper shows Debian{\textquoteright}s approach to inactive volunteers. Insights presented here can be applied to other free software projects in order to implement effective quality assurance strategies.},
	keywords = {debian, volunteer, volunteer teams},
	attachments = {https://flosshub.org/sites/flosshub.org/files/michlmayr-mia.pdf},
	author = {Martin Michlmayr}
}
@conference {flosswp180,
	title = {Towards a Portfolio of FLOSS project Success Measures},
	booktitle = {Workshop on Open Source Software Engineering, International Conference on Software Engineering},
	year = {2004},
	month = {May},
	abstract = {Project success is one of the most widely used dependent variables in information systems research. However, conventional measures of project success are difficult to apply to Free/Libre Open Source Software projects. In this paper, we present an analysis of four measures of success applied to SourceForge projects: number of members of the extended development community, project activity, bug fixing time and number of downloads. We argue that these four measures provide different insights into the collaboration and control mechanisms of the projects.},
	keywords = {bug fixing, developers, downloads, project success, sourceforge, team, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowston04towards.pdf},
	author = {Kevin Crowston and Hala Annabi and Howison, James and Chengetai Masango}
}
@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.}
}
@conference {German03automatingthe,
	title = {Automating the measurement of open source projects},
	booktitle = {Proceedings of the 3rd Workshop on Open Source Software Engineering},
	year = {2003},
	note = {"We have chosen to use Evolution to illustrate some of the capabilities of SoftChange. We focus on the data provided by CVS logs and the CVS commit mailing list. Our data includes changes to the CVS repository from April 1998 to January 2003."},
	pages = {63{\textendash}67},
	abstract = {The proliferation of open source projects raises a number of vital economic, social, and software engineering questions that are subject of intense research. Based on experience analyzing numerous open source and commercial projects we propose a set of tools to support extraction and validation of software project data. Such tools would streamline empirical investigation of open source projects and make it possible to test existing and new theories about the nature of open source projects. Our soft- ware includes tools to extract and summarize information from mailing lists, CVS logs, ChangeLog files, and defect tracking databases. More importantly, it cross-links records from various data sources and identifies all contributors for a software change. We illustrate some of the capabilities by analyzing data from Ximian Evolution project.},
	keywords = {bug reports, bug tracking, changelog, cvs, defects, evolution, log files, logs, mailing list, scm, softchange, source code, ximian, ximian evolution},
	attachments = {https://flosshub.org/sites/flosshub.org/files/germanMockus2003.pdf},
	author = {German, Daniel and Audris Mockus}
}
@unpublished {flosswp129,
	title = {The Big Project That Never Ends{\textquoteright}: Role and Task Negotiation Within an Emerging Occupational Community},
	year = {2003},
	month = {December},
	abstract = {This dissertation involved in-depth interviews of over fifty open source developers in two major open source projects. The primary areas of interest were 1) conducting an ethnographic study of the work practices and culture of {\textquoteright}post-burecratic{\textquoteright} organizations to see what lessons these groups may hold for managing intellectual labor and 2) examining whether the open source movement represents a new professional model for software engineering.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mccormick.pdf},
	author = {Chip McCormick}
}
@conference {DBLP:conf/csmr/CapiluppiLM03,
	title = {Characteristics of Open Source Projects},
	booktitle = {7th European Conference on Software Maintenance and Reengineering (CSMR{\textquoteright}03)},
	year = {2003},
	note = {"We analyze a sample of around 400 projects from a popular OS project repository. "
no pdf to confirm what projects these are or what the repository is.[ms]},
	pages = {317-},
	abstract = {Most empirical studies about Open Source (OS)projects or products are vertical and usually deal with the flagship, successful projects. There is a substantial lack of horizontal studies to shed light on the whole population of projects, including failures. This paper presents a horizontal study aimed at characterizing OS projects. We analyze a sample of around 400 projects from a popular OS project repository. Each project is characterized by a number of attributes. We analyze these attributes statically and over time. The main results show that few projects are capable of attracting a meaningful community of developers. The majority of projects is made by few (in many cases one) person with a very slow pace of evolution.},
	keywords = {evolution, project success, repository},
	author = {Capiluppi, Andrea and Patricia Lago and Maurizio Morisio}
}
@article {flosswp111,
	title = {Episodes of Collective Invention},
	year = {2003},
	month = {August},
	abstract = {The process of developing technology through open discussion has been called collective invention. Open source software projects have this form. This paper documents two earlier episodes of collective invention and proposes a general model based on search theory. One episode was the development of mass production steel in the U.S. (1866-1885), and the second with early personal computers (1975-1985). Technical people openly discussed and shared these developing technologies between firms. Collective invention episodes begin with an invention or a change in legal restrictions. Hobbyists and startup firms experiment with practical methods of production and share their results through a social network whose members gradually form a new industry.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/meyer.pdf},
	author = {Peter Meyer}
}
@unpublished {flosswp164,
	title = {Kategorisierung von Open Source Projekten: Aufbau- und Ablauforganisation (in german) - Categorization of Open Source Projects: Operational and Organizational Structure},
	year = {2003},
	month = {September},
	abstract = {The number of open source projects is growing. The largest part can be found on large develompent portals. But open source is not open source, each project has unique characteristics. This paper examines operational and organizational characteristics, licencing, communication and documentation specifications of open source projects and explains the trove categorization model introduced by SourceForge.net.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/matuska.pdf},
	author = {Martin Matuska}
}
@article {flosswp128,
	title = {Knowledge Transfer in R\&D Outsourcing (and Linux-Vs-Windows)},
	year = {2003},
	month = {November},
	abstract = {Why did Microsoft not hire all those smart programmers who ended up developing Linux through the internet? Because, we answer, the value of the information about its operating system that Microsoft should have transferred to any of them to render her productive would have been too high compared to her expected individual contribution, so that after writing a contract with Microsoft the typical developer would have run away to sell the acquired knowledge on the market. On the other hand, knowledge transfer in R\&D outsourcing is not always so critical, and for example in the pharmaceutical and chemical industries research contracts are extensively used, usually in the context of a long term relationship between firm and innovator. We analyze this kind of repeated interaction, and find that when the knowledge-transfer problem is not blocking, the firm should transfer to the innovator as much information as it is compatible with the latter{\textquoteright}s incentive constraints.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/modica.pdf},
	author = {Salvatore Modica}
}
@article {flosswp130,
	title = {Open Source as a Complex Adaptive System - Published in Emergence 5 (3)},
	year = {2003},
	month = {November},
	abstract = {The Open Source community and its activities can be considered to have the characteristics of a system. The Open Source system is distinctive because it is neither controlled by a central authority that defines strategy and organization nor totally chaotic. It can be placed at a middle position between a planned system and a chaotic one. In this sort of position there are non-formal rules which allow the system to produce significant results. The Complex Adaptive System theory can be used to better understand and analyze the Open Source system. This work presents a description of the main characteristics of the functioning of the Open Source community regarding its organizational structure and development process. The concept of complex adaptive system is then introduced and its functioning mechanisms briefly described. Finally, we will interpret the characteristics of the Open Source community in the context of complex adaptive systems theory.},
	author = {Moreno Muffatto}
}
@article {flosswp97,
	title = {Participatory Usability: supporting proactive users},
	journal = {Proceedings of the 4th Annual Conference of the ACM Special Interest Group on Computer Human Interaction - New Zealand Chapter (CHINZ{\textquoteright}03)},
	year = {2003},
	month = {June},
	pages = {63{\textendash}68},
	publisher = {ACM SIGCHI New Zealand.},
	abstract = {After software has been released the opportunities for users to influence development can often be limited. In this paper we review the research on post-deployment usability and make explicit its connections to open source software development. We describe issues involved in the design of end-user reporting tools with reference to the Safari web browser and a digital library prototype.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nicholsmckaytwidale.pdf},
	author = {David M Nichols and Dana McKay and Michael B Twidale}
}
@proceedings {1177,
	title = {Quality and the Reliance on Individuals in Free Software Projects},
	year = {2003},
	month = {2003},
	pages = {105-109},
	attachments = {https://flosshub.org/sites/flosshub.org/files/105-109.pdf},
	author = {Martin Michlmayr and Hill, B.M.}
}
@proceedings {1178,
	title = {Studying the evolution of libre software projects using publicly available data},
	year = {2003},
	month = {2003},
	pages = {111-115},
	attachments = {https://flosshub.org/sites/flosshub.org/files/111-115.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona and Jose Centeno-Gonz{\'a}lez and Vicente Matellan-Olivera and Luis Rodero-Merino}
}
@proceedings {1167,
	title = {Tools for light-weight knowledge sharing in open-source software development},
	year = {2003},
	pages = {25-29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/25-29.pdf},
	author = {Cubranic, Davor and Holmes, Reid and Ying, Annie and Murphy, Gail C.}
}
@proceedings {1176,
	title = {Why OSS Folks Think SE Folks Are Clue-Impaired},
	year = {2003},
	pages = {91-97},
	attachments = {https://flosshub.org/sites/flosshub.org/files/91-97.pdf},
	author = {Bart Massey}
}
@article {65,
	title = {Analyzing cloning evolution in the Linux kernel},
	journal = {Information and Software Technology},
	volume = {44},
	number = {13},
	year = {2002},
	pages = {755-765},
	abstract = {Identifying code duplication in large multi-platform software systems is a challenging problem. This is due to a variety of reasons including the presence of high-level programming languages and structures interleaved with hardware-dependent low-level resources and assembler code, the use of GUI-based configuration scripts generating commands to compile the system, and the extremely high number of possible different configurations. This paper studies the extent and the evolution of code duplications in the Linux kernel. Linux is a large, multi-platform software system; it is based on the Open Source concept, and so there are no obstacles in discussing its implementation. In addition, it is decidedly too large to be examined manually: the current Linux kernel release (2.4.18) is about three million LOCs. Nineteen releases, from 2.4.0 to 2.4.18, were processed and analyzed, identifying code duplication among Linux subsystems by means of a metric-based approach. The obtained results support the hypothesis that the Linux system does not contain a relevant fraction of code duplication. Furthermore, code duplication tends to remain stable across releases, thus suggesting a fairly stable structure, evolving smoothly without any evidence of degradation. (C) 2002 Elsevier Science B.V. All rights reserved.},
	keywords = {cvs, kernel, lines of code, linux, loc, project success, source code},
	url = {web.soccerlab.polymtl.ca/~antoniol/publications/.../infsoft2002.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/infsoft2002.pdf},
	author = {Antoniol, G. and Villano, U. and Merlo, E. and Di Penta, M.}
}
@conference {1153,
	title = {Characterizing the OSS process},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	note = {"We have considered two well-known Open Source portals (FreshMeat [1] and SourceForge [2] )."
"Using pseudo-random sampling we have selected a sample of 400 projects (mostly from FreshMeat). Each project is described by several variables (programming language, type of license, size of source code, type of documentation available and others). By indirect means (analysis of the Changelog file, or CVS) it is also possible to compute the number of people working on the project, and the number of external contributors. From FreshMeat we get both a vitality index, that considers the number of releases per time period, and a popularity index, which is a first measure of the interest of users to the project (project URL hits, mixed with subscriptions to it)."},
	abstract = {The Open Source model of software development has gained the attention of both the business, the practitioners{\textquoteright} and the research communities. The Open Source process has been described by the seminal paper by Eric Raymond [4] and [5]. However, sound empirical studies are still very limited [3], [6].
Our goal is to investigate the OS process by empirical means, to analyze, characterize it, and possibly model it with quantitative models. It should be noted that the Open Source process provides open process and product data, and therefore is a rare opportunity for empirical research.
Our initial research focus is on the characterization of the process, starting from the evolution of OS projects. In traditional projects, a significant number of releases in a short time is usually considered an instability factor [7] and [8], while in the OSS community, it is an evidence of vitality, shows the commitment of the authors and the power of attraction of other programmers [9]. Is it possible to characterize the vitality of projects? And, can vitality be traced to some other characteristics of a project?},
	keywords = {bugs, change log, classification, cvs, downloads, freshmeat, metadata, patches, popularity, project success, release history, sourceforge, vitality},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CapiluppiLagoMorisio.pdf},
	author = {Capiluppi, Andrea and Patricia Lago and Maurizio Morisio}
}
@article {flosswp38,
	title = {Competing on Open Source: Strategies and Practise},
	year = {2002},
	month = {January},
	abstract = {This paper seeks to address the following issues: How do firms compete with open source? What resources become critical in managing their growth? What strategies do they adopt to co-exist with dominant proprietary software firms? How do they interface with communities of practice to exploit network externalities? What strategies do they adopt to lock-in developers? Based on a multiple case analysis the authors seek to draw initial conclusions about the key strategic aspects that underlie the open source initiatives. Finally they describe how for-profit firms can establish and sustain open source practice.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/madanmohan.pdf},
	author = {T.R. Madanmohan}
}
@unpublished {flosswp39,
	title = {Open Source Software and Software Patents: Finding the Common Ground in a Patent Pool},
	year = {2002},
	month = {May},
	abstract = {Software patents threaten the future of the OSS community, especially with the increased importance of software standards and the change in attitude in the organizations forming these standards. The OSS community does not exercise much influence over the policymakers who have legitimized software patents because of differences between the two groups{\textquoteright} motivations. There are many possible actions the OSS community could take, but an OSS patent pool is the best way for the OSS community to leverage both the patent system and the OSS culture to help protect the future of OSS.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/morgan.pdf},
	author = {Jason V. Morgan}
}
@article {flosswp68,
	title = {Open Source Software Communities and Industrial Districts: A Useful Comparison?},
	year = {2002},
	month = {February},
	abstract = {Aim of this paper is to add a new and complementary perspective on the existing economic analysis of open-source software by comparing the structure and evolution of open-source software communities and of industrial districts, a peculiar organisational form of production based on a large number of interacting small and medium sized enterprises. The comparison between open-source software communities and industrial districts, in spite of some major differences allows the recognition of the role played by agglomeration economies, an explicit analysis of the incentives structure - governing the private provision of complex public goods-, and an in depth study of the governance structure and evolution of these phenomena. The paper presents some simple simulations which show the dependence of the governance structure{\textquoteright}s evolution on transaction costs dynamics.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/maggioni.pdf},
	author = {Mario Maggioni}
}
@inbook {Madey_Freeh_Tynan_2002,
	title = {The open source software development phenomenon: An analysis based on social network theory},
	booktitle = {Proceedings of the Eighth Americas Conference on Information Systems},
	year = {2002},
	pages = {1806{\textendash}1813},
	abstract = {The OSS movement is a phenomenon that challenges many traditional theories in economics, software engineering, business strategy, and IT management. Thousands of software programmers are spending tremendous amounts of time and effort writing and debugging software, most often with no direct monetary compensation. The programs, some of which are extremely large and complex, are written without the benefit of traditional project management, change tracking, or error checking techniques. Since the programmers are working outside of a traditional organizational reward structure, accountability is an issue as well. A significant portion of internet e-commerce runs on OSS, and thus many firms have little choice but to trust mission-critical e-commerce systems to run on such software, requiring IT management to deal with new types of socio-technical problems. A better understanding of how the OSS community functions may help IT planners make more informed decisions and develop more effective strategies for using OSS software. We hypothesize that open source software development can be modeled as self-organizing, collaboration, social networks. We analyze structural data on over 39,000 open source projects hosted at SourceForge.net involving over 33,000 developers. We define two software developers to be connected part of a collaboration social network if they are members of the same project, or are connected by a chain of connected developers. Project sizes, developer project participation, and clusters of connected developers are analyzed. We find evidence to support our hypothesis, primarily in the presence of power-law relationships on project sizes (number of developers per project), project membership (number of projects joined by a developer), and cluster sizes. Potential implications for IT researchers, IT managers, and governmental policy makers are discussed.},
	keywords = {developers, social network analysis, social networks, sourceforge},
	url = {http://ais.bepress.com/cgi/viewcontent.cgi?article=1606\&context=amcis2002},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MadeyFreehAmcis2002.pdf},
	author = {Madey, G. and Freeh, V and Tynan, R}
}
@conference {Dinkelacker:2002:POS:581339.581363,
	title = {Progressive open source},
	booktitle = {Proceedings of the 24th International Conference on Software Engineering},
	series = {ICSE {\textquoteright}02},
	year = {2002},
	pages = {177{\textendash}184},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The success of several Open Source{\texttrademark} software systems, e.g., Apache, Bind, Emacs, and Linux, has recently sparked interest in studying and emulating the software engineering principles underlying this innovative development and use model. Certain aspects of the Open Source development method, e.g., community building, open discussions for requirements and features, and evolvable and modular designs are having fundamental and far reaching consequences on general software engineering practices.To leverage such Open Source methods and tools, we have defined an innovative software engineering paradigm for large corporations: Progressive Open Source (POS). POS leverages the power of Open Source methods and tools for large corporations in a progressive manner: starting from completely within the corporation, to include partner businesses, and eventually complete Open Source. In this paper we present the design goals and principles for POS. We illustrate POS with two programs in HP: Corporate Source and the Collaborative Development Program (CDP). We present early results from both these programs suggesting the power and necessity of POS for all modern large corporations.},
	keywords = {companies},
	isbn = {1-58113-472-X},
	doi = {10.1145/581339.581363},
	url = {http://doi.acm.org/10.1145/581339.581363},
	author = {Dinkelacker, Jamie and Garg, Pankaj K. and Miller, Rob and Nelson, Dean}
}
@article {flosswp43,
	title = {Roles and Knowledge Management in Online Technology Communities: An Ethnography Study},
	year = {2002},
	month = {June},
	abstract = {Technical communities are groups who share a common interest in a technology. The literature on technology communities lacks a conceptual understanding of the roles of various players in the online community. An understanding of the different roles the members of the community and the impact of the roles on knowledge management is crucial to manage and sustain such online technical communities. This study based on an ethnographic analysis of two technical communities identifies seven distinct roles. The impact of each of the role on knowledge management activities is discussed.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/madanmohan2.pdf},
	author = {T.R. Madanmohan}
}
@article {flosswp144,
	title = {TOOL: The Open Opinion Layer},
	year = {2002},
	month = {July},
	abstract = {Shared opinions drive society: what we read, how we vote, and where we shop are all heavily influenced by the choices of others. However, the cost in time and money to systematically share opinions remains high, while the actual performance history of opinion generators is often not tracked. This article explores the development of a distributed open opinion layer, which is given the generic name of TOOL. Similar to the evolution of network protocols as an underlying layer for many computational tasks, we suggest that TOOL has the potential to become a common substrate upon which many scientific, commercial, and social activities will be based.},
	author = {Hasan Masum}
}
@article {121,
	title = {Two case studies of open source software development: Apache and Mozilla},
	journal = {ACM Transactions on Software Engineering and Methodology},
	volume = {11},
	number = {3},
	year = {2002},
	note = {apache data sources:
email, cvs, bug database 
regarding email: "We wrote Perl scripts to extract date, sender identity, message subject, and the message body that was further processed to obtain details on code changes and problem reports (see below). Manual inspection was used to resolve such things as multiple email addresses in cases where all automated techniques failed."
(but the rest of the paper does not address this data source at all)

mozilla data sources
bugzilla, cvs

},
	pages = {309-346},
	abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. In order to begin investigating such claims, we examine data from two major open source projects, the Apache web server and the Mozilla browser. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution intervals for these OSS projects. We develop several hypotheses by comparing the Apache project with several commercial projects. We then test and refine several of these hypotheses, based on an analysis of Mozilla data. We conclude with thoughts about the prospects for high- performance commercial/ open source process hybrids.},
	keywords = {apache, bug fixing, bug reports, bugzilla, change history, core, defect density, email, email archives, mailing list, mozilla, ownership, participation, productivity, scm, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mockusFieldingHerbsleb2002.pdf},
	author = {Audris Mockus and Roy Fielding and Herbsleb, J. D.}
}
@conference {Madey02understandingoss,
	title = {Understanding oss as a self-organizing process},
	booktitle = {In The 2nd Workshop on Open Source Software Engineering at the 24th International Conference on Software Engineering (ICSE2002},
	year = {2002},
	abstract = {We hypothesize that open source software development can be modeled as self-organizing, collaboration, social networks. We analyze structural data on over 39,000 open source projects hosted at SourceForge.net. We define two software developers to be connected {\textemdash} part of a collaboration social network {\textemdash} if they are members of the same project, or are connected by a chain of connected developers. Project sizes, developer project participation, and clusters of connected developers are analyzed. We find evidence to support our hypothesis, primarily in the presence of power-law relationships on project sizes (number of developers per project), project membership (number of projects joined by a developer), and cluster sizes.},
	keywords = {developers, size, social network analysis, social networks, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MadeyFreehTynan.pdf},
	author = {Madey, G. and Freeh, V and Tynan, R}
}
@conference {1158,
	title = {Where Do Open Source Requirements Come From (And What Should We Do About It)?},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {The collection and specification of software requirements is one of the most intense areas of software engineering research. This makes it a natural area to explore when considering open-source software. In this paper, I argue that the sources of open-source software requirements differ in some important respects from the sources of commercial software project requirements. This has some interesting implications for both open-source and commercial development.},
	keywords = {requirements},
	attachments = {https://flosshub.org/sites/flosshub.org/files/massey.pdf},
	author = {Bart Massey}
}
@conference {1159,
	title = {Why Not Improve Coordination in Distributed Software Development by Stealing Good Ideas from Open Source?},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	keywords = {apache, communication, coordination, distributed},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MockusHerbsleb.pdf},
	author = {Audris Mockus and Herbsleb, James}
}
@article {flosswp46,
	title = {Innovating without Money: Linux and the Open Source Paradigm as an Alternative to Commercial Software Development},
	year = {2001},
	month = {August},
	abstract = {This dissertation analyses two different paradigms used for the development of a operating systems by Microsoft Corporation and the Linux Community. Through the observation of the strategies and methodologies used by these actors in their work, and taking into account the constraints to which they are subject, assesses, from a dynamic perspective, the relative strengths and weaknesses of their competing paradigms. A theoretical model based on Giovanni Dosi?s "Technological Paradigms" framework, incorporating institutional, industrial, social and cultural aspects, is constructed and specifically adapted to the software industry case. The private management of technology issues considered during the analysis of the development processes inside different organisations are linked to questions having to do with the evolution of high technology, networked, markets.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mateos.pdf},
	author = {Mateos Garcia, Juan}
}
@unpublished {flosswp147,
	title = {Opening The Code: Software Excellence As A Function Of Its Development Environment},
	year = {2001},
	month = {January},
	abstract = {Software is an increasingly important component of the modern world; indeed, software forms the architecture around which today?s digital society is built. Because of the complex interrelationship between computer code, liberty, and the distribution of power in society, the environment in which code is produced makes a tremendous difference in the resulting structure of the world. An "Open" foundation for software development provides a variety of economic and societal benefits, but there are a number of preconditions necessary for its full deployment. One of the primary stumbling blocks is the need for the Open development process to demonstrate its capacity for producing "excellent" software. This thesis tackles that obstacle by first defining excellence in software, and then examining the software ecosystems that surround proprietary and Open Source conceptions of digital property in terms of their incentive structures{\textendash}incentives that either encourage or discourage quality. Herein, this thesis demonstrates that not only can an Open Source development model produce quality software, but it also takes advantage of the complex adaptive systems model of diversity and adaptation to better meet the established criteria of an "ideal" software development system.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mclaughlin.pdf},
	author = {David McLaughlin}
}
@conference {1145,
	title = {Reputation Layers for Open-Source Development},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	keywords = {currency, developers, MOTIVATION, reputation},
	attachments = {https://flosshub.org/sites/flosshub.org/files/masum.pdf},
	author = {Hasan Masum}
}
@article {flosswp26,
	title = {A Case Study of Open Source Software Development: The Apache Server},
	journal = {Proceedings of the International Conference on Software Engineering (ICSE 2000)},
	year = {2000},
	note = {We used the following archival sources of data:
Developer email list (EMAIL).
Concurrent Version Control archive (CVS).
Problem reporting database (BUGDB).},
	month = {June},
	abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. We examine the development process of a major open source application, the Apache web server. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution interval for this OSS project. This analysis reveals a unique process, which performs well on important measures.},
	keywords = {apache, bug fix revisions, bugs, core, cvs, defect density, developers, email archives, participation, productivity, revision control, revision history, roles, scm, source code, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mockusapache.pdf},
	author = {Audris Mockus and Roy Fielding and Herbsleb, James}
}
@article {flosswp11,
	title = {Essence of Distributed Work: The Case of the Linux Kernel},
	year = {2000},
	month = {November},
	abstract = {This paper provides a historical account of how the Linux operating system kernel was developed from three different perspectives. Each focuses on different critical factors in its success at the individual, group, and community levels. The paper concludes by summarizing the factors important in the successful distributed development of the Linux kernel, and the implications for organizationally managed distributed work arrangements.},
	author = {JY Moon}
}
