unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: "Tomáš Čech" <sleep_walker@gnu.org>
Cc: 31121@debbugs.gnu.org
Subject: [bug#31121] [PATCH 1/3] gnu: Add python2-urlgrabber
Date: Tue, 17 Apr 2018 01:13:22 +0200	[thread overview]
Message-ID: <87po2ybv8t.fsf@fastmail.com> (raw)
In-Reply-To: <20180416214632.w3hmsi6fmih3u6zr@doom>

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

Tomáš Čech <sleep_walker@gnu.org> writes:

>>> +    (description "URL grabber library unifying http://, ftp:// and file://
>>> +protocols access, supporting HTTP keepalive, reget, throttling and other
>>> +convenience features.")
>>
>>Please turn this into one or more complete sentences.
>>E.g. "@code{urlgrabber} is a Python library that unifies access to
>>...  It supports bla bla.".
>
> To be honest, this is always the most painful part for me. I'll try to come with something better.

Descriptions *are* difficult, especially for tools you are unfamiliar
with.  It does not help that upstream descriptions are often targeting a
highly specialized demographic, whereas we are catering for a much wider
audience.  I try to make them generic, and include some information
about why the user would want this package/how it's used.

Occasionally I'll browse the packages at gnu.org/s/guix for inspiration.
(or look at Debians description, but don't tell anyone)

Writing the code is comparatively easy :-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-04-16 23:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10  9:24 [bug#31121] [PATCH 1/3] gnu: Add python2-urlgrabber Tomáš Čech
2018-04-10  9:29 ` [bug#31121] [PATCH 2/3] gnu: Add python-m2crypto, python2-m2crypto Tomáš Čech
2018-04-10  9:29   ` [bug#31121] [PATCH 3/3] gnu: Add osc Tomáš Čech
2018-04-16 22:04     ` Marius Bakke
2018-04-17 21:39       ` [bug#31121] [PATCH 2/3] gnu: Add python-m2crypto, python2-m2crypto Tomáš Čech
2018-04-18 11:17         ` Marius Bakke
2018-04-17 21:40       ` [bug#31121] [PATCH 3/3] gnu: Add osc Tomáš Čech
2018-04-18 11:21         ` Marius Bakke
2018-04-18 12:34           ` Tomáš Čech
2018-04-19 15:41             ` Marius Bakke
2018-04-16 21:54   ` [bug#31121] [PATCH 2/3] gnu: Add python-m2crypto, python2-m2crypto Marius Bakke
2018-04-16 21:36 ` [bug#31121] [PATCH 1/3] gnu: Add python2-urlgrabber Marius Bakke
2018-04-16 21:46   ` Tomáš Čech
2018-04-16 23:13     ` Marius Bakke [this message]
2018-04-17 21:38     ` Tomáš Čech
2018-04-18 11:22       ` Marius Bakke
2018-04-21  6:42         ` bug#31121: patchset Tomáš Čech

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=87po2ybv8t.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=31121@debbugs.gnu.org \
    --cc=sleep_walker@gnu.org \
    /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).