DOCSLIB.ORG

Automatic Bug Triaging Techniques Using Machine Learning and Stack Traces and Submitted in Partial Fulfillment of the Requirements for the Degree Of

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Automatic Bug Triaging Techniques Using Machine Learning and Stack Traces Korosh Koochekian Sabor A Thesis In The Department of Electrical and Computer Engineering Presented in Partial Fulfillment of the Requirements For the Degree of Doctor of Philosophy (Electrical and Computer Engineering) at Concordia university Montreal, Quebec, Canada July 2019 © Korosh Koochekian Sabor, 2019 CONCORDIA UNIVERSITY SCHOOL OF GRADUATE STUDIES This is to certify that the thesis prepared By: Korosh Koochekian Sabor Entitled: Automatic bug triaging techniques using machine learning and stack traces and submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy (Electrical and Computer Engineering) complies with the regulations of the University and meets the accepted standards with respect to originality and quality. Signed by the final examining committee: Chair Dr. Luis Amador External Examiner Dr. Ali Ouni External to Program Dr. Nikos Tsantalis Examiner Dr. Anjali Agarwal Examiner Dr. Nawwaf Kharma Thesis Supervisor Dr. Abdelwahab Hamou-Lhadj Approved by Dr. Rastko R. Selmic, Graduate Program Director September 27, 2019 Dr. Amir Asif, Dean Gina Cody School of Engineering & Computer Science Abstract Automatic Bug Triaging Techniques Using Machine Learning and Stack Traces Korosh Koochekian Sabor, Ph.D. Concordia University, 2019 When a software system crashes, users have the option to report the crash using automated bug tracking systems. These tools capture software crash and failure data (e.g., stack traces, memory dumps, etc.) from end-users. These data are sent in the form of bug (crash) reports to the software development teams to uncover the causes of the crash and provide adequate fixes. The reports are first assessed (usually in a semi-automatic way) by a group of software analysts, known as triagers. Triagers assign priority to the bugs and redirect them to the software development teams in order to provide fixes. The triaging process, however, is usually very challenging. The problem is that many of these reports are caused by similar faults. Studies have shown that one way to improve the bug triaging process is to detect automatically duplicate (or similar) reports. This way, triagers would not need to spend time on reports caused by faults that have already been handled. Another issue is related to the prioritization of bug reports. Triagers often rely on the information provided by the customers (the report submitters) to prioritize bug reports. However, this task can be quite tedious and requires tool support. Next, triagers route the bug report to the responsible development team based on the subsystem, which caused the crash. Since having knowledge of all the subsystems of an ever-evolving industrial system is impractical, having a tool to automatically identify defective subsystems can significantly reduce the manual bug triaging effort. iii The main goal of this research is to investigate techniques and tools to help triagers process bug reports. We start by studying the effect of the presence of stack traces in analyzing bug reports. Next, we present a framework to help triagers in each step of the bug triaging process. We propose a new and scalable method to automatically detect duplicate bug reports using stack traces and bug report categorical features. We then propose a novel approach for predicting bug severity using stack traces and categorical features, and finally, we discuss a new method for predicting faulty product and component fields of bug reports. We evaluate the effectiveness of our techniques using bug reports from two large open-source systems. Our results show that stack traces and machine learning methods can be used to automate the bug triaging process, and hence increase the productivity of bug triagers, while reducing costs and efforts associated with manual triaging of bug reports. iv Acknowledgments First and foremost, I want to express my profound and sincere gratitude to my respectful supervisor, Dr. Abdelwahab Hamou-Lhadj. Thanks for your trust in me, and thank you for proactively providing me all the academic, mental, and financial support I needed throughout the program. I would like to express my heartfelt gratitude for your mentorship, which helped me grow both professionally, personally and helped me to further develop my future career path. My deep gratitude for all the support I received from my PhD committee, Dr. Nikolaos Tsantalis, Dr. Nawwaf Kharma, Dr. Ali Ouni and Dr. Anjali Agarwal. Their suggestions significantly helped me in further improving the direction of my research. I would like to extend my thanks to Alf Larsson from Ericsson, Sweden, whose feedback and comments throughout this work have been very valuable. I would also like to thank Ericsson, MITACS, NSERC, and the Gina School of Engineering and Computer Science at Concordia University for their financial support. Many thanks to all my friends at Concordia University. I was thrilled to have been surrounded by such wonderful people. Special thanks to Mohammad Reza Rejali and Amir Bahador Gahroosi for being such wonderful friends, I would be indebted for what you did for me during our collaboration and friendship in Concordia. Thanks to all my friends outside of Concordia, including Mojataba Khomami Abadi and Parham Darbandi, for all their friendship and support. Words cannot express my gratitude and gratefulness enough to my beloved family members. My deepest appreciation for my Parents Anoushe and Saeedeh, for inspiring me to start the program and giving me heartwarming all the way through my program, my beloved sister, Camelia, who always supported my decisions from thousands miles away, and very special thanks to my wife, Camelia, I am very blessed to have you in my life, thanks for your extraordinary patience, care, kindness, love and all the sacrifices you made throughout the program. I could not have accomplished this work without your unconditional support. v Table of Contents List of Figures ..................................................................................................................... ix List of Tables ....................................................................................................................... xi 1 Introduction .......................................................................................................................... 1 1.1. Terminology ............................................................................................................ 4 1.2. Research Hypothesis ............................................................................................... 4 1.3. Thesis Contributions ................................................................................................ 5 1.3.1. Chapter 2: Background and Related Work ...................................................... 6 1.3.2. Chapter 3: Data Preparation ........................................................................... 6 1.3.3. Chapter 4: An Empirical Study on the Effectiveness of Stack traces ............... 7 1.3.4. Chapter 5: Detecting Duplicate Bug Reports ................................................... 7 1.3.5. Chapter 6: Predicting Severity of Bugs ............................................................ 7 1.3.6. Chapter 7: Predicting Faulty Product and Component Fields of Bug Reports . 7 1.3.7. Chapter 8: Conclusion and future work .......................................................... 7 2 Background and Related Work .............................................................................................. 8 2.1. Background ............................................................................................................. 8 2.1.1. Bug Report Description ................................................................................... 8 2.1.2. Stack Trace ...................................................................................................... 8 2.1.3. Categorical Information .................................................................................. 9 2.2. Related Work ......................................................................................................... 10 2.2.1. Usefulness of Stack Traces ............................................................................ 10 2.2.2. Detection of Duplicate Bug Reports .............................................................. 11 2.2.3. Predicting Bug Severity ................................................................................. 18 2.2.4. Bug Report Faulty Product and Component Field Prediction ....................... 24 3 Data Preparation ................................................................................................................. 28 3.1. Eclipse Dataset ...................................................................................................... 28 3.2. Gnome Dataset ..................................................................................................... 29 4 Empirical Study on the Effectiveness of Presence of Stack Traces ...................................... 31 4.1. Dataset Setup ........................................................................................................ 31 4.2. Statistical Analysis ................................................................................................. 32 4.3. Experiments .......................................................................................................... 32 4.4. Study Result ..........................................................................................................
Recommended publications
  • Final Study Report on CEF Automated Translation Value Proposition in the Context of the European LT Market/Ecosystem

    Final Study Report on CEF Automated Translation Value Proposition in the Context of the European LT Market/Ecosystem

    Final study report on CEF Automated Translation value proposition in the context of the European LT market/ecosystem FINAL REPORT A study prepared for the European Commission DG Communications Networks, Content & Technology by: Digital Single Market CEF AT value proposition in the context of the European LT market/ecosystem Final Study Report This study was carried out for the European Commission by Luc MEERTENS 2 Khalid CHOUKRI Stefania AGUZZI Andrejs VASILJEVS Internal identification Contract number: 2017/S 108-216374 SMART number: 2016/0103 DISCLAIMER By the European Commission, Directorate-General of Communications Networks, Content & Technology. The information and views set out in this publication are those of the author(s) and do not necessarily reflect the official opinion of the Commission. The Commission does not guarantee the accuracy of the data included in this study. Neither the Commission nor any person acting on the Commission’s behalf may be held responsible for the use which may be made of the information contained therein. ISBN 978-92-76-00783-8 doi: 10.2759/142151 © European Union, 2019. All rights reserved. Certain parts are licensed under conditions to the EU. Reproduction is authorised provided the source is acknowledged. 2 CEF AT value proposition in the context of the European LT market/ecosystem Final Study Report CONTENTS Table of figures ................................................................................................................................................ 7 List of tables ..................................................................................................................................................
  • Translate's Localization Guide

    Translate's Localization Guide

    Translate’s Localization Guide Release 0.9.0 Translate Jun 26, 2020 Contents 1 Localisation Guide 1 2 Glossary 191 3 Language Information 195 i ii CHAPTER 1 Localisation Guide The general aim of this document is not to replace other well written works but to draw them together. So for instance the section on projects contains information that should help you get started and point you to the documents that are often hard to find. The section of translation should provide a general enough overview of common mistakes and pitfalls. We have found the localisation community very fragmented and hope that through this document we can bring people together and unify information that is out there but in many many different places. The one section that we feel is unique is the guide to developers – they make assumptions about localisation without fully understanding the implications, we complain but honestly there is not one place that can help give a developer and overview of what is needed from them, we hope that the developer section goes a long way to solving that issue. 1.1 Purpose The purpose of this document is to provide one reference for localisers. You will find lots of information on localising and packaging on the web but not a single resource that can guide you. Most of the information is also domain specific ie it addresses KDE, Mozilla, etc. We hope that this is more general. This document also goes beyond the technical aspects of localisation which seems to be the domain of other lo- calisation documents.
  • Desarrollo De Una Nueva Versión De Gtranslator: Reactivando Una

    Desarrollo De Una Nueva Versión De Gtranslator: Reactivando Una

    Desarrollo de una nueva versi´onde gtranslator: reactivando una comunidad de Software Libre Pablo Jos´eSangiao Roca Master on Free Software Caixanova [email protected] 2 de diciembre de 2008 c 2008 Pablo Jos´eSangiao Roca. Este documento se distribuye bajo la licencia Creative Commons 2.5 con reco- nocimiento, compartir igual. M´asdetalles sobre esta licencia en: http://creativecommons.org/licenses/by-nc-sa/2.5/es/ Resumen Un apartado muy importante para la difusi´ondel Software Libre es, sin duda, la localizaci´onde los programas. Adem´asde permitir que los usuarios puedan hacer uso de las aplicaciones adaptadas a su lengua y costumbres, facilita tambi´enque personas con perfiles no t´ecnicos, pue- dan colaborar en las comunidades de Software Libre mediante la realiza- ci´onde traducciones. Para facilitar esta labor existen algunas aplicaciones como son Kbabel dentro del proyecto KDE y gtranslator en el proyec- to GNOME. Esta ´ultimase encontraba en un estado de desarrollo muy pobre, abandonada incluso por los traductores de GNOME y con una comunidad a su alrededor pr´acticamente inexistente. En este art´ıculose mostrar´ael trabajo que se realiz´opara desarrollar una nueva versi´onde esta herramienta, que la coloque en un punto de referencia para la co- munidad de traductores. Adem´asse indicar´anlas decisiones y propuestas realizadas para intentar dinamizar la comunidad, as´ıcomo un an´alisisdel estado de la misma a trav´esde informaci´onobtenida a partir del sistema de control de versiones y listas de correo del programa. 1. Introducci´on Los proyectos de Software Libre que tienen ´exito,suelen tener una carac- ter´ısticacom´un:una gran comunidad detr´as.Esto permite que, a pesar de que la mayor´ıason comenzados y mantenidos por personas en su tiempo libre, crez- can r´apidamente gracias a las peque~nascontribuciones de mucha gente.
  • Indicators for Missing Maintainership in Collaborative Open Source Projects

    Indicators for Missing Maintainership in Collaborative Open Source Projects

    TECHNISCHE UNIVERSITÄT CAROLO-WILHELMINA ZU BRAUNSCHWEIG Studienarbeit Indicators for Missing Maintainership in Collaborative Open Source Projects Andre Klapper February 04, 2013 Institute of Software Engineering and Automotive Informatics Prof. Dr.-Ing. Ina Schaefer Supervisor: Michael Dukaczewski Affidavit Hereby I, Andre Klapper, declare that I wrote the present thesis without any assis- tance from third parties and without any sources than those indicated in the thesis itself. Braunschweig / Prague, February 04, 2013 Abstract The thesis provides an attempt to use freely accessible metadata in order to identify missing maintainership in free and open source software projects by querying various data sources and rating the gathered information. GNOME and Apache are used as case studies. License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license. Keywords Maintenance, Activity, Open Source, Free Software, Metrics, Metadata, DOAP Contents List of Tablesx 1 Introduction1 1.1 Problem and Motivation.........................1 1.2 Objective.................................2 1.3 Outline...................................3 2 Theoretical Background4 2.1 Reasons for Inactivity..........................4 2.2 Problems Caused by Inactivity......................4 2.3 Ways to Pass Maintainership.......................5 3 Data Sources in Projects7 3.1 Identification and Accessibility......................7 3.2 Potential Sources and their Exploitability................7 3.2.1 Code Repositories.........................8 3.2.2 Mailing Lists...........................9 3.2.3 IRC Chat.............................9 3.2.4 Wikis............................... 10 3.2.5 Issue Tracking Systems...................... 11 3.2.6 Forums............................... 12 3.2.7 Releases.............................. 12 3.2.8 Patch Review........................... 13 3.2.9 Social Media............................ 13 3.2.10 Other Sources..........................
  • GNOME 3 Application Development Beginner's Guide

    GNOME 3 Application Development Beginner's Guide

    GNOME 3 Application Development Beginner's Guide Step-by-step practical guide to get to grips with GNOME application development Mohammad Anwari BIRMINGHAM - MUMBAI GNOME 3 Application Development Beginner's Guide Copyright © 2013 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: February 2013 Production Reference: 1080213 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-84951-942-7 www.packtpub.com Cover Image by Duraid Fatouhi ([email protected]) Credits Author Project Coordinator Mohammad Anwari Abhishek Kori Reviewers Proofreader Dhi Aurrahman Mario Cecere Joaquim Rocha Indexer Acquisition Editor Tejal Soni Mary Jasmine Graphics Lead Technical Editor Aditi Gajjar Ankita Shashi Production Coordinator Technical Editors Aparna Bhagat Charmaine Pereira Cover Work Dominic Pereira Aparna Bhagat Copy Editors Laxmi Subramanian Aditya Nair Alfida Paiva Ruta Waghmare Insiya Morbiwala About the Author Mohammad Anwari is a software hacker from Indonesia with more than 13 years of experience in software development.
  • Pdfswqokdvt2o.Pdf

    Pdfswqokdvt2o.Pdf

    GNOME 3 Application Development Beginner's Guide Step-by-step practical guide to get to grips with GNOME application development Mohammad Anwari BIRMINGHAM - MUMBAI GNOME 3 Application Development Beginner's Guide Copyright © 2013 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: February 2013 Production Reference: 1080213 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-84951-942-7 www.packtpub.com Cover Image by Duraid Fatouhi ([email protected]) Credits Author Project Coordinator Mohammad Anwari Abhishek Kori Reviewers Proofreader Dhi Aurrahman Mario Cecere Joaquim Rocha Indexer Acquisition Editor Tejal Soni Mary Jasmine Graphics Lead Technical Editor Aditi Gajjar Ankita Shashi Production Coordinator Technical Editors Aparna Bhagat Charmaine Pereira Cover Work Dominic Pereira Aparna Bhagat Copy Editors Laxmi Subramanian Aditya Nair Alfida Paiva Ruta Waghmare Insiya Morbiwala About the Author Mohammad Anwari is a software hacker from Indonesia with more than 13 years of experience in software development.
  • Debian and Ubuntu

    Debian and Ubuntu

    Debian and Ubuntu Lucas Nussbaum lucas@{debian.org,ubuntu.com} lucas@{debian.org,ubuntu.com} Debian and Ubuntu 1 / 28 Why I am qualified to give this talk Debian Developer and Ubuntu Developer since 2006 Involved in improving collaboration between both projects Developed/Initiated : Multidistrotools, ubuntu usertag on the BTS, improvements to the merge process, Ubuntu box on the PTS, Ubuntu column on DDPO, . Attended Debconf and UDS Friends in both communities lucas@{debian.org,ubuntu.com} Debian and Ubuntu 2 / 28 What’s in this talk ? Ubuntu development process, and how it relates to Debian Discussion of the current state of affairs "OK, what should we do now ?" lucas@{debian.org,ubuntu.com} Debian and Ubuntu 3 / 28 The Ubuntu Development Process lucas@{debian.org,ubuntu.com} Debian and Ubuntu 4 / 28 Linux distributions 101 Take software developed by upstream projects Linux, X.org, GNOME, KDE, . Put it all nicely together Standardization / Integration Quality Assurance Support Get all the fame Ubuntu has one special upstream : Debian lucas@{debian.org,ubuntu.com} Debian and Ubuntu 5 / 28 Ubuntu’s upstreams Not that simple : changes required, sometimes Toolchain changes Bugfixes Integration (Launchpad) Newer releases Often not possible to do work in Debian first lucas@{debian.org,ubuntu.com} Debian and Ubuntu 6 / 28 Ubuntu Packages Workflow lucas@{debian.org,ubuntu.com} Debian and Ubuntu 7 / 28 Ubuntu Packages Workflow Ubuntu Karmic Excluding specific packages language-(support|pack)-*, kde-l10n-*, *ubuntu*, *launchpad* Missing 4% : Newer upstream
  • Interns Lightning Talks

    Interns Lightning Talks

    Interns Lightning Talks Proxy editing PiTiVi Proxy editing Anton Belka, [email protected] GUADEC 2013 The TM Conference GUADEC Proxy editing What is proxy editing? Proxy editing is the ability to swap video clips by a "proxy" version that is more suited for editing, and then using the original, full-quality clips to do the render. The TM Conference GUADEC Proxy editing Implementation GStreamer Editing Services (GES) Design and implement proxy editing API in GES Write tests for proxy editing API Fixing possible issues PiTiVi Integrate changes in GES with PiTiVi Fixing possible issues The TM Conference GUADEC Proxy editing Summary We must have manual/semi-automated and fully-automated modes We must be able choose what video clips must use proxy editing mode No negative impacts on perfomance when generating the clips "proxies" The TM Conference GUADEC Appendix ResourcesI PiTiVi http://pitivi.org GStreamer http://gstreamer.freedesktop.org Proxy editing requirements http://wiki.pitivi.org/wiki/Proxy_editing_ requirements My blog http://antonbelka.com The TM Conference GUADEC Bookshelf View Tiled Rendering Things I learnt Bookshelf View & Tiling for Evince Aakash Goenka, [email protected] Google Summer of Code 2013 GUADEC 2013 The TM Conference GUADEC Bookshelf View Tiled Rendering Things I learnt Why bookshelf? For easy access to recently opened documents Looks way cooler than a blank window Display more items than `Recent Files' menu The TM Conference GUADEC Bookshelf View Tiled Rendering Things I learnt Bookshelf Screenshot Figure
  • GUADEC Schedule.Pdf

    GUADEC Schedule.Pdf

    1 Contents About the event ......................................................................................................................... 5 Map of the location............................................................................................................................................................. 5 Welcome to GUADEC!................................................................................................................. 6 The G !ME !pen Des"top Da#............................................................................................... $ Main t%ac" sche&ule................................................................................................................... ' We&nes&a# ('th )ul#.......................................................................................................................................................... ' Thurs&a# 29th )ul#............................................................................................................................................................... * +ri&a# ,-th )ul#.................................................................................................................................................................... 10 Abst%acts..................................................................................................................................... 1( G OME, the /eb. an& +ree&om................................................................................................................................
  • Yearbook 2013 – GNOME Outreach Program

    Yearbook 2013 – GNOME Outreach Program

    YEARBOOK 2013 GNOME OutrEACH PrOGRAM Editor, Layout & Design: Daniel G. Siegel <[email protected]> With LOTS OF HELP BY AleXANDRE FrANKe, Allan Day, AndrEAS Nilsson, Christophe Fergeau, Ekaterina GerASIMOva, Fabiano Fidêncio, Jakub Steiner, KarEN Sandler, Marina ZhurAKHINSKAYA AND Zeeshan Ali (Khattak). Last UPDATED ON August 1, 2013. This DOCUMENT IS LICENSED UNDER A CrEATIVE Commons Attribution – ShareAlikE license. Contents 1 ForEWORD4 2 WORDS BY THE GNOME OutrEACH Admins5 3 Students & INTERNS7 Aakanksha Gaur8 • Aakash Goenka9 • AlessandrO Campagni 10 • AleX MuñoZ 11 • Anton Belka 12 • Aruna SankarANARAYANAN 13 • Bogdan Gabriel Ciobanu 14 • Camilo Polymeris 15 • Carlos Soriano 16 • Dylan McCall 17 • Eslam Mostafa 18 • Evgeny Bobkin 19 • Flavia WEISGHIZZI 20 • Garima Joshi 21 • GökCEN ErASLAN 22 • Guillaume MazoYER 23 • Joris VALETTE 24 • KaleV Lember 25 • Lavanya GunasekarAN 26 • Magdalen Berns 27 • MarCOS Chavarría TEIJEIRO 28 • Mathieu Duponchelle 29 • Mattias Bengtsson 30 • Meg ForD 31 • Melissa S. R. WEN 32 • Parin PorECHA 33 • P¯ETERIS KrišJ¯ANIS 34 • Pooja SaxENA 35 • Rafael Fonseca 36 • RicharD Schwarting 37 • Sai Suman PrAYAGA 38 • Sam Bull 39 • Satabdi Das 40 • Saumya Dwivedi 41 • Saumya Pathak 42 • Sébastien Wilmet 43 • Shivani Poddar 44 • Simon Corsin 45 • Sindhu S 46 • TiffANY YAU 47 • Ting-WEI Lan 48 • TOMASZ MaczyńSKI 49 • Valentín BarrOS 50 • Victor TOSO 51 • Xuan Hu 52 • ŽAN DoberšEK 53 4 Sponsors 54 3 ForEWORD Dear GNOME Lovers, WELCOME TO GNOME! As EXECUTIVE DIRECTOR OF THE GNOME Foundation AND A I THINK I CAN SAFELY SAY, HOWEver, THAT IF YOU’RE READING MENTOR IN THE OPW, I HOPE YOU USE ALL OF THE RESOURCES THIS YOU’RE ALREADY AN IMPORTANT PART OF GNOME.
  • Open Translation Tools: Disruptive Potential to Broaden Access to Knowledge

    Open Translation Tools: Disruptive Potential to Broaden Access to Knowledge

    Open Translation Tools: Disruptive Potential to Broaden Access to Knowledge Prepared for Open Society Institute by Allen Gunn Aspiration September 2008 This document is distributed under a Creative Commons Attribution-ShareAlike 3.0 License San Francisco Nonprofit Technology Center, 1370 Mission St., San Francisco, CA 94103 Phone: (415) 839-6456 • [email protected] • Page 1 Table of Contents 1. Executive Summary..........................................................................3 2. Acknowledgments............................................................................6 3. OTT07 Event Background and Agenda...........................................7 4. Translation Concepts......................................................................11 5. Use Cases for Open Content Translation......................................13 6. Open Translation Tools..................................................................17 7. OTT07 “Dream” Translation Tool...................................................22 8. Technical Innovations and Considerations....................................26 9. Related Issues and Gating Factors................................................33 10.Event Outcomes and Ideas for Next Steps....................................36 11.Appendix I: Open Translation Use Cases......................................39 12.Appendix II: Open Translation Tools..............................................49 San Francisco Nonprofit Technology Center, 1370 Mission St., San Francisco, CA 94103 Phone: (415) 839-6456 •
  • Translations in Libre Software

    Translations in Libre Software

    UNIVERSIDAD REY JUAN CARLOS Master´ Universitario en Software Libre Curso Academico´ 2011/2012 Proyecto Fin de Master´ Translations in Libre Software Autor: Laura Arjona Reina Tutor: Dr. Gregorio Robles Agradecimientos A Gregorio Robles y el equipo de Libresoft en la Universidad Rey Juan Carlos, por sus consejos, tutor´ıa y acompanamiento˜ en este trabajo y la enriquecedora experiencia que ha supuesto estudiar este Master.´ A mi familia, por su apoyo y paciencia. Dedicatoria Para mi sobrino Dar´ıo (C) 2012 Laura Arjona Reina. Some rights reserved. This document is distributed under the Creative Commons Attribution-ShareAlike 3.0 license, available in http://creativecommons.org/licenses/by-sa/3.0/ Source files for this document are available at http://gitorious.org/mswl-larjona-docs 4 Contents 1 Introduction 17 1.1 Terminology.................................... 17 1.1.1 Internationalization, localization, translation............... 17 1.1.2 Free, libre, open source software..................... 18 1.1.3 Free culture, freedom definition, creative commons........... 20 1.2 About this document............................... 21 1.2.1 Structure of the document........................ 21 1.2.2 Scope................................... 22 1.2.3 Methodology............................... 22 2 Goals and objectives 23 2.1 Goals....................................... 23 2.2 Objectives..................................... 23 2.2.1 Explain the phases of localization process................ 24 2.2.2 Analyze the benefits and counterparts.................. 24 2.2.3 Provide case studies of libre software projects and tools......... 24 2.2.4 Present personal experiences....................... 24 3 Localization in libre software projects 25 3.1 Localization workflow.............................. 25 3.2 Prepare: Defining objects to be localized..................... 27 3.2.1 Some examples.............................