rename master to main

Author: almccon

.travis.yml

@@ -5,7 +5,7 @@ before_install:
  - npm install -g geojsonhint
 branches:
   only:
-    - master
+    - main
 rvm:
   - 2.2.2
 script:

CONTRIBUTING.md

@@ -6,7 +6,7 @@ We'd love for you to contribute and help make [Maptime.io](http://maptime.io) be
 Code for Conduct
 ----------------
 
-Help us keep Maptime open and inclusive. Please read and follow our [Code of Conduct](https://github.com/maptime/code-of-conduct/blob/master/code-of-conduct.md).
+Help us keep Maptime open and inclusive. Please read and follow our [Code of Conduct](https://github.com/maptime/code-of-conduct/blob/main/code-of-conduct.md).
 
 Need a question answered?
 -------------------------
@@ -24,7 +24,7 @@ If you find a bug, or issue in the documentation, you can help us out by [creati
 
 Want to contribute without writing code?
 ----------------------------------------
-Help us move the [abs-of-cartography](https://github.com/maptime/abcs-of-cartography/wiki) over to our [glossary](https://github.com/maptime/maptime.github.io/blob/master/_data/glossary.yml).  Each entry in the wiki should have an entry in the website's glossary.  The format is as follows:
+Help us move the [abs-of-cartography](https://github.com/maptime/abcs-of-cartography/wiki) over to our [glossary](https://github.com/maptime/maptime.github.io/blob/main/_data/glossary.yml).  Each entry in the wiki should have an entry in the website's glossary.  The format is as follows:
 
 ```yml
 # Add a term to the glossary:
@@ -46,7 +46,7 @@ Before you submit your pull request consider the following guidelines:
 - Make your changes in a new git branch
 
      ```
-     git checkout -b my-fix-branch master
+     git checkout -b my-fix-branch main
      ```
 
 - Commit your changes using a descriptive commit message
@@ -63,7 +63,7 @@ Before you submit your pull request consider the following guidelines:
     git push origin my-fix-branch
     ```
 
-- In GitHub, send a pull request to `maptime.github.io:master`.
+- In GitHub, send a pull request to `maptime.github.io:main`.
 
 That's it, thanks!
 

README.md

@@ -1,4 +1,4 @@
-[![Build Status](https://travis-ci.org/maptime/maptime.github.io.svg?branch=master)](https://travis-ci.org/maptime/maptime.github.io)
+[![Build Status](https://travis-ci.org/maptime/maptime.github.io.svg?branch=main)](https://travis-ci.org/maptime/maptime.github.io)
 
 maptime.github.io
 =================
@@ -72,6 +72,6 @@ $ gem install rdiscount
 Clone the [maptime.github.io repo](http://github.com/maptime/maptime.github.io) on your computer. Then switch into that file directory.
 
 ```
-$ git clone -b master git@github.com:maptime/maptime.github.io.git
+$ git clone -b main git@github.com:maptime/maptime.github.io.git
 $ cd maptime.github.io
 ```

_posts/2014-10-24-maptime-has-a-new-website.md

@@ -27,7 +27,7 @@ With the new website it's easier than ever to get the materials you need to star
 1. __Get on Slack__: [Slack](https://maptime.slack.com/messages/general/) is our internal chat app for all things Maptime. We have channels for everything from website admin to tutorials. It's a great way to manage your chapter's communications. We'll send you an invite to get you squared away.
 1. __Get on Github__: we use Github for everything from [managing our website](https://github.com/maptime/maptime.github.io/issues) to writing our [Code of Conduct](https://github.com/maptime/code-of-conduct). You and your admins can be added to teams where you can get access to the Maptime organization, your chapter's repo, or other privileges that you think you need.
 
-Once you're all setup, you can add your new chapter to the [map](http://maptime.io/chapters/). With the new re-design all you need to do is add your information in [one place](https://github.com/maptime/maptime.github.io/blob/master/_data/chapters.json) and make a __pull request__. Once your chapter has its first meeting scheduled, you'll see your chapter added to the map and the Chapters listing automatically!
+Once you're all setup, you can add your new chapter to the [map](http://maptime.io/chapters/). With the new re-design all you need to do is add your information in [one place](https://github.com/maptime/maptime.github.io/blob/main/_data/chapters.json) and make a __pull request__. Once your chapter has its first meeting scheduled, you'll see your chapter added to the map and the Chapters listing automatically!
 
 ### [Curated resources to get started with mapping](http://maptime.io/lessons-resources/)
 

chapters/README.md

@@ -4,9 +4,9 @@
 
 1. Ask [Alan](https://twitter.com/mappingmashups) (or some other Maptime organizer) to make you an owner on the GitHub organization.
 2. Publicize your membership!  (Go [here](https://github.com/orgs/maptime/people), find you, and click **make public**.)
-3. Add your chapter to [chapters.geojson](https://github.com/maptime/maptime.github.io/blob/master/_data/chapters.json) -- We use this to populate our map and the listing of Maptime Chapters!
-    - If you have the [geojson.io chrome extension](https://chrome.google.com/webstore/detail/geojsonio/oibjgofbhldcajfamjganpeacipebckp?hl=en-US) installed you'll see a link to the geojson.io editor above the [Chapters map](https://github.com/maptime/maptime.github.io/blob/master/_data/chapters.json) on GitHub.
-    - Otherwise open the file in the geojson.io editor by [clicking here!](http://geojson.io/#id=github:maptime/maptime.github.io/blob/master/_data/chapters.json&map=3/29.56/-54.94)
+3. Add your chapter to [chapters.geojson](https://github.com/maptime/maptime.github.io/blob/main/_data/chapters.json) -- We use this to populate our map and the listing of Maptime Chapters!
+    - If you have the [geojson.io chrome extension](https://chrome.google.com/webstore/detail/geojsonio/oibjgofbhldcajfamjganpeacipebckp?hl=en-US) installed you'll see a link to the geojson.io editor above the [Chapters map](https://github.com/maptime/maptime.github.io/blob/main/_data/chapters.json) on GitHub.
+    - Otherwise open the file in the geojson.io editor by [clicking here!](http://geojson.io/#id=github:maptime/maptime.github.io/blob/main/_data/chapters.json&map=3/29.56/-54.94)
 4. Add your chapter as a new marker to the map (be sure to click **Table** and add twitter and contact info).
 5. Click **Save > GitHub** and add a commit message (maybe something like "just added Maptime Null Island chapter!").
 6. You're done!

chapters/start.md

@@ -25,13 +25,13 @@ Forking a site means you're making a copy of it to your account and the origin r
 1. Once you have a fork of the site, create a folder for your chapter.
 ![start-add-folder](/img/start-add-folder.png)
 Keep things simple by naming your folder after your city. 
-1. Add a file named `index.html` and copy contents from the [/nullisland/index.html](https://github.com/maptime/maptime.github.io/blob/master/nullisland/index.html) file for the template into your new file.
+1. Add a file named `index.html` and copy contents from the [/nullisland/index.html](https://github.com/maptime/maptime.github.io/blob/main/nullisland/index.html) file for the template into your new file.
 1. Modify your details.
 1. When you're finished, commit the new file (it's like saving it) and add a commit message like '_Adds new Maptime chapter for Null Island!_'
 1. Once committed, go back to the root directory of your repo and make a __Pull Request__ (aka PR) by clicking the green button to the left of your repo's branch name.
 ![start-pull](/img/start-pull.png)
 1. A new page appears where you can review your changes.
-1. Make sure you are making a PR from your repo's branch to the maptime.github.io master branch.
+1. Make sure you are making a PR from your repo's branch to the maptime.github.io main branch.
 ![start-compare](/img/start-compare.png)
 1. Add a nice, relevant message regarding the changes you're proposing.
 1. Finally, click the big shiny green __Create Pull Request__ button. It's ok, you won't break anything. Extra points if you tag an admin with Maptime to notify them of changes (e.g. @geografa).