Seeking co-maintainer(s)

Conditional Text module for Drupal

This module adds a text filter called "Conditional text" to your site. The conditional text filter allows you to write content for your site that contains sections that are displayed or hidden depending on certain conditions, allowing you to write content that can be used in different situations or for different audiences. For example, if you are writing software documentation, you might want to write content explaining how to use a particular feature, and include certain sections that apply to one version of the software, and other sections that apply to another version. If you were displaying this documentation to a user of one version, you would hide the inapplicable information from the other version. This allows you to avoid duplicating the content (which makes it more difficult to maintain) -- instead of writing a different manual for each version, you write one version with conditional sections.

The URL ID module provides a field that gives an entity a 'global' ID, based on the domain name, entity name and entity id (such as http://example.com/node/1).
The idea is that remote entities can be downloaded, inheriting the remote URL ID – a node could have the URL ID 'http://example2.com/node/123'.

The Lazy URL ID Reference module provides a lazy-loading reference field, utilizing URL IDs. The idea is to refer to a URL ID such as 'http://example2.com/node/123'. If there is a local entity with this URL ID, the reference field will point to it (eg. node/456), if not, it will point to the remote source (eg. 'http://example2.com/node/123').
Furthermore, URL ID fields have fetchers – plugins that allow fetching remote data and saving it locally. These fetchers can also affect the reference link, for example by automatically download the referenced entity, or to redirect to the remote source.

This is a work in progress. It is related to a project for being able to download and sync help pages from drupal.org to your local site. See the following links for more information:

* Specification/wish list for better help system: http://drupal.org/node/1095012
* Better help system for Drupal 8: http://drupal.org/node/1031972
* Want the ability to create multiple outlines/maps: http://drupal.org/node/995370

This is a GSoC 2011 project: Derivatives API for Media ecosystem (D7).

The goal of this project is to implement Derivatives API for Media Library (Media, Styles, ...) ecosystem in Drupal 7. This API will provide a flexible, extensible and abstract API to implement derivation engines for different types of files.

• Project wiki
• Project proposal

This module is still under heavy development and should not be used in any production environment!

Info for plugin developers

Derivatives API currently introduces 4 types of plugins, that can be implemented in 3rd party modules to extend API's functionality. API's rough structure should be fixed at the moment, but some changes could still happen. You can contact me if you start working on a plugin module and I will communicate with you about the planned changes. Any suggestions on how to make this API better are also welcome.

You can find some developer resources in module's API reference and on blog post where I explain API structure.

Please note that this module is minimally maintained and seeking a co-maintainer

This module pulls in Open government data from a Microsoft Open Data server, via it's API and then outputs it to screen in a nicely formatted table and map.

An example can be seen here - http://www.datadotgc.ca/dataset/location_of_historic_buildings_in_edmonton

Here's the text from the README.txt file of the module

What is OGDI? - http://www.microsoft.com/industry/government/opengovdata/

Module development was sponsored by Microsoft Canada and Raised Eyebrow Web Studio (http://www.raisedeyebrow.com).
Module developed by Colin Calnan @ Raised Eyebrow Web Studio

The OGDI Field Module allows you to add a CCK field to any content type, which accepts a valid URL to a OGDI dataset as input, and outputs a slick, themed scrollable, filterable, sortable, searchable table and a map displaying that data. It does all this magic by communicating with the OGDI API.

OG Forum fixes for SA-CONTRIB-2011-004

Note: due to lack of time, I'm looking for a new-maintainer for this module.

This project integrates Drupal with Recurly, a subscription billing service that takes the headache out of subscription management. It can work in conjunction with your existing payment gateway or merchant account (see the list of supported payment gateways) or you can use the included Recurly Gateway (which is included free with all accounts).

This project includes a few sub-modules that allow users to choose how deeply they wish to integrate their Drupal site with Recurly:

• Recurly: The main Recurly module provides basic Drupal integration, including receiving push notifications from Recurly.com. It also includes built-in pages for users to view invoices, subscriptions, and to upgrade/downgrade their subscription level.
• Recurly Hosted Pages: Rather than hosting account management yourself, you can use Recurly.com to handle all aspects of subscription management through their hosted pages option. This requires the least amount of integration with Drupal, thus the least responsibility for customer data. Recurly's hosted pages are PCI-DSS Level 1 compliant. Sites using this solution will still need to comply with the shortened self-assessment questionnaire (SAQ-A) to meet PCI compliance on their own site.
• Recurly.js: Recurly provides a client-side credit card authorization mechanism called Recurly.js that interacts with the payment gateway through JavaScript. Because the credit card information is not processed by your server, your responsibility is dramatically reduced. Like the Hosted Pages solution, you may achieve PCI compliance through the shortened self-assessment questionnaire (SAQ-A). This approach allows users to make payments from within your site but with the least responsibility possible.

For more information about Recurly and PCI-compliance, see the Recurly documentation on PCI-compliance.

This module uses Recurly's PHP client library to provide various points of integration with Drupal.

Here's a blog post with details on getting started with this module and Recurly.js: Integrating Recurly and Drupal. And a blog post on testing Recurly webhooks locally: Testing Recurly Webhooks with Ngrok.