DOCSLIB.ORG

Hermano José Marques Cintra.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Hermano José Marques Cintra.Pdf PONTIFÍCIA UNIVERSIDADE CATÓLICA DE SÃO PAULO PROGRAMA DE PÓS-GRADUAÇÃO EM TECNOLOGIAS DA INTELIGÊNCIA E DESIGN DIGITAL HERMANO JOSÉ MARQUES CINTRA A NOVA POTÊNCIA DA COOPERAÇÃO: efeitos da interatividade digital na ação coletiva empreendedora São Paulo - SP 2016 HERMANO JOSÉ MARQUES CINTRA A NOVA POTÊNCIA DA COOPERAÇÃO: efeitos da interatividade digital na ação coletiva empreendedora Tese apresentada à Banca Examinadora da Pontifícia Universidade Católica de São Paulo, exigência parcial para obtenção do título de Doutor em Tecnologias da Inteligência e Design Digital. Área de concentração: processos cognitivos e ambientes digitais Orientador: Profa. Dra. Maria Lucia Santaella Braga. São Paulo – SP 2016 ERRATA CINTRA, H J M. A Nova Potência da Cooperação: efeitos da interatividade digital na ação coletiva empreendedora. (Tese de Doutorado) Pontifícia Universidade Católica de São Paulo - Programa de Tecnologias da Inteligência e Design Digital, 2016. Folha (página) Linha Onde se lê: Leia-se: 19 (s/n) 4 <http://www.hcintra.com.br/linksdoutorado> <http://www.hcintra.com/linksdoutorado> 385 (355) 4 <http://www.hcintra.com.br/biBliodoutorado> <http://www.hcintra.com/biBliodoutorado> (Os endereços não possuem a terminação “.br”) Autorização de Publicação Autorizo a reprodução total ou parcial desta tese por processos de fotocópia ou eletrônicos para fins acadêmicos, científicos e educacionais, desde que citada a fonte. São Paulo, 28 de junho de 2016 Convite ao diáloGo O trabalho aqui apresentado procura entender a cooperação em ambiente digitais, portanto, não poderiam faltar meus localizadores digitais e meu convite à discussão dos temas abordados: Email: hcintra (em) hotmail.com Skype: hermano (ponto) cintra Site: www.hcintra.com Folha de Assinaturas da Banca Examinadora Profa. Dra.: Maria Lucia Santaella Braga (orientadora) Prof. Dr.: Prof. Dr.: Prof. Dr.: Prof. Dr.: À memória de meu pai, um homem bom, justo e sábio. Registro meu agradecimento à Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (Capes), fundação do Ministério da Educação (MEC) do Governo Federal do Brasil, por haver me agraciado com uma bolsa de estudos integral no âmbito do Programa de Suporte à Pós-Graduação de Instituições de Ensino Particulares (PROSUP) no período de 2013 a 2015. AgradeCimentos Acima de tudo e de todos, agradeço mil vezes à minha querida esposa, Satomi Nanba. Esta tese não teria sido possível sem sua constante parceria, paciência e estímulo. Seu companheirismo foi inabalável nos momentos mais difíceis, de desalento, desespero e cansaço. Também agradeço a paciência e o carinho de meus filhos, Thomas e Sophia. Não foi fácil aguentar o pai ensandecido nesses últimos meses. O amor dos três foi o combustível essencial da jornada. Agradeço à minha orientadora, Lucia Santaella, pelo aprendizado contínuo dentro e fora da sala de aula. Fui inspirado por sua paixão pelos ideais, pelo rigor de seu pensamento, pela generosidade do diálogo franco, realizado à maneira dos pares, muito embora sua elevada estatura intelectual e experiência. Devo a ela boa parte da sustentação teórica deste texto. Por seu intermédio, tive acesso à fenomenologia do grande filósofo americano Charles Sanders Peirce, que tomou papel de suma importância na articulação de meu pensamento. Além disso, sob sua liderança, tive diversas oportunidades adicionais de pesquisa, especialmente nas investigações conduzidas no Grupo de Pesquisa Sociotramas, que, inclusive, materializaram-se na forma de um capítulo sobre a fluência digital em livro por ela organizado. A gratidão faz-se ainda mais intensa em função de sua plena confiança face a meus esforços, apesar dos atrasos constantes de minhas entregas. Agradeço aos professores do Programa de Pós-Graduação em Tecnologias da Inteligência e Design Digital. Foram bons cursos, diversos seminários e palestras enriquecedoras. Agradeço, especialmente, ao professor Nelson Brissac pela oportunidade de contribuir com os meus conhecimentos profissionais para seu fantástico projeto ZL Vórtice. Agradeço aos membros da banca de qualificação, professores Demi Getschko e Rogério da Costa (com quem já tenho longa dívida de gratidão pela orientação de meu mestrado), por seus conselhos e incentivo. Agradeço aos colegas do Sociotramas. A troca de conhecimento no grupo foi, além de estimulante, habitualmente prazerosa. Também tenho dívida de gratidão com diversos colegas de trabalho ao longo da vida profissional, aprendi com eles mais do que imaginam. Particularmente, preciso agradecer a meu velho amigo Francisco Yonamine, sem o qual a pesquisa paralela sobre os eventos relacionados ao ativismo digital não teria acontecido. De maneira especial, quero agradecer a Howard Rheingold, além do inestimável valor da leitura de seus livros, devo a ele meu despertar para o tema da cooperação, o privilégio de acompanhar sua investigação ao longo dos anos e dois de seus cursos sobre o mesmo tema. Finalmente, agradeço de todo coração aos meus pais. Primeiro, a meu pai, Sebastião Hermano Leite Cintra, a quem dedico este volume e que se foi durante o período da pesquisa muito tristemente. Sua sabedoria, perspicácia e caráter são inspirações eternas. Em seguida, a minha mãe, Anna Maria Marques Cintra, cuja carreira acadêmica é um exemplo maior em muitos sentidos. Minha curiosidade intelectual descende da sua, o que é motivo de muito orgulho. Resumo CINTRA, H. J. M. A nova potênCia da Cooperação: efeitos da interatividade digital na ação coletiva empreendedora. (Tese de doutorado) São Paulo: Pontifícia Universidade Católica de São Paulo. 2016. 394 f. As comunidades de desenvolvimento de software livre produzem objetos complexos organizando sua ação coletiva por meio de mecanismos de interatividade digital. Algumas delas envolvem centenas, ou até milhares, de programadores e, por vezes, milhões de linhas de código. A cooperação alcança uma nova potência. A pesquisa recolhe evidências das práticas de interatividade digital de um amplo conjunto de projetos de software livre. Demonstra como transformações no processo de comunicação constituem os vínculos sociais necessários às ações coletivas organizadas via internet. O levantamento e a análise estão alicerçados em um modelo para compreensão da fluência digital inspirado na fenomenologia de Charles Peirce e na epistemologia do design institucional de Elinor Ostrom associada uma releitura da natureza da firma. Antes da exposição do método, o texto apresenta o fenômeno em discussão (cooperação), o objeto em estudo (comunidades de desenvolvimento de software livre), e o universo da pesquisa (cultura digital). O primeiro elemento segue por um panorama crítico do embate entre as narrativas da cooperação e competição. O segundo passa por detalhada análise, incluindo as questões da motivação dos participantes, das qualidades do produto técnica, de sua perspectiva política (interna e externa), de sua natureza econômica (bem e produção) e da própria interatividade digital, tema da tese defendida pelo texto. Para o terceiro, a discussão faz sucessivos estreitamento de foco, partindo dos quatro conceitos-chaves da cultura digital identificados por Lucia Santaella, orientadora da presente pesquisa – pós-humano, hibridismo, fluidez, ubiquidade –, caminha pelas comunidades virtuais, pelo ativismo político online, para chegar à cultura hacker, berço do software livre. O estudo desses três elementos e o trabalho com instrumentos metodológicos escolhidos permitiram comprovar o elevado patamar de fluência nas práticas de interatividade digital evidenciadas. O framework da análise institucional foi aplicado ao desenvolvimento de software livre, destacando três diferentes momentos e formatos das contribuições coletivas: formativas (novos projetos), extensivas (novas funções), e de ajuste. A pesquisa conseguiu associar a comunicação digital com suas potências expressiva, afetiva e cooperativa, demonstrando como os diálogos muitos-muitos alteram a escala e o alcance, como a permanência do registro reconstitui a confiança, como as interlocuções assíncronas remodelam as atividades coordenação, e como espaços de interação mais complexos possibilitam novos modelos de governança da ação coletiva. Muitos outros estudos foram realizados sobre temas conexos, diversos deles citados. O presente trabalho pretende preencher uma lacuna no exame do fenômeno como tecnologia da inteligência no âmbito da teoria da comunicação. Somente esta perspectiva permitiu concluir a pesquisa com a proposição de sete princípios de design interatividade digital para a ação coletiva empreendedora e cooperativa: (1) fomente da fluência digital; (2) especialize os espaços de interação; (3) utilize uma moderação ativa; (4) espelhe as funções produtivas no digital; (5) exercite completa transparência; (6) explicite o mérito; e (7) viabilize a iniciativa aberta e múltipla. Palavras-chave: Cooperação. Interatividade digital. Fluência digital. Ação coletiva. Software livre. Comunicação. Design digital. Tecnologias da inteligência. AbstraCt CINTRA, H. J. M. THe new power of Cooperation: effects of digital interactivity in entrepreneurial collective action. (Doctorate thesis) São Paulo: Pontifícia Universidade Católica de São Paulo. 2016. 394 f. Free software development communities produce complex objects organizing their collective action through mechanisms of digital interactivity. Some of them reach hundreds, even thousands, of programmers, working on, sometimes, millions lines of code. Cooperation is taken to a new level. The research has collected evidence of digital interactivity
Load more

