Hi, I’m Ian 👋

I’m a Flarum core developer and the lead Flarum developer at GlowingBlue — and I spend a lot of my time maintaining Flarum itself and the wider extension ecosystem (including work in the FriendsOfFlarum org).

If Flarum helps your community run, your sponsorship helps keep the platform healthy: fixing bugs, reviewing PRs, improving performance, keeping extensions compatible, and making sure upgrades don’t become a weekend project.

What your sponsorship supports

• Core maintenance: bug fixes, refactors, tooling, and long-term stability work
• Extension ecosystem: compatibility updates, maintenance releases, and issue triage
• Support and guidance: reproductions, debugging, and helping unblock real deployments
• Quality & reliability: reducing regressions and making upgrades smoother

This isn’t “one big feature” work — it’s the constant, sometimes invisible effort that keeps the whole ecosystem dependable.

Where I focus

• Flarum core development and review
• FriendsOfFlarum maintenance and coordination
• Long-term ecosystem health: docs, DX improvements, dependency updates, and upgrade paths

Why I’m asking

Open-source maintenance is real work: it’s research, review, releases, and support — often after-hours. Sponsorship helps me justify putting more consistent, focused time into the work that keeps Flarum and its extensions reliable for everyone.

If you’ve ever shipped a Flarum upgrade without drama, found an extension that “just works”, or gotten unblocked by a fix landing quickly — that’s exactly the kind of work your sponsorship enables.

Thanks ❤️

Whether you sponsor, contribute code, report issues, or simply run Flarum thoughtfully — thank you for being part of the community.