DOCSLIB.ORG

The Ultimate Debian Database: Consolidating Bazaar Metadata for Quality Assurance and Data Mining

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Ultimate Debian Database: Consolidating Bazaar Metadata for Quality Assurance and Data Mining The Ultimate Debian Database: Consolidating Bazaar Metadata for Quality Assurance and Data Mining Lucas Nussbaum Stefano Zacchiroli LORIA / Nancy-Universite´ Universite´ Paris Diderot, PPS Nancy, France UMR 7126, Paris, France Email: [email protected] Email: [email protected] Abstract—FLOSS distributions like RedHat and Ubuntu form—, it is not as common among FLOSS distributions. require a lot more complex infrastructures than most other The role of such distributions (e.g. Debian, Fedora, Ubuntu, FLOSS projects. In the case of community-driven distributions openSUSE, Gentoo, to name just a few) is to mediate be- like Debian, the development of such an infrastructure is often not very organized, leading to new data sources being added in tween “upstream” development projects and their final users. an impromptu manner while hackers set up new services that In doing so distributions try to ease software installation gain acceptance in the community. Mixing and matching data and configuration, often by the mean of the package ab- is then harder than should be, albeit being badly needed for stractions [4]. The peculiar role of distributions makes their Quality Assurance and data mining. Massive refactoring and infrastructure needs different from those of development integration is not a viable solution either, due to the constraints imposed by the bazaar development model. projects; some of their peculiar needs are: 1 This paper presents the Ultimate Debian Database (UDD), • archive management that enable developers to release which is the countermeasure adopted by the Debian project new packages, usually to fix bugs or in response to new to the above “data hell”. UDD gathers data from various data sources into a single, central SQL database, turning Quality upstream releases; Assurance needs that could not be easily implemented before • build bots (or build daemons) that rebuild packages on into simple SQL queries. The paper also discusses the customs architectures other than those available to individual that have contributed to the data hell, the lessons learnt while maintainers; designing UDD, and its applications and potentialities for data • support for distribution-wide rebuilds to evaluate the mining on FLOSS distributions. impact of core toolchain (e.g. gcc) changes [5]; Keywords-open source; distribution; data warehouse; quality • multi-package bug tracking able to scale up to millions assurance; data mining of bugs; • automated testing I. INTRODUCTION to check that packages adhere to some distribution policy, that might change over time; Most FLOSS (Free/Libre Open Source Software) projects • developer tracking to quickly identify developers whose require some infrastructure: a version control system (VCS) interest fade away [6]; to store source code, a bug tracker to organize development • support for different line of developments (or suites, work, mailing lists for user and developer communication, e.g.: stable, unstable, . ), corresponding to indepen- and a homepage for “marketing” purposes. The needs are dently evolving sets of packages; usually that simple, and are also similar across projects. That similarity has paved the way to the diffusion of forge The sheer amount of packages to be managed, the resources software and providers of one-fits-all FLOSS-infrastructures, needed, the relatively small number of FLOSS distributions, that have been steadily growing for the past decade [1]. Such and the existence of distribution-specific customizations of a de facto standardization of infrastructure eases all tasks the above processes have hindered the standardization of that require mining and comparing facts about, for instance, distribution infrastructures: every distribution has developed all projects hosted on the very same (or across very similar) its own infrastructure. Still, the ability to combine together forge(s) (e.g. [2], [3]). information coming from different distribution data sources While infrastructure standardization is common among is compelling for distributions as it is for researchers willing FLOSS development projects—whose aim is developing and to mine and study facts about them. periodically release software components, usually in source The need of researchers to have convenient access to distribution data is easily explained: they want to focus on Stefano Zacchiroli is partially supported by the European Community data mining rather than on the gazillion of technologies FP7, MANCOOSI project, grant agreement n. 214898 Unless otherwise stated, cited URLs have been retrieved on 12/01/2010. under which they are hidden. As an example of distribution 1http://udd.debian.org needs to combine data, we consider Quality Assurance (QA) Table I DESIGN CHOICES IN THE DEBIAN INFRASTRUCTURE: PROGRAMMING LANGUAGE AND DATA FORMAT Purpose Name Implementation language and data storage format Python, problem-specific PostgreSQL database. Archive management dak Data exported as text files formatted similarly to (but not equal to) RFC 2822 email. Distribution of package wanna-build Perl, PostgreSQL database (now), Berkeley DB (until recently). builds over build daemons buildd.debian.org Data exported on the Web, with an interface not suitable for massive retrieval. debbugs Perl, per-bug text files and mailbox Bug tracker bugs.debian.org Data exported on the Web; SOAP API available, but not suitable for massive retrieval. Management of developer Debian LDAP LDAP (accessible using standard LDAP tools and APIs), GnuPG keyrings. accounts keyring.debian.org Developers identity carnivore Perl, Berkeley DB. tracking (email addresses) History of packages upload — Mailing list archives. DEHS Upstream version tracking PHP, PostgreSQL database dehs.alioth.debian.org Perl, all results exported as a line-oriented text database, emails (to record the Package popularity popcon.debian.org submissions). Policy conformance check (a-la` continuous lintian.debian.org Perl, all results exported on the web as a line-oriented text database. integration) Package classification debtags C++, all data exported on the web as a line-oriented text database. Python, XSLT, per-package XML files. Package tracking system packages.qa.debian.org SOAP API available, but not suitable for massive retrieval. Web site www.debian.org WML (Website META Language), static HTML pages. in the context of Debian, a very large distribution currently II. THE DEBIAN DATA HELL formed by about 27,000 binary packages [7]. The task The difficulty of joining together different data sources, boils down to identify sub-standard quality packages which which has plagued the Debian project for several years, are in need of specific actions such as technical changes, is colloquially referred to as the Debian data hell. Before assignment to a new maintainer, or removal from the archive. analyzing UDD as a solution to that, we summarize here the Example 1: The authors, as members of the Debian QA factors that have caused the Debian data hell: team, often face the following question:2 • heterogeneity Which release critical bugs affect source pack- • community inertia ages in the testing suite, sorted by decreasing • long history package popularity? • maintainers’ programming and design skills The affected packages are in urgent need of attention, given • tight-coupling and service distribution how popular and at the same time how buggy they are. Discussing these factors highlights how the data hell cannot Implementing a monitor that periodically answers the above easily appear in distributions whose infrastructures are run question turns out to be surprisingly difficult in Debian, due by (wise) companies, and how it is likely to plague only to the amount of involved data sources (binary and source purely community-driven distributions. Among mainstream package metadata, bug tracker, suite status, popularity, . ) distributions, that boils down to Debian itself and Gentoo.3 and, more importantly, due to their heterogeneity. Heterogeneity: The basic cause of the Debian data hell This paper reports about the countermeasure that has been is of course heterogeneity. Even though the basic entities are adopted to such a difficulty—called the Ultimate Debian fairly clear albeit complex (packages, bugs, . ), the services Database (UDD)—and how it implements data integration dealing with them have been implemented according to for the purposes of both data mining and Quality Assurance. sharply different design choices. To give an idea of that, Paper structure: SectionII discusses the data integra- TableI shows the core parts of the Debian infrastructure tion problem in Debian and the peculiar factors which have summarizing, for each service, the main design choices in originated it, while Section III details the architecture of term of implementation language and data storage format: UDD. SectionIV gives an overview of the current status languages vary from system-level languages such as C to of UDD and some of its figures. Some applications are scripting languages (Shell, Perl, Python) and even XSLT, presented in SectionV, and a comparison with related work data formats vary from databases of all kinds (SQL, Berke- is made in SectionVI. leyDB, LDAP) to ad-hoc textual languages and even plain mailboxes(!). 2A few Debian terminology explanations are in order: release critical (RC) are those bugs whose severity makes a package unsuitable for release; 3Private communication with Gentoo developers has indeed confirmed testing is the suite meant to become the next stable release. that they suffer,
Load more

