From: "Pierre-Henry Fröhring" <contact@phfrohring.com>
To: Maxime Devos <maximedevos@telenet.be>, 53821@debbugs.gnu.org
Subject: [bug#53821] [PATCH] Add the python-psycopg2-binary package.
Date: Sun, 06 Feb 2022 16:27:33 +0100 [thread overview]
Message-ID: <e8f4a229a8e0c65bcbfef06ea9496c9fac709838.camel@phfrohring.com> (raw)
In-Reply-To: <6eea11cd2971dda53763d83640ea85af33d04e74.camel@telenet.be>
Hello Maxime,
I've just copy-pasted the author's description as in:
https://pypi.org/project/psycopg2-binary/
So, if I understand correctly, package contributors should (re)write
packages descriptions?
PHF
On Sun, 2022-02-06 at 15:50 +0100, Maxime Devos wrote:
> Pierre-Henry Fröhring schreef op zo 06-02-2022 om 15:38 [+0100]:
> > + "Psycopg is the most popular [...]
> > +
> > +[...], resulting in being both efficient and secure.
> >
>
> From (guix)Synopses and Descriptions:
>
> Please avoid marketing phrases such as “world-leading”,
> “industrial-strength”, and “next-generation”, and avoid superlatives
> like “the most advanced”—they are not helpful to users looking for a
> package and may even sound suspicious. Instead, try to be factual,
> mentioning use cases and features.
>
> Here, ‘most popular’ would could as marketing (it isn't important
> whether it's popular, what is important is that it works well),
> and to a lesser degree ‘efficient and secure’ -- everything is
> supposed to be efficient and secure (with varying success).
>
> Greetings,
> Maxime.
next prev parent reply other threads:[~2022-02-06 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 14:38 [bug#53821] [PATCH] Add the python-psycopg2-binary package Pierre-Henry Fröhring
2022-02-06 14:50 ` Maxime Devos
2022-02-06 15:27 ` Pierre-Henry Fröhring [this message]
2022-02-06 15:44 ` Maxime Devos
2022-02-06 14:51 ` Maxime Devos
2022-02-06 15:35 ` Pierre-Henry Fröhring
2022-03-24 22:23 ` bug#53821: " Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e8f4a229a8e0c65bcbfef06ea9496c9fac709838.camel@phfrohring.com \
--to=contact@phfrohring.com \
--cc=53821@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).