[2024-09-05] APAC & EMEA Building DevRel Foundation Community Call

[anajsana]

Part of our community calls are being used as Open Office Hours to reach community consensus on the foundation's next phases and address questions and blockers on the DevRel Challenges and Frequently Asked Questions. If you would like to get involved, this is a safe and welcoming space to start!

Agenda

👋 Intros - If we have a large group, we'll use chat
🧹 Housekeeping

• Code of conduct (link).
  Instances of abusive, harassing, or otherwise unacceptable behavior, please report at [email protected]
• Intro to roles: facilitator, moderator, scribe

🤔 What we're doing in this call

The Developer Relations Foundation mission:
The mission of the Developer Relations Foundation project is to elevate the professional practice of developer relations and increase awareness of it as a driver of business value.

Open Office Hours

Time to listen to the voices of community members, answer questions, and tackle blockers together. Topics can be related to:

• Proposal: A Phased Approach for Leading DevRel Community Initiatives

  • Review comments and input from the community - See how can those be integrated into the phase proposal
  • What’s missing? What works? What does not?

• Engagement and Location Survey Updates - Sharing Preliminary results and identifying insights with the community

• Any other topic the community wishes to raise!

Essential Information

• 🕛 Thursday 5, 13:00 - 14:00 pm CEST
• 📝 g.doc agenda

Frequency	Duration	Zoom link	Join Discord
bi-weekly	1 hour	Here	Join

[anajsana]

Meeting Notes

Phases Proposal Review and Input

Community Review on GitHub Discussion. Questions Raised:

• Code of Conduct: Does the Code of Conduct also fall under the collection of themes, or are we looking at having a separate mechanism for setting it up/electing members to it?
  • CoC has been established as an initial version, and the Steering Committee is currently handling it. However, there hasn’t been any discussion on forming a separate CoC committee. In communities like CHAOSS or other Linux Foundation projects, they usually have a dedicated committee.
• Membership: Are there any minimum requirements for membership, i.e., a set criteria or something of the sort?
  • PL: No official membership criteria have been established.
  • DV: What are the selection criteria? Is it joining Discord? Making a certain number of contributions?
  • AJ: I like the idea of establishing a contribution ladder that documents the criteria for becoming a community participant. For instance, this https://glossary.cncf.io/contributor-ladder/ (but more simple).
• PL, AJ: Addressed the differences between those who want to contribute content vs. those contributing to project infrastructure, go-to-market, and community management (meta parts).
  • DM: Having different people and channels for those two roles might be helpful:
    • DevRel Foundation community participants contributing to infrastructure, community guidelines, etc.
    • DevRel Foundation community participants contributing to addressing the challenges of the DevRel profession, developing best practices, and other content-related themes for the foundation.

Scope and Goals for Each Group to Set Expectations

• RJ: I think that when the themes are announced, there should be a discussion about the scope and goals of each group to help set expectations for people considering volunteering as group managers. I would probably not commit without knowing if I align with the rest of the group.
• PL: Do goals come before or after defining the groups?
• RJ: Chicken-and-egg problem. It can be an iterative process. Start by defining the groups, then adjust as needed. But it’s an important topic to address directly if I’m going to commit to this.
• AJ: Reusing existing guides from other open-source communities could be a starting point for these iterations. We don’t need to reinvent the wheel.

Updates on Engagement and Location Survey - Ways to Help

Recap on the current survey: To date, 45 people have completed the survey. Discussed Ideas to reach more people and increase diversity across regions in survey participation:

Input on the call:

• Partnerships with other groups and projects involved with DevRel to amplify the message.
• DM: Awareness at local events (KCDs) and global ones where DevRels gather.
• AO: Have we tapped into region-specific communities to collaborate so far? I remember seeing the DevRel Communities sheet on the Discord server.
• SG: “DevRel” is a complicated term. Some people might be doing DevRel without using the term. When presenting, consider alternative words like “community management.”
• AO: Amplify in localized DevRel communities and collaborate with organizations for greater reach.
• Have a public and accessible list of communities that have been contacted so that people can see what’s been done and how newcomers can help drive awareness in their local communities.
• PL: Using other DevRel-related research, such as the “State of DevRel” report coming out on September 10th, could be helpful.

Communication Templates for Regional Ambassadors/Supporters to Promote the DevRel Foundation Survey and Other CTAs

• AJ: Would having a set of “Introducing DevRel Foundation” communication templates for people to share locally be useful?
  - DM: +1 to this. We’d need to clearly outline our asks in the template.

Resources of Interest Shared During the Call:

• Survey Link for Local Promotion: https://forms.gle/ukt2Y1jiVJkLY7L28
• DevRel Community Calendar: https://lists.dev-rel.org/g/community/calendar

AO: Request to record the meeting participants on the call.

Participants

• Divya Mohan, SUSE
• Raul Jimenez, Esri
• Atsushi, MOONGIFT
• Aditya Oberai, Appwrite
• Ana Jiménez Santamaría, LF
• Tochuk Wun
• Phil Leggetter
• Samson Goddy, Hedera