[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [RFR] templates://phamm/{phamm.templates}



Christian Perrier wrote:
> Your review should be sent as an answer to this mail.

>  Template: phamm/ldap-server
[...]
>   Please enter the host name or the address of the LDAP server you want to
>   connect to.

Or:
    Please enter the host name or IP address of the LDAP server that Phamm
    should connect to.
  
I might after all be doing it because my idiot boss insists.  And
it isn't connecting *me* to an LDAP server!

>  Template: phamm/ldap-basedn
[...]
> +Default: dc=example,dc=tld
> +_Description: Distinguished name of the search base:
>   Please enter the distinguished name of the LDAP search base. Many sites
>   use the components of their domain names for this purpose. For example,
> + the domain "example.com" would use "dc=example,dc=com".

Could we change the example and default to example.org?  Also, the
references to DNs throughout these templates are inconsistent; here,
let's keep them spelled-out and capitalised.

   Default: dc=example,dc=org
   _Description: Distinguished Name of the search base:
    Please enter the Distinguished Name of the LDAP search base. Many sites
    use the components of their domain names for this purpose. For example,
    the domain "example.org" would use "dc=example,dc=org".

>  Template: phamm/ldap-binddn
> +Default: cn=manager,dc=example,dc=tld
> +_Description: Login DN for the LDAP server:
> + Please enter the name of the account that will be used to log in to the LDAP

It doesn't want a *name* (like "Justin", or even "jbr").  Compare
the default, above (oh, and again, .org).

>   server. If you chose a form based authentication this will be the default
> + login DN. In this case you can also leave it empty, if you do not want a
>   default one.

Again, whether I want it isn't necessarily relevant.  And hyphen but
no article on "form based authentication".

    Please enter the Distinguished Name of the account that will be used to
    log in to the LDAP server. If you chose form-based authentication this
    will be the default login DN. In this case leaving it empty will prevent
    the creation of a default login DN.

(But when did the user get an opportunity to choose form-based
authentication?)

>  Template: phamm/ldap-bindpw
[...]
> + Please enter the password that will be used to login to the LDAP server.
                                                      ^
This is another of those cases (like setup/backup) where the verb's
two words (you can tell because it's possible "to log yourself in").

    Please enter the password that will be used to log in to the LDAP server.
  
>  Package: phamm
[...]
> +Description: PHP front-end to manage virtual services using LDAP - main package
>   Phamm provides an useful PHP front-end with multi-role access to manage
> + virtual services using a LDAP backend.

A yuseful, an el-DAP.  Also, reorganising for enhanced
buzzword-compliance (what's multi-role access?):

    Phamm is a useful PHP front-end providing role-based administrative
    access to virtual services using an LDAP back-end.

> + Phamm works with a plug-in system: the typical service is a mail
> + server with virtual mail domain support but other plug-ins are
> + available (ftp, proxy...). The creation of new plugins or the
> + customization of existing ones are made easy by the use of XML
> + descriptor files.

Inlining the messy parenthesis, and de-passivising further:

    server with virtual mail domain support, but plug-ins are also
    available for FTP, web proxying, and so on. The use of XML descriptor
    files simplifies creating new plugins or customizing existing ones.

> Package: phamm-ldap
[...]
> +Description: PHP front-end to manage virtual services using LDAP - LDAP backend files

That's getting really long - worse if I standardise throughout on
hyphenated front- and back-ends.  How about: 

   Description: PHP front-end to manage virtual services with LDAP - back-end files

-- 
JBR	with qualifications in linguistics, experience as a Debian
	sysadmin, and probably no clue about this particular package
--- ../phamm.old/debian/phamm.templates	2007-12-29 21:08:58.000000000 +0000
+++ debian/phamm.templates	2008-01-07 13:39:12.000000000 +0000
@@ -1,51 +1,49 @@
 Template: phamm/ldap-server
 Type: string
-_description: LDAP server host address:
- Please enter the host name or the address of the LDAP server you want to
- connect to.
 Default: 127.0.0.1
+_Description: LDAP server host:
+ Please enter the host name or the address of the LDAP server that Phamm
+ should connect to.
 
 Template: phamm/ldap-basedn
 Type: string
-_description: Distinguished name of the search base:
- Please enter the distinguished name of the LDAP search base. Many sites
+Default: dc=example,dc=org
+_Description: Distinguished Name of the search base:
+ Please enter the Distinguished Name of the LDAP search base. Many sites
  use the components of their domain names for this purpose. For example,
- the domain "example.com" would use "dc=example,dc=com" as the
- distinguished name of the search base.
-Default: dc=example,dc=tld
+ the domain "example.org" would use "dc=example,dc=org".
 
 Template: phamm/ldap-binddn
 Type: string
-_description: Login dn for the LDAP server:
- Enter the name of the account that will be used to log in to the LDAP
- server. If you chose a form based authentication this will be the default
- login dn. In this case you can also leave it empty, if you do not want a
- default one.
-Default: cn=manager,dc=example,dc=tld
+Default: cn=manager,dc=example,dc=org
+_Description: Login DN for the LDAP server:
+ Please enter the Distinguished Name of the account that will be used to
+ log in to the LDAP server. If you chose form-based authentication this
+ will be the default login DN. In this case leaving it empty will prevent
+ the creation of a default login DN.
 
 Template: phamm/ldap-bindpw
-Type: string
-_description: Login password for the LDAP server:
- Enter the password that will be used to log in to the LDAP server.
+Type: password
 Default: secret
+_Description: Login password for the LDAP server:
+ Please enter the password that will be used to log in to the LDAP server.
 
 Template: phamm/plugins
 Type: multiselect
-_description: Which plugins you want Phamm supports:
-_Choices: mail, alias, ftp, person, proxy
-Default: mail
+__Choices: mail, alias, ftp, person, proxy
+_Default: mail
+_Description: Plugins to be supported by Phamm:
 
 Template: phamm/reconfigure-webserver
 Type: multiselect
-_description: Web server which will be reconfigured automatically:
+Choices: apache, apache-ssl, apache-perl, apache2
+Default: apache, apache-ssl, apache-perl, apache2
+_Description: Web server to reconfigure automatically:
  Phamm supports any web server that PHP does, but this automatic
  configuration process only supports Apache.
-_Choices: apache, apache-ssl, apache-perl, apache2
-Default: apache, apache-ssl, apache-perl, apache2
 
 Template: phamm/restart-webserver
 Type: boolean
-_description: Restart of your webserver(s)?
- Remember that in order to apply the changes your webserver(s) has/have to
- be restarted.
 Default: true
+_Description: Restart the webserver(s)?
+ In order to apply the changes, the webserver(s) must be restarted.
--- ../phamm.old/debian/control	2007-12-29 21:08:59.000000000 +0000
+++ debian/control	2008-01-07 13:32:39.000000000 +0000
@@ -8,15 +8,20 @@
 Package: phamm
 Architecture: all
 Depends: apache2 | httpd, php5-ldap | php4-ldap, libapache2-mod-php5 | libapache-mod-php5 | php5-cgi | php5 | libapache2-mod-php4 | libapache-mod-php4 | php4 (>= 4.1.0) | php4-cgi, debconf (>= 0.5) | debconf-2.0, ${misc:Depends}
-Description: a PHP front-end to manage virtual services using LDAP
- Phamm provides an useful PHP front-end with multi-role access to manage
- virtual services using a LDAP backend. Phamm works with a plug-in system,
- the typical service is a mail server with virtual mail domain support
- but other plug-ins are available (ftp, proxy...). It is easy create or
- customize existing plug-ins for Phamm using XML descriptor files.
+Description: PHP front-end to manage virtual services with LDAP - main package
+ Phamm is a useful PHP front-end providing role-based administrative
+ access to virtual services using an LDAP back-end.
+ .
+ Phamm works with a plug-in system: the typical service is a mail
+ server with virtual mail domain support, but plug-ins are also
+ available for FTP, web proxying, and so on. The use of XML descriptor
+ files simplifies creating new plugins or customizing existing ones.
 
 Package: phamm-ldap
 Architecture: all
 Depends: gnarwl
-Description: Phamm LDAP backend files
- Phamm backend require own phamm.schema and custom ACL.
+Description: PHP front-end to manage virtual services with LDAP - back-end files
+ Phamm is a useful PHP front-end providing role-based administrative
+ access to virtual services using an LDAP back-end.
+ .
+ This package provides Phamm's own LDAP schema file and custom ACL.
Template: phamm/ldap-server
Type: string
Default: 127.0.0.1
_Description: LDAP server host:
 Please enter the host name or the address of the LDAP server that Phamm
 should connect to.

Template: phamm/ldap-basedn
Type: string
Default: dc=example,dc=org
_Description: Distinguished Name of the search base:
 Please enter the Distinguished Name of the LDAP search base. Many sites
 use the components of their domain names for this purpose. For example,
 the domain "example.org" would use "dc=example,dc=org".

Template: phamm/ldap-binddn
Type: string
Default: cn=manager,dc=example,dc=org
_Description: Login DN for the LDAP server:
 Please enter the Distinguished Name of the account that will be used to
 log in to the LDAP server. If you chose form-based authentication this
 will be the default login DN. In this case leaving it empty will prevent
 the creation of a default login DN.

Template: phamm/ldap-bindpw
Type: password
Default: secret
_Description: Login password for the LDAP server:
 Please enter the password that will be used to log in to the LDAP server.

Template: phamm/plugins
Type: multiselect
__Choices: mail, alias, ftp, person, proxy
_Default: mail
_Description: Plugins to be supported by Phamm:

Template: phamm/reconfigure-webserver
Type: multiselect
Choices: apache, apache-ssl, apache-perl, apache2
Default: apache, apache-ssl, apache-perl, apache2
_Description: Web server to reconfigure automatically:
 Phamm supports any web server that PHP does, but this automatic
 configuration process only supports Apache.

Template: phamm/restart-webserver
Type: boolean
Default: true
_Description: Restart the webserver(s)?
 In order to apply the changes, the webserver(s) must be restarted.
Source: phamm
Section: web
Priority: extra
Maintainer: Alessandro De Zorzi <lota@nonlontano.it>
Build-Depends: debhelper (>= 5), po-debconf
Standards-Version: 3.7.2

Package: phamm
Architecture: all
Depends: apache2 | httpd, php5-ldap | php4-ldap, libapache2-mod-php5 | libapache-mod-php5 | php5-cgi | php5 | libapache2-mod-php4 | libapache-mod-php4 | php4 (>= 4.1.0) | php4-cgi, debconf (>= 0.5) | debconf-2.0, ${misc:Depends}
Description: PHP front-end to manage virtual services with LDAP - main package
 Phamm is a useful PHP front-end providing role-based administrative
 access to virtual services using an LDAP back-end.
 .
 Phamm works with a plug-in system: the typical service is a mail
 server with virtual mail domain support, but plug-ins are also
 available for FTP, web proxying, and so on. The use of XML descriptor
 files simplifies creating new plugins or customizing existing ones.

Package: phamm-ldap
Architecture: all
Depends: gnarwl
Description: PHP front-end to manage virtual services with LDAP - back-end files
 Phamm is a useful PHP front-end providing role-based administrative
 access to virtual services using an LDAP back-end.
 .
 This package provides Phamm's own LDAP schema file and custom ACL.

Reply to: