Apt Team

We maintain apt and python-apt.

Infrastructure

Current Team Roles

How to use git

The apt team is using git as version control system.

Help needed

How to contribute

Everybody can help APT. You are welcome to contribute on bug traging, coding, fixing bugs and merging patches, translating and so on.

Creating a local branch

Before you start, we suggest you to get a working copy of either debian-sid or debian-experimental development branch.

APT uses git

apt-get install git

Preparing and triaging

Now let's look at some bugs about apt and search for the ones tagged patch. This tag means the bug has already a patch that fixes the bug and should be reviewed. You can filter the search further.

At the beginning, it's better you start gaining experience with both the code and the documentation by looking at some minor and normal bugs. The following steps are suggested to get the triage done the best way for one bug:

  1. Read the whole information about the bug (and merged bugs), including comments until the end
  2. Read the provided patches (including merged bugs)
  3. Thank the reporter and the patcher then tune tags and severity when needed by using the control server. Please ask the maintainer when you are in doubt.

  4. Apply the patches you think are worth to be included in the latest TIP of bzr (i.e. debian-experimental). If it doesn't get applied correctly, modify the sources accordingly to the patches and to the discussion and please attach an updated patch to the bug.

Save in a personal TODO all the bugs you triage and the ones you are in doubt to contact the maintainer at once.

Committing the changes

For each patch you apply or different things you do (also small changes or typos), commit them in your local branch and create a debian/changelog entry about the changes in a compact form:

git commit -m "Message"

Usually using the changelog entry as the message is enough.