@proceedings {1901,
	title = {Adoption of Academic Tools in Open Source Communities: The Debian Case Study},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {139-150},
	publisher = {Springer},
	abstract = {Component repositories play a key role in the open software ecosystem. Managing the evolution of these repositories is a challenging task, and maintainers are confronted with a number of complex issues that need automatic tools to be adressed properly.

In this paper, we present an overview of 10 years of research in this field and the process leading to the adoption of our tools in a FOSS community. We focus on the Debian distribution and in particular we look at the issues arising during the distribution lifecycle: ensuring buildability of source packages, detecting packages that cannot be installed and bootstrapping the distribution on a new architecture. We present three tools, distcheck, buildcheck and botch, that we believe of general interest for other open source component repositories.

The lesson we have learned during this journey may provide useful guidance for researchers willing to see their tools broadly adopted by the community.},
	keywords = {components, debian, distribution},
	doi = {10.1007/978-3-319-57735-7_14},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_14},
	author = {Abate, Pietro and Di Cosmo, Roberto}
}
@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}
}
@article {1924,
	title = {Developers, Quality Control and Download Volume in Open Source Software (OSS) Projects},
	journal = {Journal of Organizational and End User Computing},
	volume = {29},
	year = {2017},
	month = {04/2017},
	pages = {43 - 66},
	abstract = {The open-source software (OSS) movement is often analogized as a commons, where products are developed by and consumed in an open community. However, does a larger commons automatically beget success or does the phenomenon fall prey to the tragedy of the commons? This research forwards and empirically investigates the curvilinear relationship between developers and OSS project quality and a project{\textquoteright}s download volume. Using segmented regression on over 12,000 SourceForge OSS projects, findings suggest an inflection point in the number of contributing developers on download volume {\textendash} suggesting increasing and diminishing returns to scale from adding developers to OSS projects. Findings support the economic principle of the tragedy of the commons, a concept where an over-allocated (large number) of developers, even in an open-source environment, can lead to resource mismanagement and reduce the benefit of a public good, i.e. the OSS project.
},
	issn = {1546-5012},
	doi = {10.4018/JOEUC.2017040103},
	author = {Hill, Geoffrey and Datta, Pratim and Vander Weerdt, Candice}
}
@proceedings {1908,
	title = {How Open Source Projects use Static Code Analysis Tools in Continuous Integration Pipelines},
	year = {2017},
	note = {Data: the paper studies the use of ASCATs (Automated Static Code Analysis Tools) within CI pipelines of 20 popular Java open source projects hosted on GitHub and using Travis CI to support CI activities},
	month = {05/2017},
	pages = {334-344},
	abstract = {Static analysis tools are often used by software developers
to entail early detection of potential faults, vulnerabilities,
code smells, or to assess the source code adherence to coding
standards and guidelines. Also, their adoption within Continuous
Integration (CI) pipelines has been advocated by researchers and
practitioners. This paper studies the usage of static analysis tools
in 20 Java open source projects hosted on GitHub and using
Travis CI as continuous integration infrastructure. Specifically,
we investigate (i) which tools are being used and how they are
configured for the CI, (ii) what types of issues make the build fail
or raise warnings, and (iii) whether, how, and after how long are
broken builds and warnings resolved. Results indicate that in the
analyzed projects build breakages due to static analysis tools are
mainly related to adherence to coding standards, and there is also
some attention to missing licenses. Build failures related to tools
identifying potential bugs or vulnerabilities occur less frequently,
and in some cases such tools are activated in a {\textquotedblleft}softer{\textquotedblright} mode,
without making the build fail. Also, the study reveals that build
breakages due to static analysis tools are quickly fixed by actually
solving the problem, rather than by disabling the warning, and
are often properly documented.},
	keywords = {continuous integration, empirical study, static analysis},
	doi = {10.1109/MSR.2017.2},
	author = {Zampetti, Fiorella and Scalabrino, Simone and Oliveto, Rocco and Canfora, Gerardo and Di Penta, Massimiliano}
}
@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 {1911,
	title = {Machine Learning-Based Detection of Open Source License Exceptions},
	year = {2017},
	note = {"We address these questions by first performing a large scale mining-based study... [W]e analyzed the  source code of 51,754 projects written in six different programming languages (Ruby, Javascript, Python, C, C++, and C$\#$) hosted on GitHub. },
	month = {05/2017},
	pages = {118-129},
	abstract = {From a legal perspective, software licenses govern the redistribution, reuse, and modification of software as both source and binary code. Free and Open Source Software (FOSS) licenses vary in the degree to which they are permissive or restrictive in allowing redistribution or modification under licenses different from the original one(s). In certain cases developers may modify the license by appending to it an exception to specifically allow reuse or modification under a particular condition. These exceptions are an important factor to consider for license compliance analysis since they modify the standard (and widely understood_ terms of the original license. In this work, we first perform a large-scale empirical study on the change history of over 51k FOSS systems aimed at quantitatively investigating the prevalence of known license exceptions and identifying new ones. Subsequently, we performed a study on the detection of license exceptions by relying on machine learning. We evaluated the license exception classification with four different supervised learners and sensitivity analysis. Finally we present a categorization of license exceptions and explain their implications.},
	keywords = {classifier, empirical studies, license, machine learning},
	doi = {10.1109/ICSE.2017.19},
	author = {Vendome, Christopher and Mario Linares-Vasquez and Bavota, Gabriele and Di Penta, Massimiliano and Daniel M. German and Poshyvanyk, Denys}
}
@proceedings {1888,
	title = {Technical Lag in Software Compilations: Measuring How Outdated a Software Deployment Is},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {182 - 192},
	publisher = {Springer International Publishing},
	abstract = {Large software compilations based on free, open source software (FOSS) packages are the basis for many software systems. When they are deployed in production, specific versions of the packages in the compilation are selected for installation. Over time, those versions become outdated with respect to the upstream software from which they are produced, and from the components available in the compilations as well. The fact that deployed components are outdated is not a problem in itself, but there is a price to pay for not being "as much updated as reasonable". This includes bug fixes and new features that could, at least potentially, be interesting for the deployed system. Therefore, a balance has to be maintained between "being up-to-date" and "keeping the good old working versions". This paper proposes a theoretical model (the "technical lag") for measuring how outdated a system is, with the aim of assisting in the decisions about upgrading in production. The paper explores several ways in which technical lag can be implemented, depending on requirements. As an illustration, it presents as well some specific cases in which the evolution of technical lag is computed.},
	isbn = {978-3-319-57735-7},
	issn = {1868-422X},
	doi = {10.1007/978-3-319-57735-7_17},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_17},
	author = {Gonz{\'a}lez-Barahona, J.M. and Sherwood, P. and Robles, G. and Izquierdo, D.},
	editor = {Balaguer, Federico and Di Cosmo, Roberto and Garrido, Alejandra and Kon, Fabio and Gregorio Robles and Zacchiroli, Stefano}
}
@proceedings {1918,
	title = {Using Gamification to Orient and Motivate Students to Contribute to OSS Projects},
	year = {2017},
	month = {05/2017},
	pages = {36-42},
	abstract = {Students can benefit from contributing to Open Source Software (OSS), since they can enrich their portfolio and learn with real world projects. However, sometimes students are demotivated to contribute due to entrance barriers. On the other hand, gamification is widely used to engage and motivate people to accomplish tasks and improve their performance. The goal of this work is to analyze the use of gamification to orient and motivate undergraduate students to overcome onboarding barriers and engage to OSS projects. To achieve this goal, we implemented four gaming elements (Quests, Points, Ranking, and Levels) in GitLab and assessed the environment by means of a study conducted with 17 students within a real OSS project (JabRed). At the end of the study, the students evaluated their experience through a questionnaire. We found that the Quest element helped to guide participants and keep them motivated and points helped by providing feedback on students{\textquoteright} performed tasks. We conclude that the gamified environment oriented the students in an attempt to make a contribution and that gamification can motivate and orient newcomers{\textquoteright} to engage to OSS projects. },
	keywords = {engagement, gamification, MOTIVATION, newcomers, students},
	author = {Guilherme C. Diniz and Marco A. Graciotto Silva and Marco Gerosa and Steinmacher, Igor}
}
@inbook {Rodr{\'\i}guez-P{\'e}rez2016,
	title = {BugTracking: A Tool to Assist in the Identification of Bug Reports},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {192{\textendash}198},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {BugTracking: A Tool to Assist in the Identification of Bug Reports},
	address = {Cham},
	abstract = {Issue tracking systems are used, in most software projects, but in particular in almost all free open source software, to record many different kinds of issues: bug reports, feature requests, maintenance tickets and even design discussions. Identifying which of those issues are bug reports is not a trivial task. When researchers want to conduct studies on the bug reports, managed by a software development project, first of all they need to perform this identification.
The job for researchers here is very different from the bug triaging that researchers do. In the latter case, people with a considerate experience in the project make a decision based on the information available at that time (maybe just a short comment by some user), asking, if needed, for more details. In the former case, researchers usually have not that experience in the project, but they have at their use all the information produced, until the moment the issue was closed. This may include not only all comments and actions on the issue tracking system, but for example, discussions about a fix in the code review system, or the final fixing patch in the source code management system. Having all that information conveyed to the researchers, in an easy, flexible and quick way, accelerates and makes their decision process much more reliable. It simplifies large scale manual analysis of issues (in hundreds or thousands), helping researchers to ensure that they are really working with what they intend to work: bug reports.
This paper presents a tool designed to solve exactly the problem of providing the researchers with all the relevant information needed to decide whether an issue corresponds to a bug report or not. The tool uses information extracted automatically from the projects repositories. It offers a web-based interface which allows collaboration, traceability and transparency of the identification of bug reports. All this makes the process easier, faster, and more reliable.},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_16},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_16},
	author = {Rodr{\'\i}guez-P{\'e}rez, Gema and Gonzalez-Barahona, Jes{\'u}s M. and Gregorio Robles and Dalipaj, Dorealda and Sekitoleko, Nelson},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@proceedings {1825,
	title = {Externalization of Software Behavior by the Mining of Norms},
	year = {2016},
	month = {05/2016},
	pages = {223-234},
	abstract = {Open Source Software Development (OSSD) often suffers from conflicting views and actions due to the perceived flat and open ecology of an open source community. This often manifests itself as a lack of codified knowledge that is easily accessible for community members. How decisions are made and expectations of a software system are often described in detail through the many forms of social communications that take place within a community. These social interactions form norms which are influential in dictating what behaviors are expected in a community and of the system. In this paper, we provide a tool which mines these social interactions (in the form of bug reports) and extract norms of the system, externalizing this information into a codified form that allows others within the community to be aware of without having witnessed the social interactions.},
	doi = {http://dx.doi.org/10.1145/2901739.2901744},
	author = {Daniel Avery and Dam, Hoa Khanh and Savarimuthu, Bastin Tony Roy and Aditya Ghose}
}
@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}
}
@article {Krishnamurthy:2016:PDP:2869770.2820618,
	title = {Peripheral Developer Participation in Open Source Projects: An Empirical Analysis},
	journal = {ACM Trans. Manage. Inf. Syst.},
	volume = {6},
	number = {4},
	year = {2016},
	pages = {14:1{\textendash}14:31},
	publisher = {ACM},
	address = {New York, NY, USA},
	abstract = {The success of the Open Source model of software development depends on the voluntary participation of external developers (the peripheral developers), a group that can have distinct motivations from that of project founders (the core developers). In this study, we examine peripheral developer participation by empirically examining approximately 2,600 open source projects. In particular, we hypothesize that peripheral developer participation is higher when the potential for building reputation by gaining recognition from project stakeholders is higher. We consider recognition by internal stakeholders (such as core developers) and external stakeholders (such as end-users and peers). We find a positive association between peripheral developer participation and the potential of stakeholder recognition after controlling for bug reports, feature requests, and other key factors. Our findings provide important insights for OSS founders and corporate managers for open sourcing or OSS adoption decisions.
},
	keywords = {Code ownership, open source software, project management, software metrics},
	issn = {2158-656X},
	doi = {10.1145/2820618},
	url = {http://doi.acm.org/10.1145/2820618},
	author = {Krishnamurthy, Rajiv and Jacob, Varghese and Radhakrishnan, Suresh and Kutsal Dogan}
}
@conference {Vasilescu:2016:SLM:2884781.2884875,
	title = {The Sky is Not the Limit: Multitasking Across GitHub Projects},
	booktitle = {Proceedings of the 38th International Conference on Software Engineering (ICSE 2016)},
	series = {ICSE {\textquoteright}16},
	year = {2016},
	pages = {994{\textendash}1005},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software development has always inherently required multitasking: developers switch between coding, reviewing, testing, designing, and meeting with colleagues. The advent of software ecosystems like GitHub has enabled something new: the ability to easily switch between projects. Developers also have social incentives to contribute to many projects; prolific contributors gain social recognition and (eventually) economic rewards. Multitasking, however, comes at a cognitive cost: frequent context-switches can lead to distraction, sub-standard work, and even greater stress. In this paper, we gather ecosystem-level data on a group of programmers working on a large collection of projects. We develop models and methods for measuring the rate and breadth of a developers{\textquoteright} context-switching behavior, and we study how context-switching affects their productivity. We also survey developers to understand the reasons for and perceptions of multitasking. We find that the most common reason for multitasking is interrelationships and dependencies between projects. Notably, we find that the rate of switching and breadth (number of projects) of a developer{\textquoteright}s work matter. Developers who work on many projects have higher productivity if they focus on few projects per day. Developers that switch projects too much during the course of a day have lower productivity as they work on more projects overall. Despite these findings, developers perceptions of the benefits of multitasking are varied.
},
	keywords = {github, multitasking, productivity},
	isbn = {978-1-4503-3900-1},
	doi = {10.1145/2884781.2884875},
	url = {http://doi.acm.org/10.1145/2884781.2884875},
	author = {Vasilescu, Bogdan and Blincoe, Kelly and Xuan, Qi and Casalnuovo, Casey and Damian, Daniela and Devanbu, Premkumar and Filkov, Vladimir}
}
@proceedings {1830,
	title = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	year = {2016},
	month = {05/2016},
	pages = {163-173},
	publisher = {Springer},
	abstract = {Women are underrepresented in the IT sector. But the situation in FLOSS (free, libre, open source software) development is really extreme in this respect: past publications and studies show a female participation of around 2\% to 5\% and have shed some light into this problem. In this paper, we give an update the state of knowledge tot he current situation of gender in FLOSS, by analyzing the results of surveying more than 2,000 contributors to FLOSS projects in 2013, of which more than 200 were women. Our findings confirm that women enter the FLOSS community later than men, do primarily other tasks than coding, participate less if they have children, and have slightly different reasons to enter (and to stay in) the development communities they join. However, we also find evidence that women are joiningFLOSS projects in higher numbers in recent years, and that the share of women devoting few hours per week to FLOSS and full-time dedication is higher than for men. All in all, comparing our results with the ones from the 2000s, the context of participation of women in FLOSS has not changed much. 
},
	attachments = {https://flosshub.org/sites/flosshub.org/files/paper-pre.pdf},
	author = {Gregorio Robles and Reina, Laura Arjona and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Due{\~n}as Dominguez, Santiago}
}
@inbook {Robles2016,
	title = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {163{\textendash}173},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Women in Free/Libre/Open Source Software: The Situation in the 2010s},
	address = {Cham},
	abstract = {Women are underrepresented in the IT sector. But the situation in FLOSS (free, libre, open source software) development is really extreme in this respect: past publications and studies show a female participation of around 2 \% to 5 \% and have shed some light into this problem. In this paper, we give an update the state of knowledge to the current situation of gender in FLOSS, by analyzing the results of surveying more than 2,000 contributors to FLOSS projects in 2013, of which more than 200 were women. Our findings confirm that women enter the FLOSS community later than men, do primarily other tasks than coding, participate less if they have children, and have slightly different reasons to enter (and to stay in) the development communities they join. However, we also find evidence that women are joining FLOSS projects in higher numbers in recent years, and that the share of women devoting few hours per week to FLOSS and full-time dedication is higher than for men. All in all, comparing our results with the ones from the 2000s, the context of participation of women in FLOSS has not changed much.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_13},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_13},
	author = {Gregorio Robles and Reina, Laura Arjona and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Dom{\'\i}nguez, Santiago Due{\~n}as},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@inbook {1735,
	title = {On the Availability and Effectiveness of Open Source Software for Digital Signing of PDF Documents},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {71-80},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Digital signatures are important in order to ensure the integrity and authenticity of information communicated over the Internet involving different stakeholders within and beyond the borders of different nations. The topic has gained increased interest in the European context and there is legislation and project initiatives aiming to facilitate use and standardisation of digital signatures. Open standards and open source implementations of open standards are important means for the interoperability and long-term maintenance of software systems implementing digital signatures. In this paper we report from a study aiming to establish the availability and effectiveness of software provided under an open source license for digital signing and validation of PDF documents. Specifically, we characterise the use of digital signatures in Swedish Governmental agencies, report on the interoperability of open source and proprietary licensed software for digital signatures in PDF documents, and establish the effectiveness of software provided under an open source license for validation of digital signatures in PDF documents.
},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_7},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_7},
	author = {Gamalielsson, Jonas and Jakobsson, Fredrik and Lundell, Bj{\"o}rn and Feist, Jonas and Gustavsson, Tomas and Landqvist, Fredric},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {1774,
	title = {Characterization and prediction of issue-related risks in software projects},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Identifying risks relevant to a software project and
planning measures to deal with them are critical to the success
of the project. Current practices in risk assessment mostly rely
on high-level, generic guidance or the subjective judgements
of experts. In this paper, we propose a novel approach to
risk assessment using historical data associated with a software
project. Specifically, our approach identifies patterns of past
events that caused project delays, and uses this knowledge to
identify risks in the current state of the project. A set of risk
factors characterizing {\textquotedblleft}risky{\textquotedblright} software tasks (in the form of
issues) were extracted from five open source projects: Apache,
Duraspace, JBoss, Moodle, and Spring. In addition, we performed
feature selection using a sparse logistic regression model to
select risk factors with good discriminative power. Based on
these risk factors, we built predictive models to predict if an
issue will cause a project delay. Our predictive models are able
to predict both the risk impact (i.e. the extend of the delay)
and the likelihood of a risk occurring. The evaluation results
demonstrate the effectiveness of our predictive models, achieving
on average 48\%{\textendash}81\% precision, 23\%{\textendash}90\% recall, 29\%{\textendash}71\%
F-measure, and 70\%{\textendash}92\% Area Under the ROC Curve. Our
predictive models also have low error rates: 0.39{\textendash}0.75 for Macroaveraged
Mean Cost-Error and and 0.7{\textendash}1.2 for Macro-averaged
Mean Absolute Error},
	url = {http://www.uow.edu.au/~hoa/papers/msr-2015-preprint.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr-2015-preprint.pdf},
	author = {Morakot Choetkiertikul and Dam, Hoa Khanh and Truyen Tran and Aditya Ghose}
}
@proceedings {1710,
	title = {Data Mining Behavioral Transitions in Open Source Repositories},
	year = {2015},
	pages = {5280-5289},
	publisher = {IEEE},
	abstract = {Open-source repository data can be automatically mined
using sequence mining methods to provide high-level
feedback on project status. GitHub.com projects are
acquired, sequence-mined, clustered, and regressed to
analyze project characteristics. Such results can be presented
to project managers, as part of a display generated by an
automated monitoring system. Such monitoring systems
provide high-level feedback in real-time. This project is a
preliminary step in a larger research project aimed at
understanding and monitoring FLOSS projects using this
process modeling approach. },
	author = {Robinson, William and Tianjie Deng}
}
@conference {blincoeMSR15,
	title = {Ecosystems in GitHub and a Method for Ecosystem Identification using Reference Coupling},
	booktitle = {12th Working Conference on Mining Software Repositories},
	series = {MSR},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	organization = {IEEE},
	abstract = {Software projects are not developed in isolation.
Recent research has shifted to studying software ecosystems,
communities of projects that depend on each other and are
developed together. However, identifying technical dependencies
at the ecosystem level can be challenging. In this paper, we
propose a new method, known as reference coupling, for detecting
technical dependencies between projects. The method establishes
dependencies through user-specified cross-references between
projects. We use our method to identify ecosystems in GitHubhosted
projects, and we identify several characteristics of the
identified ecosystems. We find that most ecosystems are centered
around one project and are interconnected with other ecosystems.
The predominant type of ecosystems are those that develop
tools to support software development. We also found that the
project owners{\textquoteright} social behaviour aligns well with the technical
dependencies within the ecosystem, but project contributors{\textquoteright}
social behaviour does not align with these dependencies. We
conclude with a discussion on future research that is enabled
by our reference coupling method.},
	url = {http://kblincoe.github.io/publications/2015_MSR_Ecosystems_CameraReady.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/2015_MSR_Ecosystems_CameraReady.pdf},
	author = {Blincoe, Kelly and Harrison, Francis and Damian, Daniela}
}
@inbook {1730,
	title = {An Empirical Study of the Relation Between Strong Change Coupling and Defects Using History and Social Metrics in the Apache Aries Project},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {3-12},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Change coupling is an implicit relationship observed when artifacts change together during software evolution. The literature leverages change coupling analysis for several purposes. For example, researchers discovered that change coupling is associated with software defects and reveals relationships between software artifacts that cannot be found by scanning code or documentation. In this paper, we empirically investigate the strongest change couplings from the Apache Aries project to characterize and identify their impact in software development. We used historical and social metrics collected from commits and issue reports to build classification models to identify strong change couplings. Historical metrics were used because change coupling is a phenomenon associated with recurrent co-changes found in the software history. In turn, social metrics were used because developers often interact with each other in issue trackers to accomplish the tasks. Our classification models showed high accuracy, with 70-99 \% F-measure and 88-99 \% AUC. Using the same set of metrics, we also predicted the number of future defects for the artifacts involved in strong change couplings. More specifically, we were able to predict 45.7 \% of defects where these strong change couplings reoccurred in the post-release. These findings suggest that developers and projects managers should detect and monitor strong change couplings, because they can be associated with defects and tend to happen again in the subsequent release.},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_1},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_1},
	author = {Wiese, Igor Scaliante and Kuroda, Rodrigo Takashi and Re, Reginaldo and Oliva, Gustavo Ansaldi and Gerosa, MarcoAur{\'e}lio},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1734,
	title = {Examining Usability Work and Culture in OSS},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {58-67},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Organizational culture has been recognized as an influential factor affecting the successes and failures of usability work in organizations; however, there is a lack of research on organizational culture in open source software (OSS) development. This paper shows that there are different kinds of cultures in OSS development projects and builds propositions on the relationship between culture and usability work in OSS development projects. Partly those are derived from the literature, partly from an exploratory empirical inquiry. We speculate whether there is an ideal culture type for usability work in OSS development or whether usability work should be modified to fit the different cultures of OSS development projects.
},
	keywords = {culture, empirical study, open source software, Usability},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_6},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_6},
	author = {Rajanen, Mikko and Iivari, Netta},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1741,
	title = {First Results About Motivation and Impact of License Changes in Open Source Projects},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {137-145},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Free and open source software is characterized by the freedoms and criteria that are warranted by specific licenses. These licenses describe the rights and duties of the licensors and licensees. However, a licensing change may be necessary in the life of an open source project to meet legal developments or to allow the implementation of new business models. This paper examines the motivations and impacts of license changes in open source projects. After a state of the art on the subject, a set of case studies where projects changed their license is presented. Then a set of motivations to change licenses, the ways to legally make this change, the problems caused by this change and a set of benefits of the license change are discussed.
},
	keywords = {Business model, Contributor agreement, intellectual property, license, open source},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_13},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_13},
	author = {Viseur, Robert and Gregorio Robles},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {1713,
	title = {Gender and Tenure Diversity in GitHub Teams},
	year = {2015},
	abstract = {Software development is usually a collaborative venture.
Open Source Software (OSS) projects are no exception; indeed,
by design, the OSS approach can accommodate teams
that are more open, geographically distributed, and dynamic
than commercial teams. This, we find, leads to OSS teams
that are quite diverse. Team diversity, predominantly in of-
fline groups, is known to correlate with team output, mostly
with positive effects. How about in OSS?
Using GITHUB, the largest publicly available collection of
OSS projects, we studied how gender and tenure diversity
relate to team productivity and turnover. Using regression
modeling of GITHUB data and the results of a survey, we
show that both gender and tenure diversity are positive and
significant predictors of productivity, together explaining a
sizable fraction of the data variability. These results can
inform decision making on all levels, leading to better outcomes
in recruiting and performance.},
	keywords = {gender, github, team},
	url = {http://bvasiles.github.io/papers/chi15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/chi15.pdf},
	author = {Vasilescu, Bogdan and Posnett, Daryl and Ray, Baishakhi and van den Brand, Mark G.J. and Serebrenik, Alexander and Devanbu, Premkumar and Filkov, Vladimir}
}
@inbook {1732,
	title = {How Developers Acquire FLOSS Skills},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {23-32},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {With the increasing prominence of open collaboration as found in free/libre/open source software projects and other joint production communities, potential participants need to acquire skills. How these skills are learned has received little research attention. This article presents a large-scale survey (5,309 valid responses) in which users and developers of the beta release of a popular file download application were asked which learning styles were used to acquire technical and social skills. We find that the extent to which a person acquired the relevant skills through informal methods tends to be higher if the person is a free/libre/open source code contributor, while being a professional software developer does not have this effect. Additionally, younger participants proved more likely to make use of formal methods of learning. These insights will help individuals, commercial companies, educational institutions, governments and open collaborative projects decide how they promote learning.
},
	keywords = {competencies, Informal learning, Non-formal learning, open source, Skills, Software developer},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_3},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/oss-2015.pdf},
	author = {Barcomb, Ann and Grottke, Michael and Stauffert, Jan-Philipp and Dirk Riehle and Jahn, Sabrina},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1733,
	title = {Implicit Coordination: A Case Study of the Rails OSS Project},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {35-44},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Previous studies on coordination in OSS projects have studied explicit communication. Research has theorized on the existence of coordination without direct communication or implicit coordination in OSS projects, suggesting that it contributes to their success. However, due to the intangible nature of implicit coordination, no studies have confirmed these theories. We describe how implicit coordination can now be measured in modern collaborative development environments. Through a case study of a popular OSS GitHub-hosted project, we report on how and why features that support implicit coordination are used.
},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_4},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_4},
	author = {Blincoe, Kelly and Damian, Daniela},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@article {1796,
	title = {An in-depth study of the promises and perils of mining GitHub},
	journal = {Empirical Software Engineering},
	year = {2015},
	publisher = {Springer},
	abstract = {With over 10 million git repositories, GitHub is becoming one of the most important sources of software artifacts on the Internet. Researchers mine the information stored in GitHub{\textquoteright}s event logs to understand how its users employ the site to collaborate on software, but so far there have been no studies describing the quality and properties of the available GitHub data. We document the results of an empirical study aimed at understanding the characteristics of the repositories and users in GitHub; we see how users take advantage of GitHub{\textquoteright}s main features and how their activity is tracked on GitHub and related datasets to point out misalignment between the real and mined data. Our results indicate that while GitHub is a rich source of data on software development, mining GitHub for research purposes should take various potential perils into consideration. For example, we show that the majority of the projects are personal and inactive, and that almost 40\% of all pull requests do not appear as merged even though they were. Also, approximately half of GitHub{\textquoteright}s registered users do not have public activity, while the activity of GitHub users in repositories is not always easy to pinpoint. We use our identified perils to see if they can pose validity threats; we review selected papers from the MSR 2014 Mining Challenge and see if there are potential impacts to consider. We provide a set of recommendations for software engineering researchers on how to approach the data in GitHub.},
	keywords = {github},
	issn = {1573-7616},
	doi = {10.1007/s10664-015-9393-5},
	url = {http://www.gousios.gr/pub/promises-perils-github-extended.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/promises-perils-github-extended.pdf},
	author = {Kalliamvakou, Eirini and Gousios, Georgios and Blincoe, Kelly and Singer, Leif and Daniel M. German and Damian, Daniela}
}
@conference {1798,
	title = {Integrating Open Source Software Repositories on the Web through Linked Data},
	booktitle = {2015 IEEE International Conference on Information Reuse and Integration (IRI)2015 IEEE International Conference on Information Reuse and Integration},
	year = {2015},
	pages = {114 - 121},
	publisher = {IEEE},
	organization = {IEEE},
	address = {San Francisco, CA, USA},
	abstract = {In this paper, we propose a novel approach to the problem of integrating code forges based on metadata (e.g., programming language, database, intended audience, operating system), similar software projects and software developers. We review the current problems in integrating metadata of different code forges and argue that Semantic Web technologies are suitable for representing and integrating knowledge contained inside these code forges. Further, we show the advantages of interlinking metadata of software projects to other relevant data sources on the Web, which will enable querying more information from the Web. Moreover, we compute the overlapping between code forges based on similar software developers and argue the benefit of interlinking similar software developers and software projects across different code forges through examples.
},
	doi = {10.1109/IRI.2015.27},
	author = {Iqbal, Aftab and Decker, Stefan}
}
@proceedings {1748,
	title = {Mining Component Repositories for Installability Issues},
	year = {2015},
	month = {05/2015},
	abstract = {Component repositories play an increasingly relevant
role in software life-cycle management, from software
distribution to end-user, to deployment and upgrade management.
Software components shipped via such repositories are
equipped with rich metadata that describe their relationship (e.g.,
dependencies and conflicts) with other components.
In this practice paper we show how to use a tool, distcheck,
that uses component metadata to identify all the components in
a repository that cannot be installed (e.g., due to unsatisfiable
dependencies), provides detailed information to help developers
understanding the cause of the problem, and fix it in the
repository.
We report about detailed analyses of several repositories: the
Debian distribution, the OPAM package collection, and Drupal
modules. In each case, distcheck is able to efficiently identify not
installable components and provide valuable explanations of the
issues. Our experience provides solid ground for generalizing the
use of distcheck to other component repositories.},
	keywords = {drupal, opam},
	url = {http://www.dicosmo.org/preprints/msr-2015-distcheck.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr-2015-distcheck.pdf},
	author = {Abate, Pietro and Di Cosmo, Roberto and Gesbert, Louis and Fabrice Le Fessant and Ralf Treinen and Zacchiroli, Stefano}
}
@proceedings {1728,
	title = {Mining Software Repositories for Social Norms},
	volume = {2},
	year = {2015},
	pages = {627-630},
	abstract = {Social norms facilitate coordination and cooperation
among individuals, thus enable smoother functioning of social
groups such as the highly distributed and diverse open source
software development (OSSD) communities. In these communities,
norms are mostly implicit and hidden in huge records
of human-interaction information such as emails, discussions
threads, bug reports, commit messages and even source code. This
paper aims to introduce a new line of research on extracting social
norms from the rich data available in software repositories. Initial
results include a study of coding convention violations in JEdit,
ArgoUML and Glassfish projects. It also presents a new lifecycle
model for norms in OSSD communities and demonstrates
how a number of norms extracted from the Python development
community follow this life-cycle model.},
	author = {Dam, Hoa Khanh and Savarimuthu, Bastin Tony Roy and Daniel Avery and Aditya Ghose}
}
@conference {1797,
	title = {On the Need of Integrating Social Media Channels and Open Source Software Repositories},
	booktitle = {2015 IEEE International Conference on Information Reuse and Integration (IRI)2015 IEEE International Conference on Information Reuse and Integration},
	year = {2015},
	pages = {396 - 402},
	publisher = {IEEE},
	organization = {IEEE},
	address = {San Francisco, CA, USA},
	abstract = {The growing interest in the usage of social media channels have attracted the open source software community to adopt an identity in order to disseminate project-related information to a wider audience. We foresee the need to integrate social media channels and open source software repositories in order to get an integrated view on the software project not only from the software development perspective but also from social perspective. Therefore, in this paper we study the usage of Twitter by software developers through harvesting their project-related activities on Twitter. In particular, we present the most frequently used hashtags by software developers and further investigate if project-related hashtags are the most frequent and commonly used hashtags by software developers. Based on our findings, we argue that relevant information from social media channels should be integrated with the open source software repositories in order to provide a homogeneous view on a software project.
},
	doi = {10.1109/IRI.2015.66},
	author = {Iqbal, Aftab and Decker, Stefan}
}
@proceedings {1726,
	title = {Open Source-Style Collaborative Development Practices in Commercial Projects Using GitHub},
	volume = {1},
	year = {2015},
	month = {05/2015},
	pages = {574-585},
	publisher = {ACM/IEEE},
	abstract = {Researchers are currently drawn to study projects
hosted on GitHub due to its popularity, ease of obtaining data,
and its distinctive built-in social features. GitHub has been found
to create a transparent development environment, which together
with a pull request-based workflow, provides a lightweight mechanism
for committing, reviewing and managing code changes.
These features impact how GitHub is used and the benefits it
provides to teams{\textquoteright} development and collaboration. While most of
the evidence we have is from GitHub{\textquoteright}s use in open source software
(OSS) projects, GitHub is also used in an increasing number of
commercial projects. It is unknown how GitHub supports these
projects given that GitHub{\textquoteright}s workflow model does not intuitively
fit the commercial development way of working. In this paper, we
report findings from an online survey and interviews with GitHub
users on how GitHub is used for collaboration in commercial
projects. We found that many commercial projects adopted
practices that are more typical of OSS projects including reduced
communication, more independent work, and self-organization.
We discuss how GitHub{\textquoteright}s transparency and popular workflow can
promote open collaboration, allowing organizations to increase
code reuse and promote knowledge sharing across their teams.},
	keywords = {github},
	doi = {10.1109/ICSE.2015.74},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icse-camera.pdf},
	author = {Kalliamvakou, E and Damian, Daniela and Blincoe, Kelly and Singer, L. and German, Daniel}
}
@inbook {1738,
	title = {A Qualitative Study on the Adoption of Open Source Software in Information Technology Outsourcing Organizations},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {103-113},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {The purpose of this paper is to identify the influence of Outsourcing on Open source software (OSS) and further investigate the factors that impact the adoption of OSS in global Information Technology (IT) outsourcing organizations serviced by Indian IT services providers. This exploratory research adopted positivism research philosophy and qualitative approach. An in-depth interview was conducted with ten participants across IT outsourcing organizations, IT service providers, and OSS service providers. The results show that IT outsourcing was not found to have an impact on OSS adoption. However, eight factors including management support and OSS support availability was identified to influence OSS adoption. IT services providers can utilize this research model to increase their understanding of why some IT outsourcing organizations choose to adopt OSS, while seemingly similar ones facing similar market conditions do not.
},
	keywords = {Diffusion of innovation, Indian IT, IT outsourcing, open source software, OSS adoption, TOE},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_10},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_10},
	author = {Ramanathan, Lakshmanan and Iyer, Sundaresan Krishnan},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1743,
	title = {The Right to a Contribution: An Exploratory Survey on How Organizations Address It},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {157-167},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Free and Open Source Software (FOSS) projects are characterized by the opportunity to attract external contributors, where contributions can be in any form of copyrightable material, such as code or documentation. In most of them it is understood that contributions would be licensed in similar or compatible terms than the project{\textquoteright}s license. Some projects require a copyright transfer from the contributor to an organization for the work contributed to a project, such documents are known as copyright assignment agreements. In a way, it is similar to the copyright transfer than some researchers grant to a publisher. In this work we present an exploratory survey of the multiple visions of copyright assignments, and aggregate them in a work that researchers and practitioners could use to get informed of the alternatives available in the literature. We expect that our findings help inform practitioners on legal concerns when receiving external contributions.
},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_15},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_15},
	author = {Poo-Caama{\~n}o, Germ{\'a}n and German, DanielM.},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@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 {1731,
	title = {Scaling and Internationalizing an Agile FOSS Project: Lessons Learned},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {13-22},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {This paper describes problems that arose with the scaling and internationalization of the open source project Catrobat. The problems we faced were the lack of a centralized user management, insufficient scaling of our communication channels, and the necessity to adapt agile development techniques to remote collaboration. To solve the problems we decided to use a mix of open source tools (Git, IRC, LDAP) and commercial solutions (Jira, Confluence, GitHub) because we believe that this mix best fits our needs. Other projects can benefit from the lessons we learned during the reorganization of our knowledge base and communication tools, as infrastructure changes can be very labor-intensive and time-consuming.},
	keywords = {Agile development, communication, Distributed software development, Documentation management, Internationalization, kanban, Scaling},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_2},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_2},
	author = {Fellhofer, Stephan and Harzl, Annemarie and Slany, Wolfgang},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@inbook {1737,
	title = {Smart Route Planning Using Open Data and Participatory Sensing},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {91-100},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {Smart cities are not merely the infusion of technology into a city{\textquoteright}s infrastructure, but also require citizens interacting with their urban environment in a smart and informed manner. Transportation is key aspect of smart cities. In this paper, we present a smart route planning open-source system; SMART-GH utilizes open data and participatory sensing, where citizens actively participate in collecting data about the city in their daily environment, e.g., noise, air pollution, etc. SMART-GH then augments the routing logic with sensor data to answer queries such as {\textquoteleft}return the least noisy route{\textquoteright}. SMART-GH enables citizens to make smarter decisions about their daily commute, and subsequently improve their quality of life.
},
	keywords = {Open-data, open-source, Participatory sensing, Smart-city-routing},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_9},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/nallur15.pdf},
	author = {Nallur, Vivek and Elgammal, Amal and Clarke, Siobh{\'a}n},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@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.}
}
@proceedings {1754,
	title = {Unveiling Exception Handling Bug Hazards in Android based on GitHub and Google Code Issues},
	year = {2015},
	month = {05/2015},
	abstract = {This paper reports on a study mining the exception
stack traces included in 159,048 issues reported on Android
projects hosted in GitHub (482 projects) and Google Code (157
projects). The goal of this study is to investigate whether stack
trace information can reveal bug hazards related to exception
handling code that may lead to a decrease in application robustness.
Overall 6,005 exception stack traces were extracted,
and subjected to source code and bytecode analysis. The outcomes
of this study include the identification of the following
bug hazards: (i) unexpected cross-type exception wrappings (for
instance, trying to handle an instance of OutOfMemoryError
{\textquotedblleft}hidden{\textquotedblright} in a checked exception) which can make the exceptionrelated
code more complex and negatively impact the application
robustness; (ii) undocumented runtime exceptions thrown by both
the Android platform and third party libraries; and (iii) undocumented
checked exceptions thrown by the Android Platform.
Such undocumented exceptions make difficult, and most of the
times infeasible for the client code to protect against {\textquotedblleft}unforeseen{\textquotedblright}
situations that may happen while calling third-party code. This
study provides further insights on such bug hazards and the
robustness threats they impose to Android apps as well as to
other systems based on the Java exception model.},
	keywords = {github, google code},
	url = {http://www.gousios.gr/pub/android-stacks.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/android-stacks.pdf},
	author = {Roberta Coelho and Lucas Almeida and Gousios, Georgios and van Deursen, Arie}
}
@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.}
}
@proceedings {1766,
	title = {Wait For It: Determinants of Pull Request Evaluation Latency on GitHub},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {The pull-based development model, enabled by git
and popularised by collaborative coding platforms like BitBucket,
Gitorius, and GitHub, is widely used in distributed software
teams. While this model lowers the barrier to entry for potential
contributors (since anyone can submit pull requests to any repository),
it also increases the burden on integrators (i.e., members
of a project{\textquoteright}s core team, responsible for evaluating the proposed
changes and integrating them into the main development line),
who struggle to keep up with the volume of incoming pull
requests. In this paper we report on a quantitative study that tries
to resolve which factors affect pull request evaluation latency
in GitHub. Using regression modeling on data extracted from
a sample of GitHub projects using the Travis-CI continuous
integration service, we find that latency is a complex issue,
requiring many independent variables to explain adequately.},
	url = {https://bvasiles.github.io/papers/msr15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr15.pdf},
	author = {Yu, Yue and Wang, Huaimin and Filkov, Vladimir and Devanbu, Premkumar and Vasilescu, Bogdan}
}
@proceedings {1768,
	title = {Will they like this? Evaluating Code Contributions With Language Models},
	year = {2015},
	month = {05/2015},
	publisher = {IEEE},
	abstract = {Popular open-source software projects receive and
review contributions from a diverse array of developers, many
of whom have little to no prior involvement with the project. A
recent survey reported that reviewers consider conformance to
the project{\textquoteright}s code style to be one of the top priorities when evaluating
code contributions on Github. We propose to quantitatively
evaluate the existence and effects of this phenomenon. To this aim
we use language models, which were shown to accurately capture
stylistic aspects of code. We find that rejected changesets do
contain code significantly less similar to the project than accepted
ones; furthermore, the less similar changesets are more likely
to be subject to thorough review. Armed with these results we
further investigate whether new contributors learn to conform to
the project style and find that experience is positively correlated
with conformance to the project{\textquoteright}s code style.},
	url = {http://sback.it/publications/msr2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2015_0.pdf},
	author = {Vincent J. Hellendoorn and Premkumar T. Devanbu and Bacchelli, Alberto}
}
@conference {Vasilescu:2014:SQS:2531602.2531659,
	title = {How Social Q\&A Sites Are Changing Knowledge Sharing in Open Source Software Communities},
	booktitle = {Proceedings of the 17th ACM Conference on Computer Supported Cooperative Work \&\#38; Social Computing},
	series = {CSCW {\textquoteright}14},
	year = {2014},
	pages = {342{\textendash}354},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Historically, mailing lists have been the preferred means for coordinating development and user support activities. With the emergence and popularity growth of social Q\&A sites such as the StackExchange network (e.g., StackOverflow), this is beginning to change. Such sites offer different socio-technical incentives to their participants than mailing lists do, e.g., rich web environments to store and manage content collaboratively, or a place to showcase their knowledge and expertise more vividly to peers or potential recruiters. A key difference between StackExchange and mailing lists is gamification, i.e., StackExchange participants compete to obtain reputation points and badges. In this paper, we use a case study of R (a widely-used tool for data analysis) to investigate how mailing list participation has evolved since the launch of StackExchange. Our main contribution is the assembly of a joint data set from the two sources, in which participants in both the texttt{r-help} mailing list and StackExchange are identifiable. This permits their activities to be linked across the two resources and also over time. With this data set we found that user support activities show a strong shift away from texttt{r-help}. In particular, mailing list experts are migrating to StackExchange, where their behaviour is different. First, participants active both on texttt{r-help} and on StackExchange are more active than those who focus exclusively on only one of the two. Second, they provide faster answers on StackExchange than on texttt{r-help}, suggesting they are motivated by the emph{gamified} environment. To our knowledge, our study is the first to directly chart the changes in behaviour of specific contributors as they migrate into gamified environments, and has important implications for knowledge management in software engineering.},
	keywords = {a, crowdsourced knowledge, gamification., mailing lists, open source, social q\&\#38},
	isbn = {978-1-4503-2540-0},
	doi = {10.1145/2531602.2531659},
	url = {http://doi.acm.org/10.1145/2531602.2531659},
	attachments = {https://flosshub.org/sites/flosshub.org/files/cscw14.pdf},
	author = {Vasilescu, Bogdan and Serebrenik, Alexander and Devanbu, Prem and Filkov, Vladimir}
}
@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 {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 {Kalliamvakou:2014:PPM:2597073.2597074,
	title = {The Promises and Perils of Mining GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {92{\textendash}101},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {With over 10 million git repositories, GitHub is becoming one of the most important source of software artifacts on the Internet. Researchers are starting to mine the information stored in GitHub{\textquoteright}s event logs, trying to understand how its users employ the site to collaborate on software. However, so far there have been no studies describing the quality and properties of the data available from GitHub. We document the results of an empirical study aimed at understanding the characteristics of the repositories in GitHub and how users take advantage of GitHub{\textquoteright}s main features---namely commits, pull requests, and issues. Our results indicate that, while GitHub is a rich source of data on software development, mining GitHub for research purposes should take various potential perils into consideration. We show, for example, that the majority of the projects are personal and inactive; that GitHub is also being used for free storage and as a Web hosting service; and that almost 40\% of all pull requests do not appear as merged, even though they were. We provide a set of recommendations for software engineering researchers on how to approach the data in GitHub.
},
	keywords = {bias, code reviews, git, github, mining software repositories},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597074},
	url = {http://doi.acm.org/10.1145/2597073.2597074},
	attachments = {https://flosshub.org/sites/flosshub.org/files/perils.pdf},
	author = {Kalliamvakou, Eirini and Gousios, Georgios and Blincoe, Kelly and Singer, Leif and Daniel M. German and Damian, Daniela}
}
@conference {Sheoran:2014:UWG:2597073.2597114,
	title = {Understanding "Watchers" on GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {336{\textendash}339},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Users on GitHub can watch repositories to receive notifications about project activity. This introduces a new type of passive project membership. In this paper, we investigate the behavior of watchers and their contribution to the projects they watch. We find that a subset of project watchers begin contributing to the project and those contributors account for a significant percentage of contributors on the project. As contributors, watchers are more confident and contribute over a longer period of time in a more varied way than other contributors. This is likely attributable to the knowledge gained through project notifications.
},
	keywords = {github, mining challenge, msr challenge, repositories, Software Teams, Watchers},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597114},
	url = {http://doi.acm.org/10.1145/2597073.2597114},
	author = {Sheoran, Jyoti and Blincoe, Kelly and Kalliamvakou, Eirini and Damian, Daniela and Ell, Jordan}
}
@inbook {1622,
	title = {USB Device Management in GNU/Linux Systems},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {218-225},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

Protecting the access to USB ports has the same priority for information security than firewalls and antivirus software. Nowadays there are some tools that allow us to monitor and regulate the access to USB devices, but all of them are distributed under proprietary licenses. This work presents an application that solves the mentioned problem: ?{\textquoteright}How controlling the access to USB mass storage devices in GNU/Linux Operating Systems?
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_33},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_33},
	author = {Deroncel{\'e}, EdilbertoBlez and Fuentes, AllanPierra and Tejera Hern{\'a}ndez, DayanaCaridad and C{\'a}ceres Navarro, Haniel and F{\'\i}rvida Donest{\'e}vez, AbelAlfonso and Febles Parker, MichelEvaristo},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@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 {1522,
	title = {Boa: A Language and Infrastructure for Analyzing Ultra-Large-Scale Software Repositories},
	year = {2013},
	month = {05/2013},
	pages = {422-431},
	abstract = {In today{\textquoteright}s software-centric world, ultra-large-scale software repositories, e.g. SourceForge (350,000+ projects), GitHub (250,000+ projects), and Google Code (250,000+ projects) are the new library of Alexandria. They contain an enormous corpus of software and information about software. Scientists and engineers alike are interested in analyzing this wealth of information both for curiosity as well as for testing important hypotheses. However, systematic extraction of relevant data from these repositories and analysis of such data for testing hypotheses is hard, and best left for mining software repository (MSR) experts! The goal of Boa, a domain-specific language and infrastructure described here, is to ease testing MSR-related hypotheses. We have implemented Boa and provide a web-based interface to Boa{\textquoteright}s infrastructure. Our evaluation demonstrates that Boa substantially reduces programming efforts, thus lowering the barrier to entry. We also see drastic improvements in scalability. Last but not least, reproducing an experiment conducted using Boa is just a matter of re-running small Boa programs provided by previous researchers.},
	keywords = {ease of use, forge, github, google code, lower barrier to entry, mining, repository, reproducible, scalable, Software, sourceforge},
	author = {Dyer, Robert and Nguyen, Hoan Anh and Rajan, Hridesh and Nguyen, Tien N.}
}
@proceedings {1491,
	title = {Communication in Open Source Software Development Mailing Lists},
	year = {2013},
	note = {"The entire dataset used in the experiment, including the cards, the resolved aliases, and detailed statistical results, can be downloaded from ..." http://www.st.ewi.tudelft.nl/~guzzi/oss-communication/},
	month = {05/2013},
	pages = {277-286},
	abstract = {Open source software (OSS) development teams use
electronic means, such as emails, instant messaging, or forums,
to conduct open and public discussions. Researchers investigated
mailing lists considering them as a hub for project communication. Prior work focused on specific aspects of emails, for example
the handling of patches, traceability concerns, or social networks.
This led to insights pertaining to the investigated aspects, but not
to a comprehensive view of what developers communicate about.
Our objective is to increase the understanding of development
mailing lists communication.
We quantitatively and qualitatively analyzed a sample of 506
email threads from the development mailing list of a major OSS
project, Lucene. Our investigation reveals that implementation
details are discussed only in about 35\% of the threads, and that
a range of other topics is discussed. Moreover, core developers
participate in less than 75\% of the threads. We observed that the
development mailing list is not the main player in OSS project
communication, as it also includes other channels such as the
issue repository.},
	keywords = {email, lucene, mailling list},
	url = {http://www.st.ewi.tudelft.nl/~guzzi/downloads/Guzzi2013msr.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Guzzi2013msr.pdf},
	author = {Guzzi, Anja and Bacchelli, Alberto and Lanza, Michele and Pinzger, Martin and van Deursen, Arie}
}
@proceedings {1502,
	title = {A Dataset from Change History to Support Evaluation  of Software Maintenance Tasks},
	year = {2013},
	month = {05/2013},
	pages = {131-134},
	abstract = {Approaches that support software maintenance need 
to be evaluated and compared against existing ones, in order to 
demonstrate their usefulness in practice. However, oftentimes the 
lack of well-established sets of benchmarks leads to situations 
where these approaches are evaluated using different datasets, 
which results in biased comparisons. In this data paper we 
describe and make publicly available a set of benchmarks from 
six Java applications, which can be used in the evaluation of 
various software engineering (SE) tasks, such as feature location 
and impact analysis. These datasets consist of textual description 
of change requests, the locations in the source code where they 
were implemented, and execution traces. Four of the benchmarks 
were already used in several SE research papers, and two of them 
are new. In addition, we describe in detail the methodology used 
for generating these benchmarks and provide a suite of tools in 
order to encourage other researchers to validate our datasets and 
generate new benchmarks for other subject software systems. 
Our online appendix: http://www.cs.wm.edu/semeru/data/msr13/ },
	url = {http://www.cs.wm.edu/~bdit/publications/MSR13DataPaper_Dit_CRC.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/MSR13DataPaper_Dit_CRC.pdf},
	author = {Bogdan Dit and Andrew Holtzhauer and Poshyvanyk, Denys and Kagdi, Huzefa}
}
@proceedings {1508,
	title = {The Eclipse and Mozilla Defect Tracking Dataset: A Genuine Dataset for Mining Bug Information},
	year = {2013},
	note = {Intended to be an "open bug database" or baseline for multiple studies in the community. 14 bug attributes [id, product, summary, status, etc], some change over time and some do not. Data set: github.com/ansymo/msr2013-bug_dataset},
	month = {05/2013},
	abstract = {The analysis of bug reports is an important subfield within the mining software repositories community. It explores the rich data available in defect tracking systems to uncover interesting and actionable information about the bug triaging process. While bug data is readily accessible from systems like Bugzilla and JIRA, a common database schema and a curated dataset could significantly enhance future research because it allows for easier replication. Consequently, in this paper we propose the Eclipse and Mozilla Defect Tracking Dataset, a representative database of bug data, filtered to contain only genuine defects (i.e., no feature requests) and designed to cover the whole bug-triage life cycle (i.e., store all intermediate actions). We have used this dataset ourselves for predicting bug severity, for studying bug-fixing time and for identifying erroneously assigned components. github.com/ansymo/msr2013-bug_dataset},
	url = {http://github.com/ansymo/msr2013-bug_dataset},
	author = {Lamkanfi, Ahmed and Javier P{\'e}rez and Demeyer, Serge}
}
@article {1865,
	title = {The Effects of Diversity in Global, Distributed Collectives: A Study of Open Source Project Success},
	journal = {Information Systems Research},
	volume = {24},
	year = {2013},
	month = {06/2013},
	pages = {312 - 333},
	abstract = {Diversity is a defining characteristic of global collectives facilitated by the Internet. Though substantial evidence suggests that diversity has profound implications for a variety of outcomes including performance, member engagement, and withdrawal behavior, the effects of diversity have been predominantly investigated in the context of organizational workgroups or virtual teams. We use a diversity lens to study the success of nontraditional virtual work groups exemplified by open source software (OSS) projects. Building on the diversity literature, we propose that three types of diversity (separation, variety, and disparity) influence two critical outcomes for OSS projects: community engagement and market success. We draw on the OSS literature to further suggest that the effects of diversity on market success are moderated by the application development stage. We instantiate the operational definitions of three forms of diversity to the unique context of open source projects. Using archival data from 357 projects hosted on SourceForge, we find that disparity diversity, reflecting variation in participants{\textquoteright} contribution-based reputation, is positively associated with success. The impact of separation diversity, conceptualized as culture and measured as diversity in the spoken language and country of participants, has a negative impact on community engagement but an unexpected positive effect on market success. Variety diversity, reflected in dispersion in project participant roles, positively influences community engagement and market success. The impact of diversity on market success is conditional on the development stage of the project. We discuss how the study{\textquoteright}s findings advance the literature on antecedents of OSS success, expand our theoretical understanding of diversity, and present the practical implications of the results for managers of distributed collectives.},
	issn = {1526-5536},
	doi = {10.1287/isre.1120.0435},
	author = {Sherae Daniel and Ritu Agarwal and Stewart, Katherine J.}
}
@proceedings {1500,
	title = {Linux Variability Anomalies: What Causes Them and How Do They Get Fixed?},
	year = {2013},
	month = {05/2013},
	abstract = {The Linux kernel is one of the largest configurable open source software systems implementing static variability. In Linux, variability is scattered over three different artifacts: source code files, Kconfig files, and Makefiles. Previous work detected inconsistencies between these artifacts that led to anomalies in the intended variability of Linux. We call these variability anomalies. However, there has been no work done to analyze how these variability anomalies are introduced in the first place, and how they get fixed. In this work, we provide an analysis of the causes and fixes of variability anomalies in Linux. We first perform an exploratory case study that uses an existing set of patches which solve variability anomalies to identify patterns for their causes. The observations we make from this dataset allow us to develop four research questions which we then answer in a confirmatory case study on the scope of the whole Linux kernel. We show that variability anomalies exist for several releases in the kernel before they get fixed, and that contrary to our initial suspicion, typos in feature names do not commonly cause these anomalies. Our results show that variability anomalies are often introduced through incomplete patches that change Kconfig definitions without properly propagating these changes to the rest of the system. Anomalies are then commonly fixed through changes to the code rather than to Kconfig files.},
	author = {Sarah Nadi and Christian Dietrich and Reinhard Tartler and Holt, Richard C. and Daniel Lohmann}
}
@proceedings {1509,
	title = {The Maven Repository Dataset of Metrics, Changes, and Dependencies},
	year = {2013},
	month = {05/2013},
	abstract = {We present the Maven Dependency Dataset (MDD), containing metrics, changes and dependencies of 148,253 jar files. Metrics and changes have been calculated at the level of individual methods, classes and packages of multiple library versions. A complete call graph is also presented which includes call, inheritance, containment and historical relationships between all units of the entire repository. In this paper, we describe our dataset and the methodology used to obtain it. We present different conceptual views of MDD and we also describe limitations and data quality issues that researchers using this data should be aware of. http://data.3tu.nl/repository/uuid:68a0e837-4fda-407a-949e-a159546e67b6},
	keywords = {maven},
	doi = {dx.doi.org/10.4121/uuid:68a0e837-4fda-407a-949e-a159546e67b6},
	url = {http://data.3tu.nl/repository/uuid:68a0e837-4fda-407a-949e-a159546e67b6},
	author = {Steven Raemaekers and van Deursen, Arie and Visser, Joost}
}
@article {1401,
	title = {Clones: what is that smell?},
	journal = {Empirical Software Engineering},
	volume = {17},
	year = {2012},
	month = {8/2012},
	pages = {503 - 530},
	abstract = {Clones are generally considered bad programming practice in software engineering folklore. They are identified as a bad smell (Fowler et al. 1999) and a major contributor to project maintenance difficulties. Clones inherently cause code bloat, thus increasing project size and maintenance costs. In this work, we try to validate the conventional wisdom empirically to see whether cloning makes code more defect prone. This paper analyses the relationship between cloning and defect proneness. For the four medium to large open source projects that we studied, we find that, first, the great majority of bugs are not significantly associated with clones. Second, we find that clones may be less defect prone than non-cloned code. Third, we find little evidence that clones with more copies are actually more error prone. Fourth, we find little evidence to support the claim that clone groups that span more than one file or directory are more defect prone than collocated clones. Finally, we find that developers do not need to put a disproportionately higher effort to fix clone dense bugs. Our findings do not support the claim that clones are really a {\textquotedblleft}bad smell{\textquotedblright} (Fowler et al. 1999). Perhaps we can clone, and breathe easily, at the same time. },
	issn = {1573-7616},
	doi = {10.1007/s10664-011-9195-3},
	author = {Rahman, Foyzur and Christian Bird and Devanbu, Premkumar}
}
@conference {1357,
	title = {Content classification of developer emails},
	booktitle = {Proceedings of the 34th IEEE/ACM International Conference On Software Engineering (ICSE 2012)},
	year = {2012},
	note = {We created a web application to manually classify email content in the chosen categories. We classified a statistically significant set of emails from four java open source software (OSS) systems, used to evaluate the accuracy of our approach.
The contributions of this paper are:
1) a novel approach that fuses parsing and ML techniques
for classification of email lines;
2) a web application to manually classify email content; 3) the manual classification of a statistically significant
sample set of emails (for a total of 67,792 lines) from mailing lists of four different software systems{\textendash}in the form of a freely available benchmark; and
4) the empirical evaluation of our approach against the benchmark},
	month = {06/2012},
	abstract = {Emails related to the development of a software system contain information about design choices and issues encountered during the development process. Exploiting the knowledge embedded in emails with automatic tools is challenging, due to the unstructured, noisy and mixed language nature of this communication medium. Natural language text is often not well-formed and is interleaved with languages with other syntaxes, such as code or stack traces.

We present an approach to classify email content at line level. Our technique classifies email lines in five categories (i.e., text, junk, code, patch, and stack trace) to allow one to subsequently apply ad hoc analysis techniques for each category. We evaluated our approach on a statistically significant set of emails gathered from mailing lists of four unrelated open source systems.},
	keywords = {email, Emails, Empirical software engineering, mailing list, natural language, Unstructured Data Mining},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icse2012.pdf},
	author = {Bacchelli, Alberto and Dal Sasso, Tommaso and D{\textquoteright}Ambros, Marco and Lanza, Michele}
}
@conference {1375,
	title = {The Effects of Diversity in Global, Distributed Collectives: A Study of Open Source Project Success},
	booktitle = {Information Systems Research},
	year = {2012},
	abstract = {Diversity is a defining characteristic of global collectives facilitated by the Internet. Though substantial evidence suggests that diversity has profound implications for a variety of outcomes including performance, member engagement, and withdrawal behavior, the effects of diversity have been predominantly investigated in the context of organizational workgroups or virtual teams. We use a diversity lens to study the success of non-traditional virtual work groups exemplified by open source software (OSS) projects. Building on the diversity literature, we propose that three types of diversity (separation, variety and disparity) influence two critical outcomes for OSS projects: community engagement and market success. We draw on the OSS literature to further suggest that the effects of diversity on market success are moderated by the application development stage. We instantiate the operational definitions of three forms of diversity to the unique context of open source projects. Using archival data from 357 projects hosted on SourceForge, we find that disparity diversity, reflecting variation in participants{\textquoteleft} contribution-based reputation, is positively associated with success. The impact of separation diversity, conceptualized as culture and measured as diversity in the spoken language and country of participants, has a negative impact on community engagement but an unexpected positive effect on market success. Variety diversity, reflected in dispersion in project participant roles, positively influences community engagement and market success. The impact of diversity on market success is conditional on the development stage of the project. We discuss how the study{\textquoteleft}s findings advance the literature on antecedents of OSS success, expand our theoretical understanding of diversity, and present the practical implications of the results for managers of distributed collectives.},
	keywords = {diversity, global collectives, open source software},
	attachments = {https://flosshub.org/sites/flosshub.org/files/isr_2012.pdf},
	author = {Daniel, Sherae L. and Ritu Agarwal and Stewart, Katherine J.}
}
@proceedings {1377,
	title = {Examining Turnover in Open Source Software Projects Using a Logistic Hierarchical Linear Modeling Approach},
	volume = {378},
	year = {2012},
	month = {09/2012},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Developer turnover in open source software projects is a critical and insufficiently researched problem. Previous research has focused on understanding the developer motivations to contribute using either the individual developer perspective or the project perspective. In this exploratory study we argue that because the developers are embedded in projects it is imperative to include both perspectives. We analyze turnover in open source software projects by including both individual developer level factors, as well as project specific factors. Using the Logistic Hierarchical Linear Modeling approach allows us to empirically examine the factors influencing developer turnover and also how these factors differ among developers and projects.},
	keywords = {Logistic Hierarchical Linear Modeling, sourceforge, turnover},
	author = {Sharma, P.N. and Hulland, J. and Daniel, S.}
}
@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}
}
@proceedings {1472,
	title = {Hybrid Business Models in Software Product Industry: Patterns and Challenges},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {362-367},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Operating in software product industry is becoming an increasingly risky proposition. Compressed timeline for product development combined with need to reduce cost has compelled organizations to look at new ways of doing business. One such avenue is combining the erstwhile conflicting practices of open source and closed source software. This industry paper highlights common patterns and challenges encountered in operationalizing such business models. The findings are based on a larger multiple case study research involving six such software products.},
	author = {Deodhar, Swanand J. and Saxena, Kalbhushan C. and Ruohonen, Mikko}
}
@proceedings {1474,
	title = {OSS in 2012: A Long-Term Sustainable Alternative for Corporate IT},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {371-376},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {The current internet leaders (Google, Facebook, etc.) all have OSS in their DNA. Traditional corporations still rely mostly on proprietary software for their mission-critical IT systems. But, situation is changing: as tip of the iceberg, major stock exchanges of the world have announced successful migrations to OSS. Many traditional corporations can now follow the OSS path because this market has clearly matured in many relevant aspects for them. In addition, solutions are here to achieve quick, efficient and secure mutations to OSS which must be undoubtedly considered by CIOs as the technological state of the art for 2012.},
	author = {Durand, Didier and Vuattoux, Jean-Luc and Ditscheid, Pierre-Jean}
}
@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}
}
@article {springerlink:10.1007/s10664-012-9199-7,
	title = {Software Bertillonage},
	journal = {Empirical Software Engineering},
	year = {2012},
	note = {10.1007/s10664-012-9199-7},
	pages = {1-43},
	publisher = {Springer Netherlands},
	abstract = {Deployed software systems are typically composed of many pieces, not all of which may have been created by the main development team. Often, the provenance of included components{\textemdash}such as external libraries or cloned source code{\textemdash}is not clearly stated, and this uncertainty can introduce technical and ethical concerns that make it difficult for system owners and other stakeholders to manage their software assets. In this work, we motivate the need for the recovery of the provenance of software entities by a broad set of techniques that could include signature matching, source code fact extraction, software clone detection, call flow graph matching, string matching, historical analyses, and other techniques. We liken our provenance goals to that of Bertillonage, a simple and approximate forensic analysis technique based on bio-metrics that was developed in 19th century France before the advent of fingerprints. As an example, we have developed a fast, simple, and approximate technique called anchored signature matching for identifying the source origin of binary libraries within a given Java application. This technique involves a type of structured signature matching performed against a database of candidates drawn from the Maven2 repository, a 275 GB collection of open source Java libraries. To show the approach is both valid and effective, we conducted an empirical study on 945 jars from the Debian GNU/Linux distribution, as well as an industrial case study on 81 jars from an e-commerce application. },
	issn = {1382-3256},
	doi = {10.1007/s10664-012-9199-7},
	url = {http://dx.doi.org/10.1007/s10664-012-9199-7},
	author = {Davies, Julius and German, Daniel and Michael Godfrey and Hindle, Abram}
}
@conference {1314,
	title = {Apples vs. oranges?},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"In this MSR challenge report, we compare the source code of two in- dustrial grade Integrated Development Environments (IDE): Netbeans, developed by Oracle Corporation, and Eclipse, developed by the Eclipse Foundation. In the same spirit as [1], our goal is not to identify how similar or different they are, but to identify differences that, if not taken into consideration, might result in biased, and potentially erroneous conclusions."},
	month = {05/2011},
	pages = {246-249},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {We attempt to compare the source code of two Java IDE systems: Netbeans and Eclipse. The result of this experiment shows that many factors, if ignored, could risk a bias in the results, and we posit various observations that should be taken into consideration to minimize such risk.

},
	keywords = {eclipse, netbeans, source code},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985483},
	author = {Davies, Julius and Daniel M. German}
}
@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 {1309,
	title = {Do time of day and developer experience affect commit bugginess},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"we study the latest versions of the Linux kernel and PostgreSQL, which have 222,332 and 31,098 commits, respectively. We study the correlation between a commit{\textquoteright}s bugginess and the time of day of the commit, the day of week of the commit, and the experience and commit frequency of the commit authors. In addition, we study several other commit characteristics, such as comment-only fixes and bug lifetimes."},
	month = {05/2011},
	pages = {153-162},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Modern software is often developed over many years with hundreds of thousands of commits. Commit metadata is a rich source of social characteristics, including the commit{\textquoteright}s time of day and the experience and commit frequency of its author. The "bugginess" of a commit is also a critical property of that commit. In this paper, we investigate the correlation between a commit{\textquoteright}s social characteristics and its "bugginess"; such results can be very useful for software developers and software engineering researchers. For instance, developers or code reviewers might be well-advised to thoroughly verify commits that are more likely to be buggy. In this paper, we study the correlation between a commit{\textquoteright}s bugginess and the time of day of the commit, the day of week of the commit, and the experience and commit frequency of the commit authors. We survey two widely-used open source projects: the Linux kernel and PostgreSQL.

Our main findings include: (1) commits submitted between midnight and 4 AM (referred to as late-night commits) are significantly buggier and commits between 7 AM and noon are less buggy, implying that developers may want to double-check their own latenight commits; (2) daily-committing developers produce less-buggy commits, indicating that we may want to promote the practice of daily-committing developers reviewing other developers{\textquoteright} commits; and (3) the bugginess of commits versus day-of-week varies for different software projects.},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985464},
	author = {Tan, Lin and Lam, Patrick and Eyolfson, Jon}
}
@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}
}
@article {1321,
	title = {Factors Affecting the Development of Absorptive Capacity in the Adoption of Open Source Software},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {17 - 38},
	abstract = {Previous research has shown that the knowledge that is available to an organization is an important factor influencing the adoption of open source software (OSS). Hence, it is important that organizations develop their absorptive capacity in order to successfully adopt OSS. Absorptive capacity refers to the ability of an organization to acquire, assimilate, and exploit new knowledge. However, no study has specifically investigated how organizations can develop their absorptive capacity by acquiring knowledge about OSS. This paper addresses this gap in research by investigating the organizational knowledge assimilation process within the context of the adoption of OSS. Based on a case study conducted at the Flemish government, a framework that is grounded in literature and that illustrates which contextual factors influence the development of absorptive capacity in the context of the adoption of OSS was developed.},
	keywords = {adoption, government},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011010102},
	author = {Ven, Kris and De Bruyn, Peter}
}
@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}
}
@proceedings {1270,
	title = {Impact of Stakeholder Type and Collaboration on Issue Resolution Time in OSS Projects},
	year = {2011},
	note = {"First, we characterize the difference in the average amount of resolved issues and issue resolution time between a volunteer assignee and a firm-paid assignee....Second, we investigate collaboration among stakeholders in OSS projects by using Social network metrics and analysis. Last, we explore the impact of the collaboration measures on issue resolution time."

"Three OSS projects were selected for our study, namely Qt, Qpid and Geronimo"

"All software issues were collected from JIRA repositories...Issue resolution time was computed by using the created time field and the issue resolved time field."},
	month = {10/2011},
	pages = {1-16},
	publisher = {Springer},
	abstract = {Initialized by a collective contribution of volunteer developers, Open source software (OSS) attracts an increasing involvement of commercial firms. Many OSS projects are composed of a mix group of firm-paid and volunteer developers, with different motivations, collaboration practices and working styles. As OSS development consists of collaborative works in nature, it is important to know whether these differences have an impact on collaboration between difference types of stakeholders, which lead to an influence in the project outcomes. In this paper, we empirically investigate the firm-paid participation in resolving OSS evolution issues, the stakeholder collaboration and its impact on OSS issue resolution time. The results suggest that though a firm-paid assigned developer resolves much more issues than a volunteer developer does, there is no difference in issue resolution time between them. Besides, the more important factor that influences the issue resolution time comes from the collaboration among stakeholders rather than from individual characteristics.},
	keywords = {COLLABORATION, companies, coordination, defects, feature requests, geronimo, jira, qpid, qt, social network analysis, volunteer},
	author = {Duc, Ach Nguyen and Cruzes, Daniela S. and Ayala, Claudia and Conradi, Reidar}
}
@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}
}
@conference {1308,
	title = {Social interactions around cross-system bug fixings},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"We rely on information stored in versioning database and mailing lists of both systems and develop methods to reconstruct and integrate different historical database"},
	month = {05/2011},
	pages = {143-152},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Cross-system bug fixing propagation is frequent among systems having similar characteristics, using a common framework, or, in general, systems with cloned source code fragments. While previous studies showed that clones tend to be properly maintained within a single system, very little is known about cross-system bug management.

