DOCSLIB.ORG

Sugarcrm Architecture Overview Agenda

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Sugarcrm Architecture Overview Agenda SugarCRM Architecture Overview Agenda 1. Architectural Overview – Components, Modules, High Availability 2. Security – Architecture, Application, API 3. Integrate With External Systems – Email, Web Services, Logic Hooks 4. Most Flexible Solution – On-Site, Configuration, Workflow 5. Mobile App – Process, Data, Security, Code SDK Architecture: Overview Capabilities Impact Flexible No constraints around Delivery deployment. You decide Model On Site Sugar On Demand Cloud Platforms Customizable Sugar adapts to the User Interface & user. Not the other way Workflows around Sugar Reporting Use what you need to Modular, Open Sugar Marketing Sugar Sales Sugar Support connect across your Applications Sugar Collaboration business Sugar Platform Tools and Administration 100% visible source Open Source code for inexpensive Architecture customization & support Multiple Avoid ‘forklift’ upgrades Operating and proprietary vendor Systems lock-in Sugar Platform • Flexible and Highly Extensible Platform • Open Web Standards Based • Built Using JavaScript & PHP • Leverages Open-Source Frameworks like backbone.js, jQuery etc. • Follows Classic MVC Architecture • Client Side MVC Framework – “Sidecar” • Metadata Driven • Supports several integration patterns SugarCRM Architecture Presentation Layer (UI) User Advanced User / Sidecar Dashlets Themes Navigation System- Preferences Web Tech. Administrator Business Layer Custom Modules Standard CRM Modules CostumCostumCustom CostumCostumCustom Accounts …. Call Opportunity module module System- modulemodule modulemodule Administrator / Developer Platform SugarBean Reports SugarLogic ModuleBuilder Charting Role Security Authentication Search Workflows Hooks Feeds Team Security System- Scheduler E-Mail Connectors Tracking Logging Documents Administrator Integration Layer Custom (business logic) entry points Generic (CRUD) web services Developer Architecture: SugarCRM Stack Sugar 7 Software Stack Browser Client JavaScript Engine Web Server Scheduler APIs PHP Server File System Memcache Elastic Search Database Scalable and Redundant Tiered Architecture Load Balancer Web Servers Backend Servers Apache Cron Memcache PHP Elastic MySQL APC Search Dedicated File Servers Sugar Files Architecture: System Example Enterprise Implementation Internet Business Data Intelligence & Historical Sources Analytics Data SSO & Security Services SugarCRM CRM Marketing ERP / Supply Corporate DB Automation Chain Applications API, Web Services, Messaging Bus (WebSphere, Tibco, etc.) Employee Product Partner Accounts Contacts Territories Directory Catalog Directory Security © 2017 SugarCRM Inc. All rights reserved. Architecture: Secure App, Secure Data • Secure Web Access – HTTPS & SSL – No other external ports needed • Behind the Firewall – Employ standard Web & DB server security measures – Web server connects to Database server via SQL • Secure Entry Points – Application routinely tested for vulnerabilities – Protected against XSS & SQL injection attacks Example Enterprise Implementation (cont) SSO & Accounts VPN Load Bus( Messaging Web Services, Security Balancer Services Contacts Territorie s SugarCRM SugarCRM etc.) Employee Directory WebSphere Product Catalog CRM Failover , CRM DB Failover DB Tibco DB DB Partner Directory , Federated HA Database Cluster Corporate Data Stores Red Zone Yellow Zone Green Zone Architecture: Secure Sessions • Password Management – Set password strength & aging, create system generated passwords and reCAPTCHA enforced login – Or use LDAP, Active Directory, Oauth or SAML tokens • IP Address Tracking – Session termination if IP address changes – Store all IP addresses used by sessions • One user, one session – Limit to one web session per user login – Prevent session hijacking with session timeouts Security: Authentication • User authentication from external systems • Roles are stored only in Sugar DB LDAP AD SAML SAML Sugar DB Custom Security: Module Access • Module-Level Access Rights based on User Roles • Restrict Actions – Delete, Create/Edit, Export, Import, List, View Security: Row Level Visibility • Users and Teams • Users can only view data if: – They are defined as the owner (Assigned to) – They are a member of a team that owns the record – Somebody that reports to the user directly or is below them on the org chart owns the record. – If row level security is turned off for a specific module, all records can be seen Security: Row Level Actions • Set actions for Editing, Deleting, and Viewing records – All allows everybody who can view the record – Owner allows on the person listed on the owner field to perform action – None disallows anybody for taking this action Security: Audit Trail • Determine what fields you want to audit. Audit trail can be viewed from any record. API Token • OAuth Token Request (Login) • API Returns OAuth Token • Subsequent Calls Require Token Integration © 2017 SugarCRM Inc. All rights reserved. Unlimited API calls (No additional cost) Base Mobile REST API Any App Portal Services Oriented Architecture (SOA) Extensible REST API’s • Truly RESTful – Design Philosophy • Extensible • POST • Create – Leverages HTTP • GET Protocol • Read • PUT • Update – JSON • DELETE Middleware Architecture Intern Business et Intelligen Data Historic ce & Sourc Data Analytics es SSO & Legacy Security Applications Services CRM DB Marketing ERP / Supply Corporate Automation Chain Applications API, Web Services, Middleware Product Account Contact Opportu Leads catalogu Custom s s nity e Integration Options • REST APIs • SOAP APIs Sugar • Middleware • UI Integration (iFrame or callout) • Direct DB Connection Sugar DB • CMIS Compliant Interface Integration Scenarios and Options Examples SOAP/RE Sugar as Provider ST • Read Customer Data from Sugar External • Update Customer Data in Sugar ETL Applicati • Show Opportunity screen in CPQ system on iFrame • Read Sugar data into BW system for reporting Materiali sed DB View Sugar as Consumer • Read Delivery/Invoice/financials data from ERP • Read Quotation data from CPQ SOAP/RE • Read ST • Embed CPQ UI into Sugar UI ES • Show BI Report in Sugar UI B External • Fully Open Standards ETL Applicati Based on iFrame • REST Enabled Modules • New Modules automatically get API Enabled • All CRUD Operations • No API usage costs • Lower TCO API Notes • Fields are automatically available • Configured modules available automatically • Define custom end points • Sudo API available • Metadata API helps drive common UIs Integration: Direct Data Access • Batch upload data to SugarCRM Database – Leverage 3rd party ETL tools such as Talend • Retrieve data real-time from existing relational DB – Oracle, SQL Server, and MySQL supported • Use EAI Infrastructure for data integration – Web services entry point Most Flexible Solution © 2017 SugarCRM Inc. All rights reserved. Run Anywhere: On-Demand, On-Site, Cloud Run Anywhere: Sugar On-Demand • Secure Datacenters – AWS, Santa Clara, California & London, UK – SAS 70 & ISO 27001 – Tier 1 Network with Multiple Providers • High Availability – Redundant server configurations • Offsite Data Storage – Backups taken daily with hourly increments – Archives stored off-site – Data stored in-country (USA or UK) Run Anywhere: On-Site • Traditional On-Premise Installations – Operating Systems: Unix, Linux, Windows or Mac • Any that runs the supported Web Server and PHP versions – Web Server: Apache or IIS – Database Server: MySQL, IBM DB2, MS-SQL Server & Oracle (Q4 2014 for Sugar 7.5) • Tightly Integrate with External Systems – Beyond Web Services: ESB Agents, ODBC Access UI: Web-based Application • Employees love it – Intuitive & Flexible – Easy to customize • Managers gain visibility – Quickly build reports & charts – Limit functionality based on role and need • Executives benefit – Better visibility – Greater insight UI: Mobile Client • Full power of SugarCRM in a mobile footprint • Native & HTML5 • Online & Offline • iOS and Android • Available now UI & Data: Studio • Edit • Fields • Labels • Layouts • Relationships • Dropdowns UI & Data: Sugar Logic • Calculated fields • Calculated date fields • Calculated dropdowns • Dependent dropdowns • Related fields • Related fields in other modules • Upgrade safe, complex customizations using excel like expressions • Another way to enforce process driven workflow UI & Data: Module Builder • Create new • Modules • Fields • Labels • Layouts • Relationships Process: Workflow • Conditions – Based on data in Sugar – Or time elapsed • Alerts – Emails – Pop-ups • Actions – Set data values – Create new tasks or other related objects • Orchestrate your entire business process Advanced Workflow • A Business Process Management (BPM) tool for modeling and executing business processes. • Drives all functionality utilizing server or APIs • Features: – BPMN 2.0 Visual designer – Time and action based Triggers – Approval process flows – Sequential and parallel – Visual status monitoring – Configurable loop detection – Stop/Cancel/Reassign running workflows 39 Real Time Workflow Monitor • Status – Executing – Completed – Stopped • Process Control – Assign – Cancel – Create Task Sugar Mobile App © 2017 SugarCRM Inc. All rights reserved. Sugar Mobile • Platform specific apps – iOS & Android • Offline support • Device Features – Geolocation, voice-to-text, etc. • Fully Extensible – MACS • Change branding, logos, app icons • MDM capable • MobileSDK – Javascript/HTML/CSS – Reuse code from browser (base platform) Fully Mobile Enabled Web Native iOS Android Dashboards Dashboard Activity Charts in Main Menu with
Load more

