DOCSLIB.ORG

Indicators for Missing Maintainership in Collaborative Open Source Projects

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

TECHNISCHE UNIVERSITÄT CAROLO-WILHELMINA ZU BRAUNSCHWEIG Studienarbeit Indicators for Missing Maintainership in Collaborative Open Source Projects Andre Klapper February 04, 2013 Institute of Software Engineering and Automotive Informatics Prof. Dr.-Ing. Ina Schaefer Supervisor: Michael Dukaczewski Affidavit Hereby I, Andre Klapper, declare that I wrote the present thesis without any assis- tance from third parties and without any sources than those indicated in the thesis itself. Braunschweig / Prague, February 04, 2013 Abstract The thesis provides an attempt to use freely accessible metadata in order to identify missing maintainership in free and open source software projects by querying various data sources and rating the gathered information. GNOME and Apache are used as case studies. License This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license. Keywords Maintenance, Activity, Open Source, Free Software, Metrics, Metadata, DOAP Contents List of Tablesx 1 Introduction1 1.1 Problem and Motivation.........................1 1.2 Objective.................................2 1.3 Outline...................................3 2 Theoretical Background4 2.1 Reasons for Inactivity..........................4 2.2 Problems Caused by Inactivity......................4 2.3 Ways to Pass Maintainership.......................5 3 Data Sources in Projects7 3.1 Identification and Accessibility......................7 3.2 Potential Sources and their Exploitability................7 3.2.1 Code Repositories.........................8 3.2.2 Mailing Lists...........................9 3.2.3 IRC Chat.............................9 3.2.4 Wikis............................... 10 3.2.5 Issue Tracking Systems...................... 11 3.2.6 Forums............................... 12 3.2.7 Releases.............................. 12 3.2.8 Patch Review........................... 13 3.2.9 Social Media............................ 13 3.2.10 Other Sources........................... 14 3.3 Weighting and Relevance of Sources................... 14 3.4 Sources in Potential Case Studies.................... 15 3.5 Selection of Case Studies......................... 18 3.5.1 The Apache Organization.................... 18 3.5.2 The GNOME organization.................... 19 4 Concept and Implementation 21 4.1 Existing Tools for Specific Sources.................... 21 4.1.1 Code Repositories......................... 21 4.1.2 Mailing Lists........................... 22 4.1.3 IRC Chat............................. 22 4.1.4 Wikis............................... 23 vii Contents 4.1.5 Issue Tracking Systems...................... 23 4.1.6 Forums............................... 23 4.1.7 Releases.............................. 24 4.1.8 Patch Review........................... 24 4.1.9 Social Media............................ 24 4.2 Data Collection Implementation..................... 24 4.2.1 Prerequisites............................ 24 4.2.2 Data Queries........................... 27 4.3 Rating Criteria.............................. 31 4.3.1 Code Repository Activity.................... 31 4.3.2 Issue Tracker Activity...................... 32 5 Results and Interpretation 33 5.1 Results................................... 33 5.1.1 Metadata Consistency and Completeness............ 33 5.1.2 Code Repositories......................... 34 5.1.3 Issue Tracker........................... 37 5.2 Rating Results.............................. 38 5.3 Interpretation............................... 39 5.4 Threats to Validity and Data Correctness................ 40 6 Conclusions 42 6.1 Data Analysis............................... 42 6.2 Recommended Actions.......................... 43 6.2.1 Data Gathering: On Metadata Availability and Consistency. 43 6.2.2 Taking Action on Results.................... 44 6.3 Outlook.................................. 45 Bibliography 47 A Source Code 62 A.1 Database Setup.............................. 62 A.2 Apache Subversion Checkout and Update................ 63 A.3 GNOME Git Checkout and Update................... 64 A.4 Extracting Metadata from Apache DOAP files............. 64 A.5 Extracting Metadata from GNOME DOAP files............ 65 A.6 Maintainer Information from Apache JIRA............... 67 A.7 Code Repository Activity Data in Apache............... 68 A.8 Code Repository Activity Data in GNOME.............. 69 A.9 Code Repository Activity Rating in Apache.............. 70 A.10 Code Repository Activity Rating in GNOME............. 71 A.11 Issue Tracker Activity Data in Apache................. 72 A.12 Issue Tracker Activity Data in GNOME................ 76 A.13 Issue Tracker Activity Rating in Apache................ 78 viii Contents A.14 Issue Tracker Activity Rating in GNOME............... 80 B List of Projects by Maintenance Rating 82 B.1 Apache: ratings.............................. 82 B.2 GNOME: ratings............................. 83 C Code Repository Activity 92 C.1 Apache................................... 92 C.2 GNOME.................................. 93 D Disclosure of Interest 102 ix List of Tables 3.1 Organization Infrastructures....................... 16 3.2 Organization Infrastructures (continued)................ 17 5.1 Metadata Consistency and Completeness................ 33 5.2 Commits and Committers in Apache: Absolute Numbers....... 35 5.3 Commits and Committers in Apache: Percentage Values....... 35 5.4 Commits and Committers in GNOME: Absolute Numbers...... 36 5.5 Commits and Committers in GNOME: Percentage Values....... 36 5.6 Number of Projects per Rating Category................ 38 x 1 Introduction 1.1 Problem and Motivation „Open source development is a form of distributed, collaborative, asynchronous, partly volunteer, software development“ [DM08, p. 159]. It is largely driven and maintained by volunteers who work on development of software in order to solve a problem they face [Gra04, p. 236]. Potential reasons for involvement include „fun, reputation, learning, enjoyment, and peer recognition“ [vKS07, p. 239]. According to [MH03, p. 105], „the majority of Free Software projects are directed by a single lead developer — usually the software’s original author — who assumes the role of maintainer, integrates patches submitted from developers in his or her user community, and organizes and coordinates releases of the software.“ At any time, a maintainer of a free software/open source project1 (in short: FOSS project) might lose interest in continuing development and become inactive. „As a result of the centralized decision making structure, development stalls in the absence of the lead developer“ [MH03, p. 105]. While spending less time is often realized by a maintainer, „there’s no point at which he consciously realizes that he can no longer fulfill the duties of the role“ [Fog06, p. 216] as the process takes place grad- ually. Furthermore, developers feel emotionally bound to their project and ask the community „to be patient but never find the time“ [MH03, p. 105]. Hence no public call for new contributors is issued either. To make the problem worse, „most free software projects are distributed, which makes it hard to quickly identify volunteers who neglect their duties“ [Mic04, p. 93]. Terms commonly used for this situation are AWOL (Away/Absent Without Official Leave) and MIA (Missing in Action) [Mic04, p. 95]. About 80% of the projects registered on the popular open source platform Source- Forge do not see any error reports, patches, feature request or other measurable in- teraction with the community after their registration [CMP05, p. 9]. Such a project can be considered inactive and unmaintained if no code development takes place and if nobody feels responsible for its state. The code base rots and does not get ported to potential new technologies in its environment, or falls behind the quality of competing projects. Inactivity is often not recognized by parties with interest in further development who could have stepped up to fill the gap if they only had known early enough. 1The terms Free Software and Open Source are often used synonymously. However, the first and older term implies an ideology and suffers from the ambiguity of the term free in English language (free as in freedom but also without costs) while Open Source rather focuses on technical aspects. For elaboration see [Fog06, p. 11–15]. 1 1 Introduction 1.2 Objective Big and established FOSS organizations can consist of hundreds of projects (modular packages) specialized on providing certain functionality in the stack [Gra04, p. 237]. Such packages, or modules, are often led and maintained by one person or a small core team of developers who lead and moderate discussions and decide on the direc- tion of the project and design questions [Seb08, p. 9][Gra04, p. 237]. Previous research shows that most projects only have a small number of developers — [CMP05, p. 6] proves that 82.6% of the projects hosted on SourceForge have only one or two devel- opers and [Wei05, p. 31] shows that the average number of developers per project on SourceForge is 2.0067. Most of these teams are loosely organized and do not require any official membership. Positions are frequently filled by individuals based on mer- its (meritocracy2), determined by previous contributions, commitment (cf. [Gra04, p. 237]), and reputation. As a result, volunteers and paid developers often work together on a project (see for example [Nea10] for an analysis of the contributor base of the GNOME organization). Moreover, most projects face the problem of only having a few main developers.
Recommended publications
  • Application-Level Virtual Memory for Object-Oriented Systems Mariano Martinez Peck

    Application-Level Virtual Memory for Object-Oriented Systems Mariano Martinez Peck

    Application-Level Virtual Memory for Object-Oriented Systems Mariano Martinez Peck To cite this version: Mariano Martinez Peck. Application-Level Virtual Memory for Object-Oriented Systems. Program- ming Languages [cs.PL]. Université des Sciences et Technologie de Lille - Lille I, 2012. English. tel-00764991 HAL Id: tel-00764991 https://tel.archives-ouvertes.fr/tel-00764991 Submitted on 26 Dec 2012 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. N° d’ordre : 40886 THESE présentée en vue d’obtenir le grade de DOCTEUR en Spécialité : informatique par Mariano MARTINEZ PECK DOCTORAT DELIVRE CONJOINTEMENT PAR MINES DOUAI ET L’UNIVERSITE DE LILLE 1 Titre de la thèse : Application-Level Virtual Memory for Object-Oriented Systems Soutenue le 29/10/2012 à 10h devant le jury d’examen : Président Jean-Bernard STEFANI (Directeur de recherche – INRIA Grenoble- Rhône-Alpes) Directeur de thèse Stéphane DUCASSE (Directeur de recherche – INRIA Lille) Rapporteur Robert HIRSCHFELD (Professeur – Hasso-Plattner-Institut, Universität Potsdam, Allemagne) Rapporteur Christophe DONY (Professeur – Université Montpellier 2) Examinateur Roel WUYTS (Professeur – IMEC & Katholieke Universiteit Leuven, Belgique) co-Encadrant Noury BOURAQADI (Maître-Assistant – Mines de Douai) co-Encadrant Marcus DENKER (Chargé de recherche – INRIA Lille) co-Encadrant Luc FABRESSE (Maître-Assistant – Mines de Douai) Laboratoire(s) d’accueil : Dépt.
  • Free Email Software Download Best Free Email Client 2021

    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.
  • The GNOME Census: Who Writes GNOME?

    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
  • An User & Developer Perspective on Immutable Oses

    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
  • Release Notes for Fedora 15

    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.
  • How-To Gnome-Look Guide

    How-To Gnome-Look Guide

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

    The Linux Command Line

    The Linux Command Line Fifth Internet Edition William Shotts A LinuxCommand.org Book Copyright ©2008-2019, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042. A version of this book is also available in printed form, published by No Starch Press. Copies may be purchased wherever fine books are sold. No Starch Press also offers elec- tronic formats for popular e-readers. They can be reached at: https://www.nostarch.com. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. Release History Version Date Description 19.01A January 28, 2019 Fifth Internet Edition (Corrected TOC) 19.01 January 17, 2019 Fifth Internet Edition. 17.10 October 19, 2017 Fourth Internet Edition. 16.07 July 28, 2016 Third Internet Edition. 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. Table of Contents Introduction....................................................................................................xvi Why Use the Command Line?......................................................................................xvi
  • Evolving Software Systems

    Evolving Software Systems

    See discussions, stats, and author profiles for this publication at: https://www.researchgate.net/publication/264799728 Evolving Software Systems CHAPTER · JANUARY 2013 DOI: 10.1007/978-3-642-45398-4_10 CITATIONS READS 4 154 4 AUTHORS, INCLUDING: Tom Mens Université de Mons 244 PUBLICATIONS 4,431 CITATIONS SEE PROFILE Available from: Alexander Serebrenik Retrieved on: 01 February 2016 Chapter 10 Studying Evolving Software Ecosystems based on Ecological Models Tom Mens, Maelick¨ Claes, Philippe Grosjean and Alexander Serebrenik Summary. Research on software evolution is very active, but evolutionary prin- ciples, models and theories that properly explain why and how software systems evolve over time are still lacking. Similarly, more empirical research is needed to understand how different software projects co-exist and co-evolve, and how contrib- utors collaborate within their encompassing software ecosystem. In this chapter, we explore the differences and analogies between natural ecosys- tems and biological evolution on the one hand, and software ecosystems and soft- ware evolution on the other hand. The aim is to learn from research in ecology to advance the understanding of evolving software ecosystems. Ultimately, we wish to use such knowledge to derive diagnostic tools aiming to predict survival of soft- ware projects within their ecosystem, to analyse and optimise the fitness of software projects in their environment, and to help software project communities in managing their projects better. This work has been partially supported by F.R.S-F.N.R.S. research grant BSS-2012/V 6/5/015 and ARC research project AUWB-12/17-UMONS-3, “Ecological Studies of Open Source Soft- ware Ecosystems” financed by the Ministere` de la Communaute´ franc¸aise - Direction gen´ erale´ de l’Enseignement non obligatoire et de la Recherche scientifique, Belgium.
  • Misc Thesisdb Bythesissuperv

    Misc Thesisdb Bythesissuperv

    Honors Theses 2006 to August 2020 These records are for reference only and should not be used for an official record or count by major or thesis advisor. Contact the Honors office for official records. Honors Year of Student Student's Honors Major Thesis Title (with link to Digital Commons where available) Thesis Supervisor Thesis Supervisor's Department Graduation Accounting for Intangible Assets: Analysis of Policy Changes and Current Matthew Cesca 2010 Accounting Biggs,Stanley Accounting Reporting Breaking the Barrier- An Examination into the Current State of Professional Rebecca Curtis 2014 Accounting Biggs,Stanley Accounting Skepticism Implementation of IFRS Worldwide: Lessons Learned and Strategies for Helen Gunn 2011 Accounting Biggs,Stanley Accounting Success Jonathan Lukianuk 2012 Accounting The Impact of Disallowing the LIFO Inventory Method Biggs,Stanley Accounting Charles Price 2019 Accounting The Impact of Blockchain Technology on the Audit Process Brown,Stephen Accounting Rebecca Harms 2013 Accounting An Examination of Rollforward Differences in Tax Reserves Dunbar,Amy Accounting An Examination of Microsoft and Hewlett Packard Tax Avoidance Strategies Anne Jensen 2013 Accounting Dunbar,Amy Accounting and Related Financial Statement Disclosures Measuring Tax Aggressiveness after FIN 48: The Effect of Multinational Status, Audrey Manning 2012 Accounting Dunbar,Amy Accounting Multinational Size, and Disclosures Chelsey Nalaboff 2015 Accounting Tax Inversions: Comparing Corporate Characteristics of Inverted Firms Dunbar,Amy Accounting Jeffrey Peterson 2018 Accounting The Tax Implications of Owning a Professional Sports Franchise Dunbar,Amy Accounting Brittany Rogan 2015 Accounting A Creative Fix: The Persistent Inversion Problem Dunbar,Amy Accounting Foreign Account Tax Compliance Act: The Most Revolutionary Piece of Tax Szwakob Alexander 2015D Accounting Dunbar,Amy Accounting Legislation Since the Introduction of the Income Tax Prasant Venimadhavan 2011 Accounting A Proposal Against Book-Tax Conformity in the U.S.
  • Return of Organization Exempt from Income

    Return of Organization Exempt from Income

    OMB No. 1545-0047 Return of Organization Exempt From Income Tax Form 990 Under section 501(c), 527, or 4947(a)(1) of the Internal Revenue Code (except black lung benefit trust or private foundation) Open to Public Department of the Treasury Internal Revenue Service The organization may have to use a copy of this return to satisfy state reporting requirements. Inspection A For the 2011 calendar year, or tax year beginning 5/1/2011 , and ending 4/30/2012 B Check if applicable: C Name of organization The Apache Software Foundation D Employer identification number Address change Doing Business As 47-0825376 Name change Number and street (or P.O. box if mail is not delivered to street address) Room/suite E Telephone number Initial return 1901 Munsey Drive (909) 374-9776 Terminated City or town, state or country, and ZIP + 4 Amended return Forest Hill MD 21050-2747 G Gross receipts $ 554,439 Application pending F Name and address of principal officer: H(a) Is this a group return for affiliates? Yes X No Jim Jagielski 1901 Munsey Drive, Forest Hill, MD 21050-2747 H(b) Are all affiliates included? Yes No I Tax-exempt status: X 501(c)(3) 501(c) ( ) (insert no.) 4947(a)(1) or 527 If "No," attach a list. (see instructions) J Website: http://www.apache.org/ H(c) Group exemption number K Form of organization: X Corporation Trust Association Other L Year of formation: 1999 M State of legal domicile: MD Part I Summary 1 Briefly describe the organization's mission or most significant activities: to provide open source software to the public that we sponsor free of charge 2 Check this box if the organization discontinued its operations or disposed of more than 25% of its net assets.
  • Designing a User Interface for the Innovative E-Mail Client Semester Thesis

    Designing a User Interface for the Innovative E-Mail Client Semester Thesis

    Designing a User Interface for the Innovative E-mail Client Semester Thesis Student: Alexandra Burns Supervising Professor: Prof. Bertrand Meyer Supervising Assistants: Stephanie Balzer, Joseph N. Ruskiewicz December 2005 - April 2006 1 Abstract Email Clients have become a crucial application, both in business and for per- sonal use. The term information overload refers to the time consuming issue of keeping up with large amounts of incoming and stored email. Users face this problem on a daily basis and therefore benefit from an email client that allows them to efficiently search, display and store their email. The goal of this thesis is to build a graphical user interface for the innovative email client developed in a previous master thesis. It also explores the possibilities of designing a user interface outside of the business rules that apply for commercial solutions. 1 Contents 1 Introduction 4 2 Existing Work 6 2.1 ReMail ................................. 6 2.1.1 Methods ............................ 6 2.1.2 Problems Identified ...................... 7 2.1.3 Proposed Solutions ...................... 7 2.1.4 Assessment .......................... 8 2.2 Inner Circle .............................. 8 2.2.1 Methods ............................ 8 2.2.2 Problems Identified ...................... 9 2.2.3 Proposed Solutions ...................... 9 2.2.4 Assessment .......................... 10 2.3 TaskMaster .............................. 10 2.3.1 Methods ............................ 10 2.3.2 Problems Identified ...................... 11 2.3.3 Proposed Solution ...................... 11 2.3.4 Assessment .......................... 12 2.4 Email Overload ............................ 12 2.4.1 Methods ............................ 12 2.4.2 Problems Identified ...................... 13 2.4.3 Proposed Solutions ...................... 13 2.4.4 Assessment .......................... 14 3 Existing Solutions 16 3.1 Existing Email Clients .......................
  • Debian Edu / Skolelinux Wheezy 7.1+Edu0 Manual

    Debian Edu / Skolelinux Wheezy 7.1+Edu0 Manual

    Debian Edu / Skolelinux Wheezy 7.1+edu0 Manual May 28, 2016 i CONTENTS CONTENTS Contents 1 Manual for Debian Edu 7.1+edu0 Codename Wheezy1 2 About Debian Edu and Skolelinux1 2.1 Some history and why two names . .1 3 Architecture 2 3.1 Network . .2 3.1.1 The default network setup . .3 3.1.2 Main server (tjener) . .3 3.1.3 Services running on the main server . .3 3.1.4 LTSP server(s) (Thin client server(s)) . .5 3.1.5 Thin clients . .5 3.1.6 Diskless workstations . .5 3.1.7 Networked clients . .5 3.2 Administration . .5 3.2.1 Installation . .5 3.2.2 File system access configuration . .6 4 Requirements 6 4.1 Hardware requirements . .6 4.2 Hardware known to work . .7 5 Requirements for network setup7 5.1 Default Setup . .7 5.2 Internet router . .7 6 Installation and download options8 6.1 Where to find additional information . .8 6.2 Download the installation media for Debian Edu 7.1+edu0 Codename "Wheezy" . .8 6.2.1 netinstall CD image for i386, amd64 . .8 6.2.2 USB flash drive / Blue-ray disc ISO image for i386 and amd64 . .8 6.2.3 Source image . .8 6.3 Request a CD / DVD by mail . .8 6.4 Installing Debian Edu . .9 6.4.1 Select type of installation . .9 6.4.1.1 Additional boot parameters for installations . 12 6.4.2 The installation process . 12 6.4.3 Notes on some characteristics . 14 6.4.3.1 A note on notebooks .