@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 {1905,
	title = {Longitudinal Analysis of the Run-up to a Decision to Break-up (Fork) in a Community},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {204-217},
	publisher = {Springer},
	abstract = {In this paper, we use a developer-oriented statistical approach to understand what causes people in complex software development networks to decide to fork (break away), and what changes a community goes through in the run-up to a decision to break-up. Developing complex software systems is complex. Software developers interact. They may have the same or different goals, communication styles, or values. Interactions can be healthy or troubled. Troubled interactions cause troubled communities, that face failure. Some of these failures manifest themselves as a community split (known as forking). These failures affects many people; developers and users. Can we save troubled projects? We statistically model the longitudinal socio-grams of software developers and present early indicators and warning signs that can be used to predict an imminent break-up decision.

},
	keywords = {community of software developers, forks, longitudinal study},
	doi = {10.1007/978-3-319-57735-7_19},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_19},
	author = {Amirhosein {\textquotedblleft}Emerson{\textquotedblright} Azarbakht and Jensen, Carlos}
}
@proceedings {1827,
	title = {A Large-Scale Study on Repetitiveness, Containment, and Composability of Routines in Open-Source Projects},
	year = {2016},
	month = {05/2016},
	pages = {362-373},
	abstract = {Source code in software systems has been shown to have a good
degree of repetitiveness at the lexical, syntactical, and API usage
levels. This paper presents a large-scale study on the repetitiveness,
containment, and composability of source code at the semantic level.
We collected a large dataset consisting of 9,224 Java projects with
2.79M class files, 17.54M methods with 187M SLOCs. For each
method in a project, we build the program dependency graph (PDG)
to represent a routine, and compare PDGs with one another as well
as the subgraphs within them. We found that within a project, 12.1\%
of the routines are repeated, and most of them repeat from 2{\textendash}7 times.
As entirety, the routines are quite project-specific with only 3.3\% of
them exactly repeating in 1{\textendash}4 other projects with at most 8 times.
We also found that 26.1\% and 7.27\% of the routines are contained
in other routine(s), i.e., implemented as part of other routine(s) elsewhere
within a project and in other projects, respectively. Except for
trivial routines, their repetitiveness and containment is independent
of their complexity. Defining a subroutine via a per-variable slicing
subgraph in a PDG, we found that 14.3\% of all routines have all
of their subroutines repeated. A high percentage of subroutines in
a routine can be found/reused elsewhere. We collected 8,764,971
unique subroutines (with 323,564 unique JDK subroutines) as basic
units for code searching/synthesis. We also provide practical
implications of our findings to automated tools.},
	doi = {http://dx.doi.org/10.1145/2901739.2901759},
	author = {Nguyen, Anh Duc and Nguyen, Hoan Anh and Nguyen, Tien N.}
}
@article {966,
	title = {License Compliance in Open Source Cybersecurity Projects},
	journal = {Technology Innovation Management Review},
	volume = {6},
	year = {2016},
	month = {02/2016},
	pages = {28-35},
	publisher = {Talent First Network},
	address = {Ottawa},
	abstract = {Developers of cybersecurity software often include and rely upon open source software packages in their commercial software products. Before open source code is absorbed into a proprietary product, developers must check the package license to see if the project is permissively licensed, thereby allowing for commercial-friendly inheritance and redistribution. However, there is a risk that the open source package license could be inaccurate due to being silently contaminated with restrictively licensed open source code that may prohibit the sale or confidentiality of commercial derivative work. Contamination of commercial products could lead to expensive remediation costs, damage to the company{\textquoteright}s reputation, and costly legal fees. In this article, we report on our preliminary analysis of more than 200 open source cybersecurity projects to identify the most frequently used license types and languages and to look for evidence of permissively licensed open source projects that are likely contaminated by restrictive licensed material (i.e., containing commercial-unfriendly code). Our analysis identified restrictive license contamination cases occurring in permissively licensed open source projects. Furthermore, we found a high proportion of code that lacked copyright attribution. We expect that the results of this study will: i) provide managers and developers with an understanding of how contamination can occur, ii) provide open source communities with an understanding on how they can better protect their intellectual property by including licenses and copyright information in their code, and ii) provide entrepreneurs with an understanding of the open source cybersecurity domain in terms of licensing and contamination and how they affect decisions about cybersecurity software architectures.},
	issn = {1927-0321},
	author = {Ahmed Shah and Selman Selman and Ibrahim Abualhaol}
}
@article {1847,
	title = {License usage and changes: a large-scale study on gitHub},
	journal = {Empirical Software Engineering},
	year = {2016},
	abstract = {Open source software licenses determine, from a legal point of view, under which conditions software can be integrated and redistributed. The reason why developers of a project adopt (or change) a license may depend on various factors, e.g., the need for ensuring compatibility with certain third-party components, the perspective towards redistribution or commercialization of the software, or the need for protecting against somebody else{\textquoteright}s commercial usage of the software. This paper reports a large empirical study aimed at quantitatively and qualitatively investigating when and why developers adopt or change software licenses. Specifically, we first identify license changes in 1,731,828 commits, representing the entire history of 16,221 Java projects hosted on GitHub. Then, to understand the rationale of license changes, we perform a qualitative analysis on 1,160 projects written in seven different programming languages, namely C, C++, C$\#$, Java, Javascript, Python, and Ruby{\textemdash}following an open coding approach inspired by grounded theory{\textemdash}on commit messages and issue tracker discussions concerning licensing topics, and whenever possible, try to build traceability links between discussions and changes. On one hand, our results highlight how, in different contexts, license adoption or changes can be triggered by various reasons. On the other hand, the results also highlight a lack of traceability of when and why licensing changes are made. This can be a major concern, because a change in the license of a system can negatively impact those that reuse it. In conclusion, results of the study trigger the need for better tool support in guiding developers in choosing/changing licenses and in keeping track of the rationale of license changes.},
	issn = {1573-7616},
	doi = {10.1007/s10664-016-9438-4},
	author = {Vendome, Christopher and Bavota, Gabriele and Di Penta, Massimiliano and Linares-V{\'a}squez, Mario and German, Daniel and Poshyvanyk, Denys}
}
@proceedings {1729,
	title = {A Large Scale Study of License Usage on GitHub},
	volume = {2},
	year = {2015},
	note = {14.9\% of projects have a license file.},
	month = {05/2015},
	pages = {772-774},
	publisher = {ACM/IEEE},
	abstract = {The open source community relies upon licensing
in order to govern the distribution, modification, and reuse of
existing code. These licenses evolve to better suit the requirements
of the development communities and to cope with unaddressed
or new legal issues. In this paper, we report the results of a large
empirical study conducted over the change history of 16,221 open
source Java projects mined from GitHub. Our study investigates
how licensing usage and adoption changes over a period of ten
years. We consider both the distribution of license usage within
projects of a rapidly growing forge and the extent that new
versions of licenses are introduced in these projects.},
	keywords = {github, license},
	author = {Vendome, Christopher}
}
@booklet {1781,
	title = {Lessons Learned from Applying Social Network Analysis on an Industrial Free/Libre/Open Source Software Ecosystem},
	year = {2015},
	abstract = {Many software projects are no longer done in-house by a single organization. Instead, we are in a new age where software is developed by a networked community of individuals and organizations, which base their relations to each other on mutual interest. Paradoxically, recent research suggests that software development can actually be jointly-developed by rival firms. For instance, it is known that the mobile-device makers Apple and Samsung kept collaborating in open source projects while running expensive patent wars in the court. Taking a case study approach, we explore how rival firms collaborate in the open source arena by employing a multi-method approach that combines qualitative analysis of archival data (QA) with mining software repositories (MSR) and Social Network Analysis (SNA). While exploring collaborative processes within the OpenStack ecosystem, our research contributes to Software Engineering research by exploring the role of groups, sub-communities and business models within a high-networked open source ecosystem. Surprising results point out that competition for the same revenue model (i.e., operating conflicting business models) does not necessary affect collaboration within the ecosystem. Moreover, while detecting the different sub-communities of the OpenStack community, we found out that the expected social tendency of developers to work with developers from same firm (i.e., homophony) did not hold within the OpenStack ecosystem. Furthermore, while addressing a novel, complex and unexplored open source case, this research also contributes to the management literature in coopetition strategy and high-tech entrepreneurship with a rich description on how heterogeneous actors within a high-networked ecosystem (involving individuals, startups, established firms and public organizations) joint-develop a complex infrastructure for big-data in the open source arena.},
	keywords = {business models, cloud computing, homophily, open source, Open-Coopetition, openstack, social network analysis, Software ecosystems},
	url = {http://arxiv.org/abs/1507.04587},
	author = {Teixeira, Jose and Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@inbook {1612,
	title = {A Layered Approach to Managing Risks in OSS Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {168-171},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

In this paper, we propose a layered approach to managing risks in OSS projects. We define three layers: the first one for defining risk drivers by collecting and summarising available data from different data sources, including human-provided contextual information; the second layer, for converting these risk drivers into risk indicators; the third layer for assessing how these indicators impact the business of the adopting organisation. The contributions are: 1) the complexity of gathering data is isolated in one layer using appropriate techniques, 2) the context needed to interpret this data is provided by expert involvement evaluating risk scenarios and answering questionnaires in a second layer, 3) a pattern-based approach and risk reasoning techniques to link risks to business goals is proposed in the third layer.
},
	keywords = {Layered Model, open source, OSS, Risk Management},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_23},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_23},
	author = {Franch, Xavier and Kenett, Ron and Mancinelli, Fabio and Susi, Angelo and Ameller, David and Ben-Jacob, Ron and Siena, Alberto},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Gousios:2014:LGG:2597073.2597126,
	title = {Lean GHTorrent: GitHub Data on Demand},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {384{\textendash}387},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In recent years, GitHub has become the largest code host in the world, with more than 5M developers collaborating across 10M repositories. Numerous popular open source projects (such as Ruby on Rails, Homebrew, Bootstrap, Django or jQuery) have chosen GitHub as their host and have migrated their code base to it. GitHub offers a tremendous research potential. For instance, it is a flagship for current open source development, a place for developers to showcase their expertise to peers or potential recruiters, and the platform where social coding features or pull requests emerged. However, GitHub data is, to date, largely underexplored. To facilitate studies of GitHub, we have created GHTorrent, a scalable, queriable, offline mirror of the data offered through the GitHub REST API. In this paper we present a novel feature of GHTorrent designed to offer customisable data dumps on demand. The new GHTorrent data-on-demand service offers users the possibility to request via a web form up-to-date GHTorrent data dumps for any collection of GitHub repositories. We hope that by offering customisable GHTorrent data dumps we will not only lower the "barrier for entry" even further for researchers interested in mining GitHub data (thus encourage researchers to intensify their mining efforts), but also enhance the replicability of GitHub studies (since a snapshot of the data on which the results were obtained can now easily accompany each study).
},
	keywords = {data on demand, dataset, github, msr data showcase},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597126},
	url = {http://doi.acm.org/10.1145/2597073.2597126},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lean-ghtorrent_0.pdf},
	author = {Gousios, Georgios and Vasilescu, Bogdan and Serebrenik, Alexander and Zaidman, Andy}
}
@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 {1783,
	title = {Linchpin Developers in Open Source Software Projects},
	booktitle = {Artificial Intelligence and Applications},
	year = {2013},
	note = {"The datasources used have been FLOSSmole[5], providing statistical data about each  project.   From  this  repository  we  extracted  the  role assumed by the developers, and domains of participation. "

"We compared our dataset, mined from the FLOSSmole repository [5], based on Sourceforge data, with the one given in [9]. "},
	publisher = {ACTAPRESS},
	organization = {ACTAPRESS},
	address = {Innsbruck, AustriaCalgary,AB,Canada},
	abstract = {In Open Source Software (OSS) development, the so-called linchpin developers are those that contribute contemporaneously to several projects, contributing to keeping the community tied together. While such developers have been identified in previous research, their importance within the OSS community has not been widely discussed. The main objective of this work is to analyze their {\textquotedblleft}weaving{\textquotedblright} role across projects. With this aim, we mined software repositories, using text mining techniques as log-likehood ratio and co-word analysis, further building social networks of developers within emerging communities. The findings show that linchpin developers generally attach in a preferential way to projects in a single specific domain. They tend to be more {\textquotedblleft}project managers{\textquotedblright}, and {\textquotedblleft}all-hands-persons{\textquotedblright}, meaning that they bring multi-disciplinary experience across projects. They tend to cover the same role across projects. They generally have high centrality in their projects, and contribute to create projects that ease the transition from a fragmented projects community to a more core-periphery community.
},
	keywords = {flossmole},
	doi = {10.2316/P.2013.796-018},
	url = {https://www.researchgate.net/publication/266632252_Linchpin_Developers_in_Open_Source_Software_Projects},
	author = {Corona, Erika Ingrid Mastranzo and Rossi, Bruno}
}
@proceedings {1500,
	title = {Linux Variability Anomalies: What Causes Them and How Do They Get Fixed?},
	year = {2013},
	month = {05/2013},
	abstract = {The Linux kernel is one of the largest configurable open source software systems implementing static variability. In Linux, variability is scattered over three different artifacts: source code files, Kconfig files, and Makefiles. Previous work detected inconsistencies between these artifacts that led to anomalies in the intended variability of Linux. We call these variability anomalies. However, there has been no work done to analyze how these variability anomalies are introduced in the first place, and how they get fixed. In this work, we provide an analysis of the causes and fixes of variability anomalies in Linux. We first perform an exploratory case study that uses an existing set of patches which solve variability anomalies to identify patterns for their causes. The observations we make from this dataset allow us to develop four research questions which we then answer in a confirmatory case study on the scope of the whole Linux kernel. We show that variability anomalies exist for several releases in the kernel before they get fixed, and that contrary to our initial suspicion, typos in feature names do not commonly cause these anomalies. Our results show that variability anomalies are often introduced through incomplete patches that change Kconfig definitions without properly propagating these changes to the rest of the system. Anomalies are then commonly fixed through changes to the code rather than to Kconfig files.},
	author = {Sarah Nadi and Christian Dietrich and Reinhard Tartler and Holt, Richard C. and Daniel Lohmann}
}
@conference {Alspaugh:2012:LS:2419620.2419854,
	title = {Licensing Security},
	booktitle = {Proceedings of the 2012 Fifth International Workshop on Requirements Engineering and Law (RELAW)},
	series = {RELAW {\textquoteright}12},
	year = {2012},
	pages = {25{\textendash}28},
	publisher = {IEEE Computer Society},
	organization = {IEEE Computer Society},
	address = {Washington, DC, USA},
	abstract = {There exist legal structures defining the exclusive rights of authors, and means for licensing portions of them to others in exchange for appropriate obligations. We propose an analogous approach for security, in which portions of exclusive security rights owned by system stakeholders may be licensed as needed to others, in exchange for appropriate security obligations. Copyright defines exclusive rights to reproduce, distribute, and produce derivative works, among others. We envision exclusive security rights that might include the right to access a system, the right to run specific programs, and the right to update specific programs or data, among others. Such an approach uses the existing legal structures of licenses and contracts to manage security, as copyright licenses are used to manage copyrights. At present there is no law of {\textquotedblleft}security right{\textquotedblright} as there is a law of copyright, but with the increasing prevalence and prominence of security attacks and abuses, of which Stuxnet and Flame are merely the best known recent examples, such legislation is not implausible. We discuss kinds of security rights and obligations that might produce fruitful results, and how a license structure and approach might prove more effective than security policies.},
	isbn = {978-1-4673-4380-0},
	doi = {10.1109/RELAW.2012.6347799},
	url = {http://dx.doi.org/10.1109/RELAW.2012.6347799},
	author = {Alspaugh, Thomas A. and Walt Scacchi}
}
@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 {1441,
	title = {Long-Term Sustainability of Open Source Software Communities beyond a Fork: A Case Study of LibreOffice},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {29-47},
	publisher = {IFIP AICT},
	abstract = {Many organisations have requirements for long-term sustainable software systems and associated communities. In this paper we consider long-term sustainability of Open Source software communities in Open Source projects involving a fork. There is currently a lack of studies in the literature that address how specific Open Source software communities are affected by a fork. We report from a case study aiming to investigate the developer community around the LibreOffice project, which is a fork from the OpenOffice.org project. The results strongly suggest a long-term sustainable community and that there are no signs of stagnation in the project 15 months after the fork. Our analysis provides details on the LibreOffice developer community and how it has evolved from the OpenOffice.org community with respect to project activity, long-term involvement of committers, and organisational influence over time. The findings from our analysis of the LibreOffice project make an important contribution towards a deeper understanding of challenges regarding long-term sustainability of Open Source software communities.},
	author = {Gamalielsson, Jonas and Lundell, Bj{\"o}rn}
}
@proceedings {1284,
	title = {Libre Software as an Innovation Enabler in India: Experiences of a Bangalorian Software SME},
	year = {2011},
	month = {10/2011},
	pages = {220-232},
	publisher = {Springer},
	abstract = {Free/Libre and open source software (FLOSS) has been advocated for its presumed capacity to support native software industries in developing countries. It is said to create new spaces for exploration and to lower entry barriers to mature software markets, for example. However, little empirical research has been conducted concerning FLOSS business in a developing country setting and, thus, there is not much evidence to support or refute these claims. This paper presents a business case study conducted in India, a country branded as a {\textquoteright}software powerhouse{\textquoteright} of the developing world. The findings show how FLOSS has opened up significant opportunities for the case company, especially in terms of improving its innovative capability and upgrading in the software value chain. On the other hand, they also highlight some challenges to FLOSS involvement that rise specifically from the Indian context.},
	keywords = {free software, India, INNOVATION, open source, software business},
	author = {Henttonen, Katja}
}
@proceedings {1281,
	title = {License Update and Migration Processes in Open Source Software Projects},
	year = {2011},
	note = {"The case studies in this report are part of an ongoing, multi-year research project discovering and modeling open source software processes. Our research methodology is ethnographically informed, applying a grounded theory to the analysis of artifacts found in OSS projects. The primary data sources in this study come from mailing list archives of the Apache and NetBeans projects."},
	month = {10/2011},
	pages = {177-195},
	publisher = {Springer},
	abstract = {Open source software (OSS) has increasingly been the subject of research efforts. Central to this focus is the nature under which the software can be distributed, used, and modified and the causes and consequent effects on software development, usage, and distribution. At present, we have little understanding of, what happens when these licenses change, what motivates such changes, and how new licenses are created, updated, and deployed. Similarly, little attention has been paid to the agreements under which contributions are made to OSS projects and the impacts of changes to these agreements. We might also ask these same questions regarding the licenses governing how individuals and groups contribute to OSS projects. This paper focuses on addressing these questions with case studies of processes by which the Apache Software Foundation{\textquoteright}s creation and migration to Version 2.0 of the Apache Software License and the NetBeans project{\textquoteright}s migration to the Joint Licensing Agreement.},
	keywords = {apache, case study, email, email archive, license evolution, mailing list, netbeans, open source, process},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1.pdf},
	author = {Chris Jensen and Walt Scacchi}
}
@proceedings {1379,
	title = {Learning in Open Source Software (OSS) Development: How Developer Interactions in Culturally Diverse Projects Impact the Acquisition of Collaboration and Learning Skills},
	year = {2010},
	abstract = {Participants in an OSS/FLOSS development project often span national and organizational boundaries, as developers from different countries and corporations join the project. A project team{\textquoteright}s national and organizational culture creates opportunities for learning from others, but may also lead to conflict and inhibit learning. This research examines developers{\textquoteright} learning in an OSS project, and the cultural context in which learning takes place. We focus on single- and doubleloop learning and examine the impact of the team{\textquoteright}s national and organizational culture on a developer{\textquoteright}s learning. Archival and survey data are collected from two large-scale Sourceforge projects. This research can contribute to the OSS literature by examining the impact of team interactions on developers{\textquoteright} learning. Practically, administrators and managers stand to gain insight into the learning benefits of participation in OSS projects, and thus better assess their value as a training ground for global software development.},
	keywords = {sourceforge},
	url = {http://aisel.aisnet.org/icis2010_submissions/66/},
	author = {Diamant, I. and Daniel, S.L.}
}
@conference {1255,
	title = {{\textquoteright}Letting go of Control{\textquoteright} to Embrace Open Source: Implications for Company and Community},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)},
	year = {2010},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {It is increasingly understood across the information technology and services sector that engagement with the open source software model can serve as a means for firms to capture intellectual energy, learn about productive software processes, access relevant technical skills, identify and recruit staff, as well as obtain valuable resources including code. This paper reports a study undertaken within two large global IT companies that have been actively involved with open source for more than ten years. The study involved over 30 semi-structured interviews with employees of the companies drawn from top, middle, and lower level management, and included active and experienced developer as well as open source community members. Our findings indicate how these companies have adapted their day-to-day management practices to take into account the need for flexibility and freedom expected by open source communities. This paper focuses on how they {\textquoteright}let go of control{\textquoteright} and what the implications of this are for both companies and the communities involved. Our data reveals a number of themes and in this paper we focus on three principal ones; issues of requirements, total cost of adoption, and alignment of open source engagement with long term company strategy.},
	keywords = {adoption, companies, interviews, organizations},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-06-01.pdf},
	author = {Maha Shaikh and Cornford, Tony}
}
@conference {1359,
	title = {Linking e-mails and source code artifacts},
	booktitle = {Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - ICSE {\textquoteright}10},
	volume = {1},
	year = {2010},
	note = {"we devised a set of lightweight methods, based on regular expressions, to establish the link between e-mails and software artifacts. We evaluated them in terms of precision and recall considering one single Java system. In this paper we overcome a number of limitations of our previous work, resulting in the following contributions:
{\textbullet} An extensive and publicly available1 benchmark and toolset for recovering traceability links between e-mails and source code artifacts. We created our benchmark by analyzing the mailing lists of six different software systems written in four different programming languages. For each system we manually annotated a statistically significant number of e-mails.
{\textbullet} A comprehensive evaluation of linking techniques. We evaluated and compared, in terms of precision and recall, different linking methods, ranging from lightweight grep-style approaches to more complex approa- ches from the information retrieval (IR) field."},
	month = {05/2010},
	pages = {375-384},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Cape Town, South Africa},
	abstract = {E-mails concerning the development issues of a system constitute an important source of information about high-level design decisions, low-level implementation concerns, and the social structure of developers.

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

In this article we present such a benchmark, which we created through the manual inspection of a statistically significant number of e-mails pertaining to six unrelated software systems. We then use our benchmark to measure the effectiveness of a number of approaches, ranging from lightweight approaches based on regular expressions to full-fledged information retrieval approaches.},
	isbn = {9781605587196},
	doi = {10.1145/1806799.1806855},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	author = {Bacchelli, Alberto and Lanza, Michele and Robbes, Romain}
}
@conference {bird2010lee,
	title = {{Linkster: Enabling Efficient Manual Mining}},
	booktitle = {Demonstration Track, Proceedings of the 17th SIGSOFT Symposium on Foundations of Software Engineering},
	year = {2010},
	note = {"LINKSTER efficiently displays, integrates, and allows inspection and annotation of information from three main sources of data: source code repositories, developer mailing lists archives, and bug tracking databases. LINKSTER requires access to a source code repository for file content and a database which contains the raw mined repository, mailing list, and bug tracking information. All notes and annotations made by the user are also recorded in the database."},
	publisher = {ACM},
	organization = {ACM},
	abstract = {While many uses of mined software engineering data are automatic in nature, some techniques and studies either require, or can be improved, by manual methods. Unfortunately, manually inspecting, analyzing, and annotating mined data can be difficult and tedious, especially when information from multiple sources must be integrated. Oddly, while there are numerous tools and frameworks for automatically mining and analyzing data, there is a dearth of tools which facilitate manual methods. To fill this void, we have developed LINKSTER, a tool which integrates data from bug databases, source code repositories, and mailing list archives to allow manual inspection and annotation. LINKSTER has already been used successfully by an OSS project lead to obtain data for one empirical study.},
	keywords = {artifacts, bug, bug tracking, data mining, email, mailing lists, open source, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2010lee.pdf},
	author = {Christian Bird and Adrian Bachman and Rahman, Foyzur and Bernstein, Abraham}
}
@conference {1218,
	title = {A Longitudinal Study on Collaboration Networks and Decision to Participate in a FLOSS Community},
	booktitle = {5th Workshop on Public Data about Software Development (WoPDaSD 2010)},
	year = {2010},
	note = {"we chose as a case of study Epiphany, which is the default web browser of the GNOME graphical desktop environment"

"We collected all relevant data by parsing all the bug reports in GNOME Bugzilla repository relative to Epiphany. The data collection and storing was done using Bicho (v. 0.4 rev. 7198), a software part of the FLOSSMetric project [14]."},
	abstract = {In this paper we conjecture that individual decisions of FLOSS (Free/Libre Open Source Software) developers to take on a task are influenced by network relations generated by collaboration among project members. In order to explore our conjecture we collected data on a FLOSS project team consisting of 227 developers committed since 2002 to the development of a web browser. We reconstructed 2-mode co- collaboration networks (software developer by bug) in which a tie represents an action taken by a developer in order to solve a specific bug. Co-collaboration networks were collected at five points in time during a six-month development cycle of the software. We report and discuss results of longitudinal actor-based modeling that we specify to test for the influence of local network structures on developer{\textquoteright}s decision to take action on a specific bug. The study controls for bug-specific and developer-specific characteristics that may also affect developers{\textquoteright} decisions exogenously. We also control for priority and severity levels assigned by the team to bugs in an attempt to manage voluntary contribution.},
	keywords = {bicho, bug fixing, bug reports, bugzilla, COLLABORATION, developers, epiphany, flossmetrics, gnome, social network analysis},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd002.pdf},
	author = {Guido Conaldi and Tonellato, Marco}
}
@conference {837,
	title = {Lurking? Cyclopaths? A Quantitative Lifecyle Analysis of User Behavior in a Geowiki},
	booktitle = {ACM Conference on Computer-Human Interaction (CHI)},
	year = {2010},
	month = {04/2010},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Atlanta, GA},
	keywords = {content,, geographic, geowiki,, information,, lurking, open, volunteer, volunteered, Wiki,, work,},
	author = {Panciera, K. and Priedhorsky, R. and Erickson, T. and Terveen, L.}
}
@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 {944,
	title = {Learning from defect removals},
	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 = {179 - 182},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Recent research has tried to identify changes in source code repositories that fix bugs by linking these changes to reports in issue tracking systems. These changes have been traced back to the point in time when they were previously modified as a way of identifying bug introducing changes. But we observe that not all changes linked to bug tracking systems are fixing bugs; some are enhancing the code. Furthermore, not all fixes are applied at the point in the code where the bug was originally introduced. We flesh out these observations with a manual review of several software projects, and use this opportunity to see how many defects are in the scope of static analysis tools.},
	keywords = {bug fixing, bugzilla, change management, cherry, cvs, eclipse, groovy, launching, source code, svn, text editor},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069500},
	attachments = {https://flosshub.org/sites/flosshub.org/files/179LearnFromDefects-MSR09.pdf},
	author = {Ayewah, Nathaniel and Pugh, William}
}
@conference {842,
	title = {Learning to Recognize Valuable Tags},
	booktitle = {International Conference on Intelligent User Interfaces},
	year = {2009},
	month = {2/8/2009},
	publisher = {ACM},
	organization = {ACM},
	address = {Sanibel Island, FL},
	author = {Sen, S. and Vig, J. and Riedl, J.}
}
@conference {608,
	title = {Libre Software in Spanish Public Administrations},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {366 - 366},
	publisher = {Springer},
	organization = {Springer},
	chapter = {40},
	abstract = {Libre software started to be used in Public Administrations in Spain during the 1990s, in some isolated but interesting experiences.During the early 2000s, and specially in some regional governments, libre software started to be considered as an integral part of ITrelated policies. In 2007, it was evident that many experiences related to libre software were running in Public Administrations with different levels of success. However, no study had looked into the details of these experiences, and no comprehensive analysis had been performed to better understand the different factors that affect them.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_40},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Libre\%20Software.pdf},
	author = {Ortega, Felipe and Lafuente, Isabel and Gato, Jose and Gonz{\'a}lez-Barahona, Jes{\'u}s}
}
@proceedings {72,
	title = {A large-scale study of MySpace: Observations and implications for online social networks},
	year = {2008},
	month = {March 30{\textendash}April 2},
	address = {Seattle, WA},
	author = {James Caverle and Steve Webb}
}
@conference {bird2008lss,
	title = {{Latent Social Structure in Open Source Projects}},
	booktitle = {SIGSOFT {\textquoteright}08/FSE-16: Proceedings of the 16th ACM SIGSOFT Symposium on Foundations of Software Engineering},
	year = {2008},
	note = {We first identified the projects of interest and mined the developer mailing list archives and source code repositories of each of the projects. Next, we filtered the mailing list messages and created a social network of the participants over 3-month intervals. We then calculated the community structure of each social network. Following that, the relevance of the divisions of participants was evaluated quantitatively using mined source code development data and qualitatively by manual methods.},
	pages = {24{\textendash}35},
	publisher = {ACM},
	organization = {ACM},
	abstract = {Commercial software project managers design project organizational structure carefully, mindful of available skills, division of labour, geographical boundaries, etc. These organizational {\textquotedblleft}cathedrals{\textquotedblright} are to be contrasted with the "bazaar-like" nature of Open Source Software (OSS) Projects, which have no pre-designed organizational structure. Any structure that exists is dynamic, self-organizing, latent, and usually not explicitly stated. Still, in large, complex, successful, OSS projects, we do expect that subcommunities will form spontaneously within the developer teams. Studying these subcommunities, and their behavior can shed light on how successful OSS projects self-organize. This phenomenon could well hold important lessons for how commercial software teams might be organized. Building on known well-established techniques for detecting community structure in complex networks, we extract and study latent subcommunities from the email social network of several projects: Apache HTTPD, Python, PostgresSQL, Perl, and Apache ANT. We then validate them with software development activity history. Our results show that subcommunities do indeed spontaneously arise within these projects as the projects evolve. These subcommunities manifest most strongly in technical discussions, and are significantly connected with collaboration behaviour.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bird2008lss.pdf},
	author = {Christian Bird and David Pattison and Raissa D{\textquoteright}Souza and Filkov, Vladimir and Devanbu, Premkumar}
}
@mastersthesis {484,
	title = {Licensing Freedom; An Ethical Analysis of Free and Open Source Software Licenses},
	year = {2008},
	month = {January},
	abstract = {Free and open source software enables users to use, read and modify the source code of computer programs. In proprietary software, access to the source code is not given and users are generally not permitted to use, read and modify the source code. Opponents of a proprietary system state that proprietary software is morally wrong and in this thesis, the arguments they use are evaluated.Several licensing schemes can be used as an addition to copyright law to give users the rights described above. The most important division between these different licenses can be made on the basis of the use of the copyleft principle. This principle obliges the licensee to distribute modified versions of the software under the same, or similar terms as the original license. In this thesis, this obligation is seen as a restriction on the freedom of the individual. Comparisons and possible justifications will give better insight in this supposed contradiction.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Thesis_SaskiavandeNieuwenhof.pdf},
	author = {Saskia van de Nieuwenhof}
}
@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 {637,
	title = {Learning and the imperative of production in Free/Open Source development},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {235 - 240},
	publisher = {Springer},
	organization = {Springer},
	chapter = {21},
	abstract = {This paper examines the role of learning in structuring access and participation in F/OS communities. In particular it highlights the challenges and barriers to access faced by new developers and the expectations of senior developers regarding the mindsets and capabilities of new contributors. It is argued that learning in F/OS is inextricably connected with the demand for continuous production. The evidence presented is drawn from interviews conducted with inexperienced and experienced contributors from the GNOME and KDE projects. The author challenges the view of learning as an enculturation process and the paper contributes to the understanding of power relations among established and peripheral members in communities of practice.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_21},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Learning\%20and\%20the\%20imprative\%20of\%20production.pdf},
	author = {Evangelia Berdou}
}
@conference {646,
	title = {Learning Through Practical Involvement in the OSS Ecosystem: Experiences from a Masters Assignment},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {289 - 294},
	publisher = {Springer},
	organization = {Springer},
	chapter = {30},
	abstract = {Increased awareness of and interest in Open Source has led to a number of university teaching initiatives, at both national and European level. In this paper we present experiences from a practical assignment designed to give students on an Open Source Masters course an insight into real involvement in Open Source projects. It discusses the motivations for the assignment, and how it was set up and executed. It reports on post facto student feedback, and reflects on a parallel, reduced exercise offered at undergraduate level. We find that the learning experience was both positive and valuable in that it gave real insight into Open Source participation, and also encouraged further participation in Open Source projects by students after the course had completed.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_30},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Learning\%20through\%20practical\%20involvement.pdf},
	author = {Lundell, Bj{\"o}rn and Persson, Anna and Lings, Brian}
}
@conference {657,
	title = {Legal issues for free and open source software in government},
	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 = {353 - 354},
	publisher = {Springer},
	organization = {Springer},
	chapter = {41},
	abstract = {As more governments begin to adopt and release free and open source software, it is important to be able to readily recognise and identify the associated legal risks and potential liabilities. This panel will examine and discuss the most common of these associated risks and liabilities. These issues include, but are not limited to: 

  indemnities against claims of intellectual property  infringement from third parties
  requirements of consumer protection and antitrust legislation
  obligations to redistribute source, and when they arise
  enforceability of free software licences
  layering and combining of licences
  dual-licensing
  licence incompatibility
  software patent liability
  contemporary developments in software licensing
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_41},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Legal\%20Issues\%20for\%20Free\%20and\%20OSS.pdf},
	author = {Nic Suzor and Fitzgerald, Brian and Perry, Mark}
}
@conference {654,
	title = {Levels of Formality in FOSS Communities},
	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 = {337 - 342},
	publisher = {Springer},
	organization = {Springer},
	chapter = {38},
	abstract = {One of the aspects of Free and Open Source Software (FOSS) which may act as a significant deterrent to its adoption, is the method used to collaboratively develop the software and provide support through the use of communities. It is not until this method is examined more closely that its many advantages can be realised. The method can, however, seem very disorganised especially when compared with traditional proprietary development styles. A key difference between these two development approaches lies in the management of projects, and perhaps as a consequence, in the level of formality in the community environment.
This paper presents the results of empirical survey research investigating FOSS community participants{\textquoteright} views on the level of formality in FOSS, and the way in which this affects both development and support provision activities. The paper then concludes by analysing what can be learnt from the participant{\textquoteright}s views.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_38},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Levels\%20of\%20Formality.pdf},
	author = {Schofield, Andrew and Cooper, Grahame}
}
@conference {1018,
	title = {Local and Global Recency Weighting Approach to Bug Prediction},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {33 - 33},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Finding and fixing software bugs is a challenging maintenance task, and a significant amount of effort is invested by software development companies on this issue. In this paper, we use the Eclipse project{\textquoteright}s recorded software bug history to predict occurrence of future bugs. The history contains information on when bugs have been reported and subsequently fixed.},
	keywords = {bug fixing, bug reports, eclipse, maintenance, prediction},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.17},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300033.pdf},
	author = {Joshi, Hemant and Zhang, Chuanlei and Ramaswamy, S. and Bayrak, Coskun}
}
@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}
}
@unpublished {flosswp337,
	title = {Learning and knowledge in FLOSS - Situated learning and organizational knowledge-conversion in community-based free/libre open source software development},
	year = {2006},
	month = {November},
	abstract = {In free/libre open source software development (FLOSS), groups of developers and users working in geographically dispersed settings are supported by a dense network of interactions. The participants are highly skilled in the use of information- and communication technologies, and build the software by relying on extensive peer production and through skillful use of communication tools available on the Internet. In building the software, explicit, formal and structured knowledge in the form of documents, objects, machines and external sources are communicated and stored in ways that make it available for others in the present and future. This knowledge make up an important resource for the members and developers of the community. Another kind, or aspect, of knowledge, often called tacit or soft knowledge, is informal, unstructured, resides in people, and are difficult, or maybe impossible, to articulate. The questions guiding this research is how knowledge, both explicit and tacit, is shared, and how a new member is able take part in the practice and knowledge of the community. The theory of legitimate peripheral participation in communities of practice describes an environment for people to develop knowledge through interaction with others in an environment where knowledge is created, nurtured and sustained. By taking part in the practice as a participant observer, through virtual ethnography, the author describes the practice and communication in this decentralized and knowledge-intensive process. Taking it a step further, the knowledge of the community, and how it is shared within the ???organization???, is explored with a model for managing dynamic aspects of organizational knowledge-creation. The central theme here is that knowledge is created through a continuous dialogue between tacit and explicit knowledge. Logs from Internet Relay Chat (IRC) and interviews with core developers are analyzed, and the author argues that the Plone community is able to share both kinds of knowledge in a complex web of resources and interaction. The analysis further suggest that the FLOSS development-model facilitates access, transparency and participation on premisses that are important for learning.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Learning-and-knowledge-in-FLOSS.pdf},
	author = {Sverre Helge Bolstad}
}
@conference {696,
	title = {Licensing Services: An {\textquotedblleft}Open{\textquotedblright} Perspective},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {143 - 154},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Though service orientation is an incipient technology, the inherently infinite potentiality of services makes them to proliferate seamlessly, serving in myriad domains. Licensing of services enables to regulate the commercial use and modifications of service, retaining the copyright with owner of the service. With the growing influence of open source initiatives today, it becomes a significant topic to analyze {\textquoteleft}open{\textquoteright}ing services. In this paper, we present a concept of {\textquoteleft}open service{\textquoteright} and analyze the implications of open source approach on service licenses.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_14},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Licensing\%20Services\%20\%20An\%20Open\%20Perspective.pdf},
	author = {D{\textquoteright}Andrea, Vincenzo and Gangadharan, G.}
}
@conference {697,
	title = {Life cycle of Defects in Open Source Software Projects},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	note = {"we collected and analyzed defects of the apache http server and mozilla firefox" 
"all the defects reported between X and X were analyzed"},
	pages = {195 - 200},
	publisher = {Springer},
	organization = {Springer},
	abstract = {We studied the maintenance process from the viewpoint of defect management and the defect life cycle. First, we outline a model for the defect life cycle based on ISO/IEC standards, the Framework for Open Source maintenance process, and the Bugzilla defect management system. Thereafter, we analyze defects from two Open Source software projects. The aim of the study was support the maintenance reliability. However, we found that most of the defects did not follow the life-cycle model. Defects were usually directly resolved from initial state without being assigned.
},
	keywords = {apache, defects, Firefox, mozilla},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_19},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Life\%20cycle\%20of\%20Defects\%20in\%20OSS\%20Projects.pdf},
	author = {Koponen, Timo}
}
@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}
}
@article {flosswp200,
	title = {The Launching of Mozilla Firefox - A Case Study in Community-Led Marketing},
	year = {2005},
	month = {January},
	abstract = {Mozilla Firefox is a Free/Libre/Open Source (FLOSS) browser supported by the Mozilla Foundation. This browser was recently released and has met with considerable success- it has been downloaded more than 20 million times and has already taken considerable market share from its prime competitor- Microsoft?s Internet Explorer. In this paper, I chronicle how the efforts of 63000 volunteers led to a community successfully competing with a powerful corporation. I identify four factors as the key facilitators to Firefox? success- complacent competition, product superiority, presence of marketing leader and volunteer support.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/sandeep2.pdf},
	author = {Sandeep Krishnamurthy}
}
@conference {789,
	title = {Legal issues of Open Source Software},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {320-321},
	abstract = {From the legal standpoint, Open Source amounts to distributing rights and obligations in software license agreements in such a way, that they would (1) both grant users control over the program and (2) facilitate the sharing of improvements. The Open Source idea aims at reversing the process usually referred to as proprietary licensing and equaling the rights of the users with these of the authors. To some extent, it attempts to destroy monopolies created by copyright laws and to prevent them to arise again. There is much in the discussion on the legal issues of Open Source. The first voices came from the programmers who started the movement.},
	keywords = {cooperation, copyright law, freedom, intellectual property, legal issue, license, open source software},
	url = {http://pascal.case.unibz.it/handle/2038/974},
	author = {Siewicz, Krzysztof}
}
@conference {Antoniol:2005:LPC:1083142.1083156,
	title = {Linear predictive coding and cepstrum coefficients for mining time variant information from software repositories},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {74-78},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {This paper presents an approach to recover time variant information from software repositories. It is widely accepted that software evolves due to factors such as defect removal, market opportunity or adding new features. Software evolution details are stored in software repositories which often contain the changes history. On the other hand there is a lack of approaches, technologies and methods to efficiently extract and represent time dependent information. Disciplines such as signal and image processing or speech recognition adopt frequency domain representations to mitigate differences of signals evolving in time. Inspired by time-frequency duality, this paper proposes the use of Linear Predictive Coding (LPC) and Cepstrum coefficients to model time varying software artifact histories. LPC or Cepstrum allow obtaining very compact representations with linear complexity. These representations can be used to highlight components and artifacts evolved in the same way or with very similar evolution patterns. To assess the proposed approach we applied LPC and Cepstral analysis to 211 Linux kernel releases (i.e., from 1.0 to 1.3.100), to identify files with very similar size histories. The approach, the preliminary results and the lesson learned are presented in this paper.},
	keywords = {change history, data mining, evolution, files, kernel, linear predictive coding, linux, lpc, size, software evolution, source code},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083156},
	url = {http://doi.acm.org/10.1145/1082983.1083156},
	attachments = {https://flosshub.org/sites/flosshub.org/files/74LinearPredictive.pdf},
	author = {Antoniol, Giuliano and Rollo, Vincenzo Fabio and Venturi, Gabriele}
}
@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}
}
@article {flosswp245,
	title = {Linux vs. Windows: A comparison of application and platform innovation incentives for open source and proprietary software platforms},
	year = {2005},
	month = {October},
	abstract = {The paper analyzes and compares the investment incentives of platform and application developers for Linux and Windows. We find that the level of investment in applications is larger when the operating system is open source rather than proprietary. The comparison of the levels of investment in the operating systems depends, among others, on reputation effects and the number of developers. The paper also develops a short case study comparing Windows and Linux and identifies new directions for open source software research.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/economideskatsamakas.pdf},
	author = {Nicholas Economides and Evangelos Katsamakas}
}
@conference {777,
	title = {Live! I-Learn @ Home},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {294-295},
	abstract = {In this paper we present a live CD based on GNU/Linux (Knoppix), customized in order to supply a complete working and studying environment for the students of the Corso di Studi in Informatica. In particular, it supplies the Moodle course management system for e-learning complete of the courses of the first year. The aim is to enable the use of such resources off-line and without requiring special skills that will be achieved by studying but that newbies do not have.},
	keywords = {e-learning, environment, GNU/Linux, java, open source, technology},
	url = {http://pascal.case.unibz.it/handle/2038/977},
	author = {Baldoni, Matteo and Baroglio, Cristina and Roversi, Luca and Grandi, Claudio}
}
@conference {791,
	title = {Looking at Free and Open Source Software: A Study about F/OSS Developers{\textquoteright} Culture},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {324-325},
	abstract = {My work will be a cultural study of a F/OSS development project, mixing a symmetric approach with the interaction analysis by Erving Goffman. Methodologically I will approach cyber {\textendash} ethnography.},
	keywords = {cultural analysis, cultural study, cyber, F/OSS developers, open source, software development},
	url = {http://pascal.case.unibz.it/handle/2038/968},
	author = {Teli, Maurizio}
}
@conference {1054,
	title = {LASER: a lexical approach to analogy in software reuse},
	booktitle = {International Workshop on Mining Software Repositories (MSR 2004)},
	volume = {2004},
	year = {2004},
	pages = {112 - 116},
	publisher = {IEE},
	organization = {IEE},
	address = {Edinburgh, Scotland, UK},
	abstract = {Software reuse is the process of creating a software system from existing software components, rather than creating it from scratch. With the increase in size and complexity of existing software repositories, the need to provide intelligent support to the programmer becomes more pressing. An analogy is a comparison of certain similarities between things which are otherwise unlike. This concept has shown to be valuable in developing UML-level reuse techniques. In the LASER project we apply lexically-driven Analogy at the code level, rather than at the UML-level, in order to retrieve matching components from a repository of existing components. Using the lexical ontology Word-Net, we have conducted a case study to assess if class and method names in open source applications are used in a semantically meaningful way. Our results demonstrate that both hierarchical reuse and parallel reuse can be enhanced through the use of lexically-driven Analogy.},
	keywords = {class, developers, functions, jrefactory, method, naming, natural language, reuse, source code, wordnet},
	doi = {10.1049/ic:20040487},
	attachments = {https://flosshub.org/sites/flosshub.org/files/112LASER.pdf},
	author = {Amin, R. and Mel O Cinneide and Veale, Tony}
}
@article {flosswp161,
	title = {Legal Issues for the Use of Free and Open Source Software in Government},
	year = {2004},
	month = {January},
	abstract = {This paper examines some of the legal issues that face the uptake of free and open source software in government in Australia. This paper was presented at the {\textquoteright}Linux and Open Source in Government{\textquoteright} conference, part of Linux.Conf.Au 2004 in Adelaide, Australia.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/suzorfitzgeraldbasset.pdf},
	author = {Nic Suzor}
}
@unpublished {flosswp162,
	title = {Linux Adoption by Firms},
	year = {2004},
	month = {May},
	abstract = {The objective of this study is to examine the evolution of the market for Linux based products for the 1993-2003 period. Using data on 317 Linux suppliers available online, the differences in firms? size and in their first products were explored across the adoption stages of the Linux life cycle. Then two temporal patterns of the Linux-market were identified: changes in the entry rate of new Linux suppliers and changes in product diversity. Finally, the attributes of the partnerships formed by four major Linux distributors were examined. The study determined whether the number of partnerships formed by Linux distributors was related to the number of new entrants, whether the motives for partnerships formed by Linux distributors varied over adoption stages, and whether the type of partner selected by Linux distributors was a function of partnership motive. This study builds on the literature on open source software and traditional theories of technology adoption to make three important contributions. First, it develops a method to identify the stages of the life of a new technology. Secondly, it provides a way to measure the temporal patterns of the evolution of a new market. Finally, it validates the densitydependence model using data on open source.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/peng.pdf},
	author = {Zheshi Peng}
}
@book {flosswp160,
	title = {Legal Issues Relating to Free and Open Source Software},
	year = {2003},
	month = {September},
	abstract = {This is the publication that follows the {\textquoteright}Legal Issues Relating to Free and Open Source Software Conference{\textquoteright} that was held in Brisbane, Australia on 3 July 2002. The conference examined legal and business issues facing the development and implementation of free and open source software. The presenters were lawyers, academics and software developers expert in the area drawn from Australia and the USA.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/opensourcelawbook.pdf},
	author = {Fitzgerald, Brian}
}
@article {flosswp101,
	title = {Licensing schemes in the production and distribution of Open Source software. An empirical investigation},
	year = {2003},
	month = {August},
	abstract = {Contrary to what most people assume, Open source doesn{\textquoteright}t just mean access to the source code. A software is considered Open Source if and only if its distribution terms [i.e. the license] comply with the set of criteria defined by the Open Source Definition (OSD). That is, to say that a code is Open Source is to say that it is subject to a member of a particular category of licenses (McGowan, 2000). As many others in the Open Source field, the research on Open Source licenses suffers from lack of empirical data. Although in the literature there are empirical studies that explore the relationships between license choice and project characteristics (Lerner and Tirole, 2002a), at present we are not aware of surveys that collect data on licensors, that is on firms producing and distributing software on an Open Source basis. This study addresses his shortcoming. We examine the license choice of the firms that supply Open Source products and services and relate it to their structural characteristics, business models and attitudes towards the movement and its community. Between September 2002 and March 2003 we conducted a survey on Italian firms that do business with Open Source software. We asked them to indicate the Open Source licenses with which they work, for the distribution of their software as well as the production process. We made reference to the distinction between copyleft and non-copyleft distribution schemes. Using these data, this paper aims at testing several theoretical hypotheses advanced by the literature on Open Source licenses. In order to make the discussion more lively, for each issue we present the hypothesis and our findings in sequence.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bnaccorsirossilicense.pdf},
	author = {Andrea Bonaccorsi}
}
@article {flosswp99,
	title = {The Linux Managing Model},
	year = {2003},
	month = {July},
	abstract = {This study focuses on the distinguishing traits of the Linux managing model. It introduces the concept of process to capture the idea of impermanence, dissolvability and change. Far from being a predictable flow of programming, assembling and releasing activities, it is suggested that the Linux development process displays a stream of activities that keep feeding back into each other, thus creating a complex and unpredictable outcome. The paper further introduces the concept of contingent response patterns to investigate the interaction flows occurring on the Linux mailing lists and subsume patch postings, bug reports and the associated reviewing and debugging activities under its umbrella. The enactment-selection-retention (ESR) model is subsequently brought forward to conceptualize this process as enactment of programming skills subject to selection activities conducted by Torvalds who retains the selected features and feeds them back to the developers? pool to undergo further enactment activities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/iannacci2.pdf},
	author = {Federico Iannaci}
}
@conference {1150,
	title = {Leveraging Open-Source Communities To Improve the Quality \& Performance of Open-Source Software},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {Open-source processes have emerged as an effective approach to reduce cycle-time and decrease development and quality assurance costs for certain types of software. they are not without challenges, however, such as decreasing long-term maintenance and evolution costs, improving quality assurance, sustaining end-user confidence and good will, and ensuring the coherency of system-wide software and usability properties. Although aspects of these issues are unique to open-source	development,	well-organized	open-source projects make it easier to address certain of these challenges compared with traditional closed-source approaches to building software.
We have begun a long-term research effort, called Skoll, whose goal is to leverage common open-source project assets, such as their technologically sophisticated worldwide user communities, to devise techniques that address key challenges of open-source software development. In particular, we are conducting a long-term case study of two widely used open-source projects, ACE and TAO, to design, deploy, and evaluate techniques for improving quality through continuous distributed testing and profiling. This position paper presents our view of the pros and cons of open-source processes and outlines the work we are doing to improve the quality and performance of open-source software.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/schmidt.pdf},
	author = {Schmidt, D.C. and Porter, A.}
}
@article {flosswp9,
	title = {The Linux Kernel Development As a Model of Knowledge Creation},
	year = {2000},
	month = {October},
	abstract = {Applying the method of induction theory building, the authors have developed a case study based on the Linux kernel development process to build a model of Open Source knowledge creation.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/LinuxKernelDevelopmentAbstract.pdf},
	author = {Gwendolyn Lee}
}
