Gnomepal <-> Drupal Gap Analysis

As Gnomepal starts to cohere from "I wish Drupal did n" into a reasonable set of 1.0 requirements, it will be critical to assess how these requirements can be met by existing Drupal contributed modules and what's not there yet. This space will serve as a place where existing functionality can be mapped to desired functionality.

Here's a proposed format for this:

gnomepal requirements | candidate modules | contributed module functionality | gap | discussion

And here's a starter example:

Gnomepal Requirements:

• Community members need a means to create groups within their communities. -...

Candidate Modules:

• Organic Groups

Contributed Module Functionality:

• Enable users to create and manage their own 'groups'
• Each group can have subscribers
• Group maintains a group home page
• Group subscribers communicate with each other via posting the usual node types
• Groups may be open, require approval to subscribe or be invitation only
• Groups get their own theme, language, taxonomy.
• ...

Gap:

• ...

Discussion:

• Organic Groups has s rich family of modules designed to work with it. Perhaps the best approach would be to create one of these for Gnomepal that provides any functionality that is lacking and plays nice with OG and all the other children.

You get the idea...