Spaces
© 2026 Minsk Python Community. All rights reserved. This website is built using open-source software. The source code is available on GitHub.
Wagtail Space & our community
In late October 2018, Minsk hosted Wagtail Space — a gathering from the international Wagtail CMS series. It was primarily a hands-on open-source code sprint: people opened issues, shipped pull requests, improved docs and translations, and sat next to maintainers who reviewed the work.
What it was
Wagtail Space is the Wagtail community’s own series of contributor events. Minsk was the first Belarus edition and sits in the official history alongside later and earlier cities on wagtail.space. That archive lists the Minsk edition as 26–28 October 2018; the main two-day code sprint took place over the weekend of 27–28 October.
Calling it a “conference” undersells the format. The pitch invited Python and frontend developers, UX/UI designers, translators, and Wagtail users — anyone who could help improve the project, not only people who wanted to sit through talks.
This was not “Minsk Python Meetup under another name.” It was an official Wagtail Space event. Local Python community members helped organise it and showed up as contributors; the series brand and core facilitation came from the Wagtail community.
How the local community took part
Wagtail’s post-event write-up credits organisation to Wagtail’s own Mikalai together with Tatiana and Stas — “two great members of the Minsk Python community.” That Mikalai is Mikalai Radchuk (Torchbox / Wagtail): he initiated bringing the sprint to Minsk and, during the weekend, guided participants and reviewed incoming pull requests. Tatsiana Tsygan and Stas Rudakou were the Minsk Python organisers working with him.
From the meetup’s side, the weekend landed in the same weeks when people in the community chat were talking about independence and looking for partners — not only for another lecture evening. The sprint was announced there as a chance to try a new format: two days of coding instead of “only lectures.” More on that shift is on our community history page.
iTechArt sponsored the venue and kept people fed — coffee, pastries, sandwiches — so contributors could stay focused on the codebase. International Wagtail people (core team and regular contributors) worked side by side with locals who already knew each other from meetups, and with newcomers who discovered Wagtail at the sprint itself.
How the sprint ran
Organisers started people on good first issues rather than forcing teams immediately — a way to welcome newcomers and gauge familiarity with Wagtail and open-source workflow. Dan Braghiș from the Wagtail core team gave a Russian-language State of Wagtail (project status and roadmap), followed by discussion of use cases, headless CMS, and GraphQL. After that, most of the weekend was real development: discuss a fix, write the change, open a PR, get review, merge.
Maintainers prepared work in advance. Wagtail’s GitHub still carries the historical label
sprint:Minsk2018
(“Historical - Wagtail sprint in Minsk 2018”). Some of those issues also carried Hacktoberfest and good first issue — for example
#4146
(Edit button shown without edit permission).
What landed
The official retrospective describes upstream work, not classroom demos. Among the outcomes called out there:
- Development-environment improvements (including
vagrant-wagtail-developand Windows contributor friction that spawned new issues) - Documentation fixes and PyPI trove-identifier cleanup
- Accessible starter page work and custom-logo handling in admin
- CSS / media-query fixes and a more mobile-friendly image edit page
- Proof-of-concept thinking around automated accessibility and visual regression testing
- Permissions/UI fixes and document-chooser UX when no documents exist yet
- Django deprecation / test work aimed at future compatibility
- Dynamic image URL template-tag work from core contributors
- Russian translation improvements and roughly 40% Belarusian localisation started during the sprint
Evenings were social in a small-gathering way: walk Minsk, share food stories (draníki get a mention; glazed cheese snacks appear in the report too), then return to code the next day.
October and Hacktoberfest
The sprint fell squarely inside Hacktoberfest 2018. Prepared Minsk issues often wore both the sprint label and a Hacktoberfest label, so newcomers opening useful PRs were already speaking the language of that October programme — even though the weekend itself was a Wagtail Space event, not a meetup branded as Hacktoberfest.
For Minsk Python Meetup, that weekend is an early chapter in local October open-source culture. Dedicated Hacktoberfest gatherings under our own banner came later, starting in 2020. See the Hacktoberfest pages for how the community hosted kick-offs from then on.