Seeking co-maintainer(s)

The User Import Framework (uif) module provides simple, extensible user import via CSV (comma-separated value) files. The guiding philosophy is to make the import process as simple as possible for the end-user (the user doing the import). Hooks allow the developer (you) to add the bells and whistles you need, e.g. content_profile (D6), core user fields or profile2 (D7) support, while providing a framework which takes care of the tedious aspects of the job (forms, input parsing).

This module allows you to control anonymous commenting per node type via the node type edit screen once anonymous user is given the 'post comments' permission.

This module makes it easy to add Open Graph meta tags (http://opengraphprotocol.org/) to a node to enable it to be come a "rich" social object. For instance, Facebook uses this information to work out how to preview shared content in a user's Facebook profile (http://developers.facebook.com/docs/share).

This module provides pages and blocks that integrate with Apache Solr to search specifically by content type.

Features

The modules provides the following features:

This module is intended to allow integration of Moxicode's Imagemanager and Filemanager into the WYSIWYG module.

The module currently only supports TinyMCE.

Your variable table can get bloated under three circumstances:

The Deny Access module (Drupal 7 only!) allows overriding access granted by other node access modules and/or core. It uses the node access system but not the {node_access} table, and so if you don't have any other node access module installed, then it does not carry the typical overhead. The downside is that it will not work to guard against showing lists of nodes, like lists created by the Views module or the front page. At this point it's a very simple module.

Deny Access provides the following global 'permissions' on the Permissions page, admin/people/permissions#module-deny_access:

• DENY accessing any content
  Override content view access (to single nodes!) granted by other modules.
• DENY creating any content
  Override content create access granted by other modules.
• DENY editing any content
  Override content edit access granted by other modules.
• DENY deleting any content
  Override content delete access granted by other modules.
• DENY access per content type
  Generally override access (to single nodes only!) for a specific content type.

This is a very simply module which allows you to define CCK fields for content types which display terms for each given node. Each field you add is "read only". This means there is no addition to the node add/edit form. It just grabs the terms associated with a node and allows you to output them either as inline or block elements (in each case either as plain text or as a hyperlink). If you use one of the inline formatting options, you get a nice "a, b, c and d" style list.

A stripped down version of the Theme Developer Module.
All the theme information are written in html comments - so no sexy javascript or the trillion of span tags in the markup, that should make it easier to read.

Relation is an API module and storage model for both simple and the most complex relations between entities. The module can handle both directional and symmetrical relations very well.

Relations are entities and can therefore have fields. This makes Relation the most flexible and powerful relation model out there. (Still, using Relation with anything but the default SQL storage will not work in most cases.)