# Summary

RedHen is a Drupal-native CRM initially designed for common nonprofit needs, but built for flexibility. It has classic CRM functionality for managing information about contacts, organizations, and their relationships between each other and your organization (like memberships). It also knows some modern tricks (like engagement tracking) and customizable one page donation forms, and stuff you'd hope for in a website-integrated CRM (like event registration integration).

A working Alpha release is available on the project page, and includes Contacts, Orgs, and Connections modules in working order. Major development pushed primarily take place on github, but the Drupal repository is kept up-to-date.

# Project URL

https://www.drupal.org/project/redhen

# Where is the code?

8.x-1.0-alpha3
Primarily on GitHub: https://github.com/thinkshout/redhen/tree/8.x-1.x

# Estimated completion date

Initial version with Contacts, Organizations, and Connections is available now in an alpha release. A more feature-rich beta is planned for late summer of 2017, including Notes, Membership, and Activity submodules. Engagement and Dedupe modules are planned for future releases.

# Dependencies

No dependencies beyond core modules. (Entity, Field, Views)

# Who's doing the port?

ThinkShout on behalf of our clients.

# What help do they need?

Additional testing is always needed: especially automated tests.

# D8 roadmap

Not yet available.

Comments

tauno created an issue. See original summary.

tauno’s picture

Issue summary: View changes
levelos’s picture

Status: Needs work » Needs review

Made initial alpha release and in use on production sites.

reptilex’s picture

so how far are you from a beta, even better a stable release? What is missing, what has to be done?

gcb’s picture

The heart of RedHen -- Contacts, Orgs, and Connections -- is quite functional. It is currently in use on active sites. The alpha2 is very usable if you do not need any of the other RedHen submodules. We have debated releasing the current functionality as a Beta, but we are looking to add some additional submodules in the next 3-6 months and would prefer to have the Beta feel more functionally complete.

Submodule status:

  • Activity - We would like to include this in the Beta
  • Dedupe - Not planned for Beta Ready for Beta (thanks to @arosboro)
  • Engagement - Possible for Beta
  • Fields - Obsolete, functionality included in Alpha
  • Membership - Would like to include in Beta
  • Note - Planned for Beta
  • Relations - Replaced by Connections, already functional in Alpha
gcb’s picture

Issue summary: View changes
bgronek’s picture

It looks like there is a lot of great progress on this D8 port! Thank you! A review of the issues seems like we are not far from beta on this project. Is that the case?

Thank you all for your contribution on this effort.

gcb’s picture

We have a high standard for our betas, but I think we're getting close. I have some items in mind that I'd like to cover before we get there, and will try to get some tickets in for them so it's more transparent (and folks can help!), and I'll check in with the rest of the core team here to see what others are thinking.

gcb’s picture

(That said, we are using D8 Redhen in production on multiple sites at this point without issues.)

mmjvb’s picture

Issue summary: View changes
bgronek’s picture

Thank you!

mmjvb’s picture

Issue summary: View changes

In the mean time alpha3 arrived.

skyredwang’s picture

It has been a while since alpha3, I was wondering if someone from the core team can share a little bit more progress?

sealionking’s picture

any update about beta?

gcb’s picture

We've got a couple tickets that we really want to get sorted out before releasing a beta, and our current plan is to get this work done in Q1. I realize it's been pretty quiet on the update-front, and I assure you all we are still here! Are there any particular tickets or issues that those looking for a Beta are hoping to see resolved in that Beta?

jptillman’s picture

Is it reasonable to assume that this effort is stalled or perhaps even dead? No update in nearly a year, and the github repo hasn't seen a commit since 2018. I'm evaluating a D8 solution between RedHen and CiviCRM. There's much more activity on the CiviCRM side to get up-to-date.

gcb’s picture

It's hard to argue with your analysis!

Stalled is accurate. We will likely be resuming work on this project in the next year (we will be using it for new projects ourselves), but I can't promise there will be major feature enhancements in the works. Some features, some stability.

RedHen and Civi are pretty different approaches. If you want to build your CRM in Drupal, using Drupal fields for data and Views for reports, etc, RedHen works for that (despite the "alpha" designation). If it would make a significant difference in your decision making for us to roll a new release (I was waiting on 1 specific ticket before rolling a beta), I will be tempted to find some time to do it. Feel free to contact me directly on my contact form if you have other questions or want to discuss concerns.

jptillman’s picture

My main concern was keeping up with Drupal 8, which seems to be making it difficult for even well-maintained modules to keep up with API drift. It looks like your feature set is pretty close to what we'd need. We have been using Civi for years now, but I'm really getting tired of dealing with a bolt-on that will always be running side-by-side with Drupal.

If it's possible to deploy successfully from your Git repository, I wouldn't need a new release to get some preliminary evaluation testing going. I was just looking for assurances that there were still signs of life.

gcb’s picture

Redhen lives!

I hear you about the API concerns. We have actively maintained client sites using the module, so keeping up with the API changes is certainly on the radar.

The issue queue is not closely watched these days, (it's just a time issue right now), but feel free to draw my attention to any key issues in the issue itself or via direct message. I totally understand the frustration with bolt-on solutions.