Hi Justin, thanks a lot for your very detailed review! Am Sonntag, 31. Januar 2010 schrieb Justin B Rye: > Thomas Müller wrote: > I'm not keen on this terminology of Quassel being an IRC *client* > with a core and a *client* component - it seems unnecessarily > confusing. I'd suggest calling them "back-end" and "front-end" > components; but that's far too radical for a package description > review! > Well - that's the upstream terminology - we better not change this. > > [...] A modern, cross-platform, > > distributed IRC client, meaning that one (or multiple) client(s) can > > attach to and detach from this central core. [...] > Using parentheses may seem logical, but it would be idiomatic > English just to say "one or more clients". > Lesson learned - thx. > A knock-on effect: s/this/the/. (Mind you, if the core is > "central", that's not very "distributed"...) > Well upstream again - I agree to you. > > [...] It's much like the popular combination of screen > > and a text-based IRC client such as WeeChat, but graphical. > > Judging by popcon scores you'd be much better off comparing irssi > rather than weechat. > WeeChat is used in the upstream description. They know weechat more than irssi. Lets take both ... > 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. > I like it - THX > > . > > 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/? > > > Package: quassel-client > > [...] > > > Recommends: quassel-core > > Do I gather that in principle you can use a quassel-client* package > without also having quassel-core installed on the same host? It > might be worth explaining that dependency here. Otherwise, fine. > Thats right. The idea is to have a core running on a server with 24h internet access - maybe in a virtual server on the internet. Users connect to the core from other hosts as they like. While offline the chat messages are stored in a database and can be viewed later. Shall we explain it in the description? > > . > > This package installs the monolithic client. This contains both core and > > client and can be used like a traditional IRC client, without requiring > > an external core. > > Uh... why would anyone want that? Does Quassel have any selling > points apart from the one that this version leaves out? And how > does providing both in one package provide any benefit to Debian > users? It's only one "apt-get install" invocation either way. > Well thats for all the people out there - like me;-) - who have no interest in viewing the backlog. I just want an irc client - I use the monolithic client. > (You might also consider being kind to non-teutonophones wondering > what "quassel" means, but that could go elsewhere in the > documentation.) > Its derived from the german word "quasseln" - blather in english -- Thomas Müller (Thomas Mueller) E-Mail: thomas.mueller@tmit.eu Packages: http://qa.debian.org/developer.php?login=thomas.mueller@tmit.eu Powered by Debian
Attachment:
signature.asc
Description: This is a digitally signed message part.