[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#108416: Format of short description should be mandated

[Do not CC me on messages to mailing lists, including mail to
debian-policy bugs; I read the debian-policy list.]

On Mon, Aug 13, 2001 at 11:36:22AM -0400, Jim Penny wrote:
> A question--
> suppose you were packaging a database adapter
> python-popy: database adapter
> Seems a bit light.  Certainly you are going to have to say which
> database the adapter adapts to.
> python-popy: module providing programmers a database adapter from python to Pos
> tgreSQL using the Python Database API Specification 2.0 (level 2 compliant)
> I assert that in some sense, this is a minimal correct short description.
> It can be shortened.  But even a confusing description hitting only the
> keywords is more than 80 characters, e.g.
> python-popy database adapter PostgreSQL Python Database API Specification 2.0 (level 2 compliant)
> What is the correct solution?

The correct solution is to put as much useful information into the short
description as you can fit into the character limit without awkwardness,
and without sacrificing comprehensibility.

E.g, removing all vowels would be unacceptable.

G. Branden Robinson                |     Suffer before God and ye shall be
Debian GNU/Linux                   |     redeemed.  God loves us, so He
branden@debian.org                 |     makes us suffer Christianity.
http://people.debian.org/~branden/ |     -- Aaron Dunsmore

Attachment: pgpFX8nU7RGpo.pgp
Description: PGP signature

Reply to: