[docs] Update callemall to mui-org (mui#9284)

Author: mbrookes

.github/ISSUE_TEMPLATE.md

@@ -6,7 +6,7 @@
 -->
 
 <!-- Checked checkbox should look like this: [x] -->
-- [ ] I have searched the [issues](https://github.com/callemall/material-ui/issues) of this repository and believe that this is not a duplicate.
+- [ ] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.
 
 ## Expected Behavior
 <!--- 
@@ -26,7 +26,7 @@
     Include code to reproduce, if relevant (which it most likely is). 
 
     This codesandbox.io template _may_ be a good starting point: 
-    https://codesandbox.io/s/github/callemall/material-ui/tree/v1-beta/examples/create-react-app
+    https://codesandbox.io/s/github/mui-org/material-ui/tree/v1-beta/examples/create-react-app
 
 
     If YOU DO NOT take time to provide a codesandbox.io reproduction, should the COMMUNITY take time to help you? 

CHANGELOG.md

@@ -231,7 +231,7 @@ Big thanks to the 14 contributors who made this release possible.
 
 Here are some highlights ✨:
 - New InputAdornment component (#8504)
-- New [Frequently asked questions](https://github.com/callemall/material-ui/blob/4df547d56448cedf70977d6e2463b38eaf64d1c7/docs/src/pages/getting-started/frequently-asked-questions.md) documentation section
+- New [Frequently asked questions](https://github.com/mui-org/material-ui/blob/4df547d56448cedf70977d6e2463b38eaf64d1c7/docs/src/pages/getting-started/frequently-asked-questions.md) documentation section
 - We have saved 1 KB gzip by removing our internal react-transition-group fork (#8785)
 - We have made one step further in order to upgrade all our development dependencies to react@16 (#8804)
 
@@ -1705,7 +1705,7 @@ Big thanks to the 11 contributors who are pushing the `next` branch forward.
 
 We are continuing investing in the documentation and the test suite.
 
-Visual regression tests are now sent to [argos-ci](https://www.argos-ci.com/callemall/material-ui).
+Visual regression tests are now sent to [argos-ci](https://www.argos-ci.com/mui-org/material-ui).
 Thanks @agamrafaeli for increasing the test coverage of 1% since the last release (95.23%).
 Thanks @mbrookes for fixing the inconsistency of the API and improving the API.
 
@@ -2028,12 +2028,12 @@ We are releasing sooner than we use to for this **special day** :christmas_tree:
 
 2016 has been an exceptional year for Material-UI.
 - We went from 40k to 180k [downloads](https://npm-stat.com/charts.html?package=material-ui&from=2014-12-24&to=2016-12-25) a month. :package:
-- We went from 12k to 22k [stars](http://www.timqian.com/star-history/#callemall/material-ui). :star:
+- We went from 12k to 22k [stars](http://www.timqian.com/star-history/#mui-org/material-ui). :star:
 
 That wouldn't have been possible without this awesome community.
 **Thank you!**
 
-But this's just the beginning, some [exciting stuff](https://github.com/callemall/material-ui/blob/master/ROADMAP.md) is coming in 2017 :sparkles:.
+But this's just the beginning, some [exciting stuff](https://github.com/mui-org/material-ui/blob/master/ROADMAP.md) is coming in 2017 :sparkles:.
 You can preview a **very early** version of the `next` branch following [that link](https://material-ui-next.com).
 
 #### Component Fixes / Enhancements
@@ -2112,7 +2112,7 @@ This is another release improving the stability of `v0.16.x`.
 ## 0.16.3
 ###### _Nov 17, 2016_
 
-This release is intended to solve an [issue](https://github.com/callemall/material-ui/issues/5573) with `react-tap-event-plugin` following the release of React `v15.4.0`.
+This release is intended to solve an [issue](https://github.com/mui-org/material-ui/issues/5573) with `react-tap-event-plugin` following the release of React `v15.4.0`.
 
 #### Component Fixes / Enhancements
 
@@ -2221,7 +2221,7 @@ We are switching in goal so we can release changes more **often**.
 Regarding going forward, this is likely to be the last `minor` release using the **inline-style** approach.
 We are migrating all the components to a **CSS-in-JS** approach on the `next` branch.
 
-For more details, you can have a look a the [next milestone](https://github.com/callemall/material-ui/milestone/14) as well as the [next project](https://github.com/callemall/material-ui/projects/1)
+For more details, you can have a look a the [next milestone](https://github.com/mui-org/material-ui/milestone/14) as well as the [next project](https://github.com/mui-org/material-ui/projects/1)
 
 :warning: New features based on the `master` branch (inline-style) have low priority and will most likely not be reviewed nor merged.
 
@@ -2609,7 +2609,7 @@ documentation page.
 
 Have a ton of imports? almost had a heart attack? worry not, we also made a tool
 to ease your pain. checkout the
-[readme](https://github.com/callemall/material-ui/tree/master/packages/material-ui-codemod/README.md).
+[readme](https://github.com/mui-org/material-ui/tree/master/packages/material-ui-codemod/README.md).
 
 ##### Breaking Changes
 - [Core] Improve import path for published lib (#3921)
@@ -2799,7 +2799,7 @@ import MUI from 'material-ui'; // no changes here :D
 This release includes huge improvements to the implementation
 of components and utility modules. The most important improvement
 is the removal of mixins from the library, thanks to the
-[great efforts](https://github.com/callemall/material-ui/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aclosed+author%3Anewoga+style-propable)
+[great efforts](https://github.com/mui-org/material-ui/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aclosed+author%3Anewoga+style-propable)
 of @newoga :+1:
 
 There are also improvements to the unit testing infrastructure. We own this
@@ -3693,7 +3693,7 @@ We've cleaned up some of our click/tap events. (#771) Upgrade should be straight
     component specific. In addition to the benefits mentioned in the
     presentation, inline styles allow Material-UI to become CSS preprocessor
     agnostic and make Themeing much more dynamic and simple.
-    [Read our CSS in JS discussion](https://github.com/callemall/material-ui/issues/30)
+    [Read our CSS in JS discussion](https://github.com/mui-org/material-ui/issues/30)
   - Upgrade path:
     - *If you are overriding component CSS classes:* Redefine your overrides as
       an object following [React's inline styles format](https://facebook.github.io/react/tips/inline-styles.html),
@@ -3702,10 +3702,10 @@ We've cleaned up some of our click/tap events. (#771) Upgrade should be straight
       overriding a nested element of the component, check the component's
       documentation and see if there is a style prop available for that nested
       element. If a style prop does not exist for the component's nested element
-      that you are trying to override, [submit an issue](https://github.com/callemall/material-ui/issues/new)
+      that you are trying to override, [submit an issue](https://github.com/mui-org/material-ui/issues/new)
       requesting to have it added.
     - *If you are using any of Material-UI's Less files:* These files have been
-      refactored into their [own javascript files](https://github.com/callemall/material-ui/tree/css-in-js/src/styles)
+      refactored into their [own javascript files](https://github.com/mui-org/material-ui/tree/css-in-js/src/styles)
       and can be accessed like so `var FILENAME = require('material-ui').Styles.FILENAME;`.
       Material-UI has moved away from being a CSS Framework to being simply a
       set of React components.
@@ -3862,7 +3862,7 @@ We've cleaned up some of our click/tap events. (#771) Upgrade should be straight
       For FontIcon, create a custom font file and include it in your project and just pass the Icon
       className into the FontIcon component. For SvgIcon, create a new React component that represents
       that particular icon. This will allow you to package your icons inside your js files. Examples
-      can be found [here](https://github.com/callemall/material-ui/tree/master/src/js/svg-icons).
+      can be found [here](https://github.com/mui-org/material-ui/tree/master/src/js/svg-icons).
     - Additionally, all components that had an icon prop now take an iconClassName prop instead. These
       include FloatingActionButton, IconButton, Menu, MenuItem, and DropDownIcon.
 

CONTRIBUTING.md

@@ -10,11 +10,11 @@ When in doubt, keep your pull requests small. To give a PR the best chance of ge
 
 As with issues, please begin the title with [ComponentName].
 
-When adding new features or modifying existing, please attempt to include tests to confirm the new behaviour. You can read more about our test setup [here](https://github.com/callemall/material-ui/blob/v1-beta/test/README.md).
+When adding new features or modifying existing, please attempt to include tests to confirm the new behaviour. You can read more about our test setup [here](https://github.com/mui-org/material-ui/blob/v1-beta/test/README.md).
 
 ### Branch Structure
 
-All stable releases are tagged ([view tags](https://github.com/callemall/material-ui/tags)). At any given time, `v1-beta` represents the latest development version of the library.
+All stable releases are tagged ([view tags](https://github.com/mui-org/material-ui/tags)). At any given time, `v1-beta` represents the latest development version of the library.
 Patches or hotfix releases are prepared on an independent branch.
 
 #### `v1-beta` is unsafe
@@ -33,7 +33,7 @@ Please create a new branch from an up to date v1-beta on your fork. (Note, urgen
 
 If you have an existing local repository, please update it before you start, to minimise the chance of merge conflicts.
 ```js
-git remote add upstream git@github.com:callemall/material-ui.git
+git remote add upstream git@github.com:mui-org/material-ui.git
 git checkout v1-beta
 git pull upstream v1-beta
 git checkout -b my-topic-branch
@@ -110,12 +110,12 @@ Then, you will need to add the following code:
 
 #### 4. You are done 🎉!
 
-In case you missed something, [we have a real example that can be used as a summary report]((https://github.com/callemall/material-ui/pull/8922/files)).
+In case you missed something, [we have a real example that can be used as a summary report]((https://github.com/mui-org/material-ui/pull/8922/files)).
 
 ## Roadmap
 
-To get a sense of where Material-UI is heading, or for ideas on where you could contribute, take a look at the [ROADMAP](https://github.com/callemall/material-ui/blob/v1-beta/ROADMAP.md).
+To get a sense of where Material-UI is heading, or for ideas on where you could contribute, take a look at the [ROADMAP](https://github.com/mui-org/material-ui/blob/v1-beta/ROADMAP.md).
 
 ## License
 
-By contributing your code to the callemall/material-ui GitHub repository, you agree to license your contribution under the MIT license.
+By contributing your code to the mui-org/material-ui GitHub repository, you agree to license your contribution under the MIT license.

README.md

@@ -9,7 +9,7 @@ that you can use to tag your questions.
 # [Material-UI@v1-beta](https://material-ui-next.com/)
 [![npm package](https://img.shields.io/npm/v/material-ui/next.svg)](https://www.npmjs.org/package/material-ui)
 [![CircleCI](https://img.shields.io/circleci/project/github/mui-org/material-ui/v1-beta.svg)](https://circleci.com/gh/mui-org/material-ui/tree/v1-beta)
-[![Gitter](https://img.shields.io/badge/gitter-join%20chat-f81a65.svg)](https://gitter.im/mui-org/material-ui?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+[![Gitter](https://img.shields.io/badge/gitter-join%20chat-f81a65.svg)](https://gitter.im/callemall/material-ui?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 [![Coverage Status](https://img.shields.io/codecov/c/github/mui-org/material-ui/v1-beta.svg)](https://codecov.io/gh/mui-org/material-ui/branch/v1-beta)
 [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/1320/badge)](https://bestpractices.coreinfrastructure.org/projects/1320)
 
@@ -63,24 +63,24 @@ render(<App />, document.querySelector('#app'));
 ## Examples
 
 Are you looking for an example project to get started?
-[We host some](https://github.com/callemall/material-ui/blob/v1-beta/docs/src/pages/getting-started/example-projects.md).
+[We host some](https://github.com/mui-org/material-ui/blob/v1-beta/docs/src/pages/getting-started/example-projects.md).
 
 ## Documentation
 
 Check out our [documentation website](https://material-ui-next.com/).
 
 ## Contributing
 
-We'd greatly appreciate any [contribution](https://github.com/callemall/material-ui/blob/v1-beta/CONTRIBUTING.md) you make. :)
+We'd greatly appreciate any [contribution](https://github.com/mui-org/material-ui/blob/v1-beta/CONTRIBUTING.md) you make. :)
 
 ## Changelog
 
 Recently Updated?
-Please read the [changelog](https://github.com/callemall/material-ui/releases).
+Please read the [changelog](https://github.com/mui-org/material-ui/releases).
 
 ## Roadmap
 
-The future plans and high priority features and enhancements can be found in the [ROADMAP.md](https://github.com/callemall/material-ui/blob/v1-beta/ROADMAP.md) file.
+The future plans and high priority features and enhancements can be found in the [ROADMAP.md](https://github.com/mui-org/material-ui/blob/v1-beta/ROADMAP.md) file.
 
 ## Thanks
 
@@ -91,4 +91,4 @@ Thank you to [BrowserStack](https://www.browserstack.com/) for providing the inf
 ## License
 
 This project is licensed under the terms of the
-[MIT license](https://github.com/callemall/material-ui/blob/v1-beta/LICENSE).
+[MIT license](https://github.com/mui-org/material-ui/blob/v1-beta/LICENSE).

ROADMAP.md

@@ -9,16 +9,16 @@ The roadmap is a living document, and it is likely that priorities will change,
 Version 1 release is going to be huge ✨.
 We host a temporary [documentation site](https://material-ui-next.com) for the pre-releases.
 
-Material-UI was started [3 years ago](https://github.com/callemall/material-ui/commit/28b768913b75752ecf9b6bb32766e27c241dbc46).
+Material-UI was started [3 years ago](https://github.com/mui-org/material-ui/commit/28b768913b75752ecf9b6bb32766e27c241dbc46).
 The ecosystem has evolved a lot since then, we have also learned a lot.
 [@nathanmarks](https://github.com/nathanmarks/) started an ambitious task, rebuilding Material-UI from the **ground-up**
 taking advantage of this knowledge to address long-standing issues.
 Expect various **breaking changes**.
 
-The core team is now helping him in the [v1-beta](https://github.com/callemall/material-ui/tree/v1-beta) branch.
+The core team is now helping him in the [v1-beta](https://github.com/mui-org/material-ui/tree/v1-beta) branch.
 If you are interested in following our progress or if you want to help us reach that goal faster, you can have a look at the following milestones:
-- ~~[v1.0.0-beta](https://github.com/callemall/material-ui/milestone/22)~~ - complete!
-- [v1.0.0-prerelease](https://github.com/callemall/material-ui/milestone/14)
+- ~~[v1.0.0-beta](https://github.com/mui-org/material-ui/milestone/22)~~ - complete!
+- [v1.0.0-prerelease](https://github.com/mui-org/material-ui/milestone/14)
 
 ## Q&A with the v1 version
 
@@ -70,11 +70,11 @@ We should answer the following questions:
 - What trade-offs are we going to make?
 - What features will be implemented?
 
-That conversation could start on one of the following [issues](https://github.com/callemall/material-ui/issues?q=is%3Aissue+is%3Aopen+label%3ARefactoring+label%3Anext).
+That conversation could start on one of the following [issues](https://github.com/mui-org/material-ui/issues?q=is%3Aissue+is%3Aopen+label%3ARefactoring+label%3Anext).
 
 ### How do I know if a component still needs to be migrated `v1-beta`?
 
-We have [some open issues](https://github.com/callemall/material-ui/issues?q=is%3Aopen+is%3Aissue+label%3ARefactoring+label%3Av1) to **coordinate** the work toward the `v1.0.0` release.
+We have [some open issues](https://github.com/mui-org/material-ui/issues?q=is%3Aopen+is%3Aissue+label%3ARefactoring+label%3Av1) to **coordinate** the work toward the `v1.0.0` release.
 
 ### How do I start migrating components to the `v1-beta` branch?
 
@@ -90,7 +90,7 @@ That's really up to you. At least, you going to have to:
 
 We don't have an ETA for the release of the `v1`, however, we are going to try to follow this plan:
 
-1. ~~We completely address the styling issue before moving from *alpha* to [*beta*](https://github.com/callemall/material-ui/milestone/22).~~
+1. ~~We completely address the styling issue before moving from *alpha* to [*beta*](https://github.com/mui-org/material-ui/milestone/22).~~
 2. ~~We publish our first beta releases.~~
 3. We fix the last API inconsistencies (as we can make breaking changes without having to worry much).
 4. We merge the beta branch into master
@@ -120,5 +120,5 @@ On the other hand, using a smart date library for the DatePicker / TimePicker wo
 ## Future
 
 - Add missing components, and missing features from current ones
-- [[#7721](https://github.com/callemall/material-ui/issues/7721)] Preact support
-- [[#593](https://github.com/callemall/material-ui/issues/593)] Support React Native
+- [[#7721](https://github.com/mui-org/material-ui/issues/7721)] Preact support
+- [[#593](https://github.com/mui-org/material-ui/issues/593)] Support React Native

SUPPORT.md

@@ -6,7 +6,7 @@ For how-to questions and other non-issues, please use [StackOverflow](http://sta
 
 ## Opening an Issue
 
-If you think you have found a bug, or have a new feature idea, please start by making sure it hasn't already been [reported or fixed](https://github.com/callemall/material-ui/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aclosed). You can search through existing issues and PRs to see if someone has reported one similar to yours.
+If you think you have found a bug, or have a new feature idea, please start by making sure it hasn't already been [reported or fixed](https://github.com/mui-org/material-ui/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aclosed). You can search through existing issues and PRs to see if someone has reported one similar to yours.
 
 Next, create a new issue that briefly explains the problem, and provides a bit of background as to the circumstances that triggered it, and steps to reproduce it.
 

docs/README.md

@@ -10,5 +10,5 @@ npm run docs:dev
 
 ## How can I add a new demo in the documentation?
 
-[You can follow this guide](https://github.com/callemall/material-ui/blob/v1-beta/CONTRIBUTING.md)
+[You can follow this guide](https://github.com/mui-org/material-ui/blob/v1-beta/CONTRIBUTING.md)
 on how to get started contributing to Material-UI.

docs/src/modules/components/AppDrawer.js

@@ -81,7 +81,7 @@ function reduceChildRoutes(props, activePage, items, childPage, index) {
   return items;
 }
 
-const GITHUB_RELEASE_BASE_URL = 'https://github.com/callemall/material-ui/releases/tag/';
+const GITHUB_RELEASE_BASE_URL = 'https://github.com/mui-org/material-ui/releases/tag/';
 
 function AppDrawer(props: Object, context: Object) {
   const { classes, className, disablePermanent, mobileOpen, onRequestClose } = props;

docs/src/modules/components/AppFooter.js

@@ -39,13 +39,13 @@ function AppFooter(props: Object) {
             <Grid item xs={12} sm={6}>
               <ul className={classes.list}>
                 <li className={classes.listItem}>
-                  <Link href="https://github.com/callemall/material-ui/tree/v1-beta">GitHub</Link>
+                  <Link href="https://github.com/mui-org/material-ui/tree/v1-beta">GitHub</Link>
                 </li>
                 <li className={classes.listItem}>
                   <Link href="https://twitter.com/MaterialUI">Twitter</Link>
                 </li>
                 <li className={classes.listItem}>
-                  <Link href="https://github.com/callemall/material-ui/tree/v1-beta/examples">
+                  <Link href="https://github.com/mui-org/material-ui/tree/v1-beta/examples">
                     Examples
                   </Link>
                 </li>

docs/src/modules/components/AppFrame.js

@@ -238,7 +238,7 @@ class AppFrame extends React.Component<any, any> {
               component="a"
               title="GitHub"
               color="contrast"
-              href="https://github.com/callemall/material-ui/tree/v1-beta"
+              href="https://github.com/mui-org/material-ui/tree/v1-beta"
             >
               <Github />
             </IconButton>