@conference {721,
	title = {Software Problem Management as Information Management in a F/OSS Development Community},
	booktitle = {OSS2005: Open Source Systems },
	year = {2005},
	pages = {44-49},
	abstract = {Bug reports created by a large, successful open source software development community show that software problem management (SWPM) is first of all information management and secondarily a problem solving activity. Solving software problems occurs only after a bug report, a first-class information object, has been created and {\textquotedblleft}triaged{\textquotedblright} by community members. One predominant structural feature of defect tracking repositories is the evolving "bug report network" (BRN). Community members create BRNs by progressively asserting various formal and informal relationships between bug reports (BRs). In one F/OSS bug repository under study, participants assert two formal relationships (duplications and dependencies) and various informal relationships (like "see also" references). BRNs can be interpreted as (1) information ordering strategies that support collocation of related BRs, decreasing cognitive and organizational effort; (2) sense-making strategies wherein BRNs provide mor...},
	url = {http://pascal.case.unibz.it/handle/2038/1533},
	author = {Sandusky, Robert J.}
}
@conference {Gasser04researchinfrastructure,
	title = {Research Infrastructure for Empirical Science of F/OSS},
	booktitle = {Proc. Intern. Workshop on Mining Software Repositories},
	year = {2004},
	pages = {12-16},
	abstract = {F/OSS research faces a new and unusual situation: the traditional difficulties of gathering enough empirical data have been replaced by issues of dealing with enormous amounts of freely available data from many disparate sources (forums, code, bug reports, etc.) At present no means exist for assembling these data under common access points and frameworks for comparative, longitudinal, and collaborative research. Gathering and maintaining large F/OSS data collections reliably and making them usable present several research challenges. For example, current projects usually rely on {\textquotedblleft}web scraping{\textquotedblright} or on direct access to raw data from groups that generate it, and both of these methods require unique effort for each new corpus, or even for updating existing corpora. In this paper we identify several common needs and critical factors in F/OSS empirical research, and suggest orientations and recommendations for the design of a shared research infrastructure.},
	keywords = {data, Data Collection, empirical, infrastructure},
	attachments = {https://flosshub.org/sites/flosshub.org/files/12ResearchInfrastructure.pdf},
	author = {Gasser, Les and Gabriel Ripoche and Sandusky, Robert J.}
}