Recommended publications
  • Release Notes for Fedora 15
    Fedora 15 Release Notes Release Notes for Fedora 15 Edited by The Fedora Docs Team Copyright © 2011 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. 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, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. 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. All other trademarks are the property of their respective owners.
    [Show 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.
    [Show full text]
  • How the Fedora Project Works
    How the Fedora Project works Open Source Days 2013, Copenhagen Robert Scheck Robert Scheck Fedora Package Maintainer and Provenpackager Fedora Ambassador and Ambassador Mentor Part of Fedora Websites and Translation teams Open Source Contributor and Software Developer Mail: [email protected] Web: http://fedoraproject.org/wiki/RobertScheck Open Source Days 2013 – How the Fedora Project works – Robert Scheck History A long, long time ago... ...between 1994 and 2003... ...in a country far, far away... ...Raleigh, North Carolina, US... ...there was a Linux distribution named... Open Source Days 2013 – How the Fedora Project works – Robert Scheck Red Hat Linux Commercially available as box with CDs and printed manual Concurrently available as free download on the Internet New versions released about every 6 months Open Source Days 2013 – How the Fedora Project works – Robert Scheck Problems Less profit with commercially sold boxes Main profit due to large business customers Different product and support life times → Between 18 months and 5 years No stable and reliable base for partners Extreme between innovation vs. stabilization Open Source Days 2013 – How the Fedora Project works – Robert Scheck Answer Split-up into two different Linux distributions: Fedora Core Red Hat Enterprise Linux Open Source Days 2013 – How the Fedora Project works – Robert Scheck Fedora vs. RHEL Free available Subscription Short release cycle: Long release cycle: 6 months 2-3 years Latest software Stable software 13 month support 10-13 years support and product
    [Show full text]
  • Op E N So U R C E Yea R B O O K 2 0
    OPEN SOURCE YEARBOOK 2016 ..... ........ .... ... .. .... .. .. ... .. OPENSOURCE.COM Opensource.com publishes stories about creating, adopting, and sharing open source solutions. Visit Opensource.com to learn more about how the open source way is improving technologies, education, business, government, health, law, entertainment, humanitarian efforts, and more. Submit a story idea: https://opensource.com/story Email us: [email protected] Chat with us in Freenode IRC: #opensource.com . OPEN SOURCE YEARBOOK 2016 . OPENSOURCE.COM 3 ...... ........ .. .. .. ... .... AUTOGRAPHS . ... .. .... .. .. ... .. ........ ...... ........ .. .. .. ... .... AUTOGRAPHS . ... .. .... .. .. ... .. ........ OPENSOURCE.COM...... ........ .. .. .. ... .... ........ WRITE FOR US ..... .. .. .. ... .... 7 big reasons to contribute to Opensource.com: Career benefits: “I probably would not have gotten my most recent job if it had not been for my articles on 1 Opensource.com.” Raise awareness: “The platform and publicity that is available through Opensource.com is extremely 2 valuable.” Grow your network: “I met a lot of interesting people after that, boosted my blog stats immediately, and 3 even got some business offers!” Contribute back to open source communities: “Writing for Opensource.com has allowed me to give 4 back to a community of users and developers from whom I have truly benefited for many years.” Receive free, professional editing services: “The team helps me, through feedback, on improving my 5 writing skills.” We’re loveable: “I love the Opensource.com team. I have known some of them for years and they are 6 good people.” 7 Writing for us is easy: “I couldn't have been more pleased with my writing experience.” Email us to learn more or to share your feedback about writing for us: https://opensource.com/story Visit our Participate page to more about joining in the Opensource.com community: https://opensource.com/participate Find our editorial team, moderators, authors, and readers on Freenode IRC at #opensource.com: https://opensource.com/irc .
    [Show full text]
  • Standard Presentation
    Welcome to Linux ➲ Welcome ➲ Survey Of Class ➲ Logging in ➲ What is a shell? ➲ Using a shell ➲ How to use a command line Welcome ➲ Instructor: Tom Duffy ➲ CA: Hendra Wijaya ➲ Course Materials ➲ Course Outline ➲ Chapter 3, Linux Tutorial ➲ VI Tutorial ➲ "In The Beginning Was The Command Line" ➲ "The Cathedral And The Bazaar" Welcome (cont.) ➲ Class should be interactive ➲ Ask Questions at any time ➲ Let me know if I am going too fast or too slow ➲ One topic required for next topic, so it is really important for every one to keep up ➲ 15 minute break in the middle of class Survey Of Class ➲ Computer Experience (show of hands) ➲ Windows/Mac GUI (I assume all have good to excellent experience) ➲ Inside a computer (Harddrive, CPU, memory, etc.) ➲ Command Line Experience (DOS?) ➲ UNIX or Linux Experience Logging In ➲ Multitasking, Multiuser operating system ➲ Can run many programs at once ➲ Many people can be on same machine at same time ➲ Unlike DOS, where only one person can run one program at one time ➲ Windows NT can run multiple programs at same time, but only one person can be logged in Logging In (part 2) ➲ Each user on a system has a login name ➲ Normally between 2 and 8 characters ➲ Each login name has a password ➲ Only the user should know their password ➲ Normally should be something hard to guess ➲ Please press [Ctrl]-[Alt]-[F1] Logging In (part 3) ➲ Each machine has a hostname ➲ You should see a screen with hostname login: ➲ Here, the login name is "student" and the password is "student" ➲ When you enter your password, nothing
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • Hydrogeology, Water Quality, Water Budgets, and Simulated Responses
    USGS science for a changing world Q. I Hydrogeology, Water Quality, Water Budgets, to and Simulated Responses to Hydrologic Changes in o o30 CD o Santa Rosa and San Simeon Creek Ground-Water Basins, CD < San Luis Obispo County, California 30 C I m 30 cCO o mCT CO CO o CD U.S. GEOLOGICAL SURVEY CO-D Water-Resources Investigations O O Report 98-4061 O >o o 30 CO O CO 30 30 CO Prepared in cooperation with the SAN LUIS OBISPO COUNTY FLOOD CONTROL AND WATER CONSERVATION DISTRICT Hydrogeology, Water Quality, Water Budgets, and Simulated Responses to Hydrologic Changes in Santa Rosa and San Simeon Creek Ground-Water Basins, San Luis Obispo County, California By Eugene B.Yates and Kathryn M. Van Konyenburg U.S. GEOLOGICAL SURVEY Water-Resources Investigations Report 98-4061 Prepared in cooperation with the SAN LUIS OBISPO COUNTY FLOOD CONTROL AND WATER CONSERVATION DISTRICT ON O Sacramento, California 1998 U.S. DEPARTMENT OF THE INTERIOR BRUCE BABBITT, Secretary U.S. GEOLOGICAL SURVEY Thomas J. Casadevall, Acting Director The use of firm, trade, and brand names in this report is for identification purposes only and does not constitute endorsement by the U.S. Geological Survey. For additional information write to: Copies of this report can be purchased from: District Chief U.S. Geological Survey U.S. Geological Survey Information Services Placer Hall, Suite 2012 Box 25286 6000 J Street Federal Center Sacramento, CA 95819-6129 Denver, CO 80225 CONTENTS Abstract................................................................................................................................................................................
    [Show full text]
  • Support and Typical Problems
    Hill_ch06.ps 7/18/06 4:32 PM Page 183 CHAPTER 6 Support and Typical Problems Your System Applications 6 Multimedia Networking Hardware System Administration Other Summary 183 Hill_ch06.ps 7/18/06 4:32 PM Page 184 DESPITE THE FACT that the Ubuntu developers work tirelessly to make the Ubuntu user experience as fluid and problem-free as possible, there are always going to be bugs, glitches, and errors in software. This is nothing unique to Ubuntu; it is a characteristic that is applied to all software. Any- thing created by humans is subject to error. One of the many benefits of the Open Source development process is that errors and bugs are typically reported, found, and fixed in a far shorter time frame than is the case with proprietary software. This ensures that the software included with Ubuntu is far more solid and stable than some pro- prietary alternatives. Although bugs are typically fixed quickly, there is still the case of user error. Even if a piece of software is completely bug-free, it can be used incorrectly, be misconfigured, or otherwise not work as expected. This is perfectly normal, and the aim of this chapter is to discuss some of the most common problems faced by users and explore how to fix or otherwise resolve these issues. This chapter is presented in a cookbook format, presenting each problem followed by a concise solution. If you have read through the other chapters in the book and not found the solution in this chapter, the next option is to try the superb Ubuntu Forums at www.ubuntuforums.org/.
    [Show full text]
  • Fedora: Una Distribuzione GNU/Linux Al Passo Coi Tempi Pag
    Fedora Una distribuzione GNU/Linux al passo coi tempi Fedora: Una distribuzione GNU/Linux al passo coi tempi Pag. 1 di 16 Introduzione • Leggendo di qui e di la, parlando con sviluppatori e amici che bazzicano nel settore GNU/Linux & C. ho avuto la percezione che le informazioni su Fedora siano, come minimo, superficiali. • Questo perché, a mio avviso (IMHO si direbbe nel gergo digitale), spesso non si ha il tempo o l’occasione di approfondire l’argomento. • E allora ecco perché ho colto l’occasione di questo GNU/Linux Day per parlare un po della distribuzione che personalmente utilizzo come Sistema Operativo di lavoro e casalingo, Fedora, appunto. Fedora: Una distribuzione GNU/Linux al passo coi tempi Pag. 2 di 16 Fedora: chi la fa e quale è il suo scopo • Iniziamo subito col capire chi la fa e quale è il suo scopo, in modo da poterne comprendere e forse apprezzare le sue caratteristiche, comprendendo in questo modo alcune scelte effettuate dalla comunità Fedora per il confezionamento e distribuzione. • Per semplificare al massimo,si può dire che Fedora è la beta di RedHat Enterprise che è il sistema operativo, Open Source, commerciale di RedHat. • In cambio RedHat fornisce supporto in termini di denaro, strutture e risorse umane al progetto Fedora e a tutta la comunità Open Source mondiale. • Un altra caratteristica di Fedora è che è totalmente Open, quindi Fedora, appena installata, sarà composta al 100% da software Open Source aggiornato all’ultima versione, non saranno presenti in quel caso driver e applicazioni basati su sorgenti “chiusi” e proprietari.
    [Show full text]
  • Debian and Ubuntu
    Debian and Ubuntu Lucas Nussbaum lucas@{debian.org,ubuntu.com} lucas@{debian.org,ubuntu.com} Debian and Ubuntu 1 / 28 Why I am qualified to give this talk Debian Developer and Ubuntu Developer since 2006 Involved in improving collaboration between both projects Developed/Initiated : Multidistrotools, ubuntu usertag on the BTS, improvements to the merge process, Ubuntu box on the PTS, Ubuntu column on DDPO, . Attended Debconf and UDS Friends in both communities lucas@{debian.org,ubuntu.com} Debian and Ubuntu 2 / 28 What’s in this talk ? Ubuntu development process, and how it relates to Debian Discussion of the current state of affairs "OK, what should we do now ?" lucas@{debian.org,ubuntu.com} Debian and Ubuntu 3 / 28 The Ubuntu Development Process lucas@{debian.org,ubuntu.com} Debian and Ubuntu 4 / 28 Linux distributions 101 Take software developed by upstream projects Linux, X.org, GNOME, KDE, . Put it all nicely together Standardization / Integration Quality Assurance Support Get all the fame Ubuntu has one special upstream : Debian lucas@{debian.org,ubuntu.com} Debian and Ubuntu 5 / 28 Ubuntu’s upstreams Not that simple : changes required, sometimes Toolchain changes Bugfixes Integration (Launchpad) Newer releases Often not possible to do work in Debian first lucas@{debian.org,ubuntu.com} Debian and Ubuntu 6 / 28 Ubuntu Packages Workflow lucas@{debian.org,ubuntu.com} Debian and Ubuntu 7 / 28 Ubuntu Packages Workflow Ubuntu Karmic Excluding specific packages language-(support|pack)-*, kde-l10n-*, *ubuntu*, *launchpad* Missing 4% : Newer upstream
    [Show full text]
  • Displaying Augmented Reality Content on Hololens Environment
    Minja Silvennoinen Displaying Augmented Reality content on HoloLens environment Metropolia University of Applied Sciences Bachelor of Engineering Information and Communication Technology Thesis 17 September 2017 Abstract Minja Silvennoinen Author Displaying augmented reality content on HoloLens environ- Title ment Number of Pages 40 pages Date 17 September 2017 Degree Bachelor of Engineering Degree Programme Information and Communication Technology Specialisation option Game Applications Otto Laurila (Arilyn) Instructors Antti Laiho (Senior Lecturer) Thesis was done for digital communication company Arilyn, which uses augmented reality for creating interactive media. The goal of the thesis was to convert Arilyn mobile applica- tion for Microsoft’s HoloLens. The application should support basic data types and have a visual appearance similar to Arilyn mobile application. The first part of thesis concentrates on general research about augmented reality and Ho- loLens technologies. Next the content creation process for HoloLens is described and best practices for augmented reality applications are considered. Last part concentrates on the actual converting process from Arilyn mobile application to Arilyn for HoloLens. Arilyn for HoloLens includes almost all the predefined features. It supports image, video and sound files. The only datatype that is missing is 3D models. HoloLens uses different texture compression than smartphones, so the support for this type needs to be added to Arilyn Manager. During the conversion process, it was noted that target-based augmented reality is not the most suitable for HoloLens device. HoloLens renders dark colors transparent which some- times leads to a situation where the content seems it is positioned behind the target. An- other problem was how the user’s eye focuses on the content.
    [Show full text]
  • TUGBOAT Volume 33, Number 2 / 2012 TUG 2012 Conference
    TUGBOAT Volume 33, Number 2 / 2012 TUG 2012 Conference Proceedings TUG 2012 130 Conference program, delegates, and sponsors 132 David Latchman / TUG 2012: A first-time attendee 138 Roundtable discussion: TEX consulting Typography 146 David Walden / My Boston: Some printing and publishing history 156 Boris Veytsman and Leyla Akhmadeeva / Towards evidence-based typography: First results 158 Federico Garcia / TEX and music: An update on TEXmuse A L TEX 165 LATEX Project Team / LATEX3 news, issue 8 167 David Latchman / Preparing your thesis in LATEX 172 Peter Flynn / A university thesis class: Automation and its pitfalls 178 Bart Childs / LATEX source from word processors Software & Tools 184 Richard Koch / The MacTEX install package for OS X 192 Boris Veytsman / TEX and friends on a Pad 196 Pavneet Arora / YAWN —ATEX-enabled workflow for project estimation 199 Didier Verna / Star TEX: The Next Generation 209 Bob Neveln and Bob Alps / Adapting ProofCheck to the author’s needs Graphics 213 Michael Doob and Jim Hefferon / Approaching Asymptote Macros 219 Amy Hendrickson / The joy of \csname...\endcsname Abstracts 225 TUG 2012 abstracts (Cheswick, Garcia, Henderson, Mansour, Mittelbach, Peter, Preining, Robertson, Thiele) 227 Die TEXnische Kom¨odie: Contents of issues 2–3/2012 228 ArsTEXnica: Contents of issue 13 (2012) 229 MAPS: Contents of issue 42 (2011) Hints & Tricks 230 Karl Berry / The treasure chest Book Reviews 232 Boris Veytsman / Book review: About more alphabets: The types of Hermann Zapf Advertisements 233 TEX consulting and production services TUG Business 235 TUG institutional members News 235 TEX Collection 2012 236 Calendar TEX Users Group Board of Directors TUGboat (ISSN 0896-3207) is published by the TEX Donald Knuth, Grand Wizard of TEX-arcana † Users Group.
    [Show full text]