DebConf18

Opening remarks by Jen-Hui Chuang, Dean, College of Computer Science, NCTU 開幕致詞 邀請交通大學資訊學院院長 Talks: - Ying-Chun Liu (PaulLiu) - DFSG for the General Public - Bdale Garbee

Exploring Diversity in Debian, and how it affects the project

Minister [Audrey Tang](https://en.wikipedia.org/wiki/Audrey_Tang) [唐鳳](https://zh.wikipedia.org/wiki/%E5%94%90%E9%B3%B3) will join us for a Q & A session

在 Android 手機系統內，Google Play 商店中的 LibreOffice Viewer 有一部 30 秒的動畫短片。 不要看它只有 30 秒，它可是台灣之光，是台灣自由軟體社群朋友送給 LibreOffice 社群的一份大禮！這部動畫短片由台灣的 LibreOffice 社群與 A+A Space 社群共同創作，包含動畫、特效製作、音樂、歡呼聲的錄製與合成都使用 Blender、Krita、Inkscape 等自由軟體製作；裡面還藏了許多彩蛋，每個畫面都有故事並充滿驚喜。 這一場 Session 將會把這部動畫的來由、製作的幕後花絮與含義分享給大家。

Debian Meets Smart City Applications

The DRBL and Clonezilla projects were born in Taiwan, and were heavily developed at NCHC. They were needed in the computer classroom and cluster computing in the beginning. Later as Debian live-package debuted in 2006, the DRBL/Clonezilla team created "Clonezilla live" with live-package and this Debian derivative release became popular. If you are interested in how the projects were born, and the evolution about them, please come to this talk.

Are you a newcomer to Debian Packaging? Come join us in a workshop.

這是一場國際化主題的演講，主要說明如何讓注音符號排版在Web以及資訊系統上呈現。在這五年的時間中，注音符號從W3C規範上的一項註釋開始，完成了HTML5的標註方法、確立了CSS標準並且受到瀏覽器實作。最終遇到了調號位置的問題，最近終於透過OpenType字體的功能而完成了最後一步。本演講主要說明這段時間的進程與標準化進度，以及所遇到的問題與經驗分享。 This speech is about i18n. Bopomofo (Zhuyin Fuhao) is a phonetic system for Mandarin only used in Taiwan. It's layout is complex for web and information systems. In past five years, I participated W3C standardization activities to bring this issue from an annotation on W3C spec to finalize HTML ruby markup and push CSS spec to be implied by browsers. Tone mark position is the last step and we tried OpenType font feature as solution. I'll describe the process for standardization and problems and experience.

當 TangleID 遇上台北市政府: 自由軟體如何改善公部門處理流程 Google Translates as: When TangleID meets the Taipei City Government: How Free Software Improves Public Sector Processes

The lightweight classic desktop environment LXDE has been developed for 12 years and remains one of the best choices for less powerful hardware. In 2013, the LXDE project teamed up with the Razor-Qt project and initiated LXQt desktop together. This is a historic event in FOSS since most of the time we saw forks rather than merges. It's especially true for desktop environments. In this session, we will talk about the past and future of LXDE/LXQt and share what we have learned during the journey.

This Panel Discussion features Debian contributors from around the world, including: * Bdale Garbee (USA) * David Prévot (Tahiti) * Jonathan Carter (South Africa) * Josué Ortega (Guatemala) * Hideki Yamane (Japan) * Nicolas Dandrimont (France) Moderated by: Hong Phuc Dang (Vietnam)

共享試用不是真自由 - 從 DFSG 論如何認識及做好自由軟體著作權標示

EzGo project

Welcome to Taiwan! Opening ceremony for DebConf18, practical information, and all sorts of Q&A

This talk is aimed for an audience who wants to learn more about games in Debian. How many are there, how can I find them, what kind of games are available and who maintains them? This presentation will give you a broad overview of the current state of Debian Games. It should give you some ideas what free software games are, who creates them, how they differ from commercial titles and why we should care about them. While the main focus of this talk will be on free software games, I will also discuss tools and programs that make it possible to play commercial games on Linux that were released for different platforms, some of them long forgotten.

Current package distribution security is based on cryptographic signatures. We propose to extend the current release file signature mechanism with an architecture offering protection against targeted backdoors by a compromised archive. This project introduces a Merkle tree-based transparency log for package meta data and source code, similar to certificate transparency. In our system, the APT client verifies that it installs the same binary package as everybody else. Utilising reproducible builds, we further ensure that the source code and buildinfo corresponding to that binary can be retrieved. We explain parts of our prototype and show the results of replaying two years of Debian updates.

State of the project, ongoing activities, etc..

Civil infrastructure systems, such as Power generation and distribution, industrial IoT gateways, healthcare devices, traffic control systems are essential systems to keep our society. Debian has already run on many kind of controllers for civil infrastructure systems, however there are gaps that need to be solved, for example such kind of systems has to survive for 10-50 years. To fill the gap, the Civil Infrastructure Platform (CIP) project has launched to create an open source “base layer” of industrial grade software with Debian as a reference distribution. CIP has already started to contribute Debian related projects. In this talk, Yoshitake will start brief introduction of CIP. Then move to explain the latest status for CIP's activities which include collaboration with Debian. Finally, he will show CIP's technical roadmap to discuss how CIP can collaborate with Debian to make more sustainable base-layer.

This is the usual Debian Med BoF to report about details inside the Debian Med Blend and to discuss future development.

We present our work towards representing Debian's packages, including history and releases, as well as other components of the Debian environment, in a Graph Database. The Ultimate Debian Database [UDD](https://wiki.debian.org/UltimateDebianDatabase/) collects a variety of data around Debian and Ubuntu: Packages and sources, bugs, history of uploads, just to name a few. The database scheme reveals a highly de-normalized [RDB](https://udd.debian.org/schema/). In this on-going work we extract (some) data from UDD and represent it as a graph database. The presentation will give a short introduction on the life time and structure of Debian packages, followed with the graph database scheme (nodes and relations). After going through some of the queries used on the UDD web pages we will show how they can be translated to Cypher. We close with an outlook of our future plans and open problems.

This is the usual Debian Science BoF to report about details inside the Debian Science Blend and to discuss future development.

Since November 2017, [AppArmor](https://wiki.debian.org/AppArmor) is enabled by default in Debian testing and sid. This [experiment]((https://lists.debian.org/debian-devel/2017/08/msg00090.html)) aims to gather data, so that we can decide whether we should enable AppArmor by default in Buster. # Share feedback We will share feedback about our experience with AppArmor, be it as users or contributors. I'm interested in hearing about: * General feelings. If you feel like it, we will try to understand where these feelings come from. * Technical issues. It's OK not to have filed a bug report yet :) * Raw data: did you disable AppArmor on your systems? When? # Share skills We will share AppArmor skills, tips and tricks we've learned along the way. Let's help each other! The notes of this session can be used later to: * Fix underlying technical issues we're working around with tips and tricks. * Fill holes in our documentation.

On the surface, this story shares vignettes about my Mom. But its purpose is to increase awareness of human resources in technology, and overlooked career pathways of women and other young technologists. For example, In 1973 RCA hired her for self-directed projects in their chip prototyping lab. A marathon week of late-night needlework produced a crochet blanket and proved her mathematical mind to skeptical women co-workers. She told me stories of such ladies who wrapped wires for NASA a few years before. She said women's milleniums of technical fiber-crafts were acknowledged when they helped put men on the moon.

I was born in year 1955. So, I can explore the world of elderly people as an insider. This short talk is about a series of workshops which I organized in a French computer club which often gathers a small society of elderly people, most of whom are retired for a long time. Debian may be a good system for the elderly, when someone can tune it finely for each particular user. We shall consider a catalog of situations implying individual users, and their feelings about such a disruptive environment (just imagine: having lived all one's life with W$, and discover freedom). You know? old timers are not that different from you. Maybe some day you will feel like them?

In December a team to maintain GNU R packages in Debian was founded. This is the first meeting of team members to discuss about enhancing the cooperation inside the team.

One of DebConf’s recurring activities is the Key Signing Party. It helps Debian strengthen and expand its web of trust. This session will: • Explain how keysigning is done in a DebConf setting • Validate the SHA256 hash of the KSP coordination document • Explain how to participate to people who did not send their keys in time Note: It is strongly recommended for interested people to [read the Wiki page on our keysiging party/process](https://wiki.debconf.org/wiki/DebConf18/Keysigning) beforehand!

In Debian Pure Blends several tools were created to maintain packaging on one hand as well as publishing related content in the so called web sentinel. This talk will give an overview about the tools, the collection of data (like scientific citations, software registries and other metadata) as well as team metrics to know how a Blends team works together. It might help people to get a better understanding of Blends and get an idea how to create an own Blend.

You don't need to be a developer to contribute to Debian - triaging bugs helps the maintainers a lot, and it's not difficult to do! Maintainers are welcome too - your input will be appreciated, and you might even learn a thing or two :)

The Xen packages in Debian are in need of some work, including some tidying up, upstreaming of some Makefile patches, and updating to new versions. There is a large outstanding bug list. Also with the demise of Alioth and the change to maintainers, we will be talking about the future git maintence workflow. Come and stick your oar in. You can help influence the Xen maintainers' workflows, and our priorities.

Recently we completed a tool (debcargo) to automatically convert Rust crates to Debian packages. The tool focuses on making long-term maintenance easier - in the vast majority of cases a maintainer only has to maintain two files (d/copyright, d/changelog) in git and everything else is automatically generated. Most crates take about 2-5 minutes to package, build and upload. Over the past month or so we have already uploaded about 100 Rust packages, and have more on the way. The limiting factor has been the speed of the NEW queue. This BoF will go over the whole end-to-end process of packaging Rust crates, and hopefully get some of you on board helping with the Debian Rust team.

Discussion session for the Debian Cloud team: - status on official images - tools for building our images - etc…

Running games on Debian often means compromising the integrity of our systems by dual-booting non-free operating systems or installing non-free drivers on our Debian systems. This presentation will describe some work sponsored by the Valve Corporation aimed at helping make this situation better. We're working on improving the free Mesa implementation of the Vulkan API for AMD hardware, fixing support for Head Mounted Displays, and improving X support for animated applications. All of this work is (naturally) being done in the open within the context of the relevant free software projects.

Projects like Debian can only exist in a connected world, but the immense increase in communication capability of the Internet also has a dark side. The same capabilities that enable intense technical collaboration across immense distances also make it possible for negative voices to be amplified. This session will be a panel discussion featuring some well-known, long-time contributors to Debian who are willing to share their experiences and advice on how to remain focused on what's important. Criticism is vitally important to Debian, but developers need to be able to extract the constructive elements from public discussions. Hopefully, the content of this session will help!

With git-debrebase the Debian changes to the upstream source are represented and manipulated as git commits, with one commit corresponding to one quilt patch. However, unlike with gbp-pq and git-dpm, git-debrebase uses just a single git branch. git-debrebase branches are: * directly buildable * directly editable with git-commit(1) (whether of Debian files, upstream files, or both); * directly useable with dgit (without --quilt= option); * automatically made fast forwarding when published; and * have a history useful for git log, git blame etc. Unlike with gbp pq, there is no need to switch back and forth between public and patch queue branches and there is no need to apply and unapply patches. Unlike git-dpm, git-debrebase requires no in-tree metadata. Uploads of git-debrebase branches done with dgit publish the source both as: 1. a git branch which anyone new to Debian can immediately use, and which Debian contributors can directly work on; 2. a perfect `3.0 (quilt)' source package as expected by non-git users.

An opportunity to meet the members of the Debian Technical Committee who are in attendance at Debconf, hear the status of open issues, understand the nature of the TC's work, and discuss pending and future issues with the committee. URLs: [https://www.debian.org/devel/tech-ctte](https://www.debian.org/devel/tech-ctte "Technical Committee")

This introductory level talk will provide an overview of the build workflow for a Debian derivative by discussing the challenges inherent in being the sole manager of everything from source code commits to published packages. Real world examples will be provided from Cumulus Linux: a Debian derivative for white box network switches. Topics covered will include: - Incorporating Debian as the upstream. - Choosing software to meet build requirements. - Lessons learned after the aforementioned software was chosen. - Where some distribution specific customization will be required. - Difficulties in supporting multiple architectures. - The role of human factors in making the build system invisible. - And why a good dynamic package versioning scheme is very, very important. The intended audience would be anyone setting up a Debian Derivative, or anyone seeking a greater awareness of what commonly used Debian build tools are available, and what roles they perform.

GNU Ring is a free software for universal communication which respects the freedoms and privacy of its users. The program allows users to communicate with each other without relying on a centralized server to relay messages. This presentation will give a short overview of the challenges faced by the Ring project, both technical and non-technical. Among others we will discuss the question of attracting external contributors in the special context of Ring, as well as the technical challenges arising from the development of offline messaging and name servers in a fully distributed network.

_di-netboot-assistant_ is a tool to simplify the preparation of files for TFTP net booting. It downloads and extracts the files needed and takes care of organizing them. In addition, it prepares a top level menu for PXElinux and grub-efi, which allows one to choose from all installed netboot images at boot time. _di-netboot-assistant_ supports preseeding the installer in order to set up systems completely automatically. The talk shows how _di-netboot-assistant_ can be combined with _ansible-pull_ to install machines in one step from an ansible-playbook. [Netboot Assistant Package Homepage](https://wiki.debian.org/DebianInstaller/NetbootAssistant "Package di-netboot-assistant") [Example Playbooks](https://salsa.debian.org/andi/debian-lan-ansible "Example playbooks")

I have been setting up contributors.debian.org and nm.debian.org to deploy new versions to production once Continuous Integration tests succeed on salsa. I would like to discuss what I did and see how to make it easy to have a similar workflow for other projects, and if possible, share the code for doing so.

There are various tools for creating system images based on Debian and its derivatives, including vmdebootstrap(2), bitbake, and live-wrapper. Each has its own pros and cons. This is an opportunity to share practical experience, including recommendations for effective usage, traps to avoid, and lesser-known tools for this task.

Show off your project here!

After 7 years of OpenStack existence, it's time to step back, and understand why using, and operating it is more important than ever. In this talk, we'll cover why running your workload on the cloud is becoming increasingly crucial because of the costs and agility of the cloud empowers its users. We'll see why running on the cloud, rather than on legacy dedicated servers, gives more freedom than ever. Then we'll see why using OpenStack over proprietary solutions matters for your freedom. Finally, we'll see how choosing Debian to run OpenStack makes a real difference in avoiding vendor lock-in.

This talk will look at the developments since last DebConf and what our plans are for the future. Highlights: - zstd support for APT, dpkg; and what it means for us - the dpkg frontend lock - evaluation of seccomp sandboxing; problems with it - happy eyeballs and what it means for apt on mixed ipv6/ipv4 networks - new JSON-RPC-based hooks for apt; and an outlook on future possibilities for more complete RPC - $random other bits

This in mainly about 1. packaging XMPP software (clients, servers, libraries) both within the XMPP team (https://salsa.debian.org/xmpp-team/) and elsewhere. 2. the XMPP infrastructure of Debian itself (prosody on vogler.d.o). Everybody interested in one or the other topic is invited.

OpenRC is a dependency based init system written in C and shell script. It is modular and can be extended by s6 supervisor and Linux cgroup. Keeping itself simple and stupid, OpenRC values Unix philosophy. OpenRC is shipped with Debian stable since Jessie and runs on kFreeBSD and Hurd besides Linux. It readily runs Debian in LXC, OpenVZ, vserver containers, usermodel Linux or Xen domains. In this talk I am going to walk you through the features of OpenRC, and show you how OpenRC is hacked to suit our needs in real life.

Talk about the future of Debian Brasil community and the DebConf19 organization. We will talk in portuguese.

Debian sid contains more than 31.000 maintainer scripts, the vast majority of which are written in the POSIX shell language. We have written, in the context of the CoLiS project, the tool shstats which allows us to do a statistical analysis of a large corpus of shell scripts. The tool operates on concrete syntax trees of shell scripts constructed by the morbig shell parser. The morbig parser has already been presented at a devroom at FOSDEM 2018, and at the minidebconf 2018 in Hamburg. The shstats tool comes with a number of analysis modules, and it is easy to extend it by adding new modules. In this talk we will present both the design of the analyzer tool and how it can be extended by new analysis modules, and some of the results we have obtained so far on the corpus of sid maintainer scripts. Among these are answers to questions like: - are recursive functions used in maintainer scripts? - how many variable assignments are in reality definition of constants? - how many shell scripts don't do any variable assignments, besides definitions of constants? - how often are shell constructs like while, for, if, etc. used? - which UNIX commands are most commonly used in the corpus, and with which options? - are there any syntax errors in the arguments of complex commands like test?

git-debrebase is a new tool for managing Debian packaging in git. dgit is a bidirectional gateway between git and the Debian archive. These tools can be used independently or in combination. We have published a tutorial for using the combination of git-debrebase and dgit to maintain Debian packages: the dgit-maint-debrebase(7) manpage. There are also: dgit-maint-gbp(7), dgit-maint-merge(7) and dgit-simple-nmu(7). In this workshop we will help package maintainers start using the workflows described in these tutorials to maintain their packages. We can also answer general questions about dgit and git-debrebase. We also hope to gain feedback as to how dgit-maint-debrebase(7), and git-debrebase and dgit more generally, could be improved. For more information about git-debrebase, see the abstract for the talk about git-debrebase. Before joining this workshop, it would be useful to review some of the dgit-maint-*(7) manpages.

Software in the Public Interest is the legal and financial umbrella organization providing services to Debian in the United States. This session will provide an opportunity to meet the members of the SPI board attending Debconf, hear a brief update on the organization’s activities in the last year, and get your questions answered.

Last year's two sessions on this topic showed that there is a fair amount of interest in pursuing the topic of being more inclusive and welcoming to underrepresented groups within the Debian community. The aim of the yet-to-be-formed diversity team should be to offer a contact point to exchange and connect various groups. The main principle is based on intersectionality. We'll start the session with a name and pronoun round where people can also shortly say what they specifically are interested in, and we'll form the topics and schedule from there on. This session is meant to offer a safe space for attendees, and thus no recordings will be kept to not out people accidentally against their will. Also this means that all attending parties are expected to discuss in a non-discriminatory way and reflect on when they are told that some wording was not okay. In the hopefully unlikely case that a participant's actions make others uncomfortable they will be asked to leave. That includes nosy questions that question other people's identity.

As Infomaniak has offered 30 yubikeys to DDs in Debconf, this workshop will teach how to set it up, so you can be up and running to upload packages signed with your GPG subkeys in the Yubikey. This will also help to avoid some of the traps.

Discussing about the future development about deep learning frameworks and applications in Debian. This BoF may cover some content from the computer vision field and computational linguistics field.

This talk is a report on the current status of the support of Secure Boot on Debian by the EFI team and what is missing. The team are going to explain the main architecture and workflow, the required changes in dak, how the signing service works and how this impacts packaging due to the new template binary packages required for the signing service.

Debian has been participating for Outreachy and Google summer of Code as mentor organisation. The session would be about the journey of Debian and the discussion of students and mentors on their ongoing projects.

After an exciting and incredibly well-attended BoF at DebConf 17 in Montréal, interesting developments regarding mobile devices continued (in no particular order and without any attempt of being complete or fair): 1. The Pyra, while still not released (as of 2018-02-07), nears completion of hardware and casing. 1. Purism announced their plans for the Librem 5, a Debian based smartphone. Their crowdfunding campaign was amazingly successful. 1. Another recent crowdfunding reached their financial goal in only one day: The plan to create a free Linux driver for the Allwinner VPU, started by Bootlin. 1. ZeroPhone has constant progress on both hardware and software side, as well as many other projects. Let us look, where we are one year later. Which ideas took off - more or less, which did not?

Long before the Snowden revelations or recent stirs about Cambridge Analyticas use of Facebook data, the Debian community was and continues to be very attentive about privacy aspects of using our operating system. Still, privacy is not a “core value” of Debian. It is not mentioned in our social contract nor in the policy manual. Because privacy is important to many in the Debian project and probably most of our users, we might like to discuss privacy aspects of the Debian operating system and the applications we deliver, develop guidelines to improve on it, and help our users to understand how to protect their privacy when using Debian. This becomes also more relevant because of new data protection laws, like the EU GDPR. This BoF should help us to clarify, whether we need to do something and what. Maybe develop a "Debian privacy manual"? Or create yet another team? Also, we can discuss whatever we like related to Debian and privacy. There is already a team packaging privacy related software, and another team, that is responsible for privacy of Debian infrastructure. But here we like to discuss privacy implications of the Debian OS to its users.

The talk[1] from Keith Edmunds gave me some inspiration, why Debian needs to change its home page. I like to share my thoughts about improvements of the Debian home page without changing the design in the first step. I started by cleaning up the content and removed a lot of links. I will show a prototype and explain what I've changed and why. [1] https://meetings-archive.debian.net/pub/debian-meetings/2017/mini-debconf-cambridge/building-a-05m-business-on-debian.vp9.webm (from 0:36:30) The audience are people working on the web page and designers who could do this much better than I can do.

You are beginning to learn more about Debian packaging and one of your favorite programming languages is Java. You are already an experienced maintainer or packager but you are unfortunate enough having to package some Java app and you don't know how to start. Never heard of Ant, Maven and Gradle? Then this presentation will hopefully help you to get started quickly by introducing you to the most important Java build systems and methods to make them Debian compliant. This talk is about learning by examples. It will highlight some Java applications and libraries that are already in Debian and demonstrate what you need to do to deliver your own package to your users. I will also talk about some common Java specific packaging errors and how you can avoid them.

The Linux kernel is under rapid development. Stable releases are made around 5 times per year, each including many new features and support for new hardware. This talk will summarise the features that have been added and enabled in the last year. There have been many changes to Linux between 4.14 and 4.18. Some of these will require new or updated userland applications to take advantage of them. I will attempt to summarise the most interesting changes and the state of integration in Debian.

Many packaging tasks can be automated, and are likely to succeed without any human intervention: - creating a backport for Debian stable from a packaging in Debian testing - upgrading a package to a newer upstream version - packaging a simple Perl, Python or Ruby using one of the tools listed on AutomaticPackagingTools However, doing those tasks still require Debian packaging knowledge. As a step towards Debian's world domination, it would be great if we could automate those tasks and provide ready-to-use Debian packages, so that users are left with a deb-based alternative when there are no packages for their needs in Debian itself, instead of using upstream packages or building from source. Autodeb is a project that tries to automatically create and distribute package updates and backports. This talk will present the current status of the projects, statistics, and takeaways.

Tome to do a BoF about Pkg Webextension Team? --------------------------------------------- Since Firefox 58 AddOns with an Webextensions interface are required to act as a plugin. By this one extensions could be used in Chromium and Firefox. Thunderbird has also switched to Webextensions but not that strict as Firefox is doing. This BoF should help to clear out some questions to improve the packaging of AddOns in the near future. Possible Topics --------------- - How does Webextension work? - Where to collect the (team based) packaging in Salsa? - What about the build helping systems like xul_ext and dh_webext, where to move and what is still needed? - How can the wiki site in the Debian wiki improved? - Which information needs to be collected so existing packages or new packages can be build easily from stretch? If you are interested, have questions or willing to help please join!

Facilitated discussion and short story sharing. What works well in some teams? How to share that knowledge across teams? How have new contributors become good project leaders? Where have good moderators learned their skills? How should we discuss team problems in ways that lead to good outcomes? In the future, how might Debian encourage discussion-process skills between teams?

The support for typesetting Japanese (or any CJK language) in TeX in particular TeX Live, has been considerably improving over the last few years. From practical non-existence 10 years ago where every Japanese TeX user was used to download and compile packages (pteTeX, pTeXLive) to a simple `apt-get install texlive-lang-japanese` was a long way. In this talk we recall a bit of the history of Japanese TeX in (Debian) TeX Live and give an introduction to the particularities of Japanese typographic rules and how they are implemented in TeX. We will shortly touch on how to typeset multilingual CJK documents in TeX using upTeX and LuaTeX, and report on the current state of CJK font support in TeX concerning free and commercial fonts.

Debian's focus is on getting a great distribution in front of its users and the importance of the end user is enshrined within our Social Contract. All pieces of software have rough edges and users will always need support to help them make the most out of their available resources. The environment in which support is provided is important to the user and also to the volunteer who is spending time providing help. In commercial situations the user support job is colloquially known as the "helldesk", so how do we make it an attractive place for knowledgable volunteers to help out in our project? User support brings together all the best and the worst of the technical and social aspects of free software, offering opportunities for innovative tools to help with user support and also exceedingly negative inter-personal interactions. In this BoF, we will discuss the channels that Debian currently uses for user support, consider the strengths and weaknesses of these approaches, look for ways to help users find the answers they need to solve the problems they face and also how to better support the volunteers who make this all happen. Spam, trolling, support vampires, BOFHs and burn out will be discussed. The venues to be discussed will include at least mailing lists, IRC, forums, official/unofficial documentation, wiki, and 3rd party websites.

Now that libre fonts are widely available through projects like Google Fonts and Open Font Library, what's next for free-software typography? Font selection and access for users relies on support from the entire operating system stack. Our font packages, however, are still structured like command-line applications. Documentation and supplemental data are not integrated with system or application-layer help frameworks. Metadata is not tracked by the desktop environment as it is for other content types. The OS provides little to no help for users downloading fonts online or simply maintaining a large library. We can make improvements to how fonts are packaged and how font metadata is handled throughout the OS that will make it easier for application developers to create font managers or to provide richer experiences for finding and choosing fonts in GUI applications—including those that use custom widgets, as design applications often do. Designers and authors, who make the most use of fonts on a day-to-day basis, will gain from these improvements first. But the same changes that simplify life for users whose daily work involves their font library will benefit others. Enhancing font packaging will improve the experience for translators and internationalization projects, simplify the build process for Debian and downstream developers, and reduce the number of bugs caused by the peculiarities of font licensing. This talk will cover proposed changes to the contents and policy of font packages as well as in-progress work on improving font support in AppStream and other metadata tools, software centers, and package managers. It will address upcoming changes to SPDX to better support font-licensing details like Reserved Font Names (RFNs) and how those changes will affect license-compliance work, and it will look at the possibilities of integrating a Debian desktop with online font libraries and services.

We use several different approaches to improve hardware support during a Debian stable release: - Updating selected drivers in the linux package - Adding newer versions of linux and other packages to the associated backports suite - Adding an alternate kernel version in the stable suite (etch-and-a-half, jessie LTS) Updating selected drivers in the linux package (and other driver packages) is the best way to make new hardware support available to users, but it can require substantial development time and carries a relatively high risk of regression. I did many kernel driver backports during the stretch and wheezy releases, but haven't found time to do so more recently. The backports suites can provide comprehensive support for new hardware, but they are less easily available (for example, there is no official installer build using the kernel from backports). The backports suites are often the last to get security updates, and they are not maintained during the LTS period. We've previously tried to add alternate kernel versions half way through a stable cycle, with limited success. For etch, the etch-and-a-half update added new versions of the Linux kernel, some X drivers, and the installer to etch shortly before the lenny release. For jessie, there were plans to improve Arm64 support in a similar way, but these were overtaken by the stretch release. How can we do better?

It looks like a bunch of us are interested in writing a new Debian installer that would live on a live distribution, rather than using Busybox as it is today. Let's talk about how we can do it.

Typical group photo as usual

Some people might remember my talk last year ["Am I really married with Debian"](http://meetings-archive.debian.net/pub/debian-meetings/2017/debconf17/am-i-really-married-with-debian.vp8.webm). Since I was asked by some people about the wedding of my Vietnamese daughter I have some cute story to tell and some images to show. I can do this in an evening event if more than two people are interested. For interested people I can show some preview of the images online but since they are private I do not want to publish the URL in a public place - fell free to write me some e-mail.

Join the maintainers of MariaDB and MySQL in Debian to discuss current state of how the SQL database servers, connectors, clustering tools and other related software is packaged, shipped and automatically tested, installed or upgraded in Debian. If you are interested in joining the MariaDB/MySQL packaging team, this is the place to meet current maintainers and get introduced to the current packaging efforts. If you just want to occasionally contribute, this is the place to share your plans and ideas to they can be refined together.

FAI.me is a web-based build service for creating customized installation or cloud images for Debian. It's using the FAI software, so the installation will run unattended without any interaction necessary. The cloud images are ready to boot in a VM. On the website, you can customize different properties of your image, like the disk image size and the disk format, the language, a user name and password. You can select a Debian distribution, a desktop and enable backports just by one click. It's possible to add your public key for access to the root account. This can also be done by just specifying your GitHub account. You can add your own list of packages that will be included into the image. After a few minutes the your disk images is created and you will get a download link, including a log the the creation process and a link to the FAI configuration that was used to create your customized image. The talk will demonstrate the build service and explains how the jobs are processed in the background using the FAI tools. The configuration, that is used will also be presented. https://fai-project.org/FAIme Talk slides available at https://fai-project.org/doc/fai.me-build-service-dc18.pdf

Mathematical models allow the designer to optimise and predict, with most engineering curricula containing courses to teach the use mathematical and computational skills to develop, test, and interpret models or simulations. The traditional teaching approach has relied heavily on commercial packages and assumed that students can recall details and integrate concepts from previous years. In this case study, we investigate displacing proprietary tools with free software, look at the effects that has on the community of learners as well as the instructors, and examine the challenges posed to this project by binary distribution through Debian and fragmented/uncoordinated module development. The teaching of engineering modelling tends to be focused on the use of numerical methods techniques with a small amount of simple programming skills being needed to deliver the required results. Commercial packages such as Matlab are dominant in the teaching of many sub-disciplines of engineering, with institutional or low-cost student licences required. From a teaching perspective, the empty Matlab prompt offers neither assistance nor encouragement to the novice and the path to reconnect model to reality is not encouraged by its raw numerical output; understanding the principles of the model, scepticism based on the “garbage in, garbage out” principle, and robust interpretation of the results are not supported by its user interface. For the scientist and engineer, the mathematics and its embodiment in code are insufficient and there is a strong expectation that translation into words and interpretation are necessary. [Jupyter notebooks](https://jupyter.org/ "Jupyter Project") offer a [literate computing environment](https://osf.io/h9gsd/ "Millman and Pérez, Developing open source scientific practice") in which numerical methods and data analysis code can be interactively developed and refined in ‘cells’, while relevant rich context (text, images and equations) is interspersed amongst the code. For the engineer undertaking one-off model development and also for the educational scenario, the Jupyter notebook offers the fusion of code, documentation and output. To scaffold the three-fold development in programming, numerical methods and discipline knowledge, we have assembled a free software stack based on Jupyter notebooks in which problem statements (in Markdown/MathJax) are accompanied by code cells (in [Python](https://www.python.org/ "Python Project") or [Octave](https://octave.sourceforge.io/ "Octave Project")) with some parts of the necessary code to solve the problem redacted, thereby offering hints at how to approach the problems without giving away the entire solution. Within each problem set, progressively less help is offered as confidence and competence is gained. To ease maintenance, both the problem and solution notebooks are generated out of the same annotated precursor notebooks using some [simple Python modules](https://github.com/llimeht/jupyter-teaching-tools "jupyter-teaching-tools to manipulate ipynb files") we have developed that work with the [Jupyter notebook files](http://nbformat.readthedocs.io/en/latest/ "Jupyter notebook file format"). Students are: introduced to the concept of free software, offered ways of downloading and installing the tools they will need (Debian shines in this: `apt install jupyter`), provided with instructor-generated complete examples to analyse and imitate, and given the problem sets on which they can work. Over the past three years, we have also learnt much about the interplay between the [software development/distribution life cycle](http://dx.doi.org/10.1007/s41019-017-0050-4 "Möller et al.") (scattered upstream releases, updated source packages, binary distribution, deployment) and our own development and delivery cycle (heterogeneous deployments, cloud hosters, strictly time-based releases). For a stable basis on which a course can be built, we prefer Debian stable releases where package versions, features and bugs are a fixed set for the 4 month teaching block; all our development work is done in this environment. How do we then overcome development friction to (say) realise a particularly nifty delivery idea that requires a newer version of the [ipywidgets](https://ipywidgets.readthedocs.io/en/latest/ "ipywidgets documentation") module to add interactivity to the student experience in Jupyter? How do we address a bug with interactive plotting that only exists in one particular combination of module versions that happens to be what is packaged? With such young technology, the tension between 'latest' and 'stable' plays out each time the course is run, with new features, new bugs and new workarounds to be discovered. We add to this a desire for someone else do the sysadmin work ([CoCalc.com as a cloud hoster](https://cocalc.com/ "CoCalc.com Jupyter hosting (and more)")) and for students to run the code on their own devices, and then problem space becomes significantly larger. In working through the inevitable bugs, the students also see real bug reports, fixes and tests of workarounds, illustrating the power and importance of free software. In this talk, the benefits and limitations of the chosen tools will be analysed from a software distribution perspective, with discussion of the strengths and weaknesses of Debian's current approach to packaging the entire stack for binary distribution. The effect of the Debian release model on our teaching and the interplay between Debian and the fragmented upstream communities that are relied upon will be investigated. Some of the capabilities of Jupyter notebooks in the hands of both students and instructors will also be demonstrated.

Cross-building Debian packages is important topic for embedded developers. Many activities are there for cross-building or tooling for that in debian-embedded, debian-cross and others. In this BoF, the following topics would be discussed (and others are welcome) to share the current development state of cross-building, clarify new issues to be solved, and future plan of such kind of activities. * Recent issues in debian-cross * How to share efforts (i.e. patches, testing, investigation) for cross-building packages * Infrastructure for cross-building packages (cross-buildd?) * Involving people who are interested in this topic (info in PTS, etc.) * Documentating using Wiki to share information * And more...

This is a follow up from the last DebConfs "If you love a package let it go" [1]. With the input from this BoF and after talking about package salvaging with several people we'd like to come forward with the proposal to establish a package salvaging process. In this BoF we'd like to discuss the proposal and hear your thoughts and points of view about it and where you think it should be tweaked. It would be great if the result would lead to something concrete enough to be able to kick off the process in the near future. Debian-devel thread: https://lists.debian.org/debian-devel/2018/07/msg00453.html [1] https://debconf17.debconf.org/talks/233/

The idea for this session it to get together and as discuss all things autopkgtest/Debian CI and any related aspects. If you have ideas on how to test your package but don’t know exactly how to wire things up for running with autopkgtest, want to share your joy and/or your frustration with the tools or with the environments, or have tips or questions on writing autopkgtest tests, this is for you.

FAI was chosen as the standard tool to build cloud images. This talk explores the experiences of using FAI to build live images for ARM based platforms, such as 96boards Hikey and Dragonboard 410C. Using standards compliant firmware, same FAI image can be booted from many different ARM platforms without modifications. Since on ARM platforms using premade images remains more popular than using installers, the talk will discuss how Debian could provide such images for people. Talk slides available at https://people.debian.org/~riku/arm-fai.js/

Though it is not strictly debian related, archlinux share lots and lots of similarities with the debian community. Since there is no such thing as an archconf, we would like to use this opportunity to exchange ideas about archlinux development, package management and ways to get involved. We will be joined by archlinux local team member Felix Yan from China and Kerwin Tsai from Taiwan. Extremely laid back, come hang out to talk about anything you want regarding thsi distribution.

On May 25th, the EU's General Data Protection Regulation went into effect. This changes how every organisation needs to treat personal data. What does this mean for Debian? We have a data protection team which acts as an external contact point and an internal advice service, but Debian has not otherwise prepared for GDPR. We would like to talk about what the team does, does not and how Debian should approach the GDPR.

With the saturation of technology in our lives, free software has become more important than ever. You can find computers in the walls of your home and woven through the walls of your heart. With the advent of electronic voting, and the possibility of an all-online census, questions of software safety and user freedom are now touching parts of our lives we may not have thought about before. If you've ever wondered to yourself whether something is a free software issue, the answer is probably yes. Join cyborg lawyer and Software Freedom Conservancy executive director Karen Sandler and free software activist and Free Software Foundation campaigns manager, Molly de Blanc to discuss the wide range of what is a free software issue and why it's important to view our technology issues through that lens. Together, we'll discuss how to talk about free software from different perspectives, drawing the connection between issues of software and user freedom to issues ranging from institutional racism to avocado toast. Bring your questions and the topics you want to connect to free software.

The goal of this talk is to give the whole Debian community an update on the state of Reproducible Builds in Debian and in the whole free software world. It's been 5 years since Reproducible Builds were first introduced to the Debian community at large at DebConf13 in Vaumarcus and much progress has been achieved since. In this talk we will present some milestones we have reached since then, show where our current blockers are and give an outlook on what we consider still achievable until the Buster freeze. While it is true that we have been quite succesful in promoting Reproducible Builds, both the concept as well as actual patches in a great number of projects, too many people are misled by our "93% of Debian packages are reproducible (in theory)" statistics and other things. So, to sum up, Buster is not frozen yet and so we are still working on making Buster as reproducible in practice as possible. And we want to go even further in future! To achieve this we want and need to take all of Debian with us on this journey.

we'll try to squash as many Python 3.7's transition related bugs as possible and answer questions one might have about Debian Python related issues at the same time

This session will start with an update on the state of Debian packages used for electronics work, then transition to a discussion about work needed in the future. Anyone who uses or would like to use Debian's electronics packages is more than welcome to attend, ask questions, and contribute to the discussion!

Once again, lightning talks return to DebConf!

Discussion about the current state of the Debian Policy Manual and related documents. Expected topics of discussion include: - where volunteer time is most needed - Q&A about the process by which Policy is modified - difficult normative bugs that are stuck and how we might unstick them - Sphinx issues: remaining bugs and infrastructure needed for translations - recruiting volunteers to translate Policy. Not strictly within the remit of Policy, but something we might discuss, is the state of the Developer's Reference, and other pieces of Debian internal documentation.

The philosophy of free software is well known, but speak to hardware, it is a bit different. We want to talk about open hardware and make people involved. Who is working on freely licensed Open Hardware? What projects exist? How to people solve challenges? We would also like to talk and discuss how to collaborate across projects and what funding models exist.

Using a library without being exposed to any of its dependencies & without requiring recompilation of the binary that pulls it in. The goal is to improve portability of programs that are distributed with runtimes (cf flatpak) but which still need access to some libraries from the host (eg libGL) without requiring recompilation of either the host libraries or the application+runtime. The background: https://people.collabora.com/~vivek/dynamic-linking/segregated-dynamic-linking.pdf The code: https://gitlab.collabora.com/vivek/libcapsule A previous version of the talk (which is being updated a bit): Slides: https://people.collabora.com/~vivek/libcapsule.pdf Video: http://meetings-archive.debian.net/pub/debian-meetings/2017/mini-debconf-cambridge/segregated-dynamic-linking.vp9.webm

In this talk I will be showing tooling that is being used in BMW to test embedded systems with hardware control, test execution, log collection and log analysis. The tooling will be released to open source and integrated into Debian (hopefully before this talk).

This BoF is here to discuss fast, on-demand creation of lightweight (but secure!) sandboxes. This enables a variety of applications: - sbuild/pbuilder-style build environments with stronger isolation; - sandboxing of regular, packaged application, esp. desktop applications; - safer, and more isolated, development environments; - ... Plainly, we have situations where we run untrusted code (either a large desktop application exposed to a variety of attack vectors, or we literally ran `{pip,npm,cargo,whatever} install`) and want to reduce the privileges this code runs with (i.e. it may not do everything your current user can do), the harm it can do, and the attack surface towards the rest of the system. There are current efforts to address this, like Flatpak and Snap for desktop applications, and Docker containers for development, but they come with very severe shortcomings: they all involve some (unspecified) upstream shipping a complete chroot-like image, which is a return, in a sense, to static linking (or at least it has all the same issues as far as security support is concerned). Moreover, Docker isn't designed a s a security boundary, and as such fails to provide strong isolation and security. We can however be inspired by those efforts, and take advantage of the support they introduced in various upstream projects: what if when a users start LibreOffice (or enter their code directory) we could install the necessary packages to a fresh environment, fast enough, and start the application (or subshell) in a sandbox? We could get the security and privacy benefits of those technologies (prompting users before enabling webcam, only granting access to explicitly-requested files, stopping random code from the Internet from riffling through your ~/.gnupg), but still use software packaged in Debian, with all the ensuing goodness (security support, DFSG-freedom, ...)

Debian in my school ------------------- As a teacher of physics and chemistry (and marginally, computer science) in a French high school, I have to bring reliable applications and tools to my students. Even if Debian will finally spread the world, it has not yet pervaded the end-user computers which my students can access. An instant Debian environment ----------------------------- Here comes "[Jean Bart - Knoppix](ftp://usb.freeduc.org/freeduc-usb/freeduc-jbart/index.html "download the disk image ...")", the pocket Debian live thumbdrive, which allows my students to boot Debian's scientific environment in a single minute. In tight agreement with the employee who manages my school's computers, we let users boot the machines from external disks, like this particular thumbdrive. Touring through the scientific applications intended for students ----------------------------------------------------------------- During the short talk, I shall give an overview of the scientific applications which are available in this particular environment, present shortly which of them are most used by the students, and which less frequently. One of these applications drives a low-cost, yet powerful data acquisition and signal generating [box](http://expeyes.in/ "change your computer to a science lab ..."), which provides quite a complete scientific workshop, with an oscilloscope and a few signal sources. I am eager to hear suggestions for alternatives uses and for improvements of this appliance.

### Rethinking of debian/watch rule The debian/watch file is used to check the newer version of the upstream release and it makes easy to download if you need. Once debian/watch is ready for the package, you may not care so much about the existence of it anymore. But until you make it in good shape, you may hit common mistakes in your debian/watch. It is well documented in [WiKi page](https://wiki.debian.org/debian/watch), and there are many practical examples, but is it kindly enough for new package maintainers? ### Target audience * Debian contributor/maintainer who will work on ITP or something * Debian developer who will maintain devscripts ### What will talk about In this session, I'll talk about rethinking of debian/watch rule. Are there any kind of more simple, easy to maintain, cover most of the use case which can integrate seamlessly into current debian/watch? I would like to provide some experience with it and introduce & share a thought expertments with you from the point of view of Debian contributor if it is possible.

GNU Guix is a build system... or is it a package manager... or an operating system? Regardless of what angle you're looking at it with, it brings a twinkle to my eye lately. As a user, maintainer and developer of Debian for the past sixteen years, I've tried various other Linux distributions but few really seem to offer anything significantly different. Other distros have rarely left me feeling the intense curiosity, excitement and maybe even a bit of swooning that you might find with something genuinely new in your life. Some of the exciting features of GNU Guix include functional package management, reproducibile builds by design, trivial container and virtual machine instantiation, transactional upgrades and rollbacks, user specific package installation, and user customized packages. There's even some configuration management built-in. It's a relatively new, small developer community. They understand Free Software in ways very similar to Debian. They're welcoming and make it easy to contribute improvements and fixes large and small. There are some rough spots, and I'll try not to glaze over them despite my enthusiasm. The grumpy old sysadmin within will have some thoughts to share as well. Perhaps most exciting is that love and crushes are not exclusive; Debian and GNU Guix can coexist concurrently on the same running system, it just requires setting some reasonable expectations, and being willing to work some things out now and then. https://www.gnu.org/software/guix/

Upgrades often involve redownloading package content that is already on your system, wasting bandwidth, and thus potentially time. debdelta has been around for quite some time solving the bandwidth problem, but it's approach to deltas is slow - it reconstructs .deb files, including compression; hence with a DSL connection, it's going to be slower than no deltas. This talk introduces [a new approach to delta upgrades](https://wiki.debian.org/Teams/Dpkg/Spec/DeltaDebs "a new approach to delta upgrades") that is substantially faster than debdelta; and, with tiny patches to dpkg, these deltas can be installed just like a .deb - without needing to reconstruct anything-

The Debian System Administration team will provide a status update on its activities since DebConf17 and will discuss objectives for the following year.

Over the last months, I've been trying to package an up-to-date version of Docker for Debian. I started this task with only a rough knowledge of Debian packaging. I discovered Go from zero, and especially the development practices in use by the Golang community. I got in touch with the Debian Go packaging team, and learned a lot more about Debian packaging tools, infrastructure, and practices. In this 20 minutes talk, I would like to provide some feedback on this experience, things I learnt and would like to share to an audience that might not be familiar with the issues faced by the Go packaging team. In short: - what is the difference between the Docker package provided by docker.com, and the package provided by Debian? - what makes Docker, and more generally Go, packaging difficult? The audience would be people interested in Go packaging, and wanting a quick, simple presentation of the challenges. Or people wondering why the Debian Docker package lags behind. Or Go packagers curious about the feedback from a newcomer.

Steve McIntyre leading a small group of interested contributors through the process of building official Debian CD images.

This is a talk for everyone. Starting from Debian, I have been for a long time part of various groups where diversity is accepted and valued, and it has been an invaluable supply of inspiration, allowing my identity to grow with unexpected freedom. During the last year, I have been thinking passionately about things such as diversity, gender identity, sexual orientation, neurodiversity, and preserving identity in a group. I would like to share some of those thoughts, and some of that passion.

Debian and the Free Software Foundation, along with its GNU Project, share many goals and ideals. They are two of the most mature and dedicated organizations working in the free software movement. This is a great opportunity to talk in person about how they can better work together and inspire each other. FSF members (and potential members) will meet to talk about the FSF’s work, the FSF's relationship with Debian, and progress of the movement as a whole: * A very brief update by the FSF’s executive director and campaigns manager on highlights of the FSF’s work since the last DebConf * Feedback (positive and negative) from members, and a little brainstorming about what the FSF should and shouldn’t be doing * A review of the current relationship between the FSF and Debian * A discussion of areas for collaboration, focused on projects that could be completed or significantly advanced before the next DebConf Recognizing that we can't cover everything in 45 minutes, at the beginning, we'll choose some specific topics to focus on under this general Debian logo umbrella. Past sessions at DebConf have led to concrete positive results like collaboration on the hardware database at https://h-node.org/. Let’s have another productive one!

cryptsetup(8) is a popular tool to setup block-device encryption, usually based on the kernel's `dm-crypt` module. The debian package comes up with its own set of features such as initramfs integration, which enables encryption of root devices, resume devices, and other devices required at early boot stage. I will briefly talk about the new “LUKS2” format, which is not the default yet but is available since upstream [released v2.0.0](https://kernel.org/pub/linux/utils/cryptsetup/v2.0/v2.0.0-ReleaseNotes) last autumn. However the emphasis of the talk is on the Debian-specific features (such as key scripts, remote disk unlocking, storing key material directly in the initrd, etc.) and which use-case each of them covers. Most of these features have been added along the years per popular request; but as it turns out they are not always well known, and many users are still using more or less brittle workarounds while they could use our scripts — and blame us for regressions :-) — instead. I will conclude by sharing some of our future plans, the other features we'd like to have, the challenges and the blockers.

The pkg-perl team will again take the opportunity to meet in person for discussing current topics and planning future work. Items for discussion and work are collected at https://wiki.debian.org/Teams/DebianPerlGroup/OpenTasks

Discussion session for the Debian website team: - VCS Migration - it's done! - Post-mortem and future work - (re)Design work for the future - Content - what do we have? Enough? Too much? Potentially many more topics, could be a busy session!

Debian, as a collection of software packages and components, is known to be one of the largest software projects in the history of mankind. Combined with a traceable history over many years, the artefacts created by Debian developers and users make it one of science's favourite targets to quantitatively or qualitatively understand how real-world software development works (or does not), how people collaborate, and many other other related questions. Unfortunately, while scientists make ample use of the resources and artefacts created by FLOSS and friends, the exchange of insights and ideas does not seem to extend in both directions: Developers, users and integrators are often unaware of results obtained in science. This talk will introduce the Debian community to a selection the most important results obtained by scientific (software engineering) research, with a special focus on large-scale socio-technical analysis of projects like Debian, and the possible implications and improvements these may bring to Debian development itself.

Pretty much an overview about Deepin: the DE, the distribution, the porting progress to Debian.

Most people have heard of DNSSec, which provides integrity of DNS requests and responses but not privacy. DNS requests and responses are still sent over the wire in plaintext, available for eavesdropping and traffic analysis. There are a number of newer protocols to protect the privacy of requests, like DNS-over-HTTPS, DNS-over-TLS and DNSCrypt. There are also a number of new public DNS resolvers available that support some or all of these newer protocols. This talk will explore the protocols, the service providers offering encrypted public DNS resolvers and how to configure Debian to use them.

Bdale and Keith love to design, build, and fly high-power model rockets. They even started a small business together to manufacture completely open design hflight computers and related electronics that are now widely-known, used, and respected in the rocketry hobby. What not everyone knows is the role that Debian plays in all of this! Punctuated by many cool pictures and videos of rockets, Bdale and Keith will explain how Debian is part of every aspect of their involvement in the rocketry hobby and Altus Metrum, LLC.

Now, Ed25519/X25519 is getting popular, **Gnuk Token** can be a practical choice for Debian Developers and Users. In this short talk, we will explain the typical use case of **Gnuk Token** with **GnuPG**, and how **GnuPG** components (gpg front-end, gpg-agent, and scdaemon) interact. We will explain: - Use of gpg-agent as ssh-agent - Storing private keys on physically independent device may reduce the attack surface - Using Gnuk Token is convenient when we use multiple computers This is an extension to the talk in Debconf17 (GnuPG 2.1 Explained for Everyone).

During this session we'll provide a quick update on the current status of the Puppet and PuppetDB packages. We will also discuss about Puppet's future in Debian and how people can help. Whether you're just using Puppet, or you would like to be involved in the Debian Puppet team, this BoF is for you!

BoF for the Debian Go Packaing Team. As discussed on the team's mailing list [here](https://lists.alioth.debian.org/pipermail/pkg-go-maintainers/Week-of-Mon-20180402/020614.html "pkg-go mailing list discussion"). Team Website: https://go-team.pages.debian.net/ Salsa Team: https://salsa.debian.org/go-team

Displaying text is the most common interface to convey information from computer systems to humans. On a Linux system there is a variety of techniques for rendering text some of which are used more or less on modern systems. Many of those text rendering techniques originate from different time periods of computing history and rendering text in graphical environments is more complex than often thought off. We find two approaches in Linux systems for displaying text: - using bitmap fonts designed for fixed resolution displays - rendering text based on scalable glyph shapes using a stack of software components for rasterisation, text shaping and text layout. This talk will give an overview on the different techniques, software and standards for font rendering on Linux systems in the context of their historical origins. [Slides (PDF)](https://salsa.debian.org/debconf-team/public/data/misc/blob/master/talks/dc18/fontrendering.pdf "Slides (PDF)")

Debian in my school ------------------- As a teacher of physics and chemistry (and marginally, computer science) in a French high school, I have to bring reliable applications and tools to my students. Even if Debian will finally spread the world, it has not yet pervaded the end-user computers which my students can access. An instant Debian environment ----------------------------- Here comes "[Jean Bart - Knoppix](ftp://usb.freeduc.org/freeduc-usb/freeduc-jbart/index.html "download the disk image ...")", the pocket Debian live thumbdrive, which allows my students to boot Debian's scientific environment in a single minute. In tight agreement with the employee who manages my school's computers, we let users boot the machines from external disks, like this particular thumbdrive. Experimenting the applications ------------------------------ Attendees of the workshop are welcome to ask for any use we might make of the live thumbdrives which will be demonstrated. I shall bring a few [Expeyes](http://expeyes.in/ "Let's have fun with science") boxes, and give an overview of scientific experiments which can be performed with such a frugal technology setup. More than one experiment may be fun!

Annual get-together for the Arm porters and users, to discuss the state of the multiple Arm ports: - Current status - Future plans - Issues …

The Debian riscv64 port has made considerable progress, reaching 80% of packages built at the time of this writing! There is support upstream in linux, glibc, and important core toolchains. There is real-world hardware, and some of it is even in the hands of Debian Developers and other community members. There is support in Debian's qemu packages, for those who don't have hardware. What are blockers and other issues that need help to make this port a properly supported port for Debian? https://wiki.debian.org/RISC-V

Where will DebConf20 be held? It's your opportunity to suggest the best possible place in the world: Your own city! The presented bids are: - India (specific location not yet decided): [Slideshow (ODP)](https://salsa.debian.org/debconf-team/public/data/misc/blob/master/talks/dc18/dc20_in_your_city/debConfInIndiaBid2018NewVersion.odp "Slideshow (ODP)") - Israel (Haifa): [Slideshow (ODP)](https://salsa.debian.org/debconf-team/public/data/misc/blob/master/talks/dc18/dc20_in_your_city/bid-israel-2020.odp "Slideshow (ODP)"), [Slideshow (PDF)](https://salsa.debian.org/debconf-team/public/data/misc/blob/master/talks/dc18/dc20_in_your_city/bid-israel-2020.pdf "Slideshow (PDF)") - Portugal (Lisbon): [Slideshow (ODP)](https://salsa.debian.org/debconf-team/public/data/misc/blob/master/talks/dc18/dc20_in_your_city/SlideDebConf20Portugal.odp "Slideshow (ODP)") - Slovakia (Bratislava): [Video (webm)](https://salsa.debian.org/debconf-team/public/data/misc/blob/master/talks/dc18/dc20_in_your_city/debconf20-in-bratislava.webm "Video (webm)"), [Subtitles](https://salsa.debian.org/debconf-team/public/data/misc/blob/master/talks/dc18/dc20_in_your_city/debconf20-in-bratislava.srt "Subtitles")

Tablet devices are too attractive mobile computer devices now. They are too inexpensive, lightweight, large display, touchscreen, Wifi, Bluetooth, battery and more. They can buy only US$ 20~ (only used Tablets). Used Tablet is more inexpensive than RaspberryPi 2 or 3. But they can use iOS, Android, Windows only. No Linux Distributions on Tablet. They can't use LibreOffice and the other Linux applications. New generation peoples doesn't have to need and want to use traditional computer? Smartphones and tablets are necessary to use Linux Distributions for new generation peoples. I feel that it will become an era when it is difficult for new generation peoples to use desktop Linux. In this session, I will talk about 「Install and use Intel ATOM Tablet, UMPC and install grub2 bootloader on Debian」. The Linux kernel evolved rapidly from Kernel 4.9LTS to 4.16LTS. A lot of inexpensive devices can use more attractive Linux devices driver now, like a touchscreen. Recently Linux Kernel has evolved rapidly to use on x86 ATOM devices, Tablet, Stick PC, Apollo-Lake devices, UMPC GPD-WIN and GPD-Pocket. A lot of mobile devices can use Debian, and others now! Let's install Linux on Tablet and any mobile devices.

Discussion about improvements necessary for the sponsorship team / fundraising: - Allocation of dedicated contacts - Follow up on the financials / tracking - Use of Kanboard for fulfillment tracking instead of git? - ...

Debian Derivatives BoF Session. There are quite a few people present in DebConf from multiple Debian Derivatives. And it would be a great opportunity for each of them to share/collaborate/discuss the issues and opportunities on Debian derivatives development. Also it will give an opportunity to Debian derivatives team to discuss on how Debian and derivatives collaborate with each other more inclusively. A tentative list of various distributions present in DebConf are 1. PureOS 2. Hamara Linux 3. Tails 4. Deepin Linux 5. GRML 6. Meilix OS 7. AIMS Desktop There may be more people from more distributions which are not in the list. This list is just what I made from my interactions with people during DebCamp and DebConf. Please let us know if there are more distributions which are not listed above.

Wikimedia's ContentTranslation tool helped translating more than 3,00,000 articles since 2015 which helped narrowing gap between big and small Wikipedias. This talk is about how Debian packaging of Apertium Machine Translation played key role in it and how we can improve current Machine Translation packaging in Debian. Talk isn't technical but contains some thoughts on packaging as background.

The computer is a tool to meet people. Many website also do that, FetLife, Facebook and Couchsurfing are some examples. I do post-processing of social network websites to enhance my user experience. To narrow in the things I'm concerned about.

When software developers try to apply Linux into their embedded products, they would be able to choose their base system from various distributions today, which could be divided into two kinds; binary based and source code based distributing. Debian, one of the major binary based distributions, has stability and long-term support from its strong communities, which are essential stuff especially for civil infrastructure system. On the other hand, additional efforts for customizations and management of product releases are sometimes needed to cover various product requirements. Kazuhiro will introduce approaches for applying Debian into embedded systems with Yocto Project build tools. In this talk, he will show some possibilities in combining Debian and benefits from Yocto Project, examples of customizations and resource managements, lessens learned from product developments thus far, and future plans for getting better affinity with Debian and other communities.

Hanjp-IM is a project for building an Input Method that can type Japanese using Korean Hangul and it's hosted by Ubuntu Korea Community(Ubuntu Korean LoCo Team) I'll talk a story about how project was started and what we've done so far. Note: Hanjp-IM has no working prototype yet. So don't look forward about that. [Slides](https://salsa.debian.org/debconf-team/public/data/misc/blob/master/talks/dc18/debconf-hanjpim.pdf "Slides")

SUSI.AI is a personal assistant framework for personal assistants developed with the FOSSASIA community. It is an alternative to proprietary solutions like Alexa, Siri and Google Home. Other Open Assistants are MyCroft and Jasper. In this session we will discuss the next steps in bringing free personal assistants into Debian, talk about components, architectures and requirements. An important aspect that we will look at are also privacy and offline capabilities. Links: * Website: https://susi.ai * Github: https://github.com/fossasia?utf8=%E2%9C%93&q=susi

During the "Ignoring negativity" talk there was no time for Q&A, and in later discussions it has become clear that there is much more conversation to be had in this area. We'd like a second session to allow more people to participate. This is intended to be purely Q&A and a discussion between the people in the BOF.

Debian Account Managers, New Member Front Desk members, Application Managers, Applicants and everyone interested can join in a discussion about how the New Member process works and how it can be made better

During and After my talk “Linux Font Rendering Stack” I was approached and asked about issues in the font rendering stack for users of non-latin script. - Linux VT (text console) is pretty much useless for non-latin scripts - Japanese users get Chinese variants of some characters In this BoF we will discuss these and other problems and possible solutions. It is open to everyone interested.

It has been said that the scripts folks build up over time are an interesting source of knowledge about deficiencies in a system, codebase or population. Lets share samples of our personal script collections, discuss why they were needed, get advice on what we should do with them and what they mean about the world they were born in.

Meet the DebConf Committee. Discuss what worked well for DebConf18 and what can be improved for DebConf19 and beyond. Current and future DebConf organizers are invited to attend the session.

Debian is currently experimenting with AppArmor as a default mandatory access control system. This talk will introduce mandatory access control systems; discuss AppArmor's purpose; provide a quick overview of AppArmor's past, present, and future; and briefly cover daily use.

See you next year in Brazil! What can we expect from our trip to Curitiba? Get your questions ready for this session!

Time to say goodbye! Some practical indications, some thanks to our local teams, etc.