Blaze Usergroup Meetings 2026

jkuester · December 12, 2025, 9:53am

Hey Blaze users

I was thinking about quarterly (online) usergroup meetings on Blaze, its current state and its future.

Meeting Dates

Q1-26: February 19, 2026
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:

UTC-time	Los Angeles	New York	Berlin	Delhi	Tokyo
15:00:00	Thu 07:00	Thu 10:00	Thu 16:00	Thu 20:30	Fri 00:00
16:00:00	Thu 08:00	Thu 11:00	Thu 17:00	Thu 21:30	Fri 01:00
17:00:00	Thu 09:00	Thu 12:00	Thu 18:00	Thu 22:30	Fri 02:00

UTC 15:00
UTC 16:00
UTC 17:00

0 voters

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

0 voters

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.

italojs · December 19, 2025, 1:30pm

amazing! count with me

storyteller · January 15, 2026, 3:46pm

I’ll join in as well.

jkuester · January 15, 2026, 4:16pm

Okay it looks like it’s settled. On a Thursday at 15:00UTC I will look for potential dates and propose here.

harry97 · January 19, 2026, 1:34am

https://blog.jquery.com/2026/01/17/jquery-4-0-0/

You might want to discuss this

jkuester · January 19, 2026, 6:14am

@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.

github.com/meteor/blaze

Replace jquery parseHTML with native alternative

meteor:master ← harryadel:parsehtml

opened 01:43PM - 06 Jan 25 UTC

harryadel

+348 -13

Decoupling jQuery and Blaze would take substantial effort. jQuery is used in man…y places: 1. HTML Parsing ```js DOMBackend.parseHTML = function (html) { return $jq.parseHTML(html, DOMBackend.getContext()) || []; }; ``` 2. DOM Selection ```js findBySelector: function (selector, context) { return $jq(selector, context); } ``` 3. Element Teardown Detection ```js $jq.event.special[DOMBackend.Teardown._JQUERY_EVENT_NAME] ``` 4. Event Delegation/Handling ```js delegateEvents: function (elem, type, selector, handler) { $jq(elem).on(type, selector, handler); } ``` They're ranked them in terms of ease of replacement, and impact. The challenge lies mostly in testing and ensuring cross browser compatibility so it's best to merge each change individually, do a minor release, test then repeat until all is merged then we can do a major release. I chose to start off with [parseHTML](https://api.jquery.com/jQuery.parseHTML/). It present a nice challenge where even if we got it off won't cause major errors and can act an indicator if the moving out of jQuery would be doable. This [implementation](https://gist.github.com/Munawwar/6e6362dbdf77c7865a99) and the official [tests](https://github.com/jquery/jquery/blob/4466770992d5833358169d0248c4deedadea1a96/test/unit/core.js#L1352) were used in constructing the new tests to ensure backwards compatibility. You may remove the code I did and then re-add the jQuery `parseHTML` function and you'd find the tests still pass.

italojs · January 20, 2026, 6:21pm

@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.

What do you think?

jkuester · January 21, 2026, 8:19am

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

0 voters

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.

italojs · January 21, 2026, 1:48pm

Agree 100%
Will create a repo for it and leave it here soon

what about record it and post at meteor’s YT channel?

do you already have a server/channel for it? I can create one for it inside our official discord

jkuester · February 2, 2026, 2:17pm

The first meeting is now settled: Thursday, 19th February 2026 at 15:00 UTC.

jkuester · February 2, 2026, 2:19pm

@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.