DOCSLIB.ORG

A Brief History of GNOME

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
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. This General Public License applies to most of ● 1993 — Distributions appear the Free Software Foundation's software ● 1995 — Windows 95 released and to any other program whose authors commit to using it…” ● 1995 — The GIMP released ● 1996 — KDE Announced –GNU GPL v2 preamble A Brief History of GNOME 7 Setting the stage ● 1984 — X Windows created at MIT From: [email protected] (Linus ● 1985 — GNU Manifesto Benedict Torvalds) ● 1991 — GNU General Public License v2.0 Subject: What would you like to see most in minix? ● 1991 — Initial Linux release Date: 25 Aug 91 20:57:08 GMT ● 1991 — Era of big projects Hello everybody out there using minix – ● 1993 — Distributions appear ● 1995 — Windows 95 released I’m doing a (free) operating system (just a hobby, won’t be big and professional ● 1995 — The GIMP released like gnu) for 386(486) AT clones. This ● 1996 — KDE Announced has been brewing since april, and is starting to get ready… A Brief History of GNOME 8 Setting the stage ● 1984 — X Windows created at MIT Linux (‘91) ● 1985 — GNU Manifesto Python (‘91) Samba (‘92) ● 1991 — GNU General Public License v2.0 Apache (‘95) ● 1991 — Initial Linux release mysql (‘95) ● 1991 — Era of big projects gimp (‘95) ● 1993 — Distributions appear postgresql (‘96) ● 1995 — Windows 95 released KDE (‘96) ● 1995 — The GIMP released GNOME (‘97) Mozilla (‘98) ● 1996 — KDE Announced Eclipse (‘01) ... A Brief History of GNOME 9 Setting the stage ● 1984 — X Windows created at MIT SLS (‘92) ● 1985 — GNU Manifesto Slackware (‘93) ● 1991 — GNU General Public License v2.0 Debian (‘93) ● 1991 — Initial Linux release Suse (‘94) ● 1991 — Era of big projects Red Hat (‘94) Ubuntu (‘04) ● 1993 — Distributions appear CentOS (‘04) ● 1995 — Windows 95 released Mint (‘06) ● 1995 — The GIMP released Sugar (‘06) ● 1996 — KDE Announced ChromeOS (‘09) SteamOS (‘13) EOS (‘13) A Brief History of GNOME 10 Setting the stage ● 1984 — X Windows created at MIT ● 1985 — GNU Manifesto Windows 95 ● 1991 — GNU General Public License v2.0 ● Dominated the industry like ● 1991 — Initial Linux release nothing before or since ● 1991 — Era of big projects ● Rocketed to take 98% PC ● 1993 — Distributions appear Market share by 1998 ● 1995 — Windows 95 released ● Microsoft was SCARY, and played for keeps ● 1995 — The GIMP released ● 1996 — KDE Announced Never forget!! A Brief History of GNOME 11 Setting the stage ● 1984 — X Windows created at MIT ● GNU Image Manipulation ● 1985 — GNU Manifesto Program. Inspired by ● 1991 — GNU General Public License v2.0 Photoshop, started at ● 1991 — Initial Linux release Berkeley ● 1991 — Era of big projects ● Fully Free Software except ● 1993 — Distributions appear for Motif as the underlying ● 1995 — Windows 95 released widget toolkit ● Led to GTK+ being created ● 1995 — The GIMP released ● Initial cultural pool for ● 1996 — KDE Announced GNOME hackers A Brief History of GNOME 12 Setting the stage ● 1984 — X Windows created at MIT ● First major effort at a coordinated Desktop ● 1985 — GNU Manifesto Project ● 1991 — GNU General Public License v2.0 ● Free Software code as the ● 1991 — Initial Linux release core desktop. Based on Qt ● 1991 — Era of big projects as the underlying widget ● 1993 — Distributions appear toolkit ● 1995 — Windows 95 released ● It was amazing, but... ● 1995 — The GIMP released ● 1996 — KDE Announced This was not Free Software A Brief History of GNOME 13 Desktop Wars Begin 1997 - 1999 A Brief History of GNOME 14 Desktop wars begin From: Miguel de Icaza To: [email protected], 1997 [email protected]. uni-tuebingen.de, ● Miguel announces GNOME Project [email protected] Subject: The GNOME Desktop project. ● GNOME vs KDE Date: Fri, 15 Aug 1997 22:19:34 -0500 1998 The GNOME Desktop project ● RHAD Labs formed at Red Hat (GNU Network Object Model ● Qt relicenses to the QPL Environment) http://bananoid.nuclecu.unam.mx/gnome ● Project Bob Goals: We want to develop a free and complete set of user friendly applications and desktop tools, similar to CDE and KDE but based entirely on free software.... A Brief History of GNOME 15 Desktop wars begin VS 1997 ● Miguel announces GNOME Project Massive fight breaks out across the Linux scene: ● GNOME vs KDE 1998 ● C vs. C++ ● RHAD Labs formed at Red Hat ● Germany vs. America ● Qt relicenses to the QPL ● Corporate vs. Hackers ● Project Bob ● Qt vs. GTK+ ● Cats vs. Dogs ● Riots and chaos in the streets! A Brief History of GNOME 16 Desktop wars begin 1997 ● Miguel announces GNOME Project Red Hat Advanced Development Labs ● GNOME vs KDE 1998 Early corporate engagement. ● RHAD Labs formed at Red Hat Seven full-time engineers ● Qt relicenses to the QPL working on GNOME ● Project Bob Took over some of the less-glamorous work at the time A Brief History of GNOME 17 GNOME 0.30 September, 1998 ● The Panel ● Panel Applets ● File Manager (GMC) ● Control center settings ● Simple games ● Simple utilities ● Login Manager ● help browser ● VFS layer ● Calendar (gnome-cal) ● Spreadsheet (gnumeric) ● Word Processor (abi) ● Themes ● CORBA ● Canvas ● Internationalized Keyboard A Brief History of GNOME 18 Desktop wars begin 1997 ● Miguel announces GNOME Project Trolltech invented a new license ● GNOME vs KDE 1998 In theory it changed everything. ● RHAD Labs formed at Red Hat In practice it changed nothing... ● Qt relicenses to the QPL In a couple years, Trolltech ● Project Bob would fully embrace the GPL w/ a licensing exception A Brief History of GNOME 19 Desktop wars begin 1997 Project Bob ● Miguel announces GNOME Project The mission: 36 Hours to get ● GNOME vs KDE something that could be shown 1998 to Red Hat’s board so GNOME ● RHAD Labs formed at Red Hat wouldn’t be cut ● Qt relicenses to the QPL The solution: Spend 36 hours ● Project Bob without sleeping to get a working desktop A Brief History of GNOME 20 Desktop wars begin 1997 Project Bob ● Miguel announces GNOME Project The mission: 36 Hours to get ● GNOME vs KDE something that could be shown 1998 to Red Hat’s board so GNOME ● RHAD Labs formed at Red Hat wouldn’t be cut ● Qt relicenses to the QPL The solution: Spend 36 hours ● Project Bob without sleeping to get a working desktop The actual solution: Write a cool new theme! A Brief History of GNOME 21 Battle for Dominance and Survival 1998 - 2001 A Brief History of GNOME 22 Battle for dominance 1999 GNOME 1.0 ● GNOME 1.0 Released at Linux Expo ● Helixcode, Eazel, and Sun 2000 Barely worked. Everything ● GUADEC in Paris crashed ● The GNOME Foundation ● Sun Microsystems and clocks Terrible press conference with 2001 RMS yelling at the New York ● dotcom bubble bursts, Eazel goes bust Times for not saying “GNU ● Novell buys Ximian, then Suse slash Linux” ● OSX 10.0 released A Brief History of GNOME 23 GNOME 1.0 (March 1999) A Brief History of GNOME 24 Battle for dominance 1999 HelixCode was founded by Miguel de ● GNOME 1.0 Icaza and Nat Friedman. It later became ● Helixcode, Eazel, and Sun Ximian - Evolution 2000 - bonobo ● GUADEC in Paris Eazel was founded by Andy Hertzfeld of ● The GNOME Foundation MacOS fame - nautilus ● Sun Microsystems and clocks - Gnome-vfs 2001 Sun was the biggest Unix vendor at the ● dotcom bubble bursts, Eazel goes bust time ● Novell buys Ximian, then Suse - GNOME Accessibility ● OSX 10.0 released A Brief History of GNOME 25 Battle for dominance 1999 ● GNOME 1.0 GNOME Users And Developers ● Helixcode, Eazel, and Sun European Conference 2000 - Where the project gets ● GUADEC in Paris together to recharge and ● The GNOME Foundation renew ● Sun Microsystems and clocks - Started in Paris in 2000 2001 - 18th is here in Manchester! ● dotcom bubble bursts, Eazel goes bust ● Novell buys Ximian, then Suse ● OSX 10.0 released A Brief History of GNOME 26 Battle for dominance 1999 ● GNOME 1.0 Started in a Parisian Café ●
Load more

Recommended publications
  • Fairies, Elves, Elementals, Gnomes
    Circulating File FAIRIES, ELVES, ELEMENTALS, GNOMES A compilation of Extracts from the Edgar Cayce Readings Edgar Cayce Readings Copyrighted by Edgar Cayce Foundation 1971, 1993-2013 All Rights Reserved These readings or parts thereof may not be reproduced in any form without permission in writing from the Edgar Cayce Foundation 215 67th Street Virginia Beach, VA 23451 Printed in U.S.A. FAIRIES, ELVES, ELEMENTALS CIRCULATING FILE Circulating Files are collections of verbatim quotes of what Edgar Cayce said during his readings on a given subject or, in some cases everything. We have medical circulating files which focus on the over 9,000 health-related readings with subjects from Acidity- Alkalinity to Weight Loss. We also have non-medical circulating files on a broad range of topics, for example Egypt: Sphinx, Pyramids, and Hall of Records, Fear and Its Far- Reaching Effects, Advice to Parents, Serving in Accord with Ideals, and Business Advice. Each circulating file is simply a collection of reading quotes or full readings given for different individuals on a similar subject or disease. The A.R.E. cannot and does not suggest treatments for physical ailments nor make claims about the effectiveness of the therapies. We encourage anyone working with the health readings to do so under a doctor's care and advice. The circulating files support the research aspect of the Cayce work. We appreciate any feedback informing us of progress made in improving one’s life or achieving good health by applying suggestions given in the readings. Please send any feedback (testimonies, experiences, results, etc.) to: Library: Circulating File Desk A.R.E.
    [Show full text]
  • Web Vmstat Any Distros, Especially Here’S Where Web Vmstat Comes Those Targeted at In
    FOSSPICKS Sparkling gems and new releases from the world of FOSSpicks Free and Open Source Software Mike Saunders has spent a decade mining the internet for free software treasures. Here’s the result of his latest haul… Shiny statistics in a browser Web VMStat any distros, especially Here’s where Web VMStat comes those targeted at in. It’s a system monitor that runs Madvanced users, ship an HTTP server, so you can connect with shiny system monitoring tools to it via a web browser and see on the desktop. Conky is one such fancy CSS-driven charts. Before you tool, while GKrellM was all the rage install it, you’ll need to get the in the last decade, and they are websocketd utility, which you can genuinely useful for keeping tabs find at https://github.com/ on your boxes, especially when joewalnes/websocketd. Helpfully, you’re an admin in charge of the developer has made pre- various servers. compiled executables available, so Now, pretty much all major you can just grab the 32-bit or distros include a useful command 64-bit tarball, extract it and there line tool for monitoring system you have it: websocketd. (Of course, Here’s the standard output for vmstat – not very interesting, right? resource usage: vmstat. Enter if you’re especially security vmstat 1 in a terminal window and conscious, you can compile it from copy the aforementioned you’ll see a regularly updating (once its source code.) websocketd into the same place. per second) bunch of statistics, Next, clone the Web VMStat Git Then just enter: showing CPU usage, free RAM, repository (or grab the Zip file and ./run swap usage and so forth.
    [Show full text]
  • Desktop Migration and Administration Guide
    Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Last Updated: 2021-05-05 Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Marie Doleželová Red Hat Customer Content Services [email protected] Petr Kovář Red Hat Customer Content Services [email protected] Jana Heves Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • Canadian Guiding Badges and Insignia Brownie Six/Circle Emblems
    Canadian Guiding Badges And Insignia Brownie Six/Circle Emblems Following the introduction of the Brownie program to provide Guiding for younger girls, and after the decision to base the new program on The Brownie Story, a further decision was made in 1919 to subdivide a Brownie Pack into smaller groups consisting of six girls. These smaller groups within the Pack were known as Sixes and were identified by a Six emblem bearing the name of some mythical fairy- like person from folklore. [Reference: POR (British, 1919)] The original Six emblems were brown felt; later versions were brown cotton with the edges bound in brown. In 1995, the term “Sixes” was replaced by the term “Circles”, and the shape of the emblems was changed as well. In 1972, three of the original twelve Six emblems were retired and in 1995 four new ones were added. Page 1 V.2 Canadian Guiding Badges And Insignia Brownie Six/Circle Emblems SC0001 SC0002 Bwbachod Badge Discontinued 1919- 19? 19? - 1972 SC0003 SC0004 Djinn Introduced 1994 1995-2004 1994 SC0005 SC0006 Dryad Introduced 1994 1995- 1994 Page 2 V.2 Canadian Guiding Badges And Insignia Brownie Six/Circle Emblems SC0007 SC0008 SC0009 Elf 1919-19? 19? - 1995 1995- SC0010 SC0011 SC0012 Fairy 1919-19? 19? - 1995 1995- SC0013 SC0014 Ghillie Dhu Badge Discontinued 1919-19? 19? - 1972 Page 3 V.2 Canadian Guiding Badges And Insignia Brownie Six/Circle Emblems SC0015 SC0016 SC0017 Gnome 1995- 1919-19? 19? - 1995 SC0018 SC0019 Imp Badge Discontinued 1919-19? 19? - 1995 SC0020 SC0021 SC0022 Kelpie (formerly called Scottish
    [Show full text]
  • The Gnome Bazaar How Gnome Gets Built and How We Can Improve
    the gnome bazaar how gnome gets built and how we can improve daniel g. siegel 1. some serious stuff about my thesis 2. awesome gnome stuff how do foss projects work, which structures do they have and which workflows have they established. to accomplish this, several foss will be analyzed in order to identify concertedly models. in addition they will be compared to traditional software engineering models in order to see whether they are similar or oppose differences. good selection of projects with which the analysis is able to produce reliable and reasonable results • popularity • community • age ◦ communication • category ◦ number of developers • activity ◦ conferences ◦ releases ◦ foundations ◦ downloads ◦ ongoing projects ◦ commits project origin category Debian 1993 operating system Drupal 2001 content management system Fedora 2002 operating system GNOME 1997 desktop environment KDE 1996 desktop environment MySQL/MariaDB 1997 database management system PHP 1994 interpreted programming language Plone 1999 content management system PostgreSQL 1986 database management system Python 1989 interpreted programming language results 1 • history & origin 2 • community structure 3 • release process 4 • development model "[...] rather, the community seemed to resemble a great babbling bazaar of differing agendas and approaches" eric s. raymond what? comparison 1 • history & origin 2 • community structure 3 • release process 4 • development model history & origin • diverse origin • small group of founders • big burst of growth after first release • more big bursts before big releases community structure • very hierarchical • lead by leader or team • differences in hierachical structure • though easy to step up the ladder community structure: remarks • missing visionary • role of rt • unfruitful discussions release process • mostly fixed release cycles • lead by release manager/team • similar phases in all projects release process: remarks • cycle often too long for small projects • api/abi compatibility • jhbuild etc.
    [Show full text]
  • Free Email Software Download Best Free Email Client 2021
    free email software download Best Free Email Client 2021. This article is all about best free email clients and how they can help you be more productive. We also talk about Clean Email, an easy-to-use email cleaner compatible with virtually all major email services. But before we go over the best email clients for 2021, we believe that we should first explain what advantages email clients have over web-based interfaces of various email services. Clean Email. Take control of your mailbox. What Is an Email Client and Why Should I Use One? If you’re like most people, you probably check your email at least once every day. And if you’re someone whose work involves communication with customers, clients, and coworkers, the chances are that you deal with emails all the time. Even though we spend so much time writing, forwarding, and managing emails, we hardly ever pause for a moment and think about how we could improve our emailing experience. We use clunky web interfaces that are not meant for professional use, we accept outdated applications as if alternatives didn’t exist, and we settle for the default email apps on our mobile devices even though app stores are full of excellent third-party email apps. Broadly speaking, an email client is a computer program used to access and manage a user’s email. But when we use the term email client in this article, we only mean those email clients that can be installed on a desktop computer or a mobile device—not web-based email clients that are hosted remotely and are accessible only from a web browser.
    [Show full text]
  • Broken Breakout Promises
    Broken Breakout Promises Broken Breakout Promises Before co-founding Apple in April 1976, Steve Jobs was one of the To make ends meet in the summer of first 50 employees at Atari, the legendary Silicon Valley game company 1972, Woz, Jobs, and Jobs’ girlfriend took $3-per-hour jobs at the Westgate founded by Nolan Kay Bushnell in 1972. Atari’s Pong, a simple Mall in San Jose, California, dressing up electronic version of ping-pong, had caught on like wildfire in arcades as Alice In Wonderland characters. Jobs and homes across the country, and Bushnell was anxious to come up and Woz alternated as the White Rabbit with a successor. He envisioned a variation on Pong called Breakout, and the Mad Hatter. in which the player bounced a ball off a paddle at the bottom of the screen in an attempt to smash the bricks in a wall at the top. Bushnell turned to Jobs, a technician, to design the circuitry. Initially Jobs tried to do the work himself, but soon realized he was in way over his head and asked his friend Steve Wozniak to bail him out. “Steve wasn’t capable of designing anything that complex. He came .atarihq.com) “He was the only person I met who knew more about electronics than me.” Courtesy of Atari Gaming Headquarters (www Courtesy of Steve Jobs, explaining his initial fascination with Woz “Steve didn’t know very much about electronics.” Conceived by Bushnell, Breakout was originally designed by Wozniak and Jobs. Steve Wozniak For more info, or to order a copy, please visit http://www.netcom.com/~owenink/confidential.html 17 Broken Breakout Promises to me and said Atari would like a game and described how it would work,” recalls Wozniak.
    [Show full text]
  • Porting a Window Manager from Xlib to XCB
    Porting a Window Manager from Xlib to XCB Arnaud Fontaine (08090091) 16 May 2008 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 pub- lished by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". Contents List of figures i List of listings ii Introduction 1 1 Backgrounds and Motivations 2 2 X Window System (X11) 6 2.1 Introduction . .6 2.2 History . .6 2.3 X Window Protocol . .7 2.3.1 Introduction . .7 2.3.2 Protocol overview . .8 2.3.3 Identifiers of resources . 10 2.3.4 Atoms . 10 2.3.5 Windows . 12 2.3.6 Pixmaps . 14 2.3.7 Events . 14 2.3.8 Keyboard and pointer . 15 2.3.9 Extensions . 17 2.4 X protocol client libraries . 18 2.4.1 Xlib . 18 2.4.1.1 Introduction . 18 2.4.1.2 Data types and functions . 18 2.4.1.3 Pros . 19 2.4.1.4 Cons . 19 2.4.1.5 Example . 20 2.4.2 XCB . 20 2.4.2.1 Introduction . 20 2.4.2.2 Data types and functions . 21 2.4.2.3 xcb-util library . 22 2.4.2.4 Pros . 22 2.4.2.5 Cons . 23 2.4.2.6 Example . 23 2.4.3 Xlib/XCB round-trip performance comparison .
    [Show full text]
  • Nix on SHARCNET
    Nix on SHARCNET Tyson Whitehead May 14, 2015 Nix Overview An enterprise approach to package management I a package is a specific piece of code compiled in a specific way I each package is entirely self contained and does not change I each users select what packages they want and gets a custom enviornment https://nixos.org/nix Ships with several thousand packages already created https://nixos.org/nixos/packages.html SHARCNET What this adds to SHARCNET I each user can have their own custom environments I environments should work everywhere (closed with no external dependencies) I several thousand new and newer packages Current issues (first is permanent, second will likely be resolved) I newer glibc requires kernel 2.6.32 so no requin I package can be used but not installed/removed on viz/vdi https: //sourceware.org/ml/libc-alpha/2014-01/msg00511.html Enabling Nix Nix is installed under /home/nixbld on SHARCNET. Enable for a single sessiong by running source /home/nixbld/profile.d/nix-profile.sh To always enable add this to the end of ~/.bash_profile echo source /home/nixbld/profile.d/nix-profile.sh \ >> ~/.bash_profile Reseting Nix A basic reset is done by removing all .nix* files from your home directory rm -fr ~/.nix* A complete reset done by remove your Nix per-user directories rm -fr /home/nixbld/var/nix/profile/per-user/$USER rm -fr /home/nixbld/var/nix/gcroots/per-user/$USER The nix-profile.sh script will re-create these with the defaults next time it runs. Environment The nix-env commands maintains your environments I query packages (available and installed) I create a new environment from current one by adding packages I create a new environment from current one by removing packages I switching between existing environments I delete unused environements Querying Packages The nix-env {--query | -q} ..
    [Show full text]
  • The GNOME Desktop Environment
    The GNOME desktop environment Miguel de Icaza ([email protected]) Instituto de Ciencias Nucleares, UNAM Elliot Lee ([email protected]) Federico Mena ([email protected]) Instituto de Ciencias Nucleares, UNAM Tom Tromey ([email protected]) April 27, 1998 Abstract We present an overview of the free GNU Network Object Model Environment (GNOME). GNOME is a suite of X11 GUI applications that provides joy to users and hackers alike. It has been designed for extensibility and automation by using CORBA and scripting languages throughout the code. GNOME is licensed under the terms of the GNU GPL and the GNU LGPL and has been developed on the Internet by a loosely-coupled team of programmers. 1 Motivation Free operating systems1 are excellent at providing server-class services, and so are often the ideal choice for a server machine. However, the lack of a consistent user interface and of consumer-targeted applications has prevented free operating systems from reaching the vast majority of users — the desktop users. As such, the benefits of free software have only been enjoyed by the technically savvy computer user community. Most users are still locked into proprietary solutions for their desktop environments. By using GNOME, free operating systems will have a complete, user-friendly desktop which will provide users with powerful and easy-to-use graphical applications. Many people have suggested that the cause for the lack of free user-oriented appli- cations is that these do not provide enough excitement to hackers, as opposed to system- level programming. Since most of the GNOME code had to be written by hackers, we kept them happy: the magic recipe here is to design GNOME around an adrenaline response by trying to use exciting models and ideas in the applications.
    [Show full text]
  • The GNOME Census: Who Writes GNOME?
    The GNOME Census: Who writes GNOME? Dave Neary & Vanessa David, Neary Consulting © Neary Consulting 2010: Some rights reserved Table of Contents Introduction.........................................................................................3 What is GNOME?.............................................................................3 Project governance...........................................................................3 Why survey GNOME?.......................................................................4 Scope and methodology...................................................................5 Tools and Observations on Data Quality..........................................7 Results and analysis...........................................................................10 GNOME Project size.......................................................................10 The Long Tail..................................................................................11 Effects of commercialisation..........................................................14 Who does the work?.......................................................................15 Who maintains GNOME?................................................................17 Conclusions........................................................................................22 References.........................................................................................24 Appendix 1: Modules included in survey...........................................25 2 Introduction What
    [Show full text]
  • An User & Developer Perspective on Immutable Oses
    An User & Developer Perspective on Dario Faggioli Virtualization SW. Eng. @ SUSE Immutable OSes [email protected] dariof @DarioFaggioli https://dariofaggioli.wordpress.com/ https://about.me/dario.faggioli About Me What I do ● Virtualization Specialist Sw. Eng. @ SUSE since 2018, working on Xen, KVM, QEMU, mostly about performance related stuff ● Daily activities ⇒ how and what for I use my workstation ○ Read and send emails (Evolution, git-send-email, stg mail, ...) ○ Write, build & test code (Xen, KVM, Libvirt, QEMU) ○ Work with the Open Build Service (OBS) ○ Browse Web ○ Test OSes in VMs ○ Meetings / Video calls / Online conferences ○ Chat, work and personal ○ Some 3D Printing ○ Occasionally play games ○ Occasional video-editing ○ Maybe scan / print some document 2 ● Can all of the above be done with an immutable OS ? Immutable OS: What ? Either: ● An OS that you cannot modify Or, at least: ● An OS that you will have an hard time modifying What do you mean “modify” ? ● E.g., installing packages ● ⇒ An OS on which you cannot install packages ● ⇒ An OS on which you will have an hard time installing packages 3 Immutable OS: What ? Seriously? 4 Immutable OS: Why ? Because it will stay clean and hard to break ● Does this sound familiar? ○ Let’s install foo, and it’s dependency, libfoobar_1 ○ Let’s install bar (depends from libfoobar_1, we have it already) ○ Actually, let’s add an external repo. It has libfoobar_2 that makes foo work better! ○ Oh no... libfoobar_2 would break bar!! ● Yeah. It happens. Even in the best families distros
    [Show full text]