Possible Roadmap

1.) Release Profile2 #d7cx
2.a) Help update Features Module and Views for D7
2.b) Help Drupal Commerce standardize postal address solution.
3.) Define CRM Object model - Entities and Relationships
4.) Identify architecture for Relationships (existing module)?
5.) Identify Architecture for entity inheritance/subtypes
6.) Create Contact Entity with support for profile2, relationships, subtypes, and user-binding. Release 7.0.1-beta
7.) Proliferate Features leveraging new entities.
8.) Create additional entities & relationships defined in (3), and revise (3) as needed.
9.) Release early, release often.
10.) Repeat from step 7.

Comments

An alternative approach would

An alternative approach would be to build a proof-of-concept with Drupal 6 CCK/Views/Features/(Ubercart?), while we wait for the pieces to be ready for Drupal 7.

Personally, I'd rather dive in help get D7 components going, but I eager to hear input from others on whether a D6 project is worthwhile at this point, even if it's nothing more than a prototype.

I think we should prioritize

I think we should prioritize 2b. This is an important foundation piece, and we need to coordinate with UC in order to get something that we can have in common.

I am thinking we should look at http://drupal.org/project/uc_addresses for a basis, and make a D7 address module that is independent of both Drop and DC, but is used by both. This gives us a reusable component, compatibility between Drop and DC, and also an on-ramp for all the sites that initially just want addresses but later may find they want more CRM features.

Just updating: The planned

Just updating:

The planned successor to uc_addresses is:

http://drupal.org/project/addressfield

The other key bit of possible

The other key bit of possible DC-Drop interaction is profiles.

IIRC Ryan recently said that it would be possible for anon checkout to not create a user account. This smells a lot like a profile! We should talk to him about whether it's possible to use common stuff here too.