This paper describes an approach to mine explicitly documented cross-system bug fixings, and to relate their occurrences to social characteristics of contributors discussing through the project mailing lists--e.g., degree, betweenness, and brokerage--as well as to the contributors{\textquoteright} activity on source code.

The paper reports results of an empirical study carried out on FreeBSD and OpenBSD kernels. The study shows that the phenomenon of cross-system bug fixing between these two projects occurs often, despite the limited overlap of contributors. The study also shows that cross-system bug fixings mainly involve contributors with the highest degree, betweenness and brokerage level, as well as contributors that change the source code more than others.},
	keywords = {bug fixing, bug tracking system, committers, email, email archives, freebsd, mailing list, openbsd},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985463},
	author = {Cerulo, Luigi and Cimitile, Marta and Di Penta, Massimiliano and Canfora, Gerardo}
}
@proceedings {1294,
	title = {Something of a Potemkin Village? Acid2 and Mozilla{\textquoteright}s Efforts to Comply with HTML4},
	year = {2011},
	month = {10/2011},
	pages = {320-324},
	publisher = {Springer},
	abstract = {The real point here is that the Acid3 test isn{\textquoteright}t a broad-spectrum standards-support test. It{\textquoteright}s a showpiece, and something of a Potemkin village at that. Which is a shame, because what{\textquoteright}s really needed right now is exhaustive test suites for specifications{\textemdash} XHTML, CSS, DOM, SVG.},
	author = {den Besten, Matthijs and Jean-Michel Dalle}
}
@conference {1303,
	title = {A study of language usage evolution in open source software},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {13-22},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Waikiki, Honolulu, HI, USA},
	abstract = {The use of programming languages such as Java and C in Open Source Software (OSS) has been well studied. However, many other popular languages such as XSL or XML have received minor attention. In this paper, we discuss some trends in OSS development that we observed when considering multiple programming language evolution of OSS. Based on the revision data of 22 OSS projects, we tracked the evolution of language usage and other artefacts such as documentation files, binaries and graphics files. In these systems several different languages and artefact types including C/C++, Java, XML, XSL, Makefile, Groovy, HTML, Shell scripts, CSS, Graphics files, JavaScript, JSP, Ruby, Phyton, XQuery, OpenDocument files, PHP, etc. have been used. We found that the amount of code written in different languages differs substantially. Some of our findings can be summarized as follows: (1) JavaScript and CSS files most often co-evolve with XSL; (2) Most Java developers but only every second C/C++ developer work with XML; (3) and more generally, we observed a significant increase of usage of XML and XSL during recent years and found that Java or C are hardly ever the only language used by a developer. In fact, a developer works with more than 5 different artefact types (or 4 different languages) in a project on average.},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985447},
	author = {Gall, Harald and Karus, Siim}
}
@conference {1310,
	title = {System compatibility analysis of Eclipse and Netbeans based on bug data},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {230-233},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Waikiki, Honolulu, HI, USANew York, New York, USA},
	abstract = {Eclipse and Netbeans are two top of the line Integrated Development Environments (IDEs) for Java development. Both of them provide support for a wide variety of development tasks and have a large user base. This paper provides an analysis and comparison for the compatibility and stability of Eclipse and Netbeans on the three most commonly used operating systems, Windows, Linux and Mac OS. Both IDEs are programmed in Java and use a Bugzilla issue tracker to track reported bugs and feature requests. We looked into the Bugzilla repository databases of these two IDEs, which contains the bug records and histories of these two IDEs. We used some basic data mining techniques to analyze some historical statistics of the bug data. Based on the analysis, we try to answer certain stability-comparison oriented questions in the paper, so that users can have a better idea which of these two IDEs is designed better to work on different platforms.

},
	keywords = {bug tracking system, bugzilla, eclipse, ms challenge, netbeans, version history},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985479},
	author = {Baik, Eilwoo and Devanbu, Premkar and Wang, Xinlei (Oscar)}
}
@conference {1312,
	title = {A tale of two browsers},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {238-241},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {We explore the space of open source systems and their user communities by examining the development artifact histories of two popular web browsers -- Firefox and Chrome -- as well as usage data. By examining the data and addressing a number of research questions, two very different profiles emerge: Firefox, as the older and established system, with long product version cycles but short bug fix cycles, and a user base that is slow to adopt newer versions; and Chrome, as the new and fast evolving system, with short version cycles, longer bug fix cycles, and a user base that very quickly adopts new versions as they become available (due largely to Chrome{\textquoteright}s mandatory automatic updates).

},
	keywords = {chrome, development history, Firefox, msr challenge},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985481},
	author = {Davis, Ian and Godfrey, Michael W. and Baysal, Olga}
}
@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}
}
@conference {1311,
	title = {What topics do Firefox and Chrome contributors discuss?},
	booktitle = {Proceedings of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	month = {05/2011},
	pages = {234-237},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Firefox and Chrome are two very popular open source Web browsers, implemented in C/C++. This paper analyzes what topics were discussed in Firefox and Chrome bug reports over time. To this aim, we indexed the text contained in bug reports submitted each semester of the project history, and identified topics using Latent Dirichlet Allocation (LDA). Then, we investigated to what extent Firefox and Chrome developers/contributors discussed similar topics, either in different periods, or over the same period. Results indicate a non-negligible overlap of topics, mainly on issues related to page layouting, user interaction, and multimedia contents.},
	keywords = {bug reports, chrome, Firefox, LDA, msr challenge},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985480},
	author = {Zagarese, Quirino and Distante, Damiano and Di Penta, Massimiliano and Bernardi, Mario Luca and Sementa, Carmine}
}
@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}
}
@conference {954,
	title = {Clones: What is that smell?},
	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 = {72 - 81},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Clones are generally considered bad programming practice in software engineering folklore. They are identified as a bad smell and a major contributor to project maintenance difficulties. Clones inherently cause code bloat, thus increasing project size and maintenance costs. In this work, we try to validate the conventional wisdom empirically to see whether cloning makes code more defect prone. This paper analyses relationship between cloning and defect proneness. We find that, first, the great majority of bugs are not significantly associated with clones. Second, we find that clones may be less defect prone than non-cloned code. Finally, we find little evidence that clones with more copies are actually more error prone. Our findings do not support the claim that clones are really a "bad smell". Perhaps we can clone, and breathe easy, at the same time.},
	keywords = {apache, bug fix revisions, bugs, clone, evolution, gimp, nautilus, scm, source code},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463343},
	attachments = {https://flosshub.org/sites/flosshub.org/files/72rahman2010cws.pdf},
	author = {Rahman, Foyzur and Christian Bird and Devanbu, Premkumar}
}
@conference {1483,
	title = {Creating and evolving developer documentation},
	booktitle = {Proceedings of the eighteenth ACM SIGSOFT international symposium},
	year = {2010},
	pages = {127},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Santa Fe, New Mexico, USANew York, New York, USA},
	abstract = {Developer documentation helps developers learn frameworks and libraries. To better understand how documentation in open source projects is created and maintained, we performed a qualitative study in which we interviewed core contributors who wrote developer documentation and developers who read documentation. In addition, we studied the evolution of 19 documents by analyzing more than 1500 document revisions. We identified the decisions that contributors make, the factors influencing these decisions and the consequences for the project. Among many findings, we observed how working on the documentation could improve the code quality and how constant interaction with the projects{\textquoteright} community positively impacted the documentation.},
	isbn = {9781605587912},
	doi = {10.1145/1882291.1882312},
	author = {Dagenais, Barth{\'e}l{\'e}my and Robillard, Martin P.}
}
@conference {1258,
	title = {Exploring Complexity in Open Source Software: Evolutionary Patterns, Antecedents, and Outcomes},
	booktitle = {2010 43rd Hawaii International Conference on System Sciences (HICSS 2010)},
	year = {2010},
	note = {"The sample of projects was drawn from SourceForge"
"projects were selected that were built with C++."
"Applying the selection criteria generated a total of 108 projects for analysis"
"Scientific Toolwork{\textquoteright}s Understand (version 1.4)"},
	pages = {1 - 11},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Honolulu, Hawaii, USA},
	abstract = {Software complexity is important to researchers and managers, yet much is unknown about how complexity evolves over the life of a software application and whether different dimensions of software complexity may exhibit similar or different evolutionary patterns. Using cross-sectional and longitudinal data on a sample of 108 open source projects, this research investigated how the complexity of open source project releases varied throughout the life of the project. Functional data analysis was applied to the release histories of the projects and recurring evolutionary patterns were derived. There were projects that saw little evolution, according to their measures of size and structural complexity. However, projects that displayed some evolution often differed on the pattern of evolution depending on whether size or structural complexity was examined. Factors that contribute to and result from the patterns of complexity were evaluated, and implications for research and practice are presented.},
	keywords = {complexity, evolution, fda, life cycle, sourceforge, srda},
	isbn = {978-1-4244-5509-6},
	doi = {10.1109/HICSS.2010.198},
	attachments = {https://flosshub.org/sites/flosshub.org/files/10-07-02.pdf},
	author = {Darcy, David P. and Daniel, Sherae L. and Stewart, Katherine J.}
}
@conference {950,
	title = {An extensive comparison of bug prediction approaches},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {31 - 41},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Reliably predicting software defects is one of software engineering{\textquoteright}s holy grails. Researchers have devised and implemented a plethora of bug prediction approaches varying in terms of accuracy, complexity and the input data they require. However, the absence of an established benchmark makes it hard, if not impossible, to compare approaches. We present a benchmark for defect prediction, in the form of a publicly available data set consisting of several software systems, and provide an extensive comparison of the explanative and predictive power of well-known bug prediction approaches, together with novel approaches we devised. Based on the results, we discuss the performance and stability of the approaches with respect to our benchmark and deduce a number of insights on bug prediction models.},
	keywords = {apache, bug reports, eclipse, famix, lucene, mylyn, prediction, scm},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463279},
	attachments = {https://flosshub.org/sites/flosshub.org/files/31dambrosLanzaRobbes31.pdf},
	author = {D{\textquoteright}Ambros, Marco and Lanza, Michele and Robbes, Romain}
}
@conference {1358,
	title = {Extracting source code from e-mails},
	booktitle = {Proceedings of ICPC 2010 (18th IEEE International Conference on Program Comprehension)},
	year = {2010},
	note = {"We want to extract source code fragments from e-mail messages. To do this, we first need to select e-mails that contain source code fragments, and then we extract such fragments from the content in which they are enclosed."

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

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

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

In this work we focus both on classifying e-mails that hold fragments of the source code of a system, and on extracting the source code pieces inside the e-mail. We devised and analyzed a number of lightweight techniques to accomplish these tasks. To assess the validity of our techniques, we manually inspected and annotated a statistically significant number of e-mails from five unrelated open source software systems written in Java. With such a benchmark in place, we measured the effectiveness of each technique in terms of precision and recall.},
	keywords = {argouml, email, freenet, jmeter, mailing lists, mina, natural language, openjpa, source code},
	url = {http://www.inf.usi.ch/phd/bacchelli/publications.php},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icpc2010.pdf},
	author = {Bacchelli, Alberto and D{\textquoteright}Ambros, Marco and Lanza, Michele}
}
@conference {965,
	title = {Identifying licensing of jar archives using a code-search approach},
	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 = {151 - 160},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Free and open source software strongly promotes the reuse of source code. Some open source Java components/libraries are distributed as jar archives only containing the bytecode and some additional information. For whoever wanting to integrate this jar in her own project, it is important to determine the license(s) of the code from which the jar archive was produced, as this affects the way that such component can be used. This paper proposes an automatic approach to determine the license of jar archives, combining the use of a code-search engine with the automatic classification of licenses contained in textual flies enclosed in the jar. Results of an empirical study performed on 37 jars - from 17 different systems - indicate that this approach is able to successfully infer the jar licenses in over 95\% of the cases, but that in many cases the license in textual flies may differ from the one of the classes contained in the jar.},
	keywords = {apache, bytecode, classification, eclipse, google code, jar, java, licenses, source code},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463282},
	attachments = {https://flosshub.org/sites/flosshub.org/files/151msr2010.pdf},
	author = {Di Penta, Massimiliano and Daniel M. German and Antoniol, Giuliano}
}
@proceedings {1380,
	title = {The Impact of Person-Organization Fit on Turnover in Open Source Software Projects},
	number = {13},
	year = {2010},
	abstract = {Participant turnover in open source software development is a critical problem. Using Schneider{\textquoteright}s (1987) Attraction Selection and Attrition Framework and the notion of Person- Organization fit, we hypothesize about the relationship between a participant{\textquoteright}s fit with an open source project and turnover. Specifically we predict that value fit, needs-supplies fit and demandsabilities fit between a participant and a particular project will have a negative association with participant turnover and that the role of the participant in the project acts a moderator. An empirical study is designed to examine the hypotheses using a combination of survey and archival data. Since for-profit companies are increasingly leveraging open source software development, implications of our findings will be useful for project managers seeking to retain talented contributors in the absence of financial compensation.},
	url = {http://aisel.aisnet.org/icis2010_submissions/13},
	author = {Sharma, P.N. and Daniel, Sherae L. and Chung, Ting-Ting (Rachel)}
}
@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.}
}
@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 {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 {955,
	title = {Perspectives on bugs in the Debian bug tracking system},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {86 - 89},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Bugs in Debian differ from regular software bugs. They are usually associated with packages, instead of software modules. They are caused and fixed by source package uploads instead of code commits. The majority are reported by individuals who appear in the bug database once, and only once. There also exists a small group of bug reporters with over 1,000 bug reports each to their name. We also explore our idea that a high bug-frequency for an individual package might be an indicator of popularity instead of poor quality.},
	keywords = {bug reports, debian, msr challenge, popularity},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463288},
	attachments = {https://flosshub.org/sites/flosshub.org/files/86bugs-debian.pdf},
	author = {Davies, Julius and Hanyu Zhang and Nussbaum, Lucas and Daniel M. German}
}
@conference {949,
	title = {Predicting the severity of a reported bug},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {The severity of a reported bug is a critical factor in deciding how soon it needs to be fixed. Unfortunately, while clear guidelines exist on how to assign the severity of a bug, it remains an inherent manual process left to the person reporting the bug. In this paper we investigate whether we can accurately predict the severity of a reported bug by analyzing its textual description using text mining algorithms. Based on three cases drawn from the open-source community (Mozilla, Eclipse and GNOME), we conclude that given a training set of sufficient size (approximately 500 reports per severity), it is possible to predict the severity with a reasonable accuracy (both precision and recall vary between 0.65-0.75 with Mozilla and Eclipse; 0.70-0.85 in the case of GNOME).},
	keywords = {bug reports, eclipse, gnome, mozilla, severity, text mining},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463284},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1lamkanfiDemeyer1.pdf},
	author = {Lamkanfi, Ahmed and Demeyer, Serge and Giger, Emanuel and Goethals, Bart}
}
@article {1376,
	title = {Sustainability of Open-Source Projects: A Longitudinal Study},
	journal = {Journal of the Association for Information Systems},
	volume = {11},
	number = {5},
	year = {2010},
	abstract = {This paper examines the factors that influence the long-term sustainability of FLOSS projects. A model of project sustainability based on organizational ecology is developed and tested empirically. Data about activity and contribution patterns over the course of five years for 2,772 projects registered with SourceForge is analyzed. Our results suggest that the size of the project{\textquoteright}s development base, project age and the size of niche occupied by the project are positively related to the project{\textquoteright}s ability to attract user and/or developer resources. The ability to attract resources is an indicator of the perceived project legitimacy, which in turn is a strong predictor of the project{\textquoteright}s future sustainability. Thus a project{\textquoteright}s ability to attract developer and user resources is shown to play a mediating role between the demographic (size and age) and ecological (niche) characteristics of the project and its future sustainability. Our results support the applicability of tenets of organizational ecology related to the liability of smallness, the liability of newness, and population characteristics (niche size) to the FLOSS development environment. The implications of the results for future research and practice are discussed.},
	keywords = {contribution, developers, sourceforge, sustainability},
	url = {http://aisel.aisnet.org/jais/vol11/iss11/5/},
	author = {Chengular-Smith, I. and Sidorova, Anna and Daniel, Sherae L.}
}
@conference {969,
	title = {Validity of network analyses in Open Source Projects},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	note = {"We have mined archival records of developer mailing lists to generate reply-to social networks for the three OSS projects: Apache, MySQL, and Perl."

"For each of these projects, we construct an information flow network based on messages that are sent as replies to previous messages....We use this methodology on all mined data to create a network of mailing list participants. "},
	pages = {201 - 209},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Social network methods are frequently used to analyze networks derived from Open Source Project communication and collaboration data. Such studies typically discover patterns in the information flow between contributors or contributions in these projects. Social network metrics have also been used to predict defect occurrence. However, such studies often ignore or side-step the issue of whether (and in what way) the metrics and networks of study are influenced by inadequate or missing data. In previous studies email archives of OSS projects have provided a useful trace of the communication and co-ordination activities of the participants. These traces have been used to construct social networks that are then subject to various types of analysis. However, during the construction of these networks, some assumptions are made, that may not always hold; this leads to incomplete, and sometimes incorrect networks. The question then becomes, do these errors affect the validity of the ensuing analysis? In this paper we specifically examine the stability of network metrics in the presence of inadequate and missing data. The issues that we study are: 1) the effect of paths with broken information flow (i.e. consecutive edges which are out of temporal order) on measures of centrality of nodes in the network, and 2) the effect of missing links on such measures. We demonstrate on three different OSS projects that while these issues do change network topology, the metrics used in the analysis are stable with respect to such changes.},
	keywords = {apache, email archives, mailing lists, missing data, mysql, perl, social networks},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463342},
	attachments = {https://flosshub.org/sites/flosshub.org/files/201NetworkAnalysis.pdf},
	author = {Nia, Roozbeh and Christian Bird and Devanbu, Premkumar and Filkov, Vladimir}
}
@article {1239,
	title = {Weaving a Semantic Web Across OSS Repositories},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	month = {32/2010},
	pages = {29 - 40},
	abstract = {Several public repositories and archives of {\textquotedblleft}facts{\textquotedblright} about libre software projects, maintained either by open source communities or by research communities, have been flourishing over the Web in recent years. These have enabled new analysis and support for new quality assurance tasks. This paper presents some complementary existing tools, projects and models proposed both by OSS actors or research initiatives that are likely to lead to useful future developments in terms of study of the FLOSS phenomenon, and also to the very practitioners in the FLOSS development projects. A goal of the research conducted within the HELIOS project is to address bugs traceability issues. In this regard, the authors investigate the potential of using Semantic Web technologies in navigating between many different bugtracker systems scattered all over the open source ecosystem. By using Semantic Web techniques, it is possible to interconnect the databases containing data about open-source software projects development, which enables OSS partakers to identify resources, annotate them, and further interlink those using dedicated properties and collectively designing a distributed semantic graph.},
	keywords = {archive, bug, bugtracker, database, debian, forge, interoperability, ontology, OSLC-CM, RDF, repository of repositories, semantic, semantic Web},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010040103},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd2009-olivier-berger.pdf},
	author = {Olivier Berger and Valentin Vlasceanu and Christian Bac and Quang Vu Dang and Lauriere, St{\'e}phane}
}
@conference {606,
	title = {Assessing FLOSS Communities: An Experience Report from the QualOSS Project},
	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 = {364 - 364},
	publisher = {Springer},
	organization = {Springer},
	chapter = {38},
	abstract = {This paper presents work done in the QualOSS (Quality of Open Source Software) research project,which aims at building a methodology and tools to help in the assessment of the quality of FLOSS (free, libre, open source software) endeavors. In particular, we introduce the research done to evaluate the FLOSS endeavor communities. Following the Goal-Question-Metric paradigm, QUALOSS describes goals, the associated questions and then metrics that allow to answer the questions.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_38},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Assessing\%20FLOSS\%20Communities.pdf},
	author = {Izquierdo-Cortazar, Daniel and Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s and Deprez, Jean-Christophe}
}
@conference {605,
	title = {Assurance Evaluation for OSS Adoption in a Telco Context},
	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 = {363 - 363},
	publisher = {Springer},
	organization = {Springer},
	chapter = {37},
	abstract = {Software Assurance (SwA) is a complex concept that involves different stages of a software development process and may be defined differently depending on its focus, as for instance software quality, security, or dependability. In Computer Science, the term assurance is referred to all activities necessary to provide enough confidence that a software product will satisfy its users{\textquoteright} functional and non-functional requirements.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Assurance\%20Evaluation\%20for\%20OSS.pdf},
	author = {Ardagna, Claudio and Banzi, Massimo and Damiani, Ernesto and El Ioini, Nabil and Frati, Fulvio}
}
@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 {1360,
	title = {Benchmarking Lightweight Techniques to Link E-Mails and Source Code},
	booktitle = {2009 16th Working Conference on Reverse Engineering},
	year = {2009},
	note = {"We present different lightweight approaches that, exploiting the specific characteristics of e-mails and the ones of the source code, are capable of establishing a bi-directional link between source code entities and e-mails"

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

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

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

To overcome this issue, we manually inspected a statistically significant number of e-mails pertaining to the ArgoUML system. Based on this benchmark, we present a variety of lightweight techniques to assign e-mails to software artifacts and measure their effectiveness in terms of precision and recall.},
	keywords = {argouml, email, mailing lists},
	isbn = {978-0-7695-3867-9},
	doi = {10.1109/WCRE.2009.44},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wcre2009.pdf},
	author = {Bacchelli, Alberto and D{\textquoteright}Ambros, Marco and Lanza, Michele and Robbes, Romain}
}
@conference {929,
	title = {Code siblings: Technical and legal implications of copying code between 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 = {81 - 90},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Source code cloning does not happen within a single system only. It can also occur between one system and another. We use the term code sibling to refer to a code clone that evolves in a different system than the code from which it originates. Code siblings can only occur when the source code copyright owner allows it and when the conditions imposed by such license are not incompatible with the license of the destination system. In some situations copying of source code fragments are allowed - legally - in one direction, but not in the other. In this paper, we use clone detection, license mining and classification, and change history techniques to understand how code siblings - under different licenses - flow in one direction or the other between Linux and two BSD Unixes, FreeBSD and OpenBSD. Our results show that, in most cases, this migration appears to happen according to the terms of the license of the original code being copied, favoring always copying from less restrictive licenses towards more restrictive ones. We also discovered that sometimes code is inserted to the kernels from an outside source.},
	keywords = {bsd, fossology, freebsd, linux, openbsd, source code},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069483},
	attachments = {https://flosshub.org/sites/flosshub.org/files/81CodeSiblings.pdf},
	author = {Daniel M. German and Di Penta, Massimiliano and Gueheneuc, Yann-Gael and Antoniol, Giuliano}
}
@article {1343,
	title = {A Framework for Understanding the Open Source Revolution},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {1 - 16},
	abstract = {Traditional software engineering methodologies have mostly evolved from the environment of proprietary, large-scale software systems. Here, software design principles operate within a hierarchical decision-making context. Development of banking, enterprise resource and complex weapons systems all fit this paradigm. However, another paradigm for developing software-intensive systems has emerged, the paradigm of open source software. Although from a traditional perspective open source projects might look like chaos, their real-world results have been spectacular. This chapter presents open source software development as a fundamentally new paradigm driven by economics and facilitated by new processes. The new paradigm{\textquoteright}s revolutionary aspects are explored, a framework for describing the massive impact brought about by the new paradigm is proposed, and directions of future research are outlined. The proposed framework{\textquoteright}s goals are to help the understanding of the open source paradigm as a new economic revolution and stimulate research in designing open source software.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009070101},
	author = {Elpern, Jeff and Dascalu, Sergiu}
}
@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.}
}
@proceedings {1645,
	title = {Mining Programming Language Vocabularies from Source Code},
	year = {2009},
	pages = {12 pp},
	abstract = {We can learn much from the artifacts produced as the by-products of software devel- opment and stored in software repositories. Of all such potential data sources, one of the most important from the perspective of program comprehension is the source code itself. While other data sources give insight into what developers intend a program to do, the source code is the most accurate human-accessible description of what it will do. However, the ability of an individual developer to comprehend a particular source file depends directly on his or her familiarity with the specific features of the programming language being used in the file. This is not unlike the difficulties second-language learners may encounter when attempting to read a text written in a new language. We propose that by applying the techniques used by corpus linguists in the study of natural language texts to a corpus of programming language texts (i.e., source code repositories), we can gain new insights into the communication medium that is programming language. In this paper we lay the foundation for applying corpus linguistic methods to programming language by 1) defining the term {\textquotedblleft}word{\textquotedblright} for programming language, 2) developing data collection tools and a data storage schema for the Java programming language, and 3) presenting an initial analysis of an example linguistic corpus based on version 1.5 of the Java Developers Kit.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/21st-delorey.pdf},
	author = {Delorey, Daniel P. and Knutson, Charles D. and Davies, Mark}
}
@article {1342,
	title = {Open Source and Commercial Software Platforms},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	pages = {67 - 80},
	abstract = {In this article, we consider the dynamics and competition between two software platforms (Open Source and proprietary software). Potential user-developers can adopt one of the two platforms in order to develop and sell new applications based on the platform. We consider the static issue first and then use a simple dynamic system where the dynamics comes from the development efforts (spillovers) made on each platforms. In this context, we first identify the conditions for the two platforms to coexist in the long run. From this baseline, we then consider different strategies for the editor. A first strategy is for the editor to {\textquotedblleft}show the code{\textquotedblright} of its software, so as to develop more compatible products. A second strategy is to strategically monitor the compatibility degree between the proprietary and OS platform. In both cases, we analyze whether a mixed industry may be sustainable in the long run.},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009040105},
	author = {Darmon, Eric and Torre, Dominique}
}
@article {Barcellini2009533,
	title = {Participation in online interaction spaces: Design-use mediation in an Open Source Software community},
	journal = {International Journal of Industrial Ergonomics},
	volume = {39},
	number = {3},
	year = {2009},
	note = {<ce:title>Selected papers from ECCE 2007, the 25th Anniversary Conference of the European Conference on Cognitive Ergonomics</ce:title>},
	pages = {533 - 540},
	abstract = {This research aims at characterizing emerging roles fostering design-use mediation during the Open Source Software (OSS) design process through the analysis of participation. Studying OSS is of particular interest: (1) to investigate socio-technical settings supporting user participation to the design process, which is considered to be the major strength of OSS design; (2) to gain insights into supporting the changing nature of the software industry, which is becoming more and more distributed and global, and which is thus increasingly making use of OSS design tools and methods. In this research, we characterized effective roles of participants, i.e. participation, on the basis of activities analysis in three online interaction spaces (discussion, documentation and implementation) during a continuous {\textquotedblleft}pushed-by-users{\textquotedblright} design process of the Python project. Participation is targeted through a methodology articulating: (1) structural analyses (organization of the discussions, regularity and involvement of participants, quotes-based social network) in usage-oriented and development-oriented mailing lists of the projects{\textquoteright} discussion space; (2) actions to the code and documentation made by participants in the implementation and documentation spaces. Besides the importance of the users{\textquoteright} contribution to the process, OSS design is fostered by some key-participants, the cross-participants, who act as boundary spanners between the developers and the users, helping them to go beyond some barriers to participation. These findings can be reinforced developing software to automate the structural analysis of discussions and actions to the code and documentation.},
	keywords = {Distributed participatory design},
	issn = {0169-8141},
	doi = {10.1016/j.ergon.2008.10.013},
	url = {http://www.sciencedirect.com/science/article/pii/S0169814108001637},
	author = {Barcellini, Flore and D{\'e}tienne, Fran{\c c}oise and Burkhardt, Jean-Marie}
}
@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 {DBLP:conf/msr/BirdRBHGD09,
	title = {The promises and perils of mining git},
	booktitle = {Proceedings of the 6th International Working Conference on Mining Software Repositories, MSR 2009},
	year = {2009},
	pages = {1-10},
	abstract = {We are now witnessing the rapid growth of decentralized source code management (DSCM) systems, in which every developer has her own repository. DSCMs facilitate a style of collaboration in which work output can flow sideways (and privately) between collaborators, rather than always up and down (and publicly) via a central repository. Decentralization comes with both the promise of new data and the peril of its misinterpretation. We focus on git, a very popular DSCM used in high-profile projects. Decentralization, and other features of git, such as automatically recorded contributor attribution, lead to richer content histories, giving rise to new questions such as "How do contributions flow between developers to the official project repository?" However, there are pitfalls. Commits may be reordered, deleted, or edited as they move between repositories. The semantics of terms common to SCMs and DSCMs sometimes differ markedly, potentially creating confusion. For example, a commit is immediately visible to all developers in centralized SCMs, but not in DSCMs. Our goal is to help researchers interested in DSCMs avoid these and other perils when mining and analyzing git data.},
	keywords = {dscm, git, mining, scm, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1promisePeril.pdf},
	author = {Christian Bird and Peter C. Rigby and Earl T. Barr and David J. Hamilton and Daniel M. Germ{\'a}n and Premkumar T. Devanbu}
}
@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 {H{\"a}rtig09roitzsch:the,
	title = {Roitzsch: The Mathematics of Obscurity: On the Trustworthiness of Open Source},
	booktitle = {9th Workshop on the Economics of Information Security (WEIS)},
	year = {2009},
	pages = {2016{\textendash}2023},
	publisher = {ACM},
	organization = {ACM},
	abstract = {It is more difficult to find errors when source code is secret.
More people search for errors when source code is
public. These counteracting effects are pivotal to the question
whether openness fosters security. Errors in software
are found by people with either constructive contribution or
exploitation in mind. Focusing exclusively on this discovery
aspect, we present a probabilistic model, which allows us to
compare the open source and closed source situations.
We start out with our assumptions explained using a simple
introductory model. We then extend this to what we
believe to be an adequate model of a bug-hunting process
conducted by multiple competing parties. The model employs
an asymmetric race paradigm. One of the surprising
results is that even an arbitrarily large group with good intentions
cannot safely dominate the evil attackers. Instead,
they are limited by a significant upper bound in their winning
chances.},
	url = {http://www.econinfosec.org/archive/weis2010/papers/session6/weis2010_haertig.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/weis2010_haertig.pdf},
	author = {Hermann H{\"a}rtig and Claude-joachim Hamann and Michael Roitzsch and Technische Universit{\"a}t Dresden}
}
@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 {1807,
	title = {Supporting Situation Awareness in FLOSS Projects by Semantical Aggregation of Tools Feeds},
	booktitle = {Internet-Based Systems (SITIS 2009)2009 Fifth International Conference on Signal Image Technology and Internet Based Systems},
	year = {2009},
	note = {"The FLOSSmole  project provides public data about FLOSSdevelopment for academic research. It includes data and analysisfrom SourceForge, Freshmeat, RubyForge, ObjectWeb"},
	pages = {423 - 429},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Marakesh, Morocco},
	abstract = {It is rather difficult to monitor or visualize what can be the contribution of a member in a collaboration project, especially when the project uses multiple tools to produce its results. This is the case for collaborative development of FLOSS software, that uses Wiki, bug tracker, mailing lists and source code management tools. This paper presents an approach to data collection by using aggregation of feeds published by the different tools of a software forge. To allow this aggregation, collected data is semantically reformatted into Semantic Web standards: RDF, DC, DOAP, FOAF and EvoOnt. Resulting data can then be processed, re-published or displayed to project members. This approach was used to implement a supervision module that is integrated into the PicoForge platform. This module is able to draw a live graph of the social community out of the different sources of data, and in turn exports semantic feeds for other uses.},
	isbn = {978-1-4244-5740-3},
	doi = {10.1109/SITIS.2009.72},
	author = {Quang Vu Dang and Christian Bac and Olivier Berger and Valentin Vlasceanu}
}
@conference {597,
	title = {Using FLOSS Project Metadata in the Undergraduate Classroom},
	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 = {330 - 339},
	publisher = {Springer},
	organization = {Springer},
	chapter = {29},
	abstract = {This paper describes our efforts to use the large amounts of data available from public repositories of free, libre, and open source software (FLOSS) in our undergraduate classrooms to teach concepts that would have previously been taught using other types of data from other sources.
},
	keywords = {artificial intelligence, database, education, teaching, undergraduate, undergraduate research},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Using\%20FLOSS\%20Project\%20Metadata.pdf},
	author = {Squire, Megan and Duvall, Shannon}
}
@article {denBesten2008316,
	title = {The allocation of collaborative efforts in open-source software},
	journal = {Information Economics and Policy},
	volume = {20},
	number = {4},
	year = {2008},
	note = {"we have selected a set of 10 large open-source projects"
apache, cvs, gaim, gcc, ghostscript, mozilla, netbsd, openssh, postgresql, python
"Our data were extracted from logs of development activity generated by software version control systems. For each project in the selection, we extracted CVS development logs"
"We notably computed for each file in the sample, and for each month in its history, the number of distinct maintainers that had committed a change during that month, and the number of commits, the blocks of code addition, each file had received during that month."
"other variables used in the regressions are proxies for the size, age, and granularity of files; the size of a file is represented as its number of lines of code (LOCs), its age by its creation date (Youth), and its granularity by the number of functions it contains."},
	pages = {316 - 322},
	abstract = {The article investigates the allocation of collaborative efforts among core developers (maintainers) of open-source software by analyzing on-line development traces (logs) for a set of 10 large projects. Specifically, we investigate whether the division of labor within open-source projects is influenced by characteristics of software code. We suggest that the collaboration among maintainers tends to be influenced by different measures of code complexity. We interpret these findings by providing preliminary evidence that the organization of open-source software development would self-adapt to characteristics of the code base, in a {\textquoteright}stigmergic{\textquoteright} manner.},
	keywords = {age, apache, complexity, cvs, division of labor, functions, gaim, gcc, ghostscript, lines of code, loc, log files, mozilla, netbsd, openssh, postgresql, python, revision control, scm, size, source code, Stigmergy, version control},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.06.003},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4SSG4PN-1/2/88b3824c30a31c18929d8a5ca6d64f62},
	author = {den Besten, Matthijs and Jean-Michel Dalle and Galia, Fabrice}
}
@conference {1210,
	title = {Author Entropy: A Metric for Characterization  of Software Authorship Patterns},
	booktitle = {3rd Workshop on Public Data about Software Development (WoPDaSD 2008)},
	year = {2008},
	note = {used flossmole to get sample of SF developers},
	month = {2008},
	pages = {42-47},
	abstract = {We propose the concept of author entropy and describe how file-level entropy measures may be used to understand and characterize authorship patterns within individual files, as well as across an entire project. As a proof of concept, we compute author entropy for 28,955 files from 33 open-source projects. We explore patterns of author entropy, identify techniques for visualizing author entropy, and propose avenues for further study. },
	keywords = {developers, entropy, flossmole, sourceforge},
	attachments = {https://flosshub.org/sites/flosshub.org/files/entropy2008.pdf},
	author = {Taylor, Quinn C. and Stevenson, James E. and Delorey, Daniel P. and Knutson, Charles D.}
}
@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}
}
@booklet {511,
	title = {Competitive Implications of Software Open-Sourcing},
	year = {2008},
	month = {Aug},
	abstract = {This paper is concerned with the economic trade-offs associated with open-sourcing, the business strategy of releasing free open-source versions of commercial software products. The effect of the release of open-source versions on the customers{\textquoteright} perception of products is an important determinant of open-sourcing outcomes. We model open-sourcing as a strategic option for firms that compete in the market for software products. Of particular importance in our model is the effect of open-sourcing on customer values and the possibility for better customization offered by the open-source products. We show that open-sourcing can arise as an equilibrium outcome in our simple two-stage game. If the enhancement of customer values from open-sourcing is moderate or high, firms may find it optimal to release open-source versions of their products.},
	url = {http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1185374},
	author = {Jai Asundi and Octavian Carare and Kutsal Dogan}
}
@conference {504,
	title = {Continuous Integration in Open Source Software Development},
	booktitle = {Fourth International Conference on Open Source Software},
	year = {2008},
	month = {Sept},
	abstract = {Commercial software firms are increasingly using and contributing to open source software. Thus, they need to understand and work with open source software development processes. This paper investigates whether the practice of continuous integration of agile software development methods has had an impact on open source software projects. Using fine-granular data from more than 5000 active open source software projects we analyze the size of code contributions over a project{\textquoteright}s life-span. Code contribution size has stayed flat. We interpret this to mean that open source software development has not changed its code integration practices. In particular, within the limits of this study, we claim that the practice of continuous integration has not yet significantly influenced the behavior of open source software developers.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/oss-2008-continuous-integration-final.pdf},
	author = {Amit Deshpande and Dirk Riehle}
}
@conference {550,
	title = {Continuous Integration in Open Source 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 = {273 - 280},
	publisher = {Springer},
	organization = {Springer},
	chapter = {23},
	abstract = {Commercial software firms are increasingly using and contributing to open source software. Thus, they need to understand and work with open source software development processes. This paper investigates whether the practice of continuous integration of agile software development methods has had an impact on open source software projects. Using fine-granular data from more than 5000 active open source software projects we analyze the size of code contributions over a project{\textquoteright}s life-span. Code contribution size has stayed flat. We interpret this to mean that open source software development has not changed its code integration practices. In particular, within the limits of this study, we claim that the practice of continuous integration has not yet significantly influenced the behavior of open source software developers.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Continous\%20Integration.pdf},
	author = {Amit Deshpande and Dirk Riehle}
}
@conference {870,
	title = {Crafting the initial user experience to achieve community goals},
	booktitle = {ACM Conference on recommender Systems},
	year = {2008},
	publisher = {ACM},
	organization = {ACM},
	address = {Lausanne, Switzerland},
	isbn = {978-1-60558-093-7},
	author = {Drenner, S. and Sen, S. and Terveen, L.}
}
@article {1084,
	title = {Dynamics of innovation in an "open source" collaboration environment: lurking, laboring, and launching FLOSS projects on SourceForge},
	journal = {Industrial and Corporate Change},
	volume = {17},
	year = {2008},
	note = {"For the purposes of this study, we are able to draw upon micro-level data pertaining to the activities undertaken during the period between the beginning of September 2000 and December 2002 by the entire cohort of 222,835 individuals who had registered on SF.net during the 14 months from September 1, 2000 through October 26, 2001."
"The statistical analysis in this article is based upon an edited dataset (referred to here as the SFnetDataset) covering the SourceForge cohort of 222,835 individuals who registered on SF.net during the 14 months from September 1, 2000 through October 26, 2001."
They appear to be using their own dataset which is from 2000-2001 even though this paper is from 2008},
	month = {07/2008},
	pages = {647 - 710},
	abstract = {A systems analysis perspective is adopted to examine the critical properties of the Free/Libre/Open Source Software (FLOSS) mode of innovation, as reflected on the SourceForge platform (SF.net). This approach re-scales March{\textquoteright}s (1991) framework and applies it to characterize the {\textquotedblleft}innovation system{\textquotedblright} of a {\textquotedblleft}distributed organization{\textquotedblright} of interacting agents in a virtual collaboration environment, rather than to innovation within a firm. March (1991) views the process of innovation at the organizational level as the coupling of sub-processes of exploration and exploitation. Correspondingly, the innovation system of the virtual collaboration environment represented by SF.net is an emergent property of two {\textquotedblleft}coupled{\textquotedblright} processes: one involves the interactions among agents searching the locale for information and knowledge resources to use in designing novel software products (i.e., exploration), and the other involves the mobilization of individuals{\textquoteright} capabilities for application in the software development projects that become established on the platform (i.e., exploitation). The micro-dynamics of this system are studied empirically by constructing transition probability matrices representing the movements of 222,835 SF.net users among seven different activity states, which range from {\textquotedblleft}lurking{\textquotedblright} (not contributing or contributing to projects without becoming a member) to {\textquotedblleft}laboring{\textquotedblright} (joining one or more projects as members), and to {\textquotedblleft}launching{\textquotedblright} (founding one or more projects) within each successive 6-month interval. The estimated probabilities are found to form first-order Markov chains describing ergodic processes. This makes it possible the computation of the equilibrium distribution of agents among the states, thereby suppressing transient effects and revealing persisting patterns of project joining and project launching. The latter show the FLOSS innovation process on SF.net to be highly dissipative: a very large proportion of the registered {\textquotedblleft}developers{\textquotedblright} fail to become even minimally active on the platform. There is nevertheless an active core of mobile project joiners, and a (still smaller) core of project founders who persist in creating new projects. The structure of these groups{\textquoteright} interactions (as displayed within the 3-year period examined) is investigated in detail, and it is shown that it would be sufficient to sustain both the exploration and exploitation phases of the platform{\textquoteright}s global dynamics.},
	keywords = {contributors, core, developers, roles, SFnetDataset, sourceforge, users, virtual communities, virtual organization, virtual organizations},
	issn = {1464-3650},
	doi = {10.1093/icc/dtn026},
	author = {David, P. A. and Rullani, F.}
}
@conference {Alonso:2008:EIV:1370750.1370780,
	title = {Expertise identification and visualization from CVS},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {125{\textendash}128},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {As software evolves over time, the identification of expertise becomes an important problem. Component ownership and team awareness of such ownership are signals of solid project. Ownership and ownership awareness are also issues in open-source software (OSS) projects. Indeed, the membership in OSS projects is dynamic with team members arriving and leaving. In large open source projects, specialists who know the system very well are considered experts. How can one identify the experts in a project by mining a particular repository like the source code? Have they gotten help from other people?

We provide an approach using classification of the source code tree as a path to derive the expertise of the committers. Because committers may get help from other people, we also retrieve their contributors. We also provide a visualization that helps to further explore the repository via committers and categories. We present a prototype implementation that describes our research using the Apache HTTP Web server project as a case study.},
	keywords = {apache, classification, committers, components, contributors, expertise, expertise identification, repository, scm, source code},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370780},
	url = {http://doi.acm.org/10.1145/1370750.1370780},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p125-alonso.pdf},
	author = {Alonso, Omar and Premkumar T. Devanbu and Gertz, Michael}
}
@conference {558,
	title = {Facilitating Social Network Studies of FLOSS using the OSSNetwork Environment},
	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 = {343 - 350},
	publisher = {Springer},
	organization = {Springer},
	chapter = {31},
	abstract = {Open source projects are typical examples of successful distributed software development projects. Understanding how coordination in these projects takes place can provide important lessons to Software Engineering researchers and practitioners. This understanding has been achieved using different research methods, including, surveys, case studies and social network analysis. However, to conduct these studies each researcher needs to build his own infra-structure from the scratch, a time consuming and error-prone task. This paper aims to alleviate this problem by describing an environment, the OSSNetwork, which allows the automatic data collection of open source repositories. Data collected by the OSSNetwork is aimed to support the construction, visualization, and analysis of social networks. This environment is extensible, therefore facilitating empirical studies of open source projects.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_31},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Facilitating\%20Social\%20Network\%20Studies.pdf},
	author = {Balieiro, Marco and de J{\'u}nior, Samuel and De Souza, Cleidson}
}
@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}
}
@conference {flosswp1737,
	title = {Improving community awareness in software forges by semantical aggregation of tools feeds},
	booktitle = {3nd International Workshop on Public Data about Software Development (WoPDaSD 2008), Milano, Italy, September 2008},
	year = {2008},
	abstract = {It is rather difficult to monitor or visualize what can be the contribution of a member in a project, especially when the project uses multiple tools to produce its results. This is the case for collaborative development of FLOSS software, that use Wiki, bug tracker, mailing lists and source code management tools. This paper presents an approach to data collection by using aggregation of feeds published by the different tools of a software forge. To allow this aggregation, collected data is semantically reformatted into Semantic Web standards: RDF, DC, DOAP, and FOAF. Resulting data can then be processed, republished or displayed to project members. We implemented this approach in a supervision module that has been integrated into the PicoForge platform. This module is able do draw a live graph of the social community out of the different sources of data, and in turn export semantic feeds for other uses.},
	keywords = {community of practice, DOAF., FOAF, free and open source software development, public data, RDF, semantic Web, social filtering, social network analysis},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Paper4.pdf},
	author = {Quang Vu Dang and Christian Bac and Olivier Berger and Xuan Sang Dao}
}
@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}
}
@conference {530,
	title = {Mapping Linux Security Targets to Existing Test Suites},
	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 = {29 - 45},
	publisher = {Springer},
	organization = {Springer},
	chapter = {3},
	abstract = {The Common Criteria standard provides an infrastructure for evaluating security functions of IT products and for certifying that security policies claimed by product suppliers are correctly enforced by the security functions themselves. Certifying Open Source software (OSS) can pave the way to OSS adoption in a number of security-conscious application environments. Recent experiences in certifying Linux distributions has pointed out the problem of finding a mapping between descriptions of OSS security functions and existingtest suites developed independently, such as the Linux Test Project. In this paper, we describe a mechanism, based on matching techniques, which semiautomatically associates security functions to existing test suite such as the ones developed by Open Source communities.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Mapping\%20Linux\%20Security\%20Targets.pdf},
	author = {Ardagna, C. and Damiani, E. and Ioini, N. and Frati, F. and Giovannini, P. and Tchokpon, R.}
}
@conference {545,
	title = {Migration Discourse Structures: Escaping Microsoft{\textquoteright}s Desktop Path},
	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 = {223 - 235},
	publisher = {Springer},
	organization = {Springer},
	chapter = {18},
	abstract = {Most studies of FOSS organizational migration projects focus solely on technological and economical aspects, neglecting the importance of organizational discourse structures for migration decisions as well as success. In looking at the case of the municipality of Munich this paper uses structuration theory in combination with discourse analysis to explain why and how in this case actors were able to overcome strong barriers to migration in the field of desktop software.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Migration\%20Discourse\%20Structure.pdf},
	author = {Dobusch, Leonhard}
}
@conference {536,
	title = {Mining for Practices in Community Collections: Finds From Simple Wikipedia},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {105 - 120},
	publisher = {Springer},
	organization = {Springer},
	chapter = {9},
	abstract = {The challenges of commons based peer production are usually associated with the development of complex software projects such as Linux and Apache. But the case of open content production should not be treated as a trivial one. For instance, while the task of maintaining a collection of encyclopedic articles might seem negligible compared to the one of keeping together a software system with its many modules and interdependencies, it still poses quite demanding problems. In this paper, we describe the methods and practices adopted by Simple Wikipedia to keep its articles easy to read. Based on measurements of article readability and similarity, we conclude that while the mechanisms adopted by the community had some effect, in the long run more efforts and new practices might be necessary in order to maintain an acceptable level of readability in the Simple Wikipedia collection.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_9},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Mining\%20for\%20Practices.pdf},
	author = {den Besten, Matthijs and Rossi, Alessandro and Gaio, Loris and Loubser, Max and Jean-Michel Dalle}
}
@inbook {868,
	title = {Movement Ideology vs. User Pragmatism in the Organizational Adoption of Open Source Software},
	booktitle = {Computerization Movements and Technology Diffusion: From Mainframes to Ubiquitous Computing},
	year = {2008},
	pages = {427-452},
	publisher = {Information Today},
	organization = {Information Today},
	address = {Medford, NJ},
	author = {Dedrick, Jason and Joel West},
	editor = {Kraemer, Kenneth L. and Elliott, Margaret}
}
@conference {568,
	title = {Open Source Environments for Collaborative Experiments in e-Science},
	booktitle = {OSS2008: Open Source Development, Communities and Quality (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	volume = {275/2008},
	year = {2008},
	month = {2008///},
	pages = {415 - 416},
	publisher = {Springer},
	organization = {Springer},
	chapter = {41},
	abstract = {Open Source Software (OSS) for e-Science should make reference to the paradigm of a distributed surrounding over a multi system mix of Web Services and Grid technologies, allowing data exchanging through services, according to standards in the area of the Grid and of Service Oriented Computing (SOC). In fact, biologists, medical doctors, and scientists are often involved in time consuming experiments and are aware of the degree of difficulty in validating or rejecting a given hypothesis by lab experiments. The benefits of OSS for e-Science consider that as many operating nodes as possible can work cooperatively sharing data, resources, and software, thus avoiding the bottleneck of licenses for distributed use of tools needed to perform cooperative scientific experiments. In particular, this chapter presents an architecture based on nodes equipped with a Grid and with Web Services in order to access OSS, showing how scientific experiments can be enacted through the use of a cooperation among OSS sites. Such a choice, besides reducing the cost of the experiments, would support distributed introduction of OSS among other actors of the dynamical networks, thus supporting the awareness about OSS and their diffusion. An OSS environment for cooperative scientific experiments (e-experiments) can effectively support the distributed execution of different classes of experiments, from visualization to model identification through clustering and rules generation, in various application fields, such as bioinformatics, neuro-informatics, tele-monitoring,or drug discovery. By applying Web Services and Grid computing, an experiment or a simulation can be executed in a cooperative way on various computation nodes of a network equipped with OSS, allowing data exchange among researchers. Our environment  formalizes experiments as cooperative services on various computational nodes of a grid network. Basic elements are models, languages, and support tools creating a virtual
network of organizational responsibility of the global experiments, according to rules under which each node can execute local services to be accessed by other nodes in order to achieve the whole experiment{\textquoteright}s results.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_41},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Environments.pdf},
	author = {Bosin, Andrea and Dess{\'\i}, Nicoletta and Fugini, Maria and Liberati, Diego and Pes, Barbara}
}
@conference {537,
	title = {Open to Grok. How do Hackers{\textquoteright} Practices Produce Hackers?},
	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 = {121 - 129},
	publisher = {Springer},
	organization = {Springer},
	chapter = {10},
	abstract = {How do hackers{\textquoteright} practices produce hackers{\textquoteright} identities? In this paper we argue that the association between science fiction and software programs is rooted in hackers{\textquoteright} practices, defining how hackers{\textquoteright} knowledge{\textquoteright} emerge. The mediation is the one of the Heinlein verb {\textquotedblleft}to grok{\textquotedblright}, part of the Jargon file and of the name of a code browser, OpenGrok, the technology mediating the relationship between OpenSolaris developers and the code base. Starting with a description of the peculiarity of the verb {\textquotedblleft}to grok{\textquotedblright}, and its connection with a non-Cartesian view of knowledge, we discuss how the history of OpenGrok and its use by developers make this knowledge part of hackers{\textquoteright} practices and identities, as someone involved in a true, deep understanding of software.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_10},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20to\%20Grok.pdf},
	author = {D{\textquoteright}Andrea, Vincenzo and De Paoli, Stefano and Teli, Maurizio}
}
@conference {532,
	title = {PMLite: An Open Source Solution for Process Monitoring},
	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 = {57 - 68},
	publisher = {Springer},
	organization = {Springer},
	chapter = {5},
	abstract = {Process Monitoring represents a big challenge for organizations that aim to manage software projects adopting different development paradigms. In fact, across-process enterprise-level measurement campaigns can be difficult to enact since process attributes to retrieve are semantically diverse and may be difficult to integrate. In this paper, we present PMLite (Process Monitoring Lite) an open source solution to this problem. PMLite is based on an open metamodel and paves the way to the definition of ad-hoc open monitoring frameworks.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/PMLite.pdf},
	author = {Colombo, Alberto and Damiani, Ernesto and Frati, Fulvio}
}
@conference {WeiBgerber:2008:SPG:1370750.1370767,
	title = {Small patches get in!},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {67{\textendash}76},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {While there is a considerable amount of research on analyzing the change information stored in software repositories, only few researcher have looked at software changes contained in email archives in form of patches. In this paper we look at the email archives of two open source projects and answer questions like the following: How many emails contain patches? How long does it take for a patch to be accepted? Does the size of the patch influence its chances to be accepted or the duration until it gets accepted? Obviously, the answers to these questions can be helpful for the authors of patches, in particular because some of the answers are surprising.},
	keywords = {case study, cvs, email, email archives, flac, mailing list, openafs, patch acceptance, patches, revision control, scm},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370767},
	url = {http://doi.acm.org/10.1145/1370750.1370767},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p67-weissgerber.pdf},
	author = {Wei{\ss}gerber, Peter and Neu, Daniel and Diehl, Stephan}
}
@conference {552,
	title = {Social Networking Technologies for Free-Open Source E-Learning Systems},
	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 = {289 - 297},
	publisher = {Springer},
	organization = {Springer},
	chapter = {25},
	abstract = {In this paper, we illustrate our methodology for academic teaching, based on cooperative learning paradigm, which also relies on cutting edge e-learning techniques. We use Web 2.0 resources to fulfill requirements for an interactive-constructivistic {\textquotedblleft}learning space{\textquotedblright}, where blended-teaching paradigm may be proficiently applied. We extend an existing Free/Open Source Software Learning Management System, to create a cooperative and community-based learning space adherent to our proposal.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_25},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Social\%20Networking\%20Technologies.pdf},
	author = {Di Cerbo, Francesco and Dodero, Gabriella and Succi, Giancarlo}
}
@article {Barcellini2008141,
	title = {A socio-cognitive analysis of online design discussions in an Open Source Software community},
	journal = {Interacting with Computers},
	volume = {20},
	number = {1},
	year = {2008},
	pages = {141 - 165},
	abstract = {This paper is an analysis of online discussions in an Open Source Software (OSS) design community, the Python project. Developers of Python are geographically distributed and work online asynchronously. The objective of our study is to understand and to model the dynamics of the OSS design process that takes place in mailing list exchanges. We develop a method to study distant and asynchronous collaborative design activity based on an analysis of quoting practices. We analyze and visualize three aspects of the online dynamics: social, thematic temporal, and design. We show that roles emerge during discussions according to the involvement and the position of the participants in the discussions and how they influence participation in the design discussions. In our analysis of the thematic temporal dynamics of discussion, we examine how themes of discussion emerge, diverge, and are refined over time. To understand the design dynamics, we perform a content analysis of messages exchanged between developers to reveal how the online discussions reflect the {\textquotedblleft}work flow{\textquotedblright} of the project: it provides us with a picture of the collaborative design process in the OSS community. These combined results clarify how knowledge and artefacts are elaborated in this epistemic, exploration-oriented, OSS community. Finally, we outline the need to automate of our method to extend our results. The proposed automation could have implications for both researchers and participants in OSS communities.},
	keywords = {Role},
	issn = {0953-5438},
	doi = {10.1016/j.intcom.2007.10.004},
	url = {http://www.sciencedirect.com/science/article/pii/S0953543807000793},
	author = {Barcellini, Flore and D{\'e}tienne, Fran{\c c}oise and Burkhardt, Jean-Marie and Warren Sack}
}
@conference {Pattison:2008:TWP:1370750.1370776,
	title = {Talk and work: a preliminary report},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {113{\textendash}116},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Developers in Open Source Software (OSS) projects communicate using mailing lists. By convention, the mailing lists used only for task-related discussions, so they are primarily concerned with the software under development, and software process issues (releases, etc.). We focus on the discussions concerning the software, and study the frequency with which software entities (functions, methods, classes, etc) are mentioned in the mail. We find a strong, striking, cumulative relationship between this mention count in the email, and the number of times these entities are included in changes to the software. When we study the same phenomena over a series of time-intervals, the relationship is much less strong. This suggests some interesting avenues for future research.},
	keywords = {ant, apache, email, mailing lists, postgresql, python, scm, source code},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370776},
	url = {http://doi.acm.org/10.1145/1370750.1370776},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p113-pattison.pdf},
	author = {Pattison, David S. and Bird, Christian A. and Premkumar T. Devanbu}
}
@conference {543,
	title = {The Total Growth of Open Source},
	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 = {197 - 209},
	publisher = {Springer},
	organization = {Springer},
	chapter = {16},
	abstract = {Software development is undergoing a major change away from a fully closed software process towards a process that incorporates open source software in products and services. Just how significant is that change? To answer this question we need to look at the overall growth of open source as well as its growth rate. In this paper, we quantitatively analyze the growth of more than 5000 active and popular open source software projects. We show that the total amount of source code as well as the total number of open source projects is growing at an exponential rate. Previous research showed linear and quadratic growth in lines of source code of individual open source projects. Our work shows that open source is expanding into new domains and applications at an exponential rate.
},
	issn = {978-0-387-09683-4},
	doi = {http://dx.doi.org/10.1007/978-0-387-09684-1_16},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Total\%20Growth\%20of\%20Open\%20Source.pdf},
	author = {Amit Deshpande and Dirk Riehle}
}
@inbook {869,
	title = {Towards a Global Research Infrastructure for Multidisciplinary Study of Free/Open Source Software Development},
	booktitle = {Open Source Development, Communities and Quality},
	series = {IFIP International Federation for Information Processing},
	volume = {275},
	year = {2008},
	pages = {143-158},
	publisher = {Springer},
	organization = {Springer},
	address = {Boston},
	author = {Gasser, Les and Walt Scacchi},
	editor = {Russo, B. and Damiani, E. and Hissan, S. and Lundell, B. and Succi, G.}
}
@article {Sadowski2008323,
	title = {Transition of governance in a mature open software source community: Evidence from the Debian case},
	journal = {Information Economics and Policy},
	volume = {20},
	number = {4},
	year = {2008},
	note = {"We primarily used internal documents related to the contents and context of different Debian projects."
"Furthermore, we attended several Debian conferences and were {\textquoteleft}{\textquoteleft}lurking around{\textquotedblright} on the Debian mailing lists, websites, IRC channels, etc."},
	pages = {323 - 332},
	abstract = {As open source software (OSS) communities mature, they have to introduce a variety of governance mechanisms to manage the participation of their members and to coordinate the launch of new releases. The Debian community introduced new mechanisms of informal administrative control based on a constitution, elected leaders, and used interactive communication channels. We show that these control mechanisms were introduced as a response to emerging innovative opportunities due to the usage of source packages and to the need to build a responsive organization within the Debian OSS community.},
	keywords = {debian, governance},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.05.001},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4SHF4BS-1/2/579ba679ee43d7c77302f3595334dd24},
	author = {Bert M. Sadowski and Gaby Sadowski-Rasters and Geert Duysters}
}
@article {Barcellini:2008:UDM:1379919.1380288,
	title = {User and developer mediation in an Open Source Software community: Boundary spanning through cross participation in online discussions},
	journal = {Int. J. Hum.-Comput. Stud.},
	volume = {66},
	number = {7},
	year = {2008},
	pages = {558{\textendash}570},
	publisher = {Academic Press, Inc.},
	address = {Duluth, MN, USA},
	abstract = {The aim of this research is to analyse how design and use are mediated in Open Source Software (OSS) design. Focusing on the Python community, our study examines a {\textquoteright}{\textquoteright}pushed-by-users{\textquoteright}{\textquoteright} design proposal through the discussions occurring in two mailing-lists: one, user-oriented and the other, developer-oriented. To characterize the links between users and developers, we investigate the activities and references (knowledge sharing) performed by the contributors to these two mailing-lists. We found that the participation of users remains local to their community. However, several key participants act as boundary spanners between the user and the developer communities. This emerging role is characterized by cross-participation in parallel same-topic discussions in both mailing-lists, cohesion between cross-participants, the occupation of a central position in the social network linking users and developers, as well as active, distinctive and adapted contributions. The user championing the proposal acts as a key boundary spanner coordinating the process and using explicit linking strategies. We argue that OSS design may be considered as a form of {\textquoteright}{\textquoteright}role emerging design{\textquoteright}{\textquoteright}, i.e. design organized and pushed through emerging roles and through a balance between these roles. The OSS communities seem to provide a suitable socio-technical environment to enable such role emergence. },
	keywords = {Boundary spanners, Cross-participants, Distributed design, Open Source Software Community, Role emerging design},
	issn = {1071-5819},
	doi = {10.1016/j.ijhcs.2007.10.008},
	url = {http://dx.doi.org/10.1016/j.ijhcs.2007.10.008},
	author = {Barcellini, Flore and D{\'e}tienne, Fran{\c c}oise and Burkhardt, Jean-Marie}
}
@conference {Pohl:2008:DNM:1370114.1370135,
	title = {What dynamic network metrics can tell us about developer roles},
	booktitle = {Proceedings of the 2008 international workshop on Cooperative and human aspects of software engineering (CHASE {\textquoteright}08)},
	series = {CHASE {\textquoteright}08},
	year = {2008},
	note = {paper d/l from http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.217.4765

this particular paper focuses on building the SNA using co-authorship of files in Tomcat.},
	pages = {81{\textendash}84},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Software development is heavily dependent on the participants of the process and their roles within the process. Each developer has his specific skills and interests and hence contributes to the project in a different way. While some programmers work on separate modules, others developers integrate these modules towards the final product. To identify such different groups of people one approach is to work with methods taken from social network analysis. To this end, a social network has to be defined in a suitable way, and appropriate analysis strategies have to be chosen. This paper shows how a network of software developers could be defined based on information in a software repository, and what it can possibly tell about roles of developers (and what not) in the process of the application server Tomcat.},
	keywords = {identifying roles, social network analysis},
	isbn = {978-1-60558-039-5},
	doi = {10.1145/1370114.1370135},
	url = {http://doi.acm.org/10.1145/1370114.1370135},
	attachments = {https://flosshub.org/sites/flosshub.org/files/10.1.1.217.4765.pdf},
	author = {Pohl, Mathias and Diehl, Stephan}
}
@conference {636,
	title = {Authenticating from multiple authentication sources in a collaborative platform},
	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 = {229 - 234},
	publisher = {Springer},
	organization = {Springer},
	chapter = {20},
	abstract = {This paper presents a proposal to address the need for multiple authentication sources for users of collaborative work platforms. The proposed approach, developed for the needs of GET and Picolibre, relies on a generic solution that integrate groupware servers in a Shibboleth infrastructure. We have developed adapters for this integration, that we contributed to the phpGroupware
project. This document should serve as a basis for discussion in order to validate the level of generality of the proposed approach. We hope that this approach can also help maintainers of other collaboration platforms, who want to integrate a park of deployed platforms with external user identification and authentication services, get a better view of solutions available with Shibboleth.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Authenticating\%20from\%20multiple.pdf},
	author = {Quang Vu Dang and Olivier Berger and Christian Bac and Hamet, Beno{\^\i}t}
}
@article {flosswp357,
	title = {Business models in FLOSS-based companies},
	year = {2007},
	month = {May},
	abstract = {The sustainability of Free/Libre/Open Source Software (FLOSS) has recently become an important aspect of the overall open source phenomenon, and as such has received a significant research attention. Since 1999, several articles addressed the role of licenses, communities and business models in FLOSS-based companies, but mostly from a theoretical point of view. In this article, we present the result of a detailed analysis of 80 FLOSS-based companies and business models, using publicly available data on service offers, mailing list archives, online articles and when available public financial data. The result is a simplified and effective classification that can be used as a guide to companies willing to offer services in the same area, and an analysis on how the community process is influenced by the choice of licensing and business model.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OSSEMP07-daffara.pdf},
	author = {Carlo Daffara}
}
@conference {626,
	title = {Corporate Involvement of Libre Software: Study of Presence in Debian Code over Time},
	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 = {121 - 132},
	publisher = {Springer},
	organization = {Springer},
	chapter = {10},
	abstract = {Although much of the research on the libre (free, open source) phenomenon has been focused on the involvement of volunteers, the role of companies is also important in many projects. In fact, during the last years, the involvement of companies in the libre software world seems to be raising. In this paper we present an study that shows, quantitatively, how important this involvement is in the production of the largest collection of code available for Linux: the Debian GNU/Linux distribution. By studying copyright attributions in source code, we have identified those companies with more attributed code, and the trend of corporate presence in Debian from 1998 to 2004.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_10},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Corporate\%20Involvement\%20of\%20Libro.pdf},
	author = {Gregorio Robles and Due{\~n}as, Santiago and Gonzalez-Barahona, Jesus}
}
@conference {1011,
	title = {Detecting Patch Submission and Acceptance in OSS Projects},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {26 - 26},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {The success of open source software (OSS) is completely dependent on the work of volunteers who contribute their time and talents. The submission of patches is the major way that participants outside of the core group of developers make contributions. We argue that the process of patch submission and acceptance into the codebase is an important piece of the open source puzzle and that the use of patch-related data can be helpful in understanding how OSS projects work. We present our methods in identifying the submission and acceptance of patches and give results and evaluation in applying these methods to the Apache webserver, Python interpreter, Postgres SQL database, and (with limitations) MySQL database projects. In addition, we present valuable ways in which this data has been and can be used.},
	keywords = {apache, contributions, mysql, patches, postgresql, python, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300026.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem}
}
@conference {639,
	title = {Different Bug Fixing Regimes? A Preliminary Case for Superbugs},
	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 = {247 - 252},
	publisher = {Springer},
	organization = {Springer},
	chapter = {23},
	abstract = {The paper investigates the processes by which bugs are fixed in open-source software projects. Focusing on Mozilla and combining data from both its bug tracker (Bugzilla) and from its CVS, we suggest that: a) Some bugs resist beyond the first patch applied to the main branch of the source code in relation to them, which we denote as superbugs; b) There might exist different bug fixing regimes; c) priority and severity flags as defined in bug repositories are not optimized for superbugs and might lead to a involuntary side effects; d) The survival time of superbugs is influenced by the nature of the discussions within Bugzilla, by bug dependencies and by the provision of contextual elements.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Different\%20Bug\%20Fixing\%20Regimes.pdf},
	author = {Jean-Michel Dalle and den Besten, Matthijs}
}
@conference {633,
	title = {EDOS Distribution System: a P2P architecture for open-source content dissemination},
	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 = {209 - 215},
	publisher = {Springer},
	organization = {Springer},
	chapter = {17},
	abstract = {The open-source software communities currently face an increasing complexity of managing the software content among theirs developers and contributors. This is mainly due to the continuously growing size of the software, the high frequency of the updates, and the heterogeneity of the participants. We propose a distribution system that tackles two main issues in the software content management: efficient content dissemination through a P2P system architecture, and advanced information system capabilities, using a distributed index for resource location.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_17},
	attachments = {https://flosshub.org/sites/flosshub.org/files/EDOS\%20Distribution\%20System.pdf},
	author = {Abiteboul, Serge and Dar, Itay and Pop, Radu and Vasile, Gabriel and Vodislav, Dan}
}
@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}
}
@conference {669,
	title = {FOCSE: An OWA-based Evaluation Framework for OS Adoption in Critical Environments},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	pages = {3-16},
	publisher = {Springer},
	organization = {Springer},
	chapter = {1},
	abstract = {While the vast majority of European and US companies increasingly use open source software for non-key applications, a much smaller number of companies have deployed it in critical areas such as security and access control. This is partly due to residual difficulties in performing and documenting the selection process of open source solutions. In this paper we describe the FOCSE metrics framework, supporting a specific selection process for security-related open source code. FOCSE is based on a set of general purpose metrics suitable for evaluating open source frameworks in general; however, it includes some specific metrics expressing security solutions{\textquoteright} capability of responding to continuous change in threats. We show FOCSE at work in two use cases about selecting two different types of security-related open source solutions, i.e. Single Sign-On and Secure Shell applications.
 },
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/FOCSE\%20\%20an\%20\%20OWA.pdf},
	author = {Ardagna, Claudio and Damiani, Ernesto and Frati, Fulvio}
}
@conference {640,
	title = {Free/Open Services: Conceptualization, Classification, and Commercialization},
	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 = {253 - 258},
	publisher = {Springer},
	organization = {Springer},
	chapter = {24},
	abstract = {The concept of Free/Open Services (F/O-Services) emerges by bringing together services with Free/Open Source Software (FOSS). F/O-Services enable the creation of transparent composite services collectively and allow people and other services to access them. This paper extends the concept of F/O-Services beyond the level of open interfaces, analyzing the associated licensing interpretations and exploring the notion of open service dependencies. Further, the paper overviews the business models for F/O-Services as a part of this social mechanism of exchange.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_24},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Free\%20Open\%20Services.pdf},
	author = {Gangadharan, G. and D{\textquoteright}Andrea, Vincenzo and Weiss, Michael}
}
@article {497,
	title = {The functioning of a free software community: entanglement of three regulation modes - control, autonomous, and distributed},
	journal = {Science Studies},
	number = {2},
	year = {2007},
	abstract = {This paper consider FLOSS communities as ""going concerns"" which necessitate a minimum of order and common, shared, social rules to function. Through an in-depth and diachronic analysis of the Spip project, we present two classical modes of social regulation: a control regulation centred on the product and an autonomous regulation reflecting the differentiated commitments. Our data shows that the meaning, value and legitimacy of contributors{\textquoteright} involvements are defined and rated more collectively, through exchanges, judgments, and evaluations. A third regulation mode, called distributed community regulation and aimed at creating and transforming shared rules that produces recognition and stratification, is then presented.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Science_Studies_02-2007-Demaziere_Horn_Zune.pdf},
	author = {Didier Demazi{\`e}re and Francois Horn and Marc Zune}
}
@conference {1001,
	title = {Identifying Changed Source Code Lines from Version Repositories},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {14 - 14},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Observing the evolution of software systems at different levels of granularity has been a key issue for a number of studies, aiming at predicting defects or at studying certain phenomena, such as the presence of clones or of crosscutting concerns. Versioning systems such as CVS and SVN, however, only provide information about lines added or deleted by a contributor: any change is shown as a sequence of additions and deletions. This provides an erroneous estimate of the amount of code changed.

This paper shows how the evolution of changes at source code line level can be inferred from CVS repositories, by combining information retrieval techniques and the Levenshtein edit distance. The application of the proposed approach to the ArgoUML case study indicates a high precision and recall.},
	keywords = {argouml, cvs, levenshtein, scm, source code},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.14},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300014.pdf},
	author = {Canfora, Gerardo and Cerulo, Luigi and Di Penta, Massimiliano}
}
@conference {659,
	title = {Introduction to OSS 2007 Tutorial Program},
	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 = {359 - 360},
	publisher = {Springer},
	organization = {Springer},
	chapter = {43},
	abstract = {Today, most software researchers and professionals consider Open Source as a greatly successful paradigm for large-scale production of high-quality software systems. However, most of them would probably agree that successfully applying this paradigm requires dealing with a number of important issues. One of the best reasons to attend OSS conference series is being able to discuss these issues in an unprecedented gathering of top-notch researchers, developers, and leaders from all avenues of the open source movement. Attending good tutorials, in particular, is a great opportunity for getting in touch with new ideas and discussing them in depth with real experts.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_43},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Introduction\%20to\%20OSS\%202007.pdf},
	author = {Damiani, Ernesto}
}
@article {flosswp331,
	title = {Micro-dynamics of Free and Open Source Software Development. Lurking, laboring and launching new projects on SourceForge},
	year = {2007},
	month = {January},
	abstract = {Quantitative methods are employed to describe two fundamental processes in the creation of free (libre) and open source software (FLOSS) that are at work in the collaborative development environment of the SourceForge.Net platform: resource mobilization and "entrepreneurial initiatives" which generate new development projects. The micro dynamics of the individuals{\textquoteright} involvements in these processes are analysed by defining "activity states" that correspond to "lurking" (not contributing or contributing to projects without become a member), "laboring" (joining one or more projects as members), and "launching" (founding one or more projects). The transition probability matrices constructed from observations on the activities of 222,835 individuals who registered on SF.net (during a 14-month period, mainly in 2001) characterize first-order Markov chains describing processes that are ergodic. The computation of the limiting "equilibrium" distribution of individual joining and launching activities is not used here to produce long-run predictions, because the time window of the available data is too short. Instead, it is conceived as an instrument to isolate the main forces acting in the underlying entrepreneurial and recruitment dynamics at work on the platform "shaking off" the weaker tendencies. It is shown that, although only a small proportion of the considered cohorts of SF.net registrants become even minimally active, the active "core" of project members and project founders is able to attract an increasing number of developers. SourceForge is seen to be more than an attractor of projects that are being "born again" under open source licenses: this virtual collaborative development environment shares the regenerative properties of tangible "industrial districts" that give rise to new, innovative enterprises. Implications for the exploitation and exploitation processes at work in the FLOSS model and about its sustainability are also derived.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/davidrullani.pdf},
	author = {Paul A. David and Francesco Rullani}
}
@conference {995,
	title = {Open Borders? Immigration in Open Source Projects},
	booktitle = {Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {6 - 6},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Open source software is built by teams of volunteers. Each project has a core team of developers, who have the authority to commit changes to the repository; this team is the elite, committed foundation of the project, selected through a meritocratic process from a larger number of people who participate on the mailing list. Most projects carefully regulate admission of outsiders to full developer privileges; some projects even have formal descriptions of this process. Understanding the factors that influence the "who, how and when" of this process is critical, both for the sustainability of FLOSS projects, and for outside stakeholders who want to gain entry and succeed. In this paper we mount a quantitative case study of the process by which people join FLOSS projects, using data mined from the Apache web server, Postgres, and Python. We develop a theory of open source project joining, and evaluate this theory based on our data.},
	keywords = {apache, core, joining, postgresql, python, team},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300006.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem and Swaminathan, Anand and Hsu, Greta}
}
@conference {638,
	title = {Open source technologies for visually impaired people},
	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 = {241 - 246},
	publisher = {Springer},
	organization = {Springer},
	chapter = {22},
	abstract = {We describe two open source applications which we have experienced as very useful aids for the integration of people suffering from visual impairments, from hypovision to actual blindness. The first application is based on speech synthesis and has been experienced by disabled university students. The second experience is oriented to schoolchildren with low residual vision, and it provides their educators and parents with easy to use tools for image manipulation, especially designed for exploiting
residual visual abilities.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_22},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Open\%20Source\%20Technologies\%20for\%20Visually\%20.pdf},
	author = {Boccacci, Patrizia and Carrega, Veronica and Dodero, Gabriella}
}
@article {flosswp375,
	title = {Penguin in a new suit: A tale of how de novo entrants emerged to harness free and open source communities},
	year = {2007},
	month = {October},
	abstract = {A growing body of literature has explored the motivations for individuals to take part in free and open source software (FOSS), yet how firms participate is largely an unattended research area. Building on information from an extensive dataset of secondary sources and 30 in-depth interviews, I show that de novo entrants have emerged in conjunction with a changing institutional infrastructure and a more pragmatic attitude toward firms that focus on technological benefits rather than ideology. To understand how these firms try to harness the work of these communities, I use the empirical data to derive a 2*2 matrix of different approaches. The X axis reflects whether or not the firms initiated a new community or relied on communities founded by peers, whereas the Y axis represents the degree of participation of the firm in the community. This taxonomy illustrates how de novo entrant are initiating new forms of communities or joining communities established by peers. This suggests that while many of the central pillars of FOSS remains, de novo entrants have emerged to find new ways of making business resulting in various implications for firm strategies and knowledge disclosure. PLEASE EMAIL IF YOU LIKE A COPY OF THE PAPER!},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dahlander2007.pdf},
	author = {Linus Dahlander}
}
@conference {1214,
	title = {A Preliminary Analysis of Publicly Available FLOSS Measurements: Towards Discovering Maintainability Trends},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	note = {used SourceKibitzer data downloaded from FLOSSmole},
	month = {2007},
	abstract = {The spread of free/libre/open source software (FLOSS) and the openness of its development model offer researchers a valuable source of information regarding software data. The creation of large portals, which host a vast amount of FLOSS projects make it easy to create large datasets with valuable information regarding the FLOSS development process. In addition initiatives such as FLOSSMole provide researchers with a single point and continuing access to those data. Up to now the majority of datasets from FLOSSMole offered data regarding the development process and not the code itself. From February 2007 FLOSSMole offers data donated 
by SourceKibitzer, which contain source code metrics for FLOSS projects written in Java. In this paper we provide 
a premilinary analysis on those data using machine learning techniques, such as classification rules and decision trees. Using the first available data from February 2007, we tried to build rules that can be used in order to estimate the future values of metrics offered for March. Here we present some preliminary results that are encouraging and deserve to be further analyzed in future releases of SourceKibitzer datasets. },
	keywords = {decision tree, flossmole, java, machine learning, metrics, sourcekibitzer},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Samolades2007.pdf},
	author = {Samoladas, Ioannis and Bibi, Stamatia and Ioannis Stamelos and Sowe, Sulayman K. and Deligiannis, Ignatios}
}
@conference {1225,
	title = {Programming Language Trends in Open Source Development: An Evaluation Using Data from All Production Phase SourceForge Projects},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	note = {"Our data were gathered from the SourceForge Research Ar- chive (SFRA) [4] and the CVS repositories Open Source projects hosted on SourceForge. We used cvs2mysql and SFRA+ to collect the data. cvs2mysql gathers data from CVS repositories and writes them to SQL scripts for im- port into a MySQL 5.0 database. The data collected by cvs2mysql are the name of the file, the location of the file in the repository, the type and state of the file, as well as the author, date, number of lines added and removed, and the author{\textquoteright}s message for each revision to the file."},
	abstract = {In this work, we analyze data collected from the CVS repos- itories of 9,997 Open Source projects hosted on SourceForge in an effort to understand trends in programming language usage in the Open Source community between 2000 and 2005. The trends we consider include: 1) the relative popularity of the ten most popular programming languages over time, 2) the use of multiple programming languages by individual programmers and by individual projects, and 3) the programming languages most often used in combination.},
	keywords = {cvs, cvs2mysql, programming languages, sfra, sourceforge, srda},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Delorey2007b.pdf},
	author = {Delorey, Daniel P. and Knutson, Charles D. and Giraud-Carrier, C.}
}
@conference {634,
	title = {Reusing an open source application {\textemdash} practical experiences with a mobile CRM pilot},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	year = {2007},
	month = {2007///},
	pages = {217 - 222},
	publisher = {Springer},
	organization = {Springer},
	chapter = {18},
	abstract = {We discuss experiences in extending an open source CRM application to develop a new server-based mobile business application. Combining the application code reuse with incremental development process allowed successful development of a pilot application in a tight schedule. In particular, it enabled a quick start for customer-driven development, diminished risks related to the baseline application itself, and provided the flexibility needed in experimental pilot development.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_18},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Reusing\%20an\%20Open\%20Source\%20Application.pdf},
	author = {Akkanen, Jyrki and Demeter, Hunor and Eppel, Tam{\'a}s and Iv{\'a}nfi, Zolt{\'a}n and Nurminen, Jukka and Stenman, Petri}
}
@conference {1227,
	title = {Simulation of the temporal evolution of OSS projects: application to XMMS and MPLAYER},
	booktitle = {2nd Workshop on Public Data about Software Development (WoPDaSD 2007)},
	year = {2007},
	author = {Antoniades, Ionannis~ and Kontoyiannis and Ioannis Stamelos and Deligiannis, Ignatios}
}
@conference {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 {1002,
	title = {Studying Versioning Information to Understand Inheritance Hierarchy Changes},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {16 - 16},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {With the widespread adoption of object-oriented programming, changing the inheritance hierarchy became an inherent part of today{\textquoteright}s software maintenance activities. Unfortunately, little is known about the "state-of-the-practice" with respect to changing an application{\textquoteright}s inheritance hierarchy, and consequently we do not know how the change process can be improved. In this paper, we report on a study of the hierarchy changes stored in a versioning system to explore the answers to three research questions: (1) why are hierarchy changes made? (2) what kind of hierarchy changes are made? (3) what is the impact of these changes? Based on the results of this study, we formulate 7 hypotheses which should be investigated further to make conclusive interpretations on how hierarchy changes fit in the actual change process.},
	keywords = {argouml, change management, inheritance, jedit},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.30},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300016.pdf},
	author = {Rysselberghe, Filip Van and Demeyer, Serge}
}
@conference {874,
	title = {Talk Amongst Yourselves: Inviting Users to Participate in Online Conversations.},
	booktitle = {International Conference on Intelligent User Interfaces  },
	series = {Proceedings of the 12th international conference on Intelligent user interfaces},
	year = {2007},
	month = {28/01/2007},
	pages = {62-71},
	publisher = {ACM},
	organization = {ACM},
	address = {Honolulu, Hawaii},
	isbn = {1-59593-481-2},
	author = {F. Harper and D. Frankowski and Drenner, S. and Y. Ren and S. Kiesler and Terveen, L. and Kraut, R. and Riedl, J.}
}
@conference {666,
	title = {Toward a New Industrial Organization? OSS in Economic and Managerial Perspective},
	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 = {377 - 379},
	publisher = {Springer},
	organization = {Springer},
	chapter = {50},
	abstract = {At present, an more and more users are running Open Source software (OSS) on their systems. Major companies, like IBM, Oracle, or Sun Microsystems, have now started to make significant investments in developing open communities and creating a portfolio of systems incorporating OSS applications into their design. Meanwhile, an increasing number of firms are entering the market by offering OSS-based solutions to their customers, often supplying a mix of proprietary and open solutions through hybrid business models. In this context, economists and management scientists are now moving beyond the state of puzzlement that has driven much of the initial attention towards OSS. Located in the context of OSS2007 in order to foster close and fruitful interactions with scholars from various other disciplines, this workshop aims at contributing to the current evolutions of the economic and managerial research agendas about OSS, and thus to provide, first, an assessment of where we {\textemdash} economics and management scholars - are about OSS, and, second, an analysis of the renewed directions in which we should consider inquiring further in the near future, focusing notably on business, production, diffusion and innovation models.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_50},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Toward\%20a\%20new\%20indusctial\%20Org.pdf},
	author = {Dalle, Jean and Cristina Rossi and Francesco Rullani}
}
@article {flosswp341,
	title = {Towards an Open Ontology for Emergency Response},
	year = {2007},
	month = {January},
	abstract = {Emergency Response and Relief Coordination Efforts are evolving to leverage the efficiencies offered by the internet in the area of real time communication among agents and stakeholders. There is widespread consensus both in the technical and ER community that to improve efficiency of response, information must be shared and web based protocols must be used [22]. In addition to known technical and non-technical obstacles that inhibit the effective and seamless coordination of operations, we identify issues that challenge the development of functional information and communication models. Recent studies in ontology engineering, and evidence from direct observations of open-source work groups in this field, point to the need for an easy to use {\textquoteright}open{\textquoteright} conceptual and semantic framework, defined here broadly as ???Open Ontology??? (OOnt), and a corresponding design and implementation methodology that can be referenced unambiguously and universally by developers and users of information systems designed to support ER operations.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/TOWARDS_AN_OPEN_ONTOLOGY_FOR_ER.pdf},
	author = {Paola Di Maio}
}
@article {495,
	title = {Towards an understanding of FLOSS: Infrastructures, Materiality and the Digital Business Ecosystem},
	journal = {Science Studies},
	number = {2},
	year = {2007},
	abstract = {In this paper we present empirical work detailing the engagement practices of a large FLOSS project, the Digital Business Ecosystem (DBE). In common with many other FLOSS projects, the DBE project focused on the development of infrastructural software components. Infrastructures and FLOSS software exhibit multiplicity: as objects they both change and stay the same. Whilst the implications of multiplicity with respect to infrastructure have been well-documented, with respect to FLOSS, they remain under-explored. Through examining how the DBE engaged new participants we were able to explore the nature of the FLOSS software object by asking the implied question: engagement with what? We draw on recent analysis by Law and Singleton to show how the innovative yet non-existent potentiality of the DBE was as significant to engagement as its steadily growing codebase. We argue that acknowledging the materiality and immateriality of the FLOSS software object has important consequences for management of, and engagement with, FLOSS projects.},
	keywords = {engagement, FLOSS, infrastructures, INNOVATION, materiality},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Darking_Whitley.pdf},
	author = {Mary Darking and Edgar A Whitley}
}
@article {1215,
	title = {Using FLOSSmole Data in Determining Business Readiness Ratings},
	journal = {2nd Workshop on Public Data about Software Development (WopDaSD 2007)},
	year = {2007},
	month = {2007},
	abstract = {This paper is a preliminary report on using FLOSSmole data retrieved from open source repositories (forges) to calculate Business Readiness Rating scores.  },
	keywords = {brr, business readiness rating, flossmole},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Using\%20FLOSSmole\%20Data\%20in\%20Determining\%20Business\%20Readiness\%20Ratings.pdf},
	author = {Wasserman, Anthony and Ashutosh Das}
}
@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}
}
@proceedings {91,
	title = {An absorptive capacity perspective of open source software development group performance},
	year = {2006},
	keywords = {NotreDameArchive},
	author = {Sherae Daniel and Ritu Agarwal and Katherine Stewart}
}
@conference {679,
	title = {Adopting Open Source for Mission-Critical Applications: A Case Study on Single Sign-On},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {209 - 220},
	publisher = {Springer},
	organization = {Springer},
	abstract = {In this paper, we describe a specific selection process for security-related open source code, based on a methodology aimed at evaluating open source security frameworks in general and Single-Sign-On (SSO) systems in particular. Our evaluation criteria for open source security-related software include the community{\textquoteright}s timeliness of reaction against newly discovered vulnerabilities or incidents.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_21},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Adapting\%20OS\%20for\%20Mission-critical\%20Applications.pdf},
	author = {Ardagna, Claudio and Damiani, Ernesto and Frati, Fulvio and Reale, Salvatore}
}
@conference {D{\textquoteright}Ambros:2006:AER:1137983.1138029,
	title = {Applying the evolution radar to PostgreSQL},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {177{\textendash}178},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	keywords = {cvs, documentation, evolution, evolution radar, logical coupling, makefile, mining challenge, msr challenge, postgresql, re-engineering, refactoring, release history, rhdb, source code, version control, visualization},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138029},
	url = {http://doi.acm.org/10.1145/1137983.1138029},
	attachments = {https://flosshub.org/sites/flosshub.org/files/177ApplyingEvolution.pdf},
	author = {D{\textquoteright}Ambros, Marco and Lanza, Michele}
}
@conference {WeiBgerber:2006:RLE:1137983.1138011,
	title = {Are refactorings less error-prone than other changes?},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {112{\textendash}118},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Refactorings are program transformations which should preserve the program behavior. Consequently, we expect that during phases when there are mostly refactorings in the change history of a system, only few new bugs are introduced. For our case study we analyzed the version histories of several open source systems and reconstructed the refactorings performed. Furthermore, we obtained bug reports from various sources depending on the system. Based on this data we identify phases when the above hypothesis holds and those when it doesn{\textquoteright}t.},
	keywords = {argouml, bug reports, bugs, change history, jedit, junit, re-engineering, refactoring, reverse engineering, software evolution, version control},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138011},
	url = {http://doi.acm.org/10.1145/1137983.1138011},
	attachments = {https://flosshub.org/sites/flosshub.org/files/112AreRefactorings.pdf},
	author = {Wei{\ss}gerber, Peter and Diehl, Stephan}
}
@conference {682,
	title = {Collaborative Maintenance in Large Open-Source Projects},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {233 - 244},
	publisher = {Springer},
	organization = {Springer},
	abstract = {The paper investigates collaborative work among maintainers of open source software by analyzing the logs of a set of 10 large projects. We inquire whether teamwork can be influenced by several characteristics of code. Preliminary results suggest that collaboration among maintainers in most large open-source projects seems to be positively influenced by file vintage and by Halstead volume of files, and negatively by McCabe complexity and size measured in SLOCs. These results could be consistent with an increased attractivity of files created early in the history of a project, and with maintainers being less attracted by more verbose code and by more complex code, although in this last case it might also reflect the fact that more complex files would be de facto more exclusive in terms of maintenance.
},
	keywords = {apache, COLLABORATION, complexity, cvs, gaim, gcc, ghostscript, halstead, lines of code, loc, mccabe, mozilla, netbsd, openssh, postgresql, python, sloc},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Collaborative\%20Maintenance.pdf},
	author = {den Besten, Matthijs and Jean-Michel Dalle and Galia, Fabrice}
}
@conference {684,
	title = {Comparing macro development for personal productivity tools: an experience in validating accessibility of Talking Books},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {247 - 252},
	publisher = {Springer},
	organization = {Springer},
	abstract = {We describe an experience in developing macros for both Power Point and Impress, to be used in accessibility validation for educational multimedia (Talking Books) designed for visually impaired people. Minor disadvantages in the use of Impress are outlined, which however do not constitute a serious obstacle to adoption of Open Source tools for our purposes.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_24},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Comparing\%20macro\%20development.pdf},
	author = {Dodero, Gabriella and Lupi, Katia and Piffero, Erika}
}
@conference {688,
	title = {Development Platforms as a Niche for Software Companies in Open Source Software},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {341 - 342},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Without Abstract},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Development\%20Platforms\%20as\%20a\%20Niche.pdf},
	author = {Savonnet, Marinette and Leclercq, Eric and Terrasse, Marie-No{\"e}lle and Grison, Thierry and Becker, George and Farizy, Anne and Denoyelle, Ludovic}
}
@conference {D{\textquoteright}Ambros:2006:ERV:1137983.1137992,
	title = {The evolution radar: visualizing integrated logical coupling information},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {26{\textendash}32},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In software evolution research logical coupling has extensively been used to recover the hidden dependencies between source code artifacts. They would otherwise go lost because of the file-based nature of current versioning systems. Previous research has dealt with low-level couplings between files, leading to an explosion of data to be analyzed, or has abstracted the logical couplings to module level, leading to a loss of detailed information. In this paper we propose a visualization-based approach which integrates both file-level and module-level logical coupling information. This not only facilitates an in-depth analysis of the logical couplings at all granularity levels, it also leads to a precise characterization of the system modules in terms of their logical coupling dependencies.},
	keywords = {change management, cvs, evolution, logical coupling, mozilla, scm, source code, thunderbird, tinderbox, visualization},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137992},
	url = {http://doi.acm.org/10.1145/1137983.1137992},
	attachments = {https://flosshub.org/sites/flosshub.org/files/26TheEvolutionRadar.pdf},
	author = {D{\textquoteright}Ambros, Marco and Lanza, Michele and Lungu, Mircea}
}
@conference {674,
	title = {A Framework for Teaching Software Testing using F/OSS Methodology},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {261 - 266},
	publisher = {Springer},
	organization = {Springer},
	abstract = {In this paper we discuss a framework for teaching software testing to undergraduate students{\textquoteright} volunteers. The framework uses open source software development methodology and was implemented in the {\textquotedblleft}Introduction to Software Engineering{\textquotedblright} course at the department of Informatics, Aristotle University, Greece. The framework is in three phases, each describing a teaching and learning context in which students get involved in real software projects activities. We report on our teaching experiences, lessons learned and some practical problems we encountered. Results from preliminary evaluation shows that students did well as bug hunters in the bazaar and are willing to  participate in their projects long after graduation.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_26},
	attachments = {https://flosshub.org/sites/flosshub.org/files/A\%20Framework\%20for\%20Teaching\%20Software\%20Testing.pdf},
	author = {Sowe, Sulayman and Ioannis Stamelos and Deligiannis, Ignatios}
}
@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}
}
@article {flosswp302,
	title = {How free software developers work. The mobilization of "distant communities"},
	year = {2006},
	month = {January},
	abstract = {The work of free software developers is an individual activity carried out in extremely heterogeneous conditions and a collective action with original production methods. We propose to analyze this work starting with the paradoxical notion of a "distant community", that aims to illustrate the tension between, on the one hand, the strength of the sense of belonging to a specific world identifiable in the discourse of the participants and, on the other hand, the distances that separate the contributors in terms of relationships, status, and background. In doing this the aim is to produce a description, necessarily plural, of the different forms of "distant communities" that enables the production of goods in unique social and organizational conditions. More generally speaking, this notion points to methods of coordination that combine two forms of collective action that are usually contrary and antagonistic: a communitarian form based on the subjective feeling of belonging to the same community and a form of partnership based on the coordination of common interests and sharing of objectives (T??nnies, 1887, Weber, 1921). At first, we examine the ways the individual participants organize themselves in order to contribute to a project and we focus on the forms of cooperation and coordination used to deal with the constraints of efficiency and quality associated with the distribution of a product. Secondly, we look at the other side of the coin and examine the ways individual participants take action and we underline the mechanisms of commitment and participation that account for their contribution to the production of free software. These two dimensions, that in our opinion are inseparable, are explored through a survey carried out with free software developers.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CLES_DDFHNJ_juin_2006__vm_Anglais.pdf},
	author = {Didier Demazi{\`e}re and Francois Horn and Nicolas Jullien}
}
@conference {888,
	title = {Insert Movie Reference Here: A System to Bridge Conversation and Item-Oriented Web Sites},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2006},
	month = {22/04/2006},
	pages = {951-954},
	publisher = {ACM},
	organization = {ACM},
	isbn = {1-59593-372-7},
	author = {Sara Drenner and Max Harper and Dan Frankowski and John Riedl and Loren Terveen}
}
@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.}
}
@article {flosswp374,
	title = {A man on the inside: Unlocking communities as complementary assets},
	year = {2006},
	month = {October},
	abstract = {Since Teece{\textquoteright}s seminal paper explaining who were the gainers from technological innovation, increased globalization and the information and communication technology revolution have brought newways for firms to organize and appropriate from innovation. A new more open model of innovation suggests that firms can benefit from sources of innovation that stem from outside the firm. The central theme of this paper is how firms try to unlock communities as complementary assets. These communities exist outside firm boundaries beyond ownership or hierarchical control. Because of practices developed by communities to protect their work, firms need to assign individuals to work in these communities in order to gain access to developments and, to an extent, influence the direction of the community. Using network analysis we show that some software firms sponsor individuals to act strategically within a free and open source software (FOSS) community. Firm sponsored individuals interact with more individuals than interact with them, and also they seek to interact with central individuals in the community. However, we can see differences in how individuals interact, depending on whether their affiliation is with a dedicated FOSS firm or an incumbent in the software industry. Apparently, some firm managers believe they need ???a man on the inside??? to be able to gain access to communities. PLEASE EMAIL IF YOU LIKE A COPY OF THE PAPER!},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dahlanderwallin.pdf},
	author = {Linus Dahlander and Martin W. Wallin}
}
@conference {711,
	title = {The micro-dynamics of open source software development activity},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {339 - 340},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This study aims to isolate and identify the properties of FLOSS development insofar as these can be revealed by examining the ecology of SF.net. It characterizes the contrast between the many {\textquotedblleft}lurkers{\textquotedblright} and a much smaller core of {\textquotedblleft}entrepreneurial{\textquotedblright} developers who are responsible for launching new projects, and gives an interpretation of the function of platforms such as SF.net as sites that people with a propensity to start open source projects can use to recruit {\textquotedblleft}laborers{\textquotedblright}. It describes the process underpinning the mobility of those who are recruited among the projects that are launched and provides insights on the evolution of developers{\textquoteright} level and mode of involvement in FLOSS production.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_36},
	attachments = {https://flosshub.org/sites/flosshub.org/files/The\%20micro-dynamics\%20of\%20open\%20source.pdf},
	author = {David, Paul and Francesco Rullani}
}
@conference {1228,
	title = {Mining CVS Signals},
	booktitle = {1st Workshop on Public Data about Software Development (WoPDaSD 2006)},
	year = {2006},
	pages = {10-19},
	author = {Jean-Michel Dalle and L. Daudet and den Besten, Matthijs}
}
@conference {Bird:2006:MES:1137983.1138016,
	title = {Mining email social networks},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {137{\textendash}143},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Communication \& Co-ordination activities are central to large software projects, but are difficult to observe and study in traditional (closed-source, commercial) settings because of the prevalence of informal, direct communication modes. OSS projects, on the other hand, use the internet as the communication medium,and typically conduct discussions in an open, public manner. As a result, the email archives of OSS projects provide a useful trace of the communication and co-ordination activities of the participants. However, there are various challenges that must be addressed before this data can be effectively mined. Once this is done, we can construct social networks of email correspondents, and begin to address some interesting questions. These include questions relating to participation in the email; the social status of different types of OSS participants; the relationship of email activity and commit activity (in the CVS repositories) and the relationship of social status with commit activity. In this paper, we begin with a discussion of our infrastructure (including a novel use of Scientific Workflow software) and then discuss our approach to mining the email archives; and finally we present some preliminary results from our data analysis.},
	keywords = {communication, contributions, developers, email, email archives, mailing lists, open source, social networks},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138016},
	url = {http://doi.acm.org/10.1145/1137983.1138016},
	attachments = {https://flosshub.org/sites/flosshub.org/files/137MiningEmail.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem and Gertz, Michael and Swaminathan, Anand}
}
@conference {Bird:2006:MES:1137983.1138033,
	title = {Mining email social networks in Postgres},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {185{\textendash}186},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open Source Software (OSS) projects provide a unique opportunity to gather and analyze publicly available historical data. The Postgres SQL server, for example, has over seven years of recorded development and communication activity. We mined data from both the source code repository and the mailing list archives to examine the relationship between communication and development in Postgres. Along the way, we had to deal with the difficult challenge of resolving email aliases. We used a number of social network analysis measures and statistical techniques to analyze this data. We present our findings in this paper.},
	keywords = {developers, email, email archives, open source, postgresql, scm, social network analysis, social networks, source code, status},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138033},
	url = {http://doi.acm.org/10.1145/1137983.1138033},
	attachments = {https://flosshub.org/sites/flosshub.org/files/185MiningEmail.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem and Gertz, Michael and Swaminathan, Anand}
}
@conference {WeiBgerber:2006:MRA:1137983.1138028,
	title = {Mining refactorings in ARGOUML},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	note = {"To see if refactorings in ARGOUML have an effect on the occurrence of new bugs and on communication between the developers, we relate the refactorings to bug reports in ISSUEZILLA respectively to mails on the developer mailing list. "},
	pages = {175{\textendash}176},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In this paper we combine the results of our refactoring reconstruc- tion technique with bug, mail and release information to perform process and bug analyses of the ARGOUML CVS archive.},
	keywords = {argouml, bug tracking, bugs, cvs, email, evolution, mining challenge, msr challenge, re-engineering, refactoring, release history},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138028},
	url = {http://doi.acm.org/10.1145/1137983.1138028},
	attachments = {https://flosshub.org/sites/flosshub.org/files/175MiningRefactorings.pdf},
	author = {Wei{\ss}gerber, Peter and Diehl, Stephan and G{\"o}rg, Carsten}
}
@article {2006,
	title = {Opportunities and Challenges Applying Functional Data Analysis to the Study of Open Source Software Evolution},
	journal = {Statistical Science},
	volume = {21},
	number = {2},
	year = {2006},
	note = {"As part of a larger project, data were collected on 105 OSS	projects hosted online at Sourceforge (sf.net)." "...we limited our data collection to projects that use only the Java programming language and were listed in the Internet and System Networking domains." "... only including these projects that use an OSI approved license..." "had to have posted at least one file on the Sourceforge site as of the time of our initial project selection Fall 2002" "Data were collected on the published release history of each project thatmet the screening criteria. Each release of each project was
analyzed to calculate CplXLCoh. The size of each release was measured using a calculation of the number of lines of code (LOC)"},
	pages = {167-178},
	publisher = {Institute of Mathematical Statistics},
	abstract = {This paper explores the application of functional data analysis (FDA) as a means to study the dynamics of software evolution in the open source context. Several challenges in analyzing the data from software projects are discussed, an approach to overcoming those challenges is described, and preliminary results from the analysis of a sample of open source software (OSS) projects are provided. The results demonstrate the utility of FDA for uncovering and categorizing multiple distinct patterns of evolution in the complexity of OSS projects. These results are promising in that they demonstrate some patterns in which the complexity of software decreased as the software grew in size, a particularly novel result. The paper reports preliminary explorations of factors that may be associated with decreasing complexity patterns in these projects. The paper concludes by describing several next steps for this research project as well as some questions for which more sophisticated analytical techniques may be needed.},
	keywords = {complexity, evolution, fda, java, lines of code, loc, release history, scm, size, sourceforge},
	issn = {08834237},
	url = {http://www.jstor.org/stable/27645747},
	author = {Stewart, Katherine J. and Darcy, David P. and Daniel, Sherae L.}
}
@article {886,
	title = {Scope and Timing of Deployment: Moderators of Organizational Adoption of the Linux Server Platform.},
	journal = {International Journal of IT Standards Research},
	volume = {4},
	year = {2006},
	month = {7/2006},
	pages = {1-23},
	abstract = {<p>\&nbsp;Market selection of product compatibility standards has long been explained through aggregate positive-feedback theoretical models of economic utility. Explaining aggregate patterns of organizational standards adoption requires two additional steps \&mdash; not only differences between organizations, but also differences within organizations.</p><p>Here we present a qualitative study of how organizations do (or do not) adopt a new computer server platform standard, namely Linux using PC-compatible hardware. While discussions of Linux typically focus on its open source origins, our respondents were primarily interested in low price. Despite this relative advantage in price, incumbent standards enjoyed other advantages identified by prior theory, namely network effects and switching costs.</p><p>We show when, how and why such incumbent advantages are overcome by a new standard. We find that Linux adoption within organizations began for uses with a comparatively limited scope of deployment, thus minimizing network effect and switching costs disadvantages. We identify four attributes of information systems that potentially limit the scope of deployment: few links of the system to organizational processes, special-purpose computer systems, new uses and replacement of obsolete systems. We also identify an organizational level variable \&mdash; internal standardization \&mdash; which increases scope of deployment and thus the attractiveness of the incumbent standard.</p><p>\&nbsp;</p>},
	author = {Joel West and Dedrick, Jason}
}
@conference {709,
	title = {Software Patents and Open Source Software in the European Union: Evidences of a Trade-Off?},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {349 - 351},
	publisher = {Springer},
	organization = {Springer},
	abstract = {The present work aims at giving an account of the patenting behaviour in the software sector, focusing on the European Union and pointing out issues regarding a trade-off which would support a policy attitude in favour of a wider diffusion of the Open Source model.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_41},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Software\%20Patents\%20and\%20Open\%20Source\%20Software.pdf},
	author = {Rentocchini, Francesco and De Prato, Giuditta}
}
@conference {678,
	title = {A tool to support the introduction of GNU/Linux desktop system in a professional environment},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {253 - 260},
	publisher = {Springer},
	organization = {Springer},
	abstract = {The introduction of a GNU/Linux-based desktop system in a large company is often problematic, in terms of technical issues but especially for employees{\textquoteright} training costs. Mainly, these obstacles are represented by different hardware configurations that might require several ad-hoc activities to adapt a standard release to the specific environment, including company{\textquoteright}s application profile. On the other hand, GNU/Linux live distributions provide to the users{\textquoteright} community new and interesting capabilities, as self-configuration and better usability, but loosing compatibility with original distributions, that is unaffordable in professionals scenarios. DSS (Debased Scripts Set) is an answer to both questions. It is a live distribution that includes an unmodified Debian-based Linux release and a modular-designed file system.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_25},
	attachments = {https://flosshub.org/sites/flosshub.org/files/A\%20tool\%20to\%20support\%20the\%20introduction.pdf},
	author = {Di Cerbo, Francesco and Favara, Daniele and Scotto, Marco and Sillitti, Alberto and Succi, Giancarlo and Vernazza, Tullio}
}
@conference {714,
	title = {Towards an Ontology for Open Source Software Development},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {65 - 75},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Software development is a knowledge intensive process and the information generated in open source software development projects is typically housed in a central Internet repository. Open source repositories typically contains vast amounts of information, much of it unstructured, meaning that even if a question has previously been discussed and dealt with it is not a trivial task to locate it. This can lead to rework and confusion amongst developers and possibly deter new developers from getting involved in the project in the first place. This paper will present the case for an open source software development ontology. Such an ontology would enable better categorization of information and the development of sophisticated knowledge portals in order to better organize community knowledge and increase efficiency in the open source development process.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Towards\%20an\%20Ontology\%20for\%20OSS\%20Development.pdf},
	author = {Simmons, Gregory and Dillon, Tharam}
}
@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 {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 {766,
	title = {Economics approaching OSS: reviewing 15 years of debate},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {268},
	abstract = {The work aims at reviewing the theoretical literature on the development and diffusion of Open Source Software (OSS) relevant to an economic approach. It provides a synthetic picture of the areas of economic analysis for OSS, by attempting to frame relevant research efforts into a taxonomy based on attributes of innovation and process of diffusion. The main contributions investigating in the past decade the economic theoretical models beyond the {\textquotedblleft}open{\textquotedblright} way of producing and distributing software goods analyse: i) its supposed nature of complex public good, ii) the production process and distributed work organisation, iii) the evaluation of its impact on the software market, both at market level and at firm level. The relationship of the open source model with knowledge appropriation and reuse, and with innovation diffusion to support economic growth and social wealth would help drawing related economics and policy issues.},
	url = {http://pascal.case.unibz.it/handle/2038/765},
	author = {De Prato, Giuditta}
}
@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}
}
@article {DBLP:journals/tse/Dinh-TrongB05,
	title = {The FreeBSD Project: A Replication Case Study of Open Source Development},
	journal = {IEEE Trans. Software Eng.},
	volume = {31},
	number = {6},
	year = {2005},
	note = {" we obtained the necessary data from the [FreeBsd] CVS repository, the bug report database, and the e-mail archive. The CVS repository contains all of the code and related documentation that is committed to the project from 1993 until the present. The bug report database contains information describing all reported problems, as well as the status (such as fixed, under test, or open) of each problem. Each bug report is called a PR and assigned a reference number. The e-mail archive contains every e-mail message exchanged between the developers since 1994."

d/l: research.cs.queensu.ca/~ahmed/home/teaching/.../F06/.../free-bsd.pdf},
	pages = {481-494},
	abstract = {Case studies can help to validate claims that open source software development produces higher quality software at lower cost than traditional commercial development. One problem inherent in case studies is external validity{\textemdash}we do not know whether or not results from one case study apply to another development project. We gain or lose confidence in case study results when similar case studies are conducted on other projects. This case study of the FreeBSD project, a long-lived open source project, provides further understanding of open source development. The paper details a method for mining repositories and querying project participants to retrieve key process information. The FreeBSD development process is fairly well-defined with proscribed methods for determining developer responsibilities, dealing with enhancements and defects, and managing releases. Compared to the Apache project, FreeBSD uses 1) a smaller set of core developers{\textemdash}developers who control the code base{\textemdash}that implement a smaller percentage of the system, 2) a larger set of top developers to implement 80 percent of the system, and 3) a more well-defined testing process. FreeBSD and Apache have a similar ratio of core developers to people involved in adapting and debugging the system and people who report problems. Both systems have similar defect densities and the developers are also users in both systems.},
	keywords = {apache, bug reports, contributors, core, cvs, defect density, developers, email, email archive, freebsd, mailing list, scm, source code, users},
	doi = {10.1109/TSE.2005.73},
	attachments = {https://flosshub.org/sites/flosshub.org/files/DinhTrungBieman.pdf},
	author = {Trung T. Dinh-Trong and James M. Bieman}
}
@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 {750,
	title = {Open Source for e-Government Application Integration: a PHP-based solution},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {204-208},
	abstract = {This paper introduces UniGeINT - University of Genoa Integration Tool -, a framework designed to provide integration between several existing tools, databases and data repositories we used in internal administrative processes, by exploiting OSS benefits in terms of costs reduction and bug reporting. Moreover, it adopts state-of-art solutions in Enterprise Application Integration, by using specific design patterns able to match existing IT marrow. So we required in final product common features unmissable for a large scale corporative environment: reliability and fault tolerance, besides to a complete integration with anything previously developed.},
	url = {http://pascal.case.unibz.it/index.jsp},
	author = {Gammeri, Simone and Di Cerbo, Francesco and Scotto, Marco and Succi, Giancarlo and Vernazza, Tullio}
}
@conference {734,
	title = {Open Source Software in Public Administration. A real example OSS for egovernment Observatories},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {119-124},
	abstract = {Open Source Software (OSS) has risen to great prominence. Briefly, OSS programs are programs whose licenses give users the freedom to run the program for any purpose, to study and modify the program, and to redistribute copies of either the original or modified program (without having to pay royalties to previous developers). In the last years the Italian Public Administrations (PA) points out the benefits of using OSS as a valid alternative to closed source software. The goal of this paper is to illustrate the state of the art of OSS in Italian PA and describe two pratical examples of the use of OSS in the e-government area. Those examples are represented by the local e-government observatories developed respectively by Emilia Romagna and Liguria Regions. A real and settled knowledge about current and past egovernment initiatives in Italy can improve the future planning. For these reasons several Italian Regions developed Observatories for e-Government and Informatio...},
	url = {http://pascal.case.unibz.it/handle/2038/1208},
	author = {Davini, Emanuela and Faggioni, Elisabetta and Granatella, Giampiero and Tartari, Dimitri and Scotto, Marco}
}
@conference {757,
	title = {Proprietary Software and Open Source Philosophy: a shift in software{\textquoteright}s production methods},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {237-240},
	abstract = {The aim of this paper is to point out that, since the massive growth of Open Source Software (OSS), the production methods of software have changed. The change is not only recognisable within the OSS communities but most evident effects can be also observed in the {\textquotedblleft}proprietary{\textquotedblright} segment of the market. The data analysis has been performed by allocating a variation towards or away from cooperation/ competition according to the direction of about 12,000 communications, articles and technical notes dated from 1998 up to February 2005. A co-evolution path is identifiable: both the OSS and the proprietary models interchange their original market and production strategies. In the case of the OSS segment, market strategies becomes more business oriented; as a result, systems previously based solely on remote users/producers relations exchange some of the redundancy in its process in favour of a more businessdriven and coordinated production process. On the other hand, proprieta...},
	url = {ttp://pascal.case.unibz.it/handle/2038/1425},
	author = {De Prato, Giuditta and Gagliardi, Dimitri}
}
@conference {759,
	title = {Risk Assessment of an Open Source Migration Project},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {246-249},
	abstract = {In this paper we investigate the risks of an Open Source migration in the small Public Administration (PA) area. We consider not just technical risks (like security or reliability), but strategic issues (like e-government priorities, mid-term ownership cost items) and some social relations are also taken into consideration.},
	url = {http://pascal.case.unibz.it/handle/2038/1432},
	author = {Drozdik, Sylvester and Kov{\'a}cs, George L. and Kochis, P{\'a}l Zolt{\'a}n}
}
@article {flosswp232,
	title = {Seeking the Source: Software Source Code as a Social and Technical Artifact},
	year = {2005},
	month = {November},
	abstract = {In distributed software development, two sorts of dependencies can arise. The structure of the software system itself can create dependencies between software elements, while the structure of the development process can create dependencies between software developers. Each of these both shapes and reflects the development process. Our research concerns the extent to which, by looking uniformly at artifacts and activities, we can uncover the structures of software projects, and the ways in which development processes are inscribed into software artifacts. We show how a range of organizational processes and arrangements can be uncovered in software repositories, with implications for collaborative work in large distributed groups such as open source communities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/desouza.pdf},
	author = {De Souza, Cleidson and Jon Froehlich and Paul Dourish}
}
@article {springerlink:10.1007/s10606-005-9000-1,
	title = {Socialization in an Open Source Software Community: A Socio-Technical Analysis},
	journal = {Computer Supported Cooperative Work (CSCW)},
	volume = {14},
	year = {2005},
	note = {"I present the results of my analyses of participation patterns in a particular OSS project, used as a case study: Python. More precisely, I use the Open Source Project Browser to qualitatively track and analyze the trajectories of several project members who evolved (or not) into full-fledged participants. This allows me to later discuss how socialization proceeds in an OSS community such as Python"

"Over the course of 2002, I progressively retrieved the entire email archive of python-dev (the developers{\textquoteright} mailing list) and the CVS source tree for the project. "

"I read the entirety of the messages written by these participants and also looked at the software code they produced. There were striking similarities between their progressions over time, which I will de- scribe shortly. Overall the trajectory of these participants reflects successful socialization in Python: an evolution from newcomer to developer."

http://www2.parc.com/csl/members/nicolas/documents/JCSCW-OSS.pdf},
	pages = {323-368},
	publisher = {Springer Netherlands},
	abstract = {Open Source Software (OSS) development is often characterized as a fundamentally new way to develop software. Past analyses and discussions, however, have treated OSS projects and their organization mostly as a static phenomenon. Consequently, we do not know how these communities of software developers are sustained and reproduced over time through the progressive integration of new members. To shed light on this issue I report on my analyses of socialization in a particular OSS community. In particular, I document the relationships OSS newcomers develop over time with both the social and material aspects of a project. To do so, I combine two mutually informing activities: ethnography and the use of software specially designed to visualize and explore the interacting networks of human and material resources incorporated in the email and code databases of OSS. Socialization in this community is analyzed from two perspectives: as an individual learning process and as a political process. From these analyses it appears that successful participants progressively construct identities as software craftsmen, and that this process is punctuated by specific rites of passage. Successful participants also understand the political nature of software development and progressively enroll a network of human and material allies to support their efforts. I conclude by discussing how these results could inform the design of software to support socialization in OSS projects, as well as practical implications for the future of these projects.},
	keywords = {cvs, developers, email, email archive, mailing list, open source project browser, participation, python, scm, source code, team, tools},
	issn = {0925-9724},
	url = {http://dx.doi.org/10.1007/s10606-005-9000-1},
	author = {DUCHENEAUT, NICOLAS}
}
@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 {788,
	title = {Structure, Cohesion, and Open Source Software Success},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {317-319},
	abstract = {This paper proposes a dissertation designed to understand how the open source software (OSS) development group and its associated interest community jointly and independently impact OSS success for a single OSS project.},
	keywords = {interest community, network externalities, open source software, software quality},
	url = {http://pascal.case.unibz.it/handle/2038/1536},
	author = {Sherae Daniel}
}
@article {flosswp296,
	title = {Thematic Coherence and Quotation Practices in Open Source Software design-oriented online discussions},
	journal = {Group {\textquoteright}05 Conference Proceedings},
	year = {2005},
	month = {November},
	publisher = {ACM},
	abstract = {This paper presents an analysis of online discussions in Open Source Software (OSS) design. The objective of our work is to understand and model the dynamics of OSS design that take place in mailing list exchanges. We show how quotation practices can be used to locate design relevant data in discussion archives. OSS developers use quotation as a mechanism to maintain the discursive context. To retrace thematic coherence in the online discussions of a major OSS project, Python, we follow how messages are linked through quotation practices. We compare our quotation-based analysis with a more conventional analysis: a thread-based of the reply-to links between messages. The advantages of a quotation-based analysis over a thread-based analysis are outlined. Our analysis reveals also the links between the social structure and elements in the discussion space and how it shapes influence in the design process.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Barcellinietal.pdf},
	author = {F. Barcellini and F. Detienne and J. M. Burkhardt and W. Sack}
}
@conference {797,
	title = {Transfering Libre Software Development Practices to the Production of Educational Resources: the Edukalibre Project},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {341-348},
	abstract = {The transfer of methodologies common in libre (free, open source) sofware development to the domain of educational resources can radically change the way educational content is developed and used, enabling both educational practitioners and students to become actively involved in its creation and distribution. New software architectures and tools are needed to effectively support this process. This paper describes a platform aimed to support the creation of free, collaboratively constructed educational content on the web, which has been developed within the Edukalibre project. It provides easy access to core technologies: a control version system combined with conversion tools to produce several convenient formats for each document. Its modular architecture offers many different interfaces to the users. The Edukalibre platform is distributed as libre software.},
	keywords = {educational resources, information systems, open source, software development practices},
	url = {http://pascal.case.unibz.it/handle/2038/1548},
	author = {Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Chris Tebb and Vania Dimitrova and Chaparro, Diego and Romera, Teo}
}
@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 {727,
	title = {Virtual Square},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {76-81},
	abstract = {It is common to call {\textquotedblleft}virtual world{\textquotedblright} the set of abstractions given to humans by computers and networks. When the computers and the networks are emulated by programs, i.e. are virtual machines and virtual networks, there is one more layer of virtuality: a kind of virtual squared world. Virtual square (V{\texttwosuperior}) is the project to study how to exploit the possibilities given by multi layered virtuality. V{\texttwosuperior} integrates the existing technologies in system emulation with a new overlay network that is able to integrate virtual machines, real computers and processes. The virtual networking infrastructure, the educational virtual machine uMPS and the user level network virtual machine Ale4NET are original contributions made by this project. All the code developed for Virtual Square as well as all the code of the other virtual machines presented here have been released as Open Source or Free Software.},
	url = {http://pascal.case.unibz.it/handle/2038/1560},
	author = {Davoli, Renzo}
}
@article {flosswp1738,
	title = {Why and how-to contribute to libre software when you integrate them into an in-house application ?},
	journal = {Proceedings of the 1st International Conference on Open Source Systems},
	year = {2005},
	month = {June},
	pages = {113{\textendash}118},
	abstract = {Free or open source software are common tools that everybody can use and customise at its convenience to create in-house applications. Using and customising free software is not sufficient to ensure that this in-house application will be maintainable at mid or long term. This paper draws lessons from our in-house project, the development of a groupware Web platform for researchers, to help defining a policy through which efficient contributions can be made to open source software so that the in-house projects may remain viable.},
	author = {Christian Bac and Olivier Berger and V{\'e}ronique Deborde and Benoit Hamet}
}
@conference {801,
	title = {Workshop on "Open Source and Multimedia"},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {360},
	author = {Julien Bourgeois and Fran{\c c}ois Spies and Dodero, Gabriella and Vittoria Gianuzzi}
}
@article {flosswp193,
	title = {Advancing Economic Research on the Free and Open Source Software Mode of Production},
	year = {2004},
	month = {December},
	abstract = {Early contributions to the academic literature on free/libre and open source software (F/LOSS) movements have been directed primarily at identifying the motivations that account for the sustained and often intensive involvement of many people in this non-contractual and unremunerated productive activity. This issue has been particularly prominent in economists{\textquoteright} contributions to the literature, and it reflects a view that widespread voluntary participation in the creation of economically valuable goods that is to be distributed without charge constitutes a significant behavioral anomaly. Undoubtedly, the motivations of F/LOSS developers deserve to be studied more intensively, but not because their behaviors are unique, or historically unprecedented. In this essay we argue that other aspects of the "open source" phenomenon are just as intriguing, if not more so, and possibly are also more consequential topics for economic analysis. We describe the re-focusing and re-direction of empirical and theoretical research in an integrated international project (based at Stanford University/SIEPR) that aims at better understanding a set of less widely discussed topics: the modes of organization, governance and performance of F/LOSS development {\textendash} viewed as a collective distributed mode of production.. We discuss of the significance of tackling those questions in order to assess the potentialities of the "open source way of working" as a paradigm for a broader class of knowledge and information-goods production, and conclude with proposals for the trajectory of future research along that line.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/davidetal.pdf},
	author = {Jean-Michel Dalle}
}
@article {flosswp143,
	title = {Appropriating the Commons: Firms in Open Source Software},
	year = {2004},
	month = {April},
	abstract = {Firms in open source software (OSS) are active in a field encompassing all the characteristics of a public good, given the non-excludability and non-rivalry nature of OSS. As the case of OSS demonstrates, the fact that many important inputs to the innovative process are public should not be taken to mean that innovators are prevented from capturing private returns. The objective of this paper is to explore how firms appropriate returns from innovations that are created outside the boundaries of firms and in the public domain using the case of OSS. To do so, the paper draws upon an explorative multiple case study of six small firms that attempt to appropriate returns from OSS, with rich empirical evidence from various data sources. The cases illustrate how firms try a variety of approaches to appropriate adequate returns and that selling services seem to be the dominant trend. Firm also balance the relative inefficiency of traditional means of intellectual property right such as patents by putting greater emphasis on first mover advantages and creating network externalities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dahlander2.pdf},
	author = {Linus Dahlander}
}
@article {flosswp203,
	title = {The critical delusion of the condition of digitisation},
	year = {2004},
	month = {December},
	abstract = {This essay analyses how digital media prosthetics, institutionalisation (in particular the manifestations of copyright and patent law which lurk behind vested interests in controlling the transition to a vastly more powerful new world), and the imperatives of corporate planning have come into a conflict so fierce that shared lived experience, increasingly, is forced to undergo a rapid process of commodification. This struggle, which can no longer be defined through the lens of geography or class alone, in turn, points to a not too distant future in which commons-based peer production/consumption is exploited within the context of intense social taylorism and digital fordism with the ultimate goal to turn culture into a paid-for experience, and hence moving the terrain of struggle away from the surplus value of labour to the legitimacy of knowledge sharing and pervasive networking, and how the latter can be monetised and controlled in accordance with anarcho-capitalist agendas. Obviously, the question which we ought to pose to ourselves is how the revolutionary demands of hacking can be guided, assembled, and reproduced, so that this process of commodification is consciously resisted by technology developers and users alike, artists, and all those whose creativity and desire for socially conscious technological innovation and emergent social co-operation have been enhanced by the digital condition we{\textquoteright}re increasingly in the centre of.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dafermos_ccc.pdf},
	author = {George Dafermos}
}
@conference {Xinyi04fourinteresting,
	title = {Four Interesting Ways in Which History Can Teach Us About Software},
	booktitle = {Proceedings of the 2004 international workshop on Mining software repositories  - MSR {\textquoteright}04},
	year = {2004},
	month = {05/2004},
	pages = {58-62},
	abstract = {In this position paper, we outline four kinds of studies that we have undertaken in trying to understand various aspects of a software system{\textquoteright}s evolutionary history. In each instance, the studies have involved detailed examination of real software systems based on {\textquotedblleft}facts{\textquotedblright} extracted from various kinds of source artifact repositories, as well as the development of accompanying tools to aid in the extraction, abstraction, and comprehension processes. We briefly discuss the goals, results, and methodology of each approach.},
	keywords = {ant, apache, change analysis, clone, clone detection, cvs, evolution, gcc, growth, kepler, linux, midworld, mycore, postgresql, source code, version control},
	attachments = {https://flosshub.org/sites/flosshub.org/files/58FourInterestingWays.pdf},
	author = {Michael Godfrey and Xinyi Dong and Cory Kapser and Lijie Zou}
}
@conference {1105,
	title = {Free \& Open Source Software Creation and {\textquoteleft}the Economy of Regard{\textquoteright}},
	booktitle = {Third EPIP Workshop},
	year = {2004},
	month = {04/2004},
	keywords = {linux, linux kernel, scm, source code},
	attachments = {https://flosshub.org/sites/flosshub.org/files/DalleDavidGhosh\%20Wolak.pdf},
	author = {Jean-Michel Dalle and Paul A. David and Rishab Ayer Ghosh and Frank A. Wolak}
}
@conference {1050,
	title = {Mining version control systems for FACs (frequently applied changes)},
	booktitle = {International Workshop on Mining Software Repositories (MSR 2004)},
	volume = {2004},
	year = {2004},
	pages = {48 - 52},
	publisher = {IEE},
	organization = {IEE},
	address = {Edinburgh, Scotland, UK},
	abstract = {Today, programmers are forced to maintain a software system based on their gut feeling and experience. This paper makes an attempt to turn the software maintenance craft into a more disciplined activity, by mining for frequently applied changes in a version control system. Next to some initial results, we show how this technique allows to recover and study successful maintenance strategies, adopted for the redesign of long{\textendash}lived systems.},
	keywords = {ccfinder, change analysis, change history, clone, clone detection, cvs, maintenance, tomcat, version control},
	doi = {10.1049/ic:20040475},
	attachments = {https://flosshub.org/sites/flosshub.org/files/48MiningVersion.pdf},
	author = {Van Rysselberghe, F. and Demeyer, S}
}
@article {flosswp192,
	title = {SimCode: Agent-based Simulation Modelling of Open-Source Software Development},
	year = {2004},
	month = {November},
	abstract = {We present an original modeling tool, which can be used to study the mechanisms by which free/libre and open source software developers{\textquoteright} code-writing efforts are allocated within open source projects. It is first described analytically in a discrete choice framework, and then simulated using agent-based experiments. Contributions are added sequentially to either existing modules, or to create new modules out of existing ones: as a consequence, the global emerging architecture forms a hierarchical tree. Choices among modules reflect expectations of peer-regard, i.e. developers are more attracted a) to generic modules, b) to launching new ones, and c) to contributing their work to currently active development sites in the project. In this context, we are able - particularly by allowing for the attractiveness of "hot spots"{\textendash} to replicate the high degree of concentration (measured by Gini coefficients) in the distributions of modules sizes. The latter have been found by empirical studies to be a characteristic typical of the code of large projects, such as the Linux kernel. Introducing further a simple social utility function for evaluating the mophology of "software trees," it turns out that the hypothesized developers{\textquoteright} incentive structure that generates high Gini coefficients is not particularly conducive to producing self-organized software code that yields high utility to end-users who want a large and diverse range of applications. Allowing for a simple governance mechanism by the introduction of maintenance rules reveals that "early release" rules can have a positive effect on the social utility rating of the resulting software trees.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dalledavid2.pdf},
	author = {Jean-Michel Dalle}
}
@proceedings {1189,
	title = {Toward Collaborative Open-Source Technology Transfer},
	year = {2004},
	pages = {34-42},
	abstract = {We analyze several occurrences of open-source technology transfer where research tools or prototypes developed in academic environments are transferred to private actors to be exploited economically. We enlight common characteristics which lead us to suggest that academic duality is a general consequence of the academic design of research tools and prototypes, and that the associated high transfer costs could be reduced first by implementing dual versioning using a dual licensing scheme, by associating a new academic public license with a traditional technology transfer one, and second through the transparent and shared maintenance of products built according to a dual architecture, as it would be precisely allowed by a dedicated collaborative development platform such as LibreSource.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dalle35-43.pdf},
	author = {Jean-Michel Dalle and Guillame Rousseau}
}
@article {flosswp83,
	title = {The Allocation of Software Development Resources in {\textquoteright}Open Source{\textquoteright} Production},
	year = {2003},
	month = {February},
	abstract = {The paper develops a stochastic simulation model capable of describing the decentralized, micro-level decisions that allocate programming resources both within and among open source/free software (OS/FS) projects, and which critically shape their growth. The core or behavioral kernel of our simulation tool is based on dynamic "growing" trees, and incorporates the effects of the reputational reward structure of OS/FS communities as characterized by Eric S. Raymond (1998). In this regard, our line of investigation also follows recent approaches associated with studies of academic researchers in ?open science? communities. For the purposes of this first step, we mainly focus on showing the ways in which the specific norms of the reward system and organizational rules can shape emergent properties of projects, and we also point to a validation in this framework of the often adovcated, but yet mainly empirical "release early" rule.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dalledavid.pdf},
	author = {Jean-Michel Dalle}
}
@article {flosswp133,
	title = {Blogging the Market},
	year = {2003},
	month = {December},
	abstract = {Weblogs have been recently characterised as the "open source media". And in much the same way that open source software is been deployed, marketed and sold within both commercial and non-commercial contexts, weblogs can advance both commercial and non-commercial objectives. However, in this primary - research paper, the focus is on the benefits that organisations can seize by embracing weblogs, and how weblogs are bound to revitalise marketplace and workplace conversations. In addition, several case studies are being analysed, ranging from Slashdot and Openflows to Amazon, Macromedia, Groove Networks, and Gizmodo.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dafermos3.pdf},
	author = {George Dafermos}
}
@conference {DBLP:conf/pakdd/ChawlaAD03,
	title = {Mining Open Source Software (OSS) Data Using Association Rules Network},
	booktitle = {Lecture Notes in Computer Science },
	volume = {2637},
	year = {2003},
	pages = {461-466},
	abstract = {The Open Source Software(OSS) movement has attracted considerable attention in the last few years. In this paper we report our results of mining data acquired from SourceForge.net, the largest open source software hosting website. In the process we introduce Association Rules Network(ARN), a (hyper)graphical model to represent a special class of association rules. Using ARNs we discover important relationships between the attributes of successful OSS projects. We verify and validate these relationships using Factor Analysis, a classical statistical technique related to Singular Value Decomposition(SVD).},
	keywords = {arn, association rules, factor analysis, project success, sourceforge, svd},
	author = {Sanjay Chawla and Bavani Arunasalam and Joseph G. Davis}
}
@article {flosswp115,
	title = {Neither market or hierarchy or network: The emerging bazaar governance},
	year = {2003},
	month = {September},
	abstract = {Despite the growing body of literature describing the open-source phenomenon, few contributions have been theoretically grounded and research has largely focused on the software industry. Drawing on transaction cost economics, we go beyond these limitations and advance that open source constitutes a new generic governance structure?which we label bazaar governance? based on a specific contract. We characterize this structure in terms of its strengths and weaknesses and in comparison with market, firm and network structures. We consider how bazaar governance is actualized within an industry and the institutional entrepreneur?s crucial role in this process. Finally, we propose that bazaar governance has a profound impact on the structure of the industry in which it is introduced.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/demillecocq.pdf},
	author = {Benoit Demil}
}
@proceedings {1168,
	title = {Towards a Product Model of Open Source Software in a Commercial Environment},
	year = {2003},
	pages = {31-37},
	attachments = {https://flosshub.org/sites/flosshub.org/files/31-37.pdf},
	author = {Deng, J. and Seifert, T. and Vogel, S.}
}
@article {100,
	title = {Trust, control and the role of interorganizational systems in electronic partnerships},
	journal = {Information Systems Journal},
	volume = {13},
	number = {2},
	year = {2003},
	note = {Times Cited: 12},
	pages = {159-190},
	abstract = {To survive and thrive in today{\textquoteright}s competitive marketplace, organizations are increasingly migrating to new organizational structures in which partnerships and interorganizational systems (IOSs) are becoming more important. The success of these partnerships depends on both trust and control - complex constructs that act on and shape each other over time. Many organizations assume that high levels of trust are necessary for net-enabled electronic partnerships. We examine this assumption from two perspectives: the initial decision to enter into a partnership or alliance, and its ongoing operation. Our findings suggest that researchers have treated trust simplistically, failing to distinguish the need for trust (which is inversely related to the organization{\textquoteright}s ability to control its partners) and the level of trust (which is an actual quantity that may change during the lifetime of the partnership). In many organizations, there is a gap between these two trust dimensions, which management attempts to close by changing the level of control. In this process, the IOS is key. To understand the relationship of IOS use to trust and control, we applied structured content analysis and analytic induction to 16 published case studies and used the results to create a framework for relating trust and control. At the heart of the framework is the recognition that trust and control are not simple substitutes for each other. Rather, they form a dialectic, where it makes sense to consider each construct only in relationship to the other. Using the framework, we identify areas for follow-up research and suggestions for practitioners.},
	author = {Gallivan, M. J. and Depledge, G.}
}
@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.}
}
@article {flosswp22,
	title = {Open-Source vs. Proprietary Software},
	year = {2002},
	month = {January},
	abstract = {The article studies technological competition between open-source and proprietary software using a model from interaction theory. We argue that the organizational structure of open-source software, allowed by openness of source codes and by the subsequent development of dedicated communities, is a key feature which, together with compatibility, can allow open-source software to overcome existing proprietary standards.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dalle2.pdf},
	author = {Jean-Michel Dalle and Nicolas Jullien}
}
@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}
}
@conference {1141,
	title = {Corporate Source: Applying Open Source Concepts to a Corporate Environment},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	keywords = {commercial software, hewlett packard, hp, organizational sponsorship},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dinkelackergarg.pdf},
	author = {Dinkelacker, J. and Garg, P.K.}
}
@unpublished {flosswp21,
	title = {Management and Virtual Decentralized Networks: The Linux Project},
	year = {2001},
	month = {September},
	abstract = {This paper examines whether geographically dispersed knowledge workers can virtually collaborate for a project under no central planning. Co-ordination, management and the role of knowledge arise as the central areas of focus. The Linux Project and its development model are selected as a case of analysis and the critical success factors of this organizational design are identified. The study proceeds to the formulation of a framework that can be applied to all kinds of virtual decentralized work and concludes that value creation is maximized when there is intense interaction and uninhibited sharing of information between the organization and the surrounding community.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/dafermoslinux.pdf},
	author = {George Dafermos}
}
@article {912,
	title = {Open Source Standardization: The Rise of Linux in the Network Era},
	journal = {Knowledge, Technology \& Policy},
	volume = {14},
	year = {2001},
	pages = {88-112},
	abstract = {To attract complementary assets, firms that sponsor proprietary de facto compatibility standards must trade off control of the standard against the imperative for adoption. For example, Microsoft and Intel in turn gained pervasive adoption of their technologies by appropriating only a single layer of the standards architecture and encouraging competition in other layers. In reaction to such proprietary strategies, the open source movement relinquished control to maximize adoption. To illustrate this, we examine the rise of the Linux operating system from 1995-2001, particularly the motivations of organizational buyers and suppliers of complementary assets, and Microsoft?s reaction to its success.},
	author = {Joel West and Dedrick, Jason}
}
