We maintain apt and python-apt.
Salsa Project: https://salsa.debian.org/apt-team/apt
- Source code:
git clone https://salsa.debian.org/apt-team/apt.git (anonymous)
git clone email@example.com:apt-team/apt.git (team members)
Current Team Roles
- David Kalnischkies is the main person that does the coding work (and is the evil mastermind)
- Michael Vogt is currently the main person doing review/uploads.
- Julian Andres Klode works mostly on python-apt
- Christian Perrier is doing l10n maintenance.
How to use git
The apt team is using git as version control system.
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
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:
- Read the whole information about the bug (and merged bugs), including comments until the end
- Read the provided patches (including merged bugs)
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.
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.