Thanks to the Board for opening this discussion up here. I have a lot of thoughts but will try to be succinct (lol yeah right…).
Getting Face-to-Face
I’d been around FreeDesktop and GNOME-adjacent spaces for quite a while with elementary before getting much more involved; I started working on elementary around 2010, when we mostly existed as a sort of siloed project doing our own thing. We were young and hacking things together; we had thought about and tried contributing to some GNOME stuff, but were mostly unsuccessful due to our inexperience (and our desire to do things differently from GNOME).
We attended one Ubuntu Developer Summit in 2011, but I don’t recall mingling a whole lot with GNOME folks there (I was a bit overwhelmed by all of the people and simultaneous tracks, but still had a good time!). So, we just kind of kept doing our own thing—until @sri invited us to the GNOME West Coast Summit in 2015, which was a sort of GNOME/GTK/xdg-app (what would become Flatpak) hackfest.
There we finally met and hung out with people working on GNOME face-to-face, and it completely changed the trajectory of elementary—and honestly, my life—for the better. In particular, I had the opportunity to meet @sri, @matthiasc, @chergert, @cosimoc, @alexl, and a handful of others who were so incredibly welcoming to us relative outsiders to GNOME. We broke through several blockers to making elementary OS better, but more importantly, we developed lasting relationships with the people and project of GNOME.
A few years later in 2018 when I was able to attend GUADEC for the first time, I flew halfway across the world and walked into the venue, nervous and sort of uncomfortable—until @matthiasc greeted me and invited my over to a group of people chatting. We talked about elementary and GTK, and I started to get a whole lot more comfortable. I ended up having a great time that week, and felt like I really became a part of the community; I started to contribute to GNOME design discussions, attend more hackfests, regularly attend GUADEC, and stay in closer contact with GNOME folks afterwards.
When I left elementary, it was such a natural transition into the GNOME community for me, because I was already here and a part of it. So for me, these face-to-face experiences are monumentally important—not just for the increased bandwidth of communication and ability to work through things so much better in person (though that’s a huge benefit!), but for the humanization of the people behind usernames—and the deep, lasting connections that are made.
I genuinely don’t know if I’d be involved with the GNOME community today had I not been able to attend the in-person events I did over a span of years.
Local Community
I’ve been very impressed with the efforts of a handful of folks (hi, Berlin!) to build and nurture a local community. I’m honestly a bit jealous, because I’ve not had the time to do that nearer to me. Maybe if I had that sort of local community supporting me, I’d feel similarly connected and not feel the need for larger in-person events—but that’s not the case for me where I am today, and definitely wasn’t the case for me in 2010 or 2015 or 2018. So the global event with the opportunity to meet familiar and new faces from all across the GNOME community still seems critical to me personally.
Remote/Hybrid Events
When I was at elementary, I organized and helped host a two-day all-remote developer conference. I learned a lot there, and it really made me realize a well-done remote conference can work as an event—but it’s not a complete replacement for at least occasional centralized, in-person events. There was good sharing of information and some nice follow-up energy from people, but there was none of the high-bandwidth communication and none of the humanizing social bits.
When helping organize and run this year’s GUADEC in Denver, I felt like we did a decent job of enabling remote participation, but there was some friction with having two “separate” events between Denver and Berlin—and I feel like I really missed out collaborating and just hanging out with people who I’d been looking forward to see because they were halfway around the world.
Climate
The climate impact of traveling has come up a lot in the discussions about how to do GUADEC, but I continue to be reminded of @pwithnall’s analysis of GNOME’s climate impact where conference travel has less carbon impact than the usage of our software. That’s not to dismiss the carbon impact of travel, but to contextualize it; I do think it is necessary as humans from around the world building things together to get together in person every now and then to do it effectively—including to bring new people into the community, and to actively work on reducing the power consumption of that software that goes out to millions of people’s power-hungry computers.
My Proposal
I don’t think we necessarily need to have GUADEC as an annual thing where everyone gets together all in one place—it’s pretty clear that’s not going to happen anyway, as we would probably end up having a large European event every other year where everyone in Europe and whoever can make it from the Americas will attend, and then an event outside of Europe the other half of the time where the Europeans all meet up in Berlin.
If that’s the reality, I feel like we could take a multi-pronged approach:
-
A less-frequent but centralized/in-person “flagship” event. Call it GNOME Conference or something. I don’t really care where this is held personally, if we are able to have some amount of travel sponsorship to ensure people who would not otherwise be able to attend can also join. This could be every two years, maybe, ensuring a regular cadence but literally halving the climate impact. There should also be an explicit focus, as a policy of the event organization itself, to encourage the least climate-intense options for things like travel, local transit, lodging, and food whenever possible.
Remote participation for talks should be possible and encouraged for those who cannot otherwise make it in person, but the focus should be on getting people together face-to-face and optimizing for that (similar to GUADEC in Denver this year).
-
More frequent local events, with more documentation and support from people who have organized these successfully! Basically, let’s work to develop something like a Local Community Kit where we lay out tips and tricks, provide resources like editable designs for signage, etc. that local organizers can take and use to make a successful event. These would not need to be centrally organized or even regularly scheduled, and as we’ve seen with events in Berlin (and I’m sure elsewhere), these don’t even have to explicitly be only GNOME-focused; pairing with another open source community or a slightly wider scope of interest can encourage cross-pollination of ideas and more local community development.
-
Regular completely remote events, let’s say an annual GNOME Online Summit more like edw where it’s designed to ensure contributors are sharing their work and collaborating around shared topics, but it’s accessible to anyone with an Internet connection. This can coincide with local events as well, of course, as another way to encourage local community building.
I have no idea how practical that all is, but I think it could be a bit of a restructuring that balances climate impact, travel costs, remote participation, and local community development. And dropping the GUADEC name could signify that it’s not just “changing how we do GUADEC,” but that we’re reworking how the GNOME community does events more broadly for the better.
And lastly, we shouldn’t be afraid to iterate! While it’s nice to try to get into a rhythm, we should also be open to trying things and gathering feedback from the community, then tweaking as needed. We don’t need to have a single “correct” solution for the rest of eternity on our first try.