@proceedings {1895,
	title = {How are Developers Treating License Inconsistency Issues? A Case Study on License Inconsistency Evolution in FOSS Projects},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {69-79},
	publisher = {Springer},
	abstract = {A license inconsistency is the presence of two or more source files that evolved from the same original file containing different licenses. In our previous study, we have shown that license inconsistencies do exist in open source projects and may lead to potential license violation problems. In this study, we try to find out whether the issues of license inconsistencies are properly solved by analyzing two versions of a FOSS distribution{\textemdash}Debian{\textemdash}and investigate the evolution patterns of license inconsistencies. Findings are: license inconsistencies occur mostly because the original copyright owner updated the license while the reusers were still using the old version of the source files with the old license; most license inconsistencies would disappear when the reusers synchronize their project from the upstream, while some would exist permanently if reusers decide not to synchronize anymore. Legally suspicious cases have not been found yet in those Debian distributions.},
	keywords = {Code clone, debian, License inconsistency, licenses, Software license},
	doi = {10.1007/978-3-319-57735-7_8},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_8},
	author = {Y. Wu and Manabe, Yuki and Daniel M. Germ{\'a}n and Inoue, K.}
}
@proceedings {1909,
	title = {How Does Contributors{\textquoteright} Involvement Influence the Build Status of an Open-Source Software Project?},
	year = {2017},
	note = {We used the data released by TravisTorrent
on 06-Dec-2016 as our main data source.},
	month = {05/2017},
	pages = {475-478},
	abstract = {The recent introduction of the pull-based development
model promoted agile development practices such as
Code Reviews and Continuous Integration (CI). CI, in particular,
is currently a standard development practice in opensource
software (OSS) projects. Although it is well-known that
OSS contributors have different involvements (e.g., while some
developers drive the project, there is a long tail of peripheral
developers), little is known about how the contributor{\textquoteright}s degree
of participation can influence the build status of an OSS project.
Through TravisTorrent{\textquoteright}s dataset, we compare the success rates
of builds made by casual and non-casual contributors and what
factors on their contributions may influence the build result. Our
results suggest that there is no representative difference between
their build success (they are similar in 85\% of the analyzed
projects), meaning that being a casual contributor is not a strong
indicator for creating failing builds. Also, factors like the size
of their contributions and the number of project configurations
(jobs) have the potential of impacting the build success.},
	keywords = {travis torrent},
	author = {Reboucas, Marcel and Santos, Renato O. and Pinto, Gustavo and Fernando Castor}
}
@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 {Poo-Caama{\~n}o2016,
	title = {Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem},
	booktitle = {Open Source Systems: Integrating Communities: 12th IFIP WG 2.13 International Conference, OSS 2016, Gothenburg, Sweden, May 30 - June 2, 2016, Proceedings},
	year = {2016},
	pages = {147{\textendash}162},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {Herding Cats: A Case Study of Release Management in an Open Collaboration Ecosystem},
	address = {Cham},
	abstract = {Release management in large-scale software development projects requires significant communication and coordination. It is particularly challenging in Free and Open Source Software (FOSS) ecosystems, in which hundreds of loosely connected developers and their projects need to be coordinated to release software to a schedule. To better understand this process and its challenges, we analyzed over two and half years of communication in the GNOME ecosystem and studied developers{\textquoteright} interactions. We cataloged communication channels, categorized high level communication and coordination activities in one of them, and triangulated our results by interviewing developers. We found that a release schedule, influence instead of direct control, and diversity are factors that impact positively the release process in the GNOME ecosystem. Our results can help organizations build better large-scale teams and show that research focused on individual projects might miss important parts of the picture.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_12},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_12},
	author = {Poo-Caama{\~n}o, Germ{\'a}n and Singer, Leif and Knauss, Eric and Daniel M. German},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@proceedings {1808,
	title = {How Do Free/Open Source Developers Pick Their Tools? A Delphi Study of the Debian Project},
	year = {2016},
	abstract = {Free and Open Source Software (FOSS) has come to play a critical role in the global software industry. Organizations are widely adopting FOSS and interacting with open source communities, and hence organizations have a considerable interest in seeing these communities flourishing. Very little research has focused on the tools used to develop that software. Given the absence of organizational policies and mandate that would occur in a traditional environment, an open question is how FOSS developers decide what tools to use. In this paper we report on a policy delphi study conducted in the Debian Project, one of the largest FOSS projects. Drawing from data collected in three phases from a panel of 21 experts, we identified 15 factors that affect their decision to adopt tools. This in turn can help FOSS communities to define a suitable policy of actions, in order to improve their processes.},
	keywords = {Delphi, Free/Open Source Software, Qualitative Study, study, tools},
	url = {https://www.researchgate.net/publication/291312269_How_Do_FreeOpen_Source_Developers_Pick_Their_Tools_A_Delphi_Study_of_the_Debian_Project},
	author = {Martin Krafft and Stol, Klaas-Jan and Fitzgerald, Brian}
}
@proceedings {1826,
	title = {How Software Developers Use Work Breakdown Relationships in Issue Repositories},
	year = {2016},
	month = {05/2016},
	pages = {281-285},
	abstract = {Software developers use issues as a means to describe a range
of activities to be undertaken on a software system, including
features to be added and defects that require fixing. When
creating issues, software developers expend manual effort
to specify relationships between issues, such as one issue
blocking another or one issue being a sub-task of another.
In particular, developers use a variety of relationships to express
how work is to be broken down on a project. To better
understand how software developers use work breakdown relationships
between issues, we manually coded a sample of
work breakdown relationships from three open source systems.
We report on our findings and describe how the recognition
of work breakdown relationships opens up new ways
to improve software development techniques.},
	doi = {http://dx.doi.org/10.1145/2901739.2901779},
	author = {C. Albert Thompson and Murphy, Gail C. and Palyart, Marc and Marko Ga{\v s}paric}
}
@proceedings {1771,
	title = {A Historical Analysis of Debian Package Incompatibilities},
	year = {2015},
	abstract = {Users and developers of software distributions are often confronted with installation problems due to conflicting packages. A prototypical example of this are the Linux distributions such as Debian. Conflicts between packages have been studied under different points of view in the literature, in particular for the Debian operating system, but little is known about how these package conflicts evolve over time. This article presents an extensive analysis of the evolution of package incompatibilities, spanning a decade of the life of the Debian stable and testing distributions for its most popular architecture, i386. Using the technique of survival analysis, this empirical study sheds some light on the origin and evolution of package incompatibilities, and provides the basis for building indicators that may be used to improve the quality of package-based distributions.
},
	url = {http://di.umons.ac.be/details.aspx?pub=b5a887bd-0612-4439-8f66-ec37803a32db},
	author = {Claes Maelick and Mens Tom and Di Cosmo Robert and Vouillon Jerome}
}
@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.}
}
@conference {1692,
	title = {Hackers on Forking},
	booktitle = {The International SymposiumProceedings of The International Symposium on Open Collaboration - OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1 - 10},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {Berlin, GermanyNew York, New York, USA},
	abstract = {All open source licenses allow the copying of an existing body of code for use as the basis of a separate development project. This practice is commonly known as forking the code. This paper presents the results of a study in which 11 programmers were interviewed about their opinions on the right to fork and the impact of forking on open source software development.

The results show that there is a general consensus among programmers{\textquoteright} views regarding both the favourable and unfavourable aspects that stem from the right to fork. Interestingly, while all programmers noted potential downsides to the right to fork, it was seen by all as an integral component of open source software, and a right that must not be infringed regardless of circumstance or outcome.},
	isbn = {9781450330169},
	doi = {10.1145/2641580.2641590},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p06.pdf},
	author = {Nyman, Linus}
}
@inbook {1594,
	title = {How Do Social Interaction Networks Influence Peer Impressions Formation? A Case Study},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {31-40},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {Due to their lack of physical interaction, Free and Open Source Software (FOSS) participants form impressions of their teammates largely based on sociotechnical mechanisms including: code commits, code reviews, mailing-lists, and bug comments. These mechanisms may have different effects on peer impression formation. This paper describes a social network analysis of the WikiMedia project to determine which type of interaction has the most favorable characteristics for impressions formation. The results suggest that due to lower centralization, high interactivity, and high degree of interactions between participants, the code review interactions have the most favorable characteristics to support impression formation among FOSS participants.},
	keywords = {COLLABORATION, FOSS, open source, OSS, social network analysis},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_4},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_4},
	author = {Bosu, Amiangshu and Carver, JeffreyC.},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@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}
}
@inbook {1618,
	title = {How to Support Newcomers Onboarding to Open Source Software Projects},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {199-201},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

While onboarding an open source software (OSS) project, contributors face many different barriers that hinder their contribution, leading in many cases to dropout. Many projects leverage the contribution of outsiders and the sustainability of the project relies on retaining some of these newcomers. In this research, we aim at understanding the barriers that hinder onboarding of newcomers to OSS projects, by means of different empirical approaches, and proposing a set of strategies that can be used to support the first step of newcomers.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_29},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_29},
	author = {Steinmacher, Igor and Gerosa, MarcoAur{\'e}lio},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Thorne:2014:YRM:2641580.2641582,
	title = {How You Run a Meeting Says a Lot About Your Values: Participatory Practices for Open Communities},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {42:1{\textendash}42:1},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Live events are some of the best ways to see the power dynamics and philosophical bent of a community. Many communities, open and closed, glorify sitting in a darkened room and being inspired by a sage on the stage. And then there are events about participation: making and learning with fellow participants around shared passions and interests. The session argues for the use of participatory methods at events as a way to manifest open values. We{\textquoteright}ll unpack some techniques and case studies, as well as practice ourselves.
},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641582},
	url = {http://doi.acm.org/10.1145/2641580.2641582},
	author = {Thorne, Michelle}
}
@proceedings {1510,
	title = {A Historical Dataset for the Gnome Ecosystem},
	year = {2013},
	month = {05/2013},
	abstract = {We present a dataset of the open source software ecosystem Gnome from a social point of view. We have collected historical data about the contributors to all Gnome projects stored on git.gnome.org, taking into account the problem of identity matching, and associating different activity types to the contributors. This type of information is very useful to complement the traditional, source-code related information one can obtain by mining and analyzing the actual source code. The dataset can be obtained at https://bitbucket.org/mgoeminne/sgl-flossmetric-dbmerge.},
	keywords = {cvsanaly, flossmetrics, gnome},
	author = {Mathieu Goeminne and Ma{\"e}lick Claes and Mens, Tom}
}
@conference {zmzkh-icsm-2013,
	title = {How does Context affect the Distribution of Software Maintainability Metrics?},
	booktitle = {Proceedings of the 29th IEEE International Conference on Software Maintainability},
	series = {ICSM {\textquoteright}13},
	year = {2013},
	note = {"FLOSSMole [25] is another data source, from
where we download descriptions (i.e., application domain)
of SourceForge software systems. Furthermore, we download
latest application domain information4
and monthly download
data5 of studied software systems directly from SourceForge."},
	abstract = {Software metrics have many uses, e.g., defect prediction, effort estimation, and benchmarking an organization against peers and industry standards. In all these cases, metrics may depend on the context, such as the programming language. Here we aim to investigate if the distributions of commonly used metrics do, in fact, vary with six context factors: application domain, programming language, age, lifespan, the number of changes, and the number of downloads. For this preliminary study we select 320 nontrivial software systems from SourceForge. These software systems are randomly sampled from nine popular application domains of SourceForge. We calculate 39 metrics commonly used to assess software maintainability for each software system and use Kruskal Wallis test and Mann-Whitney U test to determine if there are significant differences among the distributions with respect to each of the six context factors. We use Cliff{\textquoteright}s delta to measure the magnitude of the differences and find that all six context factors affect the distribution of 20 metrics and the programming language factor affects 35 metrics. We also briefly discuss how each context factor may affect the distribution of metric values.We expect our results to help software benchmarking and other software engineering methods that rely on these commonly used metrics to be tailored to a particular context.},
	keywords = {benchmark, context, contextual factor, flossmole, large scale, metrics, mining software repositories, sampling, software maintainability, sourceforge, static metrics},
	attachments = {https://flosshub.org/sites/flosshub.org/files/icsm2013_contextstudy.pdf},
	author = {Zhang, Feng and Audris Mockus and Ying Zou and Foutse Khomh and Hassan, Ahmed E.}
}
@book {1532,
	title = {How Healthy Is My Project? Open Source Project Attributes as Indicators of Success},
	series = {IFIP Advances in Information and Communication Technology Open Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	note = {"The dataset used has thus been obtained through a third source which has made
the data publicly available [18]. FlossMole.org contains data collected for the period
2006 to December 2009 from which a dataset was compiled of 125,700 projects. "},
	pages = {30 - 44},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {Determining what factors can influence the successful outcome of a software project has been labeled by many scholars and software engineers as a difficult problem. In this paper we use machine learning to create a model that can determine the stage a software project has obtained with some accuracy. Our model uses 8 Open Source project metrics to determine the stage a project is in. We validate our model using two performance measures; the exact success rate of classifying an Open Source Software project and the success rate over an interval of one stage of its actual performance using different scales of our dependent variable. In all cases we obtain an accuracy of above 70\% with one away classification (a classification which is away by one) and about 40\% accuracy with an exact classification. We also determine the factors (according to one classifier) that uses only eight variables among all the variables available in SourceForge, that determine the health of an OSS project.
},
	keywords = {flossmole, sourceforge},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_3},
	url = {http://link.springer.com/chapter/10.1007/978-3-642-38928-3_3},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OSSHealth_1.0.pdf},
	author = {Piggot, James and Amrit, Chintan},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@proceedings {1476,
	title = {How Can Open Standards Be Effectively Implemented in Open Source? Challenges and the ORIOS Project},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {383-388},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Many organisations are currently restricted in their choice of software because of restrictions imposed by existing systems. Challenges include a lack of interoperability and a risk of technological lock-in, which many small companies seek to address by utilising Open Standards and Open Source implementations of such standards when developing and deploying systems. This paper presents an overview of how the industrial research project ORIOS (Open Source software Reference Implementations of Open Standards) seeks to address identified challenges. An overarching goal of the project is to improve understanding within organisations of Open Standards, Open Source Reference Implementations, and the ecosystems around them. This will be done by developing a reference model of necessary and desirable features of an Open Standard, and how Open Standards and their implementations can be utilised by small companies in different usage contexts. An action case study approach will be used as a core strategy for evolving a reference model together with Swedish companies.},
	author = {Lundell, Bj{\"o}rn and AbduraHmanovic, Admir and Andersson, Stefan and Bergström, Erik and Feist, Jonas and Gamalielsson, Jonas and Gustavsson, Tomas and Kahlbom, Roger and Papaxanthis, Konstantin}
}
@article {1397,
	title = {How do open source communities blog?},
	journal = {Empirical Software Engineering},
	year = {2012},
	abstract = {We report on an exploratory study, which aims at understanding how software communities use blogs compared to conventional development infrastructures. We analyzed the behavior of 1,100 bloggers in four large open source communities, distinguishing between committing bloggers and other community members. We observed that these communities intensively use blogs with one new entry every 8 h. A blog entry includes 14 times more words than a commit message. When analyzing the content of the blogs, we found that committers and others bloggers write about similar topics. Most popular topics in committers{\textquoteright} blogs represent high-level concepts such as features and domain concepts, while source code related topics are discussed in 15\% of their posts. Other community members frequently write about community events and conferences as well as configuration and deployment topics. We found that the blogging peak period is usually after the software is released. Moreover, committers are more likely to blog after corrective engineering than after forward engineering and re-engineering activities. Our findings call for a hypothesis-driven research to (a) further understand the role of social media in dissolving the collaboration boundaries between developers and other stakeholders and (b) integrate social media into development processes and tools. },
	keywords = {blog, blogs},
	issn = {1573-7616},
	doi = {10.1007/s10664-012-9211-2},
	author = {Pagano, Dennis and Maalej, Walid}
}
@article {1519,
	title = {How the FLOSS Research Community Uses Email Archives},
	journal = {International Journal of Open Source Software and Processes},
	volume = {4},
	year = {2012},
	note = {classifies 72 FLOSS papers into various analysis categories},
	month = {12/2012},
	pages = {37 - 59},
	abstract = {Artifacts of the software development process, such as source code or emails between developers, are a frequent object of study in empirical software engineering literature. One of the hallmarks of free, libre, and open source software (FLOSS) projects is that the artifacts of the development process are publicly-accessible and therefore easily collected and studied. Thus, there is a long history in the FLOSS research community of using these artifacts to gain understanding about the phenomenon of open source software, which could then be compared to studies of software engineering more generally. This paper looks specifically at how the FLOSS research community has used email artifacts from free and open source projects. It provides a classification of the relevant literature using a publicly-available online repository of papers about FLOSS development using email. The outcome of this paper is to provide a broad overview for the software engineering and FLOSS research communities of how other researchers have used FLOSS email message artifacts in their work},
	keywords = {email, email archives, literature, mailing lists, review, Survey},
	issn = {1942-3934},
	doi = {10.4018/jossp.2012010103},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ijossp_v3_PREPRINT.pdf},
	author = {Squire, Megan}
}
@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 {1298,
	title = {Health Informatics: The Relevance of Open Source and Multilevel Modeling},
	year = {2011},
	month = {10/2011},
	pages = {338-347},
	publisher = {Springer},
	abstract = {Health information features significant spatial-temporal and domain complexities, which brings challenges to the implementation of patient-centered, interoperable and semantically coherent healthcare information systems. This position paper supports the idea that the multilevel modeling approach is essential to ensure interoperability at the semantic level, but true interoperability is only achieved by the adoption of open standards, and open source implementations are needed for promote competition based on software quality. The Multilevel Healthcare Information Modelling (MLHIM) specifications are presented as the fully open source multilevel modeling reference implementation, and best practices for the development of multilevel- based open source healthcare applications are suggested.},
	keywords = {Health informatics, multilevel modeling, open source software},
	author = {Cavalini, Luciana T. and Cook, Timothy W.}
}
@proceedings {1282,
	title = {A Historical Account of the Value of Free and Open Source Software: From Software Commune to Commercial Commons},
	year = {2011},
	note = {"In order to understand how perceptions of FOSS software have developed over time, we have traced justifying arrangements that historically have been used to define the value of FOSS. This has been done by going through canonical texts and previous research [3]; i.e. we look at research and publications considered to have had a major impact on the perception of FOSS...."

Software Commune, software bazaar, public commons},
	month = {10/2011},
	pages = {196-207},
	publisher = {Springer},
	abstract = {Free and open source software has transformed from what has been characterized as a resistance movement against proprietary software to become a commercially viable form of software development, integrated in various forms with proprietary software business. In this paper we explain this development as a dependence on historical formations, shaped by different ways of justifying the use of open source during different periods of time. These formations are described as arrangements of different justificatory logics within a certain time frame or a certain group of actors motivating the use of free and open source software by referring to different potentialities. The justificatory arrangements change over time, and tracing these changes makes it easier to understand how the cultural, economic and social practices of open source movements are currently being absorbed and adopted in a commercial context.},
	keywords = {Free and Open Source Software, Historical approach, Justification}
}
@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}
}
@article {1335,
	title = {Helping to Bridge the Digital Divide with Free Software and Services},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {13 - 27},
	abstract = {The growing importance of digital media in citizens{\textquoteright} participation in government is a major issue in obtaining government services, elections and campaigning in the 21st century. In order to participate in the consumption and creation of online media, citizens must have access to, and knowledge of, appropriate technology resources. There exists a gap between those who have access to technology and those who do not A gap commonly referred to as the digital divide. While there are many different aspects to the digital divide one of them is access to the software necessary to participate in digital media. A potential solution to the software component of the digital divide is the use of open source software and free online services. Implementing these solutions can play a part in narrowing the digital divide and producing better informed citizens more capable of participating in the modern electoral process.},
	issn = {1942-3934},
	doi = {10.4018/IJOSSP.2010100102},
	author = {Caudill, Jason G.}
}
@article {1327,
	title = {Higher Education and FOSS for e-Learning},
	journal = {International Journal of Open Source Software and Processes},
	volume = {2},
	year = {2010},
	pages = {15 - 31},
	abstract = {This paper examines the paradox of FOSS adoption in U.S. institutions of higher education, where campus-wide deployment of FOSS for e-learning lags far behind adoption for technical infrastructure applications. Drawing on the fields of organizational management, information systems, and education, the author argues that the gap between FOSS advocacy and the enterprise-wide deployment of FOSS for e-learning is a consequence of the divergent perspectives of two organizational sub-cultures{\textemdash}the technologist and the academic{\textemdash}and the extent to which those sub-cultures are likely to embrace FOSS. The author recommends (a) collaborative needs analysis/assessment prior to a go/no go adoption decision, and (b) broad dissemination of total cost of ownership (TCO) data by institutions deploying FOSS for e-learning enterprise-wide. This discussion satisfies e-learning administrators and practitioners seeking research-based, cross-disciplinary evidence about the FOSS decision-making process and also assists educators seeking to expand student knowledge of e-learning technology options. },
	keywords = {education},
	issn = {1942-3934},
	doi = {10.4018/jossp.2010010102},
	author = {Williams van Rooij, Shahron}
}
@conference {578,
	title = {Heartbeat: Measuring Active User Base and Potential User Interest in FLOSS Projects},
	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 = {94 - 104},
	publisher = {Springer},
	organization = {Springer},
	chapter = {10},
	abstract = {This paper presents a novel method and algorithm to measure the size of an open source project{\textquoteright}s user base and the level of potential user interest that it generates. Previously unavailable download data at a daily resolution confirms hypothesized patterns related to release cycles. In short, regular users rapidly download the software after a new release giving a way to measure the active user base. In contrast, potential new users download the application independently of the release cycle, and the daily download figures tend to plateau at this rate when a release has not been made for some time. An algorithm for estimating these measures from download time series is demonstrated and the measures are examined over time in two open source projects.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_10},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Heatbeat\%20Measuring\%20Active\%20Use.pdf},
	author = {Andrea Wiggins and Howison, James and Kevin Crowston}
}
@conference {570,
	title = {How Open Source Can Still Save the World},
	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 = {2 },
	chapter = {2},
	abstract = {Many of the worlds{\textquoteright} major problems - economic distress, natural disaster responses, broken health care systems, education crises, and more - are not fundamentally information technology issues. However, in every case mentioned and more, there exist opportunities for Open Source software to uniquely change the way we can address these problems. At times this is about addressing a need for which no sufficient commercial market exists. For others, it is in the way Open Source licenses free the recipient from obligations to the creators, creating a relationship of mutual empowerment rather than one of dependency. For yet others, it is in the way the open collaborative processes that form around Open Source software provide a neutral ground for otherwise competitive parties to find a greatest common set of mutual needs to address together rather than in parallel. Several examples of such software exist today and are gaining traction. Governments, NGOs, and businesses are beginning to recognize the potential and are organizing to meet it. How far can this be taken?
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_2},
	attachments = {https://flosshub.org/sites/flosshub.org/files/How\%20Open\%20Source\%20Can\%20Still\%20Save\%20the\%20World.pdf},
	author = {Behlendorf, Brian}
}
@article {44,
	title = {Hacker practice: Moral genres and the cultural articulation of liberalism},
	journal = {Anthropological Theory},
	volume = {8},
	number = {3},
	year = {2008},
	pages = {255},
	author = {Coleman, E.G. and Golub, A.}
}
@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 {991,
	title = {How Long Will It Take to Fix This Bug?},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {1},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Predicting the time and effort for a software problem has long been a difficult task. We present an approach that automatically predicts the fixing effort, i.e., the person-hours spent on fixing an issue. Our technique leverages existing issue tracking systems: given a new issue report, we use the Lucene framework to search for similar, earlier reports and use their average time as a prediction. Our approach thus allows for early effort estimation, helping in assigning issues and scheduling stable releases. We evaluated our approach using effort data from the JBoss project. Given a sufficient number of issues reports, our automatic predictions are close to the actual effort; for issues that are bugs, we are off by only one hour, beating naive predictions by a factor of four.},
	keywords = {bug fixing, bug reports, effort estimation, jboss, lucene, prediction, time},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.13},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300001.pdf},
	author = {Weiss, Cathrin and Premraj, Rahul and Zimmermann, Thomas and Zeller, Andreas}
}
@conference {660,
	title = {How to Gather FLOSS Metrics},
	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 = {361 - 362},
	publisher = {Springer},
	organization = {Springer},
	chapter = {44},
	abstract = {In this half-day tutorial, participants will gain hands-on exposure to key technologies for data collection about open source projects.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_44},
	attachments = {https://flosshub.org/sites/flosshub.org/files/How\%20to\%20gather\%20Floss\%20Metrics.pdf},
	author = {Conklin, Megan and Gonzalez-Barahona, Jesus and Gregorio Robles}
}
@article {Crowston:2006a,
	title = {Hierarchy and centralization in Free and Open Source Software team communications},
	journal = {Knowledge, Technology \& Policy},
	volume = {18},
	number = {4},
	year = {2006},
	pages = {65{\textendash}85},
	abstract = {Free/Libre Open Source Software (FLOSS) development teams provide an interesting and convenient setting for studying distributed work. We begin by answering perhaps the most basic question: what is the social structure of these teams? Based on a social network analysis of interactions represented in 62,110 bug reports from 122 large and active projects, we find that some OSS teams are highly centralized, but contrary to expectation, others are not. Projects are mostly quite hierarchical on four measures of hierarchy, consistent with past research but contrary to the popular image of these projects. Furthermore, we find that the level of centralization is negatively correlated with project size, suggesting that larger projects become more modular. The paper makes a further methodological contribution by identifying appropriate analysis approaches for interaction data. We conclude by sketching directions for future research.},
	keywords = {apache, bug fixing, bug tracking, FLOSS, project success, savannah, social network analysis, sourceforge, team size, teams},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHierarchyAndCentralization.pdf},
	author = {Kevin Crowston and Howison, James}
}
@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 {692,
	title = {How is it possible to profit from innovation in the absence of any appropriability?},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {203/2006},
	year = {2006},
	month = {2006///},
	pages = {333 - 334},
	publisher = {Springer},
	organization = {Springer},
	abstract = {Open Source Software (OSS) represents an {\textquotedblleft}open innovation{\textquotedblright} paradigm based on knowledge produced and shared by developers and users. New findings from a large survey of European software companies show that: (i) the OSS business model is currently involving almost one third of the industry, although with different intensity; (ii) compared with pure proprietary software producers, OSS firms have a broader product portfolio and are more diversified; moreover, (iii) OSS firms provide more complementary services to their customers; (iv) over time OSS firms increase the share of OS turnover out of the total turnover, becoming more and more OSS oriented; (v) both NOSS and OSS firms do not consider appropriability as a crucial requirement for innovation and do not consider the lack of appropriability as an obstacle to profitability.
},
	issn = {978-0-387-34225-2},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/How\%20is\%20it\%20possible\%20to\%20profit.pdf},
	author = {Andrea Bonaccorsi and Lucia Piscitello and Monica Merito and Cristina Rossi}
}
@conference {Kim:2006:LDT:1137983.1138027,
	title = {How long did it take to fix bugs?},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {173{\textendash}174},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The number of bugs (or fixes) is a common factor used to measure the quality of software and assist bug related analysis. For example, if software files have many bugs, they may be unstable. In comparison, the bug-fix time--the time to fix a bug after the bug was introduced--is neglected. We believe that the bug-fix time is an important factor for bug related analysis, such as measuring software quality. For example, if bugs in a file take a relatively long time to be fixed, the file may have some structural problems that make it difficult to make changes. In this report, we compute the bug-fix time of files in ArgoUML and PostgreSQL by identifying when bugs are introduced and when the bugs are fixed. This report includes bug-fix time statistics such as average bug-fix time, and distributions of bug-fix time. We also list the top 20 bug-fix time files of two projects.},
	keywords = {argouml, bug fixing, bugs, mining challenge, msr challenge, postgresql, quality, time},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138027},
	url = {http://doi.acm.org/10.1145/1137983.1138027},
	attachments = {https://flosshub.org/sites/flosshub.org/files/173HowLong.pdf},
	author = {Kim, Sunghun and Whitehead,Jr., E. James}
}
@article {flosswp228,
	title = {The Hacker Ethic and Meaningful Work},
	year = {2005},
	month = {August},
	abstract = {This paper begins with the following proposition: given that we spend a large proportion of our time working, a just society will provide or encourage meaningful work. Hackers have created and broadened spaces where working life can unfold freely, so a proper analysis of the Hacker Ethic ought to be of concern both to philosophers interested in meaningful work, and to academics researching hackers and the free software community. I proceed by first developing an understanding of the Hacker Ethic that highlights a central concern of my essay, that of orientations that I characterise as self-indulgent and social placing conflicting obligations upon individuals. Using Marx{\textquoteright}s conception of alienated as a basis, I go on to show how the Hacker Ethic can to an extent overcome these conflicts by developing a more rounded understanding of the ethic. Finally I raise some concerns for the underdeveloped field of the philosophy of hacking and free software that are particularly pertinent to the paper.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/chance.pdf},
	author = {Tom Chance}
}
@article {vanWendeldeJoode2005109,
	title = {Handling variety: the tension between adaptability and interoperability of open source software},
	journal = {Computer Standards \& Interfaces},
	volume = {28},
	number = {1},
	year = {2005},
	note = {unable to find concise description of the data used [ms]},
	pages = {109 - 121},
	abstract = {Open source software (OSS) offers unprecedented opportunities to create variety. This could lead to incompatibility and fragmentation. To prevent this some form of coordination is needed. This paper explores which mechanisms of coordination are responsible for limiting divergence in OSS. Two cases are examined: Java and Linux. A systematic difference seems to exist between the mechanisms identified in the two communities. With respect to Java, divergence is where possible avoided ex ante, whereas for Linux divergence is foremost reduced ex post. The conclusion discusses this difference and the implications of both types of coordination in respect to interoperability.},
	keywords = {coordination, divergence, java, linux},
	issn = {0920-5489},
	doi = {DOI: 10.1016/j.csi.2004.12.004},
	url = {http://www.sciencedirect.com/science/article/B6TYV-4F6K72H-1/2/c74c64ce51e6f46abf9f39ae945c9e15},
	author = {Ruben van Wendel de Joode and Tineke M. Egyedi}
}
@article {1393,
	title = {Hipikat: a project memory for software development},
	journal = {IEEE Transactions on Software Engineering},
	volume = {31},
	year = {2005},
	month = {06/2005},
	pages = {446 - 465},
	abstract = {Sociological and technical difficulties, such as a lack of informal encounters, can make it difficult for new members of noncollocated software development teams to learn from their more experienced colleagues. To address this situation, we have developed a tool, named Hipikat, that provides developers with efficient and effective access to the group memory for a software development project that is implicitly formed by all of the artifacts produced during the development. This project memory is built automatically with little or no change to existing work practices. After describing the Hipikat tool, we present two studies investigating Hipikat{\textquoteright}s usefulness in software modification tasks. One study evaluated the usefulness of Hipikat{\textquoteright}s recommendations on a sample of 20 modification tasks performed on the Eclipse Java IDE during the development of release 2.1 of the Eclipse software. We describe the study, present quantitative measures of Hipikat{\textquoteright}s performance, and describe in detail three cases that illustrate a range of issues that we have identified in the results. In the other study, we evaluated whether software developers who are new to a project can benefit from the artifacts that Hipikat recommends from the project memory. We describe the study, present qualitative observations, and suggest implications of using project memory as a learning aid for project newcomers.},
	issn = {0098-5589},
	doi = {10.1109/TSE.2005.71},
	author = {Cubranic, D. and Murphy, G. C. and Singer, J. and Booth, K.S.}
}
@article {flosswp236,
	title = {How open is the future (Book - Under creative Commons},
	year = {2005},
	month = {September},
	abstract = {There are two reasons why the free and open-source software issue has become such an inspirational and powerful force today: the rise of the Internet and the growing tendency to protect all intellectual property. Internet technology made it possible to handle massive decentralized projects and irreversibly changed our personal communication and information research. Intellectual property, on the other hand, is a legal instrument which - due to recent excesses - became the symbol of exactly the opposite of what it had been developed for: the protection of the creative process. As a result, free-thinking programmers, scientists, artists, designers, engineers and scholars are daily trying to come up with new ways of creating and sharing knowledge.},
	author = {Marleen Wynants}
}
@conference {903,
	title = {How Oversight Improves Member-Maintained Communities},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2005},
	publisher = {ACM},
	organization = {ACM},
	address = {Portland OR},
	author = {Cosley, D. and D. Frankowski and S. Kiesler and Terveen, L. and Riedl, J.}
}
@conference {904,
	title = {How Peer Photos Influence Member Participation in Online Communities},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2005},
	publisher = {ACM},
	organization = {ACM},
	address = {Portland, OR},
	author = {Kapoor, N. and Konstan, J.A. and Terveen, L. G.}
}
@proceedings {117,
	title = {A human capital perspective of organizational intention to adopt open source software},
	year = {2005},
	keywords = {Survey},
	author = {Yan Li and Chuan-Hoo Tan and Hock-Hai Teo and Alex Siow}
}
@article {flosswp211,
	title = {Hybrid Innovation - How Does the Collaboration Between the FLOSS Community and Corporations Happen?},
	year = {2005},
	month = {April},
	abstract = {Unlike innovation based on a strong professional culture involving close collaboration between professionals in academia and/or corporations, the current Free/Libre Open Source Software (FLOSS) development entails a global knowledge network, which consists of 1) a heterogeneous community of individuals and organisations who do not necessarily have professional backgrounds in computer science but competent skills to understand programming and working in a public domain; 2) corporations. This paper highlights the importance of the hybrid form of developing and implementing software, and also identifies several key factors shaping the collaboration between OSS firms and the community.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin4_hybrid.pdf},
	author = {Yu-wei Lin}
}
@conference {769,
	title = {An Hypergraph Based Approach for Unlocking Power Relations in Rhizomatic Open Source Software Communities},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {272},
	abstract = {This study, first, points the rhizomatic nature of open source software (OSS) communities. Then, it proposes an hypergraph based research methodology both to capture and to analyze dynamics of OSS communities. An exemplary hypergraph theoretical analysis of power antecedence within rhizomatic network of an OSS community is illustrated.},
	url = {http://pascal.case.unibz.it/handle/2038/626},
	author = {{\"O}zel, B{\"u}lent}
}
@article {flosswp191,
	title = {Hacking Alone? The Effects of Online and Offline Participation on Open Source Community Leadership},
	year = {2004},
	month = {September},
	abstract = {Research on computer mediated communication has examined how a lack of social presence affects participation, communication and leadership in online groups, but until recently, has not examined offline relations or emergent social structures. The few studies examining these issues have not been integrated with research on open source communities. Online communities producing open source software face even greater problems of governance than affinity or interest based online communities, as leadership responsibilities extend beyond mailing list management to managing release dates, public relations, and collaborations with firms. With data from one open source community{\textquoteright}s online and offline networks over three consecutive years, we assess factors affecting voting participation and leadership. We find that the more developers one has met face to face, the more likely one was to vote in a leadership election. Controlling for contributions of code, developers are more likely to hold a top leadership position when they participate more in online discussions. However, online participation in technical discussions did not affect leadership as much as occupying a structurally advantaged position in the community{\textquoteright}s social network. We conclude with theoretical implications that consider the dynamics of online and offline networks for governing distributed online communities.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/omahonyferraro2.pdf},
	author = {Siobhan O{\textquoteright}Mahony}
}
@mastersthesis {flosswp188,
	title = {Hacking Practices and Software Development: A Social Worlds Analysis of ICT Innovation and the Role of Free/Libre Open Source Software},
	year = {2004},
	note = {Through use of social worlds theory and qualitative research methods, this thesis explores hackers{\textquoteright} practices and their relationships with the computing world and the wider society from a socio-technical perspective. The hacker social world comprises actors from diverse social-technical backgrounds who share a constellation of im/material practices, namely open source practices (OSPs). Through engaging with these collective practices, actors and actants communicate, negotiate, and shape each other{\textquoteright}s identities, practices and understandings of the innovation structure and system in various aspects. In examining the diverse articulations and performances in which hacker culture and hacker identity are both reflected and constructed, the thesis tries to contextualise and deconstruct the ICT architecture we take for granted, as well as the innovations made possible by this architecture.The major findings of my research are: (1) As a community of open source practices, the FLOSS social world allows diverse actors to engage in the innovation process and therefore fosters a greater innovation resource than other relatively conventional software engineering models. (2) The strategic collaboration between the public (i.e. the free software community) and the private (i.e. information technology corporations) sectors symbolises a pattern of hybrid innovation that entails complex communications and networks, though stabilizing these can be problematic. (3) Tacit knowledge anchored in everyday experiences is particularly valued in a community-based innovation system where social networking and information sharing are extensive. (4) The development of FLOSS democratises software innovation process and allows lay people to develop their understanding and knowledge of a shared problem/issue, especially through the web, to challenge established views on the issue.},
	month = {September},
	abstract = {Through use of social worlds theory and qualitative research methods, this thesis explores hackers{\textquoteright} practices and their relationships with the computing world and the wider society from a socio-technical perspective. Through engaging with a constellation of open source practices (OSPs), actors and actants communicate, negotiate, and shape each other?s identities, practices and understandings of the innovation structure and system in various aspects. In examining the diverse articulations and performances in which hacker culture and hacker identity are both reflected and constructed, the thesis tries to contextualise and deconstruct the ICT architecture we take for granted, as well as the innovations made possible by this architecture.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lin2.pdf},
	author = {Yu-wei Lin}
}
@proceedings {1186,
	title = {How can Academic Software Research and Open Source Software Development help each other?},
	year = {2004},
	pages = {5-8},
	abstract = {In this paper we discuss a few issues faced in coordinating, managing and implementing academic software research projects and suggest how some of these issues can be addressed by adopting tools and processes from Open Source Software Development. At the same time we also discuss how a few issues in Open Source Software Development (OSSD) projects can be addressed by adopting processes from Academic Software Research.},
	keywords = {academic, education},
	attachments = {https://flosshub.org/sites/flosshub.org/files/ambati6-9.pdf},
	author = {Ambati, V. and Kishore, S.P.}
}
@article {129,
	title = {How effective developers investigate source code: An exploratory study},
	journal = {Ieee Transactions on Software Engineering},
	volume = {30},
	number = {12},
	year = {2004},
	note = {Times Cited: 6},
	pages = {889-903},
	abstract = {Prior to performing a software change task, developers must discover and understand the subset of the system relevant to the task. Since the behavior exhibited by individual developers when investigating a software system is influenced by intuition, experience, and skill, there is often significant variability in developer effectiveness. To understand the factors that contribute to effective program investigation behavior, we conducted a study of five developers performing a change task on a medium-size open source system. We isolated the factors related to effective program investigation behavior by performing a detailed qualitative analysis of the program investigation behavior of successful and unsuccessful developers. We report on these factors as a set of detailed observations, such as evidence of the phenomenon of inattention blindness by developers skimming source code. In general, our results support the intuitive notion that a methodical and structured approach to program investigation is the most effective. Index Terms-Software evolution, empirical software engineering, program investigation, program understanding.},
	author = {Robillard, M. P. and Coelho, W. and Murphy, G. C.}
}
@article {flosswp187,
	title = {How Free Become Open and Everything Else Under the Sun},
	year = {2004},
	month = {October},
	abstract = {Free and Open Source Software (FOSS) has been adopted as a political tool by leftist activists. At the same time, it has been embraced by large corporations to extend profits and has been criticized as an integral force in late capitalism. It has been adopted by members of the growing Commons movement as a model for limiting the power of capitalism. This essay attempts to confront the variability of these relationships through a cursory analysis of each field and through an look at FOSS philosophy and practice. It argues that Free Software exists as a politically agnostic field of practice{\textendash}built on and through a broadly defined philosophy. It analyzes the way that this philosophy is well suited for the spread of FOSS technologies and its translation into the terms of radically different, even oppositional, social and political movements.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/colemanhill.pdf},
	author = {Biella Coleman}
}
@article {flosswp173,
	title = {How is Open Source affecting software development?},
	year = {2004},
	month = {January},
	abstract = {Paper describes impact of using open source software in general development environments. (From the intro): " The dynamism of open source software development efforts, numerous high-profile success stories, and the novel economic, business, and legal aspects of open source software adoption are justifiably creating a stir in the development community. We software practitioners increasingly face the possibility of using or basing our work on open source components, libraries, frameworks, systems, platforms, and development environments."},
	attachments = {https://flosshub.org/sites/flosshub.org/files/spinellisszyperski.pdf},
	author = {Diomidis Spinellis and Clemens Szyperski}
}
@article {flosswp242,
	title = {How to Have a Successful Free Software Project},
	year = {2004},
	month = {December},
	abstract = {Some free software projects have been extremely successful. This rise to prominence can be attributed to the high quality and suitability of the software. This quality and suitability is achieved through an elaborate peer-review process performed by a large community of users, who act as co-developers to identify and correct software defects and add features. Although this process is crucial to the success of free software projects, there is more to the free software development than the creation of a ?bazaar?. In this paper we draw on existing free software projects to define a lifecycle model for free software. This paper then explores each phase of the lifecycle model and agrees that, while the bazaar phase attracts the most attention, it is the initial modular design that accommodates diverse interventions. Moreover, it is the period of transition from the initial group to the larger community based development that is crucial in determining whether a free software project will succeed or fail.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/senyardmichlmay.pdf},
	author = {Anthony Senyard}
}
@article {flosswp105,
	title = {How Firm Initiation and Control of Projects Affects Open-Source Development},
	year = {2003},
	month = {May},
	abstract = {After witnessing the success of open-source projects such as Linux and Apache, firms have sought to appropriate the open-source development model and integrate it into their own projects. Firms face a dilemma, however, since their initiation and control of open-source projects affects the traditional open-source development model in significant ways. Once a firm takes the role of starting and guiding an open-source project, the open-source development model that attracted the firm is forever altered. This paper examines the effects commercial firms have on the open-source development model when they initiate and control open-source projects.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/long.pdf},
	author = {Anthony Long}
}
@article {flosswp75,
	title = {How Open is Open Enough? Melding Proprietary and Open Source Platform Strategies},
	journal = {RP Special Issue},
	year = {2003},
	month = {February},
	abstract = {Computer platforms provide an integrated architecture of hardware and software standards as a basis for developing complementary assets. The most successful platforms were owned by proprietary sponsors that controlled platform evolution and appropriated associated rewards. Responding to the Internet and open source systems, three traditional vendors of proprietary platforms experimented with hybrid strategies which attempted to combine the advantages of open source software while retaining control and differentiation. Such hybrid standards strategies reflect the competing imperatives for adoption and appropriability, and suggest the conditions under which such strategies may be preferable to either the purely open or purely proprietary alternatives.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rp-west.pdf},
	author = {Joel West}
}
@article {909,
	title = {How open is open enough? Melding proprietary and open source platform strategies},
	journal = {Research Policy},
	volume = {32},
	year = {2003},
	month = {07/2003},
	pages = {1259 - 1285},
	author = {Joel West}
}
@article {116,
	title = {How open source software works: "free" user-to-user assistance},
	journal = {Research Policy},
	volume = {32},
	number = {6},
	year = {2003},
	note = {"The empirical data we collected for study was related to postings to the Apache Usenet help forum, CIWS-U (comp.infosystems.www.servers.unix). "
"For data regarding long-term participation in CIWS-U{\textemdash}who participated, long-term trends, etc.{\textemdash}we examined Usenet posting patterns from 1996 to 1999."
"The Usenet log data was obtained from a World Wide Web service called Deja.com (since acquired by Google)"
survey},
	pages = {923-943},
	abstract = {Research into free and open source software development projects has so far largely focused on how the major tasks of software development are organized and motivated. But a complete project requires the execution of "mundane but necessary" tasks as well. In this paper, we explore how the mundane but necessary task of field support is organized in the case of Apache web server software, and why some project participants are motivated to provide this service gratis to others. We find that the Apache field support system functions effectively. We also find that, when we partition the help system into its component tasks, 98\% of the effort expended by information providers in fact returns direct learning benefits to those providers. This finding considerably reduces the puzzle of why information providers are willing to perform this task "for free." Implications are discussed.},
	keywords = {apache, help, logs, MOTIVATION, participants, Survey, usenet},
	doi = {http://dx.doi.org/10.1016/S0048-7333(02)00095-1},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.110.8172\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/lakhani2003.pdf},
	author = {Karim R Lakhani and von Hippel, Eric}
}
@article {1095,
	title = {High Quality and Open Source Software Practices},
	journal = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	note = {"We examined the publicly visible portions of these projects from November 2001 through March 2002, ...The SLOC counts for the predominate languages are shown},
	month = {2002},
	abstract = {Surveys suggest that, according to various metrics, the quality and dependability of today{\textquoteright}s open source software is roughly on par with commercial and government developed software. What are the prospects for advancing to much higher levels of quality in open source software? More specifically, what attributes must be possessed by quality-related interventions for them to be feasibly adoptable in open source practice? In order to identify some of these attributes, we conducted a preliminary survey of the quality practices of a number of successful open source projects. We focus, in particular, on attributes related to adoptability by the open source practitioner community.},
	keywords = {apache, bug report, bug tracker, bug tracking system, feature requests, gcc, gnome, kde, lines of code, linux, loc, mozilla, netbeans, perl, position paper, python, sloc, source code, Survey, tomcat, xfree86},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HalloranScherlis.pdf},
	author = {T. Halloran and W. Scherlis}
}
@article {flosswp44,
	title = {Horizontal innovation networks- by and for users},
	year = {2002},
	month = {June},
	abstract = {Innovation development, production, distribution and consumption networks can be built up horizontally with actors consisting only of innovation users. User innovation networks can function entirely independently of manufacturers when (1) at least some users have sufficient incentive to innovate, (2) at least some users have an incentive to voluntarily reveal their innovations, and (3) diffusion of innovations by users is low cost and can compete with commercial production and distribution. In this paper we explore the empirical evidence related to each of these matters and conclude that conditions favorable to user innovation networks are often present in the economy.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/vonhippel3.pdf},
	author = {von Hippel, Eric}
}
@article {flosswp16,
	title = {How Communities Support Innovative Activities: As Exploration of Assistance and Sharing Among Innovative Users of Sporting Equipment},
	year = {2001},
	month = {August},
	abstract = {This exploratory study finds that end-user innovators who are members of voluntary sports communities often receive assistance in developing their sports-equipment innovations from fellow community members. Innovation-related information and assistance, as well as the innovations themselves, are freely within these communities. The processes by which these communities operate may be of general interest both within and beyond the consumer product arena; for example, communities of open source software developers appear to operate in similar ways.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/frankeshah.pdf},
	author = {Nik Franke}
}
