So Matt, I'm unclear on whether your vision for Drupal CRM and work on it involves integrating with and leveraging CiviCRM or redeveloping from the ground up, or maybe both. <br><br>In the short term I am interested in allowing Drupal's goodness as a dev framework to supplement the user focussed built-in functionality of CiviCRM. <br>
<br>Creating a data layer in Drupal to access CiviCRM's database is a great start, since this will presumably enable stuff to built on top of it. D7's shift from node to entities and other more generic standards like a Schema, EntityController, etc will avoid the ugliness and waste of things like synching up CiviCRM with copies in Drupal nodes, or membership in an OG and a CiviCRM group. <br>
<br>In the medium and longer term there may some ability to share efforts between a Drop CRM and CiviCRM. However, at the moment I see a fair degree of divergence. Drop is oriented towards a commercial rather than non-profit organization. All CRM's share a great deal of functionality, however, and there are benefits to having a larger install base and developer community for an open source software project / install profile. For example, Convio has reskinned and extended SalesForce.com for the non-profit world in its Common Ground SaaS offering. The second area where I have trouble imagining a full convergence is that CiviCRM supports Joomla as well as Drupal. I have trouble imagining Joomla folks wanting to have a Drupal as well as Joomla install on their system.<br>
<br clear="all">Joe Murray, PhD<br>President, JMA Consulting<br><a href="mailto:joe.murray@jmaconsulting.biz">joe.murray@jmaconsulting.biz</a><br>skype JosephPMurray twitter JoeMurray<br>416.466.1281<br>
<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Date: Sat, 8 May 2010 17:19:27 -0700<br>
From: Matt Chapman <<a href="mailto:matt@ninjitsuweb.com">matt@ninjitsuweb.com</a>><br>
Subject: Re: [consulting] CiviCRM comments (Re: CiviCRM / Drupal<br>
integration expert)<br>
To: "A list for Drupal consultants and Drupal service/hosting<br>
providers" <<a href="mailto:consulting@drupal.org">consulting@drupal.org</a>><br>
Message-ID:<br>
<<a href="mailto:z2v80badb991005081719hbec42985z795536efd2df9fd6@mail.gmail.com">z2v80badb991005081719hbec42985z795536efd2df9fd6@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
On Thu, May 6, 2010 at 10:56 AM, Donald A. Lobo <<a href="mailto:lobo@yahoo.com">lobo@yahoo.com</a>> wrote:<br>
> * As matt has mentioned, we do think talk is silver, code is golden.<br>
<br>
Here's some code:<br>
<br>
git clone git://<a href="http://github.com/matt2000/profile.git" target="_blank">github.com/matt2000/profile.git</a><br>
<br>
(make sure you're getting the 'civicrm' branch -- i'm new to github<br>
and not sure how to direct you beyond that.)<br>
<br>
I would NOT call this a proof-of-concept. Merely a silly Saturday<br>
experiment. On install, the profile2_civicrm module reads the<br>
Contact.xml database schema definition from CiviCRM, and creates the<br>
fields using Drupal 7 Field API on the Profile2 'main' profile entity.<br>
<br>
In reality, this is almost definitely the wrong thing to do; we'd<br>
probably want to create our base tables with Schema API and add an<br>
EntityController (both of which can also be automated from CiviCRM's<br>
XML, if it seems like a good idea to do so.) Field API would be used<br>
just for adding 'custom' fields to our Entities. But I already know<br>
how to use SchemaAPI and wanted to practice more with Fields, so this<br>
was my exercise for the day.<br>
<br>
You can see here a roadmap for the kind of code work I think is needed<br>
to get Drupal CRM off the ground:<br>
<br>
<a href="http://www.dropcrm.org/" target="_blank">http://www.dropcrm.org/</a><br>
<br>
Please forgive the rough start there; we're just starting to get<br>
organized. Feel free to jump in and help flesh out ideas; all pages<br>
are wiki'd. Let's be realistic; we're not going to have a release in a<br>
month. A year or more to 1.0rc is not an unreasonable expectations.<br>
But based on the discussions I've had since DCSF, there are more than<br>
enough people who know that it's time to start breaking the dependency<br>
on external systems in order to build the best possible CRM for<br>
Drupal.<br>
<br>
For more golden code & places to help out, see:<br>
<br>
<a href="http://drupal.org/project/profile2" target="_blank">http://drupal.org/project/profile2</a><br>
<a href="http://drupal.org/project/entity" target="_blank">http://drupal.org/project/entity</a><br>
<a href="http://drupal.org/project/issues/views?text=&status=All&priorities=All&categories=All&version=7.x&component=All" target="_blank">http://drupal.org/project/issues/views?text=&status=All&priorities=All&categories=All&version=7.x&component=All</a><br>
<a href="http://drupal.org/project/issues/date?text=&status=Open&priorities=All&categories=All&version=7.x&component=All" target="_blank">http://drupal.org/project/issues/date?text=&status=Open&priorities=All&categories=All&version=7.x&component=All</a><br>
<a href="http://github.com/Vertice/features" target="_blank">http://github.com/Vertice/features</a><br>
<a href="http://github.com/damz/postaladdress" target="_blank">http://github.com/damz/postaladdress</a><br>
<a href="http://github.com/drupalcommerce/drupalcommerce" target="_blank">http://github.com/drupalcommerce/drupalcommerce</a><br>
<br>
<br>
All the Best,<br>
<br>
Matt Chapman<br>
Ninjitsu Web Development<br>
<br>
--<br>
The contents of this message should be assumed to be Confidential, and<br>
may not be disclosed without permission of the sender.Message: 1<br></blockquote></div><br>