C in CRM Stands for Community: The DevRel Way

### Overview In this talk, Anahi Manet discusses the intersection of Developer Relations (DevRel), Community Relationship Management (CRM), and community building within Open Source Program Offices (OSPOs). Companies frequently participate in open source by consuming software, contributing back to upstream projects, or releasing new open source initiatives to attract and retain talent. To handle legal, HR, and community needs, organizations establish OSPOs. While community building is often associated with project managers or marketing specialists, DevRel practitioners can provide critical value by establishing developer relationships and guiding community members along their lifecycle from users to maintainers.

### Key Topics - **DevRel Role and Alignment Challenges**: DevRel professionals operate under varied structures depending on whether they work for foundations or companies, whether products are open source, and which department they report to (such as marketing, engineering, or support). This departmental variation creates differing KPIs and makes measuring DevRel success complex. - **Developer Journey and Transitions**: A primary OSPO goal highlighted is transitioning community members from users (asking questions on forums or issue trackers) to contributors (answering questions and submitting changes) and maintainers (reviewing and accepting code pull/merge requests). - **Limitations of Traditional CRMs**: Traditional customer relationship management platforms are built around sales and marketing behaviors, failing to capture the distinct touchpoints, motivations, and platform interactions typical of software developers.

### Technical Details & Case Studies - **Cross-Platform Activity Tracking**: Developers rarely reside on a single platform; they interact across discourse forums, Slack channels, mailing lists, Git repositories (such as GitHub and GitLab), and chats. Understanding how an individual's presence shifts between these platforms indicates their stage in the developer journey. - **Case Study (Chef)**: Chef, a customer of Bitergia, evaluated community activity across Discourse, Slack, and GitHub. Chef tracked how users asking questions on Discourse or Slack eventually initiated contributions on GitHub, allowing the organization to allocate appropriate internal developer and support resources across platforms. - **Identity and Affiliation Management**: Community Relationship Management requires identity affiliation tooling to map disparate user accounts across multiple platforms to a single real-world contributor. The speaker highlights **SortingHat**, an open-source tool with a web interface called **Hatstall**, which manages contributor affiliations and organizational attributions. SortingHat is part of **GrimoireLab**, an open-source analytics platform developed under the Linux Foundation's CHAOSS project. - **Related Metrics Initiatives**: During the Q&A, the speaker references community metrics for developer engagement and activity, metrics documentation within the CHAOSS community, and inner-source metrics developed through the InnerSource Commons.

### Takeaways - DevRel serves as a key bridge within OSPOs to facilitate community progression from software users to long-term maintainers. - Organizations need dedicated community relationship management rather than standard sales-oriented CRMs to accurately model developer behavior. - Identity affiliation tools like SortingHat (GrimoireLab/CHAOSS) are essential for consolidating multi-platform identities and measuring the true ROI and health of an open-source community.