Tech report - Oct 2026
Hello everyone,
After a month as loud as IndiaFOSS, October was meant to be quiet. On the codebase, it mostly was. This was an upgrade month.
Hacktober for the code, Havoctober for the threads. Lots of noise, very little light; we upgraded the stack and slept well at night.
The platform now runs on Frappe Framework v16, up from v15, on Python 3.14. The dashboard moved from frappe-ui 0.1.162 to its first stable 1.0 release. Both are large jumps, and both are mostly invisible for majority of users. If you use the site, you are unlikely to notice anything beyond things feeling a little quicker. Most of the change is in the desk, where our team and organisers manage events, and under the hood in how pages are built and served. Along the way we also moved the dashboard build to Vite 8 and swapped our pre-commit tooling for prek, which does the same job faster.
The nice outcome of all this: every piece of software listed on our stack page is now on its latest release. Staying current is a choice we have to make on purpose, because nobody else will make it for us. Falling a version or two behind is easy. Climbing back up later is the expensive part.
If the commit graph looks thin in a few places this month, that is festival season and some long-pending leave. The upgrades did not mind waiting.
On the IndiaFOSS side, the event photos are now up in an Ente album at indiafoss/2026/photos. The IndiaFOSS handbook, the guide we use to plan and run the event, now lives on docs.fossunited.org
Talk proposals got simpler to read and manage. The speaker details on a proposal used to be stored twice, once as personal information and once in the speakers list. We merged them into one place and tidied up how the speaker section looks. When a proposal's status changes, speakers now move to the right mailing list too, instead of staying on the "accepted" list after a talk is withdrawn. And if a call for proposals is set to keep speakers anonymous, the event page now respects that.
Single-use free ticket coupons are now tied to the email they were issued for, so a code shared around cannot be claimed by someone else. James Reilly worked on this, and also closed a small gap where two people claiming the last use of a coupon at the same moment could both get a ticket.
Profiles, event pages, RSVP pages and talk proposals now show proper preview images when you share their links, and profile previews carry Forklore and FOSS Hack badges.
Anas Khan went through every link on the site, all 934 of them, and fixed the ones that no longer worked. S Mayur fixed ticket PDF downloads, which were failing with an error. And a warm welcome to Ganesh (Vecto), who sent in their first contribution this month, a cleanup of our documentation links.
That is October. Quiet on the surface, a lot of moving furniture hammering underneath.
Now, the technical list for those who like the details.
Framework & Dashboard Upgrades (#1866, #1851)
Frappe Framework v15 to v16 on Python 3.14, and frappe-ui 0.1.160 to 1.0.2. Also Vite 6 to 8 (#1860), prek replacing pre-commit (#1863), and the dashboard text editor moved to frappe-ui's new molecule Editor (#1864).
CFP Submissions (#1828, #1829, #1859, #1850)
Duplicate personal information section removed and merged into the speakers table, simpler speaker section, email groups sync on status change, anonymised CFPs hide speakers on the event page.
Free Ticket Coupons (#1795)
Single-use coupons are bound to their mapped email; usage count is race-safe. Credits: James Reilly.
OG Images (#1861, #1867)
Dynamic preview images for profile, RSVP, event and CFP pages, with Forklore and FOSS Hack badges on profiles. Credits: Siddharth Bansal.
Dead Link Audit (#1810)
934 URLs checked, dead ones repointed. Credits: Anas Khan.
Ticket PDF Download (#1804)
Fixed a 500 error on ticket PDF download. Credits: S Mayur.
Documentation (#1824, #1840)
IndiaFOSS handbook and logistics docs on docs.fossunited.org (credits: Siddharth), documentation link cleanup (first contribution from Vecto).
For the full & detailed list: CHANGELOG · docs
As always, drop suggestions and issues at Git, hope you don't make a violation.
Dilip G
Software Engineer & Tinkerer
No comments yet. Login to start a new discussion Start a new discussion