previous day < Friday: as grid - as list > next day

08:00 - 09:30 PDT
Meal
10:00 - 10:45 PDT
Speaker: Aurelien Jarno
General discussion about the MIPS port, including the future mips64 and mips64el ports.

Tracks:
  • Ports
Room 327
Speaker: Ian Jackson
I want to cross-build half of the NetBSD kernel for Xen, build qemu against it, and put the result in an amd64 .deb. Help me do this in the least annoying way. Event structure: I'll spend the first quarter or so of the time sketching out what I'm trying to do and why. Then we can move onto the difficult question of how. I have a few slides, here: http://www.chiark.greenend.org.uk/~ijackson/2014/debconf-builds-bof/slides.pdf --- Notes from the session are here: http://www.chiark.greenend.org.uk/~ijackson/2014/debconf-builds-bof/gobby.txt

Tracks:
  • Packaging and tools
Room 328
Speaker: Antonio Terceiro
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.

Tracks:
  • Debian Teams
Room 329
11:00 - 11:45 PDT
Speaker: Enrico Zini
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.

Tracks:
  • Packaging and tools
Room 327
Speaker: Breno Leitao
This is going to be a presentation/discussiong abound adding the new ppc64el architecture in the Debian operating System. This discussion is going track the ppc64el progress and the missing parts. This is a draft of the agenda that I would like to follow: The Power8 little endian architecture (together with PowerKVM) The OpenPower Foundation PPC64 Little Endian Toolchain and new ABI Cross-compilation phase rootfs Buildd

Tracks:
  • Ports
Room 329
12:00 - 13:30 PDT
Meal
13:30 - 14:15 PDT
Speaker: Steve McIntyre
General discussion on how ARM is going: the existing armel and armhf ports, and the exciting new world of arm64.

Tracks:
  • Ports
Room 327
Speaker: Julien Cristau
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.

Tracks:
  • Cloud
Room 328
Speaker: Thomas Goirand
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.

Tracks:
  • Packaging and tools
Room 329
14:30 - 15:15 PDT
Speaker: Wookey
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.

Tracks:
  • Ports
Room 327
Speaker: Jimmy Kaplowitz
Google's Cloud Platform, especially Compute Engine, has prominently supported Debian as a guest OS for over a year now. Google wants to give its Debian users an even better experience than they have today, as well as give the Debian community more direct involvement in preparing the version of Debian we promote to our customers. This session will start with an overview of where we are today, how we got here, and where we know we need to go. Then we'll open it up for a discussion, hopefully leading to follow-up collaboration with attendees for the rest of the conference and beyond.

Tracks:
  • Cloud
Room 328
Speaker: Francois Marier
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.

Tracks:
  • Packaging and tools
Room 329
15:20 - 15:45 PDT
Group photo -- Aigars Mahinovs ( Social activities )
Speaker: Aigars Mahinovs
DC14: Pics or it didn't happen.

Tracks:
  • Social activities
Elsewhere
16:00 - 16:45 PDT
Speaker: Michael Vogt
A overview of APTs recent past, present and future(s).

Tracks:
  • Packaging and tools
Room 327
Speaker: Nattie Mayer-Hutchings
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.)

Tracks:
  • Debian project
Room 328
Speaker: Agustin Henze
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.

Tracks:
  • Ports
Room 329
17:00 - 18:30 PDT
Meal
19:00 - 19:45 PDT
Speaker: Paul Tagliamonte
Bits from the Docker Maintainer. Brief overview of Docker, it's pros, cons, best practices and loads of opinions.

Tracks:
  • Cloud
Room 327
DC16 proposals -- Gunnar Wolf ( DebConf Organization )
Speaker: Gunnar Wolf
Canada, Norway, Brazil, Finland, Mexico, Scotland, Argentina, Spain, USA, Bosnia, Nicaragua, Switzerland, USA, Germany... Where do you want to go next?

Tracks:
  • DebConf Organization
Room 329
20:00 - 20:45 PDT [PLENARY]
Speakers: Daniel Kahn Gillmor, Ana Guerrero López
Linus will come by DebConf to do a small Q&A session with us.

Tracks:
  • Ad-hoc sessions
Plenary Room
21:00 - 21:45 PDT
< Friday >