Building a CRM system that is flexible enough for everyone, yet supportable for the long haul is a pretty big challenge. There are several different development initiatives, each with a different perspective on the problems, and each with a different set of developers.
In the interest of forward progress, we've agreed that it is OK to continue developing these projects independently, even though they might duplicate or even conflict with each other. But each of these developers values the idea of coming together to find common ground and areas for collaboration. There is a regularly-scheduled meeting for CRM developers to discuss their progress and ideas.
Everyone: If you are interested in following the progress of these CRM projects, please join the CRM group on groups.drupal.org. Announcements, invitations to test new releases, and other end user-oriented updates will be posted here.
Developers: Please join the CRM group and the CRM API group. This will help you understand and participate in conversations about users needs, and also give you a place to comfortably discuss parties and entities and API's and use other foul-sounding language as you see fit :). If you are actively working on a project and would like to start collaborating with other CRM developers, please add/update your project status on this wiki and join the regular calls.
We try to keep this section up-to-date as a definitive current state of each project.
Party Module:- This iniative has a "party" entity which is just the generic entity for "stuff" in the CRM. A Party can be an individual, organisation, family, etc. It is using the Profile2 module to store all the data. Whilst Parties can be related to a user they do not have to be. We are currently working on building views to view this information and working on the concept of Data Sets and Party Pieces [#1302682]. The next step is Party Hats are different types of individuals (Teacher, Developer, Student) that can be both placed on a party and taken off later. Most of the work here is conducted by Joachim and rlmumford although CaptainDav is about to get involved.
Development on this project can be found here: http://drupal.org/project/party
Contact Module:- This is an fully entity-based approach to CRM. There is a contact entity where fields can be attached to it like any other entity. A UI has been fleshed out to view contacts, add contacts and create multiple contact types. Everything in this iniative is based on revisions and so changes to data is also stored. Currently they are working on "activities" so that different methods of interacting with contacts (such as a phone call) can be recorded.
Development on this project can be found here: http://drupal.org/sandbox/citizenkane/1260982
Red Hen CRM:- RedHen CRM is similar to CRM Core in that it bundles its own custom entity types for contacts, organizations, and affiliations. It provides a set of developer tools and APIs for building custom CRM solutions. The feature set is largely based around "association management" needs. It provides tight integration with the Entity Registrations module. It also ships with "groups" functionality similar to Organic Groups, as well as an "engagement scoring" feature. A sandbox install profile can be found at: http://drupal.org/project/redhen_demo. You can learn more at: http://thinkshout.com/blog/2012/06/sean/redhen-crm-part-1