Differences between revisions 13 and 14
Revision 13 as of 2019-08-26 17:08:20
Size: 2202
Editor: nodiscc
Comment: remove link to unmaintained, empty page
Revision 14 as of 2019-08-26 17:10:38
Size: 2823
Editor: nodiscc
Comment: move content from FortunesDebianDevel here, page is unmaintained
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
||
Line 44: Line 44:
'''Debian Hints:'''
 * Where's the source? Provide a [[http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-vcs|Vcs-*]] field for your package, so people can easily write and provide patches.
 * Documentation, Documentation, Documentation: Good software needs good documentation.
 * React to bugs. (answer bugreports, mark them as [[http://www.debian.org/Bugs/Developer#tags|pending]]... so bug reporter know bugs matter to you).
 * Promote your package: [[http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-pkg-desc|Description]] is the key !

Line 47: Line 54:

Note

This page is a draft for a frontpage for DD, DM and packages maintainers.


<< Return to frontpage

Collaboration

DD Ressources

Calling for help

Misc

Debian Hints:

  • Where's the source? Provide a Vcs-* field for your package, so people can easily write and provide patches.

  • Documentation, Documentation, Documentation: Good software needs good documentation.
  • React to bugs. (answer bugreports, mark them as pending... so bug reporter know bugs matter to you).

  • Promote your package: Description is the key !

See also


This wiki is a support and documentation resource for the Debian project, as well as a means of communication between developers.
This portal is targeted to Debian Maintainers and Developers.

(Visit also the website's Developers' corner pages)

Search the wiki (by pages title)

News (from #debian-devel topic)

DEPRECATED







Collabortation

DD Ressources

Calling for help

Misc

Debian Hints:

  • Where's the source? Provide a Vcs-* field for your package, so people can easily write and provide patches.

  • Documentation, Documentation, Documentation: Good software needs good documentation.
  • React to bugs. (answer bugreports, mark them as pending... so bug reporter know bugs matter to you).

  • Promote your package: Description is the key !

See also