Re: policy for source package names

[Ben Finney <ben+debian@benfinney.id.au>]

Vincent Cheng <vcheng@debian.org> writes:

> […] just don't pick a source package name that's already taken, and
> pick one that is relevant to your package […]

I further advise: Try to avoid names which are too broad (e.g.
“coverage” for a Python-specific code coverage package), or names which
can easily be anticipated to conflict in future.

These are both judgements you'll need to make on expertise and a
perspective beyond only Python and Debian; they are (and IMO should)
based not in fixed rules, but principles.

-- 
 \         “Education is learning what you didn't even know you didn't |
  `\                  know.” —Daniel J. Boorstin, historian, 1914–2004 |
_o__)                                                                  |
Ben Finney