### Lessons Learned from Organizing Community Workshops for Open-Source Tools Pascal Sauer & Alex Hagen
notes: https://events.hifis.net/event/1741/contributions/13920/ 15 min presentation, 5 min questions -- ### setting the stage - π open source model/tool - used by some externals, interest by more - you organized workshop - with 15 participants - πΊοΈ from all over the world - hybrid - π€¦ ignored setup instructions, tech trouble - πππ online participants stay muted & invisible notes: - ~ representative situation from 3 workshops - what to expect, think about in advance for smooth workshop --- ### main goal - discuss, clarify, write down - common understanding - informs all further decisions - how to measure success? notes: we didn't do this, but should have -- #### strengthen knowledge - improve understanding of the model and its results - spark interest vs. provide in depth understanding - support informed decision if this is the right tool - basis for long-term cooperation -- #### grow community - enable people to - use and run model - develop and contribute notes: 2 examples your goal may/should be specific --- ### key questions - quite general - informed by main goal notes: if unclear, work on goal? -- #### target audience - open for all - β more people - β οΈ unpredictable (prior knowledge, commitment) - β οΈ heterogeneous audience - π©βπ» tech support required - by invitation - β more predictable, more control - β οΈ no new people --- #### workshop format - online - β more people, accessible - β οΈ potentially timezone trouble - recordings - Q&A sessions for different timezones - β οΈ challenge: camera off audience; who is following? - β οΈ less commited audience notes: - 1-2 tech support people, still slowed - ask people to turn on camera - eventually some participants started, others followed - have team join with camera -- - in-person - β οΈ less people, much less accessible - β οΈ meeting room required - β direct access for tech help - β better interaction/discussion, also outside sessions - hybrid - β οΈ more setup - β οΈ danger: 2-class audience --- #### type of sessions - input - discussion - requires good understanding - hands-on - π§βπ» tech support! - how to get feedback? - exercises? --- #### where participants work - local PC - heterogeneous systems (Windows, Mac, Linux) - π no admin permission - π super slow/outdated system - π pre-workshop setup ignored - π©βπ» lots of tech support needed -- - provide access to prepared system - β system works - suitable infrastructure required - β οΈ unfamiliar system for participants - virtual machine on PC (e.g. dockerfile) - β system works - β οΈ requires setup on PC - β οΈ unfamiliar system for participants notes: best or worst of both worlds? --- #### workshop team - organizers (timetable, website, ...) - presenters - one session per person - less work for each presenter - more coordination overhead - β οΈ danger: redundant or missing parts - π§βπ» tech support --- ## recap | **question** | **A** | **B** | **C** | |--------------|------------|------------|-----------| | **audience** | broader | interested | involved | | **format** | online | in person | hybrid | | **session** | input | discussion | hands-on | | **team** | organizers | presenters | π©βπ» tech support | --- ### recommendations - expectation management (communicate goal) - π stories session - ποΈ timetable - website with all infos, tutorials, slides notes: invited externals to present spark interest show whats possible timetable + timezone feature --
--- ### summary - π‘ clarify main goal - π€ consider ressources & key questions upfront - β οΈ prepare for complications - tricky setup problems - participants not committed, drop out - more time is needed - π be proud of spreading open source! --- ### final slide [pascal.sauer@pik-potsdam.de](mailto:pascal.sauer@pik-potsdam.de) [github.com/pascal-sauer](https://github.com/pascal-sauer) [slides on GitHub](https://github.com/pascal-sauer/open-source-community-workshops) [slides made with reveal.js](https://revealjs.com/)