DOCSLIB.ORG

Bugs Tracking at a Large Scale in the FLOSS Ecosystem - FOSSA 2010

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Bugs Tracking at a Large Scale in the FLOSS Ecosystem - FOSSA 2010 Bugs tracking at a large scale in the FLOSS ecosystem - FOSSA 2010 Olivier Berger, Telecom SudParis Bugs tracking at a large scale in the FLOSS Introduction ecosystem - FOSSA 2010 Purpose Foreword About HELIOS Tracking bug Olivier Berger, Telecom SudParis reports Goals Existing tools Problems Solutions Tuesday 09/11/2010 Bugs tracking at a large scale in Large scale bugtracking the FLOSS ecosystem - Denition : bugtracking FOSSA 2010 Olivier Berger, Telecom SudParis Introduction Purpose Foreword About HELIOS NO : Looking for bugs in the code / programs Tracking bug reports Goals YES : Looking for bug reports for these bugs Existing tools Problems Solutions Bugs tracking at a large scale in Context : FLOSS ecosystem the FLOSS ecosystem - FOSSA 2010 Olivier Berger, Telecom SudParis Introduction Purpose Foreword About HELIOS Lots of duplicate or related bugs Tracking bug reports Not a single place where to monitor bugs Goals Existing tools Problems Solutions Bugs tracking at a large scale in Who I am the FLOSS ecosystem - FOSSA 2010 Institut TELECOM / TELECOM SudParis / Olivier Berger, Computer Science dept. / PFTCR/FOCS2 Telecom team SudParis 2 perm. sta Christian BAC and myself Introduction 2 PhD students Purpose Foreword 2 non permanent research engineers About HELIOS Research on collaborative development Tracking bug reports platforms, tools, process, in FLOSS Goals communities Existing tools Problems Solutions Previously worked in service companies (Cap Gemini, IDEALX) At TELECOM SudParis since 2002 R&D on FLOSS, forges, bugtracking, Linked Data, etc. (CALIBRE, HELIOS, COCLICO) Contributor to Debian, FusionForge, Mantis Bugs tracking at a large scale in About HELIOS the FLOSS ecosystem - FOSSA 2010 Olivier Berger, Telecom SudParis Introduction Purpose Foreword About HELIOS Tracking bug reports Goals Existing tools http://heliosplatform.sourceforge.net/ Problems Solutions Application Lifecycle Management with Open Source tools Bugs tracking at a large scale in About HELIOS the FLOSS ecosystem - Funding programme FOSSA 2010 Olivier Berger, Telecom SudParis French collaborative R&D cluster programmes Introduction System@tic Paris Region Purpose Foreword About HELIOS Tracking bug reports Goals Public funding (partial) Existing tools Problems Solutions 2 years (2008-2010) (over now) Partners : Alcatel-Lucent, Artenum, Institut TELECOM / TELECOM & Management SudParis, Kalis, Mandriva, Thales Bugs tracking at a large scale in Specic Goals on Helios WP3 the FLOSS ecosystem - FOSSA 2010 Olivier Berger, Telecom Help developers, maintainers, power users SudParis Monitoring work done around particular issues Introduction Purpose Not one single distribution channel Foreword About HELIOS Many venues for support : many distributions, many Tracking bug bugtrackers reports Goals Existing tools Redundancy of reports across trackers Problems Solutions Final goal : ease of monitoring bug links all over the Open Source ecosystem Application to Internal bugtracker (integrators) monitoring 3rd parties (OSS projects) bugs Bugs tracking at a large scale in Existing tools : bts-link the FLOSS ecosystem - FOSSA 2010 http://bts-link.alioth.debian.org/ Olivier Berger, Telecom Bts-link : monitoring bug status change around the Debian SudParis bugtracker Introduction Purpose Debian tool for package maintainers Foreword About Uses existing bug links (forwarded-to) set by humans : HELIOS Tracking bug Distribution (Debian) package bugs reports Upstream project bugtrackers bugs Goals Existing tools Problems Monitoring status changes on upstream bugs Solutions Email notication for Debian packagers (or people monitoring Debian bugs) Supports lots of upstream bugtracker types (through specic connectors) : bugzilla (and issuezilla), gnats, launchpad, mantis, savane (from savanah), sourceforge trackers, trac, gforge (and fusionforge most probably), google code Bugs tracking at a large scale in Issues with tools like bts-link the FLOSS ecosystem - FOSSA 2010 Olivier Berger, Telecom SudParis At the moment works only over debbugs Introduction Purpose Needs custom ad-hoc connectors/scrapers for each Foreword About HELIOS bugtracker : no standard APIs Tracking bug reports Make it more generic and not Debian specic : Goals Existing tools Either : Problems Solutions custom bugtracker data gatherer or standard for bugtracker data interchange : none yet Bugs tracking at a large scale in Problems : interop / the FLOSS ecosystem - FOSSA 2010 standardisation (lack of -) Olivier Berger, Telecom SudParis Introduction Purpose Foreword About HELIOS Tracking bug Until recently, no real standard for bugtracker APIs reports Goals Interchange of data representing Bugs/Issues Existing tools Problems Solutions Bugs tracking at a large scale in Past eorts : our Helios ontology the FLOSS ecosystem - FOSSA 2010 Olivier Berger, Telecom SudParis Bug/Issue representation Introduction Purpose Ontology, Schema (Semantik Web standards) Foreword About Standard proposed and community build : baetle HELIOS Tracking bug http ://code.google.com/p/baetle/ reports Goals Reuse of EvoOnt BOM http ://www.i.uzh.ch/ddis/evo/ Existing tools Problems Semantic web techniques (RDF) : extensible Solutions Mapping bugtrackers data to RDF/Linked Data : prototype on UDD, bugzilla, etc. (D2R) Bugs tracking at a large scale in Our rst result the FLOSS ecosystem - FOSSA 2010 http://heliosplatform.sourceforge.net/ontologies/ Olivier helios_bt.html Berger, Telecom SudParis Introduction Purpose Foreword About HELIOS Tracking bug reports Goals Existing tools Problems Solutions Bugs tracking at a large scale in OSLC-CM : a proposed standard the FLOSS ecosystem - FOSSA 2010 for bugtracker interoperability Olivier Berger, OSLC (Open Services for Lifecycle Collaboration) proposed Telecom SudParis standard Web technology : REST, RDF, AJAX, Introduction Purpose Open community, Open standard Foreword About OSLC-CM (Change Management) FLOSS implementations HELIOS developped in Helios and COCLICO Tracking bug reports Mantis bugtracker Goals Existing tools FusionForge trackers (soon Codendi too) Problems Solutions Many more domains than trackers WebID, aka FOAF+SSL OAuth Building grounds for forge interop standard to be elaborated at PlanetForge community as part of the COCLICO project Bugs tracking at a large scale in Demo of our OSLC-CM Add-on for the FLOSS ecosystem - FOSSA 2010 Mantis Olivier Berger, Telecom SudParis Introduction Purpose Foreword About HELIOS Tracking bug https://picoforge.int-evry.fr/cgi-bin/twiki/view/ reports Goals Oslc/Web/MantisOslcServer Existing tools Problems Solutions Bugs tracking at a large scale in SemWeb / Linked-Data the FLOSS ecosystem - FOSSA 2010 Olivier Berger, Telecom SudParis Introduction Semantic Web and Linked Data hype Purpose Foreword Linked (Open ?) Data About HELIOS Tracking bug http://linkeddata.org/ reports Goals Existing tools Problems Solutions Bugs (reports) become rst class citizens of the SemWeb (RDFa, adapters, OSLC-CM. ) Bugs tracking at a large scale in Linked Open Data the FLOSS ecosystem - (Public) Development artifacts part of Web 3.0 ? FOSSA 2010 Olivier Berger, Telecom SudParis Introduction Purpose Foreword About HELIOS Tracking bug reports Goals Existing tools Problems Solutions Source : http ://linkeddata.org/ Bugs tracking at a large scale in Perspectives the FLOSS ecosystem - FOSSA 2010 Olivier Berger, Telecom SudParis Introduction Purpose Foreword SD (Simple Deects) : Distributed bugtracker About HELIOS Semantic desktop integration (Nepomuk, . ) Tracking bug reports Goals fetchbugs4.me someday (web app to monitor one's bug Existing tools Problems reports) Solutions Bugs tracking at a large scale in Bibliography the FLOSS ecosystem - FOSSA 2010 Olivier Berger, Telecom SudParis Introduction Purpose O. Berger, V. Vlasceanu, C. Bac, S. Lauriere, Q. V. Dang, Foreword About HELIOS Weaving a Semantic Web across OSS repositories : Tracking bug unleashing a new potential for academia and practice, in reports Goals International Journal of Open Source Software & Processes Existing tools Problems (IJOSSP), Volume 2, Issue 2 (2010) Solutions Bugs tracking at a large scale in Copyright & License the FLOSS ecosystem - FOSSA 2010 Olivier Berger, Telecom SudParis Introduction Purpose Foreword This presentation is under CC-by-SA license About HELIOS Tracking bug Copyright (c) 2010 Olivier Berger reports Goals Made with org-mode under emacs (org + beamer) Existing tools Problems Solutions Bugs tracking at a large scale in Q&A the FLOSS ecosystem - FOSSA 2010 Olivier Berger, Telecom SudParis Introduction Thank you Purpose Questions ? Foreword About HELIOS Tracking bug reports More Goals @oberger : http://identi.ca/oberger/ Existing tools Problems email : mailto:[email protected] Solutions blog : http://www-public.it-sudparis.eu/~berger_o/weblog/.
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]
  • Code Distribution Process - Definition of Evaluation Metrics
    Code Distribution Process - Definition of Evaluation Metrics Project Acronym Edos Project Full Title Environment for the Development and Distribution of Open Source Software Project # FP6-IST-004312 Contact Author Radu POP, [email protected] Authors List Ciaran Bryce, Michel Pawlak, Michel Deriaz - Universite de Geneve Serge Abiteboul, Boris Vrdoljak - INRIA Gemo Project Tova Milo, Assaf Sagi - Tel-Aviv University Stephane Lauriere, Florent Villard, Radu POP - MandrakeSoft Workpackage # WP 4 Deliverable # 1 Document Type Report Version 1.0 Date March 22, 2005 Distribution Consortium, Commission and Reviewers. Chapter 1 Introduction This document proposes a measurement and evaluation methodology and defines the metrics that we consider as important in EDOS for the code distribution process for Free and Open Source Software (F/OSS). Our aim in attempting to define the metrics is the following: Clarify our understanding of the F/OSS code distribution process, and • subsequently to help identify areas for improvement. Enumerate what needs to be measured in the F/OSS code distribution • process. The purpose of measurement and evaluation is to compare different architectures for code distribution the existing one and those that will be proposed in the EDOS project. Measurement and evaluation have been facets of software engineering for some time. ISO (the International Organisation for Standardisation) and IEC (the International Electrotechnical Commision) have established a joint technical committee for worldwide standardization in the field of information technology. They have developed a set of standards for software product quality relating to the definition of quality models (the 9126 series) and to the evaluation process (the 14598 series). A quality model defines the characteristics of a system to be measured and the metrics that evaluate how the system to be measured performs with respect to these characteristics.
    [Show full text]
  • A Case Study on Software Vulnerability Coordination
    A Case Study on Software Vulnerability Coordination Jukka Ruohonena,∗, Sampsa Rautia, Sami Hyrynsalmia,b, Ville Lepp¨anena aDepartment of Future Technologies, University of Turku, FI-20014 Turun yliopisto, Finland bPori Department, Tampere University of Technology, P.O. Box 300, FI-28101 Pori, Finland Abstract Context: Coordination is a fundamental tenet of software engineering. Coordination is required also for identifying discovered and disclosed software vulnerabilities with Common Vulnerabilities and Exposures (CVEs). Motivated by recent practical challenges, this paper examines the coordination of CVEs for open source projects through a public mailing list. Objective:The paper observes the historical time delays between the assignment of CVEs on a mailing list and the later appearance of these in the National Vulnerability Database (NVD). Drawing from research on software engineering coordination, software vulnerabilities, and bug tracking, the delays are modeled through three dimensions: social networks and communication practices, tracking infrastructures, and the technical characteristics of the CVEs coordinated. Method: Given a period between 2008 and 2016, a sample of over five thousand CVEs is used to model the delays with nearly fifty explanatory metrics. Regression analysis is used for the modeling. Results: The results show that the CVE coordination delays are affected by different abstractions for noise and prerequisite constraints. These abstractions convey effects from the social network and infrastructure dimensions. Particularly strong effect sizes are observed for annual and monthly control metrics, a control metric for weekends, the degrees of the nodes in the CVE coordination networks, and the number of references given in NVD for the CVEs archived. Smaller but visible effects are present for metrics measuring the entropy of the emails exchanged, traces to bug tracking systems, and other related aspects.
    [Show full text]
  • GNAT User's Guide
    GNAT User's Guide GNAT, The GNU Ada Compiler For gcc version 4.7.4 (GCC) AdaCore Copyright c 1995-2009 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; with no Invariant Sections, with no Front-Cover Texts and with no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". About This Guide 1 About This Guide This guide describes the use of GNAT, a compiler and software development toolset for the full Ada programming language. It documents the features of the compiler and tools, and explains how to use them to build Ada applications. GNAT implements Ada 95 and Ada 2005, and it may also be invoked in Ada 83 compat- ibility mode. By default, GNAT assumes Ada 2005, but you can override with a compiler switch (see Section 3.2.9 [Compiling Different Versions of Ada], page 78) to explicitly specify the language version. Throughout this manual, references to \Ada" without a year suffix apply to both the Ada 95 and Ada 2005 versions of the language. What This Guide Contains This guide contains the following chapters: • Chapter 1 [Getting Started with GNAT], page 5, describes how to get started compiling and running Ada programs with the GNAT Ada programming environment. • Chapter 2 [The GNAT Compilation Model], page 13, describes the compilation model used by GNAT. • Chapter 3 [Compiling Using gcc], page 41, describes how to compile Ada programs with gcc, the Ada compiler.
    [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]
  • Bug Tracker Net Documentation
    Bug Tracker Net Documentation Piscatorial and platelike Jean-Pierre backwash rigorously and immerge his pup pausingly and qualmishly. Glaucescent and nicotinic Sayers meditates anachronistically and reregulating his Bruges redolently and unemotionally. Jurassic Miguel befool whitely while Stevie always dedicating his squeezers marauds unthankfully, he miring so monumentally. The targeted project issue date. The predefined values should put left alone. Default user preference to enable filtering based on issue severity. Your comment has been received. Mantis Bug Tracker REST API Postman. It might been released, settings, you create and wade a script. NET Framework XML classes to steep and manipulate the data assess them. Compare to other products or configurations, take their moment to browse these introductory docs. Try upgrading to the latest stable version. The consider of filter fields to buy per row. We erect not, schedules, an object will be flagged. Alternatively, hence, we to submit a report back soon please report cannot be displayed on to main window. Automate data source between Sheets and Tracker. NET, remainder of the bugs are readable, their description etc in the cemetery of reports from time start time. It will no longer if possible login using this account. Then what problem behavior be solved more promptly. Someone hijacked my Google account. Kanban board for visualizing your project timeline. Default value list ON. The default value somewhere ON. Google users are affected. Specifies the LDAP or Active Directory server to key to. You can afford click the Updated column heading to which most recently updated issues at our top along the search results.
    [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]
  • Software Development and Maintenance
    Software Development, Maintenance, Releases and Tech Transfer Presenters: Bill Oakley and David Neumann 2013 RiverWare User Group Meeting August 27, 2013 Software Development Team • Professional software engineers • Continuity and institutional knowledge • Variety of complimentary backgrounds • Professional water resource engineers • Engineering methods • User support • Professional support staff • Software configuration management (licensing, releases) • Hardware maintenance August 27-28, 2013 2013 RiverWare User Group Meeting 2 Software Development Process • Our goal is to deliver professional quality software applications which meet our users’ needs: • Requirements analysis • Requirements document • High level design document • Estimates • Other documents as appropriate • Document reviews August 27-28, 2013 2013 RiverWare User Group Meeting 3 Software Development Process • Implementation • Write code • Unit test (may include writing test code) • Peer code review (correctness, efficiency, coding standard conformance, readability, maintainability), • Integration testing (including regression tests, memory analysis) August 27-28, 2013 2013 RiverWare User Group Meeting 4 Software Maintenance • Bug fixing • Critical bugs fixed for next patch release • Non-critical bugs deferred to next major release • Before major release thorough review of bug list to identify bugs to fix for release • RiverWare development requires many software packages: • Applications or libraries • Commercial • Open Source • Home Grown (Java, Perl, Python, Tcl/Tk) August
    [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]
  • RTEMS Development Roadmap
    OAR RTEMS Roadmap 2012 Joel Sherrill, Ph.D. OAR Corporation September 2012 OAR RTEMS in a Nutshell • RTEMS is an embedded real-time O/S – deterministic performance and resource usage • RTEMS is free software – no restrictions or obligations placed on fielded applications • Supports open standards like POSIX • Available for 15+ CPU families and 150+ BSPs • Training and support services available http://www.rtems.org 2 OAR RTEMS Applications BMW Superbike Avenger Curiosity Solar Dynamics Observatory ARTEMIS Galileo IOV DAWN MRO/Electra Milkymist Avenger Planck TECHNIC 1 LISA ST-5 Pathfinder Proba-2 Herschel http://www.rtems.org Images Credit: NASA and ESA 3 OAR Outline of Remainder • Community Driven Focus • Development Activities • Wish List for Future Improvements • Active Release Branch Updates • OAR Support Subscriptions & Legacy Releases • Conclusion http://www.rtems.org 4 OAR Community Driven Focus • Without users, project has no reason to exist! • Users drive requirements – Please let us know what you need • Users provide or fund many improvements – Again those reflect your requirements • Most bug reports are from users RTEMS Evolves to Meet Your Needs http://www.rtems.org 5 RTEMS Project Participation In OAR Student Programs • Google Summer of Code (2008-2012) – Almost 40 students over the five years • Google Code-In (2010-2011) – High school students did ~200 tasks for RTEMS – Included only twenty FOSS projects • ESA Summer of Code In Space (2011-2012) – Small program with only twenty FOSS projects involved http://www.rtems.org
    [Show full text]