Harry… Interestingly, you bring up the confusion between DevRel and HR, as these are distinct fields with different responsibilities.
DevRel, especially in an open-source environment like Meteor, encompasses a wide range of tasks that go beyond pure code. It’s a role that addresses the ecosystem in which the code is created and used, including the community that supports it.
I’m also surprised that the conversation has yet to evolve into a more solution-focused dialogue concerning hard skills and specific technical challenges. I strongly believe in practical, targeted actions that solve concrete problems rather than philosophical debates, which, though interesting, may not lead to effective changes.
Given your enthusiasm and interest in the community, I look forward to seeing you actively participate in the various initiatives we’re planning. This includes mentorships with a particular focus on contribution onboarding for new members and the creation of technical documentation and articles. Actions like these are what build a strong community and a better product.
We are currently focusing on building a robust technical ecosystem based on respect and contributions in all aspects of an open-source community. Because of this, I don’t intend to spend any more time on this topic. We’ve already established a good dialogue, and if you have technical ideas that could solve problems and improve the Meteor ecosystem, I’m eager to hear them.
Once again, thank you for your feedback. It’s only through open conversations like this that we can improve.