https://debconf14.debconf.orgThe published videos from DebConf 14Wed, 03 Aug 2016 16:20:34 GMTPyRSS2Gen-1.1.0http://blogs.law.harvard.edu/tech/rsshttps://summit.debconf.org/debconf14/meeting/155/qa-with-linus-torvalds/Linus will come by DebConf to do a small Q&A session with us.https://summit.debconf.org/debconf14/meeting/155/qa-with-linus-torvalds/Fri, 29 Aug 2014 20:00:00 GMThttps://summit.debconf.org/debconf14/meeting/108/debian-in-the-dark-ages-of-free-software/Arguably, Free Software has never been more successful than these days. Free Software is common place in many contexts, from embedded devices to supercomputers, ... including the space (with the ISS) and beyond! Free Software is also more and more common in education, it is subject of ad-hoc legislation around the world , and thanks to our friends at NSA it is also being looked with increasing interest by privacy-conscious citizens. Taking issue with such an optimistic view of the (Free) world, a pessimistic speaker is gonna argue that we are, on the contrary, about to enter the so called "Dark Ages of Free Software", where the user freedoms we have accrued over the past 30 years are at risk of being taken away by reckless technological trends. Unsatisfied with his own pessimism, the speaker will try to induce some of it into the audience, but only shortly before bringing the good news that distributions—and Debian in particular—have a fundamental role to play in Free Software's path toward a new enlightenment.https://summit.debconf.org/debconf14/meeting/108/debian-in-the-dark-ages-of-free-software/Sat, 23 Aug 2014 16:00:00 GMThttps://summit.debconf.org/debconf14/meeting/122/weapons-of-the-geek/Drawing on a decade of research on free software communities and Anonymous, I will discuss the hacker and geek contribution to activism and social change, especially in light of the dramatic series of leaks, hacks and whistle blowing of the last five years.https://summit.debconf.org/debconf14/meeting/122/weapons-of-the-geek/Sat, 23 Aug 2014 19:00:00 GMThttps://summit.debconf.org/debconf14/meeting/15/bugsdebianorg-database-ho/Brief overview of the current state of the BTS, new features, and new developments in the ongoing onslaught of bugs. https://summit.debconf.org/debconf14/meeting/15/bugsdebianorg-database-ho/Sun, 24 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/140/debconf-organisation-working-group/ DebConf organisation working grouphttps://summit.debconf.org/debconf14/meeting/140/debconf-organisation-working-group/Sat, 30 Aug 2014 10:00:00 GMThttps://summit.debconf.org/debconf14/meeting/136/notmuch-bof/ Originally inspired by the sup mail user agent (MUA), notmuch is a GPL3+ set of tools for for dealing with your mail (stored in Maildirs or similar) via searching and tagging. On top of the C bindings and a scriptable command line interface, the project directly supports user interfaces based on Emacs and VIM as well as integration with Mutt. We also support python, ruby, and go bindings. Other projects based on notmuch include curses based frontends written in python and Mercury, a fork of mutt using notmuch as a the backend, several web interfaces, and a virtual filesystem. Depending on audience demand, I could give a brief a tour of the notmuch "ecosystem", concentrating on the Emacs interface and command line tool. Otherwise, we can discuss what are the most irritating missing features, people can give demos, we can help each other configure various notmuch related things, and just generally have not much of a fixed agenda. https://summit.debconf.org/debconf14/meeting/136/notmuch-bof/Mon, 25 Aug 2014 15:30:00 GMThttps://summit.debconf.org/debconf14/meeting/138/tasksel-default-desktop-requalification/This session is about filling out a wiki page and defining a process, not making any kind of controversial decision.https://summit.debconf.org/debconf14/meeting/138/tasksel-default-desktop-requalification/Thu, 28 Aug 2014 11:00:00 GMThttps://summit.debconf.org/debconf14/meeting/24/dsa-team-round-tablebof/What has DSA done for you and what you can do for DSA.https://summit.debconf.org/debconf14/meeting/24/dsa-team-round-tablebof/Sun, 24 Aug 2014 14:30:00 GMThttps://summit.debconf.org/debconf14/meeting/88/infrastructure-updates-can-we-change-anything-in-less-than-2-years/The use of stable in our infrastructure and understandably conservative rules for backports, stable updates and infra changes make it very difficult to even test something like Build Profiles (or Mulitarch builds) (which need changes in build tools and core infra), never mind get them into widespread use, without waiting for a whole stable release cycle (these are just recent examples - it's a general problem). So this also means that it takes 2-4 years to make a change, which hampers progress. This session is a discussion on whether we can do anything to be a bit more nimble than this?https://summit.debconf.org/debconf14/meeting/88/infrastructure-updates-can-we-change-anything-in-less-than-2-years/Sun, 24 Aug 2014 19:00:00 GMThttps://summit.debconf.org/debconf14/meeting/144/my-pgpgpg-key-is-rsa-2048-bit-but-i-put-the-private-key-on-gnuk-token/In this casual session, I will demonstrate Gnuk Token, which is built by Free Software and free hardware design. I will demonstrate NeuG standalone device, which can generate random numbers at 70KiB/s, too. My PGP/GPG key is RSA 2048-bit now. I understand that some person doesn't want to sign my key, because it looks weaker. I develop Gnuk, the firmware for USB Token, which is compatible to OpenPGP card, under GPLv3. My original purpose/goal was not to put a person into a dilemma: computing freedom vs. better security. I think that I have achieved the goal somehow, and it's strong enough (RSA 2048-bit) and it's not that slow (1.4sec to sign), IMO. It is unfortunate for me that Debian community demands RSA 4096-bit or more. Thus, another dilemma is still there; longer key length or better control of private key by Free Software. Good news is that I have implemented Ed25519 (for signing) already, and going to implement Curve25519 (for decryption) in Gnuk. Besides, I am also GnuPG developer, and try to implement Curve25519 support now. It will be good if GnuPG 2.1 will be released and people will enjoy Gnuk Token with Ed25519/Curve25519 until Debconf15 in Germany. During the development of Gnuk, I develop NeuG, the true random number generator to generate private keys on the device. The entropy source is built-in A/D converter. I realized that this feature is very useful, and I build standalone device (just for generating random numbers). FST-01 is a reference board for Gnuk/NeuG. It has STM32F103 as MCU which runs at 72MHz. It has no crypto accelerator. Schematic design and PCB design are available as free hardware design. Material is available at gobby.debian.org: debconf14 -> bof -> gnuk https://summit.debconf.org/debconf14/meeting/144/my-pgpgpg-key-is-rsa-2048-bit-but-i-put-the-private-key-on-gnuk-token/Thu, 28 Aug 2014 10:00:00 GMThttps://summit.debconf.org/debconf14/meeting/95/grub-ancient-and-modern/GRUB has moved on a great deal from its beginnings, when most of us just used it over LILO because you didn't have to remember to reinstall your boot loader when you installed a new kernel. Nowadays, thanks in part to the work of several Debian developers, it's a very powerful boot loader ported to many architectures that's actually fun to hack on. I'll be giving a whistle-stop tour of its history and design, and laying out some of the things where the Debian GRUB team could do with help.https://summit.debconf.org/debconf14/meeting/95/grub-ancient-and-modern/Sun, 24 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/64/one-year-of-fedmsg-in-debian/Fedmsg, the federated messaging infrastructure, was built by the Fedora Infra team to streamline the communication between its services. During the Google Summer of Code in 2013, Simon Chopin worked under my tutelage to bring fedmsg to Debian. For a year, fedmsg has sent messages regarding the BTS, package uploads, and mentors.debian.net. This session will present fedmsg, and start a conversation on where we should go from here.https://summit.debconf.org/debconf14/meeting/64/one-year-of-fedmsg-in-debian/Sun, 24 Aug 2014 14:30:00 GMThttps://summit.debconf.org/debconf14/meeting/101/status-report-of-the-debian-printing-team/During this free-form talk, we'll take a look at the current status of the Debian Printing stack as well as the upcoming challenges.https://summit.debconf.org/debconf14/meeting/101/status-report-of-the-debian-printing-team/Sun, 24 Aug 2014 16:00:00 GMThttps://summit.debconf.org/debconf14/meeting/104/lsb-for-debian-bof/Let's discuss what we want to do with src:lsb, lsb-base and friends.https://summit.debconf.org/debconf14/meeting/104/lsb-for-debian-bof/Sun, 24 Aug 2014 19:00:00 GMThttps://summit.debconf.org/debconf14/meeting/58/meet-the-technical-committee/An opportunity to meet the members of the Debian Technical Committee who are in attendance at Debconf, hear the status of open issues, and discuss pending and future issues with the committee.https://summit.debconf.org/debconf14/meeting/58/meet-the-technical-committee/Mon, 25 Aug 2014 10:00:00 GMThttps://summit.debconf.org/debconf14/meeting/11/status-of-the-debian-openpgp-keyring/The Debian OpenPGP keyring is a vital part of the project's infrastructure: It provides a secure way to ensure each participant's identity in a way amenable to the geographically distributed nature of the project, and is used for basically all actions requiring authentication — Package uploads, General Resolution votes, mails to the =-announce= lists, etc. For several years already, the keyring maintenance team has been pushing to migrate to more secure keys. In July 2010, the last PGPv3 keys were replaced. The current push is to get developers to migrate from older 1024D keys to (at least) 4096R keys. In this talk, we want to: - Introduce keyring-maint's work processes and policies, to get them better understood by the overall Debian community - Present the migration process to stronger keys in numbers, highlighting the migration rhythm and possible issues - Delineate a consensuated migration plan, with deadlines to be followed, to allow for a complete migration to 4096R and higher keys - Reviewing, as a group, what constitutes proper identification and what we require. - Address all of your questions regarding keyring maintenance in Debian https://summit.debconf.org/debconf14/meeting/11/status-of-the-debian-openpgp-keyring/Mon, 25 Aug 2014 11:00:00 GMThttps://summit.debconf.org/debconf14/meeting/100/python-bof/any Python related topics, including moving DPMT/PAPT repo to git and PyPy3https://summit.debconf.org/debconf14/meeting/100/python-bof/Mon, 25 Aug 2014 10:00:00 GMThttps://summit.debconf.org/debconf14/meeting/103/debian-java-packaging-bof/The adoption of maven is creating new kinds of dependency hell for Debian. The "download dependencies at compile time" approach is antithetical to the idea of distribution-provided libraries, and encourages authors to be slap-dash about dependency management, and API stability. If people are going to package java apps for Debian, then we need a better way to build java library packages, perhaps by enhancing maven-debian-helper. This BoF aims to propose solutions to this problem.https://summit.debconf.org/debconf14/meeting/103/debian-java-packaging-bof/Mon, 25 Aug 2014 11:00:00 GMThttps://summit.debconf.org/debconf14/meeting/44/debian-installer-and-cd-bof/General discussion on how things are going in the team and future planshttps://summit.debconf.org/debconf14/meeting/44/debian-installer-and-cd-bof/Mon, 25 Aug 2014 10:00:00 GMThttps://summit.debconf.org/debconf14/meeting/12/use-perl-annual-meeting-of-the-debian-perl-group/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 http://wiki.debian.org/Teams/DebianPerlGroup/OpenTasks https://summit.debconf.org/debconf14/meeting/12/use-perl-annual-meeting-of-the-debian-perl-group/Mon, 25 Aug 2014 11:00:00 GMThttps://summit.debconf.org/debconf14/meeting/30/mia-team-bof/The Purpose of the MIA(Missing In Action) team is to track the inactive developers/maintainers with a main concern for the quality of their packages. In the past years the MIA process and tools have not changed so much, the purpose of this discussion is to improve our process, get more feedback of what we are doing good, what we are doing wrong and how can we improve; Before the discussion starts we will give a brief introduction on how does the MIA team works right now, which tools we have at hand and how do we handle the MIA process.https://summit.debconf.org/debconf14/meeting/30/mia-team-bof/Tue, 26 Aug 2014 10:00:00 GMThttps://summit.debconf.org/debconf14/meeting/69/gnupg-in-debian-bof/GnuPG is a critical part of debian infrastructure. Upcoming changes to GnuPG may have significant impact on debian. This will be a convening of people involved with debian packaging of GnuPG and its related tools, and an attempt to plan for the future. Some topics for discussion: * Making gpg an alternative that can be gpg1 or gpg2 * Thoughts on making the default gpg be gpg2 (or gpg 2.1?) * More shared maintenance via pkg-gnupg. * cross-building and gpg's place in bootstrapping debianhttps://summit.debconf.org/debconf14/meeting/69/gnupg-in-debian-bof/Tue, 26 Aug 2014 11:00:00 GMThttps://summit.debconf.org/debconf14/meeting/70/quit-logging-or-data-minimization-in-debian/Computer users leave traces of data on local and remote machines that record their activity. These records can cause problems for people who do not want their activities tracked, and they facilitate both mass and targeted surveillance. Service operators are put in an uncomfortable position because of the existence of this data: they have a responsibility to protect their users, but they may also be at risk of compelled data disclosure against their users' interests. One way to avoid this problem is to reduce or eliminate the quantity of data generated and stored by any system by default in its regular operations. If you don't have the data, it can't be used against you or against your users. Debian is in a good position to shape norms around this -- we can configure default logging levels; we can tune what specifically gets logged, and we can determine how long logs are kept by default. This is a discussion about how to achieve the goal of data minimization within Debian, while considering the tradeoffs and consequences of this sort of change. We should cover at least: * what kind of statement (if any) about default levels of logging for debian packages might belong in Debian Policy * points of convenient control for minimizing logging on standard debian systems * different system logging architectures and how they can support data minimization * how to provide both data minimization and useful debugging information at a system levelhttps://summit.debconf.org/debconf14/meeting/70/quit-logging-or-data-minimization-in-debian/Tue, 26 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/92/debian-long-term-support/What is the Debian LTS, what are the experiences so far, what are the plans and expectations?https://summit.debconf.org/debconf14/meeting/92/debian-long-term-support/Tue, 26 Aug 2014 14:30:00 GMThttps://summit.debconf.org/debconf14/meeting/123/looking-back-on-a-debian-summer-of-code/This joint session will be the occasion for this year's crop of Debian Google Summer of Code students to present the work they have done in Debian this summer. The planned presentations so far are: - debmetrics: powering metrics.debian.net — Joseph Bisch - Recursively Building Java Projects and their Dependencies — Andrew Schurman - WebRTC — Juliana Louback - Lil'Debi-Running Debian on Android — Kumar Sukhanihttps://summit.debconf.org/debconf14/meeting/123/looking-back-on-a-debian-summer-of-code/Tue, 26 Aug 2014 19:00:00 GMThttps://summit.debconf.org/debconf14/meeting/59/spi-bof/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.https://summit.debconf.org/debconf14/meeting/59/spi-bof/Tue, 26 Aug 2014 10:00:00 GMThttps://summit.debconf.org/debconf14/meeting/7/debsources-powering-sourcesdebiannet/Debsources is an infratructure and a web application to publish on the web the entire source code of Debian, allowing to search and browse through it. The main Debsources instance, currently running at http://sources.debian.net , spans Debian history from Debian early releases of the 90s to sid and experimental. In this talk I will present Debsources and sources.d.n, highlighting plans for the future and how people could hack on Debsources for fun and/or profit.https://summit.debconf.org/debconf14/meeting/7/debsources-powering-sourcesdebiannet/Tue, 26 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/78/reproducible-builds-for-debian/How can we enable multiple parties to verify that a binary package has been produced untampered from a given source in a distribution like Debian? With free software, anyone can inspect the source code for malicious flaws. But most distributions provide binary packages to their users. We would like them to be able to verify that no flaws are introduced during the build process. The idea of “deterministic” or “reproducible” builds is to enable anyone to reproduce a byte-for-byte identical binary packages from a given source. Last year at DebConf13, a last minute BoF kicked off the effort. The last large scale experiment on 5151 source packages yield 62% of them producing matching binaries after a couple changes to the toolchain. A pretty encouraging result! The presentation will explain why we need reproducible builds, what has been done over the past yeast, the problems that have been identified so far and possible solutions. A subsequent BoF will allow interested parties to discuss solutions to some hard problems that were found during this first year of research.https://summit.debconf.org/debconf14/meeting/78/reproducible-builds-for-debian/Tue, 26 Aug 2014 14:30:00 GMThttps://summit.debconf.org/debconf14/meeting/109/removing-obsolete-packages-for-fun-and-profit/For various reasons, obsolete packages can accumulate in Debian. They may be old versions kept around for compatibility. They may be things long obsoleted by a newer piece of software. Eventually, they're all cruft cluttering up our beautiful archive. I'll briefly walk through the work I did to remove old versions of automake from the archive, including dramatized accounts of bug filings, NMUs, tools used, and maintainers cajoled. Then I'll lead a discussion of how we can make this easier, around these areas: * Tools that are missing that could make this easier. * How to encourage maintainers to do the right thing. * Best ways to proceed with mass bug filings & NMUs. * What to do about the long tail of broken packages and obstinate maintainers. Hopefully we can share techniques and come up with ideas to make this easier in the future.https://summit.debconf.org/debconf14/meeting/109/removing-obsolete-packages-for-fun-and-profit/Tue, 26 Aug 2014 16:00:00 GMThttps://summit.debconf.org/debconf14/meeting/121/power-tuning-linux-a-case-study/In this talk we will do a reality-check in terms of the power consumption on off-the-shelve systems running “out of the box” Linux distributions. The goal is to prove how out-of the-box Linux distros on the latest commercial hardware is not optimal. We will demonstrate the steps needed to achieve optimal system power using various tools and analysis techniques including PowerTOP & Turbostat. Upon completion of the talk, the audience should understand the steps needed to properly configure an out of the box Linux distro to take advantage of the power features available on the latest Intel platforms.https://summit.debconf.org/debconf14/meeting/121/power-tuning-linux-a-case-study/Tue, 26 Aug 2014 19:00:00 GMThttps://summit.debconf.org/debconf14/meeting/99/auditors-trademark-teams-merged-bof/For members of the two teams to meet, and discuss plans for upcoming year. (Meeting of two teams is combined as there is overlap in team memberships.) Topics like roles of Debian's Trusted Organizations, and how best to manage Debian assets (including Trademarks) will be covered. If anyone is interested in the work of either team, team members will be available for Q&A.https://summit.debconf.org/debconf14/meeting/99/auditors-trademark-teams-merged-bof/Tue, 26 Aug 2014 11:00:00 GMThttps://summit.debconf.org/debconf14/meeting/86/web-and-wiki-bof/Regular meetup of the Debian WWW and Wiki teamshttps://summit.debconf.org/debconf14/meeting/86/web-and-wiki-bof/Tue, 26 Aug 2014 11:00:00 GMThttps://summit.debconf.org/debconf14/meeting/79/reproducible-builds-for-debian-finding-solutions/How can we enable multiple parties to verify that a binary package has been produced untampered from a given source in a distribution like Debian? While trying to get reproducible builds for Debian packages, several problems were identified. For some, like paths encoded in debug files, we are still missing good solutions. Let's review them and find great ideas!https://summit.debconf.org/debconf14/meeting/79/reproducible-builds-for-debian-finding-solutions/Tue, 26 Aug 2014 19:00:00 GMThttps://summit.debconf.org/debconf14/meeting/81/bits-from-the-dpl/Discussion of the State of the Union^HProjecthttps://summit.debconf.org/debconf14/meeting/81/bits-from-the-dpl/Thu, 28 Aug 2014 14:30:00 GMThttps://summit.debconf.org/debconf14/meeting/5/a-glimpse-into-a-systemd-future/Let's look at a future Debian system, taking full advantage of systemd components and features. This presentation will take an entirely different approach from past discussions of systemd in Debian. Rather than thinking about how to avoid or replace individual components, we'll look at how they fit together, and what unique functionality they provide. Finally, after exploring this world of the future, we'll return to the present and discuss ways to enable smooth transitions. We'll also explore facilities in systemd that support easier and better integrated selection of components, both for system services and within user sessions. Technologies covered include journald, systemd-networkd, socket activation, timer units, containers, and systemd user sessions. Goals include reducing boot time, reducing duplicate configuration, improving system manageability, improving battery life, and unifying graphical session startup.https://summit.debconf.org/debconf14/meeting/5/a-glimpse-into-a-systemd-future/Thu, 28 Aug 2014 16:00:00 GMThttps://summit.debconf.org/debconf14/meeting/90/whats-new-in-the-linux-kernel/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 3.10 and 3.16. 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. https://summit.debconf.org/debconf14/meeting/90/whats-new-in-the-linux-kernel/Thu, 28 Aug 2014 19:00:00 GMThttps://summit.debconf.org/debconf14/meeting/6/new-network-interface-manager-for-debian-ifupdown2/This talk introduces ifupdown2, a new network interface manager for Debian. ifupdown2 is a rewrite of ifupdown. It maintains backward compatibility with ifupdown. ifupdown2 is used on Cumulus Linux, a Debian based distribution for network switches. Existing tools for network interface configuration have several shortcomings when applied to network switches. These challenges include the lack of ability to handle interface dependencies, incremental updates to interface configuration without disruption, interface configuration validation and simplifying interface configuration in large scale deployments. The lack of such functionality increases operational burden. ifupdown2 attempts to solve these challenges through an implementation based on dependency graphs, querying running state before applying interface configuration, extensions to ifquery to support validation of interface configuration, templates for large scale cookie-cutter interface configurations, JSON support and more. ifupdown2 on github: https://github.com/CumulusNetworks/ifupdown2 ifupdown2 documentation on github: http://cumulusnetworks.github.io/ifupdown2/ https://summit.debconf.org/debconf14/meeting/6/new-network-interface-manager-for-debian-ifupdown2/Thu, 28 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/41/debci-and-the-debian-continuous-integration-project/The Debian Continuous Integration project, powered by the debci package, aims at constantly running tests against packages uploaded to Debian. In this talk I will present the origins and current state of the project, how it works and how to add test suites for your packages. There will be also a discussion of best practices for as-installed test suites for Debian packages. https://summit.debconf.org/debconf14/meeting/41/debci-and-the-debian-continuous-integration-project/Thu, 28 Aug 2014 14:30:00 GMThttps://summit.debconf.org/debconf14/meeting/2/automated-validation-in-debian-using-lava/This talk looks at how to extend the existing automated validation architecture recently added to Debian beyond the scope of Linux on ARM to include distribution kernel images, package combinations and installer images. https://summit.debconf.org/debconf14/meeting/2/automated-validation-in-debian-using-lava/Thu, 28 Aug 2014 19:00:00 GMThttps://summit.debconf.org/debconf14/meeting/22/validation-and-continuous-integration-bof/Planning and brain-storming for how to validate Debian. Which parts of Debian need (more) validation? How is that validation going to work? What new software is needed or what changes are needed to existing software to get this running? Who is going to do the work?https://summit.debconf.org/debconf14/meeting/22/validation-and-continuous-integration-bof/Thu, 28 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/62/acc-for-abi-breaks/ABI-compliance-checker (acc) is a tool that can be used to catch unintentional abi breakage, as well as to assert ABI stability of a release and validate 3rd party binaries to be compatible with a given release. A debhelper plugin dh_acc is also available, but the adoption has been very slow. A short presentation on what dh_acc is and how one can leverage it will be presented. Presentation will be followed by discussion on how to lower adoption barrier and/or provide abi compliance on a more holistic approach (e.g. do we want an archive-wide service for Debian similar to http://upstream-tracker.org/ ?) Type: BoF, presentation, discussion Tracks: QA, Validation & CI, Packaging and toolshttps://summit.debconf.org/debconf14/meeting/62/acc-for-abi-breaks/Thu, 28 Aug 2014 16:00:00 GMThttps://summit.debconf.org/debconf14/meeting/105/mips-bof/General discussion about the MIPS port, including the future mips64 and mips64el ports.https://summit.debconf.org/debconf14/meeting/105/mips-bof/Fri, 29 Aug 2014 10:00:00 GMThttps://summit.debconf.org/debconf14/meeting/25/debdry-debian-dont-repeat-yourself/Upstreams are doing their best packaging their tarballs, and then we redo most of their work when we debianise them. I personally find this situation wasteful and boring. I like how debhelper7 allows to write debian/rules files that describe only when something diverges from the norm, and I think that debianising a package should be the same. I want to debianise a package by just saying "I'm fine with everything upstream says, and put this in Section: foobar". I want to fix upstream's packaging by sending them patches instead of redoing it in debian/. I want most policy or toolchain updates to be handled with just a binNMU. I don't want to manually do any of the work that can possibly be done by a computer. debdry is a prototype tool that tries to address that by running autodebianisation tools, which exist and work reasonably well for at least perl, python, haskell, ruby and node.js, and then applying semantically significant, manually maintained tweaks, if any is needed. The bulk of my debian work should be adding Debian-specific metadata, testing, interacting with upstream, dealing with the BTS. It should not involve writing files that say that the README needs to be installed with the package documentation. Let's make it happen.https://summit.debconf.org/debconf14/meeting/25/debdry-debian-dont-repeat-yourself/Fri, 29 Aug 2014 11:00:00 GMThttps://summit.debconf.org/debconf14/meeting/43/state-of-the-arm/General discussion on how ARM is going: the existing armel and armhf ports, and the exciting new world of arm64.https://summit.debconf.org/debconf14/meeting/43/state-of-the-arm/Fri, 29 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/89/the-state-of-the-bootstrap/Update on the work on making debian bootstrappable. BuildProfiles infra and package-fixing, rebootstrap, cross-building, and recent port work, including news from last week's sprint.https://summit.debconf.org/debconf14/meeting/89/the-state-of-the-bootstrap/Fri, 29 Aug 2014 14:30:00 GMThttps://summit.debconf.org/debconf14/meeting/119/docker-debian/Bits from the Docker Maintainer. Brief overview of Docker, it's pros, cons, best practices and loads of opinions. https://summit.debconf.org/debconf14/meeting/119/docker-debian/Fri, 29 Aug 2014 19:00:00 GMThttps://summit.debconf.org/debconf14/meeting/61/upstream-guide-bof/Debian's Upstream Guide has grown organically since it was created. In this BoF we hope to improve the guide and make it more comprehensive and comprehendable. We will copy the wiki text into gobby, review the text, make changes and add new recommendations and push the changes back to the wiki. https://wiki.debian.org/UpstreamGuidehttps://summit.debconf.org/debconf14/meeting/61/upstream-guide-bof/Sat, 30 Aug 2014 11:00:00 GMThttps://summit.debconf.org/debconf14/meeting/91/putting-some-salt-in-your-debian-systems/Salt allows scalable infrastructure management, including provisioning new systems and managing them over their lifetime. In this talk I'll show how it makes managing Debian systems easier.https://summit.debconf.org/debconf14/meeting/91/putting-some-salt-in-your-debian-systems/Fri, 29 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/40/live-demos/If you would like to show off your project, here is the place! (Demonstrators are requested to attend a setup session beforehand in order to make sure they have the correct settings for the projector.)https://summit.debconf.org/debconf14/meeting/40/live-demos/Fri, 29 Aug 2014 16:00:00 GMThttps://summit.debconf.org/debconf14/meeting/42/debian-ruby-bof/Anual face-to-face meeting of the Debian Ruby team. Discussion of status, plans for the next release, and everything else. Ruby users are more than welcome to provide feedback to the team.https://summit.debconf.org/debconf14/meeting/42/debian-ruby-bof/Fri, 29 Aug 2014 10:00:00 GMThttps://summit.debconf.org/debconf14/meeting/48/openstack-update-packaging-experience-sharing/In this talk, I'm planning to first give an update on what has been going on in OpenStack over the past year. Then, as packaging OpenStack means packaging a LOT of Python dependencies, I would like to share the packaging experience related to it: tricks that I've been doing, issues that I've faced and that I had to solve, etc.https://summit.debconf.org/debconf14/meeting/48/openstack-update-packaging-experience-sharing/Fri, 29 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/16/outsourcing-your-webapp-maintenance-to-debian/Today's web applications often have a lot of external dependencies. Start off with a basic framework, sprinkle a couple of handy modules and finish with a generous serving of JavaScript front-end libraries. What you end up is a gigantic mess of code from different sources which follow very different release schedules and policies. Language-specific package managers can automate much of the dependency resolution and package installation, but you're on your own in terms of integration and quality assurance. Also, the minute you start distributing someone else's code with your project, you become responsible for the security of that third-party code. We moved away from statically-linked C/C++ programs a long time ago and now (mostly) live in a nicely-packaged shared library world. Can we leverage the power of Debian (i.e. the great work of the package maintainers and security team) to similarly reduce the burden of those who end up having to maintain our webapps? This talk will examine the decision that the Libravatar project made to outsource much of its maintenance burden to Debian by using system packages for almost everything.https://summit.debconf.org/debconf14/meeting/16/outsourcing-your-webapp-maintenance-to-debian/Fri, 29 Aug 2014 14:30:00 GMThttps://summit.debconf.org/debconf14/meeting/29/embedded-arm-development-in-debian/How we got a toolchain for Jessie! This talk is an update of the status of Embedded ARM toolchain in Debian since last Debconf in Switzerland, when Keith Packard talked about the support and work needed on Cortex-M0 and M3 chips. Today we can say that Jessie will be released with a complete and an amazing ARM toolchain for Embedded Systems, providing support for all cortex-A*/R*/M* processors. When you acquire a beautiful embedded board, you realize that at some point you will be needing to download tons of proprietary and distributed binary-only software, or build a lot of projects from scratch just to try blinking a LED. Now, you have the alternative of using the ARM Bare Metal Toolchain provided by Debian altogether the favourite flavoured IDE of your choice. On the same page, there are some important areas of improvements we need to work on, one of them being improving documentation, helping to reduce a steepy learning curve.https://summit.debconf.org/debconf14/meeting/29/embedded-arm-development-in-debian/Fri, 29 Aug 2014 16:00:00 GMThttps://summit.debconf.org/debconf14/meeting/37/dc16-proposals/Canada, Norway, Brazil, Finland, Mexico, Scotland, Argentina, Spain, USA, Bosnia, Nicaragua, Switzerland, USA, Germany... Where do you want to go next?https://summit.debconf.org/debconf14/meeting/37/dc16-proposals/Fri, 29 Aug 2014 19:00:00 GMThttps://summit.debconf.org/debconf14/meeting/28/debian-contributors-one-year-later/Last Debconf Debian Contributors started to take form, and now a year has passed and we have a working site. I'm going to talk about what happened, where we are now, and where we can go with it.https://summit.debconf.org/debconf14/meeting/28/debian-contributors-one-year-later/Sat, 30 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/96/hacking-on-apt-for-fun-and-profit/A overview of APTs recent past, present and future(s). https://summit.debconf.org/debconf14/meeting/96/hacking-on-apt-for-fun-and-profit/Fri, 29 Aug 2014 16:00:00 GMThttps://summit.debconf.org/debconf14/meeting/23/debconf15-in-heidelberg/In 2015, DebConf takes place in Heidelberg, Germany. We'll offer a glimpse of the venue and our plans.https://summit.debconf.org/debconf14/meeting/23/debconf15-in-heidelberg/Sat, 30 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/77/introduction-to-pybuild-and-python-packaging/* will pybuild replace dh_python and why not? * how to customize build/install/test targets? * tips and tricks useful while packaging Python libraries and applicationshttps://summit.debconf.org/debconf14/meeting/77/introduction-to-pybuild-and-python-packaging/Sat, 30 Aug 2014 13:30:00 GMThttps://summit.debconf.org/debconf14/meeting/118/steamos-and-debian/SteamOS is one of the latest Debian derivatives and is set to be hugely popular. This talk will explore some of the decisions and implementation details behind the creation of (what will hopefully be!) the biggest linux gaming platform ever. Presented by Neil McGovern (DD, Collabora) and John Vert (Valve)https://summit.debconf.org/debconf14/meeting/118/steamos-and-debian/Sat, 30 Aug 2014 16:00:00 GMThttps://summit.debconf.org/debconf14/meeting/75/dgit-treat-the-archive-as-a-git-remote/dgit lets you clone, commit, and push to the Debian archive. Other Developers don't even need to know you're using git, but if they use dgit you share history with them. The talk will cover the basic design choices, include a demo, and go on to the current status and future plans. http://www.chiark.greenend.org.uk/~ijackson/2014/debconf-dgit-talk/slides.pdf and .../talk.txthttps://summit.debconf.org/debconf14/meeting/75/dgit-treat-the-archive-as-a-git-remote/Sat, 30 Aug 2014 19:00:00 GMThttps://summit.debconf.org/debconf14/meeting/67/hopenpgp-an-implementation-of-rfc-4880-in-haskell/An overview of hOpenPGP and openpgp-asciiarmor, an OpenPGP implementation in Haskell; hopenpgp-tools, tools based on the hOpenPGP library; and their relevance to Debian.https://summit.debconf.org/debconf14/meeting/67/hopenpgp-an-implementation-of-rfc-4880-in-haskell/Sat, 30 Aug 2014 14:30:00 GMThttps://summit.debconf.org/debconf14/meeting/9/seeing-debian-through-a-functional-lens/Using Nix's functional package management as inspiration, let's look at Debian from a functional programming perspective. Including: The rise (and limits) of declarative configuration in Debian (triggers, control files, tendencies in debian/rules), schroot and docker, reproducible builds.https://summit.debconf.org/debconf14/meeting/9/seeing-debian-through-a-functional-lens/Sat, 30 Aug 2014 16:00:00 GMThttps://summit.debconf.org/debconf14/meeting/82/debian-derivatives-discussion/Debian is the basis for a number of other software distributions. This BoF provides a space for representatives from derivatives and Debian to share experiences, find out what is is being worked on and discuss problems, solutions and tools. We will begin with a quick round of introductions and then begin open discussion. https://wiki.debian.org/Derivativeshttps://summit.debconf.org/debconf14/meeting/82/debian-derivatives-discussion/Sat, 30 Aug 2014 20:00:00 GMThttps://summit.debconf.org/debconf14/meeting/31/jessie-bits-from-the-release-team/Update on the jessie release, changes in release processes, ...https://summit.debconf.org/debconf14/meeting/31/jessie-bits-from-the-release-team/Sun, 31 Aug 2014 14:30:00 GMThttps://summit.debconf.org/debconf14/meeting/38/closing-ceremony/All good things must come to an end.https://summit.debconf.org/debconf14/meeting/38/closing-ceremony/Sun, 31 Aug 2014 15:30:00 GMT