Projects Needing Financing

Drewish has a reverse bounty going to add the ability to use external files with the audio module. This will allow you to have a remote store of MP3 or other audio files, and easily include them in your Drupal site, including in a Flash audio player, using the audio module.

See the Drupal issue tracker for more details: http://drupal.org/node/47998

Khalid Bahey is well on his way to getting a patch into Drupal 6 for spitting out logging of watchdog entries so that:
1. They can be routed to a different source other than the database, from a flat file to syslog support. The watchdog table can crush many sites.
2. Actions can be taken depending on the messages. Get notification via email, IM, pager, etc. depending on the severity levels of messages in your watchdog.

This will be a fantastic feature for Drupal 6....but really, we need it today for Drupal 5 as well. I've spoken with Khalid and he's willing to backport both the patch as well as the supporting modules. The plan of attack is:

Not too long ago, Google announced FREE processing of your Google Checkout sales until the end of 2007. That's right - more than a year's worth of free processing!

From now through December 31, 2007, you can process Checkout transactions for free, even if you aren't an AdWords advertiser. If you're already an AdWords advertiser, you can process your Checkout transactions for free regardless of your AdWords spend.

This potentially affects folks who use Drupal's ecommerce and advertising modules. Wouldn't you like to use Google Checkout (GC) for your Drupal web site(s)? Before that's possible, we need someone to create a module. Unfortunately, GC currently works ONLY in the United States. Regardless, I'd like to see a developer step up and write a membership subscriptions-based, recurring credit card charges capable module and I'd be willing to make a small financial contribution. Here's a short GC video demo, but please read on for more info.

In order to periodically update the reverse bounty status of Projects Needing Financing**, please refer to the table below.

The table is an informal list of Projects Needing Financing by the respective project maintainers/developers. If you are maintaining/developing a project with a reverse bounty and have knowledge on any of the column headers listed in the table for your respective project, please add your comment on this page so that your comment can eventually be included in the table.

Please read on for more info.

Thanks,
Walt Esquivel, MBA; MA; President, Wellness Corps; Captain, USMC (Veteran)
$50 Hosting Discount Helps Projects Needing Financing

Whether or not you need funding for your Drupal project(s), it would be good for all Drupal users to vote for Drupal. Your vote could, ultimately, help with any needed funding you and/or other developers require in order to complete a Drupal project. Voting is now open and ends on November 7! There is $5,000 up for grabs!

As mentioned in Packt's Open Source CMS finalists announced, it would be great if folks would
vote TODAY for Drupal as "the best CMS" and help Drupal claim the $5,000 first place prize. Did I mention $5,000? ; )

Cross-posting from http://drupal.org/node/77562 ...

We've seen explosive growth in 2005 and 2006 based the ability for Drupal sites to rapidly deploy new features that meet real world customer needs, not just fulfill technical requirements. This project aims to increase consultant and site administrators ability to effectively manage releases, security, versioning, issue tracking, and feature deployment into customer ready production environments. By directly improving the Drupal.org release and project management infrastructure we will speed up the life cycle for meeting customer and user requirements and ultimately improve the ability to manage Drupal web sites. Donating to this effort (via the PayPal link on the full proposal) provides funding to accelerate volunteer contributions the Drupal.org project maintainers have made over the past 8 months.

Overview

• Contributions will have real releases and version strings, just like Drupal core itself
• Security announcements will refer to exact versions of modules that are effected
• Issues will be tracked by the exact version number of the contribution where the bug is present
• Development branches for any given version of the Drupal core -- maintainers can add new features to their module or theme without endangering the stability of other code that is compatible with the same version of Drupal core.
• All contributions will be clearly identified with the version of Drupal core they are compatible with

For the rest of the proposal, please see the full post on drupal.org.