@proceedings {1875,
	title = {Considering the use of walled gardens for FLOSS project communication},
	year = {2017},
	month = {05/2017},
	abstract = {At its core, free, libre, and open source software (FLOSS) is defined by its adherence to a set of licenses that give various freedoms to the users of the software, for example the ability to use the software, to read or modify its source code, and to distribute the software to others. In addition, many FLOSS projects and developers also champion other values related to "freedom" and "openness", such as transparency, for example in communication and decision-making, or community-orientedness, for example in broadening access, collaboration, and participation. This paper explores how one increasingly common software development practice - communicating inside non-archived, third-party "walled gardens" - puts these FLOSS values into conflict. If communities choose to use non-archived walled gardens for communication, they may be prioritizing one type of openness (broad participation) over another (transparency). We use 18 FLOSS projects as a sample to describe how walled gardens are currently being used for intra-project communication, as well as to determine whether or not these projects provide archives of these communications. Findings will be useful to the FLOSS community as a whole as it seeks to under- stand the evolution and impact of its communication choices.},
	keywords = {apache, chat, communication, email, free software, irc, mailing list, open source, Slack, Stack Overflow, teams, Wordpress},
	doi = {10.1007/978-3-319-57735-7_1},
	url = {https://link.springer.com/content/pdf/10.1007\%2F978-3-319-57735-7_1.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/preprint_0.pdf},
	author = {Squire, Megan}
}
@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 {1899,
	title = {Progression and Forecast of a Curated Web-of-Trust: A Study on the Debian Project{\textquoteright}s Cryptographic Keyring},
	volume = {496},
	year = {2017},
	month = {05/2017},
	pages = {117-127},
	publisher = {Springer},
	abstract = {The Debian project is one of the largest free software undertakings worldwide. It is geographically distributed, and participation in the project is done on a voluntary basis, without a single formal employee or directly funded person. As we will explain, due to the nature of the project, its authentication needs are very strict{\textemdash}User/password schemes are way surpassed, and centralized trust management schemes such as PKI are not compatible with its distributed and flat organization; fully decentralized schemes such as the PGP Web of Trust are insuficient by themselves. The Debian project has solved this need by using what we termed a {\textquotedblleft}curated Web of Trust{\textquotedblright}.

We will explain some lessons learned from a massive key migration process that was triggered in 2014. We will present the social insight we have found from examining the relationships expressed as signatures in this curated Web of Trust, some recommendations on personal key-signing policies, and a statistical study and forecast on aging, refreshment and survival of project participants stemming from an analysis on their key-handling.},
	keywords = {cryptography, curated Web of Trust, debian, Keyring, trust management},
	doi = {10.1007/978-3-319-57735-7_12},
	url = {https://link.springer.com/chapter/10.1007/978-3-319-57735-7_12},
	author = {Gunnar Wolf and V{\'\i}ctor Gonz{\'a}lez Quiroga}
}
@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 {1713,
	title = {Gender and Tenure Diversity in GitHub Teams},
	year = {2015},
	abstract = {Software development is usually a collaborative venture.
Open Source Software (OSS) projects are no exception; indeed,
by design, the OSS approach can accommodate teams
that are more open, geographically distributed, and dynamic
than commercial teams. This, we find, leads to OSS teams
that are quite diverse. Team diversity, predominantly in of-
fline groups, is known to correlate with team output, mostly
with positive effects. How about in OSS?
Using GITHUB, the largest publicly available collection of
OSS projects, we studied how gender and tenure diversity
relate to team productivity and turnover. Using regression
modeling of GITHUB data and the results of a survey, we
show that both gender and tenure diversity are positive and
significant predictors of productivity, together explaining a
sizable fraction of the data variability. These results can
inform decision making on all levels, leading to better outcomes
in recruiting and performance.},
	keywords = {gender, github, team},
	url = {http://bvasiles.github.io/papers/chi15.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/chi15.pdf},
	author = {Vasilescu, Bogdan and Posnett, Daryl and Ray, Baishakhi and van den Brand, Mark G.J. and Serebrenik, Alexander and Devanbu, Premkumar and Filkov, Vladimir}
}
@proceedings {1725,
	title = {Mining StackOverflow to Filter out Off-topic IRC Discussion},
	year = {2015},
	month = {05/2015},
	pages = {4 pages},
	abstract = {Internet Relay Chat (IRC) is a commonly used tool by OpenSource developers. Developers use IRC channels to discuss programming related problems, but much of the discussion is irrelevant and off-topic. Essentially if we treat IRC discussions like email messages, and apply spam filtering, we can try to filter out the spam (the off-topic discussions) from the ham (the programming discussions). Yet we need labelled data that unfortunately takes time to curate.
To avoid costly curration in order to filter out off-topic discussions, we need positive and negative data-sources. On- line discussion forums, such as StackOverflow, are very effective for solving programming problems. By engaging in open-data, StackOverflow data becomes a powerful source of labelled text regarding programming. This work shows that we can train classifiers using StackOverflow posts as positive examples of on-topic programming discussion. YouTube video comments, notorious for their lack of quality, serve as training set of off- topic discussion. By exploiting these datasets, accurate classifiers can be built, tested and evaluated that require very little effort for end-users to deploy and exploit.},
	keywords = {irc, topics},
	url = {http://webdocs.cs.ualberta.ca/~hindle1/2015/shaiful-mining_so.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/shaiful-mining_so.pdf},
	author = {Shaiful Alam Chowdhury and Hindle, Abram}
}
@inbook {1738,
	title = {A Qualitative Study on the Adoption of Open Source Software in Information Technology Outsourcing Organizations},
	booktitle = {Open Source Systems: Adoption and Impact},
	series = {IFIP Advances in Information and Communication Technology},
	volume = {451},
	year = {2015},
	pages = {103-113},
	publisher = {Springer International Publishing},
	organization = {Springer International Publishing},
	abstract = {The purpose of this paper is to identify the influence of Outsourcing on Open source software (OSS) and further investigate the factors that impact the adoption of OSS in global Information Technology (IT) outsourcing organizations serviced by Indian IT services providers. This exploratory research adopted positivism research philosophy and qualitative approach. An in-depth interview was conducted with ten participants across IT outsourcing organizations, IT service providers, and OSS service providers. The results show that IT outsourcing was not found to have an impact on OSS adoption. However, eight factors including management support and OSS support availability was identified to influence OSS adoption. IT services providers can utilize this research model to increase their understanding of why some IT outsourcing organizations choose to adopt OSS, while seemingly similar ones facing similar market conditions do not.
},
	keywords = {Diffusion of innovation, Indian IT, IT outsourcing, open source software, OSS adoption, TOE},
	isbn = {978-3-319-17836-3},
	doi = {10.1007/978-3-319-17837-0_10},
	url = {http://dx.doi.org/10.1007/978-3-319-17837-0_10},
	author = {Ramanathan, Lakshmanan and Iyer, Sundaresan Krishnan},
	editor = {Damiani, Ernesto and Frati, Fulvio and Dirk Riehle and Wasserman, Anthony I.}
}
@proceedings {1715,
	title = {"Should we move to Stack Overflow?" Measuring the utility of social media for developer support},
	year = {2015},
	month = {05/2015},
	pages = {10pp},
	publisher = {IEEE},
	abstract = {Stack Overflow is an enormously popular question-and-answer web site intended for software developers to help each other with programming issues. Some software projects aimed at developers (for example, application programming interfaces, application engines, cloud services, development frameworks, and the like) are closing their self-supported developer discussion forums and mailing lists and instead directing developers to use special-purpose tags on Stack Overflow. The goals of this paper are to document the main reasons given for moving developer support to Stack Overflow, and then to collect and analyze data from a group of software projects that have done this, in order to show whether the expected quality of support was actually achieved. The analysis shows that for all four software projects in this study, two of the desired quality indicators, developer participation and response time, did show improvements on Stack Overflow as compared to mailing lists and forums. However, we also found several projects that moved back from Stack Overflow, despite achieving these desired improvements. The results of this study are applicable to a wide variety of software projects that provide developer support using social media.},
	keywords = {developer support, forums, mailing list, metrics, quality, social media, Stack Overflow, technical support},
	attachments = {https://flosshub.org/sites/flosshub.org/files/SEIP2015stackv2.pdf},
	author = {Squire, Megan}
}
@booklet {1709,
	title = {Understanding and Supporting the Choice of an Appropriate Task to Start With In Open Source Software Communities },
	howpublished = {Hawaii International Conference on System Sciences 48},
	year = {2015},
	pages = {5299-5308},
	publisher = {IEEE},
	abstract = {Open Source Software (OSS) projects leverage the
contribution of outsiders. In fact, the sustainability of
many projects relies on retaining some of these
newcomers. Usually these communities do not
coordinate the work of the newcomers, who go to the
issue trackers and self-select a task to start with. We
found that {\textquotedblleft}finding a way to start{\textquotedblright} was reported as an
important issue by practitioners. To further investigate
this specific barrier, we conducted a qualitative
analysis with data obtained from semi-structured
interviews with 36 subjects from 14 different projects,
including newcomers and experienced members. We
used procedures of Grounded Theory {\textendash} open and axial
coding {\textendash} to analyze the data. We found that newcomers
are not confident enough to choose their initial task
and they need information about the tasks or direction
from the community to support choosing a task more
suitable for them. We also present a set of strategies
identified in the literature, interviews, and state-of-the practice
that can provide newcomers with such
information, enabling them to be more confident when
choosing their first tasks and collaborate with the
community. },
	keywords = {coordination, joining process, new developer, newcomers, onboarding, open source software, task selection},
	attachments = {https://flosshub.org/sites/flosshub.org/files/HICSS-48_present.pdf},
	author = {Steinmacher, Igor and Conte, Tayana and Gerosa, MarcoAur{\'e}lio}
}
@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}
}
@conference {Passos:2014:DFA:2597073.2597124,
	title = {A Dataset of Feature Additions and Feature Removals from the Linux Kernel},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {376{\textendash}379},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {This paper describes a dataset of feature additions and removals in the Linux kernel evolution history, spanning over seven years of kernel development. Features, in this context, denote configurable system options that users select when creating customized kernel images. The provided dataset is the largest corpus we are aware of capturing feature additions and removals, allowing researchers to assess the kernel evolution from a feature-oriented point-of-view. Furthermore, the dataset can be used to better understand how features evolve over time, and how different artifacts change as a result. One particular use of the dataset is to provide a real-world case to assess existing support for feature traceability and evolution. In this paper, we detail the dataset extraction process, the underlying database schema, and example queries. The dataset is directly available at our Bitbucket repository: https://bitbucket.org/lpassos/kconfigdb
},
	keywords = {evolution, linux, msr data showcase, Traceability, Version Control History},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597124},
	url = {http://doi.acm.org/10.1145/2597073.2597124},
	attachments = {https://flosshub.org/sites/flosshub.org/files/kernel.pdf},
	author = {Passos, Leonardo and Czarnecki, Krzysztof}
}
@conference {Ahmed:2014:IAC:2641580.2641585,
	title = {The Impact of Automatic Crash Reports on Bug Triaging and Development in Mozilla},
	booktitle = {Proceedings of The International Symposium on Open Collaboration},
	series = {OpenSym {\textquoteright}14},
	year = {2014},
	pages = {1:1{\textendash}1:8},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Free/Open Source Software projects often rely on users submitting bug reports. However, reports submitted by novice users may lack information critical to developers, and the process may be intimidating and difficult. To gather more and better data, projects deploy automatic crash reporting tools, which capture stack traces and memory dumps when a crash occurs. These systems potentially generate large volumes of data, which may overwhelm developers, and their presence may discourage users from submitting traditional bug reports. In this paper, we examine Mozilla{\textquoteright}s automatic crash reporting system and how it affects their bug triaging process. We find that fewer than 0.00009\% of crash reports end up in a bug report, but as many as 2.33\% of bug reports have data from crash reports added. Feedback from developers shows that despite some problems, these systems are valuable. We conclude with a discussion of the pros and cons of automatic crash reporting systems.
},
	keywords = {Automatic Crash reporting, debugging, FOSS, Free/Open Source Software, Open Bug Reporting, testing},
	isbn = {978-1-4503-3016-9},
	doi = {10.1145/2641580.2641585},
	url = {http://doi.acm.org/10.1145/2641580.2641585},
	author = {Ahmed, Iftekhar and Mohan, Nitin and Jensen, Carlos}
}
@conference {Rahman:2014:IPR:2597073.2597121,
	title = {An Insight into the Pull Requests of GitHub},
	booktitle = {Proceedings of the 11th Working Conference on Mining Software Repositories},
	series = {MSR 2014},
	year = {2014},
	pages = {364{\textendash}367},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Given the increasing number of unsuccessful pull requests in GitHub projects, insights into the success and failure of these requests are essential for the developers. In this paper, we provide a comparative study between successful and unsuccessful pull requests made to 78 GitHub base projects by 20,142 developers from 103,192 forked projects. In the study, we analyze pull request discussion texts, project specific information (e.g., domain, maturity), and developer specific information (e.g., experience) in order to report useful insights, and use them to contrast between successful and unsuccessful pull requests. We believe our study will help developers overcome the issues with pull requests in GitHub, and project administrators with informed decision making.
},
	keywords = {Commit comments, mining challenge, msr challenge, pull request, topic model},
	isbn = {978-1-4503-2863-0},
	doi = {10.1145/2597073.2597121},
	url = {http://doi.acm.org/10.1145/2597073.2597121},
	attachments = {https://flosshub.org/sites/flosshub.org/files/rahman.pdf},
	author = {Rahman, Mohammad Masudur and Chanchal K. Roy}
}
@article {thomas2014studying,
	title = {Studying software evolution using topic models},
	journal = {Science of Computer Programming},
	volume = {80},
	year = {2014},
	pages = {457{\textendash}479},
	publisher = {Elsevier},
	abstract = {Topic models are generative probabilistic models which have been applied to information
retrieval to automatically organize and provide structure to a text corpus. Topic models
discover topics in the corpus, which represent real world concepts by frequently cooccurring
words. Recently, researchers found topics to be effective tools for structuring
various software artifacts, such as source code, requirements documents, and bug reports.
This research also hypothesized that using topics to describe the evolution of software
repositories could be useful for maintenance and understanding tasks. However, research
has yet to determine whether these automatically discovered topic evolutions describe the
evolution of source code in a way that is relevant or meaningful to project stakeholders, and
thus it is not clear whether topic models are a suitable tool for this task.
In this paper, we take a first step towards evaluating topic models in the analysis of
software evolution by performing a detailed manual analysis on the source code histories
of two well-known and well-documented systems, JHotDraw and jEdit. We define and
compute various metrics on the discovered topic evolutions and manually investigate how
and why the metrics evolve over time. We find that the large majority (87\%{\textendash}89\%) of topic
evolutions correspond well with actual code change activities by developers. We are thus
encouraged to use topic models as tools for studying the evolution of a software system.},
	keywords = {Latent Dirichlet allocation, mining software repositories, software evolution, topic model},
	url = {http://sail.cs.queensu.ca/publications/pubs/Thomas-2012-SCP.pdf},
	author = {Stephen W. Thomas and Adams, Bram and Hassan, Ahmed E. and Blostein, Dorothea}
}
@proceedings {1488,
	title = {Apache-Affiliated Twitter Screen Names: A Dataset},
	year = {2013},
	month = {05/2013},
	abstract = {This paper describes a new dataset containing Twitter screen names for members of the projects affiliated with the Apache Software Foundation (ASF). The dataset includes the confirmed Twitter screen names, as well as the real name as listed on Twitter, and the user identification as used within the Apache organization. The paper also describes the process used to collect and clean this data, and shows some sample queries for learning how to use the data. The dataset has been donated to the FLOSSmole project and is available for download (https://code. google.com/p/flossmole/downloads/detail?name=apacheTwitter2013-Jan.zip) or direct querying via a database client. },
	keywords = {apache, dataset, twitter},
	attachments = {https://flosshub.org/sites/flosshub.org/files/apacheTwitterPREPRINT.pdf , https://flosshub.org/sites/flosshub.org/files/MSR\%20presentation.pdf},
	author = {Squire, Megan}
}
@conference {Venkataramani:2013:DTE:2487788.2487832,
	title = {Discovery of Technical Expertise from Open Source Code Repositories},
	booktitle = {Proceedings of the 22Nd International Conference on World Wide Web Companion},
	series = {WWW {\textquoteright}13 Companion},
	year = {2013},
	pages = {97{\textendash}98},
	publisher = {International World Wide Web Conferences Steering Committee},
	organization = {International World Wide Web Conferences Steering Committee},
	address = {Republic and Canton of Geneva, Switzerland},
	abstract = {Online Question and Answer websites for developers have emerged as the main forums for interaction during the software development process. The veracity of an answer in such websites is typically verified by the number of {\textquoteright}upvotes{\textquoteright} that the answer garners from peer programmers using the same forum. Although this mechanism has proved to be extremely successful in rating the usefulness of the answers, it does not lend itself very elegantly to model the expertise of a user in a particular domain. In this paper, we propose a model to rank the expertise of the developers in a target domain by mining their activity in different opensource projects. To demonstrate the validity of the model, we built a recommendation system for StackOverflow which uses the data mined from GitHub.
},
	keywords = {github, knowledge discovery, recommendations, source code repository, stackoverflow, technical expertise},
	isbn = {978-1-4503-2038-2},
	url = {http://dl.acm.org/citation.cfm?id=2487788.2487832},
	author = {Venkataramani, Rahul and Gupta, Atul and Asadullah, Allahbaksh and Muddu, Basavaraju and Bhat, Vasudev}
}
@proceedings {1501,
	title = {The Impact of Tangled Code Changes},
	year = {2013},
	month = {05/2013},
	abstract = {When interacting with version control systems, developers often commit unrelated or loosely related code changes
in a single transaction. When analyzing the version history, such
tangled changes will make all changes to all modules appear
related, possibly compromising the resulting analyses through
noise and bias. In an investigation of five open-source JAVA
projects, we found up to 15\% of all bug fixes to consist of multiple
tangled changes. Using a multi-predictor approach to untangle
changes, we show that on average at least 16.6\% of all source
files are incorrectly associated with bug reports. We recommend
better change organization to limit the impact of tangled changes.},
	keywords = {bias, data quality, history, java, mining software repositories, noise, tangled code changes, version control},
	url = {http://www.kim-herzig.de/wp-content/uploads/2013/03/msr2013-untangling.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/msr2013-untangling.pdf},
	author = {Kim Herzig and Zeller, Andreas}
}
@conference {abdouSEKE2013,
	title = {{Managing Corrective Actions to Closure in Open Source Software Test Process}},
	booktitle = {The 25th International Conference on Software Engineering and Knowledge Engineering (SEKE 2013)},
	year = {2013},
	pages = {306{\textendash}311},
	address = {Boston, USA},
	abstract = {In assessing test process maturity, one of the goals is to manage disciplinary issues. Managing corrective actions to closure is known to aid software quality assurance, in general, and testing process activities, in particular. In this paper, a framework for software testing assessment, namely OSS-TPA, that aims to evaluate corrective actions in OSS test process, is proposed. The OSS-TPA framework is based on earlier studies and relies on a conceptual model for test process activities in OSS development. Using success factors in OSS development, the relationship between the maturity of managing corrective actions and the adoption of OSS is investigated.},
	keywords = {open source software, software engineering, software quality, Software testing, Test Process Improvement.},
	url = {http://index.ksi.edu/conf/seke/2013/cr/282.pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/282.pdf},
	author = {Abdou, Tamer and Grogono, Peter and Kamthan, Pankaj}
}
@book {1540,
	title = {The Role of Microblogging in OSS Knowledge Management},
	series = {IFIP Advances in Information and Communication TechnologyOpen Source Software: Quality Verification},
	volume = {404},
	year = {2013},
	pages = {140 - 152},
	publisher = {Springer Berlin Heidelberg},
	organization = {Springer Berlin Heidelberg},
	address = {Berlin, Heidelberg},
	abstract = {

Given that microblogging has been shown to play a valuable role in knowledge management within companies, it is useful to understand how it is being used in relation to OSS. This project studies tweets related to 12 open source projects and keywords, ranging from web content management systems (CMSes) to general office applications. It found considerable differences in the content and exchange of tweets, especially between specialist products such as CMSes and office suites such as OpenOffice. Tweets concerning the more specialist projects tended to provide information rather than updates on the user{\textquoteright}s current status. We found a high proportion of event-driven traffic for some CMS projects, and a lower proportion for the office products and groups of projects.
},
	keywords = {twitter},
	isbn = {978-3-642-38928-3},
	issn = {1868-422X},
	doi = {10.1007/978-3-642-38928-3_10},
	author = {Lewis, Jonathan},
	editor = {Petrinja, Etiel and Succi, Giancarlo and Ioini, Nabil and Sillitti, Alberto}
}
@article {1400,
	title = {Analyzing and mining a code search engine usage log},
	journal = {Empirical Software Engineering},
	volume = {17},
	year = {2012},
	month = {8/2012},
	pages = {424 - 466},
	abstract = {This paper presents an analysis of a year long usage log of Koders, the first commercially available Internet-Scale code search engine (http://www.koders.com). The usage log comprises about ten million activities from more than three million users. Analysis of the usage data shows that despite of attracting a large number of visitors, Koders has a very sparse usage and that it lacks regular usage from many of its users. When compared to Web search, search behavior in Koders showed many similar patterns. A topic modeling analysis of the usage data shows what topics users of Koders are looking for. Observations on the prevalence of these topics among the users, and observations on how search and download activities vary across topics, lead to the conclusion that users who find code search engines usable are those who already know to a high level of specificity what to look for. This paper also presents a general categorization of these topics that provides insights on the different ways code search engine users express their queries. It identifies various forms of queries in Koders{\textquoteright}s log and the kinds of results addressed by the queries. It also provides several suggestions for improvements in code search engines based on the analysis of usage, topics, and query forms. The work presented in this paper is the first of its kind that reveals several insights on the usage of an Internet-Scale code search engine.},
	keywords = {code search, koders, search, search engine, topics},
	issn = {1573-7616},
	doi = {10.1007/s10664-010-9144-6},
	author = {Bajracharya, Sushil Krishna and Lopes, Cristina Videira}
}
@article {1395,
	title = {Automated topic naming: supporting cross-project analysis of software maintenance activities},
	journal = {Empirical Software Engineering},
	year = {2012},
	abstract = {Software repositories provide a deluge of software artifacts to analyze. Researchers have attempted to summarize, categorize, and relate these artifacts by using semi-unsupervised machine-learning algorithms, such as Latent Dirichlet Allocation (LDA). LDA is used for concept and topic analysis to suggest candidate word-lists or topics that describe and relate software artifacts. However, these word-lists and topics are difficult to interpret in the absence of meaningful summary labels. Current attempts to interpret topics assume manual labelling and do not use domain-specific knowledge to improve, contextualize, or describe results for the developers. We propose a solution: automated labelled topic extraction. Topics are extracted using LDA from commit-log comments recovered from source control systems. These topics are given labels from a generalizable cross-project taxonomy, consisting of non-functional requirements. Our approach was evaluated with experiments and case studies on three large-scale Relational Database Management System (RDBMS) projects: MySQL, PostgreSQL and MaxDB. The case studies show that labelled topic extraction can produce appropriate, context-sensitive labels that are relevant to these projects, and provide fresh insight into their evolving software development activities. },
	keywords = {LDA, maxdb, mysql, postgresql, topics},
	issn = {1573-7616},
	doi = {10.1007/s10664-012-9209-9},
	author = {Hindle, Abram and Ernst, Neil A. and Godfrey, Michael W. and Mylopoulos, John}
}
@proceedings {1377,
	title = {Examining Turnover in Open Source Software Projects Using a Logistic Hierarchical Linear Modeling Approach},
	volume = {378},
	year = {2012},
	month = {09/2012},
	address = {Eighth International Conference on Open Source Systems},
	abstract = {Developer turnover in open source software projects is a critical and insufficiently researched problem. Previous research has focused on understanding the developer motivations to contribute using either the individual developer perspective or the project perspective. In this exploratory study we argue that because the developers are embedded in projects it is imperative to include both perspectives. We analyze turnover in open source software projects by including both individual developer level factors, as well as project specific factors. Using the Logistic Hierarchical Linear Modeling approach allows us to empirically examine the factors influencing developer turnover and also how these factors differ among developers and projects.},
	keywords = {Logistic Hierarchical Linear Modeling, sourceforge, turnover},
	author = {Sharma, P.N. and Hulland, J. and Daniel, S.}
}
@proceedings {1457,
	title = {The Impact of Formal QA Practices on FLOSS Communities {\textendash} The Case of Mozilla},
	volume = {378},
	year = {2012},
	month = {09/2012},
	pages = {262-267},
	publisher = {IFIP AICT,  Springer},
	abstract = {The number of FLOSS projects that include a QA step in the development model is increasing which suggests that a new layer may be emerging in the classic {\textquotedblleft}onion model{\textquotedblright}. This change might affect the information flow within projects and implicitly their sustainability. Communities, the essential resource of FLOSS projects, have been extensively studied but questions concerning QA remain. This paper takes a step towards answering such questions by analyzing QA mailing lists and issue tracker data for the Mozilla group of projects. Because the Bugzilla data set contains over half a million bugs, data processing and analysis is a considerable challenge for this research. The provisional conclusions are that QA activity may not be increasing steadily over time but is dependent on other factors and that the QA team and other groups of contributors form a highly connected network that doesn{\textquoteright}t contain isolates.},
	keywords = {email, information flow, mailing lists, mozilla, quality assurance, social network analysis, test},
	author = {Barham, Adina}
}
@proceedings {1467,
	title = {A Linguistic Analysis on How Contributors Solve Software Problems in a Distributed Context},
	volume = {378},
	year = {2012},
	note = {"... a sample of 4109 bug reports was extracted from Bugzilla bug report repository"
"The analysis of our sample allows identifying the roles of participants in this activity according to their hierarchical statutes in the community. "
"we look statistically at words that people use in Bugzilla to discern differences in the discourse and representation between participants (core and periphery)"},
	month = {09/2012},
	pages = {322-330},
	publisher = {IFIP AICT,  Springer},
	abstract = {There is a little understanding of distributed solving activities in Open Source communities. This study aimed to provide some insights in this way. It was applied to the context of Bugzilla, the bug tracking system of Mozilla community. This study investigated the organizational aspects of this meditated, complex and highly distributed context through a linguistic analysis method. The main finding of this research shows that the organization of distributed problem-solving activities in Bugzilla isn{\textquoteright}t based only on the hierarchical distribution of the work between core and periphery participants but on their implication in the interactions. This implication varies according to the status of each one participant in the community. That is why we distinguish their roles, as well as, the established modes to manage such activity.},
	keywords = {bug report, bugzilla, linguistic, text mining},
	author = {Masmoudi, H{\'e}la and Boughzala, Imed}
}
@conference {1304,
	title = {Entering the circle of trust},
	booktitle = {Proceeding of the 8th working conference on Mining software repositories - MSR {\textquoteright}11},
	year = {2011},
	note = {"we started by analyzing 219 projects"
},
	month = {05/2011},
	pages = {133-142},
	publisher = {ACM Press},
	organization = {ACM Press},
	address = {New York, New York, USA},
	abstract = {The success of an open-source project depends to a large degree on the proactive and constructive participation by the developer community. An important role that developers play in a project is that of a code committer. However, code-commit privilege is typically restricted to the core group of a project. In this paper, we study the phenomenon of the induction of external developers as code committers. The trustworthiness of an external developer is one of the key factors that determines the granting of commit privileges. Therefore, we formulate different hypotheses to explain how the trust is established in practice. To investigate our hypotheses, we developed an automated approach based on mining code repositories and bug-tracking systems. We implemented the approach and performed an empirical study, using the Eclipse projects, to test the hypotheses. Our results indicate that, most frequently, developers establish trust and credibility in a project by contributing to the project in a non-committer role. Moreover, the employing organization of a developer is another factor--although a less significant one--that influences trust.},
	keywords = {bug tracking, bug tracking system, commits, committers, core, developers, eclipse, trust},
	isbn = {9781450305747},
	doi = {10.1145/1985441.1985462},
	author = {Mani, Senthil and Sinha, Saurabh and Sinha, Vibha Singhal}
}
@conference {Bacchelli:2011:EEE:1985793.1985999,
	title = {Exploring, exposing, and exploiting emails to include human factors in software engineering},
	booktitle = {Companion to the Proceedings of the 33rd International Conference on Software Engineering},
	series = {ICSE {\textquoteright}11},
	year = {2011},
	note = {This paper is a summary of work in the field, for the doctoral consortium.},
	pages = {1074{\textendash}1077},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Researchers mine software repositories to support software maintenance and evolution. The analysis of the structured data, mainly source code and changes, has several benefits and offers precise results. This data, however, leaves communication in the background, and does not permit a deep investigation of the human factor, which is crucial in software engineering.

Software repositories also archive documents, such as emails or comments, that are used to exchange knowledge among people - we call it "people-centric information." By covering this data, we include the human factor in our analysis, yet its unstructured nature makes it currently sub-exploited.

Our work, by focusing on email communication and by implementing the necessary tools, investigates methods for exploring, exposing, and exploiting unstructured data. We believe it is possible to close the gap between development and communication, extract opinions, habits, and views of developers, and link implementation to its rationale; we see in a future where software analysis and development is routinely augmented with people-centric information.},
	keywords = {email communication, toolset, unstructured data},
	isbn = {978-1-4503-0445-0},
	doi = {10.1145/1985793.1985999},
	url = {http://doi.acm.org/10.1145/1985793.1985999},
	author = {Bacchelli, Alberto}
}
@proceedings {1283,
	title = {Framing the Conundrum of Total Cost of Ownership of Open Source Software},
	year = {2011},
	month = {10/2011},
	pages = {208-219},
	publisher = {Springer},
	abstract = {This paper reflects the results of phase I of our study on the total cost of ownership (TCO) of open source software adoption. Not only have we found TCO to be an intriguing issue but it is contentious, baffling and each company approaches it in a distinctive manner (and sometimes not at all). In effect it is a conundrum that needs unpacking before it can be explained and understood. Our paper discusses the components of TCO as total cost of ownership and total cost of acquisition (and besides). Using this broad dichotomy and its various components we then analyze our data to make sense of procurement decisions in relation to open source software in the public sector and private companies.},
	keywords = {benefits, exit costs, open source software, software adoption, Survey, tco, total cost of ownership},
	author = {Maha Shaikh and Cornford, Tony}
}
@article {1323,
	title = {OSS-TMM},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {1 - 22},
	abstract = {Open Source Software (OSS) products do not usually follow traditional software engineering development paradigms. Specifically, testing activities in OSS development may be quite different from those carried out in Closed Source Software (CSS) development. As testing and verification require a good deal of resources in OSS, it is necessary to have ways to assess and improve OSS testing processes. This paper provides a set of testing guidelines and issues that OSS developers can use to decide which testing techniques make most sense for their OSS products. This paper 1) provides a checklist that helps OSS developers identify the most useful testing techniques according to the main characteristics of their products, and 2) outlines a proposal for a method that helps assess the maturity of OSS testing processes. The method is a proposal of a Maturity Model for testing processes (called OSS-TMM). To show its usefulness, the authors apply the method to seven real-life projects. Specifically, the authors apply the method to BusyBox, Apache Httpd, and Eclipse Test \& Performance Tools Platform to show how the checklist supports and guides the testing process of these OSS products.},
	keywords = {testing},
	issn = {1942-3934},
	doi = {10.4018/jossp.2011040101},
	author = {Morasca, Sandro and Taibi, Davide and Tosi, Davide}
}
@article {1420,
	title = {Path dependent stochastic models to detect planned and actual technology use: A case study of OpenOffice},
	journal = {Information and Software Technology},
	volume = {53},
	year = {2011},
	month = {11/2011},
	pages = {1209 - 1226},
	abstract = {Abstract
Context

Adopting IT innovation in organizations is a complex decision process driven by technical, social and economic issues. Thus, those organizations that decide to adopt innovation take a decision of uncertain success of implementation, as the actual use of a new technology might not be the one expected. The misalignment between planned and effective use of innovation is called assimilation gap.
Objective

This research aims at defining a quantitative instrument for measuring the assimilation gap and applying it to the case of the adoption of OSS.
Method

In this paper, we use the theory of path dependence and increasing returns of Arthur. In particular, we model the use of software applications (planned or actual) by stochastic processes defined by the daily amounts of files created with the applications. We quantify the assimilation gap by comparing the resulting models by measures of proximity.
Results

We apply and validate our method to a real case study of introduction of OpenOffice. We have found a gap between the planned and the effective use despite well-defined directives to use the new OS technology. These findings suggest a need of strategy re-calibration that takes into account environmental factors and individual attitudes.
Conclusions

The theory of path dependence is a valid instrument to model the assimilation gap provided information on strategy toward innovation and quantitative data on actual use are available.},
	keywords = {Actual use of technology, Path dependence, Technology adoption, Urn models},
	issn = {09505849},
	doi = {10.1016/j.infsof.2011.05.002},
	url = {http://www.sciencedirect.com/science/article/pii/S0950584911001042},
	author = {Rossi, Bruno and Russo, Barbara and Succi, Giancarlo}
}
@proceedings {1276,
	title = {A Review of Tool Support for User-Related Communication in FLOSS Development},
	year = {2011},
	note = {"We have carried out a literature review addressing communication in FLOSS projects, and contrasted the findings with Human-Computer Interaction (HCI) literature on user-developer communication."},
	month = {10/2011},
	pages = {90-105},
	abstract = {Free/Libre/Open Source Software (FLOSS) projects rely on Internet tools for communication and in coordinating their work. Communication between developers is well supported in FLOSS projects, but user-developer communication has proven out to be challenging. This paper examines the following questions: {\textquotedblright}What kinds of means for communication exist in FLOSS projects for user-developer communication? What kinds of means should there be?{\textquotedblright} We have carried out a literature review addressing communication in FLOSS projects, and contrasted the findings with Human-Computer Interaction (HCI) literature on user-developer communication. HCI literature indicates that user-developer communication is needed during requirements construction, design and evaluation tasks, and HCI specialists are needed for orchestrating the communication and the user related tasks. Communication during the evaluation task is somewhat supported in FLOSS projects, but design and requirements construction are badly in need for support, even though ideas have already been presented. In addition, HCI specialists are in need of different kinds of communication support in FLOSS projects.},
	keywords = {Free/Libre/Open Source Software, Human-Computer Interaction, literature review, Tool Support, User-Developer Communication},
	author = {Rantalinen, Aapo and Hedberg, Henrik and Iivari, Netta}
}
@article {1325,
	title = {Tool Assisted Analysis of Open Source Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {3},
	year = {2011},
	pages = {43 - 78},
	abstract = {Open Source Software (OSS) is currently a widely adopted approach to developing and distributing software. OSS code adoption requires an understanding of the structure of the code base. For a deeper understanding of the maintenance, bug fixing and development activities, the structure of the developer community also needs to be understood, especially the relations between the code and community structures. This, in turn, is essential for the development and maintenance of software containing OSS code. This paper proposes a method and support tool for exploring the relations of the code base and community structures of OSS projects. The method and proposed tool, Binoculars, rely on generic and reusable query operations, formal definitions of which are given in the paper. The authors demonstrate the applicability of Binoculars with two examples. The authors analyze a well-known and active open source project, FFMpeg, and the open source version of the IaaS cloud computing project Eucalyptus.},
	keywords = {artifacts, tools},
	issn = {1942-3934},
	doi = {10.4018/IJOSSP.2011040103},
	author = {Syeed, M.M. Mahbubul and Aaltonen, Timo and Hammouda, Imed and Syst{\"a}, Tarja}
}
@conference {Bougie:2011:TUT:1984701.1984707,
	title = {Towards understanding twitter use in software engineering: preliminary findings, ongoing challenges and future questions},
	booktitle = {Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering},
	series = {Web2SE {\textquoteright}11},
	year = {2011},
	note = {paper d/l from http://www.thechiselgroup.org/publications/content/towards-understanding-twitter-use-software-engineering-preliminary-findings-ong

"From this site, we selected the top 30 individuals for the topics Linux and Eclipse. We chose these two topics based on their potential to expose "tweeters" from a large operating system community as well as an IDE development community. We also decided to investigate a project for which all committers use Twitter. Through a colleague, we were informed that the MXUnit project lists the Twitter user names for all eight of its committers. The MXUnit project [5] is a small, open source ColdFusion test framework that is written as an Eclipse plug-in."},
	pages = {31{\textendash}36},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {There has been some research conducted around the motivation for the use of Twitter and the value brought by micro-blogging tools to individuals and business environments. This paper builds on our understanding of how the phenomenon affects the population which birthed the technology: Software Engineers. We find that the Software Engineering community extensively leverages Twitter{\textquoteright}s capabilities for conversation and information sharing and that use of the tool is notably different between distinct Software Engineering groups. Our work exposes topics for future research and outlines some of the challenges in exploring this type of data.},
	keywords = {eclipse, linux, mxunit, social media, software development, twitter, web 2.0},
	isbn = {978-1-4503-0595-2},
	doi = {10.1145/1984701.1984707},
	url = {http://doi.acm.org/10.1145/1984701.1984707},
	attachments = {https://flosshub.org/sites/flosshub.org/files/WEB2SE2011.pdf},
	author = {Bougie, Gargi and Starke, Jamie and Storey, Margaret-Anne and Daniel M. German}
}
@conference {Bougie:2011:TUT:1984701.1984707,
	title = {Towards understanding twitter use in software engineering: preliminary findings, ongoing challenges and future questions},
	booktitle = {Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering},
	series = {Web2SE {\textquoteright}11},
	year = {2011},
	note = {paper d/l from http://www.thechiselgroup.org/publications/content/towards-understanding-twitter-use-software-engineering-preliminary-findings-ong

"From this site, we selected the top 30 individuals for the topics Linux and Eclipse. We chose these two topics based on their potential to expose "tweeters" from a large operating system community as well as an IDE development community. We also decided to investigate a project for which all committers use Twitter. Through a colleague, we were informed that the MXUnit project lists the Twitter user names for all eight of its committers. The MXUnit project [5] is a small, open source ColdFusion test framework that is written as an Eclipse plug-in."},
	pages = {31{\textendash}36},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {There has been some research conducted around the motivation for the use of Twitter and the value brought by micro-blogging tools to individuals and business environments. This paper builds on our understanding of how the phenomenon affects the population which birthed the technology: Software Engineers. We find that the Software Engineering community extensively leverages Twitter{\textquoteright}s capabilities for conversation and information sharing and that use of the tool is notably different between distinct Software Engineering groups. Our work exposes topics for future research and outlines some of the challenges in exploring this type of data.},
	keywords = {eclipse, linux, mxunit, social media, software development, twitter, web 2.0},
	isbn = {978-1-4503-0595-2},
	doi = {10.1145/1984701.1984707},
	url = {http://doi.acm.org/10.1145/1984701.1984707},
	attachments = {https://flosshub.org/sites/flosshub.org/files/WEB2SE2011_0.pdf},
	author = {Bougie, Gargi and Starke, Jamie and Storey, Margaret-Anne and Daniel M. German}
}
@conference {951,
	title = {The evolution of ANT build systems},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {42 - 51},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {Build systems are responsible for transforming static source code artifacts into executable software. While build systems play such a crucial role in software development and maintenance, they have been largely ignored by software evolution researchers. With a firm understanding of build system aging processes, project managers could allocate personnel and resources to build system maintenance tasks more effectively, reducing the build maintenance overhead on regular development activities. In this paper, we study the evolution of ANT build systems from two perspectives: (1) a static perspective, where we examine the build system specifications using software metrics adopted from the source code domain; and (2) a dynamic perspective where representative sample build runs are conducted and their output logs are analyzed. Case studies of four open source ANT build systems with a combined history of 152 releases show that not only do ANT build systems evolve, but also that they need to react in an agile manner to changes in the source code.},
	keywords = {ant, argouml, build, eclipse, jboss, maintenance, metrics, source code, tomcat},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463341},
	attachments = {https://flosshub.org/sites/flosshub.org/files/42msr2010_mcintosh.pdf},
	author = {McIntosh, Shane and Adams, Bram and Hassan, Ahmed E.}
}
@conference {949,
	title = {Predicting the severity of a reported bug},
	booktitle = {2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010)},
	year = {2010},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Cape Town, South Africa},
	abstract = {The severity of a reported bug is a critical factor in deciding how soon it needs to be fixed. Unfortunately, while clear guidelines exist on how to assign the severity of a bug, it remains an inherent manual process left to the person reporting the bug. In this paper we investigate whether we can accurately predict the severity of a reported bug by analyzing its textual description using text mining algorithms. Based on three cases drawn from the open-source community (Mozilla, Eclipse and GNOME), we conclude that given a training set of sufficient size (approximately 500 reports per severity), it is possible to predict the severity with a reasonable accuracy (both precision and recall vary between 0.65-0.75 with Mozilla and Eclipse; 0.70-0.85 in the case of GNOME).},
	keywords = {bug reports, eclipse, gnome, mozilla, severity, text mining},
	isbn = {978-1-4244-6802-7},
	doi = {10.1109/MSR.2010.5463284},
	attachments = {https://flosshub.org/sites/flosshub.org/files/1lamkanfiDemeyer1.pdf},
	author = {Lamkanfi, Ahmed and Demeyer, Serge and Giger, Emanuel and Goethals, Bart}
}
@article {Singh:2010:SEI:1824760.1824763,
	title = {The small-world effect: The influence of macro-level properties of developer collaboration networks on open-source project success},
	journal = {ACM Trans. Softw. Eng. Methodol.},
	volume = {20},
	number = {2},
	year = {2010},
	pages = {6:1{\textendash}6:27},
	publisher = {ACM},
	address = {New York, NY, USA},
	abstract = {In this study we investigate the impact of community-level networks{\textemdash}relationships that exist among developers in an OSS community{\textemdash}on the productivity of member developers. Specifically, we argue that OSS community networks characterized by small-world properties would positively influence the productivity of the member developers by providing them with speedy and reliable access to more quantity and variety of information and knowledge resources. Specific hypotheses are developed and tested using longitudinal data on a large panel of 4,279 projects from 15 different OSS communities hosted at Sourceforge. Our results suggest that significant variation exists in small-world properties of OSS communities at Sourceforge. After accounting for project, foundry, and time-specific observed and unobserved effects, we found a statistically significant relationship between small-world properties of a community and the technical and commercial success of the software produced by its members. In contrast to the findings of prior research, we also found the lack of a significant relationship between closeness and betweenness centralities of the project teams and their success. These results were robust to a number of controls and model specifications.},
	keywords = {collaborative software development, online community, open source software development, productivity, small world networks, social networks, sourceforge, team formation},
	issn = {1049-331X},
	doi = {10.1145/1824760.1824763},
	url = {http://doi.acm.org/10.1145/1824760.1824763},
	author = {Param Vir Singh}
}
@conference {1223,
	title = {Success and Abandonment in Open Source Commons: Selected Findings from an Empirical Study of Sourceforge.net Projects},
	booktitle = {Second International Workshop on Building Sustainable Open Source Communities (OSCOMM 2010)},
	year = {2010},
	note = {"we utilize data collected from August through October 2006 on 107,747 OSS projects hosted on the open source hosting site Sourceforge.net (SF henceforth). We combined SF project data gathered by the FLOSSmole project (Howison et al., 2006) with other SF data we {\textquotedblleft}crawled{\textquotedblright} ourselves"},
	month = {05/2010},
	abstract = {Some open source software collaborations are sustained over long periods of time and across several versions of a software product, while others become abandoned even before the first version of the product has been developed. In this study, we identify factors that might be responsible for one or the other of these collaborative trajectories. We examine 107,747 open source software projects hosted on Sourceforge.net in August 2006 using data available through the FLOSSmole Project. We employ Classification and Regression Tree modeling and Random Forests statistical approaches to begin to establish an understanding of how various project attributes, especially physical and community ones, contribute to project success or abandonment. We find that factors associated with success and abandonment differ for projects in the early stage of development (pre-first release) compared to projects that have had a first release, and that product utility, project vision, leadership, and group-size are associated with success in open source collaborations. We also find that successful open source projects exist across all types of software and not simply in areas associated with the open source {\textquotedblleft}movement.{\textquotedblright} Other evidence suggests that Sourceforge.net may play an important role in {\textquotedblleft}intellectual match-making.{\textquotedblright}},
	keywords = {abandonment, flossmole, metadata, project failure, project success, sourceforge, time},
	attachments = {https://flosshub.org/sites/flosshub.org/files/osscomm003.pdf},
	author = {Schweik, C. M. and English, R. and Paienjton, Q. and Haire, S.}
}
@conference {1217,
	title = {Trends That Affect Temporal Analysis Using SourceForge Data},
	booktitle = {5th Workshop on Public Data about Software Development (WoPDaSD 2010)},
	year = {2010},
	note = {"In this paper we examine some of the limitations of artifact data by specifically addressing the applicability of SourceForge data to the study of project evolution."

"For our analysis we examine 9,997 Production/Stable or Maintenance phase projects stored in CVS on SourceForge and extracted in October of 2006 [5]"},
	abstract = {SourceForge is a valuable source of software artifact data for researchers who study project evolution and developer behavior. However, the data exhibit patterns that may bias temporal analyses. Most notable are cliff walls in project source code repository timelines, which indicate large commits that are out of character for the given project. These cliff walls often hide significant periods of development and developer collaboration{\textemdash}a threat to studies that rely on SourceForge repository data. We demonstrate how to identify these cliff walls, discuss reasons for their appearance, and propose preliminary measures for mitigating their effects in evolution-oriented studies.},
	keywords = {cliff walls, committers, cvs, evolution, growth, source code, sourceforge, time, time series},
	attachments = {https://flosshub.org/sites/flosshub.org/files/wopdasd001.pdf},
	author = {MacLean, Alexander C. and Pratt, Landon J. and Krein, Jonathan L. and Knutson, Charles D.}
}
@conference {944,
	title = {Learning from defect removals},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {179 - 182},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Recent research has tried to identify changes in source code repositories that fix bugs by linking these changes to reports in issue tracking systems. These changes have been traced back to the point in time when they were previously modified as a way of identifying bug introducing changes. But we observe that not all changes linked to bug tracking systems are fixing bugs; some are enhancing the code. Furthermore, not all fixes are applied at the point in the code where the bug was originally introduced. We flesh out these observations with a manual review of several software projects, and use this opportunity to see how many defects are in the scope of static analysis tools.},
	keywords = {bug fixing, bugzilla, change management, cherry, cvs, eclipse, groovy, launching, source code, svn, text editor},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069500},
	attachments = {https://flosshub.org/sites/flosshub.org/files/179LearnFromDefects-MSR09.pdf},
	author = {Ayewah, Nathaniel and Pugh, William}
}
@conference {942,
	title = {On mining data across software repositories},
	booktitle = {2009 6th IEEE International Working Conference on Mining Software Repositories (MSR)2009 6th IEEE International Working Conference on Mining Software Repositories},
	year = {2009},
	pages = {171 - 174},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Vancouver, BC, Canada},
	abstract = {Software repositories provide abundance of valuable information about open source projects. With the increase in the size of the data maintained by the repositories, automated extraction of such data from individual repositories, as well as of linked information across repositories, has become a necessity. In this paper we describe a framework that uses web scraping to automatically mine repositories and link information across repositories. We discuss two implementations of the framework. In the first implementation, we automatically identify and collect security problem reports from project repositories that deploy the Bugzilla bug tracker using related vulnerability information from the National Vulnerability Database. In the second, we collect security problem reports for projects that deploy the Launchpad bug tracker along with related vulnerability information from the National Vulnerability Database. We have evaluated our tool on various releases of Fedora, Ubuntu, Suse, RedHat, and Firefox projects. The percentage of security bugs identified using our tool is consistent with that reported by other researchers.},
	keywords = {bug reports, bugzilla, Fedora, Firefox, htmlscraper, integration, launchpad, national vulnerability database, RedHat, Suse, tracker, Ubuntu},
	isbn = {978-1-4244-3493-0},
	doi = {10.1109/MSR.2009.5069498},
	attachments = {https://flosshub.org/sites/flosshub.org/files/171MiningAcrossmsr09.pdf},
	author = {Anbalagan, Prasanth and Vouk, Mladen}
}
@conference {1263,
	title = {Multiple Social Networks Analysis of FLOSS Projects using Sargas},
	booktitle = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	note = {"The interval of analysis for the first three networks was from 2003/02/24 to 2003/11/03. These networks were created using the OSSNetwork tool [18]. The source code of the PMD project was collected starting on 2002/06/24..."
"Transflow performs a co-changes analysis of the source code modification history and creates a matrix where software components are connected by taking into account the frequency that they have been changed together (i.e., in the same check-in): if two files have been changed together in the same check-in, an edge is created to link these two files."},
	pages = {1 - 10},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Waikoloa, Hawaii, USA},
	abstract = {Due to their characteristics and claimed advantages, several researchers have been investigating free and open-source projects. Different aspects are being studied: for instance, what motivates developers to join FLOSS projects, the tools, processes and practices used in FLOSS projects, the evolution of FLOSS communities among other things. Researchers have studied collaboration and coordination of open source software developers using an approach known as social network analysis and have gained important insights about these projects. Most researchers, however, have not focused on the integrated study of these networks and, accordingly, in their interrelationships. This paper describes an approach and tool to combine multiple social networks to study the evolution of open-source projects. Our tool, named Sargas, allows comparison and visualization of different social networks at the same time. Initial results of our analysis can be used to extend the "onion-model" of open source participation.},
	keywords = {case study, multiple social networks, ossnetwork, pmd, social network analysis, transflow},
	isbn = {978-0-7695-3450-3},
	doi = {10.1109/HICSS.2009.316},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-06.pdf},
	author = {de Sousa, S.F. and Balieiro, M.A. and dos R. Costa, J.M. and de Souza, C.R.B.}
}
@article {1082,
	title = {Returns from social capital in open source software networks},
	journal = {Journal of Evolutionary Economics},
	volume = {19},
	year = {2009},
	note = {"The data we use in this analysis come from the SourceForge.net Research Data (Department of Computer Science and Engineering, University of Notre Dame)." "Particularly, our dataset is a sub-sample of 2,962 valid observations over twelve months of projects aimed at developing games{\textquoteright} software. To get this sample, we look at the monthly dumps of data and select all projects that belong to the category of GNU Public License (GPL) [6]. "
dependent variable: performance (number of downloads); independent variable: social network ("Here we measure ties among projects through the individuals{\textquoteright} member and contributor roles at projects on the network over time.)},
	month = {4/2009},
	pages = {277 - 295},
	abstract = {Open Source Software projects base their operation on a collaborative structure for knowledge exchange in the form of provision or reception of information, expertise, and feedback on the creation of source code. Here, we address the direction of these knowledge flows among projects throughout social networks and their impact on project success. We identify the roles of membership or contribution that individuals play within projects. We found that connections through contributors who bring their knowledge to the project, improve project success, and that connection through members, who transfer their knowledge towards other projects, enhance project success. Finally, we found that ties through shared membership and contributions hamper project success. The analysis of knowledge flows and their impact on project success imply a translation of returns from investment in social capital, where investment takes the shape of knowledge flows and the returns mean the projects{\textquoteright} diffusion over the network.},
	keywords = {contributors, developers, games, gpl, project success, roles, social capital, social network analysis, social networks, sourceforge, srda, teams},
	issn = {1432-1386},
	doi = {10.1007/s00191-008-0125-5},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Mendez-DuronGarcia.pdf},
	author = {M{\'e}ndez-Dur{\'o}n, Rebeca and Garc{\'\i}a, Clara E.}
}
@conference {853,
	title = {Tagsplanations: Explaining Recommendations using Tags},
	booktitle = {International Conference on Intelligent User Interfaces},
	year = {2009},
	month = {02/08/2009},
	address = {Sanibel Island, FL},
	keywords = {recommender, SYSTEMS, tagging,},
	author = {Vig, J. and Sen, S. and Riedl, J.}
}
@article {1238,
	title = {Teaching Software Engineering with Free/Libre Open Source Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	month = {31/2009},
	pages = {72 - 90},
	abstract = {One of the major problems in software engineering education is the involvement of students in real world software projects. Industry projects are a solution, but in many cases they are hard to find and student participation can be problematic due to cultural, familiarization and other practical reasons. The abundance of Free / Libre Open Source Software (FLOSS) projects is a neat solution, offering multi-lingual, multicultural environments in virtually every application domain, at different levels of project size, maturity, organization etc. The paper analyzes how acquisition of practical experience on several basic and advanced software engineering topics can be achieved by working in a FLOSS project. The kind of skills that can be acquired are those requested by the Overview Report for Computing Curricula by ACM and topics examined are those of the Software Engineering Body of Knowledge, by IEEE. Also software engineering areas that require special care or that may not prove suitable for such treatment are identified. Various isolated teaching cases pertaining to this approach are presented and discussed.},
	keywords = {curriculum, education, teaching, undergraduate},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009010105},
	author = {Ioannis Stamelos}
}
@article {1236,
	title = {Tools for the Study of the Usual Data Sources found in Libre Software Projects},
	journal = {International Journal of Open Source Software and Processes},
	volume = {1},
	year = {2009},
	month = {31/2009},
	pages = {24 - 45},
	abstract = {Due to the open nature of Free/Libre/Open Source software projects, researchers have gained access to a rich set of development-related information. Although this information is publicly available on the Internet, obtaining and analyzing it in a convenient way is not an easy task and many considerations have to be taken into account. In this paper we present the most important data sources that can be found in libre software projects and that are studied by the research community: source code, source code management systems, mailing lists and bug tracking systems. We will give advice for the problems that can be found when retrieving and preparing the data sources for a posterior analysis, as well as provide information about the tools that support these tasks.},
	keywords = {bug tracking systems, data sources, mailing lists, scm, tools},
	issn = {1942-3934},
	doi = {10.4018/jossp.2009010102},
	attachments = {https://flosshub.org/sites/flosshub.org/files/robles.pdf},
	author = {Gregorio Robles and Gonz{\'a}lez-Barahona, Jes{\'u}s M. and Izquierdo-Cortazar, Daniel and Herraiz, Israel}
}
@conference {Orsila:2009:TIO:1527033.1527037,
	title = {Trust issues in open source software development},
	booktitle = {Proceedings of the Warm Up Workshop for ACM/IEEE ICSE 2010},
	series = {WUP {\textquoteright}09},
	year = {2009},
	note = {"We have selected two highly reusable libraries, zlib and FFmpeg. The software repository of the projects were downloaded, but mining the information is not an easy task and we considered various sources {\textemdash} such as bug reports, mailing lists, IRC conversations, and source code comments {\textemdash} in addition to the revision history. "},
	pages = {9{\textendash}12},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Open source software and the associated development model holds great promise, but the issue of trust is a major challenge. This applies to companies wishing to adopt the open source model but also within open source projects. We investigate this issue by data mining open source repositories to study two related phenomena: update propagation and distributed version control.},
	keywords = {ffmpeg, trust, version control, zlib},
	isbn = {978-1-60558-565-9},
	doi = {10.1145/1527033.1527037},
	url = {http://doi.acm.org/10.1145/1527033.1527037},
	author = {Orsila, Heikki and Geldenhuys, Jaco and Ruokonen, Anna and Hammouda, Imed}
}
@conference {804,
	title = {Users of Open Source Software - How do they get help?},
	booktitle = {HICSS 2009},
	year = {2009},
	abstract = {A study was conducted across multiple open source software online technical help communities. This paper presents the types of discussions that occur, the types of questions asked and the type of responses that are given. The implications for socio-technical design are considered, exploring how help requests and discussions can be used to improve future help-giving, documentation and interface and functionality redesign.},
	keywords = {technical help},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.489},
	author = {Singh, V and Twidale, M.B and Nichols, D.M}
}
@article {10.1109/HICSS.2009.1005,
	title = {Users of Open Source Software - How Do They Get Help?},
	journal = {42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	note = {"we collected twenty threads each from eight different websites making a total of 160 threads"},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {A study was conducted across multiple open source software online technical help communities. This paper presents the types of discussions that occur, the types of questions asked and the type of responses that are given. The implications for socio-technical design are considered, exploring how help requests and discussions can be used to improve future help-giving, documentation and interface and functionality redesign.},
	keywords = {technical help},
	isbn = {978-0-7695-3450-3},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.1005},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-04.pdf},
	author = {Singh, Vandana and Michael B Twidale and David M Nichols}
}
@conference {597,
	title = {Using FLOSS Project Metadata in the Undergraduate Classroom},
	booktitle = {OSS2009: Open Source Ecosystems: Diverse Communities Interacting (IFIP 2.13)},
	series = {IFIP Advances in Information and Communication Technology },
	volume = {299/2009},
	year = {2009},
	month = {2009///},
	pages = {330 - 339},
	publisher = {Springer},
	organization = {Springer},
	chapter = {29},
	abstract = {This paper describes our efforts to use the large amounts of data available from public repositories of free, libre, and open source software (FLOSS) in our undergraduate classrooms to teach concepts that would have previously been taught using other types of data from other sources.
},
	keywords = {artificial intelligence, database, education, teaching, undergraduate, undergraduate research},
	issn = {978-3-642-02031-5},
	doi = {http://dx.doi.org/10.1007/978-3-642-02032-2_29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Using\%20FLOSS\%20Project\%20Metadata.pdf},
	author = {Squire, Megan and Duvall, Shannon}
}
@article {10.1109/HICSS.2009.1014,
	title = {Using Software Archaeology to Measure Knowledge Loss in Software Projects Due to Developer Turnover},
	journal = {2009 42nd Hawaii International Conference on System Sciences (HICSS 2009)},
	year = {2009},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	address = {Los Alamitos, CA, USA},
	abstract = {Developer turnover can result in a major problem when developing software. When senior developers abandon a software project, they leave a knowledge gap that has to be managed. In addition, new (junior) developers require some time in order to achieve the desired level of productivity. In this paper, we present a methodology to measure the effect of knowledge loss due to developer turnover in software projects. For a given software project, we measure the quantity of code that has been authored by developers that do not belong to the current development team, which we define as orphaned code. Besides, we study how orphaned code is managed by the project. Our methodology is based on the concept of software archaeology, a derivation of software evolution. As case studies we have selected four FLOSS (free, libre, open source software) projects, from purely driven by volunteers to company-supported. The application of our methodology to these case studies will give insight into the turnover that these projects suffer and how they have managed it and shows that this methodology is worth being augmented in future research.},
	keywords = {attrition, case study, developers, evince, evolution, gimp, growth, knowledge collaboration, lines of code, nautilus, quality, sloc, turnover},
	isbn = {978-0-7695-3450-3},
	doi = {http://doi.ieeecomputersociety.org/10.1109/HICSS.2009.1014},
	attachments = {https://flosshub.org/sites/flosshub.org/files/07-07-08.pdf},
	author = {Izquierdo-Cortazar, Daniel and Gregorio Robles and Ortega, Felipe and Jesus M. Gonzalez-Barahona}
}
@article {Au20099,
	title = {Virtual organizational learning in open source software development projects},
	journal = {Information \& Management},
	volume = {46},
	number = {1},
	year = {2009},
	pages = {9 - 15},
	abstract = {We studied virtual organizational learning in open source software (OSS) development projects. Specifically, our research focused on learning effects of OSS projects and the factors that affect the learning process. The number and percentage of resolved bugs and bug resolution time of 118 SourceForge.net OSS projects were used to measure the learning effects. Projects were characterized by project type, number and experience of developers, number of bugs, and bug resolution time. Our results provided evidence of virtual organizational learning in OSS development projects and support for several factors as determinants of performance. Team size was a significant predictor, with mid-sized project teams functioning best. Teams of three to seven developers exhibited the highest efficiency over time and teams of eight to 15 produced the lowest mean time for bug resolution. Increasing the percentage of bugs assigned to specific developers or boosting developer participation in other OSS projects also improved performance. Furthermore, project type introduced variability in project team performance.},
	keywords = {bug fixing, bugs, learning, Project performance, sourceforge, team size, teams, virtual organization},
	issn = {0378-7206},
	doi = {DOI: 10.1016/j.im.2008.09.004},
	url = {http://www.sciencedirect.com/science/article/B6VD0-4V1D7NT-1/2/a3bbf7652c674f753398160b8f05f6e9},
	author = {Yoris A. Au and Darrell Carpenter and Xiaogang Chen and Jan G. Clark}
}
@article {Xu2009151,
	title = {Volunteers{\textquoteright} involvement in online community based software development},
	journal = {Information \& Management},
	volume = {46},
	number = {3},
	year = {2009},
	note = {"Data were collected through an online survey and by searching project archives. On Sourceforge.net, each developer was uniquely identified with a user account, and the developer{\textquoteright}s performance was assessed through the number of function points accepted by the project in a certain time period, obtained through conversion and calculation from the project{\textquoteright}s code repository. Data for other constructs were obtained from the developers{\textquoteright} response to the online survey. "
"a developer{\textquoteright}s performance was measured by the number of function points made and accepted into the project during the observed time period."

project age, development status, license type, number of developers},
	pages = {151 - 158},
	abstract = {We sought to gain understanding of voluntary developers{\textquoteright} involvement in open source software (OSS) projects. Data were collected from voluntary developers working on open source projects. Our findings indicated that a voluntary developer{\textquoteright}s involvement was very important to his or her performance and that involvement was dependent on individual motivations (personal software needs, reputation and skills gaining expectation, enjoyment in open source coding) and project community factors (leadership effectiveness, interpersonal relationship, community ideology). Our work contributes theoretically and empirically to the body of OSS research and has practical implications for OSS project management.},
	keywords = {age, developers, effectiveness, function points, ideology, leadership, MOTIVATION, scm, sourceforge, status, Survey, team size, Volunteers},
	issn = {0378-7206},
	doi = {DOI: 10.1016/j.im.2008.12.005},
	url = {http://www.sciencedirect.com/science/article/B6VD0-4VP1CN0-1/2/8e1c7be4fcedd1419209c5c843ffa923},
	author = {Bo Xu and Donald R. Jones and Bingjia Shao}
}
@conference {Hill:2008:AAM:1370750.1370771,
	title = {AMAP: automatically mining abbreviation expansions in programs to enhance software maintenance tools},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {79{\textendash}88},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {When writing software, developers often employ abbreviations in identifier names. In fact, some abbreviations may never occur with the expanded word, or occur more often in the code. However, most existing program comprehension and search tools do little to address the problem of abbreviations, and therefore may miss meaningful pieces of code or relationships between software artifacts. In this paper, we present an automated approach to mining abbreviation expansions from source code to enhance software maintenance tools that utilize natural language information. Our scoped approach uses contextual information at the method, program, and general software level to automatically select the most appropriate expansion for a given abbreviation. We evaluated our approach on a set of 250 potential abbreviations and found that our scoped approach provides a 57\% improvement in accuracy over the current state of the art.},
	keywords = {automatic abbreviation expansion, azureus, itext.net, liferay, maintenance, natural language, openoffice.org, program comprehension, source code, tiger envelopes, tools},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370771},
	url = {http://doi.acm.org/10.1145/1370750.1370771},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p79-hill.pdf},
	author = {Hill, Emily and Fry, Zachary P. and Boyd, Haley and Sridhara, Giriprasad and Novikova, Yana and Pollock, Lori and Vijay-Shanker, K.}
}
@conference {1460670,
	title = {The confusion of crowds: non-dyadic help interactions},
	booktitle = {CSCW {\textquoteright}08: Proceedings of the 2008 ACM conference on Computer supported cooperative work},
	year = {2008},
	pages = {699{\textendash}702},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Help-giving interactions in open source technical support 
often involve more people than the conventional help-giver 
help-seeker pair. Contributions include lightweight but 
useful me-too contributions from fellow help-seekers. 
Problems with the reuse of help documentation may be 
resolved by contextualized discussions, and those 
discussions themselves are found to be substantially reused. },
	keywords = {help-giving, technical help},
	isbn = {978-1-60558-007-4},
	doi = {http://doi.acm.org/10.1145/1460563.1460670},
	author = {Singh, V and Twidale, M.B}
}
@article {Giuri2008305,
	title = {Explaining leadership in virtual teams: The case of open source software},
	journal = {Information Economics and Policy},
	volume = {20},
	number = {4},
	year = {2008},
	note = {Empirical Issues in Open Source Software},
	pages = {305 - 315},
	abstract = {This paper contributes to the open source software (OSS) literature by investigating the likelihood that a participant becomes a project leader. Project leaders are key actors in a virtual community and are crucial to the success of the OSS model. Knowledge of the forces that lead to the emergence of project managers among the multitude of participants is still limited. We aim to fill this gap in the literature by analyzing the association between the roles played by an individual who is registered with a project, and a set of individual-level and project-level characteristics. In line with the theory of occupational choice elaborated by (Lazear, E.P., 2002. Entrepreneurship. NBER Working Paper No. 9109, Cambridge, Mass; Lazear, E.P., 2004. Balanced skills and entrepreneurship, American Economic Review 94, pp. 208-211), we find that OSS project leaders possess diversified skill sets which are needed to select the inputs provided by various participants, motivate contributors, and coordinate their efforts. Specialists, like pure developers, are endowed with more focused skill sets. Moreover, we find that the degree of modularity of the development process is positively associated with the presence of project leaders. That result is consistent with the modern theory of modular production (Baldwin, C.Y., Clark, K.B., 1997. Managing in an age of modularity. Harvard Business Review September-October. pp. 84-93; Mateos-Garcia, J., Steinmueller, W.E., 2003. The Open Source Way of Working: A New Paradigm for the Division of Labour in Software Development? SPRU - Science and Technology Policy Studies. Open Source Movement Research INK Working Paper, No. 1; Aoki, M., 2004. An organizational architecture of T-form: Silicon Valley clustering and its institutional coherence. Industrial and Corporate Change 13, pp. 967-981).},
	keywords = {contributors, Human capital, leadership, roles, sourceforge, team},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.06.002},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4SRW10C-1/2/5ce36096ba3947338962268b54a5a7a9},
	author = {Paola Giuri and Francesco Rullani and Salvatore Torrisi}
}
@conference {Hata:2008:EFF:1370750.1370772,
	title = {An extension of fault-prone filtering using precise training and a dynamic threshold},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	pages = {89{\textendash}98},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Fault-prone module detection in source code is important for assurance of software quality. Most previous fault-prone detection approaches have been based on software metrics. Such approaches, however, have difficulties in collecting the metrics and in constructing mathematical models based on the metrics. To mitigate such difficulties, we have proposed a novel approach for detecting fault-prone modules using a spam-filtering technique, named Fault-Prone Filtering. In our approach, fault-prone modules are detected in such a way that the source code modules are considered as text files and are applied to the spam filter directly. In practice, we use the training only errors procedure and apply this procedure to fault-prone. Since no pre-training is required, this procedure can be applied to an actual development field immediately. This paper describes an extension of the training only errors procedures. We introduce a precise unit of training, "modified lines of code," instead of methods. In addition, we introduce the dynamic threshold for classification. The result of the experiment shows that our extension leads to twice the precision with about the same recall, and improves 15\% on the best F1 measurement.},
	keywords = {eclipse, fault-prone modules, spam filter, text mining},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370772},
	url = {http://doi.acm.org/10.1145/1370750.1370772},
	attachments = {https://flosshub.org/sites/flosshub.org/files/p89-hata.pdf},
	author = {Hata, Hideaki and Mizuno, Osamu and Kikuno, Tohru}
}
@article {GonzalezBarahona2008356,
	title = {Geographic origin of libre software developers},
	journal = {Information Economics and Policy},
	volume = {20},
	number = {4},
	year = {2008},
	note = {Empirical Issues in Open Source Software},
	pages = {356 - 363},
	abstract = {This paper examines the claim that libre (free, open source) software involves global development. The anecdotal evidence is that developers usually work in teams including individuals residing in many different geographical areas, time zones and even continents and that, as a whole, the libre software community is also diverse in terms of national origin. However, its exact composition is difficult to capture, since there are few records of the geographical location of developers. Past studies have been based on surveying a limited (and sometimes biased) sample and extrapolating that sample to the global distribution of developers. In this paper we present an alternate approach in which databases are analyzed to create traces of information from which the geographical origin of developers can be inferred. Applying this technique to the SourceForge users database and the mailing lists archives from several large projects, we have estimated the geographical origin of more than one million individuals who are closely related to the libre software development process. The paper concludes that the result is a good proxy for the actual distribution of libre software developers working on global projects.},
	keywords = {developers, email, email address, email archives, geography, mailing list, open source software, sourceforge, timezone, users},
	issn = {0167-6245},
	doi = {DOI: 10.1016/j.infoecopol.2008.07.001},
	url = {http://www.sciencedirect.com/science/article/B6V8J-4T3DCPK-1/2/3981dfbc523eae1d1ce65fb1f0c0edb7},
	author = {Jesus M. Gonzalez-Barahona and Gregorio Robles and Roberto Andradas-Izquierdo and Rishab Aiyer Ghosh}
}
@conference {Siy:2008:SDW:1370750.1370784,
	title = {Summarizing developer work history using time series segmentation: challenge report},
	booktitle = {Proceedings of the 2008 international working conference on Mining software repositories},
	series = {MSR {\textquoteright}08},
	year = {2008},
	month = {05/2008},
	pages = {137{\textendash}140},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Temporal segmentation partitions time series data with the intent of producing more homogeneous segments. It is a technique used to preprocess data so that subsequent time series analysis on individual segments can detect trends that may not be evident when performing time series analysis on the entire dataset.

This technique allows data miners to partition a large dataset without making any assumption of periodicity or any other a priori knowledge of the dataset{\textquoteright}s features.

We investigate the insights that can be gained from the application of time series segmentation to software version repositories. Software version repositories from large projects contain on the order of hundreds of thousands of timestamped entries or more. It is a continuing challenge to aggregate such data so that noise is reduced and important characteristics are brought out.

In this paper, we present a way to summarize developer work history in terms of the files they have modified over time by segmenting the CVS change data of individual Eclipse developers. We show that the files they modify tends to change significantly over time though most of them tend to work within the same directories.},
	keywords = {contributions, cvs, developers, eclipse, msr challenge, temporal segmentation, time series, work history},
	isbn = {978-1-60558-024-1},
	doi = {http://doi.acm.org/10.1145/1370750.1370784},
	url = {http://doi.acm.org/10.1145/1370750.1370784},
	author = {Siy, Harvey and Chundi, Parvathi and Subramaniam, Mahadevan}
}
@conference {623,
	title = {Experiences on Product Development with Open Source Software},
	booktitle = {OSS2007: Open Source Development, Adoption and Innovation (IFIP 2.13)},
	series = {IFIP International Federation for Information Processing },
	volume = {234/2007},
	year = {2007},
	month = {2007///},
	pages = {85 - 96},
	publisher = {Springer},
	organization = {Springer},
	chapter = {7},
	abstract = {This article discusses Nokia{\textquoteright}s experiences of using open source in commercial product development. It presents the development model used in the creation of mobile consumer devices and highlights the opportunities and challenges experienced. This article concludes that the main benefits come from the utilization of already available open source components, and from their quality and flexibility. It illustrates the challenges and solutions faced when mixing open and closed development models at Nokia.
},
	keywords = {gtk, linux, nokia, tablet},
	issn = {978-0-387-72485-0},
	doi = {http://dx.doi.org/10.1007/978-0-387-72486-7_7},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Experiences\%20on\%20Product\%20Development.pdf},
	author = {Jaaksi, Ari}
}
@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 {1015,
	title = {Mining Eclipse Developer Contributions via Author-Topic Models},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {30 - 30},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {We present the results of applying statistical author-topic models to a subset of the Eclipse 3.0 source code consisting of 2,119 source files and 700,000 lines of code from 59 developers. This technique provides an intuitive and automated framework with which to mine developer contributions and competencies from a given code base while simultaneously extracting software function in the form of topics. In addition to serving as a convenient summary for program function and developer activities, our study shows that topic models provide a meaningful, effective, and statistical basis for developer similarity analysis.},
	keywords = {contributions, developers, eclipse, expertise, mining challenge, msr challenge, source code, topics},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.20},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300030.pdf},
	author = {Linstead, Erik and Rigor, Paul and Bajracharya, Sushil and Lopes, Cristina and Baldi, Pierre}
}
@conference {995,
	title = {Open Borders? Immigration in Open Source Projects},
	booktitle = {Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {6 - 6},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Open source software is built by teams of volunteers. Each project has a core team of developers, who have the authority to commit changes to the repository; this team is the elite, committed foundation of the project, selected through a meritocratic process from a larger number of people who participate on the mailing list. Most projects carefully regulate admission of outsiders to full developer privileges; some projects even have formal descriptions of this process. Understanding the factors that influence the "who, how and when" of this process is critical, both for the sustainability of FLOSS projects, and for outside stakeholders who want to gain entry and succeed. In this paper we mount a quantitative case study of the process by which people join FLOSS projects, using data mined from the Apache web server, Postgres, and Python. We develop a theory of open source project joining, and evaluate this theory based on our data.},
	keywords = {apache, core, joining, postgresql, python, team},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.23},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300006.pdf},
	author = {Christian Bird and Gourley, Alex and Devanbu, Prem and Swaminathan, Anand and Hsu, Greta}
}
@conference {994,
	title = {Recommending Emergent Teams},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {5 - 5},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {To build successful complex software systems, developers must collaborate with each other to solve issues. To facilitate this collaboration, specialized tools, such as chat and screen sharing, are being integrated into development environments. Currently, these tools require a developer to maintain a list of other developers with whom they may wish to communicate and to determine who within this list has expertise for a specific situation. For large, dynamic projects, like several successful open-source projects, these requirements place an unreasonable burden on the developer. In this paper, we show how the structure of a team emerges from how developers change software artifacts. We introduce the Emergent Expertise Locator (EEL) that uses emergent team information to propose experts to a developer within their development environment as the developer works. We found that EEL produces, on average, results with higher precision and higher recall than an existing heuristic for expertise recommendation.},
	keywords = {bugzilla, developers, eclipse, evolution, expertise, Firefox, teams},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.27},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300005.pdf},
	author = {Minto, Shawn and Murphy, Gail C.}
}
@article {flosswp405,
	title = {Self-organization of teams for free/libre open source software development},
	journal = {Information and Software Technology Journal},
	volume = {49},
	number = {564-575},
	year = {2007},
	note = {"First, the data from these projects that we needed for analysis had to be publicly available (ruling out projects that limit access to their email lists or trackers). Second, we chose the projects that had more than 7 members"..."projects that have attracted numerous developers beyond the initial project founders, are continuing to release software, have numerous downloads and have an active user community that provides feedback"
"3 FLOSS projects were selected for analysis, namely Gaim, eGroupWare and Compiere ERP."

all had sourceforge hosting

Data: "The primary data used for our study were interactions on the main developer communication forum, either a developer mailing list or web-based discussion forum."

Analysis: "For this project, we inductively content-analyzed developer email interactions to identify the task assignment mechanisms used in the process. We coded each instance of task assignment identified on three dimensions: who assigned the task, to whom, and how"
},
	abstract = {This paper provides empirical evidence about how free/libre open source software development teams self-organize their work. Following a case study methodology, we examined developer interaction data from three active and successful FLOSS projects using qualitative research methods, specifically inductive content analysis, to identify the task-assignment mechanisms used by the participants. We found that "self-assignment" was the most common mechanism across three FLOSS projects. This mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research.},
	keywords = {case study, compiere, coordination, DESIGN, distributed teams, egroupware, email, email archives, forum, free/libre open source software development, gaim, INTERNET, mailing list, metadata, qualitative research methods, self-organizing teams, sourceforge, SYSTEMS, task assignment, WORK},
	attachments = {https://flosshub.org/sites/flosshub.org/files/task_assignment_final.pdf},
	author = {Kevin Crowston and Li, Qing and Kangning Wei and Eseryel, U. Yeliz and Howison, James}
}
@conference {993,
	title = {Spam Filter Based Approach for Finding Fault-Prone Software Modules},
	booktitle = {Fourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {4 - 4},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Because of the increase of needs for spam e-mail detection, the spam filtering technique has been improved as a convenient and effective technique for text mining. We propose a novel approach to detect fault-prone modules in a way that the source code modules are considered as text files and are applied to the spam filter directly. In order to show the applicability of our approach, we conducted experimental applications using source code repositories of Java based open source developments. The result of experiments shows that our approach can classify more than 75\% of software modules correctly.},
	keywords = {argouml, bug reports, classification, eclipse, java, modules, scm, spam, text mining},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.29},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300004.pdf},
	author = {Mizuno, Osamu and Ikami, Shiro and Nakaichi, Shuya and Kikuno, Tohru}
}
@conference {998,
	title = {Visual Data Mining in Software Archives to Detect How Developers Work Together},
	booktitle = {Fourth International Workshop on Mining Software RepositoriesFourth International Workshop on Mining Software Repositories (MSR{\textquoteright}07:ICSE Workshops 2007)},
	year = {2007},
	pages = {9 - 9},
	publisher = {IEEE},
	organization = {IEEE},
	address = {Minneapolis, MN, USA},
	abstract = {Analyzing the check-in information of open source software projects which use a version control system such as CVS or SUBVERSION can yield interesting and important insights into the programming behavior of developers. As in every major project tasks are assigned to many developers, the development must be coordinated between these programmers.

This paper describes three visualization techniques that help to examine how programmers work together, e.g. if they work as a team or if they develop their part of the software separate from each other. Furthermore, phases of stagnation in the lifetime of a project can be uncovered and thus, possible problems are revealed.

To demonstrate the usefulness of these visualization techniques we performed case studies on two open source projects. In these studies interesting patterns of developers? behavior, e.g. the specialization on a certain module can be observed. Moreover, modules that have been changed by many developers can be identified as well as such ones that have been altered by only one programmer.},
	keywords = {change, coordination, cvs, developers, junit, modules, scm, source code, svn, teams, tomcat, visualization},
	isbn = {0-7695-2950-X},
	doi = {10.1109/MSR.2007.34},
	attachments = {https://flosshub.org/sites/flosshub.org/files/28300009.pdf},
	author = {Weissgerber, Peter and Pohl, Mathias and Burch, Michael}
}
@article {90,
	title = {Core and periphery in Free/Libre and Open Source software team communications},
	journal = {Proceedings of the 39th Annual Hawaii International Conference on System Sciences-Volume 06},
	year = {2006},
	abstract = {The concept of the core group of developers is important and often discussed in empirical studies of FLOSS projects. This paper examines the question, "how does one empirically distinguish the core?" Being able to identify the core members of a FLOSS development project is important because many of the processes necessary for successful projects likely involve core members differently than peripheral members, so analyses that mix the two groups will likely yield invalid results. 

We compare 3 analysis approaches to identify the core: the named list of developers, a Bradford{\textquoteright}s law analysis that takes as the core the most frequent contributors and a social network analysis of the interaction pattern that identifies the core in a core-and-periphery structure. We apply these measures to the interactions around bug fixing for 116 SourceForge projects. The 3 techniques identify different individuals as core members; examination of which individuals are identified leads to suggestions for refining the measures. All 3 measures though suggest that the core of FLOSS projects is a small fraction of the total number of contributors.},
	keywords = {bug fixing, contributions, contributors, core, developers, social network analysis, sourceforge, team},
	author = {Kevin Crowston and Kangning Wei and Li, Qing and Howison, James}
}
@conference {Sager:2006:DSJ:1137983.1138000,
	title = {Detecting similar Java classes using tree algorithms},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {65{\textendash}71},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Similarity analysis of source code is helpful during development to provide, for instance, better support for code reuse. Consider a development environment that analyzes code while typing and that suggests similar code examples or existing implementations from a source code repository. Mining software repositories by means of similarity measures enables and enforces reusing existing code and reduces the developing effort needed by creating a shared knowledge base of code fragments. In information retrieval similarity measures are often used to find documents similar to a given query document. This paper extends this idea to source code repositories. It introduces our approach to detect similar Java classes in software projects using tree similarity algorithms. We show how our approach allows to find similar Java classes based on an evaluation of three tree-based similarity measures in the context of five user-defined test cases as well as a preliminary software evolution analysis of a medium-sized Java project. Initial results of our technique indicate that it (1) is indeed useful to identify similar Java classes, (2)successfully identifies the ex ante and ex post versions of refactored classes, and (3) provides some interesting insights into within-version and between-version dependencies of classes within a Java project.},
	keywords = {change analysis, clones, coogle, eclipse, famix, java, similarity, software evolution, software repositories, source code, tree similarity measures},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138000},
	url = {http://doi.acm.org/10.1145/1137983.1138000},
	attachments = {https://flosshub.org/sites/flosshub.org/files/65Detecting.pdf},
	author = {Sager, Tobias and Bernstein, Abraham and Pinzger, Martin and Kiefer, Christoph}
}
@conference {D{\textquoteright}Ambros:2006:ERV:1137983.1137992,
	title = {The evolution radar: visualizing integrated logical coupling information},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {26{\textendash}32},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In software evolution research logical coupling has extensively been used to recover the hidden dependencies between source code artifacts. They would otherwise go lost because of the file-based nature of current versioning systems. Previous research has dealt with low-level couplings between files, leading to an explosion of data to be analyzed, or has abstracted the logical couplings to module level, leading to a loss of detailed information. In this paper we propose a visualization-based approach which integrates both file-level and module-level logical coupling information. This not only facilitates an in-depth analysis of the logical couplings at all granularity levels, it also leads to a precise characterization of the system modules in terms of their logical coupling dependencies.},
	keywords = {change management, cvs, evolution, logical coupling, mozilla, scm, source code, thunderbird, tinderbox, visualization},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1137992},
	url = {http://doi.acm.org/10.1145/1137983.1137992},
	attachments = {https://flosshub.org/sites/flosshub.org/files/26TheEvolutionRadar.pdf},
	author = {D{\textquoteright}Ambros, Marco and Lanza, Michele and Lungu, Mircea}
}
@conference {Robles:2006:GLD:1137983.1138017,
	title = {Geographic location of developers at SourceForge},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {144{\textendash}150},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {The development of libre (free/open source) software is usually performed by geographically distributed teams. Participation in most cases is voluntary, sometimes sporadic, and often not framed by a pre-defined management structure. This means that anybody can contribute, and in principle no national origin has advantages over others, except for the differences in availability and quality of Internet connections and language. However, differences in participation across regions do exist, although there are little studies about them. In this paper we present some data which can be the basis for some of those studies. We have taken the database of users registered at SourceForge, the largest libre software development web-based platform, and have inferred their geographical locations. For this, we have applied several techniques and heuristics on the available data (mainly e-mail addresses and time zones), which are presented and discussed in detail. The results show a snapshot of the regional distribution of SourceForge users, which may be a good proxy of the actual distribution of libre software developers. In addition, the methodology may be of interest for similar studies in other domains, when the available data is similar (as is the case of mailing lists related to software projects).},
	keywords = {distributed, email, email address, free software, geographical location, geography, libre software, mining software repositories, open source software, sourceforge, timezone},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138017},
	url = {http://doi.acm.org/10.1145/1137983.1138017},
	attachments = {https://flosshub.org/sites/flosshub.org/files/144GeographicLocation.pdf},
	author = {Gregorio Robles and Jesus M. Gonzalez-Barahona}
}
@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}
}
@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 {flosswp113,
	title = {The Impact of Ideology on Effectiveness in Open Source Software Development Teams},
	journal = {MIS Quarterly},
	volume = {30},
	number = {2},
	year = {2006},
	note = {"...we collected data related to OSS projects hosted on Sourceforge (www.sourceforge.net)."
"Data was collected using two surveys and from the Sourceforge website."
},
	month = {2006},
	pages = {291-314},
	abstract = {The emerging work on understanding open source software has argued for the importance of understanding what leads to effectiveness in OSS development teams and has pointed to the importance of ideology. This paper develops a framework of the OSS ideology (including specific norms, beliefs, and values) and a theoretical model to show how adherence to components of the ideology impact effectiveness in OSS teams. The model is based on the idea that ideology provides clan control, which is important in OSS development settings because OSS teams generally lack formal behavioral and outcome controls. The paper hypothesizes both direct effects of ideology on OSS team effectiveness and indirect effects via influences on affective trust, cognitive trust, and communication quality. Hypotheses are tested using survey and objective data on OSS projects. Four effectiveness measures are used to capture unique aspects of effectiveness in OSS including both the extent to which a team attracts input from the community and the team{\textquoteright}s success in accomplishing project outcomes. Results support the main thesis that OSS team members{\textquoteright} adherence to the tenets of the OSS community ideology enhances OSS team effectiveness. The study uncovers several differences in the importance of OSS norms, beliefs, and values to different kinds of OSS team effectiveness and discusses implications for theory and practice.},
	keywords = {bug fixing, bug reports, bug tracking, communication, COMMUNITY, effectiveness, feature requests, ideology, metadata, sourceforge, Survey, team effort, team size, trust},
	attachments = {https://flosshub.org/sites/flosshub.org/files/stewartgosain2.pdf},
	author = {Stewart, K. and Gosain, S.}
}
@article {Crowston:2006,
	title = {Information systems success in Free and Open Source Software development: Theory and measures},
	journal = {Software Process{\textendash}Improvement and Practice},
	volume = {11},
	number = {2},
	year = {2006},
	note = {"we continue our examination of success measures using data from Sourceforge..."
"e chose the number of developers (assessed from the records of the project and from bug fixing logs), bug-fixing time, and popularity (assessed from the number of downloads and viewings of project Web pages, and inclusion in distributions). These measures were chosen because they span the reconsidered FLOSS development process discussed above, including inputs (number of developers), process (speed of bug fixing) and output (popularity)."},
	pages = {123{\textendash}148},
	abstract = {Information systems success is one of the most widely used dependent variables in information systems (IS) research, but research on Free/Libre and Open Source software (FLOSS) often fails to appropriately conceptualize this important concept. In this paper, we reconsider what success means within a FLOSS context. We first review existing models of IS success and success variables used in FLOSS research and assess them for their usefulness, practicality and fit to the FLOSS context. Then, drawing on a theoretical model of group effectiveness in the FLOSS development process, as well as an online discussion group with developers, we present additional concepts that are central to an appropriate understanding of success for FLOSS. In order to examine the practicality and validity of this conceptual scheme, the second half of our paper presents an empirical study that demonstrates its operationalization of the chosen measures and assesses their internal validity. We use data from SourceForge to measure the project{\textquoteright}s effectiveness in team building, the speed of the project at responding to bug reports and the project{\textquoteright}s popularity. We conclude by discussing the implications of this study for our proposed extension of IS success in the context of FLOSS development and highlight future directions for research.},
	keywords = {bug fixing, developers, downloads, FLOSS, flossmole, page views, popularity, project success, size, sourceforge, success, team size},
	doi = {10.1002/spip.259},
	attachments = {https://flosshub.org/sites/flosshub.org/files/CrowstonHowisonAnnabi2006.pdf},
	author = {Kevin Crowston and Howison, James and Hala Annabi}
}
@article {1232,
	title = {Integration of libre software applications to create a collaborative work platform for researchers at GET},
	journal = {International Journal of Information Technology and Web Engineering},
	volume = {1},
	number = {3},
	year = {2006},
	month = {07/2006},
	pages = {1-16},
	publisher = {IGI Global},
	abstract = {Libre software provides powerful applications ready to be integrated for the build-up of platforms for internal use in organizations. We describe the architecture of the collaborative work platform which we have integrated, designed for researchers at GET. We present the elements we have learned during this project in particular with respect to contribution to external libre projects, in order to better ensure the maintainability of the internal applications, and to phpGroupware as a framework for specific applications development.},
	keywords = {collaborative work environment, contribution, free software, groupware, in-house applications, libre software, open source software, OpenLDAP, phpGroupware, PicoLibre, ProGET, Sympa, TWiki, WebDAV, wiki},
	author = {Olivier Berger and Christian Bac and Benoit Hamet}
}
@conference {Voinea:2006:MSR:1137983.1138024,
	title = {Mining software repositories with CVSgrab},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {167{\textendash}168},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	keywords = {argouml, cvs, cvsgrab, evolution, mining challenge, msr challenge, postgresql, software visualization, source code, team, visualization},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138024},
	url = {http://doi.acm.org/10.1145/1137983.1138024},
	attachments = {https://flosshub.org/sites/flosshub.org/files/167MiningSoftware.pdf},
	author = {Voinea, Lucian and Telea, Alexandru}
}
@article {1088,
	title = {Self-Organization Patterns in Wasp and Open Source Communities},
	journal = {IEEE Intelligent Systems},
	volume = {21},
	year = {2006},
	note = {"To investigate such claims, we studied an OSS community{\textquoteright}s social network from a dataset describing the email activity of 120 different software teams"
"Our test data originated from Sourceforge (http://sourceforge.net), a large open source project repository, and included communi- ties ranging from very small networks with one or two members to large networks with thousands of members."
"we limited our consideration to email traffic associated with bug fixes and bug reporting. As other researchers have shown[5] this email subset allows an effective reconstruction of the software community{\textquoteright}s social network."
"We thank Kevin Crowston and James Howison for making their software data publicly available."},
	month = {03/2006},
	pages = {36 - 40},
	abstract = {In this paper, we conducted a comparative study of how social organization takes place in a wasp colony and OSS developer communities. Both these systems display similar global organization patterns, such as hierarchies and clear labor divisions. As our analysis shows, both systems also define interacting agent networks with similar common features that reflect limited information sharing among agents. As far as we know, this is the first research study analyzing the patterns and functional significance of these systems{\textquoteright} weighted-interaction networks. By illuminating the extent to which self-organization is responsible for patterns such as hierarchical structure, we can gain insight into the origins of organization in OSS communities.},
	keywords = {agents, decentralization, developers, email, email archives, flossmole, hierarchy, labor division, organization, self-organizing teams, social network analysis, social networks, sourceforge, teams, wasps},
	issn = {1541-1672},
	doi = {10.1109/MIS.2006.34},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.95.5574\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/valverde.pdf},
	author = {Valverde, S. and Theraulaz, G. and Gautrais, J. and Fourcassie, V. and Sole, R.V.}
}
@conference {German:2006:SCP:1137983.1138022,
	title = {A study of the contributors of PostgreSQL},
	booktitle = {Proceedings of the 2006 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}06},
	year = {2006},
	pages = {163{\textendash}164},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {This report describes some characteristics of the development team of PostgreSQL that were uncovered by analyzing the history of its software artifacts as recorded by the project{\textquoteright}s CVS repository.},
	keywords = {contributions, contributors, cvs, developers, mining challenge, mining software repositories, msr challenge, patches, postgresql, revision history, roles, software evolution, source code, team},
	isbn = {1-59593-397-2},
	doi = {http://doi.acm.org/10.1145/1137983.1138022},
	url = {http://doi.acm.org/10.1145/1137983.1138022},
	attachments = {https://flosshub.org/sites/flosshub.org/files/163AStudyOf.pdf},
	author = {Daniel M. German}
}
@conference {Gorg:2005:EDR:1083142.1083148,
	title = {Error detection by refactoring reconstruction},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {29-33},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {In many cases it is not sufficient to perform a refactoring only at one location of a software project. For example, refactorings may have to be performed consistently to several classes in the inheritance hierarchy, e.g. subclasses or implementing classes, to preserve equal behavior.In this paper we show how to detect incomplete refactorings - which can cause long standing bugs because some of them do not cause compiler errors - by analyzing software archives. To this end we reconstruct the class inheritance hierarchies, as well as refactorings on the level of methods. Then, we relate these refactorings to the corresponding hierarchy in order to find missing refactorings and thus, errors and inconsistencies that have been introduced in a software project at some point of the history.Finally. we demonstrate our approach by case studies on two open source projects.},
	keywords = {bugs, class, inheritance, jedit, refactoring, tomcat},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083148},
	url = {http://doi.acm.org/10.1145/1082983.1083148},
	attachments = {https://flosshub.org/sites/flosshub.org/files/29ErrorDetection.pdf},
	author = {G{\"o}rg, Carsten and Wei{\ss}gerber, Peter}
}
@conference {781,
	title = {Idealism and Commercialism {\textendash} Developing Free/Libre and Open Source Software in Private Businesses},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {301-302},
	abstract = {This paper presents a PhD research project undertaken as part of a larger project aimed at paying sociological attention to different forms of distribution of knowledge, including program code. We want to investigate empirically how the commons knows as free/open source software is actually made. In my PhD project I study the use and development of FLOSS in private businesses, focusing on professional developers working in private businesses and at the same time participating in the FLOSS community. The theoretical starting point is theories of power, dominance and legitimacy by Max Weber and Pierre Bourdieu.},
	keywords = {dominance, FLOSS, FLOSS community, free/libre, legitimacy, linux, open source, Private Businesses, social organisation, theories of power},
	url = {http://pascal.case.unibz.it/handle/2038/970},
	author = {Lundestad, Christian V.}
}
@conference {777,
	title = {Live! I-Learn @ Home},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {294-295},
	abstract = {In this paper we present a live CD based on GNU/Linux (Knoppix), customized in order to supply a complete working and studying environment for the students of the Corso di Studi in Informatica. In particular, it supplies the Moodle course management system for e-learning complete of the courses of the first year. The aim is to enable the use of such resources off-line and without requiring special skills that will be achieved by studying but that newbies do not have.},
	keywords = {e-learning, environment, GNU/Linux, java, open source, technology},
	url = {http://pascal.case.unibz.it/handle/2038/977},
	author = {Baldoni, Matteo and Baroglio, Cristina and Roversi, Luca and Grandi, Claudio}
}
@conference {Fischer:2005:MED:1083142.1083145,
	title = {Mining evolution data of a product family},
	booktitle = {Proceedings of the 2005 international workshop on Mining software repositories},
	series = {MSR {\textquoteright}05},
	year = {2005},
	pages = {12-16},
	publisher = {ACM},
	organization = {ACM},
	address = {New York, NY, USA},
	abstract = {Diversification of software assets through changing requirements impose a constant challenge on the developers and maintainers of large software systems. Recent research has addressed the mining for data in software repositories of single products ranging from fine- to coarse grained analyses. But so far, little attention has been payed to mining data about the evolution of product families. In this work, we study the evolution and commonalities of three variants of the BSD (Berkeley Software Distribution), a large open source operating system. The research questions we tackle are concerned with how to generate high level views of the system discovering and indicating evolutionary highlights. To process the large amount of data, we extended our previously developed approach for storing release history information to support the analysis of product families. In a case study we apply our approach on data from three different code repositories representing about 8.5GB of data and 10 years of active development.},
	keywords = {bsd, change analysis, change history, cvs, evolution, freebsd, netbsd, openbsd, release history, source code, text mining},
	isbn = {1-59593-123-6},
	doi = {http://doi.acm.org/10.1145/1082983.1083145},
	url = {http://doi.acm.org/10.1145/1082983.1083145},
	attachments = {https://flosshub.org/sites/flosshub.org/files/12MiningEvolution.pdf},
	author = {Fischer, Michael and Oberleitner, Johann and Ratzinger, Jacek and Gall, Harald}
}
@conference {772,
	title = {OTRS: un sistema a ticket per la gestione dell{\textquoteright}help desk},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {281},
	abstract = {Descriviamo l{\textquoteright}esperienza di utilizzo di un software a codice sorgente aperto per la gestione a ticket dell{\textquoteright}help desk informatico del D.I.S.I. (Dipartimento di Informatica e Scienze delll{\textquoteright}Informazione) dell{\textquoteright}Universit{\`a} degli Studi di Genova.},
	keywords = {help desk, open source, ticketing system, trouble ticket},
	url = {http://pascal.case.unibz.it/handle/2038/1423},
	author = {Bencetti, Stefano and Verduci, Gianni}
}
@article {springerlink:10.1007/s10606-005-9000-1,
	title = {Socialization in an Open Source Software Community: A Socio-Technical Analysis},
	journal = {Computer Supported Cooperative Work (CSCW)},
	volume = {14},
	year = {2005},
	note = {"I present the results of my analyses of participation patterns in a particular OSS project, used as a case study: Python. More precisely, I use the Open Source Project Browser to qualitatively track and analyze the trajectories of several project members who evolved (or not) into full-fledged participants. This allows me to later discuss how socialization proceeds in an OSS community such as Python"

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

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

http://www2.parc.com/csl/members/nicolas/documents/JCSCW-OSS.pdf},
	pages = {323-368},
	publisher = {Springer Netherlands},
	abstract = {Open Source Software (OSS) development is often characterized as a fundamentally new way to develop software. Past analyses and discussions, however, have treated OSS projects and their organization mostly as a static phenomenon. Consequently, we do not know how these communities of software developers are sustained and reproduced over time through the progressive integration of new members. To shed light on this issue I report on my analyses of socialization in a particular OSS community. In particular, I document the relationships OSS newcomers develop over time with both the social and material aspects of a project. To do so, I combine two mutually informing activities: ethnography and the use of software specially designed to visualize and explore the interacting networks of human and material resources incorporated in the email and code databases of OSS. Socialization in this community is analyzed from two perspectives: as an individual learning process and as a political process. From these analyses it appears that successful participants progressively construct identities as software craftsmen, and that this process is punctuated by specific rites of passage. Successful participants also understand the political nature of software development and progressively enroll a network of human and material allies to support their efforts. I conclude by discussing how these results could inform the design of software to support socialization in OSS projects, as well as practical implications for the future of these projects.},
	keywords = {cvs, developers, email, email archive, mailing list, open source project browser, participation, python, scm, source code, team, tools},
	issn = {0925-9724},
	url = {http://dx.doi.org/10.1007/s10606-005-9000-1},
	author = {DUCHENEAUT, NICOLAS}
}
@conference {899,
	title = {Stopping spyware at the gate: a user study of privacy, notice and spyware},
	booktitle = {2005 Symposium on Usable Privacy and Security},
	year = {2005},
	month = {07/2005},
	pages = {43-52},
	publisher = {Association for Computing Machinery},
	organization = {Association for Computing Machinery},
	address = {Pittsburgh, PA},
	keywords = {agreement,, and, Aspects,, Design,, end, EULA,, Experimentation,, Factors,, Human, Legal, license, notice,, of, privacy,, security, service,, spyware,, terms, ToS,, usability,, user},
	isbn = {1-59593-178-3 },
	author = {N. Good and Dhamija, R. and J. Grossklags and D. Thaw and Aronowitz, S. and D. Mulligan and J. Konstan}
}
@conference {799,
	title = {What is the significance of Open Source Software for the education and training community?},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {353-358},
	abstract = {There is growing interest in the education community in the development and use of Open Source Software. This paper explains the ideas behind OSS and how what its significance is for education. It examines regional and national initiatives to promote the use of OSS. The paper considers the advantages of OSS and potential problems. It goes on to look at the idea of open content and the sharing of learning content, and provides short case studies. The paper concludes that the major significance of OSS and open content is in the new social relations engendered and in fostering innovation in e-learning, both in application development and new pedagogies.},
	keywords = {economic issues, education, open source, pedagocic impact, training},
	url = {http://pascal.case.unibz.it/handle/2038/1563},
	author = {Attwell, Graham}
}
@article {capiluppi:23,
	title = {Improving comprehension and cooperation through code structure},
	journal = {IEE Seminar Digests},
	volume = {2004},
	number = {908},
	year = {2004},
	note = {"In this study we measured source code size in three different forms (LOCs, SLOCs, and Kbs of code)."

"Pilot Project: The ARLA System"
},
	pages = {23-28},
	publisher = {IEE},
	abstract = {Defining a relationship between a software system{\textquoteright}s architecture and the process{\textquoteright} efforts is one of the most fascinating questions of software engineering. Apparently, when a system{\textquoteright}s architecture is complex, the process to improve and evolve it will be more difficult. We try to tackle this question from a different point of view: given an open source system, in all the phases of its evolution, we focus on both the aspects of software developers, and the obtained software product. More we observe one of the possible architectures of this system, based on the tree structure derived from source components. First conclusions show that some patterns of tree evolution are recognizable: some branches may appear more promising than other, and are extensively evolved, while other remains in the same status for all the life cycle. More, when the tree structure reaches some status, the process of joining as a core developer seems to forestall. },
	keywords = {arla, code structure, contributors, developers, open source system, scm, software development, software engineering, software process, software product, software system architecture, source code, source components, tree evolution, tree structure},
	doi = {10.1049/ic:20040260},
	url = {http://link.aip.org/link/abstract/IEESEM/v2004/i908/p23/s1},
	attachments = {https://flosshub.org/sites/flosshub.org/files/capiluppi2004.pdf},
	author = {A. Capiluppi}
}
@article {1253,
	title = {The many meanings of open source},
	journal = {IEEE Software},
	volume = {21},
	year = {2004},
	note = {"We determined a set of characteristics that are almost always present and others that vary among open source projects, and this serves as the core of this work"
"Section 3 describes some open source characteristics that can be used in determining whether a project is or not open source"},
	month = {01/2004},
	pages = {34 - 40},
	abstract = {The term Open Source is widely applied to describe some software development methodologies. This paper does not provide a judgment on the open source approach, but exposes the fact that simply stating that a project is open source does not provide a precise description of the approach used to support the project. By taking a multi- disciplinary point of view, we propose a collection of characteristics that are common, as well as some that vary among open source projects. The set of open source characteristics we found can be used as a tick-list both for analysing and for setting up open source projects. Our tick-list also provides a starting point for understanding the many meanings of the term open source.},
	keywords = {classification, projects, taxonomy},
	issn = {0740-7459},
	doi = {10.1109/MS.2004.1259206},
	attachments = {https://flosshub.org/sites/flosshub.org/files/gacek.pdf},
	author = {Gacek, C. and Arief, B.}
}
@proceedings {124,
	title = {Membership dynamics and network stability in the open-source community: the ising perspective},
	year = {2004},
	note = {"simulations with the empirical network data that were collected from two actual OSS communities, Linux and Hypermail."

"we initially downloaded nearly 100,000 archived (between 1997 and 2003) LINUX Kernel and Hypermail newsgroup messages posted in a UNIX mailbox format"

"Specific information was obtained regarding the characteristics of these two OSS communities, including the size, the number of average connections per participant, and the hierarchy of each community."},
	abstract = {In this paper, we address the following two questions: (1)How does a participant{\textquoteright}s membership decision affect the others (neighbors) with whom he has collaborated over an extended period of time in an open source software (OSS) network? (2) To what extent do network characteristics (i.e, size and connectivity) mediate the impact of external factors on the OSS participants{\textquoteright} dynamic membership decisions and hence the stability of the network? From the Ising perspective, we present fresh theoretical insight into the dynamic and reciprocal membership relations between OSS participants. We also performed simulations based on empirical data that were collected from two actual OSS communities. Some of the key findings include that (1) membership herding is highly present when the external force is weak, but decreases significantly when the force increases, (2) the propensity for membership herding is most likely to be seen in a large network with a random connectivity, and (3) for large networks, at low external force a random connectivity will perform better than a scale-free counterpart in terms of the network strength. However, as the temperature (external force) increases, the reverse phenomenon is observed. In addition, the scale-free connectivity appears to be less volatile than with the random connectivity in response to the increase in the temperature. We conclude with several implications that may be of significance to OSS stakeholders.},
	keywords = {email, email archive, hypermail, linux, mailing list, membership, membership herding, newsgroup, open source, participants, social network analysis, stakeholders, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/OhJeon.pdf},
	author = {Oh, Wonseok and Jeon, Sangyong}
}
@conference {1050,
	title = {Mining version control systems for FACs (frequently applied changes)},
	booktitle = {International Workshop on Mining Software Repositories (MSR 2004)},
	volume = {2004},
	year = {2004},
	pages = {48 - 52},
	publisher = {IEE},
	organization = {IEE},
	address = {Edinburgh, Scotland, UK},
	abstract = {Today, programmers are forced to maintain a software system based on their gut feeling and experience. This paper makes an attempt to turn the software maintenance craft into a more disciplined activity, by mining for frequently applied changes in a version control system. Next to some initial results, we show how this technique allows to recover and study successful maintenance strategies, adopted for the redesign of long{\textendash}lived systems.},
	keywords = {ccfinder, change analysis, change history, clone, clone detection, cvs, maintenance, tomcat, version control},
	doi = {10.1049/ic:20040475},
	attachments = {https://flosshub.org/sites/flosshub.org/files/48MiningVersion.pdf},
	author = {Van Rysselberghe, F. and Demeyer, S}
}
@article {1077,
	title = {Profiling an Open Source Project Ecology and Its Programmers},
	journal = {Electronic Markets},
	volume = {14},
	year = {2004},
	month = {6/2004},
	pages = {77 - 88},
	abstract = {While many successful and well-known open source projects produce output of high quality, a general assessment of this development paradigm is still missing. In this paper, an online community of both small and large, successful and failed projects and their programmers is analysed mainly using the version-control data of each project, also according to their productivity and estimation of expended effort. As the results show, there are indeed significant differences between this cooperative development model and the commercial organization of work in the areas explored. Both open source software projects in their size and their programmers{\textquoteright} effort differ significantly, and the evolution of projects{\textquoteright} size over time seems in part to contradict the laws of software evolution proposed for commercial systems. Both the inequality of effort distribution between programmers and an increasing number of developers in a project do not lead to a decrease in productivity, opposing Brooks{\textquoteright}s Law. Effort estimation based on the COCOMO model for commercial organizations shows a large amount of effort expended for the projects, while a more general Norden-Rayleigh modeling shows a distinctly smaller expenditure. This proposes that either a highly efficient development is achieved by this self-organizing cooperative and highly decentralized form of work, or that the participation of users besides programming tasks is enormous and constitutes an economic factor of large proportions. },
	keywords = {affiliation network, brooks law, cocomo, effort estimation, evolution, productivity, project success, scm, size, time, version control},
	issn = {1422-8890},
	doi = {10.1080/10196780410001675031},
	author = {Koch, Stefan}
}
@conference {flosswp180,
	title = {Towards a Portfolio of FLOSS project Success Measures},
	booktitle = {Workshop on Open Source Software Engineering, International Conference on Software Engineering},
	year = {2004},
	month = {May},
	abstract = {Project success is one of the most widely used dependent variables in information systems research. However, conventional measures of project success are difficult to apply to Free/Libre Open Source Software projects. In this paper, we present an analysis of four measures of success applied to SourceForge projects: number of members of the extended development community, project activity, bug fixing time and number of downloads. We argue that these four measures provide different insights into the collaboration and control mechanisms of the projects.},
	keywords = {bug fixing, developers, downloads, project success, sourceforge, team, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/crowston04towards.pdf},
	author = {Kevin Crowston and Hala Annabi and Howison, James and Chengetai Masango}
}
@article {flosswp85,
	title = {An Introduction to Open Source Communities},
	year = {2003},
	month = {04/2003},
	institution = {Blue Oxen Associates},
	abstract = {This report describes what open source communities are and how they work. It cites relevant research and presents original case studies of two open source projects: TouchGraph and SquirrelMail. It then identifies patterns of collaboration shared by these projects, and describes how these patterns might apply to other types of communities. Finally, it reviews what is still not well understood about open source communities, and proposes several paths for further research.},
	keywords = {free software foundation directory, freshmeat, fsf, sourceforge, squirrelmail, touchgraph},
	attachments = {https://flosshub.org/sites/flosshub.org/files/blueoxen.pdf},
	author = {Eugene Eric Kim}
}
@article {123,
	title = {Open source software development and Lotka{\textquoteright}s Law: Bibliometric patterns in programming},
	journal = {Journal of the American Society for Information Science and Technology},
	volume = {54},
	number = {2},
	year = {2003},
	note = {"Two lead- ing metadata repositories are the Linux Software Map (LSM) and Sourceforge, both of which were used for this research."
"For this article, we examined data listing the number of registered developers for each software project hosted by Sourceforge."
"The data we obtained from the LSM collection were taken mainly from the Author: field of LSM records. The Author: field in LSM records gives us the ability to track the author of record for a software package. LSM metadata also include a list of maintainers, primary software distribution sites, date of update and other items."
"The data we obtained from Sourceforge consist of a list of developer ID numbers, followed by the number of projects on which the individual is listed as a developer, then the number of projects on which the individual is listed as an administrator. These data were provided for all 33,892 individuals registered to work on projects hosted by Sourceforge in July 2001."},
	pages = {169-178},
	abstract = {This research applies Lotka{\textquoteright}s Law to metadata on open source software development. Lotka{\textquoteright}s Law predicts the proportion of authors at different levels of productivity. Open source software development harnesses the creativity of thousands of programmers worldwide, is important to the progress of the Internet and many other computing environments, and yet has not been widely researched. We examine metadata from the Linux Software Map (LSM), which documents many open source projects, and Sourceforge, one of the largest resources for open source developers. Authoring patterns found are comparable to prior studies of Lotka{\textquoteright}s Law for scientific and scholarly publishing. Lotka{\textquoteright}s Law was found to be effective in understanding software development productivity patterns, and offer promise in predicting aggregate behavior of open source developers.},
	keywords = {developers, linux, linux software map, lsm, sourceforge, team size},
	doi = {10.1002/asi.10177},
	author = {Newby, G. B. and Greenberg, J. and Jones, P.}
}
@conference {1248,
	title = {Supporting Distributed and Decentralized Projects: Drawing Lessons from the Open Source Community},
	booktitle = {1st Workshop on Open Source in an Industrial Context},
	year = {2003},
	note = {"We begin the remainder of the paper with discussion of a survey of open source projects, showing similarities that have arisen in tool usage"},
	month = {10/2003},
	abstract = {Open source projects are typically organized in a distributed and decentralized manner. These factors strongly determine the processes followed and constrain the types of tools that can be utilized. This paper explores how distribution and decentralization have affected processes and tools in existing open source projects with the goals of summarizing the lessons learned and identifying opportunities for improving both. Issues considered include decision-making, accountability, communication, awareness, rationale, managing source code, testing, and release management.},
	keywords = {abiword, apache, debian, freebsd, kde, linux, mozilla, mysql, perl, PHP, postgresql, python, subversion, tomcat, tools},
	attachments = {https://flosshub.org/sites/flosshub.org/files/erenkrantz2003.pdf},
	author = {Erenkrantz, J. and Taylor, R.N.}
}
@conference {1160,
	title = {Adopting OSS Methods by Adopting OSS Tools},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {The open source movement has created and used a set of software engineering tools with features that fit the characteristics of open source development processes. To a large extent, the open source culture and methodology are conveyed to new developers via the toolset itself, and through the demonstrated usage of these tools on existing projects. The rapid and wide adoption of open source tools stands in stark contrast to the difficulties encountered in adopting traditional CASE tools. This paper explores the characteristics that make these tools adoptable and how adopting them may influence software development processes.},
	keywords = {ant, argouml, bugzilla, cactus, cvs, developers, eclipse, emacs, email, faq, junit, mailing lists, make, netbeans, package management, rpm, scarab, subversion, teams, tools, torque, WORK},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Robbins.pdf},
	author = {Robbins, Jason E.}
}
@conference {stewart2002an-explorat,
	title = {An Exploratory Study of Factors Influencing the Level of Vitality and Popularity of Open Source Projects},
	booktitle = {ICIS 2002. Proceedings of International Conference on Information Systems 2002},
	year = {2002},
	note = {"We are currently tracking publicly available data on 240 open source projects registered on the freshmeat Website." "First, we randomly selected a total of 120 projects from the utilities, software development, and games and entertainment areas. We then selected 120 projects from these forums that had been registered on the site during the two weeks prior to the start of our data collection effort."},
	month = {2002},
	pages = {1-5},
	abstract = {In this research, we ask the question: What differentiates successful from unsuccessful open source software projects? Using a sample of 240 open source projects, we examine how organizational sponsorship, target audience (developer versus end user), license choice, and development status interact over time to influence the extent to which open source software projects attract user attention and developer activity.},
	keywords = {activity, audience, developers, freshmeat, license analysis, licenses, organizational sponsorship, project success, roles, status, target audience, users},
	author = {Stewart, Katherine J. and Ammeter, Tony}
}
@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}
}
@conference {1162,
	title = {Is Open Source Software Development Faster, Better, and Cheaper than Software Engineering?},
	booktitle = {Proceedings of the 2nd ICSE Workshop on Open Source},
	year = {2002},
	abstract = {In this paper, I draw attention to the question of determining how open source software development may represent a significant alternative to modern software engineering techniques for developing large-scale software systems. OSSD often entails shorter time frames, producing higher quality systems, and incurring lower costs than may be realized through developing systems according SE techniques. Understanding why and how this may arise is the focus of this paper.},
	keywords = {argouml, quality, tigris},
	attachments = {https://flosshub.org/sites/flosshub.org/files/Scacchi_0.pdf},
	author = {Walt Scacchi}
}
@article {Hissam,
	title = {Trust and vulnerability in open source software},
	journal = {Software, {IEE} Proceedings -},
	volume = {149},
	number = {1},
	year = {2002},
	month = {02/2002},
	pages = {47{\textendash}51},
	chapter = {47},
	abstract = {Software plays an ever increasing role in the critical infrastructures that run our cities, manage our economies, and defend our nations. In 1999, the Presidents Information Technology Advisory Committee (PITAC) reported to the United States President the need for software components that are reliable, tested, modelled and secure supporting the development of predictably reliable and secure systems that underscore our critical infrastructures. Open source software (OSS) constitutes a viable source for software components. Some believe that OSS is more reliable and more secure than closed source software (CSS)-due to a phenomenon dubbed {\textquoteright}many eyeballs{\textquoteright}-but is this truly the case? Or does OSS give the cyber criminal an edge that he would likewise not have? We explore OSS from the perspective of the cyber criminal and discuss what the community of software developers and users alike can do to increase their trust in both open source software and closed source software},
	keywords = {closed source software, community of software developers, critical infrastructures, cyber criminal, open source software, PITAC, predictably reliable systems, predictably secure systems, software components, trust, users, vulnerability},
	issn = {1462-5970},
	doi = {10.1049/ip-sen:20020208},
	author = {Hissam, S. A. and Plakosh, D. and Weinstock, C.}
}
@conference {1138,
	title = {Creating a Free, Dependable Software Engineering Environment for Building Java Applications},
	booktitle = {1st Workshop on Open Source Software Engineering at ICSE 2001},
	year = {2001},
	abstract = {As open source software engineering becomes more prevalent, employing sound software engineering practices and the tools used to implement these practices becomes more important. This paper examines the current status of free software engineering tools. For each set of tools, we determined the important attributes that would best assist a developer in each stage of the waterfall model. We rated each tool based on predetermined attributes. We used the creation of a graphical user interface based email client in Java to assist in evaluating each tool. Our findings show that there is still a need for free tools to extract UML diagrams, test graphical user interfaces, make configuring Emacs easier, and profile Java applications. In other areas there are free tools that provide satisfactory functionality such as Concurrent Versions System (CVS), GVim, JUnit, JRefactory, GNU Make, Jakarta Ant, Javadoc, and Doc++.},
	keywords = {applications, cvs, Doc++, GNU Make, GVim, Jakarta Ant, java, Javadoc, jrefactory, junit, tools},
	attachments = {https://flosshub.org/sites/flosshub.org/files/bittman.pdf},
	author = {Bittman, M. and Roos, R. and Kapfhammer, G.M.}
}
@proceedings {140,
	title = {An exploratory study of ideology and trust in open source development groups},
	year = {2001},
	note = {"To do this, we scanned information in the public domain to develop a preliminary understanding of the context. We then identified 48 OS projects using www.sourceforge.net, an on-line open source meeting place that provides information on open source efforts and hosts code repositories. Projects were selected to represent a variety of types of software, licenses, and group sizes. We contacted administrators or project leaders and asked them to complete open-ended questionnaires regarding their experience and views on open source development."},
	abstract = {Open source (OS) software development has been the subject of heightened interest among organizational scholars because of the novel social coordination practices that signal a departure from traditional proprietary software development. We propose that trust among group members in open source development groups (OSDGs) plays a key role in facilitating their success. Trust is important in this context because of the risk of opportunistic behavior by other members who volunteers may not have met and may never expect to meet, as well as a lack of explicit market contracts or common organizational affiliation. The open source community is differentiated by a coherent ideology that emphasizes a distinct set of interrelated norms, beliefs, and values. These serve to create incentives for open source practices that eschew conventional transactional norms in favor of a gift culture and a focus on reputations. In this study, we primarily examine the role of the shared ideology in enabling the development of affective and cognitive trust in OSDGs. We further examine how this trust leads to desired outcomes - group efficacy and effectiveness. The study is based on exploratory interviews, examination of archival records and a preliminary survey to understand the specific conditions of open source efforts on which this work-in-progress report is based. This is being followed-up by empirical testing of our research model through a survey of a broad variety of OSDGs. This study would contribute to a clarification of the role of trust in enabling software groups to work effectively and help to understand the bases of trust in ideology-permeated groups.},
	keywords = {contributors, groups, ideology, license analysis, licenses, metadata, open source, sourceforge, Survey, team, team size, teams, trust, types},
	doi = {10.1.1.104.638},
	url = {http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.104.638\&rep=rep1\&type=pdf},
	attachments = {https://flosshub.org/sites/flosshub.org/files/stewartGosain2001.pdf},
	author = {Katherine Stewart and Gosain, S.}
}
@article {98,
	title = {Striking a balance between trust anti control in a virtual organization: a content analysis of open source software case studies},
	journal = {Information Systems Journal},
	volume = {11},
	number = {4},
	year = {2001},
	note = {"I employ secondary analysis of published case studies of OSS projects. I used several search methods to identify such case studies about OSS pro- jects. First, I searched the electronic archives of both ACM and IEEE, using terms such as {\textquoteleft}open source.{\textquoteright} "
"Secondly, I searched on Bell \& Howell/Proquest{\textquoteright}s ABI/Inform, a database of acade- mic and trade publications on business and management (including technology management). Thirdly, I reviewed the {\textquoteleft}position papers{\textquoteright} of the various authors who attended the 1st Work- shop on Open-Source Software Engineering (Feller et al., 2001) for relevant case studies. Fourthly, I searched on Harvard Publishing{\textquoteright}s websites, which contain case studies published"
"Finally, as I located case studies or other publi- cations about OSS projects, I followed references from them to identify other case studies. Although I found literally hundreds of publications about OSS development, there was a much smaller number of case studies"},
	pages = {277-304},
	abstract = {Many organization theorists have predicted the emergence of the networked or virtual firm as a model for the design of future organizations. Researchers have also emphasized the importance of trust as a necessary condition for ensuring the success of virtual organizations. This paper examines the open source software (OSS) {\textquoteright}movement{\textquoteright} as an example of a virtual organization and proposes a model that runs contrary to the belief that trust is critical for virtual organizations. Instead, I argue that various control mechanisms can ensure the effective performance of autonomous agents who participate in virtual organizations. Borrowing from the theory of the {\textquoteright}McDonaldization{\textquoteright} of society, I argue that, given a set of practices to ensure the control, efficiency, predictability and calculability of processes and outcomes in virtual organizations, effective performance may occur in the absence of trust. As support for my argument, I employ content analysis to examine a set of published case studies of OSS projects. My results show that, although that trust is rarely mentioned, ensuring control is an important criterion for effective performance within OSS projects. The case studies feature few references to other dimensions of {\textquoteright}McDonaldization{\textquoteright} (efficiency, predictability and calculability), however, and I conclude that the OSS movement relies on many other forms of social control and self-control, which are often unacknowledged in OSS projects. Through these implicit forms of control, OSS projects are able to secure the cooperation of the autonomous agents that participate in project teams. I conclude by extrapolating from these case studies to other virtual organizations.},
	keywords = {apache, case studies, Control, fetchmail, jun, linux, linux kernel, McDonaldization, mozilla, networked organization, perl, rationalization, trust, virtual organization},
	author = {Gallivan, M. J.}
}
@article {flosswp26,
	title = {A Case Study of Open Source Software Development: The Apache Server},
	journal = {Proceedings of the International Conference on Software Engineering (ICSE 2000)},
	year = {2000},
	note = {We used the following archival sources of data:
Developer email list (EMAIL).
Concurrent Version Control archive (CVS).
Problem reporting database (BUGDB).},
	month = {June},
	abstract = {According to its proponents, open source style software development has the capacity to compete successfully, and perhaps in many cases displace, traditional commercial development methods. We examine the development process of a major open source application, the Apache web server. By using email archives of source code change history and problem reports we quantify aspects of developer participation, core team size, code ownership, productivity, defect density, and problem resolution interval for this OSS project. This analysis reveals a unique process, which performs well on important measures.},
	keywords = {apache, bug fix revisions, bugs, core, cvs, defect density, developers, email archives, participation, productivity, revision control, revision history, roles, scm, source code, team size},
	attachments = {https://flosshub.org/sites/flosshub.org/files/mockusapache.pdf},
	author = {Audris Mockus and Roy Fielding and Herbsleb, James}
}
