Differences between revisions 19 and 21 (spanning 2 versions)
Revision 19 as of 2021-07-21 10:20:59
Size: 3171
Editor: ?BrianThompson
Comment: Add myself to Current Team Roles, fixed some punctuation in the same section
Revision 21 as of 2021-08-01 12:19:37
Size: 3250
Editor: PaulWise
Comment: updates
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
The '''Apt team''' maintains [[Apt]] and python-apt. The '''Apt team''' maintains [[Apt]], DebianPackage:python-apt and DebianPackage:apt-listchanges.
Line 4: Line 4:
Line 8: Line 9:
 * Mailinglist  * Mailing list:
Line 10: Line 11:
 * Irc:
  * [[irc://irc.debian.org/debian-apt|#debian-apt on OFTC]]
 * IRC:
  * [[ircs://irc.debian.org/debian-apt|#debian-apt on OFTC]]
Line 13: Line 15:
Line 18: Line 21:
Line 19: Line 23:
Line 22: Line 27:
Line 23: Line 29:
  * [[http://bugs.debian.org/apt|bugs about apt]]
  * [[http://bugs.debian.org/python-apt|bugs about `python-apt`]]
  * [[http://bugs.debian.org/apt-listchanges|bugs about apt-listchanges]]
  * [[https://bugs.debian.org/src:apt|bugs about apt]]
  * [[https://bugs.debian.org/src:python-apt|bugs about python-apt]]
  * [[https://bugs.debian.org/src:apt-listchanges|bugs about apt-listchanges]]
Line 28: Line 34:
Line 31: Line 38:
Line 36: Line 44:
apt-get install git}}} apt install git
}}}
Line 39: Line 48:
Now let's look at some [[http://bugs.debian.org/apt|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 [[http://bugs.debian.org|filter the search]] further.
Now let's look at some [[https://bugs.debian.org/src:apt|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 [[https://bugs.debian.org|filter the search]] further.
Line 45: Line 55:
 1. Thank the reporter and the patcher then tune tags and severity '''when needed''' by using the [[http://www.debian.org/Bugs/server-control|control server]]. Please ask the maintainer when you are in doubt.
 1. 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'''.
 1. Thank the reporter and the patcher then tune tags and severity '''when needed''' by using the [[https://www.debian.org/Bugs/server-control|control server]]. Please ask the maintainer when you are in doubt.
 1. Apply the patches you think are worth to be included in the latest TIP of git (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'''.
Line 54: Line 64:
git commit -m "Message"}}} git commit -m "Message"
}}}
Line 57: Line 69:
Line 59: Line 70:

CategoryDeveloper | CategoryPackageManagement
----
CategoryTeams
CategoryDeveloper | CategoryPackageManagement | CategoryTeams

The Apt team maintains Apt, python-apt and apt-listchanges.

Infrastructure

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.
  • Brian Thompson is working on maintaining supplementary apt packages (e.g. apt-listchanges).

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 triaging, 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 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 git (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.


CategoryDeveloper | CategoryPackageManagement | CategoryTeams