I think it would be useful to document the features that the Chef repositories contain so that there can be feature parity for the puppet manifests #1432060: Puppet branch or own project?, best practices and settings can easily be incorporated, etc.

Here is an initial attempt after looking through the chef cookbooks. I'm sure I missed something. Should I submit this as a patch to the README?

+ Ubuntu / Debian Packages
build-essential
apache2
autoconf
bison
flex
git-core
imagemagick
libapache2-mod-fcgid
libapache2-mod-php5
libapache2-mod-python
libapache2-mod-wsgi
libapache2-svn
libmagickwand-dev
libmemcache-dev
libmysql-ruby
libmysqlclient-dev
memcached
mysql-client
mysql-server
php-fpdf
php5-apc
php5-curl
php5-fileinfo
php5-gd
php5-ldap
php5-memcache
php5-mysql
php5-sqlite3
php5-xhprof
phpmyadmin
pkg
subversion
varnish

+ Drupal
core 7.x

+ Tools
drush 7.x-4.5
drush make 6.x-2.2
phpmyadmin 3.3.2
webgrind trunk
xhprof 0.9.2
memcache 1.4.2
imagemagick 0.2.0

+ PHP 5.3 Settings
short_open_tag On
asp_tags Off
precision 12
output_buffering Off
serialize_precision 100
memory_limit 196M
max_execution_time 30
error_reporting ALL
display_errors On
log_errors On
post_max_size 1024M
file_uploads On
upload_max_filesize 1024M

Apache2
listen port 80
timeout 300
keepalive On
keepaliverequests 100
keepalivetimeout 5
servertokens Prod
serversignature On
traceenable On
startservers 16
minspareservers 16
maxspareservers 32
serverlimit 400
maxclients 400
maxrequestsperchild 10000

MySQL
port 3306
max_allowed_packet 16M
thread_stack 128K
thread_cache_size 8
query_cache_limit 1M
query_cache_size 16M
back_log 128
key_buffer 256M
max_allowed_packet 16M
max_connections 800
max_heap_table_size 32M
myisam_recover BACKUP
net_read_timeout 30
net_write_timeout 30
table_cache 128
table_open_cache 128
thread_cache 128
thread_cache_size 8
thread_concurrency 10
thread_stack 256K
wait_timeout 180
query_cache_limit 1M
query_cache_size 16M
log_slow_queries /var/log/mysql/slow.log
long_query_time 2