doc: fix github urls to use the new org

Signed-off-by: Fabio Utzig <fabio.utzig@nordicsemi.no>

README.md

 # [mcuboot](http://mcuboot.com/)
 
 [![Coverity Scan Build Status](https://scan.coverity.com/projects/12307/badge.svg)][coverity]
-[![Build/Test](https://img.shields.io/travis/JuulLabs-OSS/mcuboot/master.svg?label=travis-ci)][travis]
+[![Build/Test](https://img.shields.io/travis/mcu-tools/mcuboot/master.svg?label=travis-ci)][travis]
 
 [coverity]: https://scan.coverity.com/projects/mcuboot
-[travis]: https://travis-ci.org/JuulLabs-OSS/mcuboot
+[travis]: https://travis-ci.org/mcu-tools/mcuboot
 
 This is mcuboot version 1.7.0-rc1
 
@@ -33,7 +33,7 @@ Instructions for different operating systems can be found here:
 The issues being planned and worked on are tracked using GitHub issues. To
 participate please visit:
 
-[MCUBoot GitHub Issues](https://github.com/JuulLabs-OSS/mcuboot/issues)
+[MCUBoot GitHub Issues](https://github.com/mcu-tools/mcuboot/issues)
 
 ~~Issues were previously tracked on [MCUboot JIRA](https://runtimeco.atlassian.net/projects/MCUB/summary)
 , but it is now deprecated.~~

boot/cypress/README.md

@@ -43,7 +43,7 @@ Those are represented as submodules.
 
 To retrieve source code with subsequent submodules pull:
 
-    git clone --recursive https://github.com/JuulLabs-OSS/mcuboot.git
+    git clone --recursive https://github.com/mcu-tools/mcuboot.git
 
 Submodules can also be updated and initialized separately:
 

docs/SECURITY.md

@@ -39,7 +39,7 @@ vulnerabilities found within published code will undergo an embargo of
 Vulnerability reports and published fixes will be reported as follows:
 
 - Issues will be entered into Github's [Security Advisory
-  system](https://github.com/JuulLabs-OSS/mcuboot/security/advisories), with
+  system](https://github.com/mcu-tools/mcuboot/security/advisories), with
   the interested parties (including the reporter) added as viewers.
 
 - The release notes will contain a reference to any allocated CVE(s).

docs/SubmittingPatches.md

 # Submitting Patches
 
 Development on mcuboot primarily takes place in github, at:
-https://github.com/JuulLabs-OSS/mcuboot
+https://github.com/mcu-tools/mcuboot
 
 Changes should be submitted via github pull requests.  Each commit
 should have a Signed-off-by line for the author (and the committer, if

docs/index.md

@@ -41,7 +41,7 @@ of date.  You should use `imgtool.py` instead of these documents.
 The issues being planned and worked on are tracked using GitHub issues. To participate
 please visit:
 
-[MCUboot Issues](https://github.com/JuulLabs-OSS/mcuboot/issues)
+[MCUboot Issues](https://github.com/mcu-tools/mcuboot/issues)
 
 ~~Issues were previously tracked on [MCUboot JIRA](https://runtimeco.atlassian.net/projects/MCUB/summary)
 , but it is now deprecated.~~
@@ -55,13 +55,13 @@ Information and documentation on the bootloader is stored within the source.
 
 For more information in the source, here are some pointers:
 
-- [boot/bootutil](https://github.com/JuulLabs-OSS/mcuboot/tree/master/boot/bootutil): The core of the bootloader itself.
-- [boot/boot\_serial](https://github.com/JuulLabs-OSS/mcuboot/tree/master/boot/boot_serial): Support for serial upgrade within the bootloader itself.
-- [boot/zephyr](https://github.com/JuulLabs-OSS/mcuboot/tree/master/boot/zephyr): Port of the bootloader to Zephyr
-- [boot/mynewt](https://github.com/JuulLabs-OSS/mcuboot/tree/master/boot/mynewt): Mynewt bootloader app
-- [boot/mbed](https://github.com/JuulLabs-OSS/mcuboot/tree/master/boot/mbed): Port of the bootloader to Mbed-OS
-- [imgtool](https://github.com/JuulLabs-OSS/mcuboot/tree/master/scripts/imgtool.py): A tool to securely sign firmware images for booting by MCUboot.
-- [sim](https://github.com/JuulLabs-OSS/mcuboot/tree/master/sim): A bootloader simulator for testing and regression
+- [boot/bootutil](https://github.com/mcu-tools/mcuboot/tree/master/boot/bootutil): The core of the bootloader itself.
+- [boot/boot\_serial](https://github.com/mcu-tools/mcuboot/tree/master/boot/boot_serial): Support for serial upgrade within the bootloader itself.
+- [boot/zephyr](https://github.com/mcu-tools/mcuboot/tree/master/boot/zephyr): Port of the bootloader to Zephyr
+- [boot/mynewt](https://github.com/mcu-tools/mcuboot/tree/master/boot/mynewt): Mynewt bootloader app
+- [boot/mbed](https://github.com/mcu-tools/mcuboot/tree/master/boot/mbed): Port of the bootloader to Mbed-OS
+- [imgtool](https://github.com/mcu-tools/mcuboot/tree/master/scripts/imgtool.py): A tool to securely sign firmware images for booting by MCUboot.
+- [sim](https://github.com/mcu-tools/mcuboot/tree/master/sim): A bootloader simulator for testing and regression
 
 ## Joining
 

docs/readme-mbed.md

@@ -16,7 +16,7 @@ To use MCUboot, you need to create an Mbed OS project with the following configu
 * `"mcuboot.max-img-sectors"`: maximum number of sectors, should be at least the number of sectors in each slot
 * `"target.restrict_size"`: the maximum size of the bootloader, such that it does not overlap with the primary slot
 
-More configurations such as signing algorithm, slot swapping, etc. can be found in [mbed_lib.json](https://github.com/JuulLabs-OSS/mcuboot/tree/master/boot/mbed/mbed_lib.json). Please note that certain features are not currently supported.
+More configurations such as signing algorithm, slot swapping, etc. can be found in [mbed_lib.json](https://github.com/mcu-tools/mcuboot/tree/master/boot/mbed/mbed_lib.json). Please note that certain features are not currently supported.
 
 ### Providing a secondary slot
 

docs/readme-mynewt.md

@@ -14,7 +14,7 @@ First you need to add the repo to your `project.yml`:
     repository.mcuboot:
         type: github
         vers: 0-dev
-        user: JuulLabs-OSS
+        user: mcu-tools
         repo: mcuboot
 ```
 

go.mod

-module github.com/JuulLabs-OSS/mcuboot
+module github.com/mcu-tools/mcuboot
 
 go 1.14

samples/zephyr/mcutests/mcutests.go

 // Package mcutests
-package mcutests // github.com/JuulLabs-OSS/mcuboot/samples/zephyr/mcutests
+package mcutests // github.com/mcu-tools/mcuboot/samples/zephyr/mcutests
 
 // The main driver of this consists of a series of tests.  Each test
 // then contains a series of commands and expect results.

samples/zephyr/run-tests.go

@@ -25,7 +25,7 @@ import (
 	"strings"
 	"time"
 
-	"github.com/JuulLabs-OSS/mcuboot/samples/zephyr/mcutests"
+	"github.com/mcu-tools/mcuboot/samples/zephyr/mcutests"
 )
 
 // logIn gives the pathname of the log output from the Zephyr device.

scripts/setup.py

@@ -8,7 +8,7 @@ setuptools.setup(
     author_email="mcuboot@groups.io",
     description=("MCUboot's image signing and key management"),
     license="Apache Software License",
-    url="http://github.com/JuulLabs-OSS/mcuboot",
+    url="http://github.com/mcu-tools/mcuboot",
     packages=setuptools.find_packages(),
     python_requires='>=3.6',
     install_requires=[

testplan/mynewt/project.yml

@@ -32,5 +32,5 @@ repository.apache-mynewt-core:
 repository.mcuboot:
     type: github
     vers: 0-dev
-    user: JuulLabs-OSS
+    user: mcu-tools
     repo: mcuboot