I've been watching this project with great interest, so I'm curious about what's going on now that there has been a month of inactivity. I know that you guys were planning on getting some baseline code written before you open it up to collaboration. Is that still the plan?
I also know that stuff you don't get paid for simply falls down the list in terms of priorities. That's to be expected. Still, I'd love to know where things currently stand! I have a few projects going right now where we're seriously considering using CiviCRM, and I'd really prefer not to.
Warmly,
Lucas
Comments
Comment #1
seanberto commentedHi Lucus,
Sorry for the delay. I've been out of town. Thanks for your understanding about how open source projects like this progress too. The reality is that things are moving more slowly than we would like, but we're still very committed to the project. If you are going to need to choose a production-worthy CRM in the next month or so though, I'd pry stick with CiviCRM or Salesforce.
-sean
Comment #2
seanberto commentedComment #3
ldweeks commentedGot it. But what about opening things up to collaboration from the community? I resurrected this thread recently and immediately got a number of hits. That post is coming from the perspective of church management software, of course, but I consider that as a subset of CRM software. Point is that I and others may be willing to put time and energy into this space over the next few months, and I'd rather not duplicate the fine work you folks are doing.
I understand why you'd like to keep things in-house for a while, and I understand why you wouldn't want to take on the burden of trying to shepherd a community project with people you don't know. No problem. But what if we took the code that you have already written and use it as a starting point? Would you be willing to review patches if we submit them to the issue queue, or is it too early for that, even?
Thanks again.
Comment #4
zkrebs commentedimmensely excited for a real drupal crm with sales/marketing stuff in it
Comment #5
sea4 commentedi agree,
we too need to choose a CRM very soon, and this project has excite us. :-)
Comment #6
mgiffordOk, so just to know how we can jump in to help here.
You've got a bunch of modules in git already. Does this get you something better than a WSOD?
Are you looking for more contributors?
Comment #7
WilliamV commentedVery excited as well as this CRM could integrate with Drupal Commerce and fulfill client automatisation.
Grtz.
Comment #8
seanberto commentedHi Folks,
First off, thanks for the continued interest in CRM in D7! I'm assuming that all of you are involved in the more general CRM discussion for D7 here: http://groups.drupal.org/crm-api. (If not, you should follow it!)
So, here's the scope: The summer has turned out to be more slammed with projects than we'd hoped. So, not as much work has been happening with RedHen as we'd hoped. Progress is being made, but on more diverse fronts. Shomeya's been doing a lot of work with Addressfield. ThinkShout has developed an event registration system similar to D6's sign-up module but leveraging Fields. ThinkShout has also just released an alpha of its MailChimp STS module (http://drupal.org/project/mailchimp) which is a great step towards the creation of a robust bulk email tool (with click-through and delivery tracking) w/in Drupal.
The pieces are coming into place. But our work has been a bit scattered.
We still feel really strongly about this work. The project is far from dead. But we don't have a timeline for the project at the moment. There is a chance that we'll get a client project this summer that will pull all the development in tighter. I'll keep you posted.
Cheers,
Sean
Comment #9
joekrukoskySub
Comment #10
chriscohen commentedHmm, not sure how I missed this! There is already a project dedicated to making a full blown CRM happen in Drupal! As mentioned above there is a lot of work on http://groups.drupal.org/crm-api.
This project seems like a duplicate effort, so I think it would be beneficial for everybody to work together on a single CRM rather than separately. There is currently a call for participants for a code sprint at DrupalCon, at http://tiger-fish.com/blog/drupal-help-bring-drupal-crm-life-drupalcon-l...
What do you guys think to this? Did you already know there was a project to create a Drupal CRM before starting this?
Comment #11
seanberto commentedHi Chris,
Thanks for reaching out - and more importantly for helping push the community's collective work around a native CRM in Drupal forward.
Yes, we are aware of the CRM API work. (See: http://groups.drupal.org/node/134789). When we started RedHen, we hadn't seen much progress in the CRM API group. I believe the issue was that that group was waiting to see how a few things panned out with Drupal Commerce. Since then, we've had some other projects kick up that have slowed down our own progress on RedHen. Indirectly we've developed a lot of code around event sign-ups and bulk email that could support RedHen (or any other CRM implementation), but we need some additional time to get this work out the door as a contribution.
In short, we need to make some decisions in the next few weeks internally about how we can best help move CRM forward. You're right that it doesn't make sense to duplicate effort. There are some really, really smart minds in the CRM API conversation. And it's very possible that we need to fold our effort into the CRM API work. At the same time, as we've seen with Drupal Core development (and more importantly, Drupal Core architecture debates and issue queue management), it's sometimes hard to develop big feature sets "by committee". If we look at Ubercart, for example, we see that some of the large contributions to Drupal are often lead by one or two shops. Also, if you look at the work done in the Drupal mapping space, there's also sometimes a benefit to work being done in parallel tracks.
I think that this conversation needs to continue. I think that we'll have a better answer for you soon. Is that a fair answer? Perhaps we could chat a bit more either on this ticket or on a Skype call? Again, it's really great to connect with you.
Thanks!
Sean
Comment #12
nottaken commentedSubscribe
Comment #13
chriscohen commentedSean,
There is no code for the Drupal CRM project but this will be rectified by the end of DrupalCon. The basic architecture is found at http://groups.drupal.org/node/89779 although this is a guideline and I'm sure this will evolve.
In general, the discussion has been at http://groups.drupal.org/crm-api as mentioned above. However, the Drupal 'web-o-sphere' is woeful at providing places for discussion, and g.d.o itself is a confusing mess and not at all appealing to use.
My hope is that once the first code is laid down (it doesn't matter if this code is completely rewritten later, or if we have 5 versions of code doing the same thing initially), we will commit this to the CRM project and use the issue queue for discussion.
I do however feel the need to create a 'manifesto' or something similar to outline the goals for the project, such as defining a particular meaning of the term 'CRM' (since it's different things to everyone) and an overall scope for the project. This can come later though, once more momentum has been built up.
Comment #14
seanberto commentedChris, That sounds great. Can't wait to see what comes out of London!
Comment #15
zeezhao commentedHi - please is there any update on this?
Comment #16
yautja_cetanu commentedJust thought I'd post a link here: http://groups.drupal.org/node/179339#comment-595384
I was kind of replying to the discussion here and on the group in one.
Comment #17
seanberto commentedI think that the following post provides a pretty solid update on our work towards features for RedHen: http://groups.drupal.org/node/179339.
Comment #18
seanberto commentedUpdating this ticket to let folks know that we're in active development. We're currently developing RedHen for 3 clients - and as such we're using an internal Chili project for ticketing. We are mirroring code to D.O. however. The code that's up there now is actually pretty darn stable. It's very far from complete - but you can create contacts and organizations, create connections between them, do some basic filtering, etc.
Comment #20
seanberto commentedFurther updates. RedHen is in Alpha2 at the moment, with a Beta release scheduled to be released at Capital Camp in DC at the end of July, 2012.