After each DrupalSouth conference the committee sends out an online survey to gain feedback on the event. We use this information to help shape (and hopefully improve) the next event.
For those people who provided feedback - thank you for taking the time.
About the data
The feedback form received 38 submissions within the timeframe of 18 March - 24 March 2025. The feedback form was sent out via email to registrants of the event.
Quantitative feedback has been redacted to use only the options available in the feedback form, with other user provided feedback options being noted in our comments.
Qualitative data has been processed and summarised using AI, with specific names or other identifying data being redacted post AI processing.
Feedback processed via AI is in blockquote text, and feedback from the Drupalsouth committee follows.
TLDR
Communication
- 95% said pre-event comms were "just right".
- Attendees want updates on sessions (52%), keynotes (45%), speakers (34%)—but really, everything (42%).
- Preferred channels: Email (100%), Slack (40%), LinkedIn (40%).
Content & Speakers
- 79% rated speakers/topics as excellent.
- Day 2 keynote, Justin Warren was a hit; mix of tech/non-tech appreciated, though some wanted more Drupal focus.
- Suggested: better speaker vetting, improved panels, more ops/infra talks, and clearer BoF structure.
Venue & Catering
- Venue was a standout: loved location, AV, accessibility.
- Catering received mixed reviews: limited variety, quality concerns, dietary gaps.
Tickets & Value
- Most tickets were covered by employers or speaker/volunteer roles (55%).
- Ideal ticket price: $400–$600 AUD.
- Future cost-saving ideas: smaller cities, reduced swag/alcohol, BYO meals.
Future Content Preferences
- Want more: deep dives (58%), panels (39%), audience interaction (31%), diverse speakers (28%).
Community Vibe
- Loved: keynotes, mix of content, social/networking elements, overall energy.
- Least liked: session timing, cramped sponsor area, repetition in ceremony intros.
Suggestions for 2026
- Avoid date clashes with religious periods.
- Consider dev days, student projects, quiet zones.
- Improve speaker prep & MC quality.
- Use anonymous Q&A tools, balance tech/business content.
- Better marketing to attract younger devs.
DrupalSouth 2026 - New Zealand 2026?
- 49% Yes, 38% Maybe – strong support!
The long version of DrupalSouth Melbourne 2025 feedback!
The amount of communication from the organisers in the lead up to the event was:
-
Inadequate: 2.5%
-
Just Right: 95%
-
Too much: 2.5%
Committee:
Great! Thanks for the feedback, it looks like we’ll aim to do this same type of communication into the future.
What do you want to hear about from the event organisers in the lead up to the conference?
-
Keynote topics: 45%
-
General sessions: 52%
-
Speakers: 34%
-
Networking drinks: 18%
-
After parties: 13%
-
Sprint Day: 24%
-
Splash Awards: 21%
-
All of the above!: 42%
-
Omitted results: 3%
Committee:
Thanks, we’ll work on this.
The 3 custom responses omitted were specifically related to speaker communications. This has been noted, and we’ll coordinate with the track leads to better communicate and provide materials earlier and consistently across all tracks.
How do you prefer to receive communications from the event organisers?
-
DrupalSouth emails: 100%
-
X (formerly known as Twitter): 3%
-
Slack (#australia-nz channel): 40%
-
groups.drupal.org: 0%
-
Facebook: 5%
-
LinkedIn: 40%
-
Colleagues & Friends: 3%
-
Local Drupal Meetups: 13%
-
blueSky: 11%
-
Fediverse: 3%
Committee:
Looks like we’ll keep up the emails, Slack and Linkedin posts!
The quality of speakers & topics was:
-
Excellent: 79%
-
Adequate: 21%
-
Poor: 0%
Committee:
This is positive to see. Other qualitative feedback suggests that these may not be the exact thoughts and feelings though.
Please provide any feedback about speaker selection, topics or alternative session formats:
The conference received mixed feedback. Many attendees praised the overall event, highlighting the benefits of fewer sessions, more time for networking, and a good balance of technical and non-technical content. The second keynote was widely praised as compelling and relevant. Some felt that too many sessions focused on non-Drupal topics, while others appreciated the diversity of content.
Suggestions for improvement included better structuring of Birds of a Feather (BoF) sessions, potentially scheduling them before day two or during breaks. There were also calls for more workshops and operations/infrastructure talks. Some attendees were disappointed by trivia taking up a session slot and felt that speaker vetting should prioritise presentation skills. Panel discussions were criticised for being poorly moderated or running out of time, and some closed sessions were seen as not providing enough value for the ticket price.
Overall, while most talks were well-received, there was room for improvement in speaker selection, session structure, and topic focus.
Committee:
Thank you, we’ve taken previous feedback into consideration about the duration and break time in between sessions, and feel that we’ve found a balance between running slightly over, and having time for a quick break and movement to the next session.
We thank you for the overwhelmingly positive feedback about the second keynote and are looking to incorporate Justin and his methods into future DrupalSouth priorities and projects.
While we try to choose a balanced mix of technical and non technical Drupal related talks, we understand that some of the less technical talks may not be 100% related to Drupal, and appreciate your positive feedback on this, and will work on trying to get a better balance.
For the next event, I would like to see more (Select any applicable):
-
Deep dive presentations: 58%
-
Panel discussions: 39%
-
Opportunities for audience interaction (e.g. Q&A, Roundtable / Bird of a Feather formats): 31%
-
Breaks between sessions: 0%
-
Unstructured time for socialising or networking with other attendees: 25%
-
Opportunities to engage with event sponsors:14%
-
Diversity of speakers: 28%
-
Other: 3%
Committee:
Thank you for these responses. There were 6 further ‘other’ responses.
We’ll try and promote these types of talks when speaker submissions are released at following DrupalSouth events.
Who paid for your ticket?
-
I was a speaker, volunteer or sponsor: 53%
-
I paid myself: 11%
-
Work paid: 34%
-
Other: 2%
Committee:
Although this may not be representative of the 200+ people who attended, it does show that half of our responses are from people involved in some form.
The “other” response best fit the category “I was a speaker, volunteer or sponsor”, increasing that category to 55%.
What range do you think ticket prices should be?
-
Less than $400 AUD: 43%
-
$401-$600 AUD: 54%
-
$601+ AUD: 3%
Committee:
We note that this event was more expensive due to the location, venue, and drop in sponsorship.
We are currently planning the next 3 years, and are taking this feedback into consideration to lower the cost from this year's event by choosing smaller cities.
Please provide any feedback about the event venue, facilities and catering and suggestions for future consideration:
The venue received overwhelmingly positive feedback, with many attendees praising its location, facilities, accessibility, and high-quality AV setup. Several speakers appreciated the tech support, noting that it reduced setup stress and improved the overall experience. Many encouraged using similar venues in the future.
Committee:
Thank you, it’s going to be a hard venue to beat, especially the AV tech support that went above and beyond our expectations.
Catering, however, was a common point of criticism. While some found it acceptable, others felt it was lacking compared to previous years, with complaints about limited variety (mostly sandwiches), poor quality, and issues with dietary accommodations. A few suggested removing catering to lower ticket costs and allowing attendees to source their own meals.
Other minor concerns included the split-level layout affecting the event flow, limited space in the catering/sponsor area, and an issue with the water dispenser on the first day. Despite these concerns, the overall sentiment was that the event was well-organised, and the venue was one of the best used for this conference.
Committee:
We agree that the catering didn’t hit the mark. Unfortunately, with most venues the caterer is locked in and we do not get a choice on who we can use. This was the case with ACMI. The committee's focus is to ensure that the venue can support all of DrupalSouth’s requirements - which are complex. Surprisingly, there are not many venues even in the major cities that can support 3 tracks for 250 people within the budget we work with. We will try our best to work on food options going forward.
What did you like MOST about the event?
Attendees highlighted the excellent keynotes, engaging speakers, and valuable insights into Drupal and its community. The event was praised for its well-organised structure, vibrant atmosphere, and opportunities for networking and collaboration.The venue received significant appreciation for its location, facilities, and display capabilities, with some also noting the comfortable seating. Social aspects, including networking drinks and the Splash Awards, were seen as great additions to the event. The mix of business and technical sessions was well-received, and many enjoyed hearing how different organisations use Drupal to solve challenges.
Overall, the event was seen as a success, with strong community engagement and a great balance of content and social interaction.
Committee:
Thanks! We felt the positive vibes too.
What did you like LEAST about the event?
Feedback on the event highlighted a few areas for improvement. Some attendees felt the event went too quickly and lacked sufficient focus on Drupal CMS topics, with certain sessions feeling underdeveloped or impromptu. The sponsor and meal areas were considered cramped, leading to discomfort due to overcrowding and warmth. There was also a desire for more engaging presenters, as some presenters were seen as disappointing and lacking new perspectives.
Committee:
While we’re looking for plenty of variety in presentations, we rely on presenters volunteering their own time and experiences. DrupalSouth is the opportunity for new and inexperienced speakers to come forward. Each year the committee looks specifically for these people to include in the program - this ensures that our community remains fresh with new faces.
DrupalCMS is still a new area for most people, so this would contribute to it being a strong topic.
We also want to encourage first time speakers, and will work on supporting those people better.
We acknowledge that the sponsor and food area was cramped during meal times.
Attendees noted logistical challenges, such as difficulty finding people due to limited space, and the event's timing coinciding with a busy period in Melbourne, causing issues with accommodation and commuting. Additionally, the Splash Awards were criticised for being too long and having excessive preamble.
On the positive side, the seating in session rooms was appreciated, and there was acknowledgment of the efforts made with available resources. Suggestions for future events included condensing repetitive elements in opening and closing remarks for a smoother flow.
Committee:
We acknowledge we will never be able to please 100% of our audience; and feel there are a few things to highlight from DrupalSouth’s experience.
Booking venues in big cities are hard - the committee looked at 30+ venues before we settled on ACMI. Our date choices were limited to 2 available dates. To tell you the truth, F1 was not on our radar when we booked, we will look at how we can check against these events in the future.
Last year we had criticism that entries for Splash Awards were unclear and did not seem transparent on what made a winning entry. This year we tried to be more transparent so that everyone understood the process behind the selection process. We will try and find a better balance next time.
The committee accepts the opening and closing remarks was repetitive, we will do our best to make this more entertaining next time!
Please provide any other specific ideas and feedback you have to make the next DrupalSouth event more engaging and effective:
Feedback for DrupalSouth highlighted several areas for improvement and suggestions for future events:
- Timing and Scheduling: Feedback suggested moving the event dates to avoid conflicts with religious fasting periods (e.g., Baha'i and Muslim fasting in March). They also recommended clearer schedules outside venues and at the venue entrance to help attendees know what’s happening next.
- Event Structure: Some suggestions were a dedicated developer day, a student contribution project to encourage hands-on learning, and a focus on customer-facing content to showcase Drupal’s capabilities. Others proposed extending the conference to 2.5 days with more time for socialising and winding down.
- Cost and Accessibility: There were calls for lower ticket prices, reduced expenses on alcohol and swag, and eliminating advertising on event T-shirts to make the event more affordable for the average attendee.
- Venue and Logistics: A quiet room for winding down and adjustments to room temperatures and layout were suggested. Also, a better balance of business-focused and technical content was encouraged to attract non-technical Drupal users.
- Improvements for Engagement: Suggestions included using software for anonymous Q&A during sessions, shortening speeches and introductions at awards, and improving the pace of the Splash Awards ceremony to keep it engaging.
- Speaker Quality and Communication: There was feedback about speakers relying too much on reading slides and not engaging enough with the audience. Improving communication with speakers before, during, and after the event was also noted as a key area for improvement, with some suggesting an experienced MC from the community.
- Marketing and Attracting a Younger Audience: To appeal to younger developers, the event could focus more on marketing and consider smaller events with lower ticket prices to make it more accessible to a wider audience.
Overall, while the event received positive feedback for its organisation and venue, there were calls for more attention to accessibility, speaker engagement, event structure, and communication.
Committee:
Thank you, all points acknowledged.
We're trying to get a sense of the numbers for DrupalSouth 2026 - coming to New Zealand. Are you planning on joining us in New Zealand in 2026?
-
Yes: 47%
-
No: 13%
-
Maybe: 32%
-
Other: 8%
The 3 results under “other” would best be split into 1 Yes, and 2 Maybe, changing the results to something similar to:
-
Yes: 49%
-
No: 13%
-
Maybe: 38%
Committee:
DrupalSouth was set up to support both the Australian and New Zealand Drupal communities. Part of this commitment is that every third year we hold DrupalSouth in New Zealand - and 2026 is one of these years. It is great to hear that 47.4% (and a further 31.6% would consider it) of people who responded to this question are happy to travel to New Zealand next year. The committee will put some thought into how we provide opportunity for the remaining 21% to be involved.