[Pkg-silc-devel] Review of the upcoming silc-server package

The Anarcat anarcat at anarcat.ath.cx
Tue Sep 4 14:10:02 UTC 2007


On Tue, Sep 04, 2007 at 12:00:57PM +0000, pkg-silc-devel-request at lists.alioth.debian.org wrote:
> 
> Message: 1
> Date: Tue, 4 Sep 2007 12:21:51 +0200
> From: J?r?my Bobbio <lunar at debian.org>
> Subject: [Pkg-silc-devel] Review of the upcoming silc-server package
> To: debian-l10n-english at lists.debian.org
> Cc: pkg-silc-devel at lists.alioth.debian.org
> Message-ID: <20070904102151.GM4961 at selene.tanneries.taz>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi!
> 
> I am trying to finalize the release of the silc-server package.  As this
> package has some debconf templates, I am asking for advices,
> reviews, fixes. :)

I'll make a quick spelling review.

> Here is the package Description:
> 
>  silc-server is a server for the SILC protocol.
>  .
>  SILC (Secure Internet Live Conferencing) is a protocol which provides
>  secure conferencing services in the Internet over insecure channel.
>  SILC is IRC like softwarre although internally they are very different.

software

>  Biggest similarity between SILC and IRC is that they both provide
>  conferencing services and that SILC has almost same commands as IRC.  Other
>  than that they are nothing alike.  Biggest differences are that SILC is
>  secure what IRC is not in any way.  The network model is also entirely
>  different compared to IRC.

I'm not sure I like this description very much. If I would rewrite it,
it would look like:

 SILC (Secure Internet Live Conferencing) is a network protocol designed
 to provide end-to-end security for conferencing services. SILC has a
 command set and a user interface similar to IRC, but the network
 protocol is completely different as it supports public key strong
 cryptography and a different network model.
 .
 This package provides a system daemon that can act as a SILC router or
 server.

> The debconf templates are available in the attachment.

As for the templates, they seem fine, although I still have a few
comments:

 1. How about putting in some default values instead of 'e.g.'? In
 particular, the silcd hostname can be deduced from hostname -f...
 2. Would it be better to set a low priority on fields than can be left
 empty?
 3. It would be nice to tell the user how the password will be stored,
 if it will be encrypted, if he has to remember it, etc...
 4. Maybe the administrator can be compared to the IRC operator in the
 templates so some users can understand better what it is (if it's
 appropriate, i don't actually know what a SILC administrator does)

Thanks for the hard work Lunar,

A.

-- 
C'est trop facile quand les guerres sont finies
D'aller gueuler que c'était la dernière
Amis bourgeois vous me faites envie
Ne voyez vous pas donc point vos cimetières?
                        - Jaques Brel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-silc-devel/attachments/20070904/4a3488f7/attachment.pgp 


More information about the Pkg-silc-devel mailing list