Package: chef
Version: N/A
Severity: normal
Tags: patch

Dear Debian maintainer,

On Friday, June 04, 2010, I notified you of the beginning of a review process
concerning debconf templates for chef.

The debian-l10n-english contributors have now reviewed these templates,
and the proposed changes are attached to this bug report.

Please review the suggested changes, and if you have any
objections, let me know in the next 3 days.

However, please try to avoid uploading chef with these changes
right now.

The second phase of this process will begin on Wednesday, June 23, 2010, when I 
will
coordinate updates to translations of debconf templates.

The existing translators will be notified of the changes: they will
receive an updated PO file for their language.

Simultaneously, a general call for new translations will be sent to
the debian-i18n mailing list.

Both these calls for translations will request updates to be sent as
individual bug reports. That will probably trigger a lot of bug
reports against your package, but these should be easier to deal with.

The call for translation updates and new translations will run until
about Wednesday, July 14, 2010. Please avoid uploading a package with fixed or 
changed
debconf templates and/or translation updates in the meantime. Of
course, other changes are safe.

Please note that this is an approximative delay, which depends on my
own availability to process this work and is influenced by the fact
that I simultaneously work on many packages.

Around Thursday, July 15, 2010, I will contact you again and will send a final 
patch
summarizing all the updates (changes to debconf templates,
updates to debconf translations and new debconf translations).

Again, thanks for your attention and cooperation.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- chef.old/debian/chef.templates      2010-05-31 07:23:00.437646116 +0200
+++ chef/debian/chef.templates  2010-06-20 14:04:25.832370966 +0200
@@ -1,7 +1,14 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# [email protected] for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
 Template: chef/chef_server_url
 Type: string
