GNOME and the Enterprise User - JDS Ghee Teo & Brian Nitz Sun - - PowerPoint PPT Presentation

gnome and the enterprise user jds
SMART_READER_LITE
LIVE PREVIEW

GNOME and the Enterprise User - JDS Ghee Teo & Brian Nitz Sun - - PowerPoint PPT Presentation

GNOME and the Enterprise User - JDS Ghee Teo & Brian Nitz Sun Microsystems Inc. Introduction Who are we? Intended Audience CTOs, CIOs, Technical managers Software developers Anyone considering developing/deploying a GNOME-based


slide-1
SLIDE 1

GNOME and the Enterprise User - JDS Ghee Teo & Brian Nitz Sun Microsystems Inc.

slide-2
SLIDE 2

Introduction

  • Who are we?
  • Intended Audience

CTOs, CIOs, Technical managers Software developers Anyone considering developing/deploying a GNOME-based desktop

slide-3
SLIDE 3

Agenda

  • Development of Java Desktop System –

behind the scene view

  • Deployment of GNOME on Enterprise –

working in the real world

slide-4
SLIDE 4

Development

  • Java Desktop System
  • It is Desktop System - not Java Destkop
slide-5
SLIDE 5

What we did – in 1 page

  • Got GNOME as the basic desktop
  • Slapped in StarOffice productivities suites
  • Enclosed with Evolution mail client
  • Mixed in Mozilla browser
  • Grabbed GAIM messaging client
  • Mashed in many other Open Sourced Apps
  • Just to provide a well-integrated alternate to

Windows

slide-6
SLIDE 6

Why did we do it?

  • New opportunity on the desktop created by

M$

  • New markets afforded by Linux
  • Mature for Enterprise Transactions users
  • To replace vintage CDE (e.g accessibility)
  • To provide more options to Sun's customers
slide-7
SLIDE 7

Decisions Decisions?

  • Choosing base Deskop
  • Choosing base Operating System
  • Choosing Browser
  • Choosing Mail/Calendar client
  • Choosing Office Suite
  • Branding Choices
  • Other Compromising Choices
slide-8
SLIDE 8
  • GNOME

Choosing the base Desktop

  • KDE

“Easy peasy, Lemon squeecy”

slide-9
SLIDE 9

Choosing base Linux OS

  • Too expensive, competitor
  • Second to RH, Strong in Europe, KDE
  • Community based, long release cycle
slide-10
SLIDE 10

Choosing the key apps

  • Office Suite
  • Browser (Epiphany/Mozilla)
  • Mail/Calendar Client
  • Instant messaging client
slide-11
SLIDE 11

Other Open Source Apps

  • Gnomemeeting
  • GIMP
  • Gtkam
  • Planner (was Mr. Project)
  • Dia
  • totem
slide-12
SLIDE 12

Sun's specific Add Ons

  • Latest JRE, JDK, Developer Tools (JDS R2)
  • Java Web Start
  • Java Media Player (JMF based)
  • Open Sourced Java Apps
  • CUPS printing from XD2
  • Print option in nautilus menu
  • World clock
  • Plugins – Flash, Real, Java
  • Vino (JDS R2)
  • APOC (JDS R2)
slide-13
SLIDE 13

Branding

  • Why the fuss about branding?
  • Perception is reality (almost)
  • Visual differences set us apart
slide-14
SLIDE 14

The Branded Parts

  • Java Desktop System (JDS) – part of
  • verall Branding of Sun's products range
  • 'Launch' not 'Start'
  • Blueprint theme – Java Cup, oval text

boxes, gradient shaped button

  • Java Cup throbbers for Mozilla, Nautilus
  • YaST2 tools
slide-15
SLIDE 15

Building the Distro

  • Figure out all build tools required –

Common Build Envrionment

  • Distributing Common Build Envrionment
  • Automating the Build
slide-16
SLIDE 16

Working out the Build Environment

  • Open Source Open environment =>

Freedom => loose ends

  • One of the messier tasks in creating a new

distro

  • Many Open Source uses different version of

build tools

  • Generally not well-defined CBE
  • Somewhat limitted by the base OS
slide-17
SLIDE 17

Steps In working out Common Build Environrment

  • Install Base OS
  • Install all known build tools from Base OS
  • Download the version Desktop Distro tarballs
  • Create spec files for each module
  • Build desktop components bottom up (make use of

jhbuild)

  • Install built components
  • Get new build tools if needed
  • Continue the process iteratively until all components

required built successfully

  • We have a Common Build Environment for that Release!
slide-18
SLIDE 18

Distributing the Common Build Environment

  • Easy distribution of Common Build

Environment is crucial to global engineering environment

  • Initiation for development and also ensure

correct integration

  • N-1 rule apply
  • Make Easy by YaST Development option
slide-19
SLIDE 19

Automating the Build Process

  • A constant automated build helps discovered

problems earlier

  • Minimise knock on effect on upper stack
  • A set of scripts were developed in house by Release

Engineering

  • Similar to tinderbox
  • Give build results on web page
  • Notify mail alias when failure occurs
  • Nightly build encourages usage and improves quality
slide-20
SLIDE 20

Lessons Learnt

  • Tarballs releases Versus HEAD
  • Patches management
  • Importance of Common Build

Enviroment

slide-21
SLIDE 21

What's New in Release 2

Desktop Software

– Java System Update Services – Improved International Support (Japanese, Korean

Brazilian Portuguese) Management Tools

– Java Desktop System Configuration Mgr, 1 – Sun Control Station 2.1 – Remote Desktop Takeover

Developer Tools (BONUS!)

– Sun Java System Studio Std Tech Preview – NetBeans IDE 3.6 – J2SE SDK

slide-22
SLIDE 22

Java Desktop System