Hi @rjdavid and @guncebektas! We understand your concerns, and thank you for sharing your opinions. We want to assure you that we are committed to making decisions that benefit everyone in the ecosystem. As we mentioned to Harry, we are simply adjusting the programs to make them even better. The community has many issues that we need to pay attention to, not just contributions to open-source, even though that is our primary and essential focus. We’re broadening our view!
We are here to listen and work together to make our ecosystem more welcoming and productive. If you have any more questions or suggestions, please feel free to share
2 Likes
Hi @radekmie! Since I got involved with the Meteor community, Vazco and its collaborators have held a special place in my heart. I’ve heard so much about your significant contributions and the pivotal role you and your team play in our ecosystem. It’s an honour to be in a community that features people as committed to open-source as you are.
Your transparency and honesty in your recent paragraph exemplify your personal integrity and serve as a model for all of us striving for a balance between passion and pragmatism in our work.
As Development Manager, I am deeply involved in the strategy and organization of various facets of the Meteor community, whether it’s user experience, community actions, or even more academic analyses. We have been attentive to multiple fronts, including our critical documentation, technical content, and partnerships. Some of our initiatives had to be paused for reassessment, new formats, and repositioning. We have had many constructive conversations on these subjects.
One point that is definitely on my radar is the Meteor Impact event. I understand the concerns about the cost and support for organizing this event. Still, we are considering focusing our efforts on something big to launch the new Meteor version. It would be fantastic to discuss this further with you.
I was extremely pleased that you voiced your opinion, and I’m looking forward to working together to build an even more robust and welcoming ecosystem
1 Like
I think the main question here is “Why did Meteor Software end Github sponsorships?”
The analogy of artists and their creativity is great. When we sponsor developers, they are free to work on what inspires them, regardless of priorities, and we want to invest money and direct efforts toward Meteor.js’ priorities.
We are working hard and trying to put all our efforts into Meteor 3.0. We’ve been working on this for over a year now, and we’ve happily partnered with Quave, Vazco, and Zodern on this endeavor. At one point we had 8 people working on it. We finally got an alpha version running on Node.js 18, but there’s still a lot of work to do, and we want to prioritize it. Redirecting the sponsorship budget to bounties is one way to try to achieve this.
We tested Algora and are looking at other options. Once we find a good way to do this, we want to open bounties for missing Meteor 3.0 pieces, package updates, open issues, and even content creation around all the changes made. We expect that most previously sponsored developers can earn more money than they earned from sponsorships.
So, to answer your points:
- Of course, this is not our expectation and intention. We want to get more contributions from more developers. We will open Meteor.js bounties to be done by whoever is able to contribute.
- My perspective is that it wasn’t working very well. That’s what I explained at the beginning of my answer. It’s great to see new packages coming from inspiration, but not so much when Node.js 14 is not supported anymore, and we couldn’t update Meteor.js in time to ensure we didn’t lose all security and critical fixes from the Node.js team itself.
- I’m sorry @harry97, but I can’t hear you when you yell like that. You criticize every time we hire someone. Our job positions are open to everyone, as answered in the other topic.
We are open to sponsoring great initiatives like the new podcast created by @alimgafar, @storyteller, and @jkuester. We started a conversation about that, and hopefully, we can find some good ways to support that.
Regarding @radekmie, and the Vazco partnership. We are dealing with this on a project basis. And we’ll probably reach out to them again to work with us on some demands very soon.
About Meteor Impact is a community-created event run by @storyteller. It was passed to Meteor Software last year, but as requested by @storyteller, we’ve agreed to return it to him. Sadly, he won’t be able to run it this year. But we plan to hold another new Meteor event by the end of the year.
7 Likes
I don’t know how, but these people need to be rewarded. Although sponsorship seems nice, motivating them with better methods will benefit our community.
Money is undoubtedly a motivating tool, but I believe that the people mentioned should be more respected. If we can learn about the changes made in such decisions directly from you, communication will be healthier.
2 Likes
I’m very grateful for your response @radekmie, it’s so intriguing to finally hear from one of the OSS contributors where they share their side of the story. Thanks a lot for such an insightful details. As useful and informative as these pieces of information are you don’t talk much about how you feel about the current changes and the atmosphere as a whole except for this part:
Not entirely for free because some people sponsor me on GitHub . I’m getting paid really well, and I don’t need this money to survive. I treat it more like a token of appreciation and kind of a “thank you” – that’s it. To be perfectly transparent, I got 3332.78 PLN (777.83 USD at the time of writing) in total since November 2019 and I’m grateful for every single cent. Also for every star on GitHub, heart here on forum, “You have a typo in your latest blog post!” DM, and whatnot.
Having said all of it, I don’t think it’s unusual among the ecosystem – people come and go, and most open source work is not paid or is done by some company directly benefitting from it. I’m not sure if I like it or not, but I got used to it.
Yeah, people come and go. OSS is being taken for granted nowadays without appreciating the people behind it. And, while you may be in a good financial position thanks to Vazco paying you for your open source work, good on them btw. That doesn’t mean we shouldn’t strive for better environment.
While I don’t support you financially on GH, let me tell you I’m fully appreciative of your efforts and I’d certainly hope you continue putting out such amazing work. 
The only thing I’m truly sad for is this year’s Meteor Impact. I contacted @storyteller about it, and he’s simply too busy to organize it. I’m surprised that Meteor Software didn’t do anything about it, but it is what it is. I assume it’s partly because of how much effort goes into Meteor 3.0, but still.
Meteor Impact is an community led initiative by @storyteller, it’s not Meteor Software fault nor responsibility at all that it wasn’t held this year. Meteor Software tried to take over it but then relinquished it back to @storyteller as he requested which is a very good thing as Meteor Software was putting their needs first and you may ask @storyteller if I’m lying.
While I am working on making Blaze async alone, I wanted to give a huge shoutout to @DanielDornhardt (I hope it’s @DanielDornhardt’s forum profile!), as he’s putting a lot of effort into
nagging me to work on that and make it even bettertesting every single piece of it and providing valuable feedback. Really, if not for his questions, we wouldn’t have a half of it.
Absolutely agree, @DanielDornhardt is the unsung hero of this story. Thanks a lot for your efforts. I’m too was interested in the Blaze changes but was busy conducting the military service which is why I was away from the scene. So, I’m definitely grateful that somebody else was holding it down. Again, thank you Daniel.
@TatiBarros Let’s have a chill chat! I’m already in touch with these critical folks who are super important to the community.
I really despise relaying information which was shared to me in a private conversation but you keep playing us for fools thinking words don’t travel. Newsflash they do! So apparently @zodern isn’t one of these critical people too 
- Of course, this is not our expectation and intention. We want to get more contributions from more developers. We will open Meteor.js bounties to be done by whoever is able to contribute.
- My perspective is that it wasn’t working very well. That’s what I explained at the beginning of my answer. It’s great to see new packages coming from inspiration, but not so much when Node.js 14 is not supported anymore, and we couldn’t update Meteor.js in time to ensure we didn’t lose all security and critical fixes from the Node.js team itself.
You seem to agree with me about this whole thing not going the direction you intended and may need a little correction. So, thank you for that.
- I’m sorry @harry97, but I can’t hear you when you yell like that. You criticize every time we hire someone. Our job positions are open to everyone, as answered in the other topic.
Uhhhh, not if’s uncalled for lol. Did all you discern from my words that they’re just some angry yells?? Maybe my style put you on the defensive side so I’ll try a different method this time to get my point across where I’ll refrain from making sarcastic comments or using improper language.
You made lots of new hires to work on your ahem ahem cough
shittyplatform like Thiago Reis, Vitor Souza, André Luis. You even hired a Developer Relations Manager, who started her Meteor forums account less an 90 days ago!!! WHAT THE FUCK DOES SHE KNOW ABOUT METEOR??? HOW ABOUT GIVING THAT MONEY TO PEOPLE LIKE @storyteller @jkuester @alimgafar WHO STARTED A GODDMAN PODCAST ABOUT METEOR??? WHAT THE FUCK IS WRONG WITH YOU?? I’m truly perplexed by the amount of ignorance the people making these decisions have.
Hiring @TatiBarros was’t the best decision as a Developer Relations Manager, here’s why:
-
She doesn’t know a thing about Meteor which she admits to and is trying to work on by immersing herself in the community. Good on her but that just doesn’t cut it. Imagine your boss brings over an HR person to review your code. Angered by the move, you tell your boss how he doesn’t know a thing about Node.js. To only hear back that the HR person is working diligently on improving his code skills for nearly three months!!! WOW THREE WHOLE MONTH?? I’m seriously trying not to be sarcastic nor write in caps. How’d you feel about this situation? Infuriated, frustrated, underappreciated. How do you think the community feels? You get the idea so please take a moment to think about deeply about it.
-
You under utilize local talent and end up driving them away. It’s a slap to the face to the community, so instead of getting local talent onboard you cut them off and bring over someone else? So much for the so called ambassadors when they’re merely kept for parading and showing off. This leads to a feeling of mistrust and add to the general miscommunication image which MS needs badly to change. Frankly, it pisses me off that you completely overlook someone like @storyteller or any other community member and try to hire someone else.
-
Efficiency / Cost effectiveness. By directing your efforts to help out community endeavors like Meteor Dispatch podcast for example, you end with a two birds one stone type of situation. 1) You win the support of the community and make them feel appreciated. 2) Nobody is better suited to talk/represent your product than the guys who build/use it on daily basis. 3) It’s much more economical to donate 100$ to the podcast than paying thousand to a single person to handle all of the developer relations efforts. If I were the one making decisions at MS, I’d take the salary of @TatiBarros and donate it all community members putting actual work and believe me that’d be a lot more beneficial. Sorry, but it’s my honest opinion.
I understand that you commented that you’re willing to help out with the podcast which is nice but I hope now that you get why I wasn’t so thrilled with the new hire. As for @TatiBarros, it’s not personal. I’ve no grudge against you but I want the best for Meteor. It’s be beneficial for starters if you wanna build trust to tone down on the corporate jargon.
Your transparency and honesty in your recent paragraph exemplify your personal integrity and serve as a model for all of us striving for a balance between passion and pragmatism in our work.
As Development Manager, I am deeply involved in the strategy and organization of various facets of the Meteor community, whether it’s user experience, community actions, or even more academic analyses. We have been attentive to multiple fronts, including our critical documentation, technical content, and partnerships. Some of our initiatives had to be paused for reassessment, new formats, and repositioning. We have had many constructive conversations on these subjects.
1 Like
Probably the most important thing now for Meteor and the community is get 3.0 out, unblock node 18 update, and then work on updating commonly used packages. Any other discussion/effort is a distraction in my opinion and it seems @fredmaiaarantes is focused on that, so he has my vote.
But I understand where @harry97 is coming from and his concern about alienting open source developers however it seems to me @fredmaiaarante wants to have more control over where the money is being spent and on what activities, which is also understandable from project management perspective.
Anyway, as I mentioned, I’m personally very excited about Meteor 3.0, it is really commendable effort.
10 Likes
It is multiple things. After Pathable closed their doors earlier this year that made Impact exponentially difficult to pull of (pretty much starting from scratch). This difficulty also meant that I would have to expand a lot more money up front (Pathable’s sponsorship really saved us there) and I’m currently not in a position to do that. But that might still change depending on how the rest of the month and maybe the next one goes. Another thing that I’m exploring is to switch to in-person event.
That is some news. Well do let me know so that we don’t needlessly overlap on dates and things.
2 Likes
Another thing that I’m exploring is to switch to in-person event.
1 Like
My two cents on this. I personally didn’t know that this role/person is onboard and I can’t really fully understand the benefit obviously from my view as an enduser. However, I’d appreciate if that salary is rather spend on paying developers, either in-house at the Meteor team or by allowing the aforementioned external devs on improving packages like meteor-desktop or blaze.
Again, I haven’t interacted with @TatiBarros before and I can only judge from her answers in this trust. But if I read that corp lingo, I too think that this isn’t appreciated by the intended audience. That’s not how we talk amongst Devs.
1 Like
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.
1 Like
Hi! Thank you for your valuable feedback. My previous tone might have come across as overly formal. However, my direct approach during the first few months was intentional and necessary for me to entirely focus on understanding the Meteor ecosystem. This includes everything from its history and community to its technical content and practices.
I want to add that I have experience in other open-source communities, where I’ve organized groups focused on various contribution aspects. This extends beyond just code and includes the promotion of diversity and inclusion, establishing healthy codes of conduct, and encouraging practices that developers can apply in their careers beyond the open-source context. One of my greatest passions is helping people effectively share knowledge.
As for DevRel, it’s a multifaceted role. It’s not just about coding; it’s also about building a healthy community, organizing educational resources, and providing technical guidance. My strategic focus has been on strengthening the educational aspects and creating room for contributions beyond just code.
If you have any specific ideas or suggestions, I would be happy to hear them. I appreciate your feedback once again. Conversations like this allow us to grow and improve; I’m always open to that.
3 Likes
I agree with some points of the discussion, but not with all, and will like to add some things.
In the past I have commented that one of the main issues with Meteor, is that there is not a clear way to contribute, and many times contributions end up never even getting discussed after there is a PR by someone. This is likely, as it has been stated many times, because of a lack of clear communication and organization, and this could be improved and hopefully bringing in @TatiBarros can affect positively the communication, which most of us have asked for many times in the past.
So let’s focus on what can be improved and what can be done by the MS and us to keep around the people with the know how, but also to spread that know how so that it doesnt stay in the head of a few and more of us can contribute.
For ex: Many times I would have liked to work on some meteor internals, but the lack of documentation and the code being to “old”, makes anyone without prior experience on it to need to check around everywhere to understand what something does or comes from, and this makes any attemp to take extremely long.
Just an idea, it might be interesting, after getting meteor 3 out there, to organize some kind of online events, where the core devs share their knowledge of the meteor core so that others in the community can dig deeper and understand more about it. In the end this can help more people to be able to contribute.
9 Likes
I totally agree with the analysis @pmogollon, not exploiting and involving the community is a short-sighted choice. For example, after the release of Meteor 3 the age-old issue of migrating third-party but frequently used packages will arise. Without clear planning, one risks doing the same work at the same time and creating further entropy.
1 Like
This is very sad news. I guess it’s time to move on. If such key players leave the ecosystem, Meteor does not really have a future. It’s sad.
Sorry, but it is not woke blurb that we need. Just sayin’.
1 Like
I would not be so negative about it, people come and go and we have seen this in the history of Meteor.
But I do share the sentiment, Meteor organization has a history of alienting key open source contributors, I personally never understood that myself, it breaks trust, I just assume there is something happening behind closed doors. I personally would never have let @zodern go and would pay him over any dev relationship role while simultaneously empower others to contribute. But I didn’t want to say it because the action has been done. So I would highly advice Meteor software to never alient current contributors, long time community members and existing clients, they kept Meteor going.
However, I do think Meteor internals could be better documented and more welcome to empower all kind of maintainers going forward. Specifically the parts that need it stay aligned with Node.
Also, I would really appreciate less drama and more focus on practical things, please stabilize the team, structure and support so we don’t keep having FUD like this. People saying they are leaving, people have existential issues over sponsors, etc, it’s a piece of tech to allow building stuff not a cult, people doing their jobs/businesses, focus should be maintaining and improving it in a sustainable long-term way.
6 Likes
This pretty much sounds like the “communications strategy” of good old MDG to me.
Maybe you’re right with this. And maybe it’s just my frustration about this common pattern I could see in the past years. But I was really hoping that Tiny would value great contributors like @zodern more. As a pure user, I am very thankful to guys like him and his great work. So it’s sad to see that these guys are let down once again. Just my two cents. And no, marketing and corp blurb won’t change my mind.
1 Like
Yes I hear you, @zodern and other key contributors should be funded and set free, and never micro-managed, I think cutting sponsorship on him was big mistake. He has been a gift to the community and I think everyone here admires and appreciate his work.
Non-developers see all develoeprs with same lens, developers know the exceptional when they see one.
5 Likes