Recommended publications
  • Debian Developer's Reference Version 12.0, Released on 2021-09-01
    Debian Developer’s Reference Release 12.0 Developer’s Reference Team 2021-09-01 CONTENTS 1 Scope of This Document 3 2 Applying to Become a Member5 2.1 Getting started..............................................5 2.2 Debian mentors and sponsors......................................6 2.3 Registering as a Debian member.....................................6 3 Debian Developer's Duties 9 3.1 Package Maintainer's Duties.......................................9 3.1.1 Work towards the next stable release............................9 3.1.2 Maintain packages in stable .................................9 3.1.3 Manage release-critical bugs.................................. 10 3.1.4 Coordination with upstream developers............................ 10 3.2 Administrative Duties.......................................... 10 3.2.1 Maintaining your Debian information............................. 11 3.2.2 Maintaining your public key.................................. 11 3.2.3 Voting.............................................. 11 3.2.4 Going on vacation gracefully.................................. 12 3.2.5 Retiring............................................. 12 3.2.6 Returning after retirement................................... 13 4 Resources for Debian Members 15 4.1 Mailing lists............................................... 15 4.1.1 Basic rules for use....................................... 15 4.1.2 Core development mailing lists................................. 15 4.1.3 Special lists........................................... 16 4.1.4 Requesting new
    [Show full text]
  • Estudos Preliminares
    IGOR BESSA MENEZE PODER JUDICIÁRIO S JOSE MARIO VIANA JUSTIÇA DO TRABALHO BARBOSA JUNIOR LENIVIA TRIBUNAL REGIONAL DO TRABALHO DA 7ª REGIÃO DE CASTRO E SILVA MENDES FRANCISC O JONATHAN SECRETARIA DE TECNOLOGIA DA INFORMAÇÃO E COMUNICAÇÃO REBOUCAS MAIA Estudos Preliminares Contratação de Suporte Técnico, incluindo atualizações evolutivas e corretivas, para a ferramenta Atlassian Jira e Plugins eazyBI Reports and Charts e Git Integration. Estudos Preliminares - Contratação de Suporte Técnico, incluindo atualizações evolutivas e corretivas, para a ferramenta Atlassian Jira e Plugins eazyBI Reports and Charts e Git Integration. 1 PODER JUDICIÁRIO JUSTIÇA DO TRABALHO TRIBUNAL REGIONAL DO TRABALHO DA 7ª REGIÃO SECRETARIA DE TECNOLOGIA DA INFORMAÇÃO E COMUNICAÇÃO Sumário ANÁLISE DE VIABILIDADE DA CONTRATAÇÃO (Art.14) 4 Contextualização 4 Definição e Especificação dos Requisitos da Demanda (Art. 14, I) 5 Requisitos de Negócio 5 Requisitos Técnicos 6 Requisitos Temporais 6 Soluções Disponíveis no Mercado de TIC (Art. 14, I, a) 7 Contratações Públicas Similares (Art. 14, I, b) 10 Outras Soluções Disponíveis (Art. 14, II, a) 11 Portal do Software Público Brasileiro (Art. 14, II, b) 11 Alternativa no Mercado de TIC (Art. 14, II, c) 12 Modelo Nacional de Interoperabilidade – MNI (Art. 14, II, d) 12 Infraestrutura de Chaves Públicas Brasileira – ICP-Brasil (Art. 14, II, e) 12 Modelo de Requisitos Moreq-Jus (Art. 14, II, f) 12 Análise Comparativa dos Custos das Soluções (Art. 14, III) 12 Escolha e Justificativa da Solução (Art. 14, IV) 15 Descrição da Solução (Art. 14, IV,a) 21 Alinhamento da Solução (Art. 14, IV, b) 22 Benefícios Esperados (Art. 14, IV, c) 22 Relação entre a Demanda Prevista e a Contratada (Art.
    [Show full text]
  • Name Synopsis Description Options
    reportbug(1) General Commands Manual reportbug(1) NAME reportbug − reports a bug to a debbugs server SYNOPSIS reportbug [options] <package | pseudo-package | absolute-pathname> DESCRIPTION reportbug is primarily designed to report bugs in the Debian distribution; by default, it creates an email to the Debian bug tracking system at [email protected] with information about the bug you’ve found, and makes a carbon copyofthe report for you as well. Using the −−bts option, you can also report bugs to other servers that use the Debian bug tracking system, debbugs. Youmay specify either a package name or a filename; if you use a filename, it must either be an absolute filename (so beginning with a /)orifyou want reportbug to search the system for a filename, see the −−filename and −−path options below. Ifinstalled, also dlocate is used to identify the filename location and thus the package containing it. Youcan also specify a pseudo-package;these are used in the Debian bug tracking system to track issues that are not related to one specific package. Run reportbug without anyarguments, then enter other at the package prompt, to see a list of the most commonly-used pseudo-packages. OPTIONS The program follows the usual GNU command line syntax, with long options starting with twodashes (‘−−’). A summary of options are included below. −h, −−help Showsummary of options. −−version Showthe version of reportbug and exit. −A FILENAME, −−attach=FILENAME Attach a file to the bug report; both text and binary files are acceptable; this option can be specified multiple times to attach several files.
    [Show full text]
  • On the Evolution of Source Code and Software Defects
    On the Evolution of Source Code and Software Defects Doctoral Dissertation submitted to the Faculty of Informatics of the Università della Svizzera Italiana in partial fulfillment of the requirements for the degree of Doctor of Philosophy presented by Marco D’Ambros under the supervision of Prof. Dr. Michele Lanza October 2010 Dissertation Committee Prof. Dr. Carlo Ghezzi Politecnico di Milano, Italy Prof. Dr. Cesare Pautasso Università della Svizzera Italiana, Switzerland Prof. Dr. Harald C. Gall University of Zurich, Switzerland Prof. Dr. Hausi A. Müller University of Victoria, Canada Dissertation accepted on 19 October 2010 Prof. Dr. Michele Lanza Research Advisor Università della Svizzera Italiana, Switzerland Prof. Dr. Michele Lanza PhD Program Director i I certify that except where due acknowledgement has been given, the work presented in this thesis is that of the author alone; the work has not been submitted previously, in whole or in part, to qualify for any other academic award; and the content of the thesis is the result of work which has been carried out since the official commencement date of the approved research pro- gram. Marco D’Ambros Lugano, 19 October 2010 ii To Anna iii iv Abstract Software systems are subject to continuous changes to adapt to new and changing requirements. This phenomenon, known as software evolution, leads in the long term to software aging: The size and the complexity of systems increase, while their quality decreases. In this context, it is no wonder that software maintenance claims the most part of a software system’s cost. The analysis of software evolution helps practitioners deal with the negative effects of software aging.
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • Primera Fase Del Proyecto De Creación De Una Herramienta De Ticketing Web Ibermática Multi-Cliente Y Parametrizable
    Máster en Software Libre Trabajo Final de Máster Creación Plan de Proyecto herramienta de ticketing Análisis Comparativo Autor: Juan A. de Haro / [email protected] Tutor de prácticas: Corinne Dufraisse / [email protected] Responsable técnico Ibermática: Xavier Tejero / [email protected] Creación Plan de Proyecto herramienta de ticketing. Análisis comparativo. Índice de contenidos 1.- Estudio de viabilidad.......................................................................................................................4 1.1 Alcance del proyecto de Creación plan de proyecto herramienta de ticketing .........................4 1.2 Estudio de la situación actual.....................................................................................................5 1.3 Definición de requisitos del sistema..........................................................................................5 1.3.1 Requerimientos..................................................................................................................6 1.3.2 Funcionalidades.................................................................................................................6 1.3.3 Arquitectura........................................................................................................................8 1.3.4 Perfiles de usuarios............................................................................................................9 1.3.5 Información de tareas.......................................................................................................11
    [Show full text]
  • Producing Open Source Software How to Run a Successful Free Software Project
    Producing Open Source Software How to Run a Successful Free Software Project Karl Fogel Producing Open Source Software: How to Run a Successful Free Software Project by Karl Fogel Copyright © 2005-2013 Karl Fogel, under a CreativeCommons Attribution-ShareAlike (3.0) license [http:// creativecommons.org/licenses/by/3.0/]. Dedication This book is dedicated to two dear friends without whom it would not have been possible: Karen Underhill and Jim Blandy. i Table of Contents Preface ............................................................................................................................ vi Why Write This Book? .............................................................................................. vi Who Should Read This Book? ..................................................................................... vi Sources ................................................................................................................... vii Acknowledgments .................................................................................................... viii Disclaimer ................................................................................................................ ix 1. Introduction ................................................................................................................... 1 History ..................................................................................................................... 3 The Rise of Proprietary Software and Free Software ................................................
    [Show full text]
  • Software Reliability Analysis Via Data Mining of Bug Reports
    BUGMINER: Software Reliability Analysis Via Data Mining of Bug Reports Leon Wu Boyi Xie Gail Kaiser Rebecca Passonneau Department of Computer Science Columbia University New York, NY 10027 USA fleon,xie,kaiser,[email protected] Abstract formation that could be used to improve the quality of the bug reporting, reduce the cost of quality assurance, analyze Software bugs reported by human users and automatic software reliability, and predict future bug report trend. One error reporting software are often stored in some bug track- of the challenges in bug reporting is that the bug reports are ing tools (e.g., Bugzilla and Debbugs). These accumulated often incomplete (e.g., missing data fields such as product bug reports may contain valuable information that could version or operating system details). Another challenge is be used to improve the quality of the bug reporting, reduce that there are often many duplicate bug reports for the same the quality assurance effort and cost, analyze software re- bug. Software developers or testers normally have to re- liability, and predict future bug report trend. In this paper, view these redundant bug reports manually, which is time- we present BUGMINER, a tool that is able to derive useful consuming and cost inefficient. information from historic bug report database using data We developed a tool named BUGMINER that is able to mining, use these information to do completion check and derive useful information from historic bug reports using redundancy check on a new or given bug report, and to es- data mining techniques, including machine learning (e.g., timate the bug report trend using statistical analysis.
    [Show full text]
  • GNU Guix Reference Manual Using the GNU Guix Functional Package Manager
    GNU Guix Reference Manual Using the GNU Guix Functional Package Manager The GNU Guix Developers Edition 34cf1f4 29 September 2021 Copyright c 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021 Ludovic Court`es Copyright c 2013, 2014, 2016 Andreas Enge Copyright c 2013 Nikita Karetnikov Copyright c 2014, 2015, 2016 Alex Kost Copyright c 2015, 2016 Mathieu Lirzin Copyright c 2014 Pierre-Antoine Rault Copyright c 2015 Taylan Ulrich Bayırlı/Kammer Copyright c 2015, 2016, 2017, 2019, 2020, 2021 Leo Famulari Copyright c 2015, 2016, 2017, 2018, 2019, 2020 Ricardo Wurmus Copyright c 2016 Ben Woodcroft Copyright c 2016, 2017, 2018, 2021 Chris Marusich Copyright c 2016, 2017, 2018, 2019, 2020, 2021 Efraim Flashner Copyright c 2016 John Darrington Copyright c 2016, 2017 Nikita Gillmann Copyright c 2016, 2017, 2018, 2019, 2020 Jan Nieuwenhuizen Copyright c 2016, 2017, 2018, 2019, 2020, 2021 Julien Lepiller Copyright c 2016 Alex ter Weele Copyright c 2016, 2017, 2018, 2019, 2020, 2021 Christopher Baines Copyright c 2017, 2018, 2019 Cl´ement Lassieur Copyright c 2017, 2018, 2020, 2021 Mathieu Othacehe Copyright c 2017 Federico Beffa Copyright c 2017, 2018 Carlo Zancanaro Copyright c 2017 Thomas Danckaert Copyright c 2017 humanitiesNerd Copyright c 2017, 2021 Christine Lemmer-Webber Copyright c 2017, 2018, 2019, 2020, 2021 Marius Bakke Copyright c 2017, 2019, 2020 Hartmut Goebel Copyright c 2017, 2019, 2020, 2021 Maxim Cournoyer Copyright c 2017, 2018, 2019, 2020, 2021 Tobias Geerinckx-Rice Copyright c 2017 George Clemmer Copyright c 2017 Andy Wingo Copyright c 2017, 2018, 2019, 2020 Arun Isaac Copyright c 2017 nee Copyright c 2018 Rutger Helling Copyright c 2018, 2021 Oleg Pykhalov Copyright c 2018 Mike Gerwitz Copyright c 2018 Pierre-Antoine Rouby Copyright c 2018, 2019 G´abor Boskovits Copyright c 2018, 2019, 2020 Florian Pelz Copyright c 2018 Laura Lazzati Copyright c 2018 Alex Vong Copyright c 2019 Josh Holland Copyright c 2019, 2020 Diego Nicola Barbato Copyright c 2019 Ivan Petkov Copyright c 2019 Jakob L.
    [Show full text]
  • GNU Hyperbole Manual
    GNU Hyperbole Manual The Everyday Hypertextual Information Manager Bob Weiner This manual is for GNU Hyperbole (Edition 7.1.3, Published August, 2020). Copyright c 1989-2020 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation. GNU Hyperbole sofware is distributed under the terms of the GNU General Public License version 3 or later, as published by the Free Software Foundation, Inc. GNU Hyperbole is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY, without even the implied warranty of MERCHANTABIL- ITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details in the file, \COPYING", within the Hyperbole package directory. Published by the Free Software Foundation, Inc. Author: Bob Weiner E-mail: <[email protected]> (This is a mail list). Web: www.gnu.org/software/hyperbole The body of the manual was written in Emacs and laid out using the GNU Texinfo markup language. i Short Contents GNU Hyperbole :::::::::::::::::::::::::::::::::::::::::: 1 1 Introduction :::::::::::::::::::::::::::::::::::::::::: 2 2 Smart Keys :::::::::::::::::::::::::::::::::::::::::: 7 3 Buttons :::::::::::::::::::::::::::::::::::::::::::: 18 4 Menus:::::::::::::::::::::::::::::::::::::::::::::: 38 5 HyControl :::::::::::::::::::::::::::::::::::::::::: 42 6 Koutliner ::::::::::::::::::::::::::::::::::::::::::: 47 7 HyRolo :::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • How Can Academic Software Research and Open Source Software Development Help Each Other?
    How can Academic Software Research and Open Source Software Development help each other? Vamshi Ambati S P Kishore Institute for Software Research International Language Technologies Institute Carnegie Mellon University Carnegie Mellon University [email protected] [email protected] Abstract propose that issues in academic research can be solved by adopting some of the practices and tools In this paper we discuss a few issues faced in from OSSD. We also discuss few issues in OSSD coordinating, managing and implementing academic like the gap between the developer and non- software research projects and suggest how some of developer communities and try to address some of these issues can be addressed by adopting tools and them by adopting practices from academic software processes form Open Source Software Development. research. At the same time we also discuss how a few issues in Open Source Software Development (OSSD) projects The next few sections are organized as follows. can be addressed by adopting processes from Section 2 discusses few characteristics and issues Academic Research. that crop up in Academic Software Research. In section 3 we discuss Open Source Software development as an emerging paradigm in Software 1. Introduction Engineering and the issues faced by OSSD. Section 4 suggests tools and processes that can be adopted by Academic Software research has made substantive Academic Research while section 5 discusses how contributions in varying degrees for the growth of OSSD can benefit from processes adopted from Software and Technology in diverse areas like data Academic Software Research. Finally we conclude mining, bioinformatics, astronomy, natural language by suggesting some tools that are needed for the processing, medicine and others.
    [Show full text]
  • Debian Talk, Serenity Theme
    Help the kernel team to help you Ben Hutchings <[email protected]> Mini-DebConf Hamburg 20th May 2018 The kernel team is busy ● The Linux kernel is big, and changes quickly ● We get a lot of bug reports, and a lot of feature requests ● We don't have time to handle all of them—sorry! Report bugs upstream If you run a recent kernel (stable-backports, testing, unstable, or experimental), upstream developers want your bug reports. ● Some kernel subsystems use a bug tracking system (usually bugzilla.kernel.org) ● Others only use their mailing list, and ignore Bugzilla ● MAINTAINERS file (in Debian linux-doc package) lists the mailing list (L:) and bug tracker (B:) for each subsystem ● Use the debbugs “forwarded” command to link the upstream bug report to a Debian bug report Report bugs with the right information ● Our kernel packages include scripts for the reportbug command to gather diagnostic information ● We want to see this information with (almost) every bug report ● If the bug is in the currently running kernel, run: reportbug kernel ● Otherwise, report it against the ABI-versioned linux-image package, e.g. reportbug linux-image-4.9.0-6-amd64 ● Not a metapackage—the kernel is not in linux-image-amd64, nor is the bug ● Not a firmware package—the iwlwifi driver is not in firmware-iwlwifi, nor is the bug Add features upstream We have some long-standing patches to the kernel, but we don't want to add more. ● New features should always be submitted upstream ● Read the docs first: www.kernel.org/doc/html/latest/process/ ● We're happy to apply patches once they're accepted upstream—because we know they are only temporary ● Please help to get some of the long-standing patches upstream Tell us what the fix is Upstream bug fixes sometimes don't get into a release for months.
    [Show full text]