Recommended publications
  • Logiciel Libre, Une Introduction Part I Perspective Historique Des Étapes
    Logiciel libre, une introduction Logiciel libre, une introduction Logiciel libre, une introduction Part I Roberto Di Cosmo Perspective historique Université Paris Diderot UFR Informatique Laboratoire Preuves, Programmes et Systèmes [email protected] 7 Février 2012 Logiciel libre, une introduction Logiciel libre, une introduction Une brève histoire du logiciel Une brève histoire du logiciel Des étapes importantes Une brève histoire du logiciel I Années 50-60: Logiciel libre ante litteram Logiciel Libre aux origines La propriétarisation du logiciel I Années 70: La proprietarisation du logiciel I Années 70-80: Les briques de base I Donald Knuth et TEX Le logiciel libre ante litteram I X Windows System Le système TEX I AT&T et Unix Le système X I Années 80: le matériel devient suffisamment puissant pour des AT&T et Unix vrai OS Linux I Années 80: Richard Stallman, GNU et la Free Software Foundation Le logiciel libre formalisé I Années 1990: Linux, GNU/Linux etc.: la prise de conscience I Années 2000 : l’expansion Les années 1990 Logiciel libre, une introduction Logiciel libre, une introduction Une brève histoire du logiciel Une brève histoire du logiciel Logiciel Libre aux origines Logiciel Libre aux origines Au début le logiciel fût distribué librement. c’était une nécéssité Jusqu’à la fin des années 1960, le logiciel, avec les sources, était N’oublions pas les raisons techniques de cette réalité: distribué gratuitement, comme un complément pour les ordinateurs I modèle de service clé en main comprenant hw & sw & vendus (très chers) à l’époque. service I logiciel très dépendant de la machine utilisateur (n.
    [Show full text]
  • Opinnäytetyö Ohjeet
    Lappeenrannan–Lahden teknillinen yliopisto LUT School of Engineering Science Tietotekniikan koulutusohjelma Kandidaatintyö Mikko Mustonen PARHAITEN OPETUSKÄYTTÖÖN SOVELTUVAN VERSIONHALLINTAJÄRJESTELMÄN LÖYTÄMINEN Työn tarkastaja: Tutkijaopettaja Uolevi Nikula Työn ohjaaja: Tutkijaopettaja Uolevi Nikula TIIVISTELMÄ LUT-yliopisto School of Engineering Science Tietotekniikan koulutusohjelma Mikko Mustonen Parhaiten opetuskäyttöön soveltuvan versionhallintajärjestelmän löytäminen Kandidaatintyö 2019 31 sivua, 8 kuvaa, 2 taulukkoa Työn tarkastajat: Tutkijaopettaja Uolevi Nikula Hakusanat: versionhallinta, versionhallintajärjestelmä, Git, GitLab, SVN, Subversion, oppimateriaali Keywords: version control, version control system, Git, GitLab, SVN, Subversion, learning material LUT-yliopistossa on tietotekniikan opetuksessa käytetty Apache Subversionia versionhallintaan. Subversionin käyttö kuitenkin johtaa ylimääräisiin ylläpitotoimiin LUTin tietohallinnolle. Lisäksi Subversionin julkaisun jälkeen on tullut uusia versionhallintajärjestelmiä ja tässä työssä tutkitaankin, olisiko Subversion syytä vaihtaa johonkin toiseen versionhallintajärjestelmään opetuskäytössä. Työn tavoitteena on löytää opetuskäyttöön parhaiten soveltuva versionhallintajärjestelmä ja tuottaa sille opetusmateriaalia. Työssä havaittiin, että Git on suosituin versionhallintajärjestelmä ja se on myös suhteellisen helppo käyttää. Lisäksi GitLab on tutkimuksen mukaan Suomen yliopistoissa käytetyin ja ominaisuuksiltaan ja hinnaltaan sopivin Gitin web-käyttöliittymä. Näille tehtiin
    [Show full text]
  • BSD Projects IV – BSD Certification • Main Features • Community • Future Directions a (Very) Brief History of BSD
    BSD Overview Jim Brown May 24, 2012 BSD Overview - 5/24/2012 - Jim Brown, ISD BSD Overview I – A Brief History of BSD III – Cool Hot Stuff • ATT UCB Partnership • Batteries Included • ATT(USL) Lawsuit • ZFS , Hammer • BSD Family Tree • pf Firewall, pfSense • BSD License • Capsicum • Virtualization Topics • Jails, Xen, etc. • Desktop PC-BSD II – The Core BSD Projects IV – BSD Certification • Main Features • Community • Future Directions A (Very) Brief History of BSD 1971 – ATT cheaply licenses Unix source code to many organizations, including UCB as educational material 1975 – Ken Thompson takes a sabbatical from ATT, brings the latest Unix source on tape to UCB his alma mater to run on a PDP 11 which UCB provided. (Industry/academic partnerships were much more common back then.) Computer Science students (notably Bill Joy and Chuck Haley) at UCB begin to make numerous improvements to Unix and make them available on tape as the “Berkeley Software Distribution” - BSD A (Very) Brief History of BSD Some notable CSRG • 1980 – Computer Science Research Group members (CSRG) forms at UCB with DARPA funding to make many more improvements to Unix - job control, autoreboot, fast filesystem, gigabit address space, Lisp, IPC, sockets, TCP/IP stack + applications, r* utils, machine independence, rewriting almost all ATT code with UCB/CSRG code, including many ports • 1991 – The Networking Release 2 tape is released on the Internet via anon FTP. A 386 port quickly follows by Bill and Lynne Jolitz. The NetBSD group is formed- the first Open Source community entirely on the Internet • 1992 – A commercial version, BSDI (sold for $995, 1-800-ITS-UNIX) draws the ire of USL/ATT.
    [Show full text]
  • Configuration Management with Ansible And
    Configuration management with Ansible and Git Paul Waring ([email protected], @pwaring) January 10, 2017 Topics I Configuration management I Version control I Firewall I Apache / nginx I Git Hooks I Bringing it all together Configuration management I Old days: edit files on each server, manual package installation I Boring, repetitive, error-prone I Computers are good at this sort of thing I Automate using shellscripts - doesn’t scale, brittle I Create configuration file and let software do the rest I Less firefighting, more tea-drinking Terminology I Managed node: Machines (physical/virtual) managed by Ansible I Control machine: Runs the Ansible client I Playbook/manifest: Describes how a managed node is configured I Agent: Runs on managed nodes Ansible I One of several options I Free and open source software - GPLv3 I Developed by the community and Ansible Inc. I Ansible Inc now part of RedHat I Support via the usual channels, free and paid Alternatives to Ansible I CfEngine I Puppet, Chef I SaltStack Why Ansible? I Minimal dependencies: SSH and Python 2 I Many Linux distros ship with both I No agents/daemons (except SSH) I Supports really old versions of Python (2.4 / RHEL 5) on nodes I Linux, *BSD, macOS and Windows Why Ansible? I Scales up and down I Gentle learning curve I But. no killer features I A bit like: vim vs emacs Configuration file I Global options which apply to all nodes I INI format I Write once, then leave Configuration file [defaults] inventory= hosts Inventory file I List of managed nodes I Allows overriding of global options on per-node basis I Group similar nodes, e.g.
    [Show full text]
  • Linux on the Move
    Guest Editors’ Introduction What is Linux? And why should you care? This focus section has insights for both newcomers and diehard fans. Linux on the Move Terry Bollinger, The Mitre Corporation Peter Beckman, Los Alamos National Laboratory inux is a free, open-source operating system that looks like Unix, L except that it runs on PCs as well as other platforms. Linux was created by Linus Torvalds in 1991. Today, Linux is cooperatively improved by Torvalds and thousands of volunteers from around the world using open-source development methods. At this point in time, “Linux” generally refers to the entire suite of software in a distribution, from the operating system kernel to the Web server and graphical user interface. When we say that Linux is “free” we mean, well…free. You do not need to pay money to get a copy of it, although it is usually more convenient to buy an inexpen- sive CD-ROM copy than download an entire distribution over the Internet. Once you get a copy of Linux, you also have the right to make as many copies of it as you want. 30 IEEE Software January/February 1999 0740-7459/99/$10.00 © 1999 . DEFINING TERMS GETTING RESULTS By “open source”we mean that you also have the The only traditional software practice that open- right to get copies of all the source code from which source software developers do follow is peer review, Linux and its associated tools were originally com- and they do that with a vengeance. Each piece of piled. There are no magical, mysterious binary files, source code is placed on display in front of a global although you can of course get the Linux system precompiled if you prefer.
    [Show full text]
  • History of Unix.Pdf
    History of Unix In order to define UNIX, it helps to look at its history. In 1969, Ken Thompson, Dennis Ritchie and others started work on what was to become UNIX on a "little-used PDP-7 in a corner" at AT&T Bell Labs. For ten years, the development of UNIX proceeded at AT&T in numbered versions. V4 (1974) was re-written in C -- a major milestone for the operating system's portability among different systems. V6 (1975) was the first to become available outside Bell Labs -- it became the basis of the first version of UNIX developed at the University of California Berkeley. Bell Labs continued work on UNIX into the 1980s, culminating in the release of System V (as in "five," not the letter) in 1983 and System V, Release 4 (abbreviated SVR4) in 1989. Meanwhile, programmers at the University of California hacked mightily on the source code AT&T had released, leading to many a master thesis. The Berkeley Standard Distribution (BSD) became a second major variant of "UNIX." It was widely deployed in both university and corporate computing environments starting with the release of BSD 4.2 in 1984. Some of its features were incorporated into SVR4. As the 1990s opened, AT&T's source code licensing had created a flourishing market for hundreds of UNIX variants by different manufacturers. AT&T sold its UNIX business to Novell in 1993, and Novell sold it to the Santa Cruz Operation two years later. In the meantime, the UNIX trademark had been passed to the X/Open consortium, which eventually merged to form The Open Group.1 While the stewardship of UNIX was passing from entity to entity, several long- running development efforts started bearing fruit.
    [Show full text]
  • Perhaps Not the Answer You Were Expecting but You Asked for It
    Perhaps Not The Answer You Were Expecting But You Asked For It (An Accidental Blook) Conor McBride October 23, 2019 2 Contents 1 Haskell Curiosities 7 1.1 What is () in Haskell, exactly? . 7 1.2 What does () mean in Haskell? . 8 1.3 Implement the function lines in Haskell . 9 1.4 Boolean Expression evaluation (subtle type error) . 9 1.5 Purely functional data structures for text editors . 10 1.6 What are some motivating examples for Cofree CoMonad in Haskell? . 12 1.7 Find indices of things in lists . 15 1.8 How do I extend this mergeWords function to any number of strings? . 15 1.9 Example of UndecidableInstances yielding nonterminating typecheck . 16 1.10 Why do 3 and x (which was assigned 3) have different inferred types in Haskell? . 17 1.11 Use case for rank-3 (or higher) polymorphism? . 18 1.12 Why don’t Haskell compilers facilitate deterministic memory management? . 19 1.13 How does ArrowLoop work? Also, mfix? . 19 1.14 What does ) mean in a type signature? . 20 1.15 Meaning of Double and Floating point? . 21 1.16 Haskell terminology: meaning of type vs. data type, are they synonyms? . 22 1.17 Can you formulate the Bubble sort as a monoid or semigroup? . 23 1.18 Is this a correctly implemented mergesort in Haskell? . 24 1.19 Haskell type system nuances (ambiguity) . 26 1.20 Understanding a case of Haskell Type Ambiguity . 27 1.21 Why does Haskell use ! instead of =?.......................... 27 1.22 Is it possible to make a type an instance of a class if its type parameters are in the wrong order? .
    [Show full text]
  • MAUS: the MICE Analysis User Software
    RAL-P-2018-007 MAUS: The MICE Analysis User Software R. Asfandiyarov,a R. Bayes,b V. Blackmore,c M. Bogomilov,d D. Colling,c A.J. Dobbs,c F. Drielsma,a M. Drews,h M. Ellis,c M. Fedorov,e P. Franchini,f R. Gardener,g J.R. Greis,f P.M. Hanlet,h C. Heidt,i C. Hunt,c G. Kafka,h Y. Karadzhov,a A. Kurup,c P. Kyberd,g M. Littlefield,g A. Liu,j K. Long,c;n D. Maletic,k J. Martyniak,c S. Middleton,c T. Mohayai,h; j J.J. Nebrensky,g J.C. Nugent,b E. Overton,l V. Pec,l C.E. Pidcott,f D. Rajaram,h;1 M. Rayner,m I.D. Reid,g C.T. Rogers,n E. Santos,c M. Savic,k I. Taylor,f Y. Torun,h C.D. Tunnell,m M.A. Uchida,c V. Verguilov,a K. Walaron,b M. Winter,h S. Wilburl aDPNC, section de Physique, Université de Genève, Geneva, Switzerland bSchool of Physics and Astronomy, Kelvin Building, The University of Glasgow, Glasgow, UK cDepartment of Physics, Blackett Laboratory, Imperial College London, London, UK dDepartment of Atomic Physics, St. Kliment Ohridski University of Sofia, Sofia, Bulgaria eRadboud University of Nijmegen, Netherlands f Department of Physics, University of Warwick, Coventry, UK gBrunel University, Uxbridge, UK hPhysics Department, Illinois Institute of Technology, Chicago, IL, USA iUniversity of California, Riverside, CA, USA j Fermilab, Batavia, IL, USA k Institute of Physics, University of Belgrade, Serbia lDepartment of Physics and Astronomy, University of Sheffield, Sheffield, UK mDepartment of Physics, University of Oxford, Denys Wilkinson Building, Oxford, UK nSTFC Rutherford Appleton Laboratory, Harwell Oxford, Didcot, UK E-mail: [email protected] Abstract: The Muon Ionization Cooling Experiment (MICE) collaboration has developed the MICE Analysis User Software (MAUS) to simulate and analyze experimental data.
    [Show full text]
  • Introduction to Free Software-SELF
    Introduction to Free Software Jordi Mas Hernández (coordinador) David Megías Jiménez (coordinador) Jesús M. González Barahona Joaquín Seoane Pascual Gregorio Robles XP07/M2101/02708 © FUOC • XP07/M2101/02708 Introduction to Free Software Jordi Mas Hernández David Megías Jiménez Jesús M. González Barahona Founding member of Softcatalà and Computer Science Engineer by the Professor in the Department of Tele- of the telematic network RedBBS. Universitat Autònoma de Barcelona matic Systems and Computation of He has worked as a consultant in (UAB, Spain). Master in Advanced the Rey Juan Carlos University (Ma- companies like Menta, Telépolis, Vo- Process Automatisation Techniques drid, Spain), where he coordinates dafone, Lotus, eresMas, Amena and by the UAB. PhD. in Computer Sci- the research group LibreSoft. His Terra España. ence by the UAB. Associate Profes- professional areas of interest include sor in the Computer Science, Multi- the study of free software develop- media and Telecommunication De- ment and the transfer of knowledge partment of the Universitat Oberta in this field to the industrial sector. de Catalunya (UOC, Spain) and Di- rector of the Master Programme in Free Software at the UOC. Joaquín Seoane Pascual Gregorio Robles PhD. Enigeer of Telecommunicati- Assistant professor in the Rey Juan ons in the Politechnical University Carlos University (Madrid, Spain), of Madrid (Spain). He has worked where he acquired his PhD. de- in the private sector and has al- gree in February 2006. Besides his so taught in the Computer Scien- teaching tasks, he researches free ce Faculty of that same university. software development from the Nowadays he is professor in the De- point of view of software enginee- partment of Telematic Systems En- ring, with special focus in quantitati- gineering, and has taught courses ve issues.
    [Show full text]
  • Institutionen För Datavetenskap
    Institutionen f¨ordatavetenskap Department of Computer and Information Science Final thesis Graphical User Interfaces for Distributed Version Control Systems by Kim Nilsson LIU-IDA/LITH-EX-A{08/057{SE 2008{12{05 Linköpings universitet Linköpings universitet SE-581 83 Linköping, Sweden 581 83 Linköping Final thesis Graphical User Interfaces for Distributed Version Control Systems by Kim Nilsson LIU-IDA/LITH-EX-A{08/057{SE 2008{12{05 Supervisor: Anders H¨ockersten, Opera Software Examiner: Henrik Eriksson, MDA Abstract Version control is an important tool for safekeeping of data and collaboration between colleagues. These days, new distributed version control systems are growing increasingly popular as successors to centralized systems like CVS and Subversion. Graphical user interfaces (GUIs) make it easier to interact with version control systems, but GUIs for distributed systems are still few and less mature than those available for centralized systems. The purpose of this thesis was to propose specific GUI ideas to make dis- tributed systems more accessible. To accomplish this, existing version con- trol systems and GUIs were examined. A usage survey was conducted with 20 participants consisting of software engineers. Participants were asked to score various aspects of version control systems according to usage fre- quency and usage difficulty. These scores were combined into an indexof each aspect's \unusability" and thus its need of improvement. The primary problems identified were committing, inspecting the work- ing set, inspecting history and synchronizing. In response, a commit helper, a repository visualizer and a favorite repositories list were proposed, along with several smaller suggestions. These proposals should constitute a good starting point for developing GUIs for distributed version control systems.
    [Show full text]
  • Haskell Communities and Activities Report
    Haskell Communities and Activities Report http://tinyurl.com/haskcar Thirty Fourth Edition — May 2018 Mihai Maruseac (ed.) Chris Allen Christopher Anand Moritz Angermann Francesco Ariis Heinrich Apfelmus Gershom Bazerman Doug Beardsley Jost Berthold Ingo Blechschmidt Sasa Bogicevic Emanuel Borsboom Jan Bracker Jeroen Bransen Joachim Breitner Rudy Braquehais Björn Buckwalter Erik de Castro Lopo Manuel M. T. Chakravarty Eitan Chatav Olaf Chitil Alberto Gómez Corona Nils Dallmeyer Tobias Dammers Kei Davis Dimitri DeFigueiredo Richard Eisenberg Maarten Faddegon Dennis Felsing Olle Fredriksson Phil Freeman Marc Fontaine PÁLI Gábor János Michał J. Gajda Ben Gamari Michael Georgoulopoulos Andrew Gill Mikhail Glushenkov Mark Grebe Gabor Greif Adam Gundry Jennifer Hackett Jurriaan Hage Martin Handley Bastiaan Heeren Sylvain Henry Joey Hess Kei Hibino Guillaume Hoffmann Graham Hutton Nicu Ionita Judah Jacobson Patrik Jansson Wanqiang Jiang Dzianis Kabanau Nikos Karagiannidis Anton Kholomiov Oleg Kiselyov Ivan Krišto Yasuaki Kudo Harendra Kumar Rob Leslie David Lettier Ben Lippmeier Andres Löh Rita Loogen Tim Matthews Simon Michael Andrey Mokhov Dino Morelli Damian Nadales Henrik Nilsson Wisnu Adi Nurcahyo Ulf Norell Ivan Perez Jens Petersen Sibi Prabakaran Bryan Richter Herbert Valerio Riedel Alexey Radkov Vaibhav Sagar Kareem Salah Michael Schröder Christian Höner zu Siederdissen Ben Sima Jeremy Singer Gideon Sireling Erik Sjöström Chris Smith Michael Snoyman David Sorokin Lennart Spitzner Yuriy Syrovetskiy Jonathan Thaler Henk-Jan van Tuyl Tillmann Vogt Michael Walker Li-yao Xia Kazu Yamamoto Yuji Yamamoto Brent Yorgey Christina Zeller Marco Zocca Preface This is the 34th edition of the Haskell Communities and Activities Report. This report has 148 entries, 5 more than in the previous edition.
    [Show full text]
  • A Brief Introduction to Linux
    ABriefIntroductiontoLinux What is it? What can I use it for? Alexander B. Pacheco LTS Research Computing September 8, 2015 Outline 1 Introduction to Linux 2 Linux Components 3 Live Demo 2/25 Introduction to Linux Unix History I Unix was conceived and implemented in 1969 at AT&T Bell labs by Ken Thompson, Dennis Ritchie, Douglas McIlroy, and Joe Ossanna. First released in 1971 and was written in assembler. In 1973, Unix was re-written in the programming language C by Dennis Ritchie (with exceptions to the kernel and I/O). The availability of an operating system written in a high-level language allowed easier portability to di↵erent computer platforms. The GNU Project, started in 1983 by Richard Stallman, had the goal of creating a “complete Unix-compatible software system” composed entirely of free software. 386BSD released in 1992 and written by Berkeley alumni Lynne Jolitz and William Jolitz. FreeBSD, NetBSD, OpenBSD and NextStep (Mac OSX) descended from this Andrew S. Tanenbaum wrote and released MINIX, an inexpensive minimal Unix-like operating system, designed for education in computer science Frustated with licensing issues with MINIX, Linus Torvalds, a student at University of Helsinki began working on his own operating system which eventually became the ”Linux Kernel” Linus released his kernel for anyone to download and help further development. 4/25 Unix History II Linus’s message to comp.os.minix on Aug 26, 1991 Hello everybody out there using minix - I’m doing a (free) operating system (just a hobby, won’t be big and professional like gnu) for 386(486) AT clones.
    [Show full text]