Challenge Leads: Geraldo Barros (@barrosgeraldo), Chad Sansing (@chadsansing)
How might we teach the web even when we can't reach it?
That's the questions this Offline Games Challenge seeks to answer.
For the Mozilla Privacy Arcade Offline Game Challenge, your job is to invent games that let players:
- Participate in a fun, safe, and inviting environment that welcomes players of diverse backgrounds.
- Enact strong online safety habits through offline childhood, playground, and tabletop games.
- Enact core Internet health principles, such as digital inclusion. For example, if you incorporated privacy and digital inclusion into your game, part of winning might be making sure that all players successfully finish the game together in different ways or by using different roles.
- Make their learning as visible or invisible as they want. For example, players should be able to look like they're playing a harmless game in places where its difficult for them to teach and learn about privacy and security in the open.
- Make connections and transfer skills between their games and real-life opportunities to practice online safety.
Here are some ideas to get you started. For example, you might:
- Invent a game of information keep-away to show how encrypted packets keep their contents secret while traveling across the web.
- Adapt a popular social, collaborative game like Werewolf (sometimes called Mafia) to encourage players to work together to identify a data thief among them.
- Craft or repurpose a board game that lets players collect everything they need to practice strong privacy and security habits online.
Share your adventure in the Offline Games Challenge folder of our Mozilla Privacy Arcade repo and keep us up-to-date on your work by tweeting at @MozLearn with the hashtag #mozsprint. More about repos below.
There are lots of ways to contribute to this project that use different skills and talents. For example:
- Someone who loves to tell stories might invent several games and share them by explaining their user stories, or the ways players might experience those games.
- Someone who loves to draw might design game boards or pieces or illustrate other contributors' ideas for games.
- Someone who loves design might gather a bunch of friends during the sprint to play-test several contributors' games and offer feedback on them for revision.
- Someone who loves to teach might invent a game and create a lesson plan for it or for another contributor's game.
- Someone who loves to code might adapt a game into an online prototype people can play on the web before they learn how to play it offline.
All of our contributors and their work deserve care and thanks.
If you're unsure of what to contribute or how to contribute a piece of work, never hesitate to ask a project lead for help. We are here to support you and will be answering questions throughout the sprint.
Whether know a million games or are new to game design or the Global Sprint, we want you to feel welcome contributing to the project of your choice.
These resources might help you get started with inventing childhood, playground, and tabletop games.
- Build Your Own Board Game
- 10 Fun Games from Around the World
- What deduction games like Werewolf tell us about ourselves
- How to write rules (without confusing people).
- 11 Rules for Board Game Rules Writing
Of course. It's fine to begin the sprint with work already in-hand. You should feel free to set up for the sprint however you'd like. You might:
- Invent some games beforehand to test during the sprint.
- Research childhood, playground, or table-top games that people play around the world for inspiration.
- Reserve space now to host a "site" or meet-up during the sprint (see more details about hosting a site below).
Just keep in mind that we're asking you to license the work openly so our everyone can use, adapt, and build upon your contributions (see more about licensing below).
We’ve set up a repo for the projects you make in response to these challenges. You can check out what the greater Global Sprint community is up to on the 2017 Global Sprint landing page.
A repo is a repository - or collection of files - that belong together on GitHub. All the files contributed by everyone working on your project will eventually wind up in 1 repo so you can see each other's work, give feedback, and adapt it for yourself or your own communities.
If you are new to GitHub, it is totally fine to work on another platform, like in a Google Document, and to copy and paste your text into an issue or to share a link to your work through an issue. A project or challenge lead will put it into the master "repo" (repository), or collection of work, for you.
Please note that we’re asking all contributors to apply a Creative Commons-Attribution 4.0 license to whatever non-code contributions they make during the sprint. We’re asking contributors to license code contributions with the Mozilla Public License 2.0.
However you decide to work or whatever you make, there are lots of ways to contribute:
- Spreading word about the Global Sprint beforehand through your professional and interest-based networks.
- Organizing a team ahead of the sprint and helping it prepare.
- Hosting a site, or meet-up, during the sprint for people in your community so they can work together in person.
- Proposing helpful changes to other contributor's content with "pull requests," or requests to pull new content into older files to update them.
- Crafting new content for the project and contributing it through pull request, issue, or link.
- Sharing resources by filing an issue.
- Sharing feedback by filing an issue.
- GitHub vets, fork the repo and submit pull requests.
There is no wrong way to contribute, and project and challenge leads are here to answer your questions help you get your work into the repo. You should feel free and empowered to share your work before, during, and after the sprint on social media (like through blogs, Facebook, and Twitter), as well.
Thank you for your contributions to the challenges in our Mozilla Privacy Arcade project.
GitHub can be challenging for new users. If you experience difficulty with it, you are not alone. We want to help you overcome those challenges or find a way to contribute that works for you.
For this project in the Global Sprint, we can use a feature called the "Issue Tracker" in GitHub to communicate with one another. It's kind of like a shared message board combined with a to-do list. To address an issue to a specific person, you add their name to the issue the same way you would to a tweet, like this for example: @chadsansing would address your message to Chad, one of our project leads.
If the Issue Tracker is too difficult to use, contact a project lead. We will work with you and help you find a way to contribute no matter what.
Here are some steps you can take to get started on GitHub if you'd like to try it.
-
First, create an account on GitHub.
-
Then visit our repo or the folder for the challenge you'd like to work on during the sprint.
-
Next, click on the "Issues" tab near the top of the page.
-
Finally, click on the green "New Issue" button to the left of the page. You can then title your issue and add content. Specificity helps.
Before you submit your issue, label it. You can choose one from the "Labels" dropdown menu to the right of your issue. Add the light-green #mozsprint label to each issue to file and then pick the label that goes with the challenge you're working on during the sprint. This helps people find the people and issues associated with the challenge to which they're contributing.
We have challenge labels for:
- offline-game-challenge (orange)
We also have labels for site-related news, as well as for finding help and answering questions:
- site-related is light purple.
- help-wanted is red.
- questions are blue.
After you apply all your labels, your issue should have a #mozsprint label, your challenge label, and possibly a site-related, help-wanted, or question label.
If you'd like to learn even more about GitHub, check out the GitHub for Collaboration section of Mozilla's Open Leadership Training Series.
If you organize a team for the Global Sprint or would like to run a "site" - like a meet-up at a community center or in a learning space or makerspace - visit this page to learn how to register your event.
Site leaders receive support from project and challenge leads to help people learn and work together face-to-face. They commit to being on-site from 9AM to 5 PM local time each day so they can:
- Welcome people who come to work in-person.
- Ensure that your site is a safe and friendly working environment for all.
- Help to promote the Global Sprint to your communities and encourage local participation.
- Serve as a point of contact for communicating (updates, progress) with the rest of the Sprint during the event.
- Help to collect data on activities on the Site (number of participants and contributions).
If you would like to host and register a site, let a project lead know how to help. We will make sure you feel well-prepared to host a site.
This year’s Global Sprint runs for 48 hours from June 1st, 2017, to June 2nd, 2017. Sprint hours are 9 AM to 5 PM in your local timezone. You can sprint for a few hours, for a day, or for both days. You can contribute to 1 project or several. There is no wrong way to participate in the sprint.
We will be curating and sharing your work throughout the sprint, so keep in touch and let us know how things are going at @MozLearn on Twitter using the hashtag #mozsprint.
You can also see "Featured Projects" on Mozilla's Network Pulse, our resource for sharing exciting events and resources with our community.
We’d love to keep up with you after the Global Sprint, as well, to follow the development of your projects. We can also help you write a session proposal for this year’s MozFest.
Questions? File an issue and cc @chadsansing or email Chad.
Let’s go play.