A forum module.

Make Orchard compatible with Mono.

Simple publication workflow that enables the definition of the publication workflow for a given container or content type. The workflow itself defines what roles can create, edit & publish, and also how many validations are necessary at each validation step.

Create mobile versions of a site.

Management of lists of users, self-subscription to mailing-lists, bulk sending of e-mail, e-mail templates. Public lists where all users can post are out of scope: this is one to many.

Event management and content type, presentation of said events as lists and calendars.

Ability to remove a module and all signs it ever existed, all associated database and settings entries.

Support RTL languages (Hebrew and Arabic) and Bidi rich text editing.

Integration of video into the media gallery.

Detailed usage statistics, referral information, clicks, etc. and associated reporting.

To admin user roles and access levels for each tenant site from the main 'host' site.

Manage friend relations, enable content item sharing between users.

Currently (version 1.0.20.0) Orchard does such things as store database connection strings (including user IDs and passwords) in plain text.

Many orginazations need increased levels of security such as ecommerce (PCI compliance), healthcare (HIPPA) and public companies (SOX compliance).

It would be essential to such applications that Orchard be built with Microsoft's security best practices baked in at all stages of development.

Unfortunately security is not something that can be "bolted on" after the fact like a module. That is why this is being proposed as a core principal for the entire project.

Content item revision management, wiki markup.

Post content items to external social networks.

Create polls, manage multiple voting, display results.

Orchard Visual Studio extension that allows to create modules, controllers, etc ...

Currently there are no helpers in Orchard for easy creation of Ajax-enabled forms in custom widgets and parts, but there really should be some...

Customer Relationship Management.

Provide a way to deploy content items from one Orchard installation to another. E.g. deploy content from a Development environment to a QA environment and then to Production.