Differences between revisions 1 and 21 (spanning 20 versions)
Revision 1 as of 2008-10-01 19:24:10
Size: 410
Editor: ?MichaelVogt
Comment:
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:
= Apt Team =

We maintain apt and python-apt.
The '''Apt team''' maintains [[Apt]], DebianPackage:python-apt and DebianPackage:apt-listchanges.
Line 6: Line 4:
 * Alioth Project: http://alioth.debian.org/projects/apt
* Salsa Project: https://salsa.debian.org/apt-team/apt
Line 8: Line 7:
   * bzr branch http://bzr.debian.org/apt/apt/debian-sid (anonymous)
   * bzr checkout sftp://bzr.debian.org/apt/apt/debian-sid (team members)
 * Mailinglist
   * deity@lists.debian.org
 * Irc:
   * #debian-apt on OFTC
  * {{{git clone https://salsa.debian.org/apt-team/apt.git}}} (anonymous)
  * {{{git clone git@salsa.debian.org:apt-team/apt.git}}} (team members)
 * Mailing list:
  * deity@lists.debian.org
 * IRC:
  * [[ircs://irc.debian.org/debian-apt|#debian-apt on OFTC]]

== 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.
Line 16: Line 27:
 * bug triage
 * Bug triage:
  * [[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]]

= 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 [[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.

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
 1. Read the provided patches (including merged bugs)
 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'''.

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

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