DOCSLIB.ORG

Vertical Interaction in Open Software Engineering Communities Patrick Adam Wagstrom

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Vertical Interaction in Open Software Engineering Communities Patrick Adam Wagstrom CMU-ISR-09-103 March 2009 Carnegie Insitute of Technology and School of Computer Science Carnegie Mellon University Pittsburgh, PA 15213 Thesis Committee: James D. Herbsleb, Co-Chair Kathleen M. Carley, Co-Chair M. Granger Morgan Audris Mockus Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Engineering and Public Policy and Computation, Organizations and Society. Copyright c 2009 Patrick Adam Wagstrom. ! This research was supported by the National Science Foundation through the Graduate Research Fellowship Program, National Science Foundation Grant No. IIS-0414698, the National Science Foundation IGERT Training Program in CASOS(NSF,DGE-9972762), the Office of Naval Research under Dynamic Network Analysis program (N00014-02-1-0973, the Air Force Office of Sponsored Research (MURI: Cultural Mod- eling of the Adversary, 600322), the Army Research Lab (CTA: 20002504), and the Army Research Institute (W91WAW07C0063) for research in the area of dynamic network analysis. Additional support was provided by CASOS - the center for Computational Analysis of Social and Organizational Systems at Carnegie Mellon University. The views and conclusions contained in this thesis are those of the author and should not be interpreted as representing the official policies, either expressed or implied, of the the National Science Foundation, the Office of Naval Research, the Air Force Office of Sponsored Research, the Army Research Lab, or the Army Research Institute. Keywords: Open Source, software engineering, software development, socio-technical systems, socio- technical congruence, computer supported cooperative work This work is licensed under the Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc- nd/3.0/us/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. To Kristina and my parents. Abstract Software engineering is still a relatively young field, struggling to develop consistent standards and methods across the domain. For a given project, de- velopers can choose from dozens of models, tools, platforms, and languages for specification, design, implementation, and testing. The globalization of software engineering and the rise of Open Source further complicate the issues as firms now must collaborate and coordinate with other firms and individu- als possessing a myriad of goals, norms, values, expertise, and preferences. This thesis uses four empirical studies to take a vertical examination of Open Source ecosystems and identify the way that foundations, firms, and individu- als come together to create large scale software ecosystems and produce world class software despite their differing goals and values. First, I examine Open Source as a collaborative phenomenon between firms and non-profit foundations that support many communities and identify the ways in which non-profit foundations enable member firms to create value in the ecosystem. Next, an empirical study of direct collaboration between firms within the Eclipse system reveals that most firms operate relatively indepen- dently, but there is still heavy reliance on a single dominant player for core portions of the ecosystem. I then evaluate how the presence of commercial firms affects the attraction and retention of volunteer developers in an Open Source community. The final study examines how individual developers man- age their dependencies in Open Source and extends the socio-technical con- gruence metric to address changing requirements and facilitate the metric as a tool for continual use. Finally, based on the findings of these studies, I close with a set of recommendations for stakeholders investing in Open Source. Acknowledgments A huge amount of thanks goes to my primary thesis advisors, Jim Herbsleb and Kathleen Carley. Thank you for giving me the freedom to design and implement a course of research that I wanted. Thank you for gently guiding me back when I would stray from the course. And thank you for your input, direction, and most importantly, patience with me. I’ve had the privilege to work with and build my ideas through interaction with many other amazing researchers, engineers, and scientists at Carnegie Mellon. In particular, I am in debt to Marcelo Cataldo for his work laying the foundation for socio-technical congruence. Thanks to all the folks in the CASOS lab and COS seminar for your feedback and advice on my research. Thanks to Peter Landwehr for his help in focusing some of the ideas regard- ing Eclipse. Thanks to Anita Sarma for her feedback and willingness to take on additional responsibilities so I could finish. I’m also grateful for the sup- port and help from Robert Kraut, particularly for his help in understanding volunteer motivation and the social aspects of volunteer participation in open communities. I’ve also had the pleasure of working with numerous individuals outside of Carnegie Mellon who have greatly shaped my research. Sonali Shah was in- valuable in organizing, planning, and analyzing the interviews with the Eclipse Foundation. Thanks to the software governance team at IBM research: Clay Williams, Kate Ehrlich, Mary Helander and Peppo Valetto for their help in exploring some of the preliminary ideas with expanding the problem space around socio-technical congruence. I’m eternally in debt to my previous aca- demic mentors at Illinois Institute of Technology, Xian-He Sun and Gregor von Laszewski who were willing to help direct an undergrad in a class he wasn’t supposed to take on how to do research and be successful as a researcher and scientist. Finally, this wouldn’t be possible without the support of my friends and family. Thanks to everyone who has been in my small groups for letting me vent. Thanks to my parents for giving me just enough support so I still felt independent. Finally, thanks to my wonderful wife Kristina, whom I love very much and who tolerates all of my mood swings, listens to my frustrations, and is a sane force in my life. Thanks for being willing to move out here and share in the pain when you decided to come to Carnegie Mellon and get a Ph.D. for yourself. Contents 1 Introduction 1 1.1 A Brief History of Open Source ....................... 2 1.2 Academic Research on Open Source ..................... 7 1.3 Overview of Thesis .............................. 12 2 Firms and Foundations: Guiding an Ecosystem To Promote Value 16 2.1 Governance and Intellectual Property ..................... 17 2.2 Foundations in Open Source ......................... 19 2.3 Description of Data .............................. 22 2.3.1 Interview Methodology ........................ 24 2.4 Community Design in Eclipse ........................ 27 2.5 Dominant Purposes of the Eclipse Foundation ................ 32 2.6 Driving Value Creation ............................ 36 2.6.1 Non-Market Player .......................... 36 2.6.2 Introduction of Process ........................ 37 2.6.3 The Value of the Eclipse Brand and Joint Marketing ........ 38 2.6.4 Organizational Structure Driving Value ............... 41 2.6.5 Platform for Innovation ........................ 43 vi 2.7 Conclusion .................................. 45 2.8 Topics for Future Research .......................... 46 3 Firms and Firms: Business Collaboration Through Open Source Projects 48 3.1 Description of Data .............................. 53 3.2 The Architecture of Eclipse .......................... 55 3.3 Distribution of work .............................. 58 3.3.1 Firm Participation on Projects .................... 66 3.4 Comparison of Eclipse with GNOME .................... 74 3.5 Conclusions .................................. 83 4 Firms and Individuals: The Impact of Commercial Participation on Volunteer Participation 86 4.1 Introduction .................................. 86 4.1.1 Commercial Participation and Positive Project Momentum ..... 88 4.1.2 Negative Impacts of Heterogeneity .................. 90 4.1.3 Business Models and Community Norms .............. 90 4.1.4 Cognitive Complexity at the Module Level ............. 92 4.2 Research Method ............................... 94 4.2.1 Community Background ....................... 94 4.3 Study 1: Developer Interviews ........................ 97 4.3.1 Views of Commercial Participation .................100 4.3.2 Classification of Firms ........................102 4.4 Study 2: Quantitative Analysis ........................105 4.4.1 Data Collection and Analysis .....................106 4.4.2 Product Focused vs. Community Focused Developers ........108 vii 4.4.3 Quantifying the Impact of Commercial Developers on Volunteer Participation .............................113 4.5 Discussion ...................................129 5 Individuals and Individuals: Evolution of the Socio-Technical Congruence Metric 133 5.1 Organizational Congruence ..........................135 5.2 Problems with Socio-Technical Congruence .................138 5.3 Replication of Original Results in Open Source ...............141 5.3.1 Selection of Projects .........................141 5.3.2 Generation of Networks .......................142 5.3.3 Selection of Control Variables ....................144 5.3.4 Results in Open Source ........................146 5.4 Individualized Congruence ..........................148 5.4.1 Distribution of Metrics ........................149 5.4.2
Recommended publications
  • DICE Framework – Initial Version

    DICE Framework – Initial Version

    Developing Data-Intensive Cloud Applications with Iterative Quality Enhancements DICE Framework – Initial version Deliverable 1.5 Deliverable 1.5. DICE Framework – Initial version Deliverable: D1.5 Title: DICE Framework – Initial version Editor(s): Marc Gil (PRO) Contributor(s): Marc Gil (PRO), Ismael Torres (PRO), Christophe Joubert (PRO) Giuliano Casale (IMP), Darren Whigham (Flexi), Matej Artač (XLAB), Diego Pérez (Zar), Vasilis Papanikolaou (ATC), Francesco Marconi (PMI), Eugenio Gianniti(PMI), Marcello M. Bersani (PMI), Daniel Pop (IEAT), Tatiana Ustinova (IMP), Gabriel Iuhasz (IEAT), Chen Li (IMP), Ioan Gragan (IEAT), Damian Andrew Tamburri (PMI), Jose Merseguer (Zar), Danilo Ardagna (PMI) Reviewers: Darren Whigham (Flexi), Matteo Rossi (PMI) Type (R/P/DEC): - Version: 1.0 Date: 31-January-2017 Status: First Version Dissemination level: Public Download page: http://www.dice-h2020.eu/deliverables/ Copyright: Copyright © 2017, DICE consortium – All rights reserved DICE partners ATC: Athens Technology Centre FLEXI: FlexiOPS IEAT: Institutul e-Austria Timisoara IMP: Imperial College of Science, Technology & Medicine NETF: Netfective Technology SA PMI: Politecnico di Milano PRO: Prodevelop SL XLAB: XLAB razvoj programske opreme in svetovanje d.o.o. ZAR: Universidad De Zaragoza The DICE project (February 2015-January 2018) has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No. 644869 Copyright © 2017, DICE consortium – All rights reserved 2 Deliverable 1.5. DICE Framework – Initial version Executive summary This deliverable documents the DICE Framework, which is composed of a set of tools developed to support the DICE methodology. One of these tools is the DICE IDE, which is the front-end of the DICE methodology and plays a pivotal role in integrating the other tools of the DICE framework.
  • Resumen Los Widgets, Pequeñas Aplicaciones De Escritorio, Se Han Convertido En Objeto De Estudio Para Este Trabajo

    Resumen Los Widgets, Pequeñas Aplicaciones De Escritorio, Se Han Convertido En Objeto De Estudio Para Este Trabajo

    Resumen Los widgets, pequeñas aplicaciones de escritorio, se han convertido en objeto de estudio para este trabajo. Se ha analizado y estudiado su entorno, funcionamiento y estructura. Como resultado se ha obtenido una definición del concepto de widget, con diferentes ejemplos prácticos, y una comparativa entre las compañías más destacadas que ofrecen widgets (Apple, Microsoft, Yahoo!, Google y Opera) así como de las diferencias a nivel de estructura e implementación que se encuentran entre sus widgets. En el apartado de estudio también se ha dado atención a los usuarios de estas aplicaciones, explicando cuáles son sus necesidades, costumbres y posibilidades de elección en este campo. Otro de los apartados trata de cubrir algunas de las tecnologías más relevantes implicadas en la creación posterior de un widget, la aplicación Dashcode, el lenguaje de programación JavaScript, y los canales RSS. El tema de los widgets también ha dado lugar a todo un apartado de desarrollo. Se ha creado un widget para la plataforma de Apple, Macintosh. El widget proporciona al usuario las últimas noticias y resultados del mundo deportivo, concretamente de dos deportes, fútbol y baloncesto. Todas las fases del proceso de creación del widget han sido descritas de principio a fin, desde los bocetos iniciales a la puesta en funcionamiento, pasando por el prototipado e implementación. De manera adicional, también se ha incluido un apartado dedicado al diseño de widgets, con algunas y consejos a tener en cuenta al diseñar widgets en general. Por último se han vertido diferentes conclusiones fruto del presente trabajo y de la reflexión sobre la situación actual de este campo, sin olvidar los aspectos a mejorar, las áreas en que se está trabajando y las perspectivas de futuro.
  • How-To Gnome-Look Guide

    How-To Gnome-Look Guide

    HHOOWW--TTOO Written by David D Lowe GGNNOOMMEE--LLOOOOKK GGUUIIDDEE hen I first joined the harddisk, say, ~/Pictures/Wallpapers. right-clicking on your desktop Ubuntu community, I and selecting the appropriate You may have noticed that gnome- button (you know which one!). Wwas extremely look.org separates wallpapers into impressed with the amount of different categories, according to the customization Ubuntu had to size of the wallpaper in pixels. For Don't let acronyms intimidate offer. People posted impressive the best quality, you want this to you; you don't have to know screenshots, and mentioned the match your screen resolution. If you what the letters stand for to themes they were using. They don't know what your screen know what it is. Basically, GTK is soon led me to gnome-look.org, resolution is, click System > the system GNOME uses to the number one place for GNOME Preferences > Screen Resolution. display things like buttons and visual customization. The However, Ubuntu stretches controls. GNOME is Ubuntu's screenshots there looked just as wallpapers quite nicely if you picked default desktop environment. I impressive, but I was very the wrong size, so you needn't fret will only be dealing with GNOME confused as to what the headings about it. on the sidebar meant, and I had customization here--sorry no idea how to use the files I SVG is a special image format that Kubuntu and Xubuntu folks! downloaded. Hopefully, this guide doesn't use pixels; it uses shapes Gnome-look.org distinguishes will help you learn what I found called vectors, which means you can between two versions of GTK: out the slow way.
  • The Glib/GTK+ Development Platform

    The Glib/GTK+ Development Platform

    The GLib/GTK+ Development Platform A Getting Started Guide Version 0.8 Sébastien Wilmet March 29, 2019 Contents 1 Introduction 3 1.1 License . 3 1.2 Financial Support . 3 1.3 Todo List for this Book and a Quick 2019 Update . 4 1.4 What is GLib and GTK+? . 4 1.5 The GNOME Desktop . 5 1.6 Prerequisites . 6 1.7 Why and When Using the C Language? . 7 1.7.1 Separate the Backend from the Frontend . 7 1.7.2 Other Aspects to Keep in Mind . 8 1.8 Learning Path . 9 1.9 The Development Environment . 10 1.10 Acknowledgments . 10 I GLib, the Core Library 11 2 GLib, the Core Library 12 2.1 Basics . 13 2.1.1 Type Definitions . 13 2.1.2 Frequently Used Macros . 13 2.1.3 Debugging Macros . 14 2.1.4 Memory . 16 2.1.5 String Handling . 18 2.2 Data Structures . 20 2.2.1 Lists . 20 2.2.2 Trees . 24 2.2.3 Hash Tables . 29 2.3 The Main Event Loop . 31 2.4 Other Features . 33 II Object-Oriented Programming in C 35 3 Semi-Object-Oriented Programming in C 37 3.1 Header Example . 37 3.1.1 Project Namespace . 37 3.1.2 Class Namespace . 39 3.1.3 Lowercase, Uppercase or CamelCase? . 39 3.1.4 Include Guard . 39 3.1.5 C++ Support . 39 1 3.1.6 #include . 39 3.1.7 Type Definition . 40 3.1.8 Object Constructor . 40 3.1.9 Object Destructor .
  • Engineering at Johns Hopkins University! We Look Forward to Meeting You When You Arrive on Campus for Orientation

    Engineering at Johns Hopkins University! We Look Forward to Meeting You When You Arrive on Campus for Orientation

    Eng in eering 1 01 2019-2020 p rogr am p lanni ng gui de for fi rst-y ear e ngi neering s tudents Welcome to the Whiting School of Engineering at Johns Hopkins University! We look forward to meeting you when you arrive on campus for orientation. In the meantime, we have prepared the First-Year Academic Guide and Engineering 101 to get you started. The Academic Guide includes information for all first-year students at Hopkins, while Engineering 101 is directed specifically to engineering students. Engineering 101 contains information about all of the majors in the School of Engineering, including recommended first semester class schedules. You’ll also find out about some opportunities to join student groups. We hope that these materials help you learn about the Hopkins community and the options available to you. Again, welcome to Hopkins and we’ll see you in August! Linda Moulton, Denise Shipley, Lashell Silver, Eric Simmons, Janet Weise, and Betty Zee Johns Hopkins University Whiting School of Engineering Office of Academic Affairs—Engineering Advising Wyman Park Building Suite N125 3400 N. Charles Street Baltimore, MD 21218-2681 410-516-7395 [email protected] https://engineering.jhu.edu/advising/ Nondiscrimination Statement The Johns Hopkins University is committed to equal opportunity and providing a safe and non- discriminatory educational and working environment for its students, trainees, faculty, staff, post-doctoral fellows, residents, and other members of the University community. To that end, the university seeks to provide community members with an environment that is free from discrimination and harassment on the basis of sex, gender, marital status, pregnancy, race, color, ethnicity, national origin, age, disability, religion, sexual orientation, gender identity or expression, veteran status or other legally protected characteristic.
  • Ausgabe 06/2016 Als

    Ausgabe 06/2016 Als

    freiesMagazin Juni 2016 Themen dieser Ausgabe sind u. a. Ubuntu unter Windows ausprobiert Seite 3 Microsoft hat auf der Entwicklerkonferenz Build 2016 einigermaßen überraschend verraten, dass in zukünftigen Windows-Versionen die Bash sowie eine ganze Sammlung von Linux-Tools auf der Basis von Ubuntu 14.04 integriert werden soll. Der Artikel gibt einen ersten Eindruck des „Windows-Subsystems für Linux“, das Microsoft bereitstellt, um Ubuntu ohne Virtualisierung unter Windows laufen zu lassen. (weiterlesen) Linux-Distributionen im Vergleich – eine etwas andere Auswahl Seite 8 In dem Artikel werden eine Reihe von Linux-Distributionen vorgestellt, die nicht so bekannt sind wie die klassischen „großen“ Distributionen oder nicht so häufig verwendet werden, weil sie entweder für spezielle Anwendungen oder für einen besonderen Benutzerkreis konzipiert sind. Ziel ist es, diese Distributionen ein bisschen näher kennenzulernen, damit man weiß, was zur Verfügung steht, wenn man einmal etwas ganz bestimmtes braucht. (weiterlesen) Audacity 2.1 – Teil I Seite 21 Aus verschiedenen Gründen ist Audacity der beliebteste freie Audio-Editor. Im Internetzeitalter hat man sich daran gewöhnt, dass viele Programme kostenlos verfügbar sind, aber dennoch eine hohe Professionalität aufweisen. In die Riege der besten Open-Source-Werkzeuge reiht sich auch Audacity ein. Ob man nun die Schallplatten- oder Kassettensammlung digitalisieren, Videos nachvertonen oder das eigene Gitarrenspiel oder den Bandauftritt aufnehmen und bearbeiten möchte – all das ist mit Audacity möglich. (weiterlesen) © freiesMagazin CC-BY-SA 4.0 Ausgabe 06/2016 ISSN 1867-7991 MAGAZIN Editorial Veränderungen unter der Haube Viewport-Meta-Tag auf den meisten Seiten Stan- Inhalt Technisch betrachtet ist freiesMagazin stabil. Ver- dard ist, gilt er eher als eine Krücke, die in Zukunft Linux allgemein änderungen erfolgen daher naturgemäß in klei- wohl durch eine CSS basierte Lösung ersetzt wer- Ubuntu unter Windows ausprobiert S.
  • Third Party Terms for Modular Messaging 3.0 (July 2005)

    Third Party Terms for Modular Messaging 3.0 (July 2005)

    Third Party Terms for Modular Messaging 3.0 (July 2005) Certain portions of the product ("Open Source Components") are licensed under open source license agreements that require Avaya to make the source code for such Open Source Components available in source code format to its licensees, or that require Avaya to disclose the license terms for such Open Source Components. If you are a licensee of this Product, and wish to receive information on how to access the source code for such Open Source Components, or the details of such licenses, you may contact Avaya at (408) 577-7666 for further information. The Open Source Components are provided “AS IS”. ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR THE CONTRIBUTORS OF THE OPEN SOURCE COMPONENTS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THE PRODUCT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Avaya provides a limited warranty on the Product that incorporates the Open Source Components. Refer to your customer sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language as well as information regarding support for the Product, while under warranty, is available through the following web site: http://www.avaya.com/support.
  • Annual Report 2006

    Annual Report 2006

    Annual Report 2006 Table of contents Foreword Letter from the Chairman, Dave Neary 4–5 A year in review 2006—a year in GNOME 8–10 Distributions in 2006 11 Events and community initiatives GUADEC—The GNOME Conference 12–13 GNOME hackers descend on MIT Media Center 14–15 GNOME User Groups 16 The www.gnome.org revamp 17 GNOME platform 17 GNOME Foundation Administrator 17 Foundation development The Women’s Summer Outreach Program 18–20 The GNOME Mobile and Embedded Initiative 21 The GNOME Advisory Board 22–23 PHOTO The GNOME Foundation Board and Advisory Board members by David Zeuthen (continued on the inside back cover) GNOME Foundation 3 Dear Friends, All traditions need a starting point, they say. What you now hold in your hands is the first annual report of the GNOME Foundation, at the end of what has been an eventful year for us. Each year brings its challenges and rewards for the members of this global project. This year, many of our biggest challenges are in the legal arena. European countries have been passing laws to conform with the European Union Copyright Directive, and some, including France, have brought into law provisions which we as software developers find it hard to understand, but which appear to make much of what we do illegal. We have found our- selves in the center of patent wars as bigger companies jockey for position with offerings based on our hard work. And we are scratching our heads trying to figure out how to deal with the constraints of DRM and patents in multimedia, while still offering our users access to their media files.
  • Mailman CLI Documentation Release 1

    Mailman CLI Documentation Release 1

    Mailman CLI Documentation Release 1 Rajeev S September 26, 2014 Contents 1 mailman.client 3 1.1 Requirements...............................................3 1.2 Project details..............................................3 1.3 Documentation..............................................3 1.4 Acknowledgements...........................................3 1.5 Table of Contents.............................................4 i ii Mailman CLI Documentation, Release 1 This package is called mailman.client. Contents 1 Mailman CLI Documentation, Release 1 2 Contents CHAPTER 1 mailman.client The mailman.client library provides official Python bindings for the GNU Mailman 3 REST API. Note that the test suite current requires that a Mailman 3 server be running. It should be running using a dummy or throw-away database, as this will make changes to the running system. TBD: mock the real Mailman engine so that it is not necessary in order to run these tests. 1.1 Requirements mailman.client requires Python 2.6 or newer. 1.2 Project details You may download the latest version of the package from the Python Cheese Shop or from Launchpad. You can also install it via easy_install or pip.: % sudo easy_install mailman.client % sudo pip install mailman.client See the Launchpad project page for access to the Bazaar branch, bug report, etc. 1.3 Documentation A simple guide to using the library is available within this package, in the form of doctests. The manual is also available online in the Cheeseshop at: http://package.python.org/mailman.client 1.4 Acknowledgements Many thanks to Florian Fuchs for his contribution of an initial REST client. 3 Mailman CLI Documentation, Release 1 1.5 Table of Contents 1.5.1 Mailman REST client >>> import os >>> import time >>> import smtplib >>> import subprocess >>> from mock import patch This is the official Python bindings for the GNU Mailman REST API.
  • Anjuta 1.2.0

    Anjuta 1.2.0

    Ulasan CD | Klinik | Ulasan | Linux Ready | Utama | Bisnis | Feature | Tutorial SOFTWARE Hasil Tes dan Ulasan Software Anjuta 1.2.0 ALAT BANTU PEMROGRAMAN Sifat: Free software Lisensi: GPL Pengembang: Naba Kumar Situs web: http://anjuta.org nda termasuk developer yang senang menggunakan program- A program sederhana dalam menulis kode program? Kalau ya, barangkali Anda puas dengan editor Vim. Dengan syntax highlighting dan fasilitas pemrograman Anjuta IDE lainnya, Vim termasuk alat bantu pemrograman yang menyenangkan. Hal tersebut belum lagi ditambah dengan program terlihat rapi. Begitu tubuh fungsi pengamatan nilai register, signal kernel, fasilitas pencarian dan penggantian teks disembunyikan, maka yang terlihat breakpoint, memory dump, dan lain yang dapat diketikkan dengan mudah lewat hanyalah nama fungsinya. Menarik, bukan? sebagainya? Tenang saja. Anjuta dapat keyboard. Masih bicara tampilan, kita perlu memuji menampilkannya untuk Anda. Tinggal pilih Tapi, Vim memiliki sejumlah besar pewarnaan yang digunakan oleh Anjuta. menunya dan dalam sekejap, apa yang keterbatasan. Vim sendiri sejatinya adalah Anjuta akan memberikan warna-warna Anda inginkan sudah terpampang. Lebih teks editor biasa. Apabila Anda ingin khusus untuk sesuatu yang termasuk cepat dari sulap! mendapatkan sejumlah besar kemampuan istimewa, misalnya keyword bahasa Secara umum, fasilitas debugging pada Vim dan sekaligus memiliki yang lebih, pemrograman, komentar, sampai isi dari Anjuta pun perlu diberikan acungan jempol. maka Anjutalah pilihannya. suatu konstanta ataupun variabel tipe Fasilitas debugging dibangun di atas gdb, Anjuta adalah IDE untuk C/C++, tertentu. Dan pewarnaan yang dilakukan yang merupakan debugger populer. Anda walaupun dengan mudah dapat digunakan pun cukup menarik. Anjuta akan dapat mengeksekusi interaktif, pengamatan oleh bahasa pemrograman lain. Sebagai memberikan warna kabur terlebih dahulu nilai-nilai tertentu, manipulasi stack, dan contoh, penulis bersenang hati pada saat pengetikan.
  • A Brief History of GNOME

    A Brief History of GNOME

    A Brief History of GNOME Jonathan Blandford <[email protected]> July 29, 2017 MANCHESTER, UK 2 A Brief History of GNOME 2 Setting the Stage 1984 - 1997 A Brief History of GNOME 3 Setting the stage ● 1984 — X Windows created at MIT ● ● 1985 — GNU Manifesto Early graphics system for ● 1991 — GNU General Public License v2.0 Unix systems ● 1991 — Initial Linux release ● Created by MIT ● 1991 — Era of big projects ● Focused on mechanism, ● 1993 — Distributions appear not policy ● 1995 — Windows 95 released ● Holy Moly! X11 is almost ● 1995 — The GIMP released 35 years old ● 1996 — KDE Announced A Brief History of GNOME 4 twm circa 1995 ● Network Transparency ● Window Managers ● Netscape Navigator ● Toolkits (aw, motif) ● Simple apps ● Virtual Desktops / Workspaces A Brief History of GNOME 5 Setting the stage ● 1984 — X Windows created at MIT ● 1985 — GNU Manifesto ● Founded by Richard Stallman ● ● 1991 — GNU General Public License v2.0 Our fundamental Freedoms: ○ Freedom to run ● 1991 — Initial Linux release ○ Freedom to study ● 1991 — Era of big projects ○ Freedom to redistribute ○ Freedom to modify and ● 1993 — Distributions appear improve ● 1995 — Windows 95 released ● Also, a set of compilers, ● 1995 — The GIMP released userspace tools, editors, etc. ● 1996 — KDE Announced This was an overtly political movement and act A Brief History of GNOME 6 Setting the stage ● 1984 — X Windows created at MIT “The licenses for most software are ● 1985 — GNU Manifesto designed to take away your freedom to ● 1991 — GNU General Public License share and change it. By contrast, the v2.0 GNU General Public License is intended to guarantee your freedom to share and ● 1991 — Initial Linux release change free software--to make sure the ● 1991 — Era of big projects software is free for all its users.
  • D2.1 State-Of-The-Art, Detailed Use Case Definitions and User Requirements

    D2.1 State-Of-The-Art, Detailed Use Case Definitions and User Requirements

    D2.1 State-of-the-art, detailed use case definitions and user requirements Deliverable ID: D 2.1 Deliverable Title: State-of-the-art, detailed use case definitions and user requirements Revision #: 1.0 Dissemination Level: Public Responsible beneficiary: VTT Contributing beneficiaries: All Contractual date of delivery: 31.5.2017 Actual submission date: 15.6.2017 ESTABLISH D2.1 State-of-the-art, detailed use case definitions and user requirements 1 Table of Content Table of Content .................................................................................................................................... 2 1. Introduction ..................................................................................................................................... 4 2. Air quality state-of-the-art ................................................................................................................ 5 2.1 Indoor air quality effect on health and productivity ........................................................................ 5 2.2 Outdoor air quality ........................................................................................................................ 8 3. Technological state-of-the-art ........................................................................................................ 13 3.1 Self-awareness and self-adaptivity to cope with uncertainty ........................................................ 13 3.2 Objective health monitoring with sensors ...................................................................................