Engagement/Developer Engagement/Technical Evangelism/Technical Meetups: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "=Technical Meetups= '''Proposed program structure''' ==Goal== Primary: Drive mind-share for open web technologies by giving local community members technical knowledge needed...")
 
Line 26: Line 26:
** Web/JS skillz
** Web/JS skillz
** Github skillz
** Github skillz
==Event Guide==
* Add an SOP to the Reps wiki for how to run a developer meetup.


==Budget==
==Budget==

Revision as of 15:12, 20 August 2014

Technical Meetups

Proposed program structure

Goal

Primary: Drive mind-share for open web technologies by giving local community members technical knowledge needed to talk to web developers.

Secondary: Grow community in Technical Evangelism.

Content

a.k.a "Meetup in a Box" (MUIAB)

  • Topic-based resources (e.g., Web APIs, Fx Dev Tools)
  • Example code
  • Discussion points
  • Video/screencasts (stored on AirMo?)
    • Created by SMEs (staff or volunteers)
    • Give them a framework (questions to cover) and tools (for screencasts)
    • Use Moderator for Q&As

Content project

  • Contractor to set up MUIAB structure and initial topics
  • Initial topics based on existing Hacks content and community requests
  • Set up framework for SMEs
  • Requirements
    • Instructional design familiarity (use learning objectives for each topic)
    • Web/JS skillz
    • Github skillz

Event Guide

  • Add an SOP to the Reps wiki for how to run a developer meetup.

Budget

  • Use Reps for process and disbursement
  • Channel budget to Reps ($1000/mo)
  • Swag

Community of Organizers

  • Use Evangelism@ mailing list
  • Give feedback on content
  • Sharing best practices