Assigning Bug Reports using a Vocabulary-Based Expertise Model of Developers

For popular software systems, the number of daily submitted bug reports is high. Triaging these incoming reports is a time consuming task. Part of the bug triage is the assignment of a report to a developer with the appropriate expertise. In this paper, we present an approach to automatically suggest developers who have the appropriate expertise for handling a bug report. We model developer expertise using the vocabulary found in their source code contributions and compare this vocabulary to the vocabulary of bug reports. We evaluate our approach by comparing the suggested experts to the persons who eventually worked on the bug. Using eight years of Eclipse development as a case study, we achieve 33.6\% top-1 precision and 71.0\% top-10 recall.

„The plug and the bug“ – a case of coronary embolism in bacterial endocarditis

Systemic embolism is a classic complication of infective endocarditis. Coronary involvement and acute myocardial infarction (MI) are rare and increase mortality significantly. Recognising this unusual entity is crucial to provide adequate care. Percutaneous coronary intervention and thrombus aspiration is preferred to thrombolysis, which classically increases intracerebral hemorrhage risk. The present article describes the case of an acute inferior ST-elevated MI due to a Streptococcus salivarius endocarditis in a patient with known bicuspid aortic valve.

Mining frequent bug-fix code changes

Detecting bugs as early as possible plays an important role in ensuring software quality before shipping. We argue that mining previous bug fixes can produce good knowledge about why bugs happen and how they are fixed. In this paper, we mine the change history of 717 open source projects to extract bug-fix patterns. We also manually inspect many of the bugs we found to get insights into the contexts and reasons behind those bugs. For instance, we found out that missing null checks and missing initializations are very recurrent and we believe that they can be automatically detected and fixed.

Kaffeewelten. Historische Perspektiven auf eine globale Ware im 20. Jahrhundert

Kaffee war im 20. Jahrhundert wichtige Handelsware und heißgeliebtes Konsumgut. Der Sammelband beleuchtet Zusammenhänge und Widersprüche entlang der globalen Warenkette von Produktion, Handel und Konsum. Indigene Erntearbeiter in Mexiko, costaricanische Kleinbauern, Hamburger Importhändler, Röster, Konsumenten und Fair-Trade-Aktivisten stehen als historische Akteure im Zentrum. Geographisch erstreckt sich die Reichweite von Zentralamerika über Hamburg und die beiden deutschen Staaten bis nach Indien, Äthiopien und Brasilien. Das internationale Autorenteam präsentiert neue Forschungsergebnisse zur Wirtschafts-, Sozial- und Kulturgeschichte des Kaffees.

Hot Clones, Maintaining a Link Between Software Clones Across Repositories

Code duplication is common in current programming-practice: programmers search for snippets of code, incorporate them into their projects and then modify them to their needs. In today's practice, no automated scheme is in place to inform both parties of any distant changes of the code. As code snippets continues to evolve both on the side of the user and on the side of the author, both may wish to benefit from remote bug fixes or refinements --- authors may be interested in the actual usage of their code snippets, and researchers could gather information on clone usage. We propose maintaining a link between software clones across repositories and outline how the links can be created and maintained.