We used a Jira project to work in two-weekly sprints, identifying tasks that needed to be done and assigning them to people in our working groups. We met fortnightly until around two months before the event when we switched to weekly meetings. This meant that we could always find the information we needed, and made it simple to create the next event because all the information from the previous year was easily accessible. Having now run two successful events, I have promised several folks to write up how we did it.so herewith the long overdue writeup!įrom the start, we decided to keep everything we did - from recordings of calls to notes, research, contracts, marketing comms and design files - in a shared Google Drive folder. In the Mautic Community, we had never organised an in-person event, let alone a digital event, so it was definitely breaking new ground!
Then came the global pandemic, and two years of varying lockdown levels, forcing many communities to pivot unexpectedly from the in-person events which are the lifeblood of an Open Source community to finding a way to digitise these events. Rewind just over two years and we were about to organise our first ever Mautic World Conference - MautiCon for short - at Acquia's head office in Boston.
0 kommentar(er)
