Distributions provide site features and functions for a specific type of site as a single download containing Drupal core, contributed modules, themes, and pre-defined configuration. They make it possible to quickly set up a complex, use-specific site in fewer steps than if installing and configuring elements individually.
Nittany is a series of drush recipes maintained by the Penn State Drupal community, primarily designed to be a "starting point" for building sites as well as a series of supportable best practices for Drupal. By bundling a list of commonly-used and recommended modules, Nittany is intended to lessen the burden on new developers and site builders, by being a response to the question: "I installed Drupal, now what?". If you are building a new Drupal site, or are new to Drupal, you should try starting with Nittany.
This is an install profile that does everything that the 'Default' Drupal 6 profile does, but it also installs Admin Menu. (For Drupal 7, it uses a modified version of the 'Standard' profile.) I use this for every test site that I create, and find it very useful. I hope that I am not the only one!
This profile installs the Admin Menu, but is otherwise identical to the core default profile.
Open Event is a foundation for any cultural organisation who would like to manage and publish their events on-line. It models the events into an Open Event Data Model (described below) and automatically publishes them via a JSON API.
The OpenCivic distro of Drupal is designed to support communities of software developers in creating, cataloguing and sharing software applications. It provides a platform for sharing information specifically about "civic software" used by governments and nonprofit organizations to provide public services. The main goal of this distro therefore is to help build websites that enable people to share information about software applications — what they do, who created them and uses them, where they have been deployed, and how well the software works.
This profile installs a site with the structure, content, permissions, etc of Drupal.org to facilitate the reproduction of bugs and testing of patches for the project modules. See What theme and modules does Drupal.org use? for the complete list.
git clone --branch 6.x-2.x http://git.drupal.org/project/drush_make.git
Enter the following to install the profile at a Drupal root of /var/www/mydrupalorg (this installs a copy of Drupal core and all necessary modules all at once):
drush make http://bit.ly/gOT8mp --prepare-install --working-copy /var/www/mydrupalorg
(Note: could take 3 minutes or more before any output appears)
It's possible that apachesolr's SolrPhpClient library may have been put in the wrong location. If it's in /var/www/mydrupalorg/profiles/drupalorg_testing, move it to /var/www/mydrupalorg/profiles/drupalorg_testing/modules/apachesolr
When the site and this installation profile are fully matured (sometime in 2008, the day of action is more like a month or year of action), this will be an installation profile for a multilingual site with map integration and features for proposing actions, communicating and collaborating about actions in onsite with e-mail groups, and listing and finding actions around the world.
DrupalMU was intended as an installation profile that creates a multi-user blogging platform. It is now replaced by hosted solutions like Drupal Gardens and installation profiles like Drupal Commons and Aegir.
This is a very simple install profile. You can use it to copy a site from your dev server to your deployment server. It reads the SQL file query by query (split by ";" at the end of lines) so it shouldn't run out of memory, or time-out (like PHPMyAdmin will on big dumps if you upload them)
You need to create a PHPMyAdmin dump (or mysql dump, if you know what you are doing) of your running site.
Projectverse is an installation profile for creating a Drupal-based project management extranet. It currently uses Drupal core, CCK, Views, Organic Groups, Case Tracker and other helper modules to create a groupware environment.
Most of the functionality and design philosophy behind Projectverse is drawn from an existing groupware site (code-named Project Central) that has evolved over time to meet the needs of Drupal services firms and their clients.
It is implemented as an install profile, which a user can choose upon installing a new instance of Drupal. Upon completion of the basic site configuration information, the user is given a change to select multiple 'Packages' which can define multiple tasks, forms, and modules to enable. The installer than walks the user through each step of each package, presenting forms and updating the status of installed packages.
Behind the scenes
Each package consists of a packagename.inc file located in the packgr/packages directory. This file contains two hooks, one to define the info about the package, and another to define default tasks and their callbacks. Please look at the Default package included with packgr for more examples.
Project Management is something which helps all projects run smoothly. I personally resent having to pay good money to companies who host poor solutions. This is what spawned the idea of a Project Management profile for Drupal.
I have currently taken inspiration from a few pages around the web such as: