Differences between revisions 1 and 2
Revision 1 as of 2012-03-25 11:50:58
Size: 1412
Editor: MartinWerner
Comment:
Revision 2 as of 2012-04-04 11:49:32
Size: 1369
Editor: MartinWerner
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
=== VCS === === Comitting ===
Line 26: Line 26:

 * Notify all the people listed as Uploaders and Maintainers, including the pkg-games-devel mailing list, and wait for an 'OK' from one of the maintainers before uploading.
  * If you do not receive an answer, fall back on standard [[ NonMaintainerUpload| NMU]]/[[Teams/MIA| MIA]] procedures.
 * Notify all the people listed as Uploaders and Maintainers, including the pkg-games-devel mailing list.
  * You do not need to wait for a reply in order to upload, but you do need to act on objections by the maintainer(s) if they should arise.

WORK IN PROGRESS, DRAFT GUIDELINES ARE NOT IN EFFECT

Guidelines for packages maintained by others

These guidelines are meant to apply to both other members of the Debian Games Team and Debian Developers, who wants to help out with pkg-games packages which currently are maintained by others.

Check debian/README.source

  • If a package has differing instructions in debian/README.source (or another appropriate place), these take precedence over the guidelines on this page, please macke sure to check this first.

Comitting

For commiting to packages kept in version control (SVN/git) we ask you to:

  • Notify all the people listed as Uploaders and Maintainers, including the pkg-games-devel mailing list.
    • You do not need to wait for a reply in order to commit, but you do need to act on objections by the maintainer(s) if they should arise.

Uploading

For uploading packages we ask you to:

  • Notify all the people listed as Uploaders and Maintainers, including the pkg-games-devel mailing list.
    • You do not need to wait for a reply in order to upload, but you do need to act on objections by the maintainer(s) if they should arise.
  • If the package is kept in VCS, make sure the VCS is updated accordingly (import, commit, tag, etc.).