also sprach Philip Ashmore<contact@philipashmore.com> [2011.12.18.0834 +0100]:
If no one has any more issues with the new long description then
I'll assume all is well.
Hello Philip,
a long description is neither a text of marketing, nor should it be
a complete list of features. The former can go on a website, the
latter should be found in a README file.
The long description should preemptively provide a user with enough
information so that s/he can make a choice. It should be written
with complete sentences in free text, with an informative, objective
style.
A rough guidelines of questions to be answered across three
paragraphs could be:
1. What is the general purpose of the software in this package, or
the collection of software that this package belongs to?
2. What distinguishes this software from other software? For what
use cases was the software designed?
3. How does this package fit in into a collection (unless it's
a single package)? Are there any other noteworthy things that
the user might need to know to decide for or against a piece of
software?