Understanding the Evolution of Socio-Technical Aspects in Open Source Ecosystems: an Empirical Analysis of GNOME

Total Page:16

File Type:pdf, Size:1020Kb

Understanding the Evolution of Socio-Technical Aspects in Open Source Ecosystems: an Empirical Analysis of GNOME UMONS Faculté des Sciences Département d’Informatique Understanding the Evolution of Socio-technical Aspects in Open Source Ecosystems: An Empirical Analysis of GNOME Mathieu Goeminne A dissertation submitted in fulfillment of the requirements of the degree of Docteur en Sciences Advisor Jury Dr. TOM MENS Dr. XAVIER BLANC Université de Mons, Belgium Université de Bordeaux 1, France Dr. VÉRONIQUE BRUYÈRE Université de Mons, Belgium Dr. JESUS M. GONZALEZ-BARAHONA Universidad Rey Juan Carlos, Spain Dr. TOM MENS Université de Mons, Belgium Dr. ALEXANDER SEREBRENIK Technische Universiteit Eindhoven, The Netherlands Dr. JEF WIJSEN Université de Mons, Belgium June 2013 Acknowledgments This work could have never been completed without the support of many people. First things first, I would like to thank Dr. Tom Mens for his help throughout the years. He provided me advice and support, and helped me to grow up professionally and personally. He forced me to surpass myself, and I would like to thank him warmly for that. I would thank the other members of my jury: Dr. Xavier Blanc, Dr. Véronique Bruyère, Dr. Jesus M. Gonzalez-Barahona, Dr. Alexander Serebrenik, and Dr. Jef Wijsen. All of them have positively influenced my vision of the world and left their mark on me. Thank you for the time you have given me. I hope I will have the pleasure to continue to work with you in the future. I would also like to thank Bogdan Vasilescu, who co-authored a journal article from which a chapter of this dissertation has been extracted. Thank you for your collaboration and your precious advices. I wish to thank my friends and my colleagues who offered me so many joy and who regularly proved me that there is a life apart from the thesis! Special thanks go to my family for their encouragement and for being present in my life. To all of you: Thank you for being on my side during this crazy adventure. Finally, I would like to thank my wife Nadège and my son Antoine. I’m sorry for the too many hours I have passed far away, even when I was sitting close to you. Thank you for your unconditional support. Abstract Since the 70’s, software development has experienced an exponential growth. The number of developed software products, their size and their complexity has become so important that understanding their functioning and managing their evolution have become very hard today. Open source software (OSS) does not escape from this growth and the problems it raises. For more than a decade, OSS systems have been the subject to an increasing interest from the academic community, individuals and the software industry at large, and their development is booming because of their low cost of use (OSS systems are generally freely available), their low barriers to entry for the developers, their low cost of development (they may be built by reusing other OSS systems), and the large quantity of easily available historical data. Contrary to the traditional commercial and proprietary software, OSS is typically de- veloped by a group of persons dispersed all over the world. This geographical distribution forces contributors to use tools allowing an asynchronous communication and an informa- tion exchange over big space scales. The public availability of the historical data being handled by these tools facilitates the analysis of OSS evolution. Initially, empirical analysis of OSS projects evolution was limited to the study of source code evolution only. Later, other software development artefacts have been taken into account as well. For instance, the first analyses of OSS project mailing lists date to 2002 [157]. However, the main factor that drives the evolution of a software project is the people contributing to it. Hence, in order to better comprehend how OSS projects evolve, one needs to gain a better insight in the socio-technical aspects that surrounding them. In order to get a more accurate model of the interaction between the project contributors one needs to consider development artefacts that contain information about its social aspects, such as bug reports, e-mail discussions and version commits. Frequently, collections of different projects are developed and evolve together in the same environment. We refer to these collections as software ecosystems. Since the con- tributors to the projects belonging to these ecosystems work together towards a common goal, they tend to form de facto communities. It is therefore important to study the so- cial aspects not only at the level of individual projects, but also at the level of the entire ecosystem. The goal of this dissertation is to understand the evolution of the social aspects in open source ecosystems. More precisely, we study how contributors to open source ecosystems can be grouped in different communities that evolve and collaborate in different ways. In doing so, we provide evidence that contributors have specificities that are not taken into account by today’s analysis tools. Becoming aware of these specificities opens up new research and practically relevant questions on how new automated tools can be designed and used to offer better support to the ecosystem’s contributors in their activities. The contributions of this dissertation are manifold. We developed an application framework that allows us to empirically study the evolution of software ecosystems. Fo- cusing on the GNOME ecosystem, we designed a systematic approach for detecting the multiple accounts used by contributors to access the software repositories and used it to gain a better insight in the communities belonging to the ecosystem. We defined objec- tive criteria according to which these contributors can be categorised. In the GNOME history we observed a power law behaviour between the number of contributors and their contributions, in term of commits submitted, mails sent and bug reports handled. With further statistical analyses we established correlations and trends between the contribu- tors’ effort, their favourite means of communication and the activity types in which they are involved. For example, we observed that the contributors tend to restrict themselves to a limited number of activity types, but the more active a contributor is, the more he tends to spread his effort over different types of activity. When studying the evolution of GNOME contributors, we observed a tendency of specialisation towards less activity types. We also observed that, during the last years, the effort in each of the studied activity types is decreasing. Résumé Depuis les années 70, le développement logiciel connaît une croissance exponentielle. Le nombre de produits logiciels développés, leur taille et leur complexité sont devenus si im- portants que la compréhension de leur fonctionnement et la gestion de leur évolution sont devenues très difficiles de nos jours. Les logiciels open source (OSS) n’échappent pas à cette croissance ni aux problèmes qu’elle pose. Depuis plus d’une décennie, les systèmes open source font l’objet d’un intérêt croissant de la communauté académique, des parti- culiers et de l’industrie logicielle en général. Leur développement explose du fait de leur faible coût d’utilisation (les systèmes open source sont généralement librement accessi- bles), leur faible ticket d’entrée pour les développeurs, leur faible coût de développement (ils peuvent être construits en réutilisant d’autres systèmes open source), ainsi que la grande quantité de données historiques pouvant être aisément obtenues. Contrairement aux logiciels commerciaux et propriétaires traditionnels, les logiciels open source sont typiquement développés par un groupe de personnes dispersées à travers le monde. Cette distribution géographique oblige les contributeurs à utiliser des outils permettant une communication asynchrone et l’échange d’informations sur de grandes distances. La mise à disposition publique des données historiques gérées par ces outils facilite l’analyse de l’évolution des logiciels open source. Initialement, l’analyse empirique de l’évolution des projets open source était limitée à l’étude de l’évolution du code source. Par la suite, d’autres artefacts de développement logiciel ont été pris en compte. Par exemple, les premières analyses des listes de diffusion des projets open source datent de 2002 [157]. Cependant, les personnes contribuant à un projet logiciel en constituent le principal vecteur d’évolution. Ainsi, afin de mieux comprendre la manière dont les projets open source évoluent, il est nécessaire d’avoir un meilleur aperçu des aspect socio-techniques qui l’entourent. Afin d’avoir un modèle plus précis et plus juste des interactions existant entre les contributeurs du projet, il est nécessaire de considérer les artefacts de développement qui contiennent de l’information relative à ses aspects sociaux, tels que les rapports d’erreur, les discussions par e-mail et les commits de version. Fréquemment, des projets logiciels sont développés et évoluent ensemble dans le même environnement. Nous appelons de telles collections de projets des écosystèmes logiciels. Dans la mesure où les contributeurs des projets appartenant à ces écosystèmes travaillent ensemble dans un but commun, ils ont tendance à former de facto des communautés. Il est donc important d’étudier les aspects sociaux non seulement au niveau des projets individuels, mais également au niveau de l’écosystème dans son ensemble. L’objectif de cette thèse est de comprendre l’évolution des aspects sociaux des écosys- tèmes open source. Plus précisément, nous étudions la manière dont les contributeurs impliqués dans les écosystèmes open source peuvent être groupés en différentes commu- nautés qui évoluent et collaborent de différentes manières. De la sorte, nous apportons des indices probants selon lesquels les contributeurs ont des spécificités qui ne sont pas prises en compte par les outils d’analyses actuels. La prise de conscience de ces spécificités laisse entrevoir de nouvelles questions de recherche et de nouvelles pratiques sur la manière de concevoir de nouveaux outils automatisés aidant plus efficacement les contributeurs de l’écosystème dans la réalisation de leurs activités.
Recommended publications
  • 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]
  • Opensuse :: Les Applications Utiles
    Applications Les applications utiles e nombreuses applications sont supprimer ou actualiser des logiciels, tout se disponibles par défaut sous open- passe par YaST et ses différents modules. DSUSE. Certaines dépendantes de Le point de départ est le Centre de contrôle votre bureau (KDE ou GNOME) et d’autres YaST2. Pour y accéder, sous GNOME depuis qui sont disponibles par défaut sur les deux le menu Ordinateur, cliquez sur YaST et sous bureaux, comme Firefox par exemple. Cet KDE, depuis le menu K (la tête de caméléon article vous guidera à travers les différen- du tableau de bord), onglet Ordinateur, cli- tes applications utiles installées par défaut quez sur YaST. Ce Centre de contrôle regrou- sous openSUSE 11.1. pe tous les modules de YaST. Bien souvent, le choix entre une applica- Ceux utilisés le plus souvent sont sans tion disponible sous GNOME et celle dispo- aucun doute les modules de gestion de pa- nible sous KDE se fait par le choix du bureau quets. Pour commencer, il faut savoir gérer lui-même. Si un utilisateur préfère GNOME à les dépôts. Un dépôt de logiciels (software KDE, il utilisera sans doute l’application dis- repository en anglais), souvent abrégé en ponible sous GNOME et non celle de KDE dépôt, est un élément contenant des pa- bien qu’il soit possible de l’installer et de quets logiciels et des informations sur leurs l’utiliser tout en restant sous GNOME. En dépendances vis à vis d’autres paquets. effet, les applications offrent, la plupart du Ces dépôts sont le plus souvent sur Internet, temps, des fonctionnalités très similaires et appelés alors dépôts en ligne, mais ils peu- bien souvent, seule l’aspect diffère du point vent aussi être sur un CD, un DVD ou encore de vue de l’utilisateur.
    [Show full text]
  • Fedora 14 User Guide
    Fedora 14 User Guide Using Fedora 14 for common desktop computing tasks Fedora Documentation Project User Guide Fedora 14 User Guide Using Fedora 14 for common desktop computing tasks Edition 1.0 Author Fedora Documentation Project [email protected] Copyright © 2010 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.
    [Show full text]
  • Brave Gnu World
    LINUXCOVERCOMMUNITY USERSTORY SchlagwortSchlagwortBrave GNU sollte Worldsollte hier hier stehen stehen Schlagwort sollte hier stehen COVER STORY The Monthly GNU Column BRAVE GNU WORLD This column looks into projects and current affairs in the world of free software from the perspective of the GNU Project and the FSF. In this issue, I’ll focus on Comspari and the EU decision on software patents. BY GEORG C.F. GREVE n the past, the German government the Kroupware project in 2002. The pub- principles back to front. For example, has often caused a (positive) stir due lic tender by the BSI was aimed to pro- many other solutions are based on the Ito its activities with free software. duce a groupware solution that would principle that the server is the king of The Federal Ministry of the Economy support strong cryptography and inte- the hill and the users have to bow down (BMWi) sponsored Gnupg [1], for exam- grate seamlessly into a heterogeneous and worship it. The Kolab server does ple. Add to this a number of accompany- environment. things differently. The program makes ing activities, such as a report by the The government office gave a consor- the user king, and gives the user power Bavarian Accounts Office, the KBST let- tium comprising Erfrakon, Klarälvdalens to do things. The software simply helps ter, and the highly acclaimed migration Datakonsult [2], and Intevation [3] the coordinate things as a central intermedi- guide by the Federal Ministry of the Inte- task of developing the software. Inter- ary. rior (BMI). nally, the design and the software was Kolab 1 combined so-called partial referred to as Kolab 1.
    [Show full text]
  • Openmagazin 11/2011
    Nenechte si ujít nové číslo 1 Přihlásit 1 0 2 d a p o t s i l Jak ušetřit? Líbí se vám openMagazin? Snažíme se, abyste dostali kvalitní informace, dozvěděli se něco nového a mohli číst cestou do školy nebo do práce. OpenMagazin děláme pro vás! Kdybyste nás chtěli pochválit nebo nám poděkovat přečtěte si článek na adrese www.openmagazin.cz/ ctenari – děkujeme! http://www.openmagazin.cz/podileji­se/ .. Produkuje: za podpory 4 Co se děje ve světě Linuxu a open source 6 Minecraft – fantazii se meze nekladou Přispívají: 9 Sedm výhod Linuxu 12 Voláme pomocí programu Ekiga 14 Finanční srovnání Windows a Ubuntu 18 Placení autorských poplatků z GUI 22 Analýza: Několik pádných důvodů, proč používat GNU/Linux 26 GNOME 3.2: Leštění začalo 31 Linuxová počítačová učebna: Výukové programy a hry pro děti mateřských a základních škol prvního stupně 34 Ze světa aplikací Mozilla 35 Vytváranie šablón a ich formátovanie 37 Přizpůsobte si OpenOffice.org/LibreOffice svým reálným potřebám 41 Vkladanie obrázkov do dokumentu a práca s nimi 44 Měsíc s vývojovou sadou N950 48 Co do Linuxu na gymnáziu? 52 Mandriva 2011 jde ve stopách Ubuntu 55 Jak na seznamy ve Scribusu 56 Jak číslovat stránky ve Scribusu LinuxAlt 2011 5.–6. listopadu, Brno-Královo pole O magazínu: Šéfredaktorka: Irena Šafářová – OpenOffice.org Licence: Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported, což zna- Jazyková korektura: Petr Novotný – OpenOffice.org mená, že jej smíte šířit, ale nesmíte měnit ani komerčně využívat. Autorská práva náleží autorům Sazba: Michal Hlavatý – Scribus článků. Návrh loga: Martin Kopta – Inkscape | 2 Sedm výhod Linuxu strana 8 e c ? í t i s ř ě t e m š a Voláme pomocí u m programu Ekiga k é a Finanční srovnání T J Windows a Ubuntu Placení autorských poplatků z GUI Analýza: Několik pádných důvodů, proč používat GNU/Linux Co do Linuxu na gymnáziu? .
    [Show full text]
  • Lista Ofrecida Por Mashe De Forobeta. Visita Mi Blog Como Agradecimiento :P Y Pon E Me Gusta En Forobeta!
    Lista ofrecida por mashe de forobeta. Visita mi blog como agradecimiento :P Y pon e Me Gusta en Forobeta! http://mashet.com/ Seguime en Twitter si queres tambien y avisame que sos de Forobeta y voy a evalu ar si te sigo o no.. >>@mashet NO ABUSEN Y SIGAN LOS CONSEJOS DEL THREAD! http://blog.newsarama.com/2009/04/09/supernaturalcrimefightinghasanewname anditssolomonstone/ http://htmlgiant.com/?p=7408 http://mootools.net/blog/2009/04/01/anewnameformootools/ http://freemovement.wordpress.com/2009/02/11/rlctochangename/ http://www.mattheaton.com/?p=14 http://www.webhostingsearch.com/blog/noavailabledomainnames068 http://findportablesolarpower.com/updatesandnews/worldresponsesearthhour2009 / http://www.neuescurriculum.org/nc/?p=12 http://www.ybointeractive.com/blog/2008/09/18/thewrongwaytochooseadomain name/ http://www.marcozehe.de/2008/02/29/easyariatip1usingariarequired/ http://www.universetoday.com/2009/03/16/europesclimatesatellitefailstoleave pad/ http://blogs.sjr.com/editor/index.php/2009/03/27/touchinganerveresponsesto acolumn/ http://blog.privcom.gc.ca/index.php/2008/03/18/yourcreativejuicesrequired/ http://www.taiaiake.com/27 http://www.deadmilkmen.com/2007/08/24/leaveusaloan/ http://www.techgadgets.in/household/2007/06/roboamassagingchairresponsesto yourvoice/ http://blog.swishzone.com/?p=1095 http://www.lorenzogil.com/blog/2009/01/18/mappinginheritancetoardbmswithst ormandlazrdelegates/ http://www.venganza.org/about/openletter/responses/ http://www.middleclassforum.org/?p=405 http://flavio.castelli.name/qjson_qt_json_library http://www.razorit.com/designers_central/howtochooseadomainnameforapree
    [Show full text]
  • Article Format (Pdf)
    [Script=Arabic]XB Zar BC-isit442 Class Overview And Structure Document #PLPC-120048 Version 0.1 January 05, 2016 This Document is Available on-line at: http://mohsen.banan.1.byname.net/PLPC/120048 Mohsen BANAN Email: http://mohsen.1.banan.byname.net/contact Contents I Introductions 1 1 Class Information 1 2 About Me 1 3 About You 1 II Relevant Concepts Review 1 4 Relevant Concepts Review 1 III Class Structure And Class Overview 2 5 Class Structure 2 5.1 Theory: Model, Terminology, Protocols ................................... 2 5.2 Practice: Hands-On .............................................. 2 6 Class Overview 2 6.1 Basic Model for email (Inter-personal Message Handeling System (MHS) ................ 2 6.2 Some Basic MHS (email) Terminology Review ............................... 2 6.3 MTA Comparisons – qmail is our choice of ultimate MTA ......................... 4 6.4 The ByStar Mail Server Configuration – Hosted And In-House ...................... 4 6.5 The Right qmail Autonomous Client Configuration ............................ 4 IV Assignments And Grading 4 7 Assignment 4 7.1 Main Quarter Assignments .......................................... 4 7.2 This Week’s Assignment ........................................... 4 8 Grading 4 V Class Activities 7 9 Virtualization 7 ii 10 Obtaining Your VM Player and Your VM Images 7 10.1 About Virtual Machines Players And Virtual Machines Images ...................... 7 10.2 Virtualization Technology Choices ...................................... 7 10.3 Obtaining Your VM Player/s ......................................... 7 10.4 Obtaining Your VM Image .......................................... 7 11 Starting Your VM – Configurations and Logging In 8 11.1 Preparing Your VM .............................................. 8 11.2 Configuring Your VM ............................................. 8 12 Emacs 8 12.1 What Is Emacs? ................................................ 8 12.2 What Is Blee? ................................................
    [Show full text]
  • Microsoft Exchange Server - Wikipedia, the Free Encyclopedia Page 1 of 15
    Microsoft Exchange Server - Wikipedia, the free encyclopedia Page 1 of 15 Microsoft Exchange Server From Wikipedia, the free encyclopedia Microsoft Exchange Server is Microsoft Exchange Server the server side of a client–server, collaborative application product Developer(s) Microsoft Corporation developed by Microsoft. It is part of the Microsoft Servers line of Initial release April 11, 1993 server products and is used by Stable release Microsoft Exchange Server 2010 SP2 enterprises using Microsoft [1] infrastructure products. / December 4, 2011 Exchange's major features consist Development status Active of electronic mail, calendaring, contacts and tasks; that work with Programming language used C and C++ Microsoft Outlook on PC and Operating system Microsoft Windows Mac, wireless synchronization of email, calendar, contacts with Platform x86-64 (64-bit) major mobile devices and Translation available Multilingual browser-based access to information; and support for data Type Collaborative software storage. License Proprietary (MS-EULA) Website www.microsoft.com/exchange Contents (http://www.microsoft.com/exchange) ■ 1 History ■ 1.1 Exchange 1.0 ■ 1.2 Exchange Server 4.0 ■ 1.3 Exchange Server 5.0 ■ 1.3.1 Exchange Server 5.5 ■ 1.4 Exchange 2000 Server ■ 1.5 Exchange Server 2003 ■ 1.5.1 Editions ■ 1.6 Exchange Server 2007 ■ 1.6.1 New features ■ 1.7 Exchange Server 2010 ■ 2 Clustering and high availability ■ 3 Licensing ■ 4 Exchange Hosting ■ 5 Exchange Online ■ 5.1 History ■ 6 Clients http://en.wikipedia.org/wiki/Microsoft_Exchange_Server 7/27/2012 Microsoft Exchange Server - Wikipedia, the free encyclopedia Page 2 of 15 ■ 6.1 ActiveSync ■ 7 See also ■ 8 References ■ 9 Further reading ■ 10 External links History Planning the migration from Microsoft's internal "legacy XENIX -based messaging system" to the Exchange Server environment began in April 1993, [2] and the process was completed in the late 1996 when the last XENIX server on the MS corporate backbone had been removed.
    [Show full text]
  • Einstieg in Linux – Linux Verstehen Und Einsetzen 422 Seiten, Broschiert, Mit DVD, 6
    Wissen, wie’s geht. Leseprobe Sie möchten in die Linux-Welt eintauchen? Wir zeigen Ihnen, wie es geht! Diese Leseprobe fängt bei null an und hilft Ihnen beim Start mit Ihrem ersten Linux-System. Außerdem können Sie einen Blick in das vollständige Inhalts- und Stichwortverzeichnis des Buches werfen. »Einleitung« »Installationsvorbereitung« »Installation« »Der Linux-Desktop« Inhalt Index Die Autoren Leseprobe weiterempfehlen Steffen Wendzel, Johannes Plötner Einstieg in Linux – Linux verstehen und einsetzen 422 Seiten, broschiert, mit DVD, 6. Auflage 2014 24,90 Euro, ISBN 978-3-8362-2975-3 www.galileo-press.de/3667 Kapitel 1 1 Einleitung »Der Anfang ist der schwerste Teil der Arbeit.« –Platon 1.1 Was ist Linux? Das fängt ja gut an. Da will man ein Buch schreiben und weiß nicht einmal, wie man das Thema grob umreißen soll. Dabei könnte alles so einfach sein – wir schreiben doch nur über ein Betriebssystem, das eigentlich keines ist, und über einen Begriff, der nicht mehr nur Technik, sondern mittlerweile eine ganze Philosophie umschreibt. Neugierig? Zu Recht! Kurz gesagt steht der Begriff Linux heute für ein sehr stabiles, schnelles, freies, UNIX-ähnliches Betriebssystem – obwohl Linux streng genommen nur der Kern (»Kernel«) dieses Betriebssystems ist. Doch eins nach dem anderen! Die Entwicklung von Linux begann 1991, als sich der finnische Student Linus Torvalds an die Programmierung eines Betriebssystemkerns machte. Und weil ein Betriebssys- temkern natürlich nicht so trivial zu programmieren ist, ließ er sich kurzerhand von anderen helfen. Damit das Ganze fair zuging, veröffentlichte Torvalds den Code unter der GNU General Public Licence, kurz GPL. Diese Lizenz besagt, dass jeder das Programm, das durch diese Lizenz geschützt wird, nach Belieben verändern und verbessern kann – mit einer Einschränkung: Das veränderte bzw.
    [Show full text]
  • Aboard Openchange Deck
    Contents 1 Welcome aboard OpenChange Deck 2 MAPI Library Features 3 OCPF Library 4 MOCABOX Project 5 Conclusion Part Welcome aboard OpenChange Deck 1 1 Welcome aboard OpenChange Deck . Provides a portable Open Source implementation of Microsoft Exchange Server and Exchange protocols. Exchange is a groupware server designed to work with Microsoft Outlook providing a messaging server, shared calendars, contact databases, public folders, notes and tasks. OpenChange is working on two different aspects: Interoperability with Exchange protocols Transparent replacement to Microsoft Exchange Server with native Exchange protocols support and direct communication with Microsoft Outlook. 1 Welcome aboard OpenChange Deck Built over Samba4 infrastructure Relies on a limited set of Samba4 libraries: dcerpc and ndr for MSRPC transport talloc for Memory Allocation ldb for storage Server side designed as samba4 loadable plugins Client-side designed as stand-alone libraries calling samba4 OpenChange is 5 years old 1 Welcome aboard OpenChange Deck Client and server difference explained Libmapi: client-side library only Enable clients to communicate with a real Exchange server Implements Exchange protocols: NSPI protocol implementation: address book, name resolution EMSMDB protocol implementation: message store OpenChange Server: Doesn't use libmapi but implements providers Implements the NSPI provider (EMSABP) Doesn't implement the message store yet 1 Welcome aboard OpenChange Deck What's new since Samba XP 2007? Almost everything
    [Show full text]
  • Bien Démarrer Avec Gnupg
    Bien démarrer avec GnuPG Damien Goutte-Gattat <[email protected]> Copyright © 2020 Damien Goutte-Gattat 2020/05/21 Table des matières 1. Installation de GnuPG ............................................................................................ 1 2. Générer sa clef ...................................................................................................... 2 3. Que faire après avoir créé sa clef ? ........................................................................ 4 3.1. Sauvegarder les clefs .................................................................................. 4 3.2. Mettre à l’abri le certificat de révocation .................................................... 5 4. Diffuser la clef publique ........................................................................................ 7 4.1. Les serveurs de clefs SKS ........................................................................... 7 4.2. Le serveur keys.openpgp.org ...................................................................... 7 4.3. Autres méthodes de distribution ................................................................. 8 5. Chiffrer, signer des fichiers ................................................................................... 9 5.1. Chiffrer un fichier ....................................................................................... 9 5.2. Signer un fichier ....................................................................................... 10 5.3. Déchiffrer, vérifier un fichier ...................................................................
    [Show full text]
  • DDPR Applications
    Note: The following list will be valid from 1st April to 30th April Application Home Page URl Adobe Acrobat https://www.adobe.com Airmail https://airmailapp.com Airmail iOS http://airmailapp.com Allstate Digital Footprint https://www.infoarmor.com/digital-footprint Amazon https://www.amazon.com https://www.amazon.com/gp/help/customer/display.html/?nod Amazon Alexa eId=202126980 Apollo https://www.apollo.io App in the Air https://www.appintheair.mobi/ AquaMail http://www.aqua-mail.com/ Bark for Gmail https://www.bark.us BlackBerry Hub+ Services https://us.blackberry.com/smartphones/blackberry-hub-plus BlueMail https://bluemail.me/ Boomerang for Gmail https://www.boomeranggmail.com Brother iPrint&Scan for Android http://www.brother.com/apps/android CallApp https://www.callapp.com Checker Plus for Gmail™ https://jasonsavard.com/Checker-Plus-for-Gmail Chuck https://chuck.email/ Clean Email https://clean.email cloudHQ https://www.cloudhq.net/g_suite ColorOS_Mail https://mailvip.coloros.com/homePage.html Copper CRM https://www.copper.com/ CosmoSia https://cosmosia.net/ CRED https://www.cred.club/ DocHub - PDF Sign & Edit https://dochub.com Earny https://www.earny.co EasyMail - easy & fast email https://hbsolution.site/ eM Client https://www.emclient.com Email - Edison Mail http://www.edison.tech Email Home - Full Screen Email Widget and Launcher https://www.emailhomeapp.com/ Email Notifications for Forms https://digitalinspiration.com/product/google-forms-notification s Eメール http://www.sharp.co.jp/k-tai/ Fetch Rewards https://www.fetchrewards.com
    [Show full text]