Replies: 3 comments 4 replies
-
|
I believe the idea is very good, I will try with the regional vision of LATAM to make a contribution of thought: this would be of great value, also thinking about guiding those who still have doubts about what DevRel is. Believe it or not, this is still one of the biggest pains in part of LATAM (what it is, what it does, why it exists...). |
Beta Was this translation helpful? Give feedback.
-
|
Depending on the criteria, I feel that this could exclude those who are more deeply committed to DevRel as a business. So the criteria is very important. via FinOps. |
Beta Was this translation helpful? Give feedback.
-
|
I think this is an excellent idea, and at some point, it will have to be exclusive, which I believe is necessary. Where to draw that line? That's a more complex discussion 😅 . That being said, as Jorge Barrachina highlights in his book, I understand DevRel as a discipline more than a role, encompassing many roles such as developer advocate, developer evangelist, developer relations strategist, technical community manager, etc. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As this initiative evolves (and given the fact that DevRel Foundation operates as a non-funded, community-driven model) I think getting community consensus + having a document on what outlines the criteria and responsibilities for joining the DevRel Foundation as a practitioner member / community member is important for future elections that might arise in this community.
FinOps has a nice example. here. Maybe a similar document can be drafted and discussed in this thread and iterated in upcoming community calls, to include as part of the governance repo. Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions