Use Drupal to empower your OSS project community


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Use Drupal to empower your OSS project community
# 1  
Old 03-07-2008
Use Drupal to empower your OSS project community

Fri, 07 Mar 2008 09:00:00 GMT
When I started my tenure as marketing lead for the Haiku project in 2006, my highest priority was to renovate the project's Web site. Haiku had been using a custom-coded site which was showing its shortcomings as the project and the community grew in size. The admins wanted a new site that was easy to add content to and maintain, preferably based on an open source content management system (CMS) with a proven track record. The Web team chose Drupal 4.7 for the task. After working with the web team and a few other contributors for a few months, I built Haiku a new Web site that included not only more content, but most importantly more participation from the community. A few months months ago, when I helped start a Haiku user group in the San Francisco Bay Area started, I set up the NORCAL-HUG Web site using Drupal 5.0. In both cases, I learned how to use Drupal as a tool to empower communities, so that they become more participative and engaged in your project.


Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. AIX

Community Project AIX - All Intricacies eXplained

Hi everybody! In general the documentation of AIX is well done and rather complete. Still, there are a few undocumented parts of AIX and some of the undocumented commands offer things you just can't get done the "official" way. We once talked about collecting the information we collectively have... (0 Replies)
Discussion started by: bakunin
0 Replies

2. News, Links, Events and Announcements

A new project was posted on The UNIX and Linux Forums project board.

A new project was posted on your project board. Project title: Bash Shell Tutoring Estimated Budget: $50/hr Start date: Immediately Required skills: Linux, Bash, Shell, UNIX I work as a datawarehouse designer and developer. Although I usually stick to the role of an analyst,... (0 Replies)
Discussion started by: Neo
0 Replies

3. Solaris

SSH doesn't pick up user's project from /etc/project

We have a system running ssh. When a user logs in, they do not get the project they are assigned to (they run under "system"). I verify the project using the command "ps -e -o user,pid,ppid,args,project". If you do a "su - username", the user does get the project they are assigned to (and all... (2 Replies)
Discussion started by: kurgan
2 Replies
Login or Register to Ask a Question
DRUSH(1)						      General Commands Manual							  DRUSH(1)

NAME
drush - shell scripting interface for Drupal SYNOPSIS
drush [options] command... DESCRIPTION
drush is a veritable Swiss Army knife designed to make life easier for those of us who spend some of our working hours hacking away at the command prompt. Drush core ships with lots of useful commands for interacting with code like modules/themes/profiles. Similarly, it runs update.php, exe- cutes sql queries and DB migrations, and misc utilities like run cron or clear cache. OPTIONS
-r path, --root=path Drupal root directory to use (default: current directory) -l uri, --uri=uri URI of the drupal site to use (only needed in multisite environments) -v, --verbose Display extra information about the command. -q, --quiet Hide all output -d, --debug Display even more information, including internal messages. -y, --yes Assume 'yes' as answer to all prompts -s, --simulate Simulate all relevant actions (don't actually change the system) -p, --pipe Emit a compact representation of the command for scripting. -h, --help A detailed help system, use drush help help for complete help. --version Show drush version. If you get tired of typing options all the time, you can add them to your drush.php alias or create a drushrc.php file. These provide addi- tional options for your drush call. They provide great flexibility for a multi-site installation, for example. See example.drushrc.php. COMMANDS
Drush is all based around "commands" that are usually defined in various modules. help Print the help message. Use --filter to limit command list to one command file (e.g. --filter=pm). cache-clear (cc) Clear a specific cache, or all drupal caches. core-cli (cli) Enter a new shell optimized for Drush use. core-cron (cron) Run all cron hooks. core-status (st) Provides a birds-eye view of the current Drupal installation, if any. php-eval (eval) Evaluate arbitrary php code after bootstrapping Drupal. updatedb (updb) Apply any database updates required (as with running update.php). variable-get (vget) Get a list of some or all site variables and values variable-set (vset) Set a variable. watchdog show Shows recent watchdog log messages. Optionally filter for a specific type. pm-enable (en) Enable one or more extensions (modules or themes). pm-disable (dis) Disable one or more extensions (modules or themes). pm-download (dl) Download projects from drupal.org or other sources. pm-uninstall Uninstall one or more modules. pm-updatecode (upc) Update Drupal core and contrib projects to latest recommended releases. pm-update (up) Update Drupal core and contrib projects and apply any pending database updates (Same as pm-updatecode + updatedb). sql-cli (sqlc) Open a SQL command-line interface using Drupal's credentials. sql-connect A string for connecting to the DB. sql-dump Exports the Drupal DB as SQL using mysqldump. This manual only lists a few of the most frequently used builtin commands shipped with the Drush core, since other Drupal modules and third-party "command files" may extend this list significantly. The canonical source of information for the available commands and their usage is the online help system. More information on each command is also available through drush help <command>. Most commands have shortcuts indicated in parenthesis. FILES
/etc/drush/drushrc.php /usr/share/doc/drush/examples/example.drushrc.php SEE ALSO
cvs(1), svn(1), wget(1). AUTHOR
Drush was originally developed by Arto for Drupal 4.7 (this alpha code can still be found in the DRUPAL-4-7 branch). In May 2007, it was partly rewritten and redesigned for Drupal 5 by frando. Since 2008, the module has been maintained by Moshe Weitzman, Owen Barton and Adrian Rossouw. This manual page was written by Antoine Beaupre <anarcat@debian.org> in June 2009 for the Debian project (but may be used by others). January 11, 2011 DRUSH(1)