2025-10-02 | Resources Working Group Call (AMER)

[j12y]

• decision on whether to have meeting, cancel, or reschedule
• introductions
• intro to the devrel foundation and resources working group
• project updates
  • Persona Library @j12y
  • Tools Catalog @j12y
  • Events Directory @j12y
  • Metrics Index @arun-gupta
  • DevRel Maturity Model @j12y
• volunteers to facilitate APAC or EMEA calls
• deep dive working session for the maturity model (DevRel Maturity Model | Requirements & Use Cases #115) and discuss tools to survey schedules for a follow-up (Tools Catalog | Add Calendaring / Scheduling Tools #150) @arun-gupta @j12y
• issue backlog review
• open q&a

[j12y]

Quick Recap

The meeting focused on project updates and discussions around expanding time coverage for APAC meetings, with Jayson and Rob agreeing to explore scheduling adjustments. The team reviewed various development initiatives including a new project landing page, tools catalog, and events directory, with Jayson outlining plans for improved data structure and validation. The group also discussed the creation of a DevRel Maturity Model, agreeing to start with a phased approach and hold a special session in December to align on future projects and goals.

Next Steps

• Rob to help run the APAC Resources Working Group meetings.
• Jayson to set up the first APAC Resources Working Group meeting for the third Tuesday of the month at 11 PM Pacific time.
• Jayson, Arun, and Divya to schedule a focused breakout session to discuss metrics template and seed metrics.
• Jayson and Rob to keep the same agenda for the first few APAC meetings to see who attends and what gets discussed.
• All to use the December meeting for a retrospective and goal-setting session for the working group.
• Jayson to extend the December meeting time beyond the usual hour to accommodate the retrospective discussion.

Discussion

Project Landing Page Development

Jayson discussed the development of a new project landing page and tools catalog, explaining how the data is structured in JSON format to enable dynamic UIs and better data validation. He outlined plans to create filtered views of tools based on job categories and use cases, as well as to include tutorials and best practices for using specific tools.

Events Directory

Jayson also addressed the question of whether to create a new events directory or adapt existing ones, noting that while there are many event aggregation sites, none fully meet devrel leader use cases. He concluded that the events directory should serve as a directory of directories, aggregating data from other sources for adding additional annotations.

Jayson and Arun discussed the need to enhance the metadata for events listed in other directories. Jayson explained that while some event directories, like confs.tech, deliberately avoid adding certain types of data to focus on their core audience, there might be opportunities to standardize formats or create transformations to better meet other DevRel use cases. Arun emphasized the importance of defining a clear scope for the project to help people understand what they need to contribute. They also discussed potential improvements, such as accounting for event series and engagement types, to address spam issues and provide more detailed information for DevRel professionals.

• Example Annotated data like series, engagement types: https://github.com/DevRel-Foundation/wg-resource-aggregation/blob/poc/29/events-schema/events/data/fosdem.org.json#L32
• Example design and event aggregator notes: https://github.com/DevRel-Foundation/wg-resource-aggregation/pull/40/files#diff-00b2bca51d930fb4b4ae0d93ee81c967e9933b2bf8e78b8a42ee47e1a8515671

Metrics

Jayson and Arun discussed metrics reporting. Arun shared his experience with metrics classification and proposed focused breakout sessions to develop a template and seed metrics. Both agreed that additional breakout sessions could be effective for specific tasks, with the goal of bringing results back to the larger group for approval.

• Metrics Submission: https://github.com/DevRel-Foundation/wg-metrics-reporting/pull/7/files

DevRel Maturity Model Discussion

Jayson and Arun discussed scheduling a meeting, agreeing to align their schedules without waiting for a specific date. Arun shared his experience with creating a DevOps maturity model and suggested adapting a similar approach for the DevRel Maturity Model, focusing on clear metrics and levels of maturity. Jayson expressed challenges about some model's applicability across different organizations and teams, emphasizing the need for a more segmented approach that accommodates various DevRel roles and responsibilities.

The team discussed the DevRel Maturity Model, focusing on how different teams within a company contribute to developer experience, even if they don't own specific areas like documentation. Arun shared a personal story about a customer's outdated CI/CD process to illustrate the importance of influencing developer touchpoints across the organization. The group agreed that the proposed matrix was a good starting point, and Jayson suggested breaking down the problem into smaller, more manageable steps to reach consensus on specific aspects of the model before creating a comprehensive paper.

DevRel Maturity Model Development:

The team discussed the development of a DevRel maturity model, with Jayson and Arun agreeing that the document should serve as a collective vision rather than an individual proposal. They decided to start with a phased approach, beginning with defining the maturity levels and terms in phase one, before moving to more specific guidance on progression between levels in phase two. Jayson emphasized that the model should serve as both an organizational framework and educational resource, helping teams understand and implement DevRel practices even in smaller organizations.

• Maturity Model Example: DevRel Maturity Model | Requirements & Use Cases #115 (comment)

Goal Setting

Year end goal setting is a good way of communicating the phased approach, much like had been done during the first phases with tools, personas, and events.

• https://github.com/DevRel-Foundation/wg-resource-aggregation/blob/main/GOALS.md

DevRel Foundation as a Case Study

The group discussed the need for a maturity model and agreed to use the DevRel Foundation itself as a playground for testing and learning tactics of DevRel. They decided to hold a special session in December to reset goals and align on future projects.