Problem/Motivation

Those interested in the CRM space are unaware of the CRM project.

Proposed resolution

Announce CRM in places where existing CRM users, developers, and other contributors already are, inviting them to collaborate on the CRM project.

Remaining tasks

  1. Identify additional places to post (list them below)
  2. Post in the identified places (blocked on #3522261: Improve project description and #3522273: Document CRM architecture)

Places to create an issue/post

CRM Core
RedHen CRM
Contacts
Party
CiviCRM Entity
g.d.o/crm
LinkedIn posts (seek amplification from TheDropTimes etc.)

Comments

jdleonard created an issue. See original summary.

jdleonard’s picture

Component: Code » Miscellaneous
bluegeek9’s picture

Status: Postponed » Active
bluegeek9’s picture

Issue summary: View changes

I reached out to CRM Core maintainer. I believe his focus is on CRM Core.

bluegeek9’s picture

bluegeek9’s picture

Status: Active » Postponed

We need documentation before we approach other projects.

#3522273: Document CRM architecture

bluegeek9’s picture

Assigned: Unassigned » bluegeek9
Issue summary: View changes
Status: Postponed » Active

I reached out to the maintainer who last committed to RedHen and Party.

We should only reach out to the Drop Times after a beta release of CRM

bluegeek9’s picture

Assigned: bluegeek9 » Unassigned
Status: Active » Fixed
//www.flaticon.com/free-icons/thank-you Thank you for your contribution! Your continued support makes this project sustainable.
There are multiple ways to show appreciation for the work contributed to this project including:
  • Triage issues and adding more context to existing issues.
  • Flagging CRM as a favorite on the project page to help others discover it and show your support.
  • Review the Developer Docs for accuracy and clarity.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.