@inbook {Bibi2016,
	title = {A Bayesian Belief Network for Modeling Open Source Software Maintenance Productivity},
	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 = {32{\textendash}44},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	chapter = {A Bayesian Belief Network for Modeling Open Source Software Maintenance Productivity},
	address = {Cham},
	abstract = {Maintenance is one of the most effort consuming activities in the software development lifecycle. Efficient maintenance within short release cycles depends highly on the underlying source code structure, in the sense that complex modules are more difficult to maintain. In this paper we attempt to unveil and discuss relationships between maintenance productivity, the structural quality of the source code and process metrics like the type of a release and the number of downloads. To achieve this goal, we developed a Bayesian Belief Network (BBN) involving several maintainability predictors and three managerial indices for maintenance (i.e., duration, production, and productivity) on 20 open source software projects. The results suggest that maintenance duration depends on inheritance, coupling, and process metrics. On the other hand maintenance production and productivity depend mostly on code quality metrics.
},
	isbn = {978-3-319-39225-7},
	doi = {10.1007/978-3-319-39225-7_3},
	url = {http://dx.doi.org/10.1007/978-3-319-39225-7_3},
	author = {Bibi, Stamatia and Apostolos Ampatzoglou and Ioannis Stamelos},
	editor = {Kevin Crowston and Hammouda, Imed and Lundell, Bj{\"o}rn and Gregorio Robles and Gamalielsson, Jonas and Juho Lindman}
}
@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}
}
@conference {1800,
	title = {Big data analytics on large-scale socio-technical software engineering archives},
	booktitle = {2015 3rd International Conference on Information and Communication Technology (ICoICT )2015 3rd International Conference on Information and Communication Technology (ICoICT)},
	year = {2015},
	pages = {65 - 69},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Nusa Dua, Bali, Indonesia},
	abstract = {Given the fast growing nature of software engineering data in online software repositories and open source communities, it would be helpful to analyse these assets to discover valuable information about the software engineering development process and other related data. Big Data Analytics (BDA) techniques and frameworks can be applied on these data resources to achieve a high-performance and relevant data collection and analysis. Software engineering is a socio-technical process which needs development team collaboration and technical knowledge to develop a high-quality application. GitHub, as an online social coding foundation, contains valuable information about the software engineers{\textquoteright} communications and project life cycles. In this paper, unsupervised data mining techniques are applied on the data collected by general Big Data approaches to analyse GitHub projects, source codes and interactions. Source codes and projects are clustered using features and metrics derived from historical data in repositories, object oriented programming metrics and the influences of developers on source codes.
},
	doi = {10.1109/ICoICT.2015.7231398},
	author = {Bayati, Shahabedin and Parsons, David and Susnjak, Teo and Heidary, Marzieh}
}
@inbook {1610,
	title = {Barriers Faced by Newcomers to Open Source Projects: A Systematic Review},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {153-163},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {
To remain sustainable, some open source projects need a constant influx of new volunteers, or newcomers. However, the newcomers face different kinds of problems when onboarding to a project. In this paper we present the results of a systematic literature review aiming at identifying the barriers that a newcomer can face when contributing to an Open Source Software project. We identified and analyzed 21 studies that evidence this kind of problem. As a result we provide a hierarchical model that relies on five categories of barriers: finding a way to start, social interactions, code issues, documentation problems and newcomers{\textquoteright} knowledge. The most evidenced barriers are newcomers{\textquoteright} previous technical skills, receiving response from community, centrality of social contacts, and finding the appropriate way to start contributing. This classification provides a baseline for further researches related to newcomers onboarding.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_21},
	url = {http://flosscoach.com/publications/IST2015.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/IST2015.pdf},
	author = {Steinmacher, Igor and Silva, MarcoAur{\'e}lioGraciotto and Gerosa, MarcoAur{\'e}lio},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@proceedings {1573,
	title = {"A bit of code": How the Stack Overflow Community Creates Quality Postings},
	year = {2014},
	month = {01/2014},
	pages = {1425-1434},
	publisher = {IEEE Computer Society},
	abstract = {The Stack Overflow web site is an online community where programmers can ask and answer one another{\textquoteright}s questions, earning points and badges. The site offers guidance in the form of a Frequently Asked Questions (FAQ), beginning with "What kind of questions can I ask here?" The answer explains that "the best Stack Overflow questions have a bit of source code in them". This paper explores the role of source code and non-source code text on Stack Overflow in both questions and answers. The primary contribution of this paper is to provide a more detailed understanding of whether the presence of source code (and how much) actually will produce the "best" Stack Overflow questions or answers. A second contribution of this paper is to determine how the non-code portions of the text might also contribute the "best" Stack Overflow postings.  },
	keywords = {COLLABORATION, collaborative development, data mining, developer network, knowledge collaboration, open content, text mining},
	doi = {http://dx.doi.org/10.1109/HICSS.2014.185},
	attachments = {https://flosshub.org/sites/flosshub.org/files/hicssSMFinalWatermark.pdf},
	author = {Squire, Megan and Funkhouser, Christian}
}
@inbook {1624,
	title = {Book Locator: Books Manager},
	booktitle = {Open Source Software: Mobile Open Source Technologies},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {427},
	year = {2014},
	pages = {230-231},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	abstract = {

After performing a study of digital books organizing tools, it{\textquoteright}s observed that these don{\textquoteright}t count on a multi platform integration, and those who do, don{\textquoteright}t count on the elements pursued in the investigation. It is decided then to proceed to the implementation of a book organizer software, taking an initial requirements list from the studied tools, following the guidelines of the collaborative and open source development. It has been developed to its version 4.1, which after going through different development processes, detecting mistakes and adding new functionalities that join to the requirements list, it{\textquoteright}s fully functional.
},
	isbn = {978-3-642-55127-7},
	doi = {10.1007/978-3-642-55128-4_35},
	url = {http://dx.doi.org/10.1007/978-3-642-55128-4_35},
	author = {Garc{\'\i}a Rivas, Dairelys},
	editor = {Corral, Luis and Sillitti, Alberto and Succi, Giancarlo and Vlasenko, Jelena and Wasserman, AnthonyI.}
}
@conference {Mitropoulos:2014:BCM:2597073.2597123,
	title = {The Bug Catalog of the Maven Ecosystem},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {372{\textendash}375},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Examining software ecosystems can provide the research community with data regarding artifacts, processes, and communities. We present a dataset obtained from the Maven central repository ecosystem (approximately 265GB of data) by statically analyzing the repository to detect potential software bugs. For our analysis we used FindBugs, a tool that examines Java bytecode to detect numerous types of bugs. The dataset contains the metrics results that FindBugs reports for every project version (a JAR) included in the ecosystem. For every version we also stored specific metadata such as the JAR{\textquoteright}s size, its dependencies and others. Our dataset can be used to produce interesting research results, as we show in specific examples.
},
	keywords = {findbugs, Maven Repository, msr data showcase, Software Bugs},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597123},
	url = {http://doi.acm.org/10.1145/2597073.2597123},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mitro.pdf},
	author = {Mitropoulos, Dimitris and Vassilios Karakoidas and Louridas, Panos and Gousios, Georgios and Diomidis Spinellis}
}
@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 {1507,
	title = {Bug Resolution Catalysts: Identifying Essential Non-committers from Bug Repositories},
	year = {2013},
	month = {05/2013},
	abstract = {Bugs are inevitable in software projects. Resolving bugs is the primary activity in software maintenance. Developers, who fix bugs through code changes, are naturally important participants in bug resolution. However, there are other participants in these projects who do not perform any code commits. They can be reporters reporting bugs; people having a deep technical know-how of the software and providing valuable insights on how to solve the bug; bug-tossers who re-assign the bugs to the right set of developers. Even though all of them act on the bugs by tossing and commenting, not all of them may be crucial for bug resolution. In this paper, we formally define essential non-committers and try to identify these bug resolution catalysts. We empirically study 98304 bug reports across 11 open source and 5 commercial software projects for validating the existence of such catalysts. We propose a network analysis based approach to construct a Minimal Essential Graph that identifies such people in a project. Finally, we suggest ways of leveraging this information for bug triaging and bug report summarization.},
	author = {Mani, Senthil and Seema Nagar and Debdoot Mukherjee and Ramasuri Narayanam and Sinha, Vibha Singhal and Amit A. Nanavati}
}
@article {Ampatzoglou2013131,
	title = {Building and mining a repository of design pattern instances: Practical and research benefits},
	journal = {Entertainment Computing},
	volume = {4},
	number = {2},
	year = {2013},
	note = {flossmole cited},
	pages = {131 - 142},
	abstract = {Design patterns are well-known design solutions that are reported to produce substantial benefits with respect to software quality. However, to our knowledge there are no scientific efforts on gathering information on software projects that use design patterns. This paper introduces a web repository of design patterns instances that have been used in open source projects. The usefulness of such a repository lies in the provision of a base of knowledge, where developers can identify reusable components and researchers can find a mined data set. Currently, 141 open source projects have been considered and more than 4500 pattern instances have been found and recorded in the database of the repository. The evaluation of the repository has been performed from an academic and a practical point of view. The results suggest that the repository can be useful for both experienced and inexperienced users. However, the benefits of using the repository are more significant for inexperienced users. },
	keywords = {flossmole cited, repository},
	issn = {1875-9521},
	doi = {10.1016/j.entcom.2012.10.002},
	url = {http://www.sciencedirect.com/science/article/pii/S1875952112000195},
	author = {Apostolos Ampatzoglou and Olia Michou and Ioannis Stamelos}
}
@proceedings {1470,
	title = {Binoculars: Comprehending Open Source Projects through Graphs},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {350-355},
	publisher = {IFIP AICT,  Springer},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Comprehending Open Source Software (OSS) projects requires dealing with huge historical information stored in heterogeneous repositories, such as source code versioning systems, bug tracking system, mailing lists, and revision history logs. In this paper, we present Binoculars, a prototype tool which aims to provide a platform for graph based visualization and exploration of OSS projects. We describe the issues need to be addressed for the design and implementation of a graph based tool and distill lessons learned for future guideline.},
	author = {Syeed, M.M. Mahbubul}
}
@proceedings {1278,
	title = {Building Knowledge in Open Source Software Research in Six Years of Conferences},
	year = {2011},
	note = {RQ1. Is there any social network underlying the research production at the OSS conference series?
RQ2. What are the major streams of research proposed at the OSS conference series?},
	month = {10/2011},
	pages = {123-141},
	publisher = {Springer},
	abstract = {Since its origins, the diffusion of the OSS phenomenon and the information about it has been entrusted to the Internet and its virtual communities of developers. This public mass of data has attracted the interest of researchers and practitioners aiming at formalizing it into a body of knowledge. To this aim, in 2005, a new series of conferences on OSS started to collect and convey OSS knowledge to the research and industrial community. Our work mines articles of the OSS conference series to understand the process of knowledge grounding and the community surrounding it. As such, we propose a semi-automated approach for a systematic mapping study on these articles. We automatically build a map of cross-citations among all the papers of the conferences and then we manually inspect the resulting clusters to identify knowledge building blocks and their mutual relationships. We found that industry-related, quality assurance, and empirical studies often originate or maintain new streams of research.},
	keywords = {Cross-citations, flossmole cited, graph, literature review, network, research, Systematic Mapping Study},
	author = {Mulazzini, Fabio and Rossi, Bruno and Russo, Barbara and Steff, Maximilian}
}
@conference {948,
	title = {Beyond replication: An example of the potential benefits of replicability in the mining of software repositories community},
	booktitle = {1st Workshop on Replication in Empirical Software Engineering Research},
	year = {2010},
	month = {05/2010},
	keywords = {literature review, msr, replication},
	author = {Gregorio Robles and Daniel M. German}
}
@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 {574,
	title = {Beyond the Business Model: Incentives for Organizations to Publish Software Source Code},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {47 - 56},
	publisher = {Springer},
	organization = {Springer},
	chapter = {6},
	abstract = {The software stack opened under Open Source Software (OSS) licenses is growing rapidly. Commercial actors have released considerable amounts of previously proprietary source code. These actions beg the question why companies choose a strategy based on giving away software assets? Research on outbound OSS approach has tried to answer this question with the concept of the {\textquotedblleft}OSS business model{\textquotedblright}. When studying the reasons for code release, we have observed that the business model concept is too generic to capture the many incentives organizations have. Conversely, in this paper we investigate empirically what the companies{\textquoteright} incentives are by means of an exploratory case study of three organizations in different stages of their code release. Our results indicate that the companies aim to promote standardization, obtain development resources, gain cost savings, improve the quality of software, increase the trustworthiness of software, or steer OSS communities. We conclude that future research on outbound OSS could benefit from focusing on the heterogeneous incentives for code release rather than on revenue models.
},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_6},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Beyond\%20the\%20Business\%20Model.pdf},
	author = {Juho Lindman and Juutilainen, Juha-Pekka and Rossi, Matti}
}
@article {1237,
	title = {Bridging the Gap between Agile and Free Software Approaches},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	month = {31/2009},
	pages = {58 - 71},
	abstract = {Agile sprints are short events where a small team collocates in order to work on particular aspects of the overall project for a short period of time. Sprinting is a process that has been observed also in Free Software projects: these two paradigms, sharing common principles and values have shown several commonalities of practice. This article evaluates the impact of sprinting on a Free Software project through the analysis of code repository logs: sprints from two Free Software projects (Plone and KDE PIM) are assessed and two hypotheses are formulated: do sprints increase productivity? Are Free Software projects more productive after sprints compared with before? The primary contribution of this article is to show how sprinting creates a large increase in productivity both during the event, and immediately after the event itself: this argues for more in-depth studies focussing on the nature of sprinting.},
	keywords = {agile, kde, lines of code, loc, plone, productivity, scm, scrum, sprints, subversion},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009010104},
	author = {Paul J. Adams and Capiluppi, Andrea}
}
@book {48,
	title = {Biobazaar: The Open Source Revolution and Biotechnology},
	year = {2008},
	publisher = {Harvard University Press},
	organization = {Harvard University Press},
	author = {Janet Hope}
}
@conference {971,
	title = {Branching and merging in the repository},
	booktitle = {the 2008 international workshopProceedings of the 2008 international workshop on Mining software repositories  - MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {19-22},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {Two of the most complex operations version control software allows a user to perform are branching and merging. Branching provides the user the ability to create a copy of the source code to allow changes to be stored in version control but outside of the trunk. Merging provides the user the ability to copy changes from a branch to the trunk. Performing a merge can be a tedious operation and one that may be error prone. In this paper, we compare file revisions found on branches with those found on the trunk to determine when a change that is applied to a branch is moved to the trunk. This will allow us to study how developers use merges and to determine if merges are in fact more error prone than other commits.},
	keywords = {argouml, changes, cvs2svn, diffj, revision, scm, source code, version control},
	isbn = {9781605580241},
	doi = {10.1145/1370750.1370754},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p19-williams.pdf},
	author = {Spacco, Jamie and Williams, Chadd C.}
}
@article {Crowston:2008,
	title = {Bug Fixing Practices within Free/Libre Open Source Software Development Teams},
	journal = {Journal of Database Management},
	volume = {19},
	number = {2},
	year = {2008},
	note = {"Projects to be studied were selected from those hosted on SourceForge, (http://sourceforge.net/)"
"we chose projects for which data we need for our analysis are publicly available, meaning a large number of bug reports"
"we chose teams with more than 8 developers"
"Only 140 projects of SourceForge met the first two requirements in 2002 when we drew our sample"
kicq, gaim, phpmyadmin, dynapi
"First, we obtained data indica- tive of the effectiveness of each project, such as its level of activity, number of downloads and development status"
"we elected to use objective data about the bug- fixing process. Hence, the main source of data about the bug-fixing process was obtained from the archives of the bug tracking system, which is the tool used to support the bug-fixing process"},
	pages = {1{\textendash}30},
	abstract = {Free/libre open source software (FLOSS, e.g., Linux or Apache) is primarily developed by distributed teams. Developers contribute from around the world and coordinate their activity almost exclusively by means of email and bulletin boards, yet some how profit from the advantages and evade the challenges of distributed software development. In this article we investigate the structure and the coordination practices adopted by development teams during the bug-fixing process, which is considered one of main areas of FLOSS project success. In particular, based on a codification of the messages recorded in the bug tracking system of four projects, we identify the accomplished tasks, the adopted coordination mechanisms, and the role undertaken by both the FLOSS development team and the FLOSS community. We conclude with suggestions for further research.},
	keywords = {activity, bug tracker, bug tracking system, coordination, downloads, dynapi, effectiveness, FLOSS, gaim, kicq, phpmyadmin, project success, size, status},
	issn = {1063-8016},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonScozziJDBM2008.pdf},
	author = {Kevin Crowston and Barbara Scozzi}
}
@article {147,
	title = {The business of open source},
	journal = {Communications of the ACM},
	volume = {51},
	number = {4},
	year = {2008},
	note = {Times Cited: 0},
	pages = {41-46},
	author = {Watson, R. T. and Boudreau, M. C. and York, P. T. and Greiner, M. E. and Wynn, D.}
}
@conference {649,
	title = {Benefits and Drawbacks of Open Source Software: An Exploratory Study of Secondary Software Firms},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {307 - 312},
	publisher = {Springer},
	organization = {Springer},
	chapter = {33},
	abstract = {Much of the assessment of OSS benefits and drawbacks has been based on anecdotal evidence appearing in practitioner publications, white papers, web articles etc. To a greater extent this research has tended to concentrate more on the technical benefits and drawbacks of OSS rather than their business counterparts. Furthermore, public administrations and companies operating within the primary software sector have traditionally been the focus for research on OSS benefits and drawbacks. Taking the viewpoint of IS/IT managers in 13 companies operating in the secondary software sector in Europe, this paper examines their experiences of the benefits/drawbacks of OSS.
},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_33},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Benefits\%20and\%20Drawbacks.pdf},
	author = {Morgan, Lorraine and Finnegan, Patrick}
}
@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 {887,
	title = {Because I Carry My Cell Phone Anyway: Functional Location-Based Reminder Applications},
	booktitle = {ACM SIGCHI Conference on Human Factors in Computing Systems},
	year = {2006},
	month = {22/04/2006},
	pages = {889-898},
	publisher = {ACM},
	organization = {ACM},
	address = {Montreal, Quebec, Canada},
	isbn = {1-59593-372-7},
	author = {Ludford, P. and D. Frankowski and Reily, K. and Wilms, K. and Terveen, L.}
}
@conference {680,
	title = {Beyond Low-Hanging Fruit: Seeking the Next Generation in FLOSS Data Mining},
	booktitle = {OSS2006: Open Source Systems (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing},
	year = {2006},
	pages = {47 - 56},
	publisher = {Springer},
	organization = {Springer},
	abstract = {This paper will discuss the motivations and methods for collecting quantitative data about free, libre and open source (FLOSS) software projects. The paper also describes the current state of the art in collecting this data, and some of the problems with this process. Finally, the paper outlines the challenges data miners should look forward to when trying to improve the usefulness of their quantitative data streams.
},
	doi = {http://dx.doi.org/10.1007/0-387-34226-5_5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Beyond\%20Low-Hanging\%20Fruit.pdf},
	author = {Conklin, Megan}
}
@booklet {507,
	title = {Bringing Open Source Software to the Desktop : An In-Depth Study of the Implementation and use of Star Office},
	year = {2006},
	month = {Sept},
	abstract = {Open Source software is coming to the attention of individuals, organisations, and governments worldwide, and is increasingly being adopted by firms for specific business purposes. However, the uptake of end-user desktop OSS applications to date has been modest, and Microsoft products remain the de-facto standard on the corporate desktop. This brings into sharp focus one of the most challenging questions faced by the Open Source community today ... namely, if organisations value low acquisition costs, low total cost of ownership of software, potentially plentiful support, free access to source code, and the wish to avoid proprietary software vendor lock-in, why have more organisations not adopted OSS?  This paper contributes to the existing research by reporting on an in-depth, interpretive, processual study of an attempt by a large Irish Trade Union to replace Microsoft Office with an Open Source alternative, StarOffice.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Bringing_OSS_to_the_Desktop.pdf},
	author = {PJ Wall and Seamas Kelly}
}
@article {51,
	title = {Brazil adopts open-source software},
	volume = {2008},
	number = {5 December},
	year = {2005},
	month = {2 June, 2005},
	publisher = {BBC News},
	address = {Sao Paulo},
	url = {http://news.bbc.co.uk/2/hi/business/4602325.stm},
	author = {Kingstone, Steve}
}
@conference {1052,
	title = {Bug driven bug finders},
	booktitle = {Proceedings of the 2004 international workshop on Mining software repositories  - MSR {\textquoteright}04},
	volume = {2004},
	year = {2004},
	pages = {70 - 74},
	publisher = {IEE},
	organization = {IEE},
	address = {Edinburgh, Scotland, UK},
	abstract = {We describe a method of creating tools to find bugs in software that is driven by the analysis of previously fixed bugs. We present a study of bug databases and software repositories that characterize commonly occurring types of bugs.	Based on the types of bugs that were commonly reported and fixed in the code, we determine what types of bug finding tools should be developed. We have implemented one static checker, a return value usage checker. Novel features of this checker include the use of information from the software repository to try to improve its false positive rate by identifying patterns that have resulted in previous bug fixes.},
	keywords = {apache, bug tracking, bugs},
	doi = {10.1049/ic:20040479},
	attachments = {https://flosshub.org/sites/flosshub.org/files/70BugDrivenBug.pdf},
	author = {Williams, C.C. and Hollingsworth, J.K.}
}
@proceedings {1172,
	title = {Beyond Code: Content Management and the Open Source Development Portal},
	year = {2003},
	pages = {69-73},
	attachments = {https://flosshub.org/sites/flosshub.org/files/69-73.pdf},
	author = {T. Halloran and W. Scherlis and Erenkrantz, J.}
}
@conference {DBLP:conf/ecis/TsiavosH03,
	title = {Beyond good and evil: why open source development for peer-to-peer networks does not necessarily equal to an open society is as imbalanced as copyright law and definitely is not going to make you a better person},
	booktitle = {European Conference on Information Systems (ECIS 2003)},
	year = {2003},
	note = {"In a first stage we collected data related to the development of the Gnutella protocol. The sources included: web sites that were used for hosting forums and file repositories related to the development of the protocol that could be either archived or still operational; messages posted on discussion groups, forums and newsgroups; the design documents of the Gnutella protocol.
In a second stage we gathered material related to the Limewire application. The sources included: operational and archived web sites having been used for the development of the application; applications such as Concurrent Version Systems (CVS) or Bug reporting tools (such as Issuezila), design and implementation documentation and relevant press reports.
The data gathered covered a time span from early 2000 to late November 2002."
"Other sources informed our research and also acted, at times of uncertainty, as forms of triangulation and verification (Lee 1991). These sources include websites such as Slashdot.org and WiredNews; IRC-mediated communications and private messages exchanged between the various developers."},
	month = {2003},
	abstract = {This paper interrogates the claims that open source development is an ideal form of regulatory development. We begin by presenting the literature that offers a framework of modalities of regulation where code, along with laws, markets, and norms shape and influence individual action. Within this framework, it is argued that for an Open Society we need Open Code.	We present the processes through which the Gnutella protocol and the Limewire application are developed by deconstructing the mechanisms of participation and contribution of the individual developers. The techniques of monitoring, modularization and filtering that we identify appear to be inconsistent with open society promises. Instead we suggest a different framing, that of creating nests of interests, whose creators can find refuge from inhabitants of other nests. From that perspective, we suggest that we should stop referring to the war between Copyright and peer-to-peer networks as the battle between good and evil.},
	keywords = {bug reports, cvs, design documents, discussion, discussion forums, documentation, forums, gnutella, issuezilla, limewire, web site},
	attachments = {https://flosshub.org/sites/flosshub.org/files/tsiavosHosein.pdf},
	author = {Prodromos Tsiavos and Ian Hosein}
}
@unpublished {flosswp129,
	title = {The Big Project That Never Ends{\textquoteright}: Role and Task Negotiation Within an Emerging Occupational Community},
	year = {2003},
	month = {December},
	abstract = {This dissertation involved in-depth interviews of over fifty open source developers in two major open source projects. The primary areas of interest were 1) conducting an ethnographic study of the work practices and culture of {\textquoteright}post-burecratic{\textquoteright} organizations to see what lessons these groups may hold for managing intellectual labor and 2) examining whether the open source movement represents a new professional model for software engineering.},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mccormick.pdf},
	author = {Chip McCormick}
}
@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}
}
@article {59,
	title = {A Brief History of Hackerdom},
	year = {1999},
	pages = {1--7},
	author = {Raymond, E.S.}
}
