849 research outputs found
Is New Zealand' s Migration System a Feasible Option for Germany?
No full textNeuseeland und Deutschland können auf ähnliche Migrationserfahrungen zurückblicken, jedoch unterscheiden sich beide Länder im politischen Umgang mit Einwanderung und Integration. Neuseeland präsentiert sich hierbei als eine offenere Gesellschaft als die Bundesrepublik. Die vorliegende Studie wurde als Diplomarbeit an der Sozialwissenschaftlichen Fakultät der Universität Göttingen eingereicht. Sie vergleicht die beiden Einwanderungsländer und fragt danach, ob in migrations- und integrationspolitischen Regulierungen in Neuseeland Anleihen für eine Neuausrichtung des Politikfeldes in Deutschland genommen werden können. Dies betrifft auch die Anwerbung von hochqualifizierten Fachkräften. Neuseeland ist hier besonders erfolgreich und ergänzt die Anwerbung von Migrantinnen und Migranten und ihren Familien mit einer Integration in das Bildungssystem und politische System. Durch diesen ganzheitlichen politischen Ansatz könnte die Attraktivität Deutschlands als Zielland von Migration erhöht werden.New Zealand and Germany have both had similar experiences with migration. However, the two countries differ substantially in their political approach to migration and the social integration of migrants. In this respect, New Zealand appears to be a more open society than Germany. This study was submitted as a Diploma thesis at the faculty of Social Sciences at the University of Göttingen. The thesis compares the two countries, which are both strongly influenced by migration patterns, and seeks feasible options which Germany could potentially adopt from New Zealand's migration and integration policy. In this context the attraction of high-skilled migrants plays an important role. New Zealand's attraction of high-skilled migrants and their families is accomplished by integrative policy in the education and political systems. As the study concludes, this holistic approach could also enhance Germany's attractiveness for migration
Curated dataset of bug fix commits from "An Empirical Study on Real Bug Fixes"
No full text<p>To cite it:</p>
<p><code>@misc{bfdataset,<br>
author = {Martin Monperrus},<br>
title = {Curated dataset of bug fix commits from "An Empirical Study on Real Bug Fixes"},<br>
year = 2017,<br>
doi = {10.5281/zenodo.1004734},<br>
url = {https://doi.org/10.5281/zenodo.1004734}<br>
}</code></p>
<pre>
</pre>
<p> </p>
The Bug (After Mayakovsky)
Get PDFhttps://desingel.be/en/programme/performance/dora-garcia-and-others-the-bug-after-mayakovsky
DORA GARCÍA AND OTHERS
THE BUG (AFTER MAYAKOVSKY)
THE BUG (After Mayakovsky) is a performance adaptation of one of the last plays by Russian futurist Vladimir Mayakovsky. The play introduces (1929) a science fiction plot popular already then and used many times since: a visitor to the future coming from a past that is our present. In Mayakovsky’s bitter and comic play, a soviet revolutionary is frozen in 1929 and reawakens in 1979 - by accident, a parasite accompanies him in this time travel. Using Mayakovsky's play as a guide, a collective author wants to analyze questions such as: What happens in a time lapse of 50 years? How to explain 50 years to someone who spent them in a coma? Is it true that history moves in cycles and there is an eternal return? Could we speak of glitches in this infinite repetition, and could we liken the glitch* to THE BUG? The shared disappointment of the man projected into the future and the inhabitants of that future forced to confront their original past is what helps us analyze our present moment in terms of repetition, melancholy, and action. The development of the project aims at studying and understanding collectively created and performed theater / performance, forming a collective made of different ages, experiences, and disciplines; the idea of collective going even beyond the artists' group. THE BUG (After Mayakovsky) adopts a format, the public rehearsal, that allows for instant feedback from the audience, and no one present is out of it, approaching even the assembly format.
*A glitch is a short-lived fault in a system, such as a transient fault that corrects itself, making it difficult to troubleshoot. A glitch, which is slight and often temporary, differs from a more serious bug which is a genuine functionality-breaking problem.
The production of the new performance is conceived as a preview of Dora Garcia's exhibition at M HKA in 2023 which takes as its starting point the artist's practice at the intersection of visual arts, performing arts and literature. It is a collaboration between M HKA, DeSingel (Antwerp) and Oslo National Academy of the Arts
What if a bug has a Different Origin?: Making Sense of Bugs Without an Explicit Bug Introducing Change
No full textBackground: Many studies in the software research literature on bug fixing are built upon the assumption that "a given bug was introduced by the lines of code that were modified to fix it", or variations of it. Although this assumption seems very reasonable at first glance, there is little empirical evidence supporting it. A careful examination surfaces that there are other possible sources for the introduction of bugs such as modifications to those lines that happened before the last change an changes external to the piece of code being fixed. Goal: We aim at understanding the complex phenomenon of bug introduction and bug fix. Method: We design a preliminary approach distinguishing between bug introducing commits (BIC) and first failing moments (FFM). We apply this approach to Nova and ElasticSearch, two large and well-known open source software projects. Results: In our initial results we obtain that at least 24% bug fixes in Nova and 10% in ElasticSearch have not been caused by a BIC but by co-evolution, compatibility issues or bugs in external API. Merely 26--29% of BICs can be found using the algorithm based on the assumption that "a given bug was introduced by the lines of code that were modified to fix it". Conclusions: The approach allows also for a better framing of the comparison of automatic methods to find bug inducting changes. Our results indicate that more attention should be paid to whether a bug has been introduced and, when it was introduced.Green Open Access added to TU Delft Institutional Repository ‘You share, we take care!’ – Taverne project https://www.openaccess.nl/en/you-share-we-take-care Otherwise as indicated in the copyright section: the publisher is the copyright holder of this work and the author uses the Dutch legislation to make this work public.Software Engineerin
Editorial: Kriminalität und Innere Sicherheit: objektive Lage und Wahrnehmung durch Medien und Politik
No full textBug M, Krähnert K, Kroh M. Kriminalität und Innere Sicherheit: objektive Lage und Wahrnehmung durch Medien und Politik [Editorial]. Vierteljahrshefte zur Wirtschaftsforschung. 2015;84(2):5-10
An article on how the author gets bitten by the antiquing bug during an off-seas
No full textAn article on how the author gets bitten by the antiquing bug during an off-season expedition in southern Maine with artist friend Marguerite Robichaux
Labops, a plant bug, on Oregon rangeland
No full textTitle from PDF caption (viewed on August 21, 2017).This archived document is maintained by the State Library of Oregon as part of the Oregon Documents Depository Program. It is for informational purposes and may not be suitable for legal purposes.Mode of access: Internet from the Oregon Government Publications Collection.Text in English
Not All Bugs Are the Same:Understanding, Characterizing, and Classifying Bug Types
Get PDFModern version control systems, e.g., GitHub, include bug tracking mechanisms that developers can use to highlight the presence of bugs. This is done by means of bug reports, i.e., textual descriptions reporting the problem and the steps that led to a failure. In past and recent years, the research community deeply investigated methods for easing bug triage, that is, the process of assigning the fixing of a reported bug to the most qualified developer. Nevertheless, only a few studies have reported on how to support developers in the process of understanding the type of a reported bug, which is the first and most time-consuming step to perform before assigning a bug-fix operation. In this paper, we target this problem in two ways: first, we analyze 1280 bug reports of 119 popular projects belonging to three ecosystems such as MOZILLA, APACHE, and ECLIPSE, with the aim of building a taxonomy of the types of reported bugs; then, we devise and evaluate an automated classification model able to classify reported bugs according to the defined taxonomy. As a result, we found nine main common bug types over the considered systems. Moreover, our model achieves high F-Measure and AUC-ROC (64% and 74% on overall, respectively).Green Open Access added to TU Delft Institutional Repository ‘You share, we take care!’ – Taverne project https://www.openaccess.nl/en/you-share-we-take-care Otherwise as indicated in the copyright section: the publisher is the copyright holder of this work and the author uses the Dutch legislation to make this work public.Software Engineerin
- …