-Description: URL of Chef Server (e.g., http://chef.example.com:4000):
-  This is the full URI that clients will use to connect to the
-  server.
-  .
-  This will be used in /etc/chef/client.rb as 'chef_server_url'.
+_Description: Chef server URL:
+ Please specify the full URL that clients will use to connect to the
+ Chef server (for instance "http://chef.example.com:4000";).
--- chef.old/debian/chef-solr.templates 2010-05-31 07:23:00.441648323 +0200
+++ chef/debian/chef-solr.templates     2010-06-20 14:04:25.868380857 +0200
@@ -1,12 +1,19 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# [email protected] for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
 Template: chef-solr/amqp_password
 Type: password
-_Description: New password for the 'chef' AMQP user in the RabbitMQ vhost 
"/chef":
-  Set the password for the chef user in the AMQP server queue. Use
-  RabbitMQ's rabbitmqctl program to set this password. The default user
-  and vhost are assumed (chef and /chef, respectively).
-  .
-  RabbitMQ does not have the capability to read the password from a file, and
-  this will be passed via "" on the command-line. As such, do not use shell
-  meta-characters that could cause errors such as !.
-  .
-  This will be used in /etc/chef/solr.rb and /etc/chef/server.rb as 
'amqp_pass'.
+_Description: Password for the AMQP user "chef":
+ Please choose a password for the default user (named "chef") in the AMQP
+ server queue, under the default RabbitMQ vhost (also "/chef").
+ .
+ RabbitMQ's rabbitmqctl program, which will be used to set this password,
+ cannot read input from a file. Instead it will be passed as a command-line
+ argument, so the password should not include any shell meta-characters
+ that could cause errors, such as "!".
--- chef.old/debian/chef-server-webui.templates 2010-05-31 07:23:00.433645236 
+0200
+++ chef/debian/chef-server-webui.templates     2010-06-20 14:04:52.475360805 
+0200
@@ -1,16 +1,19 @@
+# These templates have been reviewed by the debian-l10n-english
+# team
+#
+# If modifications/additions/rewording are needed, please ask
+# [email protected] for advice.
+#
+# Even minor modifications require translation updates and such
+# changes should be coordinated with translators and reviewers.
+
 Template: chef-server-webui/admin_password
 Type: password
-_Description: New password for the 'admin' user in the Chef Server WebUI:
-  This sets a temporary first-use password to log into the Chef Server WebUI
-  as the 'admin' user for the first time. Once logged in, the password should
-  be changed immediately.
-  .
-  Once the chef-server-webui process is running, login using the username
-  'admin' using the password set here.
-  .
-  If a password is not entered, the webui default password for 'admin' will
-  be used, which is displayed on the webui home page. The password must be 
-  at least 6 characters or the webui will not start properly.
-  .
-  This will be used in /etc/chef/webui.rb as 'web_ui_admin_default_password'.
-  .
+_Description: Temporary password for the Chef server user "admin":
+ Please choose a temporary password for the first time the "admin"
+ user logs into the Chef server web interface. It should be changed
+ immediately after being used.
+ .
+ This password must be at least six characters long. If no password
+ is entered, a default value will be used which is displayed on the
+ Chef server web interface home page.
--- chef.old/debian/control     2010-05-31 07:23:00.425639567 +0200
+++ chef/debian/control 2010-06-07 06:41:49.500649660 +0200
@@ -12,13 +12,14 @@
 Architecture: all
 Depends: ${misc:Depends}, ruby1.8, liberubis-ruby1.8, libjson-ruby1.8, 
libextlib-ruby1.8 (>= 0.9.13), ohai (>= 0.4.0), libchef-ruby1.8 (= 
${source:Version}), libopenssl-ruby1.8, libmixlib-authentication-ruby1.8 (>= 
1.1.0), ucf
 Recommends: irb1.8
-Description: System integration framework written in Ruby
+Description: system integration framework - client and solo binaries
  Chef is a systems integration framework and configuration management library
  written in Ruby. Chef provides a Ruby library and API that can be used to
  bring the benefits of configuration management to an entire infrastructure.
  .
- Chef can be run as a client (chef-client) to a server, or run as a standalone
- tool (chef-solo). Configuration recipes are written in a pure Ruby DSL.
+ Chef can be run as a client (chef-client) to a server, or as a standalone
+ tool (chef-solo). Configuration recipes are written in a pure Ruby
+ domain-specific language.
  .
  This package contains the chef-client and chef-solo binaries and associated
  files.
@@ -29,7 +30,15 @@
 Suggests: chef (= ${source:Version})
 Replaces: chef-indexer
 Conflicts: chef-indexer
-Description: Manages search indexes of Chef node attributes using SOLR
+Description: system integration framework - search indexes management
+ Chef is a systems integration framework and configuration management library
+ written in Ruby. Chef provides a Ruby library and API that can be used to
+ bring the benefits of configuration management to an entire infrastructure.
+ .
+ Chef can be run as a client (chef-client) to a server, or as a standalone
+ tool (chef-solo). Configuration recipes are written in a pure Ruby
+ domain-specific language.
+ .
  The chef indexer listens to a message queue via AMQP for changes to search
  indexes. It then either creates or deletes entries in the index according
  to the information it is passed.
@@ -43,11 +52,15 @@
 Depends: ${misc:Depends}, ruby, merb-slices, libmerb-assets-ruby, 
libmerb-haml-ruby, libmerb-helpers-ruby, chef-server-api (= ${source:Version}), 
chef-solr (= ${source:Version}), thin, libjson-ruby, libchef-ruby (= 
${source:Version}), libuuidtools-ruby1.8, adduser, libjs-jquery (>= 1.3.2), ucf
 Recommends: chef (= ${source:Version})
 Suggests: nginx, apache2, rake, chef-server-webui (=${source:Version})
-Description: Merb application providing centralized management for Chef
- Chef is a systems integration framework and configuration management system
+Description: system integration framework - centralized server
+ Chef is a systems integration framework and configuration management library
  written in Ruby. Chef provides a Ruby library and API that can be used to
  bring the benefits of configuration management to an entire infrastructure.
  .
+ Chef can be run as a client (chef-client) to a server, or as a standalone
+ tool (chef-solo). Configuration recipes are written in a pure Ruby
+ domain-specific language.
+ .
  The Chef Server is a Merb application that provides centralized storage and
  distribution for recipes stored in "cookbooks," management and authentication
  of client nodes and node data, and search indexes for that data.
@@ -63,11 +76,15 @@
 Recommends: chef (= ${source:Version})
 Replaces: chef-server-slice
 Conflicts: chef-server-slice
-Description: Merb slice providing REST API for Chef client access
+Description: system integration framework - server API for clients
  Chef is a systems integration framework and configuration management library
  written in Ruby. Chef provides a Ruby library and API that can be used to
  bring the benefits of configuration management to an entire infrastructure.
  .
+ Chef can be run as a client (chef-client) to a server, or as a standalone
+ tool (chef-solo). Configuration recipes are written in a pure Ruby
+ domain-specific language.
+ .
  The Chef Server is a Merb application that provides centralized storage and
  distribution for recipes stored in "cookbooks," management and authentication
  of client nodes and node data, and search indexes for that data.
@@ -82,11 +99,15 @@
 Depends: ${misc:Depends}, ruby, merb-slices, libmerb-param-protection-ruby, 
libmerb-assets-ruby, libmerb-haml-ruby, libmerb-helpers-ruby, thin, 
libopenid-ruby, libjson-ruby, libchef-ruby (= ${source:Version}), 
libcoderay-ruby, chef-server (= ${source:Version}), adduser, libjs-jquery-ui 
(>= 1.7.1), ucf
 Suggests: chef (= ${source:Version}), apache2, nginx
 Conflicts: chef-server-slice
-Description: Merb app slice providing Web interface to API server for Chef
+Description: system integration framework - web interface
  Chef is a systems integration framework and configuration management library
  written in Ruby. Chef provides a Ruby library and API that can be used to
  bring the benefits of configuration management to an entire infrastructure.
  .
+ Chef can be run as a client (chef-client) to a server, or as a standalone
+ tool (chef-solo). Configuration recipes are written in a pure Ruby
+ domain-specific language.
+ .
  The Chef Server WebUI is a Merb application that accesses the Chef Server API
  directly to provide an easy to use interface for managing Chef clients and
  Chef server data.
@@ -96,11 +117,15 @@
 Package: libchef-ruby
 Architecture: all
 Depends: ${misc:Depends}, ruby, libchef-ruby1.8 (= ${source:Version})
-Description: Ruby libraries for Chef system integration framework
+Description: system integration framework - Ruby libraries
  Chef is a systems integration framework and configuration management library
  written in Ruby. Chef provides a Ruby library and API that can be used to
  bring the benefits of configuration management to an entire infrastructure.
  .
+ Chef can be run as a client (chef-client) to a server, or as a standalone
+ tool (chef-solo). Configuration recipes are written in a pure Ruby
+ domain-specific language.
+ .
  As a library, Chef allows administrators to easily tie various infrastructure
  components together.
  .
@@ -113,11 +138,15 @@
 Depends: ${misc:Depends}, ruby1.8, libopenssl-ruby1.8, 
libmixlib-authentication-ruby1.8 (>= 1.1.0), libmixlib-cli-ruby1.8 (>= 1.1.0), 
libmixlib-config-ruby1.8 (>= 1.1.0), libmixlib-log-ruby1.8 (>= 1.1.0), 
libohai-ruby1.8 (>= 0.4.0), libmoneta-ruby1.8, libbunny-ruby1.8
 Recommends: ohai (>= 0.4.0), chef (= ${source:Version}), rubygems1.8
 Suggests: rake, libshadow-ruby1.8
-Description: Ruby 1.8 libraries for Chef system integration framework
+Description: system integration framework - Ruby 1.8 libraries
  Chef is a systems integration framework and configuration management library
  written in Ruby. Chef provides a Ruby library and API that can be used to
  bring the benefits of configuration management to an entire infrastructure.
  .
+ Chef can be run as a client (chef-client) to a server, or as a standalone
+ tool (chef-solo). Configuration recipes are written in a pure Ruby
+ domain-specific language.
+ .
  As a library, Chef allows administrators to easily tie various infrastructure
  components together.
  .

Reply via email to