Currently

• Frequency: 1 call per month, rotating between:
  • General update (moderated by Doug/Yondon)
    • High level updates on demand side of the network
  • Topic Call (moderated by Nelson)
    • brings more investor-lens
  • Node Operator Call (moderated by Doug/Yondon)
    • Tied to updates; recent events immediately relevant to node operators; eg gas prices, how node operators are selected; how can they perform well
  • NEW: AMAs hosted by Titan-Node (weekly)
    • General support
• Community Feedback:
  • Calls can be too long and try to accomplish too much
  • Could be value in more frequent and shorter calls
  • Seeking more insight into Livepeer.com, business and go to market strategy
    • Nelson's call with Glass was viewed positively

Ideas for Improvement

Goals:

• More community-driven events
• Better alignment with product roadmap
  • Communicating technical knowledge and information
  • Pre community call process; written document shared with the community in advance
    • Eg. Confluence Pre-Proposal; Fast and Full Verification

Action Items/Next Steps

• Draft agenda for Sept 30
  • Doug: High-level context for major updates to the project
  • Yondon: implications for node operators
    • Confluence (high level technical context); ongoing work on individual tracks, why those exist and why they matter for node operators
    • Fast and Full verification design
      • Context for why two tracks, long term goal, then zero in on Fast Verification
  • Future Community Calls (+Shannon's new role)
    • Get feedback - what does the community want to see going forward? How can community calls be used going forward