[2024-11-14] APAC & EMEA Building DevRel Foundation Community Call

[leggetter]

Part of our community calls are being used as Open Office Hours to reach community consensus on Foundation Next Steps. If you would like to get involved, this is a safe and welcoming space to start!

Whether you are new to the call or a regular participant, you can add your discussion topics as a comment below or bring them up during the call. You can also share DevRel use cases, best practices, frameworks, and more by opening a new issue in the GitHub Discussions), which serves as the Foundation’s public forum. Additionally, we are always looking for 5-10 minute presentations in future community calls to spark discussion with the rest of the attendees and async.

Agenda

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

🧹 Housekeeping

• Welcome
  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.

  Welcome, everyone, to our DevRel Foundation open meeting. We are thrilled to have you with us today. Your presence here is not just appreciated; it's essential to our mission.

  At the DevRel Foundation, we believe in the power of collaboration and the importance of diverse perspectives.

  Your feedback is invaluable to us as we strive to create a space that truly supports and enhances the developer relations practice.

  We are committed to continuously evolving and improving, and your insights play a crucial role in shaping the direction of our efforts.

  Whether it's through suggestions, constructive criticism, or new ideas, we are here to listen and adapt.

  Thank you for being part of this journey with us. Let's work together to build a community that serves the needs and aspirations of everyone involved in developer relations.

• Code of conduct: Instances of abusive, harassing, or otherwise unacceptable behavior, please report at conduct@dev-rel.org

• LF Antitrust Policies. At meetings among actual or potential competitors, there is a risk that participants in those meetings may improperly disclose or discuss information in violation of the Antitrust Laws, or otherwise act in an anti-competitive manner. To avoid this risk, DRF participants must adhere to the policies available in conduct of meeting section when participating in DRF calls. To contact LF regarding matters addressed by this Antitrust Policy, please send an email to legal@linuxfoundation.org, and reference “Antitrust Policy” in the subject line.

🤔 Open Office Hour topics

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

1. DRF Steering Committee Elections discussion

SC election discussion - flagging to raise awareness and get feedback

2. Working Groups update

Working Groups plan

• There's a PR that takes the project view and lays it out as a single document Update phased plan to match project plan #118
• We have the project view Working Groups Cohort 1
• Reminder of the themes https://github.com/DevRel-Foundation/governance/blob/main/working-groups/themes.md

Working Group signup survey status

Survey: https://docs.google.com/forms/d/1PU8r__NHdysH0ElOznL-pbSnuOYQpRNF5EKLCXZkkro/viewform

78 responses in total

Working Group next steps

From the DRF FAQ:

When will you notify us that we’re part of a working group?

We plan to notify individuals by 14 November 2024, using the email shared in the sign up form. You can anticipate an email from steering-committee@dev-rel.org.

How are you selecting people for Working Groups?

We are forming groups based on expressed interest, and a willingness to commit to the DevRel Foundation Code of Conduct. In addition, there will be additional screening for working group managers for demonstrated program and/or team management experience.

What is the difference between the manager and the participant role?

The manager (or managers) of each working group will set the meeting times/dates, the agendas, facilitate the conversations, and be the contacts with the Founding Steering Committee. The participant (or participants) will play an active role in accomplishing the group tasks, including attending and engaging in meetings, contributing to ideas and recommendations, and taking on ownership of action items identified in the meetings.

3. Open discussion

Community discussion

Essential Information

• 🕛 Thursday November 14, 12 - 13 pm UTC

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

[leggetter]

Meeting Notes:

🎥 N/A

Participants (4)

• @leggetter
• @wesley83
• Aman Chopra
• Tochukwunwoke
• Debjani Chatterjee

Discussion Summary:

1. Attendance and Time Change: The time change may have contributed to low attendance. To improve participation in future calls, it was suggested to send reminders earlier in the week. Additionally, assigning new Discord members to the EMEA channel could help boost engagement.

2. Steering Committee Election Draft: Phil led the call and discussed the draft for the steering committee election, which is available on GitHub Discussions for community feedback.

3. Phased Plan Update: Phil reviewed the revisions phased plan, which is accessible in a pull request on GitHub. He also provided an update on the current timeline for the phased plan and our progress.

4. Group Themes and Participation:

   • Phil reviewed the themes for the groups and shared the Google Form submission totals, outlining the number of managers and participants for each theme cluster.

   • He noted that, although the form was set to close, it remains open for submissions, encouraging any attendees who haven't signed up to do so.

   • Phil explained the selection criteria for group membership.

5. Meeting Q&A:

   • Tochukwunwoke inquired about the absence of a Google Doc agenda for this meeting. Phil explained that limited preparation time was the reason and assured that future meetings would have an agenda document prepared in advance.

   • Tochukwunwoke also requested that the agenda be shared a day before the call.

   • Debjani Chatterjee asked if there was a cap on the number of participants per group. Phil and Wesley discussed the possibility of refining group processes and membership criteria as needed.

6. Recording Issue: Due to Zoom admin access restrictions, the call couldn’t be recorded. Phil mentioned that Ana, the Zoom admin, was not present to enable the recording feature. (note that this was @leggetter's assumption)

Meeting Conclusion: The meeting concluded 34 minutes past the hour.