maptime-onboarding.md

Typical chapter request

• Interested individual visits the website and navigates to http://maptime.io/chapters/ to look for existing maptime chapter in their area.
• If they're interested in starting a chapter, they navigate to http://maptime.io/start/ and fill out the embedded Typeform form which collects their name, email address, location, github username, and the desired name of their chapter.
• The submitted form data is sent to two places:
  • Complete form data is sent to the private chapter google sheet
  • Form data minus the email address is used to populate an issue at the maptime-admin github repo using user geografa, which is labelled as a repo request as well as mentions and alerts the maptime/onboarders team
• Repo request issues are monitored by members the onboarders team and self-assigned, who then become the designated onboarding liason and are responsible for completing the steps below

Maptime onboarding procedure

1. Confirm the following :

• Desired chapter location does not have an existing or pending chapter.
• Submitted request contains a valid github username. If not, send an email to the address on file in the master google sheet
• Desired chapter name is appropriate, unambiguous, and geographically relevant.

If onboarder is on a platform that can run a bash script, onboarding.sh can be used to automate steps 2 through 5
2. Create a new chapter repo in the Maptime organization using the name of the chapter city (e.g. newyork)
3. Clone a copy of the starter repo into a gh-pages branch
4. Create an admin team and name using the chapter location (e.g. us-ca-sandiego or fr-paris), adding the chapter repo with default write privleges 5. Add the github user that submitted the repo request to the admin team.

6. Add the organizer to Slack using the email addresss on file
7. Post a confirmation in the github repo request issue
   Following template may be used, replacing the text between < >

Hello @<githubName>. I created a repo to manage your web page, which uses our starter template. I gave you write privileges.

repo: https://github.com/maptime/<repoName>
site: http://maptime.io/<repoName>

Please customize your site by editing the [_config.yml](https://github.com/maptime/<repoName>/blob/gh-pages/_config.yml) file in the gh-pages branch. I am happy to assist with this if help is needed. We recommend securing a twitter handle and using it to promote your events and interact with your community. (e.g. `@<chapterName>`). If you choose to create a twitter account, please update the _config.yml.  Let me know if you need help learning how to create posts/events on your site. You're also free to scrap this starter template if you prefer to build a custom web page.

We'll also need to get you added to the map and list at http://maptime.io/chapters. To do that, we will add your chapter to [chapters.json](https://github.com/maptime/maptime.github.io/blob/master/_data/chapters.json). If you feel comfortable doing so, please edit the file with your chapter information using the existing entries as an example and submit a pull request. If not, we can take care of that for you. Just respond to this issue.

You should have received an invite to join our Slack, which is what we primarily use for communication between fellow organizers and with Maptime leadership (also known as MaptimeHQ). Please post any other questions you might have about how to get started building Maptime<chapterName> in the #general channel on Slack. I'm `@<yourSlackName>` there.  If you have been able to recruit any additional organizers, please send me a direct message with their name, email address, and github name.

Thanks!

8. Close the github issue but monitor for additional responses
9. Monitor Slack and send a friendly welcome message when the user joins

Additional tasks may include:

• Assisting organizer with any github-related tasks listed above (i.e. customizing the website, creating posts)
• Adding additional organizers to the Maptime github org and admin team as well as Slack