View source for Connected Devices/Participation/Events/Evaluation

{{draft}}

== Summary ==

This document is meant as an initial guide for anyone evaluating Connected Devices events, e.g. Reps Review Board deciding whether to sponsor an event.

== Need Help? ==

If you need more help, you can reach out to the following people:

* [https://mozillians.org/u/mhenretty/ Michael Henretty] - CD Collaboration Wizard
* [https://mozillians.org/u/dietrich/ Dietrich Ayala] - Developer Relations Revolutionary
* [https://mozillians.org/u/kinger/ Brian King] - Participation Kingpin

== Event Types ==

There are various types of formats that CD events can take. While this list is not exhaustive, here are some:

* Hack and Learn
** Bring a laptop and other necessary devices, and learn by doing
** [https://air.mozilla.org/community-spaces-running-hack-and-learn-events/ QA for MozSpaces crew], with some useful information
* Ideation / Design Sprints
** Similar to what we did with our team of volunteers and staff in MozLondon
** [https://github.com/mozilla/connected-devices/issues/7 More to come...]
* Project Meetups
** Groups of people meeting to contribute to CD projects
* Prototyping Contests
** Groups of people working to build things in short time, hackathon style.
** e.g. [https://reps.mozilla.org/e/iot-hackday-hyderabad-1/ IoT HackDay Hyderabad]

== Criteria And Expected Outcomes ==

* Event planning requirements
** What kind of goals do we want for these meetups? Eg, basic hardware programming literacy, or design briefs around a specific set of user research?
** CD has their own research group for topics they are exploring, and we will sync with them. Other than that, focusing on Innovation is the direction they want us to take.
* Technology requirements
** Must be Open Source
** Does there need to be a connection to Firefox or web platform technologies?
*** We don't see this being a requirement at this point. The general direction we have been receiving from CD leadership is to innovate without being burden by platform requirements.
* Logistics requirements
** How to setup and run a good event is outside the scope of this document. However, make sure most of the basics are in place such as: Venue; Event schedule; Awareness of target audience - know the type of people you want to attract to your event; Invite platform, e.g. meetup, eventbrite - does it include an opt-in way to keep the relationship going with attendees, and send follow-up emails?
* Event outcome requirements
** Blog post summarizing the event, with photos, links to relevant code repos, and other outputs
** Ideation / Design workshops - Capture:
*** Ideas
*** Interview responses
*** Storyboards
*** Prototypes