Hey everyone, we have some exciting news to share!
After some discussions, we’ve decided to have @grubba, a natural advocate, take on a more prominent role in advocacy as part of his existing responsibilities with the development of Meteor.js. That transition will gradually take place after the launch of Meteor 3.0. Part of the advocacy role is to ensure we have great documentation (v3 migration docs are in the works) and promote Meteor in live streams, podcasts, events, etc., which he has naturally done in the past few days!
That decision changed our strategy: hiring a community manager instead of an advocate and bringing in another developer.
We’re happy to welcome @camikuro (Camila Rosa) as our new Tech Community Manager. She will put into practice all the plans @TatiBarros is working on, engaging in online and offline conversations (such as on Twitter and forums) to connect with the community. She will promote our projects, assist with audiovisual content (podcasts, YouTube), and overall content management. She will be crucial in organizing meetups, gatherings, and other events!
We’re also excited to introduce @nachocodoner, who will join the Meteor core team! His extensive expertise in Meteor (as well as React, Capacitor, Electron, MongoDB, Redis, Webpack, SWC, etc.) will contribute to further developing and enhancing the Meteor framework.
Lastly, I believe it was only mentioned in our newsletter that @radekmie is also working with us. That’s a part-time collaboration, and he is focusing on Blaze and all the async work we need for Meteor 3.0. His knowledge is truly valuable.
Stay tuned for more exciting news! Cheers!