The first meeting is now settled: Thursday, 19th February 2026 at 15:00 UTC.
3 Likes
@italojs I personally like the recording but we should ask all attendees at the beginning if they are okay with it as I don’t want to exclude people just because they don’t like being recorded.
It would be awesome if we can use a channel in the official discord as I think this is likely to increase the amount of users showing up.
If you want to use the same system we had for Impact, I can make that happen.
Reminder: today is the Blaze Usergroup Meeting at 15:00 UTC in the official Meteor Discord.
@italojs we cannot create an event in the official Meteor Lounge discord so we need you to set it up please. If you cannot make it in time, we will provide an alternative in the MeteorJS Community Discord.
I was hoping to pop in and take a gander, but I won’t be able to attend this one (bad schedule for it this week) but in fairness I have not touched much Blaze before anyway, so in the meantime I guess my penance is to use more Blaze in preparation for Q2 (probably with basecoat) 
1 Like
Starting in roughly one hour, the link to the Meteor Discord Lounge voice chat event is this: Meteor Lounge
Thank you for the recording!
(Moved comments to Blaze Next - Vision, Ideas, Tasks etc - #2 by zodern, sorry didn’t notice the other thread!)
1 Like
Dang! I missed it. I should have put it on my calendar. Glad to see Blaze getting some great attention in 2026!
2 Likes
Hey there, it’s time to plan the second Blaze usergroup Meeting for this year
The main topic for me would be how we can keep the awesome Momentum up and running.
For those who missed it: the Blaze repo got some awesome PRs toward the upcoming 3.1.0 release.
However, I can only manage as much as my free resources allow me to. We currently need to ensure this release remains stable and backwards compatible. Testing will be low-barrier by providing published alpha/beta/rc.
Additionally I need support in reviewing remaining PRs for 3.1.0 so I can prepare an RC.
Vote on a date
As most people voted for a Thursday 15pm utc as the sweet spot for a meeting, I will opt for the following dates:
- 28th May
- 4th June
- 11th June
- 18th June
- 25th June
0
voters
2 Likes
Looks like 4th June it is 
oh, 4th June is a holiday for me and 3pm utc is the lunch time lol, but i’ll do my best to be present
btw, I created a public calendar for those meetings, let me know if you can attach it in your calendar and if the meeting schedule is in the proper hour for your timezone, i’m still learning how it works
Click here to be redirected to the calendar
it’s good to see this user group having another meet, it’s an inspiration for what is being discussed in this PR
1 Like
Quick reminder, tomorrow is the next Blaze Usergroup meeting. Here is my proposed lightweight agenda:
- Recap of 3.1.0 development
- Last remaining steps and TODOs for 3.1.0
- What’s coming for 3.2.0
- Refining vision for 4.0.0
It would be great to see at least the contributors of 3.1.0 @dupontbertrand @wreiske and of course anyone interested in the future of Blaze @marklynch @harry97 @DanielDornhardt
5 Likes
I’ll be there! Added to my calendar just now. 
1 Like
We will meet in the Blaze audio channel on the Meteor Lounge Discord, just scroll down there is a “Blaze” audio/video channel:
1 Like
w are starting just now
The meeting invite was for a google meet… I don’t have a discord on my work device. I’ll have to make it to the next one!
Here is the recording:
4 Likes
Meeting Minutes: Blaze Usergroup Meeting Q2 2026
Source: Blaze Usergroup meeting Q2 2026
1. Meeting Overview
- Topic: Recap of Blaze 3.1 progress, upcoming plans for Blaze 3.2, and the long-term vision for Blaze 4.x and beyond [00:14].
- Key Participants: Host, Bertrand, and Jan.
2. Blaze 3.1 Recap & Next Steps
- Merged Updates: 8 PRs have been successfully merged. Major improvements include the removal of external npm dependencies and the introduction of a native DOM backend. This allows Blaze to operate completely without jQuery [01:26]. These are currently considered non-breaking changes.
- Pending PRs: There are 2 pull requests remaining:
- Testing & Reviews: The host emphasized the need for community help with code reviews and testing, particularly for reproducing and testing the stale re-renders fix [03:30].
- Release Plan: The team decided to contact the Meteor Core team to issue a Beta release right away. This will allow the community to test the current state easily via the package manager [10:45]. Once the remaining 2 PRs are reviewed and merged, a Release Candidate (RC) will be published before the final 3.1 rollout [11:57].
3. Planning for Blaze 3.2
- Upcoming Features: Development will heavily focus on adding inline expressions, enhancing Spacebars (contributed by Bertrand), and implementing server-side template rendering [12:51].
- Housekeeping & Backlog: During the call, the team actively organized the backlog, closing resolved issues (such as moving the codebase to ES2015 and removing jQuery) and appropriately linking open PRs [15:17].
- Benchmarks: The team agreed that implementing better performance benchmarks for Blaze will be an important goal for version 3.2 [17:16].
4. Long-Term Vision (Blaze 4.0 & 5.0)
- Blaze Standalone: The team discussed the complex goal of decoupling Blaze from Meteor Core (e.g., Tracker, Reactive variables, Reactive dictionaries).
- Developer Experience (DX): To ensure Blaze remains relevant in modern web development, the team highlighted two major future needs:
- IDE Support: Current IDE support is lacking compared to frameworks like Vue. Improving this will boost developer productivity [28:59].
- Single File Components (SFC): There is strong interest in adopting a single-file format (similar to Vue) to cleanly scope HTML and JavaScript together in one view file [31:45].
5. Action Items & Next Meeting
- Action: The host will coordinate with the Meteor Core team to publish the Blaze 3.1 Beta release [10:52].
- Action: Bertrand will scaffold a small test application to help developers reproduce and review the stale re-renders bug [07:59].
- Action: Meteor Core team will need to review and merge server-side rendering PRs to unblock Blaze 3.2 features [36:09].
- Next Meeting: The next Blaze Usergroup meeting is scheduled for Q3 2026 [36:41].
1 Like