User Tools

Site Tools


hackaway:final-report:2020:report

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
hackaway:final-report:2020:report [2020/10/30 11:04] roganhhackaway:final-report:2020:report [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 8: Line 8:
   * Screen sharing went well.   * Screen sharing went well.
   * Only during one event was I aware of some lag/jitter creating verbal chat from being disjointed.   * Only during one event was I aware of some lag/jitter creating verbal chat from being disjointed.
 +  * Survey responses were positive.  
  
 ==Lessons Learned For Future Events== ==Lessons Learned For Future Events==
Line 14: Line 15:
   * 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.   * 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.   * 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.
  
 ==General Observations== ==General Observations==
-  * Not a lot of code was written during the event 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.  +  * 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.   * 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 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.
Line 41: Line 44:
   * Sort through videos for Youtube content.  Figure out how to include chat if at all   * 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.     * 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.  Unfortunately, the event does not provide us with a list of all participant emails so we will have to just send it out via email and social media.+  * Send out a post-event survey to participants.  Correction: I had previously written that we didn'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.   * 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.    * 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. 
Line 63: Line 66:
  
  
-    +== Event Numbers ==
- +
- +
  
  
 +  * Registrations 68
 +  * turnout 53
 +  * Average Time Spent in Events 920 minutes 
 +  * Total Comments (text) 1,697
  
  
  
  
hackaway/final-report/2020/report.1604070264.txt.gz · Last modified: 2022/02/10 13:34 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.