Evergreen DokuWiki

• Currently confirming but no code of conduct issues - it is rare that we do have one but always good to be able to repeat.
• Platform handled our scale well. Some people reported having to leave and come back in but not much.
• Audio and video quality were good.
• The session/room jumping went well.
• The dual Dev/Doc chat rooms went well.
• Screen sharing went well.
• Only during one event was I aware of some lag/jitter creating verbal chat from being disjointed.
• Survey responses were positive.

• Sessions are misnamed. They act as rooms and persist for the entire event. This lesson will let us schedule events in a more intuitive way in the future.
• We had one spammer drop a single message in general chat. Getting rid of it was not problematic but some moderation will be necessary to watch for disruptive events in the future as we did this time.
• Recorded should be part of the name for events that are recorded.
• Events should be evaluated for if they should stay in a main chat channel or broken out.
• We need to balance privacy concerns with making people move around like migratory birds.

• Relative to past Hack-A-Ways fewer patches were written but a number of core committers were also absent or busy elsewhere during the event. That may simply be a reflection of the general busyness that I know myself and others I’ve spoken to have had this year.
• Progress was made on some significant issues including but not limited to the selection of a new release manager, a new SIP connection manager, support for Ubuntu 20.04, removal of cruft from Evergreen/OpenSRF, GitHub vs Gitea and did have several new bugs written and tested.
• We never had to use the moderator role for events but it could still be useful for someone events if we get crashers. However, someone to take questions can be helpful since placing the Hopin screen on the one being shared causes some trippy recursion.
• We did have record attendance thanks to the accessibility of being online, 55 people.

Several people commented that it was the best Hack-A-Way they had ever been to and learned more than they ever had in the past.

• This has already been provided to them via Twitter which they have been responsive to in the past.

• Ability to turn off video and/or audio per session
• Ability to enter a session muted and/or with camera disabled
• Per person volume controls would be nice. Some people’s microphones were way more sensitive than other people’s. I am used to this on platforms like Discord.

• Video recordings are done per scheduled event not session/room in two-hour blocks.
• Video appears to only be recorded when something is actively happening. Some sessions would have three videos and one might be 0 bytes in size. The largest video is 3.18 gigs.
• Videos do not include chat.
• Every session does include an analytics file as well as chat file which is independent of video recording.
• General Analytics file contains the number of unique visitors, average time spent in session, unique visitors that chatted, and total number of comments.
• The chat log is a complete log of timestamp, user name, and what was typed.

• Sort through videos for Youtube content. Figure out how to include chat if at all
• Since there was some expectation of privacy I am going to keep the general statistics for all sessions and place them on the wiki but chat logs for non-recorded events will be destroyed.
• Send out a post-event survey to participants. Correction: I had previously written that we didn't have an email list for attendees. I later found one buried in the stock report downloads that will be used.
• Provide to board as final report.
• Ask a cross-section group who worked on the Online Conference and Online Hack-a-Way to compare and contrast Zoom vs. Hopin for future events.

• Registrations 68
• turnout 53
• Average Time Spent in Events 920 minutes
• Total Comments (text) 1,697