2025-03-06 | Monthly Call and Persona Library

[j12y]

Agenda

• decision whether to have or cancel this meeting
• introductions: 1) your name, 2) a unique fact about yourself, 3) a person or company you think is doing devrel really well, 4) pick somebody that hasn't introduced themselves yet
• announcements: Next WG meeting scheduled for April 2 same time
• review persona section of charter
• share tools and events poc as a reference: Aggregation Proof of Concept #29
• present persona project plan: Persona Library 1.0 #45
• discuss persona library requirements and use cases: Persona Library | Requirements and Use Cases #46
• call for additional topics / q&a
• poll: Poll | Aggregation of Blog Posts, Tutorials, Courses, and Articles #8

Subscribe to our working group calendar for instructions on how to connect to the call.
https://lists.dev-rel.org/g/wg-resource-aggregation/calendar

[robearlam]

I can't make this months call, but will catch up on the recording

[oleg-nenashev]

I am not 100% sure either. Paternity leave

…

On Thu, Feb 27, 2025, 03:48 Rob Earlam ***@***.***> wrote: I can't make this months call, but will catch up on the recording — Reply to this email directly, view it on GitHub <#43 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAW4RIHOG5VW27YHOI53CIL2RZ4HPAVCNFSM6AAAAABXUVEACWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZTGM2DEMA> . You are receiving this because you are subscribed to this thread.Message ID: <DevRel-Foundation/wg-resource-aggregation/repo-discussions/43/comments/12333420 @github.com>

[anajsana]

Thanks all for your time and efforts 🙏 I saw there are already a few folks who marked "attending" this call :)

ps: It's a bit late for me, but I will definitely watch the recording!

[ndekwe]

At the last minute, I can't be available. I will watch the recording.

[j12y]

Meeting Minutes

Covered topics from the agenda.

Discussion around persona requirements:

• A theme that emerged was "good enough is good enough" because creating something to discuss and gather feedback is better than abstracts. Several on the call shared this sentiment.
• Customization. Everybody will have an opinion, being able to customize versions is valuable. Having something generalized enough where three or four can allow for derivates. More than that becomes unwieldly.
• Modularity. Building out some standard blocks across the board may make sense, leaving space for other areas to be tunable by any organization's needs; but can still use common labels for ease of communication such as "Software Engineer"
• Framework. Presenting a framework or blueprint would have value; providing examples and decisions that led into it
• Developer-first or developer-plus. This should be a concept that spills into all working groups, because a million sign-ups may matter for some products, but one critical partner may be better for others. Other distinctions are for tech first projects, craftsman, explorer, etc.

General discussion:

• Think there are many resources dev.to, reddit, hackernews, etc. and the rules to use them for how to be successful would be valuable. An easy reference of things you should read like books on devrel, etc.

• Clarification that a resource in the repository is to be available for the devrel practitioner, not just resources for the foundation to use.
• Sharing other resources for DevRel interest and awareness:

• https://nyc.devrelcon.dev/
• https://devrelkaigi.org/

Thanks to all who joined the conversation.

[j12y]

Recording (note that we didn't really start until about the 10m mark):
https://zoom.us/rec/share/IG_mL3aldSscto--TqrkPUcDZYJ8_KKwGr0JDHNio5fb4tc_6edBf7kvEJ5pBecW.eTIRxz88WW35ribl

[robearlam]

I watched the recording back earlier today, some great discussions, and @j12y did an awesome job hosting!

Completely agree in the "good enough is good enough" approach. Let's get things started and iterate once we realise we can improve!