Re: [RFR] Description for package quassel
Justin B Rye <jbr@edlug.org.uk> writes:
> (Mind you, if the core is "central", that's not very "distributed"...)
Agreed. I think you (Thomas) should drop this “distributed” term
altogether, I don't see how it's appropriate for what this program is
described as doing.
You could ask the upstream for clarification of that term, since it's
only going to cause confusion in those who know the conventional meaning
of a “distributed application”.
> So my revised boilerplate is:
>
> Quassel is a modern, cross-platform, distributed IRC client, meaning that
> one or more clients can attach to and detach from the central core. It's
> much like the popular combination of screen and a text-based IRC client
> such as irssi, but graphical.
Once again, Justin beats me to the improvements I would have suggested
:-)
> Thomas Müller wrote:
> > .
> > This package installs only the core component.
>
> I wouldn't bother nitpicking this if I hadn't been invited, but saying
> that quassel-core _installs_ software makes it sound as if it's a
> contrib installer package or something.
>
> s/installs/provides/?
I think the “only” is also superfluous. How about:
This package provides the core component of Quassel.
> [...]
> > This package installs only the client component compiled with KDE4 support.
I suggest:
This package provides the Quassel client component compiled with
KDE4 support.
> (You might also consider being kind to non-teutonophones wondering
> what "quassel" means, but that could go elsewhere in the
> documentation.)
As someone reading the package description to know whether I want the
package on my system, I think it's fine to leave the package name as an
opaque pronounceable word.
--
\ “If you can't annoy somebody there is little point in writing.” |
`\ —Kingsley Amis |
_o__) |
Ben Finney <ben@benfinney.id.au>
Reply to: