# Goals

* update on piuparts and piuparts.d.o
* future plans
* make the whole thing useful: make Debian better

# /me

# Debian


# What's piuparts


# Development status

* master/slave support
  piuparts-master is in Wheezy
* support for http://packages.qa.debian.org/adequate in Jessie and wheezy-backports

# Team

* now: Andreas, h01ger and Dave Steel
* since 2010: 8 commiters in total
* tomorrow: you!

# How to help

## Roadmap

See ./TODO in git.

## In short

1. git clone git://anonscm.debian.org/piuparts/piuparts.git
2. git checkout -b feature/BLAH origin/develop
3. $EDITOR [rince & repeat]
4. submit your feature branch or Git patchset on bugs.debian.org

## Branches

* `master` for releases
* `develop` for daily development
* `bikeshed`: in production on p.d.o, generally same as `develop`

## Help test piuparts itself

`unitest.py`

* test an archive with known good and known wrong packages, see
  how piuparts behaves
* last really edited before 2007
* you can make the difference

## Random improvements you care about (and I don't)

Patches you need to write if you want it (and sometimes, first
convince us it's a good idea):

* extra tests for initscripts (#558819)
* cowbuilder
* LVM support
* make piuparts without root privs (#708663)

## Need to discuss first?

	<piuparts@lists.alioth.debian.org>

or

        #debian-qa on irc.debian.org

# And now?

## Let's get organized

We've seen what piuparts can do already. **And now?**

Let's coordinate the Debian developers community with the actual
efforts that are put into piuparts.

## What are the needs?

* e.g. run piuparts on the whole archive, not only amd64
* raise some errors priority (broken symlinks, to start with)
* add your needs here
* the long road to fully automated bug filing
  ... to keep this QA effort alive and kicking
  ... to make it possible to add more and more tests without increasing workload too much
* more: see the roadmap


Send your ideas to debian-qa@lists.debian.org.

http://piuparts.debian.org/
https://wiki.debian.org/piuparts