I was thinking about quarterly (online) usergroup meetings on Blaze, its current state and its future.
Meeting Dates
Q1-26 to be announced
Q2-26 to be announced
Q3-26 to be announced
Q4-26 to be announced
Audience
This is directed not only to those who want to develop on Blaze but also to all those who just use Blaze in their projects.
Why these meetings?
Blaze is still a viable part of Meteor and it is still one of the things that integrate perfectly with Meteor out of the box.
At the same time, Blaze is missing more and more features that are just expected when coming from similar frontends, such as Vue.
With ongoing development of Meteor toward new build system and other awesome features it is also demanding for Blaze to stay compatible.
These meetings can give us the opportunity to discuss and prioritize next steps in development and bring focus on solving the current issues and contributions.
Why quarterly?
In my experience this is the perfect frequency as it is not too intrusive in regards to all our schedules while it enables to collect enough input by everyone to fill an agenda.
Minor topics might be discussed in this thread, if necessary.
What would be a good meeting time?
There is a limited timeframe to cover most timezones around the globe within a time that is within the limits of the daytime:
Then, there is the weekday. This might be more complex as some people prefer to do this as part of their work, others can’t attend during the week but only on weekends and others want to keep their weekends off any work.
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunay
0voters
Hope to see you soon!
I am really looking forward to meet with you and get a chance to keep Blaze a first class citizen within the Meteor ecosystem.
@harry97 thanks a lot. We actually have to, since we will very likely have to drop it as Blaze is relying on methods, seemingly dropped in 4.0, which makes your PR even more relevant.
@jkuester Where are you planning to organize or document those meetings? I was thinking of doing something inspired by Node.js, which has working groups separated by areas like performance, release, security…
I was considering creating a new repository called “working groups” starting with Blaze only. Once we develop a solid format for Blaze, maybe we can replicate it for new working groups (in the same repository) for other areas.
Your initiative would be beneficial for new contributors.
Hey @italojs I was looking for a Thursday in February, which is not too far away from now.
I like the idea of a usergroup repo, where we can document agendas and meetings.
I personally think this should be a monorepo under the /meteor github or to centralize the efforts as much as possible.
Let’s do a final vote on the exact date, which will be a Thursday at 15:00 UTC.
5th Feb 26
12th Feb 26
19th Feb 26
26th Feb 26
0voters
The meeting will take place in the Meteor Discord Audio/Video channel. Video appearance is very much appreciated, but is not a 100% must.
If you have urgent topics, feel free to comment here or in the near future usergroup repo and I will compile an agenda for the meeting.
