DebConf9Cáceres, Extremadura2009-07-152009-07-31170.503:0000:1516:0003:00Upper talkroomuse Perl;Annual meeting of the Debian Perl GroupbofenThe 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/OpenTasksGunnar Wolf
Open tasks for the Debian Perl group
18:0003:00Upper talkroomD-I Work Sessions (I)workshopLuk Claes16:0003:00Lower talkroomJTAG for beginnerslectureenDebugging bootloaders and kernels with JTAG is demonstrated with an ARM embedded system.Unlike application software, which can be debugged by attaching to the process, kernels and bootloaders have no software layer above them that would provide debugging facilities, so debugging them requires hardware support and special techniques.
Contents:
- JTAG basics
- OpenOCD
- Attaching to a target
- Techniques for debuggingSimon Richter11:0003:00Upper talkroomGetting Goals DoneHow to work together with the others to accomplish goals?bofenSometimes there are bright and/or (not so) clever ideas, but either way they are far away from being easy to accomplish, so the question is: how can we work together with the others to accomplish those goals? Most, if not all, of us are volunteers and what motivates some doesn't necessarily motivate the others, what can we do to succeed then?It may be impossible to find a magic solution that works perfectly, the title might be a joke and the results may not be compared to GTD, but that doesn't mean we should not try to find some techniques to help accomplishing goals.
The release team has said that not every goal is a release goal (which is fine, but tricky), so how can we use techniques such as 0-day NMUs to circumvent those maintainers who don't really care about some goals as they see them irrelevant?
Bring lots of ideas, an open mind, and your experience (little, like mine, or lots of it! we want opinions).
Raphael Geissert18:0003:00Upper talkroomD-I Work Sessions (II)Luk Claes10:0003:00Upper talkroomComponent-based softwareunderstanding GNOME, Mozilla and WindowslectureenA short run-down of component systems is given, explaining the basic concepts and some of the details necessary to use them. Both CORBA and (XP)COM are covered.Complex software is often designed as individual components working together, with each component being implemented separate from the others, which is in stark contrast to the programming models usually found in the Unix world. This talk gives a quick insight into this design approach and its strengths and weaknesses, and should help contributors to GNOME and Mozilla to understand the codebase better.
Topics:
- Interface driven design
- CORBA and COM
- Object ownership
- Component isolation
- The memory allocation problem
- The Initial Object Reference problem
- UI components
- Scripting components
- ExamplesSimon Richter17:0001:00Upper talkroomVideoteam volunteer startup meetingAudio Video DiscoenHolger Levsen18:0003:00Upper talkroomD-I Work Sessions (III)workshopenLuk Claes18:0003:00Lower talkroomlintian workshopworkshopenSort out some checks requests, help new contributors (so don't be scared and attend!), etcRaphael Geissert09:0001:00Upper talkroomJunta de Extremadura (titulo por determinar)Rafael Martín Espadalecturees10:0001:00Upper talkroomHP and DebianlectureenBdale Garbee
presentation file
11:0001:00Upper talkroomTelefonicaEzWeb: Open Source Mashup PlatformSebastian Ortega Torreslecture12:0001:00Upper talkroomAdaptación de Debian a un entorno corporativoDiego Martínez Castañeda, COMPAREXlectureesVentajas de Debian y software libre en la integración con entornos empresariales.13:0001:00Upper talkroomExtrayendole el jugo a Debian para dar vitaminas a la Educacióngnu/LinEx y Debian en los centros educativos extremeñoslectureesPasado, presente y futuro del uso de Debian en el sistema educativo público extremeño.
Después de un breve resumen de lo que se empezó hace casi siete años, se contará los avances, problemas y soluciones
habidos durante el último curso.
También se hablará de los planes existentes para la incorporación de ordenadores portátiles en las aulas: pilotos ya hechos en Extremadura y su integración con el plan del gobierno nacional para el próximo curso.
Durante toda la charla se comentará el papel que Debian ha jugado para conseguir los objetivos propuestos, todo lo que hemos obtenido: software, configuraciones, ayuda, amigos, excelentes técnicos, etc. y lo que se ha aportado a Debian a lo largo del camino.José L. Redrejo17:3000:30Upper talkroomwtWelcome TalkDebConf9 introductory sessionotherenWelcome sessionWelcome sessionJoerg JaspertHolger LevsenJose Antonio Recio CuestaCésar Gómez Martín18:0001:00Upper talkroomDebian por dentroesAdeodato Simó19:0001:00Upper talkroom¿Por qué contribuir a Debian?Experiencias personalespodiumesLuciano BelloEnrico ZiniSteve Langasek
diapositivas de Steve
diapositivas de Enrico
diapositivas de Luciano
20:0001:00Upper talkroomLicencias de Software Libre en DebianlectureesMiriam Ruiz
Slides usadas en la charla
22:3001:00Upper talkroomGPG keysigning party information/discussionGPG keysigning party information/discussionotherenAníbal Monsalve SalazarDon ArmstrongAndrew McMillan
Keysigning @ DebConf9
10:0001:00Lower talkroomFLOSSInclude Project Presentation (FUNDECYT)podiumesMarta QuintanillaJose Antonio Recio Cuesta
FLOSSInclude
http://
11:0001:00Lower talkroomContando DebianCual es el tamaño de Lenny?lectureesFrancisco Rivas12:0001:00Lower talkroomEntendiendo Debian Así que ya eres un nuevo usuario de Debian... ¿Qué viene ahora?lectureesSo, you're new debian user, what is the next step? This talk is about Debian tools, terms, philosophys, policys, statistic, anecdotes and funny situations and we're triying to get the "debian world" to new users for make the first impression more confortable.
Así que ya eres un nuevo usuario de Debian.. ¿Qué viene ahora? Esta charla es sobre herramientas, términos, filosofía, políticas, estadísticas, anécdotas y situaciones divertidas en el proyecto Debian y con ella intentamos acerca el "mundo de Debian" a los nuevos usuarios para que esa primera impresión sea más agradable.Esta charla es un compendio de experiencias propias y de recopilación de múltiples fuentes de información del proyecto Debian para que los miembros que se vayan incorporando al proyecto puedan tener una visión más general del proyecto.
Se busca, principalmente, mostrar el lado humano de los que están involucrados en este proyecto, por otro, mostrar el arsenal de herramientas disponibles (herramientas de administración (aptitude), infraestructura web (wiki, bugs, documentación), herramientas para la calidad y buenas prácticas (pbuilder, etc).
Está dirigida a usuarios nuevos y no pretende ser un tutorial sobre las herramientas que señalan.Hector Colina13:0001:00Lower talkroomExtremadurathomeDaniel Lombraña González, IDENTIClecture18:0001:00Lower talkroomFree Beer, Power and KnowledgeThe next bottle of beerlectureenWhat is Free Software? What is a distribution of Free Software? Why do I have to pay something if people tell me it is free? What exactly do I get for my money? How can I find the things I really need in the jungle of Free Software?
These questions might be asked by people who heard something in the news about Linux, Firebird etc. but do not have a concept about the ideas behind it. The talk tries to give reasonable answers while beeing careful with the usual polemic about this topic.Andreas Tille
More information
19:0001:00Lower talkroomLiMux in Munich3 years experience using free softwareenMunich's LiMux project increases the use of free software within the 14,000 PCs of the administration. Challenges are the integration of the linux client, the availability of business applications and the migration to OpenOffice.orgMunich's LiMux project increases the use of free software within the 14,000 PCs of the administration. Challenges are the integration of the linux client, the availability of business applications and the migration to OpenOffice.org
The migration to OpenOffice.org is far advanced and the number of workstations using Debian GNU/Linux as operating system and mainly free software for daily business is rapidly growing.
The talk is intended to LiMux interested people with and without any technical prior knowledge. It gives a short overview about the project's background, points out the current numbers and presents the technical solutions (Debian based client, WollMux as office tool).Florian Schießl
official website (DE)
inofficial devblog (EN)
Wikipedia (DE)
Wikipedia (EN)
Case study at OSOR.eu
10:0001:00Upper talkroomGoogle Summer of Code 2009 at Debianpresentation of the projects and their statuspodiumenThis event will gather the admins, mentors and students of the 2009 Google Summer of Code at Debian to present our organization work, the students, their projects and how they are doing.At the time of Debconf9, our students should be way into their projects.
The Debian organization of the 2009 run of the Summer of Code will be presented and discussed, gathering feedback, especially in regard of the relation between the projects and the rest of the community.
This event will be an opportunity for mentor and student pairs to present the projects they have been working on and update about their progress, and for the Debian community to give face to face feedback and help.Obey Arthur Liu
Wiki page
Google Docs Presentation
11:0001:00Upper talkroomCounting DebianHow large is Lenny?lectureenFrancisco Rivas12:0001:00Upper talkroomTeams in Debian: Finding and integrating new membersTrying to find ideas to make the first phase of group membership easierbofenDuring DebConf8 two BOFs took place around the topic of team-maintaining
packages. One issue defined as a common challenge for all teams was the
question of how to find and integrate new members. The discussion showed
that none of the present teams was using a structured approach for
recruitment and induction at that time. [0]
This BOF is intended to pick up the discussion of finding and integrating
new members into teams where it stopped in Mar del Plata. It will focus on
collecting models of good practice and developing ideas for improvement.
[0]
http://lists.debian.org/debian-qa/2009/02/msg00006.html
a) Background
The number of teams in Debian [1] is rising, and "join an existing team" is
often an advice given to potential new contributors. In practice it's often
not so easy, neither for "newbies" nor for "old-timers", to get in touch
with each other and take the first steps together until someone becomes a
"regular" in some team.
b) Potential questions
- How can teams find new contributors -- and vice versa?
- What do we expect from potential new group members?
- What do potential new members expect from teams?
- Which approaches and methods were successful in the past? What were the
reasons for failures?
c) Methods
Should the proposal for the BOF be accepted, I intend to kick off the
session with a very short introduction into the topic, and then try to
facilitate the common discussion.
Ideally the session will conclude with a summary of "best practices,"
ideas for improvement, and maybe plans for the future ...
[1]
http://wiki.debian.org/Teams
Gregor Herrmann13:0001:00Upper talkroompam-auth-update: manhandling debconf for fun and profitlectureenthis talk will encompass:
- a discussion of how maintainers of PAM module packages should integrate with the new system
- a peek under the hood, at how pam-auth-update uses debconf in creative ways to provide a consistent user experience
- discussion: should we be doing better at innovating when it comes to this kind of distro integration?Steve Langasek
slides
18:0001:00Upper talkroomWhere does Debian fit in?DPL keynoteenSteve McIntyre19:0001:00Upper talkroomMultiarch round tableMultiarch quick review and discussionbofenMultiarch design and implementation discussionMultiarch is an idea that has been arround many time by now.
There is some people interested on bringing up all this setup. I propose to meet all together and have a talk. Some of the discussion points could be:
* Multiarch design review
* Multiarch addon proposal: cross building support
* Implementation challenge
The final goal is to have a co-installable and co-buildable system using Debian sources.Hector OronSteve Langasek
Multiarch
Ubuntu Multiarch specification for karmic
20:0001:00Upper talkroomQuality Assurance BOFbofThe Debian Quality Assurance team does work in a large number of areas. This BOF will be an opportunity to discuss the current state, and possible future changes, in:
- Maintenance of orphaned packages
- Developer tools such as the PTS, DDPO and UDD
- Tracking of maintainers Missing In Action (MIA)
- Mass bug filings (rebuilds, piuparts, etc)
- Organization of team maintenance
- etcLucas Nussbaum10:0001:00Lower talkroomKernel BoFbofenBoF for kernel team and developers working closely with the kernel.BoF for kernel team and developers working closely with the kernel.Ben Hutchings11:0001:00Lower talkroomSPI BOFMeet the SPI BoardbofenAn opportunity to meet board members of Software in the Public Interest who are present at Debconf, and informally discuss the relationship between Debian and SPI, and the future of SPI.An opportunity to meet board members of Software in the Public Interest who are present at Debconf, and informally discuss the relationship between Debian and SPI, and the future of SPI.Michael SchultheissJoerg JaspertJimmy KaplowitzBdale Garbee
Software in the Public Interest, Inc.
12:0001:00Lower talkroomDebian Science round tableBringing together DDs caring for scientific softwarepodiumenThe Debian Science Blend has undergone a new offspring since 2008 and is attracting more and more developers. It has shown that some questions are raised over and over and there seems to be a need to define some strategy for the project to serve our users best. This should be done in this panel discussion.Andreas TilleMichael Banck13:0001:00Lower talkroomNon-English IRC Supportand how #debian should use itbofenThis talk will briefly cover the current status of Debian end-user IRC support in #debian and how it has improved over time. The main part of the talk will be about non-#debian IRC support. Users who do not speak English usually get directed towards their specific language channel. The problem with this (especially for less popular languages) is that we do not know whether they are getting help there or whether that channel has similar guidelines like #debian. Points of contact for a particular language with a well-known background in the Debian community should be decided upon to act as a liaison between the local channel and the rest of the Debian end-user support. This could be expanded for other communities like mailing lists. Hopefully, a discussion on how to best achieve the above will ensue during and after the talk.In former years, complaints about the #debian atmosphere in general and the attitude of some of its regulars in particular were quite frequent. Over the last few years, the current #debian channel operators and regulars have mostly succeeded in providing a more welcoming, yet still highly effective end-user support for Debian users in #debian.
However, with the success of i18n in Debian and Free Software in general, more and more users who do not speak English fluently (if at all) request support in #debian. Those people get pointed to language-specific channels via the channel-bot factoid database. This works pretty well to keep the main #debian channel from non-English chatter and noise, but it is often unclear to the #debian channel operators and regulars whether those users are actually helped in the channels they are sent to. Feedback on how well those channels work is difficult to obtain because the users directed there usually do not return back to #debian. Sometimes, more than one end-user support channel for a particular language exist, they are split on several networks, or change names without the #debian regulars noticing. Some channels for less popular languages are also very small and low-traffic. Moreover, there have been complaints about abusive channel operators or regulars in those language-specific channels.
The Debian project might profit from general guidelines on what are acceptable and useful measures for end-user support among all of the support channels. Points of contact for a particular language with a well-known background in the Debian community should be decided upon to act as a liaison between the local channel and the Debian end-user support organizers. This could be expanded for other communities like mailing lists as well. Further discussion is needed and solicited to flesh out the above proposal.Michael Banck19:0001:00Lower talkroomTrust is good, control is betterThe road to world domination is paved by policylectureenpiuparts has been helping Debian become better since 2005. piuparts.debian.org has been testing 50000 binary packages since March 2009. How can your packages benefit from piuparts? How can you run it yourself? How can you benefit from what piuparts.debian.org does? This talk is an introduction to piuparts, taking the people from basic usage to experts in using piuparts in one short hour.Holger LevsenLars Wirzenius
http://piuparts.debian.org
http://
20:0001:00Lower talkroomI18n sessions 1/4bofenFirst i18n BOFChristian Perrier23:0003:00Garden / PatioCheese and wine partyThe traditional DebConf cheese tasting eventotherenThe Cheese and Wine party is now a tradition in Debconfs. Debconf 9 will not fail that tradition and the goal is of course having the best and smelliest cheese party ever.No Debconf without Cheese and Wine party, that's at least true
since Debconf 5 in Helsinki.
So, DC9 will not be an exception and we will again have a C&W party.
The event is, from what I see in Penta, officially scheduled for
Saturday July 25th, 21:30 local time.
Of course, that will, as usual, require participation by attendees,
particularly the French gang, to bring enough material for it.
The principle is easy: attendees do their best to bring *good* cheese
and|or *good* wine or liquors from their own place and we all share
this in the best suitable place we can find for this.
If you can't bring anything....you're still highly welcome. We need
many people to come and be sure that nothing is left at the end.
Don't expect something very organized: everybody is free to come and
join. Don't feel like you *have* to bring something to participate: we
all know this is not always easy when travelling, sometimes for a long
time. Cheese is still considered as dangerous material in many places
and as a military weapon in some others..:-)
The main rationale should be, as usual in Debian: focus on quality. If
something from your place|country|region seems worth being discovered
by Debconf attendees, you can certainly bring it and share. The last
C&W have already proven that Debconf attendees enjoy good food and
drinks.
Cheese should be the main topic of the even, along with wine, of
course. This is the spirit of the event and it should remain as is.
Spain is a very cheese-friendly country...so let's take advantage of this..:-)
One should also remember that "cheese party" generally means "cheese
AND WINE party", which generally extends to "cheese and wine and
anything containing ethanol as long as this is good stuff" party.
Christian Perrier10:0001:00BOF room - no videoLicence compatibilitybofI would like to participate with a presentation titled "License
compatibility". I think that this is a major issue to consider in the open
source software legal practice. Different open source licenses create
different legal frameworks for the production of software in a collective
and distributed manner.I will examinate the legal interoperability of main free software licenses
because software developers are confronted frequently with problems related
to incompatibility of software licenses, I also want to talk about the new
conflictual framework of patents versus intellectual property and how a free
software license interact whith patents, the limits to the virus effects of
copyleft and the closed relation of free licenses and open standards.
Undestanding the principles of license compatibility, in view of the
proliferation of licenses that are nowadays considered to fall under the
definition of "open source", and understanding the copyleft clauses address
one of the more important legal challenges of the future of the open source
software.
Jose Lancho11:0001:00BOF room - no videoOpenstreetmap - What, Why, and HowlectureenAn introduction to the Openstreetmap project.Blars Blarson
slides
openstreetmap
12:0001:00BOF room - no videoOpenstreetmap mapping partyotherAn Openstreetmap mapping party is where people get together and map an area. Bring a GPS if you have one.Blars Blarson
http://www.openstreetmap.org
13:0001:00BOF room - no videoMer: Maemo ReconstructedMaemo as a generic open platform for mobile devicesbofenPresentation on Mer, a community edition of Maemo, which has as one of its goals to attempt to make Maemo a generic mobile platform. The discussion will be focused upon Mer on top of Debian in mobile devices and where the Maemo platform can help providing quality user interfaces for Debian-based operating systems on mobile devices. Demonstration of Mer on Neo Freerunner, Nokia N8x0, SmartQ5, etc will also be shown.
Mer (http://wiki.maemo.org/Mer) is a maemo.org project that aims to reconstruct the Maemo platform based on principles such as open development, developer-friendliness, hackability and multiplatform support. While originating on the Nokia Internet Tablets, Mer now supports many diverse mobile architectures, including Freerunner.
The Mer project sees modern mobile devices as the powerful, economical, power-efficient handheld computers they are and brings these devices into closer alignment in terms of API. Mer provides packages that implements a Maemo 5.0 API on top of the Debian and Ubuntu distributions. It is as well an attempt to limit application porting to a mobile OS to be a matter of adapting the application to the mobile use case.Carsten Valdemar Munk
Website for Mer project.
http://
19:0002:00BOF room - no videoOpenmoko Buzz Fix PartyRepairing buzz hardware bug live and for free (free as beer)otherenWe will fix the Neo for you :),
At DebConf9 and with Openmoko Inc support we will celebrate a "Fix it" party and we will fix you Neo live there ,
Armed with a good soldering station a good trained technician for this specific fix after more than 60 units and two previous Fix Parties , will be there at your disposal to fix your neo live right there, meanwhile you wait for the Neo to be fixed you can take a beer with us and the rest of Neo owners out there
If for whatever reason(lack of time, too much beer...) we not can fix it then, we can pickup it, repair it at lab, and send you back the Neo wherever you want. Shipping costs will be comunicated if this situation happens
You have to have to "buy"(is free so no cost) one Fix it Party ticket from the special Debconf shop Tuxbrain, at http://www.tuxbrain.com/debconf , has setup for the event with important discounts in Openmoko related products for Debconf/Debcamp assistants.Rafael Campos Las HerasDavid SamblasVictor Remolina
Web of the company
Especial discounts for Debconf
Web of the comunity openmoko in spain
Rafael Campos's Blog
10:0001:00Upper talkroomNews on Debian Autobuildinghow the buildd and wanna-build changed recentlyenI want to reflect about what changed in the Debian autobuilding infrastructure since last Debconf. A new team has been formed around this and we took up the challenge to improve it (and not only by just being available when anything goes wrong). I will thus first and foremost talk about changes visible and important to the developers but also lay out some details behind the scenes.Philipp Kern
buildd.debian.org
11:0001:00Upper talkroomUsing FOSSology for license analysis in DebianlectureenFOSSology is a set of free software tools to facilitate the study and analysis of Free and Open Source Software. Today FOSSology is best known for finding software licenses in source code. This talk will introduce FOSSology, show a demo of the tool, and then provide a discussion how FOSSology could be used to make license analysis within Debian easier.
Martin Michlmayr12:0001:00Upper talkroomnot your grandpa's debhelperlectureendebhelper v7, dh sequences, pluggable buildsystems -- over the past year debhelper has added lots of new stuff while staying true to its decades-plus roots. In my first ever talk about debhelper, I will cover this new stuff, how to use it, and how it can be better than cdbs.Joey Hess13:0001:00Upper talkroomDSA BoFApart from better sanitation and medicine and education and irrigation and public health and roads and a freshwater system and baths and public order, what has DSA ever done for us?bofenA BoF to discuss how DSA manage Debian infrastructure, with an emphasis on feedback from teams and users.DSA would like to hold a BoF that opens with a description of the current state of affairs, and then opens up to a more general discussion of how people use the Debian infrastructure, particularly teams.Martin Zobel-HelasStephen GranPeter Palfrader18:0001:00Upper talkroomUDD: Ultimate Debian DatabaselectureenUltimate Debian Database provides a central place to dig into Debian's information. It gathers data from a large number of sources into the same PostgreSQL database, allowing its users to easily access and combine all this data. This talk will provide an introduction to UDD, discuss its current status, and possible evolutions in the future.Lucas Nussbaum
Ultimate Debian Database
http://
19:0001:00Upper talkroomApplication of Ultimate Debian Database in Debian Pure BlendslectureenThe Debian Pure Blends effort has created web pages with different overviews about the packages which are in the scope of the Blend. On one hand this are so called tasks pages which assemble packages of so called tasks (fields of interest) on one page with certain metainformation. The descriptions are translated by using DDTP translations. Moreover there are bugs pages which enable a quick overview about problematic packages which are used by the Blend. The usage of UDD enables much simpler creation of these pages as well as offering new features. The talk should stress the interlinking between two different techniques inside the Debian universe.Andreas Tille
More information about this talk
20:0001:00Upper talkroomPoint releasesHow to update stable more efficiently?workshopenDoing and preparing point releases is still not streamlined. It would be good if website changes, draft announcements and preparation mails could get autogenerated. The current process of processing packages can probably also be improved as well as the documentation of broader changes or (solved) issues (like the ones for the installer).Luk Claes22:0002:00Upper talkroomvcs-pkg.orgWhat are our goals?bofenThis is a work session mainly for the people who have been active in vcs-pkg.org so far. There is a workgroup meeting on 30 Jul at 10:00 in the morning, and we would like to prepare so that we know what we'll do and can define our expectations. Anyone is welcome, of course, but don't expect too much explanations or detail.
See http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/2009-July/000633.htmlmartin f. krafft
http://vcs-pkg.org
11:0001:00Lower talkroomChanging the default system shelllectureenWhy, How, When, Side-effects, Counter-measures, and everything you wanted to know about the switch.Raphael GeissertLuk Claes13:0001:00Lower talkroomDDE, Debian Data ExportA smart front-end to the Debian Data HelllectureenDDE (Debian Data Export) is a simple interface to remotely access Debian information. It allows to explore and export data from a wide range of sources using a simple and flexible interface.
It is designed to be simple to query, and to back the implementation of nice things such as package name autocompletion on all input fields in Debian web pages, or to make more data easily available to Debian utilities and package managers.
On top of all that, it is a RESTful Web 2.0 middleware designed to enable AJAX mashups. What more can you ask? Come and have a look.Enrico Zini
Debian DDE instance
Debtags DDE interface
18:0001:00Lower talkroomimmunity: securing untrusted processesexecute your internet browser in a secure containerlectureenDebian ships several tools like sudo and some UI frondends to get more privileges for subprocesses but no tool to effectively reduce such privileges, yet. The immunity tool provides a secure container to lock down any application that processes untrusted data like web browsers, their plugins and handler apps, and other multimedia apps. A ready to install Debian package is available as a proof of concept and it should work on any Debian or Ubuntu version or any other Debian derivative.The talk will show the features of immunity, describe the implementation details and elaborate on future plans. The features of the version 0.4 are:
* switching to a shadow user with the name "immunity-$USER" and the home dir "/var/lib/immunity/$USER" to avoid any dangerous interprocess communication, debugging, signals, ...
* switching to group "immunity" that allows easy definition of filesystem ACLs and netfilter rules
* empty the set of supplementary groups
* works with a vanilla Linux kernel and does not need any external modules
* does not need packages not available in Debian or other major distros
* depends on features of the Linux kernel and won't work with other non Linux kernels
* does not need SELinux or any other complex security framework
* employs polyinstantiation of the filesystem
* narrows the filesystem in the container
o only parts of /etc, /dev, /usr, /var and other parts of the filesystem can be seen in the container
o no /boot, /home, /media, /mnt, /root, /sbin, /sys, ...
o /proc will be optional in the future; /proc/bus/usb has already been disabled
* disables all suid and sgid binaries
* reduces number of device files to /dev/null and /dev/snd/* (alsa)
* locks down all capabilities; they can't be regained from user space
* implemented in Python
* transfers X authorization to the shadow user; optional feature in the future
* employs the X11 security extension (no screenshotting, keyboard stealing, copying + pasting); will be made optional in the future
* porting to other Linux distributions should be easyTorsten Werner
immunity
slides
19:0001:00Lower talkroomUpgrade-advisor, analysing system upgradeHow to use it, how to write your own pluginpodiumenAn Introduction to "upgrade-advisor", a tool to analyse a system before and after a dist-upgrade. How to use it, How to contribute a plugin.This session will present upgrade-advisor, which runs in two modes :
* pre-upgrade - Test the system prior to the upgrade, then display some hints to ensure seamless upgrade.
* post-upgrade - Test the system after the upgrade, then display hints for emulating a freshly installed system.
During this session, we'll see how to use it, and how to contribute a plugin for you package and known bugs.Franklin Piat
Homepage
source repository
20:0001:00Lower talkroomI18n sessions 2/4bofenSecond i18n sessionChristian Perrier22:0001:00Lower talkroomPET BoFPET-devel get togetherbofenBoF to discuss future developments of PET.Martín Ferrari
Homepage
23:0001:00Lower talkroomuse Perl qw(again);Second BoF regarding the pkg-perl groupbofenAt our first BoF (2009-07-18) we agreed to hold a second one having all the team members in Cáceres - this is it.At our first BoF (2009-07-18) we agreed to hold a second one having all the team members in Cáceres - this is it.Gunnar Wolf23:0001:00Garden / PatioDebian Science BoF IIChristopher J. Walker10:0001:00BOF room - no videoLarge-scale Debian deployments BOFbofenDiscussion of what tools are of the most help in managing large numbers of related Debian systems. Configuration management, distributed shell tools, proxy setups, apt setups, mail setups, network-related tools, automated provisioning, change control, monitoring tools, general management tools, policy enforcement, security-related tools; it's all open for discussion.paul cannon11:0001:00BOF room - no videoOpenstreetmap BOFbofenBlars Blarson12:0001:00BOF room - no videoSpanish Debian Women BoFesMiriam Ruiz16:0001:00BOF room - no videoNM AM FD DAM BOFDiscussion about people involved in the NM processenPreferably restricted to AMs, FDs, DAMs and fresh NMs, as the main point is to discuss everyday experiences.
Preferably not recorded, so that real issues can be discussed without worrying about mentioning names.
Some topics for the BOF:
- prepare a lightning talk "Bits from the AMs, FDs, DAMs, NMs", with a list of
messages to send to the rest of DDs
- the templates: how do we use them? how do we change (delete, add, alter
questions) them? What questions usually feel unsatisfactory? What questions
feel most useful?
- what extra info do AMs usually provide to NMs? (For example, I do emeritus,
upgrading-checklist, maintainer scripts on debian women wiki)Enrico Zini18:0001:00BOF room - no videoSmaller, faster, cheaperPick all three in the new boot system?bofenThe debian boot system have receieved a lot of attention and work the last few years, and it is time to make the improvements available in the default installation. This talk is about the current state of affairs, and will present a plan for discussion.Petter ReinholdtsenLuk Claes
Ubuntu boot performance plans
LSBize Debian init.d scripts
Dependency based boot in Debian
19:0001:00BOF room - no videoScratchbox2 for crosscompiling debianlectureenSince the original plan of scratchbox2, it has evolved to become a tool that has been used as the basis of Maemo SDK+. But scratchbox 2.0 is much more flexible tool, make it feasible to use even outside the maemo scope. Using scratcbox2 to crosscompile regular Debian packages will be shown. The current state and future plans for scratchbox will be explored, and the build performance and success rate will be compared to other available solutions.Riku Voipio20:0001:00BOF room - no videouclibc and busyboxbofenIn certain environments, it is desirable to replace core parts of the distribution with alternatives. In this BoF session, a solution for a C library "switch" that allows a deriver (such as emdebian) to move the entire distribution to uClibc shall be discussed.The goal for this session is to prepare a list of implementation steps to build an uclibc based binary distribution, and, if possible, also a generic procedure for switching core components.Hector OronSimon Richter22:3001:00Upper talkroomFree travel instead of free beerNice photos of conference locations and surroundingsotherenAt home I'm always asked how I manage to do all this traveling - people just assume that I do this strange Linux stuff to be able to travel around the world. Well I guess it is the other way around: If people invite me to report about my Free Software work I must do something right. Having seen some interesting places enabled me to entertain the other hobby of mine: Taking photos of scenes I like. If time permits I use my analog (!) equipment and take some slides. The talk will be a sequence of random places I visited in connection with a Free Software event. So just expect images, images, images ...
It might be important to note that the images are *not* featuring any geeks - just nice landscape and architecture I happened to see on my travels regarding Free Software.Andreas Tille
My highres uploads to WikiMedia
Photos on my homepage
The images which will actually be shown
22:0003:00Lower talkroomDance BoFDancing Geeks — since 2005 at DebConfotherThe annual DebConf dance eventSlightly formal dance eveningSimon RichterW. Martin BorgertNattie Mayer-Hutchings10:0001:00Upper talkroomemdebian BoFbofenThe current state and future of emdebian is discussed.Topics include
- emdebian Grip and Crush
- cross building
- multiarch integration
- ...WookeyNeil WilliamsSimon Richter11:0001:00Upper talkroomQEMU for Debian DeveloperslectureenQEMU is a generic and open source machine emulator, that relies on dynamic binary translation to achieve a reasonable speed. It can run OSes and programs made for one machine (e.g. an ARM board) on a different machine (e.g. your own PC). It supports emulating several hardware platforms, among others AMD64, ARM, CRIS, i386, PowerPC, MIPS, and SH4, SPARC.
QEMU can be an helpful tool for Debian Developers, as it supports a good subset of official Debian architectures. Experience has shown it is able to reproduce most of the problems detected on real hardware, and thus can be used to debug architecture specific problems. Compared to the Debian Developer accessible machines, it allows the user to have full access to the "machine", either to install new packages or to debug low level packages such as the kernel. Compared to real hardware, it is usually slower (though for some architectures, it may be faster than easily available cheap hardware), but as it is only a piece of software it can be available anywhere. Imagine having access to half a dozen of architectures while working on a laptop in a plane!
Rough plan of the talk:
* Porting for Debian architectures: emulated versus real machines
* Emulating machines with QEMU
* A quick look at QEMU internals: CPU and devices emulation
* Status and future of QEMU for the different Debian architectures
* How to get it working on your computer
* Live demoAurelien Jarno12:0001:00Upper talkroomStable/Volatile/Backports ecosystemCreating a policy and proceduresbofenThe stable release (including point releases), volatile (including volatile-sloppy) and backports.org all have their goals and rules. Having a common policy which clarifies the interactions and borders of each of them will hopefully increase their use and cooperation. This BOF's goal is to get ideas about what should be included in the common policy and procedures.Luk Claes13:0001:00Upper talkroomHardware Report, Database and PopConProvide better hardware support to our users.lectureenHardware support implies two different points : Providing a Driver and configuring the system. We need a tool to collect information to improve both situation.
- When Debian/Stable is prepared, we need to improve the devices support by improving the drivers and packages (identify most used devices, devices without driver, etc..)
- Once Debian/Stable is released, the users needs some documentation : How a given system or device is supported by Debian/Stable and what extra configuration is needed to use it at it's best .The presentation will first list what DDs and users need, regarding hardware report. Then we'll review the situation in Lenny and list needed improvements. We'll then review existing tools, list pros and cons and explained what tool(s) we decided to use.
Current situation[1] : Have been done, what goals are achieved (by July).
We would probably have two packages : one for manual reports with comments, a second one that makes automated report (might be merged in popcon).
The website to view reports will probably be quite light by July.
Future improvements / Related works :
- Improve the web interface.
- Suggest software according to plugged hardware [P.Reinholdtsen]
- Consolidate figures with other Linux distributions to ask support from hardware vendors.
- Yours Ideas ?
-> Volunteers are welcome
-> The data are available, you can use it in your tools !Franklin Piat
Information extracted from Debian Kernel
(note how the list of devices for individual devices are extracted from kernel data)
linking to wiki pages, automatically
Project Homepage
18:0001:00Upper talkroomKeynote from the Release TeamenAdeodato Simó19:0001:00Upper talkroomVisualizing Debian package clusterslectureenThe set of Debian packages and their inter-package relationships is a very interesting graph. Unfortunately, it is too big to be visualized using naively graph visualization techniques: it would be about 25'000 package nodes with more than 400'000 inter-package relation edges. Nevertheless, that graph contains interesting hidden structures which grasp semantic inter-package relations. One of such relation is "strong dependency", i.e., the inability of a package to be installed without another companion package (note that such relationship is not the usual dependency relation, due to alternative dependencies and virtual packages).
In the context of the Mancoosi project, which has just finished is 1st year of existence, we have studied such relationship which has turned out to have interesting properties. On one hand it can help in establishing Quality Assurance metrics that pinpoint important packages on which a lot of other packages rely. On another hand it can be used to graph concisely inherent sub-structures of our package archive.
The talk will present the strong dependency notion and showcase fancy package graphs representing relevant cluster of packages which exist, sometime without us knowing that, in the Debian archive.Stefano Zacchiroli20:0001:00Upper talkroomDebConf 11 in your cityBring DebConf home!podiumenEvery year, the location for DebConf, the annual international Debian conference, is selected via a competitive bid process. Although we haven't got to DebConf9 yet, organising a conference isn't quick, so it's already time to start thinking about a location for DebConf11.
We encourage everyone to think about whether their city would make a good DebConf location, and, if it would, to start working on a proposal. (You don't have to be heavily involved in Debian before making a bid.) There will be a chance to present your proposed location at DebConf9 in Spain in July, but don't worry if you can't be there -- proposals will be accepted until the end of the year, and a final decision will be made early in 2010.
Interested? For more information see http://wiki.debconf.org/wiki/DebConf11
This panel will be your opportunity to show your bid to the rest of the DebConf attendees. Although participating in the panel is not strictly a precondition to take part on the bid decision process, it will help strongly show off the pros and cons of each possible venue. Jimmy KaplowitzAdnan HodzicJoerg Jaspert10:0001:00Lower talkroomdebian-devel listits proplems and how to maybe fix thembofenThis BoF will focus on the problems perceived with the debian-devel mailing list. Quite a number of Debian Developers have unsubscribed over the years for several reasons. This BoF will start with an overview of the current problems of the debian-devel list (soliciting the feedback of the participants as well) and then review some other FLOSS communities' approach to development lists (again, soliciting experience from the audience). Finally, the most of the part of the BoF shall be reserved for a guided discussion on what can be done to make debian-devel be again a better place and the central point of Debian development.Michael Banck11:0001:00Lower talkroomDebian FTP TeamotherenThe Debian FTP Team, a history and a description of the work and the people behind it.
A history about the FTP Team, a description of the workload and how people can help with it.
Joerg Jaspert
Ftpmaster page
12:0001:00Lower talkroomPacking the data in and getting it back outlectureenIn an era of cheap terabyte hard drives and gigabyte memories, it is still useful to pack data in order to be able to access and update it in a reasonable amount of time. This talk describes techniques I use. While the examples will be in Perl, the techniques will apply to many other languages.Blars Blarson
http://wiki.openstreetmap.org/wiki/Trapi
13:0001:00Lower talkroomDrowning in BugsGetting more people involved in bug triagingbofenDon Armstrong15:3001:00Lower talkroomDebian Java BoF part 2bofenMatthew Johnson19:0001:00Lower talkroomLibvirt: Hypervisor independent virtual machine managementlectureenLibvirt provides a stable C API to different virtualization solutions. Bindings for several languages (e.g. Python, Ocaml, Ruby) are available. This makes it easy to write reusable tools to manage virtual machines running under KVM, Xen, QEMU, OpenVZ and others.
Topics covered in this talk are:
* a quick run through the API including virtual machine creation, network and storage management and device enumeration
* readily available graphical and commandline tools such as virtinst and virt-manager
Guido Günther
Slides
15:3002:00Garden / PatioFree Software and Renewable EnergiesHow will we save the planet and the penguins?bofenWho is working in the field of renewable energies? Who is not, but just interested in the issue? In which projects related to free software and renewable energies are we involved? Which free software in the field of renewable energies exist? Which of this software is worth integrating in Debian? (How) can free software help in the adoption of renewable energies?W. Martin Borgert17:3000:30Garden / PatioGroup photootherAigars Mahinovs19:0001:00Garden / PatioI18n sessions 3/4bofenThird i18n sessionChristian Perrier21:0003:00outside the venuefdConference DinnerYearly DebConf not-so-formal dinnercontestenJose Antonio Recio CuestaCésar Gómez MartínJoerg Jaspert10:0001:00BOF room - no videoDebian Med BOFbofenAs every year I would like to invite all people interested in using Debian for tasks in health care to this open discussion about how we can have even better support for users in medical care. The event will not feature a longish talk just a short status report of mine and I hope for a living discussion - perhaps recruiting some new members for the crew.Andreas Tille11:0001:00BOF room - no videoDebian Java PackagingbofenDiscussion about changes to DJ policy, new packaging tools etcMatthew Johnson12:0001:00BOF room - no videoDistributing virtually boxed applications.vdi to .debbofenThe city of Munich has, for their LiMux client, developed a system to distribute virtual box images. The system images are shared by all users, immutable and updateable, and a small persistent virtual disk for the data is generated on the fly.
This BoF introduces this solution to anyone interested and invites you to join a discussion about the pros and cons of this approach.Robert JaehneJoachim Breitner
Source code
13:0001:00BOF room - no videoPublicity BoFbofenMeeting of all people interested in publicity work. Some of the topics to be discussed:
* making times.debian.net an official thing
* How to go on with the Debian Project News
** Getting them translated in time
* Sending out more announcements on what's going on in Debian to the official mailing list
* Whatever you come up with
Alexander "Tolimar" Reichle-Schmehl15:3001:00BOF room - no videoCacert Sign meetingbofenIf you wish to participate, you need to sign up at http://cacert.org *before* the event. You have to bring at least one piece of official identification to the event, two is better. You also need to fill out a bunch of the WoT forms (https://www.cacert.org/cap.php) -- three will do for a start.Hector Colina19:0001:00BOF room - no videoReproducible Research with R and SweaveMy life outside of DebianworkshopenMy glamorous day (and often, night) job is working on finding the
genes which cause Systemic Lupus Erythematosus (SLE) and in a separate
project, determining how arteriovenous malformations (AVM) in the
brain occur. Being able to reproduce the research that I've conducted
in the past is of critical importance, especially when dealing with
millions of datapoints in projects spread over years.
The utilization of tools such as R and Sweave, which enable the
production of publication-quality plots, tables, and even text in
articles that are tied to the raw data (using make), allows researches
such as myself to be able to replicate an analysis in the future, and
know precisely where we've found mistakes. In this talk, the basics of
R and Sweave will be presented, as well as a set of examples, ranging
from simple to relatively complex.
- Basics of R
- basic datatypes (lists, vectors, matrices)
- basic operations
- basic functions
- basic plotting
- devices
- time
- basic modeling
- Basics of Sweave
- embedding R in LaTeX
- tricks for keeping everything in sync
- Examples
- Regenerating the RC bug graph
- Examining expression differences in AVM
- Genes associated with SLE
Don Armstrong
Presentation
Examples
http://
20:0001:00BOF room - no videoxcontrollectureenA framework for extending control file syntax that allows compilation of policy-compliant control files from the extended variant is presented, and common use cases (embedded Debian, backports, toolchain packages) are discussed.The control file format is designed to be purely descriptive, with only minimal text substitution functions. While this is generally a good design approach, it significantly limits reuse of source packages across different distributions. There are three major use cases that are not handled at present:
- backports: after an ABI change, it is desirable to use a versioned build-dependency in sid to force buildds to use a version after the change, while a backport might want to use the old ABI in order to pull in less new packages
- embedded Debian: for cross-compilation, build dependencies need to be split between host and target side dependencies, which is not supported in Debian
- toolchain packages: these packages need to be compiled multiple times for different target architectures, while Debian requires all built binary packages to be listed in the control file.
The xcontrol framework handles these by allowing the format to be extended in a modular way, and allows developers to generate a policy compliant control file.Simon Richter10:0001:00Upper talkroomRFH maintaining big packagesDon't panic!bofenA few packages within Debian, that also happen to be big packages (Mozilla, OpenOffice.org...) suffer from a serious lack of hands, which is a problem for the maintainers, for Debian, and for the users. This BoF intends at presenting those packages, the typical maintenance tasks, what currently can't be done due to lack of hands, and to tentatively get some more people involved.Mike Hommey11:0001:00Upper talkroomDebian redesignIntroduction of the new lookotherenThe Debian Redesign -> testing ;)
Being one of the most common linux distributions worldwide, Debian never really made its qualities visible to the outside world. In order to change that, I have been working on a campaign as my diploma, but this is going to be just the beginning. To continue and realize the project, helping hands with graphical skills are welcome and needed. For now, just stay tuned for the nice surprise that is going to be shown at the Debconf.
Cheers,
Agnieszka (pixelgirl) Agnieszka Czajkowska12:0001:00Upper talkroomState of the BTSnew features, changes and tipslectureenThe bug tracking system is where all bugs that affect Debian are
filed. New features, including the affects, summary, and local debbugs
mirror will be presented and demonstrated. Some of the underlying
architectural changes to the codebase in debbugs to make it more
maintainable and deployable are also outlined. Finally, a set of tips
and tricks that can be used to make the BTS easier to use are
presented.
- New Features
- affects
- summary
- local debbugs mirror for offline work
- New SOAP
- full text search
- filtering bugs
- multi-distribution/arch status
- control changes at submit@ time
- Code Architecture Changes
- Modularization
- Control abstraction
- release to experimental
- Tips and Tricks
- Full text search
- Using the new options limits
- Usertags
- Getting users to triage their bugs
Don Armstrong
Debian BTS
http://
13:0001:00Upper talkroompiuparts workers unite!no pasaran!workshopena workshop to improve piuparts. should be held after the talk about piuparts.piuparts could perhaps be improved a bit. It is a bit slow, maybe, and the log file output requires some experience to be interpreted properly. It might do some more testing. Or some less testing, in some cases. It might test different scenarios. What do you think? Come tell us your gripes, wishes, and experiences with piuparts and help drive its development into a brighter, better future. Our 60 minute mission: to boldly test what no-one has tested before!Holger LevsenLars Wirzenius17:0001:00Upper talkroomAccessibility and DebianotherenMario LangSam Hartman
Debian Accessibility List
http://
18:0001:00Upper talkroomIntroducing DebConf10A preview of next year's DebConf in New York City, USAlectureenJimmy KaplowitzMichael Schultheiss
DebConf10 wiki page
DebConf10 IRC channel
DebConf10 mailing list
19:0001:00Upper talkroomUsing Debian for Hardware DesignbofenUsing Debian as a platform for electronic design and micro-controller programming is completely reasonable, as proven by the success of projects such as those at http://altusmetrum.org. This session is envisioned as an opportunity for sharing best practices and identifying improvements in Debian that would benefit hardware designers.Bdale Garbee20:0001:00Upper talkroomDebian on Network Storage Devices and Other DevicesHow to give a good install experience on devices that are not PCslectureenNetwork Storage Devices (NAS) are are gaining popularity and are available quite inexpensively. For most customers, they are basically just a hard drive that you connect to the network for file storage. In reality, these devices are complete, even if fairly low-end, computers - and Debian can be installed on some of them. Recently, there has also been a lot of interest in supporting other devices, such as netbooks and more embedded devices.
This talk will:
- Briefly introduce the NAS devices we currently support in Debian.
- Explain how Debian and the Debian installer support NAS devices in a very easy way.
- Share the experience gained working with users (i.e. what works, what doesn't).
- Look at future devices that would be nice to support and a number of other features that users have requested.
Do you need more than the abstract? If so, please email me and I'll add somethingMartin Michlmayr10:0001:00Lower talkroomDebian CD - what next?bofenSteve McIntyre11:0001:00Lower talkroomCrossbuilding on Debian for a derived distroHow does everyone make their Debian-based products?bofenToby Churchill Ltd is just one company basing their products on Debian and using cross-building to do it. The process has provided some challenges, including a transition from Familiar to Debian/Emdebian. I hope that others using the cross-tools and repository and build management tools would like to share experiences of how they build things, manage chroots and manage packages, to find out the better ways others are doing things, and what functionality really is missing. Managing cross-dependencies in a derived distribution set of build chroots is particularly difficult - discussion of how to fix this would be really useful.
TCL have based their product on Familiar for several years. They are in the process of moving to Debian, probably in the form of Emdebian Grip. They use dpkg-cross, apt-cross, schroot, and some home-grown scripts for the build process, keeping parallel native and cross-build environements functional. They use reprepro for package management of releases. They do not yet have something wanna-build-like to keep arches in sync, and really should do.
All this stuff is really cool but there are still issues. pbuilder manages native build dependencies really well, but there is no equivalent to manage cross-build dependencies. Well there are (emdebian-tools, apt-cross), but there are real issues as soon as those deps come from a local repository as well as from Debian. I'd like to discuss this and issues that others have found in order to determine how we should best support people trying to do this sort of thing.
Debian and Emdebian should be a marvellous base for cross-building specific apps on top of, and building systems out of, but there is a little more work needed to make this process reliable and manageable. I think a session to discuss the tools and mechanisms, comparing different people's approaches and issues would be really useful. Wookey12:0001:00Lower talkroomboot loadersShould lilo be removed?bofenIt was proposed to remove lilo, because of know problems with some configurations. But also grub (and grub2) cannot be used for some configuration. In this BoF I will explain the boot sequence, the status of the main boot loaders (lilo, grub, grub2, extlinux) for i386 and amd64 arch, the upstream plans, and the feature (focusing on the missing features) of the various boot loaders. Then the real discussion: lilo should be really removed? How to "move" configuration of one boot loader into an other, in most transparent way?
Giacomo Catenazzi
draft of the concept
13:0001:00Lower talkroomI18n sessions 4/4bofFourth i18n sessionChristian Perrier19:0001:00Lower talkroomDebian WikiLicense, Layout, and Lenny, what nextbofenBy this summer, the wiki should have a new license and layout (and CSS hopefully).
We will discuss what we want to to next... some ideas:
- How to implement i18n?
- Structure the wiki by kind of documents (Hardware support, proposals, knowledge base...)?
- Some ideas?Franklin Piat
The Debian Wiki
A draft for the next Debian Wiki
Statistics (esp. for relicensing the content)
22:0003:00Garden / PatioGPG keysigning partyotherenAníbal Monsalve SalazarAndrew McMillanChristian PerrierDon Armstrong
Keysigning @ DebConf9
11:0001:00BOF room - no videoikiwiki bofbofenikiwiki is a wiki compiler
Lots of us are here, so a bof seems like a good idea.Joey Hess12:0001:00BOF room - no videoDebian Games Team BoFNext steps for improving the gaming experience with DebianenSince its creation in January 2006, the Debian Games Team has been working on making Debian a better platform for a gaming experience. Having among its goals the collaboratively maintenance of games, to take advantage of the "Scale economy" benefits of maintaining similar games in a similar way, discussing problems and facts relative to game packaging and in general to improve the state of the games in Debian, and also to provide a way towards a larger involvement in Debian project for people by starting maintaining just one or few games, the opportunity for the members of the Team of meeting in person (and also for people that not belonging to the Team are anyway interested in helping and/or suggesting ideas) can be used to plan the next steps towards the total world domination, also in the gaming world.Miriam Ruiz
Debian Games Team
Packages overview for Debian Games Team
Debian Games Team in Alioth
16:0001:00BOF room - no videoSecurity BOFbofenThis is a discussion amongst the involved security people at Debconf. It is not a presentation, but rather a work group discussion. The focus will be around improving the existing security work in Debian.
This BOF will discuss things such as the following:
- more members for testing-security, how do we get new
people in? I think we have becoming pretty good in
maintaing the tracker recently but we really lack of
people who also fix bugs and write patches
- testing migration, almost no one cares about testing
migration at the moment which is one of the reasons we
don't have security support for testing at the moment
- testing security support, what needs to be done and how
can we solve the current problems.
- Debian as a CNA, while we can assign CVE ids the current
workflow is far from perfect, we have large delays
sometimes getting CVE ids and I think binding this to one
person is a rather bad idea.
- how to push for enabling more hardening compile options in
squeeze
- moving infrastructure to the new KVM instance (currently the
testing-security infrastructure is spread over three non
debian.org hosts)
- tracking of packages that got into testing/unstable from
proposed upgrades (and how to detect if the maintainer uploads
a vulnerable version again)
Micah Anderson17:0001:00BOF room - no videoTechnical Committee BOFstatus of open issues and plans for the futurebofenThis BOF will actually be in the shaded area just outside the main/front door of the facility, *not* in the so-called "BOF room".Bdale Garbee19:0001:00BOF room - no videoWacky IdeasbofenA forum for ideas that might not have been thought through entirely, and bored people looking for interesting projects.This BoF is aimed at people who
- think they may have a good idea, but are not entirely sure
- have a good idea, but not enough time
- are looking for new ideas
- feel the urge to stop some of the more interesting things from happening.Simon Richter20:0001:00BOF room - no videoBuildBot, Git, Tracin multiplatform continuous integrationworkshopen- Setting up Git shared repository and cloning it.
- Setting up Buildbot master instance and couple of slaves.
- Setting up Trac instance.
- Linking all stuff together.
- Resolving bugs by commits
- Resolving and reopening bugs by testing (TDD elements)
- Issuing tickets by testing (more TDD)
- Metrics: release(aka milestone, aka branch) and target platformDuring this workshop we will share ideas on how to set up a combined centralized/distributed ecosystem consisting of code and software build artefacts repositories, automated multiplatform software build and test system, and an issue tracker.
All folks involved or interested in (non-Debian) release/software_build/configuration management are welcome!Aleksey Nikolov10:0001:00Upper talkroomBuilding Debian from Debiandiscussion of the miscelany of tools that build debian installationsbofenMany tools all essentially install Debian, in some capacity, form or fashion.
This would be a discussion of the various tools in Debian used to install
Debian chroots, virtual servers, physical hardware, etc. and what common issues
and workarounds are currently needed, with an eye towards developing more
common code to share between projects.
people interested in the following tools or similar tools would be valuable to
the discussion:
debian-installer
debian-cd
simple-cdd
debian-live
xen-tools
util-vserver
pbuilder
simple-cdd
cdebootstrap
debootstrap
LTSP
FAI
Vagrant Cascadian11:0001:00Upper talkroomDebichemDebian chemistry subprojectbofenMeeting of all people interested in chemistry applications packaging within Debian. A status overview will be given, and then a couple of points discussed, including (i) whether and how to make debichem a full-blown pure blend, (iii) how to (better) interact and cooperate with other scientific packaging projects, most notably debian-science and pkg-scicomp, (iii) how to approach, interact and integrate with ubuntu-motu-science for chemistry packages, (iv) what SCM system to use in the future, (v) how to attract more developers.Michael Banck13:0001:00Upper talkroomTool adoption behaviour in the Debian projectResearch results revealedlectureenI've conducted a study among Debian contributors to identify the influences that shape our decisions when it comes to adopting or rejecting a new tool/technique into our workflows, or the workflows of teams to which we belong. In this talk, I present some of the findings and offer hints and suggestions for tool/technique supporters to increase the adoption rate in the project.I have been involved with the Debian Project for over a decade. At first, it
was only a hobby; then teaching Debian to others and planning Debian
deployments became my main source of income. Along the way, my fascination
with the project kept building up and I documented what made Debian so special
in my book The Debian System. I am an active and prominent contributor to
date.
The Debian Project is a highly successful project, run entirely by over 2'000
volunteers, and possibly the largest FLOSS project. It produces several
computer operating systems the most popular of which (Debian GNU/Linux)
provides over 20'000 software packages for eleven different hardware
architectures. Furthermore, the Debian System is the basis for around 150
derivative distributions, such as the popular Ubuntu distribution, and
large-scale, localised installations, including Guadalinex and Limux.
At 15 years of age, it is evident that some of the project's processes did not
scale to meet the tremendous growth we've seen over the years. Endeavours,
such as library transitions, currently require dozens of contributors to work
hand in hand, and often stall because of bottlenecks or lack of coordination.
Day-to-day tasks consist of tedious and thus error-prone tasks, which are
anything but integrated: keeping track of patches, triaging bugs, follow
policy changes, and work with upstream and derivatives, to name just a few…
Looking at the way these processes are currently handled, it seems strange
that contributors of a system as technically sound and universally applicable
as Debian are still doing by hand what the computer should be doing for them.
Tasks like the aforementioned could be streamlined and optimised to avoid
redundancy and points of failure due to brittle integration. For instance,
a bug report should only be marked as done as soon as but only when the patch
fixing the issue has been signed off and appears in the repository.
Some efforts in this direction already exist, but they are not being adopted
as readily as they should be. Because the Debian Project is made up entirely
of volunteers, noone can be told what to do or how to approach their tasks.
Instead, Debian contributors prefer to choose their own methods, based on
criteria which range from technical benefits to ideology, from pragmatism to
sheer stubbornness. In addition, once settled, a developer is often unwilling
to change his/her methods at a later point in time, or may only be able to do
so through considerable additional effort without the ability to assess
whether the effort will pay off.
For coordinators, integrators, or tool designers, no guidelines exist that
could help them frame these criteria and properly cater to everyone in the
target group. Instead, everyone is on their own when trying to spread a new
tool or technique. This impedes upon progress: some ideas may be good, but
never manage to convince more than a handful, who fail to communicate them to
the majority, because they do not understand others' decision behaviours. As
a result, those ideas cannot rise to become competitors with existing methods,
people will have no reason to change, and progress is halted.
A framework of the salient influences to adoption decisions among Debian
package maintainers helps everyone figure out what is necessary to enter
competing ideas into the field, and prevents stagnation due to
unsuccessful "marketing". With healthy competition, only the best tools and
techniques will emerge as winners. And because competition drives progress,
the project should be able to scale better as a result.
martin f. krafft
Research webpage
19:0001:00Upper talkroom11 Lightning TalksPresent an idea in 5 minuteslectureenSimon Richter20:0000:30Upper talkroomccClosing ceremonyGoodBye and see you at DebConf10meetingenClose the conf properlyClose the conf properly, say thanks to volunteers, ask for cleanup help, ask for feedbackHolger LevsenJoerg JaspertCésar Gómez MartínJose Antonio Recio Cuesta10:0001:00Lower talkroomIntroduction to ShaftA tool for simplified, declarative unit testing of shell scriptslectureenWe will introduce the reasoning for developing a high-level functional unit testing tool for shell code named Shaft
(Shell Advanced Functional Tester) geared towards the GNU Bash shell. We will also provide some key highlights of its advantages and features. The tool was developed at Igalia as part of the testing environment used in some of our projects.Adrián Pérez de Castro11:0001:00Lower talkroomGaneti(a cluster of debian machines on your own laptop)lectureenGaneti is a cluster virtualization platform I help devloping at Google, which can help scheduling virtual machines on clusters of physical nodes, using various virtualization technologies, like KVM and Xen. With this talk I'd like to tackle the "for developer" aspect of Ganeti, and how I use it personally, on a platform which is most probably far away from what it was originally targeted to: my laptop.The talk will feature an introduction of Ganeti 2.0 as a tool in general, the differences with the previous version (included in Debian Lenny) and its usage on a cluster of servers. Then I'll take a look at how you can use it on your personal development machines, for testing/building packages, testing network servers and protocols, and more. There will then be time for feedback, in which I hope to get suggestions from Debian people about how to do things better, or about features they would find useful for the development of this software.Guido Trotter
Main ganeti open source page
Talk outline/example commands
12:0001:00Lower talkroomCooperation and Social Status in Free and Open Source ProjectsResults from an empirical study of the Debian projectlectureenI will talk about my master thesis about the Debian project. For my thesis I gathered an extensive dataset about all sorts of Debian developement activities (mailinglist, bug reports, uploads, ...). I used this dataset first for some descriptive analysis of the project activity. I studied the growth of the project over time, the distribution of the workload among developers, the impact of releases on project activity, the impact of the creation of Ubuntu on various aspects of project activity and the distribution of the work done on Debian over weekdays and hours of the day. In a second part I verified the hypothesis that reputation and status attained through work done for the project "pays-off". Bug reports submitted by high-status contributors are fixed significantly faster and with a higher probability. Further information about my research in german (including the full text of the thesis) is available on http://gaudenz.durcheinandertal.ch/thesis/.Gaudenz Steinlin
Further information about my research in german
Full text of the masters thesis in german
13:0001:00Lower talkroomDebian and the Openmoko FreeRunner: one year laterenAt the end of DebConf8, the Debian freesmartphone.org team released the first official version of an automatic installer for the Openmoko Neo FreeRunner, the first public smartphone developer with free software in mind. Since then, Debian has been working in a very close relationship with the freesmartphone.org community, helping developing what is intended to be a full framework for smartphones based on the freedesktop.org specifications. This talk will give an overview of the situation.Luca Capello
Team wiki page
End-user wiki page
Debian freesmartphone.org project on Alioth
19:0001:00Lower talkroomMoney!How to spend more of Debian's moneybofenDebian has quite a large amount of money held in trust at SPI and elsewhere. Probably too much. What do you think we should be doing with that money? Any bright ideas?Steve McIntyre10:0002:00BOF room - no videovcs-pkg.org workgroupDrafting a roadmap for vcs-pkg.orgworkshopenThe vcs-pkg.org project aims to improve package maintenance
in version control by providing both best practices and
tools to support those practices. While there has been valuable
discussion on the merits of various approaches to parts of the problem,
the project lacks a clear plan of how it aims to achieve these goals.
This workgroup will discuss the current state of the project, and come
up with a proposal for a roadmap for the project which the project as
a whole can then approve.
Aiming to provide a set of tools and workflows that work
for most people, while remaining distribution and VCS agnostic is
laudable, but requires solving many problems to achieve. Our knowledge
of the available techniques and the problems to solve is still limited,
and so the path from the current point to the final goal is unclear.
Breaking the problem up and deciding which parts to tackle first will
allow the project to move towards the target, and if done correctly
will mean that there is useful output before the final goal is reached.
The workgroup will asses the problem as we understand it today, and
decide which problems to solve first, without attempting to solve
the problems, though debate will certainly arise.
As vcs-pkg.org is a cross-distribution project, and the choice of
DebConf means that the workgroup will be almost entirely formed of
people from Debian and Debian-based distributions, the output will
be a proposal to take back to the rest of the project.James Westby
vcs-pkg.org
http://